14 days free · no card · your current lab software keeps runningStart a lab trial →
Recognised by
Trusted & regulated
Scroll sideways — the rail runs the way the sample does. Under every card: what the software wrote down without anyone asking.
Patient gets a permanent ID; the bill, the tests and the referring doctor are captured in one screen.
A barcode prints for every tube at registration — or a handwritten accession number where there is no printer.
Draw recorded against the barcode. From here, every scan says who held the tube and when.
The lab logs the tube in. A haemolysed or short sample is rejected HERE — with a reason — not discovered after a wrong result.
Each department sees its pending tubes. Send-outs to a reference lab are tracked until the result returns.
Keyboard-first entry with the normal range for this patient's age and sex, the last value beside today's, and automatic H/L flags.
A different login approves. Danger-level results start alerting and keep alerting until someone confirms the callback.
Your letterhead, the signing doctor's registration number, a QR that opens the genuine copy. A correction later is a new version — never a quiet edit.
The PDF itself lands in the patient's WhatsApp, with an OTP-guarded online copy. The doctor sees it the same minute the patient does.
The day's cash reconciles at shift close; specimen disposal is recorded at the end of the chain.
Haemolysed, clotted, short volume, wrong tube, unlabelled — the technician picks the reason, the front desk sees it instantly, and the patient is called for a re-draw before the referring doctor ever asks. The alternative is what most labs live with: a result that quietly never arrives, and a doctor who stops referring.
Every rejection is dated, named and countable — which is also the first quality indicator an NABL assessor asks to see.
Where does the analyser fit? Between stages 05 and 06: machines can send results straight into the worklist over HL7 — currently running as a pilot, priced as an add-on, and described honestly on the interfacing page. Nothing on this page depends on it.