T.4.2 Service Class Provider
Prev | T.4 Hanging Protocol Storage SOP Class | Next

### 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 PS3.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 PS3.7). The code values stated in column "Status Codes" are returned in Status Command Element (0000,0900).

Prev | Up | Next
T.4 Hanging Protocol Storage SOP Class | Home | T.4.3 Hanging Protocol Storage SOP Class UID