Table A.18.3-1—RT DOSE IOD MODULES
|Clinical Trial Subject||C.7.1.3||U|
|Clinical Trial Study||C.7.2.3||U|
|Clinical Trial Series||C.7.3.2||U|
|Frame of Reference||Frame of Reference||C.7.4.1||M|
|Dose||General Image||C.7.6.1||C - Required if dose data contains grid-based doses.|
|Image Plane||C.7.6.2||C - Required if dose data contains grid-based doses.|
|Image Pixel||C.7.6.3||C - Required if dose data contains grid-based doses.|
|Multi-Frame||C.7.6.6||C - Required if dose data contains grid-based doses and pixel data is multi-frame data.|
|Structure Set||C.8.8.5||C - Required if dose data contains dose points or isodose curves|
|ROI Contour||C.8.8.6||C - Required if dose data contains dose points or isodose curves|
|RT Dose ROI||C.8.8.7||C - Required if dose data contains dose points or isodose curves|
|Frame Extraction||C.12.3||C - Required if the SOP Instance was created in response to a Frame-Level retrieve request|
Notes: 1. Within the RT Dose IOD, the RT Dose module supports 2D and 3D dose grids. The Structure Set, ROI Contour and RT Dose ROI modules together support isodose curves and points, and the RT DVH module supports dose-volume histogram data. They are not mutually exclusive: all four representations may be included in a single instance of the object or they may be included in any combination. Product Conformance Statements should clearly state which of these mechanisms is supported and under what conditions.
2. The RT Dose IOD has been defined as a composite IOD, separate from the RT Plan IOD. This has been done for the following reasons:
- to allow for the multiplicity of possible dose calculations using beam models for the same basic plan,
- to avoid undesirable transmission of large amounts of data with the treatment plan, and
- to accommodate the fact that CT Simulation and other “beam geometry” generating devices that use the RT Plan IOD do not have or require access to this data, either for transmission or storage.
3. The Audio Module was previously included in this IOD but has been retired. See PS 3.3 2004.