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
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 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.
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.
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.
Data used to categorize individuals for identification, records matching, and other purposes.
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.
Draft USCDI V6
ASTP/ONC published Draft USCDI v6 on January 14, 2025, and proposes to add 6 new data elements. Please read the Draft USCDI v6 standard document and the ASTP Standards Bulletin 25-1 for details. ASTP/ONC is accepting comments here through May 12, 2025, at 11:59 PM ET.
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.
Data used to categorize individuals for identification, records matching, and other purposes.
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.
- 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.
Data used to categorize individuals for identification, records matching, and other purposes.
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.
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.
Data used to categorize individuals for identification, records matching, and other purposes.
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.
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 Fresenius Medi… on
FMCNA Comment on USCDI Draft Version 3
Fresenius Medical Care North America (FMCNA) welcomes the opportunity to comment on USCDI Draft version 3. We note there is also a statement of support appended to our letter from eHealth Exchange, the nation’s largest Health Information Network.
Submitted by gthole on
Cerner Corporation USCDI Draft V3 Comments
Cerner Corporation appreciates the opportunity to provide our comments and recommendations on the USCDI Draft V3. Please find our full comment letter attached.
Submitted by michael.e.prevoznik on
Comments for 2022 USCDI V3
Thank you for the opportunity to comment. Quest Diagnostics, Incorporated submits comments in the attached .pdf file.
Submitted by Andrew Tomlins… on
AHIMA Comments on Draft USCDI Version 3
Thank you for the opportunity to submit comments regarding ONC’s request for comment on the United States Core Data for Interoperability (USCDI) Version 3 (January 2022).
AHIMA is a global nonprofit association of health information (HI) professionals. AHIMA represents professionals who work with health data for more than one billion patient visits each year. The AHIMA mission of empowering people to impact health drives our members and credentialed HI professionals to ensure that health information is accurate, complete, and available to patients and clinicians. Our leaders work at the intersection of healthcare, technology, and business, and are found in data integrity and information privacy job functions worldwide.
AHIMA appreciates ONC’s continued work to develop and implement robust data standards to be used across all of health information technology. The USCDI is a roadmap to moving to a more interoperable and open patient centered health system. Version 3 of the USCDI continues to build on the foundation laid by both Versions 1 and 2 by pushing the adoption of data standards further down the maturity pathway. Version 3 proposes several new data classes and elements, actions AHIMA has previously provided comment on and will continue to support now and into the future.
AHIMA offers general comments on specific elements and classes followed by more detailed comments in response to certain questions contained within Standards Bulletin 2021-3 in our attached comment letter.
Submitted by jkegerize on
American Clinical Laboratory Assoc. Comments on USCDI Draft V3
April 18, 2022
Micky Tripathi, PhD, MPP National Coordinator for Health Information Technology Office of the National Coordinator for Health Information Technology U.S. Department of Health and Human Services 330 C St SW, Floor 7 Washington, DC 20201
Re: United States Core Data for Interoperability (USCDI) v3 [Draft for Comment]
Dear Dr. Tripathi,
The American Clinical Laboratory Association (ACLA) is pleased to submit our comments in response to the United States Core Data for Interoperability (USCDI) v3 [Draft for Comment] (hereinafter the “Draft”). We appreciate the opportunity to comment on the Draft Version 3.
ACLA is the national trade association representing leading laboratories that deliver essential diagnostic health information to patients and providers. ACLA members are at the forefront of driving diagnostic innovation to meet the country’s evolving health care needs and provide vital clinical laboratory tests that identify and prevent infectious, acute, and chronic disease. ACLA works to advance the next generation of health care delivery through policies that expand access to lifesaving testing services.
ACLA applauds your leadership in releasing the Draft in order to further advance health information technology (HIT) interoperability, a critical and vital goal for improving the quality of care for patients. ACLA member laboratories appreciate the opportunity to comment on the Draft and hope these comments serve to continue to move interoperability forward.
We thank ONC for its consideration of our comments. Please contact me at 202-637-9466 or jkegerize@acla.com with any questions.
Sincerely,
Joan Kegerize
Vice President for Reimbursement & Scientific Affairs
ATTACHMENT: ACLA COMMENTS
The following comments are submitted by the American Clinical Laboratory Association:
Thank you for the opportunity to comment on the USCDI v3.
Proposed USCDI V3 Additions for Laboratory Data Class:
Laboratory/Specimen Type
https://www.healthit.gov/isa/taxonomy/term/2491/draft-uscdi-v3
Data Element:
Specimen Type Type of specimen (e.g., nasopharyngeal swab, whole blood, serum, urine, wound swab) on which a lab test is performed.
Original Submission:
From CDC: | Interoperability Standards Advisory (ISA) (healthit.gov)
ACLA Comment:
These comments pertain to the “Applicable Vocabulary Standard(s)” which might be named in future USCDI versions.
The original submission from CDC specifies LOINC as an applicable standard, however the hyperlink is to PHINVADs vocabulary “hot topics” page: If you search for “Specimen Type” there are at least 13 different value sets for Specimen Type. If/when ONC cites vocabulary standard(s), please provide a hyperlink which is a direct link to the applicable vocabulary.
The CDC submission also references Supporting Artifacts which “…are standard elements in HL7 laboratory messaging: https://www.cdc.gov/elr/index.html”.
HL7’s electronic laboratory reporting (ELR) Implementation Guide that was cited for Meaningful Use Stage 1: “HL7 Version 2.5.1 Implementation Guide: Electronic Laboratory Reporting to Public Health, Release 1 (US Realm)”. The ELR requires V2.5.1 HL7 Table 0487 for Specimen Type table, which is obviously not LOINC codes. This inconsistent reference to multiple terminologies in the original submission may impede interoperability without clarifying the contextual definition. Specimen type may not be populated (although SPM-4 is required in ELR) but some PHAs prefer specimen source (OBR-15), which has been deprecated in HL7, to be reported instead.
When ONC cites vocabulary standards for this data element, we suggest the HL7 V2 terminology referenced in the ELR be cited since the ELR IG is referenced in Meaningful Use (as of Stage 1) and deployed in all US Public Health Agencies. Some PHAs prefer SNOMED CT for specimen type, however the SNOMED terminology is not totally in synch with HL7 Table 0487 values referenced in the ELR. There is a mapping from HL7 Table 0487 to SNOMED CT which might be referenced as a resource; it is available here: Conceptmap-example-specimen-type - FHIR v4.0.1 (hl7.org).
ELR: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=98
Laboratory/Result Status
https://www.healthit.gov/isa/taxonomy/term/2441/draft-uscdi-v3
Data Element: Representing the stage of completeness of a result of a laboratory test.
Original Submission:
From CDC: | Interoperability Standards Advisory (ISA) (healthit.gov)
ACLA Comment:
Please clarify the result status element and whether it is for the panel or each individual test. For example, a Complete Blood Count (CBC) is the panel, and the White Blood Count (WBC) is one individual test within the panel.
The standards referenced in the original submission do not include HL7 Version 2.5.1 Implementation Guide: Lab Results Interface (LRI); Release 1 (US Realm) which was required by Meaningful Use Stage 2 and the HL7 Version 2.5.1 Implementation Guide: Electronic Laboratory Reporting to Public Health, Release 1 (US Realm) required for Meaningful Use Stage 1 and currently used for COVID-19 and other STLT health department reporting.
When ONC cites vocabulary standards, we suggest the HL7 V2 terminology referenced in the LRI and ELR be cited as a required terminology since these terminologies are currently used for laboratory result reporting.
LRI: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=279
ELR: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=98
Submitted by John Moehrke on
Accounting of Disclosures
I would like to recommend that a critical data element for USCDI API access are the Accounting of Disclosures.
Where each Disclosure is made available using FHIR AuditEvent, and following the IHE BasicAudit Implementation Guide, Privacy Disclosure Audit Message profile -- https://profiles.ihe.net/ITI/basicaudit/content.html#3577-privacy-disclosure-audit-message
This Privacy Disclosure Audit Message could also carry more than just the disclosures that meet the HIPAA Accounting of Disclosures. The expansion beyond HIPAA specifics is not part of this recommendation, but is encouraged.
The access to the Privacy Disclosure events enables the Patient to understand how their data are used, which is an important Privacy Principle https://healthcaresecprivacy.blogspot.com/2015/04/privacy-principles.html
Access to the Privacy Disclosure events also enables the Patient to notice when inappropriate accesses happen. This can help a Covered Entity detect inappropriate access sooner than they might detect otherwise.
The IHE BasicAudit Implementation Guide further covers how a Patient may use an application implementing the Audit Consumer -- https://profiles.ihe.net/ITI/basicaudit/volume-1.html#1524-basicaudit-overview. The IHE BasicAudit Implementation Guide also covers how all other accesses (beyond Accounting of Disclosures) could be recorded in AuditEvent so that the Patient would be able to access AuditEvents where the Patient is a agent or entity. -- https://profiles.ihe.net/ITI/basicaudit/index.html
Submitted by sg999 on
CMS-CDC Joint Comment on USCDI v3
On behalf of the Centers for Medicare and Medicaid Services (CMS) and the Centers for Disease Control and Prevention (CDC), we submit the attached comment on USCDI Draft version 3 for consideration. We thank you for the opportunity to comment on the draft version 3 of the US Core Data for Interoperability (USCDI). CMS and the CDC rely on standardized data to assess quality of care, track health problems, and promote actions that safeguard the health of individuals across the nation. We appreciate the Office of the National Coordinator’s (ONC) leadership in this space and strongly support USCDI’s role as a central mechanism to identify and implement a foundational set of electronic health information for interoperable health data exchange. We were pleased to see that version 3 includes several priority data elements that are essential to both improved public health and healthcare quality data, including health insurance information, pregnancy status, disability status, laboratory specimen type, and occupation. While both of our respective agencies will be providing independent feedback on USCDI version 3, the attached letter reflects a subset of shared, priority elements CMS and CDC jointly recommend should be included in version 3.
Submitted by sg999 on
CMS-CDC Joint Comment on USCDI v3
On behalf of the Centers for Medicare and Medicaid Services (CMS) and the Centers for Disease Control and Prevention (CDC), we submit the attached comment on USCDI Draft version 3 for consideration. We thank you for the opportunity to comment on the draft version 3 of the US Core Data for Interoperability (USCDI). CMS and the CDC rely on standardized data to assess quality of care, track health problems, and promote actions that safeguard the health of individuals across the nation. We appreciate the Office of the National Coordinator’s (ONC) leadership in this space and strongly support USCDI’s role as a central mechanism to identify and implement a foundational set of electronic health information for interoperable health data exchange. We were pleased to see that version 3 includes several priority data elements that are essential to both improved public health and healthcare quality data, including health insurance information, pregnancy status, disability status, laboratory specimen type, and occupation. While both of our respective agencies will be providing independent feedback on USCDI version 3, the attached letter reflects a subset of shared, priority elements CMS and CDC jointly recommend should be included in version 3.
Submitted by crlim35 on
HL7 Gender Harmony Project, Official Comments
The HL7 Gender Harmony Project (list of participants can be found here) respectfully submits the attached comments and recommendations.
Submitted by zhornberger on
The Medical Imaging &…
The Medical Imaging & Technology Alliance (MITA) is the leading trade association representing the manufacturers of medical imaging equipment and radiopharmaceuticals. We are encouraged to see the Office of the National Coordinator for Health Information Technology (ONC) continue its work to improve USCDI and enhance interoperability in healthcare—a goal MITA members share. We submit these comments in support of that shared goal.
MITA-Comments-USCDIv3-20220421-FINAL.pdf