Platform

An ESB with an architect's brain

Message routing, protocol translation, transformation, orchestration, security and observability — wrapped in an expert system that tells you what to build next.

runtime envelope
{
  "id": "9f2c…",
  "org": "demo-tenant",
  "source": { "kind": "Device", "ref": "PM", "name": "ICU Bed 1" },
  "type": "observation.vitals",
  "protocol": "HL7 v2",
  "priority": "High",
  "correlationId": "c81a…",
  "payload": { "heartRate": 88, "spo2": 97 },
  "route": [ "EMR", "Billing" ],
  "transform": "hl7-vitals-fhir",
  "status": "Delivered",
  "latencyMs": 142
}
Core capabilities

The backbone, fully covered

⇄

Message routing

Content-based routing on message type, source, facility, priority and custom rules. Fan-out to many destinations with per-destination acknowledgement.

⇋

Protocol translation

HL7 v2 MLLP, FHIR R4, DICOM, MQTT 5, OPC-UA, Modbus TCP, RFID/LLRP, ISO 8583, database CDC, SFTP and REST behind one envelope.

✎

Data transformation

Named, versioned transforms map vitals to FHIR Observations, lab OBX to DiagnosticReports, ADT to laundry demand, Modbus registers to cycles and more.

⌁

Service orchestration

Multi-step flows across EMR, LIS, pharmacy, laundry and billing. Delivery state, retries and acknowledgements are tracked per hop.

⚿

Security & access

Hashed API keys per tenant, PBKDF2 passwords, role-aware console, organization isolation and full alert/audit history.

◉

Monitoring & errors

Live metrics, p95 latency, dead-letter inspection, one-click retry, acknowledgement tracking and alert acknowledgement with named owners.

Adapters

Twelve protocol adapters out of the box

Each adapter handles framing, validation, acknowledgements and error mapping. Edge agents extend the same contracts to serial and proprietary hardware.

AdapterTransportDirectionFormatWhat it handles
HL7 v2 (MLLP) TCP 2575 Bidirectional Pipe-delimited ADT, ORU, ORM, RDE with ACK/NACK and retry.
FHIR R4 REST HTTPS Bidirectional JSON / XML Patient, Observation, DiagnosticReport, ServiceRequest.
DICOM (C-STORE/C-FIND) TCP 11112 Bidirectional DICOM Study received, worklist query and report linking.
MQTT 5 TCP/TLS 1883/8883 Inbound JSON / CBOR Device telemetry, cold chain and laundry lifecycle events.
OPC-UA TCP 4840 Inbound Binary Access control, building and industrial equipment events.
Modbus TCP TCP 502 Inbound Registers Washer, dryer and utility telemetry decoded into cycles.
UHF RFID LLRP / HTTP Inbound Tag reads Linen and asset scans with reader-level deduplication.
REST / JSON HTTPS Bidirectional JSON Generic enterprise application integration with OAuth2 or keys.
ISO 8583 TCP Bidirectional Binary Card and ATM authorization with replay protection.
Database CDC JDBC / Debezium Inbound Rows Change data capture for legacy systems without APIs.
GPS / HTTP push HTTPS Inbound JSON Vehicle position, ignition, fuel and geofence state.
SFTP / Batch SFTP Bidirectional CSV / XML Scheduled file exchange with checksum verification.
Transforms

Normalize once, route anywhere

Transforms are named assets that can be reused by any flow — and generated by the Expert System Designer.

HL7 v2 vitals → FHIR Observation

hl7-vitals-fhir

Maps OBX segments to Observation resources and resolves the patient identifier.

HL7 v2 ORU^R01 → FHIR R4 Observation

HL7 v2 waveform → FHIR Observation

hl7-obx-fhir

Normalizes diagnostic observations for the clinical record.

HL7 v2 ORU^R01 → FHIR R4 Observation

HL7 v2 results → FHIR DiagnosticReport

hl7-oru-fhir

Groups OBX results into a diagnostic report with reference ranges.

HL7 v2 ORU^R01 → FHIR R4 DiagnosticReport

HL7 v2 ADT → event JSON

hl7-adt-json

Emits admit/discharge/transfer events for downstream operations.

HL7 v2 ADT^A01 → JSON event

MQTT telemetry → FHIR Observation

mqtt-fhir

Maps device telemetry to LOINC-coded observations.

JSON telemetry → FHIR R4 Observation

MQTT telemetry → canonical JSON

mqtt-json

Normalizes vendor telemetry into the Ethbus canonical envelope.

JSON telemetry → Canonical JSON

Modbus registers → cycle JSON

modbus-json

Decodes register maps into wash/dry cycle events.

Modbus TCP → Canonical JSON

RFID scans → linen lifecycle

rfid-json

Turns tag reads into clean, dirty and lost linen events.

UHF RFID → Canonical JSON

DICOM study → FHIR ImagingStudy

dicom-fhir

Publishes study availability and links to the patient chart.

DICOM → FHIR R4 ImagingStudy

OPC-UA events → JSON

opcua-json

Maps access and door events into identity events.

OPC-UA → Canonical JSON

FHIR resource routing

fhir-fhir

Validates and forwards FHIR resources with terminology checks.

FHIR R4 → FHIR R4

FHIR → billing JSON

fhir-json

Projects clinical resources into charge captures.

FHIR R4 → JSON

Canonical JSON → REST

json-rest

Standard envelope mapping for REST destinations.

Canonical JSON → JSON

POS basket → sales JSON

pos-json

Normalizes baskets, tenders and returns.

POS JSON → Canonical JSON

GPS telemetry → fleet JSON

gps-json

Normalizes position, speed and ignition events.

GPS JSON → Canonical JSON
Edge agents

Hardware integration without touching the core

A small agent runs beside the hardware or on an edge gateway. It owns the device conversation so the bus stays clean and stable.

What the agent does

  • ▸ Speaks RS-232, USB, Bluetooth, Modbus, MQTT, HL7 or vendor SDKs
  • ▸ Tags messages with device identity, facility and clock correction
  • ▸ Filters noise and aggregates high-frequency telemetry
  • ▸ Buffers locally when the network or bus is unavailable
  • ▸ Authenticates with a scoped, revocable API key
  • ▸ Sends a heartbeat so offline devices are visible immediately

Why it wins

Add, replace or upgrade devices without reconfiguring routing. The bus sees a consistent contract per device family; the agent absorbs vendor quirks at the edge.

POST /api/v1/messages X-Api-Key: eth_live_… { "sourceRef": "PM", "messageType": "observation.vitals", "protocol": "HL7 v2", "payload": { "heartRate": 88, "spo2": 97 } }

Every simulator in healthSimulation/ uses this exact contract.

Design your first integration in minutes.

Pick a sector, select systems and devices, and let the expert system produce the plan.

Start free trial