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.
{
"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
}
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.
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.
| Adapter | Transport | Direction | Format | What 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. |
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-fhirMaps OBX segments to Observation resources and resolves the patient identifier.
HL7 v2 waveform → FHIR Observation
hl7-obx-fhirNormalizes diagnostic observations for the clinical record.
HL7 v2 results → FHIR DiagnosticReport
hl7-oru-fhirGroups OBX results into a diagnostic report with reference ranges.
HL7 v2 ADT → event JSON
hl7-adt-jsonEmits admit/discharge/transfer events for downstream operations.
MQTT telemetry → FHIR Observation
mqtt-fhirMaps device telemetry to LOINC-coded observations.
MQTT telemetry → canonical JSON
mqtt-jsonNormalizes vendor telemetry into the Ethbus canonical envelope.
Modbus registers → cycle JSON
modbus-jsonDecodes register maps into wash/dry cycle events.
RFID scans → linen lifecycle
rfid-jsonTurns tag reads into clean, dirty and lost linen events.
DICOM study → FHIR ImagingStudy
dicom-fhirPublishes study availability and links to the patient chart.
OPC-UA events → JSON
opcua-jsonMaps access and door events into identity events.
FHIR resource routing
fhir-fhirValidates and forwards FHIR resources with terminology checks.
FHIR → billing JSON
fhir-jsonProjects clinical resources into charge captures.
Canonical JSON → REST
json-restStandard envelope mapping for REST destinations.
POS basket → sales JSON
pos-jsonNormalizes baskets, tenders and returns.
GPS telemetry → fleet JSON
gps-jsonNormalizes position, speed and ignition events.
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.
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.