| (0028,0009) |
Frame Increment Pointer |
1C
|
Required if Multi-Frame Image. Contains the Data Element Tag of the attribute which 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). |
| (0028,2110) |
Lossy Image Compression |
1C
|
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. |
| (0008,0008) |
Image Type |
1
|
Image identification characteristics. See C.8.7.1.1.1 for specialization. |
| (0028,1040) |
Pixel Intensity Relationship |
1
|
The relationship between the Pixel sample values and the X-Ray beam intensity. See Section C.8.7.1.1.2. |
| (0028,0002) |
Samples per Pixel |
1
|
Number of samples (color planes) in this image shall have a value of 1. |
| (0028,0004) |
Photometric Interpretation |
1
|
Specifies the intended interpretation of the pixel data. Only MONOCHROME2 may be used. |
| (0028,0100) |
Bits Allocated |
1
|
Number of bits allocated for each pixel sample. See Section C.8.7.1.1.6. |
| (0028,0101) |
Bits Stored |
1
|
Number of bits stored for each pixel sample. See Section C.8.7.1.1.7. |
| (0028,0102) |
High Bit |
1
|
Most significant bit for pixel sample data. See Section C.8.7.1.1.8. |
| (0028, 0103 |
Pixel Representation |
D
|
0028ata representation of the pixel samples. Shall have the value: 0000H = Unsigned Integer. |
| (0018,0022) |
Scan Options |
3
|
Parameters of scanning sequence. See Section C. 8.7.1.1.4. |
| (0008,2218) |
Anatomic Region Sequence |
3
|
Sequence of one Item that identifies the anatomic region of interest in this image (i.e. external anatomy, surface anatomy, or general region of the body). This anatomic region is placed on the table for examination. See C.8.7.1.1.10. |
| (0008,2220) |
>Anatomic Region Modifier Sequence |
3
|
Sequence of one or more Items that modifies the anatomic region of interest in this image (i.e. prone, supine, decubitus right). May be present only if Anatomic Region Sequence (0008,2218) is sent. See C.8.7.1.1.10. |
| (0008,2228) |
Primary Anatomic Structure Sequence |
3
|
Sequence of one or more Items that identifies the primary anatomic structure of interest in this image. See C.8.7.1.1.11. |
| (0008,2230) |
>Primary Anatomic Structure Modifier Sequence |
3
|
Sequence of one or more Items that modifies the primary anatomic structure of interest in this image. May be present only if Primary Anatomic Structure Sequence (0008,2228) is sent. See C.8.7.1.1.11. |
| (0028,6040) |
R Wave Pointer |
3
|
Marks the location(s) of the R Wave in the cardiac cycles by referencing frame numbers; frame numbers begin with 1. |
| (0008,1140) |
Reference Image Sequence |
1C
|
A sequence which provides reference to a set of Image SOP Class/Instance identifying other images significantly related to this image. Shall be used to relate each plane to the corresponding plane if Image Type (0008,0008) Value 3 is BIPLANE A or BIPLANE B. When relating to the corresponding plane of a Biplane acquisition, only a single item shall be present. |
| (0008,1150) |
> Reference SOP Class UID |
1C
|
Uniquely identifies the referenced SOP Class. Required if Referenced Image Sequence (0008,1140) is present. |
| (0008,1155) |
> Reference SOP Instance UID |
1C
|
Uniquely identifies the referenced SOP Instance. Required if Referenced Image Sequence (0008,1140) is present. |
| (0008,2111) |
Derivation Description |
3
|
A text description of how this image was derived. See C.8.7.1.1.5 for further explanation. |
| (0018,1400) |
Acquisition Device Processing Description |
3
|
Indicates any visual processing performed on the images prior to exchange. See Section C.8.7.1.1.3. |
| (0050,0004) |
Calibration Image |
3
|
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. |