United States Core Data for Interoperability (USCDI)

The United States Core Data for Interoperability (USCDI) is a standardized set of health data classes and constituent data elements for nationwide, interoperable health information exchange. Review the USCDI Fact Sheet to learn more.

A USCDI Data Class is an aggregation of Data Elements by a common theme or use case.

A USCDI Data Element is a piece of data defined in USCDI for access, exchange or use of electronic health information.  

USCDI ONC New Data Element & Class (ONDEC) Submission System

USCDI V1

Please reference the USCDI version 1 document to the left for applicable standards versions associated with USCDI v1.

Harmful or undesired physiological responses associated with exposure to a substance.

Health professional’s conclusions and working assumptions that will guide treatment of the patient.

Information on a person who participates or is expected to participate in the care of a patient.

Desired state to be achieved by a patient.

Health related matter that is of interest, importance, or worry to someone who may be the patient, patient’s family or patient’s health care provider.

Record of vaccine administration.

Analysis of clinical specimens to obtain information about the health of a patient.

Pharmacologic agents used in the diagnosis, cure, mitigation, treatment, or prevention of disease.

Condition, diagnosis, or reason for seeking medical attention.

Activity performed for or on a patient as part of the provision of care.

The metadata, or extra information about data, regarding who created the data and when it was created.

Representing a patient’s smoking behavior.

USCDI V2

The USCDI v2 contains data classes and elements from USCDI v1 and new data classes and elements submitted through the ONDEC system. Please reference the USCDI Version 2 document to the left for applicable vocabulary standards versions associated with USCDI v2 and to the ONC Standards Bulletin 21-3 for more information about the process to develop USCDI v2 and future versions.

Harmful or undesired physiological responses associated with exposure to a substance.

Health professional’s conclusions and working assumptions that will guide treatment of the patient.

Information on a person who participates or is expected to participate in the care of a patient.

Narrative patient data relevant to the context identified by note types.

Non-imaging and non-laboratory tests performed that result in structured or unstructured findings specific to the patient to facilitate the diagnosis and management of conditions.

Tests that result in visual images requiring interpretation by a credentialed professional.

Information related to interactions between healthcare providers and a patient.

Desired state to be achieved by a patient.

Health related matter that is of interest, importance, or worry to someone who may be the patient, patient’s family or patient’s health care provider.

Record of vaccine administration.

Analysis of clinical specimens to obtain information about the health of a patient.

Pharmacologic agents used in the diagnosis, cure, mitigation, treatment, or prevention of disease.

Condition, diagnosis, or reason for seeking medical attention.

Activity performed for or on a patient as part of the provision of care.

The metadata, or extra information about data, regarding who created the data and when it was created.

Representing a patient’s smoking behavior.

USCDI V3

USCDI v3 contains data classes and elements from USCDI v2 and new data classes and elements submitted through the ONDEC system. Please reference the USCDI Version 3 document to the left for applicable vocabulary standards versions associated with USCDI v3 and to the ONC Standards Bulletin 22-2 for more information about the process to develop USCDI v3 and future versions.

Harmful or undesired physiological responses associated with exposure to a substance.

Health professional’s conclusions and working assumptions that will guide treatment of the patient.

Information on a person who participates or is expected to participate in the care of a patient.

Narrative patient data relevant to the context identified by note types.

Non-imaging and non-laboratory tests performed that result in structured or unstructured findings specific to the patient to facilitate the diagnosis and management of conditions.

Tests that result in visual images requiring interpretation by a credentialed professional.

Information related to interactions between healthcare providers and a patient.

Desired state to be achieved by a patient.

Assessments of a health-related matter of interest, importance, or worry to a patient, patient’s family, or patient’s healthcare provider that could identify a need, problem, or condition.

Record of vaccine administration.

Analysis of clinical specimens to obtain information about the health of a patient.

Pharmacologic agents used in the diagnosis, cure, mitigation, treatment, or prevention of disease.

Condition, diagnosis, or reason for seeking medical attention.

Activity performed for or on a patient as part of the provision of care.

The metadata, or extra information about data, regarding who created the data and when it was created.

USCDI V4

USCDI v4 added 20 data elements and one data class to USCDI v3. Please reference the USCDI v4 standard document and the ONC Standards Bulletin 23-2 for details. To review the prioritization criteria ONC used to select the USCDI v4 data elements, refer to the ONC Standards Bulletin 22-2.

Harmful or undesired physiological responses associated with exposure to a substance.

Information on a person who participates or is expected to participate in the care of a patient.

Narrative patient data relevant to the context identified by note types.

Non-imaging and non-laboratory tests performed that result in structured or unstructured findings specific to the patient to facilitate the diagnosis and management of conditions.

Tests that result in visual images requiring interpretation by a credentialed professional.

Information related to interactions between healthcare providers and a patient.

Physical place of available services or resources.

Desired state to be achieved by a person or a person’s elections to guide care.

Assessments of a health-related matter of interest, importance, or worry to a patient, patient’s family, or patient’s healthcare provider that could identify a need, problem, or condition.

Record of vaccine administration.

An instrument, machine, appliance, implant, software or other article intended to be used for a medical purpose.

Pharmacologic agents used in the diagnosis, cure, mitigation, treatment, or prevention of disease.

Conclusions and working assumptions that will guide treatment of the patient, and recommendations for future treatment.

Condition, diagnosis, or reason for seeking medical attention.

Activity performed for or on a patient as part of the provision of care.

The metadata, or extra information about data, regarding who created the data and when it was created.

Draft USCDI V5

Draft USCDI v5 includes 13 new data elements and two new data classes. Please reference the Draft USCDI v5 standard document and the Standards Bulletin 2024-1 for details. ONC is accepting feedback on the proposed new data elements on the Draft USCDI v5 website until Monday, April 15, 2024 at 11:59 p.m. ET. Feedback will be considered as ONC develops the final version of USCDI v5, which we anticipate publishing in July 2024.

Harmful or undesired physiological responses associated with exposure to a substance.

Information on a person who participates or is expected to participate in the care of a patient.

Non-imaging and non-laboratory tests performed that result in structured or unstructured findings specific to the patient to facilitate the diagnosis and management of conditions.

Tests that result in visual images requiring interpretation by a credentialed professional.

Information related to interactions between healthcare providers and a patient.

Physical place of available services or resources.

Desired state to be achieved by a person or a person’s elections to guide care.

Assessments of a health-related matter of interest, importance, or worry to a patient, patient’s family, or patient’s healthcare provider that could identify a need, problem, or condition.

Record of vaccine administration.

An instrument, machine, appliance, implant, software or other article intended to be used for a medical purpose.

Pharmacologic agents used in the diagnosis, cure, mitigation, treatment, or prevention of disease.

Findings or other clinical data collected about a patient during care.

Provider-authored directive for the delivery of patient care services.

Conclusions and working assumptions that will guide treatment of the patient, and recommendations for future treatment.

Condition, diagnosis, or reason for seeking medical attention.

Activity performed for or on a patient as part of the provision of care.

The metadata, or extra information about data, regarding who created the data and when it was created.

Level 2 data elements meet the following criteria:
  • Represented by a terminology standard or SDO-balloted technical specification or implementation guide.
  • Data element is captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer.
  • Data element is electronically exchanged between more than two production EHRs or other HIT modules of different developers using available interoperability standards.
  • Use cases apply to most care settings or specialties.

Level 2

Harmful or undesired physiological responses associated with exposure to a substance.

Material substance originating from a biological entity intended to be transplanted or infused into another (possibly the same) biological entity.

Tests that result in visual images requiring interpretation by a credentialed professional.

Assessments of a health-related matter of interest, importance, or worry to a patient, patient’s family, or patient’s healthcare provider that could identify a need, problem, or condition.

Findings or other clinical data collected about a patient during care.

Provider-authored directive for the delivery of patient care services.

Conclusions and working assumptions that will guide treatment of the patient, and recommendations for future treatment.

Condition, diagnosis, or reason for seeking medical attention.

Activity performed for or on a patient as part of the provision of care.

The metadata, or extra information about data, regarding who created the data and when it was created.

Physiologic measurements of a patient that indicate the status of the body’s life sustaining functions.

Level 1 data elements meet the following criteria:
  • Represented by a terminology standard or SDO-balloted technical specification or implementation guide.
  • Data element is captured, stored, or accessed in at least one production EHR or HIT module.
  • Data element is electronically exchanged between two production EHRs or other HIT modules using available interoperability standards.
  • Use cases apply to several care settings or specialties.

Level 1

Material substance originating from a biological entity intended to be transplanted or infused into another (possibly the same) biological entity.

Narrative patient data relevant to the context identified by note types.

Assessments of a health-related matter of interest, importance, or worry to a patient, patient’s family, or patient’s healthcare provider that could identify a need, problem, or condition.

Analysis of clinical specimens to obtain information about the health of a patient.

Pharmacologic agents used in the diagnosis, cure, mitigation, treatment, or prevention of disease.

The metadata, or extra information about data, regarding who created the data and when it was created.

Physiologic measurements of a patient that indicate the status of the body’s life sustaining functions.

Level 0 data elements meet the following criteria:
  • Not represented by a terminology standard or SDO-balloted technical specification or implementation guide.
  • Data element is captured, stored, or accessed in limited settings such as a pilot or proof of concept demonstration.
  • Data element is electronically exchanged in limited environments, such as connectathons or pilots.
  • Use cases apply to a limited number of care settings or specialties, or data element represents a specialization of other, more general data elements.

Level 0

Material substance originating from a biological entity intended to be transplanted or infused into another (possibly the same) biological entity.

Information on a person who participates or is expected to participate in the care of a patient.

Tests that result in visual images requiring interpretation by a credentialed professional.

Desired state to be achieved by a patient.

Desired state to be achieved by a person or a person’s elections to guide care.

Analysis of clinical specimens to obtain information about the health of a patient.

Findings or other clinical data collected about a patient during care.

Conclusions and working assumptions that will guide treatment of the patient, and recommendations for future treatment.

Condition, diagnosis, or reason for seeking medical attention.

Activity performed for or on a patient as part of the provision of care.

The metadata, or extra information about data, regarding who created the data and when it was created.

Physiologic measurements of a patient that indicate the status of the body’s life sustaining functions.

For data class description and applicable standards supporting data elements, click to view the USCDI Version 1 (July 2020 errata) in PDF format below. 

Previous USCDI Versions

The USCDI ONC New Data Element and Class (ONDEC) Submission System supports a predictable, transparent, and collaborative process, allowing health IT stakeholders to submit new data elements and classes for future versions of USCDI. Click here for more information and to submit new data elements.

The USCDI standard will follow the Standards Version Advancement Process described in the Cures rule to allow health IT developers to update their systems to newer version of USCDI and provide these updates to their customers.

Comment

ViiV Healthcare Comments on USCDI v5

ViiV Healthcare Company (ViiV) appreciates the opportunity to provide the attached comments and feedback on data elements for inclusion into United States Core Data for Interoperability (USCDI) version 5 (v5). 

ViiV Healthcare Comments_ONC_USCDI v5_Final.pdf

Comments USCDI v5

1

USCDI v5, Pg 5 (Administrative) Concur with additions to Data Class Clinical Notes:
--Emergency Department Note
--Operative Note
Supports HIE exchange with Social Security Administration (SSA) b/c SSA disabiltiy determiniations rely on clincal note information.
Currently supported in HL7 C-CDA R2.1 which allows for faster adoption by implementers for document, or query-based exchange, (versus waiting for HL7 to create mapping or new templates).

USCDI v5, Pg 5 (Administrative) Concur with additions to Data Class Medications:
--Route
Currently supported in HL7 C-CDA R2.1 which allows for faster adoption by implementers for document, or query-based exchange, (versus waiting for HL7 to create mapping or new templates).

3

USCDI v5, Pg 5 (Substantive) Concur with additions to Data Class Patient Demographics:
• Interpreter Needed
• Pronoun
• Name to Use
Data elements are not yet supported in HL7 C-CDA R2.1. 
Therefore, adoption by implementers for document, or query-based exchange must wait for the HL7 to publish mappings to C-CDA.
However, this is not an obstacle for accepting the data elements into USCDI V5.0.
For interoperability, Pronouns needs a value set identified.

4

USCDI v5, Pronouns data element (Substantive) Some systems may determine the data element has a privacy implication. There is limited use in production environments and often implementing additional fields to collect the information is a possible  clinical burden. Recommend the pronoun data element when matured includes options: null, "use only my name" as well as "any pronoun" 

5

USCDI v5, Pg 5 (Administrative) Concur with additions to Data Class Immunizations:
--Lot Number
Currently supported in HL7 C-CDA R2.1 which allows for faster adoption by implementers for document, or query-based exchange, (versus waiting for HL7 to create mapping or new templates).

6

USCDI v5, Pg 5 (Administrative) Concur with addition of New Data Class Observations:
--Advanced Directive Observations
Currently supported in HL7 C-CDA R2.1 which allows for faster adoption by implementers for document, or query-based exchange, (versus waiting for HL7 to create mapping or new templates).

7

USCDI v5, Pg 5 (Substantive) Concur with addition of New Data Class Observations:
-SPCU  Observations
Data elements are not yet supported in HL7 C-CDA R2.1. 
Therefore, adoption by implementers for document, or query-based exchange must wait for the HL7 to publish mappings to C-CDA.
However, this is not an obstacle for accepting the data elements into USCDI V5.0.
For interoperability, Sex Parameter for Clinical Use needs a value set identified.

8

USCDI v5, Sex for Clinical Use data element  (Substantive) The SFCU data element is not widely implemented. Recommend removing the independent SFCU data element. As element use matures consider SFCU use with USCDI context-specific data elements such as Clinical Tests, Diagnostic Imaging, Laboratory, and Procedures.  
 

9

USCDI v5, Pg 5 (Administrative) Concur with additions to Data Class Provenance:
--Author
--Author Role
Currently supported in HL7 C-CDA R2.1 which allows for faster adoption by implementers for document, or query-based exchange, (versus waiting for HL7 to create mapping or new templates).

Administrative

USCDI V5.0 

10

Pg 5

VHIE

Concur with additions to Data Class Laboratory:
--  Test Kit Unique Device Identifier
Currently supported in HL7 C-CDA R2.1 which allows for faster adoption by implementers for document, or query-based exchange, (versus waiting for HL7 to create mapping or new templates).

11

USCDI v5, Pg 5 (Substantive) Do Not Concur with addition of New Data Class Order:
There is not enough explanation about how this differs from Observations,
or how it differs from an Observation, or to other clinical concpet where the status is some version of not complete.

12

Other Draft USCDI v5 Changes (ONC HEALTH IT STANDARDS BULLETIN January 2024), Pg 7 (Substantive) Concur with Encounter Location would include National Healthcare Safety Network (NHSN) Healthcare Facility 
Patient Care Location (HSLOC)
Value set needs identified.

13

Other Draft USCDI v5 Changes (ONC HEALTH IT STANDARDS BULLETIN January 2024), Pg 7 (Administrative) Concur with Procedures would include a clarification that Code on Dental Procedures and Nomenclature (CDT) 
may be exchanged. 

14

Other Draft USCDI v5 Changes (ONC HEALTH IT STANDARDS BULLETIN January 2024), Pg 7 (Administrative) Concur with Immunizations would update two applicable vocabulary standard citations

15

Other Draft USCDI v5 Changes (ONC HEALTH IT STANDARDS BULLETIN January 2024), Pg 7 (Administrative) Author and Author Role 
ONC seeks feedback on the new Author and Author Role data elements that would be added to the 
Provenance data class, specifically, whether there is sufficient implementation across health IT 
developers. For VA CCDA documents generated from the Legacy VDIF platform and for VA CCDA documents generated from the new FEHR Millennium platform, Author (specific provider name) is populated less often than Authoring Organization.  From my understanding, Provenance contributes to the level of trustability regarding the source of the data.  From that perspective, systems would begin with assigning trustability by source organization and then possibly move to assigning trust at the person level.

16

Other Draft USCDI v5 Changes (ONC HEALTH IT STANDARDS BULLETIN January 2024), Pg 7 (Administrative) Lot Number
ONC seeks feedback on the new Lot Number data element - Specifically, we are interested in feedback on whether Lot Number may apply more broadly to medications. 
For medications entered in the Legacy VA EHR, Lot Number is not captured on a prescription.
FoFor medications entered in the new Federal EHR (Cerner Millennium), Lot Number is not captured on a dispensed medication.

 

ONC Update to Current Dental Terminology (CDT)

The FEHRM Digital Health Standards advocated and represented Military Health, the American Dental Association, Indian Health Services, Dental and patient communities, and Standards Developing Organizations (HL7) by requesting that ONC require the software vendors to use the current procedure codes for dental-related services (CDT). The ONC honored the request and updated the language in the proposed national interoperability policy Draft USCDI version 5 to add CDT to use in any certified health I.T. to exchange information about dental-related procedures. We appreciate ONC Standard's teamwork with the FEHRM collaboration. ONC has proven very responsive to interoperability requirements and how the above request will improve health outcomes. 

http://build.fhir.org/ig/HL7/dental-data-exchange/

ONC Update to Current Dental Terminology (CDT)

The FEHRM Digital Health Standards advocated and represented Military Health, the American Dental Association, Indian Health Services, Dental and patient communities, and Standards Developing Organizations (HL7) by requesting that ONC require the software vendors to use the current procedure codes for dental-related services (CDT). The ONC honored the request and updated the language in the proposed national interoperability policy Draft USCDI version 5 to add CDT to use in any certified health IT to exchange information about dental-related procedures. We appreciate ONC Standard's teamwork with the FEHRM collaboration. ONC has proven very responsive to interoperability requirements and how the above request will improve health outcomes. 

Data element recommendations to improve diagnosis quality

Thank you for the opportunity to provide comments and feedback on data elements for inclusion into United States Core Data for Interoperability (USCDI). The National Quality Forum (NQF) has identified a foundational set of priority data elements that support diagnostic excellence. These data elements, when standardized and made interoperable, have the potential to enhance the quality of diagnoses and the diagnostic process. Please see NQF comments and recommended list of initial priority data element recommendations to measure and improve diagnosis quality here at https://www.qualityforum.org/WorkArea/linkit.aspx?LinkIdentifier=id&ItemID=98503.

Core Data extends beyond clinical data

As noted in comments on 2021-02-02 for USCDIv2, the value of USCDI to healthy but unengaged patients is dependent on core administrative data. For this reason, we applaud the inclusion of Orders as a key indicator of planned and completed care.

We urge the ONC to go further. Inclusion of planned encounters (Appointments) and financial data (ExplanationOfBenefit, ChargeItem) will be hugely beneficial to provide the services and tools patients and providers need.

‘Vital sign results: date and timestamps' promotion from Level 2

The Connected Health Initiative appreciates the opportunity to provide public comment in support of promoting ‘Vital sign results: date and timestamps’ from Level 2 to the draft USCDI v5.

In the Standards Bulletin, July 2023, ONC noted the need of for additional information related to average blood pressure: "ONC received significant input and support for Average Blood Pressure over several USCDI version update cycles. Average Blood Pressure is recognized as an independent risk factor in many diseases and health conditions... The time period, number of readings, and specific protocols may be needed to interpret an Average Blood Pressure value." (Source: ONC Health IT Standards Bulletin, July 2023. https://www.healthit.gov/sites/default/files/page/2023-07/Standards_Bulletin_2023-2.pdf)

Rather than suggesting new data elements specific only to average blood pressure and to reduce the burden on certified health IT companies, the vital sign results: date and timestamps data element could be utilized to provide context for a documented average blood pressure.

Several others have previously commented on the usefulness of vital sign results: date and timestamps specifically related to average blood pressure. They note that in order for average blood pressure to be useful it must include all the metadata to provide the context for interpretation.  

The Connected Health Initiative requests that ONC promote Vital sign results: date and timestamps and include it in the draft USCDI v5.

Recommendations for USCDI v5

We appreciate the opportunity to submit comments on the standardized health data classes and constituent data elements eligible for promotion to version 5 of the USCDI.  As we look to version 5 of USCDI and those items that will enable individuals to express the things that will allow them to ensure systems make the information available across care settings that are most impactful to their healthcare experience, ADVault strongly recommends that the following health data classes and constituent data elements, including clarifications to their naming convention, be included. 

USCDI Draft v5 Comments_ADVault 09202023.pdf