Published on 22/12/2025
How to Conduct Source Data Verification (SDV) in EMR Systems
As the use of Electronic Medical Records (EMRs) becomes ubiquitous in clinical settings, Source Data Verification (SDV) must evolve to meet digital workflows. CRAs increasingly access EMR systems to verify data against Case Report Forms (CRFs), and this shift requires a clear understanding of procedures, access controls, and compliance standards. This tutorial outlines best practices for performing SDV in EMR systems effectively and securely.
Understanding EMRs in the Context of SDV
EMRs serve as the official source for clinical information such as diagnoses, lab values, and treatment history. For SDV purposes, CRAs must access specific, protocol-relevant data while ensuring compliance with Good Clinical Practice (GCP) and privacy regulations like USFDA and EMA requirements.
Challenges of SDV in EMR Environments
- Diverse EMR platforms with varying user interfaces
- Access restrictions due to institutional IT policies
- Data fragmentation across modules (labs, notes, medications)
- Limited printing or screen capture permissions
- High risk of unintentional exposure to non-trial data
Access Control: Gaining Entry into EMR Systems
To perform SDV in EMRs, the CRA must be granted temporary, read-only access by the site’s IT or regulatory team. Best practices include:
- Using generic CRA logins with audit trails enabled
- Restricting access to only the
Access policies must be documented in the site monitoring SOP and agreed upon during the site initiation visit. Templates are often available from Pharma SOP templates.
Preparing for EMR-Based SDV
- Obtain the EMR navigation guide or training from site staff.
- List required data points per subject from CRF (e.g., AE dates, vitals, consent dates).
- Coordinate with the site to preload patient charts for quick access during the visit.
Steps to Perform SDV in EMR Systems
1. Locate the Correct Subject Record
Use the anonymized subject ID or assigned trial code to search within the EMR. Avoid browsing unrelated patient files.
2. Navigate to Relevant Modules
- Progress Notes: For clinical visits and AE reports
- Lab Results: For lab values and test timing
- Orders and Medications: For IP administration verification
- Consent Documentation: For date and version control
3. Compare with CRF Entries
Carefully check for transcription errors, missing dates, discrepancies in drug doses or AE onset timing.
4. Raise Queries if Needed
Use the EDC or CTMS to log discrepancies. Avoid saving screenshots of PHI. Summarize findings clearly without violating confidentiality.
5. Document in Monitoring Visit Report
Indicate which subjects were verified, which modules accessed, and summarize overall SDV quality. For example:
“SDV was conducted for Subjects 102-005 and 102-008 via Cerner EMR. Consent forms, vitals, AE logs, and IP administration data were verified. One date discrepancy was noted and queried.”
Ensuring GCP and Regulatory Compliance
CRAs must ensure:
- No patient identifiers are recorded in MVRs
- No physical or digital copies of records are retained
- Audit logs are preserved in case of inspections
Refer to Stability Studies for detailed guidance on trial documentation compliance across digital systems.
Regulatory Expectations
Regulatory agencies such as CDSCO and MHRA expect sponsors and CROs to demonstrate proper SDV procedures in EMRs:
- Access control logs must be retrievable
- Training records for CRAs on EMR navigation must be available
- Monitoring reports should reflect accurate and secure SDV execution
Conclusion
As clinical data becomes increasingly digitized, CRAs must adapt to EMR-based SDV with confidence and precision. Following structured procedures, respecting subject confidentiality, and aligning with regulatory expectations ensures reliable monitoring and robust data quality across clinical trials.
