Why We Run a Dual FHIR + openEHR Architecture (And What It Actually Costs)

Sun, 01 Nov 2026 00:00:00 +0000

On paper, the pitch for a dual-model clinical data architecture is clean: use openEHR archetypes for structured, meaning-preserving clinical documentation, and HL7 FHIR resources for interoperable exchange. Two models, each doing what it’s best at. I’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’s worth being honest about what it buys you and what it costs.

Architecture on Notes from the Health Informatics Architect

Why We Run a Dual FHIR + openEHR Architecture (And What It Actually Costs)