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

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

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

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

HCM Test Cases v1.3

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.

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

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.

MDMS

Config

Find the service build updates below:

HCM v1.4 Release chart

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

• Click to view the feedback from the UX audit.

Find the service build updates below: