GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Building a TB Lab Quick Reference Card

Developing a TB lab quick reference card for antimicrobial susceptibility breakpoints and critical concentrations should answer three bench-level questions: what is reportable, what needs confirmation, and who must act. It must be quick to use on an after-hours run while remaining clear enough that a laboratory threshold is never mistaken for a treatment recommendation.

Relevant guidance is often scattered across a laboratory information system, a WHO table, an interpretive guideline and a jurisdictional procedure. Combining operative values and actions reduces search time during reporting and follow-up. The card should point to controlled documents rather than replace them, and identify when a specialist or public-health team must review an isolate.

Australian laboratories add practical complexity. A specimen may travel from Alice Springs, Darwin or regional Western Australia to a major metropolitan laboratory, while results move through state and territory TB programs and the national notifiable disease surveillance system. Clear referral contacts, plain-English wording and a stable format matter when the audience includes laboratory scientists, clinicians, Aboriginal and Torres Strait Islander health services and remote teams.

The GLI Quality Tool offers a useful foundation through its four-phase roadmap, twelve Quality Systems Essentials, phase-specific checklists and downloadable materials. Within that framework, the card should align with the laboratory’s current quality management system, use authoritative breakpoint sources, and carry a visible review date. A practical draft can then be tested against real cases rather than created in isolation.

Why a quick reference card helps

Antibiotic susceptibility testing results often pass through several hands: bench staff perform or review the test, another scientist checks it, and a clinician or TB program receives the report. A compact card prevents values copied without units, outdated interpretive notes and unclear escalation routes. It also gives after-hours staff a consistent reference when the supervising scientist is unavailable.

The card should answer operational questions rather than replace specialist interpretation. It can distinguish a laboratory interpretation from a clinical decision, identify results needing repeat or confirmatory testing, and show where rifampicin, isoniazid or fluoroquinolone resistance changes urgency. It should never imply that a laboratory finding alone determines a patient’s regimen.

Separate critical concentrations from breakpoints

A critical concentration is a method-specific laboratory value used to discriminate resistant from susceptible growth for a named antimicrobial and organism. It supports classification and quality control. It is not a drug dose, nor automatically a clinical breakpoint, and it can differ between methods. State this plainly so numbers are not interpreted outside their technical context.

Clinical breakpoints connect test results with expected treatment outcomes. For M. tuberculosis, many agents lack routine clinical breakpoints, so WHO critical concentrations or EUCAST epidemiological cutoff values may be used for laboratory questions. CLSI principles may apply elsewhere. The card must name the source and version rather than presenting every value as a universal constant.

Categories such as susceptible, intermediate or resistant should follow the reporting framework in force at release. “Susceptible” means the isolate is expected to respond under the specified conditions, not that every patient will recover. Unusual MICs, values near a threshold, mixed growth and discordant molecular and phenotypic results require review. The card should trigger that review through a named action.

Map results through the testing pathway

Start with the request and specimen context, including the drug-susceptibility testing method, instrument, culture status and relevant prior treatment. Phenotypic DST may use proportion testing on solid media, broth microdilution or validated automated methods. Record the organism as M. tuberculosis complex where appropriate, and do not transfer critical concentrations between closely related species without evidence.

Molecular assays add speed and can detect rifampicin resistance or specific resistance determinants before a phenotype is available. They may not supply an MIC, can miss some variants and cannot always resolve mixed populations. Sequencing and confirmatory phenotypic testing can clarify important discordance. The card should state which evidence supports each report and whether a molecular prediction has been confirmed.

A practical result pathway is to verify QC and patient identifiers, compare the measured result with the authorised threshold, classify it, check discordance, then release and notify. Borderline values should be repeated from a fresh inoculum or confirmed by a suitable method, subject to the validated procedure. Record the final interpretation in the laboratory information system and send notifications through the responsible jurisdictional pathway.

Design for Australian conditions

Australia’s size and the turnaround times of commercial flights and courier networks make traceability essential. Each result should show the originating laboratory, specimen identifier, receiving laboratory, date and time, and referral contact for an isolate requiring confirmation. For work involving specimens from remote Northern Territory or Western Australian services, a phone contact can be more useful than an email address alone.

Tuberculosis is nationally notifiable in Australia. State and territory authorities coordinate with the Communicable Diseases Network Australia and Australia’s national notifiable diseases surveillance system. The reference card can name the local escalation pathway without reproducing jurisdictional rules, and it should avoid implying that a laboratory report alone completes public-health follow-up.

Australian laboratories should fit the tool to their accredited quality system. If the service is accredited by the National Association of Testing Authorities, the card should complement relevant ISO 15189 expectations, validated procedures, internal quality control and external quality assessment. Plain words such as “repeat”, “confirm” and “notify” suit local handovers better than unexplained abbreviations. Because this work can involve live cultures, nearby documentation should also include the GLI advice on waste decontamination guidance.

Build quality controls into the card

Assign a technical owner and a backup, usually from the microbiology or molecular team. Record the approval date, next review date, document number and source versions for each threshold. Set review triggers for WHO or standards changes, new drug presentations, instrument upgrades, validation findings and recurring reporting queries. Archive superseded versions so an old card cannot be mistaken for the current one.

Quality assurance extends beyond correct printing. Each local test method needs fit-for-purpose validation or verification, accepted QC ranges and external quality assessment participation. Include what to do when QC fails, the isolate is contaminated, growth is insufficient or a result is indeterminate. Escalation contacts should cover the laboratory, clinical microbiology specialist, TB program and public-health notification team.

Use audit data to test whether the card works: time to confirm borderline results, reports with complete interpretive notes, recurring corrections and feedback from after-hours staff. Keep patient identifiers off the reference copy. Test samples and fictional cases should not reveal personal information, even when the card is used during training.

Card content and usability checks

The card should present a consistent record for every drug and method. A useful clinical content checklist includes:

Usability and document-control checks are equally important:

Pilot the layout with scientists who work weekends and with staff new to TB. Ask them to interpret sample cases aloud and locate the confirmatory and notification steps without help. Revise ambiguous labels before printing. A shorter card that produces the same action is more effective than a dense matrix that resembles the source guideline but cannot be used at the bench.

Make the card part of daily work

Roll the reference card through the GLI Quality Tool roadmap. During assessment, use the relevant checklist to identify gaps in staff competency, document control and referral arrangements. During improvement planning, pilot one card with one reporting group, capture questions and track amendments through the quality system. The card should become an output of the laboratory’s management process, not an informal personal aid.

Train staff with worked examples: a clear susceptible isolate, a borderline phenotypic result, a molecular rifampicin-resistance signal and a discordant isolate. Demonstrate when to repeat, confirm, notify and contact the TB program. Keep a short change log showing why thresholds, contacts or actions moved. Use the linked continuous improvement practices to turn recurring errors into controlled tests of change.

Leadership can then judge success through fewer clarification calls, shorter confirmation times and more complete reports. Review performance at the same interval as other laboratory indicators, while also reviewing immediately when guidance changes. Keep the most current electronic version in the quality management system and distribute controlled copies to benches, on-call rooms and referral partners.

Start now by naming the card owner, selecting the authorised interpretive sources and listing the laboratories and TB programs that need current contacts. Draft one A5 side from real de-identified reporting cases, test it during the next after-hours shift, and assign a formal approval date.