Skip to main content
Xellabs Integration Engine

Integration engine connectors

The Xellabs integration engine connects to many systems that supply data in many formats - not only FHIR and HL7. This site documents each of the 14 connector types you can configure in the console: what it is for, every setting, what Test connection proves, and a worked example.

Product names and logos are trademarks of their respective owners and are shown to indicate compatibility. No endorsement is implied.

Terms used on this page

HL7 - Health Level Seven - the standard family for exchanging healthcare messages · FHIR - Fast Healthcare Interoperability Resources - a modern web API standard for health data

See the Glossary for every term.

Start here​

How it works​

Inbound: data arrives at the engine. Outbound: the engine sends data. Which connectors carry orders today is explained in Stage 1 and Stage 2.
  1. Pick a connector - a transport such as MLLP, SFTP, Kafka or a database.
  2. Choose a direction - Inbound (data arrives at the engine), Outbound (the engine sends data) - where the connector supports both.
  3. Choose a format - HL7 v2, FHIR R4, JSON, XML, CSV, Excel, fixed-width or PDF. See Data formats.
  4. Fill in the settings and press Test connection. Use Fill example to start from a working sample.
  5. Switch it on. Once a connection carries data, the engine starts an Apache Camel route from it. Which connectors do so today is explained in Stage 1 and Stage 2.

Security at a glance​

Secrets stay secretPasswords, tokens and keys are stored encrypted and never sent back to the browser - the console shows only Set / Not set.
Tests are read-onlyTest connection never sends or reads a message: it checks reachability and credentials only.
Partners must prove who they areInbound webhooks require a shared secret on every call; SFTP requires the server's host key.