> 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/introducing-public-health.md).

# Introducing Public Health

The platform for planning, running, and monitoring health campaigns

## About Public Health <a href="#mission" id="mission"></a>

The DIGIT Public Health platform is an **open-source, modular, and configurable digital public infrastructure** that enables governments and partners to enhance **health service delivery, campaign execution, and data-driven governance**.&#x20;

It enables governments and partners to efficiently plan, manage, and monitor health campaigns, including immunisation, Neglected Tropical Diseases (NTD) control, and nutrition initiatives.

With household-level planning and equitable coverage tracking, it ensures no population is left behind. Program managers can quickly configure and launch customised campaigns using the Console. At the same time, real-time dashboards offer live insights into campaign coverage, stock availability, and workforce performance, supporting timely, data-driven decisions. The platform allows multiple campaigns to be run simultaneously on a single infrastructure, reducing duplication, lowering costs, and simplifying training.

> <mark style="color:purple;">**Vision Statement -**</mark> <mark style="color:purple;"></mark><mark style="color:purple;">Helping countries achieve Health SDGs by building digital public goods that strengthen public health</mark>

## Get Started By Your Role

{% tabs %}
{% tab title="Product Managers" %}
You are understanding capabilities, planning campaigns, or reviewing rollout. Start with functional specs, then features and user manuals.

{% hint style="info" %}
**Your path:** [Functional Specifications](/health/access/public-health-product-suite/health-campaign-management-hcm/specifications/functional-specifications.md) → [HCM Features](/health/access/public-health-product-suite/health-campaign-management-hcm/features.md) → [HCM User Manual ](/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-user-manual.md)→ [Product Roadmap](/health/access/public-health-product-suite/product-roadmap.md)
{% endhint %}

**Key references:**

* [Public Health Product Suite](/health/access/public-health-product-suite.md)
* [Public Health Solution Design Approach](/health/access/public-health-solution-design-approach.md)
* [HCM Console](/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-console.md)
* [Campaign Management Dashboard](/health/access/public-health-product-suite/campaign-management-dashboard.md)
  {% endtab %}

{% tab title="Developers" %}
You are setting up, configuring, or extending HCM. Start with the architecture, then move through installation → configuration.

{% hint style="info" %}
**Your path:** [Architecture](/health/design/architecture.md) → [Installation](/health/deploy/installation.md) → [Configuration](/health/deploy/configuration.md) → [HCM Console Configuration](/health/deploy/configuration/hcm-console-configuration.md)
{% endhint %}

**Key references:**

* [Standards](/health/design/standards.md)
* [Security](/health/design/security.md)
* [Interoperability](/health/design/interoperability.md)
* [Infrastructure Setup (AWS)](/health/deploy/installation/production-setup/setup-infrastructure.md)
  {% endtab %}

{% tab title="Implementation Teams" %}
You are planning a rollout across geographies or partner organisations. Focus on implementation phases, requirements, and support.

{% hint style="info" %}
**Your path:** [Planning an HCM Implementation](/health/deploy/planning-an-hcm-implementation.md) → [Gathering Requirements](/health/deploy/gathering-requirements.md) → [Installation](/health/deploy/installation.md) → [DIGIT Solutions Support](/health/community/digit-solutions-support.md)
{% endhint %}

**Key references:**

* [Public Health Solution Design Approach](/health/access/public-health-solution-design-approach.md)
* [Microplanning](/health/access/public-health-product-suite/health-campaign-management-hcm/microplanning.md)
* [Inventory Management](/health/access/public-health-product-suite/health-campaign-management-hcm/inventory-management.md)
* [FAQs](/health/community/faqs.md)
  {% endtab %}
  {% endtabs %}

## Browse By Category

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Product Suite</strong></td><td><p>HCM, the campaign management dashboard, inventory, attendance, and health payments — the full set of Public Health products.</p><p><a href="/health/access/public-health-product-suite.md">Public Health Product Suite →</a></p></td></tr><tr><td><strong>Functional Specs</strong></td><td><p>Feature scope, campaign types, boundary hierarchy, and building blocks — the complete functional picture of HCM.</p><p><a href="/health/access/public-health-product-suite/health-campaign-management-hcm/specifications/functional-specifications.md">Functional Specifications →</a></p></td></tr><tr><td><strong>Design &#x26; Architecture</strong></td><td><p>Solution architecture, standards, security, and interoperability for the HCM platform.</p><p><a href="/health/design/architecture.md">Architecture →</a></p></td></tr><tr><td><strong>Deploy &#x26; Configure</strong></td><td><p>Planning, installation, and the full HCM configuration reference — service, UI, dashboard, and console settings.</p><p><a href="/health/deploy/configuration.md">Configure →</a></p></td></tr><tr><td><strong>User Manuals</strong></td><td><p>Step-by-step guides for field workers, supervisors, and console admins running day-to-day campaign operations.</p><p><a href="/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-user-manual.md">HCM User Manual →</a></p></td></tr><tr><td><strong>Community</strong></td><td><p>Source code, the product roadmap, solutions support, and FAQs.</p><p><a href="/health/community/ask-our-bot.md">Community →</a></p></td></tr></tbody></table>

## Setup & Installation

{% stepper %}
{% step %}

### **Understand the approach**

Start with why the platform exists and where it's being used today — campaign types, current interventions, and the underlying design principles.

[Public Health Solution Design Approach](/health/access/public-health-solution-design-approach.md)
{% endstep %}

{% step %}

### **Plan the implementation**

Scope the rollout before touching infrastructure: programme plan, master data template, and requirements gathering.

[Planning an HCM Implementation](/health/deploy/planning-an-hcm-implementation.md) → [Gathering Requirements](/health/deploy/gathering-requirements.md)
{% endstep %}

{% step %}

### **Install and configure**

Install via GitHub Actions on AWS or build the field app APK, then complete service, UI, and console configuration.

[Installation](/health/deploy/installation.md) → [Configuration](/health/deploy/configuration.md) → [HCM Console Configuration](/health/deploy/configuration/hcm-console-configuration.md)
{% endstep %}

{% step %}

### **Test and go live**

Run quality assurance testing, then lean on the community channels below if you get stuck.

Quality Assurance Testing → [DIGIT Solutions Support](/health/community/digit-solutions-support.md)
{% endstep %}
{% endstepper %}

## Contact Us

{% embed url="<https://egov.org.in/contactegov>" %}


---

# 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/health/introducing-public-health.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.