-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Low
-
Affects Version/s: None
-
None
-
STOP TB Sprint 11
Type: New requirement (remaining scope from STOP-40) · Module: Counselling Officer – Confirmed TB Cases, Treatment (PRD 7.3) · PRD: TBMJA PRD v186, highlighted changes
Background / Context
STOP-40 (To Do, release 3.0) covers Type of Treatment (DS TB / PMDT), the dependent regimen and a read-only Expected Treatment Completion Date field. Its "Open question" blocks the auto-calculation because the PRD had no durations. PRD v186 now supplies them. This ticket covers only the remaining part: the calculation rule. Field layout and regimen selection stay in STOP-40.
Problem Statement
Expected Treatment Completion Date cannot be implemented until the per-regimen durations are specified in Jira.
Current Behaviour
Not built. STOP-40 states: "If Regimen Type is DS-TB then add _" and "If Regimen Type is PMDT, then add _", values missing.
Expected Behaviour / Requirement
Auto-calculate Expected Treatment Completion Date from Treatment Start Date:
| Type of Treatment | Regimen | Add to Treatment Start Date |
|---|---|---|
| DS TB | 2 HRZE/4HRE | 6 months |
| PMDT | Regimen for H mono/Poly | 6–9 months |
| PMDT | Longer M/XDR-TB Regimen | 18–20 months |
| PMDT | Shorter MDR/RR-TB Regimen | 9–11 months |
| PMDT | BPaLM/BPaL Regimen | 6–10 months |
User Story
As a Counselling Officer, I want the expected completion date calculated from the regimen, so that follow-up planning matches the regimen's length.
Acceptance Criteria
- Given Type of Treatment = DS TB and a Treatment Start Date, when saved, then Expected Treatment Completion Date = start date + 6 months.
- Given a PMDT regimen and a Treatment Start Date, when saved, then Expected Treatment Completion Date is calculated using the rule agreed in open question 1.
- Given the regimen or start date changes, when saved, then the date recalculates.
- Given the field, when shown, then it is read-only.
Business Rules / Validations
Treatment Start Date rules in STOP-40 are unchanged (mandatory, on or after diagnosis visit date, not a future date).
Dependencies
- STOP-40 (To Do, 3.0): Type of Treatment, regimen fields and the read-only date field. This ticket cannot ship before it.
STOP-42(Closed): "Did the patient complete the full course" is enabled after 5 / 9 / 18 monthly visits, keyed to old regimen numbers "1"–"5". STOP-40 already flags that these need remapping.
Impact / Affected Areas
Confirmed TB treatment form, follow-up planning, treatment completion thresholds.
Out of Scope
Type of Treatment and regimen selection (STOP-40). Treatment outcome options (STOP-601).
QA / Testing Considerations
Test each regimen, month-end start dates (for example 31 Jan + 6 months) and switching between DS TB and PMDT.
Open Questions / Clarifications
- PMDT durations are ranges (6–9, 18–20, 9–11, 6–10 months). Which value should the auto-calculation add: the minimum, the maximum, or a user choice? [TBD/CLARIFICATION REQUIRED]
- How should the 5 / 9 / 18-visit thresholds for "Did the patient complete the full course" map to the new regimens? [TBD/CLARIFICATION REQUIRED]
- STOP-40 is in release 3.0; the backlog tracker targets Confirmed TB changes for 2.4. Which release for this ticket and STOP-40? [TBD/CLARIFICATION REQUIRED]
PRD Reference
TBMJA PRD – Section 7.3 Confirmed TB Cases — Treatment & Follow-Up: https://pmp.piramalswasthya.org/confluence/spaces/AMRIT/pages/149487638/TBMJA+PRD
- relates to
-
STOP-40 Assign Type of Treatment (DS TB / PMDT) and dependent regimen to a confirmed TB case
-
- Todo/Open
-