The Short Answer
DHIS2 stands for District Health Information Software 2. It is an open-source, web-based platform for collecting, managing, visualising, and analysing health data originally developed by the University of Oslo's HISP programme and maintained by a global community of contributors. It is free to use; you pay for servers, implementation, configuration, training, and support, but the platform itself carries no licence fee.
DHIS2 is not one tool. It is a platform with multiple modules that can be configured for different purposes.
What DHIS2 Is Built to Do
DHIS2 handles two fundamentally different types of health data, each supported by a distinct module.
Aggregate Data: Counting What Happens
The aggregate module handles periodic summary data counts, rates, and proportions reported by facility, district, or national level on a defined schedule. In Nigeria, the NHMIS (National Health Management Information System) runs on DHIS2's aggregate module. Every facility submits monthly reports through this system, and those reports feed national health statistics.
Aggregate data is fast to collect, transmits well in low-bandwidth environments, and is sufficient for monitoring trends and programme performance at population level. It does not tell you anything about individual patients.
Tracker: Following Individual Cases
DHIS2 Tracker is the individual-level module. Instead of counting aggregate events, it tracks individual people or cases through a defined workflow from initial registration through to outcome. Tracker is used for disease outbreak surveillance, contact tracing, maternal health follow-up, and immunisation records.
The Mpox surveillance system I configured in Imo State ran on DHIS2 Tracker. Each of the 231 investigated cases had an individual record linked to their LGA, investigation timeline, laboratory result, and outcome. That individual-level data enabled the epidemiological analysis published in peer-reviewed literature. For configuration detail, see DHIS2 Tracker Configuration for Outbreak Surveillance.
What DHIS2 Is Not
- Not a clinical record system. It is not designed to replace hospital information systems or manage clinical care delivery. If your use case involves managing care for individual patients, DHIS2 is the wrong tool.
- Not a laboratory information system. It can receive laboratory results, but does not manage laboratory workflows. Dedicated LIMS exist for that purpose.
- Not plug-and-play. Every DHIS2 implementation requires configuration. A DHIS2 server with no configuration is a blank platform. Technical configuration takes months; getting data flowing reliably takes longer.
- Not a data quality guarantee. The system stores whatever is entered. If facilities report incorrect data, DHIS2 will aggregate and display that incorrect data faithfully. Data quality requires active management validation rules, completeness monitoring, regular audits, and feedback loops. The platform enables this work; it does not replace it.
How DHIS2 Is Structured: Organisational Units
One of DHIS2's most powerful features is its organisational unit hierarchy. A typical Nigerian DHIS2 instance is structured as:
- National (Federal level)
- State (36 states plus FCT)
- Local Government Area (774 LGAs nationally)
- Ward
- Facility (Primary Health Centre, General Hospital, etc.)
Every piece of data entered in DHIS2 is associated with an organisational unit. A case registered at a facility in Owerri North LGA is automatically visible in the Imo State dashboard and the national dashboard without manual aggregation. The hierarchy does the work.
DHIS2 and Other Systems: The Integration Question
DHIS2 and SORMAS: SORMAS is purpose-built for rapid outbreak response with pre-configured workflows for specific diseases. Integration between the two SORMAS managing active outbreak response, DHIS2 receiving aggregate surveillance data is the approach used in several Nigerian states.
DHIS2 and ODK: Open Data Kit is a mobile data collection tool for surveys, community surveillance, and field data collection. ODK data can be imported into DHIS2 for aggregate analysis. The two tools are complementary: ODK for field collection, DHIS2 for management and analysis.
DHIS2 and national reporting: DHIS2 is increasingly used for international disease notification data from the national instance feeds into WHO's Health Emergency Preparedness and Response systems, supporting IHR reporting obligations.
Why DHIS2 Matters in West Africa
I have seen what happens when DHIS2 works as designed: a suspected measles cluster in a rural LGA is identified on a Thursday morning because Tracker data triggers an alert threshold; by Friday, investigation teams are deployed; by the following week, vaccination response is underway. A 60% reduction in outbreak confirmation time is the difference between a contained outbreak and a humanitarian crisis.
I have also seen what happens when DHIS2 is poorly implemented: dashboards showing data from six months ago, surveillance alerts that no one receives, case data that cannot be used because the configuration never mapped to any decision that anyone needed to make. The technology is not the variable. The architecture is.
Getting Started: Next Steps
If you are implementing or strengthening DHIS2 in your programme, the sequence matters: design the data flow before touching configuration; define the decisions the system needs to support before defining data elements; build dashboards for the decision-maker's question, not the data manager's report.
The next article in this series goes deeper on dashboards: DHIS2 Dashboard Best Practices: Designing Dashboards That Drive Decisions.