Lab workflows sit at an awkward intersection of FHIR and legacy HL7 v2. Most reference labs still ship results over v2 ORU messages, while ordering systems are increasingly moving to FHIR ServiceRequest and Observation resources. A FHIR int
Popular Posts
-
-
ACO reporting is the use case where FHIR $export stops being a spec feature and starts being load-bearing infrastructure. An accountable care organization aggregating data across multiple provider organizations needs to ingest population-sc
-
Five FHIR integration engines dominate serious 2026 procurement conversations, each with a recognizable buyer profile. The reviews below are deliberately short; deep evaluation belongs in a pilot with real traffic patterns, not in a roundup
-
Migrating a FHIR deployment from sequential integer ids to UUIDs is a two-quarter project done well and a two-year cleanup done poorly. Every existing reference has to be rewritten, every downstream cache invalidated, every audit log...
-
FHIR gives the client and the server both the option of picking a resource id. POST to a type endpoint asks the server to assign one. PUT to an instance endpoint carries the client's choice. That flexibility is deliberate, and choosing...
-
A UUID is stable by construction — the id itself never changes. What is not stable, and what teams get wrong, is the mapping from a resource in one environment to the same resource in another. Dev, staging, and production each have their...
-
A FHIR integration engine is the layer that turns FHIR from a spec into a working bridge between systems. Every non-trivial healthcare deployment ends up with one, and the choice shapes operational ergonomics for years. The 2026 market has
-
UUID collisions are theoretically possible and effectively impossible with a properly-generated v4 across every FHIR workload short of the entire industry writing to one namespace. The real problem in multi-tenant deployments is not the...
-
UUID v4 is the workhorse — 122 bits of randomness in a fixed layout, cryptographically strong when generated with a proper RNG, no ordering information. UUID v7 is newer — it embeds a millisecond timestamp in the high bits so ids sort by...
-
Bundle.entry.fullUrl is where a Bundle assembles entries that reference each other atomically. The urn:uuid: prefix in that field is what makes cross-entry references work in a transaction Bundle where the resource ids do not exist yet. It...