STANDARD DATA DICTIONARY #2006.539 -- DICOM UID SPECIFIC ACTION FILE 3/24/25 PAGE 1
STORED IN ^MAGDICOM(2006.539, (319 ENTRIES) SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
+---------------------------------------------------------------+
| |
| 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 documents specific actions to be taken to process various kinds of DICOM-defined entities or attributes, such as SOP
Classes, application contexts, etc.
DD ACCESS: @
RD ACCESS: @
WR ACCESS: @
DEL ACCESS: @
LAYGO ACCESS: @
AUDIT ACCESS: @
CROSS
REFERENCED BY: UID(B), TYPE(C), PURPOSE(E)
INDEXED BY: TYPE & SUBTYPE (D)
2006.539,.01 UID 0;1 FREE TEXT (Required)
INPUT TRANSFORM: K:$L(X)>64!($L(X)<1)!'(X'?1P.E) X
LAST EDITED: NOV 02, 2007
HELP-PROMPT: Enter the UID for this entry.
DESCRIPTION: The value of this field is a string that conforms to the format of a DICOM UID (Unique Object
Identifier). A UID is a string that consists of only digits and periods. The first and the last
characters must be digits, and none of the integer numbers in the string (that are separated by
periods) may have leading or trailing zeroes.
The meanings of UIDs are defined in the DICOM standard.
CROSS-REFERENCE: 2006.539^B
1)= S ^MAGDICOM(2006.539,"B",$E(X,1,64),DA)=""
2)= K ^MAGDICOM(2006.539,"B",$E(X,1,64),DA)
2006.539,2 DESCRIPTION 0;2 FREE TEXT (Required)
INPUT TRANSFORM: K:$L(X)>64!($L(X)<1) X
LAST EDITED: NOV 02, 2007
HELP-PROMPT: Enter the description for this UID.
DESCRIPTION: The value of this field is a string. This string is a descriptive text that explains the meaning of
the UID in this record.
2006.539,3 TYPE 0;3 FREE TEXT
INPUT TRANSFORM: K:$L(X)>20!($L(X)<1) X
LAST EDITED: NOV 05, 2007
HELP-PROMPT: Describe the type of entity for which this UID is used.
DESCRIPTION: The value of this field is a string. This string describes the usage of this UID.
The DICOM standard currently identifies the following possible values:
Application Context Name
Coding Scheme
DICOM UIDs as a Coding Scheme
LDAP OID
Meta SOP Class
SOP Class
Service Class
Transfer Syntax
Well-known Print Queue SOP Instance
Well-known Printer SOP Instance
Well-known SOP Instance
Well-known frame of reference
CROSS-REFERENCE: 2006.539^C
1)= S ^MAGDICOM(2006.539,"C",X,DA)=""
2)= K ^MAGDICOM(2006.539,"C",X,DA)
This cross-reference keeps track of which UID belongs to which type of object that has a UID.
RECORD INDEXES: D (#553)
2006.539,4 SUBTYPE 0;4 FREE TEXT
INPUT TRANSFORM: K:$L(X)>10!($L(X)<1) X
LAST EDITED: NOV 05, 2007
HELP-PROMPT: Indicate a sub-type (if any) for this UID.
DESCRIPTION: The value of this field is a string that identifies a sub-type for the UID. Sub-types are not
defined in the DICOM standard but are used to distinguish between application-specific usages of
UIDs.
For instance, an UID that has a "type" of "SOP Class" may have a "sub-type" of "Storage".
RECORD INDEXES: D (#553)
2006.539,5 PURPOSE 1;0 Multiple #2006.5391 (Add New Entry without Asking)
2006.5391,.01 PURPOSE 0;1 FREE TEXT (Multiply asked)
INPUT TRANSFORM: K:$L(X)>64!($L(X)<1) X
LAST EDITED: NOV 05, 2007
HELP-PROMPT: Enter the name of a purpose for which an action may be executed.
DESCRIPTION: The value of this field is a string. This string identifies an action that may be executed by the
application software.
Depending on the UID of the object being manipulated, the application will find in this table
which specific action is to be executed for which specific purpose.
CROSS-REFERENCE: 2006.5391^B
1)= S ^MAGDICOM(2006.539,DA(1),1,"B",X,DA)=""
2)= K ^MAGDICOM(2006.539,DA(1),1,"B",X,DA)
CROSS-REFERENCE: 2006.539^E
1)= S ^MAGDICOM(2006.539,"E",X,DA(1),DA)=""
2)= K ^MAGDICOM(2006.539,"E",X,DA(1),DA)
This cross-reference keeps track of the various purposes for which actions have been defined
across all UIDs.
2006.5391,2 ACTION 0;2 FREE TEXT
INPUT TRANSFORM: K:$L(X)>10!($L(X)<1) X
LAST EDITED: NOV 02, 2007
HELP-PROMPT: Answer must be 1-10 characters in length.
DESCRIPTION: The value of this field is a string. This string identifies the action to be taken by the
application for this purpose for this UID.
Since the value in this field by be used by an application that runs on VistA, as well as by a
client-application that acquires this value through a remote procedure, no assumption can be made
about the mechanism that may be used to invoke the software to perform this action (it may be
MUMPS, Delphi, Java, et cetera).
Hence, the value in this field will be a numeric code. The meaning of this code is specific to
each purpose for which an action may be taken.
2006.5391,3 COMMENT 0;3 FREE TEXT
INPUT TRANSFORM: K:$L(X)>100!($L(X)<1) X
LAST EDITED: NOV 02, 2007
HELP-PROMPT: Enter a comment that describes this action.
DESCRIPTION: The value of this field is a string. The value that will be used by the applications to
determine which action to take is taken from a different field in this record (ACTION).
In order to facilitate debugging and consistency checking, a semi free text is entered in this
field that described the action to take in a human-readable form.
File #2006.539
Record Indexes:
D (#553) RECORD REGULAR IR LOOKUP & SORTING
Short Descr: Track type and subtype
Description: This cross-reference keeps track of which UIDs belong to which types and subtypes.
Set Logic: S ^MAGDICOM(2006.539,"D",X(1),X(2),DA)=""
Kill Logic: K ^MAGDICOM(2006.539,"D",X(1),X(2),DA)
Whole Kill: K ^MAGDICOM(2006.539,"D")
X(1): TYPE (2006.539,3) (Subscr 1) (forwards)
X(2): SUBTYPE (2006.539,4) (Subscr 2) (forwards)
INPUT TEMPLATE(S):
PRINT TEMPLATE(S):
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):