FHIR, interoperability, and healthcare infrastructure blog

A white paper on Atomic Workspace — an AI platform where clinicians, developers and agents build FHIR-native healthcare apps together inside a digital twin of the production environment.

A baseline note for our performance at scale series: what we measure first, why the starting point matters, and how we keep the benchmark honest.

Computing the Da Vinci PAS operational metrics with SQL on FHIR in Aidbox.

Export SQL-on-FHIR ViewDefinitions into Databricks Unity Catalog managed Delta tables using continuous delivery or one-shot exports.

Aidbox, Formbox, and Payerbox 2605 add consent-aware bulk export, SQL on FHIR operations, search usage stats, a database UI page, and payer-facing workflow updates.

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.

Centralized form authoring with tenant-specific data isolation: how Formbox's system-shared resources let healthcare SaaS platforms reuse Questionnaires across organizations without duplicating forms.

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

FHIR has no $unmerge operation. We built one that reverses a merge using Provenance + History API and lets the client decide what to do with data added between the merge and unmerge.

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.