T.4 Hanging Protocol Storage SOP Class

This Section defines the SCU and SCP behavior for the Hanging Protocol Storage SOP Class. The C-STORE DIMSE-C Service shall be the mechanism used to transfer Hanging Protocol SOP Instances between peer DICOM AEs as described in PS 3.7.

T.4.1 Service Class User

The DICOM AE that claims conformance to this SOP Class as an SCU shall be capable of sending a Hanging Protocol SOP Instance that meets the requirements of the Hanging Protocol IOD. It shall be invoked by the SCU through the use of the DIMSE C-STORE request used in conjunction with this SOP Class.

The SCU shall include a Data Set with the Attributes as defined in the Hanging Protocol IOD in PS 3.3.

The SCU shall recognize the status of the C-STORE service and take appropriate action based on the success or failure of the service. This SOP Class places no further requirements on what the SCU shall do other than that it shall distinguish between successful and failed C-STORE responses. This behavior shall be documented as part of the SOP Class Conformance Statement.

T.4.2 Service Class Provider

The DICOM AE that claims conformance to this SOP Class as an SCP shall receive a Hanging Protocol SOP Instance through the use of the DIMSE C-STORE service used in conjunction with this SOP Class.

The SCP shall store and provide access to all Type 1, Type 2, and Type 3 Attributes defined in the Hanging Protocol IOD, as well as any Standard Extended Attributes (including Private Attributes) included in the SOP Instance. The SCP may, but is not required to validate that the Attributes of the Hanging Protocol SOP Instance meet the requirements of the Hanging Protocol IOD. The SCP shall not modify the values of any Attributes in the Hanging Protocol SOP Instance without assigning a new SOP Instance UID.

If a display device acting as an SCP applies a Hanging Protocol to a set of images, all mandatory Hanging Protocol and presentation intent attributes shall be applied.

The SCP shall return, via the C-STORE response primitive, the Response Status Code applicable to the associated request. By performing this service successfully, the SCP indicates that the Hanging Protocol SOP Instance has been successfully stored. Table T.4-1 shows the response status values. General status code values and fields related to status code values are defined in PS 3.7.

Table T.4-1

C-STORE RESPONSE STATUS VALUES

Service Status Further Meaning Status Codes Related Fields
Failure Refused: Out of Resources A700 (0000,0902)
Error: Data Set Does Not Match SOP Class A900 (0000,0901) (0000,0902)
Error: Cannot Understand C000 (0000,0901) (0000,0902)
Success 0000 None

Note: Status Codes are returned in DIMSE response messages (See PS 3.7). The code values stated in column "Status Codes" are returned in Status Command Element (0000,0900).

T.4.3 Hanging Protocol Storage SOP Class UID

The Hanging Protocol Storage SOP Class shall be uniquely identified by the Hanging Protocol Storage SOP Class UID, which shall have a value “1.2.840.10008.5.1.4.38.1”.

T.4.4 Conformance Statement Requirements

An implementation may conform to the Hanging Protocol Storage SOP Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in PS 3.2.

T.4.4.1 SCU Conformance Requirements

An implementation that conforms to the Hanging Protocol Storage SOP Class as an SCU that is a creator of Hanging Protocol SOP Instances shall state in its Conformance Statement:

T.4.4.2 SCP Conformance Requirements

An implementation that conforms to the Hanging Protocol Storage SOP Class as an SCP that interprets Hanging Protocol SOP Instances for display shall state in its Conformance Statement:

An implementation that conforms to the Hanging Protocol Storage SOP Class as an SCP shall state in its Conformance Statement: