Written and maintained by CASRAI Editorial Board
Last updated
A potassium of 6.8 comes back on a floor patient at 2 a.m. The lab has thirty seconds to decide who gets called, how fast, and what happens if that person doesn’t pick up — and the hospital needs a written policy that answers all three questions before the phone ever rings, not a judgment call improvised in the moment. That policy is what “critical value reporting” means operationally: not the lab flagging an abnormal result, but the defined, documented chain of communication that gets a result capable of causing serious harm from the analyzer to a clinician who can act on it, verified and on the record.
This page is written for risk managers, laboratory quality staff, and patient-safety officers who own or audit this policy — not as bedside clinical guidance for a specific result. One verification note up front: the Joint Commission’s own accreditation-manual wording for NPSG.02.03.01 could not be independently confirmed for this page (jointcommission.org and CAP’s laboratory-accreditation pages both blocked automated retrieval), so the goal is described at the level independently corroborated by secondary clinical-laboratory and patient-safety literature, not quoted verbatim from the standard itself. Verify exact checklist language against your current Joint Commission and CAP manuals before writing it into policy.
What makes a result “critical,” and why that’s a policy decision
A critical value (also called a critical result, alert value, or panic value) is a test result that falls far enough outside the normal range that, without prompt clinical intervention, it poses an immediate risk to the patient — a potassium high enough to cause a fatal arrhythmia, a hemoglobin low enough to require transfusion, a positive blood culture in a patient nobody suspected was bacteremic. Unlike a routine “abnormal” flag, a critical value isn’t a fixed universal number: each laboratory sets its own list, by test, in consultation with its medical staff, and reviews it periodically as clinical practice and instrumentation change. That’s deliberate — the threshold that matters for a neonatal ICU is not the threshold that matters for an oncology ward, and a policy that borrows someone else’s list without local clinical sign-off is not defensible in an audit or a survey.
The list typically spans chemistry (potassium, glucose, sodium, calcium, and similar analytes at both high and low extremes), hematology and coagulation (hemoglobin, platelet count, INR, activated partial thromboplastin time), and microbiology (positive blood cultures, cerebrospinal fluid Gram stains, and other results where any positive result is critical regardless of magnitude). Critical imaging and pathology findings — a new intracranial hemorrhage, a pneumothorax, a malignant finding on a specimen nobody was tracking as urgent — belong in the same governance structure even though they don’t come from an analyzer, and a mature policy names who owns that reporting chain too, not just the core lab.
The Joint Commission goal behind the policy: reporting on a timely basis
The Joint Commission’s National Patient Safety Goal on this subject — numbered NPSG.02.03.01 in the current hospital chapter — requires accredited organizations to report critical results of tests and diagnostic procedures on a timely basis. In practice that goal doesn’t hand a hospital a single national list or a single national time limit; it requires the organization to do the governance work itself: define what counts as a critical result for each relevant test, define an acceptable time frame between the result being available and the responsible licensed caregiver being notified, implement a documented process to meet that time frame, and monitor performance against it. A surveyor asking about this goal is checking that all four pieces exist and are followed — not comparing your list or your clock against a fixed external benchmark.
This is the same structural pattern behind the Joint Commission’s other communication-focused patient safety goals: define the standard locally, document the process, then prove compliance with real data. It’s why a critical value policy and a structured handoff communication protocol like SBAR usually live in the same governance chapter — a critical result reported without a structured format is exactly the kind of communication failure both goals exist to close.
The read-back requirement
Because critical values are almost always communicated verbally — a phone call from the lab to a nurse or physician, not a portal message someone might not see for hours — the policy has to specify how that verbal exchange is verified, not just that it happens. The standard pattern, sometimes called “record-read-back-verify,” is: the receiver writes the result down as it’s given, reads it back in full to the caller, and the caller confirms the read-back matches before the call ends. That single step is what turns “I told the nurse the potassium was 6.8” into a defensible, auditable claim rather than two people’s conflicting memories of a phone call. The same read-back discipline applies to verbal and telephone orders generally, which is why it’s usually written into the same policy family as patient-identification requirements — both exist to remove a specific, well-documented category of communication error from a moment where there’s no time to double-check informally.
Setting — and defending — the notification time frame
Because the Joint Commission requires organizations to set their own acceptable time frame rather than adopt one imposed externally, the number itself has to be defensible on clinical grounds, not just short. A workable policy typically ties the clock to the point the result becomes available in the system (not the point someone happens to notice it), applies the same clock consistently across shifts, and is short enough that a genuinely critical result reaches a decision-maker before it stops being actionable. Whatever number a given hospital lands on, the policy needs a stated, board- or medical-staff-approved rationale for it and a mechanism to measure real turnaround time against it — a time frame nobody actually tracks compliance against isn’t a control, it’s an aspiration written down.
An illustrative example (a composite for explanatory purposes, not a real hospital’s actual figures or a Joint Commission-mandated number): a policy might require chemistry and hematology critical values to reach a licensed caregiver within a defined window from result availability, with a separate, typically longer window for microbiology and pathology criticals where the clinical urgency profile differs. The point isn’t the specific minutes — it’s that the number is written down, clinically justified, applied consistently, and measured, which is what a surveyor or an internal audit is actually checking for.
Escalation when the first call doesn’t connect
A policy that only describes the successful call is incomplete. The harder — and more frequently audited — case is what happens when the ordering provider doesn’t answer: a defined escalation ladder (attending, then covering provider, then charge nurse or house supervisor, then a defined final backstop) with a maximum number of attempts or elapsed time before the lab moves to the next person on the list, and a documentation requirement for every attempt, not just the one that connects. This is the same operational logic behind a hospital’s rapid response team activation criteria and its early warning score escalation thresholds — a deteriorating-patient signal that stalls because nobody defined what happens after the first unanswered call is a governance gap, not a training gap, and it shows up in root cause analyses more often than the underlying clinical miss does.
What the documentation trail has to show
A defensible critical value report — whether reviewed for an internal audit, a Joint Commission tracer, or a root cause analysis after an adverse event — needs, at minimum: the date and time the result became available; the date and time it was reported; the name of the person who reported it and the name (not just “RN” or “on-call physician”) of the person who received it; confirmation that the value was read back and verified; and, where escalation occurred, a record of each attempt and why it moved to the next contact. Missing any one of these turns an otherwise-compliant process into an unverifiable one the moment it’s actually tested — which is precisely the failure mode Joint Commission tracer methodology is designed to surface, by following one patient’s actual record rather than reviewing the policy document in the abstract.
Where CAP and CLIA fit alongside the Joint Commission goal
Three distinct regulatory layers touch this same policy, and it’s worth keeping them separate. The Joint Commission’s NPSG sets the accreditation-level expectation described above and applies at the hospital level. CAP’s Laboratory Accreditation Program checklist operates one level down, at the laboratory itself, and is the mechanism that actually drives labs to maintain a written, periodically reviewed critical value list with defined notification and escalation procedures — CAP-accredited labs are assessed against this directly during inspection, in addition to whatever their hospital’s Joint Commission survey covers. CLIA, the underlying federal statute governing laboratory testing generally, doesn’t specify a critical value list or a notification time frame itself; it sets the baseline quality requirements that CAP accreditation is deemed to satisfy, leaving the specific critical-value governance to the accrediting body and the laboratory’s own medical staff. A lab that is CAP-accredited is, in effect, already meeting CLIA’s baseline on this point — but CAP’s own checklist requirements are the more specific and more frequently surveyed standard in practice.
How this fits the rest of a hospital’s safety program
Critical value reporting rarely functions well in isolation from the rest of a hospital’s communication infrastructure. It depends on reliable patient identification so the result is never attached to the wrong chart in the first place; it feeds the same escalation pathways used for rapid response activation; and, when a critical value is one input among several that led to an adverse event, it’s the kind of contributing factor that shows up in adverse drug event surveillance and quality reporting alongside measures tracked as nurse-sensitive indicators. For the broader framework this policy sits inside, see CASRAI’s patient safety pillar.
Frequently asked questions
What’s the difference between a critical value and an abnormal result? An abnormal result falls outside the normal reference range but doesn’t necessarily require immediate action. A critical value is far enough outside that range to pose an immediate risk to the patient if not acted on promptly — it triggers the notification-and-read-back process described above, an abnormal flag alone does not.
Who is responsible for maintaining the critical value list? The laboratory’s medical director, in consultation with medical staff across the specialties that order the relevant tests, typically owns the list and its periodic review. Ownership of the notification and escalation policy itself is usually shared between the laboratory and hospital-wide patient-safety or quality leadership, since the policy governs clinical staff behavior outside the lab as much as it governs the lab’s own process.
Is there one national time limit hospitals must meet? No. The Joint Commission requires each organization to define its own acceptable time frame and to measure compliance against it — there is no single externally mandated number that applies to every hospital or every test category.
What happens if the ordering provider never answers? A compliant policy defines an escalation ladder in advance — who gets called next, after how many attempts or how much elapsed time — so the lab is never left improvising who to contact for a result that can’t wait.
