vitrea vlc image workstation

8/18/2019 Vitrea Vlc Image Workstation

1/19

Vital Images

Vitrea

DICOM 3.0 Conformance Statement

VLC-5412

COPYRIGHT © 1997-99 VITAL IMAGES, INC.

ALL RIGHTS RESERVED


2/19

VitreaVLC 5412C DICOM Conformance Statement

Page 2 of 19

Revision History

REVISION EFF DATE AUTHORS CHANGES FROM PREVIOUS REVISION

A 7/31/1998 Greg Poole

Mark Rainbow

Initial issue.

B 3/8/99 Todd Johnson Changed Vitrea to use the Study Root Query/Retrieve model

(formerly Patient Root).

Added information on the Study Date query key.

Updated the version to Vitrea 1.2.

C 11/24/99 Todd Johnson Updated for Vitrea 2.

- Added new keys to Query model.

- Removed C-Get references.


3/19


Page 3 of 19

Table of Contents

1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

1.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.2 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

1.3 High Level Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.4 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

2.0 Implementation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

2.1 Application Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

2.2 Functional Definition of AE’s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.3 Sequencing of Real-World Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

3.0 AE Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

3.1 Vitrea AE Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

3.1.1 Association Establishment Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

3.1.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.1.1.2 Number of Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93.1.1.3 Implementation Identifying Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.1.2 Association Initiation by Real-World Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

3.1.2.1 Real-World Activities - A, B, C, D, E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

3.1.2.1.1 Associated Real-World Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

3.1.2.1.2 Proposed Presentation Contexts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

3.1.2.1.2.1 SOP Specific Conformance to Query/Retrieve Service Class - FIND . . . . . . . . . . . . . . . . .11

3.1.2.1.2.2 SOP Specific Conformance to Query/Retrieve Service Class - MOVE . . . . . . . . . . . . . . .12

3.1.2.1.2.3 SOP Specific Conformance to Storage Service Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

3.1.3 Association Acceptance Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

3.1.3.1 Real-World Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .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 to Verification Service Class . . . . . . . . . . . . . . . . . . . . . . . . . .133.1.3.1.2.2 SOP Specific Conformance to Query/Retrieve Service Class . . . . . . . . . . . . . . . . . . . . . . .13

3.1.3.1.2.3 SOP Specific conformance to Storage Service Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

3.1.3.1.3 Presentation Context Acceptance Criterion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

3.1.3.1.4 Transfer Syntax Selection Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

3.2 PrintQueue AE Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

3.2.1 Association Establishment Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

3.2.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2.1.2 Number of Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

3.2.1.3 Implementation Identifying Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2.2 Association Initiation by Real-World Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

3.2.2.1 Real-World Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

3.2.2.1.1 Associated Real-World Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2.2.1.2 Presentation Context Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

3.2.2.1.2.1 SOP Specific Conformance to Basic Grayscale

Print Management Meta SOP Service Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

3.2.2.1.2.1.1 Basic Film Session SOP Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

3.2.2.1.2.1.2 Basic Film Box SOP Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

3.2.2.1.2.1.3 Basic Grayscale Image Box SOP Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

3.2.2.1.2.1.4 Printer SOP Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

3.2.2.1.2.2 SOP Specific Conformance to Basic Color

Print Management Meta SOP Service Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18


4/19


Page 4 of 19

3.2.2.1.2.2.1 Basic Film Session SOP Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

3.2.2.1.2.2.2 Basic Film Box SOP Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

3.2.2.1.2.2.3 Basic Color Image Box SOP Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

3.2.2.1.2.2.4 Printer SOP Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

3.2.3 Association Acceptance Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

4.0 Communication Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.1 Supported Communication Stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

4.2 TCP/IP Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.3 Physical Media Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

5.0 Extensions/Specializations/Privatizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

6.0 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

6.1 AE Title/Presentation Address Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

6.2 Configurable Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

7.0 Support of Extended Character Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20


5/19


Page 5 of 19

1.0 Introduction

This Conformance Statement specifies the compliance of Vital Images Vitrea product line to the DICOM v3.0 standard.

As described in the DICOM Standard PS 3.2 (Conformance), the purpose of this document is to outline the level of con-

formance to the DICOM standard and to enumerate the supported DICOM Service Classes, Information Objects, and Com-

munications Protocols supported by this implementation

1.1 Definitions

Volume - A three dimensional object created by stacking a series of images, one on top of the other.

The images are usually placed in the same order as they were acquired from the scanning device

such as an MR or CT scanner. A volume can exist either in computer memory or be stored on disk

as a volume file.

Vitrea workstation - The combination of Vital Images medical imaging software Vitrea and host

computer.

1.2 Abbreviations

AE - DICOM Application EntityASCII - American Standard Code for Information Interchange

CT - Computed Tomography

DICOM - Diagnostic Imaging and Communications In Medicine

DIMSE - DICOM Message Service Element

DIMSE-C - DICOM Message Service Element-Composite

DIMSE-N - DICOM Message Service Element-Normalized

HTML - HyperText Markup Language

IOD - DICOM Information Object Definition

MR - Magnetic Resonance

PDU - DICOM Protocol Data Unit

SC - Secondary Capture

SCP - DICOM Service Class Provider

SCU - DICOM Service Class User

SOP - Service / Object Pair

TCP/IP - Transmission Control Protocol / Internet Protocol

UID - Unique Identifier

UIF - User InterFace

1.3 High Level DescriptionThe Vitrea workstation is Vital Images’ diagnostic visualization product for routine clinical

radiology and surgical planning, which provides interactive 2-D and 3-D viewing of CT and MR

images.

A unique feature, critical to the Vitrea workstation’s speed and ease of use, is the ability to provide

automated 2-D and 3-D renderings of scanner data, optimized for individual clinical applications.

All visualizations parameters are pre-set for the specific type of clinical exam. This approach


6/19


Page 6 of 19

bypasses the time-consuming approaches inherent in other 3-D rendering techniques. The clinical

applications include assessment of the Circle of Willis, colon, spine, lungs and coronary arteries.

1.4 References

• Digital Imaging and Communications in Medicine (DICOM), NEMA Standards PublicationsPS 3.1 - 3.13.

• Vitrea Configuration Files, Vital Images, Inc., VLC-5040.

2.0 Implementation Model

2.1 Application Data Flow Diagram

Figure 1 depicts the Application Data Flow Diagram. This diagram illustrates the relationships

between the Application Entities (AE’s) and the Real-World Activities.


7/19


Page 7 of 19

Figure 1. Vitrea Application Data Flow Diagram

2.2 Functional Definition of AE’s

The Vitrea Application Entity is responsible for initiating associations with remote DICOM AE’s

that provide DICOM Query/Retrieve services. It will also initiate associations with remote DICOM

AE’s in order to store exported Secondary Capture images. It will act as the SCU for the C-STORE,

C-FIND, and C-MOVE DIMSE services. By definition, it will also act as the SCP for the C-

STORE DIMSE service. The application uses the Study Root Query/Retrieve model. It is also

responsible for accepting associations with remote AE’s and acting as a SCP of the C-STORE

DIMSE service when another DICOM AE establishes an association to it.

Remote

Query/Retrieve

Provider

Request Study,

Series,

Image Info(A)

Display Patient,

Study, Series,

Image Info

(B)

Retrieve

Images

(C)

Images received

and converted

into volume

(D)

Print DICOM

Images

Remote

DICOM

Push

Images

Printed

Remotely

Vitrea

Application

AE

PrintQueue

daemon

AE

DICOM Standard

Interface

Images

Stored

Remotely

(E)


8/19


Page 8 of 19

The PrintQueue Application Entity is responsible for initiating associations with remote DICOM

AE’s that provide DICOM Print Management services. It will act as the SCU of the Basic

Grayscale Print Management and Basic Color Print Management Meta SOP Classes.

These Application Entities, Vitrea and PrintQueue, taken as a group constitute the Vitrea

workstation DICOM support system.

2.3 Sequencing of Real-World Activities

Not applicable.

3.0 AE Specifications

3.1 Vitrea AE Specification

The Vitrea AE provides Standard Conformance to the following DICOM V3.0 SOP Classes as a

SCU:

The Vitrea AE provides Standard Conformance to the following DICOM V3.0 SOP Classes as a

SCP:

The PrintQueue AE provides Standard Conformance to the following DICOM V3.0 SOP Classes

as a SCU:

3.1.1 Association Establishment Policies

3.1.1.1 General

SOP Class Name SOP Class UID

Study Root Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.2.1

Study Root Query/Retrieve Information Model - MOVE 1.2.840.10008.5.1.4.1.2.2.2

SC Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.7


Verification SOP Class 1.2.840.10008.1.1

CT Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.2

MR Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.4


Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9

Basic Color Print Management Meta SOP Class 1.2.840.10008.5.1.1.18


9/19


Page 9 of 19

The Vitrea AE will initiate associations to remote DICOM AE’s in order to perform a Query/

Retrieve, and will automatically query all the remote DICOM AE’s listed in the configuration.

Vitrea will also initiate associations in order to store exported Secondary Capture images to a

remote DICOM AE. The Vitrea AE will accept associations from remote DICOM AE’s in order to

receive DICOM pushes.

The maximum PDU size is configurable, with a minimum of 4K. A typical PDU size that Vitrea

will offer is 100K. Vitrea will always propose the following DICOM Application Context Name:

3.1.1.2 Number of Associations

The Vitrea AE will initiate only one association (in the role of an SCU) at a time while performing

the query, retrieve or storage (export of secondary capture images) services. The number of

associations (in the role of an SCP) the Vitrea AE will accept is only limited by the available

resources on the workstation. The Vitrea AE will spawn a new process to handle each connection

request it receives.

3.1.1.3 Implementation Identifying Information

The Implementation Class UID and Implementation Version Name of Vitrea are:

3.1.2 Association Initiation by Real-World Activity

The Vitrea AE will initiate an association when a user selects the DICOM Servers radio button inthe Study Directory UIF panel, or when the user selects the DICOM Export push button in the

Reports UIF panel.

3.1.2.1 Real-World Activities - A, B, C, D, E

3.1.2.1.1 Associated Real-World Activities

The Real-World Activity (A) is associated with the C-FIND operation. The user selects the DICOM

Servers radio button in the Study Directory UIF which causes the Vitrea AE to perform a study

query of all configured Remote Query/Retrieve Provider DICOM AE’s.

The result of Real-World Activity (A) is the Real-World Activity (B), which is the display of study

information in the UIF on the local workstation. If the user further selects a study from the UIF,

another C-FIND, Real-World Activity (A), is performed for each series for each study, and each

image for each series in order to populate the UIF with relevant information.

The Real-World Activity (C) is associated with the C-MOVE operation. Selecting an image series

in the UIF causes a C-MOVE request to be sent to the Remote Query/Retrieve Provider for single

preview image to be sent back to the Vitrea AE. Selecting the Retrieve Series button or double

DICOM 3.0 Application Context Name 1.2.840.10008.3.1.1.1

Implementation Class UID 1.2.840.113747

Implementation Version Name VI_DICOM_1.2


10/19


Page 10 of 19

clicking on a series in the UIF causes a C-MOVE request to be sent to the Remote Query/Retrieve

Provider for the selected range of images from the series

The Real-World Activity (D) is associated with a C-STORE SCP operation, and is triggered by

either the Real-World Activity (C) or a Remote DICOM Push. This results in the storage of thereceived images on the local workstation as DICOM part 10 files and their conversion into a 3-D

volume file for display on the local workstation. Vitrea will issue a failure status if it is unable to

store the images on the disk or convert them into the resulting volume file and log these errors into

an error log.

The Real-World Activity (E) is associated with a C-STORE SCU operation and is triggered by the

user selecting the ‘DICOM Export’ button on the Reports panel of the Vitrea UIF. This results in a

dialog list being presented to the user allowing the selection of a remote DICOM server. Dismissing

the dialog by pressing Cancel aborts the operation and the user returns to the Reports panel. Select-

ing a server and pressing OK initiates a storage operation with the selected remote DICOM server.

Each image in the report is exported as a DICOM part 10 file and stored as a Secondary Capture

IOD on the remote server. Any errors are reported to the user via an error dialog and also logged tothe error log file.

3.1.2.1.2 Proposed Presentation Contexts

3.1.2.1.2.1 SOP Specific Conformance to Query/Retrieve Service Class - FIND

Vitrea conforms to the C-FIND DIMSE service using the Study Root SOP Class Group.

When using the C-FIND DIMSE service, Vitrea will supply a unique key attribute for each level

above the current Query/Retrieve level. Relational search queries and SOP Class Extended negotia-

tions are not supported.

Presentation Context Table - Proposed

Abstract Syntax Transfer SyntaxRole

Extended

NegotiationName UID Name UID

Study Root

FIND

1.2.840.10008.5.1.4.1.2.1.1 DICOM Implicit VR

Little Endian

1.2.840.10008.1.2 SCU None

Study Root

MOVE

1.2.840.10008.5.1.4.1.2.2.2 DICOM Implicit VR

Little Endian

1.2.840.10008.1.2 SCU None

CT Image 1.2.840.10008.5.1.4.1.1.2 DICOM Implicit VR

Little Endian

1.2.840.10008.1.2 SCP None

MR Image 1.2.840.10008.5.1.4.1.1.4 DICOM Implicit VR

Little Endian

1.2.840.10008.1.2 SCP None

SC Image 1.2.840.10008.5.1.4.1.1.7 DICOM Implicit VR

Little Endian

1.2.840.10008.1.2 SCU None


11/19


Page 11 of 19

When the user selects the DICOM Servers radio button in the Real-World Activity (A), the initial

study level query request is done using user-supplied values obtained via a dialog in the UIF. The

user is allowed to modify the “Patient Name”, “Patient ID”, “Modality” and “Study Date Range”

fields in order to limit the query as the user desires. The default values preloaded into the dialog

and the matching types used by Vitrea are shown in the following table:

*All other required query fields use Universal Matching.

One additional query field in the query dialog, “DICOM Servers:” is not used as a query key for

any DICOM query. It’s value is only used internally to limit the DICOM search.

The following table enumerates the DICOM tags which may be used as keys to uniquely indentify

a set of data during Vitrea’s query activity:

The following table enumerates the DICOM tags that Vitrea extracts data from during query in

order to populate the UIF for the Study Directory panel:

Query

AttributeDefault Value

Matching

Type

Patient Name zero length Universal,

Wild Card or

Single Value

Patient ID zero length Universal,

Wild Card or

Single Value

Modality zero length Single Value

Study Date

Range

zero length Universal or

Range

Query Level Description of Keys Used Tag

Study Study Date

Patient Name

Patient ID

(0008,0020)

(0010,0010)

(0010,0020)

Series Modality

Patient ID

StudyID

Study UID

(0008,0060)

(0010,0020)

(0020,0010)

(0020,000D)

Image Patient ID

Study UID

Series UID

(0010,0020)

(0020,000D)

(0020,000E)

Description Tag

Patient Name (0010,0010)


12/19


Page 12 of 19

3.1.2.1.2.2 SOP Specific Conformance to Query/Retrieve Service Class - MOVE

Vitrea conforms to the C-MOVE DIMSE services using the Study Root SOP Class Group.

When using the C-MOVE DIMSE services, Vitrea will supply a unique key attribute for each level

above the current Query/Retrieve level. Relational search queries and SOP Class

3.1.2.1.2.3 SOP Specific Conformance to Storage Service ClassVitrea conforms to the SOP’s of the Storage Service Class at Level 2 (Full). When a successful C-

STORE operation is completed, the image has been successfully stored on the remote DICOM AE.

When the C-STORE operation is unsuccessful, the image will not be on the remote server and a

Failed response will be returned. Detailed error messages may be found in the Vitrea error log file.

SOP Class Extended negotiation as defined in PS 3.7 Section D.3.3.5 is not supported.

3.1.3 Association Acceptance Policy

When the Vitrea AE accepts an association, it does so as a result of a C-STORE or C-MOVErequest. It may receive images transmitted on the resulting association and store them on the local

workstation in preparation for creating a 3-D volume.

3.1.3.1 Real-World Activity

3.1.3.1.1 Associated Real-World Activity

Patient ID (0010,0020)

Study ID (0020,0010)

Series Number (0020,0011)

Study UID (0020,000D)

Series UID (0020,000E)

Study Date (0008,0020)

Series Date (0008,0021)

Study Time (0008,0030)

Series Time (0008,0031)

Modality (0008,0060)

Study Description (0008,1030)

Series Description (0008,103E)

Protocol (0018,1030)

Description Tag


13/19


Page 13 of 19

The Real-World Activity associated with the C-STORE and C-MOVE operation is the storage of

the received images on the local workstation as DICOM part 10 files and their conversion into a 3-

D volume file for display on the local workstation. Vitrea will issue a failure status if it is unable to

store the images on the disk or convert them into the resulting volume file and log these error into

an error log.

3.1.3.1.2 Presentation Context Table

†Note: SCU/SCP Role Negotiation is required due to the support of the C-GET DIMSE Service

3.1.3.1.2.1 SOP Specific Conformance to Verification Service Class

Vitrea provides standard conformance to the DICOM Verification Service Class.

3.1.3.1.2.2 SOP Specific Conformance to Query/Retrieve Service Class

Vitrea conforms to the C-FIND, and C-MOVE DIMSE services using the Study Root SOP Class

Group.

When using the C-FIND or C-MOVE DIMSE service, Vitrea will supply a unique key attribute for

each level above the current Query/Retrieve level. Relational search queries and SOP Class

Extended negotiations are not supported

3.1.3.1.2.3 SOP Specific conformance to Storage Service Class

Vitrea conforms to the SOP’s of the Storage Service Class at Level 2 (Full). When a successful C-

STORE operation is completed, the image has been successfully stored in a local temporary direc-

tory as a DICOM part 10 file in the format specified by PS 3.10.

When the C-STORE operation is unsuccessful, the image will not be in the local patient/study data-

base and a Failed response will be returned. Detailed error messages may be found in the Vitrea

error log file.

SOP Class Extended negotiation as defined in PS 3.7 Section D.3.3.5 is not supported.

3.1.3.1.3 Presentation Context Acceptance Criterion

Presentation Context Table - Accepted


Extended


Verification 1.2.840.10008.1.1 DICOM Implicit VR

Little Endian

1.2.840.10008.1.2 SCP None

CT Image 1.2.840.10008.5.1.4.1.1.2 DICOM Implicit VR

Little Endian

1.2.840.10008.1.2 SCP,

SCU See Note

†

MR Image 1.2.840.10008.5.1.4.1.1.4 DICOM Implicit VR

Little Endian

1.2.840.10008.1.2 SCP,

SCUSee Note

†


14/19


Page 14 of 19

The Vitrea AE does not enforce a limit on the number of presentation contexts in an association.

These presentation contexts are specified in Table 2.2.

3.1.3.1.4 Transfer Syntax Selection Policies

The Vitrea AE only supports the Default DICOM Transfer Syntax (DICOM Implicit VR LittleEndian).

3.2 PrintQueue AE Specification

The PrintQueue AE provides Standard Conformance to the following DICOM V3.0 SOP Classes

as a SCU:

3.2.1 Association Establishment Policies

3.2.1.1 General

The PrintQueue AE will initiate associations to remote DICOM AE’s in order to print images.

The maximum PDU size is configurable, with a minimum of 4K. A typical PDU size that

PrintQueue will offer is 100K. PrintQueue will always propose the following DICOM Application

Context Name:

3.2.1.2 Number of Associations

The PrintQueue AE will initiate only one association at a time.

3.2.1.3 Implementation Identifying Information

The Implementation Class UID and Implementation Version Name of PrintQueue are:


Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9

Basic Color Print Management Meta SOP Class 1.2.840.10008.5.1.1.18

Basic Film Session SOP 1.2.840.10008.5.1.1.1

Basic Film Box SOP 1.2.840.10008.5.1.1.2

Basic Grayscale Image Box SOP 1.2.840.10008.5.1.1.4

Basic Color Image Box SOP 1.2.840.10008.5.1.1.4.1

Printer SOP 1.2.840.10008.5.1.1.16

DICOM 3.0 Application Context Name 1.2.840.10008.3.1.1.1

Implementation Class UID 1.2.840.113747

Implementation Version Name VI_DICOM_1.2


15/19


Page 15 of 19

3.2.2 Association Initiation by Real-World Activity

When the PrintQueue AE initiates an association, it does so as a result of a print request by the

Vitrea workstation.

3.2.2.1 Real-World Activity

3.2.2.1.1 Associated Real-World Activity

The Real-World Activity associated with the DICOM print operation is the user pressing the

DICOM Print button in the Vitrea workstation report panel. There are two separate presentation

context tables below to signify that the Basic Grayscale and Basic Color Print Management Meta

SOP classes are not proposed together at the time of association negotiation. The choice as to which

presentation context is proposed is determined by a configuration parameter in the Vitrea prefer-

ences file.

3.2.2.1.2 Presentation Context Table

3.2.2.1.2.1 SOP Specific Conformance to Basic Grayscale Print Management Meta SOP Service Class

PrintQueue provides standard conformance to the Basic Grayscale Print Management Meta SOP

Class. The Meta SOP Class is defined by the following set of supported SOP Classes:

Basic Film Session SOP Class

Basic Film Box SOP Class

Basic Grayscale Image Box SOP Class

Presentation Context Table A - Proposed


Extended


Basic

Grayscale

Print

Management

Meta SOP

1.2.840.10008.5.1.1.9 DICOM Implicit VR

Little Endian

1.2.840.10008.1.2 SCU None

Presentation Context Table B - Proposed


Extended


Basic Color

Print

Management

Meta SOP

1.2.840.10008.5.1.1.18 DICOM Implicit VR

Little Endian

1.2.840.10008.1.2 SCU None


16/19


Page 16 of 19

Printer SOP Class

Note that some attributes in the following tables may have a default value of the empty string. The

contents of these attributes are set by entering appropriate values into the Vitrea DICOM printer

configuration file. This file is provided to allow flexibility in configuring these attributes for themany available DICOM printers. The values are passed exactly as entered to the DICOM printer. If

a value is specified in PS 3.3 as being an enumerated value, an error is generated if the value

entered does not match one of the values specified for that attribute. If a value is specified in PS 3.3

as being a defined term, it is not considered an error if the entered value does not match any of the

defined terms, and a warning is written into the error log file.

3.2.2.1.2.1.1 Basic Film Session SOP Class

The following DIMSE services are supported:

N-CREATE is sent to the SCP to cause a Basic Film Session SOP instance to be created.

The following film session attributes are supported:

3.2.2.1.2.1.2 Basic Film Box SOP Class


N-CREATE is sent to the SCP to cause a Basic Film Box SOP instance to be created.

N-ACTION is sent to the SCP to initiate printing of the film box.

N-DELETE is sent to the SCP to delete the Basic Film Box SOP instance.

The following film box attributes are supported:

Attribute Tag Attribute Name Valid Range Default Value

(2000,0010) Number of Copies 1-99 1

(2000,0020) Print Priority HIGH, MED, LOW LOW

(2000,0030) Medium Type PAPER, CLEAR FILM, BLUE FILM None, whatever value is

present in the DICOM printer

configuration file.

(2000,0040) Film Destination MAGAZINE, PROCESSOR, BIN_i

where “i” represents a sorter bin where

exposed film is deposited

None, whatever value is


configuration file.

(2000,0050) Film Session Label Any string Empty string

(2000,0060) Memory Allocation Any string Empty string

Attribute Tag Attribute Name Valid Range Default Value


17/19


Page 17 of 19

3.2.2.1.2.1.3 Basic Grayscale Image Box SOP Class

The following DIMSE services are supported: N-SET is sent to the SCP to set the attributes for the grayscale image to be associated with that

image box.

3.2.2.1.2.1.4 Printer SOP Class


N-GET is sent to the SCP to request a Printer SOP instance be returned for printer status.

(2010,0010) Image Display Format The following predefined formats are

available based on the selected film

layout button in the Vitrea report UIF:

STANDARD\1,1

STANDARD\2,2

STANDARD\3,3

STANDARD\3,4 is generated if the

12-image layout button is selected and

the Film Orientation is Portrait.

STANDARD\4,3 is generated if the

12-image layout button is selected and

the Film Orientation is Landscape.

None, dynamically generated.

(2010,0040) Film Orientation PORTRAIT, LANDSCAPE PORTRAIT

(2010,0050) Film Size ID 8INX10IN 10INX12IN

10INX14IN 11INX14IN14INX14IN 14INX17IN

24CMX24CM 24CMX30CM


present in the DICOM printerconfiguration file.

(2010,0060) Magnification Type REPLICATE, BILINEAR, CUBIC,

NONE



configuration file.

(2010,0080) Smoothing Type Any string None, whatever value is


configuration file.

(2010,0100) Border Density BLACK, WHITE, i, where “i” repre-

sents the desired density in hundredths

of OD.



configuration file.

(2010,0110) Empty Image Density BLACK, WHITE, i, where “i” repre-

sents the desired density in hundredths

of OD.



configuration file.

(2010,0120) Minimum Density Positive integer values 0

(2010,0130) Maximum Density Positive integer values 0

(2010,0140) Trim YES, NO NO

(2010,0150) Configuration Information Any string Empty string


18/19


Page 18 of 19

N-EVENT-REPORT is received asynchronously by Vitrea from the SCP. Vitrea decodes the mes-

sage and writes the information in the error log file.

3.2.2.1.2.2 SOP Specific Conformance to Basic Color Print Management Meta SOP Service Class

PrintQueue provides standard conformance to the Basic Color Print Management Meta SOP Class.The Meta SOP Class is defined by the following set of supported SOP Classes:

Basic Film Session SOP Class

Basic Film Box SOP Class

Basic Color Image Box SOP Class

Printer SOP Class

3.2.2.1.2.2.1 Basic Film Session SOP Class

Refer to the Basic Film Session SOP Class for Basic Grayscale Print Management.

3.2.2.1.2.2.2 Basic Film Box SOP Class

Refer to the Basic Film Box SOP Class for Basic Grayscale Print Management.

3.2.2.1.2.2.3 Basic Color Image Box SOP Class


N-SET is sent to the SCP to set the attributes for the color image to be associated with that image

box.

3.2.2.1.2.2.4 Printer SOP Class

Refer to the Printer SOP Class for Basic Grayscale Print Management.

3.2.3 Association Acceptance Policy

The PrintQueue AE never accepts associations.

4.0 Communication Profiles

4.1 Supported Communication Stacks

Vitrea provides DICOM V3.0 TCP/IP Network Communication Support as defined in PS 3.8.

4.2 TCP/IP Stack

Vitrea inherits its TCP/IP stack from the operating system upon which it executes. The Berkeley

Sockets API is used to access the TCP/IP stack.

4.3 Physical Media Support

Vitrea is indifferent to the physical medium over which TCP/IP executes; it inherits this from the

operating system upon which it executes.


19/19


5.0 Extensions/Specializations/Privatizations

Not applicable.

6.0 Configuration

Vitrea is very configurable. It obtains its DICOM configuration information from ASCII text files whose names and loca-

tions are specified via the Vitrea preferences file. There is a DICOM configuration file for the Vitrea application and the

cstore daemon, and a separate configuration file for the PrintQueue daemon. Each AE uses its respective configuration file

to obtain both internal configuration and mapping from AE Title to Presentation Address.

6.1 AE Title/Presentation Address Mapping

The DICOM configuration file has sections that provide a mapping of an AE title to a Presentation

Address. A Presentation Address consists of a host name and TCP/IP port number.

The Vitrea, cstore and PrintQueue AE’s, using their respective configuration file, get their local AE

titles from the local_application_entity section of the file, their host name is the name of the

machine in the /etc/hosts file, and their TCP/IP port number from the network section.

The Vitrea and PrintQueue AE’s use the remote_application_entity section of their respective

configuration file to obtain the AE title, host name and TCP/IP port number to establish

associations with remote Application Entities.

6.2 Configurable Parameters

• PDU size

• TCP/IP port number

• AE title of Vitrea, cstore daemon, PrintQueue daemon

• AE titles which are allowed to connect to Vitrea and push images

• AE titles which are available to Vitrea for Query/Retrieve and export

For more detailed information on the DICOM configuration parameters available for Vitrea, see

document VLC-5040, Vitrea Configuration Files, or your Vitrea system administrator.

7.0 Support of Extended Character Sets

Vitrea does not support extended character sets.

vitrea vlc image workstation

Documents