GLI GLI Quality Tool
GLI Quality Tool — Version 2.0

Record-Keeping Practices for TB Culture and DST Laboratories

Reliable records are the evidence that a tuberculosis laboratory’s work was performed correctly, safely, and consistently. In culture and drug susceptibility testing (DST), documentation connects the patient specimen to the final result through every stage of testing. It also allows staff to identify errors, investigate delays, demonstrate competence, and protect the integrity of reported results.

Good record-keeping is more than storing worksheets in folders. It is a controlled process covering data capture, review, correction, access, retention, and retrieval. Records should be accurate enough for technical decisions, clear enough for another trained person to follow, and secure enough to protect confidential patient information.

A practical system must fit the laboratory’s workload, staffing, equipment, and available technology. Paper registers, electronic laboratory information systems, or a combination of both can support quality when responsibilities and controls are clearly defined. The GLI Quality Tool provides a useful framework for connecting record management with broader quality system activities.

Define What Must Be Recorded

Before creating forms or registers, laboratory managers should map the complete testing pathway. This normally begins with the request and specimen collection, continues through receipt, processing, inoculation, incubation, examination, identification, DST, result review, and reporting. Records should show who performed each activity, when it occurred, what materials and equipment were used, and whether any deviation affected the work.

Essential records commonly include specimen reception logs, rejection records, sample processing worksheets, culture registers, contamination records, identification results, DST worksheets, quality control results, equipment maintenance logs, temperature charts, stock records, corrective action reports, and issued reports. The exact list will vary, but every record should have a defined purpose and owner.

Each form should contain only fields that support a decision, traceability, or quality requirement. Excessive paperwork encourages incomplete entries and transcription errors. A well-designed record uses consistent identifiers, clear date and time formats, predefined units, and fields for reviewer approval. Blank spaces should be marked according to local policy rather than silently left unexplained.

Connect Records Across the Testing Process

The laboratory accession number should be the central link between the request, specimen, culture, DST work, and final report. Patient identifiers may be necessary, but a unique laboratory number is usually safer and more practical for tracking internal work. The same identifier should appear on containers, worksheets, culture media, DST plates or tubes, electronic entries, and reports.

At specimen reception, staff should document the source, collection date, arrival date and time, specimen type, volume or condition when relevant, requesting service, and acceptance or rejection decision. If a specimen is unsuitable, the reason should be recorded clearly, along with notification of the submitting facility and any replacement request. A rejection record is valuable evidence that pre-analytical risks are being managed rather than hidden.

During processing, records should preserve the relationship between a primary specimen and any aliquots, pellets, inoculated media, subcultures, or extracted material. When several specimens are handled together, batch records must still make individual results traceable. The quality management roadmap can help laboratories organize these responsibilities within a phased improvement programme.

Capture Culture And DST Data Consistently

Culture records should document the medium or system used, lot number where applicable, inoculation date, incubation conditions, examination dates, observed growth, contamination, and final interpretation. For liquid culture systems, instrument alerts, bottle status, time to detection, and follow-up actions should be retained. For solid media, the record should support interpretation of colony appearance, growth amount, contamination, and any repeat or confirmatory testing.

DST records require especially careful detail because small documentation gaps can affect clinical interpretation. Record the method, drug panel, concentrations or critical concentrations, organism or isolate identifier, inoculum preparation, controls, incubation conditions, reading date, raw observations, interpretation, and reviewer authorization. If results are amended after review, the original entry must remain visible and the reason for the change must be documented.

A culture or DST result should never depend on an undocumented verbal explanation. If an unusual result leads to repeat testing, referral, additional identification, or consultation with a supervisor, that action belongs in the record. Comments should distinguish observed facts from interpretations and should identify the person making the decision.

Record area Minimum information to capture Quality control point
Specimen reception Unique number, specimen type, dates, condition, acceptance decision Reconcile with request and container label
Culture processing Medium or system, lot, inoculation, incubation, examination, result Verify identifier at each transfer
DST testing Method, isolate, drug panel, controls, raw findings, interpretation Require technical review before release
Equipment monitoring Equipment ID, date, reading, acceptable range, action Investigate out-of-range values
Result reporting Final result, authorization, recipient, date and time Match report to reviewed source data
Nonconformity Problem, affected work, immediate action, root cause, follow-up Link to corrective action and closure evidence

Control Forms, Worksheets, And Procedures

Controlled documents prevent staff from using outdated instructions or unofficial forms. Every SOP, worksheet, register, and template should have a title, document number, version, effective date, author, approver, and review date. Obsolete versions should be removed from work areas or clearly marked so they cannot be used accidentally.

Procedures should explain how records are completed, corrected, reviewed, stored, and retrieved. Staff need explicit rules for legible entries, use of ink, approved abbreviations, correction of mistakes, and management of missing information. A correction should preserve the original entry, show the corrected value, include the date and initials of the person making the change, and avoid concealment or erasure.

The SOP writing guidance offers principles that can also inform documentation for culture and DST activities. Even when a laboratory uses electronic forms, the procedure should define user permissions, audit trails, data validation, backup arrangements, and what happens if the system is unavailable.

Review Data Before Results Are Released

Technical review is a deliberate check that the recorded work supports the reported result. The reviewer should compare the request, specimen identity, raw observations, quality control findings, calculations, instrument output, and interpretation. Review should also confirm that controls were acceptable and that any deviation has been assessed.

A second level of authorization may be required for complex DST findings, critical results, unexpected resistance patterns, or amended reports. The laboratory should define who can review and release each type of result. Signatures, initials, electronic approvals, or authenticated user accounts must be attributable to a specific person.

Records should make amended reports transparent. The amended version should state what changed, why it changed, when the change was authorized, and who received the correction. The original report and supporting data should remain retrievable, because removing the earlier version weakens the audit trail and can make incident investigation difficult.

Protect, Retain, And Retrieve Records

Confidentiality controls should cover both paper and electronic records. Paper files should be stored in secure areas with controlled access, while electronic systems should use individual accounts, appropriate permissions, password protection, and regular backups. Patient information should not be copied to informal notebooks, personal devices, or unsecured messaging platforms.

Retention periods should be based on national requirements, accreditation rules, clinical value, and the laboratory’s risk assessment. The retention policy should specify which records are kept, where they are stored, how long they remain available, and how disposal is authorized. Destruction should be secure and documented, particularly for records containing patient identifiers.

Retrieval is a practical test of record quality. A supervisor or assessor should be able to locate a complete testing record using the laboratory number, date, specimen source, or patient identifier permitted by policy. Periodic retrieval exercises can expose missing pages, broken electronic links, unreadable handwriting, weak indexing, or gaps between culture and DST documentation.

Priorities For A Stronger Record System

Laboratories can improve documentation without waiting for a new information system. Start with the highest-risk steps, simplify forms, train staff using real examples, and review a sample of completed records at regular intervals. Small, consistent controls usually produce more reliable results than complex procedures that staff cannot sustain.

The following priorities support a practical quality improvement programme:

Turn Documentation Into Quality Evidence

Record-keeping best practices for TB culture and DST laboratories should make technical work visible, traceable, and reviewable. When records are complete, the laboratory can defend its results, identify process weaknesses, demonstrate staff competence, and respond quickly to incidents. When records are inconsistent, even technically correct work becomes difficult to verify.

Laboratories can access tools, checklists, and phase-specific resources through the GLI Quality Tool. Use those materials to assess current documentation, prioritize gaps, and build a record system that supports safe testing and dependable tuberculosis diagnosis.