DICOM Conformance Statement ISite R4.1
DICOM Conformance Statement ISite R4.1
Statement
iSite PACS 4.1
CREF4.09-80
2011 Nov 23
CREF4.09-80
2011 Nov 23
Philips Healthcare
is part of
Royal Philips Electronics
www.medical.philips.com
[email protected]
North America
Philips Healthcare Informatics
4100 East Third Ave., Suite 101
Foster City, CA 94404
USA
Europe
Philips Medical Systems Nederland B.V.
PMS Quality & Regulatory Affairs Europe
Veenpluis 4-6
5684 PC Best
The Netherlands
Table of Contents
1 Introduction ................................................................................................................................. 1
2 Abbreviations and Symbols ...................................................................................................... 1
3 Implementation Model................................................................................................................ 2
3.1 Application Data Flow Diagram .................................................................................... 2
3.2 Functional Definitions of AEs ....................................................................................... 2
3.3 Sequencing of Real-World Activities ........................................................................... 3
4 AE Specifications ....................................................................................................................... 3
4.1 iSite DICOM Server Storage AE Specification ............................................................ 3
4.1.1 Association Establishment Policies .................................................................. 6
4.1.2 Association Initiation by Real-World Activity .................................................... 7
4.1.3 Association Acceptance Policy....................................................................... 26
4.1.4 iSite DICOM QRSCP AE Specification .......................................................... 83
4.1.5 Association Establishment Policies ................................................................ 83
4.1.6 Association Initiation by Real-World Activity .................................................. 84
4.1.7 Association acceptance policy ....................................................................... 84
4.1.8 C-FIND Conformance ..................................................................................... 85
4.1.9 C-MOVE Conformance................................................................................... 85
4.1.10 C-FIND Conformance ..................................................................................... 86
4.1.11 C-MOVE Conformance................................................................................... 86
4.1.12 C-FIND Conformance ..................................................................................... 87
4.1.13 C-MOVE Conformance................................................................................... 87
4.2 iSite Worklist Server AE Specification ...................................................................... 87
4.2.1 Association Establishment Policies ................................................................ 88
4.2.2 Association Initiation by Real-World Activity .................................................. 88
4.2.3 Association Acceptance Policy....................................................................... 88
4.3 iSite Radiology Client AE Specification .................................................................... 94
4.3.1 Association Establishment Policies ................................................................ 95
4.3.2 Association Initiation by Real-World Activity .................................................. 95
4.3.3 Association Acceptance Policy....................................................................... 97
5 Communication Profiles .......................................................................................................... 97
5.1 Supported Communication Stacks (Parts 8,9) ......................................................... 97
5.1.1 TCP/IP Stack .................................................................................................. 97
6 Extensions/Specializations/Privatizations............................................................................. 98
6.1 Standard Extended/Specialized/Private SOPs.......................................................... 98
6.2 Private Transfer Syntaxes ........................................................................................... 98
1 In tro d u c tio n
The Philips iSite Picture Archiving and Communication System (PACS) product is a medical
image and information distribution system designed for integration into a medical institution’s
existing healthcare network. The product utilizes the medical industry standard DICOM 3.0
protocol to exchange information with other DICOM compliant devices on the network. The
primary use of the DICOM protocol within the iSite product is for local and remote storage of
images, remote printing of images, remote query of image storage related information and
local query of modality worklist information.
2 Ab b re via tio n s a n d S ym b o ls
Frequently used abbreviations or acronyms in this document are defined in the table below.
All other abbreviations are defined at its first use in this document by the abbreviation
followed by its full meaning enclosed in parentheses.
Term Meaning
AE Application Entity
CT Computed Tomography
MR Magnetic Resonance
RT Radiotherapy
VR Value Representation
3 Im p le m e n ta tio n Mo d e l
The iSite system consists of integrated client and server applications within the Philips
product line. This system provides DICOM compliant interfaces for Storage, Verification,
Query/Retrieve, Printing and Modality Worklist services.
3.1 Ap p lic a tio n Da ta Flo w Dia g ra m
The iSite DICOM Server, iSite Worklist Server, and iSite Radiology Client Application Entities
are all integrated parts of the iSite product.
DICOM Standard Interface
Remote
System
Requests
Image Storage
Converted and Commitment
Stored at
Normal Priority
Remote
System
Requests
MPPS
Image
Converted and
Stored at High
Priority
Remote
System
Requests
Normal Priority
Image Storage
iSite Client
Queries
Remote
DICOM Device Remote
System
Requests High
Priority Image
Storage
iSite DICOM
iSite DICOM Server
Server
Performs
Prefetch Remote
Operation System
Responds to
DICOM Query/
Retrieve
Requests
iSite Client
Request
Remote Image
Storage Image Stored
on Remote
DICOM
System
DICOM
Service Remote
Verified System
Requests
DICOM
Verification
iSite Worklist Server Service
Remote
User Requests
System Prints
DICOM Image iSite Radiology Client
DICOM
Printing
Images
DICOM associations by the iSite DICOM Server to remote DICOM devices for Storage and
Query/Retrieve services.
The iSite Worklist Server runs as a Windows 2003 Server service and will be automatically
started as part of the operating system. Once started, the iSite Worklist Server will wait for
another application to connect to it DICOM Modality Worklist service at the presentation
address configured.
The iSite Radiology Client will initiate DICOM associations for DICOM Printing services on
an as needed basis dependent upon interactive requests from users of the system.
4 AE S p e c ific a tio n s
4.1.1.1 Ge n e ra l
The iSite DICOM Server application will request associations and accept associations for
DICOM Storage and Query/Retrieve. The iSite DICOM Server application supports a
maximum PDU size of 63KB.
4.1.1.2 Nu m b e r o f As s o c ia tio n s
The iSite DICOM Server application supports the initiation of a configurable number of
simultaneous associations. The default is “3” for Storage Service related transactions and “1”
for Query/Retrieve Service related transactions.
The iSite DICOM Server application has no configurable upper limit on the number of
simultaneous associations that it will accept. The upper limit of accepted associations is
limited by the hardware platform and overall system performance requirements.
4.1.1.3 As yn c h ro n o u s Na tu re
The iSite DICOM Server application does not support negotiation of multiple outstanding
transactions.
SOP Specific Conformance Statement for SOP Class 'Patient Root Query/Retrieve
Information Model - FIND'
All DICOM attributes specified as valid keys for C-FIND messages are legal for Philips iSite
Server query keys as well. In practice, the set actually used is defined by client-side requests
so only a pertinent subset would be used. Table 4 lists the essential tags that Philips iSite
Server will expect any Query/Retrieve SCP to support for the Patient Root Information
Model.
SOP Specific Conformance Statement for SOP Class “Study Root Query/Retrieve
Information Model – FIND"
All DICOM attributes specified as valid keys for C-FIND messages are legal for Philips iSite
Server query keys as well. In practice, the set actually used is defined by client-side requests
so only a pertinent subset would be used. Table 5 lists the essential tags that Philips iSite
Server will expect any Query/Retrieve SCP to support for the Study Root Information Model.
Ta b le 5: DICOM d a ta e le m e n ts s u p p o rte d fo r S OP Cla s s ‘S tu d y Ro o t Qu e ry/Re trie ve
In fo rm a tio n Mo d e l - FIND'
The accepted presentation contexts for DICOM storage Server are the same as listed in
Table 7.
Modification of data elements is initiated either by processing of manual edits initiated by end
users of the system or automatic edits initiated by information received from ADT and Order
Entry systems (HIS/RIS).
Depending upon the system configuration, the iSite DICOM Server application either
performs “lifetime” persistence for the Images received or manages an auto-deleted cache of
the most recently active image studies. In the cache storage mode, images received will be
deleted when the server disk space becomes full. Deletion will be performed based on a
“least accessed patient” strategy. If an iSite client has accessed any part of a patient’s
studies, all images associated with that patient have a lower probability of being deleted.
The iSite Server application entity returns the status code of “0” if the receipt of a C-STORE
message was successful, otherwise it returns one of the following codes:
Ta b le 10: C-S to re Me s s a g e Co d e s
A700 Out of Resources There is insufficient storage in the server. Try again later.
A800 Illegal SOP Class SOP class that was not negotiated was received.
A900 Data mismatch Missing type 1 or type 2 data element was detected, or other
incorrect encoding in the DICOM data stream.
C000 Cannot understand Part of the data could not be parsed. This usually indicates a
serious DICOM encoding error in the SCU implementation or
data stream corruption.
Forwarding MPPS
The MPPS messages are forwarded as received; certain forwarding information is stored in
the message as private Tags.
4.1.5.1 Ge n e ra l
The QRSCP will listen for an association as an SCP for the Query/Retrieve SOP Class. The
default maximum PDU size is 64512.
4.1.5.2 Nu m b e r o f As s o c ia tio n s
The number of threads available to process associations is configurable, and defaults to five
(5) threads. The number of simultaneous associations that can be serviced is unlimited, but
performance will degrade proportionally to the number of simultaneous associations and the
average activity per association. Higher performance can be achieved by increasing the
number of processors, threads, and memory.
4.1.5.3 As yn c h ro n o u s Na tu re
Multiple transactions on a single association are not supported.
Ta b le 16: P re s e n ta tio n Co n te xt
4.1.8 C-FIND Co n fo rm a n c e
4.1.9 C-MOVE Co n fo rm a n ce
The QRSCP does not perform C-STORE operations; an internal protocol is used to trigger
these operations on the iSite server AE. The supported Storage Service Class SOP Classes
for C-MOVE are the same as those supported by the iSite server AE, and are covered in a
separate conformance document.
C-MOVE pending response messages are sent by QRSCP at a configurable interval, and
always indicate the number of remaining, successful, failed, or warning sub-operations.
Multiple series support
Multiple series (in "Series Instance UID" (0020,000E) tag) are not supported.
4.1.10 C-FIND Co n fo rm a n c e
4.1.11 C-MOVE Co n fo rm a n ce
The QRSCP does not perform C-STORE operations; an internal protocol is used to trigger
these operations on the iSite server AE. The supported Storage Service Class SOP Classes
for C-MOVE are the same as those supported by the iSite server AE, and are covered in a
separate conformance document.
C-MOVE pending response messages are sent by QRSCP at a configurable interval, and
always indicate the number of remaining, successful, failed, or warning sub-operations.
Presentation context acceptance criterion for Find and Move commands
All presentation contexts listed in Table 16 will be accepted.
Transfer syntax selection policies for Find and Move commands
Proposed transfer syntaxes are selected in the following order:
1. Explicit VR Little Endian - 1.2.840.10008.1.2.1
2. Explicit VR Big Endian – 1.2.840.10008.1.2.2
4.1.12 C-FIND Co n fo rm a n c e
4.1.13 C-MOVE Co n fo rm a n ce
The QRSCP does not perform C-STORE operations; an internal protocol is used to trigger
these operations on the iSite server AE. The supported Storage Service Class SOP Classes
for C-MOVE are the same as those supported by the iSite server AE, and are covered in a
separate conformance document.
C-MOVE pending response messages are sent by QRSCP at a configurable interval, and
always indicate the number of remaining, successful, failed, or warning sub-operations.
Presentation context acceptance criterion for Find and Move commands
All presentation contexts listed in this document will be accepted.
Transfer syntax selection policies for Find and Move commands
Proposed transfer syntaxes are selected in the following order:
1. Explicit VR Little Endian - 1.2.840.10008.1.2.1
2. Explicit VR Big Endian – 1.2.840.10008.1.2.2
3. Implicit VR Little Endian – 1.2.840.10008.1.2
4.2.1.1 Ge n e ra l
The iSite Worklist Server supports the acceptance of DICOM associations for the DICOM
Modality Worklist Service and the DICOM Verification Service. The iSite Worklist Server
application supports a maximum PDU size of 30KB with a default of 16KB.
4.2.1.2 Nu m b e r o f As s o c ia tio n s
The iSite Worklist Server application has no configurable upper limit on the number of
simultaneous associations that it will accept. The upper limit of accepted associations is
limited by the hardware platform and overall system performance requirements.
4.2.1.3 As yn c h ro n o u s Na tu re
The iSite Worklist Server application does not support negotiation of multiple outstanding
transactions.
Please note that the configuration of querying AE titles restrict the max results to user
specified value. Also, if the incoming query does not restrict on date, the system
automatically narrows the open ended query to a span of 24 hours before and 4 hours
ahead of the current time. This is a window of 28 hours total, and the time used is the
time the DMWL query was performed. A consequence of this behavior is that if the
Scheduled Procedure Step Start Date is empty in the query, the system automatically
fills in a start and end date if requested in the query.
iSite does not support the query matching using the wild character ‘?’, it does however
support ‘*’
Ta b le 23: S u p p o rte d Ma tc h in g a n d Re tu rn Ke ys
Specific Character Set (0008,0005) O 1C Note: This attribute is omitted from the return
data sets because expanded or replacement
character sets are not used.
>Scheduled Procedure (0040,0002) R 1 Scheduled Step Start Date shall be retrieved with
Step Start Date Single Value Matching or Range Matching. See
remark under Scheduled Procedure Step Start
Time (0040,0003).
>Scheduled Procedure (0040,0003) R 1 Scheduled Step Start Time shall be retrieved with
Step Start Time Single Value Matching or Range Matching.
Scheduled Step Start Date and Scheduled Step
Start Time are subject to Range Matching. If both
keys are specified for Range Matching, e.g. the
date range "July5\July 7" and the time range
"10am\6pm" specifies the time period starting on
July 5, 10am until July 7, 6pm.
>Scheduled Procedure (0040,0011) O 2 Note: Supported, but will always be returned with
Step Location zero length
>Scheduled Procedure (0040,0009) O 1 Note: Value of this Attribute will always be equal
Step ID to that of Requested Procedure ID (0040,1001)
Requested Procedure
Referenced Study (0008,1110) O 2 Note: Supported, but the Sequence will always
Sequence be returned without Items in it
Requested Procedure (0040,1003) O 2 Note: Supported, but will always be returned with
Priority zero length
Accession Number (0008,0050) O 2 Note: Supported and will always be returned with
non-zero length
Visit Identification
Visit Status
All other Attributes from the Visit Status O 3 Note: Not Supported
Module
Visit Relationship
Visit Admission
Patient Relationship
Patient Identification
Patient's Name (0010,0010) R 1 Patient Name shall be retrieved with Single Value
Matching or Wild Card Matching.
Patient Demographic
Patient Medical
All other Attributes from the Patient Medical O 3 Note: Not Supported
Module
If the database query was unsuccessful, MWS responds to the modality with C-FIND-RSP
message conveying failure status of the operation (Status Attribute (0000,0900) with value
0xC001). It will also return Success and Pending status codes while returning information to
the modality (see Table 24).
Ta b le 24: MWS Re tu rn S ta tu s Co d e s
Pending Matches are continuing - Warning that one or more FF01 Identifier
Optional Keys were not supported for existence for
this Identifier.
4.3.1.1 Ge n e ra l
The Radiology Client will initiate DICOM associations for the DICOM Basic Printing Service
and the DICOM Verification Service. The iSite Radiology Client application supports a
maximum PDU size of 28K.
4.3.1.2 Nu m b e r o f As s o c ia tio n s
The iSite Radiology Client application only initiates a single associated at a time for the
DICOM Basic Printing Service.
4.3.1.3 As yn c h ro n o u s Na tu re
The iSite Radiology Client application does not request multiple outstanding transactions.
5 Co m m u n ic a tio n P ro file s
5.1.1.1 AP I
The Philips iSite server inherits its TCP/IP stack from Microsoft Windows2000Server
operating system (Winsock 2).
5.1.1.2 P h ys ic a l Me d ia S u p p o rt
While there are no theoretical differences in the choice of the physical media for TCP/IP
networking, the Philips iSite server platform has been quality assurance tested to work with
10 and 100 Base-T Ethernet media. Therefore, Philips recommends the use of these media
as the primary point of delivering the network traffic to the server platform.
7 Co n fig u ra tio n
Only an authorized Philips technical support representative will configure the DICOM
features.
8 S u p p o rt o f Exte n de d Ch a ra c te r S e ts
None
9 Co d e s a n d Co n tro lle d Te rm in o lo g y
None
10 S e c u rity P ro file s
None