Product walkthrough

Follow one patient from intake to follow-up.

See what your team manages, what patients do next and where licensed clinicians, pharmacies and delivery partners take over.

Browser-only simulation. Jordan Hale is fictional. Tour actions change temporary browser memory, send no requests to care or payment APIs and reset on reload. Native application workflows require normal sign-in and separate access approval.

Before a native walkthrough

Check the release here. An authorized presenter must also run the read-only operator preflight for the selected synthetic practice, including its grant expiry and simulator inventory.

Release identity has not been checked.

Staff sign-inPresenter checklist
Step 1 of 8

One patient, four roles

Find the real workflow below

Explore by role

These links open the actual product or a labeled lab. A link does not grant access. Use only approved synthetic records and normal role authentication.

What this shows—and what needs approval

Deployed means the engineering is released. Simulated means external responses or this story are synthetic. Preview means orientation only. Unavailable means the product does not support that action.

Live client API keys, raw chart exports through that API, external care-state writes and multi-item carts are unavailable. Five CRM connectors and embedded assistants remain planned. Real clinical, payment and partner use needs independent approval for that client.

Presenter checklist

  1. Use the short browser-only story for public orientation. Restart or reload returns to the same fictional starting state.
  2. Before opening native screens, confirm the current release and run npm run demo:preflight with the explicit approved operator environment. A blocked, missing or expired grant requires reviewed operator action; the tour cannot renew it.
  3. Use normal password/MFA or patient email-code sign-in for the approved practice. Never share staff credentials or patient codes in a prospect URL.
  4. Choose an existing synthetic patient and reread the same authorized record across roles. Follow the presenter runbook for response-loss reconciliation and safe recovery. Browser tour results are not durable evidence.
  5. Do not reset accepted practices to refresh this tour. Only the supported reviewed snapshot/reset tools may reset an approved practice with clinical access disabled.
  6. Coverage owner: EzPharma product/engineering (Luke). Review demo impact with every core-feature release; retain clinical, privacy, partner and client approval boundaries.

Human acceptance still requires an unfamiliar prospect to finish the short tour without help, explain each party’s role and distinguish available behavior from simulations. Physical screen-reader/device acceptance is separate from automated checks.