<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Notes from the Health Informatics Architect</title><link>https://vedprakash.vamihealth.in/</link><description>Recent content on Notes from the Health Informatics Architect</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 01 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://vedprakash.vamihealth.in/index.xml" rel="self" type="application/rss+xml"/><item><title>About</title><link>https://vedprakash.vamihealth.in/about/</link><pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate><guid>https://vedprakash.vamihealth.in/about/</guid><description>&lt;p&gt;I&amp;rsquo;m Ved Prakash, a Java and J2EE architect with 18+ years of experience building enterprise-grade, cloud-native applications — with deep specialisation in health interoperability standards including HL7 FHIR (R4/R5), openEHR, IHE integration profiles, and clinical terminology systems (SNOMED CT, LOINC, ICD-10/11).&lt;/p&gt;
&lt;p&gt;I currently serve as &lt;strong&gt;CTO of dChikitsa Private Limited&lt;/strong&gt; and &lt;strong&gt;Co-Founder &amp;amp; CTO of Akhester Technologies&lt;/strong&gt;, leading architecture and delivery of open, standards-compliant digital health platforms for national and international healthcare markets — including my current role as Solutions Architect on a UNOPS-contracted national digital health platform in Sri Lanka (HAPI FHIR, IHE XDS.b/ATNA/BALP, NEHR/NHDX alignment).&lt;/p&gt;</description></item><item><title>Projects</title><link>https://vedprakash.vamihealth.in/projects/</link><pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate><guid>https://vedprakash.vamihealth.in/projects/</guid><description>&lt;p&gt;A selection of the national digital health platforms, open-source infrastructure, and commercial products I&amp;rsquo;ve architected and built.&lt;/p&gt;
&lt;h2 id="national--government-platforms"&gt;
 National &amp;amp; Government Platforms
 &lt;a class="heading-link" href="#national--government-platforms"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Digital Health Platform — Ministry of Health and Mass Media, Sri Lanka&lt;/strong&gt; &lt;em&gt;(UNOPS)&lt;/em&gt;
Solutions Architect on a UNOPS-contracted national digital health programme, spanning three workstreams:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Digital Health Information Warehouse&lt;/strong&gt; — secondary-use data warehouse for population health analytics&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Platform Support Services&lt;/strong&gt; — generic, reusable FOSS components shared across the national platform&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Document and Imaging Repository&lt;/strong&gt; — a HAPI FHIR JPA document repository (ITI-65 Provide Document Bundle, ITI-67 Find Document References, ITI-68 Retrieve Document, ITI-105) paired with an Orthanc DICOMweb server (STOW-RS, WADO-RS, QIDO-RS) and a Record Locator service resolving cross-facility document and imaging pointers at national scale — with PDPA-compliant consent enforcement, SHA-256 document integrity verification, and IHE ATNA/BALP-compliant audit logging, aligned to Sri Lanka&amp;rsquo;s national NEHR/NHDX systems&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This work sits on an open-source stack throughout — HAPI FHIR, Orthanc, and SeaweedFS object storage — chosen deliberately so the Ministry owns and can run the infrastructure without vendor lock-in.&lt;/p&gt;</description></item><item><title>Videos</title><link>https://vedprakash.vamihealth.in/videos/</link><pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate><guid>https://vedprakash.vamihealth.in/videos/</guid><description>&lt;p&gt;Talks, walkthroughs, and technical deep-dives on health interoperability, FHIR, and digital health architecture.&lt;/p&gt;
&lt;div class="video-grid"&gt;
&lt;div class="video-card"&gt;
&lt;div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;"&gt;
 &lt;iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/ogmVKP2xQmQ?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="YouTube video"&gt;&lt;/iframe&gt;
 &lt;/div&gt;

&lt;p&gt;&lt;strong&gt;OpenMRS Patient Examination — Walkthrough&lt;/strong&gt;
An example of how patient examination is taken and recorded in OpenMRS.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;</description></item><item><title>Why I'm Writing This Blog</title><link>https://vedprakash.vamihealth.in/posts/why-im-writing-this-blog/</link><pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate><guid>https://vedprakash.vamihealth.in/posts/why-im-writing-this-blog/</guid><description>&lt;h2 id="the-gap-i-kept-noticing"&gt;
 The gap I kept noticing
 &lt;a class="heading-link" href="#the-gap-i-kept-noticing"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Interoperability projects generate an enormous amount of knowledge — lessons learned the hard way, trade-offs debated in meeting rooms, workarounds that eventually became best practice. Almost none of it is written down in a form anyone outside the project ever reads. What does get documented is usually formal, sanitized, and locked inside project reports that exist to satisfy a funder, not to teach.&lt;/p&gt;</description></item><item><title>Why We Run a Dual FHIR + openEHR Architecture (And What It Actually Costs)</title><link>https://vedprakash.vamihealth.in/posts/dual-model-fhir-openehr-architecture/</link><pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate><guid>https://vedprakash.vamihealth.in/posts/dual-model-fhir-openehr-architecture/</guid><description>&lt;p&gt;On paper, the pitch for a dual-model clinical data architecture is clean: use &lt;strong&gt;openEHR&lt;/strong&gt; archetypes for structured, meaning-preserving clinical documentation, and &lt;strong&gt;HL7 FHIR&lt;/strong&gt; resources for interoperable exchange. Two models, each doing what it&amp;rsquo;s best at. I&amp;rsquo;ve built this pattern more than once now — across an open-source Patient Management System and EMR, a health information exchange platform, and a national Hospital Information System — and it&amp;rsquo;s worth being honest about what it buys you and what it costs.&lt;/p&gt;</description></item></channel></rss>