Skip to content

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.

An empty hospital waiting area, fixed seating along a tiled corridor.

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.

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.

Powerful. Responsible. Pensieve.

Get started