Health Samurai Blog

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.

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.

Learn how we integrated WebMCP into Aidbox UI so AI agents can interact with the interface through declared tools instead of guessing from screenshots.

Why you need an independent FHIR server next to your EHR: analytics, sandboxing, granular sharing, and SMART on FHIR — without slowing the EHR.

CMS-0057-F final rule: Patient Access, Provider Access, Payer-to-Payer, and Prior Authorization FHIR APIs required by January 2027.

Role-Based Access Control for FHIR resources using Keycloak and SMART on FHIR v2: scopes, role mapping, token configuration, and Aidbox enforcement.

We recently added experimental support for the MCP Server in Aidbox. Let's explore how to set it up and use it to interact with FHIR resources through an LLM interface.

What the Patient Data Access API is, how it relates to CMS rules, and how to implement it on a FHIR server like Aidbox — with code samples.

The healthcare industry faces complex challenges, many caused by outdated infrastructure and lack of interoperability between systems.