> 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/campaign-management-dashboard/integrated-cross-campaign-dashboard-iccd.md).

# Integrated Cross Campaign Dashboard (ICCD)

## Overview

The ICCD (Integrated Cross Campaign Dashboard) system serves as a pivotal technology infrastructure that facilitates real-time data visualisation and command operations. It integrates various data sources to provide a holistic view of ongoing projects, enhancing decision-making and operational efficiency. The system is particularly beneficial for managing complex projects across different jurisdictions, enabling seamless information sharing and collaboration among stakeholders. Its dashboard rendering capability allows users to access specific project details aligned with their roles, thereby streamlining access control and reducing information overload.

## Future Enhancements

**External Systems Integration:** Enable integration with external health information systems such as DHIS2, OpenSRP, etc, to seamlessly import and visualise external health data within DIGIT dashboards.

**Predictive Analytics and Dashboard Insights:** Incorporate predictive models into dashboards to generate predictive insights on campaign performance, stock usage, and coverage trends.

**Anomaly Detection and Alerts:** Introduce automated anomaly detection and alerting to flag irregular patterns and improve data quality.


---

# 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/campaign-management-dashboard/integrated-cross-campaign-dashboard-iccd.md?ask=<question>&goal=<user_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.