...
Anchor_Toc187790140 _Toc187790140
Document Purpose
_Toc187790140 | |
_Toc187790140 |
The purpose of this document is to outline additional draft enhancements. These enhancements aim to improve user experience and ensure data accuracydescribe business requirements related to the enhancements planned for this phase of development in FLW App “SAKHI”.
Anchor_Toc187790141 _Toc187790141
About Piramal Swasthya
_Toc187790141 | |
_Toc187790141 |
...
2.Incentive to ASHA for follow up of SNCU discharge babies and for follow up of LBW babies
Anchor | ||||
---|---|---|---|---|
|
...
Find ABHA Number using Mobile Number and Aadhaar Number
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.
...
- API: 'v3/profile/account/abha/search'
- This above New V3 API would provide the list of associated ABHA IDs mapped with a particular mobile number.
- API Input: enterer Mobile number in API body which will return list of mapped ABHA numbers.
- API Output: Masked ABHA numbers with personal info i.e. Name and Gender.
- You need to select the ABHA ID by providing the respective index from the list of ABHAs.
- Then there is option to fetch the profile details based on the OTP sent to registered mobile number of the ABHA holder.
- You will get user token once the OTP is verified successfully, and the token can be used to performed further operations.[FLW-153] Find ABHA Number using Mobile Number and Aadhaar Number - Jira
Anchor | ||||
---|---|---|---|---|
|
...
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. FLW-179 - Implement API for Micro Birth Plan Data Integration
Name of Data Field | Field Type | Field Type | Validation/ Logic/ Condition |
Name of the PW | Auto-populate | ||
Age | Auto-populate | ||
Contact No. 1 Contact No. 2 | Text Box |
Should Not accept all same digits | |
SC/HWC/TG Hosp | Text Box |
All letter should be in caps | |
Block | Text Box |
All letter should be in caps | |
Husband’s Name | Auto-Populate | ||
Nearest SC/HWC | Text Box |
All letter should be in caps | |
Nearest 24*7 PHC | Text Box |
All letter should be in caps | |
Nearest FRU | Text Box |
All letter should be in caps | |
Nearest USG centre | Text Box |
All letters should be in caps | |
Blood Group | Spinner | Choose:
| Auto Fill if available OR Select form Spinner |
Blood donors identified | Text Box |
|
All letter should be in caps |
Birth Companion | Text Box |
|
All letter should be in caps |
Person who will take care of Children, if any when the PW is admitted for delivery | Text Box |
|
All letter should be in caps |
Name and Contact number of VHSND/Community member for support during emergency | Text Box |
|
All letter should be in caps |
Mode of transportation in case of labor Pain | Text Box |
|
All letter should be in caps |
Submit | Button |
| Once submitted, change the Color of button “Micro Birth Plan” to Orange on the Card |
...
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.ASHA PHOTO- Allow uploading and displaying of the ASHA worker’s photo in the placeholder. FLW-175 - ASHA Worker Profile Management System
Mockup
Name of Data Field | Field Type | Field Type | Validation/ Logic/ Condition |
Name | Text Box | Auto-Populate | |
Village | Text Box | Auto-Populate | |
User ID | Text Box | Auto-Populate | |
DOB | Text Box | Auto-Populate | |
Age | Text Box | Auto-calculated from Date of Birth. | |
Mobile Number | Text Box | Auto-Populate | |
Alternate Mobile Number | Text Box |
Should Not accept all same digits | |
Father/Spouse Name | Radio Button | Choose between Father or Spouse (Radio buttons for selecting either). | |
Date of joining | Text Box | Auto-Populate | |
Bank Account | Text Box | Accepts only numeric values (integer). Length should be between 9-18 digits depending on bank. No special characters allowed. | |
IFSC | Text Box | Non-mandatory Alphanumeric characters (typically 11 characters); Format: 4 letters followed by 7 digits (e.g., | |
Population Covered under ASHA | Text Box | Mandatory Accepts only numeric values. Should be a positive integer. | |
CHO Name | Text Box | Mandatory Accepts alphabetic characters and spaces only. | |
Mobile no. of CHO | Text Box | Accept numeric (integer) value only; Accepts 10 digits only; Should start with 6, 7, 8, or 9; Cannot start with 0; Should not accept all same digits. | |
Name of AWW | Text Box | Mandatory Accepts alphabetic characters and spaces only. | |
Mobile no. AWW | Text Box | Accept numeric (integer) value only; Accepts 10 digits only; Should start with 6, 7, 8, or 9; Cannot start with 0; Should not accept all same digits | |
Name of ANM1 | Text Box | Mandatory Accepts alphabetic characters and spaces only. | |
Mobile number of ANM1 | Text Box | Accept numeric (integer) value only; Accepts 10 digits only; Should start with 6, 7, 8, or 9; Cannot start with 0; Should not accept all same digits. | |
Name of ANM2 | Text Box | Mandatory Accepts alphabetic characters and spaces only. | |
Mobile number of ANM2 | Text Box | Accept numeric (integer) value only; Accepts 10 digits only; Should start with 6, 7, 8, or 9; Cannot start with 0; Should not accept all same digits. | |
ABHA number | Text Box | Accept a 14-digit alphanumeric value only. | |
ASHA Household Registration | Text Box | Alphanumeric characters. Should follow a specific format if defined for the household registration number. | |
ASHA Family Member | Text Box | Accepts alphabetic characters, numeric, and spaces. Should list the names and relationships of family members | |
Save | Button | Save any changes made to the profile |
...
- Displaying ABHA Generated Count and RCH ID Count as icons on the dashboard, with line listings for detailed insights.
- Adding filters in the All Beneficiaries and Pregnant Women (PW) sections to sort beneficiaries with ABHA and RCH IDs.
- Providing the ability to export ABHA beneficiary lists to Excel for easy sharing and analysis.FLW-176 - Dashboard Enhancement for ABHA and RCH Count Tracking
Name of Data Field | Field Type | Field Type | Validation/ Logic/ Condition |
ABHA Generation Icon | Label |
|
|
RCH ID Icon | Label |
|
|
Pregnant Women Line Listing | Filter |
|
|
Beneficiary Line Listing Filter | Filter |
|
|
Export ABHA | Button |
|
|
...
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.
Filter Implementation
- Use last visit date and compare it with the current date.
- Include records only from the current year to avoid old entries.
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.[FLW-177] Flagging Logic for LMP and Visit Details - Jira
Name of Data Field | Field Type | Field Type | Validation/ Logic/ Condition |
Flag (for No Visit in Last 3 Months) | Flag (Boolean) |
|
|
No Visit (3Months) | Icon |
|
|
Anchor | ||||
---|---|---|---|---|
|
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.
...
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.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.FLW-178 - LMP Date Tracking and Missed Period Line Listing
Name of Data Field | Field Type | Value/ Options | Validation/ Logic/ Condition |
LMP Date | Calendar Picker |
| Eligible Couple Registration and Eligible Tracking Section, |
Missed Period Flag | Flag |
| Triggered if the difference between the current date and the LMP date exceeds 35 days. |
Missed Period (Dashboard Indicator) |
| Included it under "Dashboard" Section Displays the count of women with missed periods based on the Missed Period Flag from both "Eligible Couple Registeration" and "Eligible Couple Tracting" Section Provides a list of flagged women with their Names, LMP dates. |