DICOM PS3.4 2017e - Service Class Specifications

F.7.4 Conformance Requirements
Prev | F.7 Modality Performed Procedure Step SOP Class | Next

### F.7.4 Conformance Requirements

Implementations providing conformance to the Modality Performed Procedure Step SOP Class shall be conformant as described in the following sections and 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 PS3.2.

#### F.7.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.

##### F.7.4.1.1 Operations

Any Attributes for which Attribute Values may be provided (using the N-CREATE Service) by the SCU shall be enumerated in the Conformance Statement.

Any Attributes for which Attribute Values may be provided (using the N-SET Service) by the SCU shall be enumerated in the Conformance Statement.

An implementation that conforms to this SOP Class as an SCU shall specify under which conditions during the performance of the real-world Performed Procedure Step it will create the SOP Class Instance and under which conditions it will set the status value to COMPLETED and DISCONTINUED.

An implementation that conforms to this SOP Class as an SCU shall specify what strategy it applies to group Storage SOP Class Instances referenced in a Performed Procedure Step.

### Note

For example, whether or not Radiation Dose SR instances are sent within the same Performed Procedure Step as the images to which it applies, or a different Performed Procedure Step. See the discussion of the MPPS in the DICOM real-world model in PS3.3.

Prev | Up | Next
F.7.3 Modality Performed Procedure Step SOP Class UID | Home | F.7.4.2 SCP Conformance

DICOM PS3.4 2017e - Service Class Specifications