AlevantDischarge NavigationStanford Medicine
Synced · live demo state
Discharge Workflow Map
James's path through the machinery — readiness is colored by their live gate status. Hover to trace · click any card for its checklist.
Patient pathJames ThompsonView the system model →
Plan readiness — 46 of 110 checklist items confirmed (46 auto-confirmed from the EHR · readiness cards colored by gate status). Open any lit card and press the checkmark to confirm the rest.
case opens at admission

Readiness workstreams

parallel from day 1 · event-recomputed · revocable · hard/soft gates

Post-discharge needs — the “what”

structured Need objects · fulfilled-confirmed or risk-accepted, never silent

Services — who fulfills

skill level → coverage predicates → registry match → confirmed referral

Place of disposition — where

candidacy → choice w/ quality data → acceptance + auth · UB code derived from setting × services · curated to operationally-distinct paths — full NUBC/UB-04 set in the rule library

Home / community
Post-acute facilities
Long-term / custodial
Specialty inpatient transfer
End of life
Non-medical / exception
Disposition modifier

Logistics — how the patient gets there

mode derived from positioning × clinical needs en route × behavior × funding × timing

disposition code derived here
Edges:assessment flowneed derivationneed → serviceservice → settingsetting → transport→ discharge → loopreplan loop (ALC → re-derivation)★ scenario note on card
Demo concept · no PHI · click any card for its airline-style checklist · scenario chips light the path a real patient takes through the same machinery.
Disposition column shows the operationally-distinct paths. The complete NUBC / UB-04 patient-discharge-status code set — including the codes folded out of this view (09, 30, 40–42, 69, 70) and the full 81–95 planned-readmission band — lives in the rule library (src/lib/discharge/discharge-status-codes.ts) with citation; the map is a curated view of it.