Electronic Data Capture (EDC): One Layer in the Stack

At a glance

• EDC is the system that captures clinical trial data into electronic case report forms (eCRFs). It is one layer in the eClinical stack, not the whole thing.
• The EDC workflow is a loop: data is entered into the eCRF, edit checks flag problems, queries resolve discrepancies, and the database is locked. Each step has a job.
• EDC is not the same as clinical data management (the discipline) or a CDMS (the broader system). People use the terms interchangeably; they should not.
• An eCRF is an electronic record under 21 CFR Part 11, so an EDC system has to support Part 11 controls: audit trails, access control, validation, and electronic signatures.
• Capturing data electronically reduces transcription errors and enables real-time review and remote monitoring, which is exactly why the field moved off paper.

If you keep hearing “EDC” and “CDMS” used as if they were the same thing, you are not alone, and the confusion leads teams to shop for the wrong system. This guide fixes that. It explains what EDC actually is, walks the capture-to-lock workflow, untangles EDC from clinical data management and the CDMS, places EDC in the broader eClinical stack, and sets out what Part 11 expects of any electronic capture system. It is a concept explainer, not a buyer’s guide and not a clinical-data-management course; those are separate guides.

What electronic data capture (EDC) is

EDC is the technology used to record clinical trial data directly into electronic forms. The unit of capture is the eCRF. FDA describes the eCRF as an auditable electronic record of information generally reported to the sponsor on each trial subject according to the protocol, which enables clinical investigation data to be systematically captured, reviewed, managed, stored, analyzed, and reported (FDA eSource, §II). Crucially, an eCRF is an electronic record in the regulatory sense: FDA’s regulations define an electronic record as any combination of text, graphics, data, audio, pictorial, or other information in digital form created, modified, maintained, archived, retrieved, or distributed by a computer system (21 CFR 11.3(b)(6)), and an eCRF is an example of one.

The eCRF: the unit of data capture

Each eCRF holds data elements, the smallest units of observation for a subject, such as a blood pressure reading or a lab value. The whole point of capturing those elements electronically, rather than on paper and transcribing later, is data quality. FDA notes that capturing source data electronically and transmitting it to the eCRF should eliminate unnecessary duplication, reduce the possibility of transcription errors, facilitate remote monitoring of data, and promote real-time access for data review (FDA eSource, §II). And source data, however captured, should be attributable, legible, contemporaneous, original, and accurate, the ALCOA attributes (FDA eSource, §II).

How an EDC system works, end to end

Data entry, edit checks, and automated validation

Data enters the eCRF either by direct entry or by transcription from a source. When data is entered directly at the visit, the eCRF is the source and there is no paper step to introduce errors (FDA eSource, §III.A.2). To catch problems at the point of entry, EDC systems use edit checks. FDA encourages the use of electronic prompts, flags, and data quality checks in the eCRF to minimize errors and omissions, alerting the originator to missing data, inconsistencies, and inadmissible values such as a date out of range (FDA eSource, §III.A.5). These checks are what make EDC more than a digital form: they enforce data quality as data arrives.

Query workflow, source data verification, and database lock

When an edit check or a reviewer flags a discrepancy, it becomes a query that must be resolved. Any change to data must be traceable: FDA requires that changes not obscure the original entry and that the system record who made the change, when, and why (FDA eSource, §III.A.4; 21 CFR 11.10(e)). Each data element carries a data element identifier recording who entered it and when, which lets sponsors and FDA examine the audit trail and reconstruct the investigation (FDA eSource, §III.A.3). The clinical investigator reviews and electronically signs the completed eCRF for each subject before data is archived or submitted, and that signature must comply with Part 11 (FDA eSource, §III.B.1.a). Once review and cleaning are complete, the database is locked. Because both trial data and source data can be accessed electronically, much source data review can be done remotely, which is part of why EDC enables risk-based and centralized monitoring (FDA eSource, §II).

EDC vs paper CRFs: the benefits that actually matter

The case for EDC over paper is not novelty; it is fewer errors and faster visibility. Eliminating the transcription step removes a whole class of errors, and real-time access lets the team and sponsor see problems while they can still be fixed (FDA eSource, §II). FDA even encourages authorized viewers to look at eCRF data before and after investigator sign-off, to detect study problems early such as safety concerns, protocol deviations, missing data, and discrepancies (FDA eSource, §III.D). Paper still lingers where source data originates on paper and is transcribed, in which case the paper source must be retained for inspection (FDA eSource, §III.A.2).

EDC vs CDMS vs clinical data management: untangling the terms

This is where most confusion lives, so be precise:

• Clinical data management (CDM) is the discipline: the people and processes that design forms, clean data, manage queries, and lock the database.
• EDC is the tool that captures data into eCRFs and runs edit checks and queries.
• CDMS (clinical data management system) is the broader software environment in which data is managed; EDC is often a component of, or overlaps with, a CDMS.

The short version: CDM is what you do, EDC is what you capture with, and a CDMS is the wider system you manage in. EDC is not a synonym for clinical data management, even though vendors and job descriptions often blur them.

Where EDC sits in the eClinical stack

EDC is one of several systems in a modern trial, each with a different job:

• EDC captures study data into eCRFs.
• RTSM/IRT handles randomization and trial supply management.
• eTMF stores the trial’s essential records and documents.
• CTMS manages the operational side: sites, visits, timelines, and tasks.

These are different layers. Knowing which problem EDC solves, data capture, keeps you from expecting it to do randomization, document storage, or project management.

What 21 CFR Part 11 expects of an EDC system

Because an eCRF is an electronic record, an EDC system must support the Part 11 controls. Part 11 sets the criteria under which FDA considers electronic records and signatures trustworthy, reliable, and generally equivalent to paper (21 CFR 11.1(a)). For closed systems, it requires, among other controls: validation of systems to ensure accuracy, reliability, and the ability to discern invalid or altered records; the ability to generate accurate and complete copies for inspection; protection of records for retrieval throughout retention; limiting access to authorized individuals; and secure, computer-generated, time-stamped audit trails that record the date, time, and author of entries that create, modify, or delete records without obscuring previous information (21 CFR 11.10). Where electronic signatures are used, they must show the signer’s printed name, the date and time, and the meaning of the signature, and be linked to their records so they cannot be excised or transferred to falsify a record (21 CFR 11.50, 11.70).

A key nuance: Part 11 compliance is a property of how a system is validated and operated, not a feature you buy. FDA’s eSource guidance puts it generally: adequate controls should be in place to ensure confidence in the reliability, quality, and integrity of the electronic source data, and sponsors should describe the intended use of computerized systems, the security measures, and the electronic data flow in the protocol or data management plan (FDA eSource, §IV). The system must support Part 11 controls; making them work is the sponsor’s responsibility, and no vendor’s “Part 11 compliant” label changes that. (For the full anatomy of Part 11, see the dedicated Part 11 explainer.)

Choosing and adopting EDC: what to evaluate next

Once you understand what EDC is, the buying questions become clearer: how fast can a non-programmer build and amend a study, how much of the validation burden does the vendor carry, and how well does the EDC integrate with the rest of your stack. Those are the subject of the EDC buyer’s guide; this piece is about understanding the concept first.

A note on boundaries: TrialTrack handles clinical project management, not electronic data capture. It sits alongside your EDC in the stack, managing sites, visits, and tasks, rather than capturing study data.

The bottom line

EDC is the data-capture layer of the eClinical stack: it records data into eCRFs, runs edit checks, manages queries, and feeds the database lock. It is not clinical data management and not a CDMS, and it lives next to RTSM, eTMF, and CTMS rather than replacing them. Because an eCRF is a regulated electronic record, an EDC system has to support Part 11 controls, but compliance is something you operate, not something you purchase. Understand which problem EDC solves, and you will evaluate systems for the right thing.

Sources

• 21 CFR Part 11, Electronic Records; Electronic Signatures
• FDA Guidance: Electronic Source Data in Clinical Investigations (2013)