Implementation of 21CFR11 Features in Micromeritics Software Software ID



Similar documents
Self-Assessment of eresearch Compliance with 21 CFR Part 11, Electronic Record; Electronic Signatures

21 CFR PART 11 ELECTRONIC RECORDS, ELECTRONIC SIGNATURES CFR Part 11 Compliance PLA 2.1

InfinityQS SPC Quality System & FDA s 21 CFR Part 11 Requirements

Electronic records and electronic signatures in the regulated environment of the pharmaceutical and medical device industries

Compliance Matrix for 21 CFR Part 11: Electronic Records

The Impact of 21 CFR Part 11 on Product Development

FILEHOLD DOCUMENT MANAGEMENT SYSTEM 21 CFR PART 11 COMPLIANCE WHITE PAPER

21 CFR Part 11 Implementation Spectrum ES

POLICY ISSUES IN E-COMMERCE APPLICATIONS: ELECTRONIC RECORD AND SIGNATURE COMPLIANCE FDA 21 CFR 11 ALPHATRUST PRONTO ENTERPRISE PLATFORM

FDA Title 21 CFR Part 11:Electronic Records; Electronic Signatures; Final Rule (1997)

A ChemoMetec A/S White Paper September 2013

SolidWorks Enterprise PDM and FDA 21CFR Part 11

Oracle WebCenter Content

InfoCenter Suite and the FDA s 21 CFR part 11 Electronic Records; Electronic Signatures

rsdm and 21 CFR Part 11

21 CFR Part 11 White Paper

Enabling SharePoint for 21 CFR Part 11 Compliance - Electronic Signature Use Case

Implement best practices by using FileMaker Pro 7 as the backbone of your 21 CFR 11 compliant system.

How To Control A Record System

Intland s Medical Template

FDA 21 CFR Part 11 Electronic records and signatures solutions for the Life Sciences Industry

Tools to Aid in 21 CFR Part 11 Compliance with EZChrom Elite Chromatography Data System. White Paper. By Frank Tontala

Assessment of Vaisala Veriteq vlog Validation System Compliance to 21 CFR Part 11 Requirements

Full Compliance Contents

Agilent MicroLab Software with Spectroscopy Configuration Manager and Spectroscopy Database Administrator (SCM/SDA)

21 CFR Part 11 Electronic Records & Signatures

DeltaV Capabilities for Electronic Records Management

AutoSave. Achieving Part 11 Compliance. A White Paper

Implementing CitectSCADA to meet the requirements of FDA 21 CFR Part 11

21 CFR Part 11 Checklist

Software Manual Part IV: FDA 21 CFR part 11. Version 2.20

21 CFR Part 11 Compliance Using STATISTICA

Empower TM 2 Software

DeltaV Capabilities for Electronic Records Management

Meeting the FDA s Requirements for Electronic Records and Electronic Signatures (21 CFR Part 11)

21 CFR Part 11 Deployment Guide for Wonderware System Platform 3.1, InTouch 10.1 and Historian 9.0

Compliance Response Edition 07/2009. SIMATIC WinCC V7.0 Compliance Response Electronic Records / Electronic Signatures. simatic wincc DOKUMENTATION

ScreenMaster RVG200 Paperless recorder FDA-approved record keeping. Measurement made easy

Compliance in the BioPharma Industry. White Paper v1.0

Implementing Title 21 CFR Part 11 (Electronic Records ; Electronic Signatures) in Manufacturing Presented by: Steve Malyszko, P.E.

Using the Thermo Scientific Dionex Chromeleon 7 Chromatography Data System (CDS) to Comply with 21 CFR Part 11. Compliance Guide

Declaration of Conformity 21 CFR Part 11 SIMATIC WinCC flexible 2007

For technical assistance, please contact: Thermo Nicolet Corporation 5225 Verona Road Madison WI

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

Software. For the 21 CFR Part 11 Environment. The Science and Technology of Small Particles

Nova Southeastern University Standard Operating Procedure for GCP. Title: Electronic Source Documents for Clinical Research Study Version # 1

Compliance Response SIMATIC SIMATIC PCS 7 V8.1. Electronic Records / Electronic Signatures (ERES) Edition 03/2015. Answers for industry.

Thermal Analysis. Subpart A General Provisions 11.1 Scope Implementation Definitions.

Guidance for Industry. 21 CFR Part 11; Electronic. Records; Electronic Signatures. Time Stamps

Electronic Document and Record Compliance for the Life Sciences

Waters Empower 2 Software Seamlessly Manages Regulated Data to Aid in 21 CFR Part 11 Compliance

Achieving 21 CFR Part 11 Compliance with Appian

Data Management PACT Workshop: Design & Operation of GMP Cell Therapy Facilities April 10 th -11 th, 2007

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

Waters Empower Software Seamlessly Manages Regulated Data to Aid in 21 CFR Part 11 Compliance

Guidance for Industry. 21 CFR Part 11; Electronic Records; Electronic Signatures. Electronic Copies of Electronic Records

Electronic Records and Signatures: Compliance with Title 21 CFR Part 11 Requirements

Considerations for validating SDS Software v2.x Enterprise Edition for the 7900HT Fast Real-Time PCR System per the GAMP 5 guide

Life sciences solutions compliant with FDA 21 CFR Part 11

Guidance for Industry. 21 CFR Part 11; Electronic Records; Electronic Signatures. Maintenance of Electronic Records

Good Electronic Records Management (GERM) Using IBM Rational ClearCase and IBM Rational ClearQuest

Guidance for Industry

Sympatec GmbH System-Partikel-Technik WINDOX 4. Electronic Records/ Electronic Signatures Compliance Assessment Worksheet for 21 CFR Part 11

Guidance for Industry COMPUTERIZED SYSTEMS USED IN CLINICAL TRIALS

Guidance for Industry

TIBCO Spotfire and S+ Product Family

THE ROLE OF WATERS NUGENESIS SDMS IN 21 CFR PART 11 COMPLIANCE

Supplement to the Guidance for Electronic Data Capture in Clinical Trials

CoSign for 21CFR Part 11 Compliance

SIMATIC SIMATIC PCS 7 V8.0. Electronic Records / Electronic Signatures. Compliance Response. Answers for industry.

January 30, 2014 Mortgagee Letter

Quality Manual # QS MD Logistics, Inc. (Signed copy available upon request) Prepared by Robert Grange, Director Quality

federal register Department of Health and Human Services Part II Thursday March 20, 1997 Food and Drug Administration

Manual 074 Electronic Records and Electronic Signatures 1. Purpose

21 CFR Part 11 LIMS Requirements Electronic signatures and records

A unique biometrics based identifier, such as a fingerprint, voice print, or a retinal scan; or

FDA CFR PART 11 ELECTRONIC RECORDS, ELECTRONIC SIGNATURES

Guidance for Industry Computerized Systems Used in Clinical Investigations

REGULATIONS COMPLIANCE ASSESSMENT

Alfresco CoSign. A White Paper from Zaizi Limited. March 2013

Rackspace Archiving Compliance Overview

Issues in Information Security and Verifiability for Biomedical Technology Companies

Comparison of FDA s Part 11 and the EU s Annex 11

Eclipsys Sunrise Clinical Manager Enterprise Electronic Medical Record (SCM) and Title 21 Code of Federal Regulations Part 11 (21CFR11)

RULES OF TENNESSEE DEPARTMENT OF ENVIRONEMENT AND CONSERVATION CHAPTER ELECTRONIC REPORTING TABLE OF CONTENTS

5 FAM 140 ACCEPTABILITY AND USE OF ELECTRONIC SIGNATURES

Guidance for Industry Part 11, Electronic Records; Electronic Signatures Scope and Application

ILLINOIS GAMING BOARD MINIMUM INTERNAL CONTROL STANDARDS SECTION A - GENERAL AND ADMINISTRATIVE TABLE OF CONTENTS

Electronic Signature Assurance & the Digital Chain-of-Evidence

ELECTRONIC SIGNATURE REQUIREMENTS FOR LENDERS

OLEY VALLEY SCHOOL DISTRICT

Electronic Signature, Attestation, and Authorship

Department of Veterans Affairs VA DIRECTIVE 6510 VA IDENTITY AND ACCESS MANAGEMENT

LabChip GX/GXII with LabChip GxP Software

Auditing Chromatographic Electronic Data. Jennifer Bravo, M.S. QA Manager Agilux Laboratories

The Infrastructure Audit Trail and Part 11

Excel Spreadsheets and FDA Device Regulations

National Information Management Conference and Exposition Thursday, April 23, 2009

U.S. FDA Title 21 CFR Part 11 Compliance Assessment of SAP Records Management

Electronic Laboratory Notebook on Web2py Framework

Transcription:

Implementation of 21CFR11 Features in Micromeritics Software Software ID PART 11 ELECTRONIC RECORDS; ELECTRONIC SIGNATURES Subpart A General Provisions Sec. 11.1 Scope. 11.2 Implementation. 11.3 Definitions. Subpart B Electronic Records 11.10 Controls for closed systems. 11.30 Controls for open systems. 11.50 Signature manifestations. 11.70 Signature/record linking. Subpart C Electronic Signatures 11.100 General requirements. 11.200 Electronic signature components and controls. 11.300 Controls for identification codes/passwords. Subpart A General Provisions 21CFR11 Requirements of 21CFR11 Method of Implementation in Micromeritics Software Section Number and Title. Sec. 11.3 The following definitions of terms also apply to this part: Definitions (1) Act means the Federal Food, Drug, and Cosmetic Act (secs. Not applicable to MIC software product. 201-903 (21 U.S.C. 321-393)).(2) Agency means the Food and Drug Administration. (3) Biometrics means a method of verifying an individual's identity based on measurement of the individual's physical feature(s) or repeatable action(s) where those features and/or actions are both unique to that individual and measurable. (4) Closed system means an environment in which system access is controlled by persons who are responsible for the content of electronic records that are on the system. Not implemented in MIC software product; may be implemented at operating system level. MIC software is designed to be used in a closed system.

(5) Digital signature means an electronic signature based upon cryptographic methods of originator authentication, computed by using a set of rules and a set of parameters such that the identity of the signer and the integrity of the data can be verified. (6) Electronic record means any combination of text, graphics, data, audio, pictorial, or other information representation in digital form that is created, modified, maintained, archived, retrieved, or distributed by a computer system. (7) Electronic signature means a computer data compilation of any symbol or series of symbols executed, adopted, or authorized by an individual to be the legally binding equivalent of the individual's handwritten signature. (8) Handwritten signature means the scripted name or legal mark of an individual handwritten by that individual and executed or adopted with the present intention to authenticate a writing in a permanent form. The act of signing with a writing or marking instrument such as a pen or stylus is preserved. The scripted name or legal mark, while conventionally applied to paper, may also be applied to other devices that capture the name or mark. (9) Open system means an environment in which system access is not controlled by persons who are responsible for the content of electronic records that are on the system. Not implemented by MIC software. May be implemented at operating system level. MIC software generates forms of electronic records:.smp files: analysis data.dat files:.rpt files:.. Implemented only in the respect that printed and displayed records, and archived electronic records have associated with them the full name identity of the person who generated the data. See Subpart C for details. Not applicable to MIC software. The MIC software can be used in an open system.

Subpart B Electronic Records Sec. 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: (a) Validation of systems to ensure accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records. MIC 21CFR11 software provides control and security of electronic records while they are resident in the instrument system. However, it is strongly suggested that these records not be stored on the instrument system, but stored in a more secure environment such as a network, or relegated to the control of an external data management system such as NuGenesis. MIC offers supporting information with which to perform validation. (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. (c) Protection of records to enable their accurate and ready retrieval throughout the records retention period. (d) Limiting system access to authorized individuals. (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. MIC s 21CFR11 software provides the capability to product records of analyses (setup parameters, analysis conditions, experimental data) and audit trails in human-readable form on screen or as hard copies. These reports may be embodied, for example, in an Acrobat.pdf file, which also represents a humanreadable copy in Portable Data Format. Records are protected from unauthorized access while on the instrument system computer, however it is strongly suggested that these records be offloaded to a more secure, central environment such as a system network or data management system. Access is limited to the MIC instrument software to those individuals who have been assigned logons and passwords. Further security may be implemented at the operating system level to restrict use of the computer on which the instrument system software is executed. A level of authority can be assigned to the logon/password combination so that once logged on to the MIC instrument system, only certain operations can be achieved. An audit trail having attributes as described in 21CFR11 Subpart B, Section 11.10 (e) is maintained.

(f) Use of operational system checks to enforce permitted sequencing of steps and events, as appropriate. (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. (h) Use of device (e.g., terminal) checks to determine, as appropriate, the validity of the source of data input or operational instruction. Two levels of control are provided in the MIC 21CFR11 software to assure that only authorized individuals can use the system. The first, a unique logon/password combination limits access to the program. Second, a level of authority is assigned by the system administrator to each logon/password, which limits the user to a certain range of operations within the software. (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. (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. (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. (2) Revision and change control procedures to maintain an audit trail that documents time-sequenced development and modification of systems documentation.

Sec.11.30 Controls for open systems. Sec. 11.50 Signature manifestations. 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 Sec. 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. (a) Signed electronic records shall contain information associated with the signing that clearly indicates all of the following: The printed name of the signer; The date and time when the signature was executed; and The meaning (such as review, approval, responsibility, or authorship) associated with the signature. 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). Sec. 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.

Subpart C Electronic Signatures Sec. 11.100 (a) Each electronic signature shall be unique to one individual General and shall not be reused by, or reassigned to, anyone else. requirements. (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. Sec. 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. (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 of the electronic signature components. (2) Be used only by their genuine owners; and (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 owner Sec. 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: (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. (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. Note that the FDA has stated that the list of system controls is not intended to be all inclusive of what may be needed for a given electronic records system, and that some controls may not be necessary in all types of systems. The wording is intended to clarify which controls are generally applicable and which are germane to certain types of systems depending upon their intended use. For example, operational checks to enforce permitted sequencing of events would not be appropriate to systems in which proper sequencing was not relevant to the events being recorded. Examples of system controls that would be applicable in all cases include validation and protection of records to ensure that records remain accurate and retrievable throughout their retention period.