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 110 7.8.2 Private Templates LOGIQ 7 supports the following private templates for SOP Instances created by this product. xxvii. Private TID GEMS_US_0100 - GE Ultrasound M&A NL Relation with Parent Value Type Concept Name VM Req Type Condition Value Set Constraint 1 CONTAINER EV (43126, 99GEMS,”Ultrasound M&A Document”) 1 M > CONTAINS UIDREF EV (43140, 99GEMS,”Series Instance UID”) 1 U > CONTAINS TEXT EV(29463-7, LN,”Patient Weight”) 1 U > CONTAINS TEXT EV(8302-2, LN, ”Patient Height”) 1 U > CONTAINS TEXT EV (43148, 99GEMS, “Ultrasound Category”) 1 U > CONTAINS TEXT EV (11878-6,LN, “Number of Fetuses”) 1 U > CONTAINS TEXT EV(43139, 99GEMS, “EDD method”) 1 U 7.8.2.1 Template ID GEMS_US_0100 “ultrasound M&A document title” LOGIQ 7 supports the private template GEMS_US_0100 from the mapping resource 99GEMS.
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 111 8. BASIC DIRECTORY INFORMATION OBJECT IMPLEMENTATION 8.1 INTRODUCTION This section specifies the use of the DICOM Basic Directory IOD to represent the information included in directories produced by this implementation. Corresponding attributes are conveyed using the module construct. The contents of this section are: 8.2 - IOD Implementation 8.3 - IOD Entity-Relationship Model 8.4- IOD Module Table 8.5 - IOD Module Definition 8.2 BASIC DIRECTORY IOD IMPLEMENTATION This section defines the implementation of Basic Directory information object. 8.3 BASIC DIRECTORY ENTITY-RELATIONSHIP MODEL The Entity-Relationship diagram for the Basic Directory interoperability schema is shown in Illustration 8.3-1. 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. 8.3.1 LOGIQ 7 Mapping of DICOM entities TABLE 8.3-1 MAPPING OF DICOM ENTITIES TO LOGIQ 7 ENTITIES DICOM LOGIQ 7 Patient Patient Study Exam Series Exam Image Image
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 112 ILLUSTRATION 8.3-1 BASIC DIRECTORY ENTITY RELATIONSHIP DIAGRAM Root Directory Entity Patient DR Includes 1 0 - n * Study DR * 1 - n Series DR * 1 - n Image DR 1 - n 1 1 1 8.4 IOD MODULE TABLE Within an entity of the Basic Directory IOD, 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 8.4-1 identifies the defined modules within the entities, which comprise the Basic Directory IOD. Modules are identified by Module Name. See DICOM Part 3 for a complete definition of the entities, modules, and attributes. TABLE 8.4-1 BASIC DIRECTORY IOD MODULES Entity Name Module Name Reference File Set Identification File Set Identification 8.5.1.1 Directory Information Directory Information 8.5.2.1
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 113 The Directory Information Module is created when initializing the media. If it already exists, the existing information is not changed regarding patient, study, series or image data. An existing Directory Information Module may have been obtained from application entities using removable media. These instances are external to this conformance claim and the origin of the SOP instances is outside the scope of this claim. 8.5 INFORMATION MODULE DEFINITIONS Please refer to DICOM Standard Part 3 (Information Object Definitions) for a description of each of the entities and modules contained within the Basic Directory Information Object. The following modules are included to convey Enumerated Values, Defined Terms, and Optional Attributes supported. Type 1 & Type 2 Attributes are also included for completeness and to define what values they may take and where these values are obtained. It should be noted that they are the same ones as defined in the DICOM Standard Part 3 (Information Object Definitions). 8.5.1 Common File Set identification Modules 8.5.1.1 File Set identification Module TABLE 8.5-1 FILE-SET IDENTIFICATION MODULE Attribute Name Tag Type Attribute Description File-set ID (0004,1130) 2 Has NULL value File-set Descriptor File ID (0004,1141) 3 Not used Specific Character Set of File-set Descriptor File (0004,1142) 1C Not used 8.5.2 Common Directory Information Modules 8.5.2.1 Directory Information Module TABLE 8.5-2 DIRECTORY INFORMATION MODULE Attribute Name Tag Type Attribute Description Offset of the First Directory Record of the Root Directory Entity (0004,1200) 1 Is set Offset of the Last Directory Record of the Root Directory Entity (0004,1202) 1 Is set File-set Consistency Flag (0004,1212) 1 FSC/FSU: Has the value 0000H: no known inconsistencies Directory Record Sequence (0004,1220) 2 Is created by FSC >Offset of the Next Directory Record (0004,1400) 1C Is set >Record In-use Flag (0004,1410) 1C FSC/FS: Is set to FFFFH FSR: A value of 0000H: imply skipping this record Read: A value of 0000H: the record is skipped
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 114 Attribute Name Tag Type Attribute Description >Offset of Referenced Lower-Level Directory Entity (0004,1420) 1C Is set >Directory Record Type (0004,1430) 1C The values support by FSC and FSU are PATIENT STUDY SERIES IMAGE >Private Record UID (0004,1432) 1C Not used >Referenced File ID (0004,1500) 1C Is set if Directory Record Type is IMAGE Contains the file path consisting of 5 elements: 1. “GEMS_IMG” 2. Month of exam 3. Day of exam 4. Patient initials and time of exam 5. Time stamp >MRDR Directory Record Offset (0004,1504) 1C A MRDR is not created by an FSC or FSU. >Referenced SOP Class UID in File (0004,1510) 1C Is set to the SOP class UID in File >Referenced SOP Instance UID in File (0004,1511) 1C Is set to the SOP instance UID in File >Referenced Transfer Syntax UID in File (0004,1512) 1C Is set to the Transfer Syntax UID in File >Record Selection Keys See 8.5.3. 8.5.3 Definition of Specific Directory Records 8.5.3.1 Patient Directory Record Definition TABLE 8.5-3 PATIENT KEYS Key Tag Type Attribute Description Specific Character Set (0008,0005) 1C Is filled in by FSC and FSU as in chapter 4, 5, and 6. Patients Name (0010,0010) 2 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Patient ID (0010,0020) 1 Is filled in by FSC and FSU as in chapter 4, 5, and 6. If empty, a Patient Id is created by the equipment. Patients Birth Date (0010,0030) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Patients Sex (0010,0040) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Referenced Patient Sequence (0008,1120) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6.
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 115 Key Tag Type Attribute Description >Referenced SOP Class UID (0008,1150) 1C Is filled in by FSC and FSU as in chapter 4, 5, and 6. >Referenced SOP Instance UID (0008,1155) 1C Is filled in by FSC and FSU as in chapter 4, 5, and 6. Patients Birth Time (0010,0032) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Other Patient Ids (0010,1000) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Other Patient Names (0010,1001) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Ethnic Group (0010,2160) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Patient Comments (0010,4000) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. 8.5.3.2 Study Directory Record Definition TABLE 8.5-4 STUDY KEYS Key Tag Type Attribute Description Specific Character Set (0008,0005) 1C Is filled in by FSC and FSU as in chapter 4, 5, and 6. Study Instance UID (0020,000D) 1C Is filled in by FSC and FSU as in chapter 4, 5, and 6. Study Date (0008,0020) 1 Is filled in by FSC and FSU as in chapter 4, 5and 6. If empty, a Study Date is created by the equipment. Study Time (0008,0030) 1 Is filled in by FSC and FSU as in chapter 4, 5, and 6. If empty, a Study Time is created by the equipment. Referring Physicians Name (0008,0090) 2 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Study ID (0020,0010) 1 Is filled in by FSC and FSU as in chapter 4, 5, and 6. If empty, a Study Id is created by the equipment. Accession Number (0008,0050) 2 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Study Description (0008,1030) 2 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Physician(s) of Record (0008,1048) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Name of Physician(s) Reading Study (0008,1060) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Referenced Study Sequence (0008,1110) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. >Referenced SOP Class UID (0008,1150) 1C Is filled in by FSC and FSU as in chapter 4, 5, and 6.
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 116 Key Tag Type Attribute Description >Referenced SOP Instance UID (0008,1155) 1C Is filled in by FSC and FSU as in chapter 4, 5, and 6. Admitting Diagnoses Description (0008,1080) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Patients Age (0010,1010) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Patients Size (0010,1020) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6.. Patients Weight (0010,1030) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Occupation (0010,2180) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Additional Patient’s History (0010,21B0) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. 8.5.3.3 Series Directory Record Definition TABLE 8.5-5 SERIES KEYS Key Tag Type Attribute Description Specific Character Set (0008,0005) 1C Is filled in by FSC or FSU as contained in the image or SR document message, if one of the tags contains extended characters Modality (0008,0060) 1 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Series Instance UID (0020,000E) 1 Is filled in by FSC and FSU as in chapter 4, 5, and 6.. Series Number (0020,0011) 1 Is filled in by FSC and FSU as in chapter 4, 5, and 6. If empty, a Series Number is created by the equipment. Icon Image Sequence (0088,0200) 3 Not used. Series Date (0008,0021) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Series Time (0008,0031) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Performing Physicians’ Name (0008,1050) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Protocol Name (0018,1030) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Series Description (0008,103E) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6..
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 117 Key Tag Type Attribute Description Operator’s Name (0008,1070) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Referenced Performed Procedure Step Sequence (0008,1111) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. >Referenced SOP Class UID (0008,1150) 1C Is filled in by FSC and FSU as in chapter 4, 5, and 6.. >Referenced SOP Instance UID (0008,1155) 1C Is filled in by FSC and FSU as in chapter 4, 5, and 6. Request Attributes Sequence (0040,0275) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6.. >Requested Procedure ID (0040,1001) 1C Is filled in by FSC and FSU as in chapter 4, 5, and 6. >Scheduled Procedure Step ID (0040,0009) 1C Is filled in by FSC and FSU as in chapter 4, 5, and 6. >Scheduled Procedure Step Description (0040,0007) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. >Scheduled Protocol Code Sequence (0040,0008) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. >>Include ‘Code Sequence Macro’ Is filled in by FSC and FSU as in chapter 4, 5, and 6. Performed Procedure Step ID (0040,0253) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6.. Performed Procedure Step Start Date (0040,0244) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Performed Procedure Step Start Time (0040,0245) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Performed Procedure Step Description (0040,0254) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Performed Protocol Code Sequence (0040,0260) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. >Include ‘Code Sequence Macro’
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 118 Key Tag Type Attribute Description Manufacturer (0008,0070) 2 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Institution Name (0008,0080) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6.. Station Name (0008,1010) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6.. Institutional Department Name (0008,1040) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Manufacturers Model Name (0008,1090) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6.. Software Versions (0018,1020) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6.. 8.5.3.4 Image Directory Record Definition TABLE 8.5-6 IMAGE KEYS Key Tag Type Attribute Description Specific Character Set (0008,0005) 1C Is filled in by FSC and FSU as in chapter 4, 5, and 6. Instance Number (0020,0013) 1 Is filled in by FSC and FSU as in chapter 4, 5, and 6. If empty, a Instance Number is created by the equipment. Icon Image Sequence (0088,0200) 3 Not used Image Type (0008,0008) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Rows (0028,0010) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6.. Columns (0028,0011) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Number Of Frames (0028,0008) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Photometric Interpretation (0028,0004) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Referenced Transfer Syntax UID in File (0004,1512) 3 Is set to the Transfer Syntax UID in File Referenced SOP Instance UID in File (0004,1511) 3 Is set to the SOP instance UID in File Referenced SOP Class in File (0004,1510) 3 Is set to the SOP class UID in File Contrast/Bolus Agent (0018,0010) 2 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Lossy Image Compression (0028,2110) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6. Lossy Image Compression Ratio (0028,2112) 3 Is filled in by FSC and FSU as in chapter 4, 5, and 6.
LOGIQ7 GE HEALTHCARE DICOM CONFORMANCE STATEMENT DIRECTION 2316173-100REV 7.03 119 8.5.3.4.1 Private Directory Record Definition Not used.8.5.3.5 Multi-Referenced File Directory Record Definition Not used. 8.6 PRIVATE DATA DICTIONARY If so configured, the product will send ultrasound raw data information in private data elements designated by the Private Creator element: Element Name Tag VR VM Description Private Creator 7FE1,00xx LO 1 GEMS_Ultrasound_MovieGroup_001 This means that all private tags starting with 7FE1,xx will belong to the GEMS_Ultrasound_MovieGroup_001. If so configured, the product will send preview image in private data elements designated by the Private Creator element: Element Name Tag VR VM Description Private Creator 6003,00xx LO 1 GEMS_Ultrasound_ImageGroup_001 This means that all private tags starting with 6003,xx will belong to the GEMS_Ultrasound_ImageGroup_001.