How to implement a two-person verification system for TB test results
A two-person verification system adds an independent review before a tuberculosis (TB) result is released, reported, or used to guide patient care. One staff member performs and records the test, while another qualified person checks the work, confirms the interpretation, and authorizes the final result. The process can apply to smear microscopy, molecular testing, culture, identification, and drug-susceptibility testing, although the review points will differ by method.
The purpose is not to create unnecessary duplication. It is to detect preventable errors such as sample mix-ups, incorrect result transcription, invalid controls, transcription mistakes, or an interpretation that does not match the test evidence. A well-designed verification process should fit the laboratory’s staffing, workload, technology, and reporting system.
The GLI Quality Tool can help laboratories connect this procedure with broader quality management activities, including personnel competency, documentation, equipment, assessment, and continual improvement. Verification is most effective when it is treated as a routine quality control measure rather than an informal second opinion.
Why independent verification matters
TB testing often involves results with serious clinical and public health consequences. A false-positive result can expose a patient to unnecessary treatment and stigma, while a false-negative result may delay care and allow transmission to continue. Errors may arise at any stage, from specimen reception to data entry and report dispatch.
A second reviewer provides an intentional pause between testing and reporting. The reviewer confirms that the patient and specimen identifiers match, the test was valid, quality control requirements were met, the result is technically plausible, and the final report accurately reflects the approved interpretation. This is especially valuable for positive results, rifampicin resistance findings, contaminated cultures, and unexpected changes from previous results.
Verification should be risk-based. A laboratory may require review of every result when staff numbers are small or a new method is being introduced, then apply targeted verification after competency has been demonstrated. The policy must clearly state which results require independent approval and which may be released under defined routine controls.
Define roles, authority, and review points
The primary tester is responsible for performing the examination according to the current standard operating procedure, recording raw observations, and identifying any problem before submitting the result for review. The verifier must be competent in the relevant method and sufficiently independent to assess the work without simply copying the first person’s conclusion.
Independence does not always require a different shift or department. In a small facility, it may mean that the second person reviews the original worksheet, instrument record, quality control data, and specimen identifiers before seeing or accepting the reported interpretation. The verifier should document their own decision, rather than signing automatically.
The procedure should specify when verification occurs. For example, a molecular result may be reviewed after the run validity and internal controls are checked, while a culture result may require review after identification and susceptibility testing are complete. If the verifier is unavailable, the result should remain pending or follow a documented escalation pathway; staff should never use another person’s login or signature.
Design a practical result workflow
Start by mapping the complete path of a specimen: accessioning, testing, technical review, verification, reporting, and correction. At each stage, identify where a wrong patient identifier, an incomplete record, a failed control, or an unclear interpretation could enter the process. The workflow should show who acts, what evidence they check, and what happens when the two staff members disagree.
A paper-based system can use separate tester and verifier fields on worksheets, with dates, signatures, and a clear final authorization box. An electronic laboratory information system can assign a pending status, require a second login, and preserve an audit trail. Either approach is acceptable if records are legible, retrievable, protected from unauthorized changes, and linked to the original specimen.
The verifier should review source information rather than only the final number or word. Depending on the assay, this may include the specimen label, accession number, run or batch identifier, instrument flags, control results, images, culture observations, identification data, and drug-susceptibility patterns. A result should not be released until all required fields are complete.
| Testing activity | Primary tester records | Verifier checks | Typical release decision |
|---|---|---|---|
| Smear microscopy | Stain quality, slide reading, grading, reader identification | Slide identity, staining quality, grading criteria, discordant findings | Approve, request reread, or refer for resolution |
| Molecular testing | Sample ID, run data, controls, detected targets, resistance markers | Run validity, control status, instrument flags, interpretation | Release valid result or hold for repeat/investigation |
| Culture | Growth observations, contamination status, dates, preliminary findings | Specimen identity, incubation records, contamination decision, linked results | Report according to validated stages |
| Identification and DST | Organism identification, raw susceptibility findings, QC data | QC acceptability, pattern plausibility, critical resistance result | Approve, repeat, or escalate to supervisor |
| Result entry and reporting | Transcribed result and comments | Patient details, units, wording, interpretation, recipient | Authorize final report or correct before release |
Manage discrepancies without blame
A verification system only works when disagreement triggers a defined investigation rather than an argument between colleagues. The verifier should mark the result as pending, describe the discrepancy, and notify the responsible supervisor or senior technologist. The primary tester and verifier can then compare the raw data, procedure requirements, instrument information, and specimen history.
Possible actions include rereading a slide, repeating a test when permitted, checking reagent or control performance, reviewing a batch, contacting the referring facility about specimen identity, or referring the case to a reference laboratory. The final decision and reason should be recorded. If the original report was already issued, the laboratory must follow its controlled correction and notification procedure.
The laboratory should distinguish between a technical discrepancy and a clerical error. A mismatch in patient identification requires immediate containment and an assessment of other specimens that may be affected. A difference in interpretation may indicate unclear criteria, insufficient competency, poor image quality, or a need to revise the standard operating procedure. Staff should be encouraged to report these events early so that the system improves instead of concealing risk.
Connect verification with contamination and quality monitoring
Verification should include review of events that affect the reliability of a result, not just the result itself. For culture laboratories, this includes contamination rates, unusual clusters, media performance, environmental observations, and delays in processing. A second reviewer may identify a pattern that is invisible when each culture is considered separately. Laboratories can use the practical guidance on contamination monitoring to establish indicators and response thresholds.
Quality indicators should be reviewed at regular intervals. Useful measures include the percentage of eligible results independently verified, the number of discrepancies, time from testing to authorization, corrected reports, unresolved pending results, and recurring causes of review failure. Results should be separated by method, testing site, staff member, and error category when this information can be handled confidentially and fairly.
A high discrepancy rate does not automatically mean that an individual is performing poorly. It may reflect unclear instructions, equipment problems, an overloaded service, or a weak specimen reception process. Management should examine trends, provide focused coaching, and verify whether corrective actions actually reduce recurrence.
Document competency and protect the audit trail
Before a staff member acts as a verifier, the laboratory should document training and competency for the relevant test method. Competency assessment may include observation of practice, review of recorded results, blind or known samples, interpretation exercises, and evaluation of quality control decisions. A person competent in smear microscopy is not automatically competent to verify molecular resistance results or DST findings.
The written procedure should define terminology, responsibilities, review criteria, required records, escalation contacts, report correction, and retention periods. Forms should make it difficult to skip the second review. Electronic systems should restrict authorization privileges to approved users, record timestamps, and prevent changes to an approved result without an amendment trail.
The phase-specific quality checklists can support a structured review of documentation, personnel, assessment, and continual improvement requirements. Laboratories should adapt checklist items to local regulations and testing methods rather than treating the checklist as a substitute for a validated procedure.
Put the process into daily practice
Implementation is easier when the laboratory begins with one method or one category of high-risk results. Test the workflow for several weeks, collect staff feedback, and correct practical problems such as missing fields, unclear escalation routes, or verification delays. Once the process is stable, extend it to additional methods and reporting stages.
The following actions help establish a reliable system:
- Assign primary tester and verifier responsibilities for every reporting period.
- Define which results require review, including critical, unexpected, invalid, and corrected results.
- Use separate signatures or authenticated logins and prohibit shared credentials.
- Track discrepancies, delays, amended reports, and their documented causes.
- Reassess staff competency and the verification procedure after audits, incidents, or method changes.
A verification program should protect turnaround time as well as accuracy. Staffing plans may need a designated reviewer during peak hours, and urgent results may require an approved escalation process. The goal is a consistent, evidence-based release decision that supports patients, clinicians, and public health teams.
Begin by documenting the current reporting workflow, selecting the highest-risk review points, and assigning trained personnel to a short pilot. Record what the verifier checks, how disagreements are resolved, and which indicators reveal improvement. Then use those findings to formalize the procedure within the laboratory’s quality management system and make independent result verification a dependable part of TB service delivery.