Skip to main content

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​

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.

  1. Modalities in your facility send images to Link over TCP/IP, through the configured port.
  2. Link sends the received data to the OmegaAI server over a secure HTTPS connection.
  3. 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 isHow it's protected
Between modalities and LinkSent 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 OmegaAISent 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 computerLink 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.

  1. On the Link computer, put the certificate files in a folder, for example C:\OmegaAICertificateFolder.

  2. As an administrator, open Link's appsettings.json file in a text editor.

  3. Set these three values to the locations of your files:

    SettingWhat it points toExample
    CertFileLink's certificate fileC:\\OmegaAICertificateFolder\\pacs.crt
    PKFileLink's private key fileC:\\OmegaAICertificateFolder\\pacs.key
    PeerCertPathThe folder that holds peer certificatesC:\\OmegaAICertificateFolder\\peers

    For example:

    "PeerCertPath": "C:\\OmegaAICertificateFolder\\peers",
    "PKFile": "C:\\OmegaAICertificateFolder\\pacs.key",
    "CertFile": "C:\\OmegaAICertificateFolder\\pacs.crt",
  4. 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.

Troubleshooting​

These guides cover the most common OmegaAI Link and DICOM transfer issues:

For more, see Troubleshooting & FAQs.