They Declined the Meeting. I Built the App Anyway — Local-First, No Cloud, No Stored Health Data
Description and use
After a hospital declined to evaluate a patient‑prep architecture, the author built Radiology Companion™ v5, a local‑first app that delivers prep instructions, verifies receipt, and stores no health data.
Problem
A hospital system declined to evaluate a patient‑prep architecture, yet patients experienced missed appointments because the system’s sent‑flag did not verify actual delivery of prep instructions.
Outcome
Within seventeen days, a single developer built a fully functional local‑first app that eliminates the missing‑delivery problem, protects patient data, and provides a teach‑back mechanism to ensure adherence.
Workflow
- 1. Hospital uploads prep instructions to its portal. 2. Portal logs instruction as sent. 3. Radiology Companion retrieves the instruction locally. 4. App presents each preparation step to the patient, reading it aloud. 5. Patient confirms completion of each step. 6. App records completion locally and can export a paper or calendar entry. 7. No data leaves the device; the hospital only supplies its URL for branding.
- 8. The app’s local‑first design ensures no cloud or stored health data.
- 9. The system supports twenty languages and uses institutional demo libraries (Mayo, Johns Hopkins, Cleveland Clinic).
Evidence
Seventeen days after the decline, the thing existed anyway: Radiology Companion™ v5, a working local‑first reference build.
No cloud. No stored health data. Nothing about the patient leaves the device.
The system’s ledger says sent. The patient’s ledger says lost.
The app invents no prep. The canon is cited; the app is the delivery layer that gets the sheet out of the app: paper, calendar, read‑aloud.
- Record date: 2026-10-25T16:26:10.482Z