GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Developing A Corrective Action Plan After A Failed TB Lab Proficiency Test

A failed tuberculosis laboratory proficiency test is a quality signal, not simply a disappointing score. It indicates that one or more parts of the testing pathway did not produce the expected result under external assessment conditions. The response should therefore protect patient care, identify the true cause, and strengthen the laboratory system rather than focus only on correcting one result.

Proficiency testing, external quality assessment, and panel testing can reveal problems that routine internal quality control does not detect. A laboratory may have competent staff and acceptable daily controls yet still experience failures caused by specimen handling, reagent performance, interpretation, documentation, equipment, or communication.

A well-designed corrective action plan turns the proficiency testing report into a controlled improvement process. It defines what happened, why it happened, who will act, what evidence will demonstrate completion, and how the laboratory will verify that the problem has not returned.

Secure The Result And Assess Immediate Risk

Begin by preserving the proficiency testing materials, worksheets, instrument printouts, electronic records, and final report. Do not discard or overwrite information while staff are trying to reconstruct events. Record the date of testing, specimen identifiers, methods used, personnel involved, equipment, reagents, control results, and any deviations from the routine procedure.

The laboratory director or quality manager should determine whether the failed result could reflect a broader patient-testing risk. If the same method, lot, instrument, or staff practice has been used for clinical samples, review recent internal quality control, maintenance records, repeat testing, error logs, and unusual result patterns. The review should be proportionate and confidential, with the aim of protecting patients rather than assigning blame.

If there is credible evidence that patient results may be unreliable, follow the laboratory’s escalation and notification procedures. This may include suspending a specific test, referring samples to a competent facility, reviewing affected reports, and informing relevant clinical or public health authorities. The decision, rationale, and approval should be documented.

Define The Nonconformity Precisely

A corrective action plan is weak when it describes the problem as “proficiency test failed” and immediately proposes retraining. The nonconformity needs a precise statement. Identify the analyte or TB test, the expected and reported result, the reporting deadline, the testing platform, the phase of the testing process, and the evidence showing that performance was unacceptable.

Separate the observed event from assumptions about its cause. For example, “the laboratory reported a false-negative result for a panel specimen” is an observation. “The technologist lacks competence” is a hypothesis that requires evidence. Other possible causes may include incorrect specimen reconstitution, transcription error, expired controls, unsuitable storage temperature, contamination, instrument malfunction, an unclear standard operating procedure, or an interpretation problem.

Use a structured investigation that follows the complete testing pathway:

Look for contributing conditions as well as the immediate mistake. A staff member may have followed an ambiguous procedure correctly, or a result may have been entered incorrectly because the reporting form lacks an independent verification step. These distinctions lead to sustainable action.

Investigate Root Causes With Evidence

Root-cause analysis should involve the people who performed or supervised the testing, the quality officer, and technical personnel familiar with the method. Construct a timeline from panel receipt to submission of results. Compare what actually happened with the current procedure, manufacturer instructions, biosafety requirements, and proficiency testing instructions.

Useful techniques include the five-whys method, a fishbone analysis, process mapping, and review of similar nonconformities. Avoid stopping at “human error.” Human error is often a symptom of a system weakness, such as workload pressure, poor workspace design, inadequate competency assessment, unclear labeling, insufficient supervision, or an information technology problem.

The investigation should distinguish correction from corrective action. A correction addresses the immediate issue, such as repeating an authorized control test, amending a record, replacing a deteriorated reagent, or correcting a transcription error. Corrective action removes or controls the underlying cause, such as revising the workflow, adding a verification step, improving storage monitoring, or reassessing staff competency.

Evidence To Collect During The Review

Review area Questions to answer Examples of objective evidence
Specimen and panel handling Were materials received, identified, stored, and prepared as instructed? Receipt log, temperature record, preparation worksheet
Method and equipment Was the approved method performed under suitable conditions? SOP, maintenance log, run record, instrument flags
Reagents and controls Were materials within expiry, correctly stored, and acceptable in use? Lot records, inventory log, control charts
Personnel and competency Was the assigned staff member authorized and competent for the task? Training record, observation checklist, competency assessment
Result management Was interpretation, verification, and submission accurate and timely? Worksheet, electronic audit trail, report review record

The evidence should be sufficient for another reviewer to understand the decision. If records are missing, that absence is itself a finding. It may indicate that documentation controls, record retention, or staff understanding require corrective action.

Build Actions That Address The Cause

Each action should be specific, assigned to a named role, given a realistic due date, and linked to completion evidence. “Improve staff performance” is not measurable. “The section supervisor will observe two complete runs using the revised SOP and document competency before the next proficiency panel” is much stronger.

Actions may include revising a standard operating procedure, introducing a second-person result check, replacing unsuitable consumables, repairing or recalibrating equipment, changing sample flow, improving environmental monitoring, or providing focused training. Training should be selected only when the investigation shows a knowledge or skill gap. Attendance at a classroom session alone does not prove competence.

For TB laboratories, risk controls must preserve biosafety and continuity of testing. Any method change, equipment replacement, or revised workflow should be reviewed for its effect on contamination prevention, staff protection, turnaround time, and result reliability. If testing is temporarily referred elsewhere, document how samples, reports, and clinical communication will be managed.

A practical plan can use the following fields: finding, root cause, immediate correction, corrective action, responsible person, target date, required resources, completion evidence, and effectiveness check. This format makes the plan useful during management review and future assessments.

Verify Completion And Effectiveness

Closing an action because a document was revised or a staff member attended training is premature. Completion means the planned step occurred; effectiveness means the step reduced the risk and improved performance. Both should be recorded separately.

Verification may include direct observation, review of a new batch of internal quality control results, examination of temperature or maintenance records, retrospective review of patient reports, an audit of result transcription, or successful participation in a subsequent proficiency testing round. For a procedural change, the laboratory may observe several routine runs and confirm that all critical steps are followed consistently.

Set an effectiveness review date based on risk. A high-risk molecular testing error may require prompt review and interim monitoring, while a documentation weakness may be assessed after several completed records. If the action does not work, reopen the investigation rather than marking the finding complete. The root cause may have been incomplete, or several interacting causes may remain.

The GLI Quality Tool provides phase-based checklists that can help teams connect a proficiency testing finding with relevant quality system activities, including equipment, personnel, documents, assessment, and continual improvement. Using a checklist as a prompt supports consistency, but it should complement professional judgment and local procedures.

Strengthen The Quality Management System

A proficiency testing failure often exposes a gap between written policy and daily practice. Use the event to review related processes across the laboratory rather than isolating the affected bench. If a result transcription error occurred, examine all reporting pathways. If reagent storage was inadequate, review temperature monitoring for other storage areas and critical supplies.

Share lessons in a controlled, non-punitive way. Staff meetings, quality huddles, and supervisory reviews can communicate the change, explain why it matters, and identify practical barriers. Protect confidential information and avoid using the event to embarrass an individual. A culture that encourages early reporting is more likely to detect weak signals before they affect patient results.

Trend proficiency testing outcomes with internal quality control, complaints, rejected specimens, turnaround time, equipment failures, and other quality indicators. Repeated errors in the same Quality Systems Essential may show that local actions are too narrow. Management should provide resources, remove obstacles, and confirm that corrective actions are integrated into the laboratory’s annual quality objectives.

The laboratory can also share a concise, de-identified learning summary with its quality network or use the GLI feedback channel to communicate practical observations about the tool and implementation experience. External feedback can help improve guidance for facilities working in different resource settings.

Keep The Plan Visible And Active

A corrective action register should be reviewed regularly until every action has documented evidence and an effectiveness decision. Overdue items need an explanation, a revised date, and escalation when resources or authority are blocking progress. The register should be available to authorized staff and referenced during internal audits and management review.

The strongest plans create a repeatable response for future external quality assessment events. They clarify who receives the report, who performs the risk review, how findings are investigated, when testing is restricted, and how performance is communicated to leadership. This reduces delays when the next proficiency testing result is unexpected.

Use the following principles when approving the plan:

A failed TB proficiency test should become a documented learning cycle: detect, contain, investigate, correct, verify, and standardize. Download the relevant GLI Quality Tool materials, convene the responsible laboratory team, and open a dated corrective action record while the evidence is still available. This disciplined response can restore confidence in the affected method and strengthen the quality management system well beyond a single proficiency testing event.