DICOM PS3.4 2016d - Service Class Specifications

B.4.4 Specialized Conformance
Prev | B.4 Conformance | Next

### B.4.4 Specialized Conformance

Implementations may provide Specialized SOP Class conformance by providing a proper superset of the SOP Instances to be stored. Implementations providing Specialized SOP Class Conformance to one of the SOP Classes defined in this Annex shall be conformant as described in the following sections and shall include within their Conformance Statement information as described in the following sections.

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

#### B.4.4.1 Specialized SOP Class Identification

Any implementation that specializes the standard SOP Class shall define its specialization as an Allomorphic subclass of the standard SOP Class. As such, the specialization shall have its own unique SOP Class identification.

The Conformance Statement shall include a SOP Class Identification Statement as defined in PS3.2, declaring a SOP Name and SOP Class UID that identify the Specialized SOP Class. The SOP Name is not guaranteed to be unique (unless the implementer chooses to copyright it) but is provided for informal identification of the SOP Class. The SOP Class UID shall uniquely identify the Specialized SOP Class and conform to the DICOM UID requirements as specified in PS3.5.

Prev | Up | Next
B.4.3.2 Conformance Statement for an SCP | Home | B.4.4.2 Specialized Information Object Definition

DICOM PS3.4 2016d - Service Class Specifications