STOP TB – Sprint Scope & Prioritization – v2.2

Overview

⚠️ Note: Tickets already marked Closed below are included for completeness (they're tagged to 2.2) but represent work already done — no scope decision needed on those.

Scope of 2.2

At a glance — what 2.2 covers:

• 🧩 Modules split for role-based access — Counselling, Contact Tracing, TB Treatment Follow-up, and TPT become separate, independently navigable modules so each role sees only what's relevant to them.

• 🔐 Role-based access control — different user roles (Nurse, Counsellor, etc.) get controlled, role-specific access to modules.

• 🏠 Household & beneficiary registration clean-up — consent capture, pincode/address fixes, and field-level corrections to improve registration data quality.

• 🩺 TB screening & diagnostics reliability — faster screening form submission, auto-sync of presumptive TB cases, and fixes to duplicate beneficiary/work-order records.

• 🆔 Nikshay ID generation — ID generation and CSV-based sync support for camp admins.

• 📶 ABHA & attendance fixes — ABHA creation/download bug fixes, attendance tracking.

• 💊 ADR (Adverse Drug Reaction) tracking — new fields added in TPT and Treatment Follow-up modules.

• ✅ Net new vs. clean-up: ~44 of 50 tickets are pending team review; 6 are already delivered/closed.

Detailed scope narrative:

Release 2.2 is primarily a stabilisation and workflow-restructuring release, with a smaller set of new capability additions layered on top.

1. Module separation & role-based access (biggest structural change) Counselling, Contact Tracing, TB Treatment Follow-up, and TPT are being split out of combined screens into distinct, separately-navigable modules/cards (STOP-427, STOP-428), which directly unblocks Role Based User Access (STOP-138) and Manage User Role (STOP-137) — so different roles (Nurse, Counsellor, etc.) only see the modules relevant to them.

2. Household & beneficiary registration clean-up Consent capture on Household Registration to match Family Member Registration (STOP-426), capturing Pincode/Residential Area only once (STOP-412), correcting field visibility for Nurse/Counsellor roles (STOP-424), Add Member button placement (STOP-413), and several smaller field/validation fixes (STOP-162, STOP-165, STOP-166, STOP-168, STOP-171).

3. TB screening, diagnostics & sync reliability Performance and correctness fixes to the TB Screening form (slow submission — STOP-425), auto-sync of presumptive TB cases (STOP-429), duplicate beneficiary/work-order records on TrueNat (STOP-397, STOP-287), and general data-sync stability (STOP-352).

4. Supporting features carried over from earlier analysis Nikshay ID generation & CSV-based sync (STOP-340, STOP-367, STOP-368), Attendance Tracking (STOP-294), ABHA creation/download fixes (STOP-386, STOP-182), and ADR fields added to the TPT and Treatment Follow-up modules (STOP-349, STOP-350).

Scope & Prioritization — by Jira Priority

This table is a live Jira query — it automatically reflects any ticket added, removed, or re-prioritized against Fix Version 2.2, without needing to edit this page. Sorted highest priority first.

Scope Summary

Release Plan

What this release will cover

Once scope is confirmed via the In Scope column above, this will lock to the final list. At draft stage, based on priority, the release is expected to cover: - All 3 Highest-priority items (role-based access foundation, consent & address capture) - The majority of the 30 High-priority items (module separation, registration clean-up, screening/diagnostics reliability) - Medium/Low priority items to be picked up as capacity allows, based on team sign-off below

Module-wise Accountability

QA Testing Plan

• Functional QA: Each in-scope ticket tested against its acceptance criteria before moving "Pending QA" → "Closed"

• Regression QA: Full regression pass on Household Registration, TB Screening, and Referral flows given the volume of changes touching these areas

• Role-based Access testing: Explicit test pass per role (Nurse, Counsellor, Registrar, Admin) to confirm correct module visibility post STOP-138/STOP-427

• Owner: Nidhi (QA Accountable) to confirm test case coverage before UAT sign-off

Data Quality Testing

• Duplicate record checks: Verify fixes for duplicate beneficiary/work-order issues (STOP-287, STOP-397) actually eliminate duplicates in production-like data

• Sync integrity checks: Confirm presumptive TB case auto-sync (STOP-429) and observation auto-sync (STOP-352) produce consistent counts between device and central server

• Field-level data validation: Confirm Pincode/Residential Area (STOP-412) and Address special-character handling (STOP-183) don't corrupt existing records on migration

• Owner: BSA (Madhava) jointly with QA to validate sample data sets pre- and post-release

Reviewer Sign-off

🔒 This release cannot move to development lock / QA start until every reviewer below has marked Approved = Y. No ticket in the "Pending Decision" bucket should be treated as in-scope until this sign-off is complete.

Open Issues / Risks

Release Linkage

• Release Notes page: once the release will be done 

• Related Confluence: Updated- STOP TB PRD