Designing A Confidential TB Laboratory Audit Trail Checklist
Electronic records can make tuberculosis laboratory work easier to trace, review and improve, but only when the audit trail is designed deliberately. A complete record should show what happened, when it happened, which account performed the action and whether the information was viewed, changed, authorised or deleted. It must support quality investigations without exposing patient information unnecessarily.
For Australian laboratories, confidentiality is connected to the Privacy Act 1988, the Australian Privacy Principles and relevant state or territory health-record requirements. A laboratory may also need to demonstrate control during NATA assessment, internal audits, public health reporting and investigations of delayed or incorrect results. The checklist should therefore link information governance with the Quality Systems Essentials for documents, records, assessment, equipment, personnel and continual improvement.
The GLI Quality Tool offers a practical four-phase pathway for laboratories working in different resource settings. Its approach is useful for TB services in major centres such as Sydney and Melbourne, as well as regional facilities that rely on shared pathology networks, scheduled courier runs and limited information technology support. A well-built electronic audit trail can provide consistent evidence across all of these environments.
Define The Audit Trail’s Purpose And Scope
Begin by stating why the audit trail exists. Its purpose may include protecting patient confidentiality, demonstrating specimen traceability, investigating amended results, supporting staff competency reviews and proving that critical laboratory actions were authorised. A checklist that simply says “enable audit logging” is too vague to guide implementation or an assessment.
Set the scope across the full TB testing pathway. Include specimen collection and receipt, accessioning, rejection, microscopy, molecular testing, culture, identification, drug susceptibility testing, result verification, reporting, referral testing, equipment interfaces and record retention. Include paper-to-electronic transfers where they occur, such as handwritten request forms scanned into a laboratory information system.
Define the systems and user groups covered by the checklist. These might include the laboratory information management system, instrument middleware, electronic medical record, secure email, document repositories and public health reporting portals. Record whether access is used by scientists, technicians, pathologists, couriers, administrators, infection prevention staff, IT support or external service providers.
Specify The Events And Data To Capture
Each audit record should answer five basic questions: who performed the action, what action occurred, when it occurred, which record was affected and what changed. The system should preserve the previous value and the new value for edits to identifiers, specimen status, test results, comments, authorisation fields and reporting destinations. Date and time should use a consistent format and time zone, particularly where a service operates across Australian states.
Capture significant viewing activity as well as editing activity. A confidential result may be copied, exported, printed, transmitted or viewed by an inappropriate user without any value being changed. The checklist should therefore ask whether the system records report downloads, bulk exports, print events, failed logins, password resets, privilege changes and access by technical support personnel.
Avoid collecting unnecessary clinical details in the audit log itself. The log should reference the patient or specimen through a controlled identifier rather than repeating diagnosis, address, telephone number or other sensitive information. Where a vendor uses a support dashboard, confirm that the dashboard does not expose identifiable TB information to staff who do not need it.
Build Confidentiality Controls Into User Access
An audit trail has limited value if accounts are shared. Require unique user IDs, strong authentication and role-based access that reflects the person’s duties. For example, a courier may need to confirm collection and delivery, while a bench scientist may need to enter test data but not alter a final report. Pathologists and authorised senior staff should have defined approval rights rather than broad administrator access.
Include joiner, mover and leaver controls. The checklist should ask who approves access, how quickly a departed worker’s account is disabled and how temporary access is removed after leave or a short-term placement. This matters in Australian laboratories that use rotating registrars, agency staff, university students and staff moving between metropolitan and regional sites.
Protect the audit records from alteration by ordinary users. Ideally, logs should be write-once, tamper-evident or stored separately from the operational database, with restricted administrative access. Encryption should apply during transmission and storage where appropriate. Backups need equivalent protection, and restoration tests should confirm that audit history remains complete after a system outage.
Connect Specimen Traceability With Result History
For TB work, the audit trail must follow the specimen from receipt to final report. Capture the accession number, collection and receipt times, receiving location, specimen type, condition, storage movement, testing pathway, referral destination and disposal or retention decision. Record identity checks and any discrepancy resolution, especially where labels, request forms or electronic orders do not match.
A clear rejection record is essential because unsuitable sputum can affect turnaround time and clinical decisions. The checklist should verify that the reason for rejection, person making the decision, notification, recollection request and final disposition are retained and cannot be silently overwritten. Laboratories can use this specimen rejection guidance to align rejection records with a broader quality management process.
Link each result to the instrument, assay version, operator, run identifier, quality control status and authoriser. If a result is transmitted automatically, record the interface status and any failure or manual intervention. This creates a defensible chain of evidence when a clinician asks why a result was delayed, when a run is invalidated or when public health staff need confirmation of a notification.
Control Amendments, Corrections And Protocol Changes
The system should distinguish an ordinary data correction from a clinical or technical amendment. A typographical correction may require a reason and second-person review, while a changed positive or resistance result may require documented investigation, senior authorisation and notification of affected recipients. Never allow a user to replace the original value without preserving the prior result and the reason for change.
The audit trail should also document changes to test protocols, reference ranges, reporting comments, critical result rules and instrument settings. Record the request, risk assessment, approval, implementation date, validation evidence, staff training and post-change review. This is especially important when an assay manufacturer updates software or a laboratory introduces a new molecular platform.
For a structured approach, laboratories can consult protocol change guidance when deciding which approvals and verification records should be connected to an electronic change history. The record should show whether testing continued under the old or new procedure during the transition and how affected reports were managed.
Retain, Review And Test The Records
Set retention periods according to Australian privacy obligations, health service policy, accreditation expectations, contractual requirements and the clinical or public health value of the record. Do not assume that deleting the patient result should delete the audit history. Define what happens when a record reaches the end of its retention period, including secure destruction, legal holds and documented approval.
Routine review should look for unusual access, repeated failed logins, after-hours activity, bulk downloads, use of dormant accounts and frequent result amendments. Establish who reviews alerts, how quickly they must be investigated and where findings are recorded. A small regional service may use a weekly manual review, while a large Sydney network may use automated security monitoring linked to its incident system.
Test the checklist through realistic scenarios. Ask an authorised user to correct a specimen identifier, an administrator to change a role, a pathologist to amend a result and IT support to investigate an interface failure. Confirm that each event is visible, time-stamped, attributable and protected from unauthorised editing. Include downtime and recovery tests, because an audit trail that fails during a network outage can leave a serious gap in traceability.
Practical Checklist Design Recommendations
Use plain language and assign an owner to every control. A checklist item should identify the evidence required, the person responsible, the review frequency and the action needed when the answer is “no”. This makes it useful for self-assessment, internal audits and staged improvement rather than a one-time compliance exercise.
Keep a controlled version of the checklist with approval history and review dates. Australian laboratories often work with mixed technology environments, including older analysers, cloud-based pathology platforms and locally maintained spreadsheets. Document compensating controls where a legacy system cannot produce a required event, such as a signed access register, a protected manual amendment log or a supervisor review of daily exceptions.
- Confirm that every user has an individual account and an appropriate role.
- Verify that additions, edits, approvals, exports, print events and deletions are logged.
- Preserve original values, reasons for changes and the identity of the approving person.
- Test audit-log security, backup, restoration and review procedures at planned intervals.
- Link corrective actions to staff training, risk assessment and continual improvement records.
A confidentiality-focused audit trail checklist should be treated as a living quality document. Review it after a privacy incident, system upgrade, new assay, interface change, accreditation finding or alteration to state or federal requirements. Keep the checklist proportionate to the laboratory’s risks while preserving the same core principles of accountability, traceability and minimum necessary access.
Adopt the checklist within the laboratory’s quality management system, map each item to existing procedures and assign a date for the first evidence review. Use the findings to close access gaps, strengthen result amendment controls and demonstrate that electronic TB records remain trustworthy from specimen receipt through reporting and retention.