Critical Lab Result Alerts in Nigeria: What Hospital Software Should Do

Night shift, potassium 6.8. The scientist sees it. The result sits in a WhatsApp group, or in a folder, or on a printer nobody collects until morning. A critical lab alert is the interrupt: the value is recognised as critical, the ordering clinician is told, and someone can show who was notified. It is not a red High badge that staff can scroll past.

This guide is for medical directors, pathologists, lab managers, and administrators buying EMR or HMS in Nigeria. Pair it with the laboratory LIMS path and NEWS2 (vitals, not analytes). Score the alert on a named patient with a real potassium, not a slide titled “AI safety.”

What is a critical lab result alert in a Nigerian hospital?

In lab medicine, a critical (sometimes called panic) value is a result that may need immediate clinical attention, not only a comment on the report. The classic SOP is still a phone call with read-back. Software should make that SOP visible. It does not replace the call.

At minimum you should be able to:

• Separate critical bounds from ordinary reference ranges on each catalogue field.
• See Critical Low / Critical High at result entry, not only after print.
• Confirm sign-off when any critical is present, so the scientist is not one click from a silent release.
• Notify the ordering clinician in the product (urgent, named patient, link back to the request).
• Record that the doctor was notified, and who signed the result.

Buyers mash four products into “we have critical alerts”:

1. A High / Low flag. Useful. Not the same decision as critical.
2. Catalogue critical bounds plus an urgent notice. The results screen computes critical from the field’s own limits, asks the scientist to confirm, and writes an in-app notice to the ordering doctor. This is the DawaHQ day-to-day claim.
3. A named-analyte checker plus a dedicated critical channel. A second, conservative list (potassium, sodium, glucose, haemoglobin, WBC, platelets, INR, creatinine) can raise a critical_lab notice and an optional ops Telegram. Ask which path you are watching.
4. A patient “result ready” SMS or WhatsApp. Collection logistics. It must not carry the potassium into a family phone.

If a vendor says “we escalate critical labs,” ask which of those four they opened. Then type a potassium above the field’s critical high and watch who is interrupted.

DawaHQ treats this as clinical safety on the diagnostic lab module (laboratory is core, enable-per-clinic). Do not buy a standalone LIMS that cannot see the same patient as the chart and the till.

How is a critical value different from an abnormal flag?

Medical directors already know the split. Vendors blur it because both colour a cell.

Reference range / abnormal. The result is outside the usual interval for that field (age- and sex-aware when your catalogue supports it). A slightly high urea is abnormal. It is not automatically a 2 a.m. phone call.

Critical bound. A tighter limit the laboratory director owns. Crossing it means notify now. A potassium of 6.8 mmol/L is the teaching example. A haemoglobin of 4.6 g/dL is another. The software should show Critical Low or Critical High as its own state, not recycle the High badge.

DawaHQ’s result-entry screen uses five states: normal, low, high, critical low, critical high. Critical bounds are checked first. The summary bar counts criticals. A confirm modal appears when any critical is present: the doctor will be notified; the scientist can still cancel and review.

Do not treat NEWS2 as a lab-value engine. NEWS2 aggregates ward vitals. A critical potassium is a laboratory event. You want both. See NEWS2 and critical care. Do not call either matcher “AI.” Catalogue limits and named-analyte rules are deterministic.

Who should own the critical thresholds?

The laboratory director (or the pathologist who signs the SOP), not the vendor’s marketing PDF, and not a cashier who edits tariffs.

Ask for fields staff already argue about in quality meetings:

| Control | Why it matters | |---------|----------------| | Reference low / high | Ordinary abnormal flags | | Critical low / high | The notify-now bounds | | Unit | mmol/L vs mg/dL mistakes are how glucose alerts lie | | Who may edit | Lab catalogue admin, not every receptionist | | Audit of the edit | Yesterday’s limit is how you defend a missed call |

DawaHQ stores critical_low and critical_high on lab catalogue fields (Settings, Lab). Result entry reads those bounds. If a field has no critical limits, the screen will not invent a panic value. Empty bounds are a go-live job, not a silent safety net.

A second, conservative named-analyte list ships for an alternate submit path (starting values, not a WHO certificate, not your SOP): potassium below 2.5 or above 6.0 mmol/L; sodium below 120 or above 160 mmol/L; glucose below 2.5 or above 25.0 mmol/L; haemoglobin below 5.0 g/dL; WBC below 1.0 or above 30 ×10⁹/L; platelets below 20 ×10⁹/L; INR above 5.0; creatinine above 800 μmol/L. Troponin and bilirubin sit on a separate checklist. Paediatric and assay-specific cutoffs remain yours. Confirm units in the demo: mg/dL typed against a mmol/L bound will lie.

What should happen at result entry and sign-off?

A critical value that appears only on the printed report is a filing system, not an alert.

At entry. The scientist types the number. The field goes red. The badge says Critical Low or Critical High. A banner counts criticals on the request. DawaHQ does this from the catalogue bounds on the results screen.

At sign-off. If any critical is present, demand a confirmation step. DawaHQ opens a modal: confirm that the doctor will be notified, or cancel and review. Sign-off then completes the request and writes the notice.

What the server should do. Does it re-check every analyte, or trust the count the results screen sent? DawaHQ’s day-to-day sign-off path sends critical_count with the patch and raises urgent priority when that count is greater than zero. The message includes the count and who signed. The alternate submit path re-runs the named-analyte checker on the server. In the demo, break a potassium and watch both the badge and the notice.

Unpaid results. A critical potassium cannot wait for the cashier. Emergency release of a pending-payment request should require a written reason and leave who, when, and why. DawaHQ allows that for owner, admin, doctor, or lab scientist. The invoice can stay open. See the cashier queue. Walk-in requests with no ordering doctor still need a named inbox owner.

Who must be notified, and what should not go to the patient’s phone?

Ordering clinician, in the product. Urgent in-app notice, named patient, tests, critical count, link to the request. That is the DawaHQ sign-off claim. It is not a phone call and not a pager.

Optional ops channel. A dedicated critical_lab notice and an optional Telegram alert exist on the alternate submit path. Telegram is fire-and-forget and not configured for every clinic. Keep identifiable values off group chats you do not control.

Clinic owner escalation. A scheduled job can look for unacknowledged critical verification records older than 30 minutes and notify the owner. That is not a CAP, Joint Commission, or CLSI certificate, and it is not the same table as day-to-day sign-off. If the vendor cannot show an unacknowledged record age out, do not buy “automatic 30-minute escalation.”

Patient channels. WhatsApp, SMS, and email add-ons can say a result is ready. The template does not include the number. That is correct. The patient portal can show completed lab summaries when enabled. It is not raw analyser output, and patients cannot pay from the portal today.

A critical result may justify emergency release. It does not submit an NHIA portal claim. Prefer HMO claim workflows. See HMO claims. Minimise names and values in broadcasts. Prefer NDPA-oriented consent logging and a patient-access audit trail. We do not sell “NDPA certified” or “HIPAA lab EMR.”

Is a red badge the same as acknowledgement?

No. A badge is visibility. Acknowledgement is a named person saying they have seen the critical result.

Read-back (who called, who repeated the value, when) is a laboratory SOP. Software can store critical_acknowledged_by on a verification record. DawaHQ has those fields and an acknowledge route. The bell can offer Acknowledge on some urgent lab notices. The day-to-day sign-off notice links to the results page. Confirm the button writes the verification acknowledgement, not only marks the bell read.

Assign who clears renal, maternity, oncology, and general OPD. Flags without owners become wallpaper. A cashier should not acknowledge a critical potassium. A locum should use their own login. See staff roles and handover.

What should we test in a critical-alert demo?

Bring the medical director or the lab manager, not only the cashier.

1. Open Settings, Lab. Set critical high on potassium (for example 6.0 mmol/L) and confirm the unit. Leave a second field with no critical bounds.
2. Order an E-U-Cr on a named patient. Enter potassium above that critical high. Confirm Critical High, a critical count, and that a High-only field does not steal the same badge.
3. Click sign-off. Confirm the modal. Cancel once (nothing notified). Confirm again.
4. Log in as the ordering doctor. Confirm an urgent notice: patient, critical count, link. Open the result.
5. Ask whether that notice is urgent lab_result, or a dedicated critical_lab plus Telegram. Ask to see a 30-minute owner escalation on this path. If they cannot show it, write that down.
6. If you use WhatsApp or SMS, confirm the patient message is “result ready,” not the potassium.
7. Mark the request unpaid. Emergency-release with a reason under five characters should fail. A real reason should unlock sign-off and leave who / when / why.
8. Ask for “AI critical detection,” “CLSI certified,” “NDHI / FHIR,” or “NHIA integrated alerts.” DawaHQ does not ship those claims.

If step 3 only says High, you do not have a critical state. If step 5 never interrupts the doctor, you have a badge.

What to do next

This week, list the analytes your SOP already treats as call-now (potassium, sodium, glucose, haemoglobin, platelets, INR at minimum). Put those bounds on the catalogue. Name who owns the doctor inbox after 16:00.

Then book a demo or request access. Walk one critical potassium, one confirm modal, one urgent doctor notice, and one patient “result ready” message that does not include the number. Explore diagnostic lab, HMS for Nigeria, and EMR for Nigeria. Pricing is sales-led from ₦25,000/month, then a scoped quote. If the product cannot interrupt the ordering clinician, it will not help after the arrest.