Managing TB Laboratory Document Changes With Revision History
A reliable document control process helps tuberculosis laboratories keep methods, forms, worksheets and safety instructions accurate when work changes. In a TB service, a small wording error can affect specimen acceptance, biosafety, culture interpretation, reporting or communication with a referring clinician. A controlled revision history creates evidence that each change was considered, approved and introduced properly.
Developing a TB lab document change control procedure with revision history does not require expensive software. A well-designed register, consistent file naming and clear approval rules can work in a metropolitan laboratory, a regional hospital or a service supporting remote communities. The essential point is to make the current version easy to identify and older versions impossible to use by accident.
The GLI Quality Tool provides a practical framework for this work through its Quality Systems Essentials and phased improvement approach. Its guidance can help a laboratory connect document control with personnel competence, equipment management, assessment, safety and continual improvement rather than treating it as an isolated administrative task.
Set The Scope For Controlled Documents
Begin by defining which records and documents require formal change control. The scope commonly includes standard operating procedures, test methods, specimen collection instructions, result interpretation guides, forms, equipment work instructions, safety procedures, referral instructions and quality control plans. Documents supplied by manufacturers should also be identified, even if the laboratory cannot edit them.
Distinguish controlled documents from temporary working notes and completed records. A completed worksheet is evidence of an activity and must be retained according to the laboratory’s retention rules; it should not be altered as though it were a live procedure. A controlled procedure, by contrast, must show its owner, approval status, effective date and current revision.
Australian laboratories should align this system with the evidence expected for NATA accreditation to ISO 15189, as well as applicable state or territory requirements. A public laboratory in Sydney may use a central electronic document system, while a smaller service in regional Queensland or the Northern Territory may rely on a secure shared drive and printed controlled copies. The control principles remain the same: authorised content, traceability and access to the current version.
Assign Ownership And Approval
Every controlled document needs a named owner. This may be the senior scientist, section head, quality manager or technical supervisor, depending on the document’s subject. Ownership means responsibility for keeping the content current, monitoring related risks and initiating review; it does not mean that one person must write every amendment.
Set an approval pathway based on risk. A minor spelling correction may be checked by the document owner and quality officer, while a change to a molecular assay, decontamination step or reporting threshold should be reviewed by technical experts, the laboratory director and, where relevant, the biosafety adviser. Changes affecting clinical interpretation may also require communication with infectious diseases physicians or public health authorities.
The procedure should state who can request a change, what information the request must contain and how urgency is managed. A request might arise from a nonconformance, audit finding, incident, supplier update, changed instrument, revised national guidance or a staff suggestion. In Australia, a change involving hazardous chemicals or infectious material should be checked against the laboratory’s work health and safety obligations, including the relevant state or territory WHS legislation.
Design A Useful Revision History
A revision history should be visible within the document, not hidden in a separate folder. Place it near the front or at the end, using a consistent format. Each entry should identify the revision number, date, description of change, reason, author, reviewer, approver and effective date. If training or document distribution is required, include those details in the same record or link them clearly.
Use a numbering convention that staff can understand. Sequential major revisions, such as 1.0, 2.0 and 3.0, can identify substantive changes, while minor updates such as 2.1 may cover formatting or clarification. Avoid changing the revision number merely because a file was opened. The number should represent an approved version that has entered controlled use.
| Document situation | Record in revision history | Required follow-up |
|---|---|---|
| New TB testing procedure | Initial issue, author, approval and effective date | Staff training and controlled distribution |
| Updated assay or instrument setting | Exact technical change and reason | Verification, validation or performance review |
| Typographical correction | Location and nature of correction | Reviewer check; retraining only if meaning changed |
| Safety or regulatory update | Source of requirement and risk addressed | Risk assessment and communication |
| Withdrawn procedure | Withdrawal date and replacement document | Remove obsolete copies and archive securely |
Do not delete previous versions without a retention decision. Mark them as obsolete, move them to a restricted archive and prevent them from appearing in routine searches. Printed copies in a bench folder, specimen reception area or staff room should be listed and replaced. This is especially important in laboratories that use a mixture of electronic records and paper forms during power outages, network interruptions or outreach work.
Link Changes To Verification And Training
A document change is complete only when the laboratory has assessed its effect. Ask whether the amendment changes a test principle, specimen type, critical result, turnaround time, safety control, equipment setting, staff competency requirement or interface with another service. The answer determines whether simple review is enough or whether verification, validation, risk assessment or a competency check is required.
For example, changing a culture workflow may require updated environmental monitoring, revised stock records and a review of contamination trends. Replacing a reporting phrase may require consultation with the medical microbiologist and a check that the laboratory information system still displays the intended result. A revised sputum collection instruction may require new patient information, collection staff training and confirmation that courier packaging remains suitable.
Proficiency testing and external quality assessment should be considered when a change affects analytical performance. The proficiency testing guidance can support decisions about participation, result analysis and follow-up actions. Link the relevant assessment record to the document revision so an auditor can see how the laboratory confirmed that the new process worked.
Australian services often operate across long distances, with specimens travelling between Perth, Darwin, Brisbane and smaller regional centres. A change that appears local may affect collection timing, courier temperature control, referral forms and result communication. Where a laboratory supports Aboriginal and Torres Strait Islander health services or remote clinics, implementation should account for connectivity, local workflows, language needs and the practical availability of trained staff.
Make Implementation Visible And Sustainable
Once a revision is approved, record the release date and communicate the change to affected personnel. A short briefing at the daily handover, an email summary and an updated electronic link may be sufficient for a minor amendment. A new method or safety control needs documented training, supervised practice and competency assessment. Staff should know what changed, why it changed and where to find the current version.
Use a master document register to monitor review dates, owners, status and storage location. Set review intervals according to risk rather than choosing the same date for every document. A high-risk TB procedure may need annual review, while a stable administrative form may be reviewed less often. The register should also identify documents awaiting approval and those that have passed their scheduled review date.
Practical Controls For Daily Use
- Place the document title, unique identifier, version, page number and effective date in a consistent header or footer.
- Keep the editable master file in a restricted location, while staff receive a read-only approved copy.
- Record the reason for every substantive change, including the incident, audit finding, supplier notice or guidance that prompted it.
- Require staff to acknowledge critical updates and retain attendance or competency evidence.
- Audit work areas, shared drives and local downloads for obsolete copies at planned intervals.
Review the process through internal audits, incident investigations and staff feedback. A recurring finding that people use locally saved procedures may indicate poor access, confusing file names or excessive approval delays. Continual improvement should address the cause rather than simply reminding staff to comply.
A practical starting point is to select one high-use TB procedure, create its document register entry, reconstruct its current revision history and test the approval workflow. After the process works for that document, extend it to forms, equipment instructions and related quality records. This staged approach suits Australian laboratories with limited quality staff while building evidence of a functioning quality management system.
Adopt the procedure as a controlled quality document, assign its owner and begin with a small review of active TB methods. Replace obsolete copies, record the first improvement and use the resulting history as evidence that document changes are safe, traceable and understood across the laboratory.