1. Document Overview

Utprerona is a unified application used by multiple health system actors such as ASHA Supervisors, CHOs, and ANMs, with access governed through role-based user authentication. Based on the logged-in user's role and mapped geography, the application provides access to relevant ASHAs, their performance indicators, and incentive claim data. This document defines the requirements for a mobile-first ASHA Supervisor Incentive Verification module within the Utprerona application, aimed at digitising the monthly incentive verification process that is currently carried out through paper-based workflows.

2. Background & Context

Utprerona is used by ASHAs to digitally capture health care activities and generate monthly incentive claims, with incentive amounts auto calculated based on predefined NHMNHM logic.
Currently, ASHA Supervisors:

• Manage multiple sub-centres (often 3–5+)
• Verify ASHA incentive using paper registers (Master claim form)On Master claim form

This manual process is time-consuming, error-prone, and lacks transparency and auditability.

3. Problem Statement

• No digital interface for supervisors to review incentive claims
• Heavy dependency on paper records
• Delays in verifications and payments
• No system-level audit trail

4. Product Vision & Goals

Vision

Provide ASHA Supervisors with a simple, mobile-first digital interface to review and verify ASHA incentive claims efficiently and transparently.

5. User Persona

Primary User: ASHA Supervisor

• Oversees multiple mapped ASHAs under supervisoreditedASHAs mapped across sub-centres
• Responsible for monthly incentive validations further is validated by CHO/ANM
• Uses smartphone as primary device
• High workload, limited time

6. In-Scope / Out-of-Scope

In-Scope (Phase 1)

• Role based login for Supervisor/ CHO/ ANM using FLW App
• Supervisor Dashboard
• ASHA Monthly incentive summary
• Activity-level review
• Single Verify Verifiedaction
• Audit loggingSupervisor Dashboard requirementwe have to collect all required KPIs for ASHA cell & ops team

Out-of-Scope

• Block/District approvals
• Incentive recalculation or edits
• Payment disbursement
• Web portal

7. State Specific Configuration

Certain configurations must be applied differently for the Mitanin and Utprerona application build variants based on Statespecific requirements. The following functional behaviors distinguish the two builds:

Supporting Document Verification

• • Not applicable in the Mitanin app.
  • Applicable in the Utprerona app.

Incentive Amount Calculation

• • Not applicable in the Mitanin app.
  • Applicable in the Utprerona app.

Verification Workflow

• • In the Mitanin app, only ASHA Supervisor verification is required.
  • Additional verification layers (CHO or ANM) apply only to the Utprerona app.

Cutoff Dates

• • Cutoff dates are different for each State-specific build, and the configuration must be maintained separately for the Mitanin and Utprerona app variants.

8. Verification Model

Verification Granularity

Every month all ASHAs incentive claimed activities are verified by respective ASHA supervisor; and if required, followed by other actors like CHO or ANM, further post verification claims are processed to the SSD portal for approval actions. Hence the two roles of ASHA supervisor broadly are

1. *Validate individual incentive-linked activities of ASHAs*Is this about ASHA Supervisor related incentives activities?
   If that is the case, we have take it up in next coming phases as this requirement is pending
2. Verify Verifies-so change accordinglyall pending claimed activities of ASHA for that particular month

Incentive amounts are read-only and system-calculated.

8. User Journey (High-Level)

9. Functional Requirements

*9.1 Supervisor Dashboard (KPIs will be shared separately later)*we will share the KPIs separatelyMentioned

Features

• Login Screen for Supervisor- Role based access- mapped with facility
• The dashboard header Pending status should also be shown to supervisor -so that she can reachout to asha for completion shall display the logged-in Supervisor's name and Supervisor ID
• Dashboard should display overall status of how many ASHAs verification is pending vs completed so that supervisor can approach them for completion
• Month selector (default: previous month)
• Smart search:
  • ASHA name
  • Sub-centre name (shows all ASHAs under it)
• Optional sub-centre filter (for shortcut)
• Option to Verify or Reject each ASHA claims globally- Each ASHA's verification will be done only ONCE unless it is rejected, if rejected then post resubmission of ASHA, it can be verified again
• Notification Alerts to Supervisor after submission by ASHAs
• Supervisor profile
• Report generation of Incentives PDF

ASHA Card Fields

• ASHA's Full Name
• ASHA Emp ID
• Sub-centre Name
• Total incentive amount
• Activity count
• Verification Status: verified by / Pending

9.2 ASHA Monthly Detail Screen

Header

• ASHA Name, Emp ID
• Sub-centre Name
• Month & Year
• Overall status

Summary Card

• Total activities
• Total incentive (read-only)
• Approved amount
• Pending amount

Primary Action

• Verify All Pending Activities

9.3 Activity Review

Each activity displayed as expandable card:
Collapsed View

• Activity name
• Date
• Incentive amount
• Status

Expanded View

• Activity metadata (read-only)
• Approve/reject action after physical verification of documents on ASHA's device
  • (Dropdown-multiselect) Rejection Reasons: • Incomplete documentation• Incorrect data (system error)• Beneficiary data mismatch• Calculation error• Duplicate claim• Ineligible activity• Outside service period• Other (mandatory remarks)

9.3.1 Activity Colour Coding

Activity cards in the Supervisor application shall follow the same colour coding used in the Utprerona ASHA application to maintain visual consistency and improve verification efficiency.

Colour Categories

Implementation Notes

• Colour must be driven from backend activity metadata.
• Supervisor app must not hardcode colour mapping.
• Colour should be applied to activity card background/header.

10. Status Lifecycle

10.1 Activity-Level Status (Role-based)

Each incentive-linked activity shall move through the following role-based verification statuses, which are visible to ASHA users:

Note: Either CHO or ANM verification is required / applicable.

10.2 Monthly ASHA Status (Derived)

The monthly status for an ASHA shall be system-derived based on the verification state of all activities submitted for the selected month.

Note: Monthly status is read-only and updated automatically by the system.

*11. Business & System Logic*Add rejection flow and simultaneous triggers: If rejection happens @supervisor level then ASHA will get a notification with rejection remarks.

@CHO will get similar reflection of the three tiles of the supervisor dashboard with pending and rejection

12. Data & Audit Requirements

Audit Logging (Next phase/update can include the

13. Security & Access Control

1. Supervisor can view only mapped ASHAs and sub-centres
2. Role & geography enforced at API level
3. Along with incentive claim data, the system shall transmit verifier metadata, including ASHA Supervisor, CHO, and ANM identifiers, as part of the API integration with the SSD portal to support auditability and downstream processing.
4. Access to the module (Important):
   • Role-Based Access to Applications
     • Users with roles CHO, Medical Officer (MO/Doctor), Nurse, Pharmacist, Lab Technician, Registrar, or any combination of these roles, should have access to the HWC application.
     • Users with the CHO role must be able to log in to both FLW and HWC applications.
   • FLW App Access Control
     • Users with roles ASHA, ASHA Supervisor, or ANM should have access only to the FLW application.
     • In the FLW app:
       • Users with roles CHO, ASHA Supervisor, or ANM should have access only to Supervisor modules, and must not access ASHA comprehensive modules.
       • Users with the ASHA role should have access to all ASHA comprehensive modules, but not to Supervisor modules.

*14. Escalation & Reminder Mechanism (Please refer to User Journey on Page 3 for reference)*Hierarchy:

ASHA- Supervisor- CHO/ANM (beyond cut off date for supervisor CHO/ANM will have the verification responsbility)-SSD
Maintaining the status level (Verified/Pending/Rejected) at every level (Supervisor/CHO/ANM)
To ensure timely completion of incentive verification and prevent delays in downstream processing, the system shall implement an automated reminder and escalation mechanism.
Please note: In Utprerona for ASHAs they should get reminder to fill out the claim information in accordance with the monthly set date set up by the Supervisor

14.1 Supervisor Reminder Notifications

Notification content (indicative): "X ASHAs have pending incentive verifications for Month YYYY. Please complete verification to avoid delays in payment processing."

14.2 Escalation to Medical Officer/Reporting Manager

*Escalation message (indicative):*  "Incentive verification for _X ASHAs_ under Supervisor _\[Name\]_ is pending for _Month YYYY_ beyond the defined timeline. Kindly review and follow up."
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\
\\

Screen (UI) Mockups

Log in page Profile under the 3 line (hamburger)option
(Admin filled) Incentive Dashboard
Follow it up with ASHA Supervisor profile: Nmae, employee ID, Designation, email, Working since etc In Supervisor profile what details need to show?
Incentive screen for ASHAs listed Single ASHA screen with Incentive
under a particular subcentre Verification