DICOM PS3.4 2024e - Service Class Specifications |
---|
The DIMSE Services that are applicable to the IOD are shown below.
The meaning of the Usage (SCU/SCP) is described in Section H.2.4.
This Section describes the behavior of the DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is specified in PS3.7.
The N-EVENT-REPORT is used to report execution status changes to the SCU in an asynchronous way.
The arguments of the N-EVENT-REPORT are defined as shown in Table H.4-14.
The encoding of Notification Event Information is defined in PS3.7.
The SCP uses the N-EVENT-REPORT to inform the SCU about each execution change. The SCP shall only use the N-EVENT-REPORT within the context of the Association in which the Print Job SOP Instance was created.
If SCU wants to monitor the complete execution process of a Print Job, then the SCU should only release the Association after the receipt of the event type Done or Failure.
The SCU shall return the confirmation from the N-EVENT-REPORT operation.
If the Event Type Name = Failure or Pending then the error/pending condition is stored in the Execution Status Info argument. The possible values of the Execution Status Info argument are defined in Section H.4.5.3.
If the Event Type Name = Failure or Done then the SCP shall delete the Print Job SOP Instance after receiving a confirmation from the SCU.
There are no specific Status Codes. See PS3.7 for response Status Codes.
DICOM PS3.4 2024e - Service Class Specifications |
---|