Stakeholders
Accountable to every party the record serves.
Most companies answer this question with a roster of photographs. A hospital’s record outlives the people who write it, and it is meant to outlive the company that sold the hospital its software. So the list on this page is not employees. It is the parties with a claim on whether that record is kept correctly, and what each claim obliges us to build.
The thesis
The architecture answers to a single thesis.
Pensieve is built on one thesis: a hospital should run on one record, one system of permission, and one audit trail, beneath everything else the software does.
Every tool on the platform is built against that thesis. Accountability for the architecture is held at the top of the company.

Who has a stake
Six claims on the record, and what each obliges.
Listed outward, from the person the record is about to the country it is kept in. Each has a claim on whether the record is kept correctly, each claim obliges a specific mechanism, and every mechanism below is linked to the page that specifies it.
- 01. The person the record is aboutThe record is read, most often, in a room the patient is not in. They cannot audit us and they cannot see the log. Their consent has to be something the system checks on every read. What it obliges: consent is a first-class data object on a two-plane model. The authorization system reads it on every access, and withdrawal is recorded on the record itself.
- 02. The physician who signs the noteA signature is an assertion of fact by a named person, and it stays attached to that person for as long as the record exists. They are entitled to a record that cannot be altered behind them. What it obliges: every action is audited in the same transaction as the change, then archived to write-once storage. An audit written separately can be incomplete. This one cannot come apart from the change.
- 03. The engineer carrying the pager at 3amAt three in the morning nobody reads the whole system. They read what the system tells them. That obliges us to keep the number of places a failure can hide small, and to write the rules so that a machine enforces them. What it obliges: one path to the database, one authorization check, one audit trail, one way out to the network. A graph-wide check fails the build the moment a tool tries to go around any of them.
- 04. The auditor reading the trail years laterAn audit is read long after the event, by someone who was not there and has nobody left to ask. Everything they need has to already be in the trail, and it has to still parse. What it obliges: the audit is written at the moment of the change, never reconstructed from logs afterwards, and the record leaves on the open standards the rest of the field already reads: HL7 v2, FHIR R4, and DICOM.
- 05. The institution that must outlast usA hospital is a hundred-year institution. Its record must outlast any vendor, Pensieve included, and the exit stays visible the whole time you are inside. What it obliges: the record exports on open standards, and the bridge lets Pensieve run beside the systems already installed, leaving each of them in service. Portability is a property of the architecture, so it cannot quietly lapse.
- 06. The villageThe record that matters is not written only in metro tertiary centers. It is also written where the line drops, the staff are fewer, and no vendor sends an engineer. Software that works only where the infrastructure is good is a claim about the infrastructure. What it obliges: the on-premise bridge keeps a durable outbox, so machine traffic queues through an outage and delivers on reconnect. We are also direct about the boundary: the staff web app is a cloud app and still needs a connection.
Every obligation has an owner.
Responsibility is assigned by obligation. The people who build the software answer for what it does inside a hospital.
The work is organised in three kinds of role, and open roles are published on the careers pages.