Overview#
A paramedic crew responding to a multi-vehicle collision needs a trauma centre, not a clinic that is currently on divert. Their mobile device shows the nearest hospitals in order: the first two are open with available capacity, the third is on divert. Meanwhile, the incident commander checking radio channels for mutual-aid coordination can see exactly which frequencies are active and encrypted. The Responder Tools domain puts this reference data into the hands of field personnel quickly, without requiring them to call dispatch or flip through paper directories.
Key Features#
-
Medical Facility Directory: Access a comprehensive listing of medical facilities with real-time operational status (Open, Divert, Closed) and capacity information, prioritised to surface available facilities first for rapid triage routing.
-
Radio Channel Directory: Browse organised radio channel information including frequency assignments, communication protocols, and encryption status, ordered for quick reference on mobile devices.
-
Status-Prioritised Ordering: Facility listings are automatically sorted so that open facilities with the most available capacity appear first, reducing decision time during critical moments.
-
Cross-Agency Visibility: Authorised administrators can view facility and channel data across organisational boundaries, supporting mutual aid and multi-agency coordination.
-
Active Channel Filtering: Radio channel listings can be filtered to show only active channels, reducing clutter and helping responders quickly find the right communication path.
Use Cases#
Field reference tools for medical facilities and radio channels matter most in high-tempo, time-critical environments. Industries served include emergency medical services, public safety, and military and defence operations.
-
Emergency Triage Routing: Paramedics in the field can instantly identify the nearest open hospital with available capacity for patient transport decisions.
-
Multi-Agency Coordination: During large-scale incidents, supervisors can review radio channels across agencies to establish interoperable communications.
-
Dispatch Support: Dispatchers can reference facility status when directing units, ensuring patients are routed to facilities that can accept them.
-
Shift Briefings: Responders can review current facility status and active radio channels at the start of each shift.
Integration#
The Responder Tools domain supports coordinated emergency operations across the platform:
- Dispatch: Facility status informs routing decisions for patient transport
- Unified Command: Radio channel data supports multi-agency communication planning
- Incident Management: Real-time facility capacity feeds into incident resource planning
Open Standards#
- GraphQL (June 2018 specification): All facility and radio channel reference data is queried through a typed GraphQL API, enabling mobile clients to request precisely the fields they need without over-fetching.
- APCO Project 25 (P25 / TIA-102): Radio channel records carry a protocol field that identifies P25 talkgroups and frequencies, allowing responders to confirm interoperable digital radio parameters directly from the directory.
- ETSI Digital Mobile Radio (DMR, TS 102 361): The channel directory supports DMR as a protocol variant alongside P25, covering agencies that operate European digital trunked radio infrastructure.
- WGS 84 (ISO 6709 / EPSG:4326): Medical facility locations are stored as decimal-degree latitude and longitude coordinates on the WGS 84 datum, compatible with any standard GPS or mapping client.
- JSON (RFC 8259 / ECMA-404): A structured JSONB metadata field is available on both facility and channel records, allowing tenants to attach arbitrary operational attributes without schema changes.
- ISO 8601 / RFC 3339: All record timestamps (created_at, updated_at) are stored and returned as timezone-aware datetime values in ISO 8601 format, supporting consistent time-ordering across deployments in different regions.
- JSON Web Token (RFC 7519) with RS256: Access to both queries is gated by JWT bearer tokens verified against a JWKS endpoint using RS256, ensuring only authenticated users receive reference data.
Last Reviewed: 2026-02-24 Last Updated: 2026-04-14