Designing a TB laboratory incident report form with severity grading

Tuberculosis laboratories across Australia operate within a tightly regulated quality framework, where even small errors can compromise patient safety and public health outcomes. Whether your facility is a high-throughput reference centre in Sydney, a regional service in Townsville, or a mobile screening unit supporting remote communities in the Northern Territory, capturing what went wrong, when, and why is a cornerstone of quality management. A well-designed incident report form helps laboratories meet the expectations of NATA accreditation, NPAAC standards, and the international requirements of ISO 15189, while providing actionable data for continual improvement.

The GLI Quality Tool organises laboratory quality around twelve Quality Systems Essentials and a four-phase roadmap, placing incident management firmly within the assessment and continual improvement phases. Building an incident report form that includes a clear severity classification system transforms scattered complaints and near-misses into a structured dataset that laboratories can analyse over time. The guidance below walks through the essential components, grading logic, practical design choices, integration with broader quality systems, and strategies for rolling the form out across diverse Australian settings.

Defining the core elements of the report

A useful incident report form starts with the basics: who, what, when, where, and how. In Australian TB laboratories, the form should capture a unique incident identifier, the date and time of detection rather than only the date of occurrence, and the specific workstation or testing platform implicated, such as a GeneXpert system, MGIT culture workflow, or line-probe assay station. Patient identifiers must be carefully balanced with privacy obligations under the Privacy Act 1988, typically using a laboratory accession number rather than full names or dates of birth.

The form needs a clear free-text section for describing the sequence of events. Encourage staff to write chronologically, focusing on systems rather than individual blame. Include prompts for the immediate corrective actions taken, whether samples were retained for investigation, and whether the incident had any potential impact on patient results already released. For biosafety-related events common in mycobacteriology, such as aerosol-generating spills or BSC failures, the form should specifically ask about containment, decontamination, and personnel exposure, since TB laboratories handle Risk Group 3 organisms that demand rigorous post-event documentation.

Building a severity classification scale

Severity grading is what turns an incident log into a quality management tool. A widely used approach is a four-level scale aligned with patient impact and operational consequence. Level 1 (minor) covers near-misses and deviations caught before release, such as a mislabelled specimen detected at aliquoting. Level 2 (moderate) covers events that reached the patient or required repeat testing without clinical harm. Level 3 (major) applies to incorrect results issued that may have influenced treatment decisions, while Level 4 (critical) covers events with confirmed or probable serious harm, biosafety exposures, or breaches involving multiple patients.

For TB laboratories specifically, severity should consider the consequence of a false negative or false positive result, the risk of laboratory-acquired infection, and whether drug susceptibility data were affected. A false rifampicin-resistant result on a GeneXpert test, for example, carries far greater clinical weight than a transcription error in a demographic field. Laboratories can calibrate their scale by reviewing historical incidents and testing the scheme against a sample set, an approach that complements precision monitoring over time using statistical process control charts to identify when a run of Level 2 events suggests an underlying drift.

Designing the form for real-world workflows

Paper forms remain common in regional and remote Australian laboratories where connectivity can be patchy, but digital forms offer searchable databases and automated trend analysis. Hybrid approaches work well: a paper intake form scanned into a laboratory information system, or an offline-capable tablet application for sites with intermittent internet. Whatever the medium, keep the form to a single page where possible, with logical grouping of fields so staff can complete it in under fifteen minutes, which improves reporting rates on busy shifts.

Layout matters for completeness. Place administrative fields (incident ID, date, reporter) at the top, followed by event description and immediate actions, then severity assessment and root cause considerations. Use drop-down menus for incident category (pre-analytical, analytical, post-analytical, biosafety, equipment, documentation), and provide clear definitions to reduce variation between reporters. In multicultural workplaces such as those found across western Sydney or Melbourne's western suburbs, where laboratory teams often include staff from diverse linguistic backgrounds, plain English wording with a glossary appendix improves consistency and reduces misclassification.

Australian laboratories expanding their test menu should also align their incident form with any new workflow changes. A practical capacity assessment guide helps identify the staffing, training, and equipment gaps that often surface as incidents once a new assay is introduced, allowing the form to be adapted before problems emerge rather than after.

Connecting incidents to the wider quality system

An incident report form is only as valuable as the response it triggers. The completed form should feed into the laboratory's quality meeting agenda, where incidents are reviewed alongside internal audit findings, customer complaints, and proficiency testing outcomes. This is the territory of Quality Systems Essential 11 (Internal Audit) and QSE 12 (Continual Improvement), and it is where Australian laboratories pursuing ISO 15189 accreditation will be expected to demonstrate a closed feedback loop with documented evidence.

Trend analysis should look beyond raw counts. Stratify incidents by test, by shift, by operator experience, and by severity level to identify patterns that would otherwise stay hidden. A spike in Level 2 incidents on a particular instrument, for example, may indicate a calibration drift that weekly maintenance cannot catch. Many Australian laboratories use the Plan-Do-Check-Act cycle to formalise this review, documenting corrective actions, preventive actions, and effectiveness checks in the same record. Linking incident data to the laboratory's quality indicators also satisfies NPAAC requirements for measurable quality monitoring and supports annual management review discussions.

Rolling out the form across the laboratory

Introducing a new incident report form is a change management exercise as much as a documentation exercise. Start with a pilot in one section of the laboratory, such as the mycobacterial culture bench, gather feedback, and refine the wording before broader rollout. Training sessions should include worked examples drawn from real or simulated TB scenarios, showing staff how to classify severity and avoid common pitfalls such as conflating the incident date with the discovery date.

Reinforce a no-blame culture that focuses on systems rather than individuals. Australian workplace culture tends to value open feedback channels, and laboratories that pair incident reporting with peer learning, such as short lunchtime case discussions, see higher reporting rates. Schedule a formal review of the form at six months and annually thereafter, checking that severity definitions still match the laboratory's risk profile and that the form continues to align with evolving GLI Quality Tool checklists and Australian pathology standards.

The four-phase roadmap of the GLI Quality Tool offers a practical framework for putting these ideas into action, from initial planning through to sustained continual improvement. Laboratories ready to develop or update their incident reporting toolkit can download the phase-specific checklists and user instructions available on the GLI Quality Tool website, adapt the templates to local context, and share feedback with peers through professional networks such as the Australian Society for Microbiology. Building a robust severity-graded incident form today lays the groundwork for safer TB diagnosis, stronger quality culture, and better outcomes for the patients and communities your laboratory serves.