{"id":"psap-ng911-additional-data-repository","slug":"psap-ng911-additional-data-repository","title":"PSAP NG911 / NG112 Additional Data Repository","description":"When a 9-1-1 or 1-1-2 call arrives, the dispatcher often needs more than the caller can say in the first few seconds. They may need vulnerable-person information, subscriber detail, a prior hazard profile for the address","category":"geospatial","tags":["geospatial","ai","blockchain"],"lastModified":"2026-04-22","source_ref":"content/modules/psap-ng911-additional-data-repository.md","url":"/developers/psap-ng911-additional-data-repository","htmlPath":"/developers/psap-ng911-additional-data-repository","jsonPath":"/api/docs/modules/psap-ng911-additional-data-repository","markdownPath":"/api/docs/modules/psap-ng911-additional-data-repository?format=markdown","checksum":"fed2b02fc9467a645538649c434880fa9f759930f2cc5968361e6c387ced1f3b","headings":[{"id":"overview","text":"Overview","level":2},{"id":"key-features","text":"Key Features","level":2},{"id":"use-cases","text":"Use Cases","level":2},{"id":"integration","text":"Integration","level":2},{"id":"open-standards","text":"Open Standards","level":2}],"markdown":"# PSAP NG911 / NG112 Additional Data Repository\n\n## Overview\n\nWhen a 9-1-1 or 1-1-2 call arrives, the dispatcher often needs more than the caller can say in the first few seconds. They may need vulnerable-person information, subscriber detail, a prior hazard profile for the address, or context from connected systems that already know something important about the call. In NG911 / NG112, that supporting material should arrive as part of the call workflow, not as a scavenger hunt across separate screens.\n\nThe Additional Data Repository module gives the platform a standards-based way to assemble and deliver those supporting data blocks for an active emergency call. It lets a PSAP query approved providers in parallel, merge the resulting additional data into the live incident context, and hand that material to dispatch workflows in a form aligned with NG911 / NG112 practice.\n\n```mermaid\nflowchart TD\n    A[Live Emergency Call] --> B[Additional Data Request]\n    B --> C[Provider 1]\n    B --> D[Provider 2]\n    B --> E[Provider 3]\n    C --> F[Signed Additional Data Blocks]\n    D --> F\n    E --> F\n    F --> G[Call Context and Incident Enrichment]\n    G --> H[Dispatcher Console]\n    G --> I[CAD and Audit Record]\n```\n\n**Last Reviewed:** 2026-04-22\n**Last Updated:** 2026-04-22\n\n## Key Features\n\n- **Call-Scoped Additional Data Retrieval**: Pull supporting data in the context of a live call rather than as a detached background search.\n\n- **Parallel Provider Fan-In**: Query multiple approved data providers at once so dispatchers receive a fuller picture without waiting through a serial lookup chain.\n\n- **Standard Block Typing**: Organise the returned material into well-understood additional-data block types rather than free-form blobs.\n\n- **Short-Lived Cache for Active Calls**: Reuse recent results during the life of the incident so repeat lookups stay fast while still reflecting that emergency call context is time-sensitive.\n\n- **Signed Block Handling**: Preserve the provenance of returned blocks so a receiving workflow can tell where the data came from and whether it was altered in transit.\n\n- **Audit-Ready Call Context**: Record which additional data was requested, which providers responded, and what was attached to the call context.\n\n- **Provider Flexibility**: Support public safety, digital footprint, entity graph, vulnerable person, and intelligence-style providers behind one NG911 / NG112 retrieval pattern.\n\n## Use Cases\n\n- **Vulnerable Person Alerting**: A dispatcher handling a welfare or medical call receives pre-registered information relevant to vulnerability and care planning without searching manually.\n\n- **Hazardous Address Context**: A PSAP pulls prior premises context or service information that could affect responder safety before units arrive.\n\n- **Caller Context Enrichment**: Subscriber or service context arrives as structured additional data alongside the core call record.\n\n- **Cross-System Emergency Fusion**: An emergency communications centre combines multiple approved sources into one NG911 / NG112-aligned call package instead of asking the call taker to pivot across separate tools.\n\n- **Audit and Assurance Review**: A standards-based log shows which additional data was used during the call and where it came from.\n\n## Integration\n\n- **PSAP NG911 / NG112 Call Handling**: Additional data retrieval becomes part of the live NG911 / NG112 workflow rather than a separate enrichment tool.\n\n- **CAD and Dispatcher Console**: Structured blocks can be surfaced to call takers, dispatchers, and downstream incident workflows as part of the same case context.\n\n- **Voice AI and Silent-Caller Workflows**: Additional data can enrich automated or assisted call handling in the same way it informs human dispatch.\n\n- **NG911 / NG112 Audit and Governance**: Query history and provider outcomes support operational assurance and post-incident review.\n\n## Open Standards\n\n- **RFC 7852**: additional emergency-call data follows the IETF model for attaching structured supporting information to emergency communications.\n\n- **NENA-STA-012**: the repository aligns returned content to the standard NG911 / NG112-style additional-data block types used by emergency communications environments.\n\n- **NENA-STA-021 EIDO**: additional data can sit alongside the broader emergency incident data object model used in NG911 / NG112 operations.\n\n- **W3C Verifiable Credentials Data Model v2.0**: signed block envelopes can preserve provenance in a portable, standards-based verification model.\n\n- **Ed25519**: cryptographic signing of additional-data envelopes uses an open modern public-key signature standard.\n\n- **JSON**: additional-data blocks remain easy to exchange across NG911 / NG112-aware systems using a standard structured payload format.\n"}