DHIS2 eHMIS transformation

Municipal health reporting was paper-based, which meant routine data arrived late, incomplete, or not at all. Digitizing it is the obvious answer and the usual failure: systems get deployed, training happens, and six months later staff are back on paper.

In Nepal one reason was specific and unglamorous. DHIS2 expects Gregorian dates. Health workers work in Bikram Sambat. Every single data entry required a mental conversion, and every conversion was a chance to enter the wrong date.

I led the rollout end to end, and treated the calendar problem as a platform defect rather than a training problem.

• Ran the full implementation cycle in Tokha and Gokarneshwor: requirements, configuration, metadata design, data migration, training, and post-deployment support.
• Migrated 20,000+ health records, improving completeness and timeliness of routine reporting.
• Built Java-based Bikram Sambat calendar integration into DHIS2, resolving date-handling defects and removing the conversion step from every data-entry interaction.
• Built DHIS2 dashboards so the municipalities could see their own data rather than only reporting it upward.
• Delivered training as part of the rollout, not as a hand-off event at the end of it.

• DHIS2
• Java
• PostgreSQL
• Data migration
• ETL
• DHIS2 dashboards
• Bikram Sambat calendar

Two municipalities moved to digital routine reporting with measurably better completeness and timeliness — and the calendar localization removed a usability barrier that affected DHIS2 users well beyond these two deployments.

• 20,000+ health records digitized across two municipalities.
• Improved completeness and timeliness of routine health reporting.
• A long-standing date-entry usability barrier removed for local health workers.
• Operational dashboards putting data back in the hands of the people who collect it.