Protocols & pharmacist-approved guidance
Separate intake rules from reply guidance and approve shop-specific versions without AI rewriting.
On this page · Jump to a section
Before you begin
A real pharmacist reviewer, shop sources and a sandbox for Thai/English testing.
Where to go
Pharmacy Protocols / Pharmacy Guidance
Visible menus may vary with language, permissions, app version and shop configuration.Follow these steps
- A new protocol starts DRAFT. Validate fields, red flags, triggers and completion, then submit it. APPROVED is still inactive until the enable switch and environment allowlist agree.
- Guidance applies to deterministically classified question types. A pharmacist edits a draft, previews real shop facts and approves the shop version.
- Editing APPROVED guidance returns it to DRAFT before a new version can reach customers. Missing, slow or malformed reads fall back to the standard handoff.
- Customers receive the pharmacist-approved wording verbatim; AI does not translate, shorten or elaborate it. Emergency routing always runs first.
- Test guidance, handoff, emergency and missing-shop-placeholder cases; template tokens must never leak to customers.
How to verify success
Protocols run only when every gate agrees, customers see only APPROVED guidance and edits require re-review.
Limits & things to check
Starter templates are not ready clinical advice, and approved sale policy is not guidance approval.
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.