Data Capture Systems and Entering Data Well

Part of Clinical Research Coordinator (CRC) Training: Source Documentation and Data.

About 6 minutes. Free, in your language, no account needed.

Why this matters

Most of a coordinator's data work happens inside software. Knowing what each system is for prevents two expensive mistakes: entering something in the wrong place, and assuming a system has done something it has not.

The systems you will meet

Electronic data capture (EDC). Where case report form data are entered and stored. This is where you will spend most of your data time. It contains visit-based forms, built-in checks, a query function, and an audit trail.

Electronic patient-reported outcome or clinical outcome assessment systems (ePRO, eCOA). Capture data directly from the participant or clinician, usually on a tablet, phone or web portal. Symptom diaries, quality-of-life questionnaires, pain scales.

Interactive response technology (IRT, IWRS, RTSM). Handles randomization and investigational product supply. You enter a participant and it returns an allocation or a kit number.

Clinical trial management system (CTMS). The sponsor's operational tracker: sites, visits, enrollment, monitoring reports, issues. Sites usually do not enter data here, but what your monitor records about your site lives in it.

Electronic trial master file (eTMF). The sponsor's repository for essential records.

Safety or pharmacovigilance database. Where serious adverse event reports are processed by the sponsor.

The site's own electronic health record. Often a source record for the trial, and never under the sponsor's control.

How data flow

Source, wherever it lives, is entered or transferred into EDC. From EDC the data go to the sponsor's data management team for cleaning, then to the statisticians. Safety events also flow to the safety database, and the two must agree — a reconciliation step that will produce questions for your site.

You do not need to be technical. You do need to understand that a value you enter in one system does not automatically appear in another. Randomization entered in the IRT still has to be reflected in EDC. A serious adverse event reported on a safety form still has to be entered on the EDC adverse event page.

Access and accounts

• Every user has their own account. Never share a login, never let someone enter data under your account, and never leave a session open on a shared computer.
• Roles matter. A coordinator's account, an investigator's signature account and a monitor's read-only account exist for different purposes.
• Access changes when staff change. When someone joins the study, request access; when they leave, request removal. E6(R3) section 2.12.10 expects the investigator to notify the sponsor when access permissions need to change.
• Complete the required system training before entering real data, and keep the certificate.

Entering data well

Enter promptly. Most protocols and contracts set a target, commonly a few working days after the visit. Prompt entry is not administrative tidiness; details are forgotten and errors multiply as time passes.

Enter from source, not from memory. Have the record open in front of you.

Do not guess at fields. If a value was not obtained, use the system's provision for missing data and document why in the source. An invented plausible value is falsification.

Respect the field. Units, decimal places, date formats. A weight entered in the wrong unit is a data point that will produce a query, and sometimes a safety flag.

Watch the automated checks. A range check firing usually means one of three things: the value is wrong, the unit is wrong, or the value is genuinely unusual and needs a comment. Overriding checks repeatedly without thought is a pattern monitors look for.

Never copy forward. Identical vital signs across several visits, or values copied between participants, is the most recognizable sign of fabricated data.

Electronic signatures and investigator review

Most systems require the investigator to review and sign off participant data. That signature is a medical review, not a formality. Do not chase it as a box to tick, and never apply it on the investigator's behalf under any circumstances.

When something goes wrong with the system

• Record what happened and when: the error message, what you were doing, and which participant and visit were affected.
• Report it through the sponsor's helpdesk route, not informally.
• If data cannot be entered, record it in source and enter it when the system is available, noting the reason for the delay.
• If you suspect data have been lost or altered, escalate immediately rather than re-entering and hoping.

In practice

Nadia enters visit 4 for a VT-201 participant. The system rejects a systolic blood pressure of 84, which is outside the expected range.

Her first instinct is to assume she mistyped. She checks the source: the printed strip really does say

1. The participant had felt faint that morning.

She does three things. She enters the value and adds the comment the system asks for. She makes sure the episode of dizziness is recorded as an adverse event, because a low reading with a symptom is not just a data point. And she tells Dr. Osei the same day, because he decides whether anything about the participant's treatment must change.

She does not change the value to make the check pass. She does not delete the entry and start again.

The check did its job: it made a human look. That is what checks are for.

Key takeaways

• Each system has one purpose — EDC for case report form data, IRT for randomization and supply, ePRO for participant-entered data, CTMS and eTMF for the sponsor's operations and records — and entering data in one does not populate another.
• Every user must have an individual account, and access must be requested and removed as staff join and leave the study.
• Enter data promptly and from source, never from memory, and never invent a plausible value for a measurement that was not obtained.
• An automated check that fires means the value, the unit, or the situation needs a human decision, and repeatedly overriding checks is a pattern monitors look for.
• Identical values repeated across visits or participants are the most recognizable signature of fabricated data, and investigator sign-off is a medical review that must never be applied by anyone else.