Department
Dialysis Unit
A dialysis unit is the most repetitive part of a hospital and the most exposed to a scheduling error. The same patients return three times a week for years, on machines that produce data nobody keeps, against a scheme that pays per session.
The published record
The programme this unit sits inside.
India's national dialysis programme reports 1,889 centres across 759 districts, 262,444 patients and more than 14.4 million haemodialysis sessions delivered. Source 9 Haemodialysis is the single most frequently claimed procedure under the national assurance scheme, which makes this the most repeatable, most scheme-funded workload in an Indian hospital.
And the settlement behind it.
A 2025 study of the national and state schemes in one Indian state found settlement running from three months to a year against a thirty day guideline. Source 11 A unit billing per session carries that delay multiplied by every chair, every day.
Impact and action
A schedule on a whiteboard.
- Chairs, shifts and patients are allocated on a board wiped clean every evening, so a missed session is discovered when a patient arrives on the wrong day.Sessions run as recurring schedules against the chair as a resource in the hospital twin, and a missed session is a recorded state rather than a gap.Quest
- A patient who misses two sessions is noticed by whoever happens to know them.A missed session fires a rule the hospital wrote as an owned alert, and a reminder goes out on an audited channel.SentinelRaven
Machine data that stays on the machine.
- The dialysis machine records the session and the record keeps a handwritten summary of it.The orophin bridge carries machine data into the record over one outbound connection, with no inbound hole in the firewall, and Westron keeps a forensic trail of every exchange.Westron
- Per-session observations are kept on a chart that lives in the unit.Per-session forms are built by the unit in Glyph, filled at the chair, and locked when finished.Glyph
Sessions that were never charged.
- Dialysers, tubing and heparin are counted at month end, and the difference between what was used and what was billed is absorbed.Consumables post from the session that used them, so a chair-hour and its materials are one billable object.ForgeVault
- Scheme claims for sessions are batched by hand, and one incomplete pack holds up the batch.Each session produces its own claim pack from the record, in a standard exchange format, with the deduction and appeal loop modelled on the same claim.Vault
One session
Chair to claim.
Scheduled.
The session exists before the patient arrives, against a chair and a shift that exist in the hospital twin.
Prepared.
The order set carries the dialyser, the tubing and the drugs, so what is used is what was ordered.
Run.
Machine data arrives on the record, and the unit’s own per-session form is filled at the chair.
Closed.
The session locks. Consumables have already posted, because using them is what posted them.
Claimed.
The pack is assembled from the record and submitted in a standard format, and settlement is tracked as a live view.
The tools this unit runs on.
Each row is what the tool does at the chair, with the example the unit in-charge would recognise.
| Tool | What it does here | Example |
|---|---|---|
| Quest | Runs recurring session schedules and the unit’s due list. | A patient’s Monday, Wednesday and Friday chair exists as a standing schedule. |
| Glyph | Runs the per-session form the unit designed, locked when finished. | Pre and post weights, captured at the chair and unalterable afterwards. |
| Westron | Manages the machine connections and keeps a trail of every exchange. | Session data from the machine arrives against the right session. |
| Forge | Carries the session order set and the consumables it uses. | A dialyser issued to a session posts and draws down together. |
| Vault | Prices the session and packages the scheme claim. | One session produces the claim pack in a standard exchange format. |
| Sentinel | Fires the unit’s own rules as owned alerts with escalation. | Two missed sessions reach the nephrologist rather than nobody. |
Interdepartmental
The unit’s standing relationships.
- Nephrology.The prescription that governs every session is a clinical record, and the sessions run against it.
- The laboratory.Monthly bloods drive the prescription, and the result lands on the record the session runs from.
- The insurance and scheme desk.Session billing is the most repetitive claim workload in the hospital.
- Stores.Pensieve integrates with the inventory system a hospital already runs. Where there is none, the app is built in [Durin](/tools/durin), either by hospital staff with no code and no vendor ticket, or by a Pensieve forward-deployed engineer who builds it for the hospital and hands it over. Anything built that way sits on the same permissions and the same audit trail as the rest of the platform.