> 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/release-notes/hcm-console-polio-co-delivery.md).

# HCM Console - Polio, Co-Delivery

Multi hierarchy support -Polio and Co-delivery Campaign types

## **Summary**

This release adds configurable co-delivery combinations for individual-based delivery (example: AZM+VAS, SMC+VAS), onboards Polio as a supported campaign type, and introduces multi-hierarchy support within a single tenant.

Co-delivery moves the combination setup from a hard-coded, per-combination build to console configuration. Polio is onboarded using the same approach as ITN and SMC, with LQAS, Independent Monitoring, and Team Level Stock Details as new modules for the campaign type. Multi-hierarchy support lets a single tenant run more than one boundary hierarchy structure at the same time, instead of being limited to one across all campaigns.

### At a glance

* **Upgrade path:** Initial build. Co-delivery configuration, Polio as a campaign type, and multi-hierarchy support did not exist in v2.0.
* **New services:** LQAS, Independent Monitoring, and Team Level Stock Details modules, newly available for Polio campaigns
* **Major feature:** Configurable co-delivery for individual-based delivery (e.g. AZM+VAS, SMC+VAS)

### What you need to do

**Campaign Admin**

* Define co-delivery rules and combined eligibility criteria for individual-based combinations (e.g. AZM+VAS or SMC+VAS) in the console before campaign start.
* Configure Polio as a campaign type, including the LQAS, Independent Monitoring, and Team Level Stock Details modules.
* Configure boundary hierarchy structures per country or campaign as needed.

**CDD (Community Drug Distributor)**

* No setup needed. The combined delivery workflow and the configured hierarchy appear automatically on the mobile app based on the rules set by the Campaign Admin.

**Supervisor**

* No setup needed. The zero-dose and missed-immunisation dashboard for Polio campaigns is available automatically once the campaign is configured.

## Highlights

This release focuses on three areas: giving campaign admins console control over co-delivery combinations, extending campaign type support to Polio with WHO-aligned data collection, and letting a tenant run multiple boundary hierarchies at once.

## New Services

**LQAS (Lot Quality Assurance Sampling):** Configurable through the HCM Console module grid, alongside the other Polio modules. Records Lot/Cluster survey location details, surveyor information, and GPS coordinates, including state, district, village, cluster ID, enumerator name, supervisor details, and survey date, captured by field surveyors on the mobile app for accurate tracking, verification, and reporting of field survey activities.

**Independent Monitoring:** Configurable through the HCM Console module grid. Captures post-campaign household-level data on the mobile app to validate vaccination coverage, similar to LQAS. Monitors record GPS points, survey responses, missed vaccination reasons, caregiver awareness, and surveillance details, and the module provides a settlement summary (missed children count, risk flags, coverage status, comments) accessible only to configured monitor roles.

**Team Level Stock Details:** Configured through the HCM Console via the Vial Details flow, where the page heading, description, and template elements (Record Issued Vials, Record Returned Vials) can each be toggled on or off. Once configured, field teams use the flow on the mobile app to track and update resource stock at each distribution point, including issued and returned vials, to maintain visibility of medicines across the campaign.

## New Features

### **ICD/Co-Delivery Capabilities (e.g. AZM+VAS, SMC+VAS)**

**New capability:** Co-delivery configuration

**What's new:** Co-delivery combinations for individual-based delivery, such as AZM+VAS and SMC+VAS, can now be configured directly through the console, replacing fixed, hard-coded setups for each combination.

**How it works:** Campaign administrators define co-delivery rules for a combination in the console. Eligibility criteria can be combined across both interventions within a combo, rather than being set independently for each one. CDD users see the combined delivery workflow on the mobile app based on whatever rules were configured.

**Impact:** New co-delivery combinations can be introduced without a custom build for each one. Countries running combinations such as AZM+VAS or SMC+VAS can apply eligibility logic that reflects how the two interventions actually interact, not just how each one works in isolation.

### Polio

**New capability:** Polio campaign support

**What's new:** Polio is now supported as a campaign type on the platform, following the same onboarding approach used for ITN and SMC.

**How it works:** Registration and distribution are aligned with WHO standards for data collection. The platform supports both LQAS and Independent Monitoring as data collection workflows for Polio campaigns. A dashboard tracks zero-dose children and flags children who missed immunisation.

**Impact:** Polio campaigns can run on the platform without a separate build. Supervisors get visibility into zero-dose children and missed immunisations, and data collection stays consistent with WHO standards for reporting and comparison across campaigns.

### Multi-hierarchy support

**New capability:** Multi-hierarchy support

**What's new:** A single tenant can now support more than one boundary hierarchy at the same time, instead of being limited to one hierarchy structure across all campaigns.

**How it works:** Hierarchies are configured and visible through the console. The mobile app now recognises and works across multiple hierarchy types within the same tenant.

**Impact:** Implementers can configure country- or campaign-specific hierarchy structures without standing up a separate tenant for each. Campaign managers can run campaigns with different structural needs side by side.

### Changed

<table><thead><tr><th width="200.19140625">Function</th><th width="302.34765625">Old version</th><th>This release</th></tr></thead><tbody><tr><td>Configuring a co-delivery combination</td><td>Hardcoded per combination, requiring a custom build for each new combo</td><td>Configured directly in the console; admin defines rules per combination without a custom build</td></tr><tr><td>Eligibility criteria for co-delivery</td><td>Set independently for each intervention in the combo</td><td>Can be combined across both interventions within a combo</td></tr><tr><td>Polio as a campaign type</td><td>Not supported on the platform</td><td>Supported and onboarded the same way as ITN and SMC</td></tr><tr><td>Data collection for Polio</td><td>No LQAS or Independent Monitoring workflow on the platform</td><td>LQAS and Independent Monitoring supported as data collection workflows</td></tr><tr><td>Missed immunization visibility</td><td>No dedicated dashboard</td><td>Dashboard tracks zero-dose children and flags missed immunizations</td></tr><tr><td>Boundary hierarchy per tenant</td><td>One hierarchy structure per tenant, applied across all campaigns</td><td>A tenant can support more than one hierarchy structure at the same time</td></tr><tr><td>Mobile app hierarchy recognition</td><td>Recognizes a single hierarchy type</td><td>Recognizes and works across multiple hierarchy types within the same tenant</td></tr></tbody></table>

## Fixed

No bug fixes documented for this release, as these are new features.

## Known Issues

The co-delivery microplan template is currently static. Dynamic template support is planned for a future release.

## Related Docs

{% content-ref url="/pages/jxxgB4JL0aAFJ3spcIgI" %}
[Configure Polio Campaign](/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-console/configure-polio-campaign.md)
{% endcontent-ref %}

{% content-ref url="/pages/B4nIWpPpCf3PZ2vXGTlV" %}
[Configure Co-Delivery](/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-console/configure-co-delivery.md)
{% endcontent-ref %}


---

# 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/release-notes/hcm-console-polio-co-delivery.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.