DICOM PS3.17 2018a - Explanatory Information

GGG.2.4 Third Party Cancel
Prev | GGG.2 Implementation Examples | Next

### GGG.2.4 Third Party Cancel

Cancel requests are always directed to the system managing the UPS instance since it is the SCP. When the UPS is being managed by one system (for example a Treatment Management System) and performed by a second system (for example a Treatment Delivery System), a third party would send the cancel request to the TMS and cancellation would take place as shown below.

Performing SCUs are not required to react to cancel requests, or even to listen for them, and in some situations would be unable to abort the task represented by the UPS even if they were listening. In the diagram below we assume the performing SCU is listening, willing, and able to cancel the task.

If the User had sent the cancel request while the UPS was still in the SCHEDULED state, the SCP (i.e., the TMS) could simply have canceled the UPS internally. Since the UPS state was IN PROGRESS, it was necessary to send the messages as shown. Note that since the TDS has no need for the UPS instance to persist, it subscribed without setting a Deletion Lock, and so it didn't need to bother unsubscribing later.

Figure GGG.4-1. Diagram of Third Party Cancel

Prev | Up | Next
GGG.2.3 Reporting Workflow With "hand-off" | Home | GGG.2.5 Radiation Therapy Dose Calculation Push Workflow

DICOM PS3.17 2018a - Explanatory Information