> 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.md). # Public Health The Public Health solution is built as an open-source Digital Public Good to expand capabilities in public health. It is being designed to work across countries at varying levels of capacity and complexity. The solution reimagines the public health space as a set of horizontal building blocks, such as shared registries, and services, accessible through well-defined open APIs, which can be leveraged by multiple countries and disease programmes. The Public Health solution offers an end-to-end flexible, open, configurable, and reusable platform to plan, manage and run any public health programme such as health campaigns so there is detailed and timely monitoring and evaluation to review coverage, target achievement and identification of gaps for their distribution. Explore the Public Health reference applications below: * [Health Campaign Management](/welcome-aboard/products-and-solutions/public-health/health-campaign-management-hcm.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 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/welcome-aboard/products-and-solutions/public-health.md?ask=&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.