Global: ^MAGDICOM(2006.598

FileMan FileNo	FileMan Filename	Package
2006.598	DICOM ERROR MESSAGE QUEUE	Imaging

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. | | | +---------------------------------------------------------------+ As a DICOM Gateway performs its various tasks, there are occasions where error messages need to be transmitted to remote recipients (FileMan users and/or mailgroups as well as SMTP mail recipients). When such a message needs to be transmitted, a new entry is made into this table, which will contain the message text and some information about the message. Then an attempt is made to transmit the message. When the transmission is successful, the entry is removed from this table. When the transmission is not successful (which is likely since many errors that need to be transmitted have to report some type of "network failure") the text remains in this table while the software on the DICOM Gateway can enter its further error processing. A supervisory task on the DICOM Gateway scans the content of this table on a regular basis and will transmit any "left over" messages. As soon as a message has been transmitted successfully, its entry in this table will be removed.

Package	Total	Routines
Imaging	4	^MAGDICOM(2006.598 ERROR REPORT IMAGES PRINTED MESSAGE TEXT

Fields, Total: 6

Field #	Name	Loc	Type	Details
.01	HEADER	0;1	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:$L(X)>80!($L(X)<3)!'(X'?1P.E) X` LAST EDITED: `JUL 16, 2003` HELP-PROMPT: `Enter a header for the error message.` DESCRIPTION: `The value of this field is a string that is used as the header for the error message.` CROSS-REFERENCE: `2006.598^B` `1)= S ^MAGDICOM(2006.598,"B",$E(X,1,30),DA)=""` `2)= K ^MAGDICOM(2006.598,"B",$E(X,1,30),DA)`
2	ROUTINE	1;1	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>8!($L(X)<1) X` LAST EDITED: `JUL 16, 2003` HELP-PROMPT: `Enter the name of the routine that invoked the error trap.` DESCRIPTION: `The value of this field is a string that identifies a MUMPS routine.`
3	IGNORE	1;2	SET	'0' FOR Create error log; '1' FOR Ignore error log; LAST EDITED: `JUL 16, 2003` HELP-PROMPT: `Indicate whether or not to create an error log.` DESCRIPTION: `The value of this field is a flag that indicates whether or not an error log is to be produced. When the value of this field is false, an error log is created, otherwise the creation of the error log is ignored.`
4	CRITICAL	1;3	SET	'0' FOR Not critical; '1' FOR Critical; LAST EDITED: `JUL 16, 2003` HELP-PROMPT: `Indicate whether or not this is a critical error.` DESCRIPTION: `The value of this field is a flag that indicates whether or not the current error is a "critical" one. When an error is "critical", a e-mail message will be transmitted to the Imaging Team in Silver Spring.`
5	MESSAGE TEXT	2;0	Multiple #2006.5985	2006.5985
6	ERROR REPORT	3;0	Multiple #2006.5986	2006.5986

>>	Not killed explicitly
*	Changed
!	Killed
~	Newed

Name	Field # of Occurrence
>> DA	.01(XREF 1S), .01(XREF 1K)
X	.01+1!, .01(XREF 1S), .01(XREF 1K), 2+1!

Customize PDF page

Package: Imaging

Global: ^MAGDICOM(2006.598

Information

Description

Directly Accessed By Routines, Total: 4

Fields, Total: 6

Global Variables Directly Accessed

Local Variables

Legend: