11.1 Critical Value Notification and Documentation

11.1 Critical Value Notification and Documentation

Quick Answer: A critical (panic) value is a result so far outside expected ranges that it may immediately threaten life or require urgent clinical action. The laboratory must notify an authorized provider promptly, obtain read-back, and document who/when/what. The MLA recognizes flags, follows the call tree, escalates STAT paths, and never leaves a critical uncommunicated—while verifying the recipient under HIPAA before speaking results.

Critical-value communication sits in Domain III: Support for Clinical Testing (about 15–20% of the ASCP MLA exam under the content guideline for testing dates beginning June 1, 2026). You will not invent panic lists on the exam; you will show you understand why speed + accuracy + documentation matter and where the MLA stops (notification support vs clinical interpretation).

---

What Critical / Panic Values Are

Laboratories maintain a written critical-value list (sometimes called panic or alert values) approved by laboratory medical leadership. Examples vary by site and analyte, but the concept is fixed: the result is time-sensitive for patient safety, not merely “abnormal.”

Typical categories that often appear on critical lists (examples only—your lab list is law):

• Extremely low or high potassium, glucose, hemoglobin, platelets, INR
• Positive blood culture or certain Gram stain findings on sterile specimens (site-specific)
• Critical troponin or other cardiac markers when defined
• Certain blood bank incompatibilities or transfusion-related alerts under separate protocols

MLA scope boundary: You do not decide “this feels critical” based on gut alone if the LIS did not flag it and policy does not define it—and you also do not ignore a clear critical flag because the patient “looked fine” at draw. Follow the list and the SOP.

---

MLA Role: Recognize Flags and Follow the Call Tree

In many laboratories, the MLS or pathologist verifies and releases the critical result; the MLA may:

• Notice LIS/instrument critical alerts, printer banners, or verbal handoffs (“K is critical—call path”)
• Pull contact information from the order, census, or call list
• Place the call, transfer to the MLS, or complete notification steps exactly as trained
• Stay on the line until read-back is complete when assigned to notify
• Document in LIS or critical-call log
• Escalate when no one answers

Call tree principles

1. Start with the authorized recipient named in policy (ordering provider, covering service, ED attending, unit RN who can escalate—site-specific).
2. Do not stop at “left a voicemail” if policy requires live confirmation—criticals need a closed loop.
3. Move down the escalation list (covering MD → house supervisor → medical director pathway) when the primary contact is unreachable within the time frame.
4. Never assume “the nurse already knows” without completing the required notification and documentation.
5. One patient, one result chain—do not batch-discuss multiple patients’ criticals in a hallway in a way that mixes identity.

---

Read-Back Requirement

Read-back is a patient-safety control used for verbal critical (and often STAT) results. After you state the patient identifiers and the critical result (with units and specimen/date-time as required), the recipient repeats the information back. You confirm accuracy.

Typical verbal sequence (adapt to SOP)

1. Identify yourself, laboratory name, and reason for call (critical result).
2. Verify you have the correct authorized person.
3. State two patient identifiers (e.g., full name + DOB or MRN).
4. State the test name, critical result, units, and collection/result time as required.
5. Request read-back.
6. Correct any mismatch; do not accept a mumbled “okay.”
7. Document the read-back completed.

Why exams care: Wrong-patient critical calls and misheard numbers (e.g., potassium 2.1 vs 3.1) are classic harm scenarios. Read-back catches them before the chart is acted on incorrectly.

---

Documentation: Who, When, What

If it is not documented, the laboratory cannot prove the critical was communicated. Documentation usually includes:

Document in the LIS critical-call module or designated log immediately after the call—not from memory at shift change. If the MLS released the result and you only assisted, document your actions accurately; do not claim you interpreted the result.

---

STAT Result Escalation vs Critical Values

STAT is an order priority (turnaround expectation). Critical is a result severity flag. They often overlap but are not identical:

STAT escalation for the MLA includes: flagging the specimen visually and in LIS, notifying processing/bench of arrival, not burying the tube under routine racks, and alerting the testing section when a STAT is delayed (instrument down, QNS, missing sample). If a STAT result is also critical, complete both priority handling and critical notification requirements.

Never leave a critical uncommunicated. End-of-shift “I thought days would call” is not acceptable. If you are the person who owns the flag at that moment, close the loop or hand off with explicit verbal + documented transfer to the next responsible staff member.

---

HIPAA on Phone Calls: Verify the Recipient

Speaking a potassium of 6.8 over the phone is a PHI disclosure. Protect it.

Before stating any result content

1. Confirm you reached the correct department/line.
2. Ask for the recipient’s name and role.
3. Verify they are an authorized recipient under policy (ordering provider, covering clinician, designated RN, etc.).
4. Use minimum necessary information—still include identifiers needed for safety (two IDs + result), but do not add unrelated history.
5. Do not leave full critical results on unsecured voicemail unless policy explicitly allows a limited message (many labs forbid detailed voicemail for criticals and require live contact).
6. Do not discuss criticals in public areas where visitors can overhear.
7. Family members are not automatic recipients of laboratory criticals—clinical team decides family disclosure.

---

Integrated Scenarios

Scenario A — Flag ignored
LIS shows critical low glucose; you are finishing a stock order. Stop the non-urgent task. Ensure the critical pathway is activated immediately.

Scenario B — No answer
Ordering office is closed. Follow after-hours call tree (covering service, ED, house supervisor)—do not leave a detailed voicemail and walk away if policy requires live notification.

Scenario C — Read-back fails
Recipient says “potassium 5.1” when you reported 3.1 (or vice versa). Correct clearly, request read-back again, then document.

Scenario D — HIPAA
A relative calls the lab asking for “the critical from this morning.” Direct them to the clinical team; do not release results to family from the lab phone without authorization pathway.

---

Link to Practice

Critical-value judgment items pair with LIS ethics and professionalism. Reinforce with scenario practice on /practice/ascp-mla.

---

Key Takeaways

• Critical values demand immediate authorized notification—not casual “abnormal” handling.
• Follow the call tree; read-back patient ID and result.
• Document who, when, what, by whom, plus attempts/escalation.
• STAT priority and critical severity both need active MLA support; never abandon a critical flag.
• Verify recipients before phone disclosure—HIPAA applies.