Sustainability of dhis2 utilization

This community innovation has been accepted at the 2025 DHIS2 Annual Conference


SUSTAINABILITY OF DHIS2 UTILIZATION

The Zambia National Public Health Institute developed the electronic Integrated Disease Surveillance and Response (eIDSR) using the DHIS2 in 2019. The institute transitioned from excel based database to DHIS2 database. Having deployed the system to all the 10 Province, 116 Districts and 2480 Health Facilities, the ZNPHI embarked on a quest to sustain the gains accomplished through the use of DHIS2, by implementing the following measures; 1. Incorporated costs of running and maintaining the DHIS2 in annual action plans. The costs involved training, hosting, internet and equipment such as serves, tablets and laptops. As of to date more about 2000 tablets have been purchased to support data capturing. The ZNPHI also planned and budgeted for cost to migrate the instance from cloud hosting to local hosting which was successfully done in adherence to government policies on management of systems. 2. Mobilized resource for expansion, enhancement and operations through strategic partnership engagement. The ZNPHI so far has drawn support that has helped to sustain DHIS2 from US Centres for Disease Control and Prevention, Evidence for Health, World Bank, Resolve to Save Lives, World Health Organization and UNICEF. The support has been used to enhance DHIS2 capacities to capture data, create linkages with laboratory. Conclusion: To sustain the use of DHIS2 there is need to plan and budget for the system once deployed. This can be accomplished through advocacy and partnership engagements that aid mobilization of resources to support hosting of the system, training of staff, purchase and maintenance of equipment and internet costs. The DHIS2 related costed must be budgeted for in annual work plan and prioritized at all levels of the health care system

Primary Author: Dindi Miyoba


Keywords:
Plan and Budget

2 Likes

Dear @m_dindi

Nice information shared, you dont talk about the developed pieces if you used core or custom app, otherwise sustaining custom app needs to be planned and addressed too.

Looking forward to the presentation at DAC25