Skip to content

Health Samurai

Health Samurai is the vendor of Aidbox — a FHIR Server and Database — and a portfolio of healthcare-interoperability tooling that standardises clinical data into FHIR at point of entry. First wiki disclosure 2026-05-27 in the Databricks Blog co-marketing post on building a FHIR-native health data platform on Lakebase.

Position in the wiki

Health Samurai sits in the healthcare-interoperability ISV slot. Its product portfolio addresses the healthcare data interoperability problem head-on: clinical data exists across HL7v2 / C-CDA / X12 / proprietary formats, encoded with different code systems, with patients duplicated across source systems. The portfolio's job is to canonicalise that data into FHIR + a single golden record per patient at point of entry.

Named capabilities (2026-05-27 disclosure)

  • Open-source HL7v2, C-CDA, X12 converters — legacy formats → FHIR.
  • FHIR-native Terminology Server — normalises codes across LOINC / SNOMED CT / RxNorm / ICD-10.
  • MDM / MPI (Master Patient Index) — deduplicates patient records into a single golden record.
  • FHIR Implementation Guides + Validation — conformance to US Core, CARIN Blue Button, Da Vinci PDex, mCODE; enforced at point of entry, not after the fact.
  • Aidbox FHIR Server and Database — the operational FHIR-native data platform that consumes the standardised + deduplicated + IG-validated data.

All capabilities are described at capability altitude only in the source — no specific subsystem names beyond Aidbox itself, no mechanism depth, no scale numbers.

Substrate strategy

The 2026-05-27 disclosure is the first wiki record of an ISV positioning its operational database directly on Lakebase as a substrate. Aidbox runs natively on Lakebase Postgres. Moonlink handles real-time operational↔analytical synchronisation. The combination delivers the dual-access pattern (FHIR API + Databricks-native Spark / SQL / ML / AI/BI from a single dataset) without customer-managed ETL.

The strategic argument is the open-standards-not-vendor-lock-in posture: data formats and APIs are HL7 + X12; clinical meaning is LOINC / SNOMED CT / RxNorm / ICD-10; conformance is FHIR IGs. Verbatim: "Open standards mean ensuring your data model isn't locked into a singular vendor. The same FHIR resources that power interoperability today can support analytics, AI, and future applications without rework. Switching tools shouldn't require re-modeling your data."

Recent articles

Last updated · 542 distilled / 1,571 read