The HCM v1.6 release does not require any migration from the 1.5 release.

Mission

Help countries achieve Health SDGs by building digital public goods that strengthen public health.

What are public health campaigns?

Health risks such as infectious diseases generally cannot be addressed at the individual and health worker levels alone. They require intervention at the policy level. This is where public health campaigns come into the picture.

Public health campaigns are specific, time-bound health services that respond to particular challenges and are provided to a target population by dedicated campaign workers. Such campaigns can influence perceptions, attitudes, and behaviors to achieve the desired goal. They can prevent or respond to disease outbreaks, control or eliminate targeted diseases, or achieve other health objectives. According to the World Health Organisation (WHO), two strains of wild poliovirus have “officially been certified as globally eradicated,” and immunisation campaigns have played a key role in this. Over the years campaigns to fight malaria, AIDS and other diseases have not only improved the lives of millions of people in poor and developing countries and disadvantaged communities, but it has also enabled them to lead more productive lives.

In 2019, 534 campaigns were tracked globally, providing vaccines, drugs, vitamins, and preventative tools for malaria, malnutrition, measles, meningitis, NTDs, polio, tetanus, typhoid, and yellow fever. However, by the end of 2020, an estimated 50% of the public health campaigns were postponed, suspended, or canceled due to the COVID-19 pandemic. This left millions of people and children at risk of vaccine-preventable diseases and malnutrition.

How can HCM help?

As health campaigns catch up on missed vaccinations, drugs, and other preventative measures globally, there is an opportunity to reimagine the way countries can plan and implement campaigns through open-source digital platforms.

Today, digital tools are either free but not fit for purpose, or they do the job but cost a fortune due to repetitive work adding to the costs. Data is locked in silos and there is no operability between systems. These tools are also difficult to sustain and scale. These realities made it clear that isolated approaches cannot do the job.

Health campaigns require a holistic digital transformation. Health Campaign Management, or HCM, was developed to address these challenges effectively.

HCM is a free, fit-for-purpose, open-source, end-to-end health campaign digitisation product. It covers campaign setup, planning, registration, service delivery, inventory management, and real-time data dashboards, enabling faster and cost-effective health campaigns. HCM is designed to evolve rapidly and adapt to local needs while addressing systemic challenges.

With HCM, all programmes — whether for polio, malaria, or measles — are unified under a single, streamlined interface. This ensures data flows seamlessly across different modules, improving data quality and accessibility.

The shared data repository within HCM guarantees a “single source of truth,” maintaining high data quality. It offers easy integrations and seamlessly operates with open-source products, providing a unified system for health campaign management.

HCM is designed with highly configurable, reusable modular building blocks, enabling rapid reconfiguration of the same product for different health campaigns. These modules can also be repurposed to develop new solutions for routine health, primary healthcare, and other areas.

More than just a product, HCM is a comprehensive solution designed to streamline health campaigns, enhance coordination, and improve outcomes at every level of the health campaign management system.

Useful Links

Contact Us

Release Summary

HCM v1.5 is a product release with upgrades for a new campaign adaptation such as IRS.

Features:

• Enhancement of DIGIT HCM for managing a new campaign such as IRS.

• Enhancement to provide the ability to link downloaded households to new campaigns.

• The product has been enhanced to capture information related to house structure, room details, and the number of pregnant women and children present in the house independent of the campaign type.

• Enhanced accuracy for geo coordinates capture in the app.

• Enhancement of DSS dashboards for new campaign adaption.

• Enhancement to provide the ability to view dashboards for District Supervisors in the mobile application.

Functional Changes

• Closed Household: This feature enables data collection on closed households by utilizing the existing registration and delivery package. It allows CDDs (Community Drug Distributors) to revisit households for registry updates efficiently.

• Registration and Delivery: Added intermediate screens to enhance registration of households to support new campaigns.

• User Action: Full CRUD functionality for project-related actions taken by the field worker that are not tasks related to the beneficiary like:

Non-Functional Changes

• Pop-ups have been added to various screens to improve geo-coordinate accuracy within the app. These pop-ups will display a message and temporarily freeze the screen, allowing users to capture a person's geo-coordinates without disruption.

Breaking Changes

• No breaking changes were made.

Benefits - v1.5

• Configurable Project Dashboard: Previously, project dashboard configurations were hardcoded. Now, they are fully configurable based on boundary v2 and project-type codes.

• Removal of Hardcoded Context Paths: All hardcoded context paths have been removed throughout the application, improving flexibility and maintainability.

• Map Config Data Moved to S3: Due to the large size of the map configuration data, it could not be loaded into MDMS v2. This data has now been moved to S3 assets for better handling and storage.

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

The HCM v1.5 release does not require any migration from the 1.4 release.

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.

HCM Test Cases v1.3

Here are the articles in this section:

• Frontline Worker's App

• Campaign Management Dashboard

• Microplanning

A digital partner for the frontline workers:

• Better user experience for frontline workers leads to better quality data captured in less time, thus facilitating improved efficiency

• The ability for frontline workers to access on-demand training, and in-app guided walkthroughs, enabling improved efficiency

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.

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:

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.

Here are the articles in this section:

Click on the links below to learn more:

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:

Click to learn more.

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'.

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.

The articles in this section include:

Here are the articles in this section:

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.

Here are the articles in this section:

The articles in this section include:

Release Summary

HCM v1.4 is a tech release with only server upgrade to DIGIT 2.9 LTS with some additional cleanup.

Features:

• Digit core LTS integration

  • MDMS v2 integration

  • Boundary V2 integration

• HCM Admin Console

• DIGIT HCM app modules as package extractions

Functional Changes

• Missing unique validation on client reference ID added in all offline supported services.

• Project types have been moved to project additional details from MDMS.

Non-Functional Changes

• UI modules extracted as packages

  • Registration and delivery

  • Referral reconciliation

  • Inventory management

Breaking Changes

• All the master data for the DIGIT HCM app are separated by functionality from one single master.

• Flyway version upgrade to 9.22.3 for LTS upgrade.

• Boundary v2 Integration

Health Campaign Management (HCM) aims to expand capabilities in public health. It covers campaign setup, planning, registration and delivery, inventory management, and real-time data dashboards enabling the establishment of digital public health infrastructure for faster and cost-effective health campaigns. DIGIT HCM is designed to evolve rapidly and adapt to local needs while addressing systematic challenges. It enables decision-makers and programme managers to streamline campaign planning, manage workflows and monitor service delivery in real-time to aid data-driven decision-making.

Why do we need HCM?

Health campaigns are a commonly used strategy that helps the routine health system prevent or control diseases by delivering essential healthcare interventions in a time-bound manner.

Health campaign management faces several challenges, which include the inability to fetch accurate population targets or monitor the campaigns in real-time and tune the campaign to the defined population needs. Lack of timely and actionable data is often the primary cause of operational inefficiency. Additional concerns relate to siloed, redundant datasets adding to the implementation costs.

There is a need for a campaign management product that offers:

• Single interface for managing all components in a campaign lifecycle

• Allows reuse of assets across campaigns

• Reduces fragmentation by supporting multiple diseases

• Supports data interoperability with other health intervention areas (Eg. disease surveillance systems)

The goals include:

• Increased campaign effectiveness (coverage)

• Reduced time to respond to outbreaks

• Improved efficiency (lower costs)

• Increased transparency and accountability

Watch the video below to find out how Health Campaign Management meets the above goals and more:

Reimagine Health Campaigns with HCM

• Setup campaigns in 3 days

• Run hundreds of campaigns simultaneously

• Record bednet delivery in 1 minute

• Real-time campaign data dashboards

MDMS

Config

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.

Building blocks are individual, independent blocks of solutions, that are assembled to solve large, complex problems. With building blocks, any solution could be evolved to fit the evolving problem as against building a new system from the ground up.

DIGIT HCM is built using modular building blocks that are highly configurable allowing countries to tailor the product to their specific needs, easily. These building blocks are reusable allowing for the creation of new solutions. They facilitate reusable assets for all campaigns, and have the following benefits:

• Easy to adapt to local needs (Highly configurable - easy to rework)

• One asset for all campaigns (Multiple campaign types, diseases)

• Maximise leverage (Additive blocks - Create new solutions)

With these building blocks, one campaign could easily be pivoted to set up another health campaign. For example. a malaria campaign could be pivoted from a cholera campaign to an NTD campaign with minimal effort and time. Beyond campaigns, the same blocks could create solutions for routine health delivery and other health needs.

Data resides in shared open registries enabling the reuse of data and establishing a single source of truth. Interoperability is baked into the design of DIGIT HCM allowing free flow of data across different systems. DIGIT HCM enables countries to set up their digital public infrastructure for health.

From setting up campaigns quickly, to planning, inventory management, registrations, service delivery, and real-time data dashboards, DIGIT HCM covers all elements required to run effective campaigns. The same product can be used for all campaign types across multiple diseases.

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.

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.

Find the Product Capability Roadmap below:

To see a detailed version of this roadmap, click here.

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.

Boundary v2 migration

If the current environment has boundary data in MDMS v1 please follow the steps mention in the document below to migrate to boundary v2. Boundary migration from v1 to v2 LTS

MDMS v2 migration

If the environment is new the one click installer and data loader will by default load the data required.

If the Environment has pre existing data then the MDMS v2 migration tool should be run using the below document:

Following is the code link:

API Spec

Sequence Diagrams

API Spec

Sequence Diagrams

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.

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

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.

Deployment Configuration

Build Details

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

DIGIT is India’s largest open-source platform for digital governance. The health services are built on top of DIGIT. It is built on OpenAPI (OAS 2.0) and provides API-based access to various services, enabling governments to provide health campaign services with relevant new ones. It also facilitates integration with the existing system into the platform and runs seamlessly on any commercial/on-prem cloud infrastructure with scale and speed.

Key Architecture Highlights

• Health DIGIT is a micro-services-based platform that is built to scale. Micro-services are small, autonomous, and developer-friendly services that work together.

• It facilitates decentralised control between teams so that its developers strive to produce useful tools that can then be used by others to solve the same problems.

• Micro-services have intelligent endpoints that process information and apply logic. They receive requests, process them, and generate a response accordingly.

• Parallelism in development: Micro-services architectures are mainly business-centric.

• A large software or system can be broken down into multiple small components or services. These components can be designed, developed, and deployed independently without compromising the integrity of the application.

Multi-Layer Architecture

DIGIT Health follows a multi-layer or n-tiered distributed architecture pattern. As seen in the illustration above, there are different horizontal layers with some set of components such as Services, Registries, and DIGIT . Every layer consists of a set of microservices. Each layer of the layered architecture pattern has a specific role and responsibility within the application. The following are the advantages:

• Layered architecture increases flexibility, maintainability, and scalability.

• Multiple applications can reuse the components.

• Parallelism.

• Different components of the application can be independently deployed, maintained, and updated, on different time schedules.

Release Summary

Health Campaign Management v1.3: The Frontline Worker’s App includes two new features that enable frontline teams to perform their tasks efficiently even when offline.

To learn more about the DIGIT Health Platform and the Health Campaign Management (HCM) product, click here.

New Feature Additions

Localisation Keys

​

Health campaigns, critical for disease control in the global south, face challenges such as limited resources, outdated tools, and a lack of real-time data. In Mozambique, where malaria is endemic, 95% of the population is affected, with 617,000 malaria-related deaths reported in 2021 underscoring the urgency to revolutionize the existing health campaign framework. Hence, we felt the need for a product to address these issues and our first exemplar was in Mozambique.

The Ministério da Saúde ((MISAU) or the Ministry of Health Mozambique in partnership with eGov recognised the need to use infrastructure-first thinking to reimagine how health campaigns were managed, run, and could be sustained over years, not just for malaria, but for many other diseases.

Mozambique reimagined health campaigns using a platform approach, with DIGIT Health Campaign Management (HCM). DIGIT HCM worked closely with various departments within NMCP, as well as other partners to build state capacity, provide technical assistance, and contribute to digital transformation.

DIGIT HCM, customised and branded as Salama for Mozambique, was rolled out as part of the Long Lasting Insecticidal Nets (LLIN) campaign. In 2023, Mozambique used DIGIT HCM to manage the distribution of malaria bednets across Tete and Gaza provinces. Click on the links below to learn more:

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.

Overview

Attendance service allows users to maintain attendance registers, enrol individuals, create, update or search attendance logs and manage staff permissions.

API Specifications

Base Path: /health-attendance/

API Contract Link

Data Model

DB Schema Diagram

Web Sequence Diagrams

Attendance Register

Staff

Attendee

Attendance Log

Find the service build updates below:

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.

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.

Here are the articles in this section:

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.

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.

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.

Impacted Services

Project:

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.

Overview

The National Malaria Control Program (NMCP) transitioned to a digital system for their bed net distribution campaign in 2022/2023, moving away from their previous paper-based method. However, the team faced numerous issues with the new tool, such as synchronisation errors, data quality issues, inadequate visualization and analysis of geolocation data, and ineffective bednet tracking during the campaign.

To address these challenges, NMCP partnered with eGov to develop DIGIT HCM, a Digital public infrastructure. This collaborative effort resulted in the creation of an open-source digital public infrastructure (DPI) with interoperability and scalability. Customised as Salama (implying health in Swahili), the aim was to mitigate the above challenges and support multiple campaigns efficiently.

Release Summary

Health Campaign Management v1.2: The frontline worker’s App includes 8 new features that allow the frontline teams to perform their tasks efficiently even when offline.

New Feature Additions

Scan the resource code to track the resources delivered:

1. Package utilised to parse the barcode : .

2. Package utilised to QR code scanner:

3. GS1 - standards :

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

API Spec

Sequence Diagrams

Following is the list of customisations enabled for the campaign in Mozambique:

• Allow registration without searching.

• Removed a few location and address-related fields from the registration page.

• Removed the option to edit household and individual details

API Spec

Sequence Diagrams

Click to learn more.

Overview

In the HCM 1.6 release, we are excited to introduce several technical improvements and functional enhancements, including two key capabilities:

1. Micro Planning: This module enables campaign workers to generate precise population estimates and optimize resource allocation, leading to significant time and cost savings in campaign execution.

2. Admin Console: A streamlined tool for campaign setup, the Admin Console reduces setup time from days to mere minutes, accelerating our ability to support partners across Africa effectively.

New Capabilities

1. Microplanning

Overview:

It is the process of creating detailed, delivery-level operational plans for reaching target populations with health interventions.

Microplanning helps to know -

1. Who needs the intervention?

2. Where is the intervention site?

3. How many resources (Medical supply, people, commodities, etc.) are needed for the intervention?

In the current version of Microplan module, users can:

• Set up and manage microplan: Set up microplan by ingesting boundary population and facilities or distribution points, managing microplan assumptions for resource calculation, and managing user access.

• Validate & finalise population data for microplanning: Validate, update, and approve campaign population data to be used for microplan estimations.

• Assign facilities or distribution points to catchment areas: Assign the facilities to their catchment areas and finalise the assignment.

• Validate & finalise microplan estimations: Validate, update and approve the microplan estimations to be used for campaign execution.

Key values delivered:

1. Enhanced Efficiency: Speeds up the microplanning process by automating calculations and resource estimations, reducing planning time.

2. Improved Accuracy: Minimizes errors in campaign resource estimates, ensuring optimal allocation.

3. Real-Time Collaboration: Facilitates real-time data validation and approval among stakeholders, improving coordination.

4. Scalability: Easily adapts to different campaigns with no or minimal changes.

Targeted users:

Central system administrators, program managers, and users that are part of campaign microplanning

Discovery and validations:

Multiple validation and process reviewal sessions were conducted with the partners such as CRS, AMP, Malaria consortium, NMCP, CHAI, and WHO. Activities included in the sessions are:

1. Understanding the workflow of a campaign microplan

2. Figuring out the key capabilities required in a digital microplan

3. Product flow walkthrough for validation

Test yourself:

Please check out the user-manual .

Login credentials - Username : MICROADMIN11 Password : eGov@1234

Value measurement:

• User feedback from the UAT sessions in Moz

• Roll-out in other countries and campaigns will further validate the value

• Measuring the product metric such as time to create a microplan, population coverage accuracy and resource utilization accuracy.

Key metrics to monitor:

1. User adoption and engagement

a. User Registration: The number of microplan users who are registered on the platform.

b. Session Time: The average amount of time users spend on the platform in minutes.

1. Population coverage accuracy - The total population considered in the microplan vs the total population captured during the campaign execution.

2. Resource utilization accuracy - The total number of resources (bednets, frontline workers, vehicles, etc.) estimated during the microplanning phase versus the total number of resources utilised during campaign execution.

3. Operational efficiency - Time required to finalise a microplan from the created time.

4. Microplan adoption - The number of microplans created concerning countries.

Implementation considerations:

1. Adding a new village (with population data) and running the resource calculation for the village

2. Adding a new facility, assigning the facility to a village, and then running the estimation service

3. In some scenarios, a country just wants to use our Microplan product and not the Admin console. In that case, the impel team should be able to consume the Microplan Excel output created by the Microplan v0.1 module and create a Microplan using a script or something.

4. For Mozambique specifically, the impel team needs to add 3 columns in the estimation dashboard - Fixed monitors, Moving monitors, and Number of days. These will be user input (free text) fields. Add the columns and data points to the finalised microplan estimation Excel report.

Console

Overview:

The Console is a critical module within the HCM platform designed for System Administrators and Programme Managers to efficiently set up, configure, and manage health campaigns. With the Console, users can:

• Set Up Campaigns: Create campaigns for specific diseases in under three hours.

• Configure Campaigns: Tailor HCM Mobile App features to align with country-specific needs within a day

• Manage Campaigns: Update or modify campaign data in real-time to adapt to the how the campaign is evolving

What the Admin Console Is Not:

• A module that lets you create new features and data models on HCM

• A Module that can create new campaign types

Future Potential:

• Management Dashboard: A centralized view for organizational leaders to oversee multiple campaigns at a strategic level.

• Organisational Insights: Provide actionable analytics not just at the campaign level but across the entire organization.

Key values delivered:

• Effort Reduction: Simplifies campaign setup, minimizing coordination and manual effort

• Time Savings: Speeds up the campaign setup process

• Error Reduction: Decreases the risk of setup errors

• Lower Technical Barriers: Allows non-technical users to manage campaigns efficiently

Target users:

System Administrators, Programme Managers, IT Managers, and non-technical personnel familiar with health campaign workflows.

Discovery and validations:

Extensive validations and process reviews were conducted with our partner network. Key activities included:

• Feedback sessions during online workshops and field visits in Mozambique.

• Insights from ongoing campaigns, particularly from NMCPs and field users.

• A webinar showcasing the Admin Console's capabilities is planned.

Test it yourself:

1. The Login credentials for the App -

2. The

3. The Admin Console link -

4. Credentials For Console login:

Value measurement

• User feedback from UAT sessions with partners and Ministry of Health representatives

• Usability metrics, such as time taken to set up campaigns and system usability scores

Key metrics to monitor:

• Time required by users to set up, configure, and manage campaigns.

• Feedback from user interviews during and after campaigns

• Usability lab results to track user efficiency and satisfaction

Implementation considerations:

• Localisation: Localizing labels to accommodate country-specific languages and contexts

Known bugs/Issues

None

Enhancements

HCM dashboard enhancements

Overview:

The Seasonal Malaria Chemoprevention (SMC) campaign dashboard within the HCM system has been enhanced to provide greater flexibility, data visualization, and actionable insights. Key improvements include:

• Pre-Built Dashboards with Customisation: Out-of-the-box dashboards tailored for various campaign types (ITN, SMC, IRS) with the ability to configure custom charts for specific country/program needs using the open-source ElasticSearch Kibana dashboard.

• Data Evaluation Modules: New features to assess data quality, team performance, and attendance.

• Expanded Chart Capabilities:

- Venn diagrams for advanced analysis. For example, in SMC campaigns, these charts help evaluate multi-cycle intervention delivery, such as determining how many beneficiaries received medication across all cycles, one cycle, or specific combinations.

- Side-by-side comparison charts for multi-dimensional data with more than two bars.

Key Values Delivered:

• Customisation Flexibility: Partners and countries can add custom charts to suit specific country requirements integrated into ready-to-use campaign dashboards built in DIGIT’s DSS that have enhanced user experience.

• Targeted Insights: Enables evaluation of intervention coverage, such as tracking how many individuals received medication across multiple cycles.

• Advanced Visualisation: Multi-dimensional data analysis through side-by-side charts and Venn diagrams. For example, inventory trends across different supply chain stages or intervention outcomes by region.

Target users:

Campaign managers and supervisors are responsible for monitoring and evaluating campaigns daily

Discovery and validations:

The enhancements were finalized after discussions with key stakeholders, including the Malaria Consortium, Mozambique NMCP, and feedback from the Digital Product Advisory Committee (DPAC).

Test it yourself:

The URL for the dashboard is linked

The login credentials for the dashboard are linked

Value measurement:

Usability and impact assessments will be conducted through planned surveys with end users, including Mozambique NMCP, Malaria Consortium, CRS, and CHAI. The pilot rollout for the SMC campaign in Mozambique’s Nampula and Niassa provinces will further validate these features.

Key metrics to monitor:

Implementation considerations:

• Localisation of labels to align with country-specific contexts and languages.

• Addition of custom charts not included in the pre-built DSS.

• Drill-down capabilities for heatmaps rely on the availability of shapefiles for sub-national boundaries (e.g., districts, localities).

• Customisation of logic for charts in the ‘Data quality’ module logic tailored to program/country needs (e.g., identifying suspected fraud or households exceeding 20 members)

The framework used for dashboard development: HCM SMC dashboard metrics design:

Calculations for charts: KPI Calculation: HCM Dashboard SMC:

Known bugs/issues:

None

HCM application enhancements

Overview:

The checklist feature in HCM includes a supportive "Help Text" section designed to provide additional guidance for supervisors. This section can be used to clarify the intent of each question or offer useful hints, ensuring that supervisors understand the context and provide accurate responses. By including detailed explanations or examples in the help text, this feature reduces confusion and promotes consistency in data collection, ultimately improving the quality and reliability of the information gathered.

Key values delivered:

• Contextual Guidance: Provides additional information to clarify the purpose or context of each question

• Hints for Accurate Responses: Offers examples or tips to help supervisors choose the correct answers or fill in the required data accurately

• Improved Data Quality: Reduces errors and inconsistencies by ensuring supervisors fully understand the questions

• Customisable Content: Allows administrators to tailor the help text for specific questions to suit the campaign or data collection needs

Targeted users:

Supervisors who monitor campaign activities, health facilities in charge for assessing the beneficiaries referred, and distributors assessing the eligibility of beneficiaries for service delivery.

Discovery and validations:

This feature was developed in collaboration with the Malaria Consortium, with multiple validation sessions conducted to finalize the design. The process included:

• UI/UX Validation: Assessing the visual design and functionality of the feature

• User Navigation Walkthrough: Reviewing the user flow to ensure ease of navigation

• UAT Sessions: Conducting User Acceptance Testing to gather feedback and make improvements

Value measurement

• User feedback from UAT with the partners and state team representatives

• Effectiveness in terms of improvement in the checklist responses to assess the campaign data for the supervision module

Key metrics to monitor:

• The time taken by supervisors to complete and submit the checklist

• Insights gathered from user interviews conducted during and after the campaigns

• Adoption metrics, including usability scores, to evaluate user efficiency and satisfaction

Implementation considerations:

• Localisation of labels to align with country-specific contexts and languages

• Content customisation to meet implementation requirements

Conclusion

Overall Benefits

Console v0.3

• Time for campaign configuration for post Intervention flows reduces from 1 week to less than an hour through HCM Admin Console v0.3

• With the implementation of the edit feature in the HCM Console v0.3, the dependency by partners/country teams on eGov during the campaign was reduced substantially.

• Campaign Targets (Denominators) for DSS are pushed directly from the target sheet uploaded on the console egov's intervention.

• All Checklists should be created through the Console with no interventions from the solutions team of eGov.

SMC App Improvement and Dashboard

• User Interface enhanced for better user experience

• New charts such as Venn Diagram and Side by Side multiple bar charts have been added for visualisation of the dashboard.

Microplanning v0.1

• Improved Accuracy in Population Data through Micro Planning v0.1.

• Enhanced Resource Allocation and Efficiency through Micro Planning v0.1

• Implements robust validation mechanisms, including the ability to approve or reject data updates, fostering trust in the process through Micro Planning v0.1.

• Improves accountability by maintaining controlled access for various stages of the microplanning process through Micro Planning v0.1.

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

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

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

Role action mapping has only been completed for registrars, distributors, and system administrators to support the development of registration and delivery flows. Other roles are still in progress.

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.

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".

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).

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

Key Features

• Register households

Release Summary

The Health Campaign Management V1.0 frontline worker’s app includes four new modules with several features that allow frontline teams to perform their tasks efficiently even when offline. To learn more about the DIGIT Health Platform and the Health Campaign Management (HCM) product, please follow the

Release Highlights

Find the service build updates below:

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

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.

Sync

1. A server should be responsible to handle or offer a mechanism to handle errors once data reaches it. (Error handling mechanism is being designed by the platform).

2. Sync will be manually triggered by the user (except for automatically syncing configuration down on the first login).

3. Sync down of data is not required to support (good to have) the first rollout.

4. Sync will be done through bulk APIs.

5. Sync will send each save action performed by the field user while offline to the server to preserve an audit of actions performed by the field user.

   1. Eg: If a field user registers an individual and saves the record and then goes back to update the individual, this will result in two API calls to the server (one create and one update).

6. API response compression Gzip will be turned on for all the endpoints.

7. Unique identifier to be used between client and server:

   1. A Client will create a unique (client-generated) identifier per entity (clientReferenceId) to relate entities while operations are being performed offline and send this id to the server for creating operations.

   2. Any subsequent operations (like update, delete) will be on the server gen id, so the client has to get the server gen id by searching using the client generated id. The client will call search API with clientReferenceId and will get the server generated id.

8. Processing on the backend will continue to be asynchronous and not changed for the health use case.

Configurability

Backend

1. Search API max limit and the default limit.

2. Service details and endpoints.

Frontend

1. Service details and endpoints.

2. Number of entities sent to the server in bulk API calls

3. Additional fields per entity in the app.

4. The drop-down values or select options to be presented in the app for field users.

Access Control

1. Access to data will be defined by the linkages of staff to the project and the corresponding boundary while respecting role-action mappings instead of the tenant-based approach.

Data

1. All deletes are soft deletes.

2. The server is responsible to delete nested/child entities if applicable when the parent entity is deleted.

3. Undeletion is not permitted.

4. Duplicate updates do not need to be detected or filtered out. The client is responsible to send duplicate updates on entity as separate requests to server.

Limitations

1. From the Product requirement perspective, there is no unique identification identifier, so Platform is unable to check the uniqueness of registry entities.

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 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.

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.

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.

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