Acc‑01 · Healthcare
Interop
8 wk
Acc‑02 · Fintech
Risk Signal
6 wk
Acc‑03 · Salesforce
Agent
4 wk
Acc‑04 · Industry
Asset
10 wk
Interop Accelerator · Healthcare

From HL7 chaos
to FHIR-ready
in fourteen days.

A pre‑built ingest pipeline that maps any HL7 v2 feed to clean FHIR R4 — schema detection, segment parsing, validation, enrichment, and publish. Tuned on your data in week one, in production by week eight.

Book a pilot scope
Latest: v2.4.1, Mar 2026 License: Per deployment

What you actually
get on day one.

9 modules · git‑cloneable
M.01

→ Ingest pipeline

5-stage transform engine: schema detect → segment parse → FHIR map → validate → publish. Configurable per source.

Python · Pydantic · FastAPI
M.02

→ Schema mapping library

2,400+ pre-built HL7 → FHIR mappings covering ADT, ORM, ORU, MDM, SIU. Custom mappings in DSL.

YAML DSL · 2.4k mappings
M.03

→ FHIR validator

US Core, IPS, and custom profile validation. Sends rejected records to a queue with the failing rule attached.

FHIR Validator · US Core 6.1
M.04

→ Audit log writer

HIPAA-grade audit. FHIR AuditEvent resource, append-only Postgres backing store, 7-year retention.

Append-only · 7yr retention
M.05

→ Drift monitor

Detects schema drift in upstream feeds. Alerts to PagerDuty when rejection rate exceeds threshold.

PagerDuty · Slack · Email
M.06

→ Replay engine

Reprocess any time window with a new mapping. Useful for backfills, schema changes, and corrections.

Kafka · Time-travel
M.07

→ Admin console

Operator UI to inspect feeds, see rejection queue, replay records, and view drift dashboards.

React · Tailwind
M.08

→ Terraform deploy

One-command deploy to AWS, GCP, or Azure. HIPAA-eligible services only. Optional on-prem K8s manifest.

Terraform · K8s · HIPAA-eligible
M.09

→ Runbook + SLA

15 named runbooks for common incidents. 99.97% uptime SLA on Hosted tier. On-call by Emorphis engineers.

Runbook v2.4 · SLA-backed

The pipeline,
flattened out.

5 stages · < 100ms p99

Five stages, two queues, one source of truth.

interop-accelerator v2.4.1
HL7 v2 FEED IN STAGE 1 Schema Detect ~12ms STAGE 2 Parse Segments ~28ms STAGE 3 Map to FHIR R4 ~34ms · core STAGE 4 Validate & Enrich ~19ms STAGE 5 Publish ~11ms ↳ rejection q audit log · every stage
Stage 1
Schema Detect
Identify HL7 version, message type, sending facility.
v2.5 / v2.7 / v2.9
Stage 2
Parse Segments
MSH / PID / OBR / OBX / DG1 / ZRS. Custom Z-segments configurable.
HL7 parser · forgiving mode
Stage 3
Map to FHIR R4
2,400+ canonical mappings. Custom mappings declared in YAML DSL.
US Core 6.1 · IPS
Stage 4
Validate & Enrich
FHIR validator + reference resolver + enrichment from your master data.
FHIR Validator · MDM lookup
Stage 5
Publish
Write to your FHIR server. Bulk Data export. Webhook fanout optional.
FHIR REST · Bulk Data $export

The eight‑week plan.
Pinned, not promised.

8 weeks · 3 engineers
Week ↓ Ship
Week 1
Source audit.
Two engineers on-site (or virtual) with your interop lead. We catalogue every feed, every Z-segment, every quirk. Drop the deploy script on a staging EMR.
Source matrix
Week 2
First ingest live.
Connect the first feed in staging. End-to-end pipeline runs on real records. You get the admin console with a working dashboard.
Staging live
Week 3
Custom mappings.
Z-segments, custom profiles, MDM resolver wired up. We deliver mapping DSL + tests for everything outside the canonical 2,400.
Mapping DSL
Week 4
Validation & rejection.
US Core profile validation. Rejection queue routing. Your team starts handling rejections via the console.
Validation suite
Week 5
Audit + compliance.
FHIR AuditEvent fully wired. HIPAA technical safeguard test plan executed and signed. Compliance review meeting with your security team.
Audit attestation
Week 6
Load & resilience.
Synthetic load run at 2x your peak. Chaos drill. Replay engine validated on a backfill window. p99 latency benchmarked.
Load report
Week 7
Runbook handoff.
15 named runbooks reviewed with your on-call team. Two joint paging drills. Drift monitor thresholds set.
Runbook v2.4
Week 8
Production cutover.
Production deploy. Monitoring on. We stay on-call for 30 days as a safety net. SLA contract starts.
In production

What our last
three customers said.

Verified · 2025—2026
"
We'd spent eighteen months trying to build an HL7-to-FHIR layer in-house. Emorphis had ours in staging by week two, in production by week eight, and we redirected the team to clinical work that actually mattered.
Director of Engineering
US Multi-State Payer · 38M records/mo
Time saved
14months
Throughput at launch
1,840msg/sec
Uptime since cutover
99.97%

Pilot scope
in 72 hours.

↳ Direct line · Interop Accelerator

Tell us about your feeds, your downstream FHIR server, and your timeline. We'll send a pilot scope, architecture sketch, and fixed-fee quote within three business days.

Get in Touch

Questions we
get every week.

Click to expand ↓
Q.01
What if our HL7 feed has weird custom Z-segments?+
Every healthcare org has them. We catalogue yours in week 1, write the mapping in our YAML DSL in week 3, and ship a test suite alongside. You can edit the DSL files directly — no Emorphis lock-in.
Q.02
Do you handle our BAA and SOC 2 paperwork?+
Yes. We have a BAA on file with every Hosted customer. Our SOC 2 Type II report is shared under NDA. For Pilot tier, we sign your BAA but you operate the system.
Q.03
Can it run on-prem instead of cloud?+
Yes. We ship Kubernetes manifests alongside the cloud Terraform. Five of the eleven production deployments are on-prem (regulated payers and one VA system).
Q.04
What does week 8 actually deliver?+
A production system handling your live HL7 feed at p99 < 100ms, with audit logs, a working admin console, 15 runbooks, two joint on-call drills with your team, and a written compliance attestation. Then a 30-day safety-net window where we stay on-call.
Q.05
What happens after the 30-day safety net?+
Hosted customers stay on our SLA indefinitely. Pilot customers take full ownership — though most upgrade to Hosted around the 60-day mark. Enterprise customers have us embedded long-term.
Q.06
Are you actually replaceable?+
We design for it. Code is open to your team from day one. All mappings are declarative YAML. The admin console is white-labellable. Two Pilot customers operate the system entirely on their own staff today.