7 Persistent Object types

The provisions for some specific object types shall be as defined in this section.

Note: In all cases the categorization depends on the SOP Class of the objects, enabling a client, or application building an HTML page for the client, to determine in advance of the request what the requirements will be.

7.1 Single Frame Image Objects

7.1.1 Objects accessed

In this category are all object instances of SOP classes defined in PS 3.3 that consist of a single image frame, instances of multi-frame SOP Classes that contain only one frame, or object instances that consist of single frame accessed from instances of multi-frame SOP Classes using the "frameNumber" parameter.

7.1.2 MIME type constraints

The Server shall be able to send a response in each of the following MIME types:

If the contentType parameter is not present in the request, the response shall contain an image/jpeg MIME type, if compatible with the ‘Accept’ field of the GET method.

When an image/jpeg MIME type is returned, the image shall be encoded using the JPEG baseline lossy 8 bit Huffman encoded non-hierarchical non-sequential process ISO/IEC 10918.

Note: The choice of image/jpeg as the default for continuous tone images is a consequence of the universal support by Web Clients.

The Server should also support the following MIME types:

The Server may also support other MIME types.

7.2 Multi-Frame Image Objects

7.2.1 Objects included

In this category are all SOP classes defined in PS 3.3 that are multi-frame image objects.

7.2.2 MIME type constraints

The Server shall be able to send a response in the following MIME type:

If the contentType parameter is not present in the request, the response shall contain a application/dicom MIME type.

The Server should also support the following MIME type:

The Server may also support other MIME types.

7.3 Text Objects

7.3.1 Objects included

In this category are all SOP classes defined in PS 3.3 that include the SR Document Content Module.

Note: This includes all SOP Classes that are SR documents, such as narrative text, structured reports, CAD, measurement reports and key object selection documents.

7.3.2 MIME type constraints

The Server shall be able to send a response in each of the following MIME types:

If the contentType parameter is not present in the request, or contains only MIME types that the Server does not support, the response shall contain a text/html MIME type.

It is recommended that the Server also support the following MIME types:

The Server may also support other MIME types.

7.4 Other Objects

7.4.1 Objects included

The category shall include all objects of all SOP classes defined in PS 3.3 that are not included in the categories described in the sections above, and which are considered in PS 3.3 as classes of persistent objects.

7.4.2 MIME type constraints

The Server shall be able to send a response in the following MIME type:

The Server may also support other MIME types.

If the contentType parameter is not present in the request, the response shall contain an application/dicom MIME type.