...
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.
Anchor | ||||
---|---|---|---|---|
|
...
Anchor | ||||
---|---|---|---|---|
|
...
Refer to this Jira ticket:
Jira | ||||||
---|---|---|---|---|---|---|
|
Use cases:
- 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.
- Successfully, OTP verified records
...
- should sync to server and indicate with green
...
- color 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
...
- color 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
...
- color 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.
...
Name of Data Field | Field Type | Value/ Options | Validation/ Logic/ Condition |
Mobile Number (for taking consent using OTP) | Textbox |
| |
Whose Mobile Number | Dropdown Values |
|
|
Send OTP | Button |
| |
Resend OTP | Button |
| |
OTP Verification | Textbox | A) Online Mode
| |
...
- 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.
Upload MCP Card
MOCKUP for MCP CARD UPLOADUpload MCP Card
MCP Card Related Fields (Under ANC Module)
Name of Data Field | Field Type | Field Type | Validation/ Logic/ Condition |
MCP card Upload | Button |
|
|
File Overwrite Logic | System |
|
|
View Uploads | Button |
|
|
Allowed File Types/File Size |
|
|
Upload Birth Certificate
MOCKUP for Birth Certificate UPLOAD (Under Child Registration Module)Upload Birth Certificate
Birth Certificate Related Fields (Under Child Registration Module)
...
- 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.
Micro Birth Plan
This below table is only for the reference of metadata used for creating API, since this screen/ form is currently available in the Application.
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 |