Configuring DICOM Push

DICOM Push allows SliceVault to send imaging data directly to a client owned PACS system. This setup requires coordination between SliceVault and the client’s IT/PACS administrator.

In DICOM terminology, both SliceVault and the PACS are considered DICOM nodes. A DICOM node is defined by an AE Title (AET), a network address, and a port.

Prerequisites

Before configuring DICOM Push, ensure the following:

• The client has an operational PACS that supports inbound DICOM C-STORE.
• The PACS administrator is available to provide network and DICOM configuration details.
• The PACS is reachable from SliceVault over the network.

Required PACS Configuration Details

To configure a DICOM Push destination, SliceVault requires the following information:

• RemoteAET
  The AE Title of the client PACS. This identifies the PACS as a DICOM node.

• RemoteURI
  The IP address of the PACS.

• RemotePort
  The TCP port on which the PACS is listening for incoming DICOM associations.

In addition, SliceVault will be configured with:

• OurAET
  The AE Title used by SliceVault when sending data. This can be named according to client requirements and must be allowed on the client PACS.

Network and Firewall Requirements

• The client PACS must expose an open inbound port that SliceVault can connect to.
• No firewall, VPN, or IP filtering may block inbound connections from SliceVault.
• SliceVault does not operate from a single static IP address. Instead, SliceVault uses an IP range. This IP range can be provided to the client for allowlisting purposes.
• The PACS must be configured to accept associations from SliceVault’s AE Title and IP range.

Project Level Limitations

• Only one PACS connection per project is supported.
• DICOM Push is push-only.
• SliceVault does not support DICOM retrieve (C-MOVE or C-GET).
• All data transfer is initiated from SliceVault to the client PACS.

Triggering DICOM Push

DICOM Push can be initiated in two ways:

• Trigger manually from the visit dashboard by selecting Push visit to DICOM server.
• Trigger automatically when a visit transitions to a specific status. Example: when a visit reaches the status Pending Reader, a DICOM Push is automatically initiated.

Troubleshooting Notes

Common causes of failed DICOM Push operations include:

• Incorrect AE Titles (local or remote).
• Closed or filtered PACS ports.
• Firewall rules blocking SliceVault IP ranges.
• PACS configuration not allowing inbound C-STORE from SliceVault.