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 about 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.
-
- Usage note: Clinical Notes data elements are content exchange standard agnostic. They should not be interpreted or associated with the structured document templates that may share the same name.
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.
Data used to categorize individuals for identification, records matching, and other purposes.
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.
Unique identifier(s) for a patient's implantable device(s).
Physiologic measurements of a patient that indicate the status of the body’s life sustaining functions.
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 about 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.
-
- Usage note: Clinical Notes data elements are content exchange standard agnostic. They should not be interpreted or associated with the structured document templates that may share the same name.
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.
Data used to categorize individuals for identification, records matching, and other purposes.
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.
Unique identifier(s) for a patient's implantable device(s).
Physiologic measurements of a patient that indicate the status of the body’s life sustaining functions.
USCDI V3
Please read the USCDI v3 standard document and the ONC Standards Bulletin 22-2 for details. Consistent with EO 14168 and OPM guidance, ASTP/ONC is exercising enforcement and issuing certification guidance for the ONC Health IT Certification Program with respect to certain data elements in USCDI v3. For more information see https://www.healthit.gov/topic/uscdi-v3-data-elements-enforcement-discretion.
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 about 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.
-
- Usage note: Clinical Notes data elements are content exchange standard agnostic. They should not be interpreted or associated with the structured document templates that may share the same name.
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.
Data related to an individual’s insurance coverage for health 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.
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.
Data used to categorize individuals for identification, records matching, and other purposes.
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.
Unique identifier(s) for a patient's implantable device(s).
Physiologic measurements of a patient that indicate the status of the body’s life sustaining functions.
USCDI V3.1
Please read the USCDI v3.1 standard document and the ONC Standards Bulletin 22-2 for details. USCDI version 3.1 updates USCDI version 3 with the following changes: consistent with Executive Order 14168, the Sex, Sexual Orientation, and Gender Identity data elements have been removed or updated in the Patient Demographics/Information Data Class.
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 about 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.
-
- Usage note: Clinical Notes data elements are content exchange standard agnostic. They should not be interpreted or associated with the structured document templates that may share the same name.
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.
Data related to an individual’s insurance coverage for health 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.
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.
Data used to categorize individuals for identification, records matching, and other purposes.
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.
Unique identifier(s) for a patient's implantable device(s).
Physiologic measurements of a patient that indicate the status of the body’s life sustaining functions.
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 about 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.
-
- Usage note: Clinical Notes data elements are content exchange standard agnostic. They should not be interpreted or associated with the structured document templates that may share the same name.
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.
Data related to an individual’s insurance coverage for health 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.
Analysis of clinical specimens to obtain information about the health of a patient.
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.
Data used to categorize individuals for identification, records matching, and other purposes.
Information that guides 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.
USCDI V5
USCDI v5 was published on July 16, 2024, and includes 16 new data elements and two new data classes. Please read the USCDI v5 standard document and the ONC Standards Bulletin 24-2 for details.
Harmful or undesired physiological responses associated with exposure to a substance.
Information about 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.
-
- Usage note: Clinical Notes data elements are content exchange standard agnostic. They should not be interpreted or associated with the structured document templates that may share the same name.
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.
Data related to an individual’s insurance coverage for health 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.
Analysis of clinical specimens to obtain information about the health of a patient.
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 request for the delivery of patient care services.
Usage notes: Orders convey a provider’s intent to have a service performed on or for a patient, or to give instructions on future care.
Data used to categorize individuals for identification, records matching, and other purposes.
Information that guides 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.
USCDI V6
ASTP/ONC published USCDI v6 on July 24, 2025, which includes 6 new data elements. Please read the USCDI v6 Standard Document and the ASTP/ONC Standards Bulletin 25-2 for details. ASTP/ONC welcomes input on future versions during the USCDI feedback period, open through September 29, 2025, at 11:59 PM ET. During this time, ASTP/ONC is accepting new data element submissions through ONDEC, and comments on existing data elements may be entered via the updated commenting feature on the USCDI data element pages.
Harmful or undesired physiological responses associated with exposure to a substance.
Information that guides treatment of the patient and recommendations for future treatment.
Information about 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.
-
- Usage note: Clinical Notes data elements are content exchange standard agnostic. They should not be interpreted or associated with the structured document templates that may share the same name.
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.
Family member health condition(s) that are relevant to a patient's care.
Desired state to be achieved by a person or a person’s elections to guide care.
Data related to an individual’s insurance coverage for health 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.
Analysis of clinical specimens to obtain information about the health of a patient.
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.
Provider-authored request for the delivery of patient care services.
Usage notes: Orders convey a provider’s intent to have a service performed on or for a patient, or to give instructions on future care.
Data used to categorize individuals for identification, records matching, and other purposes.
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.
- 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.
Physical place of available services or resources.
Data related to an individual’s insurance coverage for health care.
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.
Provider-authored request for the delivery of patient care services.
Usage notes: Orders convey a provider’s intent to have a service performed on or for a patient, or to give instructions on future care.
Data used to categorize individuals for identification, records matching, and other purposes.
Activity performed for or on a patient as part of the provision of care.
Physiologic measurements of a patient that indicate the status of the body’s life sustaining functions.
- 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.
-
- Usage note: Clinical Notes data elements are content exchange standard agnostic. They should not be interpreted or associated with the structured document templates that may share the same name.
Physical place of available services or resources.
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.
Data used to categorize individuals for identification, records matching, and other purposes.
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.
- 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
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.
Information about 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.
-
- Usage note: Clinical Notes data elements are content exchange standard agnostic. They should not be interpreted or associated with the structured document templates that may share the same name.
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.
Health data as reflected in a patient's Explanation of Benefits (EOB) statements, typically derived from claims and other administrative data.
Desired state to be achieved by a patient.
Desired state to be achieved by a person or a person’s elections to guide care.
Data related to an individual’s insurance coverage for health 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.
Analysis of clinical specimens to obtain information about the health of a patient.
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 request for the delivery of patient care services.
Usage notes: Orders convey a provider’s intent to have a service performed on or for a patient, or to give instructions on future care.
Data used to categorize individuals for identification, records matching, and other purposes.
Information that guides 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.
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
Submitted by JPHIT on
JPHIT USCDIv6 Comments
The Joint Public Health Informatics Taskforce (JPHIT) welcomes the opportunity to comment on USCDI v6. Please find our comments attached below.
Submitted by peter.yochum@va on
FEHRM Feedback on Draft USCDI V6
May 9, 2025
Mr. Steven Posnack
Acting Assistant Secretary for Technology Policy
Office of the Assistant Secretary for Technology Policy and Office of the National Coordinator for Health Information Technology (ASTP/ONC)
Department of Health and Human Services
Hubert Humphrey Building, Suite 729
200 Independence Avenue SW
Washington, DC 20201
Re: ASTP’s Request for Comments on United States Core Data for Interoperability Version 6
Acting Assistant Secretary Posnack,
The Federal Electronic Health Records Modernization (FEHRM) Program Office appreciates this opportunity to review and provide feedback on ASTP/ONC’s United States Core Data for Interoperability Version 6. The FEHRM surveyed subject matter experts at the Department of Defense (DOD) and the Veteran’s Administration (VA) in compiling these comments.
Please consider adding the following considerations for the revised data classes and elements in this version of USCDI:
1. Recommend there be two data elements, (Unique Device Identifier—Implantable and Unique Device Identifier—Non-implantable), to ensure clinicians receive the most specific information as possible.
Use Case: A clinician is sorting through a patient's chart for the types of medical devices. Rather than sort through numerous devices, the distinction of implantable versus non-implantable will allow the clinician to filter through the data more efficiently.
2. Recommend adding Allergy Severity as a separate data element or a sub-category to the Allergy Reaction. Additionally, recommend adding Allergy Criticality as a new data element. Both recommended data elements are commonly exchanged in the industry and valuable clinical information.
Use Case: A patient has a severe allergy to latex. However, without allergy severity the clinician is unable to document and must use a free-text comment field. The receiving system does not display free-text comments and the receiving system's clinicians do not receive the patient's allergy severity. The same can be said for criticality.
3. Recommend support with an additional consideration of inpatient/outpatient situations (e.g., bedside, patient wearable)
Use Case: If patient diabetic wearable reading and also a lab draw reading, how to differentiate.
4. Recommend a clear definition of the segments of the Unique Identification (ID) (e.g., National Drug Code) with segments clearly identifying manufacture device, type, serial number, model, etc.
Use Case: an operational /clinical/regulatory user can parse the ID for expanded focused reports that identifies a specific company, device type, device model, etc.
5. Recommend a standardized set of section labels so that Artificial Intelligence (AI) and Natural Language Processing (NLP) can parse appropriately. The value of codified data will inform actionable insights
Use Case: NLP can locate a section data element label for the consistent reporting and analysis.
6. Recommend a SNOMED CT identifier for Date of Onset. To be practical, there is a need to define a default date format if patient reported date is not exact. Guidance is needed on format of a default date (e.g., 01/01/2025)
Use Case: the patient is asked for the date of onset of leg pain that started in 2025 but does not remember the exact date.
7. Recommend a codified structure for family health history to support future AI and NLP requirements (e.g., standardized data labels)
Use Case: by identifying the data element with a data label, AI algorithms can identify trends in chronic diseases across the family members.
8. Recommend constraining the applicable vocabulary standards in the Family History class to only SNOMED CT. As the draft notes in its submission text, “Current users of 552 products of health information technology certified to the ONC 2015 or Cures Update to 2015 certification criteria: The health IT permits users to record, change, and access a patient’s family health history according to the September 2015 Release of SNOMED CT®, U.S. Edition.” Adding ICD-10-CM as an applicable standard significantly increases the inbound (receiver side) interoperability burden, typically requiring the receiving systems to implement and maintain maps and rules, while not materially improving the coverage of likely family history data.
We appreciate the opportunity to comment on this updated version of USCDI. Please feel free to contact us if you have any questions or would like any further information.
Regards,
Charles Gabrial
Digital Health Standards Lead
Federal Electronic Health Record Modernization (FEHRM) Office
Submitted by AnthonyCorso on
Veeva Comments on Draft USCDI V6
On behalf of Veeva Systems, please see the attached comments.
Submitted by jessilott on
Tennessee Department of Health
May 9, 2025
Steven Posnack, MS, MHS
Acting Assistant Secretary for Technology Policy, Acting National Coordinator for Health Information Technology
Department of Health and Human Services
Hubert Humphrey Building, Suite 729
200 Independence Avenue SW
Washington, DC 20201
RE: Draft USCDI Version 6
Dear Mr. Posnack,
The Tennessee Department of Health (TDH) Office of Informatics and Analytics (TDH-OIA) appreciates the opportunity to share comments on Version 6 the United States Core Data for Interoperability Version 6 (USCDI v6). TDH is the primary public health agency responsible for public health in Tennessee. The department oversees eighty-nine rural county health departments and works closely with six metropolitan health departments under local governance to carry out the provision of public health services to people in Tennessee. Each county in Tennessee is served by a county health department providing direct and indirect services to Tennessee residents and visitors. TDH staff participates in many health care and health IT industry organizations, associations, workgroups, and task forces to ensure the needs of public health programs including those that conduct surveillance, outbreak investigations and event response, laboratory testing, and prevention of communicable and non-communicable diseases and conditions in Tennessee are heard.
The mission of the Tennessee Department of Health is to protect, promote and improve the health and prosperity of people in Tennessee. The TDH has a great deal of interest in the widespread adoption and use of nationally accepted standards and requirements that increase data sharing, improves timely reporting and accuracy, that enforces information sharing between the clinical sector and public health. TDH can appreciate ONC’s effort for its development of the USCDI as the foundation of data elements and classes that all electronic health record technology should be able to collect, analyze and share between providers. Once broadly adopted, the USCDI will lead to improved interoperability and health data exchange, enabling better care coordination, improved health for patients and lower costs.
TDH-OIA strongly supports comments submitted by the Council of State and Territorial Epidemiologists (CSTE). Specifically, we support the previous CSTE comments regarding confusion with including “intent” in the “Pregnancy Status” data element definition. We recommend considering a separate data element to capture information regarding pregnancy intent more accurately.
Additionally, we support the newly proposed addition of Facility Address and Facility Information.
We would also like to offer for consideration the addition of data elements “Ordering Facility” and “Performing Facility” to increase clarity when reviewing information related to lab specimens. This information is especially important for public health programs that use the details for reporting and investigations.
Again, TDH-OIA is appreciative of ASTP’s efforts and are thankful for the opportunity to comment. If there are any questions or concerns, please reach us at TDH.Informatics@tn.gov.
Submitted by rbaker@cdisc.org on
CDISC Response on ASTP USCDI v6 Draft
CDISC welcomes the opportunity to submit comments on ASTP's draft USCDI v6. Please see the attached comments.
Submitted by Erin_ORourke_AHIP on
AHIP Comments on Draft USCDI V6
Dear Mr. Posnack:
AHIP appreciates the Assistant Secretary for Technology Policy/Office of the National Coordinator for Health Information Technology’s (ASTP/ONC) ongoing work to advance the interoperability of health information through the United States Core Data for Interoperability (USCDI). We agree that a common set of data classes and elements is essential to achieving interoperability between consumers, doctors, hospitals, health plans, and other stakeholders. Patients deserve high-quality, equitable, and affordable care delivered by health care providers and health plans who are working together— that includes sharing the data patients and their doctors need to make informed health care decisions. With this goal in mind we are pleased to offer the following comments on the draft USCDI v6.
Data Class: Health Insurance Information
We continue to be concerned that several data elements in the Health Insurance Information data class do not exist or risk exposing personally identifiable information without providing value to consumers.
The USCDI should not contain elements that have no associated value set or national standard, but rather only include information that is feasible to collect and has a specific use case. ONC should remove the payer identifier data element as there is no broadly used national standard for this data element.
The privacy and security of member data is a paramount responsibility and a major concern for health plans and the consumers they serve. While this information may be robustly protected when held by a physician, hospital, or health insurance provider, the data are outside the reach of the Health Insurance Portability and Accountability Act (HIPAA) once shared through the API to third-party applications per the ONC Cures Act Rule or the Centers for Medicare & Medicaid Services Interoperability and Patient Access Rule. Moreover, all USCDI data elements are required to be shared with the selected third-party applications under the CMS rules— there is no data segmentation opportunity to pull out elements that the patient may consider sensitive.
For the Health Insurance Information data class, the data elements include identifiers (ID) of not only the patient but also their spouse or parent (if they are the subscriber) and where they are employed. While the patient ID may be useful in the EHR to match information with practice management systems or payer claims information, this sort of detailed benefit information does not provide clinically relevant or even intelligible information for third party applications unless the identifier is also the patient’s social security number. Moreover, it is information consumers already know, so they do not need to access it through a third party. However, in the hands of third-party applications via the Patient Access API, the information could be used to identify someone in a different data set, make associations with other people in other data sets, or even re-identify a de-identified data set. Thus, while there may be important reasons to share some of this data among HIPAA covered entities, sharing it with entities outside of HIPAA exposes patients to risk without material benefit.
To remedy this threat CMS and ASTP/ONC should reconsider the automatic link between the USCDI and the Patient Access API. Instead, each data element for the purposes of standardizing EHR data should be weighed separately from whether it should be shared with third-party applications that are not covered by HIPAA. Otherwise, we are providing patients with a false choice: access the data they need to make informed choices, or risk potential exposure of sensitive information. Until then, ONC should remove the following data elements to protect consumer privacy:
- Member identifier,
- Subscriber identifier,
- Relationship to subscriber,
- Group identifier.
ONC could focus the Health Insurance Information data class, in the meantime, on higher level elements such as whether the person has insurance coverage and the type of coverage. This could help third-party applications determine if information and support is available from a health insurer or whether, for example, cost estimates for the uninsured would be of use.
Data Class: Facility Information
We support the addition of the Facility Address data element. This data element will provide important information necessary to identify facilities and link service and outcome data to a specific physical institution or facility. Currently, it can be challenging to differentiate specific service locations and link data or records for purposes such as quality measurement. Accurate facility information, including name, address, and identifier will facilitate the transition to digital quality measurement and help public payers and health plans more accurately understand the quality of care offered at specific facilities, rather than overall quality at a system level.
Data Class: Problems
AHIP supports the addition of the Date of Onset data element. This data element will capture important information about the onset of symptoms, timing, and potential triggers to support better diagnosis and case management. This data element also serves an important public health function to help track disease outbreaks.
We are concerned about the addition of the Family Health History Data element. While we appreciate the impact of genetics and the potential clinical value of this information, we are concerned that including this data element in USCDI could jeopardize patient privacy and the privacy of a patient’s family members who may not have consented to having this information shared.
As noted above, AHIP continues to be concerned about the risk to patient privacy posed by third-party applications that are not covered by HIPAA. These new entities can be collecting, using, disclosing, and disseminating consumer health data for the purpose of monetizing it, and yet consumers are generally unaware that the data are outside these regulatory protection frameworks. AHIP continues to be very concerned about the potential for bad actors to exploit data gained via the APIs and the potential consequences for patients and their families. This risk grows exponentially as additional data elements are required to be shared with third-party apps not governed by the health care privacy legal requirements. For example, sensitive patient data, at an individually identifiable level, shared by a payer with an app developer under CMS required policies can be freely sold or disclosed as long as it is noted in the consumer terms and agreement provided by the app (which can be changed at any time).
The privacy and security of member data is a paramount responsibility and a major concern for health plans and the consumers they serve. Until more robust privacy protections are extended to third-party applications ASTP/ONC should be judicious about adding data elements to USCDI. As noted above, ASTP/ONC should also consider that instead of adopting versions of the USCDI wholesale for sharing via the CMS required APIs, CMS and ASTP/ONC should consider the contribution of each data element and whether it is necessary to share through the Patient Access API and expose to the risk of passing to a third-party app that is not covered by HIPAA.
Future Directions: Support Digital Quality Measurement
We appreciate ASTP/ONC’s efforts to coordinate with the Core Quality Measures Collaborative (CQMC) and build on the CQMC’s work when developing the USCDI+ Quality. Aligned measures based on interoperable data have the potential to reduce the burden on clinicians and providers while providing all stakeholders more robust information on performance. We strongly encourage ASTP/ONC to continue to collaborate with the CQMC when updating the USCDI+ Quality in the future and prioritize the data elements necessary to calculate the CQMC core measures for future versions. However, ASTP/ONC should also add data elements necessary to calculate digital quality measures in the baseline USCDI to ensure they are available for all payers and health care providers to use.
Additionally, we urge ASTP/ONC to include data elements for high-value measures beyond CMS programs in the USCDI and the USCDI+ Quality. For example, ASTP/ONC should add data elements to support the exchange of data to support the National Committee for Quality Assurance (NCQA)’s HEDIS measures to support aligned measures across public and private payers. ASTP/ONC should also prioritize high-value but high burden measures such as patient experience measures, patient-reported outcomes-based performance measures (PRO-PMs), and social needs screening measures where digital measurement could materially advance their use and facilitate the exchange of person-centered data. Promoting the interoperability of patient-generated data could allow for it to be used across the system while reducing the response burden on patients.
AHIP and its members look forward to working with ASTP/ONC to continue to advance interoperability to empower patients and support patient care. If you have any questions, please contact me at dlloyd@ahip.org.
Sincerely,
Danielle A. Lloyd, MPH
Senior Vice President, Private Market Innovations and Quality Initiatives
Submitted by mrallins on
Regenstrief Institute Comments on Draft USCDI v6
The Regenstrief Institute welcomes the opportunity to submit the attached comments on ASTP’s Draft United States Core Data for Interoperability (USCDI) Version 6 and related data classes standards and elements. Our comments for USCDI v6, are intended to augment the USCDI with critical input and support its use in facilitating information exchange and interoperability goals. We appreciate and look forward to continued collaboration with ASTP.
USCDI v6 Cover Letter, Comments_Regenstrief_2025-05-07_FINAL.pdf
Submitted by mturchioe on
Alliance for Nursing Informatics comments on draft USCDI v6
On behalf of the Alliance for Nursing Informatics, please see the attached comments.
Submitted by pross@jointcom… on
USCDI Draft v6
On behalf of The Joint Commission, please see the attached comments.
2025_04_14_The Joint Commissions Comments_ASTP_USCDI draft v6.pdf
Help
1. Optional: Background Text / Cover Letter
The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.
If you wish to provide context, explanation, or an introduction to your comment, enter this information in the field labeled "Optional Background Text / Cover Letter." This is entirely optional and is most useful when submitting multiple related comments or when additional background would help reviewers understand your feedback.
If you are only commenting on a single data class or element, you may leave this field blank.
2. Select the Data Class
To specify which data class your comment addresses:
- In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
- If you are providing a general comment that is not specific to a data element, select "General" from the options. Comments with this designation will be displayed on the USCDI landing page.
- Note that the Data Class field will automatically populate based on your current location in the platform:
- If you are on a data class page, the field will be set to that specific data class
- If you are on a data element page, the corresponding data class will be pre-selected
3. Select the Data Element
To specify which data element your comment addresses:
- In the "Data Element" drop-down menu, select the specific data element you want to comment on.
- The drop-down menu will display only the elements available under the data class you selected in the previous step.
- You can use the search function within the drop-down to quickly locate a specific data element.
- If you are commenting on the data class itself rather than a specific element, you may leave this field blank.
Note: Comments on a specific data element will appear on the respective data element page, while comments on a data class (without a specific element selected) will appear on the landing page for that data class.
Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.
4. Optional: Propose New Data Class or Element
If you cannot find the appropriate data class or element for your comment:
- Instead of clicking the "Comment On An Existing Data Class Or Element" button, click the adjacent button labeled "Propose a New Data Class or Data Element."
- This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
- In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
- Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Fig 2 The "Propose a New Data Class or Data Element" button redirects users to the ONDEC Submission System for proposing new data elements not currently available in the system.
5. Complete the Comment Form
Fill out the required fields in the comment form:
Subject: Enter a brief, descriptive title that summarizes your comment. This helps reviewers quickly understand the nature of your feedback.
Comment: In this field, provide the full details of your comment or feedback. Be as clear and specific as possible about your suggestions, concerns, or observations. Include any relevant details that support your position.
6. Optional: Add Additional Comments
If you need to comment on multiple data classes or elements:
- After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
- A new comment section will appear, allowing you to enter details for your additional comment.
- For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
- Complete the Subject and Comment fields for your additional comment.
- Repeat this process for each additional comment you wish to submit.
Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.
7. Optional: Upload Supporting Files
The platform allows you to upload supporting documentation to enhance your comment:
- Locate the "File Upload" section at the bottom of the comment form.
- Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.
Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.
Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.
8. Optional: Save and Exit
If you need to pause your work and return to complete your comment later:
- Click the "Save and Exit" button at the bottom of the form.
- Your comment will be saved as a draft that you can access and complete later.
- When you return to the platform, you will see a red triangle with an exclamation mark next to the “Return to saved Comment” button, indicating that you have saved comments in draft status.
- Click this button to continue working on your draft.
- You will be taken to a review page where you can:
- Select "Submit Comment" to officially submit your feedback.
- Click "Edit" to return to the comment form and make changes
- Select "Discard Draft" to delete the saved draft and start fresh
Fig 5 A red triangle with exclamation mark indicator appears next to the “Return to saved Comment” button when draft comments are saved in the system.
9. Review and Submit
Once you have completed your comment:
- Click the "Review and Submit" button at the bottom of the form.
- This will take you to a review screen displaying your comment(s) in full.
- Review all information for accuracy and completeness.
- On this review screen, you have three options:
- Click "Submit Comment" to officially submit your feedback
- Click "Edit" to return to the comment form and make changes
- Click "Discard Draft" to delete the comment and start fresh
- The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records.
- If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.
Submitted by melanie.kourba… on
APHL Comments on USCDI V6
The Association of Public Health Laboratories (APHL) welcomes the opportunity to comment on USCDI v6. Please find our comments attached.
APHL USCDI V6 Comments 20250512.pdf