+---------------------------------------------------------------+ | | | 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. | | | +---------------------------------------------------------------+ The entries in this file each represent a file to be transmitted to a remote location. Entries are placed (automatically) into this file when images are acquired, based on rules that are set up in a separate table. Entries in this file are processed by a "background routing processor" that takes care of the actual transmission of files to remote locations, and also takes care of purging obsolete routed files from those locations. Processed entries can be purged from this file using a menu option on the menu of the "Routing Processor".
.01image(+)0;1POINTER2005The value of this field is a pointer to the image file. This entry in the SEND queue is intended to cause transmission of files for the image that is indicated by this pointer.
1destination(+)0;2VARIABLE-POINTER2005.2, 2006.585, 2006.587The value of this field is a "Variable Pointer". The pointer may reference either an entry in either File 2005.2 (Imaging Network Location) or File 2006.585 (DICOM User Application). When pointing to File 2005.2, images will be transmitted using a host-system copy protocol; when pointing to File 2006.585, images will be transmitted using the DICOM protocol.
This field identifies the kind of file that is to be transmitted. Currently 5 possible types exist (Abstract, Full, Big, Text and DICOM).
The value of this field indicates the status of the queue-entry. Normally, an entry goes through three stages: First, the status is "WAITING". When the queue-processor starts working on the current file, the status will become "SENDING". When the file has been transmitted, the status will change to "SENT". When a transmission fails, the queue processor will make a number of additional attempts to transmit the file. If all attempts remain unsuccessful, the status will be changed to "FAILED". There is a menu option to "re-queue" entries with a status of "FAILED".
4priority1;2NUMERICThis field indicates the relative priority of the entry in the queue. Normally, all entries have priority 500. The software may assign a low priority (250) or a high priority (750). In the future further refinement of these priorities is expected.
5time in(+)1;3DATE-TIMEThe value of this field is a time-stamp that identifies the date and time on which the entry was added to the queue.
6time out1;4DATE-TIMEThe value of this field is a time stamp that identifies when the entry in the queue was processed (status changed to either SENT or FAILED).
7mechanism0;4SET OF CODES1:MS-DOS Copy
2:DICOM Send
The value of this field is a code that indicates how files are to be transmitted to the remote location. Possible methods of transmission are "MS-DOS copy" and "DICOM copy".
8origin(+)0;5POINTER4The value of this field is a pointer (to the Institution file, #4). The institution that is identified by this value is the place where the image "comes from". In the context of auto-routing, the image "comes from" the place where it is permanently stored.
9transaction id0;6FREE TEXTIDThe value of this field is a string that identifies the transaction to which this file belongs. A transaction typically corresponds to a "study", a group of images that are to be manipulated as a unit.

Not Referenced