DICOM PS3.4 2017e - Service Class Specifications

F.9 Modality Performed Procedure Step Notification SOP Class
Prev | F Procedure Step SOP Classes (Normative) | Next

## F.9 Modality Performed Procedure Step Notification SOP Class

The Modality Performed Procedure Step Notification SOP Class is intended for those Application Entities requiring notifications of Modality Performed Procedure Step's changes in state.

An Application Entity may choose to take some actions based upon a notification or request for information but is in no way required to do so.

### Note

1. For example, in one configuration, an IS could be responsible for maintaining data related to performed procedure steps. A PACS reviewing workstation may need to display the images for any study viewed. In order for the PACS to link the images to the study, a PACS may receive a notification whenever a procedure step has been performed. In such a configuration the IS is the SCP and the PACS is the SCU. When the PACS receives this notification, it may link the images and the performed procedure step to the study within its internal database or may choose to take no action.

2. The terms IS and PACS used in the previous example are provided for clarification purposes only. This document does not define nor constrain the purpose or role of any IS, PACS or acquisition Application Entity conforming to this Service Class Specification.

### F.9.1 DIMSE Service Group

Table F.9.1-1 shows the DIMSE-N Services applicable to the Modality Performed Procedure Step IOD under the Modality Performed Procedure Step Notification SOP Class.

The DIMSE-N Services and Protocol are specified in PS3.7.

Table F.9.1-1. DIMSE-N Service Group

DIMSE Service Element | Usage SCU/SCP
--- | ---
N-EVENT-REPORT | M/M

Prev | Up | Next
F.8.4.2 SCP Conformance | Home | F.9.2 Notifications

DICOM PS3.4 2017e - Service Class Specifications