Deep dives into FHIR, openEHR, IHE, and the architecture decisions shaping modern health information exchange.
We've joined the openEHR Specifications Editorial Committee (SEC) Experts Panel. A moment to reflect on what that means, how we got here, and why openEHR continues to be at the center of everything we build.
Read articleAt HL7's Converge & Collaborate in Dublin, we ran a hands-on "Let's Build" session where participants assembled a working FHIR facade on top of an openEHR CDR, step by step, using FHIRConnect mappings and openFHIR to generate a real IPS Bundle — no proprietary glue required.
Read articleThe Dutch Ministry of Health (VWS) is building reusable national infrastructure called Generic Functions, covering addressing, routing, consent, identification, authentication, and authorization. Here's how they work, and more importantly, where openEHR fits into the picture.
Read articleCan openEHR and FHIR truly work together without proprietary glue? This webinar walks through the International Patient Summary use case end to end — from the gap between the two standards to a live demo of openFHIR generating an IPS from an openEHR CDR.
Read articleIHE defines how systems exchange data. openEHR defines what that data means at its core. At the IHE Connectathon in Brussels, openEHR International and IHE explored where these two worlds overlap — and what a truly vendor-neutral, semantically rich architecture could look like.
Read articleA working proof-of-concept showing how the Dutch national care transfer standard can be implemented in a hybrid openEHR + FHIR environment — covering mCSD routing, ACP data models, and vendor-neutral design.
Read articleDespite momentum toward FHIR adoption, XDS remains extensively used across Europe. This article explores how Firely Server acts as a FHIR interface over XDS systems through MHD, mXDE, and QEDm profiles.
Read articleRunning analytics directly on production clinical databases creates serious risks. This article presents an architecture using Firely Server integrated with Elasticsearch, Logstash, Kibana, and RabbitMQ to keep analytics isolated and safe.
Read articleFHIR and openEHR will coexist rather than compete. This article explores how Firely Server can be configured as a gateway, routing FHIR requests to an openEHR backend via custom plugins and the openFHIR mapping engine.
Read articleA practical walkthrough of implementing the FHIR DS4P Implementation Guide as a Firely Server plugin, covering custom search parameters, IReadAuthorizer services, and inline security label enforcement.
Read articleAfter the IHE Connectathon in Rennes, the Vitaly platform achieved full compliance across MHD, International Patient Summary, mXDE, QEDm, and legacy XDS profiles — plus a FHIR federation component for multi-server querying.
Read articleNUTS is a joint initiative by healthcare software suppliers to develop an open-source protocol regulating access to healthcare data. This article covers how it works, how it integrates with Vitaly, and a proof-of-concept implementation.
Read articleBehind every virtual MDT meeting lies a stack of interoperability standards. This article examines how SMART on FHIR, XDS, IHE Cross Enterprise Workflow, Master Patient Index, and QEDm combine to make collaborative clinical decision-making work at scale.
Read articleTechnical integration is only the first phase. The real opportunity emerges when organisations leverage integrated data to create meaningful solutions. This article introduces two use-case-driven applications built on an interoperable platform foundation.
Read articleReal-world healthcare interoperability requires pragmatism. This article traces an evolution through five stages of understanding standards in health IT, and the value of remaining flexible across XDS, FHIR, and HL7v2 rather than over-committing to any one approach.
Read article