OpenHEXA connects natively to any DHIS2 instance. Whether you need to clean up your system, sync data between instances, extract datasets, or enrich your data with external sources.
Discover what it looks like in practice.
DHIS2 instances accumulate configuration issues over time: orphan data elements, broken indicator formulas, inactive users still enabled. Left unaddressed, these slow down the system and create data quality problems.
Step 1: Audit tool (dhis2-audit.bluesquare.org): connect to your DHIS2 instance and run checks across different modules. Without storing any data, the tool surfaces what could be improved.
Step 2: OpenHEXA: once you know what needs fixing, OpenHEXA pipelines do the work. They disable inactive accounts automatically, clean up orphan elements, or run recurring maintenance jobs on a schedule.
What OpenHEXA fixes
→ Extract list of inactive users (e.g. no login in 90+ days) and disable automatically
→ Remove or archive orphan data elements with no associated datasets
→ Fix broken UID references in indicator formulas
→ Clean up org unit metadata inconsistencies
→ Schedule recurring cleanup pipelines to keep the instance healthy
Many organisations run more than one DHIS2 instance: a national system at the Ministry of Health, a disease-specific programme instance, a donor-funded deployment. Each one captures data, but they don’t talk to each other.
With OpenHEXA you can build a pipeline that connects two DHIS2 instances, extracts data from one, and pushes it into the other on a schedule.
What OpenHEXA does
→ Connect multiple DHIS2 instances through ready to use pipelines
→ Extract aggregate data, data elements, indicators or metadata from the source instance
→ Push data into the target instance on a configurable schedule
→ Run the pipeline automatically so no manual export or import is needed
Getting data out of DHIS2 in a consistent, analysis-ready format is harder than it sounds, especially for large datasets spanning multiple periods, org unit levels, or programs. Direct API calls often hit server limits or return incomplete data.
OpenHEXA’s DHIS2 pipelines handle all of this reliably, including dynamic chunking of large requests to prevent server overload. The result is a clean, structured dataset in OpenHEXA, ready for notebooks, dashboards, or download.
What OpenHEXA does
→ Connect any DHIS2 instance in a couple of second
→ Use the available template pipelines to extract your data
→ Run the pipeline on any given data element and period
→ Store the data directly in OpenHEXA in a table or file, or open it in the integrated JupyterHub to do your data science work
Watch it in action: 5-minute demo of DHIS2 data extraction with OpenHEXA.
DHIS2 holds your routine health data, but some questions cannot be answered with routine data alone. Coverage rates need population denominators. Disease burden analysis needs climate or demographic context. Supply performance needs LMIS data.
OpenHEXA lets you pull in external data sources alongside your DHIS2 data, align them on a shared org unit hierarchy, and push enriched indicators back into DHIS2 or use them directly in dashboards and reports.
What OpenHEXA does
→ Connect population data (WorldPop) for coverage denominators
→ Integrate climate data (ERA5) for disease burden modelling
→ Merge LMIS/supply chain data (OpenLMIS, mSupply) with DHIS2 indicators
→ Push computed/enriched values back into DHIS2
→ Use enriched datasets in notebooks, dashboards, or automated reports
Ministries of Health
NGOs & implementing partners
UN agencies & donors
Run a free audit on your DHIS2 instance, or book a demo to see OpenHEXA in action.
