Interface Engine 2.0 — Healthcare Data Orchestration
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.
The integration tax
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.
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.
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
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.
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.
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
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.
Capability matrix
| Capability | Interface Engine 2.0 | |||
|---|---|---|---|---|
| HL7 v2 (MLLP) in/out | YES | YES | YES | YES |
| FHIR R4 facade + SMART on FHIR gateway | YES | YES | YES | YES |
| Canadian profiles — CA-Core, CIHI, Ontario | YES | — | — | — |
| Mental-health submissions — OMHRS / MHA PDS rehearsal | YES | — | — | — |
| OntarioMD EMR connectors — Accuro, TELUS, OSCAR Pro, Ocean | YES | — | — | — |
| DICOM MWL SCP + Storage SCP + C-STORE SCU | YES | — | YES* | YES* |
| Universal adapters — raw TCP, ODBC, API polling, Excel | YES | PARTIAL | PARTIAL | PARTIAL |
| Self-contained Docker bundle — installs offline, no JVM sprawl | YES | — | — | — |
| SaaS multi-tenant + outbound-only site agent | YES | — | — | — |
| AI transform assist — BYOK LLM + offline fallback | YES | — | — | — |
| Single-seat clinic edition — running in 10 minutes | YES | — | — | — |
* Varies by site licensing and partner modules. Matrix reflects generally published capabilities; we will happily be corrected.
Three editions. One engine.
The full engine inside your network: EPIC-to-everything domains, DICOM imaging, provincial submissions, Postgres HA. Ships as a self-contained Docker bundle your team installs offline — PHI never leaves the building at install time.
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.
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.
Private distribution
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.
Your organization, name, GitHub username (used for the access grant), and the edition — Hospital or Clinic.
We add your team to the private distribution channel — same day, typically within the hour.
Download, unzip, docker compose up, open the console. Under an hour, offline at install.