Update Presumptive TB Cases & TB HWC Referrals : Workflow and Visit-wise Data Capture

XMLWordPrintable

    • Type: Story
    • Resolution: Done
    • Priority: Low
    • 2.14
    • Affects Version/s: None
    • None
    • FLW Sprint 55
    • FLW Mobile App
    • All

      Changes applicabale for both Utprerona and Mitanin 
      Module: Disease Control → Communicable Diseases → Tuberculosis → Presumptive TB Cases

      BRD to refer : https://pmp.piramalswasthya.org/confluence/spaces/AMRIT/pages/85753874/BRD+Sakhi+Mobile+App#BRDSakhiMobileApp-_Toc190870944PresumptiveTBcases

      1. Background

      The Presumptive TB Cases workflow needs to be updated to support visit-wise data capture, allow ASHAs to update investigation and diagnosis details during subsequent visits, and ensure records move to the appropriate sections based on TB diagnosis and TPT recommendation status.

      2. Requirements

      A. Rename Track Button

      • Rename the existing Track button to Follow Up.
      • Retain the existing functionality to access and update beneficiary visit details.

      B. Remove Referral Facility

      • Remove the Referral Facility question from the Presumptive TB Case form.

      C. Nikshay ID Validation


      • Add validation to the Nikshay ID field to ensure that only valid IDs are accepted. As mentioned in the BRD.

      D. Change the question from 'Has the diagnosis of TB been confirmed ? to 'Is TB confirmed?'

      E. Add a new question of 'Recommended for TPT?'

      F. Make the question 'Sputum test Result' mandatory

      F. TB Diagnosis Confirmation and Record Movement Logic

      Field / Condition Expected Behaviour
      Is TB confirmed? — Yes Move the record to the Confirmed TB Cases section.
      Is TB confirmed? — No Display the next question: 'Recommended for TPT'?
      Recommended for TPT? — Yes Move the record to the TPT section.
      Recommended for TPT? — No Move the record to the TB Screening section.

      G. Visit-wise Data Capture

      Visit 1 – Initial Visit

      Display the following fields:

      • Type of TB Case
      • Is Sputum Sample Collected?
      • Sputum Sample Submitted
      • Nikshay ID

      Do not display the following fields during Visit 1:

      • Sputum Test Result*
      • Is TB confirmed?*

      Visit 2 – Follow-up Visit

      • Provide an Edit option to reopen the existing beneficiary record.
      • Allow the ASHA to enter/update:
      1. Sputum Test Result*
      2. Is TB confirmed?*
      3. Recommended for TPT?*
      • Previously captured information and visit history must be retained.
      • Updating the record must not create a duplicate beneficiary record.

      F. HWC Referrals – TB Follow-up Workflow

      Requirement: Remove the currently displayed form in the HWC follow-up workflow and directly link it to the existing Presumptive TB Cases Follow-up flow.Ensure consistent navigation between Start Follow-up in the HWC Referrals section and Track/Follow-up in the Presumptive TB Cases workflow.

      Acceptance Criteria

      • When an ASHA navigates to HWC Referrals→ TB and clicks Start Follow-up, the system should open the same follow-up flow displayed when the ASHA clicks Track/Search Follow-up in the Presumptive TB Cases module.
      • The same fields, previously captured information, follow-up details, and available actions should be displayed in both entry points.
      • The system should retain the selected beneficiary's context and display the relevant beneficiary's existing record, rather than opening a blank form or an unrelated record.
      • Accessing the follow-up flow through either entry point must not create duplicate beneficiary or follow-up records.

      Acceptance Criteria

      1. Track Button renamed to Follow Up, while retaining the functionality to access and update beneficiary visit details.
      2. Referral Facility Removal: The Referral Facility question is no longer displayed in the Presumptive TB Cases form.
      3. Nikshay ID Validation: The Nikshay ID field validates entries as per the rules defined in the BRD. Invalid entries must trigger an appropriate validation message and must not be accepted.
      4. Question Label Update: The question “Has the diagnosis of TB been confirmed?” is renamed to “Is TB confirmed?” wherever it appears in the relevant workflow.
      5. Sputum Test Result Mandatory: The Sputum Test Result field is mandatory when displayed during the follow-up visit. The record cannot be submitted without a valid selection.
      6. Visit 1 – Initial Visit: The form displays only the following fields:
      • Type of TB Case
      • Is Sputum Sample Collected?
      • Sputum Sample Submitted
      • Nikshay ID

      The Sputum Test Result, Is TB confirmed?, and Recommended for TPT? questions are not displayed during Visit 1.

           7. Visit 2 – Follow-up Visit: The ASHA can access the existing beneficiary record using the Edit option and enter or update the following fields:

      • Sputum Test Result
      • Is TB confirmed?
      • Recommended for TPT?, displayed only when Is TB confirmed? = No

      8. Data Retention: Information captured during Visit 1, along with previous visit details and history, is retained when the record is reopened and updated during Visit 2.

      9. Duplicate Prevention: Updating an existing beneficiary record during follow-up does not create a duplicate beneficiary or presumptive TB case record.

      10. TB Confirmation Logic: When Is TB confirmed? = Yes, the record moves to the Confirmed TB Cases section.

      11. TPT Recommendation Logic: When Is TB confirmed? = No, the system displays the Recommended for TPT? question.

      12. TPT Section Movement: When Recommended for TPT? = Yes, the record moves to the TPT section.

      13. TB Screening Section Movement: When Recommended for TPT? = No, the record moves to the TB Screening section.

      14. Conditional Question Behaviour: The Recommended for TPT? question is displayed only when Is TB confirmed? = No and is not required when TB is confirmed.

      15. Cross-Application Consistency: All the above changes, validations, visit-wise data capture rules, and record movement logic work consistently in both Utprerona and Mitanin.

      16. Regression Testing: Existing Presumptive TB Cases functionality, beneficiary data, and visit history continue to work as expected after these changes.

      cc: madhava.ramu@piramalswasthya.org  ritam.dubey@piramalswasthya.org 

              Assignee:
              Pratiksha Pandey
              Reporter:
              Pranoti Monde
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: