GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Designing a practical assessment tool for TB microscopy networks

A laboratory assessment tool for a tuberculosis microscopy network must do more than measure whether individual sites meet technical requirements. It should show how well the network detects, records, verifies, communicates, and improves results across facilities with different workloads, staffing levels, equipment, and access to supervision.

The most useful tool combines structured scoring with evidence review and clear follow-up actions. It should help assessors identify immediate risks, distinguish isolated site problems from network-wide weaknesses, and track whether corrective actions produce lasting improvement.

The GLI Quality Tool offers a useful foundation because its four-phase roadmap connects laboratory development to twelve Quality Systems Essentials. These include organization, personnel, equipment, purchasing and inventory, process management, information management, documents and records, assessment, and continual improvement.

Define the purpose and scope

Begin by stating what the assessment is intended to accomplish. A tool used for accreditation preparation will require more detailed evidence than one used for routine supervisory visits. Similarly, a national mapping exercise may prioritize coverage and urgent gaps, while a quality improvement assessment may focus on root causes and corrective action.

The scope should specify the facilities, services, testing methods, and reporting pathways included. For a TB microscopy network, this may cover peripheral microscopy sites, district laboratories, referral laboratories, supervisors, specimen transport links, and the central coordinating unit. If digital reporting, external quality assessment, or reagent distribution is included, those functions should appear in the scope rather than being treated as informal background activities.

Set a defined assessment cycle. A baseline assessment can establish current performance, followed by shorter verification visits at agreed intervals. The same core indicators should be retained between rounds so that the network can distinguish genuine progress from changes caused by different assessors or altered questions.

Convert standards into observable evidence

Broad requirements such as “the laboratory maintains quality” are difficult to score consistently. Convert each requirement into an observable assessment item. For example, instead of asking whether records are well managed, check whether the laboratory has a current register, defines who may enter results, protects records from unauthorized changes, and can retrieve a selected entry within a specified period.

Each item should identify the evidence expected. Evidence may include direct observation, interviews, document review, record sampling, equipment inspection, or review of quality indicators. Combining evidence types reduces the risk that a site receives a high score because staff can describe a procedure that is not consistently followed.

Use language that assessors and laboratory staff can interpret in the same way. Terms such as “available,” “current,” “implemented,” and “effective” need operational definitions. A current procedure might mean approved, dated, version-controlled, and reviewed within the required interval. Effective implementation might require evidence from several recent records rather than a single example.

Linking the tool to a recognized quality framework also improves continuity. The quality management framework can help organize questions around system requirements while keeping the assessment understandable for facilities working in varied resource settings.

Build a network-level measurement model

A microscopy network needs two connected views of performance. The facility view examines whether each site can perform testing safely and reliably. The network view examines whether sites are supported, monitored, supplied, and connected to referral and reporting systems. A laboratory may follow the correct staining procedure yet still contribute to poor program performance if slides are not transported, results are delayed, or errors are not communicated.

Use a hierarchy of measures. Domain scores summarize broad areas, process indicators show whether essential activities occur, and outcome indicators show the effect on testing quality and service delivery. Examples include the proportion of staff trained and authorized, stock-out frequency, concordance in blinded rechecking, turnaround time, rejected specimens, and the percentage of corrective actions closed by their due dates.

Avoid allowing one strong area to conceal a critical failure. A site with excellent documentation should not receive an acceptable overall rating if it lacks functioning safety controls or has persistent false-positive results. Use critical items or risk thresholds for issues involving biosafety, result integrity, equipment failure, or staff competency.

Design element Facility-level focus Network-level focus
Personnel Training, competency, authorization, workload Staffing distribution, supervision, refresher training
Equipment and supplies Function, maintenance, availability, storage Procurement, redistribution, downtime trends
Testing process Smear preparation, staining, reading, reporting Standardization, referral pathways, error patterns
Records and information Completeness, traceability, confidentiality Data aggregation, timeliness, feedback loops
Assessment Internal checks, rechecking, corrective action External quality assessment, supervisory coverage
Improvement Local action plans and follow-up Policy changes, resource allocation, system learning

Design scoring that supports action

A scoring system should be simple enough for routine use and detailed enough to guide decisions. A four-level scale often works well: absent, partially implemented, largely implemented, and fully implemented. The tool should define each level with evidence examples, since numerical labels alone can create false precision.

Consider scoring compliance and risk separately. Compliance describes how closely a site follows the expected process, while risk reflects the possible effect of a gap on patients, staff, results, or program decisions. A minor documentation omission and an uncontrolled biosafety hazard should not receive the same management priority merely because both are marked “partially implemented.”

Include a “not applicable” option with a required explanation. This prevents assessors from forcing a score where a process genuinely does not apply, while discouraging sites from using the option to avoid difficult questions. The system should also prevent blank items from being mistaken for satisfactory performance.

For each deficient item, capture the evidence, responsible person, due date, required resources, and verification method. The assessment becomes far more useful when it produces a manageable corrective action plan rather than a long list of disconnected observations.

Make data collection consistent and efficient

Create an assessor guide alongside the digital or paper form. It should explain the purpose of each section, acceptable evidence, interview prompts, sampling rules, scoring examples, and procedures for resolving disagreements. New assessors should practice with the guide and compare their ratings before conducting independent visits.

Sampling is particularly important for TB microscopy. Reviewing one slide, one register entry, or one month of stock records cannot represent routine performance. Define a practical sample, such as selected slides from different days, recent positive and negative entries, several result reports, and records covering both high- and low-workload periods. The sample can be adjusted for facility size, but the adjustment should be documented.

Design the data system to support offline work where connectivity is unreliable. It should allow assessors to save records locally, attach evidence securely, flag critical findings, and synchronize later. Automated calculations can reduce errors, but the underlying scoring rules must remain visible to users and managers.

Protect patient and staff information. Use coded identifiers where possible, restrict access by role, and avoid including identifiable patient data in narrative findings. A clear audit trail should show who entered, reviewed, edited, or approved assessment information.

Connect assessment with quality improvement

Assessment should be treated as a cycle rather than a one-time inspection. After data collection, the assessor and laboratory team should review findings together, confirm the evidence, and identify root causes. A recurring stain-quality problem, for example, may reflect water quality, supply interruptions, unclear procedures, inadequate supervision, or workload pressure rather than a simple staff error.

Organize findings by urgency and ownership. Immediate risks require prompt containment, while systemic issues may need changes in procurement, training policy, supervision, or referral design. Network managers should be able to see which findings can be resolved locally and which require central action.

Track corrective actions in the same system as the original assessment. Useful fields include action status, evidence of completion, date verified, and whether the intervention was effective. A closed action should mean that implementation has been confirmed and the problem has not simply been marked complete by declaration.

Reliable records make this follow-up possible. Guidance on record-keeping practices provides relevant principles for traceability, retention, review, and controlled documentation that can be adapted to microscopy services.

Recommendations for implementation

A strong tool is developed with the people who will use it. Laboratory staff, supervisors, quality officers, program managers, and information specialists can identify ambiguous questions and reveal barriers that are invisible in policy documents.

Pilot the instrument in facilities with different sizes and operating conditions before national deployment. Review completion time, missing data, scoring variation, and whether findings lead to practical actions. Revise the tool when an item repeatedly produces disagreement or collects information that no one uses.

Put the tool into routine practice

A well-designed assessment tool should become part of the laboratory management system, not a separate reporting exercise. Align its domains with existing supervisory visits, external quality assessment, staff competency reviews, stock monitoring, and management meetings. This reduces duplicate data collection and makes quality activities easier to sustain.

Review the instrument periodically as testing methods, information systems, policies, and network structures change. Retain stable indicators for trend analysis, but revise questions when they no longer reflect current risks. The goal is a credible picture of performance that helps laboratories act, supports managers in allocating resources, and strengthens confidence in TB microscopy results.

Start with a focused pilot, document what the evidence reveals, and expand the tool through staged implementation. When every finding has an owner, a deadline, and a verification step, assessment becomes a practical engine for safer work and more dependable tuberculosis diagnosis.