Health Samurai Blog
RSSOur experts have a deep understanding of FHIR, and here you will find the most relevant articles
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.
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.
We're benchmarking popular open-source FHIR servers and Aidbox across CRUD, batch processing, and search workloads. Here's what we're testing and why.
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.
Benchmarking Aidbox with 8 CPU cores: single instance vs multiple. 2×4 loses only 6% RPS but adds redundancy and better P99.
Learn how we integrated WebMCP into Aidbox UI so AI agents can interact with the interface through declared tools instead of guessing from screenshots.
Formbox Builder is a low-code platform for questionnaires. With MCP, the same Builder session can now be driven from a broader agent environment while keeping the live visual feedback loop.
Get the latest articles on FHIR, interoperability, and healthcare IT.





