Health Samurai Blog

Generate strongly typed Pydantic models from any FHIR packages with @atomic-ehr/codegen — validation, IDE support, polymorphic bundles, primitive extensions, and fhirpy integration included.

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.

What if working with FHIR didn’t start with APIs and clients, but with files and folders? This article explores FHIR-FUSE, a filesystem interface for FHIR servers, what it makes easier, and where its limits become clear.

Despite shared specs, FHIR validators disagree on edge cases. FHIR Schema fixes this with a JSON Schema-inspired format and simple, universal algorithm. Learn Aidbox insights, snapshot-less validation, and the roadmap.

A modern Python SDK for FHIR built on Type Schema. Strong typing, autocompletion, and a smooth path from FHIR resources to Python data classes.

FHIR has become the primary standard for exchanging healthcare data. To get started with FHIR, developers need to read the FHIR specification and implementation guides (IGs, such as US Core, MCODE, etc.), and then implement them in their programming language. FHIR SDKs simplify this process by offer

FHIR specifies the translation extension to store translations from the base language of a resource to other languages. In this post, we will cover how to search through resources by specifying the language.

The new FHIR Resource Browser in Aidbox makes exploring resources, types, and references fast — with code-aware search and a clean UI.

Resource Preview in Aidbox lets you inspect any FHIR resource at a glance — references, terminology, and field-level context, in one panel.

FHIR specification defines an HTTP interface to complex medical data, including "simple" patient info like the history of their statements, endorsements, observations and so on.