Health Samurai Blog

How to configure and fine-tune a patient matching model in MDMbox — from defining match criteria and model structure to blocking, training, and manual tuning.

How Aidbox handles concurrent requests through its HTTP queue — three load scenarios, common failure modes, and how to tune worker capacity for stable performance.

We analyzed 7 million records in the NPI Registry and found thousands of providers with multiple NPIs. Explore the duplicates yourself with our interactive tool.

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.

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.

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.

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