Pharmacy launch rehearsal
Rehearse product policy, counter, queue, evidence, emergency and failure paths with fictional data.
On this page · Jump to a section
Before you begin
A fully migrated sandbox, fictional data, every test role and no real health/prescription data.
Where to go
Test shop → Pharmacy Intake Lab / Queue / POS Readiness
Visible menus may vary with language, permissions, app version and shop configuration.Follow these steps
- Create test SKUs for DIRECT_SALE, short check, pharmacist approval, online-prohibited, prescription, missing policy and quantity-limit cases; test counter and online separately.
- Test counter pharmacist and Queue paths, basket edits, bill cancellation and approval reuse. Fresh authorization is required and quantity limits remain enforced.
- In Intake Lab test consent, missing/conflicting data, red flag, AI-off/failure and manual fill. Attempt approval as an unlicensed user before a real pharmacist.
- Attach fictional evidence and verify access denial. Edit approved guidance back to DRAFT and confirm AI suggestions neither reach customers nor create orders.
- Exercise planned provider/DB failures in sandbox, fixed fallback and emergency routing. Record expected/actual results, tester and remediation owner before soft launch.
How to verify success
Every scenario has observed evidence, a licensed pharmacist signs off the workflow and fixtures/screenshots/exports contain no real patient data.
Limits & things to check
Pure tests and Lab do not prove RLS, provider, hardware or live database behavior; DB/sandbox and clinical review are required before production.
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.