Harmful or undesired physiological responses associated with exposure to a substance.

Data Element
Criticality
Description

Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance.
Submitted By: Sandi Mitchell / J P Systems, Inc.
Data Element Information
Data Element Description Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance.
Use Case Description(s)
Use Case Description To ensure interoperability across the healthcare ecosystem, national standardizing bodies must align. For example, if one standard body requires allergy criticality, then all standard bodies should require that same data element.
Estimate the breadth of applicability of the use case(s) for this data element Level 1
ONC Priority
  • None of the above
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) HL7 FHIR R4 Allergy Intolerance Criticality, Rx Norm, SNOMED CT, National Drug Code (NDC)
http://hl7.org/fhir/ValueSet/allergy-intolerance-criticality
Additional Specifications HL7 FHIR R4 Allergy Intolerance Criticality
Current Use (Level 1) Captured, stored, or accessed in at least one production EHR or HIT module
Extent of exchange (Level 1) Between two production EHRs or other HIT modules using available interoperability standards
Supporting Artifacts HL7 FHIR R4
http://hl7.org/fhir/ValueSet/allergy-intolerance-criticality
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) None
Restrictions on Use (e.g. licensing, user fees) None
Privacy and Security Concerns Standard HIPAA concerns.
Estimate of Overall Burden Minimal burden to implement since the data element is already being exchanged. This data element impacts patient safety to ensure clinicians understand the criticality of the patient's allergy.
Other Implementation Challenges Educational awareness for clinicians will be necessary since this field has replaced severity in clinical practice.
ASTP Evaluation Details
Each submitted Data Element has been evaluated based on the following criteria. The overall Level classification is a composite of the maturity based on these individual criteria. This information can be used to identify areas that require additional work to raise the overall classification level and consideration for inclusion in future versions of USCDI
Criterion #1
Maturity - Current Standards		 Level 2 - Data element is represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Criterion #2
Maturity - Current Use 		Level 1 - Data element is captured, stored, or accessed in at least one production EHR or HIT module.
Criterion #3
Maturity - Current Exchange		 Level 1 - Data element is electronically exchanged between two production EHRs or other HIT modules using available interoperability standards.
Criterion #4
Use Case(s) - Breadth of Applicability		 Level 2 - Use cases apply to most care settings or specialties.

Comment

Submitted by jpatterson@mitre.org on

PACIO Recommends Advancement to USCDI V7

  • Recommendation: Advance Criticality data element from Level 2 to USCDI V7. 
  • Rationale: The PACIO Project Community* supports the earlier comments from CMS regarding food allergy intolerance, including the recommendation to advance the Criticality data element from Level 2 to inclusion in the USCDI V7. The inclusion of the Criticality data element in the Allergies and Intolerances data class of USCDI V7 is crucial for enhancing patient safety and clinical decision-making. The Criticality data element is the necessary companion to the allergy or intolerance agent and the clinical manifestation, aka reaction, that have been included in the USCDI since V4. While the patient's allergy or intolerance agent and clinical manifestation (reaction) provide foundational information about what triggers a reaction and how it presents, the Criticality data element adds an essential layer by indicating the severity and potential impact of a future reaction. This provides clinically actionable data for healthcare providers to assess risks more accurately and prioritize interventions, ensuring that they can make informed decisions about prescribing medications, selecting alternative treatments, and avoiding agents that could trigger severe reactions. 
  • Current standards: The PACIO Community* recommends including LOINC as an applicable standard, specifically the LOINC 82606-5 code “Allergy or intolerance criticality”, and the LOINC-based example answer list for criticality, LOINC LL4063-5. HL7 FHIR R4 Allergy Intolerance Criticality, Rx Norm, SNOMED-CT, the National Drug Code (NDC), and LOINC.
  • Current Use: Criticality is currently captured, stored, and accessed in multiple production EHRs.
  • References: 
  • * The PACIO (Post-Acute Care Interoperability) Project, established February 2019, is a collaborative effort between industry, government, and other stakeholders, that aims to advance interoperable health information exchange between post-acute care (PAC) providers, patients, and other key stakeholders across health care. 

Submitted by rdillaire on

CMS-CCSQ Supports Criticality for USCDI v6

Recommendation: CMS CCSQ recommends the Criticality element be added to final USCDI v6.

Rationale: CMS CCSQ supports Post-Acute Care Interoperability (PACIO)’s recommendation to include the Criticality data element in USCDI v6. Adding this data element to the Allergies and Intolerances data class is essential for improving patient safety and clinical decision-making. The Criticality data element complements existing USCDI elements by providing critical information about the severity and potential impact of allergic reactions, enabling healthcare providers to better assess risks and prioritize care. CMS CCSQ and PACIO share a commitment to enhancing data exchange and empowering providers to make informed, patient-centered decisions.

Submitted by jpatterson@mitre.org on

PACIO Supports Advancement to USCDI V6

  • Data Class: Allergies and Intolerances Data Class
  • Data Element: Criticality (Level 2)
  • Recommendation: Advance Criticality data element from Level 2 to final USCDI v6.
  • Rationale: The PACIO Project Community* supports the earlier comments from CMS regarding food allergy intolerance, including the recommendation to advance the Criticality data element from Level 2 to inclusion in the final USCDI V6. The inclusion of the Criticality data element in the Allergies and Intolerances data class of USCDI V6 is a crucial for enhancing patient safety and clinical decision-making. The criticality data element is the necessary companion to the allergy or intolerance agent and the clinical manifestation, aka reaction, that have been included in the USCDI since V4. While the patient's allergy or intolerance agent and clinical manifestation (reaction) provide foundational information about what triggers a reaction and how it presents, the Criticality data element adds an essential layer by indicating the severity and potential impact of a future reaction. This allows healthcare providers to assess risks more accurately and prioritize interventions, ensuring that they can make informed decisions about prescribing medications, selecting alternative treatments, and avoiding agents that could trigger severe reactions. Citations are provided below:
    • Goss FR, Zhou L, Plasek JM, Broverman C, Robinson G, Middleton B, Rocha RA. Evaluating standard terminologies for encoding allergy information. J Am Med Inform Assoc. 2013 Sep-Oct;20(5):969-79. doi: 10.1136/amiajnl-2012-000816. Epub 2013 Feb 9. PMID: 23396542; PMCID: PMC3756252.; https://pmc.ncbi.nlm.nih.gov/articles/PMC3756252/
    • HL7 AllergyIntolerance – FHIR v5.0.0 
  • * The PACIO (Post-Acute Care Interoperability) Project, established February 2019, is a collaborative effort between industry, government, and other stakeholders, with the goal of establishing a framework for the development of FHIR implementation guides to facilitate health information exchange.
  • Applicable standards: The PACIO Community also recommends including LOINC as an applicable standard, specifically the LOINC 82606-5 code “Allergy or intolerance criticality”, and the LOINC-based example answer list for criticality, LOINC LL4063-5. HL7 FHIR R4 Allergy Intolerance Criticality, Rx Norm, SNOMED-CT, the National Drug Code (NDC), and LOINC.

Log in or register to post comments

FormGuide

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:

  1. In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
  2. 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.
  3. Note that the Data Class field will automatically populate based on your current location in the platform:
    1. If you are on a data class page, the field will be set to that specific data class
    2. 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:

  1. In the "Data Element" drop-down menu, select the specific data element you want to comment on.
  2. The drop-down menu will display only the elements available under the data class you selected in the previous step.
  3. You can use the search function within the drop-down to quickly locate a specific data element.
  4. 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.
 

Data Class and Data Element

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:

  1. 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."
  2. This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
  3. In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
  4. Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Propose New Data Class or Element

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:

  1. After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
  2. A new comment section will appear, allowing you to enter details for your additional comment.
  3. For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
  4. Complete the Subject and Comment fields for your additional comment.
  5. 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.

Upload Supporting Files

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:

  1. Click the "Save and Exit" button at the bottom of the form.
  2. Your comment will be saved as a draft that you can access and complete later.
  3. 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.
  4. Click this button to continue working on your draft.
  5. You will be taken to a review page where you can:
    1. Select "Submit Comment" to officially submit your feedback.
    2. Click "Edit" to return to the comment form and make changes
    3. 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:

  1. Click the "Review and Submit" button at the bottom of the form.
  2. This will take you to a review screen displaying your comment(s) in full.
  3. Review all information for accuracy and completeness.
  4. On this review screen, you have three options: 
    1. Click "Submit Comment" to officially submit your feedback
    2. Click "Edit" to return to the comment form and make changes
    3. Click "Discard Draft" to delete the comment and start fresh
  5. The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records. 
  6. If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Review and Submit

Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.

USCDI Comments

Close

Add a New Comment

Review comment and Submit

Edit
Comment #1