> 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/v2.0/introducing-public-health/release-notes/release-history.md).

# Release History

<table><thead><tr><th width="86.21875">Version</th><th width="115.41015625">Release Date</th><th width="207.203125">Module(s)</th><th width="240.09375">Description</th><th>Reference Links</th></tr></thead><tbody><tr><td><a href="https://docs.digit.org/health">v2.0</a></td><td>02-03-2026</td><td><ol><li>HCM Console v1.0</li><li>Payments v2.0</li><li>Register Management</li></ol></td><td>HCM v2.0 significantly improves scalability, usability, and efficiency, introducing secure BYOD support, end-to-end campaign configuration through Console v1.0, and periodic wage disbursement via Payment Advice v2.0.</td><td><a href="https://docs.digit.org/health/introducing-public-health/release-notes">Release Notes</a></td></tr><tr><td><a href="https://docs.digit.org/health">v1.8</a></td><td>06-08-2025</td><td><ol><li>HCM Console v0.4</li><li>Server generated beneficiary IDs</li><li>Enumeration tool</li><li>Transit tool</li><li>P2P data sharing</li></ol></td><td>DIGIT HCM v1.8 introduces a Central Instance Deployment Model that reduces maintenance, standardises configurations, avoids service duplication, enables country-specific customisations, and lowers infrastructure costs.</td><td><a href="https://docs.digit.org/health/ph-v1.8/introducing-public-health/release-notes">Release Notes</a></td></tr><tr><td><a href="https://docs.digit.org/health">v1.7</a></td><td>10-04-2025</td><td><ol><li>Community Living Facilities</li><li>Eligibility based delivery</li><li>Payment advisory reports</li><li>Enhancements to microplanning</li></ol></td><td>Smarter eligibility checks, extending campaign reach into communal facilities, generating payments advisory reports, and enhancements to the console and microplanning modules</td><td><a href="https://docs.digit.org/health/release-notes">Release Notes</a></td></tr><tr><td><a href="https://docs.digit.org/health/v1.6">v1.6</a></td><td>19-12-2024</td><td><ol><li>Microplanning</li><li>Console</li><li>Enhancements to HCM app &#x26; dashboards</li></ol></td><td>Added microplanning for resource optimisation and admin console to streamline campaign setup</td><td><a href="https://docs.digit.org/health/v1.6/introducing-health/release-notes/hcm-v1.6-release-notes">Release Notes</a></td></tr><tr><td><a href="https://docs.digit.org/health/v1.5">v1.5</a></td><td>03-09-2024</td><td><ol><li>Configurable Project Dashboard</li><li>Search Query Enhancement</li><li>Managing a new campaign such as IRS</li></ol></td><td><strong>Support for IRS campaigns</strong>: Enhances Health Campaign Management to handle Indoor Residual Spraying (IRS) campaigns</td><td><a href="https://docs.digit.org/health/v1.5/introducing-health/release-notes/hcm-v1.5-release-notes">Release Notes</a></td></tr></tbody></table>


---

# 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/v2.0/introducing-public-health/release-notes/release-history.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.