Knogin
[Core Modules]

EDXL Resource Availability and Hospital Capacity (HAVE)

During a surge event, a control room needs to know which hospitals are open, which emergency departments are under pressure, and where limited specialist capacity still exists.

Module metadata

During a surge event, a control room needs to know which hospitals are open, which emergency departments are under pressure, and where limited specialist capacity still exists.

Back to All Modules

Source reference

content/modules/edxl-resource-availability-have.md

Last Updated

Apr 22, 2026

Category

Core Modules

Content checksum

a0dd7164d92b994e

Tags

modules

Overview#

During a surge event, a control room needs to know which hospitals are open, which emergency departments are under pressure, and where limited specialist capacity still exists. If that picture is built from phone calls and manually updated notes, it is outdated as soon as the next ambulance is assigned.

The EDXL Resource Availability and Hospital Capacity module brings hospital and facility-availability information into the platform using the EDXL-HAVE model. It gives operational users a structured way to review current status, bed availability, and effective-time updates, and to keep that picture live inside wider response and patient-flow workflows.

Diagram

flowchart TD
    A[Hospital Availability Feed] --> B[HAVE Record Ingested]
    B --> C[Latest Capacity View]
    C --> D[Dispatch and Clinical Users Review]
    D --> E[Destination and Diversion Decisions]
    C --> F[Live Availability Refresh]

Last Reviewed: 2026-04-22 Last Updated: 2026-04-22

Key Features#

  • Hospital Availability View: Present current facility status, emergency-department status, and available capacity in a structured list.
  • Latest-State Aggregation: Focus users on the most recent operational state rather than a pile of disconnected updates.
  • Live Refresh Pattern: Support repeat polling or live-style refresh for users who need current availability during active coordination.
  • Regional Source Awareness: Preserve which source or tenant supplied the availability update.
  • Operational Reuse: Make capacity information available to dispatch, clinical, and command workflows instead of isolating it in a separate status board.

Use Cases#

  • Destination Planning: Ambulance control reviews current ED and bed availability before deciding where to route a patient.
  • Mass Casualty Management: Command staff monitor regional capacity while spreading patients across receiving facilities.
  • Diversion Awareness: A dispatch centre sees that a facility is degraded and adjusts routing decisions accordingly.
  • Regional Coordination: Multiple hospitals publish a structured current-state view into a shared operational picture.

Integration#

  • PSAP and Dispatch Workflows: Hospital availability can inform destination and transport decisions during live incidents.
  • ePCR and Handover Workflows: Receiving-facility awareness can complement handover and pre-arrival planning.
  • Operational Picture and Command Views: Capacity status can sit inside the wider common operating picture.
  • Major-Incident Coordination: Regional capacity can support surge, diversion, and multi-facility casualty planning.

Open Standards#

  • OASIS EDXL-HAVE 2.0: the module aligns with the emergency data standard for hospital and healthcare-facility availability.
  • EDXL Distribution Element: HAVE exchanges can align with the broader EDXL family for routed emergency-information distribution.
  • ISO 8601: effective times and status timestamps use a standard date-time representation.
  • RFC 8259 JSON: structured availability payloads can be exchanged in a standard machine-readable format where JSON transport is used.