Group of Companies ifa systems AG ifa united i-tech, Inc. Augustinusstr. 11b 1850 SE 17 th Street Suite C Suite 107 50226 Frechen Fort Lauderdale, FL 33316 Germany USA Phone: +49 2234 93367-0 Phone: +1 954 713-1476 Fax: +49 2234 93367-30 Fax: +1 954 713-1477 http://www.ifasystems.com http://www.ifauniteditech.com info@ifasystems.com info@ifauniteditech.com DICOM Connection Module V3.10 DICOM Conformance Statement Worklist Storage Query Retrieve Document Version 1.90 1999-2014
DOCUMENT VERSION DATE AUTHOR DESCRIPTION 1.0 JUNE 20 TH, 1999 PETER SCHERER, SEBASTIAN WENTE 1.1 AUGUST 10 TH, 1999 PETER SCHERER, SEBASTIAN WENTE 1.2 AUGUST 26 TH, 1999 PETER SCHERER, SEBASTIAN WENTE CREATED REVISED REVISED 1.3 JULY 1 ST, 2001 PETER SCHERER REVISED 1.4 JULY 1 ST, 2002 PETER SCHERER REVISED 1.5 JUNE 1 ST, 2003 PETER SCHERER REVISED 1.6 APRIL 1 ST, 2005 PETER SCHERER REVISED 1.7 OCTOBER 1 ST, 2007 PETER SCHERER REVISED 1.71 NOVEMBER 15 ST, 2007 PETER SCHERER REVISED 1.80 SEPTEMBER 15 TH, 2012 PETER SCHERER REVISED 1.90 JANUARY 1 ST, 2014 PETER SCHERER REVISED - 2 / 21 -
EXECUTIVE OVERVIEW This document is the DICOM 3.0 Conformance Statement for the Computerized Patient Record (CPR) DICOM Interface to interconnect CPR Subsystems to clinical Host Systems. It offers services to - Query worklist information from a site DICOM worklist using the DICOM Modality Worklist Information Model - Find Service Class as a Storage Class User - Store images/data to the site DICOM archive using a variety of ophthalmic specific Storage Service Classes as a Storage Class User - Query for patients, studies, series and images/data stored at the site DICOM server using DICOM Patient Root Query/Retrieve Information Model Find or DICOM Study Root Query/Retrieve Information Model Find Service Class as a Storage Class User - Retrieve images/data from the site DICOM archive using DICOM Patient Root Query/Retrieve Information Model Move, Patient Root Query/Retrieve Information Model Get, Study Root Query/Retrieve Information Model Move or Study Root Query/Retrieve Information Model Get Service Class as a Storage Class User Supported DICOM SOP Classes Table 1.1 SOP Class Name SOP Class UID Service Class Role Verification 008.1.1 BOTH Modality Worklist Information 008.5.1.4.31 SCU Model - Find Secondary Capture Image Storage.1.7 SCU VL Photographic Image Storage.1.77.1.4 SCU Ultrasound Image Storage.1.6.1 SCU Ultrasound Multi-frame Image.1.3.1 SCU Storage Ophthalmic 8 bit Photography.1.77.1.5.1 SCU Image Storage Ophthalmic Tomography Image.1.77.1.5.4 SCU Storage Encapsulated PDF Storage.1.104.1 SCU Lensometry Measurements.1.78.1 SCU Autorefraction Measurements.1.78.2 SCU Keratometry Measurements.1.78.3 SCU Subjective Refraction.1.78.4 SCU Measurements Visual Acuity Measurements.1.78.5 SCU Spectacle Prescription Report.1.78.6 SCU Study Root Query/Retrieve Information Model Find.2.2.1 SCU Patient Root Query/Retrieve.2.1.2 SCU Information Model Move Patient Root Query/Retrieve.2.1.3 SCU Information Model Get Study Root Query/Retrieve.2.2.2 SCU Information Model Move Study Root Query/Retrieve Information Model Get.2.2.3 SCU - 3 / 21 -
Table of Contents DICOM Connection Module - DICOM Conformance Statement EXECUTIVE OVERVIEW... 3 1. INTRODUCTION... 5 2. IMPLEMENTATION MODEL... 6 2.1. Application Data Flow Diagram... 6 2.2. Functional definitions of ME... 7 2.3. Sequencing of Real World Activities... 7 3. ME SPECIFICATIONS... 8 3.1. Worklist ME... 8 3.1.1. Association Establishment Policies... 8 3.1.2. Association Initiation Policy... 8 3.2. Storage ME... 10 3.2.1. Association Establishment Policies... 10 3.2.2. Association Initiation Policy... 10 3.3. Query ME... 12 3.3.1. Association Establishment Policies... 12 3.3.2. Association Initiation Policy... 12 3.4. Retrieve ME... 14 3.4.1. Association Establishment Policies... 14 3.4.2. Association Initiation Policy... 14 4. COMMUNICATION PROFILES... 17 4.1. Supported Communication Stacks... 17 4.1.1. TCP/IP Stack... 17 4.2. Physical Media Support... 17 5. EXENTIONS/SPECIALIZATIONS/PRIVATIZATIONS... 17 6. CONFIGURATION... 17 6.1. ME Title/Presentation Address Mapping... 17 7. SUPPORT OF EXTENDED CHARACTER SETS... 17 8. IOD DESCRIPTION:... 18 8.1. Visible Light IOD... 18 9. DEFINITION OF TERMS... 21-4 / 21 -
1. INTRODUCTION DICOM Connection Module - DICOM Conformance Statement This document is the DICOM 3.0 Conformance Statement for the DICOM Connection Module. The DICOM Connection Module is an interface component used for retrieving, storing and displaying diagnostic and medical images. The component conforms to the DICOM 3.0 standard to allow the sharing of medical information and images with other digital imaging systems that support DICOM as well. - 5 / 21 -
2. IMPLEMENTATION MODEL 2.1. Application Data Flow Diagram Figure 1 DICOM Connection Module Data Flow Model Create Worklist Worklist SCP Module Entity Verification SCU Worklist SCU Retrieve Worklist Worklist SCU Module Entity Verification SCP Worklist SCP Send Documents Storage SCU Module Entity Verification SCP Storage SCP Query Documents Query SCU Module Entity Verification SCP Query SCP Request Documents Retrieve SCU Module Entity Verification SCP Storage SCP Retrieve Documents Storage SCP Module Entity Verification SCU Storage SCU Internal Environment (ifa ecpacs) External Environment (DICOM Modality) - 6 / 21 -
2.2. Functional definitions of ME - After a CPR subsystem requests to query the Worklist Service, the Worklist ME reads the Hospital Worklist information using the query parameters provided by the CPR subsystem and hands the results to the CPR subsystem. It can be configured if the ME should check using the Verification Service that the Hospital System is available only if starting the application or every time requesting the Worklist. Also the CPR application can manually initiate the Verification service. - After a CPR subsystem requests to store images to the Hospital Storage the Storage ME sends images to the Hospital Storage using the Remote Storage Service. It can be configured: - If the ME should check using the Verification Service that the Hospital System is available only if starting the application or every time requesting the Storage Service. Also the user can manually initiate the Verification service. - If the ME should use Secondary Capture or Photographic Image SOP. - If the ME should store the image Uncompressed or JPEG Baseline compressed. - After a CPR subsystem requests to query the Query Service, the Query ME queries the Hospital Query Service using the query parameters provided by the CPR subsystem and hands the results to the CPR subsystem. It can be configured: - If the ME should check using the Verification Service that the Hospital System is available only if starting the application or every time processing a query. Also the CPR application can manually initiate the Verification service. - If the ME should use Patient Root or Study Root SOP. - After a CPR subsystem requests to retrieve images from the Hospital Storage the Retrieve ME downloads images from the Hospital Storage using the Storage Service. It can be configured: - If the ME should check using the Verification Service that the Hospital System is available only if starting the application or every time requesting the Storage Service. Also the user can manually initiate the Verification service. - If the ME should use Patient Root Move, Patient Root Get, Study Root Move or Study Root Get SOP. - All ME s acts as SCP for Verification in background. 2.3. Sequencing of Real World Activities - ME s can be configured that every time the ME s has to contact the Hospital system they check first that the Hospital System is available using the Verification Service. In case of success the ME s do their main functionality. - If it is not configured this way there is no sequencing of Real World Activities. - 7 / 21 -
3. ME SPECIFICATIONS 3.1. Worklist ME This Module Entity provides Standard Conformance to the following DICOM V3.0 SOP Classes: SOP Class Name SOP Class UID Usage Verification 008.1.1 SCU/SCP Modality Worklist Information Model Find 008.5.1.4.31 SCU 3.1.1. Association Establishment Policies 3.1.1.1. General For the Verification SOP Class the Worklist ME initiates an Association when acting as a SCU, it accepts an Association when acting as a SCP. For the Modality Worklist Information Model Find SOP Class the Worklist ME initiates an Association to the Modality Worklist Provider. The PDU size can be specified in a configuration file - the default value is 16k (16,384 Byte), the minimum value is 4k (4,096 Byte), the maximum value is 1MB (1,048,576 Byte). 3.1.1.2. Number of Associations The ME will attempt only one association establishment at a time for each SOP Class. 3.1.1.3. Asynchronous Nature Asynchronous operation is not supported. 3.1.1.4. Implementation Identifying Information The ME provides a single Implementation Class UID which is "1.2.276.0.43.100.1" and an implementation version name of "ifa DCM-MWL 2.22" 3.1.2. Association Initiation Policy - There are 2 real world activities that initiate an association for Verification SOP Class: - Manual request by the Operator - Automatic request at system start - The ME initiates an association for Modality Worklist Information Model Find SOP Class each time the user requests the Modality Worklist. 3.1.2.1. Real World Activity Verify Availability of Destination 3.1.2.1.1. Associated Real-World Activity The associated Real-World Activity is the verification of the availability of the destination. The ME will attempt to use the DIMSE C-ECHO command to verify whether the receiving AE is able to negotiate an Association and respond. - 8 / 21 -
3.1.2.1.2. Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Name UID Name List UID List Neg. Verification 008.1.1 Implicit VR Little Endian 008.1.2 SCU None 3.1.2.1.2.1. Specific Conformance The ME provides Standard Conformance to the DICOM Verification Service class. 3.1.2.1.2.2. Association length and duration The association is released immediately after the response has been received. 3.1.2.1.2.3. Implementation Specific Behavior Not applicable. 3.1.2.2. Real World Activity Request Worklist 3.1.2.2.1. Associated Real-World Activity The associated Real-World Activity is the attempt to display a Worklist dialog box. 3.1.2.2.2. Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Name UID Name List UID List Neg. Worklist 008.5.1.4.31 Implicit VR Little Endian 008.1.2 SCU None Worklist 008.5.1.4.31 Explicit VR Little Endian 008.1.2.1 SCU None 3.1.2.2.2.1. SOP Specific Conformance The ME provides Standard Conformance to the DICOM Verification Service class. 3.1.2.2.2.1.1. Association length and duration The association is released after all data are transmitted to satisfy the actual request. In case of timeout (See Chapter 6.) the ME retries to establish an association automatically in background, displaying a dialog box with status information (number of retrievals done/to go before abort) and gives the user the possibility to cancel the retrieval of the worklist. 3.1.2.2.2.1.2. Error and Status handling In case of error or non-successful status the ME repeats the request automatically in background, displaying a dialog box with status information (number of retrievals done/to go before abort) and gives the user the possibility to cancel the procedure. - 9 / 21 -
3.2. Storage ME DICOM Connection Module - DICOM Conformance Statement This Module Entity provides Standard Conformance to the following DICOM V3.0 SOP Classes: SOP Class Name SOP Class UID Usage Verification 008.1.1 SCU/SCP Secondary Image Capture.1.7 SCU VL Photographic Image Storage.1.77.1.4 SCU 3.2.1. Association Establishment Policies 3.2.1.1. General For the Verification SOP Class the Storage ME initiates an Association when acting as a SCU, it accepts an Association when acting as a SCP. For the Secondary Image Capture and VL Photographic Image Storage SOP Class the ME acting as a SCU initiates an Association to the Hospital Storage Provider. The size can be specified in a configuration file - the default value is 16k (16,384 Byte), the minimum value is 4k (4,096 Byte), the maximum value is 1MB (1,048,576 Byte). 3.2.1.2. Number of Associations The ME will attempt only one association establishment at a time for each SOP Class. 3.2.1.3. Asynchronous Nature Asynchronous operation is not supported. 3.2.1.4. Implementation Identifying Information The ME provides a single Implementation Class UID which is "1.2.276.0.43.100.2" and an implementation version name of "ifa DCM-VLS 2.22" 3.2.2. Association Initiation Policy - There are 2 real world activities that initiate an association for Verification SOP Class: - Manual request by the Operator - Automatic request at system start - The ME initiates an association as a SCU for VL Photographic Image Storage or Secondary Image Capture SOP Class each time the user requests to send one image or a collection of images. 3.2.2.1. Real World Activity Verify Availability of Destination 3.2.2.1.1. Associated Real-World Activity The associated Real-World Activity is the verification of the availability of the destination. The ME will attempt to use the DIMSE C-ECHO command to verify whether the receiving AE is able to negotiate an Association and respond. 3.2.2.1.2. Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Name UID Name List UID List Neg. Verification 008.1.1 Implicit VR Little Endian 008.1.2 SCU None - 10 / 21 -
3.2.2.1.2.1. Specific Conformance The ME provides Standard Conformance to the DICOM Verification Service class. 3.2.2.1.2.2. Association length and duration The association is released immediately after the response has been received. 3.2.2.1.2.3. Implementation Specific Behavior Not applicable. 3.2.2.2. Real World Activity Stores Images 3.2.2.2.1. Associated Real-World Activity The associated Real-World Activity is the attempt to store images in the Hospital System. 3.2.2.2.2. Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Secondary Image Capture Storage Secondary Image Capture Storage VL Photographic Image Storage VL Photographic Image Storage VL Photographic Image Storage.1.7.1.7.1.77.1.4.1.77.1.4.1.77.1.4 Implicit VR Little Endian 008.1.2 SCU None Explicit VR Little Endian 008.1.2.1 SCU None Implicit VR Little Endian 008.1.2 SCU None Explicit VR Little Endian 008.1.2.1 SCU None JPEG Baseline 008.1.2.4.50 SCU None 3.2.2.2.2.1. Specific Conformance - The attributes (0040,1001) Requested Procedure ID, (0040,0009) Scheduled Procedure Step ID and (0040,0007) - Scheduled Procedure Step Description are supported as required attributes if MWL is present (see Chapter 8.1.) 3.2.2.2.2.1.1. Association length and duration The association is released after all data are transmitted to satisfy the actual request. In case of timeout (See Chapter 6.) the ME retries to establish an association automatically in background, displaying a dialog box with status information (number of retrievals done/to go before abort) and gives the user the possibility to cancel the procedure. 3.2.2.2.2.1.2. Error and Status handling In case of error or non-successful status the ME repeats the request automatically in background. If after a configurable number of failed trials the ME displays a dialog box with status information (number of retrievals done/to go before abort) and gives the user the possibility to cancel the procedure or to repeat it again. All necessary data will be cached in a queue handled by the ME. Only images that are not send successfully are part of the retransmission. - 11 / 21 -
3.3. Query ME DICOM Connection Module - DICOM Conformance Statement This Module Entity provides Standard Conformance to the following DICOM V3.0 SOP Classes: SOP Class Name SOP Class UID Usage Verification 008.1.1 SCU/SCP Patient Root Find.2.1.1 SCU Study Root Find.2.2.1 SCU 3.3.1. Association Establishment Policies 3.3.1.1. General For the Verification SOP Class the Query ME initiates an Association when acting as a SCU, it accepts an Association when acting as a SCP. For the Patient Root Find and Study Root Find SOP Class the ME acting as a SCU initiates an Association to the Hospital Query Provider. The size can be specified in a configuration file - the default value is 16k (16,384 Byte), the minimum value is 4k (4,096 Byte), the maximum value is 1MB (1,048,576 Byte). 3.3.1.2. Number of Associations The ME will attempt only one association establishment at a time for each SOP Class. 3.3.1.3. Asynchronous Nature Asynchronous operation is not supported. 3.3.1.4. Implementation Identifying Information The ME provides a single Implementation Class UID which is "1.2.276.0.43.100.4" and an implementation version name of "ifa DCM-QR 2.22" 3.3.2. Association Initiation Policy - There are 2 real world activities that initiate an association for Verification SOP Class: - Manual request by the Operator - Automatic request at system start - The ME initiates an association as a SCU for Patient Root Find or Study Root Find SOP Class each time the user queries for patients, studies, series or images stored at the site DICOM server. 3.3.2.1. Real World Activity Verify Availability of Destination 3.3.2.1.1. Associated Real-World Activity The associated Real-World Activity is the verification of the availability of the destination. The ME will attempt to use the DIMSE C-ECHO command to verify whether the receiving AE is able to negotiate an Association and respond. 3.3.2.1.2. Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Name UID Name List UID List Neg. Verification 008.1.1 Implicit VR Little Endian 008.1.2 SCU None - 12 / 21 -
3.3.2.1.2.1. Specific Conformance The ME provides Standard Conformance to the DICOM Verification Service class. 3.3.2.1.2.2. Association length and duration The association is released immediately after the response has been received. 3.3.2.1.2.3. Implementation Specific Behavior Not applicable. 3.3.2.2. Real World Activity Stores Images 3.3.2.2.1. Associated Real-World Activity The associated Real-World Activity is the attempt to store images in the Hospital System. 3.3.2.2.2. Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Patient Root Find Patient Root Find Study Root Find Study Root Find.2.1.1.2.1.1.2.2.1.2.2.1 Implicit VR Little Endian 008.1.2 SCU None Explicit VR Little Endian 008.1.2.1 SCU None Implicit VR Little Endian 008.1.2 SCU None Explicit VR Little Endian 008.1.2.1 SCU None 3.3.2.2.2.1. Specific Conformance The ME provides Standard Conformance to the DICOM Query Service class. 3.3.2.2.2.1.1. Association length and duration The association is released after all data are transmitted to satisfy the actual request. In case of timeout (See Chapter 6.) the ME retries to establish an association automatically in background, displaying a dialog box with status information (number of retrievals done/to go before abort) and gives the user the possibility to cancel the procedure. 3.3.2.2.2.1.2. Error and Status handling In case of error or non-successful status the ME repeats the request automatically in background. If after a configurable number of failed trials the ME displays a dialog box with status information (number of retrievals done/to go before abort) and gives the user the possibility to cancel the procedure or to repeat it again. All necessary data will be cached in a queue handled by the ME. Only images that are not send successfully are part of the retransmission. - 13 / 21 -
3.4. Retrieve ME DICOM Connection Module - DICOM Conformance Statement This Module Entity provides Standard Conformance to the following DICOM V3.0 SOP Classes: SOP Class Name SOP Class UID Usage Verification 008.1.1 SCU/SCP Patient Root Move.2.1.2 SCU/SCP Patient Root Get.2.1.3 SCU Study Root Move.2.2.2 SCU/SCP Study Root Get.2.2.3 SCU 3.4.1. Association Establishment Policies 3.4.1.1. General For the Verification SOP Class the Retrieve ME initiates an Association when acting as a SCU, it accepts an Association when acting as a SCP. For the Patient Root Move, Patient Root Get, Study Root Query Retrieve Move and Study Root Get SOP Class the ME acting as a SCU initiates an Association to the Hospital Retrieve Provider. The size can be specified in a configuration file - the default value is 16k (16,384 Byte), the minimum value is 4k (4,096 Byte), the maximum value is 1MB (1,048,576 Byte). 3.4.1.2. Number of Associations The ME will attempt only one association establishment at a time for each SOP Class. 3.4.1.3. Asynchronous Nature Asynchronous operation is not supported. 3.4.1.4. Implementation Identifying Information The ME provides a single Implementation Class UID which is "1.2.276.0.43.100.4" and an implementation version name of "ifa DCM-QR 2.22" 3.4.2. Association Initiation Policy - There are 2 real world activities that initiate an association for Verification SOP Class: - Manual request by the Operator - Automatic request at system start - The ME initiates an association as a SCU for Patient Root Move, Patient Root Get, Study Root Move or Study Root Get SOP Class each time the user requests to retrieve one image or a collection of images. 3.4.2.1. Real World Activity Verify Availability of Destination 3.4.2.1.1. Associated Real-World Activity The associated Real-World Activity is the verification of the availability of the destination. The ME will attempt to use the DIMSE C-ECHO command to verify whether the receiving AE is able to negotiate an Association and respond. 3.4.2.1.2. Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Name UID Name List UID List Neg. Verification 008.1.1 Implicit VR Little Endian 008.1.2 SCU None - 14 / 21 -
3.4.2.1.2.1. Specific Conformance The ME provides Standard Conformance to the DICOM Verification Service class. 3.4.2.1.2.2. Association length and duration The association is released immediately after the response has been received. 3.4.2.1.2.3. Implementation Specific Behavior Not applicable. 3.4.2.2. Real World Activity Stores Images 3.4.2.2.1. Associated Real-World Activity The associated Real-World Activity is the attempt to store images in the Hospital System. 3.4.2.2.2. Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Patient Root Move Patient Root Move Patient Root Get Patient Root Get Study Root Move Study Root Move Study Root Get Study Root Get.2.1.2.2.1.2.2.1.3.2.1.3.2.2.2.2.2.2.2.2.3.2.2.3 Implicit VR Little Endian 008.1.2 SCU None Explicit VR Little Endian 008.1.2.1 SCU None Implicit VR Little Endian 008.1.2 SCU None Explicit VR Little Endian 008.1.2.1 SCU None Implicit VR Little Endian 008.1.2 SCU None Explicit VR Little Endian 008.1.2.1 SCU None Implicit VR Little Endian 008.1.2 SCU None Explicit VR Little Endian 008.1.2.1 SCU None 3.4.2.2.2.1. Specific Conformance The ME provides Standard Conformance to the DICOM Retrieve Service class. 3.4.2.2.2.1.1. Association length and duration The association is released after all data are transmitted to satisfy the actual request. In case of timeout (See Chapter 6.) the ME retries to establish an association automatically in background, displaying a dialog box with status information (number of retrievals done/to go before abort) and gives the user the possibility to cancel the procedure. - 15 / 21 -
3.4.2.2.2.1.2. Error and Status handling In case of error or non-successful status the ME repeats the request automatically in background. If after a configurable number of failed trials the ME displays a dialog box with status information (number of retrievals done/to go before abort) and gives the user the possibility to cancel the procedure or to repeat it again. All necessary data will be cached in a queue handled by the ME. Only images that are not send successfully are part of the retransmission. - 16 / 21 -
4. COMMUNICATION PROFILES 4.1. Supported Communication Stacks The TCP/IP stack is the only supported protocol. 4.1.1. TCP/IP Stack The ME s inherit the TCP/IP stack from the MS-WINDOWS system upon which they execute. 4.2. Physical Media Support The ME s are only software components (without any hardware parts)! Therefore they are indifferent to the physical medium over which TCP/IP executes; they can use all network adapters to which MS-WINDOWS can bind the TCP/IP protocol. 5. EXENTIONS/SPECIALIZATIONS/PRIVATIZATIONS Not applicable 6. CONFIGURATION The following parameters are configurable (in the manner described in the Product Installation Guide): - table of mapping of ME Title to Presentation Address (hostname and port number) - MWL ME title (default: ifa DCM-MWL) - Storage ME title (default: ifa DCM-STO) - Query ME title (default: ifa DCM-QR) - Retrieve ME title (default: ifa DCM-QR) - PDU size in kbyte (1024 Byte) min.: 4, default: 16, max.: 1024 - Timeout value in seconds min.: 1, default: 10, max.: 120 - Number of retrials min.: 0, default: 10, max.: 99 6.1. ME Title/Presentation Address Mapping - The ME titles are configurable - Node IP address, subnetmask, hostname, hostname aliases are configured by the local system administrator - TCP/IP port is configurable. 7. SUPPORT OF EXTENDED CHARACTER SETS No extended character sets are supported. - 17 / 21 -
8. IOD DESCRIPTION: 8.1. Visible Light IOD Legend: Column 3 (T): Type of Tag Column 4 (MaxLength): Maximum Length of Data in Character Column 5 (A): X: value is taken from MWL if present Column 6 (B): X: must be entered by user if MWL missing Column 7 (C): X: can be entered by user if not filled out tag will not be sent -: not applicable nd: not defined Attribute Tag Description T MaxLength A B C Remarks Patient IE (0010,0010) Patient Name 2 32 X X (0010,0020) Patient ID 2 64 X X (0010,0030) Patient s Birth Date 2 - X X (0010,0040) Patient s Sex 2 1 X X if MWL missing user can select M, F or O (0010,1000) Other Patient ID s 3 64 X X (0010,2160) Ethnic Group 3 16 X X (0010,21B0) Additional Patient History nd 10240 X only used in case of MWL (0010,4000) Patient Comments 3 10240 X X - 18 / 21 -
Study IE (0020,000D) Study Instance UID 1 - X if MWL missing generated by modality (0020,0010) Study ID 2 16 - - - generated by modality (0008,0020) Study Date 2 - - - - (0008,0030) Study Time 2 - - - - (0008,0050) Accession Number 2 16 X X (0008,0090) Referring Physician s 2 64 X X Name (0008,1030) Study Description 3 64 X (0008,1048) Physician(s) of Record 3 64 X X Series IE (0020,000E) Series Instance UID 1 - - - - generated by modality (0020,0011) Series Number 2 12 - - - generated by modality (0008,0060) Modality 1 - X if MWL missing set to XC (0008,1070) Operators Name 3 64 X X (0040,0007) Scheduled Procedure 3 64 X only used in case of MWL Step Description (0040.0009) Scheduled Procedure 1C 16 X only used in case of MWL Step ID (0040,1001) Requested Procedure ID 1C 16 X only used in case of MWL Equipment IE (0008,0070) Manufacturer 2 - - - - (0008,0080) Institution Name 3 64 - - - (0008,1010) Station Name 3 16 - - - (0008,1090) Manufacturer Model Name 3 - - - - - 19 / 21 -
Image IE (0008,0016) SOP Class UID 1 - - - -.1.77.1.4 (0008,0018) SOP Instance UID 1 - - - - (0008,0033) Image Time 1C - - - - (0008,0008) Image Type 1 - - - - values depend of image (0008,1140) Referenced Image 1C - - - - Sequemce (0008,1150) Referenced SOP Class 1C - - - - UID (0008,1155) Referenced SOP 1C - - - - Instance UID (0020,0013) Image Number 2 12 - - - generated for each image (0028,0002) Samples per Pixel 1 - - - - depends on image - can be 1 or 3 (0028,0004) Photometric 1 - - - - depends on image - can be MONOCHROME2 or RGB Interpretation (0028,0006) Planar Configuration 1C - - - - depends on image is not used or value is 0 (0028,0010) Rows 1 - - - - depends on image there is no limitation (0028,0011) Columns 1 - - - - depends on image there is no limitation (0028,0100) Bits Allocated 1 - - - - 8 (0028,0101) Bits Stored 1 - - - - 8 (0028,0102) High Bit 1 - - - - 7 (0028,0103) Pixel Representation 1 - - - - 0 (0040,0555) Acquisition Context - - - - TID2 (0040,A043) Concept Name Code - - - - depends on image (0040,A168) Concept Code - - - - depends on image (7FE0,0010) Pixel Data 1 - - - - - 20 / 21 -
IAG DICOM Connection Module - DICOM Conformance Statement 9. DEFINITION OF TERMS ASCII American Standard Code for Information Interchange AE Application Entity ANSI American National Standards Institute CR Computed Radiography CT Computed Tomography DICOM Digital Imaging and Communications in Medicine DIMSE DICOM Message Service Element DIMSE-C DICOM Message Service Element Composite DIMSE-N DICOM Message Service Element Normalized DOD Department Of Defense DX Digital Radiography FTP File Transfer Protocol (part of the TCP/IP protocol suite) HL7 Health Level 7 HIS/RIS Hospital Information System/ Radiology Information System ID Identifier IE Information Entity IHE Integrating the Healthcare Enterprise IHS Indian Health Services HIMSS Healthcare Information and Management Systems Society IS Information System IOD Information Object Definition ISO International Standards Organization ME Module Entity MPPS Modality Performed Procedure Step NEMA National Electrical Manufacturers Association MR Magnetic Resonance OSI Open Systems Interconnection PACS Picture Archiving and Communication System PDU Protocol Data Unit PN Person Name RFC Request For Comments RIS Radiology Information System RSNA Radiological Society of North America SCP Service Class Provider SCU Service Class User SOP Service-Object Pair TCP/IP Transmission Control Protocol/Internet Protocol UID Unique Identifier VA Department of Veterans Affairs VL Visible Light VR Value Representation XA X-Ray Angiography - 21 / 21 -