BRD Utprerona App feature enhancements

Business Requirements Document (BRD)

1. Introduction

1.1 Document Purpose

The purpose of this document is to describe business requirements related to the enhancements planned for this phase of development in FLW App “SAKHI”.

1.2 About Piramal Swasthya

Piramal Swasthya Management and Research Institute (PSMRI), an initiative under the aegis of Piramal Foundation. Is one of the largest not-for-profit organizations in India. Piramal Swasthya is contributing with its experience and expertise of building innovative solutions that impact at scale.
Piramal Swasthya is focused on bridging the public healthcare gaps by supplementing and complementing the Government of India's vision to meet Universal Health Coverage. In the primary public healthcare space with a focus on Maternal, Child and Adolescent Health and Non-communicable Diseases. Piramal Swasthya has more than a decade-long experience in operating several healthcare innovations at scale, which are addressing the primary healthcare needs of the most underserved and marginalized populations across India. Piramal Swasthya is operational in 21 States in India through 35 innovative public healthcare delivery programs and has served more than 112 million beneficiaries so far.
One such innovation is AMRIT (Accessible Medical Records via Integrated Technologies) which is a digital health platform developed by Piramal Swasthya that stores electronic health records of beneficiaries for the use of public primary healthcare service delivery and decision-making. The platform enables the connection between beneficiaries, health facilities, and frontline workers in an integrated ecosystem through technology.

1.3 Services and features under AMRIT Platform

HWC Application: A comprehensive application with 12 Service packages.
MMU Application: Offline and Online Application to support operations in outreach programs.
HIHL Application: Helpline CRM to support services like 104, 1097, MCTS and ECD with inbound and outbound facility.
Telemedicine Solution: Video consulting facility.
Smart Phone Applications: Sakhi/ Utprerona Android Mobile App ASHAs.
Point of Care Device: AMRIT is integrated with PoCT devices like Fetosense and Healthcube etc.
ABDM compliant: and AMRIT is integrated with ABDM for ABHA with all three (M1, M2, M3) milestones.

1.4 Background

1.5 Background of ASHA Concept

The Government of India launched National Rural Health Mission (NRHM) in 2005 to address the health needs of rural population, especially the vulnerable sections of society. The Sub Centre (SC) is the most peripheral level of contact with the community under the public health infrastructure. This caters to a population norm of 5000, but is effectively serving much larger population at the SC level.
Thus, provision for new band of community based functionaries, named as Accredited Social Health Activist (ASHA) was made to fill this void. ASHA is the first port of call for any health related demands of the rural population, especially women and children, who find it difficult to access health services.
ASHA is volunteer health activists in the communities, who is creating awareness on health and its social determinants and mobilize the community towards local health planning and increased utilization and accountability of the existing public health services. She is a promoter of good health practices.
ASHA will be entitled for Performance Based Incentives fixed by the NRHM State HQ for prefixed activities only. The performance based incentives required to be given on monthly basis to ASHA.

The role, responsibilities, profile and compensation package for ASHA is given below.

1.6 Scope of Work

1. In FLW Android Mobile App, design and development of new features and enhancements specified in this Business requirements document.
   Including FLW App dependent backend tasks (related to new APIs, business logic, database).
2. Tasks related to AMRIT Admin web portal, related enhancements specified in this Business requirements document.

2. AMRIT Admin web portal enhancements

2.1 Bulk User accounts Registration

Purpose

This process helps admin to save time in creating multiple User accounts individually by entering details manually in the registration form.

Currently the admin portal supports creating single User account at a time. This new approach of bulk User accounts registration process simplifies creating multiple user accounts at a time, simply by entering details in an excel sheet and upload.

Admin Module: Bulk User accounts registration and validation notes

1. Bulk User Creation Process:

   • Download Template: Admin must download a predefined Excel sheet template containing all necessary metadata fields including optional and mandatory fields marked with star ().

   • Fill Template: Admin should fill the excel sheet template with the necessary Users' details including optional and mandatory fields. Mandatory fields must be completed with valid data.
   • Upload Template: The filled excel sheet template is imported using upload function.
   • Validation: System should validate each record as follows:
     • Create User accounts for valid data.
     • Reject creating accounts for invalid data
     • Provide a log report with reason for each record, like invalid/missing data.
   • Feedback:
     • Show success message with count (e.g., "15 out of 20 users created successfully").
     • Provide an error log file for failed records with reasons for failure

Mockup:

Refer to this Jira ticket:  AMM-1220 - Getting issue details... STATUS

In addition to the current feature of creating single User account at a time, introducing this feature of creating multiple User accounts by uploading a excel sheet with the user details like mentioned in this below table.

This below table is only for the reference of metadata used for User account creation, values used in the dropdowns, mandatory or non-mandatory fields, and specific data validation for data sanity. 

3. FLW App enhancements

3.1 About Sakhi App

Sakhi App is a digital job aid tool, specially designed for Accredited Social Health Activist (ASHA). ASHAs usually use multiple registers for Household enumeration, family member registration, and health data collection. This leads to challenges of manual errors, loss of data, and data accuracy. In this context, Piramal Swasthya Management and Research Institute has designed and developed a mobile application for ASHA workers to digitalize and reduce the manual work.

It is designed to reduce manual labor, enhance efficiency, and ensure timely and accurate data collection by ASHAs.

All the services that are carried by ASHA in the field are available in the Sakhi Mobile App, including services for RMNCH+A (Reproductive, Maternal, Newborn, Child, and Adolescent Health), this application enhances service delivery and monitoring for Household Enumeration, Antenatal care, Postnatal care, Immunization services, as well as Non-Communicable Diseases (NCDs) screening and Tuberculosis (TB) screening.

3.2 Sakhi App overview of Comprehensive Modules

3.3 Process flow diagram of Sakhi App

3.4 Implement Beneficiary Consent process

Purpose

Taking consent from beneficiary is very important to save their demographic details, clinical and health records in EHR. 
Beneficiary consent is a process by which we take proper consent from beneficiary digitally, like
OTP-Based Consent: Real-time verification through OTP sent to the beneficiary's mobile number.

This process of taking consent from Beneficiary by verifying the OTP received on the Beneficiary's mobile number is applicable in entire platform service lines where Beneficiary registration takes place.  

Beneficiary Consent using OTP approach

Now consent via OTP should be mandated for Head of the Family and Family Members registration. Once Household registration is completed, proceed with Head of the Family and Family Members registration with taking proper consent by verifying OTP sent on beneficiary's Mobile number via SMS.

After the "Date of Registration" field, provide a editable-text field with Pre-filled Mobile number of HOF for entering the mobile number to capture consent. Display a "Mobile Number Belongs To" dropdown with values, followed by a "Send OTP" button.

Refer to this Jira ticket:  FLW-25 - Getting issue details... STATUS

Use cases:

1. Household registration (amenities) record should sync to server, only once Head of the Family Member's consent is verified. Like order of record syncing process should follow: Household registration >> Head of the Family Member registration >> Family Member registration; only once consent is verified.
2. Successfully, OTP verified records should sync to server and indicate with green color symbol on beneficiary card as "consent is taken"
3. Beneficiary records that are not verified with OTP, should not sync to server, should save as draft and indicate with orange color symbol on beneficiary card to notify "consent is due"
4. Existing Beneficiary records that are already synced to server, but OTP consent is not verified earlier, should indicate with yellow color symbol on beneficiary card to notify "record is synced but consent is due"
5. Beneficiary records should be flag based on the status of consent
6. In Beneficiary line listing, should have a filter to sort the records based on the status of consent

This feature should be implemented in the existing screens/ form of Head of the Family and Family Members registration.

Data fields mentioned in this below table are new fields, should be added to the existing screens/ form for taking Beneficiary consent.

For receiving the OTP on the Beneficiary's mobile number, verifying OTP, etc. An API and SMS gateway integration is required, for these details refer to this Jira ticket: AMM-778 - Getting issue details... STATUS   

3.5 ASHA Incentives

ASHAs are entitled for performance based incentives fixed by the NRHM State HQ for prefixed activities only. The performance based incentives required to be given on monthly basis to ASHA.

Incentive Claim Form should be calculated on monthly basis, that is claim Form should be generated for every month
At any point of time should be able to generate claim Form for selected month
Should the maintain the status of claimed activity and un claimed activity for every beneficiaries
Since some of the activities start and end up after 3 months, 6 months, 9 months and 2 Years, 5 years, so we need to track this activities when it is ended, based on the end date of activity that activity amount can be claimed in that month.

Automate the ASHA incentives claim form

In the FLW App, the primary objective is to generate incentives claim form for the activities completed by the ASHA in that particular month. This will help ASHA to reduce her manual work of filling her incentives claim form.

For calculating the incentives of several activities refer to this document BRD for FLW Mobile App, under section of system validation table under the 'validation section' mentioned as "Incentives Logic". 

This entire incentives logic should be calculated in the backend business model and on hitting the "Create Incentives" button generate the incentives claim form in the PDF format.

Some of the sample activities related to incentives are below:

1.Incentives for ASHAs: Quarterly Visits under HBYC in Aspirational Districts

• This initiative is part of the Health and Wellness initiative under the Home-Based Young Childcare (HBYC) program.

ASHA will get an incentive of ₹250 per child if the following conditions are met (see BRD section 3.5.11- Font in Orange)

• The district selected must be an aspirational district.
• The ASHA worker must have submitted the HBYC forms for the 3, 6, 9, 12, and 15-month milestones.

2.Incentive to ASHA for follow up of SNCU discharge babies and for follow up of LBW babies 

Add ASHA Incentive of ₹200 per case for following up on SNCU discharge babies. (see BRD section 3.5.10- Font in Orange)

• New Fields to Capture Discharge Details

  • Field: “Baby Discharged from SNCU” → Options: Yes/No
  • If Yes is selected, add:
    • Field: “Date of Discharge” (Mandatory)

3.Incentive for National Deworming Day for mobilising out of school children

Add ASHA Incentive for National Deworming Day for mobilizing out of school children Rs.100 per ASHA Per round 3.1.1.1.6 FMR Code(see below, under Disease Control Module :Sub Module: Deworming- Font in Orange)

Link to ASHA Incentives Claim Form :  ASHA Incentives.xlsx

3.6 Find ABHA

To find ABHA Number of beneficiary by search using Mobile Number
Search may result multiple ABHA Numbers linked to the Mobile Number
Select the Name and proceed to get other details
Proceed to save the ABHA Number of selected beneficiary.

There should be one Radio Button with below options:
1. Search ABHA
2. Create ABHA

Steps to Find ABHA number using Mobile number

1. API: 'v3/profile/account/abha/search'
2. This above New V3 API would provide the list of associated ABHA IDs mapped with a particular mobile number.
3. API Input: enterer Mobile number in API body which will return list of mapped ABHA numbers.
4. API Output: Masked ABHA numbers with personal info i.e. Name and Gender.
5. You need to select the ABHA ID by providing the respective index from the list of ABHAs.
6. Then there is option to fetch the profile details based on the OTP sent to registered mobile number of the ABHA holder.
7. You will get user token once the OTP is verified successfully, and the token can be used to performed further operations.

Refer to this Jira ticker: FLW-153 - Getting issue details... STATUS

3.7 Implement API for Micro Birth Plan Data Integration

This below table is only for the reference of metadata used for creating API, since this screen/ form is currently available in the Application.

Refer to these Jira tickets:

FLW-179 - Getting issue details... STATUS

AMM-1230 - Getting issue details... STATUS

3.8 ASHA's Profile

Purpose

To create a comprehensive ASHA Worker Profile management system, enabling the collection and management of personal and family data. This will ensure that all necessary information related to the ASHA workers, their family members, and village details is accurately recorded and synced with the server.

Hamburger Menu Update

• A new Button called ASHA Profile will be added in the hamburger menu.
• When the user clicks on the ASHA Profile menu item, they will be redirected to the ASHA Profile Screen.

ASHA Profile

• The ASHA Profile Screen will display the following details about the ASHA worker:

  • Name of the ASHA worker
  • Village the ASHA worker belongs to
  • Employee ID (assigned to the ASHA worker)
  • Contact Information (mobile number, alternate mobile number)
  • Family Details (e.g., husband's name, number of children, spouse information)
  • Bank Details (e.g. Bank account, IFSC)
  • Name & Contact Information (e.g. CHO, ANM, AWW)

  
  

• Edit Profile Option:
  A Edit Profile will be available on the profile screen. Clicking this will redirect the user to the Edit Profile Screen.

Edit ASHA Profile

• The Edit ASHA Profile Screen will allow the ASHA worker to modify their details. The fields available for editing will include:

  • Name
  • Village
  • Employee ID
  • Husband's Name
  • Number of Children
  • Spouse Information
  • Bank Details
  • Name & Contact Information

• Save Changes:
  A Save button will be available to save any changes made to the profile. Once the save action is triggered, the updated information should be stored and displayed on the View Profile screen.

• Allow add, edit and view of the ASHA’s photo in the placeholder. 

Refer to this Jira ticket: FLW-175 - Getting issue details... STATUS

Mockup

This below table is for the reference of data fields used in this screen/ form and metadata used for creating API.

Note: 

3.9 Dashboard KPIs for ABHA and RCH Tracking

Purpose:

As part of enhancing the existing dashboard, introducing new Key Performance Indicator (KPIs) by displaying actionable insights for ABHA Generation and RCH ID Count, allowing users to track progress effectively. Introduce filters in the All Beneficiaries and Pregnant Women (PW) sections for better sorting of records with ABHA and RCH IDs. Additionally, enable export functionality for beneficiaries with ABHA to Excel, ensuring streamlined management and accessibility of data.

Enhance the dashboard and beneficiary management features by:

1. Displaying ABHA Generated Count and RCH ID Count as icons on the dashboard, with line listings for detailed insights.
2. Adding filters in the All Beneficiaries and Pregnant Women (PW) sections to sort beneficiaries with ABHA and RCH IDs.
3. Providing the ability to export ABHA beneficiary lists to Excel for easy sharing and analysis.

Refer to this Jira ticket: FLW-176 - Getting issue details... STATUS

3.10 ASHA's Non-Follow-Up cases

Purpose:
Highlight the beneficiaries (Pregnant Women, Eligible Couples) who have not been visited in the last three months. This helps ASHA workers quickly identify and prioritize these beneficiaries for follow-up, ensuring timely care and interventions.

Action Plan for the Flagging Feature:

1. Dashboard Changes

   • Add an indicator labeled "No Visit in Last 3 Months" under relevant sections (ANC, PNC, EC).
   • Clicking the indicator will navigate to a line listing of flagged beneficiaries.

2. Filter Implementation

   • Use last visit date and compare it with the current date.
   • Include records only from the current year to avoid old entries.

3. Logic for Flagging

   • If the gap between the last visit date and the current date is greater than three months, flag the beneficiary.
   • Ensure the system considers only valid and current records to avoid redundant flags.

Refer to this Jira ticket: FLW-177 - Getting issue details... STATUS

3.11 Identify and track missed period cases

Purpose

To introduce a system that records the Last Menstrual Period (LMP) date during the registration of eligible couples and ensures proper tracking of women who have missed their periods. This system will help in early identification and intervention for possible pregnancies.

Action Plan

1. LMP Date Field:
   A new date field will be added to the Eligible Couple Registration and Eligible Tracking screens to record the LMP date at the time of registration. This will allow better monitoring of the menstrual cycle for eligible couples.

2. Dashboard Indicator:

   • A count of women who have missed their periods will be displayed on the Dashboard.
   • A separate line listing will provide detailed information about these women for further action.
   • Missed periods will be determined based on the LMP date and the system's predefined cycle tracking logic.

Refer to this Jira ticket: FLW-178 - Getting issue details... STATUS

3.12 Disease Control Module

Purpose:

The Disease Control Module is designed to facilitate the identification, tracking, and management of infectious diseases in the village community. This module enhances early detection through a structured approach. It ensures real-time case monitoring, to reduce the disease burden in communities.

• A new Disease Control Module should be available on the Home Screen.
• The module should contain submodules for different diseases.
• Each submodule should include a household line listing.
• Under the household line listing, there should be a family member line listing.
• This structure should be consistent across all modules.

This module includes following sub-modules for specific diseases

1. Malaria
2. Kala Azar
3. AES/JE (Acute Encephalitis Syndrome/ Japanese Encephalitis)
4. Filaria
5. Leprosy
6. Deworming 

Refer to this Jira ticket: FLW-48 - Getting issue details... STATUS

3.12.1 Malaria Module

This sub-module enables the identification and management of malaria cases at the village community level. It includes household search, auto-populated individual details, malaria case management with symptoms tracking, referral and treatment workflow, and lab test confirmation

• When selecting a household, a toggle button should be available at the top of the family member listing.
• When the toggle is ON, a table should appear showing:
  • Date
  • Rounds
  • Submit button
• Below the table, a history section should display previous IRS rounds in a separate table, including:
  • Serial number
  • Date
  • Number of rounds
• IRS rounds should be tracked yearly (frequency to be decided).

3.12.2 Kala Azar Module

The Kala Azar sub-module focuses on early detection, treatment and tracking of Kala Azar cases at the village community level. It ensures accurate case status updates, referral options, treatment initiation, and structured follow-up at different points of the treatment cycle.

3.12.3 AES/JE

This sub-module facilitates the tracking and management of AES/JE cases through household searches, individual case tracking, referral management, and status updates to ensure effective case monitoring.

3.12.4 Filaria Module

The Filaria sub-module tracks filariasis cases by capturing household and individual details, home visit dates, affected body parts, medication distribution under the Mass Drug Administration (MDA) program, and any reported side effects of treatment

3.12.5 Leprosy Module

This sub-module supports leprosy screening, detection, and follow-up at the village community level, screening status, referral information, leprosy type classification, and ongoing treatment follow-up to ensure continuous patient care.

3.12.6 Deworming

This Sub-module supports deworming of children at the community level, ensuring the coverage of out-of-school children through ASHA-led mobilization. It tracks deworming status, location of administration (school/home visit), age group eligibility, ensuring proper monitoring of the deworming process.

Add ASHA Incentive for National Deworming Day for mobilizing out of school children Rs.100 per ASHA Per round 3.1.1.1.6 FMR Code

3.13 File Upload Feature

Implement File Upload Feature for MCP Card and Birth Certificate

This feature allows users to upload files in two key scenarios—MCP Card uploads during ANC visits and Birth Certificate uploads during child registration.

1. MCP Card Uploads (ANC Module):
   • Allows ASHA workers to upload the Mother and Child Protection (MCP) Card during any ANC visit.
   • The system ensures that only the latest uploaded version is retained, replacing older versions.
   • Users are provided with an upload button, and an indicator icon or text confirms successful uploads.
   • Uploaded MCP cards can be viewed via a dedicated view button, and acceptable file types include JPG, PNG, and PDF.
   • Positioning: The "Upload MCP Card" button must be positioned below the ANC Period field (refer to mockup for better understanding.)
2. Birth Certificate Uploads (Child Registration Module):
   • Enables uploading of the child's birth certificate during registration or in later edits.
   • Both front and back sides of the certificate can be uploaded, and only the latest version is retained.
   • The system includes an upload button and a view button for accessing the most recent certificate.
   • Accepted file formats are JPG, PNG, and PDF, with a file size limit of 5 MB.
   • Positioning: The "Upload Birth Certificate" button must be positioned below the Date of Birth field (refer to mockup for better understanding.)
3. File Overwrite Logic:
   • Both MCP Card and Birth Certificate uploads follow a single-file overwrite policy, ensuring only the most recent upload is displayed.
   • This prevents clutter and avoids managing multiple files for the same document.

Refer to this Jira ticket: FLW-174 - Getting issue details... STATUS

3.13.1 Upload MCP Card

MOCKUP for MCP CARD UPLOAD

MCP Card Related Fields (Under ANC Module)

3.13.1 Upload Birth Certificate

Mockup for Birth Certificate upload (Under Child Registration Module)

 

Birth Certificate Related Fields (Under Child Registration Module)

3.14 Help Module with User Guide and Video Tutorials

The Help Module assists ASHA workers by providing comprehensive guidance on application functionalities through a user-friendly interface.

Help Module

The Help Module should be accessible via the hamburger menu

3.14.1 Video Tutorials

• • A sub section for accessing video tutorials should be available under Help Module.
  • Videos must play offline to ensure accessibility without internet connectivity.

3.14.2 User Guide

• • A sub section for accessing the user manual in the form of PDF format should be available under the Help Module.
  • The PDF manual will be pre-uploaded and available for offline use. 
• Refer to this Jira ticket: FLW-39 - Getting issue details... STATUS

 Mockup

3.15 ABHA Number creation using Biometrics

Purpose

Alternatively ABHA number can be created using the Fingerprint and Face authentication methods, these both methods are used to securely verify an individual’s identity for creating an ABHA number. These authentication methods helps and streamlines the ABHA number creation process by offering a simple, fast, and secure way to verify an individual's identity without OTP process.

3.15.1 Create ABHA using Fingerprint authentication method

To create ABHA using Fingerprint authentication method, optical fingerprint scanner device is required and device should be Aadhaar registered device (RD Device).

In this method, using fingerprint scanner device capture fingerprint of the beneficiary and processes for Aadhaar authentication.

This RD Service returns an encrypted PID block containing signed biometrics.

The PID can be then passed through the API mentioned below. 

This API creates an ABHA account using fingerprint:
V3 URL: {{base_url}}/v3/enrollment/enrol/byAadhaar

Steps to Create ABHA number:

1. First connect the fingerprint scanner device to mobile device
2. On the beneficiary card, click on 'Create ABHA' and navigate to the below mockup screen
3. In select mode dropdown, select "Fingerprint"
4. Enter Aadhaar number with Aadhaar consent and capture fingerprint on the scanner device
5. then processes for authentication as per the API provided
6. then finally on successful authentication and after ABHA is created, print number on the beneficiary card

Mockup screen

3.15.2 Create ABHA using Face authentication method

To create ABHA using Face authentication method, a third-party app named as 'Aadhaar RD service' should be installed on the mobile device and Aadhaar RD service App with WADH key. 

In this method, using Aadhaar RD service App capture face of the beneficiary and processes for Aadhaar authentication.

This RD Service returns an encrypted PID block containing signed biometrics.

The PID can be then passed through the API mentioned below. 

This API creates an ABHA account using FaceAuth:
V3 URL: {{base_url}}/v3/enrollment/enrol/byAadhaar

Steps to Create ABHA number:

1. First mobile device should be installed with 'Aadhaar RD service' App and configure FLW App and allow permission to call Aadhaar RD service App
2. On the beneficiary card, click on 'Create ABHA' and navigate to the below mockup screen
3. In select mode dropdown, select "FaceAuth"
4. then redirected to the Aadhaar RD service App and capture face; If this application is not installed in device, then user should be redirected to google play store to download the RD service App
5. Enter Aadhaar number with Aadhaar consent 
6. then processes for authentication as per the API provided
7. then finally on successful authentication and after ABHA is created, print number on the beneficiary card

Mockup screen