Skip to content
DWKD

Daily brief · 20 September 2026

Interoperable does not mean integrated

Two systems can both be standards-compliant and still disagree about the patient. Where the gap actually lives.

What happened

A health system announced FHIR compliance across its estate. Their clinicians still cannot see an outside record at the point of care.

Why it matters

Compliance is about message format. Integration is about meaning.

Two systems can both emit valid FHIR and still disagree on what counts as an active problem, which identifier is authoritative, or whether a cancelled appointment is a status change or a new message.

The standard is a starting point, not a guarantee.

What to learn

The gap is almost always in three places: identity resolution, code set translation, and who wins when two records conflict. None of them are solved by the standard.

What to try

Take one patient who exists in two of your systems. Print both records. Circle every field that disagrees. That page is your actual integration backlog.

Worth stealing

The pre-build checklist. Line four is the one that saves the quarter: who owns the mapping document after go-live?