Root Cause Analysis For Stronger TB Laboratory Quality Systems
A reliable tuberculosis laboratory depends on more than accurate instruments and skilled scientists. When a culture is contaminated, a result is delayed, or a safety step is missed, the laboratory needs a disciplined way to understand what happened and prevent recurrence. Root cause analysis provides that structure.
A practical TB lab guide to root cause analysis should help staff move beyond blaming an individual. The purpose is to identify weaknesses in processes, equipment, training, communication, supplies, or the working environment. The 5 Whys technique and fishbone diagrams are simple tools, yet they become powerful when supported by records and tested against real laboratory practice.
This approach fits the quality management principles promoted by the GLI Quality Tool. Its phased roadmap and Quality Systems Essentials can help laboratories connect an investigation to document control, personnel competency, equipment management, assessment, safety, and continual improvement. The method can be used in a large metropolitan service or a small regional facility.
Australian laboratories may be working within NATA accreditation requirements, state or territory public health systems, and strict work health and safety obligations. A laboratory in Melbourne, Brisbane, or Sydney may have specialist support close by, while services in the Northern Territory, regional Western Australia, or remote communities may face freight delays, limited staffing, and restricted access to maintenance providers. Root cause analysis should reflect those operating conditions.
| Method | Best use | Main strength | Common limitation |
|---|---|---|---|
| 5 Whys | A focused incident with a likely process chain | Quick and easy to facilitate | Can oversimplify complex causes |
| Fishbone diagram | Repeated, complicated, or cross-functional problems | Shows several contributing factors | Can become a list without evidence |
| Record review | Confirming timelines and controls | Anchors findings in facts | May miss informal workarounds |
| Staff discussion | Exploring how work is actually performed | Reveals practical barriers | Can be affected by hierarchy or memory |
| Corrective action review | Checking whether change worked | Links analysis to improvement | Requires follow-up data |
Why Root Cause Analysis Matters
A rejected specimen, failed internal quality control result, or delayed positive report is an event that needs explanation, not merely a correction. Repeating the test may restore the immediate result, but it does not address why the error occurred. If the underlying issue is an unclear procedure, an unsuitable storage condition, or a recurring supply problem, the same event is likely to return.
Root cause analysis separates the direct cause from contributing causes and system causes. For example, a contaminated TB culture may appear to result from poor aseptic technique. Further investigation may show that a new staff member had not completed competency assessment, the procedure was difficult to find, and the disinfectant supplied to the bench was incorrectly diluted.
The investigation should be proportionate to risk. A minor documentation omission may need a short review, while a false-negative result or exposure incident requires a formal investigation, escalation through the quality manager, and careful consideration of patient and staff safety.
Start With A Precise Problem Statement
Begin with a neutral description of what happened. Include the test or process involved, the date and location, the observed deviation, and the potential impact. “The culture failed” is too vague. “Three liquid cultures from the regional referral batch showed contamination above the laboratory’s alert threshold during the week commencing 8 July” gives the team a workable starting point.
Avoid writing the suspected cause into the statement. “Technician error caused contamination” closes the investigation before evidence has been reviewed and may discourage staff from speaking openly. Use language such as “an unexpected contamination pattern was identified” until the facts support a causal finding.
Collect the initial evidence promptly. Relevant material may include worksheets, instrument logs, temperature records, maintenance reports, reagent lot numbers, environmental monitoring results, training records, and nonconformance reports. In Australia, records may also need to align with the laboratory’s NATA documentation system and local health service incident procedures.
Apply The Five Whys Carefully
The 5 Whys method asks why an event occurred, then continues asking why each answer was possible. The aim is to trace the chain from the visible problem to a controllable system weakness. If a sputum specimen was processed late, the sequence might examine why it entered the testing queue late, why the queue was not reviewed, why staffing coverage was inadequate, and why the workflow had no escalation trigger.
The technique should not become a ritual that always ends with “staff did not follow the procedure”. That answer may be incomplete. Ask why the procedure was not followed: was it unavailable, ambiguous, impractical, poorly taught, or inconsistent with the equipment in use? Also ask whether the laboratory design, workload, interruptions, or stock shortages made the expected behaviour difficult.
Five is a guide, not a fixed number. Some incidents need three questions; complex failures may need several branches. Record each answer and identify the evidence supporting it. If the team cannot verify an answer, label it as a hypothesis and assign an action to test it.
Build A Fishbone Diagram
A fishbone, or cause-and-effect diagram, is useful when multiple factors may have combined. Place the defined problem at the head of the diagram and create branches for categories such as people, methods, machines, materials, measurement, environment, and management. These categories can be adapted to the laboratory’s terminology and the relevant Quality Systems Essentials.
For a TB culture problem, the team might explore staff competency, specimen transport, biosafety cabinet performance, incubation conditions, media preparation, quality control, workload, and communication with the collecting site. A diagram helps prevent the discussion from focusing only on the person closest to the event.
Keep each cause specific. “Equipment” is a category, not a cause. “Incubator temperature alarm was disabled after repeated nuisance alerts” is specific enough to investigate. “Transport” can become “the courier schedule did not protect the recommended time from collection to processing,” which can then be tested against dispatch records.
Use Evidence In The Laboratory
A strong analysis compares written procedures with actual work. Observe the process where it occurs, speak with staff who perform it, and review a sample of normal as well as abnormal records. This can reveal workarounds that have become routine, particularly when a laboratory is managing vacancies, high demand, or limited access to specialist services.
Quality control data may help establish whether a failure was isolated or part of a trend. For culture laboratories, practical methods such as streak plate controls can support a closer review of contamination control and media performance. The investigation should still consider the complete workflow, from specimen collection and transport through reporting and communication.
Cost information can also expose process weaknesses. If repeat testing, wasted media, or emergency freight is increasing, a review of cost per test may help show the operational effect of a recurring problem. Financial evidence should inform priorities without replacing clinical risk assessment.
Make Corrective Action Measurable
Corrective action should address the cause that the investigation has demonstrated. Re-training alone is rarely sufficient if the real issue is an unclear form, inadequate equipment maintenance, or a staffing model that creates predictable delays. Actions should specify an owner, due date, required resources, and a measure of completion.
Useful actions might include revising a specimen acceptance procedure, introducing a second-person check for a high-risk step, changing the storage location for reagents, repairing an alarm, or arranging competency assessment for staff who perform a specialised method. In a remote Australian service, the action may need to account for supplier lead times, cold-chain arrangements, and the availability of a visiting engineer.
Practical Habits For Australian Laboratories
- Use a standard investigation form that records the event, immediate containment, evidence reviewed, causes, actions, and effectiveness check.
- Include staff from specimen reception, testing, quality, maintenance, and transport when the problem crosses departmental boundaries.
- Check whether an action is workable during night shifts, public holidays, staff leave, and periods of high respiratory illness demand.
- Link findings to the relevant GLI Quality Systems Essential and retain approved records in the laboratory’s document system.
- Review trends across sites, especially when specimens are referred between metropolitan and regional services.
The effectiveness review should be planned at the time the action is approved. A revised procedure is not proof of improvement. The laboratory might track contamination rates, turnaround times, rejected specimens, QC failures, or completion of competency checks for a defined period and compare results with the baseline.
Embed Learning In Routine Quality Work
Root cause analysis becomes valuable when its findings influence everyday management. Add recurring causes to quality meetings, internal audit schedules, risk registers, and management review. If several investigations identify unclear responsibilities, the laboratory may need to redesign the workflow rather than create separate reminders for each incident.
Share outcomes in a way that protects fairness and confidentiality. Staff are more likely to report near misses when the laboratory treats them as opportunities to strengthen systems rather than occasions for public blame. A short debrief can explain what changed, why it changed, and how the team will know whether the change worked.
Use the GLI Quality Tool’s phase-specific guidance and checklists to keep improvement practical. A laboratory can start with a small investigation, document the reasoning, and gradually build a consistent approach across safety, personnel, equipment, documentation, and assessment. This creates a durable quality culture suited to both well-resourced city laboratories and services supporting Australia’s regional and remote communities.
Adopt one recent TB laboratory incident, complete a 5 Whys review, and draw a fishbone diagram with the people involved in the work. Record the evidence, approve one measurable corrective action, and schedule an effectiveness check. That first completed investigation can become the template for a clearer, safer, and more reliable quality management system.