Insights
Implementation guides for HL7, FHIR, patient identity and clinical data exchange.
How the main FHIR servers differ on licence, FHIR versions, persistence, SMART on FHIR, Bulk Data, Subscriptions, validation and EU hosting, with a selection guide by scenario.
A vendor-neutral comparison of HL7 interface engines in 2026: Mirth Connect licensing after 4.6 and its open-source forks, Rhapsody, IguanaX, Qvera QIE, InterSystems Health Connect, BizTalk and the Azure, Google and AWS healthcare services, with a selection checklist and migration notes.
A field-level reference for HL7 v2 messages: how MSH-9 and the delimiters work, one annotated synthetic sample per common message type, and the pitfalls that break interfaces in production.
A practitioner comparison of openEHR and HL7 FHIR: two-level modelling, AQL and the openEHR REST API against FHIR resources and profiles, with European deployments and the openEHR CDR plus FHIR façade pattern.
ELGA production is still CDA document exchange over IHE XDS. HL7 Austria Core R4 2.0.0 is the FHIR baseline. Austrian Patient Summary FHIR is not live ELGA. Social security number uses urn:oid:1.2.40.0.10.1.4.3.1.
eHealth Platform Federal Core 2.2.0 is the Belgian FHIR baseline. HL7 Belgium community IGs and Patient Dossier CareSets 1.0.0 sit on top. SSIN is the patient identifier. BIHR/EHDS is roadmap, not a live product.
Showing 1–6 of 30 articles
Talk through your integration, data or software delivery needs.
Allow analytics cookies to help understand site visits and enquiries? Optional analytics stays off until you accept.