# Health Payments

## Overview

The primary purpose of this module is to streamline attendance review and payment processing workflows for health campaign workers. It ensures that supervisors can:

* Access tools and functionalities tailored to their responsibilities.
* Maintain clear separation between proximity- and campaign-specific workflows.
* Facilitate accurate, timely payments for healthcare workers based on attendance.

## **User Roles**

<table><thead><tr><th width="158.03125">Roles</th><th width="278.5">Scope of action</th><th>Role description</th></tr></thead><tbody><tr><td>Proximity Supervisor </td><td><p>View attendance: Filter, search, and view attendance data.</p><p>Edit attendance: Modify attendance entries for accuracy.</p><p>Approve attendance: Validate and approve attendance registers for payment processing.</p></td><td>Proximity Supervisors can manage attendance records within a specific boundary assigned</td></tr><tr><td>Campaign Supervisor</td><td><p>View registers: Access to view registers to generate bills.</p><p>Download reports: Export reports in Excel/PDF formats for stakeholder communication.</p><p>Generate bills: Create bills based on three boundary levels: Country, Province, and District.</p></td><td>Campaign Supervisors can generate campaign-wide bills. If the boundary is set to a district, all the registers within that district will be consolidated into a single bill.</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.digit.org/health/access/public-health-product-suite/health-campaign-management-hcm/health-payments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.