Pensieve
What one record changes for the person it is about.
The patient is the one party in a hospital who cannot see their own record, and the one with the most at stake in it being correct.
Three accounts, and none of them is a customer.
Pensieve has no customer on the record, so the three episodes below were written by us.
Our hospital partners run under a non-disclosure agreement. We publish no names, no logos and no outcome figures, and an invented one would be worse than publishing nothing at all. So what follows is explicitly constructed: three ordinary episodes an Indian hospital sees every week, written to show where a patchwork costs the patient and where the same defect costs the institution.
Read them as illustrations of a mechanism. Every capability named inside them is something the platform does and is stated plainly elsewhere on this site. Nothing inside them is a measurement, a saving, a duration or a result.
The figures this site does cite are sector research with a named source and a link, collected at research. Nothing on that page is a Pensieve outcome either.
The shape of all three
One line through every desk, and a second line under it
Illustrative account, written by us
A man on maintenance dialysis, at two units of the same hospital.
What he meets today
He dialyses three times a week at a satellite unit near his home and comes to the main hospital when there is trouble with his vascular access. Each place holds a different part of him. His dry weight, his last sessions, the access that failed and the transfusion he was given for it live in a register at one unit and in a folder he carries. When he arrives breathless on a Sunday, the team on duty starts from the folder, and if a session was missed anywhere the folder does not say so.
What one record changes for him
Both units are sites inside one tenant, so there is one of him. The session history, the access history, his last set of bloods and the medicines he is actually taking are the same object at both, and the nephrologist at the main hospital opens what the satellite wrote without asking anyone to send it. He is not asked to be his own medical record, and every read of it is on the trail.
What the hospital gets back
A session is an order, and the order raises its own charge at the price of that day, with the consumables issued against it on the same bill. The scheme pack is assembled from the sessions rather than from a register somebody has to find, and a missed session is a task that was not completed rather than a gap discovered at month end. Dialysis is repeatable, session-billed work, which is exactly the shape that punishes a hospital for keeping it on paper.
Illustrative account, written by us
A woman of seventy, second eye, on a day-care list.
What she meets today
Her biometry was done three weeks ago and the printout is in a file. Her diabetes is managed by a physician in the same hospital whose notes are somewhere else. On the morning of the list her consent is signed against a sheet that names the eye, the lens power is read off a photocopy, and the safety of the operation rests on three pieces of paper agreeing with one another in a corridor.
What one record changes for her
The biometry result is attached to the order that asked for it, and the order carries the eye, so theatre reads laterality from the same object the surgeon booked rather than from a note beside it. Her consent is a completed form that locks the moment it is signed and cannot be quietly altered afterwards, and it sits on the same record as the physician’s note about her glycaemic control. Nothing about her operation depends on a photocopy travelling.
What the hospital gets back
A high-volume list is a scheduling problem before it is a surgical one. The cases, the theatre, the staff actually on shift and the consumables issued are on one record, so utilisation is read off the work instead of being reconstructed at the end of the month. The discharge summary and the claim are made of the same events, which is why one never waits on the other.
Illustrative account, written by us
A man of fifty-eight, chest pain, arriving at two in the morning.
What he meets today
The tracing is done in the casualty and the strip goes into a file. Troponin is sent and the result comes back to a screen in the laboratory. Somebody telephones a cardiologist. Registration is still taking his details, the insurance desk opens at nine, and the clock the hospital will later be judged on is being kept in three places by three people who will disagree about it.
What one record changes for him
Registration opens a visit, and the visit is what everything else attaches to. The tracing, the troponin order, the result and the decision that followed are events on one record, each with an author and a time. A critical result raises an owned alert with an escalation chain instead of sitting on an unwatched screen, and it is delivered on the channel the person on call is actually reachable on.
What the hospital gets back
The clock is computed from the events rather than kept by hand, so time to decision is a figure the hospital can defend to an accreditation assessor and act on internally. The authorisation his family will need at nine is built from the visit that already exists. If a step was missed, the record says which one, and that is the only version of an audit worth holding.
The pattern underneath
The record does not follow the person.
- A test is repeated because the first result never arrived, and the patient pays for it twice: once in money, and once in the week it took.One record per patient, with the result attached to the order that asked for it rather than sent to whoever asked last.AtlasForge
- An allergy is recorded in one place and missing from another, and the second place is where the drug is given.The record is held once and every tool reads it, so there is no second place for it to be missing from.Atlas
Nobody can say who read it.
- A patient who asks who has looked at their record is told the question cannot be answered, and in most hospitals that is true.Every access is written by the same transaction that made it, so the answer is a query rather than an investigation.
- Consent is a signature collected at admission, filed, and never consulted again by anything.Consent is a modelled object the access check reads every time, and a withdrawal takes effect at the next read rather than at the next audit.
The bill arrives without an explanation.
- A family is handed a total at discharge and finds that nobody in the building can say which line came from which day.Every charge is raised by the order that treated the patient, so a bill opens to the work behind it.VaultForge
- The patient waits at the counter while a claim is assembled from documents held in four departments.The authorisation and the claim are built from the visit the treatment is already recorded on.Vault
The patient is the last to be told anything.
- An appointment moves, a report is ready, a follow-up falls due, and the patient learns each of them by turning up.Messages go out on the channel the person agreed to, inside quiet hours, with the delivery recorded rather than assumed.RavenQuest
- A patient who wants a copy of their own record has to ask a department for it and wait.The patient application holds their record, their appointments, their reports and their bills, on the same data the hospital is reading.
What this page is not claiming
It is not claiming that any of the above happened. There is no hospital behind these three people, no measured improvement attached to any of them, and no figure anywhere on this page.
What the accounts are for is to name the defect precisely, from the side that carries it. Each one is the same architectural fact seen from a corridor: the record is held once, the access to it is decided by one check and written down, and the money is made of the same events as the care. The mechanisms are at governance and one record; the patient’s own half of the platform is at the patient app.