Files > NETWORK LOCATION

name

NETWORK LOCATION

number

2005.2

location

^MAG(2005.2,

description

+---------------------------------------------------------------+ | | | Property of the US Government. | | No permission to copy or redistribute this software is given. | | Use of unreleased versions of this software requires the user | | to execute a written test agreement with the VistA Imaging | | Development Office of the Department of Veterans Affairs, | | telephone (301) 734-0100. | | | | The Food and Drug Administration classifies this software as | | a medical device. As such, it may not be changed in any way. | | Modifications to this software may result in an adulterated | | medical device under 21CFR820, the use of which is considered | | to be a violation of US Federal Statutes. | | | +---------------------------------------------------------------+ This file will contain an entry for every network storage location, as well as MUSE (EKG) network location(s). This file maps logical device names to physical device names, allowing continued operation even when network storage devices are done. The Imaging site parameters has a number of fields pointing to this file to locate where on the network different files are written. Because the Imaging System operates in a distributed environment, an object may be stored on one or more of the network storage devices. These include multiple magnetic file servers, one or more optical jukeboxes, and possibly additional network devices accessed through a gateway. Each logical location in the Network Location file is mapped to a physical device. Every physical device on the network that will be used for objects must have at least one entry in the Network Location file. The Operational Status field allows rapid software reconfiguration in the event of failure of one of the object storage devices. Each network storage device has a type, such as magnetic or optical. This allows "automatic file migration," where an object resides on a fast magnetic disk until 30 days since its last access, then it is moved to slower, less expensive optical media. Three fields in the Image file (2005) are used to indicate the storage device(s) on which the object resides. For example, an object may originally be captured to MAG1, the first magnetic server. Within seconds, an abstract is created and stored on this same device; the Disk & Vol, Abstract field will be set to MAG1 also. Next, the Image file will be copied to the optical jukebox (if present on the network), creating an immediate backup copy. The Disk & Vol, Optical field will now be set to point to the optical device used for the optical copy. The Network Location file was designed to allow access across a gateway. This type of access has not been required at the test sites. We recommend using names for magnetic devices that begin with the three letters, MAG, followed by sequential numbers. We recommend that images be stored in directories named IMAGE at the first level. Do not store any files in this directory that are not objects handled by File 2005. Logical names for Write Once Read Many (WORM) optical devices should start with the four letters, WORM.

applicationGroups

MAG

Fields

#	Name	Location	Type	Details	Index	Description
.01	network location(+)	0;1	FREE TEXT		B	This is the alias name of an Imaging share.
.04	place(+)	0;10	POINTER	2006.1		This field identifies the SITE PARAMETER file entry. The Site parameter entry defines all of the attributes of Vista Imaging local area network. This includes facility user preferences, network write locations, etc.
1	physical reference	0;2	FREE TEXT		AC	This is the physical network location where the image is stored. This is the Universal Naming Convention (UNC) path for the Image Storage. For example: \\SERVER01\IMAGE1\ This is a required field for all entries except for an entry defined with a RAID-GROUP STORAGE TYPE (#6). Duplicate PHYSICAL REFERENCE values within the same VistA Imaging configuration PLACE (#.04) are not allowed.
2	total space	0;3	NUMERIC			This is the total available formatted space of this network location. The information in this field is dependent on the connectivity of the share and may be set to zero if the share is not available. This field is maintained by the RPC MAGQ FS CHNGE.
3	space used	0;4	NUMERIC			This is the amount of space which has been used for this network location - this value is device dependent.
4	free space	0;5	NUMERIC			This is the amount of available space remaining for this network location. The information in this field is dependent on the connectivity of the share and may be set to zero if the share is not available. This field is maintained by the RPC MAGQ FS CHNGE.
5	operational status(+)	0;6	SET OF CODES	0:Off-Line 1:On-Line		This field tells the Imaging software whether or not this network location, where images are stored, is online. The default is online if the field is null.
5.5	read only	1;6	BOOLEAN	0:NO 1:YES		This field enables applications to filter shares that are designated as read only by active VistA Imaging applications.
6	storage type(+)	0;7	SET OF CODES	MAG:MAGNETIC WORM-DG:WORM-DG WORM-PDT:WORM-PDT RW:READ/WRITE WORM-OTG:WORM-OTG EKG:MUSE-EKG GCC:EXPORT DGM:DIAGRAM URL:URL RTR:ROUTER GRP:RAID-GROUP	E	This field describes the media type of this network location. It should be MAGNETIC for a magnetic disk server. Jukeboxes should be WORM-DG for Data General Jukeboxes under OpenNetware or WORM-PDT for Pegasus Jukeboxes or WORM-OTG for OTG Disk Extender. WORM-DG and WORM-PDT are for backward compatibility only. Note: WORM stands for Write Once, Read Many. The GCC type refers to the Generic Carbon Copy (GCC) utility. URL is used for Web based file access. Type 'RTR' should be used to identify network entries that are used for Routing images. Type 'GRP' will identify a group entry and will allow sites to group network locations. This functionality is useful for the Background Processor and Verifier applications.
7	hash subdirectory	0;8	BOOLEAN	Y:YES		Control whether subdirectory should be hashed.
8	abstract	1;1	BOOLEAN	0:No 1:Yes		This field is a flag indicating whether or not a network location supports ABSTRACT image files'.
9	full	1;2	BOOLEAN	0:No 1:Yes		This field is a flag indicating whether or not a network location supports FULL image files.
10	big	1;3	BOOLEAN	0:No 1:Yes		This field is a flag indicating whether or not a network location supports BIG image files.
11	text	1;4	BOOLEAN	0:No 1:Yes		This field is a flag indicating whether or not a network location supports TEXT image files.
12	dicom	1;5	BOOLEAN	0:No 1:Yes		This field is a flag indicating whether or not a network location supports DICOM image files.
14	compression	1;7	SET OF CODES	NONE:None J2K:JPEG-2000		This field indicates which type of compression, if any, is to use while transmitting files to this network location.
15	user name	2;1	FREE TEXT			This field is for a user name used to establish a connection with the network location.
16	password	2;2	FREE TEXT			This field is a password used with a user name to establish a connection with this network location.
17	maintainconnection	2;3	BOOLEAN	0:NO 1:YES
18	max # retry on connect	3;2	NUMERIC			This field indicates the number of attempts to make to connect with the network location. When no connection can be established within this number of attempts, the status of the network location will be set to 'Off-Line'.
19	max # retry on transmit	3;3	NUMERIC			This field indicates the number of attempts to make to transmit a file. When a file cannot be transmitted within this number of attempts, its status will be set to 'FAILED'.
20	syntax	4;1	SET OF CODES	UNC:UNC		This field is a code for the syntax that describes the actual (physical) name of the network location.
21	subdirectory	4;2	FREE TEXT			Files are typically not stored in root directories. This field is the name of a subdirectory where files are to be stored. The value of this field is concatenated to the name of the network location (the 'physical name') to create the complete path-name for the location where files are to be stored. When "directory hashing" iS active, additional subdirectory names will be added to the above-mentioned path-name before the file name is appended.
22	email	5;0	MULTIPLE	2005.201
23	retention period	3;1	NUMERIC			This field indicates the number of days to retain routed image files at the location identified by this entry in the NETWORK LOCATION file. When Images are present for more than this number of days, they are candidates for automatic removal.
24	last purge date	3;4	DATE-TIME			This field indicates the date and time of the most recent purge at this network location. An automatic purge will be executed at most once per day; the value of this field determines whether or not a purge has already taken place.
25	site	3;5	FREE TEXT			This field is a code for the site of the 'network location. This code is typically a three-letter abbreviation\acronym (WAS for Washington DC, STL for St. Louis, etcetera). For stations 'at home', a longer code that starts with "HOME" is entered.
26	router	0;9	BOOLEAN	0:NO 1:YES		This boolean value is used to designate certain network location shares as routing shares. This is necessary to allow clinical WS applications access to images on these shares but to prevent the background processor from designating this share as the current write location.
27	time offline	3;6	DATE-TIME			This field is a time stamp indicating when the equipment in question most recently went off-line. This time stamp is used by the Routing software to decide whether or not to attempt to reconnect to a destination that was not reachable at an earlier stage.
28	muse site #	6;1	NUMERIC			If this is a MUSE EKG network location, enter the MUSE site number for this location. Typically, a site with a single MUSE server that holds EKGs for one site uses 1. If a MUSE server stores EKGs for more than one site, then Marquette assigns each site a MUSE site number.
29	muse version #	6;2	POINTER	2006.17		Enter the MUSE version number if this network location is a MUSE EKG storage type.
30	share group	7;0	MULTIPLE	2005.22		This subfile identifies the entries that are part of a Shared Group Imaging sites can use this functionality to group their network shares.
31	group member	1;8	POINTER	2005.2		This field identifies the Group name that this network location is part of. Only entries that have a Storage Type of 'GRP' can be selected.