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

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.

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

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

​Release kit Link

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

  • 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

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:

MDMS migration from v1 to V2 LTS

Following is the code link:

Code link for the above-mentioned migration utilities

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

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:

HCM v1.6 Release chart

Find the service build updates below:

HCM v1.4 Release chart

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

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:

1. The Login credentials for the App - File

2. The APK

3. The Admin Console link - Link

4. Credentials For Console login:link

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 here

The login credentials for the dashboard are linked here

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:

HCM v1.5 Release chart

MDMS

Config

HCM Test Cases v1.3

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

Bug Fixes (Feedback from the bug bash)

• Click to access the Jira dashboard.

Known Issues

• Field 'type' does not exist or this field cannot be viewed by anonymous users.

• The field 'assignee' does not exist or this field cannot be viewed by anonymous users.

• A value with ID '10141' does not exist for the field 'project'.

• Field 'labels' do not exist or this field cannot be viewed by anonymous users.

• The field 'priority' does not exist or this field cannot be viewed by anonymous users.

• Not able to sort using field 'priority'.

Related Documents and Links