HL7 FHIR AllergyIntolerance Resource: clinicalStatus vs. verificationStatus, Criticality, RxNorm/SNOMED CT Coding, and US Core Profile

The HL7 FHIR AllergyIntolerance resource is the normative clinical data structure in Fast Healthcare Interoperability Resources (FHIR R4) for documenting a patient’s clinical propensity, hypersensitivity, or physiological intolerance toward a medication, food, biologic, or environmental substance. Within the broader ecosystem of HL7 FHIR resources, AllergyIntolerance serves as a foundational patient safety artifact: every time a clinician initiates an electronic prescription using FHIR MedicationRequest or reconciles a patient’s longitudinal chart, automated clinical decision support (CDS) engines evaluate active AllergyIntolerance records to block anaphylactic drug re-exposures and flag chemical cross-reactivities.

What Is FHIR AllergyIntolerance and How Is It Used in Clinical Research and Healthcare?

In the HL7 FHIR R4 clinical module, AllergyIntolerance represents a forward-looking risk assertion rather than a single isolated past event. While an acute toxic overdose, medication administration error, or procedural complication is documented using the FHIR AdverseEvent or FHIR Condition resource, AllergyIntolerance specifically captures an ongoing predisposition to react adversely if re-exposed to the offending agent.

The resource distinguishes between two physiological mechanisms via the AllergyIntolerance.type element (bound to http://hl7.org/fhir/allergy-intolerance-type):

• allergy (Immune-Mediated Hypersensitivity): An immunologically mediated response to a substance, including IgE-mediated Type I immediate hypersensitivity (such as urticaria, angioedema, bronchospasm, or anaphylaxis to beta-lactam antibiotics or peanuts) and T-cell-mediated Type IV delayed hypersensitivity (such as Stevens-Johnson Syndrome [SJS] or Toxic Epidermal Necrolysis [TEN] associated with lamotrigine, allopurinol, or carbamazepine).
• intolerance (Non-Immune-Mediated Sensitivity): A non-immunologic, reproducible adverse physiological reaction at normal therapeutic or dietary doses—such as gastrointestinal distress from oral erythromycin, lactase deficiency causing lactose intolerance, or pharmacological pseudo-allergic reactions (such as NSAID-exacerbated respiratory disease or ACE-inhibitor-induced bradykinin angioedema).

In clinical research, electronic data capture (EDC) and eSource pipelines query AllergyIntolerance resources via FHIR APIs to screen trial candidates against protocol exclusion criteria (such as documented hypersensitivity to monoclonal antibody excipients like polysorbate 80 or histidine buffers) and to populate CDISC SDTM Concomitant/Prior Medical History logs.

Core Schema Elements, Status Invariants (ait-1 & ait-2), and Criticality vs. Severity

Implementing AllergyIntolerance accurately requires strict adherence to its two status axes (clinicalStatus and verificationStatus), its category taxonomy, and the separation between prospective criticality and retrospective reaction.severity:

FHIR R4 Element Path	Cardinality (Base / US Core)	Data Type & Value Set Binding	Clinical & Informatics Role
clinicalStatus	0..1 (MustSupport; conditional mandatory)	CodeableConcept: active | inactive | resolved	Indicates whether the propensity is currently active (`active`) or has clinically resolved (e.g., after oral immunotherapy or outgrowing a childhood allergy).
verificationStatus	0..1 (MustSupport)	CodeableConcept: unconfirmed | presumed | confirmed | refuted | entered-in-error	Records epistemological certainty—for example, changing a penicillin allergy to refuted following a negative skin prick test and graded oral amoxicillin challenge.
type	0..1	code: allergy | intolerance	Differentiates true immune-mediated hypersensitivity from non-immune pharmacological or metabolic intolerance.
category	0..*	code: food | medication | environment | biologic	Classifies the substance domain to route alerts to pharmacy CPOE vs. hospital dietary/nutrition systems.
criticality	0..1	code: low | high | unable-to-assess	Prospective risk assessment of potential future life-threatening harm or organ failure upon re-exposure.
code	1..1 (US Core Mandatory)	CodeableConcept (RxNorm, SNOMED CT, UNII, NDC)	Identifies the causative substance, pharmaceutical product, or drug class, or asserts “No Known Allergies”.
patient	1..1 (Mandatory)	Reference(Patient)	Links the allergy record to the subject’s FHIR Patient resource.
reaction.manifestation	1..* inside reaction (MustSupport)	CodeableConcept (SNOMED CT clinical findings)	Documents the specific clinical signs/symptoms observed during a past exposure event (e.g., anaphylaxis, urticaria, bronchospasm).
reaction.severity	0..1 inside reaction	code: mild | moderate | severe	Retrospective physiological grading of how severe a specific historical reaction episode was.

FHIRPath Invariants ait-1 and ait-2

Just like the FHIR Condition resource, AllergyIntolerance enforces two normative FHIRPath validation invariants governing the interaction of clinicalStatus and verificationStatus:

• Invariant ait-1: AllergyIntolerance.clinicalStatus SHALL be present if verificationStatus is not entered-in-error.
• Invariant ait-2: AllergyIntolerance.clinicalStatus SHALL NOT be present if verificationStatus is entered-in-error.

Violating either invariant causes any conformant FHIR server or ONC Inferno certification test suite to reject the payload with an OperationOutcome validation error.

Why criticality and reaction.severity Are Not Interchangeable

A common implementation mistake in health IT interfaces is mapping an HL7 v2 allergy severity flag simultaneously to both criticality and reaction.severity. In HL7 FHIR R4, these elements answer two different clinical questions:

• A patient may have experienced a mild cutaneous hives reaction (reaction.severity = "mild") after their first sensitizing dose of an intravenous beta-lactam or platinum chemotherapy agent, yet an allergist may assign criticality = "high" because a subsequent full-dose intravenous challenge carries a high probability of IgE-mediated anaphylactic shock.
• Conversely, a patient may have experienced severe gastrointestinal nausea and vomiting from oral codeine (reaction.severity = "severe", type = "intolerance"), while the clinician records criticality = "low" because re-exposure is not life-threatening.

What Standards or Regulatory Requirements Govern FHIR AllergyIntolerance?

In the United States, the US Core FHIR Implementation Guide (STU 3.1.1 through STU 7.0.0) profiles AllergyIntolerance to satisfy the ASTP/ONC United States Core Data for Interoperability (USCDI) Allergies and Intolerances data class required under 45 CFR § 170.315(g)(10) standardized API certification:

• US Core Allergen Terminology Bindings (AllergyIntolerance.code): Bound to the US Core Common Substances value set, which combines:
  • RxNorm (http://www.nlm.nih.gov/research/umls/rxnorm): Required for specific branded and generic medications and ingredient concepts (e.g., Penicillin G 7980, Amoxicillin 723, Sulfamethoxazole 10180).
  • SNOMED CT (http://snomed.info/sct): Used for broader pharmacological drug classes (e.g., Sulfonamide antibacterial 764146007), food allergens (e.g., Peanut 762952008), venom, latex (111088007), and environmental allergens.
  • FDA UNII — Unique Ingredient Identifier (http://fdasis.nlm.nih.gov): Used for specific chemical substances, vaccine adjuvants, and inactive pharmaceutical excipients (e.g., Polyethylene glycol [PEG] or Polysorbate 80).
• Representing “No Known Allergies” (NKA) and “No Known Drug Allergies” (NKDA): Rather than leaving a patient’s allergy query empty—which is clinically ambiguous because a consuming system cannot tell whether the patient has no allergies or whether the allergy history was simply never asked—US Core specifies recording an explicit AllergyIntolerance resource with clinicalStatus = "active", verificationStatus = "confirmed", and a SNOMED CT negation concept in code:
  • 716186003 — No known allergy (situation)
  • 409137002 — No known drug allergy (situation)
  • 429625007 — No known food allergy (situation)
  • 428607008 — No known environmental allergy (situation)

Worked JSON Example: US Core Conformant AllergyIntolerance

The following JSON payload illustrates a conformant US Core AllergyIntolerance resource documenting a confirmed, high-criticality penicillin allergy with a historical anaphylaxis manifestation:

{
  "resourceType": "AllergyIntolerance",
  "id": "example-penicillin-anaphylaxis",
  "meta": {
    "profile": [
      "http://hl7.org/fhir/us/core/StructureDefinition/us-core-allergyintolerance"
    ]
  },
  "clinicalStatus": {
    "coding": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical",
        "code": "active",
        "display": "Active"
      }
    ]
  },
  "verificationStatus": {
    "coding": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-verification",
        "code": "confirmed",
        "display": "Confirmed"
      }
    ]
  },
  "type": "allergy",
  "category": ["medication"],
  "criticality": "high",
  "code": {
    "coding": [
      {
        "system": "http://www.nlm.nih.gov/research/umls/rxnorm",
        "code": "7984",
        "display": "Penicillin V"
      },
      {
        "system": "http://snomed.info/sct",
        "code": "764146007",
        "display": "Penicillin"
      }
    ],
    "text": "Penicillin"
  },
  "patient": {
    "reference": "Patient/example-patient-101"
  },
  "recordedDate": "2025-04-12",
  "reaction": [
    {
      "substance": {
        "coding": [
          {
            "system": "http://www.nlm.nih.gov/research/umls/rxnorm",
            "code": "723",
            "display": "Amoxicillin"
          }
        ]
      },
      "manifestation": [
        {
          "coding": [
            {
              "system": "http://snomed.info/sct",
              "code": "39579001",
              "display": "Anaphylaxis"
            }
          ],
          "text": "Anaphylaxis with airway angioedema"
        }
      ],
      "severity": "severe"
    }
  ]
}

How Does FHIR AllergyIntolerance Integrate with EHR Workflows, HL7 v2 AL1, and C-CDA?

In hospital interoperability pipelines, interface engineers translate between legacy messaging standards and FHIR R4 AllergyIntolerance:

Semantic Concept	HL7 v2 AL1 Segment Field	HL7 C-CDA R2.1 Allergies Section (LOINC 48765-2)	HL7 FHIR R4 AllergyIntolerance Path
Allergen Category / Type	AL1-2 (Allergen Type Code: DA Drug, FA Food, EA Env)	Allergy Intolerance Observation value code (`419511003` Drug allergy, etc.)	AllergyIntolerance.category & AllergyIntolerance.type
Causative Substance / Drug	AL1-3 (Allergen Code/Mnemonic/Description)	participant[@typeCode='CSM']/participantRole/playingEntity/code	AllergyIntolerance.code ( general class ) & reaction.substance (specific agent)
Severity / Criticality	AL1-4 (Allergy Severity Code: SV Severe, MO Moderate, MI Mild)	Severity Observation (2.16.840.1.113883.10.20.22.4.8) & Criticality Observation	AllergyIntolerance.reaction.severity & AllergyIntolerance.criticality
Clinical Manifestation	AL1-5 (Allergy Reaction Code — repeating text/coded symptom)	Reaction Observation (2.16.840.1.113883.10.20.22.4.9) value (SNOMED CT)	AllergyIntolerance.reaction.manifestation
Onset / Identification Date	AL1-6 (Identification Date)	Allergy Observation effectiveTime/low	AllergyIntolerance.onset[x] & AllergyIntolerance.recordedDate

Frequently Asked Questions

What is FHIR AllergyIntolerance and how is it used in clinical research and healthcare?

In HL7 FHIR R4, AllergyIntolerance is the normative clinical resource used to record a clinical assessment of a patient’s propensity or potential risk for an adverse reaction upon future exposure to a specific substance, pharmaceutical product, or drug class. It is used in Electronic Health Records (EHRs), computerized provider order entry (CPOE) drug-allergy clinical decision support, patient intake reconciliation, and clinical trial eligibility screening to prevent life-threatening hypersensitivity or intolerance reactions.

What standards or regulatory requirements govern FHIR AllergyIntolerance?

The FHIR AllergyIntolerance resource is governed by the HL7 FHIR R4 specification, the HL7 US Core Implementation Guide (US Core AllergyIntolerance Profile, STU 3.1.1 through STU 7.0.0), and the ONC United States Core Data for Interoperability (USCDI) Allergies and Intolerances data class. Under ONC Health IT certification criteria (45 CFR § 170.315(g)(10)), certified EHR APIs must expose patient AllergyIntolerance records coded with RxNorm (medications), SNOMED CT (substances, foods, environmental agents, and reaction manifestations), or FDA UNII (active/inactive ingredients).

How does FHIR AllergyIntolerance integrate with EHR and health informatics workflows?

In EHR workflows, AllergyIntolerance resources are queried during patient chart launch (SMART on FHIR) and CPOE medication ordering (HL7 CDS Hooks order-select and order-sign) alongside FHIR MedicationRequest resources to trigger automated drug-allergy and cross-sensitivity checks. Health systems also map legacy HL7 v2 AL1 segments and HL7 C-CDA Allergy Concern Act (2.16.840.1.113883.10.20.22.4.30) XML entries into FHIR AllergyIntolerance resources via hospital integration engines.

What is the difference between AllergyIntolerance.criticality and AllergyIntolerance.reaction.severity?

AllergyIntolerance.criticality (low, high, or unable-to-assess) is a prospective, clinical risk assessment of the potential life-threatening harm or organ damage that could occur upon a future exposure to the substance. By contrast, AllergyIntolerance.reaction.severity (mild, moderate, or severe) is a retrospective clinical grading of the physical intensity of a specific historical reaction event (such as a mild localized rash during a past exposure that may still warrant a high future criticality rating).