Aspyra, LLC’s CyberLAB® version 7.3.1 Laboratory Information System software has been verified and validated to provide the necessary capability that end users can implement policies, procedures and processes that comply with the requirements of 21 CFR, Part 11 as detailed below:
Sec 11.10 Closed System Checklist
| Sec 11.10 (a) | Validation of systems to ensure accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records. | |
| Sec 11.10 (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 of the electronic records. | |
| User's responsibility (System is capable) | Sec 11.10 (c) | Protection of records to enable their accurate and ready retrieval throughout the records retention period. |
| User's responsibility (System is capable) | Sec 11.10 (d) | Limiting system access to authorized individuals. |
| Sec 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. | |
| User's responsibility (System is capable) | Sec 11.10 (f) | Use of operational system checks to enforce permitted sequencing of steps and events, as appropriate. |
| User's responsibility (System is capable) | Sec 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. |
| User's responsibility (Not Applicable) | Sec 11.10 (h) | Use of device (e.g., terminal) checks to determine, as appropriate, the validity of the source of data input or operational instruction. |
| Sec 11.10 (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. | |
| User's responsibility (Not Applicable) | Sec 11.10 (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. |
| User's responsibility (Paperwork used to document) | Sec 11.10 (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 Opened System Checklist
| User's responsibility (Not applicable) | Sec. 11.30 | 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. |
Sec. 11.50 Signature manifestations.
| Sec. 11.50 (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. |
|
| Sec. 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). |
Sec. 11.70 Signature/record linking.
| Tech. ID | Sec. 11.70 | 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 General requirements.
| User's responsibility (System is capable) | Sec. 11.100 (a) | Each electronic signature shall be unique to one individual and shall not be reused by, or reassigned to, anyone else. |
| User's responsibility | Sec. 11.100 (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. |
| User's responsibility | Sec. 11.100 (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.
| Sec. 11.200 (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. |
|
| Not applicable | Sec. 11.200 (b) | (b) Electronic signatures based upon biometrics shall be designed to ensure that they cannot be used by anyone other than their genuine owners. |
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:
| User's responsibility (System is capable) | Sec. 11.300 (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. |
| User's responsibility | Sec. 11.300 (b) | Ensuring that identification code and password issuances are periodically checked, recalled, or revised (e.g., to cover such events as password aging). |
| User's responsibility | Sec. 11.300 (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. |
| User's responsibility | Sec. 11.300 (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. |
| User's responsibility | Sec. 11.300 (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. |
Ready To Learn More?
If your organization is interested in learning more, or would like to see a demo of our Lab or imaging solutions, please contact us today or call