For decades, sponsors leaned on 100% source data verification (SDV) as a security blanket, checking every field against every source document. That approach is expensive, slow, and — according to FDA's own risk-based monitoring guidance — often delivers minimal added benefit compared to targeted review.
This guide breaks down what SDV actually is, how it differs from source data review (SDR), what regulators expect, and the best practices sponsors and CROs should apply to protect data quality without burning through budget.
Key Takeaways
- SDV compares CRF/EDC entries against original source documents to catch transcription errors before they compromise trial results
- FDA guidance finds 100% SDV often adds little value for its cost, which is why risk-based monitoring is now the preferred approach
- Accuracy checks and documentation review are not interchangeable: SDV verifies data, while SDR confirms quality and protocol adherence
- Pairing risk-based monitoring with trained staff and validated EDC systems produces the strongest data integrity outcomes
What Is Source Data and Source Data Verification in Clinical Trials?
Source data is the original record of a trial participant's experience. Under ICH E6(R2), this includes:
- Hospital and medical records
- Laboratory reports and notes
- Imaging results
- Patient diaries and PRO data
- Pharmacy records
- EHR entries
Everything entered into a CRF or EDC system must trace back to one of these original sources.
Source data verification (SDV) is the process of comparing that CRF/EDC entry against the original source document to confirm accuracy. If a lab value in the database doesn't match the lab report, SDV catches it.
Why SDV Matters for GCP Compliance
SDV underpins Good Clinical Practice by protecting two things simultaneously: participant safety and the scientific credibility of trial results. A miscoded adverse event or transposed dosage doesn't just create a query. It can mask a safety signal or invalidate an endpoint.
Three Common SDV Approaches
| Approach | Coverage | Trade-off |
|---|---|---|
| Complete (100%) SDV | Every field, every subject | Thorough but resource-intensive |
| Static/partial SDV | Fixed sample or percentage | Moderate cost, moderate coverage |
| Targeted/risk-based SDV | Critical data points only | Efficient, requires strong risk assessment |
Historically, on-site monitoring visits devoted a substantial share of time to 100% SDV checks. That resource burden is one reason the industry has moved toward smarter alternatives.
A 2014 peer-reviewed study verifying over 3 million data fields found an overall discrepancy rate of just 0.45%. Those findings raise real questions about whether exhaustive verification is worth the drain.
SDV vs. Source Data Review (SDR): Understanding the Difference
These two terms get used interchangeably far too often, and that's a mistake.
SDV verifies that data entered into the CRF matches the source document. It's a transcription check.
SDR evaluates the quality, completeness, and protocol compliance of the source documentation itself, regardless of what got transcribed. SDV asks "did they copy it correctly?" SDR asks "was the underlying record any good in the first place?"
SDR catches problems SDV simply can't see, including:
- Poor documentation practices at the site level
- Missing informed consent details
- Non-adherence to standard of care
- Gaps in investigator oversight
TransCelerate's glossary of risk-based monitoring terms explicitly separates the two activities, noting that SDR is not a source-to-CRF comparison at all.
Industry research associated with TransCelerate also suggests that few critical data discrepancies come from transcription errors caught by SDV. Documentation quality issues, not typos, are often the bigger risk.
The practical takeaway: relying on SDV alone leaves a blind spot. Sponsors who pair SDV with SDR get a far more complete picture of both data accuracy and site conduct.
Regulatory Expectations Shaping SDV Practices
Neither ICH E6 nor FDA guidance mandates 100% SDV. Many sponsors still operate as if full verification were required.
ICH E6 (Good Clinical Practice) requires that source documents be complete, accurate, and accessible to monitors. It says nothing about verifying every single data point.
FDA's risk-based monitoring guidance goes further, stating explicitly that comparing 100% of source data for every subject and visit may offer minimal benefit. Instead, FDA recommends a "representative" review, sampling the most critical data points across a subset of subjects and visits.
FDA's electronic source data guidance adds a technical layer, requiring that:
- Data originators and timestamps are identifiable
- Audit trails preserve every addition, deletion, or alteration
- Investigators retain control and inspection access
None of this means reduced vigilance. FDA is clear that risk-based approaches exist to focus oversight on the risks that matter most, not to loosen standards.
Informed consent and protocol compliance remain tightly linked to SDV. If consent documentation is incomplete, no amount of transcription checking fixes that underlying problem.
Best Practices for Conducting Effective Source Data Verification
1. Identify critical data points up front
Before monitoring begins, map out what actually matters:
- Inclusion/exclusion criteria
- Primary and secondary endpoints
- Safety data (adverse events, SAEs)
Everything else gets proportionally less scrutiny.
2. Adopt a risk-based monitoring (RBM) plan
Blend targeted on-site checks with centralized, remote data review. The strongest plans combine both, adjusting intensity based on site performance and risk signals.
3. Establish clear SOPs for discrepancy resolution
Every protocol deviation and data discrepancy needs a documented path: identification, escalation, resolution, and closure. Ambiguity here is where audit findings come from.
4. Use EDC/eSource systems with built-in validation
Direct data entry with automated edit checks catches errors at the point of entry, before they ever require SDV. Systems with role-based access and validated audit trails also satisfy FDA's electronic source data expectations.
5. Train monitors and site staff continuously
Guidelines evolve. Study protocols change. Staff turnover happens. Ongoing training on current SDV/SDR expectations keeps everyone aligned.
At DRK Research Solutions, clinical data management spans the full lifecycle: protocol review and eCRF programming at study setup, proactive data review and discrepancy handling during conduct, and database lock with SDTM conversion at closeout.
That full-cycle visibility across sites in Europe, the Middle East, Asia, Africa, and the Americas helps sponsors maintain consistent verification standards when local infrastructure and regulatory expectations vary from site to site.
Technology and Emerging Trends in SDV
EDC systems, eSource platforms, and AI/ML-assisted anomaly detection are steadily shifting SDV away from manual, on-site checks toward centralized statistical monitoring. Instead of a monitor flipping through paper charts, algorithms flag statistical outliers across an entire dataset in real time.
Decentralized clinical trials (DCTs) are accelerating this shift further. When patients generate data remotely through wearables or e-diaries, traditional on-site SDV isn't even feasible — centralized, remote review becomes the default.
ACRO's peer-reviewed analysis of risk-based quality management found at least one RBQM component in:
- 53% of trials in 2019
- 77% in 2020
- 88% in 2021
That is a rapid shift in just two years. Adoption of some RBQM component still does not mean 100% SDV has vanished. ACRO's 2023 summary reports that full SDR/SDV coverage still occurred on a majority of trials, even amid growing centralized monitoring. The transition is real, but gradual—not universal.
Choosing the Right Partner for Data Integrity in Global Trials
Multi-regional trials multiply complexity quickly. A monitoring plan that works at a well-resourced site in Western Europe may not translate cleanly to a site with limited connectivity or a different regulatory infrastructure.
Sponsors running trials across multiple regions need a partner that can:
- Maintain consistent SDV/SDR standards regardless of local infrastructure
- Navigate varying regulatory frameworks (FDA, MHRA, WHO PQ, PIC/S) without diluting rigor
- Provide local-language site support alongside centralized oversight
DRK Research Solutions has operated as a full-service CRO for over a decade, with offices spanning Switzerland, the UK, USA, Pakistan, Malaysia, Nepal, and the UAE. That footprint pairs localized site support with centralized data management oversight, the combination that underpins risk-based monitoring at scale.
For sponsors running Phase II–IV studies across regulated markets and emerging regions, that mix of global reach and local execution helps keep SDV standards consistent at every site.
Frequently Asked Questions
What is considered source data in a clinical trial?
Source data includes medical records, lab results, imaging reports, and patient diaries — any original record documenting a participant's trial experience. It's the baseline against which CRF entries are checked.
What is source data verification (SDV) in clinical trials?
SDV compares data entered into CRFs or EDC systems against original source documents to confirm accuracy. It catches transcription errors before they affect study results.
What is the difference between source data verification (SDV) and source data review (SDR) in clinical trials?
SDV checks whether transcribed data matches the source document. SDR evaluates whether the source documentation itself is complete, high-quality, and protocol-compliant.
Is 100% SDV still required in clinical trials?
No regulation mandates 100% SDV. FDA guidance explicitly supports risk-based approaches, noting that verifying every data point often adds minimal value relative to its cost.
How does risk-based monitoring improve SDV efficiency?
Risk-based monitoring concentrates verification resources on high-risk, high-impact data points like endpoints and safety data, rather than checking everything equally. This saves time and cost without sacrificing oversight of what matters most.
Who is responsible for source data verification in a clinical trial?
Sponsors and their designated CRO monitors carry SDV responsibility, while site investigators must ensure their CRF entries stay consistent with source documentation throughout the trial.
