F.1 Overview

This Annex defines the Procedure Step SOP Classes.

Note: This Annex formerly defined a Study Management Service Class that has been retired. See PS 3.4 2004.

F.1.1 Scope

Retired. See PS 3.4-2004.

F.1.2 Study Management Functional Model

Retired. See PS 3.4-2004.

F.1.3 Study Management Information Model

Retired. See PS 3.4-2004.

F.1.4 Study Management States

Retired. See PS 3.4-2004.

F.1.5 Modality Performed Procedure Step Management States

The state information related to the Modality Performed Procedure Step is specified by the Modality Performed Procedure Step IOD in the Attribute Performed Procedure Step Status (0040,0252).

The Performed Procedure Step Object represents only the “performed” segment of the real-world procedure step and not the “scheduled” segment. The number of events is therefore limited; all events are initiated by the modality. The state “DISCONTINUED” means canceled or unsuccessfully terminated, which may happen when the performance of a Procedure Step has been started but cannot be finished by the modality. The modality shall convey this state change to the information system ( the SCP ), to allow the information system to reschedule or cancel the related Procedure Step. The state “COMPLETED” means that the acquisition of Composite SOP Instances has been successfully completed and the SCU has provided all required attribute values for the Performed Procedure Step.

Table F.1-3 describes the valid Modality Performed Procedure Step states.

Table F.1-3

MODALITY PERFORMED PROCEDURE STEP STATES

State Description
In Progress Modality Performed Procedure Step created and execution in progress
Discontinued Execution of Modality Performed Procedure Step canceled by modality
Completed Modality Performed Procedure Step completed

Table F.1-4 defines the valid state transitions for the Performed Procedure Steps. For each of the above defined states the valid state resulting from the occurrence of events is specified. These state transitions are managed by the Modality Performed Procedure Step SOP Class.

Table F.1-4

MODALITY PERFORMED PROCEDURE STEP S TATE TRANSITION DIAGRAM

States
Events In Progress Discontinued Completed
Performed Procedure Step Discontinued Discontinued
Performed Procedure Step Completed Completed

F.1.6 General Purpose Scheduled Procedure Step Management States

Figure F.1-3 specifies how changes in the status of a General Purpose Scheduled Procedure Step shall be managed.

[pic]

Figure F.1-3: Management of General Purpose Scheduled Procedure Step Status

The SCP will create the General Purpose Scheduled Procedure Step (GP-SPS) with an initial status of SCHEDULED. The availability of the input information is denoted by the Attribute “Input Availability Flag” (0040,4020) . The SCU may start working on a GP-SPS which has the status SCHEDULED, regardless of the availability of the input information. As soon as an SCU starts working on the performance of a GP-SPS, a status modification to IN PROGRESS shall be requested by the SCU. If the status modification to IN PROGRESS is acknowledged, the SCU at the same time has an implicit exclusive lock on the GP-SPS, as long as the status is IN PROGRESS. When the status has a value other than IN PROGRESS, there is no implicit exclusive lock on the GP-SPS.

Once a GP-SPS is started and the status is IN PROGRESS (that is, with an implicit exclusive lock) all subsequent attempts by another SCU to set the status will fail. This failure to set the status will indicate that someone else has already set the status of the GP-SPS to IN PROGRESS and will perform tasks related to it. The SCU that has set the status of the GP-SPS to IN PROGRESS and wants to relinquish control of it before its completion may request a status modification to SUSPENDED or SCHEDULED.

There is no limit on the number of transactions in either direction between IN PROGRESS and SCHEDULED or IN PROGRESS and SUSPENDED.

Once an IN PROGRESS GP-SPS is completed, the SCU shall request a modification of its status to COMPLETED.

The SCU may discontinue an IN PROGRESS GP-SPS at any time, provided the GP-SPS is not completed. To do so, the SCU requests a modification of the GP-SPS status to DISCONTINUED.

The SCP is responsible for defining how long a GP-SPS persists (is visible in worklist) once its status is COMPLETED or DISCONTINUED.

The state information related to the General Purpose Scheduled Procedure Step is specified by the General Purpose Scheduled Procedure Step IOD in the Attribute “General Purpose Scheduled Procedure Step Status” (0040,4001).

Table F.1-5 describes the valid General Purpose Scheduled Procedure Step states, and Table F.1-6 the valid state transitions.

Table F.1-5

GENERAL PURPOSE SCHEDULED PROCEDURE STEP STATES

State Description
Scheduled General Purpose Scheduled Procedure Step created and scheduled to be performed
In Progress General Purpose Scheduled Procedure Step created and execution in progress. This is the only state that implies an exclusive lock.
Suspended Execution of the General Purpose Scheduled Procedure Step temporarily suspended.
Discontinued Execution of General Purpose Scheduled Procedure Step canceled by SCU
Completed General Purpose Scheduled Procedure Step completed by SCU

Table F.1-6

GENERAL PURPOSE SCHEDULED PROCEDURE STEP S TATE TRANSITION DIAGRAM

States
Events Scheduled In Progress Suspended Completed Discontinued
General Purpose Scheduled Procedure Step Started In Progress (SCU)
General Purpose Scheduled Procedure Step Completed Completed (SCU)
General Purpose Scheduled Procedure Step Suspended Suspended (SCU)
General Purpose Scheduled Procedure Step Resumed In Progress (SCU)
General Purpose Scheduled Procedure Step Discontinued Discontinued (SCU)
General Purpose Scheduled Procedure Step Completed Completed (SCP)
General Purpose Scheduled Procedure Step Re-Scheduled Scheduled (SCU) Scheduled (SCP)

F.1.7 General Purpose Performed Procedure Step Management States

The General Purpose Performed Procedure Step Object represents only the “performed” segment of the real-world procedure step and not the “scheduled” segment.

As soon as a SCU starts working on the performance of a General Purpose Performed Procedure Step ( GP-PPS), the GP-PPS object will be created and the initial status shall be set to IN PROGRESS.

Once an IN PROGRESS GP-PPS is completed, its status shall be set to COMPLETED.

The SCU may discontinue a GP-PPS at any time, provided the GP-PPS is not completed. To do so, the GP-PPS status shall be set to DISCONTINUED.

The state “DISCONTINUED” means canceled or unsuccessfully terminated which may happen when the performance of a General Purpose Procedure Step has been started but cannot be finished by the SCU. The state “COMPLETED” means that the step has been successfully completed and the SCU has provided all required attribute values for the General Purpose Performed Procedure Step.

The SCP is responsible for determining how long a GP-PPS persists once its status is COMPLETED or DISCONTINUED.

The state information related to the General Purpose Performed Procedure Step is specified by the General Purpose Performed Procedure Step IOD in the Attribute “General Purpose Performed Procedure Step Status” (0040,4002).

Table F.1-7 describes the valid General Purpose Performed Procedure Step states.

Table F.1-7

GENERAL PURPOSE PERFORMED PROCEDURE STEP STATES

State Description
In Progress Performed Procedure Step created and execution in progress
Discontinued Execution of Performed Procedure Step canceled by SCU
Completed Performed Procedure Step completed

Table F.1-8 defines the valid state transitions for the General Purpose Performed Procedure Steps. For each of the above-defined states the valid state resulting from the occurrence of events is specified. These state transitions are managed by the General Purpose Performed Procedure Step SOP Class.

Table F.1-8

GENERAL PURPOSE PERFORMED PROCEDURE STEP S TATE TRANSITION DIAGRAM

States
Events In Progress Discontinued Completed
Performed Procedure Step Discontinued Discontinued (SCU)
Performed Procedure Step Completed Completed (SCU)