Skip to main content

User guide overview

One page per shipped area of LabFlow. Each names the addresses it covers, so nothing here describes a screen that does not exist. Areas that are planned but unbuilt are on the roadmap.

The clinical spine

A specimen can be ordered, collected, accessioned, labelled, benched, entered, reviewed, released and amended. These pages follow that path.

PageCovers
Patients/patients, the record, editing, MRN issuance, merging duplicates
Test catalogue/tests and adding, viewing and editing a test
Panels and reference ranges/tests/panels, /reference-ranges, /results/personalized-ranges
Orders/orders and /tests/orders, priority, order status
Specimens and chain of custody/samples, the specimen record, /samples/register, /samples/collections
Accessioning and the bench/samples/scan and receiving a delivery
Labels and barcodes/labels and /tools/barcode-generator
Result entry/results/entry, /results, the result record
Result review and release/results/review, /results/validation-rules, escalations, amendments
Dashboard/dashboard

Running the laboratory

PageCovers
Users and access/users, roles, release scope, withdrawing and restoring access
Your profile and identity verification/profile, /profile/verification
Settings/settings and its sections
Forms/forms/builder
Utility tools/tools/calculators, /tools/document-scanner

Two rules that apply everywhere

One writer per value. Anything cached in this system is written by exactly one path, and no client role can write it directly. A specimen's status is a fold of its custody trail; a result's status changes only through one transition function. Two paths writing one field is how a laboratory system starts disagreeing with itself.

Nothing is deleted. A withdrawn membership, a rejected specimen, a retired test, a superseded result and a merged patient record all still exist. A record that vanishes is a laboratory that cannot explain what happened.