...
- 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.[
Refer to this Jira ticker:
Jira | ||||||
---|---|---|---|---|---|---|
|
...
Anchor | ||||
---|---|---|---|---|
|
...
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 |
| |
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 |
| |
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 |
|
|
Person who will take care of Children, if any when the PW is admitted for delivery | Text Box |
|
|
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 |
|
|
Anchor | ||||
---|---|---|---|---|
|
...
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 uploading add, edit and displaying view of the ASHA worker’s ASHA’s photo in the placeholder.
Refer to this Jira ticket: Jira server Jira serverId ec79ddd2-df88-3090-9639-c1c836245878 key FLW-175
...
Mockup
This below table is for the reference of data fields used in this screen/ form and metadata used for creating API.
Name of Data Field | Field Type | Field Type | Validation/ Logic/ Condition |
ASHA 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 |
| |
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 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
Refer to this Jira ticket: Jira server Jira serverId ec79ddd2-df88-3090-9639-c1c836245878 key FLW-176
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.[
Refer to this Jira ticket:
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 |
|
|
...
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.
Refer to this Jira ticket:
Jira | ||||||
---|---|---|---|---|---|---|
|
...
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) | Icon |
| Included it under "Dashboard" Section Displays the count of women with missed periods based on the Missed Period Flag from both "Eligible Couple Registration" and "Eligible Couple Tracking" Section Provides a list of flagged women with their Names, LMP dates. |
...
Name of Data Field | Field Type | Value/ Options | Validation/ Logic/ Condition |
House Hold No. | Numeric |
| Search by household number. |
Head of Family Member Name | Text Box |
|
|
Mobile No. | Numeric |
|
|
Name | Text Box |
| Auto-populated from "Enumeration FM" First Name, Middle Name, Last Name. |
Father's Name / Husband Name | Text Box |
| If Gender = Female and Marital Status = Married, auto-populate from Spouse Name. If Gender = Male, auto-populate from Father’s Name. |
Age | Text Box |
| Auto-populated from "Enumeration FM" |
Gender | Text Box |
| Auto-populated from "Enumeration FM" |
Mobile No. | Text Box |
| Auto-populated from "Enumeration FM" |
ABHA ID | Text Box |
| Auto-populated from "Enumeration FM" |
Case Date | Text Box |
| Auto-populated as Today's Date (Non-editable). |
Case Status | Drop Down | Option: 1.Suspected, 2. Confirmed, 3. Not Confirmed, 4. Treatment Given. | First Entry: Only "Suspected" can be selected. |
Symptoms | Text Box |
| Fever more than two weeks, Flu-like illness, Shaking chills, Headache, Muscle aches, Tiredness, Nausea, Vomiting, Diarrhea |
Malaria Case Count (Variable) | Text Box |
| For Lab Test: |
Referred To | Drop Down |
| Options: Primary Health Centre, Community Health Centre, District Hospital, Medical College and Hospital, Referral Hospital, Other Private Hospital, Other, None. |
Other | Text Box |
| Required only if "Referred To" = "Other". |
Malaria Case Status Date | Calendar Picker |
| Auto-populated when status is updated. |
Remarks | Text Box |
| Optional field for additional notes. |
...
Name of Data Field | Field Type | Value/ Options | Validation/ Logic/ Condition |
House Hold No. | Numeric |
| Search by household number. |
Head of Family Member Name | Text Box |
|
|
Mobile No. | Numeric |
|
|
Data Field | Text Box | ||
Name | Text Box | Auto-populated from "Enumeration FM" (First, Middle, Last Name) | |
Father's/Husband's Name | Text Box | "If Gender = Female and Marital Status = Married, auto-populate from 'Spouse Name'. If Gender = Male, auto-populate from 'Father Name'" | |
Age | Numeric | Auto-populated from "Enumeration FM" | |
Gender | Text Box | Auto-populated from "Enumeration FM" | |
Type of House | Text Box | Auto-populated from "Enumeration HH" | |
Caste | Text Box | Auto-populated from "Enumeration HH" | |
Mobile No. | Numeric | Auto-populated from "Enumeration FM" | |
ABHA ID | Numeric | Auto-populated from "Enumeration FM" | |
Date | Numeric | Display Today's Date and should be non-editable | |
Kala Azar Case Status | Radio Button | Suspected, Confirmed, Not Confirmed, Treatment Started First time user will select "Suspected" option only and from second time the user will select either "Confirmed" or "Not Confirmed". The system will display the "Treatment Started" only if the previous status was "Confirmed". Push the value of variable Kala Azar Case to ASHWIN - Dawa Papatra Define variable Kala Azar Case with default value = 0 and for every unique confirmed case in the current month Kala Azar Case = Kala Azar Case +1 | |
Referred To | Drop Down | Primary Health Centre, Community Health Centre, District Hospital, Other Private Hospital, Medical College and Hospital, Referral Hospital, Other, None Single Select Radio Button | |
Other | Text Box | If "Referred To" = "Other" | |
Kala Azar Case Status Date | Calendar |
| |
Follow Up Point | Radio Button | If "Kala Azar Case" = "Treatment Started" If "Status" not equal to "Dead" in previous "Follow Up point" 1, 2, 3, 4, 5, 6 Disabled the option (1,2,3,4,5,6) once selected | |
Follow Up Date | Calendar | If "Kala Azar Case" = "Treatment Started" If "Status" not equal to "Dead" in previous "Follow Up point" | |
Status | Radio Button | If "Status" not equal to "Dead" in previous "Follow Up point" Recovering, Cured, Dead, Recurrance Recurrence of Symptoms, Other | |
Other | Text Box | If "Status" = "Other" | |
Remarks | Text Box | If "Kala Azar Case" = "Treatment Started" If "Status" not equal to "Dead" in previous "Follow Up point" |
...
Name of Data Field | Field Type | Value/ Options | Validation/ Logic/ Condition |
House Hold No. | Numeric |
| Search by household number. |
Head of Family Member Name | Text Box |
|
|
Mobile No. | Numeric |
|
|
Is there a "सुअर बाराह" near the house ? | Radio Button | Value/Options | Yes, No Single Select Radio Button |
Name | Text Box | - | Auto-populated from "Enumeration FM" (First, Middle, Last Name) |
Father's/Husband's Name | Text Box | - | "If Gender = Female and Marital Status = Married, auto-populate from 'Spouse Name'. If Gender = Male, auto-populate from 'Father Name'" |
Age | Numeric | - | Auto-populated from "Enumeration FM" |
Gender | Text Box | - | Auto-populated from "Enumeration FM" |
Type of House | Text Box | - | Auto-populated from "Enumeration HH" |
Caste | Text Box | - | Auto-populated from "Enumeration HH" |
Mobile No. | Numeric | - | Auto-populated from "Enumeration FM" |
ABHA ID | Numeric | - | Auto-populated from "Enumeration FM" |
Date | Numeric | Display Today's Date and should be non-editable | |
AES / JE Case Status | Radio Button | Suspected, Confirmed, Not Confirmed, Treatment Started First time user will select "Suspected" option only and from second time the user will select either "Confirmed" or "Not Confirmed". The system will display the "Treatment Started" only if the previous status was "Confirmed". Push the value of variable AES / JE to ASHWIN - Dawa Papatra Define variable Kala Azar Case with default value = 0 and for every unique confirmed case in the current month Kala Azar Case = Kala Azar Case +1 | |
Referred To | Drop Down | Primary Health Centre, Community Health Centre, District Hospital, Other Private Hospital, Medical College and HosptalHospital, Referral Hospital, Other, None Single Select Radio Button | |
Other | Text Box | If "Referred To" = "Other" | |
AES / JE Case Status Date | Calendar | Mandatory | |
Follow Up Point | Radio Button | If "Kala Azar Case" = "Treatment Started" If "Status" not equal to "Dead" in previous "Follow Up point" 1, 2, 3, 4, 5, 6 Disabled the option (1,2,3,4,5,6) once selected | |
Follow Up Date | Calendar | If "Kala Azar Case" = "Treatment Started" If "Status" not equal to "Dead" in previous "Follow Up point" | |
Status | Radio Button | If "Status" not equal to "Dead" in previous "Follow Up point" Recovering, Cured, Dead, Recurrence of Symptoms, Other | |
Other | Text Box | If "Status" = "Other" | |
...
- 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.)
- 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.)
- 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. [FLW-174] Implement File Upload Feature for MCP Card and Birth Certificate - Jira
Refer to this Jira ticket:
Jira | ||||||
---|---|---|---|---|---|---|
|
3.13.1 Upload MCP Card
MOCKUP for MCP CARD UPLOAD
...
3.13.1 Upload Birth Certificate
MOCKUP Mockup for Birth Certificate UPLOAD upload (Under Child Registration Module)
...
- 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:
] Help Module with User Guide and Video Tutorials - JiraJira server Jira serverId ec79ddd2-df88-3090-9639-c1c836245878 key FLW-39
Name of Data Field | Field Type | Field Type | Validation/ Logic/ Condition |
User Guide | Image Button |
| |
Video Tutorial Icon | Image Button |
|
...
Mockup