Skip to main content

Prerequisites

Before connecting a modality to AdvaPACS, ensure your environment meets the following requirements. Preparing your Gateway server, network, and modality configuration before installation will help ensure a smooth deployment.

Gateway Requirements

The AdvaPACS Gateway is installed within your network and securely transfers studies from your modalities to AdvaPACS Cloud. It acts as the bridge between your local DICOM devices and your AdvaPACS tenant.

Supported Operating Systems

The Gateway can be installed on the following platforms:

Operating SystemSupport
LinuxRecommended for production deployments. Provides the best stability and performance.
Windows ServerFully supported for production deployments.
Windows 10 / 11Supported for smaller environments and testing.
DockerSupported where containerised deployments are preferred.

The Gateway has relatively low resource requirements and is suitable for most modern servers.

ResourceRecommendation
CPU2 CPU cores
Memory4 GB RAM minimum (8 GB recommended)
Storage50 GB minimum (200 GB recommended)

Larger environments may require additional CPU, memory, or storage depending on:

  • Study volume
  • Number of connected modalities
  • Concurrent transfers
  • Local retention requirements

Network Requirements

The Gateway server should:

  • Have a fixed IP address (either statically assigned or reserved via DHCP).
  • Have outbound HTTPS access to AdvaPACS.
  • Be reachable by all modalities that will send studies.
  • Allow inbound DICOM connections on the configured listening port.
note

Using a dynamic IP address is not recommended. If the Gateway's IP address changes, modalities will no longer be able to send studies until they are reconfigured.

Modality Requirements

Each modality must support the DICOM standard and be capable of communicating with the AdvaPACS Gateway.

Required DICOM Services

At a minimum, the modality should support:

ServiceRequiredPurpose
C-STORE (SCU)Send images to AdvaPACS
C-ECHO (SCU)Verify connectivity
C-FIND / C-MOVEOptionalQuery and retrieve studies

Network Requirements

Ensure that:

  • The modality can communicate with the Gateway over the local network.
  • The Gateway IP address or hostname is configured correctly.
  • The configured DICOM port is open.
  • Any firewalls allow DICOM traffic between the modality and Gateway.

AE Title

Each modality should have a unique AE Title.

The AE Title configured on the modality must exactly match the Remote AE configured in AdvaPACS. AE Titles are case-sensitive and must match character-for-character.