GE Logiq 7 User Manual
Have a look at the manual GE Logiq 7 User Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 45 GE manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 120 9. MODALITY WORKLIST INFORMATION MODEL DEFINITION 9.1 INTRODUCTION This section specifies the use of the DICOM Modality Worklist Information Model used to organize data and against which a Modality Worklist Query will be performed. The contents of this section are: 9.2- Information Model Description 9.3- Information Model Entity-Relationship Model 9.4- Information Model Module Table 9.5- Information Model Keys 9.2 MODALITY WORKLIST INFORMATION MODEL DESCRIPTION This section defines the implementation of Modality Worklist Information Model. 9.3 MODALITY WORKLIST INFORMATION MODEL ENTITY-RELATIONSHIP MODEL The Entity-Relationship diagram for the Modality Worklist Information Model schema is shown in Illustration 9.3-1. It represents the information that composes a Worklist Item. In this figure, the following diagrammatic convention is established to represent the information organization: · Each entity is represented by a rectangular box. · Each relationship is represented by a diamond shaped box. · The fact that a relationship exists between two entities is depicted by lines connecting the corresponding entity boxes to the relationship boxes. · In the event that a duplicate Study Instance UID is received, only the last record of the duplicate will be displayed.
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 121 ILLUSTRATION 9.3-1 MODALITY WORKLIST INFORMATION MODEL E/R DIAGRAM Scheduled Procedure Step Requested Procedure contained in requested for Patient done for Imaging Service Request 1 1 1 Visit is included 0,1 Worklist Item 9.3.1 Entity Descriptions Please refer to DICOM Standard PS 3.3. (Information Object Definitions) and PS 3.4 (Service Class Specifications) for a description of each of the Entities contained within the Modality Worklist Information Model. 9.3.1.1 Scheduled Procedure Step Schedule Procedure Step is implemented in a basic form to allow for the user to retrieve a subset of attributes. 9.3.1.2 Requested Procedure Entity Description Requested Procedure Step is implemented in a basic form to allow for the user to retrieve a subset of attributes.
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 122 9.3.1.3 Imaging Service Request Entity Description Image Service is implemented in a basic form to allow for the user to retrieve a subset of attributes. 9.3.1.4 Visit Entity Description Visit Entity is implemented in a basic form to allow for the user to retrieve a subset of attributes. 9.3.1.5 Patient Entity Description Patient Entity Description is implemented in a basic form to allow for the user to retrieve a subset of attributes. 9.3.2 LOGIQ 7 Mapping of DICOM entities TABLE 9.3-1 MAPPING OF DICOM ENTITIES TO LOGIQ 7 ENTITIES DICOM LOGIQ 7 Entity Scheduled Procedure Step Not Applicable Requested Procedure Exam Imaging Service Request Exam Visit Not Applicable Patient Patient 9.4 INFORMATION MODEL MODULE TABLE Within an entity of the DICOM Modality Worklist Information Model, attributes are grouped into related set of attributes. A set of related attributes is termed a module. A module facilitates the understanding of the semantics concerning the attributes and how the attributes are related with each other. A module grouping does not infer any encoding of information into datasets. Table 9.4-1 identifies the defined modules within the entities that comprise the DICOM Modality Worklist Information Model. Modules are identified by Module Name. See DICOM PS 3.3 and PS 3.4 for a complete definition of the entities, modules, and attributes.
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 123 TABLE 9.4-1 MODALITY WORKLIST INFORMATION MODEL MODULES Entity Name Module Name Reference Scheduled Procedure Step SOP Common 9.5.2.1 Scheduled Procedure Step 9.5.2.2 Requested Procedure Requested Procedure 9.5.3.1 Imaging Service Request Imaging Service Request 9.5.4.1 Visit Visit Identification 9.5.5.1 Visit Status 9.5.5.2 Visit Relationship 9.5.5.3 Visit Admission Not Used Patient Patient Relationship Not Used Patient Identification 9.5.6.1 Patient Demographic 9.5.6.2 Patient Medical 9.5.6.3 9.5 INFORMATION MODEL KEYS Please refer to DICOM Standard PS 3.3. (Information Object Definitions) and PS 3.4 (Service Class Specifications) for a description of each of the Entities contained within the Modality Worklist Information Model. The following Module descriptions are included to specify what data elements are supported and what type of matching can be applied. It should be noted that they are the same ones as defined in the DICOM Standard PS 3.4 (Service Class Specifications). The term Instance is used for Images and Reports in examinations, that are based on Worklist entries. 9.5.1 Supported Matching Following are the types of matching that can be requested by the implementation: · Single Value Matching. · Wild Card Matching. · Range of date. Fields with “Filtering is supported” in the Matching column can be controlled from the Search screen. All non-required matching fields can be configured in Configuration screen to be either enabled, enabled with a constant value or disabled. The constant value will be used as entered by user. Returned values, particularly those not mapped into the images or MPPSs, are viewable by the user by using the “DICOM Properties” button in the user interface. 9.5.2 Scheduled Procedure Step Entity 9.5.2.1 SOP Common Module TABLE 9.5-1 SOP COMMON MODULE ATTRIBUTES
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 124 Attribute Name Tag Expected Matching Key Type Expected Returned Key Type Mapped into Instance/MPPS Matching Specific Character Set (0008,0005) O 1C Yes/Yes Attribute is supported if the query contains matching keys in other than the default character repertoire. ISO IR 100 or ISO 2022 IR 87 is supported in responses. 9.5.2.2 Scheduled Procedure Step Module TABLE 9.5-2 SCHEDULED PROCEDURE STEP MODULE ATTRIBUTES Attribute Name Tag Expected Matching Key Type Expected Returned Key Type Mapped into Instance/MPPS Matching Scheduled Procedure Step Sequence (0040,0100) R 1 No/No Matching is supported. >Scheduled Station AE Title (0040,0001) R 1 No/No Matching is supported. >Scheduled Procedure Step Start Date (0040,0002) R 1 No/No Matching is supported. Filtering is supported. >Scheduled Procedure Step Start Time (0040,0003) R 1 No/No Matching is supported. >Modality (0008,0060) R 1 Yes/Yes (but always “US”) Matching is supported. >Scheduled Performing Physician’s Name (0040,0006) R 2 Yes/Yes (to Performing Physician’s Name) Matching is supported. >Scheduled Procedure Step Description (0040,0007) O 1C Yes/Yes Matching is supported. >Scheduled Station Name (0040,0010) O 2 No/No Matching is supported. >Scheduled Procedure Step Location (0040,0011) O 2 No/No Matching is supported. >Scheduled Procedure Step ID (0040,0009) O 1 Yes/Yes Matching is supported.
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 125 >Scheduled Protocol Code Sequence (0040,0008) O 1C Yes/Yes Matching is supported. 9.5.3 Requested Procedure Entity 9.5.3.1 Requested Procedure Module TABLE 9.5-3 REQUESTED PROCEDURE MODULE ATTRIBUTES Attribute Name Tag Expected Matching Key Type Expected Returned Key Type Mapped into Instance/MPPS Matching Requested Procedure ID (0040,1001) O 1 Yes/Yes (to Requested Procedure ID and Study ID) Matching is supported. Filtering is supported. Requested Procedure Description (0032,1060) O 1C Yes/Yes (to Study Description and Requested Procedure Description) Matching is supported. Requested Procedure Code Sequence (0032,1064) O 1C No/Yes Matching is supported. Requested Procedure Comments (0040,1400) O 3 No/No Matching is supported. Study Instance UID (0020,000D) O 1 Yes/Yes Matching is supported. Referenced Study Sequence (0008,1110) O 2 Yes/Yes Matching is supported. >Referenced SOP Class UID (0008,1150) O 1C Yes/Yes Matching is supported. >Referenced SOP Instance UID (0008,1155) O 1C Yes/Yes Matching is supported. Names of Intended Recipients of Results (0040,1010) O 3 Yes/No (to Physician(s) of Record) Matching is supported. 9.5.4 Imaging Service Request Entity 9.5.4.1 Imaging Service Request Module
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 126 TABLE 9.5-4 IMAGING SERVICE REQUEST MODULE ATTRIBUTES Attribute Name Tag Expected Matching Key Type Expected Returned Key Type Mapped into Instance/MPPS Matching Accession Number (0008,0050) O 2 Yes/Yes Matching is supported. Filtering is supported. Referring Physicians Name (0008,0090) O 2 Yes/No Matching is supported. Imaging Service Request Comments (0040,2400) O 3 No/No Matching is supported. Requesting Physician (0032,1032) O 2 No/No Matching is supported. Requesting Service (0032,1033) O 3 No/No Matching is supported. 9.5.5 Visit Entity 9.5.5.1 Visit Identification TABLE 9.5-5 VISIT IDENTIFICATION MODULE ATTRIBUTES Attribute Name Tag Expected Matching Key Type Expected Returned Key Type Mapped into Instance/MPPS Matching Admission ID (0038,0010) O 2 No/No Matching is supported. 9.5.5.2 Visit Status TABLE 9.5-6 VISIT STATUS MODULE ATTRIBUTES Attribute Name Tag Expected Matching Key Type Expected Returned Key Type Mapped into Instance/MPPS Matching Current Patient Location (0038,0300) O 2 No/No Matching is supported. 9.5.5.3 Visit Relationship TABLE 9.5-7 VISIT RELATIONSHIP MODULE ATTRIBUTES Attribute Name Tag Expected Matching Key Type Expected Returned Key Type Mapped into Instance/MPPS Matching
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 127 Referenced Patient Sequence (0008,1120) O 2 Yes/Yes Matching is supported. >Referenced SOP Class UID (0008,1150) O 2 Yes/Yes Matching is supported. >Referenced SOP Instance UID (0008,1155) O 2 Yes/Yes Matching is supported. 9.5.6 Patient Entity 9.5.6.1 Patient Identification TABLE 9.5-8 PATIENT IDENTIFICATION MODULE ATTRIBUTES Attribute Name Tag Expected Matching Key Type Expected Returned Key Type Mapped into Instance/MPPS Matching Patients Name (0010,0010) R 1 Yes/Yes Matching is supported. Filtering is supported. Patient ID (0010,0020) R 1 Yes/Yes Matching is supported. Filtering is supported. Other Patient Ids (0010,1000) O 3 Yes/No Matching is supported. 9.5.6.2 Patient Demographic TABLE 9.5-9 PATIENT DEMOGRAPHIC MODULE ATTRIBUTES Attribute Name Tag Expected Matching Key Type Expected Returned Key Type Mapped into Instance/MPPS Matching Patients Birth Date (0010,0030) O 2 Yes/Yes Matching is supported. Filtering is supported. Patients Birth Time (0010,0032) O 3 Yes/No Matching is supported. Patients Sex (0010,0040) O 2 Yes/Yes Matching is supported Filtering is supported. Patient’s Size (0010,1020) O 3 Yes/No Matching is supported. Patients Weight (0010,1030) O 2 Yes/No Matching is supported. Ethnic Group (0010,2160) O 3 Yes/No Matching is supported. Patient Comments (0010,4000) O 3 Yes/No Matching is supported.
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 128 9.5.6.3 Patient Medical TABLE 9.5-10 PATIENT MEDICAL MODULE ATTRIBUTES Attribute Name Tag Expected Matching Key Type Expected Returned Key Type Mapped into Instance/MPPS Matching Additional Patient History (0010,21B0) O 3 Yes/No Matching is supported. Contrast Allergies (0010,2210) O 2 No/No Matching is supported. Medical Alerts (0010,2000) O 2 No/No Matching is supported. Pregnancy Status (0010,21C0) O 2 No/No Matching is supported.
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 129 10. MODALITY PERFORMED PROCEDURE STEP SOP CLASS DEFINITION 10.1 INTRODUCTION This section of the DICOM Conformance Statement specifies the Modality Performed Procedure Step SOP Class, the optional attributes and service elements supported, the valid range of values for mandatory and optional attributes, and the status code behavior. 10.2 MODALITY PERFORMED PROCEDURE STEP SOP CLASS DEFINITION In this section, supported means that tag is sent with value if entered by user or from worklist. 10.2.1 IOD Description This is the description of the DICOM tags to be sent for Modality Performed Procedure Step SOP class: Modality Performed Procedure Step Sop Class N-CREATE, N-SET and Final State Attributes Attribute Name Tag Req. Type N-CREATE Req. Type N-SET Performed Procedure Step Relationship Scheduled Step Attribute Sequence (0040,0270) 1 Not allowed >Study Instance UID (0020,000D) 1 Not allowed >Referenced Study Sequence (0008,1110) 2, supported Not allowed >>Referenced SOP Class UID (0008,1150) 1C, supported Not allowed >>Referenced SOP Instance UID (0008,1155) 1C, supported Not allowed >Accession Number (0008,0050) 2, supported Not allowed >Placer Order Number/Imaging Service Request (0040,2016) 3, not supported Not allowed >Filler Order Number/Imaging Service Request (0040,2017) 3, not supported Not allowed >Requested Procedure ID (0040,1001) 2, supported Not allowed >Requested Procedure Description (0032,1060) 2, supported Not allowed >Scheduled Procedure Step ID (0040,0009) 2, supported Not allowed >Scheduled Procedure Step Description (0040,0007) 2, supported Not allowed >Scheduled Protocol Code Sequence (0040,0008) 2, supported Not allowed >>Include ‘Code Sequence Macro’ Patients Name (0010,0010) 2, supported Not allowed Patient ID (0010,0020) 2, supported Not allowed Patients Birth Date (0010,0032) 2, supported Not allowed Patients Sex (0010,0040) 2, supported Not allowed >Referenced Patient Sequence (0008,1120) 2, supported Not allowed >>Referenced SOP Class UID (0008,1150) 1C, supported Not allowed