DICOM PS3.4 2020a - Service Class Specifications

B.4.3 Conformance Statement Requirements (Current)
Prev | B.4 Conformance | Next

### B.4.3 Conformance Statement Requirements

An implementation may conform to a SOP Class of the Storage Service Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in PS3.2.

#### B.4.3.1 Conformance Statement for an SCU

The following issues shall be documented in the Conformance Statement of any implementation claiming conformance to the Storage SOP Class as an SCU:

- The behavior of the SCU in the case of a successful C-STORE response status shall be described.

- The behavior of the SCU in each case of an unsuccessful C-STORE response status shall be described.

- The behavior of the SCU in the case of a Warning status received in response to a C-STORE operation.

- Whether extended negotiation is supported.

- The optional elements that may be included in Storage SOP Instances for each IOD supported shall be listed.

- The standard and privately defined Functional Groups that may be included in Storage SOP Instances for each Multi-frame IOD that support Functional Groups.

- The behavior of the SCU in the case of a C-STORE operation using a referenced pixel data transfer syntax such as JPIP Referenced Pixel Data Transfer Syntax shall be described. This includes the duration of validity of the reference

Prev | Up | Next
B.4.2 Conformance as an SCU | Home | B.4.3.2 Conformance Statement for an SCP

DICOM PS3.4 2020a - Service Class Specifications