A.9 Annexes

A.9.1 IOD Contents

A.9.1.1 Created SOP Instance(s)

This section specifies each IOD created (including Private IODs). It should specify the Attribute Name, tag, VR, and Value. The Value should specify the range and source (e.g., User input, Modality Worklist, automatically generated, etc.). For content items in templates, the range and source of the concept name and concept values should be specified. Whether the value is always present or not shall be specified.

Recommended abbreviations to be used for the tables are:

VNAP Value Not Always Present (attribute sent zero length if no value is present)

ANAP Attribute Not Always Present

ALWAYS Always Present with a value

EMPTY Attribute is sent without a value

Recommended abbreviations to be used for the source of the data values in the tables are:

USER the attribute value source is from User input

AUTO the attribute value is generated automatically

MWL,MPPS, etc. the attribute value is the same as the value received using a DICOM service such as Modality Worklist, Modality Performed Procedure Step, etc.

CONFIG the attribute value source is a configurable parameter

Specification of a company web address can refer to sample SOP Instances that are available.

Private attributes should be specified.

A.9.1.2 Usage of Attributes From Received IODs

Each Application that depends on certain fields to function correctly should specify which ones are required for it to perform its intended function.

A.9.1.3 Attribute Mapping

When attributes are used by different SOP Classes, e.g., Modality Worklist, Storage and Modality Performed Procedure Step, this mapping shall be specified. For devices that specify other external protocols, such as HL7, mapping of their fields into the DICOM attributes is not required but highly recommended.

A.9.1.4 Coerced/Modified Fields

A SCU might coerce certain Attributes, e.g., the Patient Name. A SCP might provide a different value of an Attribute than was received. These changes shall be specified here. An example is Patient Name, which could be modified using available information from either an internal database or obtained from an Information System/Information Manager. Another example is the generation of a new SOP Instance UID for an existing instance. The conditions influencing such coercion should be specified..

A.9.2 Data Dictionary of Private Attributes

Any private Attributes should be specified, including VR and VM, should be specified. Private SOP Classes and Transfer syntaxes should be listed.

A.9.3 Coded Terminology and Templates

Support for Coded Terminology and templates shall be described here.

A.9.3.1 Context Groups

Each Context Group (i.e., use of coded terminology in a specific context) shall be specified here with its default value set, and whether the value set is configurable. The configurable options are specified.

Table A.9.3-1. Context Groups

Context Group

Default Value Set



Logical Context Identification

CID xxx | extended CID xxx | Private CID yyyy | None

No| Extensible|Replaceable

Description of method of selection of a term from the Context Group, and identification of the IOD, Attribute, and/or Content Item that uses the term

e.g., Acquisition Protocol Equipment Settings

e.g., None

e.g., Replaceable

e.g., Value of Scheduled Protocol Code Sequence (0040,0008) from selected Modality Worklist Scheduled Procedure Step is matched to this group for protocol-assisted equipment set-up.

Selected value from this group is used in Modality Performed Procedure Step Performed Protocol Code Sequence (0040,0260)

e.g., Patient Orientation

e.g., CID 19 “Patient Orientation”

e.g., No

e.g., Mapped from user console selection of Patient Orientation. Used in Patient Orientation Code Sequence (0054,0410)





The Default Value Set may be an extension of a standard context group ("extended CID xxx"). If used, a table shall be provided specifying the extended context group, the Context Group Local Version (0008,0107) value and the Context Group Creator UID (0008,010D).

This section describes the specification of any private context groups that are used. It shall follow the format for context groups specified in PS3.16.

A.9.3.2 Template Specifications

This section specifies any extensions to standard templates and/or any private templates that are used, and defines them. Definitions shall follow the format for templates specified in PS3.16

A.9.3.3 Private Code Definitions

This section specifies any private codes used and their definitions.

A.9.4 Grayscale Image Consistency

Any support for the DICOM Grayscale Standard Display Function will be specified in this section.

A.9.5 Standard Extended/Specialized/Private SOP Classes

This section describes Standard Extended SOP Class, Specialized SOP Class, or Private SOP Class that are used.

A.9.5.1 Standard Extended/Specialized/Private SOP <i>

This section describes a particular Standard Extended SOP Class, Specialized SOP Class, or Private SOP Class.

A.9.6 Private Transfer Syntaxes

This section describes any private Transfer Syntaxes that are listed in the Transfer Syntax Tables.

A.9.6.1 Private Transfer Syntax <i>

This section describes particular private transfer syntax. It shall follow the guidelines specified in PS3.5.