FHIR, interoperability, and healthcare infrastructure blog

CodeableConcept through the producer/consumer lens: why one field holds multiple codes, what the producer must capture while they still can, and how the consumer should interpret the array — membership, subsumption, projection — without .first() biting them.

Termbox's new support for Atom Feed syndication; what it solves, how it works, and the specific features we've built around it

Instead of duplicating a form for every language, define it once and extend it with translations and terminology bindings — one structured form that renders in many languages.

Termbox is a high-performance FHIR terminology server: SNOMED, LOINC, RxNorm, ICD-10, and conformance to FHIR R4/R5 — try it free.

We're publishing the first in a series of open FHIR benchmarks: a performance benchmark for FHIR terminology servers across 20 test cases and 5 servers.

How FHIR R5 additional bindings solve the limitations of the classic one-binding-per-element model with layered terminology constraints.

What residual categories mean in FHIR terminology, how they affect ValueSet authoring, and pitfalls to avoid when modelling clinical concepts.

Healthcare systems constantly exchange data using different code sets, creating thousands of daily terminology translations. Aidbox TX Engine automates this process with FHIR ConceptMap and $translate, eliminating spreadsheets, custom scripts, and integration errors.

A hybrid FHIR terminology engine that combines local value sets with external servers — pros, cons, ValueSet/$expand examples, Aidbox setup.

We focused on the FHIR IG Registry as it offers a comprehensive dataset. By doing this, we aimed to identify the most pressing issues, challenges, and use cases we were likely to encounter.