Insights
Implementation guides for HL7, FHIR, patient identity and clinical data exchange.
Map a de-identified ORU/OBX fragment onto Observation.code and value[x] using HL7 v2-to-FHIR 1.0.0. LOINC binds observations; SNOMED binds problems and allergies as the IG maps them. Local codes fail first, not PID.
A product-team guide to AU Core R2 (published 28 January 2026), AU eRequesting R1, the Australian IHI, and why hybrid HL7 v2 plus FHIR still carries orders and results.
What C-CDA is (CDA R2, C-CDA R2.1 through 5.0, CCD and the other document types, templateIds, ONC requirements) and how to map C-CDA documents to FHIR Composition and DocumentReference, including MHD versus XDS and Swiss EPR MHD.
A product-team map of ISiK (hospital interface), MIO (KBV ePA objects), MII Kerndatensatz and HL7 DE Basisprofile — plus the gematik INA statement that Germany stays on FHIR R4 until a national calendar exists.
FHIR UK Core is the four-nation R4 profile baseline. NHS England catalogue APIs — PDS, EPS, e-Referral, BaRS and MESH/ITK3 — are separate products. Care Connect STU3 is deprecated.
A playbook for projecting HL7 v2 ADT A01, A04, A08 and A03 onto FHIR Patient and Encounter — PID-3 versus identifier.system, PV1-19 visit numbers, and de-identified test fixtures.
Showing 13–18 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.