# Reporting on time and reporting correctly are different problems

> Ethiopia runs one of the world's largest DHIS2 deployments — 30,000+ facilities, 95% reporting rates. The national maturity assessment scores data quality and infrastructure far lower. Submitting a report and submitting a correct one are not the same achievement.

Source: https://www.medicine.et/research/dhis2-data-quality  
Site: Bloom Medicine — https://www.medicine.et  
Last updated: 2026-07-25

---

Digital health · Health information systems · published July 25, 2026

## Key findings

- More than 30,000 public facilities and 5,000 private facilities report through Ethiopia's DHIS2, covering a population over 120 million.
- Between 2018 and 2022, over 95% of government facilities reported consistently, with more than 90% completeness but only about 70% timeliness.
- The national DHIS2 maturity assessment scores implementation at 2.81 of 5 — the 'defined' stage — with ICT infrastructure lagging at 2.14, the 'repeatable' stage.
- Reporting rates measure whether a form arrived, not whether the numbers on it match what happened at the point of care.

Ethiopia's national health information system is genuinely impressive at scale. It is also a good illustration of a distinction that matters inside any clinic: the difference between a report being *submitted* and a report being *right*.

## The scale is real

DHIS2 is Ethiopia's national health management information system. As of 2024, **more than 30,000 public health facilities** report through it, alongside **more than 5,000 private facilities**, covering a population of over 120 million [2].

The reporting performance is strong on its own terms: **more than 95% of government health facilities reported consistently between 2018 and 2022, with more than 90% completeness and around 70% timeliness on average**, and reporting lag fell from up to 26 days under previous systems to as few as 5 days [2].

```chart
{
  "type": "bars",
  "title": "DHIS2 reporting performance, 2018–2022",
  "subtitle": "Each of these measures whether a report arrived and was filled in — none measures whether its numbers are right.",
  "unit": "%",
  "max": 100,
  "highlight": "Timeliness",
  "source": "DHIS2 impact story, 2025 [2]",
  "data": [
    { "label": "Facilities reporting consistently", "value": 95 },
    { "label": "Report completeness", "value": 90 },
    { "label": "Timeliness", "value": 70 }
  ]
}
```

## The maturity assessment is more sober

A national assessment using the Stages of Continuous Improvement tool — covering 5 domains, 13 components and 39 subcomponents, scored 1 (emerging) to 5 (optimized) — placed Ethiopia's DHIS2 implementation at **2.81, the "defined" stage**, with a plan to reach the "managed" stage (4.09) [1].

```chart
{
  "type": "bars",
  "title": "DHIS2 implementation maturity, scored 1–5",
  "subtitle": "1 emerging · 2 repeatable · 3 defined · 4 managed · 5 optimized. ICT infrastructure is the lowest-scoring domain and the target is a stage above where the system now sits.",
  "max": 5,
  "highlight": "ICT infrastructure (current)",
  "source": "Yilma et al. 2024, JMIR Medical Informatics [1]",
  "data": [
    { "label": "National target for 2025", "value": 4.09 },
    { "label": "Other four domains (approx.)", "value": 3 },
    { "label": "National maturity today", "value": 2.81 },
    { "label": "ICT infrastructure (current)", "value": 2.14 }
  ]
}
```

Domain by domain, four of five sit at the defined stage (around 3.0). The exception is **ICT infrastructure at 2.14 — the "repeatable" stage** [1], which is the lowest-scoring domain in the assessment and the one that most directly determines whether a facility can capture data at the point of care rather than reconstructing it later.

## Why the two pictures differ

A reporting rate answers: did this facility send its monthly aggregate on time? A maturity score asks whether the system underneath — governance, skills, infrastructure, interoperability, data quality and use — can be relied on.

The gap between them is where aggregate reporting quietly decouples from clinical reality. And there is direct Ethiopian evidence for how that happens: in a review of 2,145 medical records across 73 public health facilities, only **18.4% were complete and readable**, with **20.1% recording no diagnosis** and **60.3% carrying no date and/or signature** [3].

A monthly report compiled from those records can be complete, timely, and still wrong — because the primary record it was compiled from was incomplete before anyone opened the reporting form. **Timeliness is a property of the report. Accuracy is a property of the point of care.**

## What this means inside a clinic

1. **Capture once, at the point of care.** Every step between the clinical event and the number in the report is an opportunity for the two to diverge. Ethiopian providers describe re-entering data by hand between systems as "a burden" — and hand re-entry is where discrepancies enter.
2. **Reporting compliance is not a data-quality metric.** A clinic can be fully compliant and have unusable data. They are separate things and should be measured separately.
3. **Infrastructure is the binding constraint, not the software.** ICT infrastructure is the weakest domain in the national assessment [1]; at clinic level that reads as power, devices and connectivity — the things to fix before choosing a system.
4. **Aggregate numbers cannot be audited backwards.** If the source record has no date, no signature and no diagnosis, the report derived from it cannot be checked. Verification has to start at the chart.

## What this note does not claim

The deployment figures in reference [2] come from a DHIS2 programme communication, not from peer-reviewed research — we cite them for scale, which is not contested, and flag the source accordingly. The maturity assessment [1] is a consultative, workshop-based self-assessment involving national stakeholders; that is the standard method for this instrument, but it is not an independent audit.

Neither source measures how accurately individual facility reports reflect underlying patient records. The record-quality study [3] is from public facilities in one region and was not designed to validate DHIS2 submissions; the link drawn here between poor primary records and unreliable aggregates is an inference, and a well-supported one, but not a measured chain in a single study.

## References

1. Yilma TM, Taddese A, Mamuye A, Endehabtu BF, Alemayehu Y, Senay A, et al. *Maturity Assessment of District Health Information System Version 2 Implementation in Ethiopia: Current Status and Improvement Pathways*. JMIR Medical Informatics 12:e50375, 2024. https://doi.org/10.2196/50375
2. DHIS2 (University of Oslo). *Enhancing Healthcare Performance in Ethiopia Using DHIS2*. dhis2.org impact story, published 28 February 2025, 2025. https://dhis2.org/enhancing-healthcare-in-ethiopia-using-dhis2/ — Programme communication from the software's developer, not peer-reviewed. Deployment scale figures are cited from it; interpretation is ours.
3. Endriyas M, Kawza A, Alano A, Lemango F. *Quality of medical records in public health facilities: A case of Southern Ethiopia, resource limited setting*. Health Informatics Journal 28(3):14604582221112853, 2022. https://doi.org/10.1177/14604582221112853