Building a TB laboratory incident investigation form
A well-designed incident investigation form helps a tuberculosis laboratory move from a vague report of “something went wrong” to a clear, evidence-based understanding of what happened. It should capture the event, protect patient and staff information, document immediate controls, and guide a root cause analysis (RCA) that leads to practical corrective action.
For laboratories in Australia, the form must work across metropolitan reference services, hospital laboratories and smaller regional facilities. A specimen error in Sydney, a delayed referral from regional Queensland, or a cartridge stock issue affecting a remote service may have different operational causes, but each incident needs a consistent method for recording facts and learning from them.
Define the purpose and scope
Start by stating what the form is for. It should cover incidents, near misses, nonconforming work, safety events and quality complaints connected with TB testing. Examples include a mislabelled sputum specimen, an incorrect result transcription, contamination in a culture workflow, a failed temperature excursion response, an expired reagent being used, or a delay in notifying a clinically significant result.
The form should distinguish between an initial notification and a completed investigation. The person who notices the event may have only a few facts, while the investigation lead will later add interview notes, instrument records, training information and corrective action details. Keeping these stages separate prevents early assumptions from being presented as established facts.
Include a short instruction at the top: record what is known, preserve relevant evidence, avoid blame, and escalate urgent risks immediately. The form is a quality tool, not a disciplinary document. Personal information should be limited to what is necessary, with patient identifiers handled according to the laboratory’s privacy and information governance requirements.
A useful scope statement can refer to the laboratory’s quality management system, biosafety procedures, incident reporting policy and applicable accreditation obligations. Australian laboratories may need to align the form with NATA expectations, state or territory public health reporting arrangements, hospital governance requirements and local work health and safety processes.
Capture the event and its immediate risk
The first part of the form should establish a reliable timeline. Include fields for incident number, date and time discovered, date and time of occurrence if known, location, testing area, person reporting, supervisor notified and investigation owner. Add a classification field for incident, near miss, complaint, equipment failure, safety event or external event.
Record the affected process in plain language. Suitable categories include specimen collection, receipt and accessioning, transport, pre-analytical processing, nucleic acid amplification testing, microscopy, culture, identification, drug susceptibility testing, result authorisation, reporting, waste handling and referral testing. The form should allow more than one category when an event crosses workflow boundaries.
The immediate response section should answer four practical questions: what was stopped, what was quarantined, who was notified, and how was patient or staff risk controlled? Include prompts for repeat testing, result correction, clinician notification, specimen recollection, exposure management, instrument isolation and referral to a senior microbiologist or infection prevention team.
A risk-rating field can support consistent triage. Ask the investigator to assess actual impact and potential impact separately. A near miss involving a false-negative TB result may have caused no harm because it was detected during review, yet its potential clinical and public health consequences remain serious. Include severity, likelihood, detectability and required escalation, using the laboratory’s existing risk matrix rather than creating a competing scale.
Gather evidence before forming opinions
The investigation section should prompt staff to collect objective evidence. Useful sources include request forms, accession logs, instrument runs, quality control results, middleware and laboratory information system audit trails, temperature records, maintenance logs, batch and expiry information, competency records, staff rosters, transport documentation, photographs and relevant correspondence.
Add a field titled “established facts” and another titled “assumptions or information to verify”. This simple separation reduces hindsight bias. For example, “result released at 14:20” is a fact supported by an audit trail, while “the scientist skipped the verification step” is an assumption until the workflow and records confirm it.
Reagent and consumable traceability deserves a specific prompt. Record manufacturer, product name, lot number, expiry date, date opened, storage conditions and tests affected. If lot information is difficult to follow across platforms or assays, the GLI resource on reagent lot tracking can help laboratories design a more reliable approach.
Include space for confidential interview summaries, with the interviewee’s role and date recorded. Ask what normally happens, what happened on the day, what made the action reasonable at the time, and whether staff had the information, equipment, time and authority needed to work safely. These prompts focus on system conditions rather than treating individual memory as the sole explanation.
Use root cause prompts that examine the system
A strong RCA section should begin with a concise problem statement. It should describe the undesirable outcome, process, location, date and impact without assigning blame. “A positive molecular TB result was authorised without the required second review” is more useful than “staff failed to check the result.”
Use a five-whys prompt where appropriate, but do not require exactly five questions. Continue asking why until the answer reaches a controllable process condition. For example, a missed second review may relate to an unclear roster, an unavailable reviewer, an electronic workflow that allowed release, or a procedure that did not define escalation during after-hours testing.
Add prompts covering common contributory factors:
- Were the procedure and acceptance criteria current, accessible and understood?
- Was the staff member trained, supervised and assessed as competent for the task?
- Were staffing levels, workload, interruptions or shift handovers relevant?
- Did the instrument, software, barcode system or laboratory information system function as intended?
- Were specimens, reagents and controls suitable, correctly identified and stored?
- Did the physical environment, biosafety controls or workflow layout contribute?
- Were communication, referral, transport or clinical notification arrangements clear?
- Had previous incidents identified the same weakness?
- Were quality indicators or internal audits capable of detecting the problem earlier?
The form should ask investigators to classify causes as immediate, contributing and root causes. An immediate cause might be a result released before review. A contributing cause might be a queue of urgent specimens during a staff shortage. A root cause might be an electronic release rule that did not enforce review for a high-risk result. This layered analysis produces better actions than retraining alone.
Turn findings into corrective action
The action section should connect every confirmed cause to an owner, due date, completion evidence and effectiveness check. Actions may include revising a procedure, changing an accessioning step, adding a barcode control, improving stock rotation, modifying an instrument rule, introducing a handover checklist or changing the escalation pathway.
Avoid recording “retrain staff” as the only response unless the investigation demonstrates a knowledge or competency gap. Training cannot correct an unsafe interface, inadequate staffing model, ambiguous procedure or unreliable supply chain. When training is appropriate, specify the audience, content, delivery method and competency assessment.
Include a hierarchy of controls prompt. Prefer design changes, automation, physical separation, verification controls and standardised workflows before relying on reminders. For example, a mandatory electronic field for specimen source may prevent more errors than a poster asking staff to remember the field.
Effectiveness review should be scheduled after enough time has passed to observe the revised process. Ask what measure will demonstrate improvement, who will review it and when. Suitable measures include rejected specimen rates, amended reports, contamination rates, turnaround time, failed quality controls, stock discrepancies, repeat testing and completion of critical result notifications.
Repeated or significant events should feed into the laboratory’s broader improvement programme. The GLI guidance on lab improvement planning provides a useful way to connect incident findings with the Quality Systems Essentials, including documents and records, personnel, equipment, assessment and continual improvement.
Make the form practical for Australian laboratories
A digital form is often preferable where the laboratory has a secure quality management platform, but a controlled paper form may be more realistic for a small service, outreach setting or temporary referral arrangement. In either format, use mandatory fields for critical safety and escalation information while leaving enough free text for unusual events.
Design for the realities of Australian geography. A metropolitan laboratory in Melbourne may have direct access to specialist support, while a service receiving specimens from the Northern Territory or Far North Queensland may depend on scheduled transport, courier temperature controls and telephone escalation. Add prompts for referral laboratory details, transport delays, public holidays, weather disruption and communication across time zones where relevant.
Use Australian terminology and governance pathways. Fields may need to refer to NATA accreditation, state or territory TB programs, hospital medical officers, infection prevention and control teams, WorkSafe or equivalent authorities, and the Therapeutic Goods Administration when a product or device issue requires escalation. The exact pathway should be configured locally rather than assumed to be identical across jurisdictions.
Before launch, test the form with scientists, specimen reception staff, couriers, quality managers, biomedical engineers and medical officers. Run a short simulation using a realistic scenario, such as a delayed positive result from a regional collection centre or an unexpected reagent lot failure. Remove fields that duplicate existing records, clarify unfamiliar terminology and confirm that the completed form can be retrieved during an audit or review.
Store the final form under document control, with an owner, version number, approval date and review interval. Trend completed investigations at quality meetings, protecting confidential details while sharing system lessons. A form becomes valuable when staff can complete it quickly, managers act on its findings, and the laboratory verifies that corrective actions have made TB testing safer and more reliable.
Adopt the form as a controlled part of the quality management system, train each role on its responsibilities, and review the first several investigations for consistency. Regular use will reveal recurring weaknesses in specimens, equipment, documentation and communication—and provide the evidence needed to address them before they affect patient care or public health.