> 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/welcome-aboard/products-and-solutions/public-health/health-campaign-management-hcm.md).

# Health Campaign Management (HCM)

The mission is to build a digital infrastructure that 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.

A Health Campaign Management Platform will offer a single interface for managing all components in a campaign lifecycle, enable reuse of assets across campaigns, reduce fragmentation by supporting multiple diseases, and support data interoperability with other health intervention areas.

Click on the links below to learn more about our products:

* [Frontline Worker's App](/welcome-aboard/products-and-solutions/public-health/health-campaign-management-hcm/frontline-workers-app.md)
* [Campaign Management Dashboard](/welcome-aboard/products-and-solutions/public-health/health-campaign-management-hcm/campaign-management-dashboard.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/welcome-aboard/products-and-solutions/public-health/health-campaign-management-hcm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.