> 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/ph-v1.7/release-notes.md).
# Release Notes
## Release Summary
The HCM v1.7 release introduces several enhancements and new features to the Health Campaign Management system, focusing on streamlining operations, improving user experience, and ensuring timely payments.
### New Capabilities
1. **Payments Module:** A dedicated module to automate and manage payments for campaign staff, addressing challenges like manual processing, delays, and lack of transparency. Key benefits include timely and accurate payments, enhanced staff satisfaction, financial inclusion, cost efficiency, and improved transparency and accountability.
2. **Community Living Facilities (CLF):** Integration of CLF test cases to better manage and monitor communal living settings within health campaigns.
3. **Eligibility Checklist:** Implementation of eligibility and CLF test cases to ensure that beneficiaries meet specific criteria, enhancing the targeting and effectiveness of health interventions.
### **Enhancements**
1. **Microplanning v0.2:** Improvements made to the microplanning process, facilitating detailed operational plans for reaching target populations with health interventions.
2. **HCM Console v0.3.1:** HCM Console updated, enhancing the user interface and experience for administrators and supervisors.
### **Technical Improvements**
* **HCM Product:** Technical refinements to the core HCM product, improving performance and reliability.
* **Microplanning:** Further technical enhancements to support the updated microplanning features.
* **HCM Console:** Technical updates to the HCM Console to support new functionalities and improve system stability.
## Document Resources & Links
| Technical Documents | Functional Documents |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| - Eligibility Checklist Configuration
- UI Configuration Details - Eligibility Checklist
- UI Configuration Details - CLF
- Master promotion guide - HCM Dashboard
| - Payments Module
- Payments User Manual
- CLF User Manual
|
---
# 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/ph-v1.7/release-notes.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.