Source Documents and Source Data Verification
4.2 Source Documents and Source Data Verification
Reading 1
3 / 7
4.2 Source Documents and Source Data Verification
Source documents are the original records in which clinical research data are first captured. They may include hospital files, clinic notes, laboratory reports, pharmacy records, imaging reports, participant diaries, consent forms, vital signs charts, electronic health records, device outputs, field notebooks, or study-specific worksheets. Source data are the values and observations recorded in these documents that are necessary for reconstructing and evaluating the study.
The relationship between source documents and the research database is central to data integrity. A database value should be traceable to an appropriate source unless the eCRF itself is defined as the source. For example, if a nurse measures a participant's temperature and enters it directly into REDCap during the encounter, the REDCap entry may function as the source record if the protocol and data management plan define it that way. If the nurse first writes the value on a clinic worksheet and a data clerk later enters it into REDCap, the worksheet is the source document and the REDCap entry is a transcription of that source.
Source Data Verification, often abbreviated as SDV, is the process of comparing database values against source documents to confirm accuracy, completeness, and consistency. In traditional monitoring models, monitors may verify a high proportion of key variables, especially primary outcomes, informed consent, eligibility criteria, and safety events. In risk-based approaches, SDV may focus on critical data and processes rather than every field. Regardless of the model, the study team must know which source documents support each database variable.
Source documentation is important because it allows reconstruction of the study. If a regulator, sponsor, monitor, auditor, or investigator asks how a value entered the final dataset, the team should be able to trace it back to the original observation or certified copy. Without source traceability, the credibility of the data is weakened. In addition, source documents protect participants and study teams by demonstrating that procedures occurred as required by the protocol.
The data manager should document source expectations in the data management plan or source document agreement. This is especially important when data come from multiple sources. A laboratory value may come from a laboratory information system, a printed report, or an uploaded file. A follow-up outcome may come from a clinic visit record or a phone follow-up form. A medication exposure may come from pharmacy dispensing logs or clinician notes. The source hierarchy should be clear.
**Table 4.2: Examples of Source Documents and Related Database Fields**
| Database field | Possible source document | Verification concern |
|---|---|---|
| Consent status | Signed consent form or consent log | Confirm consent before study procedures |
| Enrollment date | Enrollment CRF or clinic note | Confirm participant entered study on correct date |
| Temperature | Vital signs chart or direct eCRF entry | Confirm unit and measurement time |
| Hemoglobin result | Laboratory report or laboratory system export | Confirm value, unit, date, and participant ID |
| Treatment dispensed | Pharmacy log or medication administration record | Confirm drug name, dose, and date |
| Adverse event | Clinical note, AE form, participant report | Confirm event description, seriousness, and outcome |
| Follow-up status | Follow-up phone log or clinic attendance record | Confirm outcome and date of assessment |
[Figure 4.2: Suggested image showing source document, CRF/eCRF, database value, query, and audit trail relationship]