Workflow integration

Encrypt DIMSE associations with DICOM TLS

Search and retrieve over DIMSE without sending patient data in the clear.

Desktop app only, 1.6.0 or newerdcmage pro

Problem

A plain DIMSE association sends everything in the clear: patient names, IDs, the application entity titles, and the images themselves. On a hospital network that is often not allowed, and many archives offer DICOM TLS on a separate port (usually 2762). Some of them also ask the workstation to prove who it is with a client certificate.

Steps

  1. Tick “Encrypt the association (DICOM TLS)” on the DIMSE connection. Enter the archive’s TLS port. The archive’s certificate is checked the way this computer checks any certificate, so a hospital CA that IT already installed on this computer works with no extra step.

  2. Add the CA certificate if this computer does not trust it yet. Choose the PEM file of the certificate authority that issued the archive’s certificate. It is trusted for this connection only and is remembered with the archive.

  3. Add a client certificate if the archive asks for one. Choose the certificate and its private key, both as PEM files. The key goes to the connection and is not saved anywhere, so you choose it again each time you connect. The app remembers only that this archive needed a certificate.

  4. Connect. The connection check runs over TLS. If the archive’s certificate cannot be verified, or the archive wanted a client certificate you did not give it, the connection is refused and the message says why.

Why C-MOVE is not offered

C-MOVE sends the study back on a second connection that the archive opens to your machine. To encrypt that one, this application would need its own server certificate trusted by the archive, which means enrolling each installation with the hospital’s certificate authority. Without it the images would come back unencrypted on a connection you had just been told was encrypted. So an encrypted connection retrieves with C-GET, which brings the study back over the same encrypted association. Ticking TLS switches the retrieval to C-GET.

Limits

  • TLS 1.2 and 1.3 only. The older DICOM secure transport profiles (TLS 1.0, 3DES) are refused.
  • The operating system applies its own rules to server certificates. macOS requires a subject alternative name that matches the host you typed, the server-authentication usage, and a validity of no more than 825 days. A certificate that breaks one of these is refused even when its CA is trusted. Windows also refuses a certificate that does not name the host or is not usable for a server, but under a private CA it accepts a common name that names the host, even beside a subject alternative name for another one, and it sets no 825-day limit. Issue certificates to the stricter macOS rules if both kinds of computer connect.
  • There is no switch to skip verification.

Result

Searches and retrievals travel encrypted, the connection details no longer carry the unencrypted warning, and the remembered archive is marked TLS in Settings → Connections.