Integration is where a hospital facility registers the channels through which it exchanges data with the hospital information system (HIS) and with an external sign-in provider (SSO), and then watches what has gone through them. The screen describes itself in one sentence: "Manage HIS/SSO connectors and the message bus."
How to do it
Add a connector
Click Add connector. The panel asks for three things:
- Connector type — HL7 v2 (HIS), FHIR (HIS), SSO — SAML or SSO — OIDC.
- Name — anything descriptive; it has to be unique within the clinic.
- Configuration (JSON) — the vendor's endpoints and keys.
You confirm with Save connector, and Heltio acknowledges with Connector saved.
Correct by replacing, not by editing
Edit lets you change the name, and the configuration only by overwriting it: you tick Replace config and type the whole thing afresh. The warning next to it is not decoration — "Existing config will be permanently overwritten."
Disable rather than delete
Disable stops messages routing through the connector and can be undone: "Messages will stop routing through this connector. You can re-enable it at any time." The Status column then reads Disabled instead of Active.
Delete is irreversible and takes the links with it: "All messages linked to this connector will be detached. This cannot be undone." To silence a channel for a few days, use disable.
Check the state of the bus
The Health button in the header opens Integration health. Four tiles at the top: Queued, Failed, Last processed (or Never) and Connectors.
Below sits the Messages list with the columns Received, Direction (In / Out), Type, Status, Attempts and Last error. Filter by status narrows the list to Queued, Processed, Failed or Ignored; All brings the full history back.
This screen is read from the top down. 2 are the four numbers telling you whether the bus is working at all — a growing queue with Last processed at nothing means nothing is picking it up. 3 is Filter by status. 4 is the Status column — the place you look for Failed entries before reaching for Retry.
Retry or ignore a message
Heltio retries a failed message by itself — up to six attempts, with a longer pause between each. Once the attempts are exhausted it stays on the list with the status Failed; nothing disappears quietly.
Retry puts it back into the queue at once (Message re-queued). Mark as ignored closes the matter for good: "The message will be permanently marked IGNORED and removed from the retry queue." Use that for messages that have stopped being relevant — not for ones that need fixing.
Prove that the bus is alive
Send test echo puts an internal message onto the bus that needs no external system at all. Heltio confirms with Echo enqueued — watch the message list. If the echo stays Queued and never becomes Processed, message processing is not running in this installation — write to Heltio support before you start looking for the fault in the vendor's configuration.
When something does not work
A connector with this name already exists.
What this means: Connector names have to be unique within a clinic.
Invalid JSON
What this means: The content of the Configuration (JSON) field is not a valid JSON document — most often a missing quotation mark or a comma after the last field.
Failed to save connector
What this means: The save did not reach the server, or encrypting the configuration failed.
Failed to load connectors.
What this means: The list did not answer. The same symptom on the health screen reads **Failed to load health status.**
Retry failed
What this means: The message did not return to the queue — usually because it changed state in the meantime (somebody marked it as ignored, for instance).
No messages with this status. Try 'All' to see the full history.
What this means: The filter is set to a status no message currently holds.
Who has access
Clinic AdminThis whole screen — reading the list and the health state included — is reserved for the clinic owner and administrator. Coordinator is deliberately excluded here, even though in a hospital facility that role manages structure and teams: a technical configuration holding the vendor's keys is a different matter from running a ward.
Adding, changing, enabling, disabling and deleting a connector, and every retry and every ignore of a message, leave an entry in the audit log.
Related
- Roles and permissions — why a Coordinator does not get in here.
- Audit log — where you see who changed a connector.
- P1 — overview — the second, independent route for exchanging medical data.
Related features
Roles and permissions
Thirteen roles: four in an ordinary clinic, eight more in a hospital facility and one on the patient side. What each one sees, what it can change, and why a role cannot be overridden with a single permission.
Audit log
A record of who reached for patient data and when, and who changed it. Filters, export to CSV or JSON, the starting point for a GDPR inspection and for internal explanations.
P1 integration — overview
Who is obliged to report to the Polish e-Health system, how the configuration in Heltio runs, and where you check whether visits are actually reaching Centrum e-Zdrowia.