What we examine in depth.
In-depth technical articles on clinical interoperability — CDA-to-FHIR migration, terminologies, ontologies and FHIR profiling. From project practice, mirrored against formal methodology.
HL7 CDA in the light of modern FHIR approaches
HL7 Clinical Document Architecture (CDA) has been a central standard for the electronic exchange of clinical documents for many years—from physician letters to diagnostic reports.
Read full article →CDA → FHIR without a Big Bang (Part 1): Migration patterns that work in practice
Many organizations face the same task: keep operating CDA-based document landscapes while at the same time establishing FHIR for modern interfaces, workflows, and data platforms.
Read full article →CDA → FHIR without a Big Bang (Part 2): Pitfalls, quality rules, and a cutover checklist
Part 2 describes why CDA→FHIR projects often fail not at “mapping” but at terminology, identifiers, narratives, testability, and governance.
Read full article →Documents with FHIR: IHE MHD as a bridge between document flow and the FHIR world
IHE MHD (Mobile access to Health Documents) connects document-based reports (PDF/CDA) with the modern FHIR API world: metadata, search, retrieval, versioning.
Read full article →Terminologies in FHIR: Without SNOMED/LOINC, It Gets Expensive — How to Keep Code Systems Under Control
FHIR isn’t the hard part — semantics is. Why LOINC, SNOMED CT, UCUM, ValueSets and ConceptMaps determine cost and interoperability — with practical guidance, callouts, checklist and a small graphic.
Read full article →Ontologies and ISO-compliant metadata as a sustainable foundation for HL7 FHIR in healthcare
The increasing digitalization in healthcare is leading to a growing amount of heterogeneous data that is intended to be exchanged across organizational boundaries and remain reusable in the long term.
Read full article →FHIR profiles are not an end in themselves
Why stable FHIR profiles begin with use cases, governance, and testability – not with constraints. Fewer profiles, but better ones – as robust contracts for interoperability.
Read full article →Considerations for using AI to model data exchange (interoperability) in FHIR
This article outlines where AI can meaningfully support interoperability work with HL7 FHIR—not as an autopilot, but as a co‑pilot that accelerates consolidation, documentation, and quality checks.
Read full article →