Health Samurai Blog

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.

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.

Aidbox 2604 brings HIPAA Safe Harbor de-identification in SQL-on-FHIR, Databricks Lakebase token auth, a reworked SQL Console, and Formbox SMART on FHIR integration.

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.

Aidbox supports HIPAA Safe Harbor de-identification directly in ViewDefinitions. Transform FHIR data into compliant, analytics-ready tables with per-column control — and map results back when needed.

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.

Termbox is a high-performance FHIR terminology server: SNOMED, LOINC, RxNorm, ICD-10, and conformance to FHIR R4/R5 — try it free.

We're publishing the first in a series of open FHIR benchmarks: a performance benchmark for FHIR terminology servers across 20 test cases and 5 servers.