Creating a TB laboratory validation report template for automated readers

Automated readers can improve consistency in tuberculosis testing, but their results still require documented evidence that the system performs as intended in a particular laboratory. A validation report turns that evidence into a traceable record covering the instrument, software, specimen types, operators, acceptance criteria and final authorisation.

For Australian laboratories, the report should fit within an existing quality management system rather than sit as an isolated technical document. NATA accreditation against ISO 15189, applicable NPAAC requirements, workplace health and safety obligations, and any TGA conditions relevant to the device may all influence the validation file.

The template should be practical for laboratories in Sydney, Melbourne, Brisbane and Perth, as well as services supporting regional and remote communities. A reader installed in a central reference laboratory may have stable connectivity and dedicated engineering support, while a smaller service may need clear procedures for downtime, manual review and delayed servicing.

A strong report also helps the laboratory distinguish manufacturer claims from local evidence. It should show whether the automated reader is suitable for the intended TB workflow, how errors are managed, and when revalidation is required after software, reagent, hardware or process changes.

Define the reader and its intended use

Begin with a document-control block containing the report title, instrument name, model, serial number, software version, location, laboratory section, report identifier, author, technical reviewer and approval date. Include the related procedure, installation record, risk assessment, training record and change-control reference. Version control is essential when the same reader model is used across multiple sites.

State the intended use in precise operational language. Identify whether the system reads culture tubes, lateral-flow devices, stained smears, susceptibility panels, molecular cartridges or another TB-related assay. Record the specimen or test material, result categories, reporting pathway, intended users and limitations. A reader validated for one assay must not be assumed to perform acceptably with another assay or specimen type.

Describe the clinical and service context. For example, a metropolitan laboratory may process high daily volumes and require automated result transfer into a laboratory information system, while a regional service may use batch testing and refer complex specimens to a state reference laboratory. These differences affect workload, staffing, turnaround expectations and the evidence needed.

Set scope, risks and acceptance criteria

The scope should explain what is being validated and what remains outside the exercise. Separate analytical performance from user workflow, connectivity, cybersecurity, environmental conditions and business continuity. Include the reader, associated consumables, software, barcode scanner, printer, middleware and laboratory information system where each component can affect the reported result.

Create a risk-based summary before testing begins. Consider false-positive and false-negative readings, unreadable specimens, barcode mismatches, incorrect result mapping, power failure, network interruption, instrument contamination and unauthorised access. In Australia, risk controls should align with the laboratory’s existing WHS system and local incident-reporting arrangements, including procedures for exposure to infectious material.

Acceptance criteria must be measurable and approved in advance. They may cover agreement with a comparator method, repeatability, reproducibility, invalid or error rates, carryover, reading time, barcode accuracy and successful transmission of results. Avoid vague wording such as “works reliably”; specify the minimum acceptable agreement, maximum error rate and required number of successful runs.

A useful template includes a decision rule for each criterion. The result should be recorded as pass, fail, conditional pass or not applicable, with a justification and corrective action reference. Conditional approval should identify restrictions, such as mandatory manual review of weak signals or use only by trained senior staff.

Plan samples, operators and test conditions

The validation plan should describe sample selection and explain why the panel represents routine work. Include positive and negative materials, weak or borderline results, invalid specimens, different specimen types and challenging examples likely to cause reader uncertainty. Where patient samples are used, document de-identification, storage, stability and approval under the laboratory’s governance process.

If positive TB material is limited, the laboratory may use characterised external quality assessment material, quality-control material or archived specimens, provided the material is suitable for the intended claim. Record source, assigned value, expiry, storage conditions and preparation. Do not present simulated material as equivalent to fresh clinical specimens without explaining its limitations.

Use multiple operators and, where practical, multiple days or runs. This helps assess reproducibility and reduces the risk that one experienced user makes the system appear more reliable than it will be in routine service. Include new and experienced staff if both groups will operate the reader. Document training completed before testing and any deviations from the planned protocol.

Environmental conditions should be recorded when relevant, including temperature, humidity, lighting, bench stability, power supply and network availability. This matters for laboratories in tropical Darwin, hot inland locations or facilities with generator-backed power. If the manufacturer specifies environmental limits, show that the limits were met or explain how an exception was assessed.

Capture raw evidence and performance calculations

The template should provide a results section that links every summary value to source data. Include run date, operator, sample or control identifier, expected result, reader result, comparator result, error code, repeat result and final interpretation. A separate spreadsheet or laboratory information system export may hold detailed data, but the report must identify its location and protect it from unauthorised alteration.

For qualitative readers, calculate positive agreement, negative agreement, overall agreement and invalid or indeterminate rates where appropriate. Add confidence intervals when the sample size supports them, and state the comparator method. For quantitative outputs, assess bias, precision, repeatability and reproducibility using a method suitable for the measurement range.

Explain discrepant results individually. A disagreement may arise from a reference-method limitation, sample degradation, operator interpretation, reader optics, software classification or transcription error. Record the investigation, repeat testing, expert review and final disposition. A simple total agreement percentage can conceal clinically important failures in weak-positive or low-level samples.

Include screenshots, instrument printouts, audit-trail extracts, error logs and connectivity test records when they support the conclusion. Each attachment should have a unique identifier and be cross-referenced in the report. This creates an auditable chain from the approved protocol to the final decision.

Verify workflow, data and user competence

Technical performance is only part of validation. Test the complete workflow from specimen receipt or assay preparation through result review, authorisation, transmission, storage and reporting. Confirm that positive, negative, invalid and amended results map correctly into the laboratory information system and that comments or flags are retained.

Check user access levels and audit trails. A routine operator may be able to start a run and review images, while only authorised staff should release or amend results. Verify date and time settings, password controls, backup arrangements and recovery after a network outage. Privacy and security controls should be consistent with the laboratory’s governance policies and relevant Australian requirements for health information.

Include a competency assessment for each staff group. Evidence can include supervised runs, identification of quality-control failures, correct response to unreadable results, safe handling of materials and accurate result entry. The GLI user instructions can help teams organise practical quality-management activities and use the site’s downloadable resources consistently.

Write the normal operating procedure only after the validation workflow has been settled. The procedure should cover start-up checks, quality control, maintenance, cleaning, result review, manual override, incident escalation and shutdown. It should also explain what happens when the reader is unavailable, especially for services that send urgent specimens from regional Queensland or remote Western Australia to a larger centre.

Record deviations, decisions and ongoing review

Every deviation from the approved plan belongs in the report, including missing samples, failed controls, software interruptions, environmental excursions and repeated runs. Describe the impact assessment rather than simply listing the event. A deviation with no effect on the intended claim may be accepted with rationale; a deviation affecting a critical result may require additional testing.

The final approval statement should identify the exact scope of use, effective date, restrictions and responsible approvers. Sign-off commonly involves the laboratory manager, technical authority and quality manager, with clinical input where interpretation affects patient care. If the device is not acceptable, document the reason, containment action and path to remediation.

Set review triggers before implementation. Revalidation or documented verification may be needed after a software upgrade, hardware replacement, new reagent lot, change in specimen type, altered algorithm, relocation, major maintenance or repeated quality-control failure. Review should also follow a significant complaint, proficiency-testing failure or unexplained shift in performance.

Australian laboratories should connect these records to their NATA surveillance and internal-audit programme. The GLI resource on TB laboratory gap analysis can support a structured review of gaps across equipment, documentation, assessment, personnel and continual improvement.

Use a template that supports accreditation

A well-designed report template should be easy to complete without encouraging copied text. Use prompts, checkboxes and controlled fields for mandatory information, while leaving enough space for technical reasoning. Include a change history so reviewers can see whether the template itself has been altered since the original validation.

Keep the report proportionate to the risk and complexity of the reader. A small instrument with a narrow intended use may need a concise evidence pack, while a networked automated platform used across several assays requires deeper software, cybersecurity, interoperability and performance documentation. The report should demonstrate control, not create paperwork with no decision-making value.

Report component	Evidence to include	Approval or review point
Device identity	Model, serial number, software, location and accessories	Confirm configuration matches the intended use
Scope	Assay, specimen type, result categories and exclusions	Technical authority approves the claim
Risk assessment	Failure modes, controls and escalation pathways	Quality manager checks risk treatment
Performance plan	Samples, operators, runs and acceptance criteria	Protocol approved before testing
Results	Raw data, calculations, errors and discrepancies	Independent technical review
Workflow verification	LIS transfer, audit trail, downtime and reporting	Laboratory manager confirms operational readiness
Training	Competency records and user restrictions	Supervisor authorises staff
Final decision	Approval, limitations, actions and review triggers	Named approvers sign and date

Treat the completed report as a controlled quality record. Store it with the validation protocol, raw data, maintenance documents, training evidence and relevant change controls. A clear template gives Australian TB laboratories a defensible way to show that an automated reader is fit for purpose, safely integrated and monitored throughout its working life.

Adapt the structure to the reader, assay and local service, then have the technical and quality authorities approve it before testing begins. Use the finished report as a living record that supports reliable results, consistent staff practice and readiness for accreditation review.