> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v1.5/health-campaign-management/understanding-health-campaign-management-hcm.md).

# Understanding Health Campaign Management (HCM)

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.&#x20;

There is a need for a campaign management product that offers:&#x20;

* [x] Single interface for managing all components in a campaign lifecycle&#x20;
* [x] Allows reuse of assets across campaigns&#x20;
* [x] Reduces fragmentation by supporting multiple diseases&#x20;
* [x] Supports data interoperability with other health intervention areas (Eg. disease surveillance systems)&#x20;
* [x] Improves sustainability by providing ownership and control to the government&#x20;
* [x] Uses a modular and standards-based architecture

The goals include:

* Increased campaign effectiveness (coverage)
* Reduced time to respond to outbreaks&#x20;
* Improved efficiency (lower costs)&#x20;
* Increased transparency and accountability

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

{% embed url="<https://www.youtube.com/watch?v=_yxD9Wjqkfw>" %}

### 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
* Interoperability with any system
* Reusable campaign setup
* Data privacy by maintaining control over data from day one


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/health/v1.5/health-campaign-management/understanding-health-campaign-management-hcm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
