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.
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.
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.
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.
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 |
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 |
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.
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.
These notifications allow an SCU to receive from the SCP an unsolicited notification of a change in the state of a real-world performed procedure step. This notification 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 SCP shall specify in the N-EVENT-REPORT request primitive the UID of the Modality Performed Procedure Step SOP Instance with which the event is associated and the Event Type ID. The Affected SOP Class UID specified in the DIMSE N-EVENT-REPORT request primitive shall be the UID of the Modality Performed Procedure Step Notification SOP Class.
The encoding of Notification Event Information is defined in PS3.7.
There are no specific status codes. See PS3.7 for response status codes.
The Modality Performed Procedure Step Notification SOP Class shall be uniquely identified by the Modality Performed Procedure Step Notification SOP Class UID that shall have the value "1.2.840.10008.3.1.2.3.5".
Implementations providing Standard SOP Class Conformance to the Modality Performed Procedure Step Notification SOP Class 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 may conform to this SOP Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in PS3.2.
An implementation that is conformant to this SOP Class as an SCU shall meet conformance requirements for the:
notifications that it receives
All standard event types for which notifications may be requested by the SCU shall be enumerated in the SCU Notifications Statement. The SCU Notifications Statement shall include an enumerated list of the event types supported:
Performed Procedure Step In Progress
Performed Procedure Step Completed
Performed Procedure Step Discontinued
Performed Procedure Step Updated
Performed Procedure Step Deleted
An implementation that is conformant to this SOP Class as an SCP shall meet conformance requirements for:
notifications that it invokes
Any optional Attributes that may be included in Standard notifications to the SCU shall be enumerated in the SCP Notifications Statement. The SCP Notifications Statement shall be formatted as defined in PS3.2. Following this statement shall be the list of event types and optional Attributes.