GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Managing the Shift to Electronic TB Laboratory Records

Moving from paper registers to electronic records changes far more than where information is stored. It affects specimen reception, testing workflows, result authorization, reporting, stock control, quality indicators, and communication with clinicians and public health teams. A carefully managed transition can improve traceability and reduce transcription errors, while a rushed change can create gaps that are difficult to detect.

Tuberculosis laboratories often work with limited connectivity, shared computers, varied staff experience, and several reporting requirements. The right approach must therefore fit the laboratory’s actual operating environment. An electronic system should simplify reliable work rather than impose a complex process that staff cannot sustain.

The GLI Quality Tool offers a useful framework for this work through its phased roadmap and twelve Quality Systems Essentials. Records management connects directly with personnel, equipment, documents and records, information management, assessment, and continual improvement. Treating digitization as a quality project helps the laboratory preserve control during every stage.

Define the purpose and scope

Start by documenting why the laboratory is changing its record system. Common objectives include improving specimen traceability, shortening reporting time, reducing duplicate entry, supporting external quality assessment, and giving managers timely information about workload and turnaround time. Clear objectives make it easier to decide which records should be digitized first and how success will be measured.

Map the existing paper workflow before selecting software. Follow a specimen from collection and transport through accessioning, testing, verification, referral, reporting, and storage or disposal. Record every form, register, signature, correction, and handoff. This process often reveals that the laboratory has several unofficial versions of the same record or that essential information is being copied repeatedly.

Set a realistic scope for the first implementation. A laboratory may begin with specimen registration and result reporting, then add culture tracking, drug susceptibility testing, inventory, equipment maintenance, and quality indicators. A controlled expansion is safer than attempting to digitize every process at once.

Establish ownership and document control

Assign a project lead and define responsibilities for laboratory management, quality officers, bench staff, information technology personnel, and data users. Someone should own configuration decisions, while another person verifies that the system reflects approved procedures. Staff who perform daily testing must have a meaningful role in design because they understand practical workflow constraints.

Create controlled documents for electronic records just as you would for paper records. These should describe user access, data entry rules, result review, amendments, backups, downtime procedures, retention periods, and archival arrangements. Version control is essential: staff must know which forms, codes, and procedures are current.

Access permissions should follow job responsibilities. For example, reception staff may register specimens, analysts may enter technical results, and authorized supervisors may validate or release reports. Shared accounts weaken accountability and make investigations difficult. Use individual credentials wherever possible, with a process for promptly disabling accounts when staff change roles or leave.

The transition also needs a cutover policy. Decide whether paper and electronic systems will run in parallel, for how long, and which record is considered authoritative if the two disagree. Parallel entry may provide reassurance during early implementation, but it increases workload and creates opportunities for inconsistent data unless the period is tightly controlled.

Select and configure a practical system

An electronic laboratory information system should match the laboratory’s test menu, reporting needs, connectivity, staffing, and budget. Assess whether it supports unique specimen identifiers, barcode use, audit trails, role-based access, result verification, amended reports, data export, and routine backups. Confirm that the system can operate during interruptions and that technical support is available within a reasonable time.

Configure standardized fields and permitted values rather than relying on free-text entry. Use consistent codes for specimen types, test methods, instruments, results, contamination, referral status, and rejection reasons. Required fields can prevent incomplete records, but excessive mandatory fields may encourage inaccurate workarounds. Each field should have a clear purpose and an agreed definition.

Data migration requires special care. Decide which historical records must be entered, which can remain in secure archives, and how legacy identifiers will be connected to new identifiers. Clean existing data before importing it by removing duplicates, resolving inconsistent spellings, and checking dates and result formats. Keep a migration log that records what was transferred, by whom, and when.

When planning the laboratory information system, include interoperability and reporting needs from the beginning. The system may need to exchange information with national TB programs, referral laboratories, electronic medical records, or surveillance platforms. Test these exchanges with realistic records before relying on them for routine reporting.

Area Manual record system Electronic record system Control needed during transition
Specimen identification Handwritten labels and registers Unique identifiers, barcodes, and searchable entries Match identifiers at every handoff
Result entry Transcription between forms Direct entry with validation rules Review and authorize results
Corrections Cross-outs, initials, and dates Auditable amendments with reason codes Preserve the original value
Access Physical possession of records User accounts and permissions Assign role-based access
Availability Vulnerable to loss or damage Available across approved workstations Maintain backups and downtime forms
Reporting Manual aggregation Automated summaries and exports Validate indicators against source data

Protect integrity, confidentiality, and continuity

Electronic records must remain accurate, complete, legible, retrievable, and protected from unauthorized alteration. Configure audit trails so the system records who entered, changed, reviewed, or released information. A correction should never erase the original result without leaving a visible history and a documented reason.

Confidentiality controls are especially important for TB records, which may contain patient identifiers, clinical information, and drug resistance results. Position screens carefully, limit printed reports, secure portable devices, and establish rules for transmitting files. Use strong passwords, protect backup media, and review access logs when the system supports that function.

Plan for power failure, network interruption, equipment breakdown, malware, and software unavailability. A downtime form should capture the minimum information needed to continue safe testing, including specimen identity, collection details, test status, results, and staff initials. Once the system is restored, designate a trained person to reconcile downtime entries with electronic records and document the reconciliation.

Data quality checks should be built into daily work. Supervisors can review missing fields, improbable dates, duplicate identifiers, delayed results, unexplained status changes, and discrepancies between the electronic system and paper source documents. For laboratories managing culture workflows, practical guidance on culture contamination issues can support investigations when contamination trends appear in the data.

Train staff and manage the change

Training should be role-specific and based on real laboratory tasks. Registration staff need practice with accessioning and identifiers; analysts need result entry and correction procedures; supervisors need verification, reporting, and data review; administrators need user management and backups. Demonstrations should be followed by supervised practice using test records rather than live patient data.

Competency must be assessed after training, not assumed from attendance. Observe users completing common tasks, review their entries, and provide targeted coaching. Keep a record of training, assessment results, refresher sessions, and authorization to use particular functions. Identify local super-users who can provide immediate support when the project team is unavailable.

Expect a period of adjustment. Staff may worry that electronic monitoring will expose mistakes or increase their workload. Explain how the system supports patient safety and laboratory quality, and use early feedback to remove unnecessary steps. Avoid changing the software and the underlying testing procedure at the same time unless the change is essential, since simultaneous changes make problems harder to diagnose.

Verify performance before full implementation

Pilot the system with a limited test menu, work shift, or specimen pathway. Use realistic scenarios, including rejected specimens, repeat tests, invalid results, amended reports, referrals, equipment downtime, and urgent notifications. Compare electronic outputs with the approved paper workflow and involve quality staff in reviewing every discrepancy.

Before full rollout, confirm that identifiers remain linked from reception to reporting, turnaround times are calculated correctly, and reports contain all required information. Check that users cannot bypass critical review steps and that the system handles duplicate or amended results correctly. Confirm backup restoration by conducting a test recovery rather than relying on a backup log alone.

During the first weeks, hold brief review meetings and track issues by severity, owner, action, and closure date. A small problem with a field label may need rapid correction, while a problem affecting result release requires immediate containment. Do not make uncontrolled configuration changes in response to individual complaints; assess proposed changes through the laboratory’s document and change-control process.

Use records for continual improvement

Electronic records create opportunities for routine quality monitoring. Select indicators that reflect laboratory priorities, such as rejected specimens, missing demographic data, turnaround time, contamination rates, amended reports, equipment downtime, stock-outs, and unresolved discrepancies. Define each indicator precisely so results remain comparable over time.

Review data with the people who generate it. A dashboard may show delayed reporting, but staff can explain whether the cause is transport, reagent availability, instrument failure, verification bottlenecks, or an inaccurate timestamp. Use trends to investigate causes and assign corrective actions rather than treating the figures as a performance score alone.

Keep reviewing whether the system remains fit for purpose. New TB testing methods, reporting requirements, instruments, connectivity arrangements, and privacy rules may require updates. Periodic internal audits should examine both electronic controls and the underlying laboratory practice. The GLI Quality Tool’s emphasis on assessment and continual improvement can help organize these reviews across the quality system.

Actions that support a controlled transition

A successful shift preserves the reliability of the old process while building stronger traceability, faster access, and better oversight. Begin with a documented workflow, involve the people who use the records, and expand only after the pilot evidence supports the change. Use the GLI Quality Tool resources to align system decisions with laboratory quality requirements, then turn routine electronic data into practical action for safer, more dependable TB testing.