Onboarding a hospital modality: The pre-flight checklist

  • Onboarding a hospital modality requires exchanging an AE title, TCP port, DNS hostname, and client certificate.
  • You must hand the hospital a called AE title, public hostname, listening port, and server CA certificate.
  • You must collect the hospital's calling AE title, outbound NAT IP, client certificate, and conformance statement.
  • Testing the mutual TLS handshake with OpenSSL before DICOM testing avoids vague, unhelpful protocol errors.
  • A DICOM C-ECHO test verifies AE titles and association negotiation without transmitting any patient data.

Connecting a hospital scanner to your receiver works best when both sides agree on the details before anyone clicks send. You need 4 values ready: an Application Entity (AE) title, a TCP port, a DNS hostname, and a client certificate for mutual TLS. If 1 value is wrong, the modality may only show a vague network error.

A Picture Archiving and Communication System (PACS) administrator handles imaging traffic every day. Give them a clear worksheet, not a request to “open the firewall.” The first hospital can feel slow, but the second and tenth get easier when you reuse the same checklist.

What belongs on a hospital modality DICOM onboarding checklist?

A good onboarding checklist separates network setup from DICOM setup. The network layer opens the TCP connection and completes the TLS handshake. The DICOM layer negotiates the association and sends instances.

Treat the exchange as a 2-sided contract. You provide the destination settings so the hospital can configure its send job. You also collect the sender identity so your receiver knows which device is connecting.

Hospital Side (Modality / PACS)            Your Receiving Side
--------------------------------            -------------------
Source IP (Outbound NAT)          ----->    Firewall / Allowlist
Calling AE Title                  ----->    Receiver Sender Map
Client Certificate (or CSR)       ----->    CA Trust Store
Modality Model & SOP Classes      ----->    Storage Capabilities

Firewall Outbound Rule            <-----    Public DNS Hostname
Modality Destination Port         <-----    Listening TCP Port (e.g. 11112)
Called AE Title                   <-----    Receiver AE Title
Server CA Certificate             <-----    Receiver CA Bundle

Send these values as a static worksheet. Include exact strings, port numbers, and certificate files.

What connection details do you give the hospital?

To receive DICOM studies from a hospital, you hand the PACS team 4 values.

  1. Called AE title: The 16-character identifier of your DICOM receiver. Follow the rules for configuring a DICOM Application Entity title. Keep it short, uppercase, and alphanumeric with no spaces, such as CLOUDRECEIVER.

  2. Public DNS hostname: A fully qualified domain name (FQDN) that resolves to your public gateway. Prefer DNS over a numeric IP address. The hospital must verify DNS resolution from the modality subnet, which may add one test. In return, you can change infrastructure later without reconfiguring scanners.

  3. Listening TCP port: The external port where your service accepts connections. Traditional unencrypted DICOM uses port 104. Standard DICOM over TLS uses port 2762. Custom secure gateways often use port 11112. Ask the hospital to allow outbound traffic to that port.

  4. Server CA certificate: The Certificate Authority (CA) certificate that signed your server certificate. The hospital modality or PACS router must install it before the TLS handshake can trust your server.

For a general model of endpoints and certificates, read the endpoint and certificate overview.

Creating these details for 1 hospital is manageable. Doing it for many hospitals means more worksheets, more certificates, and more values to keep consistent for years. A managed gateway such as Dicomly’s sender connection guide can handle that connection package for you. The flow is simple: 1 API call creates an endpoint and returns the host, port, Called AE title, client certificate, and private key you hand to the sender. The trade-off is less control over the gateway layer and a monthly cost.

What details do you collect from the hospital?

You cannot finish your receiver setup until the PACS administrator gives you their side of the connection.

  1. Calling AE title: The identifier the modality or PACS uses when it starts the transfer, such as CT_SCANNER_01. Your receiver uses this value to identify the sending device.

  2. Outbound NAT IP address: Hospital modalities often sit on private subnets. When they connect to the internet, a firewall translates the address to a public Network Address Translation (NAT) IP. You need that public IP or range for your allowlist.

  3. Client certificate or CSR: With mutual TLS for DICOM connections, both sides verify certificates. You can issue a signed client certificate to the hospital. Some teams send a Certificate Signing Request (CSR) for signing.

  4. Modality manufacturer, model, and SOP classes: Ask for the vendor DICOM Conformance Statement. It lists the Service-Object Pair (SOP) classes and transfer syntaxes the scanner supports. An older magnetic resonance (MR) scanner may only support uncompressed transfer syntaxes. A newer computed tomography (CT) scanner may send compressed JPEG 2000 files.

Do not skip the device model. It tells you whether the modality supports TLS directly. If it does not, the hospital can route traffic through a local DICOM router.

How do you verify mutual TLS before DICOM?

Test the transport before you test a DICOM association. If the TLS handshake fails, DICOM software often cannot report a useful protocol error. The connection just closes.

Ask the hospital network engineer to test the TCP socket and TLS handshake. They can run OpenSSL from an imaging workstation.

openssl s_client -connect dicom.yourdomain.com:11112 \
  -CAfile server-ca.pem \
  -cert client-cert.pem \
  -key client-key.pem \
  -tls1_3

This test proves a short list of facts:

  • The hospital firewall permits outbound traffic to your port.
  • The hospital system trusts your server CA certificate.
  • Your server accepts the hospital client certificate.

If the handshake succeeds, you see the TLS certificate chain and a cipher suite such as TLS_AES_256_GCM_SHA384. If it fails with unknown_ca (alert 48), the client probably did not load your CA certificate correctly. Fix that before DICOM testing.

How do you run the first DICOM C-ECHO test?

After TLS works, test the application layer with a DICOM verification request. DICOM C-ECHO is an application ping. It proves that AE titles match and association negotiation works without transmitting Protected Health Information (PHI).

Ask the PACS administrator to trigger a C-ECHO from the modality console to your Called AE title. The DICOM C-ECHO verification guide explains the protocol exchange if you need to debug the packet flow.

If C-ECHO succeeds, the modality usually shows a green status. If it fails, check your receiver logs at once. The common causes are an AE title mismatch or an unsupported presentation context.

If an association request is rejected, DICOM sends an A-ASSOCIATE-RJ packet. Use the failed DICOM association debugging guide to decode the rejection instead of guessing.

What pre-flight failures should you expect?

Even experienced teams hit the same failures during first onboarding. The good news is that each one has a practical fix.

1. Trailing spaces in AE titles

DICOM standard PS3.5 defines AE titles as 16 bytes, padded with trailing spaces (ASCII 0x20). Legacy PACS software can handle padding differently. If your receiver expects RECEIVER and the modality sends RECEIVER , strict string comparison fails. Trim AE titles in receiver logic before comparing them.

2. Deep packet inspection on non-standard ports

Hospital firewalls sometimes inspect traffic by port. If you run DICOM over TLS on port 443, a proxy may expect HTTP. It can drop the connection when it sees DICOM frames inside the TLS tunnel. Use a dedicated DICOM port such as 2762 or a clearly agreed custom port such as 11112.

3. Missing intermediate CA certificates

When you provide your server CA to the hospital, include the complete certificate chain. Older scanners may reject the connection if an intermediate certificate is missing. Bundle the intermediates before the live test, not during it.

4. Unsupported transfer syntaxes during C-STORE

A C-ECHO test only negotiates the Verification SOP Class. The first real CT or MR study uses C-STORE and negotiates storage SOP classes. If the scanner proposes only compressed transfer syntaxes that your receiver does not accept, the association fails. Check the vendor conformance statement before you schedule the first study.

What should you schedule for the live test?

Hospital change-control can be slower than your engineering work. A firewall change or scanner configuration may need 2 weeks of approval. Plan for that delay.

Book the onboarding window at least 1 week ahead. Send the worksheet early. Test TLS first, run C-ECHO second, and send 1 test study only after both pass.

Create your first worksheet today. Fill in your Called AE title, DNS name, port, server CA file, and the 4 values you need back from the hospital. Then rehearse the first application-layer check with the DICOM C-ECHO verification guide before the hospital call.

Dicomly builds infrastructure for healthcare software teams that receive DICOM studies from hospitals. Why we built Dicomly →

Sources

  1. DICOM Standard Part 8 (PS3.8, Section 9.3.2 — A-ASSOCIATE-RQ Message) (dicom.nema.org)
  2. DICOM Standard Part 15 (PS3.15, Annex B — Secure Transport Connection Profiles) (dicom.nema.org)
  3. RFC 8446 — The Transport Layer Security (TLS) Protocol Version 1.3 (www.rfc-editor.org)
  4. RFC 9325 — Recommendations for Secure Use of TLS and DTLS (BCP 195) (www.rfc-editor.org)

Start receiving DICOM today.

Early access. No credit card. First endpoint free.