Emergency QR access

The right information for a paramedic, in seconds โ€” and only that.

Each person has a pre-approved emergency protocol. In an emergency, staff make three decisions โ€” who is responding, why, generate โ€” and hand over a QR code. The responder sees exactly what the protocol allows, for a limited time.

๐Ÿ–ฅ๏ธ Care Office ๐Ÿ“ฑ Carer app ๐Ÿ‘จโ€๐Ÿ‘ฉโ€๐Ÿ‘ง Family portal ๐Ÿ  Client portal
For the responder

Identity first, then the essentials

The responder gives their name, organisation and an identifier before seeing anything. They get allergies, current medication and the documents the protocol includes โ€” with medication clearly marked as provisional when it is not fully reconciled.

  • No account or app needed for the responder
  • Each device needs its own acknowledgement, so a forwarded link still asks who is reading
  • Medication is never shown as current when it is not
  • The page closes itself the moment the session is revoked
Protocol

Approved in advance, versioned

The protocol has an owner, reviewers, effective and review dates, consent and legal basis, and a scope for each type of responder. It moves from draft to review to approved โ€” and nothing can generate a code without an approved protocol.

  • Responder scopes decide fields, documents, verification and maximum time
  • Readiness shows when something is stale, like an overdue review
  • A senior can block a protocol for a critical discrepancy
  • Changes during a live session are detected and applied
After the event

Close-out and review

When the session ends it is closed out to the incident and the person's chronology, and a post-event review is opened. The office has an oversight view of every session and an assurance view over time.

  • Sessions expire automatically and are swept every minute
  • Extensions need a senior, a reason and a hard maximum
  • Every allow and deny decision is recorded
  • Events are hash-chained so the record can be verified
Rules enforced in code

Fast in an emergency. Strict about data.

999 first

Never a condition of calling for help

Every refusal and every responder page says to call 999 first.

Scope

From the protocol, not the request

Fields and documents come only from the approved protocol. There is no generic "Other".

Expiry

The clock starts at first scan

Unscanned codes die after 60 minutes; an idle responder must acknowledge again.

Tokens

Only a hash is stored

The code is random and opaque. Verio stores its hash, never the token itself.

Revocation

Immediate

Revoking ends the token and every device grant together.

Exceptions

A fresh session, not a wider one

Escalation closes the old session and opens a new one with a recorded reason.

Connected to

Works with the rest of Verio

See Emergency QR access

We'll trigger a session and show the responder's view on a phone.

Book a demoAll features