Cutting lab turnaround time in a small clinic

Ask a clinic how long a routine blood test takes and you will get the lab's processing time — four hours, say. Measure it end to end, from the doctor writing the order to the doctor reading the result, and the number is usually a day and a half.

The gap between those two numbers is entirely handoffs, and handoffs are the cheapest thing in a clinic to fix.

Measure the right interval

Turnaround time should be measured order to result-reviewed, not sample to report. Broken into segments:

1. Order to collection — the doctor writes it, the patient walks to phlebotomy
2. Collection to lab receipt — relevant if samples go to an external lab
3. Processing
4. Result to record — the report gets attached to the patient's file
5. Record to review — the doctor actually reads it

Time each segment for a week. In most small clinics, segments 1, 4 and 5 dominate, and the lab — the part everyone blames — is not the bottleneck.

Segment 1: the walk to phlebotomy

A paper requisition handed to a patient who then queues again is a common design, and it leaks time and patients. Some fraction simply do not go.

The fix is that the order should exist in the system the moment the doctor writes it, so the collection point already knows the patient is coming and what is required. The patient carries themselves, not the paperwork.

Two details matter more than they look:

• Fasting and prep instructions must reach the patient at ordering time, not at the collection desk. A patient turned away for having eaten is a full day lost.
• Sample requirements — tube type, volume — should be on the collection screen, so a resample is not discovered during processing.

Segments 4 and 5: where the day goes

This is the real bottleneck in most clinics, and it is almost always the same thing: results arrive as a PDF in an email or a WhatsApp message, and someone has to notice, download, rename and attach them to the right patient file. Then the doctor has to be told they exist.

That process has three failure modes, all common: the result is attached to the wrong patient, the result is never attached, and the result is attached but nobody tells the doctor.

What fixes it:

• Results attach to the order, not to the patient. The order already knows which patient, which doctor and which test. Uploading against the order removes the misfiling failure entirely.
• An unreviewed-results queue per doctor. A result that has landed but not been read should be visible as a work item, not as a notification that scrolls away.
• An age alert on that queue. Anything unreviewed after 24 hours needs to be conspicuous. This is a patient safety control, not an efficiency one — the abnormal result nobody read is the worst outcome in this whole workflow.

Critical values need their own path

A critically abnormal result should not sit in the same queue as a routine one. Define a short list of critical values with your lab, and agree a protocol: who is called, within what time, and what is recorded about the call.

For a small clinic this can be a one-page document. It should not be an assumption.

Where ABDM fits

Under ABDM's milestone structure, a facility acting as a Health Information Provider can link records it generates — including lab reports — to the patient's ABHA. The patient then carries the result forward to any other facility without a physical report.

For a clinic with an in-house lab, this is one of the more immediately tangible benefits of ABDM: a report that does not need to be printed, photographed or re-explained at the next hospital. It requires your software to hold M2 certification in production, not just M1.

A realistic target

For an in-house lab running routine biochemistry and haematology, order to result-reviewed inside four hours is achievable for same-day patients. For an external lab, next-morning is realistic.

The clinics that hit those numbers are rarely the ones with the fastest analysers. They are the ones where nobody has to remember to attach a PDF.