You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »



Business Requirements Document (BRD)

Date

Version Number

Author

Approved By

Document change reference

12/31/2024

1.0

Shreshtha


Initial draft on following features:

  1. Bulk user registration feature
  2. Beneficiary consent process
  3. ASHA Incentive Claim form




Contents
Introduction
Document Purpose
About Piramal Swasthya
Background
Background of ASHA Concept 
Scope of Work
AMRIT Admin web portal enhancements
Bulk User Registration
FLW App enhancements
Implement Beneficiary Consent process
Beneficiary Consent using OTP approach
Feature: File Upload
Feature: Help Module
ASHA Incentives



Definitions, Acronyms, and Abbreviations

S. No

Term / Acronym / Abbreviation

Full form/ Definition

1

FLW

Frontline Health Workers; i.e. ASHA, ANM and AWW

2

ASHA

Accredited Social Health Activist


Introduction

Document Purpose

The purpose of this document is to outline additional draft enhancements. These enhancements aim to improve user experience and ensure data accuracy.

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.

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.

Background

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.

Scope of Work

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).

Tasks related to AMRIT Admin web portal, related enhancements specified in this Business requirements document.

AMRIT Admin web portal enhancements

Bulk User Registration

Admin Module: Bulk User Registration and Validation Notes
General Flow for Bulk User Registration:

  1. New User Creation:
    • Currently the system supports creating single User account at a time,
    • Bulk user creation simplifies registration for 100+ users by allowing Excel-based upload.
  2. Bulk User Creation Process:
    • Download Template: Users must download a predefined Excel template containing all necessary fields and mandatory fields marked with star ((red star)).

    • Fill Template: Users fill the template with the required data. Mandatory fields must be completed with valid input.
    • Upload Template: The completed template is uploaded back into the system.
    • Validation: System validates each record and:
      • Creates users with valid data.
      • Logs errors for records with invalid/missing data.
    • Feedback:
      • Show success count (e.g., "15 out of 20 users created successfully").
      • Provide an error log file for failed records with reasons for failure

Mockup:



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. 

S No

Name of Data Field

Field Type

Value/ Options

Validation/ Logic/ Condition


1.

Download Bulk User Template

Button


  • Allow user to download a predefined Excel template
  • The structure for the Excel template has two tabs
  • Tab 1: Bulk User Details

    This tab contains the field names listed horizontally as provided in below fields. It serves as the main data entry section, where users will fill out the required information based on the guidelines provided in "Tab 2: Help" Sheet
  • Tab 2: Help

    This tab provides additional guidance, dropdown options, and validation logic for each field in "Tab 1: Bulk User Details". It ensures users understand how to fill out the template correctly and the possible values for each field.


2.

Title

Dropdown

Major,
Madam,
Mr.,
Mrs.,
Ms.,
Dr.,
Baby,
Master,
Capt.,
Prof.,
Col.,
Md.,
Smt.,
Lt.,
Unknown

  • Mandatory
  • Must match one of the predefined dropdown options.


3.

First Name

Text

Any

  • Mandatory
  • Alphabetic characters only; Max length: 50;
  • No special characters or numbers are allowed.


4.

Middle Name

Text

Any

  • Optional
  • Alphabetic characters only; Max length: 50;
  • No special characters or numbers are allowed.

5.

Last Name

Text

Any

  • Mandatory
  • Alphabetic characters only; Max length: 50
  • No special characters or numbers are allowed.

6.

Gender

Dropdown

Female,
Male,
Transgender

  • Mandatory

7.

Contact No.

Numeric


  • Mandatory
  • Must be exactly 10 digits;
  • 10-digit number starting with 6,7, 8, 9 only
  • Numeric only.



8.

Designation

Dropdown

  • Administrator
  • ASHA Counsellor
  • Dean
  • Medical College
  • Director
  • Medical & Health Department
  • Doctor
  • Driver
  • Mandatory

9.

Emergency Contact No.

Numeric


  • Mandatory
  • Must be exactly 10 digits;
  • 10-digit number starting with 6,7, 8, 9 only
  • Numeric only.

10.

Date of Birth

Date

Date Format

  • Mandatory
  • Must follow the format DD/MM/YYYY;
  • Invalid format will be rejected.


11.

Age

Numeric

Any

  • Mandatory
  • Must be exactly 2 digits;
  • Numeric only


12.

Email

Text


  • Mandatory
  • Must be in a valid email format (e.g., user@example.com).



13.

Marital Status

Dropdown

Divorced, Married, Not Applicable, Separated, Unmarried, Widow, Widower



14.

Aadhar No.

Numeric

12-digit number

  • Must be exactly 12 digits
  • Allow Numeric values only.


15.

PAN Card No.

Alphanumeric

Any valid PAN format

  • Must follow valid PAN card format (e.g., ABCDE1234F).
  • Allow Alphanumeric Values only.



16.

Qualification

Dropdown

Graduate, Post Graduate & Above, Secondary, Senior Secondary, Under Graduate


17.

Father's Name

Text

Any

  • Alphabetic characters only; Max length: 50
  • No special characters or numbers.


18.

Mother's Name

Text

Any

  • Alphabetic characters only
  • Max length: 50,
  • No special characters or numbers.


19.

Community

Dropdown

General, SC, ST, BC, OBC, OC, Not given

  • Must match one of the predefined dropdown options.



20.

Religion

Dropdown

Hindu, Muslim, Christian, Sikh, Buddhism, Jainism, Other, Parsi, Not Disclosed

  • Must match one of the predefined dropdown options.


21.

Current Address

Text

Any

  • Mandatory
  • Must include Address Line 1, State, District, and Pin-code; Pin-code must be numeric and 6 digits.


22.

Permanent Address

Text

Any

  • Optional;
  • Must include Address Line 1, State, District, and Pin-code; Pin-code must be numeric and 6 digits.


23.

Date of Joining

Date

DD/MM/YYYY

  • Mandatory
  • Must follow the format DD/MM/YYYY; Invalid format will be rejected.



24.

Upload Template

Button

Upload completed template

  • The completed template must be allowed to Upload, Display Processing bar
  • The system must validate each record
  • Show success count (e.g., "15 out of 20 users created successfully").
  • Display an error msg for failed records with reasons for failure and Serial. No that it is belonging to













FLW App enhancements

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.

Process flow diagram of Sakhi App



Implement Beneficiary Consent process

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.

Use cases:
Successfully OTP verified records, should sync to server and indicate with green colour symbol on beneficiary card as "consent is taken"
Beneficiary records that are not verified with OTP, should not sync to server, should save as draft and indicate with orange colour symbol on beneficiary card to notify "consent is due"
Existing Beneficiary records that are already synced to server, but OTP consent is not verified earlier, should indicate with yellow colour symbol on beneficiary card to notify "record is synced but consent is due"
Beneficiary records should be flag based on the status of consent
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   


Name of Data Field

Field Type

Value/ Options

Validation/ Logic/ Condition

Mobile Number

(for taking consent using OTP)

Textbox


  • Mandatory
  • After entering the Mobile number in the textbox, enable the "Send OTP" button
  • By default, show Mobile Number of Head of Family
  • Should allow to edit Mobile Number
  • Must be exactly 10 digits;
  • 10-digit number starting with 6,7, 8, 9 only
  • Allow only Numbers

Whose Mobile Number

Dropdown Values


If "Other" is selected, enable a text field to specify the relationship (max 50 characters, alphanumeric only).

Send OTP

Button


  • This Button should be in green on right corner below Mobile Number.
  • It should initiate a request to generate OTP & send OTP via SMS to the above mentioned mobile number
  • In case of failed attempts, enable "Resend" OTP button

Resend OTP

Button


  • Regenerate OTP and send to the mobile number

OTP Verification

Textbox


A) Online Mode
1. Head of Family Member Registration:

  • After entering the "Mobile number of the Head of the Family," enable the "Send OTP" button in green on right corner

    2. Family Member Registration:
  • Under "Members," after entering the Contact Number, enable the "Send OTP" button in green.

    3.All Beneficiaries:
  • If OTP verification is pending, display a navigation button to "Verify OTP."

    4.OTP Verification Details
  • Allowed OTP: Numerical codes only, 4 digits long.
  • Verification Process:
  • Verify OTP against the generated code.
  • Set a 15-minute time limit for OTP entry.
  • Valid OTP within timeframe: Display "OTP Verified successfully."
  • Invalid OTP or timeout:
  • Display "Session Expired"
  • ASHA needs to request a new OTP in subsequent visits.
  • Not validated from server: Keep in draft mode

    5.Enable Mode (During Internet Availability)
  • Display a green "Send OTP" button.
  • If no OTP is received, allow editing of the mobile number and resending the OTP.

    C)Offline Mode
    1.New Registration:
  • After entering the mobile number, Disable the "Send OTP" button.
  • Allow form submission and save as draft.
  • On the card, display a "Verify OTP" navigation button beside the contact number in orange.
  • This beneficiary should not sync to the server.
  • Clicking the button opens the consent form in edit mode with no data loss.

    2.Household Submission
  • Do not sync or generate an ID until the Head of Family's consent management is completed and verified..

    D)OTP Verification Status Indicators
    1.Verification Pending: "Orange icon" with text beside the contact number.
    2.Verification Not Done for Existing Records: "Red icon" with text in the right corner of the card. ASHA can recognize this and add the consent for older records
    3.Verification Done: "Green icon" with text.
    Additional Features
  • Auto-Submit: Automatically submit once all OTP digits are entered.
  • Auto-Close: Close the card after OTP verification attempt (successful or unsuccessful).







Feature: File Upload

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.


MOCKUP for MCP CARD UPLOAD
Upload MCP Card
MCP Card Related Fields (Under ANC Module)

Name of Data Field

Field Type

Field Type

Validation/ Logic/ Condition

MCP card Upload

Button

 

  • Allows uploading MCP card during any ANC visit.
  • Only the latest MCP card is retained.
  • Indicates the uploaded status with a visible icon.

File Overwrite Logic

System
Action

 

  • When a new birth certificate is uploaded, the previous file is overwritten.
  • Retain only the latest uploaded version.
  • Display icon or text indicating that the MCP card has been successfully uploaded.

View Uploads

Button

 

  • Displays the latest uploaded MCP card.

Allowed File Types/File Size


 

  • Accept JPG, PNG, and PDF files.
  • Maximum file size of 5 MB per upload.



MOCKUP for Birth Certificate UPLOAD (Under Child Registration Module)
Upload Birth Certificate

Birth Certificate Related Fields (Under Child Registration Module)

Name of Data Field

Field Type

Field Type

Validation/ Logic/ Condition

Birth Certificate Upload

Button


  • User can upload Birth Certificate in Child registration.
  • Enables file upload for the birth certificate during child registration.
  • If not available during initial registration, can be added later during edit.
  • Option to upload both sides (front and back) of the birth certificate.

File Overwrite Logic

System
Action


  • When a new birth certificate is uploaded, the previous file is overwritten.
  • Retains only the latest uploaded version..

View Uploads

Button


  • Displays the latest uploaded MCP card.

Allowed File Types/File Size

System
Action


  • Accept JPG, PNG, and PDF files.
  • Maximum file size of 5 MB per upload.



Feature: Help Module

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

  1. Help Module Access:
    • The Help Module must be accessible via the hamburger icon in the main menu.

a) Video Tutorial Icon:

    • An icon for accessing video tutorials will be available in the Help Module.
    • Videos must play offline to ensure accessibility without internet connectivity.

b) User Manual (PDF):

    • An icon for accessing the PDF-based user manual must be provided in the Help Module.
    • The PDF manual will be pre-uploaded and include detailed guidance on system usage.

      Name of Data Field

      Field Type

      Field Type

      Validation/ Logic/ Condition

      User Guide

      Button


      • Displays a comprehensive user guide covering all key features and functionalities.

      Video Tutorial Icon

      Button


      • Videos must play offline, ensuring accessibility without internet connectivity.

      ASHA Incentives

      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

Feature: Search and Manage ABHA Numbers

To find ABHA Number of beneficiary by search using Mobile Number or Aadhaar 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.
  • No labels