Local build · mocked data · no external connections
A referral rail for outpatient imaging.
A doctor writes a referral. The patient gets a link, sees real prices, picks a center and pays. Shyft holds the money and releases it to the center after the scan. The referring office is never charged.
Walk the whole thing
One referral, end to end, on mocked data. Every step below actually moves state.
- 1In the referring office, write a referral. You get a link and a QR code.
- 2Open that link. Enter a ZIP, compare centers and prices, choose one and pay.
- 3As the imaging center, the referral is now inbound and paid. Confirm a time.
- 4Mark the service complete — the most consequential button in the product.
- 5As Shyft ops, release the funds. Watch the ledger and the access log fill in.
- 6Try the edges: a declined card (ending 0002), an expired link, an off-list request.
What is real here
- · The FHIR data model from EPIC 02, as real Medplum resource types.
- · The money model kept out of the clinical store, with a double-entry ledger.
- · Per-location fee configuration over a base rate — the fee is data, not code.
- · Organization scoping enforced in the repository, not in the screens.
- · A patient contract that has no field capable of holding PHI.
- · Access logging that records reads, with a named person on every entry.
What is stubbed
- · Medplum itself — the repository is the seam a real client slots into.
- · Stripe: payment and transfer are simulated, including the failure paths.
- · Turquoise Health comparison prices, from a local fixture.
- · The NPI registry lookup, from a local fixture.
- · SMS and email — EPIC 09 does not exist yet, and the UI says so.
- · Identity: the user picker stands in for a provider not yet chosen.