How lab orders reach the lab instantly, and results come back safely

Lost request slips, phone calls to ask whether a sample arrived, critical values that nobody acknowledged. Most lab delays are not in the analyser; they are in the hand-offs. Here is how a connected order flow removes them.

Ask a lab manager where time is lost and the answer is rarely the analyser. Time is lost between people: the paper request that waits at the nursing station, the tube labelled by hand, the result typed twice, the critical potassium phoned to a ward where nobody wrote down who took the call. A laboratory information system earns its place by removing those hand-offs, one by one. This article follows a single order through Nabd, step by step.

1. The doctor orders, the lab sees it at once

The doctor orders tests from the patient’s encounter, alone or as an order set. The charge is captured at the same moment from the payer’s price list, so the lab never has to ask finance whether a test was billed. The order appears on the collection worklist immediately: every change in the lab is pushed to the screens of that facility in real time, so worklists refresh by themselves without anyone pressing reload.

2. One tube per specimen type, labelled at the bedside

At collection, the phlebotomist or ward nurse selects the patient’s pending orders and Nabd groups them into tubes: one tube per visit, specimen type and container. A CBC and an HbA1c share one EDTA tube; liver and kidney function share one serum tube. Each tube receives an accession number, and a barcode label prints immediately. Fewer tubes means fewer needle sticks for the patient and fewer labelling errors for the lab.

3. Scan to receive, enter results on one grid

At lab reception, scanning the tube marks it as received with the time and the person. Technologists then enter results on one grid that shows every parameter of every test on that tube. The grid is keyboard-first, flags each value against the reference range and saves results as preliminary.

4. A specialist validates, the doctor is told

Technologists cannot release results; only the lab specialist or supervisor role validates. When an order is complete, the ordering doctor receives a “results ready” notification. Released results can still be corrected, but only with a written reason: the old and new values are kept, the correction is recorded in the audit trail, and the doctor is notified again.

5. Critical results: a closed loop, not a phone call

Critical values are where a lab system protects patients directly. In Nabd, numeric values outside the configured critical limits are detected automatically; qualitative ones, such as a positive blood culture, can be marked critical by the lab. Then the loop runs:

  1. On validation, and immediately at entry for STAT orders, the ordering doctor receives a critical notification that requires acknowledgement. For inpatient, emergency and day-case patients the nurses of the facility are notified too.
  2. The receiver acknowledges with read-back. When the result is given by telephone, lab staff record the read-back, the method and the name of the person who received it.
  3. If nobody acknowledges within the facility’s time limit (30 minutes by default), the result is escalated to the lab supervisors and the hospital manager.
  4. Every critical result appears in a log: time reported, patient and location, value, who reported it, who was notified, who acknowledged and when, minutes to acknowledge and escalation.

The log is printable, which is what quality teams need during accreditation surveys. Nabd is built to support GAHAR accreditation workflows; accreditation itself is granted to the hospital, not to the software.

6. When a sample has to be rejected

A haemolysed, clotted or mislabelled sample is rejected with a reason chosen from a list. The orders go back to the collection worklist so they are not forgotten, any unreleased results are cancelled, and the ordering doctor, plus the nurses for admitted and emergency patients, receive a notification. The patient is recollected instead of waiting for a result that will never come.

7. Analysers, and what is still on the roadmap

Nabd exposes an analyser results interface: an on-site agent sends results with the tube’s accession number over HTTPS with a restricted key, and they arrive as preliminary results for normal validation. Nothing is released automatically.

Honest status: the results interface in Nabd exists today. The on-site interface agent that talks to analysers in ASTM or HL7 and forwards their results is in development. Until it is in place, results are entered on the result grid or come from the analyser’s own middleware.

8. Results the doctor can read in context

A result is only useful when the doctor sees it next to the patient’s history. In the chart, lab results appear on the encounter with their flags, and doctors can open a cumulative view of a patient’s results over time or a trend of one parameter, which is how a slowly rising creatinine is spotted before it becomes critical. Routine results that are not validated yet stay inside the lab, so clinicians never act on a preliminary number by mistake.

The lab report prints from the same validated data, with reference ranges and flags, and test preparation instructions are kept in Arabic and English, so reception can tell a patient to fast before a glucose test in the language they read.

9. Measuring turnaround time

Because every step has a time and a person, the lab can measure itself: turnaround time and workload statistics over any period, and minutes to acknowledge critical results. Those are the numbers a quality committee asks for, and they come from the daily work rather than from a separate spreadsheet.

What changes for each person

The order flow by role
RoleBeforeWith a connected order flow
DoctorWrites a slip, calls to ask for resultsOrders in the chart, notified when results are ready or critical
Nurse / phlebotomistLabels tubes by handPrints barcode labels at collection, one tube per specimen type
Lab receptionMatches slips to tubesScans the tube to receive it
TechnologistTypes results, checks ranges by eyeOne grid with automatic flags and delta checks
SpecialistSigns paper reportsValidates on screen; corrections need a reason
QualityCollects critical-result notebooksPrints the critical results log

The lab module is described in more detail on our laboratory information system page, and the result screens are on the features page. Results also reach patients: verified lab results can be shown in the patient app after a configurable delay, and an order with an unacknowledged critical value is held back.

If you want to see the flow from order to critical-result log on fictional data, request a demo. Lab work is one part of a hospital information system where the same order also prices the invoice and posts to the accounts.

See Nabd on sample data

A live demo focused on the departments that matter to your hospital.