Routing User Guide | Configuring Routing |
|
|
Defining DICOM Destinations
In general terms, defining a DICOM destination breaks down into the following steps:
1Determine the names that will be used to identify the destination and gather information about the receiving application.
2Edit the SCU_List.dic file, a dictionary file used by the DICOM Gateway(s).
3Use the DICOM Gateway to load the contents of SCU_List.dic into the MUMPS databases on the DICOM Gateway and on the VistA Host.
The three following sections explain in detail how each general step is performed. A destination definition worksheet is located on page 73.
Note: A DICOM destination must be a DICOM Storage SCP (Service Class Provider). For information about defining Imaging (VistARad) destinations, see page 26.
Naming Conventions for DICOM Destinations
The first step in defining a DICOM destination is determining what to name the destination and how to identify the sender of DICOM images.
When selecting a destination name (entered as the Application in SCU_List.dic), be sure that the name is 31 characters or less in length (case insensitive, punctuation is allowed), and that the name does not match any name defined for an Imaging destination.
The sender of DICOM images (Calling AE in SCU_List.dic) is the ‘Transmit DICOM Images to a DICOM SCP’ function of the DICOM Gateway. The name used to identify this function needs to be agreed on by the sender and receiver of the DICOM transmission.
The remaining information needed to define a DICOM destination is determined by the system that will be receiving the routed images. This information is described in detail on page 39.
DICOM Destination Definitions in SCU_List.dic
This section explains how to update SCU_List.dic specifically for the purposes of routing, and how to load the contents of SCU_List.dic into the DICOM and VistA system databases. The steps below assume that a single instance of SCU_List.dic is used by all DICOM Gateways at a site.
Adding DICOM Destinations to SCU_List.dic
1Stop all active DICOM processes by waiting until they reach an idle state, and then terminating them.
April 2006 | VistA Imaging V. 3.0, Patch 18 | 37 |