Under ICH E6(R3), a data collection tool is a paper-based or electronic instrument that, in a clinical trial, collects data and related metadata from a data originator and transmits them to the sponsor. The data originator may be a participating person, a member of the study team, a wearable, a sensor, or another computer system. The term therefore describes the function of data capture, not a specific screen form or a single document.
Collection at the Point of Data Origin
A data collection tool translates the information defined in the protocol into capture fields, questions, measurements, or data transfers. What matters is the link between the planned data point and its origin: a blood pressure measurement may be documented by site staff, a symptom reported by the participating person, or an activity provided automatically by a sensor. Each of these routes includes metadata that make the context and origin of the information identifiable.
For manual transfer from paper or an electronic health record into another system, the level of review must follow the criticality of the data. ICH E6(R3) also requires that data sources and the collection method can be pre-specified in the protocol; a data flow diagram can complement this specification. Automated edit checks at the point of capture must be implemented in a controlled manner so that any triggered query is based on a traceable rule.
Suitability, Release, and Operation
The sponsor must ensure that the tool is fit for its intended purpose, can capture the protocol-required information, and is validated and ready for use before deployment. For an ePRO application, this includes aspects such as language, questionnaire logic, and time windows; for a wearable, data transmission, assignment to the correct study participant, and handling interruptions in the data stream are also relevant.
Even after study start, use remains bound to the protocol and study-specific instructions. The site is responsible for complete, legible, and timely entry into the tools it operates. If corrections are made, they must not obscure the original entry; the rationale and the associated source record must substantiate the correction.
Distinction from the CRF and from Standalone Digital Solutions
The case report form is a data collection tool, but it is not synonymous with it. It serves to record, for each participating person, the protocol-required information to be reported by the investigator to the sponsor. An electronic case report form is its electronic form and falls under the umbrella term, as does an electronic patient-reported outcome.
Interactive Response Technologies often manage randomization or investigational product supply, but they can also capture data within a defined process. Clinical outcome assessments and wearables are further examples because they capture information directly from people or machines. The umbrella term prevents capture requirements from being assessed only for the eCRF, even though a relevant endpoint originates from a completely different instrument.
Before release, it should also be verified that entries can be unambiguously assigned to a visit, a person, and a study version. For mobile applications, offline behavior, subsequent synchronization, and timestamps are part of the functional review. For system transfers, it must be defined whether the sponsor receives raw data, pre-processed values, or both. This decision affects which metadata remain available for later plausibility checks and for reconstructing a data flow.
A technical release must therefore also demonstrate that these assignments work in the medium actually used and are not merely described in a demonstration environment.
Relevance for clinical trials
Selecting the data collection tool determines early on which data source will be used for an endpoint and what training, review, and technical safeguards are required. Incorrectly configured visit logic can represent visits incompletely; an untested interface can transmit measurements without the required metadata. Therefore, the protocol, eCRF specification, device instructions, and data management plan must describe the same collection pathway.
Full-service CROs such as Mediconomics support the selection and specification of protocol-compliant collection instruments, eCRF and ePRO design, UAT and validation documentation, and data flow diagrams for wearables or laboratory interfaces. This enables Data Management, Clinical Operations, and Monitoring to align site training, oversight of incoming data, and handling of system-specific queries.
Frequently Asked Questions (FAQ)
Is a wearable always a data collection tool?
If the device captures study data and the associated context in accordance with the protocol and reports them to the sponsor, it falls under the term. A privately used device without study relevance does not, solely by virtue of its technical capability.
Can an electronic health record provide data to a data collection tool?
Yes. ICH E6(R3) explicitly cites electronic transfer from a system such as an electronic health record or a laboratory system as a possible origin of the data.
Why is testing the eCRF alone not sufficient?
Because the study may also use PRO questionnaires, randomization systems, sensors, or system-to-system transfers. Each data collection instrument actually used must be fit for its specific purpose.
Regulatory References
- ICH E6(R3), Good Clinical Practice – defines data collection tools and assigns their suitability to data governance.
- EMA/INS/GCP/112288/2023 – describes expectations for computerized systems and electronic study data.
- EudraLex Volume 4, Annex 11 – specifies risk-based controls for computerized systems.
