Building a TB lab turnaround time log for critical diagnostic tests
In a country where the tuberculosis caseload is relatively contained but geographically dispersed, laboratories from Sydney to Darwin shoulder real responsibility for keeping diagnostic intervals short. A well-designed turnaround time tracking log translates raw sample movement into measurable evidence that a quality management system is functioning. For Australian TB laboratories, the log becomes a living record that supports accreditation under NPAAC standards, satisfies the expectations of state reference facilities such as the Mycobacterium Reference Laboratory in Brisbane, and helps clinicians decide whether a patient in the Torres Strait or a remote WA community receives timely treatment.
The shift toward digital LIS platforms has made manual tracking feel old-fashioned, yet most public pathology networks still rely on spreadsheets or hybrid paper-electronic systems for batched culture work. A purpose-built log brings rigour to a process that often drifts when workloads spike. Used alongside the GLI Quality Tool roadmap, it can anchor broader quality goals within everyday bench practice.
Why turnaround time matters in Australian TB laboratories
Australia reports around 1,400 to 1,600 active TB notifications each year, a modest but persistent caseload concentrated in Victoria, NSW, and Queensland. Each notification triggers a diagnostic cascade, and clinicians measure the system's responsiveness against practical benchmarks: when a GeneXpert result should land on a clinician's desk, how quickly a smear should be reported, and how reliably a positive culture reaches an Australian Mycobacterium Reference Laboratory Network member for DST. A tracking log converts these expectations into dated, traceable evidence.
Pathologists at facilities such as SA Pathology's Frome Road campus or at Westmead Hospital often describe TAT performance in shorthand: lab-to-clinician intervals that flag a result ready for action, and lab-to-LIMS intervals that capture pre-analytical bottlenecks. Both matter. The former is what a treating physician experiences; the latter is what your bench team controls. NTAC-endorsed protocols reinforce the case by requiring positive M. tuberculosis cultures to be referred to a reference laboratory within defined windows, and a well-kept log becomes proof during an RCPA or NPAAC audit that those windows are met.
Defining critical tests and measurable targets
A tracking log only works when the term "critical" is defined explicitly. In most Australian TB laboratories, critical tests fall into three families: rapid molecular assays such as Xpert MTB/RIF Ultra or Xpert MTB/XDR, smear microscopy performed at the receiving laboratory, and mycobacterial culture with phenotypic DST performed at a reference site. Each carries a different clinical urgency and a different internal workflow, so each demands its own TAT target.
Bench managers commonly use a 24-hour target for smear and Xpert results on sputum received before 10 am, a 21-day target for liquid culture flagging, and a 42-day target for phenotypic first-line DST. These figures align loosely with WHO recommendations and are tightened or relaxed depending on courier schedules to places such as Broome or Cairns. Setting the target is one step, but defining the clock start and clock stop is where many logs fail. The clock should start at specimen accessioning, not at sample collection, and stop at the moment the verified result is released to the treating clinician or the state register, preventing the silent inflation that occurs when laboratories quietly shift their start point to "same-day-received" specimens only.
Designing the tracking log: fields, format, and workflow
A practical log captures only what the team will actually review. Over-designed spreadsheets quickly become graveyard files in a shared folder. The fields worth committing to include unique specimen ID, accession date and time, specimen type, referring facility, test requested, clock start, clock stop, result, analyst, and a free-text column for delays. Some Australian laboratories also record the courier batch number for inter-site referrals, invaluable when investigating late arrivals from regional centres.
Format matters as much as content. A simple line-list in Excel or Google Sheets is enough for sites processing fewer than twenty TB samples a week, while high-throughput sites often embed a TAT module directly inside the LIS. Either way, the log should be locked against casual editing once the row is closed, with reviewer sign-off captured in a separate column. This small discipline mimics the document-control expectations in NPAAC ISO 15189 assessments and keeps the file defensible.
Bench leaders across the country often start with a snapshot of typical targets by test category, drawn from common practice in Australian reference laboratories:
| Test category | Clock start | Clock stop | Typical target | Escalation threshold |
|---|---|---|---|---|
| Xpert MTB/RIF or Ultra | Specimen accession | Result released to clinician | ≤ 24 hours | > 48 hours |
| Smear microscopy (fluorochrome) | Specimen accession | Result released to clinician | ≤ 24 hours | > 48 hours |
| Liquid culture (MGIT) flagging | Specimen accession | Instrument flag | ≤ 21 days | > 28 days |
| Phenotypic first-line DST | MGIT-positive culture ready | DST result released | ≤ 42 days from primary specimen | > 56 days |
| Referral to reference laboratory | Culture confirmed | Shipment logbook entry | ≤ 5 working days | > 7 working days |
Threshold values are not mandated nationally; laboratories should calibrate them to local courier realities, workforce rosters, and the patient population served.
Implementing the log step by step in your laboratory
Rollout begins with piloting, not proclamation. Choose one bench, one shift, and one test category — smear microscopy at the morning cutoff is a forgiving starting point — and trial the log for a single month. This window reveals which fields feel redundant, which dropdown menus are ignored, and where reviewers forget to sign. Feedback gathered here prevents the rollout collapse that follows a big-bang deployment across multiple benches at once.
Training should be short and specific. Bench scientists at labs such as Royal Hobart or PathWest in Nedlands engage with new paperwork only when it cuts a known frustration — usually duplicate data entry, lost paper requisitions, or chasing an emailed result. Position the log as a fix for those pains. A five-minute walk-through, recorded for new starters, outperforms a one-hour classroom session every time.
Link the log to broader quality objectives through the framework described in the guide on aligning TB lab quality goals with national TB program targets. When staff can see a TAT audit feeding into a stated quality objective, the log stops being extra work and becomes part of the documented system. Quarterly reviews can then examine trends without scrambling for evidence.
Finally, store templates and supporting forms in a controlled location so that versions do not multiply across network drives. The GLI resource downloads section provides version-controlled templates, including adaptable logbook spreadsheets and reviewer sign-off sheets, that smaller laboratories in regional Queensland or the NT can adopt without designing from scratch.
Monitoring performance and driving continual improvement
A log without review is merely a record. Establish a recurring monthly review of TAT performance against targets, attended by the senior scientist, a bench representative, and a clinician if possible. The review should distinguish between systemic delays (courier gaps, instrument downtime, staff leave) and one-off outliers (mis-labelled specimen, contaminated culture). Systemic delays feed straight into the corrective action register; outliers trigger individual case review but rarely need systemic change.
Trend analysis over six to twelve months exposes patterns hidden in single-month reviews. Many Australian laboratories notice a recurring TAT spike in late December, when courier schedules thin out and annual leave peaks. Anticipating those spikes, with a pre-planned surge staffing arrangement or a planned extension of internal testing, transforms the log from an audit tool into a planning tool. Continual improvement also means retiring data fields that no longer earn their keep — if "analyst" is never used to investigate delays, drop it; if "free-text delay reason" produces consistent themes that could be coded, code them.
Adopt the approach your bench can sustain today, refine it as workflows change, and let each iteration of the log draw your team closer to the diagnostic intervals Australian TB patients deserve. Start by drafting a log tailored to your highest-volume critical test, pilot it for one reporting cycle, and review what the data actually tells you about where time is really being lost.