For diagnostics

Barcoded from order to result, reports that release complete.

LabBridge and CheckUp run the order-to-report line; LabelPress puts a GS1 barcode on every sample; results land in the chart as observations with abnormal flags escalating to a named person.

An illustration of a clinician and a patient at a shared digital care record
Scan verification against what was actually printedA report does not release with pending resultsCritical results escalate until acknowledged

A day for diagnostics

  1. 01the patient is registeredPatient Registry
  2. 02the week’s bookable slots are materialised from the availability template, and leave removes timeSlotGrid
  3. 03the label is printed, then scan verification checks what was printedLabelPress
  4. 04the order moves from ordered to collected to resultedLabBridge
  5. 05each station is resulted with a name on it, then the report is releasedCheckUp
  6. 06the bill is made and the payment is takenBillDesk
  7. 07the patient’s message comes in on WhatsApp, and the message back goes out on itCarePings
Schematic frames, not screenshots — each one names the live app that does the step.

The stack diagnostics run

● live apps install today · ◦ in-design apps arrive on the same record, no migration