The clinician's app
Electron, React, TypeScript, Node
Runs on Windows, Mac or Linux. Keeps working when the connection drops.
Our main system
the middle man
A.N.C.H.O.R.
Autonomous Navigator for Clinical Healthcare Orchestration & Reliability
ANCHOR keeps track of what a hospital has promised a patient, and chases the things that slip. It runs on the computer in front of the clinician, works without an internet connection, and is still being built.
The parts
five parts
The parts, and how far along each one is
| Area | Part | What it does | How far along |
|---|---|---|---|
| What people see | H.E.L.M. | The screen a clinician works in, and the reasons behind what it suggests | Being built |
| How work moves | Autopilot bus | Passes events between parts, checking the rules each time | Being built |
| The helpers | Specialist agents | Each does one narrow job, and says so when it does not know | Being built |
| Working out what is urgent | OLRHM + TRIS | The maths that ranks what is closest to going wrong | Designed, not built |
| The safety core | Shared kernel | The shared foundation everything else has to go through | Not built |
How it works
a person decides
How a piece of information travels through it
This is the plan. Steps that need the ranking maths are marked, because that part is designed but not yet written.
- 01
Take it in
Only with permission
Appointments, notes, device readings and workflow events arrive tagged with where they came from, who consented, how sensitive they are, and which rules apply.
- 02
Write it down
One record per promise
Every open promise becomes its own record: who owns it, when it is due, where it has got to, what has been tried, and whether we know the full picture.
- 03
Work out the pressure
Planned - not built yet
The ranking maths recalculates how close a patient is to something being missed, every time a promise opens, is fixed, is missed, or is cancelled.
- 04
Put it in order
Planned - and it shows its reasoning
The to-do list is meant to put the most time-critical work first, and show which open promises pushed it up the list.
- 05
A person decides
Always
A clinician makes the call. What was done, why, which version of the software suggested it, whether they overruled it, and what happened next are all recorded.
Where it runs
on your machine
It runs on the machine in front of you
ANCHOR is built to work where clinicians actually are, storing everything locally and encrypted. Bigger shared services can be added later, but nothing basic should depend on them.
Storage
SQLite with SQLCipher
Encrypted on the machine, with no setup. Patient names must never appear in plain text in the logs.
The thinking, done locally
Ollama, Whisper, deterministic rules
Transcription and AI run on the same machine. Anything an AI produces can never be the only reason care is stopped.
Shared services
Kafka, NATS, Vault, Terraform
For running across a whole hospital later. None of this is built.
Next
live, not slides
See it working.
We show the working part live. We do not send screenshots of things that do not exist.