Coordinate the rollout.
Manage the operational side of a Critical ID programme: people, assignments and deployment status as those features are developed.
04 / PRIVACY & SECURITY
HomeCritical ID is being built around a simple separation: organisations coordinate identification; individuals manage personal emergency information; responders see only the appropriate emergency view.
01 THE BOUNDARY
Managing a programme does not automatically create a right to read personal health information. The emergency journey has its own restricted access rules.
Manage the operational side of a Critical ID programme: people, assignments and deployment status as those features are developed.
Provide and update personal emergency information through an owner-managed experience.
A validated product scan opens a limited emergency view. It is not unrestricted access to the underlying profile.
02 ACCESS BY PURPOSE
The current prototype uses owner-scoped profile access, tenant-bound encrypted health data and a restricted emergency view after product validation. The wider privacy, access and operating model remains part of release work.
03 PRODUCT STATUS
This page describes the design approach and current development work. It is not a certification statement or a legal privacy notice.
Owner checks for core profile information, encrypted tenant data and a limited emergency projection after a validated scan.
Broader access tiers, operational audits, recovery, retention, live integration testing and a full production security review.
No external certification, public-sector approval or completed production accreditation is claimed here.
DISCUSS THE REQUIREMENTS
Talk to us about your organisation’s access, privacy, security and procurement requirements.
Talk to our team