Healthcare
Procedure & surgery checkpoint
Add an identity checkpoint before a procedure.
Operational journey
- 01Select order
- 02Verify identity
- 03Check order & site
- 04Perform clinical safety checks
- 05Team confirms
- 06Record event
The right person is the start.
The right context is the next requirement.
| Component | Scenario application |
|---|---|
| Actors | Patient; clinical team |
| Authoritative identity | HIS / Procedure order |
| Purpose | Add an identity checkpoint before a procedure. |
| Trust service | Verify 1:1 |
| Decision | VERIFIED / NOT_VERIFIED / RETRY / REVIEW_REQUIRED |
| Policy | Organization-, workflow- and version-specific approved policy. |
| Evidence | Patient; order; team; location; result; fallback. |
| Integration | Verification API |
| Status | Solution scenario - deployment validation required |
Exceptions & alternatives
Verify the right person.
Do not replace clinical checks.
| Control | Applicability boundary |
|---|---|
| Palm verification | Supports identity verification; does not establish the correct medication, dose, specimen or procedure. |
| Representative | Keep representative and patient identities separate; check authority to act. |
| Emergency / unable to use palm | Do not delay care. Use the approved alternative identification procedure. |
| Hygiene | No reader contact in a contactless configuration; this does not establish elimination of infection risk. |
Start with a controlled PoC.
Define purpose, devices, risks and acceptance criteria before scaling.