Critical Value Reporting Workflow in an LIS

Of every workflow a clinical lab owns, critical-value reporting is the one where a missed step is most likely to harm a patient. A potassium of 7.2, a glucose of 28, a positive blood culture, an INR of 9 — the result is in the LIS within seconds of the analyzer finishing, and the question becomes mechanical: who has it, when did they get it, and did they understand what it said. Inspectors look at this workflow more closely than almost any other, and for good reason. The literature traces the framework back to George Lundberg’s 1972 essay When to Panic over Abnormal Values in Medical Laboratory Observer (PubMed), which named the concept and gave labs the first working definition. Fifty-plus years later, the practice has hardened into a measurable, audited, time-bound process — and the LIS is what makes that auditable at scale.

This post walks through what a defensible critical-value workflow looks like in a modern LIS, what the regulators actually require, and where labs get tripped up.

What counts as a critical value

A critical value (sometimes still called a panic value) is a laboratory result that reflects a pathophysiologic state so far outside the expected range that the patient may be in immediate danger unless someone acts promptly. The defining feature is not just the magnitude of the deviation but the time-criticality of the response. A hemoglobin of 6.5 in a stable chronic anemic patient is not the same kind of event as a hemoglobin of 6.5 in a postoperative patient on the surgical floor — but the lab does not know which patient the result belongs to, so the result triggers a notification either way and the receiving clinician decides what to do with it.

CLIA at 42 CFR §493.1291(g) puts this in regulatory language: the laboratory must immediately alert the individual or entity requesting the test when any test result indicates an imminently life-threatening condition, or “panic or alert values.” That word “immediately” is the load-bearing one — every layer of the workflow below exists to make “immediately” operationally defined and verifiable.

The critical-value list — the lab’s first decision

Before the LIS can flag anything, the lab has to publish a list. The list is the medical director’s responsibility, reviewed at least annually, signed and dated, kept under document control. It typically covers:

• Chemistry — glucose, potassium, sodium, calcium (ionized and total), magnesium, phosphorus, ammonia, lactate, troponin, bicarbonate/CO₂, anion gap.
• Hematology — hemoglobin, hematocrit, platelet count, WBC, blast cells on smear, malaria parasites.
• Coagulation — PT/INR, aPTT, fibrinogen, D-dimer in specific contexts.
• Blood gas — pH, pCO₂, pO₂, base excess.
• Microbiology — any positive blood culture, any positive CSF Gram stain, any acid-fast positive smear, any organism designated reportable by the public health agency.
• Toxicology / therapeutic drug monitoring — acetaminophen, salicylate, digoxin, lithium, theophylline, anti-epileptics, vancomycin troughs above defined thresholds.
• Other — any newly positive pregnancy test on an unexpected presentation, any new diagnosis of an immediately reportable infectious disease, any result the medical director designates.

Each line carries a low threshold, a high threshold, an age range, and sometimes a specimen-type or department modifier — neonatal critical values are not the same as adult, and ICU thresholds for some analytes differ from outpatient. The LIS stores this list as data, not as code, so the medical director can revise the threshold without a release cycle.

Workflow inside the LIS — from analyzer to acknowledgment

A complete critical-value workflow in the LIS has nine stages, and any one of them done sloppily becomes the gap an auditor finds.

1. Detection. The analyzer result lands in the LIS. Rule logic compares it against the active critical-value list, and a match raises critical result and specimen flags. The laboratory’s validated rules determine whether that flag blocks auto-approval, requires manual review, or feeds a preliminary-report workflow. CAP COM.30000 addresses critical-result notification and COM.30100 addresses read-back documentation for results communicated by phone; neither establishes a universal software rule that every critical result must be manually reviewed before any report is released.
2. Repeat or confirm — when policy says so. Some labs require an analyzer repeat (a second aliquot run on the same instrument) for select analytes before notification, particularly on first-encounter patients with no prior trend. Others repeat only on questionable specimen integrity (hemolysis, clot, short draw). When the laboratory configures repeat confirmation as a release gate, the workflow should hold the original result until the repeat lands and meets the laboratory’s tolerance.
3. Specimen integrity review. Before the technologist initiates a notification call, they confirm the specimen is acceptable — no hemolysis driving the potassium, no clotted EDTA driving the platelet count, no IV-contaminated chemistry. If the specimen is rejected, the result is canceled and a recollect ordered, not notified as a critical value.
4. Notification queue. The result drops into a critical-value queue visible to the bench. The queue is sorted by time-in-queue so the oldest result rises to the top. Every result carries an internal SLA — typically 30 minutes for inpatient critical values from result-available to clinician-acknowledged, and 60 minutes for outpatient, but the actual numbers come from the lab’s policy, which is what The Joint Commission’s NPSG.02.03.01 requires the organization to define and measure.
5. Identifying who to call. This is harder than it sounds. The ordering provider on the requisition may be off shift, on call, or on vacation. The LIS resolves the call target from the order: ordering provider first, then covering provider, then the nursing unit, then the on-call hospitalist or rapid-response. For outreach work, the call target is the office plus the after-hours service. The provider directory inside the LIS — phone numbers, pager lines, secure-text routes, after-hours numbers — is the data layer the workflow depends on. A stale directory is the single most common reason a notification slips past the SLA.
6. Placing the call and the read-back. The technologist calls. They give the patient identifiers, the test, the value, and the units. For results communicated by phone, CAP COM.30100 calls for the recipient to read the result back and for that read-back to be recorded; electronically transmitted critical results require confirmation that the intended recipient received them, but not a verbal read-back. The notification record should capture who called, who answered, the result communicated, whether read-back was required and completed, and the timestamps.
7. Logging the notification. The LIS records the notification as a structured event linked to the result: caller, recipient name and role, recipient phone or pager, time placed, time acknowledged, read-back captured, free-text notes. The same event populates HL7 segments on the outbound result message. In the HL7 v2 ORU^R01, the critical flag rides in OBX-8 with code HH or LL; the notification act is documented in an attached NTE segment and, where the receiving system supports it, a ROL segment naming the notified clinician.
8. Escalation if the SLA is missed. If the lab-defined reporting time elapses without acknowledgment, the workflow should trigger the laboratory’s documented escalation path — for example, notifying a supervisor and moving to the next authorized recipient. Every attempt, not just the successful one, belongs in the audit history.
9. Release of the result. Release follows the laboratory’s validated policy and configured approval rules. A lab may hold an order with an unresolved critical error for review, while another workflow may issue a preliminary report so the critical value is communicated before the full requisition is approved. In either case, the lab must preserve the notification record and meet its defined reporting time.

The exact sequence is a laboratory policy decision, not a single release model imposed on every lab. Inspectors evaluate whether the laboratory follows its written process, reports critical results within its defined time, and retains the notification and read-back evidence that applies to each communication method.

Time-to-notification as a measurable KPI

Once the workflow is in place, the LIS can produce the metric that everyone — the medical director, the quality committee, the inspector — actually wants to see: time from result-available to clinician acknowledgment, distributed across the lab’s last 30, 90, and 365 days. Cuts that matter:

• Median and 95th-percentile time-to-call for inpatient and outpatient separately.
• Rate of SLA violations (over 30 minutes inpatient, over 60 minutes outpatient — or whatever the lab’s policy defines).
• Top reasons for SLA misses — stale provider directory, unreachable on-call, read-back disputed, specimen integrity recheck.
• Notifications by analyte — the most-frequent critical values, which informs whether a threshold is set too tight (false alarms) or too loose (real events).
• Notifications by shift — overnight performance versus day shift is a real signal about staffing.

42 CFR §493.1291(h) requires the lab to notify the ordering clinician when established turnaround times cannot be met. For critical-value reporting specifically, the equivalent practical control is monitoring the SLA-miss rate and acting on it — the report should land on the medical director’s desk monthly, not once a year before inspection.

Where labs get tripped up

The failures that show up in patient-safety case reviews and inspector findings cluster around a few patterns that the AHRQ Patient Safety Network has documented since the mid-2000s.

• Stale provider directories. The number called rang an empty office. The pager belonged to a clinician who left the practice. The on-call schedule had not been updated.
• No read-back captured. The technologist gave the value, the clinician said “got it,” and hung up. No read-back, no documentation, no audit trail. In a downstream review, there is no way to prove the right value was heard.
• Notified the wrong person. Notified a unit secretary instead of the responsible clinician, or notified a covering provider who then never escalated to the primary team.
• No escalation path. First attempt failed, second attempt was the same number, third attempt repeated. The SLA blew past 90 minutes with no supervisor visibility.
• No closed-loop with the EHR. The result was reported in the LIS but the EHR notification firehose buried it. The clinician genuinely never saw it because the alert was lost in 200 other notifications.
• Threshold drift over time. The critical-value list was set six years ago, the medical director changed twice, and nobody reviews it annually. New therapies (DOACs, newer chemotherapies, mass-spec drug panels) added analytes that never made it onto the list.

The fix for all of these is the same: structural. Make the directory a maintained data layer, make the read-back a required field in the LIS event record, make the escalation automatic, make the threshold review a calendared agenda item. None of these are heroic — they are governance steps that get done because the LIS workflow is built such that they cannot be skipped.

Why the LIS, not just the EHR

EHRs surface lab results to clinicians, but the regulated workflow lives in the clinical LIS. A few reasons it has to:

• The result enters the LIS first; the EHR receives it via HL7 after the LIS has processed it.
• The notification act — who called, when, what was read back — needs to be captured at the source, before the result is released downstream. If the LIS does not own this, the audit trail is reconstructed from notes scattered across the EHR.
• The critical-value list is a laboratory document under the medical director’s control. It belongs in the LIS as data, not in an EHR rule set that may not be visible to lab inspectors.
• The escalation path involves the lab supervisor, who lives in the LIS, not the EHR.
• The HL7 outbound message that informs the EHR carries the LIS’s metadata — OBX-8 abnormal flag, NTE notification note, optional ROL — and that is what closes the loop with whatever downstream chart, registry, or app the receiving system feeds.

One more loop runs alongside the clinician callback: the patient now sees the same result. Under the Cures Act information-blocking rule, results reach the patient without unreasonable delay, so the critical-value callback to the clinician and the patient’s own portal view happen in parallel — see lab patient portals and the Cures Act for how the two obligations coexist.

Where LIMS IQ fits

LIMS IQ evaluates results against configured critical-low and critical-high thresholds, can apply a critical specimen flag across review worklists, and can trigger notification and escalation workflows. Labs can require every result to be marked reviewed before completion, and unresolved critical requisition errors can block completion. Rules-based auto-approval releases an eligible requisition only when every configured business rule passes; critical handling can also feed preliminary reporting so the value is communicated before full approval. The laboratory validates which flags hold approval, who must review them, how notification is documented, and which delivery channels are used for its scope. Request a demo to walk through that configuration against your critical-value policy.

Sources

• 42 CFR §493.1291 — Standard: Test report — the CLIA requirement to alert the requesting individual immediately on imminently life-threatening, panic, or alert values, and to notify when TAT cannot be met.
• The Joint Commission — 2026 Laboratory NPSG (PDF) — NPSG.02.03.01 requires a written procedure defining critical results, who reports to whom, acceptable elapsed time, and an evaluation of timeliness.
• The Joint Commission — NPSG Lab FAQ — FAQ guidance on implementing NPSG.02.03.01.
• CAP — Accreditation Checklists — All Common Checklist items COM.30000 / COM.30100 (notification, read-back, documentation) and Laboratory General GEN.20316. Checklist text is in the e-LAB Solutions Suite for accredited labs.
• HL7 Terminology — ObservationInterpretation value set — the codes carried in OBX-8 for abnormal and critical results (HH, LL, AA, etc.).
• AHRQ PSNet — Communicating Critical Test Results, Safe Practice Recommendations — Hanna et al., the benchmark recommendations for closed-loop critical-result communication.
• AHRQ PSNet — Advancing Safety Through Closed-Loop Communication of Test Results — closed-loop framework for test-result communication.
• Lundberg, When to Panic over Abnormal Values, 1972 (PubMed) — the original framing of the critical-value concept.