Submitted By: Sandi Mitchell / J P Systems, Inc. | |
---|---|
Data Element Information | |
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 |
|
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. |
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. |
||||||||||
|
Comment