Getting started
What to do next, in order.
This page is the briefing: the three ways to start, what happens after you write, and what we will ask you for. Everything after that runs inside the Trust Center, where the evaluation, the paperwork and the purchase are handled.
Start here
Three ways in.
Write to us on this page
The shortest route, and the form is at the foot of this page. Name your hospital, the systems you run today and what you want to see. A person reads it and answers you.
Request access to the Trust Center
For a team that wants to read before it talks. The security posture, the architecture, the deployment models, the interoperability position and the commercial framework are open; the evidence a security review asks for is released once the non-disclosure agreement is signed.
Begin the purchase directly
A clinic on the subscription tier needs no conversation to start. Purchase is initiated inside the Trust Center, and the Trust Center administrator carries it from there.
The route
Three doors, one room.
The sequence
What happens next.
One. Make contact, or request access
The form on this page, or an access request at the Trust Center. A clinic buying on the subscription tier can do neither and begin in the Trust Center itself.
Two. Receive the evaluation centre and the Trust Center
Access is granted to a named person at a named hospital. The public tier opens immediately. The gated tier opens on a signed non-disclosure agreement, and each release is recorded.
Three. Read the brief for your facility
A briefing written for a hospital of your size and shape: what onboarding involves, what is asked of your team, and what each step waits on.
Four. Complete the evaluation forms
The forms establish what you run today, how your hospital decides, who signs, and what the deployment has to meet. What you write in them becomes the scope of work.
Five. Get a response
A written answer: whether Pensieve fits, what deploying it would involve, and the commercial shape. If the answer is that it does not fit your hospital, that is the answer you get, and you get it at this stage.
Six. Forward deployed engineering
Engineers survey the hospital, connect the systems and machines you already run, build the roles and the workflows against your own structure, and rehearse the cutover on a dummy site.
Seven. Go-live
One workflow at a time, in production, against a parallel run.
Every step after access is handled inside the Trust Center, behind authentication. The plan, the brief, the forms, the questions, the signatures and the payments sit in one place with one record of what was agreed, which is the reason none of it happens by email.
Timing
Two clocks.
Two clocks run, and neither waits on the other. The commercial clock closes when the fee that commissions the work is settled. The delivery clock runs from survey to go-live on its own schedule. Because the money question is answered early, nothing downstream is still negotiating a price while the build is running.
Why they are held apart
A price that depends on a measured result cannot be agreed before there is anything to measure: a baseline, a method, an attribution rule and a dispute process are each a negotiation of their own. Holding the fixed part apart from the measured part is what lets a hospital sign in weeks. The measured part has its own baseline window, and it opens after go-live.
Why no day count appears here
The elapsed time is set by your board calendar, your security review and your procurement route. We control none of the three, so a number printed on a web page would be a guess about your institution. The dated sequence for your own facility, with a named owner on both sides of every step, is the mutual action plan in the Trust Center.
The two clocks
The paper and the engineering run together.
Commercial
How it is priced.
Three components. A deployment and activation fee, paid in advance, which covers provisioning, configuration, master and tariff setup, migration, the integration build, training and cutover. A platform fee, recurring and in advance, which carries the availability commitment, the support escalation, the release stream and the security programme. A value share, in arrears, computed on a published methodology and invoiced only once the value statement is accepted.
The threshold is the platform fee
Value share begins above a threshold set at the annual platform fee. Below that line it is nil, so the platform earns nothing extra until it has paid for itself. It is capped as well, both as a multiple of the platform fee and as a share of the hospital’s own revenue. An uncapped share is an option written against your own improvement, and no hospital should sign one.
Two things we will never do
Price per bed or per user, in any market. Benchmark against a hospital management software list price. The comparison that decides whether this is worth buying is your own operating leakage: the charges never captured, the consumables never billed, the discounts nobody approved, the payer disallowances nobody appealed, the cash that never reconciled and the stock that expired on the shelf. Where that number is small, we say so at qualification.
For your chartered accountant
Healthcare services supplied by a clinical establishment are exempt, so most hospitals cannot claim input tax credit on software, and the hospital absorbs the tax on a platform invoice as a cost. Every proposal states that, names the withholding section and rate, and carries the invoice format to match. The vendor compliance pack reaches your hospital as one bundle, addressed to it by name.
Where the figures are
On an order form issued to a named hospital, with the segment band they were derived from and the payment schedule beside them. The methodology behind the value share sits in the contract documents, and it is published so your finance team can read it before anyone quotes you anything.
Where the work happens
The Trust Center.
The Trust Center at trust.pensievelabs.org is where Pensieve is evaluated and where it is bought. It is a separate system from this site, with its own authentication, its own document register and its own audit trail, and it holds the one authored copy of every legal, security and privacy text we publish. Each document carries a version, a last-modified date and a SHA-256 hash, so the text your reviewer quotes and the text we hold are the identical bytes.
Open to anyone
The security posture and the security policy, the architecture, the deployment models, the interoperability position, the jurisdictions we operate under, the subprocessor register, data residency, the exit and data-export position, the commercial framework, the status page, the update feed, and the register that explains how every artefact is classified and reviewed.
Released under agreement
The evidence a security review actually asks for, and the answers to the questionnaires it arrives with. Access is requested by a named person at a named hospital and released once the non-disclosure agreement is signed. Every release is recorded, and it can be withdrawn.
The workspace, once you are inside
The mutual action plan with dates and named owners on both sides. The onboarding brief for your facility. The forms and checklists, the questions channel, the document library, the signatures, the payments, and the offboarding and exit path. The whole of the sales and purchase process is handled there, which is why none of it happens by email.
Why it is a separate system
A marketing site holds no copy of a governed text. The legal pages on this site are fetched from the Trust Center when they are requested and render its bytes, so a policy cannot be current in one place and stale in the other. A stale privacy policy is a false statement about how a hospital’s patient data is handled.
Before the first call
Read these first.
Four teams usually have to agree before a hospital moves, and each of them has a page written for it. Sending the right page to the right person before the first call is the single fastest thing you can do here.
For the security officer
The guarantees the platform is held to and the mechanism behind each one: one authorization check on every read and every write, an audit written in the same transaction as the change, and a patient lens at the database read path. The governed security documents are published with a version, a date and a checksum.
For the CTO or CIO
The core systems every tool is required to route through, and the automated check that fails the build when a tool tries to go around one. It answers the lock-in question directly, because export speaks the same standards the import does.
For the team that owns the interfaces
Which of the systems you already run Pensieve speaks to, over which protocols, and how one outbound connection carries all of it with no inbound opening into your network. Bring the list: the HIS, the LIS, the RIS-PACS, the pharmacy system and the analysers on the floor.
For whoever owns the rollout
Where Pensieve runs, what each deployment model changes about what go-live waits on, and the sequence from survey through parallel run to cutover.
For the person who will live with it
What the relationship is after cutover and who you deal with. The engineering continues past go-live, because the hospital that runs in year two is a different shape from the one that was surveyed.
On response times
Every message is read by a person, and the answer comes from that person. We print no number of hours here, because a response commitment belongs in an agreement where it binds us. Ours is in the service level agreement, which the Trust Center releases in full. What you get back is a written answer to the question you asked and a named person to continue with.
What to bring
Before you write.
A first conversation runs on facts about your estate. What you are shown is built on records we generate to match the shape of your hospital.
What we will ask for
- The systems you run today: HIS or EMR, LIS, RIS-PACS, pharmacy, billing, and the analysers on the floor.
- Beds, sites, and daily outpatient volume. Size changes what we would recommend, and sometimes whether we recommend anything at all.
- The department that hurts most, and what it costs you: staff hours, delayed discharges, write-offs.
- Who signs. The person who approves the decision, and the person who controls what changes on your network.
- How your hospital decides and how it buys. An owner who can sign, a committee, a board, or a tender.
What we will never ask for
- Patient data. No live extract, no anonymised sample, no screenshot of a real record. We need none of it to show you anything.
- Credentials or access to your existing systems. An interoperability review runs on vendor names and protocol lists.
- A signature before you have seen the software running on work shaped like yours.
- Your budget before we have told you plainly whether Pensieve fits.
On confidentiality
Hospitals run Pensieve today, under NDA. We will not show you their records, and we will not show yours to the hospital that comes after you.
Contact
Write to us.
A person reads every message and answers it. Name the hospital, the systems you run today, and what you want to see.
Everything after this happens in the Trust Center.
Request access and the evaluation begins there: the brief for your facility, the forms, the governed documents, and the purchase.