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.
Canada Conformance Accelerator
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.
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.
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.
Persistent, tenant-separated run history shows what changed between evaluations. Compare results over time, identify regressions, and give integration teams a shared operational record.
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
| 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 | — | — | — |
| Canada Conformance Accelerator — packs, CI gate + evidence | 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.
Why we exist
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.
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.
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.
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.
The 60-second tour
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.
Straight answers
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.
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.
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.
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.
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.
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.
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
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.