GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

A Practical Weekly Review Of TB Laboratory Quality Indicators

A weekly review of tuberculosis laboratory quality indicator charts turns routine data into an early-warning system. It helps a laboratory see whether testing is timely, accurate, safe, and consistent before a small deviation becomes a service disruption or a patient-care problem.

The review does not require complex software. A clear chart, reliable source records, agreed thresholds, and a disciplined discussion are often enough. The aim is to identify meaningful variation, verify its cause, assign action, and check whether the response worked.

Quality indicators may cover specimen rejection, turnaround time, contamination, testing volume, equipment downtime, internal quality control, external quality assessment, biosafety incidents, and report corrections. The right set depends on the tests performed, the laboratory’s workload, and the risks in its testing pathway.

Establish A Consistent Review Routine

Schedule the review on the same day each week and assign a named facilitator. The laboratory manager, quality officer, or section supervisor can lead, while staff responsible for reception, testing, reporting, equipment, and safety contribute relevant information. A fixed routine makes the review part of normal work rather than an occasional response to a crisis.

Use the same reporting period every time, such as Monday through Sunday. Record the date when the review occurred, the indicators examined, the people present, and the decisions made. If a public holiday, instrument failure, stock-out, or staff absence affected the period, note it beside the chart rather than leaving the context undocumented.

The GLI Quality Tool provides a useful framework for connecting weekly indicator review with broader quality management activities. Its focus on assessment, documentation, equipment, personnel, safety, and continual improvement helps laboratories avoid treating charts as isolated statistics.

Prepare Reliable Data Before The Meeting

Begin by confirming that every value has a source record. A specimen register, laboratory information system, equipment log, incident form, stock record, or quality control worksheet should support the number shown on the chart. If data are incomplete, label the result as incomplete instead of filling gaps with estimates.

Check both the numerator and denominator. For example, a rise from four rejected specimens to six may appear serious, but its significance differs when the weekly workload changes from 100 specimens to 300. Calculate percentages only when the denominator is appropriate, and retain the raw count so staff can understand the scale of the event.

Use a short data-validation checklist before discussion:

Read The Chart For Patterns And Signals

A weekly chart should show the current result alongside previous weeks, the target, and any alert or action threshold. A run chart is often sufficient. For indicators with an expected range, such as turnaround time or contamination, display the baseline and identify the point at which investigation is required.

Do not react to every movement in the line. Look for sustained change, repeated threshold breaches, a sudden outlier, a gradual drift, or a difference between testing areas or shifts. A single unusual value deserves verification; a repeated pattern usually deserves a structured investigation.

Indicator Weekly signal to examine Possible interpretation Immediate verification
Specimen rejection rate Repeated rise or breach of target Collection, transport, labeling, or reception problem Review rejection reasons and collection sites
Turnaround time More delayed results or widening spread Workload, staffing, equipment, or referral delay Check receipt, testing, authorization, and dispatch times
Contamination rate Sudden increase in one period or section Processing, environmental, reagent, or technique issue Review controls, batches, cleaning, and staff records
Equipment downtime Longer or repeated interruptions Maintenance, power, calibration, or supply problem Examine equipment logs and service reports
Corrected reports Increase in amendments or transcription errors Documentation, review, or result-entry weakness Sample amended reports and trace the approval process

Interpretation should include operational context. A temporary increase in turnaround time during a national campaign may have a different cause from a gradual delay that appears during every weekend shift. Compare similar periods where possible, and avoid ranking staff or sites before the underlying process has been examined.

Investigate Deviations Without Blame

When a chart signals a problem, define the deviation precisely. State what happened, when it occurred, which process was affected, how many specimens or results were involved, and what the expected performance was. “Poor turnaround time” is too vague; “nine of 42 eligible specimens exceeded the 48-hour target during the evening shift” gives the team something measurable to investigate.

Trace the workflow from specimen receipt to final reporting. Ask where the delay, error, or failure first became possible. Consider workload, staffing, competency, supply availability, equipment status, environmental conditions, transport, information flow, and unclear instructions. Separate an immediate cause from a contributing factor and from a system weakness.

The purpose is learning and risk control, not assigning personal blame. A staff member may have made an error, but the review should also examine whether the procedure was clear, training was current, supervision was available, and the work environment supported correct performance. This approach produces stronger corrective actions and encourages accurate reporting.

For a recurring issue, create a formal record using guidance on corrective action logs. The log should connect the indicator signal to its root cause, action owner, due date, verification method, and closure decision.

Link Each Finding To An Action

Every significant finding should end with a documented decision. The action may involve retraining, revising a procedure, repairing equipment, changing specimen transport arrangements, adjusting workload distribution, improving stock control, or reviewing results before release. Select an action that addresses the cause rather than merely reminding staff to “be careful.”

Assign one accountable person and a realistic due date. If several teams are involved, identify the lead owner and list supporting roles. Define the evidence that will show completion, such as a maintenance certificate, revised form, competency assessment, transport audit, or three consecutive weeks within the target range.

Prioritize actions according to patient risk, biosafety risk, regulatory significance, recurrence, and the number of specimens affected. A small documentation error may need a quick local fix, while a suspected loss of result integrity or exposure event requires immediate escalation, containment, and management review.

Safety-related deviations need their own response pathway. If a spill, exposure, unsafe handling event, or containment failure occurred, complete an appropriate safety incident report and preserve the facts needed for follow-up. The weekly chart review can track whether preventive actions reduced recurrence, but it should not replace urgent incident management.

Verify That Corrective Actions Worked

Closing an action because a meeting occurred is not the same as verifying effectiveness. The review team should decide how and when to test the result. A revised specimen transport process might be checked through rejection rates over four weeks; a competency intervention might require direct observation and review of subsequent quality control records.

Use the next weekly chart to evaluate whether performance changed. Compare equivalent periods and consider whether the workload or case mix was similar. If the indicator improves briefly and then worsens, the action may have been incomplete, poorly implemented, or dependent on one person.

Record the verification result as effective, partially effective, ineffective, or pending. If the target was not achieved, reopen the investigation and revise the action. This creates a continual improvement cycle: measure, interpret, investigate, act, and verify.

Recommendations For A Stronger Weekly Review

A concise meeting record should capture the chart reviewed, abnormal findings, contributing factors, decisions, owners, deadlines, and follow-up evidence. Store it with related quality records so an auditor or supervisor can trace the decision from source data to improvement.

The weekly discussion should also communicate important learning to the wider team. Share changes to procedures, equipment status, safety controls, or specimen requirements during shift handovers and staff meetings. Feedback closes the information loop and helps staff see how accurate recording supports better TB diagnosis and laboratory safety.

Make the review a protected quality activity rather than an optional conversation. Bring the updated charts, source records, action log, and incident information to the next scheduled session, then document decisions before the meeting ends. With consistent review and verified follow-through, laboratory data become a practical tool for safer, faster, and more reliable TB testing.