Offering

For the laboratory, inside a hospital and outside it.

A laboratory lives on two things: the order arriving intact, and the result getting back to the person who asked for it.

Two directions, one object.

Almost nothing that goes wrong in a laboratory goes wrong at the analyser.

It goes wrong where a request is written down a second time, where a sample is labelled, and where a validated result waits for somebody to notice it. Add an outside client and each of those three happens across an organisational boundary as well as a departmental one.

Inside a hospital, Pensieve carries the order from the point a clinician places it to the point the result is signed, on one record. The analysers talk to the platform over the bridge in the protocol they already speak, so a result lands against the right patient and the right order without being keyed again.

Outside a hospital, an independent laboratory serves clinics and hospitals it does not run. The same bridge and the same standards work in the other direction: an order arrives from a system the laboratory does not control, and the report returns to that system rather than to a fax machine. Nothing about the bench changes, because the order object is the same object.

The shape

Work from inside and work from outside, as one object

A request from a ward in this hospital and a request from a clinic that outsources its bench work become the same order. The analysers answer the order rather than the requester, which is why a result cannot arrive unattached, and the report returns on the route the request came in on.

Where the work is lost

The work arrives as a piece of paper.

An outside requisition reaches the reception desk as a form, a phone call or a photograph. Somebody types it in, and the laboratory now works a transcription rather than the request that was actually made.The request arrives as an order object with the patient, the tests, the priority and the clinical indication attached, from a system the laboratory need never own.ForgeWestron
The patient on the requisition and the patient on the tube are matched by a name and an age, which is the point at which most laboratory error is introduced.The sample is a state of the order rather than a separate object, so a container without an order and an order without a container are both visible conditions.ForgeAtlas

The result has to get back to a system you do not control.

A validated report is emailed, faxed or collected. Whether it reached the clinician who ordered it is a question the laboratory answers by telephone.The result returns over the same connection the order arrived on, in the format that system reads, with a forensic trail of the exchange on both legs.Westron
A critical value found at midnight is telephoned to a number that rings out, and the call is recorded in a diary if at all.Sentinel raises an owned alert with an escalation chain, Raven delivers it on the channel the recipient is reachable on, and the acknowledgement is recorded.SentinelRaven

Referred work is invisible until an invoice arrives.

A test the laboratory does not perform is sent out on a form, tracked in a register, and reconciled when the reference laboratory bills for it a month later.Sending a test out is a route on the same order, so the state of an outsourced test is the state of the order, and the cost of it lands against the same event.ForgeVault
Nobody can say what the laboratory spends on outsourcing, per test, per client or per month, without assembling it by hand.Falcon reads outsourcing spend, turnaround by stage and rejection rate off the work itself rather than off a register somebody maintains.Falcon

The client relationship is a spreadsheet.

Each referring clinic is on a different rate card, held in a file, applied by whoever raises the monthly bill and disputed at the point of payment.Each client is a payer with its own pricing, and the charge is raised by the order at the price of the day it was placed, so a later change to the card never rewrites an old test.Vault
Quality control, calibration and competency records live in bench registers, and the accreditation file is rebuilt in the weeks before an assessment.Glyph carries them as structured forms that lock on completion, and Vigil reads them as standing evidence rather than as a project.GlyphVigil

The laboratory as a network.

A hospital that outsources its bench

A hospital without a haematology bench, or without a histopathologist, sends the work out. In Pensieve that is a route on the order rather than a second process: the test is ordered from the same catalogue, its state is the state of the order, the result comes back onto the record it was ordered from, and the cost of it lands on the same visit.

How an order works

A laboratory that takes the work in

From the other side, that hospital is a client. Its requests arrive over a configured connection, its reports leave the same way, and its rate card, its credit book and its turnaround are readable per client rather than in aggregate. A collection centre that only draws samples is the same arrangement with a shorter list of tests.

Westron

Imaging is the same shape of work

A scan is an order, a study and a report, with a scarcer reporter at the end of it. The modality speaks DICOM to the bridge, the study is tied back to the patient and the order that produced it, and the viewer opens it from wherever in the platform the reader happens to be. Where reporting is done elsewhere, the study leaves and the report returns on the same connection any other outside system uses.

Radiology and imaging

Accreditation is a separate file, and it is kept the same way

Laboratories are accredited on their own terms, against their own standard, by their own board. The evidence that standard asks for is the work: quality control runs, calibration, competency, internal audit, equipment maintenance. It is recorded as it happens and read as evidence rather than reconstructed for an assessment.

Vigil

Standing up a client

What connecting an outside institution actually involves

The connection
The client’s system is configured as a connection in Westron: the protocol it speaks, the credentials, and the translation between its format and the laboratory’s. It is mirrored on the bridge inside the estate, which is the thing that physically carries the traffic.
The catalogue
The tests that client may order are drawn from the laboratory’s own approved catalogue, so staff on both sides pick rather than type, and an order names a test the laboratory actually performs.
The order
A request becomes an order object carrying the patient, the tests, the priority and the indication. What was ordered is locked at that moment, so a later change to the catalogue or the price list never rewrites it.
The bench
The analyser receives the work and its output is bridged back and matched to the order that produced it. A test sent on to a reference laboratory is a route on the same order rather than a new one.
The report, and the charge
A validated result returns to the system the request arrived from, and a critical value raises an owned alert instead of waiting to be read. The charge was raised when the order was placed, at that day’s price, against the rate card the client is on.

Every one of those exchanges is observable. Westron shows connection health and message flow per client, so a feed that has gone quiet is a visible state rather than a discovery made when somebody asks where their report is.

The tools a laboratory lives in

Tools inside Pensieve and what each one does in a laboratory network
Tool	What it does here
Forge	The order itself: the approved test catalogue, the sample, the state of the work, and the route out to a reference laboratory when the test is not performed here.
Westron	Every connection, in both directions: analysers on the bench, the systems outside clients run, credentials, translation, traffic health and a forensic trail of each exchange.
Atlas	The record the validated result lands on, beside the note that ordered it, under one access check.
Glyph	The reporting form, the histopathology report, internal quality control and calibration records, each locking on completion with a version history.
Sentinel	Critical value rules the laboratory defines, raised as owned alerts with an escalation chain and a resolution state.
Raven	Delivery of those alerts and of client and patient notifications, on the channel each recipient consented to, with a delivery log.
Quest	Collection rounds, recollections after a rejection and timed sample handling, as due tasks against whoever is actually on shift.
Vault	The charge raised by the order at that day’s price, client rate cards, outsourced test cost, and the credit book for referring institutions.
Falcon	Turnaround by stage, rejection rate by client and by tube type, workload by bench, and outsourcing spend.
Vigil	The accreditation evidence file: competency records, internal audits, equipment maintenance and quality control, kept live rather than assembled.

Published research

What the literature already measured

Three findings about laboratory and diagnostic work, each with its study and a link. None of it is a Pensieve result.

Every figure this site cites, with its source