DHIS2 as a Data warehousing platform

Part of the DHIS2 as Data Warehouse - Country implementation stories DAC2021 Session: Wednesday 23nd June 15:00

If you are attending the DHIS2 Annual Conference, more details on this session are available here.

If you have not yet registered to the DHIS2 Annual Conference, do not hesitate to visit the DHIS2 Annual Conference website and secure your spot!


Mr. Ikramuddin Himmat Yar -Country Coordinator-IOUNV-Kabul-Afghanistan

The HMIS department in the EHIS directorate is mandated to manage the information systems used by the programs in Ministry of Public Health (MoPH). However, several donors have been supporting the programs to have vertical data management systems, and also population based surveys created a heterogenic environment of information systems. The scattered data management in the MoPH resulted in duplicated /triplicate data elements in the different data collection forms and reporting systems. Subsequently, this environment made the data access and analysis very difficult and cumbersome.
To overcome the heterogenic environment and facilitate D3 (Data Driven Decision making), MoPH come up with the idea of data warehousing. Ministry of Health has chosen DHIS2 as a data warehousing platform and HMIS department as leading of the process. The four (4) data sources selected for integration in the DHIS2 as a pilot included: HR, HMIS (EPI, TB, DDR, Blood-Bank), EMIS (Expenditure Management Information System) and Pharmaceutical.‚ÄĚ

Four major data sources we have selected includes different nature in terms of types of data, which are:

HMIS: Aggregate data
HR: individual data
Pharmaceutical: transactional data
EMIS (Expenditure Management Information System): transactional data

We intentionally selected these different types of data sources to test the real scenario. So, we started from HMIS first and this was easy work because our HMIS was already in aggregate types of data and the system (database) was modeled in (EAV: Entity Attribute Value) which almost matches the model of DHIS2. So, data elements, data Sets and categories were already clear and defined within the HMIS database. We just developed a custom ETL (Extract Transform and Load) to extract data from our HMIS and load it into DHIS2 so Here with HMIS actually no/little transformation happened.
Having integrated our HMIS system, we went for EMIS. Our EMIS system is a transactional system, which records expenses of MoPH, and its partners based on unified Chart of Account. So, to facilitate the triangulation of data between data sources, data sharing and data use we identified a list of key indicators/data elements from EMIS and then we developed a procedure within the ETL to aggregate data from the EMIS. After integrating these two systems, we continued to integrate the other two systems almost with the same methodology. (Quoting by: Dr. Lutfullah Shifa)

Refer to:


Dear UiO, First of all, a country use case should be confirmed with MoPH as this use case not representing our country use case, 2nd Mr. Hikmatyar not resenting the MoPH nor HMIS or any other partner contributor in the DHIS2 implementation in the Afghanistan, The DHIS2 implementation supported under USAID HSR with close collaboration of MoPH, Dr.Lutfullah Shifaa is the main lead person from the MoPH side while I, Sam Kasozi and Mr.Baktash Saleh represented HSR project with technical support, The implementation success story also published by UiO a reference link Impact Stories - DHIS2.
Also worth mentioning that I and Baktash currently supporting the implementation of the MoPH data warehouse under USAID another project called AFIAT, implementing by MSH.

We are so sorry for worse presentation.

Questions during the session (from the zoom chat):

From @taufiqhs:
Q: How to measure the data quality from many sources?