Integration Contract — Allergy & Adverse Reaction Tracking

​

Publishers

​

Payload (UUID-only, no PHI)

// cl_allergy_recorded
{
  "event": "cl_allergy_recorded",
  "publisher": "CL",
  "subscriber": ["CL-08", "CL-15", "PF-10"],
  "payload": {
    "allergy_id": "uuid",
    "chart_id": "uuid",
    "organization_id": "uuid",
    "criticality": "low | high | unable-to-assess",
    "is_sud_mat_class": false
  },
  "metadata": { "organization_id": "uuid", "user_id": "uuid", "timestamp": "iso8601", "correlation_id": "uuid" }
}

​

API Contracts (synchronous)

​

getActiveAllergies(chartId): AllergyForAlert[]

• Exposed via @/platform/clinical.
• Consumers: CL-05 medication ordering, CL-06 e-prescribing.
• Returns active allergies filtered by RLS + cl_has_sud_consent for SUD-MAT class.
• Shape: { id, allergen_code, allergen_class_code, allergen_display, reaction_severity, criticality }[].

​

Idempotency & Retry

• All events idempotent on (event, payload.allergy_id, metadata.timestamp).
• Subscribers MUST tolerate at-least-once delivery.

​

Security

• No PHI in event payloads (constitution §4).
• SUD-MAT-class payloads still emit but with is_sud_mat_class=true; consumers re-resolve via consent-gated read before disclosure.
• Redisclosure log entry written by CL-16 / CL-20 when exporting SUD-MAT class allergies.

​

Open Items

• Confirm channel name (cl_events vs spec-specific) with EVENT_CONTRACTS.md owner before Phase 3.
• Confirm GR audit subscription mechanism (event vs trigger) for cl_allergy_alert_overridden.