Thesis
The shape of the system
Sets out the organising idea behind Pensieve, why the tools fit together as one platform, and what that shape means for the hospital.
Pensieve is one governed platform rather than a collection of separate products, and this page sets out the organising idea behind that shape. It explains why the tools fit together as one system, and what that coherence means for a hospital.
One platform
A hospital usually runs on a patchwork of systems that hold separate records, keep separate access rules, and write separate histories. Reconciling them becomes a standing tax on the hospital.
Pensieve replaces that arrangement with a single platform. One patient record, one authorisation decision, and one audit trail sit beneath every tool, so the tools read as one system rather than a bundle of separate products.
A tool is a feature area of the platform, such as admissions, the record, orders, or billing. Each tool carries one responsibility and shares the same foundations underneath.
The organising idea
The organising idea is to model the hospital itself, as a connected set of real things and the relationships between them, and route every tool through that shared model.
That model is the platform's ontology: a working digital representation of the hospital, its people, and its patients. Sites, units, beds, services, assets, staff and roles sit on one side; patients, encounters, orders, results, charges and consent sit on the other.
Because access, billing, orders and the record all resolve against the same model, one change to it is understood everywhere at once. A bed moves, a role changes, or a service opens, and every tool reads the change together.
Only the record tool holds a patient's clinical data. Every other tool asks the record for it rather than keeping a copy, so the record stays the one account of the patient.
Why the tools cohere
Each tool reaches the others through a small set of shared platform capabilities rather than by calling them directly.
Every tool reads and writes one patient record rather than holding its own copy.
Each read and each write resolves against one authorisation decision.
A committed change carries its audit entry, written inside the same transaction.
Tools react to one another through events rather than direct calls.
Every request enters through one path, and every outside connection leaves through one path.
Sharing these foundations is what turns a set of tools into a platform. The interface a person sees is a projection of what the same decision permits, so the screen and the record agree.
What the shape provides
The shape carries through to the hospital as a handful of plain outcomes.
| Separate systems | One platform | |
|---|---|---|
| Shared patient record across tools | Absent | Present |
| One access decision for every read and write | Absent | Present |
| One account of who did what | Partial | Present |
| Tools react without waiting on each other | Absent | Present |
Clinical work proceeds without waiting on back-office work. Placing an order completes on its own, and billing reacts to the event afterwards, so the ward keeps moving while the ledger keeps pace.
One account of who acted
Because a committed change carries its audit entry, the record stays reconstructable. The whole platform answers the question of who did what, and when, from one trail.
The rest of this section takes the shape apart. Read how each request enters and leaves through a single controlled path in one door in and one door out.