ISSUE N 1 MAJOR MODIFICATIONS. Version Changes Related Release No. PREVIOUS VERSIONS HISTORY. Version Date History Related Release No.

Similar documents
Exhibitor Software and 21 CFR Part 11

Compliance Matrix for 21 CFR Part 11: Electronic Records

21 CFR Part 11 Module Design

21 CFR PART 11 COMPLIANCE

ChromQuest 5.0. Tools to Aid in 21 CFR Part 11 Compliance. Introduction. General Overview. General Considerations

NucleoCounter NC-200, NucleoView NC-200 Software and Code of Federal Regulation 21 Part 11; Electronic Records, Electronic Signatures (21 CFR Part 11)

TECHNICAL BULLETIN [ 1 / 13 ]

COMPLIANCE. associates VALIDATOR WHITE PAPER. Addressing 21 cfr Part 11

Compliance of Shimadzu Total Organic Carbon (TOC) Analyzer with FDA 21 CFR Part 11 Regulations on Electronic Records and Electronic Signatures

Adobe Sign and 21 CFR Part 11

REGULATION ASPECTS 21 CFR PART11. 57, av. Général de Croutte TOULOUSE (FRANCE) (0) Fax +33 (0)

WHITE PAPER AGILOFT COMPLIANCE WITH CFR 21 PART 11

21 CFR Part 11 FAQ (Frequently Asked Questions)

OpenLAB ELN Supporting 21 CFR Part 11 Compliance

The Impact of 21 CFR Part 11 on Product Development

Integration of Agilent UV-Visible ChemStation with OpenLAB ECM

SDA COMPLIANCE SOFTWARE For Agilent ICP-MS MassHunter Software

Integration of Agilent OpenLAB CDS EZChrom Edition with OpenLAB ECM Compliance with 21 CFR Part 11

Agilent ICP-MS ChemStation Complying with 21 CFR Part 11. Application Note. Overview

Sparta Systems TrackWise Solution

Sparta Systems Stratas Solution

EZChrom Elite Chromatography Data System. Regulatory Compliance with FDA Rule of Electronic Records and Electronic Signatures (21 CFR Part 11)

Sparta Systems TrackWise Digital Solution

INFORMATION. Guidance on the use of the SM1000 and SM2000 Videographic Recorders for Electronic Record Keeping in FDA Approved Processes

Electronic Data Processing 21 CFR Part 11

System Assessment Report Relating to Electronic Records and Electronic Signatures; 21 CFR Part 11. System: tiamo (Software Version 2.

FDA 21 CFR Part 11 Compliance by Metrohm Raman

Metrohm White paper. FDA 21 CFR Part 11 Requirements for NIR Spectroscopy. Dr. N. Rühl

Technical Information

Using "TiNet 2.5 Compliant SR1" software to comply with 21 CFR Part 11

Validation Checklist Appendix A WiZARD2 Secure and 21 CFR 11 Requirements

System Assessment Report Relating to Electronic Records and Electronic Signatures; 21 CFR Part 11. System: StabNet (Software Version 1.

System Assessment Report Relating to Electronic Records and Electronic Signatures; Final Rule, 21 CFR Part 11

21 CFR Part 11 LIMS Requirements Electronic signatures and records

Introduction 2. History. Adapted to zenon version 6.20 (MH) January 13 th, 2006

White Paper Assessment of Veriteq viewlinc Environmental Monitoring System Compliance to 21 CFR Part 11Requirements

System Assessment Report Relating to Electronic Records and Electronic Signatures; Final Rule, 21 CFR Part 11. System: tiamo 2.3

Using Chromeleon 7 Chromatography Data System to Comply with 21 CFR Part 11

Cell Therapy Data Management

Guidelines for applying FactoryTalk View SE in a 21 CFR Part 11 environment

Part 11 Compliance SOP

Using the Titrando system to comply with 21 CFR Part 11

21 CFR 11 Assistant Software. 21 CFR Part 11 Compliance Booklet

Using "IC Net 2.2 " software to comply with 21 CFR Part 11

Assessment of Vaisala Veriteq viewlinc Continuous Monitoring System Compliance to 21 CFR Part 11 Requirements

Using Chromeleon Chromatography Management Software to Comply with 21 CFR Part 11

ComplianceQuest Support of Compliance to FDA 21 CFR Part 11Requirements WHITE PAPER. ComplianceQuest In-Depth Analysis and Review

Electronic Records and Signatures with the Sievers M9 TOC Analyzer and DataPro2 Software

Agilent Response to 21CFR Part11 requirements for the Agilent ChemStation Plus

Using the Titrando system to comply with 21 CFR Part 11

Guidance for a 21 CFR Part 11 implementation on Microsoft Office SharePoint Server 2007

OM-MICROLITE-8 AND OM- MICROLITE-16 DATA LOGGERS AND OM-MICROLAB

Meeting regulatory compliance guidelines with Agilent ICP-MS MassHunter and OpenLAB Server

Spectroscopy Configuration Manager (SCM) Software. 21 CFR Part 11 Compliance Booklet

System Assessment Report Relating to Electronic Records and Electronic Signatures; Final Rule, 21 CFR Part 11. System: tiamo 2.0

Achieving 21 CFR Part11 Compliance using Exaquantum/Batch Authored by Stelex

How to get your Movicon 11 project FDA 21 CFR Part 11 ready. Document: RAC-4105 Released: Updated: Rel. Movicon: 11.

Agilent Technologies Dissolution Workstation Software Electronic Records and Data Storage Background

Automation Change Management for Regulated Industries

State of Colorado Cyber Security Policies

21 CFR PART 11 FREQUENTLY ASKED QUESTIONS (FAQS)

Achieving 21 CFR Part 11 Compliance using CENTUM VP

MySign Electronic Signature

SECURITY & PRIVACY DOCUMENTATION

Introduction. So what is 21 CFR Part 11? Who Should Comply with 21CFR Part 11?

TECHNICAL AND ORGANIZATIONAL DATA SECURITY MEASURES

21 CFR Part 11 Fundamentals

EU Annex 11 Compliance Regulatory Conformity of eve

New York Department of Financial Services Cybersecurity Regulation Compliance and Certification Deadlines

Electronic Signature Policy

90% 191 Security Best Practices. Blades. 52 Regulatory Requirements. Compliance Report PCI DSS 2.0. related to this regulation

Chapter 9 Section 3. Digital Imaging (Scanned) And Electronic (Born-Digital) Records Process And Formats

TECHNICAL AND ORGANIZATIONAL DATA SECURITY MEASURES

HIPAA Compliance Checklist

User Manual. Version 1 1/10/ of 26

Criminal Justice Information Security (CJIS) Guide for ShareBase in the Hyland Cloud

Statement of 21 CFR Part 11 Validation Results

Achieving 21 CFR Part 11 Compliance using CENTUM VP

Enterprise Income Verification (EIV) System User Access Authorization Form

The University of Texas at El Paso. Information Security Office Minimum Security Standards for Systems

Policy Document. PomSec-AllSitesBinder\Policy Docs, CompanyWide\Policy

Canadian Access Federation: Trust Assertion Document (TAD)

DFARS Requirements for Defense Contractors Must Be Satisfied by DECEMBER 31, 2017

Canadian Access Federation: Trust Assertion Document (TAD)

Summary. Implementing CFR21 Part 11 with Movicon 11 Page 2

eprost System Policies & Procedures

2016 SC REGIONAL HOUSING AUTHORITY NO. 3 S EIV SECURITY POLICY

Minnesota State Colleges and Universities System Procedures Chapter 5 Administration

Real World Examples for Part 11 Technical Controls

testo Comfort Software CFR 4 Instruction manual

Table of Contents. PCI Information Security Policy

ORA HIPAA Security. All Affiliate Research Policy Subject: HIPAA Security File Under: For Researchers

System Administrator s Guide Login. Updated: May 2018 Version: 2.4

Access to University Data Policy

Security Policies and Procedures Principles and Practices

Policy and Procedure: SDM Guidance for HIPAA Business Associates

Wescom Solutions, Inc. Practitioner Engagement Android Version CFR EPCS Certification Report

Hong Kong Access Federation (HKAF) Identity Management Practice Statement (IMPS)

Learning Management System - Privacy Policy

Employee Security Awareness Training Program

Transcription:

ISSUE N 1 MAJOR MODIFICATIONS Version Changes Related Release No. 01 First issue. 2.8.0 PREVIOUS VERSIONS HISTORY Version Date History Related Release No. N/A N/A N/A N/A APPROVAL TABLE Signatures below signify that the content of the document was reviewed and approved for correctness, accuracy, reliability and completeness. Prepared by: Patrice Joly, Validation Specialist, Document Author Information Technology: Document Reviewers/Approvers Signature: Date: Validation: Signature: Date: Quality Assurance: Signature: Date: Page 1 of 11

US FDA 21 CFR PART 11 ASSESSMENT FOR COMPLIANCE WITH QM? Subpart B Electronic Records 11.10 Controls for Closed Systems Persons who use closed systems to create, modify, maintain, or transmit electronic records shall employ procedures and controls designed to ensure the authenticity, integrity, and, when appropriate, the confidentiality of electronic records, and to ensure that the signer cannot readily repudiate the signed record as not genuine. Such procedures and controls shall include the following : Is this a closed system (i.e. a system that does not use the public internet or public email systems and is administered by an individual responsible for its operation)? Yes Yes The system is installed within a corporate network and access is controlled by system administrators. (a) Validation of systems to ensure accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records. Has the system been or will the system be validated? Yes or No (Based on Client Decision) Yes The system validation is the responsibility of the client. provides a validation package to support the validation of the system. However some clients may choose to take care of the validation without any help from. (b) The ability to generate accurate and complete copies of records in both human readable and electronic form suitable for inspection, review, and copying by the agency. Persons should contact the agency if there are any questions regarding the ability of the agency to perform such review and copying of the electronic records. Can the system produce the requested information in both electronic and human readable form? Yes No Records that are created when using QM can be accessed in a human readable form by different means i.e. 1- directly in the GUI (Graphical User Interface) by the use of menus (e.g. accessing a Document audit trail), where the information can be printed, or 2- by using direct means (e.g. reports) of accessing the data stored in the database. Page 2 of 11

? (c) Protection of records to enable their accurate and ready retrieval throughout the records retention period. Are the Electronic records being maintained in electronic format for the time periods required by applicable regulations? Yes Yes QM system enables archiving and retrieval of records. (Retention period determination is responsibility of client and should be governed by client s SOP.) Backup and recovery procedure should be tested as part of the Installation Qualification protocol execution. SOP on Backup and Recovery (d) Limiting system access to authorized individuals. Is system access restricted to appropriate personnel? Yes Yes System access is controlled and limited to authorized individuals by use of a valid and unique combination of User Name and Password. SOP on System Access (f) Use of operational system checks to enforce permitted sequencing of steps and events as appropriate. Does the system use checks to enforce sequencing of steps and events? (optional) Yes No System enables operational system checks permitting sequencing majorly in documents, process and ad hoc tasks treating, superseding, referencing and retiring actions. Page 3 of 11

? (g) Use of authority checks to ensure that only authorized individuals can use the system, electronically sign a record, access the operation or computer system input or output device, alter a record, or perform the operation at hand Are adequate security measures in place to protect the system? Yes Yes System access, use and actions within system are restricted only to authorized individuals who have been given access (refer to d) and appropriate privileges. (It is client responsibility to determine level of system access per user). (h) Use of device (e.g. terminal) checks to determine, as appropriate, the validity of the source of data input or operational instruction. (i) Determination that persons who develop, maintain, or use electronic record/electronic signature systems have the education, training, and experience to perform their assigned tasks. Does the system use terminal checks to determine the validity of the source of the input? (optional) Are appropriate employee qualifications documented in accordance with internal SOPs, including training records, CV s, and Job Descriptions? No No N/A N/A Yes Yes personnel involved in system development and testing are trained on applicable procedures and training records are maintained. (j) The establishment of, and adherence to, written policies that hold individuals accountable and responsible for actions initiated under their electronic signatures, in order to deter record and signature falsification. If electronic signatures are used, is there a corporate policy or SOP that holds individuals accountable and responsible for actions initiated under their electronic signatures? No Yes Page 4 of 11

? (k) Use of appropriate controls over systems documentation including (1) Adequate controls over the distribution of, access to, and use of documentation for system operation and maintenance. (1) Are controls in place for the distribution, access, retention and use of all system documentation? No Yes (2) Revision and change control procedures to maintain an audit trail that documents time-sequenced development and modification of systems documentation. (2) If the system is developed /maintained in-house, are controls in place to maintain a revision history for system documentation? Yes Yes maintains a quality system based on ISO 9001 requirements. Changes to the application are documented and all relevant system documentation is reviewed in accordance with the changes. The information on changes is communicated to the user. To system documentation 11.30 Controls for Open Systems Persons who use open systems to create, modify, maintain, or transmit electronic records shall employ procedures and controls designed to ensure the authenticity, integrity, and as appropriate, the confidentiality of electronic records from the point of their creation to the point of their receipt. Such procedures and controls shall include those identified in 11.10, as appropriate, and additional measures such as document encryption and use of appropriate digital signature standards to ensure, as necessary under the circumstances, record authenticity, integrity, and confidentiality. Is this an open system (i.e. one that uses the public internet or public email systems)? - If yes, are controls in place to ensure authenticity, integrity, and, as appropriate, the confidentiality of electronic records? No No N/A N/A Page 5 of 11

? 11.50 Signature Manifestations (a) Signed electronic records shall contain information associated with the signing that clearly indicates all of the following : (1) The printed name of the signer (1) Does the system use an electronic signature feature? If no, move to next section. Yes No application uses electronic signature feature and signature indicates clearly the printed name of the signer (2) The date and time when the signature was executed (3) The meaning (such as review, approval, responsibility, or authorship) associated with the signature (2) Does the signature have associated metadata that includes printed name of signer, date and time signature was executed, and meaning of the signature? (3) Is the information associated with the signature (printed name of the signer, the date, and purpose) controlled by the system and not the user? Yes No QM system indicates on signed records: - Printed name of the signer - Action performed by the signer (or meaning when the action is not self-explanatory) - Date and time. Information is also captured in the Audit Trail. Yes No In QM, the meaning of signature is captured on documents approvals. When signingoff other records, the meaning of signature is captured by the action performed, e.g. signing-off a QA Review process step or a Training record as trainer. (b) The items identified in paragraphs (a)(1), (a)(2), and (a)(3) of this section shall be subject to the same controls as for electronic records and shall be included as part of any human readable form of the electronic record (such as electronic display or printout) Is the information associated with the signature (printed name of the signer, the date, and purpose) displayed by the system whenever the signature is displayed or printed? Yes No The information associated with the signer (printed name of the signer, the date, and purpose) is displayed by QM whenever the signature is displayed or printed. Page 6 of 11

? 11.70 Signatures/Record Linking Electronic signatures and handwritten signatures executed to electronic records shall be linked to their respective electronic records to ensure that the signatures cannot be excised, copied, or otherwise transferred to falsify an electronic record by ordinary means. Does the system accomplish, through technical means, the linking of the records to the signature? Does the system insure, through technical means, that signatures cannot be copied and pasted? Yes Yes The system uses secure relational database references for linking of electronic records to corresponding signatures. The system s database cannot be accessed by system users. Access to the database is controlled by procedure on security. Subpart C Electronic Signatures 11.100 General requirements (a) Each electronic signature shall be unique to one individual and shall not be reused by, or reassigned to, anyone else Are electronic signatures unique to their owners? Is there an SOP precluding reuse or reassignment of electronic signatures? Yes Yes System access is controlled and limited to authorized individuals by use of a valid and unique combination of User Name and Password. User Names in QM are unique and cannot be deleted. However in most cases, QM is installed to authenticate users on the corporate network (by matching the username and password with network accounts. Then the client is responsible to ensure that reuse or reassignment of electronic signatures is not permitted. (b) Before an organization establishes, assigns, certifies, or otherwise sanctions an individual s electronic signature, or any element of such electronic signature, the organization shall verify the identity of the individual. Are identities verified prior to granting an electronic signature? Is there an SOP governing this procedure? No Yes Page 7 of 11

(c) Persons using electronic signatures shall, prior to or at the time of such use, certify to the agency that the electronic signatures in their system, used on or after August 20, 1997, are intended to be the legally binding equivalent of traditional handwritten signatures. (1) The certification shall be submitted in paper form and signed with a traditional handwritten signature, to the Office of Regional Operations (HFC-100), 5600 Fishers Lane, Rockville, MD 20857 (1) Has required notification been sent to FDA? No Yes? (2) Persons using electronic signatures shall, upon agency request, provide additional certification or testimony that a specific electronic signature is the legally binding equivalent of the signer s handwritten signature. (2) Have users signed a statement indicating that their electronic signatures are equivalent to their handwritten signatures? Yes or No (Based on Client Decision) Yes QM can be delivered with a System Access process in which case new users must sign-off a process step indicating that their electronic signatures are equivalent to their handwritten signatures in QM. 11.200 Electronic Signature Components and Controls (a) Electronic signatures that are not based upon biometrics shall : (1) Employ at least two distinct identification components such as an identification code and password. (1) Do electronic signatures employ at least two distinct identification components, where one of the components is known only to the user, such as an identification code and password? Yes No Users in QM use a Username and Password (known only to the user) combination as their electronic signature. Page 8 of 11

? (i) When an individual executes a series of signings during a single, continuous period of controlled system access, the first signing shall be executed using all electronic signature components; subsequent signings shall be executed using at least one electronic signature component that is only executable by, and designed to be used only by, the individual. (ii) When an individual executes one or more signings not performed during a single, continuous period of controlled system access, each signing shall be executed using all the electronic signature components. (2) Be used only by their genuine owners; and Is there a defined or configurable signing period within the system? If so, is only the component of the signature known only to the user required to execute a signature within the signing period? Once the signing period expires, are both components required to execute an electronic signature? (2) Are there SOPs in place to ensure that electronic signatures are not shared or otherwise accessible to others? Yes No During a session opened by a user in QM, all signing actions require the Username and Password combination. In some cases, the Username field (editable) may already be populated with the Username of the user currently logged in QM. Yes No See 11.200 (a) (i) above No Yes (3) Be administered and executed to ensure that attempted use of an individual s electronic signature by anyone other than its genuine owner requires collaboration of two or more individuals. (b) Electronic signatures based upon biometrics shall be designed to ensure that they cannot be used by anyone other than their genuine owners. (3) Are there controls within the system that prevents or detects unauthorized access? Are biometrics used for executing electronic signatures? If so, are they designed to ensure that they cannot be used by anyone other than their genuine owners? No Yes No No QM s electronic signature is not based upon biometrics. Page 9 of 11

? 11.300 Controls for Identification Codes/Passwords Persons who use electronic signatures based upon use of identification codes in combination with passwords shall employ controls to ensure their security and integrity. Such controls shall include: Note: QM uses the network password for system users. (a) Maintaining the uniqueness of each combined identification code and password, such that no two individuals have the same combination of identification code and password. Is the user identification and password combination for each user account unique? No Yes (b) Ensuring that identification code and password issuances are periodically checked, recalled, or revised (e.g. to cover such events as password aging) (c) Following loss management procedures to electronically de-authorize lost, stolen, missing, or otherwise potentially compromised tokens, cards, and other devices that bear or generate identification code or password information, and to issue temporary or permanent replacements using suitable, rigorous controls. Does the system have technical means to expire passwords periodically? If not, do SOPs exist to govern such a process? Do SOPs exist to disable user accounts that have had their security compromised? If so, do they include procedures for re-enabling the accounts, such as issuing new passwords? No Yes No Yes Page 10 of 11

? (d) Use of transaction safeguards to prevent unauthorized use of passwords and/or identification codes, and to detect and report in an immediate and urgent manner any attempts at their unauthorized use to the system security unit, and, as appropriate, to organizational management. Does the system have technical means to detect and report in an immediate and urgent manner any attempts at unauthorized use of the system If not, do SOPs exist to periodically review security logs for evidence of unauthorized attempts at accessing the system? Yes Yes system will automatically lock a user upon three (3) consecutive unsuccessful attempts to log in, and send an e-mail to the system administrator. (e) Initial and periodic testing of devices, such as tokens or cards, that bear or generate identification code or password information to ensure that they function properly and have not been altered in an unauthorized manner. All requirements are met? : Completed by: Can the system perform self-test of tokens or cards upon each use? If not, are SOPs in place to periodically require this testing? No Yes Date: Page 11 of 11