Improving TB Sample Submission Forms Through User Feedback
A sample submission form is often the first point of contact between a referring facility and a tuberculosis laboratory. It carries clinical details, patient identifiers, test requests, specimen information, and safety-related instructions. When the form is unclear or incomplete, the laboratory may need to delay accessioning, contact the sender repeatedly, or reject a specimen that could otherwise have supported timely diagnosis.
Feedback from people who complete, review, transport, and receive these forms provides practical evidence for improvement. Their experience can reveal confusing terminology, duplicated fields, missing prompts, and workflow problems that are easy to overlook during an internal review.
The goal is not to make the document longer. A well-designed submission form collects the information required for reliable testing while making the correct action easy for the user. This supports traceability, reduces pre-analytical errors, and strengthens communication across the TB diagnostic network.
Why submission forms deserve attention
Many laboratory errors begin before a specimen reaches the testing bench. A missing collection date can affect specimen stability and turnaround monitoring. An illegible patient identifier can create a serious risk of misidentification. An unclear test request may lead to unnecessary clarification or inappropriate processing.
Forms also influence biosafety. A prompt indicating suspected infectious disease, the type of specimen, or special transport conditions helps staff prepare for receipt. If these fields are hidden in dense text or expressed in unfamiliar language, users may skip them or provide inconsistent answers.
A form should therefore be treated as a controlled laboratory document rather than a routine administrative attachment. Its design affects quality indicators such as rejection rates, incomplete request rates, corrected reports, and delays between collection and testing. Reviewing these indicators alongside user comments creates a stronger basis for change.
Listen to every type of user
The person filling out a request form may be a clinician, nurse, laboratory technologist, community health worker, courier, or records clerk. Each group interacts with different parts of the process. A clinician may struggle to identify the correct test, while a courier may need clearer packaging or receipt instructions.
Users at the receiving laboratory also provide valuable feedback. Accessioning staff know which fields are most often missing, which handwriting is difficult to interpret, and which forms require phone calls. Supervisors can identify recurring trends across facilities, while referral-site staff can explain why a field is difficult to complete in a busy clinic.
Collect feedback through several channels: short interviews, observation, review meetings, help-desk records, rejection logs, and direct comments written on returned forms. Ask users to describe the task they were trying to complete, where they hesitated, and what information they needed at that moment. Specific examples are more useful than general statements such as “the form is confusing.”
Turn comments into measurable evidence
User feedback becomes more actionable when it is linked to a defined problem. A comment such as “the specimen section is difficult” should be examined further. Is the problem the number of specimen options, unfamiliar abbreviations, insufficient writing space, or uncertainty about whether sputum is spot or early-morning material?
Group findings into categories that match the laboratory workflow. Common categories include patient identification, clinical information, specimen collection, test selection, transport, authorization, and result communication. Record the source of each observation, the frequency of the problem, its effect on testing, and the proposed response.
A simple review record can help teams prioritize changes:
| Feedback or finding | Possible cause | Quality risk | Useful measure | Potential response |
|---|---|---|---|---|
| Collection date often missing | Field is too small or poorly placed | Delayed processing or uncertain stability | Percentage of forms missing date | Enlarge and reposition the field |
| Test request is unclear | Similar tests are listed together | Incorrect or delayed examination | Clarification calls per 100 requests | Use plain-language options |
| Patient identifier is inconsistent | Different facilities use different identifiers | Misidentification risk | Corrected or rejected requests | Add required identifier guidance |
| Transport details are incomplete | No prompt for dispatch conditions | Specimen deterioration or safety concern | Requests with missing transport data | Add time and temperature fields |
| Users leave clinical fields blank | Information is not available at collection point | Limited interpretation of results | Blank rate by field and site | Mark essential fields and explain why |
Prioritize issues according to risk, frequency, and feasibility. A small change to the order of fields may prevent more errors than adding several instructions. In a quality management system, the reasoning behind each change should be recorded so that the team can assess whether the revision produced the expected benefit.
Design around the real workflow
Begin with the sequence of actions, not the existing appearance of the form. The user should be able to identify the patient, describe the specimen, select the requested service, provide collection and transport details, and sign or authorize the request without moving repeatedly between unrelated sections.
Use clear labels and locally understood terms. If an abbreviation is essential, define it near its first use. Separate mandatory information from optional clinical context, and explain why critical fields matter. A prompt such as “collection date and time” is more useful than “date,” particularly when specimen stability and transport delays are monitored.
Test the revised form with people who were not involved in its design. Ask them to complete it using realistic scenarios, including a routine sputum request, a referral for molecular testing, and a specimen with incomplete clinical information. Observe where they pause, ask for help, or make an unintended selection. Their performance may expose problems that a review meeting does not reveal.
Digital forms require the same care. Required fields, drop-down menus, and validation rules can prevent omissions, but poorly chosen options can create new barriers when connectivity is limited or devices are shared. Paper and electronic versions should use consistent field names, identifiers, and revision controls so that information remains traceable across sites.
Verify that revisions improve performance
After changing a sample request form, define a review period and compare results with a baseline. Useful indicators include the proportion of forms returned for correction, specimen rejection by reason, missing-field frequency, clarification calls, and time from receipt to accessioning. Analyze results by referring facility where possible; an overall improvement can conceal continuing problems at one site.
Feedback should continue after implementation. A short follow-up conversation may show that users understand the new layout but cannot access a required patient identifier. A rejection log may reveal that an apparently simple specimen category is interpreted differently by different facilities. These findings should lead to refinement rather than blame.
Keep the form under document control. Assign a document number, version, approval date, owner, and review schedule. Remove obsolete copies from facilities and explain the change before distributing the new version. Training should focus on the reasons for critical fields and the actions required when information is unavailable.
The WHO SLMTA assessment guidance can help laboratories connect this review to broader evidence of implementation, monitoring, and continual improvement. Documented user feedback, corrective actions, and follow-up measurements can demonstrate that the form is managed as part of the quality system.
Connect form improvement to quality essentials
Sample submission forms intersect with several Quality Systems Essentials. Documents and records require control of versions and retention. Organization and personnel determine who completes, checks, and authorizes a request. Equipment and purchasing may affect transport information, while assessment and continual improvement provide methods for identifying and correcting recurring failures.
This wider view prevents the laboratory from treating every incomplete form as an individual user error. Patterns may indicate unclear responsibilities, insufficient training, poor referral communication, or a mismatch between the form and available services. Addressing the underlying process usually has a greater effect than repeatedly reminding staff to “fill out the form correctly.”
The quality management framework provides useful context for placing this work within a structured laboratory improvement effort. Teams can use its phased approach to decide what should be standardized first, which records to maintain, and how to progress from basic controls to sustained monitoring.
Actions for a practical review cycle
A focused improvement cycle can be completed without waiting for a major redesign project. Start with a limited number of high-volume referral sites and collect enough evidence to understand their normal workflow. Include staff who use the form under time pressure, since convenience and clarity are central to reliable completion.
Use the findings to make a controlled revision, communicate the change, and measure its effect. The following actions provide a practical starting point:
- Review rejected or incomplete requests from the previous three to six months and group them by missing or confusing information.
- Observe at least one complete referral process, from form completion and packaging to laboratory receipt and accessioning.
- Interview users from both sending facilities and the receiving laboratory using specific examples rather than general satisfaction questions.
- Pilot the revised form with representative users and record completion time, clarification requests, and remaining errors.
- Set a review date and assign responsibility for checking indicators, collecting comments, and approving future revisions.
An effective form is a living part of the TB laboratory workflow. When laboratories systematically use feedback, they can remove avoidable barriers, improve specimen traceability, and make communication more dependable across the testing network. Begin with the most frequent or highest-risk problem, document the change, and invite users to help evaluate whether the new form works in practice.