Health Samurai Blog
RSSOur experts have a deep understanding of FHIR, and here you will find the most relevant articles
How FHIR R5 additional bindings solve the limitations of the classic one-binding-per-element model with layered terminology constraints.
Should FHIR profile constraints apply recursively to nested elements? The spec says yes, but real-world profiles break. We dug into this while building the Aidbox validator.
We design agent tools as if agents were junior developers. They're not. Give them raw protocols and they'll outperform our carefully crafted abstractions.
R6 moves immature resources out of core into incubator IGs. Here is how additional resources work, what changed, and what it means for implementers.
Get the latest articles on FHIR, interoperability, and healthcare IT.




