Skip to content
Pensieve

The operating record a hospital runs on

Pensieve carries the clinical work of the ward and the business work of the back office on one governed record, and presents that work to staff as a set of tools. This documentation states what the platform holds, how it decides access, and where each boundary sits.

Read the documentation
HOSPITAL NETWORKstaff browserorophin bridgerequestsone outbound pathTRUST BOUNDARYone door inPENSIEVE PLATFORMone recordone authorisation decisionone audit entry per changeone door outoutside systems
One entry path in, one exit path out, and the boundary named.

Documentation for the Pensieve platform. Last updated 18 August 2026.

The shared foundation

What holds across every system

One recordEvery system reads and writes one patient record rather than keeping copies.One authorisation decisionEach read and each write resolves against one access decision.One audit entry per changeA committed change carries its audit entry, written with it.One event logSystems react to one another through events rather than direct calls.One entry and exit pathEvery request enters through one path, and every outside connection leaves through one path.Enforced boundariesAutomated checks hold each boundary as the platform is built.

Systems

What the platform is made of

The care systems

Gate

Registers patients, opens visits, and runs the visit lifecycle from arrival to discharge.

Atlas

Holds the patient record, the one place a patient's clinical data lives.

Forge

Carries an order from placement to completion, with a frozen snapshot of each placed order.

Vault

Runs billing and revenue, from a raised charge through invoice, payment and settlement.

The model and access

Nexus Manager

Models the hospital: sites, units, locations, beds, services, assets, people and roles.

Cirith Manager

Decides, for every action, whether a person may take it, and keeps the access log.

The connective systems

orophin

The on-site bridge that carries connections to the hospital's own machines over one outbound path.

Westron

The console where staff configure and monitor the connections orophin carries.

Image study viewer

Reads imaging studies in the browser, tied to the right patient and order.

The workflow and intelligence systems

Cadence

Runs a repeatable multi-step process and shows which step each case is on and what is next.

Quest

Turns due work into scheduled tasks and shows each member of staff their own due list.

Glyph

Builds and runs forms, with validation, calculation, sign-off, and a locked completed form.

Sentinel

Holds the alert ledger, decides when an alert fires, and tracks acknowledgement and escalation.

Raven

Sends a message over the right channel within consent, and keeps the delivery log.

Falcon

Turns hospital activity into governed metrics, and shows the lineage of every number.

Durin

Composes new tools and desktop widgets on the platform's governed data.

The staff desktop

Chamber

A person signs in, lands in the Chamber, and reaches the tools their role and relationships allow.

Critical

The pages a reviewer reads first

Access and audit

Clinical safety

Money

Connection and exit

Deployment and implementation are documented in the Trust Center.

Answers

Questions the documentation settles