| Submitted By: Anthony Corso
/ Veeva Systems
|
| Data Element Information |
| Data Element Description |
A structured indicator reflecting whether an individual meets the eligibility criteria for participation in a specific clinical research study. |
| Rationale for Separate Consideration |
USCDI currently includes many foundational clinical data elements that are commonly used to evaluate research eligibility, such as diagnoses, laboratory results, demographics, and observations. However, USCDI does not provide a standardized way to represent the outcome of a study-specific eligibility assessment or to indicate whether an individual meets the criteria for a particular clinical research study.
The Eligibility Indicator represents a research-scoped determination derived from one or more clinical attributes, rather than the underlying clinical observations themselves, which are already represented elsewhere in USCDI. As such, it is distinct from existing observation-level data and does not duplicate clinical facts or eligibility logic.
Standardizing an Eligibility Indicator enables consistent representation of eligibility status across healthcare and research systems, supporting interoperability for research screening, enrollment, monitoring, and downstream regulatory and analytical use cases.
This data element is limited to research eligibility and does not represent insurance coverage, benefit eligibility, or payer determinations. |
| Use Case Description(s) |
| Use Case Description |
The Eligibility Indicator supports clinical research workflows by enabling systems to record and exchange whether an individual meets the eligibility criteria for a specific study at a given point in time. It is used in research screening, recruitment, enrollment decision-making, and monitoring of eligibility status over the lifecycle of a study.
By representing eligibility status as a structured, exchangeable data element, healthcare organizations and research sponsors can more efficiently identify potential participants, coordinate eligibility assessments across sites, and integrate research workflows with EHR-based clinical data. This supports just-in-time recruitment, reduces manual screening burden, and improves auditability of eligibility determinations.
Eligibility indicators also support real-world evidence generation and regulatory analysis by enabling consistent identification of study cohorts used in comparative effectiveness research, surveillance activities, and post-market evaluation. |
| Estimate the breadth of applicability of the use case(s) for this data element
|
Aligns with Level 2
This data element applies broadly across interventional and observational clinical research studies, including studies that leverage real-world healthcare data. It is relevant to research conducted by pharmaceutical companies, academic institutions, government agencies, and collaborative research networks.
The Eligibility Indicator supports expanding reliance on EHR-enabled research, real-world data submissions to regulatory authorities, and learning health system models by enabling consistent, interoperable representation of research eligibility status across systems and over time. |
| Supporting Attachments |
Veeva_USCDI_v6_Comments.pdf
|
| ONC Priority |
- Address public health interoperability needs of reporting, investigation, and emergency response
|
| Maturity of Use and Technical Specifications for Data Element |
| Applicable Standard(s) |
Eligibility determinations are represented and operationalized across multiple standards and data models:
HL7 FHIR, including ResearchStudy and ResearchSubject resources, which support representation of study participation context and eligibility status
HL7 FHIR Observation, which supports exchange of the clinical attributes commonly used to derive eligibility
CDISC SDTM, which captures eligibility-related information as part of standardized clinical trial datasets submitted to regulatory authorities
OMOP Common Data Model, which supports cohort definition and eligibility indicators across multi-institution observational research networks
These standards demonstrate that eligibility determinations are already implemented and exchanged across research and healthcare systems using established interoperability frameworks.
|
| Additional Specifications |
HL7 FHIR ResearchStudy and ResearchSubject resources
HL7 FHIR Observation and related implementation guides
CDISC SDTM Implementation Guide v3.4
These specifications support consistent capture and exchange of eligibility-related data across production systems. |
| Current Use |
(Level 2) Captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer |
| Extent of exchange
|
(Level 2) Between more than two production EHRs or other HIT modules using available interoperability standards |
| Supporting Artifacts |
HL7 FHIR ResearchSubject and ResearchStudy Resources: These resources support exchange of research participation context, including eligibility and enrollment-related status, across EHRs, CTMS platforms, registries, and research systems using FHIR-based interoperability.
HL7 FHIR Observation Resource: Eligibility determinations are derived from structured clinical attributes such as diagnoses, laboratory results, and performance status, which are exchanged across multiple production systems using FHIR Observation and reused in research eligibility workflows.
CDISC SDTM Implementation Guide v3.4: Eligibility-related determinations and subject disposition are captured and exchanged as part of standardized clinical trial datasets submitted to regulatory authorities, supporting consistent identification of eligible and ineligible participants across sponsors, CROs, and health authorities.
OMOP Common Data Model: Eligibility indicators and cohort inclusion status are implemented and exchanged across multi-institution observational research networks, supporting large-scale eligibility assessment and reuse of real-world clinical data for research.
These artifacts demonstrate that research eligibility indicators are already captured and exchanged across more than two production systems using widely adopted interoperability standards.
|
| Potential Challenges |
| Restrictions on Standardization (e.g. proprietary code) |
There are no proprietary restrictions on the standardization of this data element. Relevant standards are publicly available and maintained by recognized standards development organizations. |
| Restrictions on Use (e.g. licensing, user fees) |
There are no licensing or user fee restrictions associated with the use of this data element. |
| Privacy and Security Concerns |
Privacy and security concerns are limited. While eligibility determinations may reflect sensitive clinical criteria, the Eligibility Indicator itself does not include clinical detail and does not independently enable identification of individual patients or participants. |
| Estimate of Overall Burden |
The overall burden to implement this data element is low to moderate. Eligibility determinations are already captured or derived in many research and healthcare systems. Implementation primarily requires standardized representation and governance rather than new data collection, making adoption feasible with modest configuration and coordination. |
| Other Implementation Challenges |
A key implementation challenge is ensuring consistent definition and governance of eligibility criteria and resulting indicators across studies and systems, particularly where eligibility is assessed dynamically over time. This can be addressed through standardized metadata, study protocol alignment, and clear distinction between eligibility indicators and underlying clinical data. |
ONC Evaluation Details
Each submitted Data Element has been evaluated based on the following criteria. The overall Level classification is a composite of the maturity based on these individual criteria. This information can be used to identify areas that require additional work to raise the overall classification level and consideration for inclusion in future versions of USCDI
|
Criterion #1 Maturity - Current Standards |
Level 2
- Data element is represented by a terminology standard or SDO-balloted technical specification or implementation guide.
|
Criterion #2 Maturity - Current Use
|
Level 0
- Data element is captured, stored, or accessed in limited settings such as a pilot or proof of concept demonstration.
|
Criterion #3 Maturity - Current Exchange |
Level 0
- Data element is electronically exchanged in limited environments, such as connectathons or pilots.
|
Criterion #4 Use Case(s) - Breadth of Applicability |
Level 0
- Use cases apply to a limited number of care settings or specialties, or data element represents a specialization of other, more general data elements.
|
|