NG112 reference
Emergency Apps
Structured NG112 reference page.
112 readiness
Policy, location, routing, and response quality connected in one operational model.
Applications and Data
Emergency Apps
Apps can help users who need accessibility support, language assistance, traveler support or richer incident data. They should not be positioned as a substitute for dialing 112 unless the national authority explicitly supports that service model.
What it does
Emergency apps can provide alternative access, location and data, but they must fit official emergency-service workflows.
Apps can originate emergency data or sessions that complement ordinary 112 access.
How it works
- Collects user, location or incident data through a managed application.
- Routes or forwards the information through an official or authorized emergency path.
- Can integrate with PEMEA for cross-border use where supported.
Key interfaces and protocols
- App APIs
- Location permissions
- PEMEA where used
- PSAP data intake
Systems it interacts with
- PEMEA
- Additional data
- Accessibility
- Location
- PSAP
Common failure modes
- App is unavailable during emergency.
- Public misunderstands coverage.
- Location permission is disabled.
- PSAP receives data outside the call-taking workflow.
Implementation considerations
- Keep dialing 112 as the primary public instruction unless authority says otherwise.
- Design for accessibility and language support.
- Use strong privacy and consent controls.
Standards
- European emergency communications policy
- PEMEA references
Related NG112 technologies
Related country deployments
No country deployments are listed here until independently verified against official or high-confidence sources.
Related articles
Sources
- 112: the European emergency number - European Commission, accessed 2026-08-31
- Next Generation 112 and the new Emergency Services Networks Landscape - EENA, accessed 2026-08-31
Last verified: 2026-08-31