Concept explainer
How it fits together
Shows how the tools connect, how work moves between them and how one patient event travels through the record, orders and billing.
The tools connect through one shared record, one authorisation decision and one event log. This page shows how work moves between them, and how one patient event travels through the record, orders and billing.
How tools connect
The tools stay separate in what they do and joined in what they read. Each one holds its own work, and all of them meet at the same governed record and the same access rules.
| What is shared | How the tools use it |
|---|---|
| One record | Every tool reads from and writes to the same patient record. Only the record tool holds clinical data, and the others ask it for what they show. |
| One decision | Every read and every write clears one authorisation decision, so the tools agree on who may do what. |
| One event log | A tool announces what it did, and other tools react in their own time. |
| One audit entry | Each change is written with the entry that records it, so the trail follows the work across tools. |
One record
Only the record tool holds a patient's clinical data. When another tool needs a diagnosis or a result, it asks the record rather than keeping a copy. This keeps one account of a patient true, and it keeps every tool reading the same version of it.
Work moves as events
Tools react to each other through events rather than by calling each other directly. A tool announces that something happened, and the tools that care about it respond in their own time. Clinical work continues while back-office work follows, so placing an order proceeds while billing and scheduling pick it up behind.
One event travels
A single order shows the whole shape. Follow one medication order from the clinician's screen to the ledger and the due list.
- 1
Place the order
A clinician places the order in Forge inside an open episode. Forge freezes a snapshot of the orderable as it stands, so a later catalogue change leaves the placed order alone.
- 2
Write it to the record
The order attaches to the episode in Atlas, so the patient record carries what was ordered and when.
- 3
Raise the charge
Vault hears that a chargeable order was placed and raises a charge that carries the price in force at that moment.
- 4
Schedule the doses
Quest hears the same event and turns the medication order into due doses, each with a time, on the right person's due list.
One event reached the record, billing and scheduling, and each tool acted on it while the others carried on.
The boundaries hold
Every request enters and leaves the platform by one controlled path, and every link to an outside system leaves by one outbound path. The platform holds its tool boundaries in code, and an automated check fails the build when a tool reaches another by a path the platform holds closed. The effect is that the connections between tools stay the ones on the map.
Read how the system is shaped behind one door in and one door out.