What Is OmegaAI Link?
OmegaAI Link is a gateway that connects your on-site imaging equipment to OmegaAI. It runs as a Windows service on a dedicated computer at your site. Link sends and receives images from traditional DICOM (Digital Imaging and Communications in Medicine) stations that don't support DICOMweb.
In OmegaAI, Link appears as a device in your organization. The DICOM stations it serves, such as modalities and archives, are set up under that device. See Add and set up a DICOM station.
This article explains how Link moves data between your site and OmegaAI, how that data is protected, and where to find each Link task.
Before You Begin
- Setup: To add a Link device and download the installer, see Add and set up an OmegaAI Link device.
- Setup order: OmegaAI Link is one step in setting up your organization. For the full order, see Set up OmegaAI for your organization.
- Computer: Link needs a dedicated computer that meets the hardware requirements. See Install And Uninstall OmegaAI Link.
How OmegaAI Link Moves Data
Link receives data from your configured modalities over a DICOM TCP/IP (Transmission Control Protocol/Internet Protocol) port. The port is set up when you install Link, and you can change it in OmegaAI.
- Modalities in your facility send images to Link over TCP/IP, through the configured port.
- Link sends the received data to the OmegaAI server over a secure HTTPS connection.
- In the other direction, OmegaAI sends studies through Link to the DICOM stations you've set up.
Note: Modalities and Link communicate over your local network (LAN to LAN). They must be able to reach each other on that network.
How Your Data Is Protected
| Where the data is | How it's protected |
|---|---|
| Between modalities and Link | Sent unencrypted over your local network by default. You can encrypt it with DICOM TLS (Transport Layer Security). See Encrypt DICOM Traffic With TLS. |
| Between Link and OmegaAI | Sent over HTTPS to a secure OmegaAI API, which is authenticated with the OAuth 2.0 standard. Data in transit is encrypted with TLS 1.2 between your site and Azure. |
| Stored on the Link computer | Link is a stand-alone device, so encryption at rest can't be standardized at the disk or operating system level. Images held in Link's local cache are encrypted (see Set Up OmegaAI Link Caching). Your IT team can also encrypt the whole disk, as described in the note below. |
Note: Full disk encryption, such as Windows BitLocker, is managed by your IT team at the operating system, hardware, or infrastructure level, not by OmegaAI Link. It's supported, and it's standard practice for securing computers. The operating system drive must unlock when the computer starts, so that the Link service can start normally.
Encrypt DICOM Traffic With TLS
- Traffic that Link receives: Turn on Enable TLS in the Link device's TLS Configuration section. Link then listens for encrypted DICOM traffic on its TLS Port (default
2762). The regular port keeps working, so modalities that don't use TLS aren't affected. See Add and set up an OmegaAI Link device. - Traffic that Link sends to a station: Select Enable TLS on that DICOM station. See Add and set up a DICOM station.
Important: Before you turn on TLS, set up Link's TLS certificate on the Link computer. Otherwise, Link can't accept encrypted connections. See Set Up The TLS Certificate.
Note: The TLS Port must be different from Link's regular port. If they're the same, OmegaAI shows the message
TLS Port and Non-TLS Port must be different.
Set Up The TLS Certificate
You need Link's certificate file, its private key file, and a folder for peer certificates.
-
On the Link computer, put the certificate files in a folder, for example
C:\OmegaAICertificateFolder. -
As an administrator, open Link's
appsettings.jsonfile in a text editor. -
Set these three values to the locations of your files:
Setting What it points to Example CertFileLink's certificate file C:\\OmegaAICertificateFolder\\pacs.crtPKFileLink's private key file C:\\OmegaAICertificateFolder\\pacs.keyPeerCertPathThe folder that holds peer certificates C:\\OmegaAICertificateFolder\\peersFor example:
"PeerCertPath": "C:\\OmegaAICertificateFolder\\peers",
"PKFile": "C:\\OmegaAICertificateFolder\\pacs.key",
"CertFile": "C:\\OmegaAICertificateFolder\\pacs.crt", -
Save the file.
Expected result: Link can use the certificate when you turn on Enable TLS.
Tip: In
appsettings.json, type each backslash in a path twice (\\), as in the example.
What You Can Do With OmegaAI Link
- Add the Link device in OmegaAI: Add and set up an OmegaAI Link device
- Connect modalities and archives: Add and set up a DICOM station
- Install and remove Link: Install And Uninstall OmegaAI Link
- Learn how Link stays running and up to date: What Is The OmegaAI Link Guardian?
- Load images faster from a local cache: Set Up OmegaAI Link Caching
- Find and pull studies from other DICOM devices: Query And Retrieve Studies From DICOM Devices
- Send studies to a DICOM device: Send Studies To A DICOM Device
- Keep a trusted source's study identifiers: Preserve Study Instance UIDs From Trusted DICOM Sources
- Understand how modalities get their worklist through Link: How the modality worklist works
Troubleshooting
These guides cover the most common OmegaAI Link and DICOM transfer issues:
- OmegaAI Link is offline or studies aren't crossing
- Test Connection to a station fails
- Transfers are slow, or studies arrive with missing images
For more, see Troubleshooting & FAQs.
Related Articles
- Set up OmegaAI for your organization: The order to set up OmegaAI as an administrator.
- Understanding your organization hierarchy: How managing organizations and their devices fit together.
- How Browser Pre-Caching Works: How studies load faster at sites with or without a Link.
- How the modality worklist works: How modalities query the worklist through Link.