Emergency routing, clinical handoff & prohibited promises
Put emergency routing ahead of every workflow and communicate only evidenced status without diagnosis.
On this page · Jump to a section
Before you begin
The team has reviewed fixed emergency wording, duty ownership and the shop's emergency-call procedure.
Where to go
Pharmacy Queue / Inbox / Pharmacy manual
Visible menus may vary with language, permissions, app version and shop configuration.Follow these steps
- Emergency-shaped text must use the fixed emergency path before profile, history, catalog or AI. Never convert it into commerce or normal intake.
- Medication suitability, dose, interaction or unsupported symptom questions use clinical handoff or APPROVED guidance only, never general staff/AI knowledge.
- Read Queue/Inbox state from the system. Say received, provide a case reference or claim notification only when that evidence was created successfully.
- A shift stamp does not prove current pharmacist presence. Case expiry is not a response ETA, and no detected red flag does not mean safe.
- After the event, manager and pharmacist review routing, delivered wording, case state and audit without copying unnecessary patient data to support.
How to verify success
Emergency replies precede AI/commerce, handoff makes no unsupported creation claim and staff can explain the boundary consistently.
Limits & things to check
Text matching is conservative routing, not diagnosis or complete triage; expert review is required before live use.
Ready to try it in your shop
Lessons are free to read. Actual operations require sign-in and the appropriate permission. Use test data for training.