DICOM PS3.17 2016e - Explanatory Information

MM.2.8 A "Single Frame" Multi-frame Image
Prev | MM.2 Frame Extraction Issues | Next

### MM.2.8 A "Single Frame" Multi-frame Image

The requirement that the newly created image object generated in response to a Frame level retrieve request must be the same as the SOP class will frequently result in the need to create a single frame instance of an object that is more commonly a multi-frame object, but this should not cause any problems with the IOD rules, as all such objects may quite legally have Number of Frames = 1.

However, a single frame may well cause problems for a transfer syntax based on "video" such as those using MPEG-2, MPEG-4 AVC/H.264 or HEVC/H.265, and therefore the SCU when negotiating a C-GET should consider this problem, and include one or more transfer syntaxes suitable for holding single or non-contiguous frames where such a retrieval request is being made.

Prev | Up | Next
MM.2.7 Nuclear Medicine Images | Home | MM.3 Frame Numbers

DICOM PS3.17 2016e - Explanatory Information