Connectathon Network Infrastructure

The systems listed below will be used for communication and coordination during the Connectation:

  • A Virtual Private Network (VPN) with fixed IP addresses will be used to connect systems under test with the DICOM test archive and the IHE-RO Test Tools.
  • VPN Concentrator hardware has been installed at AAPM headquarters in Alexandria, VA. VPN profiles have been created for participants.
  • A virtual server in the Azure cloud hosts the Brainlab DICOM Proxy Archive for exchange of test data.
  • Zoom teleconferencing will be used for virtual side-by-side testing of remote Actors.
  • Google Meet teleconferencing will be used for daily coordination meetings for the benefit of remotely located participants.
  • A Slack channel (“IHE-RO Connectathon”) has been created for messaging among participants.

VPN Access

Registered vendor personnel should have been assigned a VPN login

Participants should have received email with subject “AAPM VPN profile for IHE-RO Connectathon” (or similar) with an attached connection profile for the OpenVPN client software. This email will also include login credentials and an assigned IP address in the VPN network. Please download the OpenVPN client software ( and install it on the System Under Test (SUT), i.e., the one running the IHE-RO Profile Actor to be tested.

Remote Desktop Viewing of Systems Under Test

For testing of remote Actors, Connectathon judges will distribute a Zoom meeting ID / link. The Zoom meeting will be used by the judges both for interacting with participants via audio and video, as well as for viewing the display of the Systems Under Test (SUT), i.e., Profile Actors. Note: if it is not feasible to run Zoom on your SUT, you will need to establish a remote desktop session to the SUT on a separate PC (using RDP or VNC) and share the remote desktop client application in Zoom. NOTE: Use of multiple monitors for your system under test is recommended.

Testing Connectivity

Before the Connectathon, each participant should take the following steps to ensure the needed connections are in place.

  • Connect the system under test to the VPN using the OpenVPN (or compatible) client software and confirm that the system has the assigned IP address. Test the ability of the SUT to connect (TCP/IP ping) to the Test Server (
  • Verify connection using DICOM Echo with Test Server SCP (IP:, Port: 104, AET: PROXY)
  • Verify DICOM Push from a Storage SCU on your system to the Test Server SCP (IP:, Port 104, AET: PROXY)
  • Verify Query/Retrieve from a SCU on your system from the Test Server (IP:, Port 104, AET: PROXY). Retrieval requires a STORAGE-SCP on your system with an AET of AUTOnnnn, where nnnn equals the port number of your STORAGE SCP.
  • For remote participants: establish a Zoom meeting connection that includes audio (mic and speakers), video (camera) and the ability to share the screen of your SUT.

Archive (PACS) Usage

The Archive will be used for dataset storage and retrieval.

  • Storage SCP (IP:, Port: 104, AET: PROXY)
  • Query/Retrieve SCP (IP:, Port: 104, AET: PROXY). Requires a STORAGE-SCP on your system with an AET of AUTOnnnn, where nnnn equals the port number of your STORAGE SCP.
Log In