Verification Status Lifecycle, Audit & SSD Integration

XMLWordPrintable

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

      As a Supervisor, I want structured verification status transitions with complete audit logging and SSD portal integration, so that incentive claims are securely tracked, compliant, and accurately submitted.

      Monthly Status Derivation

      Monthly status auto-calculated based on activity states:

      Condition Monthly Status
      No submissions Not Submitted
      Some pending Pending
      All verified Completed
      Sent to SSD Submitted to SSD
      SSD processed Closed
      SSD Portal Integration
      Push Trigger

      System pushes data to SSD when:

      • All activities for ASHA (selected month) are:
        • Verified by Supervisor
      • Monthly status = Completed

      Acceptance Criteria

      • Activity status follows defined hierarchy:
        • Pending with Supervisor
        • Verified by Supervisor
        • Pending with CHO
        • Verified by CHO
        • Pending with ANM (if applicable)
        • Verified by ANM
        • Eligible for SSD Processing
      • Monthly status auto-derived from activity states
      • Audit log captures:
        • Supervisor ID
        • ASHA ID
        • Activity ID (nullable for bulk)
        • Action type
        • Timestamp
        • Remarks
      • SSD push triggered only after:
        • Supervisor + CHO/ANM verification

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

                Created:
                Updated:
                Resolved: