Exhibitor Software and 21 CFR Part 11

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

Compliance Matrix for 21 CFR Part 11: Electronic Records

21 CFR Part 11 Module Design

TECHNICAL BULLETIN [ 1 / 13 ]

21 CFR PART 11 COMPLIANCE

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

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

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

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

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

21 CFR Part 11 FAQ (Frequently Asked Questions)

OpenLAB ELN Supporting 21 CFR Part 11 Compliance

SDA COMPLIANCE SOFTWARE For Agilent ICP-MS MassHunter Software

Integration of Agilent UV-Visible ChemStation with OpenLAB ECM

Adobe Sign and 21 CFR Part 11

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

The Impact of 21 CFR Part 11 on Product Development

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

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

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

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

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

Sparta Systems Stratas Solution

Sparta Systems TrackWise Solution

FDA 21 CFR Part 11 Compliance by Metrohm Raman

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

Electronic Data Processing 21 CFR Part 11

Sparta Systems TrackWise Digital Solution

Technical Information

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

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

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

Using the Titrando system to comply with 21 CFR Part 11

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

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

21 CFR Part 11 LIMS Requirements Electronic signatures and records

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

Cell Therapy Data Management

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

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

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

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

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

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

Using the Titrando system to comply with 21 CFR Part 11

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

Part 11 Compliance SOP

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

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

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

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

Agilent Technologies Dissolution Workstation Software Electronic Records and Data Storage Background

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

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

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

User Manual. Version 1 1/10/ of 26

21 CFR Part 11 Fundamentals

Real World Examples for Part 11 Technical Controls

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

Achieving 21 CFR Part 11 Compliance using CENTUM VP

EU Annex 11 Compliance Regulatory Conformity of eve

Automation Change Management for Regulated Industries

Summary. Implementing CFR21 Part 11 with Movicon 11 Page 2

State of Colorado Cyber Security Policies

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

Achieving 21 CFR Part 11 Compliance using CENTUM VP

TECHNICAL AND ORGANIZATIONAL DATA SECURITY MEASURES

TECHNICAL AND ORGANIZATIONAL DATA SECURITY MEASURES

21 CFR PART 11 FREQUENTLY ASKED QUESTIONS (FAQS)

Minnesota State Colleges and Universities System Procedures Chapter 5 Administration

SUBJECT: Bureau of Highway Instructional Memorandum Digitally Encrypted Electronic Signatures

testo Comfort Software CFR 4 Instruction manual

eprost System Policies & Procedures

EXCERPT. NIST Special Publication R1. Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations

SECURITY & PRIVACY DOCUMENTATION

Statement of 21 CFR Part 11 Validation Results

Electronic Signature Policy

Voting System Security as per the VVSG

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

21 CFR 11 Validation Document for ERSA. Ochsner IRB s Electronic Research Study Application

Security Policies and Procedures Principles and Practices

Learning Management System - Privacy Policy

Implementing Electronic Signature Solutions 11/10/2015

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

Red Flags/Identity Theft Prevention Policy: Purpose

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

Virginia Commonwealth University School of Medicine Information Security Standard

Standard: Event Monitoring

Disclosure text - PDS (PKI Disclosure Statement) for electronic signature and authentication certificates

Policy for Certification of Private Label Products Within the Cradle to Cradle Certified Certification Scheme. Version 1.0.

Page 1 of 15. Applicability. Compatibility EACMS PACS. Version 5. Version 3 PCA EAP. ERC NO ERC Low Impact BES. ERC Medium Impact BES

Document Title: Electronic Data Protection and Encryption Policy. Revision Date Authors Description of Changes

CERTIFICATE POLICY CIGNA PKI Certificates

NSIF APPROVED DOCUMENT. Common Applications Requirements for SONET NE Security System

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

GDPR Draft: Data Access Control and Password Policy

Website Privacy Policy

Transcription:

Exhibitor Software and 21 CFR Part 11 Subpart B Electronic Records 15 Columbia Drive Amherst, New Hampshire 03031-2334 No. 11.10 11.10(a) Controls for Closed Systems Validation of systems to ensure accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records. Exhibitor is fully validated and Validation Reference Documentation is available. Monarch Instrument is ISO 9001:2008 certified and has a Quality Management System in accordance with ISO 9001. 11.10(b) 11.10(c) 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. Protection of records to enable their accurate and ready retrieval throughout the records retention period. Log files which include logged process data and audit trail of user activity are in binary encrypted format proprietary to Monarch. Details are not published. Invalid data records are rejected by Exhibitor software and there is no facility to modify the records. DC6000 creates secure unmodifiable electronic records that are encrypted and saved in a format that is accessible only through the Exhibitor software. The system is capable of producing accurate and complete copies of records in electronic form for inspection, review and copying by the FDA. No Data is logged to PC media. Archiving and retrieval is the responsibility of the user and should be governed by the user s SOP. 11.10(d) Limiting system access to authorized individuals. System Administrator grants access privileges and maintains operator registry. 11.10(e) Use of secure, computer-generated, time-stamped audit trails to independently record the date and time of operator entries and actions that create, modify, or delete electronic records. Record changes shall not obscure previously recorded information. Such audit trail documentation shall be retained for a period at least as long as that required for the subject electronic records and shall be available for agency review and copying. Each action that could affect the integrity of the Exhibitor software and the data files is logged in an audit trail. This file is composed of data records identifying the type of action performed, the timestamp of this action, the user name associated with this action, and additional information required to understand the action taken. There is no mechanism in place to alter records. Archiving and retrieval is the responsibility of the user and should be governed by the user s SOP. 11.10(f) Use of operational system checks to enforce permitted sequencing of steps and events, as appropriate. The audit trail is available for review and copying by the FDA. Not Applicable 1

No. 11.10 11.10(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. Exhibitor software requires unique individual ID and password combination for access and operation. A System Administrator grants access privileges and maintains operator registry. The System Administrator creates a new account and assigns passwords and user privileges. Passwords expire as set by the Administrator and System Administrator can disable user accounts. Administrator can disable a user s account automatically after a preset number of consecutive login failures. 11.10(h) 11.10(i) 11.10(j) 11.10(k)(1) 11.10(k)(2) Use of device (e.g., terminal) checks to determine, as appropriate, the validity of the source of data input or operational instruction. Determination that persons who develop, maintain, or use electronic record/electronic signature systems have the education, training, and experience to perform their assigned tasks. 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. Use of appropriate controls over systems documentation including: Adequate controls over the distribution of, access to, and use of documentation for system operation and maintenance. Use of appropriate controls over systems documentation including: Revision and change control procedures to maintain an audit trail that documents time-sequenced development and modification of systems documentation. Whenever an action occurs that requires the user s ID/password combination identification, the user name associated with that ID/password combination and a date and time stamp are written to the secure audit file along with a description of the action. No System errors and input channel status are alarmed and logged automatically. Various methods to ensure a valid format of operator entered data are available. This is a shared responsibility. Monarch Instrument maintains a Quality System based on ISO 9001 certification and will provide, on an ongoing basis, relevant revision and change information to the user. Implementation of changes and maintenance of an audit trail that documents time-sequenced development and modification of systems documentation is the responsibility of the user. 2

Subpart B Electronic Records No. 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. 11.50(a) Signature manifestation Signed electronic records shall contain information associated with the signing that clearly indicates all of the following: (1) The printed name of the signer; (2) The date and time when the signature was executed; and (3) The meaning (such as review, approval, responsibility, or authorship) associated with the signature. 11.50(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) 11.70 Signature/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. Exhibitor software is targeted for use in closed Systems. The Systems Administrator can force all actions to require the use of a unique combination ID/Password (signature) when using the Exhibitor software. Signed records contain printed name (ID), date and time, meaning. Meaning includes signed / authorized plus an operator entered note plus automatically generated action type (e.g. start or stop recording, source of data). Name (ID), timestamp and meaning are all embedded in the binary format history file. Signature manifestation is embedded in the binary format audit file. The appropriate individual(s) can apply either handwritten or an electronic signature generated by means of Exhibitor software for review and approval of records. 3

Subpart C Electronic Signatures No. 11.100(a) 11.100(b) 11.100(c) (a) Each electronic signature shall be unique to one individual and shall not be reused by, or reassigned to, anyone else. (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. (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. (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. Exhibitor requires unique individual ID and password combination for access and operation. The System Administrator creates an account and assigns a password. 4

Subpart C Electronic Signatures No. 11.200 11.200(a) 11.200(a)(1) 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. (i) (ii) 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. 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 of the electronic signature The System Administrator can set a login timer for user identification. The login timer allows users, after initial identification, to enter only their password if user identification is within the preset time limit. When this option is enabled, the login timer can be set from 1 to 30 minutes. Should the time expire, both user name and password will be required to log back into the system. components. 11.200(a)(2) (2) Be used only by their genuine owners; and Users can change their own passwords and no read access to passwords is provided. It is also possible to have logins time out after a set period of inactivity; to limit the number of login retries before an account is disabled and to force password expiry after a preset number of days. Passwords need to be a minimum length of 5 characters. 11.200(a)(3) 11.200(b) (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. Users can change their own passwords and no read access to passwords is provided. So, unless one user tells another their password, it is impossible to commit fraud without an audit trail of that fraud being left. Not Applicable 5

Subpart C Electronic Signatures No. 11.300 11.300 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: 11.300(a) (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. 11.300(b) 11.300(c) 11.300(d) 11.300(e) (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 deauthorize 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. (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. (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. A System Administrator grants access privileges and maintains operator registry. Exhibitor software requires unique individual ID and password combination for access and operation. The system requires a minimum password length of 5 characters. It is possible to force password expiry on a preset date. If a user leaves, their account can be deleted. Procedural - Compromised accounts can be disabled. On loss of password, the Administrator may set a new password for an account. It is possible to have logins time out after a set period of inactivity; to limit the number of login retries before an account is disabled; and to force account expiry on a preset date. Not Applicable AJW 10/02/07 MLK 01/15/13 6