Integration Engine for Modern Healthcare Solutions
Interbox
Orchestrate healthcare data with a durable, queue-driven runtime. Interbox turns HL7v2 into FHIR through mappings you own in TypeScript, delivering to Aidbox.
Solutions born from years of integration experience
Our deep experience with HL7v2, C-CDA, and X12 across major EHRs taught us where production pipelines break. Interbox builds those lessons into every feature.
Hash-based diffing deduplicates bundles and picks optimal write strategy per resource. Parallel writes scale throughput — Aidbox load stays minimal, partial updates keep data consistent.
Wire built-in source, parser, and sender stages by config, then own the HL7v2 → FHIR mapping stage in TypeScript. The conversion logic is yours; the runtime is ours.
Map local lab codes, patient classes, and status values to LOINC, SNOMED, and FHIR ValueSets without leaving the workflow.
Every message carries a live status — received, processed, sent, or flagged error or deferred. Inspect any message at each stage, filter by source and status, and watch throughput from the operations dashboard.
Your Git repo plugs directly into the engine for a fast edit-and-reload loop. Use our TypeScript SDK and built-in AI assistance to build mappings and pipelines — you focus on the logic, we handle the runtime.
Every error, message, and result stays in the queue until you resolve it. Retry or fix on your schedule — not under pressure.
The runtime that runs your mappings
Three stages chain through PostgreSQL-backed tables. The source and sender are built-ins; the mapper in the middle is the converter you wrote in your repo. A failed message never moves to a separate log — its row flips to error or deferred carrying the cause, ready to retry.
Any FHIR server that accepts transaction Bundles works — tuned for maximum throughput against Aidbox.
error — flagged for investigation, with the cause attached. The message waits right where it is — nothing is lost.deferred — you've looked, and you're parking it to revisit once you know more about the cause or how to resolve it.Work the queue on your schedule: fix the source or the mapping and retry, or defer until you have what you need.
High-load built-in ingestion worker
Built to solve three production-grade problems that decide whether your integration scales.
Multi-threaded ingestion — workers drain Postgres queues in parallel, stress-tested against million-row datasets.
Single-threaded ingestion that buckles under realistic message volume.
Hash-based checks decide PUT vs PATCH vs skip — partial updates never clobber fields with nulls.
Blind PUT requests overwrite existing fields with nulls and lose data on every retry.
Delivery step hashes each resource and skips writes when content is unchanged. Common reuse cases (Organizations, Practitioners, Coverages) never hit the wire — the FHIR server handles only real changes.
Every message rewrites Organizations, Practitioners, and Coverages even when nothing changed. Write volume scales with traffic, not with actual change.
A console for the people running it
Day-to-day work doesn't need a terminal. Switch screens to see traffic, failures, mappings, and the running repo.
Interbox
ops
Interbox / Dashboard
live · 3 workers
TV
| unmapped_code | 127 |
| validation_error | 48 |
| mapping_error | 31 |
| prerequisite_missing | 19 |
| aidbox_5xx | 6 |
Your repo is the deployment unit
A Git repo with src/pipelines/ and src/mappers/ plugs into the runtime. Push to main, pull it in, and the engine reloads — no image rebuilds for mapping changes.
your-org/hl7-pipeline ├── src/ │ ├── index.ts # imports pipelines + mappers │ ├── pipelines/ │ │ └── hl7-to-aidbox.ts # .source().mapper().sender() │ └── mappers/v2-to-fhir/ │ ├── segments/pid-patient.ts │ ├── segments/pv1-encounter.ts │ └── segments/obx-observation.ts ├── test/ └── package.json # "@healthsamurai/interbox"
Push to main, pull it in from the dashboard, and the engine reloads the workspace. No image rebuilds, no rollout choreography for mapping changes.
Mappers and pipeline topology live in TypeScript next to your unit tests. PRs, blame, rollbacks — the same workflow as the rest of your stack.
Repo ships with agent skills and HL7v2 spec tooling — any agent with ACP support — embedded right in the operations console — generates segment converters and tests against your structure, with the spec one tool-call away.
Simple, predictable licensing
Build for free in development. Go to production standalone, or at a lower rate alongside an Aidbox license.
The full engine and SDK for building and testing — no PHI.
- All built-in stages and your own mappers
- Operations UI, AI assistant, hot-reload
- Synthetic / non-PHI data only
The same Interbox at a lower price when you buy it together with an Aidbox license.
- Everything in Standalone
Run Interbox in production against any FHIR server.
- Everything in Developer
- Production use with PHI
- Any FHIR transaction-bundle server
Our engineers work alongside yours — converters for your message types, EHR wiring, operations handoff. You ship faster; your team owns it after.
- Address
- Health Samurai Inc. 1891 N Gaffey St Ste O, San Pedro, CA 90731
- Telephone
- +1 (818) 731-1279
