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

Similar documents
OpenLAB ELN Supporting 21 CFR Part 11 Compliance

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

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

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

Exhibitor Software and 21 CFR Part 11

Compliance Matrix for 21 CFR Part 11: Electronic Records

Integration of Agilent UV-Visible ChemStation with OpenLAB ECM

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

Adobe Sign and 21 CFR Part 11

SDA COMPLIANCE SOFTWARE For Agilent ICP-MS MassHunter Software

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

21 CFR PART 11 COMPLIANCE

TECHNICAL BULLETIN [ 1 / 13 ]

21 CFR Part 11 Module Design

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

WHITE PAPER AGILOFT COMPLIANCE WITH CFR 21 PART 11

The Impact of 21 CFR Part 11 on Product Development

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

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

Sparta Systems TrackWise Solution

Sparta Systems Stratas Solution

21 CFR Part 11 FAQ (Frequently Asked Questions)

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

Using "TiNet 2.5 Compliant SR1" software to comply with 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

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

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

Validation Checklist Appendix A WiZARD2 Secure and 21 CFR 11 Requirements

21 CFR Part 11 LIMS Requirements Electronic signatures and records

Electronic Data Processing 21 CFR Part 11

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

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

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

Technical Information

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

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

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

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

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

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

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

Cell Therapy Data Management

Using the Titrando system to comply with 21 CFR Part 11

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

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

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

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

Part 11 Compliance SOP

Using the Titrando system to comply with 21 CFR Part 11

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

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

Agilent Technologies Dissolution Workstation Software Electronic Records and Data Storage Background

21 CFR PART 11 FREQUENTLY ASKED QUESTIONS (FAQS)

Real World Examples for Part 11 Technical Controls

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

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

MySign Electronic Signature

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

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

Automation Change Management for Regulated Industries

EU Annex 11 Compliance Regulatory Conformity of eve

Virginia Commonwealth University School of Medicine Information Security Standard

Comply with Data Integrity Regulations with Chromeleon CDS Software

Statement of 21 CFR Part 11 Validation Results

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

Achieving 21 CFR Part 11 Compliance using CENTUM VP

SECURITY & PRIVACY DOCUMENTATION

eprost System Policies & Procedures

User Manual. Version 1 1/10/ of 26

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

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

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

Achieving 21 CFR Part 11 Compliance using CENTUM VP

testo Comfort Software CFR 4 Instruction manual

Data Integrity: Technical controls that demonstrate trust

21 CFR Part 11 Fundamentals

ABB Limited. Table of Content. Executive Summary

Enterprise Income Verification (EIV) System User Access Authorization Form

State of Colorado Cyber Security Policies

21 CFR Part 11 Compliance DELMIA Apriso 2018 Implementation Guide

Summary. Implementing CFR21 Part 11 with Movicon 11 Page 2

Oracle Eloqua HIPAA Advanced Data Security Add-on Cloud Service

North Carolina Health Information Exchange Authority. User Access Policy for NC HealthConnex

Learning Management System - Privacy Policy

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

Red Flags/Identity Theft Prevention Policy: Purpose

Premium HMI and FDA 21 Part 11 regulations TN0009. Version Description Date 1 First emission 10/04/2012

Security Policies and Procedures Principles and Practices

Virginia Commonwealth University School of Medicine Information Security Standard

Leveraging ALCOA+ Principles to Establish a Data Lifecycle Approach for the Validation and Remediation of Data Integrity. Bradford Allen Genentech

Complying with FDA's 21 CFR Part 11 Regulation

Table of Contents. PCI Information Security Policy

May ORION User Access Procedures

Certification Practice Statement of the Federal Reserve Banks Services Public Key Infrastructure

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

HIPAA Regulatory Compliance

Information Security Policy

Standard: Event Monitoring

Transcription:

ChromQuest 5.0 Tools to Aid in 21 CFR Part 11 Compliance Introduction Thermo Scientific, Inc. is pleased to offer the ChromQuest chromatography data system (CDS) as a solution for chromatography labs seeking to operate in a regulated environment. ChromQuest represents over 14 years of experience in the CDS market. Its use of industry standard technology such as Microsoft s COM, DCOM, ActiveX and.net, and its awareness of regulatory compliance requirements, enables ChromQuest to be a powerful CDS for deployments in regulated environments. This document is intended to provide an overview of the compliance capabilities of ChromQuest version 5.0 as they relate to 21 CFR Part 11. It is not a certificate of validation or compliance, nor a warranty of such. General Overview The final Food and Drug Administration (FDA) ruling on electronic records and electronic signatures has been in effect since August 20, 1997. While ChromQuest provides significant and extensive compliance tools to facilitate compliance, the ultimate responsibility rests with the enterprise employing the technology. Complete compliance therefore requires that the enterprise employing this functionality have the appropriate internal Standard Operating Procedures (SOP). Articles that can only be satisfied by an SOP are indicated as such in the detail below. This section will outline the top-level issues. The next section will go into some detail and it will follow the organization of the ruling. Closed system General Considerations When installed and managed in a compliant manner, ChromQuest is defined a Closed System. The ruling defines a closed system as: an environment in which system access is controlled by persons who are responsible for the content of electronic records that are on the system. 1

E-Sig enhancements In addition to the minimum Electronic Signature (e-sig) requirements specified by the FDA, ChromQuest offers some additional important enhancements: 1. Up to 5 levels of signature hierarchy. The roles are definable by the system administrator and hence can be tailored to the specific SOP requirements. 2. Reasons for a signature are definable by the system administrator; once set, they are fixed and are unalterable by users. An additional free text field is available for any supplemental comments. 3. Time-outs are definable by the administrator to ensure that only the appropriate individual is involved in the e-signature process. 4. While allowable, e-signature revocation can only be performed by the highest signatory in the hierarchy. Of course all activities are recorded in the appropriate log or audit trail. Subpart B: E-Records: Controls for Closed Systems Validated software Security and traceability 11.10a Has the system been validated in order to ensure accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records? ChromQuest has been validated with tests written to specifically evaluate accuracy, reliability and consistent performance. All data, sequences and methods have embedded audit trails that are CRC checksummed to discern invalid or altered records. 11.10b Is the system capable of generating accurate and complete copies of all required records in both human readable and electronic form suitable for inspection, review and copying by the FDA? ChromQuest maintains the integrity of all data files using a unique checksum algorithm. These files and the resulting reports are available for review and inspection. 11.10c Are the records protected to enable the accurate and ready retrieval throughout the record retention period? All records are protected in secure storage locations and are readily retrievable. 11.10d Is system access limited to authorized individuals? ChromQuest works with the Microsoft Windows Active Directory (AD) user lists to authenticate users based on their AD login name and password. The system administrator assigns rights to each function in the software on an individual or AD Group basis. 11.10e Is there a secure, computer-generated, time-stamped audit trail that independently records the date and time of operator entries and actions that create, modify, or delete electronic records? The secure, computer-generated, time-stamped audit trail is embedded with the data itself to insure long-term retention and association.

Subpart B: E-Records: Controls for Closed Systems System checks and controls 11.10e When records are changed, is previously recorded information left unchanged? All versions of the data and methods are maintained. In addition, all changes are added to the audit trail. There is no overwriting of information. 11.10e Are electronic audit trails kept for a period at least as long as their subject electronic records' and available for agency review and copying? Audit trails exist for the system and for each instrument, as well as for methods, sequences and data and report templates. The secure, computer-generated, timestamped data audit trail is embedded in the file itself to insure long-term retention and association. 11.10 (f) Are operational system checks used to enforce permitted sequencing of steps and events? 11.10(g) 11.10(h) 11.10(i) Within ChromQuest, users are stepped through sequences and events; data cannot be acquired unless parameters are within valid instrument and data processing ranges. Users are prompted with an error message when steps are performed out of sequence. Are authority checks in place 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? ChromQuest works with the Microsoft Windows Active Directory (AD) user lists to authenticate users based on their AD login name and password. The system administrator assigns rights to each function in the software on an individual or AD Group basis. Are device checks used to determine, as appropriate, the validity of the source of data or operational instruction? Integration with instruments through comprehensive automation and control provides various levels of device and validity checks depending on the instrument make and model. Do the persons who develop, maintain, or use electronic records/signature systems have the education, training, and experience to perform their assigned tasks? Records of the educational and employment history of those who specify and develop the functionality of ChromQuest are verified and kept with personnel records of their employer. The customer is responsible for ensuring that end users of ChromQuest have adequate education, training and/or experience with the system.

Subpart B: E-Records: Controls for Closed Systems 11.10(j) 11.10(k)(1) 11.10(k)(2) Have written policies been established, and adhered to, that hold individuals accountable and responsible for actions initiated under their e-signatures in order to deter record and signature falsification? It is the responsibility of the organization implementing electronic signatures to develop written policies that ensure that individuals responsible for signing documents understand that their electronic signature is as equally binding as their handwritten signature. Are there adequate controls over the distribution of, access to, and use of documentation for system operation and maintenance? While documentation is available for ChromQuest users and administrators, controls over the storage and distribution of this material are the responsibility of the end user. Are there formal revisions and change control procedures to maintain an audit trail that documents time-sequenced development and modification of systems documentation? Thermo Scientific, Inc. s ISO 9001 certified quality process includes formal written revision and change control procedures for systems documentation. Controls for Open Systems 11.30 Are there procedures and controls used to protect the authenticity, integrity and confidentiality of the electronic records from their creation point to the point of their receipt? ChromQuest is a closed system. 11.30 Are additional measures used to ensure the confidentiality of the electronic records from the point of their creation to the point of their receipt? ChromQuest is closed system.

Signature Manifestations 11.50 (a) Do the signed electronic records contain information associated with the signing that clearly indicates the following: 1. Printed name of signer, 2. Date and time that the signature was executed 3. The meaning associated with the signature? Both the machine-readable data and the human readable report contain the name, date / time and meaning. An electronic signature time-out is provided for added security. 11.50 (b) Are these items part of any human readable form of the electronic record? Both the machine-readable data and the human readable report contain the name, date / time and meaning. Signature / Record Linking 11.70 Is the electronic signature linked to its respective electronic record to ensure that the signature cannot be excised, copied or otherwise transferred to falsify an electronic record by ordinary means? Signed records have a unique checksum that prevents signatures from being excised, copied or otherwise transferred.

General Requirements 11.100 (a) Is each electronic signature unique to one individual and not reused by, or reassigned to, anyone else? Through the use of Microsoft Active Directory security, user s signatures are unique and cannot be reused or reassigned. 11.100 (b) Are the identities of the individual verified prior to the establishment, assignment, and certification or otherwise sanctioning an individual's electronic signature or any element of an electronic signature? This would be a requirement of the customer before implementing electronic signature procedures and/or assigning electronic signature privileges to an individual. 11.100 (c) Has the Company delivered its corporate electronic signature certification letter to the FDA? 11.100 (c)(1) Is it in paper form with a traditional handwritten signature? 11.100 (c)(2) Can additional certification or testimony be provided that a specific electronic signature is the legally binding equivalent of the signer's handwritten signature? It is the Company's responsibility, before a submitting electronically signed documentation to the FDA, to register their intent to use electronic signatures. In addition, training programs must be in place to ensure that users signing documents electronically understand the legal significance of their electronic signature. Electronic Signature Components and Controls 11.200 (a)(1) Does the e-signature employ at least two distinct identification components such as User ID and password? The ChromQuest electronic signature tools employ two distinct components, username (unique) and password. 11.200 (a)(1)(i) When an individual executes a series of signings during a single, continuous period of controlled system access, is the first signing executed using all the electronic signature components? When an individual signs the first of a series of documents during a single period of controlled access the user is required to enter both signature components: username and password.

Electronic Signature Components and Controls 11.200 (a)(1)(ii) When an individual executes a series of signings during a single, continuous period of controlled system access, is each subsequent signing executed using at least one electronic signature component that is only executable by, and designed to be used by, the individual? When a ChromQuest user executes a series of continuous electronic signatures (defined as signatures executed within a system administrator determined period of time) they are required to enter username, password and reason on the first signature only. Each subsequent signature requires only the user s password, which is known only to the user. 11.200 (a)(1)(ii) When an individual executes a series of signings not performed during a single, continuous period of controlled system access; does each signing executed require all signature components? When a ChromQuest user executes a series of non-continuous electronic signatures (defined as signatures executed outside of a system administrator determined period of time) they are required to enter username, password and reason on each signature. 11.200 (a)(2) Are controls in place to ensure that only their genuine owners can use the electronic signature? Through the use of Microsoft Windows Active Directory security, no two users can have the same username and password. 11.200 (a)(3) Are the electronic signatures to be administered and executed to ensure that the attempted use of an individual s electronic signature by anyone other than its genuine owner requires the collaboration of two or more individuals? ChromQuest uses the user s user name and password to initiate the electronic signature. The system can be configured such that an administrator can assign an initial password to a user for a new account or forgotten password, but the user is required to change that password on their first login. In this manner, the username / password combination is known only to the individual. Controls for Identification Codes / Passwords 11.300 (a) Are controls in place to ensure the uniqueness of each combined identification code and password maintained, such that no two individuals have the same combination of identification code and password? Through the use of Microsoft Windows Active Directory security, no two users can have the same username and password.

Controls for Identification Codes / Passwords ID control Safeguards notifications Automated notifications 11.300 (b) Are controls in place to ensure that the identification code and password issuance is periodically checked, recalled, and revised? Through the use of Microsoft Windows Active Directory security, identification codes and passwords can be periodically checked, recalled and revised. 11.300 (c) Are there loss management procedures in place to electronically disable lost, stolen, missing, or otherwise potentially compromised tokens, cards, and other devices that bear or generate identification code or password information? A ChromQuest administrator can at any time disable a user account, or issue a new password to an existing account in the event the account becomes compromised. If a ChromQuest user forgets his/her password, the system administrator can issue a new one. The user can be required to change this temporary password at their next login attempt. 11.300 (d) Are transaction safeguards in use to prevent unauthorized use of passwords and/or identification codes? ChromQuest can be configured such that only the user knows their username / password identification code. Passwords are always displayed as asterisks and are stored encrypted within the database so that even an administrator cannot see them. 11.300 (d) Are transaction safeguards in use 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? ChromQuest can be configured such that unauthorized access attempts lock out the user account and send email notification to a system administrator. 1 Federal Register, Part II, Department of Health and Human Services, FDA, 21CFR Part 11, Sect. 11.3 Definitions, Item 4, pg. 13465.