DICOM PS3.4 2017a - Service Class Specifications

CC.2.5 Create a Unified Procedure Step (N-CREATE)
Prev | CC.2 DIMSE Service Groups | Next

### CC.2.5 Create a Unified Procedure Step (N-CREATE)

This operation allows an SCU to instruct an SCP to create a Unified Procedure Step. This operation shall be invoked by the SCU through the DIMSE N-CREATE Service.

#### CC.2.5.1 Unified Procedure Step Attribute Specification

An Application Entity that claims conformance to the UPS Push SOP Class as an SCU shall provide all Required Attributes as specified in Table CC.2.5-3. Additional Attributes defined by the UPS IOD may be provided as well.

An Application Entity that claims conformance to the UPS Push SOP Class as an SCP shall support all required Attributes as specified in Table CC.2.5-3. Additional Attributes defined by the UPS IOD may be supported as well.

##### CC.2.5.1.1 UPS Final State Requirements

COMPLETED and CANCELED are Final States for a UPS instance. The Attributes and values of the UPS instance must meet certain requirements before it may be placed in either of the Final States.

### Note

A UPS instance is in the SCHEDULED state when created. See Section CC.1.1 for rules governing state transitions.

Attributes shall be valued as indicated by the Final State Codes in the Final State Column of Table CC.2.5-3 before the Procedure Step State (0074,1000) may be set to COMPLETED or CANCELED (i.e., Final State).

Performing systems are encouraged to ensure that the values for all Attributes reasonably reflect what was done and the Final State of the UPS. This may include blanking Attributes that are permitted to be empty and for which no reasonable value can be determined. The UPS contents should make it clear whether the step was completed, what work was done, what results were produced and whether the results are usable. See Section GGG.3.1 “What Was Scheduled Vs. What Was Performed” in PS3.17 for a discussion of methods to convey things like partial completion.

### Note

The SCU may choose not to distribute, or otherwise make available, some or all instances created during the procedure step and referenced in the Output Information Sequence (0040,4033).

Table CC.2.5-1. Final State Codes

Final State Code | Meaning
--- | ---
R | The UPS State shall not be set to COMPLETED or CANCELED if this Attribute does not have a value.
RC | The UPS State shall not be set to COMPLETED or CANCELED if the condition is met and this Attribute does not have a value.
P | The UPS State shall not be set to COMPLETED if this Attribute does not have a value, but may be set to CANCELED.
X | The UPS State shall not be set to CANCELED if this Attribute does not have a value, but may be set to COMPLETED.
O | The UPS State may be set to either COMPLETED or CANCELED if this Attribute does not have a value.

##### CC.2.5.1.2 UPS Macros

To reduce the size and complexity of Table CC.2.5-3, a macro notation is used.

For example, in Table CC.2.5-3, a table entry specifying "Include Table CC.2.5-2a “UPS Code Sequence Macro”" should be interpreted as including the following table of text as a substitution. The nesting level for the sequence inclusion is indicated by the nesting level on the reference to the macro. Where the matching key type requirement is "*" it should be replaced with the matching key type requirement of the sequence Attribute that incorporates this macro.

For code sequences that have requirements for N-CREATE, N-SET, N-GET, or C-FIND behavior that differ from the Macro, the code sequence contents are explicitly listed in the Table rather than specifying inclusion of the Macro.

Table CC.2.5-2a. UPS Code Sequence Macro

Attribute Name | Tag | Req. Type N-CREATE (SCU/SCP) | Req. Type N-SET (SCU/SCP) | Final State | Req. Type N-GET (SCU/SCP) | Match Key Type | Return Key Type | Remark/Matching Type
--- | --- | --- | --- | --- | --- | --- | --- | ---
Code Value | (0008,0100) | 1/1 | 1/1 |  | -/1 | * | 1 | Code Value shall be retrieved with Single Value Matching.
Coding Scheme Designator | (0008,0102) | 1/1 | 1/1 |  | -/1 | * | 1 | Coding Scheme Designator shall be retrieved with Single Value Matching.
Coding Scheme Version | (0008,0103) | 1C/1C | 1C/1C |  | -/1 | - | 1C | Required if the value of Coding Scheme Designator (0008,0102) is not sufficient to identify the Code Value (0008,0100) unambiguously.
Code Meaning | (0008,0104) | 1/1 | 1/1 |  | -/1 | - | 1 | Code Meaning shall not be used as Matching Key.

Table CC.2.5-2b. UPS Content Item Macro

Attribute Name | Tag | Req. Type N-CREATE (SCU/SCP) | Req. Type N-SET (SCU/SCP) | Final State | Req. Type N-GET (SCU/SCP) | Match Key Type | Return Key Type | Remark/Matching Type
--- | --- | --- | --- | --- | --- | --- | --- | ---
Value Type | (0040,A040) | 1/1 | 1/1 |  | -/1 | * | 1 | The type of the value encoded in this name-value Item. Enumerated Values: DATETIME DATE TIME PNAME UIDREF TEXT CODE NUMERIC
Concept Name Code Sequence | (0040,A043) | 1/1 | 1/1 |  | -/1 | * | 1 | Coded concept name of this name-value Item.
>Include Table CC.2.5-2a “UPS Code Sequence Macro” | No Baseline CID is defined.
DateTime | (0040,A120) | 1C/1C | 1/1 |  | -/1 | * | 1C | Datetime value for this name-value Item. Required if Value Type (0040,A040) is DATETIME.
Date | (0040,A121) | 1C/1C | 1/1 |  | -/1 | * | 1C | Date value for this name-value Item. Required if Value Type (0040,A040) is DATE.
Time | (0040,A122) | 1C/1C | 1/1 |  | -/1 | * | 1C | Time value for this name-value Item. Required if Value Type (0040,A040) is TIME.
Person Name | (0040,A123) | 1C/1C | 1/1 |  | -/1 | * | 1C | Person name value for this name-value Item. Required if Value Type (0040,A040) is PNAME.
UID | (0040,A124) | 1C/1C | 1/1 |  | -/1 | * | 1C | UID value for this name-value Item. Required if Value Type (0040,A040) is UIDREF.
Text Value | (0040,A160) | 1C/1C | 1/1 |  | -/1 | * | 1C | Text value for this name-value Item. Required if Value Type (0040,A040) is TEXT.
Concept Code Sequence | (0040,A168) | 1C/1C | 1/1 |  | -/1 | * | 1C | Coded concept value of this name-value Item. Required if Value Type (0040,A040) is CODE.
>Include Table CC.2.5-2a “UPS Code Sequence Macro” | No Baseline CID is defined.
Numeric Value | (0040,A30A) | 1C/1C | 1/1 |  | -/1 | * | 1C | Numeric value for this name-value Item. Required if Value Type (0040,A040) is NUMERIC.
Measurement Units Code Sequence | (0040,08EA) | 1C/1C | 1/1 |  | -/1 | * | 1C | Units of measurement for a numeric value in this name-value Item. Required if Value Type (0040,A040) is NUMERIC.
>Include Table CC.2.5-2a “UPS Code Sequence Macro” | Baseline CID 82 “Units of Measurement”

Table CC.2.5-2c. Referenced Instances and Access Macro

Attribute Name | Tag | Req. Type N-CREATE (SCU/SCP) | Req. Type N-SET (SCU/SCP) | Final State | Req. Type N-GET (SCU/SCP) | Match Key Type | Return Key Type | Remark/Matching Type
--- | --- | --- | --- | --- | --- | --- | --- | ---
Type of Instances | (0040,E020) | 1/1 | 1/1 |  | -/1 | O | 1 |
Study Instance UID | (0020,000D) | 1C/1 | 1C/1 |  | -/1 | O | 1C | Required if Type of Instances (0040,E020) is DICOM
Series Instance UID | (0020,000E) | 1C/1 | 1C/1 |  | -/1 | O | 1C | Required if Type of Instances (0040,E020) is DICOM
Referenced SOP Sequence | (0008,1199) | 1/1 | 1/1 |  | -/1 | O | 1 |
>Referenced SOP Class UID | (0008,1150) | 1/1 | 1/1 |  | -/1 | O | 1 |
>Referenced SOP Instance UID | (0008,1155) | 1/1 | 1/1 |  | -/1 | O | 1 |
>HL7 Instance Identifier | (0040,E001) | 1C/1 | 1C/1 |  | -/1 | O | 1C | Required if Type of Instances (0040,E020) is CDA.
>Referenced Frame Number | (0008,1160) | 1C/1 | 1C/1 |  | -/2 | O | 1C | Required if the Referenced SOP Instance is a multi-frame image and the reference does not apply to all frames, and Referenced Segment Number (0062,000B) is not present.
>Referenced Segment Number | (0062,000B) | 1C/1 | 1C/1 |  | -/2 | O | 1C | Required if the Referenced SOP Instance is a Segmentation and the reference does not apply to all segments and Referenced Frame Number (0008,1160) is not present.
DICOM Retrieval Sequence | (0040,E021) | 1C/1 | 1C/1 |  | -/1 | O | 1C | Required if DICOM Media Retrieval Sequence (0040,E022), WADO Retrieval Sequence (0040,E023), WADO-RS Retrieval Sequence (0040,E025) and XDS Retrieval Sequence (0040,E024) are not present. May be present otherwise.
>Retrieve AE Title | (0008,0054) | 1/1 | 1/1 |  | -/1 | O | 1 |
DICOM Media Retrieval Sequence | (0040,E022) | 1C/1 | 1C/1 |  | -/1 | O | 1C | Required if DICOM Retrieval Sequence (0040,E021), WADO Retrieval Sequence (0040,E023), WADO-RS Retrieval Sequence (0040,E025) and XDS Retrieval Sequence (0040,E024) are not present. May be present otherwise.
>Storage Media File-Set ID | (0088,0130) | 2/2 | 2/2 |  | -/2 | O | 2 |
>Storage Media File-Set UID | (0088,0140) | 1/1 | 1/1 |  | -/1 | O | 1 |
WADO Retrieval Sequence | (0040,E023) | 1C/1 | 1C/1 |  | -/1 | O | 1C | Required if DICOM Retrieval Sequence (0040,E021), DICOM Media Retrieval Sequence (0040,E022), WADO-RS Retrieval Sequence (0040,E025) and XDS Retrieval Sequence (0040,E024) are not present. May be present otherwise.
>Retrieve URI | (0040,E010) | 1/1 | 1/1 |  | -/1 | O | 1 |
XDS Retrieval Sequence | (0040,E024) | 1C | 1C/1 |  | -/1 | O | 1C | Required if DICOM Retrieval Sequence (0040,E021), DICOM Media Retrieval Sequence (0040,E022), WADO-RS Retrieval Sequence (0040,E025) and WADO Retrieval Sequence (0040,E023) are not present. May be present otherwise.
>Repository Unique ID | (0040,E030) | 1 | 1/1 |  | -/1 | O | 1 |
>Home Community ID | (0040,E031) | 3/2 | 3/2 |  | 3/2 | O | 2 |
WADO-RS Retrieval Sequence | (0040,E025) | 1C/1 | 1C/1 |  | -/1 | O | 1C | Required if DICOM Retrieval Sequence (0040,E021), DICOM Media Retrieval Sequence (0040,E022), WADO Retrieval Sequence (0040,E023), and XDS Retrieval Sequence (0040,E024) are not present. May be present otherwise.
>Retrieve URL | (0008,1190) | 1/1 | 1/1 |  | -/1 | O | 1 | URL specifying the location of the referenced instance(s).

Table CC.2.5-2d. HL7V2 Hierarchic Designator Macro

Attribute Name | Tag | Req. Type N-CREATE (SCU/SCP) | Req. Type N-SET (SCU/SCP) | Final State | Req. Type N-GET (SCU/SCP) | Match Key Type | Return Key Type | Remark/Matching Type
--- | --- | --- | --- | --- | --- | --- | --- | ---
Local Namespace Entity ID | (0040,0031) | 1C/1 | Not Allowed |  | -/1 | * | 1C | Creation required if Universal Entity ID (0040,0032) is not present; may be present otherwise. Return Key required if set.
Universal Entity ID | (0040,0032) | 1C/1 | Not Allowed |  | -/1 | * | 1C | Creation required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise. Return Key required if set.
Universal Entity ID Type | (0040,0033) | 1C/1 | Not Allowed |  | -/1 | * | 1C | Creation required if Universal Entity ID (0040,0032) is present. Return Key required if set.
Local Namespace Entity ID | (0040,0031) | 1C/1 | Not Allowed |  | -/1 | * | 1C | Creation required if Universal Entity ID (0040,0032) is not present; may be present otherwise. Return Key required if set.

Table CC.2.5-2e. Issuer of Patient ID Macro

Attribute Name | Tag | Req. Type N-CREATE (SCU/SCP) | Req. Type N-SET (SCU/SCP) | Final State | Req. Type N-GET (SCU/SCP) | Match Key Type | Return Key Type | Remark/Matching Type
--- | --- | --- | --- | --- | --- | --- | --- | ---
Issuer of Patient ID | (0010,0021) | 2/2 | Not allowed | O | 3/2 | R | 2 |
Issuer of Patient ID Qualifiers Sequence | (0010,0024) | 2/2 | Not allowed | O | 3/2 | O | 2 |
>Universal Entity ID | (0040,0032) | 2/2 | Not allowed | O | 3/2 | O | 2 |
>Universal Entity ID Type | (0040,0033) | 1C/1 | Not allowed | O | 3/2 | O | 1C | Required if Universal Entity ID (0040,0032) is present in this item with a value.
>Identifier Type Code | (0040,0035) | 2/2 | Not allowed | O | 3/2 | O | 2 |
>Assigning Facility Sequence | (0040,0036) | 2/2 | Not allowed | O | 3/2 | O | 2 | The Attributes of the Assigning Facility Sequence shall only be retrieved with Sequence Matching.
>>Include Table CC.2.5-2d “HL7V2 Hierarchic Designator Macro” |
>Assigning Jurisdiction Code Sequence | (0040,0039) | 2/2 | Not allowed | O | 3/2 | O | 2 | The Attributes of the Assigning Jurisdiction Code Sequence shall only be retrieved with Sequence Matching.
>>Include Table CC.2.5-2a “UPS Code Sequence Macro” | Baseline CID 5001 “Countries” for country codes.
>Assigning Agency or Department Code Sequence | (0040,003A) | 2/2 | Not allowed | O | 3/2 | O | 2 | The Attributes of the Assigning Agency or Department Code Sequence shall only be retrieved with Sequence Matching.
>>Include Table CC.2.5-2a “UPS Code Sequence Macro” | No Baseline CID.

Table CC.2.5-2f. SOP Instance Reference Macro

Attribute Name | Tag | Req. Type N-CREATE (SCU/SCP) | Req. Type N-SET (SCU/SCP) | Final State | Req. Type N-GET (SCU/SCP) | Match Key Type | Return Key Type | Remark/Matching Type
--- | --- | --- | --- | --- | --- | --- | --- | ---
Referenced SOP Class UID | (0008,1150) | 1/1 | 1/1 |  | -/1 | * | 1 |
Referenced SOP Instance UID | (0008,1155) | 1/1 | 1/1 |  | -/1 | * | 1 |

Table CC.2.5-2g. Storage Macro

Attribute Name | Tag | Req. Type N-CREATE (SCU/SCP) | Req. Type N-SET (SCU/SCP) | Final State | Req. Type N-GET (SCU/SCP) | Match Key Type | Return Key Type | Remark/Matching Type
--- | --- | --- | --- | --- | --- | --- | --- | ---
Referenced SOP Class UID | (0008,1150) | 1C/1 | 1C/1 |  | -/1 | O | 1C | Required if the storage request only applies to a specific SOP Class.
DICOM Storage Sequence | (0040,4071) | 1C/1 | 1C/1 |  | -/1 | O | 1C | Required if STOW-RS Storage Sequence (0040,4072) and XDS Storage Sequence (0040,4074) are not present. May be present otherwise.
>Destination AE | (0040,4071) | 1/1 | 1/1 |  | -/1 | * | 1 |
STOW-RS Storage Sequence | (0040,4072) | 1C/1 | 1C/1 |  | -/1 | O | 1C | Required if DICOM Storage Sequence (0040,4071) and XDS Storage Sequence (0040,4074) are not present. May be present otherwise.
>Storage URL | (0040,4073) | 1/1 | 1/1 |  | -/1 | * | 1 |
XDS Storage Sequence | (0040,4074) | 1C/1 | 1C/1 |  | -/1 | O | 1C | Required if DICOM Storage Sequence (0040,4071) and STOW-RS Storage Sequence (0040,4072) are not present. May be present otherwise.
>Repository Unique ID | (0040,E030) | 1/1 | 1/1 |  | -/1 | * | 1 |
>Home Community ID | (0040,E031) | 3/2 | 3/2 |  | 3/2 | * | 2 |

##### CC.2.5.1.3 UPS Attribute Service Requirements

This table combines the Attribute requirements for multiple DIMSE services (N-CREATE, N-SET, N-GET, C-FIND) to facilitate consistency between the requirements.

See PS3.4 for the meaning of the requirement codes used in the N-CREATE, N-SET, N-GET and Return Key columns in the following table.

See Section C.1.2 for the meaning of the requirement codes used in the Match Key column in the following table.

See Table CC.2.5-1 for the meaning of the requirement codes used in the Final State column of the following table.

Table CC.2.5-3. UPS SOP Class N-CREATE/N-SET/N-GET/C-FIND Attributes

Attribute Name | Tag | Req. Type N-CREATE (SCU/SCP) | Req. Type N-SET (SCU/SCP) | Final State | Req. Type N-GET (SCU/SCP) | Match Key Type | Return Key Type | Remark/Matching Type
--- | --- | --- | --- | --- | --- | --- | --- | ---
Transaction UID | (0008,1195) | 2/2 Shall be empty | (see CC.2.6.3) | O | Not allowed | - | - | Cannot be queried.
SOP Common Module
Specific Character Set | (0008,0005) | 1C/1C | 1C/1C | RC | 3/1 | - | 1C | Required if extended or replacement character set is used
SOP Class UID | (0008,0016) | See CC.2.5.1.3.1 | Not allowed | R | Not allowed | O | 1 | Uniquely identifies the SOP Class of the Unified Procedure Step. See Section CC.3.1 for further explanation.
SOP Instance UID | (0008,0018) | Not allowed. SOP Instance is conveyed in the Affected SOP Instance UID (0000,1000) | Not allowed. SOP Instance is conveyed in the Requested SOP Instance UID (0000,1001) | R | Not allowed. SOP Instance is conveyed in the Requested SOP Instance UID (0000,1001) | U | 1 | Uniquely identifies the SOP Instance of the UPS. SOP Instance UID shall be retrieved with Single Value Matching.
All other Attributes of the SOP Common Module |  | 3/3 | 3/3 | O | 3/3 | - | - |
Unified Procedure Step Scheduled Procedure Information Module
Scheduled Procedure Step Priority | (0074,1200) | 1/1 | 3/1 | R | 3/1 | R | 1 | Scheduled Procedure Step Priority shall be retrieved with Single Value Matching.
Scheduled Procedure Step Modification Date and Time | (0040,4010) | 2/1 SCP shall use time of CREATE rather than any value provided | -/1 SCP will use time of SET | R | 3/1 | O | 3 | Scheduled Procedure Step Modification Date and Time shall be retrieved with Single Value Matching or Range Matching.
Procedure Step Label | (0074,1204) | 1/1 | 3/1 | O | 3/1 | R | 1 |
Worklist Label | (0074,1202) | 2/1 If a value is not provided by the SCU, the SCP shall fill in the Worklist Label, e.g., using a default value or by assigning the UPS instance to a logical worklist. | 3/1 | O | 3/1 | R | 1 |
Scheduled Processing Parameters Sequence | (0074,1210) | 2/2 | 3/2 | O | 3/2 | - | 2 |
>Include Table CC.2.5-2b “UPS Content Item Macro”
Scheduled Station Name Code Sequence | (0040,4025) | 2/2 | 3/2 | O | 3/2 | R | 2 | The Attributes of the Scheduled Station Name Code Sequence shall only be retrieved with Sequence Matching. ### Note In Push Scenario, the SCP-Performer has to create empty but could self fill later.
>Include Table CC.2.5-2a “UPS Code Sequence Macro”
Scheduled Station Class Code Sequence | (0040,4026) | 2/2 | 3/2 | O | 3/2 | R | 2 | The Attributes of the Scheduled Station Class Code Sequence shall only be retrieved with Sequence Matching.
>Include Table CC.2.5-2a “UPS Code Sequence Macro”
Scheduled Station Geographic Location Code Sequence | (0040,4027) | 2/2 | 3/2 | O | 3/2 | R | 2 | The Attributes of the Scheduled Station Geographic Location Code Sequence shall only be retrieved with Sequence Matching.
>Include Table CC.2.5-2a “UPS Code Sequence Macro”
Scheduled Human Performers Sequence | (0040,4034) | 2C/2C | 3/2 | O | 3/2 | R | 2 | The Attributes of the Scheduled Human Performers Sequence shall only be retrieved with Sequence Matching. Required if a Human Performer is specified.
>Human Performer Code Sequence | (0040,4009) | 1/1 | 1/1 | O | -/1 | R | 1 | The Attributes of the Scheduled Human Performers Code Sequence shall only be retrieved with Sequence Matching.
>>Include Table CC.2.5-2a “UPS Code Sequence Macro”
>Human Performer's Name | (0040,4037) | 1/1 | 1/1 | O | -/1 | O | 3 |
>Human Performer's Organization | (0040,4036) | 1/1 | 1/1 | O | -/1 | O | 3 |
Scheduled Procedure Step Start Date and Time | (0040,4005) | 1/1 | 3/1 | R | 3/1 | R | 1 | Scheduled Procedure Step Start Date and Time shall be retrieved with Single Value Matching or Range Matching.
Expected Completion Date and Time | (0040,4011) | 3/1 | 3/1 | O | 3/1 | R | 3 | Expected Completion Date and Time shall be retrieved with Single Value Matching or Range Matching.
Scheduled Workitem Code Sequence | (0040,4018) | 2/2 | 3/1 | O | 3/1 | R | 2 | The Attributes of the Scheduled Workitem Code Sequence shall only be retrieved with Sequence Matching.
>Include Table CC.2.5-2a “UPS Code Sequence Macro”
Comments on the Scheduled Procedure Step | (0040,0400) | 2/2 | 3/1 | O | 3/1 | O | 3 |
Input Readiness State | (0040,4041) | 1/1 | 3/1 | R | 3/1 | R | 1 | Input Readiness State shall be retrieved with Single Value Matching.
Input Information Sequence | (0040,4021) | 2/2 | 3/2 | O | 3/2 | O | 2 | The Attributes of the Input Information Sequence shall only be retrieved with Sequence Matching.
>Include Table CC.2.5-2c “Referenced Instances and Access Macro”
Study Instance UID | (0020,000D) | 1C/2 | 3/2 | O | 3/2 | O | 2 | Required if the Workitem is expected to result in the creation of any DICOM Composite Instances whose IOD contains the Study IE. There may be situations where the performer does not use the Study Instance UID suggested by the Scheduler.
Output Destination Sequence | (0040,4070) | 3/3 | 3/3 | O | 3/3 | O | 3 | The Attributes of the Output Destination Sequence shall only be retrieved with Sequence Matching.
>Include Table CC.2.5-2g “Storage Macro”
All other Attributes of the Unified Procedure Step Scheduled Procedure Information Module |  | 3/3 | 3/3 | O | 3/3 | - | - |
Unified Procedure Step Relationship Module
Patient's Name | (0010,0010) | 2/2 | Not allowed | O | 3/2 | R | 2 |
Patient ID | (0010,0020) | 1C/2 | Not allowed | O | 3/2 | R | 2 | Required if the subject of the workitem requires identification or if the workitem is expected to result in the creation of objects that identify the subject. See Section C.30.4.1 “Patient Identification” in PS3.3
Include Table CC.2.5-2e “Issuer of Patient ID Macro”
Other Patient IDs Sequence | (0010,1002) | 2/2 | 3/3 | O | 3/2 | O | 2 |
>Patient ID | (0010,0020) | 1/1 | 1/1 | O | -/1 | O | 1 |
Include Table CC.2.5-2e “Issuer of Patient ID Macro”
Patient's Birth Date | (0010,0030) | 2/2 | Not allowed | O | 3/2 | R | 2 |
Patient's Sex | (0010,0040) | 2/2 | Not allowed | O | 3/2 | R | 2 |
Referenced Patient Photo Sequence | (0010,1100) | 3/3 | 3/3 | O | 3/3 | - | 3 |
>Include Table CC.2.5-2c “Referenced Instances and Access Macro”
Admission ID | (0038,0010) | 2/2 | Not allowed | O | 3/2 | R | 2 |
Issuer of Admission ID Sequence | (0038,0014) | 2/2 | Not allowed | O | 3/2 | R | 2 |
>Include Table CC.2.5-2d “HL7V2 Hierarchic Designator Macro”
Admitting Diagnoses Description | (0008,1080) | 2/2 | Not allowed | O | 3/2 | O | 2 |
Admitting Diagnoses Code Sequence | (0008,1084) | 2/2 | Not allowed | O | 3/2 | O | 2 | The Attributes of the Admitting Diagnoses Code Sequence shall only be retrieved with Sequence Matching.
>Include Table CC.2.5-2a “UPS Code Sequence Macro”.
Referenced Request Sequence | (0040,A370) | 2/2 | Not allowed | O | 3/2 | R | 2 | Could be "changed" while SCHEDULED by canceling and re-creating with the "correct" values.
>Study Instance UID | (0020,000D) | 1/1 | Not allowed | O | -/1 | O | 1 |
>Accession Number | (0008,0050) | 2/2 | Not allowed | O | -/2 | R | 2 |
>Issuer of Accession Number Sequence | (0008,0051) | 2/2 | Not allowed | O | -/2 | R | 2 | The Issuer of Accession Number Sequence shall only be retrieved with Sequence Matching.
>>Include Table CC.2.5-2d “HL7V2 Hierarchic Designator Macro”
>Placer Order Number/Imaging Service Request | (0040,2016) | 3/1 | Not allowed | O | -/1 | O | 1C | Required if set.
>Order Placer Identifier Sequence | (0040,0026) | 2/2 | Not allowed | O | -/2 | O | 2 | The Order Placer Identifier Sequence shall only be retrieved with Sequence Matching.
>>Include Table CC.2.5-2d “HL7V2 Hierarchic Designator Macro”
>Filler Order Number/Imaging Service Request | (0040,2017) | 3/1 | Not allowed | O | -/1 | O | 1C | Required if set.
>Order Filler Identifier Sequence | (0040,0027) | 2/2 | Not allowed | O | -/2 | O | 2 | The Order Filler Identifier Sequence shall only be retrieved with Sequence Matching.
>>Include Table CC.2.5-2d “HL7V2 Hierarchic Designator Macro”
>Requested Procedure ID | (0040,1001) | 2/2 | Not allowed | O | -/2 | R | 2 |
>Requested Procedure Description | (0032,1060) | 2/2 | Not allowed | O | -/2 | O | 2 |
>Requested Procedure Code Sequence | (0032,1064) | 2/2 | Not allowed | O | -/2 | O | 2 |
>>Include Table CC.2.5-2a “UPS Code Sequence Macro”
>Reason for the Requested Procedure | (0040,1002) | 3/3 | 3/3 | O | -/3 | - | - |
> Reason for Requested Procedure Code Sequence | (0040,100A) | 3/3 | 3/3 | O | -/3 | - | - |
>>Include Table CC.2.5-2a “UPS Code Sequence Macro”
>Requested Procedure Comments | (0040,1400) | 3/3 | 3/3 | O | -/3 | O | 1C | Required if set.
>Confidentiality Code | (0040,1008) | 3/3 | 3/3 | O | -/3 | O | 3 |
>Names of Intended Recipients of Results | (0040,1010) | 3/3 | 3/3 | O | -/3 | O | 3 |
>Imaging Service Request Comments | (0040,2400) | 3/3 | 3/3 | O | -/3 | O | 3 |
>Requesting Physician | (0032,1032) | 3/3 | 3/3 | O | -/3 | O | 3 |
>Requesting Service | (0032,1033) | 3/1 | 3/1 | O | -/3 | R | 3 |
>Issue Date of Imaging Service Request | (0040,2004) | 3/3 | 3/3 | O | -/3 | O | 3 |
>Issue Time of Imaging Service Request | (0040,2005) | 3/3 | 3/3 | O | -/3 | O | 3 |
>Referring Physician's Name | (0008,0090) | 3/3 | 3/3 | O | -/3 | O | 3 |
Replaced Procedure Step Sequence | (0074,1224) | 1C/1C | Not allowed | O | 3/2 | R | 3 | Required if the UPS replaces another Procedure Step.
>Include Table CC.2.5-2f “SOP Instance Reference Macro”
Patient Medical Module
Medical Alerts | (0010,2000) | 3/2 | 3/2 | O | 3/2 | O | 2C | Required if present.
Pregnancy Status | (0010,21C0) | 3/2 | 3/2 | O | 3/2 | O | 2C | Required if present.
Special Needs | (0038,0050) | 3/2 | 3/2 | O | 3/2 | O | 2C | Required if present.
All other Attributes of the Patient Medical Module |  | 3/3 | 3/3 | O | 3/3 | O | 3 |
Unified Procedure Step Progress Information Module
Procedure Step State | (0074,1000) | 1/1 Shall be created with a value of "SCHEDULED" | Not Allowed. Use N-ACTION | R | 3/1 | R | 1 | Procedure Step State shall be retrieved with Single Value Matching
Progress Information Sequence | (0074,1002) | 2/2 Shall be empty | 3/2 | X | 3/2 |  | 2 |
>Procedure Step Progress | (0074,1004) | Not Allowed | 3/1 | O | -/1 | - | - |
>Procedure Step Progress Description | (0074,1006) | Not Allowed | 3/1 | O | -/1 | - | - |
>Procedure Step Communications URI Sequence | (0074,1008) | Not Allowed | 3/1 | O | -/1 | - | - |
>>Contact URI | (0074,100a) | Not Allowed | 1/1 | O | -/1 | - | - |
>>Contact Display Name | (0074,100c) | Not Allowed | 3/1 | O | -/1 | - | - |
>Procedure Step Cancellation DateTime | (0040,4052) | Not Allowed | 3/1 | X | -/1 | - | - | If changing the UPS State (0074,1000) to CANCELED and this Attribute has no value, the SCP shall fill it with the current datetime.
>Reason For Cancellation | (0074,1238) | Not Allowed | 3/1 | O | -/1 | - | - |
>Procedure Step Discontinuation Reason Code Sequence | (0074,100e) | Not Allowed | 3/1 | X | -/1 |  |  |
>>Include Table CC.2.5-2a “UPS Code Sequence Macro”
Unified Procedure Step Performed Procedure Information Module
Unified Procedure Step Performed Procedure Sequence | (0074,1216) | 2/2 Shall be created empty | 3/2 | P | 3/2 | - | - | See CC.2.5.1.3.2.
>Actual Human Performers Sequence | (0040,4035) | Not Allowed | 3/1 | RC | -/1 | O | 1C | Shall be provided if known. Return Key required if set. The Attributes of the Actual Human Performers Sequence shall only be retrieved with Sequence Matching.
>>Human Performer Code Sequence | (0040,4009) | Not Allowed | 3/1 | RC | -/1 | - | - | Shall be provided if known.
>>>Include Table CC.2.5-2a “UPS Code Sequence Macro”
>>Human Performer's Name | (0040,4037) | Not Allowed | 3/1 | RC | -/1 | - | - | Shall be provided if known
>>Human Performer's Organization | (0040,4036) | Not Allowed | 3/1 | O | -/1 | - | - |
>Performed Station Name Code Sequence | (0040,4028) | Not Allowed | 3/2 | P | -/2 | O | 3 |
>>Include Table CC.2.5-2a “UPS Code Sequence Macro”
>Performed Station Class Code Sequence | (0040,4029) | Not Allowed | 3/2 | O | -/2 | - | - |
>>Include Table CC.2.5-2a “UPS Code Sequence Macro”
>Performed Station Geographic Location Code Sequence | (0040,4030) | Not Allowed | 3/2 | O | -/2 | - | - |
>>Include Table CC.2.5-2a “UPS Code Sequence Macro”
>Performed Procedure Step Start DateTime | (0040,4050) | Not Allowed | 3/1 | P | -/1 | - | - |
>Performed Procedure Step Description | (0040,0254) | Not Allowed | 3/1 | O | -/1 | - | - |
>Comments on the Performed Procedure Step | (0040,0280) | Not Allowed | 3/1 | O | -/1 | - | - |
>Performed Workitem Code Sequence | (0040,4019) | Not Allowed | 3/1 | P | -/1 | - | - |
>>Include Table CC.2.5-2a “UPS Code Sequence Macro”
>Performed Processing Parameters Sequence | (0074,1212) | Not Allowed | 3/1 | O | -/1 | - | - |
>>Include Table CC.2.5-2b “UPS Content Item Macro”
>Performed Procedure Step End DateTime | (0040,4051) | Not Allowed | 3/1 | P | -/1 | O | 1C | Required if set.
>Output Information Sequence | (0040,4033) | Not Allowed | 2/2 | P | -/2 | - | - | If there are no relevant output objects, then this sequence may have no items.
>Include Table CC.2.5-2c “Referenced Instances and Access Macro”

###### CC.2.5.1.3.1 UPS SOP Class UID

The SOP Class UID shall be set to 1.2.840.10008.5.1.4.34.6.1 by SCP

###### CC.2.5.1.3.2 Unified Procedure Step Performed Procedure Sequence

The Attributes of the UPS Performed Procedure Sequence shall only be retrieved with Sequence Matching.

### Note

Since this Attribute may be created empty and has a Final State requirement of X, a UPS in the SCHEDULED state may be canceled with two N-ACTIONS (IN PROGRESS then CANCELED) and no N-SETs.

Prev | Up | Next
CC.2.4.4 Status Codes | Home | CC.2.5.2 Service Class User Behavior

DICOM PS3.4 2017a - Service Class Specifications