Implement Follow-Up and Case Closure Workflow

XMLWordPrintable

    • Type: Story
    • Resolution: Done
    • Priority: Medium
    • 5.0
    • Affects Version/s: None

      As a Community Health Officer (CHO) I want to record follow-up details and close cases when appropriate so that patient progress is tracked and cases are closed with clear outcomes.

      Acceptance Criteria

      • Follow-Up & Closure section is available as part of the ongoing care workflow.
      • “Follow-up required” is a mandatory Yes / No selection.
      • If “Follow-up required” is set to Yes, Follow-up date becomes mandatory.
      • Follow-up date must be captured in dd-mm-yyyy format.
      • “Improvement noted” is mandatory and must be selected as:
        • Improved
        • Same
        • Worse
      • Repeat PHQ-9 is available as applicable based on clinical need or program rules.
      • “Referral escalation required” is a mandatory Yes / No selection.
      • If referral escalation is required, the system follows the existing referral workflow.
      • Case closure requires selection of a Case closure reason.
      • Case closure reason options include:
        • Recovered
        • Referred
        • Lost to follow-up
        • Death
      • Case cannot be closed unless a closure reason is selected.
      • Clear validation messages are displayed for missing mandatory or conditional fields.
      Data Fields
      Field Type Options Rules
      Follow-up required Radio Yes / No Mandatory
      Follow-up date Date dd-mm-yyyy Mandatory if follow-up required = Yes
      Improvement noted Radio Improved / Same / Worse Mandatory
      Repeat PHQ-9 Assessment Same as baseline As applicable
      Referral escalation required Radio Yes / No Mandatory
      Case closure reason Dropdown Recovered / Referred / Lost to follow-up / Death Mandatory on closure

              Assignee:
              Deep Shikha
              Reporter:
              Shashank Kharkwal
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: