GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

A TB laboratory incident summary log for trend analysis

A TB laboratory incident report summary log is a structured index of laboratory events. It brings near misses, errors, and other quality concerns into one record so teams can see whether isolated mishaps are developing into a pattern. Instead of relying on memory at monthly meetings, staff can use comparable fields to identify repeat problems, track corrective actions, and judge whether safety controls are working.

Testing in Australia spans public hospital pathology services, private pathology providers, and central reference facilities. Metropolitan laboratories in Sydney, Melbourne, Brisbane, and Perth may process many specimens, while regional services often depend on transport to a larger laboratory. These differences make consistent event codes and denominators essential: a high event count at a busy site may reflect workload, while a low count elsewhere may reflect under-reporting.

The GLI Quality Tool supports this work through a four-phase roadmap built around twelve Quality Systems Essentials. A log can serve as evidence of documentation, assessment, and continual improvement while also supporting laboratory safety, personnel, and equipment controls. It should remain a summary index, not a replacement for detailed incident reports, investigation notes, or the laboratory information system.

Set the purpose and reporting boundary

The GLI Quality Tool is useful for placing the log within the wider quality management system. Phase checklists and practical materials can show where an event record belongs, who should own it, and how findings should feed into corrective action. A short purpose statement should define the log as a source for trend analysis of near misses and errors rather than a performance score for individual employees.

Set clear boundaries before data entry. A near miss is a potential deviation or failure that was detected before causing harm; an error is a failure that reached a patient, result, specimen, or internal process. Some organisations use additional categories such as adverse events, breaches, or observations. Retain those local categories but map them to a stable set for aggregation. Each summary entry should point to the full incident report, while names and clinical details remain in the protected source record.

Capture fields that support comparison

Every entry needs enough context to make two events comparable. Useful fields include report identifier, event date and time, laboratory site, work area, shift, test or assay, specimen type, detection stage, event category, severity, actual and potential impact, immediate action, root-cause summary, linked report number, corrective-action owner, due date, status, and closure date. Use a coded specimen or patient identifier rather than copying names into the log.

Add controlled reason codes for causes and contributing conditions, such as specimen labelling, equipment malfunction, method deviation, result transcription, interpretation, communication, staffing, environment, or reagent supply. Free text remains valuable for context, but it should supplement rather than replace codes. Include fields for the number of tests affected, whether repeat testing was required, whether results were recalled or amended, and whether external notification was required. These details turn a list of complaints or mishaps into actionable laboratory quality data.

Record events through a consistent workflow

Capture events close to the time of discovery. The person who identifies the near miss or error opens the full report, records immediate containment, and creates or requests a summary entry. For example, a wrong specimen label caught before analysis should be coded as a near miss, with the control that prevented an incorrect result recorded in the cause and action fields. Repeat errors should not disappear into a general complaint file.

Use the GLI user instructions to align local forms with the resource’s phase-specific checklists and downloadable materials. Review entries at the routine morning handover in Sydney or Melbourne operations, or at the beginning of a regional roster shift, without discussing personal blame in the meeting. Confirm that the coded record matches the detailed report and that urgent safety issues have been escalated outside the summary process.

Investigate significant events using a structured method appropriate to the risk, document the evidence, and assign corrective and preventive actions with named owners and realistic due dates. Record the date the action was verified as effective, not merely the date it was completed. Near misses deserve attention because they reveal control weaknesses before a patient is affected. Closure requires evidence, while withdrawal or rejection of a report should be transparent and auditable.

Turn entries into trends and signals

Trend analysis needs both event counts and exposure data. Calculate monthly or quarterly rates per 100 tests, 1,000 specimens, or another stable denominator, and retain the numerator, denominator, data source, and any exclusions. A run chart or control chart can show shifts, recurring peaks, and variation between tests or sites. Stratification by test type, stage, staff role, equipment, and failure cause can reveal where action will have the greatest effect.

Watch for patterns such as the same reagent lot producing documentation errors, late-night shifts showing more transcription problems, or one specimen collection site generating repeated mislabelling. A rise in near misses may initially indicate better reporting rather than worsening performance, so interpret changes with the log’s completeness and denominator. When a signal appears, check the underlying reports, confirm that codes are being applied consistently, and open a formal corrective-action review when thresholds show sustained or serious risk.

Recommendations for a reliable and usable log

The following practices keep the summary log credible, manageable, and connected to action across Australian TB laboratory settings.

Review the form after the pilot and retire fields that do not support a decision. Keep enough detail to support root-cause analysis, but avoid creating a second full incident-report system. Version control, audit trails, and retention schedules should be built into the electronic file or clearly governed for paper records. Leadership should receive trend findings and resource requests rather than a raw count of individual mistakes.

Make trend review part of routine laboratory work

In Australia, TB laboratory work sits within state and territory notification and control requirements, as well as workplace safety obligations. A mishap involving a specimen, result, or staff member must be managed as an internal laboratory incident even when it is unrelated to a notifiable disease event. Public health legislation differs by jurisdiction, so teams should confirm their local reporting duties with the relevant health department. Commonwealth privacy obligations, including the Privacy Act 1988 and Australian Privacy Principles, also shape how patient-linked information is stored and shared, although health-service exemptions and state requirements may alter the details.

Embed the log in the laboratory management system where possible, but retain a standard export for network reviews. The GLI Quality Tool can support documentation, assessment, and continual improvement without replacing the laboratory’s approved quality management system. Use monthly trend meetings, safety huddles, and quarterly management reviews to assign actions and check effectiveness. Choose one pilot laboratory, nominate the log owner, approve the event definitions today, and begin collecting a coded entry for every near miss and error.