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 wgsuarez on
Need to Supplement Birth Sex in the Demographics Data Class
ISSUE
USCDI V1 demographic section uses Birth Sex as the data element required in the Standard. While there may be some use for this data element, Birth Sex alone does not capture the “sex, gender, physiologic, or anatomical information that is important for a given clinical decision or course of treatment for a patient.”* ONC requirements to use Birth Sex as the patient demographic standard presents problems particularly for patients who have under gone Gender Affirming Surgery. A patients may have a Legal Sex and Gender Identity that is different than the Sex Assigned at Birth. Yet, Sex Assigned at Birth is the only sex/gender category allowed in the USCDI standard.
In this context, Birth Sex alone is not sufficient, nor appropriate, in some instances, to be required to be reported, as it does not reflect the current realities of many individuals. The concern is that the USCDI V2 retains the current limitation from USCDI V1 with respect to not including anything outside of Birth Sex, which is too limited and in many cases inappropriate or even potentially offensive. Two examples: 1) responding to a person’s request for information with their “birth sex” when the person have gone through gender affirming surgery, or considers him/herself to be a different sex than what was reported as “birth sex”; 2) sharing USCDI with other providers about a patient that is no longer in the same sex category as what was recorded in “birth sex”.
(*) = EPIC’s definition for clinically relevant sex
RECOMMENDATION
-- KP recommends against using only Birth Sex as a standard data element in the Demographics Section of the USCDI Version 2
-- KP recommends that in addition to Birth Sex, the USCDI v2 should include:
- Sexual Orientation: An individual’s inherent or immutable enduring emotional, romantic or sexual attraction to other people
- Gender Identity: An individual's personal sense or concept of self as a male, female, a blend of both, or neither. One's gender identity can be the same or different from their sex assigned at birth.
- Recorded/Legal Sex: Sex or Gender on an identity document where identity document examples include a passport, driver's license and birth certificate.
-- KP believes that the clinically relevant INFORMATION related to sex is NOT a single field or EPT item, but a detail inventory of organs the patient currently has, plus the relevant associated details (e.g. organ from birth vs. surgically constructed organ).
Submitted by RiplingerL on
AHIMA USCDI Draft v2 Comments
The American Health Information Management Association appreciates the opportunity to submit comments on the USCDI Draft version 2. AHIMA supports ONC's objective of advancing nationwide, interoperable health information exchange. Please find attached AHIMA's detailed comments on USCDI draft version 2.
Submitted by trujillos@ochin.org on
OCHIN Comments on Draft USCDI Version 2
On behalf of OCHIN, we appreciate the opportunity to submit the following comments in response to the draft U.S. Core Data for Interoperability (USCDI) version 2. OCHIN is a national, non-profit community-based health innovation and research network serving as a virtual nationwide health care system and a national leader in promoting high-quality health care in underserved communities across the country. OCHIN strongly supports the Office of the National Coordinator of Health Information Technology’s (ONC) efforts to drive interoperability through national standards. National standards are the foundation needed to improve the quality of care, bend the cost curve, and empower patients, while paving the way for payment and delivery transformations, particularly for community-based providers that do not have the resources to comply with varied local, regional, state, and national standards. Further, widely adopted national standards are essential to address structural inequality in health care as well as to mount timely, data-driven responses to public health emergencies. Please find OCHIN's specific recommendations included in the uploaded attachment. Sincerely, Jennifer Stoll
Submitted by trujillos@ochin.org on
OCHIN Comments on Draft USCDI Version 2
On behalf of OCHIN, we appreciate the opportunity to submit the following comments in response to the draft U.S. Core Data for Interoperability (USCDI) version 2. OCHIN is a national, non-profit community-based health innovation and research network serving as a virtual nationwide health care system and a national leader in promoting high-quality health care in underserved communities across the country. OCHIN strongly supports the Office of the National Coordinator of Health Information Technology’s (ONC) efforts to drive interoperability through national standards. National standards are the foundation needed to improve the quality of care, bend the cost curve, and empower patients, while paving the way for payment and delivery transformations, particularly for community-based providers that do not have the resources to comply with varied local, regional, state, and national standards. Further, widely adopted national standards are essential to address structural inequality in health care as well as to mount timely, data-driven responses to public health emergencies. Please find OCHIN's specific recommendations included in the uploaded attachment. Sincerely, Jennifer Stoll
Submitted by mattreid on
AMA comments re: USCDI v2
The American Medical Association, on behalf of the nation’s physicians, has significant concerns with the proposal and HITAC’s USCDI Task Force’s recommendation to add the data class “Diagnostic Studies/Exams.” The Task Force, in its report to HITAC for 4/15/21, identifies the need to clarify the definition and scope of the “Procedures” data class due to its recommendation to add “Diagnostic Studies/Exams.” Herein lies the problem. Procedures include diagnostic and therapeutic services and cannot be separately and distinctly defined from diagnostic studies/exams. Even the terminology of “diagnostic” may be confusing as procedures may start as diagnostic and change to therapeutic. For example, a screening/diagnostic colonoscopy can change to therapeutic if polyps are identified and removed during the procedure. Another example is a primary care physician periodically obtaining an EKG as part of a routine physical exam for a person over the age of 40 vs. obtaining an EKG when the same person complains of recent episodes of chest pain. Adding the data class “Diagnostic Studies/Exams,” no matter how it is intended to be used, will cause confusion for the classification of these data and their subsequent interpretation as they are exchanged among users.
Submitted by sbzemel on
Comments on USCDI version 2
On behalf of Providence, thank you for the opportunity to provide feedback in response to the Office of the National Coordinator for Health Information Technology’s (ONC) draft of United States Core Data for Interoperability (USCDI) version 2.
Providence is one of the largest health systems in the United States, with a seven-state footprint that spans Alaska, California, Montana, New Mexico, Oregon, Texas, and Washington. Our diverse family of organizations employ 120,000 people who serve in 51 hospitals, 1,085 clinics, a health plan, senior services and housing, and many other health and educational services. Our non-profit health system is dedicated to serving the Medicaid population, and each year we work to provide care and services where they are needed most, including investments in community benefit that in 2019 totaled $1.5 billion.
We appreciate the opportunity to provide comments on the proposed draft of the USCDI version 2. We support many of the elements that ONC is proposing to add. Providence is sharing most of them on our patient portal and Continuity of Care Documents (CCDs). In addition, our specific comments on the draft elements are as follows:
Clarify encounter time: The ONC website says that encounter time “Specifies the date and time associated with the encounter, for clinical context. This would include an admission and discharge date and time for a hospital encounter or a date/time of an office visit/appointment.” Providence asks ONC to clarify this further to define encounter time more fully.
Date of resolution: This data element is not something that is captured and can be easily shared. Providence urges ONC to remove this data element from the draft USCDI v.2.
Providence reviewed the level 2 data elements that were not included in the Draft USCDI v2 and has the following comments on including them in the final USCDI v.2:
- Food and non-med allergy data elements: Providence supports adding these to the final USCDI v. 2. We believe it would be appropriate and useful to include these data elements because many people are allergic to soy (food allergy) and soy is in a lot of medications. Additionally, many people are allergic to latex and nickel (non-med allergies) and it would be beneficial for healthcare providers to know this information. Providence already shares these two allergy data elements on their patient portal and CCDs so it would not be burdensome to our organization if this was added to the final USCDI v2.
- Provider DEA and NPI: We urge ONC to remove Provider DEA and NPI to the final version of the USCDI v.2. Providence believes this information does not need to be shared with other providers and should never be shared with patients.
- Provider telecom, role, and location: Providence supports adding these data elements to the final USCDI v2.
- Diagnostic studies: Providence believes Diagnostic Studies is another data element that should be added to the final USCDI v.2. These studies are beneficial to share with all healthcare providers and with the patient. Providence already shares diagnostic studies on their patient portal and CCDs so it would not be burdensome for us if this was added to the final USCDI v2.
- Encounter location: Providence supports adding this data element to the final USCDI v.2
- Disposition: Providence urges ONC to remove this data element from the final USCDI v.2.
- Social Determinants of Health (SDOH): Providence strongly supports adding these data elements to the final USCDI v.2. Providence has been working with the Gravity Project and working internally to ensure these data elements are mapped in our system.
- Medicare Patient Identifier and Mother’s Maiden Name: Providence urges ONC to remove these data elements from the final version. We believe that sharing this information would make it easier for hackers to potentially obtain this information.
Submitted by Mark Savage on
Gravity Project’s Comments on USCDI Draft Version 2
Dear National Coordinator Tripathi:
The Gravity Project submits these comments on draft version 2 of the United States Core Data for Interoperability, released for public comment by the Office of the National Coordinator for Health Information Technology on January 12, 2021. The Gravity Project develops and tests consensus-based standards that facilitate capture and exchange of social determinants of health (SDOH) data across a variety of systems and settings of care and social services, by convening stakeholders across the nation through an open and transparent collaborative process. We thank you for the opportunity to provide these comments.
The Biden-Harris Administration affirmed on day one that health equity must be an immediate national priority. The COVID-19 pandemic has highlighted the considerable gaps and disparities in health and health care in underserved communities across the nation. In a recent interview, you explained the priority for “health equity by design” and the role of social determinants of health data. The Gravity Project’s submitted Social Determinants of Health data class enables exactly that—health equity by design—by integrating terminology and FHIR API-based exchange for clinical care and community referrals and interventions.
The Office of the National Coordinator (ONC) categorized the Gravity Project’s submission as Level 2, yet failed to include the SDOH data class in the draft version 2 released for public comment on January 12. Instead, ONC proposed another “modest expansion” of the core structured health data the nation needs for interoperability and health care. For the reasons in our attached letter, the Gravity Project urges ONC to add the SDOH data class to version 2 so that health IT developers may begin integrating health equity by design now while they are designing and preparing the real-world testing and certification criteria for implementation in 2022 and 2023 under ONC’s and the Centers for Medicare & Medicaid Services’ (CMS) regulations. This assures that providers, patients, payers, community-based organizations, app developers, and stakeholders across the nation may begin using these SDOH data sets for better health care and better health.
Submitted by Mark Savage on
UCSF Center for Digital Health Innovation on USCDI Draft Ver. 2
Dear National Coordinator Tripathi:
The University of California, San Francisco’s Center for Digital Health Innovation submits the attached comments and proposals for draft version 2 of the U.S. Core Data for Interoperability, released for public comment on January 12, 2021. In short, the USCDI is the standardized set of health data classes and elements essential for nationwide interoperability, electronic health information exchange, and usability without special effort.
Clearly, what ONC does and does not include in the U.S. Core Data for Interoperability matters. Moreover, the same data element often serves multiple use cases, multiplying its importance. Structured data elements missing from the USCDI and draft version 2 are essential for a number of key national use cases, such as
- COVID-19 and remote care;
- Patient-generated health data, patient-reported outcomes, and social determinants of health;
- Health equity and health disparities;
- Value-based care delivery;
- Interoperability and the 2015-2024 Nationwide Interoperability Roadmap;
- Patient access, shared care planning, and care coordination across clinical and non-clinical settings;
- CMS’s work to build digital quality measures;
- Precision Medicine Initiative and research; and
- A robust health app ecosystem, which is constrained by the standardized data available to design and use innovative health apps with FHIR APIs.
We appreciate the considerable work that ONC has devoted to USCDI draft version 2. Unfortunately, draft version 2, like version 1, is only another “modest expansion” of the Common Clinical Data Set. If the past sixteen months of responding to the COVID-19 pandemic have taught us anything, they have taught us that America’s providers, patients, and health IT developers need far more than a “modest” addition to the U.S. Core Data for Interoperability version 2.
For a health care provider, USCDI version 1 and these few additions are not enough to meet national health imperatives, as we demonstrate in the attached letter. We urge ONC to add numerous additional data elements now so that they, too, become available for better health care, for the key national use cases above, and for the nationwide learning health system we need.
Submitted by Fresenius Medi… on
Fresenius Comment on USCDI V2
Fresenius Medical Care North America (FMNCA) welcomes the opportunity to comment on the draft version 2 United States Core Data for Interoperability (USCDI V2). FMNCA is the largest integrated supplier in the US of services and products for patients with End Stage Renal Disease (ESRD) undergoing dialysis treatment both in an outpatient clinic and at home. As a national provider with more than 200,000 patients with serious illness, we support the Office of the National Coordinator’s (ONC) goals for nationwide interoperable health information exchange. We believe ONC has an opportunity to reduce readmissions for dialysis patients by including health data classes and data elements to the USCDI that are specific to the dialysis treatment. Please find our full comments are attached.
Submitted by zhornberger on
MITA Comments on USCDI draft V2
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-USCDIV2-20210414 (5CQYP9FE).pdf