-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Medium
-
Affects Version/s: None
-
None
-
STOP TB Sprint 10
Background / Context
The follow-up section of Confirmed TB Cases was built under STOP-41 (Closed, 1.3). The ADR field was added under STOP-349 (Closed, 2.3). PRD v186 changes the section title, drops the adherence field and renames ADR to Side Effects.
Problem Statement
The app follows the old spec. Field teams see a field the PRD has dropped and a label the PRD has renamed.
Current Behaviour
- Section is titled "Follow-up & Adherence".
- "Adherence to Medicines" radio (Regular / Irregular) is captured at each follow-up (
STOP-41). - "Any discomfort" = Yes enables "Adverse Drug Reaction" (
STOP-349). - Follow-up visit history table shows an adherence column (
STOP-43).
Expected Behaviour / Requirement
| Item | Change |
|---|---|
| Section title | "Follow-up & Adherence" → "Follow-up" |
| Adherence to Medicines | Remove from the application. PRD keeps the row "for reference" only. |
| Any discomfort (Yes / No) | Yes → enable "Side Effects" |
| Adverse Drug Reactions | Rename to "Side Effects". Searchable dropdown, multi-select, mandatory if enabled. Options unchanged: the 20 listed in PRD 7.3. |
User Story
As a Counselling Officer, I want the follow-up form to show only the fields the programme now uses, so that I record side effects with the correct label and skip fields that are no longer needed.
Acceptance Criteria
- Given a confirmed TB case, when the follow-up section opens, then its title reads "Follow-up".
- Given a follow-up visit, when the form loads, then "Adherence to Medicines" is not shown.
- Given "Any discomfort" = Yes, when selected, then a field labelled "Side Effects" is enabled and mandatory.
- Given "Any discomfort" = No, when selected, then "Side Effects" is disabled and not required.
- Given "Side Effects" is enabled, when opened, then it shows the 20 PRD 7.3 options, supports search and allows multiple selections.
- Given a follow-up is submitted, when viewed in the follow-up visit history, then adherence handling matches the answer to open question 2.
Business Rules / Validations
- Side Effects: multi-select; mandatory only when "Any discomfort" = Yes.
- All other follow-up validations (Follow-up Date rules, one visit per month) are unchanged.
Dependencies
STOP-349(Closed): existing ADR field to rename.STOP-351(To Do, 2.4): search bar ticket still says "ADR"; update its wording to "Side Effects".STOP-43(Closed): follow-up visit history table.
Impact / Affected Areas
Confirmed TB follow-up form, follow-up visit history table, stored follow-up records, any report or export that reads adherence or ADR.
Out of Scope
TPT follow-up (separate ticket). Treatment outcomes (separate ticket).
QA / Testing Considerations
- Check the label change on the form, history table and any detail view.
- Open records created before the change and confirm they still display correctly.
- Confirm the 20 options match PRD 7.3 exactly.
Clarifications
- Adherence values already captured: can be hidden by not deleted.
- Existing ADR records: relabel as Side Effects in all views if possible
PRD Reference
TBMJA PRD – Section 7.3 Confirmed TB Cases — Treatment & Follow-Up: https://pmp.piramalswasthya.org/confluence/spaces/AMRIT/pages/149487638/TBMJA+PRD