
Technology
A small system you can inspect.
The rules, the data model, the closure gate and the code are all open for a reviewer to read.
The stack
Small parts, each one readable.
Native Android app
Kotlin and Jetpack Compose. Patient, clinician and coordinator roles in one app.
Case engine API
Node.js on Vercel. Every rule, permission and the closure gate runs on the server.
Safe storage
Private, encrypted storage with checked writes, so no edit overwrites another one.
Speaks FHIR R4
Any case exports as a FHIR R4 bundle with LOINC codes, ready to map to an exchange.
Explainable rules
Fixed thresholds and a combination rule, covered by tests and shown before saving.
Screenlit assistant
A small model behind a strict prompt and a red flag filter, with a safe fallback.
The care case
One record per actionable result, the same for every pathway.
| Field | Purpose | FHIR R4 |
|---|---|---|
| Trigger result and reason codes | Why the case exists | Observation |
| Owner, next action, deadline | Who acts, what and by when | Task.owner, Task.restriction |
| Notification, acknowledgement, understanding | Patient engagement | Communication |
| Referrals with status history | Hand-offs between settings | ServiceRequest |
| Consults and notes | Clinician coordination | Communication, Annotation |
| Closure record | Proof the loop closed | Task.output |
| Audit trail | Accountability | AuditEvent |
Try the full loop on Android.
Free demo build with fictional patients and clinicians. No sign-up.