INTERFACE ENGINE — HL7 · FHIR R4 · DICOM · X12 · NCPDP

Interface Engine 2.0 — Healthcare Data Orchestration

Every system.
Every format.
One engine.

The interface engine that receives anything a hospital or clinic runs — HL7 v2, FHIR R4, DICOM, X12, NCPDP, XML, CSV, even Excel — and delivers it as anything else. Self-hosted inside your network, or hosted for you.

MESSAGE TOPOLOGY / 01 SYNTHETIC DEMO
Interactive healthcare message topology A synthetic message moves from a source system through Interface Engine to a transformed destination. 02 SOURCE / MLLP EPIC ADT DEST / API FHIR R4 IMAGING PACS DOWNSTREAM EMR HUB IE·2 ROUTE / AUDIT RECEIVE TRANSFORM + VALIDATE DELIVER
ADT A01 → FHIR PATIENT TRACE READY
SCROLL ↓ ADT · ORU · DFT · SIU — SYNTHETIC DEMO ONTARIOMD-CERTIFIED EMR CATALOG CA + US STANDARDS PROFILES

The integration tax

Your data isn't the problem. The plumbing is.

01

Every vendor speaks a different dialect

EPIC speaks HL7 with Z-segments. The lab speaks ORU. The province wants FHIR with CA-Core profiles, the payer wants X12, the specialist's office sends a fax-turned-CSV — and the mental-health program reports to OMHRS on its own schedule.

02

Legacy engines charge rent on your own data

Interface engines you can't inspect, priced per interface, deployed by consultants, upgradeable only by the vendor. Twenty years of hospital IT says the same thing: the engine must live inside your network, under your keys.

03

Small clinics get nothing

Community practices on Accuro, TELUS PS Suite, or OSCAR Pro were never the target market for enterprise engines — so nobody gave them one. They get integration by email and spreadsheet, or not at all.

How it works

One pipeline. Any protocol in, any protocol out.

RECEIVEMLLP · HTTP(S) · TCPAPI poller · file PARSEHL7 · FHIR · XMLCSV · XLS · X12 TRANSFORMsandboxed JS · AI assistterminology mapping VALIDATEUS + CA profilesschema · terminology DELIVERHL7 · FHIR · SQL · filePACS · Azure · AWS AUDITimmutable logreplay · DLQ
04

Universal adapters, not vendor lock-in

Raw TCP/IP with any framing, ODBC against any DSN through a bridge sidecar, scheduled API polling, Excel workbooks over base64 — if a system can emit or accept bytes, the engine can interface with it. VPN or site-to-site tunnels need zero engine configuration.

05

Imaging, not just messages

Modality Worklist SCP, a Storage SCP receiving from modalities, and C-STORE SCU pushing imaging objects to PACS — the DICOM surface that separates enterprise engines from message movers.

06

AI that assists, on your terms

Describe a mapping in plain language and get a sandboxed transform script. Bring your own LLM key — including a private Azure OpenAI inside your own cloud tenant — or run on the engine key, metered per tenant. Every generated script is validated; anything unsafe falls back to a deterministic offline synthesizer.

Any to any

HL7 in.
FHIR out.
X12 if they insist.

HL7 V2FHIR R4CDA / CCDDICOMX12NCPDPXMLJSONCSVXLSXSQLREST

Every parser pairs with every builder. An Excel roster from payroll becomes HL7 ADT; an HL7 ORU becomes a LOINC-coded FHIR Observation; a DICOM modality schedule becomes worklist entries. One transform sandbox, no format is second-class.

Canada Conformance Accelerator

Prove readiness.
Before onboarding.

Run repeatable structural-readiness checks against isolated synthetic Canadian healthcare fixtures. Export non-PHI JSON evidence for engineering review and CI/CD gates — without sending patient data to an external service.

EVIDENCE RUN / CA-COMPLETESYNTHETIC SAMPLE
9/9 STRUCTURAL CHECKS
PACK
ca-complete
VERSION
fingerprinted
FIXTURES
isolated / synthetic
EVIDENCE
non-PHI JSON
Message structuresPASS
Profile constraintsPASS
Terminology bindingsPASS
Audit evidencePASS
ILLUSTRATIVE OUTPUT · NO PATIENT DATA · VERSIONED RUN RECORD
CI GATE HTTP 200CERTIFICATION: NOT CONFERRED
01

Versioned, fingerprinted packs

Seven versioned packs make every readiness run reproducible, including a nine-check complete Canadian suite. Pack identity and fingerprints travel with the result, so your team knows exactly what was evaluated.

02

A repeatable CI/CD quality gate

Run a pack from the console or through the HTTP interface. Successful runs return HTTP 200; structural-readiness failures return HTTP 422, making conformance work an enforceable deployment check instead of a spreadsheet exercise.

03

Run history and drift reporting

Persistent, tenant-separated run history shows what changed between evaluations. Compare results over time, identify regressions, and give integration teams a shared operational record.

04

Evidence your team can take with them

Download non-PHI JSON evidence for reviews, handoffs, and release records. The accelerator demonstrates structural readiness; it does not confer official certification or replace external authority onboarding and validation.

Capability matrix

What the incumbents leave out.

CapabilityInterface Engine 2.0IguanaCloverleafRhapsody
HL7 v2 (MLLP) in/outYESYESYESYES
FHIR R4 facade + SMART on FHIR gatewayYESYESYESYES
Canadian profiles — CA-Core, CIHI, OntarioYES———
Canada Conformance Accelerator — packs, CI gate + evidenceYES———
Mental-health submissions — OMHRS / MHA PDS rehearsalYES———
OntarioMD EMR connectors — Accuro, TELUS, OSCAR Pro, OceanYES———
DICOM MWL SCP + Storage SCP + C-STORE SCUYES—YES*YES*
Universal adapters — raw TCP, ODBC, API polling, ExcelYESPARTIALPARTIALPARTIAL
Self-contained Docker bundle — installs offline, no JVM sprawlYES———
SaaS multi-tenant + outbound-only site agentYES———
AI transform assist — BYOK LLM + offline fallbackYES———
Single-seat clinic edition — running in 10 minutesYES———

* Varies by site licensing and partner modules. Matrix reflects generally published capabilities; we will happily be corrected.

Why we exist

Built by the people who
maintained the engines.

Two decades of hospital integration teaches you one thing: interface engines fail on vendor dependence, not technology. This engine was designed backwards from that lesson — it runs inside your network, under your keys, and keeps running whether or not we do.

20+
Years in healthcare integration
0
Phone-home calls. Ever.
CA + US
Standards profiles, in one engine
Source
Available to customers for review

PHIPA-conscious by architecture: PHI stays on your infrastructure, the audit trail is immutable, and the only outbound connections are the ones your team configures. Security review welcome — we'd rather be inspected than trusted.

Three editions. One engine.

Deployed your way.

Hospital

SELF-HOSTED · FLAGSHIP

The full engine inside your network: EPIC-to-everything domains, DICOM imaging, provincial submissions, PostgreSQL state mirroring, and the Canada Conformance Accelerator. Ships as a self-contained Docker bundle your team installs offline — PHI never leaves the building at install time.

  • EPIC / Oracle Health / MEDITECH / Paragon profiles
  • ClinicalConnect, OLIS, DHDR, HRM Ontario feeds
  • Versioned readiness packs + non-PHI evidence export
  • PostgreSQL state mirror + immutable audit trail
REQUEST BUNDLE ↗

Clinic

SELF-HOSTED · VOLUME

One container, one gigabyte, ten minutes. Pre-seeded for OntarioMD-certified EMRs — Accuro, TELUS PS Suite, OSCAR Pro, Ocean — and working against the outbox from minute one. The edition small practices were never offered.

  • EMR hub, OLIS labs, Ocean referrals, OMHRS rehearsal
  • Outbox-not-fail: live before endpoints are configured
  • Upgrades to Hospital in place, same data volume
START A PILOT ↗

Hosted

SAAS · NO-IT CLINICS

We run the engine; your data stays tenant-isolated under your API key. A tiny outbound-only agent at your site reaches internal systems with zero firewall changes. Bring your own LLM key, or use ours — metered, per tenant.

  • Provision a tenant in one action, revoke instantly
  • Outbound-only site agent for in-network DSNs
  • Same engine, same routes — migrate anytime
GET A TENANT ↗

The 60-second tour

Watch it run.

Recorded against a live engine — no mockups. Real routes, real transformations, real audit trail: an EPIC ADT admission becoming a FHIR Patient, a lab result gated on LOINC coding, and every step written to an immutable log.

EPIC ADT → FHIR PATIENT, LIVE ORU → LOINC-GATED OBSERVATION PIPELINE STEPS + REPLAY IMMUTABLE AUDIT TRAIL

Straight answers

What hospital IT asks us.

Does the engine need internet access?

No. It installs and runs fully inside your network, including the first install. The only outbound connections it ever makes are the destinations your team configures — your EHR endpoints, your lab feeds, your own mail server for alerts. There is no license server and no telemetry.

Where does our data go?

Nowhere you don't put it. Messages are stored on your volume, the audit trail is a local append-only log, and imaging lands in your PACS. For Ontario deployments that means PHI never leaves your custodianship — a PHIPA conversation becomes a short one.

What happens if HealthTrust IQ disappears?

The engine keeps running — that's the architectural point. No activation, no renewal check, no kill switch. Customers additionally receive source-code access for continuity review, so your team is never held hostage by our balance sheet.

Does it really cover EPIC, MEDITECH, and the Ontario EMRs?

Yes — with named, maintained adaptor profiles rather than generic promises: EPIC ADT/ORU/SIU inbound, MEDITECH Expanse, and the OntarioMD-certified clinic EMRs (Accuro, TELUS PS Suite, OSCAR Pro, Ocean). Anything with an API, a database, or a file drop can be interfaced through the universal adapters.

Is the Canada Conformance Accelerator an official certification?

No. It produces repeatable structural-readiness results and non-PHI evidence using versioned packs and synthetic fixtures. It does not confer certification, connect to an official validator, or replace onboarding and validation with the relevant external authority. It helps your team find and fix structural issues before those external steps.

How is it licensed?

Annual subscription per deployment (or perpetual with maintenance), priced by edition — Hospital, Clinic, or Hosted. Source is available to customers for security and continuity review. No per-interface pricing: an engine that charges rent per interface is the disease, not the cure.

Can we try it before we buy?

Yes — request the bundle and we'll provision access to the private distribution channel, typically the same day. Most teams have it processing test messages inside an hour; a pilot against a real interface follows whenever you're ready.

Private distribution

Request the bundle.

Distribution is by invitation. Tell us who you are and which edition fits — we provision access to the private channel, your team downloads the self-contained bundle, and the engine is running inside your network the same day. No connection to us required, before or after install.

01 / REQUEST

Email us

Your organization, name, GitHub username (used for the access grant), and the edition — Hospital or Clinic.

02 / INVITED

Access provisioned

We add your team to the private distribution channel — same day, typically within the hour.

03 / INSTALL

Running in your network

Download, unzip, docker compose up, open the console. Under an hour, offline at install.

REQUEST ACCESS — [email protected] ↗