{"id":16581,"date":"2026-04-02T16:49:18","date_gmt":"2026-04-02T15:49:18","guid":{"rendered":"https:\/\/www.openhexa.com\/?page_id=16581"},"modified":"2026-04-16T12:30:44","modified_gmt":"2026-04-16T11:30:44","slug":"what-you-can-do-withopenhexa-dhis2","status":"publish","type":"page","link":"https:\/\/www.openhexa.com\/fr\/integrations\/what-you-can-do-withopenhexa-dhis2\/","title":{"rendered":"OpenHEXA – DHIS2"},"content":{"rendered":"
\n
\n \n\n

Get more out of your DHIS2 data with OpenHEXA <\/mark><\/h1>\n\n\n <\/div>\n <\/div>\n \n\n
\n
\n \n

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.<\/p>\n\n

Discover what it looks like in practice.<\/p>\n\n\n

\n
<\/div>\n\n\n\n
Try the free DHIS2 audit tool<\/a><\/div><\/div><\/div>\n<\/div><\/div><\/div>\n\n\n <\/div>\n <\/div>\n \n\n
\n
\n \n\n
Use cases<\/h5>\n\n\n

Discover how OpenHEXA supports your DHIS2 instance management<\/h2>\n\n <\/div>\n <\/div>\n \n\n
\n
\n \n
\n
\n
\n
\n \n 1 <\/span>\n \n \n <\/svg>\n <\/div>\n

<\/h3>\n <\/div>\n \n\n

Audit & maintenance<\/h3>\n\n\n\n

Find issues with the audit tool, fix them with OpenHEXA<\/h4>\n\n\n\n

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.<\/p>\n\n\n

\n
\n

Step 1: Audit tool<\/strong>\u00a0(dhis2-audit.bluesquare.org<\/a>): connect to your DHIS2 instance and run checks across different modules. Without storing any data, the tool surfaces what could be improved.<\/p>\n\n\n\n

Step 2: OpenHEXA<\/strong>: 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.<\/p>\n<\/div>\n\n\n\n

\n

What OpenHEXA fixes<\/mark><\/strong><\/p>\n\n\n\n

\u2192<\/mark><\/strong> Extract list of inactive users (e.g. no login in 90+ days) and disable automatically
\u2192<\/mark><\/strong> Remove or archive orphan data elements with no associated datasets
\u2192<\/mark><\/strong> Fix broken UID references in indicator formulas
\u2192<\/mark><\/strong> Clean up org unit metadata inconsistencies
\u2192<\/mark><\/strong> Schedule recurring cleanup pipelines to keep the instance healthy<\/p>\n<\/div>\n<\/div>\n\n

\n
Try the audit tool<\/a><\/div><\/div><\/div>\n<\/div>\n\n <\/div>\n <\/div>\n \n\n <\/div>\n <\/div>\n \n\n
\n
\n \n
\n
\n
\n
\n \n 2 <\/span>\n \n \n <\/svg>\n <\/div>\n

<\/h3>\n <\/div>\n \n\n

Instance synchronisation<\/h3>\n\n\n\n

Connect multiple DHIS2 instances<\/h4>\n\n\n
\n
\n

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. <\/p>\n\n\n\n

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. <\/p>\n<\/div>\n\n\n\n

\n

What OpenHEXA does<\/mark><\/strong><\/p>\n\n\n\n

\u2192<\/mark><\/strong> Connect multiple DHIS2 instances through ready to use pipelines
\u2192<\/mark><\/strong> Extract aggregate data, data elements, indicators or metadata from the source instance
\u2192<\/mark><\/strong> Push data into the target instance on a configurable schedule
\u2192<\/mark><\/strong> Run the pipeline automatically so no manual export or import is needed<\/p>\n<\/div>\n<\/div>\n\n

\n
Discover how it works<\/a><\/div><\/div><\/div>\n<\/div>\n\n <\/div>\n <\/div>\n \n\n <\/div>\n <\/div>\n \n\n
\n
\n \n
\n
\n
\n
\n \n 3 <\/span>\n \n \n <\/svg>\n <\/div>\n

<\/h3>\n <\/div>\n \n\n

Data extraction<\/h3>\n\n\n\n

Extract DHIS2 data in a predictable format<\/h4>\n\n\n
\n
\n

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. <\/p>\n\n\n\n

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.<\/p>\n<\/div>\n\n\n\n

\n

What OpenHEXA does<\/mark><\/strong><\/p>\n\n\n\n

\u2192<\/mark><\/strong> Connect any DHIS2 instance in a couple of second
\u2192<\/mark><\/strong> <\/strong>Use the available template pipelines to extract your data
\u2192<\/mark><\/strong> <\/strong>Run the pipeline on any given data element and period
\u2192<\/mark><\/strong> <\/strong>Store the data directly in OpenHEXA in a table or file, or open it in the integrated JupyterHub to do your data science work<\/p>\n\n\n\n

<\/p>\n<\/div>\n<\/div>\n\n\n

Watch it in action:<\/strong> 5-minute demo of DHIS2 data extraction with OpenHEXA.<\/p>\n\n\n

\n
<\/div>\n\n\n
\n