What we think and write.
Observations from practice — mainly on the gap between FHIR go-live and sustainable data integrity. Condensations from mandates, mirrored against formal methodology.
Interoperability Is Not an Export Button
Why “we export FHIR” and “we send a PDF” are two very different promises — transport is not meaning. On systematic semantic information loss at clinical system boundaries.
Read full article →FHIR Is Not a Modern Interface — It Is an Architectural Decision
Why “we need a FHIR API too” rarely means progress — and what separates the architectural decision from the format decision.
Read full article →An Integration Problem — or a Data Model Problem?
Hospitals believe they have an integration problem and build more and more interfaces. Why that raises complexity instead of resolving it.
Read full article →What FHIR Validation Does NOT Check
A FHIR bundle passes validation — the structure is correct. On the four canonical loss patterns that survive any formally valid transfer.
Read full article →What Did Not Change
Over thirty years the technology moved from HL7 v2 to FHIR. The tools improved — the same four losses at the system boundary stayed.
Read full article →Go-live is a project. Operations is a discipline.
The actual test doesn’t start with the first successful API call, but six months later — when it shows whether profiles, terminologies and mappings are actually maintained.
Coming soonProfiles as contracts.
A FHIR profile is not a technical document — it’s a contract between source and target system. What the contract doesn’t fix gets lost in the first mapping.
Coming soon