A practical nonroutine event log for TB laboratories
TB results are only as reliable as the conditions in which specimens, reagents and instruments are managed. A sudden loss of mains power or an instrument failure can interrupt testing, affect temperature-sensitive materials and create uncertainty about which results remain valid. A nonroutine event log gives laboratory staff a consistent place to record what happened, what was protected and what must be corrected.
The record should complement, rather than duplicate, routine maintenance, calibration and quality control logs. It is for unplanned interruptions and significant deviations: generator or UPS failure, unstable voltage, unexpected instrument shutdowns, repeated error codes, or failures that threaten safe operation. Planned maintenance belongs in the maintenance system unless it reveals a weakness requiring escalation.
Australian laboratories work in metropolitan hospital pathology services, state reference laboratories, and small regional or remote facilities connected through public-funded care. A disruption in a solo rural laboratory has different backup arrangements from a breakdown in a busy Sydney or Melbourne hub. One form should work across sites without assuming a full-time quality manager is always available.
Define the purpose and scope
Define a nonroutine event before designing the form. Include events that interrupt testing, compromise specimen or reagent conditions, affect staff safety, delay reporting, or invalidate results. Assign each entry a unique identifier and record the event in the laboratory’s local time, including start, restoration and close-out times. A near miss should be logged when it exposed a real risk even though no result was affected.
| Event | Entry trigger | Immediate record | Follow-up evidence |
|---|---|---|---|
| Power interruption | Loss of mains power, generator or UPS failure, or unstable voltage | Start time, alarms, affected circuits and instruments, restoration time | Temperature checks, switch-off decisions, sample status, electrical response |
| Instrument breakdown | Crash, leak, unexplained error, failed calibration or repeated abort | Asset ID, error code, troubleshooting, quarantine status and downtime | Service record, affected-result review, repair decision, verification before return |
| Consequential near miss | Disruption that could have affected specimens, staff safety or reporting | Hazard, near-miss rationale | Escalation, preventive action and effectiveness evidence |
Keep the master log concise enough for use during a disruption, with mandatory fields for event type, location, instrument or circuit, impact, immediate action, owner and status. A short narrative can capture observations that software error codes do not. Link—not copy—associated maintenance records, laboratory incident reports and corrective-action files. Use electronic access controls and an audit trail where available; if work continues on paper, reconcile it promptly into the controlled record.
Record power interruptions with useful detail
Record the outage as a timeline, not a single statement that power failed. Note the source, whether the generator and UPS started, observed voltage symptoms, circuits and instruments affected, estimated versus confirmed duration, and who authorised each switching decision. A burnt smell, arcing or repeated breaker trip needs isolation under local electrical safety procedures; the event log should record the decision but not replace a qualified electrical assessment.
Next, document what happened to work in progress. Record actions taken for TB specimens and cultures, temperature-sensitive reagents, incubators, alarms, data transfer and critical notifications, using the relevant laboratory SOP rather than guessing at acceptable limits. State whether results were held, repeated, referred to another laboratory or released, and link the authorised decision. Where monitoring equipment fails during the outage, document the alternative method used and its limitations.
Remote realities belong in the plan. Aboriginal Community Controlled Health Organisations and remote services in Central Australia may face long travel distances, limited on-site engineering and power systems exposed to heat, storms or bushfire activity; northern Queensland facilities also face cyclone disruption. Busy hospitals may have generators, alternate feeders and uninterruptible supplies with different levels of protection. Staff may say “power’s gone out” or “the unit’s playing up”, but entries should preserve the actual observation and time. Laboratories can align the form with the GLI Quality Tool, whose phased roadmap, checklists and practical materials support varied resource settings.
Document instrument breakdowns and downtime
For a TB laboratory instrument, capture identity and context: asset number, manufacturer, model, serial number, location, software version, connected accessories and the last known service or calibration. Transcribe error messages exactly, record every authorised troubleshooting step, and state whether the instrument was stopped, tagged out or placed out of service. Staff should not dismantle equipment or bypass safety interlocks; the log records actions and responsible people, not speculative diagnoses.
Assess downstream impact in the same entry. Identify affected specimens, controls, runs and reports; quarantine results where validity is uncertain; and document checks, repeats, referrals and notifications. A broken analyser that interrupts a shared hospital workflow may need escalation beyond the bench, including the state reference laboratory or the authorised clinical team. Avoid patient identifiers in the operational log and use secure cross-references to the laboratory information system.
Record the service pathway as evidence, including a call-out request, vendor case number, engineer attendance, parts ordered and expected return-to-service time. Australian support may come from a hospital network, state health service, local biomedical engineering team or vendor service agreement. Established engineering hubs around Melbourne, Sydney and Brisbane can support major repairs, while regional and remote sites may wait longer for a technician, replacement module or shipped part; downtime and transport should therefore be explicit fields.
Link events to corrective action
An entry becomes a quality record when it drives a decision. Classify the event, assess risk to patients, staff and results, and route it into the existing corrective and preventive action process. Use root-cause analysis to test causes such as an inadequate maintenance interval, an overloaded circuit, an expired UPS battery, an undocumented workaround or a training gap. The goal is to change systems, not attribute blame.
The quality management guidance within the tool connects event review with the twelve Quality Systems Essentials, including safety, personnel competence, equipment, documentation, assessment and continual improvement. Link each significant event to the relevant checklist or control, then attach the risk assessment, action owner, due date and evidence of completion. This makes the nonroutine log usable during internal audits and management reviews without turning it into a second quality system.
Set escalation thresholds before an event occurs: for example, repeated outages, critical instrument downtime, suspected reportable safety events, loss of specimen integrity or breaches of turnaround commitments. Review closed entries at a regular quality meeting and sample reopened records for effectiveness. Track measures such as time to restore critical service, recurrence, overdue actions and results delayed by the event, then use the findings to prioritise preventive maintenance and capital replacement.
Make the log workable across Australian services
Design for the workforce you have. A shared electronic form can support several sites but remain usable during network outages; a numbered paper book with controlled synchronisation can be the fallback. Use plain English labels, fixed categories, mandatory key fields and free text for context. In regional teams, assign ownership because one person may wear several hats; larger networks should route entries to the laboratory manager and central quality coordinator.
Govern access, confidentiality and retention under the laboratory’s approved policies. The log should contain operational and quality information rather than names, addresses or clinical narratives, while still allowing secure traceability to affected work. Backups, version control and sign-off prevent silent edits. Where several systems are used, nominate the master record and specify which fields are copied elsewhere, reducing duplicate entry and conflicting status.
- Appoint an event owner and a backup owner for each shift, with authority to request engineering, laboratory or clinical escalation.
- Pilot one page-based form at a representative site, including a paper fallback and one simulated instrument failure.
- Use a short monthly review to confirm every open entry has an owner, due date, risk decision and next action.
- Publish a simple summary to participating staff so recurring faults lead to funded fixes rather than repeated workarounds.
Turn entries into dependable laboratory action
A dependable log is neither a diary nor storage for unresolved work. Each entry should progress from open to actioned, monitored, verified and closed, with later events linking to the original cause. Attach evidence that a repair was tested, a workaround approved, training completed or a preventive change implemented. If an action fails, reopen or link a new event rather than overwrite the earlier account.
Test the process through a tabletop exercise involving night-shift staff, biomedical engineering, safety, quality and a senior clinician or laboratory director. Exercise a mains failure during incubation, a critical analyser failure and an extended network outage. Record how long staff need to find the procedure, contact support and return results to service. Track exercise gaps as actions in the same system used for live events.
Begin the pilot now: choose one laboratory or network, appoint the responsible officer and use the form for the next outage or breakdown. After 30 days, review completeness and response time with the participating team, then expand only when every serious event has an owner, a recorded decision and traceable closure.