Health Samurai Blog

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.

Generate typed profile classes from the US Core IG with @atomic-ehr/codegen. Build compliant Patients and BP observations with typed factories, typed extensions and slices, profile-aware validation, type guards, and typed bundles.

EHDS shifts interoperability to the moment of data capture. How FHIR SDC turns forms into the first layer of structured, reusable, cross-border health data.

FHIR's Patient/$merge assumes the server knows how to merge. Two decades of MPI vendor configs, EHR vendor divergence, and national registry policy show why one algorithm cannot serve every organization.

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

FHIR R5's Patient/$merge is a start, but production MDM needs more. We built a resource-agnostic $merge with client-driven plans, atomic audit trails, and a generic $referencing operation.

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.

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.