+---------------------------------------------------------------+ | | | 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.
.01uid(+)0;1FREE TEXTBThe 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.
2description(+)0;2FREE TEXTThe value of this field is a string. This string is a descriptive text that explains the meaning of the UID in this record.
3type0;3FREE TEXTCThe 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
4subtype0;4FREE TEXTThe 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".

Not Referenced