Customization of Registration Page

Goals

The project goal is to develop and implement a configurable registration page within the AMRIT platform that accommodates the unique data collection requirements for different service lines, specifically targeting MMU (Mobile Medical Unit), HWC (Health and Wellness Center), and telemedicine. The primary objective is to create a flexible and easily customizable framework that allows administrators to modify and set up fields on the user interface (UI) based on the specific needs of each project within these service lines.

Background and strategic fit

Currently   the system lacks the flexibility needed to accommodate the unique requirements of different service lines (MMU, HWC, and Telemedicine) and projects. Challenges such as the inability to customize fields based on service line and project specifications, the need for streamlined data collection, and the desire for a user-friendly interface have been identified. The document aims to address these issues by proposing comprehensive functionalities and customization options for the registration page.

Assumptions

User Access and Permissions:

Within the framework of our system, a robust role-based access control mechanism is assumed to be in place. This security measure ensures that only authorized personnel possess the requisite privileges to access both the Admin Module and the User login page. By strictly defining and assigning roles, we guarantee that users are granted access only to the functionalities aligned with their specific responsibilities. This deliberate approach to access control enhances the overall security posture of our system, safeguarding sensitive areas and reinforcing confidentiality. As a result, the integrity and confidentiality of the Admin Module and User login page are preserved, promoting a secure and controlled environment for system interactions

Platform Compatibility:

The document assumes that the HWC, MMU, and Telemedicine applications will be developed on a platform that supports the required customization features outlined in the document.

Data Privacy and Security:

It is assumed that the development and implementation of the applications will adhere to relevant data privacy and security standards and regulations. Any sensitive information collected will be handled securely.

Development Environment:

The development team is assumed to have the necessary tools, software, and infrastructure to implement the customizations specified in the document.

Requirements

User interaction and design

2.3 Admin Module

 2.3.1 Add Project customization section in Admin module.

Add a dedicated "Project Customization Master" section within the Activities tab in Admin Module 

Below is the screenshot for the reference

After clicking on “Project Customization Master” the below mentioned fields should appear in the next screen which are

• State
• Project
• Service line
• District
• Block

Add Save and cancel button in Project customization Master

This save and cancel button  should support customization changes and the configuration changes

For Example :- In Personal information ,Location Information and Other Information if any fields are checked and unchecked and if any new fields are added then this save button should work and it should should have option to cancel those changes in the fields .

2.3.2 Enable Mandatory and Non-Mandatory selection check box in Admin Module

In Admin Module Fields should have option to enable or disable and it should also have option to select the mandatory or non-mandatory based on the specific project requirement, by using check-box option in admin module.

Post selecting the service line, project Name and state ,District and Block as outlined in section 2.3.2 the following tabs should appear in the form of header in the next screen which are

• Personal Information
• Location Information
• Other Information

Note:-All the configuration of Personal Information ,Location Information and Other Information should be done at the project level and if there is any additional change required then configuration will be done at the lower level which is block level .

Add New Field

In the context of Personal Information, Location Information, and other Information, it is imperative to incorporate a flexible system that allows Admin to add new fields. These additional fields should be project-specific, district-specific, or block-specific, catering to the unique requirements of each. This dynamic feature ensures adaptability and customization, empowering users to tailor the information collection process to the specific needs of their projects, districts, or blocks."

Personal Information

After selecting "Personal Information," the following fields should be displayed as checkboxes in Admin page .

Kindly find the sample screenshot in which check box is required for all these fields

Location Information

After selecting "Location Information," the following fields should be displayed as checkboxes.

Kindly find the sample screenshot in which check box is required for all these fields

Other Information

After clicking “other Information” the following fields should be displayed as check box

• Generate ABHA should show same as currently displaying on HWC application as an independent activity.

Kindly find the sample screenshot in which check box is required for all these fields

Note :-In Registration Module there is a field called Father’s Name under Other Information and the same field label  has to be changed to Fathers Name /Husband Name and that should be configured from Admin Module and these changes should happen in HWC ,Telemedicine and MMU Application as per the above screenshot  .

Below is the screenshot where the changes should take place

After adding checkbox of selecting Mandatory and Non-Mandatory the same selection should reflect in Registration page page of HWC, Telemedicine and MMU Application

For e.g. – If we need make Literacy status on Personal information page as Mandatory, then this can be customized from Admin Module to display on UI page.

Below is the screenshot for the reference.

Note :- All the configurations done on the Registration page should be done on the District level and Block level

For example:- If there is an additional field required such as Literacy in the Baksa block then after selecting Baksa block Literacy should be added

2.3.3 Enable Search Bar before registration

Need to add search option before going on the registration. Before Landing to the registration page, Mobile

Number /Beneficiary Id/ABHA Number search option should be made available to display the existing beneficiaries linked to searched mobile no, User can select the existing beneficiary or click on New Registration.

If the existing Beneficiary details are not available with Normal search  then the Advance search option should be made available to search the Beneficiary details and below is the screenshot for the reference

2.3.4 Customization Personal Information, Location Information and Other Information

2.3.4.1. Page section placement need (Header position) to change from current vertical placement to Horizontal placement

1. Personal Information
2. Location Information
3. Other Information

e.g., Personal information, Location Information and other information should appear like how it appears in Nurse module for History, Vitals and screening and kindly find the screenshot for the reference.

2.3.4.2 In personal information change the Label "Last Name/Sur Name" to Last Name

The term "Sur Name" may introduce some ambiguity as it's less standard in certain English-speaking contexts. Eliminating potential confusion by using the well-established "Last Name" can enhance the accuracy of the information provided.

Kindly find the screenshot for the reference where the changes has to be made and it should be applicable for all the service lines

2.3.4.3 Remove “Deactivate Mandatory Fields in HWC Application

Since the selection of Mandatory and Non-Mandatory Fields should be customized from the admin. The selection of Mandatory and Non-Mandatory Fields should be removed from the HWC Application

Below is the screenshot for the reference

2.3.4.4 Remove check box in “Contact number” field from HWC, Telemedicine as well as MMU Application and Remove checkbox in “Occupation” field from MMU Application

Remove the checkbox in the "Contact number" field from HWC, Telemedicine, and MMU Application, as well as remove the checkbox in the "Occupation" field from the MMU Application.

Below is the screenshot for the reference

Contact Number field

2.4 Changes in Application

2.4.1 Removal of Edit location  from Location information section

To optimize and simplify the user interface, we propose the removal o "Edit Location" from the "Location Information" section. The decision to implement this change is driven by the goal to enhance user experience and reduce unnecessary manual inputs.

2.4.2 Need to remove Aadhar number from Government ID Field in “Other Information section”

 Remove “Aadhar number section from Government ID Field in HWC Application as it is no longer used for creating A number . This adjustment is necessary to align the application with the current protocol and ensure accurate data representation.

2.4.3  User Login Mapping

The “state” and “District should be hidden from the MMU Application in the login page

Location will capture automatically, based on the user work location, mapped van ID, Service point

MMU Application

Once the User logs in to MMU Application then location of the user should automatically capture based on the work location of the user ,Mapped van ID as well as the service point

These changes should impact when the user logs in to the MMU Application and “state” and District “should be hidden and rest of the fields will still remain editable

User should be mapped with Telemedicine Application

In Telemedicine application the entire Registration screen should be mapped to all the fields in Registration in the same way the user is mapped to HWC Application and all the fields of state ,District ,Taluk and street should auto populate once the user logs in to telemedicine application .

Kindly find the screenshot of HWC Application for the reference

• Block should be available for Telemedicine and MMU Service lines and user should be mapped with the Block in work location
• Block should patch in the Registration address