> 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.8/access/public-health-product-suite/health-campaign-management-hcm/specifications.md). # Specifications This section provides a structured and comprehensive technical overview of DIGIT HCM. It is divided into three main segments: 1. [**Functional Specifications** ](/health/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/specifications/functional-specifications.md)– Detailed documentation of core modules, including campaign type setup, inventory management, beneficiary data handling, boundary hierarchies, system user roles, and more 2. [**Role Action Mapping**](/health/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/specifications/role-action-mapping.md) – Defines the permissions and actions available to each system role—from system administrators to registrars, supervisors, warehouse managers, and programme managers—ensuring clarity, security, and accountability 3. [**Building Blocks & Services** ](/health/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/specifications/building-blocks-and-services.md)– Highlights the modular architecture of HCM, emphasising reusable, configurable building blocks—such as registries and service modules—that support adaptability, scalability, and seamless interoperability across campaigns and systems --- # 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.8/access/public-health-product-suite/health-campaign-management-hcm/specifications.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.