Pensieve Labs
Pensieve documentation
Learn how Pensieve solves the most complex real problems in a hospital, while maintaining data sovereignty and governance, for all use cases ranging from clinical to managerial.
Pensieve Labs publishes this documentation beside the Trust Center and Pensieve Learn.
Slide 1. The Chamber desktop. 1200 by 630
Trust Center
Deployment, controls and assurance
The documentation states what the platform does. The Trust Center holds the material a reviewer needs beside it: how Pensieve is deployed, the controls that hold in operation, the data handling position, and the implementation record. The two surfaces are kept in step, and each points at the other where a question crosses the line between them.
Open the Trust CenterTrust Center. 1200 by 630
Capabilities
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
The connective systems
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.
Architecture
What holds across every system
Basics
The questions a hospital asks first
The record. 1200 by 630
What the record holds
One patient record carries the clinical data a hospital writes, and every system reads and writes that same record.
Access. 1200 by 630
How a permission is decided
Every action resolves against one access decision, taken from the person, their role and their relationship to the patient.
Audit. 1200 by 630
The audit trail
A committed change carries its audit entry, written with it, so the record of what happened cannot drift from what happened.
Access log. 1200 by 630
Who saw this record
Reads are logged as well as writes, so the question of who opened a patient record has a direct answer.
Visits. 1200 by 630
The visit lifecycle
A visit opens at arrival and closes at discharge, and the work of the ward hangs from that one thread.
Orders. 1200 by 630
The order lifecycle
An order runs from placement to completion, carrying a frozen snapshot of what was ordered and by whom.
Billing. 1200 by 630
How a charge is created
A charge is raised from recorded activity, and once posted it stays fixed. A correction is a new entry beside it.
Export. 1200 by 630
Export and exit
The hospital's data leaves in a documented form on request, so the exit route is known before it is needed.