Skip to content

The Pensieve platform

One platform the whole hospital runs on.

Pensieve is one integrated platform for a hospital’s clinical, operational, and financial work. Staff use it as a web app in Chrome. Every tool lives inside it, on one patient record, over the core systems each is required to route through.

SCREENSHOTThe Chamber, the desktop shell staff land in: a persistent bar across the top, a dock of full-screen tools, one tool open. Real product UI.SCREENSHOT, 16/9

One product

Move past the standing integration project. The tools sit inside one platform.

What a hospital runs on today

One system for admissions, another for the lab, another for imaging, another for billing, and spreadsheets for the gaps. None of them share a record, a permission model, or an audit trail.

What replaces it

A single platform. Inside it, the work is organised into tools, full-screen applications for one job each: admitting patients, viewing the record, placing orders, billing. There is one purchase and one login. Every tool reads and writes the same record, under the same permissions, into the same audit trail, because they all sit inside the one platform.

How it’s built

The tools. The core systems. One bridge.

DIAGRAMThe platform map: the tools as a top row, the core systems as an enforced layer beneath them, and the orophin bridge at the base reaching out to external hospital systems.DIAGRAM, 16/9
Every tool sits on the core systems, the layer nothing gets past; the orophin bridge reaches the machines the hospital already runs. Keep these three layers straight, and the whole platform makes sense.

The structural guarantees

Three things are always true.

  • One recordEvery tool reads and writes the same patient record. There is no second copy to reconcile, drift, or contradict the first.
  • One authorizationNo tool implements its own access control. Every read and every write routes through one check, Cirith, so a user cannot see or touch what their role doesn’t allow.
  • One audit trailEvery action is recorded in the same transaction as the change, then written once and never altered. Who did what, when, and with whose permission, all in one place.

The workspace

Staff log in and land in the Chamber.

The Chamber is a desktop of tools.

A persistent bar across the top, a dock of full-screen tools, and pinnable widgets. Staff open a tool the way they open an app on a Mac.

What a person sees is a projection of their permissions.

In the dock, and inside each tool, they see only the tools, screens, and patient data their role allows.

Read more about the Chamber

SCREENSHOTThe Chamber with the dock visible and a tool open; the global bar, the dock, and a pinned widget annotated. Real product UI.SCREENSHOT, 4/3

One record, one permission model

Tools don’t block on each other. They react through events.

Placing an order doesn’t wait on billing.

Tools notify each other through a shared event log rather than calling each other directly, so the clinician moves and the paperwork follows.

No tool talks to the database directly.

No tool invents its own login check or opens its own connection to the outside world. This is enforced: an automated graph-wide check fails the build the moment a tool tries to bypass a core system.

DIAGRAMOne tool emitting an event that several others react to independently (a Forge order fanning out to nursing, pharmacy, billing, and the schedule), none blocking the first.DIAGRAM, 4/3

Governed by construction

How one request moves through the platform.

  1. Identify

    One login, shared across every tool, establishes who is asking.

  2. Authorize

    Cirith checks the request against the person’s role and relationships, on this read, and on this write.

  3. One door

    There is a single path to patient data. No tool keeps a private back channel to the database.

  4. Record

    What happened is written to a shared event log, so other tools react without holding up the first.

  5. One path out

    Anything bound for an external system leaves by one governed route, over the orophin bridge.

Powerful. Responsible. Pensieve.

Get started