DHIS2 for health financing: how data systems help pay frontline health services for results

DHIS2 for health financing: how data systems help pay frontline health services for results

DHIS2 has helped channel hundreds of millions of dollars to the frontlines of global health, and continues to do so.

No country has cut child or maternal deaths in a meaningful way without putting more money into primary health care. Getting that money to the facilities that need it, and making sure it buys real services, is a data problem as much as a funding one.

What is Results-Based Financing?

Results-based financing (RBF) pays primary health care providers based on what they deliver. Performance-based financing (PBF) is the best-known version. In these schemes, payment providers often have to offer care for free, or with lower out-of-pocket charges, in return for payments from the health funding agency. Typically these payments will depend on three elements:

  • The quantity of services delivered : for example how many deliveries have been attended in the health facility.

  • The quality of care, as measured according to quality of care standards defined by programs. Here, RBF programs do not only want to pay for quantity, they also want quality.

  • The quality patients say they received. This is an important part of a PBF scheme, and ensuring the voice of patients and communities are heard in defining what public money should pay for is important.

Some additional dimensions can be added, such as the services received by more vulnerable patients. The payment to be made combines these elements into account to define the monetary amount to be transferred to a health facility. RBF is thus directly linked to universal health coverage (UHC): it pays for results and protects patients from financial hardship at the same time.

Over the past 20 years, more than 30 low- and middle-income countries in Africa, Asia, and the Caribbean have set up funding mechanisms that allocate resources based on results. Many started as pilots supported by the World Bank and other partners. Several have since become national strategic purchasing systems, run by ministries of health or health insurance agencies.

How DHIS2 became the data backbone of some RBF systems ?

An RBF system lives or dies by the data behind it. Every payment has to be traced to verified services at a named facility, computed under transparent rules, and open to audit. In many countries, ministries of health chose DHIS2 to do this.

Bluesquare has worked with ministries of health and their partners to design and implement these systems in a wide range of settings. This covers the full cycle: setting up the data model and payment rules, configuring DHIS2, training national teams, and handing the system over to the people who will run it.

An important part of the RBF system can live in DHIS2, that can structure all the information used to manage payments to be made.

  • Facility accreditation: registering and managing which health facilities can join the scheme through organisation unit management

  • Service packages: defining the services to be purchased, their unit prices, and any equity bonuses attached to them can be made through data elements management.

  • Quality of care: structured checklists used during supervision visits can also be collected in DHIS2 and attached to the health facility.

  • Perceived quality: client satisfaction surveys, often run in the community, are collected in trackers attached to the organisation units of reference

  • Payment orders: while payments are computed outside of DHIS2, the invoices facilitating the release of funds to facilities are edited in DHIS2 so they can be accessed directly in the system by facility managers, as well as health district and province managers.

  • Monitoring and visualization: dashboards for program managers at every level can also be set up in DHIS2 to ensure they have a clear understanding of the programs performance and funding.

In the meantime, Bluesquare has implemented additional tools to for more specific feature needed for RBF:

  • Payment computation. The rules often combine quantity, quality scores, equity weights, and caps, using non linear computations that need to be changed as the RBF scheme evolves. These calculations run in OpenHEXA, Bluesquare’s open-source data integration and analysis platform, which is integrated with DHIS2. Results are written back to DHIS2, so the data stays in one place and every calculation can be traced. Invoices are edited through DHIS2.

  • Risk-based verification. Checking every facility every month is expensive. OpenHEXA uses past reporting patterns to rank facilities by risk of fraud or performance issues. Verifiers can plan their time visiting facilities where errors or over-reporting are most likely or where measured performance seems alarming. Low-risk facilities are checked less often, which cuts verification costs without weakening control.

  • Open data portals. Bluesquare designs and implements public portals that publish, facility by facility, what was delivered, what quality scores were achieved, and what was paid. When citizens, local authorities, and funders can all see the same figures, accountability no longer depends on audits alone, and facilities can compare their performance with their peers.

From projects to national systems

Two decades of RBF suggest that linking funding to results works best when it is built on a strong, country-owned information system. DHIS2 has proven to be a reliable foundation for this. As countries move toward universal health coverage and look for better ways to finance primary health care, the data used to plan, purchase, and account for health services will matter more and more. Countries that already use DHIS2 for routine health data have a strong building block in place for future health financing reforms.

USE CASE

From data to decisions: strategic purchasing in the DRC

Since 2015, Bluesquare has supported the Democratic Republic of Congo’s Ministry of Health and its strategic purchasing unit, the Cellule Technique Achat Stratégique (CT-AS). This support runs under the World Bank-financed PDSS and PMNS projects. By the end of 2024, the DHIS2 strategic purchasing instance covered more than 3,600 contracted facilities in 11 provinces.

How the system is built

DHIS2 at the center

DHIS2 is at the core of the system. Every contracted facility, health area and health zone is recorded as an organisation unit, with its level of care and its location. Boundaries are now available for 96.6% of health areas, and verifiers’ updates to facility locations and boundaries have also been added to the national health map in the HMIS. For each facility, DHIS2 stores the quantities declared, verified and validated, the quality scores and the free-care services. It also holds the PMNS results framework. Program managers follow performance on DHIS2 dashboards.

Open-source Bluesquare add-ons for DHIS2 handle the steps specific to PBF. The Invoice App is used to validate data and edit invoices. Hesabu computes each subsidy from quantities, quality scores, unit prices and equity weights. Results are published on the DataViz public portal and on Apache Superset dashboards that anyone can open without a login. The add-ons and DataViz are now being phased out as OpenHEXA takes over their functions. CT-AS data managers configure and administer the whole system themselves.

How the PBF instance relates to the national HIS

The PBF scheme runs on a dedicated DHIS2 instance, separate from the national DHIS2 that hosts the HMIS. Today, facilities report the same services in both systems: in their routine HMIS reports, and to the verification agencies, which enter declared quantities in the PBF instance. The program’s next phase will connect the two instances in both directions. Declared quantities will come from the HMIS, so facilities report only once. Validated quantities and quality scores will go back to the HMIS, where they can support routine monitoring.

Three innovations, evaluated in 2026

On top of this system, the program introduced 3 innovations. In 2026, the CT-AS evaluated them in 15 health zones of Kwilu, Kasaï and Kasaï Central.

  • Digital verification with IASO
    Verification used to rely on paper forms. Verifiers filled them in and scored them by hand, then entered the results into the system. Verifiers and quality assessors now use IASO on tablets, even where there is no connection. Scores are calculated automatically and each visit is geolocated. Because IASO is interoperable with DHIS2, verification data flow straight back into the DHIS2 PBF instance without being entered a second time.

The evaluation found savings of up to USD 182 per mission on printing, partly offset by spending on mobile data and batteries. Quantity verification missions became 1 to 5 days shorter, depending on the province. Users also report fewer calculation errors, and results can no longer be changed after submission. Connectivity, power cuts and gaps in training still limit these gains.

  • Free deliveries through the PBF system

In PBF facilities, patients usually pay part of the cost of care, known as the user fee. The program now covers this fee for all deliveries, including C-sections, and for the care of sick newborns and sick pregnant women. It needed no new system to do this. Each free service has its own DHIS2 data element, is verified like any other service and is reimbursed on the facility invoice.

In the facilities visited, registers and cash books showed no direct payment for more than 27,000 deliveries in the second half of 2025. The evaluation also surveyed 223 women who had recently given birth in these facilities. Between 87% and 100% of them, depending on the province, said they had paid nothing, and 88% to 100% were satisfied with their care. Assisted deliveries exceeded program targets in all 3 provinces. In Kwilu, quality scores for obstetric services rose by 13 to 35 points.

  • Risk-based verification with OpenHEXA

In a PBF scheme, a facility is paid only after verifiers have checked the services it reported against its registers. Visiting every facility every quarter takes a lot of time and money. Risk-based verification (RBV) concentrates that effort on the facilities most likely to have problems.

Each quarter, OpenHEXA pipelines connect to the DHIS2 PBF instance. For each facility, they compare what it declared, what verifiers found and what was finally validated, then rate it as low, moderate or high risk. Program managers set the thresholds in a settings interface, and a dashboard lists the facilities to visit. High- and moderate-risk facilities are verified every quarter. Low-risk facilities are checked at random and paid on their past validated results, so every facility still has a reason to report accurately.

The program piloted RBV from April to December 2025 in 3 health zones in each province. Verification missions became shorter everywhere: from 22 to 15 days in Kwilu, from 25 to 18 days in Kasaï Central and from 18 to 14 days in Kasaï. In Kwilu, the average quarterly cost of verification fell by about 25%, from USD 4,573 to USD 3,423. Costs also went down in the other 2 provinces, but the difference was not statistically significant.

The data also revealed a weakness. In Kwilu, the gap between declared and validated figures was 19%. It reached 54% in Kasaï Central and 65% in Kasaï, where facilities that were not verified reported less carefully. The CT-AS therefore recommends adjusting the targeting algorithm. In June 2026, the program agreed to extend RBV to all provinces once this adjustment is made.

The evaluation concludes that the 3 innovations reinforce each other. Free care raises demand, PBF supports the quality of care, and digital and risk-based verification keep payments credible.

More about Bluesquare : https://www.bluesquarehub.com/

3 Likes