Health Samurai Blog
RSSOur experts have a deep understanding of FHIR, and here you will find the most relevant articles
CMS-4208-F2 requires MA organizations to publish provider directory data for Medicare Plan Finder. HPMS attestation is due September 1, 2026 — before CMS-0057-F.
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.
Termbox is a high-performance FHIR terminology server: SNOMED, LOINC, RxNorm, ICD-10, and conformance to FHIR R4/R5 — try it free.
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'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.
How duplicate patient records silently corrupt healthcare analytics — inflating population metrics, fragmenting clinical histories, skewing cohort construction, and biasing ML models — and why identity resolution upstream is the structural fix.
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.
Aidbox 2603 brings BigQuery streaming, Databricks Lakebase support, FHIR package dependency overrides, and Formbox improvements.
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.
Get the latest articles on FHIR, interoperability, and healthcare IT.





