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 nachcinformatics on
Public Comment on USCDI v2 from NACHC
NACHC agree with ONC's proposal to include encounters in USCDIv2. NACHC also strongly encourages ONC to include SDOH domains as described in PRAPARE and listed in ISA and the Gravity Project, SOGI and sexual health data elements, pregnancy status and other women's health data elements as proposed by NACHC and occupational and COVID-19 related data elements in USCDIv2. Please see the attached letter for details.
Submitted by nachcinformatics on
Public Comment on USCDI v2 from NACHC
NACHC agree with ONC's proposal to include encounters in USCDIv2. NACHC also strongly encourages ONC to include SDOH domains as described in PRAPARE and listed in ISA and the Gravity Project, SOGI and sexual health data elements, pregnancy status and other women's health data elements as proposed by NACHC and occupational and COVID-19 related data elements in USCDIv2. Please see the attached letter for details.
Submitted by mdoan on
Comments on USCDI v2
Thank you for this opportunity to provide comments to the draft USCDI v2. Attached are comments from the Federal Electronic Health Record Modernization Program Office, Defense Health Agency, and Veterans Affairs.
Submitted by tracyedinger on
LOINC comment on USCDI v2
LOINC appreciates the opportunity to give feedback on USCDI v2. While we recognize that the scope of changes from USCDI v1 to USCDI v2 was limited due to the ongoing COVID-19 pandemic and its burden on health IT developers and the health care community, we believe that the addition or clarification of several additional data classes and elements is important to advancing health data interoperability in the U.S. The attached document contains our detailed feedback.
Submitted by mbkurilo@immre… on
USCDI V2, Level 2 Data Elements for Immunization
Hello - Please see attached comments from the American Immunization Registry Association. Thank you for the opportunity to share our thoughts.
Sincerely,
Mary Beth Kurilo, AIRA
Submitted by brianscarpelli on
Comments of the Connected Health Initiative
Please find attached comments of the Connected Health Initiative (www.connectedhi.com).
Brian Scarpelli
Senior Global Policy Counsel
+1 517-507-1446 | bscarpelli@actonline.org
Connected Health Initiative
1401 K St NW (Ste 501)
Washington, DC 20005
Submitted by JN2021 on
LexisNexis Risk Solutions Comment on USCDI draft V2
This field is for general comments on the USCDI. To submit new USCDI data classes and/or data elements, please use the USCDI ONDEC system: https://healthit.gov/ONDEC
Submitted by JN2021 on
LexisNexis Risk Solutions Comment on USCDI draft V2
Attached please find LexisNexis Risk Solutions comments to the proposed USCDI Draft Version 2.
Submitted by Allina Health … on
Comment on USCDI V2 Draft
On behalf of Allina Health, attached are comments in response to the Draft Version 2 of the United States Core Data for Interoperability (USCDI) standards. Thank you for the opportunity to submit comments.
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 ragnhildurb on
ANI comments on USCDI draft V2
On behalf of the The Alliance for Nursing Informatics (ANI), we submit our comments on the USCDI draft version 2, attached.
The Alliance for Nursing Informatics (ANI), cosponsored by AMIA & HIMSS, advances nursing informatics leadership, practice, education, policy and research through a unified voice of nursing informatics organizations. We transform health and healthcare through nursing informatics and innovation. ANI is a collaboration of organizations that represents more than 20,000 nurse informaticists and brings together 25 distinct nursing informatics groups globally. ANI crosses academia, practice, industry, and nursing specialty boundaries and works in collaboration with the more than 4 million nurses in practice today.
ANI COMMENTS on USCDI_SDH_FINAL.pdf