The Modality Worklist SOP Class defined within the Basic Worklist Management Service Class defines an application-level class of service that facilitates the communication of information to the imaging modality about Scheduled Procedure Steps, and entities related to the Scheduled Procedure Steps. As will be detailed below, part of the information carried by the worklist mechanism is intended to be used by the imaging modality itself, but much of the information is intended to be presented to the modality operator.
This worklist is structured according to Scheduled Procedure Steps. A procedure step is a unit of service in the context of a requested imaging procedure.
The Modality Worklist SOP Class supports the following requirements:
-
Verify patient (e.g., download patient demographic information from IS to Modality, to verify that the person to be examined is the intended subject).
-
Select a Scheduled Procedure Step from the IS (e.g., download procedure step information from the IS to the Modality). The Modality Worklist SOP Class supports two alternatives for the realization of this requirement, supporting different organization methods of the department:
-
The Modality may obtain the list of Scheduled Procedure Steps from the IS. Display of the list and selection from the list is done at the Modality.
-
The list is displayed and selection is performed on the IS. This implies, that the information is obtained by the Modality just before the Scheduled Procedure Step starts.
-
-
Couple DICOM images unambiguously with related information from the IS (e.g., patient demographics, procedure description, ID data structure from the IS, contextual IS information).
-
Capture all the Attributes from the IS, that are mandatory to be inserted into the DICOM Image Object
The Modality Worklist SOP Class is not intended to provide access to all IS information and services that may be of interest to a Modality operator or attending physician. Its primary focus is the efficient operation of the image acquisition equipment. DICOM SOP Classes such as the Relevant Patient Information Query SOP Class and non-DICOM Services that fall beyond the scope of the Modality Worklist SOP Class may be needed.
The Modality Worklist SOP Class does not support the transmission of information from the Modality to the information system.
In response to a given C-FIND request, the SCP might have to send several C-FIND responses, (i.e., one C-FIND response per matching worklist item). Each worklist item focuses on one Scheduled Procedure Step and the related information. The E-R diagram presented in Figure K.6-1 depicts the content of one C-FIND request, that is:
Therefore, for a given C-FIND request, a given Scheduled Procedure Step will appear in only one of the resulting C-FIND responses. Obviously, information about the Requested Procedure, Imaging Service Request, Visit and Patient may be mentioned in several of these C-FIND responses.
The Modality Worklist Information Model is represented by the Entity Relationship diagram shown in figure Section K.6 -1.
Note
The entities appearing in messages related to the Modality Worklist SOP Class are required to comply to the Modality Worklist model. However, DICOM does not define the internal structure of the database.
The entry point of the Modality Worklist is the Scheduled Procedure Step entity.
The Attributes of a Scheduled Procedure Step Worklist can be found in the following Modules in PS3.3.
Table K.6-1 defines the Attributes of the Modality Worklist Information Model:
Table K.6-1. Attributes for the Modality Worklist Information Model
|
The Attributes of the Scheduled Procedure Step shall only be retrieved with Sequence Matching. The Scheduled Procedure Step Sequence shall contain only a single Item. |
||||
|
Scheduled Station AE Title shall be retrieved with Single Value Matching only. |
||||
|
Scheduled Procedure Step Start Date (0040,0002) shall be retrieved with Single Value Matching or Range Matching. See remark under Scheduled Procedure Step Start Time (0040,0003). |
||||
|
Scheduled Procedure Step Start Time (0040,0003) shall be retrieved with Single Value Matching or Range Matching. Scheduled Procedure Step Start Date (0040,0002) and Scheduled Procedure Step Start Time (0040,0003) are subject to Range Matching. If both keys are specified for Range Matching, e.g., the date range July 5 to July 7 and the time range 10am to 6pm specifies the time period starting on July 5, 10am until July 7, 6pm. |
||||
|
Scheduled Performing Physician's Name shall be retrieved with Single Value Matching or Wild Card Matching. |
||||
|
The Scheduled Procedure Step Description (0040,0007) and/or the Scheduled Protocol Code Sequence (0040,0008) shall be supported by the SCP. |
||||
|
The Scheduled Procedure Step Description (0040,0007) and/or the Scheduled Protocol Code Sequence (0040,0008) shall be supported by the SCP. The Scheduled Protocol Code Sequence contains one or more Items. |
||||
|
>>Include Table 8-2a “Enhanced Coded Entry Macro with Optional Matching Key Support and Optional Meaning” |
||||
|
The Protocol Context Sequence and its Items shall not be used for matching |
||||
|
>>>>Include Table 8-3a “Enhanced SCU/SCP Coded Entry Macro with no SCU Support and no Matching Key Support” |
||||
|
>>>>Include Table 8-3a “Enhanced SCU/SCP Coded Entry Macro with no SCU Support and no Matching Key Support” |
||||
|
>>>>Include Table 8-3a “Enhanced SCU/SCP Coded Entry Macro with no SCU Support and no Matching Key Support” |
||||
|
Required if Pre-Medication is to be applied to that Scheduled Procedure Step. |
||||
|
Required if Contrast Media is to be applied to that Scheduled Procedure Step. |
||||
|
>All other Attributes of the Scheduled Procedure Step Sequence |
||||
|
>>Include Table 8-3a “Enhanced SCU/SCP Coded Entry Macro with no SCU Support and no Matching Key Support” |
||||
|
Specimen Preparation Sequence (0040,0610), if present, describes preparation steps already performed, not scheduled procedure steps |
||||
|
The Requested Procedure Description (0032,1060) or the Requested Procedure Code Sequence (0032,1064) or both shall be supported by the SCP. |
||||
|
The Requested Procedure Description (0032,1060) or the Requested Procedure Code Sequence (0032,1064) or both shall be supported by the SCP. The Requested Procedure Code Sequence shall contain only a single Item. |
||||
|
>Include Table 8-2a “Enhanced Coded Entry Macro with Optional Matching Key Support and Optional Meaning” |
||||
|
>Include Table 8-2b “Basic Coded Entry Macro with Optional Matching Key Support and Optional Meaning” |
||||
|
All other Attributes of the Requested Procedure Module |
||||
|
All other Attributes of the Imaging Service Request Module |
||||
|
All other Attributes of the Visit Identification Module |
||||
|
All other Attributes of the Visit Status Module |
||||
|
All other Attributes of the Visit Relationship Module except those explicitly included in this table (see Note 3) |
||||
|
All Attributes from the Patient Relationship Module except those explicitly included in this table (see Note 3) |
||||
|
Patient Name shall be retrieved with Single Value Matching or Wild Card Matching. |
||||
|
All other Attributes of the Patient Identification Module |
||||
|
The languages that can be used to communicate with the patient. If returned, the Patient's Primary Language Code Sequence shall contain one or more Items. The items are ordered by preference (most preferred language to least preferred language). |
||||
|
>Include Table 8-4a “Enhanced Coded Entry Macro with Optional Matching Key Support and Mandatory Meaning” |
||||
|
A modifier for a Patient's Primary Language. Can be used to specify a national language variant. If returned, the Patient's Primary Language Modifier Code Sequence shall contain only a single Item. |
||||
|
>>Include Table 8-4a “Enhanced Coded Entry Macro with Optional Matching Key Support and Mandatory Meaning” |
||||
|
All other Attributes of the Patient Demographic Module |
||||
|
Pertinent Documents Sequence shall be retrieved with Universal Matching only |
||||
|
>>Include Table 8-3a “Enhanced SCU/SCP Coded Entry Macro with no SCU Support and no Matching Key Support” |
||||
|
All other Attributes of the Patient Medical Module |
||||
Note
-
Just like Series and Image Entities specified in the Query/Retrieve Service Class either an SCU or an SCP may support optional Matching Key Attributes and/or Type 3 Return Key Attributes that are not included in the Worklist Information Model (i.e., Standard or Private Attributes). This is considered a Standard Extended SOP Class (see PS3.2).
-
Each Module contains a Comment Attribute. This may be used to transmit non-structured information, which may be displayed to the operator of the Modality.
-
The reason for this exclusion is to assure that the Attributes that may be present in multiple Modules are included only once with the meaning pertaining to only one Module (for example, Referenced Study Sequence (0008,1110) shall be included once with the meaning as defined in the Requested Procedure Module).
-
The use of Specific Character Set is discussed in Section K.4.1.1.3.1 and Section K.4.1.1.3.2.
-
The values of Study Date (0008,0020) and Study Time (0008,0030) may be provided in order to achieve consistency of Study level Attributes in composite instances generated in multiple performed procedure steps on different devices, and the worklist values may be updated by the SCP based on information received from Modality Performed Procedure Steps or by examining the composite instances generated.
The Attributes in Table K.6-1a are not part of the Worklist Information Model; their inclusion in the C-FIND request and response identifier are governed by rules in sections Section K.4.1.1.3.1 and Section K.4.1.1.3.2, respectively.
Table K.6-1a. Attributes for the Modality Worklist C-FIND Identifier
|
This Attribute is required if expanded or replacement character sets are used. See Section C.2.2.2 and Section K.4.1.1.3 |
||||
|
This Attribute is required if times are to be interpreted explicitly in the designated local timezone. See Section C.2.2.2 and Section K.4.1.1.3 |
||||
|
One or more Items may be included in this sequence. Required if HL7 Structured Documents are referenced within the Identifier. See Section K.4.1.1.3 |
||||
An implementation may conform to the Modality Worklist SOP Class as an SCU or an SCP. The Conformance Statement shall be in the format defined in PS3.2.
An implementation that conforms to the Modality Worklist SOP Class as an SCU shall support queries against the Worklist Information Model described in Section K.6.1.2 of this Annex using the baseline C-FIND SCU Behavior described in Section K.4.1.2 of this Part.
An implementation that conforms to the Modality Worklist SOP Class as an SCU shall state in its Conformance Statement whether it requests matching on Optional Matching Key Attributes. If it requests Type 3 Return Key Attributes, then it shall list these Optional Return Key Attributes. It shall identify any Templates it supports for the Protocol Context Sequence.
An implementation that conforms to the Modality Worklist SOP Class as an SCU shall state in its Conformance Statement whether or not it supports Extended Negotiation of fuzzy semantic matching of person names.
An implementation that conforms to the Modality Worklist SOP Class as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when encoding queries and interpreting responses.
An implementation that conforms to the Modality Worklist SOP Class as an SCP shall support queries against the Worklist Information Model described in Section K.6.1.2 of this Annex using the C-FIND SCP Behavior described in Section K.4.1.3 of this Part.
An implementation that conforms to the Modality Worklist SOP Class as an SCP shall state in its Conformance Statement whether it supports matching on Optional Matching Key Attributes. If it supports Type 3 Return Key Attributes, then it shall list the Optional Return Key Attributes that it supports. It shall identify any Templates it supports for the Protocol Context Sequence (0040,0440).
An implementation that conforms to the Modality Worklist SOP Class as an SCP shall state in its Conformance Statement whether it supports case-insensitive matching for PN VR Attributes and list the Attributes for which this applies.
An implementation that conforms to the Modality Worklist SOP Class as an SCP shall state in its Conformance Statement whether or not it supports Extended Negotiation of fuzzy semantic matching of person names. If fuzzy semantic matching of person names is supported, then the mechanism for fuzzy semantic matching shall be specified.
An implementation that conforms to the Modality Worklist SOP Class as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when interpreting queries, performing matching and encoding responses.
An implementation that conforms to the Modality Worklist SOP Class as an SCP shall state in its Conformance Statement the manner in which Single Value Matching is performed for DS and IS VR Attributes (if supported) and list the Attributes for which this applies.