|
Sample Pages | RCGLOBAL |
| Sample pages of
Evidence Product Checklist for the FDA Document “FDA 21 CFR Part 11 - Electronic Records; Electronic Signatures; Final Rule” |
| Introduction
The process of defining what is necessary for compliance with a document such as “FDA 21 CFR Part 11 Electronic Records; Electronic Signatures; Final Rule” is sometimes confusing and laborious because the directions contained in the document may be unclear or ambiguous. This checklist was produced to aid in determining what is actually “required” by the document in the way of physical evidence of compliance. The checklist is constructed around a classification scheme of physical evidence comprised of policies, procedures, plans, records, documents, audits, and reviews. Based upon this classification scheme, this FDA document was carefully reviewed and required physical evidence required was defined. A second review of the complete list was conducted to ensure that the document’s producers did not leave out a physical piece of evidence that a “reasonable person” would expect to find. It could certainly be argued that if the document did not call it out then it is not required; however if this document were used by an enterprise to improve its software process, then it would make sense to recognize missing documents. Therefore, there are documents specified in this checklist, though not specifically called out, which are implied by “FDA 21 CFR Part 11 Electronic Records; Electronic Signatures; Final Rule”. These implied documents are designated by an asterisk (*) throughout this checklist. If a document is called out more than one time, only the first reference is stipulated. There are occasional situations in which a procedure or document is not necessarily separate and could be contained within another document. For example, the Software Detail Specification Document could be a subset of Software Design Specification. These individual items have been called out separately to ensure that the organization does not overlook any facet of physical evidence. If the organization does not require a separate document, and an item can be a subset of another document or record, then this fact should be denoted in the detail section of the checklist for that item. This should be done in the form of a statement reflecting that the information for this document may be found in section XX of Document XYZ. If the organizational requirements do not call for this physical evidence for a particular project, this should also be denoted with a statement reflecting that this physical evidence is not required and why. The reasons for the evidence not being required should be clearly presented in this statement. Further details on this step are provided in the in the Detail Steps section of the introduction. The size of these documents could vary from paragraphs to volumes depending upon the size and complexity of the software project or business requirements. This checklist is focused solely on “FDA 21 CFR Part 11 Electronic Records; Electronic Signatures; Final Rule”. It does not cover the requirements for any other standard unless so stated. FDA Document Checklist for Electronic Records and Electronic Signatures This checklist was prepared by analyzing each clause of this document for the key words that signify a:
Using the Checklist
Detail Steps
|
|
Electronic Records and Electronic Signatures; Final Rule |
|
|
|
|
|
| 11.0 General Provisions | . | . | . | . | . |
| 11.1 Scope | . | . | . | . | . |
| 11.2 Implementation | . | . | . | . | . |
| 11.3 Definitions | . | . | . | . | . |
| 11.10 Controls for Closed Systems |
|
|
|
|
|
| FDA 21 CFR Part 11
Electronic Records and Electronic Signatures; Final Rule |
RECORDS | AVAILABILITY | NOT REQUIRED RATIONALE | COMMENTS |
| 11.10 Controls for Closed Systems |
|
. | . | . |
| 11.50 Signature Manifestations |
|
. | . | . |
| 11.70 Signature/Record Linking |
|
. | . | . |
| © 2002. Software Engineering Process Technology. All rights reserved. |