Here are the articles in this section:

• Frontline Worker's App

• Campaign Management Dashboard

• Microplanning

• HCM Admin Console

A digital partner for different users such as registrars, frontline workers, and supervisors, this is an easy-to-use app with offline capability, guided user flows, and analytics support. It simplifies routine tasks, has built-in checks to reduce errors, and provides on-call assistance.

The app enables the following:

• Register new households and individuals.

• Search existing households and individuals

• Update details for existing households and individuals.

• Record service delivery of healthcare interventions to households and individuals for a single round campaign.

• Auto-calculation of resources to be delivered to a household or individuals based on the configured rule.

• Record stock movement for a warehouse-stock received, issued, returned, damaged and lost.

• Stock reconciliation to automatically calculate the stock on hand available in the warehouse.

• Offline reports for viewing all stock transactions and stock counts in the mobile application.

• Register complaints on the mobile app with offline support.

• Search, sort, and filter complaints based on configured parameters.

• Configurable checklists for supervisors for various supervision activities.

• Multi-language support.

• Track GPS coordinates to record locations with offline support.

• Progress bar for monitoring the daily work status of registration and service delivery against the targets assigned.

• Reuse beneficiary data from the registries for future campaigns.

• Web portal for user management.

• In-app notification to prompt users to perform actions that are due.

Click on the links below to learn more about the different features of the app:

• Single Round Campaigns

• Multi-Rounds Campaigns

• Common Functions

• Support Functions

Here are the articles in this section:

• Single Round Campaigns

• Multi-Round Campaigns

• Common Functions

• Support Functions

Public health initiatives intended to address particular health-related concerns within a predetermined timeframe or scope, and in a single round. Click on the link below to learn more:

• Registration & Delivery

This enables frontline workers to register households and individuals using the HCM application.

Key Features

• Register households

• Add/Delete members to/from the households

• Edit household/individual details

• Delete household

• Record delivery of an intervention

User Roles

Using Registration & Delivery

When field and district supervisors navigate to the home screen, the beneficiaries button is visible to them.

On this page, the following actions can be performed:

• You can register a new household only after attempting a search.

• Click on the "Register New Household" button to register a household.

• After the user clicks on "Register New Household", the page navigates to the "Household Location" page.

• The "Administrative Area" is the only mandatory field. "Address Line 1", "Address Line 2", 'Landmark' and "Postal Code" are optional fields.

• Clicking on the 'Next' button will take the user to the "Household Details" page where the number of members living in the household can be registered.

• Clicking the 'Next' button will take the user the "Individual details" screen.

• The first individual added will be the "Head of Household" by default.

• The name, ID type, and ID number fields are mandatory. You can enter the date of birth or their age. The date birth will take precedence over age.

• When the user clicks on the submit button, a popup appears asking for confirmation.

• If the user clicks on ‘Submit’, the household is registered and a confirmation screen is displayed.

• The user can click on the "Back to Search" button for editing the household or register new household fields.

• Click on the open card to navigate to the detailed page of the household.

• There is an "Edit Household" button for editing household details, which navigates the user to the household location screen. The service delivery status is present below the household’s name followed by the administrative area and the number of members.

• There are cards for each member, starting from the household head. The card consists of the ‘Edit’ button for individual-level actions.

• For adding new members to the household, there is the "Add Member" button below the member cards, which navigates the user to the "Individual Details" screen.

• At the bottom, the "Deliver Intervention" button is present which navigates the user to the update delivery screen.

Vector control is pivotal in global efforts to control and eliminate malaria. It is essential for reducing malaria transmission and ultimately halting its spread. Currently, the two primary vector control strategies are long-lasting insecticidal nets (LLINs) and indoor residual spraying (IRS), which together constitute nearly 60% of global investment in malaria control initiatives.

DIGIT HCM for IRS will empower stakeholders involved in the campaign to achieve their objectives seamlessly without disrupting their routine activities. It will facilitate real-time tracking and monitoring of campaign coverage and progress, enabling timely interventions. This will lead to improved campaign reach, enhanced efficiency for campaign workers, and cost savings through better management of inventory and operations.

Using Registration & Delivery for IRS

User Role: Registrar

Home Screen:

This is the home screen for a registrar. You will see the following cards:

1. Beneficiary: For registration and spraying of households

2. Sync Data

3. File Complaint

4. Dashboard: View key metrics and visualisations

Search Households (Reuse of registry)

You can search for the households that are registered from previous campaigns before registering as a New Household. This page has 2 indicators:

1. Number of houses sprayed

2. Number of houses for revisits (closed/refused/ineligible)

There will be 2 filters for the search results:

1. Search by proximity

2. Filter for ‘Revisits’

a. The Revisits filter should also show the count in that filter

The households card will show the following additional information on top of what is already available in the product.

1. Number of pregnant women

2. Number of children

3. Number of rooms

By default, the "Register New Household" should be disabled and should be enabled only upon searching (3 chars minimum).

Household Location

The household details page will capture:

1. The village name (populated based on boundary selection)

2. Landmark (non-mandatory)

3. GPS coordinates and accuracy

There will be an info card that tells you to ensure the village name matches the actual one on the field.

Household Details

Case 1: Reuse of registry

• The date of registration should be as per Today’s date

• The total number of members living in the HH should be populated from the registry and should be editable

• The number of pregnant women in household needs input from the user

• Number of children less than 5 years in HH needs input from the user

• Info card to make sure the calculations are correct

Case 2: New registrations

• The date of registration should be as per Today’s date

• The total number of members living in the household needs input from the user

• The number of pregnant women in a household needs input from the user

• Number of children less than 5 years in household needs input from the user

• Info card to make sure the calculations are correct

Edit/Delete Households

The edit household/delete household options are available on the household details page.

House Details

To capture:

1. Type of structure

2. No.of rooms in the house

The type of structure will have clickable cards that can be toggled to select/deselect.

Each type of structure should be tagged to a status:

• Eligible

• Ineligible

Once you capture the details, click on Next.

Individual Details

Case 1: New registrations

The individual details page will capture:

1. Name of the individual

2. Age

3. Gender

4. Mobile number

Once you capture all the details, click on Next.

Case 2: Reuse registry from previous campaigns/registrations: This page will be skipped.

Summary

This will provide a summary of all data captured so far. Check the details and click on Submit.

Confirmation Screen

It will ask for:

1. Submit

2. Cancel

Click on Submit if the correct details have been captured.

Success/Failure message screen

You will get a success message. You can click "View Household Details" to check the information.

User Role: Spray Operator Home Screen:

You will see the following cards:

1. Beneficiary: For registration and spraying of households

2. Sync Data

3. File Complaint

4. Dashboard: View Key metrics and visualisations

Search Households

You will search for registered households to mark spray details. If a household is not registered and requires to be registered, you should be able to register them by clicking on "Register New Household".

IEC Details

This page captures if the IEC Mobilizer has visited the household or not. If the spray operator is recording data against an existing household, this will be the first screen they should see after searching and selecting the household. If the spray operator is creating a new household, then they will arrive at this screen after the registration flow is complete. Click on 'Yes' or 'No' to record if the IEC Mobilizer has visited the household. Next, click on 'Sprayed' or "Did Not Spray".

Spray Details

If you click on 'Sprayed' in the previous screen, the spray details will be captured, which includes:

• The date of spraying

• Total no.of rooms sprayed

• Type of insecticide used

Check the details and click on Submit.

Success/Failure Screen

You will get a success message.

Spraying Not Done

If you selected "Did Not Spray", then this page should capture

• The date of the visit

• Reason for not spraying

The incompatible structure card should be auto-selected based on the household structure chosen at the registration flow.

Closed Households

The home screen has a separate icon for marking closed households. Clicking on the icon will take you to the Household details screen.

On this screen, the following details can be captured:

1. GPS coordinate

2. Village name

3. Coordinate accuracy

4. Household head name (Optional)

Clicking on Next will take you to the Summary screen.

On the summary screen, the details captured so far should be displayed. If the program allows, then you can scan a voucher and encode the details in the QR code. The voucher can then be affixed on the house for scanning during re-visit. The record created should be labeled with the status as ‘Closed’. Click on Submit.

Success/Failure Screen

You will see the success screen.

On revisits, when the user selects the filter ‘ ‘Closed’, all households with the status as closed should be shown in the results (Within the boundary selected). Opening any card should take the user to the normal flow of registration:

Household location → Household details → Individual details → IEC → Spray/non spray

The status needs to be updated from ‘Closed’ accordingly.

Multi-round campaigns for health initiatives entail registering beneficiaries once, followed by interventions delivered in successive rounds at predefined intervals. Click on the link below to learn more:

• Downloading Beneficiary Data

• Registration & Delivery

This enables distributors to deliver multiple doses for multiple cycles, and record the deliveries for the drugs prescribed for that specific cycle.

Key Features

• Allows a distributor to see the eligible household members for the current cycle under the selected household.

• For each eligible household member, the distributor has two options: Record Delivery and Unable To Deliver.

• A distributor can record the exact quantity delivered for each drug with a delivery comment.

• A distributor can also record if the drugs for the next set of doses in the current cycle are already provided to the beneficiary or not. If the doses for next rounds are already provided, the distributor can mark next doses as 'Delivered' for the next rounds.

User Roles

Steps for Recording Delivery

Step 1

Once the distributor is on the household details page, he/she can see which beneficiary is eligible for drug delivery in the current cycle. Click on "Record Delivery" or "Unable to Deliver":

Step 2

You are taken to the Record Cycle (X) Dose (Y) screen, where you can see the status of drug delivery for all doses for the current and previous cycles (if available). Click on "Record Cycle (X) Dose (Y)" button at the bottom of the screen to record the drug delivery.

Step 3

You are taken to the "Record Delivery Details" screen. Select the "Quantity Distributed" for each drug to the beneficiary.

Additionally, you can add any new drug if distributed using the "+ Add Resource" button and mark its quantity similar to the drugs added before. You can choose to add a comment which is optional, and then press on the 'Submit' button.

Step 4

You will be directed to the "Data Successfully Recorded" screen.

The screen automatically moves to the next one that will ask if the upcoming set of doses were provided to the beneficiary or not.

Step 5: Once the User Presses on Next Button in the Previous Screen the user is taken to the "Data Recorded Successfully" screen which has 2 buttons. "View Household Details" button would take the user to Household Details page of the household for which the distributor recorded the data. "Back to Search" button will take the Distributor to the "Search Individual" Screen to search for beneficiaries from other families.

You can choose "Yes" or "No" with a table below that shows the dosage to be provided for the upcoming cycles. Click on 'Next'.

In Step 4 of recording the multi-round campaign process, based on the response provided by you for the question "Did you provide Drugs for the next Doses?" the screens for next round of delivery in a given cycle will be as follows:

If you replied Yes: If you replied 'Yes', the next time you visit the beneficiary and click on "Record Delivery" against that beneficiary in the household details page, you will see the following screen:

Once you submit the answers for the above questions, you can record the side-effects for a beneficiary by clicking on 'Yes' If no side-effects were reported, select 'No' to move on to the beneficiary details screen, and the delivery status for all cycles will show as 'Completed'.

If you replied No: If you selected "No" in Step 4, for recording the next dose, you will start again from the household details page. Click on the "Record Delivery" button and follow the same flow as for the first round of drug delivery.

This feature allows the distributors to download all the boundary data along with data for beneficiaries which will be covered by the distributor on a given day of a campaign. For this process, the distributor must select all the levels of boundary data till the lowest level of boundary hierarchy so that he/she only need to download limited data at one go, which would aid for device memory and data bandwidth constraints.

Key Features

• Distributor has to select the boundary hierarchy to the lowest level and then download the latest beneficiary data from the server to start their drug delivery.

• Once the data is found, the data can be downloaded and the distributor can choose to download data for other boundaries if they plan to use it.

• This feature can only be done in areas where a stable internet connection is available.

User Roles

Steps to Download Beneficiary Data for Longitudinal Tracking

Step 1

When you login to the app, you will arrive on the "Boundary Selection" screen once the micro-planning data is synced. You will have to select all hierarchies of boundary till the last level of boundary hierarchy before you can click on 'Submit' and download any data onto your devices.

Step 2

Once you click on 'Submit', the app checks with the server if the selected boundary has any new data associated with it which needs to be downloaded on to the device. If new data is found, the following screen will appear and you click the 'Download' button or click on "Proceed without downloading" the data.

Step 3

If you click on 'Download' the download will start if the internet is available on the device.

Step 4

Once the download is completed, a success screen with two buttons will be shown. The "Go To Home Screen" button will take you to the app home screen and you can continue with the deliveries. If you click on the "Download More Data" button, you will be taken to the hierarchy selection screen (shown in Step 1) again.

These are standard features that can be used as-is across any campaign depending on the requirement, with minimal configurations, and can be shared with other products/services as well.

Click on the links below to learn more:

• User Management

• 2D Voucher Scanning

• Proximity-Based Search

• Voucher-Based Registration and Distribution

• Tracking Beneficiary Referrals

• Tracking Side-effects for Beneficiaries

• Tracking Adverse Events

• Health Facility Referral

• Raising Complaints

• Resolving Complaints

The ability for supervisors/managers to create and manage users and team assignments for their respective boundaries through the user interface.

User Roles

Using the User Management Module

A landing page must be available to the user to access all available modules.

Search Page

A user must be able to search for an existing employee using search parameters (name, mobile number, username).

Create New Employee

Users must be able to create new users by providing the following details. Refer to the section on specifications.

Assign Campaigns

View and Edit Screen

Allow users to reset the password. Allow users to edit existing information or add information to an existing employee. Refer to the section on specifications for validations and conditions.

Deactivate Employee Screen

Refer to the section on specifications for validations and conditions.

Supports voucher scanning use cases for Beneficiary Registration, Service Delivery and Bed Net verification use cases.

Key Features

• Enables actors to execute the registration and delivery process efficiently through the use of scanners.

• Code scanning capability provides better user experience by auto populating the data, thus reducing the time and effort.

• Allows manual entry of codes to ensure maximum data collection, with defined validations.

• Prevents duplication of records and monitor resources by linking beneficiaries to their respective codes and reusing it while registering a new beneficiary or distributing resources. One can also monitor the quantity of stock distributed by scanning the code available on the stock.

• Allows multiple scanning of resource at once.

User Roles

Using 2D Voucher Scanning

HCM Home Screen

After logging into the application, the user lands on this screen which displays the daily performance (number of households registered). The progress bar must reset daily at 00:00 hours and start from 0 registrations. The action buttons related to the beneficiary include:

• Beneficiaries

• View Reports

• Sync Data

• Call Supervisor

• File Complaint

At the bottom, there is a card that shows how many records are unsynced for the user’s convenience to sync data. If all the records are synced, then the card must say: “All records are synced”.

The help button is on every screen of the application. By clicking on it, a user can get a walkthrough of the elements on that screen.

On the top right, the administrative area assigned to the user is displayed which is based on the level of hierarchy. The hamburger button on the top left corner covers some other actions mentioned further.

Search Beneficiary Screen

On this screen, a user can search for a registered beneficiary or register a new one. There are multiple options included to search for a beneficiary: search by name, proximity, and scan a code. The metrics card shows the data for beneficiaries registered and the number of resources delivered, depending on the type of campaign.

Scan Code (Search Beneficiary)

Clicking on the scan button on the search household screen opens a scanner that allows a user to scan the voucher code provided to the beneficiary during registration. The user can also enter the code manually by clicking on the “Enter Beneficiary Code” button, if the device is unable to scan.

Based on the campaign type, the beneficiary card is opened with a set of actions for the scanned beneficiary. The user can close the scanner if needed by clicking on the close button.

Scan Code (Linking Beneficiary)

While creating a beneficiary, the user can link the beneficiary to the voucher card provided during registration by clicking on the “Link Voucher to Individual” button. If the scanner is not able to scan the code, the user can also enter the details manually. Screens for the scanner are same as that for search beneficiary.

On successful scanning, the toast message appears over the individual details screen and the voucher code is displayed. In case the scanned code does not match with the one mentioned in the voucher, the user can click on the edit button and rescan or re-enter the code. The previously scanned value must be overwritten by the latest one (No multiple scanning to be done).

Scan Code (Track Delivery Resource)

While delivering any resource to the beneficiary, the user must scan the code provided on the packaging of the resource. The scanner must be able to identify duplicate scans and must not scan the same voucher multiple times. The user can perform multiple scans at a time, but the number must not exceed the value provided by the user in the “Quantity Distributed” field.

The scanner screen has an expandable card that provides the list of resources scanned. The card displays the count of resources scanned along with the identification number for each scanned resource. If one is unable to scan, the user can enter the codes manually, but after every code, he/she must click on the enter beneficiary code again and repeat the process. The user can remove any resource by the help of the delete button provided against each resource. Once scanned, the user must click on the submit button which brings him back to the deliver intervention screen. The toast message for successful scan is displayed on the screen.

At time of registration and drug delivery, the product captures the latitudinal and longitudinal data and the distributor can search for the registered beneficiaries based on the distance from their current location. All the registered beneficiaries are populated based on the distance in an ascending order. The search populates all the beneficiaries registered in a 3-km radius from the current location of the distributor.

Key Features

• Enables distributors to search for beneficiaries within a 3-km radius (configurable) from their current location based on the latitudinal and longitudinal data recorded by the product at the time of registration.

• The latitudinal and longitudinal data will be recorded by the product for both registration and drug delivery.

User Roles

Using Proximity Based Search

On the "Search Individual" details page, you can flip toggle switch to populate all the registered beneficiaries, by distance, in an ascending order, available in a 3-km radius.

With the help of Voucher-Based Registration and Distribution, the registrar can use a QR code-based voucher provided by the program to link beneficiaries to the QR code voucher at the time of registration. This will enable distributors to search for beneficiaries at the time of delivery by scanning the QR code vouchers linked to a specific beneficiary.

Key Features

• Allows a registrar to link a QR code voucher provided by the program to the beneficiary by scanning the QR code at the time of registration.

• Allows a distributor to search for a beneficiary in the system by scanning the QR code voucher shown by the beneficiary when the Distributor has to deliver the drug.

User Roles

Steps to Register Using Voucher Based Registration and Distribution

User Role: Registrar

Step 1

Once the all the mandatory details for an individual are added on the Individual Details screen, you can link the QR code voucher by clicking on the "Link Voucher To Individual" button.

Step 2

The QR code scanner is launched and you can scan the unique QR code linked to the beneficiary. The "1 Resource Scanned" message will appear below the QR scanning panel.

If the QR code voucher scanning shows an error, you can link the voucher manually by clicking on the "Enter Beneficiary Code". The following screen appears, which lets you add the voucher code manually. Next, click on 'Submit' to link the code successfully to the beneficiary.

Step 3

The voucher will appear on the Individual Details page. If click on the 'Edit' button next to the voucher code, you redo step 2 and link the correct QR code voucher to the beneficiary. Click on 'Submit' after adding the correct voucher code for the beneficiary to link the Voucher to the Beneficiary in the database.

Step 4

You will be directed to the "Data Record Successfully" screen.

User Role: Distributor

After the registrations have been done and the respective QR code vouchers are linked to all beneficiaries, the distributors at the time of delivering the drug can search for beneficiaries using the QR code voucher associated to that beneficiary.

Step 1

Come to the "Search Individual" screen, and click on the "Scan QR Code" button.

Step 2

The QR code scanner will open up. Scan the voucher shown by the beneficiary and click on submit.

Step 3

If there is a user linked to the voucher scanned by the distributor, the details of the beneficiaries will appear on the "Individual Details" page. If not, a message will be shown saying "Match Not Found".

Step 4

If the beneficiary is found after scanning, you can open the record of the beneficiary and add the drug administration as per the regular flow.

This feature allows a distributor to refer a beneficiary to a health worker. The referral can happen before or after the drug administration by the distributor.

Key Features

• Allow a distributor to refer a beneficiary to the correct health facility and mark the correct health facility for the referral.

• Referral can be done both before and after drug administration.

User Roles

Steps to Track Referrals

Step 1

On the Household Details screen, you can see the list of beneficiaries who are supposed to receive the drug in that cycle. If the beneficiary is experiencing significant discomfort/sickness due to which you cannot administer the drug, you can click on the "Unable To Deliver?" button for that specific beneficiary.

Step 2

Click on "Refer Beneficiary".

Step 3

You will be directed to the "Referral Details" screen.

In the screen above, you will see the following fields:

• Date For Referral: This will be a non-editable field and will capture the date of referral which is picked directly from the system.

• Administrative Unit: This will be a non-editable field and will be captured based on your user login, which will define the "Administrative Unit".

• Referred By: This field will contain the unique ID for the distributor who has referred the beneficiary and is an editable field.

• Referred To: This field will have a search ability which can be used by clicking on the search lens icon on the field. The following screen will load where you can search for the ID of the facility where the beneficiary is being referred to.

• Reason For Referral: This is a mandatory field which will have all the reasons for referral based on the configuration set for the specific household.

• Referral Comment: This is a non-mandatory field that allows you some custom comments regarding the referral being made for the beneficiary.

Step 4

After you populate all the required fields, click on the 'Submit' button which will take you to the "Data Successfully Recorded" screen.

Once the beneficiary is referred successfully, he/she will be marked as "Beneficiary Referred" in the household details screen.

A distributor can record the side-effects experienced by a beneficiary after consuming the drug. The list of side-effects can be configured based on the specific campaign being conducted.

Key Features

• Allows administrators to record side-effects for drugs delivered to the beneficiaries after every dose consumed by the beneficiary.

• The distributor can record the side-effects for both direct delivery where all the doses of the drug is administered directly to the beneficiary, as well as for indirect delivery where the beneficiary is provided with all the remaining doses by the distributor at the same time and is asked to administer the drug on their own.

User Roles

Steps for Recording Side-Effects During Direct Delivery:

In Step 4 of recording the Multi-Round Campaign delivery process, based on the response provided by the distributor for the question "Did you provide drugs for the next doses?" the screens for recording the side-effects in a given cycle will be as follows:

If you replied 'No' (Recording side-effects when the the distributor does direct delivery for all rounds):

Step 1

After you have completed the delivery for first dose, you will see the list of beneficiaries who are eligible for the next round of drug delivery. If the beneficiary experienced any side-effect, click on the "Unable to Deliver?" button, where you will get 3 options. Here, the last option will be "Record Side Effects".

Step 2

You will be taken to the next screen where you need to record the side-effect experienced by the beneficiary. Once you have selected the relevant side-effect, click on 'Next'.

You will see a success screen that says, "Data recorded successfully".

If you replied 'Yes' (Recording side-effects when the the distributor does indirect delivery for subsequent deliveries):

Step 1

If you replied 'Yes' the next time you visit the beneficiary and click on "Record Delivery" against that beneficiary in the household details page, you will see the following screens:

Step 2

Once you submit the answers, you can record the side-effects for the beneficiary. If no side-effects were reported, select 'No' to move on to the beneficiary details screen, and the delivery status for all cycles will show as 'Completed'.

Step 3

If you select 'Yes', you can record the side effect. Click on 'Next'.

You will see a success screen that says, "Data recorded successfully'. If you select 'No' for side-effects, you will be taken directly to the "Data Recorded Successfully Screen".

Note: If the Distributor answered 'No' on the "Record Past Delivery" page, the delivery status will changed to 'Visited' on the household details page for that specific beneficiary.

While administering the dose to a beneficiary (usually children), there can be instances when the beneficiary shows some symptoms against the dose provided. These adverse events need to be recorded and monitored as it helps to take precautionary measures for further doses as well as in future campaigns for that beneficiary. It is helpful for cases when a beneficiary's situation becomes critical and he/she needs to be referred to a healthcare facility. This is also crucial for resource tracking because, in certain campaigns, the beneficiary can be re-administered the dose even after he vomits out the medicine.

Kay Features

1. Recording adverse events.

2. Enabling actors to record and track the adverse events observed in a beneficiary after administration of the dose.

3. Monitoring the data to plan and decide for upcoming doses during the campaign.

User Roles

Using Tracking Adverse Events

Deliver Intervention

The user needs to provide the delivery details for the resources delivered to the beneficiary. The screen is configurable depending upon the campaign type and the auto-calculated resources and quantity are displayed and populated in the fields. The user can edit the fields if required to change the resource administered.

Adverse Events

When the user clicks ‘Next’ on the deliver intervention screen, it opens a pop-up that asks: “Did you observe any adverse events?” If the user selects ‘No’, the adverse events screen is skipped, and he/she is directly navigated to the next screen in the flow. If the user selects ‘Yes’, it opens the adverse events form to capture the details. On top the summary of delivered resources is displayed in a tabular form. The list of symptoms must be configurable to include more values if required. It is possible that the beneficiary shows multiple symptoms, thus the user must be able to select multiple values from the list.

If the dose is readministered, then the user must select ‘yes’ and provide the number of times it has been readministered.

The “Refer Beneficiary” button navigates the user to the refer beneficiary flow, in case the beneficiary is critical and requires medical assistance. The ‘Next’ button takes the user to the next screen in the flow.

This will enable the health facility supervisors to track referrals made by on-field health workers to different health facilities digitally via the Digit HCM app

Key Features

It captures all the cases of:

1. Beneficiary being referred.

2. Referral details of the beneficiary.

3. Reason for referrals and its diagnosis.

4. Based on the diagnosis chosen further details if applicable.

User Roles

Using the Health Facility Referral Management Module

User Persona: This feature will be used by workers working at a given Health Facility (HF) who will be responsible for giving the diagnosis based on the type of symptoms they observe and then do a diagnosis and provide the appropriate drugs.

Steps for Referral Flows:

Step 1:

Login for a HF worker who will see the home screen options based on the role-action mapping and will see the option which says “Beneficiary Referral“. The options available on the home screen for HF workers apart from the Beneficiary Referral option will be defined based on the role-action mapping provided for them.

Step 2:

When the user clicks on the “Beneficiary Referral” button in the previous screen, the user will be taken to the “Search Beneficiary” screen where he/she can search for a given beneficiary by their name or a QR code voucher provided to the beneficiary.

Search Produces Result: If the user searches for a given beneficiary name and finds a match, he/she can click on the 'Open' button in the card for that beneficiary and view their details.

Search Does Not Produce Result: If the search does not provide any results, the user can click on the “Create New Referral" button to add a new entry under the Referral module.

Step 3:

Once the user creates a new referral or opens an existing one in the previous step, he/she is taken to the Facility Details screen first where he/she needs to enter the details of the health facility they are in to attend the beneficiary. This screen will have the following fields:

1. Administrative Unit: This field will be auto-filled from the value available from the role-action mapping, and will be non-editable.

2. Date of Evaluation: This field will be auto-filled with system value and will be non-editable.

3. Evaluation Facility: This will be a mandatory field for the health facility worker to search and add. It is the ID used for a given health facility.

4. Name of Health Facility Coordinator: This is a non-mandatory field that will capture the name of the health facility coordinator who is attending the referred beneficiary.

5. Referred By (CDD Team Code): This is a non-mandatory field that will capture the CDD team code of the field worker who referred the beneficiary.

Once the user has filled all the fields with the relevant information, he/she must click on the 'Next' button.

Step 4:

After the user has clicked on submit, he/she will come to the screen called “Referral Details”. On this screen, the user is supposed to enter details into sections, that is, “Referral Details” and “What is the reason for referral”.

Section 1: Referral Details

In this section, the user must add the details to the following fields:

• Select Cycle: This will be a dropdown selector which will have the cycle numbers. This is a mandatory field and cannot be left empty.

• Name of the child: The user needs to add the name of the referred beneficiary. This field is mandatory.

• Beneficiary ID: This will be added by the user with the beneficiary ID of the referred Beneficiary. This is a mandatory field.

• Age in Months: This will be a mandatory field that will capture the age of the beneficiary being referred in months.

• Gender: This is a mandatory field with a dropdown having values: Male, Female, Other.

Section 2: Reason for Referral

In this section, the user must capture the data as to why the beneficiary was referred. The field will capture data with the help of the radio button option selector. The options are:

• Sick

• Fever

• Drug side effect in current cycle

• Drug side effect in previous cycle

After selecting one of the reasons for referral, the user needs to press 'Next' which will navigate the user to 3 different screens based on what they select in the “Reason for Referral” section.

Step 5:

Based on what the user selects in the previous step in the “Reason for Referral” section, the following 3 flows could be shown to the user:

• If “Sick” was chosen as a reason: If the user selects 'Sick' as the reason for eeferral in Step 4, he/she will be taken to “Referral Due to Illness” screen, where he/she will see the following list of questions:

  • “Child evaluated to determine cause of illness”: This will be a mandatory question to be answered with 2 options in the form of a radio button: Yes or No.

  • Enter Comment for Diagnosis: The answer to this question should be entered by the user in a free text form which will be a mandatory field.

  • “Was the Child Treated?”: This question will be answered by the user using a radio button option of 'Yes' or 'No', and it will be a mandatory question

  • Name and Dose of the Drug: Provide an open text field that will be mandatory.

  • “Was the child admitted / transferred to the hospital due to serious illness?”: This question will have a Yes/No radio button selection for it. This is a mandatory field.

• If “Fever” was chosen as a reason: If the user selects 'Fever' as the reason for referral in Step 4, the user will be taken to the “Referral Due to Fever” screen, where he/she will see the following list of questions:

  • “Was the child tested for malaria?”: This question will have a Yes/No radio button option. This will be a mandatory field.

  • “Result of Malaria Diagnostic Test? “: This will be a mandatory field and based on what the user answers to this question the next set of questions for the user will open up as a nested form.

    • If the user chooses 'Positive' as the answer for “Result of Malaria Diagnostic Test? then he/shewill see the following questions:

      • Was the child admitted/transferred to the hospital due to serious illness?: This will be answered with a simple Yes/No radio button and will be a mandatory field.

      • Child with positive malaria test treated with anti-malarial?: This will be answered with a simple Yes/No radio button and will be a mandatory field.

      • Name and Dose of Anti Malarial: This will be answered with an open text form and will be a mandatory field.

      
    • If the user chooses “Negative” for “Result of Malaria Diagnostic Test?, then he/she will see the following questions as a nested fForm:

      • “Child with negative malaria test received SPAQ in this cycle“: This will be a Yes/No Radio button question, and is a non-mandatory field.

      

• If “Drug side effect in current/previous cycle” was chosen as a reason: If the user selects “Drug side effect in current/previous cycle” as the reason for referral in Step 4, he/she will be taken to the“Referral due to adverse drug reaction” screen, where he/she will see the following list of questions:

  • Child evaluated for adverse reaction for SP and AQ?: This will be a simple Yes/No radio button in the form and it will not be a mandatory field.

  • The National Pharmacovigilance has been filled out?: This will be a simple Yes/No radio button in the form, and it will not be a mandatory field.

  • Was the child admitted/transferred to the hospital due to serious illness?: This will be a simple Yes/No radio button in the form, and it will not be a mandatory field.

Once all the questions in one of these flows are answered, a pop-up frame asking for confirmation will be shown for submission as shown below:

Once the user clicks on submit, he/she will see the ”Data Recorded Successfully” screen, and the option to navigate to the home screen.

Users can file a complaint using the HCM app. There are a few assumptions:

• Not all complaints will be logged using the complaints module. Users may prefer raising complaints on WhatsApp groups/calls, and may not be registered in the system.

• Complaints are most likely to be logged by users on behalf of other users (Most common use case: Supervisors raising complaints on behalf of users).

User Roles

Users Raising Complaints

After logging into the application, the user lands on this screen which displays daily performance (number of households registered). The progress bar must reset daily at 00:00 hours and start from 0 registrations. The action buttons related to the beneficiary are present, which include:

• Beneficiaries

• View reports

• Sync data

• Call supervisor

• Complaints

Complaints

When the user clicks on the complaints, she is navigated to the “My Complaints” screen, which consists of two actions:

• File a complaint (primary action): Clicking on this must open the complaint type screen.

• View previously logged complaints.

File Complaint Workflow

Complaint Type

When the user clicks on file a complaint, the complaint type screen appears. The user must select the type of complaint from the list, which must be configurable (to be configured during implementation as per program requirements).

There is a ‘Next’ button at the bottom of the screen, clicking on which, the user is navigated to the complaint details screen.

Complaint Details

Once the user has selected the type of complaint and clicked on ‘Next’, this screen appears, where they need to provide the complaint details.

The date field is auto-captured by the system, which must be non-editable.

The administrative area is also auto-captured but it is editable. It is editable in case the user is creating the complaint on someone’s behalf. The dropdown displays a list of boundaries that are assigned to the user.

The user needs to select whether she is raising a complaint for herself or on behalf of another user.

If the user wants to raise a complaint for herself, then she must provide the following details:

1. Name (must be populated if already available in the user’s profile else must be blank).

2. Contact number (must be populated if already available in the user’s profile else must be blank).

3. Supervisor’s name and contact number.

If the complaint is raised on behalf of another user, then her details must be captured in the above fields. The user has the option to upload images describing the issue along with a text-based description. If the user wants to change the type of complaint, they can click on the ‘Back’ button and return to the previous screen.

After filling in all the details, the user needs to click on the ‘Submit’ button to file the complaint.

Confirmation Screen

When the user clicks on the submit button after providing all the complaint details, the confirmation screen appears, which provides information on whether the complaint has been submitted or not.

• If the complaint has been submitted, then it must show the message to sync the data for generating the complaint number. There must be a back to home button below the message. When the user clicks on it, she must be navigated to the home screen.

• If the complaint has not been submitted, then there must be two buttons available; Retry and Back to Home.

There is a support helpdesk set up by the program which will receive all complaints raised by system users. The support helpdesk is responsible for reviewing all the complaints in the inbox. Depending on the complaint, the helpdesk can either resolve, reject, or assign the complaint to the respective actor Helpdesk users may create complaints on the user’s behalf, which are received over call/WhatsApp messages.

User Roles

Resolving Complaints

Resolving a complaint (Mobile App View)

Helpdesk

The L1 support helpdesk must be the first point in the complaint management workflow. All complaints created must be first routed to the helpdesk, after which the helpdesk may take appropriate action (mentioned below).

The helpdesk user must be able to do the following :

• View the list of complaints in the inbox

• File a new complaint

• Open a complaint from the inbox and

View complaints status

Resolve a complaint

Reject a complaint

Assign to other roles

The inbox view for other workflow states must be similar and must be able to view complaints assigned to their respective inbox. The user must also have the option to assign the complaint back to the L1 support helpdesk by selecting the value in the “Assign To” field. The users must be able to view complaints that have been assigned to their role. For example, the L1 helpdesk user must not be able to view complaints assigned to the L2 helpdesk and vice versa.

Filters The user can apply filters in multiple parameters as follows:

• Complaint Type: The user can select the complaint type from the dropdown

• Administrative Area: The area of complaint.

• Status: Refer to the list of statuses detailed above.

A button to clean all filters must be available at the bottom of the page. An “Apply Filter” button must be available to set the filters and route the user to the inbox and display the filtered complaints.

Search By

A user must be able to search for one or more complaints by using the following search parameters (must support passing multiple search parameters):

• Complaint Number

• Mobile Number

• Administrative Area

After providing the appropriate search parameters, the user must click on the “Search” button located at the bottom of the screen and must be routed to the inbox which displays the search-appropriate search results.

Complaint Summary

A summary screen must be displayed when the user clicks on the ‘Open’ button located on the complaints card.

Actions

The “Take Action” button at the bottom of the screen must open a pop-up displaying all possible actions that the user can take. The actions available to address the complaint are as follows:

• Resolve Complaint

• Assign to P2

• Reject Complaint

• Close

The close button collapses the overlay and takes the user back to the complaints summary screen.

Assign Complaint

If the user wants to assign any project to P2, she must click on the assign button which opens this screen. The date of assigning the complaint is user input which can be filled in with the help of the calendar icon within the field.

In the "assigned to" field, the user needs to select the person to whom she wants to assign that complaint. There is an additional comments field in which the user can provide any remarks if she wants. The user can attach any supporting documents such as photos, documents, etc.

At the bottom, there is a cancel button which takes the user back to the complaint summary screen, and an assign button which assigns the complaint to the selected person.

Confirmation Screen

If the complaint has been assigned successfully, then the following screen must appear.

Landing Page (Common page)

A landing page must be available to the user to access all available modules.

Helpdesk (Desktop View)

When the user clicks on complaints on the home screen, then this screen must appear. On the top left, there is an option to file a new complaint, view reports. Besides, there are search fields for different parameters, such as complaint number and mobile number, and the search button to execute the search action. There is a clear search button below the search one if the user wants to clear the search parameters.

Below the new complaint and reports buttons, there are filters available to apply over the results. The filter parameters are the same as that for the mobile view.

The complaints are displayed in a horizontal format with the same values for mobile view. The user can click on the entire area of a particular complaint.

At the bottom, there are forward, backward, first page, and last page arrow buttons along with the page number information as displayed on the screen.

Complaint Details

When the user clicks on a complaint, the details screen appears which provides the entire information of that complaint. The summary includes the same information mentioned in the card along with the additional comments/remarks, and photos provided by the complainant.

There is a "Take Action" button at the bottom. When the user clicks on it, the actions appear above the button as displayed on the screen. The actions include resolve complaint, assign to P2, and reject complaint. If the user clicks on any blank area on the screen, the actions collapse.

Resolve Complaint

If the complaint has been resolved, then the user must click on the "Resolve Complaint" button which opens this screen. There is an "Additional Comments" field in which the user can provide any remarks if he wants. At the bottom, there is a submit button that updates the complaint status as resolved.

Reject Complaint

If the user has rejected any complaint, then she needs to select the reason for rejection from the dropdown. There is an additional comments field in which the user can provide any remarks if he wants. At the bottom, there is a submit button that updates the complaint status as rejected.

Assign to P2

If the user wants to assign any project to P2, she must click on the assign button which opens this screen. The date of assigning the complaint is user input which can be filled in with the help of the calendar icon within the field.

In the assigned to field, the user needs to select the person to whom she wants to assign that complaint.

There is an additional comments field in which the user can provide any remarks if he wants. The user can attach any supporting documents such as photos, documents, etc.

At the bottom, there is a cancel button which takes the user back to the complaints screen, and an assign button which assigns the complaint to the selected person.

Confirmation Screen

If the complaint has been assigned successfully, then the following screen must appear. If the complaint could not be assigned, then the text must say, “Complaint Not Assigned.”

New Complaint

When the user clicks on the “New Complaint” button on the complaints screen, then this screen appears. The details captured are the same as that entered by the complainant. When the details are entered, the user needs to click on the submit button which opens the confirmation window over the same screen. If the user clicks on the cancel button, then she is navigated back to the complaints screen

Confirmation Screen

When the user clicks on the submit button, the system confirms whether the complaint has been submitted successfully or not. There is a back to home button placed on both screens, clicking on which will navigate the user to the home screen of the helpdesk.

In health campaigns, it is crucial to keep track of the resources delivered to prevent stock mis-handlings and maximise coverage. This helps to track the resource till the last mile delivery, that is, it captures the stock till it reaches the distributor, and the distributor can record the quantity of stock received along with other stock transactions.

Users can do the following:

1. Track stock till the last mile.

2. Capture stock details till the end user to keep track of the transactions that take place.

3. Record the stock transactions during a campaign.

4. Ensure the safety of stock.

5. Keep track of the stock count and verify from both ends (received versus issued) to prevent the misuse of stocks.

Using Inventory Management: Last Mile Delivery

HCM Home Screen

After logging into the application, the user lands on this screen which displays daily performance (number of households registered). The progress bar must reset daily at 00:00 hours, and start from 0 registrations. The action buttons related to the beneficiary are present which include:

• Beneficiaries

• View Reports

• Sync Data

• Call Supervisor

• File Complaint

• Manage Stock

On the bottom, there is a card that shows how many records are unsynced for the user’s convenience to sync data. If all the records are synced, then the card must say “All records are synced”.

The help button is on every screen of the application, and by clicking on it, a user can get a walkthrough of the elements on that screen.

On the top right, the administrative area assigned to the user is displayed which will be based on the level of hierarchy.

The hamburger button on the top left corner covers some other actions mentioned further.

Manage Stock

This includes all the stock transactions that can be captured by the distributor.

Transaction Details

The transaction details are captured on this screen. The date and administrative unit fields are auto-captured by the system and are non-editable. The team code/identifier is captured from the user profile and it must be editable.

Received Stock Details

The stock-related details are captured on this screen. “Select product” is a dropdown field that includes the resource that has been received. “Received from” is a search-based dropdown field, clicking on which navigates the user to the search facility screen that includes the facilities along with ‘Supervisor’ as the value. If the user selects ‘Supervisor’ then he/she must enter the supervisor’s name. The user must enter the quantity received, and if any additional comments are needed, they can be added.

Acknowledgement Screen

Once the user clicks on ‘Submit’, the confirmation pop-up appears. If the user clicks on the ‘Submit’ button, the acknowledgement screen appears, and ‘Cancel’ takes the user back to the previous screen.

Transaction Details (Stock Consumed)

Consumed Stock Details

This screen includes all the fields except for the facility field.

This screen includes all the fields except for the facility field.

Transaction Details (Stock Returned)

Returned Stock Details

Click on the links below to learn more:

• Stock Management

• Stock Reconciliation

• View Reports

• Bale Scanning

This enables a user to manage stocks, besides facilitating stock reconciliation.

Using Stock Management

On this page, the following actions can be performed:

• After a successful login as a warehouse manager, a user lands on the home screen which consists of "Manage Stock", and "Stock Reconciliation".

Manage Stocks

This screen consists of the following types of transactions that take place for the the inventory:

• Stock Receipt

• Stock Issued

• Stock Returned

• Stock Damaged

• Stock Loss

Stock Receipt

• When a user clicks on record stock receipt, the warehouse details screen will appear.

• The latitude/longitude captures the geo-location of the warehouse which can be fetched with the help of the location icon within the field.

• Clicking on the next button will navigate the user to the "Received Stock" details screen.

• The "Receipt Stock Details" form has some mandatory fields: product, received from warehouse, and quantity received.

• The optional fields include waybill number, quantity indicated on waybill, transport type, vehicle number, and comments.

• Clicking on the submit button will take the user to the success page.

Record Stock Issued

• This screen captures the mandatory fields: Product, Issued to warehouse, and the quantity.

• The optional fields include waybill number, quantity indicated on waybill, transport type, vehicle number and comments.

• Clicking on the submit button will go to the success page.

Returned Stock Details

This screen captures the mandatory fields: Product, returned to warehouse, and quantity returned.

The optional fields are waybill number, quantity indicated on waybill, transport type, vehicle number, and comments.

Clicking on the submit button will take the user to the success page.

Damaged Stock Details

• This screen captures the mandatory fields: Product, damaged during, received from, and quantity damaged.

• The optional fields include waybill number, quantity indicated on waybill, transport type, vehicle number, and comments.

• Clicking on the submit button will take he user to the success page.

Lost Stock Details

This screen captures the mandatory fields: Product, lost during, received from, and quantity lost.

The optional fields are wWaybill Number, quantity indicated on waybill, transport type, vehicle number, and comments.

Clicking on the submit button will take the user to the success page.

Stock Reconciliation

Click here to learn more about stock reconciliation.

This enables a user to verify whether the physical count and calculated stock values are the same or not.

Using Stock Reconciliation

After successful login, a user lands on the home screen, which consists Stock Reconciliation". When the user clicks on the stock reconciliation button on the home screen, he/she is navigated to this screen where they need to verify whether the physical count and calculated stock values are the same or not.

In the select product field, the user needs to select a product from the dropdown. There are warehouse name and administrative area fields as well, all of which are mandatory. The following details are there:

• Date of Reconciliation

• Received Stock

• Issued Stock

• Returned Stock

• Damaged Stock

• Stock Lost

• Stock on Hand- The stock on hand is calculated as incoming stock minus outgoing stock. There is a hint icon for how the stock on hand is calculated. The received and returned stocks will be considered incoming stocks. The issued, damaged, and lost stocks will be considered outgoing stocks.

The date of reconciliation is system-generated and non-editable. Other values are calculated based on the data recorded in stock receipts, stock issued, and the stock returned screens. In the manual stock count, the user needs to enter the value for manually counted inventory. If the stock on hand does not match the physical count, then the latter must take precedence, provided the user has submitted the form with a proper reason. In the comments field, the user can add remarks and comments.

When a user clicks on the view reports button on the home screen, he/she is navigated to this page where he/she has the provision to view the following reports:

• Stock Received

• Stock Issued

• Stock Returned

• Stock Reconciliation

Users can click on the arrow button placed next to every transaction to open the respective report. The back button will navigate them back to the home screen.

Using View Reports

Report (Stock Received)

When the user clicks on the “Stock Received” button, the report for stock received appears which provides a tabular representation of the data. The table is scrollable, both vertically and horizontally, to cater to multiple values and columns. The date column is kept frozen and other columns are scrollable. The first column is for the date of the receipt, followed by units received in the second column, and received from (warehouse name) in the third column. The “Back To Home” button is placed at the bottom of the screen which navigates the user back to the home screen.

Report (Stock Reconciliation)

For the stock reconciliation report, the table consists of the date in the first column and other columns. The “Back To Home” button will navigate users to the home screen.

Scan the resource code to track the resources delivered:

1. Package utilised to parse the barcode : https://pub.dev/packages/gs1_barcode_parser.

2. Package utilised to QR code scanner: https://pub.dev/packages/qr_code_scanner

3. GS1 - standards : https://www.gs1.org/docs/barcodes/GS1_DataMatrix_Guideline.pdf

4. Package utilised for barcode scanning-

https://pub.dev/packages/google_mlkit_barcode_scanning

google_mlkit_barcode_scanning

Given a field value formatted with the GS1 data matrix standard and a string key from the GS1 application identifiers. The function should look and return the value linked to the provided key.

A well-formatted value would look like:

]d20108470006991541211008199619525610DXB200517220228

The Attendance Module will allow supervisors to mark attendance for their attendees which will, in turn, help the system maintain the authenticity of records and provide consistent data for payments to the attendees.

Key Features

Enables supervisors to mark attendance for their attendees in an offline-first manner. The attendance can be marked in 2 ways based on the type of attendance structure chosen by the programme team:

1. Attendance recording once a day.

2. Attendance recording twice a day (Morning and Evening).

User Roles

Using Attendance Management Module

User role: Supervisor

Step 1:

The user will see the "Mark Attendance" option in the home screen of the app as follows:

Step 2:

When the user clicks on "Manage Attendance", they will see the attendance registers created under the specific user name having the following details:

1. Campaign Name

2. Event Type

3. Start Date

4. End Date

5. Staff Count

6. Status

7. Attendance Completion (in Days)

Step 3:

Once the user clicks on "Open Register" for one of the available registers, the user will be taken to the "Select Session" screen where the sessions available to be marked in the given attendance register will be seen.

Step 4:

Once the user has selected the desired session and clicks on the "Mark Attendance" button, the user will be taken to the "Mark Attendance" screen where the list of attendees for a given project and a given session will be available.

Step 5:

The user can click on the empty circles in front of every attendee and move the state of the attendance from "Not Marked" to 'Present' to 'Absent' on each click of the circle.

Once all the attendees have their attendance marked in the register, only then the user can click on submit.

If the attendance in a given register is partially marked, the user cannot submit the attendance and will have to click on "Save and Mark Later" which will allow the user to save attendance as a draft for the given register.

User Roles:

• Proximity supervisor

• Payments approver

Steps on how a proximity supervisor can use the Payments module

First, select the language before you can log in. Currently, three languages are supported:

English

Portuguese

French

Select the desired language and click on ‘Continue’ to access the Login page.

On the login page, enter the credentials for a proximity supervisor and select the assigned boundary. After reading through the Privacy Policy statement, select the checkbox to accept the terms and conditions and then click on ‘Continue’ to proceed to the landing page for proximity supervisor.

On the landing page for a proximity supervisor, ‘Payments’ label is displayed along with an option to view the “Attendance Registers”. Click on the “Attendance Registers” label to access project-specific attendance registers.

Select the desired project name (event name) from the options in the dropdown and click ‘Next’ to proceed.

Following selecting the project name, you will navigate to the ‘Inbox’ screen, where no attendance registers are shown by default. To view attendance registers, a desired boundary must be selected through a boundary filter (in this case ‘District’). Once the desired boundary is selected, click on ‘Apply’ to proceed.

Post selection of a desired boundary, you will be directed to a screen that shows all the “Pending for approval (#)” and ‘Approved (#)’ attendance registers that have been created within that specific boundary, with “Pending for approval (#)” registers being the default viewing option. ‘Approved (#)’ attendance registers can be accessed through toggling. Based on the status type (either pending for approval or approved), further discretised information is provided in a tabular format which includes the following: Attendance ID, Attendance marked by, Boundary, and Number of attendees.

Clicking on the “Attendance ID” on the ‘Inbox’ page will open the “View Attendance” screen, which will provide all the campaign-related details of the registrant and their attendance summary. The ‘Action’ button present on the bottom right of the screen allows the proximity supervisor to either “Edit Attendance” or ‘Approve’ the submitted data.

On clicking “Edit Attendance”, a warning message is displayed informing the proximity supervisor that editing the attendance days data will impact the payments and the same will be frozen for the entire event duration, followed by a confirmation question. This means that if the field supervisor marks the attendance for any further dates, it will not be updated in the register. The proximity supervisor can decide to either ‘Proceed’ to update the attendance data or select ‘Cancel’ to go back to the “View Attendance” page. Click on ‘Proceed’ to confirm the editing of the attendance data.

Next, the “Edit Attendance” page is displayed which will allow the proximity supervisor to update the attendance data for each field supervisor with the help of the ‘+/-’ buttons, or they can enter the count directly within the data entry field. The ‘Submit’ button is disabled until the proximity supervisor updates the attendance for at least one field supervisor.

If the “number of days worked” entered exceeds the event duration while updating, an error message will be shown informing the proximity supervisor.

Once the new attendance data has been entered, click on ‘Submit’ to proceed.

Subsequently, a toast message is displayed indicating that attendance has been updated successfully. The attendance data can be modified as many times as required until it is approved.

Following the successful submission of the new data, the “View Attendance” page will automatically appear, where the updated attendance data is reflected.

Now, click on the ‘Action’ button and then select the ‘Approve’ option. This will open a dialog box, where mandatory comments should be provided to proceed with the approval process which is continued by clicking again on ‘Approve’. The approval process can also be cancelled at this stage by clicking on ‘Cancel’.

After submitting the mandatory comments, if the ‘Approve’ option is selected, then a confirmation pop-up will appear with a message highlighting that the data once approved cannot be modified.

On clicking again on ‘Approve’, a success screen will be displayed for the confirmation, and the muster roll will be generated and displayed on the screen. Following this, any other assigned tasks can be carried out by clicking on “View Another Register” or “Go Back to Home”.

On the ‘Inbox’ page, the status of the register can now be seen as approved, and when it is opened, no actions are available, except to “Go Back”.

Steps on how a payments approver can use the Payments module

The payment approver is responsible for generating and downloading the final payment bill which is further used to disburse the payments to all the campaign workers.

First, select the language before you can log in. Currently, three languages are supported:

English

Portuguese

French

Select the desired language and click on ‘Continue’ to access the login page.

Next is the Login page, where the credentials for a campaign supervisor are entered and the assigned boundary is selected. After reading through the Privacy Policy statement, the checkbox is selected to indicate acceptance. Then click on ‘Continue’ to proceed.

This is the landing page for a campaign supervisor. On this page, a card is displayed for Payments with the options to go to the ‘Inbox’ page to generate bills, and to ‘My Bills’ to view and download already generated bills. Click on ‘Inbox’ to proceed.

On this page, the project name (event type name) from the available options must be selected, as well as the aggregation boundary details; whether the bill should be aggregated at the National, Province/State, or District Level. Select the required aggregation boundary level and click on ‘Next’.

Following this, the “Bill Inbox” page will appear, where the specific boundary should be filtered for which the bill has to be generated. Once selected, it will display all the attendance registers, both approved and pending approval, which can be only viewed by the campaign supervisor, along with an option to generate the bill. Click on “Generate Bill”.

The campaign supervisor will be able to generate the bill only once for a particular boundary, and this can be done only when all the registers within that boundary have been approved.

On clicking “Generate Bill”, a confirmation popup is displayed that indicates that the bill cannot be generated again. Click on “Generate Bill” to proceed.

This will initiate the bill generation process along with displaying a toast message highlighting the wait time for completion of the process. Click on “My Bills” to proceed.

Clicking on “My Bills”, will display the bill inbox page, where all the generated bills can be found. On this page, bills can be searched by the “Bill ID” or a date range based on the date they were generated. The bills still being generated can be identified in the ‘Actions’ column.

Once the bill has been generated successfully, it can be downloaded as either an Excel file or a PDF by clicking on the respective action button. Choose the required format for the report to be downloaded.

Find below an illustration of the PDF report. The report provides the following information: total amount to be processed, details of each individual, different cost heads that are applicable based on the assigned role, and the sum of the amount to be paid based on the number of days attended.

1. Purpose

This document serves as a guide to effectively use the Payments module within Health Campaign Management (HCM). It outlines the features and functionalities available to users, clarifying tasks that can be performed and limitations to be aware of. Additionally, it provides essential instructions for critical processes, such as approving attendance and generating payments, including key considerations and best practices. The document also highlights important dos and don'ts to ensure smooth and error-free operations. To enhance understanding, it offers a detailed overview of the Payments module's workflow, supported by illustrative screenshots for better clarity and ease of reference.

2. Definitions

• HCM: Health Campaign Management - The tool for managing health campaigns, including modules for various functions such as payments, attendance, enumeration, supervision, etc.

• Event: Key activities during a campaign where attendance is recorded, such as training, enumeration, and distribution.

• Attendance Register: A record of attendance for different campaign events, detailing participant names and attendance dates. Attendance markers use the HCM attendance module to record attendance daily until the event concludes.

• Muster Roll: An official report documenting the daily attendance of workers engaged in a specific project or campaign. It includes essential details such as worker names, roles, work locations, attendance dates, and days worked. The muster roll is created after the attendance register is approved and serves as a reference for validating attendance, calculating wages, and generating payment reports.

• Attendance Marker: The individual responsible for recording event attendance using the HCM mobile app’s attendance module.

• Proximity Supervisor: The person authorized to review and, if necessary, edit attendance records submitted by attendance markers. They approve the records for payment processing.

• Payment Approver: The person tasked with reviewing generated muster rolls, consolidating them into a single payment report for a specific boundary, and sharing it with financial authorities for payment disbursement.

• Boundary: An administrative area used for managing campaigns, such as a province, district, locality, or village. Events and users are assigned to specific boundaries. For instance, a district supervisor assigned to District ABC will oversee district-level training registers created within District ABC.

3. Scope

1. Editing Attendance Records Post-Event Completion

• Authorised personnel, such as proximity supervisors, can modify attendance records after an event concludes to correct errors or omissions made during initial data entry.

• Edits include correcting the number of days worked, or marking attendance for previously unrecorded participants.

• All edits are tracked and documented within the system for audit purposes.

1. Approval of Attendance Records and Muster Roll Generation

• Once attendance records are reviewed and finalised, they are submitted for approval by proximity supervisors.

• Approved records are used to automatically generate the muster roll, which contains attendance details for the event.

• The muster roll becomes the official document for wage validation and payment processing.

1. Reviewing Approved Registers

• Payment approvers or other authorised stakeholders can access and review attendance registers that have already been approved.

• The review process ensures compliance with organisational guidelines and verifies that data matches muster roll records before payment reports are generated.

1. Viewing Approved and Unapproved Registers

• Users with appropriate permissions can view both approved and pending approval attendance registers.

• This view allows campaign managers to monitor the status of attendance records for all events within a given boundary.

• Filters and search functionalities may be available to help locate specific registers based on event type, date, or boundary.

4. Out of Scope

The following features and functionalities are not included in this version of the Payments module and are considered out of scope. Some may be considered for inclusion in future versions.

• Campaign Worker Onboarding: Workers must be onboarded via the HRMS or Console web interfaces, as this is not supported in the app.

• Worker Registry Validation: The module does not support checks for:

- Duplicate entries or boundary over-allocations.

- Mobile number authentication (inactive numbers or mismatches).

- Identity verification or validation of mobile money accounts for status and transaction limits.

• Approval Workflows: Missing workflows for:

- Payment report approvals

- Muster roll approvals

• Attendance Corrections: No provision for:

- Proximity supervisors returning attendance reports to field supervisors for corrections.

- Payment approvers returning attendance reports to proximity supervisors for corrections or rejections.

• Worker Payment Configuration: Setting different rates for workers with the same role based on location boundaries is not considered for this version.

• Reporting Limitations: Support for generating intermediate reports before event completion is not considered for this version.

• Attendance Evidence: The following capabilities are not in scope for this release:

- Photos of workers or ID card

- Signature, QR code, or biometric-based attendance

• Financial Integrations: No integration with mobile money operators (MMOs), banks, or financial institutions.

• Worker Communication: Automated SMS notifications for payments, attendance tracking, or registrations are not considered for this version.

• KYC and Registry Cross-Checks: No automated cross-checking of failed KYC attempts, name mismatches, or duplicates against MMOs and the worker registry in HCM.

5. Roles and responsibilities

1. Attendance Marker: Responsible for recording attendance at events (e.g., trainings, enumerations). This role may be filled by a field team supervisor or any individual presiding over the event.

2. Proximity Supervisor: Charged with approving the attendance recorded by the attendance marker. They verify attendance details (often via phone outside HCM) if discrepancies arise and have the authority to edit records after the event concludes. This role typically operates at the district level or higher.

3. Payment Approver: Oversees the consolidation of attendance records to generate boundary-specific reports. They are responsible for approving the payment report, forwarding it to higher operations for additional approvals, and liaising with financial institutions to process payments.

6. Dos and Don’ts for Key Roles

1. Attendance Marker

Do's:

• Mark daily attendance for all assigned registers without fail.

• Sync all records to ensure no pending entries remain on the device before the proximity supervisor edits or approves the attendance records for that event.

• Raise complaints for issues like adding/removing persons or correcting details of the staff using the complaints module or by contacting the system administrator.

Don’ts:

• Submit incorrect attendance—once submitted, corrections are not possible for the attendance marker.

2. Proximity Supervisor

Do's:

• Verify with the attendance marker for all the districts that all records are synced before editing or approving attendance.

• Make edits as necessary but ensure all details are accurate before final approval.

• Approve all registers systematically, completing one district before moving to the next.

• Raise complaints for issues like entry corrections via the complaints module or the system administrator.

Don’ts:

• Approve attendance without confirming that all records are synced.

• Assume changes can be made after approval—final approvals are irreversible.

3. Payment Approver

Do's:

• Double-check all details in the payment report (PDF/Excel) before submission to financial institutions.

• Generate payment reports for each boundary systematically, starting with one district and moving to the next, including provincial/national events.

• Wait 2-3 minutes for report generation before reporting issues.

Don’ts:

• Editing Excel reports after generation is not allowed.

• Submit incomplete or inaccurate reports.

4. System Administrator

Do's:

• Validate worker information (enumerators, supervisors, etc.) before onboarding them in the system, ensuring correct mobile numbers and IDs.

• Confirm no duplicate personnel or mobile numbers exist in the system.

• Map workers accurately per the microplan, avoiding over or under-allocations

• Verify that mobile and bank account numbers belong to the correct person and not their family members.

• Ensure mobile numbers are active and unrestricted for receiving payments.

• Approve register changes only after supervisory authorisation.

Don’ts:

• Allow unverified or incorrect data to be entered into the system.

• Approve register changes without proper supervisory approval.

7. Prerequisites

1. Before the Campaign or Related Event Starts

• Ensure all workers, including supervisors as per the microplan, are created in the system.

• Complete all worker validations as outlined in Section 6.

• Confirm that all attendance registers are created and assigned to the appropriate attendance markers and proximity supervisors.

• If payment reports need to be generated mid-event, make it as two separate attendance registers for the event: one for the first half and another for the second half.

• For different wage amounts across specific boundaries for the same role, create separate roles with the appropriate wage amounts and assign workers accordingly.

• Verify that all attendance markers and proximity supervisors can log in and view their assigned attendance registers.

1. During the Campaign or Related Event

• Mark attendance diligently for each register daily using the HCM application.

• Perform routine syncs to ensure no unsynced records remain, particularly upon event completion.

1. After the Campaign Starts or Ends

• Ensure no registers are pending approval by proximity supervisors.

• Verify the accuracy of the worker and register details before generating the payment report.

• Confirm that payment registers are created for all boundary levels and individual boundaries (e.g., districts, province, country).

8. Process Flows

1. Overall process flow diagram:

1. Proximity supervisor workflow

On the language selection screen, select the preferred language from the available options. Select the desired language and click on ‘Continue’ to access the login page.

On the login page, enter the credential for a proximity supervisor and select the assigned boundary. After reading through the privacy policy statement, select the checkbox to accept the terms and conditions and then click on ‘Continue’ to proceed to the landing page for proximity supervisor.

On the landing page for a proximity supervisor, the ‘Payments’ label is displayed along with an option to view the "Attendance Registers". Click on the "Attendance Registers" label to access project-specific attendance registers.

Select the desired project name (event name) from the available options in the dropdown and click ‘Next’ to proceed.

Following the selection of the project name, you will be navigated to the ‘Inbox’ screen, where by default no attendance registers are shown. To view attendance registers, a desired boundary must be selected through a boundary filter (in this case ‘District’). Once the desired boundary is selected, click on ‘Apply’ to proceed.

Post selection of a desired boundary, you will be directed to a screen that shows all the "Pending for approval (#)" and ‘Approved (#)’ attendance registers that have been created within that specific boundary, with "Pending for approval (#)" registers being the default viewing option. ‘Approved (#)’ attendance registers can be accessed through toggling. Based on the status type (either pending for approval or approved), further discretised information is provided in a tabular format which includes the following: Attendance ID, Attendance marked by, Boundary, and Number of attendees.

Clicking on the "Attendance ID" on the ‘Inbox’ page will open the "View Attendance" screen, which will provide all the campaign-related details of the registrant and their attendance summary. The ‘Action’ button present on the bottom right of the screen allows the proximity supervisor to either "Edit Attendance" or ‘Approve’ the submitted data.

On clicking "Edit Attendance", a warning message is displayed informing the proximity supervisor that editing the attendance days data will impact the payments and the same will be frozen for the entire event duration, followed by a confirmation question. This means that if the field supervisor marks the attendance for any further dates, it will not be updated in the register. The proximity supervisor can decide to either ‘Proceed’ to update the attendance data or select ‘Cancel’ to go back to the "View Attendance" page. Click on ‘Proceed’ to confirm the editing of the attendance data.

Next, the "Edit Attendance" page is displayed which will allow the proximity supervisor to update the attendance data for each field supervisor with the help of the ‘+/-’ buttons, or they can enter the count directly within the data entry field. The ‘Submit’ button is disabled until the proximity supervisor updates the attendance for at least one field supervisor.

If the "number of days worked" entered exceeds the event duration while updating, an error message will be shown informing the proximity supervisor about it. The system allows marking the number of days as 0, accommodating those who may not have participated for the entire duration of the event.

Once the new attendance data has been entered, click on ‘Submit’ to proceed.

Subsequently, a toast message is displayed indicating that attendance has been updated successfully. The attendance data can be modified as many times as required until it is approved.

Following the successful submission of the new data, the "View Attendance" page will automatically appear, where the updated attendance data is reflected.

Now, click on the ‘Action’ button and then select the ‘Approve’ option. This will open a dialog box, where mandatory comments should be provided to proceed with the approval process which is continued by clicking again on ‘Approve’. The approval process can also be cancelled at this stage by clicking on ‘Cancel’.

After submitting the mandatory comments, if the ‘Approve’ option is selected, then a confirmation popup will appear with a message highlighting that the data once approved cannot be modified.

On clicking again on ‘Approve’, a success screen will be displayed for the confirmation, and the muster roll will be generated and displayed on the screen. Following this, any other assigned tasks can be carried out by clicking on "View Another Register" or "Go Back to Home".

On the ‘Inbox’ page, the status of the register can now be seen as approved, and when it is opened, no actions are available, except to "Go Back".

1. Payments approver workflow

The payment approver is responsible for generating and downloading the final payment bill which is further used to disburse the payments to all the campaign workers.

On the language selection screen, select the preferred language from the available options, and click on ‘Continue’.

Next is the login page, where the credentials for a campaign supervisor are entered and the assigned boundary is selected. After reading through the privacy policy statement, select the checkbox to indicate acceptance. Then click on ‘Continue’ to proceed.

This is the landing page for a campaign supervisor. On this page, a card is displayed for payments with the options to go to the ‘Inbox’ page to generate bills and to "My Bills" to view and download already generated bills. Click on ‘Inbox’ to proceed.

On this page, the project name (event type name) from the available options must be selected, as well as the aggregation boundary details; whether the bill should be aggregated at the national, province/state, or district level. Select the required aggregation boundary level and click on ‘Next’.

Following this, the "Bill Inbox" page will appear, where the specific boundary should be filtered for which the bill has to be generated. Once selected, it will display all the attendance registers, both approved and pending approval, which can be only viewed by the campaign supervisor, along with an option to generate the bill. Click on "Generate Bill".

The campaign supervisor will be able to generate the bill only once for a particular boundary, and this can be done only when all the registers within that boundary have been approved.

On clicking "Generate Bill", a confirmation pop-up is displayed that indicates that the bill cannot be generated again. Click on "Generate Bill" to proceed.

This will initiate the bill generation process along with displaying a toast message highlighting the wait time for completion of the process. Click on "My Bills" to proceed.

Clicking on "My Bills" will display the bill inbox page, where all the generated bills can be found. On this page, bills can be searched by the ‘Bill ID’ or a date range based on the date they were generated. The bills which are still being generated can be identified in the ‘Actions’ column.

Once the bill has been generated successfully, it can be downloaded as either an Excel file or a PDF by clicking on the respective action button. Choose the required format for the report to be downloaded.

An illustration of the PDF report is given below. The report provides the following information: total amount to be processed, details of each individual, different cost heads that are applicable based on the assigned role, and the sum of the amount to be paid based on the number of days attended.

9. FAQs

1. What are the different types of roles available in the HCM payments module There are two different types of roles that have been made available in the HCM payments module version 1.

a. Proximity Supervisors

They are responsible for making changes in the attendance registers as well as approving them.

b. Payment Approvers

They are responsible for generating the bills and are authorised to download them in Excel/PDF formats for further processing.

1. What is the workflow of the payments module in the HCM platform? In the HCM platform, the payments module is coupled with the attendance module. The typical workflow diagram is provided in section 8:

2. How to mark attendance in the HCM platform? There is a dedicated attendance module available in the HCM platform to allow field supervisors to mark the attendance of their team members.

3. What is an attendance register in the HCM platform? An attendance register is a record-keeping tool that is used to track the count of present or absent campaign workers, along with their activities such as training, registration/distribution, etc.

4. How can a proximity supervisor edit an attendance register? User Navigation: Login > Home Page > Attendance Registers > Select Project Name > Select Boundary > Click on Attendance Register in ‘Pending for Approval’ state > View Attendance > Action: Edit Attendance > Warning Message: Proceed > Edit Attendance > Submit > Success Message. (Note: You can edit the attendance as many times as required till it is approved).

5. How can a proximity supervisor approve an attendance register? User Navigation: Login > Home Page > Attendance Registers > Select Project Name > Select Boundary > Click on Attendance Register in ‘Pending for Approval’ state > View Attendance > Action: Approve > Add Comments and Approve > Confirmation: Approve > Success Screen (Note: Once approved, you cannot take any further action on the register)

6. What are approved and unapproved registers? Approved registers are those that are marked as approved by the proximity supervisors, and they cannot take any further action on these registers. Unapproved registers are the ones that are submitted by the field supervisors to be approved by the proximity supervisor, and their attendance details can be updated by the proximity supervisor before approval.

7. How can I select a different type of attendance register? The first step as a proximity supervisor is to select the type of attendance register from the drop-down after logging in to the payments module. There will be multiple types of registers such as Master Training register, Registration team training, Campaign, etc.

8. As a proximity supervisor, I have selected one of the districts as a boundary. Which attendance registers can I manage? You can manage only those registers assigned at the selected district or boundary levels below the district.

9. As a payments supervisor, I have selected the country name. Which muster rolls can I generate the payment report for?

You can generate the payment report for all the muster rolls that are assigned at a county level.

1. As a payments supervisor, I have selected a province name. Which muster rolls can I generate the payment report for?

You can generate the payment report for all the muster rolls that are assigned at a province level.

1. As a payments supervisor, I have selected a district name. Which muster rolls can I generate the payment report for?

You can generate the payment report for all the muster rolls that are assigned at a district level or below the district level.

1. What is a muster roll in the HCM payments module? A muster roll is a simple document used to keep track of workers and their activities. It records who showed up for work, the hours they worked, and sometimes their pay. It helps employers know who was present and how much work was done. In campaigns, a muster roll can track attendance and ensure workers are paid correctly for their efforts.

2. What is an event? In the context of attendance for a campaign, an event refers to a specific activity or session where workers or participants are expected to be present. This could include training sessions, daily fieldwork (registration/distribution), or any other scheduled task as part of the campaign.

3. When should I approve an attendance register? You must wait for the event to be completed to review and approve the attendance register.

4. Is it advisable to approve a register before an event is completed? What happens if I edit attendance during an ongoing event? Always approve the attendance register only after the event has fully concluded to ensure data accuracy. Editing attendance during an ongoing event will overwrite the current records, and the system will consider the edited data as final. Additionally, if the attendance register has been edited and approved, attendance markers attempting to record attendance will encounter errors, as there is no downward data flow from the proximity supervisor to the attendance marker

5. Which formats can I download the payment report in? The reports are available for download in Excel and PDF formats.

6. How can I view and download the bills I generated? Navigation: Login > Home Page > My Bills > Actions (Download in Excel/PDF)

7. Can I create bills again for already generated muster rolls?

No, you cannot regenerate bills. However, you can view the generated bills as well as download them as many times as needed.

1. How long will it take to generate a bill? The bill generation can take up to 2-3 minutes depending on the number of registers collated.

2. How can I aggregate muster rolls into a single bill? Is aggregation mandatory? At what levels can aggregation occur?" Aggregation of muster rolls can be done at different boundary levels, as described below: District Level: Muster rolls from all events created at the district or subordinate levels are aggregated for the selected event type. Example: Aggregating muster rolls for all registration events in the district of Nampula, including those at locality levels within Nampula. Province/State Level: Muster rolls from events across the entire province/state are combined. Example: Aggregating all muster rolls for distribution events across the province of Cabo Delgado. National Level: Muster rolls from events nationwide are collated. Example: Aggregating muster rolls for all master trainer training conducted at the national capital in Mozambique. Aggregation is separated at various levels to ensure there are no duplications of bills generated for the same registers

3. What should I do if bill generation fails?"

• Wait for some time and try generating the bill again.

• Check that all attendance registers have been approved.

• If the issue persists, contact the system administrator for assistance.

1. Can I edit the Excel sheet of the payment report? Payment report sheets are protected and cannot be directly edited. If edits are necessary, duplicate the sheet and make the required changes. Ensure that any modifications are made only with the approval of the respective supervisory authority.

2. How can I change the payment rates for specific roles? If certain roles require different payment rates, you need to define those roles separately and assign individuals accordingly. If people in the same role working across different boundaries need different rates, create distinct roles for each boundary. Ensure any changes are made before generating bills

3. Can I assign different payment rates to the same role for different boundaries? No, the system currently supports assigning rates based on roles, which must remain consistent across all boundaries.

4. How can I generate an intermediate payment report before the event is completed? The current version of the module does not support generating intermediate payment reports during an ongoing event

10. Appendix Attendance Management

The Attendance Module enables supervisors to track attendance for their attendees, ensuring accurate records and consistent data for processing payments. This serves as the precursor to the Payments module. For more details, click here.

Steps to Use Community Living Facilities

Boundary Selection

There are 3 scenarios

1. The user is assigned to work at a community living facility.

2. The user is assigned to work at both a community living facility and house-to-house.

3. The user is assigned to work at house-to-house.

Home Screen

- Separate navigation for community living facilities/ based delivery, transit post-based delivery, and household-based delivery.

- Clicking on the cards will navigate the user to the respective flows.

- The community living facilities/transit postcards will be available depending on the campaign requirements.

- The progress bar will cater to the number of beneficiaries covered in household + community living facilities (Transit post coverage will be monitored separately since this is not included in the microplan).

Search CLF screen

Clicking on the community living facilities icon navigates the user to the search page. This screen is as same as we have in the product.

• A toggle is enabled to search the nearby CLF.

• Search bar: All the loaded CLF from the microplan can be searched from here.

• Filter (as same as in product).

There can be multiple categories of Communal living facilities. For example:

Boarding schools

Military camps

Orphans

Retirement home

University campus

Prison

Police camps

Refugee camps

Search CLF screen with search results

• When the user searches for the respective CLF, a card with the name of the CLF along with the proximity is displayed.

• There is an action button to open the CLF.

Search CLF - Match not found

The behavior of the screen remains the same as we have in the product but when searched for a CLF and if a match is not found then it shows the info message related to CLF.

Filter

This will be a multi-select filter. These are the filters that need to be added: Administered - intervention given Not Administered - Intervention pending Refused - Beneficiary declined intervention Ineligible -Beneficiary does not meet criteria Referred - Beneficiary directed to another facility or service When clear is clicked, all the selected filters must be removed.

CLF Location

Here we capture the location details of the CLF. This is where we capture geo-coordinates for the respective CLF.

CLF Details

In this screen, the type of structure of the facility is selected using the card layout. The number of rooms in the facility is also captured using the +/- counter.

Capturing these details will help to build the facility details in the registry and the data can be reused for campaigns such as Indoor Residual Spraying.

Individual Details In this screen, the details of the individual residing in the facility are captured which include:

• Name of the individual

• ID type

• ID number

• Date of birth / Age

• Gender

• Mobile number

• Scan voucher / ID

Clicking on the scan voucher will open the camera to scan the QR code on the voucher.

Once the voucher is Linked, clicking on ‘Submit’ will take the user to the Summary screen.

There is a warning pop-up message asking the user if they are ready to submit. Once submitted, a success toast message will be shown.

The data thus captured can be down-synced and used for another campaign in the future and can be also edited or updated if required

Search results with the filter

Once the beneficiaries are added to a facility, they can be filtered based on the administration status of the intervention. Once the filter is selected and the user clicks on “Apply Filter”, the beneficiaries screen is displayed with the applied filter displayed. The Individual filters can be removed from the same screen when clicking on the cancel button next to the respective applied filters.

Assess Eligibility

The Assess Eligibility screen opens when one clicks on the “Assess Eligibility” button. This screen will have a set of questions to assess the eligibility of the individual - this is particular to an individual campaign.

Deliver Intervention - Individual campaigns

The beneficiary details screen is opened when one cicks on “Record Delivery” where we record the administration for any type of individual-based campaign. For example: NTDs , SMC, and Polio.

Deliver Intervention - household campaigns

The beneficiary details screen is opened when one clicks on “Record Delivery” where we record the delivery for any type of household-based campaign. For example: Bednet.

Summary Screen - CLF

Deliver Intervention - Data gets pre-loaded from microplan

Click on the delivery card, and search for the CLF with the name. Since all the data would be pre-loaded, when down-synced, we will get the necessary information for the respective CLFs.

Deliver Intervention - When the data is not pre-loaded

When the data is not pre-loaded from the microplan, then the delivery will depend on the registration, and the delivery screens will remain the same.

Transit Post

- The KPI indicators show the deliveries completed for the current data and cumulative for that user. The following details are captured:

• Type of transit post (master data)

• Name of transit post (user input)

Scan resource

The resource is scanned using the scanner feature. The scan feature should be configurable such that for interventions where any codes are not available, the screen will jump to the delivery page without scanning.

Manual entry

Enter the resource code if the scan does not work due to any reason.

Deliver Intervention

- The screen shows:

• The number of deliveries for the transit post selected

• The transit post details

• The resource to be delivered

• Eligibility conditions

• Resource details scanned

Clicking on record delivery will count toward the delivery of one beneficiary. The process is repeated until all beneficiaries are administered. Clicking on close delivery will complete the deliveries for the selected transit post.

Upon successful scan, the user must see a flash acknowledgment screen, which must be available for a configurable duration, and must take the user back to the "Vaccination Details" screen. This process will be repeated until the user closes the delivery.

The support features enhance user satisfaction, promote ease of use, and contribute to the app's overall effectiveness in facilitating seamless interactions and data management

Click on the links below to learn more:

• Language Selection

• Login

• Forgot Password

• Project Selection

• Hamburger Menu

• Help

• Sync

Allows users to select their preferred language for the app UI. It enables users to easily switch between the languages, which enhances the user experience.

Key Feature

• Select between Portuguese, French, and English languages.

Using Language Selection

When the user opens the application, it asks them to first select the language. The selected language is highlighted in orange color.

On this page, the following actions can be performed:

• A user can switch the language by clicking on Portuguese, French, or English.

• A user can click on 'Continue' to navigate to the login screen.

Key Feature

Log in to the HCM app with user ID and password.

Using Login

Users are redirected to this screen once they select the preferred language in the previous screen.

On this page, the following actions can be performed:

• A user can log in to the app by giving the User ID and Password.

• The "Forgot Password" button gives a user the option to contact the administrator to reset if he/she has forgotten the password.

Using Forgot Password

Users are redirected to this screen once they click on the "Forgot Password" button in the language selection screen.

Clicking on the forgot password option in the login page opens a popup message “Please contact your administrator if you have forgotten your password”. This is an informative popup which does not lead to any further action within the application and the user can close the popup by clicking on 'OK'.

Key Feature

After a user logs into the HCM app, the project selection screen displays all the projects assigned to the user. This will be displayed only when a user is assigned to multiple projects.

Using Project Selection

On this page, the following actions can be performed:

• A user has to select one project.

• After selecting a project, the system downloads the data for the selected project only.

• After every login action, the system will automatically sync the data with the system.

• Since the user will log in only at the start of the day and before going into the field, there must be stable internet connectivity for the device to perform this process.

• A “Sync in Progress” window appears on the screen and the user cannot perform any other action until the process is complete.

After clicking on the hamburger button, a list of actions appears on the user screen. The top displays the user name and contact number, followed by other options such as the home button, language select, edit profile, projects, and logout.

If the user clicks on the hamburger button again, it collapses the hamburger menu. The button is available on all screens of the application.

Edit Profile

The user can edit his/her name, and phone number, and select the gender. After updating the details, the user needs to click on the save button which opens a prompt stating “saved successfully”.

If the user does not want to make any changes, he/she can click on the back button, which will take them back to the hamburger menu.

After logging into the application, the user lands on the home screen of the HCM app, which displays the 'Help' button on the top right.

Using the Help Button

If the user clicks on the help button, it will give a walkthrough of the entire screen, including the role of each button placed with two buttons:

• Skip: If the user wants to skip the walkthrough at any point.

• Next: It will proceed to the next action aligned.

The text box appears at the bottom of the button.

Brief Intro

Sync action allows users to sync the data that is recorded in the system so that it reaches the server and the data is secured.

Using Sync

Before going into the field, the user needs to log into the application every day, which will initiate an automatic sync process. For manual sync, there is a "Sync Data" button on the home screen, which allows the user to sync data according to his/her convenience. At the bottom of the screen, there is a card that shows the message “Data unsynced” along with the number of records unsynced.

When the user clicks on the ‘Sync’ button, the sync action starts along with an overlay showing “Sync in Progress” over the home page. The user cannot perform any other action until the sync is complete or there is some error.

Sync Status

Once the data is synced, it will show a popup, stating “Data Synced” along with a ‘Close’ button at the bottom. When the user clicks on 'Close', it navigates him/her to the home screen.

If the data is not synced due to any error, it will show a popup stating “Sync Failed” with two buttons below it:

1. Retry: If the user wants to retry syncing the data.

2. Close: Clicking on this will navigate the user back to the home screen.

Brief Intro

Checklist is a tool that enables supervisors to monitor certain activities and record observations according to defined set of questions.

Features

• Allows users to observe the tasks and fill checklists.

• View all the submitted responses for the checklists.

User Roles

Using Checklist

The "My Checklist" screen allows supervisors to perform random or scheduled inspections, and record observations of the inspection activity.

On this page, the following actions can be performed:

• Clicking on "My Checklist," will display the checklists assigned to the user role.

• Clicking on any checklist will show a popup with

- Fill Checklist

- View Submitted Checklists

• The "Fill Checklist" option will allow the supervisor to fill the checklist against the date and the administrative area.

• The "View Submitted Checklists" will show the checklists submitted by the supervisor.

The Campaign Management Dashboard offers a wide range of features that deliver a comprehensive view of campaign performance. It empowers supervisors to easily monitor their teams, assess campaign progress, and quickly address any obstacles that may arise.

The Dashboard equips campaign supervisors with real-time insights to evaluate their teams' effectiveness and make data-driven decisions for optimising campaign performance. Featuring intuitive visualisations and customisable metrics, supervisors can easily track key performance indicators (KPIs) such as campaign coverage, engagement, and inventory movement. The Dashboard also provides a comprehensive view of team productivity and individual performance, enabling supervisors to identify top performers and areas that may need additional support. With these powerful tools, supervisors can efficiently monitor and manage their teams, ensuring the success of the health campaign.

The Dashboard's intuitive interface makes tracking campaign progression seamless for supervisors. They can effortlessly monitor campaign milestones, goals, and progress against predefined targets, allowing them to assess the campaign's overall health and take corrective actions when necessary. Moreover, the Dashboard offers historical and predictive data, along with trend analysis, enabling supervisors to identify patterns and make data-driven decisions to optimise strategies for future campaigns. With these powerful features, supervisors can effectively analyse campaign performance and continuously refine their approach for maximum impact.

Apart from performance tracking, the dashboard provides campaign supervisors with efficient tools to troubleshoot roadblocks. It promptly highlights any issues or bottlenecks that may impact campaign progress, allowing supervisors to quickly identify and address them. Additionally, supervisors can drill down into specific boundaries, such as villages, to pinpoint areas that require attention and proactively take measures to resolve challenges. With these capabilities, supervisors can effectively overcome obstacles and ensure smooth campaign execution at all levels, from a macro to a micro level, to achieve desired outcomes.

The HCM Dashboard is purposefully designed to be user-friendly, with an intuitive and easy-to-navigate interface that requires minimal training to get started. Its robust features and user-centric design empower campaign supervisors to efficiently monitor, evaluate, and troubleshoot campaign performance. With this powerful tool, supervisors can effectively drive the success of their health campaigns, making informed decisions and taking corrective actions as needed. The HCM Dashboard is a valuable asset for campaign supervisors, ensuring a seamless and effective management of health campaigns.

The following are the features of the HCM Dashboard:

• Bar charts with percentage and number toggle.

• Brush component for bar charts to zoom in and out for an enhanced view.

• Heat maps with zoom-in/out, toggle, and drill-downs to show coverages.

• Date range selection through the calendar date picker and toggle buttons to select ‘Today’ and ‘Cumulative’ date ranges.

• A new component to display the list of cards based on the chart data, and includes a collection of numeric data and a circular progress bar.

• Predictive line graphs to show planned versus actual campaign progression.

• Multi-campaign card layout to view campaigns of multiple types happening simultaneously.

• Progress bar to show the campaign duration.

• Tabular charts with drill-down, search, toggle, and sort functionalities.

• Pie charts with the aggregation are shown at the centre.

• Stacked bar charts.

• Hover definitions and sub-headings to show more details about a specific card.

• Download all charts and pages in PDF and JPG formats.

• Share all charts and pages in PDF and JPG formats across WhatsApp and email.

The DIGIT HCM comes up with an out-of-the-box dashboard that helps the supervisors who manage the campaign to view real-time campaign indicators such as coverage that helps in making data-driven decisions.

Key Features

• Download charts in PDF or JPG format.

• Share charts via WhatsApp or email.

• A diverse range of charts and graphs for visualising key metrics.

• Drill-down functionality for detailed data examination.

• Multi-language support.

• Geographic boundary-based heat maps.

• View data across multiple campaigns via a single dashboard.

• Geo-coordinate map to view delivery data at the household level.

• Restrict data access based on user hierarchy.

• Tab navigation across modules.

• Predictive charts to forecast campaign extensions and stock availability.

• Custom Excel reports for in-depth analysis.

• Filter and sort tables.

• Vewi data for custom date ranges or specific campaign cycles.

User Roles

The dashboard data will be tailored according to the user's hierarchical boundary, ensuring access is aligned with their operational scope. For instance, a national supervisor will oversee campaign operations nationwide, while a district supervisor will solely access data within their designated district, without visibility into other districts.

Using the Dashboard

To access the dashboard, open your browser and enter the URL [ ]. Log in with your credentials and click on submit.

After logging in, you will land on a page listing all campaign dashboards. This page also includes About and FAQ sections, and a link for downloading custom Excel reports.

To view a specific campaign's dashboard, click on the campaign name.

National Level View

If you are a national-level supervisor, the initial page you see is a national-level view. Here, you can monitor the campaign's progress across various sub-national boundaries, including aggregates of households, population, and service deliveries.

To navigate to a sub-national level dashboard, click on the ‘View Dashboard’ button next to the sub-national boundary name.

Modules

The dashboard is divided into several tabs based on campaign modules: Registration & Delivery, Inventory, Complaints, and Supervision.

• Registration & Delivery module: Displays indicators related to registration, including coverage metrics and charts for households, population, and service delivery.

• Complaints module: Shows the status of various complaints, types, resolution times, and details of each complaint.

• Inventory module: Provides insights into stock status across all warehouses and predicts stock-out scenarios.

• Supervision module: Evaluates supervisors' performance in monitoring campaigns using checklists.

Features

• Date Filters: Each page has filters to view data for a specific date range, today's data, or cumulative data since the campaign's start.

• Campaign Progress: A progression line at the top displays the number of days since the campaign began.

• Data Completeness: The sync rate chart indicates how many users have synced data so far.

• Drill-Down Charts: Double-click on any bar to drill down to sub-boundaries, continuing until the lowest level (e.g., a village). To return to the previous view, click the 'x' button.

• Toggle Chart Views: Switch between percentage and absolute values by clicking toggle buttons.

• Prediction Line Chart: Estimates how many more days are needed to reach target coverage based on current service delivery rates.

• Sortable Tables: Summary tables can be sorted by column in ascending/descending order or alphabetically.

• Download Options: Each chart can be downloaded as a PDF or JPG by clicking the kebab button. Charts can also be shared via WhatsApp or email. Tabular charts can be downloaded as Excel files.

• Brush Component: Use the brush component below bar charts to expand or contract the view to see all represented boundaries.

• Heat Maps: Monitor campaign progression by boundary through interactive, drill-down heat maps.

• Geocoordinate maps: To view each household-level service delivery data.

The Geo Json assets files need to be loaded to s3 bucket and the reference urls need to be mapped in map-config.GeoJsonMapping mdms schema data.

To configure dashboard links, add the dashboard URLs to the project type in MDMS

For the campaign, the required charts should be added to the dashboard-analytics chart configuration.

The UI configuration can be loaded into the MasterDashboardConfig within the dashboard-analytics.

Overview

This Node.js service acts as a reverse proxy for Kibana, enforcing authentication and access control based on specific rules. It validates requests using DIGIT’s authentication API.The service utilizes express, express-http-proxy, and axios for proxying and API interaction.

Setup & Configuration

The service relies on environment variables defined in envVariables for key configuration. These variables include:

These configurations can be overridden by environment variables, and they include:

• SERVER_PORT: The port on which the Node.js service will run.

• EGOV_USER_HOST and EGOV_USER_SEARCH: The host and path for the external authentication API.

• KIBANA_HOST and KIBANA_BASE_PATH: The Kibana server URL and base path.

• KIBANA_ACCEPTED_CONTEXT_UI_PATHS: List of valid context paths for referer validation.

• KIBANA_ACCEPTED_DOMAIN_NAME: Domain name allowed for Kibana access.

• KIBANA_EXCLUDE_URL_PATTERNS: URL patterns excluded from authentication.

Deployment Configuration

Helm Charts

Build Details

Auth-Proxy : auth-proxy-urlencoded-fix-aad9a5959c-23

Overview

Supervisors can use the real-time dashboard to monitor campaign activities and track coverage, enabling them to make informed, data-driven decisions.

Existing Capabilities

• Download charts in PDF or JPG format.

• Share charts via WhatsApp or email.

• A diverse range of charts and graphs for visualising key metrics.

• Drill-down functionality for detailed data examination.

• Multi-language support.

• Geographic boundary-based heat maps.

• Geo-coordinate map to view delivery data at the household level.

• Restrict data access based on user hierarchy.

• Tab navigation across modules.

• Predictive charts to forecast campaign extensions.

• Filter and sort tables.

• View data for custom date ranges or specific campaign cycles.

New Capabilities

• Side-by-side bar chart visualization for more than 2 variables

• Venn diagram for inter-cycle analysis

• Filter data by cycles

User Roles

The dashboard data will be customized based on the user's hierarchical level, ensuring access is aligned with their specific operational scope. For example, a national supervisor will have oversight of the entire campaign at the national level, while a provincial supervisor will have access to data within their assigned province, and a district supervisor will only have access to data within their assigned district, with no visibility into other districts.

Steps to use the SMC Dashboard

To access the dashboard, open your browser and enter the URL [ ]. The language selection screen will appear, select the preferred language and click on ‘Continue’. You will navigate to the ‘Login’ page. Log in with your credentials and click on ‘Continue’.

After logging in, you will land on a page listing all campaign dashboards.

Click on the dashboard. If you are a National Supervisor, the landing page you will see is the national overview page.

To navigate to a sub-national level dashboard, click on the ‘View Dashboard’ button next to the sub-national boundary name.

Modules

The dashboard is divided into several tabs based on campaign modules: Registration & Delivery, Inventory, Complaints, Supervision, Team Performance, Data Quality, and Referral and Side Effects.

Features

Date Filters: Each page has filters to view data for a specific date range, today's data, or cumulative data since the campaign's start.

Campaign Progress: A progression line at the top displays the number of days since the campaign began.

Filter by cycle: This allows you to view and analyze data for specific treatment cycles in the seasonal malaria chemoprevention campaign. Since children are treated in multiple cycles, this filter helps you focus on performance and coverage for a particular cycle, making it easier to track progress and identify gaps.

Drill-Down Bar Charts: Click on any bar to drill down to sub-boundaries, continuing until the lowest level (e.g., a village). To return to the previous view, click the 'x' button.

Drill-Down Table Charts: Click on any boundary in the table to drill down to sub-boundaries, continuing until the lowest level (e.g., a village). To return to the previous view, click the 'x' button.

Drill-Down Pie Charts: Click on any slice in the pie chart to drill down to sub-categories or data split across sub-boundaries. To return to the previous view, click the 'x' button.

Prediction Line Chart: Estimates how many more days are needed to reach target coverage based on current service delivery rates.

Geocoordinate maps: To monitor distributor coverage and track supervisor performance, the system uses the geographic coordinates of completed checklists. On a zoomed-out map, the coordinates are grouped into clusters for easier viewing. By clicking on a cluster, users can see details such as the total number of points in the cluster and information about the supervisors who recorded the data. This makes it easy to track performance and coverage across different areas.

Side-by-side comparative bar charts (2 variables): The side-by-side bar charts enable a clear comparative analysis between two distinct variables, making it easier to identify differences and trends. For example, they can be used to compare coverage by gender concerning population distribution. Additionally, side-by-side bar charts can visualize the comparison between expected stock levels and actual stock balance. This provides a clear view of inventory management, helping supervisors determine whether stock levels are in line with the campaign’s needs, or if there are discrepancies that could lead to shortages or overstocking.

Side-by-side bar chart (More than 2 variables): This layout allows supervisors to view multiple relevant variables simultaneously in a single, unified chart. By displaying these indicators next to each other, supervisors can easily compare and analyze the data across different dimensions, such as age categories, referral summary, and stock movements. The ability to view all relevant variables at once enhances efficiency, allowing for quicker identification of trends, patterns, or areas requiring attention.

Stacked bar charts: Stacked bar charts are an effective tool for visualizing the distribution of data across multiple variables, allowing for easy comparison and analysis. For example, a stacked bar chart can display the number of complaints filed within each operational boundary (district), grouped by factors such as the type or status of the complaint (pending, resolved, rejected).

Similarly, the chart can be used to show the types of side effects recorded during the campaign, with the side effect categories stacked vertically for each boundary. This enables stakeholders to easily identify trends, compare performance across regions or cycles, and pinpoint areas that may require further attention or intervention. By clustering data in this way, the chart provides a clear, comparative view that helps drive data-driven decisions and enhance campaign efficiency.

Venn diagram for inter-cycle analysis: The Venn diagram on the dashboard visually represents the overlap and distribution of inter-cycle children administration data. It illustrates the number of children who received treatment across different cycles, highlighting:

• Cycle 1: Children treated in the first cycle.

• Cycle 2: Children treated in the second cycle.

• Overlap: Children who received treatment in both cycles.

This diagram helps identify the extent of coverage across different cycles and ensures that children who need multiple rounds of treatment are properly accounted for. It provides a clear visual of treatment gaps and overlaps, supporting efficient campaign management and decision-making

Click here to learn more.

Click here to learn more.

Purpose of the module

The primary purpose of this module is to streamline attendance review and payment processing workflows for health campaign workers. It ensures that supervisors can:

• Access tools and functionalities tailored to their responsibilities.

• Maintain clear separation between proximity- and campaign-specific workflows.

• Facilitate accurate, timely payments for healthcare workers based on attendance.

Flows Overview

1. Proximity Supervisor Flow

This flow focuses on managing attendance records within a specific boundary assigned to the logged-in proximity supervisor.

Key Actions:

• View attendance: Filter, search, and view attendance data.

• Edit attendance: Modify attendance entries for accuracy.

• Approve attendance: Validate and approve attendance registers for payment processing.

2. Campaign Supervisor Flow

This flow supports campaign-wide bill generation.

Key Actions:

• View registers: Access to view registers to generate bills.

• Download reports: Export reports in Excel/PDF formats for stakeholder communication.

• Generate bills: Create bills based on three boundary levels: Country, Province, and District.

• If the boundary is set to a district, all the registers within that district will be consolidated into a single bill.

The Proximity Supervisor Flow for managing attendance registers is designed to provide supervisors with a seamless experience for selecting projects, viewing associated attendance records, and managing the details effectively. The flow emphasizes ease of navigation, quick access to project and register information, and actionable steps to edit or approve attendance records.

Core Features

• Project Selection: Enables supervisors to pick a specific project to manage.

• Registers Inbox: Displays filtered attendance registers for selected boundaries.

• View Attendance: Provides detailed attendance information for campaigns and projects.

• Edit Attendance: Allows supervisors to update attendee records.

• Approve Attendance: Facilitates approval with clear validation and comment requirements.

Each step in this flow ensures user-friendly interactions and adheres to the necessary validation rules and role-based permissions for supervisors and project managers.

Note: In Payments version 0.1, each user will be associated with only one project.

Sequence Diagram

Interface Elements:

User Actions Flow:

1. Select a Project: Choose a project from the dropdown list.

2. Proceed to Next Screen: Click "Next" to access the registers associated with the project.

Overview: Enables supervisors to view attendance registers filtered by selected boundaries (e.g., district).

Interface Elements:

User Actions Flow:

1. Select Boundary: Choose a district from the dropdown.

2. Apply Filter: Click "Apply" to filter results.

3. View Results: Access filtered attendance registers for the selected district.

API Endpoints:

Clicking on any register ID from the inbox displays detailed information about the attendance register. The screen includes information such as campaign details, attendance officer details, and attendee information. Users can perform two primary actions: Edit and Approve.

Interface Elements

• Campaign Details: Displays the campaign name, ID, and dates.

• Attendance Officer Details: Name, ID, and contact information.

• Attendee Information: Includes register ID, attendee names, and attendance data.

• Action Buttons:

  • Edit Attendance: Allows editing attendance details.

  • Approve Attendance: Approve the attendance register.

Interface Elements:

Validations and Conditions

1. Campaign Status:

   • If the campaign is ongoing, Edit and Approve buttons are disabled, and only a "Back" button is shown.

   • Administrators can override this behavior through MDMS (configurable settings).

2. Approved Registers:

   • If the register is already approved, the action buttons are disabled, and a "Back" button is displayed.

3. Role-Based Permissions:

   • Only authorized supervisors can access Edit/Approve features.

Action Flows

1. Edit Attendance Flow

a. Step 1: Pop-Up Confirmation

• Message: "Editing attendance will affect the number of days for attendees. Do you want to proceed?"

• Buttons:

  • Cancel: Close the pop-up.

  • Proceed: Navigate to the Edit Attendance screen.

b. Step 2: Edit Attendance Screen

• Validation:

  • Number of days worked must be a positive integer and must not exceed the event duration.

• Submit Button Behaviour:

  • Initially disabled until changes are made.

  • Upon submission:

    • Displays a success message: "Attendance updated successfully!"

    • Displays an error message if the update fails.

1. Approve Attendance Flow

   1. Step 1: Add Comment

      • Message: "Please add a comment before approving."

      • Input Field: Allows users to enter comments (mandatory).

      • Buttons:

        • Cancel: Closes the pop-up and returns to the view screen.

        • Submit: Proceeds to the final warning.

1. Step 2: Confirmation Pop-Up

   • Message: "Do you want to approve this attendance register?"

   • Buttons:

     • Cancel: Closes the pop-up and remains on the view screen.

     • Proceed: Opens a Comment Entry Pop-Up.

1. Step 4: Success Page

   • Message: "Attendance approved"

   • Action: view another registers or go back to home.

The Campaign Supervisor Flow is designed to streamline the management of attendance registers and bill generation processes for supervisors overseeing specific projects and boundaries. This flow ensures efficient selection, filtering, and approval of registers and simplifies the generation and tracking of bills. It focuses on clear workflows, actionable feedback, and validation mechanisms to enhance usability and accuracy.

Core Features

• Project and Bill Aggregation Selection: Supervisors select a project and boundary aggregation level to narrow down the scope for attendance registers and billing.

• Registers Filtering and Bill Generation: Enables supervisors to filter registers based on boundaries, view attendance data, and generate bills only when all registers are approved.

• Bill Management (My Bills): Provides a centralised view of all generated bills, with tools for searching, filtering, and downloading them in preferred formats.

This structured approach empowers supervisors to manage attendance registers and related billing tasks with ease while adhering to necessary validations and role-based permissions.

Sequence Diagram:

This is the initial screen where the user selects:

1. Project: The specific project they are managing.

2. Bill Aggregation Level: The boundary level at which the bill should be generated (Country, Province, or District).

Users cannot proceed without filling out these fields.

Interface Elements:

User Actions Flow:

1. Use the dropdown menu to select the project.

2. Select one of the available aggregation levels (Country, Province, or District) from the dropdown.

3. Click the "Next" button to navigate to the register filtering screen.

Validations:

• Both fields are mandatory:

• If either the Project or Bill Aggregation Level is not selected, an error toast message is displayed if you try to proceed.

Purpose:

This screen allows Campaign Supervisors to:

1. Filter attendance registers based on boundaries (Country, Province, and District) tied to the selected project and aggregation level.

2. View the list of registers within the selected boundary.

3. Generate bills for the selected boundary if all registers are approved.

Interface Elements:

Filters Section

no of levels will vary based on the aggregation level selection:

• Country: Dropdown menu to select the country (e.g., Mbazi Highlands).

  • Mandatory Field: Must be selected before applying filters.

• Province: Dropdown menu to select the province (e.g., Nampula).

  • Mandatory Field: Must be selected before applying filters.

• District: Dropdown menu to select the district (e.g., Murrupula).

  • Mandatory Field: Must be selected before applying filters.

• Apply Button: Triggers the filter to display attendance registers for the selected boundary.

Register Inbox

• Project Name: Displays the selected project name .

• Aggregation Level: Displays the selected aggregation level (e.g., District level).

• Register Status Summary:

  • Approved Registers: Shows the count of approved registers (e.g., 18).

  • Pending Registers: Shows the count of pending registers (e.g., 0).

Registers Table

Displays a tabular list of attendance registers for the filtered boundary, with the following columns:

Action Section

• Generate Bill Button:

  • Enabled State: If all registers are approved, this button becomes active, allowing users to trigger the bill generation process and bill is not already generated.

  • Disabled State: If any registers are pending approval, the button remains inactive.

User Actions Flow:

1. Filter Attendance Registers:

   • Mandatory Filters: The user must select a Country, Province, and District before clicking "Apply".

   • After clicking Apply, the attendance registers for the selected boundary are displayed.

2. View Attendance Registers:

   • The filtered registers are shown in a tabular format.

3. Generate Bill:

   • The Generate Bill button is enabled only if all the registers within the selected boundary are approved and bill is not generated already.

   • Clicking Generate Bill triggers the bill generation process:

     • A confirmation pop-up appears with the warning.

     • Buttons:

       • Cancel: Returns to the register list.

       • Proceed: Starts the bill generation process.

   • A toast message will be shown whether bill generation started or failed. and a info message will be displayed with same.

Scenarios and System Responses:

1. All If all registers within the selected boundary are approved Approved:

   • The Generate Bill button is enabled.

   • Upon clicking Generate Bill, an info message is displayed: "Bill generation in progress. Please wait."

2. Bill Already Generated:

   • If all registers within the selected boundary are approved but a bill has already been generated:

   • An info message is displayed: "Bill has already been generated for this boundary."

3. Pending Registers:

   • If some registers within the selected boundary are still pending approval:

   • An info message is displayed: "Bill cannot be generated until all the registers are approved."

Validations:

1. Boundary Selection:

   • All three boundary levels (Country, Province, and District) are mandatory for filtering attendance registers.

   • Error toast massage if you click on apply without selecting all mandatory boundaries.

2. The system verifies the approval status of all registers in the selected boundary before enabling the Generate Bill button.

API Endpoints:

The "My Bills" section serves as a centralised dashboard for campaign supervisors to view and manage all bills associated with their assigned projects. By default, the dashboard displays all bills related to the projects under their supervision. Supervisors can search for specific bills or filter them using date ranges or by bill id.

Interface Elements:

Search Filters

1. Bill ID: Enter a specific Bill ID.

2. Date Range: Select a start and end date to filter bills within a specific time frame.

3. Action Buttons:

   • Search: Filters the results based on the provided criteria.

   • Clear Search: Resets the filters and shows all assigned bills.

Bill List

A table format displays the bills with the following columns:

Status Descriptions

• Generated: The bill has been successfully generated. The user can download it in PDF or Excel format.

• In Progress: The report is still being generated. The user should wait for completion.

• Failed: The report generation failed. The user can:

  • Retry the process.

  • Contact support if the issue persists.

API Endpoints: