INLOOP
Discharge planning agent displaying on Patient Lists and Patient Charts
Core trick
Claude reads each inpatient's note, problems, vitals, and labs to return discharge milestones, blockers, and a suggested disposition on the patient list.
Description
Discharge planning agent displaying on Patient Lists and Patient Charts
README excerpt
# inloop — discharge-planning viewer for care teams Made by [Jhonatan Munoz MD](https://www.linkedin.com/in/jhonatan-munoz-md-00735992/), [Caroline Luu](https://www.linkedin.com/in/carolineluu/), and Claude. View the demo [here](https://www.loom.com/share/ab67edc64dc640838f4c9ac1e47db371). Play with prototype: [inloop.carolineluu.com](https://inloop.carolineluu.com/) A web interface for doctors and multidisciplinary care teams to review their inpatient list and open a patient chart. The differentiator over a typical patient-list app is **discharge planning**: for each patient, Claude reads the clinical note, problems, vitals, and labs and returns clinical milestones, the physician's remaining next steps (including orders to place), blockers, and a suggested disposition. This helps the team discharge-plan early and move patients efficiently without sacrificing their perception of care. > Prototype built on **synthetic** data. AI output is decision support, **not** > a substitute for clinical judgment. ## Two screens 1. **Patient list** (`/`) — an inpatient census with **Location** (bed), reason for encounter, admit date, LOS, and a **sortable Discharge readiness** column (defaults to Ready-first). Badges are `Ready` / `Not ready` / `Not assessed`. 2. **Patient chart** (`/patients/[id]`) — an EHR-style chart on the left (patient banner with a Location/Admitted/LOS/Status facts row, a vitals tile row, and titled sections: encounter reason, problem list, medic