Ram Chandra Poudel

I have spent twelve years designing, implementing, and scaling health information systems — national interoperability platforms, municipal HMIS rollouts, emergency-scale public services, and AI-enabled digital health products. The work has run across government, healthcare, and academic settings, which is a useful education in why technically correct systems still fail.

As Co-Founder and Chief Technology Officer of Amakomaya, I lead technology strategy, architecture, AI adoption, and engineering delivery for a maternal and neonatal health platform recognised nationally for reaching rural and underserved populations. In parallel I work as a senior digital health consultant, partnering directly with the Ministry of Health and Population, the Integrated Health Information Management Section, municipal health authorities, and development partners.

That consulting work is deliberately unglamorous in parts. Alongside designing Nepal’s national FHIR interoperability platform, it has meant assessing the national DHIS2 HMIS across infrastructure, configuration, data integrity, and security — and then fixing what the assessment found, from metadata defects and unmanaged log growth to user-management SOPs and password policy. National systems are mostly kept alive by that kind of attention.

I hold a Master of Health Informatics from Kathmandu University and an MBA from ACE Institute of Management. The combination is intentional. Most digital health failures are organisational before they are technical, and the people who can only diagnose one half of that tend to prescribe the wrong fix.

For five years I taught software engineering, information systems, and data analytics at undergraduate level, mentoring over 500 students. I have also trained more than 300 healthcare professionals in health system use, analytics, and mobile health platforms. Both are the same discipline: if you cannot explain the system to the people who have to run it, you have not finished designing it.

• Standards before bespoke integration. FHIR, SNOMED CT, ICD-11, and OpenHIE exist so that the next connection is cheaper than the last one. Custom JSON is a loan against future work.
• Open source, stewarded properly. DHIS2, OpenMRS, OpenIMIS, and Open Concept Lab — contributed back as implementations and configurations the wider community can reuse.
• Usability is an architecture concern. The Nepali calendar work in DHIS2 was a two-line problem for a designer and a real barrier for every health worker entering data.
• Security and privacy are structural. ISO/IEC 27701, HIPAA, GDPR, and audit practice inform the design rather than getting retrofitted before a review.
• The handover is the deliverable. Implementation guidelines, SOPs, documentation, and training decide whether a system survives the team that built it.

Digital transformation

AI & data science

Privacy, security & compliance

Project management & leadership

Business analysis & consulting

Process improvement

• Presented DHIS2/eHMIS rollout models at regional digital health forums.
• Contributed to Nepal’s Health Information System interoperability roadmap and national FHIR implementation guidelines.