dhis2

Initialize a centralized DHIS2 client and route API calls to specialized sub-skills.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill consolidates and coordinates DHIS2 interactions by providing a centralized client setup, routing to specialized sub-skills, and standardized API patterns. It reduces fragmentation when working with health information systems and accelerates common DHIS2 tasks.

Core Features & Use Cases

  • Client Setup (Centralized): Initialize the DHIS2 client consistently across projects.
  • API Basics & Routing: Use the dhis.api.get() and route requests to appropriate sub-skills for analytics, metadata, users, and system info.
  • Query Guidance: Reference the dhis2-query-optimization workflow to handle large queries efficiently.
  • Use Case Example: Connect to a DHIS2 instance, fetch metadata, then run an analytics query across multiple org units and periods.

Quick Start

Initialize the centralized DHIS2 client using the provided workspace configuration and demonstrate a simple API call to fetch system info.

Frequently Asked Questions about dhis2

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

FAQPage Schema
How do I centralize DHIS2 client setup and API routing for health data workflows?

Centralizing DHIS2 client setup involves initializing a consistent client configuration across projects, then routing API requests through standardized patterns like dhis.api.get() to fetch system info, metadata, and analytics data.

What is the best way to handle large DHIS2 analytics queries across multiple org units and periods?

Handling large DHIS2 analytics queries requires referencing the dhis2-query-optimization workflow, which provides guidance on efficiently structuring requests across multiple org units and periods to prevent system timeouts and data retrieval failures.

How does DHIS2 API routing work for analytics, metadata, and system information requests?

DHIS2 API routing works by using a centralized client to execute standard API calls, then directing those requests to specialized sub-skills based on the data type needed, whether that is analytics, metadata, user management, or system info.

Can I use a single DHIS2 client configuration for both metadata retrieval and analytics queries?

Yes, you can use a single centralized DHIS2 client configuration for both tasks. The client initializes consistently across projects, allowing you to fetch metadata and run analytics queries without fragmented setup processes.

Do I need specialized sub-skills to fetch system info and user data from a DHIS2 instance?

Fetching system info and user data from a DHIS2 instance uses specialized sub-skills. The centralized client routes your standard API calls to these specific sub-skills to simplify data access and system management.

Why does my DHIS2 data access workflow suffer from fragmentation across different projects?

DHIS2 data access workflows suffer from fragmentation when client setup is not centralized. Standardizing API patterns and routing interactions through a single client reduces this fragmentation and accelerates common tasks.