Annex F PROCEDURE STEP SOP CLASSES(Normative)

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)

F.2 CONFORMANCE OVERVIEW

The application-level services addressed by this Service Class Definition are specified via the following distinct SOP Classes:

  1. Modality Performed Procedure Step SOP Class

  2. Modality Performed Procedure Step Notification SOP Class

  3. Modality Performed Procedure Step Retrieve SOP Class

  4. General Purpose Scheduled Procedure Step SOP Class

  5. General Purpose Performed Procedure Step SOP Class

Each SOP Class operates on a subset of the Modality Performed Procedure Step IOD, General Purpose Scheduled Procedure Step IOD, or General Purpose Performed Procedure Step IOD and specifies the Attributes, operations, notifications, and behavior applicable to the SOP Class. Conformance of Application Entities shall be defined by selecting one or more of the Study and Study Component Management SOP and Meta SOP Classes. For each SOP Class conformance requirements shall be specified in terms of the Service Class Provider (SCP) and the Service Class User (SCU).

F.2.1 Association Negotiation

Association establishment is the first phase of any instance of communication between peer DICOM AEs. The Association negotiation procedure specified in PS 3.7 shall be used to negotiate the supported SOP Classes.

Support for the SCP/SCU role selection negotiation is mandatory. The SOP Class Extended Negotiation shall not be supported.

Note: Event notification is a process that logically extends across multiple Associations. SCP implementations should support a local table of SCUs to which event notifications are to be sent.

F.3 Detached study management SOP class

Retired. See PS 3.4-2004.

F.4 Study component management SOP class

Retired. See PS 3.4-2004.

F.5 Study management meta SOP class

Retired. See PS 3.4-2004.

F.6 Specialized SOP class conformance

Retired. See PS 3.4-2004.

F.7 MODALITY Performed Procedure Step SOP Class

F.7.1 DIMSE Service Group

The DIMSE Services shown in Table F.7.1-1 are applicable to the Modality Performed Procedure Step IOD under the Modality Performed Procedure Step SOP Class.

Table F.7.1-1

DIMSE SERVICE GROUP

DIMSE Service Element Usage SCU/SCP
N-CREATE M/M
N-SET M/M

The DIMSE Services and Protocols are specified in PS 3.7

F.7.2 Operations

The Application Entity which claims conformance to this SOP Class as an SCU shall be permitted to invoke the following operations and the Application Entity which claims conformance as an SCP shall be capable of providing the following operations.

F.7.2.1 CREATE Modality Performed Procedure Step SOP Instance

This operation allows an SCU to create an instance of the Modality Performed Procedure Step SOP Class and provide information about a specific real-world Performed Procedure Step that is under control of the SCU. This operation shall be invoked through the DIMSE N-CREATE Service.

Note : The modality should inform the Information System as soon as possible that the performance of the Procedure Step has been started by sending the N-CREATE Service Request. This allows an SCP of the Modality Worklist SOP Class (if supported) to update the Modality Worklist. Some of the attribute values are already known at the beginning of the Procedure Step, they are required to be sent in the N-CREATE command. Other mandatory attributes are known only at the end of the Performed Procedure Step, they are assigned a value in the N-SET command.

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 service of the Modality Performed Procedure Step Notification SOP Class. The SOP Class UID specified in the DIMSE N-CREATE and N-SET request primitives shall be the UID of the Modality Performed Procedure Step SOP Class.

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

F.7.2.1.1 Modality Performed Procedure Step Subset Specification

The Application Entity which claims conformance to this SOP Class as an SCU must provide all Required Attributes as specified in Table F.7.2-1. Optional Attributes maintained by the SCP may be provided as well. The Application Entity which claims conformance as an SCP to this SOP Class shall support the subset of the Modality Performed Procedure Step Attributes specified in Table F.7.2-1.

Table F.7.2-1 MODALITY PERFORMED PROCEDURE STEP SOP CLASS N-CREATE, N-SET AND FINAL STATE ATTRIBUTES

Attribute Name Tag Req. Type N-CREATE (SCU/SCP) Req. Type N-SET (SCU/SCP) Requirement Type Final State (See Note 1)
Specific Character Set (0008,0005) 1C/1C (Required if an extended or replacement character set is used) Not allowed
Performed Procedure Step Relationship
Scheduled Step Attribute Sequence (0040,0270) 1/1 Not allowed
>Study Instance UID (0020,000D) 1/1 Not allowed
>Referenced Study Sequence (0008,1110) 2/2 Not allowed
>>Referenced SOP Class UID (0008,1150) 1/1 Not allowed
>>Referenced SOP Instance UID (0008,1155) 1/1 Not allowed
>Accession Number (0008,0050) 2/2 Not allowed
>Issuer of Accession Number Sequence (0008,0051) 3/3 Not allowed
>>Local Namespace Entity ID (0040,0031) 1C/1C Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed
>>Universal Entity ID (0040,0032) 1C/1C Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise. Not allowed
>>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present. Not allowed
>Placer Order Number/Imaging Service Request (0040,2016) 3/3 Not allowed
>Order Placer Identifier Sequence (0040,0026) 3/3 Not allowed
>>Local Namespace Entity ID (0040,0031) 1C/1C Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed
>>Universal Entity ID (0040,0032) 1C/1C Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise.. Not allowed
>>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present. Not allowed
>Filler Order Number/Imaging Service Request (0040,2017) 3/3 Not allowed
>Order Filler Identifier Sequence (0040,0027) 3/3 Not allowed
>>Local Namespace Entity ID (0040,0031) 1C/1C Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed
>>Universal Entity ID (0040,0032) 1C/1C Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise.. Not allowed
>>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present. Not allowed
>Requested Procedure ID (0040,1001) 2/2 Not allowed
>Requested Procedure Code Sequence (0032,1064) 3/3 Not allowed
>>Code Value (0008,0100) 1/1 Not allowed
>>Coding Scheme Designator (0008,0102) 1/1 Not allowed
>>Code Meaning (0008,0104) 1/1 Not allowed
>Requested Procedure Description (0032,1060) 2/2 Not allowed
>Scheduled Procedure Step ID (0040,0009) 2/2 Not allowed
>Scheduled Procedure Step Description (0040,0007) 2/2 Not allowed
>Scheduled Protocol Code Sequence (0040,0008) 2/2 Not allowed
>>Code Value (0008,0100) 1/1 Not allowed
>>Coding Scheme designator (0008,0102) 1/1 Not allowed
>>Coding Scheme Version (0008,0103) 3/3 Not allowed
>>Code Meaning (0008,0104) 3/3 Not allowed
>>All other Attributes from Scheduled Protocol Code Sequence 3/3 Not allowed
Patient’s Name (0010,0010) 2/2 Not allowed
Patient ID (0010,0020) 2/2 Not allowed
Issuer of Patient ID (0010,0021) 3/3 Not allowed
Issuer of Patient ID Qualifiers Sequence (0010,0024) 3/3 Not allowed
>Universal Entity ID (0040,0032) 3/3 Not allowed
>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present. Not allowed
>All other attributes of Issuer of Patient ID Qualifiers Sequence 3/3 Not allowed
Patient’s Birth Date (0010,0030) 2/2 Not allowed
Patient’s Sex (0010,0040) 2/2 Not allowed
Referenced Patient Sequence (0008,1120) 2/2 Not allowed
>Referenced SOP Class UID (0008,1150) 1/1 Not allowed
>Referenced Instance UID (0008,1155) 1/1 Not allowed
Admission ID (0038,0010) 3/3 Not Allowed
Issuer of Admission ID Sequence (0038,0014) 3/3 Not allowed
>Local Namespace Entity ID (0040,0031) 1C/1C Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed
>Universal Entity ID (0040,0032) 1C/1C Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise.. Not allowed
>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present. Not allowed
Service Episode ID (0038,0060) 3/3 Not allowed
Issuer of Service Episode ID Sequence (0038,0064) 3/3 Not allowed
>Local Namespace Entity ID (0040,0031) 1C/1C Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed
>Universal Entity ID (0040,0032) 1C/1C Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise.. Not allowed
>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present. Not allowed
Service Episode Description (0038,0062) 3/3 Not allowed
Performed Procedure Step Information
Performed Procedure Step ID (0040,0253) 1/1 Not allowed
Performed Station AE Title (0040,0241) 1/1 Not allowed
Performed Station Name (0040,0242) 2/2 Not allowed
Performed Location (0040,0243) 2/2 Not allowed
Performed Procedure Step Start Date (0040,0244) 1/1 Not allowed
Performed Procedure Step Start Time (0040,0245) 1/1 Not allowed
Performed Procedure Step Status (0040,0252) 1/1 3/1
Performed Procedure Step Description (0040,0254) 2/2 3/2
Performed Procedure Type Description (0040,0255) 2/2 3/2
Procedure Code Sequence (0008,1032) 2/2 3/2
>Code Value (0008,0100) 1/1 1/1
>Coding Scheme Designator (0008,0102) 1/1 1/1
>Coding Scheme Version (0008,0103) 3/3 3/3
>Code Meaning (0008,0104) 3/3 3/3
Reason For Performed Procedure Code Sequence (0040,1012) 3/3 3/3
>Code Value (0008,0100) 1/1 1/1
>Coding Scheme Designator (0008,0102) 1/1 1/1
>Coding Scheme Version (0008,0103) 3/3 3/3
>Code Meaning (0008,0104) 1/1 1/1
Performed Procedure Step End Date (0040,0250) 2/2 3/1 1
Performed Procedure Step End Time (0040,0251) 2/2 3/1 1
Comments on the Performed Procedure Step (0040,0280) 3/3 3/3
Performed Procedure Step Discontinuation Reason Code Sequence (0040,0281) 3/3 3/3
>Code Value (0008,0100) 1/1 1/1
>Coding Scheme Designator (0008,0102) 1/1 1/1
>Coding Scheme Version (0008,0103) 3/3 3/3
>Code Meaning (0008,0104) 3/3 3/3
Image Acquisition Results
Modality (0008,0060) 1/1 Not allowed
Study ID (0020,0010) 2/2 Not allowed
Performed Protocol Code Sequence (0040,0260) 2/2 3/2
>Code Value (0008,0100) 1/1 1/1
>Coding Scheme Designator (0008,0102) 1/1 1/1
>Coding Scheme Version (0008,0103) 3/3 3/3
>Code Meaning (0008,0104) 3/3 3/3
>All other Attributes from Performed Protocol Code Sequence 3/3 Not allowed
Performed Series Sequence (0040,0340) 2/2 3/1 1 (See note 2)
>Performing Physician’s Name (0008,1050) 2/2 2/2 2
>Protocol Name (0018,1030) 1/1 1/1 1
>Operators’ Name (0008,1070) 2/2 2/2 2
>Series Instance UID (0020,000E) 1/1 1/1 1
>Series Description (0008,103E) 2/2 2/2 2
>Retrieve AE Title (0008,0054) 2/2 2/2 2
>Archive Requested (0040,A494) 3/3 3/3
>Referenced Image Sequence (0008,1140) 2/2 2/2 See F.7.2.2.2.
>>Referenced SOP Class UID (0008,1150) 1/1 1/1
>>Referenced SOP Instance UID (0008,1155) 1/1 1/1
>>Container Identifier (0040,0512) 3/3 3/3
>>Specimen Description Sequence (0040,0560) 3/3 3/3
>>>Specimen Identifier (0040,0551) 1/1 1/1
>>>Specimen UID (0040,0554) 1/1 1/1
>Referenced Non-Image Composite SOP Instance Sequence (0040,0220) 2/2 2/2 See F.7.2.2.2.
>>Referenced SOP Class UID (0008,1150) 1/1 1/1
>>Referenced SOP Instance UID (0008,1155) 1/1 1/1
>All other attributes from Performed Series Sequence 3/3 3/3
All other attributes from Radiation Dose Module and Billing and Material Code Module 3/3 3/3

Notes: 1. The requirement for the final state is that which applies at the time that the Performed Procedure Step Status (0040,0252) is N-SET to a value of COMPLETED or DISCONTINUED, as described in F.7.2.2.2. It is only described if it is different from the SCP requirement for the N-CREATE.

2. The Performed Series Sequence (0040,0340) may not be empty (zero length) at the time that the Performed Procedure Step Status (0040,0252) is N-SET to a value of COMPLETED or DISCONTINUED. In other words a Series must exist for every Performed Procedure Step, though it may contain no Images or Non-Image Composite objects, if none were created, as described in F.7.2.2.2.

3. Attributes (0040,1006) Placer Order Number/Procedure and (0040,1007) Filler Order Number/Procedure were previously defined in DICOM. They are now retired (See PS3.3 1998).

4. Attributes (0040,2006) and (0040,2007) were previously defined in DICOM. They are now retired (See PS3.3 1998).

5. Only attributes that are specified in a SOP Instance at N-CREATE may later be updated through the N-SET. If an SCU wishes to use the PPS Discontinuation Reason Code Sequence (0040,0281), it must create that attribute (zero-length) during MPPS N-CREATE.

F.7.2.1.2 Service Class User

The SCU shall specify in the N-CREATE request primitive the Class and Instance UIDs of the Modality Performed Procedure Step SOP Instance which is created and for which Attribute Values are to be provided.

Note: This requirement facilitates the inclusion of relevant Attributes in the Composite SOP Instances generated during the Performed Procedure Step.

The SCU shall provide Attribute values for the Modality Performed Procedure Step SOP Class Attributes as specified in Table F.7.2-1. Additionally, values may be provided for optional Modality Performed Procedure Step IOD Attributes that are supported by the SCP. The encoding rules for Modality Performed Procedure Step Attributes are specified in the N-CREATE request primitive specification in PS 3.7.

The SCU shall be capable of providing all required Attribute values to the SCP in the N-CREATE request primitive. The SCU may provide Attribute values for optional Attributes which are not maintained by the SCP. In such case the SCU shall function properly regardless of whether the SCP accepts values for those Attributes or not.

All Attributes shall be created before they can be set. Sequence Attributes shall be created before they can be filled. Sequence Item Attributes shall not be created at zero length.

Note: Not all the attributes that can be created can be set afterwards (see Table F.7.2-1).

The SCU shall only send the N-CREATE request primitive with the value for the Attribute “Performed Procedure Step Status” (0040,0252) set to “IN PROGRESS”.

Notea: 1. It is assumed but not required that the SCU (the modality) received the Study Instance UID within the scope of the Basic Worklist Management SOP Class.

2. If the SCU has grouped multiple Requested Procedures into a single performed step the Study Instance UID (0020,000D) attribute within the Scheduled Step Attributes Sequence (0040,0270) may be the Study Instance UID (0020,000D) for the study that contains all images and non-image composite instances created during performance of the current step. This value may be generated by the SCU and may be the same for all items of the sequence. In addition, the Referenced Study Sequence (0008,1110) may contain the Study Instance UIDs from the Requested Procedures being grouped.

3. If the SCU does not have available Scheduled Procedure Step data applicable to the current step, the SCU may generate a value for the Study Instance UID (0020,000D) attribute within the Scheduled Step Attributes Sequence (0040,0270). This value of the Study Instance UID (0020,000D) may be stored in all mages and non-image composite SOP instances created during performance of this step. All other attributes within the Scheduled Step Attribute Sequence (0040,0270) may be set to zero length for 2/2 requirement types or absent for 3/3 requirement types (see Table F.7.2-1) .

F.7.2.1.3 Service Class Provider

The N-CREATE operation allows the SCU to provide to the SCP selected Attribute values for a specific Modality Performed Procedure Step SOP Instance. This operation shall be invoked through the use of the DIMSE N-CREATE Service used in conjunction with the appropriate Modality Performed Procedure Step SOP Instance.

The SCP shall return, via the N-CREATE response primitive, the N-CREATE Response Status Code applicable to the associated request.

The SCP shall accept N-CREATE request primitives only if the value of the attribute “Performed Procedure Step Status” (0040,0252) is “IN PROGRESS”. If the Performed Procedure Step Status attribute has another value, the SCP shall set the failure status code “Invalid attribute value” (Code: 0106H) with an Attribute List.

Note: The SCP may update the scheduling information on which the Modality Worklist is based, including the values of Study Date (0008,0020) and Study Time (0008,0030) using the earliest corresponding values of Performed Procedure Step Date (0040,0244) and Performed Procedure Step Time (0040,0245), in order to achieve consistency of Study level attributes when multiple procedure steps are performed on different devices.

F.7.2.1.4 Status Codes

There are no specific status codes. See PS 3.7 for response status codes.

F.7.2.2 SET Modality Performed Procedure Step Information

This operation allows an SCU to set Attribute Values of an instance of the Modality Performed Procedure Step SOP Class and provide information about a specific real-world Modality Performed Procedure Step that is under control of the SCU. This operation shall be invoked through the DIMSE N-SET Service.

F.7.2.2.1 Modality Performed Procedure Step IOD Subset Specification

The Application Entity which claims conformance to this SOP Class as an SCU may choose to modify a subset of the Attributes maintained by the SCP. The Application Entity which claims conformance as an SCP to this SOP Class shall support the subset of the Modality Performed Procedure Step Attributes specified in Table F.7.2-1.

The character set used for Attribute Values updated using the N-SET shall be the same as that specified by the N-CREATE Request Primitive.

F.7.2.2.2 Service Class User

The SCU shall specify in the N-SET request primitive the UID of the Modality Performed Procedure Step SOP Instance for which it wants to set Attribute Values.

The SCU shall be permitted to set Attribute values for any Modality Performed Procedure Step SOP Class Attribute specified in Table F.7.2-1. The SCU shall specify the list of Modality Performed Procedure Step SOP Class Attributes for which it wants to set the Attribute Values. The SCU shall provide, with one or more N-SET request primitives, the attribute values specified in Table F.7.2-1. The encoding rules for Modality Performed Procedure Step Attributes are specified in the N-SET request primitive specification in PS 3.7. The SCU shall only set Attribute Values which are already created with an N-CREATE request.

The SCU shall not send N-SET request primitives for a Modality Performed Procedure Step SOP Instance after a N-SET request primitive with a value for the attribute “Performed Procedure Step Status” (0040,0252) is “COMPLETED” or “DISCONTINUED” has been sent.

If Sequences are included in a N-SET command, all Items of a Sequence are to be included in the command and not only the Items to be updated.

Once the Modality Performed Procedure Step Status (0040,0252) has been set to “COMPLETED” or “DISCONTINUED” the SCU shall no longer modify the Modality Performed Procedure Step SOP Instance, and shall not create new Composite SOP Instances as part of the same Modality Performed Procedure Step SOP Instance.

Note: A Modality that wishes to continue or resume creating Composite SOP Instances may create a new Modality Performed Procedure Step.

Before or when Modality Performed Procedure Step Status (0040,0252) is set to “COMPLETED” or “DISCONTINUED” the SCU shall have created or set all the Attributes according to the requirements in the Final State column of Table F.7.2-1.

Before or when Modality Performed Procedure Step Status (0040,0252) is set to “COMPLETED” or “DISCONTINUED” the SCU shall have sent to the SCP a list of all Image SOP Instances and all Non-Image Composite SOP Instances created during the Procedure Step in Referenced Image Sequence (0008,1140) and Referenced Non-Image Composite SOP Instance Sequence (0040,0220) respectively.

Notes: 1. The intent is that a completed or discontinued Modality Performed Procedure Step entity will contain a complete list of all the Images and Non-Image Composite SOP Instances that were created.

2. The distinction between the list of images and non-images is present for historic reasons only, and has no semantic significance.

The Modality Performed Procedure Step Status (0040,0252) shall not be set to “COMPLETED” or “DISCONTINUED” if the list contains neither Image references nor Non-Image Composite SOP Instance references, unless no such Instances were created.

F.7.2.2.3 Service Class Provider

The N-SET operation allows the SCU to request that the SCP update selected Attribute values for a specific Modality Performed Procedure Step SOP Instance. This operation shall be invoked through the use of the DIMSE N-SET Service used in conjunction with the appropriate Modality Performed Procedure Step SOP Instance.

The SCP shall return, via the N-SET response primitive, the N-SET Response Status Code applicable to the associated request. Contingent on the N-SET Response Status, the SCP shall update the Referenced Performed Procedure Step Attributes.

The SCP shall accept N-SET request primitives only if the value of the already existing attribute “Performed Procedure Step Status” (0040,0252) is “IN PROGRESS”. If the already existing Performed Procedure Step Status attribute has another value, the SCP shall set the failure status code “Processing failure” (Code: 0110H) with a Specific Error Comment (see Section F.7.2.2.4).

The SCP may itself modify any Attributes of the Modality Performed Procedure Step SOP Instance only after the “Performed Procedure Step Status” (0040,0252) has been set to “COMPLETED” or “DISCONTINUED”.

Notes: 1. Such coercion of Attributes by the SCP may be necessary to correct, for example, patient identification information or incorrectly selected scheduling information. Such an operation is not permitted to the SCU by the requirements described in Table F.7.2-1, which might create a new Modality Performed Procedure Step SOP Instance to achieve the same objective.

2. Under exceptional circumstances, it may be necessary for the SCP to itself set the Performed Procedure Step Status (0040,0252) to COMPLETED or DISCONTINUED, for example if the Modality has failed. When the Modality recovers, subsequent N-SETs may fail.

F.7.2.2.4 Status Codes

The specific error comment which may be returned as a status code in a N-SET-RSP is defined in Table F.7.2-2. See PS 3.7 for additional response status codes.

Table F.7.2-2

N-SET STATUS

Service Status Further Meaning Status Code Error Comment (0000,0902) Error ID (0000,0903)
Failure Processing Failure 0110H Performed Procedure Step Object may no longer be updated A710

F.7.3 Modality Performed Procedure Step SOP Class UID

The Modality Performed Procedure Step SOP Class shall be uniquely identified by the Modality Performed Procedure Step SOP Class UID which shall have the value “1.2.840.10008.3.1.2.3.3”.

F.7.4 Conformance Requirements

Implementations providing conformance to the Modality Performed Procedure Step SOP Class shall be conformant as described in the following sections and shall include within their Conformance Statement information as described below.

An implementation may conform to this SOP Class as an SCU or as an SCP. The Conformance Statement shall be in the format defined in PS 3.2.

F.7.4.1 SCU Conformance

An implementation which is conformant to this SOP Class as an SCU shall meet conformance requirements for the operations that it invokes.

F.7.4.1.1 Operations

Any Attributes for which Attribute Values may be provided (using the N-CREATE Service) by the SCU shall be enumerated in the Conformance Statement.

Any Attributes for which Attribute Values may be provided (using the N-SET Service) by the SCU shall be enumerated in the Conformance Statement.

An implementation that conforms to this SOP Class as an SCU shall specify under which conditions during the performance of the real-world Performed Procedure Step it will create the SOP Class Instance and under which conditions it will set the status value to COMPLETED and DISCONTINUED.

An implementation that conforms to this SOP Class as an SCU shall specify what strategy it applies to group Storage SOP Class Instances referenced in a Performed Procedure Step.

Note: For example, whether or not Radiation Dose SR instances are sent within the same Performed Procedure Step as the images to which it applies, or a different Performed Procedure Step. See the discussion of the MPPS in the DICOM real-world model in PS 3.3.

F.7.4.2 SCP Conformance

An implementation which is conformant to this SOP Class as an SCP shall meet conformance requirements for the operations which it performs.

F.7.4.2.1 Operations

Any Attributes for which Attribute Values may be provided (using the N-CREATE Service) by the SCU shall be enumerated in the Conformance Statement.

Any Attributes for which Attribute Values may be updated (using the N-SET Service) by the SCU shall be enumerated in the Conformance Statement.

The Conformance Statement shall also provide information on the behavior of the SCP at the following occurrences:

F.8 MODALITY Performed Procedure Step RETRIEVE SOP Class

F.8.1 DIMSE Service Group

The DIMSE Services shown in Table F.8.1-1 are applicable to the Modality Performed Procedure Step IOD under the Modality Performed Procedure Step Retrieve SOP Class.

Table F.8.1-1

DIMSE SERVICE GROUP

DIMSE Service Element Usage SCU/SCP
N-GET M/M

The DIMSE Services and Protocols are specified in PS 3.7. If the Modality Performed Procedure Step Object is no longer available the Request Primitive will be answered with a Failure Status message “No Such Object Instance”.

F.8.2 Operations

The Application Entity which claims conformance to this SOP Class as an SCU shall be permitted to invoke the following operations and the Application Entity which claims conformance as an SCP shall be capable of providing the following operations.

F.8.2.1 GET Performed Procedure Step Information

This operation allows an SCU to get information about a specific real-world Performed Procedure Step which is represented as a Modality Performed Procedure Step Retrieve SOP Instance by a Modality Performed Procedure Step Retrieve SCP. The operation is performed on a Modality Performed Procedure Step IOD. This operation shall be invoked through the DIMSE N-GET Service used in conjunction with the appropriate Modality Performed Procedure Step Retrieve SOP Instance.

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 service of the Modality Performed Procedure Step Notification SOP Class. The SOP Class UID specified in the DIMSE N-GET request primitive shall be the UID of the Modality Performed Procedure Step Retrieve SOP Class.

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

Note: An Application Entity may support the SCU role of the Modality Performed Procedure Step Retrieve SOP Class in order to obtain information about Performed Procedure Steps created by other Application Entities.

F.8.2.1.1 Modality Performed Procedure Step Retrieve IOD Subset Specifications

The Application Entity which claims conformance to this SOP Class as an SCU may choose to interpret the Attribute values maintained by the SCP which the SCU receives via the operation of this SOP Class. The Application Entity which claims conformance as an SCP to this Modality Performed Procedure Step Retrieve SOP Class shall support the subset of the Modality Performed Procedure Step Retrieve Attributes specified in Table F.8.2-1.

Table F.8.2-1

MODALITY PERFORMED PROCEDURE STEP RETRIEVE SOP CLASS N-GET ATTRIBUTES

Attribute Name Tag Requirement Type (SCU/SCP)
Specific Character Set (0008,0005) 3/1C (Required if an extended or replacement character set is used)
Performed Procedure Step Relationship
Scheduled Step Attributes Sequence (0040,0270) 3/1
>Study Instance UID (0020,000D) -/1
>Referenced Study Sequence (0008,1110) -/2
>>Referenced SOP Class UID (0008,1150) -/1
>>Referenced SOP Instance UID (0008,1155) -/1
>Accession Number (0008,0050) -/2
>Issuer of Accession Number Sequence (0008,0051) -/3
>>Local Namespace Entity ID (0040,0031) -/3
>>Universal Entity ID (0040,0032) -/3
>>Universal Entity ID Type (0040,0033) -/3
>Placer Order Number/Imaging Service Request (0040,2016) -/3
>Order Placer Identifier Sequence (0040,0026) -/3
>>Local Namespace Entity ID (0040,0031) -/3
>>Universal Entity ID (0040,0032) -/3
>>Universal Entity ID Type (0040,0033) -/3
>Filler Order Number/Imaging Service Request (0040,2017) -/3
>Order Filler Identifier Sequence (0040,0027) -/3
>>Local Namespace Entity ID (0040,0031) -/3
>>Universal Entity ID (0040,0032) -/3
>>Universal Entity ID Type (0040,0033) -/3
>Requested Procedure Code Sequence (0032,1064) -/3
>>Code Value (0008,0100) -/1
>>Coding Scheme Designator (0008,0102) -/1
>>Code Meaning (0008,0104) -/1
>Requested Procedure Description (0032,1060) -/2
>Requested Procedure ID (0040,1001) -/2
>Scheduled Procedure Step ID (0040,0009) -/2
>Scheduled Procedure Step Description (0040,0007) -/2
>Scheduled Protocol Code Sequence (0040,0008) -/2
>>Code Value (0008,0100) -/1
>>Coding Scheme designator (0008,0102) -/1
>>Coding Scheme Version (0008,0103) -/3
>>Code Meaning (0008,0104) -/3
>>All other Attributes from Scheduled Protocol Code Sequence -/3
Patient’s Name (0010,0010) 3/2
Patient ID (0010,0020) 3/2
Issuer of Patient ID (0010,0021) 3/3
Issuer of Patient ID Qualifiers Sequence (0010,0024) 3/3
>Universal Entity ID (0040,0032) 3/3
>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present.
>All other attributes of Issuer of Patient ID Qualifiers Sequence 3/3
Patient’s Birth Date (0010,0032) 3/2
Patient’s Sex (0010,0040) 3/2
Referenced Patient Sequence (0008,1120) 3/2
>Referenced SOP Class UID (0008,1150) -/1
>Referenced Instance UID (0008,1155) -/1
Admission ID (0038,0010) 3/3
Issuer of Admission ID Sequence (0038,0014) 3/3
>Local Namespace Entity ID (0040,0031) -/3
>Universal Entity ID (0040,0032) -/3
>Universal Entity ID Type (0040,0033) -/3
Service Episode ID (0038,0060) 3/3
Issuer of Service Episode ID Sequence (0038,0064) 3/3
>Local Namespace Entity ID (0040,0031) -/3
>Universal Entity ID (0040,0032) -/3
>Universal Entity ID Type (0040,0033) -/3
Service Episode Description (0038,0062) 3/3
Performed Procedure Step Information
Performed Station AE Title (0040,0241) 3/1
Performed Station Name (0040,0242) 3/2
Performed Location (0040,0243 3/2
Performed Procedure Step Start Date (0040,0244) 3/1
Performed Procedure Step Start Time (0040,0245) 3/1
Performed Procedure Step ID (0040,0253) 3/1
Performed Procedure Step Status (0040,0252) 3/1
Performed Procedure Step End Date (0040,0250) 3/2
Performed Procedure Step End Time (0040,0251) 3/2
Performed Procedure Step Description (0040,0254) 3/2
Performed Procedure Type Description (0040,0255) 3/2
Procedure Code Sequence (0008,1032) 3/2
>Code Value (0008,0100) -/1
>Coding Scheme Designator (0008,0102) -/1
>Coding Scheme Version (0008,0103) -/3
>Code Meaning (0008,0104) -/3
Comments on the Performed Procedure Step (0040,0280) 3/3
Performed Procedure Step Discontinuation Reason Code Sequence (0040,0281) 3/2
>Code Value (0008,0100) -/1
>Coding Scheme Designator (0008,0102) -/1
>Coding Scheme Version (0008,0103) -/3
>Code Meaning (0008,0104) -/3
Image Acquisition Results
Performed Series Sequence (0040,0340) 3/2
>Performing Physician’s Name (0008,1050) -/2
>Protocol Name (0018,1030) -/1
>Operators’ Name (0008,1070) -/2
>Series Instance UID (0020,000E) -/1
>Series Description (0008,103E) -/2
>Retrieve AE Title (0008,0054) -/2
>Referenced Image Sequence (0008,1140) -/2
>>Referenced SOP Class UID (0008,1150) -/1
>>Referenced SOP Instance UID (0008,1155) -/1
>Referenced Non-Image Composite SOP Instance Sequence (0040,0220) -/2
>>Referenced SOP Class UID (0008,1150) -/1
>>Referenced SOP Instance UID (0008,1155) -/1
>All other Attributes from Performed Series Sequence -/3
Modality (0008,0060) 3/1
Study ID (0020,0010) 3/2
Performed Protocol Code Sequence (0040,0260) 3/2
>Code Value (0008,0100) -/1
>Coding Scheme Designator (0008,0102) -/1
>Coding Scheme Version (0008,0103) -/3
>Code Meaning (0008,0104) -/3
>All other Attributes from Performed Protocol Code Sequence -/3
All other attributes from Radiation Dose Module and Billing and Material Code Module 3/3

Notes: 1. Attributes (0040,1006) Placer Order Number/Procedure and (0040,1007) Filler Order Number/Procedure were previously defined in DICOM. They are now retired (See PS3.3 1998).

2. Attributes (0040,2006) and (0040,2007) were previously defined in DICOM. They are now retired (See PS3.3 1998).

F.8.2.1.2 Service Class User

The SCU uses the N-GET Service Element to request the SCP to get a Modality Performed Procedure Step Retrieve SOP Instance. The SCU shall specify in the N-GET request primitive the UID of the SOP Instance to be retrieved, which is a UID of a Modality Performed Procedure Step SOP Instance. The SCU shall be permitted to request that Attribute Values be returned for any Modality Performed Procedure Step Retrieve SOP Class Attribute specified in Table F.8.2-1. Additionally values may be requested for optional Modality Performed Procedure Step IOD Attributes.

The SCU shall specify the list of Modality Performed Procedure Step Retrieve SOP Class Attributes for which values are to be returned. The encoding rules for Modality Performed Procedure Step Attributes are specified in the N-GET request primitive specification in PS 3.7.

In an N-GET operation, the values of Attributes which are defined within a Sequence of Items shall not be requested by an SCU.

The SCU shall be capable of receiving all requested Attribute Values provided by the SCP in response to the N-GET indication primitive. The SCU may request Attribute Values for optional Attributes which are not maintained by the SCP. In such a case, the SCU shall function properly regardless of whether the SCP returns values for those Attributes or not. This Service Class Specification places no requirements on what the SCU shall do as a result of receiving this information.

Note: In order to accurately interpret the character set used for the Attribute Values returned, it is recommended that the Attribute Value for the Specific Character Set (0008,0005) be requested in the N-GET request primitive.

F.8.2.1.3 Service Class Provider

The N-GET operation allows the SCU to request from the SCP selected Attribute values for a specific Modality Performed Procedure Step SOP Instance via a Modality Performed Procedure Step Retrieve SOP Instance. This operation shall be invoked through the use of the DIMSE N-GET Service used in conjunction with the appropriate Modality Performed Procedure Step Retrieve SOP Instance which equals the Modality Performed Procedure SOP Instance. The SCP shall retrieve the selected Attribute values from the indicated Modality Performed Procedure Step SOP Instance.

The SCP shall return, via the N-GET response primitive, the N-GET Response Status Code applicable to the associated request. A Failure Code shall indicate that the SCP has not retrieved the SOP Instance. Contingent on the N-GET Response Status, the SCP shall return, via the N-GET response primitive, Attribute Values for all requested Attributes maintained by the SCP.

F.8.2.1.4 Status Codes

The status values which are specific for this SOP Class and DIMSE Service are defined in Table F.8.2-2. See PS 3.7 for additional response status codes.

Table F.8.2-2RESPONSE STATUS

Service Status Further Meaning Response Status Code
Warning Requested optional Attributes are not supported 0001

F.8.3 Modality Performed Procedure Step Retrieve SOP Class UID

The Modality Performed Procedure Step Retrieve SOP Class shall be uniquely identified by the Modality Performed Procedure Step Retrieve SOP Class UID which shall have the value “1.2.840.10008.3.1.2.3.4”.

F.8.4 Conformance Requirements

Implementations providing conformance to the Modality Performed Procedure Step Retrieve SOP Class shall be conformant as described in the following sections and shall include within their Conformance Statement information as described below.

An implementation may conform to this SOP Class as an SCU or as an SCP. The Conformance Statement shall be in the format defined in Annex A of PS 3.2.

F.8.4.1 SCU Conformance

An implementation which is conformant to this SOP Class as an SCU shall meet conformance requirements for the operations which it invokes.

F.8.4.1.1 Operations

Any Attributes for which Attribute Values may be requested (using the N-GET Service) by the SCU shall be enumerated in the SCU Operations Statement. The SCU Operations Statement shall be formatted as defined in Annex A of PS 3.2.

F.8.4.2 SCP Conformance

An implementation which is conformant to this SOP Class as an SCP shall meet conformance requirements for the operations which it performs.

F.8.4.2.1 Operations

Any Attributes for which Attribute Values may be requested (using the N-GET Service) by the SCU shall be enumerated in the SCP Operations Statement. The SCP Operations Statement shall be formatted as defined in Annex A of PS 3.2.

F.9 MODALITY performed Procedure step notification SOP class

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.

Notes: 1. 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.

2. 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.

F.9.1 DIMSE service group

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 PS 3.7.

Table F.9.1-1 DIMSE-N SERVICE GROUP

DIMSE Service Element Usage SCU/SCP
N-EVENT-REPORT M/M

F.9.2 Notifications

The Application Entity which claims conformance as an SCU to this SOP Class shall be permitted to receive the following notification. The Application Entity which 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

Note: The Notification Event Information contains no Attributes, beyond those defined in PS 3.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.

F.9.2.2 Provide Modality Performed Procedure Step Event Notification

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.

Note: The encoding of Notification Event Information is defined in PS 3.7.

F.9.2.3 Status Codes

There are no specific status codes. See PS 3.7 for response status codes.

F.9.3 Modality Performed Procedure Step Notification SOP Class UID

The Modality Performed Procedure Step Notification SOP Class shall be uniquely identified by the Modality Performed Procedure Step Notification SOP Class UID which shall have the value ”1.2.840.10008.3.1.2.3.5”.

F.9.4 Conformance Requirements

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 PS 3.2.

F.9.4.1 SCU Conformance

An implementation which is conformant to this SOP Class as an SCU shall meet conformance requirements for the:

F.9.4.1.1 Notifications

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;]

F.9.4.2 SCP Conformance

An implementation which is conformant to this SOP Class as an SCP shall meet conformance requirements for:

F.9.4.2.1 Notifications

Any optional Attributes which 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 PS 3.2. Following this statement shall be the list of event types and optional Attributes.

F.10 GENERAL PURPOSE SCHEDULED Procedure step SOP Class

F.10.1 DIMSE Service Group

The DIMSE Services shown in Table F.10.1-1 are applicable to the General Purpose Scheduled Procedure Step IOD under the General Purpose Scheduled Procedure Step SOP Class.

Table F.10.1-1

DIMSE SERVICE GROUP

DIMSE Service Element Usage SCU/SCP
N-ACTION M/M

The DIMSE Services and Protocols are specified in PS 3.7

F.10.2 Operations

The DICOM AEs that claim conformance to this SOP Class as an SCU shall invoke the N-ACTION operation. The DICOM AEs that claim conformance to this SOP Class as an SCP shall support the N-ACTION operation.

F.10.2.1 Modify General Purpose Scheduled Procedure Step Information Request

This operation allows an SCU to request the modification of Attribute Values of an instance of the General Purpose Scheduled Procedure Step SOP Class and provide information about a specific real-world General Purpose Scheduled Procedure Step that is under control of the SCP. This operation shall be invoked through the DIMSE N-ACTION Service.

F.10.2.1.1 Action Information

The Application Entity which claims conformance to this SOP Class as an SCU may choose to request the modification of a subset of the Attributes maintained by the SCP.

The DICOM AEs that claim conformance to this SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information as specified in Table F.10.2-1.

Table F.10.2-1MODIFY GP-SPS INFORMATION REQUEST – ACTION INFORMATION

Action Type Name Action Type ID Attribute Tag Requirement Type SCU/SCP
Request GP-SPS Status Modification 1 General Purpose Scheduled Procedure Step Status (0040,4001) 1/1
Transaction UID (0008,1195) 1/1
Actual Human Performers Sequence (0040,4035) 3/1
>Human Performer Code Sequence (0040,4009) 1/1
>>Code Value (0008,0100) 1/1
>>Coding Scheme designator (0008,0102) 1/1
>>Code Meaning (0008,0104) 1/1
>Human Performer’s Name (0040,4037) 3/3
>Human Performer’s Organization (0040,4036) 3/3

F.10.2.1.2 Service Class User Behavior

The SCU shall specify in the Requested SOP Instance UID parameter of the N-ACTION request primitive the UID of the General Purpose Scheduled Procedure Step SOP Instance for which it wants to modify Action Information, as specified in Table F.10.2-1.

Note: In the usage described here, there is no explicit creation of a SOP Instance upon which an N-ACTION primitive may operate. Instead, the N-ACTION primitive operates upon a SOP Instance previously created by the SCP. The SCU will retrieve the value for the SOP Instance UID by means of the General Purpose Worklist C-FIND service.

The SCU shall specify the requested value for the Attribute “General Purpose Scheduled Procedure Step Status” (0040,4001) in the Action Information.

The encoding rules for General Purpose Scheduled Procedure Step Action Information are specified in the N-ACTION request primitive specification in PS 3.7

The SCU shall not send N-ACTION request primitives for a General Purpose Scheduled Procedure Step SOP Instance when the Attribute “General Purpose Scheduled Procedure Step Status” (0040,4001) of that SOP Instance is “COMPLETED” or “DISCONTINUED”.

The SCU shall supply a “Transaction UID” Attribute (0008,1195) to identify the Modify GP-SPS Information Request that requests a modification of the value of the Attribute “General Purpose Scheduled Procedure Step Status” (0040,4001) to “IN PROGRESS”. The same Transaction UID shall be used to request a modification of the status from “IN PROGRESS” to: “SUSPENDED”, “SCHEDULED”, “COMPLETED” or “DISCONTINUED”. Once the status has any other value than “IN PROGRESS” this Transaction UID shall no longer be used.

Note: This “Transaction UID” Attribute (0008,1195) is used to identify the single transition into the “IN PROGRESS” state, not the ownership of the General Purpose Procedure Step SOP Instance.

F.10.2.1.3 Service Class Provider Behavior

The N-ACTION operation allows the SCU to request that the SCP update selected Attribute values for a specific General Purpose Scheduled Procedure Step SOP Instance. This operation shall be invoked through the use of the DIMSE N-ACTION Service used in conjunction with the appropriate General Purpose Scheduled Procedure Step SOP Instance.

The SCP shall return, via the N-ACTION response primitive, the N-ACTION Response Status Code applicable to the associated request. Contingent on the N-ACTION Response Status, the SCP shall update the Referenced General Purpose Scheduled Procedure Step Attributes.

The SCP shall accept N-ACTION request primitives for a SOP Instance only if the value of the Attribute “General Purpose Scheduled Procedure Step Status” (0040,4001) of that SOP Instance is “SCHEDULED” or “SUSPENDED” or “IN PROGRESS”. If the General Purpose Scheduled Procedure Step Status attribute has a value of “COMPLETED” or “DISCONTINUED”, the SCP shall send the failure status code as specified in Section F.10.2.1.4.

When the value of the Attribute “General Purpose Scheduled Procedure Step Status” (0040,4001) of the SOP Instance is “IN PROGRESS”, the SCP shall accept N-ACTION request primitives only if the Transaction UID of the request primitive equals the Transaction UID of the request primitive which has successfully requested the modification of the value of this Attribute to “IN PROGRESS”. If another value is used, the SCP shall send the failure status code as specified in Section F.10.2.1.4.

F.10.2.1.4 Status Codes

The status values which are specific for this SOP Class are defined in Table F.10.2-2.

Table F.10.2-2 SOP CLASS STATUS VALUES

Status Meaning Code
Success The requested modification of the attribute value is performed 0000
Failure Refused because General Purpose Scheduled Procedure Step Object may no longer be updated A501
Refused because the wrong Transaction UID is used. A502
Refused because the General Purpose Scheduled Procedure Step SOP Instance is already in the “IN PROGRESS” state A503

F.10.3 General Purpose Scheduled Procedure Step SOP Class UID

The General Purpose Scheduled Procedure Step SOP Class shall be uniquely identified by the General Purpose Scheduled Procedure Step SOP Class UID which shall have the value “1.2.840.10008.5.1.4.32.2”.

F.10.4 Conformance Requirements

Implementations providing conformance to the General Purpose Scheduled Procedure Step SOP Class shall be conformant as described in the following sections and shall include within their Conformance Statement information as described below.

An implementation may conform to this SOP Class as an SCU or as an SCP. The Conformance Statement shall be in the format defined in Annex A of PS 3.2.

An implementation which conforms to the General Purpose Scheduled Procedure Step SOP Class shall also support the General Purpose Worklist Management Meta SOP Class.

F.10.4.1 SCU Conformance

An implementation, which is conformant to this SOP Class as an SCU, shall meet conformance requirements for the operations that it invokes.

F.10.4.1.1 Operations

The SCU Conformance Statement shall be formatted as defined in Annex A of PS 3.2.

An implementation, which conforms to this SOP Class as an SCU, shall specify under which conditions during the performance of the real-world Performed Procedure Step it will request the modification of the value of the Attribute “General Purpose Scheduled Procedure Step Status” (0040,4001) to “IN PROGRESS”, “SUSPENDED”, “COMPLETED”,”DISCONTINUED”, and “SCHEDULED”.

F.10.4.2 SCP Conformance

An implementation which is conformant to this SOP Class as an SCP shall meet conformance requirements for the operations which it performs.

F.10.4.2.1 Operations

The SCP Conformance Statement shall be formatted as defined in Annex A of PS 3.2.

The SCP Conformance Statement shall provide information on the behavior of the SCP (the Workflow Manager) at the following occurrences:

F.11 General Purpose Performed Procedure step SOP Class

F.11.1 DIMSE Service Group

The DIMSE Services shown in Table F.11.1-1 are applicable to the General Purpose Performed Procedure Step IOD under the General Purpose Performed Procedure Step SOP Class.

Table F.11.1-1

DIMSE SERVICE GROUP

DIMSE Service Element Usage SCU/SCP
N-CREATE M/M
N-SET M/M
N-GET U/M

The DIMSE Services and Protocols are specified in PS 3.7

F.11.2 Operations

The Application Entity which claims conformance to this SOP Class as an SCU shall be permitted to invoke the following operations and the Application Entity which claims conformance as an SCP shall be capable of providing the following operations.

F.11.2.1 CREATE General Purpose Performed Procedure Step SOP Instance

This operation allows an SCU to create an instance of the General Purpose Performed Procedure Step SOP Class and provide information about a specific real-world Performed Procedure Step that is under control of the SCU. This operation shall be invoked through the DIMSE N-CREATE Service.

Note : Some of the attribute values are already known at the beginning of the General Purpose Performed Procedure Step. They are required to be sent in the N-CREATE command. Other mandatory attributes are known only at the end of the General Purpose Performed Procedure Step. They are assigned a value in the N-SET command.

F.11.2.1.1 General Purpose Performed Procedure Step Subset Specification

The Application Entity which claims conformance to this SOP Class as an SCU must provide all Required Attributes as specified in Table F.11.2-1. Optional Attributes maintained by the SCP may be provided as well. The Application Entity which claims conformance as an SCP to this SOP Class shall support the subset of the General Purpose Performed Procedure Step Attributes specified in Table F.11.2-1.

Table F.11.2-1 GENERAL PURPOSE PERFORMED PROCEDURE STEP SOP CLASS N-CREATE, N-SET AND FINAL STATE ATTRIBUTES

Attribute Name Tag Req. Type N-CREATE (SCU/SCP) Req. Type N-SET (SCU/SCP) Requirement Type Final State (See Note 1)
Specific Character Set (0008,0005) 1C/1C (Required if an extended or replacement character set is used) Not allowed
General Purpose Performed Procedure Step Relationship
Referenced Request Sequence (0040,A370) 2/2 Not allowed
>Study Instance UID (0020,000D) 1/1 Not allowed
>Referenced Study Sequence (0008,1110) 2/2 Not allowed
>>Referenced SOP Class UID (0008,1150) 1/1 Not allowed
>>Referenced SOP Instance UID (0008,1155) 1/1 Not allowed
>Accession Number (0008,0050) 2/2 Not allowed
>Issuer of Accession Number Sequence (0008,0051) 3/3 Not allowed
>>Local Namespace Entity ID (0040,0031) 1C/1C Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed
>>Universal Entity ID (0040,0032) 1C/1C Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise. Not allowed
>>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present. Not allowed
>Requested Procedure Code Sequence (0032,1064) 2/2 Not allowed
>>Code Value (0008,0100) 1/1 Not allowed
>>Coding Scheme designator (0008,0102) 1/1 Not allowed
>>Coding Scheme Version (0008,0103) 3/3 Not allowed
>>Code Meaning (0008,0104) 1/1 Not allowed
>Placer Order Number/Imaging Service Request (0040,2016) 3/3 Not allowed
>Order Placer Identifier Sequence (0040,0026) 3/3 Not allowed
>>Local Namespace Entity ID (0040,0031) 1C/1C Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed
>>Universal Entity ID (0040,0032) 1C/1C Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise. Not allowed
>>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present. Not allowed
>Filler Order Number/Imaging Service Request (0040,2017) 3/3 Not allowed
>Order Filler Identifier Sequence (0040,0027) 3/3 Not allowed
>>Local Namespace Entity ID (0040,0031) 1C/1C Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed
>>Universal Entity ID (0040,0032) 1C/1C Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise. Not allowed
>>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present. Not allowed
>Requested Procedure ID (0040,1001) 2/2 Not allowed
>Requested Procedure Description (0032,1060) 2/2 Not allowed
Referenced General Purpose Scheduled Procedure Step Sequence (0040,4016) 1C/1C Required if related General Purpose Scheduled Procedure Step exists Not allowed
>Referenced SOP Class UID (0008,1150) 1/1 Not allowed
>Referenced SOP Instance UID (0008,1155) 1/1 Not allowed
>Referenced General Purpose Scheduled Procedure Step Transaction UID (0040,4023) 1/1 Not allowed
Patient’s Name (0010,0010) 2/2 Not allowed
Patient ID (0010,0020) 2/2 Not allowed
Issuer of Patient ID (0010,0021) 3/3 Not allowed
Issuer of Patient ID Qualifiers Sequence (0010,0024) 3/3 Not allowed
>Universal Entity ID (0040,0032) 3/3 Not allowed
>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present. Not allowed
>All other attributes of Issuer of Patient ID Qualifiers Sequence 3/3 Not allowed
Patient’s Birth Date (0010,0030) 2/2 Not allowed
Patient’s Sex (0010,0040) 2/2 Not allowed
Admission ID (0038,0010) 3/3 Not allowed
Issuer of Admission ID Sequence (0038,0014) 3/3 Not allowed
>Local Namespace Entity ID (0040,0031) 1C/1C Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed
>Universal Entity ID (0040,0032) 1C/1C Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise. Not allowed
>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present. Not allowed
Service Episode ID (0038,0060) 3/3 Not allowed
Issuer of Service Episode ID Sequence (0038,0064) 3/3 Not allowed
>Local Namespace Entity ID (0040,0031) 1C/1C Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed
>Universal Entity ID (0040,0032) 1C/1C Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise. Not allowed
>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present. Not allowed
Service Episode Description (0038,0062) 3/3 Not allowed
General Purpose Performed Procedure Step Information
Actual Human Performers Sequence (0040,4035) 2/2 Not allowed
>Human Performer Code Sequence (0040,4009) 1/1 Not allowed
>>Code Value (0008,0100) 1/1 Not allowed
>>Coding Scheme Designator (0008,0102) 1/1 Not allowed
>>Coding Scheme Version (0008,0103) 3/3 Not allowed
>>Code Meaning (0008,0104) 1/1 Not allowed
>Human Performer’s Name (0040,4037) 3/3 Not allowed
>Human Performer’s Organization (0040,4036) 3/3 Not allowed
Performed Procedure Step ID (0040,0253) 1/1 Not allowed
Performed Station Name Code Sequence (0040,4028) 2/2 Not allowed
>Code Value (0008,0100) 1/1 Not allowed
>Coding Scheme Designator (0008,0102) 1/1 Not allowed
>Coding Scheme Version (0008,0103) 3/3 Not allowed
>Code Meaning (0008,0104) 1/1 Not allowed
Performed Station Class Code Sequence (0040,4029) 2/2 Not allowed
>Code Value (0008,0100) 1/1 Not allowed
>Coding Scheme Designator (0008,0102) 1/1 Not allowed
>Coding Scheme Version (0008,0103) 3/3 Not allowed
>Code Meaning (0008,0104) 1/1 Not allowed
Performed Station Geographic Location Code Sequence (0040,4030) 2/2 Not allowed
>Code Value (0008,0100) 1/1 Not allowed
>Coding Scheme Designator (0008,0102) 1/1 Not allowed
>Coding Scheme Version (0008,0103) 3/3 Not allowed
>Code Meaning (0008,0104) 1/1 Not allowed
Performed Processing Applications Code Sequence (0040,4007) 2/2 Not Allowed
>Code Value (0008,0100) 1/1 Not allowed
>Coding Scheme Designator (0008,0102) 1/1 Not allowed
>Coding Scheme Version (0008,0103) 3/3 Not allowed
>Code Meaning (0008,0104) 1/1 Not allowed
Performed Procedure Step Start Date (0040,0244) 1/1 Not allowed
Performed Procedure Step Start Time (0040,0245) 1/1 Not allowed
General Purpose Performed Procedure Step Status (0040,4002) 1/1 3/1
Performed Procedure Step Description (0040,0254) 2/2 3/2
Comments on the Performed Procedure Step (0040,0280) 3/3 3/3
Performed Workitem Code Sequence (0040,4019) 2/2 Not allowed
>Code Value (0008,0100) 1/1 Not allowed
>Coding Scheme designator (0008,0102) 1/1 Not allowed
>Coding Scheme Version (0008,0103) 3/3 Not allowed
>Code Meaning (0008,0104) 1/1 Not allowed
Performed Procedure Step End Date (0040,0250) 2/2 3/1 1
Performed Procedure Step End Time (0040,0251) 2/2 3/1 1
General Purpose Results
Output Information Sequence (0040,4033) 2/2 2/2 See F.11.2.2.2.
>Study Instance UID (0020,000D) 1/1 1/1
>Referenced Series Sequence (0008,1115) 1/1 1/1
>>Series Instance UID (0020,000E) 1/1 1/1
>>Retrieve AE Title (0008,0054) 2C/2 (Required if Storage Media File-Set ID (0088,0130) or Storage Media File-Set UID (0088,0140) is not present) 2C/2 (Required if Storage Media File-Set ID (0088,0130) or Storage Media File-Set UID (0088,0140) is not present)
>>Storage Media File-Set ID (0088,0130) 2C/2 (Required if Retrieve AE Title (0008,0054) is not present) 2C/2 (Required if Retrieve AE Title (0008,0054) is not present)
>>Storage Media File-Set UID (0088,0140) 2C/2 (Required if Retrieve AE Title (0008,0054) is not present) 2C/2 (Required if Retrieve AE Title (0008,0054) is not present)
>>Referenced SOP Sequence (0008,1199) 1/1 1/1
>>>Referenced SOP Class UID (0008,1150) 1/1 1/1
>>>Referenced SOP Instance UID (0008,1155) 1/1 1/1
Requested Subsequent Workitem Code Sequence (0040,4031) 2/2 2/2
>Code Value (0008,0100) 1/1 1/1
>Coding Scheme Designator (0008,0102) 1/1 1/1
>Coding Scheme Version (0008,0103) 3/3 3/3
>Coding Meaning (0008,0104) 1/1 1/1
Non-DICOM Output Code Sequence (0040,4032) 2/2 2/2
>Code Value (0008,0100) 1/1 1/1
>Coding Scheme Designator (0008,0102) 1/1 1/1
>Coding Scheme Version (0008,0103) 3/3 3/3
>Coding Meaning (0008,0104) 1/1 1/1

Note: The requirement for the final state is that which applies at the time that the General Purpose Performed Procedure Step Status (0040,4002) is N-SET to a value of COMPLETED or DISCONTINUED, as described in F.11.2.2.2. It is only described if it is different from the SCP requirement for the N-CREATE.

F.11.2.1.2 Service Class User

The SCU shall specify in the N-CREATE request primitive the SOP Class and SOP Instance UIDs of the General Purpose Performed Procedure Step SOP Instance which is created and for which Attribute Values are to be provided.

The SCU shall provide Attribute values for the General Purpose Performed Procedure Step SOP Class Attributes as specified in Table F.11.2-1. Additionally, values may be provided for optional General Purpose Performed Procedure Step IOD Attributes that are supported by the SCP. The encoding rules for General Purpose Performed Procedure Step Attributes are specified in the N-CREATE request primitive specification in PS 3.7.

The SCU shall be capable of providing all required Attribute values to the SCP in the N-CREATE request primitive. The SCU may provide Attribute values for optional Attributes which are not maintained by the SCP. In such case the SCU shall function properly regardless of whether the SCP accepts values for those Attributes or not.

All Attributes shall be created before they can be set. Sequence Attributes shall be created before they can be filled. Sequence Item Attributes shall not be created at zero length.

Note: Not all the attributes that can be created can be set afterwards (see Table F.11.2-1).

The SCU shall only send the N-CREATE request primitive with the value for the Attribute “General Purpose Performed Procedure Step Status” (0040,4002) set to “IN PROGRESS”.

F.11.2.1.3 Service Class Provider

The N-CREATE operation allows the SCU to provide to the SCP selected Attribute values for a specific General Purpose Performed Procedure Step SOP Instance. This operation shall be invoked through the use of the DIMSE N-CREATE Service used in conjunction with the appropriate General Purpose Performed Procedure Step SOP Instance.

The SCP shall return, via the N-CREATE response primitive, the N-CREATE Response Status Code applicable to the associated request.

The SCP shall accept N-CREATE request primitives only if the value of the Attribute “General Purpose Performed Procedure Step Status” (0040,4002) is “IN PROGRESS”. If the General Purpose Performed Procedure Step Status attribute has another value, the SCP shall set the failure status code “Invalid attribute value” (Code: 0106H) with an Attribute List.

If the General Purpose Performed Procedure Step SOP Instance is related to a general Purpose Scheduled Procedure Step SOP Instance, then the SCP shall accept N-CREATE request primitives only if the value of the Attribute “General Purpose Scheduled Procedure Step Status” (0040,4001) has the value “IN PROGRESS”. If the General Purpose Scheduled Procedure Step Status attribute has another value, the SCP shall send the failure status code as specified in Section F.11.2.1.4.

If a Referenced General Purpose Scheduled Procedure Step Sequence (0040,4016) item is present in the N-CREATE request, then the Referenced General Purpose Scheduled Procedure Step Transaction UID (0040,4023) contained therein shall be the same as the Transaction UID (0008,1195) that identifies the transaction of the General Purpose Scheduled Procedure Step Status (0040,4001) to “IN PROGRESS”. If the Transaction UIDs do not match, the SCP shall send the failure status code as specified in Section F.11.2.1.4.

Note: In the unscheduled case no related General Purpose Scheduled Procedure Step exists, so the rules for the Transaction UID do not apply.

If a Referenced General Purpose Scheduled Procedure Step Sequence (0040,4016) item is present in the N-CREATE request, the SCP shall update the Attribute Resulting General Purpose Performed Procedure Steps Sequence (0040,4015) in the identified General Purpose Scheduled Procedure Step SOP Instance.

Note: The SCP may update the scheduling information on which the General Purpose Worklist is based, including the values of Study Date (0008,0020) and Study Time (0008,0030) using the earliest corresponding values of Performed Procedure Step Date (0040,0244) and Performed Procedure Step Time (0040,0245), in order to achieve consistency of Study level attributes when multiple procedure steps are performed on different devices.

F.11.2.1.4 Status Codes

The status values which are specific for this SOP Class are defined in Table F.11.2-2.

Table F.11.2-2 SOP CLASS STATUS VALUES

Service Status Meaning Status Code
Failure Refused because the related General Purpose Scheduled Procedure Step SOP Instance is not in the “IN PROGRESS” state. A504
Refused because Referenced General Purpose Scheduled Procedure Step Transaction UID does not match the Transaction UID of the N-ACTION request. A505

F.11.2.2 SET General Purpose Performed Procedure Step Information

This operation allows an SCU to set Attribute Values of an instance of the General Purpose Performed Procedure Step SOP Class and provide information about a specific real-world General Purpose Performed Procedure Step that is under control of the SCU. This operation shall be invoked through the DIMSE N-SET Service.

F.11.2.2.1 General Purpose Performed Procedure Step IOD Subset Specification

The Application Entity which claims conformance to this SOP Class as an SCU may choose to modify a subset of the Attributes maintained by the SCP. The Application Entity which claims conformance as an SCP to this SOP Class shall support the subset of the General Purpose Performed Procedure Step Attributes specified in Table F.11.2-1.

The character set used for Attribute Values updated using the N-SET shall be the same as that specified by the N-CREATE Request Primitive.

F.11.2.2.2 Service Class User

The SCU shall specify in the N-SET request primitive the UID of the General Purpose Performed Procedure Step SOP Instance for which it wants to set Attribute Values.

The SCU shall be permitted to set Attribute values for any General Purpose Performed Procedure Step SOP Class Attribute specified in Table F.11.2-1. The SCU shall specify the list of General Purpose Performed Procedure Step SOP Class Attributes for which it wants to set the Attribute Values. The SCU shall provide, with one or more N-SET request primitives, the attribute values specified in Table F.11.2-1. The encoding rules for General Purpose Performed Procedure Step Attributes are specified in the N-SET request primitive specification in PS 3.7. The SCU shall only set Attribute Values which are already created with an N-CREATE request.

The SCU shall not send N-SET request primitives for a General Purpose Performed Procedure Step SOP Instance after a N-SET request primitive with a value for the attribute “General Purpose Performed Procedure Step Status” (0040,4002) is “COMPLETED” or “DISCONTINUED” has been sent.

Once the General Purpose Performed Procedure Step Status (0040,4002) has been set to “COMPLETED” or “DISCONTINUED” the SCU shall no longer modify the General Purpose Performed Procedure Step SOP Instance, and shall not create new Composite SOP Instances as part of the same General Purpose Performed Procedure Step SOP Instance.

If Sequences are included in a N-SET command, all Items of a Sequence are to be included in the command and not only the Items to be updated.

Before or when General Purpose Performed Procedure Step Status (0040,4002) is set to “COMPLETED” or “DISCONTINUED” the SCU shall have created or set all the Attributes according to the requirements in the Final State column of Table F.11.2-1.

Before or when General Purpose Performed Procedure Step Status (0040,4002) is set to “COMPLETED” or “DISCONTINUED” the SCU shall have sent to the SCP a list of all Composite SOP Instances created during the Procedure Step in Output Information Sequence (0040,4033).

Note: The intent is that a completed or discontinued General Purpose Performed Procedure Step entity will contain a complete list of all the Composite Instances that were created.

The General Purpose Performed Procedure Step Status (0040,4002) shall not be set to “COMPLETED” or “DISCONTINUED” if the list contains no Composite Instance references, unless no such Instances were created.

F.11.2.2.3 Service Class Provider

The N-SET operation allows the SCU to request that the SCP update selected Attribute values for a specific General Purpose Performed Procedure Step SOP Instance. This operation shall be invoked through the use of the DIMSE N-SET Service used in conjunction with the appropriate General Purpose Performed Procedure Step SOP Instance.

The SCP shall return, via the N-SET response primitive, the N-SET Response Status Code applicable to the associated request. Contingent on the N-SET Response Status, the SCP shall update the Referenced Performed Procedure Step Attributes.

The SCP shall accept N-SET request primitives only if the value of the already existing attribute “General Purpose Performed Procedure Step Status” (0040,4002) is “IN PROGRESS”. If the already existing General Purpose Performed Procedure Step Status attribute has another value, the SCP shall send the failure status code as specified in Section F.11.2.2.4.

The SCP may itself modify any Attributes of the General Purpose Performed Procedure Step SOP Instance only after the “General Purpose Performed Procedure Step Status” (0040,4002) has been set to “COMPLETED” or “DISCONTINUED”, or when error conditions require such a modification.

Note: Under exceptional circumstances, it may be necessary for the SCP to itself set the Performed Procedure Step Status (0040,0252) to COMPLETED or DISCONTINUED, for example if the performing device has failed. When the SCU recovers, subsequent N-SETs may fail.

F.11.2.2.4 Status Codes

The status values which are specific for this SOP Class are defined in Table F.11.2-3a.

Table F.11.2-3a SOP CLASS STATUS VALUES

Service Status Meaning Status Code
Failure Refused because the General Purpose Performed Procedure Step SOP Instance is not in the “IN PROGRESS” state A506

F.11.2.3 GET General Purpose Performed Procedure Step Information

This operation allows an SCU to get information about a specific real-world Performed Procedure Step which is represented as a General Purpose Performed Procedure Step SOP Instance by a General Purpose Performed Procedure Step SCP. The operation is performed on a General Purpose Performed Procedure Step IOD. This operation shall be invoked through the DIMSE N-GET Service used in conjunction with the appropriate General Purpose Performed Procedure Step SOP Instance.

F.11.2.3.1 General Purpose Performed Procedure Step IOD Subset Specifications

The Application Entity which claims conformance to this SOP Class as an SCU may choose to interpret the Attribute values maintained by the SCP which the SCU receives via the operation of this SOP Class. The Application Entity which claims conformance as an SCP to this General Purpose Performed Procedure Step SOP Class shall support the subset of the General Purpose Performed Procedure Step Attributes specified in Table F.11.2-3.

Table F.11.2-3

GENERAL PURPOSE PERFORMED PROCEDURE STEP SOP CLASS N-GET ATTRIBUTES

Attribute Name Tag Requirement Type (SCU/SCP)
Specific Character Set (0008,0005) 3/1C (Required if an extended or replacement character set is used)
General Purpose Performed Procedure Step Relationship
Referenced Request Sequence (0040,A370) 3/2
>Study Instance UID (0020,000D) -/1
>Referenced Study Sequence (0008,1110) -/2
>>Referenced SOP Class UID (0008,1150) -/1
>>Referenced SOP Instance UID (0008,1155) -/1
>Accession Number (0008,0050) -/2
>Issuer of Accession Number Sequence (0008,0051) -/3
>>Local Namespace Entity ID (0040,0031) -/3
>>Universal Entity ID (0040,0032) -/3
>>Universal Entity ID Type (0040,0033) -/3
>Requested Procedure Code Sequence (0032,1064) -/2
>>Code Value (0008,0100) -/1
>>Coding Scheme Designator (0008,0102) -/1
>>Coding Scheme Version (0008,0103) -/3
>>Code Meaning (0008,0104) -/1
>Placer Order Number/Imaging Service Request (0040,2016) -/3
>Order Placer Identifier Sequence (0040,0026) -/3
>>Local Namespace Entity ID (0040,0031) -/3
>>Universal Entity ID (0040,0032) -/3
>>Universal Entity ID Type (0040,0033) -/3
>Filler Order Number/Imaging Service Request (0040,2017) -/3
>Order Filler Identifier Sequence (0040,0027) -/3
>>Local Namespace Entity ID (0040,0031) -/3
>>Universal Entity ID (0040,0032) -/3
>>Universal Entity ID Type (0040,0033) -/3
>Requested Procedure ID (0040,1001) -/2
>Requested Procedure Description (0032,1060) -/2
Referenced General Purpose Scheduled Procedure Step Sequence (0040,4016) 3/2
>Referenced SOP Class UID (0008,1150) -/1
>Referenced SOP Instance UID (0008,1155) -/1
>Referenced General Purpose Scheduled Procedure Step Transaction UID (0040,4023) -/1
Patient’s Name (0010,0010) 3/2
Patient ID (0010,0020) 3/2
Issuer of Patient ID (0010,0021) 3/3
Issuer of Patient ID Qualifiers Sequence (0010,0024) 3/3
>Universal Entity ID (0040,0032) 3/3
>Universal Entity ID Type (0040,0033) 1C/1C Required if Universal Entity ID (0040,0032) is present.
>All other attributes of Issuer of Patient ID Qualifiers Sequence 3/3
Patient’s Birth Date (0010,0030) 3/2
Patient’s Sex (0010,0040) 3/2
Admission ID (0038,0010) -/3
Issuer of Admission ID Sequence (0038,0014) 3/3
>Local Namespace Entity ID (0040,0031) -/3
>Universal Entity ID (0040,0032) -/3
>Universal Entity ID Type (0040,0033) -/3
Service Episode ID (0038,0060) -/3
Issuer of Service Episode ID Sequence (0038,0064) 3/3
>Local Namespace Entity ID (0040,0031) -/3
>Universal Entity ID (0040,0032) -/3
>Universal Entity ID Type (0040,0033) -/3
Service Episode Description (0038,0062) -/3
General Purpose Performed Procedure Step Information
Actual Human Performers Sequence (0040,4035) -/2
>Human Performer Code Sequence (0040,4009) -/1
>>Code Value (0008,0100) -/1
>>Coding Scheme Designator (0008,0102) -/1
>>Coding Scheme Version (0008,0103) -/3
>>Code Meaning (0008,0104) -/1
>Human Performer’s Name (0040,4037) -/3
>Human Performer’s Organization (0040,4036) -/3
Performed Procedure Step ID (0040,0253) 3/1
Performed Station Name Code Sequence (0040,4028) 3/2
>Code Value (0008,0100) -/1
>Coding Scheme Designator (0008,0102) -/1
>Coding Scheme Version (0008,0103) -/3
>Code Meaning (0008,0104) -/1
Performed Station Class Code Sequence (0040,4029) 3/2
>Code Value (0008,0100) -/1
>Coding Scheme Designator (0008,0102) -/1
>Coding Scheme Version (0008,0103) -/3
>Code Meaning (0008,0104) -/1
Performed Station Geographic Location Code Sequence (0040,4030) 3/2
>Code Value (0008,0100) -/1
>Coding Scheme Designator (0008,0102) -/1
>Coding Scheme Version (0008,0103) -/3
>Code Meaning (0008,0104) -/1
Performed Processing Applications Code Sequence (0040,4007) 3/2
>Code Value (0008,0100) -/1
>Coding Scheme Designator (0008,0102) -/1
>Coding Scheme Version (0008,0103) -/3
>Code Meaning (0008,0104) -/1
Performed Procedure Step Start Date (0040,0244) 3/1
Performed Procedure Step Start Time (0040,0245) 3/1
General Purpose Performed Procedure Step Status (0040,4002) 3/1
Performed Procedure Step Description (0040,0254) 3/2
Comments on the Performed Procedure Step (0040,0280) 3/3
Performed Workitem Code Sequence (0040,4019) 3/2
>Code Value (0008,0100) -/1
>Coding Scheme Designator (0008,0102) -/1
>Coding Scheme Version (0008,0103) -/3
>Code Meaning (0008,0104) -/1
Performed Procedure Step End Date (0040,0250) 3/2
Performed Procedure Step End Time (0040,0251) 3/2
General Purpose Results
Output Information Sequence (0040,4033) -/2
>Study Instance UID (0020,000D) -/1
>Referenced Series Sequence (0008,1115) -/1
>>Series Instance UID (0020,000E) -/1
>>Retrieve AE Title (0008,0054) -/2C Shall not be present if Storage Media File-Set ID (0088,0130) or Storage Media File-Set UID (0088,0140) is present.
>>Storage Media File-Set ID (0088,0130) -/2C Shall not be present if Retrieve AE Title (0008,0054) is present.
>>Storage Media File-Set UID (0088,0140) -/2C Shall not be present if Retrieve AE Title (0008,0054) is present.
>>Referenced SOP Sequence (0008,1199) -/1
>>>Referenced SOP Class UID (0008,1150) -/1
>>>Referenced SOP Instance UID (0008,1155) -/1
Requested Subsequent Workitem Code Sequence (0040,4031) 3/2
>Code Value (0008,0100) -/1
>Coding Scheme Designator (0008,0102) -/1
>Coding Scheme Version (0008,0103) -/3
>Code Meaning (0008,0104) -/1
Non-DICOM output Code Sequence (0040,4032) 3/2
>Code Value (0008,0100) -/1
>Coding Scheme Designator (0008,0102) -/1
>Coding Scheme Version (0008,0103) -/3
>Code Meaning (0008,0104) -/1

F.11.2.3.2 Service Class User

The SCU uses the N-GET Service Element to request the SCP to get a General Purpose Performed Procedure Step SOP Instance. The SCU shall specify in the N-GET request primitive the UID of the SOP Instance to be retrieved. The SCU shall be permitted to request that Attribute Values be returned for any General Purpose Performed Procedure Step SOP Class Attribute specified in Table F.11.2-3. Additionally values may be requested for optional General Purpose Performed Procedure Step IOD Attributes.

The SCU shall specify the list of General Purpose Performed Procedure Step SOP Class Attributes for which values are to be returned. The encoding rules for General Purpose Performed Procedure Step Attributes are specified in the N-GET request primitive specification in PS 3.7.

In an N-GET operation, the values of Attributes which are defined within a Sequence of Items shall not be requested by an SCU.

The SCU shall be capable of receiving all requested Attribute Values provided by the SCP in response to the N-GET indication primitive. The SCU may request Attribute Values for optional Attributes which are not maintained by the SCP. In such a case, the SCU shall function properly regardless of whether the SCP returns values for those Attributes or not. This Service Class Specification places no requirements on what the SCU shall do as a result of receiving this information.

Note: In order to accurately interpret the character set used for the Attribute Values returned, it is recommended that the Attribute Value for the Specific Character Set (0008,0005) be requested in the N-GET request primitive.

F.11.2.3.3 Service Class Provider

The N-GET operation allows the SCU to request from the SCP selected Attribute values for a specific General Purpose Performed Procedure Step SOP Instance. This operation shall be invoked through the use of the DIMSE N-GET Service used in conjunction with the appropriate General Purpose Performed Procedure Step SOP Instance. The SCP shall retrieve the selected Attribute values from the indicated General Purpose Performed Procedure Step SOP Instance.

The SCP shall return, via the N-GET response primitive, the N-GET Response Status Code applicable to the associated request. A Failure Code shall indicate that the SCP has not retrieved the SOP Instance. Contingent on the N-GET Response Status, the SCP shall return, via the N-GET response primitive, Attribute Values for all requested Attributes maintained by the SCP.

F.11.2.3.4 Status Codes

The status values which are specific for this SOP Class and DIMSE Service are defined in Table F.11.2-4. See PS 3.7 for additional response status codes.

Table F.11.2-4N-GET STATUS

Service Status Further Meaning Response Status Code
Warning Requested optional Attributes are not supported 0001

F.11.3 General Purpose Performed Procedure Step SOP Class UID

The General Purpose Performed Procedure Step SOP Class shall be uniquely identified by the General Purpose Performed Procedure Step SOP Class UID which shall have the value “1.2.840.10008.5.1.4.32.3”.

F.11.4 Conformance Requirements

Implementations providing conformance to the General Purpose Performed Procedure Step SOP Class shall be conformant as described in the following sections and shall include within their Conformance Statement information as described below.

An implementation may conform to this SOP Class as an SCU or as an SCP. The Conformance Statement shall be in the format defined in Annex A of PS 3.2.

An implementation which conforms to the General Purpose Performed Procedure Step SOP Class shall also support the General Purpose Worklist Management Meta SOP Class.

F.11.4.1 SCU Conformance

An implementation which is conformant to this SOP Class as an SCU shall meet conformance requirements for the operations which it invokes.

F.11.4.1.1 Operations

Any Attributes for which Attribute Values may be provided (using the N-CREATE Service) by the SCU shall be enumerated in the SCU Conformance Statement. The SCU Conformance Statement shall be formatted as defined in Annex A of PS 3.2.

Any Attributes for which Attribute Values may be provided (using the N-SET Service) by the SCU shall be enumerated in the SCU Conformance Statement.

An implementation which conforms to this SOP Class as an SCU shall specify under which conditions during the performance of the real-world Performed Procedure Step it will create the SOP Class Instance and under which conditions it will set the General Purpose Performed Procedure Step Status (0040,4002) value to COMPLETED and DISCONTINUED.

Any Attributes for which Attribute Values may be requested (using the N-GET Service) by the SCU shall be enumerated in the SCU Conformance Statement.

F.11.4.2 SCP Conformance

An implementation which is conformant to this SOP Class as an SCP shall meet conformance requirements for the operations which it performs.

F.11.4.2.1 Operations

Any Attributes for which Attribute Values may be provided (using the N-CREATE Service) by the SCU shall be enumerated in the SCP Conformance Statement. The SCP Conformance Statement shall be formatted as defined in Annex A of PS 3.2.

Any Attributes for which Attribute Values may be updated (using the N-SET Service) by the SCU shall be enumerated in the SCP Conformance Statement.

Any Attributes for which Attribute Values may be requested (using the N-GET Service) by the SCU shall be enumerated in the SCP Conformance Statement.

The SCP Conformance Statement shall also provide information on the behavior of the SCP (the Information System) at the following occurrences: