Version 3.

0– 30 Sep 96 IMPAX Storage and Print Services Page 1 of 23

Agfa Medical Division

DICOM Conformance Statement
IMPAX Storage and Print Services

Conformance Statement
IMPAX
30 September 1996

Copyright  1997 Agfa Medical Division

All rights reserved

Page 2 of 23 IMPAX Storage and Print Services Version 3.0– 30 Sep 96

Issued by: The equipment described in this document has

been validated in accordance with the DICOM
Agfa Medical Division
standard. Agfa shall not be liable for errors
Septestraat 27 contained herein or consequential damages in
B-2640 Mortsel connection with the furnishing, performance or
Belgium use of this document. Agfa reserves the right to
Tel: +32 3 444 8230 revise this publication and to make changes to
Fax: +32 3 444 7750 its content at any time, without obligation to
email: [email protected] notify any person or entity of such revisions and
changes.

For questions regarding the technical content of this

document, please contact Peter Gielen. Copyright  1997
Tel: +32 3 444 7504 Agfa Medical Division
Fax: +32 3 444 7495 All rights reserved
Version 3.0– 30 Sep 96 IMPAX Storage and Print Services Page 3 of 23

Table of Contents

INTRODUCTION ............................................................................................................................................................ 6

1. IMPLEMENTATION MODEL ............................................................................................................................. 7

1.1. APPLICATION DATA FLOW DIAGRAM ................................................................................................................ 7
1.1.1. Receive Images ............................................................................................................................................. 7
1.1.2. Query to/from Other Devices........................................................................................................................ 7
1.1.3. Retrieve to/from Other Devices .................................................................................................................... 7
1.1.4. Transmit Images ........................................................................................................................................... 7
1.2. FUNCTIONAL DEFINITIONS OF AES .................................................................................................................... 8
1.3. SEQUENCING OF REAL WORLD ACTIVITIES ....................................................................................................... 8
2. AE SPECIFICATIONS........................................................................................................................................... 8
2.1. IMPAX SPECIFICATIONS .................................................................................................................................... 8
2.1.1. Association Establishment Policies .............................................................................................................. 9
2.1.1.1. General.................................................................................................................................................................. 9
2.1.1.2. Number of Associations...................................................................................................................................... 10
2.1.1.3. Asynchronous Nature.......................................................................................................................................... 10
2.1.1.4. Implementation Identifying Information............................................................................................................. 10
2.1.1.5. Called/Calling Titles ........................................................................................................................................... 10
2.1.2. Association Initiation by Real World Activity............................................................................................. 10
2.1.2.1. Real World Activity - Verification...................................................................................................................... 10
2.1.2.1.1. Associated Real World Activity – Verification.............................................................................................. 10
2.1.2.1.2. Presentation Context Table - Verification ...................................................................................................... 10
2.1.2.1.3. SOP Specific Conformance - Verification ..................................................................................................... 10
2.1.2.2. Real World Activity – Storage ............................................................................................................................ 11
2.1.2.2.1. Associated Real World Activity – Storage..................................................................................................... 11
2.1.2.2.2. Presentation Context Table – Storage ............................................................................................................ 11
2.1.2.2.3. SOP Specific Conformance – Storage............................................................................................................ 11
2.1.2.3. Real World Activity – Find................................................................................................................................. 11
2.1.2.3.1. Associated Real World Activity – Find.......................................................................................................... 11
2.1.2.3.2. Presentation Context Table – Find ................................................................................................................. 11
2.1.2.3.3. SOP Specific Conformance - Find ................................................................................................................. 11
2.1.2.4. Real World Activity – Move............................................................................................................................... 12
2.1.2.4.1. Associated Real World Activity – Move........................................................................................................ 12
2.1.2.4.2. Presentation Context Table – Move ............................................................................................................... 12
2.1.2.4.3. SOP Specific Conformance – Move............................................................................................................... 12
2.1.2.5. Real World Activity –Printing ............................................................................................................................ 13
2.1.2.5.1. Associated Real World Activity – Printing .................................................................................................... 13
2.1.2.5.2. Presentation Context Table – Printing............................................................................................................ 13
2.1.2.5.3. SOP Specific Conformance - Printing............................................................................................................ 13
2.1.2.5.3.1. SOP Specific Conformance to Basic Film Session SOP Class ............................................................... 13
2.1.2.5.3.2. SOP Specific Conformance to Basic Film Box SOP Class .................................................................... 13
2.1.2.5.3.3. SOP Specific Conformance to Basic Greyscale Image Box SOP Class ................................................. 14
2.1.2.5.3.4. SOP Specific Conformance to Basic Color Image Box SOP Class ........................................................ 15
2.1.2.5.3.5. SOP Specific Conformance to Referenced Image Box SOP Class......................................................... 15
2.1.2.5.3.6. SOP Specific Conformance to Printer SOP Class................................................................................... 16
2.1.3. Association Acceptance Policy ................................................................................................................... 16
2.1.3.1. Real World Activity – Verification ..................................................................................................................... 16
2.1.3.1.1. Associated Real World Activity – Verification.............................................................................................. 16
2.1.3.1.2. Presentation Context Table – Verification ..................................................................................................... 16
2.1.3.1.3. SOP Specific Conformance – Verification..................................................................................................... 16
2.1.3.1.4. Presentation Context Acceptance Criterion – Verification............................................................................. 16
2.1.3.1.5. Transfer Syntax Selection Policies - Verification .......................................................................................... 17
2.1.3.2. Real World Activity – Storage ............................................................................................................................ 17
2.1.3.2.1. Associated Real World Activity – Storage..................................................................................................... 17
2.1.3.2.2. Presentation Context Table - Storage ............................................................................................................. 17
2.1.3.2.3. SOP Specific Conformance - Storage ............................................................................................................ 17
2.1.3.2.4. Presentation Context Acceptance Criterion - Storage .................................................................................... 18
2.1.3.2.5. Transfer Syntax Selection Policies – Storage................................................................................................. 18
Page 4 of 23 IMPAX Storage and Print Services Version 3.0– 30 Sep 96

2.1.3.3. Real World Activity – Find................................................................................................................................. 18

2.1.3.3.1. Associated Real World Activity – Find.......................................................................................................... 18
2.1.3.3.2. Presentation Context Table – Find ................................................................................................................. 18
2.1.3.3.3. SOP Specific Conformance – Find ................................................................................................................ 19
2.1.3.3.4. Presentation Context Acceptance Criterion – Find ........................................................................................ 20
2.1.3.3.5. Transfer Syntax Selection Policies – Find...................................................................................................... 20
2.1.3.4. Real World Activity – Move............................................................................................................................... 20
2.1.3.4.1. Associated Real World Activity – Move........................................................................................................ 20
2.1.3.4.2. Presentation Context Table - Move................................................................................................................ 21
2.1.3.4.3. SOP Specific Conformance - Move ............................................................................................................... 21
2.1.3.4.4. Presentation Context Acceptance Criterion - Move ....................................................................................... 22
2.1.3.4.5. Transfer Syntax Selection Policies - Move .................................................................................................... 22
3. COMMUNICATIONS PROFILES ..................................................................................................................... 22
3.1. TCP/IP STACK................................................................................................................................................. 22
3.1.1. Physical Media Support.............................................................................................................................. 22
4. EXTENSIONS/SPECIALIZATIONS/PRIVATIZATIONS .............................................................................. 22

5. CONFIGURATION .............................................................................................................................................. 22

6. SUPPORT FOR EXTENDED CHARACTER SETS......................................................................................... 22

7. ACRONYMS AND ABBREVIATIONS.............................................................................................................. 23

Version 3.0– 30 Sep 96 IMPAX Storage and Print Services Page 5 of 23

Revision History

Revision Date Author Reason for Change

3.0 ? ? ?
2.11 10/2/95 Andrew Added this revision page
2.2 6/3/95 Andrew Revisions to support new DICOM Part 10-12
2.3 14/5/95 Andrew Modifications to the transfer syntaxes that are supported. Also
removed references to DICOM-PA
2.4 14/11/95 Andrew Modifications based upon latest release of software, as well as
minor corrections
3.0 30/9/96 Eric Product release. Added many new services
Page 6 of 23 IMPAX Storage and Print Services Version 3.0– 30 Sep 96

Introduction

Purpose of this Document

This document is a provisional DICOM Conformance Statement for the storage and print services of IMPAX.
IMPAX is a Service Class Provider (SCP) and Service Class User (SCU) for services relating to the
storage, retrieval and printing of images.

Sources for this Document

• American College of Radiology-National Electrical Manufacturers Association (ACR-NEMA)

Digital Imaging and Communications V2.0, 1988.

ACR-NEMA Digital Imaging and Communications in Medicine (DICOM) V3.0. 1993.

Version 3.0– 30 Sep 96 IMPAX Storage and Print Services Page 7 of 23

1. Implementation Model
IMPAX is an image database and storage facility. IMPAX is a single application entity that stores
images sent to it by service class users, allows queries based on several standard query models, and
retrieves requested images.

1.1. Application Data Flow Diagram

SCP

IMPAX
Release 3

SCU Key:
DICOM Application Entity
Standard
Interface Association Negotiation

1.1.1. Receive Images

IMPAX stores a received image in its entirety, without change, in its internal data store. IMPAX
stores each image with the File Meta Information attached to it.

IMPAX extracts the query information with respect to the patient, study, series and image, and
stores this information within its internal database.

1.1.2. Query to/from Other Devices

IMPAX responds to queries based on the records stored in its database. IMPAX issues unsolicited
queries to other compatible devices.

1.1.3. Retrieve to/from Other Devices

IMPAX responds to requests to retrieve images (C-MOVEs to the requester, or to a third party) by
obtaining a reference from the database then obtaining the image object itself from the data store.
IMPAX issues C-MOVEs to other compatible devices.

1.1.4. Transmit Images

IMPAX transmits images to other compatible devices.
Page 8 of 23 IMPAX Storage and Print Services Version 3.0– 30 Sep 96

1.2. Functional Definitions of AEs

Not applicable

1.3. Sequencing of Real World Activities

Not applicable.

2. AE Specifications

2.1. IMPAX Specifications

IMPAX provides Standard Conformance to the following DICOM V3.0 SOP Class as an SCP and
SCU.

Table 1 Verification SOP Class

SOP Class Name SOP Class UID

Verification 1.2.840.10008.1.1

Table 2 lists the SOP Classes that are supported by IMPAX for storage services. In general, IMPAX
will be extended to support all image SOP classes recognized by DICOM.

Table 2 Storage SOP Classes

SOP Class Name SOP Class UID

Computed Radiography 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 1.2.840.10008.5.1.4.1.1.3
MR Image Storage 1.2.840.10008.5.1.4.1.1.4
Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.5
Ultrasound Image Storage 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
Stand-alone Overlay Image Storage 1.2.840.10008.5.1.4.1.1.8
Stand-alone Curve Storage 1.2.840.10008.5.1.4.1.1.9
Stand-alone Modality LUT Storage 1.2.840.10008.5.1.4.1.1.10
Stand-alone VOI LUT Storage 1.2.840.10008.5.1.4.1.1.11
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
X-ray Angiographic Bi-plane Image Storage 1.2.840.10008.5.1.4.1.1.12.3
Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20
Version 3.0– 30 Sep 96 IMPAX Storage and Print Services Page 9 of 23

Table 3 Query/Retrieve SOP Classes

SOP Class Name SOP Class UID

Patient Root Query/Retrieve IM Find 1.2.840.10008.5.1.4.1.2.1.1
Patient Root Query/Retrieve IM Move 1.2.840.10008.5.1.4.1.2.1.3
Study Root Query/Retrieve IM Find 1.2.840.10008.5.1.4.1.2.2.1
Study Root Query/Retrieve IM Move 1.2.840.10008.5.1.4.1.2.2.3
Patient/Study Only Query/Retrieve IM Find 1.2.840.10008.5.1.4.1.2.3.1
Patient/Study Only Query/Retrieve IM Move 1.2.840.10008.5.1.4.1.2.3.3

Table 4 Print SOP Classes

SOP Class Name SOP Class UID

Basic Greyscale Print Management Meta 1.2.840.10008.5.1.1.9
Referenced Greyscale Print Management Meta 1.2.840.10008.5.1.1.9.1
Basic Color Print Management Meta 1.2.840.10008.5.1.1.18
Referenced Color Print Management Meta 1.2.840.10008.5.1.1.18.1
Basic Film Session 1.2.840.10008.5.1.1.1
Basic Film Box 1.2.840.10008.5.1.1.2
Basic Greyscale Image Box 1.2.840.10008.5.1.1.4
Basic Color Image Box 1.2.840.10008.5.1.1.4.1
Basic Referenced Image Box 1.2.840.10008.5.1.1.4.2
Printer 1.2.840.10008.5.1.1.16

Table 5 Default Transfer Syntaxes

Transfer Syntax UID

DICOM Implicit VR Little Endian 1.2.840.10008.1.2

Table 6 Transfer Syntaxes for Storage

Transfer Syntax UID

DICOM Implicit VR Little Endian 1.2.840.10008.1.2
JPEG Baseline 1.2.840.10008.1.2.4.50

2.1.1. Association Establishment Policies

2.1.1.1. General
The following Application Context Name will be proposed and recognized by IMPAX:
• DICOM 3.0 Application Context 1.2.840.10008.3.1.1.1

IMPAX contains no limitations for maximum PDU size.

Page 10 of 23 IMPAX Storage and Print Services Version 3.0– 30 Sep 96

2.1.1.2. Number of Associations

The maximum number of simultaneous associations accepted by IMPAX is configurable at run time,
based on the system resources available. By default, the maximum number of associations is set at
32. There is no inherent limit to the number of associations other than limits imposed by the
computer operating system.

2.1.1.3. Asynchronous Nature

IMPAX allows a single outstanding operation on any association. Therefore, IMPAX does not
support asynchronous operations window negotiation, other than the default as specified by the
DICOM specification.

2.1.1.4. Implementation Identifying Information

IMPAX will respond with the following implementation identifying parameters:
• Implementation Class UID 1.3.51.0.2.1
• Implementation Version Name IMPAX_WS_5.0

The implementation version name policies are the following: product name “IMPAX_WS” followed
by the version of the product, “_5.0”.

2.1.1.5. Called/Calling Titles

The default calling title that IMPAX will use is “IMPAX_WS”. This parameter can be configured via
the GUI. IMPAX is configured to validate the Called Title of the requesting SCU during association
negotiation. This will provide IMPAX with a first pass level of security, to prevent unwanted SCU
processes from accessing vital hospital information.

2.1.2. Association Initiation by Real World Activity

2.1.2.1. Real World Activity - Verification

2.1.2.1.1. ASSOCIATED REAL WORLD ACTIVITY – VERIFICATION

IMPAX will issue Verification requests in response to UI mediated requests from the user to test
validity of DICOM connection.

2.1.2.1.2. PRESENTATION CONTEXT TABLE - VERIFICATION

Table 7 Presentation Contexts for Verification

SOP Class Transfer Syntax Role Extended Negotiation

All Table 1 All Table 5 SCU None

2.1.2.1.3. SOP SPECIFIC CONFORMANCE - VERIFICATION

IMPAX provides standard conformance to the DICOM Verification Service Class.

Version 3.0– 30 Sep 96 IMPAX Storage and Print Services Page 11 of 23

2.1.2.2. Real World Activity – Storage

2.1.2.2.1. ASSOCIATED REAL WORLD ACTIVITY – STORAGE

IMPAX will transmit images that have been sent to it previously, driven by user requests or
automated processes.

2.1.2.2.2. PRESENTATION CONTEXT TABLE – STORAGE

IMPAX may request any of the Presentation Contexts listed in Table 8for Storage.

Table 8 Presentation Contexts for Storage

SOP Class Transfer Syntax Role Extended Negotiation

All Table 2 All Table 6 SCU None

2.1.2.2.3. SOP SPECIFIC CONFORMANCE – STORAGE

IMPAX conforms to the DICOM Storage Service Class as an SCU.

2.1.2.3. Real World Activity – Find

2.1.2.3.1. ASSOCIATED REAL WORLD ACTIVITY – FIND

IMPAX will issue query requests to other SCPs upon UI mediated requests from the user.

2.1.2.3.2. PRESENTATION CONTEXT TABLE – FIND

IMPAX may request the Presentation Contexts list in Table 9 for Query.

Table 9 Presentation Contexts for Query

SOP Class Transfer Syntax Role Extended Negotiation

All Table 3 Find All Table 5 SCU None

2.1.2.3.3. SOP SPECIFIC CONFORMANCE - FIND

IMPAX may request any mandatory search keys. The following four tables describe the search keys
for the 4 levels of query that IMPAX requests.

Table 10 Patient Level Attributes

Description Tag
Patient name (0x0010, 0x0010)
Patient ID (0x0010, 0x0020)
Page 12 of 23 IMPAX Storage and Print Services Version 3.0– 30 Sep 96

Table 11 Study level attributes

Description Tag
Study instance UID (0x0020, 0x000D)
Study ID (0x0020, 0x0010)
Study date (0x0008, 0x0020)
Study time (0x0008, 0x0010)
Accession number (0x0008, 0x0050)

Table 12 Series Level Attributes

Description Tag
Series instance UID (0x0020, 0x000E)
Series number (0x0020, 0x0011)
Modality (0x0008, 0x0060)

Table 13 Image Level Attributes

Description Tag
SOP instance UID (0x0008, 0x0018)
Image number (0x0020, 0x0013)

2.1.2.4. Real World Activity – Move

2.1.2.4.1. ASSOCIATED REAL WORLD ACTIVITY – MOVE

IMPAX may issue requests to an SCU. IMPAX may propose one of the three query models: Patient
Root, Study Root, and Patient/Study Only.

2.1.2.4.2. PRESENTATION CONTEXT TABLE – MOVE

IMPAX may request any of the Presentation Contexts listed in Table 14 for Move.

Table 14 Presentation Contexts for Move

SOP Class Transfer Syntax Role Extended Negotiation

All Table 3 Move All Table 5 SCU None

2.1.2.4.3. SOP SPECIFIC CONFORMANCE – MOVE

IMPAX provides standard conformance as an SCU.

Version 3.0– 30 Sep 96 IMPAX Storage and Print Services Page 13 of 23

2.1.2.5. Real World Activity –Printing

2.1.2.5.1. ASSOCIATED REAL WORLD ACTIVITY – PRINTING

IMPAX will issue print requests based on UI mediated requests from users.

2.1.2.5.2. PRESENTATION CONTEXT TABLE – PRINTING

IMPAX will request any of the Presentation Contexts listed in Table 15 for Print Management.

Table 15 Presentation Contexts for Printing

SOP Class Transfer Syntax Role Extended Negotiation

All Table 4 All Table 5 SCU None

2.1.2.5.3. SOP SPECIFIC CONFORMANCE - PRINTING

IMPAX provides standard conformance to the DICOM Print Service Classes by supporting a
number of distinct Service classes, as described below.

2.1.2.5.3.1. SOP Specific Conformance to Basic Film Session SOP Class

IMPAX requests the following attributes of the Basic Film Session SOP Class. Values and ranges
are configured to match the capabilities of the printer, and the preferences of the particular user.

Table 16 Attributes for a Basic Film Session

Attribute Name Tag

Number of Copies (2000,0010)
Print Priority (2000,0020)
Medium Type (2000,0030)
Film Destination (2000,0040)
Film Session Label (2000,0050)

2.1.2.5.3.2. SOP Specific Conformance to Basic Film Box SOP Class

IMPAX requests the following attributes of the Basic Film Box SOP Class. Values and ranges are
configured to match the capabilities of the printer, and the preferences of the particular user.
Page 14 of 23 IMPAX Storage and Print Services Version 3.0– 30 Sep 96

Table 17 Attributes for a Basic Film Box

Attribute Name Tag

Image Display Format (2010,0010)
Referenced Film Session Sequence (2010,0500)
Referenced Basic Image Box Sequence (2010,0510)
Film Orientation (2010,0040)
Film Size ID (2010,0050)
Magnification Type (2010,0060)
Max Density (2010,0130)
Configuration Information (2010,0150)
Annotation Display Format ID (2010,0030)
Smoothing Type (2010,0080)
Border Density (2010,0100)
Empty Image Density (2010,0110)
Min Density (2010,0120)
Trim (2010,0140)

2.1.2.5.3.3. SOP Specific Conformance to Basic Greyscale Image Box SOP Class

The following attributes are requested. Values and ranges depend on the characteristics of the
images stored in IMPAX.

Table 18 Attributes for a Basic Greyscale Image Box

Attribute Name Tag

Image Position (2020,0010)
Preformatted Greyscale Image Sequence (2020,0110)
> Samples Per Pixel (0028,0002)
> Photometric Interpretation (0028,0004)
> Rows (0028,0010)
> Columns (0028,0011)
> Pixel Aspect Ratio (0028,0034)
> Bits Allocated (0028,0100)
> Bits Stored (0028,0101)
> High Bit (0028,0102)
> Pixel Representation (0028,0103)
> Pixel Data (7FE0,0010)
Polarity (2020,0020)
Magnification Type (2010,0060)
Smoothing Type (2010,0080)
Version 3.0– 30 Sep 96 IMPAX Storage and Print Services Page 15 of 23

2.1.2.5.3.4. SOP Specific Conformance to Basic Color Image Box SOP Class

The following attributes are requested. Values and ranges depend on the characteristics of the
images stored in IMPAX.

Table 19 Attributes for a Basic Color Image Box

Attribute Name Tag

Image Position (2020,0010)
Preformatted Color Image Sequence (2020,0111)
> Samples Per Pixel (0028,0002)
> Photometric Interpretation (0028,0004)
> Planar Configuration (0028,0006)
> Rows (0028,0010)
> Columns (0028,0011)
> Pixel Aspect Ratio (0028,0034)
> Bits Allocated (0028,0100)
> Bits Stored (0028,0101)
> High Bit (0028,0102)
> Pixel Representation (0028,0103)
> Pixel Data (7FE0,0010)
Polarity (2020,0020)
Magnification Type (2010,0060)
Smoothing Type (2010,0080)

2.1.2.5.3.5. SOP Specific Conformance to Referenced Image Box SOP Class

IMPAX will be responsible for any image processing, generation of overlays for demographics,
laterality indicators, measurement, automatic window selection, or any other analysis. All
information to appear on the printed image will be either “burned into” the image or contained in
overlay and/or curve groups.

Table 20 Attributes for a Referenced Image Box

Attribute Name Tag

Image Position (20200010)
Referenced Image Sequence (2020,1140)
> Referenced SOP Class UID (0008,1150)
> Referenced SOP Instance UID (0008,1155)
Polarity (2020,0020)
Magnification Type (2010,0060)
Smoothing Type (2010,0060)
Page 16 of 23 IMPAX Storage and Print Services Version 3.0– 30 Sep 96

2.1.2.5.3.6. SOP Specific Conformance to Printer SOP Class

The following attributes are requested:

Table 21Attributes for a Printer

Attribute Name Tag

Printer Status (2110,0010)
Printer Status Info (2110,0020)
Printer Name (2110,0030)
Manufacturer (0008,0070)
Manufacturer Model Name (0008,1090)
Device Serial Number (0018,1000)
Software Versions (0018,1020)
Date of Last Calibration (0018,1200)
Time of Last Calibration (0018,1201)

2.1.3. Association Acceptance Policy

2.1.3.1. Real World Activity – Verification

2.1.3.1.1. ASSOCIATED REAL WORLD ACTIVITY – VERIFICATION

IMPAX will respond to Verification requests to provide an SCU with the ability to determine if
IMPAX is receiving DICOM requests.

2.1.3.1.2. PRESENTATION CONTEXT TABLE – VERIFICATION

IMPAX will accept any of the Presentation Contexts listed in Table 22 for Verification.

Table 22 Presentation Contexts for Verification

SOP Class Transfer Syntax Role Extended Negotiation

All Table 1 All Table 5 SCP None

2.1.3.1.3. SOP SPECIFIC CONFORMANCE – VERIFICATION

IMPAX provides standard conformance to the DICOM Verification Service Class. IMPAX returns
one of the following status codes:

Table 23 Verification Status Codes

Service Status Further Meaning Protocol Codes Related Fields Description

Success Success 0000 Operation performed properly

2.1.3.1.4. PRESENTATION CONTEXT ACCEPTANCE CRITERION – VERIFICATION

IMPAX will always accept a Presentation Context for the Verification SOP Class with the default
DICOM transfer syntax listed in Table 5.
Version 3.0– 30 Sep 96 IMPAX Storage and Print Services Page 17 of 23

2.1.3.1.5. TRANSFER SYNTAX SELECTION POLICIES - VERIFICATION

Since no DICOM data object is associated with a Verification command, only the default DICOM
transfer syntax is required/supported.

2.1.3.2. Real World Activity – Storage

2.1.3.2.1. ASSOCIATED REAL WORLD ACTIVITY – STORAGE

IMPAX will store images that are sent to it from an SCU. All images received by IMPAX can be
retrieved at a later time from IMPAX. However, the rate of return of the images will vary,
depending on the state of the images. The images can be in one of three states:

• Online The image is immediately available.

• Nearline The image is automatically available; however, there may be a small delay in the
retrieval time.
• Offline The image requires manual assistance to become online. The retrieval time is
dependent upon the time for manual intervention.

2.1.3.2.2. PRESENTATION CONTEXT TABLE - STORAGE

IMPAX will accept any of the Presentation Contexts listed in Table 24 for Storage.

Table 24 Presentation Contexts for Storage

SOP Class Transfer Syntax Role Extended Negotiation

All from Table 2 Table 6 SCP See Note

Note: Storage Extended Negotiation will be supported. IMPAX will respond with the
following information:

Table 25 Storage Extended Negotiation

Field Name Value Description of Field

Level of Support 2 Level 2 (FULL) SCP
Element Criterion 0 Does not coerce any element

2.1.3.2.3. SOP SPECIFIC CONFORMANCE - STORAGE

IMPAX conforms to the DICOM Storage Service Class at Level 2 (Full). No elements are discarded
or coerced by IMPAX. In the event of a successful C-STORE operation, the image has been written
to internal storage, and can be retrieved at any later time.

IMPAX conforms to the DICOM File Management Roles and Services as a File-set Creator
(FSC), a File-set Reader (FSR) and a File-set Updater (FSU), as defined in Part 10 of the DICOM
specification. IMPAX will store all DICOM images with the File Meta Information Header.
IMPAX will create and update the DICOMDIR file for each File-set. The contents of the Record
Selection Keys will contain those fields that are stored within the IMPAX database at the time the
image was written.
Page 18 of 23 IMPAX Storage and Print Services Version 3.0– 30 Sep 96

⇒ C-STORE: IMPAX returns one of the following status codes to a C-STORE request.

Code Status Meaning

A700 Refused Out of resources. Indicates that there was not enough
storage space to store the image. Recovery from this
condition is left to the administrative functions.
A800 Refused SOP Class not supported.
Indicates that the SOP Class of the Image in the
C-STORE operation did not match the Abstract Syntax
negotiated for the Presentation Context.
A900 Error Data set does not match SOP Class.
Indicates that the Data Set does not encode an instance of
the SOP Class specified.
C000 Error Failed.
The operation was not successful.
C005 Error Cannot understand.
Indicates that the Data Set cannot be parsed into
elements.
B007 Warning Indicates that the Data Set does not match the SOP Class,
but that the image was stored anyway.
D000 Warning Duplicate SOP Instance UID.
Indicates that the SOP Instance UID of the specified
image is already stored in the database.
0000 Success Operation performed properly.

2.1.3.2.4. PRESENTATION CONTEXT ACCEPTANCE CRITERION - STORAGE

IMPAX will accept any number of Storage Presentation Contexts per association request. Any one
Abstract Syntax may be specified more than once in an association request, if the Transfer Syntaxes
differ between the Presentation Contexts.

2.1.3.2.5. TRANSFER SYNTAX SELECTION POLICIES – STORAGE

IMPAX currently only supports the default transfer syntax of Implicit Little Endian.

2.1.3.3. Real World Activity – Find

2.1.3.3.1. ASSOCIATED REAL WORLD ACTIVITY – FIND

IMPAX will respond to query requests that are sent to it from an SCU. IMPAX accepts the three
query models: Patient Root, Study Root, and Patient/Study Only.

2.1.3.3.2. PRESENTATION CONTEXT TABLE – FIND

IMPAX will accept any of the Presentation Contexts list in Table 26 for Query.
Version 3.0– 30 Sep 96 IMPAX Storage and Print Services Page 19 of 23

Table 26 Presentation Contexts for Find

SOP Class Transfer Syntax Role Extended Negotiation

All Table 3 Find All Table 5 SCP See Note

Note: Find Extended Negotiation will be supported. IMPAX will respond with the following
information:

Table 27 Find Extended Negotiation

Field Name Value Description of Field

Relational queries 1 Relational queries supported

2.1.3.3.3. SOP SPECIFIC CONFORMANCE – FIND

SOP classes of the Query/Retrieve Service Class are implemented via the DIMSE C-FIND, C-
MOVE and C-GET services as defined in Part 7 of the DICOM standard.

IMPAX supports hierarchical queries. IMPAX supports relational queries. IMPAX, by default,
supports all mandatory search keys. By configuration, any additional field that is in the data
dictionary or a private extension can be made a search key. The following four tables describe the
search keys for the four levels of query that IMPAX supports.

Table 28 Patient Level Attributes

Description Tag
Patient name (0x0010, 0x0010)
Patient ID (0x0010, 0x0020)

Table 29 Study Level Attributes

Description Tag
Study instance UID (0x0020, 0x000D)
Study id (0x0020, 0x0010)
Study date (0x0008, 0x0020)
Study time (0x0008, 0x0010)
Accession number (0x0008, 0x0050)

Table 30 Series Level Attributes

Description Tag
Series instance UID (0x0020, 0x000E)
Series number (0x0020, 0x0011)
Modality (0x0008, 0x0060)
Page 20 of 23 IMPAX Storage and Print Services Version 3.0– 30 Sep 96

Table 31 Image Level Attributes

Description Tag
SOP instance UID (0x0008, 0x0018)
Image number (0x0020, 0x0013)

⇒ C-FIND: IMPAX returns one of the following status codes to a C-FIND request.

Code Status Meaning

A700 Refused Out of Resources
A900 Failed The specified identifier contains a request that does not
match the specified SOP Class.
C001 Failed Unable to process.
For some reason (database off-line?) we cannot process
this request at this time.
FE00 Cancel Matching terminated due to Cancel Request.
The original requester canceled this operation.
FF00 Pending All Optional Keys are supported in the same manner as
Required Keys.
FF01 Pending The matching operation is continuing. Warning that one
or more Optional Keys were not supported in the same
manner as Required Keys.
0000 Success Operation performed properly.

2.1.3.3.4. PRESENTATION CONTEXT ACCEPTANCE CRITERION – FIND

IMPAX will accept any number of Find Presentation Contexts per association request. Any one
Abstract Syntax may be specified more than once in an association request, if the Transfer Syntaxes
differ between the Presentation Contexts.

2.1.3.3.5. TRANSFER SYNTAX SELECTION POLICIES – FIND

IMPAX currently only supports the default transfer syntax of Implicit Little Endian.

2.1.3.4. Real World Activity – Move

2.1.3.4.1. ASSOCIATED REAL WORLD ACTIVITY – MOVE

IMPAX will respond to retrieve requests that are sent to it from an SCU. IMPAX accepts the three
query models, Patient Root, Study Root, and Patient/Study Only.
Version 3.0– 30 Sep 96 IMPAX Storage and Print Services Page 21 of 23

2.1.3.4.2. PRESENTATION CONTEXT TABLE - MOVE

IMPAX will accept any of the Presentation Contexts listed in Table 32 for Query.

Table 32 Presentation Contexts for Move

SOP Class Transfer Syntax Role Extended Negotiation

All Table 3 Move Table 5 SCP See Note

Note: Move Extended Negotiation will be supported. IMPAX will respond with the following
information:

Table 33 Move Extended Negotiation

Field Name Value Description of Field

Relational queries 1 Relational queries supported

2.1.3.4.3. SOP SPECIFIC CONFORMANCE - MOVE

IMPAX will try to establish an association with the move destination specified in the Move request.
One or more of the Presentation Contexts listed in the Store section of this document may be
negotiated in this association.

IMPAX will send pending responses after each image has been successfully sent to the move
destination.

⇒ C-MOVE: IMPAX returns one of the following status codes to a C-MOVE request:

Code Status Meaning

A701 Refused Out of Resources.
Unable to calculate number of matches.
A702 Refused Out of Resources.
Unable to perform storage of images to move destination
A801 Failed The destination of this move request is unknown.
A900 Failed The specified identifier contains a request that does not
match the specified SOP Class.
C002 Failed Indicates that IMPAX cannot process this request at this
time.
FE00 Cancel Storage terminated due to Cancel Request.
The original requester canceled this operation.
B000 Warning Storage complete with one or more failures.
FF00 Pending The storage operation is continuing.
FF02 Pending Pending for a long time.
This operation is expected to require a long period of time
to complete. The SCU may break the association at any
time, but the operation will continue to completion.
0000 Success Operation performed properly.
Page 22 of 23 IMPAX Storage and Print Services Version 3.0– 30 Sep 96

2.1.3.4.4. PRESENTATION CONTEXT ACCEPTANCE CRITERION - MOVE

IMPAX will accept any number of Move Presentation Contexts per association request. Any one
Abstract Syntax may be specified more than once in an association request, if the Transfer Syntaxes
differ between the Presentation Contexts.

2.1.3.4.5. TRANSFER SYNTAX SELECTION POLICIES - MOVE

IMPAX currently only supports the default transfer syntax of Implicit Little Endian.

3. Communications Profiles
IMPAX provides DICOM V3.0 TCP/IP Network Communication Support, as defined in Part 8 of
the DICOM standard.

3.1. TCP/IP Stack

IMPAX inherits its TCP/IP stack from the computer system upon which it executes.

3.1.1. Physical Media Support

IMPAX is indifferent to the physical medium over which TCP/IP executes; it inherits the medium
from the computer system upon which it executes.

4. Extensions/Specializations/Privatizations
Not applicable.

5. Configuration
IMPAX obtains configuration information from the following sources:

• Mapping from Application Entity Title to Presentation Address is provided by the database.
Along with this mapping, the database stores those AE titles that are allowed to communicate
with IMPAX. These AE titles are considered “Friends”.

6. Support for Extended Character Sets

IMPAX is known to support the following character sets:

• ISO-IR 6 (default) Basic G0 Set

• ISO-IR 100 Latin Alphabet No. 1
Version 3.0– 30 Sep 96 IMPAX Storage and Print Services Page 23 of 23

7. Acronyms and Abbreviations

The following acronyms and abbreviations are used in this document:

ACR American College of Radiology

AE Application Entity
DICOM Digital Imaging and Communications in Medicine
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