Printer Friendly, PDF & Email

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 various Data Elements by a common theme or use case.

A USCDI “Data Element” is the most granular level at which a piece of data is exchanged.

For example, Date of Birth is a Data Element rather than its component Day, Month, or Year, because Date of Birth is the unit of exchange.

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

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

Allergies and Intolerance Allergies and Intolerances Represents harmful or undesirable physiological response associated with exposure to a substance.

Assessment and Plan of Treatment Assessment and Plan of Treatment Represents a health professional’s conclusions and working assumptions that will guide treatment of the patient.

Care Team Member(s) Care Team Member(s) The specific person(s) who participate or are expected to participate in the care team.

Clinical Notes Clinical Notes Composed of both structured (i.e. obtained via pick-list and/or check the box) and unstructured (free text) data. A clinical note may include the history, Review of Systems (ROS), physical data, assessment, diagnosis, plan of care and evaluation of plan, patient teaching and other relevant data points.

Goals Goals An expressed desired health state to be achieved by a subject of care (or family/group) over a period of time or at a specific point of time

Health Concerns Health Concerns 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.

Immunizations Immunizations Record of an administration of a vaccination or a record of a vaccination as reported by a patient, a clinician, or another party.

Problems Problems Information about a condition, diagnosis, or other event, situation, issue, or clinical concept that is documented.

Procedures Procedures An activity that is performed with or on a patient as part of the provision of care.

Provenance Provenance The metadata, or extra information about data, that can help answer questions such as when and who created the data.

Smoking Status Smoking Status Classification of a patient’s smoking behavior.

Unique Device Identifier Unique Device Identifier(s) for a Patient’s Implantable Device(s) A unique numeric or alphanumeric code that consists of a device identifier (DI) and a production identifier (PI).

The Draft USCDI v2 contains data classes and elements from USCDI v1 and new data classes and elements submitted through the ONDEC system. Public comments will be accepted on this page or on any data class or element pages below until April 15, 2021. Please reference the Draft USCDI version 2 document to the left for applicable standards versions associated with Draft USCDI v2.

Allergies and Intolerance Allergies and Intolerances Represents harmful or undesirable physiological response associated with exposure to a substance.

Assessment and Plan of Treatment Assessment and Plan of Treatment Represents a health professional’s conclusions and working assumptions that will guide treatment of the patient.

Care Team Member(s) Care Team Member(s) The specific person(s) who participate or are expected to participate in the care team.

Clinical Notes Clinical Notes Composed of both structured (i.e. obtained via pick-list and/or check the box) and unstructured (free text) data. A clinical note may include the history, Review of Systems (ROS), physical data, assessment, diagnosis, plan of care and evaluation of plan, patient teaching and other relevant data points.

Goals Goals An expressed desired health state to be achieved by a subject of care (or family/group) over a period of time or at a specific point of time

Health Concerns Health Concerns 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.

Immunizations Immunizations Record of an administration of a vaccination or a record of a vaccination as reported by a patient, a clinician, or another party.

Problems Problems Information about a condition, diagnosis, or other event, situation, issue, or clinical concept that is documented.

Procedures Procedures An activity that is performed with or on a patient as part of the provision of care.

Provenance Provenance The metadata, or extra information about data, that can help answer questions such as when and who created the data.

Smoking Status Smoking Status Classification of a patient’s smoking behavior.

Unique Device Identifier Unique Device Identifier(s) for a Patient’s Implantable Device(s) A unique numeric or alphanumeric code that consists of a device identifier (DI) and a production identifier (PI).

In addition to “Comment” and “Level 1” criteria, Level 2 data elements demonstrate extensive existing use in systems and exchange between systems, and use cases that show significant value to current and potential users. These data elements would clearly improve nationwide interoperability. Level 2 Data Elements with the flag were prioritized for inclusion in the Draft USCDI v2, now available for public review. ONC encourages public comment through the USCDI home page on all Level 2 data classes and elements as well as the Draft USCDI v2 as a whole. Comments will be accepted through April 15, 2021.

Allergies and Intolerance Allergies and Intolerances Represents harmful or undesirable physiological response associated with exposure to a substance.

Care Team Member(s) Care Team Member(s) The specific person(s) who participate or are expected to participate in the care team.

Immunizations Immunizations Record of an administration of a vaccination or a record of a vaccination as reported by a patient, a clinician, or another party.

Problems Problems Information about a condition, diagnosis, or other event, situation, issue, or clinical concept that is documented.

Procedures Procedures An activity that is performed with or on a patient as part of the provision of care.

Provenance Provenance The metadata, or extra information about data, that can help answer questions such as when and who created the data.

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

In addition to “Comment” level criteria, Level 1 data elements demonstrate limited existing use in electronic systems, limited exchange between systems and more well-defined use cases and value to potential users. There may still be some burdens associated with development and implementation.

Provenance Provenance The metadata, or extra information about data, that can help answer questions such as when and who created the data.

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

A data element designated as "Comment" level is represented by health care standard terminology such as SNOMED CT® or implementation specifications such as HL7® FHIR® 4. It may not have a well-defined use case or value to potential users. There may be significant or unknown burdens associated with development or implementation.

Allergies and Intolerance Allergies and Intolerances Represents harmful or undesirable physiological response associated with exposure to a substance.

Assessment and Plan of Treatment Assessment and Plan of Treatment Represents a health professional’s conclusions and working assumptions that will guide treatment of the patient.

Care Team Member(s) Care Team Member(s) The specific person(s) who participate or are expected to participate in the care team.

Clinical Notes Clinical Notes Composed of both structured (i.e. obtained via pick-list and/or check the box) and unstructured (free text) data. A clinical note may include the history, Review of Systems (ROS), physical data, assessment, diagnosis, plan of care and evaluation of plan, patient teaching and other relevant data points.

Goals Goals An expressed desired health state to be achieved by a subject of care (or family/group) over a period of time or at a specific point of time

Immunizations Immunizations Record of an administration of a vaccination or a record of a vaccination as reported by a patient, a clinician, or another party.

Problems Problems Information about a condition, diagnosis, or other event, situation, issue, or clinical concept that is documented.

Procedures Procedures An activity that is performed with or on a patient as part of the provision of care.

Provenance Provenance The metadata, or extra information about data, that can help answer questions such as when and who created the data.

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

Click to View USCDI V1

Previous USCDI Versions

Click to View Draft USCDI V2

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

How should ONDEC submitters flag Required vs Preferred?

Submissions will be going to USCDI ONDEC system: https://healthit.gov/ONDEC How does HHS ONC recommend submitters flag existing FHIR fields for elements, e.g. clinicalStatus for Allergy Intolerance, as recommending a field to be required, rather than preferred? For this Example, see AllergyIntolerance resource and FHIR, and FHIR coding for clinicalStatus: https://www.hl7.org/fhir/allergyintolerance.html http://hl7.org/fhir/R4/valueset-allergyintolerance-clinical.html In this example, active = Active, inactive = Inactive, resolved = Resolved. For example, clinically, a significant number of patient labelled as 'penicillin allergic' are not truly allergic to the drug.  As a result, these antibiotics can be withheld unnecessarily.  (ref: https://www.pharmaceutical-journal.com/learning/learning-article/penicillin-allergy-identification-and-management/20069170.article ) Thank you. Henry Wei MD Google

flags for submissions

USCDI data elements refer to a system's ability to capture and share a data element.  The referenced flag of "clinical status" would be represented as a unique data element associated with another data element, such as Allergy/Intolerance.  A similar data element, "Medication Usage", has been submitted through ONDEC, to address one aspect of medication status.  ONC would consider a clinical status data element which could be applied to Allergy/Intolerance, but may also be applicable to other classes/elements like Problems, Health Concerns.

USCDI to FHIR Resource Mapping Guide

Hi. Will there be a data spec/map be published to show how data elements are mapped to FHIR resources? 

As USCDI v2 develops, we…

As USCDI v2 develops, we anticipate work will be done to update the mapping from USCDI data elements to US Core Profiles and FHIR resources.  The current mapping of these can be found at https://www.hl7.org/fhir/us/core/general-guidance.html.

Proposal for precise modeling of entities in the USCDI

The USCDI V1 is a landmark specification of core clinical data for nationwide exchange. Recognizing USCDI's significant promise for directing future interoperability efforts, we seek to improve its foundation for continued expansion. In particular, we believe that improving the clarity of USCDI entity definitions (e.g. Data Class, Data Element) are necessary for the industry to interpret them consistently. We seek to add precision to their specifications to enable a principled approach for users to understand, implement, extend, and refine them with future submissions for new USCDI content. To that end, we submit these recommendations, which includes a proposed model that is described in the accompanying appendix.

Proposal for precise modeling of entities in the U.S. Core Data for Interoperability - Version 1.0.pdf

UCSF Center for Digital Health Innovation's Comment on USCDI

Dear Dr. Rucker: The University of California, San Francisco’s Center for Digital Health Innovation provides the attached comments on new data classes and elements for version 2 of the U.S. Core Data for Interoperability.  We appreciate the considerable work that ONC has devoted to the Common Clinical Data Set (CCDS) and its next evolution, the U.S. Core Data for Interoperability version 1.  Version 1, however, was only a “modest expansion” of the Common Clinical Data Set.   As a health care provider, we urge ONC to add numerous additional data elements now so that they, too, become available for better health care, for key national use cases such as COVID-19 and virtual care, and for the nationwide learning health system we need.  According to ONC, technical specifications are already available for 46 of 50 data classes ONC listed for candidate and emerging status, and all 50 are “critical to achieving nationwide interoperability.” To illustrate the importance of adding the missing data elements now, we tested them against two COVID-19 use cases and asked which missing structured data elements are necessary or important now for health care in the midst of the COVID-19 pandemic.  Not surprisingly, most were necessary or important. If you or your staff have any thoughts or questions about these comments, please feel free to contact me at Mark.Savage@ucsf.edu. Yours truly,   Mark Savage   Mark Savage Director, Health Policy Center for Digital Health Innovation University of California, San Francisco   E. Mark.Savage@ucsf.edu C. 415.225.1676 W. www.CenterforDigitalHealthInnovation.org

Support for the Gravity Project's submission on SDOH

Please see the attached letter for Providence St. Joseph Health's support to the Gravity Project's submission for two approaches for including social determinants of health data in the USCDI.

PSJH Gravity support USCDI 10-23-20.pdf

NYeC Support for Gravity Project Submission

The New York eHealth Collaborative (NYeC) supports the inclusion of key social determinants of health (SDOH) data elements as submitted by the Gravity Project in the U.S. Core Data for Interoperability (USCDI) Version 2. New York State has been a leader in requiring interventions and data collection to address SDOH in Value-Based Payment as part of the Medicaid program, which underscores the importance of this work. The Gravity Project’s submissions would add critical domains such as food insecurity, housing instability, transportation insecurity, social isolation, and stress to the USCDI, integrated with core clinical activities such as assessments, diagnoses, interventions, and outcomes. Widespread capturing of standardized SDOH data is critical to understanding and addressing health disparities and improving health outcomes for individuals and communities.

Highmark Health Letter of Support for Gravity Project Submission

This letter is written in support of The Gravity Project’s submission to the Office of the National Coordinator to advocate for the inclusion of Social Determinants of Health (SDOH) in the U.S. Core Data for Interoperability.   As one of the nation’s largest integrated healthcare delivery systems, Highmark Health believes this integration is critical to improve the health and well-being of those we serve.    Public health professionals have long known that social and environmental determinants of health explain most of a person’s and population’s health status.  The health care delivery sector is now understanding that the delivery of traditional health care accounts for only 20% of one’s health.  The COVID-19 pandemic has highlighted this reality daily across the nation.  The Gravity Project’s submissions would add critical domains such as food insecurity, housing instability, transportation insecurity, social isolation, and stress to the USCDI, integrated with core clinical activities such as assessments, diagnoses, interventions, and outcomes.  The need for inclusion of SDOH as a new data class in USCDI is a requisite to capturing social risk and supports a focus on and prioritization of use cases with a high impact on the triple aim, the widely accepted policy objective of HHS that refers to improving the experience of care, improving the health of populations, and reducing per capita costs of health care.  The fact that SDOH accounts for 80 percent of health status at a population level and that there is no consistent method to document and communicate these factors during a health care encounter emphasizes the urgency of a national standard approach across the health care system.  The implementation of these standards is necessary to drive reductions in missed appointments, cost savings from preventable health events, culturally competent care, increased care plan compliance, reduced administrative burden, promoting effective investment in community health programs, and leveraging critical data to improve patient outcomes. Health care’s transition from a fee-for-service model to value-based care adds an additional imperative for SDOH, since these elements will become increasingly necessary to establish appropriate and equitable reimbursement of health care service providers and advance reimbursement models for community based organizations.  Without standards and code sets, health plans will be challenged to evolve their value based reimbursement programs to include social risk. Please accept this recommendation on behalf of Highmark, for The Gravity Project’s submission to the USCDI.  Should you have any questions or need additional insight please don’t hesitate to contact me at (412) 721-6800 or via email at Deborah.donovan@highmarkhealth.org.

Letter of support 12 4 20 DJD Highmark Health. FINAL.pdf

Division of Vital Statistics Support for Death and Birth items

The Division of Vital Statistics (DVS) within CDC’s National Center for Health Statistics (NCHS) supports inclusion of submitted mortality and natality data elements into USCDIv2.  The mortality data elements include Cause of Death Information, Autopsy Performed, and Date and Time pronounced dead.  These mortality data elements requested not only support multiple public health use cases, but they also support the clinical information reported on death certificates. This will inform mortality reporting about public health challenges, determine life expectancy and compare death trends with other countries. The natality data elements include Clinical Notes for Newborn, Pregnancy History, Apgar Score, Estimated Date of Delivery, Gestational Age at Birth, Last Menstrual Period (LMP), Number of Fetal Deaths This Delivery, and Patient Birth Place. Currently there are natality elements that have progressed to level 2, and to compliment the reporting of natality holistically are a reason these Comment Level items should also be included within the Level 2 inclusion.  These data elements track health trends that includes pregnancy risk factors and preterm births. The inclusion of these elements in USCDIv2 would have a significant impact on mortality and natality reporting by reducing the burden of duplicative data entry and streamlining the process flow.  The primary objective is to improve the timeliness, quality, and sustainability of vital statistics reporting.  The inclusion of these elements would not only support national level reporting but also benefit State partners who are the first line of receiving these data and clinical providers who are on the first line of sending these data. DVS has been working with State partners and their electronic registration systems as part of modernization efforts. Inclusion of these elements would support interoperability among the vital statistics ecosystem.  DVS and State partners have been focusing working towards using the HL7 FHIR standards that adhere to the US Core resources within their implementation guides when possible.