Organizing TB laboratory improvement with PDSA cycles
A tuberculosis laboratory quality improvement project becomes easier to manage when it is treated as a sequence of small, measurable changes rather than one large reform. Plan-Do-Study-Act (PDSA) cycles give the team a practical way to identify a problem, test a response, examine evidence, and decide what should happen next.
The method fits laboratories working with different levels of staffing, equipment, funding, and infrastructure. A facility may begin with specimen reception, result reporting, biosafety, or internal quality control. The priority is to choose a meaningful gap, define a realistic aim, and learn from actual work without disrupting essential TB testing services.
The GLI Quality Tool can provide the wider structure for this effort. Its four-phase roadmap and twelve Quality Systems Essentials help teams connect individual improvement cycles with a sustainable quality management system. PDSA is the engine for testing change; the roadmap helps ensure that improvements become part of routine laboratory practice.
Set the improvement direction
Begin by establishing a small project team with authority to observe work and make decisions. Include the laboratory manager or quality manager, staff who perform the relevant process, a biosafety representative where appropriate, and personnel responsible for equipment, procurement, or information systems if their roles affect the problem. A focused team is usually more effective than a large committee that meets rarely.
Review available evidence before selecting the first cycle. Useful sources include nonconformity records, external quality assessment results, internal quality control trends, turnaround-time data, stock-out reports, maintenance logs, staff observations, and user complaints. The purpose is to identify a process failure that is important, visible, and suitable for a short test.
Connect the selected issue to the relevant Quality Systems Essential. For example, delayed reporting may involve documents and records, assessment, process management, or customer focus. A biosafety gap may relate to facilities and safety, personnel, or equipment. This connection keeps the project aligned with the laboratory’s larger quality plan instead of treating each PDSA cycle as an isolated activity.
Define a measurable aim
A useful aim statement describes who or what will improve, by how much, and by when. “Improve specimen processing” is too broad to guide a cycle. “Increase the proportion of correctly labeled sputum specimens received from participating clinics from 82% to 95% within eight weeks” gives the team a defined population, measure, target, and time frame.
Select one primary measure and a few balancing measures. The primary measure shows whether the intended result is changing. Balancing measures reveal whether the intervention creates a new problem, such as faster processing accompanied by more transcription errors or reduced waiting time accompanied by unsafe work practices.
Establish a baseline using recent records, but check how the data were generated. A low compliance rate may reflect genuine performance problems, inconsistent recording, or unclear definitions. Agree on terms before collecting new data: what counts as a correctly labeled specimen, a delayed result, a complete worksheet, or a closed corrective action.
Keep the first aim modest enough to test. A single bench, shift, specimen type, or referring facility can provide useful learning. Once the process and intervention are understood, the team can expand the change with greater confidence.
Build the PDSA cycle
The planning stage should explain the current problem, likely causes, proposed change, responsible staff, resources, timing, and measurement method. Map the process briefly from beginning to end. For example, a result-reporting project may include verification, authorization, entry into the laboratory information system, communication to the clinic, and filing of the record.
Use root-cause tools proportionately. A process map, five-whys review, or cause-and-effect diagram may reveal that a reporting delay is caused by several linked issues: unclear authorization, missing contact details, an unreliable printer, and no backup procedure. Select one or two causes that the team can influence during the first cycle rather than attempting to correct everything at once.
The “Do” stage is a controlled test, not simply the launch of a permanent policy. Record what happened, who participated, deviations from the plan, and unexpected effects. If the team tests a new specimen-reception checklist for five working days, staff should note missing fields, time required, rejected specimens, and any confusion about responsibilities.
During “Study,” compare results with the baseline and examine the process behind the numbers. A small improvement may still reveal an important barrier. The team should ask whether the intervention was used as intended, whether the measurement method was consistent, and whether external factors influenced performance. In “Act,” decide whether to adopt, adapt, or abandon the change and then start the next cycle.
Choose practical tests for varied settings
PDSA cycles should match the laboratory’s operating conditions. A facility with limited connectivity might test a paper-based referral log, a wall-mounted escalation guide, or a scheduled review of pending results. A larger laboratory might evaluate barcode scanning, automated alerts, or dashboard reporting. The quality principle is the same: test a specific change with evidence that can be collected locally.
| Improvement focus | Small change to test | Primary measure | Possible balancing measure |
|---|---|---|---|
| Specimen reception | Use a short acceptance checklist at the receiving bench | Percentage of specimens accepted with complete information | Additional reception time |
| Result reporting | Introduce a daily pending-result review | Percentage of results reported within the target time | Reporting or transcription errors |
| Equipment maintenance | Add a weekly verification of maintenance status | Percentage of scheduled checks completed | Time diverted from testing |
| Document control | Place the current approved procedure at each work area | Percentage of observed documents at the correct version | Staff time spent replacing copies |
| Internal quality control | Review control trends at a fixed weekly meeting | Number of investigations completed when limits are exceeded | Meeting duration |
| Biosafety practice | Conduct brief observational feedback during one shift | Compliance with the selected safety behavior | Staff interruptions or workflow delays |
Choose interventions that staff can understand and repeat. A complicated form may produce more documentation without improving control. A short checklist, clearly assigned responsibility, reminder at the point of work, or scheduled review often provides a stronger first test than a broad training session with no follow-up.
Control documents and evidence
Quality improvement depends on trustworthy information. Each cycle should have a simple record containing the aim, baseline, intervention, dates, measures, findings, decision, and person responsible for the next action. Retain raw data where practical so that the team can verify calculations and explain results during internal audits or management reviews.
When a test changes a procedure, form, worksheet, or instruction, control the document before distributing it. The laboratory should know which version is approved, where it is available, who reviewed it, and what happened to obsolete copies. The guidance on document control practices can help teams establish consistent version numbering and approval arrangements.
Avoid creating records only to satisfy an audit. Each form should support a decision, demonstrate that a required activity occurred, or make a recurring problem visible. If staff cannot explain why a record is needed, the team should reconsider its design and remove unnecessary fields.
Use visual management carefully. A trend chart, status board, or control chart can make performance visible to staff, but displayed information must protect patient confidentiality. Data should be reviewed at a regular interval, with defined thresholds for escalation when results worsen or remain below the target.
Review results and spread gains
At the end of each cycle, hold a short review with the people who performed the work. Start with the evidence, then discuss what made the change easier or harder to use. Separate implementation failure from intervention failure. If a checklist was never available at the bench, poor results do not show that checklists are ineffective; they show that deployment was incomplete.
Document the decision to adopt, adapt, or abandon. Adoption means the change worked sufficiently and can become routine. Adaptation means the idea is promising but needs modification and another test. Abandonment means the intervention did not address the cause, created unacceptable risks, or required resources that are not sustainable. Each decision is useful learning when recorded clearly.
Before spreading a successful change, confirm that it works in more than one situation. Test it with another shift, staff member, instrument, specimen stream, or referring site. Consider whether training, supplies, supervision, equipment capacity, or procurement arrangements must change before expansion.
The broader GLI Quality Tool resources can help the project team connect its findings to phase-specific activities and checklists. Using the quality improvement checklists during periodic review can help identify related gaps in personnel, equipment, assessment, documentation, safety, and continual improvement.
Sustain the improvement
A PDSA project is complete only when the improved process is owned by the routine management system. Assign responsibility for monitoring, include the measure in the laboratory quality indicators, and specify what action is required if performance falls below the agreed level. Sustainability should not depend on the person who led the original test.
Update controlled procedures and train affected personnel whenever the final process changes. Orientation for new staff should include the revised practice, while existing staff may need a brief competency check. Supervisors can use direct observation, record review, or internal audit to confirm that the improvement remains active.
Maintain a visible improvement register with the project aim, current status, latest result, next review date, and unresolved risks. Review it during quality meetings and management reviews. Several small gains across specimen flow, safety, equipment, and records can gradually strengthen the entire TB laboratory quality management system.
The most effective projects combine disciplined measurement with respect for frontline knowledge. Start with one important problem, run a manageable test, study what the data and staff experience reveal, and make the next decision explicit. Use the GLI Quality Tool to anchor that learning in a complete quality framework, then document and sustain each gain. Begin the first PDSA cycle with a clearly defined aim and a review date already placed on the laboratory calendar.