Building a stronger TB laboratory incident report
A well-designed incident report helps a tuberculosis laboratory move from a vague description of “what went wrong” to a defensible record of what happened, why it happened, and how recurrence will be prevented. The document should support patient safety, staff safety, reliable testing, and fair learning rather than assigning blame.
For Australian laboratories, the template must work across metropolitan services in Sydney, Melbourne, Brisbane, Perth and Adelaide, as well as regional and remote facilities where specimens may travel long distances. It should align with the laboratory’s quality management system, local work health and safety duties, privacy obligations, accreditation expectations, and the practical realities of staffing, procurement and courier schedules.
Set the purpose and scope
Begin the form with a short statement explaining when it must be used. Reportable events may include a specimen mix-up, delayed transport, contamination, incorrect result entry, exposure to infectious material, equipment failure, reagent problem, breach of procedure, or an incident that was detected before reaching a patient. Including near misses is important because they reveal weak controls without the added consequences of patient harm.
Record the incident number, date and time, location, service area, reporter, shift, and people notified. Use a neutral event title such as “Delayed culture processing after temperature excursion” rather than “Technician error.” Add fields for the specimen type, test requested, batch or lot number, instrument, relevant procedure, and whether a result was released.
The form should distinguish between an incident, a nonconformity, a complaint, and a critical event requiring immediate escalation. A laboratory may have separate notification pathways for an exposure, a privacy breach, a notifiable disease matter, or a serious workplace event. The report should point staff to those pathways without trying to replace them.
Capture facts before interpreting causes
The first narrative field should ask for a concise chronological account. Prompt the investigator to state what was expected, what actually occurred, how the discrepancy was detected, and what happened afterwards. Separate observed facts from assumptions. For example, “the sputum container arrived without a matching request form at 9:20 am” is stronger than “the ward failed to label the sample properly.”
Include a timeline with useful checkpoints: collection, dispatch, receipt, accessioning, preparation, testing, review, authorisation and notification. Add space for environmental conditions, instrument status, staff roster, workload, interruptions and unusual events. In a rural service, a specimen may spend hours with a contracted courier or at a transfer hub, so transport handovers and temperature records deserve explicit fields.
Attach or reference objective evidence, including worksheets, electronic audit trails, instrument logs, quality control results, photographs, maintenance records, training records, emails and courier documentation. Protect patient information by using the minimum necessary identifiers and storing the completed report in an approved system. A clear clear job descriptions approach can also help investigators decide whether an unclear responsibility contributed to the event.
Use prompts that test the whole system
A root cause section should guide the investigator through several layers rather than invite a single explanation. Ask whether the procedure was available, current, readable and suitable for the task. Check whether staff had the right skills, supervision, authorisation and workload to complete the work safely. A person may have followed a confusing procedure correctly and still produced an unreliable outcome.
Prompts should cover equipment, materials, environment, communication and management controls. Was an analyser overdue for maintenance? Was a reagent within expiry but affected by storage conditions? Were supplies substituted because the Australian market had a shortage? Did a software alert go unnoticed? Was the bench layout practical while wearing required personal protective equipment? These questions turn the investigation towards system design.
Technical causes need particular care in TB testing. If staining quality is questioned, review reagent preparation, lot verification, storage temperatures, controls, microscopy conditions and competency records; the guidance on staining reagent checks provides a useful quality control reference. For culture, molecular testing or susceptibility work, include prompts for contamination controls, run validity, result interpretation, referral testing and communication of urgent findings.
A five-whys sequence can be included, but it should not be used mechanically. Each answer should be supported by evidence, and the final cause should be something the laboratory can control or influence. “The staff member forgot” is rarely sufficient. Ask why the task depended on memory, why the checking step failed, and whether the system made the correct action easy.
Link findings to corrective action
Every confirmed cause should connect to a corrective or preventive action. The report should identify the action owner, due date, required resources, priority, completion evidence and effectiveness measure. Actions might include revising a procedure, adding a barcode check, changing a storage location, adjusting roster coverage, improving courier instructions, validating a new reagent lot, or providing supervised competency assessment.
Avoid weak actions such as “remind staff to be careful.” A stronger action changes the process or adds a reliable control. If an incorrect result was almost released because one person performed every step without an independent check, the response might define risk-based second-person review, electronic verification rules or a clearly documented authorisation threshold.
Classify the event by actual and potential impact. Consider patient management, staff exposure, specimen integrity, turnaround time, result accuracy, confidentiality, accreditation risk and service continuity. A near miss with high potential harm may deserve the same depth of review as an event that caused limited harm. The classification should be based on evidence rather than the seniority of the people involved.
Australian laboratories should also record whether external notification or consultation was required. Depending on the circumstances, this may involve a laboratory manager, infection prevention team, work health and safety officer, medical director, referring clinician, state or territory health authority, or an accreditation body. The template can include a decision field and date without giving staff legal advice inside the form.
Build review into the quality cycle
The final part of the report should confirm that actions were implemented and tested. Evidence may include an approved document revision, audit results, competency observations, repeat quality control data, a completed maintenance record, or a measured reduction in delays. Set a review date that matches the risk: a serious exposure or invalid result may require prompt reassessment, while a low-risk documentation issue may be reviewed during the next internal audit.
Use the report to identify recurring patterns. Several small incidents involving missing request details may point to a collection-site problem. Repeated temperature excursions may indicate unsuitable packaging, a weak courier handover or a refrigerator alarm that is not monitored after hours. Trend reviews should consider location, shift, specimen pathway, equipment, staff group and cause category.
The GLI Quality Tool’s four-phase roadmap and twelve Quality Systems Essentials provide a useful structure for embedding this process into routine quality management. Incident reporting connects particularly well with assessment, documentation, personnel, equipment, laboratory safety and continual improvement. A template is most effective when it is available with phase-specific checklists and instructions, rather than stored as an isolated form that staff rarely see.
Train staff using realistic scenarios and short debriefs. A morning huddle can discuss a de-identified near miss, while a quarterly quality meeting can review action completion and recurring causes. In a large Melbourne or Sydney service, dashboards may support trend analysis; in a small regional laboratory, a simple register and scheduled review may be more practical. Both approaches can produce reliable learning when responsibilities and follow-up are clear.
| Incident type | Immediate containment | Root cause prompts | Evidence of effective action |
|---|---|---|---|
| Specimen identification mismatch | Stop testing, quarantine the specimen, notify the authorised lead | Were identifiers checked at collection, receipt and accessioning? Was barcode scanning available? | Audit shows correct matching across sampled specimens |
| Delayed or unsuitable transport | Record condition, protect the specimen, assess recollection or referral | Did packaging, courier timing, transfer points or weather affect the pathway? | Fewer transport exceptions and documented temperature compliance |
| Invalid staining or reagent performance | Hold affected results, repeat controls, identify impacted runs | Were lot verification, storage, preparation and expiry checks adequate? | Acceptable control results across defined repeat runs |
| Instrument failure | Stop affected testing, preserve logs, activate backup or referral pathway | Was maintenance current? Were alarms visible and escalation instructions clear? | Maintenance completion and reduced repeat downtime |
| Exposure to infectious material | Provide first aid and urgent occupational health escalation | Was PPE suitable? Was the spill or aerosol procedure accessible and practised? | Competency observation and successful safety drill |
| Incorrect or delayed result communication | Correct the record, notify the responsible clinician, assess patient impact | Did review, authorisation, electronic transfer or escalation controls fail? | Timeliness and accuracy audit demonstrates sustained improvement |
A practical report should be short enough to complete promptly but detailed enough to support a defensible investigation. Keep the core form to essential fields, with optional attachments for complex events. Use plain English, define specialist terms, and include prompts that guide staff without predetermining the answer.
Downloadable materials, local examples and controlled template versions can help the laboratory standardise its approach. Make the current version easy to find, review it after major incidents, and retire outdated copies from shared drives and printed folders.
Adopt the template as part of everyday laboratory practice, brief every relevant team member, and schedule regular reviews of open actions and recurring causes. A consistent, evidence-based investigation process will help Australian TB laboratories protect patients, support staff and strengthen the quality system over time.