Skip to main content

Stage 1 and Stage 2

The connectors were built in two stages. The pages on this site mention Stage 2 wherever something depends on it.

What it means
Stage 1Catalog, configure, test and audit. You can add a connection of any of the 14 types, fill in its settings, press Test connection, see it in the connections grid and see every change in its history.
Stage 2Make a configured connection carry real orders and results at runtime: the engine starts and stops a Camel route from an enabled connection (no restart), and every incoming message goes through the same intake as the portal and the EMR.

Stage 2 is delivered a few connectors at a time. Some of it needs a new Camel component to be installed first, which is approved one by one. That is why some pages say a check "is done once the component is installed (Stage 2)": the engine can reach the system today, but cannot yet sign in or check the topic, queue or key.

How to tell what carries orders​

In the console, each connection in the grid shows Carries orders or Not live under its name. Hover over it to see the reason, the last thing received and the last problem. This is the live answer; the list below is a snapshot.

Snapshot from the project notes (12 November 2026)​

This is a dated snapshot

It is taken from the engine's task notes as of 12 November 2026. Ask the engine team, or check the Carries orders label in the console, for the current position.

Carrying orders inbound at that date

  • Shared folder and Inbound webhook - HL7 v2 or FHIR R4.
  • MLLP - HL7 v2, answered with an HL7 acknowledgement.
  • SFTP - HL7 v2 or FHIR R4, only when the server's host key is set.
  • RabbitMQ - messages that fail are dead-lettered; the queue must already exist.

Not yet at that date

  • Format readers for CSV, Excel, JSON and XML (they need a mapping into the order first). A CSV connection can be configured and tested, but does not carry orders yet.
  • Outbound sending of results and status to a configured connection.
  • Components still waiting for approval or installation: Kafka, email, cloud storage (S3, Azure Blob) and the SQL database drivers other than PostgreSQL.

See also: Testing a connection · Troubleshooting