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:

  • Refusal of consent for data collection.

  • Scanning of resources that will be reused for multiple deliveries.

  • Marking a transit post-non-compliant (polio).

  • Marking any incident that doesn't bear relation to the beneficiary.

  • Location capture of the field worker app.

• Dashboard Updates:

  • Mobile Dashboard: Enabled the mobile dashboard for district supervisors and configured the Digit UI DSS Dashboard to support new campaigns (e.g. IRS).

  • National Dashboard Enhancements: Introduced support for pie charts and bar charts.

  • Map Configurations: Moved map configuration data to S3 assets.

  • Chart Configurations: Added and modified chart configurations for both the Mobile and DSS Dashboards (e.g., IRS), including both new and existing charts.

• Tech Debts

  • Search Query Optimization: Enhanced search queries across the mobile application for improved performance.

  • Boundary Localizations: Migrated boundary localizations from the ISAR (JSON) database to an SQL database in the mobile application for better efficiency.

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.

• Search Query Enhancement: Previously, each entity had its own individual search. Now, we have implemented a unified query builder, which has significantly improved the performance of the search functionality.

Click the links below to learn more:

In the HCM 1.7 release, we are introducing several technical improvements and functional enhancements, including 3 new key capabilities.

New Capabilities

1. Payments

Overview

Health campaigns involve multiple events spanning different jurisdiction levels, managed by various supervisors and attended by diverse types of campaign staff, such as healthcare workers, frontline workers, supervisors, etc. These events incur logistical costs and necessitate timely payments, including daily allowances for campaign personnel. However, the lack of a dedicated payment module presents several challenges.

Current Challenges

• Manual and fragmented payment processes: Payments are often tracked and processed manually, leading to inefficiencies and errors.

• Delays in payments: Staff compensation is frequently delayed, impacting motivation, engagement, and retention.

• Lack of transparency: The absence of a streamlined payment process results in limited visibility for supervisors and stakeholders regarding payment status.

• High administrative costs: Manual reconciliation and payment processes increase operational overheads.

Key values delivered

• Timely and accurate payments: Automated calculation and disbursement based on attendance ensure prompt compensation to campaign staff.

• Enhanced staff satisfaction: Timely payments encourage greater participation and improve workforce morale.

• Financial inclusion: Digital payments help bring unbanked staff into formal financial systems, contributing to financial equality.

• Cost efficiency: Automated processes reduce administrative expenses and improve resource allocation.

• Alignment with Sustainable Development Goals (SDGs): By digitising financial services responsibly, the module advances digital inclusion and promotes financial equality in health campaign operations.

• Transparency and accountability: Clear payment tracking fosters trust and provides better visibility for supervisors and stakeholders.

• Operational efficiency: Streamlined processes reduce administrative burdens and errors in payment handling.

User manual

Discovery and validations

The discovery of the users, the pain points, and potential solutions were formulated from various discussions with the different stakeholders such as:

• NMCP Mozambique workshop

• NMEP Burundi workshop

• Digital Finance Team, World Health Organisation

Test yourself:

Credentials

Value measurement

• User feedback from the UAT sessions in Burundi, Mozambique (SUS, CSAT).

• Validations and feedback from WHO-DFT.

• Validations and feedback with partners.

- Catholic Relief Services

- Malaria Consortium

- Alliance for Malaria Prevention

Key metrics to monitor

1. Payment Processing Efficiency:

• The time between campaign event completion and payment report submission to financial providers (MMO/Bank).

• The percentage of payments disbursed within the defined timeline. (SLA to be defined by the programme).

1. Data Accuracy and Quality:

• The number of reports requiring edits or corrections after generation.

• The error rates in payment data submitted for processing (Edited reports/Total reports).

1. User Engagement and Experience:

• CSAT score from proximity supervisors and payment approvers.

1. Operational and Cost Efficiency:

• Reduction in administrative costs due to digitisation of payment processes.

• The time saved per payment processing cycle compared to manual methods (Compare between As is vs To be).

1. Adoption Rates:

• The number of campaigns adopting the payments module.

1. Financial Inclusion:

• The number of users with mobile money accounts onboarded.

• The number of people paid out in cash vs mobile money vs bank.

Implementation considerations

1. Non-campaign events, such as training sessions, must be created as separate projects. This means that users will need to log out and select the appropriate project to mark attendance for each event.

For example, the following events require attendance tracking:

• Training of health facility supervisors at the district level

• Training of frontline workers at the district level

• Household registration (first half of the campaign)

• Household registration (second half of the campaign)

• Household distribution (first half of the campaign)

• Household distribution (second half of the campaign)

Since these events occur sequentially rather than simultaneously, the supervisor's application will contain six separate projects for attendance marking, along with an additional project for routine campaign activities such as checklists, complaint logging, and supervision. As a result, the project created for campaign activities cannot be used for attendance tracking, and a dedicated project will need to be created specifically for that purpose.

1. The indicators for monitoring the payment-related activities need to be incorporated in the dashboard depending on the programme requirements. Currently, the following indicators are considered.

• Number of attendance registers at the national level created, approved, payment report generated - Number chart.

• Number of attendance registers at provincial level created, approved, payment report generated - Number chart.

• Number of attendance registers at district level created, approved, payment report generated - Number chart.

• Attendance registers created vs approved - by district side-by-side bar chart with drill-down.

1. Ensure all actors involved in training, registration, and distribution follow the prerequisites outlined in the attached guidelines. (Part of the guidelines attached above).

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

• 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, create two separate 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.

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

c. 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 (For example: districts, province, country).

Baseline data for report generation performance testing

Known bugs/Issues

None

2. Community Living Facilities (CLF)

Overview

In health campaigns, HCM has primarily supported house-to-house delivery, where the distribution was tied to a specific household or individual. For fixed post mode, HCM has done only household-based campaigns where enumeration was done house-to-house and distribution was done at a fixed post. Even in individual-based campaigns, the beneficiaries were usually part of a household with a limited number of members, with the largest households we’ve encountered being up to 30 members.

During the discussions for the polio campaign in Nigeria, there was a need to administer vaccines in fixed locations like schools, community centers, or in transit settings. In these scenarios, delivery agents are mobile, administering vaccines on the go, such as along roadsides or under trees.

There is now a growing demand for addressing similar alternative delivery modes in other health campaigns. For example, in Nigeria's Schistosomiasis campaign, medicines had to be delivered to children residing in Madrassas (residential schools), where they are permanent residents. Other similar use cases could include:

• Nursing homes and long-term care facilities

• Orphanages

• Military camps

• Police camps

• Retirement homes

• Religious Community living facilities with permanent residents

• Refugee camps

• Jails

• Schools (Residential and Non-residential)

• Bus stands / railway stations

As these use cases expand, HCM needs to adapt to cater to these modes of delivery as well and also ensure the HCM Console enables the same.

Key values delivered

As a campaign manager, I can configure different modes of delivery (fixed locations or transit points) in HCM, so that I can ensure efficient and adaptable health interventions across diverse settings like schools, refugee camps, or transit locations.

As a field worker, I can easily administer vaccines or medicines on the go using HCM, so that I can reach beneficiaries efficiently in non-household environments, such as roadsides, schools, or community centers.

Targeted users

Frontline workers who are responsible for registering and delivering interventions to community living groups.

Discovery and validations

The problem discovery and solution were done through discussions with the Burundi NMEP program team and also during the field visit to Kano, Nigeria as part of the discovery for the polio campaign.

Test yourself:

Link to download APK:

Credentials

Value measurement

• User feedback from the UAT sessions in Burundi, Nigeria (SUS, CSAT).

Key metrics to monitor

1. Adoption & Usage

• The number of health campaigns utilising non-household-based delivery.

• The percentage of the total health campaigns that use non-household-based delivery.

• The average number of beneficiaries served per CLF.

1. Efficiency & Reach

• The percentage of the total beneficiaries covered through non-household-based campaigns.

• The average time taken per beneficiary in non-household-based campaigns vs. household-based campaigns.

• The number of beneficiaries reached per field worker per day in different delivery modes.

1. Operational Effectiveness

• The percentage of campaigns successfully configured with fixed post and transit delivery modes.

• The percentage of frontline workers successfully using HCM for non-household-based delivery.

1. Impact on Health Outcomes

• The percentage increase in service delivery due to non-household-based campaigns.

• The percentage of targeted vulnerable populations (for example, refugees, children in schools) reached.

1. User Experience & System Performance

• SUS (System Usability Scale) and CSAT (customer Satisfaction) scores from field workers using HCM for non-household-based campaigns.

• The percentage of frontline workers who report ease of use in administering interventions in non-household settings.

Implementation considerations

• The distribution logic — determining the number of interventions based on CLF type — needs to be configured as per implementation requirements. For example, schools may distribute one bednet per child, while refugee camps may allocate one bednet for every two people.

• If household registration within a CLF (For example, households within refugee camps) is required, it is not currently supported in the product and will require code adjustments. The Burundi Bednet Campaign 2025 can serve as a reference for such modifications.

• Additionally, KPIs and charts specific to CLFs must be customised based on the requirements of different implementations.

Known bugs/Issues

None

3. Eligibility Checklist

Overview

For campaigns like SMC, NTD, or Polio, where medication is administered and specific considerations arise — such as referring a beneficiary, marking side effects, or identifying ineligibility — the decision-making process currently rests with frontline workers in HCM. They assess the child and determine the appropriate flow within the application. However, this approach heavily depends on the efficiency, knowledge, and capacity of frontline workers, making it prone to inconsistencies.

As a pilot, a checklist-based approach was implemented at the solution level for the SMC campaign in Kebbi State, Nigeria. This approach was well received by both the implementation partner and the program, as it reduced the effort required from frontline workers. Based on this success, the feature has now been incorporated into the product offering for SMC, NTD, and similar campaigns.

Key values delivered

For frontline workers, the administration and referrals for beneficiaries become faster, allowing for greater coverage of beneficiaries. This approach reduces inconsistencies stemming from varying capabilities and knowledge among workers, ensuring that all beneficiaries receive the appropriate intervention or service based on their health conditions, thereby promoting standardisation.

Targeted users

Frontline workers who are administering medicines for campaigns such as SMC, NTS, and polio.

Discovery and validations

• Discussions with Malaria Control Programme of Kebbi State, Nigeria.

• Discussions with Malaria Consortium.

Test yourself

Link to download apk:

Credentials

Value measurement

Through field study for upcoming campaigns in SMC and NTD campaigns in Nigeria and Mozambique, we intend to observe the following:

1. Efficiency of administration and referrals: Measure the reduction in time taken by frontline workers to administer medicines and refer beneficiaries, as compared to the previous process without the checklist approach. To compare against past campaign data (baseline).

2. Coverage of beneficiaries: Track the number of beneficiaries covered per frontline worker before and after implementing the checklist approach to gauge the increase in coverage. To compare against past campaign data (baseline).

3. Stakeholder satisfaction: Collect feedback from implementation partners (like the Malaria Consortium) and frontline workers regarding the ease of use and effectiveness of the checklist-based approach.

Key metrics to monitor

1. Time per beneficiary: The average time taken by a frontline worker to complete the administration and referral process.

2. Beneficiaries covered per worker: The number of beneficiaries attended to by each frontline worker within a given time frame (for example, per day/campaign).

3. SUS, CSAT scores: Regularly gather insights from supervisors overseeing the implementation of the checklist, evaluating both worker performance and the overall success of the checklist-based approach.

4. Training and support effectiveness: Track the number of training sessions provided to frontline workers and the success rate of those workers incorrectly using the checklist.

Implementation considerations

• If a program or implementation prefers not to use a checklist-based approach and instead allows frontline workers to make decisions independently, the checklist should be configured for removal

• The logic and navigation flow may vary based on each country's health protocols and must be configured accordingly. Currently, the referral and delivery processes follow the logic outlined in the following document:

Known bugs/Issues

• Currently, ineligibility is determined solely based on age, height, and weight as per campaign requirements. Checklist-based ineligibility is not yet supported but will be addressed and released as a patch in an upcoming update.

• Marking side effects is not included in the checklist-based approach and should be recorded independently by the frontline worker.

Tech doc link

Enhancements

1. Microplanning

Overview

The enhancements focus on improving the estimation dashboard, refining microplan estimation reports, optimising facility data handling, and incorporating mixed distribution strategies. These changes aim to enhance usability, data accuracy, and flexibility in microplanning workflows.

Key values delivered

• Improved usability: Facility and accessibility filters enable better data segmentation.

• Data accuracy & flexibility: Editable estimate sheets and facility capacity adjustments improve data handling.

• Strategic decision-making: Mixed distribution strategy consideration allows for adaptable service delivery.

Targeted users

Health campaign managers & planners: Managing facility-level microplanning.

Discovery and validations:

• User feedback: Identified usability pain points in dashboard filtering and report editing.

• Stakeholder input: Validated mixed distribution strategy feasibility for service delivery.

Test yourself

Value measurement

User feedback: Identified usability pain points in dashboard filtering and report editing.

Key metrics to monitor:

N/A

Implementation considerations:

N/A

Known Issue

Configuration of microplan assumptions according to the village’s/settlement’s accessibility or security in the estimation dashboard will not be available.

2. HCM Console Patch

Overview

This version will see HCM Console being enabled with co-delivery as a campaign type where the users can create a multi-round, multi-delivery campaign with different delivery rules using various attributes like age, weight, height, gender, type of structure and number of individuals per bednets. The user can add any resources to be delivered based on their needs.

This release will also show how the Console handles user and facility mapping to boundaries through UI. The user now does not have to manually copy and paste boundary code in mapping facilities and users to boundaries.

Key values delivered

Capability to run co-delivery campaigns using the Console.

Targeted users

System admins and programme managers

Discovery and validations

Validations are done with CHAI, AMP, and CRS

Test yourself

Credentials

Key metrics to monitor

The total time to set up a campaign.

The number of campaigns set up by the users.

Implementation considerations:

N/A

Known bugs/Issues

N/A

Technical Improvements

1. HCM Product

• Show proper message for project error.

• Loader in language selection and fix code display during language change.

• Custom template for the white screen issue.

• PGR's new component changes.

• DSS new component changes.

• Extract peer-to-peer as a different module.

• Integration testing.

• Change facility selection to the latest component.

• Unit test cases for missing modules.

• HRM new component changes.

• Integration Testing Flutter.

2. Microplanning

• Download Microplan sheet frontend changes: Keep the download button disabled until the sheet's status is updated and it’s ready to download.

• Implement UI configuration in plan and pop inbox.

• POC: Throttle/Debounce create and update calls throughout the Microplan UI to avoid duplicate API calls in UI.

• Plan configuration APIs.

• Plan service - DB indexes.

• Boundary screen optimisation.

• Assumption values can be decimal values, so they should also accept numbers between 0 and 1.

• Update data table to ui-components' data table in Microplan UI.

• Design UI configuration for plan and pop inbox.

• If the user "Download estimations" immediately after validating the estimations, we won't get the sheet in format or localised way.

• Search and count query logic separation.

• Census Service -

  • Modify the search plan method to match the implementation in the plan service

  • APIs

  • Add method descriptor for bulk update

3. HCM Console

• Checklist Configuration: The console allows configuring checklists only in the user-selected language during the flow. It does not support configuring checklists in other languages, even if the server provides support for multiple languages.

• Assessment Checklist Configuration: Assessment checklists cannot be configured in the Console.

• Boundary Management: Boundary management is restricted to a single language.

• User Management: The same user cannot be assigned to multiple campaigns.

• Data Updates: Updating facility or user data during the update flow is not supported.

• Fetch Data From Microplan: Currently, users can fetch data from one selected microplan.

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:

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.

5. Reusability of Microplans: The frequency with which previous micro plans are reused or adapted for new campaigns.

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.

5. For Mozambique, the user's 9-digit phone number must be validated when uploading the user's Excel file using the user management module.

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

• Enhanced Agility: Accommodates last-minute campaign data and app configuration changes without causing delays

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:

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:

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

• Training Support: Serves as an on-the-go reference tool for supervisors, minimizing the need for extensive pre-training

• Localized Support: The help text can be written in local languages or customized to fit cultural contexts for better understanding

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.

• Offers downloadable finalised micro plans in Excel format, simplifying data sharing and usage across stakeholders through Micro Planning v0.1.

• Ensures better service delivery through precise facility-to-catchment area assignments.

Find the service build updates below:

Checklist Configuration

1. Attributes:

• Each checklist consists of multiple attributes, where each attribute represents a specific question or input field.

• Attributes may have associated codes (e.g., SMC1, SMC1.YES.SM1).

1. Points Mapping:

• Each possible response to an attribute (e.g., YES, NO, NOT_SELECTED) is mapped to specific points for different flows.

1. Precedence Questions:

• Some attributes are designated as precedence attributes.

• Precedence attributes determine the priority flow when multiple flows are eligible.

1. Flow Types:

• Common flow types include:

- TO_ADMINISTER

- BENEFICIARY_REFUSED

- BENEFICIARY_REFERRED

Checklist Configuration Process

1. Define the checklist attributes and associate them with codes.

2. Map each possible response of an attribute to flow points.

3. Identify precedence attributes and configure precedence mapping.

4. Define precedence flow logic (e.g., YES maps to TO_ADMINISTER, NO maps to BENEFICIARY_REFUSED).

Example:

1. Processing Inputs

• For each attribute in the checklist:

- Retrieve the user input.

- Generate a unique key (e.g., SMC1_YES) to avoid duplicate processing.

- Check if the input has already been processed to prevent double counting.

2. Update Scores:

• For each response:

- Retrieve the corresponding flow points from the points mapping.

- Update the scores for each flow type by adding the mapped points.

3. Handle Precedence:

• If the attribute is a precedence attribute and an input is provided:

- Record the precedence flow answer.

• Skip precedence attributes if no input is provided.

Final Flow Assignment:

• Calculate the total scores for all flows based on user inputs.

• If there is a tie in scores between flows:

- Check for precedence answers and assign the flow based on the precedence mapping.

- If no precedence answer exists, assign the flow with the highest score.

• If no tie exists, directly assign the flow with the highest score.

Find the service build updates below:

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

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

Impacted Services

Project:

• Implemented validation for updating the project start date and the end date. Implementing this ensures that any changes made to these critical campaigns adhere to the predefined criteria.

• Added the number of sessions field in additional details for the attendance registry, which enhances the system's ability to manage attendance tracking within projects. This field specifically denotes the frequency of attendance-taking sessions for a given project. Each session represents an instance where attendance is recorded, typically within a single day. For instance, if a project requires attendance twice daily (for example, morning and afternoon sessions), the number of sessions field would indicate ‘2’ to reflect this frequency. This information provides crucial context for understanding the attendance requirements and scheduling patterns within the project.

Individual:

• Added the ability to search by user UUID (Universally Unique Identifier) for individual search. This addition expands the search capabilities within the DIGIT-HCM platform, providing users with a more versatile and efficient means of locating specific individuals. A UUID is a unique identifier assigned to each user within the system. This new feature allows users to quickly retrieve information about a particular individual by entering their UUID into the search functionality. By leveraging UUIDs, which ensure each user has a distinct identifier, the search process becomes highly precise and reliable, minimising the risk of ambiguity or confusion, particularly in large datasets.

Referral Management:

Health Facility Referral Feature Update

New Feature: HF Referral

DIGIT-HCM now includes a Health Facility Referral (HF Referral) functionality that enhances the platform’s capability to efficiently manage referrals across health facilities. This addition is aimed at improving coordination and communication, ensuring a smoother referral process.

Stock Registry:

Enhance the inventory flow with the sender ID and the receiver ID added. Including sender and receiver IDs offers flexibility in handling inventory transactions within the DIGIT-HCM platform. Transactions can involve movement between warehouses, from warehouse to staff, from staff to staff, or any combination thereof. This accommodates various scenarios, such as inter-departmental transfers, internal requisitions, or supplier deliveries.

1. Sender Identification: The sender ID specifies the entity initiating the inventory transaction. This could be a warehouse, indicating that inventory items are being dispatched from a specific storage location. Alternatively, it could represent an individual staff member responsible for authorising the transfer of inventory items.

2. Receiver Identification: The receiver ID denotes the entity or individual receiving the inventory items. Similar to the sender ID, this could represent either a warehouse where the items are being delivered or an individual staff member who is the designated recipient.

Attendance:

Implemented offline-enabled functionality in the Attendance Module. Implementing this functionality in the attendance module significantly enhances the usability and reliability of the DIGIT-HCM platform, especially in environments where internet connectivity may be intermittent or unavailable.

Find the service build updates below:

Release Summary

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

  • Attendance management

  • DIGIT scanner

  • DIGIT showcase

• All core services have been upgraded to core 2.9 LTS barring the services modified for offline use cases.

• All data models have been restructured with an "is a relationship" from base eGov model and the base eGov search model.

• All data models have been moved to the health common library and duplicates removed.

• Removed reflection until code in the health common library that is Incompatible with Java 9 and above.

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

Boundary v2 migration

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:

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.

New Feature Additions

Localisation Keys

HCM Test Cases v1.3

MDMS

Config

Find the service build updates below:

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