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

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

Implementation of 21CFR11 Features in Micromeritics Software Software ID

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

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

FILEHOLD DOCUMENT MANAGEMENT SYSTEM 21 CFR PART 11 COMPLIANCE WHITE PAPER

21 CFR Part 11 White Paper

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

rsdm and 21 CFR Part 11

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

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

Oracle WebCenter Content

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

A ChemoMetec A/S White Paper September 2013

SolidWorks Enterprise PDM and FDA 21CFR Part 11

Full Compliance Contents

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

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

DeltaV Capabilities for Electronic Records Management

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

How To Control A Record System

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

AutoSave. Achieving Part 11 Compliance. A White Paper

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

21 CFR Part 11 Checklist

Intland s Medical Template

DeltaV Capabilities for Electronic Records Management

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

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

21 CFR Part 11 Compliance Using STATISTICA

21 CFR Part 11 Electronic Records & Signatures

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

Empower TM 2 Software

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

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

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

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

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

Declaration of Conformity 21 CFR Part 11 SIMATIC WinCC flexible 2007

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.

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

Electronic Document and Record Compliance for the Life Sciences

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

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

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

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

Achieving 21 CFR Part 11 Compliance with Appian

Life sciences solutions compliant with FDA 21 CFR Part 11

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. Maintenance of Electronic Records

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

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

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

21 CFR Part 11 LIMS Requirements Electronic signatures and records

CoSign for 21CFR Part 11 Compliance

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

TIBCO Spotfire and S+ Product Family

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

Supplement to the Guidance for Electronic Data Capture in Clinical Trials

Guidance for Industry COMPUTERIZED SYSTEMS USED IN CLINICAL TRIALS

January 30, 2014 Mortgagee Letter

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

Manual 074 Electronic Records and Electronic Signatures 1. Purpose

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

Guidance for Industry Computerized Systems Used in Clinical Investigations

5 FAM 140 ACCEPTABILITY AND USE OF ELECTRONIC SIGNATURES

Guidance for Industry

Guidance for Industry

LabChip GX/GXII with LabChip GxP Software

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

REGULATIONS COMPLIANCE ASSESSMENT

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

Rackspace Archiving Compliance Overview

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

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

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

FDA CFR PART 11 ELECTRONIC RECORDS, ELECTRONIC SIGNATURES

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

Issues in Information Security and Verifiability for Biomedical Technology Companies

REVENUE REGULATIONS NO issued on December 29, 2009 defines the requirements, obligations and responsibilities imposed on taxpayers for the

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

OLEY VALLEY SCHOOL DISTRICT

ELECTRONIC SIGNATURE REQUIREMENTS FOR LENDERS

Neutralus Certification Practices Statement

Minnesota State Colleges and Universities System Guideline Chapter 5 Administration

Minnesota State Colleges and Universities System Procedures Chapter 5 Administration Procedures associated with Board Policy 5.22

INTRODUCTION. This book offers a systematic, ten-step approach, from the decision to validate to

Dissecting Electronic Signatures for the Life Sciences

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

SUBJECT: SECURITY OF ELECTRONIC MEDICAL RECORDS COMPLIANCE WITH THE HEALTH INSURANCE PORTABILITY AND ACCOUNTABILITY ACT OF 1996 (HIPAA)

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

Transcription:

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

SEC. 11.2 IMPLEMENTATION. (a) For records required to be maintained but not submitted to the agency, persons may use electronic records in lieu of paper records or electronic signatures in lieu of traditional signatures, in whole or in part, provided that the requirements of this part are met. (b) For records submitted to the agency, persons may use electronic records in lieu of paper records or electronic signatures in lieu of traditional signatures, in whole or in part, provided that: (1) The requirements of this part are met; and (2) The document or parts of a document to be submitted have been identified in public docket No. 92S-0251 as being the type of submission the agency accepts in electronic form. This docket will identify specifically what types of documents or parts of documents are acceptable for submission in electronic form without paper records and the agency receiving unit(s) (e.g., specific center, office, division, branch) to which such submissions may be made. Documents to agency receiving unit(s) not specified in the public docket will not be considered as official if they are submitted in electronic form; paper forms of such documents will be considered as official and must accompany any electronic records. Persons are expected to consult with the intended agency receiving unit for details on how (e.g., method of transmission, media, file formats, and technical protocols) and whether to proceed with the electronic submission. 2 21 CFR Part 11 Compliance PLA 2.1 21 CFR PART 11 ELECTRONIC RECORDS, ELECTRONIC SIGNATURES COMPLIANCE OF PLA 2.1 This document describes the compliance of Stegmann Systems software package PLA 2.1 with the FDA regulation 21 CFR Part 11 Electronic Records; Electronic Signatures. The document is divided into three parts that are provided by the original document. The first part (Subpart A General Provisions) is the only part which remains not commented. The following chapters contain the current text of the 21 CFR Part 11 rule along with a corresponding description or comment on how PLA 2.1 meets the appropriate specifications in the regulation. PLA 2.1 is a 21 CFR part 11 compliant software. However to create a 21 CFR part 11 solution with PLA 2.1, several regulations on the customer side need to be defined. SUBPART A--GENERAL PROVISIONS SEC. 11.1 SCOPE. (a) The regulations in this part set forth the criteria under which the agency considers electronic records, electronic signatures, and handwritten signatures executed to electronic records to be trustworthy, reliable, and generally equivalent to paper records and handwritten signatures executed on paper. (b) This part applies to records in electronic form that are created, modified, maintained, archived, retrieved, or transmitted, under any records requirements set forth in agency regulations. This part also applies to electronic records submitted to the agency under requirements of the Federal Food, Drug, and Cosmetic Act and the Public Health Service Act, even if such records are not specifically identified in agency regulations. However, this part does not apply to paper records that are, or have been, transmitted by electronic means. (c) Where electronic signatures and their associated electronic records meet the requirements of this part, the agency will consider the electronic signatures to be equivalent to full handwritten signatures, initials, and other general signings as required by agency regulations, unless specifically excepted by regulation(s) effective on or after (d) Electronic records that meet the requirements of this part may be used in lieu of paper records, in accordance with Sec. 11.2, unless paper records are specifically required.(e) Computer systems (including hardware and software), controls, and attendant documentation maintained under this part shall be readily available for, and subject to, FDA inspection.

SEC. 11.3 DEFINITIONS. (a) The definitions and interpretations of terms contained in section 201 of the act apply to those terms when used in this part. (b) The following definitions of terms also apply to this part: (1) Act means the Federal Food, Drug, and Cosmetic Act (secs. 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. (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. 3

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. Beside the internal development documentation, the optional Validation Package lists more than 2500 pages of printed reference material and procedures (IQ, OQ and PQ) to ensure accuracy and reliability. The ability to discern invalid or altered records is realized by the internal PKI of PLA. (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 PLA is able to generate complete copies of records in both human readable and electronic form. The software is able to create a complete database backup (electronic form) or to produce reports that contain the whole information in a human readable form (PDF documents). of the electronic records. (c) Protection of records to enable their accurate and ready retrieval throughout the records retention period. PLA has an integrated backup and restore feature for a complete database backup. Alternatively the customer can save the PLA database file on a network attached drive and backup the file with external tools (backup software). PLA is able to restore the database without compromising the data integrity, which is secured by the internal PKI of PLA. (d) Limiting system access to authorized individuals. PLA has an integrated user account management and controls the access to the PLA system by a unique user ID and a secret password. User groups are implemented to allow a detailed rights management. (e) Use of secure, computer-generated, timestamped 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. PLA provides a secure, computer generated and time-stamped audit trail. All required information and features of the audit trail are supported by PLA. The audit trail information is saved within the PLA database and is therefore retained with the electronic records. 4

(f) Use of operational system checks to enforce permitted sequencing of steps and events, as appropriate. PLA does not allow altering the sequence of the analysis steps; therefore this aspect is fulfilled. (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. With the integrated user account management the access to the PLA system is controlled and only authorized individuals have access to the system.pla ensures the access to the PLA database through its internal PKI. (h) Use of device (e.g., terminal) checks to determine, as appropriate, the validity of the source of data input or operational instruction. Our optional Import Modules, which are intended for the easy and secure transfer of external data into the PLA system, carry out strict checks on the raw data format. If the raw data that should be imported cannot be identified securely, the import process is being stopped. (i) Determination that persons who develop, maintain, or use electronic record/electronic signature The implementation of such rules is the administrative 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 The establishment of such policies is the administrative 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. The implementation of these controls is the administrative 5

SEC. 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 As defined in Sec. 11.3 paragraph (4) and (9) PLA is a closed system and this section does not apply. For information on closed systems, see Sec. 11.10. 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. SEC. 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; (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. PLA provides electronic signatures that clearly indicate the username, timestamp and the meaning of the signature. In order to sign an electronic record the user has to enter his password. (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). SEC. 11.70 SIGNATURE/RECORD LINKING. If an electronic signature is applied to an electronic record this information will be printed out with the resulting report in a human readable format. 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. The electronic signature that is applied to an electronic record is stored as a secured ML document representing the record and is prevented from modification. 6

SUBPART C--ELECTRONIC SIGNATURES SEC. 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. PLA authenticates individuals by a unique username and a secret password. If the confidentiality of the password is ensured, the authentication of individuals complies with the regulation. (b) Before an organization establishes, assigns, certifies, or otherwise sanctions an individual s electronic The verification of an individual s identity is the administrative 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. The implementation of such regulations is the administrative 7

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. The PLA user authentication is based on both - an identification code and a password. During the login process both identification components (username and password) are required. For all subsequent operations only one component - the password - is required. (2) Be used only by their genuine owners; and If the confidentiality of the password is ensured, the authentication of individuals complies with the regulation. (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. Each signature in PLA is designed to be executed by its genuine owner only. For any administrative purposes the collaboration of two individuals (PLA administrator and genuine owner) is required. (b) Electronic signatures based upon biometrics shall be designed to ensure that they cannot be used by anyone other than their genuine owners. PLA does not support electronic signatures based on biometry, therefore this point is not applicable. 8

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 It is not possible to generate two PLA user accounts with identical usernames. 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). PLA supports detailed password aging and complexity rules. The implementation and maintenance of such schedules is the administrative responsibility of the customer. (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, PLA does not support any devices for the storage and/or generation of identification codes or passwords. All PLA accounts (usernames and respective passwords) can de deauthorized by the PLA system administrator. rigorous controls. (d) Use of transaction safeguards to prevent unauthorized use of passwords and/or identification All system activities including any security violations are logged within the system audit trail. 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. PLA does not use any devices for the storage and/ or generation of identification codes or passwords. Stegmann Systems GmbH Raiffeisenstr. 2 // C1, C2 63110 Rodgau, Germany Fon: + 49 6106 77010-0 Fax: + 49 6106 77010-29 info@stegmannsystems.com www.bioassay.de