
Configuring Routing Routing User Guide
Defining Imaging Destinations
The following sections explain how to define an Imaging (non-DICOM) destination for
routing. In general terms, defining an Imaging destination breaks down into the
following steps:
1 Establish naming conventions that are agreed on by the sending and receiving sites.
2 Define storage folders for routed images at the receiving site and verify that the
sending site can access those folders.
3 Create routing-specific entries in the NETWORK LOCATION File (#2005.2) at the
sending site.
A destination definition worksheet is located on page
71.
Note: Imaging destinations are defined to support remote reading using VistARad. For
information about defining a DICOM destination, see page
37.
Naming Conventions for Imaging Destinations
Before an Imaging destination is established, the sending and receiving sites should
decide how to identify themselves to routing users.
The values that identify an Imaging destination are stored in the
NETWORK LOCATION
File (#2005.2) at the site where the Routing Gateway is installed. The values defined for
the following should be related in some way.
Field Description Notes
Network
Location
(.01)
The “official”
destination name.
Used by routing rules and the Routing
Gateway at the sending site. Referenced
in VistARad CacheLocationID at
appropriate receiving site.
Cannot match any other name in the
NETWORK LOCATION File or in the DICOM
TRANSMIT DESTINATION
File (#2006.587).
30 max, no spaces or punctuation.
The value used should contain the
nationally assigned 3-character site code
and should indicate that the entry in
question is used for routing.
Physical
Reference (1)
The computer and
share name at the
receiving site.
The name used should be meaningful to
both the sending and receiving sites.
Cannot exceed 63 characters in length
Site (25) Destination as
reported to
VistARad users.
Used in the RC column of VistARad’s
exam lists.
The value used should contain the
nationally assigned 3-character site code.
VistA Imaging V. 3.0, Patch 18 April 2006 26
Kommentare zu diesen Handbüchern