The application-level services addressed by this Service Class Definition are specified via the following distinct SOP Classes:
Modality Performed Procedure Step SOP Class
Modality Performed Procedure Step Notification SOP Class
Modality Performed Procedure Step Retrieve SOP Class
General Purpose Scheduled Procedure Step SOP Class
General Purpose Performed Procedure Step SOP Class
Each SOP Class operates on a subset of the Modality Performed Procedure Step IOD, General Purpose Scheduled Procedure Step IOD, or General Purpose Performed Procedure Step IOD and specifies the Attributes, operations, notifications, and behavior applicable to the SOP Class. Conformance of Application Entities shall be defined by selecting one or more of the Study and Study Component Management SOP and Meta SOP Classes. For each SOP Class conformance requirements shall be specified in terms of the Service Class Provider (SCP) and the Service Class User (SCU).
Association establishment is the first phase of any instance of communication between peer DICOM AEs. The Association negotiation procedure specified in PS 3.7 shall be used to negotiate the supported SOP Classes.
Support for the SCP/SCU role selection negotiation is mandatory. The SOP Class Extended Negotiation shall not be supported.
Note: Event notification is a process that logically extends across multiple Associations. SCP implementations should support a local table of SCUs to which event notifications are to be sent.