Connect

Connect is the device-integration hub. It links your laboratory analyzers and imaging modalities to Veona as connected devices, sends orders down to those instruments, and ingests their results back into the right requisition. It speaks the instrument standards directly — ASTM and LIS2-A (lab analyzer protocols), HL7 v2 (Health Level 7 messaging), FHIR (Fast Healthcare Interoperability Resources), and DICOM with MWL (the DICOM Modality Worklist that pushes imaging orders down to modalities).

Note

Every integrated device ships with a true-to-equipment simulator as well as a live reporter. The simulator transmits continuously against the device’s real protocol, so connection and operational status on every screen reflects a genuine live state — never a frozen, seeded value. You can pause or resume all simulators from the Devices screen; live devices are unaffected.

Who uses it

• Integration admins manage devices, standards, mappings, and the message queue.
• Connect is a fulfilment-side hub; prescribers do not hold access to it.

Editions

Available in Hospital, Network, and Public Health editions.

Screens

Screen	What it is for
Connect Console	The integration overview.
Devices	The device registry — register, enable/disable, and test instruments.
Standards	The outward FHIR, HL7 v2, DHIS2, DICOM, and REST endpoints and their health.
Routing	How orders and results route between Veona and devices.
Message Queue	The retry queue — replay or dead-letter messages.
Mappings	Code and identifier mappings between Veona and devices.
Message Logs	The exchanged-message audit trail.
Health	Live device and interface health.
Appliance	The on-site Connect appliance configuration.
Settings	Cloud-link, facility identity, and reliability configuration.
Connect Catalogue	The catalogue of supported devices and vendors.

The device registry

Analyzers and imaging modalities are registered as connected devices. The Devices screen is the instrument-interfacing console (“ASTM / LIS2-A / HL7 v2 / DICOM”).

1. Open Devices and press Add Device. Enter the device’s details and protocol.

2. After registering, run Test Connection on the device. In live mode the appliance attempts the real instrument at the configured address; the result confirms the link before you rely on it.

A device’s directionality is shown on its detail: bidirectional instruments support results-up, orders-down, and host-query; unidirectional instruments report results-up only.

How orders go down and results come back

• Orders down: when a lab or imaging order is raised, Connect routes it to the mapped instrument. Imaging modalities receive their orders through MWL; lab analyzers receive theirs over their ASTM/LIS2-A/HL7 link.
• Results up: the instrument returns results, and Connect ingests them and matches them back to the correct requisition by barcode (the specimen or accession barcode), so values land on the right order automatically.

Retry the message queue

1. Open the Message Queue. Messages are listed by state (Queued, Retrying, Failed, Sent, Acknowledged).

2. On a failed message, choose Retry to re-queue it for delivery (the retry is idempotent — safe even if the message already sent), or Dead-Letter to move it aside for manual review.

Standards

The Standards screen (“Standards & Exchange”) shows the outward FHIR R4, HL7 v2, DHIS2, DICOM, and REST endpoints and their health, with a live toggle per endpoint. Mappings holds the code and identifier translations between Veona and each device.

The Connect console

The Connect Console is the integration hub’s landing page. A status banner shows the appliance, and four readouts summarise the flow — Devices configured, active Channels, Delivered Today, and Queue Pending (which flags any dead-lettered messages). A Device States card gives the live connection rollup across every configured instrument — how many are connected, reconnecting, in error, or disabled — and a Store-And-Forward card shows the message queue’s health: pending, sent, dead-lettered, deduplicated, and failed counts. Messages survive an outage on the appliance and re-sync when the link is back, and each figure links straight to the devices, queue, or logs behind it.

Integration health

Health is the live state of every integration. Readouts count the total integrations, how many are healthy, the combined queue depth, and any open incidents. The integrations table shows each device’s protocol, queue depth, errors today, and a health pill — Healthy, Degraded, Down, or Maintenance — which you can filter by state; a second panel lists active incidents with their severity and status.

Open an integration to see its detail, and use Reconnect to ask a down or degraded link to re-establish. While an integration is down, its queued messages are held and deliver automatically once it reconnects.

Routing tests to equipment

Routing decides which analyzer each test’s orders go down to. It has two views. Device to Assigned Tests lets you pick a device and see every test pinned to it. Test to Device Resolution lists every catalogue test and how it currently resolves — pinned to a specific device (Pinned), matched By Family, or Unrouted.

• Assign pins a test to a specific device; clearing the pin lets it fall back to its routing family.
• Explain opens a resolution waterfall showing exactly why a test resolved the way it did.

A banner warns when tests are unrouted — their orders have no analyzer to push to, so results can only come back by barcode match. Pin a device or set a routing family to close the gap.

The instrument catalogue

The Connect Catalogue lists every instrument Veona can integrate. Search by vendor, model, codec, or protocol and filter by device type, integration maturity (Verified, Variant, File Ingest, or Spec Pending), and licensing. Each row shows the protocol, the transports it supports, and whether it is bidirectional (orders down and results up) or unidirectional (results only).

Open an instrument for its full detail, then Add As Device to register it on this appliance — available only for integrations your organization is licensed for. An unlicensed instrument stays visible in the catalogue for reference but cannot be registered until Veona enables it.

Message logs

Message Logs is the stream of every interface message exchanged with your devices. Readouts count the total messages, how many Need Attention (failed or retrying), and how many were Acknowledged or Sent. Search by device, kind, or content, narrow by a date range, and filter by state (Queued, Retrying, Failed, Sent, or Acknowledged). Open a message with View for its full detail, and Retry a failed or retrying message to re-queue it for delivery (retries are safe to repeat). To act on the queue itself rather than review it, see the message queue.

Code and field mappings

Mappings translates the codes an instrument speaks into the standards Veona uses. Each mapping ties a device’s source code — for a test, result, unit, specimen, sex, or order priority — to a target system such as LOINC, UCUM, the Veona catalogue, or SNOMED CT. Search or filter by domain, and each row shows a status pill: Mapped, Unmapped, or Conflict.

Add Mapping (or Edit on a row) captures the device, the source code and label, and the target system and code. A banner warns when codes are unmapped or in conflict — results for those route to manual review until you resolve them.

Appliance and edge nodes

Appliance shows the on-site Connect appliances (edge nodes) reporting in. Readouts count the nodes, how many are online, the messages queued across them, and any stale links. The edge-nodes table lists each node’s version, device count, queue depth, last sync time, and cloud-link health (Healthy, Degraded, or Offline), and a This Appliance card shows the one you are connected to. Open a node for its detail; an offline node buffers its messages locally and delivers them on reconnect.

This is the same console whether you open it on the appliance over the local network or here in the cloud — the cloud surface reaches each appliance over its configured link.

Connect settings

Settings configures how this appliance talks to the cloud. The Cloud-Edge Link panel holds the facility identity and the connection: the authentication mode — mTLS (a client certificate) or a bearer token — and the cloud address, with the current link status. A Reliability & Audit panel carries two switches: Verify TLS, which rejects the link on a certificate mismatch, and Offline-first, which buffers messages locally through an outage and syncs them on reconnect. Further ingest and fleet options sit below, and Save Changes applies your edits.