This chapter describes different scenarios and application cases organized by domains of application. Each application case is basically structured in four sections:
1) User Scenario : Describes the user needs in a specific clinical context, and/or a particular system configuration and equipment type.
2) Encoding Outline : Describes the specificities of the XA SOP Class and the Enhanced XA SOP Class related to this scenario, and highlights the key aspects of the Enhanced XA SOP Class to address it.
3) Encoding Details : Provides detailed recommendations of the key attributes of the object(s) to address this particular scenario.
4) Example : Presents a typical example of the scenario, with realistic sample values, and gives details of the encoding of the key attributes of the object(s) to address this particular scenario. In the values of the attributes, the text in bold face indicates specific attribute values; the text in italic face gives an indication of the expected value content.
This application case is related to the results of an X-Ray acquisition and parallel ECG data recording on the same equipment.
The image acquisition system records ECG signals simultaneously with the acquisition of the Enhanced XA multi-frame image. All the ECG signals are acquired at the same sampling rate.
The acquisition of both image and ECG data are not triggered by an external signal.
The information can be exchanged via Offline Media or Network.
Synchronization between the ECG Curve and the image frames allows synchronized navigation in each of the data sets.
The General ECG IOD is used to store the waveform data recorded in parallel to the image acquisition encoded as Enhanced XA IOD.
The Synchronization Module is used to specify a common time-base.
The option of encoding trigger information is not recommended by this case.
The solution assumes implementation on a single imaging modality and therefore the mutual UID references between the General ECG and Enhanced XA objects is recommended. This will allow faster access to the related object.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.1-1. Enhanced X-Ray Angiographic Image IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Series |
General Series |
C.7.3.1 |
The General Series Module Modality (0008,0060) attribute description in PS3.3 enforces the storage of waveform and pixel data in different Series IE. |
Frame of Reference |
Synchronization |
C.7.4.2 |
Specifies that the image acquisition is synchronized. Will have the same content as the General ECG SOP Instance. |
Equipment |
General Equipment |
C.7.5.1 |
Same as in the General ECG SOP Instance. |
Image |
Cardiac Synchronization |
C.7.6.18.1 |
Contains information of the type of relationship between the ECG waveform and the image. |
Enhanced XA/XRF Image |
C.8.19.2 |
Contains UID references to the related General ECG SOP Instance. |
Table FFF.2.1-2. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
Frame Content |
C.7.6.16.2.2 |
Provides timing information to correlate each frame to the recorded ECG samples. |
Cardiac Synchronization |
C.7.6.16.2.7 |
Provides time relationships between the angiographic frames and the cardiac cycle. |
The usage of this Module is recommended to encode a "synchronized time" condition.
The specialty of Synchronization Triggers is not part of this scenario.
Table FFF.2.1-3. Synchronization Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Synchronization Frame of Reference UID |
(0020,0200) |
Same UID as in the related General ECG SOP Instance. |
Synchronization Trigger |
(0018,106A) |
In this scenario with no external trigger signal, the value "NO TRIGGER" is used. |
Acquisition Time Synchronized |
(0018,1800) |
The value "Y" is used in this scenario. |
The usage of this Module is recommended to assure that the image contains identical equipment identification information as the referenced General ECG SOP Instance.
The usage of this module is recommended to indicate that the ECG is not used to trig the X-Ray acquisition, rather to time relate the frames to the ECG signal.
Table FFF.2.1-4. Cardiac Synchronization Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Cardiac Synchronization Technique |
(0018,9037) |
The value "REAL TIME" is used in this scenario. |
Cardiac Signal Source |
(0018,9085) |
In this scenario, the value "ECG" is used to indicate that the cardiac waveform is an electrocardiogram. |
The usage of this module is recommended to reference from the image object to the related General ECG SOP Instance that contains the ECG data recorded simultaneously.
Table FFF.2.1-5. Enhanced XA/XRF Image Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Referenced Instance Sequence |
(0008,114A) |
Reference to "General ECG SOP Instance" acquired in conjunction with this image. Contains a single item. |
>Referenced SOP Class UID |
(0008,1150) |
"1.2.840.10008.5.1.4.1.1.9.1.2" i.e., reference to an General ECG SOP Instance |
>Referenced SOP Instance UID |
(0008,1155) |
Instance UID of referenced waveform |
>Purpose of Reference Code Sequence |
(0040,A170) |
CID 7004 “Waveform Purposes of Reference” is used; identify clear reason for the Reference. |
If there is a specific ECG analysis that determines the time between the R-peaks and the angiographic frames, the usage of this macro is recommended.
As the frames are acquired at a frame rate independent of cardiac phases, this macro is used in a "per frame functional group" to encode the position of each frame relative to its prior R-peak.
In this scenario the timing information is important to correlate each frame to the recorded ECG.
If there is a specific ECG analysis, this macro allows the encoding of the position in the cardiac cycle that is most representative of each frame.
The following table gives recommendations for usage in this scenario.
Table FFF.2.1-6. Frame Content Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Frame Content Sequence |
(0020,9111) |
|
>Frame Reference DateTime |
(0018,9151) |
Exact Time taken from the internal clock. |
>Frame Acquisition DateTime |
(0018,9074) |
Exact Time taken from the internal clock. |
>Cardiac Cycle Position |
(0018,9236) |
Optional, if ECG analysis is available. |
This IOD will encode the recorded ECG waveform data, which is done by the image acquisition system. Since this is not a dedicated waveform modality device, appropriate defaults for most of the data have to be recommended to fulfill the requirements according to PS3.3.
Table FFF.2.1-7. General ECG IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Series |
General Series |
C.7.3.1 |
The General Series Module Modality (0008,0060) attribute description in PS3.3 enforces the storage of waveform and pixel data in different Series IE. |
Frame of Reference |
Synchronization |
C.7.4.2 |
Specifies that the waveform acquisition is synchronized. Will have the same content as the image. |
Equipment |
General Equipment |
C.7.5.1 |
Same as in the image. |
Waveform |
Waveform Identification |
C.10.8 |
Contains references to the related image object. |
Waveform |
C.10.9 |
Contains one multiplex group with the same sampling rate. |
A new Series is created to set the modality "ECG" for the waveform.
Most of the attributes are aligned with the contents of the related series level attributes in the image object.
The Related Series Sequence (0008,1250) is not recommended because instance level relationship can be applied to reference the image instances.
Table FFF.2.1-8. General Series Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Modality |
(0008,0060) |
"ECG" |
Series Instance UID |
(0020,000E) |
Different from the one of the image object. |
Series Date |
(0008,0021) |
Identical to the contents of related image object |
Series Time |
(0008,0031) |
Identical to the contents of related image object. |
Other attributes of General Series Module |
Match contents of related image object, if set there. |
The usage of this Module is recommended to encode a "synchronized time" condition, which was previously implicit when using the curve module.
Table FFF.2.1-9. Synchronization Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Synchronization Frame of Reference UID |
(0020,0200) |
Same UID as in the related image object. |
Synchronization Trigger |
(0018,106A) |
The value "NO TRIGGER" is used in this scenario with no external trigger signal. |
Acquisition Time Synchronized |
(0018,1800) |
The value "Y" is used to allow synchronized navigation. |
The usage of this Module is recommended to assure that the General ECG SOP Instance contains identical equipment identification information as the referenced image objects.
The usage of this module is recommended to relate the acquisition time of the waveform data to the image acquired simultaneously.
The module additionally includes an instance level reference to the related image.
Table FFF.2.1-10. Waveform Identification Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Acquisition DateTime |
(0008,002A) |
Exact start of the waveform acquisition taken from common (or synchronized) clock. NoteIn case the ECG acquisition started before the image acquisition itself, the given DateTime value is not the same as for the image. |
Referenced Instance Sequence |
(0008,114A) |
Only one item used in this application case. |
>Referenced SOP Class UID |
(0008,1150) |
"1.2.840.10008.5.1.4.1.1.12.1.1" i.e., Enhanced XA |
>Referenced SOP Instance UID |
(0008,1155) |
Instance UID of Enhanced XA Image Object to which this parallel ECG recording is related. |
>Purpose of Reference Code Sequence |
(0040,A170) |
The referenced image is related to this ECG. |
The usage of this module is a basic requirement of the General ECG IOD.
Any application displaying the ECG is recommended to scale the ECG contents to its output capabilities (esp. the amplitude resolution).
If more than one ECG signal needs to be recorded, the grouping of the channels in multiplex groups depends on the ECG sampling rate. All the channels encoded in the same multiplex group have identical sampling rate.
Table FFF.2.1-11. Waveform Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Waveform Sequence |
(5400,0100) |
Only one item is used in this application case, as all the ECG signals have the same sampling rate. |
> Multiplex Group Time Offset |
(0018,1068) |
If needed, specify the Group Offset from the Acquisition DateTime. |
> Waveform Originality |
(003A,0004) |
The value "ORIGINAL" is used in this scenario. |
In the two following examples, the Image Modality acquires a multi-frame image of the coronary arteries lasting 4 seconds, at 30 frames per second.
Simultaneously, the same modality acquires two channels of ECG from a 2-Lead ECG (the first channel on Lead I and the second on Lead II) starting one second before the image acquisition starts, and lasting 5 seconds, with a sampling frequency of 300 Hz on 16 bits signed encoding, making up a number of 1500 samples per channel. The first ECG sample is 10 ms after the nominal start time of the ECG acquisition. Both ECG channels are sampled simultaneously. The time skew of both channels is 0 ms.
In this example, the Enhanced XA image does not contain information of the cardiac cycle phases.
The attributes that define the two different SOP Instances (Enhanced XA and General ECG) of this example are described in Figure FFF.2.1-3.
Enhanced XA SOP Instance
In this example, the heart rate is 75 beats per minute. As the image is acquired during a period of four seconds, it contains five heartbeats.
The ECG signal is analyzed to determine the R-peaks and to relate them to the angiographic frames. Thus the Enhanced XA image contains information of this relationship between the ECG signal and the frames.
The attributes that define the two different SOP Instances (Enhanced XA and General ECG) of this example are described in the figures of the previous example, in addition to the attributes described in Figure FFF.2.1-5.
Enhanced XA SOP Instance
These application cases are related to the results of an X-Ray acquisition and simultaneous ECG data recording on different equipment. The concepts of synchronized time and triggers are involved.
The two modalities may share references on the various entity levels below the Study, i.e., Series and Image UID references using non standard mechanisms. Nothing in the workflow requires such references. For more details about UID referencing, refer to the previous application case "ECG Recording at Acquisition Modality" (see Section FFF.2.1.1).
If both modalities share a common data store, a dedicated post-processing station can be used for combined display of waveform and image information, and/or combined functional analysis of signals and pixel data to time relate the cardiac cycle phases to the angiographic frames. The storage of the waveform data and images to PACS or media will preserve the combined functional capabilities.
In these application cases, this post-processing activity is outside the scope of the acquisition modalities. For more details about the relationship between cardiac cycle and angiographic frames, refer to the previous application case "ECG Recording at Acquisition Modality" (see Section FFF.2.1.1).
Image runs are taken by the image acquisition modality. Waveforms are recorded by the waveform acquisition modality. Both modalities are time synchronized via NTP. The time server may be one of the modalities or an external server. The resulting objects will include the time synchronization concept.
Dedicated Waveform IODs exist to store captured waveforms. In this case, General ECG IOD is used to store the waveform data.
Depending on the degree of coupling of the modalities involved, the usage of references on the various entity levels can vary. While there is a standard DICOM service to share Study Instance UID between modalities (i.e., Worklist), there are no standard DICOM services for sharing references below the Study level, so any UID reference to the Series and Image levels is shared in a proprietary manner.
With the Synchronization Module information, the method to implement the common time-base can be documented.
The Enhanced XA IOD provides a detailed "per frame" timing to encode timing information related to each frame.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.1-12. Enhanced X-Ray Angiographic Image IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Frame of Reference |
Synchronization |
C.7.4.2 |
Specifies that the image acquisition is time synchronized with the ECG acquisition. Will have the same content as the General ECG SOP Instance. |
Image |
Enhanced XA/XRF Image |
C.8.19.2 |
Specifies the date and time of the image acquisition. |
Table FFF.2.1-13. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
Frame Content |
C.7.6.16.2.2 |
Provides timing information to correlate each frame to any externally recorded waveform. |
This Module is used to document the synchronization of the two modalities.
Table FFF.2.1-14. Synchronization Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Synchronization Frame of Reference UID |
(0020,0200) |
The UTC Synchronization UID "1.2.840.10008.15.1.1" is used in this case. |
Synchronization Trigger |
(0018,106A) |
The value "NO TRIGGER" is used for the case of time synchronization via NTP. |
Acquisition Time Synchronized |
(0018,1800) |
The value "Y" is used in this scenario. |
Time Source |
(0018,1801) |
The same value as in the related General ECG SOP Instance is used in this scenario. |
Time Distribution Protocol |
(0018,1802) |
The value "NTP" is used in this scenario. |
NTP Source Address |
(0018,1803) |
The same value as in the related General ECG SOP Instance is used in this scenario. |
This module includes the acquisition date and time of the image, which is in the same time basis as the acquisition date and time of the ECG in this scenario.
In this scenario the timing information is important to correlate each frame to any externally recorded waveform.
Table FFF.2.1-15. Frame Content Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Frame Content Sequence |
(0020,9111) |
|
>Frame Reference DateTime |
(0018,9151) |
Exact date and time taken from the synchronized clock. |
>Frame Acquisition DateTime |
(0018,9074) |
Exact date and time taken from the synchronized clock. |
The ECG recording system will take care of filling in the waveform-specific contents in the General ECG SOP Instance. This section will address only the specifics for attributes related to synchronization.
Table FFF.2.1-16. Waveform IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Frame of Reference |
Synchronization |
C.7.4.2 |
Specifies that the ECG acquisition is time synchronized with the image acquisition. Will have the same content as the Enhanced XA SOP Instance. See Section FFF.2.1.2.1.3.1.1. |
Waveform |
Waveform Identification |
C.10.8 |
Provides timing information to correlate the waveform data to any externally recorded image. |
FFF.2.1.2.1.3.2.1 Waveform Identification Recommendations
The usage of this module is recommended to relate the acquisition time of the waveform data to the related image(s).
Table FFF.2.1-18. Waveform Identification Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Acquisition DateTime |
(0008,002A) |
Exact start of the waveform acquisition: taken from synchronized clock. |
In this example, there are two modalities that are synchronized with an external clock via NTP. The Image Modality acquires three multi-frame images within the same Study and same Series. Simultaneously, the Waveform Modality acquires the ECG non-stop during the same period, leading to one single Waveform SOP Instance on a different Study.
In this example, there is no UID referencing capability between the two modalities.
The attributes that define the relevant content in the two different SOP Instances (Enhanced XA and General ECG) are described in Figure FFF.2.1-8.
Image runs are taken by the image acquisition modality. Waveforms are recorded by waveform recording modality. Both modalities are time synchronized via NTP. The acquisition in one modality is triggered by the other modality. The resulting objects will include the time synchronization and trigger synchronization concepts.
There are two cases depending on the triggering modality:
1- At X-Ray start, the image modality sends a trigger signal to the waveform modality.
2- The waveform modality sends trigger signals to the image modality to start the acquisition of each frame.
Dedicated Waveform IODs exist to store captured waveforms. In this case, General ECG IOD is used to store the waveform data.
With the Synchronization Module information, the method to implement the triggers can be documented.
The Enhanced XA IOD provides per-frame encoding of the timing information related to each frame.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.1-20. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
Frame Content |
C.7.6.16.2.2 |
Provides timing information of each frame. |
The usage of this Module is recommended to document the triggering role of the image modality.
Table FFF.2.1-21. Synchronization Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Synchronization Frame of Reference UID |
(0020,0200) |
The UTC Synchronization UID "1.2.840.10008.15.1.1" is used in this case. |
Synchronization Trigger |
(0018,106A) |
The value "SOURCE" is used when the image modality sends a trigger signal to the waveform modality. The value "EXTERNAL" is used when the image modality receives a trigger signal from the waveform modality. |
Trigger Source or Type |
(0018,1061) |
If Synchronization Trigger (0018,106A) equals SOURCE, then ID of image equipment. If Synchronization Trigger (0018,106A) equals EXTERNAL, then ID of waveform equipment if it is known. |
Acquisition Time Synchronized |
(0018,1800) |
The value "Y" is used in this scenario. |
Time Source |
(0018,1801) |
The same value as in the related General ECG SOP Instance is used in this scenario. |
Time Distribution Protocol |
(0018,1802) |
The value "NTP" is used in this scenario. |
NTP Source Address |
(0018,1803) |
The same value as in the related General ECG SOP Instance is used in this scenario. |
This module includes the acquisition date and time of the image.
Table FFF.2.1-22. Enhanced XA/XRF Image Module Recommendations
Attribute |
Tag |
Comment |
---|---|---|
Acquisition DateTime |
(0008,002A) |
Exact date and time taken from the synchronized clock. |
In this scenario the timing information does not allow relating each frame to any externally recorded waveform.
Table FFF.2.1-23. Frame Content Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Frame Content Sequence |
(0020,9111) |
|
>Frame Reference DateTime |
(0018,9151) |
Exact date and time taken from the synchronized clock. |
>Frame Acquisition DateTime |
(0018,9074) |
Exact date and time taken from the synchronized clock. |
The recording system will take care of filling in the waveform-specific contents, based on the IOD relevant for the type of system (e.g., EP, Hemodynamic, etc.). This section will address only the specifics for attributes related to synchronization.
Table FFF.2.1-24. Waveform IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Frame of Reference |
Synchronization |
C.7.4.2 |
Specifies that the ECG acquisition triggers (or is triggered by) the image acquisition, and that they are time synchronized. |
Waveform |
Waveform Identification |
C.10.8 |
Specifies the date and time of the ECG acquisition. |
Waveform |
C.10.9 |
Specifies the time relationship between the trigger signal and the ECG samples. |
The usage of this Module is recommended to document the triggering role of the waveform modality.
Table FFF.2.1-25. Synchronization Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Synchronization Frame of Reference UID |
(0020,0200) |
The UTC Synchronization UID "1.2.840.10008.15.1.1" is used in this case. |
Synchronization Trigger |
(0018,106A) |
The value "EXTERNAL" is used when the waveform modality receives a trigger signal from the image modality. The value "SOURCE" is used when the waveform modality sends a trigger signal to the image modality. |
Trigger Source or Type |
(0018,1061) |
If Synchronization Trigger (0018,106A) equals SOURCE, then ID of Waveform equipment. If Synchronization Trigger (0018,106A) equals EXTERNAL, then ID of image equipment if it is known. |
Synchronization Channel |
(0018,106C) |
Number or ID of Synchronization channel recorded in this waveform. |
Acquisition Time Synchronized |
(0018,1800) |
The value "Y" is used in this scenario. |
Time Source |
(0018,1801) |
The same value as in the related image SOP Instance is used in this scenario. |
Time Distribution Protocol |
(0018,1802) |
The value "NTP" is used in this scenario. |
NTP Source Address |
(0018,1803) |
The same value as in the related image SOP Instance is used in this scenario. |
This module includes the acquisition date and time of the waveform, which may be different than the acquisition date and time of the image in this scenario.
Table FFF.2.1-26. Waveform Identification Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Acquisition DateTime |
(0008,002A) |
Exact date and time taken from the internal clock of the Waveform modality. It may be different from the Acquisition DateTime of the Enhanced XA SOP instance. |
The usage of this module is recommended to encode the time relationship between the trigger signal and the ECG samples.
Table FFF.2.1-27. Waveform Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Waveform Sequence |
(5400,0100) |
Only one item is used in this application case, as all the ECG signals have the same sampling rate. |
>Multiplex Group Time Offset |
(0018,1068) |
If needed, specify the Group Offset from the Acquisition DateTime. |
>Waveform Originality |
(003A,0004) |
The value "ORIGINAL" is used in this scenario. |
>Trigger Time Offset |
(0018,1069) |
In case the waveform recording started with a synchronization trigger from the image modality, this value allows specifying the time relationship between the trigger and the ECG samples. |
>Trigger Sample Position |
(0018,106E) |
In case the waveform recording started with a synchronization trigger from the image modality, this value allows specifying the waveform sample corresponding to the trigger sent from the image modality. |
In this example, there are two modalities that are synchronized with an external clock via NTP. The Image Modality acquires three multi-frame images within the same Study and same Series. Simultaneously, the Waveform Modality acquires the ECG non-stop during the same period, leading to one single Waveform SOP Instance on a different Study. The ECG sampling frequency is 300 Hz on 16 bits signed encoding, making up a number of 1500 samples per channel. The first ECG sample is acquired at nominal start time of the ECG acquisition.
The image modality sends a trigger to the waveform modality at the start time of each of the three images. This signal is stored in one channel of the waveform modality, together with the ECG signal.
In this example, there is no UID referencing capability between the two modalities.
The attributes that define the relevant content in the two different SOP Instances (Enhanced XA and General ECG) are described in Figure FFF.2.1-11.
In this example, there are two modalities that are synchronized with an external clock via NTP.
The Image Modality starts the X-Ray image acquisition and simultaneously the Waveform Modality acquires the ECG and analyzes the signal to determine the phases of the cardiac cycles. At each cycle, the waveform modality sends a trigger to the image modality to start the acquisition of a frame. This trigger is stored in one channel of the waveform modality, together with the ECG signal.
The ECG sampling frequency is 300 Hz on 16 bits signed encoding, making up a number of 1500 samples per channel. The first ECG sample is acquired 10 ms after the nominal start time of the ECG acquisition.
In this example, there is no UID referencing capability between the two modalities.
The attributes that define the relevant content in the two different SOP Instances (Enhanced XA and General ECG) are described in Figure FFF.2.1-13.
This section provides information on the encoding of the movement of the X-Ray Positioner during the acquisition of a rotational angiography.
The related image presentation parameters of the rotational acquisition that are defined in the Enhanced XA SOP Class, such as the mask information of subtracted display, are described in further sections of this annex.
The multi-frame image acquisition is performed during a continuous rotation of the X-Ray Positioner, starting from the initial incidence and acquiring frames in a given angular direction at variable angular steps and variable time intervals.
Typically such rotational acquisition is performed with the purpose of further 3D reconstruction. The rotation axis is not necessarily the patient head-feet direction, which may lead to images where the patient is not heads-up oriented.
There may be one or more rotations of the X-Ray Positioner during the same image acquisition, performed by following different patterns, such as:
One rotation for non-subtracted angiography;
Two rotations in the same or in opposite angular directions, for subtracted angiography;
Several rotations at different time intervals for cardiac triggered acquisitions.
The XA SOP Class encodes the absolute positioner angles as the sum of the angle of the first frame and the increments relative to the first frame. The Enhanced XA SOP Class encodes per-frame absolute angles.
In the XA SOP Class, the encoding of the angles is always with respect to the patient, so-called anatomical angles, and the image is assumed to be patient-oriented (i.e., heads-up display). In case of positioner rotation around an axis oblique to the patient, not aligned with the head-feet axis, it is not possible to encode the rotation of the image necessary for 3D reconstruction.
The Enhanced XA SOP Class encodes the positioner angles with respect to the patient as well as with respect to a fixed coordinate system of the equipment.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.1-28. Enhanced X-Ray Angiographic Image IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Image |
XA/XRF Acquisition |
C.8.19.3 |
Specifies the type of positioner. |
Table FFF.2.1-29. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
X-Ray Positioner |
C.8.19.6.10 |
Specifies the anatomical angles per-frame. |
X-Ray Isocenter Reference System |
C.8.19.6.13 |
Specifies the angles of the positioner per-frame in equipment coordinates for further applications based on the acquisition geometry (e.g., 3D reconstruction, registration…). |
The usage of this module is recommended to define the type of positioner.
Table FFF.2.1-30. XA/XRF Acquisition Module Example
Attribute Name |
Tag |
Comment |
---|---|---|
Positioner Type |
(0018,1508) |
The value CARM is used in this scenario. |
C-arm Positioner Tabletop Relationship |
(0018,9474) |
Both values YES and NO are applicable to this scenario. NoteOn mobile systems where this attribute equals NO, it is possible to do rotation and 3D reconstruction. In such case, the table is assumed to be static during the acquisition. |
This macro is used in the per-frame context in this scenario.
Table FFF.2.1-31. X-Ray Positioner Macro Example
Attribute Name |
Tag |
Comment |
---|---|---|
Positioner Position Sequence |
(0018,9405) |
|
>Positioner Primary Angle |
(0018,1510) |
Angle with respect to the patient coordinate system. |
>Positioner Secondary Angle |
(0018,1511) |
Angle with respect to the patient coordinate system. |
If the value of the C-arm Positioner Tabletop Relationship (0018,9474) is NO, the following macro may not be provided by the acquisition modality. This macro is used in the per-frame context in this scenario.
Table FFF.2.1-32. X-Ray Isocenter Reference System Macro Example
Attribute Name |
Tag |
Comment |
---|---|---|
Isocenter Reference System Sequence |
(0018,9462) |
|
>Positioner Isocenter Primary Angle |
(0018,9463) |
Angle with respect to the Isocenter coordinate system, independent of table angulations and how the patient is positioned on the table. |
>Positioner Isocenter Secondary Angle |
(0018,9464) |
Angle with respect to the Isocenter coordinate system, independent of table angulations and how the patient is positioned on the table. |
>Positioner Isocenter Detector Rotation Angle |
(0018,9465) |
Angle with respect to the Isocenter coordinate system, independent of table angulations and how the patient is positioned on the table. |
In this example, the patient is on the table, in position "Head First Prone". The table horizontal, tilt and rotation angles are equal to zero.
The positioner performs a rotation of 180 deg from the left to the right side of the patient, with the image detector going above the back of the patient, around an axis parallel to the head-feet axis of the patient.
The encoded values of the key attributes of this example are shown in Figure FFF.2.1-15.
This section provides information on the encoding of the movement of the X-Ray Table during the acquisition of a stepping angiography.
The related image presentation parameters of the stepping acquisition that are defined in the Enhanced XA SOP Class, such as the mask information of subtracted display, are described in further sections of this annex.
The multi-frame image acquisition is performed during a movement of the X-Ray Table, starting from the initial position and acquiring frames in a given direction along the Z axis of the table at variable steps and variable time intervals.
There may be one or more "stepping movements" of the X-Ray Table during the same image acquisition, leading to one or more instances of the Enhanced XA SOP Class. The stepping may be performed by different patterns, such as:
One stepping for non-subtracted angiography;
Two stepping acquisitions, one for each leg, for non-subtracted angiography, stored in two different multi-frame images;
Two or more stepping acquisitions for subtracted angiography, in the same or in opposite directions.
The XA SOP Class encodes table position as increments relative to the position of the first frame, while the position of the first frame is not encoded.
The Enhanced XA SOP Class encodes per-frame absolute table vertical, longitudinal and lateral position, as well as table horizontal rotation angle, table head tilt angle and table cradle tilt angle.
This allows registration between separate multi-frame images in the same table frame of reference, as well as accounting for magnification ratio and other aspects of geometry during registration. Issues of patient motion during acquisition of the images is not addressed in this scenario.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.1-33. Enhanced X-Ray Angiographic Image IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Image |
XA/XRF Acquisition |
C.8.19.3 |
Specifies the relationship between the table and the positioner. |
Table FFF.2.1-34. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
X-Ray Table Position |
C.8.19.6.11 |
Specifies the table position per-frame in three dimensions. |
X-Ray Isocenter Reference System |
C.8.19.6.13 |
Specifies the position and the angles of the table per-frame in equipment coordinates, for further applications based on the acquisition geometry (e.g., registration…). |
The usage of this module is recommended to specify the relationship between the table and the positioner.
Table FFF.2.1-35. XA/XRF Acquisition Module Example
Attribute Name |
Tag |
Comment |
---|---|---|
C-arm Positioner Tabletop Relationship |
(0018,9474) |
Both values YES and NO are applicable to this scenario. NoteOn mobile systems where this attribute equals NO, it is possible to do table stepping. In such case, the system is not able to determine the absolute table position relative to the Isocenter, which is necessary for 2D-2D registration. |
This macro is used in the per-frame context in this scenario.
Table FFF.2.1-36. X-Ray Table Position Macro Example
Attribute Name |
Tag |
Comment |
---|---|---|
Table Position Sequence |
(0018,9406) |
|
>Table Top Vertical Position |
(300A,0128) |
The same value for all frames. |
>Table Top Longitudinal Position |
(300A,0129) |
The same value for all frames. |
>Table Top Lateral Position |
(300A,012A) |
Different values per frame, corresponding to the "stepping" intervals in the table plane. |
>Table Horizontal Rotation Angle |
(0018,9469) |
The same value for all frames. |
>Table Head Tilt Angle |
(0018,9470) |
The same value for all frames. |
>Table Cradle Tilt Angle |
(0018,9471) |
The same value for all frames. |
If the value of the C-arm Positioner Tabletop Relationship (0018,9474) is NO, the following macro may not be provided by the acquisition modality. This macro is used in the per-frame context in this scenario.
Table FFF.2.1-37. X-Ray Isocenter Reference System Macro Example
Attribute Name |
Tag |
Comment |
---|---|---|
Isocenter Reference System Sequence |
(0018,9462) |
|
>Table X Position to Isocenter |
(0018,9466) |
X-position of a fixed point in the table top, it changes per-frame if table horizontal rotation is not zero |
>Table Y Position to Isocenter |
(0018,9467) |
Vertical position of a fixed point in the table top, it changes per-frame if table head tilt is not zero |
>Table Z Position to Isocenter |
(0018,9468) |
Z-position of a fixed point in the table top, it changes per-frame |
>Table Horizontal Rotation Angle |
(0018,9469) |
The same value for all frames. |
>Table Head Tilt Angle |
(0018,9470) |
The same value for all frames. |
>Table Cradle Tilt Angle |
(0018,9471) |
The same value for all frames. |
In this example, the patient is on the table in position "Head First Supine". The table is tilted of -10 degrees, with the head of the patient below the feet, and the image detector is parallel to the tabletop plane. The table cradle and rotation angles are equal to zero.
The image acquisition is performed during a movement of the X-Ray Table in the tabletop plane, at constant speed and of one meter of distance, acquiring frames from the abdomen to the feet of the patient in one stepping movement for non-subtracted angiography.
The table is related to the C-arm positioner so that the coordinates of the table position are known in the isocenter reference system. This allows determining the projection magnification of the table top plane with respect to the detector plane.
The encoded values of the key attributes of this example are shown in Figure FFF.2.1-18.
This section provides information on the encoding of the "sensitive areas" used for regulation control of the X-Ray generation of an image that resulted from applying these X-Rays.
The user a) takes previous selected regulation settings or b) manually enters regulation settings or c) automatically gets computer-calculated regulation settings from requested procedures.
Acquired images are networked or stored in offline media.
Later problems of image quality are determined and user wants to check for reasons by assessing the positions of the sensing regions.
The Enhanced XA IOD includes a module to supply information about active regulation control sensing fields, their shape and position relative to the pixel matrix.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.1-38. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
X-Ray Exposure Control Sensing Regions |
C.8.19.6.3 |
Specifies the shape and size of the sensing regions in pixels, as well as their position relative to the top left pixel of the image. |
This macro is recommended to encode details about sensing regions.
If the position of the sensing regions is fixed during the multi-frame acquisition, the usage of this macro is shared.
If the position of the sensing regions was changed during the multi-frame acquisition, this macro is encoded per-frame to reflect the individual positions.
The same number of regions is typically used for all the frames of the image. However it is technically possible to activate or deactivate some of the regions during a given range of frames, in which case this macro is encoded per-frame.
Table FFF.2.1-39. X-Ray Exposure Control Sensing Regions Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Exposure Control Sensing Regions Sequence |
(0018,9434) |
As many items as number of regions. |
In this section, two examples are given.
The first example shows how three sensing regions are encoded: 1) central (circular), 2) left (rectangular) and 3) right (rectangular).
The encoded values of the key attributes of this example are shown in Figure FFF.2.1-20.
The second example shows the same regions, but the field of view region encoded in the Pixel Data matrix has been shifted of 240 pixels right and 310 pixels down, thus the left rectangular sensing region is outside the Pixel Data matrix as well as both rectangular regions overlap the top row of the image matrix.
Figure FFF.2.1-21. Example of X-Ray Exposure Control Sensing Regions partially outside the Pixel Data matrix
The encoded values of the key attributes of this example are shown in Figure FFF.2.1-22.
This section provides information on the encoding of the image detector parameters and field of view applied during the X-Ray acquisition.
The user selects a given size of the field of view before starting the acquisition. This size can be smaller than the size of the Image Detector.
The position of the field of view in the detector area changes during the acquisition in order to focus on an object of interest.
Acquired image is networked or stored in offline media, then the image is:
Displayed and reviewed in cine mode, and the field of view area needs to be displayed on the viewing screen;
Used for quality assurance, to relate the pixels of the stored image to the detector elements, for instance to understand the image artifacts due to detector defects;
Used to measure the dimension of organs or other objects of interest;
Used to determine the position in the 3D space of the projection of the objects of interest.
The XA SOP Class does not encode some information to fully characterize the geometry of the conic projection acquisition, such as the position of the Positioner Isocenter on the FOV area. Indeed, the XA SOP Class assumes that the isocenter is projected in the middle of the FOV.
The Enhanced XA SOP Class encodes the position of the Isocenter on the detector, as well as specific FOV attributes (origin, rotation, flip) per-frame or shared. It encodes some existing attributes from DX to specify information of the Digital Detector and FOV. It also allows differentiating the image intensifier vs. the digital detector and then defines conditions on attributes depending on image intensifier or digital detector.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.1-41. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
X-Ray Field of View |
C.8.19.6.2 |
Specifies the field of view. |
XA/XRF Frame Pixel Data Properties |
C.8.19.6.4 |
Specifies the Imager Pixel Spacing. |
The usage of this module is recommended to specify the type and details of the receptor.
Table FFF.2.1-42. XA/XRF Acquisition Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
X-Ray Receptor Type |
(0018,9420) |
Two values are applicable to this scenario: IMG_INTENSIFIER or DIGITAL_DETECTOR |
Distance Receptor Plane to Detector Housing |
(0018,9426) |
Applicable to this scenario, regardless the type of receptor. |
Distance Receptor Plane to Detector Housing (0018,9426) is a positive value except in the case of an image intensifier where the receptor plane is a virtual plane located outside the detector housing, which depends on the magnification factor of the intensifier.
The Distance Receptor Plane to Detector Housing (0018,9426) may be used to calculate the pixel size of the plane in the patient when markers are placed on the detector housing.
When the X-Ray Receptor Type (0018,9420) equals "IMG_INTENSIFIER" this module specifies the type and characteristics of the image intensifier.
The Intensifier Size (0018,1162) is defined as the physical diameter of the maximum active area of the image intensifier. The active area is the region of the input phosphor screen that is projected on the output phosphor screen. The image intensifier device may be configured for several predefined active areas to allow different levels of magnification.
The active area is described by the Intensifier Active Shape (0018,9427) and the Intensifier Active Dimension(s) (0018,9428).
The field of view area is a region equal to or smaller than the active area, and is defined as the region that is effectively irradiated by the X-Ray beam when there is no collimation. The stored image is the image resulting from digitizing the field of view area.
There is no attribute that relates the FOV origin to the intensifier. It is commonly assumed that the FOV area is centered in the intensifier.
The position of the projection of the isocenter on the active area is undefined. It is commonly understood that the X-Ray positioner is calibrated so that the isocenter is projected in the approximate center of the active area, and the field of view area is centered in the active area.
When the X-Ray Receptor Type (0018,9420) equals "DIGITAL_DETECTOR" this module specifies the type and characteristics of the image detector.
The size and pixel spacing of the digital image generated at the output of the digital detector are not necessarily equal to the size and element spacing of the detector matrix. The detector binning is defined as the ratio between the pixel spacing of the detector matrix and the pixel spacing of the digital image.
If the detector binning is higher than 1.0 several elements of the detector matrix contribute to the generation of one single digital pixel.
The digital image may be processed, cropped and resized in order to generate the stored image. The schema below shows these two steps of the modification of the pixel spacing between the detector physical elements and the stored image:
Table FFF.2.1-43. X-Ray Detector Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Detector Binning |
(0018,701A) |
The ratio between the pixel spacing of the detector matrix and the pixel spacing of the digital image. It does not describe any further post-processing to resize the pixels to generate the stored image. |
Detector Element Spacing |
(0018,7022) |
Pixel spacing of the detector matrix. |
Position of Isocenter Projection |
(0018,9430) |
Relates the position of the detector elements to the isocenter reference system. It is independent from the detector binning and from the field of view origin. This attribute is defined if the Isocenter Reference System Sequence (0018,9462) is present. |
The usage of this macro is recommended to specify the characteristics of the field of view.
When the field of view characteristics change across the multi-frame image, this macro is encoded on a per-frame basis.
The field of view region is defined by a shape, origin and dimension. The region of irradiated pixels corresponds to the interior of the field of view region.
When the X-Ray Receptor Type (0018,9420) equals "IMG_INTENSIFIER", the intensifier TLHC is undefined. Therefore the field of view origin cannot be related to the physical area of the receptor. It is commonly understood that the field of view area corresponds to the intensifier active area, but there is no definition in the DICOM standard that forces a manufacturer to do so. As a consequence, it is impossible to relate the position of the pixels of the stored area to the isocenter reference system.
Table FFF.2.1-44. X-Ray Field of View Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Field of View Sequence |
(0018,9432) |
|
>Field of View Shape |
(0018,1147) |
Applicable in this scenario. |
>Field of View Dimension(s) in Float |
(0018,9461) |
Applicable in this scenario. |
>Field of View Origin |
(0018,7030) |
Applicable only in the case of digital detector. |
>Field of View Rotation |
(0018,7032) |
Applicable regardless the type of receptor. |
>Field of View Horizontal Flip |
(0018,7034) |
Applicable regardless the type of receptor. |
>Field of View Description |
(0018,9433) |
Free text defining the type of field of view as displayed by the manufacturer on the acquisition system. For display purposes. |
The usage of this macro is recommended to specify the Imager Pixel Spacing.
When the field of view characteristics change across the multi-frame image, this macro is encoded on a per-frame basis.
Table FFF.2.1-45. XA/XRF Frame Pixel Data Properties Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Frame Pixel Data Properties Sequence |
(0028,9443) |
|
>Imager Pixel Spacing |
(0018,1164) |
Applicable regardless the type of receptor. |
In case of image intensifier, the Imager Pixel Spacing (0018,1164) may be non-uniform due to the pincushion distortion, and this attribute corresponds to a manufacturer-defined value (e.g., average, or value at the center of the image).
This example illustrates the encoding of the dimensions of the intensifier device, the intensifier active area and the field of view in case of image intensifier.
In this example, the diameter of the maximum active area is 410 mm. The image acquisition is performed with an electron lens that focuses the photoelectron beam inside the intensifier so that an active area of 310 mm of diameter is projected on the output phosphor screen.
The X-Ray beam is projected on an area of the input phosphor screen of 300 mm of diameter, and the corresponding area on the output phosphor screen is digitized on a matrix of 1024 x1024 pixels. This results on a pixel spacing of the digitized matrix of 0.3413 mm.
The distance from the Receptor Plane to the Detector Housing in the direction from the intensifier to the X-Ray tube is 40 mm.
The encoded values of the key attributes of this example are shown in Figure FFF.2.1-25.
The following examples show three different ways to create the stored image from the same detector matrix.
In the figures below:
The blue dotted-line squares
represent the physical detector pixels;
The blue square
represents the TLHC pixel of the physical detector area;
The purple square
represents the physical detector pixel in whose center the Isocenter is projected;
The dark green square
represents the TLHC pixel of the region of the physical detector that is exposed to X-Ray when there is no collimation inside the field of view;
The light green square
represents the TLHC pixel of the stored image;
The thick black straight line square
represents the stored image, which is assumed to be the field of view area. The small thin black straight line squares represent the pixels of the stored image;
The blue dotted-line arrow
represents Field Of View Origin (0018,7030);
The purple arrow
represents the position of the Isocenter Projection (0018,9430).
Note that the detector active dimension is not necessarily the FOV dimension.
In all the examples,
The physical detector area is a matrix of 10x10 square detector elements, the TLHC element being the element (1,1);
The detector elements irradiated during this acquisition (defining the field of view) are in a matrix of 8x8 whose TLHC element is the element (3,3) of the physical detector area.
In the first example, there is neither binning nor resizing between the detector matrix and the stored image.
The encoded values of the key attributes of this example are shown in Figure FFF.2.1-26.
In the second example, there is a binning factor of 2 between the detector matrix and the digital image. There is no resizing between the digital image (binned) and the stored image.
The encoded values of the key attributes of this example are shown in Figure FFF.2.1-27.
In the third example, in addition to the binning factor of 2 between the detector matrix and the digital image, there is a resizing of 0.5 (downsizing) between the digital image (binned) and the stored image.
The encoded values of the key attributes of this example are shown in Figure FFF.2.1-28.
Note that the description of the field of view attributes (dimension, origin) is the same in these three examples. The field of view definition is independent from the binning and resizing processes.
This section provides information on the encoding of the presence and type of contrast bolus administered during the X-Ray acquisition.
The user performs image acquisition with injection of contrast agent during the X-Ray acquisition. Some frames are acquired without contrast, some others with contrast.
The type of contrast agent can be radio-opaque (e.g., iodine) or radio-transparent (e.g., CO2).
The information of the type of contrast and its presence or absence in the frames can be used by post-processing applications to set up e.g., vessel detection or image quality algorithms automatically.
The Enhanced XA SOP Class encodes the characteristics of the contrast agent(s) used during the acquisition of the image, including the type of absorption (radio-opaque or radio-transparent).
The Enhanced XA SOP Class also allows encoding the presence of contrast in a particular frame or set of frames, by encoding the Contrast/Bolus Usage per-frame.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.1-46. Enhanced X-Ray Angiographic Image IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Image |
Enhanced Contrast/Bolus |
C.7.6.4b |
Specifies the characteristics of the contrast agent(s) administered. |
Table FFF.2.1-47. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
Contrast/Bolus Usage |
C.7.6.16.2.12 |
Specifies the presence of contrast in the frame(s). |
The usage of this module is recommended to specify the type and characteristics of the contrast agent administered.
The usage of this macro is recommended to specify the characteristics of the contrast per-frame.
Table FFF.2.1-48. Contrast/Bolus Usage Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Contrast/Bolus Usage Sequence |
(0018,9341) |
One item per contrast agent used in this frame. |
>Contrast/Bolus Agent Number |
(0018,9337) |
Contains the internal number of the agent administered as specified in the Enhanced Contrast/Bolus Module. |
>Contrast/Bolus Agent Administered |
(0018,9342) |
The value "YES" indicates that the contrast may be visible on the frame, but not necessarily if the frame is acquired before the contrast reaches the imaged region. |
>Contrast/Bolus Agent Detected |
(0018,9343) |
The value "YES" is used if the contrast is visible on that particular frame. Note that it is not expected to be YES if Contrast/Bolus Agent Administered (0018,9342) equals NO. |
In this example, the user starts the X-Ray acquisition at 4 frames per second at 3:35pm. After one second the user starts the injection of 45 milliliters of contrast media Iodipamide (350 mg/ml Cholographin (Bracco) ) at a flow rate of 15 ml/sec during three seconds, in intra-arterial route. When the injection of contrast agent is finished, the user continues the X-Ray acquisition for two seconds until wash out of the contrast agent.
There could be two ways to determine the presence of contrast agent on the frames:
The injector is connected to the X-Ray acquisition system, the presence of contrast agent is determined based on the injector start/stop signals and a preconfigured delay to allow the contrast to reach the artery of interest, or.
The X-Ray system processes the images in real time and detects the presence or absence of contrast agent on the images.
In this example, the image acquired contains 25 frames: From frames 5 to 17, the contrast is being injected. From frames 8 to 23, the contrast is visible on the pixel data.
The figure below shows the attributes of this example in a graphical representation of the multi-frame acquisition.
The encoded values of the key attributes of this example are shown in Figure FFF.2.1-30.
This section provides information on the encoding of the parameters related to the X-Ray generation.
The user performs X-Ray acquisitions during the examination. Some of them are dynamic acquisitions where the positioner and/or the table have moved between frames of the multi-frame image, the acquisition parameters such as kVp, mA and pulse width may change per-frame to be adapted to the different anatomy characteristics.
Later quality assurance wants to assess the X-Ray generation techniques in order to understand possible degradation of image quality, or to estimate the level of irradiation at different skin areas and body parts examined.
The XA SOP Class encodes the attributes kVp, mA and pulse duration as a unique value for the whole multi-frame image. For systems that can provide only average values of these attributes, this SOP Class is more appropriate.
The Enhanced XA SOP Class encodes per-frame kVp, mA and pulse duration, thus the estimated dose per frame can be now correlated to the positioner angles and table position of each frame.
In order to accurately estimate the dose per body area, other attributes are needed such as positioner angles, table position, SID, ISO distances, Field of View, etc.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.1-49. Enhanced X-Ray Angiographic Image IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Image |
XA/XRF Acquisition |
C.8.19.3 |
Specifies average values for the X-Ray generation techniques. |
Table FFF.2.1-50. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
Frame Content |
C.7.6.16.2.2 |
Specifies the frame duration. |
X-Ray Frame Acquisition |
C.8.19.6.8 |
Specifies the kVp and mA per frame. |
The usage of this module is recommended to specify the average values of time, voltage and current applied during the acquisition of the multi-frame image.
It gives general information of the X-Ray radiation during the acquisition of the image. In case of dynamic acquisitions, this module is not sufficient to estimate the radiation per body area and additional per-frame information is needed.
Table FFF.2.1-51. XA/XRF Acquisition Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
KVP |
(0018,0060) |
Recommended in this scenario. |
Radiation Setting |
(0018,1155) |
The values "SC" and "GR" give a rough indication of the level of the dose such as "low" or "high", nevertheless they are used more for quality assurance and/or display purposes, not for estimation of radiation values. |
X-Ray Tube Current in mA |
(0018,9330) |
Recommended in this scenario. |
Exposure Time in ms |
(0018,9328) |
Recommended in this scenario. |
Exposure in mAs |
(0018,9332) |
Recommended in this scenario. |
Average Pulse Width |
(0018,1154) |
Recommended in this scenario. |
Radiation Mode |
(0018,115A) |
The value of this attribute is used more for quality assurance and/or display purposes, not for estimation of radiation values. |
Note that the three attributes X-Ray Tube Current in mA (0018,9330), Exposure Time in ms (0018,9328) and Exposure in mAs (0018,9332) are mutually conditional to each other but all three may be present. In this scenario it is recommended to include the three attributes.
The usage of this macro is recommended to specify the duration of each frame of the multi-frame image.
Note that this macro is allowed to be used only in a per-frame context, even if the pulse duration is constant for all the frames.
The usage of this macro is recommended to specify the values of voltage (kVp) and current (mA) applied for the acquisition of each frame of the multi-frame image.
If the system can provide only average values of kVp and mA, the usage of the X-Ray Frame Acquisition macro is not recommended, only the XA/XRF Acquisition Module is recommended.
If the system predefines the values of the kVp and mA to be constant during the acquisition, the usage of the X-Ray Frame Acquisition macro in a shared context is recommended in order to indicate that the value of kVp and mA is identical for each frame.
If the system is able to change dynamically the kVp and mA during the acquisition, the usage of the X-Ray Frame Acquisition macro in a per-frame context is recommended.
Table FFF.2.1-52. X-Ray Frame Acquisition Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Frame Acquisition Sequence |
(0018,9417) |
Recommended in this scenario if both values kVp and mA are known for each frame. |
For more details, refer to the Section FFF.1.4
This application case provides information on how X-Ray acquisitions with variable time between frames can be organized by groups of frames to be reviewed with individual group settings.
The image acquisition system performs complex acquisition protocols with groups of frames to be displayed at different frame rates and others to be skipped.
Allow frame-rates in viewing applications to be different than acquired rates.
The XA IOD provides only one group of frames between start and stop trim.
The Enhanced XA/XRF IOD allows encoding of multiple groups of frames (frame collections) with dedicated display parameters.
The Enhanced XA IOD provides an exact acquisition time for each frame.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.2-1. Enhanced X-Ray Angiographic Image IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Image |
XA/XRF Multi-frame Presentation |
C.8.19.7 |
Specifies the groups of frames and their display parameters. |
The usage of this module is recommended to encode the grouping of frames (one or more groups) for display purposes and the related parameters for each group.
Table FFF.2.2-2. XA/XRF Multi-frame Presentation Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Preferred Playback Sequencing |
(0018,1244) |
Specifies the direction of the playback. |
Frame Display Sequence |
(0008,9458) |
Specifies the details on how frames are grouped for display purposes. |
An example of a 4 position peripheral stepping acquisition with different frame-rates is provided. One group is only 2 Frames (e.g., due to fast contrast bolus) and will be skipped for display purposes.
The whole image is reviewed in looping mode:
The first group, from frames 1 to 17, is to be reviewed at 4 frames per second;
The second group, from frames 18 to 25, is to be reviewed at 2 frames per second;
The third group, of frames 26 and 27, is not to be displayed;
The fourth group, from frames 28 to 36, is to be reviewed at 1.5 frames per second.
The encoded values of the key attributes of this example are shown in Figure FFF.2.2-1.
This section provides information on the encoding of the density and geometry characteristics of the stored pixel data and the ways to display it.
The image acquisition may be performed with a variety of settings on the detector image pre-processing component that modifies the way the gray levels are stored in the pixel data.
In particular, it may impact the relationship between the X-Ray intensity and the gray level stored (e.g., non-linear function), as well as the geometry of the X-Ray beam (e.g., pincushion distortion).
Based on the characteristics of the stored pixel data, the acquisition system determines automatically an optimal way to display the pixel data on a frame-by-frame basis, which is expected to be applied by the viewing applications.
The XA SOP Class encodes the VOI settings to be common to all the frames of the image. It also restricts the Photometric Interpretation (0028,0004) to MONOCHROME2.
The Enhanced XA SOP Class encodes per-frame VOI settings. Additionally it allows the Photometric Interpretation (0028,0004) to be MONOCHROME1 in order to display low pixel values in white while using window width and window center VOI. Other characteristics and settings can be defined, such as:
Relationship between X-Ray intensity and the pixel value stored;
Edge Enhancement filter strength;
Geometrical properties.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.3-1. Enhanced X-Ray Angiographic Image IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Image |
Enhanced XA/XRF Image |
C.8.19.2 |
Specifies the sign of the slope of the VOI transformation to be applied during display. |
XA/XRF Multi-frame Presentation |
C.8.19.7 |
Specifies the subtractive mode and the edge enhancement filter characteristics to be applied during display. |
Table FFF.2.3-2. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
Frame VOI LUT |
C.7.6.16.2.10 |
Specifies the VOI transformation to be applied during display. |
Pixel Intensity Relationship LUT |
C.7.6.16.2.13 |
Specifies the different LUTs to transform the stored pixel values to a given function of the X-Ray intensity. |
XA/XRF Frame Pixel Data Properties |
C.8.19.6.4 |
Specifies geometrical characteristics of the pixel data. |
The usage of this module is recommended to specify the sign of the slope of the VOI transformation to be applied during display of the multi-frame image.
Table FFF.2.3-3. Enhanced XA/XRF Image Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Photometric Interpretation |
(0028,0004) |
The value MONOCHROME1 indicates negative slope (i.e., minimum pixel value is intended to be displayed as white), and the value MONOCHROME2 indicates positive slope (i.e., minimum pixel value is intended to be displayed as black). |
Presentation LUT Shape |
(2050,0020) |
The values IDENTITY and INVERSE are applicable. |
The usage of this module is recommended to specify some presentation settings:
Whether the viewing mode is subtracted or not by using the Recommended Viewing Mode (0028,1090), and.
The recommended edge enhancement filter as a percentage of subjective sensitivity by using the Display Filter Percentage (0028,9411).
The recommended filter percentage does not guaranty a full consistency of the image presentation across applications, rather gives an indication of the user sensitivity to such filtering to be applied consistently. To optimize the consistency of the filtering perception, the applications sharing the same images should be customized to calibrate the highest filtering (i.e., 100%) to similar perception by the users. Setting the application to the lowest filtering (i.e., 0%) means that no filter is applied at all.
The usage of this macro is recommended to specify the windowing to be applied to the pixel data in native mode, i.e., non-subtracted.
The usage of this macro is recommended to enable the applications to get the values of the stored pixel data back to a linear relationship with the X-Ray intensity.
When the value of Pixel Intensity Relationship (0028,1040) equals LOG, a LUT to get back to linear relationship (TO_LINEAR) is present to allow applications to handle linear pixel data.
Other LUTs can be added, for instance to transform to logarithmic relationship for subtraction (TO_LOG) in case the relationship of the stored pixel data is linear. Other LUTs with manufacturer-defined relationships are also allowed.
The LUTs of this macro are not used for the standard display pipeline.
The usage of this macro is recommended to specify some properties of the values of the stored pixel data with respect to the X-Ray intensity (i.e., gray level properties) and with respect to the geometry of the detector (i.e., pixel geometrical properties).
In this example, two different systems perform an X-Ray Acquisition of the coronary arteries injected with radio-opaque contrast agent.
The system A is equipped with a digital detector, and stores the pixel data with the lower level corresponding to the lower X-Ray intensity. Then the user creates two instances: one to display the injected vessels as black, and other to display the injected vessels as white.
The system B is equipped with an image intensifier configured to store the pixel data with the lower level corresponding to the higher X-Ray intensity. Then the user creates two instances: one to display the injected vessels as black, and other to display the injected vessels as white.
The figure below illustrates, for the two systems, the gray levels of the injected vessels on both the stored pixel data and the displayed pixels, which depend on the value of the attributes Pixel Intensity Relationship Sign (0028,1041), Photometric Interpretation (0028,0004), and Presentation LUT Shape (2050,0020).
This section provides information on the usage of attributes to encode an image acquisition in subtracted display mode.
A straightforward DSA acquisition is performed. The first few frames do not contain contrast, then the rest of frames contain contrast. An "averaged mask" may be selected to average some of the first frames without contrast.
A peripheral stepping DSA acquisition is performed. The acquisition is running in N steps and is timed to perform a mask run (e.g., from feet to abdomen) and then perform contrast runs at the positions of each mask, as triggered by the user.
One or more ranges of contrast frames will be used for subtraction from the mask for loop display. During the display, some ranges are to be fully subtracted, some others may be partially subtracted allowing a certain degree of visibility of the anatomical background visible on the mask, and finally some ranges are to be displayed un-subtracted.
The Enhanced XA SOP Class allows the encoding of the mask attributes similar to what the XA SOP Class provides.
The Enhanced XA SOP Class allows defining of specific display settings to be applied to a subset of frames, for instance the recommended viewing mode and the degree of visibility of the mask.
This section provides detailed recommendations of the key attributes to address this particular scenario.
This module is used to specify the subtraction parameters. The number of items depends on the number of Subtractions to be encoded. Typically, in case of AVG_SUB, the number of items is at least the number of ranges of contrast frames to be subtracted from a different mask.
Table FFF.2.3-5. Mask Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Recommended Viewing Mode |
(0028,1090) |
Recommended in this scenario, a value of "SUB" is used in this case. |
Mask Subtraction Sequence |
(0028,6100) |
Recommended in this scenario. Items can be used to specify:
|
The frame ranges of this module typically include all the masks and contrast frames defined in the Mask Module, and their presentation settings are consistent with the Mask Module definitions.
The mask frames are typically displayed non-subtracted, i.e., Recommended Viewing Mode (0028,1090) equals NAT.
If there is a frame range without mask association, the value "NAT" is used for Recommended Viewing Mode (0028,1090) in the item of the Frame Display Sequence (0008,9458) of that frame range.
In case where Recommended Viewing Mode (0028,1090) equals "NAT", the display is expected to be un-subtracted even if the Recommended Viewing Mode (0028,1090) of the Mask module equals "SUB".
The user performs an X-Ray acquisition in three steps:
First step of 5 frames for mask acquisition, without contrast agent injection;
Second step of 20 frames to assess the arterial phase, with contrast agent injection, to be subtracted to the average of the 5 mask frames acquired in the first phase;
Third step of 10 frames to assess the venous phase, without further contrast agent injection, to be subtracted to a new mask related to that phase and with a 20% of mask visibility.
In the three steps, the system automatically identifies the mask frame(s) to be associated with the contrast frames.
The encoded values of the key attributes of this example are shown in Figure FFF.2.3-2.
This section provides information on the attribute encoding for use with image acquisitions that require subtracted display modes with multiple pixel shift ranges e.g., multiple subtracted views on a DSA acquisition.
When performing DSA acquisitions, the acquisition system may choose a default subtraction pixel-shift to allow review of the whole multi-frame, as acquired.
With advanced post-processing function the medical user may add further subtraction pixel-shifts to carve out certain details or improve contrast bolus visualization of a part of the anatomy that suffered from different movement during the acquisition.
The Mask Module is used to encode the various subtractions applicable to a multi-frame image.
The Enhanced XA IOD allows creating groups of mask-contrast pairs in the Mask Module, each group identified by a unique Subtraction Item ID within the multi-frame image.
The Enhanced XA IOD, with per frame macro encoding, supports multiple and different pixel-shift values per frame, each pixel-shift value is related to a given Subtraction Item ID.
It has to be assured that all the frames in the scope of a Subtraction Item ID have the pixel-shift values defined under that Subtraction Item ID.
In case a frame does not belong to any Subtraction Item ID, that frame does not necessarily have a pixel shift value encoded.
This section provides detailed recommendations of the key attributes to address this particular scenario. The usage of the "Frame Pixel Shift" macro in a 'per frame' context is recommended. Only the usage of Mask Module and the Frame Pixel Shift Macro is further detailed.
Table FFF.2.3-6. Enhanced X-Ray Angiographic Image IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Image |
Mask |
C.7.6.10 |
Specifies the groups of mask-contrast pairs identified by a Subtraction Item ID. |
Table FFF.2.3-7. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
Frame Pixel Shift |
C.7.6.16.2.14 |
Specifies the pixel shift associated with the Subtraction IDs. |
This module is recommended to specify the subtraction parameters. The number of items depends on the number of Subtractions to be applied (see Section FFF.2.3.2).
Table FFF.2.3-8. Mask Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Recommended Viewing Mode |
(0028,1090) |
Recommended in this scenario, a value of "SUB" is used in this case. |
Mask Subtraction Sequence |
(0028,6100) |
Recommended in this scenario. Item can be used to specify:
|
The usage in this scenario is on a "per frame" context to allow individual pixel shift factors for each Subtraction Item ID.
The Subtraction Item ID specified in the Mask Subtraction Sequence (0028,6100) as well as in the Frame Pixel Shift Sequence (0028,9415) allows creating a relationship between the subtraction (mask and contrast frames) and a corresponding set of pixel shift values.
The Pixel Shift specified for a given frame in the Frame Pixel Shift Macro is the shift to be applied when this frame is subtracted to its associated mask for the given Subtraction Item ID.
Not all frames may have the same number of items in the Frame Pixel Shift Macro, but all frames that are in the scope of a Subtraction Item ID and identified as "contrast" frames in the Mask module are recommended to have a Frame Pixel Shift Sequence item with the related Subtraction Item ID.
Table FFF.2.3-9. Frame Pixel Shift Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Frame Pixel Shift Sequence |
(0008,9415) |
Recommended in this scenario. The number of items may differ for each frame. |
In this example, the pixel shift -0.3\2.0 is applied to the frames 2 and 3 when they are subtracted to the mask frame 1 as defined in the Mask Subtraction Sequence.
The usage in a per-frame context is expected in a typical clinical scenario where the shift between the mask and the contrast frames is not constant across the frames of the multi-frame image to compensate for patient/organ movement.
The encoded values of the key attributes of this example are shown in Figure FFF.2.3-4.
The usage in a per-frame context is also appropriate to specify more than one set of shifts in case of more than one region of interest suffered from patient/organ movement independently, like in case of the two legs imaged simultaneously.
In this example, two Subtraction Item IDs are defined in the Mask Subtraction Sequence.
The encoded values of the key attributes of this example are shown in Figure FFF.2.3-5.
This section provides information on the encoding of the projection pixel size calibration and the underlying geometry.
The user wants to measure the size of objects in the patient with a default system calibration based on the acquisition geometry and the default distance from the table to the object. In order to have more accurate measurements than this default calibration, the user may provide information of the distance from the table to the object to be measured.
The image is stored in an archive system and retrieved by a second user who wants to re-use the calibration and needs to know which object this calibration applies to.
This second user may need to re-calibrate based on another object at a different geometry.
In conic projection imaging, the pixel size in the patient is not constant. If a value of Pixel Spacing (0028,0030) is provided, it is best appropriate at a given distance from the X-Ray source to the object of interest in the patient (patient plane). It is less exact for other objects at other distances.
In addition, the distance from the X-Ray source to the object of interest may change per frame in case of gantry or table motion. In this case the Enhanced XA SOP Class allows the pixel size in the patient to be defined per-frame.
A macro provides a compound set of all relevant attributes.
The value "Table to Object Height" can be used for individual patient plane definition.
Automatic isocenter calibration method is supported.
Values of gantry and table positions are provided to complete all necessary attributes for a later re-calibration.
This section provides detailed recommendations of the key attributes to address this particular scenario. See Section C.8.19.6.9.1 in PS3.3 for detailed description of the attributes involved in the calculation of the calibration.
Table FFF.2.4-1. Enhanced X-Ray Angiographic Image IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Image |
XA/XRF Acquisition |
C.8.19.3 |
Specifies system characteristics relevant for this scenario. |
Table FFF.2.4-2. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
XA/XRF Frame Pixel Data Properties |
C.8.19.6.4 |
Specifies the pixel spacing on the receptor plane. |
X-Ray Projection Pixel Calibration |
C.8.19.6.9 |
Specifies the calibration-specific attributes. |
X-Ray Geometry |
C.8.19.6.14 |
Specifies the distances of the conic projection. |
In order to check if a calibration is appropriate, certain values have to be set in the XA/XRF Acquisition Module.
Table FFF.2.4-3. XA/XRF Acquisition Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
X-Ray Receptor Type |
(0018,9420) |
Recommended in this scenario. The values IMG_INTENSIFIER or DIGITAL_DETECTOR can provide information about exactness of the image plane. |
Positioner Type |
(0018,1508) |
Recommended in this scenario. The value of CARM is typically expected for equipment providing geometry information required for calibration. |
C-arm Positioner Tabletop Relationship |
(0018,9474) |
A value of YES is recommended in this scenario, to allow use of related information for calibration because table and gantry are geometrically aligned. |
This macro is recommended to provide the Pixel Spacing in the receptor plane. Typically the Image Pixel Spacing is identical for all frames. Future acquisition system techniques may result in per frame individual values.
Table FFF.2.4-4. XA/XRF Frame Pixel Data Properties Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Frame Pixel Data Properties Sequence |
(0028,9443) |
|
>Imager Pixel Spacing |
(0018,1164) |
Recommended for this scenario, regardless the type of receptor. |
This macro contains the core inputs and results of calibration.
When there is no movement of the gantry and table, the macro is typically used in shared functional group context.
The attribute Beam Angle (0018,9449) is supplementary for the purpose of calibration; it is derived from the Primary and Secondary Positioner Angles but is not intended to replace them as they provide information for other purposes.
Table FFF.2.4-5. X-Ray Projection Pixel Calibration Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Projection Pixel Calibration Sequence |
(0018,9401) |
|
>Distance Object to Table Top |
(0018,9403) |
Recommended in this scenario. |
>Object Pixel Spacing in Center of Beam |
(0018,9404) |
Recommended in this scenario. The value pair corresponds to the patient plane defined by the other parameters in this macro. |
>Table Height |
(0018,1130) |
Recommended in this scenario. |
>Beam Angle |
(0018,9449) |
Recommended in this scenario. |
The user performs an X-Ray acquisition with movement of the positioner during the acquisition. The patient is in Head First Supine position. During the review of the multi-frame image, a measurement of the object of interest in the frame "i" needs to be performed, which requires the calculation of the pixel spacing at the object location for that frame.
For the frame "i", the Positioner Primary Angle is -30.0 degrees, and the Positioner Secondary Angle is 20.0 degrees. According to the definition of the positioner angles and given the patient position, the Beam Angle is calculated as follows:
Beam Angle = arcos( |cos(-30.0) | * |cos(20.0) | ) = 35.53 degrees
The value of the other attributes defining the geometry of the acquisition for the frame "i" are the following:
ISO = 750 mm SID = 983 mm TH = 187 mm
ΔPx (Imager Pixel Spacing) = 0.2 mm/pix
The user provides, via the application interface, an estimated value of the distance from the object of interest to the tabletop: TO = 180 mm. This value can be encoded in the attribute Distance Object to Table Top (0018,9403) of the Projection Pixel Calibration Sequence (0018,9401) for further usage.
This results in an SOD of 741.4 mm (according to the equation SOD = 750mm - [(187mm-180mm) / cos(35.53°) ] ), and in a magnification ratio of SID/SOD of 1.32587.
The resulting pixel spacing at the object location and related to the center of the X-Ray beam is calculated as ΔPx * SOD / SID = 0.150844 mm/pix. This value can be encoded in the attribute Object Pixel Spacing in Center of Beam (0018,9404) of the Projection Pixel Calibration Sequence (0018,9401) for further usage.
The encoded values of the key attributes of this example are shown in Figure FFF.2.4-1.
This section provides information on the encoding of the derivation process and the characteristics of the stored pixel data.
An acquisition system performs several processing steps on an original image, and then it creates a derived image with the processed pixel data.
A viewing application applies post-processing algorithms to that derived image, e.g., measurements, segmentation etc. This application needs to know what kind of post-processing can or cannot be applied depending on the characteristics of the derived image.
The XA SOP Class does not encode any specific attribute values to characterize the type of derivation.
The Enhanced XA SOP Class encodes defined terms for processing applied to the Pixel Data, and allows getting back to linear relationship between pixel values and X-Ray intensity. Viewing applications can consistently interpret the stored pixel data and enable/disable applications like edge detection algorithms, subtraction, filtering, etc.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.4-6. Enhanced X-Ray Angiographic Image IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Image |
Enhanced XA/XRF Image |
C.8.19.2 |
Specifies the image type: ORIGINAL or DERIVED. |
Table FFF.2.4-7. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
Derivation Image |
C.7.6.16.2.6 |
Specifies the different derivation steps (including the latest step) that led to this instance. |
Pixel Intensity Relationship LUT |
C.7.6.16.2.13 |
Specifies the relationship between the stored pixel data values and the X-Ray intensity of the resulting derived instance. |
XA/XRF Frame Characteristics |
C.8.19.6.1 |
Specifies the latest derivation step that led to this instance. |
XA/XRF Frame Pixel Data Properties |
C.8.19.6.4 |
Specifies the characteristics of the derived pixel data, both geometric and densitometric. |
The usage of this module is recommended to specify the image type.
Table FFF.2.4-8. Enhanced XA/XRF Image Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Image Type |
(0008,0008) |
The first value is DERIVED in this scenario. |
The usage of this macro is recommended to encode the information of the different derivation processes and steps, as well as the source SOP instance(s) when the image or frame are derived from other SOP Instance(s).
Table FFF.2.4-9. Derivation Image Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Derivation Image Sequence |
(0008,9124) |
Contains one item per derivation process that led to this SOP Instance. |
>Derivation Description |
(0008,2111) |
Free text description of this derivation process, typically for display purposes. |
>Derivation Code Sequence |
(0008,9215) |
Contains as many items as derivation steps in this derivation process. |
>Source Image Sequence |
(0008,2112) |
Contains one item per source SOP Instance used in this derivation process. |
If this image is not derived from source SOP Instances, the Derivation Image macro is not present, and the XA/XRF Frame Characteristics macro is used instead.
The usage of this macro is recommended to enable the applications to get the pixel values back to a linear relationship with the X-Ray intensity.
If readers of the image do not recognize the Pixel Intensity Relationship value, readers can use the value "OTHER" as default.
The number of bits in the LUT Data attribute (0028,3006) may be different from the value of Bits Stored attribute (0028,0101).
The usage of this macro is recommended to specify the derivation characteristics
Table FFF.2.4-10. XA/XRF Frame Characteristics Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
XA/XRF Frame Characteristics Sequence |
(0018,9412) |
|
>Derivation Description |
(0008,2111) |
Contains the description of the latest derivation process. |
>Derivation Code Sequence |
(0008,9215) |
Contains as many items as derivation steps in this derivation process. |
>Acquisition Device Processing Description |
(0018,1400) |
Specifies the derivation made at the acquisition system. |
>Acquisition Device Processing Code |
(0018,1401) |
Specifies the derivation made at the acquisition system. |
If the image is derived from one or more SOP Instances, the XA/XRF Frame Characteristics Sequence always contains the same values as the last item of the Derivation Image Sequence.
If the image is derived but not from other SOP Instances, it means that the derivation was performed on the Acquisition system, and the Acquisition Device Processing Description (0018,1400) and the Acquisition Device Processing Code (0018,1401) contain the information of that derivation.
An image derived from a derived image will change the Derivation Description but not the Acquisition Device Processing Description.
The usage of this macro is recommended to specify the type of processing applied to the stored pixel data of the derived frames.
Table FFF.2.4-11. XA/XRF Frame Pixel Data Properties Macro Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
Frame Pixel Data Properties Sequence |
(0028,9443) |
Recommended in this scenario. |
>Frame Type |
(0008,9007) |
The first value is DERIVED in this scenario |
>Image Processing Applied |
(0028,9446) |
In case of derivation from a derived image, this attribute contains a concatenation of the previous values plus the new value(s) of the latest derivation process. |
In this example, the acquisition modality creates two instances of the Enhanced XA object: the instance "A" with mask frames and the instance "B" with contrast frames. A temporal filtering has been applied by the modality before the creation of the instances.
The workstation 1 performs a digital subtraction of the frames of the instance "B" by using the frames of the instance "A" as mask, then the resulting subtracted frames are stored in a new instance "C".
Finally the workstation 2 processes the instance "C" by applying a zoom and edge enhancement, and the resulting processed frames are stored in a new instance "D".
Figure FFF.2.4-3 shows the values of the attributes of the instance "D" in the corresponding modules and macros related to derivation information. The Source Image Sequence (0008,2112) of the Derivation Image Sequence (0008,9124) does not contain the attribute Referenced Frame Number (0008,1160) because all the frames of the source images are used to generate the derived images.
In this example, the acquisition modality creates the instance "A" of the Enhanced XA object with 14 bits stored where the relationship between the pixel intensity and the X-Ray intensity is linear.
A workstation reads the instance "A", transforms the pixel values of the stored pixel data by applying a square root function and stores the resulting frames on the instance "B" with 8 bits stored.
The following figure shows the values of the attributes of the instance "B" in the corresponding modules and macros related to derivation information.
Note that the Derivation Code Sequence (0008,9215) is present when the Derivation Image Sequence (0008,9124) includes one or more items, even if the derivation code is not defined in the CID 7203 “Image Derivation”.
The Pixel Intensity Relationship LUT Sequence (0028,9422) contains a LUT with the function "TO_LINEAR" to allow the calculation of the gray level intensity to be linear to the X-Ray intensity. Since the instance "B" has 8 bits stored, this LUT contains 256 entries (starting the mapping at pixel value 0) and is encoded in 16 bits.
The value of the Pixel Intensity Relationship (0028,1040) in the Frame Pixel Data Properties Sequence (0028,9443) could be "OTHER" as it is described in the defined terms. However, a more explicit term like "SQRT" is also allowed and will have the same effect in the reading application.
In the case of a modification of the pixel intensity relationship of an image, the value of the attribute Image Processing Applied (0028,9446) in the Frame Pixel Data Properties Sequence (0028,9443) can be "NONE" in order to indicate to the reading applications that there was no image processing applied to the original image that could modify the spatial or temporal characteristics of the pixels.
This section provides information on the encoding of the acquisition geometry in a fixed reference system.
The operator identifies the position of an object of interest projected on the stored pixel data of an image A, and estimates the magnification of the conic projection by a calibration process.
The operator wants to know the position of the projection of such object of interest on a second image B acquired under different geometry, assuming that the patient does not move between image A and image B (i.e., the images share the same frame of reference).
The XA SOP Class encodes the information in a patient-related coordinate system.
The Enhanced XA SOP Class additionally encodes the geometry of the acquisition system with respect to a fixed reference system defined by the manufacturer, so-called Isocenter reference system. Therefore, it allows encoding the absolute position of an object of interest and to track the projection of such object across the different images acquired under different geometry.
This section provides detailed recommendations of the key attributes to address this particular scenario.
Table FFF.2.5-1. Enhanced X-Ray Angiographic Image IOD Modules
IE |
Module |
PS3.3 Reference |
Usage |
---|---|---|---|
Image |
Image Pixel |
C.7.6.3 |
Specifies the dimension of the pixel array of the frames. |
XA/XRF Acquisition |
C.8.19.3 |
Describes some characteristics of the acquisition system that enables this scenario. |
|
X-Ray Detector |
C.8.19.5 |
Specifies the type and characteristics of the image detector. |
Table FFF.2.5-2. Enhanced XA Image Functional Group Macros
Functional Group Macro |
PS3.3 Reference |
Usage |
---|---|---|
X-Ray Field of View |
C.8.19.6.2 |
Specifies the dimension of the Field of View as well as the flip and rotation transformations. |
X-Ray Isocenter Reference System |
C.8.19.6.13 |
Specifies the acquisition geometry in a fixed reference system. |
X-Ray Geometry |
C.8.19.6.14 |
Specifies the distances of the conic projection. |
XA/XRF Frame Pixel Data Properties |
C.8.19.6.4 |
Specifies the dimensions of the pixels at the image reception plane. |
The usage of this module is recommended to specify the number of rows and columns of the Pixel Data, as well as the aspect ratio.
The usage of this module is recommended to give the necessary conditions to enable the calculations of this scenario.
Table FFF.2.5-3. XA/XRF Acquisition Module Recommendations
Attribute Name |
Tag |
Comment |
---|---|---|
X-Ray Receptor Type |
(0018,9420) |
DIGITAL_DETECTOR is used in this scenario. |
Positioner Type |
(0018,1508) |
CARM is used in this scenario. |
C-arm Positioner Tabletop Relationship |
(0018,9474) |
YES is necessary in this scenario. |
In case of X-Ray Receptor Type (0018,9420) equals "IMG_INTENSIFIER", there are some limitations that prevent the calculations described on this scenario:
The position of the projection of the isocenter on the intensifier active area is undefined;
The Field of View Origin (0018,7030) cannot be related to the physical area of the receptor because the Intensifier TLHC is undefined.
As a consequence, in case of image intensifier it is impossible to relate the position of the pixels of the stored area to the isocenter reference system.
In case of X-Ray Receptor Type (0018,9420) equals "DIGITAL_DETECTOR" the usage of this module is recommended to specify the type and characteristics of the image detector.
The usage of this macro is recommended to specify the characteristics of the field of view.
The field of view characteristics may change per-frame across the multi-frame image.
The usage of this macro is recommended to specify the fixed reference system of the acquisition geometry.
The usage of this macro is recommended to specify the distances between the X-Ray source, isocenter and X-Ray detector.
In this example, the operator identifies the position (i, j) of an object of interest projected on the stored pixel data of an image A, and estimates the magnification of the conic projection by a calibration process.
The operator wants to know the position of the projection of such object of interest on a second image B acquired under different geometry.
The attributes that define the geometry of both images A and B are described in the following figure:
The following steps describe the process to calculate the position (i, j)B of the projection of the object of interest in the Pixel Data of the image B, assuming that (i, j)A is known and is the offset of the projection of the object of interest from the TLHC of the Pixel Data of the image A, measured in pixels of the Pixel Data matrix as a column offset "i" followed by a row offset "j". TLHC is defined as (0,0).
Step 1: Calculate the point (i, j)A in FOV coordinates of the image A.
Step 2: Calculate the point (i, j)A in physical detector coordinates of the image A.
Step 3: Calculate the point (Pu, Pv)A in positioner coordinates of the image A.
Step 4: Calculate the point (PXp, PYp, PZp)A in positioner coordinates of the image A.
Step 5: Calculate the point (PX, PY, PZ)A in Isocenter coordinates of the image A.
Step 6: Calculate the point (PXt, PYt, PZt)A in Table coordinates of the image A.
Step 7: Calculate the point (PXt, PYt, PZt)B in Table coordinates in mm of the image B.
Step 8: Calculate the point (PX, PY, PZ)B in Isocenter coordinates in mm of the image B.
Step 9: Calculate the point (PXp, PYp, PZp)B in positioner coordinates of the image B.
Step 10: Calculate the point (Pu, Pv)B in positioner coordinates of the image B.
Step 11: Calculate the point (i, j)B in physical detector coordinates of the image B.
Step 12: Calculate the point (i, j)B in FOV coordinates of the image B.
Step 13: Calculate the point (i, j)B in Pixel Data of the image B.
In this example let's assume:
(i, j)A = (310,122) pixels
Magnification ratio = 1.3
Step 1 : Image A: Point (i, j)A in FOV coordinates
In this step, the FOV coordinates are calculated by taking into account the FOV rotation and Horizontal Flip applied to the FOV matrix when the Pixel Data were created:
1.1: Horizontal Flip : YES
new i = (columns -1) - i = 850 - 1 - 310 = 539
new j = j = 122
1.2: Image Rotation : 90 (clockwise)
new i = j = 122
new j = (columns -1) - i = 850 - 1 - 539 = 310
(i, j)A = (122, 310) in stored pixel data.
Step 2: Image A: Point (i, j)A in physical detector coordinates
In this step, the physical detector coordinates are calculated by taking into account the FOV origin and the ratio between Imager Pixel Spacing and Detector Element Spacing:
Di = Imager Pixel Spacing (column) = 0.2 mm
Dj = Imager Pixel Spacing (row) = 0.2 mm
Didet = Detector Element Spacing between two adjacent columns = 0.2 mm
Djdet = Detector Element Spacing between two adjacent rows = 0.2 mm
Zoom Factor (column) = Di / Didet = 1.0
Zoom Factor (row) = Dj / Djdet = 1.0
FOV Origin (column) = FOVidet = 600.0
FOV Origin (row) = FOVjdet = 600.0
new i = FOVidet + (i + (1 - Didet / Di) / 2) * Dj / Djdet = 600 + 122 * 1.0 = 722
new j = FOVjdet + (j + (1 - Djdet / Dj) / 2) * Di / Didet = 600 + 310 * 1.0 = 910
(i, j)A = (722, 910) in detector elements.
Step 3: Image A: Point ( Pu, Pv)A in positioner coordinates
In this step, the (Pu, Pv)A coordinates in mm are calculated from (i, j)A by taking into account the projection of the Isocenter in physical detector coordinates, and the Detector Element Spacing:
ISO_Pidet = Position of Isocenter Projection (column) = 1024.5
ISO_Pjdet = Position of Isocenter Projection (row) = 1024.5
Didet = Detector Element Spacing between two adjacent columns = 0.2 mm
Djdet = Detector Element Spacing between two adjacent rows = 0.2 mm
Pu = (i - ISO_Pidet) * Didet = (722 - 1024.5) * 0.2 = -60.5 mm
Pv = (ISO_Pjdet - j) * Djdet = (1024.5 - 910) * 0.2 = 22.9 mm
( Pu, Pv)A = (-60.5, 22.9) in mm.
Step 4: Image A: Point (PXp, PYp, PZp)A in positioner coordinates
In this step, the positioner coordinates (PXp, PYp, PZp)A are calculated from (Pu, Pv)A by taking into account the magnification ratio, the Distance Source to Detector and the Distance Source to Isocenter:
SID = Distance Source to Detector = 1300 mm
ISO = Distance Source to Isocenter = 780 mm
Magnification ratio = SID / (ISO - P Yp ) = 1.3
P Yp = ISO - SID / 1.3 = 780 - 1300/1.3 = -220 mm
P Xp = Pu / Magnification ratio = -60.5 / 1.3 = -46.54 mm
P Zp = Pv / Magnification ratio = 22.9 / 1.3 = 17.62 mm
(PXp, PYp, PZp)A = (-46.54, -220, 17.62) in mm.
Step 5: Image A: Point (PX, PY, PZ)A in Isocenter coordinates
In this step, the isocenter coordinates (PX, PY, PZ)A are calculated from the positioner coordinates (PXp, PYp, PZp)A by taking into account the positioner angles of the image A in the Isocenter coordinate system:
Ap1 = Positioner Isocenter Primary Angle = 60.0 deg
Ap2 = Positioner Isocenter Secondary Angle = 20.0 deg
Ap3 = Positioner Isocenter Detector Rotation Angle = 0.0 deg
(PX, PY, PZ)T= (R2 ·R1)T·(R3 T·(PXp, PYp, PZp)T)
(PX, PY, PZ)A = (150.55, -65.41, 91.80) in mm.
Step 6: Image A: Point (PXt, PYt, PZt)A in Table coordinates
In this step, the table coordinates (PXt, PYt, PZt)A are calculated from the isocenter coordinates (PX, PY, PZ)A by taking into account the table position and angles of the image A in the Isocenter coordinate system:
Tx =Table X Position to Isocenter = 10.0 mm
Ty =Table Y Position to Isocenter = 30.0 mm
Tz =Table Z Position to Isocenter = 100.0 mm
At1 = Table Horizontal Rotation Angle = -10.0 deg
At2 = Table Head Tilt Angle = 0.0 deg
At3 = Table Cradle Tilt Angle = 0.0 deg
(PXt, PYt, PZt)T= (R3 · R2 · R1) · ((PX, PY, PZ)T- (TX, TY, TZ)T)
(PXt, PYt, PZt)A = (136.99, -95.41, -32.48) in mm.
Step 7: Image B: Point (PXt, PYt, PZt)B in Table coordinates
In this step, the table has moved from image A to image B. The table coordinates of the object of interest are the same on image A and image B because it is assumed that the patient is fixed on the table.
(PXt, PYt, PZt)B = (136.99, -95.41, -32.48) in mm.
Step 8: Image B: Point (PX, PY, PZ)B in Isocenter coordinates
In this step, the isocenter coordinates (PX, PY, PZ)B are calculated from the table coordinates (PXt, PYt, PZt)B by taking into account the table position and angles of the image B in the Isocenter coordinate system:
Tx =Table X Position to Isocenter = 20.0 mm
Ty =Table Y Position to Isocenter = 100.0 mm
Tz =Table Z Position to Isocenter = 0.0 mm
At1 = Table Horizontal Rotation Angle = 0.0 deg
At2 = Table Head Tilt Angle = 10.0 deg
At3 = Table Cradle Tilt Angle = 0.0 deg
(PX, PY, PZ)T= (R3 · R2 · R1)T· (PXt, PYt, PZt)T+ (TX, TY, TZ)T
(PX, PY, PZ)B = (156.99, -12.11, -48.55) in mm.
Step 9: Image B: Point (PXp, PYp, PZp)B in positioner coordinates
In this step, the positioner coordinates (PXp, PYp, PZp)B are calculated from the isocenter coordinates (PX, PY, PZ)B by taking into account the positioner angles of the image B in the Isocenter coordinate system:
Ap1 = Positioner Isocenter Primary Angle = -30.0 deg
Ap2 = Positioner Isocenter Secondary Angle = 0.0 deg
Ap3 = Positioner Isocenter Detector Rotation Angle = 0.0 deg
(PXp, PYp, PZp)T= R3 · ((R2 · R1) · (PX, PY, PZ)T)
(PXp, PYp, PZp)B = (142.01, 68.00, -48.55) in mm.
Step 10: Image B: Point ( Pu, Pv)B in positioner coordinates
In this step, the (Pu, Pv)B coordinates in mm are calculated from the positioner coordinates (PXp, PYp, PZp)B by taking into account the Distance Source to Detector and the Distance Source to Isocenter of the image B:
SID = Distance Source to Detector = 1000 mm
ISO = Distance Source to Isocenter = 800 mm
Magnification ratio = SID / (ISO - P Yp ) = 1200/(800-68) = 1.366
Pu = P Xp * Magnification ratio = 142.01 * 1.64 = 194.00 mm
Pv = P Z p * Magnification ratio = -48.55 * 1.64 = -66.33 mm
( Pu, Pv)B = (194.00, -66.33) in mm.
Step 11: Image B: Point (i, j)B in physical detector coordinates
In this step, the physical detector coordinates (i, j)B are calculated from the positioner coordinates ( Pu, Pv)B by taking into account the projection of the Isocenter in physical detector coordinates, and the Detector Element Spacing of the image B:
ISO_Pidet = Position of Isocenter Projection (column) = 1024.5
ISO_Pjdet = Position of Isocenter Projection (row) = 1024.5
Didet =Detector Element Spacing between two adjacent columns = 0.2
Djdet =Detector Element Spacing between two adjacent rows = 0.2
i = ISO_Pidet + Pu / Didet = 1024.5 + 194.00 / 0.2 = 1994.5
j = ISO_Pidet - Pv / Didet = 1024.5 - (-66.33) / 0.2 = 1356.2
(i, j)B = (1994.5, 1356.2) in detector elements.
Step 12 : Image B: Point (i, j)B in FOV coordinates
In this step, the FOV coordinates are calculated from the physical detector coordinates by taking into account the FOV origin and the ratio between Imager Pixel Spacing and Detector Element Spacing of the image B:
Di = Imager Pixel Spacing (column) = 0.4 mm
Dj = Imager Pixel Spacing (row) = 0.4 mm
Didet = Detector Element Spacing between two adjacent columns = 0.2 mm
Djdet = Detector Element Spacing between two adjacent rows = 0.2 mm
Zoom Factor (column) = Di / Didet = 2.0
Zoom Factor (row) = Dj / Djdet = 2.0
FOV Origin (column) = FOVidet = 25.0
FOV Origin (row) = FOVjdet = 25.0
new i = (i - FOVidet).Didet / Di - (1 - Didet / Di) / 2 = (1994.5 - 25.0) / 2.0 - 0.25 = 984.5
new j = (j - FOVjdet).Djdet / Dj - (1 - Djdet / Dj) / 2 = (1356.2 - 25.0) / 2.0 - 0.25 = 665.35
(i, j)B = (984.50, 665.35) in stored pixel data.
Step 13 : Image B: Point (i, j)B in Pixel Data
In this step, the position (i, j)B of the projection of the object of interest in the Pixel Data of the image B is calculated from the FOV coordinates by taking into account the FOV rotation and Horizontal Flip applied to the FOV matrix when the Pixel Data were created:
1.1: Horizontal Flip : NO
new i = i = 984.50
new j = j = 665.35
1.2: Image Rotation : 180 (clockwise)
new i = (columns -1) - i = 1000 - 1 - 984.50 = 14.50
new j = (rows -1) - j = 1000 - 1 - 665.35 = 333.65
(i, j)B = (14.50, 333.65) in stored pixel data.