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.
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.
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.
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.
Governed by construction
How one request moves through the platform.
Identify
One login, shared across every tool, establishes who is asking.
Authorize
Cirith checks the request against the person’s role and relationships, on this read, and on this write.
One door
There is a single path to patient data. No tool keeps a private back channel to the database.
Record
What happened is written to a shared event log, so other tools react without holding up the first.
One path out
Anything bound for an external system leaves by one governed route, over the orophin bridge.
The tools, one platform
Everything a hospital does, on one record.
- GateThe care cycle: admissions, appointments, and visits, from arrival to discharge, on one record.
- AtlasThe patient’s clinical record: one chronological timeline every other tool reads and writes.
- ForgeThe order system: one order (a drug, a test, a scan, a consult, or a form) carried through to the result.
- VaultBilling and the revenue cycle, run on the same record as the clinical work.
- GlyphThe form builder and fill engine: a hospital designs its own forms, and a person confirms every assisted entry.
- QuestScheduling off the record: dose schedules, due cards, and patient reminders.
- CadenceThe operations workflow engine: a hospital’s own processes, run as governed workflows.
- RavenOne communications layer for the whole hospital: SMS, email, WhatsApp, voice, push, and app notices.
- SentinelThe alert ledger and rules engine: clinical and operational alerts, acknowledgement, and escalation.
- FalconThe analytics and intelligence layer, built on the governed record.
- VigilAccreditation and quality: NABH and JCI evidence as the exhaust of daily work.
- DurinA no-code app builder: staff build their own apps on the platform’s governed data.
- CorneaThe site simulation studio: model and rehearse a site’s configuration before it goes live.
- WestronThe interoperability console: configure and monitor every connection to external hospital systems.