A serum potassium comes back at 6.8. On the worksheet it is just three characters. In the patient, it is a number that can stop a heart. The difference between those two readings is entirely down to whether your lab's system knows that 6.8 is not merely 'high' but critical — and whether it insists someone pick up the phone to the referring doctor now, not whenever the report is typed up this evening. That gap, between a value produced and a value understood, is where small labs carry the most risk and think about it the least.
We build a LIMS for single-centre and small labs, so this is close to home. This is an honest look at reference ranges and critical flags — the quiet safety net a report is supposed to carry — and why leaving it to memory and manual highlighting is the wrong bet.
A number is not a result
A measurement becomes a result only when it is placed against the range it should be read in. Print 13.5 with no context and you have told the doctor nothing; print it beside the reference interval, with a clear high or low marker where it falls outside, and you have communicated. This is the baseline job of a report, and it is astonishing how often it is done by hand — a technician mentally comparing a value to a range they half-remember, then bolding a cell if they notice. Memory is not a safety system. The range belongs to the test, and the software should attach it every time, without anyone choosing to.
Reference ranges are not one-size
The trap is thinking a range is a single pair of numbers. It rarely is. Haemoglobin norms differ for men, women and children. Many analytes shift with age. Some ranges depend on the method or analyser you run, so a value that is normal on one platform reads abnormal against the wrong reference. A creatinine or a TSH interpreted against a generic adult range can quietly mislead for a child or an elderly patient. A lab that stores one flat range per test will, sooner or later, flag something that is fine or — far worse — fail to flag something that is not. Ranges have to be age-aware, sex-aware and method-aware, and applied automatically to the right patient, because no busy technician can hold all of that in their head at four in the afternoon.
Critical values and the call-back you cannot skip
Some results are not just abnormal; they are emergencies, and the accreditation frameworks labs work under — NABL and ISO 15189 — expect you to have defined your critical values and to have a protocol for notifying the treating doctor immediately, with a record that you did. A critical potassium, glucose, sodium, or a platelet count in freefall is not something to leave sitting in a report queue. The system should catch it the moment it is entered, mark it unmistakably, and prompt a documented call-back — who was informed, when, by whom. That last part matters as much as the call itself: if it is not recorded, from the lab's point of view it did not happen.
What a report and a lab must actually carry
- The correct reference interval printed against every analyte, matched to the patient's age and sex.
- Method- or analyser-specific ranges where the test demands them, so the comparison is valid.
- Automatic high/low markers, so an out-of-range value is obvious, not hunted for.
- A defined critical-value list that triggers an immediate, unmissable alert at result entry.
- A recorded call-back: who was notified, when, and by whom — the documented proof the protocol was followed.
- Delta checks that notice when a patient's result has swung implausibly from last time, catching mix-ups and errors.
Where manual flagging fails
Manual systems fail in the most predictable way: on the busiest day, with the most samples, when a safety net matters most. Highlighting by hand works when there are twenty reports. At two hundred, on a short-staffed afternoon, the one critical result that needed a phone call is the one that blends into the run. This is not about doubting your technicians' care — it is about not making patient safety depend on flawless human vigilance during the exact conditions that erode it. Encode the ranges and the critical rules once, and the net holds regardless of how heavy the day is.
A manual safety net fails on the busiest day — which is precisely the day it matters most.
Delta checks: the error the range won't catch
Reference ranges catch values outside normal. They do not catch a result that is technically in range but wildly different from the same patient's last visit — often the fingerprint of a sample mix-up or a labelling error. A delta check does: it compares against history and raises a hand when a value has moved more than it plausibly should. For a small lab without a second pair of eyes on every run, that automated second look is worth a great deal, and it costs nothing once the system simply does it.
How BizRevolt builds the net in
BizRevolt attaches the right reference interval to every analyte by age and sex, applies method-specific ranges where they matter, and marks out-of-range values automatically so nothing depends on remembering. Critical values are defined once and then caught at the moment of entry, with an unmissable alert and a recorded call-back so the notification is both made and documented. Delta checks flag the implausible swing that a plain range would miss. It is the safety net a report should carry, built in rather than bolted on by hand. Pricing is honest and small-lab-sized: ₹999 a month for a single Lab and ₹2,499 for Growth — the safety features are not a premium tier, because they should never have been optional.
We are building this alongside working labs, in the open, and the feedback we value most is a lab owner telling us where our defaults are wrong for their patients. If that is you, we want the conversation. Message us, or call and talk to a person on +91 91 0657 4865 — bring the result that still gives you a cold feeling, and we will show you how the net catches it.