GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

A reliable format for reporting TB drug susceptibility results

Developing a standard reporting format for TB drug susceptibility testing results helps laboratories communicate clear, comparable, and clinically useful findings. A well-designed report reduces transcription errors, prevents ambiguous interpretations, and gives clinicians and tuberculosis programs the information needed to select or adjust treatment.

The format should work across the full testing pathway, from specimen receipt and identification of Mycobacterium tuberculosis complex to the final release of susceptible, resistant, or inconclusive findings. It should also distinguish results produced by rapid molecular assays from those generated through phenotypic drug susceptibility testing.

A useful report is more than a list of drugs and laboratory outcomes. It is a controlled record with defined terminology, traceable methods, authorized review, and enough context to support safe decisions without overwhelming the recipient.

Define the report’s purpose and users

Before designing fields, identify who will read and act on the report. Clinicians may need a concise resistance profile and interpretive comment, while the national tuberculosis program may require additional information for surveillance, cohort management, and quality monitoring. Referral laboratories may need method details, run identifiers, and a record of the original specimen.

The report should state whether it presents an initial molecular resistance result, a phenotypic DST result, or a consolidated interpretation based on several tests. If results are issued in stages, each report should show its status clearly, such as “preliminary,” “partial,” or “final.” This prevents an early result from being mistaken for a complete susceptibility profile.

Laboratory managers should align the reporting workflow with program objectives and reporting obligations. Guidance on national TB targets can help connect laboratory outputs with broader surveillance, case-management, and quality goals.

Establish a consistent patient and specimen identity

Every report needs reliable identifiers that link the result to the correct patient and specimen. A practical core includes the laboratory accession number, patient identifier, date of birth or age, sex where required, requesting facility, specimen type, collection date, and date received. Local privacy rules should determine which personal details are displayed and how electronic records are protected.

The accession number should be prominent and remain unchanged through amended reports. If multiple specimens are submitted for one patient, each result must retain its own specimen identifier. The report can include an episode or case number for grouping related tests, but that broader identifier should not replace the unique laboratory number.

Specimen information should be specific enough to explain the scope of the result. “Respiratory specimen” may be insufficient when the laboratory tested sputum, induced sputum, bronchoalveolar lavage, or another material. For extrapulmonary samples, the anatomical source should be recorded. A report should also indicate whether the specimen was direct, cultured, or derived from an isolate.

Standardize methods, drugs, and interpretations

A drug susceptibility report should identify the test method and platform, because results are meaningful only in relation to the procedure used. Include the assay or system name, testing date, tested isolate or specimen, and relevant method version. For phenotypic testing, record the medium or system, critical concentration or other interpretive basis, and the laboratory’s approved interpretation rules.

Drug names must follow a controlled list. Avoid informal abbreviations that could be confused across facilities, and separate individual agents from drug classes. The report should state whether a result means susceptible, resistant, intermediate, borderline, invalid, contaminated, or not tested. If a method produces a category such as “detected resistance,” the exact assay terminology should be retained rather than replaced with a broader statement.

Interpretation rules can change as evidence, standards, or national policies develop. For that reason, the report template should include a document version or interpretation framework, with controlled approval and review dates. The GLI Quality Tool offers a practical quality-management structure for controlling documents, equipment, personnel responsibilities, assessment, and continual improvement.

Reporting element Basic report Expanded report Quality benefit
Test identification Assay or method name Method version, run date, and instrument Supports traceability
Resistance finding Drug and interpretation Drug, category, critical concentration, and result value Reduces ambiguity
Specimen link Accession number and specimen type Collection, receipt, processing, and isolate details Confirms result identity
Quality status Final, preliminary, or invalid Reason for delay, repeat, or referral Supports safe follow-up
Authorization Reviewer name or code Analyst, reviewer, approval date, and amendment history Demonstrates accountability

Present results in a clinically clear sequence

The main result section should be easy to scan. A common structure begins with organism identification, followed by molecular resistance markers, phenotypic susceptibility findings, and an overall interpretation. The laboratory should decide whether drugs are listed alphabetically, by treatment group, or in a nationally approved order. Once selected, the order should remain consistent.

A report may use a result grid with columns for drug, method, finding, interpretation, and comment. For example, a molecular test could show a detected resistance marker, while a phenotypic test could show resistance at a defined critical concentration. These are related findings, but they should not be merged in a way that hides the evidence source.

Use plain, controlled language for exceptional outcomes. “No result” is too vague if the actual reason was contamination, insufficient growth, inhibition, invalid internal control, mixed culture, or a test not performed. The report should identify the reason and state whether repeat testing or referral is recommended.

Add comments that support safe action

Interpretive comments should explain the significance of a result without turning the laboratory report into a treatment prescription. A detected resistance-associated mutation may require confirmation, correlation with phenotypic testing, or referral according to national procedures. A resistant result should be accompanied by a statement that treatment decisions must follow current clinical and program guidance.

Comments are particularly important for discordant findings. If molecular testing suggests resistance but phenotypic testing is susceptible, the report should identify the discrepancy, state which result is being released as authoritative, and describe the escalation pathway. If the result is limited because only a small number of drugs were tested, that limitation must be visible.

Critical results require a defined communication process. The report can document the date and time the result was communicated, the recipient, and the staff member responsible. This communication record may be held in the laboratory information system rather than printed on the patient copy, but the report should still indicate when urgent notification has occurred where policy requires it.

Control release, amendments, and data exchange

A standard format is effective only when the release process is standardized too. The laboratory should define who performs the technical review, who authorizes the final report, and how results are transmitted to clinicians, referral sites, and surveillance systems. Electronic reports should use fixed data fields wherever possible instead of relying on free text.

Amended reports need strong version control. Each amendment should retain the original accession number, identify what changed, state why it changed, and show the date and authorizing person. The revised document should be clearly marked so recipients do not continue using a superseded interpretation.

Printed reports require the same safeguards as electronic records. Include page numbering, report status, laboratory contact details, and a statement indicating whether the document is final. If a report is transmitted by fax, email, or a portal, the laboratory should verify recipient details and protect patient confidentiality.

Validate the format before routine use

The template should be tested with real or simulated examples covering common and difficult scenarios. Validation cases can include a fully susceptible isolate, multidrug resistance, an invalid molecular assay, contamination, mixed growth, a pending result, discordant molecular and phenotypic findings, and an amended report. Reviewers should confirm that each case produces an understandable and complete document.

Staff training should address both data entry and interpretation of report statuses. Analysts need to know which fields are mandatory, while reviewers need a method for checking patient identity, specimen linkage, drug terminology, critical concentrations, and comments. Competency assessment can use blinded examples and periodic review of released reports.

Once implemented, the laboratory should monitor indicators such as reports returned for correction, missing mandatory fields, delayed authorization, amended results, and complaints from users. Feedback from clinicians and program staff can reveal whether the report is too dense, omits essential information, or uses terms that are interpreted differently across sites.

Practical design priorities

A dependable TB susceptibility report creates a common language between the laboratory, clinical services, and tuberculosis control program. It makes uncertainty visible, preserves the evidence behind each result, and supports traceability from specimen to authorized interpretation.

Begin by mapping the current reporting workflow, removing ambiguous fields, and testing a draft format with staff and report users. Approve the template through the laboratory quality system, train the team, and monitor its performance until every released result is clear, complete, and fit for clinical and public health use.