DICOM 3.0 Conformance Statement for InSight Receiver

Version 1.0

January 1998

Copyright Neo Imagery Technologies, Inc.

TABLE OF CONTENTS

1 Introduction *

1.1 Purpose *

1.2 Related Documents *

1.3 Symbols and Abbreviations *

2 Implementation Model *

2.1 Application Data Flow Diagram *

2.2 Functional Definitions of Application Entities *

2.3 Sequencing of Real-World Activities *

3 Application Entity Specifications *

3.1 InSight Receiver Specification *

3.1.1 Association Establishment Policies *

3.1.1.1 General *

3.1.1.2 Number of Associations *

3.1.1.3 Asynchronous Nature *

3.1.1.4 Implementation Identifying Information *

3.1.2 Association Initiation by Real-World Activity *

3.1.3 Association Acceptance Policy *

3.1.3.1 Real World Activity *

3.1.3.1.1 Associated Real-World Activity *

3.1.3.1.2 Proposed Presentation Contexts *

3.1.3.1.2.1 SOP Specific Conformance for C-ECHO *

3.1.3.1.2.2 SOP specific Conformance for C-STORE *

4 Communication Profiles *

4.1 Supported Communication Stacks *

4.2 TCP/IP Stack *

4.2.1 Physical Media Support *

5 Extensions *

5.1 Standard Extended/Specialized Private SOPs *

6 Configuration *

6.1 Configurable Parameters *

6.1.1 Port Configuration Parameters *

6.1.2 Files Configuration Parameters *

1 Introduction

1.1 Purpose

InSight Diagnostics Workstation is a Pentium/Windows NT based medical 3D diagnostics workstation. This conformance statement details the InSight Receiver compliance to DICOM 3.0. It covers all DICOM Service Class roles supported by InSight Receiver:

• Verification Service Class Role

• Storage Service Class Role

1.2 Related Documents

NEMA PS3.1-16 (1996), the DICOM Standard

1.3 Symbols and Abbreviations

ACR American College of Radiology

AE Application Entity

DICOM Digital Imaging and Communications in Medicine

IOD Information Object Definition

NEMA National Electrical Manufacturers Association

PDU Protocol Data Unit

SCP Service Class Provider

SCU Service Class User

SOP Service Object Pair

TCP/IP Transmission Control Protocol/Internet Protocol

UID Unique Identifier

2. Implementation Model

InSight Receiver acts as a local DICOM AE to accept or reject associations from Remote Application Entities and stores Information Objects in files on the local storage devices.

2.1 Application Data Flow Diagram

The following Application Data flow Diagram depicts the flow of data from remote AE via local AE to files on the local storage.

The following diagram depicts the association process between remote AE and local AE.

A remote AE can verify that InSight Receiver is running at local site by initiating a Verification request. In Verification process, association parameters are used in the determination of accepting or denying association request. If accepted, InSight Receiver replies to the remote AE that it is capable of accepting association.

A remote AE can send images to InSight Receiver, acting as a local AE, for storage purpose. To start the storage process, an association request is sent to the local AE. The local AE can either accept or deny this association request based on the association parameters communicated in the association request. If accepted, information regarding local AE’s capabilities is communicated back. At this point, the agreed upon transaction is started. The Real-World activity is that the remote AE then stores files to the local AE within the specifications set forth by InSight Receiver.

2.2 Functional Definitions of Application Entities

InSight Receiver will act as a SCP for both the Storage Service Class and the Verification Service Class. After the Workstation is logged in, the InSight Receiver is left running whether the InSight software is operational or not.

InSight Receiver receives images from remote AEs and stores them on the local drives. All images transmitted with the C-STORE Service Class will be stored with all private data elements in entirety to a user-defined location. All files will be stored with meta-header information as defined in Part 10 of the DICOM 3.0 standard.

InSight Receiver will respond to all verification requests using the C-ECHO Service Class.

2.3 Sequencing of Real-World Activities

The InSight Receiver DICOM AE waits for association requests on a user specified TCP/IP port.

3 Application Entity Specifications

This section contains the specifications of InSight Receiver DICOM Application Entity acting as a Storage Service Class Provider and a Verification Service Class Provider.

3.1 InSight Receiver Specification

The InSight Receiver AE provides Standard Conformance to the following DICOM 3.0 SOP Classes as an SCP:

3.1.1 Association Establishment Policies

3.1.1.1 General

The InSight Receiver will establish association to all DICOM requests whose abstract Syntax and Transfer Syntax are determined valid.

The DICOM Application Context Name (ACN) which is always proposed is:

Protocol Data Unit (PDU) defines the data segment that two AEs used for communication. The Maximum Length PDU is negotiated at all association establishment time.

The Maximum Length PDU for InSight Receiver is:

3.1.1.2 Number of Associations

InSight Receiver can accept multiple associations concurrently, and is only limited by Windows NT operating system and TCP/IP stack on which it is running.

The number of concurrent associations is configurable on Windows NT 4.0 Server Edition.

3.1.1.3 Asynchronous Nature

InSight Receiver does not support asynchronous operations window negotiation. All operations are performed synchronously.

3.1.1.4 Implementation Identifying Information

3.1.2 Association Initiation by Real-World Activity

InSight Receiver does not initiate associations.

3.1.3 Association Acceptance Policy

3.1.3.1 Real World Activity

This section details the action of InSight Receiver as a result of association establishment.

3.1.3.1.1 Associated Real-World Activity

When an association request is detected, the association is first checked for validity and verification of the remote AE’s ability to initiate an association with InSight Receiver. The sequence of actions is:

• InSight Receiver checks the remote AE’s association for the validity of the DICOM Application Context Name against the standard set forth in the DICOM 3.0 standard. If the UID 1.2.840.10008.3.1.1.1 of the DICOM Application Context Name is not present or different, the association will be rejected.

• The AE Title of InSight Receiver is "INSIGHT" in all capital letters.

• The InSight Receiver will accept all association requests regardless of calling AE Titles and called AE Titles.

When an association is accepted, the Real-World activity of InSight Receiver will depend on the requested Service Class, either Verification or Storage. For Verification Service Class request, the Real-World activity of InSight Receiver will be the construction of affirmative response to calling AE indicating that InSight Receiver is running and can accept future association. For Storage Service Class request, the Real-World activity of InSight Receiver will be storing a file or multiple files to a local drive.

3.1.3.1.2 Proposed Presentation Contexts

InSight Receiver accepts the following Presentation Contexts:

3.1.3.1.2.1 SOP Specific Conformance for C-ECHO

InSight Receiver provides standard conformance to the DICOM Verification Service Class.

3.1.3.1.2.2 SOP specific Conformance for C-STORE

InSight Receiver can perform multiple C-STORE operations over a single association. No elements are dropped or coerced.

Upon receiving a successful status on C-STORE confirmation, InSight Receiver will perform the next C-STORE operation. The association will be maintained through out this process.

If a C-STORE operation cannot be completed successfully, a C-STORE confirmation will contain an Error, Refused, or Warning status. InSight Receiver will then fail the specific IOD in question. If more images are left to be sent, then they will be sent in the same association.

4 Communication Profiles

4.1 Supported Communication Stacks

InSight Receiver supports DICOM Upper Layer as defined in Part 8 of the Standard using TCP/IP Network.

4.2 TCP/IP Stack

InSight Receiver inherits TCP/IP stack from the host (Windows NT).

4.2.1 Physical Media Support

InSight Receiver is indifferent to any Windows NT supported physical media.

5 Extensions

5.1 Standard Extended/Specialized Private SOPs

Not applicable.

6 Configuration

6.1 Configurable Parameters

Two parameters of InSight Receiver are configurable: Port and Image Root Directory.

6.1.1 Port Configuration Parameters

Any valid TCP port can be configured for DICOM association acceptance. The total number of concurrent connections is only limited by the Windows NT operating system. The default port number is 104. InSight Receiver will accept all calling or called AE Titles.

6.1.2 Files Configuration Parameters

User can configure the destination directory on the storage for the incoming images. The site can be on a local disk, other removable or fixed storage devices, or a network drive connected to the InSight Diagnostics Workstation.