Overview#
A 911 call comes in from a diabetic caller who has collapsed at home. The PSAP operator can see not only the caller's precise GPS location from their smartphone, but also their medical profile showing insulin-dependent diabetes. The paramedic crew is briefed before they arrive. This is what the RapidSOS Integration module delivers: supplemental caller data from the RapidSOS emergency data platform, pushed directly to PSAP operators in real time. Beyond basic cell tower triangulation, the integration surfaces precise location, medical history, and connected device data so that dispatchers and responders have the context they need before the first unit rolls.
Key Features#
- Integration with RapidSOS emergency data platform
- Supplemental caller location data for improved dispatch accuracy
- Medical profile access for informed emergency response
- Connected device data enrichment
- Real-time data delivery to PSAP operators
Use Cases#
The RapidSOS integration applies in any environment where enriched caller data can improve emergency response outcomes. Industries served include public safety, emergency medical services, and smart-city operations.
- Enhancing 911 call handling with precise caller location data beyond cell tower triangulation
- Providing emergency responders with caller medical information for better-prepared response
- Using connected device data to improve situational awareness during emergency calls
- Supplementing PSAP operations with additional caller context
Integration#
Integrates with PSAP operations, dispatch management, and emergency response modules within the Argus platform.
Open Standards#
- IETF RFC 7852 (Additional Data Related to an Emergency Call): The RapidSOS supplemental data (subscriber information, device details, and medical profile) is ingested and surfaced as RFC 7852 Additional Data blocks, using the seven NENA-STA-012 block types (SubscriberInfo, DeviceInfo, CommsInfo, ServiceInfo, OwnerInfo, ProviderInfo, ComponentInfo).
- NENA-STA-012 (Additional Data for Emergency Calls): Block-type vocabulary and payload structure for the seven standard additional-data categories that carry caller medical profile and connected-device context to PSAP operators.
- NENA-STA-021 / NENA i3 (Emergency Incident Data Object, EIDO): Incident and location components derived from the RapidSOS feed are mapped onto NENA EIDO dataclasses (Incident, Location, Agent, Person, Call, Vehicle) for interoperability with NG9-1-1 dispatch workflows.
- NENA-STA-006.3 (NG9-1-1 GIS Data Model): Precise caller location data from RapidSOS is validated and rendered against the NENA GIS layer schema, including PSAPBoundary routing boundaries, for accurate dispatch-zone resolution.
- RFC 4119 / RFC 5491, PIDF-LO (Presence Information Data Format, Location Object): GPS and civic-address location data from the RapidSOS platform is encoded as PIDF-LO XML (GML Point in WGS-84/EPSG:4326) for routing through the LoST/ECRF layer.
- RFC 5222, LoST (Location-to-Service Translation): PIDF-LO location payloads sourced from RapidSOS are submitted to the LoST server to resolve the responsible PSAP URI for incoming emergency calls.
- W3C Verifiable Credentials v2: ADR blocks carrying RapidSOS-derived data are wrapped in a W3C VC v2 tamper-evident envelope (Ed25519, deterministic sorted-JSON + SHA-256 canonicalisation) before being cached and delivered to the dispatcher interface.
- RFC 5031 / RFC 6443 (Emergency Service URNs): Service classification (sos, sos.ambulance, sos.police, etc.) applied to RapidSOS incidents follows the standard URN vocabulary used in SIP emergency call routing.
Last Reviewed: 2026-02-24 Last Updated: 2026-04-14