Study guide

18.3 Compliance in Clinical Trial Informatics

Certified Clinical Research Coordinator CCRC

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Scientific Concepts and Research Design

1.1 Protocol Elements 1.2 Study Design and Objectives 1.3 Study Endpoints and Biostatistics

2 Chapter 2: Ethical Principles and Guidelines

2.1 Ethical Principles (Declaration of Helsinki, Belmont Report) 2.2 Informed Consent Process and Documentation 2.3 Vulnerable Populations and Assent

3 Chapter 3: IRB/IEC Oversight and Participant Safety

3.1 IRB/IEC Functions and Oversight 3.2 Adverse Event Classification and Reporting 3.3 Safety Monitoring and Safety Reporting

4 Chapter 4: Participant Rights and Ethics

4.1 Participant Rights and Confidentiality (HIPAA/GDPR) 4.2 Conflicts of Interest 4.3 Ethical Scenarios in Clinical Trials

5 Chapter 5: Product Development and Regulatory Framework

5.1 Drug and Device Development Phases 5.2 U.S. and International Regulatory Frameworks 5.3 Investigational Product Investigator's Brochure (IB)

6 Chapter 6: Investigational Product Accountability

6.1 Investigational Product Labeling and Storage 6.2 Investigational Product Receipt, Dispensing, and Accountability 6.3 Investigational Product Return and Destruction

7 Chapter 7: Regulatory Submissions and Actions

7.1 Regulatory Submissions (IND, NDA, IDE, PMA) 7.2 Regulatory Actions and Compliance 7.3 Pharmacokinetics and Pharmacodynamics in Product Development

8 Chapter 8: Clinical Trial Operations and GCP Principles

8.1 Introduction to ICH E6 GCP Principles (including R3 updates) 8.2 Investigator Responsibilities under GCP 8.3 Sponsor Responsibilities and Oversight

9 Chapter 9: Essential Documents and Site Qualification

9.1 Essential Documents (Pre-study, During, Post-study) 9.2 Site Selection and Qualification 9.3 Quality Management and Standard Operating Procedures (SOPs)

10 Chapter 10: Protocol Deviations and Amendments

10.1 Protocol Adherence and Compliance 10.2 Protocol Deviations and Violations 10.3 Protocol Amendments and Version Control

11 Chapter 11: Monitoring Visits and Audits

11.1 Monitoring Preparation and Visit Types 11.2 Monitoring Visits (SIV, IMV, COV) 11.3 Regulatory Inspections and Site Audits

12 Chapter 12: Study and Site Management - Startup

12.1 Site Startup Operations 12.2 Site Budget and Contract Management 12.3 Site Staffing, Training, and Documentation

13 Chapter 13: Enrollment and Recruitment

13.1 Enrollment Management and Strategies 13.2 Participant Recruitment and Retention 13.3 Participant Compensation and Ethics

14 Chapter 14: Daily Trial Coordination

14.1 Visit Scheduling and Logistics 14.2 Equipment Maintenance and Calibration 14.3 Specimen Handling and Shipping (IATA/dangerous goods)

15 Chapter 15: Quality Improvement and Site Closeout

15.1 Participant Safety Management 15.2 Quality Improvement and Site Audits Preparation 15.3 Study and Site Closeout Procedures

16 Chapter 16: Source Documentation and Case Report Forms

16.1 Source Documentation Standards (ALCOA-C) 16.2 Case Report Forms and eCRF Completion 16.3 Electronic Data Capture (EDC) Systems

17 Chapter 17: Data Management and Queries

17.1 Data Management Processes 17.2 Data Queries and Discrepancy Resolution 17.3 Data Correction and Audit Trails

18 Chapter 18: Data Privacy and Records Retention

18.1 Data Privacy and Confidentiality 18.2 Records Retention and Archiving 18.3 Compliance in Clinical Trial Informatics

18.3 Compliance in Clinical Trial Informatics

Key Takeaways Explain This Topic AI

21 CFR Part 11 establishes the FDA's criteria for accepting electronic records and electronic signatures as equivalent to paper records and handwritten signatures.

ALCOA-C is the guiding principle for data integrity: Attributable, Legible, Contemporaneous, Original, Accurate, and Complete.

Audit trails are non-editable, computer-generated, time-stamped records that track all data entries and changes within an electronic system.

Electronic Data Capture (EDC) systems must undergo strict computer system validation before use in a clinical trial.

Last updated: October 2026

Informatics and Electronic Systems in Clinical Trials

The transition from paper-based data collection to electronic systems has revolutionized clinical research, enabling faster data analysis, real-time monitoring, and global collaboration. However, the use of informatics in clinical trials introduces new compliance challenges. The Clinical Research Coordinator (CRC) must understand the regulatory guardrails that ensure electronic data is as trustworthy and verifiable as traditional paper records.

21 CFR Part 11: Electronic Records and Signatures

In 1997, the FDA issued Title 21 of the Code of Federal Regulations, Part 11 (commonly referred to simply as "Part 11"). This regulation defines the criteria under which the FDA 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.

For an electronic system (like an Electronic Health Record (EHR), Electronic Data Capture (EDC) system, or eRegulatory binder) to be Part 11 compliant, it must feature several technical and procedural controls:

Validation: The system must be validated to ensure accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records.

Audit Trails: The system must generate a secure, computer-generated, time-stamped audit trail that independently records the date and time of operator entries and actions that create, modify, or delete electronic records. The audit trail must not obscure the original data.

Access Controls: The system must limit system access to authorized individuals.

Electronic Signatures: Electronic signatures must be unique to one individual and cannot be reused or reassigned. When an electronic signature is applied, it must clearly indicate the printed name of the signer, the date and time the signature was executed, and the meaning of the signature (e.g., "review," "approval," "responsibility").

Data Integrity and the ALCOA-C Principles

Data integrity refers to the completeness, consistency, and accuracy of data over its entire lifecycle. Regulatory agencies globally rely on the ALCOA-C principles to assess data integrity, whether the data is paper-based or electronic.

Principle Definition Application in Electronic Systems

A ttributable It must be clear who observed and recorded the data. Unique user logins and passwords ensure every data entry is tied to a specific person. Passwords must never be shared.

L egible Data must be readable and understandable. Electronic systems inherently solve handwriting legibility issues, but data must be stored in a readable format long-term.

C ontemporaneous Data must be recorded at the time the observation occurs. System time-stamps capture the exact moment data is entered, preventing retroactive falsification.

O riginal The first place data is recorded is the source document. If data is entered directly into an EDC (eSource), the EDC is the original. If transferred from paper, the paper remains the original.

A ccurate Data must be correct, truthful, and valid. Built-in EDC edit checks (e.g., flagging a body temperature of 150°F as impossible) help prevent inaccurate entries.

C omplete All data must be available, including metadata and audit trails. No data can be deleted. If a change is made, the audit trail shows the old value, new value, who made the change, and why.

Note: ALCOA+, the set named in ACRP's content outline, adds Consistent, Enduring and Available to these six attributes.

Electronic Data Capture (EDC) Systems

The EDC is the primary tool used by CRCs to transmit subject data to the sponsor. When a subject comes in for a visit, the CRC gathers the source documents (lab results, physician notes) and transcribes the required datapoints into the EDC's electronic Case Report Forms (eCRFs).

Ensuring Compliance in the EDC

Training: CRCs must complete sponsor-provided training on the specific EDC system before they are granted a username and password. This training is documented and filed in the regulatory binder.

Data Entry Timelines: Sponsors usually require data to be entered into the EDC within a specific timeframe after a study visit. Timely entry ensures contemporaneous data and allows monitors to detect safety signals rapidly.

Resolving Queries: Clinical Research Associates (CRAs) or Data Managers review the EDC data. If they find discrepancies (e.g., a missing blood pressure reading or a protocol deviation), they issue a "query" within the system. The CRC is responsible for investigating the query, correcting the data if necessary, and providing a rationale in the EDC. This process must be completed promptly to keep the database clean and ready for lock.

E-Source and Direct Data Entry

The industry is moving toward eSource , where clinical data is entered directly into an electronic system (like an electronic tablet given to a patient for a questionnaire) without a prior paper record. When utilizing eSource, the electronic record is the original source. The system used must be fully Part 11 compliant and allow the investigator to retain control of the data, separate from the sponsor, to ensure independent verification.

System Validation Life Cycle

Computerized systems used in clinical trials must undergo rigorous validation to ensure they meet their intended purpose consistently. Validation is not a one-time event; it encompasses the entire life cycle of the software. It begins with defining the User Requirements Specifications (URS)—what exactly the system needs to do. This is followed by building the system and executing extensive testing protocols, including Operational Qualification (OQ) and Performance Qualification (PQ). For the CRC, while the sponsor or vendor typically handles the heavy lifting of validation, the site must maintain documentation proving that the system (especially if it is site-owned, like an institutional EHR) has been validated. If the system undergoes an update or patch, a risk assessment and potential re-validation must occur to ensure the changes did not break existing functionality or compromise Part 11 compliance.