DICOM PS3.4 2017a - Service Class Specifications

F.9.2 Notifications
Prev | F.9 Modality Performed Procedure Step Notification SOP Class | Next

### F.9.2 Notifications

The Application Entity that claims conformance as an SCU to this SOP Class shall be permitted to receive the following notification. The Application Entity that claims conformance as an SCP to this SOP Class shall be capable of providing the notifications defined in Table F.9.2-1.

Table F.9.2-1. Performed Procedure Step Notification Event Information

Event Type Name | Event Type ID | Attribute Name | Tag | Req. Type SCU/SCP
--- | --- | --- | --- | ---
Performed Procedure Step In Progress | 1 |  |  |
Performed Procedure Step Completed | 2 |  |  |
Performed Procedure Step Discontinued | 3 |  |  |
Performed Procedure Step Updated | 4 |  |  | An Update event shall not be used to notify changes in Performed Procedure Step Status (0040,0252).
Performed Procedure Step Deleted | 5 |  |  |

### Note

The Notification Event Information contains no Attributes, beyond those defined in PS3.7. An SCU receiving a Notification and requiring further information may also be an SCU of the Modality Performed Procedure Step Retrieval SOP Class and may use the Affected SOP Instance UID (0000,1000) to perform an N-GET of the Modality Performed Procedure Step SOP Instance.

#### F.9.2.1 Receive Modality Performed Procedure Step Event Notification

This notification allows an SCU to receive from the SCP an unsolicited notification of a change in a Modality Performed Procedure Step SOP Instance. These notifications shall be invoked by the SCP through the use of the DIMSE N-EVENT-REPORT Service used in conjunction with the related Modality Performed Procedure Step SOP Instance.

The SCU shall return, via the N-EVENT-REPORT response primitive, the N-EVENT-REPORT Response Status Code applicable to the associated request. The SCU shall accept all Attributes included in any notification. This Service Class Specification places no requirements on what the SCU shall do as a result of receiving this information.

The same SOP Instance UID is shared by all three Modality Performed Procedure Step SOP Classes. This means that the SOP Instance created and set using the services of the Modality Performed Procedure Step SOP Class can be retrieved using its SOP Instance UID within the service of the Modality Performed Procedure Step Retrieve SOP Class. Changes in its state can be notified by using its SOP Instance UID within the request primitive of the Modality Performed Procedure Step Notification SOP Class.

The Modality Performed Procedure Step Notification SOP Instance UID shall not be used to identify a SOP Instance of the Study Component Service Class.

Prev | Up | Next
F.9 Modality Performed Procedure Step Notification SOP Class | Home | F.9.2.2 Provide Modality Performed Procedure Step Event Notification

DICOM PS3.4 2017a - Service Class Specifications