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.
Who Maintains the FHIR Profiles After Go-live?
Go-live is a project, operations is a discipline. On maintaining profiles, terminologies and mappings — and how to tell whether governance is alive.
Read full article →What Your FHIR Profile Does Not Say
A FHIR profile is a contract between source and target system. What it fixes survives the mapping — what it leaves open is lost silently.
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 →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 →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 →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 →