CT 2014a

syngo CT 2014A
DICOM Conformance Statement
www.siemens.com/healthcare
This product is provided with a CE mark in accordance with the
regulations stated in Council Directive 93/42/EEC of June 14th,
1993, concerning Medical Devices. 0.0
The CE marking applies only to Medical Devices which have been

put on the market according to the above-mentioned EC Directive.
Unauthorized changes to this product are not covered by the CE
mark and the related Declaration of Conformity. 0.0
The original language of this document is English. 0.0

Table of Contents 0.0
Introduction
A DICOM Conformance Statement

Network
A.1 Implementation Models
A.2 AE Specifications
A.3 Communication Profiles
A.4 Extensions/Specializations/Privatizations
A.5 Configuration
A.6 Support of Extended Character Sets
B DICOM Conformance Statement

Media Storage
B.1 Implementation Model
B.2 Application Entity Specifications
B.3 Augmented and Private Profiles
B.4 Extensions, Specializations and Privatizations of SOP

Classes and Transfer Syntaxes
B.5 Configuration
B.6 Support of Extended Character Sets
Annex
0.0
Version syngo CT 2014A 3

July 2013
Table of Contents DICOM
0.0
4 DICOM Conformance Statement syngo

Introduction 0.0
Overview 0.0
This DICOM Conformance Statement is written according to part

PS 3.2 of [1]. 0.0
The applications described in this conformance statement are

implemented in the Siemens SOMATOM products using soft-
ware Somaris/5 syngo CT 2014A (internal: VB42A). 0.0
The Somaris/5 DICOM network implementation acts as SCU and

SCP for the DICOM Verification, Storage, Storage Commitment
Push Model, and Query/Retrieve Services. It acts as SCU for the
DICOM Print Management Service, the Modality Worklist Ser-
vice, and the Performed Procedure Step Service. 0.0
These services are described in "Part I". 0.0
The Somaris/5 DICOM Media Storage Service implementation

acts as FSC, FSU, and FSR for the specified application profiles
and the related SOP Class instances. These services are
described in "Part II". 0.0
Somaris/5 is based on a Siemens common medical platform.

This platform is shared with other Siemens modalities in order
to provide a common look and feel and common interoperabil-
ity features. 0.0
In this document parts of the Siemens common medical plat-

form are referenced by the terms "syngo®"1, "MedCom", and
"CSA". 0.0
As Somaris/5 is a syngo based product, this DICOM Conform-

ance Statement is based on the corresponding syngo template
[2]. 0.0
1. ’syngo’ and ’We speak syngo’ are registered trademarks of Siemens AG
0.0

July 2013
Introduction DICOM Conformance Statement
Audience 0.0
This document is intended for hospital staff, health system inte-

grators, hospital IT-managers, and software designers or imple-
mentors. It is assumed that the reader has a working under-
standing of DICOM. 0.0
0.0

DICOM Conformance Statement Introduction
Scope 0.0
This DICOM Conformance Statement refers to Siemens

SOMATOM products using software Somaris/5. The following
table relates software names to Siemens products. 0.0
0.0
Siemens Product Software Name Internal

Sensation 16 0 Somaris/5 syngo CT 2014A 0 VB42A 0
Sensation Cardiac 0 Somaris/5 syngo CT 2014A 0 VB42A 0
Sensation Cardiac 64 0 Somaris/5 syngo CT 2014A 0 VB42A 0
Sensation Open 0 Somaris/5 syngo CT 2014A 0 VB42A 0
Emotion Duo 0 Somaris/5 syngo CT 2014A 0 VB42A 0
Emotion 0 Somaris/5 syngo CT 2014A 0 VB42A 0
Emotion 6 0 Somaris/5 syngo CT 2014A 0 VB42A 0
Emotion 16 0 Somaris/5 syngo CT 2014A 0 VB42A 0
Emotion 6-slice configuration 0 Somaris/5 syngo CT 2014A 0 VB42A 0
Emotion 16-slice Somaris/5 syngo CT 2014A 0 VB42A 0
configuration 0
Definitions 0.0
❏ DICOM: Digital Imaging and Communications in Medicine

❏ DIMSE: DICOM Message Service Element
❏ DIMSE-C: DICOM Message Service Element with Composite
information objects
0.0

July 2013
Acronyms and Abbreviations 0.0
❏ ACR: American College of Radiology

❏ AE: DICOM Application Entity
❏ ASCII: American Standard Code for Information Interchange
❏ FSC: File Set Creator
❏ FSR: File Set Reader
❏ FSU: File Set Updater
❏ HIS: Hospital Information System
❏ IOD: DICOM Information Object Definition
❏ ISO: International Standard Organization
❏ NEMA: National Electrical Manufacturers Association
❏ O: Optional Key Attribute
❏ R: Required Key Attribute
❏ RIS: Radiology Information System
❏ RWA: Real-World Activity
❏ PDU: DICOM Protocol Data Unit
❏ SCU: DICOM Service Class User (DICOM client)
❏ SCP: DICOM Service Class Provider (DICOM server)
❏ SOP: DICOM Service-Object Pair
❏ U: Unique Key Attribute
❏ UID: Unique Identifier
❏ VR: Value Representation
0.0

DICOM Conformance Statement Introduction
References 0.0
[1]: Digital Imaging and Communications in Medicine (DICOM)

3.0, NEMA PS 3.1-3.14
DICOM Standard is under continuous maintenance, the current
official version is available at: http://dicom.nema.org 0.0
[2]: syngo VE32B DICOM Conformance Statement 0.0
0.0
0.0

July 2013
Connectivity and Interoperability 0.0
The implementation of the Somaris/5 DICOM interface has been

carefully tested to assure correspondence with this Conform-
ance Statement. But the Conformance Statement and the
DICOM standard do not guarantee interoperability of Siemens
modalities and modalities of other vendors. The user must com-
pare the relevant Conformance Statements and if a successful
interconnection should be possible, the user is responsible to
specify an appropriate test suite and to validate the interopera-
bility, which is required. A network environment may need addi-
tional functions out of the scope of DICOM. 0.0
0.0
0.0

PART DICOM
A Conformance Statement
Network
0.0
Version syngo CT 2014A A-1

July 2013
Network DICOM Conformance Statement
0.0
A-2 DICOM Conformance Statement syngo

CHAPTER
A.1 Implementation Models A.0
Verification A.0
The Verification service class defines an application-level class

of service which allows for the operator to verify the ability of an
application on a remote node to respond to DICOM messages.
The DICOM Service Tool application supports the Verification
service to act as SCU. A.0
The other direction – responding to Verification requests from

remote applications – is handled by the Storage SCP applica-
tion. A.0
Application Data Flow Diagram A.0
The Somaris/5 DICOM network implementation acts as SCU for

the C-ECHO DICOM network service. The product target operat-
ing system is Windows XP. A.0
DICOM Standard Interface
Service A
User Verification Verification

C-ECHO
Interface A SCU SCP
DICOM Application
A.0
Functional Definitions of Application Entities A.0
The DICOM Service Tool application opens an association to an

application on the remote node and sends a Verification mes-
sage to verify that the remote application can respond to DICOM
messages. A.0
Sequencing of Real-World Activities A.0
Newly configured data of a remote AE have to be saved first,

before a "verification" of these data is possible. A.0
0.0
Version syngo CT 2014A A.1-1

July 2013
Network – Implementation Models DICOM Conformance Statement
Storage A.0
The Somaris/5 DICOM Application Entity both originates associ-

ations for Storage of DICOM Composite Information Objects in
Remote Application Entities and accepts association requests for
Storage from Remote Application Entities. A.0

SCP for the C-STORE DICOM network service and as SCP for the
C-ECHO DICOM network service. The product target operating
system is Windows XP. A.0
A DICOM Standard Interface
“Send to ... “ DICOM

User Storage SCU Receiver
C-STORE
Interface A (Storage
SCP)
DICOM Application
DICOM
DatabaseA Storage SCP Sender
C-STORE
Verification SCP C-ECHO (Storage
SCU) A.0
DICOM Application
A
0.0
A.1-2 DICOM Conformance Statement syngo

DICOM Conformance Statement Network – Implementation Models
The Storage SCU is invoked by the job control interface that is

responsible for processing network archiving tasks. The job con-
sists of data describing the composite image objects selected for
storage and the destination. An association is negotiated with
the destination application entity and the image data is trans-
ferred using the C-STORE DIMSE-Service. Status of the transfer
is reported to the job control interface. A.0
The Storage SCP component of the Siemens Somaris/5 DICOM

application is operating as background server process. It is exist-
ing, when the machine is powered on and waits for Storage
association requests. Upon accepting an association with a
negotiated Presentation Context it starts to receive the Compos-
ite Image Objects and imports them to local database. Verifica-
tion requests will be processed and responded to by Storage SCP
component, too. A.0
Not applicable. A.0
0.0

July 2013
Storage Commitment A.0
The Storage Commitment service class defines an application-

level class of service which facilitates the commitment to stor-
age. It performs an additional task of commitment of composite
objects apart from the network based storage of images as
defined by the Storage Service class. The Somaris/5 DICOM
implementation supports the Storage Commitment Push Model
as SCU. A.0

the Storage Commitment Push Model Service using the Storage
Commitment Service Class. The product target operating sys-
tem is Windows XP. A.0

Job
complete
N-ACTION
DICOM
SC SCU Receiver
N-EVENT- (SC SCP)
Update REPORT
flags A.0 DICOM Application
0.0

With each successfully completed send job the Somaris/5

DICOM application will create a Storage Commitment Push
Model Identifier from the SOP Instances sent. Then a Storage
Commit Request is triggered. Depending on configuration, the
Somaris/5 DICOM application will keep the association open for
responses with a configurable time-out, or closes the associa-
tion and expects responses on a different association that has to
be established by the remote Storage Commitment SCP. A.0
The commitment status derived from the related trigger

response will be indicated in the Status Flags of the related
entrity. It is possible to create triggers ("auto rules") from this
event. A.0
The Transaction UIDs of the pending commitment request are

kept "open" for a configurable amount in time (default: 1h). If
the "open time" for a pending commitment request has elapsed
without a related response from the provider, the Transaction
UID is removed and the related entities are indicated as "commit
failed". A.0
In any case, commitment will only be requested for previously

and successfully sent images. A.0
Sequencing of real World Activities A.0
The Storage Commitment trigger is automatically derived from

the successful completion of a Send job. A.0
0.0

July 2013
Query/Retrieve A.0
The query/retrieve service class defines an application-level

class of services which facilitates the management of images
and patient data against the well defined information model of
DICOM and allows a DICOM AE to retrieve images from a remote
DICOM node or to request a remote DICOM AE to initiate a trans-
fer of images to another DICOM AE. The DICOM query/retrieve
application supports the query/retrieve services to act as SCU
and SCP. A.0
0.0


SCP for the query/retrieve network service. The product target
operating system is Windows XP. A.0
C-FIND
User Query/Retrieve Query/
Interface
SCU Retrieve
(Search...)
C-MOVE SCP
DICOM Application
A.0
A Date
Base Storage C-STORE
Storage
SCP
SCU
DICOM Application
A.0

C-GET
C-FIND
Query/Retrieve Query/
Database SCP Retrieve
C-MOVE SCU
DICOM Application
Storage C-STORE Storage

SCU SCP
DICOM Application
0.0

July 2013
The query/retrieve SCU requests the remote query/retrieve SCP

to perform a search and match to the keys specified in the
request in order to display the results in the user interface.
Depending on user action (Import) the Somaris/5 DICOM SCU
sends a C-MOVE DIMSE service to initiate a C-STORE sub-opera-
tion on the SCP to start an image transfer from the remote Stor-
age SCU to the Somaris/5 DICOM Storage SCP. A.0
The query/retrieve SCP responds to C-FIND DIMSE services from

remote SCU applications. Depending on further remote request,
a C-GET or a C-MOVE involves the Somaris/5 DICOM query/
retrieve SCP application to initiate a C-STORE association (by
triggering and parameterizing the own Storage SCU) to send
image objects to a remote Storage SCP. A.0
All components of the Somaris/5 DICOM query/retrieve SCP

application are operating as background server processes. They
are existing when the machine is powered on and then respond
to queries based on the records stored in its database. A.0
Note
The Somaris/5 DICOM query/retrieve SCU application will
execute new queries based upon the data found in the
higher level query. For details see → Page A.2–47. A
Retrieve of images is only possible if results from a previous

"Search..." operation exist and those entities can be selected for
"Import". A.0
0.0

Print A.0
The Print Management Service Classes define an application-

level class of services which facilitate the printing of images on
a hardcopy medium. The print management SCU and print man-
agement SCP are peer DICOM print management application
entities. The DICOM print application supports the print man-
agement DIMSE services to act as SCU. A.0

the print management network service. The product target
N-GET
HC User N-SET DICOM
Interface Print SCU Printer
(Filming) N-CREATE (Print
N-ACTION SCP)
DICOM Application
N-DELETE
N-EVENT-
Data Base REPORT
0.0

July 2013
The Print SCU is invoked by the user interface to set up film sheet
layout and whenever and image is ready to be printed on film.
The print SCU will hold and maintain all data needed to compile
a complete film sheet from the data (images, layout, configura-
tion) received. Whenever a film sheet is ready to print the
related data is used to supply the information to the SOP Classes
of the Print Management Service Class. A queue is maintained
in order to intermediately store several film sheets in case of
resource problems on printer. The SCU will only supply and
require the mandatory SOP Classes of the Print Management
Service Class. A.0
Not applicable. A.0
0.0

Worklist A.0
The Basic Worklist Service Class defines an application-level

class of service which facilitates the transfer of worklists from
the information system to the imaging modality. The worklist is
queried by the AE and supplies the SCU with the scheduled
tasks, which have to be performed on the modality. The DICOM
worklist application supports the worklist service as SCU. A.0

the Basic Worklist Service using the Modality Worklist SOP Class.
The product target operating system is Windows XP. A.0
DICOM Standard Interface A.0

Update
Worklist/
A.0
Daemon Basic Basic
Worklist C-FIND Worklist A.0
SCU SCP
Get A.0
DICOM Application
Worklist
A.0
A.0
Note: It is configurable to get the worklist updates either auto-

matically (in a configurable time interval) or manually (initiated
by the user). There are two kinds of query the user can do: broad
worklist query (all jobs for the own modality or own application
entity) and patient based worklist query (where more search
keys can be given, including Patient Name and Patient ID). A.0
0.0

July 2013
The worklist SCU ("broad query") is invoked from the patient

browser user interface or by timer to request the worklist from
a remote Information System (Modality Worklist SCP). This is
done to perform a match to the internal worklist query keys
specified in the C-FIND DIMSE service issued for the Modality
Worklist Model. A.0
The Worklist SCP responds to the C-FIND query and scheduled

imaging service requests (scheduled procedure steps) and
patient demographic information will be downloaded from the
information system to the Somaris/5 modality. All information
retrieved will be held in the scheduling database for usage dur-
ing patient registration procedure. A.0
The "narrow" (patient based) Worklist Query requires that suffi-

cient matching keys or a unique matching key are/is entered
before the query is issued. Only then a single response can be
expected to complete the registration dialog. A.0
0.0

Modality Performed Procedure

Step A.0
The Modality Performed Procedure Step service class defines an

application-level class of service which facilitates the transfer of
billing and radiation dose information from the imaging modal-
ity to the information system. The performed procedure step is
created and set by the AE and supplies the SCP with the informa-
tion about a real world procedure which is performed on the
modality. The DICOM Modality Performed Procedure Step appli-
cation supports the MPPS service as SCU. A.0
The Somaris/5 DICOM network implementation is acts as SCU

for the performed procedure step network service. The target

Patient
registered
MPPS N-CREATE Performed

SCU Proc. Step
N-SET SCP
MPPS DICOM Application
UI-Update
0.0

July 2013
With registration of a patient (i.e. a Scheduled Procedure Step

from Worklist), the Somaris/5 DICOM application will create a
MPPS instance and communicate it to the MPPS SCP. A.0
Furthermore a manual update can be performed with the

Somaris/5 MPPS user interface. Only there it is possible to set the
state of the MPPS to "Completed" or "Discontinued". If done so,
the DICOM application will no longer allow updates on the
related MPPS Instance. A.0
Somaris/5 will not only allow a "1:1 relationship" of Scheduled

Procedure Steps and Performed Procedure Steps, but also sup-
ports the "group case" (grouping several SPS of the same or dif-
ferent Requested Procedures) and "append case" from the
respective IHE scenarios. A.0
Somaris/5 supports creation of "unscheduled cases" by allowing

MPPS instances to be communicated for locally registered
patients. A.0
Sequencing of real World Activities A.0
Not applicable. A.0
A.0
0.0

CHAPTER
A.2 AE Specifications A.0
Verification AE Specification A.0
Association Establishment Policies A.0
General A.0
The Somaris/5 DICOM Service Tool application attempts to ini-

tiate a new open an association for verification request when-
ever the "verification" function is activated during network con-
figuration of a remote DICOM application. A.0
Number of Associations A.0
The Somaris/5 DICOM Service Tool application initiates several

associations one association at a time, one for each destination
time to which a transfer request is being processed in the active
job queue listverification. A.0
Asynchronous Nature A.0
The Somaris/5 DICOM implementation Service Tool application

does not support asynchronous communication (multiple out-
standing transactions over a single association). A.0
Implementation Identifying Information A.0
The Somaris/5 DICOM implementation Service Tool application

provides the Implementation Class UID of A.1
❏ “1.3.12.2.1107.5.1.4"
and an Implementation Version Name of A.1
❏ “SIEMENS_S5VB42A”.
0.0

July 2013
Network – Application Entity Specifications DICOM Conformance Statement
Association Initiation by Real-World Activity A.1
The Somaris/5 DICOM Service Tool application attempts to ini-

tiate a new association for A.1
❏ DIMSE C-ECHO
service operations. A.1
Associated Real-World Activity - Verification A.1
Associated Real-World
Activity - Verification SCU A
The associated Real-World activity is a C-ECHO request initiated
by the Service and Configuration SW environment whenever a
"verification" is requested. If an association to a remote Applica-
tion Entity is successfully established, Verification with the con-
figured AET is requested via the open association. If the C-ECHO
Response from the remote Application contains a status other
than "Success" this will be indicated in the service environment
and the association is closed. A.0
Proposed Presentation The Somaris/5 DICOM application will propose Presentation

Contexts - Verification SCU A Contexts as shown in the following table: A.0
A
Presentation Context Table A
Abstract Syntax A Transfer Syntax A Role A Extended A
Name A UID A Name List A UID List A A Negotiation A
Verification A 1.2.840.10008.1.1 A Implicit VR Little 1.2.840.10008.1.2 SCU A None A
Endian A A
Explicit VR Big 1.2.840.10008.1.2.2

Endian A A
Explicit VR Little 1.2.840.10008.1.2.1 A
Endian A
SOP Specific Conformance The Application conforms to the definition of a Verification SCU
Statement - Verification SCU A in accordance to the DICOM Standard. A.0
0.0

DICOM Conformance Statement Network – Application Entity Specifications
Association Acceptance Policy A.0
The Verification SCP is part of the Storage SCP – see

→ page A.2–17, Association Acceptance Policy. A.0
0.0

July 2013
Storage AE Specification A.0
The Somaris/5 Storage service class user applications and ser-

vice class provider applications use one AE when initiating/
receiving associations to/from remote DICOM nodes. A.0
The SIEMENS Somaris/5 DICOM implementation provides Stan-

dard Conformance to the following DICOM V3.0 SOP Classes as
both an SCU and SCP: A.0
SOP Class Name A SOP Class UID A

A
Computed Radiography 1.2.840.10008.5.1.4.1.1.1 A
Image Storage A
Digital X-Ray 1.2.840.10008.5.1.4.1.1.1.1 A
Image Storage - For

Presentation A
Digital X-Ray 1.2.840.10008.5.1.4.1.1.1.1.1 A
Image Storage - For

Processing A
Digital Mammography X-Ray 1.2.840.10008.5.1.4.1.1.1.2 A
Image Storage - For

Presentation A
Digital Mammography X-Ray 1.2.840.10008.5.1.4.1.1.1.2.1 A
Image Storage - For

Processing A
Digital Intra-oral X-Ray 1.2.840.10008.5.1.4.1.1.1.3 A
Image Storage - For

Presentation A
Digital Intra-oral X-Ray 1.2.840.10008.5.1.4.1.1.1.3.1 A
Image Storage - For

Processing A
Computed Tomography 1.2.840.10008.5.1.4.1.1.2 A
Image Storage A
0.0

UltraSound Multi-Frame 1.2.840.10008.5.1.4.1.1.3 A
Image Storage (retired) (SCP

only) A
UltraSound Multi-Frame 1.2.840.10008.5.1.4.1.1.3.1 A
Image Storage A
Magnetic Resonance 1.2.840.10008.5.1.4.1.1.4 A
Image Storage A
UltraSound Image Storage 1.2.840.10008.5.1.4.1.1.6 A
(retired) (SCP only) A
UltraSound Image Storage A 1.2.840.10008.5.1.4.1.1.6.1 A
Secondary Capture Image 1.2.840.10008.5.1.4.1.1.7 A
Storage A
12-lead ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.1 A
Storage A
General ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.2 A
Storage A
Ambulatory ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.3 A
Storage A
Hemodynamic Waveform 1.2.840.10008.5.1.4.1.1.9.2.1 A
Storage A
Cardiac Electrophysiology 1.2.840.10008.5.1.4.1.1.9.3.1 A
Waveform Storage A
Basic Voice Audio Waveform 1.2.840.10008.5.1.4.1.1.9.4.1 A
Storage A
X-Ray Angiographic Image 1.2.840.10008.5.1.4.1.1.12.1 A
Storage A
X-Ray RadioFluoroscopic 1.2.840.10008.5.1.4.1.1.12.2 A
Image Storage A
Nuclear Medicine Image 1.2.840.10008.5.1.4.1.1.20 A
Storage A
0.0

July 2013
Basic Text SR A 1.2.840.10008.5.1.4.1.1.88.11 A
Enhanced SR A 1.2.840.10008.5.1.4.1.1.88.22 A
Comprehensive SR A
1.2.840.10008.5.1.4.1.1.88.33 A
Procedure Log A 1.2.840.10008.5.1.4.1.1.88.40 A
Mammography CAD SR A 1.2.840.10008.5.1.4.1.1.88.50 A
Chest CAD SR A 1.2.840.10008.5.1.4.1.1.88.65 A
X-Ray Radiation Dose SR A 1.2.840.10008.5.1.4.1.1.88.67 A
PET Image Storage A 1.2.840.10008.5.1.4.1.1.128 A
Radio Therapy Image Storage 1.2.840.10008.5.1.4.1.1.481.1

A A
Radio Therapy Dose Storage A 1.2.840.10008.5.1.4.1.1.481.2 A
Radio Therapy Structure Set 1.2.840.10008.5.1.4.1.1.481.3 A
Storage A
Radio Therapy Plan Storage A 1.2.840.10008.5.1.4.1.1.481.5 A
Radio Therapy Ion Plan 1.2.840.10008.5.1.4.1.1.481.8 A
Storage A
Radio Therapy Ion Beams 1.2.840.10008.5.1.4.1.1.481.9 A
Treatment Record Storage A
Verification (only SCP) A 1.2.840.10008.1.1 A
Somaris/5 DICOM implementation provides Private Conform-

ance to the following DICOM V3.0 conform Private SOP Classes
as both an SCU and SCP: A.0

A
CSA Non-Image Storage A 1.3.12.2.1107.5.9.1 A
0.0

General A.0
The existence of a job queue with network destination or an

internal trigger from processing a retrieve request will activate
the DICOM Storage Application. An association request is sent to
the destination AE and upon successful negotiation of a Presen-
tation Context the transfer is started. A.0
The default PDU size will be 28 KB. A.0
The Somaris/5 DICOM application initiates several associations

at a time, one for each destination to which a transfer request is
being processed in the active job queue list. A.0
The Somaris/5 DICOM application is able to accept multiple

associations at a time. It can handle up to 10 associations in par-
allel. A.0
The number of Simultaneous DICOM associations can be config-

ured via the Service-UI. The dialog can be found in Configura-
tion / DICOM / General. A.0
The Somaris/5 DICOM application does not support asynchro-

nous communication (multiple outstanding transactions over a
single association). A.0
The Somaris/5 DICOM implementation provides the Implemen-

tation Class UID of A.0
❏ “1.3.12.2.1107.5.1.4"
0.0

July 2013
Association Initiation Policy A.0
If a job with network destination becomes active in the job list

or a retrieve sub-operation is processed the Somaris/5 DICOM
application attempts to initiate a new association for A.0
❏ DIMSE C-STORE
service operations. A.0
Associated Real-World Activity - Send (Storage SCU) A.0
Associated Real-World The associated Real-World activities are: A.0
Activity - Send Image

❏ A user wants to send one or more composite objects to a
Objects to a Network
remote node. A job with network destination triggers an
Destination A
internal process, which initiates a C-STORE request.
❏ A user on a remote node wants to retrieve one or more com-
posite objects: The local C-MOVE SCP initiates
C-STORE suboperations as a reaction to a C-MOVE-RQ coming
from a remote node.
For both cases, if the process successfully establishes an associ-
ation to a remote Application Entity, it will transfer each image
one after another via the open association. If the C-STORE
Response from the remote Application contains a status other
than "Success" or "Warning", the association is aborted or
released. A.0
0.0


Contexts - Send Images Contexts as shown in the following table: A.0
(Storage SCU) A
A
Computed 1.2.840.10008.5.1.4.1.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Radiography Explicit VR Little Endian 1.2.840.10008.1.2.1
Image Explicit VR Big Endian 1.2.840.10008.1.2.2
JPEG Lossy Baseline 1.2.840.10008.1.2.4.50
(Process 1)
JPEG Lossy Extended (2 & 4) 1.2.840.10008.1.2.4.51
JPEG Lossless, Process 14 1.2.840.10008.1.2.4.70
(selection value 1)
Digital X-Ray 1.2.840.10008.5.1.4.1.1.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Image for Explicit VR Little Endian 1.2.840.10008.1.2.1
presentation Explicit VR Big Endian 1.2.840.10008.1.2.2
(Process 1)
(selection value 1)
Digital X-Ray 1.2.840.10008.5.1.4.1.1.1.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

processing Explicit VR Big Endian 1.2.840.10008.1.2.2
(Process 1)
(selection value 1)
0.0

July 2013
Digital 1.2.840.10008.5.1.4.1.1.1.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

MammoGraphy Explicit VR Little Endian 1.2.840.10008.1.2.1
X-Ray Image for Explicit VR Big Endian 1.2.840.10008.1.2.2
presentation JPEG Lossy Baseline 1.2.840.10008.1.2.4.50
(Process 1)
(selection value 1)
Digital 1.2.840.10008.5.1.4.1.1.1.2.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

processing JPEG Lossy Baseline 1.2.840.10008.1.2.4.50
(Process 1)
(selection value 1)
Digital Intra- 1.2.840.10008.5.1.4.1.1.1.3 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

oral X-Ray Explicit VR Little Endian 1.2.840.10008.1.2.1
Image for Explicit VR Big Endian 1.2.840.10008.1.2.2
(Process 1)
(selection value 1)
Digital Intra- 1.2.840.10008.5.1.4.1.1.1.3.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

(Process 1)
(selection value 1)
0.0

Computed 1.2.840.10008.5.1.4.1.1.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Tomography Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
UltraSound 1.2.840.10008.5.1.4.1.1.3.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Multi-Frame Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
Magnetic 1.2.840.10008.5.1.4.1.1.4 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Resonance Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
UltraSound 1.2.840.10008.5.1.4.1.1.6.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Image Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
(Process 1)
(selection value 1)
0.0

July 2013
Secondary 1.2.840.10008.5.1.4.1.1.7 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Capture Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
Waveform 1.2.840.10008.5.1.4.1.1.9.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

12-lead ECG Explicit VR Big Endian 1.2.840.10008.1.2.2
Object Explicit VR Little Endian 1.2.840.10008.1.2.1

General ECG Explicit VR Big Endian 1.2.840.10008.1.2.2

Ambulatory Explicit VR Big Endian 1.2.840.10008.1.2.2
ECG Object Explicit VR Little Endian 1.2.840.10008.1.2.1

Hemodynamic Explicit VR Big Endian 1.2.840.10008.1.2.2

Cardiac Electro- Explicit VR Big Endian 1.2.840.10008.1.2.2
physiology Explicit VR Little Endian 1.2.840.10008.1.2.1
Object
Waveform Basic 1.2.840.10008.5.1.4.1.1.9.4.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Audio Object Explicit VR Big Endian 1.2.840.10008.1.2.2
Explicit VR Little Endian 1.2.840.10008.1.2.1
X-Ray 1.2.840.10008.5.1.4.1.1.12.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Angiographic Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
0.0

X-Ray Radio 1.2.840.10008.5.1.4.1.1.12.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Fluoro-scopic Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
Nuclear 1.2.840.10008.5.1.4.1.1.20 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Medicine Image Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
Basic Text SR 1.2.840.10008.5.1.4.1.1.88.11 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Enhanced SR 1.2.840.10008.5.1.4.1.1.88.22 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Comprehensive 1.2.840.10008.5.1.4.1.1.88.33 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

SR Explicit VR Little Endian 1.2.840.10008.1.2.1
Mammography 1.2.840.10008.5.1.4.1.1.88.55 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

CAD SR Explicit VR Little Endian 1.2.840.10008.1.2.1
Chest CAD SR 1.2.840.10008.5.1.4.1.1.88.65 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

X-Ray Radiation 1.2.840.10008.5.1.4.1.1.88.67 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Dose SR Explicit VR Little Endian 1.2.840.10008.1.2.1
0.0

July 2013
PET Image 1.2.840.10008.5.1.4.1.1.128 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

(Process 1)
(selection value 1)
RT Image 1.2.840.10008.5.1.4.1.1.481.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

(Process 1)
(selection value 1)
RT Dose 1.2.840.10008.5.1.4.1.1.481.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

(Process 1)
(selection value 1)
RT 1.2.840.10008.5.1.4.1.1.481.3 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Structure Set Explicit VR Little Endian 1.2.840.10008.1.2.1
RT 1.2.840.10008.5.1.4.1.1.481.5 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Plan Explicit VR Little Endian 1.2.840.10008.1.2.1
RT Brachy 1.2.840.10008.5.1.4.1.1.481.6 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Treatment Explicit VR Little Endian 1.2.840.10008.1.2.1
Record Explicit VR Big Endian 1.2.840.10008.1.2.2
0.0

RT Brachy 1.2.840.10008.5.1.4.1.1.481.7 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Summary Explicit VR Big Endian 1.2.840.10008.1.2.2
Record
RT Ion Plan 1.2.840.10008.5.1.4.1.1.481.8 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

RT Ion Beams 1.2.840.10008.5.1.4.1.1.481.9 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

CSA 1.3.12.2.1107.5.9.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Non-Image Explicit VR Little Endian 1.2.840.10008.1.2.1
Note
Uncompressed transfer syntaxes are proposed together in a
single presentation context for each abstract syntax. A
The "MOVE" destinations must be configured as Storage desti-

nations. This will include the configuration of Transfer Syntax
capabilities. A.0
0.0

July 2013
Not all the listed transfer syntaxes will be proposed all the time.
For some abstract syntaxes only a list of uncompressed (UC)
transfer syntaxes (one or more) will be proposed, for other
abstract syntaxes also JPEG Lossless (LL) syntax will be proposed
and/or a list of JPEG Lossy (LY) transfer syntaxes. The contents of
this lists is configurable, e.g. UC could be configured to contain
only Implicit Little Endian for instance. For further configuration
details see → page A.5–3. A.0
It is not possible to send an image that is locally stored in a Lossy

compressed format using an uncompressed or lossless transfer
syntax. A.0
SOP Specific Conformance The DICOM images created by Somaris/5 DICOM application
Statement - Storage SCU A conform to the DICOM IOD definitions (Standard Extended
IODs). But they will contain additional private elements which
have to be discarded by a DICOM system when modifying the
image. A.0
The DICOM nodes are responsible for data consistency when

modifying images. All unknown private attributes have to be
removed upon modification! A.0
Somaris/5 does not change private attributes if no modification

is done. But during a Save as operation all non syngo defined
private attributes will be removed. For association and DIMSE
level time outs refer
→ page A.5–3, Configurable Parameters A.0
0.0

The Somaris/5 DICOM application attempts to accept a new

association for A.0
❏ DIMSE C-ECHO
❏ DIMSE C-STORE
service operations. Any Information Object transmitted on that
association will be checked for conformance and stored in the
database if check was successful. A.0
Real-World Activity - Receive (Storage SCP) A.0
Associated Real-World The daemon receiving process will accept an association and
Activity - Receiving will receive any images transmitted on that association and will
Images from Remote Note store the images on disk in the own database if the conform-
(Storage SCP) A ance check is performed successfully. A.0
0.0

July 2013

Contexts - Receiving Images Contexts as shown in the following table: A.0
(Storage SCP) A
A
Computed 1.2.840.10008.5.1.4.1.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Radiography Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
Digital X-Ray 1.2.840.10008.5.1.4.1.1.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

presentation Explicit VR Big Endian 1.2.840.10008.1.2.2
(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
Digital X-Ray 1.2.840.10008.5.1.4.1.1.1.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

processing Explicit VR Big Endian 1.2.840.10008.1.2.2
(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
0.0

Digital 1.2.840.10008.5.1.4.1.1.1.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
Digital 1.2.840.10008.5.1.4.1.1.1.2.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
Digital Intra- 1.2.840.10008.5.1.4.1.1.1.3 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
Digital Intra- 1.2.840.10008.5.1.4.1.1.1.3.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
0.0

July 2013
Computed 1.2.840.10008.5.1.4.1.1.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Tomography Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
UltraSound 1.2.840.10008.5.1.4.1.1.3.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Multi-Frame Explicit VR Little Endian 1.2.840.10008.1.2.1
Image 1.2.840.10008.5.1.4.1.1.3 Explicit VR Big Endian 1.2.840.10008.1.2.2
(retired) *1 JPEG Lossy Baseline 1.2.840.10008.1.2.4.50
(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
Magnetic 1.2.840.10008.5.1.4.1.1.4 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Resonance Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
UltraSound 1.2.840.10008.5.1.4.1.1.6.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Image Explicit VR Little Endian 1.2.840.10008.1.2.1
1.2.840.10008.5.1.4.1.1.6 Explicit VR Big Endian 1.2.840.10008.1.2.2
(retired) *1 JPEG Lossy Baseline 1.2.840.10008.1.2.4.50
(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
0.0

Secondary 1.2.840.10008.5.1.4.1.1.7 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Capture Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
Waveform 1.2.840.10008.5.1.4.1.1.9.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

12-lead ECG Explicit VR Big Endian 1.2.840.10008.1.2.2

General ECG Explicit VR Big Endian 1.2.840.10008.1.2.2

Ambulatory Explicit VR Big Endian 1.2.840.10008.1.2.2
ECG Object Explicit VR Little Endian 1.2.840.10008.1.2.1

Hemodynamic Explicit VR Big Endian 1.2.840.10008.1.2.2

Cardiac Electro- Explicit VR Big Endian 1.2.840.10008.1.2.2
physiology Explicit VR Little Endian 1.2.840.10008.1.2.1
Object
Waveform Basic 1.2.840.10008.5.1.4.1.1.9.4.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Audio Object Explicit VR Big Endian 1.2.840.10008.1.2.2
0.0

July 2013
X-Ray 1.2.840.10008.5.1.4.1.1.12.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Angiographic Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
X-Ray Radio 1.2.840.10008.5.1.4.1.1.12.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Fluoroscopic Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
Nuclear 1.2.840.10008.5.1.4.1.1.20 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Medicine Explicit VR Little Endian 1.2.840.10008.1.2.1
(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
Basic Text SR 1.2.840.10008.5.1.4.1.1.88.11 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Enhanced SR 1.2.840.10008.5.1.4.1.1.88.22 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Comprehensive 1.2.840.10008.5.1.4.1.1.88.33 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

SR Explicit VR Little Endian 1.2.840.10008.1.2.1
0.0

Mammography 1.2.840.10008.5.1.4.1.1.88.55 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

CAD SR Explicit VR Little Endian 1.2.840.10008.1.2.1
Chest CAD SR 1.2.840.10008.5.1.4.1.1.88.65 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

X-Ray Radiation 1.2.840.10008.5.1.4.1.1.88.67 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Dose SR Explicit VR Little Endian 1.2.840.10008.1.2.1
PET Image 1.2.840.10008.5.1.4.1.1.128 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
RT Image 1.2.840.10008.5.1.4.1.1.481.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
RT Dose 1.2.840.10008.5.1.4.1.1.481.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

(Process 1)
(selection value 1)
RLE Lossless 1.2.840.10008.1.2.2
0.0

July 2013
RT 1.2.840.10008.5.1.4.1.1.481.3 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Structure Set Explicit VR Little Endian 1.2.840.10008.1.2.1
RT Beams 1.2.840.10008.5.1.4.1.1.481.4 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

RT 1.2.840.10008.5.1.4.1.1.481.5 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Plan Explicit VR Little Endian 1.2.840.10008.1.2.1
RT Branchy 1.2.840.10008.5.1.4.1.1.481.6 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

RT Treatment 1.2.840.10008.5.1.4.1.1.481.7 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Summary Explicit VR Little Endian 1.2.840.10008.1.2.1
RT Ion Plan 1.2.840.10008.5.1.4.1.1.481.8 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

RT Ion Beams 1.2.840.10008.5.1.4.1.1.481.9 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

CSA 1.3.12.2.1107.5.9.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

Non-Image Explicit VR Little Endian 1.2.840.10008.1.2.1
Verification 1.2.840.10008.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

*1: US Retired and US Multiframe Retired images are converted

to US images/US Multiframe images before storing them into
the local database. The conversion creates new images, which
implies new UIDs. A.0
0.0

Note
With RLE Lossless Transfer Syntax the DICOM application will
decompress the image before storing it into the database. A
Note
JPEG 2000 decompression supported only for import in

connection with COSMOS / syngo Imaging workplace. A
Note
Private attributes in sequence items will be removed during
import in syngo. A
0.0

July 2013
SOP Specific Conformance The Somaris/5 DICOM application conforms to the Full Storage
Statement - Receiving Service Class at Level 2. A.0
Images A
Upon successfully receiving a C-STORE-RQ, the SIEMENS
Somaris/5 DICOM receiver performs a quick plausibility test on
the received image and available system resources. If this test
succeeds, it returns the status SUCCESS, otherwise one of the
following status codes is returned and the association is
aborted: A.0
❏ Refused (A700):
This error status indicates a lack of Resources (e.g. not
enough disk space) on the Somaris/5 modality.
❏ Invalid Dataset (A900):
The dataset is not containing one of the attributes "Study
Instance UID", "Series UID" or "SOP Instance UID", or one of
them has an invalid value.
❏ Processing Error (0110 or C000):
An error occurred while processing the image which makes it
impossible to proceed.
Attention! Only after sending the response, the image will be
saved into the database. If an error occurs during this operation,
the association will be aborted. This implies that a C-STORE-RSP
with status SUCCESS does not mean that the image was suc-
cessfully stored into the database. A.0
A.0
In order to confirm that the images sent were successfully

stored into the database, the sending application should use
Storage Commitment Service. A.0
A.0
If an image instance is received that is identified by a SOP

Instance UID which is already used by an Instance stored in the
database then the received image will be discarded. The exist-
ing image is not superseded. So if a remote node sends twice
the same image (same SOP Instance UID) then there will still be
only one image (the first) in the database of the DICOM receiver.
A.0
0.0

The following sections will differentiate the attribute contents

required for Image Viewing. The Somaris/5 DICOM application
supports more formats for Storage of images than Viewing. A.0
0.0

July 2013
Image Pixel Attribute Acceptance Criterion for Grayscale

Images A.0
The Display application accepts the MONOCHROME1 and

MONOCHROME2 photometric interpretation pixel format and
graphic overlay with unsigned integer and 8 or 16 bits allocated.
Accepted values: A.0
Pixel plane A.0
❏ samples per pixel (attribute 0028, 0002) = 1

❏ photometric interpretation (attribute 0028,0004) =
"MONOCHROME1"
"MONOCHROME2"
❏ pixel representation (attribute 0028, 0103) = 0 (unsigned)
❏ bits allocated (attribute 0028, 0100) = 8, 16
❏ bits stored (attribute 0028,0101) = 8, 10, 12, 14, 15, 16
❏ high bit (attribute 0028,0102) = bits stored - 1
❏ only aspect ratio (attribute 0028,0034) 1:1 is supported
Overlay plane A.0
❏ overlay type (attribute 60xx, 0040) = “G”

❏ overlay bits allocated (attribute 60xx, 0100) = 16
❏ overlay bit position (attribute 60xx, 0102) = 12, 13, 14, 15
(only bits above high bit permitted)
❏ Graphic Overlay will be shifted to fill Overlay Planes from Bit
12 and consecutive.
Overlay plane A.0

❏ overlay bit position (attribute 60xx, 0102) = 0
❏ overlay data (attribute 60xx, 3000) = supported
0.0

The Somaris/5 DICOM application accepts also the

MONOCHROME1 and MONOCHROME2 photometric interpreta-
tion pixel format with binary 2’s complement integer and 16 bits
allocated. Accepted values: A.0
Pixel plane A.0

"MONOCHROME1"
"MONOCHROME2"
❏ pixel representation (attribute 0028, 0103) = 1 (signed)
❏ bits allocated (attribute 0028, 0100) = 16
❏ bits stored (attribute 0028,0101) = 16
❏ high bit (attribute 0028,0102) = 15
❏ only aspect ratio (attribute 0028,0034) 1:1 is supported
Overlay plane A.0

❏ overlay bit position (attribute 60xx, 0102) = 0
❏ overlay data (attribute 60xx, 3000) = supported
For MOD LUT both the linear LUT (Rescale Slope/Intercept) and
the MOD LUT SQ are supported and considered when pixel data
is displayed. However there are two limitations. The MOD LUT
SQ will be ignored in the following cases: A.0
❏ 8 bit signed pixels

❏ The pixel format is changed by the MOD LUT (e.g. 8 bit -> 16 bit).
❏ If the MOD LUT SQ contains multiple LUTs then only the first
one is used.
For VOI LUT also both the linear LUT (Window Center/Width) and
the VOI LUT SQ are supported (VOI LUT SQ with 8 or 16 bit LUT
data). A.0
But if both a VOI LUT SQ and a linear MOD LUT are specified
within one image, then the value of Rescale Slope is restricted
to 1. A.0
0.0

July 2013
If the VOI LUT SQ contains multiple LUTs, then only the first one
is used by default. The other VOI LUTs are selectable. A.0
In this version the Display application supports only rectangular

and circular Shutters. Images with other shutter types will be
displayed without Shutter. A.0
0.0

Image Pixel Attribute Acceptance Criterion for Color Images A.0
The Siemens Display application supports the RGB color image

description with the unsigned integer 24 bit color image plane
pixel format. Accepted values: A.0

❏ photometric interpretation (attribute 0028,0004) = “RGB”
❏ pixel representation (attribute 0028, 0103) = 0
❏ planar configuration (attribute 0028,0006) =
0 (pixel interleave) or 1 (plane interleave)
A.0
The Siemens Display application supports the “Palette Color”

color image description with unsigned integer and 2’s comple-
ment pixel format: A.0

❏ photometric interpretation (attribute 0028,0004) = "PALETTE
COLOR"
❏ bits allocated (attribute 0028, 0100) = 8 and
bits stored (attribute 0028,0101) = 8
❏ bits allocated (attribute 0028, 0100) = 16 and
bits stored (attribute 0028,0101) = 16
❏ high bit (attribute 0028,0102) = 7, 15
Both 8bit and 16bit palettes are supported - but no Segmented
Palette Color LUTs. A.0
0.0

July 2013
The Siemens Display application supports the YBR_FULL color

image description with the unsigned integer pixel format.
Accepted values: A.0

“YBR_FULL” or "YBR_FULL_422"
If Somaris/5 software is making any persistent changes on a YBR
image, the resulting new image will be saved with Photometric
Interpretation "RGB". A.0
Presentation Context The Somaris/5 DICOM application will accept any number of Ver-
Acceptance Criterion - ification or storage SOP classes that are listed above. The num-
Storage SCP A ber of presentation contexts accepted is limited to the maxi-
mum of 127 (DICOM limit). In case the Siemens Somaris/5
DICOM application runs out of resources, it will reject the asso-
ciation request. A.0
0.0

Transfer Syntax Selection The Somaris/5 DICOM application supports A.0
Policies - Storage SCP

➭ the Implicit VR Little Endian, the Explicit VR Little Endian and
A
Explicit VR Big Endian transfer syntaxes

➭ the JPEG Baseline and JPEG Extended transfer syntaxes (JPEG
lossy)
➭ the JPEG lossless Non-Hierarchical transfer syntax
➭ the RLE Lossless Transfer Syntax
➭ the JPEG 2000 Lossless and Lossy Transfer Syntax
Any proposed presentation context which includes one of these
transfer syntaxes will be accepted. Any proposed presentation
context that does not include one of these transfer syntaxes will
be rejected. A.0
The order of preference in accepting Transfer Syntaxes within

Presentation Contexts or Presentation Contexts with single
Transfer Syntaxes is: A.0
1. JPEG Lossy Extended

2. JPEG Lossless Non-hierarchical
3. JPEG Lossy Baseline
4. RLE Lossless
5. Explicit VR Little Endian
6. Explicit VR Big Endian
7. Implicit VR Little Endian
8. JPEG 2000 Lossy
9. JPEG 2000 Lossless
With RLE Lossless Transfer Syntax the Somaris/5 application will
decompress the image before storing it to the database. A.0
With Implicit VR Little Endian Transfer Syntax the Somaris/5

DICOM application will remove any private attributes not known
to the application. Decision on removal of a Private Element is
done if there is NO entry in the attribute dictionary of the
Somaris/5 DICOM application. A.0
0.0

July 2013
Thus any Explicit VR Transfer Syntax shall preferrably be used by

the Storage SCUs when sending Composite Image Instances to
the Somaris/5 application. A.0
0.0

Storage Commitment AE
Specification A.0
The Somaris/5 DICOM application provides Standard Conform-

ance to the following DICOM V3.0 SOP Classes as SCU. A.0

A
Storage Commitment Push 1.2.840.10008.1.20.1 A
Model A
General A.0
With a Send Job successfully completed, the DICOM application

will generate a Storage Commitment Identifier which refer-
ences all instances of the processed job. The Commit Request is
then sent over a single opened association. Somaris/5 will wait
for Status responses of the Storage Commitment Request. If the
Provider accepts the Storage Commitment with Success Status,
the generated Transaction UID, together with study identifica-
tion data and time stamp, is kept. Depending on configuration,
the association is closed when the configured time out has
elapsed or a response was received before. If the association is
closed before a response was received, the response is then
expected on a different association. Multiple Storage Commit-
ment Requests can be pending. A.0
The Somaris/5 DICOM application initiates several association at

a time, one for each destination to which a transfer request is
being processed in the active job queue list. A.0
0.0

July 2013
The Somaris/5 DICOM application is able to accept multiple

association at a time. It can handle up to 10 associations in par-
allel. A.0
The Somaris/5 DICOM application does not support asynchro-

nous communication (multiple outstanding transactions over a
single association). A.0
The Somaris/5 DICOM application provides the Implementation

Class UID of A.0
❏ “1.3.12.2.1107.5.1.4"
0.0

The Somaris/5 Storage Commitment Application Entity acts as a

SCU for the A.0
❏ Storage Commitment Push Model Service Class (to request

commitment for storage of instances previously sent)
A.0
To do so, Somaris/5 will issue a A.0
❏ N-ACTION DIMSE to request commitment or a

❏ N-EVENT-REPORT DIMSE to respond to a received storage
commitment request and the association was closed by the
remote system prior to response.
Real-World Activity - Send Storage Commitment

Request A.0
Associated Real-World The Somaris/5 Storage Commitment application sends the com-
Activity - Job Completed A mit request (N-ACTION_RQ) message and waits for acceptance
of this request (N_ACTION-RSP). After receiving this, the trans-
action is marked as "waiting". A.0
Depending on a configuration value, the association will then

be closed or kept open. In the first case there is another config-
urable timeout giving the number of hours (h) and minutes (m)
(by default 1h:0m) to wait for the corresponding commit
response (N_EVENT-REPORT). In the second case, this time is the
(also configurable) time out for the association. For both cases,
if the commit response (N-EVENT-REPORT) does not arrive dur-
ing the configured time, the transaction will be marked as
failed. Somaris/5 does not re-send objects because of a failed
Storage Commitment result in any case. A.0
If the commit response (N-EVENT-REPORT) received has the sta-

tus of "complete - failure exists", the transaction is marked as
failed, else the transaction is marked as "completed"; in both
cases, a message is shown to the user. A.0
0.0

July 2013
Proposed Presentation The Somaris/5 Storage Commitment AE will propose Presenta-

Contexts - Job Completed A tion Contexts as shown in the following table: A.0
A
Storage 1.2.840.10008.1.20.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Commitment Explicit VR Little Endian 1.2.840.10008.1.2.1
Push Explicit VR Big Endian 1.2.840.10008.1.2.2
Model
SOP Specific Conformance Storage Commitment is supported for all the SOP class UIDs as
Statement - Job Completed A mentioned in table → page A.2–18. A.0
The Referenced Study Component Sequence is not supported. A.0
Storage Media File-Set ID and UID Attributes will not be sup-

ported in the commitment request (N-ACTION primitive)
invoked by the Storage Commitment SCU. A.0
0.0

The Somaris/5 Storage Commitment AE accepts an association

in this case: when acting as SCU if configured to receive N-
EVENT-REPORT on a separate association. A.0
Real World Activity - Receive Storage Commitment

Response A.0
Associated Real World The Somaris/5 Storage Commitment AE has sent a Storage Com-
Activity - Update Flags A mitment Request and, being configured to receive response on
a separate association, has closed the association, and now it
gets an association request from the Storage Commitment SCP
that wants to send the results. The application will wait for Stor-
age Commitment Notification triggers. Any incoming notifica-
tion will be checked for validity, that is, if the related Transaction
UID is still part of the Pending Request Queue. A.0
If the Notification is valid, the Notification Identifier is evaluated

and the related Instances marked with the related status. The
over all Commit Status of the higher Information Entities is
derived from propagation of all Image entities included in a
study. A.0
The status flags directly affected by Storage Commitment

results and indicated in the different entities of the Patient
Browser list can be one of (English UI assumed): A.0
❏ "AC" or "SC" - Successful Commitment. A means archived to

configured archive destination, whereas S means sent to any
other destination.
❏ "Af" or "Sf" - Commitment failed
❏ "A?" or "S?" - Commitment request is sent, response is pend-
ing
In case of failure the user has to repeat the transfer of images to
the Archive destination. Another Storage Commitment will be
performed after sending is completed successfully. A.0
0.0

July 2013
Accepted Presentation The Somaris/5 Storage Commitment AE will accept Presentation

Contexts - Update Flags A Contexts as shown in the following table: A.0
A
Storage 1.2.840.10008.1.20.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Commitment Explicit VR Little Endian 1.2.840.10008.1.2.1
Push Explicit VR Big Endian 1.2.840.10008.1.2.2
Model SOP
class
SOP Specific Conformance If the Commitment Response (N_EVENT_REPORT) received has

Statement - Receive Storage the status of "complete - failure exists", the transaction is
Commitment Response A marked as failed, else the transaction is marked as "completed";
In both cases, a message is shown to the user. A.0
The related status flags are set for the committed images in the
local database. A.0
The Somaris/5 DICOM application will NOT support the Storage

Media File Set ID attributes. A.0
0.0

Query/Retrieve AE Specification A.0
The Query/Retrieve SCU requests that the remote SCP performs

a match of all keys specified in the request against the informa-
tion in its database and the identified images will be moved over
a different (C-MOVE) storage association. A.0
The Query/Retrieve SCP responds to queries of the records based

on its database and images will be sent to the requesting SCU or
to a different storage destination. A.0
The Somaris/5 DICOM application provides Standard Conform-

ance to the following DICOM V3.0 SOP Classes as SCU and SCP: A.0

A
Patient Root Query/Retrieve 1.2.840.10008.5.1.4.1.2.1.1 A
Information Model - FIND A
Information Model - MOVE A
Study Root Query/Retrieve 1.2.840.10008.5.1.4.1.2.2.1 A
Patient/Study Only Query/ 1.2.840.10008.5.1.4.1.2.3.1 A
Retrieve Information Model -

FIND A

MOVE A
0.0

July 2013
Somaris/5 DICOM implementation provides Standard Conform-

ance to the following DICOM V3.0 SOP Classes as an SCP: A.0

A
Information Model - GET A
Information Model - GET A

FIND A

MOVE A

GET A
0.0

Note
See also the Storage DICOM Conformance Statement
(→ page A.2–17, Association Acceptance Policy ) to
compare for conformance of the C-STORE sub-operation
generated by the C-MOVE and C-GET DIMSE services.
Furthermore compare the supported Storage Service SOP
classes described in the Storage DICOM Conformance
Statement of the Modality to which the images shall be
transferred to. A
0.0

July 2013
General A.0
With the "Search..." function the query data are entered and the
DICOM Query/Retrieve application is started. A query request
will be sent out to one remote node that can be selected from a
list of configured Query Providers and the response data will be
displayed for the user. In order to provide detailed information
early additional queries are sent for the more detailed levels not
yet covered by the first results. Upon request (Import), the
retrieval of selected items is initiated. A.0
The default PDU size used will be 28 KB. A.0
The Somaris/5 DICOM Query/Retrieve application initiates sev-

eral association at a time, one for each query/retrieve request
being processed. A.0
The Somaris/5 DICOM Query/Retrieve application is able to

accept multiple associations at a time. It can handle up to
10 associations in parallel. A.0
The Somaris/5 DICOM Query/Retrieve application does not sup-

port asynchronous communication (multiple outstanding trans-
actions over a single association). A.0
The Somaris/5 DICOM Query/Retrieve AE provides the Imple-

mentation Class UID of A.0
❏ “1.3.12.2.1107.5.1.4"
0.0

The Query/Retrieve user interface will request the query data

from the user and triggers C-FIND requests to the selected
remote node. The response data will be displayed in the query
UI for further data navigation. A.0
When requesting Import of related items the browser requests

the retrieve application to send a C_MOVE request to the related
remote node. Images will then be received by the Storage SCP
as described in the related section. A.0
The following DIMSE-C operations are supported as SCU: A.0
❏ C-FIND
❏ C-MOVE
Real-World Activity - Find SCU A.0
Associated Real-World The associated Real-World activity is to fill out a query form with
Activity - Find SCU "Search" A search data and pass it as queries to the network application
which issues a C-FIND over a previously built association. The
remote SCP will respond with related data entries that will be
passed to a browser application. When data transfer is finished
the association is closed. A.0
Proposed Presentation The Somaris/5 DICOM Query application will propose Presenta-
Contexts - Find SCU A tion Contexts as shown in the following table: A.0
A
Patient Root 1.2.840.10008.5.1.4.1.2.1.1 DICOM Implicit VR Little 1.2.840.10008.1.2 SCU See Note
Query/Retrieve Endian Transfer Syntax
Model - FIND DICOM Explicit VR Little 1.2.840.10008.1.2.1
Endian Transfer Syntax
DICOM Explicit VR Big 1.2.840.10008.1.2.2
0.0

July 2013
Study Root 1.2.840.10008.5.1.4.1.2.2.1 DICOM Implicit VR Little 1.2.840.10008.1.2 SCU See Note
Model - FIND DICOM Explicit VR Little 1.2.840.10008.1.2.1
Patient Study 1.2.840.10008.5.1.4.1.2.3.1 DICOM Implicit VR Little 1.2.840.10008.1.2 SCU See Note
only Query/ Endian Transfer Syntax
Retrieve DICOM Explicit VR Little 1.2.840.10008.1.2.1
Model - FIND Endian Transfer Syntax
It is configurable which of the three query models are to be used

by the Somaris/5 Query SCU application. If Patient and Study
Root Abstract Syntaxes are configured, the C_FIND SCU will use
the Patient Root Model only for C-FIND requests on PATIENT
level. For all other levels it will use the STUDY Root Model. A.0
It is highly recommended to configure only the Study Root

Model if the corresponding Query SCP supports this Model. If
the Query SCP does not support queries on Series Level, Patient
Study Only Model should be used. A.0
0.0

SOP Specific Conformance The Somaris/5 DICOM Query/Retrieve SCU supports hierarchical
Statement - Find SCU A queries with all mandatory search keys. On each level, the
unique attributes of all previous levels are also sent (values are
provided by the user by selection from a list). For instance for a
query using the patient root model on Series level, the Patient
ID of the current selected patient and the Study Instance UID of
the current selected study are included in the message. The
interactive querying of attributes on IMAGE level is not sup-
ported by the Query SCU. Nevertheless, retrieval of individual
Objects is possible. A.0
The Query dialog in Somaris/5 offers search keys on different

levels (Patient, Study, Series). Depending on the used Query
Model (Patient Root, Study Root, Patient Study Only) the
Somaris/5 DICOM Query/Retrieve SCU will execute multiple que-
ries sequentially. A.0
E.g. Patient Root Model: A.0
The first query is performed on patient level with the entered

patient level query keys. For each query result a new query is
performed on study level with the entered study level query
keys. At last for each result on study level a query is performed
on series level with the entered series level keys. A.0
The following table Query attributes describes the search keys

for the three query models (Patient Root, Study Root and Patient
Study Only) that the Somaris/5 Query/Retrieve application sup-
ports as an SCU. Matchings are either wildcard, which means
that the user can supply a string containing wildcards, either
universal, or means that the attribute is returned no matter
what value it has. A.0
0.0

July 2013
A
Attribute name Tag A Type A Matching A User input A Return
value
displayed A
Patient levela A
d
Patient name A (0010,0010) A R A wildcard A enter value A yes A
Patient ID A (0010,0020) A U A wildcardd A enter value A yes A
Patient’s birth date A (0010,0030) A O A universal enter value A yes A
(NULL) A
Patient’s sex A (0010,0040) A O A universal enter value A yes A
(NULL) A
Number of Patient related (0020,1200) A O A universal - A yesb A
studies A (NULL) A
Number of Patient relates (0020,1202) A O A universal - A no A
series A (NULL) A
Number of Patient related (0020,1204) A O A universal - A no A
instances A (NULL) A
Study level A
c d
Patient name A (0010,0010) A R A wildcard A enter value A yes A
Patient ID A (0010,0020) A R A wildcardd A enter value A yes A
Patient’s birth datec A (0010,0030) A O A universal enter value A yes A
(NULL) A
Patient’s sexc A (0010,0040) A O A universal enter value A yes A
(NULL) A
Study Instance UID A (0020,000D) A U A single - A yes A
value A
Study ID A (0020,0010) A R A universal enter yes A
(NULL) A valued A
Study date A (0008,0020) A R A universal enter yes A
(NULL) A valuee A
0.0


value
displayed A
Study time A (0008,0030) A R A universal - A yes A
(NULL) A
Accession number A (0008,0050) A R A universal enter yes A
(NULL) A valued A
Study description A (0008,1030) A O A universal enter yes A
(NULL) A valued A
Referring physician’s name A (0008,0090) A O A universal enter yes A
(NULL) A valued A
Name of physician reading (0008,1060) A O A universal enter yes A
study A (NULL) A valued A
Modalities in Study A (0008,0061) A O A universal enter yes A
(NULL) A valued A
Storage Media File Set ID A (0008,0130) A O A universal - A no A
(NULL) A
Retrieve AE Title A (0008,0054) A O A universal - A no A
(NULL) A
Number of study related (0020,1206) A O A universal - A yesf A
series A (NULL) A
Number of study related (0020,1208) A O A universal - A no A
Series level A
Series instance UID A (0020,000E) A U A single - A yes A
value A
Series number A (0020,0011) A R A universal - A yes A
(NULL) A
Modality A (0008,0060) A R A universal enter value A yes A
(NULL) A
0.0

July 2013

value
displayed A
Series date A (0008,0021) A O A universal - A yes A
(NULL) A
Series time A (0008,0031) A O A universal - A yes A
(NULL) A
Study ID A (0020,0010) A O A universal - A yes A
(NULL) A
Series description A (0008,103E) A O A universal enter yes A
(NULL) A valued A
Storage Media File Set ID A (0008,0130) A O A universal - A yes A
(NULL) A
Retrieve AE Title A (0008,0054) A O A universal - A yes A
(NULL) A
Body Part Examined A (0018,0015) A O A universal enter yes A
(NULL) A valued A
Protocol name A (0018,1030) A O A universal - A no A
(NULL) A
Performing Physician A (0018,1050) A O A universal enter yes A
(NULL) A valued A
Performed procedure step (0040,0244) A O A universal - A yes A
start date A (NULL) A
Performed procedure step (0040,0245) A O A universal - A yes A
start time A (NULL) A
Request Attribute Sequence A (0040,0275) A O A universal - A yes A
(NULL) A
> Requested Procedure ID A (0040,1001) A O A universal - A yes A
(NULL) A
> Scheduled Procedure ID A (0040,0009) A O A universal - A yes A
(NULL) A
0.0


value
displayed A
Number of series related (0020,1209) A O A universal - A yes A
Image Level A A A A A A
SOP Instance UID A (0008,0018) A U A single - A no A
value A
Instance Number A (0020,0013) A R A universal - A yes A
(NULL) A
Storage Media File Set ID A (0008,0130) A O A universal - A no A
(NULL) A
Retrieve AE Title A (0008,0054) A O A universal - A no A
(NULL) A
Content date A (0008,0023) A O A universal - A no A
(NULL) A
Content time A (0008,0033) A O A universal - A no A
(NULL) A
Number of Frames A (0028,0008) A O A universal - A yes A
(NULL) A
Image comments A (0020,4000) A O A universal - A no A
(NULL) A
Referenced Request A (0040,A370) A O A sequence - A yes A
matching A
> Accession Number A (0008,0050) A O A single - A yes A
value,
universal A
> Requested Procedure ID A (0040,1000) A O A single - A yes A
value,
universal A
0.0

July 2013

value
displayed A
Concept Name Code (0040,A043) A O A single - A yes A
Sequence A
value,
universal A
> Code Value A (0008,0100) A O A single - A yes A
value,
universal A
> Coding Scheme Designator A (0008,0102) A O A single - A yes A
value,
universal A
> Coding Scheme Version A (0008,0103) A O A single - A yes A
value,
universal A
> Code Meaning A (0008,0104) A O A single - A yes A
value,
universal A
Template Identifier A (0040,DB00) A O A single - A yes A
value,
universal A
Completion Flag A (0040,A491) A O A single entervalue A yes A
value,
universal A
Verification Flag A (0040,A493) A O A single entervalue A yes A
value,
universal A
Verifying Observer Sequence A (0040,A073) A O A sequence entervalue A yes A
matching A
> Verifying Oragnization A (0080,A072) A O A single - A A
value,
universal A
0.0


value
displayed A
> Verifying Date Time A (0008,A030) A O A single entervalue A yes A
value,
universal A
> Verifying Observer Name A (0080,A075) A O A single entervalue A yes A
value,
universal A
> Verifying Observer (0040,A088) A O A single A yes A
Identification Code Sequence A value,

universal A
>> Code Value A (0008,0100) A O A single - A yes A
value,
universal A
>> Coding Scheme (0008,0102) A O A single - A yes A
Designator A
value,
universal A
>> Coding Scheme Version A (0008,0103) A O A single - A yes A
value,
universal A
>> Code Meaning A (0008,0104) A O A single - A yes A
value,
universal A
a. Only for Patient Root or Patient Study Only information model

b. Implicitly visualized in the UI if no study and series search attributes have been entered
c. Only for Study Root information model
d. Always a "*" is added to the string supplied by the user
e. Date range possible
f. Implicitly visualized in the UI if no series search attributes have been entered
A.0
0.0

July 2013
The Find SCU interprets following status codes: A.0
A
C-FIND response status A
Service Status Meaning Protocol Related Fields A
Codes A
Refused A Out of Resources A A700 A (0000,0902) A
Failed A Identifier does not match SOP Class A A900 A (0000,0901) A
(0000,0902) A
A Unable to process A Cxxx A (0000,0901) A
(0000,0902) A
Cancel A Matching terminated due to Cancel request A FE00 A None A
Success A Matching is complete - No final Identifier is 0000 A None A
supplied A
Pending A Matches are continuing – Current Match is FF00 A Identifier A
supplied and any Optional Keys were

supported in the same manner as Required
Keys A
A Matches are continuing – Warning that one FF01 A Identifier A
or more Optional Keys were not supported

for existence and/or matching for this
identifier A
0.0

Real-World Activity - Move SCU A.0
Associated Real-World The operator selects a data entry in the Query UI and activates
Activity - Move SCU "Import" A the "Import" function. A.0
This will generate a retrieval request to the archival application

which issues a C-MOVE service according to the Patient Root or
Study Root query model. (The Storage Service Class Conform-
ance Statement of the SCP describes the C-STORE service which
is generated by processing the C-MOVE service.) A.0
The transferred image data are processed as described in the

storage class SCP descriptions. A.0
The possibility to request the remote C-MOVE provider to move

data to an application entity other than the C-MOVE SCU (the
Somaris/5 DICOM application) is NOT used. A.0

Contexts - Move SCU Contexts as shown in the following table: A.0
"Import" A
A
Patient Root 1.2.840.10008.5.1.4.1.2.1.2 DICOM Implicit VR Little 1.2.840.10008.1.2 SCU See Note
Model - MOVE DICOM Explicit VR Little 1.2.840.10008.1.2.1
Study Root 1.2.840.10008.5.1.4.1.2.2.2 DICOM Implicit VR Little 1.2.840.10008.1.2 SCU See Note
Model - MOVE DICOM Explicit VR Little 1.2.840.10008.1.2.1
0.0

July 2013
Patient Study 1.2.840.10008.5.1.4.1.2.3.2 DICOM Implicit VR Little 1.2.840.10008.1.2 SCU See Note
Only Query/ Endian Transfer Syntax
Retrieve Model DICOM Explicit VR Little 1.2.840.10008.1.2.1
- MOVE Endian Transfer Syntax
A.0
Note
C-MOVE Extended Negotiation will be NOT supported
by the SCU. A
C-MOVE on Patient level is not supported by the application. A
0.0

SOP Specific Conformance At association establishment time the C-MOVE presentation

Statement - Move SCU context shall be negotiated. The C-STORE sub-operations must
"Import" A be done on a different association to transfer images to the own
Storage Service Class SCP. A.0
The Move SCU interprets following status codes: A.0
A
C-MOVE response status A
Codes A
Refused A Out of Resources - Unable to calculate A701 A (0000,0902) A
number of matches A A A
Out of Resources - Unable to perform A702 A (0000,1020) A
suboperations A
(0000,1021) A
(0000,1022) A
(0000,1023) A
A A (0000,0902) A
Failed A Unable to process A Cxxx A (0000,0901) A
(0000,0902) A
Cancel A Sub-operations terminated due to Cancel FE00 A (0000,1020) A
Indication A (0000,1021) A
(0000,1022) A
(0000,1023) A
Warning A Sub-operations Complete - One or more B000 A (0000,1020) A
Failures of Warnings A (0000,1021) A
(0000,1022) A
(0000,1023) A
Pending A Sub-operations are continuing A FF00 A (0000,1020) A
(0000,1021) A
(0000,1022) A
(0000,1023) A
0.0

July 2013
C-MOVE response status A
Codes A
Success A Sub-operations Complete - No Failures or 0000 A (0000,1020) A
Warning A (0000,1021) A
(0000,1022) A
(0000,1023) A
0.0

The Query/Retrieve SCU and SCP establish an association by

using the DICOM association services. During association estab-
lishment the Query/Retrieve application entities negotiate the
supported SOP classes to exchange the capabilities of the SCU
and the SCP. A.0
The following DIMSE-C operations are supported as SCP: A.0
❏ C-FIND
❏ C-GET
❏ C-MOVE
❏ C-FIND-CANCEL
❏ C-GET-CANCEL
❏ C-MOVE-CANCEL
Real-World Activity - Find SCP A.0
Associated Real-World The associated Real-World activity is to respond to query

Activity - Find SCP A requests to an SCU with the query model Patient Root, Study
Root and Patient/Study Only. Relational retrieve operation is
NOT supported. With a C-FIND-CANCEL request the running
query can be cancelled at any time. A.0
The SCP does support multiple C-FIND-requests over the same

association, but not multiple C-MOVE requests. A.0
0.0

July 2013
Accepted Presentation The Somaris/5 Query/Retrieve AE will accept Presentation Con-

Contexts - Find SCP A texts as shown in the following table: A.0
A
Patient Root 1.2.840.10008.5.1.4.1.2.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP See Note
Query/Retrieve Explicit VR Little Endian 1.2.840.10008.1.2.1
Model - FIND Explicit VR Big Endian 1.2.840.10008.1.2.2
Study Root 1.2.840.10008.5.1.4.1.2.2.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP See Note
Model - FIND Explicit VR Big Endian 1.2.840.10008.1.2.2
Patient/Study 1.2.840.10008.5.1.4.1.2.3.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP See Note

Only Query/ Explicit VR Little Endian 1.2.840.10008.1.2.1
Retrieve Model Explicit VR Big Endian 1.2.840.10008.1.2.2
- FIND
0.0

Note
C-FIND Extended Negotiation will NOT be supported
by the SCP. A
The order of preference in accepting a Transfer syntax is: A.0

0.0

July 2013
SOP Specific Conformance The Somaris/5 DICOM Query/Retrieve SCP supports hierarchical
Statement - Find SCP A queries with all mandatory and optional search keys. A.0
The following six notes apply to the handling of attribute

Patient’s Name (0010,0010) as Query/Retrieve SCP. The syntac-
tical structure of Patient’s Name (0010,0010) attribute is as fol-
lows: A.0
<single byte group>=<ideographic group>=<phonetic group> A.0
Each group may have up to five components, which are sepa-

rated by carets "^". A.0
❏ 1. Matching of Patient’s Name attribute (0010,0010) is done

case-insensitive.
❏ 2. If a search string matches the complete value of a data
base objectís Patient’s Name, a match will be returned.
❏ 3. If a search string matches an individual group (single byte,
ideographic or phonetic) of a data base object’s Patient’s
Name, a match will be returned.
❏ 4. If a search string matches two consecutive groups of a data

base objectís Patient’s Name, a match will be returned.
❏ 5. Redundant group separators "=" or component separators
"^" are treated as insignificant for matching.
❏ 6. Leading and trailing blanks within a component or a group
of Patient’s Name (0010,0010) are treated as insignificant for
matching.
Except for the attribute Patient’s Name (0010,0010) any other

query attribute contents will be treated Case Sensitive. A.0
With wildcard queries the symbol "?" is treated as "*" by the C-

FIND-SCP application. As a consequence the query string of
"?abc*" will be processed as "*abc*". A.0
0.0

If the value for the patient level unique key "Patient ID" is not
known, it may be returned with zero length. The attribute
"Image Comments" will not be included in the C-FIND-RSP, if it is
not set in the DB, even if it was requested as return key in the
related C-FIND-RQ. A.0
Usage of Storage Media File Set ID, Retrieve AE Title with C-

FIND-RSP message: A.0
❏ The C-FIND SCP may return the DICOM attributes StorageMe-

diaFileSetID (0088,0130) and StorageMediaFileSetUID
(0088,0140) as empty or not at all. The Storage Media File
Set ID - if existent - can be returned at Study/Series/Image
Level. Only on Image Level, the values of ONLINE, NEARLINE
or OFFLINE are returned to indicate the Storage Location of
the related instance.
❏ The C-FIND SCP may return the DICOM attributes Retrieve AE
Title (0008,0054) as empty or not at all. The Retrieve AE Title
- if existent - can only be returned at Image Level (for Patient
Root and Study Root models) or Study Level (for Patient/Study
Only model).
Relational Queries are NOT supported. A.0
A remote DICOM AE can cancel the running query by sending a

C-FIND-CANCEL. Matches are possibly continuing (more C-FIND
response with status PENDING) until the cancel operation has
completed. A.0
The supported attributes on the various levels of the three infor-

mation models are listed in the tables of the following sec-
tions. A.0
0.0

July 2013
Patient Root Information A.0
Model A
A
Patient level attributes, Patient Root Information ModelPatient level attributes A
Attribute name Tag A Type A Matching A
Patient name A (0010,0010) A R A single value,

wildcard, universal A
Patient id A (0010,0020) A U A single value,

Patient’s birth date A (0010,0030) A O A single value, range,

universal A
Patient’s birth time A (0010,0032) A O A single value, range,

universal A
Patient’s sex A (0010,0040) A O A single value,

Ethnic group A (0010,2160) A O A single value,

Patient comments A (0010,4000) A O A wildcard, universal A
Number of Patient related (0020,1200) A O A universal A
studies A
Number of Patient relates (0020,1202) A O A universal A
series A
instances A
A
Study level attributes, Patient Root Information Model A
Attribute name Tag A Usage SCU A Matching A
Study instance UID A (0020,000D) A U A single value,

list of UID A
Study id A (0020,0010) A R A single value,

0.0

Study level attributes, Patient Root Information Model A
Study date A (0008,0020) A R A single value, range,

universal A
Study time A (0008,0030) A R A single value, range,

universal A
Accession number A (0008,0050) A R A single value,

Referring physician’s name A (0008,0090) A O A single value,

Study description A (0008,1030) A O A single value,

Admitting diagnoses (0008,1080) A O A single value,

description A wildcard, universal A
Patient’s age A (0010,1010) A O A single value,

Patient’s size A (0010,1020) A O A single value,

universal A
Patient’s weight A (0010,1030) A O A single value,

universal A
Additional patient history A (0010,21B0) A O A wildcard, universal A
Name of physician reading (0008,1060) A O A single value,

study A wildcard, universal A
Modalities in Study A (0008,0061) A O A multiple values,

universal A
Number of study related series A (0020,1206) A O A universal A
Number of study related (0020,1208) A O A universal A
instances A
0.0

July 2013
A
Series level attributes, Patient Root Information Model A
Series instance UID A (0020,000E) A U A single value,

list of UID A
Series number A (0020,0011) A R A single value,

universal A
Modality A (0008,0060) A R A single value,

Laterality A (0020,0060) A O A single value,

Body part examined A (0018,0015) A O A single value,

Patient position A (0018,5100) A O A single value,

Smallest pixel value in series A (0028,0108) A O A single value, A
universal A
Largest pixel value in series A (0028,0109) A O A single value, A
universal A
Protocol name A (0018,1030) A O A single value,

Series date A (0008,0021) A O A single value, range,

universal A
Series time A (0008,0031) A O A single value, range,

universal A
Series description A (0008,103E) A O A single value,

Operators name A (0008,1070) A O A single value,

Performing physician’s name A (0008,1050) A O A single value,

0.0

Series level attributes, Patient Root Information Model A
Performed procedure step start (0040,0244) A O A universal A
date A
time A
Number of series related (0020,1209) A O A universal A
instances A
Referenced request sequence A (0040,A370) A O A sequence

matching A
A
Image level attributes, Patient Root Information Model A
SOP instance UID A (0008,0018) A U A single value,

list of UID A
Instance number A (0020,0013) A R A single value,

universal A
Content date A (0008,0023) A O A single value, range,

universal A
Content time A (0008,0033) A O A single value, range,

universal A
Modality A (0008,0060) A O A single value,

Image comments A (0020,4000) A O A universal A
Referenced Request Sequence A (0040,A370) A O A sequence

matching A
> Accession Number A (0008,0050) A O A single value,

universal A
> Requested Procedure ID A (0040,1000) A O A single value,

universal A
0.0

July 2013
Concept Name Code (0040,A043) A O A sequence

Sequence A matching A
> Code Value A (0080,0100) A O A single value,

universal, wildcard A
> Coding Scheme Designator A (0008,0102) A O A single value,

> Coding Scheme Version A (0008,0103) A O A single value,

> Code Meaning A (0008,0104) A O A single value,

Template Identifier A (0040,DB00) A O A single value,

Completion Flag A (0040,A491) A O A single value,

Verification Flag A (0040,A493) A O A single value,

Verifying Observer Sequence A (0040,A473) A O A sequence

matching A
> Verifying Organization A (0040,A072) A O A single value,

> Verifying Date Time A (0008,A030) A O A single value, range

matching,
universal, A
> Verifying Observer Name A (0008,A075) A O A single value,

> Verifying Oberser (0040,A088) A O A sequence

Identification Code Sequence A matching A
>> Code Value A (0008,0100) A O A single value,

0.0

>> Coding Scheme Designator A (0008,0102) A O A single value,

>> Coding Scheme Version A (0008,0103) A O A single value,

>> Code Meaning A (0008,0104) A O A single value,

0.0

July 2013
Study Root Information A
Model A
A
Study level attributes, Study Root Information Model A

Patient id A (0010,0020) A R A single value,


universal A

universal A

studies A
series A
instances A

list of UIDs A


universal A

universal A

0.0

Study level attributes, Study Root Information Model A





universal A

universal A
Occupation A (0010,2180) A O A single value,



universal A
instances A
0.0

July 2013
A
Series level attributes, Study Root Information Model A
Series instance UID A (0020,000E) A U A single value,

list of UID A
Series number A (0020,0011) A R A single value,

universal A
Modality A (0008,0060) A R A single value,

Laterality A (0020,0060) A O A single value,

Body part examined A (0018,0015) A O A single value,

Patient position A (0018,5100) A O A single value,

Smallest pixel value in series A (0028,0108) A O A single value, A
universal A
Largest pixel value in series A (0028,0109) A O A single value, A
universal A
Protocol name A (0018,1030) A O A single value,

Series date A (0008,0021) A O A single value, range,

universal A
Series time A (0008,0031) A O A single value, range,

universal A
Series description A (0008,103E) A O A single value,

Operators name A (0008,1070) A O A single value,

Performing physician’s name A (0008,1050) A O A single value,

0.0

Series level attributes, Study Root Information Model A
date A
time A
Number of series related (0020,1209) A O A universal A
instances A
A
Image level attributes, Study Root Information Model A
SOP instance UID A (0008,0018) A U A single value,

list of UID A
Instance number A (0020,0013) A R A single value,

universal A
Content date A (0008,0023) A O A single value, range,

universal A
Content time A (0008,0033) A O A single value, range,

universal A
Modality A (0008,0060) A O A single value,

Image comments A (0020,4000) A O A universal A
Referenced Request Sequence A (0040,A370) A O A sequence

matching A
> Accession Number A (0008,0050) A O A single value,

universal A
> Requested Procedure ID A (0040,1000) A O A single value,

universal A
Concept Name Code (0040,A043) A O A sequence

Sequence A matching A
0.0

July 2013
> Code Value A (0008,0100) A O A single value,

> Code Scheme Designator A (0008,0102) A O A single value,

> Code Scheme Version A (0008,0103) A O A single value,

> Code Meaning A (0008,0104) A O A single value,

Template Identifier A (0040,DB00) A O A single value,

Completion Flag A (0040,A491) A O A single value,

Verification Flag A (0040,A493) A O A single value,

Verifying Observer Sequence A (0040,A073) A O A sequence

matching A
> Verifying Organization A (0008,A072) A O A single value,

> Verifying Date Time A (0008,A030) A O A single value, range

matching,
universal A
> Verifying Observer Name A (0008,A075) A O A single value,

> Verifying Observer (0040,A088) A O A sequence

Identification Code Sequence A matching A
>> Code Value A (0008,0100) A O A single value,

>> Coding Scheme Designator A (0008,0102) A O A single value,

0.0

>> Coding Scheme Version A (0008,0103) A O A single value,

>> Code Meaning A (0008,0104) A O A single value,

0.0

July 2013
Patient Study Only A.0
Information Models A
A
Patient instance level, Patient Study Only Information Model A

Patient id A (0010,0020) A U A single value,


universal A

universal A

Ethnic group A (0010,2160) A O A single value,

studies A
series A
instances A
A
Study level attributes, Patient Study Only Information Model A

list of UIDs A

0.0

Study level attributes, Patient Study Only Information Model A

universal A

universal A






universal A

universal A
Occupation A (0010,2180) A O A single value,



universal A
instances A
0.0

July 2013
Note
The C-FIND-RSP message will contain the following
attributes: A.0
❏ Specific Character Set (0008,0005) (If there is a specific

character set in use).
❏ Query/Retrieve Level (0008,0052) from the C_FIND_RQ.
❏ Retrieve AE Title (0008,0054) at study, series and image
level.
This value is a list of AE titles from which the images can
be retrieved. Will be NULL except for the lowest level of
the query model (Image level for Patient Root or Study
Root and Study level for Patient/Study Only).
❏ Storage-Media File-set ID (0088,0130) at level study,
series and image. If Storage-Media File-set ID is not
present a NULL value will be returned.
❏ Attributes requested by C_FIND_RQ and supported by
the SCP
A
Note
See also → page A.2–62, SOP Specific Conformance
Statement - Find SCP A
0.0

The Find SCP returns following status codes: A.0
A
C-FIND return status A
Codes A
(0000,0902) A
A Unable to process A C001 A (0000,0901) A
(0000,0902) A
Cancel A Matching terminated due to Cancel request A FE00 A None A
Success A Matching is complete - No final Identifier is 0000 A None A
supplied A
Pending A Matches are continuing – Current Match is FF00 A Identifier A
supplied and any Optional Keys were

supported in the same manner as Required
Keys A
A Matches are continuing – Warning that one FF01 A Identifier A
or more Optional Keys were not supported

for existence and/or matching for this
identifier A
0.0

July 2013
Real World Activity - Get SCP A.0
Associated Real-World The associated Real-World activity is to respond to retrieve

Activity - Get SCP A requests initiated from a foreign SCU. The SCP supports the
query model Patient Root, Study Root and Patient/Study Only.
The Storage Service Class Conformance Statement describes the
C-STORE service which is generated by C-GET service. Relational
retrieve operation is NOT supported. A.0
Multiple C-GET requests over the same association are NOT sup-
ported. A.0

Contexts - GET SCP A Contexts as shown in the following table: A.0
A
Patient 1.2.840.10008.5.1.4.1.2.1.3 Implicit VR Little 1.2.840.10008.1.2 SCP See Note

Root Query/ Endian
Retrieve Explicit VR Little 1.2.840.10008.1.2.1
Model - GET Endian
Explicit VR Big 1.2.840.10008.1.2.2
Endian
Study Root 1.2.840.10008.5.1.4.1.2.2.3 Implicit VR Little 1.2.840.10008.1.2 SCP See Note
Query/ Endian
Retrieve Explicit VR Little 1.2.840.10008.1.2.1
Model - GET Endian
Explicit VR Big 1.2.840.10008.1.2.2
Endian
0.0

Patient/ 1.2.840.10008.5.1.4.1.2.3.3 Implicit VR Little 1.2.840.10008.1.2 SCP See Note

Study Only Endian
Query/ Explicit VR Little 1.2.840.10008.1.2.1
Retrieve Endian
Model - GET Explicit VR Big 1.2.840.10008.1.2.2
Endian
Note
C-GET Extended Negotiation will be NOT supported
by the SCP. A

SOP Specific Conformance At association establishment time the C-GET presentation con-
Statement - Get SCP A text must be negotiated along with the C-STORE sub-operations
which must be accomplished on the same association as the C-
GET operation. Relational retrieve operation is NOT supported. A.0
All unique keys have to be supplied according to the selected

Query/Retrieve Level. The related tables in the C-FIND SCP sec-
tion will give information about "U" marked key attributes. A.0
Note
In DICOM wildcard queries the symbol ’?’
is treated as ’*’ by Find SCP.
So a wildcard query with "?abc*"
is actually treated as "*abc*" A
0.0

July 2013
The Get SCP returns following status codes: A.0
A
C-MOVE return status A
Codes A
suboperations A
(0000,1021) A
(0000,1022) A
(0000,1023) A
A A (0000,0902) A
A Unable to process A C001 A (0000,0901) A
(0000,0902) A
(0000,1022) A
(0000,1023) A
(0000,1022) A
(0000,1023) A
(0000,1021) A
(0000,1022) A
(0000,1023) A
Warning A (0000,1021) A
(0000,1022) A
(0000,1023) A
0.0

Real-World Activity - Move SCP A.0
Associated Real-World The associated Real-World activity is to respond to retrieve

Activity - Move SCP A requests to an SCU. The SCP supports the query model Patient
Root, Study Root and Patient/Study Only. The Storage Service
Class Conformance Statement describes the C-STORE service
which is generated by the C-MOVE service. Relational retrieve
operation is NOT supported. A.0
Multiple C-MOVE requests over the same association are NOT

supported. A.0
Accepted Presentation The Somaris/5 DICOM application will propose Presentation

Contexts - Move SCP A Contexts as shown in the following table: A.0
A
Patient Root 1.2.840.10008.5.1.4.1.2.1.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCP See Note
Model - MOVE Explicit VR Big Endian 1.2.840.10008.1.2.2
Study Root 1.2.840.10008.5.1.4.1.2.2.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCP See Note
Model - MOVE Explicit VR Big Endian 1.2.840.10008.1.2.2
Patient/Study 1.2.840.10008.5.1.4.1.2.3.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCP See Note

Only Query/ Explicit VR Little Endian 1.2.840.10008.1.2.1
Retrieve Model Explicit VR Big Endian 1.2.840.10008.1.2.2
- MOVE
Note
C-MOVE Extended Negotiation will be NOT supported
by the SCP. A
0.0

July 2013

SOP Specific Conformance At association establishment time the C-MOVE presentation
Statement - Move SCP A context shall be negotiated. The C-STORE sub-operations is
done on a different association, specified in the C-MOVE
request, to transfer images to another SCP of the Storage Ser-
vice Class. Relational retrieve operation is NOT supported. A.0
All unique keys have to be supplied according to the selected

Query/Retrieve Level. The related tables in the C-FIND SCP sec-
tion will give information about "U" marked key attributes. A.0
Note
In DICOM wildcard queries the symbol ’?’
is treated as ’*’ by Find SCP.
So a wildcard query with "?abc*"
is actually treated as "*abc*" A
0.0

The Move SCP returns following status codes: A.0
A
C-MOVE return status A
Codes A
suboperations A
(0000,1021) A
(0000,1022) A
(0000,1023) A
A Identifier does not match SOP Class A A900 A (0000,0901) A
A A (0000,0902) A
Failed A Unable to process A C001 A (0000,0901) A
(0000,0902) A
(0000,1022) A
(0000,1023) A
(0000,1022) A
(0000,1023) A
(0000,1021) A
(0000,1022) A
(0000,1023) A
Warning A (0000,1021) A
(0000,1022) A
(0000,1023) A
0.0

July 2013
Print AE Specification A.0
The print management SCU (HCS) invokes print management

DIMSE services to transfer images from the local AE to the
remote SCP AE to print the images with the defined film format
and size on a selected network DICOM hardcopy printer. See
DICOM part 4 annex H. This is done in a "full-page" print mode.
A.0
Somaris/5 DICOM implementation provides Standard Conform-

ance to the following DICOM V3.0 Basic Grayscale Print Manage-
ment Meta SOP Classes as an SCU: A.0
Basic Gray Scale Print Management Meta SOP-Classes A

A
SOP Class Name SOP Class UID A
Basic Grayscale Print 1.2.840.10008.5.1.1.9 A
Management Meta SOP Class A
– Basic Film Session SOP Class A 1.2.840.10008.5.1.1.1 A
– Basic Film Box SOP Class A 1.2.840.10008.5.1.1.2 A
– Basic Grayscale Image Box 1.2.840.10008.5.1.1.4 A
SOP Class A
– Printer SOP Class A 1.2.840.10008.5.1.1.16 A
– Print Job SOP Class A 1.2.840.10008.5.1.1.14 A
– Presentation LUT SOP Class A 1.2.840.10008.5.1.1.23 A
0.0

Basic Color Print Management Meta SOP-Classes A

A
SOP Class Name SOP Class UID A
Basic Color Print Management 1.2.840.10008.5.1.1.18 A
Meta SOP Class A
– Basic Film Session SOP Class A 1.2.840.10008.5.1.1.1 A
– Basic Film Box SOP Class A 1.2.840.10008.5.1.1.2 A
– Basic Color Image Box 1.2.840.10008.5.1.1.4.1 A
SOP Class A
– Printer SOP Class A 1.2.840.10008.5.1.1.16 A
– Print Job SOP Class A 1.2.840.10008.5.1.1.14 A
0.0

July 2013
General A.0
Whenever a film is completely set up and printed by command

or automatism, the job is prepared for processing. As soon as
the queue is ready to process the job is activated and carried out
according to the processing data. The related Print application
will initiate an association to the print destination and process
the printing of the related information. A.0
The Somaris/5 DICOM Print application initiates one association

at a time for print device configured. A.0
The Somaris/5 DICOM implementation does not support asyn-

chronous communication (multiple outstanding transactions
over a single association). A.0

❏ “1.3.12.2.1107.5.1.4”
0.0

Triggered by the Print job queue the Print Management SCU

establishes an association by using the DICOM association ser-
vices. Withe the help of the N-GET request for the printer SOP
Class the Status is determined before printing. A.0
In case no problem is encountered with the N-CREATE/N-SET

Services for the related Basic Print SOP Classes the film sheet is
set up for printing and the image(s) is(are) transferred to the
printer device. A.0
After the last film is printed from the queue, the Print applica-
tion will leave open the association for another 60 seconds. If a
new film job is ready for printing within this time limit, the job
will be processed immediately over the association still open. If
there is no new job, the association is closed when the time out
has elapsed. This is done to optimize automatic printing. A.0
During the "idle time" (no open association to printer) the Print
application will issue a cyclic camera status request (using N-
GET of Printer SOP Class) every 5 minutes. A.0
Real-World Activity A.0
Associated Real-World Whenever a film sheet is prepared by the user, it is forwarded to

Activity - Printing a Printer the Printer Job queue. As soon as the associated Printer device
Job Queue Entry A is available the job is activated and an association is set up. A.0
The film sheet is internally processed, converted to a Standard/

1-1 page and then the page image is sent. Status is controlled
by awaiting any N-EVENT message all through the transfer until
the last image or film sheet is sent. A.0
If the response from the remote application contains a status

other than Success or Warning the association is aborted. A.0
0.0

July 2013

Contexts Presentation Contexts as shown in the following table: A.0
Context Table) A
A
Presentation context - Print SCU A
Basic Grayscale 1.2.840.10008.5.1.1.9 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Print Explicit VR Little Endian 1.2.840.10008.1.2.1
Management Explicit VR Big Endian 1.2.840.10008.1.2.2
Meta SOP class
Basic Color 1.2.840.10008.5.1.1.18 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Print Explicit VR Little Endian 1.2.840.10008.1.2.1
Management Explicit VR Big Endian , 1.2.840.10008.1.2.2
Meta SOP class
Basic film 1.2.840.10008.5.1.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

session SOP Explicit VR Little Endian 1.2.840.10008.1.2.1
class Explicit VR Big Endian 1.2.840.10008.1.2.2
Basic film box 1.2.840.10008.5.1.1.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
SOP class Explicit VR Little Endian 1.2.840.10008.1.2.1
Basic grayscale 1.2.840.10008.5.1.1.4 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

image box SOP Explicit VR Little Endian 1.2.840.10008.1.2.1
Basic color 1.2.840.10008.5.1.1.4.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

image box SOP Explicit VR Little Endian 1.2.840.10008.1.2.1
Printer SOP 1.2.840.10008.5.1.1.16 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

class Explicit VR Little Endian 1.2.840.10008.1.2.1
0.0

Print Job SOP 1.2.840.10008.5.1.1.14 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
class Explicit VR Little Endian 1.2.840.10008.1.2.1
Presentation 1.2.840.10008.5.1.1.23 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

LUT SOP class Explicit VR Little Endian 1.2.840.10008.1.2.1
0.0

July 2013
SOP Specific Conformance The Somaris/5 DICOM Print Management SCU conforms to the
Statement - Meta SOP DICOM Basic Grayscale Print Management Meta SOP Class and
Classes A Basic Color Print Management Meta SOP Class. A.0
The application uses a setting platform to define the properties

of the connected DICOM SCP, e.g.: A.0
❏ maximum number of print jobs in the queue

❏ maximum number of print copies
❏ supported film sizes of the connected DICOM SCP
❏ supported film formats of the DICOM SCP
❏ lookup table definition
The printing is only suspended in the case of a failure return sta-
tus of the SCP. A.0
0.0

Basic Film Session SOP Class A.0
The Basic Film Session information object definition describes

all the user defined parameter which are common for all the
films of a film session. The Basic Film Session refers to one or
more Basic Film Boxes and that are printed on one hardcopy
printer. A.0
The Somaris/5 DICOM Print application supports the following

DIMSE Service Elements for the Basic Film Session SOP class as
SCU: A.0
❏ N-CREATE
❏ N-DELETE
The Basic Film Session SOP class N-CREATE-RQ (SCU) uses fol-
lowing attributes: A.0
A
Attribute name Tag A Usage SCU A Supported Values A
Number of Copies A (2000,0010) A U A 1 A
Medium Type A (2000,0030) A U A BLUE FILM A
CLEAR FILM A
PAPER A
Film Destination A (2000,0040) A U A MAGAZINE A
PROCESSOR A
The number of copies sent to the DICOM printer is always 1, the

job is sent n times for n copies. A.0
0.0

July 2013
The Affected SOP Instance UID received with N-CREATE-RSP

message from SCP will be kept internally and used for later
requests (e.g. N-DELETE-RQ) on the Basic Film Session SOP Class
- see table below: A.0
A
Attribute name Tag A Source of information A
Requested SOP Instance UID A (0000,1000) A Affected SOP Instance UID of N-CREATE-
A RSP on Basic Film Session A
-> (0000,1001) A
The N-DELETE-RQ on the Basic Film Session SOP Class is used to

delete the complete Basic Film Session SOP Instance hierarchy. A.0
A.0
The Basic Film Session SOP class interprets the following status
codes (from N-CREATE-RSP, N-DELETE-RSP messages): A.0
A
Service Status Meaning A Protocol Codes A
Failure A Film session SOP instances hierarchy C600 A
does not contain film box SOP instances A
Unable to create print job, print queue is C601 A
full A
Image size is larger than images box size A C603 A
Warning A Memory allocation not supported A B600 A
Film session printing is not supported A B601 A
A Film box does not contain image box B602 A
(empty page) A
Success A Film belonging to the film session are 0000 A
accepted for printing A
0.0

Basic Film Box SOP Class A.0
The Basic Film Box information object definition describes all

the user defined parameter of one film of the film session. The
Basic Film Box information description defines the presentation
parameters which are common for all images on a given sheet
of film. A.0
The Basic Film Box refers to one or more Image Boxes. A.0
Supported as SCU are: A.0
❏ N-CREATE
❏ N-ACTION
❏ N-DELETE
The Basic Film Box SOP class N-CREATE-RQ message uses follow-
ing attributes (the used values for each attribute depend on the
DICOM Printer configuration within the Somaris/5 DICOM print
management SCU): A.0
A
Image Display Format A (2010,0010) A M A STANDARD\C-R A
Referenced Film Session (2010,0500) A M A A
Sequence A
> Referenced SOP Class UID A (0008,1150) A M A 1.2.840.10008.5.1.1.1 A
> Referenced SOP Instance UID A (0008,1155) A M A A
Film Orientation A (2010,0040) A M A PORTRAIT A
LANDSCAPE A
Film Size ID A (2010,0050) A M A 8INX10IN A
10INX12IN A
10INX14IN A
11INX14IN A
14INX14IN A
14INX17IN A
24CMX24CM A
24CMX30CM A
0.0

July 2013
Magnification Type A (2010,0060) A M A BILINEAR A
CUBIC A
NONE A
REPLICATE A
Border Density A (2010,0100) A U A BLACK A
WHITE A
Max Density A (2010,0130) A U A 0 < Value A
Min Density A (2010,0120) A U A 0 < Value < 50 A
Illumination A (2010,015E) A U A 0 < Value A
Required if Presentation
LUT is present A
Reflective Ambient Light A (2010,0160) A U A 0 < Value A
Required if Presentation
LUT is present A
Referenced Presentation LUT (2050,0500) A U A A
Sequence A
For Page Mode printing the Image Display format used is Stan-
dard\1,1. For Image Mode Printing the Image Display format
used is Standard\C,R where C is the number of Columns and R is
the number of Rows as specified in the Hardcopy Layout. A.0
The N-CREATE-RSP message from the Print SCP includes the Ref-
erenced Image Box Sequence with its SOP Class / Instance UID
pairs which will be kept internally to be further used for the sub-
sequent Basic Image Box SOP Class N-SET-RQ messages. A.0
0.0

When all Image Boxes (including parameters) for the film sheet
have been set, the Somaris/5 DICOM print manager will issue a
N-ACTION-RQ message with the SOP Instance UID of the Basic
Film Box (returned in N-CREATE-RSP of Basic Film Box SOP class)
and the Action Type ID of 1. A.0
A.0
0.0

July 2013
The affected SOP Instance UID received with N-CREATE-RSP mes-

sage will be kept internally and used for later requests (e.g. N-
DELETE-RQ) on the Basic Film Box SOP Class - see table below: A.0
A
A RSP on Basic Film Box A
-> (0000,1001) A
The Basic Film Box SOP class interprets the following status
codes: A.0
A
Failure A Unable to create print job; print queue is C602 A
full A
Image size is larger than image box size A C603 A
Warning A Film box does not contain image box B603 A
(empty page) A
Requested MinDensity or MaxDensity B605 A
outside of printer’s operating range A
Success A Film accepted for printing A 0000 A
0.0

Basic Grayscale Image Box SOP Class A.0
The Basic Grayscale Image Box information object definition is

the presentation of an image and image related data in the
image area of a film. The Basic Image Box information describes
the presentation parameters and image pixel data which apply
to a single image of a sheet of film. A.0
The Grayscale Image Box SOP class uses only the N-SET-RQ with
the following attributes: A.0
A
Image Position A (2020,0010) A M A 1 A
Basic Grayscale Image (2020,0110) A M A A
Sequence A
> Samples Per Pixel A (0028,0002) A M A 1 A
> Photometric Interpretation A (0028,0004) A M A MONOCH-ROME2 A
> Rows A (0028,0010) A M A A
> Columns A (0028,0011) A M A A
> Pixel Aspect Ratio A (0028,0034) A M A A
> Bits Allocated A (0028,0100) A M A 8,16 A
> Bits Stored A (0028,0101) A M A 8,12 A
> High Bit A (0028,0102) A M A 7,11 A
> Pixel Representation A (0028,0103) A M A 0 A
> Pixel Data A (7FE0,0010) A M A A
0.0

July 2013
The Grayscale Image Box SOP class interprets following status

codes: A.0
A
Failure A Image contains more pixel than printer C603 A
can print in Image box A
Insufficient memory in printer to store C605 A
the image A
Warning A Requested MinDensity or MaxDensity B605 A
outside of printer’s operating range A
Success A A 0000 A
0.0

Basic Color Image Box SOP Class A.0
The Basic Color Image Box information object definition is the

presentation of an image and image related data in the image
area of a film. The Basic Image Box information describes the
presentation parameters and image pixel data which apply to a
single image of a sheet of film. A.0
The Color Image Box SOP class uses only the N-SET-RQ with the
following attributes: A.0
A
Image Position A (2020,0010) A M A 1 A
Basic Color Image Sequence A (2020,0111) A M A A
> Samples Per Pixel A (0028,0002) A M A 3 A
> Photometric Interpretation A (0028,0004) A M A RGB A
> Planar Configuration A (0028,0006) A M A 0 A
> Rows A (0028,0010) A M A A
> Columns A (0028,0011) A M A A
> Pixel Aspect Ratio A (0028,0034) A M A A
> Bits Allocated A (0028,0100) A M A 8 A
> Bits Stored A (0028,0101) A M A 8 A
> High Bit A (0028,0102) A M A 7 A
> Pixel Representation A (0028,0103) A M A 0 A
> Pixel Data A (7FE0,0010) A M A A
0.0

July 2013
The Color Image Box SOP class interprets following status codes: A.0
A
Warning A Image size larger than image box size. A B604 A
Failure A Image contains more pixel than printer C603 A
can print in Image box A
Insufficient memory in printer to store C605 A
the image A
Success A A 0000 A
0.0

Presentation LUT SOP Class A.0
The objective of the Presentation LUT is to realize image hard-

copy printing tailored for specific modalities, applications, and
user preferences. A.0
The output of the Presentation LUT is Presentation Values (P-

Values). P-Values are approximately related to human percep-
tual response. They are intended to facilitate common input for
hardcopy. P-Values are intended to be independent of the spe-
cific class or characteristics of the hardcopy device. A.0
A
Attributes of the N_CREATE_RQ on the Presentation LUT SOP Class A
Presentation LUT Shape A (2050,0020) A U A IDENTITY A
The affected SOP Instance UID received with N-CREATE-RSP mes-

sage wil be kept internally and is used for later requests on the
Basic Film Box (N-CREATE-RQ) and on the Presentation LUT (N-
DELETE-RQ) - see below. A.0
A
A RSP on Presentation LUT A
-> (0000,1001) A
The Presentation LUT SOP class interprets the following status

codes: A.0
A
Warning A Requested Min Density or Max Density B605 A
outside the HCD´soperating range. HCD

will use its respective minimum or
maximum density value instead. A
Success A Presentation LUT successfully created A 0000 A
0.0

July 2013
Printer SOP Class A.0
The Printer SOP Class is the possibility to monitor the status of

the hardcopy printer in a synchronous and an asynchronous
way. A.0
The SCU uses the mandatory N-EVENT Report DIMSE service to

monitor the changes of the printer status in an asynchronous
way. A.0
It can directly ask the Printer (SCP) for its status or can receive
Events from the Print SCP asynchronously: A.0
❏ N_GET as SCU
❏ N_EVENT_REPORT as SCU
In both cases the following information is supported: A.0
A
Event type name Event A Attributes A Tag A Usage SCU A
Normal A 1 A A A A
Warning A 2 A Printer Status Info A (2110,0020) A U A
Failure A 3 A Printer Status Info A (2110,0020) A U A
0.0

A
Attribute name Tag A Usage SCP A supported values A
Printer Status A (2110,0010) A M A NORMAL A
FAILURE A
WARNING A
Printer Status Info A (2110,0020) A M A see → page A.2–

108. A
For a detailed description of how Somaris/5 reacts to the various

messages please refer to → page A.2–108, DICOM Print SCU -
detailed status displays. A.0
Print Job SOP Class A.0
The Print Job SOP Class is the possibility to monitor the execu-
tion of the print process. A.0
The Somaris/5 DICOM Print application supports the optional N-

EVENT-REPORT DIMSE service to receive the changes of the print
job status in an asynchronous way. A.0
It can receive events from the Print SCP asynchronously: A.0
❏ N-EVENT-REPORT
A.0
Note
Somaris/5 does not support receiving N-EVENT from the
camera during print sessions, normally this is configurable
in the camera. A
0.0

July 2013
The following information is supported: A.0
A
Pending A 1 A Execution Status (2100,0030) A U A
Info A
Print Job ID A (2100,0010) A -

(Print Queue
Management SOP
Class not
supported) A
Film Session Label A (2000,0050) A U A
Printer Name A (2110,0030) A U A
Printing A 2 A Execution Status (2100,0030) A U A
Info A

(Print Queue
Management SOP
Class not
supported) A
Done A 3 A Execution Status (2100,0030) A U A
Info A

(Print Queue
Management SOP
Class not
supported) A
0.0

Failure A 4 A Execution Status (2100,0030) A U A
Info A

(Print Queue
Management SOP
Class not
supported) A
For a detailed description of how Somaris/5 reacts to the various

messages please refer to → page A.2–108, DICOM Print SCU -
detailed status displays. A.0
0.0

July 2013
DICOM Print SCU - detailed The following tables document the behavior of the Somaris/5
status displays A system in response to messages received for the printer SOP
class and the print job SOP class. A.0
Definitions of camera symbols: A.0
❏ Idle: Camera is installed and ready; idle icon is displayed.

❏ Interact: The user has to react in near future, but not imme-
diately.
❏ Example: A camera was low in 8x10 clear sheets: LOW 8x10
CLR was sent by N-EVENT-REPORT.
❏ Queue Stopped: The user has to react immediately. Either the
camera needs immediate interaction or a job has been
aborted.
Example: A camera is out of 8x10 clear sheets, or camera is
down, or a film job is aborted.
A.0
Note
Different camera symbols are displayed according to the
Printer Status Info. A
The Printer Status (Success, Warning, Failure) is not evaluated,

since the Printer Status Info is much more detailed and allows a
more appropriate reaction of the system. A.0
0.0

A
Printer Status Infos within Printer SOP Class/Execution Status Infos within Print Job SOP
Class A
Printer Status Description Message string visible Other action for

info/Execution in the Status Bar UI/camera symbol A
Status info
NORMAL A Camera is ready. A Camera is ready. A <None>/idle A
BAD RECEIVE There is a problem with the Problem with receive <None>/interact A
MGZ A film receive magazine. magazine. A
Films from the printer

cannot be transported into
the magazine. A
BAD SUPPLY There is a problem with a Problem with supply <None>/interact A
MGZ A film supply magazine. Films magazine. A
from this magazine cannot

be transported into the
printer. A
CALIBRATING A Printer is performing self Self calibration. Please <None>/idle A
calibration, it is expected to wait. A
be available for normal

operation shortly. A
CALIBRATION An error in the printer Problem in calibration. <None>/interact A
ERR A calibration has been Film quality may not be

detected, quality of optimal. A
processed films may not be

optimal. A
CHECK A problem with the Problem with <None>/interact A
CHEMISTRY A processor chemicals has chemistry. Film quality

been detected, quality of may not be optimal. A
processed films may not be

optimal. A
CHECK SORTER A There is an error in the film Error in film sorter. A <None>/interact A
sorter. A
0.0

July 2013
Class A

Status info
CHEMICALS There are no processing Camera chemistry <None>/interact A
EMPTY A chemicals in the processor, empty. Please check. A
films will not be printed and

processed until the
processor is back to normal. A
CHEMICALS The chemical level in the Camera chemistry low. <None>/interact A
LOW A processor is low, if not Please check. A
corrected, it will probably

shut down soon. A
COVER OPEN A One or more printer or Camera cover, drawer <None>/interact A
processor covers, drawers, or door open. A
doors are open. A
ELEC CONFIG Printer configured Camera configured Queue for this

ERR A improperly for this job. A improperly for this job. camera will be
Queue stopped. A
STOPPED/Queue
stopped A
ELEC DOWN A Printer is not operating due Camera electrical <None>/interact A
to some unspecified hardware problem. A
electrical hardware
problem. A
ELEC SW Printer not operating for Camera software Queue for this
ERROR A some unspecified software problem. Queue camera will be
error. A stopped. A
STOPPED/queue
stopped A
EMPTY 8x10 A The 8x10 inch film supply 8x10 film supply <None>/interact A
magazine is empty. A empty. A
0.0

Class A

Status info
EMPTY 8x10 The 8x10 inch blue film 8x10 blue film supply <None>/interact A
BLUE A supply magazine is empty. A empty. A
EMPTY 8x10 The 8x10 inch clear film 8x10 clear film supply <None>/interact A
CLR A supply magazine is empty. A empty. A
EMPTY 8x10 The 8x10 inch paper supply 8x10 paper supply <None>/interact A
PAPR A magazine is empty. A empty. A
EMPTY 10x12 The 10x12 inch paper 10x12 paper supply <None>/interact A
PAPR A supply magazine is empty. A empty. A
0.0

July 2013
Class A

Status info
0.0

Class A

Status info
EMPTY A4 The A4 paper supply A4 paper supply empty. A <None>/interact A
PAPR A magazine is empty. A
EMPTY A4 The A4 transparency supply A4 transparency supply <None>/interact A
TRANS A magazine is empty. A empty. A
EXPOSURE The exposure device has Exposure device has <None>/interact A
FAILURE A failed due to some failed. A
unspecified reason. A
FILM JAM A A film transport error has Film jam. A <None>/interact A
occurred and a film is

jammed in the printer or
processor. A
0.0

July 2013
Class A

Status info
FILM TRANSP There is a malfunction with Film transport problem. A <None>/interact A
ERR A the film transport, there

may or may not be a film
jam. A
FINISHER The finisher is empty. A Finisher is empty. A <None>/interact A
EMPTY A
FINISHER The finisher is not Finisher problem. A <None>/interact A
ERROR A operating due to some

FINISHER LOW A The finisher is low on Finisher low. A <None>/interact A
supplies. A
LOW 8x10 A The 8x10 inch film supply 8x10 film supply low. A <None>/interact A
magazine is low. A
LOW 8x10 The 8x10 inch blue film 8x10 blue film supply <None>/interact A
BLUE A supply magazine is low. A low. A
LOW 8x10 CLR A The 8x10 inch clear film 8x10 clear film supply <None>/interact A
supply magazine is low. A low. A
LOW 8x10 The 8x10 inch paper supply 8x10 paper supply low. A <None>/interact A
PAPR A magazine is low. A
magazine is low. A
LOW 10x12 The 10x12 inch clear film 10x12 clear film supply <None>/interact A
CLR A supply magazine is low. A low. A
0.0

Class A

Status info
LOW 10x12 The 10x12 inch paper 10x12 paper supply <None>/interact A
PAPR A supply magazine is low. A low. A
magazine is low. A
magazine is low. A
magazine is low. A
0.0

July 2013
Class A

Status info
magazine is low. A
magazine is low. A
magazine is low. A
0.0

Class A

Status info
LOW A4 PAPR A The A4 paper supply A4 paper supply low. A <None>/interact A
magazine is low. A
LOW A4 TRANS A The A4 transparency supply A4 transparency supply <None>/interact A
magazine is low. A low. A
NO RECEIVE The film receive magazine Film receiver not <None>/interact A
MGZ A no available. A available. A
NO RIBBON A The ribbon cartridge needs Replace ribbon <None>/interact A
to be replaced. A cartridge. A
NO SUPPLY The film supply magazine Film supply not <None>/interact A
MGZ A specified for this job is not available. A
available. A
CHECK The printer is not ready at Check camera. A <None>/interact A
PRINTER A this time, operator

intervention is required to
make the printer available. A
CHECK PROC A The processor is not ready Check processor. A <None>/interact A
at this time, operator

intervention is required to
make the printer available. A
PRINTER The printer is not operating Camera down. A <None>/interact A
DOWN A due to some unspecified

reason. A
0.0

July 2013
Class A

Status info
PRINTER INIT A The printer is not ready at Camera initializing. A <None>/idle A
this time, it is expected to

become available without
intervention, For example,
it may be in a normal warm-
up state. A
PRINTER The printer has been Camera off-line. A <None>/interact A
OFFLINE A disabled by an operator or

service person. A
PROC DOWN A The processor is not Processor down. A <None>/interact A
operating due to some

PROC INIT A The processor is not ready Processor initializing. A <None>/idle A
at this time, it is expected to

become available without
intervention. For example,
it may be in a normal warm-
up state. A
PROC Processor chemicals are Processor chemicals <None>/interact A
OVERFLOW FL A approaching the overflow overflow. A
full mark. A
PROC Processor chemicals have Processor chemicals <None>/interact A
OVERFLOW HI A reached the overflow full near overflow. A
mark. A
QUEUED A Print job in Queue A - A <None>/idle A
RECEIVER FULL A The Film receive magazine Receiver full. A <None>/interact A
is full. A
0.0

Class A

Status info
REQ MED NOT The requested film, paper, Install media supply. A <None>/interact A
INST A or other media supply

magazine is installed in the
printer, but may be
available with operator
intervention. A
REQ MED NOT The requested film, paper, Media supply not Queue for this
AVAI A or other media requested is available on this camera will be
not available on this camera. Queue STOPPED/queue
printer. A stopped. Change stopped A
camera. A
RIBBON ERROR A There is an unspecified Error with print ribbon. A <None>/interact A
problem with the print

ribbon. A
SUPPLY EMPTY A The printer is out of film. A Camera out of film. A <None>/interact A
SUPPLY LOW A The film supply is low. A Film supply low. A <None>/interact A
UNKNOWN A There is an unspecified Unspecified problem <None>/interact A
problem. A with camera. A
0.0

July 2013
A
Printer Status Infos: Additional Agfa printer status infos A

info in the Status Bar syngo/camera
symbol A
WARMING UP A Printer is in the warm-up Camera is warming up. A <None>idle A
stage. Spooling of print

jobs to disk is still possible. A
OFFLINE A Printer is switched off-line. Camera is switched off- <None>/interact A
Spooling of print jobs to line. A
disk is still possible. A
NONE A General printer warning, no - A <None>/idle A
specific information is
available. Spooling of print
jobs to disk is still possible. A
A
Printer Status Infos: Additional Kodak infos for Pacs Link (formerly Imation cameras) A

symbol A
SUPPLY MGZ The supply magazine has Film supply has an <None>/interact A
ERR A an error. A error. A
0.0

A
Printer Status Infos: Additional Kodak infos for Kodak 190 A

symbol A
PRINTER The printer has stopped A Camera has stopped. A <None>/interact A
STOPPED A
FATAL ERROR A Fatal error. A Fatal error. Queue Queue for this
stopped. A camera will be
STOPPED/queue
stopped A
0.0

July 2013
A
Printer Status Infos: Additional Kodak infos for 2180/1120 A

symbol A
PRINTER NOT Printer not ready. A Camera not ready. A <None>/interact A
RDY A A
CHECK Check processor. A Check processor. A <None>/interact A
PROCESSOR A A
NO TONER A No toner. A No toner. A <None>/interact A
FATAL A Fatal error. A Fatal error. Queue Queue for this

stopped. A camera will be
STOPPED/queue
stopped A
A
Printer Status Infos: Additional Codonics infos A

symbol A
STANDARD A Printer is ready. A Camera is ready. A <None>/Normal A
LOAD A-SIZE A Load A-size media. A Load A-size media. A <None>/interact A
LOAD A- Load A-size black and white Load A-size black and <None>/interact A
DVPAPER A paper. A white paper. A
LOAD A- Load A-size color paper. A Load A-size color paper. A <None>/interact A
CVPAPER A
LOAD A- Load A-size transparencies. A Load A-size <None>/interact A
CVTRANS A transparencies. A
LOAD A4-SIZE A Load A4-size media. A Load A4-size media. A <None>/interact A
LOAD A4- Load A4-size black and Load A4-size black and <None>/interact A
DVPAPER A white paper. A white paper. A
0.0


symbol A
LOAD A4- Load A4-size color paper. A Load A4-size color <None>/interact A
CVPAPER A paper. A
LOAD A4- Load A4-size Load A4-size <None>/interact A
CVTRANS A transparencies. A transparencies. A
LOAD LA-SIZE A Load LA-size media. A Load LA-size media. A <None>/interact A
LOAD LA- Load LA-size black and Load LA-size black and <None>/interact A
LOAD LA- Load LA-size color paper. A Load LA-size color <None>/interact A
CVPAPER A paper. A
LOAD LA- Load LA-size Load LA-size <None>/interact A
LOAD LA4-SIZE A Load LA4-size media. A Load LA4-size media. A <None>/interact A
LOAD LA4- Load LA4-size black and Load LA4-size black and <None>/interact A
LOAD LA4- Load LA4-size color paper. A Load LA4-size color <None>/interact A
CVPAPER A paper. A
LOAD LA4- Load LA4-size Load LA4-size <None>/interact A
LOAD XLA-SIZE A Load XLA-size media. A Load XLA-size media. A <None>/interact A
LOAD XLA- Load XLA-size black and Load XLA-size black and <None>/interact A
LOAD XLA- Load XLA-size color paper. A Load XLA-size color <None>/interact A
CVPAPER A paper. A
LOAD XLA- Load XLA-size Load XLA-size <None>/interact A
0.0

July 2013

symbol A
LOAD XLA4- Load XLA4-size media. A Load XLA4-size media. A <None>/interact A
SIZE A
LOAD XLA4- Load XLA4-size black and Load XLA4-size black <None>/interact A
DVPAPE A white paper. A and white paper. A
LOAD XLA4- Load XLA4-size color paper. A Load XLA4-size color <None>/interact A
CVPAPE A paper. A
LOAD XLA4- Load XLA4-size Load XLA4-size <None>/interact A
CVTRAN A transparencies. A transparencies. A
LOAD XLW- Load XLW-size media. A Load XLW-size media. A <None>/interact A
SIZE A
LOAD XLW- Load XLW-size black and Load XLW-size black <None>/interact A
DVPAPER A white paper. A and white paper. A
LOAD XLW- Load XLW-size color paper. A Load XLW-size color <None>/interact A
CVPAPER A paper. A
LOAD 8X10- Load 8x10 media. A Load 8x10 media. A <None>/interact A
SIZE A
LOAD 8X10- Load 8x10 black and white Load 8x10 black and <None>/interact A
DVFILM A film. A white film. A
SUPPLY The film supply magazine Film supply not <None>/interact A
MISSING A specified for this job is not available. A
available. A
RIBBON Ribbon is missing. A Ribbon is missing. A <None>/interact A
MISSING A
RIBBON EMPTY A Ribbon is empty. A Ribbon is empty. A <None>/interact A
0.0


symbol A
TOP COVER Top cover of printer is open. A Top cover of camera is <None>/interact A
OPEN A open. A
Additional DICOM Execution Status Information - evaluation. A.0
0.0

July 2013
A
Additional DICOM Execution Status Infos A
Execution Sta- Description Message string visible Other action for

tus info in the Status Bar syngo/camera
symbol A
INVALID PAGE The specified page layout Film Job cannot be Queue for this
DES A cannot be printed or other printed on this camera. camera will be
page description errors Queue stopped. Please STOPPED/queue
have been detected. A redirect film job. A
stopped A
INSUFFIC There is not enough Not enough memory Queue for this
MEMORY A memory available to available in camera. camera will be
complete this job. A Queue stopped. Please STOPPED/queue
continue queue or stopped A
change camera. A
NONE A General printer warning, no - A <None>/idle A
specific information is
available. Spooling of print
jobs to disk is still possible.
A
Additional DICOM Execution Status Information A.0
Printer Status Info and Execution Status Info are defined terms
and can therefore be extended or reduced by camera manufac-
turers. Therefore syngo shall be flexible. A.0
0.0

If any other printer status info or execution status info is

received, syngo will react as shown in the following table: A.0
A.0
Printer Sta- Printer Execution Description Message string visi- Other action for
tus/Execu- Status Info ble in the Status Bar syngo/camera
tion symbol
WARNING A <any other> A <not defined Camera info: <status <None>/interact A
A status info> A info> A
A A
FAILURE A <any other> A <not defined Camera info: <status Queue for this
A status info> A info> A camera will be
A Queue stopped. A STOPPED/Queue
stopped A
0.0

July 2013
Modality Worklist AE Specification A.0
The Modality Worklist SCU (patient registration in conjunction

with the network application) requests that the remote SCP per-
forms a match of all keys specified in the query against the infor-
mation in its worklist database. A.0
SIEMENS Somaris/5 DICOM implementation provides Standard

Conformance to the following DICOM V3.0 SOP Class as an
SCU: A.0

A
Modality Worklist Information 1.2.840.10008.5.1.4.31 A
Model - FIND A
0.0

General A.0
It is possible to configure a cyclic update of the modality sched-

uler database through a background worklist request with date/
time and modality information. A.0
In addition the user can request worklist update with "Update

Worklist". No duplicate entries will be added in the Scheduler
DB. Entries are uniquely identified by the Study Instance UID
(0020,000D) for the Requested Procedure and the SPS ID
(0040,0009) in the SPS Sequence (0040,0100). A.0
An interactive worklist query can be issued with search criteria

entered in the patient based Query dialog from the patient
browser. A.0
The Somaris/5 DICOM application initiates one association at a

time to query worklist entry data. A.0
The Somaris/5 DICOM implementation does not support asyn-

chronous communication (multiple outstanding transactions
over a single association). A.0

❏ “1.3.12.2.1107.5.1.4"
0.0

July 2013
The network application will (if configured) query the worklist

periodically or by user request. Ever then it establishes an asso-
ciation by using the DICOM association services. During associ-
ation establishment the negotiation of SOP classes to exchange
the capabilities of the SCU and the SCP is not supported. A.0
The following DIMSE-C operation is supported as SCU: A.0
❏ C-FIND
Real-World Activity A.0
Associated Real-World A network application will perform worklist queries with the C-
Activity - Query (Update) FIND request at regular intervals. In addition it can be triggered
Worklist A by immediate request. The received worklist items will be com-
pared with the contents of the local scheduler database. New
items will be inserted into scheduler database. A.0
After each broad query all RP/SPS that were cancelled or

rescheduled to another modality at the RIS will be automatically
removed from the scheduler DB if A.0
❏ the Examination of this procedure has not been started or fin-

ished yet
❏ the corresponding configuration item "Automatic removal of
cancelled/rescheduled Request" was checked in the Service
UI under DICOM / HIS/RIS Node
No automatic clean-up of the scheduler DB is performed after a
Patient based Query since the worklist received does not give
the complete list of all currently scheduled procedures for the
modality. A.0
0.0


Contexts - Query (Update) Contexts as shown in the following table: A.0
Worklist A
A
Proposed presentation contexts A
Modality 1.2.840.10008.5.1.4.31 A Implicit VR Little 1.2.840.10008.1.2 A SCU A None A
Worklist Endian A
Information Explicit VR Little 1.2.840.10008.1.2.1 A
Model - Endian A
FIND A Explicit VR Big 1.2.840.10008.1.2.2 A
Endian A
0.0

July 2013
SOP Specific Conformance Search Key Attributes of the Worklist C-FIND A.0
Statement - Update Worklist A

The Somaris/5 DICOM worklist SCU supports "broad worklist
queries" with all required search keys. A.0
The following tables describe the "broad query" search keys that
the SCU supports, which is a query for all tasks scheduled for the
own modality or own modality application entity defined with
the following search keys: A.0
A
Search Key Attributes in a broad worklist query A
Attribute namea Tag A Matching Key Query value A
Type A
Scheduled Procedure Step A A A A
Scheduled Procedure Step (0040,0100) A R A A
Sequence A
> Scheduled Station AE Title A (0040,0001) A R A Configurableb:

own AET
or "*" A
> Scheduled Procedure Step (0040,0002) A R A Configurable:

Start Date A inserted in UIc or n
days before to m
days after today A
> Scheduled Procedure Step (0040,0003) A R A Configurable:

Start Time A inserted in UId or
0:00-23:59 A
> Modality A (0008,0060) A R A Configurableb: own

modality or "*" A
a. No other attributes of Register Dialog used for C-FIND

b. One and only one of the attributes "Modality" and "AE Title" is set to "*". There is a configura-
tion parameter telling which of them. The otherone is always set to the "own" value (i.e. own
modality respectively own AE Title).
c. <startDate>-<endDate>
d. <startTime>-<endTime>
0.0

A.0
Note
Since various SCP implementations depend on the Specific
Character Set attribute to be sent with the C-FIND in order
to deliver the attribute filled with the C-FIND-RSP (see
below), as a default the attribute will be sent even if empty.
In case this turns out to be a problem for a specific SCP in
cooperation with Siemens this can be configured not to
include this attribute. A
Return Key Attributes of the Worklist C-FIND-RSP A.0
The Somaris/5 DICOM worklist SCU supports worklist queries

with return key attributes of all types. The following tables
describe the return keys that the SCU supports. A.0
An "x" in the UI column will indicate that the attribute is visual-

ized when browsing the Worklist results with Patient Browser
and/or during Patient Registration. The Patient Browser display
is additionally influenced by the related Browser configuration. A.0
A tag in the IOD column will indicate that the related attribute is
included into the SOP Instances of the IODs created during pro-
cessing of this worklist request. A.0
A tag in the MPPS column will indicate that the related attribute
is included into the SOP Instances of the MPPS objects created
during processing of this worklist request. (See also the table →
page A.2–148 and → page A.2–153). A.0
0.0

July 2013
A
Attribute name Tag A Return UI A IOD A MPPS A
Key Type A
SOP Common
a
Specific Character Set A (0008,0005) A 1C A - A (0008,0005) A (0008,0005) A
Scheduled Procedure Step A A
Scheduled Procedure Step (0040,0100) A 1 A A A A
Sequence A
> Modality A (0008,0060) A 1 A x A (0008,0060) A (0008,0060) A
> Requested Contrast Agent A (0032,1070) A 2C A x A (0032,1070) A A
> Scheduled Station AE Title A (0040,0001) A 1 A x A A (0040,0241) A
> Scheduled Procedure Step (0040,0002) A 1 A x A A A
Start Date A
Start Time A
> Scheduled Procedure Step (0040,0004) A 3 A - A A A
End Date A
> Scheduled Procedure Step (0040,0005) A 3 A - A A A
End Time A
> Scheduled Performing (0040,0006) A 1 A x A (0008,1050) A (0008,1050) A
Physician’s Name A
> Scheduled Procedure Step (0040,0007) A 1C A x A (0040,0007) A (0040,0007) A
Description A (0040,0254) A (0040,0254) A
> Scheduled Protocol Code (0040,0008) A 1C A - A (0040,0008) A (0040,0008) A
Sequence A (0040,0260) A (0040,0260) A
>> Code Value A (0008,0100) A 1C A x A A A
>> Coding Scheme (0008,0102) A 1C A x A A A
Designator A
>> Coding Scheme Version A (0008,0103) A 3 A x A A A
>> Code Meaning A (0008,0104) A 3 A x A A A
0.0

Key Type A
> Scheduled Procedure Step (0040,0009) A 1 A x A (0040,0009) A (0040,0009) A
ID A (0040,0253) A (0040,0253) A
> Scheduled Station Name A (0040,0010) A 2 A x A A A
> Scheduled Procedure Step (0040,0011) A 2 A x A A (0040,0242) A
Location A
> Pre-Medication A (0040,0012) A 2C A x A A A
Status A
> Comments on the (0040,0400) A 3 A - A A A
Scheduled Procedure Step A
Requested Procedure A A
Referenced Study Sequence A (0008,1110) A 2 A - A (0008,1110) A (0008,1110) A
> Referenced SOP Class UID A (0008,1150) A 1C A - A A A
> Referenced SOP Instance (0008,1155) A 1C A - A A A
UID A
Study Instance UID A (0020,000D) A 1 A - A (0020,000D) A (0020,000D

) A
Requested Procedure (0032,1060) A 1C A x A (0032,1060) A (0032,1060) A
Description A
Requested Procedure Code (0032,1064) A 1C A - A (0032,1032) A (0032,1032) A
Sequence A (0032,1064) A
> Code Value A (0008,0100) A 1C A x A A A
> Code Scheme Designator A (0008,0102) A 1C A x A A A
> Code Scheme Version A (0008,0103) A 3 A x A A A
> Code Meaning A (0008,0104) A 3 A x A A A
Requested Procedure ID A (0040,1001) A 1 A x A (0040,1001) A (0040,1001) A
(0020,0010) A (0020,0010) A
0.0

July 2013
Key Type A
Reason for the Requested (0040,1002) A 3 A - A A A
Procedure A
Requested Procedure Priority A (0040,1003) A 2 A x A A A
Patient Transport (0040,1004) A 2 A - A A A
Arrangements A
Requested Procedure (0040,1005) A 3 A - A A A
Location A
Confidentiality Code A (0040,1008) A 3 A - A A A
Reporting Priority A (0040,1009) A 3 A - A A A
Names of Intended (0040,1010) A 3 A - A (0008,1048) A A
Recipients of results A
Requested Procedure (0040,1400) A 3 A x A A A
Comments A
Imaging Service Request A A
Accession Number A (0008,0050) A 2 A x A (0008,0050) A (0008,0050) A
Referring Physician’s Name A (0008,0090) A 2 A x A (0008,0090) A A
Requesting Physician A (0032,1032) A 2 A x A (0032,1032) A (0032,1032) A
Requesting Service A (0032,1033) A 3 A x A (0032,1033) A A
Reason for the Imaging (0040,2001) A 3 A - A A A
Service Request A
Issuing Date of Imaging (0040,2004) A 3 A - A A A
Service Request A
Issuing Time of Imaging (0040,2005) A 3 A - A A A
Service Request A
Placer Order Number / (0040,2016) A 3 A - A A (0040,2016) A
Imaging Service Request A
0.0

Key Type A
Filler Order Number / Imaging (0040,2017) A 3 A - A A (0040,2017) A
Service Request A
Order entered by... A (0040,2008) A 3 A - A A A
Order Enterer’s Location A (0040,2009) A 3 A - A A A
Order Callback Phone (0040,2010) A 3 A - A A A
Number A
Imaging Service Request (0040,2400) A 3 A x A A A
Comments A
Visit Identification A A
Institution Name A (0008,0080) A 3 A x A (0008,0080) A A
Institution Address A (0008,0081) A 3 A - A (0008,0081) A A
Institution Code Sequence A (0008,0082) A 3 A - A A A
> Code Value A (0008,0100) A 1C A A A A
> Code Scheme Designator A (0008,0102) A 1C A A A A
> Code Scheme Version A (0008,0103) A 3 A A A A
> Code Meaning A (0008,0104) A 3 A A A A
Admission ID A (0038,0010) A 2 A x A A A
Issuer of Admission ID A (0038,0011) A 3 A - A A A
Visit Status A A
Visit Status ID A (0038,0008) A 3 A - A A A
Current Patient Location A (0038,0300) A 2 A x A A A
Patient’s Institution (0038,0400) A 3 A - A A A
Residence A
Visit Comments A (0038,4000) A 3 A - A A A
A A
0.0

July 2013
Key Type A
Visit Relationship A A
Referenced Study Sequence A (0008,1110) A 3 A - A A A
UID A
Referenced Patient (0008,1120) A 2 A - A A (0008,1120) A
Sequence A
UID A
Visit Admission A A
Referring Physician’s Name A (0008,0090) A 2 A x A (0008,0090) A A
Referring Physician’s Address A (0008,0092) A 3 A - A A A
Referring Physician’s Phone (0008,0094) A 3 A - A A A
Numbers A
Admitting Diagnoses (0008,1080) A 3 A x A (0008,1080) A A
Description A
Admitting Diagnosis Code (0008,1084) A 3 A A A A
Sequence A
Route of Admissions A (0038,0016) A 3 A - A A A
Admitting Date A (0038,0020) A 3 A - A A A
Admitting Time A (0038,0021) A 3 A - A A A
0.0

Key Type A
Patient Identification A A
Patient’s Name A (0010,0010) A 1 A x A (0010,0010) A (0010,0010) A
Patient ID A (0010,0020) A 1 A x A (0010,0020) A (0010,0020) A
Issuer of Patient ID A (0010,0021) A 3 A - A (0010,0021) A A
Other Patient IDs A (0010,1000) A 3 A x A (0010,1000) A A
Other Patient Names A (0010,1001) A 3 A x A (0010,1001) A A
Patient’s Birth Name A (0010,1005) A 3 A - A (0010,1005) A A
Patient’s Mother’s Birth (0010,1060) A 3 A - A (0010,1060) A A
Name A
Medical Record Locator A (0010,1090) A 3 A - A (0010,1090) A A
Patient Demographic A A
Patients Birth Date A (0010,0030) A 2 A x A (0010,0030) A (0010,0030) A
Patients Birth Time A (0010,0032) A 3 A - A (0010,0032) A A
Patient’s Sex A (0010,0040) A 2 A x A (0010,0040) A (0010,0040) A
Patient’s Insurance Plan Code (0010,1050) A 3 A - A (0010,1050) A A
Sequence A
Patient’s Age A (0010,1010) A 3 A x A (0010,1010) A A
Patient’s Size A (0010,1020) A 3 A x A (0010,1020) A A
Patient’s Weight A (0010,1030) A 2 A x A (0010,1030) A A
Patient’s Address A (0010,1040) A 3 A x A (0010,1040) A A
0.0

July 2013
Key Type A
Military Rank A (0010,1080) A 3 A x A (0010,1080) A A
Branch of Service A (0010,1081) A 3 A - A (0010,1081) A A
Country of Residence A (0010,2150) A 3 A - A (0010,2150) A A
Region of Residence A (0010,2152) A 3 A - A (0010,2152) A A
Patient’s Telephone (0010,2154) A 3 A - A (0010,2154) A A
Numbers A
Ethnic Group A (0010,2160) A 3 A x A (0010,2160) A A
Occupation A (0010,2180) A 3 A - A (0010,2180) A A
Patient’s Religious (0010,21F0) A 3 A - A (0010,21F0) A A
Preference A
Patient Comments A (0010,4000) A 3 A x A (0010,4000) A A
Patient Data Confidentality (0040,3001) A 2 A x A (0040,3001) A A
Constraint Description A A
Patient Medical A A
Medical Alerts A (0010,2000) A 2 A x A (0010,2000) A A
Contrast Allergies A (0010,2110) A 2 A x A (0010,2110) A A
Pregnancy Status A (0010,21C0) A 2 A x A (0010,21C0) A A
Smoking Status A (0010,21A0) A 3 A x A (0010,21A0) A A
Last Menstrual Date A (0010,21D0) A 3 A x A (0010,21D0) A A
Additional Patient History A (0010,21B0) A 3 A x A (0010,21B0) A A
Special Needs A (0038,0050) A 2 A x A (0038,0050) A A
Patient State A (0038,0500) A 2 A x A (0038,0500) A A
Patient Relationship A A
Referenced Study Sequence A (0008,1110) A 3 A - A A A
0.0

Key Type A
UID A
Referenced Visit Sequence A (0008,1125) A 3 A - A A A
UID A
Referenced Patient Alias (0038,0004) A 3 A - A A A
Sequence A
UID A
a. The Specific Character Set distributed via Modality Worklist by the hospital network shall reflect
the global hospital context, e.g. a hospital with german context shall not restrict the worklist en-
tries to ISO_IR 6 but supply a character set adequate to hold all german language text input.
0.0

July 2013
Associated Real-World With "Get Worklist" in the patient based Worklist Query dialog
Activity - Get Worklist A the entered attributes are used to form a worklist request iden-
tifier. With the response data the Patient Registration dialog can
be updated to perform examination in advance. The response
data are additionally placed in the scheduler database. A.0
Proposed Presentation The same Presentation contexts as with "Update Worklist" will
Contexts - Get Worklist A be proposed. A.0
SOP Specific Conformance - Search Key Attributes of the Worklist C-FIND A.0
Get Worklist A
The Somaris/5 DICOM worklist SCU supports "narrow worklist
queries" with all required search keys. A.0
The following table describes the search keys that the SCU sup-
ports for a patient based worklist query, which is defined by the
following search keys A.0
A
Attribute name Tag A Matching Key Query value A
Type A
Scheduled Procedure Step

Scheduled Procedure Step (0040,0100) A R A A
Sequence A
> Scheduled Performing (0040,0006) A R A inserted in UI or

Physician’s Name A zero length A
Requested Procedure
Requested Procedure ID A (0040,1001) A O A inserted in UI or
zero length A
Imaging Service Request

Accession Number A (0008,0050) A O A inserted in UI or
zero length A
Referring Physician’s Name A (0008,0090) A O A inserted in UI or

zero length A
Visit Status
0.0

Attribute name Tag A Matching Key Query value A
Type A
Current Patient Location A (0038,0300) A O A inserted in UI or

zero length A
Patient Identification
Patient’s Name A (0010,0010) A R A inserted in UI or
zero length A
Patient IDa A (0010,0020) A R A inserted in UI or

zero length A
a. Please be aware that although in the UI there are different entries for First Name and Last
Name of a patient these are combined into one query attribute. Querying just for the Last
Name (without wildcard) or not providing a first letter for the First Name may prevent expect-
ed matches.
Return Key Attributes used from the Worklist C-FIND-RSP A.0
Please see table → page A.2–134. A.0
Status Codes of the Worklist C-FIND A.0
The worklist SCU interprets following status codes: A.0
A
Service Status Meaning A Status Codes A Related Fields A
(0000,0900) A
(0000,0902) A
Unable to process A Cxxx A (0000,0901) A
(0000,0902) A
Cancel A Matching terminated due to Cancel FE00 A None A
request A
Success A Matching is complete - No final Identifier 0000 A None A
is supplied A
0.0

July 2013
Service Status Meaning A Status Codes A Related Fields A
(0000,0900) A
Pending A Matches are continuing - Current Match FF00 A Identifier A
is supplied and any Optional Keys were

supported in the same manner as
Required Keys A
Matches are continuing - Warning that FF01 A Identifier A
one or more Optional Keys were not

supported for existence and/or matching
for this identifier A
0.0

Modality Performed Procedure Step

AE Specification A.0
The Modality Performed Procedure Step SCU (Patient Registra-

tion and MPPS UI) provide information about a performed real-
world Procedure to a remote SCP (Information System). A.0
SIEMENS Somaris/5 DICOM implementation provides Standard

Conformance to the following DICOM V3.0 SOP Class as an SCU: A.0

A
Modality Performed 1.2.840.10008.3.1.2.3.3 A
Procedure Step A
0.0

July 2013
General A.0
The creation of a MPPS Instance is done automatically by the

Somaris/5 DICOM application whenever a patient is registered
for image acquisition through the Patient Registration dialog.
Exception: In case of Emergency Patients the MPPS is created
only when the user explicitly sends a corresponding message
from the MPPS user interface. A.0
Further updates on the MPPS data can be done interactively

from the related MPPS user interface. The MPPS "Complete" or
"Discontinued" states can only be set from user interface. A.0
The Siemens DICOM application initiates one association at a

time to create or set MPPS instance. A.0
The Siemens DICOM software does not support asynchronous

communication (multiple outstanding transactions over a sin-
gle association). A.0
The Siemens DICOM software provides the Implementation

Class UID of A.0
❏ “1.3.12.2.1107.5.1.4"
0.0

The Somaris/5 DICOM Application Entity acts as a Service Class

User (SCU) for the A.0
Modality Performed Procedure Step Service Class (to notify a RIS

about status of a procedure while it is performed). A.0
To do so, it will issue a: A.0
❏ N-CREATE DIMSE according to the CREATE Modality Per-

formed Procedure Step SOP Instance operationor a
❏ N-SET DIMSE to update the contents and state of the MPPS
according to the SET Modality Performed Procedure Step
Information operation
Real World Activity A.0
Associated Real-World The associated Real-World activity is to send examination infor-

Activity - Patient Registered A mation to an SCP by using the DICOM Modality Performed Pro-
cedure Step Service. A.0
Proposed Presentation The Siemens DICOM application will propose Presentation Con-
Contexts - Patient texts as shown in the following table: A.0
Registered A
A
Modality 1.2.840.10008.3.1.2.3.3 A Implicit VR Little 1.2.840.10008.1.2 A SCU A None A
Performed Endian A
Procedure Explicit VR Little 1.2.840.10008.1.2.1 A
Step A Endian A
Explicit VR Big 1.2.840.10008.1.2.2 A
Endian A
0.0

July 2013
SOP Specific Conformance Attributes used for the Performed Procedure Step N-CREATE A.0
Statement - Patient
The Siemens DICOM Modality Performed Procedure Step SCU
Registered A
informs the remote SCP when the examination of a scheduled
procedure step will be performed (i.e. the patient is registered).
The N-CREATE message is sent when the examination is started
with successful registration of patient data. The following table
describes the supported attributes for a N-CREATE message. A.0
A
Performed Procedure Step N-CREATE Attributes A
Attribute name Tag A Required Value A
Type A
SOP Common
Specific Character Set A (0008,0005) A 1C A from MWL or created A
Performed Procedure Step Relationship
Scheduled Step Attribute Sequence A (0040,0270) A 1 A A
> Study Instance UID A (0020,000D) A 1 A from MWL or created A
> Referenced Study Sequence A (0008,1110) A 2 A from MWL or zero

length A
>> Referenced SOP Class UID A (0008,1150) A 1C A A
>> Referenced SOP Instance UID A (0008,1155) A 1C A A
> Accession Number A (0008,0050) A 2 A from MWL or user input A
> Placer Order Number / Imaging Service (0040,2016) A 3 A from MWL or zero
Request A length A
> Filler Order Number / Imaging Service (0040,2017) A 3 A from MWL or zero
Request A length A
> Requested Procedure ID A (0040,1001) A 2 A from MWL or user input A
> Requested Procedure Description A (0032,1060) A 2 A from MWL or zero

length A
0.0

Type A
> Scheduled Procedure Step ID A (0040,0009) A 2 A from MWL or zero

length A
> Scheduled Procedure Step Description A (0040,0007) A 2 A from MWL or zero

length A
> Scheduled Protocol Code Sequence A (0040,0008) A 2 A from MWL or zero

length A
>> Code Value A (0008,0100) A 1C A A
>> Coding Scheme Designator A (0008,0102) A 1C A A
>> Code Scheme Version A (0008,0103) A 3 A A
>> Code Meaning A (0008,0104) A 3 A A
Patient’s Name A (0010,0010) A 2 A from MWL or user input A
Patient ID A (0010,0020) A 2 A from MWL or user input

or created A
Patients Birth Date A (0010,0030) A 2 A from MWL or user input A
Patient’s Sex A (0010,0040) A 2 A from MWL or user input A
Referenced Patient Sequence A (0008,1120) A 2 A from MWL or zero

length A
> Referenced SOP Class UID A (0008,1150) A 1C A A
> Referenced SOP Instance UID A (0008,1155) A 1C A A
Performed Procedure Step Information
Performed Procedure Step ID A (0040,0253) A 1 A from SPS ID or created A
Performed Station AE Title A (0040,0241) A 1 A own AE Title A
Performed Station Name A (0040,0242) A 2 A own hostname A
0.0

July 2013
Type A
Performed Location A (0040,0243) A 2 A from SPS Location or

zero length A
Performed Procedure Step Start Date A (0040,0244) A 1 A created A
Performed Procedure Step Start Time A (0040,0245) A 1 A created A
Performed Procedure Step Status A (0040,0252) A 1 A IN PROGRESS A
Performed Procedure Step Description A (0040,0254) A 2 A from SPS Description or

zero length A
Performed Procedure Type Description A (0040,0255) A 2 A zero length A
Procedure Code Sequence A (0008,1032) A 2 A from Requested

Procedure Code or zero
length A
> Code Value A (0008,0100) A 1C A A
> Code Scheme Designator A (0008,0102) A 1C A A
> Code Scheme Version A (0008,0103) A 3 A A
> Code Meaning A (0008,0104) A 3 A A
Performed Procedure Step End Date A (0040,0250) A 2 A zero length A
Performed Procedure Step End Time A (0040,0251) A 2 A zero length A
Image Acquisition Results
Modality A (0008,0060) A 1 A CT A
Study ID A (0020,0010) A 2 A from Requested

Procedure ID or created A
Performed Protocol Code Sequence A (0040,0260) A 2 A from Scheduled

Protocol Code SQ or
zero length A
0.0

Type A
> Code Scheme Version A (0008,0103) A 3 A A
> Code Meaning A (0008,0104) A 3 A A
Performed Series Sequence A (0040,0340) A 2 A A
> Performing Physicians’s Name A (0008,1050) A 2C A from MWL or user input A
> Protocol Name A (0008,1030) A 1C A default value A
> Operator’s Name A (0008,1070) A 2C A user input A
> Series Instance UID A (0020,000E) A 1C A created A
> Series Description A (0008,103E) A 2C A zero length A
> Retrieve AE Title A (0008,0054) A 2C A zero length A
> Referenced Image Sequence A (0008,1140) A 2C A zero length A
> Referenced Standalone SOP Instance (0040,0220) A 2C A zero length A
Sequence A
0.0

July 2013
Status Codes of the Performed Procedure Step N-CREATE A.0
The Performed Procedure Step SCU interprets the following sta-

tus values: A.0
A
N-SET Response Status A
Service Status Meaning A Status Codes A
(0000,0900) A
Failure A Processing Failure A 0110 A
No such attribute A 0105 A
Invalid attribute value A 0106 A
Duplicate SOP Instance A 0111 A
No such SOP Instance A 0112 A
No such SOP class A 0118 A
Class instance conflict A 0119 A
Missing attribute A 0120 A
Missing attribute value A 0121 A
Resource limitation A 0213 A
Success A Successful Operation A 0000 A
Associated Real-World The associated Real-World activity is to send examination infor-

Activity - Update A mation to an SCP by using the DICOM Modality Performed Pro-
cedure Step Service either implicitly (examination) or explicitly
(MPPS UI). A.0
Proposed Presentation The same Presentation Contexts as in → page A.2–147 will be

Contexts - Update A proposed. A.0
0.0

SOP Specific Conformance Attributes used for the Performed Procedure Step N-SET A.0
Statement - Update A
The Somaris/5 DICOM performed procedure step SCU informs
the remote SCP about the performed examination and its status.
The N-Set message is sent once for each reconstruction of acqui-
sition data with status "IN_PROGRESS". The N-SET message is
sent on user input with status "COMPLETED" or "DISCONTIN-
UED", respectively. This is intended to be used when the exami-
nation is finished with status "COMPLETED" or when the exami-
nation could not be completed with status "DISCONTINUED"
(already sent automatically when examination is ended via End
Exam and no acquisition was done). The following table
describes the supported attributes for a N-SET message. A.0
A
Performed Procedure Step N-SET Attributes A
Type A
Performed Procedure Step Information
Performed Procedure Step Status A (0040,0252) A 3 A IN_PROGRESS or

COMPLETED or
DISCONTINUED
(see above) A
Performed Procedure Step Description A (0040,0254) A 3 A from SPS Description or

user input A
Performed Procedure Type Description A (0040,0255) A 3 A zero length A
Procedure Code Sequence A (0008,1032) A 3 A from Requested

Procedure Code or
empty on user change
(see IHE Technical
Framework Y3,
App. C Note 6) A
0.0

July 2013
Type A
> Code Scheme Version A (0008,0103) A 1C A A
> Code Meaning A (0008,0104) A 1C A A
Performed Procedure Step End Date A (0040,0250) A 3 A created or zero length A
Performed Procedure Step End Time A (0040,0251) A 3 A created or zero length A
Image Acquisition Results
Performed Protocol Code Sequence A (0040,0260) A 3 A from Scheduled

Protocol Code SQ or
user input A
> Code Scheme Version A (0008,0103) A 1C A A
> Code Meaning A (0008,0104) A 1C A A
Performed Series Sequence A (0040,0340) A 1 A A
> Performing Physicians’s Name A (0008,1050) A 2C A from MWL or user input

[empty if Study Split is
used] A
> Protocol Name A (0018,1030) A 1C A name of Scan Protocol

(Siemens standard or
user defined)
[dummy if Study Split is
used] A
> Operator’s Name A (0008,1070) A 2C A user input

used] A
0.0

Type A
> Series Instance UID A (0020,000E) A 1C A created

[dummy if Study Split is
used] A
> Series Description A (0008,103E) A 2C A range name

with generated
reconstruction
information
or user input
used] A
> Retrieve AE Title A (0008,0054) A 2C A from Storage

Commitment RSP
or zero length A
> Referenced Image Sequence A (0008,1140) A 2C A created

used] A
>> Referenced SOP Class UID A (0008,1150) A 1C A A
>> Referenced SOP Instance UID A (0008,1155) A 1C A A
> Referenced Standalone SOP Instance (0040,0220) A 2C A zero length A
Sequence A
Radiation Dose
Total Number of Exposures A (0040,0301) A 3 A created

(number of scans) A
Distance Source to Detector (SID) A (0018,1110) A 3 A created A
Distance Source to Entrance A (0040,0306) A 3 A created A
Comments on Radiation Dose A (0040,0310) A 3 A created A
(one line per scan)a A
0.0

July 2013
Type A
Billing and Material Management Code
Film Consumption Sequence A (0040,0321) A 3 A created

or zero length A
> Number of Films A (2100,0170) A 3 A A
> Medium Type A (2000,0030) A 3 A A
> Film Size ID A (2010,0050) A 3 A A
Billing Supplies and Devices Sequence A (0040,0324) A 3 A user input in

Examination Card
(example values below)
or MPPS window A
> Billing Item Sequence A (0040,0296) A 3 A A
>> Code Value A (0008,0100) A 1C A e.g. contrast media

code A
>> Code Scheme Designator A (0008,0102) A 1C A e.g. contrast media

catalog A
>> Code Meaning A (0008,0104) A 1C A e.g. contrast media

name A
> Quantity Sequence A (0040,0293) A 1C A A
>> Quantity A (0040,0294) A 3 A e.g. volume of

contrast media A
>> Measuring Units Sequence A (0040,0295) A 3 A A
>>> Code Value A (0008,0100) A 1C A e.g. cm3 A
>>> Code Scheme Designator A (0008,0102) A 1C A e.g. UCUM A
>>> Code Scheme Version A (0008,0103) A 1C A e.g. 1.4 A
0.0

Type A
>>> Code Meaning A (0008,0104) A 1C A e.g. cm3 A
a. The following format is used:

RangeName: kV=xxx mAs=xxx CTDIvol=xxx DLP=xxx
CTDIvol and DLP is not provided for Topogram scans.
0.0

July 2013
Status Codes of the Performed Procedure Step N-SET A.0
The Performed Procedure Step SCU interprets the following sta-

tus values: A.0
A
N-SET Response Status A
Service Status Meaning A Status Codes A
(0000,0900) A
Failure A Processing Failure: Performed Procedure 0110 A
Step Object may no longer be updated A
No such attribute A 0105 A
Invalid attribute value A 0106 A
No such SOP Instance A 0112 A
Invalid object instance A 0117 A
No such SOP class A 0118 A
Class instance conflict A 0119 A
Missing attribute value A 0121 A
Resource limitation A 0213 A
Success A MPPS instance set A 0000 A
A.0
0.0

CHAPTER
A.1 Communication Profiles A.1
Supported Communication Stacks A.1
The Somaris/5 DICOM application provides DICOM V3.0 TCP/IP

Network Communication Support as defined in Part 8 of the
DICOM Standard. A.1
The product target operating system is Windows XP. A.1
OSI Stack A.1
Not supported. A.1
TCP/IP Stack A.1
The Somaris/5 DICOM application uses the TCP/IP stack from the
Windows XP system. It uses the MergeCOM-3 subroutine library
from Merge Technologies Inc. that is based on a Berkeley socket
interface. A.1
API A.1
The Somaris/5 DICOM application uses the MergeCOM library

that is based on a TCP/IP socket interface. A.1
Physical Media Support A.1
The Somaris/5 DICOM application is indifferent to the physical

medium over which TCP/IP executes. It inherits it from the target
operating system upon which it executes. A.1
Point-to-Point Stack A.1
Not supported. A.1
A.1
A.1
0.0

July 2013
Network – Communication Profiles DICOM Conformance Statement
0.0

CHAPTER Extensions/Specializations/
A.4 Privatizations A.1
Standard Extensions A.1
Standard Extensions of all SOP Classes A.1
The following tables list the data dictionary of all DICOM IOD
attributes where the DICOM standard definitions are extended:
A.1
All SOP classes may contain additional type 3 attributes which

DICOM standard defines in a different DICOM IOD or DICOM SOP
class (attributes from Normalized SOP classes). A.1
This is the case for example for A.1
❏ Rescale Slope (0028,1053)

❏ Rescale Intercept (0028,1052)
which are also used in the MR IOD. A.1
0.0

July 2013
Network – Extensions/Specializations/Privatizations DICOM Conf. Statement
Image Type A.1
The Image Type (0008,0008) attribute identifies important

image identification characteristics. These characteristics are:
A.1
1. Pixel Data Characteristics:

❏ Is the image an ORIGINAL Image; an image whose pixel
values are based on original or source data, or
❏ is the image a DERIVED Image; an image whose pixel values
have been derived in some manner from the pixel value of
one or more other images.
2. Patient Examination Characteristics:
❏ Is the image a PRIMARY Image; an image created as a direct
result of the Patient examination, or
❏ is the image a SECONDARY Image; an image created after the
initial Patient examination.
3. Modality Specific Characteristics (SOP Specific Characteris-
tics).
4. Implementation specific identifiers; other implementation
specific identifiers shall be documented in an implementa-
tion's conformance claim.
The Image Type attribute is multi-valued and shall be provided
in the following manner: A.1
❏ Value 1 shall identify the Pixel Data Characteristics;

Enumerated Values for the Pixel Data Characteristics are:
❏ ORIGINAL = identifies an Original Image
❏ DERIVED = identifies a Derived Image
❏ Value 2 shall identify the Patient Examination Characteristics;
Enumerated Values for the Patient Examination
Characteristics are:
❏ PRIMARY = identifies a Primary Image
❏ SECONDARY = identifies a Secondary Image
❏ Value 3 shall identify any Image IOD specific specialization,
the following terms are defined in addition to the DICOM
standard definitions:
❏ OTHER = converted non-Axial and non-Localizer CT
images; images of no special type (new syntax)
❏ MPR = 3D MPR images (MR)
0.0

DICOM Conf. Statement Network – Extensions/Specializations/Privatizations
❏ PROJECTION IMAGE = 3D MIP and SSD images (MR)

❏ UNDEFINED = images of no special type (old syntax)
❏ Value 4 is implementation specific. The following terms are
defined:
original syngo generated data set types:
CSA 3D EDITOR = object created by 3D Editor
CSA 3D FLY PATH = object created by Fly Through Path
CSA 3D FLY VRT = object created by Fly Through Volume
Rendering Technique
CSA 3D FUSION = object created by Fusion
CSA AVERAGE = image was created by Average
CSA BLACK IMAGE = SC Image with black pixels, only
graphics information is of interest
CSA BOOKMARK = InSpace generated SC image contain-
ing bookmark information
CSA RESAMPLED = derived image created by zooming or
panning original image
CSA REPORT = syngo Reporting (documentation of diagnosis)
CSA RESULT = syngo Reporting (post processing results)
CSA MIP = image created by Maximum Intensity Projec-
tion
CSA MIP THIN = image created by Maximum Intensity
Projection
CSA MIP THIN CV = image created by Maximum Intensity
Projection (curved cut)
CSA MPR = image created by Multi Planar Reconstruction
CSA MPR CV = image created by Multi Planar Reconstruc-
tion (curved cut)
CSA MPR THICK = image created by Multi Planar Recon-
struction
CSA MPR THICK CV = image created by Multi Planar Re-
construction (curved cut)
CSA MPR THIN = image created by Multi Planar Reconstruction
CSA PSSD = SC image as Perspective Shaded Surface Dis-
play
CSA SSD = SC Image as Shaded Surface Display
CSA SUBTRACT = image was created by Subtraction
CSA VRT = SC Image created by Volume Rendering Tech-
nique
ECAT ACF = CTI PET Attenuation Correction
0.0

July 2013
ECAT NORMAL = CTI PET Normalization

ECAT 3D SINO = CTI PET 3D Sinogram Short
ECAT 3D SINO FLT = CTI PET 3D Sinogram Float
❏ additional image types generated by Somaris/5 or

Somaris/5 based SOMATOM products:
CT_SOM5 AVE = Average Image
CT_SOM5 ICD = Interventional Cine Display Image
CT_SOM5 MON = Monitoring Image
CT_SOM5 MUL = Multiscan Image
CT_SOM5 PAR = Parameter Image
CT_SOM5 PROT = Protocol Image
CT_SOM5 ROT = ROT Image
CT_SOM5 RTD = Real Time Display Image
CT_SOM5 SEQ = Sequence Image
CT_SOM5 SPI = Spiral Image
CT_SOM5 SPO = Spiral Oblique Image
CT_SOM5 STA = Static Image
CT_SOM5 SUB = Subtracted Image
CT_SOM5 TOP = Topogram
CT_SOM5 DPAN = Dental Panorama Rebuilt Tomogram
CT_SOM5 DPAR = Dental Paraxial Rebuilt Tomogram
CT_SOM5 DFLM = Dental Filming Image
CT_SOM5 DYB = Dynamic Evaluation Averaged Baseline
Image
CT_SOM5 DYF = Dynamic Evaluation Fused Multislice
Image
CT_SOM5 PEVI = Pulmo Evaluation Image
CT_SOM5 OEVA = Osteo Evaluated Tomogram
CT_SOM5 MIP = Maximum Intensity Projection image
created by a CT application
CT_SOM5 MPR = Multi Planar Reconstruction image
created by a CT application
CT_SOM5 REP = Lung Care Report Image
❏ converted images
CT_SOM4 NONE = converted SOMARIS image
CT_SOM4 CONV = converted SOMARIS Convolution
Kernel file
CT_SOM4 DART = converted SOMARIS Dental Artificial image
0.0

CT_SOM4 DEVA = converted SOMARIS Dental Evaluation

image
CT_SOM4 DGRA = converted SOMARIS Dental Graphics
image
CT_SOM4 DMEA = converted SOMARIS Dynamic
Measurement image
CT_SOM4 DPAN = converted SOMARIS Dental Panorama
image
CT_SOM4 DPAR = converted SOMARIS Dental Paraxial
image
CT_SOM4 EBT = converted SOMARIS Evolution image
CT_SOM4 HIS = converted SOMARIS Histogram Graphics
image
CT_SOM4 HISC = converted SOMARIS Histogram Graphics
image
CT_SOM4 MUL = converted SOMARIS Multiscan image
CT_SOM4 OEVA = converted SOMARIS Osteo Evaluation
image
CT_SOM4 OTOM = converted SOMARIS Osteo Tomogram
image
CT_SOM4 OTOP = converted SOMARIS Osteo Topogram
image
CT_SOM4 PLOT = converted SOMARIS Plot image
CT_SOM4 QUAL = converted SOMARIS Quality image
CT_SOM4 R2D = converted SOMARIS 2D Rebuild image
CT_SOM4 R3D = converted SOMARIS 3D Rebuild image
CT_SOM4 R3DE = converted SOMARIS 3D Rebuild image
CT_SOM4 RMAX = converted SOMARIS Maximum
Intensity Projection image
CT_SOM4 RMIN = converted SOMARIS Minimum Intensity
Projection image
CT_SOM4 ROT = converted SOMARIS Rotation Mode
image
CT_SOM4 RRAD = converted SOMARIS Radiographic
Projection image
CT_SOM4 RVIT = converted SOMARIS Vessel Image Tool
image
CT_SOM4 RVRT = converted SOMARIS Volumetric
Rendering image
0.0

July 2013
CT_SOM4 SAVE = converted SOMARIS Evolution Screen

Save image
CT_SOM4 SCAN = converted SOMARIS Standard Mode image
CT_SOM4 SEQ = converted SOMARIS Sequence Mode image
CT_SOM4 SER = converted SOMARIS Serial Mode image
CT_SOM4 SIN = converted SOMARIS Sinogram image
CT_SOM4 SINC = converted SOMARIS Sinogram image
CT_SOM4 SPI = converted SOMARIS Spiral Mode image
CT_SOM4 STA = converted SOMARIS Static Mode image
CT_SOM4 TAB = converted SOMARIS Correction Table image
CT_SOM4 TOP = converted SOMARIS Topogram image
CT_SOM4 GTOP = converted SOMARIS Topo Graphics image
CT_SOM4 PEVG = converted SOMARIS Pulmo Evaluation
image
CT_SOM4 PEVI = converted SOMARIS Pulmo Evaluation
image
CT_SOM4 PUL = converted SOMARIS Pulmo Respiration
curve
CT_SOM4 PROT = converted SOMARIS Protocol image
CT_SOM4 TEXT = converted SOMARIS Text image
CT_SOM4 ICD = converted SOMARIS Interventional Cine
image
SHS DENT = converted MagicView Dental Tomogram
image
SHS DPAN = converted MagicView Dental Panorama
image
SHS DPAR = converted MagicView Dental Paraxial image
SHS 3D_CURVED = converted MagicView image
SHS 3D_MIP = converted MagicView Maximum Intensity
Projection image
SHS 3D_MPR = converted MagicView Multi Planar
Reconstruction image
SHS 3D_SSD = converted MagicView Shaded Surface
Display image
SHS 3D_VRT = converted MagicView Volumetric
Rendering image
0.0

• Value 5 is specific for the Somaris/5 or Somaris/5 based

SOMATOM products. In special cases (3D postprocessing)
values mentioned for a lower index may appear for value
5 or higher. This will refer to 3D postprocessing base im-
age types.
The following terms are defined:
ADD = Additional Scan
ALP = Arterial Liver Perfusion
CTL = Control Scan
HPI = Hepatic Perfusion Index
FINISHED = Lung Care Report Image (finished)
IN_WORK = Lung Care Report Image (not finished)
MRTD = Multiscan Real Time Display Image
OTOM = Osteo Scanned Tomogram
OTOP = Osteo Scanned Topogram
PBF = Perfusion Blood Flow Image
PBV = Perfusion Blood Volume Image
PKET = Peak Enhancement Parameter Image
PMON = Premonitoring Scan
PVP = Portal Venous Liver Perfusion
RT3D CONFIG = InSpace Configuration Image
STD = Standard image of corresponding Type 4
TTP = Time to Peak Parameter Image
TTS = Time to Start Parameter Image
0.0

July 2013
Body Part Examined A.1
The Body Part Examined (0018,0015) attribute provides a tex-

tual description of the part of the body examined. The Somaris/5
based SOMATOM products extend the Defined Terms: A.1
❏ SPINE = Summary term used instead of the Defined Terms

CSPINE, TSPINE, LSPINE, and SSPINE
❏ SPECIAL = Image was acquired with acquisition modes that
are not mapped to a certain part of the body
❏ SERVICE = Image was acquired for maintenance purpose
❏ UNKNOWN = No information about the body part available
See → page A.4–21, Structured Reports created by Somaris/5 for
a mapping of the organ characteristics used for examination to
the Body Part Examined terms. A.1
In addition, the user interface permits the definition of new

terms by the user. So in fact any syntactically correct value may
be present as a value of this attribute. It is recommended,
though, to use the DICOM defined terms when appropriate. A.1
0.0

RGB color images A.1
The Somaris/5 DICOM application extends the CT Image IOD by

the use of RGB color image description with the unsigned inte-
ger 24 bit color image plane pixel format: A.1

❏ photometric interpretation (attribute 0028,0004) = “RGB”
❏ planar configuration (attribute 0028,0006) = 0
This format is used for Functional Imaging, i.e. images that
meaningfully use all common CT Image attributes - however the
pixel values do not represent a scaled Hounsfield value but a dif-
ferent value (depending on the type of image). Thus window
related attributes must not be used to interpret the pixel values
as scaled HU. The values used by Somaris/5 are: A.1
❏ window center (attribute 0028, 1050) = 128

❏ window width (attribute 0028,1051) = 256
❏ rescale intercept (attribute 0028, 1050) = 0
❏ rescale slope (attribute 0028,1051) = 1
0.0

July 2013
The following types of images may use this format: A.1
A
Somaris/5 Image Type (0008,0008) for objects created by Somaris/5 A
Image Type IOD A 0008,0008 A 0008,0008 A 0008,0008 A 0008,0008 A 0008,0008 A Somaris/5

Description A Value 1 A Value 2 A Value 3 A Value 4 A Value 5 A Image
Text A
Averaged CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A none A AVE A
Image A AVE A
Parameter CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PKBV A PAR A
Image (Patlak PAR A
Blood Volume) A
Parameter CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PKET A PAR A
Image A PAR A
(Peak
enhancement) A
Parameter CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PBF A PAR A
Image PAR A
(Perfusion
Blood Flow) A
Parameter CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PBV A PAR A
Image PAR A
(Perfusion
Blood Volume) A
Parameter CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PMB A PAR A
Image PAR A
(Permeability) A
Parameter CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A TTP A PAR A
Image (Time to PAR A
Peak) A
Parameter CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A TTS A PAR A
Image (Time to PAR A
Start) A
0.0


Text A
Parameter CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PKER A PAR A
Image (Patlak PAR A
Residual) A
Parameter CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PKR2 A PAR A
Image (Patlak PAR A
RSquare) A
Parameter CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A ALP A PAR A
Image (Arterial PAR A
LiverPerfusion) A
Parameter CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PVP A PAR A
Image (Portal PAR A
Venous Liver
Perfusion) A
Parameter CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A HPI A PAR A
Image (Hepatic PAR A
Perfusion
Index) A
LungCARE CT A DERIVED A SECONDARY A OTHER A CSA MIP LC VALID MIP A
send-to- THIN A WINDOW A
Filming images A
LungCARE CT A DERIVED A SECONDARY A OTHER A CSA MPR LC VALID MPR A
send-to- THICK A WINDOW A
Filming
images A
LungCARE CT A DERIVED A SECONDARY A OTHER A CSA VRT LC VALID VRT A
send-to- THIN A WINDOW A
Filming
images A
0.0

July 2013

Text A
LungCARE CT A DERIVED A SECONDARY A OTHER A CSA PRVT A LC VALID PVRT A
send-to- WINDOW A
Filming
images A
LungCARE CT A DERIVED A SECONDARY A OTHER A CSA MPR A LC VALID MPR A
send-to- WINDOW A
Filming
images A
SC Derived SC A not set A not set A not set A not set A not set A not set A
Image (RGB)
from VSim (see
→ page A.4–
35) A
0.0

Specializations A.0
Images created by Somaris/5 A.0
The following table lists the Somaris/5 image types and the cor-
responding combinations of the Image Type Attribute values: A.0
A
Image Type IOD 0008,0008A A 0008,0008 A 0008,0008 0008,0008 0008,0008 Somaris/5
A A A
Description Value 1 A Value 2 A Value 3 AValue 4 Value 5

A Image A
[known creating Text or

applications] A Lists A
Averaged Image A CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A none A AVE A
[Average, AVE A
DynEva,
Perfusion] A
Interventional CT A ORIGINAL A PRIMARY A AXIAL A CT_SOM5 A none A ICD A
Cine Display ICD A
Image A
Monitoring CT A ORIGINAL A PRIMARY A AXIAL A CT_SOM5 A none A MON A
Image A MON A
Premonitoring CT A ORIGINAL A PRIMARY A AXIAL A CT_SOM5 A PMON A MON A
Image A MON A
Multiscan Image A CT A ORIGINAL A PRIMARY A AXIAL A CT_SOM5 A none A MUL A
MUL A
Parameter Image CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A ALP A PAR A
(Arterial Liver PAR A
Perfusion) A
[BodyPerfusion] A
Parameter Image CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A HPI A PAR A
(Hepatic PAR A
Perfusion Index) A
[BodyPerfusion] A
Parameter Image CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PVP A PAR A
(Portal Venous PAR A
Liver Perfusion) A
[BodyPerfusion] A
0.0

July 2013
Image Type IOD 0008,0008

A A 0008,0008 A 0008,0008 0008,0008 0008,0008 Somaris/5
A A A

A Image
A

Protocol Image, SC A DERIVED A SECONDARY A OTHER A none A none A AC A
Time Density
Curve Image A
[BodyPerfusion]a A
Parameter Image CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PKBV A PAR A
(Patlak Blood PAR A
Volume) A
[Perfusion] A
Parameter Image CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PKER A PAR A
(Patlak Residual) A PAR A
[Perfusion] A
Parameter Image CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PKR2 A PAR A
(Patlak RSquare) A PAR A
[Perfusion] A
Parameter Image A CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PKET A PAR A
(Peak PAR A
enhancement)
[DynEva,
Perfusion] A
Parameter Image CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PBF A PAR A
(Perfusion Blood PAR A
Flow) A
[Perfusion] A
Parameter Image CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PBV A PAR A
(Perfusion Blood PAR A
Volume) A
[Perfusion] A
Parameter Image CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A PMB A PAR A
(Permeability) A PAR A
[Perfusion] A
0.0


A A 0008,0008 A 0008,0008 0008,0008 0008,0008 Somaris/5
A A A

A Image A

Parameter Image CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A TTP A PAR A
(Time to Peak) A PAR A
[DynEva,
Perfusion] A
Parameter Image CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A TTS A PAR A
(Time to Start) A PAR A
[Perfusion] A
Protocol Image A SC A DERIVED A SECONDARY A OTHER A CT_SOM5 A none A PROT A
PROT A (List
only) A
Report Image A SC A DERIVED A SECONDARY A OTHER A CT_SOM5 A IN_WORK A REP A
(not finished) A REP A
Report Image A SC A DERIVED A SECONDARY A OTHER A CT_SOM5 A FINISHED A REP A
(finished) A REP A
ROT Image A CT A ORIGINAL A PRIMARY A AXIAL A CT_SOM5 A none A ROT A
ROT A
Real Time Display CT A ORIGINAL A PRIMARY A AXIAL A CT_SOM5 A none A RTD A
Image A RTD A
Real Time Display CT A ORIGINAL A PRIMARY A AXIAL A CT_SOM5 A STD A RTD A
Image (Cardio) A RTD A
Multiscan Real CT A ORIGINAL A PRIMARY A AXIAL A CT_SOM5 A MRTD A RTD A
Time Display RTD A
Image A
Sequence Image A CT A ORIGINAL A PRIMARY / AXIAL A CT_SOM5 A none A SEQ A
SECONDARY A SEQ A
Additional Scan CT A ORIGINAL A PRIMARY / AXIAL A CT_SOM5 A ADD A SEQ A
Image A SECONDARY A SEQ A
Control Scan CT A ORIGINAL A PRIMARY / AXIAL A CT_SOM5 A CTL A SEQ A
Image A SECONDARY A SEQ A
0.0

July 2013

A A 0008,0008 A 0008,0008 0008,0008 0008,0008 Somaris/5
A A A
Description Value 1 A Value 2 A Value 3 Value 4

A Value 5
A Image A

Spiral Image A CT A ORIGINAL A PRIMARY / AXIAL A CT_SOM5 A none A SPI A
SECONDARY A SPI A
Sprial Image CT A ORIGINAL A PRIMARY / AXIAL A CT_SOM5 A STD A SPI A
(Cardio) A SECONDARY A SPI A
Spiral Oblique CT A DERIVED A PRIMARY / AXIAL A CT_SOM5 A none A SPI A
Image A SECONDARY A SPO A
Static Image A CT A ORIGINAL A PRIMARY A OTHER A CT_SOM5 A none A STA A
STA A
Subtracted CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A none A SUB A
Image A SUB A
Topogram A CT A ORIGINAL A PRIMARY A LOCALIZER A CT_SOM5 A none A TOP A
TOP A
Osteo Scanned CT A ORIGINAL A PRIMARY A AXIAL A CT_SOM5 A OTOM A SEQ A
Tomogram A SEQ A
Osteo Scanned CT A ORIGINAL A PRIMARY A LOCALIZER A CT_SOM5 A OTOP A TOP A
Topogram A TOP A
Osteo Evaluated CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 none A OEVA A
Tomogram A OEVA A
Pulmo Evaluated CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 A none A PEVI A
Tomogram A PEVI A
Calcium Scoring SC A DERIVED A SECONDARY A OTHER A CT_SOM5 A none A TAB A
Table A TAB A
[Calcium
Scoring] A
Dental Filming CT A DERIVED A SECONDARY A OTHER A CT_SOM5 none A DFLM A
Image A DFLM A
Dental Panorama CT A DERIVED A SECONDARY A OTHER A CT_SOM5 none A DPAN A
Rebuild DPAN A
Tomogram A
0.0


A A 0008,0008 A 0008,0008 0008,0008 0008,0008 Somaris/5
A A A

A Image
A

Dental Paraxial CT A DERIVED A SECONDARY A OTHER A CT_SOM5 none A DPAR A
Rebuild DPAR A
Tomogram A
Dental/Volume CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 none A MIP A
Maximum MIP A
Intensity
Projection Image A
[Dental, Volume,
DynEva,
Perfusion] A
Dental Panorama CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 none A MPR A
Reference Image A MPR A
[Dental, Volume] A
Dental Paraxial CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 none A MPR A
Reference Image A MPR A
Dental Reference CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 none A MPR A
Image A MPR A
Dynamic CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 none A DYB A
Evaluation DYB A
Averaged
Baseline A
Dynamic CT A DERIVED A SECONDARY A AXIAL A CT_SOM5 none A DYF A
Evaluation Fused DYF A
Multislice A
Volume CT A DERIVED A SECONDARY A OTHER A CT_SOM5 none A MPR A
reformatted MPR A
images (sagittal
and coronal) A
0.0

July 2013

A A 0008,0008 A 0008,0008 0008,0008 0008,0008 Somaris/5
A A A

A Value 5
A Image A

Various result CT A DERIVED A SECONDARY A AXIAL A CSA MPR A none A MPR A
images
[CalciumScoring,
Colon] A
Various result CT A DERIVED A SECONDARY A AXIAL A CSA MPR none A MPR A
images A THICK A
Various result CT A DERIVED A SECONDARY A AXIAL A CSA MIP A none A MIP A
images A
Various result CT A DERIVED A SECONDARY A AXIAL A CSA MIP none A MIP A
images THIN A
[CalciumScoring
] A
Various result SC A DERIVED A SECONDARY A OTHER A CSA PSSD A none A PSSD A
images [Colon] A
Various result CT A DERIVED A SECONDARY A AXIAL A CSA VRT A none A VRT A
images A
Various result SC A DERIVED A SECONDARY A OTHER A CSA VRT A none A VRT A
images [Colon] A
InSpace SC A DERIVED A SECONDARY A OTHER A CSA RT3D BOOK A
bookmark BOOKMAR CONFIG A
[InSpace] A K A
InSpace SC A DERIVED A SECONDARY A OTHER A CSA none A 3DPR A
bookmark 3DPROJEC
[InSpace] A TION A
LungCARE save SC A DERIVED A SECONDARY A OTHER A MIP A LC VALID MIP A
images WINDOW A
[LungCARE] A
LungCARE save SC A DERIVED A SECONDARY A OTHER A MRP A LC VALID MRP A
images WINDOW A
[LungCARE] A
0.0


A A 0008,0008 A 0008,0008 0008,0008 0008,0008 Somaris/5
A A A
Description Value 1 A Value 2 A Value 3 A Value 4 Value 5

A Image A

LungCARE save SC A DERIVED A SECONDARY A OTHER A VRT A LC VALID VRT A
images WINDOW A
[LungCARE] A
LungCARE save SC A DERIVED A SECONDARY A OTHER A PVRT A LC VALID PVRT A
images WINDOW A
[LungCARE] A
LungCARE save CT A DERIVED A SECONDARY A OTHER A MPR A LC VALID MPR A
images WINDOW A
[LungCARE] A
LungCARE save CT A DERIVED A SECONDARY A OTHER A CT_SOM5 LC VALID SPI A
images SPI A WINDOW A
[LungCARE] A
LungCARE save SC A DERIVED A SECONDARY A OTHER A MIP A LC VALID none A
report images WINDOW A
[LungCARE] A
LungCARE save SC A DERIVED A SECONDARY A OTHER A MRP A LC VALID none A
[LungCARE] A
LungCARE save SC A DERIVED A SECONDARY A OTHER A VRT A LC VALID none A
[LungCARE] A
LungCARE save SC A DERIVED A SECONDARY A OTHER A PVRT A LC VALID none A
[LungCARE] A
Various Graphics A SC A DERIVED A SECONDARY A OTHER A CSA BLACK none A none A
[DynEva, Osteo, IMAGE A
Pulmo, Volume,
Perfusion, Argus,
VesselView] A
0.0

July 2013

A A 0008,0008 A 0008,0008 0008,0008 0008,0008 Somaris/5
A A A

A Value 5
A Image A

SC Derived Image SC A DERIVED A SECONDARY A from CSAMPR or none A none A
(Monochrome) Original A CSAMIP or

from VSim (see → CSADRR A
page A.4–35) A
a. More detailed attribute information will be provided in a future version.
Note
Some applications will create Structured Reports. However,
when running in specific (service configured) settings
outside of the system they will appear as a SC image,
labelled as Type 3 "OTHER" and Type 4 "CSA REPORT". This
private extension is not published in detail here because the
intended use is real DICOM SR. A
For Protocol Image, some additional information about

DOSE INFO is added into Application Header
Sequence(0029,xx40), detailed info about this Sequence
see “Somaris/5 Attribute Interpretation“ in page 209. A
0.0

Structured Reports created by Somaris/5 A.0
The following table lists the Somaris/5 image types and the cor-
responding combinations of the Image Type Attribute value. A.0
A.0
Image Type IOD A 0008,0008 0008,0008 0008,0008

A A A 0008,000 0008,0008 Somaris/5
A
Description A Value 1 Value 2

A Value 3
A A 8 AValue 5 Image
A
[known Value 4 A Text A
creating
applications] A
LungCARE SR SR A ORIGINAL A PRIMARY A OTHERS A CSA none A none A
reports A REPORT A
[LungCARE,
Calcium
Scoring,
Circulation] A
CT Dose SR A SR A ORIGINAL A PRIMARY A OTHER A CSA none A none A
REPORT A
LungCARE, Calcium Scoring and Circulation create Comprehen-

sive Structured Reports. A.0
The following is valid for Calcium Scoring created Structured

Reports: A.0
CaScoring creates structured reports generally following the

templates defined in DICOM supplement 97 “CT/MR Cardiovas-
cular Analysis Report” (Version: 0.11; Working Draft). Some
changes of these templates that could not be considered may
occur until document is released as final version. A.0
The following is valid for Circulation created Structured

Reports: A.0
Circulation creates structured reports generally following the

DICOM template TID3900. A.0
A.0
Somaris system create CT Dose Structured Reports as a default

configuration for every patient when he/she finish measure-
ment.(user can disable this function.) A.0
0.0

July 2013
CT Dose Report generally follows the templates defined in

DICOM Standard 2008 “CT Radiation Dose”. A.0
The following is valid for CT Dose Structured Reports: A.0
CT Dose SR follows the DICOM template TID10011.

A.0
0.0

Somaris/5 Attribute Interpretation A.0
For an overview of selected attribute filling for different Image

Types please refer to the Annex. A.0
The table below explains how common attributes of created

and uncompressed ORIGINAL and AXIAL images are set by
Somaris/5 image reconstruction. This table does not intend to
be a substitute for DICOM 3.0 attribute definitions. However, in
addition to these it will provide an impression of which
attributes are in common use - and how they are related to
Somaris/5 examination: A.0
A.0
Tag Name Explanation

0002,0012 A Implementation Class Value: 1.3.12.2.1107.5.1.4 A
UID A
0002,0013 A Implementation Value: “SIEMENS_S5VB42A’ A
Version Name A
0008,0005 A Specific Character Set A A
0008,0008 A Image Type A see → page A.4–13 A
0008,0016 A SOP Class UID A Value: 1.2.840.10008.5.1.4.1.1.2 A
0008,0018 A SOP Instance UID A created A
0008,0020 A Study Date A For existing studies their date and time entries are
copied into the corresponding entries in a new image's
0008,0030 A Study Time A
header. A
If a new study is created the date and time entries from

the first series of this new study will be used. A
0008,0021 A Series Date A For existing series their date and time entries are copied
into the corresponding entries in a new image's header. A
0008,0031 A Series Time A
If a new series is created the current real-world date and
time will be used. A
0.0

July 2013

0008,0022 A Acquisition Date A Acquisition Date and Time is defined as the real-world
beginning of the accumulation of data which contribute
0008,0032 A Acquisition Time A
to a particular image. Due to the multi-slice technology
several images may have the same Acquisition Date and
Time. A
0008,0023 A Image (Content) Date For all images which result from a reconstruction of
A
acquired data, the time stamp is the same as Acquisition

0008,0033 A Image (Content) Time A
Date and Time. This is true for images that were
reconstructed immediately after data acquisition as well
as for images that were reconstructed at any time later. A
For all other images created by any other means the

time stamp is derived from a point in time during the
creation process of these images. A
0008,0050 A Accession Number A Input entered from MWL or during patient registration.
May be null-length. A
NOTE: When Study Split is used, the value

corresponding to the Requested Procedure Description
selected in Exam UI will be sent A
0008,0060 A Modality A Value: CT A
0008,0070 A Manufacturer A Value: SIEMENS A
0008,0080 A Institution Name A Hospital name read from configuration data A
or user input entered during patient registration or

examination setup A
0008,0081 A Institution Address A Hospital address read from configuration data. A
Default format is 4 lines containing Street, City, District

and Country. A
0008,0090 A Referring Physician's Input from MWL or entered during patient registration
Name A or examination setup. May be null-length. A
0008,1010 A Station Name A Name of the computer the examination is controlled

with A
0.0


0008,1030 A Study Description A Is derived from information entered during patient
registration or examination setup. Concatenated from
Body Region and selected Scan Protocol name,
separated by a "^" A
NOTE: When Study Split is used, the Requested

Procedure Description selected in Exam UI will be sent A
0008,1050 A Performing Input entered from MWL or during patient registration. A
Physician’s Name A
0008,1070 A Operator’s Name A According to user input A
0008,1080 A Admitting Diagnoses Input entered from MWL or during patient registration. A
Description A
0008,103E A Series Description A According to user input (system proposes <Range

Name> <Slice Thickness> <Kernel>) A
0008,1090 A Manufacturer's Model The Siemens product name A
Name A
0008,1140 A Referenced Image A
Sequence A
>0008,1150 A Referenced SOP Class SOP Class UID of Topogram used for planning A
UID A
>0008,1155 A Referenced SOP SOP Instance UID of Topogram used for planning A
Instance UID A
0008,2112 A Source Image A
Sequence A
>0008,1150 A Referenced SOP Class SOP Class UID of Rawdata used for reconstruction A
UID A
>0008,1155 A Referenced SOP SOP Instance UID of Rawdata used for reconstruction A
Instance UID A
0008,2111 A Derivation Lossy Image Compression will be set to 01 for Extended

Description A Field of View because of low image quality. Derivation
Description: "Reconstruction field larger than scan field"
A
0.0

July 2013

0009,00xx A Private Creator A Value: SIEMENS CT VA1 DUMMY A
0010,0010 A Patient's Name A Input from MWL or entered during patient registration
or examination setup. A
0010,0020 A Patient ID A Input from MWL or entered or generated during patient

registration or examination setup. A
0010,0030 A Patient's Birth Date A Input from MWL or entered during patient registration
or examination setup. May be calculated from age. A
0010,0040 A Patient's Sex A Input from MWL or entered during patient registration
or examination setup. A
0010,1010 A Patient's Age A Input from MWL or entered during patient registration
or examination setup. May be calculated from Patient’s
Birth Date A
0018,0010 A Contrast/Bolus Agent A If present: A
The attribute is filled with the value entered in the

contrast card. If nothing was entered the attribute is
filled with the fixed term "APPLIED". A
0.0


0018,0015 A Body Part Examined A The Body Part Examined is derived from the organ
characteristic of the scan or directly entered by the
operator, which overrides this default. A
The organ characteristic parameter is contained in the

scan protocol selected for examination during patient
registration or examination setup and may vary for
different scans within one protocol (use System/Run/List
Scan Protocols column "OrgChar" for a list of values for
specific scan protocols). A
Organ Characteristic Body Part Examined A
Head HEAD
Neck NECK
Shoulder SHOULDER
Thorax CHEST
Abdomen ABDOMEN
Spine SPINE
Pelvis PELVIS
Extremities EXTREMITY
Cardio HEART
Service SERVICE
n. a. UNKNOWN
0018,0050 A Slice Thickness A Resulting slice thickness. Not necessarily equal to
collimated slice. A
0018,0060 A KVP A Voltage selected for scan. A
0018,0090 A Data Collection A
Diameter A
0018,1000 A Device Serial Number A Serial number of the CT system’s gantry. A
0018,1020 A Software Version(s) A Software Version of Somaris/5. Only one value is used. A
0018,1030 A Protocol Name A Name of Scan Protocol selected during patient

registration or examination setup A
0018,1100 A Reconstruction Field of View selected for reconstruction A
Diameter A
0.0

July 2013

0018,1110 A Distance Source to A
Detector A
0018,1111 A Distance Source to A
Patient A
0018,1120 A Gantry/Detector Tilt A A
0018,1130 A Table Height A Table height as entered for scan A
0018,1140 A Rotation Direction A A
0018,1150 A Exposure Time A The exposure time for the respective image. For spiral
scan or multiscan this corresponds to the rotation time. A
0018,1151 A X-ray Tube Current A Tube current used for scanning A
0018,1152 A Exposure A (Effective) mAs. For spiral images the product of

exposure time and x-ray tube current is corrected with
Table Feed per Rotation. Expressed in mAs. A
0018,1160 A Filter Type A 0: No Filter, 1: Teflon Filter A
0018,1170 A Generator Power A A
0018,1190 A Focal Spots A Size of the focal spot actually used to generate x-ray
radiation for a particular image.This is a single value
expressed in mm. A
0018,1200 A Date of Last Date of last Base Calibration A
Calibration A
0018,1201 A Time of Last Time of last Base Calibration A
Calibration A
0018,1210 A Convolution Kernel A 4 character code of convolution kernel A
0018,5100 A Patient Position A As entered for scan A
0018,9306 A Single Collimation The width of a single row of acquired data (in mm). A
Width A
0018,9307 A Total Collimation The width of the total collimation (in mm) over the
Width A
area of active x-ray detection. A
0.0


0018,9309 A Table Speed A
The distance in mm that the table moves in one second
during the gathering of data that resulted in this image A
0018,9310 A Table Feed per Motion of the table (in mm) during a complete
Rotation A
revolution of the source around the gantry orbit. A
0018,9311 A CT Pitch Factor A

Ratio of the Table Feed per Rotation (0018, 9310) to the
Total Collimation Width (0018, 9307). A
0018,9323 A Exposure Modulation A label describing the type of exposure modulation used
Type A for the purpose of limiting the dose. A
Defined Terms: A
ModeLib DoseModulationType DICOM Entry (string) A
MlZAxisExposureControl Z_EC A
MlOnlineControl XY_EC A
MlmAControl FIX_EC A
MlAutomaticExposureControl XYZ_EC A
MlDvModulation PULS_EC A
MlDvAdvanced PULS_MINDOSE_EC A
MlDvModulationZEC PULS_EC A
MlDvAdvancedZEC PULS_MINDOSE_EC A
MlDvModulationMAC PULS_EC A
MlDvAdvancedMAC PULS_MINDOSE_EC A
MlAngularTrigger XY_PREDEF_EC A
MlAngularTriggerZEC XY_PREDEF_Z_EC A
MlAngularTriggerMAC XY_PREDEF_FIX_EC A
MlNoModulation OFF A
0018,9324 A Estimated Dose A percent value of dose saving due to the use of
Saving A Exposure Modulation Type (0018,9323). A negative
percent value of dose savings reflects an increase of
exposure. A
0018,9345 A CTDIvol A Computed Tomography Dose Index (CTDIvol), im

mGy according to IEC 60601-2-44, Ed.2.1 (Clause
29.1.103.4), The Volume CTDIvol. It describes the
average dose for this image for the selected CT
conditions A
0.0

July 2013

0019,00xx A Private Creator A Value: SIEMENS CT VA0 COAD A
0019,xxB0 A Feed per Rotation A Movement of table during one rotation in mm A
0020,000D A Study Instance UID A From MWL or created A

0020,000E A Series Instance UID A From MWL or created A
0020,0010 A Study ID A From MWL or created A

0020,0011 A Series Number A created

0020,0012 A Acquisition Number A Scan number within this examination. A
0020,0013 A Instance Number created; direction within range selectable by user

0020,0032 A Image Position The x, y, and z coordinates of the center of the first pixel,
(Patient) in mm.
0020,0037 A Image Orientation
(Patient)
0020,0052 A Frame of Reference created
UID
0020,1040 A Position Reference null-length
Indicator
0.0


0020,1041 A Slice Location Topogram: Slice Location is defined as the relative table
position of the very beginning of the Topogram image
expressed in mm.
Tomogram: Slice Location is defined as the relative
position of the intersection of the image's slice with the
z-axis expressed in mm.
This positions is relative to the current reference point
and corresponds to the table position.
0020,4000 A Image Comments According to user input. 2 lines supported.
0021,00xx A Private Creator Value: SIEMENS MED
0021,xx11 A Target Center x/y as entered for reconstruction
0028,0002 A Samples per Pixel Value: 1
0028,0004 A Photometric Value: MONOCHROME2
Interpretation
0028,0010 A Rows
0028,0011 A Columns
0028,0030 A Pixel Spacing
0028,0100 A Bits Allocated Value: 16
0028,0101 A Bits Stored Value: 12
0028,0102 High Bit Value: 11
0028,0103 A Pixel Representation A Value: 0 A
0028,0106 A Smallest Image Pixel Calculated by examination A
Value A
0028,0107 A Largest Image Pixel Calculated by examination A
Value A A
0028,1050 A Window Center A Last windowing center saved. First window followed by
second window. A
0028,1051 A Window Width A Last windowing width saved. First window followed by
second window. A
0.0

July 2013

0028,1052 A Rescale Intercept A Value -1024 for images without extended CT scale A
0028,1053 A Rescale Slope A Value 1 for images without extended CT scale A
0028,1055 A Window Center & Value: "WINDOW1", "WINDOW2" A
Width Explanation A
0028,2110 A Lossy Image Lossy Image Compression will be set to 01 for Extended
Compression A Field of View because of low image quality. Derivation
Description: "Reconstruction field larger than scan field"
A
0029,xxxx A (private data) A see → page A.4–77 A
0029,xx40 A Application Header see → page A.4–77 A
Sequence A
>0029,00xx A Private Creator A "SIEMENS MEDCOM HEADER" A
>0029,xx41 A Application Header "SOM 5 TPOS" A
Type A "SOMARIS DOSEINFO" A
>0029,xx42 A Application Header ID A "SOM 5 NULLPOSITION" A
"SOMARIS DOSEINFO DATA" A
>0029,xx43 A Application Header "VB10A 20030626" A
Version A "20080109" A
>0029,xx44 A Application Header Table Null Position coded as a null terminated character
Info A buffer A
Character string dose information from patient protocol A
0032,1060 A Requested Procedure Input entered during patient registration or examination

Description A setup. A

7FE0,0010 A Pixel Data A A
0.0

OOG, Overlays, High Bits A.0
Graphics in Somaris/5 images are stored as Object Oriented

Graphics (OOG) in private attributes (→ page A.4–87, MEDCOM
OOG Module). Non syngo based systems are not expected to
interpret this information. A.0
In order to allow display access to graphics information for

DICOM based systems private OOG information is converted on
export into DICOM Overlay information stored in group 6000.
This is the recommended way for a DICOM based system to
access overlay graphics information. A.0
The following attibutes are generated: A.0
Overlay Rows (6000,0010) A.0
Overlay Columns (6000,0011) A.0
Number of Frames in Overlay (6000,0015) A.0
Overlay Description (6000,0022) =

"Siemens MedCom Object Graphics" A.0
Overlay Type (6000,0040) = "G" A.0
Origin (6000,0050) = 1, 1 A.0
Image Frame Origin (6000,0051) A.0
Overlay Bits Allocated (6000,0100) A.0
Bit Position (6000,0102) A.0
Overlay Data (6000,3000) A.0
0.0

July 2013
However, DICOM Overlay information stored in group 6000 is

not supported by all systems that might be used to store
Somaris/5 images. These systems may not be able to display
Somaris/5 generated overlays. For a special group of these sys-
tems there is another way to provide graphical overlay informa-
tion. A remote node can be configured to have overlay graphics
converted into unused pixel data above High Bit (0028,0102)
for images that fulfil the following condition: A.0

Some systems are known to support this coding; they are able
to display this information with the images. Please note, how-
ever, that the proper and recommended way to store overlays
with DICOM is the use of group 6000. A.0
0.0

SC derived images from VSim A.0
SC Derived Image(RGB) from VSim. A.0
An overview of supplied attributes - SC derived image (RGB)

from VSim: A.0
A.0
Attribute Name Tag Value

Specific Character Set A (0008,0005) A (conf. Character Set is added, if
needed) A
Image Type A (0008,0008) A Not Set. A
SOP Class UID A (0008,0016) A 1.2.840.10008.5.1.4.1.1.7 A
SOP Instance UID A (0008,0018) A Generated based on image creation

date and time A
Study Date A (0008,0020) A from original A
Series Date A (0008,0021) A If 'new series': <yyyymmdd> A
Acquisition Date A (0008,0022) A from original A
Image Date A (0008,0023) A Not Set. A
Study Time A (0008,0030) A from original A
Series Time A (0008,0031) A If 'new series': <hhmmss> A
Acquisition Time A (0008,0032) A from original A
Image Time A (0008,0033) A Not Set. A
Accession Number A (0008,0050) A from original A
Modality A (0008,0060) A OT A
Conversion Type A (0008,0064) A WSD A
Manufacturer A (0008,0070) A Siemens Oncology Care Solutions A
Institution Name A (0008,0080) A Not Set. A
Institution Address A (0008,0081) A Not Set. A
Referring Physician´s Name A (0008,0090) A from original A
0.0

July 2013

Station Name A (0008,1010) A Not Set. A
Study Description A (0008,1030) A Vsim_TmpSeries_<num> num= a

running number A
Series Description A (0008,103E) A Not Set. A
Institutional Department (0008,1040) A Not Set. A
Name A
Performing Physician´s Name A (0008,1050) A Not Set. A
Admitting Diagnosis (0008,1080) A Not Set. A
Description A
Manufacturer´s Model Name A (0008,1090) A VSim A
Derivation Description A (0008,2111) A <algorithm> (see [0008,0008]) A
Patient´s Name A (0010,0010) A from Original A
Patient ID A (0010,0020) A from Original A
Patient´s Birth Date A (0010,0030) A from Original A
Patient´s Sex A (0010,0040) A from Original A
Device Serial Number A (0018,1000) A Not Set. A
Secondary Capture Device ID A (0018,1010) A Not Set. A
Date of Secondary Capture A (0018,1012) A <yyyymmdd> A
Time of Secondary Capture A (0018,1014) A <hhmmss> A
Secondary Capture Device (0018,1016) A Not Set. A
Manufacturer A
Manufacturer´s Model Name A
Software Version A
Software Version A (0018,1020) A String containing the build version of

VSim. A
0.0


Protocol Name A (0018,1030) A From original A
Study Instance UID A (0020,000D) A from original A
Series Instance UID A (0020,000E) A If new series generated based on date

and time of image creation else the
original A
Study ID A (0020,0010) A from original A
Series Number A (0020,0011) A <num> num=a running number A
Image Number A (0020,0013) A <num> num=a running number A
Patient Orientation A (0020,0020) A zero length A
Laterality A (0020,0060) A Not Set. A
Image Comments A (0020,4000) A Not Set. A
Samples per Pixel A (0028,0002) A 3 A
Photometric Interpretation A (0028,0004) A RGB A
Rows A (0028,0010) A from original for MPR and MIP images A
512 for DRR images A
Columns A (0028,0011) A from original for MPR and MIP images A
Bits Allocated A (0028,0100) A 8 A
Bits Stored A (0028,0101) A 8 A
High Bit A (0028,0102) A 7 A
Pixel Representation A (0028,0103) A 0 A
Window Center A (0028,1050) A Not Set. A
Window Width A (0028,1051) A Not Set. A
Window Center & Width (0028,1055) A Not Set. A
Explanation A
Study Comments A (0032,4000) A from original A
0.0

July 2013

Overlay Rows A (60xx,0010) A Not Set. A
Overlay Columns A (60xx,0011) A Not Set. A
Overlay Description A (60xx,0022) A Not Set. A
Overlay Type A (60xx,0040) A Not Set. A
Overlay Origin A (60xx,0050) A Not Set. A
Overlay Bits Allocated A (60xx,0100) A Not Set. A
Overlay Bit Position A (60xx,0102) A Not Set. A
Overlay Data A [60xx,3000] A Not Set. A
Pixel Data A (7FE0,0010) A Not Set. A
SC Derived Image (Monochrome) from VSim. A.0
An overview of supplied attributes - SC derived image (mono-

chrome) from VSim: A.0
A.0

Specific Character Set A (0008,0005) A (conf. Character Set is added, if needed) A
Specific Character Set A (0008,0005) A (conf. Character Set is added, if needed) A
Image Type A (0008,0008) A DERIVED\SECONDARY\from Original\ <Value4>

Value4=CSAMPR or CSAMIP or CSADRR A
SOP Class UID A (0008,0016) A 1.2.840.10008.5.1.4.1.1.7 A
SOP Instance UID A (0008,0018) A Generated based on image creation date and
time A
Study Date A (0008,0020) A from original A
Series Date A (0008,0021) A If 'new series': <yyyymmdd> A
Acquisition Date A (0008,0022) A from original A
Image Date A (0008,0023) A Not Set. A
0.0


Study Time A (0008,0030) A from original A
Series Time A (0008,0031) A If 'new series': <hhmmss> A
Acquisition Time A (0008,0032) A from original A
Image Time A (0008,0033) A Not Set. A
Accession Number A (0008,0050) A from original A
Modality A (0008,0060) A OT A
Conversion Type A (0008,0064) A WSD A
Manufacturer A (0008,0070) A Siemens Oncology Care Solutions A
Institution Name A (0008,0080) A Not Set. A
Institution Address A (0008,0081) A Not Set. A
Referring Physician´s Name A (0008,0090) A from original A
Study Description A (0008,1030) A VSim_TmpSeries_<num> num = a running

number A
Series Description A (0008,103E) A Not Set. A
Institutional Department (0008,1040) A Not Set. A
Name A
Performing Physician´s Name A (0008,1050) A Not Set. A
Admitting Diagnosis (0008,1080) A Not Set. A
Description A
Manufacturer´s Model Name A (0008,1090) A VSim A
Derivation Description A (0008,2111) A <algorithm> (see [0008,0008]) A
Patient´s Name A (0010,0010) A from Original A
Patient ID A (0010,0020) A from Original A
Patient´s Birth Date A (0010,0030) A from Original A
Patient´s Sex A (0010,0040) A from Original A
0.0

July 2013

Device Serial Number A (0018,1000) A Not Set. A
Secondary Capture Device ID A (0018,1010) A Not Set. A
Date of Secondary Capture A (0018,1012) A <yyyymmdd> A
Time of Secondary Capture A (0018,1014) A <hhmmss> A
Manufacturer A
Manufacturer´s Model Name A
Software Version A
Software Version A (0018,1020) A String containing the build version of VSim. A
Protocol Name A (0018,1030) A From original A
Study Instance UID A (0020,000D) A from original A
Series Instance UID A (0020,000E) A If new series generated based on date and time
of image creation else the original A
Study ID A (0020,0010) A from original A
Series Number A (0020,0011) A <num> num=a running number A
Image Number A (0020,0013) A <num> num=a running number A
Patient Orientation A (0020,0020) A zero length A
Laterality A (0020,0060) A Not Set. A
Image Comments A (0020,4000) A Not Set. A
Samples per Pixel A (0028,0002) A 1 A
Photometric Interpretation A (0028,0004) A MONOCHROME2 A
Rows A (0028,0010) A from original for MPR and MIP images A
Columns A (0028,0011) A from original for MPR and MIP images A
0.0


Bits Allocated A (0028,0100) A from original for MPR and MIP images A
Bits Stored A (0028,0101) A from original for MPR and MIP images A
High Bit A (0028,0102) A from original for MPR and MIP images A
Pixel Representation A (0028,0103) A 0 A
Window Center A (0028,1050) A Not Set. A
Window Width A (0028,1051) A Not Set. A
Window Center & Width (0028,1055) A Not Set. A
Explanation A
Study Comments A (0032,4000) A from original A
Overlay Rows A (60xx,0010) A from original A
Overlay Columns A (60xx,0011) A from original A
Overlay Description A (60xx,0022) A from original A
Overlay Type A (60xx,0040) A from original A
Overlay Origin A (60xx,0050) A from original A
Overlay Bits Allocated A (60xx,0100) A from original A
Overlay Bit Position A (60xx,0102) A from original A
Overlay Data A [60xx,3000] A Graphics Overlay A
Pixel Data A (7FE0,0010) A from original A
0.0

July 2013
IOD Specific Implementation Details for VSim A.0
A.0
The VSim application RT IOD specific implementation details are

provided with respect to its role as service class user (SCU) as
well as service class provider (SCP) in the notes. A.0
0.0

The VSim application as service class provider (SCP) makes a

copy of all non siemens RT objects identified by General Equip-
ment Module Manufacturer Name (0008,0070) set other than
“Siemens Oncology Care Solutions” and Manufacturer's Model
Name (0008,1090) set other than “COHERENCE Dosimetrist
Workspace”. During import of non siemens RT objects in the
case that the provided value of an attribute is other than that
expected by the VSim application; the attribute is corrected in
copied RT object as in the notes below. The original RT objects
are kept intact. A.0
A.0
RT Structure Set IOD Module for VSim A
IE Module Reference Usage Notes
Patient A Patient A C 7.1.1 A M A A
Study A General Study A C 7.2.1 A M A A
Patient Study A C 7.2.2 A U A Not

Supported A
Series A RT Series A C 8.8.1 A M A A
Equipment A General C 7.5.1 A M A A
Equipment A
StructureSet A Structure Set A C 8.8.5 A M A A
ROI Contour A C 8.8.6 A M A A
RT ROI C 8.8.8 A M A A
Observation A
Approval A C 8.8.16 A U A Not

Supported A
Audio A C 10.3 A U A Not

Supported A
SOP Common A C 12.1 A M A A
0.0

July 2013
RT Structure Set IOD Module for VSim A

Patient Study A C 7.2.2 A U A Not Supported A
Equipment A
StructureSet A Structure Set A C 8.8.5 A M A A
ROI Contour A C 8.8.6 A M A A
RT ROI C 8.8.8 A M A A
Observation A
Approval A C 8.8.16 A U A Not Supported A
Audio A C 10.3 A U A Not Supported A
A.0
RT Plan IOD Module Table for VSim A


Supported A
Equipment A
0.0

RT Plan IOD Module Table for VSim A

Plan A RT General Plan A C 8.8.9 A M A A
RT Prescription A C 8.8.10 A U A Not

Supported A
RT Tolerance C 8.8.11 A U A Not

Tables A Supported A
RT Patient Setup A C 8.8.12 A U A A
RT Fraction C 8.8.13 A U A Not

Scheme A Supported A
RT Beams A C 8.8.14 A C A A
RT Brachy C 8.8.15 A C A Not

Application Setups A Supported A

Supported A

Supported A
0.0

July 2013
A.0
RT Image IOD Module Table for VSim A


Supported A
Frame of Reference A Frame of C 7.4.1 A U A A
Reference A
Equipment A
0.0

RT Image IOD Module Table for VSim A

Image A General Image A C 7.6.1 A M A A
Image Pixel A C 7.6.3 A M A A
Contrast/bolus A C 7.6.4 A C A Not

Supported A
Cine A C 7.6.5 A C A Not

Supported A
Multi-Frame A C 7.6.6 A C A Not

Supported A
RT Image A C 8.8.2 A M A A
Modality LUT A C 11.1 A U A Not

Supported A
VOI LUT A C 11.2 A U A Not

Supported A

Supported A
Curve A C 10.2 A U A Not

Supported A

Supported A
A.0
Note
Whenever an existing RT object is changed and saved, WSim
generates new SOP Instance UIDs for the RT IODs saved. A
0.0

July 2013
A.0
RT Series Module Table for VSim A
Attribute Name Tag Comments

Modality A (0080,0060) A RTIMAGE = RT Image A
RTSTRUCT = RT StructureSet A
RTPLAN = RT Plan A
RTDOSE and RTRECORD are not

supported. A
Series Instance UID A (0020,000E) A Filled at the time of Series creation A
Series Number A (0020,0011) A Filled at the time of creation. A
Series Description A (0008,103E) A Filled at the time of creation. A
Referenced Study Component (0008,1111) A Not Set. A
Sequence A
Request Attributes Sequence A (0040,0275) A Not Set. A
Performed Procedure Step ID A (0040,0253) A Not Set. A
Performed Procedure Step Start Date A (0040,0244) A Not Set. A
Performed Procedure Step Start Time A (0040,0245) A Not Set. A
Performed Procedure Step Description A (0040,0254) A Not Set. A
Performed Protocol Sequence A (0040,0260) A Not Set. A
A.0
General Equipment Module Table for VSim A

Manufacturer A (0008,0070) A VSim fills this attribute with a string which is containing
the manufacturer name which is always “Siemens
Oncology Care Solutions”. A
In case provided value is other than “Siemens Oncology

Care Solutions” during import the attribute is filled with
same value as VSim created RT objects. A
0.0

General Equipment Module Table for VSim A

Institution (0008,0080) A Not Set. A
Name A
Institution (0008,0081) A Not Set. A
Address A
Institutional (0008,1040) A Not Set. A
Department
Name A
Manufacturer's (0008,1090) A VSim fills this attribute with a string containing the
Model Name A workspace name used to create the objects. For VSim
this value is always “COHERENCE Dosimetrist
Workspace”. A
In case provided value is other than “VSim” during

import the attribute is filled with same value as VSim
created RT objects. A
Device Serial (0018,1000) A Not Set. A
Number A
Software (0018,1020) A String containing the build and version information of

Versions A VSim software used to create RT Objects. A
Format: 2.0.100 - Implies version 2.0, build 100 of VSim

software was used to create the objects. A
Spatial (0018,1050) A Not Set. A
Resolution A
Date of Last (0018,1200) A Not Set. A
Calibration A
Time of Last (0018,1201) A Not Set. A
Calibration A
Pixel Padding (0028,0120) A Not Set. A
Value A
0.0

July 2013
A.0
RT Structure Set Module Table for VSim A
Attribute Name Tag Notes

Structure Set Label A (3006,0002) A VSim always fills this attribute with the string
“VSimStructureSet” A
In case of non siemens RT objects the attribute is filled

with same value as VSim created RT objects. A
Structure Set Name A (3006,0004) String containing the build and version information of
A
VSim software used to create the structure set. A
Format: VSim x.y SL nnn A
Where x.y is the VSim version A
nnn- Build number A

with same value as VSim created RT object A
Instance Number A (0020,0013) A An integer value A

with internally generated integer value for copied
structure set. A
Structure Set Date A (3006,0008) A Last modification date A
In case not provided set to system date. A
Structure Set Time A (3006,0009) A Last modification time. A
In case not provided set to system time. A
Referenced Frame of Reference A
Sequence A (3006,0010) A Dataset must have sequence describing the frame of

reference for the dataset. Only one sequence is
populated. A
> Frame of Reference (0020,0052) Frame of Reference UID of the CT series used to define
A
UID A the structures and ROIs. A
Dataset must have in case of siemens and non siemens

RT objects. A
> Frame of Reference A (3006,00C0) A Not Supported. A
Relationship Sequence A
0.0


>>Related Frame of (3006,00C2) A Not Supported. A
Reference A
UID A
>>Frame of Reference A (3006,00C4) A Not Supported. A
Transformation Type A
Transformation Matrix A
Transformation
Comment A
> RT Referenced Study A (3006,0012) A Reference to Study to which CT series belongs. Only
Sequence A one sequence is populated. A

RT objects. A
>> Referenced SOP Class (0008,1150) A Study SOP Class UID as mentioned in the DICOM
UID A standard. A

RT objects. A
>> Referenced SOP (0008,1155) A Study SOP instance UID. A
Instance A Dataset must have in case of siemens and non siemens

UID A RT objects. A
>>RT Referenced Series A (3006,0014) Reference to CT series to which the CT images belong.
A
Sequence A Only one sequence is populated. A
Note: There is exactly one RT Structure Set referencing

a CT image Series. A
>>>Series Instance UID A (0020,000E) A SOP Instance UID of CT Series used to define the
structures. A

RT objects A
>>>Contour Image (3006,0016) A This is reference to the CT input images used in to

Sequence A define the Structure set. A
0.0

July 2013

>>>>Referenced SOP (0008,1150) A CT Image SOP Class UID A
Class A
UID A
>>>>Referenced SOP (0008,1155) A SOP Instance UID of CT image A
Instance A
UID A
>>>>Referenced Frame A (0008,1160) A Not Set. A
Number A
Structure Set ROI (3006,0020) The sequence contains Structure Set ROI Sequence for
A
Sequence A all ROIs and Reference Points created by VSim. A

RT objects. A
> ROI Number A (3006,0022) A Integer number assigned during creation of ROI. Used
to uniquely identify the corresponding ROI Contour
and RT ROI Observations modules under a structure
set. VSim ensures uniqueness of this attribute while
creating ROIs. A

RT objects. A
> Referenced Frame of A (3006,0024) Frame of Reference UID of the CT series used for which
A
Reference UID A ROI is defined. A

RT objects. A
> ROI Name A (3006,0026) A ROI or Reference Point name. A
Default names generated and set for ROI and points if

not provided. A
> ROI Description A (3006,0028) A Not Set. A
> ROI Volume A (3006,002C) A Not Set. A
> ROI Generation (3006,0036) A Always set to SEMIAUTOMATIC. A
Algorithm A
0.0


> ROI Generation (3006,0038) A Not Set. A
Description A
A.0
ROI Contour Module Table for VSim A

ROI Contour Sequence A (3006,0039) A VSim creates/requires at least one ROI Contour
module to be present in a Structure Set. A
> Referenced ROI Number A (3006,0084) A An integer used to uniquely identify the ROI and its
associated modules within a Structure Set. Dataset
must have in case of siemens and non siemens RT
objects. A
> ROI Display Color A (3006,002A) A VSim expects/fills 3 integer values in the range 0-
255. These values are interpreted as RGB
components of display color. Sets default color to
red if not provided. A
> Contour Sequence A (3006,0040) A VSim stores the contour information in this
attribute. For structures there can be zero or more
contour sequences. For Reference Point, only one
contour sequence is stored. A
>> Contour Number A (3006,0048) A VSim stores a unique number within Contour
Sequence (3006,0040). A
>> Attached Contours A (3006,0049) A Not Set. A
>> Contour Image (3006,0016) A VSim passes this sequence for every contour
Sequence A sequence. Note: This is passed only for structures
and not for reference points. Dataset must have in
case of siemens and non siemens RT objects. A
>>> Referenced SOP Class (0008,1150) A CT Image SOP Class UID as defined in DICOM.
UID A Dataset must have in case of siemens and non
siemens RT objects. A
0.0

July 2013
ROI Contour Module Table for VSim A

>>> Referenced SOP (0008,1155) A SOP Instance UID of the CT image on which the
Instance UID A contour is drawn. Dataset must have in case of
siemens and non siemens RT objects. A
>>> Referenced Frame (0008,1160) A VSim stores the default frame number of CT Image
Number A i.e., 0. CT images are not single frame images.
Removed from copied structure set in case of non
>> Contour Geometric (3006,0042) A VSim stores the geometry of contour. For Reference
Type A Points, the value is “POINT”. For Structures or ROIs
the value is always “CLOSED_PLANAR”. VSim always
creates closed planar contours. Dataset must have in
>> Contour Slab (3006,0044) A Not Set. A
Thickness A
>> Contour Offset Vector A (3006,0045) A Not Set. A
>> Number of Contour (3006,0046) A VSim stores the number of contour points in the
Points A contour. Dataset must have in case of siemens and
non siemens RT objects. A
Note: For Reference Point it is always 1. A
>> Contour Data A (3006,0050) A VSim stores the contour data as sequence of triplets.
(X, Y & Z coordinates of each point). Dataset must
have in case of siemens and non siemens RT objects. A
0.0

A
RT ROI Observations Module Table for VSim A

RT ROI Observations (3006,0080) A VSim stores observation related to ROI / Reference
Sequence A Point. Dataset must have in case of siemens and non
siemens RT objects A
> Observation Number A (3006,0082) A Unique integer identifying the Observation within the
Observation Sequence. VSim sets it equal to the
Reference ROI Number (3006,0084) because, as of the
current version, only one Observation is supported per
ROI. A
> Referenced ROI (3006,0084) A An integer used to uniquely identify the ROI and its
Number A associated modules within a Structure Set. Dataset
must have in case of siemens and non siemens RT
objects. A
> ROI Observation Label A (3006,0085) A VSim stores the name of the ROI/Reference Point
(truncated to 16 characters) as set in the ROI
Name(3006,0026) attribute of Structure Set ROI
Sequence under RT Structure Set. A
> ROI Observation (3006,0088) A Not Set. A
Description A
> RT Related ROI (3006,0030) A Not Set. A
Sequence A
>> Referenced ROI (3006,0084) A Not Set. A
Number A
>> RT ROI Relationship A (3006,0033) A Not Set. A
> RT ROI Identification (3006,0086) A Not Set A
Code Sequence A
> Related RT ROI (3006,00A0) A Not Set A
Observations Sequence A
>> Observation Number A (3006,0082) A Not Set. A
0.0

July 2013
RT ROI Observations Module Table for VSim A

> RT ROI Interpreted Type A (3006,00A4) A VSim stores the information about the type of ROI /
Reference Point. VSim sets/interprets the following
terms as: A
EXTERNAL, PTV, CTV, GTV, TREATED_VOLUME,

IRRAD_VOLUME, BOLUS, AVOIDANCE, ORGAN,
REGISTRATION, CONTRAST_AGENT, CAVITY,
BRACHY_CHANNEL, BRACHY_ACCESSORY,
BRACHY_SRC_APP, BRACHY_CHNL_SHLD - All these are
structures. A
MARKER - Marked Reference Point A
ISOCENTER - Reference Point A
In case of non siemens RT objects if not provided is set

to ORGAN if Contour Geometric Type (3006,0042) is
CLOSED_PLANER and set to ISOCENTER if its POINT in
copied structure set. A
> ROI Interpreter A (3006,00A6) A Not Set. A
> Material ID A (300A,00E1) A Not Set. A
> ROI Physical Properties (3006,00B0) VSim stores the physical property associated of the
A
Sequence A ROI. Only one value for this SQ is supported if and only
if the physical property is other then “CT.” The value is
always electron density relative to water. A
Also for Reference Points, this attribute is not set and

should not be interpreted as default CT. A
>> ROI Physical Property A (3006,00B2) A VSim always stores the ROI Physical Property Value
(3006, 00B4) as electron density relative to water.
Hence this attribute will always have the value
“REL_ELEC_DENSITY” A
>> ROI Physical Property (3006,00B4) A number set by the user as the physical property of
A
Value A the ROI. The following values should be interpreted as

given below: A
1 - Water A
0.19 - Air. A
Note: The attribute value has to be interpreted as

electron density relative to water. A
0.0

A.0
RT General Plan Module Table for VSim A

RT Plan Label A (300A,0002) A VSim stores the name of the Plan in this attribute. A
RT Plan Name A (300A,0003) A String containing the build and version information of
VSim software used to create the structure set. A
Format: VSim x.y SL nnn A
Where x.y is the VSim version nnn- Build number. A
In case of non siemens RT objects set to same as VSim in

the copied RT Plan. A
Instance Number A (0020,0013) A VSim sets this attribute with an internally generated
instance number. A
Operator's Name A (0008,1070) A VSim sets the current user name as operator name in RT
Series. This attribute is mapped on to the Operator name
attribute of series. A
RT Plan Date A (300A,0006) VSim stores the last modification date of the plan. In case
A
not provided set to system date. A
RT Plan Time A (300A,0007) VSim stores the last modification time of the plan. In case
A
not provided set to system time. A
Treatment Protocols A (300A,0009) A Not Set. A
Treatment Intent A (300A,000A VSim always sets this attribute with the value
) A “CURATIVE” A
Treatment Sites A (300A,000B) A Not Set. A
RT Plan Geometry A (300A,000C) VSim always sets this attribute with the value “PATIENT”.
A
In case of non siemens RT objects “PATIENT” and

“TREATMENT_DEVICE” are supported. if RT Plan
Geometry is “TREATMENT_DEVICE” the plan should be
based on single CT, single study, its converted to
“PATIENT” based in the copied RT Plan. A
0.0

July 2013

Referenced Structure (300C,0060) A VSim stores the RT Structure Set information, based on
Set Sequence A which the plan is designed/created. Only one value is set
in this sequence. In case of non siemens RT objects
ignored if RT Plan Geometry is “TREATMENT_DEVICE” the
plan should be based on single CT, single study, and
structure set reference is added when converted to
> Referenced SOP (0008,1150) A SOP Class UID of structure set as defined in DICOM. In
Class UID A case of non siemens RT objects ignored if RT Plan
Geometry is “TREATMENT_DEVICE” the plan should be
based on single CT, single study, and structure set
reference is added when converted to “PATIENT” based in
the copied RT Plan. A
> Referenced SOP (0008,1155) A VSim stores the SOP Instance UID of the Structure set
Instance UID A used to create the plan. In case of non siemens RT objects
ignored if RT Plan Geometry is “TREATMENT_DEVICE” the
plan should be based on single CT, single study, and
structure set reference is added when converted to
Referenced Dose (300C,0080) A Not Set. A
Sequence A
> Referenced SOP (0008,1150) A Not Set. A
Class UID A
Instance UID A
Referenced RT Plan (300C,0002) A Not Set. A
Sequence A
Class UID A
Instance UID A
0.0


> RT Plan Relationship (300A,0055)
A A Not Set. A
> SIEMENS MED OCS (0039,XX76) A Private attribute stores beam number, beam color and
BEAM DISPLAY INFO A beam group separated by “,” for a beam. The values for
all beams are separated by “;”. Beam color is stored as
RGB string. Beams are grouped having common
isocenter. A
A.0
RT Patient Setup Module Table for VSim A

Patient Setup Sequence A (300A,0180) A VSim stores the patient setup information for the
following kinds of beams in the RT General Plan: A
Relative beams (includes SSD based relative

beams) and absolute SSD based beams. A
If this module is present it is ignored (deleted)

and recreated as per VSim specification for non-
> Patient Setup Number A (300A,0182) A VSim stores a number that is unique within a
plan. Beams under the plan refer to this number
for patient setup information (referenced
Isocenter and table position information). A
> Patient Position A (0018,5100) A VSim stores the patient position information as
set in the CT series used to create the structure
set. A
> Patient Additional (300A, 0184) A Not Set. Since Patient Position (0018, 5100) is
Position A set, VSim does not set this attribute. A
> Fixation Device (300A, 0190) A Not Set. A
Sequence A
>> Fixation Device Type A (300A, 0192) A Not Set. A
>> Fixation Device Label A (300A, 0194) A Not Set. A
0.0

July 2013

>> Fixation Device (300A, 0196) A Not Set. A
Description A
>> Fixation Device Position A (300A, 0198) A Not Set. A
> Shielding Device (300A, 01A0) A Not Set. A
Sequence A
>> Shielding Device Type A (300A, 01A2) A Not Set. A
>> Shielding Device Label A (300A, 01A4) A Not Set. A
>> Shielding Device (300A, 01A6) A Not Set. A
Description A
>> Shielding Device (300A, 01A8) A Not Set. A
Position A
> Setup Technique A (300A,01B0) A VSim sets this attribute only in case of SSD based
beams. In such cases the value set will be
“FIXED_SSD” A
> Setup Technique (300A,01B2) A Not Set. A
Description A
> Setup Device Sequence A (300A,01B4) A VSim uses this attribute to store the patient
alignment information. This SQ attribute is filled
if and only if the patient setup module under the
plan is referenced by one or more Relative (or
Relative-SSD) beams under the plan. VSim
optimizes on the number of patient setup
modules referenced by beams under a plan by
keeping only one patient setup module for beams
based on the same reference point and table
position. A
>> Setup Device Type A (300A,01B6) A VSim stores setup device for the patient
alignment as “LASER_POINTER” A
>> Setup Device Label A (300A,01B8) A Not Set. A
0.0


>> Setup Device (300A,01BA) A Not Set. A
Description A
>> Setup Device Parameter A (300A,01BC) A VSim always sets this attribute to 0. A
>> Setup Reference (300A,01D0) A VSim uses this attribute to store the Marked
Description A Reference Point name used to align the patient. A
> Table Top Vertical Setup A A A
displacement A (300A,01D2) A VSim stores table top vertical displacement from

the specified Marked Reference point to obtain
the beam isocenter. A
Note: This is filled only for relative beams. A
> Table Top Longitudinal (300A,01D4) A VSim stores Table top longitudinal displacement
Setup displacement A from the specified Marked Reference point to
obtain the beam isocenter. A
> Table Top Lateral Setup (300A,01D6) A VSimstores Table top lateral displacement from
displacement A the specified Marked Reference point to obtain
the beam isocenter. A
A.0
RT Beam Module for VSim A

Beam Sequence A (300A,00B0) A VSim does not support plans without beams. At least
one Beam module will exist under a plan. A
> Beam Number A (300A,00C0) A VSim stores the beam number in this attribute. The
beam number may be entered by the user or
generated by the software. VSim generates only
positive numbers in the range 1- 231 -1 as beam
numbers. In case of non siemens RT objects beam
number is generated if not provided. A
0.0

July 2013

> Beam Name A (300A,00C2) A VSim stores the beam number as it appears in (300A,
00C0). In case of non siemens RT objects Beam Name
is taken from Beam Name (300A,00C2) and set in
Beam Description (300A,00C3) in the copied RT plan.
Unique beam name is generated by setting Beam
Number (300A,00C0) if Beam Name is not provided. A
> Beam Description A (300A,00C3) A VSim uses this attribute to store the beam name. In
case of non siemens RT objects name of beam is put
in Beam Description. A
> Beam Type A (300A,00C4) A VSim sets this values as “STATIC”. Currently VSim
creates/ supports STATIC beams only. In case of non
siemens RT objects if beam type is “DYNAMIC” It is
converted to “STATIC” only control points with index 0
and 1 are kept rest are removed. A
> Radiation Type A (300A,00C6) A VSim creates/supports only “ELECTRON” and

“PHOTON” beams as configured on the site. A
> Treatment Machine (300A,00B2) A VSim stores the name of the machine selected by the
Name A user to create the beam. Dataset must have in case of
siemens and non siemens RT objects, if a machine
with same name is not configured, the plan is
rejected. A
> Manufacturer A (0008,0070) A VSim stores the machine manufacturer's name in this
attribute. The machine/equipment name used for
beam delivery is read from configuration. This
information is set at the time of configuring the
machine. In case of non siemens RT objects set same
as VSim. A
> Institution Name A (0008,0080) A VSim stores the name of the Institution where the
machine/equipment is located. This information is
read from configuration set at the time of configuring
the machine. In case of non siemens RT objects set
same as VSim. A
0.0


> Institution Address A (0008,0081) A Not Set. A
> Institutional (0008,1040) A Not Set. A
Department Name A
> Manufacturer's (0008,1090) A Not Set. A
Model Name A
> Device Serial (0018, 1000) A Not Set. A
Number A
> Primary Dosimeter (300A, 00B3) A Not Set. A
Unit A
> Referenced Tolerance (300C, 00A0) A Not Set. A
Number A
> Source - Axis (300A,00B4) A VSim stores the Source to Axis Distance of the
Distance A machine. This information is read from configuration
set at the time of configuring the machine. In case of
non siemens RT objects set to configured value in
case of mismatch in the copied RT plan. A
> Beam Limiting Device (300A,00B6) A VSim uses this attribute to store the beam limiting
Sequence A device information. Information is read from
configuration set at the time of configuring a
machine. The number of SQs in this attribute
depends on the number of BLDs in the machine. For
each BLD a SQ exists under a beam. Required in case
of siemens and non siemens RT objects. If extra
sequence are present not supported by configured
machine they are removed from the copied RT plan. A
0.0

July 2013

>> RT Beam Limiting (300A,00B8) A VSim uses this attribute to store the beam limiting
Device Type A device type. It can be one of: A
ASYMX A
ASYMY A
MLCX A
MLCY A
Required to be one of mentioned above in case of

siemens and non siemens RT objects. A
>> Source to Beam (300A,00BA) A VSim uses this attribute to store the source to beam
Limiting Device limiting device distance. A
Distance A In case not provided set same as read from site

configuration A
>> Number of Leaf/Jaw (300A,00BC) A VSim stores the number of BLD pairs information for
Pairs A a beam limiting device in this attribute. This is always
read from site configuration. Required in case of
siemens and non siemens RT objects and must match
with the configured machine. A
>> Leaf Position (300A,00BE) A VSim uses this attribute to store the leaf position
Boundaries A boundaries ONLY. This information is stored only for
MLC type beam limiting devices. In case not provided
set same as read from site configuration. A
> Referenced Patient (300C,006A) A VSim uses this attribute to store the patient setup
Setup Number A number corresponding to the patient setup module
containing the patient alignment information for the
Relative beams and all SSD based beams. In case of
non siemens RT objects set to created/recreated
patient setup number. A
> Referenced Reference (300C,0042) A Sequence of referenced RT images used for validation
Image Sequence A of current beam. A
>> Referenced SOP (0008,1150) A RT image SOP Class UID as per DICOM. A
Class UID A
0.0


>> Referenced SOP (0008,1155) A SOP instance UID of referenced RT image for beam. A
Instance UID A
>> Reference Image (300A,00C8) A RT image number generated internally for referenced
Number A RT image. A
>> Start Cumulative (300C,0008) A Not Set. A
Meterset Weight A
>> End Cumulative (300C,0009) A Not Set. A
Meterset Weight A
> Planned Verification (300A, 00CA) A Not Set. A
Image Sequence A
>> Start Cumulative (300A,00C8) A Not Set. A
Meterset Weight A
>> Meterset Exposure A (3002,0032) A Not Set. A
>> End Cumulative (300C,0009) A Not Set. A
Meterset Weight A
>> RT Image Plane A (3002,000C) A Not Set. A
>> X-Ray Image (3002, 000E) A Not Set. A
Receptor Plane A
>> RT Image (3002, 0010) A Not Set. A
Orientation A
>> RT Image Position A (3002, 0012) A Not Set. A
>> RT Image SID A (3002, 0026) A Not Set. A
>> Imaging Device- (300A, 00CC) A Not Set. A
Specific Acquisition
Parameters A
>> Referenced (300A, 0007) A Not Set. A
Reference Image
Number A
0.0

July 2013

> Treatment Delivery (300A, 00CE) A A
Type A
> Referenced Dose (300C,0080) A Not Set. A
Sequence A
>> Referenced SOP (0008,1150) A Not Set. A
Class UID A
>> Referenced SOP (0008,1155) A Not Set. A
Instance UID A
> Number of Wedges A (300A,00D0) A VSim stores always 0 as value. A
> Wedge Sequence A (300A, 00D1) A Not Set. Since Number of Wedges (300A, 00D0) is set
to 0, this SQ is not set. A
>> Wedge Number A (300A, 00D2) A Not Set. A
>> Wedge Type A (300A, 00D3) A Not Set. A
>> Wedge ID A (300A, 00D4) A Not Set. A
>> Wedge Angle A (300A, 00D5) A Not Set. A
>> Wedge Factor A (300A, 00D6) A Not Set. A
>> Wedge Orientation A (300A, 00D8) A Not Set. A
>> Source to Wedge (300A, 00DA) A Not Set. A
Tray Distance A
> Number of (300A,00E0) A VSim stores always 0 as value. A
Compensators A
> Total Tray (300A,00E2) A Not Set. A
Compensator Factor A
> Compensator (300A, 00E3) A Not Set. Since Number of Compensators (300A,
Sequence A 00E0) is set to 0, this SQ is not set. A
>> Compensator (300A, 00E4) A Not Set. A
Number A
0.0


>> Compensator Type A (3004, 00EE) A Not Set. A
>> Material ID A (300A, 00E1) A Not Set. A
>> Compensator ID A (300A, 00E5) A Not Set. A
>> Source to (300A, 00E6) A Not Set. A
Compensator Tray
Distance A
>> Compensator Rows A (300A, 00E7) A Not Set. A
>> Compensator (300A, 00E8) A Not Set. A
Columns A
>> Compensator Pixel (300A, 00E9) A Not Set. A
Spacing A
>> Compensator (300A, 00EA) A Not Set. A
Position A
>> Compensator (300A, 00EB) A Not Set. A
Transmission Data A
>> Compensator (300A, 00EC) A Not Set. A
Thickness Data A
> Number of Boli A (300A,00ED) A VSim stores always 0 as value. A
> Referenced Bolus (300C, 00B0) A Not Set. Since Number of Boli (300A, 00ED) is set to
Sequence A 0, this SQ is not set. A
>> Referenced ROI (3006, 0084) A Not Set. A
Number A
> Number of Blocks A (300A, 00F0) A VSim stores the number of blocks/ports for the
current beam. This information is only for HPD
machines (machines with only jaws as beam limiting
device). For all other machines (machines with beam
limiting device as MLC, or both MLC and jaws) value
stored is 0 as they do not support blocks. A
0.0

July 2013

> Total Block Tray (300A, 00F2) A Not Set. A
Factor A
> Block Sequence A (300A, 00F4) A VSim stores the block data for HPD machines having
one or more number of blocks. For MLC machines this
SQ attribute is not set. VSim expects the Block type
(300A, 00F8) to be same for all blocks under the
sequence. A
>> Block Tray ID A (300A,00F5) A Not Set. A
>>Source to Block Tray (300A, 00F6) A VSim stores the source to block tray distance in this
Distance A attribute. This information is read from configuration
set at the time of configuring a machine. A
>> Block Type A (300A, 00F8) A VSim stores the following values: A
SHIELDING - for blocks A
APERTURE - for ports A
>> Block Divergence A (300A, 00FA) A VSim always sets the value “ABSENT” A
>> Block Number A (300A, 00FC) A VSim generates a unique number under the beam for
this attribute. A
>> Block Name A (300A, 00FE) A Not Set. A
>> Material ID A (300A, 00E1) A Not Set. A
>> Block Thickness A (300A, 0100) A VSim always sets the value 0 A
>> Block Transmission A (300A, 0102) A VSim always sets the value 0 A
>> Block Number of (300A, 0104) A Number of points present in the contour drawn for
Points A block/port A
>> Block Data A (300A, 0106) A Actual contour data drawn by user. A
> Applicator Sequence A (300A, 0107) A Not Set. A
>> Applicator ID A (300A, 0108) A Not Set. A
>> Applicator Type A (300A, 0109) A Not Set. A
0.0


>> Applicator (300A, 010A) A Not Set. A
Description A
> Final Cumulative (300A,010E) A VSim always stores 1, so that the cumulative meterset
Meterset Weight A weight is equal to the fraction of the beam meterset
delivered at each control point. A
> Number of Control (300A,0110) A Since VSim creates only STATIC beams, the value is set
Points A to 2. In case of non siemens RT objects only first two
control points will be read. A
> Control Point (300A,0111) A Contains exactly 2 control points. All Control Point
Sequence A parameters are set for 1st control point. 2nd control
point contains, only, Control Point index and
Cumulative meterset weight. Dataset must have in
>> Control Point Index A (300A,0112) A 0 for 1st control point and 1 for 2nd control point.
Dataset must have in case of siemens and non
siemens RT objects A
>> Cumulative (300A,0134) A The first control point always has a cumulative
Meterset Weight A meterset weight set to zero (0). Because VSim creates
only STATIC beams, the second control point always
has a cumulative meterset weight equal to the final
cumulative meterset weight (300A,010E). A
>> Referenced Dose (300C, 0050) A Not Set. A
Reference Sequence A
>>> Referenced Dose (300C, 0051) A Not Set. A
Reference Number A
>>> Cumulative Dose (300A, 010C) A Not Set. A
Reference Coefficient A
>> Nominal Beam (300A,0114) A Default is set as configured for a machine or set to the
Energy A value entered by user. In case of non siemens RT
objects energy will be taken from the first control
point. A
0.0

July 2013

>> Dose Rate Set A (300A,0115) A Not Set. A
>> Wedge Position (300A, 0116) A Not Set. A
Sequence A
>>> Referenced Wedge (300A, 00C0) A Not Set. A
Number A
>>> Wedge Position A (300A,0118) A Not Set. A
>> Beam Limiting (300A,011A) A BLD sequence which represents the actual values.
Device Position Dataset must have in case of siemens and non
Sequence A siemens RT objects. A
>>> RT Beam Limiting (300A,00B8) A Set as per the machine configuration A
Device Type A
>>> Leaf/Jaw Positions A (300A,011C) A Actual positions as they appear in the UI (BEV or edit
beam dialog) A
>> Gantry Angle A (300A,011E) A Gantry angle as set by user A
>> Gantry Rotation (300A,011F) A NONE A
Direction A
>> Beam Limiting (300A,0120) A As set by user A
Device Angle A
>> Beam Limiting (300A,0121) A NONE A
Device Rotation
Direction A
>> Patient Support (300A,0122) A Patient Support Angle as set by user A
Angle A
>> Patient Support (300A,0123) A NONE A
Rotation Direction A
>> Table Top Eccentric (300A,0124) A 0 A
Axis Distance A
0.0


>> Table Top Eccentric (300A,0125) A Read from registry and set A
Angle A
>> Table Top Eccentric (300A,0126) A NONE A
Rotation Direction A
>> Table Top Vertical (300A,0128) A Table top vertical position set if beam is not relative A
Position A
>> Table Top (300A,0129) A Table top longitudinal position is set if beam is not
Longitudinal Position A relative A
>> Table Top Lateral (300A,012A) A Table top lateral position is set if beam is not relative A
Position A
>> Isocenter Position A (300A,012C) A Beam isocenter position in patient coordinate

system. A
>> Surface Entry Point A (300A,012E) A Set if external ROI is present along the beam axis. A
>> Source to Surface (300A,0130) A Set if external ROI is present along beam axis, other
Distance A wise 0 is set. A
A.0
RT Image Module Table for VSim A

Samples per Pixel A (0028, 0002) A 1 A
Photometric (0028, 0004) A MONOCHROME2 A
Interpretation A
Bits Allocated A (0028, 0100) A 16 A
Bits Stored A (0028, 0101) A 12 A
High Bit A (0028, 0102) A 11 (Bits Stored - 1) A
Pixel Representation A (0028, 0103) A 0000H (unsigned integer) A
RT Image Label A (3002, 0002) A Beam name to which RT Image refers. A
0.0

July 2013

RT Image Name A (3002, 0003) A A
RT Image Description A (3002, 0004) A Not Set. A
Image Type A (0008, 0008) A “DERIVED/ SECONDARY/DRR” A
Conversion Type A (0008, 0064) A WSD A
Reported Values Origin A (3002, 000A) A Not Set. A
RT Image Plane A (3002, 000C) A NORMAL A
X-Ray Image Receptor (3002, 000D) A Not Set. A
Translation A
X-Ray Image Receptor (3002, 000E) A Not Set. A
Angle A
Image Plane Pixel (3002,0011) A Set as per DRR calculator parameters' X and Y
Spacing A resolution Formula: Machine Iso-field size/.512. Iso-
field size is obtained from configuration set at the
time of configuring the system. A
RT Image Position A (3002,0012) A Not Set. A
Radiation Machine (3002,0020) A Machine name for which beam is created A
Name A
Primary Dosimeter Unit A (300A, 00B3) A Not Set. A
Radiation Machine SAD A (3002,0022) A Set as configured for a machine for which beam (DRR)
is created A
Radiation Machine SSD A (3002,0024) A Copied from control point value of the beam A
RT Image SID A (3002,0026) A VSim sets this equal to the Radiation Machine SAD
(3002,0022). A
Source to Reference (3002, 0028) A Not Set. A
Object Distance A
Referenced RT Plan (300C,0002) A RT Plan to which the RT Image belongs A
Sequence A
0.0


> Referenced SOP Class (0008,1150) A SOP Class UID of RT General Plan as defined in DICOM A
UID A
> Referenced SOP (0008,1155) A SOP Instance UID of the Plan to which the RT Image
Instance UID A belongs A
Referenced Beam (300C,0006) A Beam number for which DRR is generated A
Number A
Referenced Fraction (300C, 0022) A Not Set. A
Group Number A
Fraction Number A (3002, 0029) A Not Set. A
Start Cumulative (300C,0008) A 0 A
Meterset Weight A
End Cumulative (300C,0009) A 1 A
Meterset Weight A
Exposure Sequence A (3002,0030) A VSim creates 1 instance of Exposure Sequence

containing the Block Sequence and Beam Limiting
Device Sequence. A
> Referenced Frame (0008, 1160) A Not Set. A
Number A
> KVP A (0018, 0060) A Not Set. A
> X-Ray Tube Current A (0018, 0051) A Not Set. A
> Exposure Time A (0018, 0050) A Not Set A
> Meterset Exposure A (3002, 0032) A Not Set A
> Diaphragm Position A (3002, 0034) A Not Set A
0.0

July 2013

each BLD a SQ exists under a beam. This information
is copied from the corresponding beam. A
>> RT Beam Limiting (300A,00B8) A VSim uses this attribute to store the beam limiting
Device Type A device type. It can be one of: A
ASYMX A
ASYMY A
MLCX A
MLCY A
This information is copied from the corresponding

beam. A
>> Source to Beam (300A,00BA) A VSim uses this attribute to store the source to beam
Limiting Device limiting device distance. A
Distance A
>> Number of Leaf/Jaw (300A,00BC) A VSim stores the number of BLD pairs information for
Pairs A a beam limiting device in this attribute. This
information is copied from the corresponding beam. A
>> Leaf Position (300A,00BE) A VSim uses this attribute to store the leaf position
Boundaries A boundaries ONLY. This information is stored only for
MLC type beam limiting devices. This information is
copied from the corresponding beam. A
each BLD a SQ exists under a beam. This information
is copied from the corresponding beam. A
> Applicator Sequence A (300A, 0107) A Not Set. A
0.0


>> Applicator ID A (300A, 0108) A Not Set. A
>> Applicator Type A (300A, 0109) A Not Set. A
>> Applicator (300A, 010A) A Not Set. A
Description A
> Number of Blocks A (300A, 00F0) A This information is copied from the corresponding
beam. A
> Block Sequence A (300A, 00F4) A This information is copied from the corresponding
beam. A
>> Block Tray ID A (300A,00F5) A Not Set. A
>>Source to Block Tray (300A, 00F6) A This information is copied from the corresponding
Distance A beam. A
>> Block Type A (300A, 00F8) A This information is copied from the corresponding
beam. A
>> Block Divergence A (300A, 00FA) A This information is copied from the corresponding
beam. A
>> Block Number A (300A, 00FC) A This information is copied from the corresponding
beam. A
>> Block Name A (300A, 00FE) A Not Set. A
>> Material ID A (300A, 00E1) A Set to empty. A
>> Block Thickness A (300A, 0100) A VSim always sets the value 0 A
Gantry Angle A (300A, 011E) A This information is copied from the corresponding
beam. A
Beam Limiting Device (300A, 0120) A This information is copied from the corresponding
Angle A beam. A
Patient Support Angle A (300A, 0122) A This information is copied from the corresponding
beam. A
0.0

July 2013

Table Top Eccentric Axis (300A, 0124) A This information is copied from the corresponding
Distance A beam. A
Table Top Eccentric (300A, 0125) A This information is copied from the corresponding
Angle A beam. A
Table Top Vertical (300A, 0128) A This information is copied from the corresponding
Position A beam. A
Table Top Longitudinal (300A, 0129) A This information is copied from the corresponding
Position A beam. A
Table Top Lateral (300A, 012A) A This information is copied from the corresponding
Position A beam. A
0.0

Privatizations A.0
Private Elements for Storage SOP Classes A.0
The following private attributes are defined for all Siemens

syngo based applications: A.0
Registry of DICOM Data Elements A.0
A
Tag Private Owner Code Name VR VM
(0029,xx08) A SIEMENS CSA HEADER A CSA Image Header Type A CS A 1 A
(0029,xx09) A SIEMENS CSA HEADER A CSA Image Header Version A LO A 1 A
(0029,xx10) A SIEMENS CSA HEADER A CSA Image Header Info A OB A 1 A
(0029,xx18) A SIEMENS CSA HEADER A CSA Series Header Type A CS A 1 A
(0029,xx19) A SIEMENS CSA HEADER A CSA Series Header Version A LO A 1 A
(0029,xx20) A SIEMENS CSA HEADER A CSA Series Header Info A OB A 1 A
(0029,xx08) A SIEMENS CSA NON-IMAGE A CSA Data Type A CS A 1 A
(0029,xx09) A SIEMENS CSA NON-IMAGE A CSA Data Version A LO A 1 A
(0029,xx10) A SIEMENS CSA NON-IMAGE A CSA Data Info A OB A 1 A
(0029,xx08) A SIEMENS CSA REPORT A syngo Report Type A CS A 1 A
(0029,xx09) A SIEMENS CSA REPORT A syngo Report A LO A 1 A
(0029,xx15) A SIEMENS CSA REPORT A SR Variant A US A 1 A
(0029,xx17) A SIEMENS CSA REPORT A SC SOP Instance UID A UI A 1 A
(0029,xx10) A SIEMENS CSA ENVELOPE A syngo Report Data A OB A 1 A
(0029,xx11) A SIEMENS CSA ENVELOPE A syngo Report Presentation A OB A 1 A
(0029,xx08) A SIEMENS MEDCOM HEADER A MedCom Header Type A CS A 1 A
(0029,xx09) A SIEMENS MEDCOM HEADER A MedCom Header Version A LO A 1 A
(0029,xx10) A SIEMENS MEDCOM HEADER A MedCom Header Info A OB A 1 A
0.0

July 2013

(0029,xx20) A SIEMENS MEDCOM HEADER A MedCom History Information A OB A 1 A
(0029,xx31) A SIEMENS MEDCOM HEADER A PMTF Information 1 A LO A 1 A
(0029,xx32) A SIEMENS MEDCOM HEADER A PMTF Information 2 A UL A 1 A
(0029,xx34) A SIEMENS MEDCOM HEADER A PMTF Information 4 A CS A 1 A
(0029,xx40) A SIEMENS MEDCOM HEADER A Application Header Sequence A SQ A 1 A
(0029,xx41) A SIEMENS MEDCOM HEADER A Application Header Type A CS A 1 A
(0029,xx42) A SIEMENS MEDCOM HEADER A Application Header ID A LO A 1 A
(0029,xx43) A SIEMENS MEDCOM HEADER A Application Header Version A LO A 1 A
(0029,xx44) A SIEMENS MEDCOM HEADER A Application Header Info A OB A 1 A
(0029,xx50) A SIEMENS MEDCOM HEADER A Workflow Control Flags A LO A 8 A
(0029,xx51) A SIEMENS MEDCOM HEADER A Archive Management Flag Keep CS A 1 A
Online A
(0029,xx52) A SIEMENS MEDCOM HEAD A Archive Management Flag Do Not CS A 1 A
Archive A
(0029,xx53) A SIEMENS MEDCOM HEADER A Image Location Status A CS A 1 A
(0029,xx54) A SIEMENS MEDCOM HEADER A Estimated Retrieve Time A DS A 1 A
(0029,xx55) A SIEMENS MEDCOM HEADER A Data Size of Retrieved Images A DS A 1 A
(0029,xx70) A SIEMENS MEDCOM HEADER A Siemens Link Sequence A SQ A 1 A
(0029,xx71) A SIEMENS MEDCOM HEADER A Referenced Tag A AT A 1 A
(0029,xx72) A SIEMENS MEDCOM HEADER A Referenced Tag Type A CS A 1 A
(0029,xx73) A SIEMENS MEDCOM HEADER A Referenced Value Length A UL A 1 A
(0029,xx74) A SIEMENS MEDCOM HEADER A Referenced Object Device Type A CS A 1 A
(0029,xx75) A SIEMENS MEDCOM HEADER A Referenced Object Device Location A OB A 1 A
0.0


(0029,xx76) A SIEMENS MEDCOM HEADER A Referenced Object ID A OB A 1 A
(0029,xx60) A SIEMENS MEDCOM Series Work Flow Status A LO A 1 A
HEADER2 A
(0029,xx08) A SIEMENS MEDCOM OOG A MEDCOM OOG Type A CS A 1 A
(0029,xx09) A SIEMENS MEDCOM OOG A MEDCOM OOG Version A LO A 1 A
(0029,xx10) A SIEMENS MEDCOM OOG A MEDCOM OOG Info A OB A 1 A
(7FE1,xx10) A SIEMENS CSA NON-IMAGE A CSA Data A OB A 1 A
The next subsections will explain in which IODs these private

data elements are used. A.0
0.0

July 2013
All syngo Supported Image SOP Classes A.0
Extended Image IOD Module A.0
Table A
A
IE Module Reference Usage A Note
Patient A Patient A part3 C.7.1.1 A M A A
Study A General Study A part3 C.7.2.1 A M A A
A Patient Study A part3 C.7.2.2 A U A A
Series A General Series A part3 C.7.3.1 A M A A
Equipment A General Equipment A part3 C.7.5.1 A U A A
Image A General Image A part3 C.7.6.1 A M A A
Image Pixel A part3 C.7.6.3 A M A A
IOD specific part3 C.8.2.1 A M/U A depends on the

modules A IOD A
CSA Image Header A → page A.4–81 A U A A
CSA Series Header A → page A.4–81 A U A A
MEDCOM Header A → page A.4–82 A U A private syngo

information A
MEDCOM OOG A → page A.4–87 A U A if object graphics is

attached to image A
SOP Common A part3 C.12.1 A M A A
A.0
0.0

CSA Image Header Module A The table in this section contains private IOD Attributes that
describe the CSA Image Header. A.0
A
Attribute Name Tag A Private Creator A Type A Notes A
CSA Image Header (0029,xx08) A SIEMENS CSA 1 A CSA Image Header identification
Type A HEADER A characteristics. A
Defined Terms: A
NUM 4 = NUMARIS/4 A
SOM 5 = Somaris/5 A
CSA Image Header (0029,xx09) A SIEMENS CSA 3 A Version of CSA Image Header
Version A HEADER A Info (0029,xx10) format. A
CSA Image Header (0029,xx10) A SIEMENS CSA 3 A Manufacturer Model dependent

Info A HEADER A information. A
CSA Series Header Module A The table in this section contains private IOD Attributes that
describe the CSA Series Header. A.0
A
CSA Series Header (0029,xx18) A SIEMENS CSA 1 A CSA Series Header identification
Type A HEADER A characteristics. A
Defined Terms: A
NUM 4 = NUMARIS/4 A
SOM 5 = Somaris/5 A
CSA Series Header (0029,xx19) A SIEMENS CSA 3 A Version of CSA Series Header
Version A HEADER A Info (0029,xx20) format. A
CSA Series Header (0029,xx20) A SIEMENS CSA 3 A Manufacturer Model dependent

Info A HEADER A information. A
0.0

July 2013
MEDCOM Header Module A The table in this section contains private IOD Attributes that
describe MEDCOM Header. A.0
A
MedCom Header (0029,xx08) A SIEMENS 1C A MedCom Header identification

Type A MEDCOM characteristics. A
HEADER A Defined Terms: A
MEDCOM 1 A
Required if MedCom Header Info

(0029,xx10) present. A
MedCom Header (0029,xx09) A SIEMENS 2C A Version of MedCom Header Info

Version A MEDCOM (0029,xx10) format. A
HEADER A Required if MEDCOM Header

Info (0029,xx10) present. A
MedCom Header (0029,xx10) A SIEMENS 3 A Manufacturer model dependent

Info A MEDCOM information. A
HEADER A The value of the attribute

MedCom Header Info
(0029,xx10) can be build up in
each user defined format. A
MedCom History (0029,xx20) A SIEMENS 3 A MedCom defined Patient

Information A MEDCOM Registration history
HEADER A information. See → page A.4–
87. A
PMTF Information 1 (0029,xx31)

A A SIEMENS 3 A Transformation Information A
MEDCOM
HEADER A

MEDCOM
HEADER A

MEDCOM
HEADER A
0.0

PMTF Information 4 A (0029,xx34) A SIEMENS 3 A Transformation Information A
MEDCOM
HEADER A
Application Header (0029,xx40) A SIEMENS 3 A Sequence of Application Header

Sequence A MEDCOM Items. A
HEADER A Zero or more Items shall be

included in this sequence. A
Encoded as a sequence of items. A
> Application (0029,xx41) A SIEMENS 1C A Application Header

Header Type A MEDCOM identification characteristics. A
HEADER A Required if Sequence is sent. A
> Application (0029,xx42) A SIEMENS 3 A Identification of an application

Header ID A MEDCOM header. A
HEADER A
> Application (0029,xx43) A SIEMENS 3 A Version of Application Header

Header Version A MEDCOM Info (0029,xx43) format. A
HEADER A
> Application (0029,xx44) A SIEMENS 3 A Application dependent

Header Info A MEDCOM information. A
HEADER A
Workflow Control (0029,xx50) A SIEMENS 3 A Eight free definable flags. A
Flags A MEDCOM
HEADER A
Archive (0029,xx51) A SIEMENS 3 A Flag to control remote archive

Management Flag MEDCOM management system to keep
Keep Online A HEADER A the image always online (also
when already archived). A
Enumerated Values: 00 =
remote control not required, 01
= keep image online. A
0.0

July 2013
Archive (0029,xx52) A SIEMENS 3 A Flag to control remote archive

Management Flag MEDCOM management system not to
Do Not Archive A
HEADER A archive the related image. A
Enumerated Values: 00 =
remote control not required, 01
= don’t archive image. A
Image Location (0029,xx53) A SIEMENS 3 A Image location status to control

Status A MEDCOM retrieving. A
HEADER A Defined Terms: ONLINE =

retrieving has to be done as
usual, NEARLINE = move request
to SCP and delay according to
value of Estimated Retrieve Time
(0029,xx54), OFFLINE =
invoking a retrieve operation
initiates an operator request,
INVALID = invoking a retrieve
operation would always result in
an error. A
Estimated Retrieve (0029,xx54) A SIEMENS 3 A Estimated retrieve time in

Time A MEDCOM seconds. A value less then zero
HEADER A (< 0) indicates location is
OFFLINE or INVALID. A
Data Size of (0029,xx55) A SIEMENS 3 A Data size of images in MByte. A
Retrieved Images A MEDCOM

HEADER A
Siemens Link (0029,xx70) A SIEMENS 3 A Sequence of Link items. Each

Sequence A MEDCOM item identifies the location of
HEADER A one missing tag. One or more
items can be located in this
sequence. A
Referenced Tag A (0029,xx71) A SIEMENS 1 A The referenced tag. The value of

MEDCOM this tag is in the Child Data
HEADER A Object (CDO). Currently it is
always Pixel Data (7FE0,0010). A
0.0

Referenced Tag Type A (0029,xx72) A SIEMENS 1 A The value representation (type)

MEDCOM of the missing tag (e.g. OW).
HEADER A Enumerated values are all
DICOM defined Value
Representations. A
Referenced Value (0029,xx73) A SIEMENS 1 A The length of the referenced tag

Length A MEDCOM value in bytes. A
HEADER A
Referenced Object (0029,xx74) A SIEMENS 1 A The Device Type that stores the
Device Type A MEDCOM Child Data Object (CDO) with
HEADER A the referenced tag value.
Currently it should be "SHMEM".
In future, "SDM", "LOID" or "FILE"
are also imaginable. Defined
Terms are SHMEM = Shared
Memory SDM = Series Data
Management LOID = Database
FILE A
Referenced Object (0029,xx75) A SIEMENS 2 A The Location of the device that

Device Location A MEDCOM stores the Child Data Object
HEADER A (CDO) with the referenced tag
value. For the "SHMEM" case, it
is the shared memory directory.
Can be empty, then the default
directory will be taken. In
future, for "SDM" this will be the
SDM_ID, for FILE it will be the
directory name and for "LOID" it
will be the database name. A
0.0

July 2013
Referenced Object (0029,xx76) A SIEMENS 1 A

The ID of the object that
ID A MEDCOM contains the Child Data Object
HEADER A
(CDO) with the referenced tag
value. In case of "SHMEM", it is
the shared memory ID. In
future, for "SDM" this will be a
Sirius OID, for "FILE" the file
name, for "DB" the LOID. A
Series Work Flow (0029,xx60) A SIEMENS 3 A syngo Patient Browser specific

Status A MEDCOM flags used for clinical work:
HEADER A - com = completed
- rea = read
- ver = verified A
0.0

MEDCOM History Information A.0
The value of the attribute MEDCOM History Information

(0029,xx20) is defined in the following way: A.0
A
Part Name Type Bytes Notes
header A Identifier A string A 32 A always "CSA HISTORY" A
A Version A string A 32 A e.g. "V1.10" A
n items A Class Name A string A 64 A A
A Modification string A 1024 A A
String A
MEDCOM OOG Module A The table in this section contains private IOD Attributes that
describe MEDCOM Object Oriented Graphics (OOG). This mod-
ule is used when object graphics is drawn on the image and
need to be stored as graphic object properties (Line, Circle, Rect-
angle, Arrow, and so on). iven the condition that the module
contents was not removed by other modalities, the graphic
objects remain re-animatable if such an image was transferred
and is then retrieved back. A.0
A
MedCom OOG (0029,xx08) A SIEMENS MEDCOM 1 A MEDCOM Object Oriented

Type A OOG A Graphics (OOG) identification
characteristics. A
Defined Terms: A
MEDCOM OOG 1 A
MedCom OOG (0029,xx09) A SIEMENS MEDCOM 3 A Version of MEDCOM OOG Info

Version A OOG A (0029,xx10) format. A
MedCom OOG (0029,xx10) A SIEMENS MEDCOM 3 A MEDCOM Object Oriented

Info A OOG A Graphics (OOG) data. A
0.0

July 2013
The graphics objects are also stored in one Image overlay plane
for compatibility with other products, which don’t support the
MedCom OOG module. Any system which does not support this
MedCom OOG module has to remove these private attributes
when modifying the image overlay plane content. A.0
syngo Report Data A The module contains private IOD Attributes that describe syngo
reports. This module is used when syngo report data are added
to DICOM SR and DICOM SC objects. A.0
Attribute Name Tag Private Creator Type Notes

syngo Report Type A (0029,xx08 SIEMENS CSA 1 A syngo report characteristics,
) A REPORT A e.g. report creating application. A
Defined Terms: A
CT_CASCORING A
CT_CIRCULATION A
CT_LUNGCARE A
INSPACE A
MR_ARGUS A
This attribute value will be used

to identify the corresponding
application during generic
extension dll management. A
restricted character set is used: A
only A-Z and underscore are

supported. A
syngo Report (0029,xx09 SIEMENS CSA 3 A Version of syngo Report Data

Version A ) A REPORT A (0029,xx10) format. A
syngo Report (0029,xx10 SIEMENS CSA 3 A Application specific report

Data A ) A ENVELOPE A related data A
syngo Report (0029,xx11 SIEMENS CSA 3 A Application specific report

Presentation A ) A ENVELOPE A related data A
0.0

Attribute Name Tag Private Creator Type Notes

SR Variant A (0029,xx15 SIEMENS CSA A DICOM SR Variant. A
) A REPORT A Enumerated Values: A
0 = Basic Text SR A
(1.2.840.1008.5.1.4.1.1.88.11
) A
1 = Enhanced SR A
(1.2.840.1008.5.1.4.1.1.88.22
) A
2 = Comprehensive SR A
(1.2.840.1008.5.1.4.1.1.88.33
) A
3 = Mammography CAD SR A
(1.2.840.1008.5.1.4.1.1.88.50
) A
4 = Key Object Selection

Document A
(1.2.840.1008.5.1.4.1.1.88.59
) A
5 = Chest CAD SR A
(1.2.840.1008.5.1.4.1.1.88.65
) A
SC SOP Instance (0029,xx17 SIEMENS CSA 3 A DICOM SOP Instance UID of

UID A ) A REPORT A syngo based SC image
representing the syngo report
object. A
This UID will be used to identify

the Resulting SC object after SR
to SC conversion. A
0.0

July 2013
Private Elements for CT Image Storage SOP

Classes A.0
The following private attributes are defined by Somaris/5. A.0
Registry of DICOM Data Elements A.0
Tag Private Owner Code Name A VR A VM A Notes A

A
(0019,xx90) A SIEMENS CT VA0 COAD A Osteo Offset A DS A 1 A Offset of the water

equivalent material
of the Siemens
Osteo phantom to
real water A
(0019,xx92) A SIEMENS CT VA0 COAD A Osteo Regression Line DS A 1 A Slope of the

Slope A regression line for
the ESP (=European
Spine Phantom)
standardization A
(0019,xx93) A SIEMENS CT VA0 COAD A Osteo Regression Line DS A 1 A Intercept of the

Intercept A regression line for
the ESP (= European
Spine Phantom)
standardization A
(0019,xx96) A SIEMENS CT VA0 COAD A Osteo Phantom IS A 1 A Number of the

Number A Siemens Osteo
phantom A
(0019,xxB0) A SIEMENS CT VA0 COAD A Feed per Rotation A DS A 1 A Som/4 style Feed per
Rotation (Backwards
Compatibility) A
(0019,xxBD) A SIEMENS CT VA0 COAD A Pulmo Trigger Level A IS A 1 A Spirometer trigger

level used for the
scan, given in
percent of VC (= Vital
Capacity) of the
patient A
0.0

Tag Private Owner Code Name A VR A VM A Notes A
(0019,xxBE) A SIEMENS CT VA0 COAD A Expiratoric Reserve DS A 1 A ERV (= Exspiratoric

Volume A Reserve Volume)
achieved by the
patient A
(0019,xxBF) A SIEMENS CT VA0 COAD A Vital Capacity A DS A 1 A VC (= Vital Capacity)

achieved by the
patient A
(0019,xxC0) A SIEMENS CT VA0 COAD A Pulmo Water A DS A 1 A Density of the water

insert of the Siemens
Pulmo phantom A
(0019,xxC1) A SIEMENS CT VA0 COAD A Pulmo Air A DS A 1 A Density of the air

holes of the Siemens
Pulmo phantom A
(0019,xxC2) A SIEMENS CT VA0 COAD A Pulmo Date A DA A 1 A Date of the

evaluation of the
Siemens Pulmo
phantom A
(0019,xxC3) A SIEMENS CT VA0 COAD A Pulmo Time A TM A 1 A Time of the

evaluation of the
Siemens Pulmo
phantom A
(0021xx11) A SIEMENS MED A Target A DS A 2 A Som/4 style Target

(Backwards
Compatibility) A
A A A A A A
(0009,00xx) A SIEMENS CT VA1 Private Creator Data LO A 1 A 1 A
DUMMY A Element A
0.0

July 2013
Private SOP class CSA Non-Image A.0
This chapter includes the definition of the Siemens AG B Med

CSA defined private Non-Image Object (called CsaNonImage
IOD). The focus of this private Non-Image Object is to address
the requirement for non-image data sets found in syngo based
applications. A.0
The MedCom Non-Image Information Object Definition speci-

fies data sets that are converted from a non-DICOM format to a
modality independent DICOM format. A.0
Examples of such manufacturer model dependent data sets are: A.0
❏ Raw Data
❏ CT Admin Data
❏ MR Spectroscopy Data
❏ etc.
CSA Non-Image IOD Entity Relationship Model A.0
The E-R model in [DICOM] A.1.2 depicts those components of

the DICOM Information Model which directly refer to the CSA
Non-Image IOD. The frame of reference IE, overlay IE, modality
look up table IE, VOI lookup table IE and curve IE are not compo-
nents of the CSA Non-Image IOD. A.0
0.0

0-n
CSA Non-
Image IOD
0.0

July 2013
CSA Non-Image IOD Module Table A.0
A
IE Module Reference Usage
Patient A Patient A part 3 C.7.1.1 A M A
Study A General Study A part 3 C.7.2.1 A M A
A Patient Study A part 3 C.7.2.2 A U A
Series A General Series A part 3 C.7.3.1 A M A
Equipment A General Equipment A part 3 C.7.5.1 A U A
CSA A CSA Image Header A → page A.4–81 A U A
CSA Series Header A → page A.4–81 A U A
MEDCOM Header A → page A.4–82 A U A
MEDCOM OOG A → page A.4–87 A U A
CSA Non-Image A → page A.4–95 A M A
SOP Common A part 3 C.12.1 A M A
0.0

CSA Non-Image Module A.0
The table in this section contains private IOD Attributes that

describe CSA Non-Images. A.0
A
Attribute Name Tag A Private Type A Notes A
Creator A
Image Type A (0008,0008) A - A 3 A Image identification characteristics.

See → page A.4–98 A
Acquisition Date A (0008,0022) A - A 3 A The date the acquisition of data that

resulted in this data set started. A
Acquisition Time A (0008,0032) A - A 3 A The time the acquisition of data

that resulted in this data set started. A
Conversion Type A (0008,0064) A - A 3 A Describes the kind of image

conversion. A
Defined Terms: DV = Digitized

Video, DI = Digital Interface, DF =
Digitized Film, WSD = Workstation. A
Referenced Image (0008,1140) A - A 3 A A sequence which provides

Sequence A reference to a set of Image SOP
Class/Instance identifying other
images significantly related to this
data set. A
Encoded as sequence of items:

(0008,1150) and (0008,1155). A
Derivation (0008,2111) A - A 3 A A text description of how this data

Description A set was derived. A
Source Image (0008,2112) A - A 3 A A Sequence which identifies the set

Sequence A of Image SOP Class/Instance pairs of
the Images which were used to
derive this data set. A
Zero or more Items may be included

in this Sequence. A
Encoded as sequence of items:

(0008,1150) and (0008,1155). A
0.0

July 2013
Creator A
Patient Position A (0018,5100) A - A 3 A Patient position descriptor relative

to the equipment. A
Acquisition (0020,0012) A - A 3 A A number identifying the gathering

Number A of data over a period of time which
resulted in this data set. A
Instance Number A (0020,0013) A - A 3 A A number that identifies this data

set. A
Frame of (0020,0052) A - A 3 A Uniquely identifies the frame of

Reference UID A reference for a Series. A
Image Comments A (0020,4000) A - A 3 A User-defined comments about the

image. A
Quality Control (0028,0300) A - A 3 A Indicates whether or not this image

Image A is a quality control or phantom
image. A
If this Attribute is absent, then the

image may or may not be a quality
control or phantom image. A
Enumerated Values: YES, NO. A
Burned In (0028,0301) A - A 3 A Indicates whether or not image

Annotation A contains sufficient burned in
annotation to identify the patient
and date the image was acquired. A
If this Attribute is absent, then the

image may or may not contain
burned in annotation. A
Enumerated Values: YES, NO. A
Lossy Image (0028,2110) A - A 3 A Specifies whether an Image has

Compression A undergone lossy compression. A
Enumerated Values: 00 = Image has

NOT been subjected to lossy
compression, 01 = Image has been
subjected to lossy compression. A
0.0

Creator A
Lossy Image (0028,2112) A - A 3 A Describes the approximate lossy

CompressionRatio A compression ratio(s) that have been
applied to this image. A
May be multi valued if successive

lossy compression steps have been
applied. A
CSA Data Type A (0029,xx08) A SIEMENS CSA 1 A CSA Data identification

NON-IMAGE A characteristics. A
Defined Terms: A
RAW DATA NUM 4 = NUMARIS/4 Raw

Data A
SPEC NUM 4 = NUMARIS/4

Spectroscopy A
RAW DATA SOM 5 = Somaris/5 Raw

Data A
RAW DATA SOM 7 = Somaris/5 Raw

Data A
BSR REPORT = BSR Study Report

Data A
COL REPORT SOM5 =

syngo Colonography Report Data A
CSA Data Version A (0029,xx09) A SIEMENS CSA 3 A Version of CSA Data Info
NON-IMAGE A (0029,xx10) format and CSA Non-
Image Data (7FE1,xx10) format. A
CSA Data Info A (0029,xx10) A SIEMENS CSA 3 A Information to describe the CSA
NON-IMAGE A Data (7FE1,xx10). A
The value of the attribute CSA Data

Info (0029,xx10) can be build up in
each user defined format. A
CSA Data A (7FE1,xx10) A SIEMENS CSA 1 A Binary data as byte stream. A
NON-IMAGE A
0.0

July 2013
CT Extensions of the Somaris/5 uses the following defined term for Image Type
Non-Image Object A (0008,0008): A.0
❏ Value 1: ORIGINAL
❏ Value 2: PRIMARY
❏ Value 3: AXIAL, LOCALIZER, OTHER
❏ Value4: a CT_SOM5 * enumeration
❏ Value5: Somaris/5 specific enumeration
The following table lists the Somaris/5 non-image types and the
corresponding combinations of the Image Type Attribute val-
ues. A.0
A
Description A 0008,0008 A 0008,0008 A 0008,0008 A 0008,0008 A 0008,0008 A
Value 1 A Value 2 A Value 3 A Value 4 A Value 5 A
CAD Results A DERIVED A SECONDARY A OTHER A CAD MARKS A none A
Colonography DERIVED A SECONDARY A OTHER A CT_SOM5 none A
Data A COL A
Coronary Tree A DERIVED A SECONDARY A OTHER A CT_CIRCULA none A
TION A
Raw Data A Same entries as for images A
A.0
Private SOP Classes A.0

A
CSA Non-Image A 1.3.12.2.1107.5.9.1 A
A.0
Private Transfer Syntaxes A.0
Not applicable. A.0
A.0
0.0

CHAPTER
A.5 Configuration A.0
AE Title / Presentation Address

Mapping A.0
To ensure unique identification the hostname should be part of

the AE Titles (see examples below, hostname = station4). The
string can be up to 16 characters long and must not contain any
extended characters, only 7 bit ASCII characters (excluding con-
trol characters) are allowed according to DICOM standard. An
example name is HRI_station4. Another common setting is the
use of the hostname in capital letters, e.g. "STATION4". A.0
A.0
Note
The current implementation does not support the full
DICOM standard syntax. Spaces and special characters (like
&<>") in the AE title string are not supported. A
DICOM Verification A.0
The Verification Service uses the AE configuration of the DICOM

Service that is checked with the C-ECHO message. E.g. Verifica-
tion will use the Storage AE, if initiated to check the configura-
tion of a remote DICOM node. A.0
DICOM Storage/StorageCommitment/QR AE
Title A.0
There is a common AE Title for Storage, Storage Commitment

and Query/Retrieve. It can be configured via Service UI in Con-
figuration/DICOM/General. A.0
The port is set to the fixed value of 104. A.0
0.0

July 2013
Network – Configuration DICOM Conformance Statement
DICOM Modality Worklist and MPPS AE Title A.0
There is a common AE Title for Modality Worklist and MPPS. It

can be configured via Service UI in Configuration/DICOM/Gen-
eral. A.0
DICOM Print AE Title A.0
There is a separate AE Title for Print application. It can be config-

ured via Service UI in Configuration/DICOM/General. A.0
No input of AETs starting with a numeric character is possible. A.0
Remote AE Titles and Presentation Addresses A.0
Remote AETs, host names, IP addresses and port numbers can

be configured using the Service application. For each AET a list
of supported services can be configured. A.0
0.0

DICOM Conformance Statement Network – Configuration
Configurable Parameters A.0
Storage, Storage Commitment and Query/

Retrieve A.0
The Service Configuration Tool can be used to set the AETs, port
numbers, host names, IP addresses and capabilities for the
remote nodes’ (SCP’s). The user can select transfer syntaxes,
compression types and query models for each SCP separately. A.0
❏ If the C-STORE is initiated by a user, only the transfer syntax

will be proposed that is configured via Options -> Transfer ->
Network Nodes (No Compression, Lossless JPEG, Lossy JPEG).
The default transfer syntax (ILE) will be proposed in any case.
❏ If the C-STORE is initiated by an autotransfer rule or by the C-
MOVE SCP all transfer syntaxes that are configured in the Ser-
vice UI for this particular network destination will be pro-
posed. (Compressed Transfer Syntaxes will be proposed first
followed by the uncompressed Transfer Syntaxes).
Additional configurable parameters for Storage Commit-
ment are: A.0
When acting as SCU: A.0
❏ Flag to indicate whether the association will be kept open to

receive the response or to close the association and be pre-
pared to receive the response on another association.
❏ Time-out which defines how long the association of N-
ACTION is kept to receive a N-EVENT-REPORT on the same
association. The same value is used to wait for a N-EVENT-
REPORT on another association (applicability of transaction
UID).
(default 1 h)
When acting as SCP: A.0
flag to indicate whether an archive system is installed. A.0
0.0

July 2013
Print A.0
The Service application can be used to configure the SCP

(DICOM Printer). A.0
These parameters are mandatory to be set: A.0
❏ AET
❏ Host name
❏ IP address
❏ Port number
❏ These parameters have defaults as per configuration file and
can be changed:
❏ Default camera
❏ Pixel size
❏ Additional or changed film sheet formats (e.g. inch 14x14,
inch 14x17, ...)
❏ List with mapping pixel size to each film sheet format
❏ Minimal density
❏ Stored printed film jobs
❏ Media type
❏ Film destination
0.0

DICOM Conformance Statement Network – Configuration
Modality Worklist A.0
The Service application can be used to set the AETs, port num-
bers, host names, IP addresses, capabilities, and time-outs for
the remote nodes (SCPs). A.0
Additional configurable parameters for Basic Worklist Query are:

A.0
❏ Query Waiting time - the time to wait for the C-FIND-RSP after
sending the C-FIND-RQ (default 20 s)
❏ Max. Query Match Number - the maximum number of entries
accepted in one worklist (default is 200)
❏ Query Interval - the time between two C-FIND-RQs to the
Hospital Information System (default is 60 min)
❏ Broad Worklist Query behaviour: two values are defined:
Set the AE Title search attribute to the own AE Title, and the
Modality search attribute to "*".
Set the Modality search attribute to the own modality and the
AE Title search attribute to "*".
The sending of an empty Specific Character Set in a C-FIND-RQ
can be omitted by configuration. However, this is not available
in the Service application but must be set by a Siemens service
technician. A.0
Modality Performed Procedure Step A.0
The Service application can be used to configure the Modality

Worklist SCP to be a Modality Performed Procedure Step SCP
also. A.0
Additional configurable parameters for Modality Performed Pro-

cedure Step are: A.0
❏ Default Catalog Name - (0008,0102) used for items entered

in MPPS UI
❏ Default Catalog Version - (0008,0103) used for items
entered in MPPS UI
0.0

July 2013
Default Parameters A.0
This configuration tool also uses some default parameters: A.0
❏ maximal PDU size set to 262144 Bytes

❏ time-out for accepting/rejecting an association request: 60 s
❏ time-out for responding to an association open/close
request: 60 s
❏ time-out for accepting a message over network: 60 s
❏ time-out for waiting for data between TCP/IP-packets: 60 s
A.0
The Time-outs for waiting for a Request/Response message from

the remote node are as follows: A.0
❏ for Storage SCP/SCU: 600 s

❏ for Storage Commitment SCU:
time-out for Response to N-ACTION: 600 s
time-out for N-EVENT-REPORT: configurable, see → page
A.5–3, Configurable Parameters.
❏ for Query/Retrieve SCP/SCU: 600 s
❏ for Modality Worklist SCU: configurable, see → page A.5–3,
Configurable Parameters.
❏ for Print Management SCU:
time-out for Response to N-SET-RQ: 240 s
time-out for Response to other Requests: 60 s
A.0
A.0
0.0

CHAPTER Support of Extended
A.6 Character Sets A.0
The Somaris/5 DICOM application supports the following char-

acter sets as defined in the three tables below: A.0
A.0
Single-Byte Character Sets without Code Extension A
Character Set Descrip- Defined Term ISO registration Character Set

tion number
Default repertoire A none A ISO_IR 6 A ISO 646: A
Latin alphabet No. 1 A ISO_IR 100 A ISO_IR 100 A Supplementary set A
ISO_IR 6 A ISO 646: A
ISO_IR 6 A ISO 646 A
Cyrillic A ISO_IR 144 A ISO_IR 144 A Supplementary set A
Arabic A ISO_IR 127 A ISO_IR 127 A Supplementary set A
Greek A ISO_IR 126 A ISO_IR 126 A Supplementary set A
Hebrew A ISO_IR 138 A ISO_IR 138 A Supplementary set A
0.0

July 2013
Network – Support of Extended Character Sets DICOM Conformance Statement

tion number
Japanese A ISO_IR 13 A ISO_IR 13 A JIS X 0201: Katakana A
ISO_IR 14 A JIS X 0201: Romaji A
A.0
A.0
Single-Byte Character Sets with Code Extension A
Character Defined Term Standard ESC se- ISO registra- Character Set
Set Descrip- for Code Ex- quence tion number
tion tension
Default ISO 2022 IR 6 A ISO 2022 A ESC 02/08 ISO-IR 6 A ISO 646 A
repertoire A 04/02 A
Latin ISO 2022 IR 100 A ISO 2022 A ESC 02/13 ISO-IR 100 A Supplementary set A
alphabet 04/01 A
No.1 A
ISO 2022 A ESC 02/08 ISO-IR 6 A ISO 646 A
04/02 A
alphabet 04/02 A
No.2 A
04/02 A
alphabet 04/03 A
No.3 A
04/02 A
0.0

DICOM Conformance Statement Network – Support of Extended Character Sets
tion tension
alphabet 04/04 A
No.4 A
04/02 A
Cyrillic A ISO 2022 IR 144 A ISO 2022 A ESC 02/13 ISO-IR 144 A Supplementary set A
04/12 A
04/02 A
Arabic A ISO 2022 IR 127 A ISO 2022 A ESC 02/13 ISO-IR 127 A Supplementary set A
04/07 A
Greek A ISO 2022 IR 126 A ISO 2022 A ESC 02/13 ISO-IR 126 A Supplementary set A
04/06 A
A ISO 2022 A ESC 02/08 ISO-IR 6 A ISO 646 A
04/02 A
Hebrew A ISO 2022 IR 138 A ISO 2022 A ESC 02/13 ISO-IR 138 A Supplementary set A
04/08 A
04/02 A
alphabet 04/13 A
No.5 A
04/02 A
0.0

July 2013
tion tension
Japanese A ISO 2022 IR 13 A ISO 2022 A ESC 02/13 ISO-IR 13 A JIS X 0201:
04/09 A Katakana A
ISO 2022 A ESC 02/13 ISO-IR 14 A JIS X 0201-1976:

04/10 A Romaji A
A.0
A.0
Multi-Byte Character Sets without Code Extension A.0
Character Set Defined Term A.0 ISO registration Character Set A.0
Description A.0 number A.0
Unicode A ISO_IR 192 A ISO 10646 A Unicode in UTF-8 A
Chinese A GB18030 A GB18030 A GB 18030-2000

(China Association for
Standardization) A
0.0

DICOM Conformance Statement Network – Support of Extended Character Sets
Multi-Byte Character Sets with Code Extension A
Character Defined Term Standard ESC se- ISO regis- Character Set
Set Descrip- for Code Ex- quence tration
tion tension number
Japanese A ISO 2022 IR 87 A ISO 2022 A ESC 02/04 ISO-IR 87 A JIS X 0208: Kanji A
04/02 A
A ISO 2022 IR 159 A ISO 2022 A ESC 02/04 ISO-IR 159 A JIS X 0212:
02/08 04/ Supplementary
04 A Kanji set A
Chinesea A ISO 2022 IR 58 A ISO 2022 A ESC 02/04 ISO-IR 58 A GB2312-80

04/01 A (China Association
for Standardization) A
a. This Character Set is an extension of DICOM for the Chinese language.
When there is a mismatch between the SCS tags (0008,0005)

and the characters in an IOD received by the system, then the
following measures are taken to make the characters DICOM
conform: A.0
❏ Try to import with ISO_IR 100. If ISO_IR 100 fails, convert

each illegal character to a ’?’.
❏ There are now three categories of character sets which have
to be differentiated because of their different encoding for-
mats:
❏ Conventional ISO character sets: ISO_IR 6, ISO 2022 IR 6,
ISO_IR 100, etc.
encoded in ISO 2022
❏ ISO_IR 192 encoded in UTF-8
❏ GB18030 encoded in GB18030
0.0

July 2013
It is not possible to recognize the following mismatches auto-

matically on receiving or importing: A.0
❏ An attribute value is encoded in ISO_IR 192(0008,0005)

contains a conventional ISO character set as primary
character set
❏ An attribute value is encoded in GB18030(0008,0005)
contains a conventional ISO character set as primary
character set
❏ An attribute value is encoded in ISO 2022 (0008,0005)
contains ISO_IR 192
❏ An attribute value is encoded in ISO 2022(0008,0005)
contains GB18030
An IOD that contains one of the above mentioned inconsisten-

cies is not DICOM conform. As these kinds of inconsistencies
cannot be recognized by the system, the IOD will not be rejected
but the character data might be corrupted. A.0
Older versions of syngo do not support the newly introduced

character sets ISO_IR 192 and GB18030 and their special encod-
ings. That means, an IOD which contains one of these new char-
acter sets in (0008,0005) will be rejected by an older syngo sys-
tem. A.0
0.0

PART DICOM
B Conformance Statement
Media Storage
This part contains the Conformance Statement to all "Offline
Media Application Profiles (incl. private extensions)" supported
by the Somaris/5 archive options. A.0
The application profiles supported shall be: A.0
❏ Standard Application Profiles

❏ Augmented Application Profiles
❏ syngo private Application Profiles
A.0
For general introductory topics see → Page –5, Introduction. A.0
A.0
0.0
Version syngo CT 2014A B-1

July 2013
Media Storage DICOM Conformance Statement
0.0
B-2 DICOM Conformance Statement syngo

CHAPTER
B.1 Implementation Model A.0
Browse
Directory Arch. DB A.0
Information A.0
A.0
Import into FSC
local
storage
DICOM FSR
A.0
CD-R/DVD A.0
Export to Archive FSU

A.0
local
archive
A.0
media
A.0
The DICOM archive application will serve as an interface to the

CD-R/DVD off-line medium device. It serves interfaces to include
the off-line media directory into the browser and to copy SOP
instances to a medium or retrieve SOP Instances from medium
into local storage. A.0
The DICOM Archive application will support 120 mm CD-R and

DVD-R (see Table → page B.2–1). A.0
The FSU role will update new SOP Instances only to media with
pre-existing File-sets conforming to the Application Profiles sup-
ported. A.0
The contents of the DICOMDIR will be temporarily stored in

Archive-Database. A.0
0.0
Version syngo CT 2014A B.1-1

July 2013
Media Storage – Implementation Model DICOM Conformance Statement
Functional definitions of AE’s A.0
The Somaris/5 DICOM off-line media storage application con-

sists of the DICOM Archive application entity serving all inter-
faces to access off-line media. The DICOM Archive application is
capable of A.0
✧ creating a new File-set onto an unwritten medium

(Export to...)
✧ updating an existing File-set by writing new SOP Instances
onto the medium
✧ importing SOP Instances from the medium onto local storage
✧ reading the File-set’s DICOMDIR information temporarily into
database and pass it to display applications.
0.0
B.1-2 DICOM Conformance Statement syngo

DICOM Conformance Statement Media Storage – Implementation Model
The DICOM Archive application will not perform updates before

the Directory information of the DICOMDIR is completely read.A.0
When performing updates, the SOP instances are checked for

existence before updating. Duplicate instances will be avoided.
A.0
0.0

July 2013
Media Storage – Implementation Model DICOM Conformance Statement
File Meta Information Options A.0
The Implementation Class UID is: A.0
❏ “1.3.12.2.1107.5.1.4”
❏ "SIEMENS_S5VB42A"
0.0

CHAPTER Application Entity
B.2 Specifications A.0
DICOM Archive Specification A.0
The DICOM Archive provides Standard conformance to Media

Storage Service Class (Interchange Option). A.0
A
Application Profiles Supported Real World Activity Role SC Option
PRI-SYNGO-CD A Browse Directory Information A FSR A Interchange A
PRI-SYNGO-DVD A
Import into local Storage A FSR A Interchange A
AUG-GEN-CD A
AUG-CTMR-CDa A Export to local archive media A FSC,FSU A Interchange A
STD-XA1K-CDa A
STD-GEN-CD A Browse Directory Information A FSR A Interchange A
STD-CTMR-CD A
Import into local Storage A FSR A Interchange A
STD-XABC-CD A
STD-XAIK-CD A
TD-US-zz-yF-xxxxxxb A
a. With no private SOP Class used, the PRI-SYNGO-CD profile definitions are appropriate to de-
scribe the augmentation of the related -STD Profiles.
b. All combinations of the following values for zz, yF and xxxxxx are suported:
’yF’ can take two values: SF for Single Frame and MF for Multi Frame.
’zz’ can take three values: ID (Image Display), SC (Spatial Calibration) and CC (Combined Calibration)
xxxxxx can take 2 values: CDR and DVD
On syngo-based products the Private Extended syngo Profile (e.g. PRI-SYNGO-CD) will be preferra-
bly used by the system. The General Purpose Interchange Profile (STD-GEN-CD), Ultrasound Profile
(STD-US-xxx), CT and MR Image Profile (STD-CTMR-xxx), Waveform Interchange (STD-WVFM-xxx),
Basic Cardiac Profile (STD-XABC-CD) and 1024 X-Ray Angiographic Profile (STD-XA1K-CD) will be
supported with read capability of the related media.
0.0

July 2013
Media Storage – Application Entity Specifications DICOM Conformance Statement
File Meta Information for the Application

Entity A.0
The Source Application Entity Title is set by configuration. See →

Chapter B.5, Configuration for details. A.0
Real-World Activities for this Application

Entity A.0
Real-World Activity: Browse Directory Information A.0
The DICOM Archive application acts as FSR using the inter-

change option when requested to read the media directory. A.0
The DICOM archive application will read the DICOMDIR and

insert that directory entries, that are valid for the application
profiles supported, into a local database. The database can then
be used for browsing media contents. A.0
Note
Icon Image SQ is also supported in DICOMDIR. But only
those Icon Images with Bits Allocated (0028,0100) equal to
8 and size 64 by 64 or 128 by 128 pixels are imported into
database and are visible in PatientBrowser. A
Application Profiles for the See table → page B.2–1 for the Application Profiles listed that
RWA: Browse Directory invoke this Application Entity for the Browse Directory Informa-
Information A tion RWA. A.0
0.0

DICOM Conformance Statement Media Storage – Application Entity Specifications
Real-World Activity: Import into local Storage A.0
The DICOM Archive application acts as FSR using the inter-

change option when requested to read SOP Instances from the
medium into the local storage. A.0
The SOP Instance selected from the media directory will be cop-
ied into the local storage. Only SOP Instances, that are valid for
the application profile supported and are listed as supported by
the Storage SCP Conformance section (→ page A.2–4), can be
retrieved from media storage. This is due to the fact that the
Browse Directory Information will filter all SOP Instances not
matching the Application profiles supported. A.0
During operation no "Attribute Value Precedence" is applied to

the SOP Instances. Detached Patient Management is not sup-
ported (please refer to DICOM part 11, Media Storage Applica-
tion Profiles). A.0
For media conforming to the STD-GEN-CD Profile the following

SOP classes will be supported as a FSR: A.0
A
Information Object Definitions SOP Class UID A Transfer Syntax and UID A
CR Image A 1.2.840.10008.5.1.4.1.1.1 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
DX Image - For Presentation A 1.2.840.10008.5.1.4.1.1.1.1 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
DX Image - For Processing A 1.2.840.10008.5.1.4.1.1.1.1.1 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
MG Image - For Presentation A 1.2.840.10008.5.1.4.1.1.1.2 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
MG Image - For Processing A 1.2.840.10008.5.1.4.1.1.1.2.1 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
0.0

July 2013
IOX Image - For Presentation A 1.2.840.10008.5.1.4.1.1.1.3 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
IOX Image - For Processing A 1.2.840.10008.5.1.4.1.1.1.3.1 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
CT Image A 1.2.840.10008.5.1.4.1.1.2 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
US-MF image (retired) A 1.2.840.10008.5.1.4.1.1.3 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
US-MF image A 1.2.840.10008.5.1.4.1.1.3.1 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
MR Image A 1.2.840.10008.5.1.4.1.1.4 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
US Image (retired) A 1.2.840.10008.5.1.4.1.1.6 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
US Image A 1.2.840.10008.5.1.4.1.1.6.1 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
SC Image A 1.2.840.10008.5.1.4.1.1.7 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
12-lead ECG Waveform Storage A 1.2.840.10008.5.1.4.1.1.9.1.1 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
0.0

General ECG Waveform Storage A 1.2.840.10008.5.1.4.1.1.9.1.2 A Explicit VR Little Endian

A Uncompressed
1.2.840.10008.1.2.1 A
Ambulatory ECG Wave-form 1.2.840.10008.5.1.4.1.1.9.1.3 A Explicit VR Little Endian

Storage A A Uncompressed
1.2.840.10008.1.2.1 A
Hemodynamic Waveform 1.2.840.10008.5.1.4.1.1.9.2.1 A Explicit VR Little Endian

1.2.840.10008.1.2.1 A
Cardiac Elec-trophysiology 1.2.840.10008.5.1.4.1.1.9.3.1 A Explicit VR Little Endian

Waveform Storage A A Uncompressed
1.2.840.10008.1.2.1 A
Basic Voice Audio Wave-form 1.2.840.10008.5.1.4.1.1.9.4.1 A Explicit VR Little Endian

1.2.840.10008.1.2.1 A
XA Image A 1.2.840.10008.5.1.4.1.1.12.1 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
XRF-Image A 1.2.840.10008.5.1.4.1.1.12.2 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
NM Image A 1.2.840.10008.5.1.4.1.1.20 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
Basic Text SR A 1.2.840.10008.5.1.4.1.1.88.11 A

Explicit VR Little Endian
Uncompressed
1.2.840.10008.1.2.1 A
Enhanced SR A 1.2.840.10008.5.1.4.1.1.88.22 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
0.0

July 2013
Comprehensive SR A 1.2.840.10008.5.1.4.1.1.88.33 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
Mammography CAD SR A 1.2.840.10008.5.1.4.1.1.88.50 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
Chest CAD SR A 1.2.840.10008.5.1.4.1.1.88.65 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
X-Ray Radiation Dose SR A 1.2.840.10008.5.1.4.1.1.88.67 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
PET Image A 1.2.840.10008.5.1.4.1.1.128 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
RT Image A 1.2.840.10008.5.1.4.1.1.481.1 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
RT Dose A 1.2.840.10008.5.1.4.1.1.481.2 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
RT Structure Set A 1.2.840.10008.5.1.4.1.1.481.3 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
RT Plan A 1.2.840.10008.5.1.4.1.1.481.5 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
RT Brachy Treatment Record A 1.2.840.10008.5.1.4.1.1.481.6 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
0.0

RT Treatment Summary Record A 1.2.840.10008.5.1.4.1.1.481.7 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
RT Ion Plan A 1.2.840.10008.5.1.4.1.1.481.8 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
RT Ion Beams Treatment Record A 1.2.840.10008.5.1.4.1.1.481.9 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
Csa Non-Image A 1.3.12.2.1107.5.9.1 A Explicit VR Little Endian

Uncompressed
1.2.840.10008.1.2.1 A
RWA: Import into local invoke this Application Entity for the Copy to Local Storage RWA. A.0
Storage A
0.0

July 2013
Real-World Activity: Export to local Archive Media A.0
The DICOM Archive application acts as FSU (for media with exist-
ing DICOM file-set) or FSC (media not initialized) using the inter-
change option when requested to copy SOP Instances from the
local storage to local Archive medium. A.0
The DICOM Archive application will receive a list of SOP

Instances to be copied to the local archive medium. According
to the state of the medium inserted (new medium, Medium
with DICOM file-set) the validity of the SOP Instances according
to the applicable profile is checked. Only valid SOP Instances are
accepted. A.0
When the DICOM archive application is requested to copy SOP

Instances the preferred application profile according configura-
tion will be used to validate and copy the referred SOP
Instances. When creating a new file set no Descriptor File will be
allocated and the related ID is not used. A.0
The DICOM archive application will not close the medium. A.0
A.0
RWA: Export to local Archive invoke this Application Entity for the Export to local Archive
Media A Media RWA. A.0
A.0
A.0
0.0

CHAPTER Augmented and
B.3 Private Profiles A.0
Augmented Application Profiles A.0
AUG-GEN-CD A.0
With no private Siemens Non-Images stored onto Medium,

the definitions of the PRI-SYNGO-CD Profile are applicable to
denote the augmentations for the STD-GEN-CD Standard
Profile. A.0
Storage of Private Information Objects will only be supported

with reference to a Private Application Profile (see next section).
A.0
The Siemens non-image is typically used for raw data and 3D

private data. A.0
AUG-CTMR-xxxx A.0

denote the augmentations for the and STD-CTMR-CD Stan-
dard Profiles. A.0

A.0
AUG-XA1K-CD A.0

denote the augmentations for the STD-XA1K-CD Standard
Profile. A.0

A.0
0.0

July 2013
Media Storage – Augmented and Private Profiles DICOM Conformance Statement
syngo® private offline

Media Application Profiles A.0
This section will contain a syngo specific Application Profile. A.0
The Structure of this Application Profile is defined in Part 11 of

the 2000 DICOM Standard. A.0
It is needed to describe the requirements for Offline Media Stor-

age of the private IOD (Non-Image IOD). A.0
Class and Profile Identification A.0
This document defines an Application Profile class for "syngo®

speaking1" modalities or applications. A.0
The identifier for this class shall be PRI-SYNGO. This class is

intended to be used for interchange of extended and private
Information Objects via CD-R offline media between dedicated
acquisition or workstation modalities built from a common
syngo architecture. A.0
1. ’syngo’ and ’We speak syngo’ are registered trademarks of Siemens AG
0.0

DICOM Conformance Statement Media Storage – Augmented and Private Profiles
The specific application profiles in this class are shown in the

table below: A.0
Application Profile Identifier A Description A
"syngo speaking" System on PRI-SYNGO-CD A Handles interchange of

CD-R A Composite SOP Instances and
privately defined SOP
Instances (Siemens Non-
Image IOD) A
"syngo speaking" System on PRI-SYNGO-DVD A Handles interchange of

DVD R A Composite SOP Instances and
privately defined SOP
Instances (Siemens Non-
Image IOD) A
Equipment claiming conformance for this syngo Application

Profile Class shall make a clear statement on handling of the pri-
vate defined SOP Instances. A.0
0.0

July 2013
Clinical Context A.0
This application profile facilitates the interchange of original

acquired and derived images and private data related to them.
Typical media interchange would be from in-lab acquisition
equipment to dedicated workstations and archive systems with
specific extensions to handle the private data objects (in both
directions). A.0
Additionally, images used to prepare procedures, multi-modal-

ity images (e.g. integrated US) and images derived from primary
diagnostic images, such as annotations, quantitative analysis
images, reference images, screen capture images may be inter-
changed via this profile. A.0
Roles and Service Class Options A.0
This Application Profile uses the Media Storage Service Class

defines in PS 3.4 with the Interchange Option. A.0
The Application Entity shall support one or more of the roles of

File Set Creator (FSC), File Set Reader (FSR), and File Set Updater
(FSU), defined in PS3.10. A.0
File Set Creator A The Application Entity acting as File Set Creator generates a File
Set under the PRI-SYNGO Application Profiles. A.0
File Set Creators shall be able to generate the Basic Directory

SOP Class in the DICOMDIR file with all the subsidiary Directory
Records related to the Image SOP Classes and Private SOP
Classes stored in the File Set. A.0
In case of the PRI-SYNGO-CD and PRI-SYNGO-DVD profile, the

FSC shall offer the ability to allow multi-session (additional
information may be subsequently added to the disc). For both
profiles a multi-session media can be finalized. A.0
0.0

Note
A multiple volume (a logical volume that can cross multiple
phydical media) is not supported by this Application Profile
Class. If a set of Files, e.g., a Study, cannot be written
entirely on one CD-R, the FSC will create multiple
independent DICOM File Sets such that each File Set can
reside on a single CD-R medium controlled by its individual
DICOMDIR file. The user of the FSC can opt to use written
labels on the discs to reflect that there is more than one disc
for this set of files (e.g. a study). A
File Set Reader A The role of the File Set Reader shall be used by Application Enti-
ties which receive the transferred File Set. A.0
File Set Readers shall be able to read all the defined SOP
Instances files defined for the specific Application Profiles to
which a conformance claim is made, using all the defined Trans-
fer Syntaxes. A.0
File Set Updater A The role of the File Set Updater shall be used by Application Enti-
ties, which receive a transferred File Set and update it by the
addition of processed information. A.0
File Set Updaters shall be able to read and update the DICOMDIR
file. File Set Updaters do not have to read the image/private
information objects. File Set Updaters shall be able to generate
any of the SOP Instance files defined for the specific Application
Profiles to which a conformance claim is made, and to read and
update the DICOMDIR file. A.0
In case of the PRI-SYNGO-CD and PRI-SYNGO-DVD profile, the

FSU shall offer the ability to allow multi-session (additional
information can be subsequently added to the disc). A.0
0.0

July 2013
Note (for CD-R and DVD-R)

If the disc has not been finalized, the File Set Updater will be
able to update information assuming there is enough space
on the disc to write a new DICOMDIR file, the information,
and the fundamental CD-R/DVD-R control structures. CD-R/
DVD-R control structures are the structures that inherent to
CD-R standards; see PS 3.12 A
0.0

PRI-SYNGO Profiles A.0
SOP Classes and Transfer Syntaxes A.0
These Application Profiles are based on the Media Storage Ser-

vice Class with the Interchange Option. In the table below Trans-
fer Syntax UID "RLE Lossless" applies ony for decompression. A.0
Information Ob- SOP Class UID Transfer Syntax and UID FSC FSR FSU
A A A
ject Definitions
Basic Directory A 1.2.840.10008.1.3.10 A Explicit VR Little Endian M A M A M A
Uncompressed
1.2.840.10008.1.2.1 A
CR Image A 1.2.840.10008.5.1.4.1.1.1 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
CR Image A 1.2.840.10008.5.1.4.1.1.1 A JPEG Lossless Process 14 O A M A O A
(selection value 1)
1.2.840.10008.1.2.4.70 A
CR Image A 1.2.840.10008.5.1.4.1.1.1 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
CR Image A 1.2.840.10008.5.1.4.1.1.1 A JPEG Lossy (baseline or O A O A O A
extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
CR Image A 1.2.840.10008.5.1.4.1.1.1 A RLE Lossless O A O A O A
1.2.840.10008.1.2.5 A
CR Image A 1.2.840.10008.5.1.4.1.1.1 A JPEG 2000 Lossless O A O A O A
1.2.840.10008.1.2.90 A
CR Image A 1.2.840.10008.5.1.4.1.1.1 A JPEG 2000 Lossy M A M A O A
1.2.840.10008.1.2.91 A
DX Image - For 1.2.840.10008.5.1.4.1.1.1.1 A Explicit VR Little Endian M A M A O A
Presentation A Uncompressed
1.2.840.10008.1.2.1 A
0.0

July 2013
A A A
ject Definitions
DX Image - For 1.2.840.10008.5.1.4.1.1.1.1 A JPEG Lossless Process 14 O A M A O A
Presentation A (selection value 1)

1.2.840.10008.1.2.4.70 A
DX Image - For 1.2.840.10008.5.1.4.1.1.1.1 A Explicit VR Big Endian O A M A O A
1.2.840.10008.1.2.2 A
DX Image - For 1.2.840.10008.5.1.4.1.1.1.1 A JPEG Lossy (baseline or O A O A O A
Presentation A extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
DX Image - For 1.2.840.10008.5.1.4.1.1.1.1 A RLE Lossless O A O A O A
Presentation A 1.2.840.10008.1.2.5 A
DX Image - For 1.2.840.10008.5.1.4.1.1.1.1 A JPEG 2000 Lossless O A O A O A
Presentation A 1.2.840.10008.1.2.90 A
DX Image - For 1.2.840.10008.5.1.4.1.1.1.1 A JPEG 2000 Lossy O A O A O A
Presentation A 1.2.840.10008.1.2.91 A
DX Image - For 1.2.840.10008.5.1.4.1.1.1.1.1 A Explicit VR Little Endian M A M A O A
Processing A Uncompressed
1.2.840.10008.1.2.1 A
DX Image - For 1.2.840.10008.5.1.4.1.1.1.1.1 A JPEG Lossless Process 14 O A M A O A
Processing A (selection value 1)

1.2.840.10008.1.2.4.70 A
DX Image - For 1.2.840.10008.5.1.4.1.1.1.1.1 A Explicit VR Big Endian O A M A O A
1.2.840.10008.1.2.2 A
DX Image - For 1.2.840.10008.5.1.4.1.1.1.1.1 A JPEG Lossy (baseline or O A O A O A
Processing A extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
DX Image - For 1.2.840.10008.5.1.4.1.1.1.1.1 A RLE Lossless O A O A O A
Processing A 1.2.840.10008.1.2.5 A
MG Image - For 1.2.840.10008.5.1.4.1.1.1.2 A Explicit VR Little Endian M A M A O A
1.2.840.10008.1.2.1 A
0.0

A A A
ject Definitions
MG Image - For 1.2.840.10008.5.1.4.1.1.1.2 A JPEG Lossless Process 14 O A M A O A

1.2.840.10008.1.2.4.70 A
MG Image - For 1.2.840.10008.5.1.4.1.1.1.2 A Explicit VR Big Endian O A M A O A
1.2.840.10008.1.2.2 A
MG Image - For 1.2.840.10008.5.1.4.1.1.1.2 A JPEG Lossy (baseline or O A O A O A
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
MG Image - For 1.2.840.10008.5.1.4.1.1.1.2 A JPEG Lossless O A O A O A
Presentation A 1.2.840.10008.1.2.90 A
MG Image - For 1.2.840.10008.5.1.4.1.1.1.2 A JPEG Lossy O A O A O A
Presentation A 1.2.840.10008.1.2.91 A
MG Image - For 1.2.840.10008.5.1.4.1.1.1.2 A RLE Lossless O A O A O A
Presentation A 1.2.840.10008.1.2.5 A
MG Image - For 1.2.840.10008.5.1.4.1.1.1.2.1 A Explicit VR Little Endian M A M A O A
1.2.840.10008.1.2.1 A
MG Image - For 1.2.840.10008.5.1.4.1.1.1.2.1 A JPEG Lossless Process 14 O A M A O A

1.2.840.10008.1.2.4.70 A
MG Image - For 1.2.840.10008.5.1.4.1.1.1.2.1 A Explicit VR Big Endian O A M A O A
1.2.840.10008.1.2.2 A
MG Image - For 1.2.840.10008.5.1.4.1.1.1.2.1 A JPEG Lossy (baseline or O A O A O A
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
MG Image - For 1.2.840.10008.5.1.4.1.1.1.2.1 A RLE Lossless O A O A O A
Processing A 1.2.840.10008.1.2.5 A
IOX Image - For 1.2.840.10008.5.1.4.1.1.1.3 A Explicit VR Little Endian M A M A O A
1.2.840.10008.1.2.1 A
0.0

July 2013
A A A
ject Definitions
IOX Image - For 1.2.840.10008.5.1.4.1.1.1.3 A JPEG Lossless Process 14 O A M A O A

1.2.840.10008.1.2.4.70 A
IOX Image - For 1.2.840.10008.5.1.4.1.1.1.3 A Explicit VR Big Endian O A M A O A
1.2.840.10008.1.2.2 A
IOX Image - For 1.2.840.10008.5.1.4.1.1.1.3 A JPEG Lossy (baseline or O A O A O A
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
IOX Image - For 1.2.840.10008.5.1.4.1.1.1.3 A RLE Lossless O A O A O A
Presentation A 1.2.840.10008.1.2.5 A
IOX Image - For 1.2.840.10008.5.1.4.1.1.1.3 A JPEG Lossless O A O A O A
Presentation A 1.2.840.10008.1.2.90 A
IOX Image - For 1.2.840.10008.5.1.4.1.1.1.3 A JPEG Lossy O A O A O A
Presentation A 1.2.840.10008.1.2.91 A
IOX Image - For 1.2.840.10008.5.1.4.1.1.1.3.1 A Explicit VR Little Endian M A M A O A
1.2.840.10008.1.2.1 A
IOX Image - For 1.2.840.10008.5.1.4.1.1.1.3.1 A JPEG Lossless Process 14 O A M A O A

1.2.840.10008.1.2.4.70 A
IOX Image - For 1.2.840.10008.5.1.4.1.1.1.3.1 A Explicit VR Big Endian O A M A O A
1.2.840.10008.1.2.2 A
IOX Image - For 1.2.840.10008.5.1.4.1.1.1.3.1 A JPEG Lossy (baseline or O A O A O A
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
IOX Image - For 1.2.840.10008.5.1.4.1.1.1.3.1 A RLE Lossless O A O A O A
Processing A 1.2.840.10008.1.2.5 A
CT Image A 1.2.840.10008.5.1.4.1.1.2 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
0.0

A A A
ject Definitions
CT Image A 1.2.840.10008.5.1.4.1.1.2 A JPEG Lossless Process 14 O A M A O A
(selection value 1)
1.2.840.10008.1.2.4.70 A
CT Image A 1.2.840.10008.5.1.4.1.1.2 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
CT Image A 1.2.840.10008.5.1.4.1.1.2 A JPEG Lossy (baseline or O A O A O A
extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
CT Image A 1.2.840.10008.5.1.4.1.1.2 A RLE Lossless O A O A O A
1.2.840.10008.1.2.5 A
CT Image A 1.2.840.10008.5.1.4.1.1.2 A JPEG 2000 Lossless O A O A O A
1.2.840.10008.1.2.90 A
CT Image A 1.2.840.10008.5.1.4.1.1.2 A JPEG 2000 Lossy O A O A O A
1.2.840.10008.1.2.91 A
US-MF image 1.2.840.10008.5.1.4.1.1.3 A Explicit VR Little Endian - A M A - A
(retired) A Uncompressed
1.2.840.10008.1.2.1 A
US-MF image 1.2.840.10008.5.1.4.1.1.3 A JPEG Lossless Process 14 - A M A - A
(retired) A (selection value 1)

1.2.840.10008.1.2.4.70 A
US-MF image 1.2.840.10008.5.1.4.1.1.3 A Explicit VR Big Endian - A M A - A
1.2.840.10008.1.2.2 A
US-MF image 1.2.840.10008.5.1.4.1.1.3 A JPEG Lossy (baseline or - A M A - A
(retired) A extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
US-MF image 1.2.840.10008.5.1.4.1.1.3 A RLE Lossless - A M A - A
(retired) A 1.2.840.10008.1.2.5 A
US-MF image 1.2.840.10008.5.1.4.1.1.3 A JPEG 2000 Lossless - A M A - A
(retired) A 1.2.840.10008.1.2.90 A
0.0

July 2013
A A A
ject Definitions
US-MF image 1.2.840.10008.5.1.4.1.1.3 A JPEG 2000 Lossy - A M A - A
(retired) A 1.2.840.10008.1.2.91 A
US-MF image A 1.2.840.10008.5.1.4.1.1.3.1 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
US-MF image A 1.2.840.10008.5.1.4.1.1.3.1 A JPEG Lossless Process 14 O A M A O A
(selection value 1)
1.2.840.10008.1.2.4.70 A
US-MF image A 1.2.840.10008.5.1.4.1.1.3.1 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
US-MF image A 1.2.840.10008.5.1.4.1.1.3.1 A JPEG Lossy (baseline or O A O A O A
extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
US-MF image A 1.2.840.10008.5.1.4.1.1.3.1 A RLE Lossless O A M A O A
1.2.840.10008.1.2.5 A
MR Image A 1.2.840.10008.5.1.4.1.1.4 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
MR Image A 1.2.840.10008.5.1.4.1.1.4 A JPEG Lossless Process 14 O A M A O A
(selection value 1)
1.2.840.10008.1.2.4.70 A
MR Image A 1.2.840.10008.5.1.4.1.1.4 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
MR Image A 1.2.840.10008.5.1.4.1.1.4 A JPEG Lossy (baseline or O A O A O A
extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
MR Image A 1.2.840.10008.5.1.4.1.1.4 A RLE Lossless O A O A O A
1.2.840.10008.1.2.5 A
0.0

A A A
ject Definitions
MR Image A 1.2.840.10008.5.1.4.1.1.4 A JPEG 2000 Lossless O A O A O A
1.2.840.10008.1.2.90 A
MR Image A 1.2.840.10008.5.1.4.1.1.4 A JPEG 2000 Lossy O A O A O A
1.2.840.10008.1.2.91 A
US Image 1.2.840.10008.5.1.4.1.1.6 A Explicit VR Little Endian - A M A - A
1.2.840.10008.1.2.1 A
US Image 1.2.840.10008.5.1.4.1.1.6 A JPEG Lossless Process 14 - A M A - A
(retired) A (selection value 1)

1.2.840.10008.1.2.4.70 A
US Image 1.2.840.10008.5.1.4.1.1.6 A Explicit VR Big Endian - A M A - A
1.2.840.10008.1.2.2 A
US Image 1.2.840.10008.5.1.4.1.1.6 A JPEG Lossy (baseline or - A M A - A
(retired) A extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
US Image 1.2.840.10008.5.1.4.1.1.6 A RLE Lossless - A M A - A
(retired) A 1.2.840.10008.1.2.5 A
US Image 1.2.840.10008.5.1.4.1.1.6 A JPEG 2000 Lossless - A M A - A
(retired) A 1.2.840.10008.1.2.90 A
US Image 1.2.840.10008.5.1.4.1.1.6 A JPEG 2000 Lossy - A O A - A
(retired) A 1.2.840.10008.1.2.91 A
US Image A 1.2.840.10008.5.1.4.1.1.6.1 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
US Image A 1.2.840.10008.5.1.4.1.1.6.1 A JPEG Lossless Process 14 O A M A O A
(selection value 1)
1.2.840.10008.1.2.4.70 A
US Image A 1.2.840.10008.5.1.4.1.1.6.1 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
0.0

July 2013
A A A
ject Definitions
US Image A 1.2.840.10008.5.1.4.1.1.6.1 A JPEG Lossy (baseline or O A O A O A
extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
US Image A 1.2.840.10008.5.1.4.1.1.6.1 A RLE Lossless O A M A O A
1.2.840.10008.1.2.5 A
US Image A 1.2.840.10008.5.1.4.1.1.6.1 A JPEG 2000 Lossless O A M A O A
1.2.840.10008.1.2.90 A
US Image A 1.2.840.10008.5.1.4.1.1.6.1 A JPEG 2000 Lossy O A M A O A
1.2.840.10008.1.2.91 A
SC Image A 1.2.840.10008.5.1.4.1.1.7 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
SC Image A 1.2.840.10008.5.1.4.1.1.7 A JPEG Lossless Process 14 O A M A O A
(selection value 1)
1.2.840.10008.1.2.4.70 A
SC Image A 1.2.840.10008.5.1.4.1.1.7 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
SC Image A 1.2.840.10008.5.1.4.1.1.7 A JPEG Lossy (baseline or O A O A O A
extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
SC Image A 1.2.840.10008.5.1.4.1.1.7 A RLE Lossless O A O A O A
1.2.840.10008.1.2.5 A
SC Image A 1.2.840.10008.5.1.4.1.1.7 A JPEG 2000 Lossless O A O A O A
1.2.840.10008.1.2.90 A
SC Image A 1.2.840.10008.5.1.4.1.1.7 A JPEG 2000 Lossy O A O A O A
1.2.840.10008.1.2.91 A
0.0

A A A
ject Definitions
Waveform 1.2.840.10008.5.1.4.1.1.9.1.1 A Explicit VR Little Endian M A M A O A
Storage SOP 1.2.840.10008.5.1.4.1.1.9.1.2 A Uncompressed

Classes A 1.2.840.10008.5.1.4.1.1.9.1.3 A 1.2.840.10008.1.2.1 A
1.2.840.10008.5.1.4.1.1.9.2.1 A
1.2.840.10008.5.1.4.1.1.9.3.1 A
1.2.840.10008.5.1.4.1.1.9.4.1 A
Waveform 1.2.840.10008.5.1.4.1.1.9.1.1 A Explicit VR Big Endian A O A M A O A
Storage SOP 1.2.840.10008.5.1.4.1.1.9.1.2 A Uncompressed

Classes A 1.2.840.10008.5.1.4.1.1.9.1.3 A 1.2.840.10008.1.2.1 A
1.2.840.10008.5.1.4.1.1.9.2.1 A
1.2.840.10008.5.1.4.1.1.9.3.1 A
1.2.840.10008.5.1.4.1.1.9.4.1 A
X-Ray 1.2.840.10008.5.1.4.1.1.12.1 A Explicit VR Little Endian M A M A O A
Angiographic Uncompressed
Image A 1.2.840.10008.1.2.1 A
X-Ray 1.2.840.10008.5.1.4.1.1.12.1 A JPEG Lossless Process 14 O A M A O A
Angiographic (selection value 1)

Image A 1.2.840.10008.1.2.4.70 A
X-Ray 1.2.840.10008.5.1.4.1.1.12.1 A Explicit VR Big Endian O A M A O A
Angiographic Uncompressed
Image A 1.2.840.10008.1.2.2 A
X-Ray 1.2.840.10008.5.1.4.1.1.12.1 A JPEG Lossy (baseline or O A O A O A
Angiographic extended)
Image A 1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
X-Ray 1.2.840.10008.5.1.4.1.1.12.1 A RLE Lossless O A M A O A
Angiographic 1.2.840.10008.1.2.5 A
Image A
X-Ray 1.2.840.10008.5.1.4.1.1.12.1 A JPEG 2000 Lossless O A M A O A
Angiographic 1.2.840.10008.1.2.90 A
Image A
X-Ray 1.2.840.10008.5.1.4.1.1.12.1 A JPEG 2000 Lossy O A M A O A
Angiographic 1.2.840.10008.1.2.91 A
Image A
0.0

July 2013
A A A
ject Definitions
X-Ray Radio- 1.2.840.10008.5.1.4.1.1.12.2 A Explicit VR Little Endian M A M A O A
flouroscopic Uncompressed
Image A 1.2.840.10008.1.2.1 A
X-Ray Radio- 1.2.840.10008.5.1.4.1.1.12.2 A JPEG Lossless Process 14 O A M A O A
flouroscopic (selection value 1)

Image A 1.2.840.10008.1.2.4.70 A
X-Ray Radio- 1.2.840.10008.5.1.4.1.1.12.2 A Explicit VR Big Endian O A M A O A
flouroscopic Uncompressed
Image A 1.2.840.10008.1.2.2 A
X-Ray Radio- 1.2.840.10008.5.1.4.1.1.12.2 A JPEG Lossy (baseline or O A O A O A
flouroscopic extended)
Image A 1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
X-Ray Radio- 1.2.840.10008.5.1.4.1.1.12.2 A RLE Lossless O A M A O A
flouroscopic 1.2.840.10008.1.2.5 A
Image A
X-Ray Radio- 1.2.840.10008.5.1.4.1.1.12.2 A JPEG 2000 Lossless O A M A O A
flouroscopic 1.2.840.10008.1.2.90 A
Image A
X-Ray Radio- 1.2.840.10008.5.1.4.1.1.12.2 A JPEG 2000 Lossy O A M A O A
flouroscopic 1.2.840.10008.1.2.91 A
Image A
NM Image A 1.2.840.10008.5.1.4.1.1.20 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
NM Image A 1.2.840.10008.5.1.4.1.1.20 A JPEG Lossless Process 14 O A M A O A
(selection value 1)
1.2.840.10008.1.2.4.70 A
NM Image A 1.2.840.10008.5.1.4.1.1.20 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
0.0

A A A
ject Definitions
NM Image A 1.2.840.10008.5.1.4.1.1.20 A JPEG Lossy (baseline or O A O A O A
extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
NM Image A 1.2.840.10008.5.1.4.1.1.20 A RLE Lossless O A O A O A
1.2.840.10008.1.2.5 A
NM Image A 1.2.840.10008.5.1.4.1.1.20 A JPEG 2000 Lossless O A O A O A
1.2.840.10008.1.2.90 A
NM Image A 1.2.840.10008.5.1.4.1.1.20 A JPEG 2000 Lossy O A O A O A
1.2.840.10008.1.2.91 A
Basic Text SR A 1.2.840.10008.5.1.4.1.1.88.11 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
Basic Text SR A 1.2.840.10008.5.1.4.1.1.88.11 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
Enhanced SR A 1.2.840.10008.5.1.4.1.1.88.22 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
Enhanced SR A 1.2.840.10008.5.1.4.1.1.88.22 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
Comprehensive 1.2.840.10008.5.1.4.1.1.88.33 A Explicit VR Little Endian M A M A O A
SR A Uncompressed
1.2.840.10008.1.2.1 A
Comprehensive 1.2.840.10008.5.1.4.1.1.88.33 A Explicit VR Big Endian O A M A O A
SR A Uncompressed
1.2.840.10008.1.2.2 A
Mammography 1.2.840.10008.5.1.4.1.1.88.50 A Explicit VR Little Endian M A M A O A
CAD SR A Uncompressed
1.2.840.10008.1.2.1 A
0.0

July 2013
A A A
ject Definitions
Mammography 1.2.840.10008.5.1.4.1.1.88.50 A Explicit VR Big Endian O A M A O A
CAD SR A Uncompressed
1.2.840.10008.1.2.2 A
Chest CAD SR A 1.2.840.10008.5.1.4.1.1.88.65 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
Chest CAD SR A 1.2.840.10008.5.1.4.1.1.88.65 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
X-Ray Radiation 1.2.840.10008.5.1.4.1.1.88.67 A Explicit VR Little Endian M A M A O A
Dose SR A Uncompressed
1.2.840.10008.1.2.1 A
X-Ray Radiation 1.2.840.10008.5.1.4.1.1.88.67 A Explicit VR Big Endian O A M A O A
Dose SR A Uncompressed
1.2.840.10008.1.2.2 A
PET Image A 1.2.840.10008.5.1.4.1.1.128 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
PET Image A 1.2.840.10008.5.1.4.1.1.128 A JPEG Lossless Process 14 O A M A O A
(selection value 1)
1.2.840.10008.1.2.4.70 A
PET Image A 1.2.840.10008.5.1.4.1.1.128 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
PET Image A 1.2.840.10008.5.1.4.1.1.128 A JPEG Lossy (baseline or O A O A O A
extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
PET Image A 1.2.840.10008.5.1.4.1.1.128 A RLE Lossless O A O A O A
1.2.840.10008.1.2.5 A
PET Image A 1.2.840.10008.5.1.4.1.1.128 A JPEG 2000 Lossless O A O A O A
1.2.840.10008.1.2.90 A
0.0

A A A
ject Definitions
PET Image A 1.2.840.10008.5.1.4.1.1.128 A JPEG 2000 Lossy O A O A O A
1.2.840.10008.1.2.91 A
RT Image A 1.2.840.10008.5.1.4.1.1.481.1 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
RT Image A 1.2.840.10008.5.1.4.1.1.481.1 A JPEG Lossless Process 14 O A M A O A
(selection value 1)
1.2.840.10008.1.2.4.70 A
RT Image A 1.2.840.10008.5.1.4.1.1.481.1 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
RT Image A 1.2.840.10008.5.1.4.1.1.481.1 A JPEG Lossy (baseline or O A O A O A
extended)
1.2.840.10008.1.2.4.50 A
1.2.840.10008.1.2.4.51 A
RT Image A 1.2.840.10008.5.1.4.1.1.481.1 A RLE Lossless O A O A O A
1.2.840.10008.1.2.5 A
RT Image A 1.2.840.10008.5.1.4.1.1.481.1 A JPEG 2000 Lossless O A O A O A
1.2.840.10008.1.2.90 A
RT Image A 1.2.840.10008.5.1.4.1.1.481.1 A PEG 2000 Lossy O A O A O A
1.2.840.10008.1.2.91 A
RT Dose A 1.2.840.10008.5.1.4.1.1.481.2 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
RT Dose A 1.2.840.10008.5.1.4.1.1.481.2 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
RT Structure SetA 1.2.840.10008.5.1.4.1.1.481.3 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
RT Structure SetA 1.2.840.10008.5.1.4.1.1.481.3 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
0.0

July 2013
A A A
ject Definitions
RT Beams 1.2.840.10008.5.1.4.1.1.481.4 A Explicit VR Little Endian M A M A O A
Treatment Uncompressed
Record A 1.2.840.10008.1.2.1 A
RT Beams 1.2.840.10008.5.1.4.1.1.481.4 A Explicit VR Big Endian O A M A O A
Record A 1.2.840.10008.1.2.2 A
RT Plan A 1.2.840.10008.5.1.4.1.1.481.5 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
RT Plan A 1.2.840.10008.5.1.4.1.1.481.5 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
RT Brachy 1.2.840.10008.5.1.4.1.1.481.6 A Explicit VR Little Endian M A M A O A
Record A 1.2.840.10008.1.2.1 A
RT Brachy 1.2.840.10008.5.1.4.1.1.481.6 A Explicit VR Big Endian O A M A O A
Record A 1.2.840.10008.1.2.2 A
RT Treatment 1.2.840.10008.5.1.4.1.1.481.7 A Explicit VR Little Endian M A M A O A
Summary Uncompressed
Record A 1.2.840.10008.1.2.1 A
RT Treatment 1.2.840.10008.5.1.4.1.1.481.7 A Explicit VR Big Endian O A M A O A
Summary Uncompressed
Record A 1.2.840.10008.1.2.2 A
RT Ion Plan A 1.2.840.10008.5.1.4.1.1.481.8 A Explicit VR Little Endian M A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
RT Ion Plan A 1.2.840.10008.5.1.4.1.1.481.8 A Explicit VR Big Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.2 A
RT Ion Beams 1.2.840.10008.5.1.4.1.1.481.9 A Explicit VR Little Endian M A M A O A
Record A 1.2.840.10008.1.2.1 A
0.0

A A A
ject Definitions
RT Ion Beams 1.2.840.10008.5.1.4.1.1.481.9 A Explicit VR Big Endian O A M A O A
Record A 1.2.840.10008.1.2.2 A
Csa Non-Image A 1.3.12.2.1107.5.9.1 A Explicit VR Little Endian O A M A O A
Uncompressed
1.2.840.10008.1.2.1 A
FSC, FSR, FSU - denote the requirement for those roles A.0
O - Optional A.0
M - Mandatory A.0
0.0

July 2013
Physical Media and Formats A.0
The PRI-SYNGO-CD Profile requires the 120mm CD-R physical

media with the ISO/IEC 9660 Media Format, as defined in
PS3.12. A.0
The PRI-SYNGO-DVD Profile requires the 120mm DVD-R physical

media with the UDF 2.01 Media Format, as defined in PS3.12. A.0
Directory Information in DICOMDIR A.0
Conforming Application Entities shall include in the DICOMDIR

File the Basic Directory IOD containing Directory Records at the
Patient and subsidiary levels appropriate to the SOP Classes in
the File Set. All DICOM files in the File Set incorporating SOP
instances defined for the specific Application Profile shall be ref-
erenced by Directory Records. A.0
Note
DICOMDIRs with no directory information are not allowed
by this Application Profile A
Privately defined IODs will be referenced by "PRIVATE"

Directory Records. A
0.0

Basic Directory IOD This Application Profile makes use of optional attributes of the
Specification A Basic Directory IOD to support recognition of Patient’s Storage
Service request results in spanning multiple volumes (file sets).
Therefore the File Set Descriptor File can be used and is then ref-
erenced by optional Basic Directory IOD attributes. If existent,
the specified Descriptor File may be used by FSR applications.
Any FSU, FSC shall make a clear statement if the Descriptor File
mechanism is used according to the specialization defined in
this Application Profile. A.0
The Descriptor Files shall have the following contents: A.0
One single line without any control characters and according to

the Basic Character Set having the following defined text: A.0
"MULTIVOLUME: xx of yy" A.0
xx, yy are replaced by the actual number of the volume (xx) and
the total number of volumes in the set (yy). A.0
If used, the Descriptor File shall have the File ID "README" and
reside in the same directory level as the DICOMDIR. It is refer-
enced by the attribute [0004,1141] File Set Descriptor File ID
having the defined contents of "README". A.0
0.0

July 2013
Additional Keys A File Set Creators and Updaters are required to generate the man-
datory elements specified in PS 3.3, Annex F of the DICOM Stan-
dard. Table below: PRI-SYNGO-CD Additional DICOMDIR Keys
specifies the additional associated keys. At each directory record
level other additional data elements can be added, but it is not
required that File Set Readers be able to use them as keys. Refer
to the Basic Directory IOD in PS 3.3. A.0
A
Attribute Name Tag A Directory Record Type Notes
Level
Date Of Birth A (0010,0030) A PATIENT A 2C A required, if present in SOP
Instance A
Patient’s Sex A (0010,0040) A PATIENT A 2C A required, if present in SOP

Instance A
Series Date A (0008,0021) A SERIES A 3 A A
Series Time A (0008,0031) A SERIES A 3 A A
Institution name A (0008,0080) A SERIES A 2C A required, if present in SOP

Instance A
Institution (0008,0081) A SERIES A 2C A required, if present in SOP

Address A Instance A
Series Description A (0008,103E) A SERIES A 3 A A
Performing (0008,1050) A SERIES A 2C A required, if present in SOP

Physician A Instance A
Image Type A (0008,0008) A IMAGE A 1C A required, if present in SOP

Instance A
Content Date A (0008,0023) A IMAGE A 3 A A
Content Time A (0008,0033) A IMAGE A 3 A A
Referenced Image (0008,1140) A IMAGE A 1C A required, if present in SOP

Sequence A Instance A
> Referenced SOP (0008,1150) A A A A
Class UID A
> Referenced SOP (0008,1155) A A A A
Instance UID A
0.0


Level
Image Position (00020,0032) A IMAGE A 2C A required, if present in SOP
(Patient) A Instance A
Image Orientation (0020,0037) A IMAGE A 2C A required, if present in SOP

(Patient) A Instance A
Frame Of (0020,0052) A IMAGE A 2C A required, if present in SOP

Reference UID A Instance A
Rows A (0028,0010) A IMAGE A 3 A A
Columns A (0028,0011) A IMAGE A 3 A A
Pixel Spacing A (0028,0030) A IMAGE A 1C A C A
Calibration Image A (0050,0004) A IMAGE A 2C A required, if present in SOP

Instance A
Icon Image (0088,0200) A IMAGE A 3 A required for Image SOP

Sequence A Classes A
> Samples per (0028,0002) A A A 1 A
Pixel A
> Photometric (0028,0004) A A A MONOCHROME2 A
Interpretation A
> Rows A (0028,0010) A A A 128 for XA IOD, 64 otherwise A
> Columns A (0028,0011) A A A 128 for XA IOD, 64 otherwise A
> Bits Allocated A (0028,0100) A A A 8 A
> Bits Stored A (0028,0101) A A A 8 A
> High Bit A (0028,0102) A A A 7 A
> Pixel (0028,0103) A A A 0 (unsigned) A
Representation A
> Pixel Data A (7FE0,0010) A A A Icon Image pixel data A
Curve Number A (0020,0024) A CURVE A 1C A required, if present in SOP

Instance A
0.0

July 2013
Private Directory Record Private Directory Records are supproted by this Application Pro-
Keys A file Class at the following level: A.0
IMAGE A.0
The PRIVATE Directory Records will have required elements in

addition to the mandatory elements specified in PS 3.3. A.0
The following table will list the additional required keys for PRI-
VATE Directory Records. A.0
A
Level
Private Record UID A (0004,1432) A PRIVATE A 1 A See Conformance
Statement A
SOP Class UID A (0008,0016) A PRIVATE A 1C A required, if present in SOP

Instance A
SOP Instance UID A (0008,0018) A PRIVATE A 1C A required, if present in SOP

Instance A
Image Type A (0008,0008) A PRIVATE A 3 A identification

characteristics A
Acquisition Date A (0008,0022) A PRIVATE A 3 A A
Acquisition Time A (0008,0032) A PRIVATE A 3 A A
Acquisition (0020,0012) A PRIVATE A 3 A A
Number A
CSA Data Type A (0029,xx08) A PRIVATE A 1 A private owner code =

SIEMENS CSA NON-IMAGE A
CSA Data Version A (0029,xx09) A PRIVATE A 3 A private owner code =

SIEMENS CSA NON-IMAGE A
0.0

Icon Images A Directory Records of type SERIES or IMAGE may include Icon
Images. The Icon Image Pixel data shall be as specified in PS 3.3
"Icon Imge Key Definition", and restricted such, that Bits Allo-
cated (0028,0100) and Bits Stored (0028,0101) shall be equal
to 8, an d Rows (0028,0010) and Columns (0028, 0011) shall be
equal to 128 for XA Images and 64 for all other images. The Pho-
tometric interpretation (0028,0004) shall always be restricted
to "MONOCHROME2". A.0
PRIVATE Directory Records will not contain Icon Image informa-

tion. A.0
Other Parameters A.0
This section defines other parameters common to all specific

Application Profiles in the PRI-SYNGO class which need to be
specified in order to ensure interoperable media interchange. A.0
Multiframe JPEG Format A.0
The JPEG encoding of pixel data shall use Interchange Format

(with table specification) for all frames. A.0
A.0
0.0

July 2013
0.0

Extensions, Specializations and
CHAPTER Privatizations of SOP Classes and Transfer
B.4 Syntaxes A.0
The SOP Classes listed refer in majority to those created by the

equipment to which this Conformance Statement is related to.
For SOP classes not listed in this section, please refer to the Stor-
age section of the DICOM Conformance Statement of the prod-
uct. This will include all SOP Instances that can be received and
displayed and therefore will be included into offline media stor-
age even though these SOP Instances are not created by the
equipment serving the Media Storage Service. A.0
0.0

July 2013
Media Storage – Extensions/Specializations/Privatizations DICOM Conf. Statement
SOP Specific Conformance

Statement for Basic Directory A.0
Extension, Specialization for SIEMENS Non-

Image Objects A.0
According to the PRI-SYNGO Application Profile Class the usage

of the Private Creator UIDs and further optional keys for the
Directory Records referring to SIEMENS Non-Image Objects are
listed in the following table. A.0
A
Attribute Tag Value used
Private Record UID A (0004,1432) A 1.3.12.2.1107.5.9.1 A
SOP Class UID A (0008,0016) A 1.3.12.2.1107.5.9.1 A
For the Non-Images no Icon Image Sequence will be generated. A.0
A.0
0.0

CHAPTER
B.5 Configuration A.0
AE Title Mapping A.0
DICOM Media Storage AE Title A.0
The DICOM Storage application (Image Manager) provides the

application entity title: A.0
CsaImageManager A.0
A.0
0.0

July 2013
Media Storage – Configuration DICOM Conformance Statement
0.0

CHAPTER Support of Extended
B.6 Character Sets A.0
The Somaris/5 DICOM application supports the following char-

acter sets as defined in the three tables below: A.0
A.0

tion number
Default repertoire A none A ISO_IR 6 A ISO 646: A
ISO_IR 6 A ISO 646: A
Cyrillic A ISO_IR 144 A ISO_IR 144 A Supplementary set A
Arabic A ISO_IR 127 A ISO_IR 127 A Supplementary set A
Greek A ISO_IR 126 A ISO_IR 126 A Supplementary set A
Hebrew A ISO_IR 138 A ISO_IR 138 A Supplementary set A
0.0

July 2013
Media Storage – Support of Extended Character Sets DICOM Conformance Statement

tion number
Japanese A ISO_IR 13 A ISO_IR 13 A JIS X 0201: Katakana A
ISO_IR 14 A JIS X 0201: Romaji A
A.0
A.0
tion tension number
Default ISO 2022 IR 6 A ISO 2022 A ESC 02/08 ISO-IR 6 A ISO 646 A
repertoire A 04/02 A
alphabet 04/01 A
No.1 A
04/02 A
alphabet 04/02 A
No.2 A
04/02 A
alphabet 04/03 A
No.3 A
04/02 A
0.0

DICOM Conformance Statement Media Storage – Support of Extended Character Sets
tion tension number
Latin ISO 2022 IR 110

A ISO 2022 A ESC 02/13 ISO-IR 110 A Supplementary set A
alphabet 04/04 A
No.4 A
04/02 A
Cyrillic A ISO 2022 IR 144

04/12 A
04/02 A
Arabic A ISO 2022 IR 127

04/07 A
04/02 A
Greek A ISO 2022 IR 126

04/06 A
A ISO 2022 A ESC 02/08 ISO-IR 6 A ISO 646 A
04/02 A
Hebrew A ISO 2022 IR 138

04/08 A
04/02 A
Latin ISO 2022 IR 148

alphabet 04/13 A
No.5 A
04/02 A
0.0

July 2013
tion tension number
Japanese A ISO 2022 IR 13 A ISO 2022 A ESC 02/13 ISO-IR 13 A JIS X 0201:
04/09 A Katakana A
ISO 2022 A ESC 02/13 ISO-IR 14 A JIS X 0201-1976:

04/10 A Romaji A
A.0
A.0
Multi-Byte Character Sets without Code Extension A
Character Set Defined Term A ISO registration Character Set A
Description A number A
Unicode A ISO_IR 192 A ISO 10646 A Unicode in UTF-8 A
Chinese A GB18030 A GB18030 A GB 18030-2000

(China Association for
Standardization) A
0.0

DICOM Conformance Statement Media Storage – Support of Extended Character Sets
Multi-Byte Character Sets with Code Extension A
tion tension number
Japanese A ISO 2022 IR 87 A ISO 2022 A ESC 02/04 ISO-IR 87 A JIS X 0208: Kanji A
04/02 A
A ISO 2022 IR 159 A ISO 2022 A ESC 02/04 ISO-IR 159 A JIS X 0212:
02/08 04/ Supplementary
04 A Kanji set A
Chinesea A ISO 2022 IR 58 A ISO 2022 A ESC 02/04 ISO-IR 58 A GB2312-80

04/01 A (China Association
for Standardization) A
a. This Character Set is an extension of DICOM for the Chinese language.
A.0
When there is a mismatch between the SCS tags (0008,0005)

and the characters in an IOD received by the system, then the
following measures are taken to make the characters DICOM
conform: A.0
❏ Try to import with ISO_IR 100. If ISO_IR 100 fails, convert

each illegal character to a ’?’.
❏ There are now three categories of character sets which have
to be differentiated because of their different encoding for-
mats:
❏ Conventional ISO character sets: ISO_IR 6, ISO 2022 IR 6,
ISO_IR 100, etc.
❏ encoded in ISO 2022
❏ ISO_IR 192 encoded in UTF-8
❏ GB18030 encoded in GB18030
0.0

July 2013
It is not possible to recognize the following mismatches auto-

matically on receiving or importing: A.0
❏ An attribute value is encoded in ISO_IR 192(0008,0005)

contains a conventional ISO character set as primary charac-
ter set
❏ An attribute value is encoded in GB18030(0008,0005)
contains a conventional ISO character set as primary charac-
ter set
❏ An attribute value is encoded in ISO 2022 (0008,0005)
contains ISO_IR 192
❏ An attribute value is encoded in ISO 2022(0008,0005)
contains GB18030
An IOD that contains one of the above mentioned inconsisten-

cies is not DICOM conform. As these kinds of inconsistencies
cannot be recognized by the system, the IOD will not be rejected
but the character data might be corrupted. A.0
Older versions of syngo do not support the newly introduced

character sets ISO_IR 192 and GB18030 and their special encod-
ings. That means, an IOD which contains one of these new char-
acter sets in (0008,0005) will be rejected by an older syngo sys-
tem. A.0
0.0

ANNEX
Annex
0.0
Siemens Private Non-Image IOD 0
Please see section

→ page A.4–92, Private SOP class CSA Non-Image. 0.0
Siemens Standard Extended

Modules 0
Please see section

→ page A.4–80, All syngo Supported Image SOP Classes. 0.0
Siemens Standard Extended

Modules 0
Please see section

→ page A.4–77, Registry of DICOM Data Elements
and → page A.4–90, Registry of DICOM Data Elements. 0.0
0.0
Standard Extensions of all SOP

Classes 0.0
Please see section

→ page A.4–1, Standard Extensions of all SOP Classes 0.0
0.0
Version syngo CT 2014A ANNEX-1

July 2013
Appendix DICOM Conformance Statement
DICOM Print SCU-detailed status

displays 0
Please see section

→ page A.2–108, DICOM Print SCU - detailed status displays. 0.0
Additional DICOM Conformance

Statement for VSim 0
see document DICOM Conformance Statement VSim5.1.1. 0.0
0.0
ANNEX-2 DICOM Conformance Statement syngo

© 2013, Siemens AG Global Business Unit
Order No.
C2-023.610.16.01.02 Siemens AG
Printed in Germany Medical Solutions
07/2013 Computed Tomography & Radiation Oncology
Siemensstrasse 1
DE-91301 Forchheim
Germany
Phone: +49 9191 18-0
www.siemens.com/computedtomography
Global Siemens Headquarters Global Siemens Legal Manufacturer

Healthcare Headquarters
Siemens AG Siemens AG
Wittelsbacherplatz 2 Siemens AG Wittelsbacherplatz 2
80333 Muenchen Healthcare Sector DE-80333 Muenchen
Germany Henkestrasse 127 Germany
91052 Erlangen
Germany
Phone: +49 9131 840

CT 2014a

Uploaded by

Copyright:

Available Formats

CT 2014a

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CT 2014a

Uploaded by

Copyright:

Available Formats

syngo CT 2014A

DICOM Conformance Statement

The CE marking applies only to Medical Devices which have been

The original language of this document is English. 0.0

A DICOM Conformance Statement

A.3 Communication Profiles

A.6 Support of Extended Character Sets

B DICOM Conformance Statement

B.2 Application Entity Specifications

B.3 Augmented and Private Profiles

B.4 Extensions, Specializations and Privatizations of SOP

B.6 Support of Extended Character Sets

Version syngo CT 2014A 3

4 DICOM Conformance Statement syngo

This DICOM Conformance Statement is written according to part

The applications described in this conformance statement are

The Somaris/5 DICOM network implementation acts as SCU and

These services are described in "Part I". 0.0

The Somaris/5 DICOM Media Storage Service implementation

Somaris/5 is based on a Siemens common medical platform.

In this document parts of the Siemens common medical plat-

As Somaris/5 is a syngo based product, this DICOM Conform-

1. ’syngo’ and ’We speak syngo’ are registered trademarks of Siemens AG

Version syngo CT 2014A 5

This document is intended for hospital staff, health system inte-

6 DICOM Conformance Statement syngo

This DICOM Conformance Statement refers to Siemens

Siemens Product Software Name Internal

Sensation Cardiac 0 Somaris/5 syngo CT 2014A 0 VB42A 0

Sensation 64 0 Somaris/5 syngo CT 2014A 0 VB42A 0

Sensation Cardiac 64 0 Somaris/5 syngo CT 2014A 0 VB42A 0

Sensation 40 0 Somaris/5 syngo CT 2014A 0 VB42A 0

Sensation Open 0 Somaris/5 syngo CT 2014A 0 VB42A 0

Emotion Duo 0 Somaris/5 syngo CT 2014A 0 VB42A 0

Emotion 0 Somaris/5 syngo CT 2014A 0 VB42A 0

Emotion 6 0 Somaris/5 syngo CT 2014A 0 VB42A 0

Emotion 16 0 Somaris/5 syngo CT 2014A 0 VB42A 0

Emotion 6-slice configuration 0 Somaris/5 syngo CT 2014A 0 VB42A 0

Emotion 16-slice Somaris/5 syngo CT 2014A 0 VB42A 0

❏ DICOM: Digital Imaging and Communications in Medicine

Version syngo CT 2014A 7

Acronyms and Abbreviations 0.0

❏ ACR: American College of Radiology

8 DICOM Conformance Statement syngo

[1]: Digital Imaging and Communications in Medicine (DICOM)

[2]: syngo VE32B DICOM Conformance Statement 0.0

Version syngo CT 2014A 9

Connectivity and Interoperability 0.0

The implementation of the Somaris/5 DICOM interface has been

10 DICOM Conformance Statement syngo

Version syngo CT 2014A A-1

A-2 DICOM Conformance Statement syngo

The Verification service class defines an application-level class

The other direction – responding to Verification requests from

Application Data Flow Diagram A.0

The Somaris/5 DICOM network implementation acts as SCU for

DICOM Standard Interface

User Verification Verification

Functional Definitions of Application Entities A.0