PatientAllergyStatus

Reference data entity defining the clinical status of patient allergies. Used by PatientAllergy to indicate whether an allergy is currently active, inactive, or resolved.

Overview

PatientAllergyStatus provides standardized status codes for tracking the current clinical relevance of documented allergies. This allows healthcare systems to distinguish between allergies that require active precautions versus historical allergies that may no longer be clinically significant. Status tracking is essential for maintaining accurate allergy lists and ensuring appropriate clinical alerts.

Key Concepts

Status Codes

The standard allergy status values:

Code	Label	Clinical Meaning
`ACTIVE`	Active	Allergy requires current precautions - triggers safety alerts
`INACTIVE`	Inactive	Not currently relevant but retained for history - may still trigger warnings
`RESOLVED`	Resolved	Patient has outgrown or no longer has the allergy - minimal alerting

Clinical Implications

Active Allergies

Trigger medication interaction alerts
Display prominently in patient chart header
Included on patient wristbands
Block prescribing of contraindicated medications

Inactive Allergies

May show informational warnings
Retained for complete medical history
Could become active again (seasonal allergies, reintroduction)
Relevant for understanding past reactions

Resolved Allergies

Documented for historical completeness
Typically don't trigger alerts
Common for childhood allergies outgrown
May require re-verification before treatment

Status vs Verification

Note the distinction from verificationStatus in PatientAllergy:

Status (this entity): Is the allergy currently clinically relevant?
Verification: Has the allergy been confirmed through testing?

An allergy can be confirmed but inactive (verified allergy in remission) or unconfirmed but active (reported allergy requiring precautions until verified).

Use Cases

Allergy List Management

When reviewing patient allergies:

Display ACTIVE allergies prominently with full alerts
Show INACTIVE allergies in secondary section
Archive RESOLVED allergies in historical view
Allow status updates as clinical picture changes

Seasonal Allergy Tracking

For environmental allergies:

Mark as ACTIVE during allergy season
Change to INACTIVE during off-season
Automatically toggle based on time of year (optional)
Retain full history for pattern analysis

Childhood Allergy Resolution

When patient outgrows allergy:

Review allergy history with patient/family
Consider allergy testing to confirm resolution
Update status from ACTIVE to RESOLVED
Document date and clinical reasoning in notes

Allergy Reactivation

If previously resolved allergy returns:

Query RESOLVED allergies for the allergen
Update status back to ACTIVE
Document new reaction details
Reset lastOccurrence date

Related Entities

Entity	Relationship	Description
PatientAllergy	Referenced by	Allergy records that use this status

Standard Values

Code	Label	Description
`ACTIVE`	Active	Allergy is currently active and clinically relevant - requires precautions
`INACTIVE`	Inactive	Allergy is not currently active but may recur - retained for history
`RESOLVED`	Resolved	Allergy has been resolved or patient has outgrown it - historical record

3 properties

Schema

Properties

Property	Type	Mode	Description	Required
code	string	stored	Unique code identifying the allergy status Example: `"ACTIVE"`	Required
label	string	stored	Human-readable name of the status Example: `"Active"`	Required
description	string	stored	Description of the status	Optional

Examples

Example 1

{
  "@type": "PatientAllergyStatus",
  "code": "ACTIVE",
  "label": "Active",
  "description": "Allergy is currently active and relevant"
}

Example 2

{
  "@type": "PatientAllergyStatus",
  "code": "INACTIVE",
  "label": "Inactive",
  "description": "Allergy is not currently active but may recur"
}

Example 3

{
  "@type": "PatientAllergyStatus",
  "code": "RESOLVED",
  "label": "Resolved",
  "description": "Allergy has been resolved or patient has outgrown it"
}