GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Developing a training module for TB laboratory data integrity

Reliable tuberculosis laboratory results depend on more than accurate instruments and validated methods. They also depend on whether specimens, test processes, results, and reports are recorded correctly and can be traced from collection to final use. A missing date, altered worksheet, duplicated patient identifier, or unapproved result can affect clinical decisions, surveillance, drug-resistance monitoring, and public health action.

A practical training module on TB laboratory data integrity and recordkeeping should turn quality principles into daily behaviors. Staff need to understand what counts as a trustworthy record, how to document work in paper and electronic systems, and what to do when an error occurs. The module should work in laboratories with sophisticated laboratory information systems as well as those relying on registers, worksheets, and controlled paper forms.

The GLI Quality Tool offers a useful framework for organizing this work. Its four-phase roadmap and twelve Quality Systems Essentials help connect data practices with personnel, equipment, documents, assessment, safety, and continual improvement. A module built around these elements can support both initial training and ongoing competency assessment.

Define the learning purpose

The module should begin with a clear statement of why data integrity matters in TB testing. Participants should connect accurate records with patient identification, specimen referral, test selection, result interpretation, treatment decisions, and national reporting. This context helps laboratory workers see recordkeeping as part of patient safety rather than as an administrative burden.

Learning objectives should be observable. By the end of the session, participants should be able to identify critical data, create complete and contemporaneous records, apply authorized corrections, protect confidential information, and recognize potential integrity incidents. They should also be able to explain the difference between a transcription error, an invalid result, a missing record, and suspected intentional manipulation.

The audience may include specimen reception staff, laboratory technicians, supervisors, data clerks, quality officers, and managers. Their responsibilities differ, so the module can combine common content with role-specific exercises. For example, a data clerk may practice reconciling registers with reports, while a supervisor may investigate discrepancies and approve corrective actions.

Build the content around the data life cycle

A strong module follows information from its source to its final use. Start with patient and specimen identifiers, collection details, transport conditions, and accessioning. Continue through preparation, testing, quality control, result review, reporting, referral, storage, retention, and disposal. At every step, identify who creates the record, who verifies it, where it is stored, and how changes are controlled.

The central principle can be summarized through ALCOA-plus expectations: records should be attributable, legible, contemporaneous, original, accurate, complete, consistent, enduring, and available. These terms need practical examples. A technician’s initials beside a recorded result establish attribution; entering a result immediately after testing supports contemporaneous documentation; preserving the original value while adding a dated correction protects traceability.

Paper and electronic records require different demonstrations. Paper forms should be completed in permanent ink, without blank spaces that could be misinterpreted, and corrected with a single line, the correct entry, initials, date, and reason when required by procedure. Electronic systems should address unique user accounts, role-based access, audit trails, password control, downtime procedures, and protection against unauthorized deletion or overwriting.

Connect records with the quality management system

Data integrity should not be taught as an isolated information technology topic. It belongs within document control, personnel management, equipment management, process assessment, and continual improvement. Controlled forms need current versions, defined owners, approval dates, and withdrawal of obsolete copies. Standard operating procedures should state what must be recorded, when, by whom, and how long records are retained.

Equipment and software also influence the reliability of records. Instrument clocks, barcode readers, printers, network connections, and backup systems can introduce errors or gaps. When a laboratory prioritizes infrastructure investments, risk-based replacement guidance can help connect equipment decisions with patient risk, service continuity, and data reliability.

Use scenarios that reflect the laboratory’s real workflow. Participants might compare a paper worksheet with the final register, investigate a mismatch between an instrument export and a reported result, or decide how to document testing during a network outage. These activities reveal weak points more effectively than a lecture alone.

Data integrity issue Immediate response Preventive control Evidence of competence
Wrong patient or specimen identifier Stop reporting, notify the supervisor, investigate linked records Two-identifier verification and barcode checks Correctly resolves a simulated mismatch
Missing test time or operator details Review source records and document the discrepancy Mandatory fields and end-of-shift review Completes a worksheet without omissions
Paper record altered without trace Preserve the original and initiate an incident review Controlled correction procedure and supervision Applies a compliant correction
Electronic result overwritten Check the audit trail and inform authorized reviewers Role-based access and change control Explains how the original value remains traceable
Register does not match the report Reconcile records before final submission Routine data verification and sign-off Identifies and documents the root cause

Teach error reporting without blame

Staff must know that reporting an error early is safer than hiding it. The module should distinguish honest mistakes, system weaknesses, negligence, and deliberate falsification, while emphasizing fair and consistent review. A blame-focused environment encourages workarounds and delayed disclosure; a learning-focused environment produces better investigations and corrective action.

Include a simple incident pathway. The worker should secure the record, notify the designated supervisor or quality officer, assess whether a result or patient is affected, document facts, and support correction or notification through approved procedures. The pathway should explain when to quarantine reports, repeat testing, contact a clinician, or escalate to a national program or accreditation body.

Root-cause analysis can be introduced at an appropriate level. Participants should look beyond “staff forgot” and examine workload, unclear forms, training gaps, specimen flow, interface design, equipment downtime, or conflicting procedures. Corrective and preventive actions should have an owner, due date, measure of effectiveness, and follow-up record.

Use practical learning and competency checks

A blended format usually works well. A short presentation can establish terminology, followed by demonstrations, small-group exercises, role play, and a supervised workplace task. The module might take two to four hours initially, with brief refresher sessions built into staff meetings or quality review activities.

Exercises should use anonymized or fictional records. A “spot the problem” worksheet can contain missing initials, overwritten entries, inconsistent dates, and unexplained abbreviations. Another exercise can ask participants to reconcile a specimen register, instrument printout, and final report. In an electronic setting, a controlled demonstration can show user access, audit trails, result review, and downtime entry.

Competency assessment should measure behavior rather than memory. A written quiz can test key definitions, but direct observation is more valuable. Assess whether the participant verifies identifiers, records information at the right time, corrects an error properly, protects passwords, and escalates a discrepancy. Supervisors should retain assessment records and schedule reassessment after a defined interval or whenever procedures change.

Useful indicators include the percentage of records completed correctly, the number of unresolved discrepancies, turnaround time for incident review, repeat errors by process, and completion of refresher training. Trends should be discussed during management review and internal audits. The GLI Quality Tool provides practical quality management resources that can help laboratories align these activities with a broader improvement program.

Provide tools that support daily practice

Training is more effective when participants leave with usable job aids. Prepare a one-page recordkeeping checklist, a correction example, an incident notification form, a data reconciliation worksheet, and a short guide to electronic access responsibilities. Place approved tools at workstations and include them in orientation packages for new personnel.

The module should also define local rules clearly. Specify the retention period for worksheets, registers, reports, maintenance records, and electronic backups. Identify who may authorize result changes, who reviews audit trails, how confidential records are stored, and what happens when electricity, connectivity, or laboratory software is unavailable.

Recommendations for the training package include:

Turn training into routine practice

A single workshop cannot protect data integrity indefinitely. Managers should integrate the module into induction, annual competency review, internal audit preparation, and quality improvement meetings. Supervisors can reinforce expectations through brief observations, record reviews, and feedback at the point of work.

The module should be version-controlled like any other quality document. Record its author, approval date, revision history, target audience, training materials, attendance, assessment results, and follow-up actions. When an incident reveals a weakness, revise the relevant exercise or job aid so that the training reflects current laboratory risks.

Begin by mapping the TB laboratory’s data flow, selecting two or three high-risk scenarios, and testing the draft module with a small group of staff. Use their performance and feedback to refine the content, then approve, deliver, assess, and monitor it through the laboratory quality management system. This approach turns recordkeeping from a passive requirement into a practical safeguard for every result.