C.30 UNIFIED PROCEDURE STEP SPECIFIC MODULES

The following Sections specify Modules used for Unified Procedure Steps.

C.30.1 Unified Procedure Step Progress Information Module

Table C.30.1-1 specifies the Attributes that describe the progress of a Unified Procedure Step (UPS).

Table C.30.1-1

Unified Procedure Step Progress Information Module Attributes

Attribute Name Tag Attribute Description
Procedure Step State (0074,1000) State of the Procedure Step. Enumerated Values: SCHEDULED IN PROGRESS CANCELED COMPLETED See PS3.4 for details on Unified Procedure Step states.
Progress Information Sequence (0074,1002) Information about work progress for the Procedure Step. Zero or one Item shall be included in this sequence.
>Procedure Step Progress (0074,1004) A numerical indicator of progress expressed as percentage complete. Note: This is primarily for status rendering (e.g. progress bar). The percentage is not necessarily an accurate indication of total time.
>Procedure Step Progress Description (0074,1006) A textual description of progress. Note: For example, it might contain “Annealing complete”.
>Procedure Step Communications URI Sequence (0074,1008) Contact Information to communicate with performers of the Procedure Step. Zero or more Items shall be included in this sequence.
>>Contact URI (0074,100a) URI to communicate with performer of the procedure in progress. Any URI (telephone number, URL, etc.) is permitted.
>>Contact Display Name (0074,100c) Name of the person, department or organization to contact for more information about the performance of the Procedure Step.
>Procedure Step Cancellation DateTime (0040,4052) Date and Time at which the procedure step was discontinued.
>Reason For Cancellation (0074,1238) A textual description of the reason a procedure step was discontinued.
>Procedure Step Discontinuation Reason Code Sequence (0074,100e) Coded Reason(s) for Discontinuing the Procedure Step. Zero or more items shall be included in this sequence.
>>Include ‘Code Sequence Macro’ Table 8.8-1 Defined Context ID is 9300.

C.30.2 Unified Procedure Step Scheduled Procedure Information Module

Table C.30.2-1 specifies the Attributes that describe the Unified Procedure Step (UPS) to be performed. The UPS may or may not be scheduled for a specific time or device, or may simply represent a piece of work that is intended to be performed.

Table C.30.2-1

Unified Procedure Step Scheduled Procedure Information Module Attributes

Attribute Name Tag Attribute Description
Scheduled Procedure Step Priority (0074,1200) Priority of the scheduled Procedure Step Enumerated Values are: HIGH: used to indicate an urgent or emergent work item, equivalent to a STAT request. MEDIUM: used to indicate a work item that has a priority less than HIGH and higher than LOW. It can be used to further stratify work items. LOW: used to indicate a routine or non-urgent work item.
Scheduled Procedure Step Modification Date and Time (0040,4010) Date and time when the Scheduled Procedure Information was last modified or first created (whichever is most recent). Note: This attribute should be automatically updated by the worklist management system whenever any modification is made to Scheduled Procedure Information Module attributes of a Unified Procedure Step.
Worklist Label (0074,1202) A label identifying the worklist to which the Procedure Step instance belongs.
Procedure Step Label (0074,1204) A label describing the task of the Procedure Step in text appropriate for displaying in the user selection interface.
Comments on the Scheduled Procedure Step (0040,0400) User-defined comments on the scheduled Procedure Step.
Scheduled Station Name Code Sequence (0040,4025) Identifying names within the enterprise of the equipment for which the Procedure Step is scheduled. The names conveyed in the Code Value (0008,0100) may be the same as the AE Titles, but do not have to be. Zero or more Items shall be included in this sequence.
>Include Code Sequence Macro Table 8.8-1 No Baseline Context ID is defined.
Scheduled Station Class Code Sequence (0040,4026) Classes of the equipment for which the Procedure Step is scheduled. Zero or more Items shall be included in this sequence.
>Include Code Sequence Macro Table 8.8-1 No Baseline Context ID is defined.
Scheduled Station Geographic Location Code Sequence (0040,4027) Geographic locations of the equipment for which the Procedure Step is scheduled. Zero or more Items shall be included in this sequence.
>Include Code Sequence Macro Table 8.8-1 No Baseline Context ID is defined.
Scheduled Human Performers Sequence (0040,4034) Human performers that are scheduled to be involved or responsible for performing the Procedure Step. Zero or more Items shall be included in this sequence.
>Human Performer Code Sequence (0040,4009) Human performer that is involved or responsible for performing the Procedure Step. Only a single Item shall be permitted in this sequence.
>>Include Code Sequence Macro Table 8.8-1 No Baseline Context ID is defined.
>Human Performer’s Name (0040,4037) Name of the human performer.
>Human Performer’s Organization (0040,4036) Organization to which the human performer is accountable for the activities in the Procedure Step.
Scheduled Procedure Step Start Date Time (0040,4005) Date and time at which the Procedure Step is scheduled to start.
Expected Completion Date Time (0040,4011) Date and time at which the Procedure Step is expected to be completed.
Scheduled Workitem Code Sequence (0040,4018) Coded description of the Procedure Step. Only a single Item shall be permitted in this sequence.
>Include Code Sequence Macro Table 8.8-1 Baseline Context ID is CID 9231 Note: This CID has generic workitems. An implementation may choose to define more specific, detailed workitems.
Scheduled Processing Parameters Sequence (0074,1210) Processing parameters to be used by the performing system when carrying out the Procedure Step. Zero or more Items shall be included in this sequence.
>Include Content Item Macro Table 10-2 The Content Item shall not have a Value Type (0040,A040) of CONTAINER. Note: The CONTAINER limitation prevents encoding SR Trees.
Input Readiness State (0040,4041) Readiness state of the Input Information Sequence (0040,4021) and the referenced instances. Enumerated values are: INCOMPLETE UNAVAILABLE READY INCOMPLETE means the Input Information Sequence is not yet complete and additional instance references might be added. UNAVAILABLE means the Input Information Sequence is complete but one or more of the referenced instances might not yet be available from the referenced source(s). READY means that the Input Information Sequence is complete and the referenced instances are available from the referenced sources. Notes: 1) If the Procedure Step does not require input information, the Input Readiness State may be READY when the Input Information Sequence is empty. 2) There is no guarantee that the referenced instances will still be available at the referenced location when retrieval is attempted. 3) There is no requirement to confirm the presence of referenced media prior to setting the Input Readiness State to READY.
Input Information Sequence (0040,4021) References to information objects needed to perform the scheduled Procedure Step. Referencing unencapsulated HL7 documents is described further in C.12.1.1.6. See also Input Readiness State (0040,4041). Zero or more Items shall be included in this sequence.
>Include ' Referenced Instances and Access Macro' Table 10-3b
Study Instance UID (0020,000D) Unique Study identification that shall be used for the created Composite SOP Instances resulting from this Unified Procedure Step.

C.30.3 Unified Procedure Step Performed Procedure Information Module

Table C.30.3-1 specifies the Attributes that describe the performance and results of a Unified Procedure Step (UPS).

Table C.30.3-1

Unified Procedure Step Performed Procedure Information Module Attributes

Attribute Name Tag Attribute Description
Unified Procedure Step Performed Procedure Sequence (0074,1216) Details of the Procedure Step as performed. Zero or one item shall be included in this sequence.
>Actual Human Performers Sequence (0040,4035) Human performers that are/were actually involved or responsible for performing the Procedure Step. Zero or more Items shall be included in this sequence. Note: Initially this list will be empty. Items may be added to the list at or after the status transition of the Procedure Step State (0074,1000) to “IN PROGRESS”
>>Human Performer Code Sequence (0040,4009) Human performer that is involved or responsible for performing the Procedure Step. Only a single Item shall be permitted in this sequence.
>>>Include Code Sequence Macro Table 8.8-1 No Baseline Context ID is defined.
>>Human Performer’s Name (0040,4037) Name of the human performer.
>>Human Performer’s Organization (0040,4036) Organization to which the human performer is accountable for the activities in the Procedure Step.
>Performed Station Name Code Sequence (0040,4028) Names within the enterprise of the equipment that performed the Procedure Step. This name may be the same as the AE Title, but does not have to be. Zero or more Items shall be included in this sequence.
>>Include Code Sequence Macro Table 8.8-1 No Baseline Context ID is defined.
>Performed Station Class Code Sequence (0040,4029) Classes of the equipment that created the Procedure Step. Zero or more Items shall be included in this sequence.
>>Include Code Sequence Macro Table 8.8-1 No Baseline Context ID is defined.
>Performed Station Geographic Location Code Sequence (0040,4030) Geographic locations of the equipment that created Procedure Step. Zero or more Items shall be included in this sequence.
>>Include Code Sequence Macro Table 8.8-1 No Baseline Context ID is defined.
>Performed Procedure Step Start DateTime (0040,4050) Date and Time at which the Procedure Step started.
>Performed Procedure Step Description (0040,0254) Institution-generated description or classification of the Procedure Step that was performed.
>Performed Workitem Code Sequence (0040,4019) A sequence that conveys the type of procedure performed. Zero or more items shall be present in this sequence.
>>Include Code Sequence Macro Table 8.8-1 Baseline Context ID is CID 9231 Note: This CID has generic workitems. An implementation may choose to define more specific, detailed workitems.
>Performed Processing Parameters Sequence (0074,1212) Parameters used to perform the procedure. Zero or more items shall be present in this sequence
>>Include Content Item Macro Table 10-2 The Content Item shall not have a Value Type (0040,A040) of CONTAINER. Note: The CONTAINER limitation prevents including SR Trees.
>Performed Procedure Step End DateTime (0040,4051) Date and Time at which the Procedure Step ended.
>Output Information Sequence (0040,4033) References to information created as part of the Procedure Step. Referencing unencapsulated HL7 documents is described further in C.12.1.1.6. Zero or more Items shall be included in this sequence.
>>Include 'Referenced Instances and Access Macro' Table 10-3b

C.30.4 Unified Procedure Step Relationship Module

Table C.30.4-1 specifies the Attributes that describe the relationship of a Unified Procedure Step (UPS).

Table C.30.4-1

Unified Procedure Step Relationship Module Attributes

Attribute Name Tag Attribute Description
Patient's Name (0010,0010) Patient's full legal name.
Patient ID (0010,0020) Primary hospital identification number or code for the patient. See C.30.4.1
Include Issuer of Patient ID Macro Table 10-18
Other Patient IDs Sequence (0010,1002) Identification numbers or codes used to identify the patient, which may or may not be human readable, and may or may not have been obtained from an implanted or attached device such as an RFID or barcode. Zero or more Items shall be included in this sequence.
>Patient ID (0010,0020) An identification number or code used to identify the patient.
>Include Issuer of Patient ID Macro Table 10-18
Patient’s Birth Date (0010,0030) Date of birth of the named patient.
Patient’s Sex (0010,0040) Sex of the named Patient. Enumerated Values: M = male F = female O = other
Admission ID (0038,0010) Identification number of the visit as assigned by the healthcare provider
Issuer of Admission ID Sequence (0038,0014) Identifier of the Assigning Authority that issued the Admission ID. Only a single Item shall be permitted in this sequence.
>Include HL7v2 Hierarchic Designator Macro Table 10-17
Admitting Diagnoses Description (0008,1080) Description of admitting diagnosis (diagnoses) for the patient.
Admitting Diagnoses Code Sequence (0008,1084) Coded admitting diagnosis (diagnoses) for the patient. One or more Items shall be included in this Sequence.
>Include ‘Code Sequence Macro’ Table 8.8-1 No Baseline Context ID is defined.
Referenced Request Sequence (0040,A370) Requested Procedures to which the Procedure Step contributes. Zero or more Items shall be included in the sequence.
>Study Instance UID (0020,000D) Unique identifier for the Study.
>Accession Number (0008,0050) An identifier of the order for the Study.
>Issuer of Accession Number Sequence (0008,0051) Identifier of the Assigning Authority that issued the Accession Number. Only a single Item shall be permitted in this sequence.
>>Include HL7v2 Hierarchic Designator Macro Table 10-17
>Requested Procedure Code Sequence (0032,1064) Procedure Type of the Requested Procedure. Zero or one Item shall be included in this sequence.
>>Include Code Sequence Macro Table 8.8-1 No Baseline Context ID is defined.
>Placer Order Number / Imaging Service Request (0040,2016) The order number assigned to the Service Request by the party placing the order.
>Order Placer Identifier Sequence (0040,0026) Identifier of the Assigning Authority that issued the Placer Order Number. Only a single Item shall be permitted in this sequence.
>>Include HL7v2 Hierarchic Designator Macro Table 10-17
>Filler Order Number / Imaging Service Request (0040,2017) The order number assigned to the Service Request by the party filling the order.
>Order Filler Identifier Sequence (0040,0027) Identifier of the Assigning Authority that issued the Filler Order Number. Only a single Item shall be permitted in this sequence.
>>Include HL7v2 Hierarchic Designator Macro Table 10-17
>Requested Procedure ID (0040,1001) Identifier of the related Requested Procedure.
>Requested Procedure Description (0032,1060) Institution-generated description or classification of the Requested Procedure.
>Reason for the Requested Procedure (0040,1002) Reason for requesting this procedure.
> Reason for Requested Procedure Code Sequence (0040,100A) Coded reason for requesting this procedure. Zero or more Items shall be included in the sequence.
>>Include ‘Code Sequence Macro’ Table 8.8-1 No Baseline Context ID is defined.
>Requested Procedure Comments (0040,1400) User-defined comments on the Requested Procedure.
>Confidentiality Code (0040,1008) Confidentiality Constraints on the Requested Procedure by the party filling the order.
>Names of Intended Recipients of Results (0040,1010) Names of the physicians, who are intended recipients of results.
>Imaging Service Request Comments (0040,2400) User-defined comments on the Service Request.
>Requesting Physician (0032,1032) Physician who requested the Service Request.
>Requesting Service (0032,1033) Institutional department where the request initiated.
>Issue Date of Imaging Service Request (0040,2004) Date on which the Service Request was issued by the requester.
>Issue Time of Imaging Service Request (0040,2005) Time at which the Service Request was issued by the requester.
>Referring Physician’s Name (0008,0090) The physician who referred the Patient to the physician or service issuing the Service Request. Note: This is generally the recipient of any report generated by the Service Request.
Replaced Procedure Step Sequence (0074,1224) Canceled procedure step(s) which are replaced by this procedure step. Zero or more Items shall be included in the sequence.
>Include ‘SOP Instance Reference Macro’ Table 10-11

C.30.4.1 Patient Identification

For workitems which have a patient as the subject or context, the Patient ID, Issuer of Patient ID, Patient’s Name, Patient’s Sex and Patient’s Birth Date shall have appropriate values.

For workitems which have an identifiable subject that is not a patient, for example a phantom to be scanned or a display to be calibrated, the Patient ID shall be filled with an acceptable pseudo-patient value.

Note: For an object with a hospital asset control number or a manufacturer’s serial number, that number might be used as the Patient ID. The Issuer of Patient ID would identify the hospital asset control system or the device manufacturer. Alternatively, it is conceivable that a Patient ID could be generated by the ADT or the local John Doe procedure (to avoid conflicting with an ID assigned to a real patient).

The Patient Name might be set to CT^Phantom or ReadingRoom1Display.