Documente Academic
Documente Profesional
Documente Cultură
0
CONFORMANCE
STATEMENT
- Pegasys
ADAC
®
ADAC Laboratories
Copyright Statement
ADAC® has taken care to ensure the accuracy of this document. However, ADAC®
assumes no liability for errors or omissions and reserves the right to make changes
without further notice to any products herein to improve reliability, function, or
design. ADAC Laboratories provides this guide without warranty of any kind, either
implied or expressed, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. ADAC® may make improvements
or changes in the product(s) and/or program(s) described in this manual at any time.
ADAC Laboratories reserves the right to revise this publication and to make changes
in content from time to time without obligation on the part of ADAC Laboratories to
provide notification of such revision or change.
Disclaimer
The ADAC® DICOM software is in compliance with the ACR-NEMA DICOM 3.0
standard; however, due to the inherent nature of DICOM, the user must perform
acceptance testing to verify that the ADAC DICOM software meets the requirements
for your configuration. The acceptance testing must include all representative datasets
(images) that you intend to transfer, all types of transfers desired for a type of dataset,
and clinical evaluation of each representative dataset on the receiving end after each
desired type of transfer. For further information on conformance of this product to the
DICOM 3.0 standard, please refer to the DICOM 3.0 Conformance Statement -- Pegasys,
ADAC P/N 9605-0132.
Trademarks
ADAC®, CPET® Imaging System, CPET® Plus Imaging System, ForteTM, CardioTM,
CardioTM 60, GLOBALQ®, Solus, VERTEXTM, VERTEXTM Plus, VERTEXTM 60, EPIC,
PEGASYSTM, PEGASYSTMX, PEGASYSTMMD, PEGASYSTMMD+, PEGASYSTM Ultra and
Atlas are trademarks or registered trademarks of ADAC Laboratories.
Copyright 2001, ADAC Laboratories, 540 Alder Drive, Milpitas, CA, 95035, USA
TABLE OF CONTENTS
INTRODUCTION .......................................................................................................................1
Scope ..........................................................................................................................................1
Important Notes .........................................................................................................................1
Why Conformance Statement .....................................................................................................1
Source of Information .................................................................................................................2
How DICOM works in ADAC Pegasys ..........................................................................................2
Implementation Model ......................................................................................................................4
Application Data Flow Diagram ...................................................................................................4
Functional Definitions of AE (Application Entities) ........................................................................6
Sequencing of Real-world Activities ...................................................................................................8
Network Interchange AE Specifications ..............................................................................................8
Supported SOP Classes ...............................................................................................................8
Association Establishment Policies .............................................................................................10
Association Acceptance Policy ...................................................................................................11
Communication Profiles ............................................................................................................17
Media Interchange Application Entities Specification .......................................................................18
Deviation Report .............................................................................................................................19
Extensions, Specialization, Privatizations ....................................................................................19
Support of Extended Character Sets ..........................................................................................19
ADAC Pegasys Private Group ...........................................................................................................19
Configuration ..................................................................................................................................19
Comments ......................................................................................................................................21
9605-0132 REV B # 2.0 November, 2001 DICOM 3.0 Conformance Statement - Pegasys ■ 1
Table of Contents
2 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001
INTRODUCTION
INTRODUCTION
Scope
This document states the conformance of ADAC Pegasys family Nuclear Medicine
products to DICOM 3.0 standard. It only applies to Pegasys DICOM software version
3.0 or higher. The DICOM conformance of other medical devices manufactured by
ADAC Laboratories is detailed in separate documents.
Important Notes
The ADAC DICOM software is in compliance with ACR-NEMA DICOM 3.0 standard;
however, due to the inherent nature of DICOM, the user must perform acceptance
testing to verify that the ADAC DICOM software meets requirements for their
configuration. The acceptance testing should include all representative datasets
(images) that the user intends to transfer, all types of transfers desired for a type of
dataset, and clinical evaluation of each representative dataset on the receiving end
after the transfer of the desired type. Please read the following sections carefully prior
to using any of the DICOM software products.
Because of the broadness and extensibility of the DICOM standard, each DICOM
conforming system would normally support only a subset of DICOM 3.0. Each pair of
DICOM peer devices, or Application Entities (AE), can only communicate over the
intersection of commonly supported parts of DICOM. Fortunately, DICOM 3.0
standard requires some minimum conformance.
This conformance statement can help the user understand the level of connectivity
between ADAC Pegasys and other DICOM compatible devices
9605-0132 REV B # 2.0 November 2001 DICOM 3.0 Conformance Statement - Pegasys ■ 1
INTRODUCTION
Source of Information
■ Digital Imaging and Communication in Medicine (DICOM), NEMA Standards
Publication No. PS 3.1~3.9.
NEMA Publication, 2101 L St., N.W., Washington, D.C. 20037, phone: (202)-
457-8474
■ Digital Imaging and Communication in Medicine (DICOM), supplements and
drafts, PS 3.1~3.13.
Internet ftp site: ftp.xray.hmc.psu.edu, /pub/dicom
NEMA contact: Dave Snavely, (202)-457-1965
The following table in the next page describes the DICOM Service Classes and
DICOM Commands supported by ADAC Pegasys DICOM.
2 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001
How DICOM works in ADAC Pegasys
◆archiving
Patient management N-EVENT-REPORT HIS/RIS applications:
N-GET
N-SET ◆ create patient record
◆ schedule visit
◆ admit patient
◆ transfer patient
◆ discharge patient
◆ perform study
◆ read study
◆ approve results
◆ record amendment
◆ transcribe amendment
◆ approve amendment
9605-0132 REV B # 2.0 November 2001 DICOM 3.0 Conformance Statement - Pegasys ■ 3
Implementation Model
Implementation Model
Verification
DICOM interface
C-ECHO-RQ “ping”
Pegasys Foreign host
C-ECHO-RSP “echo” DICOM
DICOM
C-ECHO-RQ “ping”
Pegasys Foreign host
C-ECHO-RSP “echo” DICOM
DICOM
DICOM interface
C-STORE-RQ “put”
Pegasys Foreign host
C-STORE-RSP“acknowledge” DICOM
DICOM
4 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001
Application Data Flow Diagram
Query/Retrieve
DICOM Interface
DICOM Interface
DICOM Printing
DICOM Interface
Pegasys
DICOM printer
“print-SCU
print-SCP
DICOM
9605-0132 REV B # 2.0 November 2001 DICOM 3.0 Conformance Statement - Pegasys ■ 5
Implementation Model
Pegasys
CD-R or
DICOM File-Set-Updater “write”
disk directory
Exporter
Pegasys
DICOM File-Set-Reader “read” CD-ROM or
disk directory
Importer
B Pegasys provides bi-directional image data transfer capabilities with foreign NM, CT,
MRI, PACS and other imaging systems. Data imported which are not Nuclear
Medicine IOD will be exported using the NM IOD or SC IOD.
6 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001
Functional Definitions of AE (Application Entities)
1. “query” Pegasys patient database from a remote system and select patient/image
data for transfer.
In this case, the DICOM Query/Retrieve information model is used on the
remote system. The Pegasys DICOM server uses the SCP role of C-FIND to
respond to the query and uses SCU role of Storage service class to send the
image data. This will only work with a remote AE that supports the SCU role
Query/Retrieve and SCP role of the Storage service class.
C Image data can also be interchanged via DICOM removable media, such as a CD-R.
9605-0132 REV B # 2.0 November 2001 DICOM 3.0 Conformance Statement - Pegasys ■ 7
Sequencing of Real-world Activities
8 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001
Supported SOP Classes
a. This SOP Class has been officially retired from the DICOM standard.
b. This SOP Class for the new NM IOD has officially become part of the DICOM
standard since December 1995
9605-0132 REV B # 2.0 November 2001 DICOM 3.0 Conformance Statement - Pegasys ■ 9
Network Interchange AE Specifications
Some interactions, such as C-STORE, may require a series of packet exchanges. The
following are the general rules for transfer:
■ The association (connection) remains open until all the data are transferred.
■ The maximum PDU (Protocol Data Unit) size is user configurable. The default
maximum is 16384 8-bit bytes.
Number of Associations
■ Each SCU role client application, such as “DICOM Import”, will only maintain
one association at a time.
■ Multiple SCU role client applications, or multiple instances of the same appli-
cation, can be run at the same time, each having an association.
■ The SCP role of DICOM server accepts one association at a time but can maintain
multiple associations at the same time.
Asynchronous Nature
Pegasys DICOM will not perform asynchronous operations window negotiation.
10 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001
Association Acceptance Policy
ADAC will use UID’s with an ANSI-registered <org root> numeric root in a future
release.
9605-0132 REV B # 2.0 November 2001 DICOM 3.0 Conformance Statement - Pegasys ■ 11
Network Interchange AE Specifications
■ Each active server listens to a TCP port. The default port number is DICOM regis-
tered number 104, unless otherwise configured,.
DICOM
Explicit VR
Big Endian
12 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001
Association Acceptance Policy
The supported query keys in each level are listed in Tables 9 through 11.
According to Section C.1 of PS 3.4 of the DICOM standard, matching values of keys is
done as follows:
■ For C-FIND, the server matches the values of the Required, Unique and Optional
keys of the current level and the unique keys of the previous level, and returns
the query result.
■ For C-MOVE, the server matches the values of the Unique keys of the current
level and the previous level.
Note: Wild cards are supported in both cases. Date and time ranges are not
supported in SCP of this release.
9605-0132 REV B # 2.0 November 2001 DICOM 3.0 Conformance Statement - Pegasys ■ 13
Network Interchange AE Specifications
Table 10: Supported Query Keys for Study Root Information Model
14 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001
Association Acceptance Policy
Table 11: Supported Query Keys for Patient/Study Only Information Model
9605-0132 REV B # 2.0 November 2001 DICOM 3.0 Conformance Statement - Pegasys ■ 15
Network Interchange AE Specifications
16 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001
Communication Profiles
Communication Profiles
The default connection port is the Ethernet. The serial/modem connection can be
used in conjunction with SLIP or PPP software.
Other commonly used networking media are Token Ring, FDDI, ATM, ISDN and
dedicated T1, T3 and other types of digital or digital/audio lines. These are transpar-
ently supported by DICOM but may require additional hardware/software and
expertise.
1. Although OSI is not directly supported, Pegasys can coexist with systems operating DICOM on OSI with
an additional OSI-TCP/IP gateway.
9605-0132 REV B # 2.0 November 2001 DICOM 3.0 Conformance Statement - Pegasys ■ 17
Media Interchange Application Entities Specification
Specification Comment
Identifier STD-GEN-CD
Information
Transfer Syntax and Rol
Object SOP Class UID
UID e
Definition
Basic 1.2.840.10008.1.3.10 Explicit VR Little Endian: FSR
Directory 1.2.840.10008.1.2.1
18 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001
Deviation Report
Deviation Report
In a typical case, the values of ADAC Pegasys Headers (0019, 0020) and Pixel Data
(7FE0, 0010) make up an original Pegasys image.
Configuration
Below is the list of currently seven DICOM configuration files in a Pegasys system.
■ dicompeers.cfg - used by server and client applications to identify remote
DICOM source and destination servers.
■ dicomethers.cfg - used by client applications to ensure globally unique identi-
fiers
9605-0132 REV B # 2.0 November 2001 DICOM 3.0 Conformance Statement - Pegasys ■ 19
Configuration
These are ASCII text files residing in $DATABASE_PATH. The user will use utility tools
with graphical user interface to do the configuration.
Highlight the original text and type the new port number. The port number must be
the same number used by the remote DICOM Server. Refer to the Site Survey for the
TCP Port number.
20 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001
Comments
Comments
■ The Nuclear Medicine IOD has been redefined. The new standard is published in
DICOM 3.0 Supplement 7. It is available for anonymous ftp at ftp.xray.hmc.psu.edu.
■ ADAC is an active member of the DICOM Ad-Hoc committee. ADAC plays a
leadership role in making DICOM a better standard.
■ ADAC implementation of DICOM will be synchronized with the latest DICOM
standard development at ACR-NEMA.
9605-0132 REV B # 2.0 November 2001 DICOM 3.0 Conformance Statement - Pegasys ■ 21
Comments
22 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001
Appendix
A GLOSSARY A
9605-0132 REV B # 2.0 November 2001 DICOM 3.0 Conformance Statement - Pegasys ■ A–1
Acronyms and Abbreviations
A–2 ■ DICOM 3.0 Conformance Statement - Pegasys 9605-0132 REV B # 2.0 November 2001