DICOM

Group of Companies ifa systems AG Augustinusstr. 11b

ifa united i-tech, Inc. 1850 SE 17th Street Suite C – Suite 309 33316 Fort Lauderdale, FL USA Phone: +1 954 713-1476 Fax: +1 954 713-1477 http://www.ifauniteditech.com info@ifauniteditech.com

50226 Frechen Germany Phone: +49 2234 93367-0 Fax: +49 2234 93367-30 http://www.ifasystems.com info@ifasystems.com

DICOM Connection Module V2.22

DICOM Conformance Statement Visible Light Storage Modality Worklist Query Retrieve Document Version 1.71  1999-2007

DICOM Connection Module

- DICOM Conformance Statement

- 2 / 26 -

DICOM Connection Module

DOCUMENT VERSION DATE

- DICOM Conformance Statement

AUTHOR

DESCRIPTION

PETER SCHERER, SEBASTIAN WENTE

CREATED

TH

PETER SCHERER, SEBASTIAN WENTE

REVISED

TH

PETER SCHERER, SEBASTIAN WENTE

REVISED

ST

PETER SCHERER

REVISED

ST

PETER SCHERER

REVISED

ST

PETER SCHERER

REVISED

PETER SCHERER

REVISED

PETER SCHERER

REVISED

PETER SCHERER

REVISED

TH

1.0

JUNE, 20 , 1999

1.1

AUGUST, 10 , 1999

1.2

AUGUST, 26 , 1999

1.3

JULY, 1 , 2001

1.4

JULY, 1 , 2002

1.5

JUNE, 1 , 2003

1.6

APRIL, 1 , 2005

ST

ST

1.7

OCTOBER, 1 , 2007

1.71

NOVEMBER, 15 , 2007

ST

- 3 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

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 to the site DICOM archive using the DICOM VL Photographic Image Storage or the Secondary Capture Image Storage Service Class as a Storage Class User - Query for patients, studies, series and images 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 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 Verification Modality Worklist Information Model - Find Secondary Capture Image Storage VL Photographic Image Storage Patient Root Query/Retrieve Information Model – Find Study Root Query/Retrieve Information Model – Find Patient Root Query/Retrieve Information Model – Move Patient Root Query/Retrieve Information Model – Get Study Root Query/Retrieve Information Model – Move Study Root Query/Retrieve Information Model – Get

SOP Class UID 1.2.840.10008.1.1 1.2.840.10008.5.1.4.31 1.2.840.10008.5.1.4.1.1.7 1.2.840.10008.5.1.4.1.1.77.1.4 1.2.840.10008.5.1.4.1.2.1.1

Service Class Role BOTH SCU SCU SCU SCU

1.2.840.10008.5.1.4.1.2.2.1

SCU

1.2.840.10008.5.1.4.1.2.1.2

SCU

1.2.840.10008.5.1.4.1.2.1.3

SCU

1.2.840.10008.5.1.4.1.2.2.2

SCU

1.2.840.10008.5.1.4.1.2.2.3

SCU

- 4 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

EXECUTIVE OVERVIEW ................................................................................................................. 4 1. INTRODUCTION .......................................................................................................................... 7 2. IMPLEMENTATION MODEL ....................................................................................................... 8 2.1. Application Data Flow Diagram ............................................................................................. 8 2.2. Functional definitions of ME ................................................................................................. 10 2.3. Sequencing of Real World Activities .................................................................................... 10 3. ME SPECIFICATIONS ............................................................................................................... 11 3.1. Worklist ME .......................................................................................................................... 11 3.1.1. Association Establishment Policies ............................................................................... 11 3.1.1.1. General ................................................................................................................... 11 3.1.1.2. Number of Associations .......................................................................................... 11 3.1.1.3. Asynchronous Nature ............................................................................................. 11 3.1.1.4. Implementation Identifying Information .................................................................. 11 3.1.2. Association Initiation Policy ........................................................................................... 11 3.1.2.1. Real World Activity Verify Availability of Destination .............................................. 11 3.1.2.1.1. Associated Real-World Activity ........................................................................ 11 3.1.2.1.2. Proposed Presentation Contexts ..................................................................... 12 3.1.2.1.2.1. Specific Conformance ............................................................................ 12 3.1.2.1.2.2. Association length and duration ............................................................. 12 3.1.2.1.2.3. Implementation Specific Behavior ......................................................... 12 3.1.2.2. Real World Activity Request Worklist ..................................................................... 12 3.1.2.2.1. Associated Real-World Activity ........................................................................ 12 3.1.2.2.2. Proposed Presentation Contexts ..................................................................... 12 3.1.2.2.2.1. SOP Specific Conformance ................................................................... 12 3.1.3. Association Initiation Policy ........................................................................................... 13 3.1.3.1. Real World Activity Verify Availability of Destination .............................................. 13 3.1.3.1.1. Associated Real-World Activity ........................................................................ 13 3.1.3.1.2. Presentation Context Table ............................................................................. 13 3.1.3.1.2.1. SOP Specific Conformance ................................................................... 13 3.1.3.1.3. Presentation Context Acceptance Criterion ..................................................... 13 3.1.3.1.4. Transfer Syntax Selection Policies .................................................................. 13 3.2. Storage ME .......................................................................................................................... 13 3.2.1. Association Establishment Policies ............................................................................... 13 3.2.1.1. General ................................................................................................................... 13 3.2.1.2. Number of Associations .......................................................................................... 13 3.2.1.3. Asynchronous Nature ............................................................................................. 14 3.2.1.4. Implementation Identifying Information .................................................................. 14 3.2.2. Association Initiation Policy ........................................................................................... 14 3.2.2.1. Real World Activity Verify Availability of Destination .............................................. 14 3.2.2.1.1. Associated Real-World Activity ........................................................................ 14 3.2.2.1.2. Proposed Presentation Contexts ..................................................................... 14 3.2.2.1.2.1. Specific Conformance ............................................................................ 14 3.2.2.1.2.2. Association length and duration ............................................................. 14 3.2.2.1.2.3. Implementation Specific Behavior ......................................................... 14 3.2.2.2. Real World Activity Stores Images ......................................................................... 14 3.2.2.2.1. Associated Real-World Activity ........................................................................ 14 3.2.2.2.2. Proposed Presentation Contexts ..................................................................... 14 3.2.2.2.2.1. Specific Conformance ............................................................................ 15 3.2.3. Association Initiation Policy ........................................................................................... 15 3.2.3.1. Real World Activity Verify Availability of Destination .............................................. 15 3.2.3.1.1. Associated Real-World Activity ........................................................................ 15 3.2.3.1.2. Presentation Context Table ............................................................................. 15 3.2.3.1.2.1. SOP Specific Conformance ................................................................... 15 3.2.3.1.3. Presentation Context Acceptance Criterion ..................................................... 15 3.2.3.1.4. Transfer Syntax Selection Policies .................................................................. 15 3.3. Query ME ............................................................................................................................. 16 3.3.1. Association Establishment Policies ............................................................................... 16 3.3.1.1. General ................................................................................................................... 16 - 5 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

3.3.1.2. Number of Associations .......................................................................................... 16 3.3.1.3. Asynchronous Nature ............................................................................................. 16 3.3.1.4. Implementation Identifying Information .................................................................. 16 3.3.2. Association Initiation Policy ........................................................................................... 16 3.3.2.1. Real World Activity Verify Availability of Destination .............................................. 16 3.3.2.1.1. Associated Real-World Activity ........................................................................ 16 3.3.2.1.2. Proposed Presentation Contexts ..................................................................... 16 3.3.2.1.2.1. Specific Conformance ............................................................................ 17 3.3.2.1.2.2. Association length and duration ............................................................. 17 3.3.2.1.2.3. Implementation Specific Behavior ......................................................... 17 3.3.2.2. Real World Activity Stores Images ......................................................................... 17 3.3.2.2.1. Associated Real-World Activity ........................................................................ 17 3.3.2.2.2. Proposed Presentation Contexts ..................................................................... 17 3.3.2.2.2.1. Specific Conformance ............................................................................ 17 3.3.3. Association Initiation Policy ........................................................................................... 18 3.3.3.1. Real World Activity Verify Availability of Destination .............................................. 18 3.3.3.1.1. Associated Real-World Activity ........................................................................ 18 3.3.3.1.2. Presentation Context Table ............................................................................. 18 3.3.3.1.2.1. SOP Specific Conformance ................................................................... 18 3.3.3.1.3. Presentation Context Acceptance Criterion ..................................................... 18 3.3.3.1.4. Transfer Syntax Selection Policies .................................................................. 18 3.4. Retrieve ME ......................................................................................................................... 18 3.4.1. Association Establishment Policies ............................................................................... 18 3.4.1.1. General ................................................................................................................... 18 3.4.1.2. Number of Associations .......................................................................................... 18 3.4.1.3. Asynchronous Nature ............................................................................................. 18 3.4.1.4. Implementation Identifying Information .................................................................. 19 3.4.2. Association Initiation Policy ........................................................................................... 19 3.4.2.1. Real World Activity Verify Availability of Destination .............................................. 19 3.4.2.1.1. Associated Real-World Activity ........................................................................ 19 3.4.2.1.2. Proposed Presentation Contexts ..................................................................... 19 3.4.2.1.2.1. Specific Conformance ............................................................................ 19 3.4.2.1.2.2. Association length and duration ............................................................. 19 3.4.2.1.2.3. Implementation Specific Behavior ......................................................... 19 3.4.2.2. Real World Activity Stores Images ......................................................................... 19 3.4.2.2.1. Associated Real-World Activity ........................................................................ 19 3.4.2.2.2. Proposed Presentation Contexts ..................................................................... 19 3.4.2.2.2.1. Specific Conformance ............................................................................ 20 3.4.3. Association Initiation Policy ........................................................................................... 20 3.4.3.1. Real World Activity Verify Availability of Destination .............................................. 20 3.4.3.1.1. Associated Real-World Activity ........................................................................ 20 3.4.3.1.2. Presentation Context Table ............................................................................. 20 3.4.3.1.2.1. SOP Specific Conformance ................................................................... 20 3.4.3.1.3. Presentation Context Acceptance Criterion ..................................................... 20 3.4.3.1.4. Transfer Syntax Selection Policies .................................................................. 21 4. COMMUNICATION PROFILES ................................................................................................. 22 4.1. Supported Communication Stacks ...................................................................................... 22 4.1.1. TCP/IP Stack ................................................................................................................. 22 4.2. Physical Media Support ....................................................................................................... 22 5. EXENTIONS/SPECIALIZATIONS/PRIVATIZATIONS .............................................................. 22 6. CONFIGURATION ..................................................................................................................... 22 6.1. ME Title/Presentation Address Mapping ............................................................................. 22 7. SUPPORT OF EXTENDED CHARACTER SETS ..................................................................... 22 8. IOD DESCRIPTION: .................................................................................................................. 23 8.1. Visible Light IOD .................................................................................................................. 23 9. DEFINITION OF TERMS............................................................................................................ 26

- 6 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

1. INTRODUCTION 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.

- 7 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

2. IMPLEMENTATION MODEL 2.1. Application Data Flow Diagram Figure 1 –DICOM Connection Module – Data Flow Model

Verification SCU/SCP

Provide Worklist functionality

Worklist Module Entity

Modality Worklist SCP

Verification SCU/SCP

Upload Images

Storage Module Entity

Remote Storage SCP

External Environment (DICOM Host)

Internal Environment (CPR subnet) DICOM Interface

- 8 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

Verification SCU/SCP

Provide Query functionality

Query Module Entity

Query SCP

Verification SCU/SCP

Download images

Retrieve Module Entity

Retrieve SCP

External Environment (DICOM Host)

Internal Environment (CPR subnet) DICOM Interface

- 9 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

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.

- 10 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

3. ME SPECIFICATIONS 3.1. Worklist ME This Module Entity provides Standard Conformance to the following DICOM V3.0 SOP Classes: SOP Class Name Verification Modality Worklist Information Model Find

SOP Class UID 1.2.840.10008.1.1 1.2.840.10008.5.1.4.31

Usage SCU/SCP 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.

- 11 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

3.1.2.1.2. Proposed Presentation Contexts

Abstract Syntax Name UID Verification

Presentation Context Table Transfer Syntax Name List UID List

1.2.840.10008.1.1

Implicit VR Little Endian

1.2.840.10008.1.2

Role

Ext. Neg.

SCU

None

Role

Ext. Neg.

SCU SCU

None 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

Abstract Syntax Name UID Worklist Worklist

Presentation Context Table Transfer Syntax Name List UID List

1.2.840.10008.5.1.4.31 1.2.840.10008.5.1.4.31

Implicit VR Little Endian Explicit VR Little Endian

1.2.840.10008.1.2 1.2.840.10008.1.2.1

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.

- 12 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

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.

3.1.3. Association Initiation Policy 3.1.3.1. Real World Activity Verify Availability of Destination 3.1.3.1.1. Associated Real-World Activity The associated Real-World Activity is the request for a DIMSE C-Echo to the AE-title.

3.1.3.1.2. Presentation Context Table

Abstract Syntax Name UID Verification

1.2.840.10008.1.1

Presentation Context Table Transfer Syntax Name List UID List Implicit VR Little Endian

1.2.840.10008.1.2

Role

Ext. Neg.

SCP

None

3.1.3.1.2.1. SOP Specific Conformance The ME provides Standard Conformance to the DICOM Verification Service class.

3.1.3.1.3. Presentation Context Acceptance Criterion The ME will always accept a Presentation Context for the Verification SOP class with the DICOM Default Transfer Syntax.

3.1.3.1.4. Transfer Syntax Selection Policies not applicable

3.2. Storage ME This Module Entity provides Standard Conformance to the following DICOM V3.0 SOP Classes: SOP Class Name Verification Secondary Image Capture VL Photographic Image Storage

SOP Class UID 1.2.840.10008.1.1 1.2.840.10008.5.1.4.1.1.7 1.2.840.10008.5.1.4.1.1.77.1.4

Usage SCU/SCP SCU 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.

- 13 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

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

Abstract Syntax Name UID Verification

1.2.840.10008.1.1

Presentation Context Table Transfer Syntax Name List UID List Implicit VR Little Endian

1.2.840.10008.1.2

Role

Ext. Neg.

SCU

None

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 Name UID Name List UID List Secondary 1.2.840.10 Implicit VR Little Endian 1.2.840.10008.1.2 Image Capture 008.5.1.4.1 Storage .1.7

- 14 / 26 -

Role SCU

Extended Negotiation None

DICOM Connection Module Secondary Image Capture Storage VL Photographic Image Storage VL Photographic Image Storage VL Photographic Image Storage

1.2.840.10 008.5.1.4.1 .1.7 1.2.840.10 008.5.1.4.1 .1.77.1.4 1.2.840.10 008.5.1.4.1 .1.77.1.4 1.2.840.10 008.5.1.4.1 .1.77.1.4

- DICOM Conformance Statement

Explicit VR Little Endian

1.2.840.10008.1.2.1

SCU

None

Implicit VR Little Endian

1.2.840.10008.1.2

SCU

None

Explicit VR Little Endian

1.2.840.10008.1.2.1

SCU

None

JPEG Baseline

1.2.840.10008.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.

3.2.3. Association Initiation Policy 3.2.3.1. Real World Activity Verify Availability of Destination 3.2.3.1.1. Associated Real-World Activity The associated Real-World Activity is the request for a DIMSE C-Echo to the AE-title.

3.2.3.1.2. Presentation Context Table

Abstract Syntax Name UID Verification

1.2.840.10008.1.1

Presentation Context Table Transfer Syntax Name List UID List Implicit VR Little Endian

1.2.840.10008.1.2

Role

Ext. Neg.

SCP

None

3.2.3.1.2.1. SOP Specific Conformance The ME provides Standard Conformance to the DICOM Verification Service class.

3.2.3.1.3. Presentation Context Acceptance Criterion The ME will always accept a Presentation Context for the Verification SOP class with the DICOM Default Transfer Syntax.

3.2.3.1.4. Transfer Syntax Selection Policies - 15 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

not applicable

3.3. Query ME This Module Entity provides Standard Conformance to the following DICOM V3.0 SOP Classes: SOP Class Name Verification Patient Root Query Retrieve Find Study Root Query Retrieve Find

SOP Class UID 1.2.840.10008.1.1 1.2.840.10008.5.1.4.1.2.1.1 1.2.840.10008.5.1.4.1.2.2.1

Usage SCU/SCP SCU 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 Query Retrieve Find and Study Root Query Retrieve 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 Query Retrieve Find or Study Root Query Retrieve 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

Name

Abstract Syntax UID

Presentation Context Table Transfer Syntax Name List UID List

- 16 / 26 -

Role

Ext. Neg.

DICOM Connection Module Verification

1.2.840.10008.1.1

- DICOM Conformance Statement

Implicit VR Little Endian

1.2.840.10008.1.2

SCU

None

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 Transfer Syntax Name List UID List Implicit VR Little Endian 1.2.840.10008.1.2

Abstract Syntax Name UID Patient Root 1.2.840.10 Query Retrieve 008.5.1.4.1 Find .2.1.1 Patient Root 1.2.840.10 Explicit VR Little Endian Query Retrieve 008.5.1.4.1 Find .2.1.1 Study Root 1.2.840.10 Implicit VR Little Endian Query Retrieve 008.5.1.4.1 Find .2.2.1 Study Root 1.2.840.10 Explicit VR Little Endian Query Retrieve 008.5.1.4.1 Find .2.2.1

Role SCU

Extended Negotiation None

1.2.840.10008.1.2.1

SCU

None

1.2.840.10008.1.2

SCU

None

1.2.840.10008.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.

- 17 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

3.3.3. Association Initiation Policy 3.3.3.1. Real World Activity Verify Availability of Destination 3.3.3.1.1. Associated Real-World Activity The associated Real-World Activity is the request for a DIMSE C-Echo to the AE-title.

3.3.3.1.2. Presentation Context Table

Abstract Syntax Name UID Verification

1.2.840.10008.1.1

Presentation Context Table Transfer Syntax Name List UID List Implicit VR Little Endian

1.2.840.10008.1.2

Role

Ext. Neg.

SCP

None

3.3.3.1.2.1. SOP Specific Conformance The ME provides Standard Conformance to the DICOM Verification Service class.

3.3.3.1.3. Presentation Context Acceptance Criterion The ME will always accept a Presentation Context for the Verification SOP class with the DICOM Default Transfer Syntax.

3.3.3.1.4. Transfer Syntax Selection Policies not applicable

3.4. Retrieve ME This Module Entity provides Standard Conformance to the following DICOM V3.0 SOP Classes: SOP Class Name Verification Patient Root Query Retrieve Move Patient Root Query Retrieve Get Study Root Query Retrieve Move Study Root Query Retrieve Get

SOP Class UID 1.2.840.10008.1.1 1.2.840.10008.5.1.4.1.2.1.2 1.2.840.10008.5.1.4.1.2.1.3 1.2.840.10008.5.1.4.1.2.2.2 1.2.840.10008.5.1.4.1.2.2.3

Usage SCU/SCP SCU/SCP SCU SCU/SCP 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 Query Retrieve Move, Patient Root Query Retrieve Get, Study Root Query Retrieve Move and Study Root Query Retrieve 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.

- 18 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

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 Query Retrieve Move, Patient Root Query Retrieve Get, Study Root Query Retrieve Move or Study Root Query Retrieve 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 Transfer Syntax Name List UID List

Abstract Syntax Name UID Verification

1.2.840.10008.1.1

Implicit VR Little Endian

1.2.840.10008.1.2

Role

Ext. Neg.

SCU

None

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 Transfer Syntax Name List UID List Implicit VR Little Endian 1.2.840.10008.1.2

Abstract Syntax Name UID Patient Root 1.2.840.10 Query Retrieve 008.5.1.4.1 Move .2.1.2 Patient Root 1.2.840.10 Explicit VR Little Endian Query Retrieve 008.5.1.4.1 Move .2.1.2

- 19 / 26 -

1.2.840.10008.1.2.1

Role SCU

Extended Negotiation None

SCU

None

DICOM Connection Module Patient Root Query Retrieve Get Patient Root Query Retrieve Get Study Root Query Retrieve Move Study Root Query Retrieve Move Study Root Query Retrieve Get Study Root Query Retrieve Get

1.2.840.10 008.5.1.4.1 .2.1.3 1.2.840.10 008.5.1.4.1 .2.1.3 1.2.840.10 008.5.1.4.1 .2.2.2 1.2.840.10 008.5.1.4.1 .2.2.2 1.2.840.10 008.5.1.4.1 .2.2.3 1.2.840.10 008.5.1.4.1 .2.2.3

- DICOM Conformance Statement

Implicit VR Little Endian

1.2.840.10008.1.2

SCU

None

Explicit VR Little Endian

1.2.840.10008.1.2.1

SCU

None

Implicit VR Little Endian

1.2.840.10008.1.2

SCU

None

Explicit VR Little Endian

1.2.840.10008.1.2.1

SCU

None

Implicit VR Little Endian

1.2.840.10008.1.2

SCU

None

Explicit VR Little Endian

1.2.840.10008.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.

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.

3.4.3. Association Initiation Policy 3.4.3.1. Real World Activity Verify Availability of Destination 3.4.3.1.1. Associated Real-World Activity The associated Real-World Activity is the request for a DIMSE C-Echo to the AE-title.

3.4.3.1.2. Presentation Context Table

Abstract Syntax Name UID Verification

1.2.840.10008.1.1

Presentation Context Table Transfer Syntax Name List UID List Implicit VR Little Endian

1.2.840.10008.1.2

3.4.3.1.2.1. SOP Specific Conformance The ME provides Standard Conformance to the DICOM Verification Service class.

3.4.3.1.3. Presentation Context Acceptance Criterion

- 20 / 26 -

Role

Ext. Neg.

SCP

None

DICOM Connection Module

- DICOM Conformance Statement

The ME will always accept a Presentation Context for the Verification SOP class with the DICOM Default Transfer Syntax.

3.4.3.1.4. Transfer Syntax Selection Policies not applicable

- 21 / 26 -

DICOM Connection Module

- DICOM Conformance Statement

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.

- 22 / 26 -

DICOM Connection Module - DICOM Conformance Statement

8. IOD DESCRIPTION: 8.1. Visible Light IOD Legend: Column 3 (T): Column 4 (MaxLength): Column 5 (A): Column 6 (B): Column 7 (C): -: nd: Attribute Tag Patient IE (0010,0010) (0010,0020) (0010,0030) (0010,0040) (0010,1000) (0010,2160) (0010,21B0) (0010,4000)

Type of Tag Maximum Length of Data in Character X: value is taken from MWL if present X: must be entered by user if MWL missing X: can be entered by user – if not filled out tag will not be sent not applicable not defined

Description

T

MaxLength

A

B

Patient Name Patient ID Patient’s Birth Date Patient’s Sex Other Patient ID’s Ethnic Group Additional Patient History Patient Comments

2 2 2 2 3 3 nd 3

32 64 1 64 16 10240 10240

X X X X X X X X

X X

C

Remarks

X if MWL missing user can select „M“, „F“ or „O“

X X X

only used in case of MWL X

- 23 / 26 -

DICOM Connection Module - DICOM Conformance Statement Study IE (0020,000D) (0020,0010) (0008,0020) (0008,0030) (0008,0050) (0008,0090) (0008,1030) (0008,1048) Series IE (0020,000E) (0020,0011) (0008,0060) (0008,1070) (0040,0007)

Study Instance UID Study ID Study Date Study Time Accession Number Referring Physician’s Name Study Description Physician(s) of Record

Series Instance UID Series Number Modality Operators’ Name Scheduled Procedure Step Description (0040.0009) Scheduled Procedure Step ID (0040,1001) Requested Procedure ID Equipment IE (0008,0070) Manufacturer (0008,0080) Institution Name (0008,1010) Station Name (0008,1090) Manufacturer Model Name

1 2 2 2 2 2

16 16 64

X X X

3 3

64 64

X

1 2 1 3 3

12 64 64

X X X

1C

16

X

only used in case of MWL

1C

16

X

only used in case of MWL

2 3 3 3

64 16 -

-

X X

-

if MWL missing generated by modality generated by modality

X X -

-

generated by modality generated by modality if MWL missing set to „XC“

X only used in case of MWL

-

- 24 / 26 -

-

DICOM Connection Module - DICOM Conformance Statement Image IE (0008,0016) (0008,0018) (0008,0033) (0008,0008) (0008,1140) (0008,1150) (0008,1155) (0020,0013) (0028,0002) (0028,0004) (0028,0006) (0028,0010) (0028,0011) (0028,0100) (0028,0101) (0028,0102) (0028,0103) (0040,0555) (0040,A043) (0040,A168) (7FE0,0010)

SOP Class UID SOP Instance UID Image Time Image Type Referenced Image Sequemce Referenced SOP Class UID Referenced SOP Instance UID Image Number Samples per Pixel Photometric Interpretation Planar Configuration Rows Columns Bits Allocated Bits Stored High Bit Pixel Representation Acquisition Context Concept Name Code Concept Code Pixel Data

1 1 1C 1 1C

-

-

-

-

1C

-

-

-

-

1C

-

-

-

-

2 1 1

12 -

-

-

-

generated for each image depends on image - can be 1 or 3 depends on image - can be MONOCHROME2 or RGB

1C 1 1 1 1 1 1

-

-

-

-

depends on image – is not used or value is 0 depends on image – there is no limitation depends on image –there is no limitation 8 8 7 0 TID2 depends on image depends on image

1

- 25 / 26 -

1.2.840.10008.5.1.4.1.1.77.1.4

values depend of image

IAG DICOM Connection Module - DICOM Conformance Statement

9. DEFINITION OF TERMS ASCII AE ANSI CR CT DICOM DIMSE DIMSE-C DIMSE-N DOD DX FTP HL7 HIS/RIS ID IE IHE IHS HIMSS IS IOD ISO ME MPPS NEMA MR OSI PACS PDU PN RFC RIS RSNA SCP SCU SOP TCP/IP UID VA VL VR XA

American Standard Code for Information Interchange Application Entity American National Standards Institute Computed Radiography Computed Tomography Digital Imaging and Communications in Medicine DICOM Message Service Element DICOM Message Service Element Composite DICOM Message Service Element Normalized Department Of Defense Digital Radiography File Transfer Protocol (part of the TCP/IP protocol suite) Health Level 7 Hospital Information System/ Radiology Information System Identifier Information Entity Integrating the Healthcare Enterprise Indian Health Services Healthcare Information and Management Systems Society Information System Information Object Definition International Standards Organization Module Entity Modality Performed Procedure Step National Electrical Manufacturers Association Magnetic Resonance Open Systems Interconnection Picture Archiving and Communication System Protocol Data Unit Person Name Request For Comments Radiology Information System Radiological Society of North America Service Class Provider Service Class User Service-Object Pair Transmission Control Protocol/Internet Protocol Unique Identifier Department of Veterans Affairs Visible Light Value Representation X-Ray Angiography

- 26 / 26 -