Discrepancies Between CRF and Source Data in Audit Observations

Posted on August 18, 2025 By digi

Published on 22/12/2025

CRF vs. Source Data Discrepancies in Clinical Trial Audit Findings

Table of Contents

Toggle

Introduction: The Importance of Data Consistency

Case Report Forms (CRFs) serve as the primary medium for transferring clinical trial data from investigator sites to sponsors. Source documents—such as hospital charts, laboratory records, and diagnostic reports—provide the original clinical evidence. Regulatory agencies including the FDA, EMA, and MHRA emphasize that CRFs must accurately reflect the source data. Discrepancies between the two compromise data reliability and trigger frequent audit findings.

In many inspections, regulators classify CRF vs. source data discrepancies as major deficiencies. These issues not only delay trial analysis but also risk rejection of data in regulatory submissions. A notable example occurred during an FDA audit where blood pressure readings were consistently higher in site source records compared to CRFs, raising questions of potential data manipulation.

See also  Audit Findings in Phase I vs. Phase III Clinical Trials – Key Differences

Regulatory Expectations for CRF and Source Data Alignment

Authorities set clear expectations for data consistency in clinical trials:

• All CRF entries must be verifiable against original source documents.
• Discrepancies must be reconciled

Continue Reading

promptly and documented with an audit trail.

Source Data Verification (SDV) must be conducted regularly as part of monitoring visits.

Any changes to CRFs must retain the original entry and include justification.

Sponsors are accountable for ensuring CRO-managed data reflects source documentation.

According to ICH E6 (R2), sponsors must implement adequate monitoring to ensure trial data recorded in CRFs matches source records. The EU Clinical Trials Register also reinforces transparency in data reporting practices.

Common Audit Findings on CRF vs. Source Data Discrepancies

1. Mismatched Clinical Measurements

Auditors frequently identify cases where lab values, vital signs, or imaging results in CRFs differ from original source records.

2. Missing Source Documentation

In some trials, CRF entries are not supported by source documents, suggesting inadequate site recordkeeping or data fabrication.

3. Retrospective Data Corrections Without Justification

CRF data is sometimes modified after entry without explanation, and the original entry is not retained, violating ALCOA+ principles.

4. CRO Oversight Failures

When CROs manage data entry, sponsors often fail to confirm alignment between CRFs and site source documents, leading to systemic discrepancies.

Case Study: MHRA Audit on CRF vs. Source Data Gaps

In a Phase II oncology trial, MHRA inspectors found over 50 discrepancies between CRFs and source hospital charts, including missing adverse event documentation and altered dosing data. The deficiencies were categorized as critical, resulting in data queries, mandatory reconciliation, and retraining of site staff.

Root Causes of CRF vs. Source Data Discrepancies

Root cause analysis typically identifies the following issues:

• Poor site training on accurate CRF completion and reconciliation.
• Lack of SOPs defining responsibilities for source-to-CRF verification.
• Time pressure leading to retrospective and inaccurate CRF entries.
• Weak sponsor oversight of CRO data entry and monitoring practices.
• Inadequate source documentation practices at investigator sites.

Corrective and Preventive Actions (CAPA)

Corrective Actions

• Perform retrospective reconciliation of all CRF entries against source documents.
• Update CRFs with corrected entries while retaining original data and providing justification.
• Conduct site audits focused on documentation accuracy and completeness.

Preventive Actions

• Implement standardized CRF completion guidelines and train site staff accordingly.
• Include Source Data Verification (SDV) as a mandatory element of monitoring visits.
• Adopt electronic systems linking source and CRF data where feasible to minimize manual errors.
• Define sponsor oversight responsibilities clearly in CRO contracts.
• Introduce data integrity checkpoints prior to database lock.

Sample CRF vs. Source Data Reconciliation Log

The table below illustrates a dummy log for tracking discrepancies:

Best Practices for Preventing CRF vs. Source Discrepancies

To reduce audit risks, sponsors and CROs should adopt the following best practices:

• Provide ongoing training to investigators and site staff on data accuracy and integrity.
• Perform routine monitoring visits with focused Source Data Verification (SDV).
• Use electronic source data capture (eSource) where possible to minimize transcription errors.
• Conduct centralized data reviews to detect anomalies early.
• Maintain detailed reconciliation documentation in the TMF for inspection readiness.

Conclusion: Ensuring CRF and Source Data Integrity

Discrepancies between CRFs and source data remain a major regulatory concern, frequently cited in FDA, EMA, and MHRA audit reports. Such findings undermine the reliability of trial results and delay regulatory approvals.

Sponsors can mitigate these risks by implementing strong oversight practices, adopting electronic systems, and enforcing rigorous monitoring standards. CRF and source data alignment is not just a compliance requirement but a fundamental element of clinical trial credibility.

For further guidance, refer to the ANZCTR Clinical Trials Registry, which highlights the importance of transparent and accurate data reporting.