Evgeny Mukha

How Aidbox moved canonical resolution from runtime to configuration time — with pinning, tree-shaking, and a deterministic candidate selection algorithm.

Aidbox 2602 implements the FHIR R6 $purge operation — permanently delete a patient and their entire compartment, including all history, in one auditable call.

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.

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.

The FHIR US Core Implementation Guide (US Core IG) is a set of standardized profiles and guidelines based on HL7® FHIR® (Fast Healthcare Interoperability Resources) designed for the U.S. healthcare system.

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.

Your storage system must ensure that the SSN identifier is unique across all patient records. This means that if you try to create a new patient with an SSN and another patient with the same SSN already exists, the system will reject the request to prevent duplicate records.

The FHIR R5 specification includes 157 resources, from common ones like Patient to specialized ones. But when your data doesn't fit any existing resource, you may need to create a custom type. This article explores 3 ways to create custom FHIR resources and weighs their pros and cons.

Explore all 4 possible ways to configure IGs in the Aidbox FHIR Platform. Dive into what, how, and why each method can fit your needs.