ASHA Supervisor Module - API Requirements

XMLWordPrintable

    • Type: Story
    • Resolution: Unresolved
    • Priority: Highest
    • 3.8.1
    • Affects Version/s: None
    • Sprint 55
    • FLW Mobile App
    • AMRIT Demo

      To provide backend APIs that enable the ASHA Supervisor to view profile details, monitor ASHAs under them, verify incentives, and perform approve/reject actions.

      Need roles and sub-center list in login API (ANM and CHO).

      Supervisor Profile API

      Purpose:
      Fetch complete profile details of the logged-in ASHA Supervisor.

      Details Required:

      • Supervisor name
      • Supervisor ID
      • Mobile number
      • banks details
      • Email (if applicable)
      • Assigned Sub-center
      • Block
      • District
      • Total number of ASHAs mapped under the supervisor

        Supervisor Dashboard Summary API

      Purpose:
      Provide summary data for the supervisor dashboard related to incentive verification.

      Details Required:

        • Total ASHAs under the supervisor
        • Count of Verified incentives
        • Count of Pending incentives
        • Count of Overdue incentives
        • Count of Rejected incentives
        • Month and Year-based filtering
      • ASHA List Under Supervisor API

      Purpose:
      Fetch the list of all ASHAs mapped to the logged-in supervisor.

      Details Required per ASHA:

        • ASHA ID
        • ASHA Name
        • Sub-center
        • Total incentive amount (for selected month/year)
        • Current overall verification status

      Filters Required:

        • Status (Pending / Verified / Overdue / Rejected)
        • Month and Year
        • Search by name or mobile number
        • Pagination support.
      • Individual ASHA Incentive List API

      Purpose:
      Fetch the detailed list of incentives submitted by a particular ASHA for a selected month/year.

      Details Required per Incentive:

        • Activity name
        • Activity date
        • Submission date
        • Incentive amount
        • Current status
        • Rejection remarks (if applicable)
      • Incentive Approve / Reject API

      Purpose:
      Allow the supervisor to approve or reject individual incentives.

      Requirements:

        • Status update functionality
        • Rejection remarks must be mandatory
        • Maintain audit logs (action taken by, timestamp, remarks)

       ** 

              Assignee:
              Saurav Mishra
              Reporter:
              Ritik Rathaur
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: