R.3.4 Conformance Requirements
Prev | R.3 Instance Availability Notification SOP Class | Next

### R.3.4 Conformance Requirements

Implementations shall include within their Conformance Statement information as described below.

An implementation may conform to this SOP Class as an SCU or as an SCP. The Conformance Statement shall be in the format defined in Annex A “DICOM Conformance Statement Template (Normative)” in PS3.2.

#### R.3.4.1 SCU Conformance

An implementation that is conformant to this SOP Class as an SCU shall meet conformance requirements for the operations that it invokes.

##### R.3.4.1.1 Operations

Any Attributes for which Attribute Values may be provided (using the N-CREATE) by the SCU shall be enumerated in the SCU Conformance Statement. The SCU Conformance Statement shall be formatted as defined in Annex A “DICOM Conformance Statement Template (Normative)” in PS3.2.

An implementation that conforms to this SOP Class as an SCU shall specify under which conditions during the performance of real-world activities it will create the SOP Class Instance.

The SCU Conformance Statement shall specify what is meant by each reported value of Instance Availability (0008,0056).

The SCU Conformance Statement shall describe the relationship between the Instance Availability Notification and the Performed Procedure Step SOP Classes, if the latter are supported.

Prev | Up | Next
R.3.3 Instance Availability Notification SOP Class UID | Home | R.3.4.2 SCP Conformance