ONIS 2.0 DICOM CLIENT. DICOM 3 Conformance statement

(1)

ONIS 2.0 DICOM CLIENT

DICOM 3 Conformance statement

(2)

0. Introduction

This chapter provides general information about the purpose, scope and content of this Conformance Statement.

0.1 Scope

This document is the DICOM 3.0 Conformance Statement for the DICOM Image Client plugin of ONIS 2.0 developed by Digitalcore co,ltd. In this document, this DICOM server component will be called “ONIS DICOM Client”.

0.2 Standards

Digital Imaging and Communications in Medicine (DICOM). NEMA Standard Publications PS 3.1-16 and Supplements.

0.3 Intended Audience

The reader of this document is concerned with implementing an Enterprise wide DICOM network or Integration issues or software design.

0.4 Important Remarks

DICOM does not guarantee interoperability and this conformance statement is only the first stage of validating a connection between “ONIS DICOM Client” and other DICOM device.

0.5 Definitions

Definitions, terms and abbreviations used in this document are defined within the different parts of the DICOM standard.

AE Application Entity

DB Database

DICOM Digital Imaging and Communications in Medicine

(5)

DIMSE DICOM Message Service Element

DIMSE-C DICOM Message Service Element-Composite

DIMSE-N DICOM Message Service Element-Normative

IOD Information Object Definition

ISO International Standard Organization

NEMA National Electrical Manufacturers Association

OSI Open Systems Interconnection

PACS Picture Archive & Communication System

PDU Protocol Data Unit

SCU Service Class User (DICOM Client)

SCP Service Class Provider (DICOM Server)

SOP Service-Object Pair

Tag A 32 bit integer consisting of a group/element pair

TCP/IP Transmission Control Protocol/Internet Protocol

UID Unique Identifier Attribute

VR Value Representation

VM Value Multiplicity

(6)

1. Implementation Model

The “ONIS DICOM Client is a medical imaging application that receives objects (images) for storage but does not allow the query and retrieval of these objects. It runs on the following Microsoft Windows platform:

. Windows XP Professional

. Windows 2003 Server

. Windows Vista 32 & 64 bits

- Windows 2008 Server

as a plugin for ONIS 2.0 that accepts association requests from external applications.

“ONIS DICOM Client” can be started automatically when ONIS 2.0 starts up. Users can modify the different available settings of the “ONIS DICOM Client” from the preference panel of ONIS 2.0.

The following parameters of the “ONIS DICOM Client” are configurable from the preference panel of ONIS 2.0:

- Application Entity Title of the DICOM Server - Listening port number

- Maximum number of clients which can be connected at same time - Time out settings (Idle, Connection, Move and Store)

- PDU Size

- Security options (verification of the called and calling AE title and/or IP Addresses).

After modifying any of the above settings, the “ONIS DICOM Client” needs to be restarted in order for the changes to take effect.

Through the “Clients” page of the preference panel of ONIS 2.0, the definition of the AE Applications that can connect to the DICOM Server can be defined. The following parameters can be defined for each AE Application:

- Application Entity Title - IP Address

- Port Number (when this AE Application will be used as an SCP)

(7)

- Rights (Find, Get, Move and Store rights)

1.1 Application Data Flow Diagram

1.2 Functional Definitions

“ONIS DICOM Client” has a single Application Entity (AE) for all service Classes.

ONIS DICOM Client Plugin Image Files

Database

Request Echo Check

Request Query/Retreive

Request Image Store

Request Image transfer

Figure 1. Implementation Model

(8)

“ONIS DICOM Client” can act as an SCU and SCP for Storage Service Class, Query/Retrieve Service Class and Verification Service Class operations.

1.3 Sequencing of Real-World Activities

“ONIS DICOM Client” is a full multi-threaded application.

2. AE Specifications

2.1 “ONIS DICOM Client” AE Specification

The Application Entity provides Standard Conformance to the following DICOM V3.0 SOP Classes as a SCP and SCU:

SOP Class Name SOP Class UID Role

Verification 1.2.840.10008.1.1 SCU/SCP

CR Image Storage 1.2.840.10008.5.1.4.1.1.1 SCU/SCP CT Image Storage 1.2.840.10008.5.1.4.1.1.2 SCU/SCP Ultrasound Multi-frame

Image Storage Retired

1.2.840.10008.5.1.4.1.1.3 SCU/SCP

Ultrasound Multi-frame Image Storage

1.2.840.10008.5.1.4.1.1.3.1 SCU/SCP

MR Image Storage 1.2.840.10008.5.1.4.1.1.4 SCU/SCP Nuclear Medicine Image

Storage Retired

1.2.840.10008.5.1.4.1.1.5 SCU/SCP

Ultrasound Image Storage Retired

1.2.840.10008.5.1.4.1.1.6 SCU/SCP

Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 SCU/SCP Secondary Capture Image

Storage

1.2.840.10008.5.1.4.1.1.7 SCU/SCP

(9)

X-Ray Angiographic Image Storage

1.2.840.10008.5.1.4.1.1.12.1 SCU/SCP

X-Ray Radiofluoroscopic Image Storage

1.2.840.10008.5.1.4.1.1.12.2 SCU/SCP

Nuclear Medicine Image Storage

1.2.840.10008.5.1.4.1.1.20 SCU/SCP

Positron Emission

Tomography Image Storage

1.2.840.10008.5.1.4.1.1.128 SCU/SCP

Radiotherapy Image Storage

1.2.840.10008.5.1.4.1.1.481.1 SCU/SCP

VL Endoscopic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.1 SCU/SCP

VL Microscopic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.2 SCU/SCP

VL Slide-Coordinates Microscopic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.3 SCU/SCP

VL Photographic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.4 SCU/SCP

Digital X-Ray Image Storage- For Presentation

1.2.840.10008.5.1.4.1.1.1.1 SCU/SCP

Digital X-Ray Image Storage- For Processing

1.2.840.10008.5.1.4.1.1.1.1.1 SCU/SCP

Digital Mammography Image Storage- For Presentation

1.2.840.10008.5.1.4.1.1.1.2 SCU/SCP

Digital Mammography Image Storage- For Processing

1.2.840.10008.5.1.4.1.1.1.2.1 SCU/SCP

Digital Intra-oral X-Ray Image-For Presentation

1.2.840.10008.5.1.4.1.1.1.3 SCU/SCP

Digital Intra-oral X-Ray Image-For Processing

1.2.840.10008.5.1.4.1.1.1.3.1 SCU/SCP

Patient Root Query/Retrieve

Information Model - FIND

1.2.840.10008.5.1.4.1.2.1.1 SCU

(10)

Patient Root Query/Retrieve Information Model – MOVE

1.2.840.10008.5.1.4.1.2.1.2 SCU

Patient Root Query/Retrieve

Information Model – GET

1.2.840.10008.5.1.4.1.2.1.3 SCU

Study Root Query/Retrieve Information Model – FIND

1.2.840.10008.5.1.4.1.2.2.1 SCU

Study Root Query/Retrieve Information Model – MOVE

1.2.840.10008.5.1.4.1.2.2.2 SCU

Study Root Query/Retrieve Information Model – GET

1.2.840.10008.5.1.4.1.2.2.3 SCU

Patient Study Query/Retrieve

Information Model – FIND

1.2.840.10008.5.1.4.1.2.3.1 SCU

Patient Study Query/Retrieve Information Model – MOVE

1.2.840.10008.5.1.4.1.2.3.2 SCU

Patient Study Query/Retrieve

Information Model – GET

1.2.840.10008.5.1.4.1.2.3.3 SCU

2.1.1 Association Establishment Policies

This section describes the conditions under which the “ONIS DICOM Client” AE will either initiate or accept an association.

2.1.1.1 General

(11)

The AE will accept any PDU length, offered on associations initiated by remote applications. However, the actual PDU size will not exceed the maximum size requested by the SCP. It is recommended that it does not exceed 64 Kbytes.

2.1.1.2 Number of Associations

“ONIS DICOM Client” supports multiple associations in both SCP and SCU. The maximum number of associations opened simultaneously can be defined in the preference panel of ONIS 2.0. This number should not exceed 64.

2.1.1.3 Asynchronous Nature

“ONIS DICOM Client” does not support negotiation of multiple outstanding transactions.

2.1.1.4 Implementation Identifying Information

Implementation Class UID: 1.2.392.200193

Implementation Version Name: ONIS_Server 2.0

2.1.2 Association Initiation Policy

“ONIS DICOM Client” Initiates associations under the following conditions:

- User invokes a CFIND request to a remote AE - User invokes a CMOVE request to a remote AE - User invokes a CGET request to a remote AE - User invokes Image Store to a remote AE

2.1.2.1 CFIND requests sent to to remoted AE

(12)

2.1.2.1.1 Associated Real-World Activity

The associated Real-World Activities is to retrieve patient, study, series and/or image information from a DICOM Query/Retrieve SCP.

2.1.2.1.2 Proposed Presentation Contexts table

Abstract Syntax Transfer Syntax

Name UID Name UID

Patient Root - FIND

1.2.840.10008.5.

1.4.1.2.1.1

Implicit VR Little Endian

Explicit VR Little Endian

Explicit VR Big Endian

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2 Study Root –

FIND

1.2.840.10008.5.

1.4.1.2.2.1

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2 Patient Study -

FIND

1.2.840.10008.5.

1.4.1.2.3.1

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2

Table 2.1.2.1.2

2.1.2.1.3 SOP Specific Conformance for Patient Root – FIND SOP Class

The following attributes may be included in the Patient Root Query:

Patient Level Key Attributes

(13)

Description Tag

Patient ID (0010, 0020)

Patient’s Name (0010, 0010) Patient’s Sex (0010, 0040) Patient’s Birth Date (0010, 0030) Patient’s Birth Time (0010, 0032)

Study Level Key Attributes

Description Tag

Study Instance UID (0020, 000D) Study Date (0008, 0020)

Study Time (0008, 0030)

Accession Number (0008, 0050)

Study ID (0020, 0010)

Study Description (0008, 1030)

Series Level Key Attributes

Description Tag

Series Instance UID (0020, 000E)

Modality (0008, 0060)

Series Number (0020, 0011) Series Date (0008, 0021) Series Time (0008, 0031) Series Description (0008, 103E)

Image Level Key Attributes

Description Tag

SOP Instance UID (0008, 0018) Instance Number (0020, 0013)

SOP Class UID (0008, 0016) Acquisition Number (0020, 0012)

(14)

2.1.2.1.4 SOP Specific Conformance for Study Root – FIND SOP Class

The following attributes may be included in the Study Root Query:

Description Tag

Study Time (0008, 0030)

Study ID (0020, 0010)

Patient’s Name (0010, 0010)

Patient ID (0010, 0020)

Study Description (0008, 1030) Patient’s Sex (0010, 0040) Patient’s Birth Date (0010, 0030) Patient’s Birth Time (0010, 0032)

Series Level Key Attributes

Description Tag

Series Instance UID (0020, 000E)

Modality (0008, 0060)

Series Number (0020, 0011) Series Date (0008, 0021) Series Time (0008, 0031) Series Description (0008, 103E)

Image Level Key Attributes

Description Tag

SOP Instance UID (0008, 0018) Instance Number (0020, 0013)

(15)

SOP Class UID (0008, 0016) Acquisition Number (0020, 0012)

2.1.2.1.5 SOP Specific Conformance for Patient Study – FIND SOP Class

The following attributes may be included in the Patient Study Query:

Patient Level Key Attributes

Description Tag

Patient ID (0010, 0020)

Patient’s Name (0010, 0010) Patient’s Sex (0010, 0040) Patient’s Birth Date (0010, 0030) Patient’s Birth Time (0010, 0032)

Description Tag

Study Time (0008, 0030)

Study ID (0020, 0010)

Study Description (0008, 1030)

2.1.2.2 CMOVE requests to a remote AE

The associated Real-World Activities is the transfer of images from a DICOM CMOVE SCP to a destination AE.

(16)

Name UID Name UID

Patient Root - MOVE

1.2.840.10008.5.

1.4.1.2.1.2

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2 Study Root –

MOVE

1.2.840.10008.5.

1.4.1.2.2.2

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2 Patient Study -

MOVE

1.2.840.10008.5.

1.4.1.2.3.2

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2

Table 2.1.2.2.2

2.1.2.3 CGET requests to a remote AE

The associated Real-World Activities is to retrieve images from a DICOM CGET SCP.

(17)

Name UID Name UID

Patient Root - GET

1.2.840.10008.5.

1.4.1.2.1.3

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2 Study Root –

GET

1.2.840.10008.5.

1.4.1.2.2.3

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2 Patient Study -

GET

1.2.840.10008.5.

1.4.1.2.3.3

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2

Table 2.1.2.3.2

2.1.2.4 Image Store to a remote AE

The Associated Real-World Activity with the Storage Service is the transfer of images to a remote DICOM Storage SCP selected by the user.

2.1.2.4.2 Proposed Presentation Contexts

The Abstract syntax corresponds to the Storage SOP Class UID specified in the SOP Instance being transferred.

If the transfer syntax of the SOP Instance to be transferred is not Implicit VR Little

(18)

1) Transfer syntax of the original SOP Instance 2) Implicit VR Little Endian

“ONIS DICOM Client” always includes Implicit VR Little Endian as proposed transfer syntax for each abstract syntax.

The proposed transfer syntax can be one of the following:

Name UID

Implicit VR Little Endian 1.2.840.10008.1.2 Explicit VR Little Endian 1.2.840.10008.1.2.1 Explicit VR Big Endian 1.2.840.10008.1.2.2 Baseline JPEG (Process 1) 1.2.840.10008.1.2.4.50 Extended JPEG (Process 2,4) 1.2.840.10008.1.2.4.51 Extended JPEG (Process 3,5) 1.2.840.10008.1.2.4.52 Spectral JPEG (NonHier, Process 6,8) 1.2.840.10008.1.2.4.53 Spectral JPEG (NonHier, Process 7,9) 1.2.840.10008.1.2.4.54 Full JPEG (NonHier, Process 10, 12) 1.2.840.10008.1.2.4.55 Full JPEG (NonHier, Process 11,13) 1.2.840.10008.1.2.4.56 Lossless JPEG (NonHier, Process 14) 1.2.840.10008.1.2.4.57 Lossless JPEG (NonHier Process 15) 1.2.840.10008.1.2.4.58 Extended JPEG (Hier, Process 16, 18) 1.2.840.10008.1.2.4.59 Extended JPEG (Hier, Process 17, 19) 1.2.840.10008.1.2.4.60 Spectral JPEG (Hier, Process 20, 22) 1.2.840.10008.1.2.4.61 Spectral JPEG (Hier, Process 21, 23) 1.2.840.10008.1.2.4.62 Full JPEG (Hier, Process 24, 26) 1.2.840.10008.1.2.4.63 Full JPEG (Hier, Process 25, 27) 1.2.840.10008.1.2.4.64 Lossless JPEG (Hier, Process 28) 1.2.840.10008.1.2.4.65 Lossless JPEG (Hier, Process 29) 1.2.840.10008.1.2.4.66 Lossless JPEG (NonHier, Process 14B) 1.2.840.10008.1.2.4.70

RLE Lossless 1.2.840.10008.1.2.5

Table 2.1.2.1.2

(19)

2.1.2.4.2.1 SOP Specific Conformance for Storage SOP Class

“ONIS DICOM Client” Provides standard conformance to the DICOM Storage Service Class.

2.1.3 Association Acceptance Policy

“ONIS DICOM Client” accepts associations initiated by a remote AE under the following conditions:

- Association for Verification SOP Class is accepted, if SCU is defined in user defined list (see paragraph 5.2).

- Association for Storage SOP Classes is accepted, if SCU is defined in user defined list (see paragraph 5.2).

2.1.3.1 Verification requested by a remote AE

Associated Real-World Activity is the verification of the DICOM communications. When

“ONIS DICOM Client” receives a C-ECHO-RQ message, it returns a C-ECHO-RSP message to the SCU.

2.1.3.1.2 Accepted Presentation Context Table

Name UID Name UID

Verification 1.2.840.10008.1.

1

1.2.840.10008.1.2

1.2.840.10008.1.2.1

(20)

Explicit VR Big Endian 1.2.840.10008.1.2.2

Table 2.1.3.1.2

The User Role is SCP and Extended Negotiation is not available.

2.1.3.1.2.1 SOP Specific Conformance for Verification SOP Class

“ONIS DICOM Client” provides standard conformance to the DICOM Verification Service Class.

2.1.3.1.3 Presentation Context Acceptance Criterion

Any of the Presentation Contexts shown in Table 2.1.3.1.2 are acceptable for “ONIS DICOM Client”.

2.1.3.1.4 Transfer Syntax Selection Policies

“ONIS DICOM Client” will use the first transfer syntax proposed by the remote AE in the presentation context.

2.1.3.2 Query Requested by a remote AE

2.1.3.2.1 Associated Real-World Activity

The associated Real-World activity with the Query/Retrieve FIND Service is to find and provide patient, study and/or series and image information requested by a DICOM

(21)

Query/Retrieve SCU. ONIS Remote Client does not support any Query/Retrieve FIND service from a Remote AE.

2.1.3.3 Move Requested by a remote AE

The associated Real-World Activity with the Query/Retrieve MOVE Service is to transfer images to a destination AE as requested by a DICOM Query/Retrieve MOVE SCU. “ONIS DICOM Client” does not support Query/Retrieve MOVE Service from a remote AE.

2.1.3.4 Get Requested by a remote AE

The associated Real-World Activity with the Query/Retrieve GET Service is to transfer images to the SCU which has requested the GET SOP Service Class. “ONIS DICOM Client” does not support Query/Retrieve GET Service from a remote AE.

2.1.3.4 Storage requested by a remote AE

The associated Real-World Activity with the Storage Service is the storage of image data on a local hard disk. Images are retained in DICOM Part 10 compliant file format, until user intentionally deletes them. “ONIS DICOM Server” is Level 2 SCP for all Storage SOP Classes.

(22)

2.1.3.4.2 Accepted Presentation Context Table

SOP Class Name

SOP Class UID Name UID

CR Image Storage 1.2.840.10008.5.1.4.1.1.1 CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Ultrasound

Multi-frame Image Storage Retired

1.2.840.10008.5.1.4.1.1.3

Ultrasound Multi-frame Image Storage

1.2.840.10008.5.1.4.1.1.3.1

MR Image Storage 1.2.840.10008.5.1.4.1.1.4 Nuclear Medicine

Image Storage Retired

1.2.840.10008.5.1.4.1.1.5

Ultrasound Image Storage Retired

1.2.840.10008.5.1.4.1.1.6

Ultrasound Image Storage

1.2.840.10008.5.1.4.1.1.6.1

Secondary Capture Image Storage

1.2.840.10008.5.1.4.1.1.7

X-Ray

Angiographic Image Storage

1.2.840.10008.5.1.4.1.1.12.1

X-Ray

Radiofluoroscopic Image Storage

1.2.840.10008.5.1.4.1.1.12.2

Nuclear Medicine Image Storage

1.2.840.10008.5.1.4.1.1.20

All Transfer Syntax Specified in the Table 2.1.2.1.2

(23)

Positron Emission Tomography Image Storage

1.2.840.10008.5.1.4.1.1.128

Radiotherapy Image Storage

1.2.840.10008.5.1.4.1.1.481.1

VL Endoscopic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.1

VL Microscopic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.2

VL

Slide-Coordinates Microscopic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.3

VL Photographic Image Storage

1.2.840.10008.5.1.4.1.1.77.1.4

Digital X-Ray Image Storage- For Presentation

1.2.840.10008.5.1.4.1.1.1.1

Digital X-Ray Image Storage- For Processing

1.2.840.10008.5.1.4.1.1.1.1.1

Digital

Mammography Image Storage- For Presentation

1.2.840.10008.5.1.4.1.1.1.2

Digital

Mammography Image Storage- For Processing

1.2.840.10008.5.1.4.1.1.1.2.1

Digital Intra-oral X-Ray Image-For Presentation

1.2.840.10008.5.1.4.1.1.1.3

Digital Intra-oral X-Ray Image-For Processing

1.2.840.10008.5.1.4.1.1.1.3.1

(24)

Table 2.1.3.5.2

2.1.3.4.2.1 SOP Specific Conformance for Storage SOP Class

“ONIS DICOM Client” provides standard conformance to the DICOM Storage Service Class.

2.1.3.4.3 Presentation Context Acceptance Criterion

Any of the Presentation Contexts shown in Table 2.1.3.5.2 are acceptable for “ONIS DICOM Client”.

2.1.3.4.4 Transfer Syntax Selection Policies

“ONIS DICOM Client” will use the first transfer syntax proposed by the remote AE in the presentation context. If the first transfer syntax is not available, then it will use the second one and so on. The remote AE must support at least Implicit VR Little Endian.

3 Communication Profiles

3.1 Supported Communication Stacks

“ONIS DICOM Client” provides DICOM V3.0 TCP/IP Network Communication Support as defined in PS 3.8

3.2 TCP/IP Stacks

3.2.1 Physical Media Support

(25)

“ONIS DICOM Client” is indifferent to the physical medium over which TCP/IP excutes.

The recommended medium is 1000Base-T Ethernet.

4 Extensions / Specializations / Privatizations

Not Applicable.

5 Configuration

5.1 AE Title / Presentation Address Mapping

See paragraph 5.2 for Local AE Title and Port ID Settings. Local IP Address is configured through Windows users interface.

5.2 Configurable Parameters

The following parameters of the “ONIS DICOM Client” are configurable through the preference panel of ONIS 2.0:

- Application Entity Title of the “ONIS DICOM Server”

- Listening port number

- Maximum number of clients which can be connected at same time - Time out settings (Idle, Connection, Move and Store)

- CSTORE Overwrite behavior

- Security flags (check of called and calling AE and/or IP Addresses)

After modifying any of the above settings, the “ONIS DICOM Client” needs to be restarted in order for the changes to take effect.

(26)

Through the clients page of the preference panel of ONIS 2.0, the definition of the AE Applications which can connect to “ONIS DICOM Client” can be defined. The following parameters can be defined for each AE Application:

- Application Entity Title - IP Address

- Port Number (when this AE Application will be used as an SCP) - Rights (Find, Get, Move and Store rights)

6 Support for Extended Characters Sets

For Japanese Language only:

“ONIS DICOM Client” supports Japanese Character sets, ISO 2022 IR 13, ISO 2022 IR 14 and ISO 2022 IR 87, as extended character sets for all SOP classes and both SCU and SCP roles.

ONIS 2.0 DICOM CLIENT. DICOM 3 Conformance statement