0% found this document useful (0 votes)

22 views

PHILIPS ESSENTA DICOM

Philips ESSENTA dicom

Uploaded by

Luis Fernando Garcia S

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

22 views

PHILIPS ESSENTA DICOM

Philips ESSENTA dicom

Uploaded by

Luis Fernando Garcia S

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 61

DICOM

Conformance Statement

ELEVA WORKSPOT 1.2

© Koninklijke Philips Electronics N.V.2007

All rights are reserved.
Issued by:
Philips Medical Systems Nederland B.V.
CTO/ C&S - Interoperability Competence Center

P.O. Box 10.000

5680 DA Best
The Netherlands
Email: [email protected]
Internet: http://www.medical.philips.com/connectivity

Document Number: XBS 231-060725

Date: 13 March 2007
DICOM Conformance Statement Page 3 of 61

1. DICOM C ONFORMANCE S TATEMENT O VERVIEW

This document is the DICOM Conformance Statement for the Philips Medical Systems
ELEVA WORKSPOT 1.2.

A table of Supported Networking DICOM Service (SOP) Classes is provided with roles
(User/Provider)

This document is the DICOM Conformance Statement for the Philips Medical Systems
ELEVA WORKSPOT 1.2. The ELEVA WORKSPOT 1.2 system is a modality for
directly acquiring digital radiography. (DICOM image type is ‘CR’). It contains an
export function based on the DICOM image storage to transfer image data from the
ELEVA WORKSPOT 1.2 system to a remote system. This DICOM export function and
other functions of ELEVA WORKSPOT 1.2 are described in this document.

ELEVA WORKSPOT 1.2 in a DICOM network

The figure below shows the position of ELEVA WORKSPOT 1.2 in a radiology
environment.

RIS Archive / IMS Printer

MWL Verification Store Print

MPPS
Verification

ELEVA WORKSPOT
- 1.2

BWLM Storage

MPPS Verification

Print Media (CD)

Figure 1: ELEVA WORKSPOT 1.2 in a DICOM network

ELEVA WORKSPOT 1.2 is an embedded modality system for DICOM images. It

provides, among other things, the following features:

• Verification of application level communication.

• Basic Worklist Management (BWLM).
• Storage of images on a remote DICOM system.
• Study Management per Modality Performed Procedure Step (MPPS).
• Printing of hardcopies on a remote DICOM printer.
• Storage of images per DICOM media (CD-R).

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 4 of 61

Table 1: Network Services

SOP Class User of Provider

Service of Service
Name UID (SCU) (SCP)

Other
Verification SOP Class 1.2.840.10008.1.1 No Yes
Print Management
Basic Grayscale Print Management 1.2.840.10008.5.1.1.9 Yes No
Meta SOP Class
>Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Yes No
>Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Yes No
>Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4 Yes No
>Printer SOP Class 1.2.840.10008.5.1.1.16 Yes No
Transfer
Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1 Yes No
SOP Class
Secondary Capture Image Storage SOP 1.2.840.10008.5.1.4.1.1.7 Yes No
Class
Workflow Management
Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3 Yes No
SOP Class
Modality Worklist Information Model - 1.2.840.10008.5.1.4.31 Yes No
FIND SOP Class
Storage Commitment Push Model SOP 1.2.840.10008.1.20.1 Yes No
Class

The services can be specified as a SCU, SCP or as an Option, which means that it is
either configurable or that it can be purchased separately.

Note: Verification SCU (C-ECHO) is supported, but is only available for the service
engineer during configuration. An auto configuration of a DICOM node using an A-
ASSOCIATE-RQ can be initiated as well.

A table of Supported Media Storage Application Profiles (with roles) is provided

Table 2: Media Services

Media Storage Application Profile Write Files (FSC or FSU) Read Files (FSR)

Compact Disk – Recordable

General Purpose CD-R Interchange Option Option

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 5 of 61

2. TABLE OF C ONTENTS
1. DICOM CONFORMANCE STATEMENT OVERVIEW ............................................................... 3
2. TABLE OF CONTENTS .............................................................................................................. 5
3. INTRODUCTION ......................................................................................................................... 7
3.1. REVISION HISTORY .............................................................................................................. 7
3.2. AUDIENCE.............................................................................................................................. 7
3.3. REMARKS .............................................................................................................................. 7
3.4. DEFINITIONS, TERMS AND ABBREVIATIONS ................................................................... 8
3.5. REFERENCES ........................................................................................................................ 9
4. NETWORKING .......................................................................................................................... 10
4.1. IMPLEMENTATION MODEL ................................................................................................ 10
4.1.1. Application Data Flow ....................................................................................................... 10
4.1.2. Functional Definition of AE’s ............................................................................................. 11
4.1.2.1. Functional Definition of ELEVA AE ................................................................................... 11
4.1.3. Sequencing of Real World Activities ................................................................................. 11
4.2. AE SPECIFICATIONS .......................................................................................................... 13
4.2.1. ELEVA AE ......................................................................................................................... 13
4.2.1.1. SOP Classes..................................................................................................................... 13
4.2.1.2. Association Policies .......................................................................................................... 13
4.2.1.2.1. General ......................................................................................................................... 13
4.2.1.2.2. Number of Associations................................................................................................ 13
4.2.1.2.3. Asynchronous Nature ................................................................................................... 14
4.2.1.2.4. Implementation Identifying Information......................................................................... 14
4.2.1.2.5. Communication Failure Handling ................................................................................. 14
4.2.1.3. Association Initiation Policy............................................................................................... 14
4.2.1.3.1. (Real-World) Activity – Print Management As SCU ..................................................... 17
4.2.1.3.2. (Real-World) Activity – Image Export ........................................................................... 23
4.2.1.3.3. (Real-World) Activity – Modality Performed Procedure Step as SCU.......................... 25
4.2.1.3.4. (Real-World) Activity – Modality worklist As SCU ........................................................ 30
4.2.1.3.5. (Real-World) Activity – Storage Commitment Push Model AS SCU ............................ 36
4.2.1.4. Association Acceptance Policy ......................................................................................... 39
4.2.1.4.1. (Real-World) Activity – Verification as SCP.................................................................. 41
4.3. NETWORK INTERFACES.................................................................................................... 43
4.3.1. Physical Network Interfaces.............................................................................................. 43
4.3.2. Additional Protocols .......................................................................................................... 43
4.4. CONFIGURATION ................................................................................................................ 43
4.4.1. AE Title/Presentation Address Mapping ........................................................................... 43
4.4.1.1. Local AE Titles .................................................................................................................. 43
4.4.1.2. Remote AE Title/Presentation Address Mapping ............................................................. 43
4.4.2. Parameters........................................................................................................................ 43
5. MEDIA INTERCHANGE............................................................................................................ 45
5.1. IMPLEMENTATION MODEL ................................................................................................ 45
5.1.1. Application Data Flow Diagram......................................................................................... 45
5.1.2. Functional Definitions of AE’s ........................................................................................... 45
5.1.2.1. Functional Definition of ELEVA WORKSPOT 1.2............................................................. 45
5.1.3. Sequencing of Real World Activities ................................................................................. 45
5.1.4. File Meta Information for Implementation Class and Version........................................... 46
5.2. AE SPECIFICATIONS .......................................................................................................... 47
5.2.1. ELEVA AE ......................................................................................................................... 47
5.2.1.1. Real-World Activities ......................................................................................................... 47
5.2.1.1.1. Display Directory........................................................................................................... 47
5.2.1.1.2. Write Images................................................................................................................. 47
5.3. AUGMENTED AND PRIVATE APPLICATION PROFILES ................................................. 47
5.3.1. Augmented Application Profiles ........................................................................................ 47
5.3.2. Private Application Profiles ............................................................................................... 48
5.4. MEDIA CONFIGURATION ................................................................................................... 48
6. SUPPORT OF CHARACTER SETS ......................................................................................... 49
7. SECURITY................................................................................................................................. 50

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 6 of 61

7.1.1. Secure Transport Connection Profiles .............................................................................. 50

7.1.1.1. The Basic TLS Secure Transport Connection Profile ....................................................... 50
7.1.2. Attribute Confidentiality Profiles ........................................................................................ 50
7.1.2.1. The Basic Application Level Confidentiality Profile........................................................... 50
8. ANNEXES OF APPLICATION "ANNEX ELEVA WORKSPOT 1.2" ....................................... 52
8.1. IOD CONTENTS ................................................................................................................... 52
8.1.1. Created SOP Instance ...................................................................................................... 52
8.1.1.1. List of created SOP Classes ............................................................................................. 52
8.1.1.2. Computed Radiography Image Storage SOP Class......................................................... 53
8.1.1.3. Secondary Capture Image Storage SOP Class................................................................ 56
8.1.2. Usage of Attributes from Received IOD............................................................................ 59
8.1.3. Attribute Mapping .............................................................................................................. 59
8.1.4. Coerced/Modified fields..................................................................................................... 60
8.2. DATA DICTIONARY OF PRIVATE ATTRIBUTES .............................................................. 61
8.3. CODED TERMINOLOGY AND TEMPLATES...................................................................... 61
8.4. GRAYSCALE IMAGE CONSISTENCY ................................................................................ 61
8.5. STANDARD EXTENDED/SPECIALIZED/PRIVATE SOPS................................................. 61
8.6. PRIVATE TRANSFER SYNTAXES...................................................................................... 61

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 7 of 61

3. I NTRODUCTION
The introduction specifies product and relevant disclaimers as well as any general
information that the vendor feels is appropriate.

3.1. Revision History

The revision history provides dates and differences of the different releases.
Table 3: Revision History

Document
Date of Issue Author Description
Version
00 01 January 2006 PMS CTO Template for the DICOM Conformance Statement (Ref.
C&S IC2 DICOM Standard PS 3.2 - Conformance)
01 15 December 2006 PMS CTO Draft version for review
C&S IC2
02 08 February 2007 PMS CTO Final version
C&S IC2
03 13 March 2007 PMS CTO Update of system name
C&S IC2

3.2. Audience
This Conformance Statement is intended for:
• (Potential) customers
• System integrators of medical equipment
• Marketing staff interested in system functionality
• Software designers implementing DICOM interfaces
It is assumed that the reader is familiar with the DICOM standard.

3.3. Remarks
The DICOM Conformance Statement is contained in chapter 4 through 8 and follows
the contents and structuring requirements of DICOM PS 3.2.

This DICOM Conformance Statement by itself does not guarantee successful

interoperability of Philips equipment with non-Philips equipment. The user (or user’s
agent) should be aware of the following issues:

• Interoperability
Interoperability refers to the ability of application functions, distributed over two or
more systems, to work successfully together. The integration of medical devices
into an IT environment may require application functions that are not specified
within the scope of DICOM. Consequently, using only the information provided by
this Conformance Statement does not guarantee interoperability of Philips
equipment with non-Philips equipment.
It is the user’s responsibility to analyze thoroughly the application requirements
and to specify a solution that integrates Philips equipment with non-Philips
equipment.

• Validation
Philips equipment has been carefully tested to assure that the actual
implementation of the DICOM interface corresponds with this Conformance
Statement.
Where Philips equipment is linked to non-Philips equipment, the first step is to
compare the relevant Conformance Statements. If the Conformance Statements
indicate that successful information exchange should be possible, additional
validation tests will be necessary to ensure the functionality, performance,
accuracy and stability of image and image related data. It is the responsibility of

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 8 of 61

the user (or user’s agent) to specify the appropriate test suite and to carry out the
additional validation tests.

• New versions of the DICOM Standard

The DICOM Standard will evolve in future to meet the user’s growing requirements
and to incorporate new features and technologies. Philips is actively involved in
this evolution and plans to adapt its equipment to future versions of the DICOM
Standard. In order to do so, Philips reserves the right to make changes to its
products or to discontinue its delivery.
The user should ensure that any non-Philips provider linking to Philips equipment
also adapts to future versions of the DICOM Standard. If not, the incorporation of
DICOM enhancements into Philips equipment may lead to loss of connectivity (in
case of networking) and incompatibility (in case of media).

3.4. Definitions, Terms and Abbreviations

DICOM definitions, terms and abbreviations are used throughout this Conformance
Statement. For a description of these, see NEMA PS 3.3 and PS 3.4.
The word Philips in this document refers to Philips Medical Systems.

The following acronyms and abbreviations are used in this document.

AE Application Entity
ANSI American National Standard Institute
AP Application Profile
BOT Basic Offset Table
CD Compact Disc
CD-R CD-Recordable
CD-M CD-Medical
CR Computed Radiography
CT Computed Tomography
DCR Dynamic Cardio Review
DICOM Digital Imaging and Communications in Medicine
DIMSE DICOM Message Service Element
DIMSE-C DIMSE-Composite
DIMSE-N DIMSE-Normalized
DX Digital X-Ray
EBE DICOM Explicit VR Big Endian
ELE DICOM Explicit VR Little Endian
FSC File-set Creator
FSR File-set Reader
FSU File-set Updater
GUI Graphic User Interface
HIS Hospital Information System
HL7 Health Level Seven
ILE DICOM Implicit VR Little Endian
IOD Information Object Definition
ISIS Information System – Imaging System
MOD Magneto-Optical Disk
MPPS Modality Performed Procedure Step
MR Magnetic Resonance
NEMA National Electrical Manufacturers Association
NM Nuclear Medicine
PDU Protocol Data Unit
RF X-Ray Radiofluoroscopic
RIS Radiology Information System
RT Radiotherapy
RWA Real-World Activity
SC Secondary Capture
SCM Study Component Management

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 9 of 61

SCP Service Class Provider

SCU Service Class User
SOP Service Object Pair
TCP/IP Transmission Control Protocol/ Internet Protocol
UID Unique Identifier
US Ultrasound
USMF Ultrasound Multi-frame
WLM Worklist Management
XA X-Ray Angiographic

3.5. References
[DICOM] Digital Imaging and Communications in Medicine, Part 1 – 18
(NEMA PS 3.1– PS 3.18),
National Electrical Manufacturers Association (NEMA)
Publication Sales 1300 N. 17th Street, Suite 1847
Rosslyn, Virginia. 22209, United States of America
Internet: http://medical nema.org/
Note that at any point in time the official standard consists of the most
recent yearly edition of the base standard (currently 2004) plus all the
supplements and correction items that have been approved as Final
Text.

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 10 of 61

4. N ETWORKING
This section contains the networking related services (vs. the media related ones).

4.1. Implementation model

The implementation model consists of three sections:
• The application data flow diagram, specifying the relationship between the
Application Entities and the “external world” or Real-World Activities,
• A functional description of each Application Entity, and
• The sequencing constraints among them.

4.1.1. Application Data Flow

The ELEVA WORKSPOT 1.2 system consists of one single application entity only: the
ELEVA WORKSPOT 1.2 Application Entity (ELEVA AE).

The figure below shows the networking application data flow as a functional overview
of the ELEVA AE

It incorporates the following functionality.

• The ELEVA AE can verify application level communication by using the

Verification service as SCP.
• The ELEVA AE can request a worklist by using the Basic Worklist Management
service as SCU.
• The ELEVA AE can store images by using the Storage service as SCU and use
the Storage-Commit SOP-class perform storage-commit as SCU.
• The ELEVA AE can compose the modality performed procedure step by using the
Study Management service as SCU.
• The ELEVA AE can print images by using the Print Management service as SCU
ELEVA AE.

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 11 of 61

Verification

Query
Worklist

Basic
Wordlist
Management

Create
Preformed
Procedure
Step

Set ELEVA AE MPPS

Preformed -
Procedure
Step

Store image

Storage

Print
images
Print
management

Figure 2: Application Data Flow Diagram

4.1.2. Functional Definition of AE’s

This section contains a functional definition for each individual local Application Entity.
This describes in general terms the functions to be performed by the AE, and the
DICOM services used to accomplish these functions. In this sense, "DICOM services"
refers not only to DICOM Service Classes, but also to lower level DICOM services,
such as Association Services.

4.1.2.1. Functional Definition of ELEVA AE

4.1.3. Sequencing of Real World Activities

The figure below shows a typical sequence of an examination using a worklist. The
user updates the worklist (Query Worklist) and then selects and opens an
examination. When the user starts the examination (acquiring the first image), the RIS
is notified (Create Performed Procedure Step).After the user confirmed each
acquisition (image 1 - N) per default the image is sent to archive (Store Image) and
printer (Print Image) simultaneously. Finally, when closing the examination, the RIS is
notified to update the data of the examination (Set Performed Procedure Step).

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 12 of 61

Note that Print Image will send images to the printer only when enough images were
received to fulfill the configured print format or when the print job is flushed manually.
When the last image of an examination is received the print job will be flushed
automatically.

Figure 3 Sequencing of an examination

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 13 of 61

4.2. AE Specifications
The next section in the DICOM Conformance Statement is a set of application entity
specifications. There are as many of these subsections as there are different AE's in
the implementation.

4.2.1. ELEVA AE
Detail of this specific Application Entity is specified in this section.

4.2.1.1. SOP Classes

This Application Entity provides Standard Conformance to the following SOP Classes.
Table 4: SOP Classes for ELEVA AE

SOP Class Name SOP Class UID SCU SCP

Computed Radiography Image Storage SOP 1.2.840.10008.5.1.4.1.1.1 Yes No
Class
Modality Performed Procedure Step SOP Class 1.2.840.10008.3.1.2.3.3 Yes No
Modality Worklist Information Model - FIND SOP 1.2.840.10008.5.1.4.31 Yes No
Class
Secondary Capture Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.7 Yes No
Storage Commitment Push Model SOP Class 1.2.840.10008.1.20.1 Yes No
Verification SOP Class 1.2.840.10008.1.1 No Yes
Basic Grayscale Print Management Meta SOP 1.2.840.10008.5.1.1.9 Yes No
Class
>Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Yes No
>Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Yes No
>Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4 Yes No
>Printer SOP Class 1.2.840.10008.5.1.1.16 Yes No

Note: Any SOP specific behavior is documented later in the conformance statement in
the applicable SOP specific conformance section.

4.2.1.2. Association Policies

Each AE specification contains a description of the general association establishment
and acceptance policies of the AE.

4.2.1.2.1. General
The DICOM standard application context has specified.
Table 5: DICOM Application Context

Application Context Name 1.2.840.10008.3.1.1.1

4.2.1.2.2. Number of Associations

The number of simultaneous associations that an Application Entity may support as a
Initiator or Acceptor is specified.
Table 6: Number of Associations as an Association Initiator for ELEVA AE

Maximum number of simultaneous associations 2

Table 7: Number of Associations as an Association Acceptor for ELEVA AE

Maximum number of simultaneous associations 1

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 14 of 61

4.2.1.2.3. Asynchronous Nature

If the implementation supports negotiation of multiple outstanding transactions this is
stated here, along with the maximum number of outstanding transactions supported.
Table 8: Asynchronous Nature as an Association Initiator for ELEVA AE

Maximum number of outstanding asynchronous transactions 0

4.2.1.2.4. Implementation Identifying Information

The value supplied for Implementation Class UID and version name are documented
here.
Table 9: DICOM Implementation Class and Version for ELEVA AE

Implementation Class UID 1.3.46.670589.30.1.3

Implementation Version Name PMS_ELEVA_PA_2.1

4.2.1.2.5. Communication Failure Handling

The behavior of the AE during communication failure is summarized in next table.
Table 10: Communication Failure Behavior

Exception Behavior
ARTIM Timeout

4.2.1.3. Association Initiation Policy

This describes the conditions under which the AE will initiate an association.

The behavior of the AE during association rejection is summarized in next table

Table 11: DICOM Association Rejection Handling

Result Source Reason/Diagnosis Behavior

1– 1 – DICOM UL service-user 1 – no-reason-given Association is not established.
rejected- The following error is logged.
permanent Association rejected by peer (
1: REJECT_RESULT
_permanent,
1: REJECT_SOURCE_dul_user,
1: REJECT_REASON
_no_reason_given)
2 – application- Association is not established.
context-name-not- The following error is logged.
supported Association rejected by peer (
1: REJECT_RESULT
_permanent,
1: REJECT_SOURCE_dul_user,
2: REJECT_REASON
_application_context_not_support
)
3 – calling-AE-title- Association is not established.
not-recognized The following error is logged.
Association rejected by peer (
1: REJECT_RESULT
_permanent,
1: REJECT_SOURCE_dul_user,
3: REJECT_REASON
_calling_aetitle_not_recognized)

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 15 of 61

Result Source Reason/Diagnosis Behavior

7 – called-AE-title- Association is not established.
not-recognized The following error is logged.
Association rejected by peer (
1: REJECT_RESULT
_permanent,
1: REJECT_SOURCE_dul_user,
7: REJECT_REASON
_called_aetitle_not_recognized)
2 – DICOM UL service-provider 1 – no-reason-given Association is not established.
(ACSE related function) The following error is logged.
Error: UserRecoverable:
impl.dicom.access.PEER:
Associationrejected by peer (
1: REJECT_RESULT
_permanent,
2: REJECT_SOURCE
_dul_provider (acse),
1: REJECT_REASON
_no_reason_given)
2 – protocol-version- Association is not established.
not-supported The following error is logged.
Association rejected by peer (
1: REJECT_RESULT
_permanent,
2: REJECT_SOURCE
_dul_provider (acse),
2: REJECT_REASON
_application_context_not_support
)
3 – DICOM UL service-provider 1 – temporary- Association is not established.
(presentation related function) congestion The following error is logged.
Association rejected by peer (
1: REJECT_RESULT
_permanent,
3: REJECT_SOURCE
_dul_provider (presentation),
1: REJECT_REASON
_no_reason_given)
2 – local-limit- Association is not established.
exceeded The following error is logged.
Association rejected by peer (
1: REJECT_RESULT
_permanent,
3: REJECT_SOURCE
_dul_provider (presentation),
2: REJECT_REASON
_application_context_not_support
)
2– 1 – DICOM UL service-user 1 – no-reason-given Association is not established.
rejected- The following error is logged.
transient Association rejected by peer (
2: REJECT_RESULT_transient,
1: REJECT_SOURCE_dul_user,
1: REJECT_REASON
_no_reason_given)
2 – application- Association is not established.
context-name-not- The following error is logged.
supported Association rejected by peer (
2: REJECT_RESULT_transient,
1: REJECT_SOURCE_dul_user,
2: REJECT_REASON
_application_context_not_support
)
3 – calling-AE-title- Association is not established.
not-recognized The following error is logged.
Association rejected by peer (
2: REJECT_RESULT_transient,
1: REJECT_SOURCE_dul_user,
3: REJECT_REASON
_calling_aetitle_not_recognized)

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 16 of 61

Result Source Reason/Diagnosis Behavior

7 – called-AE-title- Association is not established.
not-recognized The following error is logged.
Association rejected by peer (
2: REJECT_RESULT_transient,
1: REJECT_SOURCE_dul_user,
7: REJECT_REASON
_called_aetitle_not_recognized)
2 – DICOM UL service-provider 1 – no-reason-given Association is not established.
(ACSE related function) The following error is logged.
Association rejected by peer (
2: REJECT_RESULT_transient,
2: REJECT_SOURCE
_dul_provider (acse),
1: REJECT_REASON
_no_reason_given)
2 – protocol-version- Association is not established.
not-supported The following error is logged.
Association rejected by peer (
2: REJECT_RESULT_transient,
2: REJECT_SOURCE
_dul_provider (acse),
2: REJECT_REASON
_application_context_not_support
)
3 – DICOM UL service-provider 1 – temporary- Association is not established.
(presentation related function) congestion The following error is logged.
Association rejected by peer (
2: REJECT_RESULT_transient,
3: REJECT_SOURCE
_dul_provider (presentation),
1: REJECT_REASON
_no_reason_given)
2 – local-limit- Association is not established.
exceeded The following error is logged.
Association rejected by peer (
2: REJECT_RESULT_transient,
3: REJECT_SOURCE
_dul_provider (presentation),
2: REJECT_REASON
_application_context_not_support
)

The behavior of the AE on receiving an association abort is summarized in next table

Table 12: DICOM Association Abort Handling

Source Reason/Diagnosis Behavior

0 – DICOM UL service-user 0 – reason-not-specified When received, the ELEVA WORKSPOT
1.2 terminates the connection with the
following log: Association ABORTED by
peer (
0: ABORT_SOURCE_dul_user,
0: ABORT_REASON_not_specified).
2 – DICOM UL service-provider 0 – reason-not-specified When received, the ELEVA WORKSPOT
1.2 terminates the connection with the
following log: Association ABORTED by
peer (
2: ABORT_SOURCE_dul_provider,
0: ABORT_REASON_not_specified).
1 – unrecognized-PDU When received, the ELEVA WORKSPOT
1.2 terminates the connection with the
following log: Association ABORTED by
peer (
2: ABORT_SOURCE_dul_provider,
1: ABORT_REASON_unrecognized_pdu).

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 17 of 61

Source Reason/Diagnosis Behavior

2 – unexpected-PDU When received, the ELEVA WORKSPOT
1.2 terminates the connection with the
following log: Association ABORTED by
peer (
2: ABORT_SOURCE_dul_provider,
2: ABORT_REASON_unexpected_pdu).
4 – unrecognized-PDU When received, the ELEVA WORKSPOT
parameter 1.2 terminates the connection with the
following log: Association ABORTED by
peer (
2: ABORT_SOURCE_dul_provider,
4: ABORT_REASON
_unrecognized_pdu_parameter).
5 – unexpected-PDU When received, the ELEVA WORKSPOT
parameter 1.2 terminates the connection with the
following log: Association ABORTED by
peer (
2: ABORT_SOURCE_dul_provider,
5: ABORT_REASON
_unexpected_pdu_parameter).
6 – invalid-PDU- When received, the ELEVA WORKSPOT
parameter value 1.2 terminates the connection with the
following log: Association ABORTED by
peer (
2: ABORT_SOURCE_dul_provider,
6: ABORT_REASON
_invalid_pdu_parameter).

The behavior of the AE for sending an association abort is summarized in next table.
Table 13: DICOM Association Abort Policies

Exception Behavior
Timeout The Association is aborted using A-ABORT and command marked as failed.
The reason is logged and reported to the user.
Association aborted The command is marked as failed. The reason is logged and reported to the
user.

4.2.1.3.1. (Real-World) Activity – Print Management As SCU

4.2.1.3.1.1. Description and Sequencing of Activities

The RWA Real World Activity Print-Image involves the printing of an image by sending
the selected image data to a Print Management SCP (i.e. printer).

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 18 of 61

Figure 4: (Real World) Activity - Print Management As SCU

The ELEVA AE cannot handle any N-EVENT-REPORT messages.

A print job (film session) comprises one single film box with one single image (that is
composed of 1..N modality images).

Print jobs may be generated in two modes:

• Manually in the print tool, after clicking the print button the ELEVA AE will send the
selected images to the selected printer.

• Automatically during an examination, after clicking the Confirm button the ELEVA
AE will automatically send the related images of the performed procedure step to
the configured printer as soon as all images for a film sheet are acquired.

In AutoPrint mode, (1..N) modality images are composed to one logical film image (film
page) according to a preconfigured Examination specific layout (size, orientation,
image number, image position, scaling, overlay, annotation and shutter information,
etc.).

In Manual Print mode, (1..N) modality images are composed on one film image by
manual arrangement of the user, allowing for a print preview or by using predefined
layouts.

Depending on the response status of set and the configuration the ELEVA AE may
perform a retry.

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 19 of 61

4.2.1.3.1.2. Proposed Presentation Contexts

Table 14: Proposed Presentation Contexts for (Real-World) Activity – Print

Management As SCU

Presentation Context Table

Abstract Syntax Transfer Syntax Exten

ded
Role
Negoti
Name UID Name List UID List
ation
Basic Grayscale Print 1.2.840.10008.5.1.1.9 SCU None
Management Meta SOP
Class
>Basic Film Box SOP 1.2.840.10008.5.1.1.2 Explicit VR Big Endian 1.2.840.10008.1.2.2 SCU None
Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Implicit VR Little Endian 1.2.840.10008.1.2
>Basic Film Session 1.2.840.10008.5.1.1.1 Explicit VR Big Endian 1.2.840.10008.1.2.2 SCU None
SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Implicit VR Little Endian 1.2.840.10008.1.2
>Basic Grayscale Image 1.2.840.10008.5.1.1.4 Explicit VR Big Endian 1.2.840.10008.1.2.2 SCU None
Box SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Implicit VR Little Endian 1.2.840.10008.1.2
>Printer SOP Class 1.2.840.10008.5.1.1.16 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Explicit VR Big Endian 1.2.840.10008.1.2.2
Explicit VR Little Endian 1.2.840.10008.1.2.1

Negotiation not supported.

This section specifies each IOD created (including private IOD’s).

Abbreviations used in the Module table for the column "Presence of Value" are:
ALWAYS The attribute is always present with a value
EMPTY The attribute is always present without any value (attribute sent
zero length)
VNAP The attribute is always present and its Value is Not Always Present
(attribute sent zero length if no value is present)
ANAP The attribute is present under specified condition – if present then it
will always have a value
VNAPCV The attribute is present under specified condition – if present then
its Value is Not Always Present (attribute sent zero length if
condition applies and no value is present)
ANAPEV The attribute is present under specified condition – if present then it
will not have any value

The abbreviations used in the Module table for the column "Source" are:
AUTO The attribute value is generated automatically
CONFIG The attribute value source is a configurable parameter
COPY The attribute value source is another SOP instance
FIXED The attribute value is hard-coded in the application
IMPLICIT The attribute value source is a user-implicit setting
MPPS The attribute value is the same as that use for Modality Performed
Procedure Step
MWL The attribute value source is a Modality Worklist
USER The attribute value source is explicit user input

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 20 of 61

4.2.1.3.1.3. SOP Specific Conformance for Basic Film Box SOP Class of the
Basic Grayscale Print Management Meta SOP Class
This section includes the SOP specific behavior, i.e. error codes, error and exception
handling, time-outs, etc.
The behavior of an Application Entity SOP class is summarized as shown in next
Table. The standard as well as the manufacturer specific status codes and their
corresponding behavior is specified.

4.2.1.3.1.3.1. Dataset Specific Conformance for Basic Film Box N-ACTION

SCU
This section includes the dataset specific behavior, i.e. error codes, error and
exception handling, time-outs, etc.

Table 15: DICOM Command Communication Failure Behavior

Exception Behavior
Timeout The Association is aborted using AP-ABORT and command marked as failed.
The reason is logged and reported to the user.
Association aborted The command is marked as failed. The reason is logged and reported to the
user.

4.2.1.3.1.3.2. Dataset Specific Conformance for Basic Film Box N-

CREATE SCU
This section includes the dataset specific behavior, i.e. error codes, error and
exception handling, time-outs, etc.

Table 16: Basic Film Box Presentation Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Image Display Format 2010,0010 ST ALWAYS Config
Film Orientation 2010,0040 CS ALWAYS Config
Film Size ID 2010,0050 CS ALWAYS Config
Magnification Type 2010,0060 CS ALWAYS Config
Max Density 2010,0130 US ALWAYS Config
Trim 2010,0140 CS ALWAYS Config
Configuration Information 2010,0150 ST ALWAYS Config

Table 17: Basic Film Box Relationship Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Referenced Film Session 2010,0500 SQ ALWAYS AUTO
Sequence
>Referenced SOP Class UID 0008,1150 UI ALWAYS AUTO
>Referenced SOP Instance UID 0008,1155 UI ALWAYS AUTO

Table 18: DICOM Command Communication Failure Behavior

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 21 of 61

4.2.1.3.1.4. SOP Specific Conformance for Basic Film Session SOP Class of the
Basic Grayscale Print Management Meta SOP Class
Images are printed using the Basic Grayscale Print Management Meta SOP Class. If
any of the return statuses is not Success, the print job is aborted and association is
released.
After successful print job the Printer Status (2100,0010) and Printer Status Info
(2100,0020) are queried using N-GET.

Details regarding the status handling behaviour from the application level and
communication errors are provided in Table 19.

Table 19: DICOM Command Response Status Handling Behavior for

Grayscale Print Management Meta Sop Class

Service Status Code Further Meaning Behavior

Success 0000 Successful operation The print job continues.
Failure xxxx Any failure In the AutoPrint mode a GUI is invoked. The status
panel of this GUI displays a message based on the
'Further Meaning'.
The warning or failure response of a print request that is
invoked by the Manual Print Composer GUI will be
displayed by a pop-up window (if the user has not
closed the GUI before the printer status was delivered).
Warning xxxx Any warning In the AutoPrint mode a GUI is invoked. The status
panel of this GUI displays a message based on the
'Further Meaning'.
The warning or failure response of a print request that is
invoked by the Manual Print Composer GUI will be
displayed by a pop-up window (if the user has not
closed the GUI before the printer status was delivered).

The behavior of the AE during communication failure is summarized in Table 20.

Table 20: DICOM Command Communication Failure Behavior

Exception Behavior
Timeout The Association is aborted using A-ABORT and the command is marked as
failed. The reason is logged. After a maximum number of retries the user is
notified via pop-up (in preview mode only).
Association aborted The command is marked as failed. The reason is logged. After a maximum
number of retries the user is notified via pop-up (in preview mode only).
Failed to connect Log entry. After a maximum number of retries the user is notified via pop-up (in
preview mode only).
.

4.2.1.3.1.4.1. Dataset Specific Conformance for Basic Film Session N-

CREATE SCU
This section includes the dataset specific behavior, i.e. error codes, error and
exception handling, time-outs, etc.

Table 21: Basic Film Session Presentation Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Number of Copies 2000,0010 IS ALWAYS AUTO
Print Priority 2000,0020 CS ALWAYS AUTO
Medium Type 2000,0030 CS ALWAYS USER
Film Destination 2000,0040 CS ALWAYS CONFI
G
Film Session Label 2000,0050 LO ALWAYS AUTO

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 22 of 61

Table 22: DICOM Command Communication Failure Behavior

4.2.1.3.1.5. SOP Specific Conformance for Basic Grayscale Image Box SOP
Class of the Basic Grayscale Print Management Meta SOP Class
This section includes the SOP specific behavior, i.e. error codes, error and exception
handling, time-outs, etc. The behavior of an Application Entity SOP class is
summarized as shown in next Table. The standard as well as the manufacturer
specific status codes and their corresponding behavior are specified.

4.2.1.3.1.5.1. Dataset Specific Conformance for Basic Grayscale Image

Box N-SET SCU
This section includes the dataset specific behavior, i.e. error codes, error and
exception handling, time-outs, etc.

Table 23: Image Box Pixel Presentation Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Image Position 2020,0010 US ALWAYS AUTO
Polarity 2020,0020 CS ALWAYS AUTO
Basic Grayscale Image 2020,0110 SQ ALWAYS AUTO
Sequence
>Samples per Pixel 0028,0002 US 1, 1 ALWAYS AUTO
>Photometric Interpretation 0028,0004 CS MONOCHROME1, ALWAYS CONFI
MONOCHROME2, G
MONOCHROME2
>Rows 0028,0010 US ALWAYS IMPLICI Depending on the
T selected printer type and
film size.
>Columns 0028,0011 US ALWAYS IMPLICI Depending on the
T selected printer type and
film size.
>Bits Allocated 0028,0100 US 16, 8, 8 ALWAYS AUTO
>Bits Stored 0028,0101 US 12, 8, 8 ALWAYS IMPLICI
T
>High Bit 0028,0102 US 11, 7, 7 ALWAYS AUTO
>Pixel Representation 0028,0103 US 0x0000 ALWAYS AUTO
>Pixel Data 7FE0,0010 O ALWAYS AUTO
W/
OB

Table 24: DICOM Command Communication Failure Behavior

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 23 of 61

4.2.1.3.1.6. SOP Specific Conformance for Printer SOP Class of the Basic
Grayscale Print Management Meta SOP Class
This section includes the SOP specific behavior, i.e. error codes, error and exception
handling, time-outs, etc. The behavior of an Application Entity SOP class is
summarized as shown in next Table. The standard as well as the manufacturer
specific status codes and their corresponding behavior is specified.

4.2.1.3.1.6.1. Dataset Specific Conformance for Printer N-EVENT-REPORT

SCP
This section includes the dataset specific behavior, i.e. error codes, error and
exception handling, time-outs, etc.

Table 25: DICOM Command Communication Failure Behavior

4.2.1.3.2. (Real-World) Activity – Image Export

4.2.1.3.2.1. Description and Sequencing of Activities

Figure 5: (Real World) Activity - Image Export

Export means that ELEVA WORKSPOT 1.2 stores images without Storage
Commitment.
This RWA may be initiated in two ways.

• Manually in the viewer, after clicking the Store button the ELEVA AE will store the
selected images at the selected Storage SCP.

• Automatically during an examination, after clicking the Confirm button the ELEVA
AE will automatically store the related images of the performed procedure step at
the configured Storage SCP.

The ELEVA AE will request an association with the remote Storage SCP for the
applicable Storage SOP classes. After accepting the association the ELEVA AE will
send the store request, wait for response, and then release the association. The store
response status may be inspected on the UI.

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 24 of 61

Depending on the status of the store the ELEVA AE may queue store requests for
retries. The queued store requests can be cancelled from the UI.

4.2.1.3.2.2. Proposed Presentation Contexts

Table 26: Proposed Presentation Contexts for (Real-World) Activity – Image

Export

Presentation Context Table

Abstract Syntax Transfer Syntax Exten

ded
Role
Negoti
Name UID Name List UID List
ation
Computed Radiography 1.2.840.10008.5.1.4.1.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Image Storage SOP Explicit VR Big Endian 1.2.840.10008.1.2.2
Class
Explicit VR Little Endian 1.2.840.10008.1.2.1
Secondary Capture 1.2.840.10008.5.1.4.1.1.7 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Image Storage SOP Explicit VR Big Endian 1.2.840.10008.1.2.2
Class
Explicit VR Little Endian 1.2.840.10008.1.2.1

Negotiation is not supported.

4.2.1.3.2.3. SOP Specific Conformance for Storage SOP Classes

This section includes the SOP specific behavior, i.e. error codes, error and exception
handling, time-outs, etc. The behavior of an Application Entity SOP class is
summarized as shown in next Table. The standard as well as the manufacturer
specific status codes and their corresponding behavior are specified.

Table 27: C-STORE-RQ Status Response

Service Status Code Further Meaning Behavior

Success 0000 Storage is complete UI status is updated
Refused A7xx Out of resources The association is released. The reason is logged. The
user is informed.
Error A9xx Data set does not match The association is released. The reason is logged. The
SOP class user is informed.
Cxxx Cannot understand The association is released. The reason is logged. The
user is informed.
Warning B000 Coercion of data The association is released. The reason is logged. The
elements user is informed.
B006 Elements discarded The association is released. The reason is logged. The
user is informed.
B007 Data set does not match The association is released. The reason is logged. The
SOP class user is informed.

Table 28: DICOM Command Communication Failure Behavior

Exception Behavior
Association aborted The command is marked as failed. The reason is logged and reported to the
user.

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 25 of 61

4.2.1.3.3. (Real-World) Activity – Modality Performed Procedure Step as SCU

4.2.1.3.3.1. Description and Sequencing of Activities

Description of Activities

An ELEVA WORKSPOT 1.2 “Examination” is regarded equivalent to a DICOM

Procedure Step. It is scheduled or manually entered before an acquisition is taken,
and performed by taking acquisitions. If scheduled by the RIS, one Examination is the
result of one Scheduled Procedure Step. Since an examination may not be re-opened
after having been closed, and each examination workflow context is enclosed in one
MPPS, one examination may result in 0:1 MPPS instances. However, image archiving
after the examination’s closure leads to 1:n MPPS instances per examination (append
case).

After the image for a Scheduled Procedure Step has been acquired, the system sets
the MPPS status of the related examination to “IN PROGRESS” and generates an
initial MPPS IN PROGRESS message. The system does not generate intermediate
MPPS IN PROGRESS messages for subsequent acquisitions of this Scheduled
Procedure Step instance.

After finishing the appropriate acquisition(s), the system will change the MPPS status
of the related examination to “COMPLETED” and generate an MPPS N-SET-FINAL
message.
ELEVA WORKSPOT 1.2 also generates MPPS messages for unscheduled
examinations.

The MPPS COMPLETED message will list the UID’s of all related DICOM archived
images and the format of (optionally) generated direct prints.

After abandoning or discontinuing a procedure step, the operator may set the MPPS
status of the related examination to “DISCONTINUED” and the system generates a
MPPS DICONTINUED message. The reason for abandoning or discontinuing a
procedure step is unspecified.

The operator may interchange the performed sequence order of scheduled procedure
steps.

MPPS messages may interleave. Depending on the application workflow optimization

by the user, an MPPS sequence like this may come up:

MPPS / SOP Instance UID 1: N-CREATE (IN PROGRESS)

MPPS / SOP Instance UID 2: N-CREATE (IN PROGRESS)
MPPS / SOP Instance UID 3: N-CREATE (IN PROGRESS)
...
MPPS / SOP Instance UID 2: N-SET (COMPLETED)
MPPS / SOP Instance UID 1: N-SET (COMPLETED)
MPPS / SOP Instance UID 3: N-SET (COMPLETED)

(i.e.: running multiple procedure steps ‘in parallel’).

Sequencing of Activities

After storing a performed procedure step the ELEVA AE shall request an association
with the configured remote Study Management SCP. After accepting the association
the ELEVA AE shall send a Create request, wait for response, and then release the
association.

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 26 of 61

Figure 6: (Real World) Activity - Modality Performed Procedure Step As SCU

Figure 7 SET Preformed Procedure Step

4.2.1.3.3.2. Proposed Presentation Contexts

Table 29: Proposed Presentation Contexts for (Real-World) Activity – Modality

Performed Procedure Step As SCU

Presentation Context Table

Abstract Syntax Transfer Syntax Exten

ded
Role
Negoti
Name UID Name List UID List
ation
Modality Performed 1.2.840.10008.3.1.2.3.3 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Procedure Step SOP Explicit VR Big Endian 1.2.840.10008.1.2.2
Class
Explicit VR Little Endian 1.2.840.10008.1.2.1

Negotiation is not supported

4.2.1.3.3.3. SOP Specific Conformance for Modality Performed Procedure Step

SOP Class
When acquiring the first image of a Scheduled or Unscheduled Procedure Step,
ELEVA WORKSPOT 1.2 generates a MPPS IN PROGRESS message.
ELEVA WORKSPOT 1.2 does not generate intermediate IN PROGRESS (N-SET)
messages and does not support the Performed Procedure Step Exception

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 27 of 61

Management Option. ELEVA WORKSPOT 1.2 has no Billing Code Tables and does
not support the Performed Procedure Step Billing and Material Management Option,
except default values for Medium Type (2000,0030) and Film Size ID (2010,0050), if
optional Local Print is configured.

Assisted Acquisition Protocol Setting Option

ELEVA AE by default derives the specific acquisition protocol from the Scheduled
Protocol Code Sequence Items. Any single Item results in an Examination.
ELEVA AE supports 3 more (configurable) mapping relations, as shown below:

• Examination is selected from Scheduled Protocol Code Items->Code Value

(0040,0008) (default)
• Examination is selected from Scheduled Procedure Step Description (0040,0007)
• Examination is selected from Requested Procedure Code Items->Code Value
(0032,1064)
• Examination is selected from Requested Procedure Description (0032,1060)

ELEVA AE does not evaluate the attributes Coding Scheme Version (0008,0103),
Coding Scheme Designator (0008,0102), Code Meaning (0008,0104), but only the
Code Value (0008,0100), for mapping the examination settings. I.e. ELEVA AE
expects that any used Code Value is unique (unambiguous) within a given RIS
domain.

Restrictions Depending on Number of Scheduled Protocol Code Items

It is highly recommended that the Scheduled Procedure Step contains only 1 Item in
the Scheduled Protocol Code Sequence.

If the Scheduled Procedure Step contains <n> items in the Scheduled Protocol Code
Sequence, the Scheduled Procedure Step is split into <n> examinations, where any
single examination shows only 1 of the Scheduled Protocol Code Items, but all the
other attributes are the same.
When such an examination is returned back via MPPS, also the Performed Protocol
Code Sequence will show only 1 item. If all <n> Scheduled Procedure Step Code
Items are performed, <n> MPPS instances will be sent back to the RIS, and the sum
of all Performed Protocol Code Items will be <n>.

4.2.1.3.3.3.1. Dataset Specific Conformance for Modality Performed

Procedure Step N-CREATE SCU
This section includes the dataset specific behavior, i.e. error codes, error and
exception handling, time-outs, etc.

Table 30: MPPS Request Identifiers for N-CREATE-RQ

Attribute Name Tag VR Value Comment

Performed Procedure Step Information Module

Performed Station AE Title 0040,0241 AE
Performed Procedure Step Start 0040,0244 DA
Date
Performed Procedure Step Start 0040,0245 TM
Time
Performed Procedure Step 0040,0252 CS
Status
Performed Procedure Step ID 0040,0253 SH
Performed Station Name 0040,0242 SH
Performed Location 0040,0243 SH
Performed Procedure Step End 0040,0250 DA
Date
Performed Procedure Step End 0040,0251 TM

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 28 of 61

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 29 of 61

Attribute Name Tag VR Value Comment

Additional Module
Issuer of Patient ID 0010,0021 LO

Table 31: N-CREATE-RQ Status Response

Service Status Code Further Meaning Behavior

Success 0000 Successful operation The SCP has successfully received the modality
performed procedure step create request. Log entry.
Failure 0213 Resource limitation The command is reported to the user as failed. The
reason is logged.
After a configured period of time the storage will be
retried up to a configured number of times.
xxxx Any failure accept The command is reported to the user as failed. The
reason is logged. No retry.

Table 32: DICOM Command Communication Failure Behavior

4.2.1.3.3.3.2. Dataset Specific Conformance for Modality Performed

Procedure Step N-SET SCU
This section includes the dataset specific behavior, i.e. error codes, error and
exception handling, time-outs, etc.

Table 33: MPPS Request Identifiers for N-SET-RQ

Attribute Name Tag VR Value Comment

Performed Procedure Step Information Module

Performed Procedure Step End 0040,0250 DA
Date
Performed Procedure Step End 0040,0251 TM
Time
Performed Procedure Step 0040,0252 CS
Status
Performed Procedure Step 0040,0254 LO
Description
Radiation Dose Module
Image and Fluoroscopy Area 0018,115E DS Not accumulating: re-
Dose Product processed images, non-
digital images. Not sent
in case of appended
MPPS instances.
Total Number of Exposures 0040,0301 US Not accumulating: re-
processed images, non-
digital images. Not sent
in case of appended
MPPS instances.
Comments on Radiation Dose 0040,0310 ST
Image Acquisition Results Module
Performed Protocol Code 0040,0260 SQ
Sequence
>Code Value 0008,0100 SH
>Coding Scheme Designator 0008,0102 SH

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 30 of 61

Table 34: N-SET-RQ Status Response

Service Status Code Further Meaning Behavior

Success 0000 Confirmation The association is released.
Failure 0110 Processing failure – The reason is logged.
performed procedure
step object may no
longer be updated
xxxx (any other failure) The reason is logged.

Table 35: DICOM Command Communication Failure Behavior

4.2.1.3.4. (Real-World) Activity – Modality worklist As SCU

4.2.1.3.4.1. Description and Sequencing of Activities

For each Broad or specific Worklist request, an association towards the Basic Worklist
Management SCP is established and a C-FIND request is transmitted. The Broad
query can be configured with a combination of the Matching Keys:
• Scheduled Station AE Title
• Scheduled Procedure Step Start Date
• Modality

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 31 of 61

Each of the matching keys is optional. The association will be closed on reception of
the last C-FIND response. The Worklist Query result is displayed in the Patient List.
The query is interruptible if it was triggered by the user.

After clicking the Query Worklist button the ELEVA AE shall request an association
with the configured remote Basic Worklist Management SCP.
When the association is accepted the ELEVA AE shall send the broad query find
request, wait for response, and then release the association.

Figure 8: (Real World) Activity - Modality worklist As SCU

This RWA may be initiated in two ways.

• After clicking the Query Worklist button the ELEVA AE shall request an
association with the configured remote Basic Worklist Management SCP. When
the association is accepted the ELEVA AE shall send the Broad Query find
request, wait for response, and then release the association.

• After clicking the Patient Query button - entering and confirming the matching key
values - the ELEVA AE shall request an association with the configured remote
Basic Worklist Management SCP. When the association is accepted the ELEVA
AE shall send the patient query find request, wait for response, and then release
the association.

Optionally the Broad Query may also be performed automatically in the system
background. The time interval between subsequent background queries is
configurable. Manual and automatic background queries are serialized and do not
interfere with another.

4.2.1.3.4.2. Proposed Presentation Contexts

Table 36: Proposed Presentation Contexts for (Real-World) Activity – Modality

worklist As SCU

Presentation Context Table

Abstract Syntax Transfer Syntax Exten

ded
Role
Negoti
Name UID Name List UID List
ation
Modality Worklist 1.2.840.10008.5.1.4.31 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 32 of 61

Presentation Context Table

Abstract Syntax Transfer Syntax Exten

ded
Role
Negoti
Name UID Name List UID List
ation
Information Model - FIND Explicit VR Big Endian 1.2.840.10008.1.2.2
SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1

Negotiation is not supported.

4.2.1.3.4.3. SOP Specific Conformance for Modality Worklist Information Model

- FIND SOP Class
The worklist received by a broad query is compared to the worklist received by a
previous broad query. In case there are any changes, the ELEVA WORKSPOT 1.2
patient list is updated. The content of a worklist received by a search query and
manually scheduled patients is remains.

4.2.1.3.4.3.1. Dataset Specific Conformance for Modality Worklist

Information Model - FIND C-FIND SCU
This section includes the dataset specific behavior, i.e. error codes, error and
exception handling, time-outs, etc.

The table below should be read as follows:

Attribute Name: Attributes supported to build a Modality Worklist Request Identifier.
Tag: DICOM tag for this attribute.
VR: DICOM VR for this attribute.
M: Matching Keys for (automatic) Worklist Update.
R: Return Keys. An “X” will indicate that this attribute as Return Key
with
zero length for Universal Matching.
Q: Interactive Query Key. An “X” will indicate that this attribute as
matching key can be used.
D: Displayed Keys. An “X” indicates that this Worklist attribute is
displayed to the user during a patient registration dialog.
IOD: An “X” indicates that this Worklist attribute is included into all object
Instances created during performance of the related Procedure
Step.
Type of matching: The following types of matching exists:
Single Value Matching
List of UID Matching
Wild Card Matching
Range Matching
Sequence Matching
Universal Matching

Table 37: Worklist Request Identifier

Attribute Name Tag VR M R Q D IOD Type of Matching Comment

SOP Common Module

Specific Character Set 0008,0005 CS Configurable
Patient Identification Module
Patient's Name 0010,0010 PN X X X Single Value,
Universal,
WildCard
Patient ID 0010,0020 LO X X X Single Value,

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 33 of 61

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 34 of 61

Attribute Name Tag VR M R Q D IOD Type of Matching Comment

Requested Procedure 0032,1060 LO X X
Description
Requested Procedure ID 0040,1001 SH X X X Single Value, Wild
Card (?),
Universal
Reason for the Requested 0040,1002 LO X X
Procedure
Requested Procedure Priority 0040,1003 SH X X
Patient Transport Arrangements 0040,1004 LO X X
Names of Intended Recipients 0040,1010 PN X
of Results
Requested Procedure 0040,1400 LT X X
Comments
Referenced Study Sequence 0008,1110 SQ X
>Referenced SOP Class UID 0008,1150 UI X
>Referenced SOP Instance UID 0008,1155 UI X
Requested Procedure Code 0032,1064 SQ X
Sequence
>Code Value 0008,0100 SH X
>Coding Scheme Designator 0008,0102 SH X
>Coding Scheme Version 0008,0103 SH X
>Code Meaning 0008,0104 LO X
Imaging Service Request Module
Accession Number 0008,0050 SH X X X Single
Value,Universal,
WildCard (?)
Referring Physician's Name 0008,0090 PN X
Requesting Physician 0032,1032 PN X
Reason for the Imaging Service 0040,2001 LO X
Request (RETIRED)
Issue Date of Imaging Service 0040,2004 DA X
Request
Imaging Service Request 0040,2400 LT X
Comments

Table 38: C-FIND-RQ Status Response

Service Status Code Further Meaning Behavior

Success 0000 Matching is complete The worklist is updated.
Failure A700 Refused The association is released. The reason is logged.
– Out of resources
A900 Failed The association is released. The reason is logged.
– Identifier does not
match SOP class
Cxxx Failed The association is released. The reason is logged.
– Unable to process
Cancel FE00 Matching terminated The association is released. The reason is logged.
due to Cancel request
Pending FF00 Matches are continuing The Query Worklist job continues.
– Current match is
supplied and any
optional keys were
supported in the same
manner as required
keys
FF01 Matches are continuing The Query Worklist job continues.
– Warning that one or
more optional keys were
not supported for
existence and/or
matching for this
identifier

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 35 of 61

Table 39: DICOM Command Communication Failure Behavior

Exception Behavior
RIS query timeout The Association is aborted using A-ABORT and command marked as failed.
(default 240 seconds) The reason is logged and reported to the user.
Association aborted The command is marked as failed. The reason is logged and reported to the
user.

4.2.1.3.4.3.2. Dataset Specific Conformance for Modality Worklist

Information Model - FIND C-CANCEL SCU
This section includes the dataset specific behavior, i.e. error codes, error and
exception handling, time-outs, etc.

Table 40: DICOM Command Communication Failure Behavior

4.2.1.3.4.4. Patient and Study Merge

The ELEVA AE looks in its internal database for a Study with the same Study Instance
UID (0020,000D) as given in the Scheduled Procedure Step.

If a Study Instance UID match was not found, it looks for a Patient with the same
Patient ID (0010,0020) as given in the Scheduled Procedure Step. If no Patient match
is found, a new Patient is created, using attributes from Scheduled Procedure Step. If
Patient with a matching Patient ID was found, attributes are updated for the internal
Patient, based on the attributes as given in the Scheduled Procedure Step.
A new Study with a Study Instance UID as given in the Scheduled Procedure Step is
created.

If a Study Instance UID match was found, all Patient attributes as given in the
Scheduled Procedure Step are updated in the internal database for the parent patient
of this study. Study attributes are updated for the internal study based on the attributes
as given in the Scheduled Procedure Step.

4.2.1.3.4.5. Scheduled Procedure Step (= Examination) Merge

If the ELEVA AE’s internal database contains no SPS with Scheduled Procedure Step
ID (0040,0009) identifying an incoming Scheduled Procedure Step, it creates a new
one and creates an corresponding Examination referencing this Scheduled Procedure
Step ID.

If the ELEVA AE’s internal database contains already an SPS with the Scheduled
Procedure Step ID (0040,0009) identifying an incoming Scheduled Procedure Step,
the behavior depends on the corresponding Examination state.

If the Examination is still “scheduled”, the SPS attributes are compared to the
attributes sent with the most recent WLM query. If at least one attribute differs, the
scheduled Examination is deleted and re-scheduled. Manual changes the user might
have performed on this Examination are lost.

If the Examination has already started, no changes are performed, and the potential
changes of the incoming Scheduled Procedure Step are disregarded.

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 36 of 61

4.2.1.3.5. (Real-World) Activity – Storage Commitment Push Model AS SCU

4.2.1.3.5.1. Description and Sequencing of Activities

Archive means that ELEVA WORKSPOT 1.2 stores images with Storage
Commitment.
This RWA may be initiated in two ways.

• Manually in the viewer, after clicking the Store button the ELEVA AE will store the
selected images at the selected Storage SCP.

• Automatically during an examination, after clicking the Confirm button the ELEVA
AE will automatically store the related images of the performed procedure step at
the configured Storage SCP.

Figure 9: (Real World) Activity - Storage Commitment Push Model AS SCU

Depending on the status of the store the ELEVA AE may queue store requests for
retries. The queued store requests can be cancelled from the UI.

4.2.1.3.5.2. Proposed Presentation Contexts

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 37 of 61

Table 41: Proposed Presentation Contexts for (Real-World) Activity – Storage

Commitment Push Model AS SCU

Presentation Context Table

Abstract Syntax Transfer Syntax Exten

ded
Role
Negoti
Name UID Name List UID List
ation
Storage Commitment 1.2.840.10008.1.20.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Push Model SOP Class Explicit VR Big Endian 1.2.840.10008.1.2.2
Explicit VR Little Endian 1.2.840.10008.1.2.1

Negotiation not supported.

4.2.1.3.5.3. SOP Specific Conformance for Storage Commitment Push Model

SOP Class
This section includes the SOP specific behavior, i.e. error codes, error and exception
handling, time-outs, etc. The behavior of an Application Entity SOP class is
summarized as shown in next Table. The standard as well as the manufacturer
specific status codes and their corresponding behavior are specified.

4.2.1.3.5.3.1. Dataset Specific Conformance for Storage Commitment

Push Model N-ACTION SCU
This section includes the dataset specific behavior, i.e. error codes, error and
exception handling, time-outs, etc.

Table 42: Storage Commitment Attribute for N-ACTION-RQ

Attribute Name Tag Comment

Storage Commitment Module

Transaction UID 0008,1195
Referenced SOP Sequence 0008,1199
>Referenced SOP Class UID 0008,1150
>Referenced SOP Instance UID 0008,1155

Table 43: N-ACTION-RQ Status Response

Service Status Code Further Meaning Behavior

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 38 of 61

Table 44: DICOM Command Communication Failure Behavior

Exception Behavior
Association aborted The command is marked as failed. The reason is logged and reported to the
user.

4.2.1.3.5.3.2. Dataset Specific Conformance for Storage Commitment

Push Model N-EVENT-REPORT SCP
This section includes the dataset specific behavior, i.e. error codes, error and
exception handling, time-outs, etc.

Table 45: Storage Commitment Attribute for N-EVENT-REPORT-RQ

Attribute Name Tag Comment

Storage Commitment Module

Transaction UID 0008,1195
Referenced SOP Sequence 0008,1199
>Referenced SOP Class UID 0008,1150
>Referenced SOP Instance UID 0008,1155
>Retrieve AE Title 0008,0054
>Storage Media File-Set ID 0088,0130
>Storage Media File-Set UID 0088,0140

Table 46: DICOM Command Communication Failure Behavior

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 39 of 61

4.2.1.4. Association Acceptance Policy

This describes the conditions under which the AE will initiate an association.

The behavior of the AE during association rejection is summarized in next table

ELEVA AE accepts associations to allow remote applications to verify application level
communication.

The ELEVA AE rejects association requests from unknown applications, i.e.

applications that offer an unknown “calling AE title”. An application is known if and only
if it is defined per configuration.

The ELEVA AE rejects association requests from applications that do not address the
ELEVA AE, i.e. that offer a wrong “called AE title”.

The AE association rejection policies are summarized in table 37.

Table 47: DICOM Association Rejection Handling

Result Source Reason/Diagnosis Explanation

1– 1 – DICOM UL service-user 1 – no-reason-given Association is not established
rejected- due to any problem other than
permanent that specified in the rows below.
(Example: Problem while
decoding the DICOM stream).
2 – application- An application context name
context-name-not- other than 1.2.840.10008.3.1.1.1
supported is requested by the SCU during
association.
3 – calling-AE-title- - The configuration does not
not-recognized contain a repository having the
Calling AE Title as per the
association request.
- There is a problem in
configuration (related to
composing the configuration from
the SCU and the SCP
configuration).
7 – called-AE-title- The called AE Title in the
not-recognized association request does not
match the AE Title as per the
configuration.
2 – DICOM UL service-provider 1 – no-reason-given Not used.
(ACSE related function) 2 – protocol-version- Not used.
not-supported
3 – DICOM UL service-provider 1 – temporary- Not used.
(presentation related function) congestion
2 – local-limit- Not used.
exceeded
2– 1 – DICOM UL service-user 1 – no-reason-given Not used.
rejected- 2 – application- Not used.
transient context-name-not-
supported
3 – calling-AE-title- Not used.
not-recognized
7 – called-AE-title- Not used.
not-recognized
2 – DICOM UL service-provider 1 – no-reason-given Maximum number of associations
(ACSE related function) is exceeded and an association
request is received.
2 – protocol-version- Not used.
not-supported
3 – DICOM UL service-provider 1 – temporary- Not used.
(presentation related function) congestion
2 – local-limit- Not used.
exceeded

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 40 of 61

The behavior of the AE on receiving an association abort is summarized in next table

Table 48: DICOM Association Abort Handling

Source Reason/Diagnosis Behavior

Sent when:
Association times out due to inactivity
Any other problem than ones specified in
the rows below. (Examples: Problem while
decoding the DICOM stream, Invalid
request, Echo SCP was unable to send the
Response to SCU, Error writing to SCU
stream).
2 – DICOM UL service-provider 0 – reason-not-specified When received, the ELEVA WORKSPOT
1.2 terminates the connection with the
following log: Association ABORTED by
peer (
2: ABORT_SOURCE_dul_provider,
0: ABORT_REASON_not_specified)
1 – unrecognized-PDU When received, the ELEVA WORKSPOT
1.2 terminates the connection with the
following log: Association ABORTED by
peer (
2: ABORT_SOURCE_dul_provider,
1: ABORT_REASON_unrecognized_pdu).

Sent when:
An unrecognized PDU type is received.
2 – unexpected-PDU When received, the ELEVA WORKSPOT
1.2 terminates the connection with the
following log: Association ABORTED by
peer (
2: ABORT_SOURCE_dul_provider,
2: ABORT_REASON_unexpected_pdu).

Sent when:
The received PDU type is not expected in
the current state of connection.
4 – unrecognized-PDU When received, the ELEVA WORKSPOT
parameter 1.2 terminates the connection with the
following log: Association ABORTED by
peer (
2: ABORT_SOURCE_dul_provider,
4: ABORT_REASON
_unrecognized_pdu_parameter).

Sent when:
An unrecognized Associate PDU item is
received.
5 – unexpected-PDU When received, the ELEVA WORKSPOT
parameter 1.2 terminates the connection with the
following log: Association ABORTED by
peer (
2: ABORT_SOURCE_dul_provider,
5: ABORT_REASON
_unexpected_pdu_parameter).

Sent when:
One of the Associate PDU items is received
more than once.
One of the Associate PDU items is received
unexpectedly.

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 41 of 61

Source Reason/Diagnosis Behavior

6 – invalid-PDU- When received, the ELEVA WORKSPOT
parameter value 1.2 terminates the connection with the
following log: Association ABORTED by
peer (
2: ABORT_SOURCE_dul_provider,
6: ABORT_REASON
_invalid_pdu_parameter).

Sent when:
One of the Associate PDU items is received
more than once.
One of the Associate PDU items is not
received.
Empty Called AE Title String (space-only) is
received.
Empty Calling AE Title String (space-only)
is received.
Unknown abstract syntax is received
The length or the format of the received
PDU item is invalid.

The behavior of the AE for sending an association abort is summarized in next table.
Table 49: DICOM Association Abort Policies

Source Reason/Diagnosis Behavior

0 – DICOM UL service-user 0 – reason-not-specified
2 – DICOM UL service-provider 0 – reason-not-specified
1 – unrecognized-PDU
2 – unexpected-PDU
4 – unrecognized-PDU
parameter
5 – unexpected-PDU
parameter
6 – invalid-PDU-
parameter value

4.2.1.4.1. (Real-World) Activity – Verification as SCP

4.2.1.4.1.1. Description and Sequencing of Activities

The ELEVA AE accepts associations from systems that whish to verify application
level communication using the C-ECHO command.

Figure 10: (Real World) Activity - Verification as SCP

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 42 of 61

4.2.1.4.1.2. Accepted Presentation Contexts

Table 50: Acceptable Presentation Contexts for (Real-World) Activity –

Verification as SCP

Presentation Context Table

Abstract Syntax Transfer Syntax Exten

ded
Role
Negoti
Name UID Name List UID List
ation
Verification SOP Class 1.2.840.10008.1.1 Explicit VR Big Endian 1.2.840.10008.1.2.2 SCP None
Explicit VR Little Endian 1.2.840.10008.1.2.1
Implicit VR Little Endian 1.2.840.10008.1.2

Negotiation not supported.

4.2.1.4.1.3. SOP Specific Conformance for Verification SOP Class

4.2.1.4.1.3.1. Dataset Specific Conformance for Verification C-ECHO SCP

This section includes the dataset specific behavior, i.e. error codes, error and
exception handling, time-outs, etc.

Table 51: C-ECHO-RSP Status Response

Service Status Code Further Meaning Behavior

Success 0000 Verification is complete The ELEVA WORKSPOT 1.2 has successfully received
the verification request.

Table 52: DICOM Command Communication Failure Behavior

© Koninklijke Philips Electronics N.V. 2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 43 of 61

4.3. Network Interfaces

4.3.1. Physical Network Interfaces

The ELEVA WORKSPOT 1.2 provides DICOM 3.0 TCP/IP Network Communication
Support as defined in Part 8 of the DICOM 3.0 Standard.

The ELEVA WORKSPOT 1.2 system supports ISO 8802-3 10BASE-T and 100Base-
TX Ethernet.

4.3.2. Additional Protocols

No additional protocols are used.

4.4. Configuration
Any implementation’s DICOM conformance may be dependent upon configuration,
which takes place at the time of installation. Issues concerning configuration is
addressed in this section.

4.4.1. AE Title/Presentation Address Mapping

An important installation issue is the translation from AE title to presentation address.
How this is to be performed shall be described in this section.

4.4.1.1. Local AE Titles

The local AE title mapping and configuration is as specified in the following table.
Table 53: AE Title Configuration Table

Application Entity Default AE Title Default TCP/IP Port

ELEVA AE ELEVA 3010

4.4.1.2. Remote AE Title/Presentation Address Mapping

All remote applications to be selected as destination (SCP) are configurable for the
following items:
• The Application Entity Title of the remote application.
The Presentation Address of where the remote application should accept association
requests.

4.4.2. Parameters
This section specifies important operational parameters and, if configurable, their
default value and range.
Table 54: Configuration Parameters

Parameter Configurable Default Value

General Parameters
Maximum PDU receive size No -
Maximum PDU send size Yes 16384
Maximum number of simultaneous associations Yes 2
Artim Timeout Yes 60 [seconds]
Specifies the time in seconds of the ARTIM (Association
Request/Reject/Release TIMer).
Allowed values:
0: unlimited waiting time
0 < n: real time in seconds

© Koninklijke Philips Electronics N.V.2007

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 44 of 61

Parameter Configurable Default Value

Automatic Association Timeout Yes 0 [unlimited]
Specifies the association inactivity timeout in seconds after which
the association is closed automatically.
Allowed values:
-1: immediate timeout
0: unlimited waiting time
0 < n: real time in seconds
Transfer Syntax support: ILE, ELE, EBE Yes ILE, ELE, EBE
Storage Specific Parameters
Automatic export to a configurable destination Yes -
Storage Commitment Specific Parameters
Storage Commit Max Reply Waiting Time Yes -1 [asynchronous]
Specifies the time in seconds that is waited for a storage
commitment event report message. After this time the
association will be terminated
Allowed values:
-1: immediate timeout
0: unlimited waiting time
0 < n: real time in seconds
Basic Worklist Management Specific Parameters
RIS query timeout Yes 240 [minutes]
Specifies the time after which the query is automatically aborted
Allowed values: 1- 300 minutes
Background broad query time interval Yes 0 [no broad query]
Specifies the time until the background query will be repeated.
Allowed values:
0: no broad query
0 < n: real time in minutes
Print Management Specific Parameters
Automatic print to a configurable destination Yes -

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 45 of 61

5. M EDIA I NTERCHANGE

5.1. Implementation Model

The implementation model shall identify the DICOM Application Entities in a specific
implementation and relate the Application Entities to Real-World Activities.

5.1.1. Application Data Flow Diagram

The ELEVA WORKSPOT 1.2 system consists of one single application entity only: the
ELEVA WORKSPOT 1.2 Application Entity (ELEVA AE).

Figure 11 shows the Media Interchange application data flow as a functional overview
of the ELEVA AE.

Display
Contents

ELEVA AE CD-R

Write
Images

Figure 11: Media Interchange Application Data Flow Diagram

The ELEVA AE will act as a FSR when reading the directory of the medium.
The ELEVA AE will act as a FSC/FSU when writing the selected images in a patient
folder onto the CD-R medium.

5.1.2. Functional Definitions of AE’s

This section shall describe in general terms the functions to be performed by the AE,
and the DICOM services used to accomplish these functions.

5.1.2.1. Functional Definition of ELEVA WORKSPOT 1.2

The ELEVA AE is the one and only application entity within the ELEVA WORKSPOT
1.2. It includes the following service class.

Media Storage Service Class

The ELEVA AE can perform the Media Storage service as SCU, with capabilities for
RWA Display Directory (as FSR) and RWA Write Images (as FSC/FSU).

5.1.3. Sequencing of Real World Activities

The following sequence of Real-World activities is supported by the system.

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 46 of 61

DICOM Media Usage

Write images can be initiated by selecting a proper export destination, selecting
requested images and clicking the export button.

Whenever a CD-R has to be written the ELEVA AE first tries to read the DICOMDIR.
The ELEVA AE will compile the updated DICOMDIR and any required DICOM images
into a CD session image; this CD session image will be written to CD-R.

Figure 12: Sequencing of RWA Write Images

An overview of images on a CD-R can be displayed in the user interface.

5.1.4. File Meta Information for Implementation Class and Version

This section shall list the values assigned to the File Meta Information attributes (ref.
[DICOM] PS 3.10) that pertain to the Implementation Class and Version.

The Implementation Class UID and the Implementation Version Name in the File Meta
Header are as specified for Networking.

Table 55: DICOM Implementation Class and Version for ELEVA AE

File Meta Information Version 00, 01

Implementation Class UID 1.3.46.670589.30.1.3

Implementation Version Name PMS_ELEVA_PA_2.1

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 47 of 61

5.2. AE Specifications
The next section contains the specification of the one and only ELEVA WORKSPOT
1.2 Application Entity: ELEVA AE.

5.2.1. ELEVA AE
The ELEVA AE provides Standard Conformance to the DICOM Media Storage Service
and File Format ([DICOM] PS 3.10) and the Media Storage Application Profiles STD-
GEN-CD ([DICOM] PS 3.11) for reading.
ELEVA AE supports multi-patient and multi-session CD-R disks.

The supported Application Profiles, their Roles and the Service Class (SC) options, all
defined in DICOM terminology, are listed in Table 56.

Table 56: AE Related Application Profiles, Real-World Activities, and Roles

Supported Application Profile Real-World Activity Roles SC Option

STD-GEN-CD Display Directory FSR Interchange
Write Images FSC, FSU Interchange

Only adding on of instances is supported for the FSU, deleting is not supported.

5.2.1.1. Real-World Activities

This section describes the real-world activities for the roles and Media Storage Service
Class options supported by the ELEVA AE as listed in Table 56.

5.2.1.1.1. Display Directory

The ELEVA AE will act as an FSR when reading the directory of the medium. This will
result in an overview of the images on the ELEVA WORKSPOT 1.2 screen.

5.2.1.1.1.1. Media Storage Application Profile

As depicted in Table 56, the ELEVA AE supports the RWA Display Directory for the
STD-GEN-CD Application Profile.

5.2.1.1.2. Write Images

When an image transfer to CD-R is initiated then the ELEVA AE acts as an FSC or
FSU using the interchange option to export SOP Instances from the local database to
a CD-R medium.

5.2.1.1.2.1. Media Storage Application Profile

As depicted in Table 56, the ELEVA AE supports the RWA Write Images for the STD-
GEN-CD Application Profile.

5.2.1.1.2.1.1. Options
The DICOMDIR file will be extended when new images are written. In case some
attributes are not present in an image but are specified as mandatory in the
DICOMDIR definition in DICOM Media, a generated value will be filled in.

5.3. Augmented and Private Application Profiles

This section shall be used for the description of augmented and private Application
Profiles.

5.3.1. Augmented Application Profiles

None.

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 48 of 61

5.3.2. Private Application Profiles

None.

5.4. Media Configuration

Not applicable.

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 49 of 61

6. S UPPORT OF C HARACTER S ETS

Any support for character sets beyond the default character repertoire in Network and
Media services shall be described here.
Table 57: Supported DICOM Character Sets of ELEVA WORKSPOT 1.2

ISO Code
Character Set ESC
Defined Term Registration Eleme Character Set
Description Sequence
Number nt
Latin alphabet No. 1 ISO_IR 100 - ISO-IR 6 G0 ISO 646
- ISO-IR 100 G1 Supplementary set of
ISO 8859

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 50 of 61

7. S ECURITY

7.1.1. Secure Transport Connection Profiles

7.1.1.1. The Basic TLS Secure Transport Connection Profile

ELEVA WORKSPOT 1.2 conforms to the Basic TLS Secure Transport Connection
Profile.

Since ELEVA WORKSPOT 1.2 acts only as SCU (except Verify) no IP port is specified
to accept TLS connections.

ELEVA WORKSPOT 1.2 provides a service accessible tool to configure private keys
and certificates of the local and remote DICOM nodes.

7.1.2. Attribute Confidentiality Profiles

7.1.2.1. The Basic Application Level Confidentiality Profile

ELEVA WORKSPOT 1.2 conforms to the Basic Application Level Confidentiality
Profile as de-identifier.

De-identified SOP Instances will be created on DICOM Media if specified by the user.

No instances of the Encrypted Attributes Data Set are created. No Transfer Syntaxes
are supported for encoding/decoding of Encrypted Attributes Data Sets.

Table 58 lists the protected attributes. The terms used to describe the replacement
value can be read as follows:

empty The attribute will have a value of zero length.

n. a. Not applicable, the attribute is not contained in the standard IOD of
ELEVA WORKSPOT 1.2.
anon string The original value is mapped onto a string with a length of max 12
characters UID using the procedure described below.
anon UID The original value is mapped onto a syntactically valid DICOM UID using
the procedure described below.

The above mentioned mapping procedure works as follows:

• The original value is taken as a string of arbitrary length.
• This string is mapped onto a 16-byte value using MD5 hash.
• From this value only the first 8 bytes are used further.
• To create an anon string these first 8 bytes are mapped onto a 12 characters long
string using base 64.
• To create an anon UID the 8 bytes are read as two integers which are used to
create a valid DICOM UID: (ImplClassUID).(DevSerialNu).2.Integer(byte[0-
3]).Integer(byte[4-7])

MD5 hash makes practically sure that different strings are mapped to different 16-byte
values. So the whole procedure ensures that the relationship between SOP Instances
by the means of their UIDs remains consistent.

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 51 of 61

Table 58: Basic Application Level Confidentiality Profile Attributes

Attribute Name Tag Replacement Value
Instance Creator UID 0008,0014 anon UID
SOP Instance UID 0008,0018 anon UID
Accession Number 0008,0050 empty
Institution Name 0008,0080 empty
Institution Address 0008,0081 empty
Referring Physician’s Name 0008,0090 empty
Referring Physician’s Address 0008,0092 n. a.
Referring Physician’s Telephone Numbers 0008,0094 n. a.
Station Name 0008,1010 empty
Study Description 0008,1030 empty
Series Description 0008,103E empty
Institutional Department Name 0008,1040 empty
Physician(s) of Record 0008,1048 empty
Performing Physicians’ Name 0008,1050 empty
Name of Physician(s) Reading Study 0008,1060 empty
Operators’ Name 0008,1070 empty
Admitting Diagnoses Description 0008,1080 empty
Referenced SOP Instance UID 0008,1155 anon UID
Derivation Description 0008,2111 empty
Patient’s Name 0010,0010 empty
Patient ID 0010,0020 anon string
Patient’s Birth Date 0010,0030 empty
Patient’s Birth Time 0010,0032 empty
Patient’s Sex 0010,0040 empty
Other Patient Ids 0010,1000 empty
Other Patient Names 0010,1001 empty
Patient’s Age 0010,1010 empty
Patient’s Size 0010,1020 empty
Patient’s Weight 0010,1030 empty
Medical Record Locator 0010,1090 n. a.
Ethnic Group 0010,2160 empty
Occupation 0010,2180 empty
Additional Patient’s History 0010,21B0 empty
Patient Comments 0010,4000 empty
Device Serial Number 0018,1000 anon string
Protocol Name 0018,1030 empty
Study Instance UID 0020,000D anon UID
Series Instance UID 0020,000E anon UID
Study ID 0020,0010 anon string
Frame of Reference UID 0020,0052 anon UID
Synchronization Frame of Reference UID 0020,0200 n. a.
Image Comments 0020,4000 empty
Requested Attributes Sequence 0040,0275 empty
UID 0040,A124 anon UID
Content Sequence 0040,A730 empty
Storage Media File-set UID 0088,0140 anon UID
Referenced Frame of Reference UID 3006,0024 n. a.
Related Frame of Reference UID 3006,00C2 n. a.

No attributes or attribute values are inserted.

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 52 of 61

8. A NNEXES OF APPLICATION "A NNEX ELEVA WORKSPOT

1.2"

8.1. IOD Contents

8.1.1. Created SOP Instance

This section specifies each IOD created (including private IOD’s). It should specify the
attribute name, tag, VR, and value. The value should specify the range and source
(e.g. user input, Modality Worklist, automatically generated, etc.). For content items in
templates, the range and source of the concept name and concept values should be
specified. Whether the value is always present or not shall be specified.

Abbreviations used in the IOD tables for the column "Presence of Module" are:
ALWAYS The module is always present
CONDITIONAL The module is used under specified condition

Abbreviations used in the Module table for the column "Presence of Value" are:
ALWAYS The attribute is always present with a value
EMPTY The attribute is always present without any value (attribute sent
zero length)
VNAP The attribute is always present and its Value is Not Always Present
(attribute sent zero length if no value is present)
ANAP The attribute is present under specified condition – if present then it
will always have a value
ANAPCV The attribute is present under specified condition – if present then
its Value is Not Always Present (attribute sent zero length if
condition applies and no value is present)
ANAPEV The attribute is present under specified condition – if present then it
will not have any value

8.1.1.1. List of created SOP Classes

Table 59: List of created SOP Classes

SOP Class Name SOP Class UID

Computed Radiography Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.1
Secondary Capture Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.7

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 53 of 61

8.1.1.2. Computed Radiography Image Storage SOP Class

Table 60: IOD of Created Computed Radiography Image Storage SOP Class
Instances

Presence Of
Information Entity Module
Module
Patient Patient Module
Study General Study Module
Study Patient Study Module
Series General Series Module
Series CR Series Module
Equipment General Equipment Module
Image General Image Module
Image Contrast/Bolus Module
Image CR Image Module
Image Image Pixel Module
Image SOP Common Module
Image Overlay Plane Module
Image Modality LUT Module
Image VOI LUT Module
Additional Module

Table 61: Patient Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Patient's Name 0010,0010 PN VNAP MWL/U
SER
Patient ID 0010,0020 LO ALWAYS MWL/A
UTO
Patient's Birth Date 0010,0030 DA VNAP MWL/U
SER
Patient's Sex 0010,0040 CS VNAP MWL/U
SER
Other Patient IDs 0010,1000 LO ANAP MWL/U
SER
Ethnic Group 0010,2160 SH ANAP AUTO
Patient Comments 0010,4000 LT ANAP MWL/U
SER

Table 62: General Study Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Study Instance UID 0020,000D UI ALWAYS MWL/A
UTO
Study Date 0008,0020 DA VNAP AUTO
Study Time 0008,0030 TM VNAP AUTO
Accession Number 0008,0050 SH VNAP MWL/U
SER
Referring Physician's Name 0008,0090 PN VNAP MWL/U
SER
Study ID 0020,0010 SH VNAP MWL/A
UTO
Study Description 0008,1030 LO ANAP MWL/U
SER

Table 63: Patient Study Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Patient’s Age 0010,1010 AS ANAP AUTO
Patient's Size 0010,1020 DS ANAP AUTO

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 54 of 61

Patient's Weight 0010,1030 DS ANAP AUTO

Additional Patient History 0010,21B0 LT ANAP AUTO

Table 64: General Series Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Modality 0008,0060 CS ALWAYS AUTO
Series Instance UID 0020,000E UI ALWAYS AUTO
Series Number 0020,0011 IS ALWAYS AUTO
Laterality 0020,0060 CS VNAP CONFI
G
Performing Physician's Name 0008,1050 PN ANAP MWL
Operators' Name 0008,1070 PN ALWAYS USER
Protocol Name 0018,1030 LO ALWAYS AUTO
Performed Procedure Step Start 0040,0244 DA ANAP AUTO
Date
Performed Procedure Step Start 0040,0245 TM ANAP AUTO
Time
Performed Procedure Step ID 0040,0253 SH ANAP AUTO
Performed Procedure Step 0040,0254 LO ANAP MWL
Description
Referenced Performed 0008,1111 SQ ALWAYS AUTO
Procedure Step Sequence
>Referenced SOP Class UID 0008,1150 UI ALWAYS AUTO
>Referenced SOP Instance UID 0008,1155 UI ALWAYS AUTO

Table 65: CR Series Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Body Part Examined 0018,0015 CS VNAP USER
View Position 0018,5101 CS VNAP USER

Table 66: General Equipment Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Manufacturer 0008,0070 LO ALWAYS AUTO
Institution Name 0008,0080 LO ALWAYS AUTO
Institution Address 0008,0081 ST ALWAYS CONFI
G
Station Name 0008,1010 SH ALWAYS CONFI
G
Institutional Department Name 0008,1040 LO ALWAYS CONFI
G
Manufacturer's Model Name 0008,1090 LO ALWAYS AUTO
Device Serial Number 0018,1000 LO ALWAYS CONFI
G
Software Version(s) 0018,1020 LO ALWAYS AUTO
Spatial Resolution 0018,1050 DS ALWAYS AUTO

Table 67: General Image Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Instance Number 0020,0013 IS ALWAYS AUTO
Content Date 0008,0023 DA ALWAYS AUTO
Content Time 0008,0033 TM ALWAYS AUTO
Patient Orientation 0020,0020 CS VNAP USER
Image Type 0008,0008 CS ALWAYS AUTO
Acquisition Date 0008,0022 DA ALWAYS AUTO
Acquisition Time 0008,0032 TM ALWAYS AUTO
Burned In Annotation 0028,0301 CS ALWAYS AUTO

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 55 of 61

Presentation LUT Shape 2050,0020 CS ALWAYS AUTO

Table 68: Contrast/Bolus Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Contrast/Bolus Agent 0018,0010 LO VNAP AUTO

Table 69: CR Image Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Photometric Interpretation 0028,0004 CS ALWAYS AUTO
Imager Pixel Spacing 0018,1164 DS ALWAYS AUTO
Acquisition Device Processing 0018,1401 LO ALWAYS AUTO
Description

Table 70: Image Pixel Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Samples per Pixel 0028,0002 US 1, 1 ALWAYS AUTO
Rows 0028,0010 US ALWAYS AUTO
Columns 0028,0011 US ALWAYS AUTO
Bits Allocated 0028,0100 US ALWAYS AUTO
Bits Stored 0028,0101 US ALWAYS AUTO
High Bit 0028,0102 US ALWAYS AUTO
Pixel Representation 0028,0103 US 0000 ALWAYS AUTO
Pixel Data 7FE0,0010 O ALWAYS AUTO
W/
OB
Pixel Aspect Ratio 0028,0034 IS ALWAYS AUTO

Table 71: SOP Common Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Specific Character Set 0008,0005 CS ANAPCV AUTO
SOP Class UID 0008,0016 UI ALWAYS AUTO
SOP Instance UID 0008,0018 UI ALWAYS AUTO

Table 72: Overlay Plane Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Overlay Rows 6000,0010 US ANAP AUTO
Overlay Columns 6000,0011 US ANAP AUTO
Overlay Type 6000,0040 CS ANAP AUTO
Overlay Origin 6000,0050 SS ANAP AUTO
Overlay Bits Allocated 6000,0100 US ANAP AUTO
Overlay Bit Position 6000,0102 US ANAP AUTO
Overlay Data 6000,3000 O ANAP AUTO
W/
OB

Table 73: Modality LUT Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Rescale Intercept 0028,1052 DS ALWAYS AUTO
Rescale Slope 0028,1053 DS ALWAYS AUTO
Rescale Type 0028,1054 LO ALWAYS AUTO

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 56 of 61

Table 74: VOI LUT Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Window Center 0028,1050 DS ALWAYS AUTO
Window Width 0028,1051 DS ALWAYS AUTO

Table 75: Additional Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Medical Alerts 0010,2000 LO ALWAYS AUTO
Contrast Allergies 0010,2110 LO ALWAYS AUTO
Additional Patient History 0010,21B0 LT ALWAYS AUTO
Pregnancy Status 0010,21C0 US ALWAYS AUTO
Image and Fluoroscopy Area 0018,115E DS ALWAYS AUTO
Dose Product
Pixel Spacing 0028,0030 DS ALWAYS AUTO
Requesting Physician 0032,1032 PN ALWAYS AUTO
Requesting Service 0032,1033 LO ALWAYS AUTO
Requested Procedure 0032,1060 LO ALWAYS AUTO
Description
Special Needs 0038,0050 LO ALWAYS AUTO
Patient State 0038,0500 LO ALWAYS AUTO
Performed Station AE Title 0040,0241 AE ANAP AUTO
Performed Procedure Step Start 0040,0244 DA ANAP AUTO
Date
Performed Procedure Step Start 0040,0245 TM ANAP AUTO
Time
Performed Procedure Step End 0040,0250 DA ANAP AUTO
Date
Performed Procedure Step End 0040,0251 TM ANAP AUTO
Time
Performed Procedure Step 0040,0252 CS ANAP AUTO
Status
Performed Procedure Step 0040,0254 LO ANAP AUTO
Description
Requested Procedure ID 0040,1001 SH ALWAYS AUTO
Reason for the Requested 0040,1002 LO ALWAYS AUTO
Procedure
Requested Procedure Priority 0040,1003 SH ALWAYS AUTO
Patient Transport Arrangements 0040,1004 LO ALWAYS AUTO
Names of Intended Recipients 0040,1010 PN ALWAYS AUTO
of Results
Requested Procedure 0040,1400 LT ALWAYS AUTO
Comments
Reason for the Imaging Service 0040,2001 LO ALWAYS AUTO
Request (RETIRED)
Issue Date of Imaging Service 0040,2004 DA ALWAYS AUTO
Request
Imaging Service Request 0040,2400 LT ALWAYS AUTO
Comments

8.1.1.3. Secondary Capture Image Storage SOP Class

Table 76: IOD of Created Secondary Capture Image Storage SOP Class
Instances

Presence Of
Information Entity Module
Module
Patient Patient Module
Study General Study Module
Study Patient Study Module
Series General Series Module

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 57 of 61

Equipment General Equipment Module

Equipment SC Equipment Module
Image General Image Module
Image Image Pixel Module
Image SC Image Module
Image SOP Common Module
Image Modality LUT Module
Image VOI LUT Module
Additional Module

Table 77: Patient Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Patient's Name 0010,0010 PN VNAP MWL/U
SER
Patient ID 0010,0020 LO ALWAYS MWL/U
SER
Patient's Birth Date 0010,0030 DA VNAP MWL/U
SER
Patient's Sex 0010,0040 CS VNAP MWL/U
SER
Other Patient IDs 0010,1000 LO ANAP MWL/U
SER
Ethnic Group 0010,2160 SH ANAP MWL/U
SER
Patient Comments 0010,4000 LT ANAP MWL/U
SER

Table 78: General Study Module

Table 79: Patient Study Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Patient’s Age 0010,1010 AS ANAP MWL/A
UTO
Patient's Weight 0010,1030 DS VNAP MWL/A
UTO
Additional Patient History 0010,21B0 LT VNAP MWL/A
UTO

Table 80: General Series Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Series Instance UID 0020,000E UI ALWAYS AUTO
Series Number 0020,0011 IS ALWAYS AUTO
Laterality 0020,0060 CS VNAP CONFI
G

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 58 of 61

Performing Physician's Name 0008,1050 PN ANAP MWL

Operators' Name 0008,1070 PN ALWAYS AUTO
Body Part Examined 0018,0015 CS VNAP AUTO
Protocol Name 0018,1030 LO ALWAYS AUTO
Performed Procedure Step Start 0040,0244 DA ANAP AUTO
Date
Performed Procedure Step Start 0040,0245 TM ANAP AUTO
Time
Performed Procedure Step ID 0040,0253 SH ANAP AUTO
Performed Procedure Step 0040,0254 LO ANAP AUTO
Description
Referenced Performed 0008,1111 SQ ALWAYS AUTO
Procedure Step Sequence
>Referenced SOP Class UID 0008,1150 UI ALWAYS AUTO
>Referenced SOP Instance UID 0008,1155 UI ALWAYS AUTO

Table 81: General Equipment Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Manufacturer 0008,0070 LO ALWAYS AUTO
Institution Name 0008,0080 LO ALWAYS CONFI
G
Institution Address 0008,0081 ST ALWAYS CONFI
G
Station Name 0008,1010 SH ALWAYS CONFI
G
Institutional Department Name 0008,1040 LO ALWAYS CONFI
G
Manufacturer's Model Name 0008,1090 LO ALWAYS AUTO
Software Version(s) 0018,1020 LO ALWAYS AUTO
Spatial Resolution 0018,1050 DS ALWAYS AUTO

Table 82: SC Equipment Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Conversion Type 0008,0064 CS ALWAYS AUTO
Modality 0008,0060 CS ALWAYS AUTO

Table 83: General Image Module

Table 84: Image Pixel Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Samples per Pixel 0028,0002 US 1, 1 ALWAYS AUTO
Photometric Interpretation 0028,0004 CS ALWAYS AUTO
Rows 0028,0010 US ALWAYS AUTO
Columns 0028,0011 US ALWAYS AUTO
Bits Allocated 0028,0100 US ALWAYS AUTO

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 59 of 61

Bits Stored 0028,0101 US ALWAYS AUTO

High Bit 0028,0102 US ALWAYS AUTO
Pixel Representation 0028,0103 US 0000 ALWAYS AUTO
Pixel Data 7FE0,0010 O ALWAYS AUTO
W/
OB
Planar Configuration 0028,0006 US ALWAYS AUTO
Pixel Aspect Ratio 0028,0034 IS ALWAYS AUTO

Table 85: SC Image Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Date of Secondary Capture 0018,1012 DA ALWAYS AUTO
Time of Secondary Capture 0018,1014 TM ALWAYS AUTO

Table 86: SOP Common Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Specific Character Set 0008,0005 CS ANAPCV AUTO
SOP Class UID 0008,0016 UI ALWAYS AUTO
SOP Instance UID 0008,0018 UI ALWAYS AUTO

Table 87: Modality LUT Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Rescale Intercept 0028,1052 DS ALWAYS AUTO
Rescale Slope 0028,1053 DS ALWAYS AUTO
Rescale Type 0028,1054 LO ALWAYS AUTO

Table 88: VOI LUT Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Window Center 0028,1050 DS ALWAYS AUTO
Window Width 0028,1051 DS ALWAYS AUTO

Table 89: Additional Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Medical Alerts 0010,2000 LO ANAP MWL/U
SER
Contrast Allergies 0010,2110 LO ANAP MWL/U
SER
Additional Patient History 0010,21B0 LT ANAP MWL/U
SER
Pregnancy Status 0010,21C0 US ANAP MWL/U
SER
Special Needs 0038,0050 LO ANAP MWL/U
SER
Patient State 0038,0500 LO ANAP MWL/U
SER

8.1.2. Usage of Attributes from Received IOD

Not applicable.

8.1.3. Attribute Mapping

The following table shows the relation between BWLM and MPPS and image storage
attributes.

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 60 of 61

Table 90: Attribute Mapping during Modality Workflow

BWLM MPPS Image IOD

Name
Tag Create Tag Set Tag Tag
Accession Number 0008,0050 0008,0050 - 0008,0050
Modality - 0008,0060 - 0008,0060
Referring Physician's Name 0008,0090 - - 0008,0090
Operators’ Name - - 0008,1070 0008,1070
Referenced Study Sequence 0008,1110 0008,1110 - 0008,1110
Referenced Image Sequence - - (0008,1140) -
> Referenced SOP Class UID
- - 0008,1150 0008,0016
SOP Class UID
> Referenced SOP Instance UID
- - 0008,1155 0008,0018
SOP Instance UID
Patient's Name 0010,0010 0010,0010 - 0010,0010
Patient ID 0010,0020 0010,0020 - 0010,0020
Issuer of Patient ID 0010,0021 0010,0021 - 0010,0021
Patient's Birth Date 0010,0030 0010,0030 - 0010,0030
Patient's Sex 0010,0040 0010,0040 - 0010,0040
Other Patient IDs 0010,1000 0010,1000 - 0010,1000
Medical Alerts 0010,2000 - - 0010,2000
Contrast Allergies 0010,2110 - - 0010,2110
Ethnic group 0010,2160 - - 0010,2160
Additional Patient History 0010,21B0 - - 0010,21B0
Pregnancy Status 0010,21C0 - - 0010,21C0
Patient Comments 0010,4000 - - 0010,4000

Protocol Name - - 0018,1030 0018,1030

Study Instance UID 0020,000D 0020,000D - 0020,000D

Series Instance UID 0020,000E 0020,000E
Study ID - 0020,0010 - 0020,0010
Requesting Service 0032,1033 - - 0032,1033
Requested Procedure Description 0032,1060 0032,1060 - -
3
Requested Procedure Code Sequence
0032,1064 0008,1032 0008,1032 0008,1032
Performed Procedure Code Sequence
Special Needs 0038,0050 - - 0038,0050
Patient State 0038,0500 - - 0038,0500
4
Scheduled Procedure Step Description 0040,0007 - 0040,0007
0040,0007
Performed Procedure Step Description 0040,0254 - 0040,0254
4
Scheduled Protocol Code Sequence 0040,0008
0040,0008 0040,0260 0040,0260
Performed Protocol Code Sequence 0040,0260
Scheduled Procedure Step ID 0040,0009 0040,0009 - 0040,0009
Performed Procedure Step Start Date - 0040,0244 - 0040,0244
Performed Procedure Step Start Time - 0040,0245 - 0040,0245
Performed Procedure Step ID - 0040,0253 - 0040,0253
Requested Procedure ID 0040,1001 0040,1001 - 0040,1001
Note 1: Value accumulated from all performed acquisitions including dropped (repeated) acquisitions.
Note 2: Image related specific value.
Note 3: If procedure is performed as requested.
Note 4: If protocol is performed as scheduled.

8.1.4. Coerced/Modified fields

Not applicable.

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007
DICOM Conformance Statement Page 61 of 61

8.2. Data Dictionary of Private Attributes

Not applicable.

8.3. Coded Terminology and Templates

Not applicable.

8.4. Grayscale Image consistency

The monitor of ELEVA WORKSPOT 1.2 system can be calibrated according
Grayscale Display Function Standard.

The pixel values exported and printed should be interpreted as P-Value. If the export
destination or the printer does not support GSDF, ELEVA WORKSPOT 1.2 provides
calibration tools to adapt to this device to afford grayscale image consistency. The
calibration takes into account ambient luminance and lightbox luminance.

8.5. Standard Extended/Specialized/Private SOPs

Not applicable.

8.6. Private Transfer Syntaxes

Not applicable.

Document Number: XBS 231-060725 ELEVA WORKSPOT 1.2 13 Mar 2007

SYNAPSE3D UserManual PDF
No ratings yet
SYNAPSE3D UserManual PDF
436 pages
Spek Teknis EM1000 - Complete
No ratings yet
Spek Teknis EM1000 - Complete
7 pages
Agfa Dicom PDF
No ratings yet
Agfa Dicom PDF
93 pages
DICOM Conformance Statement Eleva Workspot 2.0
No ratings yet
DICOM Conformance Statement Eleva Workspot 2.0
81 pages
MultiDiagnost_Eleva dicom r4.1
No ratings yet
MultiDiagnost_Eleva dicom r4.1
94 pages
DICOM Conformance Statement MR 5.1.12 Release Systems
No ratings yet
DICOM Conformance Statement MR 5.1.12 Release Systems
134 pages
PHILIPS ESSENTA DR DICOM
No ratings yet
PHILIPS ESSENTA DR DICOM
94 pages
DICOM_Conformance_Statement_HD11_XE_R1.1.x.x
No ratings yet
DICOM_Conformance_Statement_HD11_XE_R1.1.x.x
256 pages
E7 E5 A70 A50 A30 Release 1.5.6+ DICOM Conformance Statement
No ratings yet
E7 E5 A70 A50 A30 Release 1.5.6+ DICOM Conformance Statement
105 pages
MultiDiagnost Eleva FD Dicom R6.2
100% (2)
MultiDiagnost Eleva FD Dicom R6.2
112 pages
DICOMConformance Statement Mammo Diagnost DR
0% (1)
DICOMConformance Statement Mammo Diagnost DR
79 pages
DICOM Conformance Statement MultiDiagnost Eleva FD R6.1
100% (3)
DICOM Conformance Statement MultiDiagnost Eleva FD R6.1
115 pages
DICOM_Conformance_Statement_for_BV_FamilyR2.3_and_VeradiusR1.1_September_2013
No ratings yet
DICOM_Conformance_Statement_for_BV_FamilyR2.3_and_VeradiusR1.1_September_2013
130 pages
DICOM Conformance Statement Achieva R1.5
No ratings yet
DICOM Conformance Statement Achieva R1.5
92 pages
DICOM Conformance Statement MobileDiagnost M50
No ratings yet
DICOM Conformance Statement MobileDiagnost M50
83 pages
E7 E5 A70 A50 Rel 1.7.x DICOM Conformance Statement
No ratings yet
E7 E5 A70 A50 Rel 1.7.x DICOM Conformance Statement
104 pages
DCS X7i Us PNL
No ratings yet
DCS X7i Us PNL
155 pages
DICOM Conformance Statement MR R5 (July 2017)
No ratings yet
DICOM Conformance Statement MR R5 (July 2017)
145 pages
DICOM_Conformance_Statement_Xcelera_2.2_L1_SP1
No ratings yet
DICOM_Conformance_Statement_Xcelera_2.2_L1_SP1
153 pages
DICOM DSI_R7.2.x
No ratings yet
DICOM DSI_R7.2.x
59 pages
DICOM Allura Xper FD10 Release 1.2
No ratings yet
DICOM Allura Xper FD10 Release 1.2
56 pages
Dicom: Conformance Statement Digital Diagnost Release 1.4
No ratings yet
Dicom: Conformance Statement Digital Diagnost Release 1.4
80 pages
E7 E5 ECVx A70 A50 A30 Rel 4.0.x A DICOM Conformance Statement PDF
No ratings yet
E7 E5 ECVx A70 A50 A30 Rel 4.0.x A DICOM Conformance Statement PDF
110 pages
DICOM Conformance
100% (1)
DICOM Conformance
144 pages
Dicom Conformance Statement dicomPACS DX-R 2018-03-01
No ratings yet
Dicom Conformance Statement dicomPACS DX-R 2018-03-01
10 pages
61873_D1070525_220516_en
No ratings yet
61873_D1070525_220516_en
28 pages
drSoftwareV5 Dicom 6K9324
No ratings yet
drSoftwareV5 Dicom 6K9324
61 pages
DICOM PHILIPS DSI_R7.1.x
No ratings yet
DICOM PHILIPS DSI_R7.1.x
59 pages
CrSoftwareV5 2 Dicom 6K9319
No ratings yet
CrSoftwareV5 2 Dicom 6K9319
71 pages
DICOM Conformance Statement IE33 R5.1.x.x and IU22 R5.1.x.x
No ratings yet
DICOM Conformance Statement IE33 R5.1.x.x and IU22 R5.1.x.x
145 pages
US3046_CH07_HD9_Connectivity
No ratings yet
US3046_CH07_HD9_Connectivity
27 pages
GEHC-DICOM-Conformance_SenographePristina9_DOC3075145_Rev1
No ratings yet
GEHC-DICOM-Conformance_SenographePristina9_DOC3075145_Rev1
161 pages
MammoScape 1.0.1 DICOM Conformance Statement 2024 08
No ratings yet
MammoScape 1.0.1 DICOM Conformance Statement 2024 08
69 pages
DICOM Conformance Statement P20
No ratings yet
DICOM Conformance Statement P20
145 pages
drx-revolution-v5-6-dicom-6K9336
No ratings yet
drx-revolution-v5-6-dicom-6K9336
68 pages
Epiq Elite Elite Advanced E7 E5 CVX I A70 A50 A30 Rel 6 0 X A Dicom Conformance Statement
100% (2)
Epiq Elite Elite Advanced E7 E5 CVX I A70 A50 A30 Rel 6 0 X A Dicom Conformance Statement
112 pages
DICOM
No ratings yet
DICOM
44 pages
NX 1.0 DICOM Conformance Statement Draft
No ratings yet
NX 1.0 DICOM Conformance Statement Draft
94 pages
PHILIPS AZURION DICOM 2.1
No ratings yet
PHILIPS AZURION DICOM 2.1
96 pages
E-CUBE 9 DICOM Conformance Statement
No ratings yet
E-CUBE 9 DICOM Conformance Statement
119 pages
Dicom
No ratings yet
Dicom
23 pages
Dicom Communication Protocols
No ratings yet
Dicom Communication Protocols
23 pages
Kodak Enterprise Gateway DICOM Conformance Statement
No ratings yet
Kodak Enterprise Gateway DICOM Conformance Statement
43 pages
E-CUBE 7 DICOM Conformance Statement
No ratings yet
E-CUBE 7 DICOM Conformance Statement
111 pages
DRX Software V5X Dicom
No ratings yet
DRX Software V5X Dicom
60 pages
Sony Up-Df750: DICOM Conformance Statement
No ratings yet
Sony Up-Df750: DICOM Conformance Statement
25 pages
E-CUBE 12 DICOM Conformance Statement
No ratings yet
E-CUBE 12 DICOM Conformance Statement
130 pages
DRX 1 Family Dicom v5 6b 6K9327 PDF
No ratings yet
DRX 1 Family Dicom v5 6b 6K9327 PDF
67 pages
Lect 4 DICOM
No ratings yet
Lect 4 DICOM
45 pages
2 2
No ratings yet
2 2
119 pages
DOC2510132 LOGIQ P8P9P10 DICOM Conformance Statement Rev1
No ratings yet
DOC2510132 LOGIQ P8P9P10 DICOM Conformance Statement Rev1
215 pages
TE7 - CE&FDA - DICOM Quick Guide & FAQ Manul - V2.0 - EN
No ratings yet
TE7 - CE&FDA - DICOM Quick Guide & FAQ Manul - V2.0 - EN
50 pages
0pescope Pleno
No ratings yet
0pescope Pleno
28 pages
NX 2.0 DICOM Conformance Statement
0% (1)
NX 2.0 DICOM Conformance Statement
93 pages
Technical Publications: Volume Share 5 - Advantage Workstation 4.6 Dicom Conformance Statement
No ratings yet
Technical Publications: Volume Share 5 - Advantage Workstation 4.6 Dicom Conformance Statement
188 pages
crSoftwareV5-4 Dicom 8J3914 PDF
100% (1)
crSoftwareV5-4 Dicom 8J3914 PDF
74 pages
NNT-iRYS Conformance Statement
No ratings yet
NNT-iRYS Conformance Statement
21 pages
Tic Resonance Gehc
No ratings yet
Tic Resonance Gehc
138 pages
Technical Publications: Senographe 2000 D Review Workstation Conformance Statement For Dicom V3.0
No ratings yet
Technical Publications: Senographe 2000 D Review Workstation Conformance Statement For Dicom V3.0
78 pages
Merge PACS v7.0 DICOM Conformance Statement
No ratings yet
Merge PACS v7.0 DICOM Conformance Statement
47 pages
Next-Generation switching OS configuration and management: Troubleshooting NX-OS in Enterprise Environments
From Everand
Next-Generation switching OS configuration and management: Troubleshooting NX-OS in Enterprise Environments
Mamta Devi
No ratings yet
Alcatel-Lucent Network Routing Specialist II (NRS II) Self-Study Guide: Preparing for the NRS II Certification Exams
From Everand
Alcatel-Lucent Network Routing Specialist II (NRS II) Self-Study Guide: Preparing for the NRS II Certification Exams
Glenn Warnock
No ratings yet
2 Inch Mattress Service Manual SM 5789847-1EN_1 (1)
No ratings yet
2 Inch Mattress Service Manual SM 5789847-1EN_1 (1)
24 pages
DOC-20250528-WA0014.
No ratings yet
DOC-20250528-WA0014.
5 pages
NEUSOFT 128 FLASH PRO. M. V1.6
No ratings yet
NEUSOFT 128 FLASH PRO. M. V1.6
156 pages
NEUVIZ 128 CALI.M. V1.4
No ratings yet
NEUVIZ 128 CALI.M. V1.4
87 pages
Zonare Z.One Ultrasound Service manual
No ratings yet
Zonare Z.One Ultrasound Service manual
225 pages
In-room AW mouse interface kit - Service Manual Addendum_SM_5765799-1EN_1 (1)
No ratings yet
In-room AW mouse interface kit - Service Manual Addendum_SM_5765799-1EN_1 (1)
26 pages
ServiceVBS3100 2D621-260EN
No ratings yet
ServiceVBS3100 2D621-260EN
39 pages
ZIEHM 7000 block diagram
No ratings yet
ZIEHM 7000 block diagram
1 page
2 Inch Mattress - Service Manual 5807536-1EN_1 (1)
No ratings yet
2 Inch Mattress - Service Manual 5807536-1EN_1 (1)
22 pages
Mammography Site Readiness brochure_1800000005714266
No ratings yet
Mammography Site Readiness brochure_1800000005714266
12 pages
5201dba8-b823-4a12-aad0-a7f225463f5a
No ratings yet
5201dba8-b823-4a12-aad0-a7f225463f5a
12 pages
siemens-healthineers_xp_mobilett-elara-max_cleaning-guide
No ratings yet
siemens-healthineers_xp_mobilett-elara-max_cleaning-guide
6 pages
senographe-600ts
No ratings yet
senographe-600ts
3 pages
SEDECAL X Service manual
No ratings yet
SEDECAL X Service manual
100 pages
HDI 3000 R47.08 DICOM
No ratings yet
HDI 3000 R47.08 DICOM
22 pages
Esaote Mri r3.1 Dicom
No ratings yet
Esaote Mri r3.1 Dicom
98 pages
ESAOTE MRI R3.6 DICOM
No ratings yet
ESAOTE MRI R3.6 DICOM
86 pages
OEC One Mobile C-Arm X-ray Product Service Manual_SM_6888001-1EN_11
No ratings yet
OEC One Mobile C-Arm X-ray Product Service Manual_SM_6888001-1EN_11
189 pages
MUSICA Acquisition Workstation (NX)_Office_Viewer_Getting_Started_Folder_4430_C_(English)
No ratings yet
MUSICA Acquisition Workstation (NX)_Office_Viewer_Getting_Started_Folder_4430_C_(English)
2 pages
Senographe_Crystal_Datasheet_-_DOC1454216_Rev31
No ratings yet
Senographe_Crystal_Datasheet_-_DOC1454216_Rev31
4 pages
LOGIQ P5_A5 3RD PROBE PORT INSTALLATION_IM_5175128_3
No ratings yet
LOGIQ P5_A5 3RD PROBE PORT INSTALLATION_IM_5175128_3
22 pages
C-Arm Comparison Chart March 08
No ratings yet
C-Arm Comparison Chart March 08
26 pages
Pegasys DICOM 3
No ratings yet
Pegasys DICOM 3
28 pages
Axb4-210 812 02 09 02
No ratings yet
Axb4-210 812 02 09 02
64 pages
[ZENIS(OSCAR Series) User's Manual Eng Ver1.1_CE 2460
No ratings yet
[ZENIS(OSCAR Series) User's Manual Eng Ver1.1_CE 2460
53 pages
SP 5500 V5.1 1.0
No ratings yet
SP 5500 V5.1 1.0
17 pages
DR6003 - MobiEye700 Operation - V2.0 - EN
100% (1)
DR6003 - MobiEye700 Operation - V2.0 - EN
83 pages
Prosound 3500Sv: Specifications Diagnostic Ultrasound System
No ratings yet
Prosound 3500Sv: Specifications Diagnostic Ultrasound System
12 pages
CT INSTRUMENTATION
No ratings yet
CT INSTRUMENTATION
37 pages
Planning Instructions for Use for Brachytherapy Planning
No ratings yet
Planning Instructions for Use for Brachytherapy Planning
164 pages
Reshin MD17G
No ratings yet
Reshin MD17G
1 page
D1T2 - How To Hack Medical Imaging Applications Via DICOM - Maria Nedyak
No ratings yet
D1T2 - How To Hack Medical Imaging Applications Via DICOM - Maria Nedyak
64 pages
EcoView 9 Plus-12p Small
0% (1)
EcoView 9 Plus-12p Small
6 pages
FORUM BOOK EN 31 200 0010III - Indd
No ratings yet
FORUM BOOK EN 31 200 0010III - Indd
28 pages
Drypro832 PreInstallGude 0921YH220B 070627 Fix
No ratings yet
Drypro832 PreInstallGude 0921YH220B 070627 Fix
23 pages
LOGIQ Book XP Enhanced
No ratings yet
LOGIQ Book XP Enhanced
30 pages
M517-E124 (DAR-7500 DR Console DICOM MWM Network WL)
No ratings yet
M517-E124 (DAR-7500 DR Console DICOM MWM Network WL)
10 pages
Blog'o'Less - How-To - Dcm4chee On Ubuntu
No ratings yet
Blog'o'Less - How-To - Dcm4chee On Ubuntu
16 pages
User'S Guide: Sectra Liteview
No ratings yet
User'S Guide: Sectra Liteview
27 pages
Gendex GX Pan User Manual
50% (2)
Gendex GX Pan User Manual
11 pages
Fluoroscopy PERLOVE
100% (1)
Fluoroscopy PERLOVE
8 pages
MedITEX IVF Software - Modules
No ratings yet
MedITEX IVF Software - Modules
2 pages
MX8000 Quad Datasheet
No ratings yet
MX8000 Quad Datasheet
3 pages
Indraprastha Apollo Hospitals
0% (1)
Indraprastha Apollo Hospitals
43 pages
Model SC-5 Portable Color Doppler Ultrasound Scanner
No ratings yet
Model SC-5 Portable Color Doppler Ultrasound Scanner
6 pages
Digital Mammography: Mammograph FFDM - Mammograph D-Tomo
No ratings yet
Digital Mammography: Mammograph FFDM - Mammograph D-Tomo
21 pages
Brochure DicomPACS DX-R - EN
No ratings yet
Brochure DicomPACS DX-R - EN
44 pages
EFIGS 032-0252P1 Reva VxWinDICOM
No ratings yet
EFIGS 032-0252P1 Reva VxWinDICOM
114 pages