Health Samurai Blog

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.

Discover how AI and Aidbox make building FHIR Implementation Guides faster, easier, and accessible to both developers and healthcare experts.

Learn how to create a FHIR Implementation Guide—your organization’s rulebook for turning flexible FHIR standards into actionable, interoperable healthcare data. From profiles and extensions to terminology, search, and packaging, this guide walks you through the essential steps to ensure consist

StructureDefinition is a resource that describes the structure of other resources, including profiles, extensions, and data types.

Simplifier is a FHIR package registry that stores basic and custom FHIR packages.

Constraint - a validation rule that is defined on a profile and described using the FHIRPath syntax.

FHIR slicing constrains array elements in profiles. Learn the syntax, when to use it, and walk through worked examples with FSH snippets.

One key function of profiles is to modify the cardinality of an element. A profile can restrict an element's cardinality within its base structure.

In FHIR, you can define a profile not only for a resource but also for an extension.