dhis2-indicators

Extract indicators and indicator groups from DHIS2 via dhis.meta and dhis.api.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/BLSQ/mcp_servers --skill dhis2-indicators
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dhis2-indicators
Source: https://github.com/BLSQ/mcp_servers/tree/main/.claude/skills/dhis2-indicators
Command: npx skills add https://github.com/BLSQ/mcp_servers --skill dhis2-indicators

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill extracts indicators and indicator groups from DHIS2 to support metadata analysis, validations, and formula referencing.

Core Features & Use Cases

  • Retrieve indicators with fields such as id, name, shortName, numerator, and denominator for reporting and governance.
  • Retrieve indicator groups to organize indicators by program, category, or context.
  • Use a custom API path when toolbox methods do not cover a data retrieval need.

Quick Start

After initializing the dhis client, fetch core metadata by running: indicators = dhis.meta.indicators() groups = dhis.meta.indicator_groups()

Frequently Asked Questions about dhis2-indicators

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract DHIS2 indicators and their numerator and denominator formulas for metadata analysis?

Extract DHIS2 indicators by fetching fields like id, name, shortName, numerator, and denominator to support metadata analysis, validations, and formula referencing. Use the dhis.meta.indicators() interface after initializing your dhis client.

What is the best way to retrieve and organize DHIS2 indicator groups by program category?

Retrieve DHIS2 indicator groups using the dhis.meta.indicator_groups() interface to organize indicators by program, category, or context. This supports metadata quality checks and groups indicators logically for downstream analysis.

Do I need a pre-initialized DHIS2 client to fetch program indicators and metadata?

Yes, you need a pre-initialized dhis client to fetch program indicators and metadata. The extraction process relies on the dhis.meta and dhis.api interfaces, which require the client to be fully initialized before querying data.

Can I use custom API paths and field selection when extracting DHIS2 metadata?

Yes, you can use a custom API path via the dhis.api interface when standard methods do not cover your data retrieval needs. The skill supports pagination, filtering, and custom field selection for detailed DHIS2 metadata extraction.

Does DHIS2 metadata extraction support pagination for large indicator datasets?

DHIS2 metadata extraction supports pagination, filtering, and custom field selection across DHIS2 instances. This allows you to retrieve large sets of program indicators and detailed fields without exceeding API limits.