Clinical and hospital operations, without leaking the access pattern
For DoH, DHA and MoHAP-licensed providers. The agent supports the records desk and triage; prescribing, ordering tests, discharging and writing records always need a clinician.
- Regulator
- DoH / DHA / MoHAP
- Output wall
- profile rules only, no output wall preset
- Deployed job
records-desk
What the agent does
The deployed agent runs a records desk. It records an access receipt for every episode it touches, using an episode tag the patient controls, drafts a triage recommendation with the model and manifest hashes, and waits for a named clinician to confirm. Exporting records or sending anything outside the provider is forbidden by the profile.
Never allowed: tool.export_records, tool.send_external
Needs a human approval: tool.prescribe, tool.order_test, tool.discharge, tool.write_record
Prices per proven outcome
| Outcome | Unit | Proof (receipt) | Price (AED) | Human gate |
|---|---|---|---|---|
| Recommendation confirmed by a named clinician | per handoff | health.confirmation | 11.00 | yes |
| Triage episode handled | per resolution | run.ok | 7.35 | no |
Receipts that prove the work
- Access receipt: episode tag, actor, purpose, time
- Recommendation receipt: model and manifest hashes, the outcome proposed
- Clinician confirmation: signed with the clinician's own key
- Break-glass receipt: emergency access with a stated reason
- Tool receipt: every tool call with its arguments hash and result hash
- Run receipt: the outcome of the whole task, chained to every step
A worked example
A nurse asks the agent to prepare a triage summary for episode tag ep-7c1. The agent records an access receipt with purpose triage, drafts the recommendation, and the attending clinician signs a confirmation receipt with their own key. The escrow for this outcome releases on that confirmation, not on the agent's own say-so.
Frequently asked questions
Does patient data go on the ledger?
No. Receipts hold an episode tag derived from a seed the patient holds, the actor, the purpose and a timestamp. Content stays in your systems.
What is a break-glass access?
An emergency access signed by the clinician with a stated reason. It is receipted immediately and listed as pending review in the profile audit until closed.
Can the agent prescribe or discharge?
No. Those tools are human-gated in the profile. The agent drafts; the clinician's signed confirmation is the receipt that counts.
Why is there no uniformity verdict for healthcare?
Individualised care is correct. The profile audit checks the protocol trail and pending break-glass events instead of forcing one rule on every case.
Where do the files live?
In the engagement's data room, encrypted at rest with a per-client key. Retention and erasure are receipted; offboarding destroys the key.
Try it on five tasks, free
A trial gives you 5 tasks over 14 days with no price and no escrow. Sign in with Zanii ID, pick an agent, and read your first receipts.