<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="ma2html.xsl"
?>
<!-- to produce output use:
$ xsltproc ma2html.xsl ModuleAttributes.xml
    -->
<!--
  Program: GDCM (Grassroots DICOM). A DICOM library

  Copyright (c) 2006-2011 Mathieu Malaterre
  All rights reserved.
  See Copyright.txt or http://gdcm.sourceforge.net/Copyright.html for details.

     This software is distributed WITHOUT ANY WARRANTY; without even
     the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
     PURPOSE.  See the above copyright notice for more information.
-->
<tables edition="2008">
  <!--macro table="5.4-1" name="Example Module Table">
    <entry group="aaaa" element="aaaa" name="Attribute A" type="1">
      <description>This is an example.</description>
    </entry>
    <entry group="bbbb" element="bbbb" name="Attribute B Sequence" type="1">
      <description>This is an example of a Sequence Attribute</description>
    </entry>
    <include ref="&gt;Include 'Example Macro' Table 5.4-2" description="In this Module, Attribute D (dddd,dddd) is Type 1"/>
  </macro>
  <macro table="5.4-2" name="Example Macro">
    <entry group="cccc" element="cccc" name="Attribute C" type="1">
      <description>This is an example.</description>
    </entry>
    <entry group="dddd" element="dddd" name="Attribute D" type="3">
      <description>This Attribute is generally a Type 3.</description>
    </entry>
  </macro>
  <macro table="5.4-3" name="Example Module Table Without The Use of an Attribute Macro">
    <entry group="aaaa" element="aaaa" name="Attribute A" type="1">
      <description>This is an example.</description>
    </entry>
    <entry group="bbbb" element="bbbb" name="Attribute B Sequence" type="1">
      <description>This is an example of a Sequence Attribute.</description>
    </entry>
    <entry group="cccc" element="cccc" name="&gt;Attribute C" type="1">
      <description>This is an example.</description>
    </entry>
    <entry group="dddd" element="dddd" name="&gt;Attribute D" type="1">
      <description>In this Module, this Attribute has been specialized to Type 1 as indicated in Table 5.4-1.</description>
    </entry>
  </macro-->
  <macro table="8.8-1" name="Common Attribute Set For Code Sequence Attributes (invoked AS “code Sequence Macro”)">
    <entry group="0008" element="0100" name="Code Value" type="1">
      <description>See Section 8.1.</description>
    </entry>
    <entry group="0008" element="0102" name="Coding Scheme Designator" type="1">
      <description>See Section 8.2.</description>
    </entry>
    <entry group="0008" element="0103" name="Coding Scheme Version" type="1C">
      <description>See Section 8.2. Required if the value of Coding Scheme Designator (0008,0102) is not sufficient to identify the Code Value (0008,0100) unambiguously.</description>
    </entry>
    <entry group="0008" element="0104" name="Code Meaning" type="1">
      <description>See Section 8.3.</description>
    </entry>
    <entry group="0008" element="010F" name="Context Identifier" type="3">
      <description>See Section 8.6.</description>
    </entry>
    <entry group="0008" element="0105" name="Mapping Resource" type="1C">
      <description>See Section 8.4. Required if Context Identifier (0008,010F) is present.</description>
    </entry>
    <entry group="0008" element="0106" name="Context Group Version" type="1C">
      <description>See Section 8.5. Required if Context Identifier (0008,010F) is present.</description>
    </entry>
    <entry group="0008" element="010B" name="Context Group Extension Flag" type="3">
      <description>Indicates whether the Code Value/Coding Scheme/Code Meaning is selected from a private extension of the Context Group identified in Context Identifier (0008,010F). See Section 8.7 of this Part.
Enumerated Values: "Y", "N"
</description>
    </entry>
    <entry group="0008" element="0107" name="Context Group Local Version" type="1C">
      <description>See Section 8.7. Required if the value of Context Group Extension Flag (0008,010B) is "Y".
.</description>
    </entry>
    <entry group="0008" element="010D" name="Context Group Extension Creator UID" type="1C">
      <description>Identifies the person or organization who created an extension to the Context Group. See Section 8.7.
Required if the value of Context Group Extension Flag (0008,010B) is "Y".</description>
    </entry>
  </macro>
  <macro table="10-1" name="Person Identification Macro Attributes Description">
    <entry group="0040" element="1101" name="Person Identification Code Sequence" type="1">
      <description>A coded entry which identifies a person.
The Code Meaning attribute, though it will be encoded with a VR of LO, may be encoded according to the rules of the PN VR (e.g. caret ‘^' delimiters shall separate name components), except that a single component (i.e. the whole name unseparated by caret delimiters) is not permitted. Name component groups for use with multi-byte character sets are permitted, as long as they fit within the 64 characters (the length of the LO VR).
One or more Items may be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="1102" name="Person's Address" type="3">
      <description>Person's mailing address</description>
    </entry>
    <entry group="0040" element="1103" name="Person's Telephone Numbers" type="3">
      <description>Person's telephone number(s)</description>
    </entry>
    <entry group="0008" element="0080" name="Institution Name" type="1C">
      <description>Institution or organization to which the identified individual is responsible or accountable. Required if Institution Code Sequence (0008,0082) is not present.</description>
    </entry>
    <entry group="0008" element="0081" name="Institution Address" type="3">
      <description>Mailing address of the institution or organization to which the identified individual is responsible or accountable.</description>
    </entry>
    <entry group="0008" element="0082" name="Institution Code Sequence" type="1C">
      <description>Institution or organization to which the identified individual is responsible or accountable. Required if Institution Name (0008,0080) is not present.
Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
  </macro>
  <macro table="10-2" name="Content Item Macro Attributes Description">
    <entry group="0040" element="A040" name="Value Type" type="1">
      <description>The type of the value encoded in this name-value Item.
Defined Terms:
DATETIME
DATE
TIME
PNAME
UIDREF
TEXT
CODE
NUMERIC</description>
    </entry>
    <entry group="0040" element="A043" name="Concept Name Code Sequence" type="1">
      <description>Coded concept name of this name-value Item. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="A120" name="DateTime" type="1C">
      <description>DateTime value for this name-value Item.
Required if Value Type (0040,A040) is DATETIME.</description>
    </entry>
    <entry group="0040" element="A121" name="Date" type="1C">
      <description>Date value for this name-value Item.
Required if Value Type (0040,A040) is DATE.</description>
    </entry>
    <entry group="0040" element="A122" name="Time" type="1C">
      <description>Time value for this name-value Item.
Required if Value Type (0040,A040) is TIME.</description>
    </entry>
    <entry group="0040" element="A123" name="Person Name" type="1C">
      <description>Person name value for this name-value Item.
Required if Value Type (0040,A040) is PNAME.</description>
    </entry>
    <entry group="0040" element="A124" name="UID" type="1C">
      <description>UID value for this name-value Item.
Required if Value Type (0040,A040) is UIDREF.</description>
    </entry>
    <entry group="0040" element="A160" name="Text Value" type="1C">
      <description>Text value for this name-value Item.
Required if Value Type (0040,A040) is TEXT.</description>
    </entry>
    <entry group="0040" element="A168" name="Concept Code Sequence" type="1C">
      <description>Coded concept value of this name-value Item. Only a single Item shall be permitted in this Sequence.
Required if Value Type (0040,A040) is CODE.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="A30A" name="Numeric Value" type="1C">
      <description>Numeric value for this name-value Item.
Required if Value Type (0040,A040) is NUMERIC.</description>
    </entry>
    <entry group="0040" element="08EA" name="Measurement Units Code Sequence" type="1C">
      <description>Units of measurement for a numeric value in this name-value Item. Only a single Item shall be permitted in this Sequence.
Required if Value Type (0040,A040) is NUMERIC.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID 82"/>
  </macro>
  <macro table="10-3" name="Image SOP Instance Reference Macro Attributes">
    <include ref="Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0008" element="1160" name="Referenced Frame Number" type="1C">
      <description>Identifies the frame numbers within the Referenced SOP Instance to which the reference applies. The first frame shall be denoted as frame number 1.
Note: This Attribute may be multi-valued.
Required if the Referenced SOP Instance is a multi-frame image and the reference does not apply to all frames, and Referenced Segment Number (0062,000B) is not present.</description>
    </entry>
    <entry group="0062" element="000B" name="Referenced Segment Number" type="1C">
      <description>Identifies the Segment Number to which the reference applies. Required if the Referenced SOP Instance is a Segmentation and the reference does not apply to all segments and Referenced Frame Number (0008,1160) is not present.</description>
    </entry>
  </macro>
  <macro table="10-4" name="Series and Instance Reference Macro Attributes">
    <entry group="0008" element="1115" name="Referenced Series Sequence" type="1">
      <description>Sequence of Items each of which includes the Attributes of one Series. One or more Items shall be present.</description>
    </entry>
    <entry group="0020" element="000E" name="&gt;Series Instance UID" type="1">
      <description>Unique identifier of the Series containing the referenced Instances.</description>
    </entry>
    <entry group="0008" element="114A" name="&gt;Referenced Instance Sequence" type="1">
      <description>Sequence of Items each providing a reference to an Instance that is part of the Series defined by Series Instance UID (0020,000E) in the enclosing Item. One or more Items shall be present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </macro>
  <macro table="10-5" name="General Anatomy Mandatory Macro Attributes">
    <entry group="0008" element="2218" name="Anatomic Region Sequence" type="1">
      <description>Sequence that identifies the anatomic region of interest in this Instance (i.e. external anatomy, surface anatomy, or general region of the body).
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Context ID may be defined in the macro invocation."/>
    <entry group="0008" element="2220" name="&gt;Anatomic Region Modifier Sequence" type="3">
      <description>Sequence of Items that modifies the anatomic region of interest of this Instance
One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 2, unless otherwise defined in the macro invocation."/>
    <include ref="Include 'Primary Anatomic Structure Macro' Table 10-8" description="Context ID may be defined in the macro invocation."/>
  </macro>
  <macro table="10-6" name="General Anatomy Required Macro Attributes">
    <entry group="0008" element="2218" name="Anatomic Region Sequence" type="2">
      <description>Sequence that identifies the anatomic region of interest in this Instance (i.e. external anatomy, surface anatomy, or general region of the body).
Zero or one Item may be present in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Context ID may be defined in the macro invocation."/>
    <entry group="0008" element="2220" name="&gt;Anatomic Region Modifier Sequence" type="3">
      <description>Sequence of Items that modifies the anatomic region of interest of this Instance
One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 2, unless otherwise defined in the macro invocation."/>
    <include ref="Include 'Primary Anatomic Structure Macro' Table 10-8" description="Context ID may be defined in the macro invocation."/>
  </macro>
  <macro table="10-7" name="General Anatomy Optional Macro Attributes">
    <entry group="0008" element="2218" name="Anatomic Region Sequence" type="3">
      <description>Sequence that identifies the anatomic region of interest in this Instance (i.e. external anatomy, surface anatomy, or general region of the body).
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Context ID may be defined in the macro invocation."/>
    <entry group="0008" element="2220" name="&gt;Anatomic Region Modifier Sequence" type="3">
      <description>Sequence of Items that modifies the anatomic region of interest of this Instance
One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 2, unless otherwise defined in the macro invocation."/>
    <include ref="Include 'Primary Anatomic Structure Macro' Table 10-8" description="Context ID may be defined in the macro invocation."/>
  </macro>
  <macro table="10-8" name="Primary Anatomic Structure Macro Attributes">
    <entry group="0008" element="2228" name="Primary Anatomic Structure Sequence" type="3">
      <description>Sequence of Items that identifies the primary anatomic structure(s) of interest in this Instance.
One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Context ID may be defined in the macro invocation."/>
    <entry group="0008" element="2230" name="&gt;Primary Anatomic Structure Modifier Sequence" type="3">
      <description>Sequence of Items that modifies the primary anatomic structure of interest in this Instance.
One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 2."/>
  </macro>
  <macro table="10-9" name="Request Attributes Macro Attributes">
    <entry group="0040" element="1001" name="Requested Procedure ID" type="1C">
      <description>Identifier that identifies the Requested Procedure in the Imaging Service Request.
Required if procedure was scheduled. May be present otherwise.
Note: The condition is to allow the contents of this macro to be present (e.g., to convey the reason for the procedure, such as whether a mammogram is for screening or diagnostic purposes) even when the procedure was not formally scheduled and a value for this identifier is unknown, rather than making up a dummy value.</description>
    </entry>
    <entry group="0008" element="0050" name="Accession Number" type="3">
      <description>An identifier of the Imaging Service Request for this Requested Procedure.</description>
    </entry>
    <entry group="0020" element="000D" name="Study Instance UID" type="3">
      <description>The unique identifier for the Study provided for this Requested Procedure.</description>
    </entry>
    <entry group="0008" element="1110" name="Referenced Study Sequence" type="3">
      <description>Uniquely identifies the Study SOP Instances associated with this SOP Instance. One or more items may be included.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0032" element="1060" name="Requested Procedure Description" type="3">
      <description>Institution-generated administrative description or classification of Requested Procedure.</description>
    </entry>
    <entry group="0032" element="1064" name="Requested Procedure Code Sequence" type="3">
      <description>A sequence that conveys the Procedure Type of the requested procedure. The Requested Procedure Code Sequence shall contain only a single item.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="1002" name="Reason for the Requested Procedure" type="3">
      <description>Reason for requesting this procedure.</description>
    </entry>
    <entry group="0040" element="100A" name="Reason for Requested Procedure Code Sequence" type="3">
      <description>Coded Reason for requesting this procedure.
One or more sequence items may be present.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Context ID may be defined in the macro invocation."/>
    <entry group="0040" element="0009" name="Scheduled Procedure Step ID" type="1C">
      <description>Identifier that identifies the Scheduled Procedure Step.
Required if procedure was scheduled.
Note: The condition is to allow the contents of this macro to be present (e.g., to convey the reason for the procedure, such as whether a mammogram is for screening or diagnostic purposes) even when the procedure step was not formally scheduled and a value for this identifier is unknown, rather than making up a dummy value.</description>
    </entry>
    <entry group="0040" element="0007" name="Scheduled Procedure Step Description" type="3">
      <description>Institution-generated description or classification of the Scheduled Procedure Step to be performed.</description>
    </entry>
    <entry group="0040" element="0008" name="Scheduled Protocol Code Sequence" type="3">
      <description>Sequence describing the Scheduled Protocol following a specific coding scheme. This sequence contains one or more Items.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Context ID may be defined in the macro invocation."/>
    <entry group="0040" element="0440" name="&gt;Protocol Context Sequence" type="3">
      <description>Sequence that specifies the context for the Scheduled Protocol Code Sequence Item. One or more items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Content Item Macro' Table 10-2" description="Context ID may be defined in the macro invocation."/>
    <entry group="0040" element="0441" name="&gt;&gt; Content Item Modifier Sequence" type="3">
      <description>Sequence that specifies modifiers for a Protocol Context Content Item. One or more items may be included in this sequence. See Section C.4.10.1.</description>
      <section ref="C.4.10.1" name="">The Protocol Context Sequence (0040,0440) allows the specification of parameters that further qualify the scheduled protocol, provided through a set of generic name/value pairs of context Content Items.
Note:  This allows the specification of clinical, acquisition, or procedural qualifiers for the scheduled protocol, such as a specific body part, imaging technique, or parameters of a preparatory event (e.g., radionuclide injection). Specific uses of this Sequence may be documented in a Template defined in accordance with PS3.16.

</section>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Content Item Macro' Table 10-2" description="Context ID may be defined in the macro invocation."/>
  </macro>
  <macro table="10-10" name="Basic Pixel Spacing Calibration Macro Attributes">
    <entry group="0028" element="0030" name="Pixel Spacing" type="1C">
      <description>Physical distance in the patient between the center of each pixel, specified by a numeric pair - adjacent row spacing (delimiter) adjacent column spacing in mm. See 10.7.1.1 and 10.7.1.3. Required if the image has been calibrated. May be present otherwise.</description>
    </entry>
    <entry group="0028" element="0A02" name="Pixel Spacing Calibration Type" type="3">
      <description>The type of correction for the effect of geometric magnification or calibration against an object of known size, if any. See 10.7.1.2.</description>
    </entry>
    <entry group="0028" element="0A04" name="Pixel Spacing Calibration Description" type="1C">
      <description>A free text description of the type of correction or calibration performed.
Notes: 1. In the case of correction, the text might include description of the assumptions made about the body part and geometry and depth within the patient.
2. in the case of calibration, the text might include a description of the fiducial and where it is located (e.g., "XYZ device applied to the skin over the greater trochanter").
3. Though it is not required, the Device Module may be used to describe the specific characteristics and size of the calibration device.
Required if Pixel Spacing Calibration Type (0028,0A02) is present.</description>
    </entry>
  </macro>
  <macro table="10-11" name="SOP Instance Reference Macro Attributes">
    <entry group="0008" element="1150" name="Referenced SOP Class UID" type="1">
      <description>Uniquely identifies the referenced SOP Class.</description>
    </entry>
    <entry group="0008" element="1155" name="Referenced SOP Instance UID" type="1">
      <description>Uniquely identifies the referenced SOP Instance.</description>
    </entry>
  </macro>
  <macro table="10-12" name="Content Identification Macro">
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description>A number that identifies this SOP Instance.</description>
    </entry>
    <entry group="0070" element="0080" name="Content Label" type="1">
      <description>A label that is used to identify this SOP Instance.</description>
    </entry>
    <entry group="0070" element="0081" name="Content Description" type="2">
      <description>A description of the content of the SOP Instance.</description>
    </entry>
    <entry group="0070" element="0084" name="Content Creator's Name" type="2">
      <description>Name of operator (such as a technologist or physician) creating the content of the SOP Instance.</description>
    </entry>
    <entry group="0070" element="0086" name="Content Creator's Identification Code Sequence" type="3">
      <description>Identification of the person who created the real world value mapping. Only a single item shall be present in this sequence.</description>
    </entry>
    <include ref="&gt; Include Person Identification Macro Table 10-1"/>
  </macro>
  <macro table="10-13" name="General Contributing Sources Macro Attributes">
    <entry group="0020" element="9529" name="Contributing SOP Instances Reference Sequence" type="1C">
      <description>A sequence that identifies the contributing SOP Instances.
Required if this SOP Instance is created from other DICOM SOP Instances.
Note: The attribute is absent in the case where the sources used to create this SOP Instance are not SOP Instances, e.g., a volume that was directly generated by an acquisition system.
One or more Items may be present.</description>
    </entry>
    <entry group="0020" element="000D" name="&gt;Study Instance UID" type="1">
      <description>Unique identifier for the Study of the Contributing SOP Instances.</description>
    </entry>
    <entry group="0008" element="1115" name="&gt;Referenced Series Sequence" type="1">
      <description>Sequence of Items each of which includes the Attributes of one Series.
One or more Items may be present.</description>
    </entry>
    <entry group="0020" element="000E" name="&gt;&gt;Series Instance UID" type="1">
      <description>Unique identifier of the Series containing the referenced Instances.</description>
    </entry>
    <entry group="0020" element="0011" name="&gt;&gt;Series Number" type="2">
      <description>A number that identifies this Series.</description>
    </entry>
    <entry group="0008" element="114A" name="&gt;&gt;Referenced Instance Sequence" type="1">
      <description>Sequence of Items each providing a reference to an Instance that is part of the Series defined by Series Instance UID (0020,000E) in the enclosing Item.
One or more Items may be present.</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0020" element="0013" name="&gt;&gt;&gt;Instance Number" type="2">
      <description>A number that identifies this instance.</description>
    </entry>
    <entry group="0008" element="0070" name="Manufacturer" type="2">
      <description>Manufacturer of the equipment that produced the sources.</description>
    </entry>
    <entry group="0008" element="1090" name="Manufacturer's Model Name" type="1C">
      <description>Manufacturer's model name of the equipment that produced the sources.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="1000" name="Device Serial Number" type="1C">
      <description>Manufacturer's serial number of the equipment that produced the sources.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="1020" name="Software Versions" type="1C">
      <description>Manufacturer's designation of software version of the equipment that produced the sources.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0008" element="002A" name="Acquisition DateTime" type="1C">
      <description>The time the acquisition of data that resulted in sources started.
The value shall be the start date and time of the first contributing SOP Instance of the group specified by the Contributing SOP Instances Reference Sequence (0020,9529).
Required if present and consistent in the contributing SOP Instances.
Note: The Acquisition DateTime may be created by combining the values of Acquisition Date (0008,0022) and Acquisition Time (0008,0032) attributes in the contributing SOP Instances.</description>
    </entry>
    <entry group="0008" element="1010" name="Station Name" type="1C">
      <description>User defined name identifying the machine that produced the sources.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0008" element="1070" name="Operators' Name" type="1C">
      <description>Name(s) of the operator(s) supporting the Series.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0008" element="1072" name="Operator Identification Sequence" type="1C">
      <description>Identification of the operator(s) supporting the Series. One or more items shall be included in this sequence. If more than one Item, the number and order shall correspond to the value of Operators' Name (0008,1070), if present.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <include ref="&gt;Include 'Person Identification Macro' Table 10-1"/>
    <entry group="0018" element="1030" name="Protocol Name" type="1C">
      <description>User-defined description of the conditions under which the Series was performed.
Required if present and consistent in the contributing SOP Instances.
Note: This attribute conveys series-specific protocol identification and may or may not be identical to the one presented in the Performed Protocol Code Sequence (0040,0260).</description>
    </entry>
    <entry group="0040" element="0260" name="Performed Protocol Code Sequence" type="1C">
      <description>Sequence describing the Protocol performed for the Procedure Step creating the sources. One or more Items may be included in this Sequence.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0018" element="9423" name="Acquisition Protocol Name" type="1C">
      <description>User defined name of the protocol used to acquire this image.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
  </macro>
  <macro table="10-14" name="Contributing Image Sources Macro Attributes">
    <entry group="0028" element="0010" name="Rows" type="1">
      <description>Number of rows in the images.</description>
    </entry>
    <entry group="0028" element="0011" name="Columns" type="1">
      <description>Number of columns in the images.</description>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored. See PS 3.5 for further explanation.</description>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1C">
      <description>Specifies whether the Source Images have undergone lossy compression. Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5 for further explanation.
Required if it is known whether or not Lossy Compression has been performed on the Images.
Note: In some SOP Class definitions the Lossy Image Compression attribute is optional.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2112" name="Lossy Image Compression Ratio" type="1C">
      <description>See C.7.6.1.1.5 for further explanation.
Required if Lossy Image Compression (0028,2110) equals 01.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2114" name="Lossy Image Compression Method" type="1C">
      <description>A label for the lossy compression method(s) that have been applied to the source images.
See C.7.6.1.1.5 for further explanation.
May be multi-valued if successive lossy compression steps have been applied; the value order shall correspond to the values of Lossy Image Compression Ratio (0028,2112).
Note: For historical reasons, the lossy compression method may also be described in Derivation Description (0008,2111).
Required if Lossy Image Compression (0028,2110) equals 01.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
  </macro>
  <macro table="10-15" name="Patient Orientation Macro Attributes">
    <entry group="0054" element="0410" name="Patient Orientation Code Sequence" type="1">
      <description>Sequence that describes the orientation of the patient with respect to gravity.
See C.8.11.5.1.2 for further explanation.
Only a single Item shall be permitted in this Sequence.</description>
      <section ref="C.8.11.5.1.2" name="">This Attribute is not related to Patient Orientation (0020,0020) and conveys a different concept entirely.
</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID 19"/>
    <entry group="0054" element="0412" name="&gt; Patient Orientation Modifier Code Sequence" type="1C">
      <description>Patient orientation modifier.
Required if needed to fully specify the orientation of the patient with respect to gravity.
Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID 20"/>
    <entry group="0054" element="0414" name="Patient Gantry Relationship Code Sequence" type="3">
      <description>Sequence that describes the orientation of the patient with respect to the head of the table. See Section C.8.4.6.1.3 for further explanation.
Only a single Item shall be permitted in this Sequence.</description>
      <section ref="C.8.4.6.1.3" name="">Patient Gantry Relationship Code Sequence (0054,0414) is used to describe the patient direction within the gantry, such as head-first or feet-first. When imaging the extremities, these directions are related to normal anatomic position.
Example: In normal anatomic position, the fingers point towards the feet.
</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID 21"/>
  </macro>
  <macro table="10-16" name="Performed Procedure Step Summary Macro Attributes">
    <entry group="0040" element="0253" name="Performed Procedure Step ID" type="3">
      <description>User or equipment generated identifier of that part of a Procedure that has been carried out within this step.</description>
    </entry>
    <entry group="0040" element="0244" name="Performed Procedure Step Start Date" type="3">
      <description>Date on which the Performed Procedure Step started.</description>
    </entry>
    <entry group="0040" element="0245" name="Performed Procedure Step Start Time" type="3">
      <description>Time on which the Performed Procedure Step started.</description>
    </entry>
    <entry group="0040" element="0254" name="Performed Procedure Step Description" type="3">
      <description>Institution-generated description or classification of the Procedure Step that was performed.</description>
    </entry>
    <entry group="0040" element="0260" name="Performed Protocol Code Sequence" type="3">
      <description>Sequence describing the Protocol performed for this Procedure Step. One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Context ID may be defined in the macro invocation."/>
    <entry group="0040" element="0440" name="&gt;Protocol Context Sequence" type="3">
      <description>Sequence that specifies the context for the Performed Protocol Code Sequence Item. One or more items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Content Item Macro' Table 10-2" description="Context ID may be defined in the macro invocation."/>
    <entry group="0040" element="0441" name="&gt;&gt; Content Item Modifier Sequence" type="3">
      <description>Sequence that specifies modifiers for a Protocol Context Content Item. One or more items may be included in this sequence. See Section C.4.10.1.</description>
      <section ref="C.4.10.1" name="">The Protocol Context Sequence (0040,0440) allows the specification of parameters that further qualify the scheduled protocol, provided through a set of generic name/value pairs of context Content Items.
Note:  This allows the specification of clinical, acquisition, or procedural qualifiers for the scheduled protocol, such as a specific body part, imaging technique, or parameters of a preparatory event (e.g., radionuclide injection). Specific uses of this Sequence may be documented in a Template defined in accordance with PS3.16.

</section>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Content Item Macro' Table 10-2" description="Context ID may be defined in the macro invocation."/>
    <entry group="0040" element="0280" name="Comments on the Performed Procedure Step" type="3">
      <description>User-defined comments on the Performed Procedure Step.</description>
    </entry>
  </macro>
  <iod table="A.2-1" name="CR Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="CR Series" ref="C.8.1.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Contrast/bolus" ref="C.7.6.4" usage="C - Required if contrast media was used in this image"/>
    <entry ie="Image" name="Display Shutter" ref="C.7.6.11" usage="U"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="CR Image" ref="C.8.1.2" usage="M"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="Modality LUT" ref="C.11.1" usage="U"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.3-1" name="CT Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Plane" ref="C.7.6.2" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Contrast/bolus" ref="C.7.6.4" usage="C - Required if contrast media was used in this image"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="CT Image" ref="C.8.2.1" usage="M"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.4-1" name="MR Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Plane" ref="C.7.6.2" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Contrast/bolus" ref="C.7.6.4" usage="C - Required if contrast media was used in this image"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="MR Image" ref="C.8.3.1" usage="M"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.5-1" name="NM Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="NM/PET Patient Orientation" ref="C.8.4.6" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="U - See Section A.5.4.1"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="NM Image Pixel" ref="C.8.4.7" usage="M"/>
    <entry ie="Image" name="Multi-frame" ref="C.7.6.6" usage="M"/>
    <entry ie="Image" name="NM Multi-frame" ref="C.8.4.8" usage="M"/>
    <entry ie="Image" name="NM Image" ref="C.8.4.9" usage="M"/>
    <entry ie="Image" name="NM Isotope" ref="C.8.4.10" usage="M"/>
    <entry ie="Image" name="NM Detector" ref="C.8.4.11" usage="M"/>
    <entry ie="Image" name="NM TOMO Acquisition" ref="C.8.4.12" usage="C - Required if Image Type (0008,0008) Value 3 is TOMO, GATED TOMO, RECON TOMO or RECON GATED TOMO"/>
    <entry ie="Image" name="NM Multi-gated Acquisition" ref="C.8.4.13" usage="C - Required if Image Type (0008,0008) Value 3 is GATED, GATED TOMO, or RECON GATED TOMO"/>
    <entry ie="Image" name="NM Phase" ref="C.8.4.14" usage="C - Required if Image Type (0008,0008) Value 3 is DYNAMIC"/>
    <entry ie="Image" name="NM Reconstruction" ref="C.8.4.15" usage="C - Required if Image Type (0008,0008) Value 3 is RECON TOMO or RECON GATED TOMO"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="Multi-frame Overlay" ref="C.9.3" usage="U"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.6-1" name="US Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Contrast/bolus" ref="C.7.6.4" usage="C - Required if contrast media was used in this image"/>
    <entry ie="Image" name="Palette Color Lookup Table" ref="C.7.9" usage="C - Required if Photometic Interpretation (0028,0004) has a value of PALETTE COLOR"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="US Region Calibration" ref="C.8.5.5" usage="U"/>
    <entry ie="Image" name="US Image" ref="C.8.5.6" usage="M"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.7-1" name="US Multi Frame Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="C - Required if Modality (0008,0060) = IVUS. May be present otherwise."/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Contrast/bolus" ref="C.7.6.4" usage="C - Required if contrast media was used in this image."/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="M"/>
    <entry ie="Image" name="Multi-frame" ref="C.7.6.6" usage="M"/>
    <entry ie="Image" name="Frame Pointers" ref="C.7.6.9" usage="U"/>
    <entry ie="Image" name="Palette Color Lookup Table" ref="C.7.9" usage="C - Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="US Region Calibration" ref="C.8.5.5" usage="U"/>
    <entry ie="Image" name="US Image" ref="C.8.5.6" usage="M"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.8-1" name="SC Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="U"/>
    <entry ie="Equipment" name="SC Equipment" ref="C.8.6.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="SC Image" ref="C.8.6.2" usage="M"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="Modality LUT" ref="C.11.1" usage="U"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.8-2" name="Multi Frame Single Bit SC Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="U"/>
    <entry ie="Equipment" name="SC Equipment" ref="C.8.6.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="C - Required if Frame Increment Pointer (0028,0009) is Frame Time (0018,1063) or Frame Time Vector (0018,1065)"/>
    <entry ie="Image" name="Multi-frame" ref="C.7.6.6" usage="M"/>
    <entry ie="Image" name="Frame Pointers" ref="C.7.6.9" usage="U"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="SC Image" ref="C.8.6.2" usage="U"/>
    <entry ie="Image" name="SC Multi-frame Image" ref="C.8.6.3" usage="M"/>
    <entry ie="Image" name="SC Multi-frame Vector" ref="C.8.6.4" usage="C - Required if Number of Frames is greater than 1"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.8-3" name="Multi Frame Grayscale Byte SC Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="U"/>
    <entry ie="Equipment" name="SC Equipment" ref="C.8.6.1" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="C - Required if Pixel Measures or Plane Position or Plane Orientation Functional Group Macros Present"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="U"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="C - Required if Frame Increment Pointer (0028,0009) is Frame Time (0018,1063) or Frame Time Vector (0018,1065)"/>
    <entry ie="Image" name="Multi-frame" ref="C.7.6.6" usage="M"/>
    <entry ie="Image" name="Frame Pointers" ref="C.7.6.9" usage="U"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Multi-frame Functional Groups" ref="C.7.6.16" usage="U"/>
    <entry ie="Image" name="Multi-frame Dimension" ref="C.7.6.17" usage="U"/>
    <entry ie="Image" name="SC Image" ref="C.8.6.2" usage="U"/>
    <entry ie="Image" name="SC Multi-frame Image" ref="C.8.6.3" usage="M"/>
    <entry ie="Image" name="SC Multi-frame Vector" ref="C.8.6.4" usage="C - Required if Number of Frames is greater than 1"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="C - Required if the VOI LUT stage is not an identity transformation"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.8-4" name="Multi Frame Grayscale Word SC Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="U"/>
    <entry ie="Equipment" name="SC Equipment" ref="C.8.6.1" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="C - Required if Pixel Measures or Plane Position or Plane Orientation Functional Group Macros Present"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="U"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="C - Required if Frame Increment Pointer (0028,0009) is Frame Time (0018,1063) or Frame Time Vector (0018,1065)"/>
    <entry ie="Image" name="Multi-frame" ref="C.7.6.6" usage="M"/>
    <entry ie="Image" name="Frame Pointers" ref="C.7.6.9" usage="U"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Multi-frame Functional Groups" ref="C.7.6.16" usage="U"/>
    <entry ie="Image" name="Multi-frame Dimension" ref="C.7.6.17" usage="U"/>
    <entry ie="Image" name="SC Image" ref="C.8.6.2" usage="U"/>
    <entry ie="Image" name="SC Multi-frame Image" ref="C.8.6.3" usage="M"/>
    <entry ie="Image" name="SC Multi-frame Vector" ref="C.8.6.4" usage="C - Required if Number of Frames is greater than 1"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="C - Required if the VOI LUT stage is not an identity transformation"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.8-5" name="Multi Frame True Color SC Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="C - Required if Pixel Measures or Plane Position or Plane Orientation Functional Group Macros Present"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="U"/>
    <entry ie="Equipment" name="SC Equipment" ref="C.8.6.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="C - Required if Frame Increment Pointer (0028,0009) is Frame Time (0018,1063) or Frame Time Vector (0018,1065)"/>
    <entry ie="Image" name="Multi-frame" ref="C.7.6.6" usage="M"/>
    <entry ie="Image" name="Frame Pointers" ref="C.7.6.9" usage="U"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Multi-frame Functional Groups" ref="C.7.6.16" usage="U"/>
    <entry ie="Image" name="Multi-frame Dimension" ref="C.7.6.17" usage="U"/>
    <entry ie="Image" name="SC Image" ref="C.8.6.2" usage="U"/>
    <entry ie="Image" name="SC Multi-frame Image" ref="C.8.6.3" usage="M"/>
    <entry ie="Image" name="SC Multi-frame Vector" ref="C.8.6.4" usage="C - Required if Number of Frames is greater than 1"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.14-1" name="X Ray Angiographic Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Contrast/Bolus" ref="C.7.6.4" usage="C - Required if contrast media was used in this Image"/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="C - Required if pixel data is Multi-Frame Cine data"/>
    <entry ie="Image" name="Multi-Frame" ref="C.7.6.6" usage="C - Required if pixel data is Multi-Frame Cine data"/>
    <entry ie="Image" name="Frame Pointers" ref="C.7.6.9" usage="U"/>
    <entry ie="Image" name="Mask" ref="C.7.6.10" usage="C - Required if the Image may be subtracted"/>
    <entry ie="Image" name="Display Shutter" ref="C.7.6.11" usage="U"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Intervention" ref="C.7.6.13" usage="U"/>
    <entry ie="Image" name="X-Ray Image" ref="C.8.7.1" usage="M"/>
    <entry ie="Image" name="X-Ray Acquisition" ref="C.8.7.2" usage="M"/>
    <entry ie="Image" name="X-Ray Collimator" ref="C.8.7.3" usage="U"/>
    <entry ie="Image" name="X-Ray Table" ref="C.8.7.4" usage="C - Required if Image is created with table motion, may be present otherwise"/>
    <entry ie="Image" name="XA Positioner" ref="C.8.7.5" usage="M"/>
    <entry ie="Image" name="DX Detector" ref="C.8.11.4" usage="U"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="Multi-Frame Overlay" ref="C.9.3" usage="C - Required if Overlay data contains multiple frames."/>
    <entry ie="Image" name="Modality LUT" ref="C.11.1" usage="C - Required if Pixel Intensity Relationship (0028,1040) is LOG U - Optional if Pixel Intensity Relationship (0028,1040) is DISP"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.16-1" name="XRF Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Contrast/bolus" ref="C.7.6.4" usage="C - Required if contrast media was used in this Image"/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="C - Required if pixel data is Multi-Frame Cine Data"/>
    <entry ie="Image" name="Multi-Frame" ref="C.7.6.6" usage="C - Required if pixel data is Multi-Frame Cine Data"/>
    <entry ie="Image" name="Frame Pointers" ref="C.7.6.9" usage="U"/>
    <entry ie="Image" name="Mask" ref="C.7.6.10" usage="C - Required if the Image may be subtracted"/>
    <entry ie="Image" name="X-Ray Image" ref="C.8.7.1" usage="M"/>
    <entry ie="Image" name="X-Ray Acquisition" ref="C.8.7.2" usage="M"/>
    <entry ie="Image" name="X-Ray Collimator" ref="C.8.7.3" usage="U"/>
    <entry ie="Image" name="Display Shutter" ref="C.7.6.11" usage="U"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Intervention" ref="C.7.6.13" usage="U"/>
    <entry ie="Image" name="X-Ray Table" ref="C.8.7.4" usage="U"/>
    <entry ie="Image" name="XRF Positioner" ref="C.8.7.6" usage="U"/>
    <entry ie="Image" name="X-Ray Tomo Acquisition" ref="C.8.7.7" usage="C - Required if Scan Option (0018,0022) is TOMO"/>
    <entry ie="Image" name="DX Detector" ref="C.8.11.4" usage="U"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="Multi-frame Overlay" ref="C.9.3" usage="C - Required if Overlay Data contains multiple frames"/>
    <entry ie="Image" name="Modality LUT" ref="C.11.1" usage="C - Required if Pixel Intensity Relationship (0028,1040) is LOG U - Optional if Pixel Intensity Relationship (0028,1040) is DISP"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.17.3-1" name="RT Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="RT Series" ref="C.8.8.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Contrast/bolus" ref="C.7.6.4" usage="C-Required if contrast media was used in this image."/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="C - Required if multi-frame image is a cine image."/>
    <entry ie="Image" name="Multi-Frame" ref="C.7.6.6" usage="C - Required if pixel data is multi-frame data."/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="RT Image" ref="C.8.8.2" usage="M"/>
    <entry ie="Image" name="Modality LUT" ref="C.11.1" usage="U"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="U"/>
    <entry ie="Image" name="Approval" ref="C.8.8.16" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.18.3-1" name="RT Dose IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="RT Series" ref="C.8.8.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Dose" name="General Image" ref="C.7.6.1" usage="C - Required if dose data contains grid-based doses."/>
    <entry ie="Dose" name="Image Plane" ref="C.7.6.2" usage="C - Required if dose data contains grid-based doses."/>
    <entry ie="Dose" name="Image Pixel" ref="C.7.6.3" usage="C - Required if dose data contains grid-based doses."/>
    <entry ie="Dose" name="Multi-Frame" ref="C.7.6.6" usage="C - Required if dose data contains grid-based doses and pixel data is multi-frame data."/>
    <entry ie="Dose" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Dose" name="Multi-Frame Overlay" ref="C.9.3" usage="U"/>
    <entry ie="Dose" name="Modality LUT" ref="C.11.1" usage="U"/>
    <entry ie="Dose" name="RT Dose" ref="C.8.8.3" usage="M"/>
    <entry ie="Dose" name="RT DVH" ref="C.8.8.4" usage="U"/>
    <entry ie="Dose" name="Structure Set" ref="C.8.8.5" usage="C - Required if dose data contains dose points or isodose curves"/>
    <entry ie="Dose" name="ROI Contour" ref="C.8.8.6" usage="C - Required if dose data contains dose points or isodose curves"/>
    <entry ie="Dose" name="RT Dose ROI" ref="C.8.8.7" usage="C - Required if dose data contains dose points or isodose curves"/>
    <entry ie="Dose" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.19.3-1" name="RT Structure Set IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="RT Series" ref="C.8.8.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Structure Set" name="Structure Set" ref="C.8.8.5" usage="M"/>
    <entry ie="Structure Set" name="ROI Contour" ref="C.8.8.6" usage="M"/>
    <entry ie="Structure Set" name="RT ROI Observations" ref="C.8.8.8" usage="M"/>
    <entry ie="Structure Set" name="Approval" ref="C.8.8.16" usage="U"/>
    <entry ie="Structure Set" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.20.3-1" name="RT Plan IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="RT Series" ref="C.8.8.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="U - See Note."/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Plan" name="RT General Plan" ref="C.8.8.9" usage="M"/>
    <entry ie="Plan" name="RT Prescription" ref="C.8.8.10" usage="U"/>
    <entry ie="Plan" name="RT Tolerance Tables" ref="C.8.8.11" usage="U"/>
    <entry ie="Plan" name="RT Patient Setup" ref="C.8.8.12" usage="U"/>
    <entry ie="Plan" name="RT Fraction Scheme" ref="C.8.8.13" usage="U"/>
    <entry ie="Plan" name="RT Beams" ref="C.8.8.14" usage="C - Required if RT Fraction Scheme Module exists and Number of Beams (300A,0080) is greater than zero for one or more fraction groups"/>
    <entry ie="Plan" name="RT Brachy Application Setups" ref="C.8.8.15" usage="C - Required if RT Fraction Scheme Module exists and Number of Brachy Application Setups (300A,00A0) is greater than zero for one or more fraction groups"/>
    <entry ie="Plan" name="Approval" ref="C.8.8.16" usage="U"/>
    <entry ie="Plan" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.21.3-1" name="PET Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="PET Series" ref="C.8.9.1" usage="M"/>
    <entry ie="Series" name="PET Isotope" ref="C.8.9.2" usage="M"/>
    <entry ie="Series" name="PET Multi-gated Acquisition" ref="C.8.9.3" usage="C - Required if Series Type (0054,1000) Value 1 is GATED."/>
    <entry ie="Series" name="NM/PET Patient Orientation" ref="C.8.4.6" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Plane" ref="C.7.6.2" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="PET Image" ref="C.8.9.4" usage="M"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="U"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.26-1" name="Digital X Ray Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="DX Series" ref="C.8.11.1" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Contrast/Bolus" ref="C.7.6.4" usage="U"/>
    <entry ie="Image" name="Display Shutter" ref="C.7.6.11" usage="U"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Intervention" ref="C.7.6.13" usage="U"/>
    <entry ie="Image" name="DX Anatomy Imaged" ref="C.8.11.2" usage="M"/>
    <entry ie="Image" name="DX Image" ref="C.8.11.3" usage="M"/>
    <entry ie="Image" name="DX Detector" ref="C.8.11.4" usage="M"/>
    <entry ie="Image" name="X-Ray Collimator" ref="C.8.7.3" usage="U"/>
    <entry ie="Image" name="DX Positioning" ref="C.8.11.5" usage="U"/>
    <entry ie="Image" name="X-Ray Tomo Acquisition" ref="C.8.7.7" usage="U"/>
    <entry ie="Image" name="X-Ray Acquisition Dose" ref="C.8.7.8" usage="U"/>
    <entry ie="Image" name="X-Ray Generation" ref="C.8.7.9" usage="U"/>
    <entry ie="Image" name="X-Ray Filtration" ref="C.8.7.10" usage="U"/>
    <entry ie="Image" name="X-Ray Grid" ref="C.8.7.11" usage="U"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="C - Required if graphic annotation is present - See A.26.4"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="C - Required if Presentation Intent Type (0008,0068) is FOR PRESENTATION. Shall not be present otherwise. See Note 8."/>
    <entry ie="Image" name="Image Histogram" ref="C.11.5" usage="U"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.27-1" name="Digital Mammography X Ray Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="DX Series" ref="C.8.11.1" usage="M"/>
    <entry ie="Series" name="Mammography Series" ref="C.8.11.6" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="C - Required if multiple images are obtained without releasing breast compression"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Contrast/Bolus" ref="C.7.6.4" usage="U"/>
    <entry ie="Image" name="Display Shutter" ref="C.7.6.11" usage="U"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Intervention" ref="C.7.6.13" usage="U"/>
    <entry ie="Image" name="DX Anatomy Imaged" ref="C.8.11.2" usage="M"/>
    <entry ie="Image" name="DX Image" ref="C.8.11.3" usage="M"/>
    <entry ie="Image" name="DX Detector" ref="C.8.11.4" usage="M"/>
    <entry ie="Image" name="X-Ray Collimator" ref="C.8.7.3" usage="U"/>
    <entry ie="Image" name="DX Positioning" ref="C.8.11.5" usage="U"/>
    <entry ie="Image" name="X-Ray Tomo Acquisition" ref="C.8.7.7" usage="U"/>
    <entry ie="Image" name="X-Ray Acquisition Dose" ref="C.8.7.8" usage="U"/>
    <entry ie="Image" name="X-Ray Generation" ref="C.8.7.9" usage="U"/>
    <entry ie="Image" name="X-Ray Filtration" ref="C.8.7.10" usage="U"/>
    <entry ie="Image" name="X-Ray Grid" ref="C.8.7.11" usage="U"/>
    <entry ie="Image" name="Mammography Image" ref="C.8.11.7" usage="M"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="C - Required if graphic annotation is present - See A.27.3"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="C - Required if Presentation Intent Type (0008,0068) is FOR PRESENTATION. Shall not be present otherwise."/>
    <entry ie="Image" name="Image Histogram" ref="C.11.5" usage="U"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.28-1" name="Digital Intra Oral X Ray Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="DX Series" ref="C.8.11.1" usage="M"/>
    <entry ie="Series" name="Intra-oral Series" ref="C.8.11.8" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Contrast/Bolus" ref="C.7.6.4" usage="U"/>
    <entry ie="Image" name="Display Shutter" ref="C.7.6.11" usage="U"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Intervention" ref="C.7.6.13" usage="U"/>
    <entry ie="Image" name="DX Anatomy Imaged" ref="C.8.11.2" usage="M"/>
    <entry ie="Image" name="DX Image" ref="C.8.11.3" usage="M"/>
    <entry ie="Image" name="DX Detector" ref="C.8.11.4" usage="M"/>
    <entry ie="Image" name="X-Ray Collimator" ref="C.8.7.3" usage="U"/>
    <entry ie="Image" name="DX Positioning" ref="C.8.11.5" usage="U"/>
    <entry ie="Image" name="X-Ray Tomo Acquisition" ref="C.8.7.7" usage="U"/>
    <entry ie="Image" name="X-Ray Acquisition Dose" ref="C.8.7.8" usage="U"/>
    <entry ie="Image" name="X-Ray Generation" ref="C.8.7.9" usage="U"/>
    <entry ie="Image" name="X-Ray Filtration" ref="C.8.7.10" usage="U"/>
    <entry ie="Image" name="X-Ray Grid" ref="C.8.7.11" usage="U"/>
    <entry ie="Image" name="Intra-oral Image" ref="C.8.11.9" usage="M"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="C - Required if graphic annotation is present - See A.28.3"/>
    <entry ie="Image" name="VOI LUT" ref="C.11.2" usage="C - Required if Presentation Intent Type (0008,0068) is FOR PRESENTATION. Shall not be present otherwise."/>
    <entry ie="Image" name="Image Histogram" ref="C.11.5" usage="U"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.29.3-1" name="RT Beams Treatment Record IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="RT Series" ref="C.8.8.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Treatment Record" name="RT General Treatment Record" ref="C.8.8.17" usage="M"/>
    <entry ie="Treatment Record" name="RT Patient Setup" ref="C.8.8.12" usage="U"/>
    <entry ie="Treatment Record" name="RT Treatment Machine Record" ref="C.8.8.18" usage="M"/>
    <entry ie="Treatment Record" name="Measured Dose Reference Record" ref="C.8.8.19" usage="U"/>
    <entry ie="Treatment Record" name="Calculated Dose Reference Record" ref="C.8.8.20" usage="U"/>
    <entry ie="Treatment Record" name="RT Beams Session Record" ref="C.8.8.21" usage="M"/>
    <entry ie="Treatment Record" name="RT Treatment Summary Record" ref="C.8.8.23" usage="U"/>
    <entry ie="Treatment Record" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.30.3-1" name="RT Brachy Treatment Record IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="RT Series" ref="C.8.8.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Treatment Record" name="RT General Treatment Record" ref="C.8.8.17" usage="M"/>
    <entry ie="Treatment Record" name="RT Patient Setup" ref="C.8.8.12" usage="U"/>
    <entry ie="Treatment Record" name="RT Treatment Machine Record" ref="C.8.8.18" usage="M"/>
    <entry ie="Treatment Record" name="Measured Dose Reference Record" ref="C.8.8.19" usage="U"/>
    <entry ie="Treatment Record" name="Calculated Dose Reference Record" ref="C.8.8.20" usage="U"/>
    <entry ie="Treatment Record" name="RT Brachy Session Record" ref="C.8.8.22" usage="M"/>
    <entry ie="Treatment Record" name="RT Treatment Summary Record" ref="C.8.8.23" usage="U"/>
    <entry ie="Treatment Record" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.31.3-1" name="RT Treatment Summary Record IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="RT Series" ref="C.8.8.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Treatment Record" name="RT General Treatment Record" ref="C.8.8.17" usage="M"/>
    <entry ie="Treatment Record" name="RT Treatment Summary Record" ref="C.8.8.23" usage="M"/>
    <entry ie="Treatment Record" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.32.1-1" name="VL Endoscopic Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="VL Image" ref="C.8.12.1" usage="M"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.32.1-2" name="VL Microscopic Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Imaging Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="VL Image" ref="C.8.12.1" usage="M"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.32.1-3" name="VL Slide Coordinates Microscopic Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Imaging Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="VL Image" ref="C.8.12.1" usage="M"/>
    <entry ie="Image" name="Slide Coordinates" ref="C.8.12.2" usage="M"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.32.4-1" name="VL Photographic Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Imaging Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="VL Image" ref="C.8.12.1" usage="M"/>
    <entry ie="Image" name="Overlay Plane" ref="C.9.2" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.32.5-1" name="Video Endoscopic Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="M"/>
    <entry ie="Image" name="Multi-frame" ref="C.7.6.6" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="VL Image" ref="C.8.12.1" usage="M"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.32.6-1" name="Video Microscopic Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Imaging Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="M"/>
    <entry ie="Image" name="Multi-frame" ref="C.7.6.6" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="VL Image" ref="C.8.12.1" usage="M"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.32.7-1" name="Video Photographic Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Imaging Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="M"/>
    <entry ie="Image" name="Multi-frame" ref="C.7.6.6" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="VL Image" ref="C.8.12.1" usage="M"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.33.1-1" name="Grayscale Softcopy Presentation State IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Presentation Series" ref="C.11.9" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Identification" ref="C.11.10" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Relationship" ref="C.11.11" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Shutter" ref="C.11.12" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Mask" ref="C.11.13" usage="M"/>
    <entry ie="Presentation State" name="Mask" ref="C.7.6.10" usage="C - Required if the referenced image(s) are multi-frame and are to be subtracted"/>
    <entry ie="Presentation State" name="Display Shutter" ref="C.7.6.11" usage="C - Required if a Display Shutter is to be applied to referenced image(s) and the Bitmap Display Shutter Module is not present"/>
    <entry ie="Presentation State" name="Bitmap Display Shutter" ref="C.7.6.15" usage="C - Required if a Display Shutter is to be applied to referenced image(s) and the Display Shutter Module is not present"/>
    <entry ie="Presentation State" name="Overlay Plane" ref="C.9.2" usage="C - Required if Overlay is to be applied to referenced image(s) or the Bitmap Display Shutter Module is present"/>
    <entry ie="Presentation State" name="Overlay Activation" ref="C.11.7" usage="C- Required if referenced image contains overlay data that is to be displayed"/>
    <entry ie="Presentation State" name="Displayed Area" ref="C.10.4" usage="M"/>
    <entry ie="Presentation State" name="Graphic Annotation" ref="C.10.5" usage="C - Required if Graphic Annotations are to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="Spatial Transformation" ref="C.10.6" usage="C - Required if rotation or flipping are to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="Graphic Layer" ref="C.10.7" usage="C - Required if Graphic Annotations or Overlays or Curves are to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="Modality LUT" ref="C.11.1" usage="C - Required if a Modality LUT is to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="Softcopy VOI LUT" ref="C.11.8" usage="C - Required if a VOI LUT is to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="Softcopy Presentation LUT" ref="C.11.6" usage="M"/>
    <entry ie="Presentation State" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.33.2-1" name="Color Softcopy Presentation State IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Presentation Series" ref="C.11.9" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Identification" ref="C.11.10" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Relationship" ref="C.11.11" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Shutter" ref="C.11.12" usage="M"/>
    <entry ie="Presentation State" name="Display Shutter" ref="C.7.6.11" usage="C - Required if a Display Shutter is to be applied to referenced image(s) and the Bitmap Display Shutter Module is not present"/>
    <entry ie="Presentation State" name="Bitmap Display Shutter" ref="C.7.6.15" usage="C - Required if a Display Shutter is to be applied to referenced image(s) and the Display Shutter Module is not present"/>
    <entry ie="Presentation State" name="Overlay Plane" ref="C.9.2" usage="C - Required if Overlay is to be applied to referenced image(s) or the Bitmap Display Shutter Module is present"/>
    <entry ie="Presentation State" name="Overlay Activation" ref="C.11.7" usage="C- Required if referenced image contains overlay data which is to be displayed"/>
    <entry ie="Presentation State" name="Displayed Area" ref="C.10.4" usage="M"/>
    <entry ie="Presentation State" name="Graphic Annotation" ref="C.10.5" usage="C - Required if Graphic Annotations are to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="Spatial Transformation" ref="C.10.6" usage="C - Required if rotation, flipping or magnification are to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="Graphic Layer" ref="C.10.7" usage="C - Required if Graphic Annotations or Overlays or Curves are to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="ICC Profile" ref="C.11.15" usage="M"/>
    <entry ie="Presentation State" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.33.3-1" name="Pseudo Color Softcopy Presentation State IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Presentation Series" ref="C.11.9" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Identification" ref="C.11.10" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Relationship" ref="C.11.11" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Shutter" ref="C.11.12" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Mask" ref="C.11.13" usage="M"/>
    <entry ie="Presentation State" name="Mask" ref="C.7.6.10" usage="C - Required if the referenced image(s) are multi-frame and are to be subtracted"/>
    <entry ie="Presentation State" name="Display Shutter" ref="C.7.6.11" usage="C - Required if a Display Shutter is to be applied to referenced image(s) and the Bitmap Display Shutter Module is not present"/>
    <entry ie="Presentation State" name="Bitmap Display Shutter" ref="C.7.6.15" usage="C - Required if a Display Shutter is to be applied to referenced image(s) and the Display Shutter Module is not present"/>
    <entry ie="Presentation State" name="Overlay Plane" ref="C.9.2" usage="C - Required if Overlay is to be applied to referenced image(s) or the Bitmap Display Shutter Module is present"/>
    <entry ie="Presentation State" name="Overlay Activation" ref="C.11.7" usage="C- Required if referenced image contains overlay data that is to be displayed"/>
    <entry ie="Presentation State" name="Displayed Area" ref="C.10.4" usage="M"/>
    <entry ie="Presentation State" name="Graphic Annotation" ref="C.10.5" usage="C - Required if Graphic Annotations are to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="Spatial Transformation" ref="C.10.6" usage="C - Required if rotation or flipping are to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="Graphic Layer" ref="C.10.7" usage="C - Required if Graphic Annotations or Overlays or Curves are to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="Modality LUT" ref="C.11.1" usage="C - Required if a Modality LUT is to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="Softcopy VOI LUT" ref="C.11.8" usage="C - Required if a VOI LUT is to be applied to referenced image(s)"/>
    <entry ie="Presentation State" name="Palette Color LUT" ref="C.7.9" usage="M"/>
    <entry ie="Presentation State" name="ICC Profile" ref="C.11.15" usage="M"/>
    <entry ie="Presentation State" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.33.4-1" name="Blending Softcopy Presentation State IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Presentation Series" ref="C.11.9" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Identification" ref="C.11.10" usage="M"/>
    <entry ie="Presentation State" name="Presentation State Blending" ref="C.11.14" usage="M"/>
    <entry ie="Presentation State" name="Displayed Area" ref="C.10.4" usage="M"/>
    <entry ie="Presentation State" name="Graphic Annotation" ref="C.10.5" usage="C - Required if Graphic Annotations are to be applied"/>
    <entry ie="Presentation State" name="Spatial Transformation" ref="C.10.6" usage="C - Required if rotation or flipping are to be applied"/>
    <entry ie="Presentation State" name="Graphic Layer" ref="C.10.7" usage="C - Required if Graphic Annotation Module is present"/>
    <entry ie="Presentation State" name="Palette Color LUT" ref="C.7.9" usage="M"/>
    <entry ie="Presentation State" name="ICC Profile" ref="C.11.15" usage="M"/>
    <entry ie="Presentation State" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.34.2-1" name="Basic Voice Audio IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Waveform" name="Waveform Identification" ref="C.10.8" usage="M"/>
    <entry ie="Waveform" name="Waveform" ref="C.10.9" usage="M"/>
    <entry ie="Waveform" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Waveform" name="Waveform Annotation" ref="C.10.10" usage="U"/>
    <entry ie="Waveform" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.34.3-1" name="12 Lead ECG IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Waveform" name="Waveform Identification" ref="C.10.8" usage="M"/>
    <entry ie="Waveform" name="Waveform" ref="C.10.9" usage="M"/>
    <entry ie="Waveform" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Waveform" name="Waveform Annotation" ref="C.10.10" usage="C - Required if annotation is present"/>
    <entry ie="Waveform" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.34.4-1" name="General ECG IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Waveform" name="Waveform Identification" ref="C.10.8" usage="M"/>
    <entry ie="Waveform" name="Waveform" ref="C.10.9" usage="M"/>
    <entry ie="Waveform" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Waveform" name="Waveform Annotation" ref="C.10.10" usage="C - Required if annotation is present"/>
    <entry ie="Waveform" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.34.5-1" name="Ambulatory ECG IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Waveform" name="Waveform Identification" ref="C.10.8" usage="M"/>
    <entry ie="Waveform" name="Waveform" ref="C.10.9" usage="M"/>
    <entry ie="Waveform" name="Acquisition Context" ref="C.7.6.14" usage="U"/>
    <entry ie="Waveform" name="Waveform Annotation" ref="C.10.10" usage="C - Required if annotation is present"/>
    <entry ie="Waveform" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.34.6-1" name="Hemodynamic IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="C - Required if Waveform Originality (003A,0004) is ORIGINAL; may be present otherwise"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Waveform" name="Waveform Identification" ref="C.10.8" usage="M"/>
    <entry ie="Waveform" name="Waveform" ref="C.10.9" usage="M"/>
    <entry ie="Waveform" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Waveform" name="Waveform Annotation" ref="C.10.10" usage="C - Required if annotation is present"/>
    <entry ie="Waveform" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.34.7-1" name="Basic Cardiac EP IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="C - Required if Waveform Originality (003A,0004) value is ORIGINAL; may be present otherwise"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Waveform" name="Waveform Identification" ref="C.10.8" usage="M"/>
    <entry ie="Waveform" name="Waveform" ref="C.10.9" usage="M"/>
    <entry ie="Waveform" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Waveform" name="Waveform Annotation" ref="C.10.10" usage="C - Required if annotation is present"/>
    <entry ie="Waveform" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.35.1-1" name="Basic Text SR IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Observation Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="SR Document Series" ref="C.17.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Document" name="SR Document General" ref="C.17.2" usage="M"/>
    <entry ie="Document" name="SR Document Content" ref="C.17.3" usage="M"/>
    <entry ie="Document" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.35.2-1" name="Enhanced SR IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Observation Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="SR Document Series" ref="C.17.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Document" name="SR Document General" ref="C.17.2" usage="M"/>
    <entry ie="Document" name="SR Document Content" ref="C.17.3" usage="M"/>
    <entry ie="Document" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.35.3-1" name="Comprehensive SR IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Observation Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="SR Document Series" ref="C.17.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Document" name="SR Document General" ref="C.17.2" usage="M"/>
    <entry ie="Document" name="SR Document Content" ref="C.17.3" usage="M"/>
    <entry ie="Document" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.35.4-1" name="Key Object Selection Document IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Observation Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="Key Object Document Series" ref="C.17.6.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Document" name="Key Object Document" ref="C.17.6.2" usage="M"/>
    <entry ie="Document" name="SR Document Content" ref="C.17.3" usage="M"/>
    <entry ie="Document" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.35.5-1" name="Mammography CAD SR IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Observation Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="SR Document Series" ref="C.17.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Document" name="SR Document General" ref="C.17.2" usage="M"/>
    <entry ie="Document" name="SR Document Content" ref="C.17.3" usage="M"/>
    <entry ie="Document" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.35.6-1" name="Chest CAD SR IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Observation Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="SR Document Series" ref="C.17.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Document" name="SR Document General" ref="C.17.2" usage="M"/>
    <entry ie="Document" name="SR Document Content" ref="C.17.3" usage="M"/>
    <entry ie="Document" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.35.7-1" name="Procedure Log IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="SR Document Series" ref="C.17.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Document" name="SR Document General" ref="C.17.2" usage="M"/>
    <entry ie="Document" name="SR Document Content" ref="C.17.3" usage="M"/>
    <entry ie="Document" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.35.8-1" name="X Ray Radiation Dose SR IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="SR Document Series" ref="C.17.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="C - shall be present if system time is synchronized to an external reference. May be present otherwise."/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Document" name="SR Document General" ref="C.17.2" usage="M"/>
    <entry ie="Document" name="SR Document Content" ref="C.17.3" usage="M"/>
    <entry ie="Document" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.36-1" name="Enhanced MR Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="MR Series" ref="C.8.13.6" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="C- Required if time synchronization was applied."/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Equipment" name="Enhanced General Equipment" ref="C.7.5.2" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Enhanced Contrast/Bolus" ref="C.7.6.4b" usage="C - Required if contrast media were applied."/>
    <entry ie="Image" name="Multi-frame Functional Groups" ref="C.7.6.16" usage="M"/>
    <entry ie="Image" name="Multi-frame Dimension" ref="C.7.6.17" usage="M"/>
    <entry ie="Image" name="Cardiac Synchronization" ref="C.7.6.18.1" usage="C - Required if cardiac synchronization was applied."/>
    <entry ie="Image" name="Respiratory Synchronization" ref="C.7.6.18.2" usage="C - Required if respiratory synchronization was applied."/>
    <entry ie="Image" name="Bulk Motion Synchronization" ref="C.7.6.18.3" usage="C - Required if bulk motion synchronization was applied."/>
    <entry ie="Image" name="Supplemental Palette Color Lookup Table" ref="C.7.6.19" usage="C - Required if Pixel Presentation (0008,9205) in the Enhanced MR Image Module equals COLOR or MIXED."/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Enhanced MR Image" ref="C.8.13.1" usage="M"/>
    <entry ie="Image" name="MR Pulse Sequence" ref="C.8.13.4" usage="C - Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise."/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.36-3" name="MR Spectroscopy IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="MR Series" ref="C.8.13.6" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="C- Required if time synchronization was applied."/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Equipment" name="Enhanced General Equipment" ref="C.7.5.2" usage="M"/>
    <entry ie="MR Spectroscopy" name="Enhanced Contrast/Bolus" ref="C.7.6.4b" usage="C - Required if contrast media were applied."/>
    <entry ie="MR Spectroscopy" name="Multi-frame Functional Groups" ref="C.7.6.16" usage="M"/>
    <entry ie="MR Spectroscopy" name="Multi-frame Dimension" ref="C.7.6.17" usage="M"/>
    <entry ie="MR Spectroscopy" name="Cardiac Synchronization" ref="C.7.6.18.1" usage="C - Required if cardiac synchronization was applied."/>
    <entry ie="MR Spectroscopy" name="Respiratory Synchronization" ref="C.7.6.18.2" usage="C - Required if respiratory synchronization was applied."/>
    <entry ie="MR Spectroscopy" name="Bulk Motion Synchronization" ref="C.7.6.18.3" usage="C - Required if bulk motion synchronization was applied."/>
    <entry ie="MR Spectroscopy" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="MR Spectroscopy" name="MR Spectroscopy" ref="C.8.14.1" usage="M"/>
    <entry ie="MR Spectroscopy" name="MR Spectroscopy Pulse Sequence" ref="C.8.14.2" usage="C - Required if Image Type (0008,0008) Value 1 is ORIGINAL. May be present otherwise."/>
    <entry ie="MR Spectroscopy" name="MR Spectroscopy Data" ref="C.8.14.4" usage="M"/>
    <entry ie="MR Spectroscopy" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.37-1" name="Raw Data IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="C- Required if time synchronization was applied."/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Raw Data" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Raw Data" name="Raw Data" ref="C.19.1" usage="M"/>
    <entry ie="Raw Data" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.38-1" name="Enhanced CT Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="CT Series" ref="C.8.15.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="C- Required if time synchronization was applied."/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Equipment" name="Enhanced General Equipment" ref="C.7.5.2" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Enhanced Contrast/Bolus" ref="C.7.6.4b" usage="C - Required if contrast media was applied."/>
    <entry ie="Image" name="Multi-frame Functional Groups" ref="C.7.6.16" usage="M"/>
    <entry ie="Image" name="Multi-frame Dimension" ref="C.7.6.17" usage="M"/>
    <entry ie="Image" name="Cardiac Synchronization" ref="C.7.6.18.1" usage="C - Required if cardiac synchronization was applied."/>
    <entry ie="Image" name="Respiratory Synchronization" ref="C.7.6.18.2" usage="C - Required if respiratory synchronization was applied."/>
    <entry ie="Image" name="Supplemental Palette Color Lookup Table" ref="C.7.6.19" usage="C - Required if Pixel Presentation (0008,9205) in the Enhanced CT Image Module equals COLOR or MIXED."/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Enhanced CT Image" ref="C.8.15.2" usage="M"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.39.1-1" name="Spatial Registration IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Spatial Registration Series" ref="C.20.1" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Spatial Registration" name="Spatial Registration" ref="C.20.2" usage="M"/>
    <entry ie="Spatial Registration" name="Common Instance Reference" ref="C.12.2" usage="M"/>
    <entry ie="Spatial Registration" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.39.2-1" name="Deformable Spatial Registration IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Spatial Registration Series" ref="C.20.1" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Equipment" name="Enhanced General Equipment" ref="C.7.5.2" usage="M"/>
    <entry ie="Deformable Registration" name="Deformable Spatial Registration" ref="C.20.3" usage="M"/>
    <entry ie="Deformable Registration" name="Common Instance Reference" ref="C.12.2" usage="M"/>
    <entry ie="Deformable Registration" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.40-1" name="Spatial Fiducials IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Spatial Fiducials Series" ref="C.21.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Spatial Fiducials" name="Spatial Fiducials" ref="C.21.2" usage="M"/>
    <entry ie="Spatial Fiducials" name="Common Instance Reference" ref="C.12.2" usage="M"/>
    <entry ie="Spatial Fiducials" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.41-1" name="Ophthalmic Photography 8 Bit Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Imaging Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Ophthalmic Photography Series" ref="C.8.17.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Enhanced Contrast/Bolus" ref="C.7.6.4b" usage="C - Required if contrast was administered, see A.41.4.2"/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="C - Required if there is a sequential temporal relationship between all frames"/>
    <entry ie="Image" name="Multi-frame" ref="C.7.6.6" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Ophthalmic Photography Image" ref="C.8.17.2" usage="M"/>
    <entry ie="Image" name="Ocular Region Imaged" ref="C.8.17.5" usage="M"/>
    <entry ie="Image" name="Ophthalmic Photography Acquisition Parameters" ref="C.8.17.4" usage="M"/>
    <entry ie="Image" name="Ophthalmic Photographic Parameters" ref="C.8.17.3" usage="M"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.42-1" name="Ophthalmic Photography 16 Bit Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Imaging Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Ophthalmic Photography Series" ref="C.8.17.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Image" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Enhanced Contrast/Bolus" ref="C.7.6.4b" usage="C - Required if contrast was administered; see A.42.4.2"/>
    <entry ie="Image" name="Cine" ref="C.7.6.5" usage="C - Required if there is a sequential temporal relationship between all frames"/>
    <entry ie="Image" name="Multi-frame" ref="C.7.6.6" usage="M"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Ophthalmic Photography Image" ref="C.8.17.2" usage="M"/>
    <entry ie="Image" name="Ocular Region Imaged" ref="C.8.17.5" usage="M"/>
    <entry ie="Image" name="Ophthalmic Photography Acquisition Parameters" ref="C.8.17.4" usage="M"/>
    <entry ie="Image" name="Ophthalmic Photographic Parameters" ref="C.8.17.3" usage="M"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.43-2" name="Stereometric Relationship IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="C - Required if the Imaging Subject is a Specimen"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Stereometric Series" ref="C.8.18.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Stereometric Relationship" name="Stereometric Relationship Module" ref="C.8.18.2" usage="M"/>
    <entry ie="Stereometric Relationship" name="Common Instance Reference Module" ref="C.12.2" usage="M"/>
    <entry ie="Stereometric Relationship" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.44.3-1" name="Hanging Protocol IOD Modules">
    <entry ie="Hanging Protocol" name="SOP Common" ref="C.12.1" usage="M"/>
    <entry ie="Hanging Protocol" name="Hanging Protocol Definition" ref="C.23.1" usage="M"/>
    <entry ie="Hanging Protocol" name="Hanging Protocol Environment" ref="C.23.2" usage="M"/>
    <entry ie="Hanging Protocol" name="Hanging Protocol Display" ref="C.23.3" usage="M"/>
  </iod>
  <iod table="A.45.1-1" name="Encapsulated PDF IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="Encapsulated Document Series" ref="C.24.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Equipment" name="SC Equipment" ref="C.8.6.1" usage="M"/>
    <entry ie="Encapsulated Document" name="Encapsulated Document" ref="C.24.2" usage="M"/>
    <entry ie="Encapsulated Document" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.45.2-1" name="Encapsulated CDA IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="Encapsulated Document Series" ref="C.24.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Equipment" name="SC Equipment" ref="C.8.6.1" usage="M"/>
    <entry ie="Encapsulated Document" name="Encapsulated Document" ref="C.24.2" usage="M"/>
    <entry ie="Encapsulated Document" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.46-1" name="Real World Value Mapping IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Real World Value Mapping Series" ref="C.25.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Real World Value Mapping" name="Real World Value Mapping" ref="C.25.2" usage="M"/>
    <entry ie="Real World Value Mapping" name="Common Instance Reference" ref="C.12.2" usage="M"/>
    <entry ie="Real World Value Mapping" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.47-1" name="Enhanced X Ray Angiographic Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="XA/XRF Series" ref="C.8.19.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="C - Required if C-arm Positioner Tabletop Relationship (0018,9474) equals YES. May be present otherwise."/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="C - Required if C-arm Positioner Tabletop Relationship (0018,9474) equals YES. May be present otherwise."/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Equipment" name="Enhanced General Equipment" ref="C.7.5.2" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Enhanced Contrast/Bolus" ref="C.7.6.4b" usage="C - Required if contrast media was applied and the system is able to register contrast usage."/>
    <entry ie="Image" name="Mask" ref="C.7.6.10" usage="U"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Intervention" ref="C.7.6.13" usage="U"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Multi-frame Functional Groups" ref="C.7.6.16" usage="M"/>
    <entry ie="Image" name="Multi-frame Dimension Module" ref="C.7.6.17" usage="U"/>
    <entry ie="Image" name="Cardiac Synchronization" ref="C.7.6.18.1" usage="C - Required if cardiac synchronization was applied."/>
    <entry ie="Image" name="Respiratory Synchronization" ref="C.7.6.18.2" usage="C - Required if respiratory synchronization was applied."/>
    <entry ie="Image" name="X-Ray Filtration" ref="C.8.7.10" usage="U"/>
    <entry ie="Image" name="X-Ray Grid" ref="C.8.7.11" usage="U"/>
    <entry ie="Image" name="Enhanced XA/XRF Image" ref="C.8.19.2" usage="M"/>
    <entry ie="Image" name="XA/XRF Acquisition" ref="C.8.19.3" usage="C - Required if Image Type (0008,0008) Value 1 equals ORIGINAL. May be present otherwise."/>
    <entry ie="Image" name="X-Ray Image Intensifier" ref="C.8.19.4" usage="C - Required if X-Ray Receptor Type (0018,9420) is present and equals IMG_INTENSIFIER."/>
    <entry ie="Image" name="X-Ray Detector" ref="C.8.19.5" usage="C - Required if X-Ray Receptor Type (0018,9420) is present and equals DIGITAL_DETECTOR."/>
    <entry ie="Image" name="XA/XRF Multi-frame Presentation" ref="C.8.19.7" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.48.-1" name="Enhanced X Ray RF Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="XA/XRF Series" ref="C.8.19.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="U"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Equipment" name="Enhanced General Equipment" ref="C.7.5.2" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Enhanced Contrast/Bolus" ref="C.7.6.4b" usage="C - Required if contrast media was applied and the system is able to register contrast usage."/>
    <entry ie="Image" name="Mask" ref="C.7.6.10" usage="U"/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Intervention" ref="C.7.6.13" usage="U"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Multi-frame Functional Groups" ref="C.7.6.16" usage="M"/>
    <entry ie="Image" name="Multi-frame Dimension Module" ref="C.7.6.17" usage="U"/>
    <entry ie="Image" name="Cardiac Synchronization" ref="C.7.6.18.1" usage="C - Required if cardiac synchronization was applied."/>
    <entry ie="Image" name="Respiratory Synchronization" ref="C.7.6.18.2" usage="C - Required if respiratory synchronization was applied."/>
    <entry ie="Image" name="X-Ray Tomography Acquisition" ref="C.8.7.7" usage="U"/>
    <entry ie="Image" name="X-Ray Filtration" ref="C.8.7.10" usage="U"/>
    <entry ie="Image" name="X-Ray Grid" ref="C.8.7.11" usage="U"/>
    <entry ie="Image" name="Enhanced XA/XRF Image" ref="C.8.19.2" usage="M"/>
    <entry ie="Image" name="XA/XRF Acquisition" ref="C.8.19.3" usage="C - Required if Image Type (0008,0008) Value 1 equals ORIGINAL. May be present otherwise."/>
    <entry ie="Image" name="X-Ray Image Intensifier" ref="C.8.19.4" usage="C - Required if X-Ray Receptor Type (0018,9420) is present and equals IMG_INTENSIFIER."/>
    <entry ie="Image" name="X-Ray Detector" ref="C.8.19.5" usage="C - Required if X-Ray Receptor Type (0018,9420) is present and equals DIGITAL_DETECTOR."/>
    <entry ie="Image" name="XA/XRF Multi-frame Presentation" ref="C.8.19.7" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.49-1" name="RT Ion Plan IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="RT Series" ref="C.8.8.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Plan" name="RT General Plan" ref="C.8.8.9" usage="M"/>
    <entry ie="Plan" name="RT Prescription" ref="C.8.8.10" usage="U"/>
    <entry ie="Plan" name="RT Ion Tolerance Tables" ref="C.8.8.24" usage="U"/>
    <entry ie="Plan" name="RT Patient Setup" ref="C.8.8.12" usage="U"/>
    <entry ie="Plan" name="RT Fraction Scheme" ref="C.8.8.13" usage="U"/>
    <entry ie="Plan" name="RT Ion Beams" ref="C.8.8.25" usage="C - Required if RT Fraction Scheme Module is included and Number of Beams (300A,0080) is greater than zero for one or more fraction groups"/>
    <entry ie="Plan" name="Approval" ref="C.8.8.16" usage="U"/>
    <entry ie="Plan" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.50-1" name="RT Ion Beams Treatment Record IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Series" name="RT Series" ref="C.8.8.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Treatment Record" name="RT General Treatment Record" ref="C.8.8.17" usage="M"/>
    <entry ie="Treatment Record" name="RT Patient Setup" ref="C.8.8.12" usage="U"/>
    <entry ie="Treatment Record" name="RT Treatment Machine Record" ref="C.8.8.18" usage="M"/>
    <entry ie="Treatment Record" name="Measured Dose Reference Record" ref="C.8.8.19" usage="U"/>
    <entry ie="Treatment Record" name="Calculated Dose Reference Record" ref="C.8.8.20" usage="U"/>
    <entry ie="Treatment Record" name="RT Ion Beams Session Record" ref="C.8.8.26" usage="M"/>
    <entry ie="Treatment Record" name="RT Treatment Summary Record" ref="C.8.8.23" usage="U"/>
    <entry ie="Treatment Record" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.51-1" name="Segmentation IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Specimen Identification" ref="C.7.1.2" usage="U"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Segmentation Series" ref="C.8.20.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="C - Required if Derivation Image Functional Group (C.7.16.2.6) is not present."/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Equipment" name="Enhanced General Equipment" ref="C.7.5.2" usage="M"/>
    <entry ie="Segmentation" name="General Image" ref="C.7.6.1" usage="M"/>
    <entry ie="Segmentation" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Segmentation" name="Segmentation Image" ref="C.8.20.2" usage="M"/>
    <entry ie="Segmentation" name="Multi-frame Functional Groups" ref="C.7.6.16" usage="M"/>
    <entry ie="Segmentation" name="Multi-frame Dimension" ref="C.7.6.17" usage="M"/>
    <entry ie="Segmentation" name="Common Instance Reference" ref="C.12.2" usage="C - Required if Derivation Image Functional Group (C.7.16.2.6) is present."/>
    <entry ie="Segmentation" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.52.3-1" name="Ophthalmic Tomography Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Ophthalmic Tomography Series" ref="C.8.17.6" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="C - Required if Ophthalmic Photography Reference Image available"/>
    <entry ie="Frame of Reference" name="Synchronization" ref="C.7.4.2" usage="C - Required if Ophthalmic Photography Reference Image available"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Equipment" name="Enhanced General Equipment" ref="C.7.5.2" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Enhanced Contrast/Bolus" ref="C.7.6.4b" usage="C - Required if contrast was administered"/>
    <entry ie="Image" name="Multi-frame Functional Groups" ref="C.7.6.16" usage="M"/>
    <entry ie="Image" name="Multi-frame Dimension" ref="C.7.6.17" usage="M"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Cardiac Synchronization" ref="C.7.6.18.1" usage="C - Required if cardiac synchronization was used"/>
    <entry ie="Image" name="Ophthalmic Tomography Image" ref="C.8.17.7" usage="M"/>
    <entry ie="Image" name="Ophthalmic Tomography Acquisition Parameters" ref="C.8.17.8" usage="M"/>
    <entry ie="Image" name="Ophthalmic Tomography Parameters" ref="C.8.17.9" usage="M"/>
    <entry ie="Image" name="Ocular Region Imaged" ref="C.8.17.5" usage="M"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.53-1" name="X Ray 3D Angiographic Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Enhanced Series" ref="C.7.3.3" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Equipment" name="Enhanced General Equipment" ref="C.7.5.2" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Enhanced Contrast/Bolus" ref="C.7.6.4b" usage="C - Required if contrast media was applied."/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Intervention" ref="C.7.6.13" usage="U"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Multi-frame Functional Groups" ref="C.7.6.16" usage="M"/>
    <entry ie="Image" name="Multi-frame Dimension" ref="C.7.6.17" usage="U"/>
    <entry ie="Image" name="Cardiac Synchronization" ref="C.7.6.18.1" usage="C - Required if cardiac synchronization was applied."/>
    <entry ie="Image" name="Respiratory Synchronization" ref="C.7.6.18.2" usage="C - Required if respiratory synchronization was applied."/>
    <entry ie="Image" name="Patient Orientation" ref="C.7.6.20" usage="U"/>
    <entry ie="Image" name="Image – Equipment Coordinate Relationship" ref="C.7.6.21" usage="U"/>
    <entry ie="Image" name="X-Ray 3D Image" ref="C.8.21.1" usage="M"/>
    <entry ie="Image" name="X-Ray 3D Angiographic Image Contributing Sources" ref="C.8.21.2.1" usage="U"/>
    <entry ie="Image" name="X-Ray 3D Angiographic Acquisition" ref="C.8.21.3.2" usage="U"/>
    <entry ie="Image" name="X-Ray 3D Reconstruction" ref="C.8.21.4" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="A.54-1" name="X Ray 3D Craniofacial Image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Patient" name="Clinical Trial Subject" ref="C.7.1.3" usage="U"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Study" name="Clinical Trial Study" ref="C.7.2.3" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Series" name="Clinical Trial Series" ref="C.7.3.2" usage="U"/>
    <entry ie="Series" name="Enhanced Series" ref="C.7.3.3" usage="M"/>
    <entry ie="Frame of Reference" name="Frame of Reference" ref="C.7.4.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="M"/>
    <entry ie="Equipment" name="Enhanced General Equipment" ref="C.7.5.2" usage="M"/>
    <entry ie="Image" name="Image Pixel" ref="C.7.6.3" usage="M"/>
    <entry ie="Image" name="Enhanced Contrast/Bolus" ref="C.7.6.4b" usage="C - Required if contrast media was applied."/>
    <entry ie="Image" name="Device" ref="C.7.6.12" usage="U"/>
    <entry ie="Image" name="Intervention" ref="C.7.6.13" usage="U"/>
    <entry ie="Image" name="Acquisition Context" ref="C.7.6.14" usage="M"/>
    <entry ie="Image" name="Multi-frame Functional Groups" ref="C.7.6.16" usage="M"/>
    <entry ie="Image" name="Multi-frame Dimension" ref="C.7.6.17" usage="U"/>
    <entry ie="Image" name="Patient Orientation" ref="C.7.6.20" usage="U"/>
    <entry ie="Image" name="Image – Equipment Coordinate Relationship" ref="C.7.6.21" usage="U"/>
    <entry ie="Image" name="X-Ray 3D Image" ref="C.8.21.1" usage="M"/>
    <entry ie="Image" name="X-Ray 3D Craniofacial Image Contributing Sources" ref="C.8.21.2.2" usage="U"/>
    <entry ie="Image" name="X-Ray 3D Craniofacial Acquisition" ref="C.8.21.3.3" usage="U"/>
    <entry ie="Image" name="X-Ray 3D Reconstruction" ref="C.8.21.4" usage="U"/>
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <iod table="B.7-1" name="Film Session IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP Common information"/>
    <entry name="Basic Film Session Presentation" ref="C.13.1" description="Contains Film Session presentations information"/>
    <entry name="Basic Film Session Relationship" ref="C.13.2" description="References to related SOPs"/>
  </iod>
  <iod table="B.8-1" name="Basic Film Box IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP Common information"/>
    <entry name="Basic Film Box Presentation Module" ref="C.13.3" description="Contains Film Box presentation information"/>
    <entry name="Basic Film Box Relationship" ref="C.13.4" description="References to related SOPs"/>
  </iod>
  <iod table="B.9-1" name="Basic Image Box IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP Common information"/>
    <entry name="Image Box Presentation Module" ref="C.13.5" description="Contains Image Box presentation information"/>
  </iod>
  <iod table="B.10-1" name="Basic Annotation Box IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP Common information"/>
    <entry name="Basic Annotation Presentation Module" ref="C.13.7" description="Contains annotation presentation information"/>
  </iod>
  <iod table="B.11-1" name="Print Job IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP Common information"/>
    <entry name="Print Job Module" ref="C.13.8" description="Contains print job transaction information"/>
  </iod>
  <iod table="B.12-1" name="Printer IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP Common information"/>
    <entry name="Printer Module" ref="C.13.9" description="Contains status information to monitor the printer"/>
  </iod>
  <iod table="B.15-1" name="Storage Commitment IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP common information"/>
    <entry name="Storage Commitment" ref="C.14" description="Contains references to the SOP Instances and associated information that are contained in Storage Commitment."/>
  </iod>
  <iod table="B.17.2-1" name="Modality Performed Procedure Step IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP common information"/>
    <entry name="Performed Procedure Step Relationship" ref="C.4.13" description="References the related SOPs and IEs."/>
    <entry name="Performed Procedure Step Information" ref="C.4.14" description="Includes identifying and status information as well as place and time"/>
    <entry name="Image Acquisition Results" ref="C.4.15" description="Identifies Series and Images related to this PPS and specific image acquisition conditions."/>
    <entry name="Radiation Dose" ref="C.4.16" description="Contains radiation dose information related to this Performed Procedure Step."/>
    <entry name="Billing and Material Management Codes" ref="C.4.17" description="Contains codes for billing and material management."/>
  </iod>
  <iod table="B.18.2" name="IOD Modules">
    <entry name="SOP Common Information" ref="C.12.1"/>
    <entry name="Presentation LUT Module" ref="C.11.4"/>
  </iod>
  <iod table="B.20-1" name="Printer Configuration IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP Common Information"/>
    <entry name="Printer" ref="C.13.9" description="Contains information about the printer"/>
    <entry name="Printer Configuration" ref="C.13.13" description="Contains Printer Configuration Information"/>
  </iod>
  <iod table="B.22.2-1" name="General Purpose Scheduled Procedure Step IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP common information"/>
    <entry name="General Purpose Scheduled Procedure Step Relationship" ref="C.4.18" description="References the related SOPs and IEs."/>
    <entry name="General Purpose Scheduled Procedure Step Information" ref="C.4.19" description="Includes identifying and status information as well as place and time"/>
  </iod>
  <iod table="B.23.2-1" name="General Purpose Performed Procedure Step IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP common information"/>
    <entry name="General Purpose Performed Procedure Step Relationship" ref="C.4.20" description="References the related SOPs and IEs."/>
    <entry name="General Purpose Performed Procedure Step Information" ref="C.4.21" description="Includes identifying and status information as well as place and time"/>
    <entry name="General Purpose Results" ref="C.4.22" description="Identifies Results related to this GP-PPS."/>
  </iod>
  <iod table="B.24.2-1" name="Instance Availability Notification IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP common information"/>
    <entry name="Instance Availability Notification" ref="C.4.23" description="References the related SOPs and IEs."/>
  </iod>
  <iod table="B.25.2-1" name="Media Creation Management IOD Modules">
    <entry name="SOP Common" ref="C.12.1" description="Contains SOP common information"/>
    <entry name="Media Creation Management" ref="C.22.1" description="Contains references to the SOP instances to be used for this media creation request, and the information about its status."/>
  </iod>
<!--
http://www.medical.siemens.com/siemens/en_GLOBAL/rg_marcom_FBAs/files/brochures/DICOM/multimod_worpl/aMMWP_2006B/VSim_DicomConformanceStatement.pdf
-->
  <iod table="CSA.1" name="Siemens Non-image IOD Modules">
    <entry ie="Patient" name="Patient" ref="C.7.1.1" usage="M"/>
    <entry ie="Study" name="General Study" ref="C.7.2.1" usage="M"/>
    <entry ie="Study" name="Patient Study" ref="C.7.2.2" usage="U"/>
    <entry ie="Series" name="General Series" ref="C.7.3.1" usage="M"/>
    <entry ie="Equipment" name="General Equipment" ref="C.7.5.1" usage="U"/>
<!--
    <entry ie="CSA" name="CSA Image Header" ref="CSA.A.2.1" usage="U"/>
    <entry ie="CSA" name="CSA Series Header" ref="CSA.A.2.2" usage="U"/>
    <entry ie="CSA" name="MEDCOM Header" ref="CSA.A.2.3" usage="U"/>
    <entry ie="CSA" name="CSA Non-Image" ref="CSA.A.1.3.1" usage="M"/>
    <entry ie="CSA" name="SOP Common" ref="C.12.1" usage="M"/>
-->
    <entry ie="Image" name="SOP Common" ref="C.12.1" usage="M"/>
  </iod>
  <module ref="C.2.1" table="C.2-1" name="Patient Relationship Module Attributes">
    <entry group="0008" element="1110" name="Referenced Study Sequence">
      <description>Uniquely identifies the Study SOP Instances associated with the Patient SOP Instance. One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0008" element="1125" name="Referenced Visit Sequence">
      <description>Uniquely identifies the Visit SOP Instances associated with this Patient SOP Instance. One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0038" element="0004" name="Referenced Patient Alias Sequence">
      <description>Uniquely identifies any Patient SOP Instances that also describe this patient. These SOP Instances are aliases. Zero or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.2.2" table="C.2-2" name="Patient Identification Module Attributes">
    <entry group="0010" element="0010" name="Patient's Name">
      <description>Patient's full name</description>
    </entry>
    <entry group="0010" element="0020" name="Patient ID">
      <description>Primary hospital identification number or code for the patient.</description>
    </entry>
    <entry group="0010" element="0021" name="Issuer of Patient ID">
      <description>Identifier of the Assigning Authority (system, organization, agency, or department) that issued the Patient ID.
Note: Issuer of Patient ID (0010,0021) is equivalent to HL7 v2 PID-3 component 4.</description>
    </entry>
    <entry group="0010" element="1000" name="Other Patient IDs">
      <description>Other identification numbers or codes used to identify the patient.</description>
    </entry>
    <entry group="0010" element="1002" name="Other Patient IDs Sequence">
      <description>A sequence of identification numbers or codes used to identify the patient, which may or may not be human readable, and may or may not have been obtained from an implanted or attached device such as an RFID or barcode.</description>
    </entry>
    <entry group="0010" element="0020" name="&gt;Patient ID">
      <description>An identification number or code used to identify the patient</description>
    </entry>
    <entry group="0010" element="0021" name="&gt;Issuer of Patient ID">
      <description>Identifier of the Assigning Authority that issued the Patient ID.</description>
    </entry>
    <entry group="0010" element="0022" name="&gt;Type of Patient ID">
      <description>The type of identifier in this item. Defined Terms:
TEXT
RFID
BARCODE
Note: The identifier is coded as a string regardless of the type, not as a binary value.</description>
    </entry>
    <entry group="0010" element="1001" name="Other Patient Names">
      <description>Other names used to identify the patient.</description>
    </entry>
    <entry group="0010" element="1005" name="Patient's Birth Name">
      <description>Patient's birth name.</description>
    </entry>
    <entry group="0010" element="1060" name="Patient's Mother's Birth Name">
      <description>Birth name of patient's mother.</description>
    </entry>
    <entry group="0010" element="1090" name="Medical Record Locator">
      <description>An identifier used to find the patient's existing medical record (e.g. film jacket).</description>
    </entry>
  </module>
  <module ref="C.2.3" table="C.2-3" name="Patient Demographic Module Attributes">
    <entry group="0010" element="1010" name="Patient's Age">
      <description>Age of the Patient.</description>
    </entry>
    <entry group="0010" element="2180" name="Occupation">
      <description>Occupation of the Patient.</description>
    </entry>
    <entry group="0040" element="3001" name="Confidentiality Constraint on Patient Data Description">
      <description>Special indication to the modality operator about confidentiality of patient information (e.g., that he should not use the patients name where other patients are present).</description>
    </entry>
    <entry group="0010" element="0030" name="Patient's Birth Date">
      <description>Date of birth of the named patient</description>
    </entry>
    <entry group="0010" element="0032" name="Patient's Birth Time">
      <description>Time of birth of the named patient</description>
    </entry>
    <entry group="0010" element="0040" name="Patient's Sex">
      <description>Sex of the named patient. Enumerated Values:
M = male
F = female
O = other</description>
    </entry>
    <entry group="0010" element="0050" name="Patient's Insurance Plan Code Sequence">
      <description>A sequence that conveys the patient's insurance plan. Zero or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0010" element="0101" name="Patient's Primary Language Code Sequence">
      <description>The languages that can be used to communicate with the patient.
Zero or more Items may be included in the sequence. The sequence items are ordered by preference (most preferred language to least preferred language).</description>
    </entry>
    <include ref="&gt; Include Code Sequence Macro Table 8.8-1" description="Baseline Context ID is CID 5000 - Languages."/>
    <entry group="0010" element="0102" name="&gt; Patient's Primary Language Code Modifier Sequence">
      <description>A modifer for a Patient's Primary Language. Can be used to specify a national language variant.
Exactly one Item may be included in the sequence.</description>
    </entry>
    <include ref="&gt;&gt; Include Code Sequence Macro Table 8.8-1" description="Baseline Context ID is CID 5001 - Countries."/>
    <entry group="0010" element="1020" name="Patient's Size">
      <description>Patient's height or length in meters</description>
    </entry>
    <entry group="0010" element="1030" name="Patient's Weight">
      <description>Weight of the patient in kilograms</description>
    </entry>
    <entry group="0010" element="1040" name="Patient's Address">
      <description>Legal address of the named patient</description>
    </entry>
    <entry group="0010" element="1080" name="Military Rank">
      <description>Military rank of patient</description>
    </entry>
    <entry group="0010" element="1081" name="Branch of Service">
      <description>Branch of the military. The country allegiance may also be included (e.g. U.S. Army).</description>
    </entry>
    <entry group="0010" element="2150" name="Country of Residence">
      <description>Country in which patient currently resides</description>
    </entry>
    <entry group="0010" element="2152" name="Region of Residence">
      <description>Region within patient's country of residence</description>
    </entry>
    <entry group="0010" element="2154" name="Patient's Telephone Numbers">
      <description>Telephone numbers at which the patient can be reached</description>
    </entry>
    <entry group="0010" element="2160" name="Ethnic Group">
      <description>Ethnic group or race of patient</description>
    </entry>
    <entry group="0010" element="21F0" name="Patient's Religious Preference">
      <description>The religious preference of the patient</description>
    </entry>
    <entry group="0010" element="4000" name="Patient Comments">
      <description>User-defined comments about the patient</description>
    </entry>
    <entry group="0010" element="2297" name="Responsible Person">
      <description>Name of person with medical decision making authority for the patient.</description>
    </entry>
    <entry group="0010" element="2298" name="Responsible Person Role">
      <description>Relationship of Responsible Person to the patient.
Defined Terms:
OWNER</description>
    </entry>
    <entry group="0010" element="2299" name="Responsible Organization">
      <description>Name of organization with medical decision making authority for the patient.</description>
    </entry>
    <entry group="0010" element="2201" name="Patient Species Description">
      <description>The species of the patient.</description>
    </entry>
    <entry group="0010" element="2202" name="Patient Species Code Sequence">
      <description>The species of the patient.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-2" description="Defined Context ID is 7454."/>
    <entry group="0010" element="2292" name="Patient Breed Description">
      <description>The breed of the patient.</description>
    </entry>
    <entry group="0010" element="2293" name="Patient Breed Code Sequence">
      <description>The breed of the patient.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-2" description="Defined Context ID is 7480."/>
    <entry group="0010" element="2294" name="Breed Registration Sequence">
      <description>Information identifying an animal within a breed registry.</description>
    </entry>
    <entry group="0010" element="2295" name="&gt;Breed Registration Number">
      <description>Identification number of a veterinary patient within the registry.</description>
    </entry>
    <entry group="0010" element="2296" name="&gt;Breed Registry Code Sequence">
      <description>Identification of the organization with which an animal is registered.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 7481."/>
  </module>
  <module ref="C.2.4" table="C.2-4" name="Patient Medical Module Attributes">
    <entry group="0010" element="2000" name="Medical Alerts">
      <description>Conditions to which medical staff should be alerted (e.g. contagious condition, drug allergies, etc.)</description>
    </entry>
    <entry group="0010" element="2110" name="Allergies">
      <description>Description of prior reaction to contrast agents, or other patient allergies or adverse reactions.</description>
    </entry>
    <entry group="0010" element="21A0" name="Smoking Status">
      <description>Indicates whether patient smokes.
Enumerated Values:
YES
NO
UNKNOWN</description>
    </entry>
    <entry group="0010" element="21B0" name="Additional Patient History">
      <description>Additional information about the patient's medical history</description>
    </entry>
    <entry group="0010" element="21C0" name="Pregnancy Status">
      <description>Describes pregnancy state of patient.
Enumerated Values:
0001 = not pregnant
0002 = possibly pregnant
0003 = definitely pregnant
0004 = unknown</description>
    </entry>
    <entry group="0010" element="21D0" name="Last Menstrual Date">
      <description>Date of onset of last menstrual period</description>
    </entry>
    <entry group="0010" element="2203" name="Patient's Sex Neutered">
      <description>Whether or not a procedure has been performed in an effort to render the patient sterile.
Enumerated value:
ALTERED = Altered/Neutered
UNALTERED = Unaltered/intact</description>
    </entry>
    <entry group="0038" element="0050" name="Special Needs">
      <description>Medical and social needs (e.g. wheelchair, oxygen, translator, etc.)</description>
    </entry>
    <entry group="0038" element="0500" name="Patient State">
      <description>Description of patient state (comatose, disoriented, vision impaired, etc.)</description>
    </entry>
    <entry group="0038" element="0100" name="Pertinent Documents Sequence">
      <description>List of Documents (e.g., SR, or CDA) that contain information considered pertinent for the patient medical condition.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence">
      <description>Describes the purpose for which the document reference is made. Zero or more Items may be present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context Group ID defined"/>
    <entry group="0042" element="0010" name="&gt;Document Title">
      <description>Title of the referenced document.</description>
    </entry>
    <entry group="0038" element="0502" name="Patient Clinical Trial Participation Sequence">
      <description>Sequence of identifiers for clinical trials in which the patient participates.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0012" element="0010" name="&gt;Clinical Trial Sponsor Name">
      <description>The name of the clinical trial sponsor, responsible for conducting the clinical trial and for defining the Clinical Trial Protocol.</description>
    </entry>
    <entry group="0012" element="0020" name="&gt;Clinical Trial Protocol ID">
      <description>Identifier for the noted protocol, used by the Clinical Trial Sponsor to uniquely identify the investigational protocol.</description>
    </entry>
    <entry group="0012" element="0021" name="&gt;Clinical Trial Protocol Name">
      <description>The name or title of the clinical trial protocol.</description>
    </entry>
    <entry group="0012" element="0030" name="&gt;Clinical Trial Site ID">
      <description>The identifier, issued by the Clinical Trial Sponsor, of the site responsible for submitting clinical trial data.</description>
    </entry>
    <entry group="0012" element="0031" name="&gt;Clinical Trial Site Name">
      <description>Name of the site responsible for submitting clinical trial data.</description>
    </entry>
    <entry group="0012" element="0040" name="&gt;Clinical Trial Subject ID">
      <description>The assigned identifier for the patient as a clinical trial subject.</description>
    </entry>
    <entry group="0012" element="0042" name="&gt;Clinical Trial Subject Reading ID">
      <description>Identifies the patient as a clinical trial subject for blinded evaluations.</description>
    </entry>
  </module>
  <module ref="C.3.1" table="C.3-1" name="Visit Relationship Module Attributes">
    <entry group="0008" element="1110" name="Referenced Study Sequence">
      <description>Uniquely identifies the Study SOP Instances associated with the Visit SOP Instance. One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0008" element="1120" name="Referenced Patient Sequence">
      <description>Uniquely identifies the Patient SOP Instance that relates to the Visit SOP Instance. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.3.2" table="C.3-2" name="Visit Identification Module Attributes">
    <entry group="0008" element="0080" name="Institution Name">
      <description>Institution where the equipment is located</description>
    </entry>
    <entry group="0008" element="0081" name="Institution Address">
      <description>Mailing Address of the institution where the equipment is located</description>
    </entry>
    <entry group="0008" element="0082" name="Institution Code Sequence">
      <description>A sequence that conveys the healthcare facility identification. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0038" element="0010" name="Admission ID">
      <description>Identification number of the visit as assigned by the healthcare provider</description>
    </entry>
    <entry group="0038" element="0011" name="Issuer of Admission ID">
      <description>Name of healthcare provider which issued the Admission ID</description>
    </entry>
    <entry group="0038" element="0060" name="Service Episode ID">
      <description>Identifier of the Service Episode as assigned by the healthcare provider</description>
    </entry>
    <entry group="0038" element="0061" name="Issuer of Service Episode ID">
      <description>Name of healthcare provider that issued the Service Episode ID</description>
    </entry>
    <entry group="0038" element="0062" name="Service Episode Description">
      <description>Description of the type of service episode.</description>
    </entry>
  </module>
  <module ref="C.3.3" table="C.3-3" name="Visit Status Module Attributes">
    <entry group="0038" element="0008" name="Visit Status ID">
      <description>Identifies the state of the visit. Defined Terms:
CREATED = Created but not yet scheduled
SCHEDULED = Scheduled but not yet admitted
ADMITTED = Patient admitted to institution
DISCHARGED = Patient Discharged</description>
    </entry>
    <entry group="0038" element="0300" name="Current Patient Location">
      <description>Describes the current known location of the patient</description>
    </entry>
    <entry group="0038" element="0400" name="Patient's Institution Residence">
      <description>Primary location where patient resides (ward, floor, room, etc. or outpatient)</description>
    </entry>
    <entry group="0038" element="4000" name="Visit Comments">
      <description>User-defined comments about the visit</description>
    </entry>
  </module>
  <module ref="C.3.4" table="C.3-4" name="Visit Admission Module Attributes">
    <entry group="0008" element="0090" name="Referring Physician's Name">
      <description>Patient's primary referring physician for this visit</description>
    </entry>
    <entry group="0008" element="0092" name="Referring Physician's Address">
      <description>Referring physician's address</description>
    </entry>
    <entry group="0008" element="0094" name="Referring Physician's Telephone Numbers">
      <description>Referring physician's telephone numbers</description>
    </entry>
    <entry group="0008" element="0096" name="Referring Physician Identification Sequence">
      <description>Identification of the patient's referring physician. Only a single item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Person Identification Macro' Table 10-1"/>
    <entry group="0008" element="1080" name="Admitting Diagnoses Description">
      <description>Description of admitting diagnosis (diagnoses).</description>
    </entry>
    <entry group="0008" element="1084" name="Admitting Diagnoses Code Sequence">
      <description>A sequence that conveys the admitting diagnosis (diagnoses). One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0038" element="0016" name="Route of Admissions">
      <description>Mode of admission: emergency, normal</description>
    </entry>
    <entry group="0038" element="0020" name="Admitting Date">
      <description>Date patient visit began</description>
    </entry>
    <entry group="0038" element="0021" name="Admitting Time">
      <description>Time patient visit began</description>
    </entry>
  </module>
  <module ref="C.4.10" table="C.4-10" name="Scheduled Procedure Step Module Attributes">
    <entry group="0040" element="0100" name="Scheduled Procedure Step Sequence">
      <description>One or more Scheduled Procedure Steps for one Requested Procedure.</description>
    </entry>
    <entry group="0040" element="0001" name="&gt;Scheduled Station AE Title">
      <description>The AE title of the modality on which the Scheduled Procedure Step is scheduled to be performed.</description>
    </entry>
    <entry group="0040" element="0010" name="&gt;Scheduled Station Name">
      <description>An institution defined name for the modality on which the Scheduled Procedure Step is scheduled to be performed.</description>
    </entry>
    <entry group="0040" element="0011" name="&gt;Scheduled Procedure Step Location">
      <description>The location at which the Procedure Step is scheduled to be performed.</description>
    </entry>
    <entry group="0040" element="0002" name="&gt;Scheduled Procedure Step Start Date">
      <description>Date on which the Scheduled Procedure Step is scheduled to start.</description>
    </entry>
    <entry group="0040" element="0003" name="&gt;Scheduled Procedure Step Start Time">
      <description>Time at which the Scheduled Procedure Step is scheduled to start.</description>
    </entry>
    <entry group="0040" element="0004" name="&gt;Scheduled Procedure Step End Date">
      <description>Date on which the Scheduled Procedure Step is scheduled to end.</description>
    </entry>
    <entry group="0040" element="0005" name="&gt;Scheduled Procedure Step End Time">
      <description>Time at which the Scheduled Procedure Step is scheduled to end.</description>
    </entry>
    <entry group="0040" element="0006" name="&gt;Scheduled Performing Physician's Name">
      <description>Name of the physician scheduled to administer the Scheduled Procedure Step.</description>
    </entry>
    <entry group="0040" element="000B" name="&gt;Scheduled Performing Physician Identification Sequence">
      <description>Identification of the physician scheduled to administer the Scheduled Procedure Step. Only a single item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Person Identification Macro' Table 10-1"/>
    <entry group="0040" element="0007" name="&gt;Scheduled Procedure Step Description">
      <description>Institution-generated description or classification of the Scheduled Procedure Step to be performed.
Note: The purpose of this attribute is to store a description or classification that is used at a local level (e.g., a hospital or a managed care network), and this description need not comply to an accepted standard.</description>
    </entry>
    <entry group="0040" element="0008" name="&gt;Scheduled Protocol Code Sequence">
      <description>Sequence describing the Scheduled Protocol following a specified coding scheme. This sequence contains one or more Items.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="0440" name="&gt;&gt;Protocol Context Sequence">
      <description>Sequence that specifies the context for the Scheduled Protocol Code Sequence Item. One or more items may be included in this sequence. See Section C.4.10.1.</description>
      <section ref="C.4.10.1" name="">The Protocol Context Sequence (0040,0440) allows the specification of parameters that further qualify the scheduled protocol, provided through a set of generic name/value pairs of context Content Items.
Note:  This allows the specification of clinical, acquisition, or procedural qualifiers for the scheduled protocol, such as a specific body part, imaging technique, or parameters of a preparatory event (e.g., radionuclide injection). Specific uses of this Sequence may be documented in a Template defined in accordance with PS3.16.

</section>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Content Item Macro' Table 10-2" description="No Baseline Template is defined."/>
    <entry group="0040" element="0441" name="&gt;&gt;&gt; Content Item Modifier Sequence">
      <description>Sequence that specifies modifiers for a Protocol Context Content Item. One or more items may be included in this sequence. See Section C.4.10.1.</description>
      <section ref="C.4.10.1" name="">The Protocol Context Sequence (0040,0440) allows the specification of parameters that further qualify the scheduled protocol, provided through a set of generic name/value pairs of context Content Items.
Note:  This allows the specification of clinical, acquisition, or procedural qualifiers for the scheduled protocol, such as a specific body part, imaging technique, or parameters of a preparatory event (e.g., radionuclide injection). Specific uses of this Sequence may be documented in a Template defined in accordance with PS3.16.

</section>
    </entry>
    <include ref="&gt;&gt;&gt;&gt;Include 'Content Item Macro' Table 10-2" description="No Baseline Template is defined."/>
    <entry group="0040" element="0009" name="&gt;Scheduled Procedure Step ID">
      <description>Identifier that identifies the Scheduled Procedure Step.</description>
    </entry>
    <entry group="0040" element="0020" name="&gt;Scheduled Procedure Step Status">
      <description>A real world condition that may affect the selection of of the Scheduled Procedure Step. Defined Terms:
SCHEDULED - Procedure Step scheduled
ARRIVED - patient is available for the Scheduled Procedure Step
READY - all patient and other necessary preparation for this step has been completed
STARTED - at least one Performed Procedure Step has been created that references this Scheduled Procedure Step</description>
    </entry>
    <entry group="0040" element="0400" name="&gt;Comments on the Scheduled Procedure Step">
      <description>User-defined comments on the Scheduled Procedure Step.
Note: The Comments attribute is intended to transmit non-structured information, which can be displayed to the operator of the Modality.</description>
    </entry>
    <entry group="0008" element="0060" name="&gt;Modality">
      <description>Source equipment for the image. See Section C.7.3.1.1.1 for Defined Terms.</description>
      <section ref="C.7.3.1.1.1" name="">Defined Terms for the Modality (0008,0060) are:
<defined-terms><term value="CR" meaning="Computed Radiography"/><term value="MR" meaning="Magnetic Resonance"/><term value="US" meaning="Ultrasound"/><term value="BI" meaning="Biomagnetic imaging"/><term value="DD" meaning="Duplex Doppler"/><term value="ES" meaning="Endoscopy"/><term value=""/><term value="PT" meaning="Positron emission tomography (PET)"/><term value="ST" meaning="Single-photon emission computed tomography (SPECT)"/><term value="XA" meaning="X-Ray Angiography"/><term value="RTIMAGE" meaning="Radiotherapy Image"/><term value="RTSTRUCT" meaning="Radiotherapy Structure Set"/><term value="RTRECORD" meaning="RT Treatment Record"/><term value="DX" meaning="Digital Radiography"/><term value="IO" meaning="Intra-oral Radiography"/><term value="GM" meaning="General Microscopy"/><term value="XC" meaning="External-camera Photography"/><term value="AU" meaning="Audio"/><term value="EPS" meaning="Cardiac Electrophysiology"/><term value="SR" meaning="SR Document"/><term value="OP" meaning="Ophthalmic Photography"/><term value="OCT" meaning="Optical Coherence Tomography (non-Ophthalmic)"/><term value="OPV" meaning="Ophthalmic Visual Field"/><term value="KO" meaning="Key Object Selection"/><term value="REG" meaning="Registration"/><term value="BDUS" meaning="Bone Densitometry (ultrasound)"/><term value="DOC" meaning="Document"/></defined-terms>
Retired Defined Terms for the Modality (0008,0060) are:
<retired-defined-terms><term value="DS" meaning="Digital Subtraction Angiography (retired)"/><term value="DF" meaning="Digital fluoroscopy (retired)"/><term value="AS" meaning="Angioscopy"/><term value="EC" meaning="Echocardiography"/><term value="FA" meaning="Fluorescein angiography"/><term value="DM" meaning="Digital microscopy"/><term value="MA" meaning="Magnetic resonance angiography"/></retired-defined-terms>
Note:  1. The XA modality incorporates the retired modality DS.
  2. The RF modality incorporates the retired modalities CF, DF, VF.
  3. The modality listed in the Modality Data Element (0008,0060) may not match the name of the IOD in which it appears. For example, a SOP instance from XA IOD may list the RF modality when an RF implementation produces an XA object.
  4. The MR modality incorporates the retired modalities MA and MS.

</section>
    </entry>
    <entry group="0032" element="1070" name="&gt;Requested Contrast Agent">
      <description>Contrast agent requested for use in the Scheduled Procedure Step.</description>
    </entry>
    <entry group="0040" element="0012" name="&gt;Pre-Medication">
      <description>Medication to be administered at the beginning of the Scheduled Procedure Step, e.g. Nuclear Medicine radiopharmaceutical.</description>
    </entry>
  </module>
  <module ref="C.4.11" table="C.4-11" name="Requested Procedure Module Attributes">
    <entry group="0040" element="1001" name="Requested Procedure ID">
      <description>Identifier that identifies the Requested Procedure in the Imaging Service Request.</description>
    </entry>
    <entry group="0040" element="1002" name="Reason for the Requested Procedure">
      <description>Reason for requesting this imaging procedure.
Note: This reason is more specific to the requested procedure than the reason mentioned in the imaging service request (0040,2001).</description>
    </entry>
    <entry group="0040" element="1400" name="Requested Procedure Comments">
      <description>User-defined comments on the Requested Procedure.</description>
    </entry>
    <entry group="0040" element="100A" name="Reason for Requested Procedure Code Sequence">
      <description>Coded Reason for requesting this procedure.
One or more sequence items may be present.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0032" element="1064" name="Requested Procedure Code Sequence">
      <description>A sequence that conveys the Requested Procedure of one Procedure Type.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0020" element="000D" name="Study Instance UID">
      <description>Unique identifier to be used to identify the Study</description>
    </entry>
    <entry group="0008" element="0020" name="Study Date">
      <description>Date the Study started, if any previous procedure steps within the same study have already been performed.</description>
    </entry>
    <entry group="0008" element="0030" name="Study Time">
      <description>Time the Study started, if any previous procedure steps within the same study have already been performed.</description>
    </entry>
    <entry group="0008" element="1110" name="Referenced Study Sequence">
      <description>Uniquely identifies the Study SOP Instances associated with this SOP Instance.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0032" element="1060" name="Requested Procedure Description">
      <description>Institution-generated administrative description or classification of Requested Procedure</description>
    </entry>
    <entry group="0040" element="1003" name="Requested Procedure Priority">
      <description>Requested Procedure Type Urgency. Defined Terms:
STAT, HIGH, ROUTINE, MEDIUM, LOW</description>
    </entry>
    <entry group="0040" element="1004" name="Patient Transport Arrangements">
      <description>Mode of transportation of the patient to the location of examination.</description>
    </entry>
    <entry group="0040" element="1005" name="Requested Procedure Location">
      <description>Physical location at which the Requested Procedure is to be performed.</description>
    </entry>
    <entry group="0040" element="1008" name="Confidentiality Code">
      <description>Confidentiality Constraints on the Requested Procedure by the party filling the order.</description>
    </entry>
    <entry group="0040" element="1009" name="Reporting Priority">
      <description>Requested Reporting Priority. Defined Terms:
HIGH, ROUTINE, MEDIUM, LOW</description>
    </entry>
    <entry group="0040" element="1010" name="Names of Intended Recipients of Results">
      <description>Names of the physicians, who are intended recipients of results.</description>
    </entry>
    <entry group="0040" element="1011" name="Intended Recipients of Results Identification Sequence">
      <description>Identification of the physicians who are intended recipients of results. One or more items shall be included in this sequence. If more than one Item, the number and order shall correspond to the value of Names of Intended Recipients of Results (0040,1010), if present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Person Identification Macro' Table 10-1"/>
  </module>
  <module ref="C.4.12" table="C.4-12" name="Imaging Service Request Module Attributes">
    <entry group="0040" element="2400" name="Imaging Service Request Comments">
      <description>User-defined comments on the Imaging Service Request.
Note: The Comments attribute is intended to transmit non-structured information, which can be displayed to the operator of the equipment (e.g. Modality).</description>
    </entry>
    <entry group="0032" element="1032" name="Requesting Physician">
      <description>Name of the physician who requested the Imaging Service Request.</description>
    </entry>
    <entry group="0032" element="1031" name="Requesting Physician Identification Sequence">
      <description>Identification of the physician who requested the Imaging Service Request. Only a single item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Person Identification Macro' Table 10-1"/>
    <entry group="0008" element="0090" name="Referring Physician's Name">
      <description>Name of the patient's referring physician for this Imaging Service Request.</description>
    </entry>
    <entry group="0008" element="0096" name="Referring Physician Identification Sequence">
      <description>Identification of the patient's referring physician. Only a single item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Person Identification Macro' Table 10-1"/>
    <entry group="0032" element="1033" name="Requesting Service">
      <description>Institutional department where the request initiated.</description>
    </entry>
    <entry group="0008" element="0050" name="Accession Number">
      <description>A departmental IS generated number that identifies the order for the Imaging Service Request.</description>
    </entry>
    <entry group="0040" element="2004" name="Issue Date of Imaging Service Request">
      <description>Date on which the Imaging Service Request was issued by the requester.</description>
    </entry>
    <entry group="0040" element="2005" name="Issue Time of Imaging Service Request">
      <description>Time at which the Imaging Service Request was issued by the requester.</description>
    </entry>
    <entry group="0040" element="2016" name="Placer Order Number / Imaging Service Request">
      <description>The order number assigned to the Imaging Service Request by the party placing the order.</description>
    </entry>
    <entry group="0040" element="2017" name="Filler Order Number / Imaging Service Request">
      <description>The order number assigned to the Imaging Service Request by the party filling the order.</description>
    </entry>
    <entry group="0040" element="2008" name="Order entered by ...">
      <description>The person who entered the Imaging Service Request into an Information System.</description>
    </entry>
    <entry group="0040" element="2009" name="Order Enterer's Location">
      <description>The location at which the Imaging Service Request was entered.</description>
    </entry>
    <entry group="0040" element="2010" name="Order Callback Phone Number">
      <description>Telephone Number at which additional information can be retrieved.</description>
    </entry>
    <entry group="0038" element="0010" name="Admission ID">
      <description>Identification number of the visit as assigned by the healthcare provider</description>
    </entry>
    <entry group="0038" element="0011" name="Issuer of Admission ID">
      <description>Name of healthcare provider that issued the Admission ID</description>
    </entry>
  </module>
  <module ref="C.4.13" table="C.4-13" name="Performed Procedure Step Relationship Module Attributes">
    <entry group="0010" element="0010" name="Patient's Name">
      <description>Patient's full legal name.</description>
    </entry>
    <entry group="0010" element="0020" name="Patient ID">
      <description>Primary hospital identification number or code for the patient.</description>
    </entry>
    <entry group="0010" element="0021" name="Issuer of Patient ID">
      <description>Identifier of the Assigning Authority that issued the Patient ID.</description>
    </entry>
    <entry group="0010" element="0030" name="Patient's Birth Date">
      <description>Date of birth of the named patient</description>
    </entry>
    <entry group="0010" element="0040" name="Patient's Sex">
      <description>Sex of the named Patient. Enumerated Values:
M = male
F = female
O = other</description>
    </entry>
    <entry group="0008" element="1120" name="Referenced Patient Sequence">
      <description>Uniquely identifies the Patient SOP Instance.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0038" element="0060" name="Service Episode ID">
      <description>Identifier of the Service Episode as assigned by the healthcare provider</description>
    </entry>
    <entry group="0038" element="0061" name="Issuer of Service Episode ID">
      <description>Name of healthcare provider that issued the Service Episode ID</description>
    </entry>
    <entry group="0038" element="0062" name="Service Episode Description">
      <description>Description of the type of service episode.</description>
    </entry>
    <entry group="0040" element="0270" name="Scheduled Step Attributes Sequence">
      <description>Sequence containing attributes that are related to the scheduling of the Procedure Step. The Sequence may have one or more Items.</description>
    </entry>
    <entry group="0020" element="000D" name="&gt;Study Instance UID">
      <description>Unique identifier for the Study.</description>
    </entry>
    <entry group="0008" element="1110" name="&gt;Referenced Study Sequence">
      <description>Uniquely identifies the Study SOP Instance associated with this Scheduled Procedure Step. This Sequence shall have only one Item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0008" element="0050" name="&gt;Accession Number">
      <description>A departmental IS generated number that identifies the order for the Study.</description>
    </entry>
    <entry group="0040" element="2016" name="&gt;Placer Order Number/Imaging Service Request">
      <description>The order number assigned to the Imaging Service Request by the party placing the order.</description>
    </entry>
    <entry group="0040" element="2017" name="&gt;Filler Order Number/Imaging Service Request">
      <description>The order number assigned to the Imaging Service Request by the party filling the order.</description>
    </entry>
    <entry group="0040" element="1001" name="&gt;Requested Procedure ID">
      <description>Identifier of the related Requested Procedure.</description>
    </entry>
    <entry group="0032" element="1060" name="&gt;Requested Procedure Description">
      <description>Institution-generated administrative description or classification of Requested Procedure.</description>
    </entry>
    <entry group="0032" element="1064" name="&gt;Requested Procedure Code Sequence">
      <description>A sequence that conveys the Procedure Type of the requested procedure. The Requested Procedure Code Sequence shall contain only a single item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="0009" name="&gt;Scheduled Procedure Step ID">
      <description>Identifier of the related Scheduled Procedure Step.</description>
    </entry>
    <entry group="0040" element="0007" name="&gt;Scheduled Procedure Step Description">
      <description>Institution-generated description or classification of the Scheduled Procedure Step to be performed.</description>
    </entry>
    <entry group="0040" element="0008" name="&gt;Scheduled Protocol Code Sequence">
      <description>Sequence describing the Scheduled Protocol following a specific coding scheme. This sequence contains one or more Items.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="0440" name="&gt;&gt;Protocol Context Sequence">
      <description>Sequence that specifies the context for the Scheduled Protocol Code Sequence Item. One or more items may be included in this sequence. See Section C.4.10.1.</description>
      <section ref="C.4.10.1" name="">The Protocol Context Sequence (0040,0440) allows the specification of parameters that further qualify the scheduled protocol, provided through a set of generic name/value pairs of context Content Items.
Note:  This allows the specification of clinical, acquisition, or procedural qualifiers for the scheduled protocol, such as a specific body part, imaging technique, or parameters of a preparatory event (e.g., radionuclide injection). Specific uses of this Sequence may be documented in a Template defined in accordance with PS3.16.

</section>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Content Item Macro' Table 10-2" description="No Baseline Template is defined."/>
    <entry group="0040" element="0441" name="&gt;&gt;&gt; Content Item Modifier Sequence">
      <description>Sequence that specifies modifiers for a Protocol Context Content Item. One or more items may be included in this sequence. See Section C.4.10.1.</description>
      <section ref="C.4.10.1" name="">The Protocol Context Sequence (0040,0440) allows the specification of parameters that further qualify the scheduled protocol, provided through a set of generic name/value pairs of context Content Items.
Note:  This allows the specification of clinical, acquisition, or procedural qualifiers for the scheduled protocol, such as a specific body part, imaging technique, or parameters of a preparatory event (e.g., radionuclide injection). Specific uses of this Sequence may be documented in a Template defined in accordance with PS3.16.

</section>
    </entry>
    <include ref="&gt;&gt;&gt;&gt;Include 'Content Item Macro' Table 10-2" description="No Baseline Template is defined."/>
  </module>
  <module ref="C.4.14" table="C.4-14" name="Performed Procedure Step Information Module Attributes">
    <entry group="0040" element="0241" name="Performed Station AE Title">
      <description>AE title of the modality on which the Performed Procedure Step was performed.</description>
    </entry>
    <entry group="0040" element="0242" name="Performed Station Name">
      <description>An institution defined name for the modality on which the Performed Procedure Step was performed.</description>
    </entry>
    <entry group="0040" element="0243" name="Performed Location">
      <description>Description of the location at which the Performed Procedure Step was performed.</description>
    </entry>
    <entry group="0040" element="0244" name="Performed Procedure Step Start Date">
      <description>Date on which the Performed Procedure Step started.
Note: This value may be used to determine the earliest date to use as the Study Date (0008,0020) in composite instances and in updated Modality Scheduled Procedure Steps in order to allow Study level attributes to have consistent values if additional Procedure Steps are performed.</description>
    </entry>
    <entry group="0040" element="0245" name="Performed Procedure Step Start Time">
      <description>Time at which the Performed Procedure Step started.
Note: This value may be used to determine the earliest time to use as the Study Time (0008,0030) in composite instances and in updated Modality Scheduled Procedure Steps in order to allow Study level attributes to have consistent values if additional Procedure Steps are performed.</description>
    </entry>
    <entry group="0040" element="0253" name="Performed Procedure Step ID">
      <description>User or equipment generated identifier of that part of a Procedure that has been carried out within this step.</description>
    </entry>
    <entry group="0040" element="0250" name="Performed Procedure Step End Date">
      <description>Date on which the Performed Procedure Step ended.</description>
    </entry>
    <entry group="0040" element="0251" name="Performed Procedure Step End Time">
      <description>Time at which the Performed Procedure Step ended.</description>
    </entry>
    <entry group="0040" element="0252" name="Performed Procedure Step Status">
      <description>Contains the state of the Performed Procedure Step. Enumerated Values:
IN PROGRESS = Started but not complete
DISCONTINUED = Canceled or unsuccessfully terminated
COMPLETED = Successfully completed</description>
    </entry>
    <entry group="0040" element="0254" name="Performed Procedure Step Description">
      <description>Institution-generated description or classification of the Procedure Step that was performed.</description>
    </entry>
    <entry group="0040" element="0280" name="Comments on the Performed Procedure Step">
      <description>User-defined comments on the Performed Procedure Step.</description>
    </entry>
    <entry group="0040" element="0255" name="Performed Procedure Type Description">
      <description>A description of the type of procedure performed.</description>
    </entry>
    <entry group="0008" element="1032" name="Procedure Code Sequence">
      <description>A sequence that conveys the (single) type of procedure performed.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="0281" name="Performed Procedure Step Discontinuation Reason Code Sequence">
      <description>The reason the Performed Procedure Step Status (0040,0252) was set to DISCONTINUED.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 9300."/>
  </module>
  <module ref="C.4.15" table="C.4-15" name="Image Acquisition Results Module Attributes">
    <entry group="0008" element="0060" name="Modality">
      <description>Type of equipment that originally acquired the data used to create the images associated with this Modality Performed Procedure Step. See C.7.3.1.1.1 for Defined Terms.
Note: A Modality value in the created SOP Instances may be different from the MPPS Modality value. For example, multiple series may have been created during the MPPS (images, waveforms, softcopy presentation states and/or structured reports) with SOP Instances in different series having different modality values.</description>
      <section ref="C.7.3.1.1.1" name="">Defined Terms for the Modality (0008,0060) are:
<defined-terms><term value="CR" meaning="Computed Radiography"/><term value="MR" meaning="Magnetic Resonance"/><term value="US" meaning="Ultrasound"/><term value="BI" meaning="Biomagnetic imaging"/><term value="DD" meaning="Duplex Doppler"/><term value="ES" meaning="Endoscopy"/><term value=""/><term value="PT" meaning="Positron emission tomography (PET)"/><term value="ST" meaning="Single-photon emission computed tomography (SPECT)"/><term value="XA" meaning="X-Ray Angiography"/><term value="RTIMAGE" meaning="Radiotherapy Image"/><term value="RTSTRUCT" meaning="Radiotherapy Structure Set"/><term value="RTRECORD" meaning="RT Treatment Record"/><term value="DX" meaning="Digital Radiography"/><term value="IO" meaning="Intra-oral Radiography"/><term value="GM" meaning="General Microscopy"/><term value="XC" meaning="External-camera Photography"/><term value="AU" meaning="Audio"/><term value="EPS" meaning="Cardiac Electrophysiology"/><term value="SR" meaning="SR Document"/><term value="OP" meaning="Ophthalmic Photography"/><term value="OCT" meaning="Optical Coherence Tomography (non-Ophthalmic)"/><term value="OPV" meaning="Ophthalmic Visual Field"/><term value="KO" meaning="Key Object Selection"/><term value="REG" meaning="Registration"/><term value="BDUS" meaning="Bone Densitometry (ultrasound)"/><term value="DOC" meaning="Document"/></defined-terms>
Retired Defined Terms for the Modality (0008,0060) are:
<retired-defined-terms><term value="DS" meaning="Digital Subtraction Angiography (retired)"/><term value="DF" meaning="Digital fluoroscopy (retired)"/><term value="AS" meaning="Angioscopy"/><term value="EC" meaning="Echocardiography"/><term value="FA" meaning="Fluorescein angiography"/><term value="DM" meaning="Digital microscopy"/><term value="MA" meaning="Magnetic resonance angiography"/></retired-defined-terms>
Note:  1. The XA modality incorporates the retired modality DS.
  2. The RF modality incorporates the retired modalities CF, DF, VF.
  3. The modality listed in the Modality Data Element (0008,0060) may not match the name of the IOD in which it appears. For example, a SOP instance from XA IOD may list the RF modality when an RF implementation produces an XA object.
  4. The MR modality incorporates the retired modalities MA and MS.

</section>
    </entry>
    <entry group="0020" element="0010" name="Study ID">
      <description>User or equipment generated Study Identifier.</description>
    </entry>
    <entry group="0040" element="0260" name="Performed Protocol Code Sequence">
      <description>Sequence describing the Protocol performed for this Procedure Step. This sequence may have zero or more Items.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="0440" name="&gt;Protocol Context Sequence">
      <description>Sequence that specifies the context for the Performed Protocol Code Sequence Item. One or more items may be included in this sequence. See Section C.4.10.1.</description>
      <section ref="C.4.10.1" name="">The Protocol Context Sequence (0040,0440) allows the specification of parameters that further qualify the scheduled protocol, provided through a set of generic name/value pairs of context Content Items.
Note:  This allows the specification of clinical, acquisition, or procedural qualifiers for the scheduled protocol, such as a specific body part, imaging technique, or parameters of a preparatory event (e.g., radionuclide injection). Specific uses of this Sequence may be documented in a Template defined in accordance with PS3.16.

</section>
    </entry>
    <include ref="&gt;&gt;Include 'Content Item Macro' Table 10-2" description="No Baseline Template is defined."/>
    <entry group="0040" element="0441" name="&gt;&gt; Content Item Modifier Sequence">
      <description>Sequence that specifies modifiers for a Protocol Context Content Item. One or more items may be included in this sequence. See Section C.4.10.1.</description>
      <section ref="C.4.10.1" name="">The Protocol Context Sequence (0040,0440) allows the specification of parameters that further qualify the scheduled protocol, provided through a set of generic name/value pairs of context Content Items.
Note:  This allows the specification of clinical, acquisition, or procedural qualifiers for the scheduled protocol, such as a specific body part, imaging technique, or parameters of a preparatory event (e.g., radionuclide injection). Specific uses of this Sequence may be documented in a Template defined in accordance with PS3.16.

</section>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Content Item Macro' Table 10-2" description="No Baseline Template is defined."/>
    <entry group="0040" element="0340" name="Performed Series Sequence">
      <description>Attributes of the Series that comprise this Modality Performed Procedure Step. The Sequence may have zero or more Items.</description>
    </entry>
    <entry group="0008" element="1050" name="&gt;Performing Physician's Name">
      <description>Name of the physician(s) administering this Series.</description>
    </entry>
    <entry group="0008" element="1052" name="&gt;Performing Physician Identification Sequence">
      <description>Identification of the physician(s) administering the Series. One or more items shall be included in this sequence. If more than one Item, the number and order shall correspond to the value of Performing Physician's Name (0008,1050), if present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Person Identification Macro' Table 10-1"/>
    <entry group="0008" element="1070" name="&gt;Operators' Name">
      <description>Name(s) of the operator(s) who supporting this Series.</description>
    </entry>
    <entry group="0008" element="1072" name="&gt;Operator Identification Sequence">
      <description>Identification of the operator(s) supporting the Series. One or more items shall be included in this sequence. If more than one Item, the number and order shall correspond to the value of Operators' Name (0008,1070), if present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Person Identification Macro' Table 10-1"/>
    <entry group="0018" element="1030" name="&gt;Protocol Name">
      <description>User-defined description of the conditions under which the Series was performed.
Note: This attribute conveys series-specific protocol identification and may or may not be identical to the one presented in the Performed Protocol Code Sequence (0040,0260).</description>
    </entry>
    <entry group="0020" element="000E" name="&gt;Series Instance UID">
      <description>Unique Identifier of the Series.</description>
    </entry>
    <entry group="0008" element="103E" name="&gt;Series Description">
      <description>User provided description of the Series</description>
    </entry>
    <entry group="0008" element="0054" name="&gt;Retrieve AE Title">
      <description>Title of the DICOM Application Entity where the Images and other Composite SOP Instances in this Series may be retrieved on the network.
Note: The duration for which this location remains valid is unspecified.</description>
    </entry>
    <entry group="0040" element="A494" name="&gt;Archive Requested">
      <description>The instances in this series are expected to be archived in the long term archive.
Defined Terms:
NO, YES</description>
    </entry>
    <entry group="0008" element="1140" name="&gt;Referenced Image Sequence">
      <description>A Sequence that provides reference to Composite SOP Instances created during the acquisition of the procedure step. The sequence may have zero or more Items.
Note: The use of Referenced Image Sequence is historical, and in this context it allows the reference of any Composite SOP Instance.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0040" element="0220" name="&gt;Referenced Non-Image Composite SOP Instance Sequence">
      <description>Uniquely identifies instances, other than images, of any SOP Class that conforms to the DICOM Composite IOD Information Model, such as Waveforms, Presentation States or Structured Reports, created during the acquisition of the procedure step, and that are not referenced in Referenced Image Sequence (0008,1140). The sequence may have zero or more Items.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.4.16" table="C.4-16" name="Radiation Dose Module Attributes">
    <entry group="0008" element="2229" name="Anatomic Structure, Space or Region Sequence">
      <description>Anatomic structure, space or region that has been exposed to ionizing radiation. The sequence may have zero or one Items.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="0300" name="Total Time of Fluoroscopy">
      <description>Total duration of X-Ray exposure during fluoroscopy in seconds (pedal time) during this Performed Procedure Step.</description>
    </entry>
    <entry group="0040" element="0301" name="Total Number of Exposures">
      <description>Total number of exposures made during this Performed Procedure Step. The number includes non-digital and digital exposures.</description>
    </entry>
    <entry group="0018" element="1110" name="Distance Source to Detector">
      <description>Distance in mm from the source to detector center.
Note: This value is traditionally referred to as Source Image Receptor Distance (SID).</description>
    </entry>
    <entry group="0040" element="0306" name="Distance Source to Entrance">
      <description>Distance in mm from the source to the surface of the patient closest to the source during this Performed Procedure Step.
Note: This may be an estimated value based on assumptions about the patient's body size and habitus.</description>
    </entry>
    <entry group="0040" element="0302" name="Entrance Dose">
      <description>Average entrance dose value measured in dGy at the surface of the patient during this Performed Procedure Step.
Note: This may be an estimated value based on assumptions about the patient's body size and habitus.</description>
    </entry>
    <entry group="0040" element="8302" name="Entrance Dose in mGy">
      <description>Average entrance dose value measured in mGy at the surface of the patient during this Performed Procedure Step.
Note: This may be an estimated value based on assumptions about the patient's body size and habitus.</description>
    </entry>
    <entry group="0040" element="0303" name="Exposed Area">
      <description>Typical dimension of the exposed area at the detector plane. If Rectangular: row dimension followed by column; if Round: diameter. Measured in mm.
Notes: 1. This may be an estimated value based on assumptions about the patient's body size and habitus.
2. This attribute is used in the X-Ray Acquisition Dose Module with units in cm (see Section C 8.7.8 Table C.8-33).</description>
    </entry>
    <entry group="0018" element="115E" name="Image and Fluoroscopy Area Dose Product">
      <description>Total area-dose-product to which the patient was exposed, accumulated over the complete Performed Procedure Step and measured in dGy*cm*cm, including fluoroscopy.
Notes: 1. The sum of the area dose product of all images of a Series or a Study may not result in the total area dose product to which the patient was exposed.
2. This may be an estimated value based on assumptions about the patient's body size and habitus.</description>
    </entry>
    <entry group="0040" element="0310" name="Comments on Radiation Dose">
      <description>User-defined comments on any special conditions related to radiation dose encountered during this Performed Procedure Step.</description>
    </entry>
    <entry group="0040" element="030E" name="Exposure Dose Sequence">
      <description>Exposure Dose Sequence will contain Total Number of Exposures (0040,0301) items plus an item for each fluoroscopy episode not already counted as an exposure.</description>
    </entry>
    <entry group="0018" element="115A" name="&gt;Radiation Mode">
      <description>Specifies X-Ray radiation mode. Enumerated Values:
CONTINUOUS
PULSED</description>
    </entry>
    <entry group="0018" element="0060" name="&gt;KVp">
      <description>Peak kilo voltage output of the x-ray generator used. An average in the case of fluoroscopy (continuous radiation mode).</description>
    </entry>
    <entry group="0018" element="8151" name="&gt;X-Ray Tube Current in µA">
      <description>X-Ray Tube Current in µA. An average in the case of fluoroscopy (continuous radiation mode).</description>
    </entry>
    <entry group="0018" element="1150" name="&gt;Exposure Time">
      <description>Time of x-ray exposure or fluoroscopy in msec.</description>
    </entry>
    <entry group="0018" element="1160" name="&gt;Filter Type">
      <description>Type of filter(s) inserted into the X-Ray beam (e.g. wedges). See C.8.7.10 and C.8.15.3.9 (for enhanced CT) for Defined Terms.</description>
      <section ref="C.8.7.10" name="">This Module describes the attributes related to the filtration of X-Rays during the acquisition of an X-Ray image.
Table C.8-35
X-RAY FILTRATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Filter Type" meaning="(0018,1160)"/><term value="Filter Material" meaning="(0018,7050)"/><term value="Filter Thickness Minimum" meaning="(0018,7052)"/><term value="Filter Thickness Maximum" meaning="(0018,7054)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0018" element="7050" name="&gt;Filter Material">
      <description>The X-Ray absorbing material used in the filter. May be multi-valued. See C.8.7.10 and C.8.15.3.9 (for enhanced CT) for Defined Terms.</description>
      <section ref="C.8.7.10" name="">This Module describes the attributes related to the filtration of X-Rays during the acquisition of an X-Ray image.
Table C.8-35
X-RAY FILTRATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Filter Type" meaning="(0018,1160)"/><term value="Filter Material" meaning="(0018,7050)"/><term value="Filter Thickness Minimum" meaning="(0018,7052)"/><term value="Filter Thickness Maximum" meaning="(0018,7054)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0040" element="0310" name="&gt;Comments on Radiation Dose">
      <description>User-defined comments on any special conditions related to radiation dose encountered during during the episode described by this Exposure Dose Sequence Item.</description>
    </entry>
  </module>
  <module ref="C.4.17" table="C.4-17" name="Billing and Material Management Code Module Attributes">
    <entry group="0040" element="0320" name="Billing Procedure Step Sequence">
      <description>Contains billing codes for the Procedure Type performed within the Procedure Step. The sequence may have zero or more Items.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="0321" name="Film Consumption Sequence">
      <description>Information about the film consumption for this Performed Procedure Step. The sequence may have zero or more Items.</description>
    </entry>
    <entry group="2100" element="0170" name="&gt;Number of Films">
      <description>Number of films actually printed.</description>
    </entry>
    <entry group="2000" element="0030" name="&gt;Medium Type">
      <description>Type(s) of medium on which images were printed. For Defined Terms see Table C.13-1.</description>
    </entry>
    <entry group="2010" element="0050" name="&gt;Film Size ID">
      <description>Size(s) of film on which images were printed. For Defined Terms see Table C.13-3.</description>
    </entry>
    <entry group="0040" element="0324" name="Billing Supplies and Devices Sequence">
      <description>Chemicals, supplies and devices for billing used in the Performed Procedure Step. The sequence may have one or more Items.</description>
    </entry>
    <entry group="0040" element="0296" name="&gt;Billing Item Sequence">
      <description>Code values of chemicals, supplies or devices required for billing. The sequence may have zero or one Items.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="0293" name="&gt;Quantity Sequence">
      <description>Sequence containing the quantity of used chemicals or devices. The sequence may have zero or one Items.</description>
    </entry>
    <entry group="0040" element="0294" name="&gt;&gt;Quantity">
      <description>Numerical quantity value.</description>
    </entry>
    <entry group="0040" element="0295" name="&gt;&gt;Measuring Units Sequence">
      <description>Unit of measurement. The sequence may have zero or one Items.</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 82."/>
  </module>
  <module ref="C.4.18" table="C.4-18" name="General Purpose Scheduled Procedure Step Relationship Module Attributes">
    <entry group="0010" element="0010" name="Patient's Name">
      <description>Patient's full legal name.</description>
    </entry>
    <entry group="0010" element="0020" name="Patient ID">
      <description>Primary hospital identification number or code for the patient.</description>
    </entry>
    <entry group="0010" element="0021" name="Issuer of Patient ID">
      <description>Identifier of the Assigning Authority that issued the Patient ID.</description>
    </entry>
    <entry group="0010" element="0030" name="Patient's Birth Date">
      <description>Date of birth of the named patient.</description>
    </entry>
    <entry group="0010" element="0040" name="Patient's Sex">
      <description>Sex of the named Patient.
Enumerated Values:
M = male
F = female
O = other</description>
    </entry>
    <entry group="0040" element="A370" name="Referenced Request Sequence">
      <description>The list of Requested Procedures the Procedure Step shall contribute to.
One or more Items may be included in the sequence.</description>
    </entry>
    <entry group="0020" element="000D" name="&gt;Study Instance UID">
      <description>Unique identifier for the Study.</description>
    </entry>
    <entry group="0008" element="1110" name="&gt;Referenced Study Sequence">
      <description>Uniquely identifies the Study SOP Instance that represents the Requested Procedure.
Zero or one Item may be included in this sequence.</description>
    </entry>
    <entry group="0008" element="1150" name="&gt;&gt;Referenced SOP Class UID">
      <description>Uniquely identifies the SOP Class.</description>
    </entry>
    <entry group="0008" element="1155" name="&gt;&gt;Referenced SOP Instance UID">
      <description>Uniquely identifies the SOP Instance.</description>
    </entry>
    <entry group="0008" element="0050" name="&gt;Accession Number">
      <description>A departmental IS generated number that identifies the Imaging Service Request.</description>
    </entry>
    <entry group="0032" element="1064" name="&gt;Requested Procedure Code Sequence">
      <description>A sequence that conveys the Procedure Type of the Requested Procedure.
Zero or one Item may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="2016" name="&gt;Placer Order Number / Imaging Service Request">
      <description>The order number assigned to the Imaging Service Request by the party placing the order.</description>
    </entry>
    <entry group="0040" element="2017" name="&gt;Filler Order Number / Imaging Service Request">
      <description>The order number assigned to the Imaging Service Request by the party filling the order.</description>
    </entry>
    <entry group="0040" element="1001" name="&gt;Requested Procedure ID">
      <description>Identifier that identifies the Requested Procedure in the Imaging Service Request.</description>
    </entry>
    <entry group="0032" element="1060" name="&gt;Requested Procedure Description">
      <description>Institution-generated description or classification of the Requested Procedure.</description>
    </entry>
    <entry group="0040" element="1002" name="&gt;Reason for the Requested Procedure">
      <description>Reason for requesting this procedure.</description>
    </entry>
    <entry group="0040" element="100A" name="&gt; Reason for Requested Procedure Code Sequence">
      <description>Coded reason for requesting this procedure.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="1400" name="&gt;Requested Procedure Comments">
      <description>User-defined comments on the Requested Procedure.</description>
    </entry>
    <entry group="0040" element="1008" name="&gt;Confidentiality Code">
      <description>Confidentiality Constraints on the Requested Procedure by the party filling the order.</description>
    </entry>
    <entry group="0040" element="1010" name="&gt;Names of Intended Recipients of Results">
      <description>Names of the physicians, who are intended recipients of results.</description>
    </entry>
    <entry group="0040" element="2400" name="&gt;Imaging Service Request Comments">
      <description>User-defined comments on the Imaging Service Request.</description>
    </entry>
    <entry group="0032" element="1032" name="&gt;Requesting Physician">
      <description>Physician who requested the Imaging Service Request.</description>
    </entry>
    <entry group="0032" element="1033" name="&gt;Requesting Service">
      <description>Institutional department where the request initiated.</description>
    </entry>
    <entry group="0040" element="2004" name="&gt;Issue Date of Imaging Service Request">
      <description>Date on which the Imaging Service Request was issued by the requester.</description>
    </entry>
    <entry group="0040" element="2005" name="&gt;Issue Time of Imaging Service Request">
      <description>Time at which the Imaging Service Request was issued by the requester.</description>
    </entry>
    <entry group="0008" element="0090" name="&gt;Referring Physician's Name">
      <description>Patient's primary physician for this Imaging Service Request.</description>
    </entry>
  </module>
  <module ref="C.4.19" table="C.4-19" name="General Purpose Scheduled Procedure Step Information Module Attributes">
    <entry group="0040" element="4001" name="General Purpose Scheduled Procedure Step Status">
      <description>A status that informs the operator and the worklist management system about the progress of the scheduled General Purpose procedure step.
Enumerated Values are:
SCHEDULED, IN PROGRESS, SUSPENDED, COMPLETED, DISCONTINUED.
See PS 3.4 for a detailed description of the meaning and usage of these values.</description>
    </entry>
    <entry group="0040" element="4003" name="General Purpose Scheduled Procedure Step Priority">
      <description>Scheduled Procedure Step priority.
Enumerated Values are:
HIGH: used to indicate an urgent or emergent work item, equivalent to a STAT request.
MEDIUM: used to indicate a work item that has a priority less than HIGH and higher than LOW. It can be used to further stratify work items.
LOW: used to indicate a routine or non-urgent work item.</description>
    </entry>
    <entry group="0040" element="0009" name="Scheduled Procedure Step ID">
      <description>Identifier that identifies the Scheduled General Purpose Procedure Step.</description>
    </entry>
    <entry group="0040" element="4010" name="Scheduled Procedure Step Modification Date and Time">
      <description>Date and time when the General Purpose Scheduled Procedure Step was last modified or first created (whichever is most recent).
Note: This attribute should be implicitly updated by the worklist management system whenever any modification is made to attributes of a General Purpose Scheduled Procedure Step. In particular, note that creation of General Purpose Performed Procedure Steps by a performing device can modify attributes of a related General Purpose Scheduled Procedure Step (e.g. the contents of Resulting General Purpose Performed Procedure Steps Sequence (0040,4015)).</description>
    </entry>
    <entry group="0040" element="4004" name="Scheduled Processing Applications Code Sequence">
      <description>The list of processing application instances and/or application types on which the General Purpose Procedure Step is scheduled.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="4025" name="Scheduled Station Name Code Sequence">
      <description>Identifying name within the enterprise of the equipment for which the General Purpose Scheduled Procedure Step is scheduled. The name conveyed in the Code Value (0008,0100) may be the same as the AE Title, but does not have to be.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="4026" name="Scheduled Station Class Code Sequence">
      <description>Class of the equipment for which the General Purpose Scheduled Procedure Step is scheduled.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="4027" name="Scheduled Station Geographic Location Code Sequence">
      <description>Geographic location of the equipment for which the General Purpose Scheduled Procedure Step is scheduled.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="4034" name="Scheduled Human Performers Sequence">
      <description>The list of human performers that are scheduled to be involved or responsible for performing the Workitem in the General Purpose Scheduled Procedure Step.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0040" element="4009" name="&gt;Human Performer Code Sequence">
      <description>Human performer that is involved or responsible for performing the Workitem.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="4037" name="&gt;Human Performer's Name">
      <description>Name of the human performer.</description>
    </entry>
    <entry group="0040" element="4036" name="&gt;Human Performer's Organization">
      <description>Organization to which the human performer is accountable for the activities in the Workitem.</description>
    </entry>
    <entry group="0040" element="4005" name="Scheduled Procedure Step Start Date and Time">
      <description>Date and time on which the General Purpose Scheduled Procedure Step is scheduled to start.</description>
    </entry>
    <entry group="0040" element="4011" name="Expected Completion Date and Time">
      <description>Date on which the Procedure Step is expected to be completed.</description>
    </entry>
    <entry group="0040" element="4018" name="Scheduled Workitem Code Sequence">
      <description>A sequence that conveys the code for the Workitem.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="Baseline Context ID is CID 9231."/>
    <entry group="0040" element="0400" name="Comments on the Scheduled Procedure Step">
      <description>User-defined comments on the Scheduled Procedure Step.</description>
    </entry>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence">
      <description>List of any Modality or General Purpose Performed Procedure Steps, that may be used to perform the procedure step.
This sequence may contain references to performed procedure steps resulting from previous contributions to the performance of the procedure step (e.g. an image processing procedure step interrupted, and completed later).
Zero or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="0040" element="4020" name="Input Availability Flag">
      <description>Flag that indicates the availability of Composite SOP Instances in the Attribute "Input Information Sequence" (0040,4021) of the General Purpose Scheduled Procedure Step.
Enumerated values are:
PARTIAL
COMPLETE
The value PARTIAL denotes that the list of Composite SOP Instances may not yet be complete, and additional ones may be added at a later time.
The value COMPLETE denotes that all Composite SOP Instances are available and listed.
Note: It may happen that the list of Composite SOP Instances is empty when the value of the Input Availability Flag is COMPLETE. In such a case a Workitem has been scheduled that does not require input information.</description>
    </entry>
    <entry group="0040" element="4021" name="Input Information Sequence">
      <description>List of Composite SOP Instances that forms the input information needed to perform the scheduled procedure step. See also Input Availability Flag (0040,4020). The same Composite SOP Instance shall not be included in both the Input Information Sequence (0040,4021) and the Relevant Information Sequence (0040,4022).
Zero or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0040" element="4022" name="Relevant Information Sequence">
      <description>List of Composite SOP Instances that refers to relevant information that is considered pertinent for the performance of the scheduled procedure step. The same Composite SOP Instance shall not be included in both the Input Information Sequence (0040,4021) and the Relevant Information Sequence (0040,4022).
Zero or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0020" element="000D" name="Study Instance UID">
      <description>Unique Study identification that shall be used for the created Composite SOP Instances resulting from this General Purpose Scheduled Procedure Step.
Note: In most cases this will be the same Study Instance UID as for the instances in the Input Information Sequence (0040,4021).</description>
    </entry>
    <entry group="0008" element="0020" name="Study Date">
      <description>Date the Study started, if any previous procedure steps within the same study have already been performed.
Note: This value should be the same as that in the instances in the Input Information Sequence (0040,4021).</description>
    </entry>
    <entry group="0008" element="0030" name="Study Time">
      <description>Time the Study started, if any previous procedure steps within the same study have already been performed.
Note: This value should be the same as that in the instances in the Input Information Sequence (0040,4021).</description>
    </entry>
    <entry group="0040" element="4006" name="Multiple Copies Flag">
      <description>This flag indicates that multiple copies have to be made of a Composite SOP Instance that supports the notion of multiple copies. This includes the SR SOP Class. If set the Study Instance UIDs in the Referenced Request Sequence (0040,A370) shall be used for the created multiple copies.
Enumerated Values:
Y = Yes
N = No</description>
    </entry>
    <entry group="0040" element="4015" name="Resulting General Purpose Performed Procedure Steps Sequence">
      <description>List of all General Purpose Performed Procedure Steps that result from the performance of the procedure step.
Zero or more Items may be included in this sequence.
Note: Initially this list will be empty. New entries will be added when General Purpose Performed Procedure Steps are created by performing devices that are related to this Scheduled Procedure Step. E.g, this sequence may contain the partial results in case a General Purpose Scheduled Procedure Step is discontinued.</description>
    </entry>
    <include ref="&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="0040" element="4035" name="Actual Human Performers Sequence">
      <description>The list of current human performers that are actually involved or responsible for performing the Workitem.
Zero or more Items may be included in this sequence.
Note: Initially this list will be empty. A list of entries may be created at the status transition of the General Purpose Scheduled Procedure Step Status (0040,4001) to "IN PROGRESS"</description>
    </entry>
    <entry group="0040" element="4009" name="&gt;Human Performer Code Sequence">
      <description>Human performer that is involved or responsible for performing the Workitem.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="4037" name="&gt;Human Performer's Name">
      <description>Name of the human performer.</description>
    </entry>
    <entry group="0040" element="4036" name="&gt;Human Performer's Organization">
      <description>Organization to which the human performer is accountable for the activities in the Workitem.</description>
    </entry>
  </module>
  <module ref="C.4.20" table="C.4.20-1" name="General Purpose Performed Procedure Step Relationship Module Attributes">
    <entry group="0010" element="0010" name="Patient's Name">
      <description>Patient's full legal name.</description>
    </entry>
    <entry group="0010" element="0020" name="Patient ID">
      <description>Primary hospital identification number or code for the patient.</description>
    </entry>
    <entry group="0010" element="0021" name="Issuer of Patient ID">
      <description>Identifier of the Assigning Authority that issued the Patient ID.</description>
    </entry>
    <entry group="0010" element="0030" name="Patient's Birth Date">
      <description>Date of birth of the named patient.</description>
    </entry>
    <entry group="0010" element="0040" name="Patient's Sex">
      <description>Sex of the named Patient.
Enumerated Values:
M = male
F = female
O = other</description>
    </entry>
    <entry group="0040" element="A370" name="Referenced Request Sequence">
      <description>The list of Requested Procedures the Procedure Step shall contribute to.
Zero or more Items may be included in the sequence.</description>
    </entry>
    <entry group="0020" element="000D" name="&gt;Study Instance UID">
      <description>Unique identifier for the Study.</description>
    </entry>
    <entry group="0008" element="1110" name="&gt;Referenced Study Sequence">
      <description>Uniquely identifies the Study SOP Instance associated with this Scheduled Procedure Step.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="0008" element="0050" name="&gt;Accession Number">
      <description>A departmental IS generated number that identifies the order for the Study.</description>
    </entry>
    <entry group="0032" element="1064" name="&gt;Requested Procedure Code Sequence">
      <description>A sequence that conveys the Procedure Type of the Requested Procedure.
Zero or one Item may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="2016" name="&gt;Placer Order Number/Imaging Service Request">
      <description>The order number assigned to the Imaging Service Request by the party placing the order.</description>
    </entry>
    <entry group="0040" element="2017" name="&gt;Filler Order Number/Imaging Service Request">
      <description>The order number assigned to the Imaging Service Request by the party filling the order.</description>
    </entry>
    <entry group="0040" element="1001" name="&gt;Requested Procedure ID">
      <description>Identifier of the related Requested Procedure.</description>
    </entry>
    <entry group="0032" element="1060" name="&gt;Requested Procedure Description">
      <description>Institution-generated administrative description or classification of Requested Procedure.</description>
    </entry>
    <entry group="0040" element="4016" name="Referenced General Purpose Scheduled Procedure Step Sequence">
      <description>Uniquely identifies the General Purpose Scheduled Procedure Step SOP Instance associated with this General Purpose Performed Procedure Step.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="0040" element="4023" name="&gt;Referenced General Purpose Scheduled Procedure Step Transaction UID">
      <description>Transaction UID (0008,1195) used in the N-ACTION transaction that requested the transition to the IN PROGRESS state for the referenced General Purpose Scheduled Procedure Step.</description>
    </entry>
    <entry group="0038" element="0010" name="Admission ID">
      <description>Identification number of the visit as assigned by the healthcare provider</description>
    </entry>
    <entry group="0038" element="0011" name="Issuer of Admission ID">
      <description>Name of healthcare provider that issued the Admission ID</description>
    </entry>
    <entry group="0038" element="0060" name="Service Episode ID">
      <description>Identifier of the Service Episode as assigned by the healthcare provider</description>
    </entry>
    <entry group="0038" element="0061" name="Issuer of Service Episode ID">
      <description>Name of healthcare provider that issued the Service Episode ID</description>
    </entry>
    <entry group="0038" element="0062" name="Service Episode Description">
      <description>Description of the type of service episode.</description>
    </entry>
  </module>
  <module ref="C.4.21" table="C.4.21-1" name="General Purpose Performed Procedure Step Information Module Attributes">
    <entry group="0040" element="4035" name="Actual Human Performers Sequence">
      <description>The list of human performers that were actually involved in or responsible for performing this General Purpose Performed Procedure Step.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0040" element="4009" name="&gt;Human Performer Code Sequence">
      <description>Human performer that is actually involved or responsible for performing the General Purpose Performed Procedure Step.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="4037" name="&gt;Human Performer's Name">
      <description>Name of the human performer.</description>
    </entry>
    <entry group="0040" element="4036" name="&gt;Human Performer's Organization">
      <description>Organization to which the human performer is accountable for the activities in the General Purpose Performed Procedure Step.</description>
    </entry>
    <entry group="0040" element="4028" name="Performed Station Name Code Sequence">
      <description>Name within the enterprise of the equipment that created the General Purpose Performed Procedure Step. This name may be the same as the AE Title, but does not have to be.
Zero or one Item may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="4029" name="Performed Station Class Code Sequence">
      <description>Class of the equipment that created the General Purpose Performed Procedure Step.
Zero or one Item may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="4030" name="Performed Station Geographic Location Code Sequence">
      <description>Geographic location of the equipment that created General Purpose Performed Procedure Step. Zero or one Item may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="4007" name="Performed Processing Applications Code Sequence">
      <description>The list of processing application instances and/or application types on which the General Purpose Performed Procedure Step is executed.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0040" element="0244" name="Performed Procedure Step Start Date">
      <description>Date on which the General Purpose Performed Procedure Step started.
Note: This value may be used to determine the earliest date to use as the Study Date (0008,0020) in composite instances and in updated General Purpose Scheduled Procedure Steps in order to allow Study level attributes to have consistent values if additional Procedure Steps are performed.</description>
    </entry>
    <entry group="0040" element="0245" name="Performed Procedure Step Start Time">
      <description>Time at which the General Purpose Performed Procedure Step started.
Note: This value may be used to determine the earliest time to use as the Study Time (0008,0030) in composite instances and in updated General Purpose Scheduled Procedure Steps in order to allow Study level attributes to have consistent values if additional Procedure Steps are performed.</description>
    </entry>
    <entry group="0040" element="0253" name="Performed Procedure Step ID">
      <description>User or equipment generated identifier of that part of a Procedure that has been carried out within this procedure step.</description>
    </entry>
    <entry group="0040" element="0250" name="Performed Procedure Step End Date">
      <description>Date on which the General Purpose Performed Procedure Step ended.</description>
    </entry>
    <entry group="0040" element="0251" name="Performed Procedure Step End Time">
      <description>Time at which the General Purpose Performed Procedure Step ended.</description>
    </entry>
    <entry group="0040" element="4002" name="General Purpose Performed Procedure Step Status">
      <description>Contains the state of the Performed Procedure Step. Enumerated Values:
IN PROGRESS = Started but not complete
DISCONTINUED = Canceled or unsuccessfully terminated
COMPLETED = Successfully completed</description>
    </entry>
    <entry group="0040" element="0254" name="Performed Procedure Step Description">
      <description>Institution-generated description or classification of the Procedure Step that was performed.</description>
    </entry>
    <entry group="0040" element="0280" name="Comments on the Performed Procedure Step">
      <description>User-defined comments on the Performed Procedure Step. This attribute shall not be used as a substitute for the code meaning in the Performed Workitem Code Sequence (0040,4019).</description>
    </entry>
    <entry group="0040" element="4019" name="Performed Workitem Code Sequence">
      <description>A sequence that conveys the (single) type of procedure performed.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="Baseline Context ID is CID 9231."/>
  </module>
  <module ref="C.4.22" table="C.4.22-1" name="General Purpose Results Module Attributes">
    <entry group="0040" element="4033" name="Output Information Sequence">
      <description>A Sequence that provides reference to one or more Composite SOP instances, that identify the Structured Reports or other results created.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0020" element="000D" name="&gt;Study Instance UID">
      <description>Unique identifier for the Study</description>
    </entry>
    <entry group="0008" element="1115" name="&gt;Referenced Series Sequence">
      <description>Sequence of Items where each Item includes the Attributes of a Series containing referenced Composite Object(s). One or more Items may be included in this sequence</description>
    </entry>
    <entry group="0040" element="A494" name="&gt;&gt;Archive Requested">
      <description>The instances in this series are expected to be archived in the long term archive.
Defined Terms:
NO, YES</description>
    </entry>
    <include ref="&gt;&gt;Include 'Hierarchical Series Reference Macro' Table C.17-3a"/>
    <entry group="0040" element="4031" name="Requested Subsequent Workitem Code Sequence">
      <description>A Sequence that provides suggested next Workitems, based on the produced results.
Note: This Attribute may also be used in case a step has been done incorrectly and should be redone.
Zero or more Items may be included in this sequence</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="Baseline Context ID is CID 9231."/>
    <entry group="0040" element="4032" name="Non-DICOM Output Code Sequence">
      <description>A Sequence that describes any non-DICOM output produced as results.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="Baseline Context ID is CID 9232."/>
  </module>
  <module ref="C.4.23" table="C.4.23-1" name="Instance Availability Notification Module Attributes">
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance to which this availability notification instance is related, if any. The Sequence shall have zero or one Item.
Notes: 1. This may refer to a different PPS than that encoded in the composite instances themselves.
2. It is typically used for notification about instances created as a consequence of some scheduled activity.</description>
    </entry>
    <include ref="&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="0040" element="4019" name="&gt;Performed Workitem Code Sequence">
      <description>A sequence that conveys the (single) type of procedure performed.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="Baseline Context ID is CID 9231."/>
    <entry group="0020" element="000D" name="Study Instance UID">
      <description>Unique identifier for the Study of which all the Instances referenced in this notification are part.</description>
    </entry>
    <entry group="0008" element="1115" name="Referenced Series Sequence">
      <description>Sequence of Items where each Item includes references to Instances within the same Series. One or more Items shall be included in this Sequence.</description>
    </entry>
    <entry group="0020" element="000E" name="&gt;Series Instance UID">
      <description>Unique identifier of the Series of which all the Instances referenced in this Item are part.</description>
    </entry>
    <entry group="0008" element="1199" name="&gt;Referenced SOP Sequence">
      <description>Sequence of Items where each Item includes a reference to a single Instance within this Series. One or more Items shall be included in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="0008" element="0056" name="&gt;&gt;Instance Availability">
      <description>The availability of the referenced Instance.
See Section C.4.23.1.1</description>
      <section ref="C.4.23.1.1" name="">The Enumerated Values for Instance Availability (0008,0056) are:
</section>
    </entry>
    <entry group="0008" element="0054" name="&gt;&gt;Retrieve AE Title">
      <description>Title of the DICOM Application Entity from which the referenced Instance may or may not be retrievable, i.e. the scope for which Instance Availability (0008,0056) applies. See Section C.4.23.1.1.</description>
      <section ref="C.4.23.1.1" name="">The Enumerated Values for Instance Availability (0008,0056) are:
</section>
    </entry>
    <entry group="0088" element="0130" name="&gt;&gt;Storage Media File-Set ID">
      <description>The user or implementation specific human readable identifier that identifies the offline storage media on which the instance resides.</description>
    </entry>
    <entry group="0088" element="0140" name="&gt;&gt;Storage Media File-Set UID">
      <description>Uniquely identifies the offline storage media on which the instance resides.</description>
    </entry>
  </module>
  <module ref="C.7.1.1" table="C.7-1" name="Patient Module Attributes">
    <entry group="0010" element="0010" name="Patient's Name" type="2">
      <description>Patient's full name.</description>
    </entry>
    <entry group="0010" element="0020" name="Patient ID" type="2">
      <description>Primary hospital identification number or code for the patient.</description>
    </entry>
    <entry group="0010" element="0021" name="Issuer of Patient ID" type="3">
      <description>Identifier of the Assigning Authority that issued the Patient ID.</description>
    </entry>
    <entry group="0010" element="0030" name="Patient's Birth Date" type="2">
      <description>Birth date of the patient.</description>
    </entry>
    <entry group="0010" element="0040" name="Patient's Sex" type="2">
      <description>Sex of the named patient.
Enumerated Values:
M = male
F = female
O = other</description>
    </entry>
    <entry group="0008" element="1120" name="Referenced Patient Sequence" type="3">
      <description>A sequence that provides reference to a Patient SOP Class/Instance pair. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="0010" element="0032" name="Patient's Birth Time" type="3">
      <description>Birth time of the Patient.</description>
    </entry>
    <entry group="0010" element="1000" name="Other Patient IDs" type="3">
      <description>Other identification numbers or codes used to identify the patient.</description>
    </entry>
    <entry group="0010" element="1002" name="Other Patient IDs Sequence" type="3">
      <description>A sequence of identification numbers or codes used to identify the patient, which may or may not be human readable, and may or may not have been obtained from an implanted or attached device such as an RFID or barcode.
If present, shall contain one or more items.</description>
    </entry>
    <entry group="0010" element="0020" name="&gt;Patient ID" type="1">
      <description>An identification number or code used to identify the patient.</description>
    </entry>
    <entry group="0010" element="0021" name="&gt;Issuer of Patient ID" type="1">
      <description>Identifier of the Assigning Authority that issued the Patient ID.</description>
    </entry>
    <entry group="0010" element="0022" name="&gt;Type of Patient ID" type="1">
      <description>The type of identifier in this item. Defined Terms:
TEXT
RFID
BARCODE
Note: The identifier is coded as a string regardless of the type, not as a binary value.</description>
    </entry>
    <entry group="0010" element="1001" name="Other Patient Names" type="3">
      <description>Other names used to identify the patient.</description>
    </entry>
    <entry group="0010" element="2160" name="Ethnic Group" type="3">
      <description>Ethnic group or race of the patient.</description>
    </entry>
    <entry group="0010" element="4000" name="Patient Comments" type="3">
      <description>User-defined additional information about the patient.</description>
    </entry>
    <entry group="0010" element="2201" name="Patient Species Description" type="1C">
      <description>The species of the patient.
Required if the patient is an animal and if Patient Species Code Sequence (0010,2202) is not present. May be present otherwise.</description>
    </entry>
    <entry group="0010" element="2202" name="Patient Species Code Sequence" type="1C">
      <description>The species of the patient.
One Item shall be present.
Required if the patient is an animal and if Patient Species Description (0010,2201) is not present. May be present otherwise.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 7454."/>
    <entry group="0010" element="2292" name="Patient Breed Description" type="2C">
      <description>The breed of the patient.
Required if the patient is an animal and if Patient Breed Code Sequence (0010,2293) is empty. May be present otherwise.</description>
    </entry>
    <entry group="0010" element="2293" name="Patient Breed Code Sequence" type="2C">
      <description>The breed of the patient.
Zero or more Items shall be present.
Required if the patient is an animal.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 7480."/>
    <entry group="0010" element="2294" name="Breed Registration Sequence" type="2C">
      <description>Information identifying an animal within a breed registry.
Zero or more Items shall be present.
Required if the patient is an animal.</description>
    </entry>
    <entry group="0010" element="2295" name="&gt;Breed Registration Number" type="1">
      <description>Identification number of an animal within the registry.</description>
    </entry>
    <entry group="0010" element="2296" name="&gt;Breed Registry Code Sequence" type="1">
      <description>Identification of the organization with which an animal is registered.
One Item shall be present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 7481."/>
    <entry group="0010" element="2297" name="Responsible Person" type="2C">
      <description>Name of person with medical decision making authority for the patient.
Required if the patient is an animal. May be present otherwise.</description>
    </entry>
    <entry group="0010" element="2298" name="Responsible Person Role" type="1C">
      <description>Relationship of Responsible Person to the patient.
Defined Terms:
OWNER
Required if Responsible Person is present and has a value.</description>
    </entry>
    <entry group="0010" element="2299" name="Responsible Organization" type="2C">
      <description>Name of organization with medical decision making authority for the patient.
Required if patient is an animal. May be present otherwise.</description>
    </entry>
    <entry group="0012" element="0062" name="Patient Identity Removed" type="3">
      <description>The true identity of the patient has been removed from the Attributes and the Pixel Data
Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="0012" element="0063" name="De-identification Method" type="1C">
      <description>A description or label of the mechanism or method use to remove the patient's identity. May be multi-valued if successive de-identification steps have been performed.
Note: This may be used to describe the extent or thoroughness of the de-identification, for example whether or not the de-identification is for a "Limited Data Set" (as per HIPAA Privacy Rule).
Required if Patient Identity Removed (0012,0062) is present and has a value of YES and De-identification Method Code Sequence (0012,0064) is not present.</description>
    </entry>
    <entry group="0012" element="0064" name="De-identification Method Code Sequence" type="1C">
      <description>A code describing the mechanism or method use to remove the patient's identity. One or more Items shall be present. Multiple items are used if successive de-identification steps have been performed
Required if Patient Identity Removed (0012,0062) is present and has a value of YES and De-identification Method (0012,0063) is not present.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined."/>
  </module>
  <module ref="C.7.1.2" table="C.7-2a" name="Specimen Identification Module Attributes">
    <entry group="0040" element="050A" name="Specimen Accession Number" type="1">
      <description>A departmental Information System identifier that identifies the Accession. See Section C.7.1.2.1.1 for further explanation.</description>
      <section ref="C.7.1.2.1.1" name="">Specimen Accession Number (0040,050A) is the primary identifier of the Specimen.
Note:   Specimen Accession Number (0040,050A) identifies tissue or fluid obtained from a Patient in a Specimen-harvest procedure. This Attribute was created to differentiate Accession Numbers, as used in Anatomic Pathology to identify specimens, from other uses of the term “Accession Number” in Information Systems. The Specimen Accession Number (0040,050A) is typically unique within the scope of the institution in which the Accession is performed. An Accession may contain multiple Specimens. Typically, an Accession contains the Specimens obtained in one Specimen-harvest procedure and submitted by one Requesting Physician. However, multiple Specimen-harvest procedures may be involved.

</section>
    </entry>
    <entry group="0040" element="0550" name="Specimen Sequence" type="2">
      <description>Detailed description of one or more specimens. Zero or more Items may be included in this Sequence.</description>
    </entry>
    <entry group="0040" element="0551" name="&gt;Specimen Identifier" type="2">
      <description>A departmental information system identifier for the Specimen. See Section C.7.1.2.1.2 for further explanation.</description>
      <section ref="C.7.1.2.1.2" name="">Specimen Identifier (0040,0551) may be used to convey a slide number, a block number, or other secondary identifier of the Specimen.
Note:   The Specimen Identifier (0040,0551) is typically unique within the scope of the institution in which the related Accession is performed. However, a value of Specimen Identifier (0040,0551) does not always exist. For example, it is common practice in some Anatomic Pathology departments to use a Specimen Identifier (0040,0551) to identify specimen-containers or blocks only if multiple containers or blocks are submitted for a single Accession. Therefore, Specimen Identifier (0040,0551) is modeled as a Type 2 Attribute.

</section>
    </entry>
    <entry group="0040" element="059A" name="&gt;Specimen Type Code Sequence" type="2C">
      <description>Specimen Type. Only a single Item shall be permitted in this Sequence. Required if Specimen Identifier (0040,0551) is sent with a value.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context IDs are defined"/>
    <entry group="0040" element="06FA" name="&gt;Slide Identifier" type="2C">
      <description>Identifier of the Slide.
Required if the Specimen is a Slide.</description>
    </entry>
  </module>
  <module ref="C.7.1.3" table="C.7-2b" name="Clinical Trial Subject Module Attributes">
    <entry group="0012" element="0010" name="Clinical Trial Sponsor Name" type="1">
      <description>The name of the clinical trial sponsor. See C.7.1.3.1.1.</description>
      <section ref="C.7.1.3.1.1" name="">The Clinical Trial Sponsor Name (0012,0010) identifies the entity responsible for conducting the clinical trial and for defining the Clinical Trial Protocol ID (0012,0020).
</section>
    </entry>
    <entry group="0012" element="0020" name="Clinical Trial Protocol ID" type="1">
      <description>Identifier for the noted protocol. See C.7.1.3.1.2.</description>
      <section ref="C.7.1.3.1.2" name="">The Clinical Trial Protocol ID (0012,0020) is the number or character sequence used by the Clinical Trial Sponsor to uniquely identify the investigational protocol in which the subject has been enrolled.
</section>
    </entry>
    <entry group="0012" element="0021" name="Clinical Trial Protocol Name" type="2">
      <description>The name of the clinical trial protocol. See C.7.1.3.1.3.</description>
      <section ref="C.7.1.3.1.3" name="">The Clinical Trial Protocol Name (0012,0021) contains the title of the investigational protocol in which the subject has been enrolled.
Note:   It is recommended that the phase of the clinical trial be noted in the Clinical Trial Protocol Name, if applicable.
</section>
    </entry>
    <entry group="0012" element="0030" name="Clinical Trial Site ID" type="2">
      <description>The identifier of the site responsible for submitting clinical trial data. See C.7.1.3.1.4.</description>
      <section ref="C.7.1.3.1.4" name="">The Clinical Trial Site ID (0012,0030) is the identification number or character string (issued by the entity identified by the Clinical Trial Sponsor Name (0012,0010)) used to identify the site responsible for submitting clinical trial data.
</section>
    </entry>
    <entry group="0012" element="0031" name="Clinical Trial Site Name" type="2">
      <description>Name of the site responsible for submitting clinical trial data. See C.7.1.3.1.5</description>
      <section ref="C.7.1.3.1.5" name="">The Clinical Trial Site Name (0012,0031) is a character string used to identify the site responsible for submitting clinical trial data.
</section>
    </entry>
    <entry group="0012" element="0040" name="Clinical Trial Subject ID" type="1C">
      <description>The assigned identifier for the clinical trial subject. See C.7.1.3.1.6. Shall be present if Clinical Trial Subject Reading ID (0012,0042) is absent. May be present otherwise.</description>
      <section ref="C.7.1.3.1.6" name="">The Clinical Trial Subject ID (0012,0040) identifies the subject within the investigational protocol specified by Clinical Trial Protocol ID (0012,0020).
</section>
    </entry>
    <entry group="0012" element="0042" name="Clinical Trial Subject Reading ID" type="1C">
      <description>Identifies the subject for blinded evaluations. Shall be present if Clinical Trial Subject ID (0012,0040) is absent. May be present otherwise. See C.7.1.3.1.7.</description>
      <section ref="C.7.1.3.1.7" name="">The Clinical Trial Subject Reading ID (0012,0042) identifies the subject in the context of blinded evaluations.

</section>
    </entry>
  </module>
  <module ref="C.7.2.1" table="C.7-3" name="General Study Module Attributes">
    <entry group="0020" element="000D" name="Study Instance UID" type="1">
      <description>Unique identifier for the Study.</description>
    </entry>
    <entry group="0008" element="0020" name="Study Date" type="2">
      <description>Date the Study started.</description>
    </entry>
    <entry group="0008" element="0030" name="Study Time" type="2">
      <description>Time the Study started.</description>
    </entry>
    <entry group="0008" element="0090" name="Referring Physician's Name" type="2">
      <description>Name of the patient's referring physician</description>
    </entry>
    <entry group="0008" element="0096" name="Referring Physician Identification Sequence" type="3">
      <description>Identification of the patient's referring physician. Only a single item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Person Identification Macro' Table 10-1"/>
    <entry group="0020" element="0010" name="Study ID" type="2">
      <description>User or equipment generated Study identifier.</description>
    </entry>
    <entry group="0008" element="0050" name="Accession Number" type="2">
      <description>A RIS generated number that identifies the order for the Study.</description>
    </entry>
    <entry group="0008" element="1030" name="Study Description" type="3">
      <description>Institution-generated description or classification of the Study (component) performed.</description>
    </entry>
    <entry group="0008" element="1048" name="Physician(s) of Record" type="3">
      <description>Names of the physician(s) who are responsible for overall patient care at time of Study (see Section C.7.3.1 for Performing Physician)</description>
    </entry>
    <entry group="0008" element="1049" name="Physician(s) of Record Identification Sequence" type="3">
      <description>Identification of the physician(s) who are responsible for overall patient care at time of Study. One or more items shall be included in this sequence. If more than one Item, the number and order shall correspond to the value of Physician(s) of Record (0008,1048), if present.</description>
    </entry>
    <include ref="&gt;Include 'Person Identification Macro' Table 10-1"/>
    <entry group="0008" element="1060" name="Name of Physician(s) Reading Study" type="3">
      <description>Names of the physician(s) reading the Study.</description>
    </entry>
    <entry group="0008" element="1062" name="Physician(s) Reading Study Identification Sequence" type="3">
      <description>Identification of the physician(s) reading the Study. One or more items shall be included in this sequence. If more than one Item, the number and order shall correspond to the value of Name of Physician(s) Reading Study (0008,1060), if present.</description>
    </entry>
    <include ref="&gt;Include 'Person Identification Macro' Table 10-1"/>
    <entry group="0008" element="1110" name="Referenced Study Sequence" type="3">
      <description>A sequence that provides reference to a Study SOP Class/Instance pair. The sequence may have zero or more Items.</description>
    </entry>
    <include ref="&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="0008" element="1032" name="Procedure Code Sequence" type="3">
      <description>A Sequence that conveys the type of procedure performed. One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
  </module>
  <module ref="C.7.2.2" table="C.7-4a" name="Patient Study Module Attributes">
    <entry group="0008" element="1080" name="Admitting Diagnoses Description" type="3">
      <description>Description of the admitting diagnosis (diagnoses)</description>
    </entry>
    <entry group="0008" element="1084" name="Admitting Diagnoses Code Sequence" type="3">
      <description>A sequence that conveys the admitting diagnosis (diagnoses). One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0010" element="1010" name="Patient's Age" type="3">
      <description>Age of the Patient.</description>
    </entry>
    <entry group="0010" element="1020" name="Patient's Size" type="3">
      <description>Length or size of the Patient, in meters.</description>
    </entry>
    <entry group="0010" element="1030" name="Patient's Weight" type="3">
      <description>Weight of the Patient, in kilograms.</description>
    </entry>
    <entry group="0010" element="2180" name="Occupation" type="3">
      <description>Occupation of the Patient.</description>
    </entry>
    <entry group="0010" element="21B0" name="Additional Patient's History" type="3">
      <description>Additional information about the Patient's medical history.</description>
    </entry>
    <entry group="0038" element="0010" name="Admission ID" type="3">
      <description>Identification number of the visit as assigned by the healthcare provider</description>
    </entry>
    <entry group="0038" element="0011" name="Issuer of Admission ID" type="3">
      <description>Name of healthcare provider that issued the Admission ID</description>
    </entry>
    <entry group="0038" element="0060" name="Service Episode ID" type="3">
      <description>Identifier of the Service Episode as assigned by the healthcare provider</description>
    </entry>
    <entry group="0038" element="0061" name="Issuer of Service Episode ID" type="3">
      <description>Name of healthcare provider that issued the Service Episode ID</description>
    </entry>
    <entry group="0038" element="0062" name="Service Episode Description" type="3">
      <description>Description of the type of service episode.</description>
    </entry>
    <entry group="0010" element="2203" name="Patient's Sex Neutered" type="2C">
      <description>Whether or not a procedure has been performed in an effort to render the patient sterile.
Enumerated value:
ALTERED = Altered/Neutered
UNALTERED = Unaltered/intact
Note: If this Attribute is present but has no value then the status is unknown.
Required if patient is an animal. May be present otherwise.</description>
    </entry>
  </module>
  <module ref="C.7.2.3" table="C.7-4b" name="Clinical Trial Study Module Attributes">
    <entry group="0012" element="0050" name="Clinical Trial Time Point ID" type="2">
      <description>An identifier specifying the one or more studies that are grouped together as a clinical time point or submission in a clinical trial. See C.7.2.3.1.1.</description>
      <section ref="C.7.2.3.1.1" name="">The Clinical Trial Time Point ID (0012,0050) attribute identifies an imaging study within the context of an investigational protocol. This attribute is used to define a set of studies that are grouped together as a clinical time point or data submission in a clinical trial. The Clinical Trial Time Point Description (0012,0051) attribute can be used to give a description of the Clinical Trial Time Point to which the set of studies belongs.
</section>
    </entry>
    <entry group="0012" element="0051" name="Clinical Trial Time Point Description" type="3">
      <description>A description of a set of one or more studies that are grouped together to represent a clinical time point or submission in a clinical trial. See C.7.2.3.1.1.</description>
      <section ref="C.7.2.3.1.1" name="">The Clinical Trial Time Point ID (0012,0050) attribute identifies an imaging study within the context of an investigational protocol. This attribute is used to define a set of studies that are grouped together as a clinical time point or data submission in a clinical trial. The Clinical Trial Time Point Description (0012,0051) attribute can be used to give a description of the Clinical Trial Time Point to which the set of studies belongs.
</section>
    </entry>
  </module>
  <module ref="C.7.3.1" table="C.7-5a" name="General Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Type of equipment that originally acquired the data used to create the images in this Series. See C.7.3.1.1.1 for Defined Terms.</description>
      <section ref="C.7.3.1.1.1" name="">Defined Terms for the Modality (0008,0060) are:
<defined-terms><term value="CR" meaning="Computed Radiography"/><term value="MR" meaning="Magnetic Resonance"/><term value="US" meaning="Ultrasound"/><term value="BI" meaning="Biomagnetic imaging"/><term value="DD" meaning="Duplex Doppler"/><term value="ES" meaning="Endoscopy"/><term value=""/><term value="PT" meaning="Positron emission tomography (PET)"/><term value="ST" meaning="Single-photon emission computed tomography (SPECT)"/><term value="XA" meaning="X-Ray Angiography"/><term value="RTIMAGE" meaning="Radiotherapy Image"/><term value="RTSTRUCT" meaning="Radiotherapy Structure Set"/><term value="RTRECORD" meaning="RT Treatment Record"/><term value="DX" meaning="Digital Radiography"/><term value="IO" meaning="Intra-oral Radiography"/><term value="GM" meaning="General Microscopy"/><term value="XC" meaning="External-camera Photography"/><term value="AU" meaning="Audio"/><term value="EPS" meaning="Cardiac Electrophysiology"/><term value="SR" meaning="SR Document"/><term value="OP" meaning="Ophthalmic Photography"/><term value="OCT" meaning="Optical Coherence Tomography (non-Ophthalmic)"/><term value="OPV" meaning="Ophthalmic Visual Field"/><term value="KO" meaning="Key Object Selection"/><term value="REG" meaning="Registration"/><term value="BDUS" meaning="Bone Densitometry (ultrasound)"/><term value="DOC" meaning="Document"/></defined-terms>
Retired Defined Terms for the Modality (0008,0060) are:
<retired-defined-terms><term value="DS" meaning="Digital Subtraction Angiography (retired)"/><term value="DF" meaning="Digital fluoroscopy (retired)"/><term value="AS" meaning="Angioscopy"/><term value="EC" meaning="Echocardiography"/><term value="FA" meaning="Fluorescein angiography"/><term value="DM" meaning="Digital microscopy"/><term value="MA" meaning="Magnetic resonance angiography"/></retired-defined-terms>
Note:  1. The XA modality incorporates the retired modality DS.
  2. The RF modality incorporates the retired modalities CF, DF, VF.
  3. The modality listed in the Modality Data Element (0008,0060) may not match the name of the IOD in which it appears. For example, a SOP instance from XA IOD may list the RF modality when an RF implementation produces an XA object.
  4. The MR modality incorporates the retired modalities MA and MS.

</section>
    </entry>
    <entry group="0020" element="000E" name="Series Instance UID" type="1">
      <description>Unique identifier of the Series.</description>
    </entry>
    <entry group="0020" element="0011" name="Series Number" type="2">
      <description>A number that identifies this Series.</description>
    </entry>
    <entry group="0020" element="0060" name="Laterality" type="2C">
      <description>Laterality of (paired) body part examined. Required if the body part examined is a paired structure and Image Laterality (0020,0062) or Frame Laterality (0020,9072) are not sent. Enumerated Values:
R = right
L = left
Note: Some IODs support Image Laterality (0020,0062) at the Image level or Frame Laterality(0020,9072) at the Frame level in the Frame Anatomy functional group macro, which can provide a more comprehensive mechanism for specifying the laterality of the body part(s) being examined.</description>
    </entry>
    <entry group="0008" element="0021" name="Series Date" type="3">
      <description>Date the Series started.</description>
    </entry>
    <entry group="0008" element="0031" name="Series Time" type="3">
      <description>Time the Series started.</description>
    </entry>
    <entry group="0008" element="1050" name="Performing Physicians' Name" type="3">
      <description>Name of the physician(s) administering the Series.</description>
    </entry>
    <entry group="0008" element="1052" name="Performing Physician Identification Sequence" type="3">
      <description>Identification of the physician(s) administering the Series. One or more items shall be included in this sequence. If more than one Item, the number and order shall correspond to the value of Performing Physicians' Name (0008,1050), if present.</description>
    </entry>
    <include ref="&gt;Include 'Person Identification Macro' Table 10-1"/>
    <entry group="0018" element="1030" name="Protocol Name" type="3">
      <description>User-defined description of the conditions under which the Series was performed.
Note: This attribute conveys series-specific protocol identification and may or may not be identical to the one presented in the Performed Protocol Code Sequence (0040,0260).</description>
    </entry>
    <entry group="0008" element="103E" name="Series Description" type="3">
      <description>User provided description of the Series</description>
    </entry>
    <entry group="0008" element="1070" name="Operators' Name" type="3">
      <description>Name(s) of the operator(s) supporting the Series.</description>
    </entry>
    <entry group="0008" element="1072" name="Operator Identification Sequence" type="3">
      <description>Identification of the operator(s) supporting the Series. One or more items shall be included in this sequence. If more than one Item, the number and order shall correspond to the value of Operators' Name (0008,1070), if present.</description>
    </entry>
    <include ref="&gt;Include 'Person Identification Macro' Table 10-1"/>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence" type="3">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance to which the Series is related (e.g. a Modality or General-Purpose Performed Procedure Step SOP Instance). The Sequence shall have zero or one Item.</description>
    </entry>
    <include ref="&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="0008" element="1250" name="Related Series Sequence" type="3">
      <description>Identification of Series significantly related to this Series. Zero or more Items may be present.
Notes: 1. For example, for a combined CT and PET acquisition, the CT images and PET images would be in separate series that could cross-reference each other with multiple purpose of reference codes meaning same anatomy, simultaneously acquired and same indication.
2. The related series may have different Frames of Reference and hence require some sort of registration before spatial coordinates can be directly compared.
3. This attribute is not intended for conveying localizer reference information, for which Referenced Image Sequence (0008,1140) should be used.</description>
    </entry>
    <entry group="0020" element="000D" name="&gt;Study Instance UID" type="1">
      <description>Instance UID of Study to which the related Series belongs</description>
    </entry>
    <entry group="0020" element="000E" name="&gt;Series Instance UID" type="1">
      <description>Instance UID of Related Series</description>
    </entry>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="2">
      <description>Describes the purpose for which the reference is made. Zero or more Items may be present.
When absent, implies that the reason for the reference is unknown.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="DCID 7210"/>
    <entry group="0018" element="0015" name="Body Part Examined" type="3">
      <description>Text description of the part of the body examined. See PS 3.16 Annex on Correspondence of Anatomic Region Codes and Body Part Examined for Defined Terms
Note: Some IODs support the Anatomic Region Sequence (0008,2218), which can provide a more comprehensive mechanism for specifying the body part being examined.</description>
    </entry>
    <entry group="0018" element="5100" name="Patient Position" type="2C">
      <description>Patient position descriptor relative to the equipment. Required for CT and MR images; shall not be present if Patient Orientation Code Sequence (0054,0410) is present; may be present otherwise. See C.7.3.1.1.2 for Defined Terms and further explanation.</description>
      <section ref="C.7.3.1.1.2" name="">Patient Position (0018,5100) specifies the position of the patient relative to the imaging equipment space. This attribute is intended for annotation purposes only. It does not provide an exact mathematical relationship of the patient to the imaging equipment.
When facing the front of the imaging equipment, Head First is defined as the patient’s head being positioned toward the front of the imaging equipment. Feet First is defined as the patient’s feet being positioned toward the front of the imaging equipment. Prone is defined as the patient’s face being positioned in a downward (gravity) direction. Supine is defined as the patient’s face being in an upward direction. Decubitus Right is defined as the patient’s right side being in a downward direction. Decubitus Left is defined as the patient’s left side being in a downward direction.
The Defined Terms are:
<defined-terms><term value="HFP&#9;= Head First-Prone"/><term value="HFS&#9;= Head First-Supine"/><term value="HFDR&#9;= Head First-Decubitus Right"/><term value="HFDL&#9;= Head First-Decubitus Left"/><term value="FFDR&#9;= Feet First-Decubitus Right"/><term value="FFDL&#9;= Feet First-Decubitus Left"/><term value="FFP&#9;= Feet First-Prone"/><term value="FFS&#9;= Feet First-Supine"/></defined-terms>
         </section>
    </entry>
    <entry group="0028" element="0108" name="Smallest Pixel Value in Series" type="3">
      <description>The minimum value of all images in this Series.</description>
    </entry>
    <entry group="0028" element="0109" name="Largest Pixel Value in Series" type="3">
      <description>The maximum value of all images in this Series.</description>
    </entry>
    <entry group="0040" element="0275" name="Request Attributes Sequence" type="3">
      <description>Sequence that contains attributes from the Imaging Service Request.
The sequence may have one or more Items.</description>
    </entry>
    <include ref="&gt;Include Request Attributes Macro Table 10-9" description="No Baseline Context IDs defined"/>
    <include ref="Include Performed Procedure Step Summary Macro Table 10-16" description="No Baseline Context IDs defined"/>
  </module>
  <module ref="C.7.3.2" table="C.7-5b" name="Clinical Trial Series Module Attributes">
    <entry group="0012" element="0060" name="Clinical Trial Coordinating Center Name" type="2">
      <description>The name of the institution that is responsible for coordinating the medical imaging data for the clinical trial. See C.7.3.2.1.1.</description>
      <section ref="C.7.3.2.1.1" name="">The Clinical Trial Coordinating Center Name (0012,0060) identifies the institution responsible for coordinating the collection of images and associated data for subjects enrolled in the clinical trial.
</section>
    </entry>
    <entry group="0012" element="0071" name="Clinical Trial Series ID" type="3">
      <description>An identifier of the series in the context of a clinical trial. See C.7.3.2.1.2.</description>
      <section ref="C.7.3.2.1.2" name="">The Clinical Trial Series ID (0012,0071) and Clinical Trial Series Description (0012,0072) attributes can be used to identify and describe a Series within the context of a clinical trial without requiring the replacement of the values in the Series Number (0020,0011) and Series Description (0008,103E) attributes in the General Series Module, whose manufacturer or user provided values may be relevant and important to retain.
</section>
    </entry>
    <entry group="0012" element="0072" name="Clinical Trial Series Description" type="3">
      <description>A description of the series in the context of a clinical trial. See C.7.3.2.1.2.</description>
      <section ref="C.7.3.2.1.2" name="">The Clinical Trial Series ID (0012,0071) and Clinical Trial Series Description (0012,0072) attributes can be used to identify and describe a Series within the context of a clinical trial without requiring the replacement of the values in the Series Number (0020,0011) and Series Description (0008,103E) attributes in the General Series Module, whose manufacturer or user provided values may be relevant and important to retain.
</section>
    </entry>
  </module>
  <module ref="C.7.3.3" table="C.7-5c" name="Enhanced Series Module Attributes">
    <entry group="0020" element="0011" name="Series Number" type="1">
      <description>A number that identifies this Series.
Notes: 1. The value of this attribute should be unique for all series in a study created on the same equipment.
2. Because series can be created on more than one equipment, it can not be guranteed that the value of Series Number (0020,0011) is unique in a study.</description>
    </entry>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence" type="1C">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance to which the Series is related (e.g. a Modality or General-Purpose Performed Procedure Step SOP Instance). Only a single Item is permitted in this sequence.
Required if the Modality Performed Procedure Step SOP Class or General Purpose Performed Procedure Step SOP Class is supported.</description>
    </entry>
    <include ref="&gt;Include SOP Instance Reference Macro Table 10-11"/>
  </module>
  <module ref="C.7.4.1" table="C.7-6" name="Frame of Reference Module Attributes">
    <entry group="0020" element="0052" name="Frame of Reference UID" type="1">
      <description>Uniquely identifies the frame of reference for a Series. See C.7.4.1.1.1 for further explanation.</description>
      <section ref="C.7.4.1.1.1" name="">The Frame of Reference UID (0020,0052) shall be used to uniquely identify a frame of reference for a series. Each series shall have a single Frame of Reference UID. However, multiple Series within a Study may share a Frame of Reference UID. All images in a Series that share the same Frame of Reference UID shall be spatially related to each other.
Notes:  1. Previous versions of this Standard defined a Data Element "Location", which has been retired. Frame of Reference UID provides a completely unambiguous identification of the image location reference used to indicate position.
  2. A common Frame of Reference UID may be used to spatially relate localizer images with a set of transverse images. However, in some cases (eg. multiple localizer images being related to a single set of transverse images) a common Frame of Reference UID may not be sufficient. The Referenced Image Sequence (0008,1140) provides an unambiguous method for relating localizer images.

</section>
    </entry>
    <entry group="0020" element="1040" name="Position Reference Indicator" type="2">
      <description>Part of the patient's anatomy used as a reference, such as the iliac crest, orbital-medial, sternal notch, symphysis pubis, xiphoid, lower coastal margin, external auditory meatus. See C.7.4.1.1.2 for further explanation.</description>
      <section ref="C.7.4.1.1.2" name="">The Position Reference Indicator (0020,1040) specifies the part of the patient’s anatomy that was used as an anatomical reference point associated with a specific Frame of Reference UID. The Position Reference Indicator may or may not coincide with the origin of the fixed frame of reference related to the Frame of Reference UID.
The Position Reference Indicator shall be used only for annotation purposes and is not intended to be used as a mathematical spatial reference.
Note:  The Position Reference Indicator may be sent zero length when it has no meaning, for example, when the Frame of Reference Module is required to relate mammographic images of the breast acquired without releasing breast compression, but where there is no meaningful anatomical reference point as such.

</section>
    </entry>
  </module>
  <module ref="C.7.4.2" table="C.7-7" name="Synchronization Module Attributes">
    <entry group="0020" element="0200" name="Synchronization Frame of Reference UID" type="1">
      <description>UID of common synchronization environment. See C.7.4.2.1.1.</description>
      <section ref="C.7.4.2.1.1" name="">A set of equipment may share a common acquisition synchronization environment, which is identified by a Synchronization Frame of Reference UID. All SOP Instances that share the same Synchronization Frame of Reference UID shall be temporally related to each other. If a Synchronization Frame of Reference UID is present, all SOP Instances in the Series must share the same Frame of Reference.
The UTC Synchronization UID, 1.2.840.10008.15.1.1, may be used when the equipment is synchronized to the international standard UTC. In this case the quality of synchronization may be determined by means of the Time Distribution Protocol (0018,1802) and NTP Source Address (0018,1803).
Notes:  1. The Synchronization Frame of Reference UID defines an equipment synchronization environment, and does not need to be changed for each unrelated acquisition. SOP Instances may therefore share a Synchronization Frame of Reference UID, but be clinically unrelated (e.g., apply to different patients).
  2. When a synchronization environment is recalibrated, a new UID must be issued.
  3. The method of distributing the Synchronization Frame of Reference UID to multiple devices is not specified.

</section>
    </entry>
    <entry group="0018" element="106A" name="Synchronization Trigger" type="1">
      <description>Data acquisition synchronization with external equipment
Enumerated Values:
SOURCE - this equipment provides synchronization channel or trigger to other equipment
EXTERNAL - this equipment receives synchronization channel or trigger from other equipment
PASSTHRU - this equipment receives synchronization channel or trigger and forwards it
NO TRIGGER - data acquisition not synchronized by common channel or trigger</description>
    </entry>
    <entry group="0018" element="1061" name="Trigger Source or Type" type="3">
      <description>Specifies equipment ID of trigger source and/or type of trigger</description>
    </entry>
    <entry group="0018" element="106C" name="Synchronization Channel" type="1C">
      <description>Identifier of waveform channel that records the synchronization channel or trigger, see C.7.4.2.1.3.
Required if synchronization channel or trigger is encoded in a waveform in this SOP Instance</description>
    </entry>
    <entry group="0018" element="1800" name="Acquisition Time Synchronized" type="1">
      <description>Acquisition DateTime (0008,002A) synchronized with external time reference.
Enumerated Values: Y, N
See C.7.4.2.1.4</description>
      <section ref="C.7.4.2.1.4" name="">The Acquisition Time Synchronized (0018,1800) attribute specifies whether the Acquisition DateTime (0008,002A) attribute of the Waveform Identification Module or the General Image Module represents an accurate synchronized timestamp for the acquisition of the waveform and/or image data. For triggered multi-frame images, the Acquisition DateTime applies to the trigger for the first image frame (see attribute Image Trigger Delay (0018.1067) in the Cine Module).
Note:   The degree of precision of the Acquisition DateTime and its accuracy relative to the external clock are not specified, but need to be appropriate for the clinical application.

For IODs that include the SR Document Content Module, the Acquisition Time Synchronized (0018,1800) attribute specifies whether the Observation DateTime (0040,A032) attribute of Items in the Content Sequence (0040,A730) of the SR Document Content Module represents an accurate synchronized timestamp for the Item.
</section>
    </entry>
    <entry group="0018" element="1801" name="Time Source" type="3">
      <description>ID of equipment or system providing time reference</description>
    </entry>
    <entry group="0018" element="1802" name="Time Distribution Protocol" type="3">
      <description>Method of time distribution used to synchronize this equipment.
Defined Terms:
NTP - Network Time Protocol
IRIG - InterRange Instrumentation Group
GPS - Global Positioning System
SNTP - Simple Network Time Protocol</description>
    </entry>
    <entry group="0018" element="1803" name="NTP Source Address" type="3">
      <description>IP Address of NTP time source. IPv4 addresses shall be in dotted decimal (e.g. 192.168.1.1). The IPv6 addresses shall be in colon separated hexadecimal (e.g. 12:34:56:78:9a:bc:de:f0).
Note: Identity of this value in two instances acquired contemporaneously implies a common time base. The NTP Source Address may not persist over time.</description>
    </entry>
  </module>
  <module ref="C.7.5.1" table="C.7-8" name="General Equipment Module Attributes">
    <entry group="0008" element="0070" name="Manufacturer" type="2">
      <description>Manufacturer of the equipment that produced the composite instances.</description>
    </entry>
    <entry group="0008" element="0080" name="Institution Name" type="3">
      <description>Institution where the equipment that produced the composite instances is located.</description>
    </entry>
    <entry group="0008" element="0081" name="Institution Address" type="3">
      <description>Mailing address of the institution where the equipment that produced the composite instances is located.</description>
    </entry>
    <entry group="0008" element="1010" name="Station Name" type="3">
      <description>User defined name identifying the machine that produced the composite instances.</description>
    </entry>
    <entry group="0008" element="1040" name="Institutional Department Name" type="3">
      <description>Department in the institution where the equipment that produced the composite instances is located.</description>
    </entry>
    <entry group="0008" element="1090" name="Manufacturer's Model Name" type="3">
      <description>Manufacturer's model name of the equipment that produced the composite instances.</description>
    </entry>
    <entry group="0018" element="1000" name="Device Serial Number" type="3">
      <description>Manufacturer's serial number of the equipment that produced the composite instances.
Note: This identifier corresponds to the device that actually created the images, such as a CR plate reader or a CT console, and may not be sufficient to identify all of the equipment in the imaging chain, such as the generator or gantry or plate.</description>
    </entry>
    <entry group="0018" element="1020" name="Software Versions" type="3">
      <description>Manufacturer's designation of software version of the equipment that produced the composite instances.</description>
    </entry>
    <entry group="0018" element="1008" name="Gantry ID" type="3">
      <description>Identifier of the gantry or positioner.</description>
    </entry>
    <entry group="0018" element="1050" name="Spatial Resolution" type="3">
      <description>The inherent limiting resolution in mm of the acquisition equipment for high contrast objects for the data gathering and reconstruction technique chosen. If variable across the images of the series, the value at the image center.</description>
    </entry>
    <entry group="0018" element="1200" name="Date of Last Calibration" type="3">
      <description>Date when the image acquisition device calibration was last changed in any way. Multiple entries may be used for additional calibrations at other times. See C.7.5.1.1.1 for further explanation.</description>
      <section ref="C.7.5.1.1.1" name="">Date of Last Calibration (0018,1200) and Time of Last Calibration (0018,1201) are used to convey the date and time of calibration. The Attribute Date of Last Calibration (0018,1200) may be supported alone, however, Time of Last Calibration (0018,1201) Attribute has no meaning unless Attribute Date of Last Calibration (0018,1200) is also supported. The order for each Attribute shall be from the oldest date/time to the most recent date/time. When the Attributes are both supported they shall be provided as pairs.
</section>
    </entry>
    <entry group="0018" element="1201" name="Time of Last Calibration" type="3">
      <description>Time when the image acquisition device calibration was last changed in any way. Multiple entries may be used. See C.7.5.1.1.1 for further explanation.</description>
      <section ref="C.7.5.1.1.1" name="">Date of Last Calibration (0018,1200) and Time of Last Calibration (0018,1201) are used to convey the date and time of calibration. The Attribute Date of Last Calibration (0018,1200) may be supported alone, however, Time of Last Calibration (0018,1201) Attribute has no meaning unless Attribute Date of Last Calibration (0018,1200) is also supported. The order for each Attribute shall be from the oldest date/time to the most recent date/time. When the Attributes are both supported they shall be provided as pairs.
</section>
    </entry>
    <entry group="0028" element="0120" name="Pixel Padding Value" type="1C">
      <description>Single pixel value or one limit (inclusive) of a range of pixel values used in animage to pad to rectangular format or to signal background that may be suppressed. See C.7.5.1.1.2 for further explanation.
Required if Pixel Padding Range Limit (0028,0121) is present. May be present otherwise.
Note: The Value Representation of this Attribute is determined by the value of Pixel Representation (0028,0103).</description>
      <section ref="C.7.5.1.1.2" name="">Pixel Padding Value (0028,0120) is used to pad grayscale images (those with a Photometric Interpretation of MONOCHROME1 or MONOCHROME2)to rectangular format. The native format of some images is not rectangular. It is common for devices with this format to pad the images to the rectangular format required by the DICOM Standard with a specific pixel value that is not contained in the native image. Further, when resampling, such as after spatial registration, padding may need to be used to fill previously non-existent pixels.
Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) are also used to identify pixels to be excluded from the normal grayscale rendering pipeline for other reasons, such as suppression of background air. Pixel Padding Range Limit (0028,0121) is defined in the Image Pixel Module.
Notes:  1. The “native image” is that which is being padded to the required rectangular format, e.g., the area within the circular reconstruction perimeter of a CT image, or the subset of the rectangular area that contains useful image information.
  2. The pixel padding value is explicitly described in order to prevent display applications from taking it into account when determining the dynamic range of an image, since the Pixel Padding Value will be outside the range between the minimum and maximum values of the pixels in the native image
  3. No pixels in the native image will have a value equal to Pixel Padding Value.

Pixel Padding Value (0028,0120) specifies either a single value of this padding value, or when combined with Pixel Padding Range Limit (0028,0121), a range of values (inclusive) that are padding.
The values of Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) shall be valid values within the constraints defined by Bits Allocated (0028,0100), Bits Stored (0028,0101), and High Bit (0028,0102).
Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) shall not be present when padding is performed but the pixel value used for padding does occur in the native image.
If Photometric Interpretation (0028,0004) is MONOCHROME2, Pixel Padding Value (0028,0120) shall be less than (closer to or equal to the minimum possible pixel value) or equal to Pixel Padding Range Limit (0028,0121). If Photometric Interpretation (0028,0004) is MONOCHROME1, Pixel Padding Value (0028,0120) shall be greater than (closer to or equal to the maximum possible pixel value) or equal to Pixel Padding Range Limit (0028,0121).
Notes:  1. When the relationship between pixel value and X-Ray Intensity is unknown, it is recommended that the following values be used to pad with black when the image is unsigned:
  0 if Photometric Interpretation (0028,0004) is MONOCHROME2.
  2BitsStored - 1 if Photometric Interpretation (0028,0004) is MONOCHROME1.
  and when the image is signed:
    -2BitsStored-1 if Photometric Interpretation (0028,0004) is MONOCHROME2.
  2BitsStored-1 - 1 if Photometric Interpretation (0028,0004) is MONOCHROME1.
  2. For projection radiography, when the relationship between pixel value and X-Ray Intensity is known (for example as defined by Pixel Intensity Relationship (0028,1040) and Pixel Intensity relationship Sign (0028,1041)), it is recommended that a pixel value equivalent to, or rendered similarly to, air (least X-Ray absorbance) be used for padding. However, if such a value may occur in the native image, the Pixel Padding Value (0028,0120) Attribute itself should not be sent.
  E.g., for an XRF image obtained with an image intensifier, if air is black then a padded perimeter, if any, should also appear black. Typically though, if unpadded, this area would be collimated with a circular collimator, in which case the pixels would appear natively as white (greatest X-Ray absorbance) and a circular shutter would be necessary to neutralize them as black. Whether collimated areas are detected and treated as padded, or neutralized with shutters is at the discretion of the application. See also the Display Shutter Module C.7.6.11.
  3. The conditional requirement for the Pixel Padding Value Range Limit (0028,0121) in the Image Pixel Module means that it shall not be present unless Pixel Padding Value (0028,0120) is also present.
  4. The range of values to be suppressed between Pixel Padding Value (0028,0120) and Pixel Padding Value Range Limit (0028,0121) is specified as being inclusive, that is the values themselves as well as all values between are suppressed.
  5. When Pixel Padding Value Range Limit (0028,0121) is present, but not supported by a rendering application, the constraint that Pixel Padding Value (0028,0120) is closest to the “blackest” value, which is typically the most frequently occurring background pixel, will most often result in an acceptable display, permitting “backward compatibility” in the majority of cases.

When modifying equipment changes the pixel padding value in the image, it shall change the values of Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121), if present. If modifying equipment changes the pixel padding values in the image to values present in the native image, the attribute Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) shall be removed.
Notes:  1. For example, if a CT image containing signed values from -1024 to 3191 and a Pixel Padding Value of -2000 and a Rescale Intercept of 0 is converted to an unsigned image with a Rescale Intercept of -1024 by adding 1024 to all pixels and clipping all more negative pixels to 0, then the padding pixels will be indistinguishable from some of the modified native image pixels, and hence Pixel Padding Value (0028,0120) needs to be removed.
  2. If the modification involves lossy compression, which may result in changes to the pixel values, then the application of Pixel Padding Value and Pixel Padding Range Limit may result in a different appearance, and hence these attributes may need different values also.

</section>
    </entry>
  </module>
  <module ref="C.7.5.2" table="C.7-8b" name="Enhanced General Equipment Module Attributes">
    <entry group="0008" element="0070" name="Manufacturer" type="1">
      <description>Manufacturer of the equipment that produced the composite instances.</description>
    </entry>
    <entry group="0008" element="1090" name="Manufacturer's Model Name" type="1">
      <description>Manufacturer's model name of the equipment that produced the composite instances.</description>
    </entry>
    <entry group="0018" element="1000" name="Device Serial Number" type="1">
      <description>Manufacturer's serial number of the equipment that produced the composite instances.</description>
    </entry>
    <entry group="0018" element="1020" name="Software Versions" type="1">
      <description>Manufacturer's designation of software version of the equipment that produced the composite instances.</description>
    </entry>
  </module>
  <module ref="C.7.6.1" table="C.7-9" name="General Image Module Attributes">
    <entry group="0020" element="0013" name="Instance Number" type="2">
      <description>A number that identifies this image.
Note: This Attribute was named Image Number in earlier versions of this Standard.</description>
    </entry>
    <entry group="0020" element="0020" name="Patient Orientation" type="2C">
      <description>Patient direction of the rows and columns of the image. Required if image does not require Image Orientation (Patient) (0020,0037) and Image Position (Patient) (0020,0032). See C.7.6.1.1.1 for further explanation.
Note: IOD's may have attributes other than Patient Orientation, Image Orientation, or Image Position (Patient) to describe orientation in which case this attribute will be zero length.</description>
      <section ref="C.7.6.1.1.1" name="">The Patient Orientation (0020,0020) relative to the image plane shall be specified by two values that designate the anatomical direction of the positive row axis (left to right) and the positive column axis (top to bottom). The first entry is the direction of the rows, given by the direction of the last pixel in the first row from the first pixel in that row. The second entry is the direction of the columns, given by the direction of the last pixel in the first column from the first pixel in that column.
Anatomical direction shall be designated by the capital letters: A (anterior), P (posterior), R (right), L (left), H (head), F (foot). Each value of the orientation attribute shall contain at least one of these characters. If refinements in the orientation descriptions are to be specified, then they shall be designated by one or two additional letters in each value. Within each value, the letters shall be ordered with the principal orientation designated in the first character.
</section>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="2C">
      <description>The date the image pixel data creation started. Required if image is part of a series in which the images are temporally related.
Note: This Attribute was formerly known as Image Date.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="2C">
      <description>The time the image pixel data creation started. Required if image is part of a series in which the images are temporally related.</description>
    </entry>
    <entry group="0008" element="0008" name="Image Type" type="3">
      <description>Image identification characteristics. See C.7.6.1.1.2 for Defined Terms and further explanation.</description>
      <section ref="C.7.6.1.1.2" name="">The Image Type (0008,0008) Attribute identifies important image identification characteristics. These characteristics are:
a.  Pixel Data Characteristics
1.  is the image an ORIGINAL Image; an image whose pixel values are based on original or source data
2.  is the image a DERIVED Image; an image whose pixel values have been derived in some manner from the pixel value of one or more other images
b.  Patient Examination Characteristics
1.  is the image a PRIMARY Image; an image created as a direct result of the Patient examination
2.  is the image a SECONDARY Image; an image created after the initial Patient examination
c.  Modality Specific Characteristics
d.  Implementation specific identifiers; other implementation specific identifiers shall be documented in an implementation's conformance statement.
The Image Type attribute is multi-valued and shall be provided in the following manner:
a.  Value 1 shall identify the Pixel Data Characteristics; Enumerated Values for the Pixel Data Characteristics are:
ORIGINAL    identifies an Original Image
DERIVED    identifies a Derived Image
b.  Value 2 shall identify the Patient Examination Characteristics; Enumerated Values for the Patient Examination Characteristics are:
PRIMARY    identifies a Primary Image
SECONDARY  identifies a Secondary Image
c.  Value 3 shall identify any Image IOD specific specialization (optional)
d.  Other Values which are implementation specific (optional)
Any of the optional values (value 3 and beyond) may be sent either with a value or zero-length, independent of other optional values, unless otherwise specified by a specialization of this attribute in an IOD.
If the pixel data of the derived Image is different from the pixel data of the source images and this difference is expected to affect professional interpretation of the image, the Derived Image shall have a UID different than all the source images.
</section>
    </entry>
    <entry group="0020" element="0012" name="Acquisition Number" type="3">
      <description>A number identifying the single continuous gathering of data over a period of time that resulted in this image.</description>
    </entry>
    <entry group="0008" element="0022" name="Acquisition Date" type="3">
      <description>The date the acquisition of data that resulted in this image started</description>
    </entry>
    <entry group="0008" element="0032" name="Acquisition Time" type="3">
      <description>The time the acquisition of data that resulted in this image started</description>
    </entry>
    <entry group="0008" element="002A" name="Acquisition DateTime" type="3">
      <description>The date and time that the acquisition of data that resulted in this image started.
Note: The synchronization of this time with an external clock is specified in the Synchronization Module in Acquisition Time Synchronized (0018,1800).</description>
    </entry>
    <entry group="0008" element="1140" name="Referenced Image Sequence" type="3">
      <description>A sequence that references other images significantly related to this image (e.g. post-localizer CT image or Mammographic biopsy or partial view images). One or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="3">
      <description>Describes the purpose for which the reference is made. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 7201."/>
    <entry group="0008" element="2111" name="Derivation Description" type="3">
      <description>A text description of how this image was derived. See C.7.6.1.1.3 for further explanation.</description>
      <section ref="C.7.6.1.1.3" name="">If an Image is identified to be a derived image (see C.7.6.1.1.2 Image Type), Derivation Description (0008,2111) and Derivation Code Sequence (0008,9215) describe the way in which the image was derived. They may be used whether or not the Source Image Sequence (0008,2112) is provided. They may also be used in cases when the Derived Image pixel data is not significantly changed from one of the source images and the SOP Instance UID of the Derived Image is the same as the one used for the source image.
Notes:  1. Examples of Derived Images that would normally be expected to affect professional interpretation and would thus have a new UID include:
  a.  images resulting from image processing of another image (e.g. unsharp masking),
  b.  a multiplanar reformatted CT image,
  c.  a DSA image derived by subtracting pixel values of one image from another.
d.  an image that has been decompressed after having been compressed with a lossy compression algorithm. To ensure that the user has the necessary information about the lossy compression, the approximate compression ratio may be included in Derivation Description (0008,2111).
  An example of a Derived Image that would normally not be expected to affect professional interpretation and thus would not require a new UID is an image that has been padded with additional rows and columns for more display purposes.
  2. An image may be lossy compressed, e.g., for long term archive purposes, and its SOP Instance UID changed. PS3.4 provides a mechanism by which a query for the original image Instance may return a reference to the UID of the lossy compressed version of the image using the Alternate Representation Sequence (0008,3001). This allows an application processing a SOP Instance that references the original image UID, e.g., a Structured Report, to obtain a reference to an accessible version of the image even if the original SOP Instance is no longer available.

</section>
    </entry>
    <entry group="0008" element="9215" name="Derivation Code Sequence" type="3">
      <description>A coded description of how this image was derived. See C.7.6.1.1.3 for further explanation. One or more Items may be included in this Sequence. More than one Item indicates that successive derivation steps have been applied.</description>
      <section ref="C.7.6.1.1.3" name="">If an Image is identified to be a derived image (see C.7.6.1.1.2 Image Type), Derivation Description (0008,2111) and Derivation Code Sequence (0008,9215) describe the way in which the image was derived. They may be used whether or not the Source Image Sequence (0008,2112) is provided. They may also be used in cases when the Derived Image pixel data is not significantly changed from one of the source images and the SOP Instance UID of the Derived Image is the same as the one used for the source image.
Notes:  1. Examples of Derived Images that would normally be expected to affect professional interpretation and would thus have a new UID include:
  a.  images resulting from image processing of another image (e.g. unsharp masking),
  b.  a multiplanar reformatted CT image,
  c.  a DSA image derived by subtracting pixel values of one image from another.
d.  an image that has been decompressed after having been compressed with a lossy compression algorithm. To ensure that the user has the necessary information about the lossy compression, the approximate compression ratio may be included in Derivation Description (0008,2111).
  An example of a Derived Image that would normally not be expected to affect professional interpretation and thus would not require a new UID is an image that has been padded with additional rows and columns for more display purposes.
  2. An image may be lossy compressed, e.g., for long term archive purposes, and its SOP Instance UID changed. PS3.4 provides a mechanism by which a query for the original image Instance may return a reference to the UID of the lossy compressed version of the image using the Alternate Representation Sequence (0008,3001). This allows an application processing a SOP Instance that references the original image UID, e.g., a Structured Report, to obtain a reference to an accessible version of the image even if the original SOP Instance is no longer available.

</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 7203."/>
    <entry group="0008" element="2112" name="Source Image Sequence" type="3">
      <description>A Sequence that identifies the set of Image SOP Class/Instance pairs of the Images that were used to derive this Image. Zero or more Items may be included in this Sequence.
See C.7.6.1.1.4 for further explanation.</description>
      <section ref="C.7.6.1.1.4" name="">If an Image is identified to be a Derived image (see C.7.6.1.1.2 Image Type), Source Image Sequence (0008,2112) is an optional list of Referenced SOP Class UID (0008,1150)/ Referenced SOP Instance UID (0008,1150) pairs that identify the source images used to create the Derived image. It may be used whether or not there is a description of the way the image was derived in Derivation Description (0008,2111) or Derivation Code Sequence (0008,9215).
Note:  Multiple Items may be present within Source Image Sequence (0008,2112), in which case either:
  a) those images were combined to make the derived image (e.g. multiple source images to make an MPR or MIP), or
  b) each of the items represents a step in the successive derivation of an image (e.g. when an image has had successive lossy compression steps applied to it),
  c) some combination of the above.
  The Purpose of Reference Code Sequence (0040,A170) and the Attributes within the referenced images themselves may be used to determine the history of the derivation, which is not otherwise explicitly specified.

</section>
    </entry>
    <include ref="&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="3">
      <description>Describes the purpose for which the reference is made, that is what role the source image or frame(s) played in the derivation of this image. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 7202."/>
    <entry group="0028" element="135A" name="&gt;Spatial Locations Preserved" type="3">
      <description>The extent to which the spatial locations of all pixels are preserved during the processing of the source image that resulted in the current image
Enumerated Values:
YES
NO
REORIENTED_ONLY - A projection radiograph that has been flipped, and/or rotated by a multiple of 90 degrees

Notes: 1. This applies not only to images with a known relationship to a 3D space, but also to projection images. For example, a projection radiograph such as a mammogram that is processed by a point image processing operation such as contrast enhancement, or a smoothing or edge enhancing convolution, would have a value of YES for this attribute. A projection radiograph that had been magnified or warped geometrically would have a value of NO for this attribute. A projection radiograph that has been flipped, and/or rotated by a multiple of 90 degrees, such that transformation of pixel locations is possible by comparison of the values of Patient Orientation (0020,0020) would have a value of REORIENTED_ONLY. This attribute is typically of importance in relating images with Presentation Intent Type (0008,0068) values of FOR PROCESSING and FOR PRESENTATION.
2. When the value of this attribute is NO, it is not possible to locate on the current image any pixel coordinates that are referenced relative to the source image, such as for example, might be required for rendering CAD findings derived from a referenced FOR PROCESSING image on the current FOR PRESENTATION image.</description>
    </entry>
    <entry group="0020" element="0020" name="&gt;Patient Orientation" type="1C">
      <description>The Patient Orientation values of the source image.
Required if the value of Spatial Locations Preserved (0028,135A) is REORIENTED_ONLY.</description>
    </entry>
    <entry group="0008" element="114A" name="Referenced Instance Sequence" type="3">
      <description>A sequence which provides reference to a set of non-image SOP Class/Instance pairs significantly related to this Image, including waveforms that may or may not be temporally synchronized with this image .
One or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="1">
      <description>Code describing the purpose of the reference to the Instance(s). Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is CID 7004 for referenced waveforms."/>
    <entry group="0020" element="1002" name="Images in Acquisition" type="3">
      <description>Number of images that resulted from this acquisition of data</description>
    </entry>
    <entry group="0020" element="4000" name="Image Comments" type="3">
      <description>User-defined comments about the image</description>
    </entry>
    <entry group="0028" element="0300" name="Quality Control Image" type="3">
      <description>Indicates whether or not this image is a quality control or phantom image.
Enumerated Values:
YES
NO
If this Attribute is absent, then the image may or may not be a quality control or phantom image. The phantom device in the image can be described using the Device Module. See C.7.6.12</description>
      <section ref="C.7.6.12" name="">Table C.7-18 describes the Attributes of devices or calibration objects (e.g., catheters, markers, baskets) that are associated with a study and/or image.
Table C.7-18
DEVICE MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Device Sequence" meaning="(0050,0010)"/><term value="&gt;Include ‘Code Sequence Macro’ Table 8.8-1" meaning="Baseline Context ID is 4051."/><term value="&gt;Manufacturer" meaning="(0008,0070)"/><term value="&gt;Manufacturer’s Model Name" meaning="(0008,1090)"/><term value="&gt;Device Serial Number" meaning="(0018,1000)"/><term value="&gt;Device ID" meaning="(0018,1003)"/><term value="&gt;Device Length" meaning="(0050,0014)"/><term value="&gt;Device Diameter" meaning="(0050,0016)"/><term value="&gt;Device Diameter Units" meaning="(0050,0017)"/><term value="&gt;Device Volume" meaning="(0050,0018)"/><term value="&gt;Inter-Marker Distance" meaning="(0050,0019)"/><term value="&gt;Device Description" meaning="(0050,0020)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0301" name="Burned In Annotation" type="3">
      <description>Indicates whether or not image contains sufficient burned in annotation to identify the patient and date the image was acquired.
Enumerated Values:
YES
NO
If this Attribute is absent, then the image may or may not contain burned in annotation.</description>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="3">
      <description>Specifies whether an Image has undergone lossy compression. Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2112" name="Lossy Image Compression Ratio" type="3">
      <description>Describes the approximate lossy compression ratio(s) that have been applied to this image.
See C.7.6.1.1.5 for further explanation.
May be multivalued if successive lossy compression steps have been applied.
Notes: 1. For example, a compression ratio of 30:1 would be described in this Attribute with a single value of 30.
2. For historical reasons, the lossy compression ratio may also be described in Derivation Description (0008,2111).</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2114" name="Lossy Image Compression Method" type="3">
      <description>A label for the lossy compression method(s) that have been applied to this image.
See C.7.6.1.1.5 for further explanation.
May be multivalued if successive lossy compression steps have been applied; the value order shall correspond to the values of Lossy Image Compression Ratio (0028,2112).
Note: For historical reasons, the lossy compression method may also be described in Derivation Description (0008,2111).</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0088" element="0200" name="Icon Image Sequence" type="3">
      <description>This icon image is representative of the Image. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt; Include 'Image Pixel Macro' Table C.7-11b" description="See C.7.6.1.1.6 for further explanation."/>
    <entry group="2050" element="0020" name="Presentation LUT Shape" type="3">
      <description>When present, specifies an identity transformation for the Presentation LUT such that the output of all grayscale transformations, if any, are defined to be in P-Values.
Enumerated Values are:
IDENTITY - output is in P-Values - shall be used if Photometric Interpretation (0028,0004) is MONOCHROME2 or any color photometric interpretation.
INVERSE - output after inversion is in P-Values - shall be used if Photometric Interpretation (0028,0004) is MONOCHROME1.
When this attribute is used with a color photometric interpretation then the luminance component is in P-Values.</description>
    </entry>
    <entry group="0008" element="3010" name="Irradiation Event UID" type="3">
      <description>Unique identification of the irradiation event(s) associated with the acquisition of this image. See C.7.6.1.1.7.</description>
      <section ref="C.7.6.1.1.7" name="">An irradiation event is the occurrence of radiation being applied to a patient in single continuous time-frame between the start (release) and the stop (cease) of the irradiation. Any on-off switching of the irradiation source during the event shall not be treated as separate events, rather the event includes the time between start and stop of irradiation as triggered by the user. E.g., a pulsed fluoro X-Ray acquisition shall be treated as a single irradiation event.
</section>
    </entry>
  </module>
  <module ref="C.7.6.2" table="C.7-10" name="Image Plane Module Attributes">
    <entry group="0028" element="0030" name="Pixel Spacing" type="1">
      <description>Physical distance in the patient between the center of each pixel, specified by a numeric pair - adjacent row spacing (delimiter) adjacent column spacing in mm. See 10.7.1.3 for further explanation.</description>
    </entry>
    <entry group="0020" element="0037" name="Image Orientation (Patient)" type="1">
      <description>The direction cosines of the first row and the first column with respect to the patient. See C.7.6.2.1.1 for further explanation.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
    <entry group="0020" element="0032" name="Image Position (Patient)" type="1">
      <description>The x, y, and z coordinates of the upper left hand corner (center of the first voxel transmitted) of the image, in mm. See C.7.6.2.1.1 for further explanation.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
    <entry group="0018" element="0050" name="Slice Thickness" type="2">
      <description>Nominal slice thickness, in mm.</description>
    </entry>
    <entry group="0020" element="1041" name="Slice Location" type="3">
      <description>Relative position of the image plane expressed in mm. C.7.6.2.1.2 for further explanation.</description>
    </entry>
  </module>
  <module ref="C.7.6.3" table="C.7-11a" name="Image Pixel Module Attributes">
    <include ref="Include 'Image Pixel Macro' Table C.7-11b"/>
    <entry group="0028" element="7FE0" name="Pixel Data Provider URL" type="1C">
      <description>A URL of a provider service that supplies the pixel data of the Image.
Required if the image is to be transferred in one of the following presentation contexts identified by Transfer Syntax UID:
1.2.840.10008.1.2.4.94 (DICOM JPIP Referenced Transfer Syntax)
1.2.840.10008.1.2.4.95 (DICOM JPIP Referenced Deflate Transfer Syntax)</description>
    </entry>
    <entry group="0028" element="0121" name="Pixel Padding Range Limit" type="1C">
      <description>Pixel value that represents one limit (inclusive) of a range of padding values used together with Pixel Padding Value (0028,0120) as defined in the General Equipment Module. See C.7.5.1.1.2 for further explanation.
Required if pixel padding is to be defined as a range rather than a single value.
Notes: 1. The Value Representation of this Attribute is determined by the value of Pixel Representation (0028,0103).
2. Pixel Padding Value (0028,0120) is also required when this Attribute is present.</description>
      <section ref="C.7.5.1.1.2" name="">Pixel Padding Value (0028,0120) is used to pad grayscale images (those with a Photometric Interpretation of MONOCHROME1 or MONOCHROME2)to rectangular format. The native format of some images is not rectangular. It is common for devices with this format to pad the images to the rectangular format required by the DICOM Standard with a specific pixel value that is not contained in the native image. Further, when resampling, such as after spatial registration, padding may need to be used to fill previously non-existent pixels.
Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) are also used to identify pixels to be excluded from the normal grayscale rendering pipeline for other reasons, such as suppression of background air. Pixel Padding Range Limit (0028,0121) is defined in the Image Pixel Module.
Notes:  1. The “native image” is that which is being padded to the required rectangular format, e.g., the area within the circular reconstruction perimeter of a CT image, or the subset of the rectangular area that contains useful image information.
  2. The pixel padding value is explicitly described in order to prevent display applications from taking it into account when determining the dynamic range of an image, since the Pixel Padding Value will be outside the range between the minimum and maximum values of the pixels in the native image
  3. No pixels in the native image will have a value equal to Pixel Padding Value.

Pixel Padding Value (0028,0120) specifies either a single value of this padding value, or when combined with Pixel Padding Range Limit (0028,0121), a range of values (inclusive) that are padding.
The values of Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) shall be valid values within the constraints defined by Bits Allocated (0028,0100), Bits Stored (0028,0101), and High Bit (0028,0102).
Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) shall not be present when padding is performed but the pixel value used for padding does occur in the native image.
If Photometric Interpretation (0028,0004) is MONOCHROME2, Pixel Padding Value (0028,0120) shall be less than (closer to or equal to the minimum possible pixel value) or equal to Pixel Padding Range Limit (0028,0121). If Photometric Interpretation (0028,0004) is MONOCHROME1, Pixel Padding Value (0028,0120) shall be greater than (closer to or equal to the maximum possible pixel value) or equal to Pixel Padding Range Limit (0028,0121).
Notes:  1. When the relationship between pixel value and X-Ray Intensity is unknown, it is recommended that the following values be used to pad with black when the image is unsigned:
  0 if Photometric Interpretation (0028,0004) is MONOCHROME2.
  2BitsStored - 1 if Photometric Interpretation (0028,0004) is MONOCHROME1.
  and when the image is signed:
    -2BitsStored-1 if Photometric Interpretation (0028,0004) is MONOCHROME2.
  2BitsStored-1 - 1 if Photometric Interpretation (0028,0004) is MONOCHROME1.
  2. For projection radiography, when the relationship between pixel value and X-Ray Intensity is known (for example as defined by Pixel Intensity Relationship (0028,1040) and Pixel Intensity relationship Sign (0028,1041)), it is recommended that a pixel value equivalent to, or rendered similarly to, air (least X-Ray absorbance) be used for padding. However, if such a value may occur in the native image, the Pixel Padding Value (0028,0120) Attribute itself should not be sent.
  E.g., for an XRF image obtained with an image intensifier, if air is black then a padded perimeter, if any, should also appear black. Typically though, if unpadded, this area would be collimated with a circular collimator, in which case the pixels would appear natively as white (greatest X-Ray absorbance) and a circular shutter would be necessary to neutralize them as black. Whether collimated areas are detected and treated as padded, or neutralized with shutters is at the discretion of the application. See also the Display Shutter Module C.7.6.11.
  3. The conditional requirement for the Pixel Padding Value Range Limit (0028,0121) in the Image Pixel Module means that it shall not be present unless Pixel Padding Value (0028,0120) is also present.
  4. The range of values to be suppressed between Pixel Padding Value (0028,0120) and Pixel Padding Value Range Limit (0028,0121) is specified as being inclusive, that is the values themselves as well as all values between are suppressed.
  5. When Pixel Padding Value Range Limit (0028,0121) is present, but not supported by a rendering application, the constraint that Pixel Padding Value (0028,0120) is closest to the “blackest” value, which is typically the most frequently occurring background pixel, will most often result in an acceptable display, permitting “backward compatibility” in the majority of cases.

When modifying equipment changes the pixel padding value in the image, it shall change the values of Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121), if present. If modifying equipment changes the pixel padding values in the image to values present in the native image, the attribute Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) shall be removed.
Notes:  1. For example, if a CT image containing signed values from -1024 to 3191 and a Pixel Padding Value of -2000 and a Rescale Intercept of 0 is converted to an unsigned image with a Rescale Intercept of -1024 by adding 1024 to all pixels and clipping all more negative pixels to 0, then the padding pixels will be indistinguishable from some of the modified native image pixels, and hence Pixel Padding Value (0028,0120) needs to be removed.
  2. If the modification involves lossy compression, which may result in changes to the pixel values, then the application of Pixel Padding Value and Pixel Padding Range Limit may result in a different appearance, and hence these attributes may need different values also.

</section>
    </entry>
  </module>
  <macro table="C.7-11b" name="Image Pixel Macro Attributes">
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (planes) in this image. See C.7.6.3.1.1 for further explanation.</description>
      <section ref="C.7.6.3.1.1" name="">Samples per Pixel (0028,0002) is the number of separate planes in this image. One, three, and four image planes are defined. Other numbers of image planes are allowed, but their meaning is not defined by this Standard.
For monochrome (gray scale) and palette color images, the number of planes is 1. For RGB and other three vector color models, the value of this attribute is 3. For four vector color models, the value of this attribute is 4.
All image planes shall have the same number of Rows (0028,0010), Columns (0028,0011), Bits Allocated (0028,0100), Bits Stored (0028,0101), High Bit (0028,0102), Pixel Representation (0028,0103), and Pixel Aspect Ratio (0028,0034).
The data in each pixel may be represented as a “Composite Pixel Code”. If Samples Per Pixel is one, the Composite Pixel Code is just the “n” bit pixel sample, where “n” = Bits Allocated. If Samples Per Pixel is greater than one, Composite Pixel Code is a “k” bit concatenation of samples, where “k” = Bits Allocated multiplied by Samples Per Pixel, and with the sample representing the vector color designated first in the Photometric Interpretation name comprising the most significant bits of the Composite Pixel Code, followed in order by the samples representing the next vector colors, with the sample representing the vector color designated last in the Photometric Interpretation name comprising the least significant bits of the Composite Pixel Code. For example, for Photometric Interpretation = “RGB”, the most significant “Bits Allocated” bits contain the Red sample, the next “Bits Allocated” bits contain the Green sample, and the least significant “Bits Allocated” bits contain the Blue sample.
</section>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data. See C.7.6.3.1.2 for further explanation.</description>
      <section ref="C.7.6.3.1.2" name="">The value of Photometric Interpretation (0028,0004) specifies the intended interpretation of the image pixel data.
See PS 3.5 for restrictions imposed by compressed Transfer Syntaxes.
The following values are defined. Other values are permitted but the meaning is not defined by this Standard.
MONOCHROME1 = Pixel data represent a single monochrome image plane. The minimum sample value is intended to be displayed as white after any VOI gray scale transformations have been performed. See PS 3.4. This value may be used only when Samples per Pixel (0028,0002) has a value of 1.
MONOCHROME2 = Pixel data represent a single monochrome image plane. The minimum sample value is intended to be displayed as black after any VOI gray scale transformations have been performed. See PS 3.4. This value may be used only when Samples per Pixel (0028,0002) has a value of 1.
PALETTE COLOR = Pixel data describe a color image with a single sample per pixel (single image plane). The pixel value is used as an index into each of the Red, Blue, and Green Palette Color Lookup Tables (0028,1101-1103&amp;1201-1203). This value may be used only when Samples per Pixel (0028,0002) has a value of 1. When the Photometric Interpretation is Palette Color; Red, Blue, and Green Palette Color Lookup Tables shall be present.
RGB = Pixel data represent a color image described by red, green, and blue image planes. The minimum sample value for each color plane represents minimum intensity of the color. This value may be used only when Samples per Pixel (0028,0002) has a value of 3.
HSV = Retired.
ARGB = Retired.
CMYK = Retired.
YBR_FULL = Pixel data represent a color image described by one luminance (Y) and two chrominance planes (CB and CR). This photometric interpretation may be used only when Samples per Pixel (0028,0002) has a value of 3. Black is represented by Y equal to zero. The absence of color is represented by both CB and CR values equal to half full scale.
Note:  In the case where the Bits Allocated (0028,0100) has value of 8 half full scale is 128.

In the case where Bits Allocated (0028,0100) has a value of 8 then the following equations convert between RGB and YCBCR Photometric Interpretation.
Y =  +  .2990R  +  .5870G  +  .1140B
CB =  -  .1687R  -  .3313G  +  .5000B  +  128
CR =  +  .5000R  -  .4187G  -  .0813B  +  128
Note:  The above is based on CCIR Recommendation 601-2 dated 1990.

YBR_FULL_422 = The same as YBR_FULL except that the CB and CR values are sampled horizontally at half the Y rate and as a result there are half as many CB and CR values as Y values.
This Photometric Interpretation is only allowed with Planar Configuration (0028,0006) equal to 0. Two Y values shall be stored followed by one CB and one CR value. The CB and CR values shall be sampled at the location of the first of the two Y values. For each Row of Pixels, the first CB and CR samples shall be at the location of the first Y sample. The next CB and CR samples shall be at the location of the third Y sample etc.
Note:  This subsampling is often referred to as cosited sampling.

YBR_PARTIAL_422 = The same as YBR_FULL_422 except that:
1. black corresponds to Y = 16;
2. Y is restricted to 220 levels (i.e. the maximum value is 235);
3. CB and CR each has a minimum value of 16;
4. CB and CR are restricted to 225 levels (i.e. the maximum value is 240);
5. lack of color is represented by CB and CR equal to 128.
In the case where Bits Allocated (0028,0100) has value of 8 then the following equations convert between RGB and YBR_PARTIAL_422 Photometric Interpretation
Y =  +  .2568R  +  .5041G  +  .0979B  +  16
CB =  -  .1482R  -  .2910G  +  .4392B  +  128
CR =  +  .4392R  -  .3678G  -  .0714B  +  128
Note:  The above is based on CCIR Recommendation 601-2 dated 1990.

YBR_PARTIAL_420 = The same as YBR_PARTIAL_422 except that the CB and CR values are sampled horizontally and vertically at half the Y rate and as a result there are four times less CB and CR values than Y values, versus twice less for YBR_PARTIAL_422.
This Photometric Interpretation is only allowed with Planar Configuration (0028,0006) equal to 0. The CB and CR values shall be sampled at the location of the first of the two Y values. For the first Row of Pixels (etc.), the first CB and CR samples shall be at the location of the first Y sample. The next CB and CR samples shall be at the location of the third Y sample etc. The next Rows of Pixels containing CB and CR samples (at the same locations than for the first Row) will be the third etc.
YBR_ICT = Irreversible Color Transformation:
Pixel data represent a color image described by one luminance (Y) and two chrominance planes (CB and CR). This photometric interpretation may be used only when Samples per Pixel (0028,0002) has a value of 3. Black is represented by Y equal to zero. The absence of color is represented by both CB and CR values equal to zero.
Regardless of the value of Bits Allocated (0028,0100), the following equations convert between RGB and YCBCR Photometric Interpretation.
Y =  +  .29900R  +  .58700G  +  .11400B
CB =  -  .16875R  -  .33126G  +  .50000B
CR =  +  .50000R  -  .41869G  -  .08131B
Notes:  1. The above is based on ISO/IEC 15444-1 (JPEG 2000).
  2. In a JPEG 2000 bitstream, DC level shifting (used if the untransformed components are unsigned) is applied before forward color transformation, and the transformed components may be signed (unlike in JPEG ISO/IEC 10918-1).
  3. In JPEG 2000, spatial down-sampling of the chrominance components, if performed, is signaled in the JPEG 2000 bitstream.

YBR_RCT = Reversible Color Transformation:
Pixel data represent a color image described by one luminance (Y) and two chrominance planes (CB and CR). This photometric interpretation may be used only when Samples per Pixel (0028,0002) has a value of 3. Black is represented by Y equal to zero. The absence of color is represented by both CB and CR values equal to zero.
Regardless of the value of Bits Allocated (0028,0100), the following equations convert between RGB and YBR_RCT Photometric Interpretation.
Y = R + 2G +B) / 4        (Note:  mean floor)
CB = B - G
CR = R - G
The following equations convert between YBR_RCT and RGB Photometric Interpretation.
G = Y –  (CR + CB) / 4
R = CR + G
B = CB + G
Notes:  1. The above is based on ISO/IEC 15444-1 (JPEG 2000).
  2. In a JPEG 2000 bitstream, DC level shifting (used if the untransformed components are unsigned) is applied before forward color transformation, and the transformed components may be signed (unlike in JPEG ISO/IEC 10918-1).
  3. This photometric interpretation is a reversible approximation to the YUV transformation used in PAL and SECAM.

</section>
    </entry>
    <entry group="0028" element="0010" name="Rows" type="1">
      <description>Number of rows in the image.</description>
    </entry>
    <entry group="0028" element="0011" name="Columns" type="1">
      <description>Number of columns in the image</description>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated. See PS 3.5 for further explanation.</description>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored. See PS 3.5 for further explanation.</description>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data. Each sample shall have the same high bit. See PS 3.5 for further explanation.</description>
    </entry>
    <entry group="0028" element="0103" name="Pixel Representation" type="1">
      <description>Data representation of the pixel samples. Each sample shall have the same pixel representation. Enumerated Values:
0000H = unsigned integer.
0001H = 2's complement</description>
    </entry>
    <entry group="7FE0" element="0010" name="Pixel Data" type="1C">
      <description>A data stream of the pixel samples that comprise the Image. See C.7.6.3.1.4 for further explanation.
Required if Pixel Data Provider URL (0028,7FE0) is not present.</description>
      <section ref="C.7.6.3.1.4" name="">Pixel Data (7FE0,0010) for this image. The order of pixels sent for each image plane is left to right, top to bottom, i.e., the upper left pixel (labeled 1,1) is sent first followed by the remainder of row 1, followed by the first pixel of row 2 (labeled 2,1) then the remainder of row 2 and so on.
For multi-plane images see Planar Configuration (0028,0006) in this Section.
</section>
    </entry>
    <entry group="0028" element="0006" name="Planar Configuration" type="1C">
      <description>Indicates whether the pixel data are sent color-by-plane or color-by-pixel. Required if Samples per Pixel (0028,0002) has a value greater than 1. See C.7.6.3.1.3 for further explanation.</description>
      <section ref="C.7.6.3.1.3" name="">Planar Configuration (0028,0006) indicates whether the color pixel data are sent color-by-plane or color-by-pixel. This Attribute shall be present if Samples per Pixel (0028,0002) has a value greater than 1. It shall not be present otherwise.
Enumerated Values:
0 = The sample values for the first pixel are followed by the sample values for the second pixel, etc. For RGB images, this means the order of the pixel values sent shall be R1, G1, B1, R2, G2, B2, ..., etc.
1 = Each color plane shall be sent contiguously. For RGB images, this means the order of the pixel values sent is R1, R2, R3, ..., G1, G2, G3, ..., B1, B2, B3, etc.
Note:  Planar Configuration (0028,0006) is not meaningful when a compression transfer syntax is used that involves reorganization of sample components in the compressed bit stream. In such cases, since the Attribute is required to be sent, then an appropriate value to use may be specified in the description of the Transfer Syntax in PS 3.5, though in all likelihood the value of the Attribute will be ignored by the receiving implementation.

</section>
    </entry>
    <entry group="0028" element="0034" name="Pixel Aspect Ratio" type="1C">
      <description>Ratio of the vertical size and horizontal size of the pixels in the image specified by a pair of integer values where the first value is the vertical pixel size, and the second value is the horizontal pixel size. Required if the aspect ratio values do not have a ratio of 1:1 and the physical pixel spacing is not specified by Pixel Spacing (0028,0030), or Imager Pixel Spacing (0018,1164) or Nominal Scanned Pixel Spacing (0018,2010), either for the entire Image or per-frame in a Functional Group Macro. See C.7.6.3.1.7.</description>
      <section ref="C.7.6.3.1.7" name="">The pixel aspect ratio is the ratio of the vertical size and horizontal size of the pixels in the image specified by a pair of integer values where the first value is the vertical pixel size, and the second value is the horizontal pixel size. To illustrate, consider the following example pixel size:

Pixel Aspect Ratio = Vertical Size \ Horizontal Size = 0.30 mm \0.25 mm. Thus the Pixel Aspect Ratio could be represented as the multivalued integer string "6\5", "60\50", or any equivalent integer ratio.
</section>
    </entry>
    <entry group="0028" element="0106" name="Smallest Image Pixel Value" type="3">
      <description>The minimum actual pixel value encountered in this image.</description>
    </entry>
    <entry group="0028" element="0107" name="Largest Image Pixel Value" type="3">
      <description>The maximum actual pixel value encountered in this image.</description>
    </entry>
    <entry group="0028" element="1101" name="Red Palette Color Lookup Table Descriptor" type="1C">
      <description>Specifies the format of the Red Palette Color Lookup Table Data (0028,1201) Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See C.7.6.3.1.5 for further explanation.</description>
      <section ref="C.7.6.3.1.5" name="">The three values of Palette Color Lookup Table Descriptor (0028,1101-1103) describe the format of the Lookup Table Data in the corresponding Data Element (0028,1201-1203) or (0028,1221-1223).
The first value is the number of entries in the lookup table. When the number of table entries is equal to 216 then this value shall be 0. The first value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the Lookup Table Data. All image pixel values less than the first value mapped are also mapped to the first entry in the Lookup Table Data if the Photometric Interpretation is PALETTE COLOR.
Note:  In the case of the Supplemental Palette Color LUT, the stored pixel values less than the second descriptor value are grayscale values.

An image pixel value one greater than the first value mapped is mapped to the second entry in the Lookup Table Data. Subsequent image pixel values are mapped to the subsequent entries in the Lookup Table Data up to an image pixel value equal to number of entries + first value mapped – 1, which is mapped to the last entry in the Lookup Table Data. Image pixel values greater than or equal to number of entries + first value mapped are also mapped to the last entry in the Lookup Table Data. The second value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The third value specifies the number of bits for each entry in the Lookup Table Data. It shall take the value of 8 or 16. The LUT Data shall be stored in a format equivalent to 8 bits allocated when the number of bits for each entry is 8, and 16 bits allocated when the number of bits for each entry is 16, where in both cases the high bit is equal to bits allocated-1. The third value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
Note:  Some implementations have encoded 8 bit entries with 16 bits allocated, padding the high bits; this can be detected by comparing the number of entries specified in the LUT Descriptor with the actual value length of the LUT Data entry. The value length in bytes should equal the number of entries if bits allocated is 8, and be twice as long if bits allocated is 16.

When the Palette Color Lookup Table Descriptor (0028,1101-1103) are used as part of the Palette Color Lookup Table Module or the Supplemental Palette Color Lookup Table Module, the third value shall be equal to 16.
Notes:  1. A value of 16 indicates the Lookup Table Data will range from (0,0,0) minimum intensity to (65535,65535,65535) maximum intensity.
  2. Since the Palette Color Lookup Table Descriptor (0028,1101-1103) Attributes are multi-valued, in an Explicit VR Transfer Syntax, only one value representation (US or SS) may be specified, even though the first and third values are always by definition interpreted as unsigned. The explicit VR actually used is dictated by the VR needed to represent the second value, which will be consistent with Pixel Representation (0028,0103).

</section>
    </entry>
    <entry group="0028" element="1102" name="Green Palette Color Lookup Table Descriptor" type="1C">
      <description>Specifies the format of the Green Palette Color Lookup Table Data (0028,1202) Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See C.7.6.3.1.5 for further explanation.</description>
      <section ref="C.7.6.3.1.5" name="">The three values of Palette Color Lookup Table Descriptor (0028,1101-1103) describe the format of the Lookup Table Data in the corresponding Data Element (0028,1201-1203) or (0028,1221-1223).
The first value is the number of entries in the lookup table. When the number of table entries is equal to 216 then this value shall be 0. The first value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the Lookup Table Data. All image pixel values less than the first value mapped are also mapped to the first entry in the Lookup Table Data if the Photometric Interpretation is PALETTE COLOR.
Note:  In the case of the Supplemental Palette Color LUT, the stored pixel values less than the second descriptor value are grayscale values.

An image pixel value one greater than the first value mapped is mapped to the second entry in the Lookup Table Data. Subsequent image pixel values are mapped to the subsequent entries in the Lookup Table Data up to an image pixel value equal to number of entries + first value mapped – 1, which is mapped to the last entry in the Lookup Table Data. Image pixel values greater than or equal to number of entries + first value mapped are also mapped to the last entry in the Lookup Table Data. The second value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The third value specifies the number of bits for each entry in the Lookup Table Data. It shall take the value of 8 or 16. The LUT Data shall be stored in a format equivalent to 8 bits allocated when the number of bits for each entry is 8, and 16 bits allocated when the number of bits for each entry is 16, where in both cases the high bit is equal to bits allocated-1. The third value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
Note:  Some implementations have encoded 8 bit entries with 16 bits allocated, padding the high bits; this can be detected by comparing the number of entries specified in the LUT Descriptor with the actual value length of the LUT Data entry. The value length in bytes should equal the number of entries if bits allocated is 8, and be twice as long if bits allocated is 16.

When the Palette Color Lookup Table Descriptor (0028,1101-1103) are used as part of the Palette Color Lookup Table Module or the Supplemental Palette Color Lookup Table Module, the third value shall be equal to 16.
Notes:  1. A value of 16 indicates the Lookup Table Data will range from (0,0,0) minimum intensity to (65535,65535,65535) maximum intensity.
  2. Since the Palette Color Lookup Table Descriptor (0028,1101-1103) Attributes are multi-valued, in an Explicit VR Transfer Syntax, only one value representation (US or SS) may be specified, even though the first and third values are always by definition interpreted as unsigned. The explicit VR actually used is dictated by the VR needed to represent the second value, which will be consistent with Pixel Representation (0028,0103).

</section>
    </entry>
    <entry group="0028" element="1103" name="Blue Palette Color Lookup Table Descriptor" type="1C">
      <description>Specifies the format of the Blue Palette Color Lookup Table Data (0028,1203) Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See C.7.6.3.1.5 for further explanation.</description>
      <section ref="C.7.6.3.1.5" name="">The three values of Palette Color Lookup Table Descriptor (0028,1101-1103) describe the format of the Lookup Table Data in the corresponding Data Element (0028,1201-1203) or (0028,1221-1223).
The first value is the number of entries in the lookup table. When the number of table entries is equal to 216 then this value shall be 0. The first value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the Lookup Table Data. All image pixel values less than the first value mapped are also mapped to the first entry in the Lookup Table Data if the Photometric Interpretation is PALETTE COLOR.
Note:  In the case of the Supplemental Palette Color LUT, the stored pixel values less than the second descriptor value are grayscale values.

An image pixel value one greater than the first value mapped is mapped to the second entry in the Lookup Table Data. Subsequent image pixel values are mapped to the subsequent entries in the Lookup Table Data up to an image pixel value equal to number of entries + first value mapped – 1, which is mapped to the last entry in the Lookup Table Data. Image pixel values greater than or equal to number of entries + first value mapped are also mapped to the last entry in the Lookup Table Data. The second value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The third value specifies the number of bits for each entry in the Lookup Table Data. It shall take the value of 8 or 16. The LUT Data shall be stored in a format equivalent to 8 bits allocated when the number of bits for each entry is 8, and 16 bits allocated when the number of bits for each entry is 16, where in both cases the high bit is equal to bits allocated-1. The third value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
Note:  Some implementations have encoded 8 bit entries with 16 bits allocated, padding the high bits; this can be detected by comparing the number of entries specified in the LUT Descriptor with the actual value length of the LUT Data entry. The value length in bytes should equal the number of entries if bits allocated is 8, and be twice as long if bits allocated is 16.

When the Palette Color Lookup Table Descriptor (0028,1101-1103) are used as part of the Palette Color Lookup Table Module or the Supplemental Palette Color Lookup Table Module, the third value shall be equal to 16.
Notes:  1. A value of 16 indicates the Lookup Table Data will range from (0,0,0) minimum intensity to (65535,65535,65535) maximum intensity.
  2. Since the Palette Color Lookup Table Descriptor (0028,1101-1103) Attributes are multi-valued, in an Explicit VR Transfer Syntax, only one value representation (US or SS) may be specified, even though the first and third values are always by definition interpreted as unsigned. The explicit VR actually used is dictated by the VR needed to represent the second value, which will be consistent with Pixel Representation (0028,0103).

</section>
    </entry>
    <entry group="0028" element="1201" name="Red Palette Color Lookup Table Data" type="1C">
      <description>Red Palette Color Lookup Table Data.
Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See C.7.6.3.1.6 for further explanation.</description>
      <section ref="C.7.6.3.1.6" name="">Palette Color Lookup Table Data (0028,1201-1203) contain the lookup table data corresponding to the Lookup Table Descriptor (0028,1101-1103).
Palette color values must always be scaled across the full range of available intensities. This is indicated by the fact that there are no bits stored and high bit values for palette color data.
Note:  For example, if there are 16 bits per entry specified and only 8 bits of value are truly used then the 8 bit intensities from 0 to 255 must be scaled to the corresponding 16 bit intensities from 0 to 65535. To do this for 8 bit values, simply replicate the value in both the most and least significant bytes.

These lookup tables shall be used only when there is a single sample per pixel (single image plane) in the image.
These lookup tables are required when the value of Photometric Interpretation (0028,0004) is Palette Color. The semantics of these lookup tables is not defined otherwise.
</section>
    </entry>
    <entry group="0028" element="1202" name="Green Palette Color Lookup Table Data" type="1C">
      <description>Green Palette Color Lookup Table Data. Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See C.7.6.3.1.6 for further explanation.</description>
      <section ref="C.7.6.3.1.6" name="">Palette Color Lookup Table Data (0028,1201-1203) contain the lookup table data corresponding to the Lookup Table Descriptor (0028,1101-1103).
Palette color values must always be scaled across the full range of available intensities. This is indicated by the fact that there are no bits stored and high bit values for palette color data.
Note:  For example, if there are 16 bits per entry specified and only 8 bits of value are truly used then the 8 bit intensities from 0 to 255 must be scaled to the corresponding 16 bit intensities from 0 to 65535. To do this for 8 bit values, simply replicate the value in both the most and least significant bytes.

These lookup tables shall be used only when there is a single sample per pixel (single image plane) in the image.
These lookup tables are required when the value of Photometric Interpretation (0028,0004) is Palette Color. The semantics of these lookup tables is not defined otherwise.
</section>
    </entry>
    <entry group="0028" element="1203" name="Blue Palette Color Lookup Table Data" type="1C">
      <description>Blue Palette Color Lookup Table Data. Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See C.7.6.3.1.6 for further explanation.</description>
      <section ref="C.7.6.3.1.6" name="">Palette Color Lookup Table Data (0028,1201-1203) contain the lookup table data corresponding to the Lookup Table Descriptor (0028,1101-1103).
Palette color values must always be scaled across the full range of available intensities. This is indicated by the fact that there are no bits stored and high bit values for palette color data.
Note:  For example, if there are 16 bits per entry specified and only 8 bits of value are truly used then the 8 bit intensities from 0 to 255 must be scaled to the corresponding 16 bit intensities from 0 to 65535. To do this for 8 bit values, simply replicate the value in both the most and least significant bytes.

These lookup tables shall be used only when there is a single sample per pixel (single image plane) in the image.
These lookup tables are required when the value of Photometric Interpretation (0028,0004) is Palette Color. The semantics of these lookup tables is not defined otherwise.
</section>
    </entry>
    <entry group="0028" element="2000" name="ICC Profile" type="3">
      <description>An ICC Profile encoding the transformation of device-dependent color stored pixel values into PCS-Values.
See Section C.11.15.1.1.1.
When present, defines the color space of color Pixel Data (7FE0,0010) values, and the output of Palette Color Lookup Table Data (0028,1201-1203).
Note: The profile applies only to the Pixel Data (7FE0,0010) attribute at the same level of the dataset and not to any icons nested within sequences, which may or may not have their own ICC profile specified.</description>
    </entry>
  </macro>
  <module ref="C.7.6.4" table="C.7-12" name="Contrast/bolus Module Attributes">
    <entry group="0018" element="0010" name="Contrast/Bolus Agent" type="2">
      <description>Contrast or bolus agent</description>
    </entry>
    <entry group="0018" element="0012" name="Contrast/Bolus Agent Sequence" type="3">
      <description>Sequence that identifies the contrast agent. One or more Items may be present.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 12."/>
    <entry group="0018" element="1040" name="Contrast/Bolus Route" type="3">
      <description>Administration route of contrast agent</description>
    </entry>
    <entry group="0018" element="0014" name="Contrast/Bolus Administration Route Sequence" type="3">
      <description>Sequence that identifies the route of administration of contrast agent. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 11."/>
    <entry group="0018" element="002A" name="&gt;Additional Drug Sequence" type="3">
      <description>Sequence that identifies any additional drug that is administered with the contrast agent bolus. One or more Items may be present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <entry group="0018" element="1041" name="Contrast/Bolus Volume" type="3">
      <description>Volume injected in milliliters of diluted contrast agent</description>
    </entry>
    <entry group="0018" element="1042" name="Contrast/Bolus Start Time" type="3">
      <description>Time of start of injection</description>
    </entry>
    <entry group="0018" element="1043" name="Contrast/Bolus Stop Time" type="3">
      <description>Time of end of contrast injection</description>
    </entry>
    <entry group="0018" element="1044" name="Contrast/Bolus Total Dose" type="3">
      <description>Total amount in milliliters of the undiluted contrast agent</description>
    </entry>
    <entry group="0018" element="1046" name="Contrast Flow Rate" type="3">
      <description>Rate(s) of injection(s) in milliliters/sec</description>
    </entry>
    <entry group="0018" element="1047" name="Contrast Flow Duration" type="3">
      <description>Duration(s) of injection(s) in seconds. Each Contrast Flow Duration value shall correspond to a value of Contrast Flow Rate (0018,1046).</description>
    </entry>
    <entry group="0018" element="1048" name="Contrast/Bolus Ingredient" type="3">
      <description>Active ingredient of agent. Defined Terms:
IODINE
GADOLINIUM
CARBON DIOXIDE
BARIUM</description>
    </entry>
    <entry group="0018" element="1049" name="Contrast/Bolus Ingredient Concentration" type="3">
      <description>Milligrams of active ingredient per milliliter of (diluted) agent</description>
    </entry>
  </module>
  <module ref="C.7.6.4b" table="C.7-12b" name="Enhanced Contrast/bolus Module Attributes">
    <entry group="0018" element="0012" name="Contrast/Bolus Agent Sequence" type="1">
      <description>Sequence that identifies one or more contrast agents administered prior to or during the acquisition. Shall contain one or more Items.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 12."/>
    <entry group="0018" element="9337" name="&gt;Contrast/Bolus Agent Number" type="1">
      <description>Identifying number, unique within this SOP Instance, of the agent administered. Used to reference this particular agent from the Contrast/Bolus Functional Group Macro. The number shall be 1 for the first Item and increase by 1 for each subsequent Item.</description>
    </entry>
    <entry group="0018" element="0014" name="&gt;Contrast/Bolus Administration Route Sequence" type="1">
      <description>Sequence that identifies the route of administration of contrast agent. Shall contain exactly one Item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 11."/>
    <entry group="0018" element="9338" name="&gt;Contrast/Bolus Ingredient Code Sequence" type="2">
      <description>Active ingredient of agent. Zero or more Items may be included in the Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 13."/>
    <entry group="0018" element="1041" name="&gt;Contrast/Bolus Volume" type="2">
      <description>Total volume administered in milliliters of diluted contrast agent.</description>
    </entry>
    <entry group="0018" element="1049" name="&gt;Contrast/Bolus Ingredient Concentration" type="2">
      <description>Milligrams of active ingredient per milliliter of agent.</description>
    </entry>
    <entry group="0018" element="9425" name="&gt;Contrast/Bolus Ingredient Opaque" type="3">
      <description>Absorption of the ingredient greater than the absorption of water (tissue).
Enumerated Values:
YES
NO
See Section C.7.6.4b.1.</description>
      <section ref="C.7.6.4" name="">Table C.7-12 specifies the Attributes that describe the contrast /bolus used in the acquisition of the Image.
Table C.7-12
CONTRAST/BOLUS MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Contrast/Bolus Agent" meaning="(0018,0010)"/><term value="Contrast/Bolus Agent Sequence" meaning="(0018,0012)"/><term value="&gt;Include ‘Code Sequence Macro’ Table 8.8-1" meaning="Baseline Context ID is 12."/><term value="Contrast/Bolus Route" meaning="(0018,1040)"/><term value="Contrast/Bolus Administration Route Sequence" meaning="(0018,0014)"/><term value="&gt;Include ‘Code Sequence Macro’ Table 8.8-1" meaning="Baseline Context ID is 11."/><term value="&gt;Additional Drug Sequence" meaning="(0018,002A)"/><term value="&gt;&gt;Include ‘Code Sequence Macro’ Table 8.8-1" meaning="No Baseline Context ID is defined."/><term value="Contrast/Bolus Volume" meaning="(0018,1041)"/><term value="Contrast/Bolus Start Time" meaning="(0018,1042)"/><term value="Contrast/Bolus Stop Time" meaning="(0018,1043)"/><term value="Contrast/Bolus Total Dose" meaning="(0018,1044)"/><term value="Contrast Flow Rate" meaning="(0018,1046)"/><term value="Contrast Flow Duration" meaning="(0018,1047)"/><term value="Contrast/Bolus Ingredient" meaning="(0018,1048)"/><term value="Contrast/Bolus Ingredient Concentration" meaning="(0018,1049)"/></unrecognized-rows>
Note:  1. Flow duration is an alternate method of specifying stop time
  2. Flow rate allows for stepped injections by being capable of multiple values (1,N) instances.
  3. For a 100 ml injection of 76% Diatrizoate and meglumine/sodium, diluted 1:1,
    the Contrast/Bolus Agent would be “76% Diatrizoate” as text
    the Contrast/Bolus Volume would be 100 ml,
    the Contrast/Bolus Total Dose would be 50 ml,
    the Contrast/Bolus Ingredient would be “IODINE”,
    the Contrast/Bolus Ingredient Concentration would be 370mg/ml.

</section>
    </entry>
    <entry group="0018" element="9340" name="&gt;Contrast Administration Profile Sequence" type="3">
      <description>Sequence that describes one or more phases of contrast administered. If present, shall contain one or more Items.</description>
    </entry>
    <entry group="0018" element="1041" name="&gt;&gt;Contrast/Bolus Volume" type="2">
      <description>Volume administered during this phase in milliliters of diluted contrast agent.</description>
    </entry>
    <entry group="0018" element="1042" name="&gt;&gt;Contrast/Bolus Start Time" type="3">
      <description>Time of start of administration.</description>
    </entry>
    <entry group="0018" element="1043" name="&gt;&gt;Contrast/Bolus Stop Time" type="3">
      <description>Time of end of administration.</description>
    </entry>
    <entry group="0018" element="1046" name="&gt;&gt;Contrast Flow Rate" type="3">
      <description>Rate of administration in milliliters/sec. Only a single value shall be present.</description>
    </entry>
    <entry group="0018" element="1047" name="&gt;&gt;Contrast Flow Duration" type="3">
      <description>Duration of injection in seconds. Only a single value shall be present.</description>
    </entry>
  </module>
  <module ref="C.7.6.5" table="C.7-13" name="Cine Module Attributes">
    <entry group="0018" element="1244" name="Preferred Playback Sequencing" type="3">
      <description>Describes the preferred playback sequencing for a multi-frame image.
Enumerated Values:
0 = Looping (1,2...n,1,2,...n,1,2,....n,...)
1 = Sweeping (1,2,...n,n-1,...2,1,2,...n,...)</description>
    </entry>
    <entry group="0018" element="1063" name="Frame Time" type="1C">
      <description>Nominal time (in msec) per individual frame. See C.7.6.5.1.1 for further explanation. Required if Frame Increment Pointer (0028,0009) points to Frame Time.</description>
      <section ref="C.7.6.5.1.1" name="">Frame Time (0018,1063) is the nominal time (in milliseconds) between individual frames of a Multi-frame image. If the Frame Increment Pointer points to this Attribute, Frame Time shall be used in the following manner to calculate 'the relative time' for each frame:
Frame 'Relative Time' (n) = Frame Delay + Frame Time * (n-1)
    where: n = number of frame within the Multi-frame image and the first frame number is one
Note:  When there is only one frame present, Frame Time (0018,1063) may have either a value of 0, or a nominal value that would apply if there were multiple frames.

</section>
    </entry>
    <entry group="0018" element="1065" name="Frame Time Vector" type="1C">
      <description>An array that contains the real time increments (in msec) between frames for a Multi-frame image. See C.7.6.5.1.2 for further explanation. Required if Frame Increment Pointer (0028,0009) points to Frame Time Vector.
Note: Frame Time Vector arrays may not be properly encoded if Explicit-VR transfer syntax is used and the VL of this attribute exceeds 65534 bytes.</description>
      <section ref="C.7.6.5.1.2" name="">Frame Time Vector (0018,1065) is an array that contains the time increments (in milliseconds) between the nth frame and the previous frame for a Multi-frame image. The first frame always has a time increment of 0. If the Frame Increment Pointer points to this Attribute, the Frame Time Vector shall be used in the following manner to calculate 'relative time' T(n) for frame n:

where ti is the ith Frame Time Vector component.
</section>
    </entry>
    <entry group="0008" element="2142" name="Start Trim" type="3">
      <description>The frame number of the first frame of the Multi-frame image to be displayed.</description>
    </entry>
    <entry group="0008" element="2143" name="Stop Trim" type="3">
      <description>The Frame Number of the last frame of a Multi-frame image to be displayed.</description>
    </entry>
    <entry group="0008" element="2144" name="Recommended Display Frame Rate" type="3">
      <description>Recommended rate at which the frames of a Multi-frame image should be displayed in frames/second.</description>
    </entry>
    <entry group="0018" element="0040" name="Cine Rate" type="3">
      <description>Number of frames per second.</description>
    </entry>
    <entry group="0018" element="1066" name="Frame Delay" type="3">
      <description>Time (in msec) from Content Time (0008,0033) to the start of the first frame in a Multi-frame image.</description>
    </entry>
    <entry group="0018" element="1067" name="Image Trigger Delay" type="3">
      <description>Delay time in milliseconds from trigger (e.g., X-Ray on pulse) to the first frame of a Multi-frame image.</description>
    </entry>
    <entry group="0018" element="0072" name="Effective Duration" type="3">
      <description>Total time in seconds that data was actually taken for the entire Multi-frame image.</description>
    </entry>
    <entry group="0018" element="1242" name="Actual Frame Duration" type="3">
      <description>Elapsed time of data acquisition in msec per each frame.</description>
    </entry>
    <entry group="003A" element="0300" name="Multiplexed Audio Channels Description Code Sequence" type="2C">
      <description>Description of any multiplexed audio channels. See Section C.7.6.5.1.3.
Required if the Transfer Syntax used to encode the multi-frame image contains multiplexed (interleaved) audio channels, such as is possible with MPEG2. Zero or more items may be present in this sequence.</description>
      <section ref="C.7.6.5.1.3" name="">During a video acquisition, audio may be used for voice commentary of what is being observed, as well as to record sound-based physiological information such as Doppler audio.
Some Transfer Syntaxes allow for the multiplexing of interleaved audio with video data, and the Attributes of the Cine Module support this encoding paradigm. They are not intended to describe audio acquired simultaneously when it is encoded in other SOP Instances or within Attributes other than Pixel Data (7FE0,0010) of the same SOP Instance.
Synchronization between audio and video is assumed to be encoded at the Transfer Syntax level (i.e. within the encoded bit stream).
Note:  If no audio was recorded, the Multiplexed Audio Channels Description Code Sequence (003A,0300) will be present and contain no sequence items.
</section>
    </entry>
    <entry group="003A" element="0301" name="&gt;Channel Identification Code" type="1">
      <description>A reference to the audio channel as identified within Transfer Syntax encoded bit stream (1 for the main channel, 2 for the second channel and 3 to 9 to the complementary channels).</description>
    </entry>
    <entry group="003A" element="0302" name="&gt;Channel Mode" type="1">
      <description>A coded descriptor qualifying the mode of the channel:
Enumerated Values:
MONO = 1 signal
STEREO = 2 simultaneously acquired (left and right) signals</description>
    </entry>
    <entry group="003A" element="0208" name="&gt;Channel Source Sequence" type="1">
      <description>A coded descriptor of the audio channel source. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Defined Context ID Audio Channel Source 3000."/>
  </module>
  <module ref="C.7.6.6" table="C.7-14" name="Multi Frame Module Attributes">
    <entry group="0028" element="0008" name="Number of Frames" type="1">
      <description>Number of frames in a Multi-frame Image. See C.7.6.6.1.1 for further explanation.</description>
      <section ref="C.7.6.6.1.1" name="">A Multi-frame Image is defined as a Image whose pixel data consists of a sequential set of individual Image Pixel frames. A Multi-frame Image is transmitted as a single contiguous stream of pixels. Frame headers do not exist within the data stream.
Each individual frame shall be defined (and thus can be identified) by the Attributes in the Image Pixel Module (see C.7.6.3). All Image IE Attributes shall be related to the first frame in the Multi-frame image.
The total number of frames contained within a Multi-frame Image is conveyed in the Number of Frames (0028,0008).
The frames within a Multi-frame Image shall be conveyed as a logical sequence. The information that determines the sequential order of the frames shall be identified by the Data Element Tag or tags conveyed by the Frame Increment Pointer (0028,0009). Each specific Image IOD that supports the Multi-frame Module specializes the Frame Increment Pointer (0028,0009) to identify the Attributes that may be used as sequences.
Even if only a single frame is present, Frame Increment Pointer (0028,0009) is still required to be present and have at least one value, each of which shall point to an attribute that is also present in the dataset and has a value.
Note:  For example, in single-frame instance of an IOD that is required to or may contain the Cine Module, it may be appropriate for Frame Time (0018,1063) to be present with a value of 0, and be the only target of Frame Increment Pointer (0028,0009).

</section>
    </entry>
    <entry group="0028" element="0009" name="Frame Increment Pointer" type="1">
      <description>Contains the Data Element Tag of the attribute that is used as the frame increment in Multi-frame pixel data. See C.7.6.6.1.1 for further explanation.</description>
      <section ref="C.7.6.6.1.1" name="">A Multi-frame Image is defined as a Image whose pixel data consists of a sequential set of individual Image Pixel frames. A Multi-frame Image is transmitted as a single contiguous stream of pixels. Frame headers do not exist within the data stream.
Each individual frame shall be defined (and thus can be identified) by the Attributes in the Image Pixel Module (see C.7.6.3). All Image IE Attributes shall be related to the first frame in the Multi-frame image.
The total number of frames contained within a Multi-frame Image is conveyed in the Number of Frames (0028,0008).
The frames within a Multi-frame Image shall be conveyed as a logical sequence. The information that determines the sequential order of the frames shall be identified by the Data Element Tag or tags conveyed by the Frame Increment Pointer (0028,0009). Each specific Image IOD that supports the Multi-frame Module specializes the Frame Increment Pointer (0028,0009) to identify the Attributes that may be used as sequences.
Even if only a single frame is present, Frame Increment Pointer (0028,0009) is still required to be present and have at least one value, each of which shall point to an attribute that is also present in the dataset and has a value.
Note:  For example, in single-frame instance of an IOD that is required to or may contain the Cine Module, it may be appropriate for Frame Time (0018,1063) to be present with a value of 0, and be the only target of Frame Increment Pointer (0028,0009).

</section>
    </entry>
  </module>
  <module ref="C.7.6.9" table="C.7-15" name="Frame Pointers Module Attributes">
    <entry group="0028" element="6010" name="Representative Frame Number" type="3">
      <description>The frame number selected for use as a pictorial representation (e.g. icon) of the Multi-frame Image</description>
    </entry>
    <entry group="0028" element="6020" name="Frame Numbers Of Interest (FOI)" type="3">
      <description>Frame number(s) selected as frames of interest. A frame number may appear more than once.</description>
    </entry>
    <entry group="0028" element="6022" name="Frame Of Interest Description" type="3">
      <description>Description of each one of the Frame(s) of Interest selected in (0028,6020). If multiple Frames of Interest are selected and this Attribute is used, it shall contain the same number of values as are in Frame Numbers of Interest (0028,6020).</description>
    </entry>
    <entry group="0028" element="6023" name="Frame of Interest Type" type="3">
      <description>A defined term for each one of the Frame(s) of Interest (0028,6020) that identifies the significance of the frame. If multiple Frames of Interest are selected and this Attribute is used, it shall contain the same number of values as are in Frame Numbers of Interest (0028,6020).
Defined Terms are:
HIGHMI = a frame acquired at the time of the high power pulse that destroys acoustic contrast
RWAVE = the frame closest to the R-Wave
TRIGGER = a trigger frame, for example a set delay from the R Wave
ENDSYSTOLE = the frame closest to end of systole, at the end of the T-wave</description>
    </entry>
  </module>
  <module ref="C.7.6.10" table="C.7-16" name="Mask Module Attributes">
    <entry group="0028" element="6100" name="Mask Subtraction Sequence" type="1">
      <description>Defines a sequence that describes mask subtraction operations for a Multi-frame Image. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="0028" element="6101" name="&gt;Mask Operation" type="1">
      <description>Defined Term identifying the type of mask operation to be performed. See C.7.6.10.1 for further explanation.</description>
      <section ref="C.7.6.10.1" name=""/>
    </entry>
    <entry group="0028" element="9416" name="&gt;Subtraction Item ID" type="1C">
      <description>Identification of the Subtraction Item used to associate a certain Mask Sub-Pixel Shift (0028,6114) in the Frame Pixel Shift Functional Group.
See C.7.6.16.2.14.1.
Required if SOP Class UID (0008,0016) equals "1.2.840.10008.5.1.4.1.1.12.1.1" or "1.2.840.10008.5.1.4.1.1.12.2.1". May be present otherwise.</description>
      <section ref="C.7.6.16.2.14.1" name="">Subtraction Item ID (0028,9416) specifies the ID of a subtraction operation to which the Mask Sub-pixel Shift (0028,6114) is associated. The Subtraction Item ID is also present in the Mask Subtraction Sequence (0028,6100) to allow this association.
When used as per-frame macro, the Subtraction Item ID (0028,9416) allows to specify different values of Mask Sub-pixel Shift (0028,6114) individually frame by frame, and relate them to a single item of the Mask Subtraction Sequence (0028,6100).
Note:  There is no restriction in the number of Subtraction Item ID’s associated to each contrast frame. The same contrast frame may be present in several items of the Mask Subtraction Sequence, each item having a different value of Subtraction Item ID.

When used as shared macro, the Subtraction Item ID (0028,9416) allows to specify one or more values of Mask Sub-pixel Shift that will be applied to all the frames of the Multi-frame image.
Note:  Example of usage of Subtraction Item ID in a per-frame macro, see Figure C.7.6.16-8:
  In this example of Multi-Frame Image with 3 frames, one Mask Frame (i.e., Frame 1) is applied to the next two frames of the Multi-Frame image (i.e., Frames 2 and 3). Therefore, there is only one item in the Mask Subtraction Sequence, containing its own Subtraction Item ID value (i.e., 100). The Frame Pixel Shift Macro allows to define a Mask Sub-Pixel Shift different for each contrast frame.
  First Frame Subtracted: Subtraction of Frame 1 (Mask) to Frame 2, with Sub-Pixel Shift 1.3\2.4
  Second Frame Subtracted: Subtraction of Frame 1 (Mask) to Frame 3, with Sub-Pixel Shift 1.9\3.0

Figure C.7.6.16-8
Example of usage of Subtraction Item ID in a per-frame Macro

</section>
    </entry>
    <entry group="0028" element="6102" name="&gt;Applicable Frame Range" type="1C">
      <description>Each pair of numbers in this multi-valued attribute specify a beginning and ending frame number inclusive of a range where this particular mask operation is valid. Discontinuous ranges are represented by multiple pairs of numbers. Frames in a Multi-frame Image are specified by sequentially increasing number values beginning with 1. If this Attribute is missing in this particular sequence item, then the mask operation is applicable throughout the entire Multi-frame Image, subject to certain limits as described in C.7.6.10.1.1.
Required if Mask Operation (0028,6101) equals REV_TID. May be present otherwise.</description>
    </entry>
    <entry group="0028" element="6110" name="&gt;Mask Frame Numbers" type="1C">
      <description>Specifies the frame numbers of the pixel data used to generate this mask. Frames in a Multi-frame Image are specified by sequentially increasing number values beginning with 1. Required if the Mask Operation (0028,6101) is AVG_SUB.</description>
    </entry>
    <entry group="0028" element="6112" name="&gt;Contrast Frame Averaging" type="3">
      <description>Specifies the number of contrast frames to average together before performing the mask operation. If the Attribute is missing, no averaging is performed.</description>
    </entry>
    <entry group="0028" element="6114" name="&gt;Mask Sub-pixel Shift" type="3">
      <description>A pair of floating point numbers specifying the fractional vertical [adjacent row spacing] and horizontal [adjacent column spacing] pixel shift applied to the mask before subtracting it from the contrast frame. See Section C.7.6.10.1.2.
Note: When the Frame Pixel Shift Functional Group is present the values of the Mask Pixel Shift attribute of that Functional Group prevails over the values specified in this module.</description>
      <section ref="C.7.6.10.1.2" name="">A pair of floating point numbers specifying the fractional vertical [adjacent row spacing] and horizontal [adjacent column spacing] pixel shift applied to the mask before subtracting it from the contrast frame. The row offset results in a shift of the pixels along the column axis. The column offset results in a shift of the pixels along the row axis. A positive row offset is a shift toward the pixels of the lower row of the pixel plane. A positive column offset is a shift toward the pixels of the left hand side column of the pixel plane.
</section>
    </entry>
    <entry group="0028" element="6120" name="&gt;TID Offset" type="2C">
      <description>If Mask Operation is TID, specifies the offset to be subtracted from the current frame number in order to locate the mask frame in TID mode.
If Mask Operation is REV_TID, specifies the initial offset to be subtracted from the first contrast frame number. See section C.7.6.10.1.1.
If zero length, TID Offset defaults to 1. Required if Mask Operation (0028,6101) is TID or REV_TID.</description>
    </entry>
    <entry group="0028" element="6190" name="&gt;Mask Operation Explanation" type="3">
      <description>Free form explanation of this particular mask operation.</description>
    </entry>
    <entry group="0028" element="9454" name="&gt;Mask Selection Mode" type="3">
      <description>Specifies the method of selection of the mask operations of this item.
Defined Terms:
SYSTEM
USER</description>
    </entry>
    <entry group="0028" element="1090" name="Recommended Viewing Mode" type="2">
      <description>Specifies the recommended viewing protocol(s).
Defined terms:
SUB = for subtraction with mask images;
NAT = native viewing of image as sent.
Note: If an implementation does not recognize the defined term for Recommended Viewing Mode (0028,1090) , reverting to native display mode is recommended.</description>
    </entry>
  </module>
  <module ref="C.7.6.11" table="C.7-17" name="Display Shutter Module Attributes">
    <include ref="Include 'Display Shutter Macro' Table C.7-17A."/>
  </module>
  <macro table="C.7-17a" name="Display Shutter Macro Attributes">
    <entry group="0018" element="1600" name="Shutter Shape" type="1">
      <description>Shape(s) of the shutter defined for display. Enumerated Values:
RECTANGULAR
CIRCULAR
POLYGONAL
This multi-valued Attribute shall contain at most one of each Enumerated Value.</description>
    </entry>
    <entry group="0018" element="1602" name="Shutter Left Vertical Edge" type="1C">
      <description>Required if Shutter Shape (0018,1600) is RECTANGULAR. Location of the left edge of the rectangular shutter with respect to pixels in the image given as column.</description>
    </entry>
    <entry group="0018" element="1604" name="Shutter Right Vertical Edge" type="1C">
      <description>Required if Shutter Shape (0018,1600) is RECTANGULAR. Location of the right edge of the rectangular shutter with respect to pixels in the image given as column.</description>
    </entry>
    <entry group="0018" element="1606" name="Shutter Upper Horizontal Edge" type="1C">
      <description>Required if Shutter Shape (0018,1600) is RECTANGULAR. Location of the upper edge of the rectangular shutter with respect to pixels in the image given as row.</description>
    </entry>
    <entry group="0018" element="1608" name="Shutter Lower Horizontal Edge" type="1C">
      <description>Required if Shutter Shape (0018,1600) is RECTANGULAR. Location of the lower edge of the rectangular shutter with respect to pixels in the image given as row.</description>
    </entry>
    <entry group="0018" element="1610" name="Center of Circular Shutter" type="1C">
      <description>Required if Shutter Shape (0018,1600) is CIRCULAR. Location of the center of the circular shutter with respect to pixels in the image given as row and column.</description>
    </entry>
    <entry group="0018" element="1612" name="Radius of Circular Shutter" type="1C">
      <description>Required if Shutter Shape (0018,1600) is CIRCULAR. Radius of the circular shutter with respect to pixels in the image given as a number of pixels along the row direction.</description>
    </entry>
    <entry group="0018" element="1620" name="Vertices of the Polygonal Shutter" type="1C">
      <description>Required if Shutter Shape (0018,1600) is POLYGONAL.
Multiple Values where the first set of two values are:
row of the origin vertex
column of the origin vertex
Two or more pairs of values follow and are the row and column coordinates of the other vertices of the polygon shutter. Polygon shutters are implicitly closed from the last vertex to the origin vertex and all edges shall be non-intersecting except at the vertices.</description>
    </entry>
    <entry group="0018" element="1622" name="Shutter Presentation Value" type="3">
      <description>A single gray unsigned value used to replace those parts of the image occluded by the shutter, when rendered on a monochrome display. The units are specified in P-Values, from a minimum of 0000H (black) up to a maximum of FFFFH (white).
Note: The maximum P-Value for this Attribute may be different from the maximum P-Value from the output of the Presentation LUT, which may be less than 16 bits in depth.</description>
    </entry>
    <entry group="0018" element="1624" name="Shutter Presentation Color CIELab Value" type="3">
      <description>A color triplet value used to replace those parts of the image occluded by the shutter, when rendered on a color display. The units are specified in PCS-Values, and the value is encoded as CIELab. See C.10.7.1.1.</description>
      <section ref="C.10.7.1.1" name="">Attributes such as Graphic Layer Recommended Display CIELab Value (0070,0401) consist of three unsigned short values:
</section>
    </entry>
  </macro>
  <module ref="C.7.6.12" table="C.7-18" name="Device Module Attributes">
    <entry group="0050" element="0010" name="Device Sequence" type="3">
      <description>Introduces sequence of items describing devices used that may be visible in the image.
One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 4051."/>
    <entry group="0008" element="0070" name="&gt;Manufacturer" type="3">
      <description>Manufacturer of the device</description>
    </entry>
    <entry group="0008" element="1090" name="&gt;Manufacturer's Model Name" type="3">
      <description>Manufacturer's model name of the device</description>
    </entry>
    <entry group="0018" element="1000" name="&gt;Device Serial Number" type="3">
      <description>Manufacturer's serial number of the device</description>
    </entry>
    <entry group="0018" element="1003" name="&gt;Device ID" type="3">
      <description>User-supplied identifier for the device</description>
    </entry>
    <entry group="0050" element="0014" name="&gt;Device Length" type="3">
      <description>Length in mm of device. See C.7.6.12.1.1.</description>
      <section ref="C.7.6.12.1.1" name="">Depending on the type of device specified by the Code Value (0008,0100) in an item of the Device Sequence (0050,0010), various device size attributes (e.g., Device Length (0050,0014), Device Diameter (0050,0016), Device Volume (0050,0018), Inter Marker Distance (0050,0019)) may be required to fully characterize the device.
</section>
    </entry>
    <entry group="0050" element="0016" name="&gt;Device Diameter" type="3">
      <description>Unit diameter of device. See C.7.6.12.1.1.</description>
      <section ref="C.7.6.12.1.1" name="">Depending on the type of device specified by the Code Value (0008,0100) in an item of the Device Sequence (0050,0010), various device size attributes (e.g., Device Length (0050,0014), Device Diameter (0050,0016), Device Volume (0050,0018), Inter Marker Distance (0050,0019)) may be required to fully characterize the device.
</section>
    </entry>
    <entry group="0050" element="0017" name="&gt;Device Diameter Units" type="2C">
      <description>Required if Device Diameter (0050,0016) is present. Defined terms:
FR = French
GA = Gauge
IN = Inch
MM = Millimeter</description>
    </entry>
    <entry group="0050" element="0018" name="&gt;Device Volume" type="3">
      <description>Volume of device in ml. See C.7.6.12.1.1.</description>
      <section ref="C.7.6.12.1.1" name="">Depending on the type of device specified by the Code Value (0008,0100) in an item of the Device Sequence (0050,0010), various device size attributes (e.g., Device Length (0050,0014), Device Diameter (0050,0016), Device Volume (0050,0018), Inter Marker Distance (0050,0019)) may be required to fully characterize the device.
</section>
    </entry>
    <entry group="0050" element="0019" name="&gt;Inter-Marker Distance" type="3">
      <description>Distance in mm between markers on calibrated device. See C.7.6.12.1.1.</description>
      <section ref="C.7.6.12.1.1" name="">Depending on the type of device specified by the Code Value (0008,0100) in an item of the Device Sequence (0050,0010), various device size attributes (e.g., Device Length (0050,0014), Device Diameter (0050,0016), Device Volume (0050,0018), Inter Marker Distance (0050,0019)) may be required to fully characterize the device.
</section>
    </entry>
    <entry group="0050" element="0020" name="&gt;Device Description" type="3">
      <description>Further description in free form text describing the device.</description>
    </entry>
  </module>
  <module ref="C.7.6.13" table="C.7-19" name="Intervention Module Attributes">
    <entry group="0018" element="0036" name="Intervention Sequence" type="3">
      <description>Introduces sequence of items describing interventional therapies or procedures.
One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 9."/>
    <entry group="0018" element="0038" name="&gt;Intervention Status" type="2">
      <description>Temporal relation of SOP Instance to intervention
Enumerated Values:
PRE
INTERMEDIATE
POST
NONE
</description>
    </entry>
    <entry group="0018" element="0029" name="&gt;Intervention Drug Sequence" type="3">
      <description>Sequence that identifies the interventional drug.
Only one item shall be included in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 10."/>
    <entry group="0018" element="0035" name="&gt;Intervention Drug Start Time" type="3">
      <description>Time of administration of the interventional drug.</description>
    </entry>
    <entry group="0018" element="0027" name="&gt;Intervention Drug Stop Time" type="3">
      <description>Time of completion of administration of the intervention drug.</description>
    </entry>
    <entry group="0054" element="0302" name="&gt; Administration Route Code Sequence" type="3">
      <description>Sequence that identifies the Administration Route. This sequence shall contain exactly one item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 11."/>
    <entry group="0018" element="003A" name="&gt;Intervention Description" type="3">
      <description>Further description in free form text describing the therapy or other intervention.</description>
    </entry>
  </module>
  <module ref="C.7.6.14" table="C.7.6.14-1" name="Acquisition Context Module Attributes">
    <entry group="0040" element="0555" name="Acquisition Context Sequence" type="2">
      <description>A sequence of Items that describes the conditions present during the acquisition of the data of the SOP Instance. Zero or more items may be included in this sequence.</description>
    </entry>
    <entry group="0040" element="A040" name="&gt;Value Type" type="3">
      <description>The type of the value encoded in this Item.
Defined Terms:
TEXT
NUMERIC
CODE
DATE
TIME
PNAME
See Section 10.2.</description>
    </entry>
    <entry group="0040" element="A043" name="&gt;Concept Name Code Sequence" type="1">
      <description>A concept that constrains the meaning of (i.e. defines the role of) the Observation Value. The "Name" component of a Name/Value pair. This sequence shall contain exactly one item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context is defined."/>
    <entry group="0040" element="A136" name="&gt;Referenced Frame Numbers" type="1C">
      <description>References one or more frames in a Multi-frame SOP Instance. The first frame shall be denoted as frame number one.
Required if this SOP Instance is a Multi-frame SOP Instance and the values in this sequence item do not apply to all frames.</description>
    </entry>
    <entry group="0040" element="A30A" name="&gt;Numeric Value" type="1C">
      <description>This is the Value component of a Name/Value pair when the Concept implied by Concept Name Code Sequence (0040,A043) is a set of one or more numeric values.
Required if the value that Concept Name Code Sequence (0040,A043) requires (implies) is a set of one or more integers or real numbers. Shall not be present otherwise.</description>
    </entry>
    <entry group="0040" element="08EA" name="&gt;Measurement Units Code Sequence" type="1C">
      <description>Units of measurement. Only a single Item shall be permitted in this Sequence.
Required if Numeric Value (0040,A30A) is sent. Shall not be present otherwise.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 82."/>
    <entry group="0040" element="A121" name="&gt;Date" type="1C">
      <description>This is the Value component of a Name/Value pair when the Concept implied by Concept Name Code Sequence (0040,A043) is a date.
Note: The purpose or role of the date value could be specified in Concept Name Code Sequence (0040,A043).

Required if the value that Concept Name Code Sequence (0040,A043) requires (implies) is a date. Shall not be present otherwise.</description>
    </entry>
    <entry group="0040" element="A122" name="&gt;Time" type="1C">
      <description>This is the Value component of a Name/Value pair when the Concept implied by Concept Name Code Sequence (0040,A043) is a time.
Note: The purpose or role of the time value could be specified in Concept Name Code Sequence (0040,A043).

Required if the value that Concept Name Code Sequence (0040,A043) requires (implies) is a time. Shall not be present otherwise.</description>
    </entry>
    <entry group="0040" element="A123" name="&gt;Person Name" type="1C">
      <description>This is the Value component of a Name/Value pair when the Concept implied by Concept Name Code Sequence (0040,A043) is a Person Name.
Note: The role of the person could be specified in Concept Name Code Sequence (0040,A043).

Required if the value that Concept Name Code Sequence (0040,A043) irequires (implies) is a person name. Shall not be present otherwise.</description>
    </entry>
    <entry group="0040" element="A160" name="&gt;Text Value" type="1C">
      <description>This is the Value component of a Name/Value pair when the Concept implied by Concept Name Code Sequence (0040,A043) is a Text Observation Value.
Required if Date (0040,A121), Time (0040,A122), and Person Name (0040,A123) do not fully describe the concept specified by Concept Name Code Sequence (0040,A043). Shall not be present otherwise.</description>
    </entry>
    <entry group="0040" element="A168" name="&gt;Concept Code Sequence" type="1C">
      <description>This is the Value component of a Name/Value pair when the Concept implied by Concept Name Code Sequence (0040,A043) is a Coded Value. This sequence shall contain exactly one item.
Required if Date (0040,A121), Time (0040,A122), Person Name (0040,A123), Text Value (0040,A160), and the pair of Numeric Value (0040,A30A) and Measurement Units Code Sequence (0040,08EA) are not present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context is defined."/>
    <entry group="0040" element="0556" name="Acquisition Context Description" type="3">
      <description>Free-text description of the image-acquisition context.</description>
    </entry>
  </module>
  <module ref="C.7.6.15" table="C.7.6.15-1" name="Bitmap Display Shutter Module Attributes">
    <entry group="0018" element="1600" name="Shutter Shape" type="1">
      <description>Shape of the shutter defined for display. Enumerated Values are:
BITMAP
This Attribute shall contain one Value.</description>
    </entry>
    <entry group="0018" element="1623" name="Shutter Overlay Group" type="1">
      <description>Specifies the Group (60xx) of an Overlay stored within the Presentation State IOD that contains the bitmap data, as defined in the Overlay Plane Module C.9.2.</description>
    </entry>
    <entry group="0018" element="1622" name="Shutter Presentation Value" type="1">
      <description>A single gray unsigned value used to replace those parts of the image occluded by the shutter, when rendered on a monochrome display. The units are specified in P-Values, from a minimum of 0000H (black) up to a maximum of FFFFH (white).
Note: The maximum P-Value for this Attribute may be different from the maximum P-Value from the output of the Presentation LUT, which may be less than 16 bits in depth.</description>
    </entry>
    <entry group="0018" element="1624" name="Shutter Presentation Color CIELab Value" type="3">
      <description>A color triplet value used to replace those parts of the image occluded by the shutter, when rendered on a color display. The units are specified in PCS-Values, and the value is encoded as CIELab. See C.10.7.1.1.</description>
      <section ref="C.10.7.1.1" name="">Attributes such as Graphic Layer Recommended Display CIELab Value (0070,0401) consist of three unsigned short values:
</section>
    </entry>
  </module>
  <module ref="C.7.6.16" table="C.7.6.16-1" name="Multi Frame Functional Groups Module Attributes">
    <entry group="5200" element="9229" name="Shared Functional Groups Sequence" type="2">
      <description>Sequence that contains the Functional Group Macros that are shared for all frames in this SOP Instance and Concatenation.
Note: The contents of this sequence are the same in all SOP Instances that comprise a Concatenation.
Zero or one Item may be included in this sequence.
See section C.7.6.16.1.1 for further explanation.</description>
    </entry>
    <include ref="&gt;Include one or more Functional Group Macros that are shared by all frames. The selected Functional Group Macros shall not be present in the Per-frame Functional Groups Sequence (5200,9230)."/>
    <entry group="5200" element="9230" name="Per-frame Functional Groups Sequence" type="1">
      <description>Sequence that contains the Functional Group Macros corresponding to each frame of the Multi-frame Image. The first Item corresponds with the first frame, and so on.
Each Item shall contain the same set of Functional Group Macros.
This Sequence shall contain the same number of Items as the number of frames in the Multi-frame image. See Section C.7.6.16.1.2 for further explanation.</description>
      <section ref="C.7.6.16.1.2" name="">The Per-frame Functional Groups Sequence Attribute (5200,9230) consists of a Sequence of Items. Each Item describes the frame of the same rank in the multi-frame pixel data. The first Item describes frame 1, the second Item describes frame 2, etc. Frames are implicitly numbered starting from 1. See Figure C.7.6.16-1.
</section>
    </entry>
    <include ref="&gt;Include one or more Functional Group Macros."/>
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description>A number that identifies this instance. The value shall be the same for all SOP Instances of a Concatenation, and different for each separate Concatenation and for each SOP Instance not within a Concatenation in a series.</description>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the data creation was started.
Note: For instance, this is the date the pixel data is created, not the date the data is acquired.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the data creation was started.
Note: For instance, this is the time the pixel data is created, not the time the data is acquired.</description>
    </entry>
    <entry group="0028" element="0008" name="Number of Frames" type="1">
      <description>Number of frames in a multi-frame image. See C.7.6.6.1.1 for further explanation.</description>
      <section ref="C.7.6.6.1.1" name="">A Multi-frame Image is defined as a Image whose pixel data consists of a sequential set of individual Image Pixel frames. A Multi-frame Image is transmitted as a single contiguous stream of pixels. Frame headers do not exist within the data stream.
Each individual frame shall be defined (and thus can be identified) by the Attributes in the Image Pixel Module (see C.7.6.3). All Image IE Attributes shall be related to the first frame in the Multi-frame image.
The total number of frames contained within a Multi-frame Image is conveyed in the Number of Frames (0028,0008).
The frames within a Multi-frame Image shall be conveyed as a logical sequence. The information that determines the sequential order of the frames shall be identified by the Data Element Tag or tags conveyed by the Frame Increment Pointer (0028,0009). Each specific Image IOD that supports the Multi-frame Module specializes the Frame Increment Pointer (0028,0009) to identify the Attributes that may be used as sequences.
Even if only a single frame is present, Frame Increment Pointer (0028,0009) is still required to be present and have at least one value, each of which shall point to an attribute that is also present in the dataset and has a value.
Note:  For example, in single-frame instance of an IOD that is required to or may contain the Cine Module, it may be appropriate for Frame Time (0018,1063) to be present with a value of 0, and be the only target of Frame Increment Pointer (0028,0009).

</section>
    </entry>
    <entry group="0020" element="9228" name="Concatenation Frame Offset Number" type="1C">
      <description>Offset of the first frame in a multi-frame image of a concatenation. Logical frame numbers in a concatenation can be used across all its SOP instances. This offset can be applied to the implicit frame number to find the logical frame number in a concatenation. The offset is numbered from zero; i.e., the instance of a concatenation that begins with the first frame of the concatenation has a Concatenation Frame Offset Number (0020,9228) of zero.
Required if Concatenation UID (0020,9161) is present.</description>
    </entry>
    <entry group="0028" element="6010" name="Representative Frame Number" type="3">
      <description>The frame number selected for use as a pictorial representation (e.g. icon) of the multi-frame Image.</description>
    </entry>
    <entry group="0020" element="9161" name="Concatenation UID" type="1C">
      <description>Identifier of all SOP Instances that belong to the same concatenation.
Required if a group of multi-frame image SOP Instances within a Series are part of a Concatenation.</description>
    </entry>
    <entry group="0020" element="9162" name="In-concatenation Number" type="1C">
      <description>Identifier for one SOP Instance belonging to a concatenation. See C.7.6.16.2.2.4 for further specification. The first instance in a concatentation (that with the lowest Concatenation Frame Offset Number (0020,9228) value) shall have an In-concatenation Number (0020,9162) value of 1, and subsequent instances shall have values monotonically increasing by 1.
Required if Concatenation UID (0020,9161) is present.</description>
      <section ref="C.7.6.16.2.2.4" name="">Due to implementation specific reasons (such as maximum object size) the information of a multi-frame image may be split into more than one SOP Instance. These SOP Instances form together a Concatenation. This is a group of SOP Instances within a Series that is uniquely identified by the Concatenation UID (0020,9161).
The Dimension Index Sequence (0020,9222) for each SOP Instance with the same Concatenation UID (0020,9161) shall contain exactly the same tags and values.
In a Concatenation the Dimension Index Sequence (0020,9222) items of the Shared Functional Groups (5200,9229) shall be identical and have the same values for all individual SOP Instances. The items of the Per-frame Functional Groups (5200,9230) shall be identical for all individual SOP Instances but the values may change per frame. For all other Attributes of all the Modules of the IOD, the same Attributes shall be present and the values shall be identical, with the exception of the following Attributes:
</section>
    </entry>
    <entry group="0020" element="9163" name="In-concatenation Total Number" type="3">
      <description>The number of SOP Instances sharing the same Concatenation UID.</description>
    </entry>
  </module>
  <macro table="C.7.6.16-2" name="Pixel Measures Macro Attributes">
    <entry group="0028" element="9110" name="Pixel Measures Sequence" type="1">
      <description>Identifies the physical characteristics of the pixels of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0028" element="0030" name="&gt;Pixel Spacing" type="1C">
      <description>Physical distance in the patient between the centers of each pixel, specified by a numeric pair - adjacent row spacing (delimiter) adjacent column spacing in mm. See 10.7.1.3 for further explanation of the value order.
Note: In the case of CT images with an Acquisition Type (0018,9302) of CONSTANT_ANGLE, the pixel spacing is that in a plane normal to the central ray of the diverging X-Ray beam as it passes through the data collection center.
Required if Volumetric Properties (0008,9206) is other than DISTORTED or SAMPLED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="0050" name="&gt;Slice Thickness" type="1C">
      <description>Nominal reconstructed slice thickness, in mm.
See C.7.6.2.1.1 and C.7.6.16.2.3.1 for further explanation.
Required if Volumetric Properties (0008,9206) is VOLUME or SAMPLED. May be present otherwise.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
  </macro>
  <macro table="C.7.6.16-3" name="Frame Content Macro Attributes">
    <entry group="0020" element="9111" name="Frame Content Sequence" type="1">
      <description>Identifies general characteristics of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0020" element="9156" name="&gt;Frame Acquisition Number" type="3">
      <description>A number identifying the single continuous gathering of data over a period of time that resulted in this frame.</description>
    </entry>
    <entry group="0018" element="9151" name="&gt;Frame Reference DateTime" type="1C">
      <description>The point in time that is most representative of when data was acquired for this frame. See C.7.6.16.2.2.1 and C.7.6.16.2.2.2 for further explanation.
Note: The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800).
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
      <section ref="C.7.6.16.2.2.1" name="">Figure C.7.6.16-2 shows the relationships among the various timing parameters used.
</section>
    </entry>
    <entry group="0018" element="9074" name="&gt;Frame Acquisition DateTime" type="1C">
      <description>The date and time that the acquisition of data that resulted in this frame started. See C.7.6.16.2.2.1 for further explanation.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
      <section ref="C.7.6.16.2.2.1" name="">Figure C.7.6.16-2 shows the relationships among the various timing parameters used.
</section>
    </entry>
    <entry group="0018" element="9220" name="&gt;Frame Acquisition Duration" type="1C">
      <description>The actual amount of time [in milliseconds] that was used to acquire data for this frame. See C.7.6.16.2.2.1 and C.7.6.16.2.2.3 for further explanation.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
      <section ref="C.7.6.16.2.2.1" name="">Figure C.7.6.16-2 shows the relationships among the various timing parameters used.
</section>
    </entry>
    <entry group="0018" element="9236" name="&gt;Cardiac Cycle Position" type="3">
      <description>Description of the position in the cardiac cycle that is most representative of this frame.
Defined Terms:
END_SYSTOLE
END_DIASTOLE
UNDETERMINED</description>
    </entry>
    <entry group="0018" element="9214" name="&gt;Respiratory Cycle Position" type="3">
      <description>Description of the position in the respiratory cycle that is most representative of this frame.
Defined Terms:
START _RESPIR
END_RESPIR
UNDETERMINED</description>
    </entry>
    <entry group="0020" element="9157" name="&gt;Dimension Index Values" type="1C">
      <description>Contains the values of the indices defined in the Dimension Index Sequence (0020,9222) for this multi-frame header frame. The number of values is equal to the number of Items of the Dimension Index Sequence and shall be applied in the same order.
See section C.7.6.17.1 for a description.
Required if the value of the Dimension Index Sequence (0020,9222) contains Items.</description>
    </entry>
    <entry group="0020" element="9128" name="&gt;Temporal Position Index" type="3">
      <description>Ordinal number (starting from 1) of the frame in the set of frames with different temporal positions.</description>
    </entry>
    <entry group="0020" element="9056" name="&gt;Stack ID" type="3">
      <description>Identification of a group of frames, with different positions and/or orientations that belong together, within a dimension organization.
See C.7.6.16.2.2.4 for further explanation</description>
      <section ref="C.7.6.16.2.2.4" name="">Due to implementation specific reasons (such as maximum object size) the information of a multi-frame image may be split into more than one SOP Instance. These SOP Instances form together a Concatenation. This is a group of SOP Instances within a Series that is uniquely identified by the Concatenation UID (0020,9161).
The Dimension Index Sequence (0020,9222) for each SOP Instance with the same Concatenation UID (0020,9161) shall contain exactly the same tags and values.
In a Concatenation the Dimension Index Sequence (0020,9222) items of the Shared Functional Groups (5200,9229) shall be identical and have the same values for all individual SOP Instances. The items of the Per-frame Functional Groups (5200,9230) shall be identical for all individual SOP Instances but the values may change per frame. For all other Attributes of all the Modules of the IOD, the same Attributes shall be present and the values shall be identical, with the exception of the following Attributes:
</section>
    </entry>
    <entry group="0020" element="9057" name="&gt;In-Stack Position Number" type="1C">
      <description>The ordinal number of a frame in a group of frames, with the same Stack ID
Required if Stack ID (0020,9056) is present.
See section C.7.6.16.2.2.4 for further explanation.</description>
    </entry>
    <entry group="0020" element="9158" name="&gt;Frame Comments" type="3">
      <description>User-defined comments about the frame.</description>
    </entry>
    <entry group="0020" element="9453" name="&gt;Frame Label" type="3">
      <description>Label corresponding to a specific dimension index value. Selected from a set of dimension values defined by the application.
This attribute may be referenced by the Dimension Index Pointer (0020,9165) attribute in the Multi-frame Dimension Module.
See C.7.6.16.2.2.5 for further explanation.</description>
      <section ref="C.7.6.16.2.2.5" name="">The Frame Label attribute (0020,9453) can be used to label frames that need to be handled as a group in application. The Dimension Index Pointer (0020,9165) from the Dimension Module may point to this attribute if it is the base of a dimension.
</section>
    </entry>
  </macro>
  <macro table="C.7.6.16-4" name="Plane Position Macro Attributes">
    <entry group="0020" element="9113" name="Plane Position Sequence" type="1">
      <description>Identifies the position of the plane of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0020" element="0032" name="&gt;Image Position (Patient)" type="1C">
      <description>The x, y, and z coordinates of the upper left hand corner (center of the first voxel transmitted) of the frame, in mm. See C.7.6.2.1.1 and C.7.6.16.2.3.1 for further explanation.
Note: In the case of CT images with an Acquisition Type (0018,9302) of CONSTANT_ANGLE the image plane is defined to pass through the data collection center and be normal to the central ray of the diverging X-Ray beam.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Volumetric Properties (0008,9206) of this frame is other than DISTORTED, may be present otherwise.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
  </macro>
  <macro table="C.7.6.16-5" name="Plane Orientation Macro Attributes">
    <entry group="0020" element="9116" name="Plane Orientation Sequence" type="1">
      <description>Identifies orientation of the plane of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0020" element="0037" name="&gt;Image Orientation (Patient)" type="1C">
      <description>The direction cosines of the first row and the first column with respect to the patient. See C.7.6.2.1.1 and C.7.6.16.2.3.1 for further explanation.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Volumetric Properties (0008,9206) of this frame is other than DISTORTED. May be present otherwise.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
  </macro>
  <macro table="C.7.6.16-6" name="Referenced Image Macro Attributes">
    <entry group="0008" element="1140" name="Referenced Image Sequence" type="2">
      <description>A sequence that provides reference to a set of SOP Class/Instance pairs identifying images or other composite SOP Instances used to plan the acquisition or significant related images. See Section C.7.6.16.2.5.1 for further explanation. Zero or more Items may be included in this Sequence.</description>
      <section ref="C.7.6.16.2.5.1" name="">Referenced Image Sequence (0008,1140) shall be used to provide a reference to a set of SOP Class/Instance pairs identifying other data objects used to plan the acquisition of this image where the images shall share the same Frame of Reference UID (0020,0052). For each Item that contains such a reference, the value of the Purpose of Reference Code Sequence (0040,A170) shall be (”121311”, DCM, ”Localizer"). Applications can use the Referenced Image Sequence (0008,1140) in combination with data in Plane Position and Plane Orientation Macros to provide projections of the position of an image with respect to the referenced image.
The Referenced Image Sequence (0008,1140) may also be present when references to other images (or frames within other images) are required for other reasons, as specified by Purpose of Reference Code Sequence (0040,A170).
Note:  An Image may contain references to itself (e.g. to other frames within itself).

</section>
    </entry>
    <include ref="&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="1">
      <description>Describes the purpose for which the reference is made. Only a single Item shall be permitted in this sequence.
See C.7.6.16.2.5.1 for further explanation.</description>
      <section ref="C.7.6.16.2.5.1" name="">Referenced Image Sequence (0008,1140) shall be used to provide a reference to a set of SOP Class/Instance pairs identifying other data objects used to plan the acquisition of this image where the images shall share the same Frame of Reference UID (0020,0052). For each Item that contains such a reference, the value of the Purpose of Reference Code Sequence (0040,A170) shall be (”121311”, DCM, ”Localizer"). Applications can use the Referenced Image Sequence (0008,1140) in combination with data in Plane Position and Plane Orientation Macros to provide projections of the position of an image with respect to the referenced image.
The Referenced Image Sequence (0008,1140) may also be present when references to other images (or frames within other images) are required for other reasons, as specified by Purpose of Reference Code Sequence (0040,A170).
Note:  An Image may contain references to itself (e.g. to other frames within itself).

</section>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 7201."/>
  </macro>
  <macro table="C.7.6.16-7" name="Derivation Image Macro Attributes">
    <entry group="0008" element="9124" name="Derivation Image Sequence" type="2">
      <description>A sequence that that provides reference to the set of SOP Class/Instance pairs of the Images or other composite SOP Instances which were used to derive this frame. Zero or more Items may be included in this Sequence.</description>
    </entry>
    <entry group="0008" element="2111" name="&gt;Derivation Description" type="3">
      <description>A text description of how this frame data was derived. See C.7.6.1.1.3 for further explanation.</description>
      <section ref="C.7.6.1.1.3" name="">If an Image is identified to be a derived image (see C.7.6.1.1.2 Image Type), Derivation Description (0008,2111) and Derivation Code Sequence (0008,9215) describe the way in which the image was derived. They may be used whether or not the Source Image Sequence (0008,2112) is provided. They may also be used in cases when the Derived Image pixel data is not significantly changed from one of the source images and the SOP Instance UID of the Derived Image is the same as the one used for the source image.
Notes:  1. Examples of Derived Images that would normally be expected to affect professional interpretation and would thus have a new UID include:
  a.  images resulting from image processing of another image (e.g. unsharp masking),
  b.  a multiplanar reformatted CT image,
  c.  a DSA image derived by subtracting pixel values of one image from another.
d.  an image that has been decompressed after having been compressed with a lossy compression algorithm. To ensure that the user has the necessary information about the lossy compression, the approximate compression ratio may be included in Derivation Description (0008,2111).
  An example of a Derived Image that would normally not be expected to affect professional interpretation and thus would not require a new UID is an image that has been padded with additional rows and columns for more display purposes.
  2. An image may be lossy compressed, e.g., for long term archive purposes, and its SOP Instance UID changed. PS3.4 provides a mechanism by which a query for the original image Instance may return a reference to the UID of the lossy compressed version of the image using the Alternate Representation Sequence (0008,3001). This allows an application processing a SOP Instance that references the original image UID, e.g., a Structured Report, to obtain a reference to an accessible version of the image even if the original SOP Instance is no longer available.

</section>
    </entry>
    <entry group="0008" element="9215" name="&gt;Derivation Code Sequence" type="1">
      <description>A coded description of how this frame was derived. See C.7.6.1.1.3 for further explanation. One or more Items may be included in this Sequence. More than one Item indicates that successive derivation steps have been applied.</description>
      <section ref="C.7.6.1.1.3" name="">If an Image is identified to be a derived image (see C.7.6.1.1.2 Image Type), Derivation Description (0008,2111) and Derivation Code Sequence (0008,9215) describe the way in which the image was derived. They may be used whether or not the Source Image Sequence (0008,2112) is provided. They may also be used in cases when the Derived Image pixel data is not significantly changed from one of the source images and the SOP Instance UID of the Derived Image is the same as the one used for the source image.
Notes:  1. Examples of Derived Images that would normally be expected to affect professional interpretation and would thus have a new UID include:
  a.  images resulting from image processing of another image (e.g. unsharp masking),
  b.  a multiplanar reformatted CT image,
  c.  a DSA image derived by subtracting pixel values of one image from another.
d.  an image that has been decompressed after having been compressed with a lossy compression algorithm. To ensure that the user has the necessary information about the lossy compression, the approximate compression ratio may be included in Derivation Description (0008,2111).
  An example of a Derived Image that would normally not be expected to affect professional interpretation and thus would not require a new UID is an image that has been padded with additional rows and columns for more display purposes.
  2. An image may be lossy compressed, e.g., for long term archive purposes, and its SOP Instance UID changed. PS3.4 provides a mechanism by which a query for the original image Instance may return a reference to the UID of the lossy compressed version of the image using the Alternate Representation Sequence (0008,3001). This allows an application processing a SOP Instance that references the original image UID, e.g., a Structured Report, to obtain a reference to an accessible version of the image even if the original SOP Instance is no longer available.

</section>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 7203."/>
    <entry group="0008" element="2112" name="&gt;Source Image Sequence" type="2">
      <description>A Sequence which identifies the set of Image or other SOP Class/Instance pairs of the Instances which were used to derive this frame. Zero or more Items may be included in this Sequence. See C.7.6.1.1.4 for further explanation.</description>
      <section ref="C.7.6.1.1.4" name="">If an Image is identified to be a Derived image (see C.7.6.1.1.2 Image Type), Source Image Sequence (0008,2112) is an optional list of Referenced SOP Class UID (0008,1150)/ Referenced SOP Instance UID (0008,1150) pairs that identify the source images used to create the Derived image. It may be used whether or not there is a description of the way the image was derived in Derivation Description (0008,2111) or Derivation Code Sequence (0008,9215).
Note:  Multiple Items may be present within Source Image Sequence (0008,2112), in which case either:
  a) those images were combined to make the derived image (e.g. multiple source images to make an MPR or MIP), or
  b) each of the items represents a step in the successive derivation of an image (e.g. when an image has had successive lossy compression steps applied to it),
  c) some combination of the above.
  The Purpose of Reference Code Sequence (0040,A170) and the Attributes within the referenced images themselves may be used to determine the history of the derivation, which is not otherwise explicitly specified.

</section>
    </entry>
    <include ref="&gt;&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0040" element="A170" name="&gt;&gt;Purpose of Reference Code Sequence" type="1">
      <description>Describes the purpose for which the reference is made, that is what role the source image or frame played in the derivation of this image or frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 7202."/>
  </macro>
  <macro table="C.7.6.16-8" name="Cardiac Synchronization Macro Attributes">
    <entry group="0018" element="9118" name="Cardiac Synchronization Sequence" type="1">
      <description>Sequence that describes the frame specific cardiac synchronization parameters.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0020" element="9241" name="&gt;Nominal Percentage of Cardiac Phase" type="1C">
      <description>The nominal time relative to the preceding R peak divided by the nominal R-R interval multiplied by 100.
Required if used as a dimension index, may be present otherwise.</description>
    </entry>
    <entry group="0020" element="9153" name="&gt;Nominal Cardiac Trigger Delay Time" type="1">
      <description>The nominal time in ms from the time of the previous R-peak to the value of the Frame Reference DateTime (0018,9151). See C.7.6.16.2.7.1 for further explanation.</description>
      <section ref="C.7.6.16.2.7.1" name="">The Nominal Cardiac Trigger Delay Time (0020,9153) is the nominal trigger delay time in ms from the previous R-peak to the value of the Frame Reference DateTime (0018,9151). When frames are acquired with prospective gating, that is, the data acquisition actually begins in response to a timed delay from the R-peak, it may be that Actual Cardiac Trigger Delay Time (0020,9252) and the Nominal Cardiac Trigger Delay Time (0020,9153) have the same value.
However, when frames are the result of retrospective gating, that is, the data is continuously acquired and then later compared with a simultaneously acquired ECG waveform and fitted into time slots corresponding to nominal phases of the cardiac cycle, then Nominal Cardiac Trigger Delay Time (0020,9153) and the Actual Cardiac Trigger Delay Time (0020,9252) may have different values.
When multiple cardiac cycles are averaged together, then the Low R-R Value (0018,1081), and High R-R Value (0018,1082) are an average of the cardiac cycles that were accepted in the frame.
Note:   For cardiac gated acquisitions the choice of the Frame Reference DateTime (0018,9151) is influenced by the Nominal Cardiac Trigger Delay Time (0020,9153). For respiratory gated acquisitions the choice of the Frame Reference DateTime (0018,9151) is influenced by the Nominal Respiratory Trigger Delay Time (0020,9255).
Figure C.7.6.16-5 depicts the usage.
</section>
    </entry>
    <entry group="0020" element="9252" name="&gt;Actual Cardiac Trigger Delay Time" type="1C">
      <description>The actual time in ms from the time of the previous R-peak to the value of the Frame Reference DateTime (0018,9151). See C.7.6.16.2.7.1 for further explanation.
Required if Intervals Acquired (0018,1083) is present and has a value of 1. May be present otherwise.</description>
      <section ref="C.7.6.16.2.7.1" name="">The Nominal Cardiac Trigger Delay Time (0020,9153) is the nominal trigger delay time in ms from the previous R-peak to the value of the Frame Reference DateTime (0018,9151). When frames are acquired with prospective gating, that is, the data acquisition actually begins in response to a timed delay from the R-peak, it may be that Actual Cardiac Trigger Delay Time (0020,9252) and the Nominal Cardiac Trigger Delay Time (0020,9153) have the same value.
However, when frames are the result of retrospective gating, that is, the data is continuously acquired and then later compared with a simultaneously acquired ECG waveform and fitted into time slots corresponding to nominal phases of the cardiac cycle, then Nominal Cardiac Trigger Delay Time (0020,9153) and the Actual Cardiac Trigger Delay Time (0020,9252) may have different values.
When multiple cardiac cycles are averaged together, then the Low R-R Value (0018,1081), and High R-R Value (0018,1082) are an average of the cardiac cycles that were accepted in the frame.
Note:   For cardiac gated acquisitions the choice of the Frame Reference DateTime (0018,9151) is influenced by the Nominal Cardiac Trigger Delay Time (0020,9153). For respiratory gated acquisitions the choice of the Frame Reference DateTime (0018,9151) is influenced by the Nominal Respiratory Trigger Delay Time (0020,9255).
Figure C.7.6.16-5 depicts the usage.
</section>
    </entry>
    <entry group="0018" element="1083" name="&gt;Intervals Acquired" type="3">
      <description>Number of R-R intervals acquired.</description>
    </entry>
    <entry group="0018" element="1084" name="&gt;Intervals Rejected" type="3">
      <description>Number of R-R intervals rejected.</description>
    </entry>
    <entry group="0018" element="1088" name="&gt;Heart Rate" type="3">
      <description>Average number of heart beats per minute for the collection period for this frame. This shall include all accepted beats as well as rejected beats.
Note: During prolonged acquisitions the average heart rate may differ from the reciprocal of the nominal R-R interval.</description>
    </entry>
    <entry group="0020" element="9251" name="&gt;R - R Interval Time Nominal" type="1C">
      <description>Nominal R-peak - R-peak interval time in ms for the cardiac cycle used for the acquisition of this frame. See C.7.6.16.2.7.1 for further explanation.
Required if Cardiac Synchronization Technique (0018,9037) equals other than NONE or REALTIME. May be present otherwise.</description>
      <section ref="C.7.6.16.2.7.1" name="">The Nominal Cardiac Trigger Delay Time (0020,9153) is the nominal trigger delay time in ms from the previous R-peak to the value of the Frame Reference DateTime (0018,9151). When frames are acquired with prospective gating, that is, the data acquisition actually begins in response to a timed delay from the R-peak, it may be that Actual Cardiac Trigger Delay Time (0020,9252) and the Nominal Cardiac Trigger Delay Time (0020,9153) have the same value.
However, when frames are the result of retrospective gating, that is, the data is continuously acquired and then later compared with a simultaneously acquired ECG waveform and fitted into time slots corresponding to nominal phases of the cardiac cycle, then Nominal Cardiac Trigger Delay Time (0020,9153) and the Actual Cardiac Trigger Delay Time (0020,9252) may have different values.
When multiple cardiac cycles are averaged together, then the Low R-R Value (0018,1081), and High R-R Value (0018,1082) are an average of the cardiac cycles that were accepted in the frame.
Note:   For cardiac gated acquisitions the choice of the Frame Reference DateTime (0018,9151) is influenced by the Nominal Cardiac Trigger Delay Time (0020,9153). For respiratory gated acquisitions the choice of the Frame Reference DateTime (0018,9151) is influenced by the Nominal Respiratory Trigger Delay Time (0020,9255).
Figure C.7.6.16-5 depicts the usage.
</section>
    </entry>
    <entry group="0018" element="1081" name="&gt;Low R-R Value" type="3">
      <description>R-R interval low limit for beat rejection, in ms.</description>
    </entry>
    <entry group="0018" element="1082" name="&gt;High R-R Value" type="3">
      <description>R-R interval high limit for beat rejection, in ms.</description>
    </entry>
  </macro>
  <macro table="C.7.6.16-9" name="Frame Anatomy Macro Attributes">
    <entry group="0020" element="9071" name="Frame Anatomy Sequence" type="1">
      <description>Identifies anatomic characteristics of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0020" element="9072" name="&gt;Frame Laterality" type="1">
      <description>Laterality of (possibly paired) body parts (as described in Anatomic Region Sequence (0008,2218)) examined.
Enumerated Values:
R = right
L = left
U = unpaired
B = both left and right
Note: This Attribute is mandatory, in order to ensure that frames may be positioned correctly relative to one another for display.
Shall be consistent with any laterality information contained in Primary Anatomic Structure Modifier Sequence (0008,2230), if present.</description>
    </entry>
    <include ref="&gt;Include 'General Anatomy Mandatory Macro' Table 10-5" description="Defined Context ID for the Anatomic Region Sequence (0008,2218) is 4030.Defined Context ID for Anatomic Region Modifier Sequence (0008,2220) and Primary Anatomic Structure Modifier Sequence (0008,2230) is 2."/>
  </macro>
  <macro table="C.7.6.16-10" name="Pixel Value Transformation Macro Attributes">
    <entry group="0028" element="9145" name="Pixel Value Transformation Sequence" type="1">
      <description>Contains the attributes involved in the transformation of stored pixel values. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0028" element="1052" name="&gt;Rescale Intercept" type="1">
      <description>The value b in relationship between stored values (SV) and the output units.
Output units = m*SV + b.</description>
    </entry>
    <entry group="0028" element="1053" name="&gt;Rescale Slope" type="1">
      <description>m in the equation specified by Rescale Intercept (0028,1052).</description>
    </entry>
    <entry group="0028" element="1054" name="&gt;Rescale Type" type="1">
      <description>Specifies the output units of Rescale Slope (0028,1053) and Rescale Intercept (0028,1052).
See C.11.1.1.2 for further explanation.
Enumerated Value:
US = Unspecified if Modality (0008,0060) equals MR.</description>
      <section ref="C.11.1.1.2" name="">Specifies the units of the output of the Modality LUT or rescale operation.
Defined Terms:
  OD = The number in the LUT represents thousands of optical density. That is, a value of 2140 represents an optical density of 2.140.
  HU = Hounsfield Units (CT)
  US = Unspecified
Other values are permitted, but are not defined by the DICOM Standard.
</section>
    </entry>
  </macro>
  <macro table="C.7.6.16-11" name="Frame VOI LUT Macro Attributes">
    <entry group="0028" element="9132" name="Frame VOI LUT Sequence" type="1">
      <description>Window Center and Width values applied to the frame. Only one item is permitted in this sequence.</description>
    </entry>
    <entry group="0028" element="1050" name="&gt;Window Center" type="1">
      <description>Window Center for display. See C.11.2.1.2 for further explanation.</description>
      <section ref="C.11.2.1.2" name="">Window Center (0028,1050) and Window Width (0028,1051) specify a linear conversion from stored pixel values (after any Modality LUT or Rescale Slope and Intercept specified in the IOD have been applied) to values to be displayed. Window Center contains the input value that is the center of the window. Window Width contains the width of the window.
Note:  The terms “window center” and “window width” are not consistently used in practice, nor were they defined in previous versions of the standard. The definitions here are presented for the purpose of defining consistent meanings for identity and threshold transformations while preserving the common practice of using integral values for center and width.

Window Width (0028,1051) shall always be greater than or equal to 1.
When Window Width (0028,1051) is greater than 1, these Attributes select the range of input values that are to be mapped to the full range of the displayed output.
When Window Width (0028,1051) is equal to 1, they specify a threshold below which input values will be displayed as the minimum output value.
Note:  Whether the minimum output value is rendered as black or white may depend on the value of Photometric Interpretation (0028,0004) or the presence of a Presentation LUT Module.

These Attributes are applied according to the following pseudo-code, where x is the input value, y is an output value with a range from ymin to ymax, c is Window Center (0028,1050) and w is Window Width (0028,1051):
    if  (x &lt;= c - 0.5 - (w-1)/2), then y = ymin
    else if  (x &gt; c - 0.5 + (w-1)/2), then y = ymax,
    else  y = ((x - (c - 0.5)) / (w-1) + 0.5) * (ymax - ymin)+ ymin

Notes:  1. For the purpose of this definition, a floating point calculation without integer truncation is assumed, though the manner of implementation may vary as long as the result is the same.
  2. The pseudo-code function computes a continuous value over the output range without any discontinuity at the boundaries. The value of 0 for w is expressly forbidden, and the value of 1 for w does not cause division by zero, since the continuous segment of the function will never be reached for that case.
  3. For example, for an output range 0 to 255:
    c=2048, w=4096 becomes:
      if (x &lt;= 0) then y = 0
      else if (x &gt; 4095) then y = 255
      else y = ((x - 2047.5) / 4095 + 0.5) * (255-0) + 0
    c=2048, w=1 becomes:
      if (x &lt;= 2047.5) then y = 0
      else if (x &gt; 2047.5) then y = 255
      else /* not reached */

    c=0, w=100 becomes:
      if (x &lt;= -50) then y = 0
      else if (x &gt; 49) then y = 255
      else y = ((x + 0.5) / 99 + 0.5) * (255-0) + 0
    c=0, w=1 becomes:
      if (x &lt;= -0.5) then y = 0
      else if (x &gt; -0.5) then y = 255
      else /* not reached */

  4. A Window Center of 2n-1 and a Window Width of 2n selects the range of input values from 0 to 2n-1. This represents an identity VOI LUT transformation in the case where no Modality LUT is specified and the stored pixel data are n bit unsigned integers.
  5. A Window Width of 1 is typically used to represent a "threshold" operation in which those integer input values less than the Window Center are represented as the minimum displayed value and those greater than or equal to the Window Center are represented as the maximum displayed value. A Window Width of 2 will have the same result for integral input values.
  6. The application of Window Center (0028,1050) and Window Width (0028,1051) may select a signed input range. There is no implication that this signed input range is clipped to zero.
  7. The selected input range may exceed the actual range of the input values, thus effectively “compressing” the contrast range of the displayed data into a narrower band of the available contrast range, and “flattening” the appearance. There are no limits to the maximum value of the window width, or to the minimum or maximum value of window level, both of which may exceed the actual or possible range of input values.
  8. Input values "below" the window are displayed as the minimum output value and input values "above" the window are displayed as the maximum output value. This is the common usage of the window operation in medical imaging. There is no provision for an alternative approach in which all values "outside" the window are displayed as the minimum output value.
  9. The output of the Window Center/Width or VOI LUT transformation is either implicitly scaled to the full range of the display device if there is no succeeding transformation defined, or implicitly scaled to the full input range of the succeeding transformation step (such as the Presentation LUT), if present. See C.11.6.1.
  10. Fractional values of Window Center and Window Width are permitted (since the VR of these Attributes is Decimal String), and though they are not often encountered, applications should be prepared to accept them.

These Attributes shall be used only for Images with Photometric Interpretation (0028,0004) values of MONOCHROME1 and MONOCHROME2. They have no meaning for other Images.
If multiple values are present, both Attributes shall have the same number of values and shall be considered as pairs. Multiple values indicate that multiple alternative views may be presented.
If any VOI LUT Table is included by an Image, a Window Width and Window Center or the VOI LUT Table, but not both, may be applied to the Image for display. Inclusion of both indicates that multiple alternative views may be presented.
If multiple items are present in VOI LUT Sequence (0028,3010), only one may be applied to the Image for display. Multiple items indicate that multiple alternative views may be presented.
If the VOI LUT Module is defined in an IOD and if neither a VOI LUT Sequence nor a Window Width and Window Center are present, then the VOI LUT stage of the grayscale pipeline is defined to be an identity transformation.
Notes:  1. This requirement is specified so that IODs that define a particular output space for the grayscale pipeline, such as P-Values, are not in an undefined state when no VOI LUT Sequence or Window Width and Window Center are present.
  2. Despite the Type 3 requirement for VOI LUT Sequence and Window Center, implementations that render images are expected to implement and apply these transformations when they are present in the image, unless overridden by the user, a presentation state, or a hanging protocol, and to allow the user to select which transformation to apply when multiple transformations are present.

</section>
    </entry>
    <entry group="0028" element="1051" name="&gt;Window Width" type="1">
      <description>Window Width for display. See C.11.2.1.2 for further explanation.</description>
      <section ref="C.11.2.1.2" name="">Window Center (0028,1050) and Window Width (0028,1051) specify a linear conversion from stored pixel values (after any Modality LUT or Rescale Slope and Intercept specified in the IOD have been applied) to values to be displayed. Window Center contains the input value that is the center of the window. Window Width contains the width of the window.
Note:  The terms “window center” and “window width” are not consistently used in practice, nor were they defined in previous versions of the standard. The definitions here are presented for the purpose of defining consistent meanings for identity and threshold transformations while preserving the common practice of using integral values for center and width.

Window Width (0028,1051) shall always be greater than or equal to 1.
When Window Width (0028,1051) is greater than 1, these Attributes select the range of input values that are to be mapped to the full range of the displayed output.
When Window Width (0028,1051) is equal to 1, they specify a threshold below which input values will be displayed as the minimum output value.
Note:  Whether the minimum output value is rendered as black or white may depend on the value of Photometric Interpretation (0028,0004) or the presence of a Presentation LUT Module.

These Attributes are applied according to the following pseudo-code, where x is the input value, y is an output value with a range from ymin to ymax, c is Window Center (0028,1050) and w is Window Width (0028,1051):
    if  (x &lt;= c - 0.5 - (w-1)/2), then y = ymin
    else if  (x &gt; c - 0.5 + (w-1)/2), then y = ymax,
    else  y = ((x - (c - 0.5)) / (w-1) + 0.5) * (ymax - ymin)+ ymin

Notes:  1. For the purpose of this definition, a floating point calculation without integer truncation is assumed, though the manner of implementation may vary as long as the result is the same.
  2. The pseudo-code function computes a continuous value over the output range without any discontinuity at the boundaries. The value of 0 for w is expressly forbidden, and the value of 1 for w does not cause division by zero, since the continuous segment of the function will never be reached for that case.
  3. For example, for an output range 0 to 255:
    c=2048, w=4096 becomes:
      if (x &lt;= 0) then y = 0
      else if (x &gt; 4095) then y = 255
      else y = ((x - 2047.5) / 4095 + 0.5) * (255-0) + 0
    c=2048, w=1 becomes:
      if (x &lt;= 2047.5) then y = 0
      else if (x &gt; 2047.5) then y = 255
      else /* not reached */

    c=0, w=100 becomes:
      if (x &lt;= -50) then y = 0
      else if (x &gt; 49) then y = 255
      else y = ((x + 0.5) / 99 + 0.5) * (255-0) + 0
    c=0, w=1 becomes:
      if (x &lt;= -0.5) then y = 0
      else if (x &gt; -0.5) then y = 255
      else /* not reached */

  4. A Window Center of 2n-1 and a Window Width of 2n selects the range of input values from 0 to 2n-1. This represents an identity VOI LUT transformation in the case where no Modality LUT is specified and the stored pixel data are n bit unsigned integers.
  5. A Window Width of 1 is typically used to represent a "threshold" operation in which those integer input values less than the Window Center are represented as the minimum displayed value and those greater than or equal to the Window Center are represented as the maximum displayed value. A Window Width of 2 will have the same result for integral input values.
  6. The application of Window Center (0028,1050) and Window Width (0028,1051) may select a signed input range. There is no implication that this signed input range is clipped to zero.
  7. The selected input range may exceed the actual range of the input values, thus effectively “compressing” the contrast range of the displayed data into a narrower band of the available contrast range, and “flattening” the appearance. There are no limits to the maximum value of the window width, or to the minimum or maximum value of window level, both of which may exceed the actual or possible range of input values.
  8. Input values "below" the window are displayed as the minimum output value and input values "above" the window are displayed as the maximum output value. This is the common usage of the window operation in medical imaging. There is no provision for an alternative approach in which all values "outside" the window are displayed as the minimum output value.
  9. The output of the Window Center/Width or VOI LUT transformation is either implicitly scaled to the full range of the display device if there is no succeeding transformation defined, or implicitly scaled to the full input range of the succeeding transformation step (such as the Presentation LUT), if present. See C.11.6.1.
  10. Fractional values of Window Center and Window Width are permitted (since the VR of these Attributes is Decimal String), and though they are not often encountered, applications should be prepared to accept them.

These Attributes shall be used only for Images with Photometric Interpretation (0028,0004) values of MONOCHROME1 and MONOCHROME2. They have no meaning for other Images.
If multiple values are present, both Attributes shall have the same number of values and shall be considered as pairs. Multiple values indicate that multiple alternative views may be presented.
If any VOI LUT Table is included by an Image, a Window Width and Window Center or the VOI LUT Table, but not both, may be applied to the Image for display. Inclusion of both indicates that multiple alternative views may be presented.
If multiple items are present in VOI LUT Sequence (0028,3010), only one may be applied to the Image for display. Multiple items indicate that multiple alternative views may be presented.
If the VOI LUT Module is defined in an IOD and if neither a VOI LUT Sequence nor a Window Width and Window Center are present, then the VOI LUT stage of the grayscale pipeline is defined to be an identity transformation.
Notes:  1. This requirement is specified so that IODs that define a particular output space for the grayscale pipeline, such as P-Values, are not in an undefined state when no VOI LUT Sequence or Window Width and Window Center are present.
  2. Despite the Type 3 requirement for VOI LUT Sequence and Window Center, implementations that render images are expected to implement and apply these transformations when they are present in the image, unless overridden by the user, a presentation state, or a hanging protocol, and to allow the user to select which transformation to apply when multiple transformations are present.

</section>
    </entry>
    <entry group="0028" element="1055" name="&gt;Window Center &amp; Width Explanation" type="3">
      <description>Explanation of the Window Center and Width.
Defined Terms for CT:
BRAIN
SOFT_TISSUE
LUNG
BONE</description>
    </entry>
    <entry group="0028" element="1056" name="&gt;VOI LUT Function" type="3">
      <description>Describes a VOI LUT function to apply to the values of Window Center (0028,1050) and Window Width (0028,1051).
See C.11.2.1.3 for further explanation.
Defined terms:
LINEAR
SIGMOID
When this attribute is not present, the interpretation of the values of Window Center (0028,1050) and Window Width (0028,1051) is linear as in C.11.2.1.2.</description>
      <section ref="C.11.2.1.3" name="">The VOI LUT Function (0028,1056) specifies a potentially non-linear conversion for the output of the (conceptual) Modality LUT values to the input of the (conceptual) Presentation LUT.
The behavior for the value LINEAR is defined in C.11.2.1.2. For all other values, the VOI LUT Function (0028,1056) shall include a unique descriptor of the LUT function to be used. Each descriptor is associated with a bivariate function of Window Center (0028,1050) and Window Width (0028,1051).
If the VOI LUT Function (0028,1056) is present with a value other than LINEAR, the values provided in Window Center (0028,1050) and Window Width (0028,1051) shall not be interpreted as a linear conversion of the (conceptual) Modality LUT values to the input to the (conceptual) Presentation LUT – but as parameters for the function defined by the VOI LUT Function descriptor in (0028,1056).
When defined, each descriptor must provide the functional relationship between the output of the (conceptual) Modality LUT values to the input of the (conceptual) Presentation LUT.
</section>
    </entry>
  </macro>
  <macro table="C.7.6.16-12" name="Real World Value Mapping Macro Attributes">
    <entry group="0040" element="9096" name="Real World Value Mapping Sequence" type="1">
      <description>The mapping of stored values to associated real world values. One or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0040" element="9216" name="&gt;Real World Value First Value Mapped" type="1">
      <description>Specifies the first stored value mapped for the Real Word Value Intercept (0040,9224) and Real World Value Slope (0040,9225) or Real World Value LUT (0040,9212) of this Item.
See C.7.6.16.2.11.1 for further explanation.</description>
      <section ref="C.7.6.16.2.11.1" name=""/>
    </entry>
    <entry group="0040" element="9211" name="&gt;Real World Value Last Value Mapped" type="1">
      <description>Specifies the last stored value mapped for the Real Word Value Intercept (0040,9224) and Real World Value Slope (0040,9225) or Real World Value LUT (0040,9212) of this Item.
See C.7.6.16.2.11.1 for further explanation.</description>
      <section ref="C.7.6.16.2.11.1" name=""/>
    </entry>
    <entry group="0040" element="9224" name="&gt;Real World Value Intercept" type="1C">
      <description>The Intercept value in relationship between stored values (SV) and the real world values.
See section C.7.6.16.2.11.2 for further explanation.
Required if Real World Value LUT Data (0040,9212) is not present.</description>
    </entry>
    <entry group="0040" element="9225" name="&gt;Real World Value Slope" type="1C">
      <description>The Slope value in relationship between stored values (SV) and the real world values.
See section C.7.6.16.2.11.2 for further explanation.
Required if Real World Value LUT Data (0040,9212) is not present.</description>
    </entry>
    <entry group="0040" element="9212" name="&gt;Real World Value LUT Data" type="1C">
      <description>LUT Data in this Sequence.
Required if Real World Value Intercept (0040,9224) is not present.</description>
    </entry>
    <entry group="0028" element="3003" name="&gt;LUT Explanation" type="1">
      <description>Free form text explanation of the meaning of the LUT.</description>
    </entry>
    <entry group="0040" element="9210" name="&gt;LUT Label" type="1">
      <description>Label that is used to identify this transformation.</description>
    </entry>
    <entry group="0040" element="08EA" name="&gt;Measurement Units Code Sequence" type="1">
      <description>Units of measurement. Only a single value shall be present. See C.7.6.16.2.11.1 for further explanation.</description>
      <section ref="C.7.6.16.2.11.1" name=""/>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="Defined Context ID is 82"/>
  </macro>
  <macro table="C.7.16-13" name="Contrast/bolus Usage Functional Group Macro Attributes">
    <entry group="0018" element="9341" name="Contrast/Bolus Usage Sequence" type="1">
      <description>Contains the attributes describing the use of contrast for this frame. One or more Items shall be present in this sequence.</description>
    </entry>
    <entry group="0018" element="9337" name="&gt;Contrast/Bolus Agent Number" type="1">
      <description>Identifying number corresponding to the agent described in the Enhanced Contrast/Bolus Module. The number shall be 1 for the first Item and increase by 1 for each subsequent Item.</description>
    </entry>
    <entry group="0018" element="9342" name="&gt;Contrast/Bolus Agent Administered" type="1">
      <description>The administration of the selected agent had begun by the time this frame was acquired.
Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="0018" element="9343" name="&gt;Contrast/Bolus Agent Detected" type="2">
      <description>The selected agent was detected in the frame.
Enumerated Values:
YES
NO
May only be zero length if the acquisition device is not capable of detecting the presence of this contrast agent in the frame.</description>
    </entry>
    <entry group="0018" element="9344" name="&gt;Contrast/Bolus Agent Phase" type="2C">
      <description>Nominal phase of intravenous contrast administration.
Defined terms:
PRE_CONTRAST
POST_CONTRAST
IMMEDIATE
DYNAMIC
STEADY_STATE
DELAYED
ARTERIAL
CAPILLARY
VENOUS
PORTAL_VENOUS
Required if Contrast/Bolus Administration Route Sequence (0018,0014) for the Contrast/Bolus Agent Number (0018,9337) defined in the Contrast/Bolus Agent Sequence (0018,0012) is (G-D101, SRT, "Intravenous route") or (G-D101, SNM3, "Intravenous route"); may be present otherwise.
Note: SRT is the preferred designator for SNOMED, but SNM3 is allowed for backward compatibility. See PS3.16.</description>
    </entry>
  </macro>
  <macro table="C.7.6.16-14" name="Pixel Intensity Relationship LUT Macro Attributes">
    <entry group="0028" element="9422" name="Pixel Intensity Relationship LUT Sequence" type="1">
      <description>Defines a sequence of Pixel Intensity Relationship LUTs.
One or more items shall be present in this sequence.
At least one item with LUT Function (0028,9474) equals TO_LINEAR LUT shall be present if Pixel Intensity Relationship (0028,1040) equals LOG.
Only a single item with LUT Function (0028,9474) equals TO_LINEAR LUT shall be present.</description>
    </entry>
    <entry group="0028" element="3002" name="&gt;LUT Descriptor" type="1">
      <description>Specifies the format of the LUT Data in this Sequence.
See C.11.1.1 and C.7.6.16.2.13.1 for further explanation.</description>
      <section ref="C.11.1.1" name=""/>
    </entry>
    <entry group="0028" element="3006" name="&gt;LUT Data" type="1">
      <description>LUT Data in this Sequence.</description>
    </entry>
    <entry group="0028" element="9474" name="&gt;LUT Function" type="1">
      <description>The transformation function this LUT applies to the stored pixel values.
Defined Terms:
TO_LOG
TO_LINEAR</description>
    </entry>
  </macro>
  <macro table="C.7.6.16-15" name="Frame Pixel Shift Macro Attributes">
    <entry group="0028" element="9415" name="Frame Pixel Shift Sequence" type="1">
      <description>Sequence containing the pixel shift for a number of masks for this frame.
One or more items shall be present in this sequence.</description>
    </entry>
    <entry group="0028" element="9416" name="&gt;Subtraction Item ID" type="1">
      <description>Identifier of the Subtraction Item in the Mask Subtraction Sequence (0028,6100) to which this pixel shift is associated.
See C.7.6.16.2.14.1.</description>
      <section ref="C.7.6.16.2.14.1" name="">Subtraction Item ID (0028,9416) specifies the ID of a subtraction operation to which the Mask Sub-pixel Shift (0028,6114) is associated. The Subtraction Item ID is also present in the Mask Subtraction Sequence (0028,6100) to allow this association.
When used as per-frame macro, the Subtraction Item ID (0028,9416) allows to specify different values of Mask Sub-pixel Shift (0028,6114) individually frame by frame, and relate them to a single item of the Mask Subtraction Sequence (0028,6100).
Note:  There is no restriction in the number of Subtraction Item ID’s associated to each contrast frame. The same contrast frame may be present in several items of the Mask Subtraction Sequence, each item having a different value of Subtraction Item ID.

When used as shared macro, the Subtraction Item ID (0028,9416) allows to specify one or more values of Mask Sub-pixel Shift that will be applied to all the frames of the Multi-frame image.
Note:  Example of usage of Subtraction Item ID in a per-frame macro, see Figure C.7.6.16-8:
  In this example of Multi-Frame Image with 3 frames, one Mask Frame (i.e., Frame 1) is applied to the next two frames of the Multi-Frame image (i.e., Frames 2 and 3). Therefore, there is only one item in the Mask Subtraction Sequence, containing its own Subtraction Item ID value (i.e., 100). The Frame Pixel Shift Macro allows to define a Mask Sub-Pixel Shift different for each contrast frame.
  First Frame Subtracted: Subtraction of Frame 1 (Mask) to Frame 2, with Sub-Pixel Shift 1.3\2.4
  Second Frame Subtracted: Subtraction of Frame 1 (Mask) to Frame 3, with Sub-Pixel Shift 1.9\3.0

Figure C.7.6.16-8
Example of usage of Subtraction Item ID in a per-frame Macro

</section>
    </entry>
    <entry group="0028" element="6114" name="&gt;Mask Sub-pixel Shift" type="1">
      <description>A pair of floating point numbers specifying the fractional vertical [adjacent row spacing] and horizontal [adjacent column spacing] pixel shift applied to the mask before subtracting it from this contrast frame.
Note: If no pixel shift has to be applied a pair of zero values should be specified.
See Section C.7.6.10.1.2.</description>
      <section ref="C.7.6.10.1.2" name="">A pair of floating point numbers specifying the fractional vertical [adjacent row spacing] and horizontal [adjacent column spacing] pixel shift applied to the mask before subtracting it from the contrast frame. The row offset results in a shift of the pixels along the column axis. The column offset results in a shift of the pixels along the row axis. A positive row offset is a shift toward the pixels of the lower row of the pixel plane. A positive column offset is a shift toward the pixels of the left hand side column of the pixel plane.
</section>
    </entry>
  </macro>
  <macro table="C.7.6.16-16" name="Patient Orientation in Frame Macro Attributes">
    <entry group="0020" element="9450" name="Patient Orientation in Frame Sequence" type="1">
      <description>Sequence containing the row and column directions for this frame in the patient.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0020" element="0020" name="&gt;Patient Orientation" type="1">
      <description>Patient direction of the rows and columns of this frame.
See C.7.6.1.1.1 for further explanation.</description>
      <section ref="C.7.6.1.1.1" name="">The Patient Orientation (0020,0020) relative to the image plane shall be specified by two values that designate the anatomical direction of the positive row axis (left to right) and the positive column axis (top to bottom). The first entry is the direction of the rows, given by the direction of the last pixel in the first row from the first pixel in that row. The second entry is the direction of the columns, given by the direction of the last pixel in the first column from the first pixel in that column.
Anatomical direction shall be designated by the capital letters: A (anterior), P (posterior), R (right), L (left), H (head), F (foot). Each value of the orientation attribute shall contain at least one of these characters. If refinements in the orientation descriptions are to be specified, then they shall be designated by one or two additional letters in each value. Within each value, the letters shall be ordered with the principal orientation designated in the first character.
</section>
    </entry>
  </macro>
  <macro table="C.7.6.16-17" name="Frame Display Shutter Macro Attributes">
    <entry group="0018" element="9472" name="Frame Display Shutter Sequence" type="1">
      <description>Sequence containing the display shutter parameters for this frame.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Display Shutter Macro' Table C.7-17A."/>
  </macro>
  <macro table="C.7.6.16-18" name="Respiratory Synchronization Macro Attributes">
    <entry group="0020" element="9253" name="Respiratory Synchronization Sequence" type="1">
      <description>Sequence that describes the frame specific respiratory synchronization parameters.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0020" element="9254" name="&gt;Respiratory Interval Time" type="1C">
      <description>Measured interval time in ms from maximum respiration peak to the next peak for the respiratory cycle in which this frame occurs. See C.7.6.16.2.17.1 for further explanation.
Required if Respiratory Motion Compensation Technique (0018,9170) equals other than NONE or REALTIME and Respiratory Trigger Type (0020,9250) is absent or has a value of TIME or BOTH.</description>
      <section ref="C.7.6.16.2.17.1" name="">For time based respiratory gating, the Nominal Respiratory Trigger Delay Time (0020,9255) is the prescribed trigger delay time in ms from the previous Respiratory-peak to the value of the Frame Reference DateTime (0018,9151). When frames are acquired with prospective gating, that is, the data acquisition actually begins in response to a timed delay from the Respiratory trigger, it may be that Actual Respiratory Trigger Delay Time (0020,9257) and the Nominal Respiratory Trigger Delay Time (0020,9255) have the same value.
However, when frames are the result of retrospective gating, that is, the data is continuously acquired and then later compared with a simultaneously acquired respiratory waveform and fitted into bins corresponding to nominal phases of the respiratory cycle, then Nominal Respiratory Trigger Delay Time (0020,9255) and the Actual Respiratory Trigger Delay Time (0020,9257) may have different values.
Figure C.7.6.16-9a and C.7.6.16-9b depict the usage.


Figure C.7.6.16-9a
Respiratory Timing Tags


Figure C.7.6.16-9b
Relationship of Respiratory Amplitude Attributes

</section>
    </entry>
    <entry group="0020" element="9245" name="&gt;Nominal Percentage of Respiratory Phase" type="1C">
      <description>The nominal time relative to the preceding respiratory inspiration maximum divided by the nominal respiratory interval multiplied by 100.
Required if used as a dimension index, may be present otherwise.</description>
    </entry>
    <entry group="0020" element="9255" name="&gt;Nominal Respiratory Trigger Delay Time" type="1">
      <description>The nominal time in ms from the beginning of the respiratory interval to the value of the Frame Reference DateTime (0018,9151). See C.7.6.16.2.17.1 for further explanation.</description>
      <section ref="C.7.6.16.2.17.1" name="">For time based respiratory gating, the Nominal Respiratory Trigger Delay Time (0020,9255) is the prescribed trigger delay time in ms from the previous Respiratory-peak to the value of the Frame Reference DateTime (0018,9151). When frames are acquired with prospective gating, that is, the data acquisition actually begins in response to a timed delay from the Respiratory trigger, it may be that Actual Respiratory Trigger Delay Time (0020,9257) and the Nominal Respiratory Trigger Delay Time (0020,9255) have the same value.
However, when frames are the result of retrospective gating, that is, the data is continuously acquired and then later compared with a simultaneously acquired respiratory waveform and fitted into bins corresponding to nominal phases of the respiratory cycle, then Nominal Respiratory Trigger Delay Time (0020,9255) and the Actual Respiratory Trigger Delay Time (0020,9257) may have different values.
Figure C.7.6.16-9a and C.7.6.16-9b depict the usage.


Figure C.7.6.16-9a
Respiratory Timing Tags


Figure C.7.6.16-9b
Relationship of Respiratory Amplitude Attributes

</section>
    </entry>
    <entry group="0020" element="9257" name="&gt;Actual Respiratory Trigger Delay Time" type="1C">
      <description>The actual time in ms from the beginning of the respiratory interval to the value of the Frame Reference DateTime (0018,9151). See C.7.6.16.2.17.1 for further explanation.
Required if Respiratory Trigger Type (0020,9250) is TIME or BOTH.</description>
      <section ref="C.7.6.16.2.17.1" name="">For time based respiratory gating, the Nominal Respiratory Trigger Delay Time (0020,9255) is the prescribed trigger delay time in ms from the previous Respiratory-peak to the value of the Frame Reference DateTime (0018,9151). When frames are acquired with prospective gating, that is, the data acquisition actually begins in response to a timed delay from the Respiratory trigger, it may be that Actual Respiratory Trigger Delay Time (0020,9257) and the Nominal Respiratory Trigger Delay Time (0020,9255) have the same value.
However, when frames are the result of retrospective gating, that is, the data is continuously acquired and then later compared with a simultaneously acquired respiratory waveform and fitted into bins corresponding to nominal phases of the respiratory cycle, then Nominal Respiratory Trigger Delay Time (0020,9255) and the Actual Respiratory Trigger Delay Time (0020,9257) may have different values.
Figure C.7.6.16-9a and C.7.6.16-9b depict the usage.


Figure C.7.6.16-9a
Respiratory Timing Tags


Figure C.7.6.16-9b
Relationship of Respiratory Amplitude Attributes

</section>
    </entry>
    <entry group="0020" element="9246" name="&gt;Starting Respiratory Amplitude" type="1C">
      <description>Nominal amplitude of the respiratory signal at which the acquisition of data for this frame begins, in percent of the nominal maximum value (which represents maximum inspiration).
Required if Respiratory Trigger Type (0020,9250) is AMPLITUDE or BOTH.</description>
    </entry>
    <entry group="0020" element="9247" name="&gt;Starting Respiratory Phase" type="1C">
      <description>The phase of respiration at which the Starting Respiratory Amplitude (0020,9246) was measured.
Enumerated Value:
INSPIRATION
MAXIMUM
EXPIRATION
MINIMUM
Required if Starting Respiratory Amplitude (0020,9246) is present.</description>
    </entry>
    <entry group="0020" element="9248" name="&gt;Ending Respiratory Amplitude" type="1C">
      <description>Nominal amplitude of the respiratory signal at which the acquisition of data for this frame ends, in percent of the nominal maximum value (which represents maximum inspiration).
Required if Respiratory Trigger Type (0020,9250) is AMPLITUDE or BOTH.</description>
    </entry>
    <entry group="0020" element="9249" name="&gt;Ending Respiratory Phase" type="1C">
      <description>The phase of respiration at which the Ending Respiratory Amplitude (0020,9248) was measured.
Enumerated Value:
INSPIRATION
MAXIMUM
EXPIRATION
MINIMUM
Required if Ending Respiratory Amplitude (0020,9248) is present.</description>
    </entry>
  </macro>
  <macro table="C.7.6.16-19" name="Irradiation Event Identification Macro Attributes">
    <entry group="0018" element="9477" name="Irradiation Event Identification Sequence" type="1">
      <description>Sequence containing the Irradiation Event Identification for this frame.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0008" element="3010" name="&gt;Irradiation Event UID" type="1">
      <description>Unique identification of the irradiation event(s) associated with the acquisition of this image.</description>
    </entry>
  </macro>
  <module ref="C.7.6.17" table="C.7.6.17-1" name="Multi Frame Dimension Module Attributes">
    <entry group="0020" element="9221" name="Dimension Organization Sequence" type="2">
      <description>Sequence that lists the Dimension Organization UIDs referenced by the containing SOP Instance. See section C.7.6.17.2 for further explanation. Zero or more Items may be included in this Sequence.</description>
    </entry>
    <entry group="0020" element="9164" name="&gt;Dimension Organization UID" type="1">
      <description>Uniquely identifies a set of dimensions referenced within the containing SOP Instance. See section C.7.6.17.2 for further explanation.</description>
    </entry>
    <entry group="0020" element="9222" name="Dimension Index Sequence" type="2">
      <description>Identifies the sequence containing the indices used to specify the dimension of the multi-frame object.
Zero or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0020" element="9165" name="&gt;Dimension Index Pointer" type="1">
      <description>Contains the Data Element Tag that is used to identify the Attribute connected with the index. See section C.7.6.17.1 for further explanation.</description>
    </entry>
    <entry group="0020" element="9213" name="&gt;Dimension Index Private Creator" type="1C">
      <description>Identification of the creator of a group of private data elements.
Required if the Dimension Index Pointer (0020,9165) value is the Data Element Tag of a Private Attribute.</description>
    </entry>
    <entry group="0020" element="9167" name="&gt;Functional Group Pointer" type="1C">
      <description>Contains the Data Element Tag of the Functional Group Sequence that contains the Attribute that is referenced by the Dimension Index Pointer (0020,9165).
See section C.7.6.17.1 for further explanation.
Required if the value of the Dimension Index Pointer (0020,9165) is the Data Element Tag of an Attribute that is contained within a Functional Group Sequence.</description>
    </entry>
    <entry group="0020" element="9238" name="&gt;Functional Group Private Creator" type="1C">
      <description>Identification of the creator of a group of private data elements.
Required if the Functional Group Pointer 0020,9167) value is the Data Element Tag of a Private Attribute.</description>
    </entry>
    <entry group="0020" element="9164" name="&gt;Dimension Organization UID" type="1C">
      <description>Uniquely identifies a set of dimensions referenced within the containing SOP Instance. In particular the dimension described by this sequence item is associated with this Dimension Organization UID. See section C.7.6.17.2 for further explanation.
Required if the value of the Dimension Organization Sequence (0020,9221) contains Items</description>
    </entry>
    <entry group="0020" element="9421" name="&gt;Dimension Description Label" type="3">
      <description>Free text description that explains the meaning of the dimension.</description>
    </entry>
  </module>
  <module ref="C.7.6.18.1" table="C.7.6.18-1" name="Cardiac Synchronization Module Attributes">
    <entry group="0018" element="9037" name="Cardiac Synchronization Technique" type="1C">
      <description>Defines if a cardiac synchronization technique was applied during or after the acquisition.
Enumerated Values:
NONE
REALTIME = total time for the acquisition is shorter than cardiac cycle, no gating is applied
PROSPECTIVE =
certain thresholds have been set for a gating window that defines the acceptance of measurement data during the acquisition
RETROSPECTIVE =
certain thresholds have been set for a gating window that defines the acceptance of measurement data after the acquisition
PACED = there is a constant RR interval (e.g., Pacemaker), which makes thresholding not required
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9085" name="Cardiac Signal Source" type="1C">
      <description>Cardiac Signal Source.
Defined Terms:
ECG = electrocardiogram
VCG = vector cardiogram
PP = peripheral pulse
MR = magnetic resonance, i.e. M-mode or cardiac navigator
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Cardiac Synchronization Technique (0018,9037) equals other than NONE.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Cardiac Synchronization Technique (0018,9037) equals other than NONE.</description>
    </entry>
    <entry group="0018" element="9070" name="Cardiac RR Interval Specified" type="1C">
      <description>R-R interval in ms measured prior to or during the scan.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Cardiac Synchronization Technique (0018,9037) equals other than NONE.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Cardiac Synchronization Technique (0018,9037) equals other than NONE.
Note: The Heart Rate (0018,1088) attribute is not used in this Module, since its value can be derived as 1/ Cardiac RR Interval Specified (0018,9070).</description>
    </entry>
    <entry group="0018" element="9169" name="Cardiac Beat Rejection Technique" type="1C">
      <description>Cardiac arrhythmia rejection technique.
Defined Terms:
NONE
RR_INTERVAL =
rejection based on deviation from average RR interval
QRS_LOOP =
rejection based on deviation from regular QRS loop
PVC =
rejection based on PVC criteria
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Cardiac Synchronization Technique (0018,9037) equals PROSPECTIVE or RETROSPECTIVE.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Cardiac Synchronization Technique (0018,9037) equals PROSPECTIVE or RETROSPECTIVE.</description>
    </entry>
    <entry group="0018" element="1081" name="Low R-R Value" type="2C">
      <description>R-R interval low limit for beat rejection, in ms.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Cardiac Synchronization Technique (0018,9037) equals PROSPECTIVE or RETROSPECTIVE.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Cardiac Synchronization Technique (0018,9037) equals PROSPECTIVE or RETROSPECTIVE.</description>
    </entry>
    <entry group="0018" element="1082" name="High R-R Value" type="2C">
      <description>R-R interval high limit for beat rejection, in ms.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Cardiac Synchronization Technique (0018,9037) equals PROSPECTIVE or RETROSPECTIVE.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Cardiac Synchronization Technique (0018,9037) equals PROSPECTIVE or RETROSPECTIVE.</description>
    </entry>
    <entry group="0018" element="1083" name="Intervals Acquired" type="2C">
      <description>Number of R-R intervals acquired and used to create the image (not including the intervals rejected).
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Cardiac Synchronization Technique (0018,9037) equals other than NONE.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Cardiac Synchronization Technique (0018,9037) equals other than NONE.</description>
    </entry>
    <entry group="0018" element="1084" name="Intervals Rejected" type="2C">
      <description>Number of R-R intervals rejected.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Cardiac Synchronization Technique (0018,9037) equals other than NONE.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Cardiac Synchronization Technique (0018,9037) equals other than NONE.</description>
    </entry>
    <entry group="0018" element="1086" name="Skip Beats" type="3">
      <description>Number of beats prescribed to be skipped after each detected arrhythmia.</description>
    </entry>
    <entry group="0018" element="1064" name="Cardiac Framing Type" type="1C">
      <description>Description of type of framing performed. Defined Terms:
FORW = time forward from trigger
BACK = time back before trigger
PCNT = percentage of R-R forward from trigger
See C.7.6.18.1.1.1.
Required if type of framing is not time forward from trigger, may be present otherwise.</description>
      <section ref="C.7.6.18.1.1.1" name="">Cardiac Framing Type (0018,1064) is the mechanism used to select the data acquired to construct the frames within a specified cardiac timing interval.C.7.6.18.2  Respiratory Synchronization Module
Table C7.6.18-2 specifies the attributes of the Respiratory Synchronization Module.
Table C.7.6.18-2
RESPIRATORY SYNCHRONIZATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Respiratory Motion Compensation Technique" meaning="(0018,9170)"/><term value="Respiratory Signal Source" meaning="(0018,9171)"/><term value="Respiratory Trigger Delay Threshold" meaning="(0020,9256)"/><term value="Respiratory Trigger Type" meaning="(0020,9250)"/></unrecognized-rows>
         </section>
    </entry>
  </module>
  <module ref="C.7.6.18.2" table="C.7.6.18-2" name="Respiratory Synchronization Module Attributes">
    <entry group="0018" element="9170" name="Respiratory Motion Compensation Technique" type="1C">
      <description>Applied technique to reduce respiratory motion artifacts.
Defined Terms:
NONE
BREATH_HOLD
REALTIME =
image acquisition shorter than respiratory cycle
GATING = Prospective gating
TRACKING =
prospective through-plane or in-plane motion tracking
PHASE_ORDERING =
prospective phase ordering
PHASE_RESCANNING =
prospective techniques, such as real-time averaging, diminishing variance and motion adaptive gating
RETROSPECTIVE =
retrospective gating
CORRECTION =
retrospective image correction
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9171" name="Respiratory Signal Source" type="1C">
      <description>Signal source from which respiratory motion is derived.
Defined Terms:
NONE
BELT = includes various devices that detect or track expansion of the chest
NASAL_PROBE
CO2_SENSOR
NAVIGATOR = MR navigator and organ edge detection
MR_PHASE = phase (of center k-space line)
ECG = baseline demodulation of the ECG
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Respiratory Motion Compensation Technique (0018,9170) equals other than NONE.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Respiratory Motion Compensation Technique (0018,9170 equals other than NONE.</description>
    </entry>
    <entry group="0020" element="9256" name="Respiratory Trigger Delay Threshold" type="1C">
      <description>Respiratory trigger threshold in percent of the chest expansion for the frame relative to the last Respiratory-Peak. See C.7.6.16.2.17.1 for further explanation.
Required if Respiratory Motion Compensation Technique (0018,9170) equals other than NONE, REALTIME or BREATH_HOLD and if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
      <section ref="C.7.6.16.2.17.1" name="">For time based respiratory gating, the Nominal Respiratory Trigger Delay Time (0020,9255) is the prescribed trigger delay time in ms from the previous Respiratory-peak to the value of the Frame Reference DateTime (0018,9151). When frames are acquired with prospective gating, that is, the data acquisition actually begins in response to a timed delay from the Respiratory trigger, it may be that Actual Respiratory Trigger Delay Time (0020,9257) and the Nominal Respiratory Trigger Delay Time (0020,9255) have the same value.
However, when frames are the result of retrospective gating, that is, the data is continuously acquired and then later compared with a simultaneously acquired respiratory waveform and fitted into bins corresponding to nominal phases of the respiratory cycle, then Nominal Respiratory Trigger Delay Time (0020,9255) and the Actual Respiratory Trigger Delay Time (0020,9257) may have different values.
Figure C.7.6.16-9a and C.7.6.16-9b depict the usage.


Figure C.7.6.16-9a
Respiratory Timing Tags


Figure C.7.6.16-9b
Relationship of Respiratory Amplitude Attributes

</section>
    </entry>
    <entry group="0020" element="9250" name="Respiratory Trigger Type" type="1C">
      <description>Characteristic of the respiratory signal used to the define the respiratory triggering.
Defined Terms:
TIME
AMPLITUDE
BOTH
Required if the value is not TIME, may be present otherwise.</description>
    </entry>
  </module>
  <module ref="C.7.6.18.3" table="C.7.6.18-3" name="Bulk Motion Synchronization Module Attributes">
    <entry group="0018" element="9172" name="Bulk Motion Compensation Technique" type="1C">
      <description>Applied technique to reduce bulk or other physiology motion artifacts.
Defined Terms:
NONE
REALTIME = image acquisition shorter than motion cycle
GATING = prospective gating
TRACKING = prospective through and/or in‑plane motion tracking
RETROSPECTIVE =
retrospective gating
CORRECTION = retrospective image correction
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9173" name="Bulk Motion Signal Source" type="1C">
      <description>Signal source to measure motion.
Defined Terms:
JOINT = joint motion detection
NAVIGATOR = MR navigator and organ edge detection
MR_PHASE = phase (of center k‑space line)
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Bulk Motion Compensation Technique (0018,9172) equals other than NONE.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Bulk Motion Compensation Technique (0018,9172) equals other than NONE.</description>
    </entry>
  </module>
  <module ref="C.7.6.19" table="C.7.6.19-1" name="Supplemental Palette Color Table Lookup Module Attributes">
    <entry group="0028" element="1101" name="Red Palette Color Lookup Table Descriptor" type="1">
      <description>Specifies the format of the Red Palette Color Lookup Table Data (0028,1201). See C.7.6.3.1.5 for further explanation.</description>
      <section ref="C.7.6.3.1.5" name="">The three values of Palette Color Lookup Table Descriptor (0028,1101-1103) describe the format of the Lookup Table Data in the corresponding Data Element (0028,1201-1203) or (0028,1221-1223).
The first value is the number of entries in the lookup table. When the number of table entries is equal to 216 then this value shall be 0. The first value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the Lookup Table Data. All image pixel values less than the first value mapped are also mapped to the first entry in the Lookup Table Data if the Photometric Interpretation is PALETTE COLOR.
Note:  In the case of the Supplemental Palette Color LUT, the stored pixel values less than the second descriptor value are grayscale values.

An image pixel value one greater than the first value mapped is mapped to the second entry in the Lookup Table Data. Subsequent image pixel values are mapped to the subsequent entries in the Lookup Table Data up to an image pixel value equal to number of entries + first value mapped – 1, which is mapped to the last entry in the Lookup Table Data. Image pixel values greater than or equal to number of entries + first value mapped are also mapped to the last entry in the Lookup Table Data. The second value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The third value specifies the number of bits for each entry in the Lookup Table Data. It shall take the value of 8 or 16. The LUT Data shall be stored in a format equivalent to 8 bits allocated when the number of bits for each entry is 8, and 16 bits allocated when the number of bits for each entry is 16, where in both cases the high bit is equal to bits allocated-1. The third value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
Note:  Some implementations have encoded 8 bit entries with 16 bits allocated, padding the high bits; this can be detected by comparing the number of entries specified in the LUT Descriptor with the actual value length of the LUT Data entry. The value length in bytes should equal the number of entries if bits allocated is 8, and be twice as long if bits allocated is 16.

When the Palette Color Lookup Table Descriptor (0028,1101-1103) are used as part of the Palette Color Lookup Table Module or the Supplemental Palette Color Lookup Table Module, the third value shall be equal to 16.
Notes:  1. A value of 16 indicates the Lookup Table Data will range from (0,0,0) minimum intensity to (65535,65535,65535) maximum intensity.
  2. Since the Palette Color Lookup Table Descriptor (0028,1101-1103) Attributes are multi-valued, in an Explicit VR Transfer Syntax, only one value representation (US or SS) may be specified, even though the first and third values are always by definition interpreted as unsigned. The explicit VR actually used is dictated by the VR needed to represent the second value, which will be consistent with Pixel Representation (0028,0103).

</section>
    </entry>
    <entry group="0028" element="1102" name="Green Palette Color Lookup Table Descriptor" type="1">
      <description>Specifies the format of the Green Palette Color Lookup Table Data (0028,1202). See C.7.6.3.1.5 for further explanation.</description>
      <section ref="C.7.6.3.1.5" name="">The three values of Palette Color Lookup Table Descriptor (0028,1101-1103) describe the format of the Lookup Table Data in the corresponding Data Element (0028,1201-1203) or (0028,1221-1223).
The first value is the number of entries in the lookup table. When the number of table entries is equal to 216 then this value shall be 0. The first value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the Lookup Table Data. All image pixel values less than the first value mapped are also mapped to the first entry in the Lookup Table Data if the Photometric Interpretation is PALETTE COLOR.
Note:  In the case of the Supplemental Palette Color LUT, the stored pixel values less than the second descriptor value are grayscale values.

An image pixel value one greater than the first value mapped is mapped to the second entry in the Lookup Table Data. Subsequent image pixel values are mapped to the subsequent entries in the Lookup Table Data up to an image pixel value equal to number of entries + first value mapped – 1, which is mapped to the last entry in the Lookup Table Data. Image pixel values greater than or equal to number of entries + first value mapped are also mapped to the last entry in the Lookup Table Data. The second value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The third value specifies the number of bits for each entry in the Lookup Table Data. It shall take the value of 8 or 16. The LUT Data shall be stored in a format equivalent to 8 bits allocated when the number of bits for each entry is 8, and 16 bits allocated when the number of bits for each entry is 16, where in both cases the high bit is equal to bits allocated-1. The third value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
Note:  Some implementations have encoded 8 bit entries with 16 bits allocated, padding the high bits; this can be detected by comparing the number of entries specified in the LUT Descriptor with the actual value length of the LUT Data entry. The value length in bytes should equal the number of entries if bits allocated is 8, and be twice as long if bits allocated is 16.

When the Palette Color Lookup Table Descriptor (0028,1101-1103) are used as part of the Palette Color Lookup Table Module or the Supplemental Palette Color Lookup Table Module, the third value shall be equal to 16.
Notes:  1. A value of 16 indicates the Lookup Table Data will range from (0,0,0) minimum intensity to (65535,65535,65535) maximum intensity.
  2. Since the Palette Color Lookup Table Descriptor (0028,1101-1103) Attributes are multi-valued, in an Explicit VR Transfer Syntax, only one value representation (US or SS) may be specified, even though the first and third values are always by definition interpreted as unsigned. The explicit VR actually used is dictated by the VR needed to represent the second value, which will be consistent with Pixel Representation (0028,0103).

</section>
    </entry>
    <entry group="0028" element="1103" name="Blue Palette Color Lookup Table Descriptor" type="1">
      <description>Specifies the format of the Blue Palette Color Lookup table Data (0028,1203). See C.7.6.3.1.5 for further explanation.</description>
      <section ref="C.7.6.3.1.5" name="">The three values of Palette Color Lookup Table Descriptor (0028,1101-1103) describe the format of the Lookup Table Data in the corresponding Data Element (0028,1201-1203) or (0028,1221-1223).
The first value is the number of entries in the lookup table. When the number of table entries is equal to 216 then this value shall be 0. The first value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the Lookup Table Data. All image pixel values less than the first value mapped are also mapped to the first entry in the Lookup Table Data if the Photometric Interpretation is PALETTE COLOR.
Note:  In the case of the Supplemental Palette Color LUT, the stored pixel values less than the second descriptor value are grayscale values.

An image pixel value one greater than the first value mapped is mapped to the second entry in the Lookup Table Data. Subsequent image pixel values are mapped to the subsequent entries in the Lookup Table Data up to an image pixel value equal to number of entries + first value mapped – 1, which is mapped to the last entry in the Lookup Table Data. Image pixel values greater than or equal to number of entries + first value mapped are also mapped to the last entry in the Lookup Table Data. The second value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The third value specifies the number of bits for each entry in the Lookup Table Data. It shall take the value of 8 or 16. The LUT Data shall be stored in a format equivalent to 8 bits allocated when the number of bits for each entry is 8, and 16 bits allocated when the number of bits for each entry is 16, where in both cases the high bit is equal to bits allocated-1. The third value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
Note:  Some implementations have encoded 8 bit entries with 16 bits allocated, padding the high bits; this can be detected by comparing the number of entries specified in the LUT Descriptor with the actual value length of the LUT Data entry. The value length in bytes should equal the number of entries if bits allocated is 8, and be twice as long if bits allocated is 16.

When the Palette Color Lookup Table Descriptor (0028,1101-1103) are used as part of the Palette Color Lookup Table Module or the Supplemental Palette Color Lookup Table Module, the third value shall be equal to 16.
Notes:  1. A value of 16 indicates the Lookup Table Data will range from (0,0,0) minimum intensity to (65535,65535,65535) maximum intensity.
  2. Since the Palette Color Lookup Table Descriptor (0028,1101-1103) Attributes are multi-valued, in an Explicit VR Transfer Syntax, only one value representation (US or SS) may be specified, even though the first and third values are always by definition interpreted as unsigned. The explicit VR actually used is dictated by the VR needed to represent the second value, which will be consistent with Pixel Representation (0028,0103).

</section>
    </entry>
    <entry group="0028" element="1201" name="Red Palette Color Lookup Table Data" type="1">
      <description>Red Palette Color Lookup Table Data. See C.7.6.3.1.6 for further explanation.</description>
      <section ref="C.7.6.3.1.6" name="">Palette Color Lookup Table Data (0028,1201-1203) contain the lookup table data corresponding to the Lookup Table Descriptor (0028,1101-1103).
Palette color values must always be scaled across the full range of available intensities. This is indicated by the fact that there are no bits stored and high bit values for palette color data.
Note:  For example, if there are 16 bits per entry specified and only 8 bits of value are truly used then the 8 bit intensities from 0 to 255 must be scaled to the corresponding 16 bit intensities from 0 to 65535. To do this for 8 bit values, simply replicate the value in both the most and least significant bytes.

These lookup tables shall be used only when there is a single sample per pixel (single image plane) in the image.
These lookup tables are required when the value of Photometric Interpretation (0028,0004) is Palette Color. The semantics of these lookup tables is not defined otherwise.
</section>
    </entry>
    <entry group="0028" element="1202" name="Green Palette Color Lookup Table Data" type="1">
      <description>Green Palette Color Lookup Table Data. See C.7.6.3.1.6 for further explanation.</description>
      <section ref="C.7.6.3.1.6" name="">Palette Color Lookup Table Data (0028,1201-1203) contain the lookup table data corresponding to the Lookup Table Descriptor (0028,1101-1103).
Palette color values must always be scaled across the full range of available intensities. This is indicated by the fact that there are no bits stored and high bit values for palette color data.
Note:  For example, if there are 16 bits per entry specified and only 8 bits of value are truly used then the 8 bit intensities from 0 to 255 must be scaled to the corresponding 16 bit intensities from 0 to 65535. To do this for 8 bit values, simply replicate the value in both the most and least significant bytes.

These lookup tables shall be used only when there is a single sample per pixel (single image plane) in the image.
These lookup tables are required when the value of Photometric Interpretation (0028,0004) is Palette Color. The semantics of these lookup tables is not defined otherwise.
</section>
    </entry>
    <entry group="0028" element="1203" name="Blue Palette Color Lookup Table Data" type="1">
      <description>Blue Palette Color Lookup Table Data. See C.7.6.3.1.6 for further explanation.</description>
      <section ref="C.7.6.3.1.6" name="">Palette Color Lookup Table Data (0028,1201-1203) contain the lookup table data corresponding to the Lookup Table Descriptor (0028,1101-1103).
Palette color values must always be scaled across the full range of available intensities. This is indicated by the fact that there are no bits stored and high bit values for palette color data.
Note:  For example, if there are 16 bits per entry specified and only 8 bits of value are truly used then the 8 bit intensities from 0 to 255 must be scaled to the corresponding 16 bit intensities from 0 to 65535. To do this for 8 bit values, simply replicate the value in both the most and least significant bytes.

These lookup tables shall be used only when there is a single sample per pixel (single image plane) in the image.
These lookup tables are required when the value of Photometric Interpretation (0028,0004) is Palette Color. The semantics of these lookup tables is not defined otherwise.
</section>
    </entry>
  </module>
  <module ref="C.7.6.20" table="C.7.6.20-1" name="Patient Orientation Module Attributes">
    <include ref="Include 'Patient Orientation Macro' Table 10-15"/>
  </module>
  <module ref="C.7.6.21" table="C.7.6.21-1" name="Image – Equipment Coordinate Relationship Module Attributes">
    <entry group="0028" element="9520" name="Image to Equipment Mapping Matrix" type="1">
      <description>A 4x4 homogeneous transformation matrix that maps patient coordinate space of the reconstructed image to the equipment defined original coordinate space. Matrix elements shall be listed in row-major order. See C.7.6.21.1.</description>
      <section ref="C.7.6.21.1" name="">The Image to Equipment Mapping Matrix (0028,9520) is used to describe the relationship between the Patient oriented coordinate system and a modality specific equipment coordinate system. This mapping can only be used with systems that have a well-defined equipment coordinate system (such as XA, etc.).
The Image to Equipment Mapping Matrix AMB describes how to transform a point (Bx,By,Bz) with respect to the Patient coordinate system into (Ax,Ay,Az) with respect to the equipment coordinate system according to the equation below.

       size 12{ left [ matrix {
"" lSup { size 8{A} } x {} ##
"" lSup { size 8{A} } y {} ##
"" lSup { size 8{A} } z {} ##
1
}  right ]= left [ matrix {
M rSub { size 8{"11"} }  {} # M rSub { size 8{"12"} }  {} # M rSub { size 8{"13"} }  {} # T rSub { size 8{x} }  {} ##
M rSub { size 8{"21"} }  {} # M rSub { size 8{"22"} }  {} # M rSub { size 8{"23"} }  {} # T rSub { size 8{y} }  {} ##
M rSub { size 8{"31"} }  {} # M rSub { size 8{"32"} }  {} # M rSub { size 8{"33"} }  {} # T rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
"" lSup { size 8{B} } x {} ##
"" lSup { size 8{B} } y {} ##
"" lSup { size 8{B} } z {} ##
1
}  right ]} {}


The Image to Equipment Mapping Matrix is a rigid transformation that involves only translations and rotations. Mathematically, the matrix shall be orthonormal and can describe six degrees of freedom: three translations, and three rotations.
Note:  Both the Patient Coordinate System and the Equipment Coordinate System are expressed in millimeters.

</section>
    </entry>
    <entry group="0028" element="9537" name="Equipment Coordinate System Identification" type="1">
      <description>Identification of the type of equipment coordinate system in which the projection images were acquired. See C.7.6.21.2.
Defined Terms:
ISOCENTER</description>
      <section ref="C.7.6.21.2" name="">The Equipment Coordinate System Identification (0028,9537) identifies the Reference Coordinate System to which the Image to Equipment Mapping Matrix (0028,9520) is related.
The Defined Term ISOCENTER refers to a coordinate reference system where the origin corresponds with the center of rotation of the projections.
Note:  For X-Ray 3D Angiographic Images created from SOP Instances of the Enhanced XA SOP Class (1.2.840.10008.5.1.4.1.1.12.1.1) the isocenter coordinate system is used to describe the positioning of the table and positioner (see C.8.19.6.13), and will use only the Defined Term ISOCENTER.

</section>
    </entry>
  </module>
  <module ref="C.7.9" table="C.7-22" name="Palette Color Lookup Module">
    <entry group="0028" element="1101" name="Red Palette Color Lookup Table Descriptor" type="1">
      <description>Specifies the format of the Red Palette Color Lookup Table Data (0028,1201). See C.7.6.3.1.5 for further explanation.</description>
      <section ref="C.7.6.3.1.5" name="">The three values of Palette Color Lookup Table Descriptor (0028,1101-1103) describe the format of the Lookup Table Data in the corresponding Data Element (0028,1201-1203) or (0028,1221-1223).
The first value is the number of entries in the lookup table. When the number of table entries is equal to 216 then this value shall be 0. The first value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the Lookup Table Data. All image pixel values less than the first value mapped are also mapped to the first entry in the Lookup Table Data if the Photometric Interpretation is PALETTE COLOR.
Note:  In the case of the Supplemental Palette Color LUT, the stored pixel values less than the second descriptor value are grayscale values.

An image pixel value one greater than the first value mapped is mapped to the second entry in the Lookup Table Data. Subsequent image pixel values are mapped to the subsequent entries in the Lookup Table Data up to an image pixel value equal to number of entries + first value mapped – 1, which is mapped to the last entry in the Lookup Table Data. Image pixel values greater than or equal to number of entries + first value mapped are also mapped to the last entry in the Lookup Table Data. The second value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The third value specifies the number of bits for each entry in the Lookup Table Data. It shall take the value of 8 or 16. The LUT Data shall be stored in a format equivalent to 8 bits allocated when the number of bits for each entry is 8, and 16 bits allocated when the number of bits for each entry is 16, where in both cases the high bit is equal to bits allocated-1. The third value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
Note:  Some implementations have encoded 8 bit entries with 16 bits allocated, padding the high bits; this can be detected by comparing the number of entries specified in the LUT Descriptor with the actual value length of the LUT Data entry. The value length in bytes should equal the number of entries if bits allocated is 8, and be twice as long if bits allocated is 16.

When the Palette Color Lookup Table Descriptor (0028,1101-1103) are used as part of the Palette Color Lookup Table Module or the Supplemental Palette Color Lookup Table Module, the third value shall be equal to 16.
Notes:  1. A value of 16 indicates the Lookup Table Data will range from (0,0,0) minimum intensity to (65535,65535,65535) maximum intensity.
  2. Since the Palette Color Lookup Table Descriptor (0028,1101-1103) Attributes are multi-valued, in an Explicit VR Transfer Syntax, only one value representation (US or SS) may be specified, even though the first and third values are always by definition interpreted as unsigned. The explicit VR actually used is dictated by the VR needed to represent the second value, which will be consistent with Pixel Representation (0028,0103).

</section>
    </entry>
    <entry group="0028" element="1102" name="Green Palette Color Lookup Table Descriptor" type="1">
      <description>Specifies the format of the Green Palette Color Lookup Table Data (0028,1202). See C.7.6.3.1.5 for further explanation.</description>
      <section ref="C.7.6.3.1.5" name="">The three values of Palette Color Lookup Table Descriptor (0028,1101-1103) describe the format of the Lookup Table Data in the corresponding Data Element (0028,1201-1203) or (0028,1221-1223).
The first value is the number of entries in the lookup table. When the number of table entries is equal to 216 then this value shall be 0. The first value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the Lookup Table Data. All image pixel values less than the first value mapped are also mapped to the first entry in the Lookup Table Data if the Photometric Interpretation is PALETTE COLOR.
Note:  In the case of the Supplemental Palette Color LUT, the stored pixel values less than the second descriptor value are grayscale values.

An image pixel value one greater than the first value mapped is mapped to the second entry in the Lookup Table Data. Subsequent image pixel values are mapped to the subsequent entries in the Lookup Table Data up to an image pixel value equal to number of entries + first value mapped – 1, which is mapped to the last entry in the Lookup Table Data. Image pixel values greater than or equal to number of entries + first value mapped are also mapped to the last entry in the Lookup Table Data. The second value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The third value specifies the number of bits for each entry in the Lookup Table Data. It shall take the value of 8 or 16. The LUT Data shall be stored in a format equivalent to 8 bits allocated when the number of bits for each entry is 8, and 16 bits allocated when the number of bits for each entry is 16, where in both cases the high bit is equal to bits allocated-1. The third value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
Note:  Some implementations have encoded 8 bit entries with 16 bits allocated, padding the high bits; this can be detected by comparing the number of entries specified in the LUT Descriptor with the actual value length of the LUT Data entry. The value length in bytes should equal the number of entries if bits allocated is 8, and be twice as long if bits allocated is 16.

When the Palette Color Lookup Table Descriptor (0028,1101-1103) are used as part of the Palette Color Lookup Table Module or the Supplemental Palette Color Lookup Table Module, the third value shall be equal to 16.
Notes:  1. A value of 16 indicates the Lookup Table Data will range from (0,0,0) minimum intensity to (65535,65535,65535) maximum intensity.
  2. Since the Palette Color Lookup Table Descriptor (0028,1101-1103) Attributes are multi-valued, in an Explicit VR Transfer Syntax, only one value representation (US or SS) may be specified, even though the first and third values are always by definition interpreted as unsigned. The explicit VR actually used is dictated by the VR needed to represent the second value, which will be consistent with Pixel Representation (0028,0103).

</section>
    </entry>
    <entry group="0028" element="1103" name="Blue Palette Color Lookup Table Descriptor" type="1">
      <description>Specifies the format of the Blue Palette Color Lookup table Data (0028,1203). See C.7.6.3.1.5 for further explanation.</description>
      <section ref="C.7.6.3.1.5" name="">The three values of Palette Color Lookup Table Descriptor (0028,1101-1103) describe the format of the Lookup Table Data in the corresponding Data Element (0028,1201-1203) or (0028,1221-1223).
The first value is the number of entries in the lookup table. When the number of table entries is equal to 216 then this value shall be 0. The first value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the Lookup Table Data. All image pixel values less than the first value mapped are also mapped to the first entry in the Lookup Table Data if the Photometric Interpretation is PALETTE COLOR.
Note:  In the case of the Supplemental Palette Color LUT, the stored pixel values less than the second descriptor value are grayscale values.

An image pixel value one greater than the first value mapped is mapped to the second entry in the Lookup Table Data. Subsequent image pixel values are mapped to the subsequent entries in the Lookup Table Data up to an image pixel value equal to number of entries + first value mapped – 1, which is mapped to the last entry in the Lookup Table Data. Image pixel values greater than or equal to number of entries + first value mapped are also mapped to the last entry in the Lookup Table Data. The second value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
The third value specifies the number of bits for each entry in the Lookup Table Data. It shall take the value of 8 or 16. The LUT Data shall be stored in a format equivalent to 8 bits allocated when the number of bits for each entry is 8, and 16 bits allocated when the number of bits for each entry is 16, where in both cases the high bit is equal to bits allocated-1. The third value shall be identical for each of the Red, Green and Blue Palette Color Lookup Table Descriptors.
Note:  Some implementations have encoded 8 bit entries with 16 bits allocated, padding the high bits; this can be detected by comparing the number of entries specified in the LUT Descriptor with the actual value length of the LUT Data entry. The value length in bytes should equal the number of entries if bits allocated is 8, and be twice as long if bits allocated is 16.

When the Palette Color Lookup Table Descriptor (0028,1101-1103) are used as part of the Palette Color Lookup Table Module or the Supplemental Palette Color Lookup Table Module, the third value shall be equal to 16.
Notes:  1. A value of 16 indicates the Lookup Table Data will range from (0,0,0) minimum intensity to (65535,65535,65535) maximum intensity.
  2. Since the Palette Color Lookup Table Descriptor (0028,1101-1103) Attributes are multi-valued, in an Explicit VR Transfer Syntax, only one value representation (US or SS) may be specified, even though the first and third values are always by definition interpreted as unsigned. The explicit VR actually used is dictated by the VR needed to represent the second value, which will be consistent with Pixel Representation (0028,0103).

</section>
    </entry>
    <entry group="0028" element="1199" name="Palette Color Lookup Table UID" type="3">
      <description>Palette Color Lookup Table UID. See C.7.9.1 for further explanation.</description>
      <section ref="C.7.9.1" name="">This data element uniquely identifies a palette color lookup table set (red, green, blue).
Note:  This can be used to avoid reloading a palette if a system already has that palette loaded without examining all the data entries in the palette.

</section>
    </entry>
    <entry group="0028" element="1201" name="Red Palette Color Lookup Table Data" type="1C">
      <description>Red Palette Color Lookup Table Data. Required if segmented data is NOT used in an Image IOD, or if the IOD is a Presentation State IOD. See C.7.6.3.1.6 for further explanation.</description>
      <section ref="C.7.6.3.1.6" name="">Palette Color Lookup Table Data (0028,1201-1203) contain the lookup table data corresponding to the Lookup Table Descriptor (0028,1101-1103).
Palette color values must always be scaled across the full range of available intensities. This is indicated by the fact that there are no bits stored and high bit values for palette color data.
Note:  For example, if there are 16 bits per entry specified and only 8 bits of value are truly used then the 8 bit intensities from 0 to 255 must be scaled to the corresponding 16 bit intensities from 0 to 65535. To do this for 8 bit values, simply replicate the value in both the most and least significant bytes.

These lookup tables shall be used only when there is a single sample per pixel (single image plane) in the image.
These lookup tables are required when the value of Photometric Interpretation (0028,0004) is Palette Color. The semantics of these lookup tables is not defined otherwise.
</section>
    </entry>
    <entry group="0028" element="1202" name="Green Palette Color Lookup Table Data" type="1C">
      <description>Green Palette Color Lookup Table Data. Required if segmented data is NOT used in an Image IOD, or if the IOD is a Presentation State IOD. See C.7.6.3.1.6 for further explanation.</description>
      <section ref="C.7.6.3.1.6" name="">Palette Color Lookup Table Data (0028,1201-1203) contain the lookup table data corresponding to the Lookup Table Descriptor (0028,1101-1103).
Palette color values must always be scaled across the full range of available intensities. This is indicated by the fact that there are no bits stored and high bit values for palette color data.
Note:  For example, if there are 16 bits per entry specified and only 8 bits of value are truly used then the 8 bit intensities from 0 to 255 must be scaled to the corresponding 16 bit intensities from 0 to 65535. To do this for 8 bit values, simply replicate the value in both the most and least significant bytes.

These lookup tables shall be used only when there is a single sample per pixel (single image plane) in the image.
These lookup tables are required when the value of Photometric Interpretation (0028,0004) is Palette Color. The semantics of these lookup tables is not defined otherwise.
</section>
    </entry>
    <entry group="0028" element="1203" name="Blue Palette Color Lookup Table Data" type="1C">
      <description>Blue Palette Color Lookup Table Data. Required if segmented data is NOT used in an Image IOD, or if the IOD is a Presentation State IOD. See C.7.6.3.1.6 for further explanation.</description>
      <section ref="C.7.6.3.1.6" name="">Palette Color Lookup Table Data (0028,1201-1203) contain the lookup table data corresponding to the Lookup Table Descriptor (0028,1101-1103).
Palette color values must always be scaled across the full range of available intensities. This is indicated by the fact that there are no bits stored and high bit values for palette color data.
Note:  For example, if there are 16 bits per entry specified and only 8 bits of value are truly used then the 8 bit intensities from 0 to 255 must be scaled to the corresponding 16 bit intensities from 0 to 65535. To do this for 8 bit values, simply replicate the value in both the most and least significant bytes.

These lookup tables shall be used only when there is a single sample per pixel (single image plane) in the image.
These lookup tables are required when the value of Photometric Interpretation (0028,0004) is Palette Color. The semantics of these lookup tables is not defined otherwise.
</section>
    </entry>
    <entry group="0028" element="1221" name="Segmented Red Palette Color Lookup Table Data" type="1C">
      <description>Segmented Red Palette Color Lookup Table Data. Required segmented data is used in an Image IOD; shall not be present in a Presentation State IOD. See C.7.9.2 for further explanation.</description>
      <section ref="C.7.9.2" name="">The Segmented Palette Color Lookup Table Data (0028,1221-1223) is stored as a series of segments, see Table C.7-23. When the segments are expanded into the actual lookup table data, it shall have the number of table entries specified by the first value of the Palette Color Lookup Table Descriptors (0028,1101-1103), Number of Table Entries.
These lookup tables shall be used only when segmented lookup table data use is desriable and there is a single sample per pixel (single image plane) in the image.
Table C.7-23
COMPRESSED PALETTE COLOR LOOKUP TABLE DATA
<unrecognized-rows><term value="Segment 0"/><term value="Segment 1"/><term value="..."/><term value="Segment n"/></unrecognized-rows>
There are currently three types of segments: discrete, linear, and indirect. The segments type is identified by the opcodes in Table C.7-24:
Table C.7-24
SEGMENT TYPES
<unrecognized-rows><term value="Opcode" meaning="Segment type"/><term value="0" meaning="Discrete"/><term value="1" meaning="Linear"/><term value="2" meaning="Indirect"/><term value="3 &amp; above" meaning="reserved"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="1222" name="Segmented Green Palette Color Lookup Table Data" type="1C">
      <description>Segmented Green Palette Color Lookup Table Data. Required if segmented data is used in an Image IOD; shall not be present in a Presentation State IOD. See C.7.9.2 for further explanation.</description>
      <section ref="C.7.9.2" name="">The Segmented Palette Color Lookup Table Data (0028,1221-1223) is stored as a series of segments, see Table C.7-23. When the segments are expanded into the actual lookup table data, it shall have the number of table entries specified by the first value of the Palette Color Lookup Table Descriptors (0028,1101-1103), Number of Table Entries.
These lookup tables shall be used only when segmented lookup table data use is desriable and there is a single sample per pixel (single image plane) in the image.
Table C.7-23
COMPRESSED PALETTE COLOR LOOKUP TABLE DATA
<unrecognized-rows><term value="Segment 0"/><term value="Segment 1"/><term value="..."/><term value="Segment n"/></unrecognized-rows>
There are currently three types of segments: discrete, linear, and indirect. The segments type is identified by the opcodes in Table C.7-24:
Table C.7-24
SEGMENT TYPES
<unrecognized-rows><term value="Opcode" meaning="Segment type"/><term value="0" meaning="Discrete"/><term value="1" meaning="Linear"/><term value="2" meaning="Indirect"/><term value="3 &amp; above" meaning="reserved"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="1223" name="Segmented Blue Palette Color Lookup Table Data" type="1C">
      <description>Segmented Blue Palette Color Lookup Table Data. Required if segmented data is used in an Image IOD; shall not be present in a Presentation State IOD. See C.7.9.2 for further explanation.</description>
      <section ref="C.7.9.2" name="">The Segmented Palette Color Lookup Table Data (0028,1221-1223) is stored as a series of segments, see Table C.7-23. When the segments are expanded into the actual lookup table data, it shall have the number of table entries specified by the first value of the Palette Color Lookup Table Descriptors (0028,1101-1103), Number of Table Entries.
These lookup tables shall be used only when segmented lookup table data use is desriable and there is a single sample per pixel (single image plane) in the image.
Table C.7-23
COMPRESSED PALETTE COLOR LOOKUP TABLE DATA
<unrecognized-rows><term value="Segment 0"/><term value="Segment 1"/><term value="..."/><term value="Segment n"/></unrecognized-rows>
There are currently three types of segments: discrete, linear, and indirect. The segments type is identified by the opcodes in Table C.7-24:
Table C.7-24
SEGMENT TYPES
<unrecognized-rows><term value="Opcode" meaning="Segment type"/><term value="0" meaning="Discrete"/><term value="1" meaning="Linear"/><term value="2" meaning="Indirect"/><term value="3 &amp; above" meaning="reserved"/></unrecognized-rows>
         </section>
    </entry>
  </module>
  <module ref="C.8.1.1" table="C.8-1" name="CR Series Module Attributes">
    <entry group="0018" element="0015" name="Body Part Examined" type="2">
      <description>Text description of the part of the body examined. See PS 3.16 Annex on Correspondence of Anatomic Region Codes and Body Part Examined for Defined Terms</description>
    </entry>
    <entry group="0018" element="5101" name="View Position" type="2">
      <description>Radiographic view associated with Patient Position (0018,5100). Defined Terms:
AP = Anterior/Posterior
PA = Posterior/Anterior
LL = Left Lateral
RL = Right Lateral
RLD = Right Lateral Decubitus
LLD = Left Lateral Decubitus
RLO = Right Lateral Oblique
LLO = Left Lateral Oblique</description>
    </entry>
    <entry group="0018" element="1160" name="Filter Type" type="3">
      <description>Label for the type of filter inserted into the x-ray beam</description>
    </entry>
    <entry group="0018" element="1180" name="Collimator/grid Name" type="3">
      <description>Label describing any grid inserted.</description>
    </entry>
    <entry group="0018" element="1190" name="Focal Spot" type="3">
      <description>Size of the focal spot in mm. For devices with variable focal spot or multiple focal spots, small dimension followed by large dimension.</description>
    </entry>
    <entry group="0018" element="1260" name="Plate Type" type="3">
      <description>Label of the type of storage phosphor plates used in this series</description>
    </entry>
    <entry group="0018" element="1261" name="Phosphor Type" type="3">
      <description>Label of type of phosphor on the plates</description>
    </entry>
  </module>
  <module ref="C.8.1.2" table="C.8-2" name="CR Image Module Attributes">
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data. Shall have one of the following Enumerated Values:
MONOCHROME1
MONOCHROME2</description>
    </entry>
    <entry group="0018" element="0060" name="KVP" type="3">
      <description>Peak kilo voltage output of the x-ray generator used</description>
    </entry>
    <entry group="0018" element="1004" name="Plate ID" type="3">
      <description>The ID or serial number of the sensing plate upon which the image was acquired</description>
    </entry>
    <entry group="0018" element="1110" name="Distance Source to Detector" type="3">
      <description>Distance in mm from source to detector center.
Note: This value is traditionally referred to as Source Image Receptor Distance (SID).</description>
    </entry>
    <entry group="0018" element="1111" name="Distance Source to Patient" type="3">
      <description>Distance in mm from source to isocenter (center of field of view) .
Note: This value is traditionally referred to as Source Object Distance (SOD).</description>
    </entry>
    <entry group="0018" element="1150" name="Exposure Time" type="3">
      <description>Time of x-ray exposure in msec</description>
    </entry>
    <entry group="0018" element="1151" name="X-Ray Tube Current" type="3">
      <description>X-Ray Tube Current in mA.</description>
    </entry>
    <entry group="0018" element="1152" name="Exposure" type="3">
      <description>The exposure expressed in mAs, for example calculated from Exposure Time and X-Ray Tube Current.</description>
    </entry>
    <entry group="0018" element="1153" name="Exposure in µAs" type="3">
      <description>The exposure expressed in µAs, for example calculated from Exposure Time and X-Ray Tube Current.</description>
    </entry>
    <entry group="0018" element="1164" name="Imager Pixel Spacing" type="3">
      <description>Physical distance measured at the front plane of the Image Receptor housing between the center of each pixel. Specified by a numeric pair - row spacing value (delimiter) column spacing value - in mm.
In the case of CR, the front plane is defined to be the external surface of the CR plate closest to the patient and radiation source.</description>
    </entry>
    <include ref="Include Basic Pixel Spacing Calibration Macro (Table 10-10)"/>
    <entry group="0018" element="1170" name="Generator Power" type="3">
      <description>Power in kW to the x-ray generator.</description>
    </entry>
    <entry group="0018" element="1400" name="Acquisition Device Processing Description" type="3">
      <description>Describes device-specific processing associated with the image (e.g. Organ Description)</description>
    </entry>
    <entry group="0018" element="1401" name="Acquisition Device Processing Code" type="3">
      <description>Code representing the device-specific processing associated with the image (e.g. CR Organ Filtering code)</description>
    </entry>
    <entry group="0018" element="1402" name="Cassette Orientation" type="3">
      <description>Orientation of cassette, used to properly position the image for display.
Enumerated Values:
LANDSCAPE
PORTRAIT</description>
    </entry>
    <entry group="0018" element="1403" name="Cassette Size" type="3">
      <description>Size of cassette. Defined Terms:
18CMX24CM
8INX10IN
24CMX30CM
10INX12IN
30CMX35CM
30CMX40CM
11INX14IN
35CMX35CM
14INX14IN
35CMX43CM
14INX17IN</description>
    </entry>
    <entry group="0018" element="1404" name="Exposures on Plate" type="3">
      <description>Total number of x-ray exposures that have been made on the plate identified in Plate ID (0018,1004)</description>
    </entry>
    <entry group="0018" element="1405" name="Relative X-Ray Exposure" type="3">
      <description>Relative x-ray exposure on the plate. Meaning of values is implementation specific. May be used to adjust the dynamic range of the plate digitizer (scanner).</description>
    </entry>
    <entry group="0018" element="6000" name="Sensitivity" type="3">
      <description>Read out sensitivity.</description>
    </entry>
    <include ref="Include 'General Anatomy Optional Macro' Table 10-7" description="Defined Context ID for the Anatomic Region Sequence is 4009."/>
  </module>
  <module ref="C.8.2.1" table="C.8-3" name="CT Image Module Attributes">
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image identification characteristics. See C.8.2.1.1.1 for specialization.</description>
      <section ref="C.8.2.1.1.1" name="">For CT Images, Image Type (0008,0008) is specified to be Type 1 and uses one of the following Defined Terms for Value 3:
AXIAL    identifies a CT Axial Image
LOCALIZER  identifies a CT Localizer Image
Note:  Axial in this context means any cross-sectional image, and includes transverse, coronal, sagittal and oblique images.
</section>
    </entry>
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (planes) in this image. See C.8.2.1.1.2 for specialization.</description>
      <section ref="C.8.2.1.1.2" name="">For CT Images, Samples per Pixel (0028,0002) shall have an Enumerated Value of 1.
</section>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data. See C.8.2.1.1.3 for specialization.</description>
      <section ref="C.8.2.1.1.3" name="">For CT Images, Photometric Interpretation (0028,0004) shall have one of the following Enumerated Values:
  MONOCHROME1
  MONOCHROME2
See C.7.6.3.1.1.2 for definition of these terms.
</section>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated. See C.8.2.1.1.4 for specialization.</description>
      <section ref="C.8.2.1.1.4" name="">For CT Images, Bits Allocated (0028,0100) shall have the Enumerated Value of 16.
</section>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored. See C.8.2.1.1.5 for specialization.</description>
      <section ref="C.8.2.1.1.5" name="">For CT Images, Bits Stored (0028,0101) shall have the Enumerated Values of 12 to 16.
</section>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data. Each sample shall have the same high bit. See C.8.2.1.1.6 for specialization.</description>
      <section ref="C.8.2.1.1.6" name="">For CT Images, High Bit (0028,0102) shall have only the Enumerated Value of one less than the value sent in Bits Stored.
</section>
    </entry>
    <entry group="0028" element="1052" name="Rescale Intercept" type="1">
      <description>The value b in relationship between stored values (SV) and Hounsfield (HU). HU = m*SV+b</description>
    </entry>
    <entry group="0028" element="1053" name="Rescale Slope" type="1">
      <description>m in the equation specified in Rescale Intercept (0028,1052).</description>
    </entry>
    <entry group="0018" element="0060" name="KVP" type="2">
      <description>Peak kilo voltage output of the x-ray generator used</description>
    </entry>
    <entry group="0020" element="0012" name="Acquisition Number" type="2">
      <description>A number identifying the single continuous gathering of data over a period of time which resulted in this image</description>
    </entry>
    <entry group="0018" element="0022" name="Scan Options" type="3">
      <description>Parameters of scanning sequence.</description>
    </entry>
    <entry group="0018" element="0090" name="Data Collection Diameter" type="3">
      <description>The diameter in mm of the region over which data were collected</description>
    </entry>
    <entry group="0018" element="9313" name="Data Collection Center (Patient)" type="3">
      <description>The x, y, and z coordinates (in the patient coordinate system) in mm of the center of the region in which data were collected. See C.8.15.3.6.1.</description>
      <section ref="C.8.15.3.6.1" name="">In Figure C.8-19 the relationship of the Geometric Attributes within the CT Geometry and CT Reconstruction functional groups is shown. The figure, viewed from the front of the gantry (where the table enters the gantry), is informative only and is not meant to represent a standardization of an equipment-based frame of reference.
 Figure C.8-19: Geometry of CT Acquisition System

</section>
    </entry>
    <entry group="0018" element="1100" name="Reconstruction Diameter" type="3">
      <description>Diameter in mm of the region from within which data were used in creating the reconstruction of the image. Data may exist outside this region and portions of the patient may exist outside this region.</description>
    </entry>
    <entry group="0018" element="9318" name="Reconstruction Target Center (Patient)" type="3">
      <description>The x, y, and z coordinates (in the patient coordinate system) of the reconstruction center target point as used for reconstruction in mm. See C.8.15.3.6.1.
Note: If the reconstructed image is not magnified or panned the value corresponds with the Data Collection Center (Patient) (0018,9313) attribute.</description>
      <section ref="C.8.15.3.6.1" name="">In Figure C.8-19 the relationship of the Geometric Attributes within the CT Geometry and CT Reconstruction functional groups is shown. The figure, viewed from the front of the gantry (where the table enters the gantry), is informative only and is not meant to represent a standardization of an equipment-based frame of reference.
 Figure C.8-19: Geometry of CT Acquisition System

</section>
    </entry>
    <entry group="0018" element="1110" name="Distance Source to Detector" type="3">
      <description>Distance in mm from source to detector center.
Note: This value is traditionally referred to as Source Image Receptor Distance (SID).</description>
    </entry>
    <entry group="0018" element="1111" name="Distance Source to Patient" type="3">
      <description>Distance in mm from source to isocenter (center of field of view).
Note: This value is traditionally referred to as Source Object Distance (SOD).</description>
    </entry>
    <entry group="0018" element="1120" name="Gantry/Detector Tilt" type="3">
      <description>Nominal angle of tilt in degrees of the scanning gantry. Not intended for mathematical computations.</description>
    </entry>
    <entry group="0018" element="1130" name="Table Height" type="3">
      <description>The distance in mm of the top of the patient table to the center of rotation; below the center is positive.</description>
    </entry>
    <entry group="0018" element="1140" name="Rotation Direction" type="3">
      <description>Direction of rotation of the source when relevant, about nearest principal axis of equipment.
Enumerated Values:
CW = clockwise
CC = counter clockwise</description>
    </entry>
    <entry group="0018" element="1150" name="Exposure Time" type="3">
      <description>Time of x-ray exposure in msec</description>
    </entry>
    <entry group="0018" element="1151" name="X-Ray Tube Current" type="3">
      <description>X-Ray Tube Current in mA.</description>
    </entry>
    <entry group="0018" element="1152" name="Exposure" type="3">
      <description>The exposure expressed in mAs, for example calculated from Exposure Time and X-Ray Tube Current.</description>
    </entry>
    <entry group="0018" element="1153" name="Exposure in µAs" type="3">
      <description>The exposure expressed in µAs, for example calculated from Exposure Time and X-Ray Tube Current.</description>
    </entry>
    <entry group="0018" element="1160" name="Filter Type" type="3">
      <description>Label for the type of filter inserted into the x-ray beam.</description>
    </entry>
    <entry group="0018" element="1170" name="Generator Power" type="3">
      <description>Power in kW to the x-ray generator.</description>
    </entry>
    <entry group="0018" element="1190" name="Focal Spot" type="3">
      <description>Size of the focal spot in mm. For devices with variable focal spot or multiple focal spots, small dimension followed by large dimension.</description>
    </entry>
    <entry group="0018" element="1210" name="Convolution Kernel" type="3">
      <description>A label describing the convolution kernel or algorithm used to reconstruct the data</description>
    </entry>
    <entry group="0018" element="9305" name="Revolution Time" type="3">
      <description>The time in seconds of a complete revolution of the source around the gantry orbit.</description>
    </entry>
    <entry group="0018" element="9306" name="Single Collimation Width" type="3">
      <description>The width of a single row of acquired data (in mm).
Note: Adjacent physical detector rows may have been combined to form a single effective acquisition row.</description>
    </entry>
    <entry group="0018" element="9307" name="Total Collimation Width" type="3">
      <description>The width of the total collimation (in mm) over the area of active x-ray detection.
Note: This will be equal the number of effective detector rows multiplied by single collimation width.</description>
    </entry>
    <entry group="0018" element="9309" name="Table Speed" type="3">
      <description>The distance in mm that the table moves in one second during the gathering of data that resulted in this image.</description>
    </entry>
    <entry group="0018" element="9310" name="Table Feed per Rotation" type="3">
      <description>Motion of the table (in mm) during a complete revolution of the source around the gantry orbit.</description>
    </entry>
    <entry group="0018" element="9311" name="Spiral Pitch Factor" type="3">
      <description>Ratio of the Table Feed per Rotation (0018,9310) to the Total Collimation Width (0018,9307).</description>
    </entry>
    <entry group="0018" element="9323" name="Exposure Modulation Type" type="3">
      <description>A label describing the type of exposure modulation used for the purpose of limiting the dose.
Defined Terms:
NONE</description>
    </entry>
    <entry group="0018" element="9324" name="Estimated Dose Saving" type="3">
      <description>A percent value of dose saving due to the use of Exposure Modulation Type (0018,9323). A negative percent value of dose savings reflects an increase of exposure.</description>
    </entry>
    <entry group="0018" element="9345" name="CTDIvol" type="3">
      <description>Computed Tomography Dose Index (CTDIvol), im mGy according to IEC 60601-2-44, Ed.2.1 (Clause 29.1.103.4), The Volume CTDIvol. It describes the average dose for this image for the selected CT conditions of operation.</description>
    </entry>
    <entry group="0018" element="9346" name="CTDI Phantom Type Code Sequence" type="3">
      <description>The type of phantom used for CTDI measurement according to IEC 60601-2-44. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="DCID 4052"/>
    <include ref="Include 'General Anatomy Optional Macro' Table 10-7" description="Defined Context ID for the Anatomic Region Sequence is 4030."/>
    <entry group="0018" element="9351" name="Calcium Scoring Mass Factor Patient" type="3">
      <description>The calibration factor for the calcium mass score. These factors incorporate the effects of
See C.8.2.1.1.7.</description>
      <section ref="C.8.2.1.1.7" name="">The calibration factors for the Calcium Scoring Mass Factor Patient (0018,9351) and Calcium Scoring Mass Factor Device (0018,9352) attributes are defined by the International Consortium for Multi-Detector CT Evaluation of Coronary Calcium, see McCollough, C.H. “A multi-institutional, multi-manufacturer, international standard for the quantification of coronary artery calcium using cardiac CT”.
</section>
    </entry>
    <entry group="0018" element="9352" name="Calcium Scoring Mass Factor Device" type="3">
      <description>The calibration factors for the calcium mass score of the device. These factors incorporate the effects of
This a multi-value attribute, the first value specifies the mass factor for a small patient size, the second value for a medium patient size and the third value for a large patient size.
See C.8.2.1.1.7.</description>
      <section ref="C.8.2.1.1.7" name="">The calibration factors for the Calcium Scoring Mass Factor Patient (0018,9351) and Calcium Scoring Mass Factor Device (0018,9352) attributes are defined by the International Consortium for Multi-Detector CT Evaluation of Coronary Calcium, see McCollough, C.H. “A multi-institutional, multi-manufacturer, international standard for the quantification of coronary artery calcium using cardiac CT”.
</section>
    </entry>
    <entry group="0018" element="9360" name="CT Additional X-Ray Source Sequence" type="3">
      <description>Contains the attributes defining the data acquisition in a multiple X-Ray source system beyond the primary source. The primary X-Ray source is specified in other attributes of this module.
One or more items may be present.</description>
    </entry>
    <entry group="0018" element="0060" name="&gt;kVP" type="1">
      <description>Peak kilo voltage output of the X-Ray generator used.</description>
    </entry>
    <entry group="0018" element="9330" name="&gt;X-Ray Tube Current in mA" type="1">
      <description>Nominal X-Ray tube current in milliamperes.</description>
    </entry>
    <entry group="0018" element="0090" name="&gt;Data Collection Diameter" type="1">
      <description>The diameter in mm of the region over which data were collected.</description>
    </entry>
    <entry group="0018" element="1190" name="&gt;Focal Spot(s)" type="1">
      <description>Used nominal size of the focal spot in mm.</description>
    </entry>
    <entry group="0018" element="1160" name="&gt;Filter Type(s)" type="1">
      <description>Type of filter(s) inserted into the X-Ray beam.</description>
    </entry>
    <entry group="0018" element="7050" name="&gt;Filter Material" type="1">
      <description>The X-Ray absorbing material used in the filter.</description>
    </entry>
  </module>
  <module ref="C.8.3.1" table="C.8-4" name="MR Image Module Attributes">
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image identification characteristics. See C.8.3.1.1.1 for specialization.</description>
      <section ref="C.8.3.1.1.1" name="">For MR Images, Image Type (0008,0008) is specified to be Type 1 and use one of the following Defined Terms for Value 3:
<defined-terms><term value="MPR"/><term value="PROJECTION IMAGE"/><term value="T1 MAP"/><term value="T2 MAP"/><term value="DIFFUSION MAP"/><term value="DENSITY MAP"/><term value="PHASE MAP"/><term value="VELOCITY MAP"/><term value="IMAGE ADDITION"/><term value="PHASE SUBTRACT"/><term value="MODULUS SUBTRACT"/><term value="OTHER"/></defined-terms>
         </section>
    </entry>
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (planes) in this image. See C.8.3.1.1.2 for specialization.</description>
      <section ref="C.8.3.1.1.2" name="">For MR Images, Samples per Pixel (0028,0002) shall have an Enumerated Value of 1.
</section>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data. See C.8.3.1.1.3 for specialization.</description>
      <section ref="C.8.3.1.1.3" name="">For MR Images, Photometric Interpretation (0028,0004) shall have one of the following Enumerated Values:
    MONOCHROME1
    MONOCHROME2
See C.7.6.3.1.2 for definition of these terms.
</section>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated. See C.8.3.1.1.4 for specialization.</description>
      <section ref="C.8.3.1.1.4" name="">For MR Images, Bits Allocated (0028,0100) shall have the Enumerated Value of 16.
</section>
    </entry>
    <entry group="0018" element="0020" name="Scanning Sequence" type="1">
      <description>Description of the type of data taken.
Enumerated Values:
SE = Spin Echo
IR = Inversion Recovery
GR = Gradient Recalled
EP = Echo Planar
RM = Research Mode
Note: Multi-valued, but not all combinations are valid (e.g. SE/GR, etc.).</description>
    </entry>
    <entry group="0018" element="0021" name="Sequence Variant" type="1">
      <description>Variant of the Scanning Sequence.
Defined Terms:
SK = segmented k-space
MTC = magnetization transfer
contrast
SS = steady state
TRSS = time reversed steady
state
SP = spoiled
MP = MAG prepared
OSP = oversampling phase
NONE = no sequence variant</description>
    </entry>
    <entry group="0018" element="0022" name="Scan Options" type="2">
      <description>Parameters of scanning sequence. Defined Terms:
PER = Phase Encode
Reordering
RG = Respiratory Gating
CG = Cardiac Gating
PPG = Peripheral Pulse Gating
FC = Flow Compensation
PFF = Partial Fourier -
Frequency
PFP = Partial Fourier - Phase
SP = Spatial Presaturation
FS = Fat Saturation</description>
    </entry>
    <entry group="0018" element="0023" name="MR Acquisition Type" type="2">
      <description>Identification of data encoding scheme. Enumerated Values:
2D = frequency x phase
3D = frequency x phase x phase</description>
    </entry>
    <entry group="0018" element="0080" name="Repetition Time" type="2C">
      <description>The period of time in msec between the beginning of a pulse sequence and the beginning of the succeeding (essentially identical) pulse sequence. Required except when Scanning Sequence (0018,0020) is EP and Sequence Variant (0018,0021) is not SK.</description>
    </entry>
    <entry group="0018" element="0081" name="Echo Time" type="2">
      <description>Time in ms between the middle of the excitation pulse and the peak of the echo produced (kx=0). In the case of segmented k-space, the TE(eff) is the time between the middle of the excitation pulse to the peak of the echo that is used to cover the center of k-space (i.e.-kx=0, ky=0).</description>
    </entry>
    <entry group="0018" element="0091" name="Echo Train Length" type="2">
      <description>Number of lines in k-space acquired per excitation per image.</description>
    </entry>
    <entry group="0018" element="0082" name="Inversion Time" type="2C">
      <description>Time in msec after the middle of inverting RF pulse to middle of excitation pulse to detect the amount of longitudinal magnetization. Required if Scanning Sequence (0018,0020) has values of IR.</description>
    </entry>
    <entry group="0018" element="1060" name="Trigger Time" type="2C">
      <description>Time, in msec, between peak of the R wave and the peak of the echo produced. In the case of segmented k-space, the TE(eff) is the time between the peak of the echo that is used to cover the center of k-space. Required for Scan Options (0018,0022) which include heart gating (e.g. CG, PPG, etc.)</description>
    </entry>
    <entry group="0018" element="0024" name="Sequence Name" type="3">
      <description>User defined name for the Scanning Sequence (0018,0020) and Sequence Variant (0018,0021) combination.</description>
    </entry>
    <entry group="0018" element="0025" name="Angio Flag" type="3">
      <description>Angio Image Indicator. Primary image for Angio processing. Enumerated Values:
Y = Image is Angio
N = Image is not Angio</description>
    </entry>
    <entry group="0018" element="0083" name="Number of Averages" type="3">
      <description>Number of times a given pulse sequence is repeated before any parameter is changed</description>
    </entry>
    <entry group="0018" element="0084" name="Imaging Frequency" type="3">
      <description>Precession frequency in MHz of the nucleus being addressed</description>
    </entry>
    <entry group="0018" element="0085" name="Imaged Nucleus" type="3">
      <description>Nucleus that is resonant at the imaging frequency. Examples: 31P, 1H</description>
    </entry>
    <entry group="0018" element="0086" name="Echo Number" type="3">
      <description>The echo number used in generating this image. In the case of segmented k-space, it is the effective Echo Number.</description>
    </entry>
    <entry group="0018" element="0087" name="Magnetic Field Strength" type="3">
      <description>Nominal field strength of MR magnet, in Tesla</description>
    </entry>
    <entry group="0018" element="0088" name="Spacing Between Slices" type="3">
      <description>Spacing between slices, in mm. The spacing is measured from the center-to-center of each slice.</description>
    </entry>
    <entry group="0018" element="0089" name="Number of Phase Encoding Steps" type="3">
      <description>Total number of lines in k-space in the 'y' direction collected during acquisition.</description>
    </entry>
    <entry group="0018" element="0093" name="Percent Sampling" type="3">
      <description>Fraction of acquisition matrix lines acquired, expressed as a percent.</description>
    </entry>
    <entry group="0018" element="0094" name="Percent Phase Field of View" type="3">
      <description>Ratio of field of view dimension in phase direction to field of view dimension in frequency direction, expressed as a percent.</description>
    </entry>
    <entry group="0018" element="0095" name="Pixel Bandwidth" type="3">
      <description>Reciprocal of the total sampling period, in hertz per pixel.</description>
    </entry>
    <entry group="0018" element="1062" name="Nominal Interval" type="3">
      <description>Average R-R interval used for the scans, in msec</description>
    </entry>
    <entry group="0018" element="1080" name="Beat Rejection Flag" type="3">
      <description>Beat length sorting has been applied.
Enumerated Values:
Y = yes
N = No</description>
    </entry>
    <entry group="0018" element="1081" name="Low R-R Value" type="3">
      <description>R-R interval low limit for beat rejection, in msec</description>
    </entry>
    <entry group="0018" element="1082" name="High R-R Value" type="3">
      <description>R-R interval high limit for beat rejection, in msec</description>
    </entry>
    <entry group="0018" element="1083" name="Intervals Acquired" type="3">
      <description>Number of R-R intervals acquired.</description>
    </entry>
    <entry group="0018" element="1084" name="Intervals Rejected" type="3">
      <description>Number of R-R intervals rejected.</description>
    </entry>
    <entry group="0018" element="1085" name="PVC Rejection" type="3">
      <description>Description of type of PVC rejection criteria used.</description>
    </entry>
    <entry group="0018" element="1086" name="Skip Beats" type="3">
      <description>Number of beats skipped after a detected arrhythmia.</description>
    </entry>
    <entry group="0018" element="1088" name="Heart Rate" type="3">
      <description>Beats per minute.</description>
    </entry>
    <entry group="0018" element="1090" name="Cardiac Number of Images" type="3">
      <description>Number of images per cardiac cycle.</description>
    </entry>
    <entry group="0018" element="1094" name="Trigger Window" type="3">
      <description>Percent of R-R interval, based on Heart Rate (0018,1088), prescribed as a window for a valid/usable trigger.</description>
    </entry>
    <entry group="0018" element="1100" name="Reconstruction Diameter" type="3">
      <description>Diameter in mm. of the region from within which data were used in creating the reconstruction of the image. Data may exist outside this region and portions of the patient may exist outside this region.</description>
    </entry>
    <entry group="0018" element="1250" name="Receive Coil Name" type="3">
      <description>Receive coil used.</description>
    </entry>
    <entry group="0018" element="1251" name="Transmit Coil Name" type="3">
      <description>Transmit coil used.</description>
    </entry>
    <entry group="0018" element="1310" name="Acquisition Matrix" type="3">
      <description>Dimensions of the acquired frequency /phase data before reconstruction.
Multi-valued: frequency rows\frequency columns\phase rows\phase columns.</description>
    </entry>
    <entry group="0018" element="1312" name="In-plane Phase Encoding Direction" type="3">
      <description>The axis of phase encoding with respect to the image. Enumerated Values:
ROW = phase encoded in rows.
COL = phase encoded in columns.</description>
    </entry>
    <entry group="0018" element="1314" name="Flip Angle" type="3">
      <description>Steady state angle in degrees to which the magnetic vector is flipped from the magnetic vector of the primary field.</description>
    </entry>
    <entry group="0018" element="1316" name="SAR" type="3">
      <description>Calculated whole body Specific Absorption Rate in watts/kilogram.</description>
    </entry>
    <entry group="0018" element="1315" name="Variable Flip Angle Flag" type="3">
      <description>Flip angle variation applied during image acquisition. Enumerated Values:
Y = yes
N = no</description>
    </entry>
    <entry group="0018" element="1318" name="dB/dt" type="3">
      <description>The rate of change of the gradient coil magnetic flux density with time (T/s).</description>
    </entry>
    <entry group="0020" element="0100" name="Temporal Position Identifier" type="3">
      <description>Temporal order of a dynamic or functional set of Images.</description>
    </entry>
    <entry group="0020" element="0105" name="Number of Temporal Positions" type="3">
      <description>Total number of temporal positions prescribed.</description>
    </entry>
    <entry group="0020" element="0110" name="Temporal Resolution" type="3">
      <description>Time delta between Images in a dynamic or functional set of Images.</description>
    </entry>
    <include ref="Include 'General Anatomy Optional Macro' Table 10-7" description="Defined Context ID for the Anatomic Region Sequence is 4030."/>
  </module>
  <module ref="C.8.4.6" table="C.8-5" name="NM/PET Patient Orientation Module Attributes">
    <entry group="0054" element="0410" name="Patient Orientation Code Sequence" type="2">
      <description>Sequence that describes the orientation of the patient with respect to gravity. See C.8.4.6.1.1 for further explanation. Zero or one item shall be present in the sequence.</description>
      <section ref="C.8.4.6.1.1" name="">The Patient Orientation Code Sequence (0054,0410) is used to describe the orientation of the patient with respect to gravity, and is independent of the position in the gantry.
</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 19. The Coding Scheme Designator (0008,0102) shall have an Enumerated Value of “99SDM” for historical reasons.Code Meaning (0008,0104) shall be Type 3 for historical reasons."/>
    <entry group="0054" element="0412" name="&gt; Patient Orientation Modifier Code Sequence" type="2C">
      <description>Patient Orientation Modifier. Required if needed to fully specify the orientation of the patient with respect to gravity. See C.8.4.6.1.2 for further explanation. Zero or one item shall be present in the sequence.</description>
      <section ref="C.8.4.6.1.2" name="">The Patient Orientation Modifier Code Sequence (0054,0412) is used to modify or enhance the orientation specified by Patient Orientation Code Sequence (0054,0410).
</section>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 20. The Coding Scheme Designator (0008,0102) shall have an Enumerated Value of “99SDM” for historical reasons. Code Meaning (0008,0104) shall be Type 3 for historical reasons."/>
    <entry group="0054" element="0414" name="Patient Gantry Relationship Code Sequence" type="2">
      <description>Sequence which describes the orientation of the patient with respect to the gantry. See Section C.8.4.6.1.3 for further explanation. Zero or one item shall be present in the sequence.</description>
      <section ref="C.8.4.6.1.3" name="">Patient Gantry Relationship Code Sequence (0054,0414) is used to describe the patient direction within the gantry, such as head-first or feet-first. When imaging the extremities, these directions are related to normal anatomic position.
Example: In normal anatomic position, the fingers point towards the feet.
</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 21. The Coding Scheme Designator (0008,0102) shall have an Enumerated Value of “99SDM” for historical reasons. Code Meaning (0008,0104) shall be Type 3 for historical reasons."/>
  </module>
  <module ref="C.8.4.7" table="C.8-6" name="NM Image Pixel Module Attributes">
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (color planes) in this image. The value shall be 1.</description>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data. See C.8.4.7.1.1 for further explanation.</description>
      <section ref="C.8.4.7.1.1" name="">For NM Images, Photometric Interpretation (0028,0004) shall have one of the following Enumerated Values:
MONOCHROME2
PALETTE COLOR
See C.7.6.3.1.2 for definition of these terms.
</section>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated.
Enumerated Values: 8, 16.</description>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored.
The value shall be the same as the value in Bits Allocated (0028,0100).</description>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data. Each sample shall have the same high bit.
Shall be one less than the value in Bits Stored (0028,0101).</description>
    </entry>
    <entry group="0028" element="0030" name="Pixel Spacing" type="2">
      <description>Physical distance in the patient between the center of each pixel, specified by a numeric pair - adjacent row spacing (delimiter) adjacent column spacing, in mm. See 10.7.1.3 for further explanation of the value order.</description>
    </entry>
  </module>
  <module ref="C.8.4.8" table="C.8-7" name="NM Multi Frame Module Attributes">
    <entry group="0028" element="0009" name="Frame Increment Pointer" type="1">
      <description>Contains the Data Element Tags of one or more frame index vectors. See C.8.4.8.1.1 for further specialization.</description>
      <section ref="C.8.4.8.1.1" name="">By definition, NM Images are multi-dimensional Multi-frame Images. The value of the Frame Increment Pointer (0028,0009) contains the Tag for one or more frame indexing vectors. This determines the number of dimensions of frame indices in the image, and the order in which these indices vary from one frame to the next, with the last Tag indicating the most rapidly changing index. The Enumerated Values for the Frame Increment Pointer (0028,0009) are determined by the Image Type (0008,0008), Value 3, as shown in Table C.8-8.
Table C.8-8
ENUMERATED VALUES FOR FRAME INCREMENT POINTER
<unrecognized-rows><term value="Image Type (0008,0008), Value 3" meaning="Frame Increment Pointer (0028,0009)"/><term value="STATIC or WHOLE BODY" meaning="0054H 0010H \ 0054H 0020H"/><term value="DYNAMIC" meaning="0054H 0010H \ 0054H 0020H \ 0054H 0030H \ 0054H 0100H"/><term value="GATED" meaning="0054H 0010H \ 0054H 0020H \ 0054H 0060H \ 0054H 0070H"/><term value="TOMO" meaning="0054H 0010H \ 0054H 0020H \ 0054H 0050H \ 0054H 0090H"/><term value="GATED TOMO" meaning="0054H 0010H \ 0054H 0020H \ 0054H 0050H \ 0054H 0060H \ 0054H 0070H \ 0054H 0090H"/><term value="RECON TOMO" meaning="0054H 0080H"/><term value="RECON GATED TOMO" meaning="0054H 0060H \ 0054H 0070H \ 0054H 0080H"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0054" element="0010" name="Energy Window Vector" type="1C">
      <description>An array which contains the energy window number for each frame. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for Energy Window Vector (0054,0010). See C.8.4.8.1.2 for specialization.</description>
      <section ref="C.8.4.8.1.2" name="">Number of Energy Windows (0054,0011) is the number of distinct energy window groupings acquired in this image. See C.8.4.10.1. When Image Type (0008,0008), Value 3, is RECON TOMO or RECON GATED TOMO, then the Number of Energy Windows (0054,0011) shall be 1.
Energy Window Vector (0054,0010) is an indexing vector. The value of the nth element of this vector is the energy window number for the nth frame in this image, and shall have a value from 1 to Number of Energy Windows (0054,0011).
</section>
    </entry>
    <entry group="0054" element="0011" name="Number of Energy Windows" type="1">
      <description>Number of energy window groupings. See C.8.4.8.1.2 for specialization.</description>
      <section ref="C.8.4.8.1.2" name="">Number of Energy Windows (0054,0011) is the number of distinct energy window groupings acquired in this image. See C.8.4.10.1. When Image Type (0008,0008), Value 3, is RECON TOMO or RECON GATED TOMO, then the Number of Energy Windows (0054,0011) shall be 1.
Energy Window Vector (0054,0010) is an indexing vector. The value of the nth element of this vector is the energy window number for the nth frame in this image, and shall have a value from 1 to Number of Energy Windows (0054,0011).
</section>
    </entry>
    <entry group="0054" element="0020" name="Detector Vector" type="1C">
      <description>An array which contains the detector number for each frame. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for Detector Vector (0054,0020). See C.8.4.8.1.3 for specialization.</description>
      <section ref="C.8.4.8.1.3" name="">Number of Detectors (0054,0021) is the number of separate detectors which differentiate the frames in this image. When Image Type (0008,0008), Value 3, is RECON TOMO or RECON GATED TOMO, then the Number of Detectors (0054,0021) shall be 1.
Note:  Number of Detectors (0054,0021) does not necessarily represent the actual number of detectors used during data acquisition.
  Example 1: In a TOMO acquisition in which frames from 2 or more detectors are interleaved to form one continuous set of frames, then no distinction is made between frames on the basis of which detector created them. In this case, the Number of Detectors (0054,0021) would be 1.
  Example 2: In a WHOLE BODY acquisition in which a single detector acquires anterior and posterior views in two separate passes, the Number of Detectors (0054,0021) would be 2.

Detector Vector (0054,0020) is an indexing vector. The value of the nth element of this vector is the detector number of the nth frame in this image, and shall have a value from 1 to Number of Detectors (0054,0021).
</section>
    </entry>
    <entry group="0054" element="0021" name="Number of Detectors" type="1">
      <description>Number of detectors. See C.8.4.8.1.3 for specialization.</description>
      <section ref="C.8.4.8.1.3" name="">Number of Detectors (0054,0021) is the number of separate detectors which differentiate the frames in this image. When Image Type (0008,0008), Value 3, is RECON TOMO or RECON GATED TOMO, then the Number of Detectors (0054,0021) shall be 1.
Note:  Number of Detectors (0054,0021) does not necessarily represent the actual number of detectors used during data acquisition.
  Example 1: In a TOMO acquisition in which frames from 2 or more detectors are interleaved to form one continuous set of frames, then no distinction is made between frames on the basis of which detector created them. In this case, the Number of Detectors (0054,0021) would be 1.
  Example 2: In a WHOLE BODY acquisition in which a single detector acquires anterior and posterior views in two separate passes, the Number of Detectors (0054,0021) would be 2.

Detector Vector (0054,0020) is an indexing vector. The value of the nth element of this vector is the detector number of the nth frame in this image, and shall have a value from 1 to Number of Detectors (0054,0021).
</section>
    </entry>
    <entry group="0054" element="0030" name="Phase Vector" type="1C">
      <description>An array which contains the phase number for each frame. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for Phase Vector (0054,0030). See C.8.4.8.1.4 for specialization.</description>
      <section ref="C.8.4.8.1.4" name="">Number of Phases (0054,0031) is the number of dynamic phases, independent of the number of Detectors and Isotopes. See Section C.8.4.14 for definition of a phase.
Phase Vector (0054,0030) is an indexing vector. The value of the nth element of this vector is the phase number of the nth frame in this image, and shall have a value from 1 to Number of Phases (0054,0031).
</section>
    </entry>
    <entry group="0054" element="0031" name="Number of Phases" type="1C">
      <description>Number of phases. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for Phase Vector (0054,0030). See C.8.4.8.1.4 for specialization.</description>
      <section ref="C.8.4.8.1.4" name="">Number of Phases (0054,0031) is the number of dynamic phases, independent of the number of Detectors and Isotopes. See Section C.8.4.14 for definition of a phase.
Phase Vector (0054,0030) is an indexing vector. The value of the nth element of this vector is the phase number of the nth frame in this image, and shall have a value from 1 to Number of Phases (0054,0031).
</section>
    </entry>
    <entry group="0054" element="0050" name="Rotation Vector" type="1C">
      <description>An array which contains the rotation number for each frame. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for Rotation Vector (0054,0050). See C.8.4.8.1.5 for specialization.</description>
      <section ref="C.8.4.8.1.5" name="">Number of Rotations (0054,0051) is the number of separate rotations. See Section C.8.4.12 for definition of a rotation. When Image Type (0008,0008), Value 3, is RECON TOMO, GATED TOMO or RECON GATED TOMO, then the Number of Rotations (0054,0051) shall be 1.
Rotation Vector (0054,0050) is an indexing vector. The value of the nth element of this vector is the rotation number of the nth frame in this image, and shall have a value from 1 to Number of Rotations (0054,0051).
</section>
    </entry>
    <entry group="0054" element="0051" name="Number of Rotations" type="1C">
      <description>Number of rotations. Required if Image Type (0008,0008), Value 3 is
TOMO,
GATED TOMO,
RECON TOMO, or
RECON GATED TOMO.
See C.8.4.8.1.5 for specialization.</description>
      <section ref="C.8.4.8.1.5" name="">Number of Rotations (0054,0051) is the number of separate rotations. See Section C.8.4.12 for definition of a rotation. When Image Type (0008,0008), Value 3, is RECON TOMO, GATED TOMO or RECON GATED TOMO, then the Number of Rotations (0054,0051) shall be 1.
Rotation Vector (0054,0050) is an indexing vector. The value of the nth element of this vector is the rotation number of the nth frame in this image, and shall have a value from 1 to Number of Rotations (0054,0051).
</section>
    </entry>
    <entry group="0054" element="0060" name="R-R Interval Vector" type="1C">
      <description>An array which contains the R-R interval number for each frame. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for R-R Interval Vector (0054,0060). See C.8.4.8.1.6 for specialization.</description>
      <section ref="C.8.4.8.1.6" name="">Number of R-R Intervals (0054,0061) is the number of ranges of heartbeat durations collected. A gated acquisition may employ one R-R Interval to collect data from normal beats, a second R-R Interval to collect data from ectopic beats, and possibly others. Each R-R Interval accepts beats whose duration is greater than its Low R-R Value (0018,1081) and shorter than its High R-R Value (0018,1082). Beats which do not fall within these ranges may be accepted by another R-R Interval, or may be rejected.
The Number of R-R Intervals (0054,0061) is the total number of such ranges.
R-R Interval Vector (0054,0060) is an indexing vector. The value of the nth element of this vector is the interval number of the nth frame in this image, and shall have a value from 1 to Number of R-R Intervals (0054,0061).
</section>
    </entry>
    <entry group="0054" element="0061" name="Number of R-R Intervals" type="1C">
      <description>Number of R-R intervals. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for R-R Interval Vector (0054,0060). See C.8.4.8.1.6 for specialization.</description>
      <section ref="C.8.4.8.1.6" name="">Number of R-R Intervals (0054,0061) is the number of ranges of heartbeat durations collected. A gated acquisition may employ one R-R Interval to collect data from normal beats, a second R-R Interval to collect data from ectopic beats, and possibly others. Each R-R Interval accepts beats whose duration is greater than its Low R-R Value (0018,1081) and shorter than its High R-R Value (0018,1082). Beats which do not fall within these ranges may be accepted by another R-R Interval, or may be rejected.
The Number of R-R Intervals (0054,0061) is the total number of such ranges.
R-R Interval Vector (0054,0060) is an indexing vector. The value of the nth element of this vector is the interval number of the nth frame in this image, and shall have a value from 1 to Number of R-R Intervals (0054,0061).
</section>
    </entry>
    <entry group="0054" element="0070" name="Time Slot Vector" type="1C">
      <description>An array which contains the time slot number for each frame. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for Time Slot Vector (0054,0070). See C.8.4.8.1.7 for specialization.</description>
      <section ref="C.8.4.8.1.7" name="">Number of Time Slots (0054,0071) is the number of frames into which each gating event is divided in a gated acquisition. For example, in a cardiac gated acquisition, data from a number of heartbeats are then combined by summing together the first frames from all beats into a summed first frame, all the second frames into a summed second frame, and so on. The result has the same number of frames as the Number of Time Slots in each beat.
Time Slot Vector (0054,0070) is an indexing vector. The value of the nth element of this vector is the time slot number of the nth frame in this image, and shall have a value from 1 to Number of Time Slots (0054,0071).
</section>
    </entry>
    <entry group="0054" element="0071" name="Number of Time Slots" type="1C">
      <description>Number of time slots. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for Time Slot Vector (0054,0070). See C.8.4.8.1.7 for specialization.</description>
      <section ref="C.8.4.8.1.7" name="">Number of Time Slots (0054,0071) is the number of frames into which each gating event is divided in a gated acquisition. For example, in a cardiac gated acquisition, data from a number of heartbeats are then combined by summing together the first frames from all beats into a summed first frame, all the second frames into a summed second frame, and so on. The result has the same number of frames as the Number of Time Slots in each beat.
Time Slot Vector (0054,0070) is an indexing vector. The value of the nth element of this vector is the time slot number of the nth frame in this image, and shall have a value from 1 to Number of Time Slots (0054,0071).
</section>
    </entry>
    <entry group="0054" element="0080" name="Slice Vector" type="1C">
      <description>An array which contains the spatial slice number for each frame. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for Slice Vector (0054,0080). See C.8.4.8.1.8 for specialization.</description>
      <section ref="C.8.4.8.1.8" name="">Number of Slices (0054,0081) is the number of slices in each separate volume.
Note:  For images with Image Type (0008,0008), Value 3, equal to RECON GATED TOMO this implies that Number of Slices (0054,0081) is the same for all R-R Intervals and Time Slots.

Slice Vector (0054,0080) is an indexing vector. The value of the nth element of this vector is the slice number of the nth frame in this image, and shall have a value from 1 to Number of Slices (0054,0081).
</section>
    </entry>
    <entry group="0054" element="0081" name="Number of Slices" type="1C">
      <description>Number of slices. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for Slice Vector (0054,0080). See C.8.4.8.1.8 for specialization.</description>
      <section ref="C.8.4.8.1.8" name="">Number of Slices (0054,0081) is the number of slices in each separate volume.
Note:  For images with Image Type (0008,0008), Value 3, equal to RECON GATED TOMO this implies that Number of Slices (0054,0081) is the same for all R-R Intervals and Time Slots.

Slice Vector (0054,0080) is an indexing vector. The value of the nth element of this vector is the slice number of the nth frame in this image, and shall have a value from 1 to Number of Slices (0054,0081).
</section>
    </entry>
    <entry group="0054" element="0090" name="Angular View Vector" type="1C">
      <description>An array which contains the angular view number for each frame. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for Angular View Vector (0054,0090). See C.8.4.8.1.9 for specialization.</description>
      <section ref="C.8.4.8.1.9" name="">Angular View Vector (0054,0090) is an indexing vector. The value of the nth element of this vector is the angular view number of the nth frame in this image. If Image Type (0008,0008), Value 3, is TOMO or GATED TOMO, then the value shall be from 1 to Number of Frames in Rotation (0054,0053).
</section>
    </entry>
    <entry group="0054" element="0100" name="Time Slice Vector" type="1C">
      <description>An array which contains the time slice number for each frame. Required if the value of the Frame Increment Pointer (0028,0009) includes the Tag for Time Slice Vector (0054,0100). See C.8.4.8.1.10 for specialization.</description>
      <section ref="C.8.4.8.1.10" name="">Time Slice Vector (0054,0100) is an indexing vector. The value of the nth element of this vector is the time slice number of the nth frame in this image, and shall have a value from 1 to Number of Frames in Phase (0054,0033).
</section>
    </entry>
  </module>
  <module ref="C.8.4.9" table="C.8-9" name="NM Image Module Attributes">
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image identification characteristics. See C.8.4.9.1.1 for specialization.</description>
      <section ref="C.8.4.9.1.1" name="">For NM images, Image Type (0008,0008) Value 3 is specified to be Type 1 and use one of the following Enumerated Values:
STATIC
DYNAMIC
GATED
WHOLE BODY
TOMO
GATED TOMO
RECON TOMO
RECON GATED TOMO

For NM images, Image Type (0008,0008) Value 4 is specified to use one of the following Enumerated Values:
EMISSION
TRANSMISSION
Note:  For NM images, Image Type (0008,0008) Value 1 will be ORIGINAL for all raw data and reconstructed images. DERIVED may be appropriate for some other results images.
  For NM images, Image Type (0008,0008) Value 2 will be PRIMARY.

</section>
    </entry>
    <entry group="0054" element="0400" name="Image ID" type="3">
      <description>User or equipment generated Image identifier.</description>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1C">
      <description>Specifies whether an Image has undergone lossy compression. Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5
Required if Lossy Compression has been performed on the Image.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0018" element="0070" name="Counts Accumulated" type="2">
      <description>Sum of all gamma events for all frames in the image. See C.8.4.9.1.2 for specialization.</description>
      <section ref="C.8.4.9.1.2" name="">Counts Accumulated (0018,0070) is the total of all gamma events accumulated in all frames of this Image. This attribute applies to acquisition data, and often does not apply to processed images (DERIVED, SECONDARY).
</section>
    </entry>
    <entry group="0018" element="0071" name="Acquisition Termination Condition" type="3">
      <description>Description of how the data collection was stopped. Defined Terms:
CNTS = counts
DENS = density
MANU = manual
OVFL = data overflow
TIME = time
TRIG = physiological trigger
See C.8.4.9.1.3 for specialization.</description>
      <section ref="C.8.4.9.1.3" name="">Acquisition Termination Condition (0018,0071) is the method of acquisition termination which was actually applied to the data collection. The Defined Terms and definitions are:
CNTS  =  preset count limit was reached
DENS  =  preset count density was reached
MANU  =  acquisition was terminated manually
OVFL  =  acquisition was terminated automatically by pixel data overflow condition
TIME  =  preset time limit was reached
TRIG  =  preset number of physiological triggers was reached

</section>
    </entry>
    <entry group="0018" element="1130" name="Table Height" type="3">
      <description>The height of the patient table in mm. The range and values of this element are determined by the manufacturer. Should not be included if Image Type (0008,0008), Value 3, is
TOMO,
GATED TOMO,
RECON TOMO or
RECON GATED TOMO.</description>
    </entry>
    <entry group="0018" element="1131" name="Table Traverse" type="3">
      <description>Location of the patient table (or gantry relative to the table) in mm. The range and values of this element are determined by the manufacturer. Should not be included if Image Type (0008,0008), Value 3, is
TOMO,
GATED TOMO,
RECON TOMO or
RECON GATED TOMO.</description>
    </entry>
    <entry group="0018" element="1242" name="Actual Frame Duration" type="1C">
      <description>Elapsed time for data acquisition in msec. Required if Image Type (0008,0008) Value 3 is:
WHOLE BODY or
STATIC.
See C.8.4.9.1.4 for specialization.</description>
      <section ref="C.8.4.9.1.4" name="">Actual Frame Duration (0018,1242) is defined as the elapsed time in msec for a single frame of an acquisition. For some types of multi-frame images, Actual Frame Duration (0018,1242) may have a more specialized meaning as defined in the appropriate IOD Module.

</section>
    </entry>
    <entry group="0018" element="1243" name="Count Rate" type="3">
      <description>Maximum count rate achieved during the acquisition in counts/sec.</description>
    </entry>
    <entry group="0018" element="5020" name="Processing Function" type="3">
      <description>Code or description of processing functions applied to the data.</description>
    </entry>
    <entry group="0028" element="0051" name="Corrected Image" type="3">
      <description>A value that indicates which, if any, corrections have been applied to the image. Corrections are applied to all frames in the image. Defined Terms:
UNIF = flood corrected
COR = center of rotation corrected
NCO = non-circular orbit corrected
DECY = decay corrected
ATTN = attenuation corrected
SCAT = scatter corrected
DTIM = dead time corrected
NRGY = energy corrected
LIN = linearity corrected
MOTN = motion corrected
CLN = count loss normalization; Any type of normalization applied to correct for count loss in Time Slots.</description>
    </entry>
    <entry group="0018" element="1301" name="Whole Body Technique" type="3">
      <description>The type of scan performed. Used only if Image Type (0008,0008), Value 3, contains the value WHOLE BODY. Enumerated Values:
1PS = one pass
2PS = two pass
PCN = patient contour following
employed
MSP = multiple static frames
collected into a whole
body frame.</description>
    </entry>
    <entry group="0018" element="1300" name="Scan Velocity" type="2C">
      <description>The speed of the camera motion over the body in mm/sec.
Required if Image Type (0008,0008) Value 3 contains the value WHOLE BODY.</description>
    </entry>
    <entry group="0018" element="1302" name="Scan Length" type="2C">
      <description>Size of the imaged area in the direction of scanning motion, in mm. Required if Image Type (0008,0008) Value 3 contains the value WHOLE BODY.</description>
    </entry>
    <entry group="0018" element="1061" name="Trigger Source or Type" type="3">
      <description>Text indicating trigger source. Defined Term:
EKG</description>
    </entry>
    <include ref="Include 'General Anatomy Optional Macro' Table 10-7" description="No Context ID for the Anatomic Region Sequence is defined."/>
  </module>
  <module ref="C.8.4.10" table="C.8-10" name="NM Isotope Module Attributes">
    <entry group="0054" element="0012" name="Energy Window Information Sequence" type="2">
      <description>Sequence of Items that describe the energy window groups used. Zero or more Items may be included in this sequence.
The number of items shall be equal to Number of Energy Windows (0054,0011). The first item corresponds to frames with value of 1 in the Energy Window Vector (0054,0010), the second item with value 2, etc.</description>
    </entry>
    <entry group="0054" element="0018" name="&gt;Energy Window Name" type="3">
      <description>A user defined name which describes this Energy Window.</description>
    </entry>
    <entry group="0054" element="0013" name="&gt;Energy Window Range Sequence" type="3">
      <description>Sequence of Items that describes this energy window group. One or more Items may be included in this Sequence.</description>
    </entry>
    <entry group="0054" element="0014" name="&gt;&gt;Energy Window Lower Limit" type="3">
      <description>The lower limit of the energy window in KeV. See C.8.4.10.1.1 for further explanation.</description>
      <section ref="C.8.4.10.1.1" name="">Energy Window Lower Limit (0054,0014) is the acquisition energy window lower limit in KeV for acceptance of scintillation events into this Isotope.
</section>
    </entry>
    <entry group="0054" element="0015" name="&gt;&gt;Energy Window Upper Limit" type="3">
      <description>The upper limit of the energy window in KeV. See C.8.4.10.1.2 for further explanation.</description>
      <section ref="C.8.4.10.1.2" name="">Energy Window Upper Limit (0054,0015) is the acquisition energy window upper limit in KeV for acceptance of scintillation events into this Isotope.
</section>
    </entry>
    <entry group="0054" element="0016" name="Radiopharmaceutical Information Sequence" type="2">
      <description>Sequence of Items that describe isotope information. Zero or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0054" element="0300" name="&gt;Radionuclide Code Sequence" type="2">
      <description>Sequence that identifies the radionuclide. Zero or one item shall be present in the sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 18.The Coding Scheme Designator (0008,0102) shall have an Enumerated Value of “99SDM” for historical reasons. Code Meaning (0008,0104) shall be Type 3 for historical reasons."/>
    <entry group="0018" element="1070" name="&gt;Radiopharmaceutical Route" type="3">
      <description>Route of injection.</description>
    </entry>
    <entry group="0054" element="0302" name="&gt;Administration Route Code Sequence" type="3">
      <description>Sequence that identifies the administration route for the radiopharmaceutical. This sequence shall contain exactly one item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 11. Code Meaning (0008,0104) shall be Type 3 for historical reasons."/>
    <entry group="0018" element="1071" name="&gt;Radiopharmaceutical Volume" type="3">
      <description>Volume of injection in cubic cm.</description>
    </entry>
    <entry group="0018" element="1072" name="&gt;Radiopharmaceutical Start Time" type="3">
      <description>Time of start of injection. See C.8.4.10.1.5 for further explanation.</description>
      <section ref="C.8.4.10.1.5" name="">Radiopharmaceutical Start Time (0018,1072) is the actual time of radiopharmaceutical administration to the patient for imaging purposes, using the same time base as for the Acquisition Start Time (0008,0032).
</section>
    </entry>
    <entry group="0018" element="1073" name="&gt;Radiopharmaceutical Stop Time" type="3">
      <description>Time of end of injection. See C.8.4.10.1.6 for further explanation.</description>
      <section ref="C.8.4.10.1.6" name="">Radiopharmaceutical Stop Time (0018,1073) is the actual ending time of radiopharmaceutical administration to the patient for imaging purposes, using the same time base as for the Acquisition Start Time (0008,0032).
</section>
    </entry>
    <entry group="0018" element="1074" name="&gt;Radionuclide Total Dose" type="3">
      <description>Total amount of radionuclide injected. See C.8.4.10.1.7 for further explanation.</description>
      <section ref="C.8.4.10.1.7" name="">Radionuclide Total Dose (0018,1074) is the radiopharmaceutical dose administered to the patient measured in MegaBecquerels (Mbq) at the Radiopharmaceutical Start Time.
</section>
    </entry>
    <entry group="0054" element="0306" name="&gt;Calibration Data Sequence" type="3">
      <description>Sequence that contains calibration data. One or more Items may be included in this Sequence.</description>
    </entry>
    <entry group="0054" element="0308" name="&gt;&gt;Energy Window Number" type="1">
      <description>The Item number in the Energy Window Information Sequence to which the following calibration data relates. The Items are numbered starting from 1.</description>
    </entry>
    <entry group="0018" element="1045" name="&gt;&gt;Syringe Counts" type="3">
      <description>Pre-injection syringe count rate in counts/sec. See C.8.4.10.1.8 for further explanation.</description>
      <section ref="C.8.4.10.1.8" name="">Syringe Counts (0018,1045) is the pre-injection syringe acquisition count rate measured in counts/sec, corrected to the Acquisition Start Time (0008,0032) if necessary.
</section>
    </entry>
    <entry group="0054" element="0017" name="&gt;&gt;Residual Syringe Counts" type="3">
      <description>Post-injection residue syringe count rate in counts/sec. See C.8.4.10.1.9 for further explanation.</description>
      <section ref="C.8.4.10.1.9" name="">Residual Syringe Counts (0054,0017) is the syringe acquisition count rate following patient injection, measured in counts/sec, corrected to the Acquisition Start Time (0008,0032) if necessary.
</section>
    </entry>
    <entry group="0018" element="0031" name="&gt;Radiopharmaceutical" type="3">
      <description>Name of the radiopharmaceutical.</description>
    </entry>
    <entry group="0054" element="0304" name="&gt;Radiopharmaceutical Code Sequence" type="3">
      <description>Sequence that identifies the radiopharmaceutical. This sequence shall contain exactly one item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 25. Code Meaning (0008,0104) shall be Type 3 for historical reasons."/>
    <entry group="0018" element="0026" name="Intervention Drug Information Sequence" type="3">
      <description>Sequence of Items that describes the intervention drugs used. Zero or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0018" element="0034" name="&gt;Intervention Drug Name" type="3">
      <description>Name of intervention drug.</description>
    </entry>
    <entry group="0018" element="0029" name="&gt;Intervention Drug Code Sequence" type="3">
      <description>Sequence that identifies the intervention drug name. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 10. Code Meaning (0008,0104) shall be Type 3 for historical reasons."/>
    <entry group="0054" element="0302" name="&gt;Administration Route Code Sequence" type="3">
      <description>Sequence that identifies the administration route for the intervention drug. This sequence shall contain exactly one item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 11. Code Meaning (0008,0104) shall be Type 3 for historical reasons."/>
    <entry group="0018" element="0035" name="&gt;Intervention Drug Start Time" type="3">
      <description>Time of administration of the intervention drug, using the same time base as for the Acquisition Start Time (0008,0032).</description>
    </entry>
    <entry group="0018" element="0027" name="&gt;Intervention Drug Stop Time" type="3">
      <description>Time of completion of administration of the intervention drug, using the same time base as for the Acquisition Start Time (0008,0032).</description>
    </entry>
    <entry group="0018" element="0028" name="&gt;Intervention Drug Dose" type="3">
      <description>Intervention drug dose, in mg.</description>
    </entry>
  </module>
  <module ref="C.8.4.11" table="C.8-11" name="NM Detector Module Attributes">
    <entry group="0054" element="0022" name="Detector Information Sequence" type="2">
      <description>Sequence of Items that describe the detectors used. Zero or more Items may be included in this sequence.
The number of items shall be equal to Number of Detectors (0054,0021). The first item corresponds to frames with value of 1 in the Detector Vector (0054,0020), the second item with value 2, etc.</description>
    </entry>
    <entry group="0018" element="1180" name="&gt;Collimator/Grid Name" type="3">
      <description>Label describing the collimator used (LEAP, hires, etc.)</description>
    </entry>
    <entry group="0018" element="1181" name="&gt;Collimator Type" type="2">
      <description>Collimator type. Defined Terms:
PARA = Parallel (default)
PINH = Pinhole
FANB = Fan-beam
CONE = Cone-beam
SLNT = Slant hole
ASTG = Astigmatic
DIVG = Diverging
NONE = No collimator
UNKN = Unknown
</description>
    </entry>
    <entry group="0018" element="1147" name="&gt;Field of View Shape" type="3">
      <description>Shape of the field of view of the Nuclear Medicine detector. Defined Terms:
RECTANGLE
ROUND
HEXAGONAL</description>
    </entry>
    <entry group="0018" element="1149" name="&gt;Field of View Dimension(s)" type="3">
      <description>Dimensions of the field of view, in mm. If Field of View Shape (0018,1147) is:
RECTANGLE: row dimension followed by column.
ROUND: diameter.
HEXAGONAL: diameter of a circumscribed circle.</description>
    </entry>
    <entry group="0018" element="1182" name="&gt;Focal Distance" type="2">
      <description>Focal distance, in mm. A value of 0 means infinite distance for parallel collimation. See C.8.4.11.1.1 for further specialization.</description>
      <section ref="C.8.4.11.1.1" name="">Focal Distance (0018,1182) for NM Image data is the focal distance, in mm for converging or diverging collimators, measured from the front face of the detector to the focus. Positive values indicate converging and negative values indicate diverging collimators. A value of 0 means infinite distance for parallel collimation.
</section>
    </entry>
    <entry group="0018" element="1183" name="&gt;X Focus Center" type="3">
      <description>Center of focus along a row. See C.8.4.11.1.2 for further explanation.</description>
      <section ref="C.8.4.11.1.2" name="">X Focus Center (0018,1183) and Y Focus Center (0018,1184) for NM Image data is used to define the projection of the focus for a converging or diverging collimator within the un-zoomed Field of View. It is defined in mm for row and column relative to the center of the un-zoomed Field of View.
</section>
    </entry>
    <entry group="0018" element="1184" name="&gt;Y Focus Center" type="3">
      <description>Center of focus along a column. See C.8.4.11.1.2 for further explanation.</description>
      <section ref="C.8.4.11.1.2" name="">X Focus Center (0018,1183) and Y Focus Center (0018,1184) for NM Image data is used to define the projection of the focus for a converging or diverging collimator within the un-zoomed Field of View. It is defined in mm for row and column relative to the center of the un-zoomed Field of View.
</section>
    </entry>
    <entry group="0028" element="0032" name="&gt;Zoom Center" type="3">
      <description>The amount of offset from (0,0) applied to each pixel in the image before application of the zoom factor, specified by a numeric pair: row value (delimiter) column value (in mm). See C.8.4.11.1.3 for further explanation.</description>
      <section ref="C.8.4.11.1.3" name="">Zoom Center (0028,0032) is the offset between the un-zoomed camera field of view and field of view, measured from the center of the un-zoomed camera field of view to the center the of the zoomed field of view. The offset is measured in mm in the un-zoomed camera FOV dimensions. Positive values are to the right and down from the un-zoomed center, as viewed from the image plane. When this attribute is not given, the Zoom Center is assumed to be 0\0.
</section>
    </entry>
    <entry group="0028" element="0031" name="&gt;Zoom Factor" type="3">
      <description>The amount of magnification applied to each pixel in the image, specified by a numeric pair: row value (delimiter) column value. See C.8.4.11.1.4 for further explanation.</description>
      <section ref="C.8.4.11.1.4" name="">Zoom Factor (0028,0031) is the magnification factor that was used during the acquisition. When this attribute is not given, it is assumed to be 1.0\1.0.
Note:  Zoom Factor (0028,0031) is informational only. Pixel Spacing (0028,0030) already takes account of this and any other changes to pixel size.

</section>
    </entry>
    <entry group="0018" element="1145" name="&gt;Center of Rotation Offset" type="3">
      <description>Average center of rotation offset of Nuclear Medicine detector in mm. See C.8.4.11.1.5 for further explanation.</description>
      <section ref="C.8.4.11.1.5" name="">Center of Rotation Offset (0018,1145) is the average amount of offset in mm between the Detector Field of View center and the physical center of rotation of the gantry for circular orbital scans. Positive values indicate the physical center is to the right of the image plane center.
If:
1) Image Type (0008,0008) Value 3 is TOMO or GATED TOMO, and
2) Corrected Image (0028,0051) does not include the value "COR", and
3) Center of Rotation Offset (0018,1145) is non-zero,
then the receiver should assume that Center of Rotation correction has not already been done.
If the Center of Rotation Offset is zero, no correction shall be applied.
</section>
    </entry>
    <entry group="0018" element="1120" name="&gt;Gantry/Detector Tilt" type="3">
      <description>Angle of tilt in degrees of the detector. See C.8.4.11.1.6 for further explanation.</description>
      <section ref="C.8.4.11.1.6" name="">Gantry/Detector Tilt (0018,1120) for NM Image data is the angle in degrees of the detector face relative to the patient's major (Head to Feet) axis (or the table supporting the patient). Positive tilt is towards the patient’s feet.
</section>
    </entry>
    <entry group="0018" element="1110" name="&gt;Distance Source to Detector" type="2C">
      <description>Distance in mm from transmission source to the detector face. Required if Image Type (0008,0008) Value 4 is TRANSMISSION, Value 3 is not TOMO,.</description>
    </entry>
    <entry group="0054" element="0200" name="&gt;Start Angle" type="3">
      <description>Position of the detector about the patient for the start of the acquisition, in degrees. Zero degrees is referenced to the origin at the patient's back. Viewing from the patient's feet, angle increases in a counter-clockwise direction (detector normal rotating from the patient's back towards the patient's left side). Should not be included if Image Type (0008,0008), Value 3, is
TOMO,
GATED TOMO,
RECON TOMO or
RECON GATED TOMO.</description>
    </entry>
    <entry group="0018" element="1142" name="&gt;Radial Position" type="3">
      <description>Radial distance of the detector from the center of rotation, in mm. Should not be included if Image Type (0008,0008), Value 3, is
TOMO,
GATED TOMO,
RECON TOMO or
RECON GATED TOMO.</description>
    </entry>
    <entry group="0020" element="0037" name="&gt;Image Orientation (Patient)" type="2">
      <description>The direction cosines of the first row and the first column with respect to the patient. See C.7.6.2.1.1 for further explanation.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
    <entry group="0020" element="0032" name="&gt;Image Position (Patient)" type="2">
      <description>The x, y, and z coordinates of the upper left hand corner (center of the first voxel transmitted) of the image, in mm. See C.7.6.2.1.1 for further explanation.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
    <entry group="0054" element="0220" name="&gt;View Code Sequence" type="3">
      <description>Sequence that describes the projection of the anatomic region of interest on the image receptor. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 26 . Code Meaning (0008,0104) shall be Type 3 for historical reasons."/>
    <entry group="0054" element="0222" name="&gt;&gt;View Modifier Code Sequence" type="2C">
      <description>View Modifier. Required if needed to fully specify the View. Zero or one Items shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 23. Code Meaning (0008,0104) shall be Type 3 for historical reasons."/>
  </module>
  <module ref="C.8.4.12" table="C.8-12" name="NM Tomo Acquisition Module Attributes">
    <entry group="0054" element="0052" name="Rotation Information Sequence" type="2">
      <description>Sequence of Items that describe TOMO rotational groups. A new rotation is defined whenever the direction of the detector motion changes, or the Table Traverse (0018,1131) changes. Zero or more Items may be included in this sequence.
The number of items shall be equal to Number of Rotations (0054,0051). If Rotation Vector (0054,0050) is present, the first item corresponds to frames with value of 1 in the Rotation Vector (0054,0050), the second item with value 2, etc.</description>
    </entry>
    <entry group="0054" element="0200" name="&gt;Start Angle" type="1">
      <description>Position of the detector about the patient for the start of this rotation, in degrees. Zero degrees is referenced to the origin at the patient's back. Viewing from the patient's feet, angle increases in a counter-clockwise direction (detector normal rotating from the patient's back towards the patient's left side).</description>
    </entry>
    <entry group="0018" element="1144" name="&gt;Angular Step" type="1">
      <description>The angular scan arc step between views of the TOMO acquisition, in degrees. See C.8.4.12.1.1 for further explanation.</description>
      <section ref="C.8.4.12.1.1" name="">Angular Step (0018,1144) is the nominal frame-to-frame incremental angle for TOMO and GATED TOMO acquisition images, defined in degrees. The Angular Step (0018,1144) shall be a positive number. Summation of Angular Step values is not defined to give accurate Angular Position or Scan Arc values. The Angular Step is the effective angular spacing between resultant frames of the Multi-framed planar image data.
</section>
    </entry>
    <entry group="0018" element="1140" name="&gt;Rotation Direction" type="1">
      <description>Direction of rotation of the detector about the patient. See Start Angle (0054,0200) for further explanation of direction.
Enumerated Values:
CW = clockwise (decreasing angle)
CC = counter-clockwise (increasing angle).
</description>
    </entry>
    <entry group="0018" element="1143" name="&gt;Scan Arc" type="1">
      <description>The effective angular range of the scan data in degrees. The value shall be positive.</description>
    </entry>
    <entry group="0018" element="1242" name="&gt;Actual Frame Duration" type="1">
      <description>Nominal acquisition time per angular position, in msec.</description>
    </entry>
    <entry group="0018" element="1142" name="&gt;Radial Position" type="3">
      <description>Radial distance of the detector
from the center of rotation, in mm. It shall have a single value which is an average value for this rotation, or it shall have one value per angular view.</description>
    </entry>
    <entry group="0018" element="1110" name="&gt;Distance Source to Detector" type="2C">
      <description>Distance in mm from transmission source to the detector face. Required if Image Type (0008,0008) and Value 4, is TRANSMISSION.</description>
    </entry>
    <entry group="0054" element="0053" name="&gt;Number of Frames in Rotation" type="1">
      <description>Number of angular views in this rotation.</description>
    </entry>
    <entry group="0018" element="1131" name="&gt;Table Traverse" type="3">
      <description>Location of the patient table (or gantry relative to the table) in mm.The range and values of this element are determined by the manufacturer.</description>
    </entry>
    <entry group="0018" element="1130" name="&gt;Table Height" type="3">
      <description>The distance in mm of the top of the patient table to the center of rotation. Table height below the center of rotation has a positive value.</description>
    </entry>
    <entry group="0054" element="0202" name="Type of Detector Motion" type="3">
      <description>Describes the detector motion during acquisition. Enumerated Values:
STEP AND SHOOT = Interrupted motion, acquire only while stationary.
CONTINUOUS = Gantry motion and acquisition are simultaneous and continuous.
ACQ DURING STEP = Interrupted motion, acquisition is continuous.</description>
    </entry>
  </module>
  <module ref="C.8.4.13" table="C.8-13" name="NM Multi Gated Acquisition Module Attributes">
    <entry group="0018" element="1080" name="Beat Rejection Flag" type="3">
      <description>Heart beat duration sorting has been applied. Enumerated Values:
Y = yes
N = no</description>
    </entry>
    <entry group="0018" element="1085" name="PVC Rejection" type="3">
      <description>Description of type of arrhythmic beat rejection criteria used.</description>
    </entry>
    <entry group="0018" element="1086" name="Skip Beats" type="3">
      <description>Number of beats skipped after a detected arrhythmia</description>
    </entry>
    <entry group="0018" element="1088" name="Heart Rate" type="3">
      <description>Average number of heart beats per minute for the collection period for these frames. This shall include all accepted beats as well as rejected beats.</description>
    </entry>
    <entry group="0054" element="0062" name="Gated Information Sequence" type="2C">
      <description>Sequence of Items that describe R-R intervals. Each gated interval is defined by an upper and lower range of heart beat durations. Required if the Frame Increment Pointer (0028,0009) contains the Tag for R-R Interval Vector (0054,0060). Zero or more Items may be included in this sequence.
The number of items shall be equal to Number of R-R Intervals (0054,0061). The first item corresponds to frames with value of 1 in the R-R Interval Vector (0054,0060), the second item with value 2, etc.</description>
    </entry>
    <entry group="0018" element="1060" name="&gt;Trigger Time" type="3">
      <description>Time interval measured in msec from the start of the R-wave to the beginning of the data taking.</description>
    </entry>
    <entry group="0018" element="1064" name="&gt;Cardiac Framing Type" type="3">
      <description>Description of type of framing performed such as forward, backward, forward/backward by percentage.
See C.7.6.18.1.1.1.</description>
      <section ref="C.7.6.18.1.1.1" name="">Cardiac Framing Type (0018,1064) is the mechanism used to select the data acquired to construct the frames within a specified cardiac timing interval.C.7.6.18.2  Respiratory Synchronization Module
Table C7.6.18-2 specifies the attributes of the Respiratory Synchronization Module.
Table C.7.6.18-2
RESPIRATORY SYNCHRONIZATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Respiratory Motion Compensation Technique" meaning="(0018,9170)"/><term value="Respiratory Signal Source" meaning="(0018,9171)"/><term value="Respiratory Trigger Delay Threshold" meaning="(0020,9256)"/><term value="Respiratory Trigger Type" meaning="(0020,9250)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0054" element="0063" name="&gt;Data Information Sequence" type="2">
      <description>Sequence of Items that describe gating criteria. Zero or more Items may be included in this sequence. See C.8.4.13.1.1.</description>
      <section ref="C.8.4.13.1.1" name="">Data Information Sequence (0054,0063) shall contain a single sequence item which applies to the sum of all angular views, except when Image Type (0008,0008) Value 3 is GATED TOMO. In this case it shall have either a single item which applies to the sum of all angular views, or it shall have one item for each angular view.
</section>
    </entry>
    <entry group="0018" element="1063" name="&gt;&gt;Frame Time" type="1">
      <description>Nominal time per individual frame in msec.</description>
    </entry>
    <entry group="0018" element="1062" name="&gt;&gt;Nominal Interval" type="3">
      <description>Average duration of accepted beats, in msec.</description>
    </entry>
    <entry group="0018" element="1081" name="&gt;&gt;Low R-R Value" type="3">
      <description>R-R interval lower limit for beat rejection, in msec</description>
    </entry>
    <entry group="0018" element="1082" name="&gt;&gt;High R-R Value" type="3">
      <description>R-R interval upper limit for beat rejection, in msec</description>
    </entry>
    <entry group="0018" element="1083" name="&gt;&gt;Intervals Acquired" type="3">
      <description>Number of heartbeats that fall within Low R-R Value (0018,1081) and High R-R Value (0018,1082), and were therefore accepted and contribute gamma events to this R-R Interval.</description>
    </entry>
    <entry group="0018" element="1084" name="&gt;&gt;Intervals Rejected" type="3">
      <description>Number of heartbeats that fall outside Low R-R (0018,1081) and High R-R Value (0018,1082), and do not contribute gamma events to this R-R Interval. However, they may contribute gamma events to other R-R Intervals.</description>
    </entry>
    <entry group="0054" element="0072" name="&gt;&gt;Time Slot Information Sequence" type="2C">
      <description>Sequence of Items that describe Time Slot Information. Required if the Frame Increment Pointer (0028,0009) contains the Tag for Time Slot Vector (0054,0070). Zero or more Items may be included in this sequence.
The number of items shall be equal to Number of Time Slots (0054,0071). The first item corresponds to frames with value of 1 in the Time Slot Vector (0054,0070), the second item with value 2, etc.</description>
    </entry>
    <entry group="0054" element="0073" name="&gt;&gt;&gt;Time Slot Time" type="3">
      <description>The total amount of time, in msec, that the acquisition accumulates gamma events into this frame. See C.8.4.13.1.2.</description>
      <section ref="C.8.4.13.1.2" name="">The Time Slot Time (0054,0073) records the effective imaging time of each Time Slot. For example, if some of the accepted beats are shorter than others then the last frames may not receive a contribution from the shorter beats. The Time Slot Time for a Time Slot is the total acquisition time for that Time Slot. It is approximately equal to the Frame Time (0018,1063) multiplied by the number of accepted beats contributing to the Time Slot.
</section>
    </entry>
  </module>
  <module ref="C.8.4.14" table="C.8-14" name="NM Phase Module Attributes">
    <entry group="0054" element="0032" name="Phase Information Sequence" type="2C">
      <description>Sequence of Items that describes each dynamic phase. Required if the Frame Increment Pointer (0028,0009) contains the Tag for Phase Vector (0054,0030). Zero or more Items may be included in this sequence.
The number of items shall be equal to Number of Phases (0054,0031). The first item corresponds to frames with value of 1 in the Phase Vector (0054,0030), the second item with value 2, etc.</description>
    </entry>
    <entry group="0054" element="0036" name="&gt;Phase Delay" type="1">
      <description>Time paused between the last frame of the previous phase and the first frame of this phase, in msec.</description>
    </entry>
    <entry group="0018" element="1242" name="&gt;Actual Frame Duration" type="1">
      <description>Nominal time of acquisition per individual frame, in msec.</description>
    </entry>
    <entry group="0054" element="0038" name="&gt;Pause Between Frames" type="1">
      <description>Time paused between each frame of this phase (in msec).</description>
    </entry>
    <entry group="0054" element="0033" name="&gt;Number of Frames in Phase" type="1">
      <description>Number of frames in this phase.</description>
    </entry>
    <entry group="0054" element="0210" name="&gt;Trigger Vector" type="3">
      <description>An array of trigger times when gating information is acquired simultaneously with the dynamic image data. See Section C.8.4.14.1.1 for further explanation.</description>
      <section ref="C.8.4.14.1.1" name="">Trigger Vector (0054,0210) is an array containing a list of the inter-trigger interval times in milliseconds in the order in which they were acquired, with the first being measured from the start time of the first frame of the image data in the Phase. If this element is used, the start times are required to be the same so that a mathematical correlation can be made between trigger times and frame start times.
</section>
    </entry>
    <entry group="0054" element="0211" name="&gt;Number of Triggers in Phase" type="1C">
      <description>The number of entries in the Trigger Vector (0054,0210) for this phase. Required if Trigger Vector (0054,0210) is present.</description>
    </entry>
    <entry group="0054" element="0039" name="&gt;Phase Description" type="3">
      <description>Description of this phase of the Dynamic image.
Defined Terms:
FLOW
WASHOUT
UPTAKE
EMPTYING
EXCRETION</description>
    </entry>
  </module>
  <module ref="C.8.4.15" table="C.8-15" name="NM Reconstruction Module Attributes">
    <entry group="0018" element="0088" name="Spacing Between Slices" type="2">
      <description>Spacing between slices, in mm, measured from center-to-center of each slice along the normal to the first image. The sign of the Spacing Between Slices (0018,0088) determines the direction of stacking. The normal is determined by the cross product of the direction cosines of the first row and first column of the first frame, such that a positive spacing indicates slices are stacked behind the first slice and a negative spacing indicates slices are stacked in front of the first slice. See Image Orientation (0020,0037) in the NM Detector module.</description>
    </entry>
    <entry group="0018" element="1100" name="Reconstruction Diameter" type="3">
      <description>Diameter, in mm, of the region from within which the data was used in creating the reconstruction of the image. Data may exist outside this region and portions of the patient may exist outside this region.</description>
    </entry>
    <entry group="0018" element="1210" name="Convolution Kernel" type="3">
      <description>A label describing the convolution kernel or algorithm used to reconstruct the data.</description>
    </entry>
    <entry group="0018" element="0050" name="Slice Thickness" type="2">
      <description>Nominal slice thickness, in mm.</description>
    </entry>
    <entry group="0020" element="1041" name="Slice Location" type="3">
      <description>Relative position of the image plane expressed in mm.
See C.7.6.2.1.2 for further explanation.</description>
      <section ref="C.7.6.2.1.2" name="">The Slice Location (0020,1041) is defined as the relative position of the image plane expressed in mm. This information is relative to an unspecified implementation specific reference point.
</section>
    </entry>
    <entry group="0054" element="0500" name="Slice Progression Direction" type="3">
      <description>Describes the anatomical direction that slices are progressing as the slices are considered in order (as defined by the Slice Vector (0054,0080)). Meaningful only for cardiac images.
When View Code Sequence (0054,0220) indicates a short axis view, then Enumerated Values are:
APEX_TO_BASE
BASE_TO_APEX</description>
    </entry>
  </module>
  <module ref="C.8.5.5" table="C.8-17" name="US Region Calibration Module Attributes">
    <entry group="0018" element="6011" name="Sequence of Ultrasound Regions" type="1">
      <description>Defines a sequence of Ultrasound Regions. One or more Items may be included in this Sequence.</description>
    </entry>
    <entry group="0018" element="6018" name="&gt;Region Location Min x0" type="1">
      <description>The bounds of a rectangle specifying the location of the region, x0,y0,x1,y1.
See C.8.5.5.1.14 for further explanation.</description>
      <section ref="C.8.5.5.1.14" name="">These attributes specify the location of the region, Region Location Min x0 (0018,6018), Region Location Min y0 (0018,601A), Region Location Max x1 (0018,601C), Region Location Max y1 (0018,601E) expressed as offsets to the pixel coordinates. The upper left corner of the entire image is x=0,y=0 and the lower right corner is x=image width - 1, and y=image length - 1. Thus, a region will be specified as within these bounds. Where x0,y0 is the coordinate of the upper left corner of the region and x1,y1 is the coordinate of the lower right corner of the region.
</section>
    </entry>
    <entry group="0018" element="601A" name="&gt;Region Location Min y0" type="1">
      <description>The bounds of a rectangle specifying the location of the region, x0,y0,x1,y1.
See C.8.5.5.1.14 for further explanation.</description>
      <section ref="C.8.5.5.1.14" name="">These attributes specify the location of the region, Region Location Min x0 (0018,6018), Region Location Min y0 (0018,601A), Region Location Max x1 (0018,601C), Region Location Max y1 (0018,601E) expressed as offsets to the pixel coordinates. The upper left corner of the entire image is x=0,y=0 and the lower right corner is x=image width - 1, and y=image length - 1. Thus, a region will be specified as within these bounds. Where x0,y0 is the coordinate of the upper left corner of the region and x1,y1 is the coordinate of the lower right corner of the region.
</section>
    </entry>
    <entry group="0018" element="601C" name="&gt;Region Location Max x1" type="1">
      <description>The bounds of a rectangle specifying the location of the region, x0,y0,x1,y1.
See C.8.5.5.1.14 for further explanation.</description>
      <section ref="C.8.5.5.1.14" name="">These attributes specify the location of the region, Region Location Min x0 (0018,6018), Region Location Min y0 (0018,601A), Region Location Max x1 (0018,601C), Region Location Max y1 (0018,601E) expressed as offsets to the pixel coordinates. The upper left corner of the entire image is x=0,y=0 and the lower right corner is x=image width - 1, and y=image length - 1. Thus, a region will be specified as within these bounds. Where x0,y0 is the coordinate of the upper left corner of the region and x1,y1 is the coordinate of the lower right corner of the region.
</section>
    </entry>
    <entry group="0018" element="601E" name="&gt;Region Location Max y1" type="1">
      <description>The bounds of a rectangle specifying the location of the region, x0,y0,x1,y1.
See C.8.5.5.1.14 for further explanation.</description>
      <section ref="C.8.5.5.1.14" name="">These attributes specify the location of the region, Region Location Min x0 (0018,6018), Region Location Min y0 (0018,601A), Region Location Max x1 (0018,601C), Region Location Max y1 (0018,601E) expressed as offsets to the pixel coordinates. The upper left corner of the entire image is x=0,y=0 and the lower right corner is x=image width - 1, and y=image length - 1. Thus, a region will be specified as within these bounds. Where x0,y0 is the coordinate of the upper left corner of the region and x1,y1 is the coordinate of the lower right corner of the region.
</section>
    </entry>
    <entry group="0018" element="6024" name="&gt;Physical Units X Direction" type="1">
      <description>The physical units of the dimensions of the region.
See C.8.5.5.1.15 for Enumerated Values.</description>
      <section ref="C.8.5.5.1.15" name="">Physical Units X Direction (0018,6024) and Physical Units Y Direction (0018,6026) provide Enumerated Values indicating the physical units of the dimensions of the region.
<enumerated-values><term value="Value" meaning="Meaning"/><term value="0000H" meaning="None or not applicable"/><term value="0002H" meaning="dB"/><term value="0004H" meaning="seconds"/><term value="0006H" meaning="dB/seconds"/><term value="0008H" meaning="cm2"/><term value="000AH" meaning="cm3"/><term value="000CH" meaning="degrees"/></enumerated-values>
         </section>
    </entry>
    <entry group="0018" element="6026" name="&gt;Physical Units Y Direction" type="1">
      <description>The physical units of the dimensions of the region.
See C.8.5.5.1.15 for Enumerated Values.</description>
      <section ref="C.8.5.5.1.15" name="">Physical Units X Direction (0018,6024) and Physical Units Y Direction (0018,6026) provide Enumerated Values indicating the physical units of the dimensions of the region.
<enumerated-values><term value="Value" meaning="Meaning"/><term value="0000H" meaning="None or not applicable"/><term value="0002H" meaning="dB"/><term value="0004H" meaning="seconds"/><term value="0006H" meaning="dB/seconds"/><term value="0008H" meaning="cm2"/><term value="000AH" meaning="cm3"/><term value="000CH" meaning="degrees"/></enumerated-values>
         </section>
    </entry>
    <entry group="0018" element="602C" name="&gt;Physical Delta X" type="1">
      <description>The physical value increments per positive X pixel increment. The units are as specified in the Physical Units X Direction (0018,6024).
See C.8.5.5.1.17 for further explanation.</description>
      <section ref="C.8.5.5.1.17" name="">The Physical Delta X (0018,602C) is the physical value increment per positive X pixel increment, which is left to right. The Physical Delta Y (0018,602E) is the physical value increment per positive Y pixel increment which is top to bottom.
Note:   When displaying Doppler data, ultrasound applications typically display the Doppler strip horizontally, with data sweeping (moving time origin) from left (oldest) to right (newest) or scrolling (static time origin) from right to left. The default display of positive velocity values normally indicates flow toward the transducer; negative velocity values indicate flow away from the transducer. In this case a negative Physical Delta Y is required to specify that the direction of positive velocities or frequencies is upward.

</section>
    </entry>
    <entry group="0018" element="602E" name="&gt;Physical Delta Y" type="1">
      <description>The physical value increments per positive Y pixel increment. The units are as specified in the Physical Units Y Direction (0018,6026).
See C.8.5.5.1.17 for further explanation.</description>
      <section ref="C.8.5.5.1.17" name="">The Physical Delta X (0018,602C) is the physical value increment per positive X pixel increment, which is left to right. The Physical Delta Y (0018,602E) is the physical value increment per positive Y pixel increment which is top to bottom.
Note:   When displaying Doppler data, ultrasound applications typically display the Doppler strip horizontally, with data sweeping (moving time origin) from left (oldest) to right (newest) or scrolling (static time origin) from right to left. The default display of positive velocity values normally indicates flow toward the transducer; negative velocity values indicate flow away from the transducer. In this case a negative Physical Delta Y is required to specify that the direction of positive velocities or frequencies is upward.

</section>
    </entry>
    <entry group="0018" element="6020" name="&gt;Reference Pixel x0" type="3">
      <description>This coordinate pair, x0,y0 defines the location of a virtual "reference" pixel.
See C.8.5.5.1.16 for further explanation.</description>
      <section ref="C.8.5.5.1.16" name="">This coordinate pair, Reference Pixel x0 (0018,6020), Reference Pixel y0 (0018,6022) defines the location of a virtual "reference" pixel. This reference pixel location is used to tie the image's pixel coordinate system to the physical coordinate system. For example, the reference pixel could be defined where a depth of zero centimeters occurs in the 2D image, or it could define where the baseline (i.e.: zero frequency) resides in a spectral display. The reference pixel location is the relative offset from the Region Location Min x0 (0018,6018) and Region Location Min y0 (0018,601A), not the image origin. The location is not required to be within the region or even within the image boundary. For this reason, the Reference Pixel x0 and Reference Pixel y0values can be positive or negative.
The reference pixel location varies depending on the type and spatial organization of the data within the region.
</section>
    </entry>
    <entry group="0018" element="6022" name="&gt;Reference Pixel y0" type="3">
      <description>This coordinate pair, x0,y0 defines the location of a virtual "reference" pixel.
See C.8.5.5.1.16 for further explanation.</description>
      <section ref="C.8.5.5.1.16" name="">This coordinate pair, Reference Pixel x0 (0018,6020), Reference Pixel y0 (0018,6022) defines the location of a virtual "reference" pixel. This reference pixel location is used to tie the image's pixel coordinate system to the physical coordinate system. For example, the reference pixel could be defined where a depth of zero centimeters occurs in the 2D image, or it could define where the baseline (i.e.: zero frequency) resides in a spectral display. The reference pixel location is the relative offset from the Region Location Min x0 (0018,6018) and Region Location Min y0 (0018,601A), not the image origin. The location is not required to be within the region or even within the image boundary. For this reason, the Reference Pixel x0 and Reference Pixel y0values can be positive or negative.
The reference pixel location varies depending on the type and spatial organization of the data within the region.
</section>
    </entry>
    <entry group="0018" element="6028" name="&gt;Ref. Pixel Physical Value X" type="3">
      <description>The Physical Value at the reference pixel x location. The units are specified in the Physical Units field.</description>
    </entry>
    <entry group="0018" element="602A" name="&gt;Ref. Pixel Physical Value Y" type="3">
      <description>The Physical Value at the reference pixel y location. The units are specified in the Physical Units field.</description>
    </entry>
    <entry group="0018" element="6012" name="&gt;Region Spatial Format" type="1">
      <description>The spatial organization of the data within the region.
See C.8.5.5.1.1 for Enumerated Values.</description>
      <section ref="C.8.5.5.1.1" name="">Enumerated Values for Region Spatial Format (0018,6012) indicate the spatial organization of the data within the region.
<enumerated-values><term value="Value Meaning" meaning="Value Meaning"/><term value="0000H None or not applicable" meaning="0001H 2D(tissue or flow)"/><term value="0002H M-Mode(tissue or flow)" meaning="0003H Spectral(CW or PW Doppler)"/><term value="0004H Wave form(physiological traces, doppler traces,....)" meaning="0005H Graphics"/></enumerated-values>
         </section>
    </entry>
    <entry group="0018" element="6014" name="&gt;Region Data Type" type="1">
      <description>The type of data within the region.
See C.8.5.5.1.2 for Enumerated Values.</description>
      <section ref="C.8.5.5.1.2" name="">Enumerated Values for Region Data Type (0018,6014) indicate the type of data within the region.
<enumerated-values><term value="Value Meaning" meaning="Value Meaning"/><term value="0000H None or not applicable" meaning="0001H Tissue"/><term value="0002H Color Flow" meaning="0003H PW Spectral Doppler"/><term value="0004H CW Spectral Doppler" meaning="0005H Doppler Mean Trace"/><term value="0006H Doppler Mode Trace" meaning="0007H Doppler Max Trace"/><term value="0008H Volume Trace" meaning="0009H d(volume)/dt Trace"/><term value="000AH ECG Trace" meaning="000BH Pulse Trace"/><term value="000CH Phonocardiogram Trace" meaning="000DH Gray bar"/><term value="000EH Color bar" meaning="000FH Integrated Backscatter"/><term value="0010H Area Trace" meaning="0011H d(area)/dt"/><term value="0012H&#9;Other Physiological (Amplitude vs. Time) input "/></enumerated-values>
         </section>
    </entry>
    <entry group="0018" element="6016" name="&gt;Region Flags" type="1">
      <description>Flags used for special handling of the region.
See C.8.5.5.1.3 for Enumerated Values and further explanation.</description>
      <section ref="C.8.5.5.1.3" name="">Region Flags (0018,6016) specify characteristics of US Regions.
Bit 0 of the Region Flags specifies the relative priority of the pixel component calibration specified by an US Region in the case where the US Region intersects with other US Regions. The calibration supplied by one or more of the regions may not be valid in the area that they intersect. Enumerated Values for Bit 0 (lsb):
  1 = Region pixels are low priority
  0 = Region pixels are high priority
A high priority region overwrites data of a low priority region when they overlap, thus invalidating any pixel component calibration specified for a low priority region. pixel component calibration of overlapping regions of the same priority is indeterminate where they overlap. Figure C.8-6 shows an example of intersecting regions.


Figure C.8-6
 Intersecting Spatial Format Regions and Overlapping Measurement
In this example, Region B is Color Flow while Region A is Tissue Echo. If Region B Color Flow values share the same bit planes as Region A Tissue Echo values, then it is indeterminate whether a pixel in this region is a Color Flow pixel or a Tissue Echo pixel. Since the pixels of the Color Flow region overwrite those of the Tissue Echo region, the Region Flag of the Tissue Echo region is assigned low priority and the Region Flag of the color region is assigned high priority. This means that if both the Tissue Echo and Color Flow regions define pixel component calibration that only the calibration specified by the Color Flow region can be applied to the pixel data value at Point X.
The measurement in Figure C.8-6 is a line between Point Y and Point Z. Both points are in Region A so the distance between them can be calculated using the Region A scaling (assuming that Region A defines both the Physical Units X Direction and Y Direction as being cm). If the points are in Region B, and hence also in Region A, it is still possible to calculate the distance because the region scaling is identical in both regions. The lower priority of Region B only applies to its pixel component calibration, not its X and Y direction scaling.
Enumerated Values for Bit 1 Scaling Protection:
  1 = Protected
  0 = Not Protected
Ultrasound systems should set this to 1 if the image is scaled automatically by the ultrasound system. If the image is frame-grabbed and scaling is not available then it should be set to 0. If the region is protected, the region can not be manually rescaled. That is the data defined by the region calibration Module can not be overridden by a reader of that image.
Enumerated Values for Bit 2 Doppler Scale Type:
  1 = Frequency
  0 = Velocity

Valid for PW and CW regions only. Indicates which type of Doppler scale is used.
Enumerated Values for Bit 3-4 Scrolling Region:
  00 = Unspecified
  01 = Scrolling
  10 = Sweeping
11 = Sweeping then Scrolling

Bit 5-31 Reserved for future use, shall be set to zero.
</section>
    </entry>
    <entry group="0018" element="6044" name="&gt;Pixel Component Organization" type="1C">
      <description>Describes how the components of a pixel can be described. Required if pixel component calibration exists for this region.
See C.8.5.5.1.4 for Enumerated Values and further explanation.</description>
      <section ref="C.8.5.5.1.4" name="">Pixel Component Organization (0018,6044) provides an Enumerated Value describing how the components of a pixel can be described. The absence of this data element means that pixel component calibration does not exist for this region. Where:
0 = Bit aligned positions
1 = Ranges
2 = Table look up
3 = Code Sequence look up
Other values reserved for future use.
Pixel Component Organization defines the way in which the composite pixel values are mapped into real world values with physical units, as illustrated in Figure C.8-7.

Figure C.8-7
Pixel Component Calibration
An example of Component Calibration for an ultrasound image is shown in Figure C.8-8.

Figure C.8-8
Pixel Component Calibration Example
In this example, some pixels lie within two Regions. One Region specifies pixel component calibration for Doppler velocity values. The second Region specifies pixel component calibration for Doppler magnitude. A particular Pixel Data (7FE0,0010) value will thus map to a displayed value, a Doppler velocity and magnitude value.
The example has a Palette Color Photometric Interpretation with 16 Bits Allocated and Bits Stored per sample. The Palette Color Lookup Tables also have 16 bits for each entry. The fact that the example has just one sample per pixel means that each composite pixel value is identical to the single Pixel Data value. An example Pixel Data value is shown in brackets along with the output values resulting from each step where it is processed.
The Pixel Data value is mapped to red, green, and blue values from the supplied Palette Color Lookup Tables before being displayed. The display device supports 8 bits per sample and thus requires the scaling of the output values from the 16 bit per entry LUTs.
The Doppler Velocity Region maps each pixel value in the Region to the Doppler velocity. The Pixel Component Organization (0018,6044) has a value of zero, indicating bit aligned positions with a bit mask. The Pixel Component Mask (0018,6046) specifies that the least significant 4 bits of the most significant byte convey the Doppler velocity of each pixel. The Pixel Component Physical Units (0018,604C) are cm/sec, and the Pixel Component Data Type (0018,604E) indicates color flow velocity. The Table of X Break Points (0018,6052) and Table of Y Break Points (0018,6054) map each masked composite pixel value to a Doppler velocity value in cm/sec.
The Doppler Magnitude Region maps each pixel value in the Region to the Doppler magnitude. The Pixel Component Organization (0018,6044) has a value of zero, indicating bit aligned positions with a bit mask. The Pixel Component Mask (0018,6046) specifies that the most significant 4 bits of the most significant byte convey the Doppler magnitude of each pixel. The Pixel Component Physical Units (0018,604C) is set to dB, and the Pixel Component Data Type (0018,604E) indicates color flow magnitude. The Table of X Break Points (0018,6052) and Table of Y Break Points (0018,6054) map each masked composite pixel value to a Doppler magnitude value in dB.
</section>
    </entry>
    <entry group="0018" element="6046" name="&gt;Pixel Component Mask" type="1C">
      <description>This value is ANDed with the composite pixel code for each pixel within the region, then shifted right by the number of contiguous least significant zeros in the mask to obtain what will be referred to as the "Shifted Masked Composite Pixel Code" (SMCPC). Required if Pixel Component Organization = Bit aligned.
See C.8.5.5.1.5 for further explanation.</description>
      <section ref="C.8.5.5.1.5" name="">Pixel Component Mask (0018,6046) is ANDed with the Composite Pixel Code (see Section C.7.6.3.1.1) for each pixel within the region, then shifted right by the number of contiguous least significant zeros in the mask to obtain what will be referred to as the "Shifted Masked Composite Pixel Code".
The mask will most likely (but not necessarily) contain a block of contiguous ones, surrounded by leading and trailing zeros. The purpose of this mask is to keep only those bits within the composite pixel code that pertain to the region. It is to be used only when Pixel Organization is bit aligned positions.
</section>
    </entry>
    <entry group="0018" element="6048" name="&gt;Pixel Component Range Start" type="1C">
      <description>Defines the start of the numeric range of values within the composite pixel where calibration is to be defined by the "pixel physical calibration table". To be used only when ranges are used to describe the portion of the composite pixel.
Required if Pixel Component Organization = Ranges.</description>
    </entry>
    <entry group="0018" element="604A" name="&gt;Pixel Component Range Stop" type="1C">
      <description>Defines the stop of the numeric range of values within the composite pixel where calibration is to be defined by the "pixel physical calibration table". To be used only when ranges are used to describe the portion of the composite pixel.
Required if Pixel Component Organization = Ranges.</description>
    </entry>
    <entry group="0018" element="604C" name="&gt;Pixel Component Physical Units" type="1C">
      <description>The physical units to be applied to the pixel component.
Required if Pixel Component Organization exists.
See C.8.5.5.1.6 for further explanation.</description>
      <section ref="C.8.5.5.1.6" name="">For Pixel Component Physical Units (0018,604C), the Enumerated Values describing the physical units to be applied to the pixel component are:
<enumerated-values><term value="Value Meaning" meaning="Value Meaning"/><term value="0000H None or not applicable" meaning="0001H Percent"/><term value="0002H dB" meaning="0003H cm"/><term value="0004H seconds" meaning="0005H hertz(seconds-1)"/><term value="0006H dB/seconds" meaning="0007H cm/sec"/><term value="0008H cm2" meaning="0009H cm2/sec"/><term value="000AH cm3" meaning="000BH cm3/sec"/><term value="000CH&#9;degrees"/></enumerated-values>
         </section>
    </entry>
    <entry group="0018" element="604E" name="&gt;Pixel Component Data Type" type="1C">
      <description>The type of data for the pixel component.
Required if Pixel Component Organization exists.
See C.8.5.5.1.7 for further explanation.</description>
      <section ref="C.8.5.5.1.7" name="">For Pixel Component Data Type (0018,604E), the Enumerated Values indicating the type of data for the pixel component are:
<enumerated-values><term value="Value Meaning" meaning="Value Meaning"/><term value="0000H None or not applicable" meaning="0001H Tissue"/><term value="0002H Spectral doppler" meaning="0003H Color Flow Velocity"/><term value="0004H Color Flow Variance" meaning="0005H Color Flow Intensity"/><term value="0006H Gray bar" meaning="0007H Color bar"/><term value="0008H Integrated Backscatter" meaning="0009H Computed Border"/></enumerated-values>000AH  Tissue Classification
</section>
    </entry>
    <entry group="0018" element="6050" name="&gt;Number of Table Break Points" type="1C">
      <description>The number of break point coordinate pairs used to describe a piece wise linear curve.
Required if Pixel Component Organization equals 0 or 1. Otherwise not used.
See C.8.5.5.1.8 for further explanation.</description>
      <section ref="C.8.5.5.1.8" name="">The Number of Table Break Points (0018,6050) gives the number of entries in each of two tables: the Table of X Break Points (0018,6052) and Table of Y Break Points (0018,6054). These tables are used to designate a curve mapping the value of a pixel component to its actual physical value, as described in Section C.8.5.5.1.9.
</section>
    </entry>
    <entry group="0018" element="6052" name="&gt;Table of X Break Points" type="1C">
      <description>An array of X values used to create the piece wise linear curve.
Required if Pixel Component Organization equals 0 or 1. Otherwise not used.
See C.8.5.5.1.9 for further explanation.</description>
      <section ref="C.8.5.5.1.9" name="">Table of X Break Points (0018,6052) and Table of Y Break Points (0018,6054) are individual arrays of coordinates which interpreted together are used to create a piecewise linear curve. Each X value from the Table of X Break Points is matched with the corresponding Y value from the Table of Y Break Points yielding an (X,Y) coordinate. The set of (X,Y) coordinates describes a piecewise linear curve mapping the value of a pixel component to its actual physical value (in units defined in Pixel Component Physical Units data element (0018,604C) ).
The X direction on the curve has no units, and represents actual pixel component values. If the Pixel Component Organization (0018,6044) is "Bit aligned positions", and the width of the Pixel Component Mask is n bits then the X coordinates are in the range 0 through 2n -1. If the Pixel Component Organization is Ranges, then the X coordinates are in the range 0 through 2 number of bits in the composite pixel - 1.
Note:  The X value is NOT relative to the Pixel Component Range Start (0018,6048). Not all possible X values in the range need be covered by the curve.
For any pixel component value in the range of the curve described by this table, the corresponding Y value is the actual physical value for that pixel, in units specified in the Pixel Component Physical Units data element (0018,604C). If the pixel component value is NOT within the range of specified X values for the curve, then no pixel calibration is defined by this region. It may be possible for pixel calibration to be defined by other spatial regions intersecting this one.
</section>
    </entry>
    <entry group="0018" element="6054" name="&gt;Table of Y Break Points" type="1C">
      <description>An array of Y values used to create the piece wise linear curve.
Required if Pixel Component Organization equals 0 or 1. Otherwise not used.
See C.8.5.5.1.9 for further explanation.</description>
      <section ref="C.8.5.5.1.9" name="">Table of X Break Points (0018,6052) and Table of Y Break Points (0018,6054) are individual arrays of coordinates which interpreted together are used to create a piecewise linear curve. Each X value from the Table of X Break Points is matched with the corresponding Y value from the Table of Y Break Points yielding an (X,Y) coordinate. The set of (X,Y) coordinates describes a piecewise linear curve mapping the value of a pixel component to its actual physical value (in units defined in Pixel Component Physical Units data element (0018,604C) ).
The X direction on the curve has no units, and represents actual pixel component values. If the Pixel Component Organization (0018,6044) is "Bit aligned positions", and the width of the Pixel Component Mask is n bits then the X coordinates are in the range 0 through 2n -1. If the Pixel Component Organization is Ranges, then the X coordinates are in the range 0 through 2 number of bits in the composite pixel - 1.
Note:  The X value is NOT relative to the Pixel Component Range Start (0018,6048). Not all possible X values in the range need be covered by the curve.
For any pixel component value in the range of the curve described by this table, the corresponding Y value is the actual physical value for that pixel, in units specified in the Pixel Component Physical Units data element (0018,604C). If the pixel component value is NOT within the range of specified X values for the curve, then no pixel calibration is defined by this region. It may be possible for pixel calibration to be defined by other spatial regions intersecting this one.
</section>
    </entry>
    <entry group="0018" element="6056" name="&gt;Number of Table Entries" type="1C">
      <description>The number of entries in the Table of Pixel Values.
Required if the value of Pixel Component Organization (0018,6044) is 2 or 3.
Otherwise not used. See C.8.5.5.1.11 for further explanation.</description>
      <section ref="C.8.5.5.1.11" name="">The Number of Table Entries (0018,6056) gives the number of entries in the Table of Pixel Values, the number of entries in the Table of Parameter Values (0018,605A), if present, and the number of items in the Pixel Value Mapping Code Sequence (0040,9098) , if present.
</section>
    </entry>
    <entry group="0018" element="6058" name="&gt;Table of Pixel Values" type="1C">
      <description>A table of Pixel Values used in conjunction with the Table of Parameter Values (0018,605A) or Pixel Value Mapping Code Sequence (0040,9098) to provide a mapping from Pixel Value to a real world value.
Required if the Pixel Component Organization equals 2. Otherwise not used.
See C.8.5.5.1.12 for further explanation.</description>
      <section ref="C.8.5.5.1.12" name="">The Table of Pixel Values (0018,6058) specifies the pixel values that are mapped to real world parameter values or coded concepts (tissue characterizations). The number of entries in the table is given by Number of Table Entries (0018,6056).
A pixel is calibrated (mapped to a real-world value) by finding an entry in the Table of Pixel Values that matches its Composite Pixel Code (see Section C.7.6.3.1.1). The offset index of this entry is used as an index into the Parameter Value Table (0018,605A) or as a sequence item number in the Pixel Value Mapping Code Sequence (0040,9098) to select the real world value. The first Table of Pixel Values entry corresponds to sequence item 1.
Note:  If a Composite Pixel Code has no matching value in the Pixel Value Table then there is no unambiguous way to determine the corresponding Parameter Value. A method may exist to determine a valid Parameter Value but the specification of such a method is outside the scope of the DICOM standard. No assumption should be made that linear interpolation will produce a valid result.

</section>
    </entry>
    <entry group="0018" element="605A" name="&gt;Table of Parameter Values" type="1C">
      <description>A table of Parameter Values used in conjunction with the Table of Pixel Values (0018,6058) to provide a mapping from Pixel Value to Parameter Value.
Required if the value of Pixel Component Organization (0018,6044) is 2.
Otherwise not used. See C.8.5.5.1.13 for further explanation</description>
      <section ref="C.8.5.5.1.13" name="">The Table of Parameter Values (0018,605A) provides the real world values for pixel values identified in the Table of Pixel Values (0018,6058). The number of table entries is given by Number of Table Entries (0018,6056) and the physical units are given by Pixel Component Physical Units (0018,604C). Values may repeat when a parameter value is associated with more than one Composite Pixel Code value.
</section>
    </entry>
    <entry group="0040" element="9098" name="&gt; Pixel Value Mapping Code Sequence" type="1C">
      <description>Sequence that, in conjunction with the Table of Pixel Values (0018,6058), provides a mapping from a Pixel Value to an associated Coded Concept. One or more Items shall be present; the number of Items shall be equal to the value of Number of Table Entries (0018,6056).
Required if the value of Pixel Component Organization (0018,6044) is 3 (Code Sequence look up).
See Sections C.8.5.6.1.18 for further explanation.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID for IVUS is 3497; no Context ID is otherwise defined."/>
    <entry group="0018" element="6030" name="&gt;Tranducer Frequency" type="3">
      <description>The manufacturer defined description of center frequency of the interrogating ultrasound energy. The units are kilohertz.</description>
    </entry>
    <entry group="0018" element="6032" name="&gt;Pulse Repetition Frequency" type="3">
      <description>The ultrasound pulse repetition frequency, as defined by the manufacturer, used to collect data in the region. The units are in hertz.</description>
    </entry>
    <entry group="0018" element="6034" name="&gt;Doppler Correction Angle" type="3">
      <description>The Doppler correction angle. The units are degrees.</description>
    </entry>
    <entry group="0018" element="6036" name="&gt;Steering Angle" type="3">
      <description>The steering angle, as defined by the manufacturer, used for a steered 2D image. The units are degrees.</description>
    </entry>
    <entry group="0018" element="6039" name="&gt;Doppler Sample Volume X Position" type="3">
      <description>The x displacement, in pixels, from the Reference pixel to the center of the Doppler sample volume.</description>
    </entry>
    <entry group="0018" element="603B" name="&gt;Doppler Sample Volume Y Position" type="3">
      <description>The y displacement, in pixels, from the Reference pixel to the center of the Doppler sample volume.</description>
    </entry>
    <entry group="0018" element="603D" name="&gt;TM-Line Position x0" type="3">
      <description>The starting and ending coordinates pairs of the m-line. Where the X0,Y0 are the starting point and X1,Y1 are the end point of the tm-line.
See C.8.5.5.1.10 for further explanation.</description>
      <section ref="C.8.5.5.1.10" name="">  TM-Line Position X1 ,TM-Line Position Y1
The TM-Line Position X0 (0018,603D) and TM-Line Position Y0 (0018,603F) are the coordinates of the starting point and TM-Line Position X1 (0018,6041), TM-Line Position Y1 (0018,6043) are the coordinates of the end point of the TM-line. The coordinate is defined as the displacement, in pixels, from the Reference pixel. Typically used for M-mode line and CW Doppler.
</section>
    </entry>
    <entry group="0018" element="603F" name="&gt;TM-Line Position y0" type="3">
      <description>The starting and ending coordinates pairs of the m-line. Where the X0,Y0 are the starting point and X1,Y1 are the end point of the tm-line.
See C.8.5.5.1.10 for further explanation.</description>
      <section ref="C.8.5.5.1.10" name="">  TM-Line Position X1 ,TM-Line Position Y1
The TM-Line Position X0 (0018,603D) and TM-Line Position Y0 (0018,603F) are the coordinates of the starting point and TM-Line Position X1 (0018,6041), TM-Line Position Y1 (0018,6043) are the coordinates of the end point of the TM-line. The coordinate is defined as the displacement, in pixels, from the Reference pixel. Typically used for M-mode line and CW Doppler.
</section>
    </entry>
    <entry group="0018" element="6041" name="&gt;TM-Line Position x1" type="3">
      <description>The starting and ending coordinates pairs of the m-line. Where the X0,Y0 are the starting point and X1,Y1 are the end point of the tm-line.
See C.8.5.5.1.10 for further explanation.</description>
      <section ref="C.8.5.5.1.10" name="">  TM-Line Position X1 ,TM-Line Position Y1
The TM-Line Position X0 (0018,603D) and TM-Line Position Y0 (0018,603F) are the coordinates of the starting point and TM-Line Position X1 (0018,6041), TM-Line Position Y1 (0018,6043) are the coordinates of the end point of the TM-line. The coordinate is defined as the displacement, in pixels, from the Reference pixel. Typically used for M-mode line and CW Doppler.
</section>
    </entry>
    <entry group="0018" element="6043" name="&gt;TM-Line Position y1" type="3">
      <description>The starting and ending coordinates pairs of the m-line. Where the X0,Y0 are the starting point and X1,Y1 are the end point of the tm-line.
See C.8.5.5.1.10 for further explanation.</description>
      <section ref="C.8.5.5.1.10" name="">  TM-Line Position X1 ,TM-Line Position Y1
The TM-Line Position X0 (0018,603D) and TM-Line Position Y0 (0018,603F) are the coordinates of the starting point and TM-Line Position X1 (0018,6041), TM-Line Position Y1 (0018,6043) are the coordinates of the end point of the TM-line. The coordinate is defined as the displacement, in pixels, from the Reference pixel. Typically used for M-mode line and CW Doppler.
</section>
    </entry>
  </module>
  <module ref="C.8.5.6" table="C.8-18" name="US Image Module Attributes">
    <entry group="0028" element="0002" name="Samples Per Pixel" type="1">
      <description>Number of samples (planes) in this image.
See C.8.5.6.1.12 for specialization</description>
      <section ref="C.8.5.6.1.12" name="">For US Images, Samples Per Pixel (0028,0002) is specified to use the following values for specific Photometric Interpretations:
Table C.8-19
US SAMPLES PER PIXEL
<unrecognized-rows><term value="Photometric Interpretation" meaning="Samples Per Pixel Value"/><term value="MONOCHROME2" meaning="1"/><term value="RGB" meaning="3"/><term value="YBR_FULL" meaning="3"/><term value="YBR_FULL_422" meaning="3"/><term value="YBR_PARTIAL_422" meaning="3"/><term value="YBR_RCT" meaning="3"/><term value="YBR_ICT" meaning="3"/><term value="YBR_PARTIAL_420" meaning="3"/><term value="PALETTE COLOR" meaning="1"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data.
See C.8.5.6.1.2 for specialization.</description>
      <section ref="C.8.5.6.1.2" name="">For US Images, Photometric Interpretation (0028,0004) is specified to use the following Defined Terms:
<defined-terms><term value="MONOCHROME2"/><term value="PALETTE COLOR"/><term value="RGB"/><term value="ARGB (retired)"/><term value="YBR_FULL"/><term value="YBR_FULL_422"/><term value="YBR_PARTIAL_422"/><term value="YBR_RCT"/><term value="YBR_ICT"/><term value="YBR_PARTIAL_420"/><term value=""/><term value=""/></defined-terms>
Note:  It is recommended that future implementations should not use ARGB photometric interpretation.

See PS 3.5 for restrictions imposed by compressed Transfer Syntaxes.
</section>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample.
See C.8.5.6.1.13 for specialization.</description>
      <section ref="C.8.5.6.1.13" name="">For US Images, Bits Allocated (0028,0100) is specified to use the following values for specific Photometric Interpretations:
Table C.8-20
US BITS ALLOCATED
<unrecognized-rows><term value="Photometric Interpretation" meaning="Bits Allocated Value"/><term value="MONOCHROME2" meaning="8"/><term value="RGB" meaning="8"/><term value="YBR_FULL" meaning="8"/><term value="YBR_FULL_422" meaning="8"/><term value="YBR_PARTIAL_422" meaning="8"/><term value="YBR_RCT" meaning="8"/><term value="YBR_ICT" meaning="8"/><term value="YBR_PARTIAL_420" meaning="8"/><term value="PALETTE COLOR" meaning="8 - 8 bit palette, or"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample.
See C.8.5.6.1.14 for specialization.</description>
      <section ref="C.8.5.6.1.14" name="">For US Images, Bits Stored (0028,0101) is specified to use the following values for specific Photometric Interpretations:
Table C.8-21
US BITS STORED
<unrecognized-rows><term value="Photometric Interpretation" meaning="Bits Stored Value"/><term value="MONOCHROME2" meaning="8"/><term value="RGB" meaning="8"/><term value="YBR_FULL" meaning="8"/><term value="YBR_FULL_422" meaning="8"/><term value="YBR_PARTIAL_422" meaning="8"/><term value="YBR_RCT" meaning="8"/><term value="YBR_ICT" meaning="8"/><term value="YBR_PARTIAL_420" meaning="8"/><term value="PALETTE COLOR" meaning="8 - 8 bit palette, or"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data.
See C.8.5.6.1.15 for specialization.</description>
      <section ref="C.8.5.6.1.15" name="">For US Images, High Bit (0028,0102) is specified to use the following values for specific Photometric Interpretations:
Table C.8-22
US HIGH BIT
<unrecognized-rows><term value="Photometric Interpretation" meaning="High Bit Value"/><term value="MONOCHROME2" meaning="7"/><term value="RGB" meaning="7"/><term value="YBR_FULL" meaning="7"/><term value="YBR_FULL_422" meaning="7"/><term value="YBR_PARTIAL_422" meaning="7"/><term value="YBR_RCT" meaning="7"/><term value="YBR_ICT" meaning="7"/><term value="YBR_PARTIAL_420" meaning="7"/><term value="PALETTE COLOR" meaning="7 - 8 bit palette, or"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0006" name="Planar Configuration" type="1C">
      <description>Indicates whether the pixel data are sent color-by-plane or color-by-pixel.
Required if Samples per Pixel (0028,0002) has a value greater than 1.
See C.8.5.6.1.16 for specialization.</description>
      <section ref="C.8.5.6.1.16" name="">For US Images, Planar Configuration (0028,0006) is specified to use the following values for specific Photometric Interpretations:
Table C.8-23
US PLANAR CONFIGURATION
<unrecognized-rows><term value="Photometric Interpretation" meaning="Planar Configuration Value"/><term value="RGB" meaning="0 - color-by-pixel, or"/><term value="YBR_FULL" meaning="1"/><term value="YBR_FULL_422" meaning="0"/><term value="YBR_PARTIAL_422" meaning="0"/><term value="YBR_RCT" meaning="0"/><term value="YBR_ICT" meaning="0"/><term value="YBR_PARTIAL_420" meaning="0"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0103" name="Pixel Representation" type="1">
      <description>Data representation of pixel samples.
See C.8.5.6.1.3 for specialization.</description>
      <section ref="C.8.5.6.1.3" name="">For US Images, Pixel Representation (0028,0103) is specified to use the following Enumerated Value:
0000H = unsigned integer
</section>
    </entry>
    <entry group="0028" element="0009" name="Frame Increment Pointer" type="1C">
      <description>Contains the Data Element Tag of the attribute which is used as the frame increment in Multi-frame pixel data (see C.7.6.6). Required if Number of Frames is sent.
See C.8.5.6.1.4 for specialization.</description>
      <section ref="C.8.5.6.1.4" name="">For US Multi-frame images, the Attribute Frame Increment Pointer (0028,0009) of the Multi-frame Module (see Section C.7.6.6) is specified by the following Defined Terms:
00181063 = sequencing by Frame Time (0018,1063)
00181065 = sequencing by Frame Time Vector (0018,1065)
</section>
    </entry>
    <entry group="0008" element="0008" name="Image Type" type="2">
      <description>Image identification characteristics.
See C.8.5.6.1.1 for specialization.</description>
      <section ref="C.8.5.6.1.1" name="">For US Images, Image Type (0008,0008) is specified to be Type 2. The Defined Terms for Value 3 are:
<defined-terms><term value="ABDOMINAL"/><term value="BREAST"/><term value="CHEST"/><term value="ENDOCAVITARY"/><term value="ENDORECTAL"/><term value="ENDOVAGINAL"/><term value="EPICARDIAL"/><term value="FETAL HEART"/><term value="GYNECOLOGY"/><term value="INTRACARDIAC"/><term value="INTRAOPERATIVE"/><term value="INTRAVASCULAR"/><term value="MUSCULOSKELETAL"/><term value="NEONATAL HEAD"/><term value="OBSTETRICAL"/><term value="OPHTHALMIC"/><term value="PEDIATRIC"/><term value="PELVIC"/><term value="RETROPERITONEAL"/><term value="SCROTAL"/><term value="SMALL PARTS"/><term value="TEE"/><term value="THYROID"/><term value="TRANSCRANIAL"/><term value="TTE"/><term value="US BIOPSY"/><term value="VASCULAR"/></defined-terms>
Value 4 is constructed as a modality bit map to allow for a description of multi-modality displays. In using this bit map, the sum of the values of the various modalities will unambiguously determine the constituent modalities.
<unrecognized-rows><term value="0001 = 2D Imaging"/><term value="0002 = M-Mode"/><term value="0004 = CW Doppler"/><term value="0008 = PW Doppler"/><term value="0010 = Color Doppler"/><term value="0020 = Color M-Mode"/><term value="0040 = 3D Rendering"/><term value="0100 = Color Power Mode"/><term value="0200 = Tissue Characterization"/></unrecognized-rows>
Notes:  1. All Values are hexadecimal encoded as a CS. See PS 3.5.
  2. For example, Color Flow with CW spectral Doppler would have a value 4 = 0015. Note that no assumption should be made in Color Doppler or Color M-Mode regarding underlying B or M-Mode, respectively.

</section>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1C">
      <description>Specifies whether an Image has undergone lossy compression. Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5
Required if Lossy Compression has been performed on the Image.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0008" element="2124" name="Number of Stages" type="2C">
      <description>Number of Stages in this protocol. Required if image was acquired in a Staged protocol.</description>
    </entry>
    <entry group="0008" element="212A" name="Number of Views in Stage" type="2C">
      <description>Number of views in this Stage. Required if image was acquired in a Staged protocol.</description>
    </entry>
    <entry group="0018" element="6060" name="R Wave Time Vector" type="3">
      <description>The time offset(s) of the reported R Wave peaks, each relative to the time of the start of the acquisition of the first frame in msec. Multi-valued, with one value per reported R Wave.</description>
    </entry>
    <entry group="0028" element="0014" name="Ultrasound Color Data Present" type="3">
      <description>This element indicates if any ultrasound color data is present in an image. Enumerated Values:
00 = Ultrasound color data not present in image
01 = Ultrasound color data is present in image.
See C.8.5.6.10</description>
    </entry>
    <entry group="0008" element="2120" name="Stage Name" type="3">
      <description>A Stage is a particular time slice of a protocol in which a set of images are collected. The names can be free form text. Recommended text for Stress Echo stage names are:
PRE-EXERCISE,
POST-EXERCISE,
PEAK-EXERCISE,
RECOVERY,
BASELINE,
LOW DOSE,
PEAK DOSE</description>
    </entry>
    <entry group="0040" element="000A" name="Stage Code Sequence" type="3">
      <description>Sequence of items describing the performed Ultrasound Protocol Stage(s). One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include “Code Sequence Macro” Table 8.8-1." description="Baseline Context ID is 12002."/>
    <entry group="0008" element="2122" name="Stage Number" type="3">
      <description>A number that identifies the Stage. Stage Number starts at one.</description>
    </entry>
    <entry group="0008" element="2127" name="View Name" type="3">
      <description>A View is a particular combination of the position and orientation when a set of images are acquired. Images are acquired at the same View in different Stages for the purpose of comparison.</description>
    </entry>
    <entry group="0008" element="2128" name="View Number" type="3">
      <description>A number that identifies the View. View Number starts at one.</description>
    </entry>
    <entry group="0008" element="2129" name="Number of Event Timers" type="3">
      <description>The number of event timers used at the time of acquisition of a Multi-frame image.</description>
    </entry>
    <entry group="0008" element="2130" name="Event Elapsed Time(s)" type="3">
      <description>An array of values associated with each event timer. Units in milliseconds.</description>
    </entry>
    <entry group="0008" element="2132" name="Event Timer Name(s)" type="3">
      <description>Name that identifies the event timer.</description>
    </entry>
    <include ref="Include 'General Anatomy Optional Macro' Table 10-7" description="For intravascular ultrasound, DCIDs 3010 and 3015 are specified for the Anatomic Region Sequence and DCID 3019 is specified for the Anatomic Region Modifier Sequence. No other Context IDs are specified."/>
    <entry group="0054" element="0220" name="View Code Sequence" type="3">
      <description>Sequence that describes the view of the patient anatomy in this image.
Only a single Item shall be permitted in this Sequence.
See Section C.8.5.6.1.19.</description>
      <section ref="C.8.5.6.1.19" name="">The view of the patient anatomy may be described using coded terminology in the View Code Sequence (0054,0220). The view is typically specified by transducer position relative to the patient anatomy and/or transducer orientation,
The view may be described by a single Code Sequence Item, or by combination of post-coordinated Code Sequence Items. The principal coded item is specified in View Code Sequence, and modifier terms in the View Modifier Code Sequence (0054,0222). The Baseline Context IDs for post-coordinated encoding of view are:
</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="See Section C.8.5.6.1.19 for Context Group IDs."/>
    <entry group="0054" element="0222" name="&gt;View Modifier Code Sequence" type="3">
      <description>Sequence that provides modifiers for the view of the patient anatomy.
Zero or more Items shall be permitted in this Sequence.
See Section C.8.5.6.1.19.</description>
      <section ref="C.8.5.6.1.19" name="">The view of the patient anatomy may be described using coded terminology in the View Code Sequence (0054,0220). The view is typically specified by transducer position relative to the patient anatomy and/or transducer orientation,
The view may be described by a single Code Sequence Item, or by combination of post-coordinated Code Sequence Items. The principal coded item is specified in View Code Sequence, and modifier terms in the View Modifier Code Sequence (0054,0222). The Baseline Context IDs for post-coordinated encoding of view are:
</section>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="See Section C.8.5.6.1.19 for Context Group IDs."/>
    <entry group="0008" element="002A" name="Acquisition DateTime" type="1C">
      <description>The date and time that the acquisition of data that resulted in this image started.
Required if Modality (0008,0060) = IVUS
May be present otherwise.
Note: The synchronization of this time with an external clock is specified in the Synchronization Module in Acquisition Time Synchronized (0018,1800).</description>
    </entry>
    <entry group="0018" element="1060" name="Trigger Time" type="3">
      <description>Time interval measured in msec from the start of the R-wave to the beginning of data taking</description>
    </entry>
    <entry group="0018" element="1062" name="Nominal Interval" type="3">
      <description>Average R-R interval used for these data, in msec</description>
    </entry>
    <entry group="0018" element="1080" name="Beat Rejection Flag" type="3">
      <description>Beat length sorting has been applied. Enumerated Values:
Y = yes
N = no</description>
    </entry>
    <entry group="0018" element="1081" name="Low R-R Value" type="3">
      <description>R-R interval low limit for beat rejection, in msec</description>
    </entry>
    <entry group="0018" element="1082" name="High R-R Value" type="3">
      <description>R-R interval high limit for beat rejection, in msec</description>
    </entry>
    <entry group="0018" element="1088" name="Heart Rate" type="3">
      <description>Beats per minute.</description>
    </entry>
    <entry group="0018" element="3100" name="IVUS Acquisition" type="1C">
      <description>Defined Terms:
MOTOR_PULLBACK
MANUAL_PULLBACK
SELECTIVE
GATED_PULLBACK
See C.8.5.6.1.21
Required if Modality (0008,0060) = IVUS</description>
      <section ref="C.8.5.6.1.21" name="">This attribute denotes which of the following defined terms describes the method used to acquire the IVUS Images.
MOTOR_PULLBACK: The IVUS imaging catheter is positioned in the blood vessel under examination distal to the anatomical structures to be examined. Then the catheter is attached to a motorized mechanism capable of withdrawing the catheter through the vessel at a constant velocity specified by the attribute IVUS Pullback Rate (0018,3101) from the defined IVUS Pullback Start Frame Number (0018,3103) (see C.8.5.6.1.24) to the IVUS Pullback Stop Frame Number (0018,3104) (see C.8.5.6.1.25).
MANUAL_PULLBACK: The IVUS imaging catheter is positioned in the blood vessel under examination distal to the anatomical structures to be examined. Then the catheter is manually withdrawn through the vessel region of interest.
SELECTIVE: The IVUS imaging catheter is positioned in the blood vessel under examination near the anatomical structures to be examined. Then the catheter is manually withdrawn or advanced through the vessel region of interest.
GATED_PULLBACK: The IVUS imaging catheter is positioned in the blood vessel under examination distal to the anatomical structures to be examined. Then the catheter is attached to a motorized mechanism capable of withdrawing the catheter through the vessel at a rate specified by the attribute IVUS Gated Rate (0018,3102), once per heart cycle, from the defined IVUS Pullback Start Frame Number (0018,3103) (see C.8.5.6.1.24) to the IVUS Pullback Stop Frame Number (0018,3104) (see C.8.5.6.1.25).
</section>
    </entry>
    <entry group="0018" element="3101" name="IVUS Pullback Rate" type="1C">
      <description>Required if IVUS Acquisition (0018,3100) value is MOTOR_PULLBACK. Specified in units of mm/sec.
See C.8.5.6.1.22</description>
      <section ref="C.8.5.6.1.22" name="">The attribute IVUS Pullback Rate (0018,3101) is required when IVUS Acquisition (0018,3100) is MOTOR_PULLBACK and it specifies the velocity of withdrawal of the IVUS imaging catheter in millimeters per second.
</section>
    </entry>
    <entry group="0018" element="3102" name="IVUS Gated Rate" type="1C">
      <description>Required if IVUS Acquisition (0018,3100) value is GATED_PULLBACK. Specified in units of mm/beat.
See C.8.5.6.1.23</description>
      <section ref="C.8.5.6.1.23" name="">The attribute IVUS Gated Rate (0018,3102) is required when IVUS Acquisition (0018,3100) is GATED_PULLBACK and it specifies the velocity of withdrawal of the IVUS imaging catheter in millimeters per beat.
</section>
    </entry>
    <entry group="0018" element="3103" name="IVUS Pullback Start Frame Number" type="1C">
      <description>Required if IVUS Acquisition (0018,3100) value is MOTOR_PULLBACK or GATED_PULLBACK.
See C.8.5.6.1.24</description>
      <section ref="C.8.5.6.1.24" name="">The IVUS Pullback Start Frame Number (0018,3103) specifies the frame number of a IVUS multi-frame acquisition upon which motorized or gated pullback begins.
</section>
    </entry>
    <entry group="0018" element="3104" name="IVUS Pullback Stop Frame Number" type="1C">
      <description>Required if IVUS Acquisition (0018,3100) value is MOTOR_PULLBACK or GATED_PULLBACK.
See C.8.5.6.1.25</description>
      <section ref="C.8.5.6.1.25" name="">The IVUS Pullback Stop Frame Number (0018,3104) specifies the frame number of a IVUS multi-frame acquisition upon which motorized or gated pullback ends.
</section>
    </entry>
    <entry group="0018" element="3105" name="Lesion Number" type="3">
      <description>Identifier(s) of the lesion(s) of interest imaged within the current SOP Instance. Each lesion shall have a unique numeric integer identifier within the study.
See C.8.5.6.1.26.</description>
      <section ref="C.8.5.6.1.26" name="">Attribute Lesion Number identifies the lesion(s) of interest imaged within the current SOP Instance. Each lesion shall have a unique numeric integer identifier within the study. If during a study the same lesion is imaged more than once, the same Lesion Number should be used for both SOP Instances.
Notes:   1.Lesion Number is not a DICOM UID.
  2.An IVUS pullback may contain multiple values in Lesion Number.

</section>
    </entry>
    <entry group="0018" element="5000" name="Output Power" type="3">
      <description>Manufacturer defined character string description of ultrasound output level(s) used in generating a given image. Data may be expressed in dB, %, W/cm2, etc.</description>
    </entry>
    <entry group="0018" element="5010" name="Transducer Data" type="3">
      <description>Manufacturer defined code or description of ultrasound transducer used.</description>
    </entry>
    <entry group="0018" element="6031" name="Transducer Type" type="3">
      <description>Defined Terms:
SECTOR_PHASED
SECTOR_MECH
SECTOR_ANNULAR
LINEAR
CURVED LINEAR
SINGLE CRYSTAL
SPLIT XTAL CWD
IV_PHASED
IV_ROT XTAL
IV_ROT MIRROR
ENDOCAV_PA
ENDOCAV_MECH
ENDOCAV_CLA
ENDOCAV_AA
ENDOCAV_LINEAR
VECTOR_PHASED</description>
    </entry>
    <entry group="0018" element="5012" name="Focus Depth" type="3">
      <description>The depth, from the transducer face, of the manufacturer defined beam focus used for the image, in cm.</description>
    </entry>
    <entry group="0018" element="5020" name="Processing Function" type="3">
      <description>Manufacturer defined description of processing of echo information. Data may include code or description of gain (initial, overall, TGC, dynamic range, etc.), preprocessing, postprocessing, Doppler processing parameters, e.g. cutoff filters, etc., as used in generating a given image.</description>
    </entry>
    <entry group="0018" element="5022" name="Mechanical Index" type="3">
      <description>See C.8.5.6.1.8 for Description.</description>
      <section ref="C.8.5.6.1.8" name="">The thermal and/or mechanical indices, when made available by a manufacturer, are defined according to the Standard for Real-Time Display of Thermal and Mechanical Acoustic Output Indices on Diagnostic Ultrasound Equipment, a voluntary performance standard jointly published by AIUM and NEMA.
</section>
    </entry>
    <entry group="0018" element="5024" name="Bone Thermal Index" type="3">
      <description>See C.8.5.6.1.8 for Description.</description>
      <section ref="C.8.5.6.1.8" name="">The thermal and/or mechanical indices, when made available by a manufacturer, are defined according to the Standard for Real-Time Display of Thermal and Mechanical Acoustic Output Indices on Diagnostic Ultrasound Equipment, a voluntary performance standard jointly published by AIUM and NEMA.
</section>
    </entry>
    <entry group="0018" element="5026" name="Cranial Thermal Index" type="3">
      <description>See C.8.5.6.1.8 for Description.</description>
      <section ref="C.8.5.6.1.8" name="">The thermal and/or mechanical indices, when made available by a manufacturer, are defined according to the Standard for Real-Time Display of Thermal and Mechanical Acoustic Output Indices on Diagnostic Ultrasound Equipment, a voluntary performance standard jointly published by AIUM and NEMA.
</section>
    </entry>
    <entry group="0018" element="5027" name="Soft Tissue Thermal Index" type="3">
      <description>See C.8.5.6.1.8 for Description.</description>
      <section ref="C.8.5.6.1.8" name="">The thermal and/or mechanical indices, when made available by a manufacturer, are defined according to the Standard for Real-Time Display of Thermal and Mechanical Acoustic Output Indices on Diagnostic Ultrasound Equipment, a voluntary performance standard jointly published by AIUM and NEMA.
</section>
    </entry>
    <entry group="0018" element="5028" name="Soft Tissue-focus Thermal Index" type="3">
      <description>See C.8.5.6.1.8 for Description.</description>
      <section ref="C.8.5.6.1.8" name="">The thermal and/or mechanical indices, when made available by a manufacturer, are defined according to the Standard for Real-Time Display of Thermal and Mechanical Acoustic Output Indices on Diagnostic Ultrasound Equipment, a voluntary performance standard jointly published by AIUM and NEMA.
</section>
    </entry>
    <entry group="0018" element="5029" name="Soft Tissue-surface Thermal Index" type="3">
      <description>See C.8.5.6.1.8 for Description.</description>
      <section ref="C.8.5.6.1.8" name="">The thermal and/or mechanical indices, when made available by a manufacturer, are defined according to the Standard for Real-Time Display of Thermal and Mechanical Acoustic Output Indices on Diagnostic Ultrasound Equipment, a voluntary performance standard jointly published by AIUM and NEMA.
</section>
    </entry>
    <entry group="0018" element="5050" name="Depth of Scan Field" type="3">
      <description>The depth, in mm, from the transducer face to the deepest point included in the displayed image- the field of view.</description>
    </entry>
    <entry group="60xx" element="0045" name="Overlay Subtype" type="3">
      <description>Defined term which identifies the intended purpose of the ROI Overlay Type.
See C.8.5.6.1.11 for specialization.</description>
      <section ref="C.8.5.6.1.11" name="">For US Images, Overlay Subtype (60xx,0045) shall use the following Defined Terms:
ACTIVE 2D/BMODE IMAGE AREA = identification of the active area of a 2D/B-mode image.
</section>
    </entry>
  </module>
  <module ref="C.8.6.1" table="C.8-24" name="SC Equipment Module Attributes">
    <entry group="0008" element="0064" name="Conversion Type" type="1">
      <description>Describes the kind of image conversion. Defined Terms :
DV = Digitized Video
DI = Digital Interface
DF = Digitized Film
WSD = Workstation
SD = Scanned Document
SI = Scanned Image
DRW = Drawing
SYN = Synthetic Image</description>
    </entry>
    <entry group="0008" element="0060" name="Modality" type="3">
      <description>Source equipment for the image. This type definition shall override the definition in the General Series Module.
See C.7.3.1.1.1 for Defined Terms.</description>
      <section ref="C.7.3.1.1.1" name="">Defined Terms for the Modality (0008,0060) are:
<defined-terms><term value="CR" meaning="Computed Radiography"/><term value="MR" meaning="Magnetic Resonance"/><term value="US" meaning="Ultrasound"/><term value="BI" meaning="Biomagnetic imaging"/><term value="DD" meaning="Duplex Doppler"/><term value="ES" meaning="Endoscopy"/><term value=""/><term value="PT" meaning="Positron emission tomography (PET)"/><term value="ST" meaning="Single-photon emission computed tomography (SPECT)"/><term value="XA" meaning="X-Ray Angiography"/><term value="RTIMAGE" meaning="Radiotherapy Image"/><term value="RTSTRUCT" meaning="Radiotherapy Structure Set"/><term value="RTRECORD" meaning="RT Treatment Record"/><term value="DX" meaning="Digital Radiography"/><term value="IO" meaning="Intra-oral Radiography"/><term value="GM" meaning="General Microscopy"/><term value="XC" meaning="External-camera Photography"/><term value="AU" meaning="Audio"/><term value="EPS" meaning="Cardiac Electrophysiology"/><term value="SR" meaning="SR Document"/><term value="OP" meaning="Ophthalmic Photography"/><term value="OCT" meaning="Optical Coherence Tomography (non-Ophthalmic)"/><term value="OPV" meaning="Ophthalmic Visual Field"/><term value="KO" meaning="Key Object Selection"/><term value="REG" meaning="Registration"/><term value="BDUS" meaning="Bone Densitometry (ultrasound)"/><term value="DOC" meaning="Document"/></defined-terms>
Retired Defined Terms for the Modality (0008,0060) are:
<retired-defined-terms><term value="DS" meaning="Digital Subtraction Angiography (retired)"/><term value="DF" meaning="Digital fluoroscopy (retired)"/><term value="AS" meaning="Angioscopy"/><term value="EC" meaning="Echocardiography"/><term value="FA" meaning="Fluorescein angiography"/><term value="DM" meaning="Digital microscopy"/><term value="MA" meaning="Magnetic resonance angiography"/></retired-defined-terms>
Note:  1. The XA modality incorporates the retired modality DS.
  2. The RF modality incorporates the retired modalities CF, DF, VF.
  3. The modality listed in the Modality Data Element (0008,0060) may not match the name of the IOD in which it appears. For example, a SOP instance from XA IOD may list the RF modality when an RF implementation produces an XA object.
  4. The MR modality incorporates the retired modalities MA and MS.

</section>
    </entry>
    <entry group="0018" element="1010" name="Secondary Capture Device ID" type="3">
      <description>User defined identification of the device that converted the image</description>
    </entry>
    <entry group="0018" element="1016" name="Secondary Capture Device Manufacturer" type="3">
      <description>Manufacturer of the Secondary Capture Device</description>
    </entry>
    <entry group="0018" element="1018" name="Secondary Capture Device Manufacturer's Model Name" type="3">
      <description>Manufacturer's model number of the Secondary Capture Device</description>
    </entry>
    <entry group="0018" element="1019" name="Secondary Capture Device Software Version" type="3">
      <description>Manufacturer's designation of software version of the Secondary Capture Device</description>
    </entry>
    <entry group="0018" element="1022" name="Video Image Format Acquired" type="3">
      <description>Original format of the captured video image (e.g. NTSC, PAL, Videomed-H)</description>
    </entry>
    <entry group="0018" element="1023" name="Digital Image Format Acquired" type="3">
      <description>Additional information about digital interface used to acquire the image</description>
    </entry>
  </module>
  <module ref="C.8.6.2" table="C.8-25" name="SC Image Module Attributes">
    <entry group="0018" element="1012" name="Date of Secondary Capture" type="3">
      <description>The date the Secondary Capture Image was captured.</description>
    </entry>
    <entry group="0018" element="1014" name="Time of Secondary Capture" type="3">
      <description>The time the Secondary Capture Image was captured.</description>
    </entry>
    <entry group="0018" element="2010" name="Nominal Scanned Pixel Spacing" type="3">
      <description>Physical distance on the media being digitized or scanned between the center of each pixel, specified by a numeric pair - adjacent row spacing (delimiter) adjacent column spacing in mm. See 10.7.1.3 for further explanation of the value order.
Shall be consistent with Pixel Aspect Ratio (0028,0034), if present.</description>
    </entry>
    <include ref="Include Basic Pixel Spacing Calibration Macro (Table 10-10)"/>
  </module>
  <module ref="C.8.6.3" table="C.8-25b" name="SC Multi Frame Image Module Attributes">
    <entry group="0028" element="0301" name="Burned In Annotation" type="1">
      <description>Indicates whether or not image contains sufficient burned in annotation to identify the patient and date the image was acquired.
Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="2050" element="0020" name="Presentation LUT Shape" type="1C">
      <description>Specifies an identity transformation for the Presentation LUT, such that the output of all grayscale transformations defined in the IOD containing this Module are defined to be P-Values.
Enumerated Values:
IDENTITY - output is in P-Values.
Required if Photometric Interpretation (0028,0004) is MONOCHROME2, and BitsStored (0028,0101) is greater than 1.
Note: If the VOI LUT Module is required by the IOD but no VOI LUT Sequence (0028,3010) or Window Center (0028,1050) is present, then the VOI LUT stage is an identity transformation.</description>
    </entry>
    <entry group="2010" element="015E" name="Illumination" type="3">
      <description>Luminance of a hypothetical viewing device illuminating a piece of monochrome transmissive film, or for the case of reflective media, luminance obtainable from diffuse reflection of the illumination present. Expressed as L0, in candelas per square meter (cd/m2).
Note: May be used together with Reflected Ambient Light (2010,0160) to recover Optical Density information from P-Values. See C.8.6.3.1.</description>
      <section ref="C.8.6.3.1" name="">Illumination (2010,015E) and Reflected Ambient Light (2010,0160) may be used to recover Optical Density information from P-Values.
Monochrome media that is being digitized is often measured in Optical Density values. These values need to be converted to P-Values for storage and display. The P-Values used in an image correspond to the perception of a human observer viewing the film on a hypothetical viewing device (such as a light box), using the specified values of Illumination (2010,015E) and Reflected Ambient Light (2010,0160).
The Grayscale Standard Display Function defined in PS 3.14 is used to convert Luminance to P-Values. In the case of scanned film, the Luminance is derived from Optical Density using the specified values of Illumination (2010,015E) and Reflected Ambient Light (2010,0160). An example of this derivation, as well as typical “default” values for these parameters, is specified in PS 3.14.
</section>
    </entry>
    <entry group="2010" element="0160" name="Reflected Ambient Light" type="3">
      <description>For scanned monochrome transmissive film viewed on a hypothetical viewing device, the luminance contribution due to reflected ambient light. Expressed as La, in candelas per square meter (cd/m2).
Note: May be used together with Illumination (2010,015E) to recover Optical Density information from P-Values. See C.8.6.3.1.</description>
      <section ref="C.8.6.3.1" name="">Illumination (2010,015E) and Reflected Ambient Light (2010,0160) may be used to recover Optical Density information from P-Values.
Monochrome media that is being digitized is often measured in Optical Density values. These values need to be converted to P-Values for storage and display. The P-Values used in an image correspond to the perception of a human observer viewing the film on a hypothetical viewing device (such as a light box), using the specified values of Illumination (2010,015E) and Reflected Ambient Light (2010,0160).
The Grayscale Standard Display Function defined in PS 3.14 is used to convert Luminance to P-Values. In the case of scanned film, the Luminance is derived from Optical Density using the specified values of Illumination (2010,015E) and Reflected Ambient Light (2010,0160). An example of this derivation, as well as typical “default” values for these parameters, is specified in PS 3.14.
</section>
    </entry>
    <entry group="0028" element="1052" name="Rescale Intercept" type="1C">
      <description>The value b in the relationship between stored values (SV) in Pixel Data (7FE0,0010) and the output units specified in Rescale Type (0028,1054).
Output units = m*SV + b.
Enumerated Value: 0
Required if Photometric Interpretation (0028,0004) is MONOCHROME2, and BitsStored () is greater than 1.
Note: This specifies an identity Modality LUT transformation.</description>
    </entry>
    <entry group="0028" element="1053" name="Rescale Slope" type="1C">
      <description>m in the equation specified by Rescale Intercept (0028,1052).
Enumerated Value: 1
Required if Photometric Interpretation (0028,0004) is MONOCHROME2, and BitsStored (0028,0101) is greater than 1.
Note: This specifies an identity Modality LUT transformation.</description>
    </entry>
    <entry group="0028" element="1054" name="Rescale Type" type="1C">
      <description>Specifies the output units of Rescale Slope (0028,1053) and Rescale Intercept (0028,1052).
Enumerated Value: US = Unspecified
Required if Photometric Interpretation (0028,0004) is MONOCHROME2, and BitsStored (0028,0101) is greater than 1.
Note: This specifies an identity Modality LUT transformation.</description>
    </entry>
    <entry group="0028" element="0009" name="Frame Increment Pointer" type="1C">
      <description>Contains the Data Element Tag of the attribute which is used as the frame increment in Multi-frame pixel data. See C.7.6.6.1.1 for further explanation.
Shall be present if Number of Frames is greater than 1, overriding (specializing) the Type 1 requirement on this attribute in the Multi-frame Module.</description>
      <section ref="C.7.6.6.1.1" name="">A Multi-frame Image is defined as a Image whose pixel data consists of a sequential set of individual Image Pixel frames. A Multi-frame Image is transmitted as a single contiguous stream of pixels. Frame headers do not exist within the data stream.
Each individual frame shall be defined (and thus can be identified) by the Attributes in the Image Pixel Module (see C.7.6.3). All Image IE Attributes shall be related to the first frame in the Multi-frame image.
The total number of frames contained within a Multi-frame Image is conveyed in the Number of Frames (0028,0008).
The frames within a Multi-frame Image shall be conveyed as a logical sequence. The information that determines the sequential order of the frames shall be identified by the Data Element Tag or tags conveyed by the Frame Increment Pointer (0028,0009). Each specific Image IOD that supports the Multi-frame Module specializes the Frame Increment Pointer (0028,0009) to identify the Attributes that may be used as sequences.
Even if only a single frame is present, Frame Increment Pointer (0028,0009) is still required to be present and have at least one value, each of which shall point to an attribute that is also present in the dataset and has a value.
Note:  For example, in single-frame instance of an IOD that is required to or may contain the Cine Module, it may be appropriate for Frame Time (0018,1063) to be present with a value of 0, and be the only target of Frame Increment Pointer (0028,0009).

</section>
    </entry>
    <entry group="0018" element="2010" name="Nominal Scanned Pixel Spacing" type="1C">
      <description>Physical distance on the media being digitized or scanned between the center of each pixel, specified by a numeric pair - adjacent row spacing (delimiter) adjacent column spacing in mm. See 10.7.1.3 for further explanation of the value order.
Required if Conversion Type (0008,0064) is DF (Digitized Film). May also be present if Conversion Type (0008,0064) is SD (Scanned Document) or SI (Scanned Image).
Shall be consistent with Pixel Aspect Ratio (0028,0034), if present.</description>
    </entry>
    <include ref="Include Basic Pixel Spacing Calibration Macro (Table 10-10)"/>
    <entry group="0018" element="2020" name="Digitizing Device Transport Direction" type="3">
      <description>Enumerated Values:
ROW
COLUMN</description>
    </entry>
    <entry group="0018" element="2030" name="Rotation of Scanned Film" type="3">
      <description>Angle of the edge of the film relative to the transport direction in degrees greater than or equal to -45 and less than or equal to +45.</description>
    </entry>
  </module>
  <module ref="C.8.6.4" table="C.8-25c" name="SC Multi Frame Vector Module Attributes">
    <entry group="0018" element="1065" name="Frame Time Vector" type="1C">
      <description>An array which contains the real time increments (in msec) between frames for a Multi-frame image.
See C.7.6.5.1.2 for further explanation.
Required if Frame Increment Pointer (0028,0009) points to Frame Time Vector (0018,1065).
Note: Frame Time Vector arrays may not be properly encoded if Explicit-VR transfer syntax is used and the VL of this attribute exceeds 65534 bytes.</description>
      <section ref="C.7.6.5.1.2" name="">Frame Time Vector (0018,1065) is an array that contains the time increments (in milliseconds) between the nth frame and the previous frame for a Multi-frame image. The first frame always has a time increment of 0. If the Frame Increment Pointer points to this Attribute, the Frame Time Vector shall be used in the following manner to calculate 'relative time' T(n) for frame n:

where ti is the ith Frame Time Vector component.
</section>
    </entry>
    <entry group="0018" element="2001" name="Page Number Vector" type="1C">
      <description>An array which contains, for each of the image frames, the corresponding page numbers of the original document.
Required if Frame Increment Pointer (0028,0009) points to Page Number Vector (0018,2001).</description>
    </entry>
    <entry group="0018" element="2002" name="Frame Label Vector" type="1C">
      <description>An array which contains, for each of the image frames, a descriptive label.
Required if Frame Increment Pointer (0028,0009) points to Frame Label Vector (0018,2002).</description>
    </entry>
    <entry group="0018" element="2003" name="Frame Primary Angle Vector" type="1C">
      <description>An array which contains, for each of the image frames, the primary angle of rotation about an undefined axis, in degrees. May be used for annotative purposes for "cine loops" of 3D reprojected images
Required if Frame Increment Pointer (0028,0009) points to Frame Primary Angle Vector (0018,2003).</description>
    </entry>
    <entry group="0018" element="2004" name="Frame Secondary Angle Vector" type="1C">
      <description>An array which contains, for each of the image frames, the secondary angle of rotation about an undefined axis that is orthogonal to that used for Frame Primary Angle Vector (0018,2003), in degrees. May be used for annotative purposes for "cine loops" of 3D reprojected images
Required if Frame Increment Pointer (0028,0009) points to Frame Secondary Angle Vector (0018,2004).</description>
    </entry>
    <entry group="0018" element="2005" name="Slice Location Vector" type="1C">
      <description>An array that contains, for each of the image frames, the relative position of the image plane expressed in mm, as defined for Slice Location (0020,1041). See C.7.6.2.1.2 for further explanation.
Required if Frame Increment Pointer (0028,0009) points to Slice Location Vector (0018,2005).</description>
      <section ref="C.7.6.2.1.2" name="">The Slice Location (0020,1041) is defined as the relative position of the image plane expressed in mm. This information is relative to an unspecified implementation specific reference point.
</section>
    </entry>
    <entry group="0018" element="2006" name="Display Window Label Vector" type="1C">
      <description>An array which contains, for each of the image frames, a label or number of the display window of a graphical user interface from which the frame was captured.
Required if Frame Increment Pointer (0028,0009) points to Display Window Label Vector (0018,2006).</description>
    </entry>
  </module>
  <module ref="C.8.7.1" table="C.8-26" name="X Ray Image Module Attributes">
    <entry group="0028" element="0009" name="Frame Increment Pointer" type="1C">
      <description>Required if Multi-Frame Image.
Contains the Data Element Tag of the attribute that is used as the Frame increment in Multi-frame image pixel data (See C.7.6.6). Specialized for X-Ray as Enumerated Value:
00181063H = Frame Time (0018,1063);
00181065H = Frame Time Vector (0018,1065).</description>
      <section ref="C.7.6.6" name="">Table C.7-14 specifies the Attributes of a Multi-frame pixel data Image.
Table C.7-14
MULTI-FRAME MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Number of Frames" meaning="(0028,0008)"/><term value="Frame Increment Pointer" meaning="(0028,0009)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1C">
      <description>Specifies whether an Image has undergone lossy compression. Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5
Required if Lossy Compression has been performed on the Image.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image identification characteristics.
See C.8.7.1.1.1 for specialization.</description>
      <section ref="C.8.7.1.1.1" name="">The Image Type attribute identifies important image characteristics in a multiple valued data element. For X-Ray, Image Type is specialized as follows:
a.  Value 1 shall identify the Pixel Data Characteristics in accordance with Section C.7.6.1.1.2; Enumerated Values are: ORIGINAL and DERIVED;
b.  Value 2 shall identify the Patient Examination Characteristics in accordance with Section C.7.6.1.1.2; Enumerated Values are: PRIMARY and SECONDARY.

Note:  X-Ray images generally use PRIMARY value for images captured from patient exposure.

c.  Value 3 shall identify the image set in terms of the imaging planes. Enumerated Values are:

<enumerated-values><term value="SINGLE PLANE" meaning="Image is a single plane acquisition;"/><term value="BIPLANE A" meaning="Image is the first plane (e.g., Frontal) of a Bi-plane acquisition;"/><term value="BIPLANE B" meaning="Image is the second plane (e.g., Lateral) of a Bi-plane acquisition"/></enumerated-values>
d.  Other Values are implementation specific (optional).

</section>
    </entry>
    <entry group="0028" element="1040" name="Pixel Intensity Relationship" type="1">
      <description>The relationship between the Pixel sample values and the X-Ray beam intensity.
See Section C.8.7.1.1.2.</description>
      <section ref="C.8.7.1.1.2" name="">Pixel Intensity Relationship (0028,1040) shall identify the relationship of the pixel values to the X-Ray beam intensity. Defined terms are:
<unrecognized-rows><term value="LIN" meaning="Approximately proportional to X-Ray beam intensity;"/><term value="LOG" meaning="Non-linear “ Log Function”; A Modality LUT shall be included with the image to allow it to be scaled back to its proportional value to X-Ray beam intensity;"/><term value="DISP" meaning="Ready to be displayed; A Modality LUT may be included with the image to allow it to be scaled back to its proportional value to X-Ray beam intensity. The Attribute Acquisition Device Processing Description may be used to provide some indication on the pre-processing performed to create the ready to be displayed image."/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (color planes) in this image shall have a value of 1.</description>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data. Only MONOCHROME2 may be used.</description>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample.
See Section C.8.7.1.1.6.</description>
      <section ref="C.8.7.1.1.6" name="">For X-Ray Images, Bits Allocated (0028,0100) shall have the Enumerated Value of 8 or 16.
</section>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample.
See Section C.8.7.1.1.7.</description>
      <section ref="C.8.7.1.1.7" name="">For X-Ray Images, Bits Stored (0028,0101) shall have the Enumerated Values of 8, 10, 12, or 16.
</section>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data.
See Section C.8.7.1.1.8.</description>
      <section ref="C.8.7.1.1.8" name="">For X-Ray Images, High Bit (0028,0102) shall have the Enumerated Value of one less than the value in Bit Stored.
</section>
    </entry>
    <entry group="0028" element="0103" name="Pixel Representation" type="1">
      <description>Data representation of the pixel samples.
Shall have the value:
0000H = Unsigned Integer.</description>
    </entry>
    <entry group="0018" element="0022" name="Scan Options" type="3">
      <description>Parameters of scanning sequence.
See Section C. 8.7.1.1.4.</description>
    </entry>
    <include ref="Include 'General Anatomy Optional Macro' Table 10-7" description="No Context ID for the Anatomic Region Sequence is defined."/>
    <entry group="0028" element="6040" name="R Wave Pointer" type="3">
      <description>Marks the location(s) of the R Wave in the cardiac cycles by referencing frame numbers; frame numbers begin with 1.</description>
    </entry>
    <entry group="0008" element="1140" name="Referenced Image Sequence" type="1C">
      <description>A sequence which provides reference to a set of Image SOP Class/Instance identifying other images significantly related to this image. Shall be present if Image Type (0008,0008) Value 3 is BIPLANE A or BIPLANE B. May be present otherwise. One or more items may be included in this sequence..
See Section C.8.7.1.1.13.</description>
      <section ref="C.8.7.1.1.13" name="">When Image Type (0008,0008) Value 3 is BIPLANE A or BIPLANE B, Referenced Image Sequence (0008,1140) shall be used to identify the corresponding SOP Instance of the Biplane acquisition. In this case, either:
</section>
    </entry>
    <include ref="&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="3">
      <description>Describes the purpose for which the reference is made. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="Defined Context ID 7201"/>
    <entry group="0008" element="2111" name="Derivation Description" type="3">
      <description>A text description of how this image was derived.
See C.8.7.1.1.5 for further explanation.</description>
      <section ref="C.8.7.1.1.5" name="">If an Image is identified to be a Derived image (see C.8.9.1.1.1 Image Type), Derivation Description (0008,2111) is an optional and implementation specific text description of the way the image was derived from an original image. As applied to X-Ray images, it may be used to describe derivation operations such as edge enhancement, temporal filtering, digital subtraction, or other linear and non-linear transformations.
</section>
    </entry>
    <entry group="0018" element="1400" name="Acquisition Device Processing Description" type="3">
      <description>Indicates any visual processing performed on the images prior to exchange.
See Section C.8.7.1.1.3.</description>
      <section ref="C.8.7.1.1.3" name="">Acquisition Device Processing Description (0018,1400) provides some indication in human readable text of the digital processing on the images before exchange. Examples of this processing are: edge enhanced, subtracted, time filtered, gamma corrected, convolved (spatially filtered).
</section>
    </entry>
    <entry group="0018" element="2002" name="Frame Label Vector" type="3">
      <description>A multi-valued attribute that contains a descriptive label for each of the image frames. The number of values shall equal the number of frames.</description>
    </entry>
    <entry group="0028" element="000A" name="Frame Dimension Pointer" type="3">
      <description>Contains the Data Element Tags of one or more attributes that vary or increment for the frames of a multi-frame image. See C.8.7.1.1.12.
Shall not be present if it would contain only one value and that value would be Frame Time (0018,1063) or Frame Time Vector (0018,1065).</description>
      <section ref="C.8.7.1.1.12" name="">Frame Dimension Pointer (0028,000A) identifies attributes that vary or increment with each frame, and which are clinically significant for viewing or processing the image. This is intended for SOP Instances whose preferred clinical presentation is dependent on frame relationships other than simply time.
Defined Terms for multiframe cine from the Cine Module (see C.7.6.5) are:
00181063H = Frame Time (0018,1063)
00181065H = Frame Time Vector (0018,1065)
Defined Terms for rotational acquisition from the XA Positioner Module (see C.8.7.5) are:
00181520H = Positioner Primary Angle Increment (0018,1520)
00181521H = Positioner Secondary Angle Increment (0018,1521)
Defined Terms for stepped acquisition from the X-Ray Table Module (see C.8.7.4) are:
00181135H = Table Vertical Increment (0018,1135)
00181137H = Table Longitudinal Increment (0018,1137)
00181136H = Table Lateral Increment (0018,1136)
Defined Terms for an arbitrary labeled increment:
00182002H = Frame Label Vector (0018,2002)

Notes:  1. Previous editions of the standard did not include the optional Frame Dimension Pointer (0028,000A), but instead depended entirely on the mandatory Frame Increment Pointer (0028,0009), and envisaged that only time and no other dimension would relate frames. Image creators that add the Frame Dimension Pointer (0028,000A) must anticipate that many implementations will ignore or discard this attribute when displaying or storing images and continue to assume that frames are temporally related.
  2. Frame Time (0018,1063) or Frame Time Vector (0018,1065) will also be present and will contain appropriate values consistent with the times of acquisition of the frames.

</section>
    </entry>
    <entry group="0050" element="0004" name="Calibration Image" type="3">
      <description>Indicates whether a reference object (phantom) of known size is present in the image and was used for calibration. Enumerated Values:
YES
NO
Device is identified using the Device module. See C.7.6.12.</description>
      <section ref="C.7.6.12" name="">Table C.7-18 describes the Attributes of devices or calibration objects (e.g., catheters, markers, baskets) that are associated with a study and/or image.
Table C.7-18
DEVICE MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Device Sequence" meaning="(0050,0010)"/><term value="&gt;Include ‘Code Sequence Macro’ Table 8.8-1" meaning="Baseline Context ID is 4051."/><term value="&gt;Manufacturer" meaning="(0008,0070)"/><term value="&gt;Manufacturer’s Model Name" meaning="(0008,1090)"/><term value="&gt;Device Serial Number" meaning="(0018,1000)"/><term value="&gt;Device ID" meaning="(0018,1003)"/><term value="&gt;Device Length" meaning="(0050,0014)"/><term value="&gt;Device Diameter" meaning="(0050,0016)"/><term value="&gt;Device Diameter Units" meaning="(0050,0017)"/><term value="&gt;Device Volume" meaning="(0050,0018)"/><term value="&gt;Inter-Marker Distance" meaning="(0050,0019)"/><term value="&gt;Device Description" meaning="(0050,0020)"/></unrecognized-rows>
         </section>
    </entry>
  </module>
  <module ref="C.8.7.2" table="C.8-27" name="X Ray Acquisition Module Attributes">
    <entry group="0018" element="0060" name="KVP" type="2">
      <description>Peak kilo voltage output of the X-Ray generator used.</description>
    </entry>
    <entry group="0018" element="1155" name="Radiation Setting" type="1">
      <description>Identify the general level of X-Ray dose exposure. Enumerated values are:
SC = low dose exposure generally corresponding to fluoroscopic settings (e.g. preparation for diagnostic quality image acquisition);
GR = high dose for diagnostic quality image acquisition (also called digital spot or cine);</description>
    </entry>
    <entry group="0018" element="1151" name="X-Ray Tube Current" type="2C">
      <description>X-Ray Tube Current in mA. Required if Exposure (0018,1152) is not present. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="8151" name="X-Ray Tube Current in µA" type="3">
      <description>X-Ray Tube Current in µA.</description>
    </entry>
    <entry group="0018" element="1150" name="Exposure Time" type="2C">
      <description>Duration of X-Ray exposure in msec. See 8.7.2.1.1. Required if Exposure (0018,1152) is not present. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="8150" name="Exposure Time in µS" type="3">
      <description>Duration of X-Ray exposure in µsec.</description>
    </entry>
    <entry group="0018" element="1152" name="Exposure" type="2C">
      <description>The exposure expressed in mAs, for example calculated from Exposure Time and X-Ray Tube Current. Required if either Exposure Time (0018,1150) or X-Ray Tube Current (0018,1151) are not present. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="1153" name="Exposure in µAs" type="3">
      <description>The exposure expressed in µAs, for example calculated from Exposure Time and X-Ray Tube Current.</description>
    </entry>
    <entry group="0018" element="1166" name="Grid" type="3">
      <description>Identify the grid. Only a single value shall be present. Defined Terms are:
IN = A Grid is positioned;
NONE = No Grid is used.</description>
    </entry>
    <entry group="0018" element="1154" name="Average Pulse Width" type="3">
      <description>Average width of X-Ray pulse in msec.</description>
    </entry>
    <entry group="0018" element="115A" name="Radiation Mode" type="3">
      <description>Specifies X-Ray radiation mode. Defined Terms:
CONTINUOUS
PULSED</description>
    </entry>
    <entry group="0018" element="1161" name="Type of Filters" type="3">
      <description>Type of filter(s) inserted into the X-Ray beam (e.g. wedges).</description>
    </entry>
    <entry group="0018" element="1162" name="Intensifier Size" type="3">
      <description>Diameter of X-Ray intensifier in mm</description>
    </entry>
    <entry group="0018" element="1147" name="Field of View Shape" type="3">
      <description>Shape of the Image Intensifier Field of View. See C.8.7.2.1.2. Defined Terms are:
ROUND
RECTANGLE</description>
      <section ref="C.8.7.2.1.2" name="">The Field of View Attribute describes the shape and dimensions of the Image Intensifier Field of View (zoom mode). This could be further restricted by the Collimator. See Section C.8.7.3.
</section>
    </entry>
    <entry group="0018" element="1149" name="Field of View Dimension(s)" type="3">
      <description>Dimensions of the Image Intensifier Field of View in mm. If Rectangle, row dimension followed by column; if Round, diameter.</description>
    </entry>
    <entry group="0018" element="1164" name="Imager Pixel Spacing" type="3">
      <description>Physical distance measured at the front plane of the Image Receptor housing between the center of each pixel specified by a numeric pair - row spacing value(delimiter) column spacing value in mm. See 10.7.1.3 for further explanation of the value order.
The value of this attribute shall never be adjusted to account for correction for the effect of geometric magnification or calibration against an object of known size; Pixel Spacing (0028,0030) is specified for that purpose.</description>
    </entry>
    <include ref="Include Basic Pixel Spacing Calibration Macro (Table 10-10)"/>
    <entry group="0018" element="1190" name="Focal Spot" type="3">
      <description>Nominal focal spot size in mm used to acquire this image.</description>
    </entry>
    <entry group="0018" element="115E" name="Image and Fluoroscopy Area Dose Product" type="3">
      <description>X-Ray dose, measured in dGy*cm*cm, to which the patient was exposed for the acquisition of this image plus any non-digitally recorded fluoroscopy which may have been performed to prepare for the acquisition of this image.
Note: The sum of the area dose product of all images of a Series or a Study may not result in the total area dose product to which the patient was exposed.</description>
    </entry>
  </module>
  <module ref="C.8.7.3" table="C.8-28" name="X Ray Collimator Module Attributes">
    <entry group="0018" element="1700" name="Collimator Shape" type="1">
      <description>Shape(s) of the collimator. Enumerated Values:
RECTANGULAR
CIRCULAR
POLYGONAL
This multi-valued Attribute shall contain at most one of each Enumerated Value.</description>
    </entry>
    <entry group="0018" element="1702" name="Collimator Left Vertical Edge" type="1C">
      <description>Required if Collimator Shape (0018,1700) is RECTANGULAR. Location of the left edge of the rectangular collimator with respect to pixels in the image given as column. See C.8.7.3.1.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1704" name="Collimator Right Vertical Edge" type="1C">
      <description>Required if Collimator Shape (0018,1700) is RECTANGULAR. Location of the right edge of the rectangular collimator with respect to pixels in the image given as column. See C.8.7.3.1.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1706" name="Collimator Upper Horizontal Edge" type="1C">
      <description>Required if Collimator Shape (0018,1700) is RECTANGULAR. Location of the upper edge of the rectangular collimator with respect to pixels in the image given as row. See C.8.7.3.1.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1708" name="Collimator Lower Horizontal Edge" type="1C">
      <description>Required if Collimator Shape (0018,1700) is RECTANGULAR. Location of the lower edge of the rectangular collimator with respect to pixels in the image given as row. See C.8.7.3.1.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1710" name="Center of Circular Collimator" type="1C">
      <description>Required if Collimator Shape (0018,1700) is CIRCULAR. Location of the center of the circular collimator with respect to pixels in the image given as row and column. See C.8.7.3.1.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1712" name="Radius of Circular Collimator" type="1C">
      <description>Required if Collimator Shape (0018,1700) is CIRCULAR. Radius of the circular collimator with respect to pixels in the image given as a number of pixels along the row direction. See C.8.7.3.1.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1720" name="Vertices of the Polygonal Collimator" type="1C">
      <description>Required if Collimator Shape (0018,1700) is POLYGONAL.
Multiple Values where the first set of two values are:
row of the origin vertex;
column of the origin vertex.
Two or more pairs of values follow and are the row and column coordinates of the other vertices of the polygon collimator. Polygon collimators are implicitly closed from the last vertex to the origin vertex and all edges shall be non-intersecting except at the vertices.</description>
    </entry>
  </module>
  <module ref="C.8.7.4" table="C.8-29" name="X Ray Table Module Attributes">
    <entry group="0018" element="1134" name="Table Motion" type="2">
      <description>Defined terms:
STATIC
DYNAMIC</description>
    </entry>
    <entry group="0018" element="1135" name="Table Vertical Increment" type="2C">
      <description>Incremental change in Vertical position of the table relative to first frame of Multi-frame image given in mm.
Required if Table Motion is DYNAMIC.</description>
    </entry>
    <entry group="0018" element="1137" name="Table Longitudinal Increment" type="2C">
      <description>Incremental change in Longitudinal position of the table relative to first frame of Multi-frame image in mm. Table motion towards +90°position of the primary angle of the positioner is positive. See C.8.7.4.1.2.
Required if Table Motion is DYNAMIC.</description>
      <section ref="C.8.7.4.1.2" name="">The direction of the longitudinal movement is perpendicular to the primary axis of rotation of the positioner. A positive value of Table Longitudinal Increment (0018,1137) attributes indicates a movement towards the +90° position of the positioner, see figure C.8-9a.

Figure C.8-9a
Table Longitudinal Movement
</section>
    </entry>
    <entry group="0018" element="1136" name="Table Lateral Increment" type="2C">
      <description>Incremental change in Lateral position of the table relative to first frame of Multi-frame image given in mm. Table motion towards +90°position of the secondary angle of the positioner is positive. See C.8.7.4.1.3.
Required if Table Motion is DYNAMIC.</description>
      <section ref="C.8.7.4.1.3" name="">The direction of the lateral movement is perpendicular to the secondary axis of rotation of the positioner. A positive value of Table Lateral Increment (0018,1136) attributes indicates a movement towards the +90° position of the positioner, see figure C.8-9b.

Figure C.8-9b
Table Lateral Movement
Note:    The terms “longitudinal” and “lateral” are relative to an operator standing tableside, and facing the patient. Thus lateral movement is to the left and right of the operator, and longitudinal movement is towards or away from the operator.

</section>
    </entry>
    <entry group="0018" element="1138" name="Table Angle" type="3">
      <description>Angle of table plane in degrees relative to horizontal plane [Gravity plane]. Positive values indicate that the head of the table is upwards.</description>
    </entry>
  </module>
  <module ref="C.8.7.5" table="C.8-30" name="XA Positioner Module Attributes">
    <entry group="0018" element="1111" name="Distance Source to Patient" type="3">
      <description>Distance in mm from source to isocenter (center of field of view).
Note: This value is traditionally referred to as Source Object Distance (SOD).</description>
    </entry>
    <entry group="0018" element="1110" name="Distance Source to Detector" type="3">
      <description>Distance in mm from source to detector center.
Note: This value is traditionally referred to as Source Image Receptor Distance (SID).</description>
    </entry>
    <entry group="0018" element="1114" name="Estimated Radiographic Magnification Factor" type="3">
      <description>Ratio of Source Image Receptor Distance (SID) over Source Object Distance (SOD).</description>
    </entry>
    <entry group="0018" element="1500" name="Positioner Motion" type="2C">
      <description>Used to describe the activity of the imaging devices. Defined terms:
DYNAMIC,
STATIC.
Required if Multi-frame data. See C.8.7.5.1.1.</description>
      <section ref="C.8.7.5.1.1" name="">Positioner Motion attribute is STATIC if the imaging table moves during a multi-frame acquisition, but the X-Ray positioner do not move.
Note:  If the positioner undergoes translation (non-rotational movement) during the acquisition, then that motion shall be described by an opposite table motion (See Section C.8.7.4).

</section>
    </entry>
    <entry group="0018" element="1510" name="Positioner Primary Angle" type="2">
      <description>Position of the X-Ray Image Intensifier about the patient from the RAO to LAO direction where movement from RAO to vertical is positive.
See C.8.7.5.1.2.</description>
      <section ref="C.8.7.5.1.2" name="">The definitions of Positioner Angles shall be with respect to the patient as illustrated in Figures C.8-11 and C.8-12 Zero degree is referenced to the origin perpendicular to the patient's chest. The Positioner Primary Angle definition is like longitude (in the equatorial plan); the Positioner Secondary Angle definition is like latitude (in the sagittal plane). The Positioner Angle attributes apply to the first frame of a multi-frame image. The valid range of Primary Positioner Angle is -180 to +180 degrees and the Secondary Positioner Angle range is -90 to + 90 degrees.
The Patient Plane is defined by the isocenter of the imaging device and slices through the patient such that it is perpendicular to the sagittal plane of the body. The Primary Axis of rotation is defined at the intersection of the Patient Plane and of the Sagittal Plane. The Positioner Primary Angle is defined in the transaxial plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest and + 90 degrees at the Patient left hand side (LAO) and -90 at the Patient right hand side (RAO). The valid range of Primary Positioner Angle is -180 to +180 degrees.
The Secondary Axis is in the Patient Plane and is perpendicular to the Primary Axis at the isocenter. The Positioner Secondary Angle is defined in the Sagittal Plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest. +90 degrees corresponds to the cranial direction. The Secondary Positioner Angle range is -90 to + 90 degrees.
At a 0 angle for both the Primary Angle (0018,1510) and Secondary Angle (0018,1511), the patient faces the Image Intensifier.
The Positioner Primary Angle (0018,1510) and Secondary Angle (0018,1511) apply to the first frame of a multi-frame image.

Figure C.8-11
Positioner Primary Angle

Figure C.8-12
Positioner Secondary Angle
</section>
    </entry>
    <entry group="0018" element="1511" name="Positioner Secondary Angle" type="2">
      <description>Position of the X-Ray Image Intensifier about the patient from the CAU to CRA direction where movement from CAU to vertical is positive.
See C.8.7.5.1.2</description>
      <section ref="C.8.7.5.1.2" name="">The definitions of Positioner Angles shall be with respect to the patient as illustrated in Figures C.8-11 and C.8-12 Zero degree is referenced to the origin perpendicular to the patient's chest. The Positioner Primary Angle definition is like longitude (in the equatorial plan); the Positioner Secondary Angle definition is like latitude (in the sagittal plane). The Positioner Angle attributes apply to the first frame of a multi-frame image. The valid range of Primary Positioner Angle is -180 to +180 degrees and the Secondary Positioner Angle range is -90 to + 90 degrees.
The Patient Plane is defined by the isocenter of the imaging device and slices through the patient such that it is perpendicular to the sagittal plane of the body. The Primary Axis of rotation is defined at the intersection of the Patient Plane and of the Sagittal Plane. The Positioner Primary Angle is defined in the transaxial plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest and + 90 degrees at the Patient left hand side (LAO) and -90 at the Patient right hand side (RAO). The valid range of Primary Positioner Angle is -180 to +180 degrees.
The Secondary Axis is in the Patient Plane and is perpendicular to the Primary Axis at the isocenter. The Positioner Secondary Angle is defined in the Sagittal Plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest. +90 degrees corresponds to the cranial direction. The Secondary Positioner Angle range is -90 to + 90 degrees.
At a 0 angle for both the Primary Angle (0018,1510) and Secondary Angle (0018,1511), the patient faces the Image Intensifier.
The Positioner Primary Angle (0018,1510) and Secondary Angle (0018,1511) apply to the first frame of a multi-frame image.

Figure C.8-11
Positioner Primary Angle

Figure C.8-12
Positioner Secondary Angle
</section>
    </entry>
    <entry group="0018" element="1520" name="Positioner Primary Angle Increment" type="2C">
      <description>Incremental change in primary positioner angle for each frame.
See C.8.7.5.1.3.
Required if Positioner Motion is DYNAMIC.</description>
      <section ref="C.8.7.5.1.3" name="">If the positioner angles change during acquisition of a multi-frame image, the Positioner Angle Increment attributes describe the angular change per frame.
If the change in positioner angle is nominally constant for each frame, these fields may contain a single value of the average angular change per frame. Alternatively, the fields may contain a vector of offsets from the (initial) Positioner Angle attributes, with one value for each frame in the multi-frame image. The number of values in the Positioner Angle Increment attributes must be one, or must be equal to the Number of Frames attribute (0028,0008) in the Multi-Frame Module (see Section C.7.6.6).
Note:  It is permissible to generate a vector of the absolute positioner angles in the Positioner Angle Increment attributes, and set the Positioner Primary and Secondary Angle attributes to value 0.

</section>
    </entry>
    <entry group="0018" element="1521" name="Positioner Secondary Angle Increment" type="2C">
      <description>Incremental change in secondary positioner angle for each frame.
See C.8.7.5.1.3.
Required if Positioner Motion is DYNAMIC.</description>
      <section ref="C.8.7.5.1.3" name="">If the positioner angles change during acquisition of a multi-frame image, the Positioner Angle Increment attributes describe the angular change per frame.
If the change in positioner angle is nominally constant for each frame, these fields may contain a single value of the average angular change per frame. Alternatively, the fields may contain a vector of offsets from the (initial) Positioner Angle attributes, with one value for each frame in the multi-frame image. The number of values in the Positioner Angle Increment attributes must be one, or must be equal to the Number of Frames attribute (0028,0008) in the Multi-Frame Module (see Section C.7.6.6).
Note:  It is permissible to generate a vector of the absolute positioner angles in the Positioner Angle Increment attributes, and set the Positioner Primary and Secondary Angle attributes to value 0.

</section>
    </entry>
    <entry group="0018" element="1530" name="Detector Primary Angle" type="3">
      <description>Angle of the X-Ray beam in the row direction in degrees relative to the normal to the detector plane. Positive values indicate that the X-Ray beam is tilted towards higher numbered columns. Negative values indicate that the X-Ray beam is tilted towards lower numbered columns.
See C.8.7.5.1.4.</description>
      <section ref="C.8.7.5.1.4" name="">Detector Angles are defined in a fashion similar to the positioner angles, except that the angle of the central x-ray beam vector is relative to the detector plane rather than the patient plane. The central x-ray beam vector is defined as the vector from the x-ray source through the isocenter to the detector plane. Zero degree is referenced to the normal to the detector plane pointing away from the x-ray source. The Detector Angle attributes apply to the first frame of a multi-frame image. The valid range of the Detector Angles is -90 to + 90 degrees.
The Primary Axis of rotation is defined along the line in the column direction of the detector plane which intersects the central x-ray beam vector. The Detector Primary Angle is defined in the plane perpendicular to the Primary Axis of rotation at the point where the central x-ray beam vector intersects the detector plane, with zero degrees in the direction normal to the detector plane and -90 degrees at the left hand side of the image (i.e., toward column 1) and +90 at the right hand side of the image (i.e., toward the highest numbered column). The valid range of Primary Detector Angle is -90 to +90 degrees.
The Secondary Axis is in the detector plane and is perpendicular to the Primary Axis at the intersection of the beam vector with the detector plane (i.e., it is along the row direction). The Detector Secondary Angle is defined in the plane perpendicular to the Secondary Axis at the point where the central x-ray beam vector intersects the detector plane, with zero degrees in the direction normal to the detector plane. +90 degrees corresponds to the direction toward the top of the image. The Secondary Detector Angle range is -90 to + 90 degrees.
</section>
    </entry>
    <entry group="0018" element="1531" name="Detector Secondary Angle" type="3">
      <description>Angle of the X-Ray beam in the column direction in degrees relative to the normal to the detector plane. Positive values indicate that the X-Ray beam is tilted towards lower numbered rows. Negative values indicate that the X-Ray beam is tilted towards higher numbered rows.
See C.8.7.5.1.4.</description>
      <section ref="C.8.7.5.1.4" name="">Detector Angles are defined in a fashion similar to the positioner angles, except that the angle of the central x-ray beam vector is relative to the detector plane rather than the patient plane. The central x-ray beam vector is defined as the vector from the x-ray source through the isocenter to the detector plane. Zero degree is referenced to the normal to the detector plane pointing away from the x-ray source. The Detector Angle attributes apply to the first frame of a multi-frame image. The valid range of the Detector Angles is -90 to + 90 degrees.
The Primary Axis of rotation is defined along the line in the column direction of the detector plane which intersects the central x-ray beam vector. The Detector Primary Angle is defined in the plane perpendicular to the Primary Axis of rotation at the point where the central x-ray beam vector intersects the detector plane, with zero degrees in the direction normal to the detector plane and -90 degrees at the left hand side of the image (i.e., toward column 1) and +90 at the right hand side of the image (i.e., toward the highest numbered column). The valid range of Primary Detector Angle is -90 to +90 degrees.
The Secondary Axis is in the detector plane and is perpendicular to the Primary Axis at the intersection of the beam vector with the detector plane (i.e., it is along the row direction). The Detector Secondary Angle is defined in the plane perpendicular to the Secondary Axis at the point where the central x-ray beam vector intersects the detector plane, with zero degrees in the direction normal to the detector plane. +90 degrees corresponds to the direction toward the top of the image. The Secondary Detector Angle range is -90 to + 90 degrees.
</section>
    </entry>
  </module>
  <module ref="C.8.7.6" table="C.8-31" name="XRF Positioner Module Attributes">
    <entry group="0018" element="1110" name="Distance Source to Detector" type="3">
      <description>Distance in mm from source to detector center.
Note: This value is traditionally referred to as Source Image Receptor Distance (SID).</description>
    </entry>
    <entry group="0018" element="1111" name="Distance Source to Patient" type="3">
      <description>Distance in mm from source to isocenter (center of field of view).
Note: This value is traditionally referred to as Source Object Distance (SOD).</description>
    </entry>
    <entry group="0018" element="1114" name="Estimated Radiographic Magnification Factor" type="3">
      <description>Ratio of SID (Source Image Receptor Distance) over SOD (Source Object Distance).</description>
    </entry>
    <entry group="0018" element="1450" name="Column Angulation" type="3">
      <description>Angle of the X-Ray beam in degree relative to an orthogonal axis to the detector plane. Positive values indicate that the tilt is towards the head of the table.
Note: The detector plane is assumed to be parallel to the table plane.</description>
    </entry>
  </module>
  <module ref="C.8.7.7" table="C.8-32" name="X Ray Tomography Acquisition Module Attributes">
    <entry group="0018" element="1460" name="Tomo Layer Height" type="1">
      <description>Distance in mm between the table surface and the sharp image plane.</description>
    </entry>
    <entry group="0018" element="1470" name="Tomo Angle" type="3">
      <description>Angle span in degrees of rotation of X-Ray Source during X-Ray acquisition.</description>
    </entry>
    <entry group="0018" element="1480" name="Tomo Time" type="3">
      <description>Time in seconds the source has taken to rotate the Tomo Angle during X-Ray acquisition.</description>
    </entry>
    <entry group="0018" element="1490" name="Tomo Type" type="3">
      <description>Type of tomography.
Defined Terms:
LINEAR
SPIRAL
POLYCYCLOIDAL
CIRCULAR</description>
    </entry>
    <entry group="0018" element="1491" name="Tomo Class" type="3">
      <description>Form of tomography:
Defined Terms:
MOTION
TOMOSYNTHESIS</description>
    </entry>
    <entry group="0018" element="1495" name="Number of Tomosynthesis Source Images" type="3">
      <description>The number of source images used to construct this tomosynthetic image. Only meaningful if Tomo Class (0018,1491) is TOMOSYNTHESIS. These may be listed in Source Image Sequence (0008,2112) of the General Image Module.</description>
    </entry>
  </module>
  <module ref="C.8.7.8" table="C.8-33" name="X Ray Acquisition Dose Module Attributes">
    <entry group="0018" element="0060" name="KVP" type="3">
      <description>Peak kilo voltage output of the X-Ray generator used.</description>
    </entry>
    <entry group="0018" element="1151" name="X-Ray Tube Current" type="3">
      <description>X-Ray Tube Current in mA.</description>
    </entry>
    <entry group="0018" element="8151" name="X-Ray Tube Current in µA" type="3">
      <description>X-Ray Tube Current in µA.</description>
    </entry>
    <entry group="0018" element="1150" name="Exposure Time" type="3">
      <description>Duration of X-Ray exposure in msec.</description>
    </entry>
    <entry group="0018" element="8150" name="Exposure Time in µS" type="3">
      <description>Duration of X-Ray exposure in µsec.</description>
    </entry>
    <entry group="0018" element="1152" name="Exposure" type="3">
      <description>The exposure expressed in mAs, for example calculated from Exposure Time and X-Ray Tube Current.</description>
    </entry>
    <entry group="0018" element="1153" name="Exposure in µAs" type="3">
      <description>The exposure expressed in µAs, for example calculated from Exposure Time and X-Ray Tube Current.</description>
    </entry>
    <entry group="0018" element="1110" name="Distance Source to Detector" type="3">
      <description>Distance in mm from source to detector center.
Note: This value is traditionally referred to as Source Image Receptor Distance (SID).</description>
    </entry>
    <entry group="0018" element="1111" name="Distance Source to Patient" type="3">
      <description>Distance in mm from source to the table, support or bucky side that is closest to the Imaging Subject, as measured along the central ray of the X-Ray beam.
Note: 1. This definition is less useful in terms of estimating geometric magnification than a measurement to a defined point within the Imaging Subject, but accounts for what is realistically measurable in an automated fashion in a clinical setting.
2. This measurement does not take into account any air gap between the Imaging Subject and the "front" of the table or bucky.
3. If the detector is not mounted in a table or bucky, then the actual position relative to the patient is implementation or operator defined.
4. This value is traditionally referred to as Source Object Distance (SOD).</description>
    </entry>
    <entry group="0018" element="115E" name="Image and Fluoroscopy Area Dose Product" type="3">
      <description>X-Ray dose, measured in dGy*cm*cm, to which the patient was exposed for the acquisition of this image plus any non-digitally recorded fluoroscopy which may have been performed to prepare for the acquisition of this image.
Notes: 1. The sum of the area dose product of all images of a Series or a Study may not result in the total area dose product to which the patient was exposed.
2. This may be an estimated value based on assumptions about the patient's body size and habitus.</description>
    </entry>
    <entry group="0018" element="11A0" name="Body Part Thickness" type="3">
      <description>The average thickness in mm of the body part examined when compressed, if compression has been applied during exposure.</description>
    </entry>
    <entry group="0018" element="1405" name="Relative X-Ray Exposure" type="3">
      <description>Indication of the applied dose, in manufacturer specific units.
Notes: 1. This value is intended to provide a single location where manufacturer specific information can be found for annotation on a display or film, that has meaning to a knowledgeable observer.
2. This may be a calculated or measured value. Examples are the detector entrance dose (KB), the CR sensitivity value (S), or the logarithmic median (lgM).</description>
    </entry>
    <entry group="0040" element="0302" name="Entrance Dose" type="3">
      <description>Average entrance dose value measured in dGy at the surface of the patient during the acquisition of this image.
Note: This may be an estimated value based on assumptions about the patient's body size and habitus.</description>
    </entry>
    <entry group="0040" element="8302" name="Entrance Dose in mGy" type="3">
      <description>Average entrance dose value measured in mGy at the surface of the patient during the acquisition of this image.
Note: This may be an estimated value based on assumptions about the patient's body size and habitus.</description>
    </entry>
    <entry group="0040" element="0303" name="Exposed Area" type="3">
      <description>Typical dimension of the exposed area at the detector plane. If Rectangular: row dimension followed by column; if Round: diameter. Measured in cm.
Notes: 1. The exposed area should be consistent with values specified in the X-Ray Collimator Module, if present.
2. This may be an estimated value based on assumptions about the patient's body size and habitus.
3. This attribute is used in the Radiation Dose Module with units in mm (see Section C.4.16 Table C.4-16).</description>
    </entry>
    <entry group="0040" element="0306" name="Distance Source to Entrance" type="3">
      <description>Distance in mm from the source to the surface of the patient closest to the source during the acquisition of this image.
Note: This may be an estimated value based on assumptions about the patient's body size and habitus.</description>
    </entry>
    <entry group="0040" element="0310" name="Comments on Radiation Dose" type="3">
      <description>User-defined comments on any special conditions related to radiation dose encountered during the acquisition of this image.</description>
    </entry>
    <entry group="0040" element="0312" name="X-Ray Output" type="3">
      <description>The X-Ray output at the patient entrance surface and kVp used to acquire the image, measured in mGy/mAs.
Note: This value may be a calibrated value rather than measured during the exposure.</description>
    </entry>
    <entry group="0040" element="0314" name="Half Value Layer" type="3">
      <description>The thickness of Aluminum in mm required to reduce the X-Ray Output (0040,0312) by a factor of two.
Note: This value may be a calibrated value rather than measured during the exposure.</description>
    </entry>
    <entry group="0040" element="0316" name="Organ Dose" type="3">
      <description>Average organ dose value measured in dGy during the acquisition of this image.
Note: This may be an estimated value.</description>
    </entry>
    <entry group="0040" element="0318" name="Organ Exposed" type="3">
      <description>Organ to which Organ Dose (0040,0316) applies.
Defined Terms:
BREAST
GONADS
BONE MARROW
FETUS
LENS
Note: The anatomic regions described by these terms are those that are particularly radiosensitive and for which it is conventional to obtain organ specific dose parameters.</description>
    </entry>
    <entry group="0018" element="1191" name="Anode Target Material" type="3">
      <description>The primary material in the anode of the X-Ray source.
Defined Terms:
TUNGSTEN
MOLYBDENUM
RHODIUM</description>
    </entry>
    <entry group="0018" element="7050" name="Filter Material" type="3">
      <description>The X-Ray absorbing material used in the filter. May be multi-valued.
Defined Terms:
MOLYBDENUM
ALUMINUM
COPPER
RHODIUM
NIOBIUM
EUROPIUM
LEAD</description>
    </entry>
    <entry group="0018" element="7052" name="Filter Thickness Minimum" type="3">
      <description>The minimum thickness in mm of the X-Ray absorbing material used in the filters. May be multi-valued, with values corresponding to the respective values in Filter Material (0018,7050).</description>
    </entry>
    <entry group="0018" element="7054" name="Filter Thickness Maximum" type="3">
      <description>The maximum thickness in mm of the X-Ray absorbing material used in the filters. May be multi-valued, with values corresponding to the respective values in Filter Material (0018,7050).</description>
    </entry>
    <entry group="0018" element="1156" name="Rectification Type" type="3">
      <description>Type of rectification used in the X-Ray generator.
Defined Terms:
SINGLE PHASE
THREE PHASE
CONST POTENTIAL</description>
    </entry>
  </module>
  <module ref="C.8.7.9" table="C.8-34" name="X Ray Generation Module Attributes">
    <entry group="0018" element="0060" name="KVP" type="3">
      <description>Peak kilo voltage output of the X-Ray generator used.</description>
    </entry>
    <entry group="0018" element="1151" name="X-Ray Tube Current" type="3">
      <description>X-Ray Tube Current in mA.</description>
    </entry>
    <entry group="0018" element="8151" name="X-Ray Tube Current in µA" type="3">
      <description>X-Ray Tube Current in µA.</description>
    </entry>
    <entry group="0018" element="1150" name="Exposure Time" type="3">
      <description>Duration of X-Ray exposure in msec.</description>
    </entry>
    <entry group="0018" element="8150" name="Exposure Time in µS" type="3">
      <description>Duration of X-Ray exposure in µsec.</description>
    </entry>
    <entry group="0018" element="1152" name="Exposure" type="3">
      <description>The exposure expressed in mAs, for example calculated from Exposure Time and X-Ray Tube Current.</description>
    </entry>
    <entry group="0018" element="1153" name="Exposure in µAs" type="3">
      <description>The exposure expressed in µAs, for example calculated from Exposure Time and X-Ray Tube Current.</description>
    </entry>
    <entry group="0018" element="7060" name="Exposure Control Mode" type="3">
      <description>Type of exposure control.
Defined Terms:
MANUAL
AUTOMATIC</description>
    </entry>
    <entry group="0018" element="7062" name="Exposure Control Mode Description" type="3">
      <description>Text description of the mechanism of exposure control.
May describe the number and type of exposure sensors or position of the sensitive area of the imaging detector.</description>
    </entry>
    <entry group="0018" element="7064" name="Exposure Status" type="3">
      <description>Whether the exposure was normally completed or not.
Defined Terms:
NORMAL
ABORTED</description>
    </entry>
    <entry group="0018" element="7065" name="Phototimer Setting" type="3">
      <description>Nominal percentage phototimer setting, where a more positive value indicates greater exposure and a more negative value indicates less exposure.</description>
    </entry>
    <entry group="0018" element="1190" name="Focal Spot" type="3">
      <description>Nominal focal spot size in mm used to acquire this image.</description>
    </entry>
    <entry group="0018" element="1191" name="Anode Target Material" type="3">
      <description>The primary material in the anode of the X-Ray source.
Defined Terms:
TUNGSTEN
MOLYBDENUM
RHODIUM</description>
    </entry>
    <entry group="0018" element="1156" name="Rectification Type" type="3">
      <description>Type of rectification used in the X-Ray generator.
Defined Terms:
SINGLE PHASE
THREE PHASE
CONST POTENTIAL</description>
    </entry>
    <entry group="0018" element="1005" name="Generator ID" type="3">
      <description>Identifier of the generator</description>
    </entry>
  </module>
  <module ref="C.8.7.10" table="C.8-35" name="X Ray Filtration Module Attributes">
    <entry group="0018" element="1160" name="Filter Type" type="3">
      <description>Type of filter(s) inserted into the X-Ray beam (e.g. wedges).
Defined Terms:
STRIP
WEDGE
BUTTERFLY
MULTIPLE
NONE</description>
    </entry>
    <entry group="0018" element="7050" name="Filter Material" type="3">
      <description>The X-Ray absorbing material used in the filter. May be multi-valued.
Defined Terms:
MOLYBDENUM
ALUMINUM
COPPER
RHODIUM
NIOBIUM
EUROPIUM
LEAD</description>
    </entry>
    <entry group="0018" element="7052" name="Filter Thickness Minimum" type="3">
      <description>The minimum thickness in mm of the X-Ray absorbing material used in the filters. May be multi-valued, with values corresponding to the respective values in Filter Material (0018,7050).</description>
    </entry>
    <entry group="0018" element="7054" name="Filter Thickness Maximum" type="3">
      <description>The maximum thickness in mm of the X-Ray absorbing material used in the filters. May be multi-valued, with values corresponding to the respective values in Filter Material (0018,7050).</description>
    </entry>
  </module>
  <module ref="C.8.7.11" table="C.8-36" name="X Ray Grid Module Attributes">
    <entry group="0018" element="1166" name="Grid" type="3">
      <description>Identifies the grid. May be multi-valued.
Defined Terms are:
FIXED
FOCUSED
RECIPROCATING
PARALLEL
CROSSED
NONE</description>
    </entry>
    <entry group="0018" element="7040" name="Grid Absorbing Material" type="3">
      <description>The X-Ray absorbing material used in the grid.</description>
    </entry>
    <entry group="0018" element="7041" name="Grid Spacing Material" type="3">
      <description>The spacing material used in the grid.</description>
    </entry>
    <entry group="0018" element="7042" name="Grid Thickness" type="3">
      <description>The thickness in mm of the X-Ray absorbing material used in the grid.</description>
    </entry>
    <entry group="0018" element="7044" name="Grid Pitch" type="3">
      <description>The pitch in mm of the X-Ray absorbing material used in the grid.</description>
    </entry>
    <entry group="0018" element="7046" name="Grid Aspect Ratio" type="3">
      <description>Ratio of the vertical spacing and horizontal spacing of the X-Ray absorbing material used in the grid. Specified by a pair of integer values where the first value is the vertical size, and the second value is the horizontal size.</description>
    </entry>
    <entry group="0018" element="7048" name="Grid Period" type="3">
      <description>Period in mSec of reciprocation cycle.
Only meaningful if Grid (0018,1166) is RECIPROCATING.</description>
    </entry>
    <entry group="0018" element="704C" name="Grid Focal Distance" type="3">
      <description>Focal distance in mm of a FOCUSED grid.</description>
    </entry>
    <entry group="0018" element="1006" name="Grid ID" type="3">
      <description>Identifier of the grid</description>
    </entry>
  </module>
  <module ref="C.8.8.1" table="C.8-37" name="RT Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Type of equipment that originally acquired the data. Enumerated Values:
RTIMAGE = RT Image
RTDOSE = RT Dose
RTSTRUCT = RT Structure Set
RTPLAN = RT Plan
RTRECORD = RT Treatment Record
See C.8.8.1.1.</description>
      <section ref="C.8.8.1.1" name="">The Enumerated Value for Modality (0008,0060) shall determined by the IOD:
RTIMAGE   if RT Image IOD,
RTDOSE  if RT Dose IOD,
RTSTRUCT  if RT Structure Set IOD,
RTPLAN  if RT Plan IOD or RT Ion Plan IOD,
RTRECORD  if RT Beams Treatment Record IOD, RT Ion Beams Treatment Record IOD, RT Brachy Treatment Record IOD, or RT Treatment Summary Record IOD.
Note:  DICOM specifies that a given series shall contain objects of only one Modality, and shall be created by a single device (described in the General Equipment Module). However, in general there may be many series defined for a given modality/device pair. Note that a radiotherapy series is generally created over an extended time interval (unlike in radiology, where all images in an image series are generally created together).

</section>
    </entry>
    <entry group="0020" element="000E" name="Series Instance UID" type="1">
      <description>Unique identifier of the series.</description>
    </entry>
    <entry group="0020" element="0011" name="Series Number" type="2">
      <description>A number that identifies this series.</description>
    </entry>
    <entry group="0008" element="103E" name="Series Description" type="3">
      <description>User provided description of the series.</description>
    </entry>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence" type="3">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance to which the Series is related (e.g. a Modality or General-Purpose Performed Procedure Step SOP Instance). One or more items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0040" element="0275" name="Request Attributes Sequence" type="3">
      <description>Sequence that contains attributes from the Imaging Service Request.
The sequence may have one or more Items.</description>
    </entry>
    <include ref="&gt;Include Request Attributes Macro Table 10-9" description="No Baseline Context IDs defined"/>
    <include ref="Include Performed Procedure Step Summary Macro Table 10-16" description="No Baseline Context IDs defined"/>
  </module>
  <module ref="C.8.8.2" table="C.8-38" name="RT Image Module Attributes">
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (planes) in this image. See C.8.8.2.6.1 for specialization.</description>
      <section ref="C.8.8.2.6.1" name="">For RT Images, Samples per Pixel (0028,0002) shall have the Enumerated Value of 0001H.
</section>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data. See C.8.8.2.6.2 for specialization.</description>
      <section ref="C.8.8.2.6.2" name="">For RT Images, Photometric Interpretation (0028,0004) shall have the Enumerated Value of MONOCHROME2.
</section>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated. See C.8.8.2.6.3 for specialization.</description>
      <section ref="C.8.8.2.6.3" name="">For RT Images, Bits Allocated (0028,0100) shall have an Enumerated Value of 8 or 16.
</section>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored. See C.8.8.2.6.4 for specialization.</description>
      <section ref="C.8.8.2.6.4" name="">For RT Images, Bits Stored (0028,0101) shall have an Enumerated Value of:
  8     when Bits Allocated (0028,0100) is 8
  12-16  when Bits Allocated (0028,0100) is 16
</section>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for each pixel sample. Each sample shall have the same high bit. See C.8.8.2.6.5 for specialization.</description>
      <section ref="C.8.8.2.6.5" name="">For RT Images, High Bit (0028,0102) shall have the Enumerated Value of one less than the value sent in Bits Stored (0028,0101).
</section>
    </entry>
    <entry group="0028" element="0103" name="Pixel Representation" type="1">
      <description>Data representation of the pixel samples. Each sample shall have the same pixel representation. See C.8.8.2.6.6 for specialization.</description>
      <section ref="C.8.8.2.6.6" name="">For RT Images, Pixel Representation (0028,0103) shall have the Enumerated Value of 0000H (unsigned integer).
</section>
    </entry>
    <entry group="0028" element="1040" name="Pixel Intensity Relationship" type="3">
      <description>The relationship between the Pixel sample values and the X-Ray beam intensity.
Enumerated Values:
LIN = Linearly proportional to X-Ray beam intensity
LOG = Logarithmically proportional to X-Ray beam intensity
See C.8.11.3.1.2 for further explanation.</description>
      <section ref="C.8.11.3.1.2" name="">Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041) describe how the stored pixel values in Pixel Data (7FE0,0010) are related to the X-Ray beam intensity incident on the detector.
They do not define a transformation intended to be applied to the pixel data for presentation.
Note:  For example, if Pixel Intensity Relationship (0028,1040) is LIN and Pixel Intensity Relationship Sign (0028,1041) is -1, then lower values of Pixel Data (7FE0,0010) indicate higher X-Ray beam intensities corresponding to less radiographically dense regions projected on the image such as through air, and higher values of Pixel Data (7FE0,0010) indicate lower X-Ray beam intensities corresponding to more radiographically dense regions projected on the image such as through bone and radio-opaque contrast agents.

The transformation to be applied to the pixel data for presentation is defined by the successive application of the conceptual Modality LUT, the VOI Attributes and the conceptual Presentation LUT. This shall result in the output of P-Values.
Rescale Slope (0028,1053) and Rescale Intercept (0028,1052) define a linear subset of a conceptual Modality LUT transformation. For IODs that include this Module, these Attributes define an identity transformation. IODs that include the DX Image Module shall not include the Modality LUT Module.
The Presentation LUT Shape (2050,0020) defines a subset of a conceptual Presentation LUT. For IODs that include this Module, this Attribute defines an identity transformation or inverse identity transformation. IODs that include the DX Image Module shall not include the Presentation LUT Module.
Photometric Interpretation (0028,0004) indicates whether lower values that are the output of the VOI Attributes should be displayed as darker or lighter. Since the output of the equivalent of a conceptual Presentation LUT is in P-Values, which are defined in PS 3.14 such that lower values correspond to lower luminance levels, then the definition of the Presentation LUT Shape (2050,0020), otherwise intended to be an identity transformation, must take into account the effect of the value specified for Photometric Interpretation (0028,0004).
Note:  Regardless of the values of Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041), the grayscale transformations to be applied to the Pixel Data (7FE0,0010) are defined by the equivalent of the Modality LUT (Rescale Slope (0028,1053) and Rescale Intercept (0028,1052)), Value of Interest Attributes, Photometric Interpretation (0028,0004) and the equivalent of the Presentation LUT (Presentation LUT Shape (2050,0020)). However, the combination of the grayscale transformations and the description of the pixel intensity relationship, together define whether, for example, air is expected to be displayed as black or white.

</section>
    </entry>
    <entry group="0028" element="1041" name="Pixel Intensity Relationship Sign" type="1C">
      <description>The sign of the relationship between the Pixel sample values stored in Pixel Data (7FE0,0010) and the X-Ray beam intensity.
Required if Pixel Intensity Relationship (0028,1040) is present.
Enumerated Values;
1 = Lower pixel values correspond to less X-Ray beam intensity
-1 = Higher pixel values correspond to less X-Ray beam intensity
See C.8.11.3.1.2 for further explanation.</description>
      <section ref="C.8.11.3.1.2" name="">Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041) describe how the stored pixel values in Pixel Data (7FE0,0010) are related to the X-Ray beam intensity incident on the detector.
They do not define a transformation intended to be applied to the pixel data for presentation.
Note:  For example, if Pixel Intensity Relationship (0028,1040) is LIN and Pixel Intensity Relationship Sign (0028,1041) is -1, then lower values of Pixel Data (7FE0,0010) indicate higher X-Ray beam intensities corresponding to less radiographically dense regions projected on the image such as through air, and higher values of Pixel Data (7FE0,0010) indicate lower X-Ray beam intensities corresponding to more radiographically dense regions projected on the image such as through bone and radio-opaque contrast agents.

The transformation to be applied to the pixel data for presentation is defined by the successive application of the conceptual Modality LUT, the VOI Attributes and the conceptual Presentation LUT. This shall result in the output of P-Values.
Rescale Slope (0028,1053) and Rescale Intercept (0028,1052) define a linear subset of a conceptual Modality LUT transformation. For IODs that include this Module, these Attributes define an identity transformation. IODs that include the DX Image Module shall not include the Modality LUT Module.
The Presentation LUT Shape (2050,0020) defines a subset of a conceptual Presentation LUT. For IODs that include this Module, this Attribute defines an identity transformation or inverse identity transformation. IODs that include the DX Image Module shall not include the Presentation LUT Module.
Photometric Interpretation (0028,0004) indicates whether lower values that are the output of the VOI Attributes should be displayed as darker or lighter. Since the output of the equivalent of a conceptual Presentation LUT is in P-Values, which are defined in PS 3.14 such that lower values correspond to lower luminance levels, then the definition of the Presentation LUT Shape (2050,0020), otherwise intended to be an identity transformation, must take into account the effect of the value specified for Photometric Interpretation (0028,0004).
Note:  Regardless of the values of Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041), the grayscale transformations to be applied to the Pixel Data (7FE0,0010) are defined by the equivalent of the Modality LUT (Rescale Slope (0028,1053) and Rescale Intercept (0028,1052)), Value of Interest Attributes, Photometric Interpretation (0028,0004) and the equivalent of the Presentation LUT (Presentation LUT Shape (2050,0020)). However, the combination of the grayscale transformations and the description of the pixel intensity relationship, together define whether, for example, air is expected to be displayed as black or white.

</section>
    </entry>
    <entry group="3002" element="0002" name="RT Image Label" type="1">
      <description>User-defined label for RT Image.</description>
    </entry>
    <entry group="3002" element="0003" name="RT Image Name" type="3">
      <description>User-defined name for RT Image.</description>
    </entry>
    <entry group="3002" element="0004" name="RT Image Description" type="3">
      <description>User-defined description of RT Image.</description>
    </entry>
    <entry group="0008" element="1070" name="Operators' Name" type="2">
      <description>Name of operator(s) acquiring or creating RT Image.</description>
    </entry>
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image identification characteristics (see Section C.7.6.1.1.2). RT Images shall use one of the following Defined Terms for Value 3:
DRR = digitally reconstructed radiograph
PORTAL = digital portal image or portal film image
SIMULATOR = conventional simulator image
RADIOGRAPH = radiographic image
BLANK = image pixels set to background value
FLUENCE = fluence map</description>
    </entry>
    <entry group="0008" element="0064" name="Conversion Type" type="2">
      <description>Describes the kind of image conversion. Defined Terms:
DV = Digitized Video
DI = Digital Interface
DF = Digitized Film
WSD = Workstation</description>
    </entry>
    <entry group="3002" element="000A" name="Reported Values Origin" type="2C">
      <description>Describes the origin of the parameter values reported in the image. Required if Value 3 of Image Type (0008,0008) is SIMULATOR or PORTAL.
Enumerated Values:
OPERATOR = manually entered by operator
PLAN = planned parameter values
ACTUAL = electronically recorded</description>
    </entry>
    <entry group="3002" element="000C" name="RT Image Plane" type="1">
      <description>Describes whether or not image plane is normal to beam axis.
Enumerated Values:
NORMAL = image plane normal to beam axis
NON_NORMAL = image plane non-normal to beam axis</description>
    </entry>
    <entry group="3002" element="000D" name="X-Ray Image Receptor Translation" type="3">
      <description>Position in (x,y,z) coordinates of origin of IEC X-RAY IMAGE RECEPTOR System in the IEC GANTRY coordinate system (mm). See Note 2.</description>
    </entry>
    <entry group="3002" element="000E" name="X-Ray Image Receptor Angle" type="2">
      <description>X-Ray Image Receptor Angle i.e. orientation of IEC X-RAY IMAGE RECEPTOR coordinate system with respect to IEC GANTRY coordinate system (degrees). See C.8.8.2.2.</description>
      <section ref="C.8.8.2.2" name="">The X-Ray Image Receptor Angle (3002,000E) specifies the rotation of the image receptor device in the IEC X-RAY IMAGE RECEPTOR PLANE. A positive angle corresponds to a counter-clockwise rotation of the X-Ray Image Receptor as viewed from the radiation source in the IEC GANTRY coordinate system. The normal (non-rotated) value for this parameter is zero degrees.
</section>
    </entry>
    <entry group="3002" element="0010" name="RT Image Orientation" type="2C">
      <description>The direction cosines of the first row and the first column with respect to the IEC X-RAY IMAGE RECEPTOR coordinate system. Required if RT Image Plane (3002,000C) is NON_NORMAL. May be present otherwise.</description>
    </entry>
    <entry group="3002" element="0011" name="Image Plane Pixel Spacing" type="2">
      <description>Physical distance (in mm) between the center of each image pixel, specified by a numeric pair - adjacent row spacing (delimiter) adjacent column spacing. See C.8.8.2.3 and 10.7.1.3 for further explanation.</description>
      <section ref="C.8.8.2.3" name="">The Image Plane Pixel Spacing (3002,0011) attribute shall always be defined on the image plane, i.e. at the radiation machine source to image plane distance specified by RT Image SID (3002,0026). For images where the source-image distance is undefined or unknown (e.g. DRR images), RT Image SID (3002,0026) shall equal Radiation Machine SAD (3002,0022) and Image Plane Pixel Spacing (3002,0011) shall be defined on this common plane.
</section>
    </entry>
    <entry group="3002" element="0012" name="RT Image Position" type="2">
      <description>The x and y coordinates (in mm) of the upper left hand corner of the image, in the IEC X-RAY IMAGE RECEPTOR coordinate system. This is the center of the first pixel transmitted. See C.8.8.2.7.</description>
      <section ref="C.8.8.2.7" name="">When RT Image Plane (3002,000C) is NORMAL and RT Image Orientation (3002,0010) is not provided, the orientation is defined as follows: The image viewing direction goes from the radiation source to the image (i.e. in the sense of a beam’s eye view, or along the negative Zr direction of the IEC X-RAY IMAGE RECEPTOR coordinate system). The direction of rows goes along the positive Xr direction and the direction of the columns goes along the negative Yr direction of the IEC X-RAY IMAGE RECEPTOR coordinate system. Other interpretations shall be documented in an implementation's conformance statement.
</section>
    </entry>
    <entry group="3002" element="0020" name="Radiation Machine Name" type="2">
      <description>User-defined name identifying radiation machine used in acquiring or computing image (i.e. name of conventional simulator, electron accelerator, X-Ray device, or machine modeled when calculating DRR).</description>
    </entry>
    <entry group="300A" element="00B3" name="Primary Dosimeter Unit" type="2">
      <description>Measurement unit of machine dosimeter.
Enumerated Values:
MU = Monitor Unit
MINUTE = minute</description>
    </entry>
    <entry group="3002" element="0022" name="Radiation Machine SAD" type="2">
      <description>Radiation source to Gantry rotation axis distance of radiation machine used in acquiring or computing image (mm).</description>
    </entry>
    <entry group="3002" element="0024" name="Radiation Machine SSD" type="3">
      <description>Source to patient surface distance (in mm) of radiation machine used in acquiring or computing image.</description>
    </entry>
    <entry group="3002" element="0026" name="RT Image SID" type="2">
      <description>Distance from radiation machine source to image plane (in mm) along radiation beam axis. See C.8.8.2.3.</description>
      <section ref="C.8.8.2.3" name="">The Image Plane Pixel Spacing (3002,0011) attribute shall always be defined on the image plane, i.e. at the radiation machine source to image plane distance specified by RT Image SID (3002,0026). For images where the source-image distance is undefined or unknown (e.g. DRR images), RT Image SID (3002,0026) shall equal Radiation Machine SAD (3002,0022) and Image Plane Pixel Spacing (3002,0011) shall be defined on this common plane.
</section>
    </entry>
    <entry group="3002" element="0028" name="Source to Reference Object Distance" type="3">
      <description>Source to reference object distance (in mm), as used for magnification calculation of RADIOGRAPH and SIMULATOR images.</description>
    </entry>
    <entry group="300C" element="0002" name="Referenced RT Plan Sequence" type="3">
      <description>Introduces sequence of one Class/Instance pair describing RT Plan associated with image. Only a single item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="300C" element="0006" name="Referenced Beam Number" type="3">
      <description>Uniquely identifies the corresponding N-segment treatment beam specified by Beam Number (300A,00C0) within Beam Sequence in RT Beams Module within the RT Plan referenced in Referenced RT Plan Sequence (300C,0002).</description>
    </entry>
    <entry group="300C" element="0022" name="Referenced Fraction Group Number" type="3">
      <description>Identifier of Fraction Group within RT Plan referenced in Referenced RT Plan Sequence (300C,0002).</description>
    </entry>
    <entry group="3002" element="0029" name="Fraction Number" type="3">
      <description>Fraction Number of fraction during which image was acquired, within Fraction Group referenced by Referenced Fraction Group Number (300C,0022) within RT Plan referenced in Referenced RT Plan Sequence (300C,0002).</description>
    </entry>
    <entry group="300C" element="0008" name="Start Cumulative Meterset Weight" type="3">
      <description>Cumulative Meterset Weight within Beam referenced by Referenced Beam Number (300C,0006) at which image acquisition starts.</description>
    </entry>
    <entry group="300C" element="0009" name="End Cumulative Meterset Weight" type="3">
      <description>Cumulative Meterset Weight within Beam referenced by Referenced Beam Number (300C,0006) at which image acquisition ends.</description>
    </entry>
    <entry group="3002" element="0030" name="Exposure Sequence" type="3">
      <description>Introduces sequence of Exposure parameter sets, corresponding to exposures used in generating the image. One or more items may be included in this sequence. See C.8.8.2.4.</description>
      <section ref="C.8.8.2.4" name="">The Exposure Sequence (3002,0030) allows specification of imaging parameters and aperture definitions for single exposure images (single item sequence) or multiple exposures (multiple item sequence). A multiple exposure image can be expressed as a multi-frame image containing either a single frame, or more than one frame. Referenced Frame Number (0008,1160) shall be specified for each Exposure Sequence item for multiple exposure images expressed using more than one frame.
</section>
    </entry>
    <entry group="0008" element="1160" name="&gt;Referenced Frame Number" type="1C">
      <description>Identifies corresponding image frame in multi-frame image. Required if there is more than one item in Exposure Sequence (3002,0030), and image is a multi-frame image.</description>
    </entry>
    <entry group="0018" element="0060" name="&gt;KVP" type="2C">
      <description>Peak kilo voltage output (kV) of X-Ray generator used to acquire image. Required if Value 3 of Image Type (0008,0008) is PORTAL, SIMULATOR or RADIOGRAPH.</description>
    </entry>
    <entry group="0018" element="1151" name="&gt;X-Ray Tube Current" type="2C">
      <description>Imaging device X-Ray Tube Current (mA). Required if Value 3 of Image Type (0008,0008) is SIMULATOR or RADIOGRAPH.</description>
    </entry>
    <entry group="0018" element="1150" name="&gt;Exposure Time" type="2C">
      <description>Time of X-Ray exposure (msec). Required if Value 3 of Image Type (0008,0008) is SIMULATOR or RADIOGRAPH.</description>
    </entry>
    <entry group="3002" element="0032" name="&gt;Meterset Exposure" type="2C">
      <description>Treatment machine Meterset duration over which image has been acquired, specified in Monitor units (MU) or minutes as defined by Primary Dosimeter Unit (300A,00B3). Required if Value 3 of Image Type (0008,0008) is PORTAL.</description>
    </entry>
    <entry group="3002" element="0034" name="&gt;Diaphragm Position" type="3">
      <description>Positions of diaphragm jaw pairs (in mm) in IEC BEAM LIMITING DEVICE coordinate axis in the IEC order X1, X2, Y1, Y2.</description>
    </entry>
    <entry group="300A" element="00B6" name="&gt;Beam Limiting Device Sequence" type="3">
      <description>Introduces sequence of beam limiting device (collimator) jaw or leaf (element) positions for given exposure. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00B8" name="&gt;&gt;RT Beam Limiting Device Type" type="1">
      <description>Type of beam limiting device (collimator).
Enumerated Values:
X = symmetric jaw pair in IEC X direction
Y = symmetric jaw pair in IEC Y direction
ASYMX = asymmetric jaw pair in IEC X direction
ASYMY = asymmetric pair in IEC Y direction
MLCX = multileaf (multi-element) jaw pair in IEC X direction
MLCY = multileaf (multi-element) jaw pair in IEC Y direction</description>
    </entry>
    <entry group="300A" element="00BA" name="&gt;&gt;Source to Beam Limiting Device Distance" type="3">
      <description>Radiation source to beam limiting device (collimator) distance (mm).</description>
    </entry>
    <entry group="300A" element="00BC" name="&gt;&gt;Number of Leaf/Jaw Pairs" type="1">
      <description>Number of leaf (element) or jaw pairs (equal to 1 for standard beam limiting device jaws).</description>
    </entry>
    <entry group="300A" element="00BE" name="&gt;&gt;Leaf Position Boundaries" type="2C">
      <description>Boundaries (in mm) of beam limiting device (collimator) leaves (elements) in IEC BEAM LIMITING DEVICE coordinate axis appropriate to RT Beam Limiting Device Type (300A,00B8), i.e. X-axis for MLCY, Y-axis for MLCX. Contains N+1 values, where N is the Number of Leaf/Jaw Pairs (300A,00BC), starting from Leaf (Element) Pair 1. Required if RT Beam Limiting Device Type (300A,00B8) is MLCX or MLCY.</description>
    </entry>
    <entry group="300A" element="011C" name="&gt;&gt;Leaf/Jaw Positions" type="1">
      <description>Positions of beam limiting device (collimator) leaf or jaw (element) pairs (in mm) in IEC BEAM LIMITING DEVICE coordinate axis appropriate to RT Beam Limiting Device Type (300A,00B8), e.g. X-axis for MLCX, Y-axis for MLCY). Contains 2N values, where N is the Number of Leaf/Jaw Pairs (300A,00BC), in IEC leaf (element) subscript order 101, 102, ... 1N, 201, 202, ... 2N.</description>
    </entry>
    <entry group="300A" element="0107" name="&gt;Applicator Sequence" type="3">
      <description>Introduces sequence of Applicators associated with Beam. Only a single item shall be permitted in this sequence.</description>
    </entry>
    <entry group="300A" element="0108" name="&gt;&gt;Applicator ID" type="1">
      <description>User or machine supplied identifier for Applicator.</description>
    </entry>
    <entry group="300A" element="0109" name="&gt;&gt;Applicator Type" type="1">
      <description>Type of Applicator.
Defined Terms:
ELECTRON_SQUARE = square electron applicator
ELECTRON_RECT = rectangular electron applicator
ELECTRON_CIRC = circular electron applicator
ELECTRON_SHORT = short electron applicator
ELECTRON_OPEN = open (dummy) electron applicator
INTRAOPERATIVE = intraoperative (custom) applicator
STEREOTACTIC = stereotactic applicator</description>
    </entry>
    <entry group="300A" element="010A" name="&gt;&gt;Applicator Description" type="3">
      <description>User-defined description for Applicator.</description>
    </entry>
    <entry group="300A" element="00F0" name="&gt;Number of Blocks" type="1">
      <description>Number of shielding blocks associated with Beam.</description>
    </entry>
    <entry group="300A" element="00F4" name="&gt;Block Sequence" type="2C">
      <description>Introduces sequence of blocks associated with Beam. Required if Number of Blocks (300A,00F0) is non-zero. Zero or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00F5" name="&gt;&gt;Block Tray ID" type="3">
      <description>User-supplied identifier for block tray.</description>
    </entry>
    <entry group="300A" element="00F6" name="&gt;&gt;Source to Block Tray Distance" type="2">
      <description>Radiation Source to attachment edge of block tray assembly (mm).</description>
    </entry>
    <entry group="300A" element="00F8" name="&gt;&gt;Block Type" type="1">
      <description>Type of block.
Enumerated Values:
SHIELDING = blocking material is inside contour
APERTURE = blocking material is outside contour</description>
    </entry>
    <entry group="300A" element="00FA" name="&gt;&gt;Block Divergence" type="2">
      <description>Indicates presence or otherwise of geometrical divergence
Enumerated Values:
PRESENT = block edges are shaped for beam divergence
ABSENT = block edges are not shaped for beam divergence</description>
    </entry>
    <entry group="300A" element="00FB" name="&gt;&gt;Block Mounting Position" type="3">
      <description>Indicates on which side of the Block Tray the block is mounted.
Enumerated Values:
PATIENT_SIDE = the block is mounted on the side of the Block Tray which is towards the patient.
SOURCE_SIDE = the block is mounted on the side of the Block Tray which is towards the radiation source.</description>
    </entry>
    <entry group="300A" element="00FC" name="&gt;&gt;Block Number" type="1">
      <description>Identification Number of the Block. The value of Block Number (300A,00FC) shall be unique within the Beam in which it is created.</description>
    </entry>
    <entry group="300A" element="00FE" name="&gt;&gt;Block Name" type="3">
      <description>User-defined name for block.</description>
    </entry>
    <entry group="300A" element="00E1" name="&gt;&gt;Material ID" type="2">
      <description>User-supplied identifier for material used to manufacture Block.</description>
    </entry>
    <entry group="300A" element="0100" name="&gt;&gt;Block Thickness" type="3">
      <description>Physical thickness of block (in mm) parallel to radiation beam axis.</description>
    </entry>
    <entry group="300A" element="0104" name="&gt;&gt;Block Number of Points" type="2">
      <description>Number of (x,y) pairs defining the block edge.</description>
    </entry>
    <entry group="300A" element="0106" name="&gt;&gt;Block Data" type="2">
      <description>A data stream of (x,y) pairs which comprise the block edge. The number of pairs shall be equal to Block Number of Points (300A,0104), and the vertices shall be interpreted as a closed polygon. Coordinates are projected onto the machine isocentric plane in the IEC BEAM LIMITING DEVICE coordinate system (mm).</description>
    </entry>
    <entry group="3002" element="0040" name="Fluence Map Sequence" type="1C">
      <description>A Sequence of data describing the fluence map attributes for a radiotherapy beam.
Only one item may be included in this sequence.
Required if the third value of Image Type (0008,0008) is FLUENCE.</description>
    </entry>
    <entry group="3002" element="0041" name="&gt;Fluence Data Source" type="1">
      <description>Source of fluence data.
Enumerated Values:
CALCULATED = Calculated by a workstation
MEASURED=Measured by exposure to a film or detector.</description>
    </entry>
    <entry group="3002" element="0042" name="&gt;Fluence Data Scale" type="3">
      <description>The meterset corresponding with a fluence map cell value of 1.0 expressed in units specified by Primary Dosimeter Units (300A,00B3). This is the meterset value used for treatment, not the meterset used to expose the film as defined by Meterset Exposure (3002,0032).</description>
    </entry>
    <entry group="300A" element="011E" name="Gantry Angle" type="3">
      <description>Treatment machine gantry angle, i.e. orientation of IEC GANTRY coordinate system with respect to IEC FIXED REFERENCE coordinate system (degrees).</description>
    </entry>
    <entry group="300A" element="014A" name="Gantry Pitch Angle" type="3">
      <description>Gantry Pitch Angle. i.e. the rotation of the IEC GANTRY coordinate system about the X-axis of the IEC GANTRY coordinate system (degrees). See C.8.8.25.6.5.</description>
      <section ref="C.8.8.25.6.5" name="">The Gantry Pitch angle is not defined in IEC 61217. This angle is defined in the DICOM standard in a way compatible with the current notion of IEC by introducing it as rotation of the IEC GANTRY System as indicated below.
The Gantry Pitch Angle is defined as the rotation of the coordinate axes Yg, Zg about axis Xg by an angle g; see Figure C.8.8.25-7. An increase in the value of angle g corresponds to the clockwise rotation as viewed from the isocenter along the positive Xg axis


Figure C.8.8.25-7 Gantry Pitch Angle
</section>
    </entry>
    <entry group="300A" element="0120" name="Beam Limiting Device Angle" type="3">
      <description>Treatment machine beam limiting device (collimator) angle, i.e. orientation of IEC BEAM LIMITING DEVICE coordinate system with respect to IEC GANTRY coordinate system (degrees).</description>
    </entry>
    <entry group="300A" element="0122" name="Patient Support Angle" type="3">
      <description>Patient Support angle, i.e. orientation of IEC PATIENT SUPPORT coordinate system with respect to IEC FIXED REFERENCE coordinate system (degrees).</description>
    </entry>
    <entry group="300A" element="0124" name="Table Top Eccentric Axis Distance" type="3">
      <description>Distance (positive) from the IEC PATIENT SUPPORT vertical axis to the IEC TABLE TOP ECCENTRIC vertical axis (mm).</description>
    </entry>
    <entry group="300A" element="0125" name="Table Top Eccentric Angle" type="3">
      <description>Table Top (non-isocentric) angle, i.e. orientation of IEC TABLE TOP ECCENTRIC coordinate system with respect to IEC PATIENT SUPPORT system (degrees).</description>
    </entry>
    <entry group="300A" element="0140" name="Table Top Pitch Angle" type="3">
      <description>Table Top Pitch Angle, i.e. the rotation of the IEC TABLE TOP coordinate system about the X-axis of the IEC TABLE TOP coordinate system (degrees). See C.8.8.25.6.2.</description>
      <section ref="C.8.8.25.6.2" name="">Pitch and Roll Coordinate Systems of the Table Top are not defined in IEC 61217. These angles are defined in the DICOM standard in a way compatible with the current notion of IEC by introducing them as rotations of the IEC Table Top System as indicated below.
The Table Top Pitch Angle is defined as the rotation of the coordinate axes Yt, Zt about axis Xt by an angle t; see Figure C.8.8.25-3. An increase in the value of angle t corresponds to the clockwise rotation of the Table Top as viewed from the Table Top coordinate system origin along the positive Xt axis.
The Table Top Roll Angle is defined as the rotation of the coordinate axes Xt, Zt about axis Yt by an angle t; see Figure C.8.8.25-4. An increase in the value of angle t corresponds to the clockwise rotation of the Table Top as viewed from the Table Top coordinate system origin along the positive Yt axis.


Figure C.8.8.25-3 Table Top Pitch Angle

Figure C.8.8.25-4 Table Top Roll Angle

</section>
    </entry>
    <entry group="300A" element="0144" name="Table Top Roll Angle" type="3">
      <description>Table Top Roll Angle, i.e. the rotation of the IEC TABLE TOP coordinate system about the Y-axis of the IEC TABLE TOP coordinate system (degrees). See C.8.8.25.6.2.</description>
      <section ref="C.8.8.25.6.2" name="">Pitch and Roll Coordinate Systems of the Table Top are not defined in IEC 61217. These angles are defined in the DICOM standard in a way compatible with the current notion of IEC by introducing them as rotations of the IEC Table Top System as indicated below.
The Table Top Pitch Angle is defined as the rotation of the coordinate axes Yt, Zt about axis Xt by an angle t; see Figure C.8.8.25-3. An increase in the value of angle t corresponds to the clockwise rotation of the Table Top as viewed from the Table Top coordinate system origin along the positive Xt axis.
The Table Top Roll Angle is defined as the rotation of the coordinate axes Xt, Zt about axis Yt by an angle t; see Figure C.8.8.25-4. An increase in the value of angle t corresponds to the clockwise rotation of the Table Top as viewed from the Table Top coordinate system origin along the positive Yt axis.


Figure C.8.8.25-3 Table Top Pitch Angle

Figure C.8.8.25-4 Table Top Roll Angle

</section>
    </entry>
    <entry group="300A" element="0128" name="Table Top Vertical Position" type="3">
      <description>Table Top Vertical position in IEC TABLE TOP coordinate system (mm).</description>
    </entry>
    <entry group="300A" element="0129" name="Table Top Longitudinal Position" type="3">
      <description>Table Top Longitudinal position in IEC TABLE TOP coordinate system (mm).</description>
    </entry>
    <entry group="300A" element="012A" name="Table Top Lateral Position" type="3">
      <description>Table Top Lateral position in IEC TABLE TOP coordinate system (mm).</description>
    </entry>
    <entry group="300A" element="012C" name="Isocenter Position" type="3">
      <description>Isocenter coordinates (x,y,z), in mm. Specifies the location of the machine isocenter in the patient-based coordinate system associated with the Frame of Reference. It allows transformation from the equipment-based IEC coordinate system to the patient-based coordinate system.</description>
    </entry>
    <entry group="0018" element="5100" name="Patient Position" type="1C">
      <description>Patient position descriptor relative to the patient support device.
Required if Isocenter Position (300A,012C) is present. May be present otherwise.
See Section C.8.8.12.1.2 for Defined Terms and further explanation.
Note: The orientation of the patient relative to the patient support device is denoted in the same manner as in the RT Patient Setup module. It defines the relation of the patient-based DICOM coordinate system identified by the frame of reference module of the RT Image to the IEC coordinate system and together with the Isocenter Position (300A,012C) allows the RT Image to be placed into the patient frame of reference. It also allows a system using an RT Image to verify that the patient is setup in a similar position relative to the patient support device.</description>
      <section ref="C.8.8.12.1.2" name="">Defined Terms for Patient Position shall be those specified in Section C.7.3.1.1.2, plus the following:
  SITTING
In the sitting position, the patient’s face is towards the front of the chair.
</section>
    </entry>
  </module>
  <module ref="C.8.8.3" table="C.8-39" name="RT Dose Module Attributes">
    <entry group="0028" element="0002" name="Samples per Pixel" type="1C">
      <description>Number of samples (planes) in this image. See C.8.8.3.4.1 for specialization. Required if Pixel Data (7FE0,0010) is present.</description>
      <section ref="C.8.8.3.4.1" name="">For RT Doses, Samples per Pixel (0028,0002) shall have the Enumerated Value of 1.
</section>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1C">
      <description>Specifies the intended interpretation of the pixel data. See C.8.8.3.4.2 for specialization. Required if Pixel Data (7FE0,0010) is present.</description>
      <section ref="C.8.8.3.4.2" name="">For RT Doses, Photometric Interpretation (0028,0004) shall have the Enumerated Value of MONOCHROME2.
</section>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1C">
      <description>Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated. See C.8.8.3.4.3 for specialization. Required Pixel Data (7FE0,0010) is present.</description>
      <section ref="C.8.8.3.4.3" name="">For RT Doses, Bits Allocated (0028,0100) shall have an Enumerated Value of 16 or 32.
</section>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1C">
      <description>Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored. See C.8.8.3.4.4 for specialization. Required if Pixel Data (7FE0,0010) is present.</description>
      <section ref="C.8.8.3.4.4" name="">For RT Doses, Bits Stored (0028,0101) shall have an Enumerated Value equal to Bits Allocated (0028,0100).
</section>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1C">
      <description>Most significant bit for each pixel sample. Each sample shall have the same high bit. See C.8.8.3.4.5 for specialization. Required if Pixel Data (7FE0,0010) is present.</description>
      <section ref="C.8.8.3.4.5" name="">For RT Doses, High Bit (0028,0102) shall have the Enumerated Value of one less than the value sent in Bits Stored (0028,0101).
</section>
    </entry>
    <entry group="0028" element="0103" name="Pixel Representation" type="1C">
      <description>Data representation of the pixel samples. Each sample shall have the same pixel representation. See C.8.8.3.4.6 for specialization. Required Pixel Data (7FE0,0010) is present.</description>
      <section ref="C.8.8.3.4.6" name="">For RT Doses, Pixel Representation (0028,0103) is specified to use the following Enumerated Values:
0001H = two’s complement integer, when Dose Type (3004,0004) = ERROR
0000H = unsigned integer, otherwise.
</section>
    </entry>
    <entry group="3004" element="0002" name="Dose Units" type="1">
      <description>Units used to describe dose.
Enumerated Values:
GY = Gray
RELATIVE = dose relative to implicit reference value</description>
    </entry>
    <entry group="3004" element="0004" name="Dose Type" type="1">
      <description>Type of dose.
Defined Terms:
PHYSICAL = physical dose
EFFECTIVE = physical dose after correction for biological effect using user-defined modeling technique
ERROR = difference between desired and planned dose</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="3">
      <description>A number that identifies this object instance.</description>
    </entry>
    <entry group="3004" element="0006" name="Dose Comment" type="3">
      <description>User-defined comments for dose data.</description>
    </entry>
    <entry group="3004" element="0008" name="Normalization Point" type="3">
      <description>Coordinates (x, y, z) of normalization point in the patient based coordinate system described in C.7.6.2.1.1 (mm). See C.8.8.3.1.</description>
      <section ref="C.8.8.3.1" name="">The Normalization Point (3004,0008) aids in the interpretation and subsequent use of the transmitted data. If used, it shall be a point receiving dose contributions from all referenced components of the dose summation.
</section>
    </entry>
    <entry group="3004" element="000A" name="Dose Summation Type" type="1">
      <description>Type of dose summation.
Defined Terms:
PLAN = dose calculated for entire RT Plan
FRACTION = dose calculated for a single Fraction Group within RT Plan
BEAM = dose calculated for one or more Beams within RT Plan
BRACHY = dose calculated for one or more Brachy Application Setups within RT Plan
CONTROL_POINT = dose calculated for one or more Control Points within a Beam</description>
    </entry>
    <entry group="300C" element="0002" name="Referenced RT Plan Sequence" type="1C">
      <description>Introduces sequence of one Class/Instance pair describing RT Plan associated with dose. Required if Dose Summation Type (3004,000A) is PLAN, FRACTION, BEAM, BRACHY or CONTROL_POINT. Only a single item shall be permitted in this sequence. See Note 1.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="300C" element="0020" name="&gt;Referenced Fraction Group Sequence" type="1C">
      <description>Introduces sequence of one Fraction Group containing beams or brachy application setups contributing to dose. Required if Dose Summation Type (3004,000A) is FRACTION, BEAM, BRACHY or CONTROL_POINT. Only a single item shall be permitted in this sequence. See Note 1.</description>
    </entry>
    <entry group="300C" element="0022" name="&gt;&gt;Referenced Fraction Group Number" type="1">
      <description>Uniquely identifies Fraction Group specified by Fraction Group Number (300A,0071) in Fraction Group Sequence of RT Fraction Scheme Module within RT Plan referenced in Referenced RT Plan Sequence (300C,0002).</description>
    </entry>
    <entry group="300C" element="0004" name="&gt;&gt;Referenced Beam Sequence" type="1C">
      <description>Introduces sequence of Beams in current Fraction Group contributing to dose. Required if Dose Summation Type (3004,000A) is BEAM or CONTROL_POINT. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300C" element="0006" name="&gt;&gt;&gt;Referenced Beam Number" type="1">
      <description>Uniquely identifies Beam specified by Beam Number (300A,00C0) in Beam Sequence of RT Beams Module within RT Plan referenced in Referenced RT Plan Sequence (300C,0002).</description>
    </entry>
    <entry group="300C" element="00F2" name="&gt;&gt;&gt;Referenced Control Point Sequence" type="1C">
      <description>Sequence defining the Control Points in current Beam contributing to dose.
Required if Dose Summation Type (3004,000A) is CONTROL_POINT.
Only a single item shall be present in this sequence.</description>
    </entry>
    <entry group="300C" element="00F4" name="&gt;&gt;&gt;&gt;Referenced Start Control Point Index" type="1">
      <description>Identifies Control Point specified by Control Point Index (300A,0112) within Beam referenced by Referenced Beam Number (300C,0006). This is the first of the two Control Points from which the Dose contribution to the Control Point can be calculated.</description>
    </entry>
    <entry group="300C" element="00F6" name="&gt;&gt;&gt;&gt;Referenced Stop Control Point Index" type="1">
      <description>Identifies Control Point specified by Control Point Index (300A,0112) within Beam referenced by Referenced Beam Number (300C,0006). This is the second of the two Control Points from which the Dose contribution to the Control Point can be calculated.
The Control Point Index (300A,0112) referenced by Referenced
Stop Control Point Index (300C,00F6) shall be the Control Point Index (300A,0112) immediately following the Control Point Index (300A,0112) referenced by Referenced Start Control Point Index (300C,00F4) within the Referenced Beam Number (300C,0006).</description>
    </entry>
    <entry group="300C" element="000A" name="&gt;&gt;Referenced Brachy Application Setup Sequence" type="1C">
      <description>Introduces sequence of Brachy Application Setups in current Fraction Group contributing to dose. Required if Dose Summation Type (3004,000A) is BRACHY. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300C" element="000C" name="&gt;&gt;&gt;Referenced Brachy Application Setup Number" type="1">
      <description>Uniquely identifies Brachy Application Setup specified by Brachy Application Setup Number (300A,0234) in Brachy Application Setup Sequence (300A,0230) of RT Brachy Application Setups Module within RT Plan referenced in Referenced RT Plan Sequence (300C,0002).</description>
    </entry>
    <entry group="3004" element="000C" name="Grid Frame Offset Vector" type="1C">
      <description>An array which contains the dose image plane offsets (in mm) of the dose image frames in a multi-frame dose. Required if multi-frame pixel data are present and Frame Increment Pointer (0028,0009) points to Grid Frame Offset Vector (3004,000C). See C.8.8.3.2.</description>
      <section ref="C.8.8.3.2" name="">Grid Frame Offset Vector (3004,000C) shall be provided if a dose distribution is sent as a multi-frame image. Values of the Grid Frame Offset Vector (3004,000C) shall vary monotonically and are to be interpreted as follows:
a.  If Grid Frame Offset Vector (3004,000C) is present and its first element is zero, this attribute contains an array of n elements indicating the plane location of the data in the right-handed image coordinate system, relative to the position of the first dose plane transmitted, i.e., the point at which the Image Position (Patient) (0020,0032) attribute is defined, with positive offsets in the direction of the cross product of the row and column directions.
b.  If Grid Frame Offset Vector (3004,000C) is present, its first element is equal to the third element of Image Position (Patient) (0020,0032), and Image Orientation (Patient) (0020,0037) has the value (1,0,0,0,1,0), then Grid Frame Offset Vector contains an array of n elements indicating the plane location (patient z coordinate) of the data in the patient coordinate system.

In future implementations, use of option a) is strongly recommended.
This attribute is conditional since the RT Dose module may be included even if pixel doses are not being transmitted, or the image may be a single-frame image. If the Multi-frame Module is present, Frame Increment Pointer (0028,0009) shall have the Enumerated Value of 3004000C (Grid Frame Offset Vector).
Note:  Option (a) can represent a rectangular-parallelepiped dose grid with any orientation with respect to the patient, while option (b) can only represent a rectangular-parallelepiped dose grid whose planes are in the transverse patient dimension and whose x- and y-axes are parallel to the patient x- and y-axes.
  Example: Figure C.8.8.3-1 shows an example of plane positions for a dose grid with transverse planes.



Figure C.8.8.3-1 Dose Grid Frame Example
  For this example, Table C.8.39b gives the values of elements in the Grid Frame Offset Vector (3004,000C) for both relative (option (a)) and absolute (option (b)) interpretations, under the following conditions:
  1. The value of Image Orientation (Patient) (0020,0037) is (1,0,0,0,1,0). I.e., the dose grid is transverse with x- and y-axes parallel to the patient x- and y-axes;
  2. The value of Image Position (Patient) (0020,0032), i.e. the position of the first element of the dose grid, is (4, 5, 6); and
  3. The spacing between adjacent dose grid planes is 2mm (uniform).

Table C.8-39b. Values of Dose Grid Frame Offset Vector under
Relative (a) and Absolute (b) Interpretations
<unrecognized-rows><term value="Grid Frame Offset Vector Element" meaning="Option (a) Relative Coordinates"/><term value="Z1" meaning="0"/><term value="Z2" meaning="2"/><term value="Z3" meaning="4"/><term value="ZN" meaning="2(N-1)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="3004" element="000E" name="Dose Grid Scaling" type="1">
      <description>Scaling factor that when multiplied by the dose grid data found in the Pixel Data (7FE0,0010) attribute of the Image Pixel Module, yields grid doses in the dose units as specified by Dose Units (3004,0002).</description>
    </entry>
    <entry group="3004" element="0014" name="Tissue Heterogeneity Correction" type="3">
      <description>Specifies a list of patient heterogeneity characteristics used for calculating dose. This Atttibute shall be multi-valued if beams used to compute the dose have differing correction techniques. Enumerated Values:
IMAGE = image data
ROI_OVERRIDE = one or more ROI densities override image or water values where they exist
WATER = entire volume treated as water equivalent</description>
    </entry>
  </module>
  <module ref="C.8.8.4" table="C.8-40" name="RT Dvh Module Attributes">
    <entry group="300C" element="0060" name="Referenced Structure Set Sequence" type="1">
      <description>Introduces sequence of one class/instance pair describing Structure Set containing structures which are used to calculate Dose-Volume Histograms (DVHs). Only a single item shall be permitted in this sequence. See C.8.8.4.1.</description>
      <section ref="C.8.8.4.1" name="">The Referenced Structure Set Sequence (300C,0060) is required for direct cross-reference of the dose bin data with the corresponding ROI(s) from which they were derived. ROIs referenced by the DVH Referenced ROI Sequence (3004,0050) shall only contain contours with a Contour Geometric Type (3006,0042) of POINT or CLOSED_PLANAR.
</section>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="3004" element="0040" name="DVH Normalization Point" type="3">
      <description>Coordinates (x, y, z) of common DVH normalization point in the patient based coordinate system described in C.7.6.2.1.1 (mm).</description>
    </entry>
    <entry group="3004" element="0042" name="DVH Normalization Dose Value" type="3">
      <description>Dose Value at DVH Normalization Point (3004,0040) used as reference for individual DVHs when Dose Units (3004,0002) is RELATIVE.</description>
    </entry>
    <entry group="3004" element="0050" name="DVH Sequence" type="1">
      <description>Introduces sequence of DVHs. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="3004" element="0060" name="&gt;DVH Referenced ROI Sequence" type="1">
      <description>Introduces sequence of referenced ROIs used to calculate DVH. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="3006" element="0084" name="&gt;&gt;Referenced ROI Number" type="1">
      <description>Uniquely identifies ROI used to calculate DVH specified by ROI Number (3006,0022) in Structure Set ROI Sequence (3006,0020) in Structure Set Module within RT Structure Set referenced by referenced RT Plan in Referenced RT Plan Sequence (300C,0002) in RT Dose Module.</description>
    </entry>
    <entry group="3004" element="0062" name="&gt;&gt;DVH ROI Contribution Type" type="1">
      <description>Specifies whether volume within ROI is included or excluded in DVH. See C.8.8.4.2. Enumerated Values: INCLUDED, EXCLUDED.</description>
      <section ref="C.8.8.4.2" name="">The volume used to calculate the DVH shall be the geometric union of ROIs where DVH ROI Contribution Type (3004,0062) is INCLUDED, minus the geometric union of ROIs where DVH ROI Contribution Type (3004,0062) is EXCLUDED.
</section>
    </entry>
    <entry group="3004" element="0001" name="&gt;DVH Type" type="1">
      <description>Type of DVH.
Enumerated Values:
DIFFERENTIAL = differential dose-volume histogram
CUMULATIVE = cumulative dose-volume histogram
NATURAL = natural dose volume histogram</description>
    </entry>
    <entry group="3004" element="0002" name="&gt;Dose Units" type="1">
      <description>Dose axis units.
Enumerated Values:
GY = Gray
RELATIVE = dose relative to reference value specified in DVH Normalization Dose Value (3004,0042)</description>
    </entry>
    <entry group="3004" element="0004" name="&gt;Dose Type" type="1">
      <description>Type of dose.
Defined Terms:
PHYSICAL = physical dose
EFFECTIVE = physical dose after correction for biological effect using user-defined modeling technique
ERROR = difference between desired and planned dose</description>
    </entry>
    <entry group="3004" element="0052" name="&gt;DVH Dose Scaling" type="1">
      <description>Scaling factor that when multiplied by the dose bin widths found in DVH Data (3004,0058), yields dose bin widths in the dose units as specified by Dose Units (3004,0002).</description>
    </entry>
    <entry group="3004" element="0054" name="&gt;DVH Volume Units" type="1">
      <description>Volume axis units.
Defined Terms:
CM3 = cubic centimeters
PERCENT = percent
PER_U= volume per u with u(dose)=dose-3/2. See C.8.8.4.3.</description>
      <section ref="C.8.8.4.3" name="">The unit PER_U is defined in: Anderson, LL: “A “natural” volume-dose histogram for brachytherapy”, Medical Physics 13(6) pp 898-903, 1986.
</section>
    </entry>
    <entry group="3004" element="0056" name="&gt;DVH Number of Bins" type="1">
      <description>Number of bins n used to store DVH Data (3004,0058).</description>
    </entry>
    <entry group="3004" element="0058" name="&gt;DVH Data" type="1">
      <description>A data stream describing the dose bin widths Dn and associated volumes Vn in DVH Volume Units (3004,0054) in the order D1V1, D2V2, ... DnVn.
Note: DVH Data arrays may not be properly encoded if Explicit-VR transfer syntax is used and the VL of this attribute exceeds 65534 bytes.</description>
    </entry>
    <entry group="3004" element="0070" name="&gt;DVH Minimum Dose" type="3">
      <description>Minimum calculated dose to ROI(s) described by DVH Referenced ROI Sequence (3004,0060).</description>
    </entry>
    <entry group="3004" element="0072" name="&gt;DVH Maximum Dose" type="3">
      <description>Maximum calculated dose to ROI(s) described by DVH Referenced ROI Sequence (3004,0060).</description>
    </entry>
    <entry group="3004" element="0074" name="&gt;DVH Mean Dose" type="3">
      <description>Mean calculated dose to ROI(s) described by DVH Referenced ROI Sequence (3004,0060).</description>
    </entry>
  </module>
  <module ref="C.8.8.5" table="C.8-41" name="Structure Set Module Attributes">
    <entry group="3006" element="0002" name="Structure Set Label" type="1">
      <description>User-defined label for Structure Set.</description>
    </entry>
    <entry group="3006" element="0004" name="Structure Set Name" type="3">
      <description>User-defined name for Structure Set.</description>
    </entry>
    <entry group="3006" element="0006" name="Structure Set Description" type="3">
      <description>User-defined description for Structure Set.</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="3">
      <description>A number that identifies this object instance.</description>
    </entry>
    <entry group="3006" element="0008" name="Structure Set Date" type="2">
      <description>Date at which Structure Set was last modified.</description>
    </entry>
    <entry group="3006" element="0009" name="Structure Set Time" type="2">
      <description>Time at which Structure Set was last modified.</description>
    </entry>
    <entry group="3006" element="0010" name="Referenced Frame of Reference Sequence" type="3">
      <description>Introduces sequence of items describing Frames of Reference in which the ROIs are defined. One or more items may be included in this sequence. See C.8.8.5.1.</description>
      <section ref="C.8.8.5.1" name="">The Referenced Frame of Reference Sequence (3006,0010) describes a set of frames of reference in which some or all of the ROIs are expressed. Since the Referenced Frame of Reference UID (3006,0024) is required for each ROI, each frame of reference used to express the coordinates of an ROI shall be listed in the Referenced Frame of Reference Sequence (3006,0010) once and only once.
Notes:  1.As an example, a set of ROIs defined using a single image series would list the image series in a single Referenced Frame of Reference Sequence (3006,0010) item, providing the UID for this referenced frame of reference (obtained from the source images), and listing all pertinent images in the Contour Image Sequence (3006,0016).
  2. As an example, a set of ROIs containing ROIs referencing more than one frame of reference would list the referenced images in two or more different Referenced Frame of Reference Sequence (3006,0010) items, providing in each case the UID for this referenced frame of reference (obtained from the source images), and listing all pertinent images in the Contour Image Sequence (3006,0016). Each ROI would then reference the appropriate Frame of Reference UID (0020,0052).

</section>
    </entry>
    <entry group="0020" element="0052" name="&gt;Frame of Reference UID" type="1">
      <description>Uniquely identifies Frame of Reference within Structure Set.</description>
    </entry>
    <entry group="3006" element="00C0" name="&gt;Frame of Reference Relationship Sequence" type="3">
      <description>Introduces sequence of transforms that relate other Frames of Reference to this Frame of Reference. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="3006" element="00C2" name="&gt;&gt;Related Frame of Reference UID" type="1">
      <description>Frame of Reference Coordinate System to be transformed to the current Frame of Reference.</description>
    </entry>
    <entry group="3006" element="00C4" name="&gt;&gt;Frame of Reference Transformation Type" type="1C">
      <description>Type of Transformation. Required if Frame of Reference Relationship Sequence (3006,00C0) is sent.
Defined Terms:
HOMOGENEOUS</description>
    </entry>
    <entry group="3006" element="00C6" name="&gt;&gt;Frame of Reference Transformation Matrix" type="1">
      <description>Four-by-four transformation Matrix from Related Frame of Reference to current Frame of Reference. Matrix elements shall be listed in row-major order. See C.8.8.5.2.</description>
      <section ref="C.8.8.5.2" name="">In a rigid body system, two coordinate systems can be related using a single 4 x 4 transformation matrix to describe any rotations and/or translations necessary to transform coordinates from the related coordinate system (frame of reference) to the primary system. The equation performing the transform from a point (X’,Y’,Z’) in the related coordinate system to a point (X,Y,Z) in the current coordinate system can be shown as follows, where for homogeneous transforms M41 = M42 = M43 = 0 and M44 = 1:
X    M11 M12 M13 M14    X’
Y  =  M21 M22 M23 M24  x  Y’
Z    M31 M32 M33 M34    Z’
1    M41 M42 M43 M44    1
</section>
    </entry>
    <entry group="3006" element="00C8" name="&gt;&gt;Frame of Reference Transformation Comment" type="3">
      <description>Comment regarding the transformation between the related and current Frames of Reference.</description>
    </entry>
    <entry group="3006" element="0012" name="&gt;RT Referenced Study Sequence" type="3">
      <description>Introduces sequence of Studies containing series to be referenced. One or more items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="3006" element="0014" name="&gt;&gt;RT Referenced Series Sequence" type="1">
      <description>Introduces sequence of items describing series of images within the referenced study which are used in defining the Structure Set. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="0020" element="000E" name="&gt;&gt;&gt;Series Instance UID" type="1">
      <description>Unique identifier for the series containing the images.</description>
    </entry>
    <entry group="3006" element="0016" name="&gt;&gt;&gt;Contour Image Sequence" type="1">
      <description>Introduces sequence of items describing images in a given series used in defining the Structure Set (typically CT or MR images). One or more items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;&gt;&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="3006" element="0020" name="Structure Set ROI Sequence" type="3">
      <description>Introduces sequence of ROIs for current Structure Set. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="3006" element="0022" name="&gt;ROI Number" type="1">
      <description>Identification number of the ROI. The value of ROI Number (3006,0022) shall be unique within the Structure Set in which it is created.</description>
    </entry>
    <entry group="3006" element="0024" name="&gt;Referenced Frame of Reference UID" type="1">
      <description>Uniquely identifies Frame of Reference in which ROI is defined, specified by Frame of Reference UID (0020,0052) in Referenced Frame of Reference Sequence (3006,0010).</description>
    </entry>
    <entry group="3006" element="0026" name="&gt;ROI Name" type="2">
      <description>User-defined name for ROI.</description>
    </entry>
    <entry group="3006" element="0028" name="&gt;ROI Description" type="3">
      <description>User-defined description for ROI.</description>
    </entry>
    <entry group="3006" element="002C" name="&gt;ROI Volume" type="3">
      <description>Volume of ROI (cubic centimeters).</description>
    </entry>
    <entry group="3006" element="0036" name="&gt;ROI Generation Algorithm" type="2">
      <description>Type of algorithm used to generate ROI.
Defined Terms:
AUTOMATIC = calculated ROI
SEMIAUTOMATIC = ROI calculated with user assistance
MANUAL = user-entered ROI</description>
    </entry>
    <entry group="3006" element="0038" name="&gt;ROI Generation Description" type="3">
      <description>User-defined description of technique used to generate ROI.</description>
    </entry>
  </module>
  <module ref="C.8.8.6" table="C.8-42" name="ROI Contour Module Attributes">
    <entry group="3006" element="0039" name="ROI Contour Sequence" type="1">
      <description>Introduces sequence of Contour Sequences defining ROIs. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="3006" element="0084" name="&gt;Referenced ROI Number" type="1">
      <description>Uniquely identifies the referenced ROI described in the Structure Set ROI Sequence (3006,0020).</description>
    </entry>
    <entry group="3006" element="002A" name="&gt;ROI Display Color" type="3">
      <description>RGB triplet color representation for ROI, specified using the range 0-255.</description>
    </entry>
    <entry group="3006" element="0040" name="&gt;Contour Sequence" type="3">
      <description>Introduces sequence of Contours defining ROI. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="3006" element="0048" name="&gt;&gt;Contour Number" type="3">
      <description>Identification number of the contour. The value of Contour Number (3006,0048) shall be unique within the Contour Sequence (3006,0040) in which it is defined. No semantics or ordering shall be inferred from this attribute.</description>
    </entry>
    <entry group="3006" element="0049" name="&gt;&gt;Attached Contours" type="3">
      <description>List of Contour Number (3006,0048) defining lower-numbered contour(s) to which the current contour is connected.</description>
    </entry>
    <entry group="3006" element="0016" name="&gt;&gt;Contour Image Sequence" type="3">
      <description>Introduces sequence of images containing the contour. One or more items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="3006" element="0042" name="&gt;&gt;Contour Geometric Type" type="1">
      <description>Geometric type of contour. See C.8.8.6.1.
Enumerated Values:
POINT = single point
OPEN_PLANAR = open contour containing coplanar points
OPEN_NONPLANAR = open contour containing non-coplanar points
CLOSED_PLANAR = closed contour (polygon) containing coplanar points</description>
      <section ref="C.8.8.6.1" name="">A contour can be one of the following geometric types:
-    A Contour Geometric Type (3006,0042) of POINT indicates that the contour is a single point, defining a specific location of significance.
-    A Contour Geometric Type (3006,0042) of OPEN_PLANAR indicates that the last vertex shall not be connected to the first point, and that all points in Contour Data (3006,0050) shall be coplanar.
-    A Contour Geometric Type (3006,0042) of OPEN_NONPLANAR indicates that the last vertex shall not be connected to the first point, and that the points in Contour Data (3006,0050) may be non-coplanar. Contours having a Geometric Type (3006,0042) of OPEN_NONPLANAR can be used to represent objects best described by a single, possibly non-coplanar curve, such as a brachytherapy applicator.
-    A Contour Geometric Type (3006,0042) of CLOSED_PLANAR indicates that the last point shall be connected to the first point, where the first point is not repeated in the Contour Data (3006,0050). All points in Contour Data (3006,0050) shall be coplanar.
</section>
    </entry>
    <entry group="3006" element="0044" name="&gt;&gt;Contour Slab Thickness" type="3">
      <description>Thickness of slab (in mm) represented by contour, where the Contour Data (3006,0050) defines a plane in the center of the slab, offset by the Contour Offset Vector (3006,0045) if it is present. See C.8.8.6.2.</description>
      <section ref="C.8.8.6.2" name="">A set of Contour slabs may define a multi-slab Volume of Interest. Contour Slab Thickness (3006,0044) shall specify the thickness of a slab, the central plane of which shall be defined by the set of points offset from Contour Data (3006,0050) by the value of Contour Offset Vector (3006,0045). One contour slab may contain one to many sets of Contour Data (3006,0050) that may define regions of one complex Volume of Interest. If no valid value of Contour Slab Thickness (3006,0044) is sent, then the offset value shall be (0,0,0) and the original Contour Data (3006,0050) shall define the central plane of the Contour slab.
</section>
    </entry>
    <entry group="3006" element="0045" name="&gt;&gt;Contour Offset Vector" type="3">
      <description>Vector (x,y,z) in the the patient based coordinate system described in C.7.6.2.1.1 which is normal to plane of Contour Data (3006,0050), describing direction and magnitude of the offset (in mm) of each point of the central plane of a contour slab from the corresponding original point of Contour Data (3006,0050). See C.8.8.6.2.</description>
      <section ref="C.8.8.6.2" name="">A set of Contour slabs may define a multi-slab Volume of Interest. Contour Slab Thickness (3006,0044) shall specify the thickness of a slab, the central plane of which shall be defined by the set of points offset from Contour Data (3006,0050) by the value of Contour Offset Vector (3006,0045). One contour slab may contain one to many sets of Contour Data (3006,0050) that may define regions of one complex Volume of Interest. If no valid value of Contour Slab Thickness (3006,0044) is sent, then the offset value shall be (0,0,0) and the original Contour Data (3006,0050) shall define the central plane of the Contour slab.
</section>
    </entry>
    <entry group="3006" element="0046" name="&gt;&gt;Number of Contour Points" type="1">
      <description>Number of points (triplets) in Contour Data (3006,0050).</description>
    </entry>
    <entry group="3006" element="0050" name="&gt;&gt;Contour Data" type="1">
      <description>Sequence of (x,y,z) triplets defining a contour in the patient based coordinate system described in C.7.6.2.1.1 (mm). See C.8.8.6.1 and C.8.8.6.3.
Note: Contour Data may not be properly encoded if Explicit-VR transfer syntax is used and the VL of this attribute exceeds 65534 bytes.</description>
      <section ref="C.8.8.6.1" name="">A contour can be one of the following geometric types:
-    A Contour Geometric Type (3006,0042) of POINT indicates that the contour is a single point, defining a specific location of significance.
-    A Contour Geometric Type (3006,0042) of OPEN_PLANAR indicates that the last vertex shall not be connected to the first point, and that all points in Contour Data (3006,0050) shall be coplanar.
-    A Contour Geometric Type (3006,0042) of OPEN_NONPLANAR indicates that the last vertex shall not be connected to the first point, and that the points in Contour Data (3006,0050) may be non-coplanar. Contours having a Geometric Type (3006,0042) of OPEN_NONPLANAR can be used to represent objects best described by a single, possibly non-coplanar curve, such as a brachytherapy applicator.
-    A Contour Geometric Type (3006,0042) of CLOSED_PLANAR indicates that the last point shall be connected to the first point, where the first point is not repeated in the Contour Data (3006,0050). All points in Contour Data (3006,0050) shall be coplanar.
</section>
    </entry>
  </module>
  <module ref="C.8.8.7" table="C.8-43" name="RT Dose ROI Module Attributes">
    <entry group="3004" element="0010" name="RT Dose ROI Sequence" type="1">
      <description>Introduces sequence of items specifying dose levels for isodose curves or dose points described in the ROI module. One or more items may be included in this sequence. See C.8.8.7.1.</description>
      <section ref="C.8.8.7.1" name="">ROIs referenced in the RT Dose ROI Module shall have a Contour Geometric Type (3006,0042) of POINT, OPEN_PLANAR or CLOSED_PLANAR.
</section>
    </entry>
    <entry group="3006" element="0084" name="&gt;Referenced ROI Number" type="1">
      <description>Uniquely identifies the referenced ROI within the current RT Dose. See Note 1 and C.8.8.7.2.</description>
    </entry>
    <entry group="3004" element="0002" name="&gt;Dose Units" type="1">
      <description>Units used for ROI Dose.
Enumerated Values:
GY = Gray
RELATIVE = dose relative to implicit reference value</description>
    </entry>
    <entry group="3004" element="0012" name="&gt;Dose Value" type="1">
      <description>Dose value for ROI, in units defined by Dose Units (3004,0002). See C.8.8.7.3.</description>
      <section ref="C.8.8.7.3" name="">Dose Value (3004,0012) shall be the dose value corresponding to the referenced isodose curve, named dose point, or unnamed dose point.
</section>
    </entry>
  </module>
  <module ref="C.8.8.8" table="C.8-44" name="RT ROI Observations Module Attributes">
    <entry group="3006" element="0080" name="RT ROI Observations Sequence" type="1">
      <description>Introduces sequence of observations related to ROIs defined in the ROI Module. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="3006" element="0082" name="&gt;Observation Number" type="1">
      <description>Identification number of the Observation. The value of Observation Number (3006,0082) shall be unique within the RT ROI Observations Sequence (3006,0080).</description>
    </entry>
    <entry group="3006" element="0084" name="&gt;Referenced ROI Number" type="1">
      <description>Uniquely identifies the referenced ROI described in the Structure Set ROI Sequence (3006,0020).</description>
    </entry>
    <entry group="3006" element="0085" name="&gt;ROI Observation Label" type="3">
      <description>User-defined label for ROI Observation.</description>
    </entry>
    <entry group="3006" element="0088" name="&gt;ROI Observation Description" type="3">
      <description>User-defined description for ROI Observation.</description>
    </entry>
    <entry group="3006" element="0030" name="&gt;RT Related ROI Sequence" type="3">
      <description>Introduces sequence of significantly related ROIs, e.g. CTVs contained within a PTV. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="3006" element="0084" name="&gt;&gt;Referenced ROI Number" type="1">
      <description>Uniquely identifies the related ROI described in the Structure Set ROI Sequence (3006,0020).</description>
    </entry>
    <entry group="3006" element="0033" name="&gt;&gt;RT ROI Relationship" type="3">
      <description>Relationship of referenced ROI with respect to referencing ROI.
Defined Terms:
SAME = ROIs represent the same entity
ENCLOSED = referenced ROI completely encloses referencing ROI
ENCLOSING = referencing ROI completely encloses referenced ROI</description>
    </entry>
    <entry group="3006" element="0086" name="&gt;RT ROI Identification Code Sequence" type="3">
      <description>Introduces sequence containing Code used to identify ROI. If this sequence is included, only one item shall be present. Baseline Context ID Number = 96. See Section 5.3 for further explanation.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 96 ."/>
    <entry group="3006" element="00A0" name="&gt;Related RT ROI Observations Sequence" type="3">
      <description>Introduces sequence of related ROI Observations. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="3006" element="0082" name="&gt;&gt;Observation Number" type="1">
      <description>Uniquely identifies a related ROI Observation.</description>
    </entry>
    <entry group="3006" element="00A4" name="&gt;RT ROI Interpreted Type" type="2">
      <description>Type of ROI. See C.8.8.8.1.
Defined Terms:
EXTERNAL = external patient contour
PTV = Planning Target Volume (as defined in ICRU50)
CTV = Clinical Target Volume (as defined in ICRU50)
GTV = Gross Tumor Volume (as defined in ICRU50)
TREATED_VOLUME = Treated Volume (as defined in ICRU50)
IRRAD_VOLUME = Irradiated Volume (as defined in ICRU50)
BOLUS = patient bolus to be used for external beam therapy
AVOIDANCE = region in which dose is to be minimized
ORGAN = patient organ
MARKER = patient marker or marker on a localizer
REGISTRATION = registration ROI
ISOCENTER = treatment isocenter to be used for external beam therapy
CONTRAST_AGENT = volume into which a contrast agent has been injected
CAVITY = patient anatomical cavity
BRACHY_CHANNEL = brachytherapy channel
BRACHY_ACCESSORY = brachytherapy accessory device
BRACHY_SRC_APP = brachytherapy source applicator
BRACHY_CHNL_SHLD = brachytherapy channel shield
SUPPORT = external patient support device
FIXATION = external patient fixation or immobilisation device
DOSE_REGION = ROI to be used as a dose reference
CONTROL = ROI to be used in control of dose optimization and calculation</description>
      <section ref="C.8.8.8.1" name="">RT ROI Interpreted Type (3006,00A4) shall describe the class of ROI (e.g. CTV, PTV). Individual instances of each class of structure (e.g. CTV1, CTV2) can be distinguished using ROI Observation Label (3006,0085).
</section>
    </entry>
    <entry group="3006" element="00A6" name="&gt;ROI Interpreter" type="2">
      <description>Name of person performing the interpretation.</description>
    </entry>
    <entry group="300A" element="00E1" name="&gt;Material ID" type="3">
      <description>User-supplied identifier for ROI material.</description>
    </entry>
    <entry group="3006" element="00B0" name="&gt;ROI Physical Properties Sequence" type="3">
      <description>Introduces sequence describing physical properties associated with current ROI interpretation. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="3006" element="00B2" name="&gt;&gt;ROI Physical Property" type="1">
      <description>Physical property specified by ROI Physical Property Value (3006,00B4).
Defined Terms:
REL_MASS_DENSITY = mass density relative to water
REL_ELEC_DENSITY = electron density relative to water
EFFECTIVE_Z = effective atomic number
EFF_Z_PER_A = ratio of effective atomic number to mass (AMU-1)
REL_STOP_RATIO = linear stopping power ratio relative to water
ELEM_FRACTION = elemental composition of the material</description>
    </entry>
    <entry group="3006" element="00B6" name="&gt;&gt;ROI Elemental Composition Sequence" type="1C">
      <description>The elemental composition of the ROI and the atomic mass fraction of the elements in the ROI.
Required if ROI Physical Property (3006,00B2) equals ELEM_FRACTION.
One or more items may be included in this sequence.</description>
    </entry>
    <entry group="3006" element="00B7" name="&gt;&gt;&gt;ROI Elemental Composition Atomic Number" type="1">
      <description>The atomic number of the element for which the ROI Elemental Composition Sequence (3006,00B6) is sent.</description>
    </entry>
    <entry group="3006" element="00B8" name="&gt;&gt;&gt;ROI Elemental Composition Atomic Mass Fraction" type="1">
      <description>The fractional weight of the element for which the ROI Elemental Composition Sequence (3006,00B6) is sent.
The sum of all ROI Elemental Composition Atomic Mass Fractions (3006,00B8) sent in the ROI Elemental Composition Sequence (3006,00B6) shall equal 1.0 within acceptable limits of floating point precision.</description>
    </entry>
    <entry group="3006" element="00B4" name="&gt;&gt;ROI Physical Property Value" type="1">
      <description>User-assigned value for physical property.</description>
    </entry>
  </module>
  <module ref="C.8.8.9" table="C.8-45" name="RT General Plan Module Attributes">
    <entry group="300A" element="0002" name="RT Plan Label" type="1">
      <description>User-defined label for treatment plan.</description>
    </entry>
    <entry group="300A" element="0003" name="RT Plan Name" type="3">
      <description>User-defined name for treatment plan.</description>
    </entry>
    <entry group="300A" element="0004" name="RT Plan Description" type="3">
      <description>User-defined description of treatment plan.</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="3">
      <description>A number that identifies this object instance.</description>
    </entry>
    <entry group="0008" element="1070" name="Operators' Name" type="2">
      <description>Name of operator(s) creating treatment plan.</description>
    </entry>
    <entry group="300A" element="0006" name="RT Plan Date" type="2">
      <description>Date treatment plan was last modified.</description>
    </entry>
    <entry group="300A" element="0007" name="RT Plan Time" type="2">
      <description>Time treatment plan was last modified.</description>
    </entry>
    <entry group="300A" element="0009" name="Treatment Protocols" type="3">
      <description>Planned treatment protocols.</description>
    </entry>
    <entry group="300A" element="000A" name="Plan Intent" type="3">
      <description>Intent of this plan.
Defined Terms:
CURATIVE = curative therapy on patient
PALLIATIVE = palliative therapy on patient
PROPHYLACTIC = preventative therapy on patient
VERIFICATION = verification of patient plan using phantom
MACHINE_QA= Quality assurance of the delivery machine (independently of a specific patient)
RESEARCH = Research project
SERVICE = Machine repair or maintenance operation</description>
    </entry>
    <entry group="300A" element="000B" name="Treatment Sites" type="3">
      <description>Planned treatment sites.</description>
    </entry>
    <entry group="300A" element="000C" name="RT Plan Geometry" type="1">
      <description>Describes whether RT Plan is based on patient or treatment device geometry. See C.8.8.9.1.
Defined Terms:
PATIENT = RT Structure Set exists
TREATMENT_DEVICE = RT Structure Set does not exist</description>
      <section ref="C.8.8.9.1" name="">An RT Plan Geometry (300A,000C) of PATIENT shall signify that an RT Structure Set has been defined upon which the plan geometry is based, and this RT Structure Set shall be specified in the Referenced Structure Set Sequence (300C,0060). An RT Plan Geometry (300A,000C) of TREATMENT_DEVICE shall indicate that no patient geometry is available, and that the RT Plan is being defined with respect to the IEC FIXED Coordinate System.
</section>
    </entry>
    <entry group="300C" element="0060" name="Referenced Structure Set Sequence" type="1C">
      <description>Introduces sequence of one Class/Instance pair describing instance of RT Structure Set on which the RT Plan is based. Only a single item shall be permitted in this sequence. Required if RT Plan Geometry (300A,000C) is PATIENT.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="300C" element="0080" name="Referenced Dose Sequence" type="3">
      <description>Introduces sequence of related SOP Class/Instance pairs describing related instances of RT Dose (for grids and named/unnamed point doses). One or more items may be included in this sequence. See Note 1.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="300C" element="0002" name="Referenced RT Plan Sequence" type="3">
      <description>Introduces sequence of related SOP Class/Instance pairs describing related instances of RT Plan. One or more items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="300A" element="0055" name="&gt;RT Plan Relationship" type="1">
      <description>Relationship of referenced plan with respect to current plan.
Defined Terms:
PRIOR = plan delivered prior to current treatment
ALTERNATIVE = alternative plan prepared for current treatment
PREDECESSOR = plan used in derivation of current plan
VERIFIED_PLAN = plan which is verified using the current plan. This value shall only be used if Plan Intent (300A,000A) is present and has a value of VERIFICATION.</description>
    </entry>
  </module>
  <module ref="C.8.8.10" table="C.8-46" name="RT Prescription Module Attributes">
    <entry group="300A" element="000E" name="Prescription Description" type="3">
      <description>User-defined description of treatment prescription.</description>
    </entry>
    <entry group="300A" element="0010" name="Dose Reference Sequence" type="3">
      <description>Introduces sequence of Dose References. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="0012" name="&gt;Dose Reference Number" type="1">
      <description>Identification number of the Dose Reference. The value of Dose Reference Number (300A,0012) shall be unique within the RT Plan in which it is created.</description>
    </entry>
    <entry group="300A" element="0013" name="&gt;Dose Reference UID" type="3">
      <description>A unique identifier for a Dose Reference that can be used to link the same entity across multiple RT Plan objects.</description>
    </entry>
    <entry group="300A" element="0014" name="&gt;Dose Reference Structure Type" type="1">
      <description>Structure type of Dose Reference.
Defined Terms:
POINT = dose reference point specified as ROI
VOLUME = dose reference volume specified as ROI
COORDINATES = point specified by Dose Reference Point Coordinates (300A,0018)
SITE = dose reference clinical site</description>
    </entry>
    <entry group="300A" element="0016" name="&gt;Dose Reference Description" type="3">
      <description>User-defined description of Dose Reference.</description>
    </entry>
    <entry group="3006" element="0084" name="&gt;Referenced ROI Number" type="1C">
      <description>Uniquely identifies ROI representing the dose reference specified by ROI Number (3006,0022) in Structure Set ROI Sequence (3006,0020) in Structure Set Module within RT Structure Set in Referenced Structure Set Sequence (300C,0060) in RT General Plan Module. Required if Dose Reference Structure Type (300A,0014) is POINT or VOLUME.</description>
    </entry>
    <entry group="300A" element="0018" name="&gt;Dose Reference Point Coordinates" type="1C">
      <description>Coordinates (x,y,z) of Reference Point in the patient based coordinate system described in C.7.6.2.1.1 (mm). Required if Dose Reference Structure Type (300A,0014) is COORDINATES.</description>
    </entry>
    <entry group="300A" element="001A" name="&gt;Nominal Prior Dose" type="3">
      <description>Dose (in Gy) from prior treatment to this Dose Reference (e.g. from a previous course of treatment).</description>
    </entry>
    <entry group="300A" element="0020" name="&gt;Dose Reference Type" type="1">
      <description>Type of Dose Reference.
Defined Terms:
TARGET = treatment target (corresponding to GTV, PTV, or CTV in ICRU50)
ORGAN_AT_RISK = Organ at Risk (as defined in ICRU50)</description>
    </entry>
    <entry group="300A" element="0021" name="&gt;Constraint Weight" type="3">
      <description>Relative importance of satisfying constraint, where high values represent more important constraints.</description>
    </entry>
    <entry group="300A" element="0022" name="&gt;Delivery Warning Dose" type="3">
      <description>The dose (in Gy) which when reached or exceeded should cause some action to be taken.</description>
    </entry>
    <entry group="300A" element="0023" name="&gt;Delivery Maximum Dose" type="3">
      <description>The maximum dose (in Gy) which can be delivered to the dose reference.</description>
    </entry>
    <entry group="300A" element="0025" name="&gt;Target Minimum Dose" type="3">
      <description>Minimum permitted dose (in Gy) to Dose Reference if Dose Reference Type (300A,0020) is TARGET.</description>
    </entry>
    <entry group="300A" element="0026" name="&gt;Target Prescription Dose" type="3">
      <description>Prescribed dose (in Gy) to Dose Reference if Dose Reference Type (300A,0020) is TARGET.</description>
    </entry>
    <entry group="300A" element="0027" name="&gt;Target Maximum Dose" type="3">
      <description>Maximum permitted dose (in Gy) to Dose Reference if Dose Reference Type (300A,0020) is TARGET.</description>
    </entry>
    <entry group="300A" element="0028" name="&gt;Target Underdose Volume Fraction" type="3">
      <description>Maximum permitted fraction (in percent) of Target to receive less than the Target Prescription Dose if Dose Reference Type (300A,0020) is TARGET and Dose Reference Structure Type (300A,0014) is VOLUME. See C.8.8.10.1.</description>
      <section ref="C.8.8.10.1" name="">If the Target Underdose Volume Fraction (300A,0028) is not present, it shall be interpreted as zero.
</section>
    </entry>
    <entry group="300A" element="002A" name="&gt;Organ at Risk Full-volume Dose" type="3">
      <description>Maximum dose (in Gy) to entire Dose Reference if Dose Reference Type (300A,0020) is ORGAN_AT_RISK and Dose Reference Structure Type (300A,0014) is VOLUME.</description>
    </entry>
    <entry group="300A" element="002B" name="&gt;Organ at Risk Limit Dose" type="3">
      <description>Maximum permitted dose (in Gy) to any part of Dose Reference if Dose Reference Type (300A,0020) is ORGAN_AT_RISK and Dose Reference Structure Type (300A,0014) is VOLUME.</description>
    </entry>
    <entry group="300A" element="002C" name="&gt;Organ at Risk Maximum Dose" type="3">
      <description>Maximum dose (in Gy) to non-overdosed part of Dose Reference if Dose Reference Type (300A,0020) is ORGAN_AT_RISK and Dose Reference Structure Type (300A,0014) is VOLUME.</description>
    </entry>
    <entry group="300A" element="002D" name="&gt;Organ at Risk Overdose Volume Fraction" type="3">
      <description>Maximum permitted fraction (in percent) of the Organ at Risk to receive more than the Organ at Risk Maximum Dose if Dose Reference Type (300A,0020) is ORGAN_AT_RISK and Dose Reference Structure Type (300A,0014) is VOLUME.</description>
    </entry>
  </module>
  <module ref="C.8.8.11" table="C.8-47" name="RT Tolerance Tables Module Attributes">
    <entry group="300A" element="0040" name="Tolerance Table Sequence" type="3">
      <description>Introduces sequence of tolerance tables to be used for delivery of treatment plan. One or more items may be included in this sequence. See Note 1.</description>
    </entry>
    <entry group="300A" element="0042" name="&gt;Tolerance Table Number" type="1C">
      <description>Identification number of the Tolerance Table. The value of Tolerance Table Number (300A,0042) shall be unique within the RT Plan in which it is created. Required if Tolerance Table Sequence (300A,0040) is sent.</description>
    </entry>
    <entry group="300A" element="0043" name="&gt;Tolerance Table Label" type="3">
      <description>User-defined label for Tolerance Table.</description>
    </entry>
    <entry group="300A" element="0044" name="&gt;Gantry Angle Tolerance" type="3">
      <description>Maximum permitted difference (in degrees) between planned and delivered Gantry Angle.</description>
    </entry>
    <entry group="300A" element="014E" name="&gt;Gantry Pitch Angle Tolerance" type="3">
      <description>Maximum permitted difference (in degrees) between planned and delivered Gantry Pitch Angle.</description>
    </entry>
    <entry group="300A" element="0046" name="&gt;Beam Limiting Device Angle Tolerance" type="3">
      <description>Maximum permitted difference (in degrees) between planned and delivered Beam Limiting Device Angle.</description>
    </entry>
    <entry group="300A" element="0048" name="&gt;Beam Limiting Device Tolerance Sequence" type="3">
      <description>Introduces sequence of beam limiting device (collimator) tolerances. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00B8" name="&gt;&gt;RT Beam Limiting Device Type" type="1C">
      <description>Type of beam limiting device (collimator). Required if Beam Limiting Device Tolerance Sequence (300A,0048) is sent.
Enumerated Values:
X = symmetric jaw pair in IEC X direction
Y = symmetric jaw pair in IEC Y direction
ASYMX = asymmetric jaw pair in IEC X direction
ASYMY = asymmetric pair in IEC Y direction
MLCX = multileaf (multi-element) jaw pair in IEC X direction
MLCY = multileaf (multi-element) jaw pair in IEC Y direction</description>
    </entry>
    <entry group="300A" element="004A" name="&gt;&gt;Beam Limiting Device Position Tolerance" type="1C">
      <description>Maximum permitted difference (in mm) between planned and delivered leaf (element) or jaw positions for current beam limiting device (collimator). Required if Beam Limiting Device Tolerance Sequence (300A,0048) is sent.</description>
    </entry>
    <entry group="300A" element="004C" name="&gt;Patient Support Angle Tolerance" type="3">
      <description>Maximum permitted difference (in degrees) between planned and delivered Patient Support Angle.</description>
    </entry>
    <entry group="300A" element="004E" name="&gt;Table Top Eccentric Angle Tolerance" type="3">
      <description>Maximum permitted difference (in degrees) between planned and delivered Table Top Eccentric Angle.</description>
    </entry>
    <entry group="300A" element="004F" name="&gt;Table Top Pitch Angle Tolerance" type="3">
      <description>Maximum permitted difference (in degrees) between the planned and delivered Table Top Pitch Angle.</description>
    </entry>
    <entry group="300A" element="0050" name="&gt;Table Top Roll Angle Tolerance" type="3">
      <description>Maximum permitted difference (in degrees) between the planned and delivered Table Top Roll Angle.</description>
    </entry>
    <entry group="300A" element="0051" name="&gt;Table Top Vertical Position Tolerance" type="3">
      <description>Maximum permitted difference (in mm) between planned and delivered Table Top Vertical Position.</description>
    </entry>
    <entry group="300A" element="0052" name="&gt;Table Top Longitudinal Position Tolerance" type="3">
      <description>Maximum permitted difference (in mm) between planned and delivered Table Top Longitudinal Position.</description>
    </entry>
    <entry group="300A" element="0053" name="&gt;Table Top Lateral Position Tolerance" type="3">
      <description>Maximum permitted difference (in mm) between planned and delivered Table Top Lateral Position.</description>
    </entry>
  </module>
  <module ref="C.8.8.12" table="C.8-48" name="RT Patient Setup Module Attributes">
    <entry group="300A" element="0180" name="Patient Setup Sequence" type="1">
      <description>Introduces sequence of patient setup data for current plan. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="0182" name="&gt;Patient Setup Number" type="1">
      <description>Identification number of the Patient Setup. The value of Patient Setup Number (300A,0182) shall be unique within the RT Plan in which it is created.</description>
    </entry>
    <entry group="300A" element="0183" name="&gt;Patient Setup Label" type="3">
      <description>The user-defined label for the patient setup.</description>
    </entry>
    <entry group="0018" element="5100" name="&gt;Patient Position" type="1C">
      <description>Patient position descriptor relative to the equipment. Required if Patient Additional Position (300A,0184) is not present. See Section C.8.8.12.1.2 for Defined Terms and further explanation.</description>
      <section ref="C.8.8.12.1.2" name="">Defined Terms for Patient Position shall be those specified in Section C.7.3.1.1.2, plus the following:
  SITTING
In the sitting position, the patient’s face is towards the front of the chair.
</section>
    </entry>
    <entry group="300A" element="0184" name="&gt;Patient Additional Position" type="1C">
      <description>User-defined additional description of patient position. Required if Patient Position (0018,5100) is not present.</description>
    </entry>
    <entry group="300A" element="0401" name="&gt;Referenced Setup Image Sequence" type="3">
      <description>Introduces sequence of setup verification images for this patient setup. One or more items may be included in this sequence. See C.8.8.12.1.1</description>
      <section ref="C.8.8.12.1.1" name="">Images with modality SC or VL serve as visible light photos for visual setup control. Images with modality RTIMAGE serve as reference images on plan level. RT Images present in this sequence shall not be referenced in the Referenced Reference Image Sequence (300C,0042) of the RT Beams module.
</section>
    </entry>
    <entry group="300A" element="0402" name="&gt;&gt;Setup Image Comment" type="3">
      <description>Comment on the Setup Image.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="300A" element="0190" name="&gt;Fixation Device Sequence" type="3">
      <description>Introduces sequence of Fixation Devices used in Patient Setup. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="0192" name="&gt;&gt;Fixation Device Type" type="1C">
      <description>Type of Fixation Device used during in Patient Setup. Required if Fixation Device Sequence (300A,0190) is sent.
Defined Terms:
BITEBLOCK
HEADFRAME
MASK
MOLD
CAST
HEADREST
BREAST_BOARD
BODY_FRAME
VACUUM_MOLD
WHOLE_BODY_POD
RECTAL_BALLOON</description>
    </entry>
    <entry group="300A" element="0194" name="&gt;&gt;Fixation Device Label" type="2C">
      <description>User-defined label identifier for Fixation Device. Required if Fixation Device Sequence (300A,0190) is sent.</description>
    </entry>
    <entry group="300A" element="0196" name="&gt;&gt;Fixation Device Description" type="3">
      <description>User-defined description of Fixation Device.</description>
    </entry>
    <entry group="300A" element="0198" name="&gt;&gt;Fixation Device Position" type="3">
      <description>Position/Notch number of Fixation Device.</description>
    </entry>
    <entry group="300A" element="0199" name="&gt;&gt;Fixation Device Pitch Angle" type="3">
      <description>The Fixation Device Pitch Angle, i.e. orientation of PITCHED FIXATION DEVICE coordinate system with respect to IEC PATIENT SUPPORT coordinate system (degrees). Pitching is the rotation around IEC PATIENT SUPPORT X-axis.</description>
    </entry>
    <entry group="300A" element="019A" name="&gt;&gt;Fixation Device Roll Angle" type="3">
      <description>The Fixation Device Roll Angle, i.e. orientation of ROLLED FIXATION DEVICE coordinate system with respect to IEC PITCHED FIXATION DEVICE coordinate system (degrees). Rolling is the rotation around IEC PATIENT SUPPORT Y-axis.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An identifier for the accessory intended to be read by a device such as a bar-code reader.</description>
    </entry>
    <entry group="300A" element="01A0" name="&gt;Shielding Device Sequence" type="3">
      <description>Introduces sequence of Shielding Devices used in Patient Setup. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="01A2" name="&gt;&gt;Shielding Device Type" type="1C">
      <description>Type of Shielding Device used in Patient Setup. Required if Shielding Device Sequence (300A,01A0) is sent.
Defined Terms:
GUM
EYE
GONAD</description>
    </entry>
    <entry group="300A" element="01A4" name="&gt;&gt;Shielding Device Label" type="2C">
      <description>User-defined label for Shielding Device. Required if Shielding Device Sequence (300A,01A0) is sent.</description>
    </entry>
    <entry group="300A" element="01A6" name="&gt;&gt;Shielding Device Description" type="3">
      <description>User-defined description of Shielding Device.</description>
    </entry>
    <entry group="300A" element="01A8" name="&gt;&gt;Shielding Device Position" type="3">
      <description>Position/Notch number of Shielding Device.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An identifier for the accessory intended to be read by a device such as a bar-code reader.</description>
    </entry>
    <entry group="300A" element="01B0" name="&gt;Setup Technique" type="3">
      <description>Setup Technique used in Patient Setup.
Defined Terms:
ISOCENTRIC
FIXED_SSD
TBI
BREAST_BRIDGE
SKIN_APPOSITION</description>
    </entry>
    <entry group="300A" element="01B2" name="&gt;Setup Technique Description" type="3">
      <description>User-defined description of Setup Technique.</description>
    </entry>
    <entry group="300A" element="01B4" name="&gt;Setup Device Sequence" type="3">
      <description>Introduces sequence of devices used for patient alignment in Patient Setup. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="01B6" name="&gt;&gt;Setup Device Type" type="1C">
      <description>Type of Setup Device used for Patient alignment. Required if Setup Device Sequence (300A,01B4) is sent.
Defined Terms:
LASER_POINTER
DISTANCE_METER
TABLE_HEIGHT
MECHANICAL_PTR
ARC</description>
    </entry>
    <entry group="300A" element="01B8" name="&gt;&gt;Setup Device Label" type="2C">
      <description>User-defined label for Setup Device used for patient alignment. Required if Setup Device Sequence (300A,01B4) is sent.</description>
    </entry>
    <entry group="300A" element="01BA" name="&gt;&gt;Setup Device Description" type="3">
      <description>User-defined description for Setup Device used for patient alignment.</description>
    </entry>
    <entry group="300A" element="01BC" name="&gt;&gt;Setup Device Parameter" type="2C">
      <description>Setup Parameter for Setup Device in appropriate IEC 61217 coordinate system.
Units shall be mm for distances and degrees for angles. Required if Setup Device Sequence (300A,011B4) is sent.</description>
    </entry>
    <entry group="300A" element="01D0" name="&gt;&gt;Setup Reference Description" type="3">
      <description>User-defined description of Setup Reference used for patient alignment.</description>
    </entry>
    <entry group="300A" element="01D2" name="&gt;Table Top Vertical Setup Displacement" type="3">
      <description>Vertical Displacement in IEC TABLE TOP coordinate system (in mm) relative to initial Setup Position, i.e. vertical offset between patient positioning performed using setup and treatment position.</description>
    </entry>
    <entry group="300A" element="01D4" name="&gt;Table Top Longitudinal Setup Displacement" type="3">
      <description>Longitudinal Displacement in IEC TABLE TOP coordinate system (in mm) relative to initial Setup Position, i.e. longitudinal offset between patient positioning performed using setup and treatment position.</description>
    </entry>
    <entry group="300A" element="01D6" name="&gt;Table Top Lateral Setup Displacement" type="3">
      <description>Lateral Displacement in IEC TABLE TOP coordinate system (in mm) relative to initial Setup Position, i.e. lateral offset between patient positioning performed using setup and treatment position.</description>
    </entry>
    <entry group="300A" element="0410" name="&gt;Motion Synchronization Sequence" type="3">
      <description>Introduces sequence of Motion Synchronization. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="0018" element="9170" name="&gt;&gt;Respiratory Motion Compensation Technique" type="1">
      <description>Technique applied to reduce respiratory motion artifacts.
Defined Terms:
NONE
BREATH_HOLD
REALTIME = image acquisition shorter than respiratory cycle
GATING = Prospective gating
TRACKING = prospective through-plane or in-plane motion tracking
PHASE_ORDERING = prospective phase ordering
PHASE_RESCANNING = prospective techniques, such as real-time averaging, diminishing variance and motion adaptive gating
RETROSPECTIVE = retrospective gating
CORRECTION = retrospective image correction
UNKNOWN = technique not known</description>
    </entry>
    <entry group="0018" element="9171" name="&gt;&gt;Respiratory Signal Source" type="1">
      <description>Signal source from which respiratory motion is derived.
Defined Terms:
NONE
BELT
NASAL_PROBE
CO2_SENSOR
NAVIGATOR = MR navigator and organ edge detection
MR_PHASE = phase (of center k-space line)
ECG = baseline demodulation of the ECG
SPIROMETER = Signal derived from flow sensor
EXTERNAL_MARKER = Signal determined from external motion surrogate
INTERNAL_MARKER = Signal determined from internal motion surrogate
IMAGE = Signal derived from an image
UNKNOWN = Signal source not known</description>
    </entry>
    <entry group="0018" element="9185" name="&gt;&gt;Respiratory Motion Compensation Technique Description" type="3">
      <description>Description of respiratory motion compensation technique.</description>
    </entry>
    <entry group="0018" element="9186" name="&gt;&gt;Respiratory Signal Source ID" type="3">
      <description>Identifies the device providing the respiratory signal.</description>
    </entry>
  </module>
  <module ref="C.8.8.13" table="C.8-49" name="RT Fraction Scheme Module Attributes">
    <entry group="300A" element="0070" name="Fraction Group Sequence" type="1">
      <description>Introduces sequence of Fraction Groups in current Fraction Scheme. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="0071" name="&gt;Fraction Group Number" type="1">
      <description>Identification number of the Fraction Group. The value of Fraction Group Number (300A,0071) shall be unique within the RT Plan in which it is created.</description>
    </entry>
    <entry group="300A" element="0072" name="&gt;Fraction Group Description" type="3">
      <description>The user defined description for the fraction group.</description>
    </entry>
    <entry group="300C" element="0080" name="&gt;Referenced Dose Sequence" type="3">
      <description>Introduces sequence of related SOP Class/Instance pairs describing related instances of RT Dose (for grids, isodose curves and named/unnamed point doses). One or more items may be included in this sequence. See Note 1.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="300C" element="0050" name="&gt;Referenced Dose Reference Sequence" type="3">
      <description>Introduces sequence of Dose References for the current Fraction Group. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) within Dose Reference Sequence (300A,0010) in RT Prescription Module. Required if Referenced Dose Reference Sequence (300C,0050) is sent.</description>
    </entry>
    <entry group="300A" element="0021" name="&gt;&gt;Constraint Weight" type="3">
      <description>Relative importance of satisfying constraint, where high values represent more important constraints.</description>
    </entry>
    <entry group="300A" element="0022" name="&gt;&gt;Delivery Warning Dose" type="3">
      <description>The dose (in Gy) which when reached or exceeded should cause some action to be taken.</description>
    </entry>
    <entry group="300A" element="0023" name="&gt;&gt;Delivery Maximum Dose" type="3">
      <description>The maximum dose (in Gy) which can be delivered to the dose reference.</description>
    </entry>
    <entry group="300A" element="0025" name="&gt;&gt;Target Minimum Dose" type="3">
      <description>Minimum permitted dose (in Gy) to Dose Reference if Dose Reference Type (300A,0020) of referenced Dose Reference is TARGET.</description>
    </entry>
    <entry group="300A" element="0026" name="&gt;&gt;Target Prescription Dose" type="3">
      <description>Prescribed dose (in Gy) to Dose Reference if Dose Reference Type (300A,0020) of referenced Dose Reference is TARGET.</description>
    </entry>
    <entry group="300A" element="0027" name="&gt;&gt;Target Maximum Dose" type="3">
      <description>Maximum permitted dose (in Gy) to Dose Reference if Dose Reference Type (300A,0020) of referenced Dose Reference is TARGET.</description>
    </entry>
    <entry group="300A" element="0028" name="&gt;&gt;Target Underdose Volume Fraction" type="3">
      <description>Maximum permitted fraction (in percent) of Target to receive less than the Target Prescription Dose (300A,0027) if Dose Reference Type (300A,0020) of referenced Dose Reference is TARGET and Dose Reference Structure Type (300A,0014) of referenced Dose Reference is VOLUME.</description>
    </entry>
    <entry group="300A" element="002A" name="&gt;&gt;Organ at Risk Full-volume Dose" type="3">
      <description>Maximum dose (in Gy) to entire Dose Reference if Dose Reference Type (300A,0020) of referenced Dose Reference is ORGAN_AT_RISK and Dose Reference Structure Type (300A,0014) of referenced Dose Reference is VOLUME.</description>
    </entry>
    <entry group="300A" element="002B" name="&gt;&gt;Organ at Risk Limit Dose" type="3">
      <description>Maximum permitted dose (in Gy) to any part of Dose Reference if Dose Reference Type (300A,0020) of referenced Dose Reference is ORGAN_AT_RISK and Dose Reference Structure Type (300A,0014) of referenced Dose Reference is VOLUME.</description>
    </entry>
    <entry group="300A" element="002C" name="&gt;&gt;Organ at Risk Maximum Dose" type="3">
      <description>Maximum dose (in Gy) to non-overdosed part of Dose Reference if Dose Reference Type (300A,0020) of referenced Dose Reference is ORGAN_AT_RISK and Dose Reference Structure Type (300A,0014) of referenced Dose Reference is VOLUME.</description>
    </entry>
    <entry group="300A" element="002D" name="&gt;&gt;Organ at Risk Overdose Volume Fraction" type="3">
      <description>Maximum permitted fraction (in percent) of Organ at Risk to receive more than the Organ at Risk Maximum Dose if Dose Reference Type (300A,0020) of referenced Dose Reference is ORGAN_AT_RISK and Dose Reference Structure Type (300A,0014) of referenced Dose Reference is VOLUME.</description>
    </entry>
    <entry group="300A" element="0078" name="&gt;Number of Fractions Planned" type="2">
      <description>Total number of treatments (Fractions) prescribed for current Fraction Group.</description>
    </entry>
    <entry group="300A" element="0079" name="&gt;Number of Fraction Pattern Digits Per Day" type="3">
      <description>Number of digits in Fraction Pattern (300A,007B) used to represent one day. See Note 2.</description>
    </entry>
    <entry group="300A" element="007A" name="&gt;Repeat Fraction Cycle Length" type="3">
      <description>Number of weeks needed to describe treatment pattern. See Note 2.</description>
    </entry>
    <entry group="300A" element="007B" name="&gt;Fraction Pattern" type="3">
      <description>String of 0's (no treatment) and 1's (treatment) describing treatment pattern. Length of string is 7 x Number of Fraction Pattern Digits Per Day x Repeat Fraction Cycle Length. Pattern shall start on a Monday. See Note 2.</description>
    </entry>
    <entry group="300A" element="0080" name="&gt;Number of Beams" type="1">
      <description>Number of Beams in current Fraction Group. If Number of Beams is greater then zero, Number of Brachy Application Setups (300A,00A0) shall equal zero.</description>
    </entry>
    <entry group="300C" element="0004" name="&gt;Referenced Beam Sequence" type="1C">
      <description>Introduces sequence of treatment beams in current Fraction Group. Required if Number of Beams (300A,0080) is greater than zero. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300C" element="0006" name="&gt;&gt;Referenced Beam Number" type="1C">
      <description>Uniquely identifies Beam specified by Beam Number (300A,00C0) within Beam Sequence (300A,00B0) in RT Beams Module. Required if Referenced Beam Sequence (300C,0004) is sent.</description>
    </entry>
    <entry group="300A" element="0082" name="&gt;&gt;Beam Dose Specification Point" type="3">
      <description>Coordinates (x,y,z) of point at which Beam Dose is specified in the patient based coordinate system described in C.7.6.2.1.1 (mm). See Note 3.</description>
    </entry>
    <entry group="300A" element="0084" name="&gt;&gt;Beam Dose" type="3">
      <description>Dose (in Gy) at Beam Dose Specification Point (300A,0082) due to current Beam.</description>
    </entry>
    <entry group="300A" element="0088" name="&gt;&gt;Beam Dose Point Depth" type="3">
      <description>The depth (in mm) in the patient along a ray from the source to the dose point specified by the Beam Dose Specification Point (300A,0082).</description>
    </entry>
    <entry group="300A" element="0089" name="&gt;&gt;Beam Dose Point Equivalent Depth" type="3">
      <description>The radiological depth in mm (water-equivalent depth, taking tissue heterogeneity into account) in the patient along a ray from the source to the dose point specified by the Beam Dose Specification Point (300A,0082).</description>
    </entry>
    <entry group="300A" element="008A" name="&gt;&gt;Beam Dose Point SSD" type="3">
      <description>Source to patient surface distance along a ray from the source to the dose point specified by the Beam Dose Specification Point (300A,0082).</description>
    </entry>
    <entry group="300A" element="0086" name="&gt;&gt;Beam Meterset" type="3">
      <description>Machine setting to be delivered for current Beam, specified in Monitor Units (MU) or minutes as defined by Primary Dosimeter Unit (300A,00B3) (in RT Beams Module) for referenced Beam. See Note 4.</description>
    </entry>
    <entry group="300A" element="00A0" name="&gt;Number of Brachy Application Setups" type="1">
      <description>Number of Brachy Application Setups in current Fraction Group. If Number of Brachy Application Setups is greater then zero, Number of Beams (300A,0080) shall equal zero.</description>
    </entry>
    <entry group="300C" element="000A" name="&gt;Referenced Brachy Application Setup Sequence" type="1C">
      <description>Introduces sequence of treatment Brachy Application Setups in current Fraction Group. Required if Number of Brachy Application Setups (300A,00A0) is greater than zero. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300C" element="000C" name="&gt;&gt;Referenced Brachy Application Setup Number" type="1C">
      <description>Uniquely identifies Brachy Application Setup specified by Brachy Application Setup Number (300A,0234) within Brachy Application Setup Sequence (300A,0230) in RT Brachy Application Setups Module. Required if Referenced Brachy Application Setup Sequence (300C,000A) is sent.</description>
    </entry>
    <entry group="300A" element="00A2" name="&gt;&gt;Brachy Application Setup Dose Specification Point" type="3">
      <description>Coordinates (x,y,z) of point in the patient based coordinate system described in C.7.6.2.1.1 at which Brachy Application Setup Dose (300A,00A4) is specified (mm).</description>
    </entry>
    <entry group="300A" element="00A4" name="&gt;&gt;Brachy Application Setup Dose" type="3">
      <description>Dose (in Gy) at Brachy Application Setup Dose Specification Point (300A,00A2) due to current Brachy Application Setup.</description>
    </entry>
  </module>
  <module ref="C.8.8.14" table="C.8-50" name="RT Beams Module Attributes">
    <entry group="300A" element="00B0" name="Beam Sequence" type="1">
      <description>Introduces sequence of treatment beams for current RT Plan. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00C0" name="&gt;Beam Number" type="1">
      <description>Identification number of the Beam. The value of Beam Number (300A,00C0) shall be unique within the RT Plan in which it is created. See Note 1.</description>
    </entry>
    <entry group="300A" element="00C2" name="&gt;Beam Name" type="3">
      <description>User-defined name for Beam. See Note 1.</description>
    </entry>
    <entry group="300A" element="00C3" name="&gt;Beam Description" type="3">
      <description>User-defined description for Beam. See Note 1.</description>
    </entry>
    <entry group="300A" element="00C4" name="&gt;Beam Type" type="1">
      <description>Motion characteristic of Beam. See Note 5.
Enumerated Values:
STATIC = All Control Point Sequence (300A,0111) attributes remain unchanged between consecutive pairs of control points with changing Cumulative Meterset Weight (300A,0134).
DYNAMIC = One or more Control Point Sequence (300A,0111) attributes change between one or more consecutive pairs of control points with changing Cumulative Meterset Weight (300A,0134).</description>
    </entry>
    <entry group="300A" element="00C6" name="&gt;Radiation Type" type="2">
      <description>Particle type of Beam.
Defined Terms:
PHOTON
ELECTRON
NEUTRON
PROTON</description>
    </entry>
    <entry group="300A" element="00C7" name="&gt;High-Dose Technique Type" type="1C">
      <description>Type of high-dose treatment technique.
Defined Terms:
NORMAL = Standard treatment
TBI = Total Body Irradiation
HDR = High Dose Rate
Required if treatment technique requires a dose that would normally require overriding of treatment machine safety controls.</description>
    </entry>
    <entry group="300A" element="00B2" name="&gt;Treatment Machine Name" type="2">
      <description>User-defined name identifying treatment machine to be used for beam delivery. See Note 2.</description>
    </entry>
    <entry group="0008" element="0070" name="&gt;Manufacturer" type="3">
      <description>Manufacturer of the equipment to be used for beam delivery.</description>
    </entry>
    <entry group="0008" element="0080" name="&gt;Institution Name" type="3">
      <description>Institution where the equipment is located that is to be used for beam delivery.</description>
    </entry>
    <entry group="0008" element="0081" name="&gt;Institution Address" type="3">
      <description>Mailing address of the institution where the equipment is located that is to be used for beam delivery.</description>
    </entry>
    <entry group="0008" element="1040" name="&gt;Institutional Department Name" type="3">
      <description>Department in the institution where the equipment is located that is to be used for beam delivery.</description>
    </entry>
    <entry group="0008" element="1090" name="&gt;Manufacturer's Model Name" type="3">
      <description>Manufacturer's model name of the equipment that is to be used for beam delivery.</description>
    </entry>
    <entry group="0018" element="1000" name="&gt;Device Serial Number" type="3">
      <description>Manufacturer's serial number of the equipment that is to be used for beam delivery.</description>
    </entry>
    <entry group="300A" element="00B3" name="&gt;Primary Dosimeter Unit" type="3">
      <description>Measurement unit of machine dosimeter.
See C.8.8.14.1.
Enumerated Values:
MU = Monitor Unit
MINUTE = minute</description>
      <section ref="C.8.8.14.1" name="">The Meterset at a given Control Point is equal to the Beam Meterset (300A,0086) specified in the Referenced Beam Sequence (300C,0004) of the RT Fraction Scheme Module, multiplied by the Cumulative Meterset Weight (300A,0134) for the Control Point, divided by the Final Cumulative Meterset Weight (300A,010E). The Meterset is specified in units defined by Primary Dosimeter Unit (300A,00B3). If the calculation for Meterset results in a meterset value which is not an exact multiple of the primary meterset resolution, then the result shall be rounded to the nearest allowed meterset value (i.e. less than a half resolution unit shall be rounded down to the nearest resolution unit, and equal or greater than half a resolution unit shall be rounded up to the nearest resolution unit).
Note also that if Final Cumulative Meterset Weight (300A,010E) is equal to 100, then Cumulative Meterset Weight (300A,0134) becomes equivalent to the percentage of Beam Meterset (300A,0086) delivered at each control point. If Final Cumulative Meterset Weight (300A,010E) is equal to Beam Meterset (300A,0086), then the Cumulative Meterset Weight (300A,0134) at each control point becomes equal to the cumulative Meterset delivered at that control point.
</section>
    </entry>
    <entry group="300C" element="00A0" name="&gt;Referenced Tolerance Table Number" type="3">
      <description>Uniquely identifies Tolerance Table specified by Tolerance Table Number (300A,0042) within Tolerance Table Sequence in RT Tolerance Tables Module. These tolerances are to be used for verification of treatment machine settings.</description>
    </entry>
    <entry group="300A" element="00B4" name="&gt;Source-Axis Distance" type="3">
      <description>Radiation source to Gantry rotation axis distance of the equipment that is to be used for beam delivery (mm).</description>
    </entry>
    <entry group="300A" element="00B6" name="&gt;Beam Limiting Device Sequence" type="1">
      <description>Introduces sequence of beam limiting device (collimator) jaw or leaf (element) sets. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00B8" name="&gt;&gt;RT Beam Limiting Device Type" type="1">
      <description>Type of beam limiting device (collimator).
Enumerated Values:
X = symmetric jaw pair in IEC X direction
Y = symmetric jaw pair in IEC Y direction
ASYMX = asymmetric jaw pair in IEC X direction
ASYMY = asymmetric pair in IEC Y direction
MLCX = multileaf (multi-element) jaw pair in IEC X direction
MLCY = multileaf (multi-element) jaw pair in IEC Y direction</description>
    </entry>
    <entry group="300A" element="00BA" name="&gt;&gt;Source to Beam Limiting Device Distance" type="3">
      <description>Radiation source to beam limiting device (collimator) distance of the equipment that is to be used for beam delivery (mm).</description>
    </entry>
    <entry group="300A" element="00BC" name="&gt;&gt;Number of Leaf/Jaw Pairs" type="1">
      <description>Number of leaf (element) or jaw pairs (equal to 1 for standard beam limiting device jaws).</description>
    </entry>
    <entry group="300A" element="00BE" name="&gt;&gt;Leaf Position Boundaries" type="2C">
      <description>Boundaries of beam limiting device (collimator) leaves (in mm) in IEC BEAM LIMITING DEVICE coordinate axis appropriate to RT Beam Limiting Device Type (300A,00B8), i.e. X-axis for MLCY, Y-axis for MLCX. Contains N+1 values, where N is the Number of Leaf/Jaw Pairs (300A,00BC), starting from Leaf (Element) Pair 1. Required if Beam Limiting Device Sequence (300A,00B6) is sent and RT Beam Limiting Device Type (300A,00B8) is MLCX or MLCY. See Note 3.</description>
    </entry>
    <entry group="300C" element="006A" name="&gt;Referenced Patient Setup Number" type="3">
      <description>Uniquely identifies Patient Setup to be used for current beam, specified by Patient Setup Number (300A,0182) within Patient Setup Sequence of RT Patient Setup Module.</description>
    </entry>
    <entry group="300C" element="0042" name="&gt;Referenced Reference Image Sequence" type="3">
      <description>Introduces sequence of reference images used for validation of current beam. One or more items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="300A" element="00C8" name="&gt;&gt;Reference Image Number" type="1C">
      <description>Uniquely identifies Reference Image within Referenced Reference Image Sequence (300A,0042). Required if Referenced Reference Image Sequence (300A,0042) is sent.</description>
    </entry>
    <entry group="300C" element="0008" name="&gt;&gt;Start Cumulative Meterset Weight" type="3">
      <description>Cumulative Meterset Weight within current Beam at which image acquisition starts.</description>
    </entry>
    <entry group="300C" element="0009" name="&gt;&gt;End Cumulative Meterset Weight" type="3">
      <description>Cumulative Meterset Weight within current Beam at which image acquisition ends.</description>
    </entry>
    <entry group="300A" element="00CA" name="&gt;Planned Verification Image Sequence" type="3">
      <description>Introduces sequence of planned verification images to be acquired during current beam. One or more items may be included in this sequence. See C.8.8.14.2.</description>
      <section ref="C.8.8.14.2" name="">The Planned Verification Image Sequence (300A,00CA) contains attributes which describe the planned verification images to be acquired during current beam. The Start Cumulative Meterset Weight (300C,0008) specifies the Cumulative Meterset Weight at which image acquisition is to begin. If Meterset Exposure (3002,0032) is present in a sequence item and End Cumulative Meterset Weight (300C,0009) is not present then a single image shall be acquired using the meterset duration specified in Meterset Exposure (3002,0032). If End Cumulative Meterset Weight (300C,0009) is present in a sequence item and Meterset Exposure (3002,0032) is not present then a single image shall be acquired over the beam delivery from Start Cumulative Meterset Weight (300C,0008) to End Cumulative Meterset Weight (300C,0009). If both Meterset Exposure (3002,0032) and End Cumulative Meterset Weight (300C,0009) are present in a sequence item then images shall be acquired every Meterset Exposure (3002,0032) from Start Cumulative Meterset Weight (300C,0008) to End Cumulative Meterset Weight (300C,0009). No images shall extend past End Cumulative Meterset Weight (300C,0009).
</section>
    </entry>
    <entry group="300C" element="0008" name="&gt;&gt;Start Cumulative Meterset Weight" type="3">
      <description>Cumulative Meterset Weight within current Beam at which image acquisition will start.</description>
    </entry>
    <entry group="3002" element="0032" name="&gt;&gt;Meterset Exposure" type="3">
      <description>Meterset duration over which image is to be acquired, specified in Monitor units (MU) or minutes as defined by Primary Dosimeter Unit (300A,00B3).</description>
    </entry>
    <entry group="300C" element="0009" name="&gt;&gt;End Cumulative Meterset Weight" type="3">
      <description>Cumulative Meterset Weight within current Beam at which image acquisition will end.</description>
    </entry>
    <entry group="3002" element="000C" name="&gt;&gt;RT Image Plane" type="3">
      <description>Describes whether or not image plane is normal to beam axis.
Enumerated Values:
NORMAL = image plane normal to beam axis
NON_NORMAL = image plane non-normal to beam axis</description>
    </entry>
    <entry group="3002" element="000E" name="&gt;&gt;X-Ray Image Receptor Angle" type="3">
      <description>X-Ray Image Receptor Angle i.e. orientation of IEC X-RAY IMAGE RECEPTOR coordinate system with respect to IEC GANTRY coordinate system (degrees). See C.8.8.14.3.</description>
      <section ref="C.8.8.14.3" name="">The X-Ray Image Receptor Angle (3002,000E) specifies the rotation of the image receptor device in the IEC X-RAY IMAGE RECEPTOR PLANE. A positive angle corresponds to a counter-clockwise rotation of the X-Ray Image Receptor as viewed from the radiation source in the IEC GANTRY coordinate system. The normal (non-rotated) value for this parameter is zero degrees.
</section>
    </entry>
    <entry group="3002" element="0010" name="&gt;&gt;RT Image Orientation" type="3">
      <description>The direction cosines of the first row and the first column with respect to the IEC X-RAY IMAGE RECEPTOR coordinate system.</description>
    </entry>
    <entry group="3002" element="0012" name="&gt;&gt;RT Image Position" type="3">
      <description>The x and y coordinates (in mm) of the upper left hand corner of the image, in the IEC X-RAY IMAGE RECEPTOR coordinate system. This is the center of the first pixel transmitted.</description>
    </entry>
    <entry group="3002" element="0026" name="&gt;&gt;RT Image SID" type="3">
      <description>Radiation machine source to image plane distance (mm).</description>
    </entry>
    <entry group="300A" element="00CC" name="&gt;&gt;Imaging Device-Specific Acquisition Parameters" type="3">
      <description>User-specified device-specific parameters that describe how the imager will acquire the image.</description>
    </entry>
    <entry group="300C" element="0007" name="&gt;&gt;Referenced Reference Image Number" type="3">
      <description>Uniquely identifies Reference Image to which planned verification image is related, specified by Reference Image Number (300A,00C8) within Referenced Reference Image Sequence (300A,0042).</description>
    </entry>
    <entry group="300A" element="00CE" name="&gt;Treatment Delivery Type" type="3">
      <description>Delivery Type of treatment.
Defined Terms:
TREATMENT = normal patient treatment
OPEN_PORTFILM = portal image acquisition with open field
TRMT_PORTFILM = portal image acquisition with treatment port
CONTINUATION = continuation of interrupted treatment
SETUP = no treatment beam is applied for this RT Beam. To be used for specifying the gantry, couch, and other machine positions where X-Ray set-up images or measurements are to be taken</description>
    </entry>
    <entry group="300C" element="0080" name="&gt;Referenced Dose Sequence" type="3">
      <description>Introduces sequence of related SOP Class/Instance pairs describing related instances of RT Dose (for grids, isodose curves, and named/unnamed point doses). One or more items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="300A" element="00D0" name="&gt;Number of Wedges" type="1">
      <description>Number of wedges associated with current Beam.</description>
    </entry>
    <entry group="300A" element="00D1" name="&gt;Wedge Sequence" type="1C">
      <description>Introduces sequence of treatment wedges. Required if Number of Wedges (300A,00D0) is non-zero. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00D2" name="&gt;&gt;Wedge Number" type="1C">
      <description>Identification number of the Wedge. The value of Wedge Number (300A,00D2) shall be unique within the Beam in which it is created. Required if Wedge Sequence (300A,00D1) is sent.</description>
    </entry>
    <entry group="300A" element="00D3" name="&gt;&gt;Wedge Type" type="2C">
      <description>Type of wedge (if any) defined for Beam. Required if Wedge Sequence (300A,00D1) is sent.
Defined Terms:
STANDARD = standard (static) wedge
DYNAMIC = moving beam limiting device (collimator) jaw simulating wedge
MOTORIZED = single wedge which can be removed from beam remotely</description>
    </entry>
    <entry group="300A" element="00D4" name="&gt;&gt;Wedge ID" type="3">
      <description>User-supplied identifier for Wedge.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An identifier for the accessory intended to be read by a device such as a bar-code reader.</description>
    </entry>
    <entry group="300A" element="00D5" name="&gt;&gt;Wedge Angle" type="2C">
      <description>Nominal wedge angle (degrees). Required if Wedge Sequence (300A,00D1) is sent.</description>
    </entry>
    <entry group="300A" element="00D6" name="&gt;&gt;Wedge Factor" type="2C">
      <description>Nominal wedge factor under machine calibration conditions at the beam energy specified by the Nominal Beam Energy (300A,0114) of the first Control Point of the Control Point Sequence (300A,0111). Required if Wedge Sequence (300A,00D1) is sent.</description>
    </entry>
    <entry group="300A" element="00D8" name="&gt;&gt;Wedge Orientation" type="2C">
      <description>Orientation of wedge, i.e. orientation of IEC WEDGE FILTER coordinate system with respect to IEC BEAM LIMITING DEVICE coordinate system (degrees). Required if Wedge Sequence (300A,00D1) is sent.</description>
    </entry>
    <entry group="300A" element="00DA" name="&gt;&gt;Source to Wedge Tray Distance" type="3">
      <description>Radiation source to wedge tray attachment edge distance (in mm) for current wedge.</description>
    </entry>
    <entry group="300A" element="00E0" name="&gt;Number of Compensators" type="1">
      <description>Number of compensators associated with current Beam.</description>
    </entry>
    <entry group="300A" element="00E2" name="&gt;Total Compensator Tray Factor" type="3">
      <description>Compensator Tray transmission factor (between 0 and 1), at the beam energy specified by the Nominal Beam Energy (300A,0114) of the first Control Point of the Control Point Sequence (300A,0111).</description>
    </entry>
    <entry group="300A" element="00E3" name="&gt;Compensator Sequence" type="1C">
      <description>Introduces sequence of treatment compensators. Required if Number of Compensators (300A,00E0) is non-zero. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="02EB" name="&gt;&gt;Compensator Description" type="3">
      <description>User defined description for the compensator.</description>
    </entry>
    <entry group="300A" element="00E4" name="&gt;&gt;Compensator Number" type="1C">
      <description>Identification number of the Compensator. The value of Compensator Number (300A,00E4) shall be unique within the Beam in which it is created. Required if Number of Compensators (300A,00E0) is non-zero.</description>
    </entry>
    <entry group="300A" element="00EE" name="&gt;&gt;Compensator Type" type="3">
      <description>Type of compensator (if any). Defined Terms:
STANDARD = physical (static) compensator
DYNAMIC = moving Beam Limiting Device (collimator) simulating physical compensator</description>
    </entry>
    <entry group="300A" element="00E1" name="&gt;&gt;Material ID" type="2C">
      <description>User-supplied identifier for material used to manufacture Compensator. Required if Number of Compensators (300A,00E0) is non-zero.</description>
    </entry>
    <entry group="300A" element="00E5" name="&gt;&gt;Compensator ID" type="3">
      <description>User-supplied identifier for compensator.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An identifier for the accessory intended to be read by a device such as a bar-code reader.</description>
    </entry>
    <entry group="300A" element="00E6" name="&gt;&gt;Source to Compensator Tray Distance" type="2C">
      <description>Radiation source to compensator tray attachment edge distance (in mm) for current compensator. Required if Compensator Sequence (300A,00E3) is sent.</description>
    </entry>
    <entry group="300A" element="02E0" name="&gt;&gt;Compensator Divergence" type="3">
      <description>Indicates presence or absence of geometrical divergence of the compensator.
Enumerated Values:
PRESENT = the compensator is shaped according to the beam geometrical divergence.
ABSENT = the compensator is not shaped according to the beam geometrical divergence.</description>
    </entry>
    <entry group="300A" element="02E1" name="&gt;&gt;Compensator Mounting Position" type="3">
      <description>Indicates on which side of the Compensator Tray the compensator is mounted.
Enumerated Values:
PATIENT_SIDE = the compensator is mounted on the side of the Compensator Tray which is towards the patient.
SOURCE_SIDE = the compensator is mounted on the side of the Compensator Tray which is towards the radiation source.
DOUBLE_SIDED = the compensator has a shaped (i.e. non-flat) surface on both sides of the Compensator Tray.</description>
    </entry>
    <entry group="300A" element="00E7" name="&gt;&gt;Compensator Rows" type="1">
      <description>Number of rows in the compensator. A row is defined to be in the X direction of the IEC Beam Limiting Device Coordinate system.</description>
    </entry>
    <entry group="300A" element="00E8" name="&gt;&gt;Compensator Columns" type="1">
      <description>Number of columns in the compensator. A column is defined to be in the Y direction of the IEC Beam Limiting Device Coordinate system.</description>
    </entry>
    <entry group="300A" element="00E9" name="&gt;&gt;Compensator Pixel Spacing" type="1C">
      <description>Physical distance (in mm) between the center of each pixel projected onto machine isocentric plane. Specified by a numeric pair - adjacent row spacing (delimiter) adjacent column spacing. See 10.7.1.3 for further explanation of the value order. Required if Compensator Sequence (300A,00E3) is sent.</description>
    </entry>
    <entry group="300A" element="00EA" name="&gt;&gt;Compensator Position" type="1C">
      <description>The x and y coordinates of the upper left hand corner (first pixel transmitted) of the compensator, projected onto the machine isocentric plane in the IEC BEAM LIMITING DEVICE coordinate system (mm). Required if Compensator Sequence (300A,00E3) is sent.</description>
    </entry>
    <entry group="300A" element="00EB" name="&gt;&gt;Compensator Transmission Data" type="1C">
      <description>A data stream of the pixel samples which comprise the compensator, expressed as broad-beam transmission values (between 0 and 1) along a ray line passing through the pixel, at the beam energy specified by the Nominal Beam Energy (300A,0114) of the first Control Point of the Control Point Sequence (300A,0111). The order of pixels sent is left to right, top to bottom, i.e., the upper left pixel is sent first followed by the remainder of the first row , followed by the first pixel of the 2nd row, then the remainder of the 2nd row and so on) when viewed from the radiation source. Required if Material ID (300A,00E1) is zero-length. May be present if Material ID (300A,00E1) is non-zero length. See C.8.8.14.10 and C.8.8.14.11.
Note: Compensator Transmission Data may not be properly encoded if Explicit-VR transfer syntax is used and the VL of this attribute exceeds 65534 bytes.</description>
      <section ref="C.8.8.14.10" name="">The direction of the rows and columns in Compensator Transmission Data (300A,00EB) and Compensator Thickness Data (300A,00EC) is defined as follows: The direction of rows goes along the positive Xb direction and the direction of the columns does along the negative Yb direction of the IEC X-BEAM LIMITING DEVICE coordinate system. Other interpretations shall be documented in an implementation's conformance statement.
</section>
    </entry>
    <entry group="300A" element="00EC" name="&gt;&gt;Compensator Thickness Data" type="1C">
      <description>A data stream of the pixel samples which comprise the compensator, expressed as thicknesses (in mm). The order of pixels sent is left to right, top to bottom, i.e., the upper left pixel is sent first followed by the remainder of the first row , followed by the first pixel of the 2nd row, then the remainder of the 2nd row and so on) when viewed from the radiation source. Required if Material ID (300A,00E1) is non-zero length. May be present if Material ID (300A,00E1) is zero length. See C.8.8.14.9 and C.8.8.14.10 and C.8.8.14.11.
Note: Compensator Thickness Data may not be properly encoded if Explicit-VR transfer syntax is used and the VL of this attribute exceeds 65534 bytes.</description>
      <section ref="C.8.8.14.9" name="">The values stored in Compensator Thickness Data (300A,00EC) and Source to Compensator Distance (300A,02E2) shall be parallel to the radiation beam axis if Compensator Divergence (300A,02E0) equals ABSENT, or divergent according to the beam geometrical divergence if Compensator Divergence (300A,02E0) equals PRESENT. If Compensator Divergence (300A,02E0) is not sent, then the parallel or divergent nature of the thicknesses is as if ABSENT was specified for Compensator Divergence (300A,02E0).
</section>
    </entry>
    <entry group="300A" element="02E2" name="&gt;&gt;Source to Compensator Distance" type="1C">
      <description>A data stream of the pixel samples which comprise the distance from the radiation source to the compensator surface closest to the radiation source (in mm). The order of pixels sent is left to right, top to bottom (upper left pixel, followed by the remainder of row 1, followed by the remainder of the columns). Required if Material ID (300A,00E1) is non-zero length, and Compensator Mounting Position (300A,02E1) is DOUBLE_SIDED. May be present if Material ID (300A,00E1) is zero length and Compensator Mounting Position (300A,02E1) is DOUBLE_SIDED. See C.8.8.14.9 and C.8.8.14.11.</description>
      <section ref="C.8.8.14.9" name="">The values stored in Compensator Thickness Data (300A,00EC) and Source to Compensator Distance (300A,02E2) shall be parallel to the radiation beam axis if Compensator Divergence (300A,02E0) equals ABSENT, or divergent according to the beam geometrical divergence if Compensator Divergence (300A,02E0) equals PRESENT. If Compensator Divergence (300A,02E0) is not sent, then the parallel or divergent nature of the thicknesses is as if ABSENT was specified for Compensator Divergence (300A,02E0).
</section>
    </entry>
    <entry group="300A" element="00ED" name="&gt;Number of Boli" type="1">
      <description>Number of boli associated with current Beam.</description>
    </entry>
    <entry group="300C" element="00B0" name="&gt;Referenced Bolus Sequence" type="1C">
      <description>Introduces sequence of boli associated with Beam. Required if Number of Boli (300A,00ED) is non-zero. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="3006" element="0084" name="&gt;&gt;Referenced ROI Number" type="1C">
      <description>Uniquely identifies ROI representing the Bolus specified by ROI Number (3006,0022) in Structure Set ROI Sequence (3006,0020) in Structure Set Module within RT Structure Set in Referenced Structure Set Sequence (300C,0060) in RT General Plan Module. Required if Referenced Bolus Sequence (300C,00B0) is sent.</description>
    </entry>
    <entry group="300A" element="00DC" name="&gt;&gt;Bolus ID" type="3">
      <description>User-supplied identifier for the Bolus.</description>
    </entry>
    <entry group="300A" element="00DD" name="&gt;&gt;Bolus Description" type="3">
      <description>User-defined description for the Bolus.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An identifier for the accessory intended to be read by a device such as a bar-code reader.</description>
    </entry>
    <entry group="300A" element="00F0" name="&gt;Number of Blocks" type="1">
      <description>Number of shielding blocks associated with Beam.</description>
    </entry>
    <entry group="300A" element="00F2" name="&gt;Total Block Tray Factor" type="3">
      <description>Total block tray transmission for all block trays (between 0 and 1) at the beam energy specified by the Nominal Beam Energy (300A,0114) of the first Control Point of the Control Point Sequence (300A,0111).</description>
    </entry>
    <entry group="300A" element="00F4" name="&gt;Block Sequence" type="1C">
      <description>Introduces sequence of blocks associated with Beam. Required if Number of Blocks (300A,00F0) is non-zero. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00F5" name="&gt;&gt;Block Tray ID" type="3">
      <description>User-supplied identifier for block tray.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An identifier for the accessory intended to be read by a device such as a bar-code reader.</description>
    </entry>
    <entry group="300A" element="00F6" name="&gt;&gt;Source to Block Tray Distance" type="2C">
      <description>Radiation Source to attachment edge of block tray assembly (mm). Required if Block Sequence (300A,00F4) is sent.</description>
    </entry>
    <entry group="300A" element="00F8" name="&gt;&gt;Block Type" type="1C">
      <description>Type of block. Required if Block Sequence (300A,00F4) is sent. See C.8.8.14.4.
Enumerated Values:
SHIELDING = blocking material is inside contour
APERTURE = blocking material is outside contour</description>
      <section ref="C.8.8.14.4" name="">All blocks with Block Type (300A,00F8) of APERTURE for a given beam shall have equal values of Block Transmission (300A,0102) and/or Block Thickness (300A,0100) if they are specified. The composite aperture shall be evaluated as the union of the individual apertures within a single Block. Shielding block transmission(s) shall be applied multiplicatively after the (composite) aperture has been evaluated.
</section>
    </entry>
    <entry group="300A" element="00FA" name="&gt;&gt;Block Divergence" type="2C">
      <description>Indicates presence or otherwise of geometrical divergence. Required if Block Sequence (300A,00F4) is sent.
Enumerated Values:
PRESENT = block edges are shaped for beam divergence
ABSENT = block edges are not shaped for beam divergence</description>
    </entry>
    <entry group="300A" element="00FB" name="&gt;&gt;Block Mounting Position" type="3">
      <description>Indicates on which side of the Block Tray the block is mounted.
Enumerated Values:
PATIENT_SIDE = the block is mounted on the side of the Block Tray which is towards the patient.
SOURCE_SIDE = the block is mounted on the side of the Block Tray which is towards the radiation source.</description>
    </entry>
    <entry group="300A" element="00FC" name="&gt;&gt;Block Number" type="1C">
      <description>Identification number of the Block. The value of Block Number (300A,00FC) shall be unique within the Beam in which it is created. Required if Block Sequence (300A,00F4) is sent.</description>
    </entry>
    <entry group="300A" element="00FE" name="&gt;&gt;Block Name" type="3">
      <description>User-defined name for block.</description>
    </entry>
    <entry group="300A" element="00E1" name="&gt;&gt;Material ID" type="2C">
      <description>User-supplied identifier for material used to manufacture Block. Required if Block Sequence (300A,00F4) is sent.</description>
    </entry>
    <entry group="300A" element="0100" name="&gt;&gt;Block Thickness" type="2C">
      <description>Physical thickness of block (in mm) parallel to radiation beam axis. Required if Material ID (300A,00E1) is non-zero length. May be present if Material ID (300A,00E1) is zero length. See C.8.8.14.4 and C.8.8.14.11.</description>
      <section ref="C.8.8.14.4" name="">All blocks with Block Type (300A,00F8) of APERTURE for a given beam shall have equal values of Block Transmission (300A,0102) and/or Block Thickness (300A,0100) if they are specified. The composite aperture shall be evaluated as the union of the individual apertures within a single Block. Shielding block transmission(s) shall be applied multiplicatively after the (composite) aperture has been evaluated.
</section>
    </entry>
    <entry group="300A" element="0102" name="&gt;&gt;Block Transmission" type="2C">
      <description>Transmission through the block (between 0 and 1) at the beam energy specified by the Nominal Beam Energy (300A,0114) of the first Control Point of the Control Point Sequence (300A,0111). Required if Material ID (300A,00E1) is zero length. May be present if Material ID (300A,00E1) is non-zero length. See C.8.8.14.4 and C.8.8.14.11.</description>
      <section ref="C.8.8.14.4" name="">All blocks with Block Type (300A,00F8) of APERTURE for a given beam shall have equal values of Block Transmission (300A,0102) and/or Block Thickness (300A,0100) if they are specified. The composite aperture shall be evaluated as the union of the individual apertures within a single Block. Shielding block transmission(s) shall be applied multiplicatively after the (composite) aperture has been evaluated.
</section>
    </entry>
    <entry group="300A" element="0104" name="&gt;&gt;Block Number of Points" type="2C">
      <description>Number of (x,y) pairs defining the block edge. Required if Block Sequence (300A,00F4) is sent.</description>
    </entry>
    <entry group="300A" element="0106" name="&gt;&gt;Block Data" type="2C">
      <description>A data stream of (x,y) pairs which comprise the block edge. The number of pairs shall be equal to Block Number of Points (300A,0104), and the vertices shall be interpreted as a closed polygon. Coordinates are projected onto the machine isocentric plane in the IEC BEAM LIMITING DEVICE coordinate system (mm). Required if Block Sequence (300A,00F4) is sent. See Note 4.</description>
    </entry>
    <entry group="300A" element="0107" name="&gt;Applicator Sequence" type="3">
      <description>Introduces sequence of Applicators associated with Beam. Only a single item shall be permitted in this sequence.</description>
    </entry>
    <entry group="300A" element="0108" name="&gt;&gt;Applicator ID" type="1C">
      <description>User or machine supplied identifier for Applicator. Required if Applicator Sequence (300A,0107) is sent.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An identifier for the accessory intended to be read by a device such as a bar-code reader.</description>
    </entry>
    <entry group="300A" element="0109" name="&gt;&gt;Applicator Type" type="1C">
      <description>Type of Applicator. Required if Applicator Sequence (300A,0107) is sent.
Defined Terms:
ELECTRON_SQUARE = square electron applicator
ELECTRON_RECT = rectangular electron applicator
ELECTRON_CIRC = circular electron applicator
ELECTRON_SHORT = short electron applicator
ELECTRON_OPEN = open (dummy) electron applicator
INTRAOPERATIVE = intraoperative (custom) applicator
STEREOTACTIC = stereotactic applicator</description>
    </entry>
    <entry group="300A" element="010A" name="&gt;&gt;Applicator Description" type="3">
      <description>User-defined description for Applicator.</description>
    </entry>
    <entry group="300A" element="0420" name="&gt;General Accessory Sequence" type="3">
      <description>Introduces a Sequence of General Accessories associated with this Beam. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="0424" name="&gt;&gt;General Accessory Number" type="1">
      <description>Identification Number of the General Accessory. The value shall be unique within the sequence.</description>
    </entry>
    <entry group="300A" element="0421" name="&gt;&gt;General Accessory ID" type="1">
      <description>User or machine supplied identifier for General Accessory.</description>
    </entry>
    <entry group="300A" element="0422" name="&gt;&gt;General Accessory Description" type="3">
      <description>User supplied description of General Accessory.</description>
    </entry>
    <entry group="300A" element="0423" name="&gt;&gt;General Accessory Type" type="3">
      <description>Specifies the type of accessory.
Defined Terms:
GRATICULE = Accessory tray with a radio-opaque grid
IMAGE_DETECTOR = Image acquisition device positioned in the beam line
RETICLE = Accessory tray with radio-transparent markers or grid</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>Machine-readable identifier for this accessory</description>
    </entry>
    <entry group="300A" element="010E" name="&gt;Final Cumulative Meterset Weight" type="1C">
      <description>Value of Cumulative Meterset Weight (300A,0134) for final Control Point in Control Point Sequence (300A,0111). Required if Cumulative Meterset Weight is non-null in Control Points specified within Control Point Sequence (300A,0111). See C.8.8.14.1.</description>
      <section ref="C.8.8.14.1" name="">The Meterset at a given Control Point is equal to the Beam Meterset (300A,0086) specified in the Referenced Beam Sequence (300C,0004) of the RT Fraction Scheme Module, multiplied by the Cumulative Meterset Weight (300A,0134) for the Control Point, divided by the Final Cumulative Meterset Weight (300A,010E). The Meterset is specified in units defined by Primary Dosimeter Unit (300A,00B3). If the calculation for Meterset results in a meterset value which is not an exact multiple of the primary meterset resolution, then the result shall be rounded to the nearest allowed meterset value (i.e. less than a half resolution unit shall be rounded down to the nearest resolution unit, and equal or greater than half a resolution unit shall be rounded up to the nearest resolution unit).
Note also that if Final Cumulative Meterset Weight (300A,010E) is equal to 100, then Cumulative Meterset Weight (300A,0134) becomes equivalent to the percentage of Beam Meterset (300A,0086) delivered at each control point. If Final Cumulative Meterset Weight (300A,010E) is equal to Beam Meterset (300A,0086), then the Cumulative Meterset Weight (300A,0134) at each control point becomes equal to the cumulative Meterset delivered at that control point.
</section>
    </entry>
    <entry group="300A" element="0110" name="&gt;Number of Control Points" type="1">
      <description>Number of control points in Beam.</description>
    </entry>
    <entry group="300A" element="0111" name="&gt;Control Point Sequence" type="1">
      <description>Introduces sequence of machine configurations describing treatment beam. Two or more items may be included in this sequence. See C.8.8.14.5 and C.8.8.14.6.</description>
      <section ref="C.8.8.14.5" name="">The DICOM RT Beams Module uses a single beam model to handle static, arc, and dynamic delivery of external beam radiation by a medical accelerator or gamma beam therapy equipment (cobalt unit). All applicable parameters shall be specified at Control Point 0, with the exception of couch positions (see C.8.8.14.6). All parameters that change at any control point of a given beam shall be specified explicitly at all control points (including those preceding the change). No assumptions are made about the behavior of machine parameters between specified control points, and communicating devices shall agree on this behavior outside the current standard.
Gantry Rotation Direction (300A,011F), Beam Limiting Device Rotation Direction (300A,0121), Patient Support Rotation Direction (300A,0123), and Table Top Eccentric Rotation Direction (300A,0126) are defined as applying to the segment following the control point, and changes to these parameters during treatment may be specified without use of a “non-irradiation” segment. All other Control Point Sequence attributes are defined only at the control point. To unambiguously encode changes in discrete-valued attributes such as Wedge Position (300A,0118) and Nominal Beam Energy (300A,0114), a non-irradiation segment where Cumulative Meterset Weight (300A,0134) does not change, shall be used.
Some examples of beam specification using control points are as follows:

a)  Static delivery:
  Control Point 0: All applicable treatment parameters defined, Cumulative Meterset Weight = 0
  Control Point 1: Cumulative Meterset Weight = 1, no other parameters defined

b)  Arc delivery:
  Control Point 0: All applicable treatment parameters defined, Cumulative Meterset Weight = 0, Gantry Rotation Direction = rotation direction, Gantry Angle = initial angle
  Control Point 1: Cumulative Meterset Weight = 1, Gantry Rotation Direction = NONE, Gantry Angle = final angle

c)  Dynamic delivery of two equally weighted segments:
  Control Point 0: All applicable treatment parameters defined, Cumulative Meterset Weight = 0
  Control Point 1: All changing treatment parameters defined (including those which do not change at this control point), Cumulative Meterset Weight = 0.5
  Control Point 2: All changing treatment parameters defined (including those which do not change at this control point), Cumulative Meterset Weight = 1

d)  Dynamic Delivery of two unequally weighted segments with a step change in table angle:
  Control Point 0: All applicable treatment parameters defined, Patient Support Angle = initial angle, Patient Support Rotation Direction = NONE, Cumulative Meterset Weight = 0
  Control Point 1: All changing parameters defined (including those that do not change at this control point), Cumulative Meterset Weight = 0.3, Patient Support Angle = initial angle, Patient Support Rotation Direction = rotation direction
  Control Point 2: All changing parameters defined (although none should change at this control point), Cumulative Meterset Weight = 0.3, Patient Support Angle = new angle, Patient Support Rotation Direction = NONE
  Control Point 3: All changing parameters defined (including those that do not change at this control point), Cumulative Meterset Weight = 1, Patient Support Angle = new angle, Patient Support Rotation Direction = NONE

</section>
    </entry>
    <entry group="300A" element="0112" name="&gt;&gt;Control Point Index" type="1C">
      <description>Index of current Control Point, starting at 0 for first Control Point. Required if Control Point Sequence (300A,0111) is sent.</description>
    </entry>
    <entry group="300A" element="0134" name="&gt;&gt;Cumulative Meterset Weight" type="2C">
      <description>Cumulative weight to current control point. Cumulative Meterset Weight for the first item in Control Point Sequence shall always be zero. Cumulative Meterset Weight for the final item in Control Point Sequence shall always be equal to Final Cumulative Meterset Weight. Required if Control Point Sequence (300A,0111) is sent. See C.8.8.14.1.</description>
      <section ref="C.8.8.14.1" name="">The Meterset at a given Control Point is equal to the Beam Meterset (300A,0086) specified in the Referenced Beam Sequence (300C,0004) of the RT Fraction Scheme Module, multiplied by the Cumulative Meterset Weight (300A,0134) for the Control Point, divided by the Final Cumulative Meterset Weight (300A,010E). The Meterset is specified in units defined by Primary Dosimeter Unit (300A,00B3). If the calculation for Meterset results in a meterset value which is not an exact multiple of the primary meterset resolution, then the result shall be rounded to the nearest allowed meterset value (i.e. less than a half resolution unit shall be rounded down to the nearest resolution unit, and equal or greater than half a resolution unit shall be rounded up to the nearest resolution unit).
Note also that if Final Cumulative Meterset Weight (300A,010E) is equal to 100, then Cumulative Meterset Weight (300A,0134) becomes equivalent to the percentage of Beam Meterset (300A,0086) delivered at each control point. If Final Cumulative Meterset Weight (300A,010E) is equal to Beam Meterset (300A,0086), then the Cumulative Meterset Weight (300A,0134) at each control point becomes equal to the cumulative Meterset delivered at that control point.
</section>
    </entry>
    <entry group="300C" element="0050" name="&gt;&gt;Referenced Dose Reference Sequence" type="3">
      <description>Introduces a sequence of Dose References for current Beam. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;&gt;&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module. Required if Referenced Dose Reference Sequence (300C,0050) is sent.</description>
    </entry>
    <entry group="300A" element="010C" name="&gt;&gt;&gt;Cumulative Dose Reference Coefficient" type="2C">
      <description>Coefficient used to calculate cumulative dose contribution from this Beam to the referenced Dose Reference at the current Control Point. Required if Referenced Dose Reference Sequence (300C,0050) is sent. See C.8.8.14.7.</description>
      <section ref="C.8.8.14.7" name="">The Cumulative Dose Reference Coefficient (300A,010C) is the value by which Beam Dose (300A,0084) is multiplied to obtain the dose to the referenced dose reference site at the current control point (and after previous control points have been successfully administered). The Cumulative Dose Reference Coefficient (300A,010C) is by definition zero for the initial control point. The Cumulative Dose Reference Coefficient (300A,010C) of the final control point multiplied by Beam Dose (300A,0084) results in the final dose to the referenced dose reference site for the current beam. Dose calculation for dose reference sites other than points is not well defined.
</section>
    </entry>
    <entry group="300C" element="0080" name="&gt;&gt;Referenced Dose Sequence" type="1C">
      <description>Sequence describing related instances of RT Dose (for grids, isodose curves, and named/unnamed point doses). One or more items may be included in this sequence.
Required if RT Dose is being sent, and Dose Summation Type (3004,000A) equals CONTROL_POINT.</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="300A" element="0114" name="&gt;&gt;Nominal Beam Energy" type="3">
      <description>Nominal Beam Energy at control point (MV/MeV).</description>
    </entry>
    <entry group="300A" element="0115" name="&gt;&gt;Dose Rate Set" type="3">
      <description>Dose Rate to be set on treatment machine for segment beginning at current control point (e.g. MU/min).</description>
    </entry>
    <entry group="300A" element="0116" name="&gt;&gt;Wedge Position Sequence" type="3">
      <description>A Sequence of Items describing Wedge Positions for the current control point.
Required for first item of Control Point Sequence if Number of Wedges (300A,00D0) is non-zero, and in subsequent control points if Wedge Position (300A,0118) changes during Beam. See C.8.8.14.5.
The number of items in this sequence shall equal the value of Number of Wedges (300A,00D0).</description>
      <section ref="C.8.8.14.5" name="">The DICOM RT Beams Module uses a single beam model to handle static, arc, and dynamic delivery of external beam radiation by a medical accelerator or gamma beam therapy equipment (cobalt unit). All applicable parameters shall be specified at Control Point 0, with the exception of couch positions (see C.8.8.14.6). All parameters that change at any control point of a given beam shall be specified explicitly at all control points (including those preceding the change). No assumptions are made about the behavior of machine parameters between specified control points, and communicating devices shall agree on this behavior outside the current standard.
Gantry Rotation Direction (300A,011F), Beam Limiting Device Rotation Direction (300A,0121), Patient Support Rotation Direction (300A,0123), and Table Top Eccentric Rotation Direction (300A,0126) are defined as applying to the segment following the control point, and changes to these parameters during treatment may be specified without use of a “non-irradiation” segment. All other Control Point Sequence attributes are defined only at the control point. To unambiguously encode changes in discrete-valued attributes such as Wedge Position (300A,0118) and Nominal Beam Energy (300A,0114), a non-irradiation segment where Cumulative Meterset Weight (300A,0134) does not change, shall be used.
Some examples of beam specification using control points are as follows:

a)  Static delivery:
  Control Point 0: All applicable treatment parameters defined, Cumulative Meterset Weight = 0
  Control Point 1: Cumulative Meterset Weight = 1, no other parameters defined

b)  Arc delivery:
  Control Point 0: All applicable treatment parameters defined, Cumulative Meterset Weight = 0, Gantry Rotation Direction = rotation direction, Gantry Angle = initial angle
  Control Point 1: Cumulative Meterset Weight = 1, Gantry Rotation Direction = NONE, Gantry Angle = final angle

c)  Dynamic delivery of two equally weighted segments:
  Control Point 0: All applicable treatment parameters defined, Cumulative Meterset Weight = 0
  Control Point 1: All changing treatment parameters defined (including those which do not change at this control point), Cumulative Meterset Weight = 0.5
  Control Point 2: All changing treatment parameters defined (including those which do not change at this control point), Cumulative Meterset Weight = 1

d)  Dynamic Delivery of two unequally weighted segments with a step change in table angle:
  Control Point 0: All applicable treatment parameters defined, Patient Support Angle = initial angle, Patient Support Rotation Direction = NONE, Cumulative Meterset Weight = 0
  Control Point 1: All changing parameters defined (including those that do not change at this control point), Cumulative Meterset Weight = 0.3, Patient Support Angle = initial angle, Patient Support Rotation Direction = rotation direction
  Control Point 2: All changing parameters defined (although none should change at this control point), Cumulative Meterset Weight = 0.3, Patient Support Angle = new angle, Patient Support Rotation Direction = NONE
  Control Point 3: All changing parameters defined (including those that do not change at this control point), Cumulative Meterset Weight = 1, Patient Support Angle = new angle, Patient Support Rotation Direction = NONE

</section>
    </entry>
    <entry group="300C" element="00C0" name="&gt;&gt;&gt;Referenced Wedge Number" type="1C">
      <description>Uniquely references Wedge described by Wedge Number (300A,00D2) in Wedge Sequence (300A,00D1). Required if Wedge Position Sequence (300A,0116) is sent.</description>
    </entry>
    <entry group="300A" element="0118" name="&gt;&gt;&gt;Wedge Position" type="1C">
      <description>Position of Wedge at current Control Point. Required if Wedge Position Sequence (300A,0116) is sent.
Enumerated Values:
IN
OUT</description>
    </entry>
    <entry group="300A" element="011A" name="&gt;&gt;Beam Limiting Device Position Sequence" type="1C">
      <description>Introduces sequence of beam limiting device (collimator) jaw or leaf (element) positions. Required for first item of Control Point Sequence, or if Beam Limiting Device changes during Beam. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00B8" name="&gt;&gt;&gt;RT Beam Limiting Device Type" type="1C">
      <description>Type of beam limiting device (collimator). The value of this attribute shall correspond to RT Beam Limiting Device Type (300A,00B8) defined in an item of Beam Limiting Device Sequence (300A,00B6). Required if Beam Limiting Device Position Sequence (300A,011A) is sent.
Enumerated Values:
X = symmetric jaw pair in IEC X direction
Y = symmetric jaw pair in IEC Y direction
ASYMX = asymmetric jaw pair in IEC X direction
ASYMY = asymmetric pair in IEC Y direction
MLCX = multileaf (multi-element) jaw pair in IEC X direction
MLCY = multileaf (multi-element) jaw pair in IEC Y direction</description>
    </entry>
    <entry group="300A" element="011C" name="&gt;&gt;&gt;Leaf/Jaw Positions" type="1C">
      <description>Positions of beam limiting device (collimator) leaf (element) or jaw pairs (in mm) in IEC BEAM LIMITING DEVICE coordinate axis appropriate to RT Beam Limiting Device Type (300A,00B8), e.g. X-axis for MLCX, Y-axis for MLCY. Contains 2N values, where N is the Number of Leaf/Jaw Pairs (300A,00BC) in Beam Limiting Device Sequence (300A,00B6). Values shall be listed in IEC leaf (element) subscript order 101, 102, ... 1N, 201, 202, ... 2N. Required if Beam Limiting Device Position Sequence (300A,011A) is sent. See Note 2.</description>
    </entry>
    <entry group="300A" element="011E" name="&gt;&gt;Gantry Angle" type="1C">
      <description>Gantry angle of radiation source, i.e. orientation of IEC GANTRY coordinate system with respect to IEC FIXED REFERENCE coordinate system (degrees). Required for first item of Control Point Sequence, or if Gantry Angle changes during Beam.</description>
    </entry>
    <entry group="300A" element="011F" name="&gt;&gt;Gantry Rotation Direction" type="1C">
      <description>Direction of Gantry Rotation when viewing gantry from isocenter, for segment following Control Point. Required for first item of Control Point Sequence, or if Gantry Rotation Direction changes during Beam. See C.8.8.14.8.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="014A" name="&gt;&gt;Gantry Pitch Angle" type="3">
      <description>Gantry Pitch Angle. i.e. the rotation of the IEC GANTRY coordinate system about the X-axis of the IEC GANTRY coordinate system (degrees). If used, must be present for first item of Control Point Sequence, or if used and Gantry Pitch Rotation Angle changes during Beam, must be present. See C.8.8.25.6.5.</description>
      <section ref="C.8.8.25.6.5" name="">The Gantry Pitch angle is not defined in IEC 61217. This angle is defined in the DICOM standard in a way compatible with the current notion of IEC by introducing it as rotation of the IEC GANTRY System as indicated below.
The Gantry Pitch Angle is defined as the rotation of the coordinate axes Yg, Zg about axis Xg by an angle g; see Figure C.8.8.25-7. An increase in the value of angle g corresponds to the clockwise rotation as viewed from the isocenter along the positive Xg axis


Figure C.8.8.25-7 Gantry Pitch Angle
</section>
    </entry>
    <entry group="300A" element="014C" name="&gt;&gt;Gantry Pitch Rotation Direction" type="3">
      <description>Direction of Gantry Pitch Angle when viewing along the positive X-axis of the IEC GANTRY coordinate system, for segment following Control Point. If used, must be present for first item of Control Point Sequence, or if used and Gantry Pitch Rotation Direction changes during Beam, must be present. See C.8.8.14.8 and C.8.8.25.6.5.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0120" name="&gt;&gt;Beam Limiting Device Angle" type="1C">
      <description>Beam Limiting Device angle, i.e. orientation of IEC BEAM LIMITING DEVICE coordinate system with respect to IEC GANTRY coordinate system (degrees). Required for first item of Control Point Sequence, or if Beam Limiting Device Angle changes during Beam.</description>
    </entry>
    <entry group="300A" element="0121" name="&gt;&gt;Beam Limiting Device Rotation Direction" type="1C">
      <description>Direction of Beam Limiting Device Rotation when viewing beam limiting device (collimator) from radiation source, for segment following Control Point. Required for first item of Control Point Sequence, or if Beam Limiting Device Rotation Direction changes during Beam. See C.8.8.14.8.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0122" name="&gt;&gt;Patient Support Angle" type="1C">
      <description>Patient Support angle, i.e. orientation of IEC PATIENT SUPPORT (turntable) coordinate system with respect to IEC FIXED REFERENCE coordinate system (degrees). Required for first item of Control Point Sequence, or if Patient Support Angle changes during Beam.</description>
    </entry>
    <entry group="300A" element="0123" name="&gt;&gt;Patient Support Rotation Direction" type="1C">
      <description>Direction of Patient Support Rotation when viewing table from above, for segment following Control Point. Required for first item of Control Point Sequence, or if Patient Support Rotation Direction changes during Beam. See C.8.8.14.8.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0124" name="&gt;&gt;Table Top Eccentric Axis Distance" type="3">
      <description>Distance (positive) from the IEC PATIENT SUPPORT vertical axis to the IEC TABLE TOP ECCENTRIC vertical axis (mm).</description>
    </entry>
    <entry group="300A" element="0125" name="&gt;&gt;Table Top Eccentric Angle" type="1C">
      <description>Table Top (non-isocentric) angle, i.e. orientation of IEC TABLE TOP ECCENTRIC coordinate system with respect to IEC PATIENT SUPPORT coordinate system (degrees). Required for first item of Control Point Sequence, or if Table Top Eccentric Angle changes during Beam.</description>
    </entry>
    <entry group="300A" element="0126" name="&gt;&gt;Table Top Eccentric Rotation Direction" type="1C">
      <description>Direction of Table Top Eccentric Rotation when viewing table from above, for segment following Control Point. Required for first item of Control Point Sequence, or if Table Top Eccentric Rotation Direction changes during Beam. See C.8.8.14.8.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0140" name="&gt;&gt;Table Top Pitch Angle" type="1C">
      <description>Table Top Pitch Angle, i.e. the rotation of the IEC TABLE TOP coordinate system about the X-axis of the IEC TABLE TOP coordinate system (degrees). If required by treatment delivery device, shall be present for first item of Control Point Sequence. If required by treatment delivery device and if Table Top Pitch Angle changes during Beam, shall be present in all subsequent items of Control Point Sequence. See C.8.8.25.6.2.</description>
      <section ref="C.8.8.25.6.2" name="">Pitch and Roll Coordinate Systems of the Table Top are not defined in IEC 61217. These angles are defined in the DICOM standard in a way compatible with the current notion of IEC by introducing them as rotations of the IEC Table Top System as indicated below.
The Table Top Pitch Angle is defined as the rotation of the coordinate axes Yt, Zt about axis Xt by an angle t; see Figure C.8.8.25-3. An increase in the value of angle t corresponds to the clockwise rotation of the Table Top as viewed from the Table Top coordinate system origin along the positive Xt axis.
The Table Top Roll Angle is defined as the rotation of the coordinate axes Xt, Zt about axis Yt by an angle t; see Figure C.8.8.25-4. An increase in the value of angle t corresponds to the clockwise rotation of the Table Top as viewed from the Table Top coordinate system origin along the positive Yt axis.


Figure C.8.8.25-3 Table Top Pitch Angle

Figure C.8.8.25-4 Table Top Roll Angle

</section>
    </entry>
    <entry group="300A" element="0142" name="&gt;&gt; Table Top Pitch Rotation Direction" type="1C">
      <description>Direction of Table Top Pitch Rotation when viewing the table along the positive X-axis of the IEC TABLE TOP coordinate system, for segment following Control Point. If required by treatment delivery device, shall be present for first item of Control Point Sequence. If required by treatment delivery device and if Table Top Pitch Rotation Direction changes during Beam, shall be present in all subsequent items of Control Point Sequence. See C.8.8.14.8 and C.8.8.25.6.2.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0144" name="&gt;&gt;Table Top Roll Angle" type="1C">
      <description>Table Top Roll Angle, i.e. the rotation of the IEC TABLE TOP coordinate system about the IEC Y-axis of the IEC TABLE TOP coordinate system (degrees). If required by treatment delivery device, shall be present for first item of Control Point Sequence. If required by treatment delivery device and if Table Top Roll Angle changes during Beam, shall be present in all subsequent items of Control Point Sequence. See C.8.8.25.6.2.</description>
      <section ref="C.8.8.25.6.2" name="">Pitch and Roll Coordinate Systems of the Table Top are not defined in IEC 61217. These angles are defined in the DICOM standard in a way compatible with the current notion of IEC by introducing them as rotations of the IEC Table Top System as indicated below.
The Table Top Pitch Angle is defined as the rotation of the coordinate axes Yt, Zt about axis Xt by an angle t; see Figure C.8.8.25-3. An increase in the value of angle t corresponds to the clockwise rotation of the Table Top as viewed from the Table Top coordinate system origin along the positive Xt axis.
The Table Top Roll Angle is defined as the rotation of the coordinate axes Xt, Zt about axis Yt by an angle t; see Figure C.8.8.25-4. An increase in the value of angle t corresponds to the clockwise rotation of the Table Top as viewed from the Table Top coordinate system origin along the positive Yt axis.


Figure C.8.8.25-3 Table Top Pitch Angle

Figure C.8.8.25-4 Table Top Roll Angle

</section>
    </entry>
    <entry group="300A" element="0146" name="&gt;&gt; Table Top Roll Rotation Direction" type="1C">
      <description>Direction of Table Top Roll Rotation when viewing the table along the positive Y-axis of the IEC TABLE TOP coordinate system, for segment following Control Point. If required by treatment delivery device, shall be present for first item of Control Point Sequence. If required by treatment delivery device and if Table Top Roll Rotation Direction changes during Beam, shall be present in all subsequent items of Control Point Sequence. See C.8.8.14.8 and C.8.8.25.6.2.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0128" name="&gt;&gt;Table Top Vertical Position" type="2C">
      <description>Table Top Vertical position in IEC TABLE TOP coordinate system (mm). Required for first item of Control Point Sequence, or if Table Top Vertical Position changes during Beam. See C.8.8.14.6.</description>
      <section ref="C.8.8.14.6" name="">All treatment machine parameters except couch translations are specified in absolute machine coordinates as defined by IEC 61217. For the Table Top Vertical Position (300A,0128), Table Top Longitudinal Position (300A,0129), and Table Top Lateral Position (300A,012A), if the first Control Point contains a value of non-zero length, all subsequent Control Point position values are absolute values in their respective coordinate system. If the first Control Point contains a zero-length value, all subsequent Control Point position values are specified relative to the (unknown) initial value.
</section>
    </entry>
    <entry group="300A" element="0129" name="&gt;&gt;Table Top Longitudinal Position" type="2C">
      <description>Table Top Longitudinal position in IEC TABLE TOP coordinate system (mm). Required for first item of Control Point Sequence, or if Table Top Longitudinal Position changes during Beam. See C.8.8.14.6.</description>
      <section ref="C.8.8.14.6" name="">All treatment machine parameters except couch translations are specified in absolute machine coordinates as defined by IEC 61217. For the Table Top Vertical Position (300A,0128), Table Top Longitudinal Position (300A,0129), and Table Top Lateral Position (300A,012A), if the first Control Point contains a value of non-zero length, all subsequent Control Point position values are absolute values in their respective coordinate system. If the first Control Point contains a zero-length value, all subsequent Control Point position values are specified relative to the (unknown) initial value.
</section>
    </entry>
    <entry group="300A" element="012A" name="&gt;&gt;Table Top Lateral Position" type="2C">
      <description>Table Top Lateral position in IEC TABLE TOP coordinate system (mm). Required for first item of Control Point Sequence, or if Table Top Lateral Position changes during Beam. See C.8.8.14.6.</description>
      <section ref="C.8.8.14.6" name="">All treatment machine parameters except couch translations are specified in absolute machine coordinates as defined by IEC 61217. For the Table Top Vertical Position (300A,0128), Table Top Longitudinal Position (300A,0129), and Table Top Lateral Position (300A,012A), if the first Control Point contains a value of non-zero length, all subsequent Control Point position values are absolute values in their respective coordinate system. If the first Control Point contains a zero-length value, all subsequent Control Point position values are specified relative to the (unknown) initial value.
</section>
    </entry>
    <entry group="300A" element="012C" name="&gt;&gt;Isocenter Position" type="2C">
      <description>Isocenter coordinates (x,y,z) in the patient based coordinate system described in C.7.6.2.1.1 (mm). Required for first item of Segment Control Point Sequence, or if Segment Isocenter Position changes during Beam.</description>
    </entry>
    <entry group="300A" element="012E" name="&gt;&gt;Surface Entry Point" type="3">
      <description>Patient surface entry point coordinates (x,y,z) in the patient based coordinate system described in C.7.6.2.1.1 (mm).</description>
    </entry>
    <entry group="300A" element="0130" name="&gt;&gt;Source to Surface Distance" type="3">
      <description>Source to Patient Surface distance (mm).</description>
    </entry>
  </module>
  <module ref="C.8.8.15" table="C.8-51" name="RT Brachy Application Setups Module Attributes">
    <entry group="300A" element="0200" name="Brachy Treatment Technique" type="1">
      <description>Type of brachytherapy treatment technique. Enumerated Values:
INTRALUMENARY
INTRACAVITARY
INTERSTITIAL
CONTACT
INTRAVASCULAR
PERMANENT
See C.8.8.15.1.</description>
      <section ref="C.8.8.15.1" name="">In permanent implant techniques the value for Channel Total Time (300A,0286) shall be mean life time of the isotope. The Brachy Control Point Sequence (300A,02D0) shall consist of two items: the first having Cumulative Time Weight (300A,02D6) = 0 and the second having Cumulative Time Weight (300A,02D6) = Final Cumulative Time Weight (300A,02C8).
</section>
    </entry>
    <entry group="300A" element="0202" name="Brachy Treatment Type" type="1">
      <description>Type of brachytherapy treatment.
Defined Terms:
MANUAL = manually positioned
HDR = High dose rate
MDR = Medium dose rate
LDR = Low dose rate
PDR = Pulsed dose rate</description>
    </entry>
    <entry group="300A" element="0206" name="Treatment Machine Sequence" type="1">
      <description>Introduces single item sequence describing treatment machine to be used for treatment delivery. Only one item may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00B2" name="&gt;Treatment Machine Name" type="2">
      <description>User-defined name identifying treatment machine to be used for treatment delivery.</description>
    </entry>
    <entry group="0008" element="0070" name="&gt;Manufacturer" type="3">
      <description>Manufacturer of the equipment to be used for treatment delivery.</description>
    </entry>
    <entry group="0008" element="0080" name="&gt;Institution Name" type="3">
      <description>Institution where the equipment is located that is to be used for treatment delivery.</description>
    </entry>
    <entry group="0008" element="0081" name="&gt;Institution Address" type="3">
      <description>Mailing address of the institution where the equipment is located that is to be used for treatment delivery.</description>
    </entry>
    <entry group="0008" element="1040" name="&gt;Institutional Department Name" type="3">
      <description>Department in the institution where the equipment is located that is to be used for treatment delivery.</description>
    </entry>
    <entry group="0008" element="1090" name="&gt;Manufacturer's Model Name" type="3">
      <description>Manufacturer's model name of the equipment that is to be used for treatment delivery.</description>
    </entry>
    <entry group="0018" element="1000" name="&gt;Device Serial Number" type="3">
      <description>Manufacturer's serial number of the equipment that is to be used for treatment delivery.</description>
    </entry>
    <entry group="300A" element="0210" name="Source Sequence" type="1">
      <description>Introduces sequence of Sources to be used within Application Setups. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="0212" name="&gt;Source Number" type="1">
      <description>Identification number of the Source. The value of Source Number (300A,0212) shall be unique within the RT Plan in which it is created.</description>
    </entry>
    <entry group="300A" element="0214" name="&gt;Source Type" type="1">
      <description>Type of Source. Defined Terms:
POINT
LINE
CYLINDER
SPHERE</description>
    </entry>
    <entry group="300A" element="0216" name="&gt;Source Manufacturer" type="3">
      <description>Manufacturer of Source.</description>
    </entry>
    <entry group="300A" element="0218" name="&gt;Active Source Diameter" type="3">
      <description>Diameter of active Source (mm).</description>
    </entry>
    <entry group="300A" element="021A" name="&gt;Active Source Length" type="3">
      <description>Length of active Source (mm).</description>
    </entry>
    <entry group="300A" element="00E1" name="&gt;Material ID" type="3">
      <description>User-supplied identifier for encapsulation material of active Source.</description>
    </entry>
    <entry group="300A" element="0222" name="&gt;Source Encapsulation Nominal Thickness" type="3">
      <description>Nominal thickness of wall of encapsulation (mm). See C.8.8.15.12.</description>
      <section ref="C.8.8.15.12" name="">If provided, Source Encapsulation Nominal Thickness (300A,0222), Brachy Accessory Device Nominal Thickness (300A,026A), Source Applicator Wall Nominal Thickness (300A,029C), and Channel Shield Nominal Thickness (300A,02B8) shall indicate that the related objects are of uniform thickness with the specified value. If this is not the case, these attributes shall not be provided.
If provided, Source Encapsulation Nominal Transmission (300A,0224), Brachy Accessory Device Nominal Transmission (300A,026C), Source Applicator Wall Nominal Transmission (300A,029E), and Channel Shield Nominal Transmission (300A,02BA) shall indicate that the related objects are of uniform transmission with the specified value. If this is not the case, these attributes shall not be provided.
No assumptions are made about the source characteristics beyond the parameters specified here.
</section>
    </entry>
    <entry group="300A" element="0224" name="&gt;Source Encapsulation Nominal Transmission" type="3">
      <description>Nominal transmission through wall of encapsulation (between 0 and 1). See C.8.8.15.12</description>
      <section ref="C.8.8.15.12" name="">If provided, Source Encapsulation Nominal Thickness (300A,0222), Brachy Accessory Device Nominal Thickness (300A,026A), Source Applicator Wall Nominal Thickness (300A,029C), and Channel Shield Nominal Thickness (300A,02B8) shall indicate that the related objects are of uniform thickness with the specified value. If this is not the case, these attributes shall not be provided.
If provided, Source Encapsulation Nominal Transmission (300A,0224), Brachy Accessory Device Nominal Transmission (300A,026C), Source Applicator Wall Nominal Transmission (300A,029E), and Channel Shield Nominal Transmission (300A,02BA) shall indicate that the related objects are of uniform transmission with the specified value. If this is not the case, these attributes shall not be provided.
No assumptions are made about the source characteristics beyond the parameters specified here.
</section>
    </entry>
    <entry group="300A" element="0226" name="&gt;Source Isotope Name" type="1">
      <description>Name of Isotope.</description>
    </entry>
    <entry group="300A" element="0228" name="&gt;Source Isotope Half Life" type="1">
      <description>Half-life of Isotope (days).</description>
    </entry>
    <entry group="300A" element="0229" name="&gt;Source Strength Units" type="1C">
      <description>Measurement unit of Source Strength.
Required if the source is not a gamma-emitting (photon) source. May be present otherwise.
Enumerated Values:
AIR_KERMA_RATE = Air Kerma Rate if Source is Gamma emitting Isotope.
DOSE_RATE_WATER = Dose Rate in Water if Source is Beta emitting Isotope.</description>
    </entry>
    <entry group="300A" element="022A" name="&gt;Reference Air Kerma Rate" type="1">
      <description>Air Kerma Rate in air of Isotope specified at Air Kerma Rate Reference Date (300A,022C) and Air Kerma Rate Reference Time (300A,022E) (in µGy h-1 at 1 m). Value shall be zero for non-gamma sources.</description>
    </entry>
    <entry group="300A" element="022B" name="&gt;Source Strength" type="1C">
      <description>Source Strength of Isotope at Source Strength Reference Date (300A,022C) and Source Strength Reference Time (300A,022E), in units specified in Source Strength Units (300A,0229).
Required if the source is not a gamma-emitting (photon) source. See C.8.8.15.13.</description>
      <section ref="C.8.8.15.13" name="">For beta emitting isotopes, the Source Strength (300A,022B) shall be defined at reference point (r0,θ0), where r0 is the radial distance of 2 mm from the source longitudinal axis, and θ0 is the angle of 90 degrees between the source longitudinal axis and the line defined by the center of the source and the reference point. Refer to:
•  IEC 60601-2-17 (Medical electrical equipment – Particular requirements for the safety of automatically-controlled brachytherapy afterloading equipment), where the beta source strength is defined as: ABSORBED DOSE RATE [Gy s-1] in water at 2 mm along the perpendicular bisector from a RADIOACTIVE SOURCE emitting beta RADIATION.
•  Nath et. al.: Intravascular brachytherapy physics: Report of the AAPM Radiation Therapy Committee Task Group No. 60, Med. Phys 26 (2) Feb 1999, pp 119-152.
</section>
    </entry>
    <entry group="300A" element="022C" name="&gt;Source Strength Reference Date" type="1">
      <description>Reference date for Reference Air Kerma Rate (300A,022A) or Source Strength (300A,022B) of Isotope.</description>
    </entry>
    <entry group="300A" element="022E" name="&gt;Source Strength Rate Reference Time" type="1">
      <description>Reference time for Air Kerma Rate (300A,022A) or Source Strength (300A,022B) of Isotope.</description>
    </entry>
    <entry group="300A" element="0230" name="Application Setup Sequence" type="1">
      <description>Introduces sequence of Application Setups for current RT Plan. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="0232" name="&gt;Application Setup Type" type="1">
      <description>Type of Application Setup. Defined Terms:
FLETCHER_SUIT
DELCLOS
BLOEDORN
JOSLIN_FLYNN
CHANDIGARH
MANCHESTER
HENSCHKE
NASOPHARYNGEAL
OESOPHAGEAL
ENDOBRONCHIAL
SYED_NEBLETT
ENDORECTAL
PERINEAL</description>
    </entry>
    <entry group="300A" element="0234" name="&gt;Application Setup Number" type="1">
      <description>Identification number of the Application Setup. The value of Application Setup Number (300A,0234) shall be unique within the RT Plan in which it is created.</description>
    </entry>
    <entry group="300A" element="0236" name="&gt;Application Setup Name" type="3">
      <description>User-defined name for Application Setup.</description>
    </entry>
    <entry group="300A" element="0238" name="&gt;Application Setup Manufacturer" type="3">
      <description>Manufacturer of Application Setup.</description>
    </entry>
    <entry group="300A" element="0240" name="&gt;Template Number" type="3">
      <description>Identification number of the Template. The value of Template Number (300A,0240) shall be unique within the Application Setup in which it is created.</description>
    </entry>
    <entry group="300A" element="0242" name="&gt;Template Type" type="3">
      <description>User-defined type for Template Device.</description>
    </entry>
    <entry group="300A" element="0244" name="&gt;Template Name" type="3">
      <description>User-defined name for Template Device.</description>
    </entry>
    <entry group="300C" element="0042" name="&gt;Referenced Reference Image Sequence" type="3">
      <description>Introduces sequence of reference images used for validation of current Application Setup. One or more items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="300A" element="0250" name="&gt;Total Reference Air Kerma" type="1">
      <description>Total Reference Air Kerma for current Application Setup, i.e. the product of Air Kerma Rate of all Sources in all Channels with their respective Channel Times (µGy at 1 m). Value shall be zero for non-gamma sources.</description>
    </entry>
    <entry group="300A" element="0260" name="&gt;Brachy Accessory Device Sequence" type="3">
      <description>Introduces sequence of Brachy Accessory Devices associated with current Application Setup. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="0262" name="&gt;&gt;Brachy Accessory Device Number" type="2C">
      <description>Identification number of the Brachy Accessory Device. The value of Brachy Accessory Device Number (300A,0262) shall be unique within the Application Setup in which it is created. Required if Brachy Accessory Device Sequence (300A,0260) is sent.</description>
    </entry>
    <entry group="300A" element="0263" name="&gt;&gt;Brachy Accessory Device ID" type="2C">
      <description>User or machine supplied identifier for Brachy Accessory Device. Required if Brachy Accessory Device Sequence (300A,0260) is sent.</description>
    </entry>
    <entry group="300A" element="0264" name="&gt;&gt;Brachy Accessory Device Type" type="1C">
      <description>Type of Brachy Accessory Device. Required if Brachy Accessory Device Sequence (300A,0260) is sent. Defined Terms:
SHIELD
DILATATION
MOLD
PLAQUE
FLAB</description>
    </entry>
    <entry group="300A" element="0266" name="&gt;&gt;Brachy Accessory Device Name" type="3">
      <description>User-defined name for Brachy Accessory Device.</description>
    </entry>
    <entry group="300A" element="00E1" name="&gt;&gt;Material ID" type="3">
      <description>User-supplied identifier for material of Brachy Accessory Device. See Note.</description>
    </entry>
    <entry group="300A" element="026A" name="&gt;&gt; Brachy Accessory Device Nominal Thickness" type="3">
      <description>Nominal thickness of Brachy Accessory Device (mm). See C.8.8.15.12.</description>
      <section ref="C.8.8.15.12" name="">If provided, Source Encapsulation Nominal Thickness (300A,0222), Brachy Accessory Device Nominal Thickness (300A,026A), Source Applicator Wall Nominal Thickness (300A,029C), and Channel Shield Nominal Thickness (300A,02B8) shall indicate that the related objects are of uniform thickness with the specified value. If this is not the case, these attributes shall not be provided.
If provided, Source Encapsulation Nominal Transmission (300A,0224), Brachy Accessory Device Nominal Transmission (300A,026C), Source Applicator Wall Nominal Transmission (300A,029E), and Channel Shield Nominal Transmission (300A,02BA) shall indicate that the related objects are of uniform transmission with the specified value. If this is not the case, these attributes shall not be provided.
No assumptions are made about the source characteristics beyond the parameters specified here.
</section>
    </entry>
    <entry group="300A" element="026C" name="&gt;&gt; Brachy Accessory Device Nominal Transmission" type="3">
      <description>Nominal Transmission through Brachy Accessory Device (between 0 and 1). See C.8.8.15.12.</description>
      <section ref="C.8.8.15.12" name="">If provided, Source Encapsulation Nominal Thickness (300A,0222), Brachy Accessory Device Nominal Thickness (300A,026A), Source Applicator Wall Nominal Thickness (300A,029C), and Channel Shield Nominal Thickness (300A,02B8) shall indicate that the related objects are of uniform thickness with the specified value. If this is not the case, these attributes shall not be provided.
If provided, Source Encapsulation Nominal Transmission (300A,0224), Brachy Accessory Device Nominal Transmission (300A,026C), Source Applicator Wall Nominal Transmission (300A,029E), and Channel Shield Nominal Transmission (300A,02BA) shall indicate that the related objects are of uniform transmission with the specified value. If this is not the case, these attributes shall not be provided.
No assumptions are made about the source characteristics beyond the parameters specified here.
</section>
    </entry>
    <entry group="3006" element="0084" name="&gt;&gt;Referenced ROI Number" type="2C">
      <description>Uniquely identifies ROI representing the Brachy Accessory specified by ROI Number (3006,0022) in Structure Set ROI Sequence (3006,0020) in Structure Set Module within RT Structure Set referenced by Referenced RT Structure Set Sequence (300C,0060) in RT General Plan Module. Required if Brachy Accessory Device Sequence (300A,0260) is sent. See C.8.8.15.2.</description>
      <section ref="C.8.8.15.2" name="">The Structure Set ROI shall be used in the Brachy Application Setups Module to describe the 3D coordinates of Accessory Devices, Applicators and Channel Shields, but not individual source positions (see C.8.8.15.9 and C.8.8.15.10).
</section>
    </entry>
    <entry group="300A" element="0280" name="&gt;Channel Sequence" type="1">
      <description>Introduces sequence of Channels for current Application Setup. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="0282" name="&gt;&gt;Channel Number" type="1">
      <description>Identification number of the Channel. The value of Channel Number (300A,0282) shall be unique within the Application Setup in which it is created.</description>
    </entry>
    <entry group="300A" element="0284" name="&gt;&gt;Channel Length" type="2">
      <description>Length of Channel (mm). See C.8.8.15.3.</description>
      <section ref="C.8.8.15.3" name="">If specified, the Channel Length (300A,0284) shall be the sum of the Source Applicator Length (300A,0296) and Transfer Tube Length (300A,02A4).
</section>
    </entry>
    <entry group="300A" element="0286" name="&gt;&gt;Channel Total Time" type="1">
      <description>Total amount of time between first and final Control Points of the Brachy Control Point Sequence (300A,02D0) for current Channel (sec). Channel Total Time calculation is based upon the Reference Air Kerma Rate (300A,022A) of the Referenced Source Number (300C,000E).</description>
    </entry>
    <entry group="300A" element="0288" name="&gt;&gt;Source Movement Type" type="1">
      <description>Type of Source movement. See C.8.8.15.4. Defined Terms:
STEPWISE
FIXED
OSCILLATING
UNIDIRECTIONAL</description>
      <section ref="C.8.8.15.4" name="">In brachytherapy treatment techniques involving oscillating source movement (i.e. when Source Movement Type (300A,0288) is OSCILLATING), the Brachy Control Point Sequence (300A,02D0) shall consist of two items. The first Control Point shall have Cumulative Time Weight (300A,02D6) = 0, and Control Point Relative Position (300A,02D2) equal to one end point of the oscillation. The second Control Point shall have Cumulative Time Weight (300A,02D6) = Final Cumulative Time Weight (300A,02C8), and Control Point Relative Position (300A,02D2) equal to the other end point of the oscillation. Transit time shall not be modeled explicitly for oscillating techniques.
</section>
    </entry>
    <entry group="300A" element="028A" name="&gt;&gt;Number of Pulses" type="1C">
      <description>Number of Pulses per fraction for current Channel. Required if Brachy Treatment Type (300A,0202) is PDR.</description>
    </entry>
    <entry group="300A" element="028C" name="&gt;&gt;Pulse Repetition Interval" type="1C">
      <description>Pulse repetition interval (sec) for current Channel. Required if Brachy Treatment Type (300A,0202) is PDR.</description>
    </entry>
    <entry group="300A" element="0290" name="&gt;&gt;Source Applicator Number" type="3">
      <description>Identification number of the Source Applicator. The value of Source Applicator Number (300A,0290) shall be unique within the Channel in which it is created.</description>
    </entry>
    <entry group="300A" element="0291" name="&gt;&gt;Source Applicator ID" type="2C">
      <description>User or machine supplied identifier for Source Applicator. Required if Source Applicator Number (300A,0290) is sent.</description>
    </entry>
    <entry group="300A" element="0292" name="&gt;&gt;Source Applicator Type" type="1C">
      <description>Type of Source Applicator. Required if Source Applicator Number (300A,0290) is sent. Defined Terms:
FLEXIBLE
RIGID</description>
    </entry>
    <entry group="300A" element="0294" name="&gt;&gt;Source Applicator Name" type="3">
      <description>User-defined name for Source Applicator.</description>
    </entry>
    <entry group="300A" element="0296" name="&gt;&gt;Source Applicator Length" type="1C">
      <description>Length of Source Applicator (mm), defined as the distance between the connector of the applicator and the distal-most position of the source. Required if Source Applicator Number (300A,0290) is sent.</description>
    </entry>
    <entry group="300A" element="0298" name="&gt;&gt;Source Applicator Manufacturer" type="3">
      <description>Manufacturer of Source Applicator.</description>
    </entry>
    <entry group="300A" element="00E1" name="&gt;&gt;Material ID" type="3">
      <description>User-supplied identifier for material of Source Applicator wall. See Note.</description>
    </entry>
    <entry group="300A" element="029C" name="&gt;&gt; Source Applicator Wall Nominal Thickness" type="3">
      <description>Nominal Thickness of Source Applicator wall (mm). See C.8.8.15.12.</description>
      <section ref="C.8.8.15.12" name="">If provided, Source Encapsulation Nominal Thickness (300A,0222), Brachy Accessory Device Nominal Thickness (300A,026A), Source Applicator Wall Nominal Thickness (300A,029C), and Channel Shield Nominal Thickness (300A,02B8) shall indicate that the related objects are of uniform thickness with the specified value. If this is not the case, these attributes shall not be provided.
If provided, Source Encapsulation Nominal Transmission (300A,0224), Brachy Accessory Device Nominal Transmission (300A,026C), Source Applicator Wall Nominal Transmission (300A,029E), and Channel Shield Nominal Transmission (300A,02BA) shall indicate that the related objects are of uniform transmission with the specified value. If this is not the case, these attributes shall not be provided.
No assumptions are made about the source characteristics beyond the parameters specified here.
</section>
    </entry>
    <entry group="300A" element="029E" name="&gt;&gt; Source Applicator Wall Nominal Transmission" type="3">
      <description>Nominal Transmission through Source Applicator wall (between 0 and 1). See C.8.8.15.12.</description>
      <section ref="C.8.8.15.12" name="">If provided, Source Encapsulation Nominal Thickness (300A,0222), Brachy Accessory Device Nominal Thickness (300A,026A), Source Applicator Wall Nominal Thickness (300A,029C), and Channel Shield Nominal Thickness (300A,02B8) shall indicate that the related objects are of uniform thickness with the specified value. If this is not the case, these attributes shall not be provided.
If provided, Source Encapsulation Nominal Transmission (300A,0224), Brachy Accessory Device Nominal Transmission (300A,026C), Source Applicator Wall Nominal Transmission (300A,029E), and Channel Shield Nominal Transmission (300A,02BA) shall indicate that the related objects are of uniform transmission with the specified value. If this is not the case, these attributes shall not be provided.
No assumptions are made about the source characteristics beyond the parameters specified here.
</section>
    </entry>
    <entry group="300A" element="02A0" name="&gt;&gt;Source Applicator Step Size" type="1C">
      <description>Distance of path along channel (in mm) between adjacent (potential) dwell positions. Required if Source Movement Type (300A,0288) is STEPWISE.</description>
    </entry>
    <entry group="3006" element="0084" name="&gt;&gt;Referenced ROI Number" type="2C">
      <description>Uniquely identifies ROI representing the Source Applicator specified by ROI Number (3006,0022) in Structure Set ROI Sequence (3006,0020) in Structure Set Module within RT Structure Set referenced by Referenced RT Structure Set Sequence (300C,0060) in RT General Plan Module. Required if Source Applicator Number (300A,0290) is sent. See C.8.8.15.2.</description>
      <section ref="C.8.8.15.2" name="">The Structure Set ROI shall be used in the Brachy Application Setups Module to describe the 3D coordinates of Accessory Devices, Applicators and Channel Shields, but not individual source positions (see C.8.8.15.9 and C.8.8.15.10).
</section>
    </entry>
    <entry group="300A" element="02A2" name="&gt;&gt;Transfer Tube Number" type="2">
      <description>Identification number of the Transfer Tube. The value of Transfer Tube Number (300A,02A2) shall be unique within the Channel in which it is created.</description>
    </entry>
    <entry group="300A" element="02A4" name="&gt;&gt;Transfer Tube Length" type="2C">
      <description>Length of Transfer Tube of current afterloading Channel (mm). Required if value Transfer Tube Number (300A,02A2) is non-null.</description>
    </entry>
    <entry group="300A" element="02B0" name="&gt;&gt;Channel Shield Sequence" type="3">
      <description>Introduces sequence of Channel Shields associated with current Channel. One or more items may be included in this sequence. See C.8.8.15.5.</description>
      <section ref="C.8.8.15.5" name="">The effect of Channel Shields on dose contributions shall be specific to the Channel for which they are specified. There shall be no effect of these shields on the dose contributions from any other Channels.
</section>
    </entry>
    <entry group="300A" element="02B2" name="&gt;&gt;&gt;Channel Shield Number" type="1C">
      <description>Identification number of the Channel Shield. The value of Channel Shield Number (300A,02B2) shall be unique within the Channel in which it is created. Required if Channel Shield Sequence (300A,02B0) is sent.</description>
    </entry>
    <entry group="300A" element="02B3" name="&gt;&gt;&gt;Channel Shield ID" type="2C">
      <description>User or machine supplied identifier for Channel Shield. Required if Channel Shield Sequence (300A,02B0) is sent.</description>
    </entry>
    <entry group="300A" element="02B4" name="&gt;&gt;&gt;Channel Shield Name" type="3">
      <description>User-defined name for Channel Shield.</description>
    </entry>
    <entry group="300A" element="00E1" name="&gt;&gt;&gt;Material ID" type="3">
      <description>User-supplied identifier for material of Channel Shield. See Note.</description>
    </entry>
    <entry group="300A" element="02B8" name="&gt;&gt;&gt;Channel Shield Nominal Thickness" type="3">
      <description>Nominal Thickness of Channel Shield (mm). See C.8.8.15.12.</description>
      <section ref="C.8.8.15.12" name="">If provided, Source Encapsulation Nominal Thickness (300A,0222), Brachy Accessory Device Nominal Thickness (300A,026A), Source Applicator Wall Nominal Thickness (300A,029C), and Channel Shield Nominal Thickness (300A,02B8) shall indicate that the related objects are of uniform thickness with the specified value. If this is not the case, these attributes shall not be provided.
If provided, Source Encapsulation Nominal Transmission (300A,0224), Brachy Accessory Device Nominal Transmission (300A,026C), Source Applicator Wall Nominal Transmission (300A,029E), and Channel Shield Nominal Transmission (300A,02BA) shall indicate that the related objects are of uniform transmission with the specified value. If this is not the case, these attributes shall not be provided.
No assumptions are made about the source characteristics beyond the parameters specified here.
</section>
    </entry>
    <entry group="300A" element="02BA" name="&gt;&gt;&gt;Channel Shield Nominal Transmission" type="3">
      <description>Nominal Transmission of Channel Shield (between 0 and 1). See C.8.8.15.12.</description>
      <section ref="C.8.8.15.12" name="">If provided, Source Encapsulation Nominal Thickness (300A,0222), Brachy Accessory Device Nominal Thickness (300A,026A), Source Applicator Wall Nominal Thickness (300A,029C), and Channel Shield Nominal Thickness (300A,02B8) shall indicate that the related objects are of uniform thickness with the specified value. If this is not the case, these attributes shall not be provided.
If provided, Source Encapsulation Nominal Transmission (300A,0224), Brachy Accessory Device Nominal Transmission (300A,026C), Source Applicator Wall Nominal Transmission (300A,029E), and Channel Shield Nominal Transmission (300A,02BA) shall indicate that the related objects are of uniform transmission with the specified value. If this is not the case, these attributes shall not be provided.
No assumptions are made about the source characteristics beyond the parameters specified here.
</section>
    </entry>
    <entry group="3006" element="0084" name="&gt;&gt;&gt;Referenced ROI Number" type="2C">
      <description>Uniquely identifies ROI representing the Channel Shield specified by ROI Number (3006,0022) in Structure Set ROI Sequence (3006,0020) in Structure Set Module within RT Structure Set referenced by Referenced RT Structure Set Sequence (300C,0060) in RT General Plan Module. Required if Channel Shield Sequence (300A,02B0) is sent. See C.8.8.15.2.</description>
      <section ref="C.8.8.15.2" name="">The Structure Set ROI shall be used in the Brachy Application Setups Module to describe the 3D coordinates of Accessory Devices, Applicators and Channel Shields, but not individual source positions (see C.8.8.15.9 and C.8.8.15.10).
</section>
    </entry>
    <entry group="300C" element="000E" name="&gt;&gt;Referenced Source Number" type="1">
      <description>Uniquely identifies the referenced Source within the Source Sequence (300A,0210) for current Application Setup.</description>
    </entry>
    <entry group="300A" element="0110" name="&gt;&gt;Number of Control Points" type="1">
      <description>Number of control points in Channel. For an N-segment Channel there will be 2N (stepwise movement) or N+1 (continuous movement) control points.</description>
    </entry>
    <entry group="300A" element="02C8" name="&gt;&gt;Final Cumulative Time Weight" type="1C">
      <description>Value of Cumulative Time Weight (300A,02D6) for final Control Point in Brachy Control Point Sequence (300A,02D0). Required if Cumulative Time Weight (300A,02D6) is non-null in Control Points specified within Brachy Control Point Sequence (300A,02D0). See C.8.8.15.6.</description>
      <section ref="C.8.8.15.6" name="">The treatment time at a given Control Point is equal to the Channel Total Time (300A,0286), multiplied by the Cumulative Time Weight (300A,02D6) for the Control Point, divided by the Final Cumulative Time Weight (300A,02C8). If the calculation for treatment time results in a time value which is not an exact multiple of the timer resolution, then the result shall be rounded to the nearest allowed timer value (i.e. less than a half resolution unit shall be rounded down to the nearest resolution unit, and equal or greater than half a resolution unit shall be rounded up to the nearest resolution unit).
Note also that if Final Cumulative Time Weight (300A,02C8) is equal to 100, then Cumulative Time Weight (300A,02D6) becomes equivalent to the percentage of Channel Total Time (300A,0286) delivered at each control point. If Final Cumulative Time Weight (300A,02C8) is equal to Channel Total Time (300A,0286), then the Cumulative Time Weight (300A,02D6) at each control point becomes equal to the cumulative treatment time delivered at that control point.
If Treatment Type (300A,0202) is PDR, then the Channel Total Time (3008,0286) shall specify the duration of a single pulse.
</section>
    </entry>
    <entry group="300A" element="02D0" name="&gt;&gt;Brachy Control Point Sequence" type="1">
      <description>Introduces sequence of machine configurations describing this Channel. Two or more items may be included in this sequence. See C.8.8.15.7.</description>
      <section ref="C.8.8.15.7" name="">The Control Points shall be arranged such that the first Control Point for a particular Channel describes the first dwell position and the final Control Point for the Channel describes the final dwell position. If Brachy Treatment Type (300A,0202) is PDR, the Brachy Control Point Sequence (300A,02D0) shall specify the sequence of machine configurations for a single pulse. Similarly, if Source Movement Type (300A,0288) is OSCILLATING, the Brachy Control Point Sequence (300A,02D0) shall specify the sequence of machine configurations for a single period.
Some examples of Brachytherapy specification using control points are as follows:

  a) Stepwise motion; Four equally weighted dwell positions; Step size = 10; Final Cumulative Time Weight = 100:

  Control Point 0:  Control Point Relative Position = 30, Cumulative Time Weight = 0
  Control Point 1:   Control Point Relative Position = 30, Cumulative Time Weight = 25
  Control Point 2:   Control Point Relative Position = 20, Cumulative Time Weight = 25
  Control Point 3:   Control Point Relative Position = 20, Cumulative Time Weight = 50
  Control Point 4:   Control Point Relative Position = 10, Cumulative Time Weight = 50
  Control Point 5:   Control Point Relative Position = 10, Cumulative Time Weight = 75
  Control Point 6:   Control Point Relative Position = 0, Cumulative Time Weight = 75
  Control Point 7:   Control Point Relative Position = 0, Cumulative Time Weight = 100

  b) Fixed (manually placed) sources; Final Cumulative Time Weight = 100:

  Control Point 0:  Control Point Relative Position = 0, Control Point 3D Position = (x,y,z),
Cumulative Time Weight = 0
  Control Point 1:  Control Point Relative Position = 0, Control Point 3D Position = (x,y,z),
Cumulative Time Weight = 100

  c) Oscillating movement; Final Cumulative Time Weight = 100:

  Control Point 0:  Control Point Relative Position = 100, Cumulative Time Weight = 0
  Control Point 1:  Control Point Relative Position = 0, Cumulative Time Weight = 100

  d) Unidirectional movement; Final Cumulative Time Weight = 100:

  Control Point 0:  Control Point Relative Position = 0, Cumulative Time Weight = 0
  Control Point 1:  Control Point Relative Position = 100, Cumulative Time Weight = 100

  e) Stepwise motion with consideration of source transit times between dwell positions; Three equally weighted dwell positions; Step size = 10; Final Cumulative Time Weight = 79:

  Control Point 0:  Control Point Relative Position = 30, Cumulative Time Weight = 0
  Control Point 1:   Control Point Relative Position = 30, Cumulative Time Weight = 25
  Control Point 2:   Control Point Relative Position = 20, Cumulative Time Weight = 27
  Control Point 3:   Control Point Relative Position = 20, Cumulative Time Weight = 52
  Control Point 4:   Control Point Relative Position = 10, Cumulative Time Weight = 54
  Control Point 5:   Control Point Relative Position = 10, Cumulative Time Weight = 79

  f) Stepwise motion with consideration of source transit times between dwell positions and to first and from last dwell position; Three equally weighted dwell positions; Step size = 10; Final Cumulative Time Weight = 383:

  Control Point 0:  Control Point Relative Position = 1200, Cumulative Time Weight = 0
  Control Point 1:  Control Point Relative Position = 30, Cumulative Time Weight = 150
  Control Point 2:   Control Point Relative Position = 30, Cumulative Time Weight = 175
  Control Point 3:   Control Point Relative Position = 20, Cumulative Time Weight = 177
  Control Point 4:   Control Point Relative Position = 20, Cumulative Time Weight = 202
  Control Point 5:   Control Point Relative Position = 10, Cumulative Time Weight = 204
  Control Point 6:   Control Point Relative Position = 10, Cumulative Time Weight = 229
  Control Point 7:   Control Point Relative Position = 1200, Cumulative Time Weight = 383

</section>
    </entry>
    <entry group="300A" element="0112" name="&gt;&gt;&gt;Control Point Index" type="1">
      <description>Index of current Control Point, starting at 0 for first Control Point.</description>
    </entry>
    <entry group="300A" element="02D6" name="&gt;&gt;&gt;Cumulative Time Weight" type="2">
      <description>Cumulative time weight to current Control Point (where the weighting is proportional to time values delivered). Cumulative Time Weight for first item in Brachy Control Point Sequence (300A,02D0) is always zero. See C.8.8.15.6 and C.8.8.15.8.</description>
      <section ref="C.8.8.15.6" name="">The treatment time at a given Control Point is equal to the Channel Total Time (300A,0286), multiplied by the Cumulative Time Weight (300A,02D6) for the Control Point, divided by the Final Cumulative Time Weight (300A,02C8). If the calculation for treatment time results in a time value which is not an exact multiple of the timer resolution, then the result shall be rounded to the nearest allowed timer value (i.e. less than a half resolution unit shall be rounded down to the nearest resolution unit, and equal or greater than half a resolution unit shall be rounded up to the nearest resolution unit).
Note also that if Final Cumulative Time Weight (300A,02C8) is equal to 100, then Cumulative Time Weight (300A,02D6) becomes equivalent to the percentage of Channel Total Time (300A,0286) delivered at each control point. If Final Cumulative Time Weight (300A,02C8) is equal to Channel Total Time (300A,0286), then the Cumulative Time Weight (300A,02D6) at each control point becomes equal to the cumulative treatment time delivered at that control point.
If Treatment Type (300A,0202) is PDR, then the Channel Total Time (3008,0286) shall specify the duration of a single pulse.
</section>
    </entry>
    <entry group="300A" element="02D2" name="&gt;&gt;&gt;Control Point Relative Position" type="1">
      <description>Distance between current Control Point Position and the distal-most possible Source position in current Channel (mm). See C.8.8.15.9.</description>
      <section ref="C.8.8.15.9" name="">Control Point Relative Position (300A,02D2) shall describe where a given source in a channel is located with respect to the end of the channel. This position shall correspond to the end of the afterloader applicator, not the “safe position”.
</section>
    </entry>
    <entry group="300A" element="02D4" name="&gt;&gt;&gt;Control Point 3D Position" type="3">
      <description>Coordinates (x, y, z) of Control Point in the patient based coordinate system described in C.7.6.2.1.1 (mm). See C.8.8.15.10.</description>
      <section ref="C.8.8.15.10" name="">Control Point 3D Position (300A,02D4) shall describe the absolute 3D coordinates of a source. This position shall correspond to the center of a source in an applicator during a remote or manually controlled afterloading treatment.
</section>
    </entry>
    <entry group="300A" element="0412" name="&gt;&gt;&gt;Control Point Orientation" type="3">
      <description>(x,y,z) component of the direction vector of the brachy source or seed at the Control Point 3D Position (300A,02D4). See C.8.8.15.14.</description>
      <section ref="C.8.8.15.14" name="">The Control Point Orientation (300A,0412) shall be used to define the orientation of an anisotropic brachytherapy source or seed for the purpose of calculating the effect of the anisotropy on the dose calculation. The Control Point Orientation (300A,0412) shall be given by the direction vector of the long axis of the Brachy source or seed in the insertion direction, in the DICOM Patient Coordinate System. The direction vector shall be oriented from the source center as defined by the Control Point 3D Position (300A,02D4) along the long axis of the source and in the insertion direction.
</section>
    </entry>
    <entry group="300C" element="0055" name="&gt;&gt;&gt;Brachy Referenced Dose Reference Sequence" type="3">
      <description>Introduces a sequence of Dose References for current Channel. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;&gt;&gt;&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely identifies Dose Reference described in Dose Reference Sequence. (300A,0010) within RT Prescription Module of current RT Plan. Required if Brachy Referenced Dose Reference Sequence (300C,0055) is sent.</description>
    </entry>
    <entry group="300A" element="010C" name="&gt;&gt;&gt;&gt;Cumulative Dose Reference Coefficient" type="1C">
      <description>Coefficient used to calculate cumulative dose contribution from this Source to the referenced Dose Reference at the current Control Point. Required if Brachy Referenced Dose Reference Sequence (300C,0055) is sent. See C.8.8.15.11.</description>
      <section ref="C.8.8.15.11" name="">The Cumulative Dose Reference Coefficient (300A,010C) is the value by which Brachy Application Setup Dose (300A,00A4) is multiplied to obtain the dose to the referenced dose reference site at the current control point (and after previous control points have been successfully administered). The Cumulative Dose Reference Coefficient (300A,010C) is by definition zero for the initial control point. The Cumulative Dose Reference Coefficient (300A,010C) of the final control point multiplied by Brachy Application Setup Dose (300A,00A4) results in the final dose to the referenced dose reference site for the current channel. Dose calculation for dose reference sites other than points is not well defined.
If Treatment Type (300A,0202) is PDR, then the Cumulative Dose Reference Coefficient (3008,010C) shall specify the dose delivered to the dose reference during a single pulse. The total dose delivered to the dose reference shall then be expressed by Cumulative Dose Reference Coefficient (3008,010C) multiplied by Number of Pulses (300A,028A) multiplied by Brachy Application Setup Dose (300A,00A4).
</section>
    </entry>
  </module>
  <module ref="C.8.8.16" table="C.8-52" name="Approval Module Attributes">
    <entry group="300E" element="0002" name="Approval Status" type="1">
      <description>Approval status at the time the SOP Instance was created.
Enumerated Values:
APPROVED = Reviewer recorded that object met an implied criterion
UNAPPROVED = No review of object has been recorded
REJECTED = Reviewer recorded that object failed to meet an implied criterion</description>
    </entry>
    <entry group="300E" element="0004" name="Review Date" type="2C">
      <description>Date on which object was reviewed. Required if Approval Status (300E,0002) is APPROVED or REJECTED.</description>
    </entry>
    <entry group="300E" element="0005" name="Review Time" type="2C">
      <description>Time at which object was reviewed. Required if Approval Status (300E,0002) is APPROVED or REJECTED.</description>
    </entry>
    <entry group="300E" element="0008" name="Reviewer Name" type="2C">
      <description>Name of person who reviewed object. Required if Approval Status (300E,0002) is APPROVED or REJECTED.</description>
    </entry>
  </module>
  <module ref="C.8.8.17" table="C.8-53" name="RT General Treatment Record Module Attributes">
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description>Instance number identifying this particular instance of the object.</description>
    </entry>
    <entry group="3008" element="0250" name="Treatment Date" type="2">
      <description>Date when current fraction was delivered, or Date last fraction was delivered in case of RT Treatment Summary Record IOD. See Note.</description>
    </entry>
    <entry group="3008" element="0251" name="Treatment Time" type="2">
      <description>Time when current fraction was delivered (begun), or Time last fraction was delivered (begun) in case of RT Treatment Summary Record IOD. See Note.</description>
    </entry>
    <entry group="300C" element="0002" name="Referenced RT Plan Sequence" type="2">
      <description>A sequence which provides reference to a RT Plan SOP Class/Instance pair. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="3008" element="0030" name="Referenced Treatment Record Sequence" type="3">
      <description>A sequence which provides reference to RT Treatment Record SOP Class/Instance pairs to which the current RT Treatment Record is significantly related. The sequence may contain one or more items.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.8.8.18" table="C.8-54" name="RT Treatment Machine Record Module Attributes">
    <entry group="300A" element="0206" name="Treatment Machine Sequence" type="1">
      <description>Introduces sequence describing treatment machine used for treatment delivery. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <entry group="300A" element="00B2" name="&gt;Treatment Machine Name" type="2">
      <description>User-defined name identifying treatment machine used for treatment delivery.</description>
    </entry>
    <entry group="0008" element="0070" name="&gt;Manufacturer" type="2">
      <description>Manufacturer of the equipment used for treatment delivery.</description>
    </entry>
    <entry group="0008" element="0080" name="&gt;Institution Name" type="2">
      <description>Institution where the equipment is located that was used for treatment delivery.</description>
    </entry>
    <entry group="0008" element="0081" name="&gt;Institution Address" type="3">
      <description>Mailing address of the institution where the equipment is located that was used for treatment delivery.</description>
    </entry>
    <entry group="0008" element="1040" name="&gt;Institutional Department Name" type="3">
      <description>Department in the institution where the equipment is located that was used for treatment delivery.</description>
    </entry>
    <entry group="0008" element="1090" name="&gt;Manufacturer's Model Name" type="2">
      <description>Manufacturer's model name of the equipment used for treatment delivery.</description>
    </entry>
    <entry group="0018" element="1000" name="&gt;Device Serial Number" type="2">
      <description>Manufacturer's serial number of the equipment used for treatment delivery.</description>
    </entry>
  </module>
  <module ref="C.8.8.19" table="C.8-55" name="Measured Dose Reference Record Module Attributes">
    <entry group="3008" element="0010" name="Measured Dose Reference Sequence" type="1">
      <description>Introduces sequence of doses measured during treatment delivery, summed over entire session. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Plan. Required only if Measured Dose Reference Number (3008,0064) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0064" name="&gt;Measured Dose Reference Number" type="1C">
      <description>Unique identifier of measured dose point. Required only if Referenced Dose Reference Number (300C,0051) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3004" element="0002" name="&gt;Dose Units" type="1">
      <description>Units used to describe measured dose.
Enumerated Values:
GY = Gray
RELATIVE = Dose relative to implicit reference value</description>
    </entry>
    <entry group="3008" element="0016" name="&gt;Measured Dose Value" type="2">
      <description>Measured Dose in units specified by Dose Units (3004,0002).</description>
    </entry>
    <entry group="3008" element="0014" name="&gt;Measured Dose Type" type="2">
      <description>Type of dose measurement.
Defined Terms:
DIODE = semiconductor diode
TLD = thermoluminescent dosimeter
ION_CHAMBER = ion chamber
GEL = dose sensitive gel
EPID = electronic portal imaging device
FILM = dose sensitive film</description>
    </entry>
    <entry group="3008" element="0012" name="&gt;Measured Dose Description" type="3">
      <description>User-defined description of Dose Reference (e.g. "Exit dose", "Point A").</description>
    </entry>
  </module>
  <module ref="C.8.8.20" table="C.8-56" name="Calculated Dose Reference Record Module Attributes">
    <entry group="3008" element="0070" name="Calculated Dose Reference Sequence" type="1">
      <description>Introduces sequence of doses estimated for each treatment delivery. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Plan. Required only if Calculated Dose Reference Number (3008,0072) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0072" name="&gt;Calculated Dose Reference Number" type="1C">
      <description>Unique identifier of dose reference point within RT Treatment Record IOD. Required only if Referenced Dose Reference Number (300C,0051) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0076" name="&gt;Calculated Dose Reference Dose Value" type="2">
      <description>Calculated Dose (Gy).</description>
    </entry>
    <entry group="3008" element="0074" name="&gt;Calculated Dose Reference Description" type="3">
      <description>User-defined description of Calculated Dose Reference.</description>
    </entry>
  </module>
  <module ref="C.8.8.21" table="C.8-57" name="RT Beams Session Record Module Attributes">
    <entry group="0008" element="1070" name="Operators' Name" type="2">
      <description>Name of operator administering treatment session.</description>
    </entry>
    <entry group="300C" element="0022" name="Referenced Fraction Group Number" type="3">
      <description>Identifier of Fraction Group within referenced RT Plan.</description>
    </entry>
    <entry group="300A" element="0078" name="Number of Fractions Planned" type="2">
      <description>Total number of treatments (Fractions) planned for current Fraction Group.</description>
    </entry>
    <entry group="300A" element="00B3" name="Primary Dosimeter Unit" type="1">
      <description>Measurement unit of machine dosimeter.
Enumerated Values:
MU = Monitor Unit
MINUTE = minute</description>
    </entry>
    <entry group="3008" element="0020" name="Treatment Session Beam Sequence" type="1">
      <description>Introduces sequence of Beams administered during treatment session. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0006" name="&gt;Referenced Beam Number" type="3">
      <description>References Beam specified by Beam Number (300A,00C0) in Beam Sequence (300A,00B0) in RT Beams Module within referenced RT Plan.</description>
    </entry>
    <entry group="300A" element="00C2" name="&gt;Beam Name" type="3">
      <description>User-defined name for delivered Beam.</description>
    </entry>
    <entry group="300A" element="00C3" name="&gt;Beam Description" type="3">
      <description>User-defined description for delivered Beam.</description>
    </entry>
    <entry group="300A" element="00C4" name="&gt;Beam Type" type="1">
      <description>Motion characteristic of delivered Beam. Enumerated Values:
STATIC = all beam parameters remain unchanged during delivery
DYNAMIC = one or more beam parameters changes during delivery</description>
    </entry>
    <entry group="300A" element="00C6" name="&gt;Radiation Type" type="1">
      <description>Particle type of delivered Beam.
Defined Terms:
PHOTON, ELECTRON, NEUTRON, PROTON.</description>
    </entry>
    <entry group="300A" element="00C7" name="&gt;High-Dose Technique Type" type="1C">
      <description>Type of high-dose treatment technique.
Defined Terms:
NORMAL = Standard treatment
TBI = Total Body Irradiation
HDR = High Dose Rate
Required if treatment technique requires a dose that would normally require overriding of treatment machine safety controls.</description>
    </entry>
    <entry group="300C" element="0040" name="&gt;Referenced Verification Image Sequence" type="3">
      <description>Introduces sequence of verification images obtained during delivery of current beam. The sequence may contain one or more items.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="3008" element="0078" name="&gt;&gt;Start Meterset" type="3">
      <description>Cumulative Meterset Weight within Beam referenced by Referenced Beam Number at which image acquisition starts.</description>
    </entry>
    <entry group="3008" element="007A" name="&gt;&gt;End Meterset" type="3">
      <description>Cumulative Meterset Weight within Beam referenced by Referenced Beam Number at which image acquisition ends.</description>
    </entry>
    <entry group="3008" element="0080" name="&gt;Referenced Measured Dose Reference Sequence" type="3">
      <description>Introduces sequence of doses measured during treatment delivery for current Beam. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely references Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Plan. Required if Referenced Measured Dose Reference Sequence (3008,0080) is sent and Referenced Measured Dose Reference Number (3008,0082) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0082" name="&gt;&gt;Referenced Measured Dose Reference Number" type="1C">
      <description>Uniquely references Measured Dose Reference specified by Measured Dose Reference Number (3008,0064) in Measured Dose Reference Sequence (3008,0010). Required if Referenced Measured Dose Reference Sequence (3008,0080) is sent and Referenced Dose Reference Number (300C,0051) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0016" name="&gt;&gt;Measured Dose Value" type="1C">
      <description>Measured Dose in units specified by Dose Units (3004,0002) in sequence referenced by Measured Dose Reference Sequence (3008,0010) or Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Plan as defined above. Required if Referenced Measured Dose Reference Sequence (3008,0080) is sent.</description>
    </entry>
    <entry group="3008" element="0090" name="&gt;Referenced Calculated Dose Reference Sequence" type="3">
      <description>Introduces sequence of doses estimated for each treatment delivery. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Plan. Required if Referenced Calculated Dose Reference Sequence (3008,0090) is sent and Referenced Calculated Dose Reference Number (3008,0092) is not sent.</description>
    </entry>
    <entry group="3008" element="0092" name="&gt;&gt;Referenced Calculated Dose Reference Number" type="1C">
      <description>Uniquely identifies Calculated Dose Reference specified by Calculated Dose Reference Number (3008,0072) within Calculated Dose Reference Sequence (3008,0070). Required if Referenced Calculated Dose Reference Sequence (3008,0090) is sent and Referenced Dose Reference Number (300C,0051) is not sent.</description>
    </entry>
    <entry group="3008" element="0076" name="&gt;&gt;Calculated Dose Reference Dose Value" type="1C">
      <description>Calculated Dose (Gy). Required if Referenced Calculated Dose Reference Sequence (3008,0090) is sent.</description>
    </entry>
    <entry group="300A" element="00B4" name="&gt;Source-Axis Distance" type="3">
      <description>Radiation source to gantry rotation axis distance of the equipment that was used for beam delivery (mm).</description>
    </entry>
    <entry group="3008" element="00A0" name="&gt;Beam Limiting Device Leaf Pairs Sequence" type="1">
      <description>Introduces sequence of beam limiting device (collimator) jaw or leaf (element) leaf pair values. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300A" element="00B8" name="&gt;&gt;RT Beam Limiting Device Type" type="1">
      <description>Type of beam limiting device (collimator).
Enumerated Values:
X = symmetric jaw pair in IEC X direction
Y = symmetric jaw pair in IEC Y direction
ASYMX = asymmetric jaw pair in IEC X direction
ASYMY = asymmetric pair in IEC Y direction
MLCX = multileaf (multi-element) jaw pair in IEC X direction
MLCY = multileaf (multi-element) jaw pair in IEC Y direction
</description>
    </entry>
    <entry group="300A" element="00BC" name="&gt;&gt;Number of Leaf/Jaw Pairs" type="1">
      <description>Number of leaf (element) or jaw pairs (equal to 1 for standard beam limiting device jaws).</description>
    </entry>
    <entry group="300C" element="006A" name="&gt;Referenced Patient Setup Number" type="3">
      <description>Uniquely identifies Patient Setup used within current beam, specified by Patient Setup Number (300A,0182) within Patient Setup Sequence (300A,0180) of RT Treatment Record.</description>
    </entry>
    <entry group="300A" element="00D0" name="&gt;Number of Wedges" type="1">
      <description>Number of wedges associated with current delivered Beam.</description>
    </entry>
    <entry group="3008" element="00B0" name="&gt;Recorded Wedge Sequence" type="1C">
      <description>Introduces sequence of treatment wedges present during delivered Beam. Required if Number of Wedges (300A,00D0) is non-zero. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300A" element="00D2" name="&gt;&gt;Wedge Number" type="3">
      <description>Identification number of the Wedge. The value of Wedge Number (300A,00D2) shall be unique within the wedge sequence.</description>
    </entry>
    <entry group="300A" element="00D3" name="&gt;&gt;Wedge Type" type="2C">
      <description>Type of wedge defined for delivered Beam. Required if Recorded Wedge Sequence (3008,00B0) is sent.
Defined Terms:
STANDARD = standard (static) wedge
DYNAMIC = moving Beam Limiting Device (collimator) jaw simulating wedge
MOTORIZED = single wedge which can be removed from beam remotely</description>
    </entry>
    <entry group="300A" element="00D4" name="&gt;&gt;Wedge ID" type="3">
      <description>User-supplied identifier for wedge.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An identifier for the accessory intended to be read by a device such as a bar-code reader.</description>
    </entry>
    <entry group="300A" element="00D5" name="&gt;&gt;Wedge Angle" type="3">
      <description>Nominal wedge angle delivered (degrees).</description>
    </entry>
    <entry group="300A" element="00D8" name="&gt;&gt;Wedge Orientation" type="3">
      <description>Orientation of wedge, i.e. orientation of IEC WEDGE FILTER coordinate system with respect to IEC BEAM LIMITING DEVICE coordinate system (degrees).</description>
    </entry>
    <entry group="300A" element="00E0" name="&gt;Number of Compensators" type="2">
      <description>Number of compensators associated with current delivered Beam.</description>
    </entry>
    <entry group="3008" element="00C0" name="&gt;Recorded Compensator Sequence" type="3">
      <description>Introduces sequence of treatment compensators associated with current Beam. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="00D0" name="&gt;&gt;Referenced Compensator Number" type="1C">
      <description>Uniquely identifies compensator specified by Compensator Number (300A,00E4) within Beam referenced by Referenced Beam Number (300C,0006). Required if Recorded Compensator Sequence (3008,00C0) is sent.</description>
    </entry>
    <entry group="300A" element="00EE" name="&gt;&gt;Compensator Type" type="2C">
      <description>Type of compensator (if any). Required if Recorded Compensator Sequence (3008,00C0) is sent.
Defined Terms:
STANDARD = physical (static) compensator
DYNAMIC = moving Beam Limiting Device (collimator) simulating compensator</description>
    </entry>
    <entry group="300A" element="00E5" name="&gt;&gt;Compensator ID" type="3">
      <description>User-supplied identifier for compensator.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An identifier for the accessory intended to be read by a device such as a bar-code reader.</description>
    </entry>
    <entry group="300A" element="00ED" name="&gt;Number of Boli" type="2">
      <description>Number of boli used with current Beam.</description>
    </entry>
    <entry group="300C" element="00B0" name="&gt;Referenced Bolus Sequence" type="3">
      <description>Introduces sequence of boli associated with Beam. The sequence may contain one or more items.</description>
    </entry>
    <entry group="3006" element="0084" name="&gt;&gt;Referenced ROI Number" type="1C">
      <description>Uniquely identifies ROI representing the bolus specified by ROI Number (3006,0022) in Structure Set ROI Sequence (3006,0020) in Structure Set Module within RT Structure Set IOD referenced by referenced RT Plan in Referenced RT Plan Sequence (300C,0002) in RT General Treatment Record Module. Required if Referenced Bolus Sequence (300C,00B0) is sent.</description>
    </entry>
    <entry group="300A" element="00DC" name="&gt;&gt;Bolus ID" type="3">
      <description>User-supplied identifier for the Bolus.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An identifier for the accessory intended to be read by a device such as a bar-code reader.</description>
    </entry>
    <entry group="300A" element="00F0" name="&gt;Number of Blocks" type="2">
      <description>Number of shielding blocks or Electron Inserts associated with Beam.</description>
    </entry>
    <entry group="3008" element="00D0" name="&gt;Recorded Block Sequence" type="3">
      <description>Introduces sequence of blocks associated with current Beam. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300A" element="00F5" name="&gt;&gt;Block Tray ID" type="3">
      <description>User-supplied identifier for block tray or Electron Insert.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An identifier for the accessory intended to be read by a device such as a bar-code reader.</description>
    </entry>
    <entry group="300C" element="00E0" name="&gt;&gt;Referenced Block Number" type="3">
      <description>Uniquely identifies block specified by Block Number (300A,00FC) within Beam referenced by Referenced Beam Number (300C,0006).</description>
    </entry>
    <entry group="300A" element="00FE" name="&gt;&gt;Block Name" type="2C">
      <description>User-defined name for block. Required if Recorded Block Sequence (3008,00D0) is sent.</description>
    </entry>
    <entry group="300A" element="0107" name="&gt;Applicator Sequence" type="3">
      <description>Introduces sequence of Applicators associated with Beam. Only a single item shall be permitted in this sequence.</description>
    </entry>
    <entry group="300A" element="0108" name="&gt;&gt;Applicator ID" type="1C">
      <description>User or machine supplied identifier for Applicator. Required if Applicator Sequence (300A,0107) is sent.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An identifier for the accessory intended to be read by a device such as a bar-code reader.</description>
    </entry>
    <entry group="300A" element="0109" name="&gt;&gt;Applicator Type" type="1C">
      <description>Type of Applicator. Required if Applicator Sequence (300A,0107) is sent.
Defined Terms:
ELECTRON_SQUARE = square electron applicator
ELECTRON_RECT = rectangular electron applicator
ELECTRON_CIRC = circular electron applicator
ELECTRON_SHORT = short electron applicator
ELECTRON_OPEN = open (dummy) electron applicator
INTRAOPERATIVE = intraoperative (custom) applicator
STEREOTACTIC = stereotactic applicator</description>
    </entry>
    <entry group="300A" element="010A" name="&gt;&gt;Applicator Description" type="3">
      <description>User-defined description for Applicator.</description>
    </entry>
    <entry group="300A" element="0420" name="&gt;General Accessory Sequence" type="3">
      <description>Introduces a Sequence of General Accessories associated with this Beam. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="0424" name="&gt;&gt;General Accessory Number" type="1">
      <description>Identification Number of the General Accessory. The value shall be unique within the sequence.</description>
    </entry>
    <entry group="300A" element="0421" name="&gt;&gt;General Accessory ID" type="1">
      <description>User or machine supplied identifier for General Accessory.</description>
    </entry>
    <entry group="300A" element="0422" name="&gt;&gt;General Accessory Description" type="3">
      <description>User supplied description of General Accessory.</description>
    </entry>
    <entry group="300A" element="0423" name="&gt;&gt;General Accessory Type" type="3">
      <description>Specifies the type of accessory.
Defined Terms:
GRATICULE = Accessory tray with a radio-opaque grid
IMAGE_DETECTOR = Image acquisition device positioned in the beam line
RETICLE = Accessory tray with radio-transparent markers or grid</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>Machine-readable identifier for this accessory</description>
    </entry>
    <entry group="3008" element="0022" name="&gt;Current Fraction Number" type="2">
      <description>Fraction number for this beam administration.</description>
    </entry>
    <entry group="300A" element="00CE" name="&gt;Treatment Delivery Type" type="2">
      <description>Delivery Type of treatment.
Defined Terms:
TREATMENT = normal patient treatment
OPEN_PORTFILM = portal image acquisition with open field
TRMT_PORTFILM = portal image acquisition with treatment port
CONTINUATION = continuation of interrupted treatment
SETUP = no treatment beam is applied for this RT Beam. To be used for specifying the gantry, couch, and other machine positions where X-Ray set-up images or measurements are to be taken</description>
    </entry>
    <entry group="3008" element="002A" name="&gt;Treatment Termination Status" type="1">
      <description>Conditions under which treatment was terminated.
Enumerated Values:
NORMAL = treatment terminated normally
OPERATOR = operator terminated treatment
MACHINE = machine terminated treatment
UNKNOWN = status at termination unknown</description>
    </entry>
    <entry group="3008" element="002B" name="&gt;Treatment Termination Code" type="3">
      <description>Treatment machine termination code. This code is dependent upon the particular application and equipment.</description>
    </entry>
    <entry group="3008" element="002C" name="&gt;Treatment Verification Status" type="2">
      <description>Conditions under which treatment was verified by a verification system.
Enumerated Values:
VERIFIED = treatment verified
VERIFIED_OVR = treatment verified with at least one out-of-range value overridden
NOT_VERIFIED = treatment verified manually</description>
    </entry>
    <entry group="3008" element="0032" name="&gt;Specified Primary Meterset" type="3">
      <description>Desired machine setting of primary meterset.</description>
    </entry>
    <entry group="3008" element="0033" name="&gt;Specified Secondary Meterset" type="3">
      <description>Desired machine setting of secondary meterset.</description>
    </entry>
    <entry group="3008" element="0036" name="&gt;Delivered Primary Meterset" type="3">
      <description>Machine setting actually delivered as recorded by primary meterset.</description>
    </entry>
    <entry group="3008" element="0037" name="&gt;Delivered Secondary Meterset" type="3">
      <description>Machine setting actually delivered as recorded by secondary meterset.</description>
    </entry>
    <entry group="3008" element="003A" name="&gt;Specified Treatment Time" type="3">
      <description>Treatment Time set (sec).</description>
    </entry>
    <entry group="3008" element="003B" name="&gt;Delivered Treatment Time" type="3">
      <description>Treatment Time actually delivered (sec).</description>
    </entry>
    <entry group="300A" element="0110" name="&gt;Number of Control Points" type="1">
      <description>Number of control points delivered.</description>
    </entry>
    <entry group="3008" element="0040" name="&gt;Control Point Delivery Sequence" type="1">
      <description>Introduces sequence of beam control points for current treatment beam. The sequence may contain one or more items. See C.8.8.21.1.</description>
      <section ref="C.8.8.21.1" name="">All treatment machine delivery parameters (including table angles and positions) in the RT Treatment Session Record Module shall be specified as absolute, not relative, values at the Control Point.
</section>
    </entry>
    <entry group="300C" element="00F0" name="&gt;&gt;Referenced Control Point Index" type="3">
      <description>Uniquely identifies Control Point specified by Control Point Index (300A,0112) within Beam referenced by Referenced Beam Number (300C,0006).</description>
    </entry>
    <entry group="3008" element="0024" name="&gt;&gt;Treatment Control Point Date" type="1">
      <description>Date administration of treatment beam began.</description>
    </entry>
    <entry group="3008" element="0025" name="&gt;&gt;Treatment Control Point Time" type="1">
      <description>Time administration of treatment beam began.</description>
    </entry>
    <entry group="3008" element="0042" name="&gt;&gt;Specified Meterset" type="2">
      <description>Desired machine setting for current control point. See C.8.8.21.2.</description>
      <section ref="C.8.8.21.2" name="">Specified Meterset (3008,0042) contains the MU as specified in the corresponding RT Plan at a given control point.
Delivered Meterset (3008,0044) shall contain one of the following three values:
</section>
    </entry>
    <entry group="3008" element="0044" name="&gt;&gt;Delivered Meterset" type="1">
      <description>Machine setting actually delivered at current control point. See C.8.8.21.2.</description>
      <section ref="C.8.8.21.2" name="">Specified Meterset (3008,0042) contains the MU as specified in the corresponding RT Plan at a given control point.
Delivered Meterset (3008,0044) shall contain one of the following three values:
</section>
    </entry>
    <entry group="300A" element="0115" name="&gt;&gt;Dose Rate Set" type="2">
      <description>Dose Rate set on treatment machine for segment beginning at current control point (meterset/min).</description>
    </entry>
    <entry group="3008" element="0048" name="&gt;&gt;Dose Rate Delivered" type="2">
      <description>Dose Rate actually delivered for segment beginning at current control point (meterset/min).</description>
    </entry>
    <entry group="300A" element="0114" name="&gt;&gt;Nominal Beam Energy" type="3">
      <description>Nominal Beam Energy at control point.</description>
    </entry>
    <entry group="300A" element="0015" name="&gt;&gt;Nominal Beam Energy Unit" type="1C">
      <description>Units used for Nominal Beam Energy (300A,0114). Required if Nominal Beam Energy (300A,0114) is sent.
Defined Terms:
MV = Megavolt
MEV = Mega electron-Volt
If Radiation Type (300A,00C6) is PHOTON, Nominal Beam Energy Unit (300A,0015) shall be MV. If Radiation Type (300A,00C6) is ELECTRON, Nominal Beam Energy Unit (300A,0015) shall be MEV.</description>
    </entry>
    <entry group="300A" element="0116" name="&gt;&gt;Wedge Position Sequence" type="3">
      <description>Introduces sequence of Wedge positions for current control point. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="00C0" name="&gt;&gt;&gt;Referenced Wedge Number" type="1C">
      <description>Uniquely identifies wedge specified by Wedge Number (300A,00D2) within Beam referenced by Referenced Beam Number (300C,0006). Required if Wedge Position Sequence (300A,0116) is sent.</description>
    </entry>
    <entry group="300A" element="0118" name="&gt;&gt;&gt;Wedge Position" type="1C">
      <description>Position of Wedge at current control point. Required if Wedge Position Sequence (300A,0116) is sent.
Enumerated Values: IN, OUT.</description>
    </entry>
    <entry group="300A" element="011A" name="&gt;&gt;Beam Limiting Device Position Sequence" type="1C">
      <description>Introduces sequence of beam limiting device (collimator) jaw or leaf (element) positions. Required for Control Point 0 of Control Point Delivery Sequence (3008,0040) or if beam limiting device (collimator) changes during beam administration. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300A" element="00B8" name="&gt;&gt;&gt;RT Beam Limiting Device Type" type="1C">
      <description>Type of beam limiting device. The value of this attribute shall correspond to RT Beam Limiting Device Type (300A,00B8) defined in an element of Beam Limiting Device Leaf Pairs Sequence (3008,00A0). Required if Beam Limiting Device Position Sequence (300A,011A) is sent.
Enumerated Values:
X = symmetric jaw pair in IEC X direction
Y = symmetric jaw pair in IEC Y direction
ASYMX = asymmetric jaw pair in IEC X direction
ASYMY = asymmetric pair in IEC Y direction
MLCX = multileaf (multi-element) jaw pair in IEC X direction
MLCY = multileaf (multi-element) jaw pair in IEC Y direction</description>
    </entry>
    <entry group="300A" element="011C" name="&gt;&gt;&gt;Leaf/Jaw Positions" type="1C">
      <description>Positions of beam limiting device (collimator) leaf (element) or jaw pairs (mm) in IEC BEAM LIMITING DEVICE coordinate axis appropriate to RT Beam Limiting Device Type (300A,00B8), e.g. X-axis for MLCX, Y-axis for MLCY. Contains 2N values, where N is the Number of Leaf/Jaw Pairs (300A,00BC) defined in element of Beam Limiting Device Leaf Pairs Sequence (3008,00A0). Values shall be in IEC leaf subscript order 101, 102, … 1N, 201, 202 … 2N. Required if Beam Limiting Device Position Sequence (300A,011A) is sent.</description>
    </entry>
    <entry group="300A" element="011E" name="&gt;&gt;Gantry Angle" type="1C">
      <description>Treatment machine gantry angle, i.e. orientation of IEC GANTRY coordinate system with respect to IEC FIXED REFERENCE coordinate system (degrees). Required for Control Point 0 of Control Point Delivery Sequence (3008,0040) or if Gantry Angle changes during beam administration.</description>
    </entry>
    <entry group="300A" element="011F" name="&gt;&gt;Gantry Rotation Direction" type="1C">
      <description>Direction of Gantry Rotation when viewing gantry from isocenter, for segment beginning at current Control Point. Required for Control Point 0 of Control Point Delivery Sequence (3008,0040), or if Gantry Rotation Direction changes during beam administration.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
    </entry>
    <entry group="300A" element="014A" name="&gt;&gt;Gantry Pitch Angle" type="3">
      <description>Gantry Pitch Angle. i.e. the rotation of the IEC GANTRY coordinate system about the X-axis of the IEC GANTRY coordinate system (degrees). If used, must be present for first item of Control Point Sequence, or if used and Gantry Pitch Rotation Angle changes during Beam, must be present. See C.8.8.25.6.5.</description>
      <section ref="C.8.8.25.6.5" name="">The Gantry Pitch angle is not defined in IEC 61217. This angle is defined in the DICOM standard in a way compatible with the current notion of IEC by introducing it as rotation of the IEC GANTRY System as indicated below.
The Gantry Pitch Angle is defined as the rotation of the coordinate axes Yg, Zg about axis Xg by an angle g; see Figure C.8.8.25-7. An increase in the value of angle g corresponds to the clockwise rotation as viewed from the isocenter along the positive Xg axis


Figure C.8.8.25-7 Gantry Pitch Angle
</section>
    </entry>
    <entry group="300A" element="014C" name="&gt;&gt;Gantry Pitch Rotation Direction" type="3">
      <description>Direction of Gantry Pitch Angle when viewing along the positive X-axis of the IEC GANTRY coordinate system, for segment following Control Point. If used, must be present for first item of Control Point Sequence, or if used and Gantry Pitch Rotation Direction changes during Beam, must be present. See C.8.8.14.8 and C.8.8.25.6.5.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="3008" element="0230" name="&gt;&gt;Beam Stopper Position" type="3">
      <description>Position of Beam Stopper during beam administration.
Enumerated Values:
EXTENDED = Beam Stopper extended
RETRACTED = Beam Stopper retracted
UNKNOWN = Position unknown</description>
    </entry>
    <entry group="300A" element="0120" name="&gt;&gt;Beam Limiting Device Angle" type="1C">
      <description>Beam Limiting Device (collimator) angle, i.e. orientation of IEC BEAM LIMITING DEVICE coordinate system with respect to IEC GANTRY coordinate system (degrees). Required for Control Point 0 of Control Point Delivery Sequence (3008,0040) or if beam limiting device (collimator) angle changes during beam delivery.</description>
    </entry>
    <entry group="300A" element="0121" name="&gt;&gt;Beam Limiting Device Rotation Direction" type="1C">
      <description>Direction of Beam Limiting Device Rotation when viewing beam limiting device (collimator) from radiation source, for segment beginning at current Control Point. Required for Control Point 0 of Control Point Delivery Sequence (3008,0040) or if Beam Limiting Device Rotation Direction changes during beam administration.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
    </entry>
    <entry group="300A" element="0122" name="&gt;&gt;Patient Support Angle" type="1C">
      <description>Patient Support angle, i.e. orientation of IEC PATIENT SUPPORT (turntable) coordinate system with respect to IEC FIXED REFERENCE coordinate system (degrees). Required for Control Point 0 of Control Point Delivery Sequence (3008,0040) or if Patient Support Angle changes during beam administration.</description>
    </entry>
    <entry group="300A" element="0123" name="&gt;&gt;Patient Support Rotation Direction" type="1C">
      <description>Direction of Patient Support Rotation when viewing table from above, for segment beginning at current Control Point. Required for Control Point 0 of Control Point Delivery Sequence (3008,0040), or if Patient Support Rotation Direction changes during beam administration.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
    </entry>
    <entry group="300A" element="0124" name="&gt;&gt;Table Top Eccentric Axis Distance" type="3">
      <description>Distance (positive) from the IEC PATIENT SUPPORT vertical axis to the IEC TABLE TOP ECCENTRIC vertical axis (mm).</description>
    </entry>
    <entry group="300A" element="0125" name="&gt;&gt;Table Top Eccentric Angle" type="1C">
      <description>Table Top (non-isocentric) angle, i.e. orientation of IEC TABLE TOP ECCENTRIC coordinate system with respect to IEC PATIENT SUPPORT coordinate system (degrees). Required for Control Point 0 of Control Point Delivery Sequence (3008,0040) or if Table Top Eccentric Angle changes during beam administration.</description>
    </entry>
    <entry group="300A" element="0126" name="&gt;&gt;Table Top Eccentric Rotation Direction" type="1C">
      <description>Direction of Table Top Eccentric Rotation when viewing table from above, for segment beginning at current Control Point. Required for Control Point 0 of Control Point Delivery Sequence (3008,0040) or if Table Top Eccentric Rotation Direction changes during beam administration.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
    </entry>
    <entry group="300A" element="0140" name="&gt;&gt;Table Top Pitch Angle" type="1C">
      <description>Table Top Pitch Angle, i.e. the rotation of the IEC TABLE TOP coordinate system about the X-axis of the IEC TABLE TOP coordinate system (degrees). If required by treatment delivery device, shall be present for first item of Control Point Sequence. If required by treatment delivery device and if Table Top Pitch Angle changes during Beam, shall be present in all subsequent items of Control Point Sequence. See C.8.8.25.6.2.</description>
      <section ref="C.8.8.25.6.2" name="">Pitch and Roll Coordinate Systems of the Table Top are not defined in IEC 61217. These angles are defined in the DICOM standard in a way compatible with the current notion of IEC by introducing them as rotations of the IEC Table Top System as indicated below.
The Table Top Pitch Angle is defined as the rotation of the coordinate axes Yt, Zt about axis Xt by an angle t; see Figure C.8.8.25-3. An increase in the value of angle t corresponds to the clockwise rotation of the Table Top as viewed from the Table Top coordinate system origin along the positive Xt axis.
The Table Top Roll Angle is defined as the rotation of the coordinate axes Xt, Zt about axis Yt by an angle t; see Figure C.8.8.25-4. An increase in the value of angle t corresponds to the clockwise rotation of the Table Top as viewed from the Table Top coordinate system origin along the positive Yt axis.


Figure C.8.8.25-3 Table Top Pitch Angle

Figure C.8.8.25-4 Table Top Roll Angle

</section>
    </entry>
    <entry group="300A" element="0142" name="&gt;&gt; Table Top Pitch Rotation Direction" type="1C">
      <description>Direction of Table Top Pitch Rotation when viewing the table along the positive X-axis of the IEC TABLE TOP coordinate system, for segment following Control Point. If required by treatment delivery device, shall be present for first item of Control Point Sequence. If required by treatment delivery device and if Table Top Pitch Rotation Direction changes during Beam, shall be present in all subsequent items of Control Point Sequence. See C.8.8.14.8 and C.8.8.25.6.2.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0144" name="&gt;&gt;Table Top Roll Angle" type="1C">
      <description>Table Top Roll Angle, i.e. the rotation of the IEC TABLE TOP coordinate system about the IEC Y-axis of the IEC TABLE TOP coordinate system (degrees). If required by treatment delivery device, shall be present for first item of Control Point Sequence. If required by treatment delivery device and if Table Top Roll Angle changes during Beam, shall be present in all subsequent items of Control Point Sequence. See C.8.8.25.6.2.</description>
      <section ref="C.8.8.25.6.2" name="">Pitch and Roll Coordinate Systems of the Table Top are not defined in IEC 61217. These angles are defined in the DICOM standard in a way compatible with the current notion of IEC by introducing them as rotations of the IEC Table Top System as indicated below.
The Table Top Pitch Angle is defined as the rotation of the coordinate axes Yt, Zt about axis Xt by an angle t; see Figure C.8.8.25-3. An increase in the value of angle t corresponds to the clockwise rotation of the Table Top as viewed from the Table Top coordinate system origin along the positive Xt axis.
The Table Top Roll Angle is defined as the rotation of the coordinate axes Xt, Zt about axis Yt by an angle t; see Figure C.8.8.25-4. An increase in the value of angle t corresponds to the clockwise rotation of the Table Top as viewed from the Table Top coordinate system origin along the positive Yt axis.


Figure C.8.8.25-3 Table Top Pitch Angle

Figure C.8.8.25-4 Table Top Roll Angle

</section>
    </entry>
    <entry group="300A" element="0146" name="&gt;&gt; Table Top Roll Rotation Direction" type="1C">
      <description>Direction of Table Top Roll Rotation when viewing the table along the positive Y-axis of the IEC TABLE TOP coordinate system, for segment following Control Point. If required by treatment delivery device, shall be present for first item of Control Point Sequence. If required by treatment delivery device and if Table Top Roll Rotation Direction changes during Beam, shall be present in all subsequent items of Control Point Sequence. See C.8.8.14.8 and C.8.8.25.6.2.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0128" name="&gt;&gt;Table Top Vertical Position" type="2C">
      <description>Table Top Vertical position in IEC TABLE TOP coordinate system (mm). This value is interpreted as an absolute, rather than relative, Table setting. Required for Control Point 0 of Control Point Delivery Sequence (3008,0040) or if Table Top Vertical Position changes during beam administration.</description>
    </entry>
    <entry group="300A" element="0129" name="&gt;&gt;Table Top Longitudinal Position" type="2C">
      <description>Table Top Longitudinal position in IEC TABLE TOP coordinate system (mm). This value is interpreted as an absolute, rather than relative, Table setting. Required for Control Point 0 of Control Point Delivery Sequence (3008,0040) or if Table Top Longitudinal Position changes during beam administration.</description>
    </entry>
    <entry group="300A" element="012A" name="&gt;&gt;Table Top Lateral Position" type="2C">
      <description>Table Top Lateral position in IEC TABLE TOP coordinate system (mm). This value is interpreted as an absolute, rather than relative, Table setting. Required for Control Point 0 of Control Point Delivery Sequence (3008,0040) or if Table Top Lateral Position changes during beam administration.</description>
    </entry>
    <entry group="3008" element="0068" name="&gt;&gt;Corrected Parameter Sequence" type="3">
      <description>Introduces a sequence of items describing any corrections made to any attributes prior to delivery of the next control point. The sequence may contain one or more items.</description>
    </entry>
    <entry group="3008" element="0061" name="&gt;&gt;&gt;Parameter Sequence Pointer" type="1">
      <description>Contains the Data Element Tag of the parent sequence containing the attribute that was corrected.
The value is limited in scope to the Treatment Session Beam Sequence (3008,0020) and all nested sequences therein.</description>
    </entry>
    <entry group="3008" element="0063" name="&gt;&gt;&gt;Parameter Item Index" type="1">
      <description>Contains the sequence item index (starting at 1) of the corrected attribute within its parent sequence.</description>
    </entry>
    <entry group="3008" element="0065" name="&gt;&gt;&gt;Parameter Pointer" type="1">
      <description>Contains the Data Element Tag of the attribute that was corrected.</description>
    </entry>
    <entry group="3008" element="006A" name="&gt;&gt;&gt;Correction Value" type="1">
      <description>The value applied to the attribute that was referenced by the Parameter Sequence Pointer (3008,0061), Parameter Item Index (3008,0063) and Parameter Pointer (3008,0065).</description>
    </entry>
    <entry group="3008" element="0060" name="&gt;&gt;Override Sequence" type="3">
      <description>Introduces sequence of parameters that were overridden during the administration of the beam segment immediately prior to the current control point. The sequence may contain one or more items.</description>
    </entry>
    <entry group="3008" element="0062" name="&gt;&gt;&gt;Override Parameter Pointer" type="2C">
      <description>Contains the Data Element Tag of the attribute that was overridden. Required if Override Sequence (3008,0060) is sent.</description>
    </entry>
    <entry group="3008" element="0061" name="&gt;&gt;&gt;Parameter Sequence Pointer" type="3">
      <description>Contains the Data Element Tag of the parent sequence containing the attribute that was overridden. The value is limited in scope to the Treatment Session Beam Sequence (3008,0020) and all nested sequences therein.</description>
    </entry>
    <entry group="3008" element="0063" name="&gt;&gt;&gt;Parameter Item Index" type="3">
      <description>Contains the sequence item index (monotonically increasing from 1) of the overridden attributes within its parent sequence. The value is limited in scope to the Treatment Session Beam Sequence (3008,0020) and all nested sequences therein.</description>
    </entry>
    <entry group="0008" element="1070" name="&gt;&gt;&gt;Operators' Name" type="2C">
      <description>Name of operator who authorized override. Required if Override Sequence (3008,0060) is sent.</description>
    </entry>
    <entry group="3008" element="0066" name="&gt;&gt;&gt;Override Reason" type="3">
      <description>User-defined description of reason for override of parameter specified by Override Parameter Pointer (3008,0062).</description>
    </entry>
  </module>
  <module ref="C.8.8.22" table="C.8-58" name="RT Brachy Session Record Module Attributes">
    <entry group="0008" element="1070" name="Operators' Name" type="2">
      <description>Name of operator administering treatment session.</description>
    </entry>
    <entry group="300C" element="0022" name="Referenced Fraction Group Number" type="3">
      <description>Identifier of Fraction Group within referenced RT Plan.</description>
    </entry>
    <entry group="300A" element="0078" name="Number of Fractions Planned" type="2">
      <description>Total number of treatments (Fractions) planned for current Fraction Group.</description>
    </entry>
    <entry group="300A" element="0200" name="Brachy Treatment Technique" type="1">
      <description>Type of brachytherapy treatment technique. Enumerated Values: INTRALUMENARY, INTRACAVITARY, INTERSTITIAL, CONTACT, INTRAVASCULAR, PERMANENT. See RT Plan IOD.</description>
    </entry>
    <entry group="300A" element="0202" name="Brachy Treatment Type" type="1">
      <description>Type of brachytherapy treatment.
Defined Terms:
MANUAL = manually positioned
HDR = High dose rate
MDR = Medium dose rate
LDR = Low dose rate
PDR = Pulsed dose rate</description>
    </entry>
    <entry group="3008" element="0100" name="Recorded Source Sequence" type="1">
      <description>Introduces sequence of Sources to be used within Application Setups. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300A" element="0212" name="&gt;Source Number" type="1">
      <description>Identification number of the Source. The value of Source Number (300A,0212) shall be unique within the Recorded Source Sequence (3008,0100) in which it is created.</description>
    </entry>
    <entry group="300A" element="0214" name="&gt;Source Type" type="1">
      <description>Type of Source. Defined Terms: POINT, LINE, CYLINDER, SPHERE.</description>
    </entry>
    <entry group="300A" element="0216" name="&gt;Source Manufacturer" type="2">
      <description>Manufacturer of source.</description>
    </entry>
    <entry group="3008" element="0105" name="&gt;Source Serial Number" type="2">
      <description>Serial Number of source.</description>
    </entry>
    <entry group="300A" element="0226" name="&gt;Source Isotope Name" type="1">
      <description>User-defined name of Isotope.</description>
    </entry>
    <entry group="300A" element="0228" name="&gt;Source Isotope Half Life" type="1">
      <description>Half-life of Isotope (days).</description>
    </entry>
    <entry group="300A" element="0229" name="&gt;Source Strength Units" type="1C">
      <description>Measurement unit of Source Strength.
Required if the source is not a gamma-emitting (photon) source. May be present otherwise.
Enumerated Values:
AIR_KERMA_RATE = Air Kerma Rate if Source is Gamma emitting Isotope.
DOSE_RATE_WATER = Dose Rate in Water if Source is Beta emitting Isotope.</description>
    </entry>
    <entry group="300A" element="022A" name="&gt;Reference Air Kerma Rate" type="1">
      <description>Air Kerma Rate in air of Isotope specified at Air Kerma Rate Reference Date (300A,022C) and Air Kerma Rate Reference Time (300A,022E) (in µGy h-1 at 1 m). Value shall be zero for non-gamma sources.</description>
    </entry>
    <entry group="300A" element="022B" name="&gt;Source Strength" type="1C">
      <description>Source Strength of Isotope at Source Strength Reference Date (300A,022C) and Source Strength Reference Time (300A,022E), in units specified in Source Strength Units (300A,0229).
Required if the source is not a gamma-emitting (photon) source. See C.8.8.15.13.</description>
      <section ref="C.8.8.15.13" name="">For beta emitting isotopes, the Source Strength (300A,022B) shall be defined at reference point (r0,θ0), where r0 is the radial distance of 2 mm from the source longitudinal axis, and θ0 is the angle of 90 degrees between the source longitudinal axis and the line defined by the center of the source and the reference point. Refer to:
•  IEC 60601-2-17 (Medical electrical equipment – Particular requirements for the safety of automatically-controlled brachytherapy afterloading equipment), where the beta source strength is defined as: ABSORBED DOSE RATE [Gy s-1] in water at 2 mm along the perpendicular bisector from a RADIOACTIVE SOURCE emitting beta RADIATION.
•  Nath et. al.: Intravascular brachytherapy physics: Report of the AAPM Radiation Therapy Committee Task Group No. 60, Med. Phys 26 (2) Feb 1999, pp 119-152.
</section>
    </entry>
    <entry group="300A" element="022C" name="&gt;Source Strength Reference Date" type="1">
      <description>Reference date for Reference Air Kerma Rate (300A,022A) or Source Strength (300A,022B) of Isotope.</description>
    </entry>
    <entry group="300A" element="022E" name="&gt;Source Strength Reference Time" type="1">
      <description>Reference time for Air Kerma Rate (300A,022A) or Source Strength (300A,022B) of Isotope.</description>
    </entry>
    <entry group="3008" element="0110" name="Treatment Session Application Setup Sequence" type="1">
      <description>Introduces sequence of Application Setups for RT Treatment Record for current RT Plan. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300A" element="0232" name="&gt;Application Setup Type" type="1">
      <description>Type of Application Setup. Defined Terms: FLETCHER_SUIT, DELCLOS, BLOEDORN, JOSLIN_FLYNN, CHANDIGARH, MANCHESTER, HENSCHKE, NASOPHARYNGEAL, OESOPHAGEAL, ENDOBRONCHIAL, SYED_NEBLETT, ENDORECTAL, PERINEAL.</description>
    </entry>
    <entry group="300C" element="000C" name="&gt;Referenced Brachy Application Setup Number" type="3">
      <description>References application setup specified by Application Setup Number (300A,0234) in Application Setup Sequence (300A,0230) in RT Brachy Applications Module within referenced RT Plan.</description>
    </entry>
    <entry group="300A" element="0236" name="&gt;Application Setup Name" type="3">
      <description>User-defined name for Application Setup.</description>
    </entry>
    <entry group="300A" element="0238" name="&gt;Application Setup Manufacturer" type="3">
      <description>Manufacturer of Application Setup.</description>
    </entry>
    <entry group="300A" element="0240" name="&gt;Template Number" type="3">
      <description>Identification number of the Template.</description>
    </entry>
    <entry group="300A" element="0242" name="&gt;Template Type" type="3">
      <description>User-defined type for Template Device.</description>
    </entry>
    <entry group="300A" element="0244" name="&gt;Template Name" type="3">
      <description>User-defined name for Template Device.</description>
    </entry>
    <entry group="3008" element="0116" name="&gt;Application Setup Check" type="3">
      <description>Results of check-wire travel through all channels of current Application Setup.
Enumerated Values:
PASSED = Passed check
FAILED = Failed check
UNKNOWN = Unknown status</description>
    </entry>
    <entry group="300C" element="0040" name="&gt;Referenced Verification Image Sequence" type="3">
      <description>Introduces sequence of verification images obtained during delivery of current beam. The sequence may contain one or more items. See Note.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="300A" element="0250" name="&gt;Total Reference Air Kerma" type="1">
      <description>Total Reference Air Kerma for current Application Setup, i.e. the sum of the products of the Air Kerma Rates of each Source in each Channel with its respective Channel Time (µGy at 1 m). Value shall be zero for non-gamma sources.</description>
    </entry>
    <entry group="3008" element="0080" name="&gt;Referenced Measured Dose Reference Sequence" type="3">
      <description>Introduces sequence of doses measured during treatment delivery, summed over entire session. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely references Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Plan. Required if Referenced Measured Dose Reference Sequence (3008,0080) is sent and Referenced Measured Dose Reference Number (3008,0082) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0082" name="&gt;&gt;Referenced Measured Dose Reference Number" type="1C">
      <description>Uniquely references Measured Dose Reference specified by Measured Dose Reference Number (3008,0064) in Measured Dose Reference Sequence (3008,0010). Required if Referenced Measured Dose Reference Sequence (3008,0080) is sent and Referenced Dose Reference Number (300C,0051) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0016" name="&gt;&gt;Measured Dose Value" type="1C">
      <description>Measured Dose in units specified by Dose Units (3004,0002) in sequence referenced by Measured Dose Reference Sequence (3008,0010) or Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Plan as defined above. Required if Referenced Measured Dose Reference Sequence (3008,0080) is sent.</description>
    </entry>
    <entry group="3008" element="0090" name="&gt;Referenced Calculated Dose Reference Sequence" type="3">
      <description>Introduces sequence of doses estimated for each treatment delivery. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Plan. Required if Referenced Calculated Dose Reference Sequence (3008,0090) is sent and Referenced Calculated Dose Reference Number (3008,0092) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0092" name="&gt;&gt;Referenced Calculated Dose Reference Number" type="1C">
      <description>Uniquely identifies Calculated Dose Reference specified by Calculated Dose Reference Number (3008,0072) within Calculated Dose Reference Sequence (3008,0070). Required if Referenced Calculated Dose Reference Sequence (3008,0090) is sent and Referenced Dose Reference Number (300C,0051) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0076" name="&gt;&gt;Calculated Dose Reference Dose Value" type="1C">
      <description>Calculated Dose (Gy). Required if Referenced Calculated Dose Reference Sequence (3008,0090) is sent.</description>
    </entry>
    <entry group="3008" element="0022" name="&gt;Current Fraction Number" type="2">
      <description>Fraction number for this application setup.</description>
    </entry>
    <entry group="300A" element="00CE" name="&gt;Treatment Delivery Type" type="2">
      <description>Delivery Type of treatment.
Defined Terms:
TREATMENT = normal patient treatment
CONTINUATION = continuation of interrupted treatment</description>
    </entry>
    <entry group="3008" element="002A" name="&gt;Treatment Termination Status" type="1">
      <description>Conditions under which treatment was terminated.
Enumerated Values:
NORMAL = treatment terminated normally
OPERATOR = operator terminated treatment
MACHINE = machine terminated treatment for other than NORMAL condition
UNKNOWN = status at termination unknown</description>
    </entry>
    <entry group="3008" element="002B" name="&gt;Treatment Termination Code" type="3">
      <description>Treatment machine termination code. This code is dependent upon the particular application and equipment.</description>
    </entry>
    <entry group="3008" element="002C" name="&gt;Treatment Verification Status" type="2">
      <description>Conditions under which treatment was verified by a verification system.
Enumerated Values:
VERIFIED = treatment verified
VERIFIED_OVR = treatment verified with at least one out-of-range value overridden
NOT_VERIFIED = treatment verified manually</description>
    </entry>
    <entry group="3008" element="0120" name="&gt;Recorded Brachy Accessory Device Sequence" type="3">
      <description>Introduces sequence of Brachy Accessory Devices associated with current Application Setup. The sequence may contain one or more items.</description>
    </entry>
    <entry group="3008" element="0122" name="&gt;&gt;Referenced Brachy Accessory Device Number" type="2C">
      <description>Identification number of the Brachy Accessory Device. The value of Brachy Accessory Device Number (300A,0262) shall be unique within the Application Setup in which it is created. Required if Recorded Brachy Accessory Device Sequence (3008,0120) is sent.</description>
    </entry>
    <entry group="300A" element="0263" name="&gt;&gt;Brachy Accessory Device ID" type="2C">
      <description>User or machine supplied identifier for Brachy Accessory Device. Required if Recorded Brachy Accessory Device Sequence (3008,0120) is sent.</description>
    </entry>
    <entry group="300A" element="0264" name="&gt;&gt;Brachy Accessory Device Type" type="1C">
      <description>Type of Brachy Accessory Device. Required if Recorded Brachy Accessory Device Sequence (3008,0120) is sent. Defined Terms: SHIELD, DILATATION, MOLD, PLAQUE, FLAB.</description>
    </entry>
    <entry group="300A" element="0266" name="&gt;&gt;Brachy Accessory Device Name" type="3">
      <description>User-defined name for Brachy Accessory Device.</description>
    </entry>
    <entry group="3008" element="0130" name="&gt;Recorded Channel Sequence" type="1">
      <description>Introduces sequence of Channels for current Application Setup. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300A" element="0282" name="&gt;&gt;Channel Number" type="1">
      <description>Identification number of the Channel. The value of Channel Number (300A,0282) shall be unique within the Application Setup in which it is created.</description>
    </entry>
    <entry group="300A" element="0284" name="&gt;&gt;Channel Length" type="2">
      <description>Length of Channel (mm). See RT Plan IOD.</description>
    </entry>
    <entry group="3008" element="0132" name="&gt;&gt;Specified Channel Total Time" type="1">
      <description>Total amount of time specified between Control Point 0 and final Control Point of the Brachy Control Point Sequence (300A,02D0) for current Channel (sec).</description>
    </entry>
    <entry group="3008" element="0134" name="&gt;&gt;Delivered Channel Total Time" type="1">
      <description>Total amount of time actually delivered between Control Point 0 and final Control Point of the Brachy Control Point Sequence (300A,02D0) for current Channel (sec).</description>
    </entry>
    <entry group="300A" element="0288" name="&gt;&gt;Source Movement Type" type="1">
      <description>Type of Source movement.
Defined Terms: STEPWISE, FIXED, OSCILLATING, UNIDIRECTIONAL.</description>
    </entry>
    <entry group="3008" element="0136" name="&gt;&gt;Specified Number of Pulses" type="1C">
      <description>Number of Pulses specified per fraction for current Channel. Required if Brachy Treatment Type (300A,0202) is PDR. See C.8.8.22.1.</description>
      <section ref="C.8.8.22.1" name="">In Brachytherapy treatment techniques where Brachy Treatment Type (300A,0202) is PDR, the Brachy Control Point Sequence (300A,02D0) shall consist of 2N items, where N = Delivered Number of Pulses (3008,0138). Each control point pair shall specify the start and end of a single pulse.
</section>
    </entry>
    <entry group="3008" element="0138" name="&gt;&gt;Delivered Number of Pulses" type="1C">
      <description>Number of Pulses actually delivered per fraction for current Channel. Required if Brachy Treatment Type (300A,0202) is PDR. See C.8.8.22.1.</description>
      <section ref="C.8.8.22.1" name="">In Brachytherapy treatment techniques where Brachy Treatment Type (300A,0202) is PDR, the Brachy Control Point Sequence (300A,02D0) shall consist of 2N items, where N = Delivered Number of Pulses (3008,0138). Each control point pair shall specify the start and end of a single pulse.
</section>
    </entry>
    <entry group="3008" element="013A" name="&gt;&gt;Specified Pulse Repetition Interval" type="1C">
      <description>Pulse repetition interval (sec) specified for current Channel. Required if Brachy Treatment Type (300A,0202) is PDR. See C.8.8.22.1</description>
      <section ref="C.8.8.22.1" name="">In Brachytherapy treatment techniques where Brachy Treatment Type (300A,0202) is PDR, the Brachy Control Point Sequence (300A,02D0) shall consist of 2N items, where N = Delivered Number of Pulses (3008,0138). Each control point pair shall specify the start and end of a single pulse.
</section>
    </entry>
    <entry group="3008" element="013C" name="&gt;&gt;Delivered Pulse Repetition Interval" type="1C">
      <description>Pulse repetition interval (sec) actually delivered for current Channel. Required if Brachy Treatment Type (300A,0202) is PDR. See C.8.8.22.1.</description>
      <section ref="C.8.8.22.1" name="">In Brachytherapy treatment techniques where Brachy Treatment Type (300A,0202) is PDR, the Brachy Control Point Sequence (300A,02D0) shall consist of 2N items, where N = Delivered Number of Pulses (3008,0138). Each control point pair shall specify the start and end of a single pulse.
</section>
    </entry>
    <entry group="3008" element="0080" name="&gt;&gt;Referenced Measured Dose Reference Sequence" type="3">
      <description>Introduces sequence of doses measured during treatment delivery, summed over entire session. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;&gt;&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely references Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Plan. Required if Referenced Measured Dose Reference Sequence (3008,0080) is sent and Referenced Measured Dose Reference Number (3008,0082) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0082" name="&gt;&gt;&gt;Referenced Measured Dose Reference Number" type="1C">
      <description>References Measured Dose Reference specified by Measured Dose Reference Number (3008,0064) in Measured Dose Reference Sequence (3008,0010). Required if Referenced Measured Dose Reference Sequence (3008,0080) is sent and Referenced Dose Reference Number (300C,0051) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0016" name="&gt;&gt;&gt;Measured Dose Value" type="1C">
      <description>Measured Dose. Required if Referenced Measured Dose Reference Sequence (3008,0080) is sent.</description>
    </entry>
    <entry group="3008" element="0090" name="&gt;&gt;Referenced Calculated Dose Reference Sequence" type="3">
      <description>Introduces sequence of doses estimated for each treatment delivery. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;&gt;&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Plan. Required if Referenced Calculated Dose Reference Sequence (3008,0090) is sent and Referenced Calculated Dose Reference Number (3008,0092) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0092" name="&gt;&gt;&gt;Referenced Calculated Dose Reference Number" type="1C">
      <description>Uniquely identifies Calculated Dose Reference specified by Calculated Dose Reference Number (3008,0072) within Calculated Dose Reference Sequence (3008,0070). Required if Referenced Calculated Dose Reference Sequence (3008,0090) is sent and Referenced Dose Reference Number (300C,0051) is not sent. It shall not be present otherwise.</description>
    </entry>
    <entry group="3008" element="0076" name="&gt;&gt;&gt;Calculated Dose Reference Dose Value" type="1C">
      <description>Calculated Dose (Gy). Required if Referenced Calculated Dose Reference Sequence (3008,0090) is sent.</description>
    </entry>
    <entry group="3008" element="0140" name="&gt;&gt;Recorded Source Applicator Sequence" type="3">
      <description>Introduces sequence of recorded Source Applicators. The sequence may contain one or more items.</description>
    </entry>
    <entry group="3008" element="0142" name="&gt;&gt;&gt;Referenced Source Applicator Number" type="2">
      <description>Identification number of the Source Applicator. The value of Source Applicator Number (300A,0290) shall be unique within the Channel in which it is created.</description>
    </entry>
    <entry group="300A" element="0291" name="&gt;&gt;&gt;Source Applicator ID" type="2C">
      <description>User or machine supplied identifier for Source Applicator. Required if Recorded Source Applicator Sequence (3008,0140) is sent.</description>
    </entry>
    <entry group="300A" element="0292" name="&gt;&gt;&gt;Source Applicator Type" type="1C">
      <description>Type of Source Applicator. Required if Recorded Source Applicator Sequence (3008,0140) is sent.
Enumerated Values: FLEXIBLE, RIGID.</description>
    </entry>
    <entry group="300A" element="0294" name="&gt;&gt;&gt;Source Applicator Name" type="3">
      <description>User-defined name for Source Applicator.</description>
    </entry>
    <entry group="300A" element="0296" name="&gt;&gt;&gt;Source Applicator Length" type="1C">
      <description>Length of Source Applicator (mm), defined as the distance between the connector of the applicator and the distal-most position of the source. Required if Recorded Source Applicator Sequence (3008,0140) is sent.</description>
    </entry>
    <entry group="300A" element="0298" name="&gt;&gt;&gt;Source Applicator Manufacturer" type="3">
      <description>Manufacturer of Source Applicator.</description>
    </entry>
    <entry group="300A" element="02A0" name="&gt;&gt;&gt;Source Applicator Step Size" type="1C">
      <description>Distance of path along channel (mm) between adjacent (potential) dwell positions. Required if Source Movement Type (300A,0288) is STEPWISE.</description>
    </entry>
    <entry group="300A" element="02A2" name="&gt;&gt;Transfer Tube Number" type="2">
      <description>Identification number of the Transfer Tube. The value of Transfer Tube Number (300A,02A2) shall be unique within the Channel in which it is created.</description>
    </entry>
    <entry group="300A" element="02A4" name="&gt;&gt;Transfer Tube Length" type="2C">
      <description>Length of Transfer Tube of current afterloading Channel (mm). Required if value Transfer Tube Number (300A,02A2) is not zero length.</description>
    </entry>
    <entry group="3008" element="0150" name="&gt;&gt;Recorded Channel Shield Sequence" type="3">
      <description>Introduces sequence of Channel Shields associated with current Channel. The sequence may contain one or more items. See RT Plan IOD for description of Channel Shields.</description>
    </entry>
    <entry group="3008" element="0152" name="&gt;&gt;&gt;Referenced Channel Shield Number" type="2C">
      <description>Identification number of the Channel Shield. The value of Channel Shield Number (300A,02B2) shall be unique within the Channel in which it is created. Required if Recorded Channel Shield Sequence (3008,0150) is sent.</description>
    </entry>
    <entry group="300A" element="02B3" name="&gt;&gt;&gt;Channel Shield ID" type="2C">
      <description>User or machine supplied identifier for Channel Shield. Required if Recorded Channel Shield Sequence (3008,0150) is sent.</description>
    </entry>
    <entry group="300A" element="02B4" name="&gt;&gt;&gt;Channel Shield Name" type="3">
      <description>User-defined name for Channel Shield.</description>
    </entry>
    <entry group="300C" element="000E" name="&gt;&gt;Referenced Source Number" type="1">
      <description>Uniquely identifies the referenced Source within the Recorded Source Sequence (3008,0100) for current Application Setup.</description>
    </entry>
    <entry group="3008" element="0162" name="&gt;&gt;Safe Position Exit Date" type="1C">
      <description>Date on which the source(s) exited the safe. Required if Recorded Channel Sequence (3008,0130) is sent and Brachy Treatment Type (300A,0202) is not MANUAL.</description>
    </entry>
    <entry group="3008" element="0164" name="&gt;&gt;Safe Position Exit Time" type="1C">
      <description>Time on which the source(s) exited the safe. Required if Recorded Channel Sequence (3008,0130) is sent and Brachy Treatment Type (300A,0202) is not MANUAL.</description>
    </entry>
    <entry group="3008" element="0166" name="&gt;&gt;Safe Position Return Date" type="1C">
      <description>Date on which the source(s) returned to the safe. Required if Recorded Channel Sequence (3008,0130) is sent and Brachy Treatment Type (300A,0202) is not MANUAL.</description>
    </entry>
    <entry group="3008" element="0168" name="&gt;&gt;Safe Position Return Time" type="1C">
      <description>Time on which the source(s) returned to the safe. Required if Recorded Channel Sequence (3008,0130) is sent and Brachy Treatment Type (300A,0202) is not MANUAL.</description>
    </entry>
    <entry group="300A" element="0110" name="&gt;&gt;Number of Control Points" type="1">
      <description>Number of control points in Channel. For an N-segment Channel there will be 2N (stepwise movement) or N+1 (continuous movement) control points.</description>
    </entry>
    <entry group="3008" element="0160" name="&gt;&gt;Brachy Control Point Delivered Sequence" type="1">
      <description>Introduces sequence of machine configurations describing this Channel. The sequence may contain two or more items. See RT Plan IOD and C.8.8.22.1 for description of Brachy Control Point Delivered Sequence.</description>
    </entry>
    <entry group="300C" element="00F0" name="&gt;&gt;&gt;Referenced Control Point Index" type="3">
      <description>Index of current Control Point, starting at 0 for first Control Point.</description>
    </entry>
    <entry group="3008" element="0024" name="&gt;&gt;&gt;Treatment Control Point Date" type="1">
      <description>Date when current Control Point occurred.</description>
    </entry>
    <entry group="3008" element="0025" name="&gt;&gt;&gt;Treatment Control Point Time" type="1">
      <description>Time when current Control Point occurred.</description>
    </entry>
    <entry group="300A" element="02D2" name="&gt;&gt;&gt;Control Point Relative Position" type="1">
      <description>Distance between current Control Point Position and the distal-most possible Source position in current Channel (mm). See RT Plan IOD.</description>
    </entry>
    <entry group="3008" element="0060" name="&gt;&gt;&gt;Override Sequence" type="3">
      <description>Introduces sequence of parameters which were overridden during the administration of the treatment immediately prior to the current control point. The sequence may contain one or more items.</description>
    </entry>
    <entry group="3008" element="0062" name="&gt;&gt;&gt;&gt;Override Parameter Pointer" type="2C">
      <description>Contains the Data Element Tag of the attribute which was overridden. Required if Override Sequence (3008,0060) is sent.</description>
    </entry>
    <entry group="0008" element="1070" name="&gt;&gt;&gt;&gt;Operators' Name" type="2C">
      <description>Name of operator who authorized override. Required if Override Sequence (3008,0060) is sent.</description>
    </entry>
    <entry group="3008" element="0066" name="&gt;&gt;&gt;&gt;Override Reason" type="3">
      <description>User-defined description of reason for override of parameter specified by Override Parameter Pointer (3008,0062).</description>
    </entry>
  </module>
  <module ref="C.8.8.23" table="C.8-59" name="RT Treatment Summary Record Module Attributes">
    <entry group="3008" element="0200" name="Current Treatment Status" type="1">
      <description>Status of the Treatment at the time the Treatment Summary was created. Enumerated Values:
NOT_STARTED, ON_TREATMENT, ON_BREAK, SUSPENDED, STOPPED, COMPLETED. See C.8.8.23.1.</description>
      <section ref="C.8.8.23.1" name="">The definition of the enumerated values for Current Treatment Status (3008,0200) are defined as follows:
NOT_STARTED    Patient has not yet begun treatment.
ON_TREATMENT  Patient is currently undergoing treatment.
ON_BREAK    Patient is currently not undergoing treatment, but a resumption date is known.
SUSPENDED    Patient is currently not undergoing treatment, but resumption of treatment is planned at an unknown date.
STOPPED    Patient has stopped treatment without completing the planned course.
COMPLETED    Patient completed the planned course of treatment.
A change in the Current Treatment Status (or any other field) in a RT Treatment Summary Record Object shall define a new instance of the RT Treatment Summary Record IOD.
</section>
    </entry>
    <entry group="3008" element="0202" name="Treatment Status Comment" type="3">
      <description>Comment on current treatment status.</description>
    </entry>
    <entry group="3008" element="0054" name="First Treatment Date" type="2">
      <description>Date of delivery of the first treatment.</description>
    </entry>
    <entry group="3008" element="0056" name="Most Recent Treatment Date" type="2">
      <description>Date of delivery of the most recent administration.</description>
    </entry>
    <entry group="3008" element="0220" name="Fraction Group Summary Sequence" type="3">
      <description>Introduces sequence describing current state of planned vs. delivered fraction groups. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0022" name="&gt;Referenced Fraction Group Number" type="3">
      <description>References Fraction Group Number (300A,0071) in Fraction Group Sequence (300A,0070) in the referenced RT Plan.</description>
    </entry>
    <entry group="3008" element="0224" name="&gt;Fraction Group Type" type="2C">
      <description>Indicates type of fraction group. Required if Fraction Group Summary Sequence (3008,0220) is sent. Enumerated Values: EXTERNAL_BEAM, BRACHY.</description>
    </entry>
    <entry group="300A" element="0078" name="&gt;Number of Fractions Planned" type="2C">
      <description>Number of fractions planned for this fraction group. Required if Fraction Group Summary Sequence (3008,0220) is sent.</description>
    </entry>
    <entry group="3008" element="005A" name="&gt;Number of Fractions Delivered" type="2C">
      <description>Number of fractions delivered as of Treatment Summary Report. Required if Fraction Group Summary Sequence (3008,0220) is sent.</description>
    </entry>
    <entry group="3008" element="0240" name="&gt;Fraction Status Summary Sequence" type="3">
      <description>Introduces sequence describing status of fractions in Fraction Group. The sequence may contain one or more items.</description>
    </entry>
    <entry group="3008" element="0223" name="&gt;&gt;Referenced Fraction Number" type="1C">
      <description>Identifies fraction. Required if Fraction Status Summary Sequence (3008,0240) is sent.</description>
    </entry>
    <entry group="3008" element="0250" name="&gt;&gt;Treatment Date" type="2C">
      <description>Date when fraction was delivered. Required if Fraction Status Summary Sequence (3008,0240) is sent.</description>
    </entry>
    <entry group="3008" element="0251" name="&gt;&gt;Treatment Time" type="2C">
      <description>Time when fraction was delivered. Required if Fraction Status Summary Sequence (3008,0240) is sent.</description>
    </entry>
    <entry group="3008" element="002A" name="&gt;&gt;Treatment Termination Status" type="2C">
      <description>Conditions under which treatment was terminated. Required if Fraction Status Summary Sequence (3008,0240) is sent.
Enumerated Values:
NORMAL = treatment terminated normally
OPERATOR = operator terminated treatment
MACHINE = machine terminated treatment for other than NORMAL condition
UNKNOWN = status at termination unknown</description>
    </entry>
    <entry group="3008" element="00E0" name="Treatment Summary Measured Dose Reference Sequence" type="3">
      <description>Introduces sequence of references to Measured Dose References. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;Referenced Dose Reference Number" type="3">
      <description>Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Plan referenced in Referenced RT Plan Sequence (300C,0002) of RT General Treatment Record Module.</description>
    </entry>
    <entry group="300A" element="0016" name="&gt;Dose Reference Description" type="3">
      <description>User-defined description of Dose Reference.</description>
    </entry>
    <entry group="3008" element="0052" name="&gt;Cumulative Dose to Dose Reference" type="1C">
      <description>Cumulative Dose delivered to Dose Reference (Gy). Required if Treatment Summary Dose Reference Sequence (3008,00E0) is sent.</description>
    </entry>
    <entry group="3008" element="0050" name="Treatment Summary Calculated Dose Reference Sequence" type="3">
      <description>Introduces sequence of references to Calculated Dose References. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;Referenced Dose Reference Number" type="3">
      <description>Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Plan referenced in Referenced RT Plan Sequence (300C,0002) of RT General Treatment Record Module.</description>
    </entry>
    <entry group="300A" element="0016" name="&gt;Dose Reference Description" type="3">
      <description>User-defined description of Dose Reference.</description>
    </entry>
    <entry group="3008" element="0052" name="&gt;Cumulative Dose to Dose Reference" type="1C">
      <description>Cumulative Dose delivered to Dose Reference (Gy). Required if Treatment Summary Dose Reference Sequence (3008,0050) is sent.</description>
    </entry>
  </module>
  <module ref="C.8.8.24" table="C.8.8.24-1" name="RT Ion Tolerance Tables Module Attributes">
    <entry group="300A" element="03A0" name="Ion Tolerance Table Sequence" type="1">
      <description>Introduces sequence of ion tolerance tables to be used for delivery of treatment plan. One or more items shall be included in this sequence. See Note 1.</description>
    </entry>
    <entry group="300A" element="0042" name="&gt;Tolerance Table Number" type="1">
      <description>Identification number of the Tolerance Table. The value of Tolerance Table Number (300A,0042) shall be unique within the RT Ion Plan in which it is created.</description>
    </entry>
    <entry group="300A" element="0043" name="&gt;Tolerance Table Label" type="3">
      <description>User-defined label for Tolerance Table.</description>
    </entry>
    <entry group="300A" element="0044" name="&gt;Gantry Angle Tolerance" type="3">
      <description>Maximum permitted difference (in degrees) between planned and delivered Gantry Angle.</description>
    </entry>
    <entry group="300A" element="0046" name="&gt;Beam Limiting Device Angle Tolerance" type="3">
      <description>Maximum permitted difference (in degrees) between planned and delivered Beam Limiting Device Angle.</description>
    </entry>
    <entry group="300A" element="0048" name="&gt;Beam Limiting Device Tolerance Sequence" type="3">
      <description>Introduces sequence of beam limiting device (collimator) tolerances. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00B8" name="&gt;&gt;RT Beam Limiting Device Type" type="1">
      <description>Type of beam limiting device (collimator).
Enumerated Values:
X = symmetric jaw pair in IEC X direction
Y = symmetric jaw pair in IEC Y direction
ASYMX = asymmetric jaw pair in IEC X
direction
ASYMY = asymmetric pair in IEC Y
direction
MLCX = multileaf (multi-element) jaw pair
in IEC X direction
MLCY = multileaf (multi-element) jaw pair
in IEC Y direction</description>
    </entry>
    <entry group="300A" element="004A" name="&gt;&gt;Beam Limiting Device Position Tolerance" type="1">
      <description>Maximum permitted difference (in mm) between planned and delivered leaf (element) or jaw positions for current beam limiting device (collimator).</description>
    </entry>
    <entry group="300A" element="004C" name="&gt;Patient Support Angle Tolerance" type="3">
      <description>Maximum permitted difference (in degrees) between planned and delivered Patient Support Angle.</description>
    </entry>
    <entry group="300A" element="0051" name="&gt;Table Top Vertical Position Tolerance" type="3">
      <description>Maximum permitted difference (in mm) between planned and delivered Table Top Vertical Position.</description>
    </entry>
    <entry group="300A" element="0052" name="&gt;Table Top Longitudinal Position Tolerance" type="3">
      <description>Maximum permitted difference (in mm) between planned and delivered Table Top Longitudinal Position.</description>
    </entry>
    <entry group="300A" element="0053" name="&gt;Table Top Lateral Position Tolerance" type="3">
      <description>Maximum permitted difference (in mm) between planned and delivered Table Top Lateral Position.</description>
    </entry>
    <entry group="300A" element="004F" name="&gt;Table Top Pitch Angle Tolerance" type="3">
      <description>Maximum permitted difference (in degrees) between planned and delivered Table Top Pitch Angle.</description>
    </entry>
    <entry group="300A" element="0050" name="&gt;Table Top Roll Angle Tolerance" type="3">
      <description>Maximum permitted difference (in degrees) between planned and delivered Table Top Roll Angle.</description>
    </entry>
    <entry group="300A" element="004B" name="&gt;Snout Position Tolerance" type="3">
      <description>Maximum permitted difference (in mm) between planned and delivered Snout Position.</description>
    </entry>
  </module>
  <module ref="C.8.8.25" table="C.8.8.25-1" name="RT Ion Beams Module Attributes">
    <entry group="300A" element="03A2" name="Ion Beam Sequence" type="1">
      <description>Introduces sequence of setup and/or treatment beams for current RT Ion Plan. One or more items shall be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00C0" name="&gt;Beam Number" type="1">
      <description>Identification number of the Beam. The value of Beam Number (300A,00C0) shall be unique within the RT Ion Plan in which it is created. See section C.8.8.25.1.</description>
    </entry>
    <entry group="300A" element="00C2" name="&gt;Beam Name" type="1">
      <description>User-defined name for Beam. See section C.8.8.25.1.</description>
    </entry>
    <entry group="300A" element="00C3" name="&gt;Beam Description" type="3">
      <description>User-defined description for Beam. See section C.8.8.25.1.</description>
    </entry>
    <entry group="300A" element="00C4" name="&gt;Beam Type" type="1">
      <description>Motion characteristic of Beam.
Enumerated Values:
STATIC = all beam parameters remain unchanged during delivery
DYNAMIC = one or more beam parameters changes during delivery</description>
    </entry>
    <entry group="300A" element="00C6" name="&gt;Radiation Type" type="1">
      <description>Particle type of Beam.
Defined Terms:
PHOTON
PROTON
ION</description>
    </entry>
    <entry group="300A" element="0302" name="&gt;Radiation Mass Number" type="1C">
      <description>Mass number of radiation. Required if Radiation Type (300A,00C6) is ION</description>
    </entry>
    <entry group="300A" element="0304" name="&gt;Radiation Atomic Number" type="1C">
      <description>Atomic number of radiation. Required if Radiation Type (300A,00C6) is ION</description>
    </entry>
    <entry group="300A" element="0306" name="&gt;Radiation Charge State" type="1C">
      <description>Charge state of radiation. Required if Radiation Type (300A,00C6) is ION</description>
    </entry>
    <entry group="300A" element="0308" name="&gt;Scan Mode" type="1">
      <description>The method of beam scanning to be used during treatment.
Defined Terms:
NONE = No beam scanning is performed.
UNIFORM = The beam is scanned between control points to create a uniform lateral fluence distribution across the field.
MODULATED = The beam is scanned between control points to create a modulated lateral fluence distribution across the field.</description>
    </entry>
    <entry group="300A" element="00B2" name="&gt;Treatment Machine Name" type="2">
      <description>User-defined name identifying treatment machine to be used for beam delivery. See section C.8.8.25.2.</description>
    </entry>
    <entry group="0008" element="0070" name="&gt;Manufacturer" type="3">
      <description>Manufacturer of the equipment to be used for beam delivery.</description>
    </entry>
    <entry group="0008" element="0080" name="&gt;Institution Name" type="3">
      <description>Institution where the equipment is located that is to be used for beam delivery.</description>
    </entry>
    <entry group="0008" element="0081" name="&gt;Institution Address" type="3">
      <description>Mailing address of the institution where the equipment is located that is to be used for beam delivery.</description>
    </entry>
    <entry group="0008" element="1040" name="&gt;Institutional Department Name" type="3">
      <description>Department in the institution where the equipment is located that is to be used for beam delivery.</description>
    </entry>
    <entry group="0008" element="1090" name="&gt;Manufacturer's Model Name" type="3">
      <description>Manufacturer's model name of the equipment that is to be used for beam delivery.</description>
    </entry>
    <entry group="0018" element="1000" name="&gt;Device Serial Number" type="3">
      <description>Manufacturer's serial number of the equipment that is to be used for beam delivery.</description>
    </entry>
    <entry group="300A" element="00B3" name="&gt;Primary Dosimeter Unit" type="1">
      <description>Measurement unit of machine dosimeter.
Enumerated Values:
MU = Monitor Unit
NP = number of particles</description>
    </entry>
    <entry group="300C" element="00A0" name="&gt;Referenced Tolerance Table Number" type="3">
      <description>Uniquely identifies Tolerance Table specified by Tolerance Table Number (300A,0042) within Tolerance Table Sequence in RT Ion Tolerance Tables Module. These tolerances are to be used for verification of treatment machine settings.</description>
    </entry>
    <entry group="300A" element="030A" name="&gt;Virtual Source-Axis Distances" type="1">
      <description>Distance (in mm) from virtual source position to gantry rotation axis or nominal isocenter position (fixed beam-lines) of the equipment to be used for beam delivery. Specified by a numeric pair - the VSAD in the IEC Gantry X direction followed by the VSAD in the IEC Gantry Y direction.
The VSAD is commonly used for designing apertures in contrast to the effective source-axis-distance (ESAD) that is commonly used with the inverse square law for calculating the dose decrease with distance. See section C.8.8.25.4.</description>
    </entry>
    <entry group="300A" element="03A4" name="&gt;Ion Beam Limiting Device Sequence" type="3">
      <description>Introduces sequence of beam limiting device (collimator) jaw or leaf (element) sets. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00B8" name="&gt;&gt;RT Beam Limiting Device Type" type="1">
      <description>Type of beam limiting device (collimator).
Enumerated Values:
X = symmetric jaw pair in IEC X direction
Y = symmetric jaw pair in IEC Y direction
ASYMX = asymmetric jaw pair in IEC X direction
ASYMY = asymmetric pair in IEC Y direction
MLCX = multileaf (multi-element) jaw pair in IEC X direction
MLCY = multileaf (multi-element) jaw pair in IEC Y direction</description>
    </entry>
    <entry group="300A" element="00BB" name="&gt;&gt;Isocenter to Beam Limiting Device Distance" type="2">
      <description>Isocenter to beam limiting device (collimator) distance (in mm) of the equipment that is to be used for beam delivery.
See section C.8.8.25.4.</description>
    </entry>
    <entry group="300A" element="00BC" name="&gt;&gt;Number of Leaf/Jaw Pairs" type="1">
      <description>Number of leaf (element) or jaw pairs (equal to 1 for standard beam limiting device jaws).</description>
    </entry>
    <entry group="300A" element="00BE" name="&gt;&gt;Leaf Position Boundaries" type="1C">
      <description>Boundaries of beam limiting device (collimator) leaves (in mm) in IEC BEAM LIMITING DEVICE coordinate axis appropriate to RT Beam Limiting Device Type (300A,00B8), i.e. X-axis for MLCY, Y-axis for MLCX.
Contains N+1 values, where N is the Number of Leaf/Jaw Pairs (300A,00BC), starting from Leaf (Element) Pair 1. Required if RT Beam Limiting Device Type (300A,00B8) is MLCX or MLCY. See section C.8.8.25.3.</description>
    </entry>
    <entry group="300C" element="006A" name="&gt;Referenced Patient Setup Number" type="3">
      <description>Uniquely identifies Patient Setup to be used for current beam, specified by Patient Setup Number (300A,0182) within Patient Setup Sequence of RT Patient Setup Module.</description>
    </entry>
    <entry group="300C" element="0042" name="&gt;Referenced Reference Image Sequence" type="3">
      <description>Introduces sequence of reference images used for validation of current beam. One or more items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="300A" element="00C8" name="&gt;&gt;Reference Image Number" type="1">
      <description>Uniquely identifies Reference Image within Referenced Reference Image Sequence (300C,0042).</description>
    </entry>
    <entry group="300A" element="00CE" name="&gt;Treatment Delivery Type" type="1">
      <description>Delivery Type of treatment.
Defined Terms:
TREATMENT = normal patient treatment
OPEN_PORTFILM = portal image acquisition with open field (the source of radiation is specified by Radiation Type (300A,00C6))
TRMT_PORTFILM = portal image acquisition with treatment port (the source of radiation is specified by Radiation Type (300A,00C6))
CONTINUATION = continuation of interrupted treatment
SETUP = no treatment beam is applied for this RT Beam. To be used for specifying the gantry, couch, and other machine positions where X-Ray set-up images or measurements shall be taken.</description>
    </entry>
    <entry group="300C" element="0080" name="&gt;Referenced Dose Sequence" type="3">
      <description>Introduces sequence of related SOP Class/Instance pairs describing related instances of RT Dose (for grids, isodose curves, and named/unnamed point doses). One or more items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include SOP Instance Reference Macro Table 10-11" description="The Referenced Class SOP UID shall be that of the RT Dose SOP Class (1.2.840.10008.5.1.4.1.1.481.2)"/>
    <entry group="300A" element="00D0" name="&gt;Number of Wedges" type="1">
      <description>Number of wedges associated with current beam.</description>
    </entry>
    <entry group="300A" element="00D7" name="&gt;Total Wedge Tray Water-Equivalent Thickness" type="3">
      <description>Shift of the wedge tray induced on the range of the ion beam as measured in water (in mm).</description>
    </entry>
    <entry group="300A" element="03AA" name="&gt;Ion Wedge Sequence" type="1C">
      <description>Introduces sequence of treatment wedges. Required if Number of Wedges (300A,00D0) is non-zero. The number of items shall be identical to the value of Number of Wedges (300A,00D0).</description>
    </entry>
    <entry group="300A" element="00D2" name="&gt;&gt;Wedge Number" type="1">
      <description>Identification number of the Wedges. The value of Wedge Number (300A,00D2) shall be unique within the Beam in which it was created.</description>
    </entry>
    <entry group="300A" element="00D3" name="&gt;&gt;Wedge Type" type="2">
      <description>Typer of wedge (if any) defined for Beam.

Defined Terms:
STANDARD = standard (static) wedge
MOTORIZED = single wedge that can be removed from beam remotely.
PARTIAL_STANDARD = wedge does not extend across the whole field and is operated manually.
PARTIAL_MOTORIZ = wedge does not extend across the whole field and can be removed from beam remotely.</description>
    </entry>
    <entry group="300A" element="00D4" name="&gt;&gt;Wedge ID" type="3">
      <description>User-supplied identifier for Wedge.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="00D5" name="&gt;&gt;Wedge Angle" type="2">
      <description>Nominal wedge angle (degrees).</description>
    </entry>
    <entry group="300A" element="00D8" name="&gt;&gt;Wedge Orientation" type="2">
      <description>Orientation of wedge, i.e. orientation of IEC WEDGE FILTER coordinate system with respect to the IEC BEAM LIMITING DEVICE coordinate systems (degrees).</description>
    </entry>
    <entry group="300A" element="00D9" name="&gt;&gt;Isocenter to Wedge Tray Distance" type="1">
      <description>Isocenter to downstream edge of wedge tray (mm).
See section C.8.8.25.4</description>
    </entry>
    <entry group="300A" element="00E0" name="&gt;Number of Compensators" type="1">
      <description>Number of compensators associated with current Beam.</description>
    </entry>
    <entry group="300A" element="02E3" name="&gt;Total Compensator Tray Water-Equivalent Thickness" type="3">
      <description>Water-Equivalent thickness of the compensator tray (in mm) parallel to radiation beam axis.</description>
    </entry>
    <entry group="300A" element="02EA" name="&gt;Ion Range Compensator Sequence" type="1C">
      <description>Introduces sequence of compensators. Required if Number of Compensators (300A,00E0) is non-zero. The number of items shall be identical to the value of Number of Compensators (300A,00E0).</description>
    </entry>
    <entry group="300A" element="02EB" name="&gt;&gt;Compensator Description" type="3">
      <description>User defined description for the compensator.</description>
    </entry>
    <entry group="300A" element="00E4" name="&gt;&gt;Compensator Number" type="1">
      <description>Identification number of the Compensator. The value of Compensator Number (300A,00E4) shall be unique within the Beam in which it is created.</description>
    </entry>
    <entry group="300A" element="00E1" name="&gt;&gt;Material ID" type="2">
      <description>User-supplied identifier for material used to manufacture Compensator.</description>
    </entry>
    <entry group="300A" element="00E5" name="&gt;&gt;Compensator ID" type="3">
      <description>User-supplied identifier for the compensator.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="02E4" name="&gt;&gt;Isocenter to Compensator Tray Distance" type="1C">
      <description>Isocenter to compensator tray attachment edge distance (in mm) for current range compensator. Required if Compensator Mounting Position (300A,02E1) is not DOUBLE_SIDED. See section C.8.8.25.4</description>
    </entry>
    <entry group="300A" element="02E0" name="&gt;&gt;Compensator Divergence" type="1">
      <description>Indicates presence or absence of geometrical divergence of the range compensator.
Enumerated Values:
PRESENT = the range compensator is shaped according to the beam geometrical divergence.
ABSENT = the range compensator is not shaped according to the beam geometrical divergence.</description>
    </entry>
    <entry group="300A" element="02E1" name="&gt;&gt;Compensator Mounting Position" type="1">
      <description>Indicates on which side of the Compensator Tray the compensator is mounted.
Enumerated Values:
PATIENT_SIDE = the Compensator is mounted on the side of the Compensator Tray that is towards the patient.
SOURCE_SIDE = the Compensator is mounted on the side of the Compensator Tray that is towards the radiation source.
DOUBLE_SIDED = the Compensator has a shaped (i.e. non-flat) surface on both sides of the Compensator Tray.</description>
    </entry>
    <entry group="300A" element="00E7" name="&gt;&gt;Compensator Rows" type="1">
      <description>Number of rows in the range compensator. A row is defined to be in the X direction of the IEC Beam Limiting Device Coordinate system.</description>
    </entry>
    <entry group="300A" element="00E8" name="&gt;&gt;Compensator Columns" type="1">
      <description>Number of columns in the range compensator. A column is defined to be in the Y direction of the IEC Beam Limiting Device Coordinate system.</description>
    </entry>
    <entry group="300A" element="00E9" name="&gt;&gt;Compensator Pixel Spacing" type="1">
      <description>Physical distance (in mm) between the center of each pixel projected onto machine isocentric plane. Specified by a numeric pair - adjacent row spacing followed by adjacent column spacing. See 10.7.1.3 for further explanation of the value order.</description>
    </entry>
    <entry group="300A" element="00EA" name="&gt;&gt;Compensator Position" type="1">
      <description>The x and y coordinates of the upper left hand corner (first pixel transmitted) of the range compensator, projected onto the machine isocentric plane in the IEC BEAM LIMITING DEVICE coordinate system (mm).</description>
    </entry>
    <entry group="300A" element="02E5" name="&gt;&gt;Compensator Column Offset" type="1C">
      <description>The offset distance (in mm) applied to the x coordinate of the Compensator Position (300A,00EA) for even numbered rows. Required if the compensator pattern is hexogonal.</description>
    </entry>
    <entry group="300A" element="00EC" name="&gt;&gt;Compensator Thickness Data" type="1">
      <description>A data stream of the pixel samples that comprise the range compensator, expressed as physical thickness (in mm), either parallel to radiation beam axis if Compensator Divergence (300A,02E0) equals ABSENT, or divergent according to the beam geometrical divergence if Compensator Divergence (300A,02E0) equals PRESENT. The order of pixels sent is left to right, top to bottom (upper left pixel, followed by the remainder of row 1, followed by the remainder of the rows).</description>
    </entry>
    <entry group="300A" element="02E6" name="&gt;&gt;Isocenter to Compensator Distances" type="1C">
      <description>A data stream of the pixel samples that comprise the distance from the isocenter to the compensator surface closest to the radiation source (in mm). The order of pixels sent is left to right, top to bottom (upper left pixel, followed by the remainder of row 1, followed by the remainder of the rows). Required if Material ID (300A,00E1) is non-zero length, and Compensator Mounting Position (300A,02E1) is DOUBLE_SIDED. See sections C.8.8.14.9 and C.8.8.25.4</description>
    </entry>
    <entry group="300A" element="02E7" name="&gt;&gt;Compensator Relative Stopping Power Ratio" type="3">
      <description>Compensator Linear Stopping Power Ratio, relative to water, at the beam energy specified by the Nominal Beam Energy (300A,0114) of the first Control Point of the Ion Control Point Sequence (300A,03A8).</description>
    </entry>
    <entry group="300A" element="02E8" name="&gt;&gt;Compensator Milling Tool Diameter" type="3">
      <description>The diameter (in mm) of the milling tool to be used to create the compensator. The diameter is expressed as the actual physcial size and not a projected size at isocenter.</description>
    </entry>
    <entry group="300A" element="00ED" name="&gt;Number of Boli" type="1">
      <description>Number of boli associated with current Beam.</description>
    </entry>
    <entry group="300C" element="00B0" name="&gt;Referenced Bolus Sequence" type="1C">
      <description>Introduces sequence of boli associated with Beam. Required if Number of Boli (300A,00ED) is non-zero. The number of items shall be identical to the value of Number of Boli (300A,00ED).</description>
    </entry>
    <entry group="3006" element="0084" name="&gt;&gt;Referenced ROI Number" type="1">
      <description>Uniquely identifies ROI representing the Bolus specified by ROI Number (3006,0022) in Structure Set ROI Sequence (3006,0020) in Structure Set Module within RT Structure Set in Referenced Structure Set Sequence (300C,0060) in RT General Plan Module.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="00F0" name="&gt;Number of Blocks" type="1">
      <description>Number of shielding blocks associated with Beam.</description>
    </entry>
    <entry group="300A" element="00F3" name="&gt;Total Block Tray Water-Equivalent Thickness" type="3">
      <description>Water-Equivalent thickness of the block tray (in mm) parallel to radiation beam axis.</description>
    </entry>
    <entry group="300A" element="03A6" name="&gt;Ion Block Sequence" type="1C">
      <description>Introduces sequence of blocks associated with Beam. Required if Number of Blocks (300A,00F0) is non-zero. The number of items shall be identical to the value of Number of Blocks (300A,00F0).</description>
    </entry>
    <entry group="300A" element="00F5" name="&gt;&gt;Block Tray ID" type="3">
      <description>User-supplied identifier for block tray.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="00F7" name="&gt;&gt;Isocenter to Block Tray Distance" type="1">
      <description>Isocenter to downstream edge of block tray (mm). See section C.8.8.25.4</description>
    </entry>
    <entry group="300A" element="00F8" name="&gt;&gt;Block Type" type="1">
      <description>Type of block. See section C.8.8.14.4.
Enumerated Values:
SHIELDING = blocking material is inside contour
APERTURE = blocking material is outside contour</description>
    </entry>
    <entry group="300A" element="00FA" name="&gt;&gt;Block Divergence" type="1">
      <description>Indicates presence or otherwise of geometrical divergence.
Enumerated Values:
PRESENT = block edges are shaped for beam divergence
ABSENT = block edges are not shaped for beam divergence</description>
    </entry>
    <entry group="300A" element="00FB" name="&gt;&gt;Block Mounting Position" type="1">
      <description>Indicates on which side of the Block Tray the block is mounted.
Enumerated Values;
PATIENT_SIDE = the block is mounted on the side of the Block Tray that is towards the patient.
SOURCE_SIDE = the block is mounted on the side of the Block Tray that is towards the radiation source.</description>
    </entry>
    <entry group="300A" element="00FC" name="&gt;&gt;Block Number" type="1">
      <description>Identification number of the Block. The value of Block Number (300A,00FC) shall be unique within the Beam in which it is created.</description>
    </entry>
    <entry group="300A" element="00FE" name="&gt;&gt;Block Name" type="3">
      <description>User-defined name for block.</description>
    </entry>
    <entry group="300A" element="00E1" name="&gt;&gt;Material ID" type="2">
      <description>User-supplied identifier for material used to manufacture Block.</description>
    </entry>
    <entry group="300A" element="0100" name="&gt;&gt;Block Thickness" type="1">
      <description>Physical thickness of block (in mm) parallel to radiation beam axis. See section C.8.8.14.4.</description>
    </entry>
    <entry group="300A" element="0104" name="&gt;&gt;Block Number of Points" type="1">
      <description>Number of (x,y) pairs defining the block edge.</description>
    </entry>
    <entry group="300A" element="0106" name="&gt;&gt;Block Data" type="1">
      <description>A data stream of (x,y) pairs that comprise the block edge. The number of pairs shall be equal to Block Number of Points (300A,0104), and the vertices shall be interpreted as a closed polygon. Coordinates are projected onto the machine isocentric plane in the IEC BEAM LIMITING DEVICE coordinate system (mm).</description>
    </entry>
    <entry group="300A" element="030C" name="&gt;Snout Sequence" type="3">
      <description>Introduces sequence of Snouts associated with Beam. Only a single item shall be permitted in this sequence.</description>
    </entry>
    <entry group="300A" element="030F" name="&gt;&gt;Snout ID" type="1">
      <description>User or machine supplied identifier for Snout.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="0107" name="&gt;Applicator Sequence" type="3">
      <description>Introduces sequence of Applicators associated with Beam. Only a single item shall be permitted in this sequence.</description>
    </entry>
    <entry group="300A" element="0108" name="&gt;&gt;Applicator ID" type="1">
      <description>User or machine supplied identifier for Applicator. See section C.8.8.14.12</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="0109" name="&gt;&gt;Applicator Type" type="1">
      <description>Type of applicator.

Defined Terms:
ION_SQUARE = square ion applicator
ION_RECT = rectangluar ion applicator
ION_CIRC = circular ion applicator
ION_SHORT = short ion applicator
ION_OPEN = open (dummy) ion applicator
INTEROPERATIVE = interoperative (custom) applicator
STEREOTACTIC = stereotactic applicator</description>
    </entry>
    <entry group="300A" element="010A" name="&gt;&gt;Applicator Description" type="3">
      <description>User-defined description for Applicator.</description>
    </entry>
    <entry group="300A" element="0420" name="&gt;General Accessory Sequence" type="3">
      <description>Introduces a Sequence of General Accessories associated with this Beam. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="0424" name="&gt;&gt;General Accessory Number" type="1">
      <description>Identification Number of the General Accessory. The value shall be unique within the sequence.</description>
    </entry>
    <entry group="300A" element="0421" name="&gt;&gt;General Accessory ID" type="1">
      <description>User or machine supplied identifier for General Accessory.</description>
    </entry>
    <entry group="300A" element="0422" name="&gt;&gt;General Accessory Description" type="3">
      <description>User supplied description of General Accessory.</description>
    </entry>
    <entry group="300A" element="0423" name="&gt;&gt;General Accessory Type" type="3">
      <description>Specifies the type of accessory.
Defined Terms:
GRATICULE = Accessory tray with a radio-opaque grid
IMAGE_DETECTOR = Image acquisition device positioned in the beam line
RETICLE = Accessory tray with radio-transparent markers or grid</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>Machine-readable identifier for this accessory</description>
    </entry>
    <entry group="300A" element="0312" name="&gt;Number of Range Shifters" type="1">
      <description>Number of range shifters associated with current beam.</description>
    </entry>
    <entry group="300A" element="0314" name="&gt;Range Shifter Sequence" type="1C">
      <description>Introduces sequence of range shifters associated with Beam. Required if Number of Range Shifters (300A,0312) is non-zero. The number of items shall be identical to the value of Number of Range Shifters (300A,0312).</description>
    </entry>
    <entry group="300A" element="0316" name="&gt;&gt;Range Shifter Number" type="1">
      <description>Identification number of the Range Shifter. The value of Range Shifter Number (300A,0316) shall be unique within the Beam in which it is created.</description>
    </entry>
    <entry group="300A" element="0318" name="&gt;&gt;Range Shifter ID" type="1">
      <description>User or machine supplied identifier for Range Shifter.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="0320" name="&gt;&gt;Range Shifter Type" type="1">
      <description>Type of Range Shifter.
Defined Terms:
ANALOG = Device is variable thickness and is composed of opposing sliding wedges, water column or similar mechanism.
BINARY = Device is composed of different thickness materials that can be moved in or out of the beam in various stepped combinations.</description>
    </entry>
    <entry group="300A" element="0322" name="&gt;&gt;Range Shifter Description" type="3">
      <description>User defined description of Range Shifter.</description>
    </entry>
    <entry group="300A" element="0330" name="&gt;Number of Lateral Spreading Devices" type="1">
      <description>Number of lateral spreading devices associated with current beam.</description>
    </entry>
    <entry group="300A" element="0332" name="&gt;Lateral Spreading Device Sequence" type="1C">
      <description>Introduces sequence of lateral spreading devices associated with Beam. Required if Number of Lateral Spreading Devices (300A,0330) is non-zero. The number of items shall be identical to the value of Number of Lateral Spreading Devices (300A,0330).</description>
    </entry>
    <entry group="300A" element="0334" name="&gt;&gt;Lateral Spreading Device Number" type="1">
      <description>Identification number of the Lateral Spreading Device. The value of Lateral Spreading Device Number (300A,0334) shall be unique within the Beam in which it is created.</description>
    </entry>
    <entry group="300A" element="0336" name="&gt;&gt;Lateral Spreading Device ID" type="1">
      <description>User or machine supplied identifier for Lateral Spreading Device.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="0338" name="&gt;&gt;Lateral Spreading Device Type" type="1">
      <description>Type of Lateral Spreading Device.
Defined Terms:
SCATTERER = metal placed into the beam path to scatter charged particles laterally.
MAGNET = nozzle configuration of magnet devices to expand beam laterally.</description>
    </entry>
    <entry group="300A" element="033A" name="&gt;&gt;Lateral Spreading Device Description" type="3">
      <description>User-defined description for lateral spreading device.</description>
    </entry>
    <entry group="300A" element="0340" name="&gt;Number of Range Modulators" type="1">
      <description>Number of range modulators associated with current beam.</description>
    </entry>
    <entry group="300A" element="0342" name="&gt;Range Modulator Sequence" type="1C">
      <description>Introduces sequence of range modulators associated with Beam. Required if Number of Range Modulators (300A,0340) is non-zero. The number of items shall be identical to the value of Number of Range Modulators (300A,0340).</description>
    </entry>
    <entry group="300A" element="0344" name="&gt;&gt;Range Modulator Number" type="1">
      <description>Identification number of the Range Modulator. The value of Range Modulator Number (300A,0344) shall be unique within the Beam in which it is created.</description>
    </entry>
    <entry group="300A" element="0346" name="&gt;&gt;Range Modulator ID" type="1">
      <description>User or machine supplied identifier for Range Modulator.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="0348" name="&gt;&gt;Range Modulator Type" type="1">
      <description>Type of Range Modulator.
Defined Terms:
FIXED = fixed modulation width and weights using ridge filter or constant speed wheel with constant beam current
WHL_FIXEDWEIGHTS = selected wheel/track (Range Modulator ID) is spinning at constant speed. Modulation width is adjusted by switching constant beam current on and off at wheel steps indicated by Range Modulator Gating Values.
WHL_MODWEIGHTS = selected wheel/track (Range Modulator ID) is spinning at constant speed. Weight per wheel step is adjusted by modulating beam current according to selected Beam Current Modulation ID (300A,034C).
Only one item in the Range Modulator Sequence (300A,0342) can have a Range Modulator Type (300A,0348) of WHL_MODWEIGHTS.</description>
    </entry>
    <entry group="300A" element="034A" name="&gt;&gt;Range Modulator Description" type="3">
      <description>User-defined description of Range Modulator.</description>
    </entry>
    <entry group="300A" element="034C" name="&gt;&gt;Beam Current Modulation ID" type="1C">
      <description>User-supplied identifier for the beam current modulation pattern. Required if Range Modulator Type (300A,0348) is WHL_MODWEIGHTS</description>
    </entry>
    <include ref="&gt;Include Patient Support Identification Macro Table C.8.8.28-1"/>
    <entry group="300A" element="0356" name="&gt;Fixation Light Azimuthal Angle" type="3">
      <description>Azimuthal angle (degrees) of the fixation light coordinate around IEC BEAM LIMITING DEVICE Y-axis. Used for eye treatments. See section C.8.8.25.6.4.</description>
    </entry>
    <entry group="300A" element="0358" name="&gt;Fixation Light Polar Angle" type="3">
      <description>Polar angle (degrees) of the fixation light coordinate. Used for eye treatments. See section C.8.8.25.6.4.</description>
    </entry>
    <entry group="300A" element="010E" name="&gt;Final Cumulative Meterset Weight" type="1C">
      <description>Value of Cumulative Meterset Weight (300A,0134) for final Control Point in Ion Control Point Sequence (300A,03A8). Required if Cumulative Meterset Weight is non-null in Control Points specified within Ion Control Point Sequence. See section C.8.8.14.1.</description>
    </entry>
    <entry group="300A" element="0110" name="&gt;Number of Control Points" type="1">
      <description>Number of control points in Beam. Value shall be greater than or equal to 2.</description>
    </entry>
    <entry group="300A" element="03A8" name="&gt;Ion Control Point Sequence" type="1">
      <description>Introduces sequence of machine configurations describing Ion treatment beam. The number of items shall be identical to the value of Number of Control Points (300A,0110). See C.8.8.25.7.</description>
      <section ref="C.8.8.25.7" name="">The control point sequence for RT Ion Beams is defined using the same rule set as in the RT Beams module (see Section C.8.8.14.5 Control Point Sequence). Specifically, the following rules apply:
</section>
    </entry>
    <entry group="300A" element="0112" name="&gt;&gt;Control Point Index" type="1">
      <description>Index of current Control Point, starting at 0 for first Control Point.</description>
    </entry>
    <entry group="300A" element="0134" name="&gt;&gt;Cumulative Meterset Weight" type="2">
      <description>Cumulative weight to current control point. Cumulative Meterset Weight for the first item in Control Point Sequence shall always be zero. Cumulative Meterset Weight for the final item in Ion Control Point Sequence shall always be equal to Final Cumulative Meterset Weight.</description>
    </entry>
    <entry group="300C" element="0050" name="&gt;&gt;Referenced Dose Reference Sequence" type="3">
      <description>Introduces a sequence of Dose References for current Beam. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;&gt;&gt;Referenced Dose Reference Number" type="1">
      <description>Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module.</description>
    </entry>
    <entry group="300A" element="010C" name="&gt;&gt;&gt;Cumulative Dose Reference Coefficient" type="2">
      <description>Coefficient used to calculate cumulative dose contribution from this Beam to the referenced Dose Reference at the current Control Point.</description>
    </entry>
    <entry group="300A" element="0114" name="&gt;&gt;Nominal Beam Energy" type="1C">
      <description>Nominal Beam Energy at control point in MeV per nucleon. Defined at nozzle entrance before all Beam Modifiers. Required for first item of Control Point Sequence, or if Nominal Beam Energy changes during Beam, and KVp (0018,0060) is not present.</description>
    </entry>
    <entry group="0018" element="0060" name="&gt;&gt;KVp" type="1C">
      <description>Peak kilo voltage output of the setup X-Ray generator to be used. Required for first item of Control Point Sequence, or if KVp changes during setup, and Nominal Beam Energy (300A,0114) is not present.</description>
    </entry>
    <entry group="300A" element="035A" name="&gt;&gt;Meterset Rate" type="3">
      <description>Specifies the speed of delivery of the specified dose in units specified by Primary Dosimeter Unit (300A,00B3) per minute.</description>
    </entry>
    <entry group="300A" element="03AC" name="&gt;&gt;Ion Wedge Position Sequence" type="1C">
      <description>Introduces sequence of Wedge positions for current control point.
Required for first item of Ion Control Point Sequence if Number of Wedges (300A,00D0) is non-zero, and in subsequent control points if Wedge Position (300A,0118) or Wedge Thin Edge Position (300A,00DB) changes during beam.
The number of items shall be identical to the value of Number of Wedges (300A,00D0).</description>
    </entry>
    <entry group="300C" element="00C0" name="&gt;&gt;&gt;Referenced Wedge Number" type="1">
      <description>Uniquely references Wedge described by Wedge Number (300A,00D2) in Wedge Sequence (300A,00D1).</description>
    </entry>
    <entry group="300A" element="0118" name="&gt;&gt;&gt;Wedge Position" type="1">
      <description>Position of Wedge at current Control Point.
Enumerated Values:
IN
OUT</description>
    </entry>
    <entry group="300A" element="00DB" name="&gt;&gt;&gt;Wedge Thin Edge Position" type="1C">
      <description>Closest distance from the central axis of the beam along a wedge axis to the thin edge as projected to the machine isocentric plane (mm). Value is positive is the wedge does not cover the central axis, negative if it does. Required if Wedge Type (300A,00D3) of the wedge referenced by Referenced Wedge Number (300C,00C0) is PARTIAL_STANDARD or PARTIAL_MOTORIZ. See section C.8.8.25.6.4.</description>
    </entry>
    <entry group="300A" element="0360" name="&gt;&gt;Range Shifter Settings Sequence" type="1C">
      <description>Introduces sequence of Range Shifter settings for the current control point. One or more items shall be included in this sequence. Required for first item of Control Point Sequence if Number of Range Shifters (300A,0312) is non-zero, or if Range Shifter Setting (300A,0362) changes during Beam.</description>
    </entry>
    <entry group="300C" element="0100" name="&gt;&gt;&gt;Referenced Range Shifter Number" type="1">
      <description>Uniquely references Range Shifter described by Range Shifter Number (300A,0316) in Range Shifter Sequence (300A,0314).</description>
    </entry>
    <entry group="300A" element="0362" name="&gt;&gt;&gt;Range Shifter Setting" type="1">
      <description>Machine specific setting attribute for the range shifter. The specific encoding of this value should be documented in a Conformance Statement. See section C.8.8.25.5.</description>
    </entry>
    <entry group="300A" element="0364" name="&gt;&gt;&gt;Isocenter to Range Shiffter Distance" type="3">
      <description>Isocenter to downstream edge of range shifter (mm) at current control point. See section C.8.8.25.4</description>
    </entry>
    <entry group="300A" element="0366" name="&gt;&gt;&gt;Range Shifter Water Equivalent Thickness" type="3">
      <description>Water equivalent thickness (in mm) of the range shifter at the central axis for the beam energy incident upon the device.</description>
    </entry>
    <entry group="300A" element="0370" name="&gt;&gt;Lateral Spreading Device Settings Sequence" type="1C">
      <description>Introduces sequence of Lateral Spreading Device settings for the current control point. One or more items shall be included in this sequence. Required for first item of Control Point Sequence if Number of Lateral Spreading Devices (300A,0330) is non-zero, or if Lateral Spreading Device Setting (300A,0372) changes during Beam.</description>
    </entry>
    <entry group="300C" element="0102" name="&gt;&gt;&gt;Referenced Lateral Spreading Device Number" type="1">
      <description>Uniquely references Lateral Spreading Device described by Lateral Spreading Device Number (300A,0334) in Lateral Spreading Device Sequence (300A,0332).</description>
    </entry>
    <entry group="300A" element="0372" name="&gt;&gt;&gt;Lateral Spreading Device Setting" type="1">
      <description>Machine specific setting attribute for the lateral spreading device. The specific encoding of this value should be documented in a Conformance Statement. See section C.8.8.25.5.</description>
    </entry>
    <entry group="300A" element="0374" name="&gt;&gt;&gt;Isocenter to Lateral Spreading Device Distance" type="3">
      <description>Isocenter to downstream edge of Lateral Spreading Device (mm) at current control point. See section C.8.8.25.4</description>
    </entry>
    <entry group="300A" element="033C" name="&gt;&gt;&gt;Lateral Spreading Device Water Equivalent Thickness" type="3">
      <description>Water equivalent thickness (in mm) of the lateral spreading device at the central axis for the beam energy incident upon the device.</description>
    </entry>
    <entry group="300A" element="0380" name="&gt;&gt;Range Modulator Settings Sequence" type="1C">
      <description>Introduces sequence of Range Modulator Settings for current control point. One or more items shall be included in this sequence. Required for first item of Control Point Sequence if Number of Range Modulators (300A,0340) is non-zero, or if Range Modulator Setting changes during Beam.</description>
    </entry>
    <entry group="300C" element="0104" name="&gt;&gt;&gt;Referenced Range Modulator Number" type="1">
      <description>Uniquely references Range Modulator described by Range Modulator Number (300A,0344) in Range Modulator Sequence (300A,0342).</description>
    </entry>
    <entry group="300A" element="0382" name="&gt;&gt;&gt;Range Modulator Gating Start Value" type="1C">
      <description>Start position defines the range modulator position at which the beam is switched on. Required if Range Modulator Type (300A,0348) of the range modulator referenced by Referenced Range Modulator Number (300C,0104) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS</description>
    </entry>
    <entry group="300A" element="0384" name="&gt;&gt;&gt;Range Modulator Gating Stop Value" type="1C">
      <description>Stop position defines the range modulator position at which the beam is switched off. Required if Range Modulator Type (300A,0348) of the range modulator referenced by Referenced Range Modulator Number (300C,0104) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS</description>
    </entry>
    <entry group="300A" element="0386" name="&gt;&gt;&gt;Range Modulator Gating Start Water Equivalent Thickness" type="3">
      <description>If Range Modulator Type (300A,0348) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS:
Water equivalent thickness (in mm) of the range modulator at the position specified by Range Modulator Gating Start Value (300A,0382).
If Range Modulator Type (300A,0348) is FIXED:
Minimum water equivalent thickness (in mm) of the range modulator.</description>
    </entry>
    <entry group="300A" element="0388" name="&gt;&gt;&gt;Range Modulator Gating Stop Water Equivalent Thickness" type="3">
      <description>If Range Modulator Type (300A,0348) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS:
Water equivalent thickness (in mm) of the range modulator at the position specified by Range Modulator Gating Stop Value (300A,0384).
If Range Modulator Type (300A,0348) is FIXED:
Maximum water equivalent thickness (in mm) of the range modulator.</description>
    </entry>
    <entry group="300A" element="038A" name="&gt;&gt;&gt;Isocenter to Range Modulator Distance" type="3">
      <description>Isocenter to downstream edge of range modulator (mm) at current control point. See section C.8.8.25.4</description>
    </entry>
    <include ref="&gt;&gt;Include Beam Limiting Device Position Macro Table C.8.8.27-1"/>
    <entry group="300A" element="011E" name="&gt;&gt;Gantry Angle" type="1C">
      <description>Gantry angle of radiation source, i.e. orientation of IEC GANTRY coordinate system with respect to IEC FIXED REFERENCE coordinate system (degrees). Required for first item of Control Point Sequence, or if Gantry Angle changes during Beam.</description>
    </entry>
    <entry group="300A" element="011F" name="&gt;&gt;Gantry Rotation Direction" type="1C">
      <description>Direction of Gantry Rotation when viewing gantry from isocenter, for segment following Control Point. Required for first item of Control Point Sequence, or if Gantry Rotation Direction changes during Beam. See section C.8.8.14.8.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
    </entry>
    <entry group="300A" element="014A" name="&gt;&gt;Gantry Pitch Angle" type="2C">
      <description>Gantry Pitch Angle of the radiation source, i.e. the rotation of the IEC GANTRY coordinate system about the X-axis of the IEC GANTRY coordinate system (degrees). Required for first item of Control Point Sequence, or if Gantry Pitch Rotation Angle changes during Beam. See C.8.8.25.6.5.</description>
      <section ref="C.8.8.25.6.5" name="">The Gantry Pitch angle is not defined in IEC 61217. This angle is defined in the DICOM standard in a way compatible with the current notion of IEC by introducing it as rotation of the IEC GANTRY System as indicated below.
The Gantry Pitch Angle is defined as the rotation of the coordinate axes Yg, Zg about axis Xg by an angle g; see Figure C.8.8.25-7. An increase in the value of angle g corresponds to the clockwise rotation as viewed from the isocenter along the positive Xg axis


Figure C.8.8.25-7 Gantry Pitch Angle
</section>
    </entry>
    <entry group="300A" element="014C" name="&gt;&gt;Gantry Pitch Rotation Direction" type="2C">
      <description>Direction of Gantry Pitch Angle when viewing along the positive X-axis of the IEC GANTRY coordinate system, for segment following Control Point. Required for first item of Control Point Sequence, or if Gantry Pitch Rotation Direction changes during Beam. See C.8.8.14.8 and C.8.8.25.6.5.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0120" name="&gt;&gt;Beam Limiting Device Angle" type="1C">
      <description>Beam Limiting Device angle, i.e. orientation of IEC BEAM LIMITING DEVICE coordinate system with respect to IEC GANTRY coordinate system (degrees). Required for first item of Control Point Sequence, or if Beam Limiting Device Angle changes during Beam.</description>
    </entry>
    <entry group="300A" element="0121" name="&gt;&gt;Beam Limiting Device Rotation Direction" type="1C">
      <description>Direction of Beam Limiting Device Rotation when viewing beam limiting device (collimator) from radiation source, for segment following Control Point. Required for first item of Control Point Sequence, or if Beam Limiting Device Rotation Direction changes during Beam. See section C.8.8.14.8.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
    </entry>
    <entry group="300A" element="0390" name="&gt;&gt;Scan Spot Tune ID" type="1C">
      <description>User-supplied or machine code identifier for machine configuration to produce beam spot. This may be the nominal spot size or some other machine specific value. Required if Scan Mode (300A,0308) is MODULATED.</description>
    </entry>
    <entry group="300A" element="0392" name="&gt;&gt;Number of Scan Spot Positions" type="1C">
      <description>Number of spot positions used to specify scanning pattern for current segment beginning at control point. Required if Scan Mode (300A,0308) is MODULATED.</description>
    </entry>
    <entry group="300A" element="0394" name="&gt;&gt;Scan Spot Position Map" type="1C">
      <description>The x and y coordinates of the scan spots are defined as projected onto the machine isocentric plane in the IEC GANTRY coordinate system (mm). Required if Scan Mode (300A,0308) is MODULATED. Contains 2N values where N is the Number of Scan Spot Positions (300A,0392).</description>
    </entry>
    <entry group="300A" element="0396" name="&gt;&gt;Scan Spot Meterset Weights" type="1C">
      <description>A data set of meterset weights corresponding to scan spot positions. The order of weights matches the positions in Scan Spot Positions (300A,0394). The sum contained in all meterset weights shall match the difference of the cumulative meterset weight of the current control point to the following control point. Required if Scan Mode (300A,0308) is MODULATED.</description>
    </entry>
    <entry group="300A" element="0398" name="&gt;&gt;Scanning Spot Size" type="3">
      <description>The Scanning Spot Size as calculated using the Full Width Half Maximum (FWHM). Specified by a numeric pair - the size measured in air at isocenter in IEC GANTRY X direction followed by the size in the IEC GANTRY Y direction (mm).</description>
    </entry>
    <entry group="300A" element="039A" name="&gt;&gt;Number of Paintings" type="1C">
      <description>The number of times the scan pattern given by Scan Spot Position Map (300A,0394) and Scan Spot Meterset Weights (300A,0396) shall be applied at the current control point. To obtain the meterset weight per painting, the values in the Scan Spot Meterset Weights (300A,0396) should be divided by the value of this attribute. Required if Scan Mode (300A,0308) is MODULATED.</description>
    </entry>
    <entry group="300A" element="0122" name="&gt;&gt;Patient Support Angle" type="1C">
      <description>Patient Support angle, i.e. orientation of IEC PATIENT SUPPORT (turntable) coordinate system with respect to IEC FIXED REFERENCE coordinate system (degrees). Required for first item of Control Point Sequence, or if Patient Support Angle changes during Beam.</description>
    </entry>
    <entry group="300A" element="0123" name="&gt;&gt;Patient Support Rotation Direction" type="1C">
      <description>Direction of Patient Support Rotation when viewing table from above, for segment following Control Point. Required for first item of Control Point Sequence, or if Patient Support Rotation Direction changes during Beam. See section C.8.8.14.8.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
    </entry>
    <entry group="300A" element="0140" name="&gt;&gt;Table Top Pitch Angle" type="2C">
      <description>Table Top Pitch Angle, i.e. the rotation of the IEC TABLE TOP coordinate system about the X-axis of the IEC TABLE TOP coordinate system (degrees). Required for first item of Control Point Sequence, or if Table Top Pitch Angle changes during Beam. See section C.8.8.25.6.2.</description>
    </entry>
    <entry group="300A" element="0142" name="&gt;&gt;Table Top Pitch Rotation Direction" type="2C">
      <description>Direction of Table Top Pitch Rotation when viewing the table along the positive X-axis of the IEC TABLE TOP coordinate system, for segment following Control Point. Required for first item of Control Point Sequence, or if Table Top Pitch Rotation Direction changes during Beam. See C.8.8.14.8 and C.8.8.25.6.2.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0144" name="&gt;&gt;Table Top Roll Angle" type="2C">
      <description>Table Top Roll Angle, i.e. the rotation of the IEC TABLE TOP coordinate system about the Y-axis of the IEC TABLE TOP coordinate system (degrees). Required for first item of Control Point Sequence, or if Table Top Roll Angle changes during Beam. See section C.8.8.25.6.2.</description>
    </entry>
    <entry group="300A" element="0146" name="&gt;&gt;Table Top Roll Rotation Direction" type="2C">
      <description>Direction of Table Top Roll Rotation when viewing the table along the positive Y-axis of the IEC TABLE TOP coordinate system, for segment following Control Point. Required for first item of Control Point Sequence, or if Table Top Roll Rotation Direction changes during Beam. See C.8.8.14.8 and C.8.8.25.6.2.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation.</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0148" name="&gt;&gt;Head Fixation Angle" type="3">
      <description>Angle (in degrees) of the head fixation for eye treatments with respect to the Table Top Pitch Angle (300A,0140) coordinate system. Positive head fixation angle is the same direction as positive Table Top pitch. See section C.8.8.25.6.4.</description>
    </entry>
    <entry group="300A" element="0128" name="&gt;&gt;Table Top Vertical Position" type="2C">
      <description>Table Top Vertical position in IEC TABLE TOP coordinate system (mm). Required for first item of Control Point Sequence, or if Table Top Vertical Position changes during Beam. See section C.8.8.14.6.</description>
    </entry>
    <entry group="300A" element="0129" name="&gt;&gt;Table Top Longitudinal Position" type="2C">
      <description>Table Top Longitudinal position in IEC TABLE TOP coordinate system (mm). Required for first item of Control Point Sequence, or if Table Top Longitudinal Position changes during Beam. See section C.8.8.14.6.</description>
    </entry>
    <entry group="300A" element="012A" name="&gt;&gt;Table Top Lateral Position" type="2C">
      <description>Table Top Lateral position in IEC TABLE TOP coordinate system (mm). Required for first item of Control Point Sequence, or if Table Top Lateral Position changes during Beam. See section C.8.8.14.6.</description>
    </entry>
    <entry group="300A" element="030D" name="&gt;&gt;Snout Position" type="2C">
      <description>Axial position of the snout (in mm) measured from isocenter to the downstream side of the snout (without consideration of variable length elements such as blocks, MLC and/or compensators). Required for first item in Control Point Sequence, or if Snout Position changes during Beam.</description>
    </entry>
    <entry group="300A" element="012C" name="&gt;&gt;Isocenter Position" type="2C">
      <description>Isocenter coordinates (x,y,z) in the patient based coordinate system described in C.7.6.2.1.1 (mm). Required for first item of Segment Control Point Sequence, or if Segment Isocenter Position changes during Beam.</description>
    </entry>
    <entry group="300A" element="012E" name="&gt;&gt;Surface Entry Point" type="3">
      <description>Patient surface entry point coordinates (x,y,z), along the central axis of the beam, in the patient based coordinate system described in C.7.6.2.1.1 (mm).</description>
    </entry>
  </module>
  <module ref="C.8.8.26" table="C.8.8.26-1" name="RT Ion Beams Session Record Module Attributes">
    <entry group="0008" element="1070" name="Operators' Name" type="2">
      <description>Name of operator administering treatment session.</description>
    </entry>
    <entry group="300C" element="0022" name="Referenced Fraction Group Number" type="3">
      <description>Identifier of fraction group within referenced RT Ion Plan.</description>
    </entry>
    <entry group="300A" element="0078" name="Number of Fractions Planned" type="2">
      <description>Total number of treatments (fractions) planned for current fraction group.</description>
    </entry>
    <entry group="300A" element="00B3" name="Primary Dosimeter Unit" type="1">
      <description>Measurement unit of the machine dosimeter.
Enumerated Values:
MU = Monitor Units
NP = Number of Particles</description>
    </entry>
    <entry group="3008" element="0021" name="Treatment Session Ion Beam Sequence" type="1">
      <description>Introduces sequence of setup and/or treatment beams administered during treatment session. One or more items shall be included in this sequence.</description>
    </entry>
    <entry group="300C" element="0006" name="&gt;Referenced Beam Number" type="1">
      <description>References Beam specified by Beam Number (300A,00C0) in Ion Beam Sequence (300A,03A2) in RT Ion Beams Module within the referenced RT Ion Plan.</description>
    </entry>
    <entry group="300A" element="00C2" name="&gt;Beam Name" type="1">
      <description>User-defined name for Beam. See section C.8.8.25.1.</description>
    </entry>
    <entry group="300A" element="00C3" name="&gt;Beam Description" type="3">
      <description>User-defined description for Beam. See section C.8.8.25.1.</description>
    </entry>
    <entry group="300A" element="00C4" name="&gt;Beam Type" type="1">
      <description>Motion characteristic of Beam.
Enumerated Values:
STATIC = all beam parameters remain unchanged during delivery
DYNAMIC = one or more beam parameters changes during delivery</description>
    </entry>
    <entry group="300A" element="00C6" name="&gt;Radiation Type" type="1">
      <description>Particle type of Beam.
Defined Terms:
PHOTON
PROTON
ION</description>
    </entry>
    <entry group="300A" element="0302" name="&gt;Radiation Mass Number" type="1C">
      <description>Mass number of radiation. Required if Radiation Type (300A,00C6) is ION</description>
    </entry>
    <entry group="300A" element="0304" name="&gt;Radiation Atomic Number" type="1C">
      <description>Atomic number of radiation. Required if Radiation Type (300A,00C6) is ION</description>
    </entry>
    <entry group="300A" element="0306" name="&gt;Radiation Charge State" type="1C">
      <description>Charge state of radiation. Required if Radiation Type (300A,00C6) is ION</description>
    </entry>
    <entry group="300A" element="0308" name="&gt;Scan Mode" type="1">
      <description>The method of beam scanning used during treatment.
Defined Terms:
NONE = No beam scanning is performed.
UNIFORM = The beam is scanned between control points to create a uniform lateral fluence distribution across the field.
MODULATED = The beam is scanned between control points to create a modulated lateral fluence distribution across the field.</description>
    </entry>
    <entry group="300C" element="00A0" name="&gt;Referenced Tolerance Table Number" type="3">
      <description>Uniquely identifies Ion Tolerance Table specified by Tolerance Table Number (300A,0042) within Ion Tolerance Table Sequence in RT Ion Tolerance Tables Module. These tolerances are to be used for verification of treatment machine settings.</description>
    </entry>
    <entry group="3008" element="00A0" name="&gt;Beam Limiting Device Leaf Pairs Sequence" type="3">
      <description>Introduces sequence of beam limiting device (collimator) jaw or leaf (element) sets. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00B8" name="&gt;&gt;RT Beam Limiting Device Type" type="1">
      <description>Type of beam limiting device (collimator).
Enumerated Values:
X = symmetric jaw pair in IEC X direction
Y = symmetric jaw pair in IEC Y direction
ASYMX = asymmetric jaw pair in IEC X direction
ASYMY = asymmetric pair in IEC Y direction
MLCX = multileaf (multi-element) jaw pair in IEC X direction
MLCY = multileaf (multi-element) jaw pair in IEC Y direction</description>
    </entry>
    <entry group="300A" element="00BC" name="&gt;&gt;Number of Leaf/Jaw Pairs" type="1">
      <description>Number of leaf (element) or jaw pairs (equal to 1 for standard beam limiting device jaws).</description>
    </entry>
    <entry group="300C" element="006A" name="&gt;Referenced Patient Setup Number" type="3">
      <description>Uniquely identifies Ion Patient Setup to be used for current beam, specified by Patient Setup Number (300A,0182) within Patient Setup Sequence of RT Patient Setup Module.</description>
    </entry>
    <entry group="300C" element="0040" name="&gt;Referenced Verification Image Sequence" type="3">
      <description>Introduces sequence of verification images obtained during delivery of current beam. One or more items may be included in this sequence. See C.8.8.14.2.</description>
      <section ref="C.8.8.14.2" name="">The Planned Verification Image Sequence (300A,00CA) contains attributes which describe the planned verification images to be acquired during current beam. The Start Cumulative Meterset Weight (300C,0008) specifies the Cumulative Meterset Weight at which image acquisition is to begin. If Meterset Exposure (3002,0032) is present in a sequence item and End Cumulative Meterset Weight (300C,0009) is not present then a single image shall be acquired using the meterset duration specified in Meterset Exposure (3002,0032). If End Cumulative Meterset Weight (300C,0009) is present in a sequence item and Meterset Exposure (3002,0032) is not present then a single image shall be acquired over the beam delivery from Start Cumulative Meterset Weight (300C,0008) to End Cumulative Meterset Weight (300C,0009). If both Meterset Exposure (3002,0032) and End Cumulative Meterset Weight (300C,0009) are present in a sequence item then images shall be acquired every Meterset Exposure (3002,0032) from Start Cumulative Meterset Weight (300C,0008) to End Cumulative Meterset Weight (300C,0009). No images shall extend past End Cumulative Meterset Weight (300C,0009).
</section>
    </entry>
    <include ref="&gt;&gt;Include SOP Instance Reference Macro Table 10-11"/>
    <entry group="3008" element="0080" name="&gt;Referenced Measured Dose Reference Sequence" type="3">
      <description>Introduces sequence of doses measured during treatment delivery for current Beam. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely references Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Ion Plan. Required if Referenced Measured Dose Reference Number (3008,0082) is not sent.</description>
    </entry>
    <entry group="3008" element="0082" name="&gt;&gt;Referenced Measured Dose Reference Number" type="1C">
      <description>Uniquely references Measured Dose Reference specified by Measured Dose Reference Number (3008,0064) in Measured Dose Reference Sequence (3008,0010). Required if Referenced Dose Reference Number (300C,0051) is not sent.</description>
    </entry>
    <entry group="3008" element="0016" name="&gt;&gt;Measured Dose Value" type="1">
      <description>Measured Dose in units specified by Dose Units (3004,0002) in sequence referenced by Measured Dose Reference Sequence (3008,0010) or Dose Reference Sequence (300A,0010) in RT Prescription Module of Referenced RT Ion Plan as defined above.</description>
    </entry>
    <entry group="3008" element="0090" name="&gt;Referenced Calculated Dose Reference Sequence" type="3">
      <description>Introduces sequence of doses estimated for each treatment delivery. The sequence may contain one or more items.</description>
    </entry>
    <entry group="300C" element="0051" name="&gt;&gt;Referenced Dose Reference Number" type="1C">
      <description>Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module of referenced RT Ion Plan. Required if Referenced Calculated Dose Reference Number (3008,0092) is not sent.</description>
    </entry>
    <entry group="3008" element="0092" name="&gt;&gt;Referenced Calculated Dose Reference Number" type="1C">
      <description>Uniquely identifies Calculated Dose Reference specified by Calculated Dose Reference Number (3008,0072) within Calculated Dose Reference Sequence (3008,0070). Required if Referenced Dose Reference Number (300C,0051) is not sent.</description>
    </entry>
    <entry group="3008" element="0076" name="&gt;&gt;Calculated Dose Reference Dose Value" type="1">
      <description>Calculated Dose (Gy).</description>
    </entry>
    <entry group="300A" element="00D0" name="&gt;Number of Wedges" type="1">
      <description>Number of wedges associated with current beam.</description>
    </entry>
    <entry group="3008" element="00B0" name="&gt;Recorded Wedge Sequence" type="1C">
      <description>Introduces sequence of treatment wedges. Required if Number of Wedges (300A,00D0) is non-zero. One or more items may be included in this sequence. The number of items shall be identical to the value of Number of Wedges (300A,00D0).</description>
    </entry>
    <entry group="300A" element="00D2" name="&gt;&gt;Wedge Number" type="1">
      <description>Identification number of the Wedges. The value of Wedge Number (300A,00D2) shall be unique within the Beam in which it was created.</description>
    </entry>
    <entry group="300A" element="00D3" name="&gt;&gt;Wedge Type" type="2">
      <description>Type of wedge (if any) defined for Beam.
Defined Terms:
STANDARD = standard (static) wedge
MOTORIZED = single wedge that can be removed from beam remotely.
PARTIAL_STANDARD = wedge does not extend across the whole field and is operated manually.
PARTIAL_MOTORIZ = wedge does not extend across the whole field and can be removed from beam remotely.</description>
    </entry>
    <entry group="300A" element="00D4" name="&gt;&gt;Wedge ID" type="3">
      <description>User-supplied identifier for Wedge.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="00D5" name="&gt;&gt;Wedge Angle" type="2">
      <description>Nominal wedge angle (degrees).</description>
    </entry>
    <entry group="300A" element="00D8" name="&gt;&gt;Wedge Orientation" type="2">
      <description>Orientation of wedge, i.e. orientation of IEC WEDGE FILTER coordinate system with respect to the IEC BEAM LIMITING DEVICE coordinate systems (degrees).</description>
    </entry>
    <entry group="300A" element="00E0" name="&gt;Number of Compensators" type="1">
      <description>Number of range compensators associated with current Beam.</description>
    </entry>
    <entry group="3008" element="00C0" name="&gt;Recorded Compensator Sequence" type="1C">
      <description>Introduces sequence of treatment compensators. Required if Number of Compensators (300A,00E0) is non-zero. One or more items may be included in this sequence. The number of items shall be identical to the value of Number of Compensators (300A,00E0).</description>
    </entry>
    <entry group="300C" element="00D0" name="&gt;&gt;Referenced Compensator Number" type="1">
      <description>Uniquely identifies compensator specified by Compensator Number (300A,00E4) within Beam referenced by Referenced Beam Number (300C,0006).</description>
    </entry>
    <entry group="300A" element="00E5" name="&gt;&gt;Compensator ID" type="3">
      <description>User-supplied identifier for compensator.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="00ED" name="&gt;Number of Boli" type="1">
      <description>Number of boli associated with current Beam.</description>
    </entry>
    <entry group="300C" element="00B0" name="&gt;Referenced Bolus Sequence" type="1C">
      <description>Introduces sequence of boli associated with Beam. Required if Number of Boli (300A,00ED) is non-zero. One or more items may be included in this sequence. The number of items shall be identical to the value of Number of Boli (300A,00ED).</description>
    </entry>
    <entry group="3006" element="0084" name="&gt;&gt;Referenced ROI Number" type="1">
      <description>Uniquely identifies ROI representing the Bolus specified by ROI Number (3006,0022) in Structure Set ROI Sequence (3006,0020) in Structure Set Module within RT Structure Set in Referenced Structure Set Sequence (300C,0060) in RT General Plan Module.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="00F0" name="&gt;Number of Blocks" type="1">
      <description>Number of shielding blocks associated with Beam.</description>
    </entry>
    <entry group="3008" element="00D0" name="&gt;Recorded Block Sequence" type="1C">
      <description>Introduces sequence of blocks associated with Beam. Required if Number of Blocks (300A,00F0) is non-zero. One or more items may be included in this sequence. The number of items shall be identical to the value of Number of Blocks (300A,00F0).</description>
    </entry>
    <entry group="300A" element="00F5" name="&gt;&gt;Block Tray ID" type="3">
      <description>User-supplied identifier for block tray.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300C" element="00E0" name="&gt;&gt;Referenced Block Number" type="1">
      <description>Uniquely identifies block specified by Block Number (300A,00FC) within Beam referenced by Referenced Beam Number (300C,0006).</description>
    </entry>
    <entry group="300A" element="00FE" name="&gt;&gt;Block Name" type="3">
      <description>User-defined name for block.</description>
    </entry>
    <entry group="3008" element="00F0" name="&gt;Recorded Snout Sequence" type="1C">
      <description>Introduces sequence of Snouts associated with Beam.
Required if Snout Sequence (300A,030C) is included in the RT Ion Plan referenced within the Referenced RT Plan Sequence (300C,0002).
Only a single item shall be permitted in this sequence.</description>
    </entry>
    <entry group="300A" element="030F" name="&gt;&gt;Snout ID" type="1">
      <description>User or machine supplied identifier for Snout.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="0107" name="&gt;Applicator Sequence" type="1C">
      <description>Introduces sequence of Applicators associated with Beam.
Required if Applicator Sequence (300A,0107) is included in the RT Ion Plan referenced within the Referenced RT Plan Sequence (300C,0002).
Only a single item shall be permitted in this sequence.</description>
    </entry>
    <entry group="300A" element="0108" name="&gt;&gt;Applicator ID" type="1">
      <description>User or machine supplied identifier for Applicator. See C.8.8.14.12</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="0109" name="&gt;&gt;Applicator Type" type="1">
      <description>Type of applicator.

Defined Terms:
ION_SQUARE = square ion applicator
ION_RECT = rectangluar ion applicator
ION_CIRC = circular ion applicator
ION_SHORT = short ion applicator
ION_OPEN = open (dummy) ion applicator
INTEROPERATIVE = interoperative (custom) applicator
STEREOTACTIC = stereotactic applicator</description>
    </entry>
    <entry group="300A" element="010A" name="&gt;&gt;Applicator Description" type="3">
      <description>User-defined description for Applicator.</description>
    </entry>
    <entry group="300A" element="0420" name="&gt;General Accessory Sequence" type="3">
      <description>Introduces a Sequence of General Accessories associated with this Beam. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="300A" element="0424" name="&gt;&gt;General Accessory Number" type="1">
      <description>Identification Number of the General Accessory. The value shall be unique within the sequence.</description>
    </entry>
    <entry group="300A" element="0421" name="&gt;&gt;General Accessory ID" type="1">
      <description>User or machine supplied identifier for General Accessory.</description>
    </entry>
    <entry group="300A" element="0422" name="&gt;&gt;General Accessory Description" type="3">
      <description>User supplied description of General Accessory.</description>
    </entry>
    <entry group="300A" element="0423" name="&gt;&gt;General Accessory Type" type="3">
      <description>Specifies the type of accessory.
Defined Terms:
GRATICULE = Accessory tray with a radio-opaque grid
IMAGE_DETECTOR = Image acquisition device positioned in the beam line
RETICLE = Accessory tray with radio-transparent markers or grid</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>Machine-readable identifier for this accessory</description>
    </entry>
    <entry group="300A" element="0312" name="&gt;Number of Range Shifters" type="1">
      <description>Number of range shifters associated with current beam.</description>
    </entry>
    <entry group="3008" element="00F2" name="&gt;Recorded Range Shifter Sequence" type="1C">
      <description>Introduces sequence of range shifters recorded with Beam. Required if Number of Range Shifters (300A,0312) is non-zero. One or more items may be included in this sequence. The number of items shall be identical to the value of Number of Range Shifters (300A,0312).</description>
    </entry>
    <entry group="300C" element="0100" name="&gt;&gt;Referenced Range Shifter Number" type="1">
      <description>Uniquely identifies range shifter specified by Range Shifter Number (300A,0316) within Beam referenced by Referenced Beam Number (300C,0006).</description>
    </entry>
    <entry group="300A" element="0318" name="&gt;&gt;Range Shifter ID" type="1">
      <description>User or machine supplied identifier for Range Modulator.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="0330" name="&gt;Number of Lateral Spreading Devices" type="1">
      <description>Number of lateral spreading devices associated with current beam.</description>
    </entry>
    <entry group="3008" element="00F4" name="&gt;Recorded Lateral Spreading Device Sequence" type="1C">
      <description>Introduces sequence of lateral spreading devices associated with Beam. Required if Number of Lateral Spreading Devices (300A,0330) is non-zero. One or more items may be included in this sequence. The number of items shall be identical to the value of Number of Lateral Spreading Devices (300A,0330).</description>
    </entry>
    <entry group="300C" element="0102" name="&gt;&gt;Referenced Lateral Spreading Device Number" type="1">
      <description>Uniquely identifies lateral spreading device specified by Lateral Spreading Device Number (300A,0334) within Beam referenced by Referenced Beam Number (300C,0006).</description>
    </entry>
    <entry group="300A" element="0336" name="&gt;&gt;Lateral Spreading Device ID" type="1">
      <description>User or machine supplied identifier for Lateral Spreading Device.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="0340" name="&gt;Number of Range Modulators" type="1">
      <description>Number of range modulators associated with current beam.</description>
    </entry>
    <entry group="3008" element="00F6" name="&gt;Recorded Range Modulator Sequence" type="1C">
      <description>Introduces sequence of range modulators associated with Beam. Required if Number of Range Modulators (300A,0340) is non-zero. One or more items may be included in this sequence. The number of items shall be identical to the value of Number of Range Modulators (300A,0340).</description>
    </entry>
    <entry group="300C" element="0104" name="&gt;&gt;Referenced Range Modulator Number" type="1">
      <description>Uniquely identifies range modulator specified by Range Modulator Number (300A,0344) within Beam referenced by Referenced Beam Number (300C,0006).</description>
    </entry>
    <entry group="300A" element="0346" name="&gt;&gt;Range Modulator ID" type="1">
      <description>User or machine supplied identifier for Range Modulator.</description>
    </entry>
    <entry group="300A" element="00F9" name="&gt;&gt;Accessory Code" type="3">
      <description>An accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
    <entry group="300A" element="0348" name="&gt;&gt;Range Modulator Type" type="1">
      <description>Type of Range Modulator.
Defined Terms:
FIXED = fixed modulation width and weights using ridge filter or constant speed wheel with constant beam current
WHL_FIXEDWEIGHTS = selected wheel/track (Range Modulator ID) is spinning at constant speed. Modulation width is adjusted by switching constant beam current on and off at wheel steps indicated by Range Modulator Interrupt Values
WHL_MODWEIGHTS = selected wheel/track (Range Modulator ID) is spinning at constant speed. Weight per wheel step is adjusted by modulating beam current according to selected Beam Current Modulation ID (300A,034C)

Only one item in the Recorded Range Modulator Sequence (3008,00F6) can have a Range Modulator Type (300A,0348) of WHL_MODWEIGHTS.</description>
    </entry>
    <entry group="300A" element="034C" name="&gt;&gt;Beam Current Modulation ID" type="1C">
      <description>User-supplied identifier for the beam current modulation pattern. Required if Range Modulator Type (300A,0348) is WHL_MODWEIGHTS</description>
    </entry>
    <include ref="&gt;Include Patient Support Identification Macro Table C.8.8.28-1"/>
    <entry group="300A" element="0356" name="&gt;Fixation Light Azimuthal Angle" type="3">
      <description>Azimuthal angle (degrees) of the fixation light coordinate around IEC PATIENT SUPPORT Y-axis. Used for eye treatments. See section C.8.8.25.6.4.</description>
    </entry>
    <entry group="300A" element="0358" name="&gt;Fixation Light Polar Angle" type="3">
      <description>Polar angle (degrees) of the fixation light coordinate. Used for eye treatments. See section C.8.8.25.6.4.</description>
    </entry>
    <entry group="3008" element="0022" name="&gt;Current Fraction Number" type="2">
      <description>Fraction number for this beam administration.</description>
    </entry>
    <entry group="300A" element="00CE" name="&gt;Treatment Delivery Type" type="2">
      <description>Delivery Type of treatment.
Defined Terms:
TREATMENT = normal patient treatment
OPEN_PORTFILM = portal image acquisition with open field (the source of radiation is specified by Radiation Type (300A,00C6))
TRMT_PORTFILM = portal image acquisition with treatment port (the source of radiation is specified by Radiation Type (300A,00C6))
CONTINUATION = continuation of interrupted treatment
SETUP = no treatment beam was applied for this RT Beam. To be used for specifying the gantry, couch, and other machine positions where X-Ray set-up images or measurements were taken.</description>
    </entry>
    <entry group="3008" element="002A" name="&gt;Treatment Termination Status" type="1">
      <description>Conditions under which treatment was terminated.
Enumerated Values:
NORMAL = treatment terminated normally
OPERATOR = operator terminated treatment
MACHINE = machine terminated treatment
UNKNOWN = status at termination unknown</description>
    </entry>
    <entry group="3008" element="002B" name="&gt;Treatment Termination Code" type="3">
      <description>Treatment machine termination code. This code is dependent upon the particular application and equipment.</description>
    </entry>
    <entry group="3008" element="002C" name="&gt;Treatment Verification Status" type="2">
      <description>Conditions under which treatment was verified by a verification system.
Enumerated Values:
VERIFIED = treatment verified
VERIFIED_OVR = treatment verified with at least one out-of-range value overridden
NOT_VERIFIED = treatment verified manually</description>
    </entry>
    <entry group="3008" element="0032" name="&gt;Specified Primary Meterset" type="3">
      <description>Desired machine setting of primary meterset in units specified by Primary Dosimeter Unit (300A,00B3).</description>
    </entry>
    <entry group="3008" element="0033" name="&gt;Specified Secondary Meterset" type="3">
      <description>Desired machine setting of secondary meterset.</description>
    </entry>
    <entry group="3008" element="0036" name="&gt;Delivered Primary Meterset" type="3">
      <description>Machine setting actually delivered as recorded by primary meterset in units specified by Primary Dosimeter Unit (300A,00B3).</description>
    </entry>
    <entry group="3008" element="0037" name="&gt;Delivered Secondary Meterset" type="3">
      <description>Machine setting actually delivered as recorded by secondary meterset.</description>
    </entry>
    <entry group="3008" element="003A" name="&gt;Specified Treatment Time" type="3">
      <description>Treatment Time set (sec).</description>
    </entry>
    <entry group="3008" element="003B" name="&gt;Delivered Treatment Time" type="3">
      <description>Treatment Time actually delivered (sec).</description>
    </entry>
    <entry group="300A" element="0110" name="&gt;Number of Control Points" type="1">
      <description>Number of control points in Beam.</description>
    </entry>
    <entry group="3008" element="0041" name="&gt;Ion Control Point Delivery Sequence" type="1">
      <description>Introduces sequence of beam control points for current ion treatment beam. One or more items may be included in this sequence. The number of items shall be identical to the value of Number of Control Points (300A,0110). See section C.8.8.21.1.</description>
    </entry>
    <entry group="300C" element="00F0" name="&gt;&gt;Referenced Control Point Index" type="1">
      <description>Uniquely identifies Control Point specified by Control Point Index (300A,0112) within the Beam referenced by Referenced Beam Number (300C,0006).</description>
    </entry>
    <entry group="3008" element="0024" name="&gt;&gt;Treatment Control Point Date" type="1">
      <description>Date administration of treatment beam began.</description>
    </entry>
    <entry group="3008" element="0025" name="&gt;&gt;Treatment Control Point Time" type="1">
      <description>Time administration of treatment beam began.</description>
    </entry>
    <entry group="3008" element="0042" name="&gt;&gt;Specified Meterset" type="2">
      <description>Desired machine setting for current control point in units specified by Primary Dosimeter Unit (300A,00B3).</description>
    </entry>
    <entry group="3008" element="0044" name="&gt;&gt;Delivered Meterset" type="1">
      <description>Machine setting actually delivered at current control point in units specified by Primary Dosimeter Unit (300A,00B3).</description>
    </entry>
    <entry group="3008" element="0045" name="&gt;&gt;Meterset Rate Set" type="3">
      <description>The specified speed of delivery of the specified dose in units specified by Primary Dosimeter Unit (300A,00B3) per minute.</description>
    </entry>
    <entry group="3008" element="0046" name="&gt;&gt;Meterset Rate Delivered" type="3">
      <description>The delivered speed of delivery of the specified dose in units specified by Primary Dosimeter Unit (300A,00B3) per minute.</description>
    </entry>
    <entry group="300A" element="0114" name="&gt;&gt;Nominal Beam Energy" type="1C">
      <description>Nominal Beam Energy at control point in MeV per nucleon. Defined at nozzle entrance before all Beam Modifiers. Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041) or if Nominal Beam Energy (300A,0114) changes during beam administration, and KVp (0018,0060) is not present.</description>
    </entry>
    <entry group="0018" element="0060" name="&gt;&gt;KVp" type="1C">
      <description>Peak kilo voltage output of the setup X-Ray generator used. Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041), or if KVp changes during setup, and Nominal Beam Energy (300A,0114) is not present.</description>
    </entry>
    <entry group="300A" element="03AC" name="&gt;&gt;Ion Wedge Position Sequence" type="1C">
      <description>Introduces sequence of Wedge positions for current control point.
Required for first item of Ion Control Point Sequence if Number of Wedges (300A,00D0) is non-zero, and in subsequent control points if Wedge Position (300A,0118) or Wedge Thin Edge Position (300A,00DB) changes during beam. One or more items may be included in this sequence. The number of items shall be identical to the value of Number of Wedges (300A,00D0).</description>
    </entry>
    <entry group="300C" element="00C0" name="&gt;&gt;&gt;Referenced Wedge Number" type="1">
      <description>Uniquely references Wedge described by Wedge Number (300A,00D2) in Wedge Sequence (300A,00D1).</description>
    </entry>
    <entry group="300A" element="0118" name="&gt;&gt;&gt;Wedge Position" type="1">
      <description>Position of Wedge at current control point.
Enumerated Values: IN, OUT.</description>
    </entry>
    <entry group="300A" element="00DB" name="&gt;&gt;&gt;Wedge Thin Edge Position" type="1C">
      <description>Closest distance from the central axis of the beam along a wedge axis to the thin edge as projected to the machine isocentric plane (mm). Value is positive is the wedge does not cover the central axis, negative if it does. Required if Wedge Type (300A,00D3) of the wedge referenced by Referenced Wedge Number (300C,00C0) is PARTIAL_STANDARD or PARTIAL_MOTORIZ. See section C.8.8.25.6.4.</description>
    </entry>
    <include ref="&gt;&gt;Include Beam Limiting Device Position Macro Table C.8.8.27-1"/>
    <entry group="300A" element="0360" name="&gt;&gt;Range Shifter Settings Sequence" type="1C">
      <description>Introduces sequence of Range Shifter settings for the current control point. One or more items may be included in this sequence. Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041) or if Range Shifter Setting (300A,0362) changes during beam administration, and Number of Range Shifters (300A,0312) is non-zero.</description>
    </entry>
    <entry group="300C" element="0100" name="&gt;&gt;&gt;Referenced Range Shifter Number" type="1">
      <description>Uniquely references Range Shifter described by Range Shifter Number (300A,0316) in Range Shifter Sequence (300A,0314).</description>
    </entry>
    <entry group="300A" element="0362" name="&gt;&gt;&gt;Range Shifter Setting" type="1">
      <description>Machine specific setting attribute for the range shifter. The specific encoding of this value should be documented in a Conformance Statement. See section C.8.8.25.5.</description>
    </entry>
    <entry group="300A" element="0370" name="&gt;&gt;Lateral Spreading Device Settings Sequence" type="1C">
      <description>Introduces sequence of Lateral Spreading Device settings for the current control point. One or more items may be included in this sequence. Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041) or if Lateral Spreading Device Setting (300A,0372) changes during beam administration, and Number of Lateral Spreading Devices (300A,0330) is non-zero.</description>
    </entry>
    <entry group="300C" element="0102" name="&gt;&gt;&gt;Referenced Lateral Spreading Device Number" type="1">
      <description>Uniquely references Lateral Spreading Device described by Lateral Spreading Device Number (300A,0334) in Lateral Spreading Device Sequence (300A,0332).</description>
    </entry>
    <entry group="300A" element="0372" name="&gt;&gt;&gt;Lateral Spreading Device Setting" type="1">
      <description>Machine specific setting attribute for the lateral spreading device. The specific encoding of this value should be documented in a Conformance Statement. See section C.8.8.25.5.</description>
    </entry>
    <entry group="300A" element="0380" name="&gt;&gt;Range Modulator Settings Sequence" type="1C">
      <description>Introduces sequence of Range Modulator Settings for current control point. One or more items may be included in this sequence.Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041), or if Range Modulator Settings change during beam administration, and Number of Range Modulators (300A,0340) is non-zero.</description>
    </entry>
    <entry group="300C" element="0104" name="&gt;&gt;&gt;Referenced Range Modulator Number" type="1">
      <description>Uniquely references Range Modulator described by Range Modulator Number (300A,0344) in Range Modulator Sequence (300A,0342).</description>
    </entry>
    <entry group="300A" element="0382" name="&gt;&gt;&gt;Range Modulator Gating Start Value" type="1C">
      <description>Start position defines the range modulator position at which the beam is switched on. Required if Range Modulator Type (300A,0348) of the range modulator referenced by Referenced Range Modulator Number (300C,0104) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS</description>
    </entry>
    <entry group="300A" element="0384" name="&gt;&gt;&gt;Range Modulator Gating Stop Value" type="1C">
      <description>Stop position defines the range modulator position at which the beam is switched off. Required if Range Modulator Type (300A,0348) of the range modulator referenced by Referenced Range Modulator Number (300C,0104) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS</description>
    </entry>
    <entry group="300A" element="011E" name="&gt;&gt;Gantry Angle" type="1C">
      <description>Treatment machine gantry angle, i.e. orientation of IEC GANTRY coordinate system with respect to IEC FIXED REFERENCE coordinate system (degrees). Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041) or if Gantry Angle changes during beam administration.</description>
    </entry>
    <entry group="300A" element="011F" name="&gt;&gt;Gantry Rotation Direction" type="1C">
      <description>Direction of Gantry Rotation when viewing gantry from isocenter, for segment beginning at current Control Point. Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041), or if Gantry Rotation Direction changes during beam administration.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
    </entry>
    <entry group="300A" element="014A" name="&gt;&gt;Gantry Pitch Angle" type="2C">
      <description>Gantry Pitch Angle. i.e. the rotation of the IEC GANTRY coordinate system about the X-axis of the IEC GANTRY coordinate system (degrees). Required for first item of Control Point Sequence, or if Gantry PitchRotation Angle changes during Beam. See C.8.8.25.6.5.</description>
      <section ref="C.8.8.25.6.5" name="">The Gantry Pitch angle is not defined in IEC 61217. This angle is defined in the DICOM standard in a way compatible with the current notion of IEC by introducing it as rotation of the IEC GANTRY System as indicated below.
The Gantry Pitch Angle is defined as the rotation of the coordinate axes Yg, Zg about axis Xg by an angle g; see Figure C.8.8.25-7. An increase in the value of angle g corresponds to the clockwise rotation as viewed from the isocenter along the positive Xg axis


Figure C.8.8.25-7 Gantry Pitch Angle
</section>
    </entry>
    <entry group="300A" element="014C" name="&gt;&gt;Gantry Pitch Rotation Direction" type="2C">
      <description>Direction of Gantry PitchAngle when viewing along the positive X-axis of the IEC GANTRY coordinate system, for segment following Control Point. Required for first item of Control Point Sequence, or if Gantry PitchRotation Direction changes during Beam. See C.8.8.14.8 and C.8.8.25.6.5.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0120" name="&gt;&gt;Beam Limiting Device Angle" type="1C">
      <description>Beam Limiting Device (collimator) angle, i.e. orientation of IEC BEAM LIMITING DEVICE coordinate system with respect to IEC GANTRY coordinate system (degrees). Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041) or if beam limiting device (collimator) angle changes during beam administration.</description>
    </entry>
    <entry group="300A" element="0121" name="&gt;&gt;Beam Limiting Device Rotation Direction" type="1C">
      <description>Direction of Beam Limiting Device Rotation when viewing beam limiting device (collimator) from radiation source, for segment beginning at current Control Point. Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041) or if Beam Limiting Device Rotation Direction changes during beam administration.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
    </entry>
    <entry group="300A" element="0390" name="&gt;&gt;Scan Spot Tune ID" type="1C">
      <description>User-supplied or machine code identifier for machine configuration to produce beam spot. This may be the nominal spot size or some other machine specific value. Required if Scan Mode (300A,0308) is MODULATED.</description>
    </entry>
    <entry group="300A" element="0392" name="&gt;&gt;Number of Scan Spot Positions" type="1C">
      <description>Number of spot positions used to specify scanning pattern for current segment beginning at control point. Required if Scan Mode (300A,0308) is MODULATED.</description>
    </entry>
    <entry group="300A" element="0394" name="&gt;&gt;Scan Spot Position Map" type="1C">
      <description>The x and y coordinates of the scan spots are defined as projected onto the machine isocentric plane in the IEC GANTRY coordinate system (mm). Required if Scan Mode (300A,0308) is MODULATED. Contains 2N values were N is the Number of Scan Spot Positions (300A,0392).</description>
    </entry>
    <entry group="3008" element="0047" name="&gt;&gt;Scan Spot Metersets Delivered" type="1C">
      <description>A data set of metersets delivered to the scan spot positions. The order of metersets matches the positions in Scan Spot Position Map (300A,0394). The sum contained in all metersets shall match the difference of the Delivered Meterset of the current control point to the following control point. Required if Scan Mode (300A,0308) is MODULATED.</description>
    </entry>
    <entry group="300A" element="0398" name="&gt;&gt;Scanning Spot Size" type="3">
      <description>The Scanning Spot Size as calculated using the Full Width Half Maximum (FWHM). Specified by a numeric pair - the size measured in air at isocenter in IEC GANTRY X direction followed by the size in the IEC GANTRY Y direction (mm).</description>
    </entry>
    <entry group="300A" element="039A" name="&gt;&gt;Number of Paintings" type="1C">
      <description>The intended number of times the scan pattern given by Scan Spot Position Map (300A,0394) and Scan Spot Meterset Weights (300A,0396) in the Referenced RT Plan was to be applied at the current control point.
Note: The actual number of paintings is not known or recorded. The Scan Spot Metersets Delivered (3008,0047) contains the sum of all complete and partial repaints.
Required if Scan Mode (300A,0308) is MODULATED.</description>
    </entry>
    <entry group="300A" element="0122" name="&gt;&gt;Patient Support Angle" type="1C">
      <description>Patient Support angle, i.e. orientation of IEC PATIENT SUPPORT (turntable) coordinate system with respect to IEC FIXED REFERENCE coordinate system (degrees). Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041) or if Patient Support Angle changes during beam administration.</description>
    </entry>
    <entry group="300A" element="0123" name="&gt;&gt;Patient Support Rotation Direction" type="1C">
      <description>Direction of Patient Support Rotation when viewing table from above, for segment beginning at current Control Point.
Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041), or if Patient Support Rotation Direction changes during beam administration.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
    </entry>
    <entry group="300A" element="0140" name="&gt;&gt;Table Top Pitch Angle" type="2C">
      <description>Table Top Pitch Angle, i.e. the rotation of the IEC TABLE TOP coordinate system about the X-axis of the IEC TABLE TOP coordinate system (degrees). Required for first item of Control Point Sequence, or if Table Top Pitch Angle changes during Beam. See section C.8.8.25.6.2.</description>
    </entry>
    <entry group="300A" element="0142" name="&gt;&gt;Table Top Pitch Rotation Direction" type="2C">
      <description>Direction of Table Top Pitch Rotation when viewing the table along the positive X-axis of the IEC TABLE TOP coordinate system, for segment following Control Point. Required for first item of Control Point Sequence, or if Table Top Pitch Rotation Direction changes during Beam. See C.8.8.14.8 and C.8.8.25.6.2.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0144" name="&gt;&gt;Table Top Roll Angle" type="2C">
      <description>Table Top Roll Angle, i.e. the rotation of the IEC TABLE TOP coordinate system about the Y-axis of the IEC TABLE TOP coordinate system (degrees). Required for first item of Control Point Sequence, or if Table Top Roll Angle changes during Beam. See section C.8.8.25.6.2.</description>
    </entry>
    <entry group="300A" element="0146" name="&gt;&gt;Table Top Roll Rotation Direction" type="2C">
      <description>Direction of Table Top Roll Rotation when viewing the table along the positive Y-axis of the IEC TABLE TOP coordinate system, for segment following Control Point. Required for first item of Control Point Sequence, or if Table Top Roll Rotation Direction changes during Beam. See C.8.8.14.8 and C.8.8.25.6.2.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation</description>
      <section ref="C.8.8.14.8" name="">For the machine rotation angles Gantry Angle (300A,011E), Beam Limiting Device Angle (300A,0120), Patient Support Angle (300A,0122) , and Table Top Eccentric Angle (300A,0125), rotation direction is specified as clockwise (CW), counter-clockwise (CC), or NONE. The maximum permitted rotation between two Control Points is 360 degrees. Examples:
a)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = NONE:
  No movement.

b)   Gantry Angle moves from 5 degrees to 5 degrees, Gantry Rotation Direction = CW:
  Full clockwise rotation (360 degrees).

c)   Table Angle moves from 170 degrees to 160 degrees, Table Rotation Direction = CC:
  Counter-clockwise rotation by 350 degrees (note direction of increasing table angle as defined by IEC 61217).

</section>
    </entry>
    <entry group="300A" element="0148" name="&gt;&gt;Head Fixation Angle" type="3">
      <description>Angle (in degrees) of the head fixation for eye treatments with respect to the Table Top Pitch Angle (300A,0140) coordinate system. Positive head fixation angle is the same direction as positive Table Top Pitch. See section C.8.8.25.6.4.</description>
    </entry>
    <entry group="300A" element="0128" name="&gt;&gt;Table Top Vertical Position" type="2C">
      <description>Table Top Vertical position in IEC TABLE TOP coordinate system (mm). This value is interpreted as an absolute, rather than relative, Table setting. Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041) or if Table Top Vertical Position changes during beam administration.</description>
    </entry>
    <entry group="300A" element="0129" name="&gt;&gt;Table Top Longitudinal Position" type="2C">
      <description>Table Top Longitudinal position in IEC TABLE TOP coordinate system (mm). This value is interpreted as an absolute, rather than relative, Table setting. Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041) or if Table Top Longitudinal Position changes during beam administration.</description>
    </entry>
    <entry group="300A" element="012A" name="&gt;&gt;Table Top Lateral Position" type="2C">
      <description>Table Top Lateral position in IEC TABLE TOP coordinate system (mm). This value is interpreted as an absolute, rather than relative, Table setting. Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041) or if Table Top Lateral Position changes during beam administration.</description>
    </entry>
    <entry group="300A" element="030D" name="&gt;&gt;Snout Position" type="2C">
      <description>Axial position of the snout (in mm) measured from isocenter to the downstream side of the snout (without consideration of variable length elements such as blocks, MLC and/or compensators). Required for Control Point 0 of Ion Control Point Delivery Sequence (3008,0041) or if Snout Position changes during beam administration.</description>
    </entry>
    <entry group="3008" element="0068" name="&gt;&gt;Corrected Parameter Sequence" type="3">
      <description>Introduces a sequence of items describing corrections made to any attributes prior to delivery of the next control point. The sequence may contain one or more items.</description>
    </entry>
    <entry group="3008" element="0061" name="&gt;&gt;&gt;Parameter Sequence Pointer" type="1">
      <description>Contains the Data Element Tag of the parent sequence containing the attribute that was corrected. The value is limited in scope to the Treatment Session Ion Beam Sequence (3008,0021) and all nested sequences therein.</description>
    </entry>
    <entry group="3008" element="0063" name="&gt;&gt;&gt;Parameter Item Index" type="1">
      <description>Contains the ones-based sequence item index of the corrected attribute within its parent sequence as indicated by Parameter Sequence Pointer (3008,0061).</description>
    </entry>
    <entry group="3008" element="0065" name="&gt;&gt;&gt;Parameter Pointer" type="1">
      <description>Contains the Data Element Tag of the attribute that was corrected.</description>
    </entry>
    <entry group="3008" element="006A" name="&gt;&gt;&gt;Correction Value" type="1">
      <description>The value that was added the value referenced by the Parameter Sequence Pointer (3008,0061), Parameter Item Index (3008,0063) and Parameter Pointer (3008,0065).</description>
    </entry>
    <entry group="3008" element="0060" name="&gt;&gt;Override Sequence" type="3">
      <description>Introduces sequence of parameters that were overridden during the administration of the beam segment immediately prior to the current control point. The sequence may contain one or more items.</description>
    </entry>
    <entry group="3008" element="0061" name="&gt;&gt;&gt;Parameter Sequence Pointer" type="1">
      <description>Contains the Data Element Tag of the parent sequence containing the attribute that was overriden. The value is limited in scope to the Treatment Session Ion Beam Sequence (3008,0021) and all nested sequences therein.</description>
    </entry>
    <entry group="3008" element="0062" name="&gt;&gt;&gt;Override Parameter Pointer" type="1">
      <description>Contains the Data Element Tag of the attribute that was overridden.</description>
    </entry>
    <entry group="3008" element="0063" name="&gt;&gt;&gt;Parameter Item Index" type="1">
      <description>Contains the ones-based sequence item index of the overriden attributes within it's parent sequence. The value is limited in scope to the Treatment Session Ion Beam Sequence (3008,0021) and all nested sequences therein.</description>
    </entry>
    <entry group="0008" element="1070" name="&gt;&gt;&gt;Operators' Name" type="2">
      <description>Name of operator who authorized override.</description>
    </entry>
    <entry group="3008" element="0066" name="&gt;&gt;&gt;Override Reason" type="3">
      <description>User-defined description of reason for override of parameter specified by Override Parameter Pointer (3008,0062).</description>
    </entry>
  </module>
  <macro table="C.8.8.27-1" name="Beam Limiting Device Position Macro Attributes">
    <entry group="300A" element="011A" name="Beam Limiting Device Position Sequence" type="1C">
      <description>Introduces sequence of beam limiting device (collimator) jaw or leaf (element) positions. Required if Ion Beam Limiting Device Sequence (300A,03A4) is included and for first item of Control Point Sequence, or if Beam Limiting Device changes during Beam. One or more items shall be included in this sequence.</description>
    </entry>
    <entry group="300A" element="00B8" name="&gt;RT Beam Limiting Device Type" type="1">
      <description>Type of beam limiting device (collimator). The value of this attribute shall correspond to RT Beam Limiting Device Type (300A,00B8) defined in an item of Ion Beam Limiting Device Sequence (300A,03A4).
Enumerated Values:
X = symmetric jaw pair in IEC X direction
Y = symmetric jaw pair in IEC Y direction
ASYMX = asymmetric jaw pair in IEC X direction
ASYMY = asymmetric pair in IEC Y direction
MLCX = multileaf (multi-element) jaw pair in IEC X direction
MLCY = multileaf (multi-element) jaw pair in IEC Y direction</description>
    </entry>
    <entry group="300A" element="011C" name="&gt;Leaf/Jaw Positions" type="1">
      <description>Positions of beam limiting device (collimator) leaf (element) or jaw pairs (in mm) in IEC BEAM LIMITING DEVICE coordinate axis appropriate to RT Beam Limiting Device Type (300A,00B8), e.g. X-axis for MLCX, Y-axis for MLCY. Contains 2N values, where N is the Number of Leaf/Jaw Pairs (300A,00BC) in Ion Beam Limiting Device Sequence (300A,03A4). Values shall be listed in IEC leaf (element) subscript order 101, 102, ... 1N, 201, 202, ... 2N. See section C.8.8.25.3.</description>
    </entry>
  </macro>
  <macro table="C.8.8.28-1" name="Patient Support Identification Macro Attributes">
    <entry group="300A" element="0350" name="Patient Support Type" type="1">
      <description>Defined terms:
TABLE = Treatment delivery system table
CHAIR = Treatment delivery system chair
See section C.8.8.25.6.3.</description>
    </entry>
    <entry group="300A" element="0352" name="Patient Support ID" type="3">
      <description>User-specified identifier for manufacturer specific patient support devices.</description>
    </entry>
    <entry group="300A" element="0354" name="Patient Support Accessory Code" type="3">
      <description>A Patient Support accessory identifier to be read by a device such as a bar code reader.</description>
    </entry>
  </macro>
  <module ref="C.8.9.1" table="C.8-60" name="PET Series Module Attributes">
    <entry group="0008" element="0021" name="Series Date" type="1">
      <description>Date the Series started. See C.8.9.1.1.2 for specialization.</description>
      <section ref="C.8.9.1.1.2" name="">For PET Series, Series Date (0008,0021) and Series Time (0008,0031) are specified to be Type 1. The Series Date (0008,0021) and Series Time (0008,0031) are used as the reference time for all PET Image attributes that are temporally related, including activity measurements. The Series Date (0008,0021) and Series Time (0008,0031) are not tied to any real-world event (e.g. acquisition start, radiopharmaceutical administration) and their real-world meaning are implementation dependent.
</section>
    </entry>
    <entry group="0008" element="0031" name="Series Time" type="1">
      <description>Time the Series started. See C.8.9.1.1.2 for specialization.</description>
      <section ref="C.8.9.1.1.2" name="">For PET Series, Series Date (0008,0021) and Series Time (0008,0031) are specified to be Type 1. The Series Date (0008,0021) and Series Time (0008,0031) are used as the reference time for all PET Image attributes that are temporally related, including activity measurements. The Series Date (0008,0021) and Series Time (0008,0031) are not tied to any real-world event (e.g. acquisition start, radiopharmaceutical administration) and their real-world meaning are implementation dependent.
</section>
    </entry>
    <entry group="0054" element="1001" name="Units" type="1">
      <description>Pixel value units. See C.8.9.1.1.3 for explanation. Defined terms:
CNTS, NONE, CM2, PCNT, CPS, BQML, MGMINML, UMOLMINML, MLMING, MLG, 1CM, UMOLML, PROPCNTS, PROPCPS, MLMINML, MLML, GML, STDDEV</description>
      <section ref="C.8.9.1.1.3" name="">The units of the pixel values obtained after conversion from the stored pixel values (SV) (Pixel Data (7FE0,0010)) to pixel value units (U), as defined by Rescale Intercept (0028,1052) and Rescale Slope (0028,1053). Defined Terms:
  CNTS = counts
  NONE = unitless
  CM2 = centimeter**2
  PCNT = percent
  CPS = counts/second
  BQML = Becquerels/milliliter
  MGMINML = milligram/minute/milliliter
  UMOLMINML = micromole/minute/milliliter
  MLMING = milliliter/minute/gram
  MLG = milliliter/gram
  1CM = 1/centimeter
  UMOLML = micromole/milliliter
  PROPCNTS = proportional to counts
  PROPCPS = proportional to counts/sec
  MLMINML = milliliter/minute/milliliter
  MLML = milliliter/milliliter
  GML = grams/milliliter
  STDDEV = standard deviations

</section>
    </entry>
    <entry group="0054" element="1002" name="Counts Source" type="1">
      <description>The primary source of counts. The primary source leads to the underlying image Units (0054,1001), as opposed to secondary sources which are used during reconstruction correction. Enumerated Values:
EMISSION
TRANSMISSION</description>
    </entry>
    <entry group="0054" element="1000" name="Series Type" type="1">
      <description>A multi-valued indicator of the type of Series. See C.8.9.1.1.4 for explanation.
Value 1 Enumerated Values:
STATIC
DYNAMIC
GATED
WHOLE BODY
Value 2 Enumerated Values:
IMAGE
REPROJECTION</description>
      <section ref="C.8.9.1.1.4" name="">The Series Type (0054,1000), Value 1 is used to identify the spatial location and temporal nature of the images within a PET Series. The Enumerated Values and their definitions are:
  STATIC = a group of images at varying spatial locations at the same time
  DYNAMIC = a group of images at a set of spatial locations (e.g. slices) at varying time slices, with all spatial locations acquired at all time slices
  GATED = a group of images at the same spatial location, same starting and ending time, but acquired in different time slots of (possibly) different R-R intervals
  WHOLE BODY = same as STATIC, except covering multiple transverse fields of view (and therefore acquired at a different time).
Notes:  1. Using this definition and the comments in C.8.9.1.1.1, here are some examples of PET series and the encoding of Series Type (0054,1000) Value 1.
  Static acquisition: a group of n transverse images at varying superior&lt;-&gt;inferior locations, all acquired between the same starting and ending time. Series Type = STATIC.
  Dynamic acquisition: a group of n*m transverse images at n superior&lt;-&gt;inferior locations, acquired with m different starting and ending times. Series Type = DYNAMIC.
  Gated acquisition: a group of n*m*p transverse images at n superior&lt;-&gt;inferior locations, all acquired between the same starting and ending time, acquired in m different R-R Intervals (as determined by Low R-R Value (0018,1081) and High R-R Value (0018,1082)), and acquired in p time slots of a given R-R Interval (as determined by Trigger Time (0054,1000) ). Series Type = GATED.
  Whole body acquisition: a group of n transverse images at varying superior&lt;-&gt;inferior locations covering a significant fraction of the entire body. Series Type = WHOLE BODY.
  Multiple transverse fields of view: a group of n transverse images at varying superior&lt;-&gt;inferior locations. Series Type = WHOLE BODY.
  Interleaved: group of 2*n transverse images acquired at overlapped AFOVs to increase transverse sampling. Series Type = WHOLE BODY.
  Sagittal (Coronal, Oblique): sagittal (coronal, oblique) re-sliced images derived by reformatting transverse images. The Series Type is STATIC, DYNAMIC, GATED, or WHOLE BODY depending on source Series Type.
  Arithmetic: images derived by an arithmetic operation on operand images. The Series Type is STATIC, DYNAMIC, GATED, or WHOLE BODY depending on source Series Type.
  Metabolic: images derived by a metabolic model. The Series Type is STATIC, DYNAMIC, GATED, or WHOLE BODY depending on source Series Type.

  2. Using this definition, here are some images that are not stored in the same PET Series:
  Two images from the same scan that were reconstructed differently.
  Emission and transmission images for the same Patient and Study, even if acquired simultaneously (because emission and transmission images have different reconstruction processing).
  Two images of same patient, one after NH3 injection and one after FDG injection.
  Two images: an original image created from reconstructed scan data and its derived image based on a metabolic model.

The Series Type (0054,1000), Value 2 is used to identify the volumetric meaning of the images within a PET Series. The Enumerated Values and their definitions are:
  IMAGE = a tomographic image slice
  REPROJECTION = a projection image derived from forward projection through slices of tomographic images, using the algorithm defined in Reprojection Method (0054,1004).
</section>
    </entry>
    <entry group="0054" element="1004" name="Reprojection Method" type="2C">
      <description>Method for projecting volumetric data onto planar projection. Required if Series Type (0054,1000), Value 2 is REPROJECTION. Defined terms:
SUM
MAX PIXEL</description>
    </entry>
    <entry group="0054" element="0061" name="Number of R-R Intervals" type="1C">
      <description>The maximum number of R-R Intervals that may exist in this Series. Required if Series Type (0054,1000), Value 1 is GATED.</description>
    </entry>
    <entry group="0054" element="0071" name="Number of Time Slots" type="1C">
      <description>The maximum number of Time Slots that may exist in this Series. Required if Series Type (0054,1000), Value 1 is GATED.</description>
    </entry>
    <entry group="0054" element="0101" name="Number of Time Slices" type="1C">
      <description>The maximum number of Time Slices that may exist in this Series. Required if Series Type (0054,1000), Value 1 is DYNAMIC.</description>
    </entry>
    <entry group="0054" element="0081" name="Number of Slices" type="1">
      <description>The maximum number of Slices that may exist in this Series.</description>
    </entry>
    <entry group="0028" element="0051" name="Corrected Image" type="2">
      <description>A value that indicates which, if any, corrections have been applied to the images in this series. Defined terms:
DECY=decay corrected
ATTN=attenuation corrected
SCAT=scatter corrected
DTIM=dead time corrected
MOTN=gantry motion corrected (e.g. wobble, clamshell)
PMOT=patient motion corrected
CLN=count loss normalization (correction for count loss in gated Time Slots).
RAN=randoms corrected
RADL=non-uniform radial sampling corrected
DCAL=sensitivity calibrated using dose calibrator
NORM=detector normalization</description>
    </entry>
    <entry group="0054" element="1100" name="Randoms Correction Method" type="3">
      <description>Type of randoms correction processing. Defined terms:
NONE = no randoms correction
DLYD = delayed event subtraction
SING = singles estimation</description>
    </entry>
    <entry group="0054" element="1101" name="Attenuation Correction Method" type="3">
      <description>A textual description of the attenuation correction processing. e.g. measured vs. calculated, transmission source type (ring, line, point), assumed patient geometry (polygon, ellipse, segmented, attenuation coefficient, skull thickness), post-injection transmission, smoothing.</description>
    </entry>
    <entry group="0054" element="1105" name="Scatter Correction Method" type="3">
      <description>A textual description of the scatter correction processing. e.g. convolution-subtraction, dual energy window, model-based, use of attenuation data.</description>
    </entry>
    <entry group="0054" element="1102" name="Decay Correction" type="1">
      <description>The real-world event to which images in this Series were decay corrected. See C.8.9.1.1.5 for explanation. Defined terms:
NONE = no decay correction
START= acquisition start time
ADMIN = radiopharmaceutical administration time</description>
      <section ref="C.8.9.1.1.5" name="">The Decay Correction (0054,1102) is the real-world event to which images in this Series were decay corrected. If decay correction is applied, all images in the Series shall be decay corrected to the same time. The Defined Terms and definitions are:
  NONE = no decay correction
  START= acquisition start time, Acquisition Time (0008,0032)
  ADMIN = radiopharmaceutical administration time, Radiopharmaceutical Start Time (0018,1072)
The time to which images have been decay corrected can be derived from Decay Factor (0054,1321), Frame Reference Time (0054,1300), Radionuclide Half Life (0018,1075), Series Date (0008,0021), and Series Time (0008,0031).
</section>
    </entry>
    <entry group="0018" element="1100" name="Reconstruction Diameter" type="3">
      <description>Diameter, in mm, of the region within which the data was used in creating the reconstruction of the image. Data may exist outside this region and portions of the patient may exist outside this region.</description>
    </entry>
    <entry group="0018" element="1210" name="Convolution Kernel" type="3">
      <description>Textual description of the convolution kernel(s) used to reconstruct the data (e.g. name, cutoff, radial/axial/angular, mathematical form, DC handling)</description>
    </entry>
    <entry group="0054" element="1103" name="Reconstruction Method" type="3">
      <description>Textual description of reconstruction processing, e.g. 2D filtered backprojection, 2D iterative, 3D PROMIS, 3D FAVOR, 3D iterative.</description>
    </entry>
    <entry group="0054" element="1104" name="Detector Lines of Response Used" type="3">
      <description>Textual description of which detector lines of response were used, mashed, or otherwise processed during tomographic reconstruction.</description>
    </entry>
    <entry group="0018" element="0073" name="Acquisition Start Condition" type="3">
      <description>Description of how the data collection was started. Defined terms:
DENS = density (counts/sec)
RDD = relative density difference (change in counts/sec)
MANU = manual
TIME = time
AUTO = automatic, when ready
TRIG = physiological trigger
See C.8.9.1.1.6 for explanation.</description>
      <section ref="C.8.9.1.1.6" name="">Acquisition Start Condition (0018,0073) is the method of starting acquisition data collection. The Defined Terms and definitions are:
  DENS = preset count density (counts/sec) was reached
  RDD = preset relative count density difference (change in counts/sec) was reached
  MANU = acquisition was started manually
  TIME = preset time limit was reached
  AUTO = start automatically, when ready
  TRIG = preset number of physiological triggers was reached
</section>
    </entry>
    <entry group="0018" element="0074" name="Acquisition Start Condition Data" type="3">
      <description>Count density, change in count density, or physiological triggers causing data collection to start.</description>
    </entry>
    <entry group="0018" element="0071" name="Acquisition Termination Condition" type="3">
      <description>Description of how the data collection for the series was stopped. Defined terms:
CNTS = counts
DENS = density (counts/sec)
RDD = relative density difference (change in counts/sec)
MANU = manual
OVFL = data overflow
TIME = time
TRIG = physiological trigger
See C.8.4.9.1.3 for explanation.</description>
      <section ref="C.8.4.9.1.3" name="">Acquisition Termination Condition (0018,0071) is the method of acquisition termination which was actually applied to the data collection. The Defined Terms and definitions are:
CNTS  =  preset count limit was reached
DENS  =  preset count density was reached
MANU  =  acquisition was terminated manually
OVFL  =  acquisition was terminated automatically by pixel data overflow condition
TIME  =  preset time limit was reached
TRIG  =  preset number of physiological triggers was reached

</section>
    </entry>
    <entry group="0018" element="0075" name="Acquisition Termination Condition Data" type="3">
      <description>Number of counts, count density, change in count density, or physiological triggers causing the termination.</description>
    </entry>
    <entry group="0018" element="1147" name="Field of View Shape" type="3">
      <description>Shape of the field of view of the PET camera. Defined Terms:
CYLINDRICAL RING
HEXAGONAL
MULTIPLE PLANAR</description>
    </entry>
    <entry group="0018" element="1149" name="Field of View Dimensions" type="3">
      <description>Dimensions of the field of view, in mm. Transverse detector diameter followed by axial width.</description>
    </entry>
    <entry group="0018" element="1120" name="Gantry/Detector Tilt" type="3">
      <description>Angle of tilt in degrees of the gantry. See C.8.9.1.1.7 for explanation.</description>
      <section ref="C.8.9.1.1.7" name="">Gantry/Detector Tilt (0018,1120) for PET Image data is the angle in degrees of the gantry relative to the patient’s major (Head to Feet) axis (or the table supporting the patient). Positive tilt is moving the top of the gantry towards the patient’s feet.
</section>
    </entry>
    <entry group="0018" element="1121" name="Gantry/Detector Slew" type="3">
      <description>Angle of slew in degrees of the gantry. Positive slew is moving the gantry on the patient's left toward the patient's superior, when the patient is supine.</description>
    </entry>
    <entry group="0054" element="0202" name="Type of Detector Motion" type="3">
      <description>Describes the detector motion during acquisition. Defined Terms:
NONE = stationary gantry
STEP AND SHOOT = Interrupted motion, acquire only while stationary
CONTINUOUS = Gantry motion and acquisition are simultaneous and continuous
WOBBLE = wobble motion
CLAMSHELL = clamshell motion</description>
    </entry>
    <entry group="0018" element="1181" name="Collimator Type" type="2">
      <description>Collimator Type. Defined Terms:
NONE = no collimator
RING = transverse septa</description>
    </entry>
    <entry group="0018" element="1180" name="Collimator/Grid Name" type="3">
      <description>Label describing the collimator used.</description>
    </entry>
    <entry group="0054" element="1200" name="Axial Acceptance" type="3">
      <description>Maximum axial angle accepted, in degrees.</description>
    </entry>
    <entry group="0054" element="1201" name="Axial Mash" type="3">
      <description>Number of adjacent axial lines of response mashed together. See C.8.9.1.1.8 for explanation.</description>
      <section ref="C.8.9.1.1.8" name="">Axial Mash (0054,1201) is multi-valued and is defined as the number of unique axial Lines of Response (LOR) that were mashed together (center of the axial field of view only). Value 1 is the number of LORs mashed for an odd slice. Value 2 is the number of LORs mashed for an even slice. For discrete crystal scanners, each unique LOR corresponds to a pair of crystals. For continuous detectors whose bin size is variable, the number of LORs mashed is determined by the actual bin size divided by the Detector Element Size (0054,1203), Value 2. The value of Axial Mash (0054,1201) is the same regardless of whether the mashing was done during acquisition or reconstruction.
Note:  As an example on a discrete crystal scanner, if a ring difference of -2,0,+2 are binned as an odd slice and a ring difference of -1,+1 are binned as an even slice, then the Axial Mash (0054,1201) is equal to 3\2 .

</section>
    </entry>
    <entry group="0054" element="1202" name="Transverse Mash" type="3">
      <description>Number of adjacent transverse lines of response mashed together. See C.8.9.1.1.9 for explanation.</description>
      <section ref="C.8.9.1.1.9" name="">Transverse Mash (0054,1202) is defined as the number of unique transverse Lines of Response (LOR) that were mashed together. For discrete crystal scanners, each unique LOR corresponds to a pair of crystals. For continuous detectors whose bin size is variable, the number of LORs mashed is determined by the actual bin size divided by the Detector Element Size (0054,1203), Value 1. The value of Transverse Mash (0054,1202) is the same regardless of whether the mashing was done during acquisition or reconstruction.
</section>
    </entry>
    <entry group="0054" element="1203" name="Detector Element Size" type="3">
      <description>Size of an individual detector element, in mm. Transverse dimension followed by axial dimension. For a discrete crystal, this is the crystal size. For a continuous detector, this is the pixel bin size.</description>
    </entry>
    <entry group="0054" element="1210" name="Coincidence Window Width" type="3">
      <description>The width of the coincidence timing window, in nsec. The maximum time difference accepted between two single events.</description>
    </entry>
    <entry group="0054" element="0013" name="Energy Window Range Sequence" type="3">
      <description>Sequence of Items that describes the energy windows used for this Series. This sequence may contain zero or more items. See C.8.9.1.1.10 for explanation.</description>
      <section ref="C.8.9.1.1.10" name="">Multiple energy windows are allowed in order to allow coincidence events based on additional Energy Windows (e.g. Compton events scattered in the detector). All energy windows are assumed to contribute to all images in the PET Series.
</section>
    </entry>
    <entry group="0054" element="0014" name="&gt;Energy Window Lower Limit" type="3">
      <description>The lower limit of the energy window, in KeV.</description>
    </entry>
    <entry group="0054" element="0015" name="&gt;Energy Window Upper Limit" type="3">
      <description>The upper limit of the energy window, in KeV.</description>
    </entry>
    <entry group="0054" element="1220" name="Secondary Counts Type" type="3">
      <description>Array defining the type of additional counts accumulated during acquisition. Defined terms:
DLYD=delayed events
SCAT=scattered events in secondary window
SING=singles
DTIM=events lost due to deadtime</description>
    </entry>
  </module>
  <module ref="C.8.9.2" table="C.8-61" name="PET Isotope Module Attributes">
    <entry group="0054" element="0016" name="Radiopharmaceutical Information Sequence" type="2">
      <description>Sequence of Items that describe isotope information. Zero or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0054" element="0300" name="&gt;Radionuclide Code Sequence" type="2">
      <description>Sequence that identifies the radionuclide. Zero or one item shall be present in the sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 4020 ."/>
    <entry group="0018" element="1070" name="&gt;Radiopharmaceutical Route" type="3">
      <description>Route of administration.</description>
    </entry>
    <entry group="0054" element="0302" name="&gt;Administration Route Code Sequence" type="3">
      <description>Sequence that identifies the administration route of the radiopharmaceutical. This sequence shall contain exactly one item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 11 ."/>
    <entry group="0018" element="1071" name="&gt;Radiopharmaceutical Volume" type="3">
      <description>Volume of administered radiopharmaceutical in cubic cm.</description>
    </entry>
    <entry group="0018" element="1072" name="&gt;Radiopharmaceutical Start Time" type="3">
      <description>Time of start of administration. The actual time of radiopharmaceutical administration to the patient for imaging purposes, using the same time base as Series Time (0008,0031).
The use of this Attribute is deprecated in favor of Radiopharmaceutical Start DateTime (0018,1078).
Note: The use of a time alone can cause confusion when the procedure spans midnight.</description>
    </entry>
    <entry group="0018" element="1078" name="&gt;Radiopharmaceutical Start DateTime" type="3">
      <description>Date and time of start of administration. The actual date and time of radiopharmaceutical administration to the patient for imaging purposes, using the same time base as Series Time (0008,0031).</description>
    </entry>
    <entry group="0018" element="1073" name="&gt;Radiopharmaceutical Stop Time" type="3">
      <description>Time of end of administration. The actual ending time of radiopharmaceutical administration to the patient for imaging purposes, using the same time base as Series Time (0008,0031).
The use of this Attribute is deprecated in favor of Radiopharmaceutical Stop DateTime (0018,1079).
Note: The use of a time alone can cause confusion when the procedure spans midnight.</description>
    </entry>
    <entry group="0018" element="1079" name="&gt;Radiopharmaceutical Stop DateTime" type="3">
      <description>Date and time of end of administration. The actual ending date and time of radiopharmaceutical administration to the patient for imaging purposes, using the same time base as Series Time (0008,0031).</description>
    </entry>
    <entry group="0018" element="1074" name="&gt;Radionuclide Total Dose" type="3">
      <description>The radiopharmaceutical dose administered to the patient measured in Becquerels (Bq) at the Radiopharmaceutical Start Time (0018,1072).
Note: In other IODs, such as the NM IOD, this same attribute is specified in MegaBecquerels (MBq).</description>
    </entry>
    <entry group="0018" element="1075" name="&gt;Radionuclide Half Life" type="3">
      <description>The radionuclide half life, in seconds, that was used in the correction of this image.</description>
    </entry>
    <entry group="0018" element="1076" name="&gt;Radionuclide Positron Fraction" type="3">
      <description>The radionuclide positron fraction (fraction of decays that are by positron emission) that was used in the correction of this image.</description>
    </entry>
    <entry group="0018" element="1077" name="&gt;Radiopharmaceutical Specific Activity" type="3">
      <description>The activity per unit mass of the radiopharmaceutical, in Bq/micromole, at the Radiopharmaceutical Start Time (0018,1072).</description>
    </entry>
    <entry group="0018" element="0031" name="&gt;Radiopharmaceutical" type="3">
      <description>Name of the radiopharmaceutical.</description>
    </entry>
    <entry group="0054" element="0304" name="&gt;Radiopharmaceutical Code Sequence" type="3">
      <description>Sequence that identifies the radiopharmaceutical. This sequence shall contain exactly one item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 4021 ."/>
    <entry group="0018" element="0026" name="Intervention Drug Information Sequence" type="3">
      <description>Sequence of Items that describes the intervention drugs used. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="0018" element="0034" name="&gt;Intervention Drug Name" type="3">
      <description>Name of the intervention drug.</description>
    </entry>
    <entry group="0018" element="0029" name="&gt;Intervention Drug Code Sequence" type="3">
      <description>Sequence that identifies the intervention drug name. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 10 ."/>
    <entry group="0018" element="0035" name="&gt;Intervention Drug Start Time" type="3">
      <description>Time of administration of the intervention drug, using the same time base as for the Series Time (0008,0031).</description>
    </entry>
    <entry group="0018" element="0027" name="&gt;Intervention Drug Stop Time" type="3">
      <description>Time of completion of administration of the intervention drug, using the same time base as for the Series Time (0008,0031).</description>
    </entry>
    <entry group="0018" element="0028" name="&gt;Intervention Drug Dose" type="3">
      <description>Intervention drug dose, in mg.</description>
    </entry>
  </module>
  <module ref="C.8.9.3" table="C.8-62" name="PET Multi Gated Acquisition Module Attributes">
    <entry group="0018" element="1080" name="Beat Rejection Flag" type="2">
      <description>Heart beat duration sorting has been applied. Enumerated values:
Y = yes
N = no</description>
    </entry>
    <entry group="0018" element="1061" name="Trigger Source or Type" type="3">
      <description>Text indicating trigger source. Defined terms:
EKG</description>
    </entry>
    <entry group="0018" element="1085" name="PVC Rejection" type="3">
      <description>Description of the type of PVC rejection criteria used.</description>
    </entry>
    <entry group="0018" element="1086" name="Skip Beats" type="3">
      <description>Number of beats skipped after a detected arrhythmia.</description>
    </entry>
    <entry group="0018" element="1088" name="Heart Rate" type="3">
      <description>Average number of heart beats per minute for the collection period for this image. This shall include all accepted beats as well as rejected beats.</description>
    </entry>
    <entry group="0018" element="1064" name="Cardiac Framing Type" type="3">
      <description>Description of type of framing performed. Defined Terms:
FORW = forward
BACK = backward
PCNT = forward/backward by percentage
See C.7.6.18.1.1.1.</description>
      <section ref="C.7.6.18.1.1.1" name="">Cardiac Framing Type (0018,1064) is the mechanism used to select the data acquired to construct the frames within a specified cardiac timing interval.C.7.6.18.2  Respiratory Synchronization Module
Table C7.6.18-2 specifies the attributes of the Respiratory Synchronization Module.
Table C.7.6.18-2
RESPIRATORY SYNCHRONIZATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Respiratory Motion Compensation Technique" meaning="(0018,9170)"/><term value="Respiratory Signal Source" meaning="(0018,9171)"/><term value="Respiratory Trigger Delay Threshold" meaning="(0020,9256)"/><term value="Respiratory Trigger Type" meaning="(0020,9250)"/></unrecognized-rows>
         </section>
    </entry>
  </module>
  <module ref="C.8.9.4" table="C.8-63" name="PET Image Module Attributes">
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image identification characteristics. See C.8.9.4.1.1 for specialization.</description>
      <section ref="C.8.9.4.1.1" name="">For PET Images, Image Type (0008,0008) is specified to be Type 1.
Note:  For PET images, Image Type (0008,0008) Value 1 will be ORIGINAL for reconstructed images. DERIVED may be appropriate for some other results images. For PET images, Image Type (0008,0008) Value 2 will be PRIMARY.

</section>
    </entry>
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (planes) in this image. This value shall be 1.</description>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data. See C.8.9.4.1.2 for specialization.</description>
      <section ref="C.8.9.4.1.2" name="">For PET images, Photometric Interpretation (0028,0004) shall have one of the following Enumerated Values:
  MONOCHROME2
See C.7.6.3.1.2 for definition of this term.
</section>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated. Enumerated values: 16.</description>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored. The value shall be the same as the value in Bits Allocated (0028,0100).</description>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data. Each sample shall have the same high bit.
Shall be one less than the value in Bits Stored (0028,0101).</description>
    </entry>
    <entry group="0028" element="1052" name="Rescale Intercept" type="1">
      <description>The value b in relationship between stored values (SV) and pixel value units (U) defined in Units (0054,1001): U = m*SV+b. The Rescale Intercept is always zero for PET images.</description>
    </entry>
    <entry group="0028" element="1053" name="Rescale Slope" type="1">
      <description>m in the equation specified in Rescale Intercept (0028,1052).</description>
    </entry>
    <entry group="0054" element="1300" name="Frame Reference Time" type="1">
      <description>The time that the pixel values in the image occurred. Frame Reference Time is the offset, in msec, from the Series reference time. See explanation in C.8.9.4.1.5.</description>
    </entry>
    <entry group="0018" element="1060" name="Trigger Time" type="1C">
      <description>Time interval, in msec, from the start of the trigger to the beginning of data acquisition for this image. Required if Series Type (0054,1000), Value 1 is GATED.</description>
    </entry>
    <entry group="0018" element="1063" name="Frame Time" type="1C">
      <description>Nominal duration per individual frame, in msec. Required if Series Type (0054,1000), Value 1 is GATED. See C.8.9.4.1.3 for explanation.</description>
      <section ref="C.8.9.4.1.3" name="">The Frame Time (0018,1063) is the explicit duration of the gated frame when Cardiac Framing Type (0018,1064) is equal to FORW or BACK. Frame Time (0018,1063) is the nominal duration of the gated frame when Cardiac Framing Type (0018,1064) is equal to PCNT.
</section>
    </entry>
    <entry group="0018" element="1081" name="Low R-R Value" type="1C">
      <description>R-R interval lower limit for beat rejection, in msec. Required if Series Type (0054,1000), Value 1 is GATED and Beat Rejection Flag (0018,1080) is Y.</description>
    </entry>
    <entry group="0018" element="1082" name="High R-R Value" type="1C">
      <description>R-R interval upper limit for beat rejection, in msec. Required if Series Type (0054,1000), Value 1 is GATED and Beat Rejection Flag (0018,1080) is Y.</description>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1C">
      <description>Specifies whether an Image has undergone lossy compression. Enumerated values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5.
Required if Lossy Compression has been performed on the image.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0054" element="1330" name="Image Index" type="1">
      <description>An index identifying the position of this image within a PET Series. See C.8.9.4.1.9 for explanation.</description>
      <section ref="C.8.9.4.1.9" name="">Image Index (0054,1330) is an index identifying the position of this image within a PET Series.
Note:  The scheme for encoding Image Index (0054,1330) is as follows. Images within a PET Series can be viewed as a multi-dimensional array whose possible dimensions include R-R Intervals, Time Slots, Time Slices, and Slices. The dimensions of the array are defined by the Series Type (0054,1000) Value 1. Each dimension of the array has an index that identifies the position of this image in the array. The indices are: R-R Interval Index, Time Slot Index, Time Slice Index, Slice Index. The indices are calculated as follows:

<unrecognized-rows><term value="Index" meaning="Range of Index"/><term value="Index" meaning="1 to"/><term value="Index" meaning="1 to"/><term value="Index" meaning="1 to"/><term value="Slice Index" meaning="1 to"/></unrecognized-rows>
Using these index values the position of this image within the multi-dimensional array (the Image Index (0054,1330)) is calculated as follows:
<unrecognized-rows><term value="Value 1" meaning="Dimensions of Array"/><term value="STATIC" meaning="Slice"/><term value="WHOLE BODY" meaning="Slice"/><term value="DYNAMIC" meaning="Time Slice \"/><term value="GATED" meaning="R-R Interval \"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0008" element="0022" name="Acquisition Date" type="2">
      <description>The date the acquisition of data that resulted in this image started. See C.8.9.4.1.4 for specialization.</description>
      <section ref="C.8.9.4.1.4" name="">For PET Images, Acquisition Date (0008,0022) and Acquisition Time (0008,0032) are specified to be Type 2. The Acquisition Date (0008,0022) and Acquisition Time (0008,0032) use the same time base as Series Time (0008,0031).
For Series Type (0054,1000) Value 1 equal to STATIC, WHOLE BODY, or DYNAMIC, the Acquisition Time (0008,0032) is the real-world beginning of the accumulation of events into this Image. For STATIC, WHOLE BODY, or DYNAMIC Series, the Acquisition Time (0008,0032) may vary from Image to Image within a PET Series.
For Series Type (0054,1000) Value 1 equal to GATED, the Acquisition Time (0008,0032) is the real-world beginning of the capability of accumulating events into this Image. (The actual accumulation of events has only occurred during an R-R Interval.) For GATED Series, the Acquisition Time (0008,0032) shall not vary from Image to Image within a PET Series.
</section>
    </entry>
    <entry group="0008" element="0032" name="Acquisition Time" type="2">
      <description>The time the acquisition of data that resulted in this image started. See C.8.9.4.1.4 for specialization.</description>
      <section ref="C.8.9.4.1.4" name="">For PET Images, Acquisition Date (0008,0022) and Acquisition Time (0008,0032) are specified to be Type 2. The Acquisition Date (0008,0022) and Acquisition Time (0008,0032) use the same time base as Series Time (0008,0031).
For Series Type (0054,1000) Value 1 equal to STATIC, WHOLE BODY, or DYNAMIC, the Acquisition Time (0008,0032) is the real-world beginning of the accumulation of events into this Image. For STATIC, WHOLE BODY, or DYNAMIC Series, the Acquisition Time (0008,0032) may vary from Image to Image within a PET Series.
For Series Type (0054,1000) Value 1 equal to GATED, the Acquisition Time (0008,0032) is the real-world beginning of the capability of accumulating events into this Image. (The actual accumulation of events has only occurred during an R-R Interval.) For GATED Series, the Acquisition Time (0008,0032) shall not vary from Image to Image within a PET Series.
</section>
    </entry>
    <entry group="0018" element="1242" name="Actual Frame Duration" type="2">
      <description>Elapsed time of the data acquisition for this image, in msec. See C.8.9.4.1.6 for explanation.</description>
      <section ref="C.8.9.4.1.6" name="">The accumulation of counts for a PET Image shall occur entirely between:
(1) the acquisition starting time (as specified by Acquisition Date (0008,0022) and Acquisition Time (0008,0032)), and
(2) the acquisition ending time, which is equal to the acquisition starting time in (1) plus the Actual Frame Duration (0018,1242).
If the Series Type (0054,1000), Value 1 is GATED, then the actual accumulation of counts has only occurred during an R-R Interval.
</section>
    </entry>
    <entry group="0018" element="1062" name="Nominal Interval" type="3">
      <description>Average duration of accepted beats, in msec, of the R-R interval.</description>
    </entry>
    <entry group="0018" element="1083" name="Intervals Acquired" type="3">
      <description>Number of heartbeats that fall within Low R-R Value (0018,1081) and High R-R Value (0018,1082), and were therefore accepted and contribute coincidence events to this R-R Interval.</description>
    </entry>
    <entry group="0018" element="1084" name="Intervals Rejected" type="3">
      <description>Number of heartbeats that fall outside Low R-R Value (0018,1081) and High R-R Value (0018,1082), and do not contribute coincidence events to this R-R Interval. However, they may contribute coincidence events to other R-R Intervals.</description>
    </entry>
    <entry group="0054" element="1310" name="Primary (Prompts) Counts Accumulated" type="3">
      <description>The sum of events that occur in the primary event channel. The counts include Trues +Scatter+ Randoms if Randoms Correction Method (0054,1100) is NONE; otherwise the counts are Trues +Scatter.</description>
    </entry>
    <entry group="0054" element="1311" name="Secondary Counts Accumulated" type="3">
      <description>Sum of counts accumulated in secondary channels. See C.8.9.4.1.7 for explanation.</description>
      <section ref="C.8.9.4.1.7" name="">Secondary Counts Accumulated (0054,1311) is multi-valued and, if supplied, has Values corresponding to the Secondary Counts Type (0054,1220). The number and order of the Values in Secondary Counts Accumulated (0054,1311) shall be the same as Secondary Counts Type (0054,1220).
</section>
    </entry>
    <entry group="0054" element="1320" name="Slice Sensitivity Factor" type="3">
      <description>The slice-to-slice sensitivity correction factor that was used to correct this image. The value shall be one if no slice sensitivity correction was applied.</description>
    </entry>
    <entry group="0054" element="1321" name="Decay Factor" type="1C">
      <description>The decay factor that was used to scale this image. Required if Decay Correction (0054,1102) is other than NONE. If decay correction is applied, all images in the Series shall be decay corrected to the same time.</description>
    </entry>
    <entry group="0054" element="1322" name="Dose Calibration Factor" type="3">
      <description>Factor that was used to scale this image from counts/sec to Bq/ml using a dose calibrator. The value shall be one if no dose calibration was applied. See C.8.9.4.1.8 for explanation.</description>
      <section ref="C.8.9.4.1.8" name="">The Dose Calibration Factor (0054,1322) is the factor that was used to scale this image from counts/sec to Bq/ml using an external dose calibrator. The value shall be one if no dose calibration was applied. The application of a dose calibration correction is specified by Corrected Image (0028,0051) equal to DCAL.
Note:  Dose Calibration Factor (0054,1322) is not equal to the inverse of the sensitivity (kcps/Bq/ml) of the scanner, which is usually measured for a given radiopharmaceutical distribution and excluding the effects of attenuation.

</section>
    </entry>
    <entry group="0054" element="1323" name="Scatter Fraction Factor" type="3">
      <description>An estimate of the fraction of acquired counts that were due to scatter and were corrected in this image. The value shall be zero if no scatter correction was applied.</description>
    </entry>
    <entry group="0054" element="1324" name="Dead Time Factor" type="3">
      <description>The average dead time correction factor that was applied to this image. The value shall be one if no dead time correction was applied.</description>
    </entry>
    <include ref="Include 'General Anatomy Optional Macro' Table 10-7" description="No Context ID for the Anatomic Region Sequence is defined."/>
    <entry group="0054" element="0500" name="Slice Progression Direction" type="3">
      <description>Describes the anatomical direction that slices are progressing as the slices are considered in order (as defined by the Slice Index. See section C.8.9.4.1.9 for a definition of Slice Index). Meaningful only for cardiac images.
When View Code Sequence (0054,0220) indicates a short axis view, then Enumerated Values are:
APEX_TO_BASE
BASE_TO_APEX</description>
    </entry>
    <entry group="0054" element="0220" name="View Code Sequence" type="3">
      <description>Sequence that describes the projection of the anatomic region of interest.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt; Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 26."/>
    <entry group="0054" element="0222" name="&gt; View Modifier Code Sequence" type="2C">
      <description>View Modifier.
Required if needed to fully specify the View.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt; Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 23."/>
  </module>
  <module ref="C.8.11.1" table="C.8-68" name="DX Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Type of equipment that originally acquired the data used to create the images in this Series.
Enumerated Values:
DX
PX
IO
MG
See section C.7.3.1.1.1 for further explanation.</description>
    </entry>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence" type="1C">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance to which the Series is related (e.g. a Modality or General-Purpose Performed Procedure Step SOP Instance). The Sequence shall have one Item.
Required if the Modality Performed Procedure Step SOP Class, General Purpose Performed Procedure Step SOP Class is supported.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0008" element="0068" name="Presentation Intent Type" type="1">
      <description>Identifies the intent of the images that are contained within this Series.
Enumerated Values:
FOR PRESENTATION
FOR PROCESSING
See C.8.11.1.1.1 for further explanation.</description>
      <section ref="C.8.11.1.1.1" name="">Presentation Intent Type (0008,0068) shall identify the intent for the purposes of display or other presentation of all Images within this Series.
Notes:  1. Since this is a Series level attribute, all Images within a Series have the same value for this Attribute.
  2. The intent of this restriction is to ensure that FOR PRESENTATION and FOR PROCESSING images are placed in separate Series, so that no confusion can arise as to which images are suitable for diagnostic reading as determined by local policy.

A Series of Images intended for viewing by an observer, after application of any grayscale transformations specified in the image object such as VOI LUT, shall have an Enumerated Value of FOR PRESENTATION.
Notes:  1. These images may still be of Image Type (0008,0008) ORIGINAL rather than DERIVED despite the possibility that they may have undergone some processing, such as unsharp masking. In this case a DERIVED image would have undergone yet further processing to make it substantially different from the original. See Figure C.8-13.
  2. These images may still be subjected to processing or further processing, if appropriate, depending on the application.
  3. These images are intended for display on a device, without (further) processing, since that device may not be capable of image processing. The quality of the displayed image or its suitability for any purpose is beyond the scope of the DICOM Standard.

Images that have been corrected to account for characteristics of the detector but which are intended to be further processed before being displayed, shall have an Enumerated Value of FOR PROCESSING.
Note:  This type is provided to allow the functions of image acquisition and image processing for presentation to be separated and yet have images conveyed between the two processes using a DICOM object. Individual sites or users may choose to substitute their own specialized processing in place of that supplied by the implementor.
  Images available at this stage of processing may be useful for quality control and problem solving purposes, as well as academic research.
  Images of this type may also be archived, retrieved and processed with different algorithms or parameters in order to alter the appearance of specific features for clinical purposes.
  The nature of the detector correction that may have been applied before sending an image of type FOR PROCESSING is not specified. In particular, acquisitions that acquire several sets of matrices of pixel values (such as image data, gain offset and a defect map) must perform some processing (detector correction) before a DX Image object can be instantiated.
  The nature of the processing that may have been applied before sending an image of type FOR PRESENTATION is also not specified.
  It is expected that individual implementors will use Private Attributes to convey specifics of the processing applied that may be of use for further processing by those aware of the parameters and algorithms. The diversity of detector types and processing algorithms make it undesirable to standardize such parameters.
  Whether or not the spatial locations of all pixels are preserved during the processing of the source image that resulted in the current image can be indicated by Spatial Locations Preserved (0028,135A) in a Source Image Sequence (0008,2112) reference from the FOR PRESENTATION image to a FOR PROCESSING predecessor.

If images from the same exposure exist with different Values of Presentation Intent Type (0008,0068), then they shall have different SOP Instance UIDs.
Notes:  1. Source Image Sequence (0008,2112) may be used to relate these images.
  2. The SOP Class UIDs of the two images will also be different.

</section>
    </entry>
  </module>
  <module ref="C.8.11.2" table="C.8-69" name="DX Anatomy Imaged Module Attributes">
    <entry group="0020" element="0062" name="Image Laterality" type="1">
      <description>Laterality of (possibly paired) body part (as described in Anatomic Region Sequence (0008,2218)) examined.
Enumerated Values:
R = right
L = left
U = unpaired
B = both left and right

Note: This Attribute is mandatory, in order to ensure that images may be positioned correctly relative to one another for display.
Shall be consistent with any laterality information contained in Primary Anatomic Structure Modifier Sequence (0008,2230), if present.
Note: Laterality (0020,0060) is a Series level Attribute and must be the same for all Images in the Series, hence it must be absent.</description>
    </entry>
    <include ref="Include 'General Anatomy Required Macro' Table 10-6" description="Defined Context ID for the Anatomic Region Sequence is 4009. This is the anatomic region that is placed on the table or bucky for examination.Note: It is strongly recommended that Anatomic Region Sequence (0008,2218) be sent with a value, in order to ensure that images may be positioned correctly relative to one another for display."/>
  </module>
  <module ref="C.8.11.3" table="C.8-70" name="DX Image Module Attributes">
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image identification characteristics.
See C.8.11.3.1.1 for specialization.</description>
      <section ref="C.8.11.3.1.1" name="">Value 1 shall identify the Pixel Data Characteristics in accordance with Section C.7.6.1.1.2 where the Enumerated Values are defined to be ORIGINAL or DERIVED.
Note:  DX images may still be of type ORIGINAL rather than DERIVED despite the possibility that they may have undergone some processing. In this case a DERIVED image would have undergone yet further processing to make it substantially different from the original.

Value 2 shall identify the Patient Examination Characteristics in accordance with Section C.7.6.1.1.2 where the Enumerated Values are defined to be PRIMARY or SECONDARY.
Note:  DX images generally use PRIMARY value for images captured from patient exposure.

If images from the same exposure exist with different Values of Image Type, then they shall have different SOP Instance UIDs.
Note:  Source Image Sequence (0008,2112) may be used to relate these images.

Value 3 (which is specific to the IOD) shall be present and have zero length (null value).
Other Values (4 and beyond) are optional and implementation specific.
</section>
    </entry>
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples in this image. Shall have an Enumerated Value of 1.</description>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data.
Enumerated Values:
MONOCHROME1
MONOCHROME2</description>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample.
Enumerated Values: 8, 16</description>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample.
Enumerated Values: 6 to 16</description>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data.
Shall have an Enumerated Value of one less than the value in Bit Stored (0028,0101).</description>
    </entry>
    <entry group="0028" element="0103" name="Pixel Representation" type="1">
      <description>Data representation of the pixel samples.
Shall have the Enumerated Value:
0000H = Unsigned Integer.</description>
    </entry>
    <entry group="0028" element="1040" name="Pixel Intensity Relationship" type="1">
      <description>The relationship between the Pixel sample values and the X-Ray beam intensity.
Enumerated Values:
LIN = Linearly proportional to X-Ray beam intensity
LOG = Logarithmically proportional to X-Ray beam intensity
See C.8.11.3.1.2 for further explanation.</description>
      <section ref="C.8.11.3.1.2" name="">Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041) describe how the stored pixel values in Pixel Data (7FE0,0010) are related to the X-Ray beam intensity incident on the detector.
They do not define a transformation intended to be applied to the pixel data for presentation.
Note:  For example, if Pixel Intensity Relationship (0028,1040) is LIN and Pixel Intensity Relationship Sign (0028,1041) is -1, then lower values of Pixel Data (7FE0,0010) indicate higher X-Ray beam intensities corresponding to less radiographically dense regions projected on the image such as through air, and higher values of Pixel Data (7FE0,0010) indicate lower X-Ray beam intensities corresponding to more radiographically dense regions projected on the image such as through bone and radio-opaque contrast agents.

The transformation to be applied to the pixel data for presentation is defined by the successive application of the conceptual Modality LUT, the VOI Attributes and the conceptual Presentation LUT. This shall result in the output of P-Values.
Rescale Slope (0028,1053) and Rescale Intercept (0028,1052) define a linear subset of a conceptual Modality LUT transformation. For IODs that include this Module, these Attributes define an identity transformation. IODs that include the DX Image Module shall not include the Modality LUT Module.
The Presentation LUT Shape (2050,0020) defines a subset of a conceptual Presentation LUT. For IODs that include this Module, this Attribute defines an identity transformation or inverse identity transformation. IODs that include the DX Image Module shall not include the Presentation LUT Module.
Photometric Interpretation (0028,0004) indicates whether lower values that are the output of the VOI Attributes should be displayed as darker or lighter. Since the output of the equivalent of a conceptual Presentation LUT is in P-Values, which are defined in PS 3.14 such that lower values correspond to lower luminance levels, then the definition of the Presentation LUT Shape (2050,0020), otherwise intended to be an identity transformation, must take into account the effect of the value specified for Photometric Interpretation (0028,0004).
Note:  Regardless of the values of Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041), the grayscale transformations to be applied to the Pixel Data (7FE0,0010) are defined by the equivalent of the Modality LUT (Rescale Slope (0028,1053) and Rescale Intercept (0028,1052)), Value of Interest Attributes, Photometric Interpretation (0028,0004) and the equivalent of the Presentation LUT (Presentation LUT Shape (2050,0020)). However, the combination of the grayscale transformations and the description of the pixel intensity relationship, together define whether, for example, air is expected to be displayed as black or white.

</section>
    </entry>
    <entry group="0028" element="1041" name="Pixel Intensity Relationship Sign" type="1">
      <description>The sign of the relationship between the Pixel sample values stored in Pixel Data (7FE0,0010) and the X-Ray beam intensity.
Enumerated Values;
1 = Lower pixel values correspond to less X-Ray beam intensity
-1 = Higher pixel values correspond to less X-Ray beam intensity
See C.8.11.3.1.2 for further explanation.</description>
      <section ref="C.8.11.3.1.2" name="">Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041) describe how the stored pixel values in Pixel Data (7FE0,0010) are related to the X-Ray beam intensity incident on the detector.
They do not define a transformation intended to be applied to the pixel data for presentation.
Note:  For example, if Pixel Intensity Relationship (0028,1040) is LIN and Pixel Intensity Relationship Sign (0028,1041) is -1, then lower values of Pixel Data (7FE0,0010) indicate higher X-Ray beam intensities corresponding to less radiographically dense regions projected on the image such as through air, and higher values of Pixel Data (7FE0,0010) indicate lower X-Ray beam intensities corresponding to more radiographically dense regions projected on the image such as through bone and radio-opaque contrast agents.

The transformation to be applied to the pixel data for presentation is defined by the successive application of the conceptual Modality LUT, the VOI Attributes and the conceptual Presentation LUT. This shall result in the output of P-Values.
Rescale Slope (0028,1053) and Rescale Intercept (0028,1052) define a linear subset of a conceptual Modality LUT transformation. For IODs that include this Module, these Attributes define an identity transformation. IODs that include the DX Image Module shall not include the Modality LUT Module.
The Presentation LUT Shape (2050,0020) defines a subset of a conceptual Presentation LUT. For IODs that include this Module, this Attribute defines an identity transformation or inverse identity transformation. IODs that include the DX Image Module shall not include the Presentation LUT Module.
Photometric Interpretation (0028,0004) indicates whether lower values that are the output of the VOI Attributes should be displayed as darker or lighter. Since the output of the equivalent of a conceptual Presentation LUT is in P-Values, which are defined in PS 3.14 such that lower values correspond to lower luminance levels, then the definition of the Presentation LUT Shape (2050,0020), otherwise intended to be an identity transformation, must take into account the effect of the value specified for Photometric Interpretation (0028,0004).
Note:  Regardless of the values of Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041), the grayscale transformations to be applied to the Pixel Data (7FE0,0010) are defined by the equivalent of the Modality LUT (Rescale Slope (0028,1053) and Rescale Intercept (0028,1052)), Value of Interest Attributes, Photometric Interpretation (0028,0004) and the equivalent of the Presentation LUT (Presentation LUT Shape (2050,0020)). However, the combination of the grayscale transformations and the description of the pixel intensity relationship, together define whether, for example, air is expected to be displayed as black or white.

</section>
    </entry>
    <entry group="0028" element="1052" name="Rescale Intercept" type="1">
      <description>The value b in the relationship between stored values (SV) in Pixel Data (7FE0,0010) and the output units specified in Rescale Type (0028,1054).
Output units = m*SV + b.
Enumerated Value: 0
See C.8.11.3.1.2 for further explanation.</description>
      <section ref="C.8.11.3.1.2" name="">Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041) describe how the stored pixel values in Pixel Data (7FE0,0010) are related to the X-Ray beam intensity incident on the detector.
They do not define a transformation intended to be applied to the pixel data for presentation.
Note:  For example, if Pixel Intensity Relationship (0028,1040) is LIN and Pixel Intensity Relationship Sign (0028,1041) is -1, then lower values of Pixel Data (7FE0,0010) indicate higher X-Ray beam intensities corresponding to less radiographically dense regions projected on the image such as through air, and higher values of Pixel Data (7FE0,0010) indicate lower X-Ray beam intensities corresponding to more radiographically dense regions projected on the image such as through bone and radio-opaque contrast agents.

The transformation to be applied to the pixel data for presentation is defined by the successive application of the conceptual Modality LUT, the VOI Attributes and the conceptual Presentation LUT. This shall result in the output of P-Values.
Rescale Slope (0028,1053) and Rescale Intercept (0028,1052) define a linear subset of a conceptual Modality LUT transformation. For IODs that include this Module, these Attributes define an identity transformation. IODs that include the DX Image Module shall not include the Modality LUT Module.
The Presentation LUT Shape (2050,0020) defines a subset of a conceptual Presentation LUT. For IODs that include this Module, this Attribute defines an identity transformation or inverse identity transformation. IODs that include the DX Image Module shall not include the Presentation LUT Module.
Photometric Interpretation (0028,0004) indicates whether lower values that are the output of the VOI Attributes should be displayed as darker or lighter. Since the output of the equivalent of a conceptual Presentation LUT is in P-Values, which are defined in PS 3.14 such that lower values correspond to lower luminance levels, then the definition of the Presentation LUT Shape (2050,0020), otherwise intended to be an identity transformation, must take into account the effect of the value specified for Photometric Interpretation (0028,0004).
Note:  Regardless of the values of Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041), the grayscale transformations to be applied to the Pixel Data (7FE0,0010) are defined by the equivalent of the Modality LUT (Rescale Slope (0028,1053) and Rescale Intercept (0028,1052)), Value of Interest Attributes, Photometric Interpretation (0028,0004) and the equivalent of the Presentation LUT (Presentation LUT Shape (2050,0020)). However, the combination of the grayscale transformations and the description of the pixel intensity relationship, together define whether, for example, air is expected to be displayed as black or white.

</section>
    </entry>
    <entry group="0028" element="1053" name="Rescale Slope" type="1">
      <description>m in the equation specified by Rescale Intercept (0028,1052).
Enumerated Value: 1
See C.8.11.3.1.2 for further explanation.</description>
      <section ref="C.8.11.3.1.2" name="">Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041) describe how the stored pixel values in Pixel Data (7FE0,0010) are related to the X-Ray beam intensity incident on the detector.
They do not define a transformation intended to be applied to the pixel data for presentation.
Note:  For example, if Pixel Intensity Relationship (0028,1040) is LIN and Pixel Intensity Relationship Sign (0028,1041) is -1, then lower values of Pixel Data (7FE0,0010) indicate higher X-Ray beam intensities corresponding to less radiographically dense regions projected on the image such as through air, and higher values of Pixel Data (7FE0,0010) indicate lower X-Ray beam intensities corresponding to more radiographically dense regions projected on the image such as through bone and radio-opaque contrast agents.

The transformation to be applied to the pixel data for presentation is defined by the successive application of the conceptual Modality LUT, the VOI Attributes and the conceptual Presentation LUT. This shall result in the output of P-Values.
Rescale Slope (0028,1053) and Rescale Intercept (0028,1052) define a linear subset of a conceptual Modality LUT transformation. For IODs that include this Module, these Attributes define an identity transformation. IODs that include the DX Image Module shall not include the Modality LUT Module.
The Presentation LUT Shape (2050,0020) defines a subset of a conceptual Presentation LUT. For IODs that include this Module, this Attribute defines an identity transformation or inverse identity transformation. IODs that include the DX Image Module shall not include the Presentation LUT Module.
Photometric Interpretation (0028,0004) indicates whether lower values that are the output of the VOI Attributes should be displayed as darker or lighter. Since the output of the equivalent of a conceptual Presentation LUT is in P-Values, which are defined in PS 3.14 such that lower values correspond to lower luminance levels, then the definition of the Presentation LUT Shape (2050,0020), otherwise intended to be an identity transformation, must take into account the effect of the value specified for Photometric Interpretation (0028,0004).
Note:  Regardless of the values of Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041), the grayscale transformations to be applied to the Pixel Data (7FE0,0010) are defined by the equivalent of the Modality LUT (Rescale Slope (0028,1053) and Rescale Intercept (0028,1052)), Value of Interest Attributes, Photometric Interpretation (0028,0004) and the equivalent of the Presentation LUT (Presentation LUT Shape (2050,0020)). However, the combination of the grayscale transformations and the description of the pixel intensity relationship, together define whether, for example, air is expected to be displayed as black or white.

</section>
    </entry>
    <entry group="0028" element="1054" name="Rescale Type" type="1">
      <description>Specifies the output units of Rescale Slope (0028,1053) and Rescale Intercept (0028,1052).
Enumerated Value: US = Unspecified
See C.8.11.3.1.2 for further explanation.</description>
      <section ref="C.8.11.3.1.2" name="">Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041) describe how the stored pixel values in Pixel Data (7FE0,0010) are related to the X-Ray beam intensity incident on the detector.
They do not define a transformation intended to be applied to the pixel data for presentation.
Note:  For example, if Pixel Intensity Relationship (0028,1040) is LIN and Pixel Intensity Relationship Sign (0028,1041) is -1, then lower values of Pixel Data (7FE0,0010) indicate higher X-Ray beam intensities corresponding to less radiographically dense regions projected on the image such as through air, and higher values of Pixel Data (7FE0,0010) indicate lower X-Ray beam intensities corresponding to more radiographically dense regions projected on the image such as through bone and radio-opaque contrast agents.

The transformation to be applied to the pixel data for presentation is defined by the successive application of the conceptual Modality LUT, the VOI Attributes and the conceptual Presentation LUT. This shall result in the output of P-Values.
Rescale Slope (0028,1053) and Rescale Intercept (0028,1052) define a linear subset of a conceptual Modality LUT transformation. For IODs that include this Module, these Attributes define an identity transformation. IODs that include the DX Image Module shall not include the Modality LUT Module.
The Presentation LUT Shape (2050,0020) defines a subset of a conceptual Presentation LUT. For IODs that include this Module, this Attribute defines an identity transformation or inverse identity transformation. IODs that include the DX Image Module shall not include the Presentation LUT Module.
Photometric Interpretation (0028,0004) indicates whether lower values that are the output of the VOI Attributes should be displayed as darker or lighter. Since the output of the equivalent of a conceptual Presentation LUT is in P-Values, which are defined in PS 3.14 such that lower values correspond to lower luminance levels, then the definition of the Presentation LUT Shape (2050,0020), otherwise intended to be an identity transformation, must take into account the effect of the value specified for Photometric Interpretation (0028,0004).
Note:  Regardless of the values of Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041), the grayscale transformations to be applied to the Pixel Data (7FE0,0010) are defined by the equivalent of the Modality LUT (Rescale Slope (0028,1053) and Rescale Intercept (0028,1052)), Value of Interest Attributes, Photometric Interpretation (0028,0004) and the equivalent of the Presentation LUT (Presentation LUT Shape (2050,0020)). However, the combination of the grayscale transformations and the description of the pixel intensity relationship, together define whether, for example, air is expected to be displayed as black or white.

</section>
    </entry>
    <entry group="2050" element="0020" name="Presentation LUT Shape" type="1">
      <description>Specifies an identity transformation for the Presentation LUT, other than to account for the value of Photometric Interpretation (0028,0004), such that the output of all grayscale transformations defined in the IOD containing this Module are defined to be P-Values.
Enumerated Values:
IDENTITY - output is in P-Values - shall be used if Photometric Interpretation (0028,0004) is MONOCHROME2.
INVERSE - output after inversion is in P-Values - shall be used if Photometric Interpretation (0028,0004) is MONOCHROME1.
See C.8.11.3.1.2 for further explanation.</description>
      <section ref="C.8.11.3.1.2" name="">Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041) describe how the stored pixel values in Pixel Data (7FE0,0010) are related to the X-Ray beam intensity incident on the detector.
They do not define a transformation intended to be applied to the pixel data for presentation.
Note:  For example, if Pixel Intensity Relationship (0028,1040) is LIN and Pixel Intensity Relationship Sign (0028,1041) is -1, then lower values of Pixel Data (7FE0,0010) indicate higher X-Ray beam intensities corresponding to less radiographically dense regions projected on the image such as through air, and higher values of Pixel Data (7FE0,0010) indicate lower X-Ray beam intensities corresponding to more radiographically dense regions projected on the image such as through bone and radio-opaque contrast agents.

The transformation to be applied to the pixel data for presentation is defined by the successive application of the conceptual Modality LUT, the VOI Attributes and the conceptual Presentation LUT. This shall result in the output of P-Values.
Rescale Slope (0028,1053) and Rescale Intercept (0028,1052) define a linear subset of a conceptual Modality LUT transformation. For IODs that include this Module, these Attributes define an identity transformation. IODs that include the DX Image Module shall not include the Modality LUT Module.
The Presentation LUT Shape (2050,0020) defines a subset of a conceptual Presentation LUT. For IODs that include this Module, this Attribute defines an identity transformation or inverse identity transformation. IODs that include the DX Image Module shall not include the Presentation LUT Module.
Photometric Interpretation (0028,0004) indicates whether lower values that are the output of the VOI Attributes should be displayed as darker or lighter. Since the output of the equivalent of a conceptual Presentation LUT is in P-Values, which are defined in PS 3.14 such that lower values correspond to lower luminance levels, then the definition of the Presentation LUT Shape (2050,0020), otherwise intended to be an identity transformation, must take into account the effect of the value specified for Photometric Interpretation (0028,0004).
Note:  Regardless of the values of Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041), the grayscale transformations to be applied to the Pixel Data (7FE0,0010) are defined by the equivalent of the Modality LUT (Rescale Slope (0028,1053) and Rescale Intercept (0028,1052)), Value of Interest Attributes, Photometric Interpretation (0028,0004) and the equivalent of the Presentation LUT (Presentation LUT Shape (2050,0020)). However, the combination of the grayscale transformations and the description of the pixel intensity relationship, together define whether, for example, air is expected to be displayed as black or white.

</section>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1">
      <description>Specifies whether an Image has undergone lossy compression. Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5 for further explanation.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2112" name="Lossy Image Compression Ratio" type="1C">
      <description>See C.7.6.1.1.5 for further explanation.
Required if Lossy Compression has been performed on the Image.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0008" element="2111" name="Derivation Description" type="3">
      <description>A text description of how this image was derived.
See C.8.11.3.1.4 for further explanation.</description>
      <section ref="C.8.11.3.1.4" name="">If an Image is identified to be a Derived image in Image Type (0008,0008), Derivation Description (0008,2111) is an optional and implementation specific text description of the way the image was derived from an original image. As applied to DX images, it may be used to describe derivation operations such as edge enhancement, temporal filtering, digital subtraction, or other linear and non-linear transformations.
</section>
    </entry>
    <entry group="0018" element="1400" name="Acquisition Device Processing Description" type="3">
      <description>Indicates any visual processing performed on the images prior to exchange.
See C.8.11.3.1.3 for further explanation.</description>
      <section ref="C.8.11.3.1.3" name="">Acquisition Device Processing Description (0018,1400) provides some indication in human readable text of the digital processing on the images before exchange. Examples of this processing are: edge enhanced, subtracted, time filtered, gamma corrected, convolved (spatially filtered).
</section>
    </entry>
    <entry group="0018" element="1401" name="Acquisition Device Processing Code" type="3">
      <description>Code representing the device-specific processing associated with the image (e.g. Organ Filtering code)
Note: This Code is manufacturer specific but provides useful annotation information to the knowledgeable observer.</description>
    </entry>
    <entry group="0020" element="0020" name="Patient Orientation" type="1">
      <description>Patient direction of the rows and columns of the image.
See C.7.6.1.1.1 for further explanation.</description>
      <section ref="C.7.6.1.1.1" name="">The Patient Orientation (0020,0020) relative to the image plane shall be specified by two values that designate the anatomical direction of the positive row axis (left to right) and the positive column axis (top to bottom). The first entry is the direction of the rows, given by the direction of the last pixel in the first row from the first pixel in that row. The second entry is the direction of the columns, given by the direction of the last pixel in the first column from the first pixel in that column.
Anatomical direction shall be designated by the capital letters: A (anterior), P (posterior), R (right), L (left), H (head), F (foot). Each value of the orientation attribute shall contain at least one of these characters. If refinements in the orientation descriptions are to be specified, then they shall be designated by one or two additional letters in each value. Within each value, the letters shall be ordered with the principal orientation designated in the first character.
</section>
    </entry>
    <entry group="0050" element="0004" name="Calibration Image" type="3">
      <description>Indicates whether a reference object (phantom) of known size is present in the image and was used for calibration. Enumerated Values:
YES
NO
Device is identified using the Device module. See C.7.6.12 for further explanation.</description>
      <section ref="C.7.6.12" name="">Table C.7-18 describes the Attributes of devices or calibration objects (e.g., catheters, markers, baskets) that are associated with a study and/or image.
Table C.7-18
DEVICE MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Device Sequence" meaning="(0050,0010)"/><term value="&gt;Include ‘Code Sequence Macro’ Table 8.8-1" meaning="Baseline Context ID is 4051."/><term value="&gt;Manufacturer" meaning="(0008,0070)"/><term value="&gt;Manufacturer’s Model Name" meaning="(0008,1090)"/><term value="&gt;Device Serial Number" meaning="(0018,1000)"/><term value="&gt;Device ID" meaning="(0018,1003)"/><term value="&gt;Device Length" meaning="(0050,0014)"/><term value="&gt;Device Diameter" meaning="(0050,0016)"/><term value="&gt;Device Diameter Units" meaning="(0050,0017)"/><term value="&gt;Device Volume" meaning="(0050,0018)"/><term value="&gt;Inter-Marker Distance" meaning="(0050,0019)"/><term value="&gt;Device Description" meaning="(0050,0020)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0301" name="Burned In Annotation" type="1">
      <description>Indicates whether or not image contains sufficient burned in annotation to identify the patient and date the image was acquired.
Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="0028" element="3010" name="VOI LUT Sequence" type="1C">
      <description>Defines a sequence of VOI LUTs.
See C.8.11.3.1.5 for further explanation.
One or more Items may be included in this Sequence.
Required if Presentation Intent Type (0008,0068) is FOR PRESENTATION and Window Center (0028,1050) is not present. May also be present if Window Center (0028,1050) is present.</description>
      <section ref="C.8.11.3.1.5" name="">The Attributes of the VOI LUT Module (C.11.2) are specialized in the DX Image Module.
Window Center (0028,1050) and Window Width (0028,1051) specify a linear conversion (unless otherwise specified by the value of VOI LUT Function (0028,1056); see C.11.2.1.3) from the output of the (conceptual) Modality LUT values to the input to the (conceptual) Presentation LUT. Window Center contains the value that is the center of the window. Window Width contains the width of the window.
The application of the Window Center (0028,1050) and Window Width (0028,1051) shall not produce a signed result.
Note:  If the Presentation LUT Shape (2050,0020) is IDENTITY, then the result of applying the Window Center (0028,1050) and Window Width (0028,1051) is P-Values.

If multiple values are present, both Attributes shall have the same number of values and shall be considered as pairs. Multiple values indicate that multiple alternative views should be presented.
The VOI LUT Sequence specifes a (potentially non-linear) conversion from the output of the (conceptual) Modality LUT values to the input to the (conceptual) Presentation LUT.
If multiple items are present in VOI LUT Sequence (0028,3010), only one shall be applied. Multiple items indicate that multiple alternative views should be presented.
If any VOI LUT Attributes are included by an Image, a Window Width and Window Center or the VOI LUT Table, but not both, shall be applied to the Image for display. Inclusion of both indicates that multiple alternative views should be presented.
The three values of the LUT Descriptor (0028,3002) describe the format of the LUT Data (0028,3006).
The first value is the number of entries in the lookup table.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the LUT. All image pixel values less than the first value mapped are also mapped to the first entry in the LUT Data. An image pixel value one greater than the first value mapped is mapped to the second entry in the LUT Data. Subsequent image pixel values are mapped to the subsequent entries in the LUT Data up to an image pixel value equal to number of entries + first value mapped - 1 which is mapped to the last entry in the LUT Data. Image pixel values greater than number of entries + first value mapped are also mapped to the last entry in the LUT Data.
The third value specifies the number of bits for each entry in the LUT Data (analogous to “bits stored”). It shall be between 10-16. The LUT Data shall be stored in a format equivalent to 16 “bits allocated” and “high bit” equal to “bits stored” - 1. The third value conveys the range of LUT entry values. These unsigned LUT entry values shall range between 0 and 2 n -1, where n is the third value of the LUT Descriptor.
Notes:  1. The third value is restricted in the VOI LUT Module to 8 or 16 but is specialized here.
  2. The first and second values are not specialized and are the same as in the VOI LUT Module.

The LUT Data (0028,3006) contains the LUT entry values.
</section>
    </entry>
    <entry group="0028" element="3002" name="&gt;LUT Descriptor" type="1C">
      <description>Specifies the format of the LUT Data in this Sequence.
See C.8.11.3.1.5 for further explanation.
Required if the VOI LUT Sequence (0028,3010) is sent.</description>
      <section ref="C.8.11.3.1.5" name="">The Attributes of the VOI LUT Module (C.11.2) are specialized in the DX Image Module.
Window Center (0028,1050) and Window Width (0028,1051) specify a linear conversion (unless otherwise specified by the value of VOI LUT Function (0028,1056); see C.11.2.1.3) from the output of the (conceptual) Modality LUT values to the input to the (conceptual) Presentation LUT. Window Center contains the value that is the center of the window. Window Width contains the width of the window.
The application of the Window Center (0028,1050) and Window Width (0028,1051) shall not produce a signed result.
Note:  If the Presentation LUT Shape (2050,0020) is IDENTITY, then the result of applying the Window Center (0028,1050) and Window Width (0028,1051) is P-Values.

If multiple values are present, both Attributes shall have the same number of values and shall be considered as pairs. Multiple values indicate that multiple alternative views should be presented.
The VOI LUT Sequence specifes a (potentially non-linear) conversion from the output of the (conceptual) Modality LUT values to the input to the (conceptual) Presentation LUT.
If multiple items are present in VOI LUT Sequence (0028,3010), only one shall be applied. Multiple items indicate that multiple alternative views should be presented.
If any VOI LUT Attributes are included by an Image, a Window Width and Window Center or the VOI LUT Table, but not both, shall be applied to the Image for display. Inclusion of both indicates that multiple alternative views should be presented.
The three values of the LUT Descriptor (0028,3002) describe the format of the LUT Data (0028,3006).
The first value is the number of entries in the lookup table.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the LUT. All image pixel values less than the first value mapped are also mapped to the first entry in the LUT Data. An image pixel value one greater than the first value mapped is mapped to the second entry in the LUT Data. Subsequent image pixel values are mapped to the subsequent entries in the LUT Data up to an image pixel value equal to number of entries + first value mapped - 1 which is mapped to the last entry in the LUT Data. Image pixel values greater than number of entries + first value mapped are also mapped to the last entry in the LUT Data.
The third value specifies the number of bits for each entry in the LUT Data (analogous to “bits stored”). It shall be between 10-16. The LUT Data shall be stored in a format equivalent to 16 “bits allocated” and “high bit” equal to “bits stored” - 1. The third value conveys the range of LUT entry values. These unsigned LUT entry values shall range between 0 and 2 n -1, where n is the third value of the LUT Descriptor.
Notes:  1. The third value is restricted in the VOI LUT Module to 8 or 16 but is specialized here.
  2. The first and second values are not specialized and are the same as in the VOI LUT Module.

The LUT Data (0028,3006) contains the LUT entry values.
</section>
    </entry>
    <entry group="0028" element="3003" name="&gt;LUT Explanation" type="3">
      <description>Free form text explanation of the meaning of the LUT.</description>
    </entry>
    <entry group="0028" element="3006" name="&gt;LUT Data" type="1C">
      <description>LUT Data in this Sequence.
Required if the VOI LUT Sequence (0028,3010) is sent.</description>
    </entry>
    <entry group="0028" element="1050" name="Window Center" type="1C">
      <description>Defines a Window Center for display.
See C.8.11.3.1.5 for further explanation.
Required if Presentation Intent Type (0008,0068) is FOR PRESENTATION and VOI LUT Sequence (0028,3010) is not present. May also be present if VOI LUT Sequence (0028,3010) is present.</description>
      <section ref="C.8.11.3.1.5" name="">The Attributes of the VOI LUT Module (C.11.2) are specialized in the DX Image Module.
Window Center (0028,1050) and Window Width (0028,1051) specify a linear conversion (unless otherwise specified by the value of VOI LUT Function (0028,1056); see C.11.2.1.3) from the output of the (conceptual) Modality LUT values to the input to the (conceptual) Presentation LUT. Window Center contains the value that is the center of the window. Window Width contains the width of the window.
The application of the Window Center (0028,1050) and Window Width (0028,1051) shall not produce a signed result.
Note:  If the Presentation LUT Shape (2050,0020) is IDENTITY, then the result of applying the Window Center (0028,1050) and Window Width (0028,1051) is P-Values.

If multiple values are present, both Attributes shall have the same number of values and shall be considered as pairs. Multiple values indicate that multiple alternative views should be presented.
The VOI LUT Sequence specifes a (potentially non-linear) conversion from the output of the (conceptual) Modality LUT values to the input to the (conceptual) Presentation LUT.
If multiple items are present in VOI LUT Sequence (0028,3010), only one shall be applied. Multiple items indicate that multiple alternative views should be presented.
If any VOI LUT Attributes are included by an Image, a Window Width and Window Center or the VOI LUT Table, but not both, shall be applied to the Image for display. Inclusion of both indicates that multiple alternative views should be presented.
The three values of the LUT Descriptor (0028,3002) describe the format of the LUT Data (0028,3006).
The first value is the number of entries in the lookup table.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the LUT. All image pixel values less than the first value mapped are also mapped to the first entry in the LUT Data. An image pixel value one greater than the first value mapped is mapped to the second entry in the LUT Data. Subsequent image pixel values are mapped to the subsequent entries in the LUT Data up to an image pixel value equal to number of entries + first value mapped - 1 which is mapped to the last entry in the LUT Data. Image pixel values greater than number of entries + first value mapped are also mapped to the last entry in the LUT Data.
The third value specifies the number of bits for each entry in the LUT Data (analogous to “bits stored”). It shall be between 10-16. The LUT Data shall be stored in a format equivalent to 16 “bits allocated” and “high bit” equal to “bits stored” - 1. The third value conveys the range of LUT entry values. These unsigned LUT entry values shall range between 0 and 2 n -1, where n is the third value of the LUT Descriptor.
Notes:  1. The third value is restricted in the VOI LUT Module to 8 or 16 but is specialized here.
  2. The first and second values are not specialized and are the same as in the VOI LUT Module.

The LUT Data (0028,3006) contains the LUT entry values.
</section>
    </entry>
    <entry group="0028" element="1051" name="Window Width" type="1C">
      <description>Window Width for display. See C.8.11.3.1.5 for further explanation.
Required if Window Center (0028,1050) is sent.</description>
      <section ref="C.8.11.3.1.5" name="">The Attributes of the VOI LUT Module (C.11.2) are specialized in the DX Image Module.
Window Center (0028,1050) and Window Width (0028,1051) specify a linear conversion (unless otherwise specified by the value of VOI LUT Function (0028,1056); see C.11.2.1.3) from the output of the (conceptual) Modality LUT values to the input to the (conceptual) Presentation LUT. Window Center contains the value that is the center of the window. Window Width contains the width of the window.
The application of the Window Center (0028,1050) and Window Width (0028,1051) shall not produce a signed result.
Note:  If the Presentation LUT Shape (2050,0020) is IDENTITY, then the result of applying the Window Center (0028,1050) and Window Width (0028,1051) is P-Values.

If multiple values are present, both Attributes shall have the same number of values and shall be considered as pairs. Multiple values indicate that multiple alternative views should be presented.
The VOI LUT Sequence specifes a (potentially non-linear) conversion from the output of the (conceptual) Modality LUT values to the input to the (conceptual) Presentation LUT.
If multiple items are present in VOI LUT Sequence (0028,3010), only one shall be applied. Multiple items indicate that multiple alternative views should be presented.
If any VOI LUT Attributes are included by an Image, a Window Width and Window Center or the VOI LUT Table, but not both, shall be applied to the Image for display. Inclusion of both indicates that multiple alternative views should be presented.
The three values of the LUT Descriptor (0028,3002) describe the format of the LUT Data (0028,3006).
The first value is the number of entries in the lookup table.
The second value is the first stored pixel value mapped. This pixel value is mapped to the first entry in the LUT. All image pixel values less than the first value mapped are also mapped to the first entry in the LUT Data. An image pixel value one greater than the first value mapped is mapped to the second entry in the LUT Data. Subsequent image pixel values are mapped to the subsequent entries in the LUT Data up to an image pixel value equal to number of entries + first value mapped - 1 which is mapped to the last entry in the LUT Data. Image pixel values greater than number of entries + first value mapped are also mapped to the last entry in the LUT Data.
The third value specifies the number of bits for each entry in the LUT Data (analogous to “bits stored”). It shall be between 10-16. The LUT Data shall be stored in a format equivalent to 16 “bits allocated” and “high bit” equal to “bits stored” - 1. The third value conveys the range of LUT entry values. These unsigned LUT entry values shall range between 0 and 2 n -1, where n is the third value of the LUT Descriptor.
Notes:  1. The third value is restricted in the VOI LUT Module to 8 or 16 but is specialized here.
  2. The first and second values are not specialized and are the same as in the VOI LUT Module.

The LUT Data (0028,3006) contains the LUT entry values.
</section>
    </entry>
    <entry group="0028" element="1055" name="Window Center &amp; Width Explanation" type="3">
      <description>Free form explanation of the meaning of the Window Center and Width. Multiple values correspond to multiple Window Center and Width values.</description>
    </entry>
  </module>
  <module ref="C.8.11.4" table="C.8-71" name="DX Detector Module Attributes">
    <include ref="Include 'Digital X-Ray Detector Macro' Table C.8-71b"/>
    <entry group="0018" element="7014" name="Detector Active Time" type="3">
      <description>Time in mSec that the detector is active during acquisition of this image.
Note: This activation window overlaps the time of the X-Ray exposure as defined by Exposure Time (0018,1150) and Detector Activation Offset From Exposure (0018,7016).</description>
    </entry>
    <entry group="0018" element="7016" name="Detector Activation Offset From Exposure" type="3">
      <description>Offset time in mSec that the detector becomes active after the X-Ray beam is turned on during acquisition of this image. May be negative.</description>
    </entry>
    <entry group="0018" element="1147" name="Field of View Shape" type="3">
      <description>Shape of the Field of View, that is the image pixels stored in Pixel Data (7FE0,0010).
Enumerated Values:
RECTANGLE
ROUND
HEXAGONAL</description>
    </entry>
    <entry group="0018" element="1149" name="Field of View Dimension(s)" type="3">
      <description>Dimensions in mm of the Field of View, that is the image pixels stored in Pixel Data (7FE0,0010). If Field of View Shape (0018,1147) is:
RECTANGLE: row dimension followed by column.
ROUND: diameter.
HEXAGONAL: diameter of a circumscribed circle.</description>
    </entry>
    <entry group="0018" element="7030" name="Field of View Origin" type="1C">
      <description>Offset of the TLHC of a rectangle circumscribing the Field of View, that is the image pixels stored in Pixel Data (7FE0,0010), before rotation or flipping, from the TLHC of the physical detector area measured in physical detector pixels as a row offset followed by a column offset.
Required if Field of View Rotation (0018,7032) or Field of View Horizontal Flip (0018,7034) is present.
See C.8.11.4.1.1 for further explanation.</description>
      <section ref="C.8.11.4.1.1" name="">The relationship between the Physical Detector Area, the Active Detector Area, the Field of View (what is stored in the Pixel Data (7FE0,0010)), the Exposed Area (after X-Ray Collimation) and the Displayed Area is illustrated in the following diagrams.
Note:  Some of these Attributes relate the image data to manufacturer specific characteristics of the detector that may be used for quality control purposes, e.g. correlation of image artifacts with a detector defect map, analysis of noise performance, etc.

The Displayed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the Display Shutter Module (see section C.7.6.11). If this Module is not present or supported, then the Displayed Area is equal to the Field of View.
The Exposed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the X-Ray Collimator Module (see section C.8.7.3).
For the Digital X-Ray IODs, the Field of View is usually rectangular in shape and the same size as the stored Pixel Data (7FE0,0010). The shape and size of the Field of View and the spacing of the pixels are defined by the following Attributes:
- Field of View Shape (0018,1147),
- Field of View Dimensions (0018,1149),
- Imager Pixel Spacing (0018,1164),
- Rows (0028,0010),
- Columns (0028,0011)

The following Attributes define the relationship of the Field of View to the Physical Detector Area:
- Field of View Origin (0018,7030),
- Field of View Rotation (0018,7032),
- Field of View Horizontal Flip (0018,7034).

For the Digital X-Ray IODs, the Active Area, i.e. that part of the detector matrix that was activated for this exposure, is usually rectangular in shape. The shape and size of the Active Area and the size and spacing of the detectors are defined by the following Attributes:
- Detector Active Shape (0018,7024),
- Detector Active Dimensions (0018,7026),
- Detector Element Physical Size (0018,7020),
- Detector Element Spacing (0018,7022).

Notes:  1. The Detector Element Physical Size (0018,7020) and Detector Element Spacing (0018,7022) may be different if there are insensitive regions between each detector.
  2. This model of description is not able to accurately describe multiple matrices of detectors that are “tiled” to produce a single image.

The following optional Attribute defines the relationship of the Active Area to the Physical Detector Area:
- Detector Active Origin (0018,7028).

The relationship between detectors and stored image pixels is defined by Detector Binning (0018,701A) which specifies how many detectors, in each of the row and column directions, contribute to (are pooled or averaged to form) a single stored image pixel.
Note:  Detector Binning (0018,701A) may have values less than one if sub-sampling is used to derive an image with higher spatial resolution than the detector matrix.



Figure C.8-14
Explanation of DX Detector Attributes




Figure C.8-15
Explanation of DX Detector Attributes
</section>
    </entry>
    <entry group="0018" element="7032" name="Field of View Rotation" type="1C">
      <description>Clockwise rotation in degrees of Field of View, that is the image pixels stored in Pixel Data (7FE0,0010), relative to the physical detector.
Enumerated Values:
0, 90, 180, 270
Required if Field of View Horizontal Flip (0018,7034) is present.
See C.8.11.4.1.1 for further explanation.</description>
      <section ref="C.8.11.4.1.1" name="">The relationship between the Physical Detector Area, the Active Detector Area, the Field of View (what is stored in the Pixel Data (7FE0,0010)), the Exposed Area (after X-Ray Collimation) and the Displayed Area is illustrated in the following diagrams.
Note:  Some of these Attributes relate the image data to manufacturer specific characteristics of the detector that may be used for quality control purposes, e.g. correlation of image artifacts with a detector defect map, analysis of noise performance, etc.

The Displayed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the Display Shutter Module (see section C.7.6.11). If this Module is not present or supported, then the Displayed Area is equal to the Field of View.
The Exposed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the X-Ray Collimator Module (see section C.8.7.3).
For the Digital X-Ray IODs, the Field of View is usually rectangular in shape and the same size as the stored Pixel Data (7FE0,0010). The shape and size of the Field of View and the spacing of the pixels are defined by the following Attributes:
- Field of View Shape (0018,1147),
- Field of View Dimensions (0018,1149),
- Imager Pixel Spacing (0018,1164),
- Rows (0028,0010),
- Columns (0028,0011)

The following Attributes define the relationship of the Field of View to the Physical Detector Area:
- Field of View Origin (0018,7030),
- Field of View Rotation (0018,7032),
- Field of View Horizontal Flip (0018,7034).

For the Digital X-Ray IODs, the Active Area, i.e. that part of the detector matrix that was activated for this exposure, is usually rectangular in shape. The shape and size of the Active Area and the size and spacing of the detectors are defined by the following Attributes:
- Detector Active Shape (0018,7024),
- Detector Active Dimensions (0018,7026),
- Detector Element Physical Size (0018,7020),
- Detector Element Spacing (0018,7022).

Notes:  1. The Detector Element Physical Size (0018,7020) and Detector Element Spacing (0018,7022) may be different if there are insensitive regions between each detector.
  2. This model of description is not able to accurately describe multiple matrices of detectors that are “tiled” to produce a single image.

The following optional Attribute defines the relationship of the Active Area to the Physical Detector Area:
- Detector Active Origin (0018,7028).

The relationship between detectors and stored image pixels is defined by Detector Binning (0018,701A) which specifies how many detectors, in each of the row and column directions, contribute to (are pooled or averaged to form) a single stored image pixel.
Note:  Detector Binning (0018,701A) may have values less than one if sub-sampling is used to derive an image with higher spatial resolution than the detector matrix.



Figure C.8-14
Explanation of DX Detector Attributes




Figure C.8-15
Explanation of DX Detector Attributes
</section>
    </entry>
    <entry group="0018" element="7034" name="Field of View Horizontal Flip" type="1C">
      <description>Whether or not a horizontal flip has been applied to the Field of View, that is the image pixels stored in Pixel Data (7FE0,0010), after rotation relative to the physical detector as described in Field of View Rotation (0018,7032).
Enumerated Values:
NO
YES
Required if Field of View Rotation (0018,7032) is present.
See C.8.11.4.1.1 for further explanation.</description>
      <section ref="C.8.11.4.1.1" name="">The relationship between the Physical Detector Area, the Active Detector Area, the Field of View (what is stored in the Pixel Data (7FE0,0010)), the Exposed Area (after X-Ray Collimation) and the Displayed Area is illustrated in the following diagrams.
Note:  Some of these Attributes relate the image data to manufacturer specific characteristics of the detector that may be used for quality control purposes, e.g. correlation of image artifacts with a detector defect map, analysis of noise performance, etc.

The Displayed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the Display Shutter Module (see section C.7.6.11). If this Module is not present or supported, then the Displayed Area is equal to the Field of View.
The Exposed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the X-Ray Collimator Module (see section C.8.7.3).
For the Digital X-Ray IODs, the Field of View is usually rectangular in shape and the same size as the stored Pixel Data (7FE0,0010). The shape and size of the Field of View and the spacing of the pixels are defined by the following Attributes:
- Field of View Shape (0018,1147),
- Field of View Dimensions (0018,1149),
- Imager Pixel Spacing (0018,1164),
- Rows (0028,0010),
- Columns (0028,0011)

The following Attributes define the relationship of the Field of View to the Physical Detector Area:
- Field of View Origin (0018,7030),
- Field of View Rotation (0018,7032),
- Field of View Horizontal Flip (0018,7034).

For the Digital X-Ray IODs, the Active Area, i.e. that part of the detector matrix that was activated for this exposure, is usually rectangular in shape. The shape and size of the Active Area and the size and spacing of the detectors are defined by the following Attributes:
- Detector Active Shape (0018,7024),
- Detector Active Dimensions (0018,7026),
- Detector Element Physical Size (0018,7020),
- Detector Element Spacing (0018,7022).

Notes:  1. The Detector Element Physical Size (0018,7020) and Detector Element Spacing (0018,7022) may be different if there are insensitive regions between each detector.
  2. This model of description is not able to accurately describe multiple matrices of detectors that are “tiled” to produce a single image.

The following optional Attribute defines the relationship of the Active Area to the Physical Detector Area:
- Detector Active Origin (0018,7028).

The relationship between detectors and stored image pixels is defined by Detector Binning (0018,701A) which specifies how many detectors, in each of the row and column directions, contribute to (are pooled or averaged to form) a single stored image pixel.
Note:  Detector Binning (0018,701A) may have values less than one if sub-sampling is used to derive an image with higher spatial resolution than the detector matrix.



Figure C.8-14
Explanation of DX Detector Attributes




Figure C.8-15
Explanation of DX Detector Attributes
</section>
    </entry>
    <entry group="0018" element="1164" name="Imager Pixel Spacing" type="1">
      <description>Physical distance measured at the front plane of the detector housing between the center of each image pixel specified by a numeric pair - row spacing value(delimiter) column spacing value in mm. See 10.7.1.3 for further explanation of the value order.
The value of this attribute shall never be adjusted to account for correction for the effect of geometric magnification or calibration against an object of known size; Pixel Spacing (0028,0030) is specified for that purpose.</description>
    </entry>
    <include ref="Include Basic Pixel Spacing Calibration Macro (Table 10-10)"/>
    <entry group="0018" element="1007" name="Cassette ID" type="3">
      <description>Identifier of the cassette that contains the photostimulable phosphor plate, for CR acquisitions.</description>
    </entry>
    <entry group="0018" element="1004" name="Plate ID" type="3">
      <description>Identifier of the photostimulable phosphor plate, for CR acquisitions.</description>
    </entry>
  </module>
  <macro table="C.8-71b" name="Digital X Ray Detector Macro Attributes">
    <entry group="0018" element="7004" name="Detector Type" type="2">
      <description>The type of detector used to acquire this image.
Defined Terms:
DIRECT = X-Ray photoconductor
SCINTILLATOR = Phosphor used
STORAGE = Storage phosphor
FILM = Scanned film/screen</description>
    </entry>
    <entry group="0018" element="7005" name="Detector Configuration" type="3">
      <description>The physical configuration of the detector.
Defined Terms:
AREA = single or tiled detector
SLOT = scanned slot, slit or spot</description>
    </entry>
    <entry group="0018" element="7006" name="Detector Description" type="3">
      <description>Free text description of detector.</description>
    </entry>
    <entry group="0018" element="7008" name="Detector Mode" type="3">
      <description>Text description of operating mode of detector (implementation specific).</description>
    </entry>
    <entry group="0018" element="700A" name="Detector ID" type="3">
      <description>The ID or serial number of the detector used to acquire this image.</description>
    </entry>
    <entry group="0018" element="700C" name="Date of Last Detector Calibration" type="3">
      <description>The date on which the detector used to acquire this image as identified in Detector ID (0018,700A) was last calibrated.</description>
    </entry>
    <entry group="0018" element="700E" name="Time of Last Detector Calibration" type="3">
      <description>The time at which the detector used to acquire this image as identified in Detector ID (0018,700A) was last calibrated.</description>
    </entry>
    <entry group="0018" element="7010" name="Exposures on Detector Since Last Calibration" type="3">
      <description>Total number of X-Ray exposures that have been made on the detector used to acquire this image as identified in Detector ID (0018,700A) since it was calibrated.</description>
    </entry>
    <entry group="0018" element="7011" name="Exposures on Detector Since Manufactured" type="3">
      <description>Total number of X-Ray exposures that have been made on the detector used to acquire this image as identified in Detector ID (0018,700A) since it was manufactured.</description>
    </entry>
    <entry group="0018" element="7012" name="Detector Time Since Last Exposure" type="3">
      <description>Time in Seconds since an exposure was last made on this detector prior to the acquisition of this image.</description>
    </entry>
    <entry group="0018" element="701A" name="Detector Binning" type="3">
      <description>Number of active detectors used to generate a single pixel. Specified as number of row detectors per pixel then column.</description>
    </entry>
    <entry group="0018" element="702A" name="Detector Manufacturer Name" type="3">
      <description>Name of the manufacturer of the detector component of the acquisition system</description>
    </entry>
    <entry group="0018" element="702B" name="Detector Manufacturer's Model Name" type="3">
      <description>Model name of the detector component of the acquisition system</description>
    </entry>
    <entry group="0018" element="7000" name="Detector Conditions Nominal Flag" type="3">
      <description>Whether or not the detector is operating within normal tolerances during this image acquisition.
Enumerated Values:
YES
NO
Note: This flag is intended to indicate whether or not there may have been some compromise of the diagnostic quality of the image due to some condition such as over-temperature, etc.</description>
    </entry>
    <entry group="0018" element="7001" name="Detector Temperature" type="3">
      <description>Detector temperature during exposure in degrees Celsius.</description>
    </entry>
    <entry group="0018" element="6000" name="Sensitivity" type="3">
      <description>Detector sensitivity in manufacturer specific units.
Note: This value is intended to provide a single location where manufacturer specific information can be found for annotation on a display or film, that has meaning to a knowledgeable observer.
</description>
    </entry>
    <entry group="0018" element="7020" name="Detector Element Physical Size" type="3">
      <description>Physical dimensions of each detector element that comprises the detector matrix, in mm.
Expressed as row dimension followed by column.
Note: This may not be the same as Detector Element Spacing (0018,7022) due to the presence of spacing material between detector elements.</description>
    </entry>
    <entry group="0018" element="7022" name="Detector Element Spacing" type="3">
      <description>Physical distance between the center of each detector element, specified by a numeric pair - row spacing value(delimiter) column spacing value in mm. See 10.7.1.3 for further explanation of the value order.
Note: This may not be the same as the Imager Pixel Spacing (0018,1164), and should not be assumed to describe the stored image.</description>
    </entry>
    <entry group="0018" element="7024" name="Detector Active Shape" type="3">
      <description>Shape of the active area.
Enumerated Value:
RECTANGLE
ROUND
HEXAGONAL
Note: This may be different from the Field of View Shape (0018,1147), and should not be assumed to describe the stored image.</description>
    </entry>
    <entry group="0018" element="7026" name="Detector Active Dimension(s)" type="3">
      <description>Dimensions in mm of the active area.
If Detector Active Shape(0018,7024) is:
RECTANGLE: row dimension followed by column.
ROUND: diameter.
HEXAGONAL: diameter of a circumscribed circle.
Note: This may be different from the Field of View Dimensions (0018,1149), and should not be assumed to describe the stored image.</description>
    </entry>
    <entry group="0018" element="7028" name="Detector Active Origin" type="3">
      <description>Offset of the TLHC of a rectangle circumscribing the active detector area from the TLHC of a rectangle circumscribing the physical detector area, measured in physical detector pixels as a row offset followed by a column offset.
See C.8.11.4.1.1 for further explanation.</description>
      <section ref="C.8.11.4.1.1" name="">The relationship between the Physical Detector Area, the Active Detector Area, the Field of View (what is stored in the Pixel Data (7FE0,0010)), the Exposed Area (after X-Ray Collimation) and the Displayed Area is illustrated in the following diagrams.
Note:  Some of these Attributes relate the image data to manufacturer specific characteristics of the detector that may be used for quality control purposes, e.g. correlation of image artifacts with a detector defect map, analysis of noise performance, etc.

The Displayed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the Display Shutter Module (see section C.7.6.11). If this Module is not present or supported, then the Displayed Area is equal to the Field of View.
The Exposed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the X-Ray Collimator Module (see section C.8.7.3).
For the Digital X-Ray IODs, the Field of View is usually rectangular in shape and the same size as the stored Pixel Data (7FE0,0010). The shape and size of the Field of View and the spacing of the pixels are defined by the following Attributes:
- Field of View Shape (0018,1147),
- Field of View Dimensions (0018,1149),
- Imager Pixel Spacing (0018,1164),
- Rows (0028,0010),
- Columns (0028,0011)

The following Attributes define the relationship of the Field of View to the Physical Detector Area:
- Field of View Origin (0018,7030),
- Field of View Rotation (0018,7032),
- Field of View Horizontal Flip (0018,7034).

For the Digital X-Ray IODs, the Active Area, i.e. that part of the detector matrix that was activated for this exposure, is usually rectangular in shape. The shape and size of the Active Area and the size and spacing of the detectors are defined by the following Attributes:
- Detector Active Shape (0018,7024),
- Detector Active Dimensions (0018,7026),
- Detector Element Physical Size (0018,7020),
- Detector Element Spacing (0018,7022).

Notes:  1. The Detector Element Physical Size (0018,7020) and Detector Element Spacing (0018,7022) may be different if there are insensitive regions between each detector.
  2. This model of description is not able to accurately describe multiple matrices of detectors that are “tiled” to produce a single image.

The following optional Attribute defines the relationship of the Active Area to the Physical Detector Area:
- Detector Active Origin (0018,7028).

The relationship between detectors and stored image pixels is defined by Detector Binning (0018,701A) which specifies how many detectors, in each of the row and column directions, contribute to (are pooled or averaged to form) a single stored image pixel.
Note:  Detector Binning (0018,701A) may have values less than one if sub-sampling is used to derive an image with higher spatial resolution than the detector matrix.



Figure C.8-14
Explanation of DX Detector Attributes




Figure C.8-15
Explanation of DX Detector Attributes
</section>
    </entry>
  </macro>
  <module ref="C.8.11.5" table="C.8-72" name="DX Positioning Module Attributes">
    <entry group="0018" element="5104" name="Projection Eponymous Name Code Sequence" type="3">
      <description>A Sequence that describes the radiographic method of patient, tube and detector positioning to achieve a well described projection or view.
Only a single Item shall be permitted in this Sequence.
Shall be consistent with the other Attributes in this Module, if present, but may more specifically describe the image acquisition.
</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID 4012"/>
    <entry group="0018" element="5100" name="Patient Position" type="3">
      <description>Description of imaging subject's position relative to the equipment.
See C.7.3.1.1.2 for Defined Terms and further explanation.
If present, shall be consistent with Patient Gantry Relationship Code Sequence (0054,0414) and Patient Orientation Modifier Code Sequence (0054,0412).</description>
      <section ref="C.7.3.1.1.2" name="">Patient Position (0018,5100) specifies the position of the patient relative to the imaging equipment space. This attribute is intended for annotation purposes only. It does not provide an exact mathematical relationship of the patient to the imaging equipment.
When facing the front of the imaging equipment, Head First is defined as the patient’s head being positioned toward the front of the imaging equipment. Feet First is defined as the patient’s feet being positioned toward the front of the imaging equipment. Prone is defined as the patient’s face being positioned in a downward (gravity) direction. Supine is defined as the patient’s face being in an upward direction. Decubitus Right is defined as the patient’s right side being in a downward direction. Decubitus Left is defined as the patient’s left side being in a downward direction.
The Defined Terms are:
<defined-terms><term value="HFP&#9;= Head First-Prone"/><term value="HFS&#9;= Head First-Supine"/><term value="HFDR&#9;= Head First-Decubitus Right"/><term value="HFDL&#9;= Head First-Decubitus Left"/><term value="FFDR&#9;= Feet First-Decubitus Right"/><term value="FFDL&#9;= Feet First-Decubitus Left"/><term value="FFP&#9;= Feet First-Prone"/><term value="FFS&#9;= Feet First-Supine"/></defined-terms>
         </section>
    </entry>
    <entry group="0018" element="5101" name="View Position" type="3">
      <description>Radiographic view of the image relative to the imaging subject's orientation.
Shall be consistent with View Code Sequence (0054,0220). See C.8.11.5.1.1 for further explanation.</description>
      <section ref="C.8.11.5.1.1" name="">View Code Sequence (0054,0220) replaces the function of View Position (0018,5101), and describes the radiographic view of the image relative to the real-world patient orientation as described in PS 3.17 annex on Explanation of Patient Orientation.

</section>
    </entry>
    <entry group="0054" element="0220" name="View Code Sequence" type="3">
      <description>Sequence that describes the projection of the anatomic region of interest on the image receptor.
Note: It is strongly recommended that this Attribute be present, in order to ensure that images may be positioned correctly relative to one another for display.
Shall be consistent with View Position (0018,5101). See C.8.11.5.1.1 for further explanation.
Only a single Item shall be permitted in this Sequence.</description>
      <section ref="C.8.11.5.1.1" name="">View Code Sequence (0054,0220) replaces the function of View Position (0018,5101), and describes the radiographic view of the image relative to the real-world patient orientation as described in PS 3.17 annex on Explanation of Patient Orientation.

</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID 4010"/>
    <entry group="0054" element="0222" name="&gt;View Modifier Code Sequence" type="3">
      <description>View modifier.

Zero or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID 4011"/>
    <entry group="0054" element="0410" name="Patient Orientation Code Sequence" type="3">
      <description>Sequence that describes the orientation of the patient with respect to gravity.
See C.8.11.5.1.2 for further explanation.
Only a single Item shall be permitted in this Sequence.</description>
      <section ref="C.8.11.5.1.2" name="">This Attribute is not related to Patient Orientation (0020,0020) and conveys a different concept entirely.
</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID 19"/>
    <entry group="0054" element="0412" name="&gt; Patient Orientation Modifier Code Sequence" type="3">
      <description>Patient Orientation Modifier.
Required if needed to fully specify the orientation of the patient with respect to gravity.
Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID 20"/>
    <entry group="0054" element="0414" name="Patient Gantry Relationship Code Sequence" type="3">
      <description>Sequence which describes the orientation of the patient with respect to the gantry.

Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID 21"/>
    <entry group="0018" element="1111" name="Distance Source to Patient" type="3">
      <description>Distance in mm from source to the table, support or bucky side that is closest to the Imaging Subject, as measured along the central ray of the X-Ray beam.
Note: 1. This definition is less useful in terms of estimating geometric magnification than a measurement to a defined point within the Imaging Subject, but accounts for what is realistically measurable in an automated fashion in a clinical setting.
2. This measurement does not take into account any air gap between the Imaging Subject and the "front" of the table or bucky.
3. If the detector is not mounted in a table or bucky, then the actual position relative to the patient is implementation or operator defined.
4. This value is traditionally referred to as Source Object Distance (SOD).
See C.8.11.7 Mammography Image Module for explanation if Positioner Type (0018,1508) is MAMMOGRAPHIC.</description>
      <section ref="C.8.11.7" name="">Table C.8-74 contains IOD Attributes that describe a Digital Mammography X-Ray Image including its acquisition and positioning.
Table C.8-74
MAMMOGRAPHY IMAGE MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Positioner Type" meaning="(0018,1508)"/><term value="Distance Source to Detector" meaning="(0018,1110)"/><term value="Distance Source to Patient" meaning="(0018,1111)"/><term value="Positioner Primary Angle" meaning="(0018,1510)"/><term value="Positioner Secondary Angle" meaning="(0018,1511)"/><term value="Image Laterality" meaning="(0020,0062)"/><term value="Organ Exposed" meaning="(0040,0318)"/><term value="Implant Present" meaning="(0028,1300)"/><term value="Partial View" meaning="(0028,1350)"/><term value="Partial View Description" meaning="(0028,1351)"/><term value="Partial View Code Sequence" meaning="(0028,1352)"/><term value="&gt;Include ‘Code Sequence Macro’ (Table 8.8-1)." meaning="Defined Context ID is 4005."/><term value="Include 'General Anatomy Mandatory Macro' Table 10-5" meaning="Defined Context ID for the Anatomic Region Sequence is 4013."/><term value="View Code Sequence" meaning="(0054,0220)"/><term value="&gt;Include ‘Code Sequence Macro’ Table 8.8-1." meaning="Enumerated Value for Context ID is 4014."/><term value="&gt;View Modifier Code Sequence" meaning="(0054,0222)"/><term value="&gt;&gt;Include ‘Code Sequence Macro’ Table 8.8-1." meaning="Enumerated Value for Context ID is 4015."/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0018" element="1110" name="Distance Source to Detector" type="3">
      <description>Distance in mm from source to detector center.
Note: This value is traditionally referred to as Source Image Receptor Distance (SID).
See C.8.11.7 Mammography Image Module for explanation if Positioner Type (0018,1508) is MAMMOGRAPHIC.</description>
      <section ref="C.8.11.7" name="">Table C.8-74 contains IOD Attributes that describe a Digital Mammography X-Ray Image including its acquisition and positioning.
Table C.8-74
MAMMOGRAPHY IMAGE MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Positioner Type" meaning="(0018,1508)"/><term value="Distance Source to Detector" meaning="(0018,1110)"/><term value="Distance Source to Patient" meaning="(0018,1111)"/><term value="Positioner Primary Angle" meaning="(0018,1510)"/><term value="Positioner Secondary Angle" meaning="(0018,1511)"/><term value="Image Laterality" meaning="(0020,0062)"/><term value="Organ Exposed" meaning="(0040,0318)"/><term value="Implant Present" meaning="(0028,1300)"/><term value="Partial View" meaning="(0028,1350)"/><term value="Partial View Description" meaning="(0028,1351)"/><term value="Partial View Code Sequence" meaning="(0028,1352)"/><term value="&gt;Include ‘Code Sequence Macro’ (Table 8.8-1)." meaning="Defined Context ID is 4005."/><term value="Include 'General Anatomy Mandatory Macro' Table 10-5" meaning="Defined Context ID for the Anatomic Region Sequence is 4013."/><term value="View Code Sequence" meaning="(0054,0220)"/><term value="&gt;Include ‘Code Sequence Macro’ Table 8.8-1." meaning="Enumerated Value for Context ID is 4014."/><term value="&gt;View Modifier Code Sequence" meaning="(0054,0222)"/><term value="&gt;&gt;Include ‘Code Sequence Macro’ Table 8.8-1." meaning="Enumerated Value for Context ID is 4015."/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0018" element="1114" name="Estimated Radiographic Magnification Factor" type="3">
      <description>Ratio of Source Image Receptor Distance (SID) over Source Object Distance (SOD).</description>
    </entry>
    <entry group="0018" element="1508" name="Positioner Type" type="2">
      <description>Defined Terms:
CARM
COLUMN
MAMMOGRAPHIC
PANORAMIC
CEPHALOSTAT
RIGID
NONE
Notes: 1. The term CARM can apply to any positioner with 2 degrees of freedom of rotation of the X-Ray beam about the Imaging Subject.
2. The term COLUMN can apply to any positioner with 1 degree of freedom of rotation of the X-Ray beam about the Imaging Subject.</description>
    </entry>
    <entry group="0018" element="1510" name="Positioner Primary Angle" type="3">
      <description>Position of the X-Ray beam about the patient from the RAO to LAO direction where movement from RAO to vertical is positive, if Positioner Type (0018,1508) is CARM.
See C.8.7.5 XA Positioner Module for further explanation if Positioner Type (0018,1508) is CARM.
See C.8.11.7 Mammography Image Module for explanation if Positioner Type (0018,1508) is MAMMOGRAPHIC.</description>
    </entry>
    <entry group="0018" element="1511" name="Positioner Secondary Angle" type="3">
      <description>Position of the X-Ray beam about the patient from the CAU to CRA direction where movement from CAU to vertical is positive, if Positioner Type (0018,1508) is CARM.
See C.8.7.5 XA Positioner Module for further explanation if Positioner Type (0018,1508) is CARM.
See C.8.11.7 Mammography Image Module for explanation if Positioner Type (0018,1508) is MAMMOGRAPHIC.</description>
    </entry>
    <entry group="0018" element="1530" name="Detector Primary Angle" type="3">
      <description>Angle of the X-Ray beam in the row direction in degrees relative to the normal to the detector plane. Positive values indicate that the X-Ray beam is tilted toward higher numbered columns. Negative values indicate that the X-Ray beam is tilted toward lower numbered columns.
See C.8.7.5 XA Positioner Module for further explanation.
See C.8.11.7 Mammography Image Module for explanation if Positioner Type (0018,1508) is MAMMOGRAPHIC.</description>
    </entry>
    <entry group="0018" element="1531" name="Detector Secondary Angle" type="3">
      <description>Angle of the X-Ray beam in the column direction in degrees relative to the normal to the detector plane. Positive values indicate that the X-Ray beam is tilted toward lower numbered rows. Negative values indicate that the X-Ray beam is tilted toward higher numbered rows.
See C.8.7.5 XA Positioner Module for further explanation.
See C.8.11.7 Mammography Image Module for explanation if Positioner Type (0018,1508) is MAMMOGRAPHIC.</description>
    </entry>
    <entry group="0018" element="1450" name="Column Angulation" type="3">
      <description>Angle of the X-Ray beam in degree relative to an orthogonal axis to the detector plane. Positive values indicate that the tilt is toward the head of the table.
Note: The detector plane is assumed to be parallel to the table plane.
Only meaningful if Positioner Type (0018,1508) is COLUMN.</description>
    </entry>
    <entry group="0018" element="113A" name="Table Type" type="3">
      <description>Defined Terms:
FIXED
TILTING
NONE</description>
    </entry>
    <entry group="0018" element="1138" name="Table Angle" type="3">
      <description>Angle of table plane in degrees relative to horizontal plane [Gravity plane]. Positive values indicate that the head of the table is upward.
Only meaningful if Table Type (0018,113A) is TILTING.</description>
    </entry>
    <entry group="0018" element="11A0" name="Body Part Thickness" type="3">
      <description>The average thickness in mm of the body part examined when compressed, if compression has been applied during exposure.</description>
    </entry>
    <entry group="0018" element="11A2" name="Compression Force" type="3">
      <description>The compression force applied to the body part during exposure, measured in Newtons.</description>
    </entry>
  </module>
  <module ref="C.8.11.6" table="C.8-73" name="Mammography Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Type of equipment that originally acquired the data used to create the images in this Series.
Enumerated Value:
MG
See section C.7.3.1.1.1 for further explanation.</description>
    </entry>
    <entry group="0040" element="0275" name="Request Attributes Sequence" type="3">
      <description>Sequence that contains attributes from the Imaging Service Request.
The sequence may have one or more Items.</description>
    </entry>
    <include ref="&gt;Include Request Attributes Macro Table 10-9" description="For Reason for Requested Procedure Code Sequence (0040,100A) the Baseline Context IDs are 6051 and 6055. No Baseline Context IDs are defined for other Attributes.Note: For example, Requested Procedure Code Sequence (0040,100A) may be used to convey whether the images in the Series were taken for screening or diagnostic purposes."/>
  </module>
  <module ref="C.8.11.7" table="C.8-74" name="Mammography Image Module Attributes">
    <entry group="0018" element="1508" name="Positioner Type" type="1">
      <description>Enumerated Values:
MAMMOGRAPHIC
NONE</description>
    </entry>
    <entry group="0018" element="1110" name="Distance Source to Detector" type="3">
      <description>Distance in mm from source to detector center on the chest wall line
Notes: 1. This value is traditionally referred to as Source Image Distance (SID).
2. See C.8.11.7.1.1.</description>
      <section ref="C.8.11.7.1.1" name="">Figure C.8-8 shows the X-Ray beam for a digital mammography system. The X-Ray beam vector is defined from the Focal Spot to the center of the chest wall line of the Image Detection device.

Figure C.8-8
</section>
    </entry>
    <entry group="0018" element="1111" name="Distance Source to Patient" type="3">
      <description>Distance in mm from source to the bucky side that is closest to the Imaging Subject, as measured along the X-Ray beam vector.
Notes: 1. This value is traditionally referred to as Source Object Distance (SOD).
2. See notes for this attribute in C.8.11.5 DX Positioning Module.
3. See C.8.11.7.1.1 for description of X-Ray beam vector.</description>
      <section ref="C.8.11.7.1.1" name="">Figure C.8-8 shows the X-Ray beam for a digital mammography system. The X-Ray beam vector is defined from the Focal Spot to the center of the chest wall line of the Image Detection device.

Figure C.8-8
</section>
    </entry>
    <entry group="0018" element="1510" name="Positioner Primary Angle" type="3">
      <description>Position in degrees of the X-Ray beam vector in the coronal anatomical plane as if the patient were standing where movement of the X-Ray source from right to vertical is positive, and vertical is zero.</description>
    </entry>
    <entry group="0018" element="1511" name="Positioner Secondary Angle" type="3">
      <description>Position in degrees of the X-Ray beam vector in the sagittal anatomical plane as if the patient were standing where movement of the X-Ray source from anterior to posterior is positive, and vertical is zero.</description>
    </entry>
    <entry group="0020" element="0062" name="Image Laterality" type="1">
      <description>Laterality of the region examined.
Enumerated Values:
R = right
L = left
B = both (e.g. cleavage)</description>
    </entry>
    <entry group="0040" element="0318" name="Organ Exposed" type="1">
      <description>Organ to which Organ Dose (0040,0316) applies.
Enumerated Value:
BREAST
Note: In the Mammography IOD, Organ Dose (0040,0316) refers to the mean glandular dose.</description>
    </entry>
    <entry group="0028" element="1300" name="Implant Present" type="3">
      <description>Whether or not an implant is present. Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="0028" element="1350" name="Partial View" type="3">
      <description>Indicates whether this image is a partial view, that is a subset of a single view of the breast.
Enumerated Values: YES, NO
If this Attribute is absent, then the image may or may not be a partial view.
Note: This may occur when a breast is larger than the active area of the detector.
If this Attribute is present, its value shall be NO if there is a View Modifier Code Sequence (0054,0222) Item of value (R-102D6, SNM3, "Magnification") or (R-102D7, SNM3, "Spot Compression").</description>
    </entry>
    <entry group="0028" element="1351" name="Partial View Description" type="3">
      <description>Free text description of the portion of the breast captured in a partial view image.
This Attribute shall not be present if there is a View Modifier Code Sequence (0054,0222) Item of value (R-102D6, SNM3, "Magnification") or (R-102D7, SNM3, "Spot Compression").</description>
    </entry>
    <entry group="0028" element="1352" name="Partial View Code Sequence" type="3">
      <description>Sequence that describes the portion or section of the breast captured in a partial view image. One or two Items may be present. See C.8.11.7.1.3.
If this Attribute is absent, then the image may or may not be a partial view.
This Attribute shall not be present if there is a View Modifier Code Sequence (0054,0222) Item of value (R-102D6, SNM3, "Magnification") or (R-102D7, SNM3, "Spot Compression").</description>
      <section ref="C.8.11.7.1.3" name="">The following combinations of coded terms may be used to express the breast sections, for example, for the left cranio-caudal (L CC) view. These terms would also apply to the R CC, and the right and left FB, XCC, XCCL and XCCM views:
<unrecognized-rows><term value="A) item 1 = Lateral"/><term value="A) item 1 = Posterior"/><term value="A) item 1 = Lateral, item 2 = Posterior"/><term value="A) item 1 = Lateral, item 2 = Posterior"/><term value="A) item 1 = Lateral, item 2 = Posterior"/></unrecognized-rows>
Note: If six images are required, then the “Central, Anterior” combination would be added.

The following combinations of coded terms may be used to express the breast sections, for example, for the left medio-lateral oblique (L MLO) view. These terms would also apply to the R MLO, and to the right and left LM, ML, LMO, and SIO views:
<unrecognized-rows><term value="A) item 1 = Superior"/><term value="A) item 1 = Posterior"/><term value="A) item 1 = Superior, item 2 = Posterior"/><term value="A) item 1 = Superior, item 2 = Posterior"/><term value="A) item 1 = Superior, item 2 = Posterior"/></unrecognized-rows>
Note: If six images are required, then the “Central, Anterior” combination would be added.

</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' (Table 8.8-1)." description="Defined Context ID is 4005."/>
    <include ref="Include 'General Anatomy Mandatory Macro' Table 10-5" description="Defined Context ID for the Anatomic Region Sequence is 4013."/>
    <entry group="0054" element="0220" name="View Code Sequence" type="1">
      <description>Sequence that describes the projection of the anatomic region of interest on the image receptor.
Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Enumerated Value for Context ID is 4014."/>
    <entry group="0054" element="0222" name="&gt;View Modifier Code Sequence" type="2">
      <description>View modifier.
Zero or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Enumerated Value for Context ID is 4015."/>
  </module>
  <module ref="C.8.11.8" table="C.8-75" name="Intra Oral Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Type of equipment that originally acquired the data used to create the images in this Series.
Enumerated Values:
IO
See section C.7.3.1.1.1 for further explanation.</description>
    </entry>
  </module>
  <module ref="C.8.11.9" table="C.8-76" name="Intra Oral Image Module Attributes">
    <entry group="0018" element="1508" name="Positioner Type" type="1">
      <description>Enumerated Values:
NONE
CEPHALOSTAT
RIGID</description>
    </entry>
    <entry group="0020" element="0062" name="Image Laterality" type="1">
      <description>Laterality of the region examined.
Enumerated Values:
R = right
L = left
B = both (i.e. midline)</description>
    </entry>
    <entry group="0008" element="2218" name="Anatomic Region Sequence" type="1">
      <description>Sequence that identifies the anatomic region of interest in this image.
Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1." description="DefinedContext ID 4016."/>
    <entry group="0008" element="2220" name="&gt;Anatomic Region Modifier Sequence" type="1C">
      <description>Sequence that refines the anatomic region of interest in this image.
Required if Primary Anatomic Structure Sequence (0008,2228) is not sent.
Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1." description="DefinedContext ID 4017."/>
    <entry group="0008" element="2228" name="Primary Anatomic Structure Sequence" type="1C">
      <description>Sequence that describes the primary anatomic structures of interest in this image.
See C.8.11.9.1.1 for further explanation.
Required if Anatomic Region Modifier Sequence (0008,2220) is not sent.
One or more Items may be included in this Sequence.</description>
      <section ref="C.8.11.9.1.1" name="">The Code Value (0008,0100) shall be drawn from the DICOM Content Mapping Resource, Context ID 4018, for permanent dentition, or Context ID 4019 for deciduous dentition.
These Context Groups correspond to ISO 3950-1984 that describes a designation of permanent and deciduous dentition using a two digit code, the first digit of which designates a quadrant, and the second digit a tooth.
The teeth imaged shall be listed as multiple Items in the Primary Anatomic Structure Sequence (0008,2228).
</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1." description="DefinedContext ID 4018 or 4019. See C.8.11.9.1.1 for further explanation."/>
  </module>
  <module ref="C.8.12.1" table="C.8-77" name="VL Image Module Attributes">
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image identification characteristics.
See C.8.12.1.1.6 for specialization.</description>
      <section ref="C.8.12.1.1.6" name="">The Image Type attribute identifies important image characteristics in a multiple valued data element. For Visible Light, Image Type is specialized as follows:
a.  Value 1 shall identify the Pixel Data Characteristics in accordance with Section C.7.6.1.1.2; Enumerated Values are: ORIGINAL and DERIVED;
b.  Value 2 shall identify the Patient Examination Characteristics in accordance with Section C.7.6.1.1.2; Enumerated Values are: PRIMARY and SECONDARY.
c.  Value 3 may be absent, but if present shall identify the members of a stereo pair, in which case Referenced Image Sequence (0008,1140) is used to identify the other member of the pair. If present, the Enumerated Values are:

<enumerated-values><term value="STEREO L" meaning="Image is the left image (relative to the observer's left) of a stereo pair acquisition;"/><term value="STEREO R" meaning="Image is the right image (relative to the observer's right) of a stereo pair acquisition."/></enumerated-values>
d.  Other Values are implementation specific (optional).

</section>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data.
See C.8.12.1.1.1 for specialization of this Attribute.</description>
      <section ref="C.8.12.1.1.1" name="">The Enumerated Values of Photometric Interpretation (0028,0004) shall be:
MONOCHROME2
RGB
YBR_FULL_422
YBR_PARTIAL_420
YBR_RCT
YBR_ICT
Note:  There is no formal color space defined, hence “false” color applications that encode near-visible light images may be encoded, for example, as RGB.

</section>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated.
See C.8.12.1.1.2 for specialization of this Attribute. See PS 3.5 for further explanation.</description>
      <section ref="C.8.12.1.1.2" name="">The Enumerated Value of Bits Allocated (0028,0100) shall be 8; the Enumerated Value of Bits Stored (0028,0101) shall be 8; and the Enumerated Value of High Bit (0028,0102) shall be 7.
</section>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored.
See C.8.12.1.1.2 for specialization of this Attribute. See PS 3.5 for further explanation.</description>
      <section ref="C.8.12.1.1.2" name="">The Enumerated Value of Bits Allocated (0028,0100) shall be 8; the Enumerated Value of Bits Stored (0028,0101) shall be 8; and the Enumerated Value of High Bit (0028,0102) shall be 7.
</section>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data. Each sample shall have the same high bit.
See C.8.12.1.1.2 for specialization of this Attribute. See PS 3.5 for further explanation.</description>
      <section ref="C.8.12.1.1.2" name="">The Enumerated Value of Bits Allocated (0028,0100) shall be 8; the Enumerated Value of Bits Stored (0028,0101) shall be 8; and the Enumerated Value of High Bit (0028,0102) shall be 7.
</section>
    </entry>
    <entry group="0028" element="0103" name="Pixel Representation" type="1">
      <description>Data representation of the pixel samples. Each sample shall have the same pixel representation.
See Section C.8.12.1.1.3 for specialization of this Attribute.</description>
      <section ref="C.8.12.1.1.3" name="">The Enumerated Value of Pixel Representation (0028,0103) shall be 0.
</section>
    </entry>
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (planes) per image.
See C.8.12.1.1.4 for specialization of this Attribute.</description>
      <section ref="C.8.12.1.1.4" name="">The Enumerated Values of Samples per Pixel (0028,0002) shall be as follows: If the value of Photometric Interpretation (0028,0004) is MONOCHROME2, then the Enumerated Value of Samples per Pixel (0028,0002) shall be one (1). If the value of Photometric Interpretation (0028,0004) is RGB or YBR_FULL_422 or YBR_PARTIAL_420 or YBR_RCT or YBR_ICT, then the Enumerated Value of Samples per Pixel (0028,0002) shall be three (3).
</section>
    </entry>
    <entry group="0028" element="0006" name="Planar Configuration" type="1C">
      <description>Indicates whether the pixel data are sent color-by-plane or color-by-pixel. Required if Samples per Pixel (0028,0002) has a value greater than 1.
See C.8.12.1.1.5 for specialization of this Attribute.</description>
      <section ref="C.8.12.1.1.5" name="">If present, the Enumerated Value of Planar Configuration (0028,0006) shall be 0. This value shall be present if Samples per Pixel (0028,0002) has a value greater than 1.
</section>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1C">
      <description>The time the image pixel data creation started. Required if the Image is part of a series in which the images are temporally related.
Note: This Attribute was formerly known as Image Time.</description>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="2">
      <description>Specifies whether an Image has undergone lossy compression. Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0008" element="1140" name="Referenced Image Sequence" type="1C">
      <description>A Sequence that references other images significantly related to this image. One or more items may be included in this sequence.
Required if Image Type (0008,0008) Value 3 is present and has a value of "STEREO L" or "STEREO R". May also be present otherwise. See Section C.8.12.1.1.7.</description>
      <section ref="C.8.12.1.1.7" name="">When Image Type (0008,0008) Value 3 is STEREO L or STEREO R, Referenced Image Sequence (0008,1140) shall be used to identify the corresponding SOP Instance of the Stereoscopic acquisition. In this case, either:
</section>
    </entry>
    <include ref="&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="2">
      <description>Describes the purpose for which the reference is made. Zero or one item shall be present in the sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="Defined Context ID 7201"/>
    <entry group="0028" element="1050" name="Window Center" type="3">
      <description>Window Center for display. See C.11.2.1.2 for further explanation.
Meaningful only if Photometric Interpretation (0028,0004) is MONOCHROME2.</description>
      <section ref="C.11.2.1.2" name="">Window Center (0028,1050) and Window Width (0028,1051) specify a linear conversion from stored pixel values (after any Modality LUT or Rescale Slope and Intercept specified in the IOD have been applied) to values to be displayed. Window Center contains the input value that is the center of the window. Window Width contains the width of the window.
Note:  The terms “window center” and “window width” are not consistently used in practice, nor were they defined in previous versions of the standard. The definitions here are presented for the purpose of defining consistent meanings for identity and threshold transformations while preserving the common practice of using integral values for center and width.

Window Width (0028,1051) shall always be greater than or equal to 1.
When Window Width (0028,1051) is greater than 1, these Attributes select the range of input values that are to be mapped to the full range of the displayed output.
When Window Width (0028,1051) is equal to 1, they specify a threshold below which input values will be displayed as the minimum output value.
Note:  Whether the minimum output value is rendered as black or white may depend on the value of Photometric Interpretation (0028,0004) or the presence of a Presentation LUT Module.

These Attributes are applied according to the following pseudo-code, where x is the input value, y is an output value with a range from ymin to ymax, c is Window Center (0028,1050) and w is Window Width (0028,1051):
    if  (x &lt;= c - 0.5 - (w-1)/2), then y = ymin
    else if  (x &gt; c - 0.5 + (w-1)/2), then y = ymax,
    else  y = ((x - (c - 0.5)) / (w-1) + 0.5) * (ymax - ymin)+ ymin

Notes:  1. For the purpose of this definition, a floating point calculation without integer truncation is assumed, though the manner of implementation may vary as long as the result is the same.
  2. The pseudo-code function computes a continuous value over the output range without any discontinuity at the boundaries. The value of 0 for w is expressly forbidden, and the value of 1 for w does not cause division by zero, since the continuous segment of the function will never be reached for that case.
  3. For example, for an output range 0 to 255:
    c=2048, w=4096 becomes:
      if (x &lt;= 0) then y = 0
      else if (x &gt; 4095) then y = 255
      else y = ((x - 2047.5) / 4095 + 0.5) * (255-0) + 0
    c=2048, w=1 becomes:
      if (x &lt;= 2047.5) then y = 0
      else if (x &gt; 2047.5) then y = 255
      else /* not reached */

    c=0, w=100 becomes:
      if (x &lt;= -50) then y = 0
      else if (x &gt; 49) then y = 255
      else y = ((x + 0.5) / 99 + 0.5) * (255-0) + 0
    c=0, w=1 becomes:
      if (x &lt;= -0.5) then y = 0
      else if (x &gt; -0.5) then y = 255
      else /* not reached */

  4. A Window Center of 2n-1 and a Window Width of 2n selects the range of input values from 0 to 2n-1. This represents an identity VOI LUT transformation in the case where no Modality LUT is specified and the stored pixel data are n bit unsigned integers.
  5. A Window Width of 1 is typically used to represent a "threshold" operation in which those integer input values less than the Window Center are represented as the minimum displayed value and those greater than or equal to the Window Center are represented as the maximum displayed value. A Window Width of 2 will have the same result for integral input values.
  6. The application of Window Center (0028,1050) and Window Width (0028,1051) may select a signed input range. There is no implication that this signed input range is clipped to zero.
  7. The selected input range may exceed the actual range of the input values, thus effectively “compressing” the contrast range of the displayed data into a narrower band of the available contrast range, and “flattening” the appearance. There are no limits to the maximum value of the window width, or to the minimum or maximum value of window level, both of which may exceed the actual or possible range of input values.
  8. Input values "below" the window are displayed as the minimum output value and input values "above" the window are displayed as the maximum output value. This is the common usage of the window operation in medical imaging. There is no provision for an alternative approach in which all values "outside" the window are displayed as the minimum output value.
  9. The output of the Window Center/Width or VOI LUT transformation is either implicitly scaled to the full range of the display device if there is no succeeding transformation defined, or implicitly scaled to the full input range of the succeeding transformation step (such as the Presentation LUT), if present. See C.11.6.1.
  10. Fractional values of Window Center and Window Width are permitted (since the VR of these Attributes is Decimal String), and though they are not often encountered, applications should be prepared to accept them.

These Attributes shall be used only for Images with Photometric Interpretation (0028,0004) values of MONOCHROME1 and MONOCHROME2. They have no meaning for other Images.
If multiple values are present, both Attributes shall have the same number of values and shall be considered as pairs. Multiple values indicate that multiple alternative views may be presented.
If any VOI LUT Table is included by an Image, a Window Width and Window Center or the VOI LUT Table, but not both, may be applied to the Image for display. Inclusion of both indicates that multiple alternative views may be presented.
If multiple items are present in VOI LUT Sequence (0028,3010), only one may be applied to the Image for display. Multiple items indicate that multiple alternative views may be presented.
If the VOI LUT Module is defined in an IOD and if neither a VOI LUT Sequence nor a Window Width and Window Center are present, then the VOI LUT stage of the grayscale pipeline is defined to be an identity transformation.
Notes:  1. This requirement is specified so that IODs that define a particular output space for the grayscale pipeline, such as P-Values, are not in an undefined state when no VOI LUT Sequence or Window Width and Window Center are present.
  2. Despite the Type 3 requirement for VOI LUT Sequence and Window Center, implementations that render images are expected to implement and apply these transformations when they are present in the image, unless overridden by the user, a presentation state, or a hanging protocol, and to allow the user to select which transformation to apply when multiple transformations are present.

</section>
    </entry>
    <entry group="0028" element="1051" name="Window Width" type="1C">
      <description>Window Width for display. See C.11.2.1.2 for further explanation.
Required if Window Center (0028,1050) is present.</description>
      <section ref="C.11.2.1.2" name="">Window Center (0028,1050) and Window Width (0028,1051) specify a linear conversion from stored pixel values (after any Modality LUT or Rescale Slope and Intercept specified in the IOD have been applied) to values to be displayed. Window Center contains the input value that is the center of the window. Window Width contains the width of the window.
Note:  The terms “window center” and “window width” are not consistently used in practice, nor were they defined in previous versions of the standard. The definitions here are presented for the purpose of defining consistent meanings for identity and threshold transformations while preserving the common practice of using integral values for center and width.

Window Width (0028,1051) shall always be greater than or equal to 1.
When Window Width (0028,1051) is greater than 1, these Attributes select the range of input values that are to be mapped to the full range of the displayed output.
When Window Width (0028,1051) is equal to 1, they specify a threshold below which input values will be displayed as the minimum output value.
Note:  Whether the minimum output value is rendered as black or white may depend on the value of Photometric Interpretation (0028,0004) or the presence of a Presentation LUT Module.

These Attributes are applied according to the following pseudo-code, where x is the input value, y is an output value with a range from ymin to ymax, c is Window Center (0028,1050) and w is Window Width (0028,1051):
    if  (x &lt;= c - 0.5 - (w-1)/2), then y = ymin
    else if  (x &gt; c - 0.5 + (w-1)/2), then y = ymax,
    else  y = ((x - (c - 0.5)) / (w-1) + 0.5) * (ymax - ymin)+ ymin

Notes:  1. For the purpose of this definition, a floating point calculation without integer truncation is assumed, though the manner of implementation may vary as long as the result is the same.
  2. The pseudo-code function computes a continuous value over the output range without any discontinuity at the boundaries. The value of 0 for w is expressly forbidden, and the value of 1 for w does not cause division by zero, since the continuous segment of the function will never be reached for that case.
  3. For example, for an output range 0 to 255:
    c=2048, w=4096 becomes:
      if (x &lt;= 0) then y = 0
      else if (x &gt; 4095) then y = 255
      else y = ((x - 2047.5) / 4095 + 0.5) * (255-0) + 0
    c=2048, w=1 becomes:
      if (x &lt;= 2047.5) then y = 0
      else if (x &gt; 2047.5) then y = 255
      else /* not reached */

    c=0, w=100 becomes:
      if (x &lt;= -50) then y = 0
      else if (x &gt; 49) then y = 255
      else y = ((x + 0.5) / 99 + 0.5) * (255-0) + 0
    c=0, w=1 becomes:
      if (x &lt;= -0.5) then y = 0
      else if (x &gt; -0.5) then y = 255
      else /* not reached */

  4. A Window Center of 2n-1 and a Window Width of 2n selects the range of input values from 0 to 2n-1. This represents an identity VOI LUT transformation in the case where no Modality LUT is specified and the stored pixel data are n bit unsigned integers.
  5. A Window Width of 1 is typically used to represent a "threshold" operation in which those integer input values less than the Window Center are represented as the minimum displayed value and those greater than or equal to the Window Center are represented as the maximum displayed value. A Window Width of 2 will have the same result for integral input values.
  6. The application of Window Center (0028,1050) and Window Width (0028,1051) may select a signed input range. There is no implication that this signed input range is clipped to zero.
  7. The selected input range may exceed the actual range of the input values, thus effectively “compressing” the contrast range of the displayed data into a narrower band of the available contrast range, and “flattening” the appearance. There are no limits to the maximum value of the window width, or to the minimum or maximum value of window level, both of which may exceed the actual or possible range of input values.
  8. Input values "below" the window are displayed as the minimum output value and input values "above" the window are displayed as the maximum output value. This is the common usage of the window operation in medical imaging. There is no provision for an alternative approach in which all values "outside" the window are displayed as the minimum output value.
  9. The output of the Window Center/Width or VOI LUT transformation is either implicitly scaled to the full range of the display device if there is no succeeding transformation defined, or implicitly scaled to the full input range of the succeeding transformation step (such as the Presentation LUT), if present. See C.11.6.1.
  10. Fractional values of Window Center and Window Width are permitted (since the VR of these Attributes is Decimal String), and though they are not often encountered, applications should be prepared to accept them.

These Attributes shall be used only for Images with Photometric Interpretation (0028,0004) values of MONOCHROME1 and MONOCHROME2. They have no meaning for other Images.
If multiple values are present, both Attributes shall have the same number of values and shall be considered as pairs. Multiple values indicate that multiple alternative views may be presented.
If any VOI LUT Table is included by an Image, a Window Width and Window Center or the VOI LUT Table, but not both, may be applied to the Image for display. Inclusion of both indicates that multiple alternative views may be presented.
If multiple items are present in VOI LUT Sequence (0028,3010), only one may be applied to the Image for display. Multiple items indicate that multiple alternative views may be presented.
If the VOI LUT Module is defined in an IOD and if neither a VOI LUT Sequence nor a Window Width and Window Center are present, then the VOI LUT stage of the grayscale pipeline is defined to be an identity transformation.
Notes:  1. This requirement is specified so that IODs that define a particular output space for the grayscale pipeline, such as P-Values, are not in an undefined state when no VOI LUT Sequence or Window Width and Window Center are present.
  2. Despite the Type 3 requirement for VOI LUT Sequence and Window Center, implementations that render images are expected to implement and apply these transformations when they are present in the image, unless overridden by the user, a presentation state, or a hanging protocol, and to allow the user to select which transformation to apply when multiple transformations are present.

</section>
    </entry>
    <entry group="0008" element="2218" name="Anatomic Region Sequence" type="1C">
      <description>Sequence that identifies the anatomic region of interest in this image (i.e. external anatomy, surface anatomy, or general region of the body).
Only a single Item shall be permitted in this sequence.
Required if Number of Frames (0028,0008) is present and Specimen Accession Number (0040,050A) is absent. May be present otherwise.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="DCID 4040 is defined for the Video Endoscopic IOD.For other IODs, no Context ID is defined."/>
    <entry group="0008" element="2220" name="&gt;Anatomic Region Modifier Sequence" type="3">
      <description>Sequence of Items that modifies the anatomic region of interest of this image
One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 2."/>
    <include ref="Include 'Primary Anatomic Structure Macro' Table 10.x-4" description="No Context ID is defined."/>
    <entry group="0022" element="001A" name="Channel Description Code Sequence" type="3">
      <description>Describes the light color used for each channel to generate the image.
If Photometric Interpretation (0028,0004) has one of the YBR values, the meaning is for pixel data in an equivalent RGB encoding.
Note: Interpretation and representation of RGB images rely on the assumption that the red channel really contains the red wavelength range of illumination light, the blue channel the blue wavelength range, etc. Some modalities use the RGB Photometric Interpretation as a container representing 3 channels of any illumination wavelength.
Shall have the same number of items as the value of Samples per Pixel (0028,0002). The channels shall be described in the order in which the channels are encoded.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 4206."/>
  </module>
  <module ref="C.8.12.2" table="C.8-78" name="Slide Coordinates Module Attributes">
    <entry group="0040" element="071A" name="Image Center Point Coordinates Sequence" type="2">
      <description>The coordinates of the center point of the Image in the Slide Coordinate System Frame of Reference. Zero or one item shall be present in the sequence. See Section C.8.12.2.1.1 for further explanation.</description>
      <section ref="C.8.12.2.1.1" name="">This Section defines the Slide Coordinate System and specifies the Attributes that shall be used to describe the location of the center point of the Image pixel plane (as captured through a microscope) in the Slide Coordinate System Frame of Reference.
Note:  In Slide Microscopy (SM), the Microscope is equipped with a moveable Stage and position sensors that enable storage of the location of the center point of the displayed image with respect to the examined Specimen.

The Stage is the part of the Microscope to which the Slide is attached for viewing. The Objective Lens is the lens that is closest to the Specimen. The Top Surface of the Slide is the surface of the Slide on which the Specimen in Mounted. The Bottom Surface of the Slide is the opposite surface. This Specification presumes that: 1) the Slide is rectangular; 2) the Top Surface of the Slide is oriented toward the Objective Lens of the Microscope; and 3) the Bottom Surface of the Slide is in perfect contact with the Microscope Stage when the Slide is attached to the Stage for viewing.
Notes:  1. The Label of the Slide is presumed to be mounted-on or written-on the Top Surface of the Slide.
  2. Specification of the mechanical form, function, or tolerances of the Microscope are outside the scope of this Standard.

Figure C.8-16 depicts the Top Surface of the Slide on the Microscope Stage from the perspective of the Objective Lens. This is Reference Slide Orientation. The X, Y, and Z axes of the Slide Coordinate System in Reference Slide Orientation are defined as follows. The Y-axis is a line that includes the Left Edge of the Slide. The X-axis is a line that is orthogonal to the Y-axis and includes at least one point of the Specimen Edge of the Slide. The Z-axis is a line that passes through the intersection of the X-axis and Y-axis and is orthogonal to the Microscope Stage. The Origin (0,0,0) of the Slide Coordinate System is the point of intersection of the X, Y, and Z axes.

Figure C.8-16
REFERENCE SLIDE ORIENTATION

Notes:  1. An improperly-placed coverslip or Specimen that overlaps an Edge of a Slide is not considered part of the Edge a Slide for purposes of defining the Slide Coordinate System. However, such objects may cause inaccurate positioning of the Slide on the Stage.
  2. If the Left Edge and Specimen Edge of the Slide are not orthogonal (e.g. the Slide is damaged or defective or the Specimen Edge is curvilinear), then the lower left-hand corner of the Slide may not be located at the Origin.
  3. The definitions of X, Y, and Z axes are the same for inverted microscopes, with the Top Surface of the slide (i.e. Specimen side of the Slide) still being closest to the Objective Lens.

Figure C.8-17 depicts the Z-axis center point location. The X-axis value of Image Center Point Location (0040,073A) shall increase from the Origin toward the Right Edge in Reference Slide Orientation. The Y-axis value of Image Center Point Location (0040,073A) shall increase from the Origin toward the Label Edge in Reference Slide Orientation. The Z-axis value of Image Center Point Location (0040,073A) shall be referenced as zero at the image substrate reference plane (i.e. utilized surface of a glass slide) and shall increase in a positive fashion coincident with increased distance from the substrate surface.

Figure C.8-17
Z-AXIS CENTER POINT LOCATION, VIEW FROM RIGHT EDGE OF SLIDE
</section>
    </entry>
    <entry group="0040" element="072A" name="&gt;X Offset in Slide Coordinate System" type="1">
      <description>The X offset in millimeters from the Origin of the Slide Coordinate System. See Figure C.8-16.</description>
    </entry>
    <entry group="0040" element="073A" name="&gt;Y Offset in Slide Coordinate System" type="1">
      <description>The Y offset in millimeters from the Origin of the Slide Coordinate System. See Figure C.8-16.</description>
    </entry>
    <entry group="0040" element="074A" name="&gt;Z Offset in Slide Coordinate System" type="2">
      <description>The Z offset in microns from the image substrate reference plane (i.e. utilized surface of a glass slide).</description>
    </entry>
    <entry group="0040" element="08D8" name="Pixel Spacing Sequence" type="3">
      <description>Physical distance in the Imaging Subject, i.e. Patient or Specimen, between the center of each pixel along specified axes. One or more items may be present.</description>
    </entry>
    <entry group="0040" element="08DA" name="&gt;Coordinate System Axis Code Sequence" type="1">
      <description>Axis of a coordinate system. This sequence shall contain exactly one item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 95."/>
    <entry group="0040" element="A30A" name="&gt;Numeric Value" type="1">
      <description>The distance between the center-points of adjacent pixels along the axis specified by Coordinate System Axis Code Sequence (0040,08DA).</description>
    </entry>
    <entry group="0040" element="08EA" name="&gt;Measurement Units Code Sequence" type="1">
      <description>Units of the measurement. This sequence shall contain exactly one item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 82."/>
  </module>
  <module ref="C.8.13.1" table="C.8-79" name="Enhanced MR Image Module Attributes">
    <include ref="Include ' MR Image and Spectroscopy Instance Macro' Table C.8-81"/>
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image characteristics. See C.8.16.1 and C.8.13.3.1.1.</description>
      <section ref="C.8.16.1" name="">The Image Type (0008,0008) and associated Image Type related attributes provide a high level description of a multi-frame SOP Instance. These attributes describe properties that provide key summary information to users of the SOP Instance. Image Type (0008,0008) contains the highest level summary of what is in the SOP Instance.
The Frame Type (0008,9007) attribute mirrors the corresponding Image Type attribute and applies to the frame level rather than to the image level.
If more than one value is used by the set of frames for a given Frame Type (0008,9007) attribute value or associated attribute value then the corresponding value of the Image Type (0008,0008) or associated attribute shall contain a value of MIXED. This indicates that a mixed set of values exists within the multi-frame SOP Instance.
The value MIXED shall only be used in the Image Type (0008,0008) when the corresponding values for the individual frames are not equal. When a value of an attribute is equal for all frames, the same value shall be used for the corresponding value of the Image Type (0008,0008). Values 2 and 3 of Image Type (0008,0008) are an exception to the rule for MIXED: Values 2 and 3 may never have the value of MIXED as described in sections C.8.16.1.2 and C.8.16.1.3.
Image Type (0008,0008) and Frame Type (0008,9007) shall consist of four non-zero length values.
</section>
    </entry>
    <include ref="Include Common CT/MR Image Description Macro' Table C.8-131"/>
    <include ref="Include 'MR Image Description Macro' Table C.8.82"/>
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (planes) in this image. This value shall be 1.</description>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data. Enumerated Value: MONOCHROME2. See C.7.6.3.1.2 for definition of this term.</description>
      <section ref="C.7.6.3.1.2" name="">The value of Photometric Interpretation (0028,0004) specifies the intended interpretation of the image pixel data.
See PS 3.5 for restrictions imposed by compressed Transfer Syntaxes.
The following values are defined. Other values are permitted but the meaning is not defined by this Standard.
MONOCHROME1 = Pixel data represent a single monochrome image plane. The minimum sample value is intended to be displayed as white after any VOI gray scale transformations have been performed. See PS 3.4. This value may be used only when Samples per Pixel (0028,0002) has a value of 1.
MONOCHROME2 = Pixel data represent a single monochrome image plane. The minimum sample value is intended to be displayed as black after any VOI gray scale transformations have been performed. See PS 3.4. This value may be used only when Samples per Pixel (0028,0002) has a value of 1.
PALETTE COLOR = Pixel data describe a color image with a single sample per pixel (single image plane). The pixel value is used as an index into each of the Red, Blue, and Green Palette Color Lookup Tables (0028,1101-1103&amp;1201-1203). This value may be used only when Samples per Pixel (0028,0002) has a value of 1. When the Photometric Interpretation is Palette Color; Red, Blue, and Green Palette Color Lookup Tables shall be present.
RGB = Pixel data represent a color image described by red, green, and blue image planes. The minimum sample value for each color plane represents minimum intensity of the color. This value may be used only when Samples per Pixel (0028,0002) has a value of 3.
HSV = Retired.
ARGB = Retired.
CMYK = Retired.
YBR_FULL = Pixel data represent a color image described by one luminance (Y) and two chrominance planes (CB and CR). This photometric interpretation may be used only when Samples per Pixel (0028,0002) has a value of 3. Black is represented by Y equal to zero. The absence of color is represented by both CB and CR values equal to half full scale.
Note:  In the case where the Bits Allocated (0028,0100) has value of 8 half full scale is 128.

In the case where Bits Allocated (0028,0100) has a value of 8 then the following equations convert between RGB and YCBCR Photometric Interpretation.
Y =  +  .2990R  +  .5870G  +  .1140B
CB =  -  .1687R  -  .3313G  +  .5000B  +  128
CR =  +  .5000R  -  .4187G  -  .0813B  +  128
Note:  The above is based on CCIR Recommendation 601-2 dated 1990.

YBR_FULL_422 = The same as YBR_FULL except that the CB and CR values are sampled horizontally at half the Y rate and as a result there are half as many CB and CR values as Y values.
This Photometric Interpretation is only allowed with Planar Configuration (0028,0006) equal to 0. Two Y values shall be stored followed by one CB and one CR value. The CB and CR values shall be sampled at the location of the first of the two Y values. For each Row of Pixels, the first CB and CR samples shall be at the location of the first Y sample. The next CB and CR samples shall be at the location of the third Y sample etc.
Note:  This subsampling is often referred to as cosited sampling.

YBR_PARTIAL_422 = The same as YBR_FULL_422 except that:
1. black corresponds to Y = 16;
2. Y is restricted to 220 levels (i.e. the maximum value is 235);
3. CB and CR each has a minimum value of 16;
4. CB and CR are restricted to 225 levels (i.e. the maximum value is 240);
5. lack of color is represented by CB and CR equal to 128.
In the case where Bits Allocated (0028,0100) has value of 8 then the following equations convert between RGB and YBR_PARTIAL_422 Photometric Interpretation
Y =  +  .2568R  +  .5041G  +  .0979B  +  16
CB =  -  .1482R  -  .2910G  +  .4392B  +  128
CR =  +  .4392R  -  .3678G  -  .0714B  +  128
Note:  The above is based on CCIR Recommendation 601-2 dated 1990.

YBR_PARTIAL_420 = The same as YBR_PARTIAL_422 except that the CB and CR values are sampled horizontally and vertically at half the Y rate and as a result there are four times less CB and CR values than Y values, versus twice less for YBR_PARTIAL_422.
This Photometric Interpretation is only allowed with Planar Configuration (0028,0006) equal to 0. The CB and CR values shall be sampled at the location of the first of the two Y values. For the first Row of Pixels (etc.), the first CB and CR samples shall be at the location of the first Y sample. The next CB and CR samples shall be at the location of the third Y sample etc. The next Rows of Pixels containing CB and CR samples (at the same locations than for the first Row) will be the third etc.
YBR_ICT = Irreversible Color Transformation:
Pixel data represent a color image described by one luminance (Y) and two chrominance planes (CB and CR). This photometric interpretation may be used only when Samples per Pixel (0028,0002) has a value of 3. Black is represented by Y equal to zero. The absence of color is represented by both CB and CR values equal to zero.
Regardless of the value of Bits Allocated (0028,0100), the following equations convert between RGB and YCBCR Photometric Interpretation.
Y =  +  .29900R  +  .58700G  +  .11400B
CB =  -  .16875R  -  .33126G  +  .50000B
CR =  +  .50000R  -  .41869G  -  .08131B
Notes:  1. The above is based on ISO/IEC 15444-1 (JPEG 2000).
  2. In a JPEG 2000 bitstream, DC level shifting (used if the untransformed components are unsigned) is applied before forward color transformation, and the transformed components may be signed (unlike in JPEG ISO/IEC 10918-1).
  3. In JPEG 2000, spatial down-sampling of the chrominance components, if performed, is signaled in the JPEG 2000 bitstream.

YBR_RCT = Reversible Color Transformation:
Pixel data represent a color image described by one luminance (Y) and two chrominance planes (CB and CR). This photometric interpretation may be used only when Samples per Pixel (0028,0002) has a value of 3. Black is represented by Y equal to zero. The absence of color is represented by both CB and CR values equal to zero.
Regardless of the value of Bits Allocated (0028,0100), the following equations convert between RGB and YBR_RCT Photometric Interpretation.
Y = R + 2G +B) / 4        (Note:  mean floor)
CB = B - G
CR = R - G
The following equations convert between YBR_RCT and RGB Photometric Interpretation.
G = Y –  (CR + CB) / 4
R = CR + G
B = CB + G
Notes:  1. The above is based on ISO/IEC 15444-1 (JPEG 2000).
  2. In a JPEG 2000 bitstream, DC level shifting (used if the untransformed components are unsigned) is applied before forward color transformation, and the transformed components may be signed (unlike in JPEG ISO/IEC 10918-1).
  3. This photometric interpretation is a reversible approximation to the YUV transformation used in PAL and SECAM.

</section>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated. Enumerated Values: 8 and 16.</description>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored. Enumerated Values: 8, 12 and 16. See C.8.13.1.1.1 for specialization.</description>
      <section ref="C.8.13.1.1.1" name="">Table C.8-80 specifies the allowed combinations of Bits Allocated (0028,0100) and Bits Stored (0028,0101).
Table C.8-80
ALLOWED COMBINATIONS OF ATTRIBUTE VALUES
 FOR BITS ALLOCATED AND BITS STORED
<unrecognized-rows><term value="Bits Allocated" meaning="Bits Stored"/><term value="8" meaning="8"/><term value="16" meaning="12, 16"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data. Each sample shall have the same high bit. Shall be one less than the value in Bits Stored (0028,0101).</description>
    </entry>
    <entry group="0018" element="0088" name="Spacing between Slices" type="3">
      <description>Value of the prescribed spacing to be applied between the slices in a volume that is to be acquired. The spacing in mm is defined as the center-to-center distance of adjacent slices.</description>
    </entry>
    <entry group="0028" element="0301" name="Burned In Annotation" type="1">
      <description>Indicates whether or not the image contains sufficient burned in annotation to identify the patient and date the image was acquired.
Enumerated Values:
NO
This means that images that contain this Module shall not contain such burned in annotations.</description>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1">
      <description>Specifies whether an Image has undergone lossy compression.
Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5 for further explanation.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2112" name="Lossy Image Compression Ratio" type="1C">
      <description>Describes the approximate lossy compression ratio(s) that have been applied to this image.
See C.7.6.1.1.5 for further explanation.
May be multivalued if successive lossy compression steps have been applied.
Note: For example, a compression ratio of 30:1 would be described in this Attribute with a single value of 30.
Required if Lossy Images Compression (0028,2110) is "01".</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2114" name="Lossy Image Compression Method" type="1C">
      <description>A label for the lossy compression method(s) that have been applied to this image.
See C.7.6.1.1.5 for further explanation.
May be multivalued if successive lossy compression steps have been applied; the value order shall correspond to the values of Lossy Image Compression Ratio (0028,2112).
Required if Lossy Image Compression (0028,2110) is "01".</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="2050" element="0020" name="Presentation LUT Shape" type="1">
      <description>Specifies an identity transformation for the Presentation LUT, such that the output of all grayscale transformations defined in the IOD containing this Module are defined to be P-Values.
Enumerated Values:
IDENTITY - output is in P-Values.</description>
    </entry>
    <entry group="0088" element="0200" name="Icon Image Sequence" type="3">
      <description>This icon image is representative of the Image. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt; Include 'Image Pixel Macro' Table C.7-11b"/>
  </module>
  <macro table="C.8-81" name="MR Image and Spectroscopy Instance Macro">
    <entry group="0020" element="0012" name="Acquisition Number" type="3">
      <description>A number identifying the single continuous gathering of data over a period of time that resulted in this image.
Note: This number is not required to be unique across SOP Instances in a series. See also the description of the Referenced Raw Data Sequence (0008,9121).</description>
    </entry>
    <entry group="0008" element="002A" name="Acquisition DateTime" type="1C">
      <description>The date and time that the acquisition of data started.
Note: The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800).
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9073" name="Acquisition Duration" type="1C">
      <description>The time in seconds needed to run the prescribed pulse sequence. See C.7.6.16.2.2.1 for further explanation.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
      <section ref="C.7.6.16.2.2.1" name="">Figure C.7.6.16-2 shows the relationships among the various timing parameters used.
</section>
    </entry>
    <entry group="0008" element="9121" name="Referenced Raw Data Sequence" type="3">
      <description>A sequence that identifies the set of Raw Data SOP Class/Instance pairs of the Raw data which were used to derive this Image.
One or more Items may be included in this Sequence.
Note: The items of in this sequence may identify raw data that has not been stored or encoded as a DICOM object. This allows recognition that images and spectra in different instances have been reconstructed from the same raw data.</description>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0008" element="113A" name="Referenced Waveform Sequence" type="3">
      <description>References to waveforms acquired in conjunction with this image. These Waveforms may or may not be temporally synchronized with this image.
One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0008" element="9092" name="Referenced Image Evidence Sequence" type="1C">
      <description>Full set of Composite SOP Instances referred to inside the Referenced Image Sequences of this Enhanced MR Image SOP Instance. See C.8.13.2.1.2 for further explanation.
One or more Items may be included in this sequence.
Required if the Referenced Image Sequence (0008,1140) is present.</description>
      <section ref="C.8.13.2.1.2" name="">The intent of the Referenced Image Evidence Sequence (0008,9092) and Source Image Evidence Sequence (0008,9154) is to provide a list of all unique SOP Instances listed in the Referenced Image Sequence (0008,1140) and Source Image Sequence (0008,2112) attributes respectively.
</section>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0008" element="9154" name="Source Image Evidence Sequence" type="1C">
      <description>Full set of Composite SOP Instances referred to inside the Source Image Sequences of this Enhanced MR Image SOP Instance. See C.8.13.2.1.2 for further explanation.
One or more Items may be included in this sequence.
Required if the Source Image Sequence (0008,2112) is present.</description>
      <section ref="C.8.13.2.1.2" name="">The intent of the Referenced Image Evidence Sequence (0008,9092) and Source Image Evidence Sequence (0008,9154) is to provide a list of all unique SOP Instances listed in the Referenced Image Sequence (0008,1140) and Source Image Sequence (0008,2112) attributes respectively.
</section>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0008" element="9237" name="Referenced Grayscale Presentation State Sequence" type="1C">
      <description>References to Grayscale Presentation State instances acquired in conjunction with this instance.
Note: May only be used to reference Presentation States belonging to the acquired data and not to reference Presentation States generated subsequently such as during interpretation.
One or more Items may be included in this sequence.
Required if Presentation State is generated during acquisition, shall not be present otherwise.</description>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0018" element="9004" name="Content Qualification" type="1">
      <description>Content Qualification Indicator
Enumerated Values:
PRODUCT
RESEARCH
SERVICE
See C.8.13.2.1.1 for further explanation.</description>
      <section ref="C.8.13.2.1.1" name="">Content Qualification (0018,9004) shall have the value PRODUCT if the content (image or Spectroscopy data) was produced with approved hardware and software. It shall have the value RESEARCH or SERVICE if there is any doubt as to whether the content was produced with approved hardware and software.
If data with Content Qualification (0018,9004) of RESEARCH or SERVICE is used to derive other content then it is expected that this derived content will also have Content Qualification (0018,9004) set to RESEARCH or SERVICE.
The intent of this element is to allow annotation of an advisory message that indicates that this content may not be suitable for clinical interpretation.
</section>
    </entry>
    <entry group="0018" element="9100" name="Resonant Nucleus" type="1C">
      <description>Nucleus that is resonant at the transmitter frequency.
Defined Terms:
1H
3HE
7LI
13C
19F
23NA
31P
129XE
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9064" name="k-space Filtering" type="1C">
      <description>Describes k-space filtering applied. Shall be NONE if no k-space filter.
Defined Terms:
COSINE
COSINE_SQUARED
FERMI
GAUSSIAN
HAMMING
HANNING
LORENTZIAN
LRNTZ_GSS_TRNSFM
RIESZ
TUKEY
NONE
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="0087" name="Magnetic Field Strength" type="1C">
      <description>Nominal field strength of the MR Magnet, in Tesla.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9174" name="Applicable Safety Standard Agency" type="1">
      <description>Agency that established MR safety standard applicable to the acquisition of this Instance.
Defined Terms:
IEC
FDA
MHW</description>
    </entry>
    <entry group="0018" element="9175" name="Applicable Safety Standard Description" type="3">
      <description>Name and Version of the applicable standard.</description>
    </entry>
    <entry group="0020" element="4000" name="Image Comments" type="3">
      <description>User-defined comments about the image.</description>
    </entry>
  </macro>
  <macro table="C.8-82" name="MR Image Description Macro Attributes">
    <entry group="0008" element="9208" name="Complex Image Component" type="1">
      <description>Representation of complex data of frames in the SOP Instance. See C.8.13.3.1.5 for a description and Defined Terms.</description>
      <section ref="C.8.13.3.1.5" name="">The value of the Complex Image Component attribute (0008,9208) shall be used to indicate which component of the complex representation of the signal is represented in the pixel data.
Table C.8-85 specifies the Defined Terms for Complex Image Component attribute (0008,9208).
Table C.8-85
COMPLEX IMAGE COMPONENT ATTRIBUTE VALUES
<unrecognized-rows><term value="Defined Term Name" meaning="Defined Term Description"/><term value="MAGNITUDE" meaning="The magnitude component of the complex image data."/><term value="PHASE" meaning="The phase component of the complex image data."/><term value="REAL" meaning="The real component of the complex image data."/><term value="IMAGINARY" meaning="The imaginary component of the complex image data."/><term value="MIXED" meaning="Used only as a value in Complex Image Component (0008,9208) in the Enhanced MR Image Module if frames within the image SOP Instance contain different values for the Complex Image Component attribute in the MR Frame Type Functional Group."/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0008" element="9209" name="Acquisition Contrast" type="1">
      <description>Indication of acquisition contrast used with frames in the SOP Instance. See C.8.13.3.1.6 for a description and Defined Terms.</description>
      <section ref="C.8.13.3.1.6" name="">Table C.8-86 specifies the Defined Terms for Acquisition Contrast attribute (0008,9209).
Table C.8-86
ACQUISITION CONTRAST VALUES
<unrecognized-rows><term value="Defined Term Name" meaning="Defined Term Description"/><term value="DIFFUSION" meaning="Diffusion weighted contrast"/><term value="FLOW_ENCODED" meaning="Flow Encoded contrast"/><term value="FLUID_ATTENUATED" meaning="Fluid Attenuated T2 weighted contrast"/><term value="PERFUSION" meaning="Perfusion weighted contrast"/><term value="PROTON_DENSITY" meaning="Proton Density weighted contrast"/><term value="STIR" meaning="Short Tau Inversion Recovery"/><term value="TAGGING" meaning="Superposition of thin saturation bands onto image"/><term value="T1" meaning="T1 weighted contrast"/><term value="T2" meaning="T2 weighted contrast"/><term value="T2_STAR" meaning="T2* weighted contrast"/><term value="TOF" meaning="Time Of Flight weighted contrast"/><term value="UNKNOWN" meaning="Value should be UNKNOWN if acquisition contrasts were combined resulting in an unknown contrast. Also this value should be used when the contrast is not known."/><term value="MIXED" meaning="Used only as a value in Acquisition Contrast (0008,9209) attribute in the Enhanced MR Image Type Module if frames within the image SOP Instance contain different values for the Acquisition Contrast attribute in the MR Frame Type Functional Group."/></unrecognized-rows>
         </section>
    </entry>
  </macro>
  <module ref="C.8.13.4" table="C.8-87" name="MR Pulse Sequence Module Attributes">
    <entry group="0018" element="9005" name="Pulse Sequence Name" type="1C">
      <description>Name of the pulse sequence for annotation purposes. Potentially vendor-specific name.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="0023" name="MR Acquisition Type" type="1C">
      <description>Identification of spatial data encoding scheme.
Defined Terms:
1D
2D
3D
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9008" name="Echo Pulse Sequence" type="1C">
      <description>Echo category of pulse sequences.
Enumerated Values:
SPIN
GRADIENT
BOTH
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9011" name="Multiple Spin Echo" type="1C">
      <description>Multiple Spin Echo category of pulse sequence used to collect different lines in k-space for a single frame.
Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Echo Pulse sequence (0018,9008) equals SPIN or BOTH.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Echo Pulse sequence (0018,9008) equals SPIN or BOTH.</description>
    </entry>
    <entry group="0018" element="9012" name="Multi-planar Excitation" type="1C">
      <description>Technique that simultaneously excites several volumes.
Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9014" name="Phase Contrast" type="1C">
      <description>Phase Contrast Pulse sequence is a pulse sequence in which the flowing spins are velocity encoded in phase.
Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9015" name="Time of Flight Contrast" type="1C">
      <description>Time of Flight contrast is created by the inflow of blood in the saturated plane.
Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9017" name="Steady State Pulse Sequence" type="1C">
      <description>Steady State Sequence.
Defined Terms:
FREE_PRECESSION
TRANSVERSE
TIME_REVERSED
LONGITUDINAL
NONE
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9018" name="Echo Planar Pulse Sequence" type="1C">
      <description>Echo Planar category of Pulse Sequences.
Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9024" name="Saturation Recovery" type="1C">
      <description>Saturation recovery pulse sequence.
Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9025" name="Spectrally Selected Suppression" type="1C">
      <description>Spectrally Selected Suppression.
Defined Terms:
FAT
WATER
FAT_AND_WATER
SILICON_GEL
NONE
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9029" name="Oversampling Phase" type="1C">
      <description>Oversampling Phase.
Enumerated Values:
2D = phase direction
3D = out of plane direction
2D_3D = both
NONE
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9032" name="Geometry of k-Space Traversal" type="1C">
      <description>Geometry category of k-Space traversal.
Defined Terms:
RECTILINEAR
RADIAL
SPIRAL
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9034" name="Rectilinear Phase Encode Reordering" type="1C">
      <description>Rectilinear phase encode reordering.
Defined Terms:
LINEAR
CENTRIC
SEGMENTED
REVERSE_LINEAR
REVERSE_CENTRIC
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Geometry of k-Space Traversal (0018,9032) equals RECTILINEAR.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Geometry of k-Space Traversal (0018,9032) equals RECTILINEAR.</description>
    </entry>
    <entry group="0018" element="9033" name="Segmented k-Space Traversal" type="1C">
      <description>Segmented k-Space traversal. If Geometry of k-Space Traversal is rectilinear, multiple lines can be acquired at one time. If Geometry of k-Space Traversal is spiral or radial, paths can be interleaved and acquired at one time.
Enumerated Values:
SINGLE = successive single echo coverage
PARTIAL = segmented coverage
FULL = single shot full coverage
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9094" name="Coverage of k-Space" type="1C">
      <description>Coverage of k-Space in the ky-kz plane.
Defined Terms:
FULL
CYLINDRICAL
ELLIPSOIDAL
WEIGHTED
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and MR Acquisition Type (0018,0023) equals 3D.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and MR Acquisition Type (0018,0023) equals 3D.</description>
    </entry>
    <entry group="0018" element="9093" name="Number of k-Space Trajectories" type="1C">
      <description>Number of interleaves or shots.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
  </module>
  <macro table="C.8-88" name="MR Image Frame Type Macro Attributes">
    <entry group="0018" element="9226" name="MR Image Frame Type Sequence" type="1">
      <description>Identifies the characteristics of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0008" element="9007" name="&gt;Frame Type" type="1">
      <description>Type of Frame. A multi-valued attribute analogous to the Image Type (0008,0008).
Enumerated Values and Defined Terms are the same as those for the four values of the Image Type (0008,0008) attribute, except that the value MIXED is not allowed. See C.8.16.1 and C.8.13.3.1.1.</description>
      <section ref="C.8.16.1" name="">The Image Type (0008,0008) and associated Image Type related attributes provide a high level description of a multi-frame SOP Instance. These attributes describe properties that provide key summary information to users of the SOP Instance. Image Type (0008,0008) contains the highest level summary of what is in the SOP Instance.
The Frame Type (0008,9007) attribute mirrors the corresponding Image Type attribute and applies to the frame level rather than to the image level.
If more than one value is used by the set of frames for a given Frame Type (0008,9007) attribute value or associated attribute value then the corresponding value of the Image Type (0008,0008) or associated attribute shall contain a value of MIXED. This indicates that a mixed set of values exists within the multi-frame SOP Instance.
The value MIXED shall only be used in the Image Type (0008,0008) when the corresponding values for the individual frames are not equal. When a value of an attribute is equal for all frames, the same value shall be used for the corresponding value of the Image Type (0008,0008). Values 2 and 3 of Image Type (0008,0008) are an exception to the rule for MIXED: Values 2 and 3 may never have the value of MIXED as described in sections C.8.16.1.2 and C.8.16.1.3.
Image Type (0008,0008) and Frame Type (0008,9007) shall consist of four non-zero length values.
</section>
    </entry>
    <include ref="&gt;Include Common CT/MR Image Description Macro' Table C.8-131"/>
    <include ref="&gt;Include 'MR Image Description Macro' Table C.8-82"/>
  </macro>
  <macro table="C.8-89" name="MR Timing and Related Parameters Macro Attributes">
    <entry group="0018" element="9112" name="MR Timing and Related Parameters Sequence" type="1">
      <description>Identifies the timing and safety information of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="0080" name="&gt;Repetition Time" type="1C">
      <description>The time in ms between two successive excitations of the same volume. Shall be 0 (zero) if there is a single excitation per volume.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="1314" name="&gt;Flip Angle" type="1C">
      <description>Steady state angle in degrees to which the magnetic vector is flipped from the magnetic vector of the primary field.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="0091" name="&gt;Echo Train Length" type="1C">
      <description>Number of lines in k-space acquired per excitation of the same volume regardless of the type of echo or the number of frames derived from them. See section C.8.12.5.2.1.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9240" name="&gt;RF Echo Train Length" type="1C">
      <description>Number of RF echoes collected per RF shot (or excitation) per frame. A value of zero shall correspond to a pure gradient echo frame. Note that this value corresponds to the current frame. Several frames may be derived from the same shot. See section C.8.13.5.2.1.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9241" name="&gt;Gradient Echo Train Length" type="1C">
      <description>Number of gradient echoes collected per RF echo per shot (or excitation) per frame. A value of zero shall correspond to a pure RF echo frame. If RF Echo Train Length (0018,9240) is non zero and Gradient Echo Train Length is as well then only the central echo will be an RF Spin Echo, all others will be gradient echoes. See section C.8.13.5.2.1.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9239" name="&gt;Specific Absorption Rate Sequence" type="1C">
      <description>Sequence containing the methods of SAR calculation and the corresponding values. One or more items may be present.
Required if the system is capable of calculating Specific Absorption Rate (0018,9181).</description>
    </entry>
    <entry group="0018" element="9179" name="&gt;&gt;Specific Absorption Rate Definition" type="1">
      <description>Specification of the method of SAR calculation as defined in Applicable Safety Standard Description (0018,9174).
Defined Terms:
IEC_WHOLE_BODY
IEC_PARTIAL_BODY
IEC_HEAD
IEC_LOCAL</description>
    </entry>
    <entry group="0018" element="9181" name="&gt;&gt;Specific Absorption Rate Value" type="1">
      <description>Specific Absorption Rate in W/kg.</description>
    </entry>
    <entry group="0018" element="9180" name="&gt;Gradient Output Type" type="1C">
      <description>Definition of gradient output unit, for which the value is stored in Gradient Output (0018,9182).
Defined Terms:
DB_DT = in T/s
ELECTRIC_FIELD = in V/m
PER_NERVE_STIM = percentage of peripheral nerve stimulation
Required if the system is capable of calculating Gradient Output (0018,9182).</description>
    </entry>
    <entry group="0018" element="9182" name="&gt;Gradient Output" type="1C">
      <description>Unit is defined by Gradient Output Type (0018,9180).
Required if the system is capable of calculating Gradient Output (0018,9182).</description>
    </entry>
    <entry group="0018" element="9176" name="&gt;Operating Mode Sequence" type="1C">
      <description>Sequence of operating mode information relating to the frame/SOP instance as required to adhere to the Applicable Safety Standard Agency (0018,9174) regulations. One or more Items may be included in this sequence.
Required if required by law or regulations. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9177" name="&gt;&gt;Operating Mode Type" type="1">
      <description>Defined Terms:
STATIC FIELD
RF
GRADIENT</description>
    </entry>
    <entry group="0018" element="9178" name="&gt;&gt;Operating Mode" type="1">
      <description>Operating mode applicable for the defined by the applicable standard.
Defined Terms:
IEC_NORMAL
IEC_FIRST_LEVEL
IEC_SECOND_LEVEL</description>
    </entry>
  </macro>
  <macro table="C.8-90" name="MR Fov/geometry Macro Attributes">
    <entry group="0018" element="9125" name="MR FOV/Geometry Sequence" type="1">
      <description>Identifies the geometry parameters of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="1312" name="&gt;In-plane Phase Encoding Direction" type="1C">
      <description>The axes of the in-plane phase encoding with respect to the frame.
Enumerated Values:
COLUMN
ROW
OTHER
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9058" name="&gt;MR Acquisition Frequency Encoding Steps" type="1C">
      <description>Number of Frequency Encoding steps (kx) acquired
Required if Frame Type (0008,9007) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9231" name="&gt;MR Acquisition Phase Encoding Steps in-plane" type="1C">
      <description>Number of In-Plane Phase Encoding steps (ky) acquired
Required if Frame Type (0008,9007) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9232" name="&gt;MR Acquisition Phase Encoding Steps out-of-plane" type="1C">
      <description>Number of Out-of-Plane Phase Encoding steps (kz) acquired
Required if MR Acquisition Type (0018,0023) equals 3D and Frame Type (0008,9007) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="0093" name="&gt;Percent Sampling" type="1C">
      <description>Fraction of acquisition matrix lines acquired, expressed as a percent.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="0094" name="&gt;Percent Phase Field of View" type="1C">
      <description>Ratio of field of view dimension in phase direction to field of view dimension in frequency direction, expressed as a percent.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
  </macro>
  <macro table="C.8-91" name="MR Echo Macro Attributes">
    <entry group="0018" element="9114" name="MR Echo Sequence" type="1">
      <description>Identifies echo timing of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9082" name="&gt;Effective Echo Time" type="1C">
      <description>The time in ms between the middle of the excitation pulse and the peak of the echo produced for kx=0.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
  </macro>
  <macro table="C.8-92" name="MR Modifier Macro Attributes">
    <entry group="0018" element="9115" name="MR Modifier Sequence" type="1">
      <description>Identifies general acquisition parameters of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9009" name="&gt;Inversion Recovery" type="1C">
      <description>Inversion Recovery preparatory sequence.
Enumerated Values:
YES
NO
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9079" name="&gt;Inversion Times" type="1C">
      <description>Times in ms after the middle of inverting RF pulse to middle of excitation pulse to detect the amount of longitudinal magnetization.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Inversion Recovery (0018,9009) equals YES.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Inversion Recovery (0018,9009) equals YES.</description>
    </entry>
    <entry group="0018" element="9010" name="&gt;Flow Compensation" type="1C">
      <description>Flow Compensation.
Defined Terms:
ACCELERATION
VELOCITY
OTHER
NONE
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9183" name="&gt;Flow Compensation Direction" type="1C">
      <description>Flow Compensation Direction.
Enumerated Values:
PHASE
FREQUENCY
SLICE_SELECT
SLICE_AND_FREQ
SLICE_FREQ_PHASE
PHASE_AND_FREQ
SLICE_AND_PHASE
OTHER
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Flow Compensation (0018,9010) equals other than NONE.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Flow Compensation (0018,9010) equals other than NONE.</description>
    </entry>
    <entry group="0018" element="9016" name="&gt;Spoiling" type="1C">
      <description>Spoiling.
Enumerated Values:
RF = RF spoiled
GRADIENT = gradient spoiled
RF_AND_GRADIENT
NONE
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Echo Pulse Sequence (0018,9008) equals GRADIENT or BOTH.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Echo Pulse Sequence (0018,9008) equals GRADIENT or BOTH.</description>
    </entry>
    <entry group="0018" element="9021" name="&gt;T2 Preparation" type="1C">
      <description>T2 prepared Pulse Sequence.
Enumerated Values:
YES
NO
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9026" name="&gt;Spectrally Selected Excitation" type="1C">
      <description>Spectrally Selected Excitation.
Enumerated Values:
WATER = water excitation
FAT = fat excitation
NONE
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9027" name="&gt;Spatial Pre-saturation" type="1C">
      <description>Spatial Pre-saturation.
Defined Terms:
SLAB
NONE
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9081" name="&gt;Partial Fourier" type="1C">
      <description>Partial Fourier.
Enumerated Values:
YES
NO
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9036" name="&gt;Partial Fourier Direction" type="1C">
      <description>Direction of Partial Fourier.
Enumerated Values:
PHASE
FREQUENCY
SLICE_SELECT
COMBINATION
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Partial Fourier (0018,9081) equals YES.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Partial Fourier (0018,9081) equals YES.</description>
    </entry>
    <entry group="0018" element="9077" name="&gt;Parallel Acquisition" type="1C">
      <description>Parallel acquisition has been used to reduce measurement time.
Enumerated Values:
YES
NO
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9078" name="&gt;Parallel Acquisition Technique" type="1C">
      <description>Parallel acquisition characteristics.
Defined Terms:
PILS
SENSE
SMASH
OTHER
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Parallel Acquisition (0018,9077) equals YES.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Parallel Acquisition (0018,9077) equals YES.</description>
    </entry>
    <entry group="0018" element="9069" name="&gt;Parallel Reduction Factor In-plane" type="1C">
      <description>Measurement time reduction factor expressed as ratio of original and reduced measurement time for the in-plane direction.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Parallel Acquisition (0018,9077) equals YES.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Parallel Acquisition (0018,9077) equals YES.</description>
    </entry>
    <entry group="0018" element="9155" name="&gt;Parallel Reduction Factor out-of-plane" type="1C">
      <description>Measurement time reduction factor expressed as ratio of original and reduced measurement time for the out-of-plane direction
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Parallel Acquisition (0018,9077) equals YES.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Parallel Acquisition (0018,9077) equals YES.</description>
    </entry>
    <entry group="0018" element="9168" name="&gt;Parallel Reduction Factor Second In-plane" type="1C">
      <description>Measurement time reduction factor expressed as ratio of original and reduced measurement time for the second in-plane direction.
Only required for MR Spectroscopy SOP Instances.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Parallel Acquisition (0018,9077) equals YES.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Parallel Acquisition (0018,9077) equals YES.</description>
    </entry>
  </macro>
  <macro table="C.8-93" name="MR Imaging Modifier Macro Attributes">
    <entry group="0018" element="9006" name="MR Imaging Modifier Sequence" type="1">
      <description>Identifies sequence containing MR modifier Sequence Attributes. Only one item may be included in this sequence.</description>
    </entry>
    <entry group="0018" element="9020" name="&gt;Magnetization Transfer" type="1C">
      <description>Magnetization Transfer pulse sequence.
Enumerated Values:
ON_RESONANCE
OFF_RESONANCE
NONE
Required if Frame Type (0008,9007) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9022" name="&gt;Blood Signal Nulling" type="1C">
      <description>Blood Signal Nulling ("Black Blood") preparatory pulse sequence.
Enumerated Values:
YES
NO
Required if Frame Type (0008,9007) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9028" name="&gt;Tagging" type="1C">
      <description>Tagging.
Defined Terms:
GRID
LINE
NONE
Required if Frame Type (0008,9007) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9030" name="&gt;Tag Spacing First Dimension" type="1C">
      <description>Space between lines in mm.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Tagging (0018,9028) is GRID or LINE.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Tagging (0018,9028) is GRID or LINE.</description>
    </entry>
    <entry group="0018" element="9218" name="&gt;Tag Spacing Second Dimension" type="1C">
      <description>Space between the lines in mm in the other direction.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Tagging (0018,9028) is GRID.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Tagging (0018,9028) is GRID.</description>
    </entry>
    <entry group="0018" element="9019" name="&gt;Tag Angle First Axis" type="1C">
      <description>Angle of the tag lines relative to the rows axis (left to right) of the image, with a range of 0-180 degrees. The angle is increasing in clockwise direction.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Tagging (0018,9028) is GRID or LINE.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Tagging (0018,9028) is GRID or LINE.</description>
    </entry>
    <entry group="0018" element="9219" name="&gt;Tag Angle Second Axis" type="1C">
      <description>Angle of the tag lines relative to the rows axis (left to right) of the image, with a range of 0-180 degrees. The angle is increasing in clockwise direction.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Tagging (0018,9028) is GRID.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Tagging (0018,9028) is GRID.</description>
    </entry>
    <entry group="0018" element="9035" name="&gt;Tag Thickness" type="1C">
      <description>Thickness of the line in mm.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Tagging (0018,9028) is GRID or LINE.
Otherwise may be present if Frame Type (0008,9007) Value 1 is DERIVED and Tagging (0018,9028) is GRID or LINE.</description>
    </entry>
    <entry group="0018" element="9184" name="&gt;Tagging Delay" type="3">
      <description>Delay time in ms of the beginning of the application of the tagging pattern relative to the last R-peak.</description>
    </entry>
    <entry group="0018" element="9098" name="&gt;Transmitter Frequency" type="1C">
      <description>Center transmitter frequency in MHz.
Required if Frame Type (0008,9007) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="0095" name="&gt; Pixel Bandwidth" type="1C">
      <description>Reciprocal of the effective sampling period, in hertz per pixel.
Required if Frame Type (0008,9007) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
  </macro>
  <macro table="C.8-94" name="MR Receive Coil Macro Attributes">
    <entry group="0018" element="9042" name="MR Receive Coil Sequence" type="1">
      <description>A sequence that provides information about each receive coil used. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="1250" name="&gt;Receive Coil Name" type="1C">
      <description>Name of receive coil used.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9041" name="&gt;Receive Coil Manufacturer Name" type="2C">
      <description>Name of manufacturer of receive coil.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9043" name="&gt;Receive Coil Type" type="1C">
      <description>Type of receive coil used.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.
Defined Terms:
BODY
VOLUME = head, extremity, etc.
SURFACE
MULTICOIL</description>
    </entry>
    <entry group="0018" element="9044" name="&gt;Quadrature Receive Coil" type="1C">
      <description>Indicates whether the receive coil is quadrature.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.
Enumerated Values:
YES = quadrature or circularly polarized
NO = linear</description>
    </entry>
    <entry group="0018" element="9045" name="&gt;Multi-Coil Definition Sequence" type="1C">
      <description>A sequence that provides information regarding each element of a multi-coil. It should include attributes for all elements, whether used in the current acquisition or not. One or more Items shall be present.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Receive Coil Type (0018,9043) equals MULTICOIL. May be present otherwise only if Receive Coil Type (0018,9043) equals MULTICOIL.</description>
    </entry>
    <entry group="0018" element="9047" name="&gt;&gt;Multi-Coil Element Name" type="1">
      <description>Name of element of multi-coil.</description>
    </entry>
    <entry group="0018" element="9048" name="&gt;&gt;Multi-Coil Element Used" type="1">
      <description>Indicates whether the multi-coil element was used in the current acquisition.
Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="0018" element="9046" name="&gt;Multi-Coil Configuration" type="3">
      <description>A textual description of the configuration of multi-coil elements which was used in the current acquisition.</description>
    </entry>
  </macro>
  <macro table="C.8-95" name="MR Transmit Coil Macro Attributes">
    <entry group="0018" element="9049" name="MR Transmit Coil Sequence" type="1">
      <description>A sequence that provides information about the transmit coil used. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="1251" name="&gt;Transmit Coil Name" type="1C">
      <description>Name of transmit coil used.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9050" name="&gt;Transmit Coil Manufacturer Name" type="2C">
      <description>Name of manufacturer of transmit coil.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9051" name="&gt;Transmit Coil Type" type="1C">
      <description>Type of transmit coil used.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.
Defined Terms:
BODY
VOLUME = head, extremity, etc.
SURFACE</description>
    </entry>
  </macro>
  <macro table="C.8-96" name="MR Diffusion Macro Attributes">
    <entry group="0018" element="9117" name="MR Diffusion Sequence" type="1">
      <description>Identifies the diffusion parameters of this frame. One Item shall be included in this sequence.</description>
    </entry>
    <entry group="0018" element="9087" name="&gt;Diffusion b-value" type="1C">
      <description>Diffusion sensitization factor in sec/mm2. This is the actual b-value for original frames and those derived from frames with the same b-value, or the most representative b-value when derived from images with different b-values.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Diffusion b-matrix Sequence (0018,9601) is not present. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9075" name="&gt;Diffusion Directionality" type="1C">
      <description>Specifies whether diffusion conditions for the frame are directional, or isotropic with respect to direction.
Defined Terms:
DIRECTIONAL
BMATRIX
ISOTROPIC
NONE = to be used when Frame Type (0008,9007) value 4 equals DIFFUSION_ANISO or Diffusion b-value (0018,9087) is 0 (zero).
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9076" name="&gt;Diffusion Gradient Direction Sequence" type="1C">
      <description>Sequence containing orientations of all diffusion sensitization gradients that were applied during the preparation phase for this frame. One or more Items may be present.
Required if Diffusion Directionality (0018,9075) equals DIRECTIONAL</description>
    </entry>
    <entry group="0018" element="9089" name="&gt;&gt;Diffusion Gradient Orientation" type="1C">
      <description>The direction cosines of the diffusion gradient vector with respect to the patient
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9601" name="&gt;Diffusion b-matrix Sequence" type="1C">
      <description>The directional diffusion sensitization expressed as a 3x3 matrix with diagonal symmetry (with six unique elements from which the other elements can be derived).
The rows and columns of the matrix are the X (right to left), Y (anterior to posterior) and Z (foot to head) patient-relative orthogonal axes as defined in C.7.6.2.1.1.
The values are in units of ms/mm2.
Exactly one Item shall be present.
Required if Diffusion Directionality (0018,9075) equals BMATRIX.</description>
    </entry>
    <entry group="0018" element="9602" name="&gt;&gt;Diffusion b-value XX" type="1">
      <description>The value of b[X,X].</description>
    </entry>
    <entry group="0018" element="9603" name="&gt;&gt;Diffusion b-value XY" type="1">
      <description>The value of b[X,Y].</description>
    </entry>
    <entry group="0018" element="9604" name="&gt;&gt;Diffusion b-value XZ" type="1">
      <description>The value of b[X,Z].</description>
    </entry>
    <entry group="0018" element="9605" name="&gt;&gt;Diffusion b-value YY" type="1">
      <description>The value of b[Y,Y].</description>
    </entry>
    <entry group="0018" element="9606" name="&gt;&gt;Diffusion b-value YZ" type="1">
      <description>The value of b[Y,Z].</description>
    </entry>
    <entry group="0018" element="9607" name="&gt;&gt;Diffusion b-value ZZ" type="1">
      <description>The value of b[Z,Z].</description>
    </entry>
    <entry group="0018" element="9147" name="&gt;Diffusion Anisotropy Type" type="1C">
      <description>Class of diffusion anisotropy calculation. Defined Terms:
FRACTIONAL
RELATIVE
VOLUME_RATIO
Required if Frame Type (0008,9007) value 4 equals DIFFUSION_ANISO.</description>
    </entry>
  </macro>
  <macro table="C.8-97" name="MR Averages Macro Attributes">
    <entry group="0018" element="9119" name="MR Averages Sequence" type="1">
      <description>Identifies the averaging parameters of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="0083" name="&gt;Number of Averages" type="1C">
      <description>Maximum number of times any point in k-space is acquired.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
  </macro>
  <macro table="C.8-98" name="MR Spatial Saturation Macro Attributes">
    <entry group="0018" element="9107" name="MR Spatial Saturation Sequence" type="2">
      <description>A sequence that provides the position of spatial saturation bands deposited as part of the pulse sequence. Zero or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0018" element="9104" name="&gt;Slab Thickness" type="1">
      <description>Thickness of slab in mm.</description>
    </entry>
    <entry group="0018" element="9105" name="&gt;Slab Orientation" type="1">
      <description>The direction cosines of a normal vector perpendicular to the saturation plane with respect to the patient. See C.7.6.2.1.1 for further explanation.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
    <entry group="0018" element="9106" name="&gt;Mid Slab Position" type="1">
      <description>The x, y, and z coordinates of the midpoint of the slab plane in mm with respect to the patient. See C.7.6.2.1.1 for further explanation.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
  </macro>
  <macro table="C.8-99" name="Table C.8 99 MR Metabolite Map Macro Attributes">
    <entry group="0018" element="9152" name="MR Metabolite Map Sequence" type="1">
      <description>Describes the chemical shift parameters used to measure the resonant peaks from which the MR metabolite map represented by this frame was derived. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9080" name="&gt;Metabolite Map Description" type="1C">
      <description>Text describing the Metabolite Map.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9083" name="&gt;Metabolite Map Code Sequence" type="3">
      <description>When the measured peaks or their ratios can be related to metabolite substances, this sequence may be used to describe the metabolite substance whose resonant peaks are mapped in the Metabolite Map, or the ratio of substance resonant peaks that is mapped.
Only one item shall be present in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Defined Context ID = 4032"/>
    <entry group="0018" element="9084" name="&gt;Chemical Shift Sequence" type="3">
      <description>The list of frequencies that were used to create the Metabolite Map. One or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0018" element="9295" name="&gt;&gt;Chemical Shift Minimum Integration Limit in ppm" type="1">
      <description>Minimal value of Chemical Shift Frequency in ppm.</description>
    </entry>
    <entry group="0018" element="9296" name="&gt;&gt;Chemical Shift Maximum Integration Limit in ppm" type="1">
      <description>Maximum value of Chemical Shift Frequency in ppm.</description>
    </entry>
  </macro>
  <macro table="C.8-100" name="MR Velocity Encoding Macro Attributes">
    <entry group="0018" element="9197" name="MR Velocity Encoding Sequence" type="1">
      <description>Identifies the velocity encoding of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9090" name="&gt;Velocity Encoding Direction" type="1C">
      <description>The direction cosines of the velocity encoding vector with respect to the patient. See C.7.6.2.1.1 for further explanation.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
    <entry group="0018" element="9091" name="&gt;Velocity Encoding Minimum Value" type="1C">
      <description>Minimum velocity in cm/s.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9217" name="&gt;Velocity Encoding Maximum Value" type="1C">
      <description>Maximum velocity in cm/s.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
  </macro>
  <module ref="C.8.13.6" table="C.8-101" name="MR Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Type of equipment that originally acquired the data used to create the images in this Series.
Enumerated Values:
MR
See section C.7.3.1.1.1 for further explanation.</description>
    </entry>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence" type="1C">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance to which the Series is related (e.g. a Modality or General-Purpose Performed Procedure Step SOP Instance). The Sequence shall have one Item.
Required if the Modality Performed Procedure Step SOP Class , General Purpose Performed Procedure Step SOP Class is supported.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.8.14.1" table="C.8-102" name="MR Spectroscopy Module Attributes">
    <include ref="Include ' MR Image and Spectroscopy Instance Macro' Table C.8-81"/>
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Spectroscopy data characteristics. See C.8.14.5.1.1.</description>
      <section ref="C.8.14.5.1.1" name="">The Image Type (0008,0008) and Frame Type (0008,9007) are not included in this Macro but one or the other is always included in the Module or Macro that invokes this Macro, and they are therefore described here.
In addition to the requirements specified in C.8.16.1 Image Type and Frame Type, the following additional requirements and Defined Terms are specified.
</section>
    </entry>
    <include ref="Include 'MR Spectroscopy Description Macro' Table C.8.107"/>
    <entry group="0018" element="9098" name="Transmitter Frequency" type="1C">
      <description>Precession frequency in MHz of the nucleus being addressed for each spectral axis.
See section C.8.14.1.1 for further explanation of the ordering.
Required if Image Type (0008,0008) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9052" name="Spectral Width" type="1C">
      <description>Spectral width in Hz.
See section C.8.14.1.1 for further explanation of the ordering.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9053" name="Chemical Shift Reference" type="1C">
      <description>The chemical shift at the transmitter frequency in ppm.
See section C.8.14.1.1 for further explanation of the ordering.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9054" name="Volume Localization Technique" type="1C">
      <description>Name of volume localization technique used. Shall be "NONE" if no spatial localization was performed.
Defined Terms:
ILOPS
ISIS
PRIME
PRESS
SLIM
SLOOP
STEAM
NONE
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9126" name="Volume Localization Sequence" type="1C">
      <description>A sequence of one or more Items that provide the position of RF excitations used to select a volume of tissue. The selected volume is described by the intersection of the sequence Items.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Volume Localization Technique (0018,9054) is other than NONE. May be present if Volume Localization Technique (0018,9054) is other than NONE.</description>
    </entry>
    <entry group="0018" element="9104" name="&gt;Slab Thickness" type="1">
      <description>Thickness of slab in mm.</description>
    </entry>
    <entry group="0018" element="9105" name="&gt;Slab Orientation" type="1">
      <description>The direction cosines of a normal vector perpendicular to the selection plane with respect to the patient. See C.7.6.2.1.1 for further explanation.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
    <entry group="0018" element="9106" name="&gt;Mid Slab Position" type="1">
      <description>The x, y, and z coordinates of the mid-point of the slab in mm. See C.7.6.2.1.1 for further explanation.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
    <entry group="0018" element="9059" name="De-coupling" type="1C">
      <description>Indicates whether de-coupling was active.
Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9060" name="De-coupled Nucleus" type="1C">
      <description>Nucleus being de-coupled.
Defined Terms:
1H
3HE
7LI
13C
19F
23NA
31P
129XE
See section C.8.14.1.1 for further explanation of the ordering.
Required if De-coupling (0018,9059) equals YES.</description>
    </entry>
    <entry group="0018" element="9061" name="De-coupling Frequency" type="1C">
      <description>The center frequency (Hz) for the de-coupling.
See section C.8.14.1.1 for further explanation of the ordering.
Required if De-coupling (0018,9059) equals YES.</description>
    </entry>
    <entry group="0018" element="9062" name="De-coupling Method" type="1C">
      <description>The de-coupling modulation scheme used.
Defined Terms:
MLEV
WALTZ
NARROWBAND
Required if De-coupling (0018,9059) equals YES.</description>
    </entry>
    <entry group="0018" element="9063" name="De-coupling Chemical Shift Reference" type="1C">
      <description>The chemical shift in ppm at the de-coupling frequency.
See section C.8.14.1.1 for further explanation of the ordering.
Required if De-coupling (0018,9059) equals YES.</description>
    </entry>
    <entry group="0018" element="9065" name="Time Domain Filtering" type="1C">
      <description>Describes time domain filtering or apodization applied. Shall be NONE if no filtering operations were applied to the time domain data.
Defined Terms:
COSINE
COSINE_SQUARED
EXPONENTIAL
GAUSSIAN
HAMMING
HANNING
LORENTZIAN
LRNTZ_GSS_TRNSFM
NONE
See section C.8.14.1.1 for further explanation of the ordering.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9066" name="Number of Zero Fills" type="1C">
      <description>Number of zero fills added to the time domain data before FT. Shall be 0 (zero) if no zero filling performed.
See section C.8.14.1.1 for further explanation of the ordering.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9067" name="Baseline Correction" type="1C">
      <description>Describes baseline correction techniques. Shall be NONE if no baseline correction was performed.
Defined Terms:
LINEAR_TILT
LOCAL_LINEAR_FIT
POLYNOMIAL_FIT
SINC_DECONVOLUTN
TIME_DOMAIN_FIT
SPLINE
NONE
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9101" name="Frequency Correction" type="1C">
      <description>Specifies whether operations were performed to correct resonant frequency of metabolite peaks due to B0 field inhomogeneities.
Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9198" name="First Order Phase Correction" type="1C">
      <description>Describes whether a first order (frequency dependent) phase correction was applied to the spectral data.
Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9199" name="Water Referenced Phase Correction" type="1C">
      <description>Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
  </module>
  <module ref="C.8.14.2" table="C.8-103" name="MR Spectroscopy Pulse Sequence Module Attributes">
    <entry group="0018" element="9005" name="Pulse Sequence Name" type="1C">
      <description>Name of the pulse sequence for annotation purposes. Potentially vendor-specific name.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9200" name="MR Spectroscopy Acquisition Type" type="1C">
      <description>Identification of data encoding scheme.
Defined Terms:
SINGLE_VOXEL
ROW
PLANE
VOLUME
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9008" name="Echo Pulse Sequence" type="1C">
      <description>Echo category of pulse sequences.
Enumerated Values:
SPIN
GRADIENT
BOTH
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9011" name="Multiple Spin Echo" type="1C">
      <description>Multiple Spin Echo category of pulse sequence used to collect different lines in k-space for a single frame.
Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Echo Pulse Sequence (0018,9008) equals SPIN or BOTH.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Echo Pulse Sequence (0018,9008) equals SPIN or BOTH.</description>
    </entry>
    <entry group="0018" element="9012" name="Multi-planar Excitation" type="1C">
      <description>Technique that simultaneously excites several volumes.
Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9017" name="Steady State Pulse Sequence" type="1C">
      <description>Steady State Sequence.
Defined Terms:
FREE_PRECESSION
TRANSVERSE
TIME_REVERSED
LONGITUDINAL
NONE
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9018" name="Echo Planar Pulse Sequence" type="1C">
      <description>Echo Planar category of pulse-sequences.
Enumerated Values:
YES
NO
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9025" name="Spectrally Selected Suppression" type="1C">
      <description>Spectrally Selected Suppression.
Defined Terms:
WATER
FAT
FAT_AND_WATER
SILICON_GEL
NONE
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9032" name="Geometry of k-Space Traversal" type="1C">
      <description>Geometry category of k-Space traversal.
Defined Terms:
RECTILINEAR
RADIAL
SPIRAL
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9034" name="Rectilinear Phase Encode Reordering" type="1C">
      <description>Rectilinear phase encode reordering.
Defined Terms:
LINEAR
CENTRIC
SEGMENTED
REVERSE_LINEAR
REVERSE_CENTRIC
Required if Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and Geometry of k-Space Traversal (0018,9032) equals RECTILINEAR.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and Geometry of k-Space Traversal (0018,9032) equals RECTILINEAR.</description>
    </entry>
    <entry group="0018" element="9033" name="Segmented k-Space Traversal" type="1C">
      <description>Segmented k-Space traversal. If Geometry of k-Space Traversal is rectilinear, multiple lines can be acquired at one time. If Geometry of k-Space Traversal is spiral or radial, paths can be interleaved and acquired at one time.
Enumerated Values:
SINGLE = successive single echo coverage
PARTIAL = segmented coverage
FULL = single shot full coverage
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9094" name="Coverage of k-Space" type="1C">
      <description>Coverage of k-Space.
Defined Terms:
FULL
CYLINDRICAL
ELLIPSOIDAL
WEIGHTED
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and MR Spectroscopy Acquisition Type (0018,9200) equals VOLUME.
Otherwise may be present if Image Type (0008,0008) Value 1 is DERIVED and MR Spectroscopy Acquisition Type (0018,9200) equals VOLUME.</description>
    </entry>
    <entry group="0018" element="9093" name="Number of k-Space Trajectories" type="1C">
      <description>Number of interleaves or shots.
Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED. May be present otherwise.</description>
    </entry>
  </module>
  <macro table="C.8-104" name="MR Spectroscopy Frame Type Macro Attributes">
    <entry group="0018" element="9227" name="MR Spectroscopy Frame Type Sequence" type="1">
      <description>Identifies sequence containing Frame Type Attributes. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0008" element="9007" name="&gt;Frame Type" type="1">
      <description>Spectroscopy data characteristics. See C.8.14.5.1.1.</description>
      <section ref="C.8.14.5.1.1" name="">The Image Type (0008,0008) and Frame Type (0008,9007) are not included in this Macro but one or the other is always included in the Module or Macro that invokes this Macro, and they are therefore described here.
In addition to the requirements specified in C.8.16.1 Image Type and Frame Type, the following additional requirements and Defined Terms are specified.
</section>
    </entry>
    <include ref="&gt;Include 'MR Spectroscopy Description Macro' Table C.8.107"/>
  </macro>
  <macro table="C.8-105" name="MR Spectroscopy Fov/geometry Macro Attributes">
    <entry group="0018" element="9103" name="MR Spectroscopy FOV/Geometry Sequence" type="1">
      <description>Identifies the geometry parameters of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9127" name="&gt;Spectroscopy Acquisition Data Columns" type="1C">
      <description>Number of data points in the columns direction.
Required if Frame Type (0008,9007) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9095" name="&gt;Spectroscopy Acquisition Phase Rows" type="1C">
      <description>Number of Phase Encoding Rows.
Required if Frame Type (0008,9007) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9234" name="&gt; Spectroscopy Acquisition Phase Columns" type="1C">
      <description>Number of Phase Encoding Columns.
Required if Frame Type (0008,9007) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9159" name="&gt;Spectroscopy Acquisition Out-of-plane Phase Steps" type="1C">
      <description>Number of out-of-plane Phase Encoding steps.
Required if MR Spectroscopy Acquisition Type (0018,9200) equals PLANE and Frame Type (0008,9007) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="0093" name="&gt;Percent Sampling" type="1C">
      <description>Fraction of acquisition matrix lines acquired, expressed as a percent.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="0094" name="&gt;Percent Phase Field of View" type="1C">
      <description>Ratio of field of view dimension in phase direction to field of view dimension in frequency direction, expressed as a percent.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
  </macro>
  <module ref="C.8.14.4" table="C.8-106" name="MR Spectroscopy Data Module Attributes">
    <entry group="0028" element="0010" name="Rows" type="1">
      <description>Number of voxels in the vertical direction in the frame.</description>
    </entry>
    <entry group="0028" element="0011" name="Columns" type="1">
      <description>Number of voxels in the horizontal direction in the frame.</description>
    </entry>
    <entry group="0028" element="9001" name="Data Point Rows" type="1">
      <description>Number of rows of data points in spectroscopic data.</description>
    </entry>
    <entry group="0028" element="9002" name="Data Point Columns" type="1">
      <description>Number of columns of data points in spectroscopic data.</description>
    </entry>
    <entry group="0028" element="9108" name="Data Representation" type="1">
      <description>Data representation of the data points. Each data point shall have the same representation.
Enumerated Values:
COMPLEX = Data is complex pair
REAL = Data contains only real component
IMAGINARY = Data contains only imaginary component
MAGNITUDE = Magnitude data</description>
    </entry>
    <entry group="0028" element="9003" name="Signal Domain Columns" type="1">
      <description>Domain of represented signal in column direction.
Enumerated Values:
FREQUENCY
TIME</description>
    </entry>
    <entry group="0028" element="9235" name="Signal Domain Rows" type="1C">
      <description>Domain of represented signal in row direction.
Enumerated Values:
FREQUENCY
TIME
Required if Data Point Rows (0028,9001) has a value of more than 1.</description>
    </entry>
    <entry group="5600" element="0010" name="First Order Phase Correction Angle" type="1C">
      <description>First Order Phase Correction Angle. Number of values is determined by Row  Column  Number of Frames.
Required if First Order Phase Correction (0018,9198) equals YES</description>
    </entry>
    <entry group="5600" element="0020" name="Spectroscopy Data" type="1">
      <description>A data stream of the signal intensities that comprise the spectroscopic data. See C.8.14.4.1 for further explanation.</description>
      <section ref="C.8.14.4.1" name="">The Spectroscopy Data attribute (5600,0020) contains the Signal intensities for the spectra. The order of voxels sent for each spectral plane is left to right, top to bottom, i.e., the upper left voxel (labeled 1,1) is sent first followed by the remainder of row 1, followed by the first voxel of row 2 (labeled 2,1) then the remainder of row 2 and so on. Each "voxel" represents an entire spectrum. The complete spectral data from each voxel is sent, followed by the spectral data from the next voxel position.
The number of voxels on each frame are described by Rows (0028,0010) and Columns (0028,0011). The number of frames is described by Number of Frames (0028,0008). The frames may represent different locations in a 3D acquisition, or the same position at a different point of time, or a difference of some other combination of attributes.
Note:  Either Rows or Columns or both may have a value of 1 (e.g., for single voxel spectroscopy). A value of zero for the corresponding value of Pixel Spacing in the Pixel Measures Macro is permitted under these circumstances. See 10.7.1.3.

The spectral data points are ordered from lower effective magnetic field strength (down-field) to higher effective magnetic field strength (up-field) when the Signal Domain Columns (0028,9003) or Signal Domain Rows (0028,9235) attributes contain the value FREQUENCY and from first sample acquired to last sample acquired when the Signal Domain Columns (0028,9003) or Signal Domain Rows (0028,9235) attributes contain the value TIME.
For two-dimensional spectral acquisitions, the ordering is such that all data points from a row (corresponding to all data points acquired in an individual sampling period), are followed by all data points from the successive sampling period. Following all data of the rows from a given voxel position, the data from the subsequent voxel position are sent. The axis parallel to the row direction corresponds to the sampling time axis. The axis parallel to the column direction corresponds to the evolution time axis.
The dimensions of each spectrum that make up a voxel are described by Data Point Rows (0028,9001) and Data Point Columns (0028,9002). In the case of 1D spectra, the number of Data Point Rows shall be 1.
For a Data Representation (0028,9108) value of COMPLEX, the order of data points is real channel followed by imaginary channel for each spectral data point. For the other Data Representation values (REAL, IMAGINARY and MAGNITUDE), each spectral data point contains only a single value.
The Figure C.8-18 depicts 6 frames each made up of 4 rows and 4 columns of voxels. Specific values for Data Point Rows (0028,9001) and Data Point Columns (0028,9002) of these voxels are not depicted.
</section>
    </entry>
  </module>
  <macro table="C.8-107" name="MR Spectroscopy Description Macro Attributes">
    <entry group="0008" element="9206" name="Volumetric Properties" type="1">
      <description>Indication if geometric manipulations are possible with frames in the SOP Instance. See C.8.14.5.1.2 for a description and Enumerated Values.</description>
      <section ref="C.8.14.5.1.2" name="">See C.8.16.2.1.2. No additional requirements or Defined Terms.
</section>
    </entry>
    <entry group="0008" element="9207" name="Volume Based Calculation Technique" type="1">
      <description>Method used for volume calculations with frames in the SOP Instance. See C.8.14.5.1.3 for a description and Defined Terms.</description>
      <section ref="C.8.14.5.1.3" name="">See C.8.16.2.1.3 for requirements, but not Defined Terms.
Table C.8-110 specifies the Defined Terms for the Volume Based Calculation Technique (0008,9207) attribute.
Table C.8-110
VOLUME BASED CALCULATION TECHNIQUE ATTRIBUTE VALUES
<unrecognized-rows><term value="Defined Term Name" meaning="Defined Term Description"/><term value="MAX_IP" meaning="Maximum Intensity Projection"/><term value="MIN_IP" meaning="Minimum Intensity Projection"/><term value="NONE" meaning="Pixels not derived geometrically"/><term value="MIXED" meaning="Used only as a value in Volume Based Calculation Technique (0008,9207) attribute in the MR Spectroscopy Module if frames within the image SOP Instance contain different terms for the Volume Based Calculation Technique attribute in MR Spectroscopy Frame Type Functional Group."/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0008" element="9208" name="Complex Image Component" type="1">
      <description>Representation of complex data of frames in the SOP Instance. See C.8.14.5.1.4 for a description and Defined Terms.</description>
      <section ref="C.8.14.5.1.4" name="">The value of the Complex Image Component attribute (0008,9208) shall be used to indicate which component of the complex representation of the signal is represented in the spectroscopy data.
Table C.8-111 specifies the Defined Terms for Complex Image Component attribute (0008,9208).
Table C.8-111
COMPLEX IMAGE COMPONENT ATTRIBUTE VALUES
<unrecognized-rows><term value="Defined Term Name" meaning="Defined Term Description"/><term value="MAGNITUDE" meaning="The magnitude component of the complex spectroscopy data."/><term value="PHASE" meaning="The phase component of the complex spectroscopy data."/><term value="REAL" meaning="The real component of the complex spectroscopy data."/><term value="IMAGINARY" meaning="The imaginary component of the complex spectroscopy data."/><term value="COMPLEX" meaning="The real and imaginary components of the complex spectroscopy data"/><term value="MIXED" meaning="Used only as a value in Complex Image Component (0008,9208) in the MR Spectroscopy Module if frames within the image SOP Instance contain different values for the Complex Image Component attribute in the MR Spectroscopy Frame Type Functional Group."/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0008" element="9209" name="Acquisition Contrast" type="1">
      <description>Indication of acquisition contrast used with frames in the SOP Instance. See C.8.14.5.1.5 for a description and Defined Terms.</description>
      <section ref="C.8.14.5.1.5" name="">Table C.8-112 specifies the Defined Terms for Acquisition Contrast attribute (0008,9209).
Table C.8-112
ACQUISITION CONTRAST VALUES
<unrecognized-rows><term value="Defined Term Name" meaning="Defined Term Description"/><term value="PROTON_DENSITY" meaning="Proton Density weighted contrast"/><term value="T1" meaning="T1 weighted contrast"/><term value="T2" meaning="T2 weighted contrast"/><term value="UNKNOWN" meaning="Value should be UNKNOWN if acquisition contrasts were combined resulting in an unknown contrast. Also this value should be used when the contrast is not known."/><term value="MIXED" meaning="Used only as a value in Acquisition Contrast (0008,9209) attribute in the MR Spectroscopy Module if frames within the SOP Instance contain different values for the Acquisition Contrast attribute in the MR Spectroscopy Frame Type Functional Group."/></unrecognized-rows>
         </section>
    </entry>
  </macro>
  <module ref="C.8.15.1" table="C.8-113" name="CT Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Type of equipment that originally acquired the data used to create the images in this Series.
Enumerated Values:
CT
See section C.7.3.1.1.1 for further explanation.</description>
    </entry>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence" type="1C">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance to which the Series is related (e.g. a Modality or General-Purpose Performed Procedure Step SOP Instance). The Sequence shall have one Item.
Required if the Modality Performed Procedure Step SOP Class , General Purpose Performed Procedure Step SOP Class is supported.</description>
    </entry>
    <include ref="&gt;Include SOP Instance Reference Macro Table 10-11"/>
  </module>
  <module ref="C.8.15.2" table="C.8-114" name="Enhanced CT Image Module Attributes">
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image characteristics. See sections C.8.16.1 and C.8.15.2.1.1.</description>
    </entry>
    <include ref="Include Common CT/MR Image Description Macro' Table C.8-131"/>
    <entry group="0020" element="0012" name="Acquisition Number" type="3">
      <description>A number identifying the single continuous gathering of data over a period of time that resulted in this image.
Note: This number is not required to be unique across SOP Instances in a series. See also the description of the Referenced Raw Data Sequence (0008,9121).</description>
    </entry>
    <entry group="0008" element="002A" name="Acquisition DateTime" type="1C">
      <description>The date and time that the acquisition of data started.
Notes: 1. The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800) .
2. See C.7.6.16.2.2.1 for an overview of all acquisition related timing attributes.
Required if Image Type (0008,0008) Value 1 of this frame is ORIGINAL or MIXED, may be present otherwise.</description>
      <section ref="C.7.6.16.2.2.1" name="">Figure C.7.6.16-2 shows the relationships among the various timing parameters used.
</section>
    </entry>
    <entry group="0018" element="9073" name="Acquisition Duration" type="2C">
      <description>The time in seconds needed to complete the acquisition of data. See C.7.6.16.2.2.1 for further explanation.
Required if Image Type (0008,0008) Value 1 of this frame is ORIGINAL or MIXED, may be present otherwise.</description>
      <section ref="C.7.6.16.2.2.1" name="">Figure C.7.6.16-2 shows the relationships among the various timing parameters used.
</section>
    </entry>
    <entry group="0008" element="9121" name="Referenced Raw Data Sequence" type="3">
      <description>A sequence that identifies the set of Raw Data SOP Class/Instance pairs of the Raw data that were used to derive this Image.
One or more Items may be included in this Sequence.
Note: The items of in this sequence may identify raw data that has not been stored or encoded as a DICOM object. This allows recognition that images in different instances have been reconstructed from the same raw data.</description>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0008" element="113A" name="Referenced Waveform Sequence" type="3">
      <description>References to waveforms acquired in conjunction with this image. These Waveforms may or may not be temporally synchronized with this image.
One or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0008" element="9092" name="Referenced Image Evidence Sequence" type="1C">
      <description>Full set of Composite SOP Instances referring to image SOP Instances inside the frames of this Enhanced CT Image SOP Instance. See C.8.13.2.1.2 for further explanation.
One or more Items may be included in this sequence.
Required if the Referenced Image Sequence (0008,1140) is present.</description>
      <section ref="C.8.13.2.1.2" name="">The intent of the Referenced Image Evidence Sequence (0008,9092) and Source Image Evidence Sequence (0008,9154) is to provide a list of all unique SOP Instances listed in the Referenced Image Sequence (0008,1140) and Source Image Sequence (0008,2112) attributes respectively.
</section>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0008" element="9154" name="Source Image Evidence Sequence" type="1C">
      <description>Full set of Composite SOP Instances used as source image SOP Instances inside the frames of this Enhanced CT Image SOP Instance. See C.8.13.2.1.2 for further explanation.
One or more Items may be included in this sequence.
Required if the Source Image Sequence (0008,2112) is present.</description>
      <section ref="C.8.13.2.1.2" name="">The intent of the Referenced Image Evidence Sequence (0008,9092) and Source Image Evidence Sequence (0008,9154) is to provide a list of all unique SOP Instances listed in the Referenced Image Sequence (0008,1140) and Source Image Sequence (0008,2112) attributes respectively.
</section>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0008" element="9237" name="Referenced Grayscale Presentation State Sequence" type="1C">
      <description>References to Grayscale Presentation State instances acquired in conjunction with this instance.
Note: May only be used to reference Presentation States belonging to the acquired data and not to reference Presentation States generated subsequently such as during interpretation.
One or more Items may be included in this sequence.
Required if Presentation State is generated during acquisition, shall not be present otherwise.</description>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (planes) in this image. This value shall be 1.</description>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data. Enumerated Value: MONOCHROME2.
See C.7.6.3.1.2 for definition of this term.</description>
      <section ref="C.7.6.3.1.2" name="">The value of Photometric Interpretation (0028,0004) specifies the intended interpretation of the image pixel data.
See PS 3.5 for restrictions imposed by compressed Transfer Syntaxes.
The following values are defined. Other values are permitted but the meaning is not defined by this Standard.
MONOCHROME1 = Pixel data represent a single monochrome image plane. The minimum sample value is intended to be displayed as white after any VOI gray scale transformations have been performed. See PS 3.4. This value may be used only when Samples per Pixel (0028,0002) has a value of 1.
MONOCHROME2 = Pixel data represent a single monochrome image plane. The minimum sample value is intended to be displayed as black after any VOI gray scale transformations have been performed. See PS 3.4. This value may be used only when Samples per Pixel (0028,0002) has a value of 1.
PALETTE COLOR = Pixel data describe a color image with a single sample per pixel (single image plane). The pixel value is used as an index into each of the Red, Blue, and Green Palette Color Lookup Tables (0028,1101-1103&amp;1201-1203). This value may be used only when Samples per Pixel (0028,0002) has a value of 1. When the Photometric Interpretation is Palette Color; Red, Blue, and Green Palette Color Lookup Tables shall be present.
RGB = Pixel data represent a color image described by red, green, and blue image planes. The minimum sample value for each color plane represents minimum intensity of the color. This value may be used only when Samples per Pixel (0028,0002) has a value of 3.
HSV = Retired.
ARGB = Retired.
CMYK = Retired.
YBR_FULL = Pixel data represent a color image described by one luminance (Y) and two chrominance planes (CB and CR). This photometric interpretation may be used only when Samples per Pixel (0028,0002) has a value of 3. Black is represented by Y equal to zero. The absence of color is represented by both CB and CR values equal to half full scale.
Note:  In the case where the Bits Allocated (0028,0100) has value of 8 half full scale is 128.

In the case where Bits Allocated (0028,0100) has a value of 8 then the following equations convert between RGB and YCBCR Photometric Interpretation.
Y =  +  .2990R  +  .5870G  +  .1140B
CB =  -  .1687R  -  .3313G  +  .5000B  +  128
CR =  +  .5000R  -  .4187G  -  .0813B  +  128
Note:  The above is based on CCIR Recommendation 601-2 dated 1990.

YBR_FULL_422 = The same as YBR_FULL except that the CB and CR values are sampled horizontally at half the Y rate and as a result there are half as many CB and CR values as Y values.
This Photometric Interpretation is only allowed with Planar Configuration (0028,0006) equal to 0. Two Y values shall be stored followed by one CB and one CR value. The CB and CR values shall be sampled at the location of the first of the two Y values. For each Row of Pixels, the first CB and CR samples shall be at the location of the first Y sample. The next CB and CR samples shall be at the location of the third Y sample etc.
Note:  This subsampling is often referred to as cosited sampling.

YBR_PARTIAL_422 = The same as YBR_FULL_422 except that:
1. black corresponds to Y = 16;
2. Y is restricted to 220 levels (i.e. the maximum value is 235);
3. CB and CR each has a minimum value of 16;
4. CB and CR are restricted to 225 levels (i.e. the maximum value is 240);
5. lack of color is represented by CB and CR equal to 128.
In the case where Bits Allocated (0028,0100) has value of 8 then the following equations convert between RGB and YBR_PARTIAL_422 Photometric Interpretation
Y =  +  .2568R  +  .5041G  +  .0979B  +  16
CB =  -  .1482R  -  .2910G  +  .4392B  +  128
CR =  +  .4392R  -  .3678G  -  .0714B  +  128
Note:  The above is based on CCIR Recommendation 601-2 dated 1990.

YBR_PARTIAL_420 = The same as YBR_PARTIAL_422 except that the CB and CR values are sampled horizontally and vertically at half the Y rate and as a result there are four times less CB and CR values than Y values, versus twice less for YBR_PARTIAL_422.
This Photometric Interpretation is only allowed with Planar Configuration (0028,0006) equal to 0. The CB and CR values shall be sampled at the location of the first of the two Y values. For the first Row of Pixels (etc.), the first CB and CR samples shall be at the location of the first Y sample. The next CB and CR samples shall be at the location of the third Y sample etc. The next Rows of Pixels containing CB and CR samples (at the same locations than for the first Row) will be the third etc.
YBR_ICT = Irreversible Color Transformation:
Pixel data represent a color image described by one luminance (Y) and two chrominance planes (CB and CR). This photometric interpretation may be used only when Samples per Pixel (0028,0002) has a value of 3. Black is represented by Y equal to zero. The absence of color is represented by both CB and CR values equal to zero.
Regardless of the value of Bits Allocated (0028,0100), the following equations convert between RGB and YCBCR Photometric Interpretation.
Y =  +  .29900R  +  .58700G  +  .11400B
CB =  -  .16875R  -  .33126G  +  .50000B
CR =  +  .50000R  -  .41869G  -  .08131B
Notes:  1. The above is based on ISO/IEC 15444-1 (JPEG 2000).
  2. In a JPEG 2000 bitstream, DC level shifting (used if the untransformed components are unsigned) is applied before forward color transformation, and the transformed components may be signed (unlike in JPEG ISO/IEC 10918-1).
  3. In JPEG 2000, spatial down-sampling of the chrominance components, if performed, is signaled in the JPEG 2000 bitstream.

YBR_RCT = Reversible Color Transformation:
Pixel data represent a color image described by one luminance (Y) and two chrominance planes (CB and CR). This photometric interpretation may be used only when Samples per Pixel (0028,0002) has a value of 3. Black is represented by Y equal to zero. The absence of color is represented by both CB and CR values equal to zero.
Regardless of the value of Bits Allocated (0028,0100), the following equations convert between RGB and YBR_RCT Photometric Interpretation.
Y = R + 2G +B) / 4        (Note:  mean floor)
CB = B - G
CR = R - G
The following equations convert between YBR_RCT and RGB Photometric Interpretation.
G = Y –  (CR + CB) / 4
R = CR + G
B = CB + G
Notes:  1. The above is based on ISO/IEC 15444-1 (JPEG 2000).
  2. In a JPEG 2000 bitstream, DC level shifting (used if the untransformed components are unsigned) is applied before forward color transformation, and the transformed components may be signed (unlike in JPEG ISO/IEC 10918-1).
  3. This photometric interpretation is a reversible approximation to the YUV transformation used in PAL and SECAM.

</section>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated. This value shall be 16.</description>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored. This value shall be 12 or16.</description>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data. Each sample shall have the same high bit. Shall be one less than the value in Bits Stored (0028,0101).</description>
    </entry>
    <entry group="0018" element="9004" name="Content Qualification" type="1">
      <description>Content Qualification Indicator
Enumerated Values:
PRODUCT
RESEARCH
SERVICE
See C.8.13.2.1.1 for further explanation.</description>
      <section ref="C.8.13.2.1.1" name="">Content Qualification (0018,9004) shall have the value PRODUCT if the content (image or Spectroscopy data) was produced with approved hardware and software. It shall have the value RESEARCH or SERVICE if there is any doubt as to whether the content was produced with approved hardware and software.
If data with Content Qualification (0018,9004) of RESEARCH or SERVICE is used to derive other content then it is expected that this derived content will also have Content Qualification (0018,9004) set to RESEARCH or SERVICE.
The intent of this element is to allow annotation of an advisory message that indicates that this content may not be suitable for clinical interpretation.
</section>
    </entry>
    <entry group="0020" element="4000" name="Image Comments" type="3">
      <description>User-defined comments about the image</description>
    </entry>
    <entry group="0028" element="0301" name="Burned In Annotation" type="1">
      <description>Indicates whether or not the image contains sufficient burned in annotation to identify the patient and date the image was acquired.
Enumerated Values:
NO
This means that images that contain this Module shall not contain such burned in annotations.</description>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1">
      <description>Specifies whether an Image has undergone lossy compression. Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5 for further explanation.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2112" name="Lossy Image Compression Ratio" type="1C">
      <description>Describes the approximate lossy compression ratio(s) that have been applied to this image.
See C.7.6.1.1.5 for further explanation.
May be multivalued if successive lossy compression steps have been applied.
Note: For example, a compression ratio of 30:1 would be described in this Attribute with a single value of 30.
Required if Lossy Images Compression (0028,2110) is "01".</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2114" name="Lossy Image Compression Method" type="1C">
      <description>A label for the lossy compression method(s) that have been applied to this image.
See C.7.6.1.1.5 for further explanation.
May be multivalued if successive lossy compression steps have been applied; the value order shall correspond to the values of Lossy Image Compression Ratio (0028,2112).
Required if Lossy Image Compression (0028,2110) is "01".</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="2050" element="0020" name="Presentation LUT Shape" type="1">
      <description>Specifies an identity transformation for the Presentation LUT, such that the output of all grayscale transformations defined in the IOD containing this Module are defined to be P-Values.
Enumerated Values:
IDENTITY - output is in P-Values.</description>
    </entry>
    <entry group="0088" element="0200" name="Icon Image Sequence" type="3">
      <description>This icon image is representative of the Image. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt; Include 'Image Pixel Macro' Table C.7-11b" description="See Section F.7."/>
  </module>
  <macro table="C.8-117" name="CT Image Frame Type Macro Attributes">
    <entry group="0018" element="9329" name="CT Image Frame Type Sequence" type="1">
      <description>Identifies the characteristics of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0008" element="9007" name="&gt;Frame Type" type="1">
      <description>Type of Frame. A multi-valued attribute analogous to the Image Type (0008,0008).
Enumerated Values and Defined Terms are the same as those for the four values of the Image Type (0008,0008) attribute, except that the value MIXED is not allowed. See sections C.8.16.1 and C.8.15.2.1.1.1.</description>
    </entry>
    <include ref="&gt; Include Common CT/MR Image Description Macro' Table C.8-131"/>
  </macro>
  <macro table="C.8-118" name="CT Acquisition Type Macro Attributes">
    <entry group="0018" element="9301" name="CT Acquisition Type Sequence" type="1">
      <description>Contains the attributes defining the CT acquisition mode. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9302" name="&gt;Acquisition Type" type="1C">
      <description>Description of the method used during acquisition of this frame. See C.8.15.3.2.1 for Defined Terms.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
      <section ref="C.8.15.3.2.1" name="">Acquisition Type (0018,9302) has the following Defined Terms:
SEQUENCED  identifies that the acquisition was performed by acquiring single or multi detector data while rotating the source about the gantry while the table is not moving. Additional slices are acquired by incrementing the table position and again rotating the source about the gantry while the table is not moving.
SPIRAL  identifies that the acquisition was performed by acquiring data while rotating the source about the gantry while continuously moving the table.
CONSTANT_ANGLE  identifies that the acquisition was performed by holding the source at a constant angle and moving the table to obtain a projection image (e.g., a localizer image).
STATIONARY  identifies that the acquisition was performed by holding the table at a constant position and acquiring multiple slices over time at the same location.
FREE  identifies that the acquisition was performed while rotating the source about the gantry while the table movement is under direct control of a human operator or under the control of an analysis application (e.g., fluoroscopic image).
</section>
    </entry>
    <entry group="0018" element="9303" name="&gt;Tube Angle" type="1C">
      <description>The constant angle at which the x-ray source is located during acquisition. 0 degrees means that the source is located at the highest point of the gantry orbit. Degrees increase from 0 to positive 360 in a clockwise direction as viewed when facing the gantry where the table enters the gantry.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Acquisition Type (0018,9302) is CONSTANT_ANGLE.
May be present otherwise if Frame Type (0008,9007) Value 1 of this frame is DERIVED and Acquisition Type (0018,9302) is CONSTANT_ANGLE.</description>
    </entry>
    <entry group="0018" element="9333" name="&gt;Constant Volume Flag" type="1C">
      <description>Identifies that the acquisition was performed by repetitively acquiring the same volume set over a period of time.
Note: The Acquisition Type (0018,9302) value may be SEQUENCED, SPIRAL or STATIONARY depending on whether table movement is necessary to cover the volume.
Enumerated Values
YES
NO
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9334" name="&gt;Fluoroscopy Flag" type="1C">
      <description>Identifies that near real-time display of a block of continuously acquired data was performed, which may result in a lower than usual image quality.
Enumerated Values
YES
NO
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
  </macro>
  <macro table="C.8-119" name="CT Acquisition Details Macro Attributes">
    <entry group="0018" element="9304" name="CT Acquisition Details Sequence" type="1">
      <description>Contains the attributes defining the details of the acquisition. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="1140" name="&gt;Rotation Direction" type="1C">
      <description>Direction of rotation of the source about the gantry, as viewed while facing the gantry where the table enters the gantry.
Enumerated Values:
CW = clockwise
CC = counter clockwise
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Acquisition Type (0018,9302) is other than CONSTANT_ANGLE.
Otherwise may be present if Frame Type (0008,9007) Value 1 of this frame is DERIVED and Acquisition Type (0018,9302) is other than CONSTANT_ANGLE.</description>
    </entry>
    <entry group="0018" element="9305" name="&gt;Revolution Time" type="1C">
      <description>The time in seconds of a complete revolution of the source around the gantry orbit. This value is independent of the Reconstruction Angle (0018,9319) of the frame.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Acquisition Type (0018,9302) is other than CONSTANT_ANGLE.
Otherwise may be present if Frame Type (0008,9007) Value 1 of this frame is DERIVED and Acquisition Type (0018,9302) is other than CONSTANT_ANGLE.</description>
    </entry>
    <entry group="0018" element="9306" name="&gt;Single Collimation Width" type="1C">
      <description>The width of a single row of acquired data (in mm).
Note: Adjacent physical detector rows may have been combined to form a single effective acquisition row.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9307" name="&gt;Total Collimation Width" type="1C">
      <description>The width of the total collimation (in mm) over the area of active x-ray detection.
Note: This will be equal to the number of effective detector rows multiplied by single collimation width.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="1130" name="&gt;Table Height" type="1C">
      <description>The distance in mm from the top of the patient table to the center of rotation of the source (i.e. the data collection center or isocenter). The distance is positive when the table is below the data collection center.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="1120" name="&gt;Gantry/Detector Tilt" type="1C">
      <description>Nominal angle of tilt in degrees of the scanning gantry. Not intended for mathematical computations. Zero degrees means the gantry is not tilted, negative degrees are when the top of the gantry is tilted away from where the table enters the gantry.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="0090" name="&gt;Data Collection Diameter" type="1C">
      <description>The diameter in mm of the region over which data were collected. See C.8.15.3.6.1.
Note: In the case of an Acquisition Type (0018,9302) of CONSTANT_ANGLE, the diameter is that in a plane normal to the central ray of the diverging X-Ray beam as it passes through the data collection center.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
      <section ref="C.8.15.3.6.1" name="">In Figure C.8-19 the relationship of the Geometric Attributes within the CT Geometry and CT Reconstruction functional groups is shown. The figure, viewed from the front of the gantry (where the table enters the gantry), is informative only and is not meant to represent a standardization of an equipment-based frame of reference.
 Figure C.8-19: Geometry of CT Acquisition System

</section>
    </entry>
  </macro>
  <macro table="C.8-120" name="CT Table Dynamics Macro Attributes">
    <entry group="0018" element="9308" name="CT Table Dynamics Sequence" type="1">
      <description>Contains the attributes defining the movement of the CT table. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9309" name="&gt;Table Speed" type="1C">
      <description>The distance in mm that the table moves in one second during the gathering of data that resulted in this frame.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Acquisition Type (0018,9302) is SPIRAL or CONSTANT_ANGLE.
May be present otherwise if Frame Type (0008,9007) Value 1 of this frame is DERIVED and Acquisition Type (0018,9302) is SPIRAL or CONSTANT_ANGLE.</description>
    </entry>
    <entry group="0018" element="9310" name="&gt;Table Feed per Rotation" type="1C">
      <description>Motion of the table (in mm) during a complete revolution of the source around the gantry orbit.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Acquisition Type (0018,9302) is SPIRAL.
May be present otherwise if Frame Type (0008,9007) Value 1 of this frame is DERIVED and Acquisition Type (0018,9302) is SPIRAL.</description>
    </entry>
    <entry group="0018" element="9311" name="&gt;Spiral Pitch Factor" type="1C">
      <description>Ratio of the Table Feed per Rotation (0018,9310) to the Total Collimation Width (0018,9307).
See C.8.15.3.4.1 for further explanation and some examples.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Acquisition Type (0018,9302) is SPIRAL.
May be present otherwise if Frame Type (0008,9007) Value 1 of this frame is DERIVED and Acquisition Type (0018,9302) is SPIRAL.</description>
      <section ref="C.8.15.3.4.1" name="">The formula for Spiral Pitch Factor (0018,9311) in terms of Table Feed per Rotation (0018,9310) and Total Collimation Width (0018,9307) is:
  Spiral Pitch Factor = (Table Feed per Rotation (mm))/(Total Collimation Width (mm))
An example calculation of Spiral Pitch Factor (0018,9311) for a single slice spiral acquisition of an image with a Total Collimation Width of 2.5mm and a Table Feed per Rotation of 10mm is:
  Spiral Pitch Factor = (10 mm)/(2.5 mm) = 4.0
An example calculation of Spiral Pitch Factor (0018,9311) for a multiple slice spiral acquisition having a Total Collimation Width of 20mm and a Table Feed per Rotation of 10mm is:
  Spiral Pitch Factor = (10 mm)/(20 mm) = 0.5
</section>
    </entry>
  </macro>
  <macro table="C.8-121" name="CT Position Macro Attributes">
    <entry group="0018" element="9326" name="CT Position Sequence" type="1">
      <description>Contains the attributes defining the CT geometry. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9327" name="&gt;Table Position" type="1C">
      <description>Relative longitudinal position of acquisition location of this frame in mm from an implementation specific reference point. Shall be relative to the same reference point for all frames in this SOP Instance, but may be different from the reference point in other SOP Instances. Positions as the table moves into the gantry viewed from the front are more negative.
Notes: 1. For contiguous slices reconstructed from multiple detectors one would expect different values for adjacent slices.
2. Lateral positioning or tilting or swiveling are not described.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9313" name="&gt;Data Collection Center (Patient)" type="1C">
      <description>The x, y, and z coordinates (in the patient coordinate system) in mm of the center of the region in which data were collected. See C.8.15.3.6.1.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
      <section ref="C.8.15.3.6.1" name="">In Figure C.8-19 the relationship of the Geometric Attributes within the CT Geometry and CT Reconstruction functional groups is shown. The figure, viewed from the front of the gantry (where the table enters the gantry), is informative only and is not meant to represent a standardization of an equipment-based frame of reference.
 Figure C.8-19: Geometry of CT Acquisition System

</section>
    </entry>
    <entry group="0018" element="9318" name="&gt;Reconstruction Target Center (Patient)" type="1C">
      <description>The x, y, and z coordinates (in the patient coordinate system) of the reconstruction center target point as used for reconstruction in mm. See C.8.15.3.6.1.
Note: If the reconstructed image is not magnified or panned the value corresponds with the Data Collection Center (0018,9313) attribute.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
      <section ref="C.8.15.3.6.1" name="">In Figure C.8-19 the relationship of the Geometric Attributes within the CT Geometry and CT Reconstruction functional groups is shown. The figure, viewed from the front of the gantry (where the table enters the gantry), is informative only and is not meant to represent a standardization of an equipment-based frame of reference.
 Figure C.8-19: Geometry of CT Acquisition System

</section>
    </entry>
  </macro>
  <macro table="C.8-122" name="CT Geometry Macro Attributes">
    <entry group="0018" element="9312" name="CT Geometry Sequence" type="1">
      <description>Contains the attributes defining the CT geometry. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="1110" name="&gt;Distance Source to Detector" type="1C">
      <description>Distance in mm from source to detector center. See C.8.15.3.6.1.
Note: This value is traditionally referred to as Source Image Receptor Distance (SID).
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
      <section ref="C.8.15.3.6.1" name="">In Figure C.8-19 the relationship of the Geometric Attributes within the CT Geometry and CT Reconstruction functional groups is shown. The figure, viewed from the front of the gantry (where the table enters the gantry), is informative only and is not meant to represent a standardization of an equipment-based frame of reference.
 Figure C.8-19: Geometry of CT Acquisition System

</section>
    </entry>
    <entry group="0018" element="9335" name="&gt;Distance Source to Data Collection Center" type="1C">
      <description>Distance in mm from source to data collection center. See C.8.15.3.6.1.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
      <section ref="C.8.15.3.6.1" name="">In Figure C.8-19 the relationship of the Geometric Attributes within the CT Geometry and CT Reconstruction functional groups is shown. The figure, viewed from the front of the gantry (where the table enters the gantry), is informative only and is not meant to represent a standardization of an equipment-based frame of reference.
 Figure C.8-19: Geometry of CT Acquisition System

</section>
    </entry>
  </macro>
  <macro table="C.8-123" name="CT Reconstruction Macro Attributes">
    <entry group="0018" element="9314" name="CT Reconstruction Sequence" type="1">
      <description>Contains the attributes holding information about the reconstruction techniques used. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9315" name="&gt;Reconstruction Algorithm" type="1C">
      <description>Description of the algorithm used when reconstructing the image from the data acquired during the acquisition process.
Defined Terms:
FILTER_BACK_PROJ
ITERATIVE
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="1210" name="&gt;Convolution Kernel" type="1C">
      <description>A label describing the convolution kernel or algorithm used to reconstruct the data. A single value shall be present.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9316" name="&gt;Convolution Kernel Group" type="1C">
      <description>A label describing the group that the Convolution Kernel (0018,1210) belongs.
Defined Terms:
BRAIN
SOFT_TISSUE
LUNG
BONE
CONSTANT_ANGLE
Required if Convolution Kernel (0018,1210) is present. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="1100" name="&gt;Reconstruction Diameter" type="1C">
      <description>The diameter in mm of the region from which data were used in creating the reconstruction of the image. Data may exist outside this region and portions of the patient may exist outside this region. See C.8.15.3.6.1.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Reconstruction Field of View (0018,9317) is not present.
Otherwise may be present if Frame Type (0008,9007) Value 1 of this frame is DERIVED and Reconstruction Field of View (0018,9317) is not present.</description>
      <section ref="C.8.15.3.6.1" name="">In Figure C.8-19 the relationship of the Geometric Attributes within the CT Geometry and CT Reconstruction functional groups is shown. The figure, viewed from the front of the gantry (where the table enters the gantry), is informative only and is not meant to represent a standardization of an equipment-based frame of reference.
 Figure C.8-19: Geometry of CT Acquisition System

</section>
    </entry>
    <entry group="0018" element="9317" name="&gt;Reconstruction Field of View" type="1C">
      <description>The field of view width (x-dimension) followed by height (y-dimension) as used for reconstruction in mm.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Reconstruction Diameter (0018,1100) is not present.
Otherwise may be present if Frame Type (0008,9007) Value 1 of this frame is DERIVED and Reconstruction Diameter (0018,1100) is not present.</description>
    </entry>
    <entry group="0018" element="9322" name="&gt;Reconstruction Pixel Spacing" type="1C">
      <description>Physical distance in the patient between the center of each reconstructed pixel, specified by a numeric pair - adjacent row spacing (delimiter) adjacent column spacing in mm. See 10.7.1.3 for further explanation of the value order.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9319" name="&gt;Reconstruction Angle" type="1C">
      <description>Angle (in degrees) over which the data from which the frame was reconstructed was collected, where 360 degrees signifies a complete revolution of the source around the gantry orbit. It is possible, in the case of over-scanning that the Reconstruction Angle is greater than 360 degrees.
Shall be 0 if Acquisition Type (0018,9302) is CONSTANT_ANGLE.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9320" name="&gt;Image Filter" type="1C">
      <description>A label describing the filter applied to the reconstructed image after the original reconstruction has been completed.
Note: When Frame Type (0008,9007) Value 1 of this frame is DERIVED and Frame Type (0008,9007) Value 4 is FILTERED the type of filtration is described in Derivation Image Macro.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL.</description>
    </entry>
  </macro>
  <macro table="C.8-124" name="CT Exposure Macro Attributes">
    <entry group="0018" element="9321" name="CT Exposure Sequence" type="1">
      <description>Contains the attributes defining exposure information. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9328" name="&gt;Exposure Time in ms" type="1C">
      <description>Duration of exposure for this frame in milliseconds. If Acquisition Type (0018,9302) equals SPIRAL the duration of exposure shall be weighted by the Spiral Pitch Factor (0018,9311).
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9330" name="&gt;X-Ray Tube Current in mA" type="1C">
      <description>Nominal X-Ray tube current in milliamperes.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9332" name="&gt;Exposure in mAs" type="1C">
      <description>The exposure expressed in milliampere seconds, for example calculated from exposure time and X-Ray tube current.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9323" name="&gt;Exposure Modulation Type" type="1C">
      <description>A label describing the type of exposure modulation used for the purpose of limiting the dose.
Defined Terms:
NONE
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9324" name="&gt;Estimated Dose Saving" type="2C">
      <description>A percent value of dose saving due to the use of Exposure Modulation Type (0018,9323). A negative percent value of dose savings reflects an increase of exposure.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Exposure Modulation Type (0018,9323) is not equal to NONE.
Otherwise may be present if Frame Type (0008,9007) Value 1 of this frame is DERIVED and Exposure Modulation Type (0018,9323) is not equal to NONE.</description>
    </entry>
    <entry group="0018" element="9345" name="&gt;CTDIvol" type="2C">
      <description>Computed Tomography Dose Index (CTDIvol), in mGy according to IEC 60601-2-44, Ed.2.1 (Clause 29.1.103.4), The Volume CTDIvol. It describes the average dose for this frame for the selected CT conditions of operation.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9346" name="&gt;CTDI Phantom Type Code Sequence" type="3">
      <description>The type of phantom used for CTDI measurement according to IEC 60601-2-44. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="DCID 4052"/>
  </macro>
  <macro table="C.8-125" name="CT X Ray Details Sequence Macro Attributes">
    <entry group="0018" element="9325" name="CT X-Ray Details Sequence" type="1">
      <description>Contains the attributes defining the x-ray information. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="0060" name="&gt;KVP" type="1C">
      <description>Peak kilo voltage output of the x-ray generator used.
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="1190" name="&gt;Focal Spot(s)" type="1C">
      <description>Used nominal size of the focal spot in mm. The attribute may only have one or two values, for devices with variable focal spot, small dimension followed by large dimension
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="1160" name="&gt;Filter Type" type="1C">
      <description>Type of filter(s) inserted into the X-Ray beam.
Defined Terms:
WEDGE
BUTTERFLY
MULTIPLE
FLAT
SHAPED
NONE
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="7050" name="&gt;Filter Material" type="1C">
      <description>The X-Ray absorbing material used in the filter. May be multi-valued.
Defined Terms:
MOLYBDENUM
ALUMINUM
COPPER
RHODIUM
NIOBIUM
EUROPIUM
LEAD
MIXED
Note: MIXED may be used to indicate a filter type of complex composition for which listing the individual materials would be excessive or undesirable; it is not intended to mean "unknown".
Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and the value of Filter Type (0018,1160) is other than NONE. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9351" name="&gt;Calcium Scoring Mass Factor Patient" type="3">
      <description>The calibration factor for the calcium mass score. These factors incorporate the effects of
See C.8.2.1.1.7.</description>
      <section ref="C.8.2.1.1.7" name="">The calibration factors for the Calcium Scoring Mass Factor Patient (0018,9351) and Calcium Scoring Mass Factor Device (0018,9352) attributes are defined by the International Consortium for Multi-Detector CT Evaluation of Coronary Calcium, see McCollough, C.H. “A multi-institutional, multi-manufacturer, international standard for the quantification of coronary artery calcium using cardiac CT”.
</section>
    </entry>
    <entry group="0018" element="9352" name="&gt;Calcium Scoring Mass Factor Device" type="3">
      <description>The calibration factors for the calcium mass score of the device. These factors incorporate the effects of
This a multi-value attribute, the first value specifies the mass factor for a small patient size, the second value for a medium patient size and the third value for a large patient size.
See C.8.2.1.1.7.</description>
      <section ref="C.8.2.1.1.7" name="">The calibration factors for the Calcium Scoring Mass Factor Patient (0018,9351) and Calcium Scoring Mass Factor Device (0018,9352) attributes are defined by the International Consortium for Multi-Detector CT Evaluation of Coronary Calcium, see McCollough, C.H. “A multi-institutional, multi-manufacturer, international standard for the quantification of coronary artery calcium using cardiac CT”.
</section>
    </entry>
  </macro>
  <macro table="C.8-126" name="CT Pixel Value Transformation Macro Attributes">
    <entry group="0028" element="9145" name="Pixel Value Transformation Sequence" type="1">
      <description>Contains the attributes involved in the transformation of stored pixel values. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0028" element="1052" name="&gt;Rescale Intercept" type="1">
      <description>The value b in relationship between stored values (SV) and the output units.
Output units = m*SV + b.</description>
    </entry>
    <entry group="0028" element="1053" name="&gt;Rescale Slope" type="1">
      <description>m in the equation specified by Rescale Intercept (0028,1052).</description>
    </entry>
    <entry group="0028" element="1054" name="&gt;Rescale Type" type="1">
      <description>Specifies the output units of Rescale Slope (0028,1053) and Rescale Intercept (0028,1052).
See C.11.1.1.2 for further explanation.
If Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and Frame Type (0008,9007) Value 3 is not LOCALIZER, the value shall be HU (Hounsfield Units).</description>
      <section ref="C.11.1.1.2" name="">Specifies the units of the output of the Modality LUT or rescale operation.
Defined Terms:
  OD = The number in the LUT represents thousands of optical density. That is, a value of 2140 represents an optical density of 2.140.
  HU = Hounsfield Units (CT)
  US = Unspecified
Other values are permitted, but are not defined by the DICOM Standard.
</section>
    </entry>
  </macro>
  <macro table="C.8-126b" name="CT Additional X Ray Source Macro Attributes">
    <entry group="0018" element="9360" name="CT Additional X-Ray Source Sequence" type="1">
      <description>Contains the attributes defining the data acquisition in a multiple X-Ray source system beyond the primary source. The primary X-Ray source is specified in the CT X-Ray Details Sequence.
One or more items may be present.</description>
    </entry>
    <entry group="0018" element="0060" name="&gt;kVP" type="1">
      <description>Peak kilo voltage output of the X-Ray generator used.</description>
    </entry>
    <entry group="0018" element="9330" name="&gt;X-Ray Tube Current in mA" type="1">
      <description>Nominal X-Ray tube current in milliamperes.</description>
    </entry>
    <entry group="0018" element="0090" name="&gt;Data Collection Diameter" type="1">
      <description>The diameter in mm of the region over which data were collected.</description>
    </entry>
    <entry group="0018" element="9190" name="&gt;Focal Spot(s)" type="1">
      <description>Used nominal size of the focal spot in mm.</description>
    </entry>
    <entry group="0018" element="9160" name="&gt;Filter Type(s)" type="1">
      <description>Type of filter(s) inserted into the X-Ray beam.</description>
    </entry>
    <entry group="0018" element="7050" name="&gt;Filter Material" type="1">
      <description>The X-Ray absorbing material used in the filter.</description>
    </entry>
  </macro>
  <macro table="C.8-131" name="Common CT/MR Image Description Macro Attributes">
    <entry group="0008" element="9205" name="Pixel Presentation" type="1">
      <description>Indication of the presence or absence of color information that may be used during rendering. See C.8.16.2.1.1 for a description and Enumerated Values.</description>
      <section ref="C.8.16.2.1.1" name="">Table C.8-132
PIXEL PRESENTATION ATTRIBUTE VALUES
<unrecognized-rows><term value="Enumerated Value Name" meaning="Enumerated Value Description"/><term value="COLOR" meaning="Image is best displayed in color using Supplemental Palette Color LUTs, but can be displayed in grayscale if current display does not support color. See section C.8.13.3.1.2.1."/><term value="MONOCHROME" meaning="Image is intended to be displayed in grayscale only. No Supplemental Palette Color LUTs are supplied."/><term value="MIXED" meaning="Used only as a value in Pixel Presentation (0008,9205) in the Enhanced MR Image Module or Enhanced CT Image Module if frames within the image SOP Instance contain different values for the Pixel Presentation attribute in the MR Image Frame Type Functional Group or CT Image Frame Type Functional Group."/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0008" element="9206" name="Volumetric Properties" type="1">
      <description>Indication if geometric manipulations are possible with frames in the SOP Instance. See C.8.16.2.1.2 for a description and Enumerated Values.</description>
      <section ref="C.8.16.2.1.2" name="">The value of the Volumetric Properties attribute (0008,9206) allows applications doing geometric manipulations (e.g., MAX_IP or MPR or planning) to determine if the image is an appropriate candidate for an operation without having to know all the details of the generating application.
Table C.8-133 specifies the Enumerated Values for the Volumetric Properties (0008,9206) attribute.
Table C.8-133
VOLUMETRIC PROPERTIES ATTRIBUTE VALUES
<unrecognized-rows><term value="Enumerated Value Name" meaning="Enumerated Value Description"/><term value="VOLUME" meaning="Image contains pixels that represent the volume specified for the image (Examples: Volume Based Calculation Technique (0008,9207) is NONE or MPR)."/><term value="SAMPLED" meaning="The specified frame or each frame within the image will not contain a representation of the average information in the slice direction because the frame was calculated by the non-linear re-sampling of a volume where each pixels of the resulting frame does not contain an average representation of the voxel represented by the frame's pixel."/><term value="DISTORTED" meaning="Image contains significantly distorted information from what is specified by the image volume attributes. For example this image should not be used in planning or for 3D volume. An example of this image type is a curved reformatted image (CURVED_MPR)."/><term value="MIXED" meaning="Used only as a value in the Volumetric Properties (0008,9206) attribute in the Enhanced MR Image Type Module or Enhanced CT Image Type Module if frames within the image SOP Instance contain different values for the Volumetric Properties (0008,9206) attributes in the MR Image Frame Type Functional Group or CT Frame Type Functional Group."/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0008" element="9207" name="Volume Based Calculation Technique" type="1">
      <description>Method used for volume calculations with frames in the SOP Instance. See C.8.16.2.1.3 for a description and Defined Terms.</description>
      <section ref="C.8.16.2.1.3" name="">The value of the Volume Based Calculation Technique attribute (0008,9207) shall be used to indicate the method used for calculating pixels based on geometry.
Shall have a value of NONE when Value 1 of Image Type (0008,0008) or Value 1 of Frame Type (0008,9007) is ORIGINAL.
Table C.8-134 specifies the Defined Terms for the Volume Based Calculation Technique (0008,9207) attribute.
Table C.8-134
VOLUME BASED CALCULATION TECHNIQUE ATTRIBUTE VALUES
<unrecognized-rows><term value="Defined Term Name" meaning="Defined Term Description"/><term value="MAX_IP" meaning="Maximum Intensity Projection"/><term value="MIN_IP" meaning="Minimum Intensity Projection"/><term value="VOLUME_RENDER" meaning="Volume Rendering Projection"/><term value="SURFACE_RENDER" meaning="Surface Rendering Projection"/><term value="MPR" meaning="Multi-Planar Reformat"/><term value="CURVED_MPR" meaning="Curved Multi-Planar Reformat"/><term value="NONE" meaning="Pixels not derived geometrically"/><term value="MIXED" meaning="Used only as a value in Volume Based Calculation Technique (0008,9207) attribute in the Enhanced MR Image Module or MR Spectroscopy Module if frames within the image SOP Instance contain different terms for the Volume Based Calculation Technique attribute in MR Frame Type Functional Group or MR Spectroscopy Frame Type Functional Group."/></unrecognized-rows>
         </section>
    </entry>
  </macro>
  <module ref="C.8.17.1" table="C.8.17.1-1" name="Ophthalmic Photography Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Source equipment that produced the Ophthalmic Photography Series. Enumerated Value: OP</description>
    </entry>
  </module>
  <module ref="C.8.17.2" table="C.8.17.2-1" name="Ophthalmic Photography Image Module Attributes">
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image identification characteristics.
See C.8.17.2.1.4 for specialization.</description>
      <section ref="C.8.17.2.1.4" name="">The Image Type attribute (0008,0008) (General Image Module, C.7.6.1) identifies important image characteristics in a multiple valued data element. For the Ophthalmic Photography Image IOD, Image Type is specified as a Type 1 attribute and further specialized as follows:
a.  Value 1 shall identify the Pixel Data Characteristics in accordance with Section C.7.6.1.1.2; Enumerated Values are: ORIGINAL and DERIVED;
</section>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description>A number that identifies this image.
</description>
    </entry>
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (planes) in this image. Enumerated values: 1 or 3.
See C.8.17.2.1.2 for further explanation.</description>
      <section ref="C.8.17.2.1.2" name="">Samples per Pixel (0028,0002) shall be 1 or 3.
Cameras producing 2-color images are required to use a value of 3 for Samples per Pixel (0028,0002) and a value of 2 for Samples per Pixel Used (0028,0003). For 2-color images with a RGB Photometric Interpretation, the R and G channel shall be used and the B channel shall have all values set to zero.
Note:   In the case of Photometric Interpretations typically used for compression such as YBR_FULL_422, the encoding will be as if the RGB values were transformed to YCbCr.

</section>
    </entry>
    <entry group="0028" element="0003" name="Samples per Pixel Used" type="1C">
      <description>The number of samples (planes) containing information. Enumerated value: 2.
Required if different from Samples per Pixel (0028,0002).
See section C.8.17.2.1.2</description>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data.
See section C.8.17.2.1.3</description>
    </entry>
    <entry group="0028" element="0103" name="Pixel Representation" type="1">
      <description>Data representation of the pixel samples. Enumerated value: 0</description>
    </entry>
    <entry group="0028" element="0006" name="Planar Configuration" type="1C">
      <description>Indicates whether the pixel data are sent color-by-plane or color-by-pixel. Required if Samples per Pixel (0028,0002) has a value greater than 1.
Enumerated value shall be 0 (color-by-pixel).</description>
    </entry>
    <entry group="0028" element="0030" name="Pixel Spacing" type="1C">
      <description>Nominal physical distance at the focal plane (in the retina) between the center of each pixel, specified by a numeric pair - adjacent row spacing (delimiter) adjacent column spacing in mm. See 10.7.1.3 for further explanation of the value order.
Note: These values are specified as nominal because the physical distance may vary across the field of the images and the lens correction is likely to be imperfect.
Required when Acquisition Device Type Code Sequence (0022,0015) contains an item with the value (SRT, R-1021A,"Fundus Camera"). May be present otherwise.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the image pixel data creation started.</description>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the image pixel data creation started.</description>
    </entry>
    <entry group="0008" element="002A" name="Acquisition DateTime" type="1C">
      <description>The date and time that the acquisition of data started.
Note: The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time Synchronized (0018,1800).
Required if Image Type (0008,0008) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0008" element="2112" name="Source Image Sequence" type="2C">
      <description>A Sequence that identifies the Images that were used to derive this Image. Required if Image Type Value 1 is DERIVED. Zero or more items may be present in the sequence.
See C.7.6.1.1.4 for further explanation.</description>
      <section ref="C.7.6.1.1.4" name="">If an Image is identified to be a Derived image (see C.7.6.1.1.2 Image Type), Source Image Sequence (0008,2112) is an optional list of Referenced SOP Class UID (0008,1150)/ Referenced SOP Instance UID (0008,1150) pairs that identify the source images used to create the Derived image. It may be used whether or not there is a description of the way the image was derived in Derivation Description (0008,2111) or Derivation Code Sequence (0008,9215).
Note:  Multiple Items may be present within Source Image Sequence (0008,2112), in which case either:
  a) those images were combined to make the derived image (e.g. multiple source images to make an MPR or MIP), or
  b) each of the items represents a step in the successive derivation of an image (e.g. when an image has had successive lossy compression steps applied to it),
  c) some combination of the above.
  The Purpose of Reference Code Sequence (0040,A170) and the Attributes within the referenced images themselves may be used to determine the history of the derivation, which is not otherwise explicitly specified.

</section>
    </entry>
    <include ref="&gt;Include Image SOP Instance Reference Macro, Table 10-3"/>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="1">
      <description>Describes the purpose for which the reference is made, that is what role the source image or frame(s) played in the derivation of this image. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 7202."/>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1">
      <description>Specifies whether an Image has undergone lossy compression. Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2112" name="Lossy Image Compression Ratio" type="1C">
      <description>Describes the approximate lossy compression ratio(s) that have been applied to this image. See C.7.6.1.1.5 for further explanation.
May be multivalued if successive lossy compression steps have been applied.
Notes: 1. For example, a compression ratio of 30:1 would be described in this Attribute with a single value of 30.
2. For historical reasons, the lossy compression ratio should also be described in Derivation Description (0008,2111)
Required if Lossy Image Compression (0028,2110) has a value of "01".</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2114" name="Lossy Image Compression Method" type="1C">
      <description>A label for the lossy compression method(s) that have been applied to this image.
See C.7.6.1.1.5 for further explanation.
May be multivalued if successive lossy compression steps have been applied; the value order shall correspond to the values of Lossy Image Compression Ratio (0028,2112).
Required if Lossy Image Compression (0028,2110) has a value of "01".
Note: For historical reasons, the lossy compression method should also be described in Derivation Description (0008,2111).</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="2050" element="0020" name="Presentation LUT Shape" type="1C">
      <description>Specifies an identity transformation for the Presentation LUT, such that the output of all grayscale transformations defined in the IOD containing this Module are defined to be P-Values.
Enumerated Values:
IDENTITY - output is in P-Values.
Required if Photometric Interpretation (0028,0004) is MONOCHROME2</description>
    </entry>
    <entry group="0050" element="0004" name="Calibration Image" type="3">
      <description>Indicates whether a reference object (phantom) of known size is present in the image and was used for calibration. Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="0028" element="0301" name="Burned In Annotation" type="1">
      <description>Indicates whether or not image contains sufficient burned in annotation to identify the patient and date the image was acquired.
Enumerated Value:
YES
NO</description>
    </entry>
  </module>
  <module ref="C.8.17.3" table="C.8.17.3-1" name="Ophthalmic PHOTOGRAPHIC PARAMETERS MODULE ATTRIBUTES">
    <!-- FIXME -->
  </module>
  <module ref="C.8.17.4" table="C.8.17.4-1" name="Ophthalmic Photography Acquisition Parameters Module Attributes">
    <entry group="0022" element="0005" name="Patient Eye Movement Commanded" type="2">
      <description>Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="0022" element="0006" name="Patient Eye Movement Command Code Sequence" type="1C">
      <description>Coded value for patient movement or orientation, which is the intent, and not necessarily the result, based on what the patient is capable of.
Required if the value of Patient Eye Movement Commanded (0022,0005) is YES.
A single item shall be present in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8.1" description="Baseline Context ID is 4201"/>
    <include ref="Include 'Ophthalmic Acquisition Parameters Macro' Table C.8.17.8-2"/>
  </module>
  <module ref="C.8.17.5" table="C.8.17.5-1" name="Ocular Region Imaged Module Attributes">
    <entry group="0020" element="0062" name="Image Laterality" type="1">
      <description>Laterality of object imaged (as described in Anatomic Region Sequence (0008,2218)) examined.
Enumerated Values:
R = right eye
L = left eye
B = both left and right eye
Shall be consistent with any laterality information contained in Primary Anatomic Structure Modifier Sequence (0008,2230), if present.
Note: Laterality (0020,0060) is a Series level Attribute and must be the same for all Images in the Series. Since most Ophthalmic Photographic Image studies contain images of both eyes, the series level attribute will rarely be present.</description>
    </entry>
    <entry group="0022" element="001D" name="Relative Image Position Code Sequence" type="3">
      <description>The position of this image on the retina (as defined by a specified nomenclature; the nomenclature is implicit in the code used). Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8.1" description="Baseline Context ID 4207"/>
    <include ref="Include 'General Anatomy Mandatory Macro' Table 10-5" description="Defined Context ID 4209 for Anatomic Region Sequence"/>
  </module>
  <module ref="C.8.17.6" table="C.8.17.6-1" name="Ophthalmic Tomography Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Type of equipment that originally acquired the data used to create the images in this Series.
Enumerated Values:
OPT
See section C.7.3.1.1.1 for further explanation.</description>
    </entry>
    <entry group="0020" element="0011" name="Series Number" type="1">
      <description>A number that identifies this Series.</description>
    </entry>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence" type="1C">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance to which the Series is related (e.g. a Modality or General-Purpose Performed Procedure Step SOP Instance). The Sequence shall have one Item.
Required if the Modality Performed Procedure Step SOP Class or General Purpose Performed Procedure Step SOP Class is supported.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.8.17.7" table="C.8.17.7-1" name="Ophthalmic Tomography Image Module Attributes">
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image identification characteristics.</description>
    </entry>
    <entry group="0028" element="0002" name="Samples Per Pixel" type="1">
      <description>Number of samples (planes) in this image. See C.7.6.3.1.1 for further explanation. Value shall be 1.</description>
      <section ref="C.7.6.3.1.1" name="">Samples per Pixel (0028,0002) is the number of separate planes in this image. One, three, and four image planes are defined. Other numbers of image planes are allowed, but their meaning is not defined by this Standard.
For monochrome (gray scale) and palette color images, the number of planes is 1. For RGB and other three vector color models, the value of this attribute is 3. For four vector color models, the value of this attribute is 4.
All image planes shall have the same number of Rows (0028,0010), Columns (0028,0011), Bits Allocated (0028,0100), Bits Stored (0028,0101), High Bit (0028,0102), Pixel Representation (0028,0103), and Pixel Aspect Ratio (0028,0034).
The data in each pixel may be represented as a “Composite Pixel Code”. If Samples Per Pixel is one, the Composite Pixel Code is just the “n” bit pixel sample, where “n” = Bits Allocated. If Samples Per Pixel is greater than one, Composite Pixel Code is a “k” bit concatenation of samples, where “k” = Bits Allocated multiplied by Samples Per Pixel, and with the sample representing the vector color designated first in the Photometric Interpretation name comprising the most significant bits of the Composite Pixel Code, followed in order by the samples representing the next vector colors, with the sample representing the vector color designated last in the Photometric Interpretation name comprising the least significant bits of the Composite Pixel Code. For example, for Photometric Interpretation = “RGB”, the most significant “Bits Allocated” bits contain the Red sample, the next “Bits Allocated” bits contain the Green sample, and the least significant “Bits Allocated” bits contain the Blue sample.
</section>
    </entry>
    <entry group="0008" element="002A" name="Acquisition DateTime" type="1">
      <description>The date and time that the acquisition of data started.
Note: The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800) .</description>
    </entry>
    <entry group="0018" element="9073" name="Acquisition Duration" type="1C">
      <description>The scan time in seconds used to create all frames of an Ophthalmic Tomography image.
Required if Image Type (0008,0008) Value 1 is ORIGINAL. May be present otherwise.</description>
    </entry>
    <entry group="0020" element="0012" name="Acquisition Number" type="1">
      <description>A number identifying the single continuous gathering of data over a period of time which resulted in this image.</description>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data.
Enumerated Value shall be: MONOCHROME2</description>
    </entry>
    <entry group="0028" element="0103" name="Pixel Representation" type="1">
      <description>Data representation of pixel samples. Enumerated Value shall be 0.</description>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated.
Bits Allocated (0028,0100) shall be 8 or 16</description>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored.
Bits Stored (0028,0101) shall be 8, 12 or 16</description>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data. Each sample shall have the same high bit.
High Bit (0028,0102) shall be one less than Bits Stored</description>
    </entry>
    <entry group="2050" element="0020" name="Presentation LUT Shape" type="1">
      <description>Specifies an identity transformation for the Presentation LUT, such that the output of all grayscale transformations defined in the IOD containing this Module are defined to be P-Values.
Enumerated Values:
IDENTITY - output is in P-Values.</description>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1">
      <description>Specifies whether an Image has undergone lossy compression (at a point in its lifetime).
Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
Once this tag has been set to 01 it shall not be reset.
If this tag is empty, no information is explicitly available.
See C.7.6.1.1.5</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2112" name="Lossy Image Compression Ratio" type="1C">
      <description>Describes the approximate lossy compression ratio(s) that have been applied to this image. Required when compression has been applied.
See C.7.6.1.1.5 for further explanation.
May be multivalued if successive lossy compression steps have been applied.
Notes: 1. For example, a compression ratio of 30:1 would be described in this Attribute with a single value of 30.
2. For historical reasons, the lossy compression ratio should also be described in Derivation Description (0008,2111).</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2144" name="Lossy Image Compression Method" type="1C">
      <description>A label for the lossy compression method(s) that have been applied to this image.
See C.7.6.1.1.5 for further explanation.
May be multi-valued if successive lossy compression steps have been applied; the value order shall correspond to the values of Lossy Image Compression Ratio (0028,2112).
Required if Lossy Image Compression (0028,2110) has a value of "01".
Note: For historical reasons, the lossy compression method should also be described in Derivation Description (0008,2111).</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="0301" name="Burned In Annotation" type="1">
      <description>Indicates whether or not image contains sufficient burned in annotation to identify the patient and date the image was acquired.
Enumerated Value:
NO</description>
    </entry>
    <entry group="0020" element="9228" name="Concatenation Frame Offset Number" type="1">
      <description>Offset of the first frame in a multi-frame image of a concatenation. Value shall be 0.</description>
    </entry>
    <entry group="0020" element="9162" name="In-concatenation Number" type="1">
      <description>Identifier for one SOP Instance belonging to a concatenation. Value shall be 1.</description>
    </entry>
    <entry group="0020" element="9163" name="In-concatenation Total Number" type="1">
      <description>The number of SOP Instances sharing the same Concatenation UID (0020,9161). Value Shall be 1.</description>
    </entry>
  </module>
  <module ref="C.8.17.8" table="C.8.17.8-1" name="Ophthalmic Tomography Acquisition Parameters Module Attributes">
    <entry group="0022" element="0030" name="Axial Length of the Eye" type="2">
      <description>Axial length of the eye in mm.</description>
    </entry>
    <entry group="0022" element="000C" name="Horizontal Field of View" type="2">
      <description>The horizontal field of view in degrees</description>
    </entry>
    <include ref="Include 'Ophthalmic Acquisition Parameters Macro' Table C.8.17.8-2"/>
  </module>
  <macro table="C.8.17.8-2" name="Ophthalmic Acquisition Parameters Macro">
    <entry group="0022" element="001B" name="Refractive State Sequence" type="2">
      <description>The refractive state of the imaged eye at
the time of acquisition. Zero or one Item
shall be present. Zero length means the refractive state was not measured.</description>
    </entry>
    <entry group="0022" element="0007" name="&gt; Spherical Lens Power" type="1">
      <description>Sphere value in diopters</description>
    </entry>
    <entry group="0022" element="0008" name="&gt; Cylinder Lens Power" type="1">
      <description>Cylinder value in diopters</description>
    </entry>
    <entry group="0022" element="0009" name="&gt; Cylinder Axis" type="1">
      <description>Axis value in degrees</description>
    </entry>
    <entry group="0022" element="000A" name="Emmetropic Magnification" type="2">
      <description>Emmetropic magnification value (dimensionless). Zero length means the emmetropic magnification was not measured.</description>
    </entry>
    <entry group="0022" element="000B" name="Intra Ocular Pressure" type="2">
      <description>Value of intraocular pressure in mmHg.
Zero length means the pressure was not measured</description>
    </entry>
    <entry group="0022" element="000D" name="Pupil Dilated" type="2">
      <description>Enumerated Values:
YES
NO
If this tag is empty, no information is available.</description>
    </entry>
    <entry group="0022" element="0058" name="Mydriatic Agent Sequence" type="2C">
      <description>Information about the agent administered. Required if the value of Pupil Dilated (0022,000D) is YES. Zero or more items may be present.
Note: An empty sequence indicates that an agent was used for dilation, but the name was not entered.</description>
    </entry>
    <entry group="0022" element="001C" name="&gt;Mydriatic Agent Code Sequence" type="1">
      <description>The actual agent administered to dilate the pupil. One item shall be present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 4208."/>
    <entry group="0022" element="004E" name="&gt;Mydriatic Agent Concentration" type="3">
      <description>The concentration of the agent.</description>
    </entry>
    <entry group="0022" element="0042" name="&gt;Mydriatic Agent Concentration Units Sequence" type="1C">
      <description>Units of measure for the Mydriatic Agent Concentration. Required if Mydriatic Agent Concentration (0022,004E) is present. One item shall be present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Defined Context ID is 3082"/>
    <entry group="0022" element="000E" name="Degree of Dilation" type="2C">
      <description>The degree of the dilation in mm.
Required if the value of Pupil Dilated (0022,000D) is YES.</description>
    </entry>
  </macro>
  <module ref="C.8.17.9" table="C.8.17.9-1" name="Ophthalmic Tomography Parameters Module Attributes">
    <entry group="0022" element="0015" name="Acquisition Device Type Code Sequence" type="1">
      <description>Describes the type of acquisition device. A single item shall be present in the sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 4210"/>
    <entry group="0022" element="0017" name="Light Path Filter Type Stack Code Sequence" type="2">
      <description>Filters used in the light source path. Zero or more items may be present in the sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 4204"/>
    <entry group="0022" element="0001" name="&gt;Light Path Filter Pass-Through Wavelength" type="3">
      <description>Nominal pass-through wavelength of light path filter in nm</description>
    </entry>
    <entry group="0022" element="0002" name="&gt;Light Path Filter Pass Band" type="3">
      <description>Pass band of light path filter in nm. This Attribute has two Values. The first is the shorter and the second the longer wavelength relative to the peak. The values are for the - 3dB nominal (1/2 of peak) pass through intensity.
One of the two Values may be zero length, in which case it is a cutoff filter.</description>
    </entry>
    <entry group="0018" element="7004" name="Detector Type" type="1">
      <description>Type of detector used for creating this image. Defined terms:
CCD = Charge Coupled Device
CMOS = Complementary Metal Oxide Semiconductor
PHOTO = Photodetector
INT = Interferometer</description>
    </entry>
    <entry group="0022" element="0055" name="Illumination Wave Length" type="1C">
      <description>Wavelength of the illuminator in nm. Required if Acquisition Device Type Code Sequence (0022,0015) contains an item with the value (A-00FBE, SRT, "Optical Coherence Tomography Scanner"). May be present otherwise.</description>
    </entry>
    <entry group="0022" element="0056" name="Illumination Power" type="1C">
      <description>Power of the illuminator in microwatts at corneal plane. Required if Acquisition Device Type Code Sequence (0022,0015) contains an item with the value (SRT, A-00FBE,"Optical Coherence Tomography Scanner"). May be present otherwise.</description>
    </entry>
    <entry group="0022" element="0057" name="Illumination Bandwidth" type="1C">
      <description>Bandwidth of the illuminator in nm. Required if Acquisition Device Type Code Sequence (0022,0015) contains an item with the value (A-00FBE, SRT, "Optical Coherence Tomography Scanner"). May be present otherwise.</description>
    </entry>
    <entry group="0022" element="0035" name="Depth Spatial Resolution" type="1C">
      <description>The inherent limiting resolution in microns for depth of the acquisition equipment for high contrast objects for the data gathering and reconstruction technique chosen. If variable, the value at the center of the scanning volume. Required if Acquisition Device Type Code Sequence (0022,0015) contains an item with the value (A-00FBE, SRT, "Optical Coherence Tomography Scanner"). May be present otherwise.</description>
    </entry>
    <entry group="0022" element="0036" name="Maximum Depth Distortion" type="1C">
      <description>Maximum distortion in depth direction in % of Depth Spatial Resolution. Required if Acquisition Device Type Code Sequence (0022,0015) contains an item with the value (SRT, A-00FBE,"Optical Coherence Tomography Scanner"). May be present otherwise.</description>
    </entry>
    <entry group="0022" element="0037" name="Along-scan Spatial Resolution" type="1C">
      <description>The inherent limiting resolution in microns of the acquisition equipment in the direction of a row. Required if Acquisition Device Type Code Sequence (0022,0015) contains an item with the value (A-00FBE, SRT, "Optical Coherence Tomography Scanner"). May be present otherwise.</description>
    </entry>
    <entry group="0022" element="0038" name="Maximum Along-scan Distortion" type="1C">
      <description>Maximum distortion in along-scan direction in % of Along-scan Spatial Resolution. Required if Acquisition Device Type Code Sequence (0022,0015) contains an item with the value (A-00FBE, SRT, "Optical Coherence Tomography Scanner"). May be present otherwise.</description>
    </entry>
    <entry group="0022" element="0048" name="Across-scan Spatial Resolution" type="1C">
      <description>The inherent limiting resolution in microns of the acquisition equipment perpendicular to the slice. Required if Acquisition Device Type Code Sequence (0022,0015) contains an item with the value (A-00FBE, SRT, "Optical Coherence Tomography Scanner"). May be present otherwise.</description>
    </entry>
    <entry group="0022" element="0049" name="Maximum Across-scan Distortion" type="1C">
      <description>Maximum distortion in across-scan direction in % of cross-scan Spatial Resolution. Required if Acquisition Device Type Code Sequence (0022,0015) contains an item with the value (A-00FBE, SRT, "Optical Coherence Tomography Scanner"). May be present otherwise.</description>
    </entry>
  </module>
  <macro table="C.8.17.10-1" name="Ophthalmic Frame Location Macro Attributes">
    <entry group="0022" element="0031" name="Ophthalmic Frame Location Sequence" type="1">
      <description>Specifies the column locations for this frame in terms of locations on a referenced image. One or more items shall be present.</description>
    </entry>
    <include ref="&gt;Include 'Image SOP Instance Reference Macro' Table 10-3" description="Defined Term for Purpose of Reference is (121311, DCM, ”Localizer”)"/>
    <entry group="0022" element="0032" name="&gt;Reference Coordinates" type="1">
      <description>Image coordinates for the points on the referenced image that correspond to the points on this frame. See section C.8.17.10.1.1.</description>
    </entry>
    <entry group="0022" element="0041" name="&gt;Depth of Transverse Image" type="2C">
      <description>Relative position in microns signifying the location of a Transverse image in the z-axis. Required if Ophthalmic Image Orientation (0022,0039) is TRANSVERSE.</description>
    </entry>
    <entry group="0022" element="0039" name="&gt;Ophthalmic Image Orientation" type="1">
      <description>Enumerated Values:
LINEAR
NONLINEAR
TRANSVERSE</description>
    </entry>
  </macro>
  <module ref="C.8.18.1" table="C.8.18.1-1" name="Stereometric Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Source equipment that produced the Stereometric Series. Enumerated Value: SMR</description>
    </entry>
  </module>
  <module ref="C.8.18.2" table="C.8.18.2-1" name="Stereometric Relationship Module Attributes">
    <entry group="0022" element="0020" name="Stereo Pairs Sequence" type="1">
      <description>Sequence of items identifying pairs of images. There shall be one or more items in this sequence.</description>
    </entry>
    <entry group="0022" element="0010" name="&gt;Stereo Baseline Angle" type="3">
      <description>Stereo separation angle in degrees</description>
    </entry>
    <entry group="0022" element="0011" name="&gt;Stereo Baseline Displacement" type="3">
      <description>Horizontal displacement of instrument between left and right image in mm</description>
    </entry>
    <entry group="0022" element="0012" name="&gt;Stereo Horizontal Pixel Offset" type="3">
      <description>Horizontal displacement of right image relative to left image in pixels for optimal display. Offset of right image to right means positive value.</description>
    </entry>
    <entry group="0022" element="0013" name="&gt;Stereo Vertical Pixel Offset" type="3">
      <description>Vertical displacement of right image relative to left image in pixels for optimal display. Offset of right image downwards means positive value.</description>
    </entry>
    <entry group="0022" element="0014" name="&gt;Stereo Rotation" type="3">
      <description>Rotation of right image relative to left image in degrees for optimal display. The rotation of the right image against the left image counterclockwise is positive, rotation around the center is assumed.</description>
    </entry>
    <entry group="0022" element="0021" name="&gt;Left Image Sequence" type="1">
      <description>Left Image of the Pair. Only one Item shall be present in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Image SOP Instance Reference Macro, Table 10-3" description="The Referenced SOP Instance UID (0008,1155) shall not be the same as the Referenced SOP Instance UID (0008,1155) of the Right Image Sequence (0022,0022)."/>
    <entry group="0022" element="0022" name="&gt;Right Image Sequence" type="1">
      <description>Right Image of the Pair. Only one Item shall be present in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Image SOP Instance Reference Macro, Table 10-3" description="The Referenced SOP Instance UID (0008,1155) shall not be the same as the Referenced SOP Instance UID (0008,1155) of the Left Image Sequence (0022,0021)."/>
  </module>
  <module ref="C.8.19.1" table="C.8.19.1-1" name="XA/XRF Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Type of equipment that originally acquired the data used to create the images in this Series.
Enumerated Values:
XA
RF
See section C.7.3.1.1.1 for further explanation.</description>
    </entry>
    <entry group="0020" element="0011" name="Series Number" type="1">
      <description>A number that identifies this Series.</description>
    </entry>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence" type="1C">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance to which the Series is related (e.g. a Modality or General-Purpose Performed Procedure Step SOP Instance). Only a single Item is permitted in this sequence.
Required if the Modality Performed Procedure Step SOP Class, General Purpose Performed Procedure Step SOP Class is supported.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.8.19.2" table="C.8.19.2-1" name="Enhanced XA/XRF Image Module Attributes">
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image identification characteristics.
See C.8.19.2.1.1 for specialization.</description>
      <section ref="C.8.19.2.1.1" name="">The Image Type attribute identifies important image characteristics in a multiple valued data element. For X-Ray, Image Type is specialized as follows:
a.  Value 1 shall identify the Pixel Data Characteristics in accordance with Section C.7.6.1.1.2; Enumerated Values are: ORIGINAL and DERIVED;
b.  Value 2 shall identify the Patient Examination Characteristics in accordance with Section C.7.6.1.1.2; Enumerated Values are: PRIMARY and SECONDARY.

Note:  X-Ray images generally use PRIMARY value for images captured from patient exposure.

c.  Value 3 shall identify the image set in terms of the imaging planes. Enumerated Values are:

<enumerated-values><term value="SINGLE PLANE" meaning="Image is a single plane acquisition;"/><term value="BIPLANE A" meaning="Image is the first plane (e.g., Frontal) of a Bi-plane acquisition;"/><term value="BIPLANE B" meaning="Image is the second plane (e.g., Lateral) of a Bi-plane acquisition"/><term value="UNDEFINED" meaning="Image is created by using data from one or two planes (e.g., reconstructed projection). May only be used when Image Type Value 1 equals DERIVED."/></enumerated-values>
d.  Other Values are implementation specific (optional).

</section>
    </entry>
    <entry group="0018" element="9457" name="Plane Identification" type="1C">
      <description>Identification of the plane used to acquire this image.
Defined Terms:
MONOPLANE
PLANE A
PLANE B
Notes: 1. MONOPLANE may only be used for a single plane system
2. PLANE A and PLANE B must be used for two plane systems, independent if the acquisition is single plane or biplane.
3. The value has to be in accordance with Image Type (0008,0008) value 3. If this value is SINGLE PLANE all three Defined Term are applicable.
Required if Image Type (0008,0008) Value 3 is not equal to UNDEFINED.</description>
    </entry>
    <entry group="0020" element="0012" name="Acquisition Number" type="3">
      <description>A number identifying the single continuous gathering of data over a period of time that resulted in this image.</description>
    </entry>
    <entry group="0008" element="002A" name="Acquisition DateTime" type="1">
      <description>The date and time that the acquisition of data that resulted in this image started.
Note: The synchronization of this time with an external clock is specified in the Synchronization Module in Acquisition Time Synchronized (0018,1800).</description>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated. Enumerated Values: 8 and 16.</description>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored. Enumerated Values: 8 to 16. See C.8.19.2.1.2 for specialization.</description>
      <section ref="C.8.19.2.1.2" name="">Table C.8.X2-2 specifies the allowed combinations of Bits Allocated (0028,0100) and Bits Stored (0028,0101).
Table C.8.19.2-2
ALLOWED COMBINATIONS OF ATTRIBUTE VALUES
 FOR BITS ALLOCATED AND BITS STORED
<unrecognized-rows><term value="Bits Allocated" meaning="Bits Stored"/><term value="8" meaning="8"/><term value="16" meaning="9 to16"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data. Each sample shall have the same high bit. Shall be one less than the value in Bits Stored (0028,0101).</description>
    </entry>
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (color planes) in this image shall have a value of 1.</description>
    </entry>
    <entry group="0028" element="0103" name="Pixel Representation" type="1">
      <description>Data representation of the pixel samples.
Shall have the value:
0000H = Unsigned Integer.</description>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the pixel data.
Enumerated Values:
MONOCHROME1
MONOCHROME2</description>
    </entry>
    <entry group="0018" element="9423" name="Acquisition Protocol Name" type="3">
      <description>User defined name of the protocol used to acquire this image.</description>
    </entry>
    <entry group="0018" element="9424" name="Acquisition Protocol Description" type="3">
      <description>User defined description of the protocol used to acquire this image.</description>
    </entry>
    <entry group="0018" element="0022" name="Scan Options" type="3">
      <description>Identifies any acquisition technique that was used during the acquisition of the image.
Defined Terms:
TOMO = Tomography
CHASE = Bolus Chasing
STEP = Stepping
ROTA = Rotation</description>
    </entry>
    <entry group="0018" element="9004" name="Content Qualification" type="1">
      <description>Content Qualification Indicator
Enumerated Values:
PRODUCT
RESEARCH
SERVICE
See C.8.13.2.1.1 for further explanation.</description>
      <section ref="C.8.13.2.1.1" name="">Content Qualification (0018,9004) shall have the value PRODUCT if the content (image or Spectroscopy data) was produced with approved hardware and software. It shall have the value RESEARCH or SERVICE if there is any doubt as to whether the content was produced with approved hardware and software.
If data with Content Qualification (0018,9004) of RESEARCH or SERVICE is used to derive other content then it is expected that this derived content will also have Content Qualification (0018,9004) set to RESEARCH or SERVICE.
The intent of this element is to allow annotation of an advisory message that indicates that this content may not be suitable for clinical interpretation.
</section>
    </entry>
    <entry group="0054" element="0410" name="Patient Orientation Code Sequence" type="1C">
      <description>Sequence that describes the orientation of the patient with respect to gravity.
See C.8.11.5.1.2 for further explanation.
Only a single Item shall be permitted in this Sequence.
Required if Positioner Type (0018,1508) equals CARM and C-arm Positioner Tabletop Relationship (0018,9474) equals YES. May be present otherwise.</description>
      <section ref="C.8.11.5.1.2" name="">This Attribute is not related to Patient Orientation (0020,0020) and conveys a different concept entirely.
</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID 19"/>
    <entry group="0054" element="0412" name="&gt; Patient Orientation Modifier Code Sequence" type="1C">
      <description>Patient Orientation Modifier.
Required if needed to fully specify the orientation of the patient with respect to gravity.
Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID 20"/>
    <entry group="0054" element="0414" name="Patient Gantry Relationship Code Sequence" type="2C">
      <description>Sequence that describes the orientation of the patient with respect to the head of the table. See Section C.8.4.6.1.3 for further explanation.
Zero or one item shall be present in the sequence.
Required if Positioner Type (0018,1508) equals CARM and C-arm Positioner Tabletop Relationship (0018,9474) equals YES. May be present otherwise.</description>
      <section ref="C.8.4.6.1.3" name="">Patient Gantry Relationship Code Sequence (0054,0414) is used to describe the patient direction within the gantry, such as head-first or feet-first. When imaging the extremities, these directions are related to normal anatomic position.
Example: In normal anatomic position, the fingers point towards the feet.
</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID 21"/>
    <entry group="0010" element="9431" name="Examined Body Thickness" type="3">
      <description>Body thickness in mm at examination location perpendicular to the table top for this series.
Notes: 1. This is intended for estimation of the thickness of the patient at the tabletop, not for precise calculation of the size of the object in the X-Ray beam (see Calculated Anatomy Thickness (0018,9452) attribute).
2. For example, used to estimate the value range of the Distance Object to Table Top (0018,9403) attribute.</description>
    </entry>
    <entry group="0028" element="0301" name="Burned In Annotation" type="1">
      <description>Indicates whether or not the image contains sufficient burned in annotation to identify the patient and date the image was acquired.
Enumerated Values:
NO</description>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1">
      <description>Specifies whether an Image has undergone lossy compression. Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5 for further explanation.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2112" name="Lossy Image Compression Ratio" type="1C">
      <description>See C.7.6.1.1.5 for further explanation.
Required if Lossy Image Compression (0028,2110) equals 01.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2114" name="Lossy Image Compression Method" type="1C">
      <description>A label for the lossy compression method(s) that have been applied to this image.
See C.7.6.1.1.5 for further explanation.
May be multi valued if successive lossy compression steps have been applied; the value order shall correspond to the values of Lossy Image Compression Ratio (0028,2112).
Note: For historical reasons, the lossy compression method may also be described in Derivation Description (0008,2111).
Required if Lossy Image Compression (0028,2110) equals 01.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0008" element="9410" name="Referenced Other Plane Sequence" type="1C">
      <description>A sequence that identifies the SOP Class/Instance pairs of the corresponding plane for a Biplane acquisition device.
Only a single Item shall be permitted in this Sequence.
Required if Image Type (0008,0008) Value 3 is BIPLANE A or BIPLANE B.</description>
    </entry>
    <include ref="&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0008" element="9092" name="Referenced Image Evidence Sequence" type="1C">
      <description>Full set of Composite SOP Instances referred to inside the Referenced Image Sequences of this SOP Instance. See C.8.13.2.1.2 for further explanation.
One or more Items may be permitted in this sequence.
Required if the Referenced Image Sequence (0008,1140) is present.</description>
      <section ref="C.8.13.2.1.2" name="">The intent of the Referenced Image Evidence Sequence (0008,9092) and Source Image Evidence Sequence (0008,9154) is to provide a list of all unique SOP Instances listed in the Referenced Image Sequence (0008,1140) and Source Image Sequence (0008,2112) attributes respectively.
</section>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0008" element="9154" name="Source Image Evidence Sequence" type="1C">
      <description>Full set of Composite SOP Instances referred to inside the Source Image Sequences of this SOP Instance. See C.8.13.2.1.2 for further explanation.
One or more Items may be permitted in this sequence.
Required if the Source Image Sequence (0008,2112) is present.</description>
      <section ref="C.8.13.2.1.2" name="">The intent of the Referenced Image Evidence Sequence (0008,9092) and Source Image Evidence Sequence (0008,9154) is to provide a list of all unique SOP Instances listed in the Referenced Image Sequence (0008,1140) and Source Image Sequence (0008,2112) attributes respectively.
</section>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0008" element="114A" name="Referenced Instance Sequence" type="3">
      <description>A sequence which provides reference to a set of non-image SOP Class/Instance pairs significantly related to this Image, including waveforms that may or may not be temporally synchronized with this image.
One or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="1">
      <description>Code describing the purpose of the reference to the SOP Instances.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is CID 7004 for referenced waveforms."/>
    <entry group="0020" element="4000" name="Image Comments" type="3">
      <description>User-defined comments about the image.</description>
    </entry>
    <entry group="0028" element="0300" name="Quality Control Image" type="3">
      <description>Indicates whether or not this image is a quality control or phantom image.
Enumerated Values:
YES
NO
If this Attribute is absent, then the image may or may not be a quality control or phantom image.</description>
    </entry>
    <entry group="0088" element="0200" name="Icon Image Sequence" type="3">
      <description>This icon image is representative of the Image. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt; Include 'Image Pixel Macro' Table C.7-11b" description="See C.7.6.1.1.6 for further explanation."/>
    <entry group="2050" element="0020" name="Presentation LUT Shape" type="1">
      <description>Specifies a predefined identity transformation for the Presentation LUT such that the output of all grayscale transformations, if any, are defined to be in P-Values.
Enumerated Values:
IDENTITY - output is in P-Values - shall be used if Photometric Interpretation (0028,0004) is MONOCHROME2
INVERSE - output after inversion is in P-Values - shall be used if Photometric Interpretation (0028,0004) is MONOCHROME1.</description>
    </entry>
  </module>
  <module ref="C.8.19.3" table="C.8.19.3-1" name="XA/XRF Acquisition Module Attributes">
    <entry group="0018" element="0060" name="KVP" type="1">
      <description>Average of the peak kilo voltage outputs of the X-Ray generator used for all frames.</description>
    </entry>
    <entry group="0018" element="1155" name="Radiation Setting" type="1">
      <description>Identify the general level of X-Ray dose exposure. Enumerated values are:
SC = low dose exposure generally corresponding to fluoroscopic settings (e.g. preparation for diagnostic quality image acquisition);
GR = high dose for diagnostic quality image acquisition (also called digital spot or cine);</description>
    </entry>
    <entry group="0018" element="9330" name="X-Ray Tube Current in mA" type="1C">
      <description>Average of the nominal X-Ray tube currents in milliamperes for all frames.
Required if Exposure in mAs (0018,9332) is not present. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="9328" name="Exposure Time in ms" type="1C">
      <description>Duration of X-Ray exposure in milliseconds. See C.8.7.2.1.1.
Required if Exposure in mAs (0018,9332) is not present. May be present otherwise.</description>
      <section ref="C.8.7.2.1.1" name="">Exposure time is the cumulative time the patient received X-Ray exposure during this image (Multi-frame image acquisition). Calculation is pulse width * number of frames.
</section>
    </entry>
    <entry group="0018" element="9332" name="Exposure in mAs" type="1C">
      <description>The exposure expressed in milliampereseconds, for example calculated from Exposure Time and X-Ray Tube Current.
Required if either Exposure Time in ms (0018,9328) or X-Ray Tube Current in mA (0018,9330) are not present. May be present otherwise.</description>
    </entry>
    <entry group="0018" element="1154" name="Average Pulse Width" type="1">
      <description>Average width of X-Ray pulse in msec.</description>
    </entry>
    <entry group="0018" element="9073" name="Acquisition Duration" type="1">
      <description>The time in seconds needed for the complete acquisition.
See C.7.6.16.2.2.1 for further explanation</description>
      <section ref="C.7.6.16.2.2.1" name="">Figure C.7.6.16-2 shows the relationships among the various timing parameters used.
</section>
    </entry>
    <entry group="0018" element="115A" name="Radiation Mode" type="1">
      <description>Specifies X-Ray radiation mode. Defined Terms:
CONTINUOUS
PULSED</description>
    </entry>
    <entry group="0018" element="1190" name="Focal Spot" type="3">
      <description>Nominal focal spot size in mm used to acquire this image.</description>
    </entry>
    <entry group="0018" element="1191" name="Anode Target Material" type="3">
      <description>The primary material in the anode of the X-Ray source.
Defined Terms:
TUNGSTEN
MOLYBDENUM
RHODIUM</description>
    </entry>
    <entry group="0018" element="1156" name="Rectification Type" type="3">
      <description>Type of rectification used in the X-Ray generator.
Defined Terms:
SINGLE PHASE
THREE PHASE
CONST POTENTIAL</description>
    </entry>
    <entry group="0018" element="9420" name="X-Ray Receptor Type" type="1">
      <description>Identifies with type of X-Ray receptor is used.
Enumerated Values:
IMG_INTENSIFIER
DIGITAL_DETECTOR</description>
    </entry>
    <entry group="0018" element="1164" name="Imager Pixel Spacing" type="1">
      <description>Physical distance measured at the receptor plane of the detector between the centers of each pixel specified by a numeric pair - row spacing value (delimiter) column spacing value in mm. See 10.7.1.3 for further explanation of the value order.
Note: These values are the actual pixel spacing distances of the stored pixel values of an image.</description>
    </entry>
    <entry group="0018" element="9426" name="Distance Receptor Plane to Detector Housing" type="2">
      <description>Distance in mm between the receptor plane and the detector housing. The direction of the distance is positive from receptor plane to X-Ray source.
Note: 1. A negative value is allowed in the case of an image intensifier the receptor plane can be a virtual plane located outside the detector housing depending the magnification factor of the intensifier. A negative value is not applicable for the digital detector.
2. Used to calculate the pixel size of the plane in the patient when markers are used, and they are placed on the detector housing.</description>
    </entry>
    <entry group="0018" element="1508" name="Positioner Type" type="1">
      <description>Defined Terms:
CARM
COLUMN
Notes: 1. The term CARM can apply to any positioner with 2 degrees of freedom of rotation of the X-Ray beam about the Imaging Subject.
2. The term COLUMN can apply to any positioner with 1 degree of freedom of rotation of the X-Ray beam about the Imaging Subject.</description>
    </entry>
    <entry group="0018" element="9474" name="C-arm Positioner Tabletop Relationship" type="1C">
      <description>Describes for C-arm positioner type systems if positioner and tabletop has the same geometrical reference system.
Enumerated Values:
YES
NO
Note: The value NO is intended for mobile systems where there is no table fixed to the system
Required if Positioner Type (0018,1508) equals CARM.</description>
    </entry>
    <entry group="0018" element="9473" name="Acquired Image Area Dose Product" type="2">
      <description>X-Ray dose, measured in dGy*cm*cm, to which the patient was exposed for the acquisition of this image only.
Notes: 1. The sum of the Image Area Dose Product of all images of a Series or a Study may not result in the actual area dose product to which the patient was exposed.
2. This may be an estimated value based on assumptions about the patient's body size and habitus.</description>
    </entry>
  </module>
  <module ref="C.8.19.4" table="C.8.19.4-1" name="X Ray Image Intensifier Module Attributes">
    <entry group="0018" element="1162" name="Intensifier Size" type="1">
      <description>Physical diameter of the maximum active area X-Ray intensifier in mm.
Note: This attribute does not specify the field of view. The attribute Field of View Dimension(s) in Float (0018,9461) is intended for this value.</description>
    </entry>
    <entry group="0018" element="9427" name="Intensifier Active Shape" type="1">
      <description>Shape of the active area used for acquiring this image.
Enumerated Value:
RECTANGLE
ROUND
HEXAGONAL
Note: This may be different from the Field of View Shape (0018,1147), and should not be assumed to describe the stored image.</description>
    </entry>
    <entry group="0018" element="9428" name="Intensifier Active Dimension(s)" type="1">
      <description>Dimensions in mm of the active area used for acquiring this image.
If Intensifier Active Shape (0018,9427) is:
RECTANGLE: row dimension followed by column.
ROUND: diameter.
HEXAGONAL: diameter of the circle circumscribing the hexagon.
Note: This may be different from the Field of View Dimension(s) in Float (0018,9461), and should not be assumed to describe the stored image.</description>
    </entry>
  </module>
  <module ref="C.8.19.5" table="C.8.19.5-1" name="X Ray Detector Module Attributes">
    <include ref="Include 'Digital X-Ray Detector Macro' Table C.8-71b"/>
    <entry group="0018" element="9429" name="Physical Detector Size" type="1">
      <description>Dimensions of the physical detector measured in mm as a row size followed by a column size.</description>
    </entry>
    <entry group="0018" element="9430" name="Position of Isocenter Projection" type="1C">
      <description>Position of the Isocenter measured in physical detector elements as a row offset followed by a column offset from the TLHC of a rectangle circumscribing the physical detector area.
Required if Isocenter Reference System Sequence (0018,9462) is present.</description>
    </entry>
  </module>
  <macro table="C.8.19.6-1" name="XA/XRF Frame Characteristics Macro Attributes">
    <entry group="0018" element="9412" name="XA/XRF Frame Characteristics Sequence" type="1">
      <description>A sequence that describes general characteristics of this frame.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0008" element="2111" name="&gt;Derivation Description" type="3">
      <description>A text description of how this frame was derived.
See C.8.7.1.1.5 for further explanation.</description>
      <section ref="C.8.7.1.1.5" name="">If an Image is identified to be a Derived image (see C.8.9.1.1.1 Image Type), Derivation Description (0008,2111) is an optional and implementation specific text description of the way the image was derived from an original image. As applied to X-Ray images, it may be used to describe derivation operations such as edge enhancement, temporal filtering, digital subtraction, or other linear and non-linear transformations.
</section>
    </entry>
    <entry group="0008" element="9215" name="&gt;Derivation Code Sequence" type="3">
      <description>A coded description of how this frame was derived. See C.7.6.1.1.3 for further explanation. One or more Items may be included in this Sequence. More than one Item indicates that successive derivation steps have been applied.</description>
      <section ref="C.7.6.1.1.3" name="">If an Image is identified to be a derived image (see C.7.6.1.1.2 Image Type), Derivation Description (0008,2111) and Derivation Code Sequence (0008,9215) describe the way in which the image was derived. They may be used whether or not the Source Image Sequence (0008,2112) is provided. They may also be used in cases when the Derived Image pixel data is not significantly changed from one of the source images and the SOP Instance UID of the Derived Image is the same as the one used for the source image.
Notes:  1. Examples of Derived Images that would normally be expected to affect professional interpretation and would thus have a new UID include:
  a.  images resulting from image processing of another image (e.g. unsharp masking),
  b.  a multiplanar reformatted CT image,
  c.  a DSA image derived by subtracting pixel values of one image from another.
d.  an image that has been decompressed after having been compressed with a lossy compression algorithm. To ensure that the user has the necessary information about the lossy compression, the approximate compression ratio may be included in Derivation Description (0008,2111).
  An example of a Derived Image that would normally not be expected to affect professional interpretation and thus would not require a new UID is an image that has been padded with additional rows and columns for more display purposes.
  2. An image may be lossy compressed, e.g., for long term archive purposes, and its SOP Instance UID changed. PS3.4 provides a mechanism by which a query for the original image Instance may return a reference to the UID of the lossy compressed version of the image using the Alternate Representation Sequence (0008,3001). This allows an application processing a SOP Instance that references the original image UID, e.g., a Structured Report, to obtain a reference to an accessible version of the image even if the original SOP Instance is no longer available.

</section>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 7203."/>
    <entry group="0018" element="1400" name="&gt;Acquisition Device Processing Description" type="3">
      <description>Indicates any visual processing performed on the frame prior to exchange.
See Section C.8.7.1.1.3.</description>
      <section ref="C.8.7.1.1.3" name="">Acquisition Device Processing Description (0018,1400) provides some indication in human readable text of the digital processing on the images before exchange. Examples of this processing are: edge enhanced, subtracted, time filtered, gamma corrected, convolved (spatially filtered).
</section>
    </entry>
    <entry group="0018" element="1401" name="&gt;Acquisition Device Processing Code" type="3">
      <description>Code representing the device-specific processing associated with the frame (e.g. Organ Filtering code)
Note: This Code is manufacturer specific but provides useful annotation information to the knowledgeable observer.</description>
    </entry>
  </macro>
  <macro table="C.8.19.6-2" name="X Ray Field of View Macro Attributes">
    <entry group="0018" element="9432" name="Field of View Sequence" type="1">
      <description>Sequence containing the field of view for this frame.
One or more items may be included in this sequence.</description>
    </entry>
    <entry group="0018" element="1147" name="&gt;Field of View Shape" type="3">
      <description>Shape of the Field of View, that is the image pixels stored in Pixel Data (7FE0,0010).
Enumerated Values:
RECTANGLE
ROUND
HEXAGONAL</description>
    </entry>
    <entry group="0018" element="9461" name="&gt;Field of View Dimension(s) in Float" type="3">
      <description>Dimensions in mm of the Field of View, that is the image pixels stored in Pixel Data (7FE0,0010). If Field of View Shape (0018,1147) is:
RECTANGLE: row dimension followed by column.
ROUND: diameter.
HEXAGONAL: diameter of the circle circumscribing the hexagon.</description>
    </entry>
    <entry group="0018" element="7030" name="&gt;Field of View Origin" type="1C">
      <description>Offset of the TLHC of a rectangle circumscribing the Field of View, i.e., the image pixels stored in Pixel Data (7FE0,0010) before rotation or flipping, from the TLHC of the physical detector area measured in physical detector pixels as a row offset followed by a column offset.
See C.8.11.4.1.1 for further explanation.
Required if X-Ray Receptor Type (0018,9420) is present and equals DIGITAL_DETECTOR.</description>
      <section ref="C.8.11.4.1.1" name="">The relationship between the Physical Detector Area, the Active Detector Area, the Field of View (what is stored in the Pixel Data (7FE0,0010)), the Exposed Area (after X-Ray Collimation) and the Displayed Area is illustrated in the following diagrams.
Note:  Some of these Attributes relate the image data to manufacturer specific characteristics of the detector that may be used for quality control purposes, e.g. correlation of image artifacts with a detector defect map, analysis of noise performance, etc.

The Displayed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the Display Shutter Module (see section C.7.6.11). If this Module is not present or supported, then the Displayed Area is equal to the Field of View.
The Exposed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the X-Ray Collimator Module (see section C.8.7.3).
For the Digital X-Ray IODs, the Field of View is usually rectangular in shape and the same size as the stored Pixel Data (7FE0,0010). The shape and size of the Field of View and the spacing of the pixels are defined by the following Attributes:
- Field of View Shape (0018,1147),
- Field of View Dimensions (0018,1149),
- Imager Pixel Spacing (0018,1164),
- Rows (0028,0010),
- Columns (0028,0011)

The following Attributes define the relationship of the Field of View to the Physical Detector Area:
- Field of View Origin (0018,7030),
- Field of View Rotation (0018,7032),
- Field of View Horizontal Flip (0018,7034).

For the Digital X-Ray IODs, the Active Area, i.e. that part of the detector matrix that was activated for this exposure, is usually rectangular in shape. The shape and size of the Active Area and the size and spacing of the detectors are defined by the following Attributes:
- Detector Active Shape (0018,7024),
- Detector Active Dimensions (0018,7026),
- Detector Element Physical Size (0018,7020),
- Detector Element Spacing (0018,7022).

Notes:  1. The Detector Element Physical Size (0018,7020) and Detector Element Spacing (0018,7022) may be different if there are insensitive regions between each detector.
  2. This model of description is not able to accurately describe multiple matrices of detectors that are “tiled” to produce a single image.

The following optional Attribute defines the relationship of the Active Area to the Physical Detector Area:
- Detector Active Origin (0018,7028).

The relationship between detectors and stored image pixels is defined by Detector Binning (0018,701A) which specifies how many detectors, in each of the row and column directions, contribute to (are pooled or averaged to form) a single stored image pixel.
Note:  Detector Binning (0018,701A) may have values less than one if sub-sampling is used to derive an image with higher spatial resolution than the detector matrix.



Figure C.8-14
Explanation of DX Detector Attributes




Figure C.8-15
Explanation of DX Detector Attributes
</section>
    </entry>
    <entry group="0018" element="7032" name="&gt;Field of View Rotation" type="1">
      <description>Clockwise rotation in degrees of Field of View, i.e., the image pixels stored in Pixel Data (7FE0,0010), relative to the physical detector.
Enumerated Values:
0, 90, 180, 270
See C.8.11.4.1.1 for further explanation.</description>
      <section ref="C.8.11.4.1.1" name="">The relationship between the Physical Detector Area, the Active Detector Area, the Field of View (what is stored in the Pixel Data (7FE0,0010)), the Exposed Area (after X-Ray Collimation) and the Displayed Area is illustrated in the following diagrams.
Note:  Some of these Attributes relate the image data to manufacturer specific characteristics of the detector that may be used for quality control purposes, e.g. correlation of image artifacts with a detector defect map, analysis of noise performance, etc.

The Displayed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the Display Shutter Module (see section C.7.6.11). If this Module is not present or supported, then the Displayed Area is equal to the Field of View.
The Exposed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the X-Ray Collimator Module (see section C.8.7.3).
For the Digital X-Ray IODs, the Field of View is usually rectangular in shape and the same size as the stored Pixel Data (7FE0,0010). The shape and size of the Field of View and the spacing of the pixels are defined by the following Attributes:
- Field of View Shape (0018,1147),
- Field of View Dimensions (0018,1149),
- Imager Pixel Spacing (0018,1164),
- Rows (0028,0010),
- Columns (0028,0011)

The following Attributes define the relationship of the Field of View to the Physical Detector Area:
- Field of View Origin (0018,7030),
- Field of View Rotation (0018,7032),
- Field of View Horizontal Flip (0018,7034).

For the Digital X-Ray IODs, the Active Area, i.e. that part of the detector matrix that was activated for this exposure, is usually rectangular in shape. The shape and size of the Active Area and the size and spacing of the detectors are defined by the following Attributes:
- Detector Active Shape (0018,7024),
- Detector Active Dimensions (0018,7026),
- Detector Element Physical Size (0018,7020),
- Detector Element Spacing (0018,7022).

Notes:  1. The Detector Element Physical Size (0018,7020) and Detector Element Spacing (0018,7022) may be different if there are insensitive regions between each detector.
  2. This model of description is not able to accurately describe multiple matrices of detectors that are “tiled” to produce a single image.

The following optional Attribute defines the relationship of the Active Area to the Physical Detector Area:
- Detector Active Origin (0018,7028).

The relationship between detectors and stored image pixels is defined by Detector Binning (0018,701A) which specifies how many detectors, in each of the row and column directions, contribute to (are pooled or averaged to form) a single stored image pixel.
Note:  Detector Binning (0018,701A) may have values less than one if sub-sampling is used to derive an image with higher spatial resolution than the detector matrix.



Figure C.8-14
Explanation of DX Detector Attributes




Figure C.8-15
Explanation of DX Detector Attributes
</section>
    </entry>
    <entry group="0018" element="7034" name="&gt;Field of View Horizontal Flip" type="1">
      <description>Whether or not a horizontal flip has been applied to the Field of View, i.e., the image pixels stored in Pixel Data (7FE0,0010), after rotation relative to the physical detector as described in Field of View Rotation (0018,7032).
Enumerated Values:
NO
YES
See C.8.11.4.1.1 for further explanation.</description>
      <section ref="C.8.11.4.1.1" name="">The relationship between the Physical Detector Area, the Active Detector Area, the Field of View (what is stored in the Pixel Data (7FE0,0010)), the Exposed Area (after X-Ray Collimation) and the Displayed Area is illustrated in the following diagrams.
Note:  Some of these Attributes relate the image data to manufacturer specific characteristics of the detector that may be used for quality control purposes, e.g. correlation of image artifacts with a detector defect map, analysis of noise performance, etc.

The Displayed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the Display Shutter Module (see section C.7.6.11). If this Module is not present or supported, then the Displayed Area is equal to the Field of View.
The Exposed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the X-Ray Collimator Module (see section C.8.7.3).
For the Digital X-Ray IODs, the Field of View is usually rectangular in shape and the same size as the stored Pixel Data (7FE0,0010). The shape and size of the Field of View and the spacing of the pixels are defined by the following Attributes:
- Field of View Shape (0018,1147),
- Field of View Dimensions (0018,1149),
- Imager Pixel Spacing (0018,1164),
- Rows (0028,0010),
- Columns (0028,0011)

The following Attributes define the relationship of the Field of View to the Physical Detector Area:
- Field of View Origin (0018,7030),
- Field of View Rotation (0018,7032),
- Field of View Horizontal Flip (0018,7034).

For the Digital X-Ray IODs, the Active Area, i.e. that part of the detector matrix that was activated for this exposure, is usually rectangular in shape. The shape and size of the Active Area and the size and spacing of the detectors are defined by the following Attributes:
- Detector Active Shape (0018,7024),
- Detector Active Dimensions (0018,7026),
- Detector Element Physical Size (0018,7020),
- Detector Element Spacing (0018,7022).

Notes:  1. The Detector Element Physical Size (0018,7020) and Detector Element Spacing (0018,7022) may be different if there are insensitive regions between each detector.
  2. This model of description is not able to accurately describe multiple matrices of detectors that are “tiled” to produce a single image.

The following optional Attribute defines the relationship of the Active Area to the Physical Detector Area:
- Detector Active Origin (0018,7028).

The relationship between detectors and stored image pixels is defined by Detector Binning (0018,701A) which specifies how many detectors, in each of the row and column directions, contribute to (are pooled or averaged to form) a single stored image pixel.
Note:  Detector Binning (0018,701A) may have values less than one if sub-sampling is used to derive an image with higher spatial resolution than the detector matrix.



Figure C.8-14
Explanation of DX Detector Attributes




Figure C.8-15
Explanation of DX Detector Attributes
</section>
    </entry>
    <entry group="0018" element="9433" name="&gt;Field of View Description" type="3">
      <description>Manufacturer defined description of the field of view selected during acquisition.</description>
    </entry>
  </macro>
  <macro table="C.8.19.6-3" name="X Ray Exposure Control Sensing Regions Macro Attributes">
    <entry group="0018" element="9434" name="Exposure Control Sensing Regions Sequence" type="1">
      <description>Sequence containing the Exposure Control Sensing Region for this frame.
One or more items may be included in this sequence.</description>
    </entry>
    <entry group="0018" element="9435" name="&gt;Exposure Control Sensing Region Shape" type="1">
      <description>Shape of the Exposure Control Sensing Region. Enumerated Values:
RECTANGULAR
CIRCULAR
POLYGONAL</description>
    </entry>
    <entry group="0018" element="9436" name="&gt;Exposure Control Sensing Region Left Vertical Edge" type="1C">
      <description>Required if Exposure Control Sensing Region Shape (0018,9435) is RECTANGULAR. Location of the left edge of the rectangular Exposure Control Sensing Region expressed as effective pixel column. See C.8.19.6.3.1.</description>
      <section ref="C.8.19.6.3.1" name="">The Exposure Control Sensing Region Left Vertical Edge (0018,9436), Exposure Control Sensing Region Right Vertical Edge (0018,9437), Exposure Control Sensing Region Upper Horizontal Edge (0018,9438), Exposure Control Sensing Region Lower Horizontal Edge (0018,9439) and Center of Circular Exposure Control Sensing Region (0018,9440) may have a negative value when the point defined by the attribute lies outside the left or upper border of the pixel data matrix. The top left pixel of the image has a pixel row and column value of 1.
</section>
    </entry>
    <entry group="0018" element="9437" name="&gt;Exposure Control Sensing Region Right Vertical Edge" type="1C">
      <description>Required if Exposure Control Sensing Region Shape (0018,9435) is RECTANGULAR. Location of the right edge of the rectangular Exposure Control Sensing Region expressed as effective pixel column. See C.8.19.6.3.1.</description>
      <section ref="C.8.19.6.3.1" name="">The Exposure Control Sensing Region Left Vertical Edge (0018,9436), Exposure Control Sensing Region Right Vertical Edge (0018,9437), Exposure Control Sensing Region Upper Horizontal Edge (0018,9438), Exposure Control Sensing Region Lower Horizontal Edge (0018,9439) and Center of Circular Exposure Control Sensing Region (0018,9440) may have a negative value when the point defined by the attribute lies outside the left or upper border of the pixel data matrix. The top left pixel of the image has a pixel row and column value of 1.
</section>
    </entry>
    <entry group="0018" element="9438" name="&gt;Exposure Control Sensing Region Upper Horizontal Edge" type="1C">
      <description>Required if Exposure Control Sensing Region Shape (0018,9435) is RECTANGULAR. Location of the upper edge of the rectangular Exposure Control Sensing Region expressed as effective pixel row. See C.8.19.6.3.1.</description>
      <section ref="C.8.19.6.3.1" name="">The Exposure Control Sensing Region Left Vertical Edge (0018,9436), Exposure Control Sensing Region Right Vertical Edge (0018,9437), Exposure Control Sensing Region Upper Horizontal Edge (0018,9438), Exposure Control Sensing Region Lower Horizontal Edge (0018,9439) and Center of Circular Exposure Control Sensing Region (0018,9440) may have a negative value when the point defined by the attribute lies outside the left or upper border of the pixel data matrix. The top left pixel of the image has a pixel row and column value of 1.
</section>
    </entry>
    <entry group="0018" element="9439" name="&gt;Exposure Control Sensing Region Lower Horizontal Edge" type="1C">
      <description>Required if Exposure Control Sensing Region Shape (0018,9435) is RECTANGULAR. Location of the lower edge of the rectangular Exposure Control Sensing Region expressed as effective pixel row. See C.8.19.6.3.1.</description>
      <section ref="C.8.19.6.3.1" name="">The Exposure Control Sensing Region Left Vertical Edge (0018,9436), Exposure Control Sensing Region Right Vertical Edge (0018,9437), Exposure Control Sensing Region Upper Horizontal Edge (0018,9438), Exposure Control Sensing Region Lower Horizontal Edge (0018,9439) and Center of Circular Exposure Control Sensing Region (0018,9440) may have a negative value when the point defined by the attribute lies outside the left or upper border of the pixel data matrix. The top left pixel of the image has a pixel row and column value of 1.
</section>
    </entry>
    <entry group="0018" element="9440" name="&gt;Center of Circular Exposure Control Sensing Region" type="1C">
      <description>Required if Exposure Control Sensing Region Shape (0018,9435) is CIRCULAR. Location of the center of the circular Exposure Control Sensing Region expressed as effective pixel row and column. See C.8.19.6.3.1.</description>
      <section ref="C.8.19.6.3.1" name="">The Exposure Control Sensing Region Left Vertical Edge (0018,9436), Exposure Control Sensing Region Right Vertical Edge (0018,9437), Exposure Control Sensing Region Upper Horizontal Edge (0018,9438), Exposure Control Sensing Region Lower Horizontal Edge (0018,9439) and Center of Circular Exposure Control Sensing Region (0018,9440) may have a negative value when the point defined by the attribute lies outside the left or upper border of the pixel data matrix. The top left pixel of the image has a pixel row and column value of 1.
</section>
    </entry>
    <entry group="0018" element="9441" name="&gt;Radius of Circular Exposure Control Sensing Region" type="1C">
      <description>Required if Exposure Control Sensing Region Shape (0018,9435) is CIRCULAR. Radius of the circular Exposure Control Sensing Region expressed as effective number of pixels along the row direction. See C.8.19.6.3.1.</description>
      <section ref="C.8.19.6.3.1" name="">The Exposure Control Sensing Region Left Vertical Edge (0018,9436), Exposure Control Sensing Region Right Vertical Edge (0018,9437), Exposure Control Sensing Region Upper Horizontal Edge (0018,9438), Exposure Control Sensing Region Lower Horizontal Edge (0018,9439) and Center of Circular Exposure Control Sensing Region (0018,9440) may have a negative value when the point defined by the attribute lies outside the left or upper border of the pixel data matrix. The top left pixel of the image has a pixel row and column value of 1.
</section>
    </entry>
    <entry group="0018" element="9442" name="&gt;Vertices of the Polygonal Exposure Control Sensing Region" type="1C">
      <description>Required if Exposure Control Sensing Region Shape (0018,9435) is POLYGONAL.
Multiple Values where the first set of two values are:
row of the origin vertex;
column of the origin vertex.
Two or more pairs of values follow and are the effective pixel row and column coordinates of the other vertices of the polygon Exposure Control Sensing Region. Polygon Exposure Control Sensing Regions are implicitly closed from the last vertex to the origin vertex and all edges shall be non-intersecting except at the vertices. See C.8.19.6.3.1.</description>
      <section ref="C.8.19.6.3.1" name="">The Exposure Control Sensing Region Left Vertical Edge (0018,9436), Exposure Control Sensing Region Right Vertical Edge (0018,9437), Exposure Control Sensing Region Upper Horizontal Edge (0018,9438), Exposure Control Sensing Region Lower Horizontal Edge (0018,9439) and Center of Circular Exposure Control Sensing Region (0018,9440) may have a negative value when the point defined by the attribute lies outside the left or upper border of the pixel data matrix. The top left pixel of the image has a pixel row and column value of 1.
</section>
    </entry>
  </macro>
  <macro table="C.8.19.6-4" name="XA/XRF Frame Pixel Data Properties Macro Attributes">
    <entry group="0028" element="9443" name="Frame Pixel Data Properties Sequence" type="1">
      <description>Sequence containing the pixel data properties for this frame.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0028" element="1040" name="&gt;Pixel Intensity Relationship" type="1">
      <description>The relationship between the Pixel and the X-Ray beam intensity. See C.8.19.6.4.1.</description>
      <section ref="C.8.19.6.4.1" name="">Pixel Intensity Relationship (0028,1040) shall identify the relationship of the pixel values to the X-Ray beam intensity. Defined terms are:
<unrecognized-rows><term value="LIN" meaning="Approximately proportional to X-Ray beam intensity."/><term value="LOG" meaning="Non-linear “ Log Function”; A Pixel Intensity Relationship LUT shall be included with the image to allow it to be mapped back to its proportional value to X-Ray beam intensity."/><term value="OTHER" meaning="Not proportional to X-Ray beam intensity. If a TO_LINEAR Pixel Intensity Relationship LUT item is supplied, scaling back to X-Ray beam intensity is possible."/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="1041" name="&gt;Pixel Intensity Relationship Sign" type="1">
      <description>The sign of the relationship between the Pixel sample values stored in Pixel Data (7FE0,0010) and the X-Ray beam intensity.
Enumerated Values:
1 = Lower pixel values correspond to less X-Ray beam intensity
-1 = Higher pixel values correspond to less X-Ray beam intensity
See C.8.11.3.1.2 for further explanation.</description>
      <section ref="C.8.11.3.1.2" name="">Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041) describe how the stored pixel values in Pixel Data (7FE0,0010) are related to the X-Ray beam intensity incident on the detector.
They do not define a transformation intended to be applied to the pixel data for presentation.
Note:  For example, if Pixel Intensity Relationship (0028,1040) is LIN and Pixel Intensity Relationship Sign (0028,1041) is -1, then lower values of Pixel Data (7FE0,0010) indicate higher X-Ray beam intensities corresponding to less radiographically dense regions projected on the image such as through air, and higher values of Pixel Data (7FE0,0010) indicate lower X-Ray beam intensities corresponding to more radiographically dense regions projected on the image such as through bone and radio-opaque contrast agents.

The transformation to be applied to the pixel data for presentation is defined by the successive application of the conceptual Modality LUT, the VOI Attributes and the conceptual Presentation LUT. This shall result in the output of P-Values.
Rescale Slope (0028,1053) and Rescale Intercept (0028,1052) define a linear subset of a conceptual Modality LUT transformation. For IODs that include this Module, these Attributes define an identity transformation. IODs that include the DX Image Module shall not include the Modality LUT Module.
The Presentation LUT Shape (2050,0020) defines a subset of a conceptual Presentation LUT. For IODs that include this Module, this Attribute defines an identity transformation or inverse identity transformation. IODs that include the DX Image Module shall not include the Presentation LUT Module.
Photometric Interpretation (0028,0004) indicates whether lower values that are the output of the VOI Attributes should be displayed as darker or lighter. Since the output of the equivalent of a conceptual Presentation LUT is in P-Values, which are defined in PS 3.14 such that lower values correspond to lower luminance levels, then the definition of the Presentation LUT Shape (2050,0020), otherwise intended to be an identity transformation, must take into account the effect of the value specified for Photometric Interpretation (0028,0004).
Note:  Regardless of the values of Pixel Intensity Relationship (0028,1040) and Pixel Intensity Relationship Sign (0028,1041), the grayscale transformations to be applied to the Pixel Data (7FE0,0010) are defined by the equivalent of the Modality LUT (Rescale Slope (0028,1053) and Rescale Intercept (0028,1052)), Value of Interest Attributes, Photometric Interpretation (0028,0004) and the equivalent of the Presentation LUT (Presentation LUT Shape (2050,0020)). However, the combination of the grayscale transformations and the description of the pixel intensity relationship, together define whether, for example, air is expected to be displayed as black or white.

</section>
    </entry>
    <entry group="0028" element="9444" name="&gt;Geometrical Properties" type="1">
      <description>Geometrical characteristics of the pixel data to indicate whether pixel spacing is uniform for all pixels or not.
Enumerated Values:
UNIFORM
NON_UNIFORM</description>
    </entry>
    <entry group="0028" element="9445" name="&gt;Geometric Maximum Distortion" type="2C">
      <description>The percentage of the maximum deviation of the pixel spacing values of images for which the geometric properties are non-uniform.
Note: This attribute may be used to judge the result of measurements, 3D reconstructions, etc.
Required if Geometrical Properties (0028,9444) equals NON_UNIFORM.</description>
    </entry>
    <entry group="0028" element="9446" name="&gt;Image Processing Applied" type="1">
      <description>The type or a combination of types of image processing applied to the pixel data before being stored.
Defined Terms:
DIGITAL_SUBTR
HIGH_PASS_FILTER
LOW_PASS_FILTER
MULTI_BAND_FLTR
FRAME_AVERAGING
NONE</description>
    </entry>
  </macro>
  <macro table="C.8.19.6-5" name="X Ray Frame Detector Parameters Macro Attributes">
    <entry group="0018" element="9451" name="Frame Detector Parameters Sequence" type="1">
      <description>Sequence containing the detector properties for this frame.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="7014" name="&gt;Detector Active Time" type="3">
      <description>Time in mSec that the detector is active during acquisition of this image.
Note: This activation window overlaps the time of the X-Ray exposure as defined by Exposure Time in ms (0018,9328) and Detector Activation Offset From Exposure (0018,7016).</description>
    </entry>
    <entry group="0018" element="7016" name="&gt;Detector Activation Offset From Exposure" type="3">
      <description>Offset time in mSec that the detector becomes active after the X-Ray beam is turned on during acquisition of this image. May be negative.</description>
    </entry>
  </macro>
  <macro table="C.8.19.6-6" name="X Ray Calibration Device Usage Macro Attributes">
    <entry group="0018" element="9455" name="Calibration Sequence" type="1">
      <description>Sequence containing the calibration flag for this frame.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0050" element="0004" name="&gt;Calibration Image" type="1">
      <description>Indicates whether a reference object (phantom) of known size is present in the frame and was used for calibration. Enumerated Values:
YES
NO
Note: Device is identified using the Device module. See C.7.6.12.</description>
      <section ref="C.7.6.12" name="">Table C.7-18 describes the Attributes of devices or calibration objects (e.g., catheters, markers, baskets) that are associated with a study and/or image.
Table C.7-18
DEVICE MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Device Sequence" meaning="(0050,0010)"/><term value="&gt;Include ‘Code Sequence Macro’ Table 8.8-1" meaning="Baseline Context ID is 4051."/><term value="&gt;Manufacturer" meaning="(0008,0070)"/><term value="&gt;Manufacturer’s Model Name" meaning="(0008,1090)"/><term value="&gt;Device Serial Number" meaning="(0018,1000)"/><term value="&gt;Device ID" meaning="(0018,1003)"/><term value="&gt;Device Length" meaning="(0050,0014)"/><term value="&gt;Device Diameter" meaning="(0050,0016)"/><term value="&gt;Device Diameter Units" meaning="(0050,0017)"/><term value="&gt;Device Volume" meaning="(0050,0018)"/><term value="&gt;Inter-Marker Distance" meaning="(0050,0019)"/><term value="&gt;Device Description" meaning="(0050,0020)"/></unrecognized-rows>
         </section>
    </entry>
  </macro>
  <macro table="C.8.19.6-7" name="X Ray Object Thickness Macro Attributes">
    <entry group="0018" element="9456" name="Object Thickness Sequence" type="1">
      <description>Sequence containing object thickness for this frame.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9452" name="&gt;Calculated Anatomy Thickness" type="1">
      <description>The physical thickness in mm of the anatomic region of interest as specified in the Anatomic Region Sequence (0008,2218) in the direction of the center of the beam.
Note: The value takes in account the position relative to object and the X-Ray source - detector axis.</description>
    </entry>
  </macro>
  <macro table="C.8.19.6-8" name="X Ray Frame Acquisition Macro Attributes">
    <entry group="0018" element="9417" name="Frame Acquisition Sequence" type="1">
      <description>Sequence containing the acquisition parameters for this frame.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="0060" name="&gt;KVP" type="1">
      <description>Exact peak kilo voltage output of the X-Ray generator used for this frame.</description>
    </entry>
    <entry group="0018" element="9330" name="&gt;X-Ray Tube Current in mA" type="1">
      <description>Exact Nominal X-Ray tube current in milliamperes applied during the Acquisition Duration (0018,9220) for this frame.</description>
    </entry>
  </macro>
  <macro table="C.8.19.6-9" name="X Ray Projection Pixel Calibration Macro Attributes">
    <entry group="0018" element="9401" name="Projection Pixel Calibration Sequence" type="1">
      <description>A sequence that describes the geometrical position of the patient relative to the equipment.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9403" name="&gt;Distance Object to Table Top" type="2">
      <description>Distance between the anatomic region of interest of observation and table top in mm.
Notes: 1.This value is always positive, the object is assumed to be above the table.
2.The value of this attribute is depending on the patient position on the tabletop (supine, left or right decubitus, etc.)</description>
    </entry>
    <entry group="0018" element="9404" name="&gt;Object Pixel Spacing in Center of Beam" type="1C">
      <description>Physical distance within the anatomic region of interest in the center of the beam and perpendicular to the beam between the center of each pixel, specified by a numeric pair adjacent row spacing (delimiter) adjacent column spacing in mm. See C.8.19.6.9.2. See 10.7.1.3 for further explanation of the value order.
Required if Distance Object to Table Top (0018,9403) is not empty.
Note: This value is provided besides the values that are the input parameters of the calibration algorithm.</description>
      <section ref="C.8.19.6.9.2" name="">The value provided for the Beam Angle (0018,9449) attribute shall correspond to the other attribute values within this module and according to the mathematic terms listed in section C.8.19.6.9.1.
The terms listed will result in infinite result when used with 90-degree beam angles.
It is outside the scope of this Standard to define reasonable limits for single input values in the above-mentioned terms, or to define the mathematical accuracy of applications using those terms.
Note:  It may be reasonable to limit automatic calculations to a narrow range of +/- 60 degrees for Beam Angle and inform users about possible deviations in the calibration result when exceeding such range limits.

</section>
    </entry>
    <entry group="0018" element="1130" name="&gt;Table Height" type="1C">
      <description>The distance of the top of the patient table to the center of rotation of the source (i.e. the isocenter) in mm. A positive value indicates that the tabletop is below the isocenter.
Note: All the distances are measured perpendicular to the Table Top plane.
Required if Image Type (0008,0008) Value 1 is ORIGINAL, may be present otherwise.</description>
    </entry>
    <entry group="0018" element="9449" name="&gt;Beam Angle" type="1C">
      <description>The equipment related angle in degrees of the X-Ray beam relative to the perpendicular to the tabletop plane. An angle from 0 to +90 degrees indicates that the X-Ray source is below the table.
The valid range is 0 to +180 degrees.
Required if Image Type (0008,0008) Value 1 is ORIGINAL, may be present otherwise.</description>
    </entry>
  </macro>
  <macro table="C.8.19.6-10" name="X Ray Positioner Macro Attributes">
    <entry group="0018" element="9405" name="Positioner Position Sequence" type="1">
      <description>A sequence that describes the geometrical position of the positioner.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="1510" name="&gt;Positioner Primary Angle" type="1C">
      <description>Position of the X-Ray Image Intensifier about the patient from the RAO to LAO direction where movement from RAO to vertical is positive.
See C.8.7.5.1.2.
Required if Positioner Type (0018,1508) equals CARM.</description>
      <section ref="C.8.7.5.1.2" name="">The definitions of Positioner Angles shall be with respect to the patient as illustrated in Figures C.8-11 and C.8-12 Zero degree is referenced to the origin perpendicular to the patient's chest. The Positioner Primary Angle definition is like longitude (in the equatorial plan); the Positioner Secondary Angle definition is like latitude (in the sagittal plane). The Positioner Angle attributes apply to the first frame of a multi-frame image. The valid range of Primary Positioner Angle is -180 to +180 degrees and the Secondary Positioner Angle range is -90 to + 90 degrees.
The Patient Plane is defined by the isocenter of the imaging device and slices through the patient such that it is perpendicular to the sagittal plane of the body. The Primary Axis of rotation is defined at the intersection of the Patient Plane and of the Sagittal Plane. The Positioner Primary Angle is defined in the transaxial plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest and + 90 degrees at the Patient left hand side (LAO) and -90 at the Patient right hand side (RAO). The valid range of Primary Positioner Angle is -180 to +180 degrees.
The Secondary Axis is in the Patient Plane and is perpendicular to the Primary Axis at the isocenter. The Positioner Secondary Angle is defined in the Sagittal Plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest. +90 degrees corresponds to the cranial direction. The Secondary Positioner Angle range is -90 to + 90 degrees.
At a 0 angle for both the Primary Angle (0018,1510) and Secondary Angle (0018,1511), the patient faces the Image Intensifier.
The Positioner Primary Angle (0018,1510) and Secondary Angle (0018,1511) apply to the first frame of a multi-frame image.

Figure C.8-11
Positioner Primary Angle

Figure C.8-12
Positioner Secondary Angle
</section>
    </entry>
    <entry group="0018" element="1511" name="&gt;Positioner Secondary Angle" type="1C">
      <description>Position of the X-Ray Image Intensifier about the patient from the CAU to CRA direction where movement from CAU to vertical is positive.
See C.8.7.5.1.2
Required if Positioner Type (0018,1508) equals CARM.</description>
      <section ref="C.8.7.5.1.2" name="">The definitions of Positioner Angles shall be with respect to the patient as illustrated in Figures C.8-11 and C.8-12 Zero degree is referenced to the origin perpendicular to the patient's chest. The Positioner Primary Angle definition is like longitude (in the equatorial plan); the Positioner Secondary Angle definition is like latitude (in the sagittal plane). The Positioner Angle attributes apply to the first frame of a multi-frame image. The valid range of Primary Positioner Angle is -180 to +180 degrees and the Secondary Positioner Angle range is -90 to + 90 degrees.
The Patient Plane is defined by the isocenter of the imaging device and slices through the patient such that it is perpendicular to the sagittal plane of the body. The Primary Axis of rotation is defined at the intersection of the Patient Plane and of the Sagittal Plane. The Positioner Primary Angle is defined in the transaxial plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest and + 90 degrees at the Patient left hand side (LAO) and -90 at the Patient right hand side (RAO). The valid range of Primary Positioner Angle is -180 to +180 degrees.
The Secondary Axis is in the Patient Plane and is perpendicular to the Primary Axis at the isocenter. The Positioner Secondary Angle is defined in the Sagittal Plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest. +90 degrees corresponds to the cranial direction. The Secondary Positioner Angle range is -90 to + 90 degrees.
At a 0 angle for both the Primary Angle (0018,1510) and Secondary Angle (0018,1511), the patient faces the Image Intensifier.
The Positioner Primary Angle (0018,1510) and Secondary Angle (0018,1511) apply to the first frame of a multi-frame image.

Figure C.8-11
Positioner Primary Angle

Figure C.8-12
Positioner Secondary Angle
</section>
    </entry>
    <entry group="0018" element="9447" name="&gt;Column Angulation (Patient)" type="1C">
      <description>Angle of the X-Ray beam in degree relative to an orthogonal axis to the detector plane. Positive values indicate that the tilt is towards the head of the patient.
Notes: 1. The detector plane is assumed to be parallel to the table plane
2. This attribute differentiates form the attribute Column Angulation (0018,1450) by using the patient based coordinate system instead of the equipment based coordinate system.
Required if Positioner Type (0018,1508) equals COLUMN.</description>
    </entry>
  </macro>
  <macro table="C.8.19.6-11" name="X Ray Table Position Macro Attributes">
    <entry group="0018" element="9406" name="Table Position Sequence" type="1">
      <description>A sequence that describes the geometrical position of the table top.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="300A" element="0128" name="&gt;Table Top Vertical Position" type="1">
      <description>Table Top Vertical position with respect to an arbitrary chosen reference by the equipment in (mm). Table motion downwards is positive</description>
    </entry>
    <entry group="300A" element="0129" name="&gt;Table Top Longitudinal Position" type="1">
      <description>Table Top Longitudinal position with respect to an arbitrary chosen reference by the equipment in (mm). Table motion towards LAO is positive assuming that the patient is positioned supine and its head is in normal position.</description>
    </entry>
    <entry group="300A" element="012A" name="&gt;Table Top Lateral Position" type="1">
      <description>Table Top Lateral position with respect to an arbitrary chosen reference by the equipment in (mm). Table motion towards CRA is positive assuming that the patient is positioned supine and its head is in normal position.</description>
    </entry>
    <entry group="0018" element="9469" name="&gt;Table Horizontal Rotation Angle" type="1">
      <description>Rotation of the table in the horizontal plane (clockwise when looking from above the table).</description>
    </entry>
    <entry group="0018" element="9470" name="&gt;Table Head Tilt Angle" type="1">
      <description>Angle of the head-feet axis of the table in degrees relative to the horizontal plane. Positive values indicate that the head of the table is upwards.</description>
    </entry>
    <entry group="0018" element="9471" name="&gt;Table Cradle Tilt Angle" type="1">
      <description>Angle of the left-right axis of the table in degrees relative to the horizontal plane. Positive values indicate that the left of the table is upwards.</description>
    </entry>
  </macro>
  <macro table="C.8.19.6-12" name="X Ray Collimator Macro Attributes">
    <entry group="0018" element="9407" name="Collimator Shape Sequence" type="1">
      <description>A sequence that describes the collimator shape.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="1700" name="&gt;Collimator Shape" type="1">
      <description>Shape(s) of the collimator. Enumerated Values:
RECTANGULAR
CIRCULAR
POLYGONAL
This multi-valued Attribute shall contain at most one of each Enumerated Value.</description>
    </entry>
    <entry group="0018" element="1702" name="&gt;Collimator Left Vertical Edge" type="1C">
      <description>Required if Collimator Shape (0018,1700) is RECTANGULAR. Location of the left edge of the rectangular collimator expressed as effective pixel column. See C.8.7.3.1.1 and C.8.19.6.12.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1704" name="&gt;Collimator Right Vertical Edge" type="1C">
      <description>Required if Collimator Shape (0018,1700) is RECTANGULAR. Location of the right edge of the rectangular collimator expressed as effective pixel column. See C.8.7.3.1.1 and C.8.19.6.12.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1706" name="&gt;Collimator Upper Horizontal Edge" type="1C">
      <description>Required if Collimator Shape (0018,1700) is RECTANGULAR. Location of the upper edge of the rectangular collimator expressed as effective pixel row. See C.8.7.3.1.1 and C.8.19.6.12.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1708" name="&gt;Collimator Lower Horizontal Edge" type="1C">
      <description>Required if Collimator Shape (0018,1700) is RECTANGULAR. Location of the lower edge of the rectangular collimator expressed as effective pixel row. See C.8.7.3.1.1 and C.8.19.6.12.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1710" name="&gt;Center of Circular Collimator" type="1C">
      <description>Required if Collimator Shape (0018,1700) is CIRCULAR. Location of the center of the circular collimator expressed as effective pixel row and column. See C.8.7.3.1.1 and C.8.19.6.12.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1712" name="&gt;Radius of Circular Collimator" type="1C">
      <description>Required if Collimator Shape (0018,1700) is CIRCULAR. Radius of the circular collimator expressed as effective number of pixels along the row direction. See C.8.7.3.1.1 and C.8.19.6.12.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1720" name="&gt;Vertices of the Polygonal Collimator" type="1C">
      <description>Required if Collimator Shape (0018,1700) is POLYGONAL.
Multiple Values where the first set of two values are:
row of the origin vertex;
column of the origin vertex.
Two or more pairs of values follow and are the effective pixel row and column coordinates of the other vertices of the polygon collimator. Polygon collimators are implicitly closed from the last vertex to the origin vertex and all edges shall be non-intersecting except at the vertices. See C.8.19.6.12.1.</description>
      <section ref="C.8.19.6.12.1" name="">The top left pixel of the image has a pixel row and column value of 1.
</section>
    </entry>
  </macro>
  <macro table="C.8.19.6-13" name="X Ray Isocenter Reference System Macro Attributes">
    <entry group="0018" element="9462" name="Isocenter Reference System Sequence" type="1">
      <description>A sequence that describes the Isocenter Reference Coordinate System (O, X, Y, Z).
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9463" name="&gt;Positioner Isocenter Primary Angle" type="1">
      <description>Position of the X-Ray center beam in the isocenter reference system in the X direction (deg).
See C.8.19.6.13.1.2 for further explanation.</description>
      <section ref="C.8.19.6.13.1.2" name="">The positioner coordinate system (Op, Xp, Yp, Zp) is defined as follows:
</section>
    </entry>
    <entry group="0018" element="9464" name="&gt;Positioner Isocenter Secondary Angle" type="1">
      <description>Position of the X-Ray center beam in the isocenter reference system in the Z direction (deg).
See C.8.19.6.13.1.2 for further explanation.</description>
      <section ref="C.8.19.6.13.1.2" name="">The positioner coordinate system (Op, Xp, Yp, Zp) is defined as follows:
</section>
    </entry>
    <entry group="0018" element="9465" name="&gt;Positioner Isocenter Detector Rotation Angle" type="1">
      <description>Rotation of the X-Ray detector plane (deg).
See C.8.19.6.13.1.2 for further explanation.</description>
      <section ref="C.8.19.6.13.1.2" name="">The positioner coordinate system (Op, Xp, Yp, Zp) is defined as follows:
</section>
    </entry>
    <entry group="0018" element="9466" name="&gt;Table X Position to Isocenter" type="1">
      <description>X position of the Table Reference Point with respect to the Isocenter (mm).
See C.8.19.6.13.1.3 for further explanation.</description>
      <section ref="C.8.19.6.13.1.3" name="">The table coordinate system (Ot, Xt, Yt, Zt) is defined as follows:
</section>
    </entry>
    <entry group="0018" element="9467" name="&gt;Table Y Position to Isocenter" type="1">
      <description>Y position of the Table Reference Point with respect to the Isocenter (mm).
See C.8.19.6.13.1.3 for further explanation.</description>
      <section ref="C.8.19.6.13.1.3" name="">The table coordinate system (Ot, Xt, Yt, Zt) is defined as follows:
</section>
    </entry>
    <entry group="0018" element="9468" name="&gt;Table Z Position to Isocenter" type="1">
      <description>Z position of the Table Reference Point with respect to the Isocenter (mm).
See C.8.19.6.13.1.3 for further explanation.</description>
      <section ref="C.8.19.6.13.1.3" name="">The table coordinate system (Ot, Xt, Yt, Zt) is defined as follows:
</section>
    </entry>
    <entry group="0018" element="9469" name="&gt;Table Horizontal Rotation Angle" type="1">
      <description>Rotation of the table in the horizontal plane.
See C.8.19.6.13.1.3 for further explanation.</description>
      <section ref="C.8.19.6.13.1.3" name="">The table coordinate system (Ot, Xt, Yt, Zt) is defined as follows:
</section>
    </entry>
    <entry group="0018" element="9470" name="&gt;Table Head Tilt Angle" type="1">
      <description>Angle of the head-feet axis of the table in degrees relative to the horizontal plane.
See C.8.19.6.13.1.3 for further explanation.</description>
      <section ref="C.8.19.6.13.1.3" name="">The table coordinate system (Ot, Xt, Yt, Zt) is defined as follows:
</section>
    </entry>
    <entry group="0018" element="9471" name="&gt;Table Cradle Tilt Angle" type="1">
      <description>Angle of the left-right axis of the table in degrees relative to the horizontal plane.
See C.8.19.6.13.1.3 for further explanation.</description>
      <section ref="C.8.19.6.13.1.3" name="">The table coordinate system (Ot, Xt, Yt, Zt) is defined as follows:
</section>
    </entry>
  </macro>
  <macro table="C.8.19.6-14" name="X Ray Geometry Macro Attributes">
    <entry group="0018" element="9476" name="X-Ray Geometry Sequence" type="1">
      <description>Sequence containing the geometric properties for this frame.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0018" element="9402" name="&gt;Distance Source to Isocenter" type="1">
      <description>Distance from source to isocenter in mm.</description>
    </entry>
    <entry group="0018" element="1110" name="&gt;Distance Source to Detector" type="1">
      <description>Distance from source to receptor plane perpendicular to the receptor plane in mm.
Note: This value is traditionally referred to as Source Image Receptor Distance (SID).</description>
    </entry>
  </macro>
  <module ref="C.8.19.7" table="C.8.19.7-1" name="XA/XRF Multi Frame Presentation Module Attributes">
    <entry group="0018" element="1244" name="Preferred Playback Sequencing" type="3">
      <description>Describes the preferred playback sequencing for a multi-frame image.
Enumerated Values:
0 = Looping (1,2...n,1,2,...n,1,2,....n,...)
1 = Sweeping (1,2,...n,n -1,...2,1,2,...n,...)</description>
    </entry>
    <entry group="0008" element="9458" name="Frame Display Sequence" type="3">
      <description>Sequence that specifies the display frame rate of a selected set of frames. The Items are ordered in increasing frame number. The range of the frames may not overlap and the ranges shall be adjacent.
One or more items may be included.</description>
    </entry>
    <entry group="0008" element="2142" name="&gt;Start Trim" type="1">
      <description>The Frame Number of the first frame of the set of frames to be displayed in this Item.</description>
    </entry>
    <entry group="0008" element="2143" name="&gt;Stop Trim" type="1">
      <description>The Frame Number of the last frame of the set of frames to be displayed in this Item.</description>
    </entry>
    <entry group="0008" element="9460" name="&gt;Skip Frame Range Flag" type="1">
      <description>A flag indicating that the range of frames in this item may be skipped.
Defined Terms:
DISPLAY
SKIP</description>
    </entry>
    <entry group="0008" element="9459" name="&gt;Recommended Display Frame Rate in Float" type="1">
      <description>Recommended rate at which the frames of this Item should be displayed in frames/second.</description>
    </entry>
    <entry group="0028" element="1090" name="Recommended Viewing Mode" type="2">
      <description>Specifies the recommended viewing protocol(s).
Defined terms:
SUB = subtraction with mask images
NAT = native viewing of image as stored
Note: If an implementation does not recognize the defined term for Recommended Viewing Mode (0028,1090), reverting to native display mode is recommended.</description>
    </entry>
    <entry group="0028" element="9411" name="Display Filter Percentage" type="2">
      <description>Edge enhancement filter percentage that is recommended by the pixel data creator as filter presetting for display purposes. The value of 100% corresponds to the maximum filter strength that can be applied by a specific application displaying the image.</description>
    </entry>
  </module>
  <module ref="C.8.20.1" table="C.8.20-1" name="Segmentation Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Modality Type
Enumerated Value:
SEG</description>
    </entry>
    <entry group="0020" element="0011" name="Series Number" type="1">
      <description>A number that identifies this Series</description>
    </entry>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence" type="1C">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance to which the Series is related (e.g. a Modality or General-Purpose Performed Procedure Step SOP). Only a single Item is permitted in this sequence.
Required if the SOP Instance was created in a workflow managed with the Modality Performed Procedure Step SOP Class or General Purpose Performed Procedure Step SOP Class.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.8.20.2" table="C.8.20-2" name="Segmentation Image Module Attributes">
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Value 1 shall be DERIVED. Value 2 shall be PRIMARY. No other values shall be present.</description>
    </entry>
    <include ref="Include Content Identification Macro Table 10-12"/>
    <entry group="0028" element="0002" name="Samples Per Pixel" type="1">
      <description>Enumerated Values:
1</description>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Enumerated Values:
MONOCHROME2</description>
    </entry>
    <entry group="0028" element="0103" name="Pixel Representation" type="1">
      <description>Enumerated Values:
0</description>
    </entry>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>If Segmentation Type (0062,0001) is BINARY, shall be 1. Otherwise it shall be 8. See Section C.8.20.2.1.</description>
      <section ref="C.8.20.2.1" name="">As a consequence of the enumerated Bits Allocated and Bits Stored attribute values, single bit pixels shall be packed 8 to a byte as defined by the encoding rules in PS 3.5.
</section>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>If Segmentation Type (0062,0001) is BINARY, shall be 1. Otherwise it shall be 8. See Section C.8.20.2.1.</description>
      <section ref="C.8.20.2.1" name="">As a consequence of the enumerated Bits Allocated and Bits Stored attribute values, single bit pixels shall be packed 8 to a byte as defined by the encoding rules in PS 3.5.
</section>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>If Segmentation Type (0062,0001) is BINARY, shall be 0. Otherwise it shall be 7. See Section C.8.20.2.1.</description>
      <section ref="C.8.20.2.1" name="">As a consequence of the enumerated Bits Allocated and Bits Stored attribute values, single bit pixels shall be packed 8 to a byte as defined by the encoding rules in PS 3.5.
</section>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1">
      <description>Specifies whether an Image has undergone lossy compression.
Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See Section C.8.20.2.2</description>
      <section ref="C.8.20.2.2" name="">If Lossy Image Compression (0028,2110) in any of the source images is “01”, the value shall be “01” for the Segmentation instance.
The process of segmentation itself is defined not to be lossy compression, even though it involves loss. If the Segmentation instance is encoded using a lossy compression transfer syntax, then the value shall be set to “01”.
Notes:  It is not advisable to lossy compress a Segmentation SOP Instance. In particular, a binary segmentation should not be lossy compressed.

</section>
    </entry>
    <entry group="0028" element="2112" name="Lossy Image Compression Ratio" type="1C">
      <description>Describes the approximate lossy compression ratio(s) that have been applied to this image.
See C.7.6.1.1.5 for further explanation. May be multivalued if successive lossy compression steps have been applied.
Notes: 1. For example, a compression ratio of 30:1 would be described in this Attribute with a single value of 30.
2. For historical reasons, the lossy compression ratio may also be described in Derivation Description (0008,2111).
Required if present in the source images or this IOD instance has been compressed.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2114" name="Lossy Image Compression Method" type="1C">
      <description>A label for the lossy compression method(s) that have been applied to this image.
See C.7.6.1.1.5 for further explanation. May be multivalued if successive lossy compression steps have been applied; the value order shall correspond to the values of Lossy Image Compression Ratio (0028,2112).
Note: For historical reasons, the lossy compression method may also be described in Derivation Description (0008,2111).
Required if present in the source images or this IOD instance has been compressed. See section C.8.20.2.2.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0062" element="0001" name="Segmentation Type" type="1">
      <description>The type of encoding used to indicate the presence of the segmented property at a pixel/voxel location.
Enumerated Values are:
BINARY
FRACTIONAL
See section C.8.20.2.3.</description>
    </entry>
    <entry group="0062" element="0010" name="Segmentation Fractional Type" type="1C">
      <description>For fractional segmentation encoding, the meaning of the fractional value.
Enumerated Values are:
PROBABILITY
OCCUPANCY
Required if Segmentation Type (0062,0001) is FRACTIONAL. See section C.8.20.2.3.</description>
    </entry>
    <entry group="0062" element="000E" name="Maximum Fractional Value" type="1C">
      <description>Specifies the value that represents 100%. There shall be no values in Pixel Data (7FE0,0010) greater than this value. Required if Segmentation Type (0062,0001) is FRACTIONAL.</description>
    </entry>
    <entry group="0062" element="0002" name="Segment Sequence" type="1">
      <description>Describes the segments that are contained within the data. One or more items shall be present.</description>
    </entry>
    <entry group="0062" element="0004" name="&gt;Segment Number" type="1">
      <description>Identification number of the segment. The value of Segment Number (0062,0004) shall be unique within the Segmentation instance in which it is created. See C.8.20.2.4.</description>
      <section ref="C.8.20.2.4" name="">Segment Number (0062,0004) shall be unique within each instance, start at a value of 1, and increase monotonically by 1.
</section>
    </entry>
    <entry group="0062" element="0005" name="&gt;Segment Label" type="1">
      <description>User-defined label identifying this segment. This may be the same as the Code Meaning (0008,0104) of the Segmented Property Type Code Sequence (0062,000F).</description>
    </entry>
    <entry group="0062" element="0006" name="&gt;Segment Description" type="3">
      <description>User-defined description for this segment.</description>
    </entry>
    <entry group="0062" element="0008" name="&gt;Segment Algorithm Type" type="1">
      <description>Type of algorithm used to generate the segment. Enumerated Values are:
AUTOMATIC: calculated segment
SEMIAUTOMATIC: calculated segment with user assistance
MANUAL: user-entered segment</description>
    </entry>
    <entry group="0062" element="0009" name="&gt;Segment Algorithm Name" type="1C">
      <description>Name of algorithm used to generate the segment. Required if Segment Algorithm Type (0062,0008) is not MANUAL.</description>
    </entry>
    <include ref="&gt;Include 'General Anatomy Mandatory Macro' Table 10-5"/>
    <entry group="0062" element="0003" name="&gt;Segmented Property Category Code Sequence" type="1">
      <description>Sequence defining the general category of this segment. This sequence shall contain a single item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 7150."/>
    <entry group="0062" element="000F" name="&gt;Segmented Property Type Code Sequence" type="1">
      <description>Sequence defining the specific property type of this segment. This sequence shall contain a single item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 7151."/>
    <entry group="0062" element="000C" name="&gt;Recommended Display Grayscale Value" type="3">
      <description>A default single gray unsigned value in which it is recommended that the maximum pixel value in this segment be rendered on a monochrome display. The units are specified in P-Values from a minimum of 0000H (black) up to a maximum of FFFFH (white).
Note: The maximum P-Value for this Attribute may be different from the maximum P-Value from the output of the Presentation LUT, which may be less than 16 bits in depth.</description>
    </entry>
    <entry group="0062" element="000D" name="&gt;Recommended Display CIELab Value" type="3">
      <description>A default triplet value in which it is recommended that segment be rendered on a color display. The units are specified in PCS-Values, and the value is encoded as CIELab. See C.10.7.1.1.</description>
      <section ref="C.10.7.1.1" name="">Attributes such as Graphic Layer Recommended Display CIELab Value (0070,0401) consist of three unsigned short values:
</section>
    </entry>
  </module>
  <macro table="C.8.20-3" name="Segmentation Macro Attributes">
    <entry group="0062" element="000A" name="Segment Identification Sequence" type="1">
      <description>Identifies the characteristics of this frame. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0062" element="000B" name="&gt;Referenced Segment Number" type="1">
      <description>Uniquely identifies the segment described in the Segment Sequence (0062,0002) by reference to the Segment Number (0062,0004). Referenced Segment Number (0062,000B) shall not be multi-valued.</description>
    </entry>
  </macro>
  <module ref="C.8.21.1" table="C.8.21.1-1" name="X Ray 3D Image Module Attributes">
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description>Image identification characteristics.
See C.8.21.1.1.1 for specialization.</description>
      <section ref="C.8.21.1.1.1" name="">In addition to the requirements specified in C.8.16.1 Image Type, the following additional requirements and Defined Terms are specified.
</section>
    </entry>
    <include ref="Include 'Common CT/MR Image Description Macro' Table C.8-131"/>
    <entry group="0028" element="0100" name="Bits Allocated" type="1">
      <description>Number of bits allocated for each voxel sample. Each sample shall have the same number of bits allocated. Enumerated Values: 8 and 16.</description>
    </entry>
    <entry group="0028" element="0101" name="Bits Stored" type="1">
      <description>Number of bits stored for each voxel sample. Each sample shall have the same number of bits stored. Enumerated Values: 8 to16.</description>
    </entry>
    <entry group="0028" element="0102" name="High Bit" type="1">
      <description>Most significant bit for pixel sample data. Each sample shall have the same high bit. Shall be one less than the value in Bits Stored (0028,0101).</description>
    </entry>
    <entry group="0028" element="0002" name="Samples per Pixel" type="1">
      <description>Number of samples (color planes) in this image shall have a value of 1.</description>
    </entry>
    <entry group="0028" element="0004" name="Photometric Interpretation" type="1">
      <description>Specifies the intended interpretation of the voxel data.
Enumerated Values:
MONOCHROME2</description>
    </entry>
    <entry group="0018" element="9004" name="Content Qualification" type="1">
      <description>Content Qualification Indicator
Enumerated Values:
PRODUCT
RESEARCH
SERVICE
See C.8.13.2.1.1 for further explanation.</description>
      <section ref="C.8.13.2.1.1" name="">Content Qualification (0018,9004) shall have the value PRODUCT if the content (image or Spectroscopy data) was produced with approved hardware and software. It shall have the value RESEARCH or SERVICE if there is any doubt as to whether the content was produced with approved hardware and software.
If data with Content Qualification (0018,9004) of RESEARCH or SERVICE is used to derive other content then it is expected that this derived content will also have Content Qualification (0018,9004) set to RESEARCH or SERVICE.
The intent of this element is to allow annotation of an advisory message that indicates that this content may not be suitable for clinical interpretation.
</section>
    </entry>
    <entry group="0028" element="0301" name="Burned In Annotation" type="1">
      <description>Indicates whether or not the image contains sufficient burned in annotation to identify the patient and date the image was acquired.
Enumerated Values:
NO</description>
    </entry>
    <entry group="0028" element="2110" name="Lossy Image Compression" type="1">
      <description>Specifies whether an Image has undergone lossy compression. Enumerated Values:
00 = Image has NOT been subjected to lossy compression.
01 = Image has been subjected to lossy compression.
See C.7.6.1.1.5 for further explanation.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2112" name="Lossy Image Compression Ratio" type="1C">
      <description>See C.7.6.1.1.5 for further explanation.
Required if Lossy Image Compression (0028,2110) equals 01.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0028" element="2114" name="Lossy Image Compression Method" type="1C">
      <description>A label for the lossy compression method(s) that have been applied to this image.
See C.7.6.1.1.5 for further explanation.
May be multi-valued if successive lossy compression steps have been applied; the value order shall correspond to the values of Lossy Image Compression Ratio (0028,2112).
Note: For historical reasons, the lossy compression method may also be described in Derivation Description (0008,2111).
Required if Lossy Image Compression (0028,2110) equals 01.</description>
      <section ref="C.7.6.1.1.5" name="">The Attribute Lossy Image Compression (0028,2110) conveys that the Image has undergone lossy compression. It provides a means to record that the Image has been compressed (at a point in its lifetime) with a lossy algorithm and changes have been introduced into the pixel data. Once the value has been set to “01”, it shall not be reset.
Note:  If an image is compressed with a lossy algorithm, the attribute Lossy Image Compression (0028,2110) is set to “01”. Subsequently, if the image is decompressed and transferred in uncompressed format, this attribute value remains “01”.

The value of the Lossy Image Compression (0028,2110) Attribute in SOP Instances containing multiple frames in which one or more of the frames have undergone lossy compression shall be “01”.
Note:  It is recommended that the applicable frames be noted in the Attribute Derivation Description (0008,2111).

If an image is originally obtained as a lossy compressed image from the sensor, then Lossy Image Compression (0028,2110) is set to “01” and Value 1 of the Attribute Image Type (0008,0008) shall be set to ORIGINAL.
If an image is a compressed version of another image, Lossy Image Compression (0028,2110) is set to “01”, Value 1 of the Attribute Image Type (0008,0008) shall be set to DERIVED, and if the predecessor was a DICOM image, then the Image shall receive a new SOP Instance UID.
Note:  1. It is recommended that the approximate compression ratio be provided in the Attribute Derivation Description (0008,2111). Furthermore, it is recommended that Derivation Description (0008,2111) be used to indicate when pixel data changes might affect professional interpretation. (see C.7.6.1.1.3).
  2. The attribute Lossy Image Compression (0028,2110) is defined as Type 3 for backward compatibility with existing IODs. It is expected to be required (i.e., defined as Type 1C) for new Image IODs and for existing IODs that undergo a major revision (e.g. a new IOD is specified).
The Defined Terms for Lossy Image Compression Method (0028,2114) are:
ISO_10918_1 = JPEG Lossy Compression
ISO_14495_1 = JPEG-LS Near-lossless Compression
ISO_15444_1 = JPEG 2000 Irreversible Compression
ISO_13818_2 = MPEG2 Compression

</section>
    </entry>
    <entry group="0008" element="9092" name="Referenced Image Evidence Sequence" type="1C">
      <description>Full set of Composite SOP Instances referred to inside the Referenced Image Sequences of this SOP Instance. See C.8.13.2.1.2 for further explanation.
One or more Items may be permitted in this sequence.
Required if the Referenced Image Sequence (0008,1140) is present.</description>
      <section ref="C.8.13.2.1.2" name="">The intent of the Referenced Image Evidence Sequence (0008,9092) and Source Image Evidence Sequence (0008,9154) is to provide a list of all unique SOP Instances listed in the Referenced Image Sequence (0008,1140) and Source Image Sequence (0008,2112) attributes respectively.
</section>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0020" element="4000" name="Image Comments" type="3">
      <description>User-defined comments about the image.</description>
    </entry>
    <entry group="0028" element="0300" name="Quality Control Image" type="3">
      <description>Indicates whether or not this image is a quality control or phantom image.
Enumerated Values:
YES
NO
If this Attribute is absent, then the image may or may not be a quality control or phantom image.</description>
    </entry>
    <entry group="0088" element="0200" name="Icon Image Sequence" type="3">
      <description>This icon image is representative of the Image.</description>
    </entry>
    <include ref="&gt; Include 'Image Pixel Macro' Table C.7-11b" description="See C.7.6.1.1.6 for further explanation."/>
    <entry group="2050" element="0020" name="Presentation LUT Shape" type="1">
      <description>Specifies a predefined identity transformation for the Presentation LUT such that the output of all grayscale transformations, if any, are defined to be in P-Values.
Enumerated Values:
IDENTITY = output is in P-Values</description>
    </entry>
  </module>
  <module ref="C.8.21.2.1" table="C.8.21.2.1-1" name="X Ray 3D Angiographic Image Contributing Sources Module Attributes">
    <entry group="0018" element="9506" name="Contributing Sources Sequence" type="1">
      <description>A sequence that describes characteristics of the sources that are used to create a derived SOP Instance.
One or more Items may be present.</description>
    </entry>
    <include ref="&gt;Include 'General Contributing Sources Macro' Table 10-13"/>
    <include ref="&gt;Include 'Contributing Image Source Macro' Table 10-14"/>
    <entry group="0018" element="1400" name="&gt;Acquisition Device Processing Description" type="1C">
      <description>Indicates any visual processing performed on the frame prior to exchange.
See Section C.8.7.1.1.3.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.8.7.1.1.3" name="">Acquisition Device Processing Description (0018,1400) provides some indication in human readable text of the digital processing on the images before exchange. Examples of this processing are: edge enhanced, subtracted, time filtered, gamma corrected, convolved (spatially filtered).
</section>
    </entry>
    <entry group="0018" element="1401" name="&gt;Acquisition Device Processing Code" type="1C">
      <description>Code representing the device-specific processing associated with the frame (e.g. Organ Filtering code)
Required if present and have an equal value in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="9457" name="&gt;Plane Identification" type="1C">
      <description>Identification of the plane used to acquire this image.
Defined Terms:
MONOPLANE
PLANE A
PLANE B
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="1164" name="&gt;Imager Pixel Spacing" type="1C">
      <description>Physical distance measured at the receptor plane of the detector between the centers of each pixel specified by a numeric pair - row spacing value (delimiter) column spacing value in mm.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
  </module>
  <module ref="C.8.21.2.2" table="C.8.21.2.2-1" name="X Ray 3D Craniofacial Image Contributing Sources Module Attributes">
    <entry group="0018" element="9506" name="Contributing Sources Sequence" type="1">
      <description>A sequence that describes characteristics of the sources that are used to create a derived SOP Instance.
One or more Items may be present.</description>
    </entry>
    <include ref="&gt;Include 'General Contributing Sources Macro' Table 10-13"/>
    <include ref="&gt;Include 'Contributing Image Source Macro' Table 10-14"/>
    <entry group="0018" element="1400" name="&gt;Acquisition Device Processing Description" type="1C">
      <description>Indicates any visual processing performed on the frame prior to exchange.
See Section C.8.7.1.1.3.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.8.7.1.1.3" name="">Acquisition Device Processing Description (0018,1400) provides some indication in human readable text of the digital processing on the images before exchange. Examples of this processing are: edge enhanced, subtracted, time filtered, gamma corrected, convolved (spatially filtered).
</section>
    </entry>
    <entry group="0018" element="1401" name="&gt;Acquisition Device Processing Code" type="1C">
      <description>Code representing the device-specific processing associated with the frame (e.g. Organ Filtering code).
Required if present and have an equal value in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="1164" name="&gt;Imager Pixel Spacing" type="1C">
      <description>Physical distance measured at the receptor plane of the detector between the centers of each pixel specified by a numeric pair - row spacing value (delimiter) column spacing value in mm.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
  </module>
  <macro table="C.8.21.3.1.1-1" name="X Ray 3D General Shared Acquisiton Macro">
    <entry group="0008" element="2112" name="Source Image Sequence" type="1C">
      <description>A Sequence that identifies the set of Images that constitute this acquisition context.
Required if the reconstruction is created from DICOM SOP Instances.
Note: The attribute is absent in the case where the images used to create the volume are not available as SOP Instances, e.g., the volume was directly generated by acquisition system.
One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0018" element="1147" name="Field of View Shape" type="1C">
      <description>Shape of the Field of View in the referenced images.
Enumerated Values:
RECTANGLE
ROUND
HEXAGONAL
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="9461" name="Field of View Dimension(s) in Float" type="1C">
      <description>Dimensions in mm of the Field of View in the referenced images. If Field of View Shape (0018,1147) is:
RECTANGLE: row dimension followed by column.
ROUND: diameter.
HEXAGONAL: diameter of the circle circumscribing the hexagon.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="7030" name="Field of View Origin" type="1C">
      <description>Offset of the TLHC of a rectangle circumscribing the Field of View in the referenced images, before rotation or flipping, from the TLHC of the physical detector area measured in physical detector pixels as a row offset followed by a column offset.
See C.8.11.4.1.1 for further explanation.
Required if X-Ray Receptor Type (0018,9420) is present and equals DIGITAL_DETECTOR.</description>
      <section ref="C.8.11.4.1.1" name="">The relationship between the Physical Detector Area, the Active Detector Area, the Field of View (what is stored in the Pixel Data (7FE0,0010)), the Exposed Area (after X-Ray Collimation) and the Displayed Area is illustrated in the following diagrams.
Note:  Some of these Attributes relate the image data to manufacturer specific characteristics of the detector that may be used for quality control purposes, e.g. correlation of image artifacts with a detector defect map, analysis of noise performance, etc.

The Displayed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the Display Shutter Module (see section C.7.6.11). If this Module is not present or supported, then the Displayed Area is equal to the Field of View.
The Exposed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the X-Ray Collimator Module (see section C.8.7.3).
For the Digital X-Ray IODs, the Field of View is usually rectangular in shape and the same size as the stored Pixel Data (7FE0,0010). The shape and size of the Field of View and the spacing of the pixels are defined by the following Attributes:
- Field of View Shape (0018,1147),
- Field of View Dimensions (0018,1149),
- Imager Pixel Spacing (0018,1164),
- Rows (0028,0010),
- Columns (0028,0011)

The following Attributes define the relationship of the Field of View to the Physical Detector Area:
- Field of View Origin (0018,7030),
- Field of View Rotation (0018,7032),
- Field of View Horizontal Flip (0018,7034).

For the Digital X-Ray IODs, the Active Area, i.e. that part of the detector matrix that was activated for this exposure, is usually rectangular in shape. The shape and size of the Active Area and the size and spacing of the detectors are defined by the following Attributes:
- Detector Active Shape (0018,7024),
- Detector Active Dimensions (0018,7026),
- Detector Element Physical Size (0018,7020),
- Detector Element Spacing (0018,7022).

Notes:  1. The Detector Element Physical Size (0018,7020) and Detector Element Spacing (0018,7022) may be different if there are insensitive regions between each detector.
  2. This model of description is not able to accurately describe multiple matrices of detectors that are “tiled” to produce a single image.

The following optional Attribute defines the relationship of the Active Area to the Physical Detector Area:
- Detector Active Origin (0018,7028).

The relationship between detectors and stored image pixels is defined by Detector Binning (0018,701A) which specifies how many detectors, in each of the row and column directions, contribute to (are pooled or averaged to form) a single stored image pixel.
Note:  Detector Binning (0018,701A) may have values less than one if sub-sampling is used to derive an image with higher spatial resolution than the detector matrix.



Figure C.8-14
Explanation of DX Detector Attributes




Figure C.8-15
Explanation of DX Detector Attributes
</section>
    </entry>
    <entry group="0018" element="7032" name="Field of View Rotation" type="1C">
      <description>Clockwise rotation in degrees of Field of View in the referenced images, relative to the physical detector.
Enumerated Values:
0, 90, 180, 270
See C.8.11.4.1.1 for further explanation.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.8.11.4.1.1" name="">The relationship between the Physical Detector Area, the Active Detector Area, the Field of View (what is stored in the Pixel Data (7FE0,0010)), the Exposed Area (after X-Ray Collimation) and the Displayed Area is illustrated in the following diagrams.
Note:  Some of these Attributes relate the image data to manufacturer specific characteristics of the detector that may be used for quality control purposes, e.g. correlation of image artifacts with a detector defect map, analysis of noise performance, etc.

The Displayed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the Display Shutter Module (see section C.7.6.11). If this Module is not present or supported, then the Displayed Area is equal to the Field of View.
The Exposed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the X-Ray Collimator Module (see section C.8.7.3).
For the Digital X-Ray IODs, the Field of View is usually rectangular in shape and the same size as the stored Pixel Data (7FE0,0010). The shape and size of the Field of View and the spacing of the pixels are defined by the following Attributes:
- Field of View Shape (0018,1147),
- Field of View Dimensions (0018,1149),
- Imager Pixel Spacing (0018,1164),
- Rows (0028,0010),
- Columns (0028,0011)

The following Attributes define the relationship of the Field of View to the Physical Detector Area:
- Field of View Origin (0018,7030),
- Field of View Rotation (0018,7032),
- Field of View Horizontal Flip (0018,7034).

For the Digital X-Ray IODs, the Active Area, i.e. that part of the detector matrix that was activated for this exposure, is usually rectangular in shape. The shape and size of the Active Area and the size and spacing of the detectors are defined by the following Attributes:
- Detector Active Shape (0018,7024),
- Detector Active Dimensions (0018,7026),
- Detector Element Physical Size (0018,7020),
- Detector Element Spacing (0018,7022).

Notes:  1. The Detector Element Physical Size (0018,7020) and Detector Element Spacing (0018,7022) may be different if there are insensitive regions between each detector.
  2. This model of description is not able to accurately describe multiple matrices of detectors that are “tiled” to produce a single image.

The following optional Attribute defines the relationship of the Active Area to the Physical Detector Area:
- Detector Active Origin (0018,7028).

The relationship between detectors and stored image pixels is defined by Detector Binning (0018,701A) which specifies how many detectors, in each of the row and column directions, contribute to (are pooled or averaged to form) a single stored image pixel.
Note:  Detector Binning (0018,701A) may have values less than one if sub-sampling is used to derive an image with higher spatial resolution than the detector matrix.



Figure C.8-14
Explanation of DX Detector Attributes




Figure C.8-15
Explanation of DX Detector Attributes
</section>
    </entry>
    <entry group="0018" element="7034" name="Field of View Horizontal Flip" type="1C">
      <description>Whether or not a horizontal flip has been applied to the Field of View in the referenced images, after rotation relative to the physical detector as described in Field of View Rotation (0018,7032).
Enumerated Values:
NO
YES
See C.8.11.4.1.1 for further explanation.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.8.11.4.1.1" name="">The relationship between the Physical Detector Area, the Active Detector Area, the Field of View (what is stored in the Pixel Data (7FE0,0010)), the Exposed Area (after X-Ray Collimation) and the Displayed Area is illustrated in the following diagrams.
Note:  Some of these Attributes relate the image data to manufacturer specific characteristics of the detector that may be used for quality control purposes, e.g. correlation of image artifacts with a detector defect map, analysis of noise performance, etc.

The Displayed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the Display Shutter Module (see section C.7.6.11). If this Module is not present or supported, then the Displayed Area is equal to the Field of View.
The Exposed Area is defined in pixel coordinates relative to the stored image pixel values by the Attributes of the X-Ray Collimator Module (see section C.8.7.3).
For the Digital X-Ray IODs, the Field of View is usually rectangular in shape and the same size as the stored Pixel Data (7FE0,0010). The shape and size of the Field of View and the spacing of the pixels are defined by the following Attributes:
- Field of View Shape (0018,1147),
- Field of View Dimensions (0018,1149),
- Imager Pixel Spacing (0018,1164),
- Rows (0028,0010),
- Columns (0028,0011)

The following Attributes define the relationship of the Field of View to the Physical Detector Area:
- Field of View Origin (0018,7030),
- Field of View Rotation (0018,7032),
- Field of View Horizontal Flip (0018,7034).

For the Digital X-Ray IODs, the Active Area, i.e. that part of the detector matrix that was activated for this exposure, is usually rectangular in shape. The shape and size of the Active Area and the size and spacing of the detectors are defined by the following Attributes:
- Detector Active Shape (0018,7024),
- Detector Active Dimensions (0018,7026),
- Detector Element Physical Size (0018,7020),
- Detector Element Spacing (0018,7022).

Notes:  1. The Detector Element Physical Size (0018,7020) and Detector Element Spacing (0018,7022) may be different if there are insensitive regions between each detector.
  2. This model of description is not able to accurately describe multiple matrices of detectors that are “tiled” to produce a single image.

The following optional Attribute defines the relationship of the Active Area to the Physical Detector Area:
- Detector Active Origin (0018,7028).

The relationship between detectors and stored image pixels is defined by Detector Binning (0018,701A) which specifies how many detectors, in each of the row and column directions, contribute to (are pooled or averaged to form) a single stored image pixel.
Note:  Detector Binning (0018,701A) may have values less than one if sub-sampling is used to derive an image with higher spatial resolution than the detector matrix.



Figure C.8-14
Explanation of DX Detector Attributes




Figure C.8-15
Explanation of DX Detector Attributes
</section>
    </entry>
    <entry group="0018" element="1166" name="Grid" type="1C">
      <description>Identifies the grid. May be multi-valued.
Defined Terms are:
FIXED
FOCUSED
RECIPROCATING
PARALLEL
CROSSED
NONE
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="9420" name="X-Ray Receptor Type" type="1C">
      <description>Identifies the type of X-Ray receptor used.
Enumerated Values:
IMG_INTENSIFIER
DIGITAL_DETECTOR
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="0060" name="KVP" type="1C">
      <description>Average of the peak kilo voltage outputs of the X-Ray generator used for all frames.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="9330" name="X-Ray Tube Current in mA" type="1C">
      <description>Average of the nominal X-Ray tube currents in milliamperes for all frames.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="9328" name="Exposure Time in ms" type="1C">
      <description>Duration of X-Ray exposure in milliseconds. See C.8.7.2.1.1.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.8.7.2.1.1" name="">Exposure time is the cumulative time the patient received X-Ray exposure during this image (Multi-frame image acquisition). Calculation is pulse width * number of frames.
</section>
    </entry>
    <entry group="0018" element="9332" name="Exposure in mAs" type="1C">
      <description>The exposure expressed in milliampereseconds, for example calculated from Exposure Time and X-Ray Tube Current.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="0010" name="Contrast/Bolus Agent" type="1C">
      <description>Contrast or bolus agent.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="0012" name="Contrast/Bolus Agent Sequence" type="1C">
      <description>Sequence that identifies the contrast agent. One or more Items may be present.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 12."/>
    <entry group="0018" element="9516" name="Start Acquisition DateTime" type="1C">
      <description>Start date and time of that part of an acquisition used for this acquisition context.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="9517" name="End Acquisition DateTime" type="1C">
      <description>End date and time of that part of an acquisition used for this acquisition context.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
  </macro>
  <macro table="C.8.21.3.1.2-1" name="X Ray 3D General Per Projection Acquisition Macro">
    <entry group="0018" element="0060" name="KVP" type="1C">
      <description>Exact peak kilo voltage output of the X-Ray generator used for this projection.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="9330" name="X-Ray Tube Current in mA" type="1C">
      <description>Exact Nominal X-Ray tube current in milliamperes applied during the Frame Acquisition Duration (0018,9220) for this projection.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="9220" name="Frame Acquisition Duration" type="1C">
      <description>The actual amount of time [in milliseconds] that was used to acquire data for this projection. See C.7.6.16.2.2.1 and C.7.6.16.2.2.3 for further explanation.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.7.6.16.2.2.1" name="">Figure C.7.6.16-2 shows the relationships among the various timing parameters used.
</section>
    </entry>
    <entry group="0018" element="1700" name="Collimator Shape" type="1C">
      <description>Shape(s) of the collimator. Enumerated Values:
RECTANGULAR
CIRCULAR
POLYGONAL
This multi-valued Attribute shall contain at most one of each Enumerated Value.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="1702" name="Collimator Left Vertical Edge" type="1C">
      <description>Required if Collimator Shape (0018,1700) is RECTANGULAR. Location of the left edge of the rectangular collimator with respect to pixels in the image given as column. See C.8.7.3.1.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1704" name="Collimator Right Vertical Edge" type="1C">
      <description>Required if Collimator Shape (0018,1700) is RECTANGULAR. Location of the right edge of the rectangular collimator with respect to pixels in the image given as column. See C.8.7.3.1.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1706" name="Collimator Upper Horizontal Edge" type="1C">
      <description>Required if Collimator Shape (0018,1700) is RECTANGULAR. Location of the upper edge of the rectangular collimator with respect to pixels in the image given as row. See C.8.7.3.1.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1708" name="Collimator Lower Horizontal Edge" type="1C">
      <description>Required if Collimator Shape (0018,1700) is RECTANGULAR. Location of the lower edge of the rectangular collimator with respect to pixels in the image given as row. See C.8.7.3.1.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1710" name="Center of Circular Collimator" type="1C">
      <description>Required if Collimator Shape (0018,1700) is CIRCULAR. Location of the center of the circular collimator with respect to pixels in the image given as row and column. See C.8.7.3.1.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1712" name="Radius of Circular Collimator" type="1C">
      <description>Required if Collimator Shape (0018,1700) is CIRCULAR. Radius of the circular collimator with respect to pixels in the image given as a number of pixels along the row direction. See C.8.7.3.1.1.</description>
      <section ref="C.8.7.3.1.1" name="">These attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator:
-  if the left edge of the collimator is not visible, Collimator Left Vertical Edge (0018,1702) shall have a value of 0;
-  if the right edge of the collimator is not visible, Collimator Right Vertical Edge (0018,1704) value shall be 1 greater than the value of the Columns (0028,0011) attribute;
-  if the top edge of the collimator is not visible, Collimator Upper Horizontal Edge (0018,1706) shall have a value of 0;
-  if the bottom edge of the collimator is not visible, Collimator Lower Horizontal Edge (0018,1708) value shall be 1 greater than the value of the Rows (0028,0010) attribute.

</section>
    </entry>
    <entry group="0018" element="1720" name="Vertices of the Polygonal Collimator" type="1C">
      <description>Required if Collimator Shape (0018,1700) is POLYGONAL.
Multiple Values where the first set of two values are:
row of the origin vertex;
column of the origin vertex.
Two or more pairs of values follow and are the row and column coordinates of the other vertices of the polygon collimator. Polygon collimators are implicitly closed from the last vertex to the origin vertex and all edges shall be non-intersecting except at the vertices.</description>
    </entry>
  </macro>
  <module ref="C.8.21.3.2" table="C.8.21.3.2-1" name="X Ray 3D Angiographic Acquisition Module Attributes">
    <entry group="0018" element="9507" name="X-Ray 3D Acquisition Sequence" type="1">
      <description>Each item represents an acquisition context related to one or more reconstructions.
The values of the Acquisition Index (0020,9518) attribute may be used as index to Items in this sequence.
One or more Items may be present.</description>
    </entry>
    <include ref="&gt;Include 'X-Ray 3D General Shared Acquisition Macro' Table C.8.215-1"/>
    <include ref="&gt;Include 'Digital X-Ray Detector Macro' Table C.8-71b"/>
    <entry group="0018" element="9429" name="&gt;Physical Detector Size" type="1C">
      <description>Dimensions of the physical detector measured in mm as a row size followed by a column size.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="9430" name="&gt;Position of Isocenter Projection" type="1C">
      <description>Position of the Isocenter measured in physical detector elements as a row offset followed by a column offset from the TLHC of a rectangle circumscribing the physical detector area.
Required if Isocenter Reference System Sequence (0018,9462) is present.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="1110" name="&gt;Distance Source to Detector" type="1C">
      <description>Distance from source to receptor plane perpendicular to the receptor plane in mm
or distance in mm from source to detector
center on the chest wall line See C.8.11.7.1.1.
Required if present and consistent in the contributing SOP Instances.
Note: This value is traditionally referred to as Source Image Receptor Distance (SID).</description>
      <section ref="C.8.11.7.1.1" name="">Figure C.8-8 shows the X-Ray beam for a digital mammography system. The X-Ray beam vector is defined from the Focal Spot to the center of the chest wall line of the Image Detection device.

Figure C.8-8
</section>
    </entry>
    <entry group="0018" element="9402" name="&gt;Distance Source to Isocenter" type="1C">
      <description>Distance from source to isocenter in mm.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="1190" name="&gt;Focal Spot" type="1C">
      <description>Nominal focal spot size in mm used to acquire this image.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="1160" name="&gt;Filter Type" type="1C">
      <description>Type of filter(s) inserted into the X-Ray beam (e.g. wedges).
Defined Terms:
STRIP
WEDGE
BUTTERFLY
MULTIPLE
NONE
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="7050" name="&gt;Filter Material" type="1C">
      <description>The X-Ray absorbing material used in the filter. May be multi-valued.
Defined Terms:
MOLYBDENUM
ALUMINUM
COPPER
RHODIUM
NIOBIUM
EUROPIUM
LEAD
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="7052" name="&gt;Filter Thickness Minimum" type="1C">
      <description>The minimum thickness in mm of the X-Ray absorbing material used in the filters. May be multi-valued, with values corresponding to the respective values in Filter Material (0018,7050).
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="7054" name="&gt;Filter Thickness Maximum" type="1C">
      <description>The maximum thickness in mm of the X-Ray absorbing material used in the filters. May be multi-valued, with values corresponding to the respective values in Filter Material (0018,7050).
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="9508" name="&gt;Primary Positioner Scan Arc" type="1C">
      <description>Total amount of rotation of the primary positioner in degrees.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="9510" name="&gt;Primary Positioner Scan Start Angle" type="1C">
      <description>Start position of the primary positioner in degrees. See C.8.7.5.1.2.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.8.7.5.1.2" name="">The definitions of Positioner Angles shall be with respect to the patient as illustrated in Figures C.8-11 and C.8-12 Zero degree is referenced to the origin perpendicular to the patient's chest. The Positioner Primary Angle definition is like longitude (in the equatorial plan); the Positioner Secondary Angle definition is like latitude (in the sagittal plane). The Positioner Angle attributes apply to the first frame of a multi-frame image. The valid range of Primary Positioner Angle is -180 to +180 degrees and the Secondary Positioner Angle range is -90 to + 90 degrees.
The Patient Plane is defined by the isocenter of the imaging device and slices through the patient such that it is perpendicular to the sagittal plane of the body. The Primary Axis of rotation is defined at the intersection of the Patient Plane and of the Sagittal Plane. The Positioner Primary Angle is defined in the transaxial plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest and + 90 degrees at the Patient left hand side (LAO) and -90 at the Patient right hand side (RAO). The valid range of Primary Positioner Angle is -180 to +180 degrees.
The Secondary Axis is in the Patient Plane and is perpendicular to the Primary Axis at the isocenter. The Positioner Secondary Angle is defined in the Sagittal Plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest. +90 degrees corresponds to the cranial direction. The Secondary Positioner Angle range is -90 to + 90 degrees.
At a 0 angle for both the Primary Angle (0018,1510) and Secondary Angle (0018,1511), the patient faces the Image Intensifier.
The Positioner Primary Angle (0018,1510) and Secondary Angle (0018,1511) apply to the first frame of a multi-frame image.

Figure C.8-11
Positioner Primary Angle

Figure C.8-12
Positioner Secondary Angle
</section>
    </entry>
    <entry group="0018" element="9514" name="&gt;Primary Positioner Increment" type="1C">
      <description>Nominal increment of the primary positioner angle in degrees. Positive values indicate moving from RAO to LAO position through the anterior. See C.8.7.5.1.2.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.8.7.5.1.2" name="">The definitions of Positioner Angles shall be with respect to the patient as illustrated in Figures C.8-11 and C.8-12 Zero degree is referenced to the origin perpendicular to the patient's chest. The Positioner Primary Angle definition is like longitude (in the equatorial plan); the Positioner Secondary Angle definition is like latitude (in the sagittal plane). The Positioner Angle attributes apply to the first frame of a multi-frame image. The valid range of Primary Positioner Angle is -180 to +180 degrees and the Secondary Positioner Angle range is -90 to + 90 degrees.
The Patient Plane is defined by the isocenter of the imaging device and slices through the patient such that it is perpendicular to the sagittal plane of the body. The Primary Axis of rotation is defined at the intersection of the Patient Plane and of the Sagittal Plane. The Positioner Primary Angle is defined in the transaxial plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest and + 90 degrees at the Patient left hand side (LAO) and -90 at the Patient right hand side (RAO). The valid range of Primary Positioner Angle is -180 to +180 degrees.
The Secondary Axis is in the Patient Plane and is perpendicular to the Primary Axis at the isocenter. The Positioner Secondary Angle is defined in the Sagittal Plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest. +90 degrees corresponds to the cranial direction. The Secondary Positioner Angle range is -90 to + 90 degrees.
At a 0 angle for both the Primary Angle (0018,1510) and Secondary Angle (0018,1511), the patient faces the Image Intensifier.
The Positioner Primary Angle (0018,1510) and Secondary Angle (0018,1511) apply to the first frame of a multi-frame image.

Figure C.8-11
Positioner Primary Angle

Figure C.8-12
Positioner Secondary Angle
</section>
    </entry>
    <entry group="0018" element="9509" name="&gt;Secondary Positioner Scan Arc" type="1C">
      <description>Total amount of rotation of the secondary positioner in degrees.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <entry group="0018" element="9511" name="&gt;Secondary Positioner Scan Start Angle" type="1C">
      <description>Start position of the secondary positioner in degrees. See C.8.7.5.1.2.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.8.7.5.1.2" name="">The definitions of Positioner Angles shall be with respect to the patient as illustrated in Figures C.8-11 and C.8-12 Zero degree is referenced to the origin perpendicular to the patient's chest. The Positioner Primary Angle definition is like longitude (in the equatorial plan); the Positioner Secondary Angle definition is like latitude (in the sagittal plane). The Positioner Angle attributes apply to the first frame of a multi-frame image. The valid range of Primary Positioner Angle is -180 to +180 degrees and the Secondary Positioner Angle range is -90 to + 90 degrees.
The Patient Plane is defined by the isocenter of the imaging device and slices through the patient such that it is perpendicular to the sagittal plane of the body. The Primary Axis of rotation is defined at the intersection of the Patient Plane and of the Sagittal Plane. The Positioner Primary Angle is defined in the transaxial plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest and + 90 degrees at the Patient left hand side (LAO) and -90 at the Patient right hand side (RAO). The valid range of Primary Positioner Angle is -180 to +180 degrees.
The Secondary Axis is in the Patient Plane and is perpendicular to the Primary Axis at the isocenter. The Positioner Secondary Angle is defined in the Sagittal Plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest. +90 degrees corresponds to the cranial direction. The Secondary Positioner Angle range is -90 to + 90 degrees.
At a 0 angle for both the Primary Angle (0018,1510) and Secondary Angle (0018,1511), the patient faces the Image Intensifier.
The Positioner Primary Angle (0018,1510) and Secondary Angle (0018,1511) apply to the first frame of a multi-frame image.

Figure C.8-11
Positioner Primary Angle

Figure C.8-12
Positioner Secondary Angle
</section>
    </entry>
    <entry group="0018" element="9515" name="&gt;Secondary Positioner Increment" type="1C">
      <description>Nominal increment of the secondary positioner angle in degrees. Positive values indicate moving from CAU to CRA through the anterior. See C.8.7.5.1.2.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.8.7.5.1.2" name="">The definitions of Positioner Angles shall be with respect to the patient as illustrated in Figures C.8-11 and C.8-12 Zero degree is referenced to the origin perpendicular to the patient's chest. The Positioner Primary Angle definition is like longitude (in the equatorial plan); the Positioner Secondary Angle definition is like latitude (in the sagittal plane). The Positioner Angle attributes apply to the first frame of a multi-frame image. The valid range of Primary Positioner Angle is -180 to +180 degrees and the Secondary Positioner Angle range is -90 to + 90 degrees.
The Patient Plane is defined by the isocenter of the imaging device and slices through the patient such that it is perpendicular to the sagittal plane of the body. The Primary Axis of rotation is defined at the intersection of the Patient Plane and of the Sagittal Plane. The Positioner Primary Angle is defined in the transaxial plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest and + 90 degrees at the Patient left hand side (LAO) and -90 at the Patient right hand side (RAO). The valid range of Primary Positioner Angle is -180 to +180 degrees.
The Secondary Axis is in the Patient Plane and is perpendicular to the Primary Axis at the isocenter. The Positioner Secondary Angle is defined in the Sagittal Plane at the isocenter with zero degrees in the direction perpendicular to the patient's chest. +90 degrees corresponds to the cranial direction. The Secondary Positioner Angle range is -90 to + 90 degrees.
At a 0 angle for both the Primary Angle (0018,1510) and Secondary Angle (0018,1511), the patient faces the Image Intensifier.
The Positioner Primary Angle (0018,1510) and Secondary Angle (0018,1511) apply to the first frame of a multi-frame image.

Figure C.8-11
Positioner Primary Angle

Figure C.8-12
Positioner Secondary Angle
</section>
    </entry>
    <entry group="0018" element="9538" name="&gt;Per Projection Acquisition Sequence" type="1C">
      <description>Sequence containing detailed acquisition context of each individual projection used in this acquisition context.
Zero or more items may be present.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <include ref="&gt;&gt;Include 'X-Ray 3D General Acquisition Per Projection Macro' Table C.8.215-2"/>
    <entry group="0018" element="9463" name="&gt;&gt;Positioner Isocenter Primary Angle" type="1C">
      <description>Position of the X-Ray center beam for this projection in the isocenter reference system in the X direction (deg).
See C.8.19.6.13.1.2 for further explanation.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.8.19.6.13.1.2" name="">The positioner coordinate system (Op, Xp, Yp, Zp) is defined as follows:
</section>
    </entry>
    <entry group="0018" element="9464" name="&gt;&gt;Positioner Isocenter Secondary Angle" type="1C">
      <description>Position of the X-Ray center beam for this projection in the isocenter reference system in the Z direction (deg).
See C.8.19.6.13.1.2 for further explanation.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.8.19.6.13.1.2" name="">The positioner coordinate system (Op, Xp, Yp, Zp) is defined as follows:
</section>
    </entry>
    <entry group="0018" element="9465" name="&gt;&gt;Positioner Isocenter Detector Rotation Angle" type="1C">
      <description>Rotation of the X-Ray detector plane for this projection (deg).
See C.8.19.6.13.1.2 for further explanation.
Required if present and consistent in the contributing SOP Instances.</description>
      <section ref="C.8.19.6.13.1.2" name="">The positioner coordinate system (Op, Xp, Yp, Zp) is defined as follows:
</section>
    </entry>
  </module>
  <module ref="C.8.21.3.3" table="C.8.21.3.3-1" name="X Ray 3D Craniofacial Acquisition Module Attributes">
    <entry group="0018" element="9507" name="X-Ray 3D Acquisition Sequence" type="1">
      <description>Each item represents a acquisition context related to a set of frames of SOP Instance defined by this IOD,
The values of the Acquisition Index (0020,9518) attribute may be used as index to Items in this sequence.
One or more Items may be present.</description>
    </entry>
    <include ref="&gt;Include 'X-Ray 3D General Shared Acquisition Macro' Table C.8.215-1"/>
    <include ref="&gt;Include 'Digital X-Ray Detector Macro' Table C.8-71b"/>
    <entry group="0018" element="9538" name="&gt;Per Projection Acquisition Sequence" type="1C">
      <description>Sequence containing detailed acquisition context of each individual projection used in this acquisition context.
Zero or more items may be present.
Required if present and consistent in the contributing SOP Instances.</description>
    </entry>
    <include ref="&gt;&gt;Include 'X-Ray 3D General Acquisition Per Projection Macro' Table C.8.215-2"/>
  </module>
  <module ref="C.8.21.4" table="C.8.21.4-1" name="X Ray 3D Reconstruction Module Attributes">
    <entry group="0018" element="9530" name="X-Ray 3D Reconstruction Sequence" type="1">
      <description>A sequence of Items each describing the characteristics of one 3D reconstruction included in this SOP instance.
One or more items may be present.</description>
    </entry>
    <entry group="0018" element="9531" name="&gt;Reconstruction Description" type="3">
      <description>Free text description of the purpose of the reconstruction, e.g., mask volume.</description>
    </entry>
    <entry group="0018" element="9524" name="&gt;Application Name" type="1">
      <description>Name of the application that created the reconstruction.</description>
    </entry>
    <entry group="0018" element="9525" name="&gt;Application Version" type="1">
      <description>Version of the application that created the reconstruction.</description>
    </entry>
    <entry group="0018" element="9526" name="&gt;Application Manufacturer" type="1">
      <description>Name of the manufacturer of the application that created the reconstruction.</description>
    </entry>
    <entry group="0018" element="9527" name="&gt;Algorithm Type" type="1">
      <description>Type of algorithm used to create the reconstruction.
Defined Terms:
FILTER_BACK_PROJ
ITERATIVE</description>
    </entry>
    <entry group="0018" element="9528" name="&gt;Algorithm Description" type="3">
      <description>Description of the algorithm used to create the reconstruction.</description>
    </entry>
    <entry group="0020" element="9518" name="&gt;Acquisition Index" type="1">
      <description>The Item number(s) of the X-Ray 3D Acquisition Sequence (0018,9507) that describes the acquisition context(s) contributing to this reconstruction.</description>
    </entry>
  </module>
  <macro table="C.8.21.5.1-1" name="X Ray 3D Frame Type Macro Attributes">
    <entry group="0018" element="9504" name="X-Ray 3D Frame Type Sequence" type="1">
      <description>A sequence that describes general characteristics of this frame.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <entry group="0008" element="9007" name="&gt;Frame Type" type="1">
      <description>Type of Frame. A multi-valued attribute analogous to the Image Type (0008,0008).
Enumerated Values and Defined Terms are the same as those for the four values of the Image Type (0008,0008) attribute, except that the value MIXED is not allowed. See C.8.16.1 and C.8.13.3.1.1.</description>
      <section ref="C.8.16.1" name="">The Image Type (0008,0008) and associated Image Type related attributes provide a high level description of a multi-frame SOP Instance. These attributes describe properties that provide key summary information to users of the SOP Instance. Image Type (0008,0008) contains the highest level summary of what is in the SOP Instance.
The Frame Type (0008,9007) attribute mirrors the corresponding Image Type attribute and applies to the frame level rather than to the image level.
If more than one value is used by the set of frames for a given Frame Type (0008,9007) attribute value or associated attribute value then the corresponding value of the Image Type (0008,0008) or associated attribute shall contain a value of MIXED. This indicates that a mixed set of values exists within the multi-frame SOP Instance.
The value MIXED shall only be used in the Image Type (0008,0008) when the corresponding values for the individual frames are not equal. When a value of an attribute is equal for all frames, the same value shall be used for the corresponding value of the Image Type (0008,0008). Values 2 and 3 of Image Type (0008,0008) are an exception to the rule for MIXED: Values 2 and 3 may never have the value of MIXED as described in sections C.8.16.1.2 and C.8.16.1.3.
Image Type (0008,0008) and Frame Type (0008,9007) shall consist of four non-zero length values.
</section>
    </entry>
    <include ref="&gt;Include Common CT/MR Image Description Macro' Table C.8-131"/>
    <entry group="0020" element="9536" name="&gt;Reconstruction Index" type="1">
      <description>The Item number of the X-Ray 3D Reconstruction Sequence (0018,9530) that describes the characteristics of the 3D Reconstruction to which this frame is part of.</description>
    </entry>
  </macro>
  <module ref="C.9.2" table="C.9-2" name="Overlay Plane Module Attributes">
    <entry group="60xx" element="0010" name="Overlay Rows" type="1">
      <description>Number of Rows in Overlay.</description>
    </entry>
    <entry group="60xx" element="0011" name="Overlay Columns" type="1">
      <description>Number of Columns in Overlay.</description>
    </entry>
    <entry group="60xx" element="0040" name="Overlay Type" type="1">
      <description>Indicates whether this overlay represents a region of interest or other graphics. Enumerated Values:
G = Graphics
R = ROI.</description>
    </entry>
    <entry group="60xx" element="0050" name="Overlay Origin" type="1">
      <description>Location of first overlay point with respect to pixels in the image, given as row\column.
The upper left pixel of the image has the coordinate 1\1.
Column values greater than 1 indicate the overlay plane origin is to the right of the image origin. Row values greater than 1 indicate the overlay plane origin is below the image origin. Values less than 1 indicate the overlay plane origin is above or to the left of the image origin.
Note: Values of 0\0 indicate that the overlay pixels start 1 row above and one column to the left of the image pixels.</description>
    </entry>
    <entry group="60xx" element="0100" name="Overlay Bits Allocated" type="1">
      <description>Number of Bits Allocated in the Overlay.
Tthe value of this Attribute shall be 1.
Note: Formerly the standard described embedding the overlay data in the Image Pixel Data (7FE0,0010), in which case the value of this Attribute was required to be the same as Bits Allocated (0028,0100). This usage has been retired. See PS 3.3 2004.</description>
    </entry>
    <entry group="60xx" element="0102" name="Overlay Bit Position" type="1">
      <description>The value of this Attribute shall be 0.
Note: Formerly the standard described embedding the overlay data in the Image Pixel Data (7FE0,0010), in which case the value of this Attribute specified the bit in which the overlay was stored. This usage has been retired. See PS 3.3 2004.</description>
    </entry>
    <entry group="60xx" element="3000" name="Overlay Data" type="1">
      <description>Overlay pixel data.
The order of pixels sent for each overlay is left to right, top to bottom, i.e., the upper left pixel is sent first followed by the remainder of the first row , followed by the first pixel of the 2nd row, then the remainder of the 2nd row and so on.
Overlay data shall be contained in this Attribute .
See C.9.2.1.1 for further explanation.</description>
      <section ref="C.9.2.1.1" name="">There are two specific types of overlays. The type is specified in this Attribute.
A Region of Interest (ROI) is a specific use of an Overlay. The overlay bits corresponding to all the pixels included in the ROI shall be set to 1. All other bits are set to 0. This is used to specify an area of the image of particular interest.
A Graphics overlay may express reference marks, graphic annotation, or bit mapped text, etc. A Graphics overlay may be used to mark the boundary of a ROI. If this is the case and the ROI statistical parameters are used, they will only refer to the pixels under the boundaries, not those in the included regions.
The overlay bits corresponding to all the pixels included in the Graphics shall be set to 1. All other bits are set to 0.
</section>
    </entry>
    <entry group="60xx" element="0022" name="Overlay Description" type="3">
      <description>User-defined comments about the overlay.</description>
    </entry>
    <entry group="60xx" element="0045" name="Overlay Subtype" type="3">
      <description>Defined term which identifies the intended purpose of the Overlay Type. See C.9.2.1.3 for further explanation.</description>
      <section ref="C.9.2.1.3" name="">Two Defined Terms are specified:
USER - User created graphic annotation (e.g. operator)
AUTOMATED - Machine or algorithm generated graphic annotation, such as output of a Computer Assisted Diagnosis algorithm.

Note:  Additional or alternative Defined Terms may be specified in modality specific Modules, such as in the Ultrasound Image Module, C.8.5.6.1.11.

</section>
    </entry>
    <entry group="60xx" element="1500" name="Overlay Label" type="3">
      <description>A user defined text string which may be used to label or name this overlay.</description>
    </entry>
    <entry group="60xx" element="1301" name="ROI Area" type="3">
      <description>Number of pixels in ROI area.
See C.9.2.1.2 for further explanation.</description>
      <section ref="C.9.2.1.2" name="">These Attributes contain the statistical parameters of the ROI. The values of these parameters are for the overlay pixel values set to 1.
</section>
    </entry>
    <entry group="60xx" element="1302" name="ROI Mean" type="3">
      <description>ROI Mean.
See C.9.2.1.2 for further explanation.</description>
      <section ref="C.9.2.1.2" name="">These Attributes contain the statistical parameters of the ROI. The values of these parameters are for the overlay pixel values set to 1.
</section>
    </entry>
    <entry group="60xx" element="1303" name="ROI Standard Deviation" type="3">
      <description>ROI standard deviation.
See C.9.2.1.2 for further explanation.</description>
      <section ref="C.9.2.1.2" name="">These Attributes contain the statistical parameters of the ROI. The values of these parameters are for the overlay pixel values set to 1.
</section>
    </entry>
  </module>
  <module ref="C.9.3" table="C.9-3" name="Multi Frame Overlay Module Attributes">
    <entry group="60xx" element="0015" name="Number of Frames in Overlay" type="1">
      <description>Number of Frames in Overlay. Required if Overlay data contains multiple frames.</description>
    </entry>
    <entry group="60xx" element="0051" name="Image Frame Origin" type="3">
      <description>Frame number of Multi-frame Image to which this overlay applies; frames are numbered from 1.</description>
    </entry>
  </module>
  <module ref="C.10.4" table="C.10-4" name="Displayed Area Module Attributes">
    <entry group="0070" element="005A" name="Displayed Area Selection Sequence" type="1">
      <description>A sequence of Items each of which describes the displayed area selection for a group of images or frames. Sufficient Items shall be present to describe every image and frame listed in the Presentation State Relationship Module.
One or more Items shall be present.</description>
    </entry>
    <entry group="0008" element="1140" name="&gt;Referenced Image Sequence" type="1C">
      <description>Sequence of Items where each Item provides reference to a selected set of Image SOP Class/SOP Instance pairs that are defined in the Presentation State Relationship Module. One or more Items shall be present.
Requiredif the displayed area selection in this Item does not apply to all the images and frames listed in the Presentation State Relationship Module.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0070" element="0052" name="&gt;Displayed Area Top Left Hand Corner" type="1">
      <description>The top left (after spatial transformation) pixel in the referenced image to be displayed, given as column\row. Column is the horizontal (before spatial transformation) offset (X) and row is the vertical (before spatial transformation) offset (Y) relative to the origin of the pixel data before spatial transformation, which is 1\1. See Figure C.10.4-1.</description>
    </entry>
    <entry group="0070" element="0053" name="&gt;Displayed Area Bottom Right Hand Corner" type="1">
      <description>The bottom right (after spatial transformation) pixel in the referenced image to be displayed, given as column\row. Column is the horizontal (before spatial transformation) offset (X) and row is the vertical (before spatial transformation) offset (Y) relative to the origin of the pixel data before spatial transformation, which is 1\1. See Figure C.10.4-1.</description>
    </entry>
    <entry group="0070" element="0100" name="&gt;Presentation Size Mode" type="1">
      <description>Manner of selection of display size.
Enumerated Values:
SCALE TO FIT
TRUE SIZE
MAGNIFY
See C.10.4 for further explanation.</description>
    </entry>
    <entry group="0070" element="0101" name="&gt;Presentation Pixel Spacing" type="1C">
      <description>Physical distance between the center of each pixel in the referenced image (before spatial transformation), specified by a numeric pair - adjacent row spacing (delimiter) adjacent column spacing in mm. See 10.7.1.3 for further explanation of the value order.
Notes: 1. This value may be different from Pixel Spacing (0028,0030) or Imager Pixel Spacing (0018,1164) specified in the referenced image, which are ignored, since some form of calibration may have been performed (for example by reference to an object of known size in the image).
2. If the row and column spacing are different, then the pixel aspect ratio of the image is not 1:1.
Required if Presentation Size Mode (0070,0100) is TRUE SIZE, in which case the values will correspond to the physical distance between the center of each pixel on the display device.
May be present if Presentation Size Mode (0070,0100) is SCALE TO FIT or MAGNIFY, in which case the values are used to compute the aspect ratio of the image pixels.</description>
    </entry>
    <entry group="0070" element="0102" name="&gt;Presentation Pixel Aspect Ratio" type="1C">
      <description>Ratio of the vertical size and the horizontal size of the pixels in the referenced image, to be used to display the referenced image, specified by a pair of integer values where the first value is the vertical pixel size and the second value is the horizontal pixel size. See C.7.6.3.1.7.
Required if Presentation Pixel Spacing (0070,0101) is not present.
Notes: 1. This value may be different from the aspect ratio specified by Pixel Aspect Ratio (0028,0034) in the referenced image, or implied by the values of Pixel Spacing (0028,0030) or Imager Pixel Spacing (0018,1164) specified in the referenced image, which are ignored.
2. This value must be specified even if the aspect ratio is 1:1.</description>
      <section ref="C.7.6.3.1.7" name="">The pixel aspect ratio is the ratio of the vertical size and horizontal size of the pixels in the image specified by a pair of integer values where the first value is the vertical pixel size, and the second value is the horizontal pixel size. To illustrate, consider the following example pixel size:

Pixel Aspect Ratio = Vertical Size \ Horizontal Size = 0.30 mm \0.25 mm. Thus the Pixel Aspect Ratio could be represented as the multivalued integer string "6\5", "60\50", or any equivalent integer ratio.
</section>
    </entry>
    <entry group="0070" element="0103" name="&gt;Presentation Pixel Magnification Ratio" type="1C">
      <description>Ratio of displayed pixels to source pixels, specified in one dimension.
Required if Presentation Size Mode (0070,0100) is MAGNIFY.
Notes: 1. A value of 1.0 would imply that one pixel in the referenced image would be displayed as one pixel on the display (i.e. it would not be interpolated if the aspect ratio of the image pixels is 1:1).
2. A value of 2.0 would imply that one pixel in the referenced image would be displayed as 4 pixels on the display (i.e. up-sampled by a factor of 2 in each of the row and column directions).
3. A value of 0.5 would imply that 4 pixels in the referenced image would be displayed as 1 pixel on the display (i.e. down-sampled by a factor of 2 in each of the row and column directions).
4. If the source pixels have an aspect ratio of other than 1:1, then they are assumed to have been interpolated to a display pixel aspect ratio of 1:1 prior to magnification.</description>
    </entry>
  </module>
  <module ref="C.10.5" table="C.10-5" name="Graphic Annotation Module Attributes">
    <entry group="0070" element="0001" name="Graphic Annotation Sequence" type="1">
      <description>A sequence of Items each of which represents a group of annotations composed of graphics or text or both.
One or more Items shall be present.</description>
    </entry>
    <entry group="0008" element="1140" name="&gt;Referenced Image Sequence" type="1C">
      <description>Sequence of Items where each Item provides reference to a selected set of Image SOP Class/SOP Instance pairs that are defined in the Presentation State Relationship Module. One or more Items shall be present.
Required if graphic annotations in this Item do not apply to all the images and frames listed in the Presentation State Relationship Module.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0070" element="0002" name="&gt;Graphic Layer" type="1">
      <description>The layer defined in the Graphic Layer Module C.10.7 in which the graphics or text is to be rendered.</description>
    </entry>
    <entry group="0070" element="0008" name="&gt;Text Object Sequence" type="1C">
      <description>Sequence that describes a text annotation. One or more Items may be present.
Either one or both of Text Object Sequence (0070,0008) or Graphic Object Sequence (0070,0009) are required .</description>
    </entry>
    <entry group="0070" element="0003" name="&gt;&gt;Bounding Box Annotation Units" type="1C">
      <description>Units of measure for the axes of the text bounding box.
Defines whether or not the annotation is Image or Displayed Area relative. Both dimensions shall have the same units.
Enumerated Values:
PIXEL = Image relative position specified with sub-pixel resolution such that the origin at the Top Left Hand Corner (TLHC) of the TLHC pixel is 0.0\0.0, the Bottom Right Hand Corner (BRHC) of the TLHC pixel is 1.0\1.0, and the BRHC of the BRHC pixel is Columns\Rows (see figure C.10.5-1). The values must be within the range 0\0 to Columns\Rows.
DISPLAY = Fraction of Specified Displayed Area where 0.0\0.0 is the TLHC and 1.0\1.0 is the BRHC. The values must be within the range 0.0 to 1.0.
Required if Bounding Box Top Left Hand Corner (0070,0010) or Bounding Box Bottom Right Hand Corner (0070,0011) is present.</description>
    </entry>
    <entry group="0070" element="0004" name="&gt;&gt;Anchor Point Annotation Units" type="1C">
      <description>Units of measure for the axes of the text anchor point annotation.
Enumerated Values for Anchor Point Annotation Units (0070,0004) are the same as for Bounding Box Annotation Units (0070,0003).
Required if Anchor Point (0070,0014) is present.</description>
    </entry>
    <entry group="0070" element="0006" name="&gt;&gt;Unformatted Text Value" type="1">
      <description>Text data which is unformatted and whose manner of display within the defined bounding box or relative to the specified anchor point is implementation dependent. See C.10.5.1.1.
The text value may contain spaces, as well as multiple lines separated by either LF, CR, CR LF or LF CR, but otherwise no format control characters (such as horizontal or vertical tab and form feed) shall be present, even if permitted by the Value Representation of ST.
The text shall be interpreted as specified by Specific Character Set (0008,0005) if present in the SOP Common Module.
Note: The text may contain single or multi-byte characters and use code extension techniques as described in PS 3.5 if permitted by the values of Specific Character Set (0008,0005).</description>
      <section ref="C.10.5.1.1" name="">The text shall be displayed if any part of the bounding box or anchor point is within the Specified Display Area.
The text need not be confined to within the bounding box, but shall be rendered in a direction from the Top Left Hand Corner (TLHC) of the bounding box to the Bottom Right Hand Corner (BRHC) of the bounding box, even if these coordinates have been specified in an image relative space and then transformed (rotated, flipped or scaled).
Notes:  1. An implementation may render text outside the confines of the bounding box if necessary to display all the specified text.
  2. Alternatively, an implementation may choose to render the text in a scrolling box, or a link to another fixed or popup window as appropriate.

Whether the contents of the bounding box completely opacify the underlying image or whether the box is “transparent” is undefined.
Notes:  1. For example, an implementation may choose an “exclusive or” style opacification to be sure that the text is discernible over light and dark portions of the image.
  2. Commonly, the region of the bounding box around the text will be rendered “transparently”, i.e. the image will be visible, though some implementations may choose to opacify the bounding box behind the text to improve its readability.

An alternative to specifying a bounding box, is to specify an Anchor Point (0070,0014), i.e. some point in an image or Specified Displayed Area that is related to the text. The semantics of this relationship, and the manner of positioning or linking the text to this point, are unspecified.
Notes:  1. For example, a description of a feature may be linked to a point in the image, and when that image is displayed, if it is magnified and panned, the rendered text (and any arrow or line drawn in response to Anchor Point Visibility (0070,0015)) might be repositioned as appropriate so as not to be cropped out of the Specified Displayed Area.
  2. As another example, the text could be rendered in a pop-up window when a hypertext link flagged on the displayed image at the location of the Anchor Point (0070,0014) is selected.
  3. The bounding box and anchor point need not be defined with the same axis units, i.e. one can be image pixel relative, and the other displayed area relative.

The size, font and rotation of the individual rendered text characters are unspecified.
</section>
    </entry>
    <entry group="0070" element="0010" name="&gt;&gt;Bounding Box Top Left Hand Corner" type="1C">
      <description>Location of the Top Left Hand Corner (TLHC) of the bounding box in which Unformatted Text Value (0070,0006) is to be displayed, in Bounding Box Annotation Units (0070,0003), given as column\row. Column is the horizontal offset and row is the vertical offset.
Required if Anchor Point (0070,0014) is not present.</description>
    </entry>
    <entry group="0070" element="0011" name="&gt;&gt;Bounding Box Bottom Right Hand Corner" type="1C">
      <description>Location of the Bottom Right Hand Corner (BRHC) of the bounding box in which Unformatted Text Value (0070,0006) is to be displayed, in Bounding Box Annotation Units (0070,0003), given as column\row. Column is the horizontal offset and row is the vertical offset.
Required if Anchor Point (0070,0014) is not present.</description>
    </entry>
    <entry group="0070" element="0012" name="&gt;&gt;Bounding Box Text Horizontal Justification" type="1C">
      <description>Location of the text relative to the vertical edges of the bounding box. Enumerated Values:
LEFT = closest to left edge
RIGHT = closest to right edge
CENTER = centered
Required if Bounding Box Top Left Hand Corner (0070,0010) is present.</description>
    </entry>
    <entry group="0070" element="0014" name="&gt;&gt;Anchor Point" type="1C">
      <description>Location of a point in the image or Specified Displayed Area to which the Unformatted Text Value (0070,0006) is related, in Anchor Point Annotation Units (0070,0004), given as column\row. Column is the horizontal offset and row is the vertical offset.
Required if Bounding Box Top Left Hand Corner (0070,0010) and Bounding Box Bottom Right Hand Corner (0070,0011) are not present.
May be present even if a bounding box is specified (i.e. Bounding Box Top Left Hand Corner (0070,0010) and Bounding Box Bottom Right Hand Corner (0070,0011) are present).</description>
    </entry>
    <entry group="0070" element="0015" name="&gt;&gt;Anchor Point Visibility" type="1C">
      <description>Flag to indicate whether or not a visible indication (such as a line or arrow) of the relationship between the text and the anchor point is to be displayed.
Enumerated Values:
Y = yes
N = no
Required if Anchor Point (0070,0014) is present.</description>
    </entry>
    <entry group="0070" element="0009" name="&gt;Graphic Object Sequence" type="1C">
      <description>Sequence that describes a graphic annotation. One or more Items may be present.
Either one or both of Text Object Sequence (0070,0008) or Graphic Object Sequence (0070,0009) are required.</description>
    </entry>
    <entry group="0070" element="0005" name="&gt;&gt;Graphic Annotation Units" type="1">
      <description>Units of measure for the axes of the graphic annotation.
Enumerated Values for Graphic Annotation Units (0070,0005) are the same as for Bounding Box Annotation Units (0070,0003).</description>
    </entry>
    <entry group="0070" element="0020" name="&gt;&gt;Graphic Dimensions" type="1">
      <description>Enumerated Value: 2</description>
    </entry>
    <entry group="0070" element="0021" name="&gt;&gt;Number of Graphic Points" type="1">
      <description>Number of data points in this graphic.</description>
    </entry>
    <entry group="0070" element="0022" name="&gt;&gt; Graphic Data" type="1">
      <description>Coordinates that specify this graphic annotation.
See C.10.5.1.2 for further explanation.</description>
      <section ref="C.10.5.1.2" name="">Graphic Data (0070,0022) contains the points in the graphic annotation, each dimension for the first point, followed by dimensions for second point, etc. For a two dimensional curve: X1, Y1, X2, Y2, etc. The first (X) dimension corresponds to the image or Specified Displayed Area column (horizontal offset), and the second (Y) dimension corresponds to the image or Specified Displayed Area row (vertical offset). The Value Representation of all components of the N-tuple shall be the same. The image or Specified Displayed Area relative drawing space is defined in Graphic Annotation Units (0070,0005).
If Graphic Type (0070,0023) is POINT, then two values (one point) shall be specified and the single point specified is to be drawn.
If Graphic Type (0070,0023) is POLYLINE, then the points are to be interpreted as an n-tuple list of end points between which straight lines are to be drawn.
If Graphic Type (0070,0023) is INTERPOLATED, then the points are to be interpreted as an n-tuple list of end points between which some form of implementation dependent curved lines are to be drawn. The rendered line shall pass through all the specified points.
If Graphic Type (0070,0023) is CIRCLE, then exactly two points shall be present; the first point is to be interpreted as the center and the second point as a point on the circumference of a circle, some form of implementation dependent representation of which is to be drawn.
If Graphic Type (0070,0023) is ELLIPSE, then exactly four points shall be present; the first two points are to be interpreted as the endpoints of the major axis and the second two points as the endpoints of the minor axis of an ellipse, some form of implementation dependent representation of which is to be drawn.
The notion of “open” or “closed” has no inherent meaning in the context of an arbitrary graphic, other than in the condition for the presence of Graphic Filled (0070,0024). The graphic has no semantic notion of an associated observation such as a region of interest, except that which the unformatted text in the same Item may describe.
The choice of pixel value used to represent the graphic on a display is defined in the Graphic Layer Module C.10.7.

Figure C.10.5-1
Sub-pixel Addressing Units in PIXEL Space
</section>
    </entry>
    <entry group="0070" element="0023" name="&gt;&gt;Graphic Type" type="1">
      <description>The shape of graphic that is to be drawn. See C.10.5.1.2.
Enumerated Values:
POINT
POLYLINE
INTERPOLATED
CIRCLE
ELLIPSE</description>
      <section ref="C.10.5.1.2" name="">Graphic Data (0070,0022) contains the points in the graphic annotation, each dimension for the first point, followed by dimensions for second point, etc. For a two dimensional curve: X1, Y1, X2, Y2, etc. The first (X) dimension corresponds to the image or Specified Displayed Area column (horizontal offset), and the second (Y) dimension corresponds to the image or Specified Displayed Area row (vertical offset). The Value Representation of all components of the N-tuple shall be the same. The image or Specified Displayed Area relative drawing space is defined in Graphic Annotation Units (0070,0005).
If Graphic Type (0070,0023) is POINT, then two values (one point) shall be specified and the single point specified is to be drawn.
If Graphic Type (0070,0023) is POLYLINE, then the points are to be interpreted as an n-tuple list of end points between which straight lines are to be drawn.
If Graphic Type (0070,0023) is INTERPOLATED, then the points are to be interpreted as an n-tuple list of end points between which some form of implementation dependent curved lines are to be drawn. The rendered line shall pass through all the specified points.
If Graphic Type (0070,0023) is CIRCLE, then exactly two points shall be present; the first point is to be interpreted as the center and the second point as a point on the circumference of a circle, some form of implementation dependent representation of which is to be drawn.
If Graphic Type (0070,0023) is ELLIPSE, then exactly four points shall be present; the first two points are to be interpreted as the endpoints of the major axis and the second two points as the endpoints of the minor axis of an ellipse, some form of implementation dependent representation of which is to be drawn.
The notion of “open” or “closed” has no inherent meaning in the context of an arbitrary graphic, other than in the condition for the presence of Graphic Filled (0070,0024). The graphic has no semantic notion of an associated observation such as a region of interest, except that which the unformatted text in the same Item may describe.
The choice of pixel value used to represent the graphic on a display is defined in the Graphic Layer Module C.10.7.

Figure C.10.5-1
Sub-pixel Addressing Units in PIXEL Space
</section>
    </entry>
    <entry group="0070" element="0024" name="&gt;&gt;Graphic Filled" type="1C">
      <description>Whether or not the closed graphics element is displayed as filled (in some unspecified manner that shall be distinguishable from an outline) or as an outline. See C.10.5.1.2.
Enumerated Values:
Y = yes
N = no
Required if Graphic Data (0070,0022) is "closed", that is Graphic Type (0070,0023) is CIRCLE or ELLIPSE, or Graphic Type (0070,0023) is POLYLINE or INTERPOLATED and the first data point is the same as the last data point.</description>
      <section ref="C.10.5.1.2" name="">Graphic Data (0070,0022) contains the points in the graphic annotation, each dimension for the first point, followed by dimensions for second point, etc. For a two dimensional curve: X1, Y1, X2, Y2, etc. The first (X) dimension corresponds to the image or Specified Displayed Area column (horizontal offset), and the second (Y) dimension corresponds to the image or Specified Displayed Area row (vertical offset). The Value Representation of all components of the N-tuple shall be the same. The image or Specified Displayed Area relative drawing space is defined in Graphic Annotation Units (0070,0005).
If Graphic Type (0070,0023) is POINT, then two values (one point) shall be specified and the single point specified is to be drawn.
If Graphic Type (0070,0023) is POLYLINE, then the points are to be interpreted as an n-tuple list of end points between which straight lines are to be drawn.
If Graphic Type (0070,0023) is INTERPOLATED, then the points are to be interpreted as an n-tuple list of end points between which some form of implementation dependent curved lines are to be drawn. The rendered line shall pass through all the specified points.
If Graphic Type (0070,0023) is CIRCLE, then exactly two points shall be present; the first point is to be interpreted as the center and the second point as a point on the circumference of a circle, some form of implementation dependent representation of which is to be drawn.
If Graphic Type (0070,0023) is ELLIPSE, then exactly four points shall be present; the first two points are to be interpreted as the endpoints of the major axis and the second two points as the endpoints of the minor axis of an ellipse, some form of implementation dependent representation of which is to be drawn.
The notion of “open” or “closed” has no inherent meaning in the context of an arbitrary graphic, other than in the condition for the presence of Graphic Filled (0070,0024). The graphic has no semantic notion of an associated observation such as a region of interest, except that which the unformatted text in the same Item may describe.
The choice of pixel value used to represent the graphic on a display is defined in the Graphic Layer Module C.10.7.

Figure C.10.5-1
Sub-pixel Addressing Units in PIXEL Space
</section>
    </entry>
  </module>
  <module ref="C.10.6" table="C.10-6" name="Spatial Transformation Module Attributes">
    <entry group="0070" element="0042" name="Image Rotation" type="1">
      <description>How far to rotate the image clockwise in degrees, before any Image Horizontal Flip (0070,0041) is applied.
Enumerated Values:
0, 90,180,270
Notes: Negative values are not permitted since the Value Representation is unsigned.</description>
    </entry>
    <entry group="0070" element="0041" name="Image Horizontal Flip" type="1">
      <description>Whether or not to flip the image horizontally after any Image Rotation has been applied such that the left side of the image becomes the right side.
Enumerated Values:
Y = yes,
N = no
Note: No vertical flip is specified since the same result can be achieved by a combination of a 180 degree rotation and a horizontal flip.</description>
    </entry>
  </module>
  <module ref="C.10.7" table="C.10-7" name="Graphic Layer Module Attributes">
    <entry group="0070" element="0060" name="Graphic Layer Sequence" type="1">
      <description>A sequence of Items each of which represents a single layer in which overlays, curves, graphics or text may be rendered.
One or more Items shall be present. An Item is required for each layer referenced from the Graphic Annotation Module or the Overlay Activation Module.</description>
    </entry>
    <entry group="0070" element="0002" name="&gt;Graphic Layer" type="1">
      <description>A string which identifies the layer.
Note: This identifier may be used by other Attributes within the same presentation state instance to reference this layer. There is no requirement for the same identifiers to be used in different presentation states, and there is no mechanism for referencing layers in other presentation states. That is, a UID is not required.</description>
    </entry>
    <entry group="0070" element="0062" name="&gt;Graphic Layer Order" type="1">
      <description>An integer indicating the order in which it is recommended that the layer be rendered, if the display is capable of distinguishing. Lower numbered layers are to be rendered first.</description>
    </entry>
    <entry group="0070" element="0066" name="&gt;Graphic Layer Recommended Display Grayscale Value" type="3">
      <description>A default single gray unsigned value in which it is recommended that the layer be rendered on a monochrome display. The units are specified in P-Values from a minimum of 0000H (black) up to a maximum of FFFFH (white).
Note: The maximum P-Value for this Attribute may be different from the maximum P-Value from the output of the Presentation LUT, which may be less than 16 bits in depth.</description>
    </entry>
    <entry group="0070" element="0401" name="&gt;Graphic Layer Recommended Display CIELab Value" type="3">
      <description>A default color triplet value in which it is recommended that the layer be rendered on a color display. The units are specified in PCS-Values, and the value is encoded as CIELab. See C.10.7.1.1.</description>
      <section ref="C.10.7.1.1" name="">Attributes such as Graphic Layer Recommended Display CIELab Value (0070,0401) consist of three unsigned short values:
</section>
    </entry>
    <entry group="0070" element="0068" name="&gt;Graphic Layer Description" type="3">
      <description>A free text description of the contents of this layer.</description>
    </entry>
  </module>
  <module ref="C.10.8" table="C.10-8" name="Waveform Identification Module Attributes">
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description>A number that identifies this Waveform.</description>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the Waveform data was created.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the Waveform data was created.</description>
    </entry>
    <entry group="0008" element="002A" name="Acquisition DateTime" type="1">
      <description>The date and time that the acquisition of data that resulted in this waveform started; the reference timestamp for the Multiplex Group Time Offset (0018,1068) for a waveform multiplex group
Note: The synchronization of this time with an external clock is specified in the Synchronization Module in Acquisition Time Synchronized (0018,1800).</description>
    </entry>
    <entry group="0008" element="114A" name="Referenced Instance Sequence" type="3">
      <description>A sequence which provides reference to a set of SOP Class/Instance pairs significantly related to this Waveform. One or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="3">
      <description>Code describing the purpose of the reference to the Instance(s). Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is CID 7004 for referenced waveforms."/>
  </module>
  <module ref="C.10.9" table="C.10-9" name="Waveform Module Attributes">
    <entry group="5400" element="0100" name="Waveform Sequence" type="1">
      <description>Sequence of one or more Items, each representing one waveform multiplex group. Ordering of Items in this Sequence is significant for external reference to specific multiplex groups.</description>
    </entry>
    <entry group="0018" element="1068" name="&gt; Multiplex Group Time Offset" type="1C">
      <description>Offset time in milliseconds from a reference time (see C.10.9.1.1).
Required if Acquisition Time Synchronized (0018,1800) value is Y; may be present otherwise.</description>
    </entry>
    <entry group="0018" element="1069" name="&gt; Trigger Time Offset" type="1C">
      <description>Offset time in milliseconds from a synchronization trigger to the first sample of a waveform multiplex group. May be positive or negative. Required if waveform acquisition is synchronized to a trigger.</description>
    </entry>
    <entry group="0018" element="106E" name="&gt; Trigger Sample Position" type="3">
      <description>Sample number whose time corresponds to a synchronization trigger (see C.10.9.1.2).</description>
    </entry>
    <entry group="003A" element="0004" name="&gt; Waveform Originality" type="1">
      <description>See C.10.9.1.3. Enumerated values:
ORIGINAL
DERIVED</description>
      <section ref="C.10.9.1.3" name="">Waveform Originality (003A,0004) shall have the value ORIGINAL if the Waveform Data samples are the original or source data, and shall have the value DERIVED if the Waveform Data samples have been derived in some manner from the sample data of other waveforms.
Notes :  1. The Waveform Originality (003A,0004) attribute is comparable to the Image Type (0008,0008) attribute value 1 (see C.7.6.1.1.2). Within a single Multiplex Group, all channels shall have the same Originality value.
  2. Waveform data which has been transcoded from a non-DICOM format may have Waveform Originality value ORIGINAL if the samples are unchanged from the originally acquired waveform samples.

</section>
    </entry>
    <entry group="003A" element="0005" name="&gt; Number of Waveform Channels" type="1">
      <description>Number of channels for this multiplex group.</description>
    </entry>
    <entry group="003A" element="0010" name="&gt; Number of Waveform Samples" type="1">
      <description>Number of samples per channel in this multiplex group.</description>
    </entry>
    <entry group="003A" element="001A" name="&gt; Sampling Frequency" type="1">
      <description>Frequency in Hz</description>
    </entry>
    <entry group="003A" element="0020" name="&gt; Multiplex Group Label" type="3">
      <description>Label for multiplex group</description>
    </entry>
    <entry group="003A" element="0200" name="&gt; Channel Definition Sequence" type="1">
      <description>Sequence of one or more Items, with one Item per channel (see C.10.9.1.4). Ordering of Items in this Sequence is significant for reference to specific channels.</description>
    </entry>
    <entry group="003A" element="0202" name="&gt;&gt; Waveform Channel Number" type="3">
      <description>Equipment physical channel number used for acquisition.</description>
    </entry>
    <entry group="003A" element="0203" name="&gt;&gt; Channel Label" type="3">
      <description>Text label for channel which may be used for display purposes</description>
    </entry>
    <entry group="003A" element="0205" name="&gt;&gt; Channel Status" type="3">
      <description>One or more values for the status of this channel within this SOP Instance. Defined terms:
OK
TEST DATA
DISCONNECTED
QUESTIONABLE
INVALID
UNCALIBRATED
UNZEROED
Precise location of a change in status may be noted in an Annotation.</description>
    </entry>
    <entry group="003A" element="0208" name="&gt;&gt; Channel Source Sequence" type="1">
      <description>A coded descriptor of the waveform channel source (metric, anatomical position, function, and technique). Only a single Item shall be permitted in this sequence. (See C.10.9.1.4.1)</description>
      <section ref="C.10.9.1.4.1" name="">Channel Source Sequence (003A,0208) identifies the metric (quality being measured, e.g., voltage or pressure), the anatomical position of the sensor or probe, the function of the channel (e.g., measurement or stimulus), and any particulars of technique which affect those parameters (e.g., pull-back across multiple anatomic sites, or differential input from two distinct sites). If the full semantics of the source is not carried in a single coded entry (e.g., if it specifies the location but not the metric), additional qualifiers are identified in Channel Source Modifiers Sequence (003A,0209) coded entries.
When a single sensor channel is used to collect a waveform from two (or more) anatomic sites, e.g., in hemodynamic pull-back procedures, multiple Channel Source Modifier items will identify the sequence of sites, if not encoded in the semantics of the Channel Source Coded Entry. Transition times from one site to another may be indicated with an Annotation, or pull-back rate may be indicated with an Acquisition Context Sequence Item (see Section C.7.6.14).
The Baseline (default) Context IDs are defined by IOD in accordance with Section A.34. Restrictions in the IOD may also determine the pattern of specification of the waveform source, i.e., which item is to be encoded in the Channel Source sequence, and the order in which Channel Source Modifier items are to be encoded. Unless otherwise specified, pattern of specification of the waveform source shall be:
</section>
    </entry>
    <include ref="&gt;&gt;&gt; Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID determined by IOD specialization"/>
    <entry group="003A" element="0209" name="&gt;&gt; Channel Source Modifiers Sequence" type="1C">
      <description>Sequence of one or more Items which further qualify the Waveform Source. Required if Channel Source Sequence (003A,0208) does not fully specify the semantics of the source. Ordering of Items in this Sequence may be semantically significant.</description>
    </entry>
    <include ref="&gt;&gt;&gt; Include 'Code Sequence Macro' Table 8.8-1." description="Baseline Context ID determined by IOD specialization"/>
    <entry group="003A" element="020A" name="&gt;&gt; Source Waveform Sequence" type="3">
      <description>A sequence which provides reference to a DICOM waveform from which this channel was derived. One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0040" element="A0B0" name="&gt;&gt;&gt; Referenced Waveform Channels" type="1">
      <description>Identifies the waveform multiplex group and channel within the referenced SOP Instance. Pair of values (M,C).</description>
    </entry>
    <entry group="003A" element="020C" name="&gt;&gt; Channel Derivation Description" type="3">
      <description>Additional description of waveform channel derivation</description>
    </entry>
    <entry group="003A" element="0210" name="&gt;&gt; Channel Sensitivity" type="1C">
      <description>Nominal numeric value of unit quantity of sample. Required if samples represent defined (not arbitrary) units.</description>
    </entry>
    <entry group="003A" element="0211" name="&gt;&gt; Channel Sensitivity Units Sequence" type="1C">
      <description>A coded descriptor of the Units of measure for the Channel Sensitivity. Only a single Item shall be permitted in this sequence. (see C.10.9.1.4.2) Required if Channel Sensitivity (003A,0210) is present.</description>
    </entry>
    <include ref="&gt;&gt;&gt; Include 'Code Sequence Macro' Table 8.8-1." description="Defined Context ID = 3082"/>
    <entry group="003A" element="0212" name="&gt;&gt; Channel Sensitivity Correction Factor" type="1C">
      <description>Multiplier to be applied to encoded sample values to match units specified in Channel Sensitivity (003A,0210) (e.g., based on calibration data) (see C.10.9.1.4.2) Required if Channel Sensitivity (003A,0210) is present.</description>
    </entry>
    <entry group="003A" element="0213" name="&gt;&gt; Channel Baseline" type="1C">
      <description>Offset of encoded sample value 0 from actual 0 using the units defined in the Channel Sensitivity Units Sequence (003A,0211). Required if Channel Sensitivity (003A,0210) is present.</description>
    </entry>
    <entry group="003A" element="0214" name="&gt;&gt; Channel Time Skew" type="1C">
      <description>Offset of first sample of channel from waveform multiplex group start time, in seconds (see C.10.9.1.4.3)
Required if Channel Sample Skew is not present.</description>
    </entry>
    <entry group="003A" element="0215" name="&gt;&gt; Channel Sample Skew" type="1C">
      <description>Offset of first sample of channel from waveform multiplex group start time, in samples (see C.10.9.1.4.3)
Required if Channel Time Skew is not present.</description>
    </entry>
    <entry group="003A" element="0218" name="&gt;&gt; Channel Offset" type="3">
      <description>Additional offset of first sample of channel to be used in aligning multiple channels for presentation or analysis, in seconds (see C.10.9.1.4.3)</description>
    </entry>
    <entry group="003A" element="021A" name="&gt;&gt; Waveform Bits Stored" type="1">
      <description>Number of significant bits within the waveform samples (see C.10.9.1.4.4)</description>
    </entry>
    <entry group="003A" element="0220" name="&gt;&gt; Filter Low Frequency" type="3">
      <description>Nominal 3dB point of lower frequency of pass band; in Hz</description>
    </entry>
    <entry group="003A" element="0221" name="&gt;&gt; Filter High Frequency" type="3">
      <description>Nominal 3dB point of upper frequency of pass band; in Hz</description>
    </entry>
    <entry group="003A" element="0222" name="&gt;&gt; Notch Filter Frequency" type="3">
      <description>Center frequency of notch filter(s); in Hz</description>
    </entry>
    <entry group="003A" element="0223" name="&gt;&gt; Notch Filter Bandwidth" type="3">
      <description>Nominal 3dB bandwidth of notch filter(s); in Hz</description>
    </entry>
    <entry group="5400" element="0110" name="&gt;&gt; Channel Minimum Value" type="3">
      <description>Minimum valid sample value as limited by the acquisition equipment (see C.10.9.1.4.5)</description>
    </entry>
    <entry group="5400" element="0112" name="&gt;&gt; Channel Maximum Value" type="3">
      <description>Maximum valid sample value as limited by the acquisition equipment (see C.10.9.1.4.5)</description>
    </entry>
    <entry group="5400" element="1004" name="&gt; Waveform Bits Allocated" type="1">
      <description>Size of each waveform data sample within the Waveform Data; see section C.10.9.1.5</description>
    </entry>
    <entry group="5400" element="1006" name="&gt; Waveform Sample Interpretation" type="1">
      <description>Data representation of the waveform data points. See C.10.9.1.5.</description>
      <section ref="C.10.9.1.5" name="">Waveform Bits Allocated (5400,1004) specifies the number of bits allocated for each sample, and Waveform Sample Interpretation (5400,1006) specifies the data representation of each waveform sample. Waveform Bits Allocated shall be a multiple of 8. These data elements are related, and their defined terms are specified in Table C.10-10.
Table C.10-10
Waveform Bits Allocated and Waveform Sample Interpretation
<unrecognized-rows><term value="Waveform Bits Allocated - Defined Terms" meaning="Waveform Sample Interpretation - Defined Terms"/><term value="8" meaning="SB"/><term value="" meaning="UB"/><term value="" meaning="MB"/><term value="" meaning="AB"/><term value="16" meaning="SS"/><term value="" meaning="US"/></unrecognized-rows>
Notes:  1. The set of valid values from within this table may be constrained by definition of the IOD (see Section A.34).
2. mu-law and A-law encoding is without the alternate bit inversion used for PCM transmission through the telephone network.
This representation also applies to the Channel Minimum and Maximum Data Values, and Waveform Padding Value.
</section>
    </entry>
    <entry group="5400" element="100A" name="&gt; Waveform Padding Value" type="1C">
      <description>Value of waveform samples inserted in channels when input is absent or invalid. Required if acquisition equipment inserts padding. See C.10.9.1.6.</description>
      <section ref="C.10.9.1.6" name="">Equipment which produces digitized waveform curves may encode a specific value when the source is disconnected or otherwise invalid. This value is encoded like the Waveform Data attribute with one sample only.
The Waveform Padding Value need not be within the range specified by the Channel Minimum and Maximum Data Values.
</section>
    </entry>
    <entry group="5400" element="1010" name="&gt; Waveform Data" type="1">
      <description>Encoded data samples - channel multiplexed
See section C.10.9.1.7</description>
    </entry>
    <entry group="003A" element="0230" name="Waveform Data Display Scale" type="3">
      <description>The recommended time-based waveform data display scale in units of mm/s (see C.10.9.1.8).</description>
    </entry>
    <entry group="003A" element="0231" name="Waveform Display Background CIELab Value" type="3">
      <description>A color triplet value recommended for rendering the waveform display background on a color display. The units are specified in PCS-Values, and the value is encoded as CIELab. See C.10.7.1.1.</description>
      <section ref="C.10.7.1.1" name="">Attributes such as Graphic Layer Recommended Display CIELab Value (0070,0401) consist of three unsigned short values:
</section>
    </entry>
    <entry group="003A" element="0240" name="Waveform Presentation Group Sequence" type="3">
      <description>Sequence of Items, each Item describing a Presentation Group of one or more waveform channels to be displayed together.
Note: A Presentation Group is conventionally denoted a "display page", and a waveform object may be rendered using several Presentation Groups under user display control.
One or more Items may be present.</description>
    </entry>
    <entry group="003A" element="0241" name="&gt;Presentation Group Number" type="1">
      <description>A number that identifies the Presentation Group.</description>
    </entry>
    <entry group="003A" element="0242" name="&gt;Channel Display Sequence" type="1">
      <description>Sequence of Items, each Item describing a channel to be displayed in the Presentation Group.
One or more Items shall be present.</description>
    </entry>
    <entry group="0040" element="A0B0" name="&gt;&gt;Referenced Waveform Channels" type="1">
      <description>Identifier of the displayed channel, specified as a pair of values (M,C) where the first value is the ordinal of the sequence item of the Waveform Sequence (5400,0100) attribute (i.e., the Multiplex Group Number), and the second value is the ordinal of the sequence item of the Channel Definition Sequence (003A,0200) attribute (i.e., the Waveform Channel Number) within the multiplex group.
Note: In the context of a Channel Display Sequence (003A,0242) Item, only a single channel shall be referenced.</description>
    </entry>
    <entry group="003A" element="0218" name="&gt;&gt;Channel Offset" type="3">
      <description>The offset in seconds from the beginning of the channel waveform data to the first sample to be used for presentation. Value may be negative.</description>
    </entry>
    <entry group="003A" element="0244" name="&gt;&gt;Channel Recommended Display CIELab Value" type="1">
      <description>A color triplet value recommended for rendering the channel on a color display. The units are specified in PCS-Values, and the value is encoded as CIELab. See C.10.7.1.1.</description>
      <section ref="C.10.7.1.1" name="">Attributes such as Graphic Layer Recommended Display CIELab Value (0070,0401) consist of three unsigned short values:
</section>
    </entry>
    <entry group="003A" element="0245" name="&gt;&gt;Channel Position" type="1">
      <description>Position of the Channel within the Presentation Group display area (see C.10.9.1.9).</description>
    </entry>
    <entry group="003A" element="0246" name="&gt;&gt;Display Shading Flag" type="3">
      <description>Specifies display area shading between the displayed waveform channel and another line. The nature of the shading (e.g., solid, or cross-hatching) is implementation dependent.
Enumerated Values:
NONE - no shading
BASELINE- shading between the waveform and the channel display baseline (sample value 0 equivalent location)
ABSOLUTE - shading between the waveform and the channel real world actual value 0 (i.e., taking into account the Channel Baseline (003A,0213) value)
DIFFERENCE - shading between the waveform and a second waveform in the Presentation Group at the same Channel Position that also has Display Shading Flag (003A,0246) value DIFFERENCE.</description>
    </entry>
    <entry group="003A" element="0247" name="&gt;&gt;Fractional Channel Display Scale" type="1C">
      <description>Fraction of the Presentation Group vertical display dimension assigned to the unit quantity (least significant bit) of the Channel samples (see C.10.9.1.10). Required if Absolute Channel Display Scale (003A,0248) is not present, may be present otherwise.</description>
    </entry>
    <entry group="003A" element="0248" name="&gt;&gt;Absolute Channel Display Scale" type="1C">
      <description>Nominal vertical display height in mm assigned to the unit quantity (least significant bit) of the Channel samples (see C.10.9.1.10). Required if Fractional Channel Display Scale (003A,0247) is not present, may be present otherwise.</description>
    </entry>
  </module>
  <module ref="C.10.10" table="C.10-11" name="– Waveform Annotation Module Attributes">
    <entry group="0040" element="B020" name="Waveform Annotation Sequence" type="1">
      <description>Sequence of Annotation Items; one or more items shall be present</description>
    </entry>
    <entry group="0070" element="0006" name="&gt; Unformatted Text Value" type="1C">
      <description>Text Observation Value (annotation).
Mutually exclusive with Concept Name Code Sequence (0040,A043)</description>
    </entry>
    <entry group="0040" element="A043" name="&gt; Concept Name Code Sequence" type="1C">
      <description>Code representing the fully specified name of the NUMERIC measurement or CODED concept. This sequence shall contain exactly one item.
Mutually exclusive with Text Value (0070,0006).</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID may be defined in IOD definition."/>
    <entry group="0040" element="A195" name="&gt;&gt; Modifier Code Sequence" type="1C">
      <description>A sequence of items modifying or specializing the Concept Name. One or more Items may be included in this Sequence.
Required if Concept Name Code Sequence (0040,A043) is sent and the value does not fully describe the semantics of the measurement or concept.</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID may be defined in IOD definition."/>
    <entry group="0040" element="A168" name="&gt; Concept Code Sequence" type="3">
      <description>A sequence that conveys the categorical coded nominal value. This sequence shall contain exactly one item.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID may be defined in IOD definition."/>
    <entry group="0040" element="A195" name="&gt;&gt; Modifier Code Sequence" type="1C">
      <description>A sequence of items modifying or specializing the Concept. One or more Items may be included in this Sequence.
Required if Concept Code Sequence (0040,A168) is sent and the value does not fully describe the semantics of the concept value.</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID may be defined in IOD definition."/>
    <entry group="0040" element="A30A" name="&gt; Numeric Value" type="3">
      <description>Numeric measurement value or values.</description>
    </entry>
    <entry group="0040" element="08EA" name="&gt; Measurement Units Code Sequence" type="3">
      <description>Units of measurement. Coded entry sequence with one item only.</description>
    </entry>
    <include ref="&gt;&gt; Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID 82"/>
    <entry group="0040" element="A0B0" name="&gt; Referenced Waveform Channels" type="1">
      <description>List of channels in waveform to which annotation applies. See C.10.10.1.1</description>
      <section ref="C.10.10.1.1" name="">Referenced Waveform Channels (0040,A0B0) is a multi-value attribute which lists the channels to which an annotation of a waveform applies. Each channel is specified as a pair of values (M,C), where the first value is the ordinal of the sequence item of the Waveform Sequence (5400,0100) attribute (i.e., the Multiplex Group Number), and the second value is the ordinal of the sequence item of the Channel Definition Sequence (003A,0200) attribute (i.e., the Waveform Channel Number) within the multiplex group.
If the specified channel number is 0, the annotation applies to all channels in the multiplex group.
Note:  As an example, an annotation which applies to the entire first multiplex group and channels 2 and 3 of the third multiplex group would have Referenced Channels value 0001 0000 0003 0002 0003 0003.
</section>
    </entry>
    <entry group="0040" element="A130" name="&gt; Temporal Range Type" type="1C">
      <description>See C.10.10.1.2 for Enumerated Values.
Required if Annotation does not apply to entire Referenced Waveform Channels; shall not be present if Annotation applies to entire temporal extent of referenced channels.</description>
      <section ref="C.10.10.1.2" name="">The Temporal Range Type attribute (0040,A130) defines the type of temporal extent of the annotated region of interest. A temporal point (or instant of time) may be defined by a waveform sample offset (for a single waveform multiplex group only), time offset, or absolute time.
The following terms are Enumerated Values for Temporal Range Type:
POINT = a single temporal point
MULTIPOINT = multiple temporal points
SEGMENT = a range between two temporal points
MULTISEGMENT = multiple segments, each denoted by two temporal points
BEGIN = a range beginning at one temporal point, and extending beyond the end of the acquired data
END = a range beginning before the start of the acquired data, and extending to (and including) the identified temporal point
</section>
    </entry>
    <entry group="0040" element="A132" name="&gt; Referenced Sample Positions" type="1C">
      <description>List of samples within a multiplex group specifying temporal points for annotation. Position of first sample is 1. Required if Temporal Range Type (0040,A130) is present, and if Referenced Time Offsets (0040,A138) and Referenced DateTime (0040,A13A) are not present. See C.10.10.1.3</description>
      <section ref="C.10.10.1.3" name="">Referenced Sample Positions (0040,A132) may be used only if Referenced Waveform Channels (0040,A0B0) refers to channels within a single multiplex group. The sample position is by channel, and applies to all channels specified in Referenced Channels (0040,A0B0).
</section>
    </entry>
    <entry group="0040" element="A138" name="&gt; Referenced Time Offsets" type="1C">
      <description>Specifies temporal points for annotation by number of seconds after start of data. Required if Temporal Range Type (0040,A130) is present, and if Referenced Sample Positions (0040,A132) and Referenced DateTime (0040,A13A) are not present.</description>
    </entry>
    <entry group="0040" element="A13A" name="&gt; Referenced DateTime" type="1C">
      <description>Specifies temporal points for annotation by absolute time. Required if Temporal Range Type (0040,A130) is present, and if Referenced Sample Positions (0040,A132) and Referenced Time Offsets (0040,A138) are not present.</description>
    </entry>
    <entry group="0040" element="A180" name="&gt; Annotation Group Number" type="3">
      <description>Number identifying associated annotations (see C.10.10.1.4).</description>
    </entry>
  </module>
  <module ref="C.11.1" table="C.11-1" name="Modality LUT Module Attributes">
    <include ref="Include Modality LUT Macro Table C.11-1b"/>
  </module>
  <macro table="C.11-1b" name="Modality LUT Macro Attributes">
    <entry group="0028" element="3000" name="Modality LUT Sequence" type="1C">
      <description>Defines a sequence of Modality LUTs.
Only one Item may be present. Shall not be present if Rescale Intercept (0028,1052) is present.</description>
    </entry>
    <entry group="0028" element="3002" name="&gt;LUT Descriptor" type="1C">
      <description>Specifies the format of the LUT Data in this Sequence.
See C.11.1.1 for further explanation.
Required if the Modality LUT Sequence (0028,3000) is sent.</description>
      <section ref="C.11.1.1" name=""/>
    </entry>
    <entry group="0028" element="3003" name="&gt;LUT Explanation" type="3">
      <description>Free form text explanation of the meaning of the LUT.</description>
    </entry>
    <entry group="0028" element="3004" name="&gt;Modality LUT Type" type="1C">
      <description>Specifies the output values of this Modality LUT.
See C.11.1.1.2 for further explanation.
Required if the Modality LUT Sequence (0028,3000) is sent.</description>
      <section ref="C.11.1.1.2" name="">Specifies the units of the output of the Modality LUT or rescale operation.
Defined Terms:
  OD = The number in the LUT represents thousands of optical density. That is, a value of 2140 represents an optical density of 2.140.
  HU = Hounsfield Units (CT)
  US = Unspecified
Other values are permitted, but are not defined by the DICOM Standard.
</section>
    </entry>
    <entry group="0028" element="3006" name="&gt;LUT Data" type="1C">
      <description>LUT Data in this Sequence.
Required if the Modality LUT Sequence (0028,3000) is sent.</description>
    </entry>
    <entry group="0028" element="1052" name="Rescale Intercept" type="1C">
      <description>The value b in relationship between stored values (SV) and the output units specified in Rescale Type (0028,1054).
Output units = m*SV + b.
Required if Modality LUT Sequence (0028,3000) is not present. Shall not be present otherwise.</description>
    </entry>
    <entry group="0028" element="1053" name="Rescale Slope" type="1C">
      <description>m in the equation specified by Rescale Intercept (0028,1052).
Required if Rescale Intercept is present.</description>
    </entry>
    <entry group="0028" element="1054" name="Rescale Type" type="1C">
      <description>Specifies the output units of Rescale Slope (0028,1053) and Rescale Intercept (0028,1052).
See C.11.1.1.2 for further explanation.
Required if Rescale Intercept is present.</description>
      <section ref="C.11.1.1.2" name="">Specifies the units of the output of the Modality LUT or rescale operation.
Defined Terms:
  OD = The number in the LUT represents thousands of optical density. That is, a value of 2140 represents an optical density of 2.140.
  HU = Hounsfield Units (CT)
  US = Unspecified
Other values are permitted, but are not defined by the DICOM Standard.
</section>
    </entry>
  </macro>
  <module ref="C.11.2" table="C.11-2" name="VOI LUT Module Attributes">
    <include ref="Include VOI LUT Macro Table C.11-2b"/>
  </module>
  <macro table="C.11-2b" name="VOI LUT Macro Attributes">
    <entry group="0028" element="3010" name="VOI LUT Sequence" type="1C">
      <description>Defines a sequence of VOI LUTs. One or more Items shall be present.
Required if Window Center (0028,1050) is not present. May be present otherwise.</description>
    </entry>
    <entry group="0028" element="3002" name="&gt;LUT Descriptor" type="1">
      <description>Specifies the format of the LUT Data in this Sequence.
See C.11.2.1.1 for further explanation.</description>
      <section ref="C.11.2.1.1" name="">The three values of the LUT Descriptor (0028,3002) describe the format of the LUT Data in the corresponding Data Element (0028,3006).
The first value is the number of entries in the lookup table. When the number of table entries is equal to 216 then this value shall be 0.
The second value is the first input value mapped. The Value Representation of the second value (US or SS) depends on the source of the input to the VOI LUT, and shall be:
- the same as specified by Pixel Representation (0028,0103), if there is no Modality LUT or Rescale Slope and Intercept specified;
- SS if the possible output range after application of the Rescale Slope and Intercept may be signed;
Note:  This is always the case for the CT Image IOD in which the Rescale Type is specified to be Hounsfield Units, which are always signed.
- US otherwise.

This input value is mapped to the first entry in the LUT. All input values less than the first value mapped are also mapped to the first entry in the LUT Data. An input value one greater than the first value mapped is mapped to the second entry in the LUT Data. Subsequent input values are mapped to the subsequent entries in the LUT Data up to an input value equal to number of entries + first value mapped - 1 which is mapped to the last entry in the LUT Data. Input values greater than or equal to number of entries + first value mapped are also mapped to the last entry in the LUT Data.
The third value specifies the number of bits for each entry in the LUT Data. If the VOI LUT is included in an Image IOD, the third value of LUT Descriptor (0028,3002) shall be 8 or 16 bits, unless otherwise specialized. If the VOI LUT is included in a Presentation State IOD, the third value of LUT Descriptor (0028,3002) shall be between 8 and 16 inclusive. The LUT Data shall be stored in a format equivalent to 8 bits allocated when the number of bits for each entry is 8, and 16 bits allocated when the number of bits for each entry is 16, where in both cases the high bit is equal to bits stored - 1, and where bits stored is the third value.
Notes:  1. Since the LUT Descriptor (0028,3002) Attribute is multi-valued, in an Explicit VR Transfer Syntax, only one value representation (US or SS) may be specified, even though the first and third values are always by definition interpreted as unsigned. The explicit VR actually used is dictated by the VR needed to represent the second value.
  2. Some implementations have encoded 8 bit entries with 16 bits allocated, padding the high bits; this can be detected by comparing the number of entries specified in the LUT Descriptor with the actual value length of the LUT Data entry. The value length in bytes should equal the number of entries if bits allocated is 8, and be twice as long if bits allocated is 16.

The LUT Data contains the LUT entry values.
The output range is from 0 to 2n-1 where n is the third value of LUT Descriptor. This range is always unsigned.
</section>
    </entry>
    <entry group="0028" element="3003" name="&gt;LUT Explanation" type="3">
      <description>Free form text explanation of the meaning of the LUT.</description>
    </entry>
    <entry group="0028" element="3006" name="&gt;LUT Data" type="1">
      <description>LUT Data in this Sequence.</description>
    </entry>
    <entry group="0028" element="1050" name="Window Center" type="1C">
      <description>Window Center for display.
See C.11.2.1.2 for further explanation.
Required if VOI LUT Sequence (0028,3010) is not present. May be present otherwise.</description>
      <section ref="C.11.2.1.2" name="">Window Center (0028,1050) and Window Width (0028,1051) specify a linear conversion from stored pixel values (after any Modality LUT or Rescale Slope and Intercept specified in the IOD have been applied) to values to be displayed. Window Center contains the input value that is the center of the window. Window Width contains the width of the window.
Note:  The terms “window center” and “window width” are not consistently used in practice, nor were they defined in previous versions of the standard. The definitions here are presented for the purpose of defining consistent meanings for identity and threshold transformations while preserving the common practice of using integral values for center and width.

Window Width (0028,1051) shall always be greater than or equal to 1.
When Window Width (0028,1051) is greater than 1, these Attributes select the range of input values that are to be mapped to the full range of the displayed output.
When Window Width (0028,1051) is equal to 1, they specify a threshold below which input values will be displayed as the minimum output value.
Note:  Whether the minimum output value is rendered as black or white may depend on the value of Photometric Interpretation (0028,0004) or the presence of a Presentation LUT Module.

These Attributes are applied according to the following pseudo-code, where x is the input value, y is an output value with a range from ymin to ymax, c is Window Center (0028,1050) and w is Window Width (0028,1051):
    if  (x &lt;= c - 0.5 - (w-1)/2), then y = ymin
    else if  (x &gt; c - 0.5 + (w-1)/2), then y = ymax,
    else  y = ((x - (c - 0.5)) / (w-1) + 0.5) * (ymax - ymin)+ ymin

Notes:  1. For the purpose of this definition, a floating point calculation without integer truncation is assumed, though the manner of implementation may vary as long as the result is the same.
  2. The pseudo-code function computes a continuous value over the output range without any discontinuity at the boundaries. The value of 0 for w is expressly forbidden, and the value of 1 for w does not cause division by zero, since the continuous segment of the function will never be reached for that case.
  3. For example, for an output range 0 to 255:
    c=2048, w=4096 becomes:
      if (x &lt;= 0) then y = 0
      else if (x &gt; 4095) then y = 255
      else y = ((x - 2047.5) / 4095 + 0.5) * (255-0) + 0
    c=2048, w=1 becomes:
      if (x &lt;= 2047.5) then y = 0
      else if (x &gt; 2047.5) then y = 255
      else /* not reached */

    c=0, w=100 becomes:
      if (x &lt;= -50) then y = 0
      else if (x &gt; 49) then y = 255
      else y = ((x + 0.5) / 99 + 0.5) * (255-0) + 0
    c=0, w=1 becomes:
      if (x &lt;= -0.5) then y = 0
      else if (x &gt; -0.5) then y = 255
      else /* not reached */

  4. A Window Center of 2n-1 and a Window Width of 2n selects the range of input values from 0 to 2n-1. This represents an identity VOI LUT transformation in the case where no Modality LUT is specified and the stored pixel data are n bit unsigned integers.
  5. A Window Width of 1 is typically used to represent a "threshold" operation in which those integer input values less than the Window Center are represented as the minimum displayed value and those greater than or equal to the Window Center are represented as the maximum displayed value. A Window Width of 2 will have the same result for integral input values.
  6. The application of Window Center (0028,1050) and Window Width (0028,1051) may select a signed input range. There is no implication that this signed input range is clipped to zero.
  7. The selected input range may exceed the actual range of the input values, thus effectively “compressing” the contrast range of the displayed data into a narrower band of the available contrast range, and “flattening” the appearance. There are no limits to the maximum value of the window width, or to the minimum or maximum value of window level, both of which may exceed the actual or possible range of input values.
  8. Input values "below" the window are displayed as the minimum output value and input values "above" the window are displayed as the maximum output value. This is the common usage of the window operation in medical imaging. There is no provision for an alternative approach in which all values "outside" the window are displayed as the minimum output value.
  9. The output of the Window Center/Width or VOI LUT transformation is either implicitly scaled to the full range of the display device if there is no succeeding transformation defined, or implicitly scaled to the full input range of the succeeding transformation step (such as the Presentation LUT), if present. See C.11.6.1.
  10. Fractional values of Window Center and Window Width are permitted (since the VR of these Attributes is Decimal String), and though they are not often encountered, applications should be prepared to accept them.

These Attributes shall be used only for Images with Photometric Interpretation (0028,0004) values of MONOCHROME1 and MONOCHROME2. They have no meaning for other Images.
If multiple values are present, both Attributes shall have the same number of values and shall be considered as pairs. Multiple values indicate that multiple alternative views may be presented.
If any VOI LUT Table is included by an Image, a Window Width and Window Center or the VOI LUT Table, but not both, may be applied to the Image for display. Inclusion of both indicates that multiple alternative views may be presented.
If multiple items are present in VOI LUT Sequence (0028,3010), only one may be applied to the Image for display. Multiple items indicate that multiple alternative views may be presented.
If the VOI LUT Module is defined in an IOD and if neither a VOI LUT Sequence nor a Window Width and Window Center are present, then the VOI LUT stage of the grayscale pipeline is defined to be an identity transformation.
Notes:  1. This requirement is specified so that IODs that define a particular output space for the grayscale pipeline, such as P-Values, are not in an undefined state when no VOI LUT Sequence or Window Width and Window Center are present.
  2. Despite the Type 3 requirement for VOI LUT Sequence and Window Center, implementations that render images are expected to implement and apply these transformations when they are present in the image, unless overridden by the user, a presentation state, or a hanging protocol, and to allow the user to select which transformation to apply when multiple transformations are present.

</section>
    </entry>
    <entry group="0028" element="1051" name="Window Width" type="1C">
      <description>Window Width for display. See C.11.2.1.2 for further explanation.
Required if Window Center (0028,1050) is sent.</description>
      <section ref="C.11.2.1.2" name="">Window Center (0028,1050) and Window Width (0028,1051) specify a linear conversion from stored pixel values (after any Modality LUT or Rescale Slope and Intercept specified in the IOD have been applied) to values to be displayed. Window Center contains the input value that is the center of the window. Window Width contains the width of the window.
Note:  The terms “window center” and “window width” are not consistently used in practice, nor were they defined in previous versions of the standard. The definitions here are presented for the purpose of defining consistent meanings for identity and threshold transformations while preserving the common practice of using integral values for center and width.

Window Width (0028,1051) shall always be greater than or equal to 1.
When Window Width (0028,1051) is greater than 1, these Attributes select the range of input values that are to be mapped to the full range of the displayed output.
When Window Width (0028,1051) is equal to 1, they specify a threshold below which input values will be displayed as the minimum output value.
Note:  Whether the minimum output value is rendered as black or white may depend on the value of Photometric Interpretation (0028,0004) or the presence of a Presentation LUT Module.

These Attributes are applied according to the following pseudo-code, where x is the input value, y is an output value with a range from ymin to ymax, c is Window Center (0028,1050) and w is Window Width (0028,1051):
    if  (x &lt;= c - 0.5 - (w-1)/2), then y = ymin
    else if  (x &gt; c - 0.5 + (w-1)/2), then y = ymax,
    else  y = ((x - (c - 0.5)) / (w-1) + 0.5) * (ymax - ymin)+ ymin

Notes:  1. For the purpose of this definition, a floating point calculation without integer truncation is assumed, though the manner of implementation may vary as long as the result is the same.
  2. The pseudo-code function computes a continuous value over the output range without any discontinuity at the boundaries. The value of 0 for w is expressly forbidden, and the value of 1 for w does not cause division by zero, since the continuous segment of the function will never be reached for that case.
  3. For example, for an output range 0 to 255:
    c=2048, w=4096 becomes:
      if (x &lt;= 0) then y = 0
      else if (x &gt; 4095) then y = 255
      else y = ((x - 2047.5) / 4095 + 0.5) * (255-0) + 0
    c=2048, w=1 becomes:
      if (x &lt;= 2047.5) then y = 0
      else if (x &gt; 2047.5) then y = 255
      else /* not reached */

    c=0, w=100 becomes:
      if (x &lt;= -50) then y = 0
      else if (x &gt; 49) then y = 255
      else y = ((x + 0.5) / 99 + 0.5) * (255-0) + 0
    c=0, w=1 becomes:
      if (x &lt;= -0.5) then y = 0
      else if (x &gt; -0.5) then y = 255
      else /* not reached */

  4. A Window Center of 2n-1 and a Window Width of 2n selects the range of input values from 0 to 2n-1. This represents an identity VOI LUT transformation in the case where no Modality LUT is specified and the stored pixel data are n bit unsigned integers.
  5. A Window Width of 1 is typically used to represent a "threshold" operation in which those integer input values less than the Window Center are represented as the minimum displayed value and those greater than or equal to the Window Center are represented as the maximum displayed value. A Window Width of 2 will have the same result for integral input values.
  6. The application of Window Center (0028,1050) and Window Width (0028,1051) may select a signed input range. There is no implication that this signed input range is clipped to zero.
  7. The selected input range may exceed the actual range of the input values, thus effectively “compressing” the contrast range of the displayed data into a narrower band of the available contrast range, and “flattening” the appearance. There are no limits to the maximum value of the window width, or to the minimum or maximum value of window level, both of which may exceed the actual or possible range of input values.
  8. Input values "below" the window are displayed as the minimum output value and input values "above" the window are displayed as the maximum output value. This is the common usage of the window operation in medical imaging. There is no provision for an alternative approach in which all values "outside" the window are displayed as the minimum output value.
  9. The output of the Window Center/Width or VOI LUT transformation is either implicitly scaled to the full range of the display device if there is no succeeding transformation defined, or implicitly scaled to the full input range of the succeeding transformation step (such as the Presentation LUT), if present. See C.11.6.1.
  10. Fractional values of Window Center and Window Width are permitted (since the VR of these Attributes is Decimal String), and though they are not often encountered, applications should be prepared to accept them.

These Attributes shall be used only for Images with Photometric Interpretation (0028,0004) values of MONOCHROME1 and MONOCHROME2. They have no meaning for other Images.
If multiple values are present, both Attributes shall have the same number of values and shall be considered as pairs. Multiple values indicate that multiple alternative views may be presented.
If any VOI LUT Table is included by an Image, a Window Width and Window Center or the VOI LUT Table, but not both, may be applied to the Image for display. Inclusion of both indicates that multiple alternative views may be presented.
If multiple items are present in VOI LUT Sequence (0028,3010), only one may be applied to the Image for display. Multiple items indicate that multiple alternative views may be presented.
If the VOI LUT Module is defined in an IOD and if neither a VOI LUT Sequence nor a Window Width and Window Center are present, then the VOI LUT stage of the grayscale pipeline is defined to be an identity transformation.
Notes:  1. This requirement is specified so that IODs that define a particular output space for the grayscale pipeline, such as P-Values, are not in an undefined state when no VOI LUT Sequence or Window Width and Window Center are present.
  2. Despite the Type 3 requirement for VOI LUT Sequence and Window Center, implementations that render images are expected to implement and apply these transformations when they are present in the image, unless overridden by the user, a presentation state, or a hanging protocol, and to allow the user to select which transformation to apply when multiple transformations are present.

</section>
    </entry>
    <entry group="0028" element="1055" name="Window Center &amp; Width Explanation" type="3">
      <description>Free form explanation of the meaning of the Window Center and Width. Multiple values correspond to multiple Window Center and Width values.</description>
    </entry>
    <entry group="0028" element="1056" name="VOI LUT Function" type="3">
      <description>Describes a VOI LUT function to apply to the values of Window Center (0028,1050) and Window Width (0028,1051).
See C.11.2.1.3 for further explanation.
Defined terms:
LINEAR
SIGMOID
When this attribute is not present, the interpretation of the values of Window Center (0028,1050) and Window Width (0028,1051) is linear as in C.11.2.1.2.</description>
      <section ref="C.11.2.1.3" name="">The VOI LUT Function (0028,1056) specifies a potentially non-linear conversion for the output of the (conceptual) Modality LUT values to the input of the (conceptual) Presentation LUT.
The behavior for the value LINEAR is defined in C.11.2.1.2. For all other values, the VOI LUT Function (0028,1056) shall include a unique descriptor of the LUT function to be used. Each descriptor is associated with a bivariate function of Window Center (0028,1050) and Window Width (0028,1051).
If the VOI LUT Function (0028,1056) is present with a value other than LINEAR, the values provided in Window Center (0028,1050) and Window Width (0028,1051) shall not be interpreted as a linear conversion of the (conceptual) Modality LUT values to the input to the (conceptual) Presentation LUT – but as parameters for the function defined by the VOI LUT Function descriptor in (0028,1056).
When defined, each descriptor must provide the functional relationship between the output of the (conceptual) Modality LUT values to the input of the (conceptual) Presentation LUT.
</section>
    </entry>
  </macro>
  <module ref="C.11.4" table="C.11-4" name="Presentation LUT Module Attributes">
    <entry group="2050" element="0010" name="Presentation LUT Sequence">
      <description>Defines a sequence of Presentation LUTs. Only a single item shall be included in this sequence.</description>
    </entry>
    <entry group="0028" element="3002" name="&gt;LUT Descriptor">
      <description>Specifies the format of the LUT Data in this Sequence.
Required if Presentation LUT Sequence (2050,0010)
is sent.
See C.11.4.1 for further explanation.</description>
      <section ref="C.11.4.1" name="">The three values of the LUT Descriptor (0028,3002) describe the format of the data in LUT Data (0028,3006).
The first value is the number of entries in the lookup table. When the number of table entries is equal to 216 then this value shall be 0. The number of entries shall be equal to the number of possible values in the input. (For 8 bit input will be 256 entries, for 12 bit input it will be 4096 entries)
The second value is the first input value mapped, and shall always be 0. The Value Representation of the second value is always US. This input value is mapped to the first entry in the LUT. Subsequent input values are mapped to the subsequent entries in the LUT Data up to an input value equal to number of entries + first value mapped - 1 which is mapped to the last entry in the LUT Data. There are no input values greater than number of entries – 1.
The third value specifies the number of bits for each entry in the LUT Data. It shall be between 10 and 16 inclusive. The LUT Data shall be stored in a format equivalent to 16 bits allocated where the high bit is equal to bits stored - 1, where bits stored is the third value.
Note:  Since the LUT Descriptor (0028,3002) Attribute is multi-valued, in an Explicit VR Transfer Syntax, only one value representation (US or SS) may be specified. Since all three values are always by definition interpreted as unsigned, the explicit VR actually used will always be US.

LUT Data (0028,3006) contains the LUT entry values, which are P-Values.
The output range is from 0 to 2n-1 where n is the third value of LUT Descriptor. This range is always unsigned.
This range specifies the output range of the P-Values.
</section>
    </entry>
    <entry group="0028" element="3003" name="&gt;LUT Explanation">
      <description>Free form text explanation of the meaning of the LUT.</description>
    </entry>
    <entry group="0028" element="3006" name="&gt;LUT Data">
      <description>LUT Data in this Sequence.</description>
    </entry>
    <entry group="2050" element="0020" name="Presentation LUT Shape">
      <description>Specifies pre-defined Presentation LUT shapes.
Enumerated Values :
IDENTITY = input to the Presentation LUT is in P-Values, no further translation is necessary.
LIN OD = input to Presentation LUT is in linear optical density over the range of Min Density (2010,0120) and Max Density (2010,1030).
Note: LIN OD is only defined for hardcopy devices and is not applicable to softcopy devices.</description>
    </entry>
  </module>
  <module ref="C.11.5" table="C.11.5-1" name="Image Histogram Module Attributes">
    <entry group="0060" element="3000" name="Histogram Sequence" type="1">
      <description>Defines a sequence of Histograms.
One or more Items may be included in this Sequence.</description>
    </entry>
    <entry group="0060" element="3002" name="&gt;Histogram Number of Bins" type="1">
      <description>The number of "bins" (entries) in the histogram.</description>
    </entry>
    <entry group="0060" element="3004" name="&gt;Histogram First Bin Value" type="1">
      <description>The stored pixel value corresponding to the lowest pixel value counted in the first bin. All image pixel values less than this value are not included in the histogram.
Note: The Value Representation of this Attribute is determined by the value of Pixel Representation (0028,0103).</description>
    </entry>
    <entry group="0060" element="3006" name="&gt;Histogram Last Bin Value" type="1">
      <description>The stored pixel value corresponding to the highest pixel value counted in the last bin. All image pixel values greater than this value are not included in the histogram.
Note: The Value Representation of this Attribute is determined by the value of Pixel Representation (0028,0103).</description>
    </entry>
    <entry group="0060" element="3008" name="&gt;Histogram Bin Width" type="1">
      <description>The number of consecutive stored pixel values included in a bin. All bins shall be of equal width.</description>
    </entry>
    <entry group="0060" element="3010" name="&gt;Histogram Explanation" type="3">
      <description>Free form text explanation of the meaning of the LUT.</description>
    </entry>
    <entry group="0060" element="3020" name="&gt;Histogram Data" type="1">
      <description>Histogram Data encoded as 32 bit unsigned counts of the number of pixel values in each bin.</description>
    </entry>
  </module>
  <module ref="C.11.6" table="C.11.6-1" name="Softcopy Presentation LUT Module Attributes">
    <entry group="2050" element="0010" name="Presentation LUT Sequence" type="1C">
      <description>Defines a sequence of Presentation LUTs. Only a single item shall be included in this sequence. Required if Presentation LUT Shape (2050,0020) is absent.</description>
    </entry>
    <entry group="0028" element="3002" name="&gt;LUT Descriptor" type="1">
      <description>Specifies the format of the LUT Data in this Sequence.
See C.11.6.1.1 for further explanation.</description>
      <section ref="C.11.6.1.1" name="">The three values of the LUT Descriptor (0028,3002) describe the format of the LUT Data in the corresponding Data Element (0028,3006).
The first value is the number of entries in the lookup table. When the number of table entries is equal to 216 then this value shall be 0.
The second value is the first implicitly scaled input value mapped, and shall always be 0. The Value Representation of the second value is always US. This implicitly scaled input value is mapped to the first entry in the LUT. There are no implicitly scaled input values less than the first value mapped. An implicitly scaled input value one greater than the first value mapped is mapped to the second entry in the LUT Data. Subsequent implicitly scaled input values are mapped to the subsequent entries in the LUT Data up to an implicitly scaled input value equal to number of entries + first value mapped - 1 which is mapped to the last entry in the LUT Data. There are no implicitly scaled input values greater than number of entries + first value mapped.
The third value specifies the number of bits for each entry in the LUT Data. The third value of the LUT Descriptor (0028,3002) shall be between 8 and 16 inclusive. The LUT Data shall be stored in a format equivalent to 8 bits allocated when the number of bits for each entry is 8, and 16 bits allocated when the number of bits for each entry is 16, where the high bit is equal to bits stored - 1, and where bits stored is the third value.
Notes:  1. Since the LUT Descriptor (0028,3002) Attribute is multi-valued, in an Explicit VR Transfer Syntax, only one value representation (US or SS) may be specified. Since all three values are always by definition interpreted as unsigned, the explicit VR actually used will always be US.
  2. Some implementations have encoded 8 bit entries with 16 bits allocated, padding the high bits; this can be detected by comparing the number of entries specified in the LUT Descriptor with the actual value length of the LUT Data entry. The value length in bytes should equal the number of entries if bits allocated is 8, and be twice as long if bits allocated is 16.

The LUT Data contains the LUT entry values, which are P-Values.
The output range is from 0 to 2n-1 where n is the third value of LUT Descriptor. This range is always unsigned.
This range specifies the output range of the P-Values.
</section>
    </entry>
    <entry group="0028" element="3003" name="&gt;LUT Explanation" type="3">
      <description>Free form text explanation of the meaning of the LUT.</description>
    </entry>
    <entry group="0028" element="3006" name="&gt;LUT Data" type="1">
      <description>LUT Data in this Sequence.</description>
    </entry>
    <entry group="2050" element="0020" name="Presentation LUT Shape" type="1C">
      <description>Specifies predefined Presentation LUT transformation. Required if Presentation LUT Sequence (2050,0010) is absent.
Enumerated Values:
IDENTITY - no further translation necessary, input values are P-Values
INVERSE - output values after inversion are P-Values
See C.11.6.1.2.</description>
      <section ref="C.11.6.1.2" name="">A value of INVERSE shall mean the same as a value of IDENTITY, except that the minimum output value shall convey the meaning of the maximum available luminance, and the maximum value shall convey the minimum available luminance. In other words:
  P-Value = maximum value - output value

</section>
    </entry>
  </module>
  <module ref="C.11.7" table="C.11.7-1" name="Overlay Activation Module Attributes">
    <entry group="60xx" element="1001" name="Overlay Activation Layer" type="2C">
      <description>The layer (defined in Graphic Layer (0070,0002) of the Graphic Layer Module C.10.7) in which the Overlay described in group 60xx shall be displayed. If no layer is specified (zero length) then the overlay shall not be displayed.
Required if Group 60xx is present in the referenced image(s) or the Presentation State instance containing this Module.</description>
    </entry>
  </module>
  <module ref="C.11.8" table="C.11.8-1" name="Softcopy VOI LUT Module Attributes">
    <entry group="0028" element="3110" name="Softcopy VOI LUT Sequence" type="1">
      <description>Defines a sequence of VOI LUTs or Window Centers and Widths and to which images and frames they apply.
No more than one VOI LUT Sequence containing a single Item or one pair of Window Center/Width values shall be specified for each image or frame.
One or more Items shall be present.</description>
    </entry>
    <entry group="0008" element="1140" name="&gt;Referenced Image Sequence" type="1C">
      <description>Sequence of Items where each Item provides reference to a selected set of Image SOP Class/SOP Instance pairs that are defined in the Presentation State Relationship Module, to which this VOI LUT or Window Center and Width applies. One or more Items shall be present.
Required if the VOI LUT transformation in this Item does not apply to all the images and frames listed in the Presentation State Relationship Module.</description>
    </entry>
    <include ref="&gt;&gt;Include Image SOP Instance Reference Macro Table 10-3"/>
    <include ref="&gt;Include VOI LUT Macro Table C.11-2b"/>
  </module>
  <module ref="C.11.9" table="C.11.9-1" name="Presentation Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Type of equipment that originally acquired the data. Enumerated Value:
PR = Presentation State
See C.7.3.1.1.1.</description>
      <section ref="C.7.3.1.1.1" name="">Defined Terms for the Modality (0008,0060) are:
<defined-terms><term value="CR" meaning="Computed Radiography"/><term value="MR" meaning="Magnetic Resonance"/><term value="US" meaning="Ultrasound"/><term value="BI" meaning="Biomagnetic imaging"/><term value="DD" meaning="Duplex Doppler"/><term value="ES" meaning="Endoscopy"/><term value=""/><term value="PT" meaning="Positron emission tomography (PET)"/><term value="ST" meaning="Single-photon emission computed tomography (SPECT)"/><term value="XA" meaning="X-Ray Angiography"/><term value="RTIMAGE" meaning="Radiotherapy Image"/><term value="RTSTRUCT" meaning="Radiotherapy Structure Set"/><term value="RTRECORD" meaning="RT Treatment Record"/><term value="DX" meaning="Digital Radiography"/><term value="IO" meaning="Intra-oral Radiography"/><term value="GM" meaning="General Microscopy"/><term value="XC" meaning="External-camera Photography"/><term value="AU" meaning="Audio"/><term value="EPS" meaning="Cardiac Electrophysiology"/><term value="SR" meaning="SR Document"/><term value="OP" meaning="Ophthalmic Photography"/><term value="OCT" meaning="Optical Coherence Tomography (non-Ophthalmic)"/><term value="OPV" meaning="Ophthalmic Visual Field"/><term value="KO" meaning="Key Object Selection"/><term value="REG" meaning="Registration"/><term value="BDUS" meaning="Bone Densitometry (ultrasound)"/><term value="DOC" meaning="Document"/></defined-terms>
Retired Defined Terms for the Modality (0008,0060) are:
<retired-defined-terms><term value="DS" meaning="Digital Subtraction Angiography (retired)"/><term value="DF" meaning="Digital fluoroscopy (retired)"/><term value="AS" meaning="Angioscopy"/><term value="EC" meaning="Echocardiography"/><term value="FA" meaning="Fluorescein angiography"/><term value="DM" meaning="Digital microscopy"/><term value="MA" meaning="Magnetic resonance angiography"/></retired-defined-terms>
Note:  1. The XA modality incorporates the retired modality DS.
  2. The RF modality incorporates the retired modalities CF, DF, VF.
  3. The modality listed in the Modality Data Element (0008,0060) may not match the name of the IOD in which it appears. For example, a SOP instance from XA IOD may list the RF modality when an RF implementation produces an XA object.
  4. The MR modality incorporates the retired modalities MA and MS.

</section>
    </entry>
  </module>
  <module ref="C.11.10" table="C.11.10-1" name="Presentation State Identification Module Attributes">
    <entry group="0070" element="0082" name="Presentation Creation Date" type="1">
      <description>Date on which this presentation was created.
Note: This date may be different from the date that the DICOM SOP Instance was created, since the presentation state information contained may have been recorded earlier.</description>
    </entry>
    <entry group="0070" element="0083" name="Presentation Creation Time" type="1">
      <description>Time at which this presentation was created.
Note: This time may be different from the time that the DICOM SOP Instance was created, since the presentation state information contained may have been recorded earlier.</description>
    </entry>
    <include ref="Include Content Identification Macro Table 10-12" description="Note: The Content Label value may be used by an application as a Defined Term in order to imply some grouping of different presentation states, i.e. it may have the same value for different presentation state instances that share some common concept."/>
  </module>
  <module ref="C.11.11" table="C.11.11-1" name="Presentation State Relationship Module Attributes">
    <include ref="Include Presentation State Relationship Macro Table C.11.11-1b"/>
  </module>
  <macro table="C.11.11-1b" name="Presentation State Relationship Macro Attributes">
    <entry group="0008" element="1115" name="Referenced Series Sequence" type="1">
      <description>Sequence of Items where each Item includes the Attributes of one Series to which the Presentation applies.
One or more Items shall be present.</description>
    </entry>
    <entry group="0020" element="000E" name="&gt;Series Instance UID" type="1">
      <description>Unique identifier of a Series that is part of the Study defined by the Study Instance UID (0020,000D) in the enclosing dataset.
Note: The Study Instance UID (0020,000D) will be that of the presentation state itself, unless the macro is invoked from the Blending Sequence (0070,0402) in the Presentation State Blending Module, in which case it will be explicitly specified.</description>
    </entry>
    <entry group="0008" element="1140" name="&gt;Referenced Image Sequence" type="1">
      <description>Sequence of Items where each Item provides reference to a selected set of Image SOP Class/SOP Instance pairs to which the Presentation applies that are part of the Study defined by Study Instance UID (0020,000D) and the Series defined by Series Instance UID (0020,000E). One or more Items shall be present. The referenced SOP Class shall be the same for all Images in any Item of this Referenced Series Sequence (0008,1115).</description>
    </entry>
    <include ref="&gt;&gt;Include Image SOP Instance Reference Macro, Table 10-3"/>
  </macro>
  <module ref="C.11.12" table="C.11.12-1" name="Presentation State Shutter Module Attributes">
    <entry group="0018" element="1622" name="Shutter Presentation Value" type="1C">
      <description>A single grayscale unsigned value used to replace those parts of the image occluded by the shutter, when rendered on a monochrome display. The units are specified in P-Values.
Required if the Display Shutter Module or Bitmap Display Shutter Module is present.
Note: The requirement in this module is type 1C which overrides the type 3 in the Display Shutter Module.</description>
    </entry>
    <entry group="0018" element="1624" name="Shutter Presentation Color CIELab Value" type="1C">
      <description>A color triplet value used to replace those parts of the image occluded by the shutter, when rendered on a color display. The units are specified in PCS-Values, and the value is encoded as CIELab. See C.10.7.1.1.
Required if the Display Shutter Module or Bitmap Display Shutter Module is present and the SOP Class is other than Grayscale Softcopy Presentation State Storage.
Note: The requirement in this module is type 1C, which overrides the type 3 in the Display Shutter and Bitmap Display Shutter Modules.</description>
      <section ref="C.10.7.1.1" name="">Attributes such as Graphic Layer Recommended Display CIELab Value (0070,0401) consist of three unsigned short values:
</section>
    </entry>
  </module>
  <module ref="C.11.13" table="C.11.13-1" name="Presentation State Mask Module Attributes">
    <entry group="0028" element="6100" name="Mask Subtraction Sequence" type="1C">
      <description>Required if Mask Module is present.
Only one Item shall be present.
Applicable Frame Range (0028,6102) shall not be included in the Sequence Item.
See C.7.6.10 for a complete definition of the Attributes in the Items of this Sequence other than Mask Operation(0028,6101) and Applicable Frame Range (0028,6102).
Notes: 1. This Sequence is replicated here in order to specify one Item, additional conditions on Mask Operation (0028,6101) and to forbid Applicable Frame Range (0028,6102).
2. The role of Applicable Frame Range (0028,6102) is replaced by Referenced Frame Number (0008,1160).</description>
      <section ref="C.7.6.10" name="">Table C.7-16 specifies the Attributes that describe mask operations for a Multi-frame image.
Table C.7-16
MASK MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Mask Subtraction Sequence" meaning="(0028,6100)"/><term value="&gt;Mask Operation" meaning="(0028,6101)"/><term value="&gt;Subtraction Item ID" meaning="(0028,9416)"/><term value="&gt;Applicable Frame Range" meaning="(0028,6102)"/><term value="&gt;Mask Frame Numbers" meaning="(0028,6110)"/><term value="&gt;Contrast Frame Averaging" meaning="(0028,6112)"/><term value="&gt;Mask Sub-pixel Shift" meaning="(0028,6114)"/><term value="&gt;TID Offset" meaning="(0028,6120)"/><term value="&gt;Mask Operation Explanation" meaning="(0028,6190)"/><term value="&gt;Mask Selection Mode" meaning="(0028,9454)"/><term value="Recommended Viewing Mode" meaning="(0028,1090)"/></unrecognized-rows>
Note:  Frame numbers begin at 1.

</section>
    </entry>
    <entry group="0028" element="6101" name="&gt;Mask Operation" type="1">
      <description>Type of mask operation to be performed
Enumerated Values:
AVG_SUB
TID
See C.7.6.10.1 for further explanation.
Note: The requirement in this module is for Enumerated Values which override the requirements of the Mask Module.</description>
      <section ref="C.7.6.10.1" name=""/>
    </entry>
    <entry group="0028" element="6112" name="&gt;Contrast Frame Averaging" type="1C">
      <description>Specified the number of contrast frames to average together before performing the mask operation.
Required if Mask Frame Numbers (0028,6110) specifies more than one frame (i.e. is multi-valued).
Note: The requirement in this module is conditional and overrides the optional requirements of the Mask Module.</description>
    </entry>
    <entry group="0028" element="1090" name="Recommended Viewing Mode" type="1C">
      <description>Specifies the recommended viewing protocol(s).
Enumerated Value:
SUB = for subtraction with mask images
Required if Mask Subtraction Sequence (0028,6100) is present.
Note: The requirement in this module is type 1C and an Enumerated Value is specified which override the requirements of the Mask Module.</description>
    </entry>
  </module>
  <module ref="C.11.14" table="C.11.14-1" name="Presentation State Blending Module Attributes">
    <entry group="0070" element="0402" name="Blending Sequence" type="1">
      <description>A Sequence of exactly two Items, one identifying and describing transformations upon a set of underlying grayscale images, and the other identifying and describing transformations upon a set of superimposed grayscale images. See C.11.14.1.1.</description>
      <section ref="C.11.14.1.1" name="">The Blending Sequence (0070,0402) Attribute is used to identify two sets of images, one to be superimposed upon the other.
The sets of images and any subset of the frames therein in the case of multi-frame images are identified by Study, Series, SOP Instance and Frame Number.
This module specifies no explicit relationship (such as pairing or ordering) between the sets of images and frames defined in the first item for the underlying images, and the second item for the superimposed images. This module does not define how the images are spatially related, and what re-sampling, if any, needs to be performed before the images are blended for rendering.
Note:  The images in the two sets may share the same Frame of Reference, in which case the rendering application can spatially relate the two sets of images based on their Image Position (Patient) (0020,0032) and Image Orientation (Patient) (0020,0037) Attributes.
  Alternatively, a Spatial Registration SOP Instance may exist that relates either two different Frames of Reference, or two sets of images identified by UID and frame.
  Whilst the two sets of images may already be spatially co-registered and oriented in the same plane, or even be sampled at the same in-plane and between-plane resolution, this will frequently not be the case.
  See PS 3.4 for behavioral requirements that apply to Storage SOP Classes using this Module.

</section>
    </entry>
    <entry group="0070" element="0405" name="&gt;Blending Position" type="1">
      <description>Whether or not the contents of the Item represent the superimposed or underlying image set.
Enumerated Values:
SUPERIMPOSED
UNDERLYING</description>
    </entry>
    <entry group="0020" element="000D" name="&gt;Study Instance UID" type="1">
      <description>Unique identifier for the Study that contains the images, which may differ from the Study in which the presentation state is contained.</description>
    </entry>
    <include ref="&gt;Include Presentation State Relationship Macro Table C.11.11-1b"/>
    <include ref="&gt;Include Modality LUT Macro Table C.11-1b 1b if a Modality LUT is to be applied to referenced image(s)"/>
    <entry group="0028" element="3110" name="&gt;Softcopy VOI LUT Sequence" type="1C">
      <description>Defines a sequence of VOI LUTs or Window Centers and Widths and to which images and frames they apply.
No more than one VOI LUT Sequence containing a single Item or one pair of Window Center/Width values shall be specified for each image or frame.
One or more Items shall be present.
Required if a VOI LUT is to be applied to referenced image(s).</description>
    </entry>
    <entry group="0008" element="1140" name="&gt;&gt;Referenced Image Sequence" type="1C">
      <description>Sequence of Items identifying images that are defined in the enclosing Item of the Blending Sequence (0070,0402), to which this VOI LUT or Window Center and Width applies. One or more Items shall be present.
Required if the VOI LUT transformation in this Item does not apply to all the images and frames in the enclosing Item of the Blending Sequence (0070,0402).</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include Image SOP Instance Reference Macro Table 10-3"/>
    <include ref="&gt;&gt;Include VOI LUT Macro Table C.11-2b"/>
    <entry group="0070" element="0403" name="Relative Opacity" type="1">
      <description>A value from 0.0 to 1.0 indicating the relative opacity of the pixels of the superimposed image, where 1.0 means that pixels of the superimposed image completely replace the pixels of the underlying image, and 0.0 means that the pixels of the underlying image completely replace the pixels of the superimposed image.
See PS 3.4 for a detailed description of the blending operation.</description>
    </entry>
    <entry group="0070" element="0404" name="Referenced Spatial Registration Sequence" type="3">
      <description>A reference to Spatial Registration Instances that may be used to register the underlying and superimposed images.
Zero or more Items may be present.
Note: A Spatial Registration Instance may identify registration between frames of reference, or between explicitly identified images. In the latter case, the list of images referenced by the Presentation State, not the list of images referenced by the Spatial Registration Instance, are to be blended.</description>
    </entry>
    <include ref="&gt;Include Hierarchical SOP Instance Reference Macro Table C.17-3"/>
  </module>
  <module ref="C.11.15" table="C.11.15-1" name="ICC Profile Module Attributes">
    <entry group="0028" element="2000" name="ICC Profile" type="1">
      <description>An ICC Profile encoding the transformation of device-dependent color stored pixel values into PCS-Values.</description>
    </entry>
  </module>
  <module ref="C.12.1" table="C.12-1" name="SOP Common Module Attributes">
    <entry group="0008" element="0016" name="SOP Class UID" type="1">
      <description>Uniquely identifies the SOP Class. See C.12.1.1.1 for further explanation. See also PS 3.4.</description>
      <section ref="C.12.1.1.1" name="">The SOP Class UID and SOP Instance UID Attributes are defined for all DICOM IODs. However, they are only encoded in Composite IODs with the Type equal to 1. See C.1.2.3. When encoded they shall be equal to their respective Attributes in the DIMSE Services and the File Meta Information header (see PS 3.10 Media Storage).
</section>
    </entry>
    <entry group="0008" element="0018" name="SOP Instance UID" type="1">
      <description>Uniquely identifies the SOP Instance. See C.12.1.1.1 for further explanation. See also PS 3.4.</description>
      <section ref="C.12.1.1.1" name="">The SOP Class UID and SOP Instance UID Attributes are defined for all DICOM IODs. However, they are only encoded in Composite IODs with the Type equal to 1. See C.1.2.3. When encoded they shall be equal to their respective Attributes in the DIMSE Services and the File Meta Information header (see PS 3.10 Media Storage).
</section>
    </entry>
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Character Set that expands or replaces the Basic Graphic Set.
Required if an expanded or replacement character set is used.
See C.12.1.1.2 for Defined Terms.</description>
      <section ref="C.12.1.1.2" name="">Specific Character Set (0008,0005) identifies the Character Set that expands or replaces the Basic Graphic Set (ISO 646) for values of Data Elements that have Value Representation of SH, LO, ST, PN, LT or UT. See PS 3.5.
If the Attribute Specific Character Set (0008,0005) is not present or has only a single value, Code Extension techniques are not used. Defined terms for the Attribute Specific Character Set (0008,0005), when single valued, are derived from the International Registration Number as per ISO 2375 (e.g., ISO_IR 100 for Latin alphabet No. 1). See Table C.12-2.
Table C.12-2
 DEFINED TERMS FOR SINGLE-BYTE CHARACTER SETS WITHOUT CODE EXTENSIONS
<unrecognized-rows><term value="Character Set Description" meaning="Defined Term"/><term value="Default repertoire" meaning="none"/><term value="Latin alphabet No. 1" meaning="ISO_IR 100"/><term value=""/><term value="Latin alphabet No. 2" meaning="ISO_IR 101"/><term value=""/><term value="Latin alphabet No. 3" meaning="ISO_IR 109"/><term value=""/><term value="Latin alphabet No. 4" meaning="ISO_IR 110"/><term value=""/><term value="Cyrillic" meaning="ISO_IR 144"/><term value=""/><term value="Arabic" meaning="ISO_IR 127"/><term value=""/><term value="Greek" meaning="ISO_IR 126"/><term value=""/><term value="Hebrew" meaning="ISO_IR 138"/><term value=""/><term value="Latin alphabet No. 5" meaning="ISO_IR 148"/><term value=""/><term value="Japanese" meaning="ISO_IR 13"/><term value=""/><term value="Thai" meaning="ISO_IR 166"/><term value=""/></unrecognized-rows>
Note:  To use the single-byte code table of JIS X0201, the value of attribute Specific Character Set (0008,0005), value 1 should be ISO_IR 13. This means that ISO-IR 13 is designated as the G1 code element which is invoked in the GR area. It should be understood that, in addition, ISO-IR 14 is designated as the G0 code element and this is invoked in the GL area.

If the attribute Specific Character Set (0008,0005) has more than one value, Code Extension techniques are used and Escape Sequences may be encountered in all character sets. Requirements for the use of Code Extension techniques are specified in PS 3.5. In order to indicate the presence of Code Extension, the Defined Terms for the repertoires have the prefix “ISO 2022”, e.g., ISO 2022 IR 100 for the Latin Alphabet No. 1. See Table 12-3 and Table 12-4. Table 12-3 describes single-byte character sets for value 1 to value n of the attribute Specific Character Set (0008,0005), and Table 12-4 describes multi-byte character sets for value 2 to value n of the attribute Specific Character Set (0008,0005).
Note:  A prefix other than “ISO 2022” may be needed in the future if other Code Extension techniques are adopted.
Table C.12-3
DEFINED TERMS FOR SINGLE-BYTE CHARACTER SETS WITH CODE EXTENSIONS
<unrecognized-rows><term value="Character Set Description" meaning="Defined Term"/><term value="Default repertoire" meaning="ISO 2022 IR 6"/><term value="No. 1" meaning="ISO 2022 IR 100"/><term value="No. 2" meaning="ISO 2022 IR 101"/><term value="No. 3" meaning="ISO 2022 IR 109"/><term value="No. 4" meaning="ISO 2022 IR 110"/><term value="Cyrillic" meaning="ISO 2022 IR 144"/><term value="Arabic" meaning="ISO 2022 IR 127"/><term value="Greek" meaning="ISO 2022 IR 126"/><term value="Hebrew" meaning="ISO 2022 IR 138"/><term value="No. 5" meaning="ISO 2022 IR 148"/><term value="Japanese" meaning="ISO 2022 IR 13"/><term value="Thai" meaning="ISO 2022 IR 166"/><term value=""/></unrecognized-rows>
Note:  If the attribute Specific Character Set (0008,0005) has more than one value and value 1 is empty, it is assumed that value 1 is ISO 2022 IR 6.

Table C.12-4
DEFINED TERMS FOR MULTI-BYTE CHARACTER SETS WITH CODE EXTENSIONS
<unrecognized-rows><term value="Character Set Description" meaning="Defined Term"/><term value="Japanese" meaning="ISO 2022 IR 87"/><term value="" meaning="ISO 2022 IR 159"/><term value="Korean" meaning="ISO 2022 IR 149"/></unrecognized-rows>
There are multi-byte character sets that prohibit the use of Code Extension Techniques. The Unicode character set used in ISO 10646, when encoded in UTF-8, and the GB18030 character set, encoded per the rules of GB18030, both prohibit the use of Code Extension Techniques. These character sets may only be specified as value 1 in the Specific Character Set (0008,0005) attribute and there shall only be one value. The minimal length UTF-8 encoding shall always be used for ISO 10646.
Notes:  1. The ISO standards for 10646 now prohibit the use of anything but the minimum length encoding for UTF-8. UTF-8 permits multiple different encodings, but when used to encode Unicode characters in accordance with ISO 10646-1 and 10646-2 (with extensions) only the minimal encodings are legal.
  2. The representation for the characters in the DICOM Default Character Repertoire is the same single byte value for the Default Character Repertoire, ISO 10646 in UTF-8, and GB18030. It is also the 7-bit US-ASCII encoding.
Table C.12-5
DEFINED TERMS FOR MULTI-BYTE CHARACTER SETS WITHOUT CODE EXTENSIONS
<unrecognized-rows><term value="Character Set Description" meaning="Defined Term"/><term value="Unicode in UTF-8" meaning="ISO_IR 192"/><term value="GB18030" meaning="GB18030"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0008" element="0012" name="Instance Creation Date" type="3">
      <description>Date the SOP Instance was created.</description>
    </entry>
    <entry group="0008" element="0013" name="Instance Creation Time" type="3">
      <description>Time the SOP Instance was created.</description>
    </entry>
    <entry group="0008" element="0014" name="Instance Creator UID" type="3">
      <description>Uniquely identifies device which created the SOP Instance.</description>
    </entry>
    <entry group="0008" element="001A" name="Related General SOP Class UID" type="3">
      <description>Uniquely identifies a Related General SOP Class for the SOP Class of this Instance. See PS 3.4.</description>
    </entry>
    <entry group="0008" element="001B" name="Original Specialized SOP Class UID" type="3">
      <description>The SOP Class in which the Instance was originally encoded, but which has been replaced during a fall-back conversion to the current Related General SOP Class. See PS 3.4.</description>
    </entry>
    <entry group="0008" element="0110" name="Coding Scheme Identification Sequence" type="3">
      <description>Sequence of items that map values of Coding Scheme Designator (0008,0102) to an external coding system registration, or to a private or local coding scheme. One or more items may be present in the sequence.</description>
    </entry>
    <entry group="0008" element="0102" name="&gt;Coding Scheme Designator" type="1">
      <description>The value of a Coding Scheme Designator, used in this SOP Instance, which is being mapped.</description>
    </entry>
    <entry group="0008" element="0112" name="&gt;Coding Scheme Registry" type="1C">
      <description>The name of the external registry where further definition of the identified coding scheme may be obtained. Required if coding scheme is registered.
Defined term: HL7</description>
    </entry>
    <entry group="0008" element="010C" name="&gt;Coding Scheme UID" type="1C">
      <description>The coding scheme UID identifier. Required if coding scheme is identified by an ISO 8824 object identifier compatible with the UI VR.</description>
    </entry>
    <entry group="0008" element="0114" name="&gt;Coding Scheme External ID" type="2C">
      <description>The coding scheme identifier as defined in an external registry. Required if coding scheme is registered and Coding Scheme UID (0008,010C) is not present.</description>
    </entry>
    <entry group="0008" element="0115" name="&gt;Coding Scheme Name" type="3">
      <description>The coding scheme full common name</description>
    </entry>
    <entry group="0008" element="0103" name="&gt;Coding Scheme Version" type="3">
      <description>The coding scheme version associated with the Coding Scheme Designator (0008,0102).</description>
    </entry>
    <entry group="0008" element="0116" name="&gt;Coding Scheme Responsible Organization" type="3">
      <description>Name of the organization responsible for the Coding Scheme. May include organizational contact information.</description>
    </entry>
    <entry group="0008" element="0201" name="Timezone Offset From UTC" type="3">
      <description>Contains the offset from UTC to the timezone for all DA and TM Attributes present in this SOP Instance, and for all DT Attributes present in this SOP Instance that do not contain an explicitly encoded timezone offset.
Encoded as an ASCII string in the format "&amp;ZZXX". The components of this string, from left to right, are &amp; = "+" or "-", and ZZ = Hours and XX = Minutes of offset. Leading space characters shall not be present.
The offset for UTC shall be +0000; -0000 shall not be used.
Notes: 1. This encoding is the same as described in PS 3.5 for the offset component of the DT Value Representation.
2. This Attribute does not apply to values with a DT Value Representation, that contains an explicitly encoded timezone offset.
3. The corrected time may cross a 24 hour boundary. For example, if Local Time = 1.00 a.m. and Offset = +0200, then UTC = 11.00 p.m. (23.00) the day before.
4. The "+" sign may not be omitted.
Time earlier than UTC is expressed as a negative offset.
Note: For example:
UTC = 5.00 a.m.
Local Time = 3.00 a.m.
Offset = -0200

The local timezone offset is undefined if this Attribute is absent.</description>
    </entry>
    <entry group="0018" element="A001" name="Contributing Equipment Sequence" type="3">
      <description>Sequence of Items containing descriptive attributes of related equipment which has contributed to the acquisition, creation or modification of the composite instance.
One or more Items may be included in this Sequence.
See C.12.1.1.5 for further explanation.</description>
      <section ref="C.12.1.1.5" name="">Contributing Equipment Sequence (0018,A001) allows equipment to be described which has contributed towards the creation of the composite instance. The general class of contribution is denoted via a coded entry within the Purpose of Reference Code Sequence (0040,A170).
Notes:  1. For example, a post-processing application creating DERIVED images from ORIGINAL images would place its own identification within the Equipment Module and identify the original acquisition equipment as an Item within the Contributing Equipment Sequence (0018,A001). Here, the value of the Purpose of Reference Code Sequence (0040,A170) within the Item would be (109101, DCM, ”Acquisition Equipment"). Image display applications wishing to annotate images with information related to the acquisition environment would prefer to extract such details from the Contributing Equipment Sequence rather than the Equipment Module.
  2. For example, an image fusion application would place its own identification within the Equipment Module and identify each of the original acquisition equipment as separate Items within the Contributing Equipment Sequence (0018,A001). Here, the value of the Purpose of Reference Code Sequence (0040,A170) within each Item would be (109101, DCM, ”Acquisition Equipment").
  3. For example, a post-processing application creating DERIVED images from other DERIVED images would place its own identification within the Equipment Module and add the source equipment as an additional Item within the Contributing Equipment Sequence (0018,A001). Here, the value of the Purpose of Reference Code Sequence (0040,A170) within the Item would be (109102, DCM, ”Processing Equipment").
  4. For example, a gateway device that coerces attributes of existing composite instances (without creating new composite instances) would retain information about the creating equipment within the Equipment Module and provide its own identification as an Item within the Contributing Equipment Sequence (0018,A001). Here, the value of the Purpose of Reference Code Sequence (0040,A170) within the Item would be (109103, DCM, ”Modifying Equipment").

</section>
    </entry>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="1">
      <description>Describes the purpose for which the related equipment is being reference. Only a single Item shall be permitted in this sequence.
See C.12.1.1.5 for further explanation.</description>
      <section ref="C.12.1.1.5" name="">Contributing Equipment Sequence (0018,A001) allows equipment to be described which has contributed towards the creation of the composite instance. The general class of contribution is denoted via a coded entry within the Purpose of Reference Code Sequence (0040,A170).
Notes:  1. For example, a post-processing application creating DERIVED images from ORIGINAL images would place its own identification within the Equipment Module and identify the original acquisition equipment as an Item within the Contributing Equipment Sequence (0018,A001). Here, the value of the Purpose of Reference Code Sequence (0040,A170) within the Item would be (109101, DCM, ”Acquisition Equipment"). Image display applications wishing to annotate images with information related to the acquisition environment would prefer to extract such details from the Contributing Equipment Sequence rather than the Equipment Module.
  2. For example, an image fusion application would place its own identification within the Equipment Module and identify each of the original acquisition equipment as separate Items within the Contributing Equipment Sequence (0018,A001). Here, the value of the Purpose of Reference Code Sequence (0040,A170) within each Item would be (109101, DCM, ”Acquisition Equipment").
  3. For example, a post-processing application creating DERIVED images from other DERIVED images would place its own identification within the Equipment Module and add the source equipment as an additional Item within the Contributing Equipment Sequence (0018,A001). Here, the value of the Purpose of Reference Code Sequence (0040,A170) within the Item would be (109102, DCM, ”Processing Equipment").
  4. For example, a gateway device that coerces attributes of existing composite instances (without creating new composite instances) would retain information about the creating equipment within the Equipment Module and provide its own identification as an Item within the Contributing Equipment Sequence (0018,A001). Here, the value of the Purpose of Reference Code Sequence (0040,A170) within the Item would be (109103, DCM, ”Modifying Equipment").

</section>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID 7005."/>
    <entry group="0008" element="0070" name="&gt;Manufacturer" type="1">
      <description>Manufacturer of the equipment that contributed to the composite instance.</description>
    </entry>
    <entry group="0008" element="0080" name="&gt;Institution Name" type="3">
      <description>Institution where the equipment that contributed to the composite instance is located.</description>
    </entry>
    <entry group="0008" element="0081" name="&gt;Institution Address" type="3">
      <description>Address of the institution where the equipment that contributed to the composite instance is located.</description>
    </entry>
    <entry group="0008" element="1010" name="&gt;Station Name" type="3">
      <description>User defined name identifying the machine that contributed to the composite instance.</description>
    </entry>
    <entry group="0008" element="1040" name="&gt;Institutional Department Name" type="3">
      <description>Department in the institution where the equipment that contributed to the composite instance is located.</description>
    </entry>
    <entry group="0008" element="1090" name="&gt;Manufacturer's Model Name" type="3">
      <description>Manufacturer's model name of the equipment that contributed to the composite instance.</description>
    </entry>
    <entry group="0018" element="1000" name="&gt;Device Serial Number" type="3">
      <description>Manufacturer's serial number of the equipment that contributed to the composite instance.</description>
    </entry>
    <entry group="0018" element="1020" name="&gt;Software Versions" type="3">
      <description>Manufacturer's designation of the software version of the equipment that contributed to the composite instance.</description>
    </entry>
    <entry group="0018" element="1050" name="&gt;Spatial Resolution" type="3">
      <description>The inherent limiting resolution in mm of the acquisition equipment for high contrast objects for the data gathering and reconstruction technique chosen. If variable across the images of the series, the value at the image center.</description>
    </entry>
    <entry group="0018" element="1200" name="&gt;Date of Last Calibration" type="3">
      <description>Date when the image acquisition device calibration was last changed in any way. Multiple entries may be used for additional calibrations at other times. See C.7.5.1.1.1 for further explanation.</description>
      <section ref="C.7.5.1.1.1" name="">Date of Last Calibration (0018,1200) and Time of Last Calibration (0018,1201) are used to convey the date and time of calibration. The Attribute Date of Last Calibration (0018,1200) may be supported alone, however, Time of Last Calibration (0018,1201) Attribute has no meaning unless Attribute Date of Last Calibration (0018,1200) is also supported. The order for each Attribute shall be from the oldest date/time to the most recent date/time. When the Attributes are both supported they shall be provided as pairs.
</section>
    </entry>
    <entry group="0018" element="1201" name="&gt;Time of Last Calibration" type="3">
      <description>Time when the image acquisition device calibration was last changed in any way. Multiple entries may be used. See C.7.5.1.1.1 for further explanation.</description>
      <section ref="C.7.5.1.1.1" name="">Date of Last Calibration (0018,1200) and Time of Last Calibration (0018,1201) are used to convey the date and time of calibration. The Attribute Date of Last Calibration (0018,1200) may be supported alone, however, Time of Last Calibration (0018,1201) Attribute has no meaning unless Attribute Date of Last Calibration (0018,1200) is also supported. The order for each Attribute shall be from the oldest date/time to the most recent date/time. When the Attributes are both supported they shall be provided as pairs.
</section>
    </entry>
    <entry group="0018" element="A002" name="&gt;Contribution DateTime" type="3">
      <description>The Date &amp; Time when the equipment contributed to the composite instance.</description>
    </entry>
    <entry group="0018" element="A003" name="&gt;Contribution Description" type="3">
      <description>Description of the contribution the equipment made to the composite instance.</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="3">
      <description>A number that identifies this Composite object instance.</description>
    </entry>
    <entry group="0100" element="0410" name="SOP Instance Status" type="3">
      <description>A flag that indicates the storage status of the SOP Instance. Not Specified (NS) implies that this SOP Instance has no special storage status, and hence no special actions need be taken. Original (OR) implies that this is the primary SOP instance for the purpose of storage, but that it has not yet been authorized for diagnostic use. Authorized Original (AO) implies that this is the primary SOP instance for the purpose of storage, which has been authorized for diagnostic use. Any copies of an Authorized Original should be given the status of Authorized Copy. Authorized Copy (AC) implies that this is a copy of an Authorized Original SOP Instance.
Enumerated Values:
NS, OR, AO, AC
Note: Proper use of these flags is specified in Security Profiles. Implementations that do not conform to such Security Profiles may not necessarily handle these flags properly.</description>
    </entry>
    <entry group="0100" element="0420" name="SOP Authorization Date and Time" type="3">
      <description>The date and time when the SOP Instance Status (0100,0410) was set to AO.</description>
    </entry>
    <entry group="0100" element="0424" name="SOP Authorization Comment" type="3">
      <description>Any comments associated with the setting of the SOP Instance Status (0100,0410) to AO.</description>
    </entry>
    <entry group="0100" element="0426" name="Authorization Equipment Certification Number" type="3">
      <description>The certification number issued to the Application Entity that set the SOP Instance Status (0100,0410) to AO.</description>
    </entry>
    <include ref="Include 'Digital Signatures Macro' Table C.12-6"/>
    <entry group="0400" element="0500" name="Encrypted Attributes Sequence" type="1C">
      <description>Sequence of Items containing encrypted DICOM data. One or more Items shall be present. Required if application level confidentiality is needed and certain recipients are allowed to decrypt all or portions of the Encrypted Attributes Data Set. See C.12.1.1.4.1.</description>
      <section ref="C.12.1.1.4.1" name="">Each Item of the Encrypted Attributes Sequence (0400,0500) contains an encrypted DICOM dataset containing a single instance of the Encrypted Attributes Data Set (Table C.12-7). It also contains encrypted content-encryption keys for one or more recipients. The encoding is based on the Enveloped-data Content Type of the Cryptographic Message Syntax defined in RFC 2630. It allows to encrypt the embedded Data Set for an arbitrary number of recipients using any of the three key management techniques supported by RFC 2630:
</section>
    </entry>
    <entry group="0400" element="0510" name="&gt;Encrypted Content Transfer Syntax UID" type="1">
      <description>Transfer Syntax used to encode the encrypted content. Only Transfer Syntaxes that explicitly include the VR and use Little Endian encoding shall be used.</description>
    </entry>
    <entry group="0400" element="0520" name="&gt;Encrypted Content" type="1">
      <description>Encrypted data. See C.12.1.1.4.2.</description>
      <section ref="C.12.1.1.4.2" name="">The Encrypted Content (0400,0520) Attribute contains an Enveloped-data content type of the cryptographic message syntax defined in RFC 2630. The encrypted content of the Enveloped-data content type is an instance of the Encrypted Attributes Data Set as shown in Table C.12-7 (i.e., it is a Sequence with a single Item), encoded with the Transfer Syntax specified by the Encrypted Content Transfer Syntax UID (0400,0510) Attribute. Figure C.12-2 shows an example of how the Encrypted Content is encoded. The exact use of this Data Set is defined in the Attribute Confidentiality Profiles in PS 3.15.
Since the de-identified SOP Instance is a significantly altered version of the original Data Set, it is a new SOP Instance, with a SOP Instance UID that differs from the original Data Set.
Note:  1. Content encryption may require that the content (the DICOM Data Set) be padded to a multiple of some block size. This shall be performed according to the Content-encryption Process defined in RFC-2630.
  2. Any standard or private Transfer Syntax may be specified in Encrypted Content Transfer Syntax UID (0400,0510) unless encoding is performed in accordance with an Attribute Confidentiality Profile that specifies additional restrictions. In general, an application entity decoding the Encrypted Attributes Sequence may not assume any particular Transfer Syntax or set of Transfer Syntaxes to be used with Encrypted Content Transfer Syntax UID (0400,0510).
  3. For certain applications it might be necessary to “blacken” (remove) identifying information that is burned in to the image pixel data. The Encrypted Attributes Data Set does not specify a means of restoring the original image information without the complete image pixel data being encoded inside the Modified Attributes Sequence (0400,0550). If access to the original, unmodified pixel data is required and the image pixel data cannot be replicated inside the Modified Attributes Sequence (0400,0550) due to resource considerations, the SOP Instance UID may be used to locate the original SOP Instance from which the de-identified version was derived.
  4. There is no guarantee that the original SOP Instance can be reconstructed from the data in Encrypted Content. If access to the original data is required, the (de-encrypted) UIDs may be used to locate the original SOP Instance from which the de-identified version was derived.

Table C.12-7
ENCRYPTED ATTRIBUTES DATA SET ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Modified Attributes Sequence" meaning="(0400,0550)"/><term value="&gt; Any Attribute from the main dataset that was modified or removed during the de-identification process."/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0400" element="0561" name="Original Attributes Sequence" type="3">
      <description>Sequence of Items containing all attributes that were removed or replaced by other values in the main dataset.
One or more Items may be permitted in this sequence.</description>
    </entry>
    <entry group="0400" element="0564" name="&gt;Source of Previous Values" type="2">
      <description>The source that provided the SOP Instance prior to the removal or replacement of the values. For example, this might be the Institution from which imported SOP Instances were received.</description>
    </entry>
    <entry group="0400" element="0562" name="&gt;Attribute Modification DateTime" type="1">
      <description>Date and time the attributes were removed and/or replaced.</description>
    </entry>
    <entry group="0400" element="0563" name="&gt;Modifying System" type="1">
      <description>Identification of the system which removed and/or replaced the attributes.</description>
    </entry>
    <entry group="0400" element="0565" name="&gt;Reason for the Attribute Modification" type="1">
      <description>Reason for the attribute modification. Defined terms are:
COERCE = Replace values of attributes such as Patient Name, ID, Accession Number, for example, during import of media from an external institution, or reconciliation against a master patient index.
CORRECT = Replace incorrect values, such as Patient Name or ID, for example, when incorrect worklist item was chosen or operator input error.</description>
    </entry>
    <entry group="0400" element="0550" name="&gt;Modified Attributes Sequence" type="1">
      <description>Sequence containing a single item that contains all the Attributes, with their previous values, that were modified or removed from the main data set.</description>
    </entry>
    <include ref="&gt;&gt;Any Attribute from the main data set that was modified or removed; may include Sequence Attributes and their Items."/>
    <entry group="0040" element="A390" name="HL7 Structured Document Reference Sequence" type="1C">
      <description>Sequence of items defining mapping and/or access mechanism for HL7 Structured Documents referenced from the current SOP Instance. One or more Items may be included in this sequence.
See C.12.1.1.6.
Required if HL7 Structured Documents are referenced within the Instance.</description>
      <section ref="C.12.1.1.6" name="">The HL7 Structured Document Reference Sequence (0040,A390) identifies instances of Structured Documents defined under an HL7 standard. The HL7 standards that define such documents include the Clinical Document Architecture (CDA) and Structured Product Labeling (SPL) standards.
References to HL7 Structured Documents from within DICOM SOP Instances shall be encoded with a SOP Class UID and SOP Instance UID pair. The Abstract Syntax of an HL7 Structured Document is defined by its Hierarchical Message Description; the Object Identifier of the Hierarchical Message Description shall be used as the SOP Class UID for the Structured Document reference.
Notes:  1. The Hierarchical Message Description Object Identifiers are specified in the HL7 OID Registry (http://hl7.org/oid). The HL7 OIDs for these types of documents are:
  CDA Release 1    2.16.840.1.113883.1.7.1
  CDA Release 2    2.16.840.1.113883.1.7.2
  SPL Release 1    2.16.840.1.113883.1.7.3
  2. The Hierarchical Message Description Object Identifiers do not imply a network or media storage service, as do SOP Class UIDs. However, they do identify the Abstract Syntax, similar to SOP Class UIDs.

The HL7 Structured Document instances are natively identified by an attribute using the Instance Identifier (II) Data Type, as defined in HL7 v3 Data Types - Abstract Specification. A UID as defined by the DICOM UI Value Representation is a valid identifier under the II Data Type; however, an II attribute is not always encodable as a UID. Therefore a UID shall be constructed for use within the DICOM Data Set that can be mapped to the native instance identifier encoded as an HL7 II Data Type. This mapping is performed through the combination of the local Referenced SOP Instance UID (0008,1155) and the HL7 Instance Identifier (0040,E001) attributes in the HL7 Structured Document Reference Sequence (0040,A390).
Notes:  1. An HL7 II is not encodable as a UID if it exceeds 64 characters, or if it includes an extension. See HL7 v3 DT R1.
  2. Even though an II may contain just a UID, applications should take care to use the II specified in HL7 Instance Identifier (0040,E001) to access the Structured Document. If the instance identifier used natively within the referenced document is encodable using the UI VR, i.e., it is an ISO 8824 OID up to 64 characters without an extension, it is recommended to be used as the Referenced SOP Instance UID within the current Instance.
  3. The Referenced SOP Instance UID used to reference a particular HL7 Structured Document is not necessarily the same in all DICOM Instances. For example, two SR Documents may internally use different SOP Instance UIDs to reference the same HL7 Structured Document, but they will each contain a mapping to the same HL7 Instance Identifier as the external identifier.
  4. The HL7 Instance Identifier is encoded in attribute (0040,E001) as a serialization of the UID and Extension (if any) separated by a caret character. This is the same format adopted in the IHE Cross-Enterprise Document Sharing (XDS) profile (see http://www.ihe.net).
  5. See Figure C.12-3.


Figure C.12-3 HL7 Structured Document References

</section>
    </entry>
    <entry group="0008" element="1150" name="&gt;Referenced SOP Class UID" type="1">
      <description>Unique identifier for the class of HL7 Structured Document.</description>
    </entry>
    <entry group="0008" element="1155" name="&gt;Referenced SOP Instance UID" type="1">
      <description>Unique identifier for the HL7 Structured Document as used in DICOM instance references.</description>
    </entry>
    <entry group="0040" element="E001" name="&gt;HL7 Instance Identifier" type="1">
      <description>Instance Identifier of the referenced HL7 Structured Document, encoded as a UID (OID or UUID), concatenated with a caret ("^") and Extension value (if Extension is present in Instance Identifier).</description>
    </entry>
    <entry group="0040" element="E010" name="&gt;Retrieve URI" type="3">
      <description>Retrieval access path to HL7 Structured Document. Includes fully specified scheme, authority, path, and query in accordance with RFC 2396</description>
    </entry>
  </module>
  <macro table="C.12-6" name="Digital Signatures Macro Attributes">
    <entry group="4FFE" element="0001" name="MAC Parameters Sequence" type="3">
      <description>A sequence of one or more items that describe the parameters used to calculate a MAC for use in Digital Signatures.</description>
    </entry>
    <entry group="0400" element="0005" name="&gt;MAC ID Number" type="1">
      <description>A number, unique within this SOP Instance, used to identify this MAC Parameters Sequence (4FFE,0001) item from an Item of the Digital Signatures Sequence (FFFA,FFFA).</description>
    </entry>
    <entry group="0400" element="0010" name="&gt;MAC Calculation Transfer Syntax UID" type="1">
      <description>The Transfer Syntax UID used to encode the values of the Data Elements included in the MAC calculation. Only Transfer Syntaxes that explicitly include the VR and use Little Endian encoding shall be used.
Notes: Certain Transfer Syntaxes, particularly those that are used with compressed data, allow the fragmentation of the pixel data to change. If such fragmentation changes, Digital Signatures generated with such Transfer Syntaxes could become invalid.</description>
    </entry>
    <entry group="0400" element="0015" name="&gt;MAC Algorithm" type="1">
      <description>The algorithm used in generating the MAC to be encrypted to form the Digital Signature.
Defined Terms: RIPEMD160
MD5
SHA1
.
Note: Digital Signature Security Profiles (see PS 3.15) may require the use of a restricted subset of these terms.</description>
    </entry>
    <entry group="0400" element="0020" name="&gt;Data Elements Signed" type="1">
      <description>A list of Data Element Tags in the order they appear in the Data Set which identify the Data Elements used in creating the MAC for the Digital Signature. See Section C.12.1.1.3.1.1.</description>
      <section ref="C.12.1.1.3.1.1" name="">The Data Elements Signed Attribute shall list the Tags of the Data Elements that are included in the MAC calculation. The Tags listed shall reference Data Elements at the same level as the Mac Parameters Sequence (4FFE,0001) Data Element in which the Data Elements Signed Attribute appears. Tags included in Data Elements Signed shall be listed in the order in which they appear within the Data Set.
The following Data Elements shall not be included either implicitly or explicitly in the list of Tags in Data Elements Signed, nor included as part of the MAC calculation:
</section>
    </entry>
    <entry group="FFFA" element="FFFA" name="Digital Signatures Sequence" type="3">
      <description>Sequence holding Digital Signatures. One or more items may be included in this sequence.</description>
    </entry>
    <entry group="0400" element="0005" name="&gt;MAC ID Number" type="1">
      <description>A number used to identify which MAC Parameters Sequence item was used in the calculation of this Digital Signature.</description>
    </entry>
    <entry group="0400" element="0100" name="&gt;Digital Signature UID" type="1">
      <description>A UID that can be used to uniquely reference this signature.</description>
    </entry>
    <entry group="0400" element="0105" name="&gt;Digital Signature DateTime" type="1">
      <description>The date and time the Digital Signature was created. The time shall include an offset (i.e., time zone indication) from Coordinated Universal Time.
Note: This is not a certified timestamp, and hence is not completely verifiable. An application can compare this date and time with those of other signatures and the validity date of the certificate to gain confidence in the veracity of this date and time.</description>
    </entry>
    <entry group="0400" element="0110" name="&gt;Certificate Type" type="1">
      <description>The type of certificate used in (0400,0115).
Defined Term: X509_1993_SIG
Note: Digital Signature Security Profiles (see PS 3.15) may require the use of a restricted subset of these terms.</description>
    </entry>
    <entry group="0400" element="0115" name="&gt;Certificate of Signer" type="1">
      <description>A certificate that holds the identity of the entity producing this Digital Signature, that entity's public key or key identifier, and the algorithm and associated parameters with which that public key is to be used. Algorithms allowed are specified in Digital Signature Security Profiles (see PS 3.15).
Notes: 1. As technology advances, additional encryption algorithms may be allowed in future versions. Implementations should take this possibility into account.
2. When symmetric encryption is used, the certificate merely identifies which key was used by which entity, but not the actual key itself. Some other means (e.g., a trusted third party) must be used to obtain the key.</description>
    </entry>
    <entry group="0400" element="0120" name="&gt;Signature" type="1">
      <description>The MAC generated as described in Section C.12.1.1.3.1.1 and encrypted using the algorithm, parameters, and private key associated with the Certificate of the Signer (0400,0115). See Section C.12.1.1.3.1.2.</description>
      <section ref="C.12.1.1.3.1.2" name="">To generate the MAC, Data Elements referenced either explicitly or implicitly by the Tags in the Data Elements Signed list shall be encoded using the Transfer Syntax identified by the MAC Calculation Transfer Syntax UID (0400,0010) of the MAC Parameters Sequence item where the Data Elements Signed Attribute appears. Data shall be formed into a byte stream and presented to the MAC Algorithm for computation of the MAC according to the following rules:
For all Data Elements except those with a VR of SQ or with a VR of OB with an undefined length, all Data Element fields, including the Tag, the VR, the reserved field (if any), the Value Length, and the Value, shall be placed into the byte stream in the order encountered.
For Data Elements with a VR of SQ or with a VR of OB with an undefined length, the Tag, the VR, and the reserved field are placed into the byte stream. The Value Length shall not be included. This is followed by each Item Tag in the order encountered, without including the Value Length, followed by the contents of the Value for that item. In the case of an Item within a Data Element whose VR is SQ, these rules are applied recursively to all of the Data Elements within the Value of that Item. After all the Items have been incorporate into the byte stream, a Sequence Delimitation Item Tag (FFFE,E0DD) shall be added to the byte stream presented to the MAC Algorithm, regardless of whether or not it was originally present.
Note:  Since the Value Length of Data Elements with a VR of SQ can be either explicit or undefined, the Value Lengths of such Data Elements are left out of the MAC calculation. Similarly, the Value Length of Data Elements with a VR of OB with an undefined length are also left out so that they are handled consistently. If such Data Elements do come with undefined lengths, including the Item Tags that separate the Items or fragments insures that Data Elements cannot be moved between Items or Fragments without compromising the Digital Signature. For those Data Elements with explicit lengths, if the length of an item changes, the added or removed portions would also impact the MAC calculation, so it is not necessary to include explicit lengths in the MAC calculation. It is possible that including the Value Lengths could make cryptoanalysis easier.

After the fields of all the Data Elements in the Data Elements Signed list have been placed into the byte stream presented to the MAC Algorithm according to the above rules, all of the Data Elements within the Digital Signatures Sequence item except the Certificate of Signer (0400,0115), Signature (0400,0120), Certified Timestamp Type (0400,0305), and Certified Timestamp (0400,0310) shall also be encoded according to the above rules, and presented to the MAC algorithm (i.e., the Attributes of the Digital Signature Sequence Item for this particular Digital Signature are also implicitly included in the list of Data Elements Signed, except as noted above).
The resulting MAC code after processing this byte stream by the MAC Algorithm is then encrypted as specified in the Certificate of Signer and placed in the Value of the Signature Data Element.
Notes:  1. The Transfer Syntax used in the MAC calculation may differ from the Transfer Syntax used to exchange the Data Set.
  2. Digital Signatures require explicit VR in order to calculate the MAC. An Application Entity which receives a Data Set with an implicit VR Transfer Syntax may not be able to verify Digital Signatures that include Private Data Elements or Data Elements unknown to that Application Entity.This also true of any Data Elements whose VR is UN. Without knowledge of the Value Representation, the receiving Application Entity would be unable to perform proper byte swapping or be able to properly parse sequences in order to generate a MAC.
  3. If more than one entity signs, each Digital Signature would appear in its own Digital Signatures Sequence item. The Digital Signatures may or may not share the same MAC Parameters Sequence item.
4. The notion of a notary public (i.e., someone who verifies the identity of the signer) for Digital Signatures is partially filled by the authority that issued the Certificate of Signer.

</section>
    </entry>
    <entry group="0400" element="0305" name="&gt;Certified Timestamp Type" type="1C">
      <description>The type of certified timestamp used in the Certified Timestamp (0400,0310) Attribute. Required if Certified Timestamp (0400,0310) is present.
Defined Terms: CMS_TSP - Internet X.509 Public Key Infrastructure Time Stamp Protocol
Note: Digital Signature Security Profiles (see PS 3.15) may require the use of a restricted subset of these terms.</description>
    </entry>
    <entry group="0400" element="0310" name="&gt;Certified Timestamp" type="3">
      <description>A certified timestamp of the Digital Signature (0400,0120) Attribute Value, which shall be obtained when the Digital Signature is created. See Section C.12.1.1.3.1.3.</description>
      <section ref="C.12.1.1.3.1.3" name="">To generate a certified timestamp, the Value of the Signature (0400,0120) Attribute is sent to a third party, as specified by the protocol referred to by the Certified Timestamp Type (0400,0305) Attribute. The third party then generates and returns a certified timestamp in the form specified by that protocol. The certified timestamp returned by the third party is encoded as a stream of bytes in the Certified Timestamp Attribute.
Note:  The timestamp protocol may be specified by a Profile in PS 3.15.

</section>
    </entry>
    <entry group="0400" element="0401" name="&gt;Digital Signature Purpose Code Sequence" type="3">
      <description>The purpose of this Digital Signature. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 7007"/>
  </macro>
  <macro table="C.12-7" name="Encrypted Attributes Data Set Attributes">
    <entry group="0400" element="0550" name="Modified Attributes Sequence" type="1">
      <description>Sequence of Items containing all Attributes that were removed or replaced by "dummy values" in the main dataset during de-identification of the SOP instance. Upon reversal of the de-identification process, the Attributes are copied back into the main dataset, replacing any dummy values that might have been created. Only a single Item shall be present.</description>
    </entry>
    <include ref="&gt; Any Attribute from the main dataset that was modified or removed during the de-identification process." type="3"/>
  </macro>
  <module ref="C.12.2" table="C.12-8" name="Common Instance Reference Module Attributes">
    <include ref="Include Series and Instance Reference Macro, Table 10-4." description="Identifies all Series within the Study of which this Instance is a part, which Series contain Instances that are referenced elsewhere in this Instance."/>
    <entry group="0008" element="1200" name="Studies Containing Other Referenced Instances Sequence" type="1C">
      <description>Sequence of items each identifying a Study other than the Study of which this Instance is a part, which Studies contain Instances that are referenced elsewhere in this Instance. One or more Items shall be present. Required if this Instance references Instances in other Studies.</description>
    </entry>
    <entry group="0020" element="000D" name="&gt;Study Instance UID" type="1">
      <description>Unique identifier of the Study containing the referenced Instances.</description>
    </entry>
    <include ref="&gt;Include Series and Instance Reference Macro, Table 10-4."/>
  </module>
  <module ref="C.13.1" table="C.13-1" name="Basic Film Session Presentation Module Attributes">
    <entry group="2000" element="0010" name="Number of Copies">
      <description>Number of copies to be printed for each film of the film session.</description>
    </entry>
    <entry group="2000" element="0020" name="Print Priority">
      <description>Specifies the priority of the print job.
Enumerated Values:
HIGH
MED
LOW</description>
    </entry>
    <entry group="2000" element="0030" name="Medium Type">
      <description>Type of medium on which the print job will be printed. Defined Terms:
PAPER
CLEAR FILM
BLUE FILM
MAMMO CLEAR FILM
MAMMO BLUE FILM</description>
    </entry>
    <entry group="2000" element="0040" name="Film Destination">
      <description>Film destination. Defined Terms:
MAGAZINE = the exposed film is stored in film magazine
PROCESSOR = the exposed film is developed in film processor
BIN_i = the exposed film is deposited in a sorter bin where "I" represents the bin number. Film sorter BINs shall be numbered sequentially starting from one and no maxiumu is placed on the number of BINs. The encoding of the BIN number shall not contain leading zeros.</description>
    </entry>
    <entry group="2000" element="0050" name="Film Session Label">
      <description>Human readable label that identifies the film session</description>
    </entry>
    <entry group="2000" element="0060" name="Memory Allocation">
      <description>Amount of memory allocated for the film session. Value is expressed in KB</description>
    </entry>
    <entry group="2100" element="0160" name="Owner ID">
      <description>Identification of the owner of the film session</description>
    </entry>
  </module>
  <module ref="C.13.2" table="C.13-2" name="Basic Film Session Relationship Module Attributes">
    <entry group="2000" element="0500" name="Referenced Film Box Sequence">
      <description>A Sequence which provides references to a set of Film Box SOP Class/Instance pairs. Zero or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.13.3" table="C.13-3" name="Basic Film Box Presentation Module Attributes">
    <entry group="2010" element="0010" name="Image Display Format">
      <description>Type of image display format. Enumerated Values:
STANDARD\C,R : film contains equal size rectangular image boxes with R rows of image boxes and C columns of image boxes; C and R are integers.
ROW\R1,R2,R3, etc. : film contains rows with equal size rectangular image boxes with R1 image boxes in the first row, R2 image boxes in second row, R3 image boxes in third row, etc.; R1, R2, R3, etc. are integers.
COL\C1,C2,C3, etc.: film contains columns with equal size rectangular image boxes with C1 image boxes in the first column, C2 image boxes in second column, C3 image boxes in third column, etc.; C1, C2, C3, etc. are integers.
SLIDE : film contains 35mm slides; the number of slides for a particular film size is configuration dependent.
SUPERSLIDE : film contains 40mm slides; the number of slides for a particular film size is configuration dependent.
CUSTOM\i : film contains a customized ordering of rectangular image boxes; i identifies the image display format; the definition of the image display formats is defined in the Conformance Statement; i is an integer</description>
    </entry>
    <entry group="2010" element="0030" name="Annotation Display Format ID">
      <description>Identification of annotation display format. The definition of the annotation display formats and the annotation box position sequence are defined in the Conformance Statement</description>
    </entry>
    <entry group="2010" element="0040" name="Film Orientation">
      <description>Film orientation. Enumerated Values:
PORTRAIT = vertical film position
LANDSCAPE = horizontal film position</description>
    </entry>
    <entry group="2010" element="0050" name="Film Size ID">
      <description>Film size identification. Defined Terms:
8INX10IN
8_5INX11IN
10INX12IN
10INX14IN
11INX14IN
11INX17IN
14INX14IN
14INX17IN
24CMX24CM
24CMX30CM
A4
A3
Note: 10INX14IN corresponds with 25.7CMX36.4CM
A4 corresponds with 210 x 297 millimeters
A3 corresponds with 297 x 420 millimeters</description>
    </entry>
    <entry group="2010" element="0060" name="Magnification Type">
      <description>Interpolation type by which the printer magnifies or decimates the image in order to fit the image in the image box on film. Defined Terms:
REPLICATE
BILINEAR
CUBIC
NONE</description>
    </entry>
    <entry group="2010" element="0080" name="Smoothing Type">
      <description>Further specifies the type of the interpolation function. Values are defined in Conformance Statement. Only valid for Magnification Type (2010,0060) = CUBIC</description>
    </entry>
    <entry group="2010" element="0100" name="Border Density">
      <description>Density of the film areas surrounding and between images on the film. Defined Terms:
BLACK
WHITE
i where i represents the desired density in hundredths of OD (e.g. 150 corresponds with 1.5 OD)</description>
    </entry>
    <entry group="2010" element="0110" name="Empty Image Density">
      <description>Density of the image box area on the film that contains no image. Defined Terms:
BLACK
WHITE
i where i represents the desired density in hundredths of OD (e.g. 150 corresponds with 1.5 OD)</description>
    </entry>
    <entry group="2010" element="0120" name="Min Density">
      <description>Minimum density of the images on the film, expressed in hundredths of OD. If Min Density is lower than minimum printer density than Min Density is set to minimum printer density.</description>
    </entry>
    <entry group="2010" element="0130" name="Max Density">
      <description>Maximum density of the images on the film, expressed in hundredths of OD. If Max Density is higher than maximum printer density than Max Density is set to maximum printer density.</description>
    </entry>
    <entry group="2010" element="0140" name="Trim">
      <description>Specifies whether a trim box shall be printed surrounding each image on the film. Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="2010" element="0150" name="Configuration Information">
      <description>Character string that contains either the ID of the printer configuration table that contains a set of values for implementation specific print parameters (e.g. perception LUT related parameters) or one or more configuration data values, encoded as characters. If there are multiple configuration data values encoded in the string, they shall be separated by backslashes. The definition of values shall be contained in the SCP's Conformance Statement.
Defined Terms:
CS000-CS999: Implementation specific curve type.
Note: It is recommended that for SCPs, CS000 represent the lowest contrast and CS999 the highest contrast levels available.</description>
    </entry>
    <entry group="2010" element="015E" name="Illumination">
      <description>Luminance of lightbox illuminating a piece of transmissive film, or for the case of reflective media, luminance obtainable from diffuse reflection of the illumination present. Expressed as L0, in candelas per square meter (cd/m2).</description>
    </entry>
    <entry group="2010" element="0160" name="Reflected Ambient Light">
      <description>For transmissive film, luminance contribution due to reflected ambient light. Expressed as La, in candelas per square meter (cd/m2).</description>
    </entry>
    <entry group="2020" element="0050" name="Requested Resolution ID">
      <description>Specifies the resolution at which images in this Film Box are to be printed.
Defined Terms:
STANDARD = approximately 4k x 5k printable pixels on a 14 x 17 inch film
HIGH = Approximately twice the resolution of STANDARD.</description>
    </entry>
    <entry group="0028" element="2000" name="ICC Profile">
      <description>An ICC Profile encoding the transformation of device-dependent color stored pixel values into PCS-Values. See C.11.15.
Note. This is an Input Device Profile that describes the characteristics of the pixel data in the film box, not an Output Device Profile that might describe the characteristics of the Print SCP.</description>
      <section ref="C.11.15" name="">Table C.11.15-1 contains Attributes that identify and describe an ICC Profile.
Table C.11.15-1
ICC PROFILE MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
  </module>
  <module ref="C.13.4" table="C.13-4" name="Basic Film Box Relationship Module Attributes">
    <entry group="2010" element="0500" name="Referenced Film Session Sequence">
      <description>A sequence which provides references to a Film Session SOP Class/Instance pairs. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="2010" element="0510" name="Referenced Image Box Sequence">
      <description>A sequence which provides references to a set of Image Box SOP Class/Instance pairs. One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="2010" element="0520" name="Referenced Basic Annotation Box Sequence">
      <description>A Sequence which provides references to a set of Basic Annotation Box SOP Class/Instance pairs. Zero or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="2050" element="0500" name="Referenced Presentation LUT Sequence">
      <description>A sequence which provides references to a Presentation LUT related SOP Class/Instance pairs. Only a single Item shall be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.13.5" table="C.13-5" name="Image Box Pixel Presentation Module Attributes">
    <entry group="2020" element="0010" name="Image Box Position">
      <description>The position of the image on the film, based on Image Display Format (2010,0010). See C.13.5.1 for specification.</description>
      <section ref="C.13.5.1" name="">The position of the image on the film; the encoding of the image position sequence is based on the selected Image Display Format (2010,0010). The image position sequence shall be increasing order beginning with the value 1. Image Box Position (2020,0010) is defined as follows:
-  STANDARD display format: image box sequence shall be major row order (from left-to-right and from top-to-bottom); top left image position shall be equal to 1.
-  ROW display format: image box sequence shall be major row order (from left-to-right and from top-to-bottom); top left image position shall be set to 1.
-  COL display format: image box sequence shall be major column order (from top-to-bottom and from left-to-right); top left image position shall be equal to 1.
-  SLIDE display format: image box sequence shall be major row order (from left-to-right and from top-to-bottom); top left image position shall be set to 1.
-  SUPERSLIDE display format: image box sequence shall be major row order (from left-to-right and from top-to-bottom); top left image position shall be set to 1.
-  CUSTOM STANDARD display format: image box sequence shall be defined in the Conformance Statement; top left image position shall be set to 1.

</section>
    </entry>
    <entry group="2020" element="0020" name="Polarity">
      <description>Specifies whether minimum pixel values (after VOI LUT transformation) are to printed black or white. Enumerated Values:
NORMAL = pixels shall be printed as specified by the Photometric Interpretation (0028,0004)
REVERSE = pixels shall be printed with the opposite polarity as specified by the Photometric Interpretation (0028,0004)
If Polarity (2020,0020) is not specified by the SCU, the SCP shall print with NORMAL polarity.</description>
    </entry>
    <entry group="2010" element="0060" name="Magnification Type">
      <description>Description is the same as in Table C.13-3. Overrides the Magnification Type specified for the Film Box</description>
    </entry>
    <entry group="2010" element="0080" name="Smoothing Type">
      <description>Description is the same as in Table C.13-3. Overrides the Smoothing Type specified for the Film Box</description>
    </entry>
    <entry group="2010" element="0150" name="Configuration Information">
      <description>See Table C.13-3 for description of Configuration Information.</description>
    </entry>
    <entry group="2020" element="0030" name="Requested Image Size">
      <description>Width (x-dimension) in mm of the image to be printed. This value overrides the size that corresponds with optimal filling of the Image Box.</description>
    </entry>
    <entry group="2020" element="0040" name="Requested Decimate/Crop Behavior">
      <description>Specifies whether image pixels are to be decimated or cropped if the image rows or columns is greater than the available printable pixels in an Image Box.
Decimation means that a magnification factor &lt;1 is applied to the image. The method of decimation shall be that specified by Magnification Type (2010,0060) or the SCP default if not specified
Cropping means that some image rows and/or columns are deleted before printing
Enumerated Values:
DECIMATE = a magnification factor &lt;1 to be applied to the image.
CROP = some image rows and/or columns are to be deleted before printing. The specific algorithm for cropping shall be described in the SCP Conformance Statement.
FAIL = the SCP shall not crop or decimate</description>
    </entry>
    <entry group="2020" element="0110" name="Basic Grayscale Image Sequence">
      <description>A sequence which provides the content of the grayscale image pixel data to be printed. This is a specialization of the Image Pixel Module defined in C.7.6.3 of this part. It is encoded as a sequence of Attributes of the Image Pixel Module. Zero or one Item may be included in this Sequence.
See PS 3.4 for further description.</description>
    </entry>
    <entry group="0028" element="0002" name="&gt;Samples Per Pixel">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Value: 1</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0004" name="&gt;Photometric Interpretation">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Values:
MONOCHROME1
MONOCHROME2</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0010" name="&gt;Rows">
      <description>See C.7.6.3 for description of Image Pixel Module</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0011" name="&gt;Columns">
      <description>See C.7.6.3 for description of Image Pixel Module</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0034" name="&gt;Pixel Aspect Ratio">
      <description>See C.7.6.3 for description of Image Pixel Module</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0100" name="&gt;Bits Allocated">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Values:
8 (if Bits Stored = 8)
16 (if Bits Stored = 12)</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0101" name="&gt;Bits Stored">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Values:
8
12</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0102" name="&gt;High Bit">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Values:
7 (if BITS STORED = 8)
11 (if BITS STORED = 12)</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0103" name="&gt;Pixel Representation">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Value:
0 (unsigned integer)</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="7FE0" element="0010" name="&gt;Pixel Data">
      <description>See C.7.6.3 for description of Image Pixel Module</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2020" element="0111" name="Basic Color Image Sequence">
      <description>A sequence which provides the content of the color image pixel data to be printed. It is a specialization of the Image Pixel Module defined in C.7.6.3 of this part. It is encoded as a sequence of Attributes of the Image Pixel Module. Zero or one Item may be included in this Sequence.
See PS 3.4 for further description.</description>
    </entry>
    <entry group="0028" element="0002" name="&gt;Samples Per Pixel">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Value:
3</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0004" name="&gt;Photometric Interpretation">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Value:
RGB</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0006" name="&gt;Planar Configuration">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Value:
1 (frame interleave)</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0010" name="&gt;Rows">
      <description>See C.7.6.3 for description of Image Pixel Module.</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0011" name="&gt;Columns">
      <description>See C.7.6.3 for description of Image Pixel Module.</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0034" name="&gt;Pixel Aspect Ratio">
      <description>See C.7.6.3 for description of Image Pixel Module.</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0100" name="&gt;Bits Allocated">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Value: 8</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0101" name="&gt;Bits Stored">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Value:
8</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0102" name="&gt;High Bit">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Value:
7</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0028" element="0103" name="&gt;Pixel Representation">
      <description>See C.7.6.3 for description of Image Pixel Module. Enumerated Value:
0000H (unsigned integer)</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="7FE0" element="0010" name="&gt;Pixel Data">
      <description>See C.7.6.3 for description of Image Pixel Module</description>
      <section ref="C.7.6.3" name="">Table C.7-11a describes the Image Pixel Module.
Table C.7-11a
IMAGE PIXEL MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Include ‘Image Pixel Macro’ Table C.7-11b"/><term value="Pixel Data Provider URL" meaning="(0028,7FE0)"/><term value="Pixel Padding Range Limit" meaning="(0028,0121)"/></unrecognized-rows>
Table C.7-11b specifies the common attributes that describe the pixel data of the image.

Table C.7-11b
IMAGE PIXEL MACRO ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Samples per Pixel" meaning="(0028,0002)"/><term value="Photometric Interpretation" meaning="(0028,0004)"/><term value="Rows" meaning="(0028,0010)"/><term value="Columns" meaning="(0028,0011)"/><term value="Bits Allocated" meaning="(0028,0100)"/><term value="Bits Stored" meaning="(0028,0101)"/><term value="High Bit" meaning="(0028,0102)"/><term value="Pixel Representation" meaning="(0028,0103)"/><term value="Pixel Data" meaning="(7FE0,0010)"/><term value="Planar Configuration" meaning="(0028,0006)"/><term value="Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="Smallest Image Pixel Value" meaning="(0028,0106)"/><term value="Largest Image Pixel Value" meaning="(0028,0107)"/><term value="Red Palette Color Lookup Table Descriptor" meaning="(0028,1101)"/><term value="Green Palette Color Lookup Table Descriptor" meaning="(0028,1102)"/><term value="Blue Palette Color Lookup Table Descriptor" meaning="(0028,1103)"/><term value="Red Palette Color Lookup Table Data" meaning="(0028,1201)"/><term value="Green Palette Color Lookup Table Data" meaning="(0028,1202)"/><term value="Blue Palette Color Lookup Table Data" meaning="(0028,1203)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
  </module>
  <module ref="C.13.7" table="C.13-7" name="Basic Annotation Presentation Module Attributes">
    <entry group="2030" element="0010" name="Annotation Position">
      <description>The position of the annotation box in the parent film box. Annotation position sequence depends on the selected Annotation Display Format ID (2010,0030)</description>
    </entry>
    <entry group="2030" element="0020" name="Text String">
      <description>Text string</description>
    </entry>
  </module>
  <module ref="C.13.8" table="C.13-8" name="Print Job Module Attributes">
    <entry group="2100" element="0020" name="Execution Status">
      <description>Execution status of print job. Enumerated Values:
PENDING
PRINTING
DONE
FAILURE</description>
    </entry>
    <entry group="2100" element="0030" name="Execution Status Info">
      <description>Additional information about Execution Status (2100,0020).
Defined Terms when the Execution Status is DONE or PRINTING:
NORMAL
Defined Terms when the Execution Status is FAILURE:
INVALID PAGE DES = The specified page layout cannot be printed or other page description errors have been detected.
INSUFFIC MEMORY = There is not enough memory available to complete this job.
See Section C.13.9.1 for additional Defined Terms when the Execution Status is PENDING or FAILURE.</description>
      <section ref="C.13.9.1" name="">Additional Defined Terms for Printer Status Info (2110,0020) and Execution Status Info (2100,0030) are:
<defined-terms><term value="BAD RECEIVE MGZ" meaning="There is a problem with the film receive magazine. Films from the printer cannot be transported into the magazine."/><term value="BAD SUPPLY MGZ" meaning="There is a problem with a film supply magazine. Films from this magazine cannot be transported into the printer."/><term value="CALIBRATING" meaning="Printer is performing self calibration, it is expected to be available for normal operation shortly."/><term value="CALIBRATION ERR" meaning="An error in the printer calibration has been detected, quality of processed films may not be optimal."/><term value="CHECK CHEMISTRY" meaning="A problem with the processor chemicals has been detected, quality of processed films may not be optimal."/><term value="CHECK SORTER" meaning="There is an error in the film sorter."/><term value="CHEMICALS EMPTY" meaning="There are no processing chemicals in the processor, films will not be printed and processed until the processor is back to normal."/><term value="CHEMICALS LOW" meaning="The chemical level in the processor is low, if not corrected, it will probably shut down soon."/><term value="COVER OPEN" meaning="One or more printer or processor covers, drawers, doors are open."/><term value="ELEC CONFIG ERR" meaning="Printer configured improperly for this job."/><term value="ELEC DOWN" meaning="Printer is not operating due to some unspecified electrical hardware problem."/><term value="ELEC SW ERROR" meaning="Printer not operating for some unspecified software error."/><term value="EMPTY 8X10" meaning="The 8x10 inch film supply magazine is empty."/><term value="EMPTY 8X10 BLUE" meaning="The 8x10 inch blue film supply magazine is empty."/><term value="EMPTY 8X10 CLR" meaning="The 8x10 inch clear film supply magazine is empty."/><term value="EMPTY 8X10 PAPR" meaning="The 8x10 inch paper supply magazine is empty."/><term value="EMPTY 10X12" meaning="The 10x12 inch film supply magazine is empty."/><term value="EMPTY 10X12 BLUE" meaning="The 10x12 inch blue film supply magazine is empty."/><term value="EMPTY 10X12 CLR" meaning="The 10x12 inch clear film supply magazine is empty."/><term value="EMPTY 10X12 PAPR" meaning="The 10x12 inch paper supply magazine is empty."/><term value="EMPTY 10X14" meaning="The 10x14 inch film supply magazine is empty."/><term value="EMPTY 10X14 BLUE" meaning="The 10x14 inch blue film supply magazine is empty."/><term value="EMPTY 10X14 CLR" meaning="The 10x14 inch clear film supply magazine is empty."/><term value="EMPTY 10X14 PAPR" meaning="The 10x14 inch paper supply magazine is empty."/><term value="EMPTY 11X14" meaning="The 11x14 inch film supply magazine is empty."/><term value="EMPTY 11X14 BLUE" meaning="The 11x14 inch blue film supply magazine is empty."/><term value="EMPTY 11X14 CLR" meaning="The 11x14 inch clear film supply magazine is empty."/><term value="EMPTY 11X14 PAPR" meaning="The 11x14 inch paper supply magazine is empty."/><term value="EMPTY 14X14" meaning="The 14x14 inch film supply magazine is empty."/><term value="EMPTY 14X14 BLUE" meaning="The 14x14 inch blue film supply magazine is empty."/><term value="EMPTY 14X14 CLR" meaning="The 14x14 inch clear film supply magazine is empty."/><term value="EMPTY 14X14 PAPR" meaning="The 14x14 inch paper supply magazine is empty."/><term value="EMPTY 14X17" meaning="The 14x17 inch film supply magazine is empty."/><term value="EMPTY 14X17 BLUE" meaning="The 14x17 inch blue film supply magazine is empty."/><term value="EMPTY 14X17 CLR" meaning="The 14x17 inch clear film supply magazine is empty."/><term value="EMPTY 14X17 PAPR" meaning="The 14x17 inch paper supply magazine is empty."/><term value="EMPTY 24X24" meaning="The 24x24 cm film supply magazine is empty."/><term value="EMPTY 24X24 BLUE" meaning="The 24x24 cm blue film supply magazine is empty."/><term value="EMPTY 24X24 CLR" meaning="The 24x24 cm clear film supply magazine is empty."/><term value="EMPTY 24X24 PAPR" meaning="The 24x24 cm paper supply magazine is empty."/><term value="EMPTY 24X30" meaning="The 24x30 cm film supply magazine is empty."/><term value="EMPTY 24X30 BLUE" meaning="The 24x30 cm blue film supply magazine is empty."/><term value="EMPTY 24X30 CLR" meaning="The 24x30 cm clear film supply magazine is empty."/><term value="EMPTY 24X30 PAPR" meaning="The 24x30 cm paper supply magazine is empty."/><term value="EMPTY A4 PAPR" meaning="The A4 paper supply magazine is empty."/><term value="EMPTY A4 TRANS" meaning="The A4 transparency supply magazine is empty."/><term value="EXPOSURE FAILURE" meaning="The exposure device has failed due to some unspecified reason."/><term value="FILM JAM" meaning="A film transport error has occurred and a film is jammed in the printer or processor."/><term value="FILM TRANSP ERR" meaning="There is a malfunction with the film transport, there may or may not be a film jam."/><term value="FINISHER EMPTY" meaning="The finisher is empty."/><term value="FINISHER ERROR" meaning="The finisher is not operating due to some unspecified reason."/><term value="FINISHER LOW" meaning="The finisher is low on supplies"/><term value="LOW 8X10" meaning="The 8x10 inch film supply magazine is low."/><term value="LOW 8X10 BLUE" meaning="The 8x10 inch blue film supply magazine is low."/><term value="LOW 8X10 CLR" meaning="The 8x10 inch clear film supply magazine is low."/><term value="LOW 8X10 PAPR" meaning="The 8x10 inch paper supply magazine is low."/><term value="LOW 10X12" meaning="The 10x12 inch film supply magazine is low."/><term value="LOW 10X12 BLUE" meaning="The 10x12 inch blue film supply magazine is low."/><term value="LOW 10X12 CLR" meaning="The 10x12 inch clear film supply magazine is low."/><term value="LOW 10X12 PAPR" meaning="The 10x12 inch paper supply magazine is low."/><term value="LOW 10X14" meaning="The 10x14 inch film supply magazine is low."/><term value="LOW 10X14 BLUE" meaning="The 10x14 inch blue film supply magazine is low."/><term value="LOW 10X14 CLR" meaning="The 10x14 inch clear film supply magazine is low."/><term value="LOW 10X14 PAPR" meaning="The 10x14 inch paper supply magazine is low."/><term value="LOW 11X14" meaning="The 11x14 inch film supply magazine is low."/><term value="LOW 11X14 BLUE" meaning="The 11x14 inch blue film supply magazine is low."/><term value="LOW 11X14 CLR" meaning="The 11x14 inch clear film supply magazine is low."/><term value="LOW 11X14 PAPR" meaning="The 11x14 inch paper supply magazine is low."/><term value="LOW 14X14" meaning="The 14x14 inch film supply magazine is low."/><term value="LOW 14X14 BLUE" meaning="The 14x14 inch blue film supply magazine is low."/><term value="LOW 14X14 CLR" meaning="The 14x14 inch clear film supply magazine is low."/><term value="LOW 14X14 PAPR" meaning="The 14x14 inch paper supply magazine is low."/><term value="LOW 14X17" meaning="The 14x17 inch film supply magazine is low."/><term value="LOW 14X17 BLUE" meaning="The 14x17 inch blue film supply magazine is low."/><term value="LOW 14X17 CLR" meaning="The 14x17 inch clear film supply magazine is low."/><term value="LOW 14X17 PAPR" meaning="The 14x17 inch paper supply magazine is low."/><term value="LOW 24X24" meaning="The 24x24 cm film supply magazine is low."/><term value="LOW 24X24 BLUE" meaning="The 24x24 cm blue film supply magazine is low."/><term value="LOW 24X24 CLR" meaning="The 24x24 cm clear film supply magazine is low."/><term value="LOW 24X24 PAPR" meaning="The 24x24 cm paper supply magazine is low."/><term value="LOW 24X30" meaning="The 24x30 cm film supply magazine is low."/><term value="LOW 24X30 BLUE" meaning="The 24x30 cm blue film supply magazine is low."/><term value="LOW 24X30 CLR" meaning="The 24x30 cm clear film supply magazine is low."/><term value="LOW 24X30 PAPR" meaning="The 24x30 cm paper supply magazine is low."/><term value="LOW A4 PAPR" meaning="The A4 paper supply magazine is low."/><term value="LOW A4 TRANS" meaning="The A4 transparency supply magazine is low."/><term value="NO RECEIVE MGZ" meaning="The film receive magazine not available"/><term value="NO RIBBON" meaning="The ribbon cartridge needs to be replaced."/><term value="NO SUPPLY MGZ" meaning="The film supply magazine specified for this job is not available."/><term value="CHECK PRINTER" meaning="The printer is not ready at this time, operator intervention is required to make the printer available."/><term value="CHECK PROC" meaning="The processor is not ready at this time, operator intervention is required to make the printer available."/><term value="PRINTER DOWN" meaning="The printer is not operating due to some unspecified reason."/><term value="PRINTER BUSY" meaning="Printer is not available at this time, but should become ready without user intervention. This is to handle non-initialization instances."/><term value="PRINT BUFF FULL" meaning="The Printer ‘s buffer capacity is full. The printer is unable to accept new images in this state. The printer will correct this without user intervention. The SCU should retry later."/><term value="PRINTER INIT" meaning="The printer is not ready at this time, it is expected to become available without intervention. For example, it may be in a normal warm-up state."/><term value="PRINTER OFFLINE" meaning="The printer has been disabled by an operator or service person."/><term value="PROC DOWN" meaning="The processor is not operating due to some unspecified reason."/><term value="PROC INIT" meaning="The processor is not ready at this time, it is expected to become available without intervention. For example, it may be in a normal warm-up state."/><term value="PROC OVERFLOW FL" meaning="Processor chemicals are approaching the overflow full mark."/><term value="PROC OVERFLOW HI" meaning="Processor chemicals have reached the overflow full mark."/><term value="QUEUED" meaning="Print Job in Queue"/><term value="RECEIVER FULL" meaning="The Film receive magazine is full."/><term value="REQ MED NOT INST" meaning="The requested film, paper, or other media supply magazine is installed in the printer, but may be available with operator intervention."/><term value="REQ MED NOT AVAI" meaning="The requested film, paper, or other media requested is not available on this printer."/><term value="RIBBON ERROR" meaning="There is an unspecified problem with the print ribbon."/><term value="SUPPLY EMPTY" meaning="The printer is out of film."/><term value="SUPPLY LOW" meaning="The film supply is low."/><term value="UNKNOWN" meaning="There is an unspecified problem."/></defined-terms>
         </section>
    </entry>
    <entry group="2100" element="0040" name="Creation Date">
      <description>Date of print job creation.</description>
    </entry>
    <entry group="2100" element="0050" name="Creation Time">
      <description>Time of print job creation.</description>
    </entry>
    <entry group="2000" element="0020" name="Print Priority">
      <description>Priority of print job (see C.13.1 for further explanation).</description>
    </entry>
    <entry group="2110" element="0030" name="Printer Name">
      <description>User defined name identifying the printer.</description>
    </entry>
    <entry group="2100" element="0070" name="Originator">
      <description>DICOM Application Entity Title that issued the print operation.</description>
    </entry>
  </module>
  <module ref="C.13.9" table="C.13-9" name="Printer Module Attributes">
    <entry group="2110" element="0010" name="Printer Status">
      <description>Printer device status. Enumerated Values:
NORMAL
WARNING
FAILURE</description>
    </entry>
    <entry group="2110" element="0020" name="Printer Status Info">
      <description>Additional information about Printer Status (2110,0010).
Defined Terms when the Printer Status is equal to NORMAL:
NORMAL
See Section C.13.9.1 for Defined Terms when the Printer Status is equal to WARNING or FAILURE.</description>
      <section ref="C.13.9.1" name="">Additional Defined Terms for Printer Status Info (2110,0020) and Execution Status Info (2100,0030) are:
<defined-terms><term value="BAD RECEIVE MGZ" meaning="There is a problem with the film receive magazine. Films from the printer cannot be transported into the magazine."/><term value="BAD SUPPLY MGZ" meaning="There is a problem with a film supply magazine. Films from this magazine cannot be transported into the printer."/><term value="CALIBRATING" meaning="Printer is performing self calibration, it is expected to be available for normal operation shortly."/><term value="CALIBRATION ERR" meaning="An error in the printer calibration has been detected, quality of processed films may not be optimal."/><term value="CHECK CHEMISTRY" meaning="A problem with the processor chemicals has been detected, quality of processed films may not be optimal."/><term value="CHECK SORTER" meaning="There is an error in the film sorter."/><term value="CHEMICALS EMPTY" meaning="There are no processing chemicals in the processor, films will not be printed and processed until the processor is back to normal."/><term value="CHEMICALS LOW" meaning="The chemical level in the processor is low, if not corrected, it will probably shut down soon."/><term value="COVER OPEN" meaning="One or more printer or processor covers, drawers, doors are open."/><term value="ELEC CONFIG ERR" meaning="Printer configured improperly for this job."/><term value="ELEC DOWN" meaning="Printer is not operating due to some unspecified electrical hardware problem."/><term value="ELEC SW ERROR" meaning="Printer not operating for some unspecified software error."/><term value="EMPTY 8X10" meaning="The 8x10 inch film supply magazine is empty."/><term value="EMPTY 8X10 BLUE" meaning="The 8x10 inch blue film supply magazine is empty."/><term value="EMPTY 8X10 CLR" meaning="The 8x10 inch clear film supply magazine is empty."/><term value="EMPTY 8X10 PAPR" meaning="The 8x10 inch paper supply magazine is empty."/><term value="EMPTY 10X12" meaning="The 10x12 inch film supply magazine is empty."/><term value="EMPTY 10X12 BLUE" meaning="The 10x12 inch blue film supply magazine is empty."/><term value="EMPTY 10X12 CLR" meaning="The 10x12 inch clear film supply magazine is empty."/><term value="EMPTY 10X12 PAPR" meaning="The 10x12 inch paper supply magazine is empty."/><term value="EMPTY 10X14" meaning="The 10x14 inch film supply magazine is empty."/><term value="EMPTY 10X14 BLUE" meaning="The 10x14 inch blue film supply magazine is empty."/><term value="EMPTY 10X14 CLR" meaning="The 10x14 inch clear film supply magazine is empty."/><term value="EMPTY 10X14 PAPR" meaning="The 10x14 inch paper supply magazine is empty."/><term value="EMPTY 11X14" meaning="The 11x14 inch film supply magazine is empty."/><term value="EMPTY 11X14 BLUE" meaning="The 11x14 inch blue film supply magazine is empty."/><term value="EMPTY 11X14 CLR" meaning="The 11x14 inch clear film supply magazine is empty."/><term value="EMPTY 11X14 PAPR" meaning="The 11x14 inch paper supply magazine is empty."/><term value="EMPTY 14X14" meaning="The 14x14 inch film supply magazine is empty."/><term value="EMPTY 14X14 BLUE" meaning="The 14x14 inch blue film supply magazine is empty."/><term value="EMPTY 14X14 CLR" meaning="The 14x14 inch clear film supply magazine is empty."/><term value="EMPTY 14X14 PAPR" meaning="The 14x14 inch paper supply magazine is empty."/><term value="EMPTY 14X17" meaning="The 14x17 inch film supply magazine is empty."/><term value="EMPTY 14X17 BLUE" meaning="The 14x17 inch blue film supply magazine is empty."/><term value="EMPTY 14X17 CLR" meaning="The 14x17 inch clear film supply magazine is empty."/><term value="EMPTY 14X17 PAPR" meaning="The 14x17 inch paper supply magazine is empty."/><term value="EMPTY 24X24" meaning="The 24x24 cm film supply magazine is empty."/><term value="EMPTY 24X24 BLUE" meaning="The 24x24 cm blue film supply magazine is empty."/><term value="EMPTY 24X24 CLR" meaning="The 24x24 cm clear film supply magazine is empty."/><term value="EMPTY 24X24 PAPR" meaning="The 24x24 cm paper supply magazine is empty."/><term value="EMPTY 24X30" meaning="The 24x30 cm film supply magazine is empty."/><term value="EMPTY 24X30 BLUE" meaning="The 24x30 cm blue film supply magazine is empty."/><term value="EMPTY 24X30 CLR" meaning="The 24x30 cm clear film supply magazine is empty."/><term value="EMPTY 24X30 PAPR" meaning="The 24x30 cm paper supply magazine is empty."/><term value="EMPTY A4 PAPR" meaning="The A4 paper supply magazine is empty."/><term value="EMPTY A4 TRANS" meaning="The A4 transparency supply magazine is empty."/><term value="EXPOSURE FAILURE" meaning="The exposure device has failed due to some unspecified reason."/><term value="FILM JAM" meaning="A film transport error has occurred and a film is jammed in the printer or processor."/><term value="FILM TRANSP ERR" meaning="There is a malfunction with the film transport, there may or may not be a film jam."/><term value="FINISHER EMPTY" meaning="The finisher is empty."/><term value="FINISHER ERROR" meaning="The finisher is not operating due to some unspecified reason."/><term value="FINISHER LOW" meaning="The finisher is low on supplies"/><term value="LOW 8X10" meaning="The 8x10 inch film supply magazine is low."/><term value="LOW 8X10 BLUE" meaning="The 8x10 inch blue film supply magazine is low."/><term value="LOW 8X10 CLR" meaning="The 8x10 inch clear film supply magazine is low."/><term value="LOW 8X10 PAPR" meaning="The 8x10 inch paper supply magazine is low."/><term value="LOW 10X12" meaning="The 10x12 inch film supply magazine is low."/><term value="LOW 10X12 BLUE" meaning="The 10x12 inch blue film supply magazine is low."/><term value="LOW 10X12 CLR" meaning="The 10x12 inch clear film supply magazine is low."/><term value="LOW 10X12 PAPR" meaning="The 10x12 inch paper supply magazine is low."/><term value="LOW 10X14" meaning="The 10x14 inch film supply magazine is low."/><term value="LOW 10X14 BLUE" meaning="The 10x14 inch blue film supply magazine is low."/><term value="LOW 10X14 CLR" meaning="The 10x14 inch clear film supply magazine is low."/><term value="LOW 10X14 PAPR" meaning="The 10x14 inch paper supply magazine is low."/><term value="LOW 11X14" meaning="The 11x14 inch film supply magazine is low."/><term value="LOW 11X14 BLUE" meaning="The 11x14 inch blue film supply magazine is low."/><term value="LOW 11X14 CLR" meaning="The 11x14 inch clear film supply magazine is low."/><term value="LOW 11X14 PAPR" meaning="The 11x14 inch paper supply magazine is low."/><term value="LOW 14X14" meaning="The 14x14 inch film supply magazine is low."/><term value="LOW 14X14 BLUE" meaning="The 14x14 inch blue film supply magazine is low."/><term value="LOW 14X14 CLR" meaning="The 14x14 inch clear film supply magazine is low."/><term value="LOW 14X14 PAPR" meaning="The 14x14 inch paper supply magazine is low."/><term value="LOW 14X17" meaning="The 14x17 inch film supply magazine is low."/><term value="LOW 14X17 BLUE" meaning="The 14x17 inch blue film supply magazine is low."/><term value="LOW 14X17 CLR" meaning="The 14x17 inch clear film supply magazine is low."/><term value="LOW 14X17 PAPR" meaning="The 14x17 inch paper supply magazine is low."/><term value="LOW 24X24" meaning="The 24x24 cm film supply magazine is low."/><term value="LOW 24X24 BLUE" meaning="The 24x24 cm blue film supply magazine is low."/><term value="LOW 24X24 CLR" meaning="The 24x24 cm clear film supply magazine is low."/><term value="LOW 24X24 PAPR" meaning="The 24x24 cm paper supply magazine is low."/><term value="LOW 24X30" meaning="The 24x30 cm film supply magazine is low."/><term value="LOW 24X30 BLUE" meaning="The 24x30 cm blue film supply magazine is low."/><term value="LOW 24X30 CLR" meaning="The 24x30 cm clear film supply magazine is low."/><term value="LOW 24X30 PAPR" meaning="The 24x30 cm paper supply magazine is low."/><term value="LOW A4 PAPR" meaning="The A4 paper supply magazine is low."/><term value="LOW A4 TRANS" meaning="The A4 transparency supply magazine is low."/><term value="NO RECEIVE MGZ" meaning="The film receive magazine not available"/><term value="NO RIBBON" meaning="The ribbon cartridge needs to be replaced."/><term value="NO SUPPLY MGZ" meaning="The film supply magazine specified for this job is not available."/><term value="CHECK PRINTER" meaning="The printer is not ready at this time, operator intervention is required to make the printer available."/><term value="CHECK PROC" meaning="The processor is not ready at this time, operator intervention is required to make the printer available."/><term value="PRINTER DOWN" meaning="The printer is not operating due to some unspecified reason."/><term value="PRINTER BUSY" meaning="Printer is not available at this time, but should become ready without user intervention. This is to handle non-initialization instances."/><term value="PRINT BUFF FULL" meaning="The Printer ‘s buffer capacity is full. The printer is unable to accept new images in this state. The printer will correct this without user intervention. The SCU should retry later."/><term value="PRINTER INIT" meaning="The printer is not ready at this time, it is expected to become available without intervention. For example, it may be in a normal warm-up state."/><term value="PRINTER OFFLINE" meaning="The printer has been disabled by an operator or service person."/><term value="PROC DOWN" meaning="The processor is not operating due to some unspecified reason."/><term value="PROC INIT" meaning="The processor is not ready at this time, it is expected to become available without intervention. For example, it may be in a normal warm-up state."/><term value="PROC OVERFLOW FL" meaning="Processor chemicals are approaching the overflow full mark."/><term value="PROC OVERFLOW HI" meaning="Processor chemicals have reached the overflow full mark."/><term value="QUEUED" meaning="Print Job in Queue"/><term value="RECEIVER FULL" meaning="The Film receive magazine is full."/><term value="REQ MED NOT INST" meaning="The requested film, paper, or other media supply magazine is installed in the printer, but may be available with operator intervention."/><term value="REQ MED NOT AVAI" meaning="The requested film, paper, or other media requested is not available on this printer."/><term value="RIBBON ERROR" meaning="There is an unspecified problem with the print ribbon."/><term value="SUPPLY EMPTY" meaning="The printer is out of film."/><term value="SUPPLY LOW" meaning="The film supply is low."/><term value="UNKNOWN" meaning="There is an unspecified problem."/></defined-terms>
         </section>
    </entry>
    <entry group="2110" element="0030" name="Printer Name">
      <description>User defined name identifying the printer.</description>
    </entry>
    <entry group="0008" element="0070" name="Manufacturer">
      <description>Manufacturer of the printer.</description>
    </entry>
    <entry group="0008" element="1090" name="Manufacturer Model Name">
      <description>Manufacturer's model number of the printer.</description>
    </entry>
    <entry group="0018" element="1000" name="Device Serial Number">
      <description>Manufacturer's serial number of the printer.</description>
    </entry>
    <entry group="0018" element="1020" name="Software Versions">
      <description>Manufacturer's designation of software version of the printer.</description>
    </entry>
    <entry group="0018" element="1200" name="Date Of Last Calibration">
      <description>Date when the printer was last calibrated.</description>
    </entry>
    <entry group="0018" element="1201" name="Time Of Last Calibration">
      <description>Time when the printer was last calibrated.</description>
    </entry>
  </module>
  <module ref="C.13.13" table="C.13-13" name="Printer Configuration Module">
    <entry group="2000" element="001E" name="Printer Configuration Sequence">
      <description>Contains printer configuration information for a single Application Entity title. See Print Management Service Class Structure in PS 3.4. The sequence shall contain one item for each physical printer/Meta SOP Class combination supported by the Application Entity title.</description>
    </entry>
    <entry group="0008" element="115A" name="&gt;SOP Classes Supported">
      <description>The Meta-SOP Class and a list of optional SOP Classes supported. It shall contain one Meta SOP Class UID and 0-n optional SOP Class UIDs.</description>
    </entry>
    <entry group="2000" element="0061" name="&gt;Maximum Memory Allocation">
      <description>Maximum number of kilobytes of memory that can be allocated for a Film Session. The value shall be 0 if Memory Allocation (2000,0060) is not supported.</description>
    </entry>
    <entry group="2000" element="00A0" name="&gt;Memory Bit Depth">
      <description>The maximum number of bits for each pixel that can be stored in printer memory.</description>
    </entry>
    <entry group="2000" element="00A1" name="&gt;Printing Bit Depth">
      <description>The number of bits used by the print engine for internal LUT calculation and printing of each pixel.</description>
    </entry>
    <entry group="2000" element="00A2" name="&gt;Media Installed Sequence">
      <description>A sequence which specifies the combinations of Medium Type and Film Size IDs available in the printer at this time and the Min and Max Densities supported by these media.
The Item Number with the value of 1 is the printer default. There is no significance to other item numbers.
One item for each Medium Type and Film Size ID installed shall be included.</description>
    </entry>
    <entry group="0020" element="0019" name="&gt;&gt;Item Number">
      <description>A number that labels this item. Each item in the sequence shall have a unique number.</description>
    </entry>
    <entry group="2000" element="0030" name="&gt;&gt;Medium Type">
      <description>See C.13.1</description>
      <section ref="C.13.1" name="">Table C.13-1
BASIC FILM SESSION PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute name" meaning="Tag"/><term value="Number of Copies" meaning="(2000,0010)"/><term value="Print Priority" meaning="(2000,0020)"/><term value="Medium Type" meaning="(2000,0030)"/><term value="Film Destination" meaning="(2000,0040)"/><term value="Film Session Label" meaning="(2000,0050)"/><term value="Memory Allocation" meaning="(2000,0060)"/><term value="Owner ID" meaning="(2100,0160)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="0050" name="&gt;&gt;Film Size ID">
      <description>See C.13.3</description>
      <section ref="C.13.3" name="">Table C.13-3
BASIC FILM BOX PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Image Display Format" meaning="(2010,0010)"/><term value="Annotation Display Format ID" meaning="(2010,0030)"/><term value="Film Orientation" meaning="(2010,0040)"/><term value="Film Size ID" meaning="(2010,0050)"/><term value="Magnification Type" meaning="(2010,0060)"/><term value="Smoothing Type" meaning="(2010,0080)"/><term value="Border Density" meaning="(2010,0100)"/><term value="Empty Image Density" meaning="(2010,0110)"/><term value="Min Density" meaning="(2010,0120)"/><term value="Max Density" meaning="(2010,0130)"/><term value="Trim" meaning="(2010,0140)"/><term value="Configuration Information" meaning="(2010,0150)"/><term value="Illumination" meaning="(2010,015E)"/><term value="Reflected Ambient Light" meaning="(2010,0160)"/><term value="Requested Resolution ID" meaning="(2020,0050)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="0120" name="&gt;&gt;Min Density">
      <description>Minimum density that can be printed, expressed in hundredths of OD.</description>
    </entry>
    <entry group="2010" element="0130" name="&gt;&gt;Max Density">
      <description>Maximum density that can be printed, expressed in hundredths of OD.</description>
    </entry>
    <entry group="2000" element="00A4" name="&gt;Other Media Available Sequence">
      <description>A sequence which specifies combinations of Medium Type and Film Size ID for which the printer will accept an N-CREATE of a Film Box, but are not physically installed in the printer at this time. It also specifies the Min and Max Densities supported by these media. User intervention may be required to instal these media in the printer.
One item for each Medium Type and Film Size ID available, but not installed shall be included.</description>
    </entry>
    <entry group="2000" element="0030" name="&gt;&gt;Medium Type">
      <description>See C.13.1</description>
      <section ref="C.13.1" name="">Table C.13-1
BASIC FILM SESSION PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute name" meaning="Tag"/><term value="Number of Copies" meaning="(2000,0010)"/><term value="Print Priority" meaning="(2000,0020)"/><term value="Medium Type" meaning="(2000,0030)"/><term value="Film Destination" meaning="(2000,0040)"/><term value="Film Session Label" meaning="(2000,0050)"/><term value="Memory Allocation" meaning="(2000,0060)"/><term value="Owner ID" meaning="(2100,0160)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="0050" name="&gt;&gt;Film Size ID">
      <description>See C.13.3</description>
      <section ref="C.13.3" name="">Table C.13-3
BASIC FILM BOX PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Image Display Format" meaning="(2010,0010)"/><term value="Annotation Display Format ID" meaning="(2010,0030)"/><term value="Film Orientation" meaning="(2010,0040)"/><term value="Film Size ID" meaning="(2010,0050)"/><term value="Magnification Type" meaning="(2010,0060)"/><term value="Smoothing Type" meaning="(2010,0080)"/><term value="Border Density" meaning="(2010,0100)"/><term value="Empty Image Density" meaning="(2010,0110)"/><term value="Min Density" meaning="(2010,0120)"/><term value="Max Density" meaning="(2010,0130)"/><term value="Trim" meaning="(2010,0140)"/><term value="Configuration Information" meaning="(2010,0150)"/><term value="Illumination" meaning="(2010,015E)"/><term value="Reflected Ambient Light" meaning="(2010,0160)"/><term value="Requested Resolution ID" meaning="(2020,0050)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="0120" name="&gt;&gt;Min Density">
      <description>Minimum density that can be printed, expressed in hundredths of OD.</description>
    </entry>
    <entry group="2010" element="0130" name="&gt;&gt;Max Density">
      <description>Maximum density that can be printed, expressed in hundredths of OD.</description>
    </entry>
    <entry group="2000" element="00A8" name="&gt;Supported Image Display Formats Sequence">
      <description>A sequence which specifies the Image Display Formats supported, rows and columns in Image Boxes for each format, pixel spacing, and whether Requested Image Size is supported as a function of Film Orientation, Film Size ID, and Printer Resolution ID.
One item for each display format, film orientation, film size, and printer resolution combination shall be included.</description>
    </entry>
    <entry group="0028" element="0010" name="&gt;&gt;Rows">
      <description>Number of printable rows in an Image Box.</description>
    </entry>
    <entry group="0028" element="0011" name="&gt;&gt;Columns">
      <description>Number of printable columns in an Image Box</description>
    </entry>
    <entry group="2010" element="0010" name="&gt;&gt;Image Display Format">
      <description>See C.13.3</description>
      <section ref="C.13.3" name="">Table C.13-3
BASIC FILM BOX PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Image Display Format" meaning="(2010,0010)"/><term value="Annotation Display Format ID" meaning="(2010,0030)"/><term value="Film Orientation" meaning="(2010,0040)"/><term value="Film Size ID" meaning="(2010,0050)"/><term value="Magnification Type" meaning="(2010,0060)"/><term value="Smoothing Type" meaning="(2010,0080)"/><term value="Border Density" meaning="(2010,0100)"/><term value="Empty Image Density" meaning="(2010,0110)"/><term value="Min Density" meaning="(2010,0120)"/><term value="Max Density" meaning="(2010,0130)"/><term value="Trim" meaning="(2010,0140)"/><term value="Configuration Information" meaning="(2010,0150)"/><term value="Illumination" meaning="(2010,015E)"/><term value="Reflected Ambient Light" meaning="(2010,0160)"/><term value="Requested Resolution ID" meaning="(2020,0050)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="0040" name="&gt;&gt;Film Orientation">
      <description>See C.13.3</description>
      <section ref="C.13.3" name="">Table C.13-3
BASIC FILM BOX PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Image Display Format" meaning="(2010,0010)"/><term value="Annotation Display Format ID" meaning="(2010,0030)"/><term value="Film Orientation" meaning="(2010,0040)"/><term value="Film Size ID" meaning="(2010,0050)"/><term value="Magnification Type" meaning="(2010,0060)"/><term value="Smoothing Type" meaning="(2010,0080)"/><term value="Border Density" meaning="(2010,0100)"/><term value="Empty Image Density" meaning="(2010,0110)"/><term value="Min Density" meaning="(2010,0120)"/><term value="Max Density" meaning="(2010,0130)"/><term value="Trim" meaning="(2010,0140)"/><term value="Configuration Information" meaning="(2010,0150)"/><term value="Illumination" meaning="(2010,015E)"/><term value="Reflected Ambient Light" meaning="(2010,0160)"/><term value="Requested Resolution ID" meaning="(2020,0050)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="0050" name="&gt;&gt;Film Size ID">
      <description>See C.13.3</description>
      <section ref="C.13.3" name="">Table C.13-3
BASIC FILM BOX PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Image Display Format" meaning="(2010,0010)"/><term value="Annotation Display Format ID" meaning="(2010,0030)"/><term value="Film Orientation" meaning="(2010,0040)"/><term value="Film Size ID" meaning="(2010,0050)"/><term value="Magnification Type" meaning="(2010,0060)"/><term value="Smoothing Type" meaning="(2010,0080)"/><term value="Border Density" meaning="(2010,0100)"/><term value="Empty Image Density" meaning="(2010,0110)"/><term value="Min Density" meaning="(2010,0120)"/><term value="Max Density" meaning="(2010,0130)"/><term value="Trim" meaning="(2010,0140)"/><term value="Configuration Information" meaning="(2010,0150)"/><term value="Illumination" meaning="(2010,015E)"/><term value="Reflected Ambient Light" meaning="(2010,0160)"/><term value="Requested Resolution ID" meaning="(2020,0050)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="0052" name="&gt;&gt;Printer Resolution ID">
      <description>Printer Resolution identification. Defined Terms are the same as Requested Resolution ID (2020,0050). See C.13.3.</description>
      <section ref="C.13.3" name="">Table C.13-3
BASIC FILM BOX PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Image Display Format" meaning="(2010,0010)"/><term value="Annotation Display Format ID" meaning="(2010,0030)"/><term value="Film Orientation" meaning="(2010,0040)"/><term value="Film Size ID" meaning="(2010,0050)"/><term value="Magnification Type" meaning="(2010,0060)"/><term value="Smoothing Type" meaning="(2010,0080)"/><term value="Border Density" meaning="(2010,0100)"/><term value="Empty Image Density" meaning="(2010,0110)"/><term value="Min Density" meaning="(2010,0120)"/><term value="Max Density" meaning="(2010,0130)"/><term value="Trim" meaning="(2010,0140)"/><term value="Configuration Information" meaning="(2010,0150)"/><term value="Illumination" meaning="(2010,015E)"/><term value="Reflected Ambient Light" meaning="(2010,0160)"/><term value="Requested Resolution ID" meaning="(2020,0050)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="0376" name="&gt;&gt;Printer Pixel Spacing">
      <description>Physical distance on the printed film between the center of each pixel, specified by a numeric pair - adjacent row spacing (delimiter) adjacent column spacing in mm. See 10.7.1.3 for further explanation of the value order.</description>
    </entry>
    <entry group="2020" element="00A0" name="&gt;&gt;Requested Image Size Flag">
      <description>Indicates whether the printer supports Requested Image Size (2020,0030) for this display format and film orientation and size combination.
Enumerated Values:
NO = not supported
YES = supported</description>
    </entry>
    <entry group="2010" element="0054" name="&gt;Default Printer Resolution ID">
      <description>The printer's default resolution identification. Defined Terms are the same as Requested Resolution ID (2020,0050). See C.13.3.</description>
      <section ref="C.13.3" name="">Table C.13-3
BASIC FILM BOX PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Image Display Format" meaning="(2010,0010)"/><term value="Annotation Display Format ID" meaning="(2010,0030)"/><term value="Film Orientation" meaning="(2010,0040)"/><term value="Film Size ID" meaning="(2010,0050)"/><term value="Magnification Type" meaning="(2010,0060)"/><term value="Smoothing Type" meaning="(2010,0080)"/><term value="Border Density" meaning="(2010,0100)"/><term value="Empty Image Density" meaning="(2010,0110)"/><term value="Min Density" meaning="(2010,0120)"/><term value="Max Density" meaning="(2010,0130)"/><term value="Trim" meaning="(2010,0140)"/><term value="Configuration Information" meaning="(2010,0150)"/><term value="Illumination" meaning="(2010,015E)"/><term value="Reflected Ambient Light" meaning="(2010,0160)"/><term value="Requested Resolution ID" meaning="(2020,0050)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="00A6" name="&gt;Default Magnification Type">
      <description>Printer's default magnification type. See C.13.3 for Defined Terms.</description>
      <section ref="C.13.3" name="">Table C.13-3
BASIC FILM BOX PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Image Display Format" meaning="(2010,0010)"/><term value="Annotation Display Format ID" meaning="(2010,0030)"/><term value="Film Orientation" meaning="(2010,0040)"/><term value="Film Size ID" meaning="(2010,0050)"/><term value="Magnification Type" meaning="(2010,0060)"/><term value="Smoothing Type" meaning="(2010,0080)"/><term value="Border Density" meaning="(2010,0100)"/><term value="Empty Image Density" meaning="(2010,0110)"/><term value="Min Density" meaning="(2010,0120)"/><term value="Max Density" meaning="(2010,0130)"/><term value="Trim" meaning="(2010,0140)"/><term value="Configuration Information" meaning="(2010,0150)"/><term value="Illumination" meaning="(2010,015E)"/><term value="Reflected Ambient Light" meaning="(2010,0160)"/><term value="Requested Resolution ID" meaning="(2020,0050)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="00A7" name="&gt;Other Magnification Types Available">
      <description>Other magnification types available in the printer. See C.13.3 for Defined Terms.</description>
      <section ref="C.13.3" name="">Table C.13-3
BASIC FILM BOX PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Image Display Format" meaning="(2010,0010)"/><term value="Annotation Display Format ID" meaning="(2010,0030)"/><term value="Film Orientation" meaning="(2010,0040)"/><term value="Film Size ID" meaning="(2010,0050)"/><term value="Magnification Type" meaning="(2010,0060)"/><term value="Smoothing Type" meaning="(2010,0080)"/><term value="Border Density" meaning="(2010,0100)"/><term value="Empty Image Density" meaning="(2010,0110)"/><term value="Min Density" meaning="(2010,0120)"/><term value="Max Density" meaning="(2010,0130)"/><term value="Trim" meaning="(2010,0140)"/><term value="Configuration Information" meaning="(2010,0150)"/><term value="Illumination" meaning="(2010,015E)"/><term value="Reflected Ambient Light" meaning="(2010,0160)"/><term value="Requested Resolution ID" meaning="(2020,0050)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="00A8" name="&gt;Default Smoothing Type">
      <description>Printer's default smoothing type. See C.13.3.</description>
      <section ref="C.13.3" name="">Table C.13-3
BASIC FILM BOX PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Image Display Format" meaning="(2010,0010)"/><term value="Annotation Display Format ID" meaning="(2010,0030)"/><term value="Film Orientation" meaning="(2010,0040)"/><term value="Film Size ID" meaning="(2010,0050)"/><term value="Magnification Type" meaning="(2010,0060)"/><term value="Smoothing Type" meaning="(2010,0080)"/><term value="Border Density" meaning="(2010,0100)"/><term value="Empty Image Density" meaning="(2010,0110)"/><term value="Min Density" meaning="(2010,0120)"/><term value="Max Density" meaning="(2010,0130)"/><term value="Trim" meaning="(2010,0140)"/><term value="Configuration Information" meaning="(2010,0150)"/><term value="Illumination" meaning="(2010,015E)"/><term value="Reflected Ambient Light" meaning="(2010,0160)"/><term value="Requested Resolution ID" meaning="(2020,0050)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="00A9" name="&gt;Other Smoothing Types Available">
      <description>Other smoothing types available in the printer. See C.13.3.</description>
      <section ref="C.13.3" name="">Table C.13-3
BASIC FILM BOX PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Image Display Format" meaning="(2010,0010)"/><term value="Annotation Display Format ID" meaning="(2010,0030)"/><term value="Film Orientation" meaning="(2010,0040)"/><term value="Film Size ID" meaning="(2010,0050)"/><term value="Magnification Type" meaning="(2010,0060)"/><term value="Smoothing Type" meaning="(2010,0080)"/><term value="Border Density" meaning="(2010,0100)"/><term value="Empty Image Density" meaning="(2010,0110)"/><term value="Min Density" meaning="(2010,0120)"/><term value="Max Density" meaning="(2010,0130)"/><term value="Trim" meaning="(2010,0140)"/><term value="Configuration Information" meaning="(2010,0150)"/><term value="Illumination" meaning="(2010,015E)"/><term value="Reflected Ambient Light" meaning="(2010,0160)"/><term value="Requested Resolution ID" meaning="(2020,0050)"/><term value="ICC Profile" meaning="(0028,2000)"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="2010" element="0152" name="&gt;Configuration Information Description">
      <description>A free form text description of Configuration Information (2010,0150) supported by the printer.</description>
    </entry>
    <entry group="2010" element="0154" name="&gt;Maximum Collated Films">
      <description>The maximum number of films that can be collated for an N-ACTION of the Film Session. The value shall be 0 if N-ACTION of the Film Session is not supported.</description>
    </entry>
    <entry group="2020" element="00A2" name="&gt;Decimate/Crop Result">
      <description>Indicates whether the printer will decimate or crop image pixels if the image rows or columns is greater than the available printable pixels in an Image Box.
See C.13.5.
Enumerated Values when the printer does not support Requested Decimate/Crop Behavior (2020,0040):
DECIMATE = image will be decimated to fit.
CROP = image will be cropped to fit.
FAIL = N-SET of the Image Box will fail
Enumerated Values when the printer supports Requested Decimate/Crop Behavior (2020,0040):

DEF DECIMATE = image will be decimated to fit.
DEF CROP = image will be cropped to fit
DEF FAIL = N-SET of the Image Box will fail
This value indicates the printer default if the SCU does not create or set Requested Decimate/Crop Behavior for the Image Box.</description>
      <section ref="C.13.5" name="">Table C.13-5
IMAGE BOX PIXEL PRESENTATION MODULE ATTRIBUTES
<unrecognized-rows><term value="Attribute Name" meaning="Tag"/><term value="Image Box Position" meaning="(2020,0010)"/><term value="Polarity" meaning="(2020,0020)"/><term value="Magnification Type" meaning="(2010,0060)"/><term value="Smoothing Type" meaning="(2010,0080)"/><term value="Configuration Information" meaning="(2010,0150)"/><term value="Requested Image Size" meaning="(2020,0030)"/><term value="Requested Decimate/Crop Behavior" meaning="(2020,0040)"/><term value="Basic Grayscale Image Sequence" meaning="(2020,0110)"/><term value="&gt;Samples Per Pixel" meaning="(0028,0002)"/><term value="&gt;Photometric Interpretation" meaning="(0028,0004)"/><term value="&gt;Rows" meaning="(0028,0010)"/><term value="&gt;Columns" meaning="(0028,0011)"/><term value="&gt;Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="&gt;Bits Allocated" meaning="(0028,0100)"/><term value="&gt;Bits Stored" meaning="(0028,0101)"/><term value="&gt;High Bit" meaning="(0028,0102)"/><term value="&gt;Pixel Representation" meaning="(0028,0103)"/><term value="&gt;Pixel Data" meaning="(7FE0,0010)"/><term value="Basic Color Image Sequence" meaning="(2020,0111)"/><term value="&gt;Samples Per Pixel" meaning="(0028,0002)"/><term value="&gt;Photometric Interpretation" meaning="(0028,0004)"/><term value="&gt;Planar Configuration" meaning="(0028,0006)"/><term value="&gt;Rows" meaning="(0028,0010)"/><term value="&gt;Columns" meaning="(0028,0011)"/><term value="&gt;Pixel Aspect Ratio" meaning="(0028,0034)"/><term value="&gt;Bits Allocated" meaning="(0028,0100)"/><term value="&gt;Bits Stored" meaning="(0028,0101)"/><term value="&gt;High Bit" meaning="(0028,0102)"/><term value="&gt;Pixel Representation" meaning="(0028,0103)"/><term value="&gt;Pixel Data" meaning="(7FE0,0010)"/></unrecognized-rows>
Note:  Referenced Image Overlay Box Sequence (2020,0130) and Original Image Sequence (2130,00C0) were previously included in this Module but have been retired. See PS 3.3 2004.

</section>
    </entry>
  </module>
  <module ref="C.14" table="C.14-1" name="Storage Commitment Module Attributes">
    <entry group="0008" element="1195" name="Transaction UID">
      <description>Uniquely identifies this Storage Commitment transaction.</description>
    </entry>
    <entry group="0008" element="0054" name="Retrieve AE Title">
      <description>Application Entity Title where the SOP Instance(s) may be retrieved via a network based retrieve service.</description>
    </entry>
    <entry group="0088" element="0130" name="Storage Media File-Set ID">
      <description>User or implementation specific human readable identification of a Storage Media on which the SOP Instances reside.</description>
    </entry>
    <entry group="0088" element="0140" name="Storage Media File-Set UID">
      <description>Uniquely identifies a Storage Media on which the SOP Instances reside.</description>
    </entry>
    <entry group="0008" element="1199" name="Referenced SOP Sequence">
      <description>A sequence of Items where each Item references a single SOP Instance for which storage commitment is requested / or has been provided.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0008" element="0054" name="&gt;Retrieve AE Title">
      <description>Application Entity Title from which the SOP Instance may be retrieved via a network based retrieve service.</description>
    </entry>
    <entry group="0088" element="0130" name="&gt;Storage Media File-Set ID">
      <description>The user or implementation specific human readable identifier that identifies a Storage Media on which this SOP Instance resides.</description>
    </entry>
    <entry group="0088" element="0140" name="&gt;Storage Media File-Set UID">
      <description>Uniquely identifies a Storage Media on which this SOP Instance resides.</description>
    </entry>
    <entry group="0008" element="1198" name="Failed SOP Sequence">
      <description>A sequence of Items where each Item references a single SOP Instance for which storage commitment could not be provided.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0008" element="1197" name="&gt;Failure Reason">
      <description>The reason that storage commitment could not be provided for this SOP Instance.
See Section C.14.1.1.</description>
      <section ref="C.14.1.1" name="">The following values and semantics shall be used for the Failure Reason Attribute :
0110H - Processing failure
A general failure in processing the operation was encountered.
0112H - No such object instance
One or more of the elements in the Referenced SOP Instance Sequence was not available.
0213H - Resource limitation
The SCP does not currently have enough resources to store the requested SOP Instance(s).
0122H - Referenced SOP Class not supported
Storage Commitment has been requested for a SOP Instance with a SOP Class that is not supported by the SCP.
0119H - Class / Instance conflict
The SOP Class of an element in the Referenced SOP Instance Sequence did not correspond to the SOP class registered for this SOP Instance at the SCP.
0131H - Duplicate transaction UID
The Transaction UID of the Storage Commitment Request is already in use.

</section>
    </entry>
  </module>
  <module ref="C.17.1" table="C.17-1" name="SR Document Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Modality type.
Enumerated Value:
SR = SR Document</description>
    </entry>
    <entry group="0020" element="000E" name="Series Instance UID" type="1">
      <description>Unique identifier of the Series.
Note: No SR-specific semantics are specified.</description>
    </entry>
    <entry group="0020" element="0011" name="Series Number" type="1">
      <description>A number that identifies the Series.
Note: No SR-specific semantics are specified.</description>
    </entry>
    <entry group="0008" element="0021" name="Series Date" type="3">
      <description>Date the Series started.</description>
    </entry>
    <entry group="0008" element="0031" name="Series Time" type="3">
      <description>Time the Series started.</description>
    </entry>
    <entry group="0008" element="103E" name="Series Description" type="3">
      <description>User provided description of the Series</description>
    </entry>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence" type="2">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance for which the Series is created. Zero or one item shall be present in the sequence.
Notes: 1. The Performed Procedure Step referred to by this Attribute is the Step during which this Document is generated.
2. If this Document is generated during the same Modality or General Purpose Performed Procedure Step as the evidence in the current interpretation procedure, this attribute may contain reference to that Modality or General Purpose Performed Procedure Step.
3. This Attribute is not used to convey reference to the evidence in the current interpretation procedure. See Current Requested Procedure Evidence Sequence (0040,A375).
4. This Sequence may be sent zero length if the Performed Procedure Step is unknown.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.17.2" table="C.17-2" name="SR Document General Module Attributes">
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description>A number that identifies the SR Document.</description>
    </entry>
    <entry group="0040" element="A491" name="Completion Flag" type="1">
      <description>The estimated degree of completeness of this SR Document with respect to externally defined criteria in a manner specified in the Conformance Statement.
Note: It may be desirable to make these criteria adaptable to local policies or user decisions.
Enumerated Values:
PARTIAL = Partial content.
COMPLETE = Complete content.</description>
    </entry>
    <entry group="0040" element="A492" name="Completion Flag Description" type="3">
      <description>Explanation of the value sent in Completion Flag (0040,A491).</description>
    </entry>
    <entry group="0040" element="A493" name="Verification Flag" type="1">
      <description>Indicates whether this SR Document is Verified. Enumerated Values:
UNVERIFIED = Not attested to.
VERIFIED = Attested to by a Verifying Observer Name (0040,A075) who is accountable for its content.
Note: The intent of this specification is that the "prevailing final version" of an SR Document is the version having the most recent Verification DateTime (0040,A030), Completion Flag (0040,A491) of COMPLETE and Verification Flag (0040,A493) of VERIFIED.</description>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the document content creation started.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the document content creation started.</description>
    </entry>
    <entry group="0040" element="A073" name="Verifying Observer Sequence" type="1C">
      <description>The person or persons authorized to verify documents of this type and accept responsibility for the content of this document. One or more Items may be included in this sequence.
Required if Verification Flag (0040,A493) is VERIFIED.
Note: In HL7 Structured Documents, the comparable attribute is the "legalAuthenticator".</description>
    </entry>
    <entry group="0040" element="A075" name="&gt;Verifying Observer Name" type="1">
      <description>The person authorized by the Verifying Organization (0040,A027) to verify documents of this type and who accepts responsibility for the content of this document.</description>
    </entry>
    <entry group="0040" element="A088" name="&gt;Verifying Observer Identification Code Sequence" type="2">
      <description>Coded identifier of Verifying Observer. Zero or one Items shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID defined."/>
    <entry group="0040" element="A027" name="&gt;Verifying Organization" type="1">
      <description>Organization to which the Verifying Observer Name (0040,A075) is accountable in the current interpretation procedure.</description>
    </entry>
    <entry group="0040" element="A030" name="&gt;Verification DateTime" type="1">
      <description>Date and Time of verification by the Verifying Observer Name (0040,A075).</description>
    </entry>
    <entry group="0040" element="A078" name="Author Observer Sequence" type="3">
      <description>The person or device that created the clinical content of this document. This attribute sets the default Observer Context for the root of the content tree.
One or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Identified Person or Device Macro' Table C.17-3b"/>
    <entry group="0040" element="A07A" name="Participant Sequence" type="3">
      <description>Persons or devices related to the clinical content of this document.
One or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0040" element="A080" name="&gt;Participation Type" type="1">
      <description>Participant's role with respect to the clinical content of this document. See C.17.2.5.
Defined Terms:
SOURCE - Equipment that contributed to the content
ENT - Data enterer (e.g., transcriptionist)
ATTEST - Attestor
Note: In HL7 Structured Documents, the participation comparable to Attestor is the "Authenticator".</description>
      <section ref="C.17.2.5" name="">The Verifying Observer Sequence (0040,A073), Author Observer Sequence (0040,A078), and Participant Sequence (0040,A07A) identify significant contributors to the SR document. The Author creates the clinical content of the document. The Verifying Observer verifies and accepts legal responsibility for the content. Other participants may include an Attestor, a person identified as a Participant who “signs” an SR document, but who does not have legal authority to verify the clinical content. E.g., an SR document may be authored and attested by a resident, and then verified by a staff physician; or a document may be authored by a CAD device and attested by a technologist, and then verified by a physician; or a technologist working with a measurement software package may be the author, the package is a Source participant, and the final content is verified by a physician.
An individual shall not be identified in both the Verifying Observer Sequence (as the legal authenticator) and in the Participant Sequence as an Attestor. An individual may be identified in both the Author Observer Sequence and either the Verifying Observer Sequence or the Participant Sequence.
The participation DateTime for the Verifying Observer is conveyed in Verification DateTime (0040,A030) within the Verifying Observer Sequence, for the Author Observer in the Observation DateTime (0040,A032) in the main Data Set (see C.17.3), and for other participants in Participation DateTime (0040,A082) within the Participant Sequence.
</section>
    </entry>
    <entry group="0040" element="A082" name="&gt;Participation DateTime" type="2">
      <description>DateTime of participation with respect to the clinical content of this document.</description>
    </entry>
    <include ref="&gt;Include 'Identified Person or Device Macro' Table C.17-3b"/>
    <entry group="0040" element="A07C" name="Custodial Organization Sequence" type="3">
      <description>Custodial organization for this SR Document instance. Represents the organization from which the document originates and that is in charge of maintaining the document, i.e., the steward of the original source document.
Note: This may or may not be identical to the Institution identified in the Equipment Module.
Only a single item shall be present in this sequence.</description>
    </entry>
    <entry group="0008" element="0080" name="&gt;Institution Name" type="2">
      <description>Name of Custodial Institution or Organization.</description>
    </entry>
    <entry group="0008" element="0082" name="&gt;Institution Code Sequence" type="2">
      <description>Coded identifier of Custodial Institution or Organization.
Zero or one Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID defined."/>
    <entry group="0040" element="A360" name="Predecessor Documents Sequence" type="1C">
      <description>Shall refer to SR SOP Instances (e.g. prior or provisional reports) whose content has been wholly or partially included in this document with or without modification. One or more Items may be included in this sequence.
Required if this document includes content from other documents.
Note: The amendment process of an existing SR Document is not explicitly described, but several approaches may be considered. One may choose, for example, to create a new SR Document that includes the original content with any amendments applied or included. The structure of this amended SR Document may or may not reflect what was amended. However, the use of the Predecessor Document Sequence allows tracing back to the input SR Document, which in this case is the previous version.</description>
    </entry>
    <include ref="&gt;Include ' Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0040" element="A525" name="Identical Documents Sequence" type="1C">
      <description>Duplicates of this document, stored with different SOP Instance UIDs. One or more Items may be included in this sequence.
Required if this document is stored with different SOP Instance UIDs in one or more other Studies.
See C.17.2.2 for further explanation.</description>
      <section ref="C.17.2.2" name="">If identical copies of an SR Document are to be included in multiple Studies then the entire SR Document shall be duplicated with appropriate changes for inclusion into the different Studies (i.e. Study Instance UID, Series Instance UID, SOP Instance UID, Identical Documents Sequence etc.). The Identical Documents Sequence Attribute in each SOP Instance shall contain references to all other duplicate SOP Instances.
Note: If an SR Document contains an Identical Documents Sequence then it will not be further duplicated without producing a new complete set of duplicate SOP Instances with re-generated Identical Documents Sequences. This is a consequence of the rules for modification of SR Document content in PS3.4. For example, if there are two identical reports and an application is creating a third identical report, then the first two reports must be re-generated in order that their Identical Documents Sequence will reference the new duplicate document and all other identical documents.

If a new SR Document is created using content from an SR Document that contains an Identical Documents Sequence and is part of the same Requested Procedure, then the new SR Document shall only contain a new Identical Documents Sequence if the new SR Document is duplicated. The Predecessor Documents Sequence in all the new SR Documents shall contain references to the original SR Document and all its duplicates as well as any other documents from which content is included.
Note:  It is up to an implementation to decide whether a new SR Document is duplicated across multiple Studies. This may require user input to make the decision.

</section>
    </entry>
    <include ref="&gt;Include ' Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0040" element="A370" name="Referenced Request Sequence" type="1C">
      <description>Identifies Requested Procedures which are being fulfilled (completely or partially) by creation of this Document. One or more Items may be included in this sequence.
Required if this Document fulfills at least one Requested Procedure.</description>
    </entry>
    <entry group="0020" element="000D" name="&gt;Study Instance UID" type="1">
      <description>Unique identifier for the Study.</description>
    </entry>
    <entry group="0008" element="1110" name="&gt;Referenced Study Sequence" type="2">
      <description>Uniquely identifies the Study SOP Instance.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt; Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0008" element="0050" name="&gt;Accession Number" type="2">
      <description>A departmental IS generated number which identifies the order for the Study.</description>
    </entry>
    <entry group="0040" element="2016" name="&gt;Placer Order Number/Imaging Service Request" type="2">
      <description>The order number assigned to the Imaging Service Request by the party placing the order.</description>
    </entry>
    <entry group="0040" element="2017" name="&gt;Filler Order Number/Imaging Service Request" type="2">
      <description>The order number assigned to the Imaging Service Request by the party filling the order.</description>
    </entry>
    <entry group="0040" element="1001" name="&gt;Requested Procedure ID" type="2">
      <description>Identifier of the related Requested Procedure</description>
    </entry>
    <entry group="0032" element="1060" name="&gt;Requested Procedure Description" type="2">
      <description>Institution-generated administrative description or classification of Requested Procedure.</description>
    </entry>
    <entry group="0032" element="1064" name="&gt;Requested Procedure Code Sequence" type="2">
      <description>A sequence that conveys the requested procedure. Zero or one Item may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID Number is specified."/>
    <entry group="0040" element="1002" name="&gt;Reason for the Requested Procedure" type="3">
      <description>Reason for requesting this procedure.</description>
    </entry>
    <entry group="0040" element="100A" name="&gt;Reason for Requested Procedure Code Sequence" type="3">
      <description>Coded Reason for requesting this procedure.
One or more sequence items may be present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID Number is specified."/>
    <entry group="0040" element="A372" name="Performed Procedure Code Sequence" type="2">
      <description>A Sequence that conveys the codes of the performed procedures pertaining to this SOP Instance. Zero or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID Number is specified."/>
    <entry group="0040" element="A375" name="Current Requested Procedure Evidence Sequence" type="1C">
      <description>Full set of Composite SOP Instances, of which the creator is aware, which were created to satisfy the current Requested Procedure(s) for which this SR Document is generated or that are referenced in the content tree. One or more Items may be included in this sequence.
Required if the creator is aware of Composite Objects acquired in order to satisfy the Requested Procedure(s) for which the SR Document is or if instances are referenced in the content tree. May be present otherwise.
See C.17.2.3 for further explanation.</description>
      <section ref="C.17.2.3" name="">The intent of the Current Requested Procedure Evidence Sequence (0040,A375) is to reference all evidence created in order to satisfy the current Requested Procedure(s) for this SR Document. This shall include, but is not limited to, all current evidence referenced in the content tree.
For a completed SR Document satisfying (i.e., being the final report for) the current Requested Procedure(s), this sequence shall list the full set of Composite SOP Instances created for the current Requested Procedure(s). For other SOP Instances that include the SR Document General Module, this sequence shall contain at minimum the set of Composite SOP Instances from the current Requested Procedure(s) that are referenced in the content tree.
The Pertinent Other Evidence Sequence (0040,A385) attribute is used to reference all other evidence considered pertinent for this SR Document that is not listed in the Current Requested Procedure Evidence Sequence (0040,A375).
This requires that the same SOP Instance shall not be referenced in both of these Sequences.
For the purposes of inclusion in the Current Requested Procedure Evidence Sequence (0040,A375) and the Pertinent Other Evidence Sequence (0040,A385), the set of Composite SOP Instances is defined to include not only the images and waveforms referenced in the content tree, but also all presentation states, real world value maps and other accompanying composite instances that are referenced from the content items.
</section>
    </entry>
    <include ref="&gt;Include ' Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0040" element="A385" name="Pertinent Other Evidence Sequence" type="1C">
      <description>Other Composite SOP Instances that are considered to be pertinent evidence by the creator of this SR Document. This evidence must have been acquired in order to satisfy Requested Procedures other than the one(s) for which this SR Document is generated. One or more Items may be included in this sequence.
Required if pertinent evidence from other Requested Procedures needs to be recorded.
See C.17.2.3 for further explanation.</description>
      <section ref="C.17.2.3" name="">The intent of the Current Requested Procedure Evidence Sequence (0040,A375) is to reference all evidence created in order to satisfy the current Requested Procedure(s) for this SR Document. This shall include, but is not limited to, all current evidence referenced in the content tree.
For a completed SR Document satisfying (i.e., being the final report for) the current Requested Procedure(s), this sequence shall list the full set of Composite SOP Instances created for the current Requested Procedure(s). For other SOP Instances that include the SR Document General Module, this sequence shall contain at minimum the set of Composite SOP Instances from the current Requested Procedure(s) that are referenced in the content tree.
The Pertinent Other Evidence Sequence (0040,A385) attribute is used to reference all other evidence considered pertinent for this SR Document that is not listed in the Current Requested Procedure Evidence Sequence (0040,A375).
This requires that the same SOP Instance shall not be referenced in both of these Sequences.
For the purposes of inclusion in the Current Requested Procedure Evidence Sequence (0040,A375) and the Pertinent Other Evidence Sequence (0040,A385), the set of Composite SOP Instances is defined to include not only the images and waveforms referenced in the content tree, but also all presentation states, real world value maps and other accompanying composite instances that are referenced from the content items.
</section>
    </entry>
    <include ref="&gt;Include ' Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0008" element="114A" name="Referenced Instance Sequence" type="1C">
      <description>Sequence specifying SOP Instances significantly related to the current SOP Instance. Such referenced Instances may include equivalent documents or renderings of this document.
One or more Items may be included in this sequence.
Required if the identity of a CDA Document equivalent to the current SOP Instance is known at the time of creation of this SOP Instance (see C.17.2.6). May be present otherwise.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="1">
      <description>Code describing the purpose of the reference to the Instance(s). Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is CID 7006."/>
  </module>
  <macro table="C.17-3" name="Hierarchical SOP Instance Reference Macro Attributes">
    <entry group="0020" element="000D" name="Study Instance UID" type="1">
      <description>Unique identifier for the Study</description>
    </entry>
    <entry group="0008" element="1115" name="Referenced Series Sequence" type="1">
      <description>Sequence of Items where each Item includes the Attributes of a Series containing referenced Composite Object(s). One or more Items may be included in this sequence</description>
    </entry>
    <include ref="&gt;Include 'Hierarchical Series Reference Macro' Table C.17-3a"/>
  </macro>
  <macro table="C.17-3b" name="Identified Person or Device Macro Attributes">
    <entry group="0040" element="A084" name="Observer Type" type="1">
      <description>Enumerated Values:
PSN - Person
DEV - Device</description>
    </entry>
    <entry group="0040" element="A123" name="Person Name" type="1C">
      <description>Name of the person observer for this document Instance.
Required if Observer Type value is PSN.</description>
    </entry>
    <entry group="0040" element="1101" name="Person Identification Code Sequence" type="2C">
      <description>Coded identifier of person observer. Zero or one Items shall be permitted in this sequence.
Required if Observer Type value is PSN.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID defined"/>
    <entry group="0008" element="1010" name="Station Name" type="2C">
      <description>Name of the device observer for this document instance.
Required if Observer Type value is DEV.</description>
    </entry>
    <entry group="0018" element="1002" name="Device UID" type="1C">
      <description>Unique identifier of device observer.
Required if Observer Type value is DEV.</description>
    </entry>
    <entry group="0008" element="0070" name="Manufacturer" type="1C">
      <description>Manufacturer of the device observer.
Required if Observer Type value is DEV.</description>
    </entry>
    <entry group="0008" element="1090" name="Manufacturer's Model Name" type="1C">
      <description>Model Name of the device observer.
Required if Observer Type value is DEV.</description>
    </entry>
    <entry group="0008" element="0080" name="Institution Name" type="2">
      <description>Institution or organization to which the identified person is responsible or accountable, or which manages the identified device.</description>
    </entry>
    <entry group="0008" element="0082" name="Institution Code Sequence" type="2">
      <description>Institution or organization to which the identified person is responsible or accountable, or which manages the identified device.
Zero or one Items shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID defined"/>
  </macro>
  <module ref="C.17.3" table="C.17-4" name="SR Document Content Module Attributes">
    <include ref="Include Document Content Macro Table C.17-5. with a Value Type (0040,A040) of CONTAINER"/>
    <include ref="Include Document Relationship Macro Table C.17-6."/>
  </module>
  <macro table="C.17-5" name="Document Content Macro Attributes">
    <entry group="0040" element="A040" name="Value Type" type="1">
      <description>The type of the value encoded in this Content Item.
Defined Terms:
TEXT
NUM
CODE
DATETIME
DATE
TIME
UIDREF
PNAME
COMPOSITE
IMAGE
WAVEFORM
SCOORD
TCOORD
CONTAINER
See C.17.3.2.1 for further explanation.</description>
      <section ref="C.17.3.2.1" name="">The value of the name/value pair is encoded with one of the Value Types defined in Table C.17.3-7 (the choice of which may be constrained by the IOD in which this Module is contained). The Value Type (0040,A040) attribute explicitly conveys the type of Content Item value encoding.

Table C.17.3-7
VALUE TYPE DEFINITIONS
<unrecognized-rows><term value="Value Type" meaning="Concept Name"/><term value="TEXT" meaning="Type of text, e.g. &quot;Findings&quot;, or name of identifier, e.g. “Lesion ID”"/><term value="NUM" meaning="Type of numeric value or measurement, e.g. &quot;BPD&quot;"/><term value="CODE" meaning="Type of code, e.g. &quot;Findings&quot;"/><term value="DATETIME" meaning="Type of DateTime, e.g. &quot;Date/Time of onset&quot;"/><term value="DATE" meaning="Type of Date, e.g. &quot;Birth Date&quot;"/><term value="TIME" meaning="Type of Time, e.g &quot;Start Time&quot;"/><term value="UIDREF" meaning="Type of UID, e.g &quot;Study Instance UID&quot;"/><term value="PNAME" meaning="Role of person, e.g., &quot;Recording Observer&quot;"/><term value="COMPOSITE" meaning="Purpose of Reference"/><term value="IMAGE" meaning="Purpose of Reference"/><term value="WAVEFORM" meaning="Purpose of Reference"/><term value="SCOORD" meaning="Purpose of Reference"/><term value="TCOORD" meaning="Purpose of Reference"/><term value="CONTAINER" meaning="Document Title or document section heading. Concept Name conveys the Document Title (if the CONTAINER is the Document Root Content Item) or the category of observation."/></unrecognized-rows>
Note: It is recommended that drawings and sketches, sometimes used in reports, be represented byIMAGE Content Items that reference separate SOP Instances (e.g., 8-bit, MONOCHROME2, Secondary Capture, or Multi-frame Single Bit Secondary Capture).

</section>
    </entry>
    <entry group="0040" element="A043" name="Concept Name Code Sequence" type="1C">
      <description>Code describing the concept represented by this Content Item. Also conveys the value of Document Title and section headings in documents. Only a single Item shall be permitted in this sequence.
Required if Value Type (0040,A040) is TEXT or NUM or CODE or DATETIME or DATE or TIME or UIDREF or PNAME.
Required if Value Type (0040,A040) is CONTAINER and a heading is present, or this is the Root Content Item.
Note: That is, containers without headings do not require Concept Name Code Sequence
Required if Value Type (0040,A040) is COMPOSITE, IMAGE, WAVEFORM, SCOORD or TCOORD, and the Purpose of Reference is conveyed in the Concept Name.
See C.17.3.2.2 for further explanation.</description>
      <section ref="C.17.3.2.2" name="">The Concept Name Code Sequence (0040,A043) conveys the name of the concept whose value is expressed by the value attribute or set of attributes. Depending on the Value Type (0040,A040), the meaning of the Concept Name Code Sequence may reflect specifics of the use of the particular data type (see Table C.17.3-7).
</section>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID."/>
    <entry group="0040" element="A160" name="Text Value" type="1C">
      <description>This is the value of the Content Item.
Required if Value Type (0040,A040) is TEXT.
Text data which is unformatted and whose manner of display is implementation dependent.
The text value may contain spaces, as well as multiple lines separated by either LF, CR, CR LF or LF CR, but otherwise no format control characters (such as horizontal or vertical tab and form feed) shall be present, even if permitted by the Value Representation of UT.
The text shall be interpreted as specified by Specific Character Set (0008,0005) if present in the SOP Common Module.
Note: The text may contain single or multi-byte characters and use code extension techniques as described in PS 3.5 if permitted by the values of Specific Character Set (0008,0005).</description>
    </entry>
    <entry group="0040" element="A120" name="DateTime" type="1C">
      <description>This is the value of the Content Item.
Required if Value Type (0040,A040) is DATETIME.</description>
    </entry>
    <entry group="0040" element="A121" name="Date" type="1C">
      <description>This is the value of the Content Item.
Required if Value Type (0040,A040) is DATE.</description>
    </entry>
    <entry group="0040" element="A122" name="Time" type="1C">
      <description>This is the value of the Content Item.
Required if Value Type (0040,A040) is TIME.</description>
    </entry>
    <entry group="0040" element="A123" name="Person Name" type="1C">
      <description>This is the value of the Content Item.
Required if Value Type (0040,A040) is PNAME.</description>
    </entry>
    <entry group="0040" element="A124" name="UID" type="1C">
      <description>This is the value of the Content Item.
Required if Value Type (0040,A040) is UIDREF.</description>
    </entry>
    <include ref="Include 'Numeric Measurement Macro' Table C.18.1-1 if and only if Value Type (0040,A040) is NUM."/>
    <include ref="Include 'Code Macro' Table C.18.2-1 if and only if Value Type (0040,A040) is CODE."/>
    <include ref="Include 'Composite Object Reference Macro' Table C.18.3-1 if and only if Value Type (0040,A040) is COMPOSITE."/>
    <include ref="Include 'Image Reference Macro' Table C.18.4-1 if and only if Value Type (0040,A040) is IMAGE."/>
    <include ref="Include 'Waveform Reference Macro' Table C.18.5-1 if and only if Value Type (0040,A040) is WAVEFORM."/>
    <include ref="Include 'Spatial Coordinates Macro' Table C.18.6-1 if and only if Value Type (0040,A040) is SCOORD."/>
    <include ref="Include 'Temporal Coordinates Macro' Table C.18.7-1 if and only if Value Type (0040,A040) is TCOORD."/>
    <include ref="Include 'Container Macro' Table C.18.8-1 if and only if Value Type (0040,A040) is CONTAINER."/>
  </macro>
  <macro table="C.17-6" name="Document Relationship Macro Attributes">
    <entry group="0040" element="A032" name="Observation DateTime" type="1C">
      <description>The date and time on which this Content Item was completed. For the purpose of recording measurements or logging events, completion time is defined as the time of data acquisition of the measurement, or the time of occurrence of the event.
Required if the date and time are different from the Content Date (0008,0023) and Content Time (0008,0033) or the Observation DateTime (0040,A032) defined in higher items. May be present otherwise.
Note: When Content Items are copied into successor reports, the Content Date (0008,0023) and Content Time (0008,0033) of the new report are likely to be different than the date and time of the original observation. Therefore this attribute may need to be included in any copied Content Items to satisfy the condition.</description>
    </entry>
    <entry group="0040" element="A730" name="Content Sequence" type="1C">
      <description>A potentially recursively nested Sequence of Items that conveys content that is the Target of Relationships with the enclosing Source Content Item.
One or more Items may be included in this sequence.
Required if the enclosing Content Item has relationships.
Notes: 1. If this Attribute is not present then the enclosing Item is a leaf.
2. The order of Items within this Sequence is semantically significant for presentation.
See C.17.3.2.4 for further explanation.</description>
      <section ref="C.17.3.2.4" name="">The Content Sequence (0040,A730) provides the hierarchical structuring of the Content Tree (see C.17.3.1) by recursively nesting Content Items. A parent (or source) Content Item has an explicit relationship to each child (or target) Content Item, conveyed by the Relationship Type (0040,A010) attribute.
Table C.17.3-8 describes the Relationship Types between Source Content Items and the Target Content Items.
Table C.17.3-8
RELATIONSHIP TYPE DEFINITIONS
<unrecognized-rows><term value="Relationship Type" meaning="Description"/><term value="CONTAINS" meaning="Contains"/><term value="HAS OBS CONTEXT" meaning="Has Observation Context"/><term value="HAS CONCEPT MOD" meaning="Has Concept Modifier"/><term value="HAS PROPERTIES" meaning="Has Properties"/><term value="HAS ACQ CONTEXT" meaning="Has Acquisition Context"/><term value="INFERRED FROM" meaning="Inferred From"/><term value="SELECTED FROM" meaning="Selected From"/></unrecognized-rows>
         </section>
    </entry>
    <entry group="0040" element="A010" name="&gt;Relationship Type" type="1">
      <description>The type of relationship between the (enclosing) Source Content Item and the Target Content Item.
IODs specify additional constraints on Relationships (including lists of Enumerated Values).
Defined Terms:
CONTAINS
HAS PROPERTIES
HAS OBS CONTEXT
HAS ACQ CONTEXT
INFERRED FROM
SELECTED FROM
HAS CONCEPT MOD
See C.17.3.2.4 for further explanation.</description>
      <section ref="C.17.3.2.4" name="">The Content Sequence (0040,A730) provides the hierarchical structuring of the Content Tree (see C.17.3.1) by recursively nesting Content Items. A parent (or source) Content Item has an explicit relationship to each child (or target) Content Item, conveyed by the Relationship Type (0040,A010) attribute.
Table C.17.3-8 describes the Relationship Types between Source Content Items and the Target Content Items.
Table C.17.3-8
RELATIONSHIP TYPE DEFINITIONS
<unrecognized-rows><term value="Relationship Type" meaning="Description"/><term value="CONTAINS" meaning="Contains"/><term value="HAS OBS CONTEXT" meaning="Has Observation Context"/><term value="HAS CONCEPT MOD" meaning="Has Concept Modifier"/><term value="HAS PROPERTIES" meaning="Has Properties"/><term value="HAS ACQ CONTEXT" meaning="Has Acquisition Context"/><term value="INFERRED FROM" meaning="Inferred From"/><term value="SELECTED FROM" meaning="Selected From"/></unrecognized-rows>
         </section>
    </entry>
    <include ref="&gt;Include Document Relationship Macro Table C.17-6 if the Target Content Item is included by-value in the Source Content Item. The Macro shall not be present if the relationship is by-reference."/>
    <include ref="&gt;Include Document Content Macro Table C.17-5 if the Target Content Item is included by-value in the Source Content Item. The Macro shall not be present if the relationship is by-reference."/>
    <entry group="0040" element="DB73" name="&gt;Referenced Content Item Identifier" type="1C">
      <description>An ordered set of one or more integers that uniquely identifies the Target Content Item of the relationship.
The root Content Item is referenced by a single value of 1.
Each subsequent integer represents an ordinal position of a Content Item in the Content Sequence (0040,A730) in which it belongs. The Referenced Content Item Identifier is the set of these ordinal positions along the by-value relationship path. The number of values in this Multi-Value Attribute is exactly the number of relationships traversed in the SR content tree plus one.
Note: 1. See C.17.3.2.5.
2. Content Items are ordered in a Content Sequence starting from 1 as defined in VR of SQ (See PS 3.5).
Required if the Target Content Item is denoted by-reference, i.e. the Document Relationship Macro and Document Content Macro are not included.</description>
      <section ref="C.17.3.2.5" name="">Content Items are identified by their position in the Content Item tree. They have an implicit order as defined by the order of the Sequence Items. When a Content Item is the target of a by-reference relationship, its position is specified in the Referenced Content Item Identifier (0040,DB73) in a Content Sequence Item subsidiary to the source Content Item.
Note:  Figure C.17.3-3 illustrates an SR content tree and identifiers associated with each Content Item:

</section>
    </entry>
  </macro>
  <module ref="C.17.6.1" table="C.17.6-1" name="Key Object Document Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Modality type.
Enumerated Value:
KO = Key Object Selection</description>
    </entry>
    <entry group="0020" element="000E" name="Series Instance UID" type="1">
      <description>Unique identifier of the Series.
Note: No specific semantics are specified.</description>
    </entry>
    <entry group="0020" element="0011" name="Series Number" type="1">
      <description>A number that identifies the Series.
Note: No specific semantics are specified.</description>
    </entry>
    <entry group="0008" element="0021" name="Series Date" type="3">
      <description>Date the Series started.</description>
    </entry>
    <entry group="0008" element="0031" name="Series Time" type="3">
      <description>Time the Series started.</description>
    </entry>
    <entry group="0008" element="103E" name="Series Description" type="3">
      <description>User provided description of the Series</description>
    </entry>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence" type="2">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance for which the Series is created. Zero or one item shall be present in the sequence.
Notes: See notes on this attribute in Section C.17.1 SR Document Series Module</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.17.6.2" table="C.17.6-2" name="Key Object Document Module Attributes">
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description>A number that identifies the Document.</description>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the document content creation started.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the document content creation started.</description>
    </entry>
    <entry group="0040" element="A370" name="Referenced Request Sequence" type="1C">
      <description>Identifies Requested Procedures to which this Document pertains. One or more Items may be included in this sequence.
Required if this Document pertains to at least one Requested Procedure.</description>
    </entry>
    <entry group="0020" element="000D" name="&gt;Study Instance UID" type="1">
      <description>Unique identifier for the Study.</description>
    </entry>
    <entry group="0008" element="1110" name="&gt;Referenced Study Sequence" type="2">
      <description>Uniquely identifies the Study SOP Instance.
Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0008" element="0050" name="&gt;Accession Number" type="2">
      <description>A departmental IS generated number which identifies the order for the Study.</description>
    </entry>
    <entry group="0040" element="2016" name="&gt;Placer Order Number/Imaging Service Request" type="2">
      <description>The order number assigned to the Imaging Service Request by the party placing the order.</description>
    </entry>
    <entry group="0040" element="2017" name="&gt;Filler Order Number/Imaging Service Request" type="2">
      <description>The order number assigned to the Imaging Service Request by the party filling the order.</description>
    </entry>
    <entry group="0040" element="1001" name="&gt;Requested Procedure ID" type="2">
      <description>Identifier of the related Requested Procedure</description>
    </entry>
    <entry group="0032" element="1060" name="&gt;Requested Procedure Description" type="2">
      <description>Institution-generated administrative description or classification of Requested Procedure.</description>
    </entry>
    <entry group="0032" element="1064" name="&gt;Requested Procedure Code Sequence" type="2">
      <description>A sequence that conveys the requested procedure. Zero or one Item may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID Number is specified."/>
    <entry group="0040" element="A375" name="Current Requested Procedure Evidence Sequence" type="1">
      <description>List of all Composite SOP Instances referenced in the Content Sequence (0040,A730) , including all presentation states, real world value maps and other accompanying composite instances that are referenced from the content items. One or more Items shall be included in this sequence.
Note: In the context of the Key Object Selection, the current evidence is considered to be only the set of instances referenced within the Key Object Selection.</description>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0040" element="A525" name="Identical Documents Sequence" type="1C">
      <description>Duplicates of this document, stored with different SOP Instance UIDs. One or more Items may be included in this sequence.
Required if this Key Object Selection document references instances in more than one Study.
See C.17.2.2 and C.17.6.2.1 for further explanation and conditions.</description>
      <section ref="C.17.2.2" name="">If identical copies of an SR Document are to be included in multiple Studies then the entire SR Document shall be duplicated with appropriate changes for inclusion into the different Studies (i.e. Study Instance UID, Series Instance UID, SOP Instance UID, Identical Documents Sequence etc.). The Identical Documents Sequence Attribute in each SOP Instance shall contain references to all other duplicate SOP Instances.
Note: If an SR Document contains an Identical Documents Sequence then it will not be further duplicated without producing a new complete set of duplicate SOP Instances with re-generated Identical Documents Sequences. This is a consequence of the rules for modification of SR Document content in PS3.4. For example, if there are two identical reports and an application is creating a third identical report, then the first two reports must be re-generated in order that their Identical Documents Sequence will reference the new duplicate document and all other identical documents.

If a new SR Document is created using content from an SR Document that contains an Identical Documents Sequence and is part of the same Requested Procedure, then the new SR Document shall only contain a new Identical Documents Sequence if the new SR Document is duplicated. The Predecessor Documents Sequence in all the new SR Documents shall contain references to the original SR Document and all its duplicates as well as any other documents from which content is included.
Note:  It is up to an implementation to decide whether a new SR Document is duplicated across multiple Studies. This may require user input to make the decision.

</section>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
  </module>
  <macro table="C.18.1-1" name="Numeric Measurement Macro Attributes">
    <entry group="0040" element="A300" name="Measured Value Sequence" type="2">
      <description>This is the value of the Content Item.
Shall consist of a Sequence of Items conveying the measured value(s), which represent integers or real numbers and units of measurement. Zero or one Items shall be permitted in this sequence.</description>
    </entry>
    <entry group="0040" element="A30A" name="&gt;Numeric Value" type="1">
      <description>Numeric measurement value. Only a single value shall be present.</description>
    </entry>
    <entry group="0040" element="08EA" name="&gt;Measurement Units Code Sequence" type="1">
      <description>Units of measurement. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 82."/>
    <entry group="0040" element="A301" name="Numeric Value Qualifier Code Sequence" type="3">
      <description>Qualification of Numeric Value in Measured Value Sequence, or reason for absence of Measured Value Sequence Item. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Defined Context ID is 42."/>
  </macro>
  <macro table="C.18.2-1" name="Code Macro Attributes">
    <entry group="0040" element="A168" name="Concept Code Sequence" type="1">
      <description>This is the value of the Content Item. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is specified."/>
  </macro>
  <macro table="C.18.3-1" name="Composite Object Reference Macro Attributes">
    <entry group="0008" element="1199" name="Referenced SOP Sequence" type="1">
      <description>References to Composite Object SOP Class/SOP Instance pairs.
Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </macro>
  <macro table="C.18.4-1" name="Image Reference Macro Attributes">
    <include ref="Include 'Composite Object Reference Macro' Table C.18.3-1"/>
    <entry group="0008" element="1160" name="&gt;Referenced Frame Number" type="1C">
      <description>Identifies the frame numbers within the Referenced SOP Instance to which the reference applies. The first frame shall be denoted as frame number 1.
Note: This Attribute may be multi-valued.
Required if the Referenced SOP Instance is a multi-frame image and the reference does not apply to all frames, and Referenced Segment Number (0062,000B) is not present.</description>
    </entry>
    <entry group="0062" element="000B" name="&gt;Referenced Segment Number" type="1C">
      <description>Identifies the segments to which the reference applies identified by Segment Number (0062,0004). Required if the Referenced SOP Instance is a Segmentation and the reference does not apply to all segments and Referenced Frame Number (0008,1160) is not present.</description>
    </entry>
    <entry group="0008" element="1199" name="&gt;Referenced SOP Sequence" type="3">
      <description>Reference to a Softcopy Presentation State SOP Class/SOP Instance pair. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0008" element="114B" name="&gt;Referenced Real World Value Mapping Instance Sequence" type="3">
      <description>Reference to a Real World Value Mapping SOP Class/SOP Instance pair. Only a single Item shall be permitted in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0088" element="0200" name="&gt;Icon Image Sequence" type="3">
      <description>This Icon Image is representative of the Image. Only a single Item shall be permitted in this Sequence.
The Icon Image may be no greater than 128 rows by 128 columns.</description>
    </entry>
    <include ref="&gt;&gt; Include 'Image Pixel Macro' Table C.7-11b" description="See Section F.7."/>
  </macro>
  <macro table="C.18.5-1" name="Waveform Reference Macro Attributes">
    <include ref="Include 'Composite Object Reference Macro' Table C.18.3-1"/>
    <entry group="0040" element="A0B0" name="&gt;Referenced Waveform Channels" type="1C">
      <description>List of channels in Waveform to which the reference applies. See C.18.5.1.1
Required if the Referenced SOP Instance is a Waveform that contains multiple Channels and not all Channels in the Waveform are referenced.</description>
      <section ref="C.18.5.1.1" name="">Referenced Waveform Channels (0040,A0B0) is a multi-value attribute which lists the channels referenced. Each channel is specified as a pair of values (M,C), where the first value is the sequence item number of the Waveform Sequence (5400,0100) attribute in the referenced object (i.e. the Multiplex Group Number), and the second value is the sequence item number of the Channel Definition Sequence (003A,0200) attribute (i.e., the Channel Number) within the multiplex group.
If the specified channel number is 0, the annotation applies to all channels in the multiplex group.
Note:  As an example, an annotation which applies to the entire first multiplex group and channels 2 and 3 of the third multiplex group would have Referenced Waveform Channels (0040,A0B0) value 0001 0000 0003 0002 0003 0003.

</section>
    </entry>
  </macro>
  <macro table="C.18.6-1" name="Spatial Coordinates Macro Attributes">
    <entry group="0070" element="0022" name="Graphic Data" type="1">
      <description>An ordered set of (column,row) pairs that denote positions in an image specified with sub-pixel resolution such that the origin at the TLHC of the TLHC pixel is 0.0\0.0, the BRHC of the TLHC pixel is 1.0\1.0, and the BRHC of the BRHC pixel is Columns\Rows. The values must be within the range 0\0 to Columns\Rows. The values Columns (0028,0011) and Rows (0028,0010) are those contained in the referenced image.
See C.18.6.1.1 for further explanation.</description>
      <section ref="C.18.6.1.1" name="">Graphic Data may be used to associate an anatomic or spatial Concept with a defined subset of one or more images. Graphic Data may be explicitly defined as a single point (i.e. to denote the epicenter of an anatomic site or lesion) or more than one point (i.e. representing a set of points or an open or closed polygon).
Note:  Spatial coordinates may be used to associate observational data with a set of Image features. Spatial coordinates also may be used to convey coordinates that are input data for a measurement.

</section>
    </entry>
    <entry group="0070" element="0023" name="Graphic Type" type="1">
      <description>See C.18.6.1.2 for Enumerated Values.</description>
      <section ref="C.18.6.1.2" name="">When annotation applies to an image, this attribute defines the type of geometry of the annotated region of interest. The following Enumerated Values are specified for image spatial coordinate geometries:
POINT = a single pixel denoted by a single (column,row) pair
MULTIPOINT = multiple pixels each denoted by an (column,row) pair
POLYLINE = a series of connected line segments with ordered vertices denoted by (column,row) pairs; if the first and last vertices are the same it is a closed polygon
CIRCLE = a circle defined by two (column,row) pairs. The first point is the central pixel. The second point is a pixel on the perimeter of the circle.
ELLIPSE = an ellipse defined by four pixel (column,row) pairs, the first two points specifying the endpoints of the major axis and the second two points specifying the endpoints of the minor axis of an ellipse

</section>
    </entry>
  </macro>
  <macro table="C.18.7-1" name="Temporal Coordinates Macro Attributes">
    <entry group="0040" element="A130" name="Temporal Range Type" type="1">
      <description>See C.18.7.1.1 for Enumerated Values.</description>
      <section ref="C.18.7.1.1" name="">This Attribute defines the type of temporal extent of the region of interest. A temporal point (or instant of time) may be defined by a waveform sample offset (for a single waveform multiplex group only), time offset, or absolute time.
The following Enumerated Values are specified for Temporal Range Type:
POINT = a single temporal point
MULTIPOINT = multiple temporal points
SEGMENT = a range between two temporal points
MULTISEGMENT = multiple segments, each denoted by two temporal points
BEGIN = a range beginning at one temporal point, and extending beyond the end of the acquired data
END = a range beginning before the start of the acquired data, and extending to (and including) the identified temporal point

</section>
    </entry>
    <entry group="0040" element="A132" name="Referenced Sample Positions" type="1C">
      <description>List of samples within a multiplex group specifying temporal points of the referenced data. Position of first sample is 1.
Required if the Referenced SOP Instance is a Waveform and Referenced Time Offsets (0040,A138) and Referenced DateTime (0040,A13A) are not present.
May be used only if Referenced Channels (0040,A0B0) refers to channels within a single multiplex group.</description>
    </entry>
    <entry group="0040" element="A138" name="Referenced Time Offsets" type="1C">
      <description>Specifies temporal points for reference by number of seconds after start of data.
Required if Referenced Sample Positions (0040,A132) and Referenced DateTime (0040,A13A) are not present.</description>
    </entry>
    <entry group="0040" element="A13A" name="Referenced DateTime" type="1C">
      <description>Specifies temporal points for reference by absolute time.
Required if Referenced Sample Positions (0040,A132) and Referenced Time Offsets (0040,A138) are not present.</description>
    </entry>
  </macro>
  <macro table="C.18.8-1" name="Container Macro Attributes">
    <entry group="0040" element="A050" name="Continuity of Content" type="1">
      <description>This flag specifies for a CONTAINER whether or not its contained Content Items are logically linked in a continuous textual flow, or are separate items.
Enumerated Values:
SEPARATE
CONTINUOUS
See C.18.8.1.1 for further explanation.</description>
      <section ref="C.18.8.1.1" name="">Continuity of Content (0040,A050) specifies whether or not all the Content Items contained in a CONTAINER are logically linked in a continuous textual flow, or are separate entities. It only applies to the children contained in the container, and not their children (which if containers themselves, will have the attribute specified explicitly).
Notes:   1. This allows the interspersing of measurements, codes, and image references, amongst text. For example, the following: “A mass of diameter = 3 cm was detected.” can be represented by the following Content Items in a CONTAINER with a Continuity of Content (0040,A050) of CONTINUOUS:
  TEXT  “A mass of”
  NUM  “Diameter” 3 “cm”
  TEXT  “was detected.”
  2. The Continuity of Content applies only to subsidiary Content Items with Relationship Type CONTAINS. Other subsidiary items, e.g., with Relationship Type HAS CONCEPT MOD or HAS OBS CONTEXT, are not part of the Continuity of Content, but apply to the Container as a whole.

</section>
    </entry>
    <entry group="0040" element="A504" name="Content Template Sequence" type="1C">
      <description>Template that describes the content of this Content Item and its subsidiary Content Items.
Only a single Item shall be permitted in this sequence.
Required if a template was used to define the content of this Item, and the template consists of a single CONTAINER with nested content, and it is the outermost invocation of a set of nested templates that start with the same CONTAINER (see C.18.8.1.2).</description>
    </entry>
    <entry group="0008" element="0105" name="&gt;Mapping Resource" type="1">
      <description>Mapping Resource that defines the template. See Section 8.4. Defined Terms:
DCMR = DICOM Content Mapping Resource</description>
    </entry>
    <entry group="0040" element="DB00" name="&gt;Template Identifier" type="1">
      <description>Template identifier.</description>
    </entry>
  </macro>
  <module ref="C.19.1" table="C.19-1" name="Raw Data Module Attributes">
    <entry group="0020" element="0013" name="Instance Number" type="2">
      <description>A number that identifies this image. The value shall be unique within a series.</description>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the raw data creation was started.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the raw data creation was started.</description>
    </entry>
    <entry group="0008" element="002A" name="Acquisition DateTime" type="3">
      <description>The date and time that the acquisition of data started.
Note: The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800).</description>
    </entry>
    <entry group="0008" element="9123" name="Creator-Version UID" type="1">
      <description>Unique identification of the equipment and version of the software that has created the Raw Data information. The UID allows one to avoid attempting to interpret raw data with an unknown format.</description>
    </entry>
    <entry group="0008" element="114A" name="Referenced Instance Sequence" type="3">
      <description>A sequence that provides reference to a set of SOP Class/Instance pairs identifying other Instances significantly related to this Instance. One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0040" element="A170" name="&gt;Purpose of Reference Code Sequence" type="1">
      <description>Describes the purpose for which the reference is made. Only a single Item shall be permitted in this sequence.
See C.7.6.16.2.5.1.</description>
      <section ref="C.7.6.16.2.5.1" name="">Referenced Image Sequence (0008,1140) shall be used to provide a reference to a set of SOP Class/Instance pairs identifying other data objects used to plan the acquisition of this image where the images shall share the same Frame of Reference UID (0020,0052). For each Item that contains such a reference, the value of the Purpose of Reference Code Sequence (0040,A170) shall be (”121311”, DCM, ”Localizer"). Applications can use the Referenced Image Sequence (0008,1140) in combination with data in Plane Position and Plane Orientation Macros to provide projections of the position of an image with respect to the referenced image.
The Referenced Image Sequence (0008,1140) may also be present when references to other images (or frames within other images) are required for other reasons, as specified by Purpose of Reference Code Sequence (0040,A170).
Note:  An Image may contain references to itself (e.g. to other frames within itself).

</section>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No Baseline Context ID is defined."/>
    <include ref="Include any private attributes that contain Raw Data information. See section C.19.1.1 for further explanation."/>
  </module>
  <module ref="C.20.1" table="C.20.1-1" name="Spatial Registration Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Modality type.
Enumerated Value:
REG</description>
    </entry>
  </module>
  <module ref="C.20.2" table="C.20.2-1" name="Spatial Registration Module Attributes">
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the content creation started.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the content creation started.</description>
    </entry>
    <include ref="Include Content Identification Macro Table 10-12"/>
    <entry group="0070" element="0308" name="Registration Sequence" type="1">
      <description>A sequence of one or more registration items. Each item defines a spatial registration to the referenced images in that item. All referenced images are in the same spatial frame of reference or atlas.</description>
    </entry>
    <entry group="0020" element="0052" name="&gt;Frame of Reference UID" type="1C">
      <description>Identifies a Frame of Reference that may or may not be an image set (e.g. atlas or physical space). See C.7.4.1.1.1 for further explanation. Required if Referenced Image Sequence (0008,1140) is absent. May be present otherwise.</description>
      <section ref="C.7.4.1.1.1" name="">The Frame of Reference UID (0020,0052) shall be used to uniquely identify a frame of reference for a series. Each series shall have a single Frame of Reference UID. However, multiple Series within a Study may share a Frame of Reference UID. All images in a Series that share the same Frame of Reference UID shall be spatially related to each other.
Notes:  1. Previous versions of this Standard defined a Data Element "Location", which has been retired. Frame of Reference UID provides a completely unambiguous identification of the image location reference used to indicate position.
  2. A common Frame of Reference UID may be used to spatially relate localizer images with a set of transverse images. However, in some cases (eg. multiple localizer images being related to a single set of transverse images) a common Frame of Reference UID may not be sufficient. The Referenced Image Sequence (0008,1140) provides an unambiguous method for relating localizer images.

</section>
    </entry>
    <entry group="0008" element="1140" name="&gt;Referenced Image Sequence" type="1C">
      <description>Identifies the set of images registered in this sequence item. One or more items shall be present. Required if Frame of Reference UID (0020,0052) is absent. May be present otherwise.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0070" element="0309" name="&gt;Matrix Registration Sequence" type="1">
      <description>A sequence that specifies one spatial registration. Exactly one item shall be present</description>
    </entry>
    <entry group="3006" element="00C8" name="&gt;&gt;Frame of Reference Transformation Comment" type="3">
      <description>User description or comments about the registration.</description>
    </entry>
    <entry group="0070" element="030D" name="&gt;&gt;Registration Type Code Sequence" type="2">
      <description>Describes the information input into the registration process. Zero or one Items may be present in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 7100"/>
    <entry group="0070" element="030A" name="&gt;&gt;Matrix Sequence" type="1">
      <description>One or more items shall be present. Each item specifies a transformation. The item order is significant and corresponds to matrix multiplication order. See C.20.2.1.1.</description>
      <section ref="C.20.2.1.1" name="">The Frame of Reference Transformation Matrix (3006,00C6) AMB describes how to transform a point (Bx,By,Bz) with respect to RCSB into (Ax,Ay,Az) with respect to RCSA according to the equation below.



















                   A



                x













                   A



                y













                   A



                z






               1




           =






                 M


                   11









                 M


                   12









                 M


                   13









                 T


                   x











                 M


                   21









                 M


                   22









                 M


                   23









                 T


                   y











                 M


                   31









                 M


                   32









                 M


                   33









                 T


                   z










                0





                0





                0





                1


















                  B



               x













                  B



               y













                  B



               z






              1









       size 12{ left [ matrix {
"" lSup { size 8{A} } x {} ##
"" lSup { size 8{A} } y {} ##
"" lSup { size 8{A} } z {} ##
1
}  right ]= left [ matrix {
M rSub { size 8{"11"} }  {} # M rSub { size 8{"12"} }  {} # M rSub { size 8{"13"} }  {} # T rSub { size 8{x} }  {} ##
M rSub { size 8{"21"} }  {} # M rSub { size 8{"22"} }  {} # M rSub { size 8{"23"} }  {} # T rSub { size 8{y} }  {} ##
M rSub { size 8{"31"} }  {} # M rSub { size 8{"32"} }  {} # M rSub { size 8{"33"} }  {} # T rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
"" lSup { size 8{B} } x {} ##
"" lSup { size 8{B} } y {} ##
"" lSup { size 8{B} } z {} ##
1
}  right ]} {}


The Frame of Reference Transformation Matrix is expressible as multiple matrices, each in a separate item of the Matrix Sequence (0070,030A). The equation below specifies the order of the matrix multiplication where M1, M2 and M3 are the first, second and third items in the sequence.














                 x
                 '





                 y
                 '





                 z
                 '





                 1








              T



           =

            M


              3







             M


               2






               M


                 1









                    x





                    y





                    z





                    1








                 T












       size 12{ left [ matrix {
x' {} # y' {} # z' {} # 1{}
}  right ] rSup { size 8{T} } =M rSub { size 8{3} }  left (M rSub { size 8{2} }  left (M rSub { size 8{1} }  left [ matrix {
x {} # y {} # z {} # 1{}
}  right ] rSup { size 8{T} }  right ) right )} {}


where  =
Registration often involves two or more RCS, each with a corresponding Frame of Reference Transformation Matrix. For example, another Frame of Reference Transformation Matrix AMC can describe how to transform a point (Cx,Cy,Cz) with respect to RCSC into (Ax,Ay,Az) with respect to RCSA. It is straightforward to find the Frame of Reference Transformation Matrix BMC that describes how to transform the point (Cx,Cy,Cz) with respect to RCSC into the point (Bx,By,Bz) with respect to RCSB. The solution is to invert AMB and multiply by AMC, as shown below:



















                   B



                x













                   B



                y













                   B



                z






               1




           =
           







             A




           Μ


             B





            



               −
               1




           ∗






              A





           M


             C














                  C



               x













                  C



               y













                  C



               z






              1









       size 12{ left [ matrix {
"" lSup { size 8{B} } x {} ##
"" lSup { size 8{B} } y {} ##
"" lSup { size 8{B} } z {} ##
1
}  right ]= \( "" lSup { size 8{A} } Μ rSub { size 8{B} }  \)  rSup { size 8{ - 1} }  * "" lSup { size 8{A} } M rSub { size 8{C} }  left [ matrix {
"" lSup { size 8{C} } x {} ##
"" lSup { size 8{C} } y {} ##
"" lSup { size 8{C} } z {} ##
1
}  right ]} {}



</section>
    </entry>
    <entry group="3006" element="00C6" name="&gt;&gt;&gt;Frame of Reference Transformation Matrix" type="1">
      <description>A 4x4 homogeneous transformation matrix that registers the referenced images to the local RCS. Matrix elements shall be listed in row-major order. See C.20.2.1.1.</description>
      <section ref="C.20.2.1.1" name="">The Frame of Reference Transformation Matrix (3006,00C6) AMB describes how to transform a point (Bx,By,Bz) with respect to RCSB into (Ax,Ay,Az) with respect to RCSA according to the equation below.



















                   A



                x













                   A



                y













                   A



                z






               1




           =






                 M


                   11









                 M


                   12









                 M


                   13









                 T


                   x











                 M


                   21









                 M


                   22









                 M


                   23









                 T


                   y











                 M


                   31









                 M


                   32









                 M


                   33









                 T


                   z










                0





                0





                0





                1


















                  B



               x













                  B



               y













                  B



               z






              1









       size 12{ left [ matrix {
"" lSup { size 8{A} } x {} ##
"" lSup { size 8{A} } y {} ##
"" lSup { size 8{A} } z {} ##
1
}  right ]= left [ matrix {
M rSub { size 8{"11"} }  {} # M rSub { size 8{"12"} }  {} # M rSub { size 8{"13"} }  {} # T rSub { size 8{x} }  {} ##
M rSub { size 8{"21"} }  {} # M rSub { size 8{"22"} }  {} # M rSub { size 8{"23"} }  {} # T rSub { size 8{y} }  {} ##
M rSub { size 8{"31"} }  {} # M rSub { size 8{"32"} }  {} # M rSub { size 8{"33"} }  {} # T rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
"" lSup { size 8{B} } x {} ##
"" lSup { size 8{B} } y {} ##
"" lSup { size 8{B} } z {} ##
1
}  right ]} {}


The Frame of Reference Transformation Matrix is expressible as multiple matrices, each in a separate item of the Matrix Sequence (0070,030A). The equation below specifies the order of the matrix multiplication where M1, M2 and M3 are the first, second and third items in the sequence.














                 x
                 '





                 y
                 '





                 z
                 '





                 1








              T



           =

            M


              3







             M


               2






               M


                 1









                    x





                    y





                    z





                    1








                 T












       size 12{ left [ matrix {
x' {} # y' {} # z' {} # 1{}
}  right ] rSup { size 8{T} } =M rSub { size 8{3} }  left (M rSub { size 8{2} }  left (M rSub { size 8{1} }  left [ matrix {
x {} # y {} # z {} # 1{}
}  right ] rSup { size 8{T} }  right ) right )} {}


where  =
Registration often involves two or more RCS, each with a corresponding Frame of Reference Transformation Matrix. For example, another Frame of Reference Transformation Matrix AMC can describe how to transform a point (Cx,Cy,Cz) with respect to RCSC into (Ax,Ay,Az) with respect to RCSA. It is straightforward to find the Frame of Reference Transformation Matrix BMC that describes how to transform the point (Cx,Cy,Cz) with respect to RCSC into the point (Bx,By,Bz) with respect to RCSB. The solution is to invert AMB and multiply by AMC, as shown below:



















                   B



                x













                   B



                y













                   B



                z






               1




           =
           







             A




           Μ


             B





            



               −
               1




           ∗






              A





           M


             C














                  C



               x













                  C



               y













                  C



               z






              1









       size 12{ left [ matrix {
"" lSup { size 8{B} } x {} ##
"" lSup { size 8{B} } y {} ##
"" lSup { size 8{B} } z {} ##
1
}  right ]= \( "" lSup { size 8{A} } Μ rSub { size 8{B} }  \)  rSup { size 8{ - 1} }  * "" lSup { size 8{A} } M rSub { size 8{C} }  left [ matrix {
"" lSup { size 8{C} } x {} ##
"" lSup { size 8{C} } y {} ##
"" lSup { size 8{C} } z {} ##
1
}  right ]} {}



</section>
    </entry>
    <entry group="0070" element="030C" name="&gt;&gt;&gt;Frame of Reference Transformation Matrix Type" type="1">
      <description>Type of Frame of Reference Transformation Matrix (3006,00C6). Defined terms:
RIGID
RIGID_SCALE
AFFINE
See C.20.2.1.2</description>
      <section ref="C.20.2.1.2" name="">There are three types of Registration Matrices:
RIGID: This is a registration involving only translations and rotations. Mathematically, the matrix is constrained to be orthonormal and describes six degrees of freedom: three translations, and three rotations.
RIGID_SCALE: This is a registration involving only translations, rotations and scaling. Mathematically, the matrix is constrained to be orthogonal and describes nine degrees of freedom: three translations, three rotations and three scales. This type of transformation is sometimes used in atlas mapping.
AFFINE: This is a registration involving translations, rotations, scaling and shearing. Mathematically, there are no constraints on the elements of the Frame of Reference Transformation Matrix, so it conveys twelve degrees of freedom. This type of transformation is sometimes used in atlas mapping.
See the PS 3.17 Annex on Transforms and Mappings for more detail.
</section>
    </entry>
    <entry group="0070" element="0314" name="&gt;Used Fiducials Sequence" type="3">
      <description>The fiducials used to determine the Frame of Reference Transformation Matrix. One or more Items may be present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11" description="Reference to the Spatial Fiducial SOP Instance identifying the Used Fiducial(s)"/>
    <entry group="0070" element="031A" name="&gt;&gt;Fiducial UID" type="1">
      <description>The UID that identifies the fiducial used as registration input.</description>
    </entry>
  </module>
  <module ref="C.20.3" table="C.20.3-1" name="Deformable Spatial Registration Module Attributes">
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the vector grid data creation started.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the vector grid data creation started.</description>
    </entry>
    <include ref="Include Content Identification Macro Table 10-12"/>
    <entry group="0064" element="0002" name="Deformable Registration Sequence" type="1">
      <description>A sequence of one or more registration items. Each item defines a spatial registration to the referenced images in that item. At least one item shall have a Deformable Registration Grid Sequence (0064,0005) with one item. See C.20.3.1.1.</description>
      <section ref="C.20.3.1.1" name="">The registrations in this module are applied to the Registered RCS coordinates in the following order. First, transform the coordinates using the matrix described in the Pre Deformation Matrix Registration Sequence (0064,000F). Next apply the deformation offsets to the resulting coordinates. Finally, transform those coordinates using the matrix described in the Post Deformation Matrix Registration Sequence (0064,0010). The resulting coordinate addresses the sample point within the Source RCS.
Thus a source coordinate may be calculated using the following equation:
(This assumes that the center position of each deformation voxel will be transformed)














                 X




                     Source













                 Y




                     Source













                 Z




                     Source











               1




           =

            M




                Post









             M



                Pr
                e












                    X




                        Start





                   

                    i
                    ∗

                     X


                       R














                    Y




                        Start





                   

                    j
                    ∗

                     Y


                       R














                    Z




                        Start





                   

                    k
                    ∗

                     Z


                       R











                 1




             






                   ΔX




                       ijk













                   ΔY




                       ijk













                   ΔZ




                       ijk











                 0












       size 12{ left [ matrix {
X rSub { size 8{ ital "Source"} }  {} ##
Y rSub { size 8{ ital "Source"} }  {} ##
Z rSub { size 8{ ital "Source"} }  {} ##
1
}  right ]=M rSub { size 8{ ital "Post"} }  left (M rSub { size 8{"Pr"e} }  left [ matrix {
X rSub { size 8{ ital "Start"} } +i*X rSub { size 8{R} }  {} ##
Y rSub { size 8{ ital "Start"} } +j*Y rSub { size 8{R} }  {} ##
Z rSub { size 8{ ital "Start"} } +k*Z rSub { size 8{R} }  {} ##
1
}  right ]+ left [ matrix {
ΔX rSub { size 8{ ital "ijk"} }  {} ##
ΔY rSub { size 8{ ital "ijk"} }  {} ##
ΔZ rSub { size 8{ ital "ijk"} }  {} ##
0
}  right ] right )} {}


Where:
  The spatial coordinate in the Source RCS.
  The start coordinate, in the Registered RCS, of the deformation grid as specified in the Image Position (Patient) attribute (0020,0032).
  The index into the deformation grid in the X, Y, and Z dimension.
  The resolution of the deformation grid in the X, Y, and Z dimension as specified in the Grid Resolution attribute (0064,0008).
  The deformation specified at index (i,j,k) in the deformation grid. If the Deformation Registration Grid Sequence (0064,0005) has no items, the  values are zero.
MPre    The transformation matrix specified in the Pre Deformation Matrix Registration Sequence (0064,000F).
MPost    The transformation matrix specified in the Post Deformation Matrix Registration Sequence (0064,0010).
</section>
    </entry>
    <entry group="0064" element="0003" name="&gt;Source Frame of Reference UID" type="1">
      <description>Identifies the Frame of Reference of a Source RCS. The Source RCS may or may not include an image set (e.g. atlas). See C.7.4.1.1.1 for further explanation.</description>
      <section ref="C.7.4.1.1.1" name="">The Frame of Reference UID (0020,0052) shall be used to uniquely identify a frame of reference for a series. Each series shall have a single Frame of Reference UID. However, multiple Series within a Study may share a Frame of Reference UID. All images in a Series that share the same Frame of Reference UID shall be spatially related to each other.
Notes:  1. Previous versions of this Standard defined a Data Element "Location", which has been retired. Frame of Reference UID provides a completely unambiguous identification of the image location reference used to indicate position.
  2. A common Frame of Reference UID may be used to spatially relate localizer images with a set of transverse images. However, in some cases (eg. multiple localizer images being related to a single set of transverse images) a common Frame of Reference UID may not be sufficient. The Referenced Image Sequence (0008,1140) provides an unambiguous method for relating localizer images.

</section>
    </entry>
    <entry group="0008" element="1140" name="&gt;Referenced Image Sequence" type="1C">
      <description>Identifies the set of images registered in this sequence item. One or more items shall be present. Required if the registration applies to a subset of images within the specified Source Frame of Reference UID (0064,0003). All referenced images shall be in the same spatial frame of reference.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="3006" element="00C8" name="&gt;Frame of Reference Transformation Comment" type="3">
      <description>User description or comments about the registration.</description>
    </entry>
    <entry group="0070" element="030D" name="&gt;Registration Type Code Sequence" type="2">
      <description>Describes the method used for the registration process. Zero or one item shall be present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context ID is 7100"/>
    <entry group="0064" element="000F" name="&gt;Pre Deformation Matrix Registration Sequence" type="1C">
      <description>A sequence that specifies one spatial registration to be applied prior to the deformation. Exactly one item shall be present. Required if a matrix transformation is to be applied prior to deformation.</description>
    </entry>
    <entry group="3006" element="00C6" name="&gt;&gt;Frame of Reference Transformation Matrix" type="1">
      <description>A 4x4 homogeneous transformation matrix. Matrix elements shall be listed in row-major order. See C.20.2.1.1.</description>
      <section ref="C.20.2.1.1" name="">The Frame of Reference Transformation Matrix (3006,00C6) AMB describes how to transform a point (Bx,By,Bz) with respect to RCSB into (Ax,Ay,Az) with respect to RCSA according to the equation below.



















                   A



                x













                   A



                y













                   A



                z






               1




           =






                 M


                   11









                 M


                   12









                 M


                   13









                 T


                   x











                 M


                   21









                 M


                   22









                 M


                   23









                 T


                   y











                 M


                   31









                 M


                   32









                 M


                   33









                 T


                   z










                0





                0





                0





                1


















                  B



               x













                  B



               y













                  B



               z






              1









       size 12{ left [ matrix {
"" lSup { size 8{A} } x {} ##
"" lSup { size 8{A} } y {} ##
"" lSup { size 8{A} } z {} ##
1
}  right ]= left [ matrix {
M rSub { size 8{"11"} }  {} # M rSub { size 8{"12"} }  {} # M rSub { size 8{"13"} }  {} # T rSub { size 8{x} }  {} ##
M rSub { size 8{"21"} }  {} # M rSub { size 8{"22"} }  {} # M rSub { size 8{"23"} }  {} # T rSub { size 8{y} }  {} ##
M rSub { size 8{"31"} }  {} # M rSub { size 8{"32"} }  {} # M rSub { size 8{"33"} }  {} # T rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
"" lSup { size 8{B} } x {} ##
"" lSup { size 8{B} } y {} ##
"" lSup { size 8{B} } z {} ##
1
}  right ]} {}


The Frame of Reference Transformation Matrix is expressible as multiple matrices, each in a separate item of the Matrix Sequence (0070,030A). The equation below specifies the order of the matrix multiplication where M1, M2 and M3 are the first, second and third items in the sequence.














                 x
                 '





                 y
                 '





                 z
                 '





                 1








              T



           =

            M


              3







             M


               2






               M


                 1









                    x





                    y





                    z





                    1








                 T












       size 12{ left [ matrix {
x' {} # y' {} # z' {} # 1{}
}  right ] rSup { size 8{T} } =M rSub { size 8{3} }  left (M rSub { size 8{2} }  left (M rSub { size 8{1} }  left [ matrix {
x {} # y {} # z {} # 1{}
}  right ] rSup { size 8{T} }  right ) right )} {}


where  =
Registration often involves two or more RCS, each with a corresponding Frame of Reference Transformation Matrix. For example, another Frame of Reference Transformation Matrix AMC can describe how to transform a point (Cx,Cy,Cz) with respect to RCSC into (Ax,Ay,Az) with respect to RCSA. It is straightforward to find the Frame of Reference Transformation Matrix BMC that describes how to transform the point (Cx,Cy,Cz) with respect to RCSC into the point (Bx,By,Bz) with respect to RCSB. The solution is to invert AMB and multiply by AMC, as shown below:



















                   B



                x













                   B



                y













                   B



                z






               1




           =
           







             A




           Μ


             B





            



               −
               1




           ∗






              A





           M


             C














                  C



               x













                  C



               y













                  C



               z






              1









       size 12{ left [ matrix {
"" lSup { size 8{B} } x {} ##
"" lSup { size 8{B} } y {} ##
"" lSup { size 8{B} } z {} ##
1
}  right ]= \( "" lSup { size 8{A} } Μ rSub { size 8{B} }  \)  rSup { size 8{ - 1} }  * "" lSup { size 8{A} } M rSub { size 8{C} }  left [ matrix {
"" lSup { size 8{C} } x {} ##
"" lSup { size 8{C} } y {} ##
"" lSup { size 8{C} } z {} ##
1
}  right ]} {}



</section>
    </entry>
    <entry group="0070" element="030C" name="&gt;&gt;Frame of Reference Transformation Matrix Type" type="1">
      <description>Type of Frame of Reference Transformation Matrix (3006,00C6). Defined terms:
RIGID
RIGID_SCALE
AFFINE
See C.20.2.1.2</description>
      <section ref="C.20.2.1.2" name="">There are three types of Registration Matrices:
RIGID: This is a registration involving only translations and rotations. Mathematically, the matrix is constrained to be orthonormal and describes six degrees of freedom: three translations, and three rotations.
RIGID_SCALE: This is a registration involving only translations, rotations and scaling. Mathematically, the matrix is constrained to be orthogonal and describes nine degrees of freedom: three translations, three rotations and three scales. This type of transformation is sometimes used in atlas mapping.
AFFINE: This is a registration involving translations, rotations, scaling and shearing. Mathematically, there are no constraints on the elements of the Frame of Reference Transformation Matrix, so it conveys twelve degrees of freedom. This type of transformation is sometimes used in atlas mapping.
See the PS 3.17 Annex on Transforms and Mappings for more detail.
</section>
    </entry>
    <entry group="0064" element="0010" name="&gt;Post Deformation Matrix Registration Sequence" type="1C">
      <description>A sequence that specifies one spatial registration to be applied after the application of the deformation. Exactly one item shall be present. Required if matrix transformation is to be performed after application of the deformation.</description>
    </entry>
    <entry group="3006" element="00C6" name="&gt;&gt;Frame of Reference Transformation Matrix" type="1">
      <description>A 4x4 homogeneous transformation matrix. Matrix elements shall be listed in row-major order. See C.20.2.1.1.</description>
      <section ref="C.20.2.1.1" name="">The Frame of Reference Transformation Matrix (3006,00C6) AMB describes how to transform a point (Bx,By,Bz) with respect to RCSB into (Ax,Ay,Az) with respect to RCSA according to the equation below.



















                   A



                x













                   A



                y













                   A



                z






               1




           =






                 M


                   11









                 M


                   12









                 M


                   13









                 T


                   x











                 M


                   21









                 M


                   22









                 M


                   23









                 T


                   y











                 M


                   31









                 M


                   32









                 M


                   33









                 T


                   z










                0





                0





                0





                1


















                  B



               x













                  B



               y













                  B



               z






              1









       size 12{ left [ matrix {
"" lSup { size 8{A} } x {} ##
"" lSup { size 8{A} } y {} ##
"" lSup { size 8{A} } z {} ##
1
}  right ]= left [ matrix {
M rSub { size 8{"11"} }  {} # M rSub { size 8{"12"} }  {} # M rSub { size 8{"13"} }  {} # T rSub { size 8{x} }  {} ##
M rSub { size 8{"21"} }  {} # M rSub { size 8{"22"} }  {} # M rSub { size 8{"23"} }  {} # T rSub { size 8{y} }  {} ##
M rSub { size 8{"31"} }  {} # M rSub { size 8{"32"} }  {} # M rSub { size 8{"33"} }  {} # T rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
"" lSup { size 8{B} } x {} ##
"" lSup { size 8{B} } y {} ##
"" lSup { size 8{B} } z {} ##
1
}  right ]} {}


The Frame of Reference Transformation Matrix is expressible as multiple matrices, each in a separate item of the Matrix Sequence (0070,030A). The equation below specifies the order of the matrix multiplication where M1, M2 and M3 are the first, second and third items in the sequence.














                 x
                 '





                 y
                 '





                 z
                 '





                 1








              T



           =

            M


              3







             M


               2






               M


                 1









                    x





                    y





                    z





                    1








                 T












       size 12{ left [ matrix {
x' {} # y' {} # z' {} # 1{}
}  right ] rSup { size 8{T} } =M rSub { size 8{3} }  left (M rSub { size 8{2} }  left (M rSub { size 8{1} }  left [ matrix {
x {} # y {} # z {} # 1{}
}  right ] rSup { size 8{T} }  right ) right )} {}


where  =
Registration often involves two or more RCS, each with a corresponding Frame of Reference Transformation Matrix. For example, another Frame of Reference Transformation Matrix AMC can describe how to transform a point (Cx,Cy,Cz) with respect to RCSC into (Ax,Ay,Az) with respect to RCSA. It is straightforward to find the Frame of Reference Transformation Matrix BMC that describes how to transform the point (Cx,Cy,Cz) with respect to RCSC into the point (Bx,By,Bz) with respect to RCSB. The solution is to invert AMB and multiply by AMC, as shown below:



















                   B



                x













                   B



                y













                   B



                z






               1




           =
           







             A




           Μ


             B





            



               −
               1




           ∗






              A





           M


             C














                  C



               x













                  C



               y













                  C



               z






              1









       size 12{ left [ matrix {
"" lSup { size 8{B} } x {} ##
"" lSup { size 8{B} } y {} ##
"" lSup { size 8{B} } z {} ##
1
}  right ]= \( "" lSup { size 8{A} } Μ rSub { size 8{B} }  \)  rSup { size 8{ - 1} }  * "" lSup { size 8{A} } M rSub { size 8{C} }  left [ matrix {
"" lSup { size 8{C} } x {} ##
"" lSup { size 8{C} } y {} ##
"" lSup { size 8{C} } z {} ##
1
}  right ]} {}



</section>
    </entry>
    <entry group="0070" element="030C" name="&gt;&gt;Frame of Reference Transformation Matrix Type" type="1">
      <description>Type of Frame of Reference Transformation Matrix (3006,00C6). Defined terms:
RIGID
RIGID_SCALE
AFFINE
See C.20.2.1.2</description>
      <section ref="C.20.2.1.2" name="">There are three types of Registration Matrices:
RIGID: This is a registration involving only translations and rotations. Mathematically, the matrix is constrained to be orthonormal and describes six degrees of freedom: three translations, and three rotations.
RIGID_SCALE: This is a registration involving only translations, rotations and scaling. Mathematically, the matrix is constrained to be orthogonal and describes nine degrees of freedom: three translations, three rotations and three scales. This type of transformation is sometimes used in atlas mapping.
AFFINE: This is a registration involving translations, rotations, scaling and shearing. Mathematically, there are no constraints on the elements of the Frame of Reference Transformation Matrix, so it conveys twelve degrees of freedom. This type of transformation is sometimes used in atlas mapping.
See the PS 3.17 Annex on Transforms and Mappings for more detail.
</section>
    </entry>
    <entry group="0064" element="0005" name="&gt;Deformable Registration Grid Sequence" type="1C">
      <description>Describes the deformation grid used to sample into the Source RCS. Exactly one item shall be present. Required if deformation is performed. See C.20.3.1.2.</description>
      <section ref="C.20.3.1.2" name="">The vector represents the deformation at the center of the voxel. Deformations between voxel centers shall be determined through interpolation of the surrounding vectors in an implementation dependent manner.
</section>
    </entry>
    <entry group="0020" element="0037" name="&gt;&gt;Image Orientation (Patient)" type="1">
      <description>The direction of cosines of the first row and first column of the Vector Grid Data (0064,0009) with respect to the patient. See C.7.6.2.1.1 for further explanation.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
    <entry group="0020" element="0032" name="&gt;&gt;Image Position (Patient)" type="1">
      <description>The x, y, and z coordinates of the upper left hand voxel (center of the first voxel transmitted) of the grid, in mm in the Registered Frame of Reference. See C.7.6.2.1.1 for further explanation.</description>
      <section ref="C.7.6.2.1.1" name="">The Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively.
The direction of the axes is defined fully by the patient’s orientation. The x-axis is increasing to the left hand side of the patient. The y-axis is increasing to the posterior side of the patient. The z-axis is increasing toward the head of the patient.
The patient based coordinate system is a right handed system, i.e. the vector cross product of a unit vector along the positive x-axis and a unit vector along the positive y-axis is equal to a unit vector along the positive z-axis.
Note  If a patient lies parallel to the ground, face-up on the table, with his feet-to-head direction same as the front-to-back direction of the imaging equipment, the direction of the axes of this patient based coordinate system and the equipment based coordinate system in previous versions of this Standard will coincide.

The Image Plane Attributes, in conjunction with the Pixel Spacing Attribute, describe the position and orientation of the image slices relative to the patient-based coordinate system. In each image frame the Image Position (Patient) (0020,0032) specifies the origin of the image with respect to the patient-based coordinate system. RCS and the Image Orientation (Patient) (0020,0037) attribute values specify the orientation of the image frame rows and columns. The mapping of pixel location  to the RCS is calculated as follows:

        size 12{ left [ matrix {
P rSub { size 8{x} }  {} ##
P rSub { size 8{y} }  {} ##
P rSub { size 8{z} }  {} ##
1
}  right ]= left [ matrix {
X rSub { size 8{x} } Δi {} # Y rSub { size 8{x} } Δj {} # 0 {} # S rSub { size 8{x} }  {} ##
X rSub { size 8{y} } Δi {} # Y rSub { size 8{y} } Δj {} # 0 {} # S rSub { size 8{y} }  {} ##
X rSub { size 8{z} } Δi {} # Y rSub { size 8{z} } Δj {} # 0 {} # S rSub { size 8{z} }  {} ##
0 {} # 0 {} # 0 {} # 1{}
}  right ] left [ matrix {
i {} ##
j {} ##
0 {} ##
1
}  right ]} {}

     = M
Where:
Pxyz  The coordinates of the voxel (i,j) in the frame’s image plane in units of mm.
Sxyz  The three values of the Image Position (Patient) (0020,0032) attributes. It is the location in mm from the origin of the RCS.
Xxyz  The values from the row (X) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
Yxyz  The values from the column (Y) direction cosine of the Image Orientation (Patient) (0020,0037) attribute.
i    Column index to the image plane. The first column is index zero.
i  Column pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.
j    Row index to the image plane. The first row index is zero.
j  Row pixel resolution of the Pixel Spacing (0028,0030) attribute in units of mm.

Additional constraints apply:
1)  The row and column direction cosine vectors shall be orthogonal, i.e. their dot product shall be zero.
2)  The row and column direction cosine vectors shall be normal, i.e. the dot product of each direction cosine vector with itself shall be unity.

</section>
    </entry>
    <entry group="0064" element="0007" name="&gt;&gt;Grid Dimensions" type="1">
      <description>The dimensions of the grid, in voxels. A triple representing the number of voxels along the X, Y, and Z axes.</description>
    </entry>
    <entry group="0064" element="0008" name="&gt;&gt;Grid Resolution" type="1">
      <description>The resolution of the grid voxels. A triple representing the size of a deformation voxel in along the X, Y, and Z dimension, in mm.</description>
    </entry>
    <entry group="0064" element="0009" name="&gt;&gt;Vector Grid Data" type="1">
      <description>A data stream of vectors. See C.20.3.1.3 for further explanation.</description>
      <section ref="C.20.3.1.3" name="">The Vector Grid Data attribute (0064,0009) contains the vector data. Each voxel in the Vector Grid Data attribute (0064,0009) is represented by an  vector. The vector describes the direction and magnitude of the deformation at the center of the deformation voxel.
The order of vectors sent for each vector plane shall be left to right, top to bottom, i.e., the upper left vector (labeled 1,1) is sent first followed by the remainder of row 1, followed by the first vector of row 2 (labeled 2,1) then the remainder of row 2 and so on.
A vector triple with values of (NaN,NaN,NaN) shall indicate that the transformation at that point of the deformation grid is undefined.
The size of this attribute value is determined by the dimensions specified in the Grid Dimensions attribute (0064,0007). For dimensions of XD\YD\ZD, the size of the attribute value can be calculated with the equation:
Number of Bytes = XD * YD * ZD * 3 * 4

</section>
    </entry>
    <entry group="0070" element="0314" name="&gt;Used Fiducials Sequence" type="3">
      <description>The fiducials used to determine the registration. One or more Items may be present.</description>
    </entry>
    <include ref="&gt;&gt; Include 'Image SOP Instance Reference Macro' Table 10-3" description="Reference to the Spatial Fiducial SOP Instance identifying the Used Fiducial(s)"/>
    <entry group="0070" element="031A" name="&gt;&gt;Fiducial UID" type="1">
      <description>The UID that identifies the fiducial used as registration input.</description>
    </entry>
  </module>
  <module ref="C.21.1" table="C.21.1-1" name="Spatial Fiducials Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Modality type.
Enumerated Value:
FID</description>
    </entry>
  </module>
  <module ref="C.21.2" table="C.21.2-1" name="Spatial Fiducials Module Attributes">
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the content creation started.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the content creation started.</description>
    </entry>
    <include ref="Include Content Identification Macro Table 10-12"/>
    <entry group="0070" element="031C" name="Fiducial Set Sequence" type="1">
      <description>A sequence of one or more items, each of which is a fiducial set.</description>
    </entry>
    <entry group="0020" element="0052" name="&gt;Frame of Reference UID" type="1C">
      <description>Identifies a Frame of Reference that may or may not be an image set (e.g. an atlas or physical space). See C.7.4.1.1.1 for further explanation. Required if Referenced Image Sequence (0008,1140) is absent. May be present otherwise.</description>
      <section ref="C.7.4.1.1.1" name="">The Frame of Reference UID (0020,0052) shall be used to uniquely identify a frame of reference for a series. Each series shall have a single Frame of Reference UID. However, multiple Series within a Study may share a Frame of Reference UID. All images in a Series that share the same Frame of Reference UID shall be spatially related to each other.
Notes:  1. Previous versions of this Standard defined a Data Element "Location", which has been retired. Frame of Reference UID provides a completely unambiguous identification of the image location reference used to indicate position.
  2. A common Frame of Reference UID may be used to spatially relate localizer images with a set of transverse images. However, in some cases (eg. multiple localizer images being related to a single set of transverse images) a common Frame of Reference UID may not be sufficient. The Referenced Image Sequence (0008,1140) provides an unambiguous method for relating localizer images.

</section>
    </entry>
    <entry group="0008" element="1140" name="&gt;Referenced Image Sequence" type="1C">
      <description>Identifies the set of images in which the fiducials are located. Required if Frame of Reference UID (0020,0052) is absent. May be present otherwise. One or more Items shall be present.
All referenced images shall have the same Frame of Reference UID if present in the images.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
    <entry group="0070" element="031E" name="&gt;Fiducial Sequence" type="1">
      <description>A sequence that specifies one or more fiducials, one item per fiducial.</description>
    </entry>
    <entry group="0070" element="0310" name="&gt;&gt;Fiducial Identifier" type="1">
      <description>A fiducial assignment identifier that is unique within this Fiducial Sequence item but may match the fiducial identifier of an equivalent feature in another item.</description>
    </entry>
    <entry group="0070" element="0311" name="&gt;&gt;Fiducial Identifier Code Sequence" type="1C">
      <description>A code sequence for a term that identifies a well-known fiducial type (potentially including methodology, anatomy, tools, etc.). Only one item shall be present. Required if Identifier (0070,0310) is absent. May be present otherwise.</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'Code Sequence Macro' Table 8.8-1" description="DCID 7101"/>
    <entry group="0070" element="031A" name="&gt;&gt;Fiducial UID" type="3">
      <description>Globally unique identifier for the fiducial instance of this fiducial assignment.</description>
    </entry>
    <entry group="0070" element="030F" name="&gt;&gt;Fiducial Description" type="3">
      <description>User description or comments about the fiducial.</description>
    </entry>
    <entry group="0070" element="0306" name="&gt;&gt;Shape Type" type="1">
      <description>See C.21.2.1.1 for defined terms.</description>
      <section ref="C.21.2.1.1" name="">For convenient registration, correlated Fiducials exist in each image set of the Registration Sequence. Correlated Fiducials are identified with either Fiducial Identifier (0070,0310) or Fiducial Identifier Code Sequence (0070,0311).

Shape Type (0070,0306) defines the geometric interpretation of the Contour Data (3006,0050) and Graphic Data (0070,0022). A point is defined as a triplet (x,y,z) in the case of spatial data or a pair (x,y) in the case of graphic data.
Defined Terms are:
POINT = a single point designating a single fiducial point.
Note: A point may be the epicenter of a more complex shape such as sphere.
LINE = two points that specify a line or axis such as the inter-orbital line. The point locations have no significance other than identifying the line, i.e. they are not line segment end points.
PLANE = three points that identify a plane such as the laterality plane
SURFACE = three or more points (usually many) that reside on, or near, a region of a curved surface. The surface may be flat or curved, closed or open. The point order has no significance.
RULER = two or more evenly spaced collinear points ordered sequentially along the line, such as a physical ruler placed in the imaging field.
L_SHAPE = three points of two perpendicular line segments, AB and BC, having a common end point B. The order of the points is: ABC. May represent an L-shaped marker placed in the imaging field.
T_SHAPE = three points of two perpendicular line segments AB and CD, such that C bisects AB. The order is ABD.
SHAPE = three or more points that specify the shape of a well-known fiducial type. The term in the Fiducial Identifier Code Sequence (0070,0311) defines the shape and the order of the points that represent it.
</section>
    </entry>
    <entry group="3006" element="0046" name="&gt;&gt;Number of Contour Points" type="1C">
      <description>Number of points (triplets) in Contour Data (3006,0050). Required if Contour Data is present.</description>
    </entry>
    <entry group="3006" element="0050" name="&gt;&gt;Contour Data" type="1C">
      <description>Specifies the coordinates of this item's fiducial. One triplet (x,y,z) shall be present for each point in the fiducial. See C.21.2.1.2 for further explanation. Required if Frame of Reference UID (0020,0052) is present in this item of the Fiducial Set Sequence (0070,031C). Shall not be present otherwise.
Note: Contour Data may not be properly encoded if Explicit-VR transfer syntax is used and the VL of this attribute exceeds 65534 bytes.</description>
      <section ref="C.21.2.1.2" name="">Contour Data (3006,0050) is an ordered set of triplets that defines a shape. The triplets (x,y,z) denote points in the Reference Coordinate System of the Registration Instance.
Note:  Contours may associate observational data with a set of Image features or specify coordinates that are input data for a measurement.
</section>
    </entry>
    <entry group="0070" element="0312" name="&gt;&gt;Contour Uncertainty Radius" type="3">
      <description>The estimated uncertainty radius for the Contour Data in mm. See C.21.2.1.3</description>
      <section ref="C.21.2.1.3" name="">The uncertainty is an estimate of the standard deviation of the fiducial location process.
</section>
    </entry>
    <entry group="0070" element="0318" name="&gt;&gt;Graphic Coordinates Data Sequence" type="1C">
      <description>The image pixel locations of the fiducial's points. Shall contain one or more items. More than one item shall be present only if a fiducial spans more than one image. Required if Contour Data is not present. May be present otherwise.</description>
    </entry>
    <entry group="0070" element="0022" name="&gt;&gt;&gt;Graphic Data" type="1">
      <description>Graphic point coordinates of the fiducial points in the image of the Referenced Image Sequence. If Fiducial's Contour Data (3006,0050) is present, these points correlate to the points in the Contour Data, one row-column pair for each point and in the same order.
See C.10.5.1.2 for further explanation.</description>
      <section ref="C.10.5.1.2" name="">Graphic Data (0070,0022) contains the points in the graphic annotation, each dimension for the first point, followed by dimensions for second point, etc. For a two dimensional curve: X1, Y1, X2, Y2, etc. The first (X) dimension corresponds to the image or Specified Displayed Area column (horizontal offset), and the second (Y) dimension corresponds to the image or Specified Displayed Area row (vertical offset). The Value Representation of all components of the N-tuple shall be the same. The image or Specified Displayed Area relative drawing space is defined in Graphic Annotation Units (0070,0005).
If Graphic Type (0070,0023) is POINT, then two values (one point) shall be specified and the single point specified is to be drawn.
If Graphic Type (0070,0023) is POLYLINE, then the points are to be interpreted as an n-tuple list of end points between which straight lines are to be drawn.
If Graphic Type (0070,0023) is INTERPOLATED, then the points are to be interpreted as an n-tuple list of end points between which some form of implementation dependent curved lines are to be drawn. The rendered line shall pass through all the specified points.
If Graphic Type (0070,0023) is CIRCLE, then exactly two points shall be present; the first point is to be interpreted as the center and the second point as a point on the circumference of a circle, some form of implementation dependent representation of which is to be drawn.
If Graphic Type (0070,0023) is ELLIPSE, then exactly four points shall be present; the first two points are to be interpreted as the endpoints of the major axis and the second two points as the endpoints of the minor axis of an ellipse, some form of implementation dependent representation of which is to be drawn.
The notion of “open” or “closed” has no inherent meaning in the context of an arbitrary graphic, other than in the condition for the presence of Graphic Filled (0070,0024). The graphic has no semantic notion of an associated observation such as a region of interest, except that which the unformatted text in the same Item may describe.
The choice of pixel value used to represent the graphic on a display is defined in the Graphic Layer Module C.10.7.

Figure C.10.5-1
Sub-pixel Addressing Units in PIXEL Space
</section>
    </entry>
    <entry group="0008" element="1140" name="&gt;&gt;&gt;Referenced Image Sequence" type="1">
      <description>A sequence that specifies the image containing the fiducial's graphic coordinates. Only one item shall be present. Shall be an image within the set of the images in the Referenced Image Sequence (0008,1140) of the encapsulating Fiducial Set Sequence (0070,031C) item.</description>
    </entry>
    <include ref="&gt;&gt;&gt;&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
  </module>
  <module ref="C.22.1" table="C.22.1-1" name="Media Creation Management Module Attributes">
    <entry group="0088" element="0130" name="Storage Media File-Set ID">
      <description>User or implementation specific human readable identification of the Storage Media to be created.</description>
    </entry>
    <entry group="0088" element="0140" name="Storage Media File-Set UID">
      <description>Uniquely identifies a Storage Media to be created.</description>
    </entry>
    <entry group="2000" element="0010" name="Number of Copies">
      <description>Number of copies of set of media to be created for storing this file-set.
Note: If the entire request fits on a single piece of media per copy, then this value corresponds to the actual number of pieces of media to be created.</description>
    </entry>
    <entry group="2200" element="0020" name="Request Priority">
      <description>Specifies the priority of the request.
Enumerated Values:
HIGH
MED
LOW</description>
    </entry>
    <entry group="2200" element="0001" name="Label Using Information Extracted From Instances">
      <description>Specifies whether or not to extract label information from the instances.
Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="2200" element="0002" name="Label Text">
      <description>Unformatted free text to include in the label instead of or in addition to information extracted from the instances.</description>
    </entry>
    <entry group="2200" element="0003" name="Label Style Selection">
      <description>An implementation-dependent code string that may be used as a hint to select a particular layout or format of label.</description>
    </entry>
    <entry group="2200" element="0004" name="Media Disposition">
      <description>Unstructured text that describes where and to whom the media is to be sent.</description>
    </entry>
    <entry group="2200" element="0005" name="Barcode Value">
      <description>String that describes the bar code value to be printed on the media label.
Note It is SCU responsibility to convey a value for this attribute coherent in length and content with the requested Barcode Symbology (2200,0006).</description>
    </entry>
    <entry group="2200" element="0006" name="Barcode Symbology">
      <description>Code string that describes the bar code symbology that shall be used for printing the Barcode Value (2200,0005).
See Section C.22.1.1 for Defined Terms.</description>
      <section ref="C.22.1.1" name="">Defined Terms for Barcode Symbology (2200,0006) are:
<defined-terms><term value="CODE128" meaning="Code 128. ISO/IEC 15417:2000 Information technology – Automatic identification and data capture techniques – Bar code symbology specification – Code128"/><term value="CODE39" meaning="Code 39. ISO/IEC 16388:1999 Information technology – Automatic identification and data capture techniques – Bar code symbology specifications – Code 39"/><term value="INTER_2_5" meaning="Interleaved 2 of 5. (also known as USS ITF 2/5, I-2/5, ITF 2of5) ISO/IEC 16390:1999 Information technology – Automatic identification and data capture techniques – Bar code symbology specifications – Interleaved 2 of 5"/><term value="HIBC" meaning="ANSI/HIBC 1-1996 Health Industry Bar Code (HIBC) Provider Applications Standard"/></defined-terms>
Note  This table doesn’t suppose to list all the bar code symbologies in use (there are currently more than 400). Implementations supporting other symbologies can extend this list. Implementation specific code values shall be defined in the Conformance Statement.

</section>
    </entry>
    <entry group="2200" element="0007" name="Allow Media Splitting">
      <description>A flag indicating if the SCP is allowed to split this request over more than one piece of media.
Enumerated Values:
YES
NO

Note: 1. The SCP is not required to support the split of a media creation request across more than one piece of media.
2. If the size of the set of SOP instances is greater than the media storage capacity, and this flag has been set to NO, the SCP shall refuse to process the request.</description>
    </entry>
    <entry group="2200" element="000F" name="Allow Lossy Compression">
      <description>A flag indicating if the SCP is allowed to perform lossy compression.
Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="2200" element="0008" name="Include Non-DICOM Objects">
      <description>A flag indicating if the SCP should include in the media additional Non-DICOM information/objects
Defined Terms:
NO
FOR_PHYSICIAN
FOR_PATIENT
FOR_TEACHING
FOR_RESEARCH</description>
    </entry>
    <entry group="2200" element="0009" name="Include Display Application">
      <description>A flag indicating if the SCP should include on the media a DICOM Instance Display Application.
Enumerated Values:
NO
YES</description>
    </entry>
    <entry group="2200" element="000A" name="Preserve Composite Instances After Media Creation">
      <description>A flag to indicate whether or not the SCU intends to issue a subsequent media creation request referencing some or all of the instances contained in Referenced SOP Sequence (0008,1199).
Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="0008" element="1199" name="Referenced SOP Sequence">
      <description>A sequence of Items where each Item references a single SOP Instance, the Media Application Profile to be used, and, where applicable, the icon representing the referenced image</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="2200" element="000C" name="&gt;Requested Media Application Profile">
      <description>The Media Application Profile to be used for this SOP Instance.
Note: This is the label of the profile as defined in PS 3.11, e.g. "STD-XABC-CD".</description>
    </entry>
    <entry group="0088" element="0200" name="&gt;Icon Image Sequence">
      <description>This Icon Image is representative of the Image.</description>
    </entry>
    <include ref="&gt;&gt; Include 'Image Pixel Macro' Table C.7-11.2"/>
    <entry group="2100" element="0020" name="Execution Status">
      <description>Execution status of a request.
See Section C.22.1.2 for Enumerated Values</description>
      <section ref="C.22.1.2" name="">Enumerated Values for Execution Status (2100,0020) are:
<enumerated-values><term value="IDLE" meaning="The SCP has created the media creation management instance, but it has not been yet scheduled."/><term value="PENDING" meaning="This media creation management instance is still scheduled for processing."/><term value="CREATING" meaning="This media creation management instance is being processed."/><term value="DONE" meaning="This media creation management instance has been successfully processed."/><term value="FAILURE" meaning="This media creation management instance failed to be processed."/></enumerated-values>
         </section>
    </entry>
    <entry group="2100" element="0030" name="Execution Status Info">
      <description>Additional information about Execution Status (2100,0020).
When Execution Status is DONE, CREATING or IDLE, Defined Terms are:
NORMAL
See Section C.22.1.3 for Defined Terms when the Execution Status is PENDING or FAILURE.</description>
      <section ref="C.22.1.3" name="">Defined Terms for Execution Status Info (2100,0030) are:
<defined-terms><term value="CHECK_MCD_OP" meaning="The media creation request could not be accomplished since the device is not ready at this time and needs to be checked by an operator (e.g., covers/doors opened or device jammed)."/><term value="CHECK_MCD_SRV" meaning="The media creation request could not be accomplished since the device is not ready at this time and needs to be checked by a vendor service engineer (e.g., internal component failure)."/><term value="DIR_PROC_ERR" meaning="The DICOMDIR building process failed for some unspecified reason (e.g., mandatory attributes or values missing)."/><term value="DUPL_REF_INST" meaning="Duplicated instances in the Referenced SOP Sequence (0008,1199)."/><term value="INST_AP_CONFLICT" meaning="One or more of the elements in the Referenced SOP Sequence (0008,1199) are in conflict (e.g., the SOP Class specified is not consistent with the requested Application Profile)."/><term value="INST_OVERSIZED" meaning="A single instance size exceeds the actual media capacity."/><term value="INSUFFIC_MEMORY" meaning="There is not enough memory available to complete this request."/><term value="MCD_BUSY" meaning="Media creation device is not available at this time, but should become ready without user intervention (e.g the media creation device‘s buffer capacity is full)."/><term value="MCD_FAILURE" meaning="Media creation device fails to operate."/><term value="NO_INSTANCE" meaning="One or more of the SOP Instances in the Referenced SOP Sequence (0008,1199) are not available."/><term value="NOT_SUPPORTED" meaning="One or more of the Application Profiles, and/or SOP Classes, referenced in the Referenced SOP Sequence (0008,1199) are not supported by the SCP."/><term value="OUT_OF_SUPPLIES" meaning="No more supplies (e.g., blank media, labeling ink) are available for the media creation device. Operator intervention is required to replenish the supply."/><term value="PROC_FAILURE" meaning="A general processing failure was encountered."/><term value="QUEUED" meaning="This Media Creation Management instance is still in queue"/><term value="SET_OVERSIZED" meaning="The file-set size exceeds the actual media capacity, and the device is not capable of splitting across multiple pieces of media."/><term value="UNKNOWN" meaning="There is an unspecified problem"/></defined-terms>
Note:  For most of the above statuses, the SCU can obtain more details about the processing errors (e.g., what are the SOP instances not available) by using the Failure Reason Attribute (0008,1197) within the Failed SOP Sequence (0008,1198).

</section>
    </entry>
    <entry group="2200" element="000B" name="Total Number of Pieces of Media Created">
      <description>Number of pieces of media that have been successfully created, in order to store all copies of the requested file-set.
Note: If the entire request fits on a single piece of media per copy, then this value corresponds to the number of copies of media created.</description>
    </entry>
    <entry group="0008" element="1198" name="Failed SOP Sequence">
      <description>A sequence of Items describing SOP Instances for which media creation failed.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="2200" element="000C" name="&gt;Requested Media Application Profile">
      <description>The Media Application Profile used for this SOP Instance.
Note: This is the label of the profile as defined in PS 3.11, e.g. "STD-XABC-CD".</description>
    </entry>
    <entry group="0008" element="1197" name="&gt;Failure Reason">
      <description>The reason that media creation failed for this SOP Instance.
See Section C.22.1.4.</description>
      <section ref="C.22.1.4" name="">Defined Terms for Failure Reason (0008,1197) are:
<defined-terms><term value="Code" meaning="Further meaning"/><term value="0110H" meaning="Processing failure"/><term value="0112H" meaning="No such object instance"/><term value="0122H" meaning="Referenced SOP Class not supported"/><term value="0119H" meaning="Class/Instance conflict"/><term value="0201H" meaning="Media Application Profiles conflict"/><term value="0202H" meaning="Media Application Profile / Instance conflict"/><term value="0203H" meaning="Media Application Profile / Compression conflict"/><term value="0204H" meaning="Media Application Profile not supported"/><term value="0205H" meaning="Instance size exceeded"/><term value="0120H" meaning="Missing attribute"/><term value="0121H" meaning="Missing attribute value"/></defined-terms>
         </section>
    </entry>
    <entry group="2200" element="000E" name="&gt;Failure Attributes">
      <description>Attributes associated with the Failure Reason (0008,1197).
See Section C.22.1.4.</description>
      <section ref="C.22.1.4" name="">Defined Terms for Failure Reason (0008,1197) are:
<defined-terms><term value="Code" meaning="Further meaning"/><term value="0110H" meaning="Processing failure"/><term value="0112H" meaning="No such object instance"/><term value="0122H" meaning="Referenced SOP Class not supported"/><term value="0119H" meaning="Class/Instance conflict"/><term value="0201H" meaning="Media Application Profiles conflict"/><term value="0202H" meaning="Media Application Profile / Instance conflict"/><term value="0203H" meaning="Media Application Profile / Compression conflict"/><term value="0204H" meaning="Media Application Profile not supported"/><term value="0205H" meaning="Instance size exceeded"/><term value="0120H" meaning="Missing attribute"/><term value="0121H" meaning="Missing attribute value"/></defined-terms>
         </section>
    </entry>
    <entry group="2200" element="000D" name="Referenced Storage Media Sequence">
      <description>A Sequence describing the identifiers of all pieces of media created to satisfy the request. One or more items are allowed.
Note: If the SCP splits a media creation request across more than one piece of media (e.g. if it doesn't fit on one), then all the created pieces of media will be included in this Sequence.</description>
    </entry>
    <entry group="0088" element="0130" name="&gt; Storage Media File-Set ID">
      <description>User or implementation specific human readable identification of the Storage Media that has been created.</description>
    </entry>
    <entry group="0088" element="0140" name="&gt; Storage Media File-Set UID">
      <description>Uniquely identifies the Storage Media that has been created.</description>
    </entry>
  </module>
  <module ref="C.23.1" table="C.23.1-1" name="Hanging Protocol Definition Module Attributes">
    <entry group="0072" element="0002" name="Hanging Protocol Name" type="1">
      <description>Short descriptor that identifies the Hanging Protocol.</description>
    </entry>
    <entry group="0072" element="0004" name="Hanging Protocol Description" type="1">
      <description>Explanation of the objective or intent of the Hanging Protocol.</description>
    </entry>
    <entry group="0072" element="0006" name="Hanging Protocol Level" type="1">
      <description>Identifies the level at which this Hanging Protocol is defined, and the intended use.
Enumerated values:
MANUFACTURER
SITE
USER_GROUP
SINGLE_USER</description>
    </entry>
    <entry group="0072" element="0008" name="Hanging Protocol Creator" type="1">
      <description>Identifies the creator of the Hanging Protocol.</description>
    </entry>
    <entry group="0072" element="000A" name="Hanging Protocol Creation DateTime" type="1">
      <description>Date and time on which the Hanging Protocol was created.</description>
    </entry>
    <entry group="0072" element="000C" name="Hanging Protocol Definition Sequence" type="1">
      <description>Sequence that defines the type of imaging studies to which this Hanging Protocol applies. One or more sequence items shall be present. See C.23.1.1.1.</description>
      <section ref="C.23.1.1.1" name="">The Hanging Protocol Definition Sequence (0072,000C) provides a collection of one or more sequence items that defines the intent for the Hanging Protocol with respect to modality, anatomy, laterality, procedure and/or reason.
This allows for some degree of flexibility in defining the intent for the Hanging Protocol, while providing a precise structure for query matching using the existing rules for Sequence Matching, as defined in PS 3.4.
Notes:1. The Hanging Protocol Definition Sequence (0072,000C) does not imply anything about the related image sets. These are defined in the Image Sets Sequence (0072,0020).
2. When creating a Hanging Protocol Instance, the values that are used for Procedure Code Sequence (0008,1032) or Reason for Requested Procedure Code Sequence (0040,100A) may come from a variety of sources, but are expected to be consistent throughout the domain in which a Hanging Protocol Instance will be exchanged. The following are recommended as potential sources of values.
Procedure Code Sequence (0008,1032):
</section>
    </entry>
    <entry group="0008" element="0060" name="&gt;Modality" type="1C">
      <description>Type of equipment that originally acquired the data used to create images or related objects to which this Hanging Protocol applies. See C.7.3.1.1.1 for Defined Terms.
Required if Anatomic Region Sequence (0008,2218) is not present. May be present otherwise.</description>
      <section ref="C.7.3.1.1.1" name="">Defined Terms for the Modality (0008,0060) are:
<defined-terms><term value="CR" meaning="Computed Radiography"/><term value="MR" meaning="Magnetic Resonance"/><term value="US" meaning="Ultrasound"/><term value="BI" meaning="Biomagnetic imaging"/><term value="DD" meaning="Duplex Doppler"/><term value="ES" meaning="Endoscopy"/><term value=""/><term value="PT" meaning="Positron emission tomography (PET)"/><term value="ST" meaning="Single-photon emission computed tomography (SPECT)"/><term value="XA" meaning="X-Ray Angiography"/><term value="RTIMAGE" meaning="Radiotherapy Image"/><term value="RTSTRUCT" meaning="Radiotherapy Structure Set"/><term value="RTRECORD" meaning="RT Treatment Record"/><term value="DX" meaning="Digital Radiography"/><term value="IO" meaning="Intra-oral Radiography"/><term value="GM" meaning="General Microscopy"/><term value="XC" meaning="External-camera Photography"/><term value="AU" meaning="Audio"/><term value="EPS" meaning="Cardiac Electrophysiology"/><term value="SR" meaning="SR Document"/><term value="OP" meaning="Ophthalmic Photography"/><term value="OCT" meaning="Optical Coherence Tomography (non-Ophthalmic)"/><term value="OPV" meaning="Ophthalmic Visual Field"/><term value="KO" meaning="Key Object Selection"/><term value="REG" meaning="Registration"/><term value="BDUS" meaning="Bone Densitometry (ultrasound)"/><term value="DOC" meaning="Document"/></defined-terms>
Retired Defined Terms for the Modality (0008,0060) are:
<retired-defined-terms><term value="DS" meaning="Digital Subtraction Angiography (retired)"/><term value="DF" meaning="Digital fluoroscopy (retired)"/><term value="AS" meaning="Angioscopy"/><term value="EC" meaning="Echocardiography"/><term value="FA" meaning="Fluorescein angiography"/><term value="DM" meaning="Digital microscopy"/><term value="MA" meaning="Magnetic resonance angiography"/></retired-defined-terms>
Note:  1. The XA modality incorporates the retired modality DS.
  2. The RF modality incorporates the retired modalities CF, DF, VF.
  3. The modality listed in the Modality Data Element (0008,0060) may not match the name of the IOD in which it appears. For example, a SOP instance from XA IOD may list the RF modality when an RF implementation produces an XA object.
  4. The MR modality incorporates the retired modalities MA and MS.

</section>
    </entry>
    <entry group="0008" element="2218" name="&gt;Anatomic Region Sequence" type="1C">
      <description>Sequence that identifies the anatomic region of interest to which this Hanging Protocol applies. One or more sequence items may be present.
Required if Modality (0008,0060) is not present. May be present otherwise.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="Defined Context ID 4"/>
    <entry group="0020" element="0060" name="&gt;Laterality" type="2C">
      <description>Laterality of the body part to which this Hanging Protocol applies.
Enumerated Values:
R - Right
L - Left
B - Both
U - Unpaired
Zero length means not applicable.
Required if Anatomic Region Sequence (0008,2218) is present.</description>
    </entry>
    <entry group="0008" element="1032" name="&gt;Procedure Code Sequence" type="2">
      <description>Sequence that identifies a procedure to which this Hanging Protocol applies. Zero or more sequence items may be present.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined"/>
    <entry group="0040" element="100A" name="&gt;Reason for Requested Procedure Code Sequence" type="2">
      <description>Sequence that identifies a reason for procedure to which this Hanging Protocol applies. Zero or more sequence items may be present.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="No Baseline Context ID is defined"/>
    <entry group="0072" element="0014" name="Number of Priors Referenced" type="1">
      <description>Identifies the number of prior image sets used in this Hanging Protocol.</description>
    </entry>
    <entry group="0072" element="0020" name="Image Sets Sequence" type="1">
      <description>Sequence describing one or more types of Image Sets to which the Hanging Protocol applies. One or more sequence items shall be present. See C.23.1.1.2.</description>
      <section ref="C.23.1.1.2" name="">The Image Sets Sequence (0072,0020) within a Hanging Protocol Instance serves to identify the type of image or other object sets to which the Hanging Protocol is intended to apply. Multiple types of image sets may be identified for a Hanging Protocol, to combine, for example, multiple imaging studies for a specific anatomy, or multiple imaging studies performed over a period of time, to monitor the progress of a condition. All image sets shall be for the same patient.
The images to be included in an Image Set may be specified directly by matching attribute values within the images, or indirectly through Key Object Selection Documents or Presentation States by matching their attribute values.
Key Object Selection Documents shall be matched by their SOP Class UID. The available Key Object Selection Documents may be further matched on the values of their other attributes (e.g., Concept Name Code Sequence, Coding Scheme Designator = “DCM” and Code Value = “113003”, which has a code meaning of “For Surgery”). When the Hanging Protocol Instance is applied, the image object instances referenced by the matching Key Object Selection Document instances comprise the image set.
Presentation States shall be matched by their SOP Class UID. The available Presentation States may be further matched on the values of their other attributes (e.g., Content Label). When the Hanging Protocol Instance is applied, the image object instances referenced by the matching Presentation State instances comprise the image set.
Note: Image Sets Sequence (0072,0020) allows other objects such as waveforms and SR documents to be identified. However, Hanging Protocol Display module operations such as filtering, reformatting, and sorting are defined only for image objects. The only expectation for non-image objects is to associate the objects with a position on a screen.
Each sequence item in the Image Sets Sequence (0072,0020) shall follow these rules:
</section>
    </entry>
    <entry group="0072" element="0022" name="&gt;Image Set Selector Sequence" type="1">
      <description>Sequence containing Image Set selection attributes and values that are used to identify one type of image or object set for the Hanging Protocol. One or more sequence items shall be present. See C.23.1.1.3.</description>
      <section ref="C.23.1.1.3" name="">The Image Set Selector Sequence (0072,0022) contains sequence items that specify the DICOM attribute tags and values that shall be used to identify the image or other object set.
The Image Set Selector Usage Flag (0072,0024) indicates whether the attribute identified by the Selector Attribute (0072,0026) causes matching to succeed or fail if the attribute is not available in an image object.
Within a sequence item, the Selector Attribute (0072,0026) identifies a DICOM attribute tag that is likely to be present in image or other object instances that are desired for the Image Set. If it is a multi-valued attribute, the Selector Value Number (0072,0028) indicates which value is intended to be used for matching. The Selector Attribute VR (0072,0050) identifies the Value Representation of the Selector Attribute (0072,0026). The value of Selector Attribute VR (0072,0050) determines which attribute of the Hanging Protocol Selector Attribute Value Macro is required to specify one or more desired values for the DICOM attribute tag. If more than one value is specified for the attribute, or more than one sequence item is specified in the Selector Code Sequence Value (0072,0080), then image object instances with a corresponding attribute that matches any one of the values shall be included in the Image Set.
Note: The values used for the Selector Attribute (0072,0026) are intended to identify a type of image set via the general categories of modality, anatomy, procedure intent and/or reason. Therefore the values of the tags represented by Selector Attribute (0072,0026) are likely to be coded terms, enumerated values, defined terms or free text. The use of free text attributes is less desirable, because their values are less predictable for matching.
In an image object, some attributes occur at the top level, or nested within a Sequence or Functional Group Sequence, or both. In addition, a Private Attribute may be identified as a Selector Attribute (0072,0026). The attributes of the Hanging Protocol Selector Attribute Context Macro identify a Sequence, Functional Group Sequence, or Private Group context for the Selector Attribute (0072,0026).
The creator of a Hanging Protocol Instance uses this collection of attributes to identify one type of image set to which the Hanging Protocol is intended to apply. The user of a Hanging Protocol Instance (e.g., softcopy review workstation or pre-fetching application) uses this collection of attributes to match a specific image set to a Hanging Protocol, and/or to determine which image sets need to be retrieved in order to use a Hanging Protocol Instance. The Key Attributes to match against to obtain image sets are specified in the Selector Attribute (0072,0026) and its context in each sequence item.
If the value of the tag represented by Selector Attribute (0072,0026) contains a free text description (i.e., Selector Attribute VR = LO, SH, ST, LT, UT), whether exact or partial matching is used to identify a specific image instance when applying a Hanging Protocol Instance is implementation dependent.
</section>
    </entry>
    <entry group="0072" element="0024" name="&gt;&gt;Image Set Selector Usage Flag" type="1">
      <description>Indicates the behavior of matching against an image object when the Selector Attribute (0072,0026) is not available in the image object.
Enumerated Values:
MATCH - if the attribute is not in the image object, consider the image to be a match anyway.
NO_MATCH - if the attribute is not in the image object, then do not consider the image to be a match.</description>
    </entry>
    <entry group="0072" element="0026" name="&gt;&gt;Selector Attribute" type="1">
      <description>Data Element Tag of an Attribute from an Image or other IOD to use for Image Set selection.</description>
    </entry>
    <entry group="0072" element="0050" name="&gt;&gt;Selector Attribute VR" type="1">
      <description>The Value Representation of the Selector Attribute (0072,0026). See PS 3.5 for Enumerated Values of Value Representation.</description>
    </entry>
    <include ref="&gt;&gt;Include Hanging Protocol Selector Attribute Context Macro Table C.23.4-1"/>
    <include ref="&gt;&gt;Include Hanging Protocol Selector Attribute Value Macro Table C.23.4-2"/>
    <entry group="0072" element="0028" name="&gt;&gt;Selector Value Number" type="1">
      <description>Positive integer identifying which value of a multi-valued attribute identified by Selector Attribute (0072,0026) is to be used for Image Set selection. The value 1 identifies the first value. The value zero identifies any value.</description>
    </entry>
    <entry group="0072" element="0030" name="&gt;Time Based Image Sets Sequence" type="1">
      <description>Sequence containing time based Image Set selection categories and values that are used to identify one type of image set for the Hanging Protocol per sequence item. One or more sequence items shall be present. The Image Set Selector Sequence (0072,0022) shall be applied to each sequence item to define an image set. See C.23.1.1.2.</description>
      <section ref="C.23.1.1.2" name="">The Image Sets Sequence (0072,0020) within a Hanging Protocol Instance serves to identify the type of image or other object sets to which the Hanging Protocol is intended to apply. Multiple types of image sets may be identified for a Hanging Protocol, to combine, for example, multiple imaging studies for a specific anatomy, or multiple imaging studies performed over a period of time, to monitor the progress of a condition. All image sets shall be for the same patient.
The images to be included in an Image Set may be specified directly by matching attribute values within the images, or indirectly through Key Object Selection Documents or Presentation States by matching their attribute values.
Key Object Selection Documents shall be matched by their SOP Class UID. The available Key Object Selection Documents may be further matched on the values of their other attributes (e.g., Concept Name Code Sequence, Coding Scheme Designator = “DCM” and Code Value = “113003”, which has a code meaning of “For Surgery”). When the Hanging Protocol Instance is applied, the image object instances referenced by the matching Key Object Selection Document instances comprise the image set.
Presentation States shall be matched by their SOP Class UID. The available Presentation States may be further matched on the values of their other attributes (e.g., Content Label). When the Hanging Protocol Instance is applied, the image object instances referenced by the matching Presentation State instances comprise the image set.
Note: Image Sets Sequence (0072,0020) allows other objects such as waveforms and SR documents to be identified. However, Hanging Protocol Display module operations such as filtering, reformatting, and sorting are defined only for image objects. The only expectation for non-image objects is to associate the objects with a position on a screen.
Each sequence item in the Image Sets Sequence (0072,0020) shall follow these rules:
</section>
    </entry>
    <entry group="0072" element="0032" name="&gt;&gt;Image Set Number" type="1">
      <description>A monotonically increasing integer, starting from 1, incrementing by one, unique within the Hanging Protocol Instance.
Note: Each item of the Display Sets Sequence (0072,0200) references one Image Set Number (0072,0032).</description>
    </entry>
    <entry group="0072" element="0034" name="&gt;&gt;Image Set Selector Category" type="1">
      <description>Category of the Time Based Image Set selector.
Enumerated Values:
RELATIVE_TIME
ABSTRACT_PRIOR</description>
    </entry>
    <entry group="0072" element="0038" name="&gt;&gt;Relative Time" type="1C">
      <description>Exactly two numeric values, indicating the start and end values of a prior range of instance acquisition times relative to the date and time of a current image set. The units shall be specified in Relative Time Units (0072,003A).
The value pair 0\0 shall indicate a current image set. The value pair n\n shall indicate "prior from the instance acquisition time of a current image set by n units".
Required if the value of Image Set Selector Category (0072,0034) is RELATIVE_TIME.
Note: 1. A value pair "1\7" with Relative Time Units (0072,003A) of DAYS would indicate the range "prior by 1 to 7 days before a current image set".
2. The VR of this attribute is unsigned, hence future time cannot be represented.</description>
    </entry>
    <entry group="0072" element="003A" name="&gt;&gt;Relative Time Units" type="1C">
      <description>Units of time for Relative Time (0072,0038).
Enumerated Values:
SECONDS, MINUTES, HOURS, DAYS, WEEKS, MONTHS, YEARS.
Required if Relative Time (0072,0038) is present.</description>
    </entry>
    <entry group="0072" element="003C" name="&gt;&gt;Abstract Prior Value" type="1C">
      <description>Identifies a prior image set in abstract terms.
Exactly two integer values, indicating the range of prior studies to include. Each value shall be greater than zero, where 1 indicates the most recent prior and higher values indicate successively older priors. The special value -1 shall indicate the oldest prior.
Notes: 1. The value pair n\n indicates the nth prior.
2. The value pair -1\-1 indicates the oldest prior.
3. The value pair m\n indicates the mth through nth priors, where m is the more recent prior.
4. The value pair 1\-1 indicates all priors.
5. The value pair m\-1 indicates the mth prior and all priors older than m.
Required if Image Set Selector Category (0072,0034) is ABSTRACT_PRIOR and Abstract Prior Code Sequence (0072,003E) is not present.</description>
    </entry>
    <entry group="0072" element="003E" name="&gt;&gt;Abstract Prior Code Sequence" type="1C">
      <description>Identifies a prior image set using coded terminology. Only one sequence item shall be present.
Required if Image Set Selector Category (0072,0034) is ABSTRACT_PRIOR and Abstract Prior Value (0072,003C) is not present.</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="Defined Context ID 31"/>
    <entry group="0072" element="0040" name="&gt;&gt;Image Set Label" type="3">
      <description>Description of the objective of the image set defined by this sequence item.</description>
    </entry>
    <entry group="0072" element="000E" name="Hanging Protocol User Identification Code Sequence" type="2">
      <description>Sequence that provides a coded identifier for the person, group, or site for which this Hanging Protocol was defined. Zero or one item shall be present in the sequence.
Note: If a standardized naming schema becomes available, it should be used. Meanwhile, local coding schemes such as employee numbers and department numbers are likely to be used.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="No baseline context ID is defined."/>
    <entry group="0072" element="0010" name="Hanging Protocol User Group Name" type="3">
      <description>Group or site for which this Hanging Protocol was defined.</description>
    </entry>
    <entry group="0072" element="0012" name="Source Hanging Protocol Sequence" type="3">
      <description>Sequence that identifies the Hanging Protocol from which this Hanging Protocol was derived, or on which it is based. One sequence item may be present.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
  </module>
  <module ref="C.23.2" table="C.23.2-1" name="Hanging Protocol Environment Module Attributes">
    <entry group="0072" element="0100" name="Number of Screens" type="2">
      <description>Positive integer indicating the number of screens for which this Hanging Protocol is intended.</description>
    </entry>
    <entry group="0072" element="0102" name="Nominal Screen Definition Sequence" type="2">
      <description>Sequence of zero or more items that describes the set of screens for which this Hanging Protocol is intended.</description>
    </entry>
    <entry group="0072" element="0104" name="&gt;Number of Vertical Pixels" type="1">
      <description>Positive integer indicating the intended number of rows of the addressable area of the screen in pixels.
Note: The goal is not absolute size matching.</description>
    </entry>
    <entry group="0072" element="0106" name="&gt;Number of Horizontal Pixels" type="1">
      <description>Positive integer indicating the intended number of columns of the addressable area of the screen in pixels.
Note: The goal is not absolute size matching.</description>
    </entry>
    <entry group="0072" element="0108" name="&gt;Display Environment Spatial Position" type="1">
      <description>Exactly four unitless floating point values indicating the rectangular coordinate position of the screen within the overall bounding box that encompasses all the screens. See C.23.2.1.1.</description>
      <section ref="C.23.2.1.1" name="">For the Display Environment Spatial Position (0072,0108) attribute, the lower left corner of the overall bounding box has Cartesian coordinates of (0.0,0.0). The upper right corner has coordinates of (1.0,1.0). The scale of the box is based on the Number of Vertical Pixels (0072,0104) and Number of Horizontal Pixels (0072,0106), not the physical size of the screens that are part of the workstation. The coordinates of each individual screen’s box are defined in absolute coordinates relative to the (0,0) and (1,1) range of the overall box. Position of a box is given by a (x1,y1), (x2,y2) pair that identifies the upper left corner and lower right corner if the box is rectangular.

Note:  The goal is not absolute position matching of the image boxes rendered on the screens using Hanging Protocol layout information, but that the relative positioning of the image boxes should be consistent between different workstations.
The following figure depicts a 1K x 1K screen positioned to the left of a 2K x 2.5K screen. The Display Environment Spatial Position (0072,0108) of the 1K x 1K screen is (0.0,0.4) (0.33,0.0), and the Display Environment Spatial Position (0072,0108) of the 2K x 2.5K screen is (0.33,1.0) (1.0,0.0).

</section>
    </entry>
    <entry group="0072" element="010A" name="&gt;Screen Minimum Grayscale Bit Depth" type="1C">
      <description>Positive integer indicating the desired minimum number of grayscale bits per pixel of the screen.
Required if Screen Minimum Color Bit Depth (0072,010C) is not present.</description>
    </entry>
    <entry group="0072" element="010C" name="&gt;Screen Minimum Color Bit Depth" type="1C">
      <description>Positive integer indicating the desired minimum total number of bits per color channel used to present a pixel.
Required if Screen Minimum Grayscale Bit Depth (0072,010A) is not present.
Note: A 24-bit color system with 8 bits per color channel (red, green, blue) would have a value of 8.</description>
    </entry>
    <entry group="0072" element="010E" name="&gt;Application Maximum Repaint Time" type="3">
      <description>Positive integer indicating the desired maximum time in milliseconds required by the application to repaint the full screen once (i.e., recalculate all pixels and paint them to the screen).
Note: This is not the screen refresh time.</description>
    </entry>
  </module>
  <module ref="C.23.3" table="C.23.3-1" name="Hanging Protocol Display Module Attributes">
    <entry group="0072" element="0200" name="Display Sets Sequence" type="1">
      <description>Sequence that describes one or more display sets used to present the Image Sets defined in the Image Sets Sequence (0072,0020). One or more sequence items shall be present. See C.23.3.1.</description>
      <section ref="C.23.3.1" name="">The attributes of a Display Set Sequence Item shall be applied to the image set represented by the value of Image Set Number (0072,0032) in the following order:
</section>
    </entry>
    <entry group="0072" element="0202" name="&gt;Display Set Number" type="1">
      <description>A monotonically increasing integer, starting from 1, incrementing by one, unique within the Hanging Protocol Instance. It shall be used to identify linked display sets in the Display Set Scrolling Group (0072,0212).</description>
    </entry>
    <entry group="0072" element="0203" name="&gt;Display Set Label" type="3">
      <description>Description of the objective of the display set defined by this sequence item.</description>
    </entry>
    <entry group="0072" element="0204" name="&gt;Display Set Presentation Group" type="1">
      <description>Positive integer value that designates this Display Set as part of a specific presentation group. All Display Sets with the same Display Set Presentation Group (0072,0204) value shall be displayed at the same time. The value 1 shall indicate that this Display Set is part of the initial presentation group.Subsequent values incrementing by 1 shall imply successive temporal ordering of display.</description>
    </entry>
    <entry group="0072" element="0032" name="&gt;Image Set Number" type="1">
      <description>Image Set Number (0072,0032) value from a Time Based Image Sets Sequence (0072,0030) Item within the Image Sets Sequence (0072,0020) Item that is selected for display by this Display Set.
Note: Multiple Image Boxes Sequence (0072,0300) Items within a Display Sets Sequence (0072,0200) Item may be used to spread one image set over multiple image boxes with the same Display Set characteristics.</description>
    </entry>
    <entry group="0072" element="0300" name="&gt;Image Boxes Sequence" type="1">
      <description>Sequence that defines the image boxes for this Display Set. Exactly one sequence item shall be present unless Image Box Layout Type (0072,0304) is TILED, in which case one or more items shall be present.</description>
    </entry>
    <entry group="0072" element="0302" name="&gt;&gt;Image Box Number" type="1">
      <description>A monotonically increasing integer that identifies the order of image boxes for scrolling, starting from 1, incrementing by one, unique within a Display Set Sequence Item.</description>
    </entry>
    <entry group="0072" element="0108" name="&gt;&gt;Display Environment Spatial Position" type="1">
      <description>Exactly four unitless floating point values indicating the rectangular coordinate position of the image box within the overall bounding box that encompasses all the display space (across all screens). See C.23.2.1.1.</description>
      <section ref="C.23.2.1.1" name="">For the Display Environment Spatial Position (0072,0108) attribute, the lower left corner of the overall bounding box has Cartesian coordinates of (0.0,0.0). The upper right corner has coordinates of (1.0,1.0). The scale of the box is based on the Number of Vertical Pixels (0072,0104) and Number of Horizontal Pixels (0072,0106), not the physical size of the screens that are part of the workstation. The coordinates of each individual screen’s box are defined in absolute coordinates relative to the (0,0) and (1,1) range of the overall box. Position of a box is given by a (x1,y1), (x2,y2) pair that identifies the upper left corner and lower right corner if the box is rectangular.

Note:  The goal is not absolute position matching of the image boxes rendered on the screens using Hanging Protocol layout information, but that the relative positioning of the image boxes should be consistent between different workstations.
The following figure depicts a 1K x 1K screen positioned to the left of a 2K x 2.5K screen. The Display Environment Spatial Position (0072,0108) of the 1K x 1K screen is (0.0,0.4) (0.33,0.0), and the Display Environment Spatial Position (0072,0108) of the 2K x 2.5K screen is (0.33,1.0) (1.0,0.0).

</section>
    </entry>
    <entry group="0072" element="0304" name="&gt;&gt;Image Box Layout Type" type="1">
      <description>Type of layout of the image box.
All types except for TILED are single rectangles containing a single frame of image pixel data. The types are primarily distinguished by their interaction technique.
Defined Terms:
TILED: a scrollable array of rectangles, each containing a single frame of image pixel data.
STACK: a single rectangle containing a steppable single frame, intended for user-controlled stepping through the image set, usually via continuous device interaction (e.g., mouse scrolling) or by single stepping (mouse or button click).
CINE: a single rectangle, intended for video type play back where the user controls are play sequence, rate of play, and direction.
PROCESSED: intended for interactive 3D visualizations that have custom interfaces.
SINGLE: a single rectangle, intended for images and objects with no defined methods of interaction.
Note: This value may also be used for non-image objects, such as waveforms and SR documents.</description>
    </entry>
    <entry group="0072" element="0306" name="&gt;&gt;Image Box Tile Horizontal Dimension" type="1C">
      <description>Positive integer defining the horizontal Image Box tile dimension; the number of columns.
Required if the value of Image Box Layout Type (0072,0304) is TILED.</description>
    </entry>
    <entry group="0072" element="0308" name="&gt;&gt;Image Box Tile Vertical Dimension" type="1C">
      <description>Positive integer defining the vertical Image Box tile dimension; the number of rows.
Required if the value of Image Box Layout Type (0072,0304) is TILED.</description>
    </entry>
    <entry group="0072" element="0310" name="&gt;&gt;Image Box Scroll Direction" type="1C">
      <description>Enumerated Values:
VERTICAL: scroll images by row
HORIZONTAL: scroll images by column.
Required if the value of Image Box Layout Type (0072,0304) is TILED, and the value of Image Box Tile Horizontal Dimension (0072,0306) or Image Box Tile Vertical Dimension (0072,0308) is greater than 1.</description>
    </entry>
    <entry group="0072" element="0312" name="&gt;&gt;Image Box Small Scroll Type" type="2C">
      <description>Defines the type of small increment scrolling to be applied to this Image Box.
Required if the value of Image Box Layout Type (0072,0304) is TILED, and the value of Image Box Tile Horizontal Dimension (0072,0306) or Image Box Tile Vertical Dimension (0072,0308) is greater than 1. Scrolling is not specified if zero length.
Enumerated Values:
PAGE: In a TILED image box, replace all image slots with the next N x M images in the set,
ROW_COLUMN: in a TILED image box, move each row or column of images to the next row or column, depending on Image Box Scroll Direction (0072,0310)
IMAGE: In a TILED image box, move each image to the next slot, either horizontally or vertically, depending on Image Box Scroll Direction (0072,0310)
Note: If there are multiple image boxes of different Tile Dimensions in a Display Set, then only IMAGE scrolling applies, and the value of this attribute is ignored.</description>
    </entry>
    <entry group="0072" element="0314" name="&gt;&gt;Image Box Small Scroll Amount" type="1C">
      <description>Defines the positive integer number of pages, rows, columns, or images per small increment scroll, based on the values of Image Box Small Scroll Type (0072,0312) and Image Box Scroll Direction (0072,0310). The value applies to both forward and backward scrolling.
Required if Image Box Small Scroll Type (0072,0312) is present with a value.</description>
    </entry>
    <entry group="0072" element="0316" name="&gt;&gt;Image Box Large Scroll Type" type="2C">
      <description>Defines the type of large increment scrolling to be applied to this Image Box.
Required if the value of Image Box Layout Type (0072,0304) is TILED, and the value of Image Box Tile Horizontal Dimension (0072,0306) or Image Box Tile Vertical Dimension (0072,0308) is greater than 1.
Enumerated Values:
PAGE: In a TILED image box, replace all image slots with the next N x M images in the set,
ROW_COLUMN: in a TILED image box, move each row or column of images to the next row or column, depending on Image Box Scroll Direction (0072,0310)
IMAGE: In a TILED image box, move each image to the next slot, either horizontally or vertically, depending on Image Box Scroll Direction (0072,0310)
Note: If there are multiple image boxes of different Tile Dimensions in a Display Set, then only IMAGE scrolling applies, and the value of the attribute is ignored.</description>
    </entry>
    <entry group="0072" element="0318" name="&gt;&gt;Image Box Large Scroll Amount" type="1C">
      <description>Defines the positive integer number of pages, rows, columns, or images per large increment scroll, based on the values of Image Box Large Scroll Type (0072,0316) and Image Box Scroll Direction (0072,cc50). The value applies to both forward and backward scrolling.
Required if Image Box Large Scroll Type (0072,0316) is present with a value.</description>
    </entry>
    <entry group="0072" element="0320" name="&gt;&gt;Image Box Overlap Priority" type="3">
      <description>If this Image Box overlaps in spatial position with others, this attribute indicates the layer of this Image Box in relation to the others. The value shall be a positive integer in the range 1 to 100, where 1 = top and 100 = bottom.
If this attribute is not present, then the expected behavior is not defined.</description>
    </entry>
    <entry group="0018" element="1244" name="&gt;&gt;Preferred Playback Sequencing" type="1C">
      <description>Describes the preferred playback sequencing for the Image Box. Overrides any Preferred Playback Sequencing (0018,1244) value in the image objects being displayed.
Required if the value of Image Box Layout Type (0072,0304) is CINE.
Enumerated Values:
0 = Looping (1,2...n,1,2,...n,1,2,....n,...)
1 = Sweeping (1,2,...n,n-1,...2,1,2,...n,...)
2 = Stop (1,2…n)</description>
    </entry>
    <entry group="0008" element="2144" name="&gt;&gt;Recommended Display Frame Rate" type="1C">
      <description>Recommended rate at which the frames of a multi-frame image shall be displayed, in frames/second. Shall have a value greater than zero. Overrides any Recommended Display Frame Rate (0008,2144) value in the image objects being displayed.
Required if the value of Image Box Layout Type (0072,0304) is CINE and if Cine Relative to Real-Time (0072,0330) is not present.</description>
    </entry>
    <entry group="0072" element="0330" name="&gt;&gt;Cine Relative to Real-Time" type="1C">
      <description>A positive unitless floating point numeric factor equal to playback rate divided by acquisition rate.
Required if the value of Image Box Layout Type (0072,0304) is CINE and if Recommended Display Frame Rate (0008,2144) is not present.
Note: The capture rate may change within the image object, as specified in Frame Time (0018,1063) or Frame Time Vector (0018,1065).</description>
    </entry>
    <entry group="0072" element="0400" name="&gt;Filter Operations Sequence" type="2">
      <description>Sequence that defines filter criteria to be applied to the image set identified by Image Set Number (0072,0032). Zero or more items shall be included in this sequence. See C.23.3.1.1.</description>
      <section ref="C.23.3.1.1" name="">The items in the Filter Operations Sequence (0072,0400) determine which subset of the images in the identified Image Set are to be displayed in the associated Display Set image boxes. If there are multiple Items in the Filter Operations Sequence (0072,0400), the filter operations shall be applied in Item order, and the output of the preceding filter shall serve as the input to the succeeding filter (i.e., an AND operation).
When Filter-by Category (0072,0402) has a value of IMAGE_PLANE, Selector Attribute VR (0072,0050) shall have a value of “CS”, and abstract enumerated values shall be used for the value of the associated Selector CS Value (0072,0062) attribute, which may be computed from the values of Image Orientation (Patient) (0020,0037) or Patient Orientation (0020,0020). Enumerated Values: TRANSVERSE, CORONAL, SAGITTAL, OBLIQUE.
Note:  Cross-sectional images do not normally contain a categorical description of the image plane, but rather only a patient-relative row and column direction cosines that are unit vectors. The category of image plane can be determined first by categorizing the row and column major directions (or detecting if the orientation is oblique according to a pre-specified threshold), and then using those categories to select a plan category.
  The following pseudo-code can be used to determine the major axis (R or L, A or P, H or F) from a single direction cosine that is an (x,y,z) tuple (as defined in C.7.6.2.1.1):

    if (abs(x) &gt; threshold)
      axis = “RL”
    else if (abs(y) &gt; threshold)
      axis = “AP”
    else if (abs(z) &gt; threshold)
      axis = “HF”
    else
      is OBLIQUE

  Having determined the major axis of the row and column, the category of plane can be obtained from a table lookup:

<unrecognized-rows><term value=""/><term value="Row"/><term value="Column"/><term value="RL"/><term value="AP"/><term value="HF"/><term value="RL"/><term value=""/><term value="TRANSVERSE"/><term value="CORONAL"/><term value="AP"/><term value="TRANSVERSE"/><term value=""/><term value="SAGITTAL"/><term value="HF"/><term value="CORONAL"/><term value="SAGITTAL"/><term value=""/></unrecognized-rows>
  Alternatively, one can obtain a single vector that is the normal to the orientation (cross product of the row and column unit vectors), then find which of the x, y and z components has the maximum absolute value that is above threshold; if x then SAGITTAL, if y then CORONAL, if z then TRANSVERSE; if all of the components are below threshold then the orientation is OBLIQUE.

  Since it is also necessary to determine whether or not to flip or rotate the image into the preferred orientation (as specified by Display Set Patient orientation (0072,0700)) for the category of plane (e.g., sagittals are normally viewed with row direction posteriorly and column direction towards the feet), the categorical row and column direction to use can be obtained as above, additional accounting for the sign of the direction cosine, e.g.:

    if x &lt; 0 then orientationX = “R” else orientationX = “L”
    if y &lt; 0 then orientationY = “A” else orientationY = “P”
    if z &lt; 0 then orientationZ = “F” else orientationZ = “H”
    if (abs(x) &gt; threshold)
      orientation = orientationX
    …

An application that is applying a Hanging Protocol Instance shall support any value for Selector Attribute (0072,0026). If the attribute identified by Selector Attribute is not present in an image of the referenced Image Set, then the image is included in the filter output. The attributes of the Hanging Protocol Selector Attribute Context Macro specify whether the Selector Attribute (0072,0026) is contained in a Sequence, Functional Group Sequence, or Private Group.
Notes:  1. The following attributes from image IODs are examples of some possible values for the Selector Attribute (0072,0026) of the Filter Operations Sequence (0072,0400). This is not a complete list:
</section>
    </entry>
    <entry group="0072" element="0402" name="&gt;&gt;Filter-by Category" type="1C">
      <description>Category of the filter operation. See C.23.3.1.1.
Defined terms:
IMAGE_PLANE
Required if Selector Attribute (0072,0026) is not present.</description>
      <section ref="C.23.3.1.1" name="">The items in the Filter Operations Sequence (0072,0400) determine which subset of the images in the identified Image Set are to be displayed in the associated Display Set image boxes. If there are multiple Items in the Filter Operations Sequence (0072,0400), the filter operations shall be applied in Item order, and the output of the preceding filter shall serve as the input to the succeeding filter (i.e., an AND operation).
When Filter-by Category (0072,0402) has a value of IMAGE_PLANE, Selector Attribute VR (0072,0050) shall have a value of “CS”, and abstract enumerated values shall be used for the value of the associated Selector CS Value (0072,0062) attribute, which may be computed from the values of Image Orientation (Patient) (0020,0037) or Patient Orientation (0020,0020). Enumerated Values: TRANSVERSE, CORONAL, SAGITTAL, OBLIQUE.
Note:  Cross-sectional images do not normally contain a categorical description of the image plane, but rather only a patient-relative row and column direction cosines that are unit vectors. The category of image plane can be determined first by categorizing the row and column major directions (or detecting if the orientation is oblique according to a pre-specified threshold), and then using those categories to select a plan category.
  The following pseudo-code can be used to determine the major axis (R or L, A or P, H or F) from a single direction cosine that is an (x,y,z) tuple (as defined in C.7.6.2.1.1):

    if (abs(x) &gt; threshold)
      axis = “RL”
    else if (abs(y) &gt; threshold)
      axis = “AP”
    else if (abs(z) &gt; threshold)
      axis = “HF”
    else
      is OBLIQUE

  Having determined the major axis of the row and column, the category of plane can be obtained from a table lookup:

<unrecognized-rows><term value=""/><term value="Row"/><term value="Column"/><term value="RL"/><term value="AP"/><term value="HF"/><term value="RL"/><term value=""/><term value="TRANSVERSE"/><term value="CORONAL"/><term value="AP"/><term value="TRANSVERSE"/><term value=""/><term value="SAGITTAL"/><term value="HF"/><term value="CORONAL"/><term value="SAGITTAL"/><term value=""/></unrecognized-rows>
  Alternatively, one can obtain a single vector that is the normal to the orientation (cross product of the row and column unit vectors), then find which of the x, y and z components has the maximum absolute value that is above threshold; if x then SAGITTAL, if y then CORONAL, if z then TRANSVERSE; if all of the components are below threshold then the orientation is OBLIQUE.

  Since it is also necessary to determine whether or not to flip or rotate the image into the preferred orientation (as specified by Display Set Patient orientation (0072,0700)) for the category of plane (e.g., sagittals are normally viewed with row direction posteriorly and column direction towards the feet), the categorical row and column direction to use can be obtained as above, additional accounting for the sign of the direction cosine, e.g.:

    if x &lt; 0 then orientationX = “R” else orientationX = “L”
    if y &lt; 0 then orientationY = “A” else orientationY = “P”
    if z &lt; 0 then orientationZ = “F” else orientationZ = “H”
    if (abs(x) &gt; threshold)
      orientation = orientationX
    …

An application that is applying a Hanging Protocol Instance shall support any value for Selector Attribute (0072,0026). If the attribute identified by Selector Attribute is not present in an image of the referenced Image Set, then the image is included in the filter output. The attributes of the Hanging Protocol Selector Attribute Context Macro specify whether the Selector Attribute (0072,0026) is contained in a Sequence, Functional Group Sequence, or Private Group.
Notes:  1. The following attributes from image IODs are examples of some possible values for the Selector Attribute (0072,0026) of the Filter Operations Sequence (0072,0400). This is not a complete list:
</section>
    </entry>
    <entry group="0072" element="0404" name="&gt;&gt;Filter-by Attribute Presence" type="1C">
      <description>Operation to be applied based on the presence or absence of the attribute represented by Selector Attribute (0072,0026) in each image of the Image Set.
Required if Selector Attribute (0072,0026) is present and Filter-by Operator (0072,0406) is not present.
Enumerated Values:
PRESENT: Include the image if the attribute is present
NOT_PRESENT: Include the image if the attribute is not present</description>
    </entry>
    <entry group="0072" element="0026" name="&gt;&gt;Selector Attribute" type="1C">
      <description>Data Element Tag of an Attribute from an Image IOD to use as a filter. See C.23.3.1.1 for potential attributes.
Required if Filter-by Category (0072,0402) is not present.</description>
      <section ref="C.23.3.1.1" name="">The items in the Filter Operations Sequence (0072,0400) determine which subset of the images in the identified Image Set are to be displayed in the associated Display Set image boxes. If there are multiple Items in the Filter Operations Sequence (0072,0400), the filter operations shall be applied in Item order, and the output of the preceding filter shall serve as the input to the succeeding filter (i.e., an AND operation).
When Filter-by Category (0072,0402) has a value of IMAGE_PLANE, Selector Attribute VR (0072,0050) shall have a value of “CS”, and abstract enumerated values shall be used for the value of the associated Selector CS Value (0072,0062) attribute, which may be computed from the values of Image Orientation (Patient) (0020,0037) or Patient Orientation (0020,0020). Enumerated Values: TRANSVERSE, CORONAL, SAGITTAL, OBLIQUE.
Note:  Cross-sectional images do not normally contain a categorical description of the image plane, but rather only a patient-relative row and column direction cosines that are unit vectors. The category of image plane can be determined first by categorizing the row and column major directions (or detecting if the orientation is oblique according to a pre-specified threshold), and then using those categories to select a plan category.
  The following pseudo-code can be used to determine the major axis (R or L, A or P, H or F) from a single direction cosine that is an (x,y,z) tuple (as defined in C.7.6.2.1.1):

    if (abs(x) &gt; threshold)
      axis = “RL”
    else if (abs(y) &gt; threshold)
      axis = “AP”
    else if (abs(z) &gt; threshold)
      axis = “HF”
    else
      is OBLIQUE

  Having determined the major axis of the row and column, the category of plane can be obtained from a table lookup:

<unrecognized-rows><term value=""/><term value="Row"/><term value="Column"/><term value="RL"/><term value="AP"/><term value="HF"/><term value="RL"/><term value=""/><term value="TRANSVERSE"/><term value="CORONAL"/><term value="AP"/><term value="TRANSVERSE"/><term value=""/><term value="SAGITTAL"/><term value="HF"/><term value="CORONAL"/><term value="SAGITTAL"/><term value=""/></unrecognized-rows>
  Alternatively, one can obtain a single vector that is the normal to the orientation (cross product of the row and column unit vectors), then find which of the x, y and z components has the maximum absolute value that is above threshold; if x then SAGITTAL, if y then CORONAL, if z then TRANSVERSE; if all of the components are below threshold then the orientation is OBLIQUE.

  Since it is also necessary to determine whether or not to flip or rotate the image into the preferred orientation (as specified by Display Set Patient orientation (0072,0700)) for the category of plane (e.g., sagittals are normally viewed with row direction posteriorly and column direction towards the feet), the categorical row and column direction to use can be obtained as above, additional accounting for the sign of the direction cosine, e.g.:

    if x &lt; 0 then orientationX = “R” else orientationX = “L”
    if y &lt; 0 then orientationY = “A” else orientationY = “P”
    if z &lt; 0 then orientationZ = “F” else orientationZ = “H”
    if (abs(x) &gt; threshold)
      orientation = orientationX
    …

An application that is applying a Hanging Protocol Instance shall support any value for Selector Attribute (0072,0026). If the attribute identified by Selector Attribute is not present in an image of the referenced Image Set, then the image is included in the filter output. The attributes of the Hanging Protocol Selector Attribute Context Macro specify whether the Selector Attribute (0072,0026) is contained in a Sequence, Functional Group Sequence, or Private Group.
Notes:  1. The following attributes from image IODs are examples of some possible values for the Selector Attribute (0072,0026) of the Filter Operations Sequence (0072,0400). This is not a complete list:
</section>
    </entry>
    <entry group="0072" element="0050" name="&gt;&gt;Selector Attribute VR" type="1C">
      <description>The Value Representation of the Selector Attribute (0072,0026).
Required if Selector Attribute (0072,0026) or Filter-by Category (0072,0402), and Filter-by Operator (0072,0406) are present.</description>
    </entry>
    <include ref="&gt;&gt;Include Hanging Protocol Selector Attribute Context Macro Table C.23.4-1"/>
    <include ref="&gt;&gt;Include Hanging Protocol Selector Attribute Value Macro Table C.23.4-2"/>
    <entry group="0072" element="0028" name="&gt;&gt;Selector Value Number" type="1C">
      <description>Positive integer identifying which value of the attribute identified by Selector Attribute (0072,0026) is to be used for filtering. The value 1 identifies the first value. The value zero identifies any value.
Required if Selector Attribute (0072,0026) and Filter-by Operator (0072,0406) are present.</description>
    </entry>
    <entry group="0072" element="0406" name="&gt;&gt;Filter-by Operator" type="1C">
      <description>Operation to be applied between the value(s) in the Hanging Protocol Selector Attribute Value Macro ("selector"), and the value(s) of the attribute identified by Selector Attribute (0072,0026) in each image of the Image Set. See C.23.3.1.1.
Required if Filter-by Category (0072,0402) is present, or if Selector Attribute (0072,0026) is present and Filter-by Attribute Presence (0072,0404) is not present.
Enumerated Values:
RANGE_INCL: the values lie within the specified range, or are equal to the endpoints; applies only to numeric, date or time Selector Attribute (0072,0026); two values shall be present in the selector, the first of which is less than or equal to the second
RANGE_EXCL: the values lie outside the specified range, and are not equal to the endpoints; applies only to numeric Selector Attribute (0072,0026); two values shall be present in the selector, the first of which is less than or equal to the second
GREATER_OR_EQUAL: applies only to numeric Selector Attribute (0072,0026)
LESS_OR_EQUAL: applies only to numeric Selector Attribute (0072,0026)
GREATER_THAN: applies only to numeric Selector Attribute (0072,0026)
LESS_THAN: applies only to numeric Selector Attribute (0072,0026)
MEMBER_OF: one of the values in the image is present in the values of the selector; if one value is present in each, this is an "equal to" operator
NOT_MEMBER_OF: none of the values in the image is present in the values of the selector; if one value is present in each, this is a "not equal to" operator</description>
      <section ref="C.23.3.1.1" name="">The items in the Filter Operations Sequence (0072,0400) determine which subset of the images in the identified Image Set are to be displayed in the associated Display Set image boxes. If there are multiple Items in the Filter Operations Sequence (0072,0400), the filter operations shall be applied in Item order, and the output of the preceding filter shall serve as the input to the succeeding filter (i.e., an AND operation).
When Filter-by Category (0072,0402) has a value of IMAGE_PLANE, Selector Attribute VR (0072,0050) shall have a value of “CS”, and abstract enumerated values shall be used for the value of the associated Selector CS Value (0072,0062) attribute, which may be computed from the values of Image Orientation (Patient) (0020,0037) or Patient Orientation (0020,0020). Enumerated Values: TRANSVERSE, CORONAL, SAGITTAL, OBLIQUE.
Note:  Cross-sectional images do not normally contain a categorical description of the image plane, but rather only a patient-relative row and column direction cosines that are unit vectors. The category of image plane can be determined first by categorizing the row and column major directions (or detecting if the orientation is oblique according to a pre-specified threshold), and then using those categories to select a plan category.
  The following pseudo-code can be used to determine the major axis (R or L, A or P, H or F) from a single direction cosine that is an (x,y,z) tuple (as defined in C.7.6.2.1.1):

    if (abs(x) &gt; threshold)
      axis = “RL”
    else if (abs(y) &gt; threshold)
      axis = “AP”
    else if (abs(z) &gt; threshold)
      axis = “HF”
    else
      is OBLIQUE

  Having determined the major axis of the row and column, the category of plane can be obtained from a table lookup:

<unrecognized-rows><term value=""/><term value="Row"/><term value="Column"/><term value="RL"/><term value="AP"/><term value="HF"/><term value="RL"/><term value=""/><term value="TRANSVERSE"/><term value="CORONAL"/><term value="AP"/><term value="TRANSVERSE"/><term value=""/><term value="SAGITTAL"/><term value="HF"/><term value="CORONAL"/><term value="SAGITTAL"/><term value=""/></unrecognized-rows>
  Alternatively, one can obtain a single vector that is the normal to the orientation (cross product of the row and column unit vectors), then find which of the x, y and z components has the maximum absolute value that is above threshold; if x then SAGITTAL, if y then CORONAL, if z then TRANSVERSE; if all of the components are below threshold then the orientation is OBLIQUE.

  Since it is also necessary to determine whether or not to flip or rotate the image into the preferred orientation (as specified by Display Set Patient orientation (0072,0700)) for the category of plane (e.g., sagittals are normally viewed with row direction posteriorly and column direction towards the feet), the categorical row and column direction to use can be obtained as above, additional accounting for the sign of the direction cosine, e.g.:

    if x &lt; 0 then orientationX = “R” else orientationX = “L”
    if y &lt; 0 then orientationY = “A” else orientationY = “P”
    if z &lt; 0 then orientationZ = “F” else orientationZ = “H”
    if (abs(x) &gt; threshold)
      orientation = orientationX
    …

An application that is applying a Hanging Protocol Instance shall support any value for Selector Attribute (0072,0026). If the attribute identified by Selector Attribute is not present in an image of the referenced Image Set, then the image is included in the filter output. The attributes of the Hanging Protocol Selector Attribute Context Macro specify whether the Selector Attribute (0072,0026) is contained in a Sequence, Functional Group Sequence, or Private Group.
Notes:  1. The following attributes from image IODs are examples of some possible values for the Selector Attribute (0072,0026) of the Filter Operations Sequence (0072,0400). This is not a complete list:
</section>
    </entry>
    <entry group="0072" element="0600" name="&gt;Sorting Operations Sequence" type="2">
      <description>Sequence that defines sorting criteria to be applied to the result of filter and reformat operations, to define the order in which to present the images in the Image Boxes. Zero or more items shall be included in this sequence. See C.23.3.1.2.</description>
      <section ref="C.23.3.1.2" name="">The Items in the Sorting Operations Sequence (0072,0600) define the order in which the images resulting from the filter and reformat operations on the Image Set are to be displayed in the associated Image Boxes of the Display Set. The sorting criteria may include the value of a numeric, date, or time Attribute that is expected to be present in each of the image objects in the filtered Image Set, and/or an abstract sorting category. A sorting direction shall be associated with each sorting criterion. If a textual Attribute is used for sorting, then the INCREASING sorting direction indicates alpabetical order, and DECREASING indicates reverse alphabetical order.
If a code sequence Attribute is used for sorting, then the Code Meaning (0008,0104) shall be sorted alphabetically. If a string numeric Attribute is used for sorting (VR of IS or DS), then sorting shall be on the numeric value, and padding shall be ignored. When sorting by date or time Attribute, then sorting shall be on the temporal value, not the alphabetic string.
If there are multiple Items in the Sorting Operations Sequence (0072,0600), then the sorting operations shall be applied in Item order. The least rapidly varying attribute for the sorting operation shall be the first Item in the sequence.
Note:  For example, a Sorting Operations Sequence (0072,0600) with two Items:
    Item #1: (0018,5101) View Position, INCREASING
    Item #2: (0008,0020) Study Date, INCREASING
  results in the following order, based on these attribute values in the image objects:
<unrecognized-rows><term value="View Position (0018,5101)" meaning="Study Date (0008,0020)"/><term value="AP" meaning="20030201"/><term value="AP" meaning="20030501"/><term value="LL" meaning="20020705"/><term value="LL" meaning="20030102"/><term value="RL" meaning="20030101"/><term value="RL" meaning="20030201"/></unrecognized-rows>
When the Sort-by Category (0072,0602) is used with a value of ALONG_AXIS, such as for CT, MR or other cross-sectional image sets, the sorting operation is computed from the values Image Position (Patient) (0020,0032) and Image Orientation (Patient) (0020,0037) in the image objects.
For the image set to be displayed, a “dominant axis” of the set shall be determined. The dominant axis is the normal to the Image Orientation (Patient) (0020,0037) attribute (assuming all selected images are parallel), computed as the dot product in a right-handed coordinate system (see C.7.6.2.1.1). The INCREASING direction for ALONG_AXIS of the image set shall be in the positive direction along the dominant axis. The DECREASING direction shall be in the negative direction along that axis.
When the Sort-by Category (0072,0602) is used with a value of BY_ACQ_TIME, the sorting operation is computed from appropriate values in the image objects (e.g., Frame Acquisition DateTime, Acquisition Time, Content Time, Acquisition DateTime), since the specific attribute used may vary from one Image Instance or SOP Class to another, yet the Hanging Protocol Instance may be generally applicable.
An application that is applying a Hanging Protocol Instance shall support any value for Selector Attribute (0072,0026), provided that it is present in the referenced Image Set. The attributes of the Hanging Protocol Selector Attribute Context Macro specify whether the Selector Attribute (0072,0026) is contained in a Sequence, Functional Group Sequence or Private Group.
Notes:  1. The following attributes from image IODs are examples of some possible values for the Selector Attribute (0072,0026) of the Sorting Operations Sequence (0072,0600). This is not a complete list:
</section>
    </entry>
    <entry group="0072" element="0026" name="&gt;&gt;Selector Attribute" type="1C">
      <description>Data Element Tag of an Attribute from an Image IOD to be used for sorting. See C.23.3.1.2 for potential attributes.
Required if Sort-by Category (0072,0602) is not present.</description>
      <section ref="C.23.3.1.2" name="">The Items in the Sorting Operations Sequence (0072,0600) define the order in which the images resulting from the filter and reformat operations on the Image Set are to be displayed in the associated Image Boxes of the Display Set. The sorting criteria may include the value of a numeric, date, or time Attribute that is expected to be present in each of the image objects in the filtered Image Set, and/or an abstract sorting category. A sorting direction shall be associated with each sorting criterion. If a textual Attribute is used for sorting, then the INCREASING sorting direction indicates alpabetical order, and DECREASING indicates reverse alphabetical order.
If a code sequence Attribute is used for sorting, then the Code Meaning (0008,0104) shall be sorted alphabetically. If a string numeric Attribute is used for sorting (VR of IS or DS), then sorting shall be on the numeric value, and padding shall be ignored. When sorting by date or time Attribute, then sorting shall be on the temporal value, not the alphabetic string.
If there are multiple Items in the Sorting Operations Sequence (0072,0600), then the sorting operations shall be applied in Item order. The least rapidly varying attribute for the sorting operation shall be the first Item in the sequence.
Note:  For example, a Sorting Operations Sequence (0072,0600) with two Items:
    Item #1: (0018,5101) View Position, INCREASING
    Item #2: (0008,0020) Study Date, INCREASING
  results in the following order, based on these attribute values in the image objects:
<unrecognized-rows><term value="View Position (0018,5101)" meaning="Study Date (0008,0020)"/><term value="AP" meaning="20030201"/><term value="AP" meaning="20030501"/><term value="LL" meaning="20020705"/><term value="LL" meaning="20030102"/><term value="RL" meaning="20030101"/><term value="RL" meaning="20030201"/></unrecognized-rows>
When the Sort-by Category (0072,0602) is used with a value of ALONG_AXIS, such as for CT, MR or other cross-sectional image sets, the sorting operation is computed from the values Image Position (Patient) (0020,0032) and Image Orientation (Patient) (0020,0037) in the image objects.
For the image set to be displayed, a “dominant axis” of the set shall be determined. The dominant axis is the normal to the Image Orientation (Patient) (0020,0037) attribute (assuming all selected images are parallel), computed as the dot product in a right-handed coordinate system (see C.7.6.2.1.1). The INCREASING direction for ALONG_AXIS of the image set shall be in the positive direction along the dominant axis. The DECREASING direction shall be in the negative direction along that axis.
When the Sort-by Category (0072,0602) is used with a value of BY_ACQ_TIME, the sorting operation is computed from appropriate values in the image objects (e.g., Frame Acquisition DateTime, Acquisition Time, Content Time, Acquisition DateTime), since the specific attribute used may vary from one Image Instance or SOP Class to another, yet the Hanging Protocol Instance may be generally applicable.
An application that is applying a Hanging Protocol Instance shall support any value for Selector Attribute (0072,0026), provided that it is present in the referenced Image Set. The attributes of the Hanging Protocol Selector Attribute Context Macro specify whether the Selector Attribute (0072,0026) is contained in a Sequence, Functional Group Sequence or Private Group.
Notes:  1. The following attributes from image IODs are examples of some possible values for the Selector Attribute (0072,0026) of the Sorting Operations Sequence (0072,0600). This is not a complete list:
</section>
    </entry>
    <include ref="&gt;&gt;Include Hanging Protocol Selector Attribute Context Macro Table C.23.4-1"/>
    <entry group="0072" element="0028" name="&gt;&gt;Selector Value Number" type="1C">
      <description>Positive integer identifying which value of the attribute identified by Selector Attribute (0072,0026) is to be used for sorting. The value of 1 identifies the first value. Shall not be zero.
Required if Selector Attribute (0072,0026) is present.</description>
    </entry>
    <entry group="0072" element="0602" name="&gt;&gt;Sort-by Category" type="1C">
      <description>Category of the sorting operation. See C.23.3.1.2.
Defined terms:
ALONG_AXIS: for CT, MR, other cross-sectional image sets
BY_ACQ_TIME
Required if Selector Attribute (0072,0026) is not present.</description>
      <section ref="C.23.3.1.2" name="">The Items in the Sorting Operations Sequence (0072,0600) define the order in which the images resulting from the filter and reformat operations on the Image Set are to be displayed in the associated Image Boxes of the Display Set. The sorting criteria may include the value of a numeric, date, or time Attribute that is expected to be present in each of the image objects in the filtered Image Set, and/or an abstract sorting category. A sorting direction shall be associated with each sorting criterion. If a textual Attribute is used for sorting, then the INCREASING sorting direction indicates alpabetical order, and DECREASING indicates reverse alphabetical order.
If a code sequence Attribute is used for sorting, then the Code Meaning (0008,0104) shall be sorted alphabetically. If a string numeric Attribute is used for sorting (VR of IS or DS), then sorting shall be on the numeric value, and padding shall be ignored. When sorting by date or time Attribute, then sorting shall be on the temporal value, not the alphabetic string.
If there are multiple Items in the Sorting Operations Sequence (0072,0600), then the sorting operations shall be applied in Item order. The least rapidly varying attribute for the sorting operation shall be the first Item in the sequence.
Note:  For example, a Sorting Operations Sequence (0072,0600) with two Items:
    Item #1: (0018,5101) View Position, INCREASING
    Item #2: (0008,0020) Study Date, INCREASING
  results in the following order, based on these attribute values in the image objects:
<unrecognized-rows><term value="View Position (0018,5101)" meaning="Study Date (0008,0020)"/><term value="AP" meaning="20030201"/><term value="AP" meaning="20030501"/><term value="LL" meaning="20020705"/><term value="LL" meaning="20030102"/><term value="RL" meaning="20030101"/><term value="RL" meaning="20030201"/></unrecognized-rows>
When the Sort-by Category (0072,0602) is used with a value of ALONG_AXIS, such as for CT, MR or other cross-sectional image sets, the sorting operation is computed from the values Image Position (Patient) (0020,0032) and Image Orientation (Patient) (0020,0037) in the image objects.
For the image set to be displayed, a “dominant axis” of the set shall be determined. The dominant axis is the normal to the Image Orientation (Patient) (0020,0037) attribute (assuming all selected images are parallel), computed as the dot product in a right-handed coordinate system (see C.7.6.2.1.1). The INCREASING direction for ALONG_AXIS of the image set shall be in the positive direction along the dominant axis. The DECREASING direction shall be in the negative direction along that axis.
When the Sort-by Category (0072,0602) is used with a value of BY_ACQ_TIME, the sorting operation is computed from appropriate values in the image objects (e.g., Frame Acquisition DateTime, Acquisition Time, Content Time, Acquisition DateTime), since the specific attribute used may vary from one Image Instance or SOP Class to another, yet the Hanging Protocol Instance may be generally applicable.
An application that is applying a Hanging Protocol Instance shall support any value for Selector Attribute (0072,0026), provided that it is present in the referenced Image Set. The attributes of the Hanging Protocol Selector Attribute Context Macro specify whether the Selector Attribute (0072,0026) is contained in a Sequence, Functional Group Sequence or Private Group.
Notes:  1. The following attributes from image IODs are examples of some possible values for the Selector Attribute (0072,0026) of the Sorting Operations Sequence (0072,0600). This is not a complete list:
</section>
    </entry>
    <entry group="0072" element="0604" name="&gt;&gt;Sorting Direction" type="1">
      <description>Sorting direction to be applied to the value(s) in the image set of the attribute identified by Selector Attribute (0072,0026) or Sort-by Category (0072,0602).
Enumerated Values: INCREASING, DECREASING</description>
    </entry>
    <entry group="0072" element="0500" name="&gt;Blending Operation Type" type="3">
      <description>Type of blending of superimposed and underlying images from the image set, performed before reformatting. See C.23.3.1.3.
Defined Terms:
COLOR - apply a pseudo-color to the superimposed image while blending</description>
      <section ref="C.23.3.1.3" name="">A Blending Operation Type (0072,0500) of COLOR implies that the filtered selected image set contains two sets of images appropriate for blending, such as CT and PET images defined in the same frame of reference or associated by a spatial registration object. The decision as to which subset are the underlying images and which subset are the superimposed images is left to the discretion of the display application. There is no mechanism to explicitly specify the two subsets.
The relative opacity and color-related aspects of blending are not specified by the Hanging Protocol, and are left to the discretion of the application.
</section>
    </entry>
    <entry group="0072" element="0510" name="&gt;Reformatting Operation Type" type="3">
      <description>Reformatting operation to be applied to the Image Set.
Defined terms: MPR, 3D_RENDERING, SLAB</description>
    </entry>
    <entry group="0072" element="0512" name="&gt;Reformatting Thickness" type="1C">
      <description>The desired thickness of the reformatted images in millimeters.
Required if value of Reformatting Operation Type (0072,0510) is SLAB or MPR. May be present otherwise.</description>
    </entry>
    <entry group="0072" element="0514" name="&gt;Reformatting Interval" type="1C">
      <description>The desired spacing of the reformatted images in millimeters. The spacing is measured from the center-to-center of each reconstructed image.
Required if value of Reformatting Operation Type (0072,0510) is SLAB or MPR. May be present otherwise.</description>
    </entry>
    <entry group="0072" element="0516" name="&gt;Reformatting Operation Initial View Direction" type="1C">
      <description>Initial view of the reformatted images.
Required if the value of Reformatting Operation Type (0072,0510) is MPR or 3D_RENDERING. May be present otherwise.
Defined Terms:
SAGITTAL, TRANSVERSE, CORONAL, OBLIQUE</description>
    </entry>
    <entry group="0072" element="0520" name="&gt;3D Rendering Type" type="1C">
      <description>Describes the intended 3D rendering type. One or more values shall be present. The first value shall not be zero length. Required if the value of Reformatting Operation Type (0072,0510) is 3D_RENDERING:
Defined Terms for value 1:
MIP, SURFACE, VOLUME
Additional values may be used to identify implementation specific sub-types.</description>
    </entry>
    <entry group="0072" element="0700" name="&gt;Display Set Patient Orientation" type="3">
      <description>Patient direction of the rows and columns of the images, as intended for display. See C.23.3.1.4.</description>
      <section ref="C.23.3.1.4" name="">The attributes that indicate the presentation intent for each Display Set of a Hanging Protocol Instance are: Display Set Patient Orientation (0072,0700), VOI Type (0072,0702), Pseudo-color Type (0072,0704), Show Grayscale Inverted (0072,0706), Show Image True Size Flag (0072,0710), Show Graphic Annotation Flag (0072,0712), Show Patient Demographics Flag (0072,0714), and Show Acquisition Techniques Flag (0072,0716).
</section>
    </entry>
    <entry group="0072" element="0717" name="&gt;Display Set Horizontal Justification" type="3">
      <description>Indicates direction in which to horizontally justify the image within a viewport that is not the same shape (aspect ratio) as the image.
Enumerated Values:
LEFT
CENTER
RIGHT
Note: Typically used in mammography display applications in which images from the patient's left and right are displayed "back to back", rather than centered.</description>
    </entry>
    <entry group="0072" element="0718" name="&gt;Display Set Vertical Justification" type="3">
      <description>Indicates direction in which to vertically justify the image within a viewport that is not the same shape (aspect ratio) as the image.
Enumerated Values:
TOP
CENTER
BOTTOM</description>
    </entry>
    <entry group="0072" element="0702" name="&gt;VOI Type" type="3">
      <description>Expected value of interest transformation for display (e.g., Window Center and Window Width or VOI LUT).
Defined Terms:
LUNG
MEDIASTINUM
ABDO_PELVIS
LIVER
SOFT_TISSUE
BONE
BRAIN
POST_FOSSA</description>
    </entry>
    <entry group="0072" element="0704" name="&gt;Pseudo-color Type" type="3">
      <description>A category of pseudo-color palette choice to be applied after application of the VOI LUT. If this attribute is not present, a pseudo-color palette shall not be applied.
Defined Terms:
BLACK_BODY
HOT_IRON
DEFAULT</description>
    </entry>
    <entry group="0072" element="0706" name="&gt;Show Grayscale Inverted" type="3">
      <description>Whether or not to invert the rendered luminance of the displayed values. See C.23.3.1.4.
Enumerated values:
YES = The maximum output value after the display pipeline has been applied shall be displayed with the minimum available luminance.
NO = The maximum output value after the display pipeline has been applied shall be displayed with the maximum available luminance.
Notes: 1. The YES and NO values of this Attribute correspond to the Presentation LUT Shape (2050,0020) values of INVERSE and IDENTITY, as described in C.11.6.1.2.
2. Only applicable to display of grayscale images.</description>
      <section ref="C.23.3.1.4" name="">The attributes that indicate the presentation intent for each Display Set of a Hanging Protocol Instance are: Display Set Patient Orientation (0072,0700), VOI Type (0072,0702), Pseudo-color Type (0072,0704), Show Grayscale Inverted (0072,0706), Show Image True Size Flag (0072,0710), Show Graphic Annotation Flag (0072,0712), Show Patient Demographics Flag (0072,0714), and Show Acquisition Techniques Flag (0072,0716).
</section>
    </entry>
    <entry group="0072" element="0710" name="&gt;Show Image True Size Flag" type="3">
      <description>Indicates whether or not to display images with the physical size of the rendered image pixel the same on the screen as specified in the image attributes, unless overridden by a Presentation State instance.
Enumerated values:
YES = Display images at True Size.
NO = The rendered size is not specified.</description>
    </entry>
    <entry group="0072" element="0712" name="&gt;Show Graphic Annotation Flag" type="3">
      <description>Indicates whether or not to display items from the Graphic Annotation Sequence (0070,0001) in an applied Presentation State, and the attributes of the Overlay Plane module in the image objects or applied Presentation State.
Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="0072" element="0714" name="&gt;Show Patient Demographics Flag" type="3">
      <description>Indicates whether or not to display patient and study identification information.
Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="0072" element="0716" name="&gt;Show Acquisition Techniques Flag" type="3">
      <description>Indicates whether or not to display image acquisition technique information.
Enumerated Values:
YES
NO</description>
    </entry>
    <entry group="0072" element="0206" name="&gt;Display Set Presentation Group Description" type="3">
      <description>Description of the intent of the Display Set Presentation Group (0072,0204). If present, shall have the same value in all sequence Items assigned the same value for Display Set Presentation Group (0072,0204).</description>
    </entry>
    <entry group="0072" element="0208" name="Partial Data Display Handling" type="2">
      <description>If one or more Image Sets identified by Image Set Number (0072,0032) in the Display Sets Sequence (0072,0200) Items is not available, indicate whether or not to maintain the expected layout in the absence of complete Image Sets. Enumerated Values:
MAINTAIN_LAYOUT: If one or more Image Sets is not available, maintain the layout with empty Image Boxes.
ADAPT_LAYOUT: If one or more Image Sets is not available, rearrange the layout at the discretion of the application.
If this attribute is zero length, then the expected behavior is not defined.</description>
    </entry>
    <entry group="0072" element="0210" name="Synchronized Scrolling Sequence" type="3">
      <description>Each sequence item of this attribute identifies a group of Display Sets to which synchronized scrolling is to be applied. Zero or more sequence items may be present.
The dimensions along which the synchronization occurs shall be those specified in the Sorting Operations Sequence (0072,0600).</description>
    </entry>
    <entry group="0072" element="0212" name="&gt;Display Set Scrolling Group" type="1">
      <description>Multi-valued list of two or more Display Set Number (0072,0202) values. Indicates that the images within the specified Display Sets are scrolled in parallel, to maintain the established synchronization.</description>
    </entry>
    <entry group="0072" element="0214" name="Navigation Indicator Sequence" type="3">
      <description>Describes a geometric relationship between Display Sets for the purpose of static or interactive localization or navigation. One or more sequence items may be present.</description>
    </entry>
    <entry group="0072" element="0216" name="&gt;Navigation Display Set" type="1C">
      <description>Display Set Number (0072,0202) of the Display Set where the geometric relationship to the Reference Display Sets (0072,0218) is graphically depicted.
Required if there is a one-way interaction such that the location of the Reference Display Sets is indicated on or controlled by the Navigation Display Set.
Note: For example, the graphical representation may indicate either the number of slices displayed or contained in the Reference Display Set(s).</description>
    </entry>
    <entry group="0072" element="0218" name="&gt;Reference Display Sets" type="1">
      <description>One or more Display Set Number (0072,0202) values.
If Navigation Display Set is present, shall list those Display Sets that are controlled by or indicated on the Navigation Display Set.
If Navigation Display Set is absent, shall indicate that all of the Reference Display Sets cross-reference each other.</description>
    </entry>
  </module>
  <module ref="C.24.1" table="C.24-1" name="Encapsulated Document Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>The modality appropriate for the encapsulated document.
This Type definition shall override the definition in the SC Equipment Module.
See section C.7.3.1.1.1 for Defined Terms.
Note: SR may be an appropriate value for an Encapsulated CDA document with a structured XML Body.</description>
    </entry>
    <entry group="0020" element="000E" name="Series Instance UID" type="1">
      <description>Unique identifier of the Series.
</description>
    </entry>
    <entry group="0020" element="0011" name="Series Number" type="1">
      <description>A number that identifies the Series.</description>
    </entry>
    <entry group="0008" element="1111" name="Referenced Performed Procedure Step Sequence" type="3">
      <description>Uniquely identifies the Performed Procedure Step SOP Instance for which the Series is created. Only a single Item shall be permitted in this sequence.
Note: The Performed Procedure Step referred to by this Attribute is the Step during which this Document is generated.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0008" element="103E" name="Series Description" type="3">
      <description>User provided description of the Series</description>
    </entry>
    <entry group="0040" element="0275" name="Request Attributes Sequence" type="3">
      <description>Sequence that contains attributes from the Imaging Service Request.
The sequence may have one or more Items.</description>
    </entry>
    <include ref="&gt;Include Request Attributes Macro Table 10-9" description="No Baseline Context IDs defined"/>
    <include ref="Include Performed Procedure Step Summary Macro Table 10-16" description="No Baseline Context IDs defined"/>
  </module>
  <module ref="C.24.2" table="C.24-2" name="Encapsulated Document Module Attributes">
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description>A number that identifies this SOP Instance. The value shall be unique within a series.</description>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="2">
      <description>The date the document content creation was started.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="2">
      <description>The time the document content creation was started.</description>
    </entry>
    <entry group="0008" element="002A" name="Acquisition DateTime" type="2">
      <description>The date and time that the original generation of the data in the document started.</description>
    </entry>
    <entry group="0028" element="0301" name="Burned In Annotation" type="1">
      <description>Indicates whether or not the encapsulated document contains sufficient burned in annotation to identify the patient and date the data was acquired.
Enumerated Values:
YES
NO
Identification of patient and date as text in an encapsulated document (e.g., in an XML attribute or element) is equivalent to "burned in annotation". A de-identified document may use the value NO.</description>
    </entry>
    <entry group="0042" element="0013" name="Source Instance Sequence" type="1C">
      <description>A sequence that identifies the set of Instances that were used to derive the encapsulated document. One or more Items may be included in this Sequence.
Required if derived from one or more DICOM Instances. May be present otherwise.</description>
    </entry>
    <include ref="&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0042" element="0010" name="Document Title" type="2">
      <description>The title of the document.
Note: In the case of a PDF encapsulated document, this may be the value of the "Title" entry in the "Document Information Directory" as encoded in the PDF data.</description>
    </entry>
    <entry group="0040" element="A043" name="Concept Name Code Sequence" type="2">
      <description>A coded representation of the document title. Zero or one item may be present.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="Baseline Context Group 7020"/>
    <entry group="0040" element="A493" name="Verification Flag" type="3">
      <description>Indicates whether the Encapsulated Document is Verified. Enumerated Values:
UNVERIFIED = Not attested by a legally accountable person.
VERIFIED = Attested to (signed) by a Verifying Observer or Legal Authenticator named in the document, who is accountable for its content.</description>
    </entry>
    <entry group="0040" element="E001" name="HL7 Instance Identifier" type="1C">
      <description>Instance Identifier of the encapsulated HL7 Structured Document, encoded as a UID (OID or UUID), concatenated with a caret ("^") and Extension value (if Extension is present in Instance Identifier).
Required if encapsulated document is a CDA document.</description>
    </entry>
    <entry group="0042" element="0012" name="MIME Type of Encapsulated Document" type="1">
      <description>The type of the encapsulated document stream described using the MIME Media Type (see RFC 2046).</description>
    </entry>
    <entry group="0042" element="0014" name="List of MIME Types" type="1C">
      <description>MIME Types of subcomponents of the encapsulated document.
Required if the encapsulated document incorporates subcomponents with MIME types different than the primary MIME Type of the encapsulated document.
Note: An Encapsulated CDA that includes an embedded JPEG image and an embedded PDF would list "image/jpeg\application/pdf".</description>
    </entry>
    <entry group="0042" element="0011" name="Encapsulated Document" type="1">
      <description>Encapsulated Document stream, containing a document encoded according to the MIME Type.</description>
    </entry>
  </module>
  <module ref="C.25.1" table="C.25.1-1" name="Real World Value Mapping Series Module Attributes">
    <entry group="0008" element="0060" name="Modality" type="1">
      <description>Modality type.
Enumerated Value:
RWV</description>
    </entry>
  </module>
  <module ref="C.25.2" table="C.25.2-1" name="Real World Value Mapping Module Attributes">
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the content creation started.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the content creation started.</description>
    </entry>
    <include ref="Include Content Identification Macro Table 10-12"/>
    <entry group="0040" element="9094" name="Referenced Image Real World Value Mapping Sequence" type="1">
      <description>A sequence of one or more real world value mapping items. Each item defines a single mapping and a list of images to which the mapping applies.</description>
    </entry>
    <include ref="&gt;Include Real World Value Mapping Macro Table C.7.6.16-12, overriding the Defined Context ID for Measurement Units Code Sequence with DCID 83."/>
    <entry group="0008" element="1140" name="&gt;Referenced Image Sequence" type="1">
      <description>A sequence listing the images to which the mapping applies. One or more items shall be present.</description>
    </entry>
    <include ref="&gt;&gt;Include 'Image SOP Instance Reference Macro' Table 10-3"/>
  </module>
  <module ref="C.26.1" table="C.26-1" name="Product Characteristics Module Attributes">
    <entry group="0044" element="0001" name="Product Package Identifier">
      <description>Identifier of the contrast agent, drug, or device being characterized, typically from a package bar code, RFID, or other materials management ID. This ID might not be globally unique and might conflict with other IDs used within the scope of the institution.</description>
    </entry>
    <entry group="0008" element="0070" name="Manufacturer">
      <description>Manufacturer of product.</description>
    </entry>
    <entry group="0044" element="0007" name="Product Type Code Sequence">
      <description>Coded type of product. One Item shall be included in the Sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="For drugs, a coded terminology in the US is RxNormFor devices, a coded terminology in the US is the FDA CDRH Product Code Classification"/>
    <entry group="0044" element="0008" name="Product Name">
      <description>Trade or generic name of product.
Note: May be multi-valued.</description>
    </entry>
    <entry group="0044" element="0009" name="Product Description">
      <description>Further description in free form text describing the drug or device.
Note: This attribute is limited by the LT Value Representation to 10240 characters. Larger text descriptions, or graphical descriptions, may be referenced in the Pertinent Documents Sequence (0038,0100).</description>
    </entry>
    <entry group="0044" element="000A" name="Product Lot Identifier">
      <description>Identifier of the manufacturing batch of which this product is part.</description>
    </entry>
    <entry group="0044" element="000B" name="Product Expiration DateTime">
      <description>The date and time after which the manufacturer no longer ensures the safety, quality, and/or proper functioning of the material.</description>
    </entry>
    <entry group="0044" element="0013" name="Product Parameter Sequence">
      <description>Parameters of the product. Zero or more Items may be included in the Sequence.</description>
    </entry>
    <include ref="&gt;Include Content Item Macro Table 10.2-1" description="For drugs or contrast agents, Baseline Context Group for Concept Name Code Sequence is 4050 For devices, Baseline Context Group for Concept Name Code Sequence is 3423"/>
    <entry group="0038" element="0100" name="Pertinent Documents Sequence">
      <description>Reference to a Product Label document for the product. Zero or more Items may be included in this sequence.</description>
    </entry>
    <entry group="0008" element="1150" name="&gt;Referenced SOP Class UID">
      <description>Unique identifier for the class of an HL7 Structured Product Label document.</description>
    </entry>
    <entry group="0008" element="1155" name="&gt;Referenced SOP Instance UID">
      <description>Unique identifier for the HL7 Structured Product Label Document as used in DICOM instance references (see C.12.1.1.6)</description>
    </entry>
    <entry group="0040" element="E001" name="&gt;HL7 Instance Identifier">
      <description>Instance Identifier of the referenced HL7 Structured Document, encoded as a UID (OID or UUID), concatenated with a caret ("^") and Extension value (if Extension is present in Instance Identifier).</description>
    </entry>
    <entry group="0040" element="E010" name="&gt;Retrieve URI">
      <description>Retrieval access path to Product Label Document. Includes fully specified scheme, authority, path, and query in accordance with RFC 2396</description>
    </entry>
  </module>
  <module ref="C.26.2" table="C.26-2" name="Substance Approval Module Attributes">
    <entry group="0044" element="0002" name="Substance Administration Approval">
      <description>Status of request for substance administration. Enumerated Values:
APPROVED - Use of the substance for the patient is approved, with related notes (e.g., appropriate dose for age/weight) in Approval Status Further Description (0044,0003)
WARNING - The substance may be used for the patient subject to warnings described in Approval Status Further Description (0044,0003)
CONTRA_INDICATED - The substance should not be used for the patient for the reasons described in Approval Status Further Description (0044,0003)</description>
    </entry>
    <entry group="0044" element="0003" name="Approval Status Further Description">
      <description>Description of warning or contra-indication, or notes on approval.</description>
    </entry>
    <entry group="0044" element="0004" name="Approval Status DateTime">
      <description>Timestamp for the Substance Administration Approval response</description>
    </entry>
  </module>
  <module ref="C.26.3" table="C.26-3" name="Substance Administration Module Attributes">
    <entry group="0054" element="0302" name="Administration Route Code Sequence">
      <description>Route of administration for drug or contrast. One Item may be present in this Sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="Baseline Context Group 11."/>
  </module>
  <module ref="C.26.4" table="C.26-4" name="Substance Administration Log Module Attributes">
    <entry group="0010" element="0010" name="Patient's Name">
      <description>Patient's full name</description>
    </entry>
    <entry group="0010" element="0020" name="Patient ID">
      <description>Primary identification number or code for the patient.</description>
    </entry>
    <entry group="0010" element="0021" name="Issuer of Patient ID">
      <description>Identifier of the Assigning Authority (system, organization, agency, or department) that issued the Patient ID.</description>
    </entry>
    <entry group="0038" element="0010" name="Admission ID">
      <description>Identification number of the visit as assigned by the healthcare provider</description>
    </entry>
    <entry group="0038" element="0011" name="Issuer of Admission ID">
      <description>Name of healthcare provider that issued the Admission ID</description>
    </entry>
    <entry group="0044" element="0001" name="Product Package Identifier">
      <description>Identifier of the contrast agent, drug, or device administered, typically from a package bar code, RFID, or other materials management ID. This ID might not be globally unique and might conflict with other IDs used within the scope of the institution.</description>
    </entry>
    <entry group="0044" element="0008" name="Product Name">
      <description>Trade or generic name of product.
Note: May be multi-valued.</description>
    </entry>
    <entry group="0044" element="0009" name="Product Description">
      <description>Text description of the contrast agent, drug, or device administered.</description>
    </entry>
    <entry group="0044" element="0010" name="Substance Administration DateTime">
      <description>Date and Time of Substance Administration</description>
    </entry>
    <entry group="0044" element="0011" name="Substance Administration Notes">
      <description>Comments provided by the operator responsible for the substance administration.</description>
    </entry>
    <entry group="0044" element="0012" name="Substance Administration Device ID">
      <description>Identifier for a device that controls substance administration, e.g., injector, infusion pump, etc.</description>
    </entry>
    <entry group="0054" element="0302" name="Administration Route Code Sequence">
      <description>Route of administration for drug or contrast. One Item may be present in this Sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1" description="Baseline Context Group 11."/>
    <entry group="0044" element="0019" name="Substance Administration Parameter Sequence">
      <description>Parameters of the substance as administered to the patient, e.g., volume, quantity. Zero or more Items may be included in the Sequence.</description>
    </entry>
    <include ref="&gt;Include Content Item Macro Table 10.2-1" description="For administration of drugs or contrast agents, Baseline Context Group for Concept Name Code Sequence is 3410."/>
    <entry group="0008" element="1072" name="Operator Identification Sequence">
      <description>Person administering the substance to the patient, or legally responsible for the administration, and authorized to add an entry to the Medication Administration Record. One or more Items may be present in this Sequence.</description>
    </entry>
    <entry group="0040" element="1101" name="&gt;Person Identification Code Sequence">
      <description>Coded identifier of the person administering the contrast agent, drug, or device.
One Item may be present in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1" description="No baseline context ID. The Coding Scheme Designator attribute may indicate a local coding scheme (e.g., with value “L”) when it is implicitly that of the institution’s employee identifier system.The Code Meaning attribute, though it is encoded with a VR of LO, may be encoded according to the rules of the PN VR (see Section 10.1)."/>
  </module>
  <iod table="F.3-1" name="Basic Directory IOD Modules">
    <entry ie="File-set Identification" ref="F.3.2.1" usage="M" name="File-set identification information"/>
    <entry ie="Directory Information" ref="F.3.2.2" usage="U" name="Directory Information followed by a Sequence of Directory Records. Note: The Directory Information Module is optional. This Directory Information Module should be present in all but primitive environments where a directory is not needed. In this case, only the File-set Identification Information is present."/>
  </iod>
  <module ref="F.3.2.1" table="F.3-2" name="File Set Identification Module">
    <entry group="0004" element="1130" name="File-set ID" type="2">
      <description>User or implementation specific Identifier (up to 16 characters). For definition, see PS 3.10. The File-set ID is intended to be a short human readable label to easily (but not necessarily uniquely) identify a specific File-set to facilitate operator manipulation of the physical media on which the File-set is stored. Assignment of Value and semantics are environment specific.</description>
    </entry>
    <entry group="0004" element="1141" name="File-set Descriptor File ID" type="3">
      <description>ID of a File (in the same File-set) used for user comments related to the File-set (e.g. a readme file). The Specific Character set used may be specified in the Specific Character Set of the File-set Descriptor File (0004,1142).
Note: This File is not DICOM formatted (no Preamble, nor DICM Prefix and Meta Information).</description>
    </entry>
    <entry group="0004" element="1142" name="Specific Character Set of File-set Descriptor File" type="1C">
      <description>Character set used in the File-set Descriptor File with a File ID as specified in File-set Descriptor File ID (0004,1141). Required to specify the expanded or replacement character set. If absent, only the Basic Graphic set is used. See C.12.1.1.2 for Defined Terms.</description>
      <section ref="C.12.1.1.2" name="">Specific Character Set (0008,0005) identifies the Character Set that expands or replaces the Basic Graphic Set (ISO 646) for values of Data Elements that have Value Representation of SH, LO, ST, PN, LT or UT. See PS 3.5.
If the Attribute Specific Character Set (0008,0005) is not present or has only a single value, Code Extension techniques are not used. Defined terms for the Attribute Specific Character Set (0008,0005), when single valued, are derived from the International Registration Number as per ISO 2375 (e.g., ISO_IR 100 for Latin alphabet No. 1). See Table C.12-2.
Table C.12-2
 DEFINED TERMS FOR SINGLE-BYTE CHARACTER SETS WITHOUT CODE EXTENSIONS
<unrecognized-rows><term value="Character Set Description" meaning="Defined Term"/><term value="Default repertoire" meaning="none"/><term value="Latin alphabet No. 1" meaning="ISO_IR 100"/><term value=""/><term value="Latin alphabet No. 2" meaning="ISO_IR 101"/><term value=""/><term value="Latin alphabet No. 3" meaning="ISO_IR 109"/><term value=""/><term value="Latin alphabet No. 4" meaning="ISO_IR 110"/><term value=""/><term value="Cyrillic" meaning="ISO_IR 144"/><term value=""/><term value="Arabic" meaning="ISO_IR 127"/><term value=""/><term value="Greek" meaning="ISO_IR 126"/><term value=""/><term value="Hebrew" meaning="ISO_IR 138"/><term value=""/><term value="Latin alphabet No. 5" meaning="ISO_IR 148"/><term value=""/><term value="Japanese" meaning="ISO_IR 13"/><term value=""/><term value="Thai" meaning="ISO_IR 166"/><term value=""/></unrecognized-rows>
Note:  To use the single-byte code table of JIS X0201, the value of attribute Specific Character Set (0008,0005), value 1 should be ISO_IR 13. This means that ISO-IR 13 is designated as the G1 code element which is invoked in the GR area. It should be understood that, in addition, ISO-IR 14 is designated as the G0 code element and this is invoked in the GL area.

If the attribute Specific Character Set (0008,0005) has more than one value, Code Extension techniques are used and Escape Sequences may be encountered in all character sets. Requirements for the use of Code Extension techniques are specified in PS 3.5. In order to indicate the presence of Code Extension, the Defined Terms for the repertoires have the prefix “ISO 2022”, e.g., ISO 2022 IR 100 for the Latin Alphabet No. 1. See Table 12-3 and Table 12-4. Table 12-3 describes single-byte character sets for value 1 to value n of the attribute Specific Character Set (0008,0005), and Table 12-4 describes multi-byte character sets for value 2 to value n of the attribute Specific Character Set (0008,0005).
Note:  A prefix other than “ISO 2022” may be needed in the future if other Code Extension techniques are adopted.
Table C.12-3
DEFINED TERMS FOR SINGLE-BYTE CHARACTER SETS WITH CODE EXTENSIONS
<unrecognized-rows><term value="Character Set Description" meaning="Defined Term"/><term value="Default repertoire" meaning="ISO 2022 IR 6"/><term value="No. 1" meaning="ISO 2022 IR 100"/><term value="No. 2" meaning="ISO 2022 IR 101"/><term value="No. 3" meaning="ISO 2022 IR 109"/><term value="No. 4" meaning="ISO 2022 IR 110"/><term value="Cyrillic" meaning="ISO 2022 IR 144"/><term value="Arabic" meaning="ISO 2022 IR 127"/><term value="Greek" meaning="ISO 2022 IR 126"/><term value="Hebrew" meaning="ISO 2022 IR 138"/><term value="No. 5" meaning="ISO 2022 IR 148"/><term value="Japanese" meaning="ISO 2022 IR 13"/><term value="Thai" meaning="ISO 2022 IR 166"/><term value=""/></unrecognized-rows>
Note:  If the attribute Specific Character Set (0008,0005) has more than one value and value 1 is empty, it is assumed that value 1 is ISO 2022 IR 6.

Table C.12-4
DEFINED TERMS FOR MULTI-BYTE CHARACTER SETS WITH CODE EXTENSIONS
<unrecognized-rows><term value="Character Set Description" meaning="Defined Term"/><term value="Japanese" meaning="ISO 2022 IR 87"/><term value="" meaning="ISO 2022 IR 159"/><term value="Korean" meaning="ISO 2022 IR 149"/></unrecognized-rows>
There are multi-byte character sets that prohibit the use of Code Extension Techniques. The Unicode character set used in ISO 10646, when encoded in UTF-8, and the GB18030 character set, encoded per the rules of GB18030, both prohibit the use of Code Extension Techniques. These character sets may only be specified as value 1 in the Specific Character Set (0008,0005) attribute and there shall only be one value. The minimal length UTF-8 encoding shall always be used for ISO 10646.
Notes:  1. The ISO standards for 10646 now prohibit the use of anything but the minimum length encoding for UTF-8. UTF-8 permits multiple different encodings, but when used to encode Unicode characters in accordance with ISO 10646-1 and 10646-2 (with extensions) only the minimal encodings are legal.
  2. The representation for the characters in the DICOM Default Character Repertoire is the same single byte value for the Default Character Repertoire, ISO 10646 in UTF-8, and GB18030. It is also the 7-bit US-ASCII encoding.
Table C.12-5
DEFINED TERMS FOR MULTI-BYTE CHARACTER SETS WITHOUT CODE EXTENSIONS
<unrecognized-rows><term value="Character Set Description" meaning="Defined Term"/><term value="Unicode in UTF-8" meaning="ISO_IR 192"/><term value="GB18030" meaning="GB18030"/></unrecognized-rows>
         </section>
    </entry>
  </module>
  <module ref="F.3.2.2" table="F.3-3" name="Directory Information Module">
    <entry group="0004" element="1200" name="Offset of the First Directory Record of the Root Directory Entity" type="1">
      <description>Offset of the first byte (of the Item Data Element) of the first Directory Record of the Root Directory Entity. This Offset is a number of bytes starting with the first byte of the File Meta Information. When the Root Directory Entity contains no Directory Record, this offset shall be set to 00000000H.
Note: This offset includes the File Preamble and the DICM Prefix.</description>
    </entry>
    <entry group="0004" element="1202" name="Offset of the Last Directory Record of the Root Directory Entity" type="1">
      <description>Offset of the first byte (of the Item Data Element) of the last Directory Record of the Root Directory Entity. This Offset is a number of bytes starting with the first byte of the File Meta Information. When the Root Directory Entity contains no Directory Record, this offset shall be set to 00000000H.
Note: This offset includes the File Preamble and the DICM Prefix.</description>
    </entry>
    <entry group="0004" element="1212" name="File-set Consistency Flag" type="1">
      <description>When set, this Flag indicates that an inconsistency within the Directory or between the Directory and the Files of the File-set may exist. Potential recovery actions are implementation specific and are beyond the scope of this Standard. Enumerated Values:
0000H: no known inconsistencies
FFFFH: the FSR or FSU shall assume that inconsistencies are present.
This flag shall be set by implementations before a File-set update which, if interrupted, may result in an inconsistent File-set.
Note: There may be error conditions where an inconsistency is present but this flag is not set. There may also be conditions where no inconsistencies are present but the flag is set.</description>
    </entry>
    <entry group="0004" element="1220" name="Directory Record Sequence" type="2">
      <description>Sequence of zero or more Items where each Item contains a Directory Record by including the Directory Elements from (0004,1400) to (0004,1511) and Record selection Keys as defined below (marked with a &gt;).
A zero length Value indicates that no Directory Records are contained in the Root Directory Entity.</description>
    </entry>
    <entry group="0004" element="1400" name="&gt;Offset of the Next Directory Record" type="1">
      <description>Offset of the first byte (of the Item Data Element) of the next Directory Record of the same Directory Entity. This Offset is an unsigned integer representing a number of bytes starting with the first byte of the File Meta-information. A zero offset shall be used to mean that there is no other Directory Record in this Directory Entity.
This Offset may be used to keep an inactive Record (0004,1410) chained with the next Directory Record of the same Directory Entity.
Note: This offset includes the File Preamble and the DICM Prefix.</description>
    </entry>
    <entry group="0004" element="1410" name="&gt;Record In-use Flag" type="1">
      <description>This flag facilitates the deletion of referenced files.
Enumerated Values:
FFFFH = record is in use.
0000H = record is inactive. All attributes of an inactive Directory Record except (0004,1400) and (0004,1410) shall be ignored.
Other Values are reserved and shall not be set by File-set Creators, but if present shall be interpreted as FFFFH by File-set Readers or Updaters.
If a Directory Record is changed from in use to inactive, the FSU shall ensure that all Directory Records of referenced lower-level Directory Entities are changed to inactive.</description>
    </entry>
    <entry group="0004" element="1420" name="&gt;Offset of Referenced Lower-Level Directory Entity" type="1">
      <description>Offset of the first byte (of the Item Data Element) of the first Directory Record of the Referenced Lower Level Directory Entity. This Offset is a number of bytes starting with the first byte of the File Meta Information.
When no lower-level Directory Entity (containing at least one Directory Record) is referenced, this Attribute shall have a Value of 00000000H.
Note: This offset includes the File Preamble and the DICM Prefix.</description>
    </entry>
    <entry group="0004" element="1430" name="&gt;Directory Record Type" type="1">
      <description>Defines a specialized type of Directory Record by reference to its position in the Media Storage Directory Information Model (see Section F.4).
Enumerated Values (see Section F.5):
PATIENT STUDY SERIES
IMAGE
RT DOSE RT STRUCTURE SET
RT PLAN RT TREAT RECORD
PRESENTATION WAVEFORM
SR DOCUMENT KEY OBJECT DOC
SPECTROSCOPY RAW DATA
REGISTRATION FIDUCIAL
HANGING PROTOCOL ENCAP DOC
HL7 STRUC DOC VALUE MAP
STEREOMETRIC

PRIVATE = Privately defined record hierarchy position. Type shall be defined by Private Record UID (0004,1432).
Notes: 1. Enumerated Values PRINT QUEUE, FILM SESSION, FILM BOX, and IMAGE BOX were previously defined in DICOM for this Attribute. They are now retired. See PS3.3-1998.
2. Enumerated Values OVERLAY, MODALITY LUT, VOI LUT, CURVE, TOPIC, VISIT, RESULTS, INTERPRETATION, STUDY COMPONENT and STORED PRINT were previously defined in DICOM for this Attribute. They are now retired. See PS3.3-2004.
3. Enumerated Value MRDR was previously defined in DICOM for this Attribute, to allow indirect reference to a File by multiple Directory Records. It is now retired. FSUs and FSRs are unlikely to be capable of supporting this mechanism. See PS3.3-2004.</description>
    </entry>
    <entry group="0004" element="1432" name="&gt;Private Record UID" type="1C">
      <description>Required if the Directory Record Type (0004,1430) is of Value PRIVATE. This UID is used to define a non-standard type of Directory Record by reference to its position in a private extension to the Basic Directory IOD Information Model (see Section F.5). This UID shall be registered according to the procedures defined in PS 3.5. Its meaning may or may not be specified in a Conformance Statement.</description>
    </entry>
    <entry group="0004" element="1500" name="&gt;Referenced File ID" type="1C">
      <description>A Multiple Value (See PS 3.5) which represents the ordered components of the File ID containing a "referenced object" or Referenced SOP Instance. A maximum of 8 components, each from 1 to 8 characters shall be used (see Section 8.2).
Note: The Referenced File ID provides the means to "locate" the File through the DICOM File Service provided by the Media Format Layer.
All referenced Files shall be with the File-set to which the Directory belongs. Any File within the File-set (to which the Directory belongs) shall be referenced by at most one Directory Record. When the Directory Record does not reference any SOP Instance this attribute shall not be present.</description>
    </entry>
    <entry group="0004" element="1510" name="&gt;Referenced SOP Class UID in File" type="1C">
      <description>Unique ID for the SOP Class of the Instance stored in the referenced File.
Required if the Directory Record references a SOP Instance.</description>
    </entry>
    <entry group="0004" element="1511" name="&gt;Referenced SOP Instance UID in File" type="1C">
      <description>Unique Identifier for the SOP Instance stored in the referenced file.
Required if the Directory Record references a SOP Instance.</description>
    </entry>
    <entry group="0004" element="1512" name="&gt;Referenced Transfer Syntax UID in File" type="1C">
      <description>Unique Identifier for the Transfer Syntax used to encode the Instance stored in the referenced file.
Required if the Directory Record references a SOP Instance.</description>
    </entry>
    <entry group="0004" element="151A" name="&gt;Referenced Related General SOP Class UID in File" type="1C">
      <description>Unique ID for the Related General SOP Class(es) related to the SOP Class of the Instance stored in the referenced file.
Required if the Directory Record references a SOP Instance that encodes the Related General SOP Class UID (0008,001A).
Note: This may be useful to an FSR that does not support the SOP Class of the referenced Instance, but which does support one of the Related General SOP Classes.</description>
    </entry>
    <include ref="&gt;Record Selection Keys" type="SeeF.5" description="A number of DICOM Data Elements which contain specific keys defined for each type of Directory Record (0004,1430) defined in Section F.5."/>
  </module>
  <!-- TODO FIXME -->
  <!-- drt : directory record type -->
<!--
  <iod table="F.4-1" name="Relationship Between Directory Records">
    <entry drt="Patient" ref="F.5.1" usage="M"/>
    <entry drt="Study" ref="F.5.2" usage="M"/>
    <entry drt="Series" ref="F.5.3" usage="M"/>
  </iod>
-->
  <module ref="F.5.1" table="F.5-1" name="Patient Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys</description>
    </entry>
    <entry group="0010" element="0010" name="Patient's Name" type="2">
      <description/>
    </entry>
    <entry group="0010" element="0020" name="Patient ID" type="1">
      <description/>
    </entry>
    <include ref="Any other Attribute of the Patient IOD or Patient IE Modules" type="3"/>
  </module>
  <module ref="F.5.2" table="F.5-2" name="Study Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys</description>
    </entry>
    <entry group="0008" element="0020" name="Study Date" type="1">
      <description/>
    </entry>
    <entry group="0008" element="0030" name="Study Time" type="1">
      <description/>
    </entry>
    <entry group="0008" element="1030" name="Study Description" type="2">
      <description/>
    </entry>
    <entry group="0020" element="000D" name="Study Instance UID" type="1C">
      <description>Required only if (0004,1511) is absent.
(See Note)</description>
    </entry>
    <entry group="0020" element="0010" name="Study ID" type="1">
      <description/>
    </entry>
    <entry group="0008" element="0050" name="Accession Number" type="2">
      <description/>
    </entry>
    <include ref="Any other Attribute of the Study IOD or Study IE Modules" type="3"/>
  </module>
  <module ref="F.5.3" table="F.5-3" name="Series Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys</description>
    </entry>
    <entry group="0008" element="0060" name="Modality" type="1">
      <description/>
    </entry>
    <entry group="0020" element="000E" name="Series Instance UID" type="1">
      <description/>
    </entry>
    <entry group="0020" element="0011" name="Series Number" type="1">
      <description/>
    </entry>
    <entry group="0088" element="0200" name="Icon Image Sequence" type="3">
      <description>This Icon Image is representative of the Series. It may or may not correspond to one of the images of the Series. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt; Include 'Image Pixel Macro' Table C.7-11b" description="See Section F.7 of this Part."/>
    <include ref="Any other Attribute of the Series IE Modules" type="3"/>
  </module>
  <module ref="F.5.4" table="F.5-4" name="Image Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description/>
    </entry>
    <entry group="0088" element="0200" name="Icon Image Sequence" type="3">
      <description>This Icon Image is representative of the Image. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt; Include 'Image Pixel Macro' Table C.7-11b" description="See Section F.7 of this Part."/>
    <include ref="Any other Attribute of the Image IE Modules" type="3"/>
  </module>
  <module ref="F.5.19" table="F.5-19" name="RT Dose Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description/>
    </entry>
    <entry group="3004" element="000A" name="Dose Summation Type" type="1">
      <description/>
    </entry>
    <entry group="3004" element="0006" name="Dose Comment" type="3">
      <description/>
    </entry>
    <entry group="0088" element="0200" name="Icon Image Sequence" type="3">
      <description>This Icon Image is representative of the RT Dose. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt; Include 'Image Pixel Macro' Table C.7-11b" description="See Section F.7 of this part."/>
    <include ref="Any other Attribute of the Dose IE Modules" type="3"/>
  </module>
  <module ref="F.5.20" table="F.5-20" name="RT Structure Set Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description/>
    </entry>
    <entry group="3006" element="0002" name="Structure Set Label" type="1">
      <description/>
    </entry>
    <entry group="3006" element="0008" name="Structure Set Date" type="2">
      <description/>
    </entry>
    <entry group="3006" element="0009" name="Structure Set Time" type="2">
      <description/>
    </entry>
    <include ref="Any other Attribute of the Structure Set IE Modules" type="3"/>
  </module>
  <module ref="F.5.21" table="F.5-21" name="RT Plan Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description/>
    </entry>
    <entry group="300A" element="0002" name="RT Plan Label" type="1">
      <description/>
    </entry>
    <entry group="300A" element="0006" name="RT Plan Date" type="2">
      <description/>
    </entry>
    <entry group="300A" element="0007" name="RT Plan Time" type="2">
      <description/>
    </entry>
    <include ref="Any other Attribute of the Plan IE Modules" type="3"/>
  </module>
  <module ref="F.5.22" table="F.5-22" name="RT Treatment Record Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description/>
    </entry>
    <entry group="3008" element="0250" name="Treatment Date" type="2">
      <description/>
    </entry>
    <entry group="3008" element="0251" name="Treatment Time" type="2">
      <description/>
    </entry>
    <include ref="Any other Attribute of the Treatment Record IE Modules" type="3"/>
  </module>
  <module ref="F.5.23" table="F.5-23" name="Presentation Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0070" element="0082" name="Presentation Creation Date" type="1">
      <description>Date on which this presentation was created.
Note: This date may be different from the date that the DICOM SOP Instance was created, since the presentation state information contained may have been recorded earlier.</description>
    </entry>
    <entry group="0070" element="0083" name="Presentation Creation Time" type="1">
      <description>Time at which this presentation was created.
Note: This time may be different from the time that the DICOM SOP Instance was created, since the presentation state information contained may have been recorded earlier.</description>
    </entry>
    <include ref="Include Content Identification Macro Table 10-12"/>
    <entry group="0008" element="1115" name="Referenced Series Sequence" type="1C">
      <description>Sequence of Items where each Item includes the Attributes of one Series to which the Presentation applies.
Required if the IOD of the Presentation SOP Instance referenced by this directory record includes the Presentation State Relationship Module. One or more Items may be included in this Sequence.</description>
    </entry>
    <entry group="0020" element="000E" name="&gt;Series Instance UID" type="1">
      <description>Unique identifier of a Series that is part of this Study.</description>
    </entry>
    <entry group="0008" element="1140" name="&gt;Referenced Image Sequence" type="1">
      <description>Sequence of Items where each Item provides reference to an Image SOP Instance .</description>
    </entry>
    <include ref="&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <entry group="0070" element="0402" name="Blending Sequence" type="1C">
      <description>Sequence of exactly two Items where each Item includes the Attributes of a Study to which the Presentation applies.
Required if the SOP Instance referenced by this directory record includes the Blending Sequence (0070,0402) attribute.</description>
    </entry>
    <entry group="0020" element="000D" name="&gt;Study Instance UID" type="1">
      <description>Unique identifier for a Study that contains the images to which the Presentation applies.</description>
    </entry>
    <entry group="0008" element="1115" name="&gt;Referenced Series Sequence" type="1">
      <description>Sequence of Items where each Item includes the Attributes of one Series to which the Presentation applies.
Only a single item shall be permitted in this Sequence.</description>
    </entry>
    <entry group="0020" element="000E" name="&gt;&gt;Series Instance UID" type="1">
      <description>Unique identifier of the Series</description>
    </entry>
    <entry group="0008" element="1140" name="&gt;&gt;Referenced Image Sequence" type="1">
      <description>Sequence of Items where each Item provides reference to an Image SOP Instance to which the Presentation applies</description>
    </entry>
    <include ref="&gt;&gt;&gt;Include 'SOP Instance Reference Macro' Table 10-11"/>
    <include ref="Any other Attribute of the Presentation IE Modules" type="3"/>
  </module>
  <module ref="F.5.24" table="F.5-24" name="Waveform Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description/>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description/>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description/>
    </entry>
    <include ref="Any other Attribute of the Waveform IE Modules" type="3"/>
  </module>
  <module ref="F.5.25" table="F.5-25" name="SR Document Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description/>
    </entry>
    <entry group="0040" element="A491" name="Completion Flag" type="1">
      <description/>
    </entry>
    <entry group="0040" element="A493" name="Verification Flag" type="1">
      <description/>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description/>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description/>
    </entry>
    <entry group="0040" element="A030" name="Verification DateTime" type="1C">
      <description>Most recent Date and Time of verification among those defined in the Verifying Observer Sequence (0040,A073).
Required if Verification Flag (0040,A493) is VERIFIED.</description>
    </entry>
    <entry group="0040" element="A043" name="Concept Name Code Sequence" type="1">
      <description>Code describing the concept represented by the root Content Item (Document Title). This sequence shall contain exactly one Item.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1"/>
    <entry group="0040" element="A730" name="Content Sequence" type="1C">
      <description>Contains the Target Content Items that modify the Concept Name Code Sequence of the root Content Item (Document Title).
Required if the root Content Item is the Source Content Item of HAS CONCEPT MOD relationships.
One or more Items shall be included in this Sequence. All, and only, Content Items with the HAS CONCEPT MOD relationship from the root Content Item shall be included in this Sequence.</description>
    </entry>
    <entry group="0040" element="A010" name="&gt;Relationship Type" type="1">
      <description>Enumerated Value:
HAS CONCEPT MOD</description>
    </entry>
    <include ref="&gt;Include Document Content Macro Table C.17-5"/>
    <include ref="Any Attribute of the Document IE Modules" type="3"/>
  </module>
  <module ref="F.5.26" table="F.5-26" name="Key Object Document Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description/>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description/>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description/>
    </entry>
    <entry group="0040" element="A043" name="Concept Name Code Sequence" type="1">
      <description>Code describing the concept represented by the root Content Item (Document Title). This sequence shall contain exactly one Item.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1"/>
    <entry group="0040" element="A730" name="Content Sequence" type="1C">
      <description>Contains the Target Content Items that modify the Concept Name Code Sequence of the root Content Item (Document Title).
Required if the root Content Item is the Source Content Item of HAS CONCEPT MOD relationships.
One or more Items shall be included in this Sequence. All, and only, Content Items with the HAS CONCEPT MOD relationship from the root Content Item shall be included in this Sequence.</description>
    </entry>
    <entry group="0040" element="A010" name="&gt;Relationship Type" type="1">
      <description>Enumerated Value:
HAS CONCEPT MOD</description>
    </entry>
    <include ref="&gt;Include Document Content Macro Table C.17-5"/>
    <include ref="Any Attribute of the Document IE Modules" type="3"/>
  </module>
  <module ref="F.5.27" table="F.5-27" name="Spectroscopy Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0008" element="0008" name="Image Type" type="1">
      <description/>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description/>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description/>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description/>
    </entry>
    <entry group="0008" element="9092" name="Referenced Image Evidence Sequence" type="1C">
      <description>Required if present in the spectroscopy instance.</description>
    </entry>
    <include ref="&gt;Include ''Hierarchical SOP Instance Reference Macro' Table C.17-3"/>
    <entry group="0028" element="0008" name="Number of Frames" type="1">
      <description/>
    </entry>
    <entry group="0028" element="0010" name="Rows" type="1">
      <description/>
    </entry>
    <entry group="0028" element="0011" name="Columns" type="1">
      <description/>
    </entry>
    <entry group="0028" element="9001" name="Data Point Rows" type="1">
      <description/>
    </entry>
    <entry group="0028" element="9002" name="Data Point Columns" type="1">
      <description/>
    </entry>
    <entry group="0088" element="0200" name="Icon Image Sequence" type="3">
      <description>This Icon Image is representative of the Spectroscopy instance. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include Image Pixel Macro Table C.7-11b" description="See Section F.7 of this Part."/>
    <include ref="Any other Attribute of the Spectroscopy IE Modules" type="3"/>
  </module>
  <module ref="F.5.28" table="F.5-28" name="Raw Data Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description/>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description/>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="2">
      <description/>
    </entry>
    <entry group="0088" element="0200" name="Icon Image Sequence" type="3">
      <description>This Icon Image is representative of the Raw Data instance. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include Image Pixel Macro Table C.7-11b" description="See Section F.7 of this Part."/>
    <include ref="Any other Attribute of the Raw Data IE Modules" type="3"/>
  </module>
  <module ref="F.5.29" table="F.5-29" name="Registration Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the content creation started.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the content creation started.</description>
    </entry>
    <include ref="Include Content Identification Macro Table 10-12"/>
    <include ref="Any other Attribute of the Spatial Registration IE Modules" type="3"/>
  </module>
  <module ref="F.5.30" table="F.5-30" name="Fiducial Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the content creation started.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the content creation started.</description>
    </entry>
    <include ref="Include Content Identification Macro Table 10-12"/>
    <include ref="Any other Attribute of the Spatial Fiducials IE Modules" type="3"/>
  </module>
  <macro table="F.5-31" name="Hanging Protocol Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys</description>
    </entry>
    <entry group="0072" element="0002" name="Hanging Protocol Name" type="1">
      <description/>
    </entry>
    <entry group="0072" element="0004" name="Hanging Protocol Description" type="1">
      <description/>
    </entry>
    <entry group="0072" element="0006" name="Hanging Protocol Level" type="1">
      <description/>
    </entry>
    <entry group="0072" element="0008" name="Hanging Protocol Creator" type="1">
      <description/>
    </entry>
    <entry group="0072" element="000A" name="Hanging Protocol Creation DateTime" type="1">
      <description/>
    </entry>
    <entry group="0072" element="000C" name="Hanging Protocol Definition Sequence" type="1">
      <description>Sequence that defines the type of imaging studies to which this Hanging Protocol applies. One or more sequence items shall be present.</description>
    </entry>
    <entry group="0008" element="0060" name="&gt;Modality" type="1C">
      <description>Required if Anatomic Region Sequence (0008,2218) is not present. May be present otherwise.</description>
    </entry>
    <entry group="0008" element="2218" name="&gt;Anatomic Region Sequence" type="1C">
      <description>Required if Modality (0008,0060) is not present. May be present otherwise.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1"/>
    <entry group="0020" element="0060" name="&gt;Laterality" type="2C">
      <description>Required if Anatomic Region Sequence (0008,2218) is present.</description>
    </entry>
    <entry group="0008" element="1032" name="&gt;Procedure Code Sequence" type="2">
      <description>One or more Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1"/>
    <entry group="0040" element="100A" name="&gt;Reason for Requested Procedure Code Sequence" type="2">
      <description>One or more Items may be included in this sequence.</description>
    </entry>
    <include ref="&gt;&gt;Include Code Sequence Macro Table 8.8-1"/>
    <entry group="0072" element="0014" name="Number of Priors Referenced" type="1">
      <description/>
    </entry>
    <entry group="0072" element="000E" name="Hanging Protocol User Identification Code Sequence" type="2">
      <description>Sequence that provides a coded identifier for the person, group, or site for which this Hanging Protocol was defined. Zero or one Items may be included in this Sequence.</description>
    </entry>
    <include ref="&gt;Include Code Sequence Macro Table 8.8-1"/>
    <include ref="Any other Attribute of the Hanging Protocol IOD" type="3"/>
  </macro>
  <module ref="F.5.32" table="F.5-32" name="Encapsulated Document Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="2">
      <description>The date the content creation started.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="2">
      <description>The time the content creation started.</description>
    </entry>
    <entry group="0020" element="0013" name="Instance Number" type="1">
      <description>A number that identifies this instance</description>
    </entry>
    <entry group="0042" element="0010" name="Document Title" type="2">
      <description>The title of the document.</description>
    </entry>
    <entry group="0040" element="E001" name="HL7 Instance Identifier" type="1C">
      <description>Instance Identifier from the referenced HL7 Structured Document, encoded as a UID (OID or UUID), concatenated with a caret ("^") and Extension value (if Extension is present in Instance Identifier).
Required if encapsulated document is an HL7 Structured Document.</description>
    </entry>
    <entry group="0040" element="A043" name="Concept Name Code Sequence" type="2">
      <description>A coded representation of the document title. Zero or one item may be present.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" type="1" description="Baseline Context Group 7020"/>
    <entry group="0042" element="0012" name="MIME Type of Encapsulated Document" type="1">
      <description>The type of the encapsulated document stream described using the MIME Media Type (see RFC 2046).</description>
    </entry>
    <include ref="Any other Attribute of the Encapsulated Document Module except Encapsulated Document (0042,0011)" type="3"/>
  </module>
  <module ref="F.5.33" table="F.5-33" name="HL7 Structured Document Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0040" element="E001" name="HL7 Instance Identifier" type="1">
      <description>Instance Identifier from the referenced HL7 Structured Document, encoded as a UID (OID or UUID), concatenated with a caret ("^") and Extension value (if Extension is present in Instance Identifier).</description>
    </entry>
    <entry group="0040" element="E004" name="HL7 Document Effective Time" type="1">
      <description>Effective Time from the referenced HL7 Structured Document</description>
    </entry>
    <entry group="0040" element="E006" name="HL7 Document Type Code Sequence" type="1C">
      <description>Document Type Code from the referenced HL7 Structured Document. Required if the HL7 Structured Document contains a Document Type Code. Only a single Item shall be permitted in this Sequence.</description>
    </entry>
    <include ref="&gt;Include 'Code Sequence Macro' Table 8.8-1" description="No BCID defined"/>
    <entry group="0042" element="0010" name="Document Title" type="1C">
      <description>Document Title from the referenced HL7 Structured Document. Required if the HL7 Structured Document contains a Document Title.</description>
    </entry>
  </module>
  <module ref="F.5.34" table="F.5-34" name="Real World Value Mapping Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <entry group="0008" element="0023" name="Content Date" type="1">
      <description>The date the content creation started.</description>
    </entry>
    <entry group="0008" element="0033" name="Content Time" type="1">
      <description>The time the content creation started.</description>
    </entry>
    <include ref="Include Content Identification Macro Table 10-12"/>
    <include ref="Any other Attribute of the Real World Value Mapping IE Modules" type="3"/>
  </module>
  <module ref="F.5.35" table="F.5-35" name="Stereometric Relationship Keys">
    <entry group="0008" element="0005" name="Specific Character Set" type="1C">
      <description>Required if an extended or replacement character set is used in one of the keys.</description>
    </entry>
    <include ref="Any other Attribute of the Stereometric relationship IE Modules" type="3"/>
  </module>
</tables>
