Ali Pacs

DICOM CONFORMANCE STATEMENT
$/, ®
8OWUD3$&6
ALI UltraPACS® 3.0
A.L.I. Technologies Inc.

ALI UltraPACS 3.0 © 1997 A.L.I. Technologies Inc.
DICOM Conformance Statement 12/01/97 Document Version 1.0
A.L.I. Imaging Systems Corp.

A.L.I. Imaging Systems Corp. ii
\\tetra\documents\ultrapacs03.doc
Contents
Revision History ......................................................................................................................... iii
1.0 Introduction ......................................................................................................... 1
2.0 Implementation Model......................................................................................... 1

2.1 Application Data Flow Diagram........................................................................... 1
2.2 Functional Definitions of Application Entities ...................................................... 2
2.3 Sequencing of Real-World Events...................................................................... 2
3.0 AE Specifications................................................................................................ 3
3.1 Storage AE ......................................................................................................... 3
3.1.1 Association Establishment Policies..................................................................... 4
3.1.2 General ............................................................................................................... 4
3.1.1.2 Number of Associations ...................................................................................... 5
3.1.1.3 Asynchronous Nature ......................................................................................... 5
3.1.1.4 Implementation Identifying Information ............................................................... 5
3.1.2 Association Initiation by Real-World Activity ....................................................... 5
3.1.3 Real-World Activity - User requests image transmission..................................... 5
3.1.4 Associated Real-World Activity ........................................................................... 5
3.1.2.1.2 Proposed Presentation Contexts ........................................................................ 6
3.1.2.1.2.1 SOP Specific Conformance  Storage .............................................................. 7
3.1.3 Association Acceptance Policy ........................................................................... 7
3.1.3.1 Real-World Activity - External system requests storage of images ..................... 7
3.1.3.1.1 Associated Real-World Activity ........................................................................... 7
3.1.3.1.2 Presentation Context Table .............................................................................. 10
3.1.3.1.2.1 SOP Specific Conformance  Verification ....................................................... 11
3.1.3.1.2.2 SOP Specific Conformance  Storage ............................................................ 11
3.1.3.1.2.3 Presentation Context Acceptance Criteria ........................................................ 11
3.1.3.1.2.4 Transfer Syntax Selection Policies.................................................................... 12
3.2 Query/Retrieve AE ............................................................................................ 12
3.2.1 Association Establishment Policies................................................................... 13
3.2.1.1 General ............................................................................................................. 13
3.2.1.2 Number of Associations .................................................................................... 13
3.2.1.3 Asynchronous Nature ....................................................................................... 13
3.2.1.4 Implementation Identifying Information ............................................................. 13
3.2.2 Association Initiation by Real-World Activity ..................................................... 14
3.2.2.1 Real-World Activity - Scheduled Examinations (Worklist) Requested by
ALI UltraPACS .................................................................................................. 14
3.2.2.1.1 Associated Real-World Activity ......................................................................... 14
3.2.2.1.2 Proposed Presentation Contexts ...................................................................... 14
3.2.2.1.2.1 SOP Specific Conformance - Modality Worklist ................................................ 14
3.2.2.2 Real-World Activity - User submits query or requests image retrieval............... 14
3.2.2.2.1 Associated Real-World Activity ........................................................................ 14
3.2.2.2.2.1 SOP Conformance - Find SOP Classes ........................................................... 15
3.2.2.2.2.2 SOP Conformance - Move SOP Classes.......................................................... 15
3.2.3 Association Acceptance Policy ......................................................................... 15
3.2.3.1 Real-World Activity - External system queries ALI UltraPACS .......................... 16
3.2.3.1.1 Associated Real-World Activity ......................................................................... 16

A.L.I. Imaging Systems Corp. iii
3.2.3.1.2 Presentation Context Table .............................................................................. 16

3.2.3.1.2.1 SOP Specific Conformance - Verification ......................................................... 17
3.2.3.1.2.2 SOP Conformance - FIND SOP Classes .......................................................... 17
3.2.3.1.2.3 SOP Specific Conformance - MOVE SOP Classes .......................................... 18
3.2.3.1.2.4 SOP Specific Conformance - GET SOP Classes.............................................. 19
3.2.3.1.3 Presentation Context Acceptance Criterion ...................................................... 20
3.2.3.1.4 Transfer Syntax Selection Policies.................................................................... 20
3.3 Print Management AE....................................................................................... 20
3.3.1 Association Establishment Policies................................................................... 21
3.3.1.1 General ............................................................................................................. 21
3.3.1.2 Number of Associations .................................................................................... 21
3.3.1.3 Asynchronous Nature ....................................................................................... 21
3.3.1.4 Implementation Identifying Information ............................................................. 21
3.3.2.1 Association Initiation by Real-World Activity ..................................................... 21
3.3.2.2 Associated Real-World Activity - User submits print job.................................... 21
3.3.2.3 Associated Real-World Activity ......................................................................... 21
3.3.2.1.2.1 SOP Specific Conformance - Basic Print Management .................................... 22
3.3.3 Association Acceptance Policy ......................................................................... 23
4.0 Communication Profiles .................................................................................... 23

4.1 Supported Communication Stacks.................................................................... 23
4.2 TCP/IP .............................................................................................................. 23
4.2.1 Physical Media Support .................................................................................... 23
5.0 Extensions/Specializations/Privatizations ......................................................... 23
6.0 Configuration .................................................................................................... 23

6.1 AE Title/Presentation Address Mapping ........................................................... 23
6.2 Configurable Parameters .................................................................................. 23
7.0 Support for Extended Character Sets ............................................................... 24

A.L.I. Imaging Systems Corp. iv
Revision History
Document Date Author Description

Version
1.0 Feb.28, 1997 Edmond Lau Created
2.0 December 1, 1997 David Heaney Added new SOP Classes

A.L.I. Imaging Systems Corp. v
1.0 Introduction
This document is the DICOM 3.0 Conformance Statement for ALI UltraPACS 1 3.0.
ALI UltraPACS is a self-contained networked computer system used for capturing, storing, and
displaying diagnostic medical images. The system conforms to the DICOM 3.0 standard to
allow the sharing of medical information with other digital imaging systems.
2.0 Implementation Model
2.1 Application Data Flow Diagram
Figure 1 - ALI UltraPACS DICOM Data Flow Diagram
User requests Images received

image transmission on external system
Storage
Application
Entity
Images stored External system
on disk requests storage
of images
List of scheduled Query/Retrieve Worklist is queried

examinations is Application on external system
requested Entity
External system
queries worklist,
Local database demographics, and
queried to process requests images
external system’s
query
External system
receives images
satisfying query
User submits Database is queried

query or requests on external system and
image retrieval images retrieved by
UltraPACS
User submits Print Management

Application Images printed
images to print
Entity
DICOM 3.0 Interface

1
ALI UltraPACS is a registered trademark of A.L.I. Technologies Inc. All other trademarks belong to their respective owners.

A.L.I. Imaging Systems Corp. 1
The Storage AE can both send and receive Storage Image objects. As an SCU, it receives
requests from an ALI UltraPACS user to transmit a list of images to a specific DICOM
destination. As an SCP, the AE can respond to external Storage Requests which are either
unsolicited or a result of DICOM C-MOVE requests.
The querying capabilities of ALI UltraPACS are bi-directional. It can query for information from
external sources and allow external systems to query it. Worklists, patient and study
demographic queries, and image retrievals can be initiated and serviced by ALI UltraPACS.
Users can initiate an association with a DICOM-compliant printer to print a list of selected
images.
2.2 Functional Definitions of Application Entities
ALI UltraPACS contains three local Application Entities (AE’s): Storage, Query/Retrieve, and
Print Management. These run as either a Service Class User (SCU); a Service Class Provider
(SCP); or both an SCU and SCP. AEs run as background Unix processes.
The Storage AE acts as an SCU and SCP and implements the Storage Service Class
operation. It can transmit images captured as frame grabs from external devices or images
received from external DICOM transmissions.
The Query/Retrieve AE runs as both an SCU and SCP which implement the Query/Retrieve
Service Class. It can act as a client to retrieve worklists, patient and study demographics, and
images from external DICOM Query/Retrieve SCPs. As an SCP, ALI UltraPACS can receive
requests from external devices to query the database and retrieve images.
The Print Management AE implements the Print Management Service Class as an SCU. It
supports both the Basic Grayscale Print Management and Basic Color Print Management
Classes.
2.3 Sequencing of Real-World Events
Not applicable.

3.0 AE Specifications
3.1 Storage AE
The Storage AE provides Standard Conformance to the following DICOM V3.0 SOP Classes
as an SCU:
Table 1: SOP Class Conformance as SCU
SOP Class Name SOP Class UID
US Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.6
US Image Storage 1.2.840.10008.5.1.4.1.1.6.1
US Multi-frame Storage (Retired) 1.2.840.10008.5.1.4.1.1.3
US Multi-frame Storage 1.2.840.10008.5.1.4.1.1.3.1
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
MR Image Storage 1.2.840.10008.5.1.4.1.1.4
NM Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.5
NM Image Storage 1.2.840.10008.5.1.4.1.1.20
Visible Light Image Storage 1.2.840.10008.5.1.4.1.1.77.1
Visible Light Multi-frame Storage 1.2.840.10008.5.1.4.1.1.77.2
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7
XA Single-Plane Image Storage 1.2.840.10008.5.1.4.1.1.12.1
RF Image Storage 1.2.840.10008.5.1.4.1.1.12.2
RT Image Storage 1.2.840.10008.5.1.4.1.1.481.1
PET Image Storage 1.2.840.10008.5.1.4.1.1.128
ALI UltraPACS can be configured to use the retired US Image objects (US Image Storage,
1.2.840.10008.5.1.4.1.1.6, and US Multi-frame Storage, 1.2.840.10008.5.1.4.1.1.3) rather than
the current US objects.
ALI UltraPACS can generate and transmit US Image, US Multi-frame, and the Secondary
2
Capture Image objects if the image was originally captured from an external device. However,
all the other classes listed in Table 1 can be transmitted only if they were originally captured
from an external DICOM device (e.g. when ALI UltraPACS receives a DICOM CT object, this
object is stored locally in DICOM format and can be transmitted in the form in which it was
received). These are the default SOP Classes support. By altering the configuration it is
possible to support additional or fewer SOP Classes
2
ALI UltraPACS always uses a frame capture board.

The Storage AE provides Standard Conformance to the following DICOM V3.0 SOP Classes
as an SCP:
Table 2: SOP Class Conformance as SCP

Verification 1.2.840.10008.1.1
US Image Storage 1.2.840.10008.5.1.4.1.1.6.1
US Multi-frame Storage (Retired) 1.2.840.10008.5.1.4.1.1.3
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
MR Image Storage 1.2.840.10008.5.1.4.1.1.4
NM Image Storage 1.2.840.10008.5.1.4.1.1.20
Visible Light Image Storage 1.2.840.10008.5.1.4.1.1.77.1
Visible Light Multi-frame Storage 1.2.840.10008.5.1.4.1.1.77.2
RF Image Storage 1.2.840.10008.5.1.4.1.1.12.2
RT Image Storage 1.2.840.10008.5.1.4.1.1.481.1
These are the default SOP Classes support. By altering the configuration it is possible to
support additional or fewer SOP Classes.
3.1.1 Association Establishment Policies
3.1.2 General
The Storage AE will initiate a new association when the user requests the transmission of a
study. Also, ALI UltraPACS can be configured to automatically initiate an association when a
study is being performed. In this case, when an image is captured from an examination that is
in progress, it will be automatically sent to a named destination. An attempt will be made to
transmit all the images in the study in a single association. The association will be released
when all the images have been sent. If the association is broken or some other association
related error is detected, the association will be aborted and an attempt will be made to
transmit the unsent images in a new association.
An association will be accepted with an external SCU if the requesting SCU provides valid
parameters. Valid parameters include a valid presentation context. The Storage AE can be
configured to allow only associations with specified hosts. It does not check the caller’s AE
Title when accepting an association.
The maximum PDU size which will be offered is 16,386 bytes.

3.1.1.2 Number of Associations
The Storage AE will initiate one association at any time.
Each time the Storage AE accepts an association, a child process is spawned to complete the
transfer of the medical image data or service the verification request. The maximum number of
child processes is set by configuration. Once this number has been reached, no more
associations will be accepted until one of the active child processes exits.
3.1.1.3 Asynchronous Nature
The Storage AE does not provide asynchronous behavior. All association requests must be
completed and acknowledged before a new operation can be initiated.
3.1.1.4 Implementation Identifying Information
An implementation class UID of “1.2.840.113711.1” is provided. The implementation version

name is configured at the time of installation.
3.1.2 Association Initiation by Real-World Activity
3.1.3 Real-World Activity  User requests image transmission
3.1.4 Associated Real-World Activity
An association is initiated when an ALI UltraPACS user requests the transmission of images.
If an error occurs during transmission, the current association is released, and a new
association will be initiated in order to continue image transmission. The maximum number of
retries for a study to be sent is configurable.

3.1.2.1.2 Proposed Presentation Contexts
Table 3: Proposed Presentation Contexts

Abstract Syntax Transfer Syntax
Name UID Name UID Role Extended
Negot-
iation
US Image 1.2.840.10008.5.1.4.1.1.6 DICOM Implicit 1.2.840.10008.1.2 SCU None
Storage VR Little Endian
(Retired)
US Image 1.2.840.10008.5.1.4.1.1.6.1 DICOM Implicit 1.2.840.10008.1.2 SCU None
US Multi- 1.2.840.10008.5.1.4.1.1.3 DICOM Implicit 1.2.840.10008.1.2 SCU None
frame Storage VR Little Endian
(Retired)
US Multi- 1.2.840.10008.5.1.4.1.1.3.1 DICOM Implicit 1.2.840.10008.1.2 SCU None
Computer 1.2.840.10008.5.1.4.1.1.1 DICOM Implicit 1.2.840.10008.1.2 SCU None
Radiography VR Little Endian
Image
Storage
CT Image 1.2.840.10008.5.1.4.1.1.2 DICOM Implicit 1.2.840.10008.1.2 SCU None
MR Image 1.2.840.10008.5.1.4.1.1.4 DICOM Implicit 1.2.840.10008.1.2 SCU None
NM Image 1.2.840.10008.5.1.4.1.1.5 DICOM Implicit 1.2.840.10008.1.2 SCU None
(Retired)
NM Image 1.2.840.10008.5.1.4.1.1.20 DICOM Implicit 1.2.840.10008.1.2 SCU None
VL Image 1.2.840.10008.5.1.4.1.1.77.1 DICOM Implicit 1.2.840.10008.1.2 SCU None
VL Multi- 1.2.840.10008.5.1.4.1.1.77.2 DICOM Implicit 1.2.840.10008.1.2 SCU None
Secondary 1.2.840.10008.5.1.4.1.1.7 DICOM Implicit 1.2.840.10008.1.2 SCU None
Capture VR Little Endian
Image
Storage
XA Single- 1.2.840.10008.5.1.4.1.1.12.1 DICOM Implicit 1.2.840.10008.1.2 SCU None
Plane Image VR Little Endian
Storage
RF Image 1.2.840.10008.5.1.4.1.1.12.2 DICOM Implicit 1.2.840.10008.1.2 SCU None
RT Image 1.2.840.10008.5.1.4.1.1.481. DICOM Implicit 1.2.840.10008.1.2 SCU None
Storage 1 VR Little Endian
PET Image 1.2.840.10008.5.1.4.1.1.128 DICOM Implicit 1.2.840.10008.1.2 SCU None

3.1.2.1.2.1 SOP Specific Conformance  Storage
In the case of a successful C-STORE response from the SCP, the Storage AE will continue to
send any unsent images belonging to the same study. The association will be properly
released after all relevant images have been sent.
If ultrasound objects are transferred, all the mandatory modules of the Ultrasound Image
Information Object Definition are provided. No non-mandatory modules are provided (e.g.
Frame of Reference, US Region Calibration, Overlay Plane, etc.). Of the mandatory modules,
all Type 1 and Type 2 data elements are provided. No optional data elements (elements of
Type 3) are provided.
If the image was originally acquired through a DICOM device, the entire set of tags received
with the image will be saved in ALI UltraPACS. When the object is selected for transmission
from ALI UltraPACS, the content of these objects will be as they were originally received.
Thus, the set of optional tags contained in DICOM objects going out from ALI UltraPACS
depends on the information that was received.
3.1.3 Association Acceptance Policy
The Storage AE accepts associations only if they have valid presentation contexts. It can be
configured to accept only associations with certain hosts. The Storage AE places configurable
limitations on the number of simultaneous connections it will support. Once the Storage AE
accepts an association, a spawned child process will receive any images transmitted on that
association and store them on the hard disk in a format required by the ALI UltraPACS system.
3.1.3.1 Real-World Activity  External system requests storage of images
The Real-World Activity is the transfer of medical images from an external storage SCU to the
Storage AE on the ALI UltraPACS system.
3.1.3.1.1 Associated Real-World Activity
The associated Real-World Activity with the C-STORE service is the storage of medical image
data on a designated hard disk. The Storage AE will return a failure status if it is unable to
store the images on to the hard disk.
The Storage AE expects that all images related to a single DICOM Study will be sent over the
same Association. If this is not the case, and images belonging to the same DICOM Study are
sent over different DICOM Associations then the Storage AE will attempt to add all images to
the same directory on the ALI UltraPACS workstation. If this is not possible because some
other process has a write-lock on an existing directory then the images will have to be added
to a different directory on the ALI UltraPACS workstation. Because ALI UltraPACS displays
images on a directory basis this will have the visible effect of presenting the user with two
Study “folders” for the same DICOM Study.
The Storage AE can be configured in two different modes. In one mode, it is configured to
retain the original DICOM data in DICOM Part 10 compliant file format. In the other mode, it
converts all incoming images to TIFF format thus losing all elements whose values are not
stored to the database.
The following elements are either stored to the permanent ALI UltraPACS database or those of
particular importance in the received images:
Table 4: Significant Elements in Received Images

Attribute Name Tag ID Significance
Patient Name (0010,0010) Storage SCP can be configured to apply a
default value if there is no value specified.
Value is saved to database as separate first and
last names. Only first and last names are
entered in the ALI UltraPACS database.
Names will be parsed correctly if they are in the
format of ‘lname^fname’ or ‘lname, fname’. If
space separation is used (i.e. ‘lname fname’)
then the entire name will be treated as the last
name.
Patient ID (0010,0010) Storage SCP can be configured to apply a
The Patient ID must be unique.
A verification on incoming Patient IDs is
performed. If an ID already exists but the
existing name does not match, then the ID is
coerced to the form ‘<original ID>+1’.
Value is saved to database.
Patient’s Birth Date (0010,0030) Storage SCP can be configured to apply a
Patient’s Sex (0010,0040) First character must be ‘M’, ‘m’, ‘F’, ‘f’, ‘O’, or ‘o’.
If a different value or not specified then will be
entered in the database as ‘U’, unknown. Value
is saved to database.
SOP Instance UID (0008,0018) Must be provided.
Study Date (0008,0020) Storage SCP can be configured to apply a
Accession Number (0008,0050) Storage SCP can be configured to apply a
Modality (0008,0060) Storage SCP can be configured to apply a
Value is saved to database but must be two
characters in length.

Attribute Name Tag ID Significance

Referring (0008,0090) Value is saved to database.
Physician’s Name
Study Description (0008,1030) If matched value(s) in the ALI UltraPACS exam
type database then it will be saved to the
database as an exam type.
Series Description (0008,103E) If matched value(s) in the ALI UltraPACS exam
Operator’s Name (0008,1070) If name matches a valid User of ALI UltraPACS
then it will be saved to the database as the
sonographer.
Body Part (0018,0015) If matched value(s) in the ALI UltraPACS exam
Examined type database then it will be saved to the
Image Type (0008,0008) If the third value, the modality specific value,
matches value(s) in the ALI UltraPACS exam
Study Instance UID (0020,000D) Must be provided.
Photometric (0028,0004) The following photometric interpretations are
Interpretation supported for display purposes:
MONOCHROME1, MONOCHROME2, RGB,
ARGB, PALETTE COLOR, CMYK, and YBR
FULL.
Bits Allocated (0028,0100) All values of 16 or fewer are supported for
display purposes.
Bits Stored (0028,0101) Must be 8 or 16 bits for display purposes.
Window Center (0028,1050) It is preferred that this value be defined for
images that have greater than 8 bits stored per
pixel sample.
Window Width (0028,1051) It is preferred that this value be defined for
images that have greater than 8 bits stored per
pixel sample.
For the purposes of display the aforementioned photometric interpretations are supported.
Currently there is no support for overlay information, either embedded in a DICOM Image
Object or as a separate Stand-Alone Overlay DICOM Object.
It is preferred that optimal Window Center and Width values be specified in the DICOM Image
Objects if they have greater than 8 bits of image data stored per sample. If optimal Window
Center and Width values can not be provided then it is preferred that none are included as ALI
UltraPACS is capable of estimating values.

3.1.3.1.2 Presentation Context Table
Any of the Presentation Contexts shown in Table 4 are acceptable to the Storage AE for
receiving images.
Table 5 : Proposed Presentation Contexts

Negot-
iation
US Image 1.2.840.10008.5.1.4.1.1.6 DICOM Implicit 1.2.840.10008.1.2 SCP None
(Retired)
US Image 1.2.840.10008.5.1.4.1.1.6.1 DICOM Implicit 1.2.840.10008.1.2 SCP None
US Multi-frame 1.2.840.10008.5.1.4.1.1.3 DICOM Implicit 1.2.840.10008.1.2 SCP None
(Retired)
US Multi-frame 1.2.840.10008.5.1.4.1.1.3.1 DICOM Implicit 1.2.840.10008.1.2 SCP None
Computer 1.2.840.10008.5.1.4.1.1.1 DICOM Implicit 1.2.840.10008.1.2 SCP None
Radiography VR Little Endian
Image Storage
CT Image 1.2.840.10008.5.1.4.1.1.2 DICOM Implicit 1.2.840.10008.1.2 SCP None
MR Image 1.2.840.10008.5.1.4.1.1.4 DICOM Implicit 1.2.840.10008.1.2 SCP None
NM Image 1.2.840.10008.5.1.4.1.1.5 DICOM Implicit 1.2.840.10008.1.2 SCP None
(Retired)
NM Image 1.2.840.10008.5.1.4.1.1.20 DICOM Implicit 1.2.840.10008.1.2 SCP None
VL Image 1.2.840.10008.5.1.4.1.1.77.1 DICOM Implicit 1.2.840.10008.1.2 SCP None
VL Multi-frame 1.2.840.10008.5.1.4.1.1.77.2 DICOM Implicit 1.2.840.10008.1.2 SCP None
Secondary 1.2.840.10008.5.1.4.1.1.7 DICOM Implicit 1.2.840.10008.1.2 SCP None
Capture Image VR Little Endian
Storage
XA Single- 1.2.840.10008.5.1.4.1.1.12.1 DICOM Implicit 1.2.840.10008.1.2 SCP None
Plane Image VR Little Endian
Storage
RF Image 1.2.840.10008.5.1.4.1.1.12.2 DICOM Implicit 1.2.840.10008.1.2 SCP None
RT Image 1.2.840.10008.5.1.4.1.1.481. DICOM Implicit 1.2.840.10008.1.2 SCP None
Storage 1 VR Little Endian
PET Image 1.2.840.10008.5.1.4.1.1.128 DICOM Implicit 1.2.840.10008.1.2 SCP None

3.1.3.1.2.1 SOP Specific Conformance  Verification
The Storage AE provides standard conformance to the Verification SOP Class as an SCP.
3.1.3.1.2.2 SOP Specific Conformance  Storage
The Storage AE is capable of providing two different levels of conformance depending on how
it is configured:
If it is configured to convert incoming images to TIFF then it has Level 0 conformance to

the Storage SOP Class. A successful storage operation means the image data has been
written to the internal storage on the ALI UltraPACS system and a subset of the Image
Attributes as defined in 3.1.3.1.1 have been stored to the database.
If it is configured to leave incoming images in DICOM format then it has Level 2 conformance to the
Storage SOP Class. A successful storage operation means that the entire original DICOM Image Object
has been written to the internal storage on the ALI UltraPACS system. In addition, a subset of the Image
Attributes as defined in 3.1.3.1.1 have been stored to the database. Thus, all elements have been stored
and may be accessed.
The Storage AE returns one of the following status codes if the C-STORE operation was unsuccessful:
A700 (Out of Resources).

Indicates that there was not enough disk space to store the image. The image will not be
saved and the association will be dropped.
B000 (Coercion of Data Elements).

Indicates that one or more element values were coerced. Refer to the Attributes defined in
3.1.3.1.1 for a list of those that can be coerced. Note that return of this status is normally
disabled as some SCUs treat it as an Error code rather than a Warning.
A800 (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 (Data Set does not match SOP Class).

Indicates that the Data Set does not encode an instance of the SOP Class specified.
C000 (Cannot understand)

Indicates that the Data Set cannot be parsed into elements by the Storage AE.
3.1.3.1.2.3 Presentation Context Acceptance Criterion
The Storage AE will only accept the Presentation Contexts specified in Table 4. The Storage
AE can be configured to reject valid Presentation Contexts if the external DICOM host is not
listed in a local configuration file. In addition, a valid Presentation Context can be rejected if the
maximum limit on the number of simultaneous processes has been reached.
The Storage AE does not check for and will accept duplicate presentation contexts.
3.1.3.1.2.4 Transfer Syntax Selection Policies
The Storage AE only supports the Implicit VR Little Endian transfer syntax. Any proposed
Presentation Context which includes the Implicit VR Little Endian transfer syntax will be
accepted with the Implicit VR Little Endian transfer syntax. Any proposed Presentation Context
that does not include the Implicit VR Little Endian transfer syntax will be rejected.
3.2 Query/Retrieve AE
The Query/Retrieve AE provides Standard Conformance to the following DICOM V3.0 SOP
Classes as an SCU:
Table 5: SOP Class Conformance as SCU
Patient Root Q/R Information Model - FIND 1.2.840.10008.5.1.4.1.2.1.1
Patient Root Q/R Information Model - MOVE 1.2.840.10008.5.1.4.1.2.1.2
Study Root Q/R Information Model - FIND 1.2.840.10008.5.1.4.1.2.2.1
Study Root Q/R Information Model - MOVE 1.2.840.10008.5.1.4.1.2.2.2
Patient Study Only Information Model - FIND 1.2.840.10008.5.1.4.1.2.3.1
Patient Study Only Information Model - MOVE 1.2.840.10008.5.1.4.1.2.3.2
Modality Worklist Information Model 1.2.840.10008.5.1.4.31
US Image Storage 1.2.840.10008.5.1.4.1.1.6.1
US Multi-frame Storage (Retired) 1.2.840.10008.5.1.4.1.1.3.1
Computer 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
MR Image Storage 1.2.840.10008.5.1.4.1.1.4
NM Image Storage 1.2.840.10008.5.1.4.1.1.20
VL Image Storage 1.2.840.10008.5.1.4.1.1.77.1
VL Multi-frame Storage 1.2.840.10008.5.1.4.1.1.77.2
RF Image Storage 1.2.840.10008.5.1.4.1.1.12.2
RT Image Storage 1.2.840.10008.5.1.4.1.1.481.1

The Query/Retrieve AE provides Standard Conformance to the following DICOM V3.0 SOP
Classes as an SCP:
Table 6: SOP Class Conformance as SCP
Patient Root Q/R Information Model - FIND 1.2.840.10008.5.1.4.1.2.1.1
Patient Root Q/R Information Model - MOVE 1.2.840.10008.5.1.4.1.2.1.2
Patient Root Q/R Information Model - GET 1.2.840.10008.5.1.4.1.2.1.3
Study Root Q/R Information Model - FIND 1.2.840.10008.5.1.4.1.2.2.1
Study Root Q/R Information Model - MOVE 1.2.840.10008.5.1.4.1.2.2.2
Study Root Q/R Information Model -GET 1.2.840.10008.5.1.4.1.2.2.3
Patient Study Only Information Model - FIND 1.2.840.10008.5.1.4.1.2.3.1
Patient Study Only Information Model - MOVE 1.2.840.10008.5.1.4.1.2.3.2
Patient Study Only Information Model - GET 1.2.840.10008.5.1.4.1.2.3.3
Modality Worklist Information Model 1.2.840.10008.5.1.4.31
3.2.1.1 General
The Query/Retrieve AE will initiate associations to retrieve worklists, to submit queries, and to
retrieve images.
The Query/Retrieve AE will accept associations for C-FIND, C-GET, and C-MOVE requests,
and in the case of C-MOVE, will initiate an association with a DICOM AE to send images as
specified by the originator of the C-MOVE.
Every time an ALI UltraPACS user submits a DICOM query, the Query/Retrieve AE initiates an
association with a named DICOM Query/Retrieve SCP.
ALI UltraPACS can also poll an external system for worklists. The Query/Retrieve AE will
initiate an association with an external system when such a poll request is received.
Each time the Query/Retrieve receives an association, a child process will be spawned to
process the query and to handle any possible image retrieval C-STORE sub-operations. The
maximum number of child processes, and thus the maximum number of simultaneous
associations that can be processed, is set by configuration.
Negotiation of multiple outstanding transactions is not supported.
The implementation class UID is “1.2.840.113711.3”. The implementation version name is

created at the time of installation.
3.2.2 Association Initiation by Real-World Activity
3.2.2.1 Real-World Activity  Scheduled Examinations (Worklist) Requested by

ALI UltraPACS
When an updated worklist is requested, either by the ALI UltraPACS user or through a polling
mechanism, the Query/Retrieve AE initiates an association with a named DICOM source.

Negot-iation
Modality 1.2.840.10008.5.1.4.3 DICOM 1.2.840.10008.1.2 SCU None
Worklist 1 Implicit VR
Little
Endian
3.2.2.1.2.1 SOP Specific Conformance  Modality Worklist
The Query/Retrieve AE does not request matching on Optional Matching Key Attributes.
3.2.2.2 Real-World Activity  User submits query or requests image retrieval
When an ALI UltraPACS user submits a query or requests to retrieve images from an external
DICOM Query/Retrieve SCP, the Query/Retrieve AE initiates an association with the named
DICOM source.


Negot-
iation
Patient Root Q/R 1.2.840.10008.5.1.4.1.2.1.1 DICOM 1.2.840.10008.1.2 SCU None
Information Implicit VR
Model - FIND Little Endian
Patient Root Q/R 1.2.840.10008.5.1.4.1.2.1.2 DICOM 1.2.840.10008.1.2 SCU None
Model - MOVE Little Endian
Study Root Q/R 1.2.840.10008.5.1.4.1.2.2.1 DICOM 1.2.840.10008.1.2 SCU None
Study Root Q/R 1.2.840.10008.5.1.4.1.2.2.2 DICOM 1.2.840.10008.1.2 SCU None
Patient Study 1.2.840.10008.5.1.4.1.2.3.1 DICOM 1.2.840.10008.1.2 SCU None
Only Information Implicit VR
Patient Study 1.2.840.10008.5.1.4.1.2.3.2 DICOM 1.2.840.10008.1.2 SCU None
Only Information Implicit VR
3.2.2.2.2.1 SOP Specific Conformance  Find SOP Classes
The Query/Retrieve AE does not support any Optional Keys and does not generate Relational-queries.
If more than one information model is negotiated on an association, and it is possible to use
more than one of the negotiated information models to form a query, the following information
model will be used (in order of preference):
1. Study Root Information Model

2. Patient Root Information Model
3. Patient/Study Only Information Model
3.2.2.2.2.2 SOP Specific Conformance  Move SOP Classes
Standard conformance to the C-MOVE service is provided.
The Query/Retrieve AE accepts associations only if they have valid presentation contexts. It
can be configured to only accept associations with certain hosts. The Query/Retrieve AE
places configurable limitations on the number of simultaneous connections it will support. Once
the Query/Retrieve AE accepts an association, a spawned child process will receive any
images transmitted on that association and store them on the hard disk in a format required by
the ALI UltraPACS system.

3.2.3.1 Real-World Activity  External system queries ALI UltraPACS
When an external system requests an association with the Query/Retrieve AE to retrieve a

worklist, query ALI UltraPACS’ database, or to retrieve images, a child process is spawned to
process the query and to retrieve any requested images.
3.2.3.1.2 Presentation Context Table

Negot-
iation
Verification 1.2.840.10008.1.1 DICOM 1.2.840.10008.1.2 SCP None
Implicit VR
Little Endian
Patient Root 1.2.840.10008.5.1.4.1.2.1.1 DICOM 1.2.840.10008.1.2 SCP None
Q/R Implicit VR
Information Little Endian
Model - FIND
Q/R Implicit VR
Model - MOVE
Q/R Implicit VR
Model - GET
Study Root 1.2.840.10008.5.1.4.1.2.2.1 DICOM 1.2.840.10008.1.2 SCP None
Q/R Implicit VR
Model - FIND
Q/R Implicit VR
Model - MOVE
Q/R Implicit VR
Model - GET
Patient Study 1.2.840.10008.5.1.4.1.2.3.1 DICOM 1.2.840.10008.1.2 SCP None
Only Implicit VR
Model - FIND
Only Implicit VR
Model - MOVE


Nego-
tiation
Only Implicit VR
Model - GET
Modality 1.2.840.10008.5.1.4.31 DICOM 1.2.840.10008.1.2 SCP None
Worklist Implicit VR
Little Endian
3.2.3.1.2.1 SOP Specific Conformance - Verification
Standard conformance is provided to the DICOM Verification Service Class as an SCP.
3.2.3.1.2.2 SOP Specific Conformance  FIND SOP Classes
The Query/Retrieve AE supports hierarchical queries and not relational queries. No optional
keys are supported, except for the Operators’ Name attribute, (0008,1070), on the series level.
The Operators’ Name attribute is supported on an existence basis and not on a matching
basis, i.e. the value specified to be matched for the Operators’ Name is ignored but a value
may be returned. The Study ID attribute (0020,0010) is not properly supported as it is not
stored in the ALI UltraPACS database. If query identifiers contain this attribute its value will be
ignored. All query responses will leave this attribute empty if its value is queried for.
Patient Root Information Model

With the exception of the Study ID attribute, all required search keys on each of the four levels
(Patient, Study, Series, and Image) are supported. However, the Patient ID (0010,0020) key
must be fully stated if the Patient’s Name (0010,0010) is not present in the query (e.g.
ALI UltraPACS does not support queries for patients having the patient id of “123*” when this
is the only search criterion).
Study Root Information Model

With the exception of the Study ID attribute, all the required search keys on each of the three
levels (Study, Series, and Image) are supported. There is, however, a caveat that applies to
the Study Time (0008,0030) and Accession Number (0008,0050) keys; they cannot be used as
the only search keys on the study level. If they are used in conjunction with the other
supported search keys on the study level, they can be used in the matching criteria.
Patient/Study Only Information Model

With the exception of the Study ID attribute, all the required search keys on the Patient and
Study levels are supported. The Patient ID (0010,0020) key must be fully stated if the
Patient’s Name (0010,0010) is not present in the query.
Modality Worklist Information Model

Matching on Optional Matching Keys is not supported. Type 3 Return Keys are not supported.

External Query/Retrieve SCU’s should be aware that when a DICOM object is sent to the ALI
UltraPACS Storage AE, that object can later be queried with a C-FIND operation down to the
image level, but information on the series and image levels will be coerced by ALI UltraPACS.
Thus, if an external DICOM device sends an object to ALI UltraPACS and then later queries for
that object, the series and image level information returned by the query may be different than
the information contained in the original object sent to ALI UltraPACS. The received DICOM
objects are, however, stored with their original content off-line in archive.
Query/Retrieve AE returns one of the following status codes in a C-FIND response:

A700 (Out of Resources)
System reached the limit in disk space or memory usage.
A900 (Identifier does not match SOP Class)

A request was made for something that did not match the specified SOP Class.
C001 (Unable to process)

Request cannot be processed.
FE00 (Matching terminated due to Cancel Request)

Requester canceled operation.
0000 (Success)
Matching is complete.
FF00 (Pending)
Matches are continuing and current match is supplied.
FF01 (Pending)
Matches are continuing but one or more Optional Keys were not supported.
3.2.3.1.2.3 SOP Specific Conformance - MOVE SOP Classes
The Query/Retrieve AE will try to establish an association with a DICOM Application Entity
named by the external C-MOVE SCU (through a MOVE Destination AE Title) to perform C-
STORE operations on requested images. One or more of the Image Storage SOP Classes
listed in Table 5 will be negotiated.
The Query/Retrieve AE will return a response to the C-MOVE SCU after each image has been
sent. This response reports the number of remaining images to transfer, as well as the
number of images transferred having a successful, failed, or warning status.
Query/Retrieve AE returns one of the following status codes in a C-MOVE response:

Number of matches cannot be determined due to system failure.

C-STORE sub-operations cannot be performed.

A801 (Move destination unknown)

Application Entity named in request is unknown to Query/Retrieve AE.



B000 (Sub-operations complete)

A warning indicating that all sub-operations are complete, but one or more failures or
warnings have occurred.
0000 (Success)
Matching is complete. No failures.
FF00 (Pending)
Sub-operations are continuing.
3.2.3.1.2.1 SOP Specific Conformance - GET SOP Classes
The supported Storage Service Class SOP Classes used to perform the C-STORE sub-
operations are listed in Table 5. The appropriate presentation context must be negotiated by
the Query/Retrieve SCU in order for the requested images to be retrieved. This presentation
context must be negotiated when the C-GET SCU initiates the association to query the
Query/Retrieve AE.
The Query/Retrieve AE will return a response to the C-GET SCU after each image has been
sent. This response reports the number of remaining images to transfer, as well as the number
of images transferred having a successful, failed, or warning status.
Query/Retrieve AE returns one of the following status codes in a C-GET response:

Number of matches cannot be determined due to system failure.

C-STORE sub-operations cannot be performed.




B000 (Sub-operations complete)

A warning indicating that all sub-operations are complete, but one or more failures or
warnings have occurred.
0000 (Success)
Matching is complete.
FF00 (Pending)
Sub-operations are continuing.
3.2.3.1.3 Presentation Context Acceptance Criteria
The Query/Retrieve AE will only accept the Presentation Contexts specified in Table 9. The
Query/Retrieve AE can be configured to reject valid Presentation Contexts if the external
DICOM host is not listed in configuration. In addition, a valid Presentation Context can be
rejected if the maximum limit on the number of simultaneous processes has been reached.
3.2.3.1.4 Transfer Syntax Selection Policies
The Query/Retrieve AE only supports the Implicit VR Little Endian transfer syntax. Any
proposed Presentation Context which includes the Implicit VR Little Endian transfer syntax will
be accepted with the Implicit VR Little Endian transfer syntax. Any proposed Presentation
Context that does not include the Implicit VR Little Endian transfer syntax will be rejected.
3.3 Print Management AE
The Print Management AE provides Standard Conformance to the following Meta SOP
Classes as an SCU:
Table 10: SOP Class Conformance as an SCU

Basic Grayscale Print Management 1.2.840.10008.5.1.1.9
Basic Color Print Management 1.2.840.10008.5.1.1.18
This corresponds to conformance to the following SOP classes as an SCU:
Table 11: SOP Class Conformance as an SCU

Basic Film Session 1.2.840.10008.5.1.1.1
Basic Film Box 1.2.840.10008.5.1.1.2
Basic Grayscale Image Box 1.2.840.10008.5.1.1.4
Basic Color Image Box 1.2.840.10008.5.1.1.4.1

3.3.1.1 General
Every print job will initiate an association. The general order in which operation will be made is
as follows:
Association Negotiated
N-GET of Printer SOP Instance to determine printer status
N-CREATE of Film Session SOP Instance
For each film box in job
{
N-CREATE of Film Box SOP Instance
For each image in film box
{
N-SET of Image Box SOP Instance
}
N-ACTION of Film Box SOP Instance
N-DELETE of Film Box SOP Instance
}
Release Association
The maximum PDU size that will be offered is 16,384 bytes.
At most one association will be processed at a time.
Multiple outstanding transactions is not supported.
The implementation class UID used is “1.2.840.113711.2”. The implementation version name
is set at installation time through configuration.
3.3.2.1 Association Initiation by Real-World Activity
3.3.2.2 Associated Real-World Activity - User submits print job
3.3.2.3 Associated Real-World Activity
An association is initiated with the named DICOM printer when an ALI UltraPACS user selects
images to be printed and submits the list of images to the Print Management AE.


Negot-
iation
Basic Grayscale 1.2.840.10008.5.1.1.9 DICOM 1.2.840.10008.1.2 SCU None
Print Management Implicit VR
Little Endian
Basic Color Print 1.2.840.10008.5.1.1.1 DICOM 1.2.840.10008.1.2 SCU None
Management 8 Implicit VR
Little Endian
3.3.2.1.2.1 SOP Specific Conformance - Basic Print Management
Standard conformance is provided to the Basic Grayscale and Basic Color Print Management
Meta SOP Classes as an SCU. All mandatory elements for film sessions, basic film boxes,
and basic Grayscale image boxes are provided. The User Optional attributes that can be set
are listed below:
Table 13: Optional Attributes Set for Film Sessions
Name Tag Possible Values
Number of Copies (2000,0010) Any non-negative integer
Print Priority (2000,0020) HIGH, MED, LOW
Medium Type (2000,0030) PAPER, CLEAR FILM, BLUE FILM
Film Destination (2000,0040) MAGAZINE, PROCESSOR
Table 14: Optional Attributes Set for Film Boxes

Film Orientation (2010,0040) PORTRAIT, LANDSCAPE
Film Size ID (2010,0050) 8INX10IN, 10INX12IN, 10INX14IN,
11INX14IN, 14INX14IN, 14INX17IN,
24CMX30CM, 24CMX24CM
Magnification Type (2010,0060) REPLICATE, BILINEAR, CUBIC,
NONE
Smoothing Type (2010,0080) values depend on printer
Empty Image (2010,0010) BLACK, WHITE
Density
Min Density (2010,0120) nnn
Max Density (2010,0130) nnn
Trim (2010,0140) YES, NO
Configuration (2010,0150) values depend on printer
Information

Table 15: Optional Attributes Set for Image Boxes

Magnification Type (2010,0060) REPLICATE, BILINEAR, CUBIC,
NONE
Smoothing Type (2010,0080) values depend on printer
Polarity (2020,0020) NORMAL, REVERSE
Requested Image Size (2020,0030) values depend on printer
The Print Management AE does not accept associations.
4.0 Communication Profiles
4.1 Supported Communication Stacks
ALI UltraPACS’ DICOM AEs provide DICOM 3.0 TCP/IP Network Communication Support as
defined in Part 8 of the DICOM Standard.
4.2 TCP/IP
ALI UltraPACS’ DICOM AEs inherit their TCP/IP stack from the UNIX system upon which they
execute.
4.2.1 Physical Media Support
ALI UltraPACS’ DICOM AEs are indifferent to the physical medium over which TCP/IP
executes as they inherit this support from the UNIX system upon which they execute.
5.0 Extensions/Specializations/Privatizations
Not applicable.
6.0 Configuration
6.1 AE Title/Presentation Address Mapping
The mapping from AE Title to TCP/IP addresses and ports is configurable and set at the time
of installation by ALI Installation Personnel.
6.2 Configurable Parameters
The following items are configurable:

For AEs running as SCPs, the maximum number of simultaneous associations.
The AE Title, ports of SCPs, implementation class UID, implementation version name.
Whether to accept associations from unspecified hosts.
A list of known external DICOM hosts.
The minimum disk space required to accept DICOM images.
7.0 Support for Extended Character Sets
No support for Extended Character Sets.


95-10551 Shellbridge Way, Richmond, BC Canada V6X 2W9
A.L.I. Imaging Systems Corp.

720 Olive Way, Suite 1020, Seattle, WA, USA 98101
Tel: (800) 661-5885 / Fax: (800) 261-5432


Ali Pacs

Uploaded by

Copyright:

Available Formats

Ali Pacs

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ali Pacs

Uploaded by

Copyright:

Available Formats

DICOM CONFORMANCE STATEMENT

A.L.I. Technologies Inc.

A.L.I. Imaging Systems Corp.

A.L.I. Technologies Inc.

2.0 Implementation Model......................................................................................... 1

A.L.I. Technologies Inc.

3.2.3.1.2 Presentation Context Table .............................................................................. 16

4.0 Communication Profiles .................................................................................... 23

5.0 Extensions/Specializations/Privatizations ......................................................... 23

6.0 Configuration .................................................................................................... 23

7.0 Support for Extended Character Sets ............................................................... 24

A.L.I. Technologies Inc.

Document Date Author Description

A.L.I. Technologies Inc.

2.0 Implementation Model

2.1 Application Data Flow Diagram

Figure 1 - ALI UltraPACS DICOM Data Flow Diagram

User requests Images received

List of scheduled Query/Retrieve Worklist is queried

User submits Database is queried

User submits Print Management

DICOM 3.0 Interface

A.L.I. Technologies Inc.

2.2 Functional Definitions of Application Entities

2.3 Sequencing of Real-World Events

A.L.I. Technologies Inc.

A.L.I. Technologies Inc.

Table 2: SOP Class Conformance as SCP

3.1.1 Association Establishment Policies

The maximum PDU size which will be offered is 16,386 bytes.

A.L.I. Technologies Inc.

3.1.1.2 Number of Associations

The Storage AE will initiate one association at any time.

3.1.1.3 Asynchronous Nature

3.1.1.4 Implementation Identifying Information

An implementation class UID of “1.2.840.113711.1” is provided. The implementation version

3.1.2 Association Initiation by Real-World Activity

3.1.3 Real-World Activity  User requests image transmission

3.1.4 Associated Real-World Activity

A.L.I. Technologies Inc.

3.1.2.1.2 Proposed Presentation Contexts

Table 3: Proposed Presentation Contexts

A.L.I. Technologies Inc.

3.1.2.1.2.1 SOP Specific Conformance  Storage

3.1.3 Association Acceptance Policy

3.1.3.1 Real-World Activity  External system requests storage of images

3.1.3.1.1 Associated Real-World Activity

Table 4: Significant Elements in Received Images

A.L.I. Technologies Inc.

Attribute Name Tag ID Significance

A.L.I. Technologies Inc.

3.1.3.1.2 Presentation Context Table

Abstract Syntax Transfer Syntax

A.L.I. Technologies Inc.

3.1.3.1.2.1 SOP Specific Conformance  Verification

3.1.3.1.2.2 SOP Specific Conformance  Storage

 If it is configured to convert incoming images to TIFF then it has Level 0 conformance to

 A700 (Out of Resources).

 B000 (Coercion of Data Elements).

If it is configured to convert incoming images to TIFF then it has Level 0 conformance to

A700 (Out of Resources).

B000 (Coercion of Data Elements).

A800 (SOP Class Not Supported).

A900 (Data Set does not match SOP Class).

C000 (Cannot understand)

A900 (Identifier does not match SOP Class)

C001 (Unable to process)

FE00 (Matching terminated due to Cancel Request)

A701 (Out of Resources)

A702 (Out of Resources)

A801 (Move destination unknown)

A900 (Identifier does not match SOP Class)

C001 (Unable to process)

FE00 (Matching terminated due to Cancel Request)

B000 (Sub-operations complete)

A701 (Out of Resources)

A702 (Out of Resources)

A900 (Identifier does not match SOP Class)

C001 (Unable to process)

FE00 (Matching terminated due to Cancel Request)

B000 (Sub-operations complete)