l

e
k
n
u
R

DICOM
TD

Troubleshooting Guide
DICOM

Troubleshooting Guide DICOM

© Siemens AG 2004
The reproduction, transmission or use
of this document or its contents is not
permitted without express written
authority. Offenders will be liable for
damages. All rights, including rights
created by patent grant or registration
of a utility model or design, are
reserved.

Print No.: TD00-000.840.01.03.02 English

Replaces: TD00-000.840.01.02.02 Doc. Gen. Date: 06.04
2 Revision / Disclaimer
1Revision / Disclaimer

Document revision level

The document corresponds to the version/revision level effective at the time of system
delivery. Revisions to hardcopy documentation are not automatically distributed.
Please contact your local Siemens office to order current revision levels.

Disclaimer
The installation and service of equipment described herein is to be performed by qualified
personnel who are employed by Siemens or one of its affiliates or who are otherwise
authorized by Siemens or one of its affiliates to provide such services.
Assemblers and other persons who are not employed by or otherwise directly affiliated
with or authorized by Siemens or one of its affiliates are directed to contact one of the
local offices of Siemens or one of its affiliates before attempting installation or service pro-
cedures.

DICOM TD00-000.840.01.03.02 Page 2 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Table of Contents 3
1- 0Table of Contents

1 _______ Introduction ____________________________________________________ 5

2 _______ No Network Transfer _____________________________________________ 9

TCP / IP Ping Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Data Transfer to Remote System is Too Slow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
DICOM Verification Fails (C-Echo). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 _______ DICOM Storage ________________________________________________ 16

Image Transfer to Remote System Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Problem During the Association Negotiation (T3 level) . . . . . . . . . . . . . . . . . . . . . . 16
Problem with the Transferred Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Timeout Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Problems Caused by the Remote System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Image Transfer from Remote System to Local System Fails . . . . . . . . . . . . . . . . . . . . . 20
Problem with the Association Negotiation (T3 level). . . . . . . . . . . . . . . . . . . . . . . . . 20
Problem with Transfered Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Timeout Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Patient / Study Browser Presentation at the Local System is not Correct . . . . . . . . . . . 24
Image Presentation and Manipulation at the Local / Remote System is not Correct . . . 26

4 _______ DICOM Basic Print ______________________________________________ 31

Image Transfer to Camera Fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Problem with the Association Negotiation (T3 level). . . . . . . . . . . . . . . . . . . . . . . . . 31
Timeout Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Image Quality Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

5 _______ Storage Commitment ___________________________________________ 34

TBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

6 _______ Query/Retrieve _________________________________________________ 35

Query Matches are not Displayed Correctly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Association Negotiation Fails on the Patient Level or Study Level . . . . . . . . . . . . . . 35
No Query Response Message is Received (no matches) . . . . . . . . . . . . . . . . . . . . 36
Received Query Response Message is not Displayed at all . . . . . . . . . . . . . . . . . . 36
Received Query Response Message not Displayed Correctly . . . . . . . . . . . . . . . . . 37
Timeout Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Remote System cannot Handle Query Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Retrieve of Selected Data Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

7 _______ DICOM Worklist ________________________________________________ 39

No Worklist in Scheduler Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Problem with Received Worklist Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Missing Information in Worklist Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
DICOM Worklist Timeout Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Information System cannot Handle the Worklist Request. . . . . . . . . . . . . . . . . . . . . 41

Siemens AG TD00-000.840.01.03.02 Page 3 of 106 DICOM

Medical Solutions 06.04 CS SD 21
4 Table of Contents

8 _______ Modality Performed Procedure Step _______________________________ 42

9 _______ Media Storage _________________________________________________ 43

10 ______ Network Tests and Commands ___________________________________ 44

PING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Ping Out of Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Ping with DICOM Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Ping Out of Hardcopy Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Ping with <Utilities><Escape to OS>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Ping Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Netstat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Netstat Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Network Test Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
ping -l 50000 -n 10 <IP address> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
netstat -rn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
netstat -s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Syngo DICOM Test Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

11 ______ Appendix _____________________________________________________ 55

Merge Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Merge_stu.log - Storage Association T2, T3 and T7. . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Merge_hc.log - Print Association T2, T3 and T7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
DICOM UIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Status Messages in merge.log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
DICOM Attributes in the Command Set (T7 in the merge.log File) . . . . . . . . . . . . . . . . 100
Dicom e-learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

12 ______ Changes to Previous Version ____________________________________ 103

13 ______ Index ________________________________________________________ 104

DICOM TD00-000.840.01.03.02 Page 4 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Introduction 5
2-
1Introduction

The goal of this document is to provide a workflow oriented guide for DICOM trouble-
shooting. The Service Tools within syngo, including the DICOM Service Tools, are cur-
rently functionally oriented (this will be changed to workflow oriented in future versions).
DICOM Troubleshooting can be performed using 2 methods:
1. The Online method by using the tools and log files provided by the syngo Service Tools.
Online troubleshooting can be performed locally or remotely. For remote troubleshoot-
ing, in some cases it is necessary to have full access or even patient data access.
2. The Office method by using the Save mechanism provided by syngo (CT ALT S), and
the network capture ability provided by the MergeCOM tool kit in syngo.

In this guide you will be asked on several places to decide which method you will use.

Fig. 1: DICOM Workflow

When to use which method

1. The Online method should be used,
- For a quick check of the problem (check of event log, check of connectivity with
TCP/IP ping and DICOM verification)
- When a specialist is available (locally or remotely)
2. The Office method should be used,

Siemens AG TD00-000.840.01.03.02 Page 5 of 106 DICOM

Medical Solutions 06.04 CS SD 21
6 Introduction

- When the problem cannot be analyzed with the Online method

- When no specialist is available (just create a Save and perform a network capture
that will be uploaded the the US).
- When no remote access is possible (the Save and network capture can be trans-
ferred via e-mail).

Overview of the DICOM Troubleshooting Guide

The guide starts with a graphical overview of the troubleshooting procedures, which
allows you to jump easily to the required procedure.
• Chapter 2 (No network Transfer) describes how to deal with problems caused on the
network level. They are independent of the DICOM service.
• The next chapters are sorted by the DICOM services (Storage, Basic Print, Work,).
Depending on the problem, you will have to go to the respective chapter and follow the
instructions and hints. If the problem can not be fixed by means of these
troubleshooting instructions, you will usually have to escalate the problem to your US.
• Appendix A provides information about the log files which the USC/HSC needs for fur-
ther investigation.
• In Appendix B you will find examples of log files (including explanations) and several ta-
bles which are necessary to analyze the log files.
• Appendix “DICOM el-learning ” provides a Dicom self-learning tool.

Which skills are required for DICOM Troubleshooting?

This troubleshooting guide is organized in such a way that a modality specialist can per-
form troubleshooting up to a certain level. Only the DICOM service tools located on the
local system are required.
Typical tasks for the modality specialist are:
• Check the Event Log
• Perform a TCP/IP ping and DICOM verification using the DICOM Service Tools
• Check configuration
• Create a SaveLog (CTRL ALT S) and perform a network capture (edit mergecom.pro
file)

A DICOM specialist is required for detailed troubleshooting. CS TC provides a training

class for DICOM Troubleshooting. In addition to DICOM basics, instruction for all required
tools and log files is provided in this training class.
Typical tasks for the DICOM specialist are:
• Analyze network problems (TCP/IP, Ethernet, Router, Switch, )
• Analyze the DICOM log files
• Analyze Image header attributes
• Understand workflow and DICOM protocol

Which tools are required for DICOM Troubleshooting?

DICOM TD00-000.840.01.03.02 Page 6 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Introduction 7

It is a general strategy of Siemens to have as many tools as possible on the local system,
i.e., the Service Tools. However offline tools are required to analyze the network capture
or to simulate remote systems such as Information Systems (Worklist, MPPS) or cameras
(Print).
1. Syngo provides several local Service Tools (online), which are also remotely
accessible with the following capabilities:

Fig. 2: DICOM Test Tools service menu

• Turn on trace levels for the appropriate log files and display these files
• Capture images and film prints using a test receiver and analyze them (display, image
header dump, validation, comparison)
• TCP/IP ping and DICOM Verification (figure available)
• Send test images or captured images to any DICOM destination
• Create SaveLog file, including event log, configuration report and mergecom logs

2. Tools running on a PC to analyze a captured network transfer.

• The Merge DICOM Protocol Monitor (MergeDPM) is a very efficient tool to decode a
captured network transfer. It allows you to save images within this network capture as
an additional file.
• Network capturing can be done either using the MergeCOM tool kit on our syn-
go-based systems (beginning with syngo VD20), using the SUN snoop command pro-
vided by the MagicView1000 U or MagicStore or using a freeware tool for your laptop,
called Ethereal.
• To display and edit DICOM image files it is recommended to use DICOMEdit, which is
free for all Siemens employees.

Siemens AG TD00-000.840.01.03.02 Page 7 of 106 DICOM

Medical Solutions 06.04 CS SD 21
8 Introduction

• To validate DICOM images and DICOM Offline Media, in addition to DICOMEdit, it is

recommended to use a tool from the University of Oldenburg (Offis institute) called DC-
Mcheck, which is also freeware for all Siemens employees.
More details about the above mentioned tools can be found on the Siemens Intranet at
http://dicom.med.siemens.de under DICOM Test Tools.

3. Tools running on a PC to simulate DICOM Services, e.g. a RIS or Camera

• Simulation of DICOM Service Class users and providers can be performed using free-
ware tools such as JDICOM (Java-based) and the AX DICOM Tools (which uses the
Offis tools).
More details about the above mentioned tools can be found on the Siemens Intranet at
http://dicom.med.siemens.de under DICOM - Test Tools.

Which additional information is available for DICOM Troubleshooting?

• Together with the CS Training Center, a self-learn tool was developed -> DICOM
e-Learning, which can be found in the appendix of this guide.(Dicom
e-learning / p. 102)
• Known problems can be found in the CS Knowledge Base
• The Connectivity Competence Center (HS IM) provides an Intranet page
http://dicom.med.siemens.de with DICOM-relevant topics such as
- Links to Siemens and other vendor Conformance Statements
- DICOM Interoperability Database where you can search for test results
- Description of DICOM test tools
- Frequently Asked Questions

NOTE For DICOM troubleshooting on the specialist level, a Service PC

with a network card and the ability of installing service tools is ab-
solutely necessary!
DICOM troubleshooting may cover all systems in the clinical work-
flow. Movable and flexible tools are therefore necessary.

DICOM TD00-000.840.01.03.02 Page 8 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
No Network Transfer 9
3-
2No Network Transfer

All DICOM services are based on the TCP/IP network protocol and use the same mecha-
nism for the DICOM association negotiation and for the message transfer. This section
deals with problems in this area, which are independent of the particular DICOM service.
Start troubleshooting with TCP/IP ping and DICOM verification provided by the DICOM
service tools.

Probable Cause and Service Action Service Tool

• Network problems; Configuration problem; Process syngo: DICOM Service Tools
not started - Verify Network (C_ECHO)
¹ Perform TCP/IP ping and DICOM verification
¹ To verify if other remote systems are also not
reachable, perform DICOM verification for all
configured DICOM nodes.

Probable Cause and Service Action

Fig. 3: IP address conflict

• Check the TCP/IP configuration of the node itself
• Check the TCP/IP configuration of the other nodes

Siemens AG TD00-000.840.01.03.02 Page 9 of 106 DICOM

Medical Solutions 06.04 CS SD 21
10 No Network Transfer

TCP / IP Ping Fails 0

Error messages:
• UI: Connection failed because the remote node does not exist / no response from node
name
• Event log: Could not open association with remote node / service is unacceptable
• Merge log: E: TCP init error / timeout in select () call

Probable Cause and Service Action Service Tool

• Network problems; configuration problem; syngo: DICOM Service Tools
¹ Check appropriate merge.log file for 'TCP/IP - Analysis
init error' to verify that the problem is caused Examine logs: merge_stu.log.
on the network level. merge_hc.log, merge_HRI.log
• Wrong configuration on local system syngo: Configuration Tool -
¹ Check IP address, subnet mask and gateway DICOM
address in your configuration or with the oper- syngo: Utilities - Escape to
ating system command ' ipconfig /all ' OS -ipcponfig / all
• Link LED on network card is off: Cable not connect- Network administrator
ed at HUB or switch, crossover port at HUB syngo: Configuration Tool -
¹ Many network cards do not provide this link
LED.
¹ It might be necessary to remove PC housing
to see link LED (if it exists at all)
¹ On AXIOM Artis system there are 2 network
adapters. For troubleshooting purposes, it is
possible to swap the connectors and the con-
figuration.
• Problems with Domain Name Service (DNS) or syngo: Utilities - Escape to
wrong configuration OS, ping IP address
¹ Perform TCP/IP ping with IP address instead IP address can be found
of node name either in syngo: Configura-
tion Tool or under
C:\Winnt\system32 \driv-
ers\etc\hosts (lmhosts)
• Gateway not accessible or down (only if remote node syngo: Utilities, Escape to
belongs to another subnet) OS, ping gateway IP address
¹ Perform TCP/IP ping to the gateway

DICOM TD00-000.840.01.03.02 Page 10 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
No Network Transfer 11
Tab. 1 For DICOM specialist level

Probable Cause and Service Action Service Tool

• Gateway is incorrectly configured Network administrator
¹ Perform TCP/IP ping to both sides of the
gateway.
¹ Check gateway configuration
• Bad performance of the network because of many syngo: Utilities -Escape to OS -
collisions. netstat -s (netstat -e)
¹ Check for collisions and errors on the net- syngo: Utilities -Escape to OS -
work before and after a transfer. - ping -l 50000 -n 10 IP address
¹ Check performance with ping command. Network administrator

¹ On switched network, set 'auto negotiation

off' and manually set full duplex,100 Mbit/sec
• Problem in remote system Service engineer for remote
¹ Service engineer for the remote system system
should perform similar checks to localize the
problem
• Problem in remote system Laptop with network card
¹ Change IP address of your laptop to the one syngo: Utilities; Escape to OS,
for the remote system and connect it instead ping IP address
of the remote system.
¹ Perform TCP/IP ping

Siemens AG TD00-000.840.01.03.02 Page 11 of 106 DICOM

Medical Solutions 06.04 CS SD 21
12 No Network Transfer

Data Transfer to Remote System is Too Slow 0

Tab. 2

Probable Cause and Service Action Service Tool

• Check the configuration of the net-
work card.
Auto Detect could reduce the speed
because sometimes the negotiation
results in a transmission speed lower
than usual.
For ACOM.net environment, select
100MBps/Full Duplex.

Fig. 4: Network adapter, link speed setting

Association/Negotiation

DICOM TD00-000.840.01.03.02 Page 12 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
No Network Transfer 13

DICOM Verification Fails (C-Echo) 0

but TCP/IP ping is O.K.

Error messages:
• UI: No response from node name
• Event log: Could not open association with remote node / service not acceptable
• Merge log: E: TCP init error

Probable Cause and Service Action Service Tool

• AET or port number of remote system is wrong Configuration Tool
¹ Verify configuration DICOM Conformance State-
¹ Find AET and port number of remote system ment of remote system
in its Conformance Statement
• Remote process is not running syngo: Utilities - Escape to OS
¹ Perform command: telnet IP address telnet IP address port number
port number of the remote provider to (i.e. telnet syngo1 104)
check if any process is listening under this
port.
If no process is listening on the port, after a time-
out the message: 'Connection to host lost' ap-
pears
- If any process is listening on the port, you imme-
diately get the message: 'Connection failed /
Host Name: host name'
• Remote system does not support DICOM verifica- DICOM Conformance State-
tion (very seldom occurs) ment of remote system
¹ Check DICOM Conformance Statement if
remote system supports DICOM verification
as SCP
• Remote system is just a SCU; C_ECHO is usually DICOM Conformance State-
not supported ment of remote system
¹ Check DICOM conformance statement if
remote system is SCP.
It is not possible to perform DICOM verification to
an SCU!!

Siemens AG TD00-000.840.01.03.02 Page 13 of 106 DICOM

Medical Solutions 06.04 CS SD 21
14 No Network Transfer
Tab. 3 For DICOM specialist level

Probable Cause and Service Action Service Tool

• Any error on DICOM level syngo: DICOM Service Tools -
¹ Check appropriate merge.log file for error Analysis
message (see appendix) Examine logs:
merge_stu.log. merge_hc.log,
merge_HRI.log
• Local SCU does not send any TCP/IP packets or If a Unix (Solaris 2) system is
network switch does not forward DICOM verifica- available in the network -> com-
tion message mand: snoop IP
¹ Display the network traffic on TCP/IP level Unix (Sun OS) device available
and check if packets are sent to the appropri- in the network -> command:
ate IP address and port number. Beside LAN etherfind IP
analyzers, the tools on the right column pro- syngo: Utilities - Escape to OS
vide the ability to display network traffic. - netstat -n
Note that in a switched network the system which
syngo Operating system: Start
captures the traffic needs to be one of the two in-
- Programs - Administration -
volved systems or connected to one of the sys-
WindowsNT Diagnosis
tems via a HUB
• Network switch does not forward DICOM verifica- - Offis Toolkit (Uni Oldenburg,
tion message available on the Intranet -
¹ Unplug SCP and simulate remote device by DICOM - Tools):
your laptop. Enter the IP address of the SCP storescp -v -AET AET 104
at your laptop. - JDICOM: Store SCP
¹ Start the command shell and start a DICOM
storage provider store scp (syntax: storescp
-h) or JDICOM - Store SCP or any other stor-
age device that supports DICOM verification.

Error messages:
• UI: search platform: Logical name breaks down during searching
• Event log: Logical name breaks down during searching
• Merge log: E: Peer aborted association

Probable Cause and Service Action Service Tool

• Remote system might check our local AET while re- Service engineer for remote
ceiving a message. Our AET is not or not correctly system
configured at the remote system.
- Note: DICOM verification uses the AET for the
appropriate service, e.g. AN_NODENAME for
query destination and HRI_NODENAME for a
worklist destination.
- Contact service engineer for the remote system

If USC / HSC support is required:

DICOM TD00-000.840.01.03.02 Page 14 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
No Network Transfer 15

If no remote access for troubleshooting is possible and a specialist needs to analyze the
problem, he needs the output of the following files and commands:
%MEDHOME%\config\merge\mergecom.app
%MEDHOME%\log\merge_stu.log with trace level T2, T3 and T7 (for print merge_hc.log;
for HIS/RIS merge_HRI.log) and output of the following commands:
Service tools: Utilities - Escape to OS - NT Command Inerpreter - Parameter: netstat -r >
C:\Temp\netstat.txt
Service tools: Utilities - Escape to OS - NT Command Interpreter - Parameter: ipconfig /
all > C:\Temp\ipconfig.txt

Siemens AG TD00-000.840.01.03.02 Page 15 of 106 DICOM

Medical Solutions 06.04 CS SD 21
16 DICOM Storage
4-
Image Transfer to Remote System Fails
3DICOM Storage

Tab. 4 For DICOM Specialist level

Probable Cause and Service Action Service Tool

• Verify that the problem is not caused on network lev- syngo: DICOM Service Tools -
el as described (No network connection) in these in- Storage - Extend Trace Level
structions (AXA4-100.840.01...). syngo: DICOM Service Tools -
• Check how far the transfer succeeds and check for Analysis - Examine logs :
error messages at the end of the log file: merge_stu.log.

• Turn on the Trace level T2, T3 and T7 for the

merge_stu.log file and send one image again to the See example of a merge.log file and
remote system. the list of error messages in the
appendix. (AXA4-100.840.01...)

First T3 should show the Association Negotiation

Request and Response. Afterwards the command
set request should be displayed on T7. On T2, you
will again see the command set and also the image
header attributes should be displayed, and finally T7
should again display the response from the SCP.

Problem During the Association Negotiation (T3 level) 0

Error messages:
• UI: Session aborted by sender
• Event log: Session aborted by sender (40003) and service is unacceptable (30023)
• Merge log: E: T9: (Assoc_ABORT) send

DICOM TD00-000.840.01.03.02 Page 16 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
DICOM Storage 17
Tab. 5 For DICOM specialist level

Probable Cause and Service Action Service Tool /Person

• If the appropriate Presentation Context (im- DICOM Conformance Statement of
age and transfer syntax) is rejected in the re- remote system.
sponse of the Association Negotiation (on the Service engineer for the remote sys-
T3 level), it will not be supported by the provid- tem
er. The sender aborts the association.
- Check configuration on both sides and the
Conformance Statement of the remote sys-
tem.
• Wrong or missing command set request (T7 DICOM Conformance Statement of
level) both systems.
- Check if the correct command set is sent Service engineer for the remote sys-
during the T7 request. tem
If no T7 request is sent, the Association Ne-
gotiation (T3 level) might have failed.
In the case of extended negotiation (SCU /
SCP role others then 'not sent'), this feature
might not be supported by the SCU or SCP.

Problem with the Transferred Image 0

Probable Cause and Service Action Service Tool

• Status in the command set response (T7 lev- syngo: DICOM Service Tools - Storage -
el) is not '0'. Extend Trace Level

- Status '0' is successful transfer. syngo: DICOM Service Tools - Analysis -

Status 'A7xx' is out of resources, which Examine logs : merge_stu.log.
might be caused by an incorrect attribute in See list of status codes in the
the data set (T2 level). Appendix (AXA4-100.840.01...)
• Value representation of explicit VR transfer syngo: <Configuration> <DICOM>
syntax causes problems or <network nodes>
• JPEG Transfer Syntax cannot be decoded
- Enable another transfer syntax (just one) at
Service Configuration and send the image
again. Only the selected transfer syntax will
be used.

Siemens AG TD00-000.840.01.03.02 Page 17 of 106 DICOM

Medical Solutions 06.04 CS SD 21
18 DICOM Storage

Probable Cause and Service Action Service Tool

• Remote system reads the first image (or the
whole study), but it fails to enter it in its local
data base.
- Send other images, if possible acquired
from another modality or application.
Do not send 'Service images'. Another remote storage provider
- If possible, send image to another remote
system (SCP) and check if the transfer is
successful. DICOM Service Tools - Storage -
Send
- Send reference image via the DICOM Ser-
vice Tools. This is a validated image that will
be sent by the Test Send Process. There is
no interaction of the local data base and oth-
er processes. syngo: DICOM Service Tools - Stor-
age - Simulate remote receiver
- Start the test receiver and send image
again. The sent image will be captured on DICOM Service Tools - Analysis
the local system and can be analyzed using Service engineer of the remote sys-
the analysis tools (verify, header dump, dis- tem
play)
- Check error logs at the remote system

Timeout Problems 0

Tab. 6 For DICOM specialist level

Probable Cause and Service Action Service Tool

• Timeout in the middle of the message stream syngo: DICOM Service Tools -
- See merge_stu.log for error message: time- Analysis - Examine Logs:
out in the middle of the stream. merge_stu.log
- Increase the inactivity timeout under Config- syngo: Configuration Tool - DICOM
uration - General

• Timeout when waiting for a response for suc- syngo: DICOM Service Tools -
cessful transfer Analysis - Examine logs:
- See merge_stu.log for error message: time- merge_stu.log
out 'Read PDU timeout' syngo: Configuration Tool - DICOM
- Increase read PDU timeout under Configu- - General
ration

DICOM TD00-000.840.01.03.02 Page 18 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
DICOM Storage 19

Problems Caused by the Remote System 0

Tab. 7 Problems caused by the remote system. For DICOM specialist level

Probable Cause and Service Action Service Tool

• The remote system can not deal with the trans- Service PC:
ferred image. - Offis storescp -AET AET 104
- Connect your Service PC instead of the remote - JDICOM - Store SCP
system. Simulate remote system by using the
same IP address and start a storage provider with Be aware of the restrictions of
the same AET and port number. the test tools
Check whether the test tools are able to receive
the local images.
Display the received image with a viewer (Osiris,
ACRNview,...)

If USC / HSC support required:

If no remote access is possible and a specialist needs to analyze the problem, he needs
the following data:
1. If possible, the DICOM transfer must be captured by means of the Solaris 2 snoop com-
mand or by the NetXray LAN analyzer.
Please note that in a switched network, the system which is to capture the traffic needs
to be one of the two involved systems or connected to one of the systems via a HUB.
The captured file can be analyzed using the Merge DPM tool.
2. If capturing of the DICOM transfer is not possible, it is necessary for storage to capture
the transferred object (e.g. image) by means of the DICOM Service Tools. To do this,
start the DICOM Service Tools <Storage><Simulate remote receiver> and transfer the
object again.
3. In addition, the following log file is required: %MEDHOME%\log\merge_stu.log with
trace level T2, T3 and T7

Siemens AG TD00-000.840.01.03.02 Page 19 of 106 DICOM

Medical Solutions 06.04 CS SD 21
20 DICOM Storage

Image Transfer from Remote System to Local System Fails 0

Tab. 8 For DICOM specialist level

Probable Cause and Service Action Service Tool

• Configuration problem Configuration - DICOM - Network
- Check whether the remote system is cor- nodes
rectly configured at local system (Net-
work Nodes AXA4-100.843.01...)
• Verify that the problem is not caused on the
network level as described (No network
connection) in these instructions
(AXA4-100.840.01...).
• Check how far the transfer succeeds and syngo: DICOM Service Tools - Storage
look for error messages at the end of the log - Extend Trace Level
file: syngo: DICOM Service Tools - Analy-
Turn on the Trace level T2, T3, T7 and T9 sis - Examine logs : merge_stu.log.
for the merge_stu..log file and send one im- See list of status codes in the appendix
age again from the remote system. (AXA4-100.840.01...)
First T3 must show the Association Negoti-
ation Request and Response.
Afterwards the Command set request must
be displayed on T7.
On T2 you will again see the command set
and the image header attributes will also be
displayed and finally the T7 will again dis-
play the response from the local system.

Problem with the Association Negotiation (T3 level) 0

Error messages:
• UI: Session aborted by sender
• Event log: Session aborted by sender (40003) and service is unacceptable (30023)
• Merge log: E: T9: (Assoc_ABORT) received

DICOM TD00-000.840.01.03.02 Page 20 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
DICOM Storage 21
Tab. 9 Association Negotiation for DICOM specialist level

Probable Cause and Service Action Service Tool

• If the appropriate Presentation Context is re- DICOM Conformance Statement of
jected in the response of the Association Ne- remote system.
gotiation (on T3 level), it will not be supported Service engineer for the remote sys-
by the provider. The sender aborts the associ- tem
ation.
- Check configuration on both sides and the
Conformance Statement of the remote sys-
tem.
• Wrong or missing command set request (T7 DICOM Conformance Statement of
level) both systems.
- Check if the correct command set was sent Service engineer for the remote sys-
during the T7 request. tem
If no T7 request was sent, the Association
Negotiation (T3 level) may have failed.
In case of Extended negotiation (SCU / SCP
role others then 'not sent') this feature may
not be supported by the SCU or SCP.

Problem with Transfered Image 0

Probable Cause and Service Action Service Tool

• Status in the command set response (T7 level) is See list of status codes in the
not '0'. appendix (AXA4-100.840.01...)
- Status '0' is successful transfer.
- Status 'A7xx' is out of resources which might be
caused by a wrong attribute in the data set (T2
level).
• Value Representation of Explicit Transfer Syntax syngo: DICOM Service Tools -
causes problems (if sent) or is required (if not sent). Storage - Extended Trace -
JPEG Transfer Syntax cannot be decoded. Transfer Syntax

- Change to another transfer syntax and send the

message again.
Only the selected transfer syntax will be used.

Siemens AG TD00-000.840.01.03.02 Page 21 of 106 DICOM

Medical Solutions 06.04 CS SD 21
22 DICOM Storage

Probable Cause and Service Action Service Tool

• Local system reads the first image (or the whole
study) but it fails to enter it in its local data base
¹ Send other images, if possible acquired at
another modality or application.
¹ If possible, send image from another remote Another remote Storage User
system (SCP) and check if the transfer is
successful.
syngo: DICOM Service Tools -
¹ Start the test receiver and send image again. Storage - Simulate local
The sent image will be captured on local sys- receiver
tem and can be analyzed by the analysis
tools (verify, header dump, display) syngo: DICOM Service Tools -
Analysis
¹ Check error log of the study server (local
system) syngo: DICOM Service Tools -
Analysis - examine logs

Timeout Problems 0

Tab. 10 For DICOM specialist level

Probable Cause and Service Action Service Tool

• Timeout in the middle of the message stream syngo: DICOM Service Tools -
¹ See merge_stu.log for error message: time- Analysis - Examine Logs
out in the middle of the stream. syngo: Configuration Tool -
¹ Increase Inactivity Timeout under Configura- DICOM
tion.
• Timeout while waiting for a response of successful syngo: DICOM Service Tools -
transfer Analysis - Examine logs:
¹ See merge_stu.log for error message: time- merge_stu.log
out 'Read PDU timeout'. syngo: Configuration Tool -
¹ Increase Read PDU timeout under Configu- DICOM
ration.

If USC / HSC support is required:

If no remote access is possible and a specialist needs to analyze the problem, he needs
the following data:
1. Preferably the DICOM transfer should be captured by means of the Solaris 2 snoop
command, Ethereal or by the NetXray Lan Analyser. See introduction to these trouble-
shooting instructions.
Please note that in a switched network, the system which captures the traffic needs to
be one of the two involved systems or connected to one of the systems via a HUB. The
captured file can be analyzed by the Merge DPM tool.

DICOM TD00-000.840.01.03.02 Page 22 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
DICOM Storage 23

2. If capturing of the DICOM transfer is not possible, it is required for Storage to capture
the transferred object (e.g. image) by means of the DICOM Service Tools. To do this,
start the DICOM Service Tools <Storage><Simulate remote receiver> and transfer the
object again.
3. In addition, the following log file is required: %MEDHOME%\log\merge_stu.log with
trace level T2, T3 and T7

Siemens AG TD00-000.840.01.03.02 Page 23 of 106 DICOM

Medical Solutions 06.04 CS SD 21
24 DICOM Storage

Patient / Study Browser Presentation at the Local System is not

Correct 0

Tab. 11 For DICOM specialist level

Probable Cause and Service Action Service Tool

Text in Patient Browser is not display in correct charac- syngo: Configuration -
ters DICOM - Character Set
• Attribute 0008,0005 ‘Specific Character Set’ is missing or Configuration for charac-
wrong. ter set of the sending sys-
If it is missing the system usually asumes that the ASCII tem.
character set is used.
If the ASCII character set does also not fit, the system
tries to interprete the image with the Latin1 (ISO IR100)
character set.
¹ The modality or the sending system needs to enter
the correct attribute 0008,0005.
For more details see the Service Online Help -
Configuration - Character Set.
The same patient occurs several times in the patient syngo: DICOM Service
browser Tools - Storage - Simulate
• A patient will be uniquely identified by the 'patient's name, local / remote receive
patient ID, patient sex and date of birth. syngo: DICOM Service
If one of these attributes is different in an image, the local Tools - Analysis - Dump
system assumes that the patient is different. message

If one or more of these 4 attributes is missing, the system

assumes that the patient is not the same, even if all other
attributes are filled in with the same value.
¹ Start the test receiver and send the study again,
which is not correctly displayed in the patient/study
browser. The sent images will be captured on the
local system and the image header can be ana-
lyzed by the analysis tool 'dump message' For fur-
ther details on troubleshooting, see the following
hints
¹ Check whether the difference in the attributes can
be avoided at the RIS or modality.
All 4 attributes must have a value!

DICOM TD00-000.840.01.03.02 Page 24 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
DICOM Storage 25

Probable Cause and Service Action Service Tool

Images from the same study are not located in the same syngo: DICOM Service
study in the patient browser Tools - Storage - Simulate
• The matching criteria for a study is the attribute local / remote receive
0020,000d 'Study Instance UID'. This attribute is created syngo: DICOM Service
by the HIS/RIS or by the modality and needs to be the Tools - Analysis - Dump
same for all images that belong to the same study. message
The Requested Procedure ID (0040,1001), which is also
created by the HIS/RIS, also needs to be the same.
¹ Start Test receiver and send the study again,
which is not correctly displayed in the patient/study
browser. The sent images will be captured on the
local system and the image header can be ana-
lyzed using the Analysis tool 'dump message' For
further details on troubleshooting, see the follow-
ing hints
¹ Check whether 0020,000d and 0040,1001 is dif-
ferent for the affected images. The 4th number in
this UID defines the creator of the UID, whereby
1107 is Siemens.
Series splitting is not o.k. syngo: DICOM Service
• The DICOM standard does not define when a new series Tools - Storage - Simulate
needs to be created. This task is always in charge of the local / remote receive
local system. Series splitting of the same study can be syngo: DICOM Service
different on different systems. Tools - Analysis - Dump
¹ Contact the USC to investigate this problem. See message
in the Intranet under http://dicom.med.sie-
mens.de - Siemens products for the rules regard-
ing the particular product.
The same image appears several times in the browser
• An image will be identified by the SOP Instance UID
(0008,0018).
If this attribute is different the image will be recognized by
the system as a different image.
¹ Check the attribute 0008,0018. In this UID you can
usually find out who created the image (4th value,
1107 is Siemens).

Siemens AG TD00-000.840.01.03.02 Page 25 of 106 DICOM

Medical Solutions 06.04 CS SD 21
26 DICOM Storage

Image Presentation and Manipulation at the Local / Remote

System is not Correct 0

Tab. 12 For DICOM Specialist level

Probable Cause and Service Action Service Tool

Image Text does not display correct characters syngo: DICOM Service
• Attribute 0008,0005 'Specific Character Set' is missing. In Tools - Storage - Simu-
this case, the system usually assumes that the ASCII char- late local / remote
acter set is used. receive

If the ASCII character set also does not fit, the system tries syngo: DICOM Service
to interpret the image with the Latin1 (ISO IR100) charac- Tools - Analysis - Dump
ter set. message

- Start the test receiver and the send image again. The
sent image will be captured on local system and the im-
age header can be analyzed using the Analysis tool
'dump message'. For further details on troubleshooting,
see the following hints.
- The modality or the sending system needs to enter the
correct attribute 0008,0005. . For more details, see Ser-
vice Online Help - Configuration - Character Set.
Windowing not correct syngo: DICOM Service
• The attributes 0028,1051 'Window Width' and 0028,1052 Tools - Storage - Simu-
'Window Center' are just optional for most image objects in late local / remote
DICOM. If these attributes are missing, syngo enters the receive
default value 100 into these attributes, which causes a dark syngo: DICOM Service
image. Tools - Analysis - Dump
¹ Start Test receiver and the send image again. The message
sent images is captured on local system and the
image header can be analyzed using the Analysis
tool 'dump message'. For further details on trouble-
shooting, see the following hints.
¹ As a workaround, you can set the default window
values under: Options - Configuration - Viewer.
Under Image - Windowing you can select one of
these configured default window values.
• For CT images, the attribute 0028,1052 'Rescale Intercept'
is sometimes ignored by non-Siemens viewers. This leads
to a window center value that is skipped by 1024 Hounds-
field values.
¹ Inform the service engineer for the remote system

DICOM TD00-000.840.01.03.02 Page 26 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
DICOM Storage 27

Probable Cause and Service Action Service Tool

• The attribute 0028,1053 'Rescale Slope' needs to be an in- syngo: DICOM Service
teger value for syngo based system. Otherwise it will not be Tools - Storage - Simu-
correctly interpreted and leads to poor image quality and late local / remote
incorrect window value interpretation. receive
¹ Call USC syngo: DICOM Service
• The image can have several Look Up Table sequences Tools - Analysis - Dump
(LUTs) which need to be used for image display. Check if message
any LUT is included in the image header and if the system
supports this LUT (Modality LUT sequence (0028,3000)
and VOI LUT sequence (0028,3010))
¹ Check DICOM Conformance Statements of the par-
ticular system. Syngo based systems shall use the
LUTs correctly.
Image is distorted (oval shape instead of circle) syngo: DICOM Service
• Attribute 0028,0034 'Pixel Aspect Ratio' is not 1/1. If this at- Tools - Storage - Simu-
tribute is missing, the system usually assumes that the pix- late local / remote
el size is squared. receive

¹ Start Test receiver and send the image again. The syngo: DICOM Service
sent images will be captured on local system and Tools - Analysis - Dump
the image header can be analyzed using the Analy- message
sis tool 'dump message'. For further details on trou-
bleshooting, see the following hints
¹ The system may not be able to display non-squared
pixel sizes.
Change the pixel aspect ratio in the modality to a
squared pixel size.

Siemens AG TD00-000.840.01.03.02 Page 27 of 106 DICOM

Medical Solutions 06.04 CS SD 21
28 DICOM Storage

Probable Cause and Service Action Service Tool

Overlay missing syngo: DICOM Service
• The overlay data are defined in the image header group Tools - Storage - Simu-
6000. If attributes in group 6000 are missing, the system late local / remote
cannot display overlays such as annotations, distance receive
measurements and ROIs. syngo: DICOM Service
¹ Start Test receiver and the send image again. The Tools - Analysis - Dump
sent images will be captured on local system and message
the image header can be analyzed using the Analy-
sis tool 'dump message'
¹ Inform the service engineer for the remote system
• The system does not support overlays at all (such as 3D
Virtuoso).
¹ Start Test receiver and send the image again. The
sent images will be captured on local system and
the image header can be analyzed using the Analy-
sis tool 'dump message'
¹ Check the Conformance Statement for the particular
system. The local system must support overlays.
• The overlay data in the group 6000 can be entered in 2 syngo: DICOM Service
ways: Tools - Storage - Simu-
1. Overlay data are in the attribute 6000.3000. In this case late local / remote
the attributes 6000.0100 'Overlay Bits Allocated' and receive
6000.01002 'Overlay Bit Position' need to have the value syngo: DICOM Service
'1'. Tools - Analysis - Dump
2. Overlay data are part of the image pixel data. Group message
6000 only points to the bit position where the overlay data
are located. In this case, 6000.3000 does not exist and
6000.0100 needs to be equal to 0028,0100 'Bits Stored'.
6000.0102 will show the bit position of the overlay data.
¹ Check if the attributes are filled in according to the
left table column (Probable Cause).

DICOM TD00-000.840.01.03.02 Page 28 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
DICOM Storage 29

Probable Cause and Service Action Service Tool

Instead of metric values the number of pixels is displayed syngo: DICOM Service
• The system needs to know the size of a pixel. Therefore Tools - Storage - Simu-
the following attributes are required (depending on the im- late local / remote
age type) receive

- CT, MR, PET, NM: 0028,0030 'Pixel Spacing' is the physi- syngo: DICOM Service
cal distance between the center of each pixel. Tools - Analysis - Dump
message
- CR, DX, : 0018,1164 'Image Pixel Spacing' is the physi-
cal distance measured on the front plane of the image re-
ceptor housing between the center of each pixel. This is not
the physical distance in the body!
- US: 0018,6024 to 0018,602E 'Physical Units X/Y Direc-
tion' and 'Physical Delta X/Y' are required.
Some US devices use the attribute 'Pixel Spacing'
(0028,0030), although this attribute is not defined for US
objects. Syngo based systems do not accept this value!
- RT: 3002,0011 'Image Plane Pixel Spacing' is the physi-
cal distance between the center of each pixel. Although RT
images are protection images (such as CR and DX), the
value is the physical distance in the body. The attribute
3002,0026 'RT Image SID' is required to calculate the cor-
rect value for 3002.0011. RT Image SID is the distance
from radiation machine source to image plane along the ra-
diation beam axis.
¹ Start Test receiver and the send image again. The
sent image will be captured on the local system and
the image header can be analyzed using the analy-
sis tool 'dump message'
¹ Check if the appropriate attribute is available. For
further investigation, call the USC / HSC.
Shutter is missing syngo: DICOM Service
• Shutter information needs to be written into the attributes Tools - Storage - Simu-
0018,1600 - 0018,1620. late local / remote
receive
Some systems write the shutter information into private
header attributes (which are unknown to other systems). syngo: DICOM Service
Tools - Analysis - Dump
¹ Start Test receiver and the send image again. The message
sent image will be captured on local system and the
image header can be analyzed by the Analysis tool
'dump message'
¹ Check whether the appropriate attributes are avail-
able. If yes, verify in the corresponding DICOM Con-
formance Statement whether 'Display Shutter' is
supported. The local system must support this func-
tionality.

Siemens AG TD00-000.840.01.03.02 Page 29 of 106 DICOM

Medical Solutions 06.04 CS SD 21
30 DICOM Storage

Probable Cause and Service Action Service Tool

Zoomed image is displayed in the original size syngo: DICOM Service
• Until 'Presentation State Object', the DICOM standard did Tools - Storage - Simu-
not define any attribute to set the zoom factor. Up to this late local / remote
time, either the zoomed image was saved as a new image receive
at the image creator, or the zooming information was sent syngo: DICOM Service
in a private attribute (which is unknown to other systems). Tools - Analysis - Dump
¹ Start Test receiver and send the image again. The message
sent image will be captured on local system and the DICOM Conformance
image header can be analyzed using the analysis Statement
tool 'dump message’
¹ The zoomed image needs to be saved with the new
pixel data at the sending system (image creator).
Color images are not displayed correctly syngo: DICOM Service
• Syngo based systems just support 'RGB' and 'Palette col- Tools - Storage - Simu-
or' images.YBR images are not supported - image is black. late local / remote
RGB images with the value 1 for 'Planar Configuration' receive
(0028,0006) will not be supported - image appears several syngo: DICOM Service
time with the wrong colors. Tools - Analysis - Dump
¹ Start Test receiver and send image again. The sent message
image will be captured on local system and the DICOM Conformance
image header can be analyzed using the analysis Statement
tool 'dump message'
¹ Check the attribute 'Photometric Interpretation'
(0028,0004) and 'Planar Configuration' (0028,0006).
• Color images transferred in JPEG compression mode may
be displayed incorrectly.
- Send images in non-compressed mode. This problem
will be solved in one of the next releases.
Multiframe images are not displayed correctly syngo: DICOM Service
• Multiframe images sent in compressed (JPEG) mode may Tools - Storage - Simu-
not be displayed correctly. late local / remote
receive
¹ Start Test receiver and send image again. The sent
image will be captured on local system and the syngo: DICOM Service
image header can be analyzed by the analysis tool Tools - Analysis - Dump
'dump message' message

¹ Multiframe images can be identified by the attribute DICOM Conformance

'Number of Frames' (0028,0008), which should have Statement
a value higher than 1.
The compression mode can be seen in the attribute
'Derivation Description' (0008,2111).
This problem will be solved in one of the next
releases.

DICOM TD00-000.840.01.03.02 Page 30 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
DICOM Basic Print 31
5-
Image Transfer to Camera Fails
4DICOM Basic Print

Tab. 13 For DICOM specialist level

Service Action Service Tool

• Verify that the problem is not caused on the net- syngo: DICOM Service Tools -
work level as described (No network connection) Basic Print - Extend Trace Level
in these instructions (AXA4-100.840.01...). syngo: DICOM Service Tools -
• Check how far the transfer succeeds and for error Analysis - Examine logs:
messages at the end of the log file: merge_hc.log.
• Turn on the Trace level T2, T3, T7 and T9 for the See example of a merge.log file
appropriate merge.log file and send one image and the list of error messages in
again from the customer User Interface the appendix.
• First T3 will show the Association Negotiation Re-
quest and Response.
First T3 will show the Association Negotiation Re-
quest and Response. Afterwards several Meta
Services (Film Session, Film Box, Image Box) will
be performed one by one.

Problem with the Association Negotiation (T3 level) 0

Probable Cause and Service Action Service Tool

• The camera might have limited open DICOM asso- Service engineer of the camera
ciations. As some modalities always keep the ses-
sion open, this limit can be reached when more
than 3 modalities are connected to a camera.
¹ Check how many modalities are connected
to the camera. Assistance from the camera
vendor’s service engineer may be neces-
sary.

Siemens AG TD00-000.840.01.03.02 Page 31 of 106 DICOM

Medical Solutions 06.04 CS SD 21
32 DICOM Basic Print

Probable Cause and Service Action Service Tool

• The local system does not send any messages to syngo: DICOM Service Tools - Basic
the camera Print - Extend Trace Level
¹ Simulate the camera using the DICOM Ser- syngo: DICOM Service Tools - Anal-
vice Tools and send an image to the cam- ysis - Examine logs :
era. Then go to Analyze, check the merge_hc.log.
merge_hc.log file and display the transferred
pixel data.
• Camera can not deal with transferred messages Service PC: - JDICOM - Print
¹ Connect your Service PC instead of the Server- Osiris, ACRNview, Be
camera. Simulate the camera by using the aware of the restrictions of the
same IP address and start a camera server Test tools
with the same AET and port number. Check
whether the test tool is able to receive the
images.
¹ Display the received image using a viewer
(Osiris, ACRNview).

Timeout Problems 0

Tab. 14 Timeout problems for DICOM specialist level

Probable Cause and Service Action Service Tool

• Timeout in the middle of the message stream. syngo: DICOM Service Tools -
¹ See merge_hc.log for error message: time- Analysis - Examine Logs:
out in the middle of the stream. merge_hc.log

¹ Increase Inactivity Timeout under Configura- syngo: Configuration Tool -

tion DICOM - General

• Timeout when waiting for a response of successful syngo: DICOM Service Tools -
transfer. Analysis - Examine logs:
¹ See merge_hc.log for error message: time- merge_hc.log
out 'Read PDU timeout' syngo: Configuration Tool -
¹ Increase Read PDU Timeout under Configu- DICOM - General
ration.

DICOM TD00-000.840.01.03.02 Page 32 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
DICOM Basic Print 33

Image Quality Problems 0

Probable Cause and Service Action Service Tool

• Wrong or no LUT configured at the local system syngo: Configuration Tool - LUT
for the appropriate image type.
¹ Check whether a LUT is configured for the
appropriate image type (e.g. CR, MR,... )
• Camera does or does not support the Presenta- syngo: Configuration Tool - LUT
tion LUT (Gray scale Display Standard Function)
¹ Check whether the camera supports the
DICOM Gray scale Display Standard Func-
tion and whether it is set this way.
¹ Check whether the presentation LUT needs
to be configured at the local system.
¹ Check whether the correction LUT needs to
be configured at the local system.
For more details, see DICOM Service Online
Help - LUT
• The camera compares the AET of the transferred Service engineer for the camera
message (local AET of the sender) with the one
configured for this sender at the camera. Depend-
ing on the AET, a Look Up Table LUT (usually lin-
ear LUT) is set.
¹ Check whether the local AET is correctly
configured at the camera
• Any local configuration settings are not correct for syngo: Configuration Tool - LUT
the camera. syngo: Configuration Tool - Print
¹ Change the configuration settings such as devices
image interpolation, min / max density to
improve the image quality. Please note that
these settings are validated for the released
cameras and it is not necessary to modify
them.

If no remote access for troubleshooting is possible and a specialist needs to analyze the
problem, he will need the following data:
1. Preferably, the DICOM transfer will be captured by means of the Solaris 2 snoop com-
mand, Ethereal or by the NetXray LAN Analyzer. See Introduction to these trouble-
shooting instructions.
Please note that in a switched network the system which captures the traffic needs to
be one of the two involved systems or connected to one of the systems via a HUB. The
captured file can be analyzed using the Merge DPM tool.
2. If capturing of the DICOM transfer is not possible, the following log file is required:
%MEDHOME%\log\merge_hc.log with trace level T2, T3 and T7.

Siemens AG TD00-000.840.01.03.02 Page 33 of 106 DICOM

Medical Solutions 06.04 CS SD 21
34 Storage Commitment
6-
TBD
5Storage Commitment

DICOM TD00-000.840.01.03.02 Page 34 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Query/Retrieve 35
7-
Query Matches are not Displayed Correctly
6Query/Retrieve

Tab. 15 For DICOM specialist level

Probable Cause and Service Action Service Tool

• Verify that the problem is not caused on the network lev- syngo: DICOM Service
el as described in chapter (No network connection) of Tools - Query/Retrieve -
these instructions (AXA4-100.840.01..). Extend Trace Level
Check how far the transfer succeeds and for error mes- syngo: DICOM Service
sages at the end of the log file: Tools - Analysis - Exam-
ine logs: merge_stu.log.
Turn on the Trace level T2, T3 and T7 for the See example of a
merge_stu.log file and perform a query request again merge.log file (Storage)
from the customer User Interface and the list of error mes-
- First T3 will show the Association Negotiation Re- sages in the appendix.
quest and Response. Then the Command set request
will be displayed on T7.
The requested attributes will be displayed on T2. A
command set with status pending on T7 and the re-
sponded data on T2 will be displayed for each match-
ing query response.
Finally, T7 will display the status 0 = success.

Association Negotiation Fails on the Patient Level or Study Level 0

Error messages:
• UI search platform: Could not establish connection to the node name
• Event log: Could not establish connection to the node name
• Merge log: E: Association rejected; permanent rejection
Tab. 16 For DICOM specialist level

Probable Cause and Service Action Service Tool

• If the remote system is configured with 'Patient Root' syngo: Configuration -
model AND 'Study Root' model but supports only one of DICOM - Network nodes
these Q/R models, the Query Request fails.When both
services are configured, syngo-based systems will start
on the patient level with 'Patient Root' and continue with a
new Association Negotiation on the study level using
'Study Root'.
- Configure only the query model that is supported by
the remote system.

Siemens AG TD00-000.840.01.03.02 Page 35 of 106 DICOM

Medical Solutions 06.04 CS SD 21
36 Query/Retrieve

No Query Response Message is Received (no matches) 0

Probable Cause and Service Action Service Tool

• There is no patient at the remote system that matches syngo: DICOM Service
the query request - No response on T2 level. Tools - Analysis -
- Check the query request on T2 level. Examine logs:
- Enter an exact patient name into the search platform merge_stu.log..
and search again.
- Enter an exact patient ID into the search platform and
search again.

Received Query Response Message is not Displayed at all 0

Probable Cause and Service Action Service Tool

• Query matches are transferred (see responses on T2 syngo: DICOM Service
level) but they are not displayed in the matching list of the Tools - Analysis -
customer UI. Examine logs:
¹ Check the query response on T2 level. If unknown merge_stu.log.
(not requested) attributes are in the response
message, the local system may not accept this
message.
• Status in the command set response (T7 level) is not See list of status codes in
pending or success. the appendix.
¹ Status '0' is successful transfer.Status 'HFF00' or
'HFF01' / Decimal 65280 or 65281 is pending (fur-
ther responses will follow). Status 'A7xx' is out of
resources which might be caused by an incorrect
attribute in the data set (T2 level).
• Value Representation of Explicit Transfer Syntax causes DICOM Service Tools -
problems (if sent) or is required (if not sent). Query/Retrieve -
¹ Change to another transfer syntax and send the Extended Trace - Transfer
message again. Only the selected transfer syntax Syntax.
will be used.
• Problem caused at the remote system. Service engineer of the
¹ Check the error logs at the remote system remote system

DICOM TD00-000.840.01.03.02 Page 36 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Query/Retrieve 37

Received Query Response Message not Displayed Correctly 0

Probable Cause and Service Action Service Tool

• Incorrect character set syngo: DICOM Service
¹ Check the query response on T2 level. If no Tools - Analysis -
attribute 0008,0005 (Special Character Set) is Examine logs:
included, the local system assumes that the merge_stu.log.
default character set (ASCII) is used.
• Not all matches are displayed syngo: DICOM Service
¹ The application accepts only a certain amount of Tools - Analysis -
matches in the response message Examine logs:
merge_stu.log.

Timeout Problems 0

Probable Cause and Service Action Service Tool

• Timeout in the middle of the message stream syngo: DICOM Service
¹ See merge_stu.log for error message: timeout in Tools - Analysis -
the middle of the stream. Examine logs:
¹ Increase Inactivity Timeout under Configuration merge_HRI.log
syngo: Configuration
Tool - DICOM - General
• Timeout when waiting for a response for successful syngo: DICOM Service
transfer.The remote system is not able to find data ac- Tools - Analysis -
cording to the query request - performance problems Examine logs:
¹ See merge_stu.log for error message: timeout merge_HRI.log.
'Read PDU timeout' syngo: Configuration
¹ Increase Read PDU Timeout under Configuration Tool - DICOM - General

Remote System cannot Handle Query Request 0

Probable Cause and Service Action Service Tool

• The remote system (query SCP) can not handle the que- Service PC: - JDICOM -
ry request Query Server GUI
- Connect your Service PC instead of the remote sys-
tem. Simulate the remote system by using the same IP
address and start a Query Provider with the same AET
and port number. Check whether the test tools are able
to handle the query request.

Siemens AG TD00-000.840.01.03.02 Page 37 of 106 DICOM

Medical Solutions 06.04 CS SD 21
38 Query/Retrieve

Retrieve of Selected Data Fails 0

Probable Cause and Service Action Service Tool

Verify that the problem is not caused on the network level as syngo: DICOM Service
described in chapter 1 of these instructions. Check how far Tools - Analysis -
the transfer succeeds and for error messages at the end of Examine logs:
the log file: Turn on the Trace level T2, T3, T7 and T9 for the merge_stu.log.
appropriate merge.log file and perform a query / retrieve
request again from the customer User Interface. Look for
the C_MOVE request and check the log file from this point
on.
• C_MOVE request fails
¹ Check the AETs in the C_MOVE request.
• C_STORE fails
¹ The C_MOVE request (retrieve) initiates a
C_STORE request (send selected images on a
separate association with DICOM Storage Ser-
vice). Send the selected images from the remote
system to the local system (not via query/retrieve).
This transfer needs to be successful to get a suc-
cessful C_MOVE request. If there are problems,
see 2.2 Image transfer from remote system fails.

If USC / HSC support required: If no remote access for troubleshooting is possible and a
specialist needs to analyze the problem, he needs the following data:
1. Preferably, the DICOM transfer is captured by means of the Solaris 2 snoop command,
Ethereal or by the NetXray Lan Analyzer. See Introduction to these troubleshooting in-
structions.
Please note that in a switched network, the system which captures the traffic needs to
be one of the two involved systems or connected to one of the systems via a HUB. The
captured file can be analyzed using the Merge DPM tool.
2. If capturing the DICOM transfer is not possible, the following log file is required: %MED-
HOME%\log\merge_stu.log with trace level T2, T3 and T7.

DICOM TD00-000.840.01.03.02 Page 38 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
DICOM Worklist 39
8-
No Worklist in Scheduler Database
7DICOM Worklist

Service Action Service Tool

• Verify that the problem is not caused on the net- syngo: DICOM Service Tools -
work level as described (No network connection) in Worklist - Extend Trace Level
these instructions (AXA4-100.840.01...). syngo: DICOM Service Tools -
• Check how far the transfer succeeds and for error Analysis - Examine logs :
messages at the end of the log file: merge_HRI.log.
• Turn on the Trace level T2, T3, T7 and T9 for the
appropriate merge.log file and send one image See example of a merge.log file
again from the customer User Interface. (Storage) and the list of error
• First T3 will show the Association Negotiation Re- messages in the appendix.
quest and Response. Afterwards the Command set
request will be displayed on T7.
The requested attributes will be displayed on T2. A
command set with status pending on T7 and the re-
sponded data on T2 for each matching worklist re-
sponse will be displayed.
Finally T7 will display the status 0 = success.

Problem with Received Worklist Message 0

Probable Cause and Service Action Service Tool

• There is no scheduled patient at the information syngo: DICOM Service Tools -
system that matches the worklist request - No re- Analysis - Examine logs:
sponse on T2 level. merge_HRI.log.
¹ Check the worklist request on the T2 level.
You will find values such as AET, modality
and study date/time. Compare this data with
the data scheduled in the Information System
(assistance from Information System com-
pany might be necessary).
• Worklist matches will be transferred (see respons- syngo: DICOM Service Tools -
es on T2 level) but no worklist will be displayed in Analysis - Examine logs:
the scheduler data base. merge_HRI.log.
¹ Check the worklist response on the T2 level.
If a mandatory attriubte is missing, the
scheduler data base will not accept the
received message.
Test using JDICOM, Error messages, also
application error messages

Siemens AG TD00-000.840.01.03.02 Page 39 of 106 DICOM

Medical Solutions 06.04 CS SD 21
40 DICOM Worklist

Probable Cause and Service Action Service Tool

• Status in the command set response (T7 level) is See list of status codes in the
not pending or successful. appendix
¹ Status '0' is successful transfer.
¹ Status 'HFF00' or 'HFF01' / Decimal 65280 or
65281 is pending (further responses will fol-
low)
¹ Status 'A7xx' is out of resources which might
be caused by an incorrect attribute in the
data set (T2 level).
• Value Representation of Explicit Transfer Syntax syngo: DICOM Service Tools -
causes problems (if sent) or is required (if not sent). Worklist - Extended Trace -
¹ Change to another transfer syntax and send Transfer Syntax
the message again. Only the selected trans-
fer syntax is used.
¹ Check the error logs at the information sys- Service engineer for the Infor-
tem mation System

Missing Information in Worklist Response 0

Error messages:
• UI: Missing Information - mandatory study info missing
• Event log: operation failed, mapping failed

Probable Cause and Service Action Service Tool

• Worklist matches will be transferred (see responses syngo: DICOM Service Tools
on T2 level) and are visible in the scheduler data- - Analysis - Examine logs:
base. merge_HRI.log.application:
As soon as a scheduled patient is registered, a mes- Scheduler - select patient ->
sage appears that a mandatory attribute is missing. Registration platform will be
opened
¹ Open the registration platform (with continue)
and check which attributes are not filled in.
¹ Check merge_HRI.log with trace level T2.
Here you will find the requested and the
responded worklist attributes.

DICOM Worklist Timeout Problems 0

Error messages:
• UI:
• Event log:
• Merge log: E:

DICOM TD00-000.840.01.03.02 Page 40 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
DICOM Worklist 41
Tab. 17 Timeout problems for DICOM specialist level

Probable Cause and Service Action Service Tool

• Timeout in the middle of the message stream syngo: DICOM Service Tools
¹ See merge_HRI.log for error message: time- - Analysis - Examine Logs:
out in the middle of the stream. merge_HRI.log
Increase Inactivity Timeout under Configura- syngo: Configuration Tool -
tion DICOM - General
• Timeout when waiting for a response for successful syngo: DICOM Service Tools
transfer. The information system is not able to find - Analysis - Examine logs:
scheduled studies according to the worklist request - merge_HRI.log
performance problems syngo: Configuration Tool -
¹ See merge_stu.log for error message: time- DICOM - General
out 'Read PDU timeout'
¹ Increase Read PDU Timeout under Configu-
ration.

Information System cannot Handle the Worklist Request 0

Tab. 18 For DICOM specialist level

Probable Cause and Service Action Service Tool

• The information system can not handle the worklist Service PC: - JDICOM - RIS
request. Server GUI
¹ Connect your Service PC instead of the remote
system. Simulate remote system by using the
same IP address and start a worklist provider
with the same AET and port number. Check
whether the test tools are able to deal with the
worklist request.

If USC / HSC support is required:

If no remote access for troubleshooting is possible and a specialist needs to analyze the
problem, he will need the following data:
1. Preferably, the DICOM transfer will be captured by using the Solaris 2 snoop com-
mand, Ethereal or by the NetXray Lan Analyzer. See introduction to these troubleshoot-
ing instructions.
Please note that in a switched network the system which captures the traffic needs to
be one of the two involved systems or connected to one of the systems via a HUB. The
captured file can be analyzed using the Merge DPM tool.
2. If capturing the DICOM transfer is not possible, the following log file is required: %MED-
HOME%\log\merge_HRI.log with trace level T2, T3 and T7.

Siemens AG TD00-000.840.01.03.02 Page 41 of 106 DICOM

Medical Solutions 06.04 CS SD 21
42 Modality Performed Procedure Step
9-
8Modality Performed Procedure Step

On the CS Intranet under: “For Service - Planning - General” you will find a Planning
and Configuration Guide called 'DICOM Interface: syngo - IS'.
This document describes how to evaluate all required data for Modality Worklist and
Modality Performed Procedure Steps and how to configure syngo. In addition, the syngo
user interfaces for MPPS are described and a workflow table with all relevant attributes is
provided.

JDICOM, which is available on the CS Intranet under “For Service - DICOM -> DICOM -
Test Tools”, provides the ability to easily simulate a Worklist and MPPS provider (Infor-
mation System) on your Service PC.

DICOM TD00-000.840.01.03.02 Page 42 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Media Storage 43
10-
9Media Storage

You can download a validation tool from the University of Oldenburg called DCMCheck
on the CS Intranet under “For Service - DICOM -> DICOM - Test Tools”. This tool allows
you to validate an entire CD; the DICOMDIR and all images on the CD will be validated.
With JDICOM, which is available on the same Intranet Page, you can display and even
edit DICOMDIR files.

Siemens AG TD00-000.840.01.03.02 Page 43 of 106 DICOM

Medical Solutions 06.04 CS SD 21
44 Network Tests and Commands
11-
10Network Tests and Commands

You can perform the elementary checks to test network connectivity with the following
commands.
Select <Utilities> <Escape to OS> in the service platform of the Host to enter the test
commands.

Command Note
ARP -A Displays current ARP entries by interrogating the current
protocol data. If inet-addr is specified, the IP and physical
addresses are displayed (only nodes in the local network
can be listed)
IPCONFIG/ALL Display the local network configuration.
PING otherhostname To check low-level connectivity. Try using the name first.
If that fails, try the IP address. If it does not work even
with the IP address, ascribe it to the NIC (Network Inter-
(Kommando Ping face Card) drivers or routing. If ping works, but something
AXA4-100.888.01...) on the high-level does not work, test with NBTSTAT -RN
NBTSTAT -RN
NETSTAT -rn To determine whether the local and remote hosts have a
default gateway specified.
NSLOOKUP otherhostname If DNS is used, find out the corresponding Internet
address; reversed name lookup works as well (find the
host name for an IP address).
TRACERT ip-address Trace routing to a destination host (over a maximum of 30
hops).
Telnet

DICOM TD00-000.840.01.03.02 Page 44 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Network Tests and Commands 45

PING 0

“PING” is used to check the ability to reach a component via the network. Two responses
to the command are possible:
• Reply; the component answers the question (“is alive”), and
• Timeout; the component cannot be reached. A response was not sent within the time
window. In this case, the configuration and the network connection for this component
must be checked.

Ping Out of Configuration 0

While doing the network configuration, it is possible to check the entered IP address with
the Test button. The system will then perform a ping to the IP address which is shown to
the left of the Test button

Ping with DICOM Tests 0

After selection of the configured host, use the “GO” button to start the network test.
This ping uses the host name. The related IP number from the “hosts file” is used.
This file contains the mappings of IP addresses to host names.
Each entry is kept on an individual line. The IP address is placed in the first column, fol-
lowed by the corresponding host name. The IP address and the host name are separated
by at least one space.
After a successful “ping”, the higher level test “DICOM ECHO” is started automatically.

Ping Out of Hardcopy Configuration 0

While doing the hardcopy configuration, it is possible to check the entered address with
the Test button. The system will then perform a ping to the selected logical name.
The higher level test “DICOM ECHO” can be performed with the ’DICOM access’ test but-
ton.

Ping with <Utilities><Escape to OS> 0

1. Call up the service software.

2. Call up “Utilities” on the service home page.
3. Under <SOURCE>, select “Escape to OS”.
4. Under <Commands>, select the NT Command Interpreter.
5. In the <Parameters> input box, enter ping and the TCP/IP number of the component.
(If the host name is entered, the name can also be entered instead of the IP address.)
6. Click on <GO>.
Example with “ping <ip-number>
Example with “ping <hostname>

Siemens AG TD00-000.840.01.03.02 Page 45 of 106 DICOM

Medical Solutions 06.04 CS SD 21
46 Network Tests and Commands

Ping Parameters 0

The following parameters can be used together with the ping command.
ping [-t] [-a] [-n count] [-l length] [-f] [-i ttl] [-v tos] [-r count] [-s count] [[-j computer-list] | [-k
computer-list]] [-w timeout] destination-list

Parameters
-t Pings the specified computer until interrupted.
-a Resolve addresses to computer names.
-n count Sends the number of ECHO packets specified by count. The
default is 4.
-l length Sends ECHO packets containing the amount of data specified by
length. The default is 64 bytes; the maximum is 8192.
-f Sends a ‘Do not Fragment’ flag in the packet. The packet will not
be fragmented by gateways on the route.
-i ttl Sets the Time To Live field to the value specified by ttl.
-v tos Sets the Type Of Service field to the value specified by tos.
-r count Records the route of the outgoing packet and the returning packet
in the Record Route field. A minimum of 1 and a maximum of 9
computers may be specified by count.
-s count Specifies the time stamp for the number of hops specified by count.
-j computer list Routes packets via the list of computers specified by computer list.
Consecutive computers may be separated by intermediate gate-
ways (loose source routed). The maximum number allowed by IP is
9.
-k computer list Routes packets via the list of computers specified by computer list.
Consecutive computers may not be separated by intermediate
gateways (strict source routed). The maximum number allowed by
IP is 9.
-w timeout Specifies a timeout interval in milliseconds. Destination list speci-
fies the remote computers to ping.

DICOM TD00-000.840.01.03.02 Page 46 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Network Tests and Commands 47

Netstat 0

This command is available only if the TCP/IP protocol has been installed.

Netstat Parameters 0

netstat [-a] [-e] [-n] [-s] [-p protocol] [-r] [interval]

Parameters
-a Displays all connections and listening ports; server connections are nor-
mally not shown.
-e Displays Ethernet statistics. This may be combined with the -s option.
-n Displays addresses and port numbers in numerical form (rather than
attempting name look-ups).
-s Displays per-protocol statistics. By default, statistics are shown for TCP,
UDP, ICMP, and IP; the -p option may be used to specify a subset of the
default.
-p protocol Shows connections for the protocol specified by proto; proto may be tcp
or udp. If used with the -s option to display per-protocol statistics, proto
may be tcp, udp, icmp, or ip.
-r Displays the contents of the routing table.interval. Redisplays selected
statistics, pausing interval seconds between each display. Press
CTRL+C to stop redisplaying statistics. If this parameter is omitted, net-
stat prints the current configuration information once.

Siemens AG TD00-000.840.01.03.02 Page 47 of 106 DICOM

Medical Solutions 06.04 CS SD 21
48 Network Tests and Commands

Telnet 0

To open a telnet window, proceed as follows

1. Call up the service software
2. Select “Utilities” at the Service Home page.
3. Under <SOURCE> select “Escape to OS”.
4. Under <Commands> select NT Command Interpreter.
5. In the input field <Parameters> enter telnet
6. Click on <GO>.
The telnet window will now appear.
Then connect the host with which you want to communicate. You can also connect to a
port or service other than the standard Telnet port.
This is useful when the Telnet client is being used to access something other than a Tel-
net daemon.
Once you connect to the remote system, the title bar in the Telnet window will show the
name of the remote system.
To connect to a remote computer
1. In the Connect menu, click on Remote System.
2. In the Host Name box, type the name of the remote system to which you want to con-
nect.
3. In the Port box, specify a port or service to use.
The available choices are typical strings a host expects during TermType subnegotiation.
Note: The string you specify in the TermType box does not control the terminal emulation
that is used, only the string that is passed during TermType negotiation. The terminal
emulation is still controlled by the settings in the Terminal Preferences dialog box.

DICOM TD00-000.840.01.03.02 Page 48 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Network Tests and Commands 49

Network Test Examples 0

ping -l 50000 -n 10 <IP address> 0

This is an example of the result with the “ping -l 50000 -n 10 <IPaddress>” command.

C:\>ping -l 50000 -n 10 157.163.196.88

Pinging 157.163.196.88 with 50000 bytes of data:
Request timed out.
Reply from 157.163.196.88: bytes=50000 time=90ms TTL=128
Reply from 157.163.196.88: bytes=50000 time=80ms TTL=128
Reply from 157.163.196.88: bytes=50000 time=81ms TTL=128
Reply from 157.163.196.88: bytes=50000 time=90ms TTL=128
Reply from 157.163.196.88: bytes=50000 time=90ms TTL=128
Reply from 157.163.196.88: bytes=50000 time=90ms TTL=128
Reply from 157.163.196.88: bytes=50000 time=80ms TTL=128
Reply from 157.163.196.88: bytes=50000 time=80ms TTL=128
Reply from 157.163.196.88: bytes=50000 time=90ms TTL=128

netstat -rn 0

This is an example of the result with the “netstat -rn” command.

Tab. 19 netstat -rn

Active Routes: Netmask Gateway Interface Metric

Network Desti-
nation
0.0.0.0 0.0.0.0 157.163.196.1 157.163.197.36 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
157.163.196.0 255.255.252.0 157.163.197.36 157.163.197.36 1

netstat -s 0

This is an example of the result with the “netstat -s” command.

IP Statistics
Packets Received = 57105
Received Header Errors = 35953
Received Address Errors = 284

Siemens AG TD00-000.840.01.03.02 Page 49 of 106 DICOM

Medical Solutions 06.04 CS SD 21
50 Network Tests and Commands

IP Statistics
Datagrams forwarded = 0
Unknown protocols received = 0
Received packets discarded = 0
Received packets delivered = 20677
Output requests = 22996
Routing discards = 0
Discarded output packets = 0
Output packet no route = 0
Reassembly required = 307
Reassembly successful = 9
Reassembly failures = 1
Datagrams successfully fragmented = 9
Datagrams failing fragmentation = 0
Fragments created = 306

ICMP Statistics Received sent

Messages 148 9
Errors 0 0
Destination unreachable 107 0
Time exceeded 0 0
Parameter problems 0 0
Source quench 0 0
Redirects 0 0
Echoes 9 0
Echo replies 0 9
Time stamps 0 0
Time stamp replies 0 0
Address masks 0 0
Address mask replies 0 0

DICOM TD00-000.840.01.03.02 Page 50 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Network Tests and Commands 51

TCP Statistics
Active Opens = 268
Passive Opens = 252
Failed Connection Attempts = 0
Reset Connections = 32
Current Connections = 316
Segments Received = 15737
Segments Sent = 15767
Segments Retransmitted = 1

UDP Statistics
Datagrams Received = 3801
No Ports = 1132
Receive Errors = 0
Datagrams Sent = 7219

ARP 0

Fig. 5: ARP-A

Siemens AG TD00-000.840.01.03.02 Page 51 of 106 DICOM

Medical Solutions 06.04 CS SD 21
52 Network Tests and Commands

Syngo DICOM Test Tools 0

DICOM Service
Verify Network

Fig. 6: Verifying the network

Storage
Send Image

Fig. 7: Sending images

DICOM TD00-000.840.01.03.02 Page 52 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Network Tests and Commands 53

DICOM Service
Storage
Simulate Local Receiver

Fig. 8: Simulating the local receiver

Siemens AG TD00-000.840.01.03.02 Page 53 of 106 DICOM

Medical Solutions 06.04 CS SD 21
54 Network Tests and Commands

DICOM Service
Simulate Remote Receiver

Fig. 9: Simulating the remote receiver

Analysis

DICOM TD00-000.840.01.03.02 Page 54 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 55
12-
Merge Error Messages
11Appendix

[MC_ALREADY_REGISTERED] Application was already registered

[MC_ASSOCIATION_ABORTED] Association was aborted
[MC_ASSOCIATION_CLOSED] Association was closed by peer
[MC_ASSOCIATION_REJECTED] Association negotiation failed
[MC_ATTRIBUTE_HAS_VALUES] Attribute has value[s] - VR cannot be changed
to SQ
[MC_BUFFER_TOO_SMALL] Value too large for buffer
[MC_CALLBACK_CANNOT_COMPLY] Callback cannot comply
[MC_CALLBACK_DATA_SIZE_NEGATIVE] Callback provided negative data size
[MC_CALLBACK_DATA_SIZE_UNEVEN] Callback provided uneven data size
[MC_CALLBACK_PARM_ERROR] Invalid parameter from callback
[MC_CALLBACK_REGISTERED] Not allowed if callback is registered
[MC_CANNOT_COMPLY] Callback cannot comply with request
[MC_CANT_ACCESS_PROFILE] Cannot access MergeCOM services file
[MC_CONFIG_INFO_ERROR] Invalid configuration parameter
[MC_CONFIG_INFO_MISSING] Required configuration info missing
[MC_DDFILE_ERROR] Problem with data dictionary file
[MC_DOES_NOT_VALIDATE] Message contains validation errors
[MC_EMPTY_VALUE] Attribute has no value yet
[MC_END_OF_DATA] End of data
[MC_EXT_INFO_UNAVAILABLE] Extended negotiation information unavailable
[MC_FOUND] Private block found
[MC_FUNCTION_UNAVAILABLE] Function not available on this machine
[MC_INCOMPATIBLE_VR] Tag's VR incompatible with function call
[MC_INCOMPATIBLE_VALUE] Tag's value incompatible with function call
[MC_INVALID_APPLICATION_ID] Application ID parameter is invalid
[MC_INVALID_APPLICATION_TITLE] Application Title parameter is invalid
[MC_INVALID_ASSOC_ID] Association ID parameter is invalid
[MC_INVALID_CHARS_IN_VALUE] Invalid characters in value for this VR
[MC_INVALID_COMMAND] Invalid command parameter
[MC_INVALID_DATA_TYPE] Invalid data type parameter

Siemens AG TD00-000.840.01.03.02 Page 55 of 106 DICOM

Medical Solutions 06.04 CS SD 21
56 Appendix

[MC_END_OF_LIST] End of list has been reached

[MC_INVALID_GROUP] Private group not an odd number
[MC_INVALID_HOST_NAME] Host name parameter invalid
[MC_INVALID_ITEM_ID] Item ID parameter invalid
[MC_INVALID_LENGTH_FOR_TITLE] Application title not 1-16 bytes long
[MC_INVALID_LENGTH_FOR_VR] Invalid VR length in stream data
[MC_INVALID_LICENSE] Invalid license number specified in
[ASSOC_PARMS][MC_INVALID_MESSAGE_ID] Message ID parameter invalid
[MC_INVALID_MESSAGE_RECEIVED] Network partner sent an invalid message
[MC_INVALID_PARAMETER_NAME] Invalid name parameter value
[MC_INVALID_PORT_NUMBER] Port number parameter not positive
[MC_INVALID_PRIVATE_CODE] Invalid private group code
[MC_INVALID_SERVICE_LIST_NAME] Invalid service list name parameter
[MC_INVALID_TAG] Tag parameter invalid
[MC_INVALID_TRANSFER_SYNTAX] Invalid transfer syntax code
[MC_INVALID_VALUE_FOR_VR] Invalid value for this tag's VR
[MC_INVALID_VALUE_NUMBER] Invalid value number for the attribute
[MC_INVALID_VR_CODE] VR parameter is invalid
[MC_LOG_EMPTY] No messages have been logged
[MC_MESSAGE_EMPTY] The message object is empty
[MC_MESSAGE_VALIDATES] Message validates
[MC_MISSING_CONFIG_PARM] Required parameter missing in merge.ini
[MC_MSGFILE_ERROR] Problem with message information file
[MC_MUST_BE_POSITIVE] Value is not positive
[MC_NETWORK_SHUT_DOWN] Network unexpectedly shutdown
[MC_NO_APPLICATIONS_REGISTERED] No applications registered
[MC_NO_CALLBACK] Attribute has no callback registered
[MC_NO_CONDITION_FUNCTION] Warning: no function specified for Type 1C or
Type 2C attribute
[MC_NO_FILE_SYSTEM] No file system available to perform requested
function
[MC_NO_INFO_REGISTERED] No negotiation information registered for the
service

DICOM TD00-000.840.01.03.02 Page 56 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 57

[MC_NO_LICENSE] License not found in [ASSOC_PARMS]

[MC_NO_MERGE_INI] MERGE.INI file cannot be located
[MC_NO_MORE_ATTRIBUTES] Message has no more attributes
[MC_NO_MORE_VALUES] Attribute has no more values
[MC_NO_PROFILE] Could not access MergeCOM Profile
[MC_NO_REQUEST_PENDING] No association request to accept/reject
[MC_NON_SERVICE_ATTRIBUTE] Invalid attribute for service
[MC_NOT_FOUND] Private block not found
[MC_NOT_ONE_OF_ENUMERATED_VALUES] Value not an enumerated value
[MC_NOT_ONE_OF_DEFINED_TERMS] Value not one of defined terms
[MC_NULL_POINTER_PARM] Null parameter
[MC_NULL_VALUE] Attribute's value is NULL
[MC_PROTOCOL_ERROR] Protocol violation: Call made out of sequence
[MC_REQUIRED_ATTRIBUTE_MISSING] Required attribute not in message
[MC_REQUIRED_DATASET_MISSING] Missing required data set for this message com-
mand
[MC_REQUIRED_VALUE_MISSING] Required attribute has no value
[MC_STATE_VIOLATION] Function call invalid now
[MC_SYSTEM_CALL_INTERRUPTED] System call was interrupted
[MC_SYSTEM_ERROR] System error
[MC_TAG_ALREADY_EXISTS] Tag already exists
[MC_TEMP_FILE_ERROR] Temporary file I/O error
[MC_TIMEOUT] Timed out waiting on network partner
[MC_TOO_FEW_VALUES] Attribute must have more values
[MC_TOO_MANY_BLOCKS] No room for more private blocks
[MC_TOO_MANY_VALUES] Too many values for this attribute
[MC_UNABLE_TO_CHECK_CONDITION] Unable to check condition
[MC_UNACCEPTABLE_SERVICE] Message service unacceptable for this associa-
tion
[MC_UNEXPECTED_EOD] Unexpected end of stream data
[MC_UNKNOWN_ITEM] Item is not configured
[MC_UNKNOWN_SERVICE] Service is not configured
[MC_VALUE_MAY_NOT_BE_NULL] Type 1[C] value may not be NULL

Siemens AG TD00-000.840.01.03.02 Page 57 of 106 DICOM

Medical Solutions 06.04 CS SD 21
58 Appendix

[MC_VALUE_NOT_ALLOWED] Attribute must not be used under current condi-

tion
[MC_VALUE_OUT_OF_RANGE] Out of range: Numeric precision would be lost.
[MC_VALUE_TOO_LARGE] Stream value length too large
[MC_VR_ALREADY_VALID] Value representation is already valid
[MC_LIBRARY_ALREADY_INITIALIZED] MC_Library_Initialization has already been
called
[MC_LIBRARY_NOT_INITIALIZED] MC_Library_Initialization not called yet
[MC_INVALID_DIRECTORY_RECORD_OFFSET] Directory record offset doesn't match a directory
record
[MC_INVALID_FILE_ID] File ID parameter invalid
[MC_INVALID_DICOMDIR_ID] DICOMDIR ID parameter invalid
[MC_INVALID_ENTITY_ID] Entity ID parameter invalid
[MC_INVALID_MRDR_ID] MRDR ID parameter invalid
[MC_UNABLE_TO_GET_ITEM_ID] Function unable to get item ID from DICOMDIR
object
[MC_INVALID_PAD] Invalid number for padding, must be even
[MC_ENTITY_ALREADY_EXISTS] Lower level directory entity already exists
[MC_INVALID_LOWER_DIR_RECORD] Invalid lower-level directory record type
[MC_BAD_DIR_RECORD_TYPE] Invalid directory record type
[MC_UNKNOWN_HOST_CONNECTED] Unknown host attempted to connect
[MC_INACTIVITY_TIMEOUT] Timed out waiting on network partner in middle
of a transfer
[MC_INVALID_SOP_CLASS_UID] SOP class UID parameter is invalid
[MC_INVALID_VERSION] Invalid version of utilities used to generate con-
figuration functions
[MC_OUT_OF_ORDER_TAG] A tag was encoded in the stream not in ascend-
ing order
[MC_CONNECTION_FAILED] Failed to connect to remote host
[MC_UNKNOWN_HOST_NAME] Unable to resolve host name to ip address
[MC_INVALID_FILE] Invalid DICOM file: did not contain DICM in pre-
fix

DICOM TD00-000.840.01.03.02 Page 58 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 59

Merge_stu.log - Storage Association T2, T3 and T7 0

This example shows the merge_stu.log with trace levels T2, T3, T7 and (only at the end)
T9.
1.) Each DICOM communication starts with the Association Negotiation, which can
be seen on trace level T3. The Service Class User (SCU) sends an Association
Request message to the provider, where it presents all supported objects with a list
of proposed transfer syntaxes (in this case, only one). Each object will be identified
by a presentation context ID. In addition, the Application Entity Titles (AETs) and
the maximum Protocol Data Unit size (PDU) will be transferred.
(312) 07-21 14:58:22.84 MC3 T3: REQUEST Association Parameters:
(312) 07-21 14:58:22.84 MC3 T3: Calling_presentation_address: cmv10001
(146.254.120.75)
(312) 07-21 14:58:22.85 MC3 T3: Called_presentation_address:
(312) 07-21 14:58:22.85 MC3 T3: Called_application_title: CSYNGO1
(312) 07-21 14:58:22.85 MC3 T3: Calling_application_title: 049SA1DCDADRSP
(312) 07-21 14:58:22.85 MC3 T3: Application_context_name: 1.2.840.10008.3.1.1.1
(312) 07-21 14:58:22.85 MC3 T3: PDU_maximum_length: 28672
(312) 07-21 14:58:22.85 MC3 T3: Implem_class_uid: 1.3.12.2.1107.5.8
(312) 07-21 14:58:22.85 MC3 T3: Version_name: SNKIT_1.10
(312) 07-21 14:58:22.85 MC3 T3: Max_operations_invoked: Not Sent
(312) 07-21 14:58:22.85 MC3 T3: Max_operations_performed: Not Sent
(312) 07-21 14:58:22.85 MC3 T3: PRESENTATION CONTEXTS:
(312) 07-21 14:58:22.86 MC3 T3: (1) Pres_context_id: 1
(312) 07-21 14:58:22.86 MC3 T3: (1) Abstract_syntax:
1.2.840.10008.5.1.4.1.1.4 (STANDARD_MR)
(312) 07-21 14:58:22.86 MC3 T3: (1) Proposed Transfer Syntaxes:
(312) 07-21 14:58:22.86 MC3 T3: 1.2.840.10008.1.2 (Implicit Little Indian)
(312) 07-21 14:58:22.86 MC3 T3: (1) SCU Role: Not sent (requestor supports SCU)
(312) 07-21 14:58:22.86 MC3 T3: (1) SCP Role: Not sent (requestor supports SCP)
(312) 07-21 14:58:22.86 MC3 T3: (1) No extended application info
(312) 07-21 14:58:22.86 MC3 T3: (2) Pres_context_id: 3
(312) 07-21 14:58:22.86 MC3 T3: (2) Abstract_syntax:
1.2.840.10008.5.1.4.1.1.1 (STANDARD_CR)
(312) 07-21 14:58:22.87 MC3 T3: (2) ProposedTransferSyntaxes:
(312) 07-21 14:58:22.87 MC3 T3: 1.2.840.10008.1.2 (Implicit Little Indian)
(312) 07-21 14:58:22.87 MC3 T3: (2) SCU Role: Not sent (requestor supports SCU)
(312) 07-21 14:58:22.87 MC3 T3: (2) SCP Role: Not sent (requestor supports SCP)
(312) 07-21 14:58:22.87 MC3 T3: (2) No extended application info
(312) 07-21 14:58:22.87 MC3 T3: (3) Pres_context_id: 5

Siemens AG TD00-000.840.01.03.02 Page 59 of 106 DICOM

Medical Solutions 06.04 CS SD 21
60 Appendix

.............
.............
.............
(312) 07-21 14:58:23.01 MC3 T3: (21) Pres_context_id: 41
(312) 07-21 14:58:23.02 MC3 T3: (21) Abstract_syntax:
1.2.840.10008.5.1.4.1.1.1.2.1
(STANDARD_MG_PROCESS)
(312) 07-21 14:58:23.02 MC3 T3: (21) Proposed Transfer Syntaxes:
(312) 07-21 14:58:23.02 MC3 T3: 1.2.840.10008.1.2 (Implicit Little Indian)
(312) 07-21 14:58:23.02 MC3 T3: (21) SCU Role: Not sent (requestor supports SCU)
(312) 07-21 14:58:23.02 MC3 T3: (21) SCP Role: Not sent (requestor supports SCP)
(312) 07-21 14:58:23.02 MC3 T3: (21) No extended application info

2.) The response of the Service Class Provider shows which objects are supported
(accepted) and which one of the proposed Transfer Syntaxes will be used.
(312) 07-21 14:58:23.02 MC3 T3: RESPONSE Association Parameters:
(312) 07-21 14:58:23.02 MC3 T3: Calling_presentation_address: cmv10001
(146.254.120.75)
(312) 07-21 14:58:23.02 MC3 T3: Called_presentation_address:
(312) 07-21 14:58:23.02 MC3 T3: Called_application_title: CSYNGO1
(312) 07-21 14:58:23.03 MC3 T3: Application_context_name: 1.2.840.10008.3.1.1.1
(312) 07-21 14:58:23.03 MC3 T3: PDU_maximum_length: 28672
(312) 07-21 14:58:23.03 MC3 T3: Implem_class_uid: 1.3.12.2.1107.5.9.990801
(312) 07-21 14:58:23.03 MC3 T3: Version_name: SIEMENS_SWFVA47A
(312) 07-21 14:58:23.03 MC3 T3: Max_operations_invoked: Not Sent
(312) 07-21 14:58:23.03 MC3 T3: Max_operations_performed: Not Sent
(312) 07-21 14:58:23.03 MC3 T3: PRESENTATION CONTEXTS:
(312) 07-21 14:58:23.03 MC3 T3: (1) Pres_context_id: 1
(312) 07-21 14:58:23.03 MC3 T3: (1) Abstract_syntax: 1.2.840.10008.5.1.4.1.1.4
(STANDARD_MR)
(312) 07-21 14:58:23.03 MC3 T3: (1) Result_transfer_syntax: 1.2.840.10008.1.2 (Implicit
Little Indian)
(312) 07-21 14:58:23.04 MC3 T3: (1) SCU Role: Not sent (remote accepts requestor SCU
role)
(312) 07-21 14:58:23.04 MC3 T3: (1) SCP Role: Not sent (remote accepts requestor SCP
role)
(312) 07-21 14:58:23.04 MC3 T3: (1) No extended application info
(312) 07-21 14:58:23.04 MC3 T3: (1) Negotiation Result: Accepted
(312) 07-21 14:58:23.04 MC3 T3: (2) Pres_context_id: 3

DICOM TD00-000.840.01.03.02 Page 60 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 61

(312) 07-21 14:58:23.04 MC3 T3: (2) Abstract_syntax: 1.2.840.10008.5.1.4.1.1.1

(STANDARD_CR)
(312) 07-21 14:58:23.04 MC3 T3: (2) Result_transfer_syntax: 1.2.840.10008.1.2 (Implicit
Little Indian)
(312) 07-21 14:58:23.04 MC3 T3: (2) SCU Role: Not sent (remote accepts requestor SCU
role)
(312) 07-21 14:58:23.05 MC3 T3: (2) SCP Role: Not sent (remote accepts requestor SCP
role)
(312) 07-21 14:58:23.05 MC3 T3: (2) No extended application info
(312) 07-21 14:58:23.05 MC3 T3: (2) Negotiation Result: Accepted
(312) 07-21 14:58:23.05 MC3 T3: (3) Pres_context_id: 5
...............
...............
...............
(312) 07-21 14:58:23.20 MC3 T3: (21) Pres_context_id: 41
(312) 07-21 14:58:23.20 MC3 T3: (21) Abstract_syntax: 1.2.840.10008.5.1.4.1.1.1.2.1
(STANDARD_MG_PROCESS)
(312) 07-21 14:58:23.20 MC3 T3: (21) Result_transfer_syntax: (Implicit Big Indian)
(312) 07-21 14:58:23.20 MC3 T3: (21) SCU Role: Not sent (remote accepts requestor
SCU role)
(312) 07-21 14:58:23.20 MC3 T3: (21) SCP Role: Not sent (remote accepts requestor
SCP role)
(312) 07-21 14:58:23.20 MC3 T3: (21) No extended application info
(312) 07-21 14:58:23.20 MC3 T3: (21) Negotiation Result: REJECTED: Abstract syntax

3.) After the Association Negotiation, the 'Command Set' of the first object (e.g.
image) will be sent and can be seen on trace level T7. All attributes within the com-
mand set belong to group 0000 and indicate which kind of object will be sent (con-
text ID and affected SOP Class UID) and the unique object identification (affected
SOP instance UID)
(409) 07-21 14:58:23.34 MC3 T7: Message received on context 5
(409) 07-21 14:58:23.34 MC3 T7: Group 0x0000 Elements:
(409) 07-21 14:58:23.34 MC3 T7: (0000,0000) Group 0000 length
(409) 07-21 14:58:23.34 MC3 T7: (1): 126
(409) 07-21 14:58:23.34 MC3 T7: (0000,0002) Affected SOP class UID
(409) 07-21 14:58:23.34 MC3 T7: (1): 1.2.840.10008.5.1.4.1.1.2
(409) 07-21 14:58:23.34 MC3 T7: (0000,0100) Command field
(409) 07-21 14:58:23.34 MC3 T7: (1): 1
(409) 07-21 14:58:23.35 MC3 T7: (0000,0110) Message ID
(409) 07-21 14:58:23.35 MC3 T7: (1): 0
(409) 07-21 14:58:23.35 MC3 T7: (0000,0700) Priority

Siemens AG TD00-000.840.01.03.02 Page 61 of 106 DICOM

Medical Solutions 06.04 CS SD 21
62 Appendix

(409) 07-21 14:58:23.35 MC3 T7: (1): 0

(409) 07-21 14:58:23.35 MC3 T7: (0000,0800) Data set Type
(409) 07-21 14:58:23.35 MC3 T7: (1): 0
(409) 07-21 14:58:23.35 MC3 T7: (0000,1000) Affected SOP instance UID
(409) 07-21 14:58:23.35 MC3 T7: (1): 1.3.12.2.1107.5.1.3.24013.4.0.2508718952428

4.) On trace level T2, you can again see the 'Command Set' with the additional infor-
mation.
Following the Command Set, the 'Data Set' will be shown including all other
attributes of the sent object. If there is an image transfer, these attributes are iden-
tical to the image header information. If there is a query or worklist request, you
can see the attributes sent within these requests.
The value length will be shown inside of ( ) and the value itself inside of | |.

Command Set:
(409) 07-21 14:58:26.37 MC3 T2: Message (STANDARD_CT,C_STORE_RQ) received
on context 5
(409) Message ID: 100
(409) Service supported: STANDARD_CT (0032)
(409) Command supported: C_STORE_RQ
(409) Message attributes:
(409) 0000,0000 Group 0000 length VR: UL VM: 1
(409) (0000004) |126|
(409) 0000,0002 Affected SOP Class UID VR: UI VM: 1
(409) (0000025) |1.2.840.10008.5.1.4.1.1.2|
(409) 0000,0100 Command Field VR: US VM: 1
(409) (0000002) |1|
(409) 0000,0110 Message ID VR: US VM: 1
(409) (0000002) |0|
(409) 0000,0700 Priority VR: US VM: 1
(409) (0000002) |0|
(409) 0000,0800 Data Set Type VR: US VM: 1
(409) (0000002) |0|
(409) 0000,1000 Affected SOP instance UID VR: UI VM: 1
(409) (0000043) |1.3.12.2.1107.5.1.3.24013.4.0.2508718952428|

Data Set
(0008,0005 Specific character set is missing -> ISO_IR6 = ASCII)
(409) 0008,0008 Image type VR: CS VM: 1-n

DICOM TD00-000.840.01.03.02 Page 62 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 63

(409) (0000035) |ORIGINAL|

(409) |PRIMARY|
(409) |LOCALIZER|
(409) |CT_SOM5 TOP|
(409) 0008,0016 SOP class UID VR: UI VM: 1
(409) (0000025) |1.2.840.10008.5.1.4.1.1.2 |
(409) 0008,0018 SOP Instance UID VR: UI VM: 1
(409) (0000043) |1.3.12.2.1107.5.1.3.24013.4.0.2508718952428|
(409) 0008,0020 Study date VR: DA VM: 1
(409) (0000008) |20000711
(409) 0008,0021 Series date VR: DA VM: 1
(409) (0000008) |20000711|
(409) 0008,0022 Acquisition date VR: DA VM: 1
(409) (0000008) |20000711|
(409) 0008,0023 Image date VR: DA VM: 1
(409) (0000008) |20000711|
(409) 0008,0030 Study time VR: TM VM: 1
(409) (0000013) |143100.140000|
(409) 0008,0031 Series time VR: TM VM: 1
(409) (0000013) |143145.375000|
(409) 0008,0032 Acquisition time VR: TM VM: 1
(409) (0000013) |143203.890001|
(409) 0008,0033 Image time VR: TM VM: 1
(409) (0000013) |143203.890001|
(409) 0008,0050 Accession Number VR: SH VM: 1
(409) (0000010) |FONo200012 |
(409) 0008,0060 Modality VR: CS VM: 1
(409) (0000002) |CT|
(409) 0008,0070 Manufacturer VR: LO VM: 1
(409) (0000007) |SIEMENS|
(409) 0008,0080 Institution name VR: LO VM: 1
(409) (0000011) |Siemens CTE |
(409) 0008,0081 Institution address VR: ST VM: 1
(409) (0000032) |Street\x0A/27E5E2/\x0ADistrict\x0ACountry|
(409) 0008,0090 Referring physician's name VR: PN VM: 1
(409) (0000061) |RefFamNam^RefGiveNam^RefMidNam^RefTitle^RefSuf^Ref|
(409) |Pre^RefDegr|
(409) 0008,1010 Station name VR: SH VM: 1

Siemens AG TD00-000.840.01.03.02 Page 63 of 106 DICOM

Medical Solutions 06.04 CS SD 21
64 Appendix

(409) (0000007) |F24013C|

(409) 0008,1030 Study description VR: LO VM: 1
(409) (0000020) |Abdomen^AbdThinSlice||
(409) 0008,103E Series description VR: LO VM: 1
(409) (0000008) |Topogram|
(409) 0008,1040 Institutional department name VR: LO VM: 1
(409) (0000000) <null>
(409) 0008,1050 Performing physician's name VR: PN VM: 1-n
(409) (0000047) |SchedPerfPhNam1^SchedPerfPhNam2^SchedPerfPhNam3|
(409) 0008,1060 Name of physician(s) reading study VR: PN VM: 1-n
(409) (0000000) <null>
(409) 0008,1070 Operators' name VR: PN VM: 1-n
(409) (0000012) |Dr. Gruening|
(409) 0008,1080 Admitting diagnosis description VR: LO VM: 1-n
(409) (0000015) |LWS Fehlerbild1|
(409) 0008,1090 Manufacturer's model name VR: LO VM: 1
(409) (0000011) |Volume Zoom|
(409) 0008,2111 Derivation description VR: ST VM: 1
(409) (0000000) <null>
(409) 0010,0010 Patient's name VR: PN VM: 1
(409) (0000040) |CCTJul2000^VZVA20A^SpineSSD^Dr.^CCC_(\xFF\xFF)|
(409) 0010,0020 Patient ID VR: LO VM: 1
(409) (0000009) |PatID_VZ3|
(409) 0010,0030 Patient's birth date VR: DA VM: 1
(409) (0000008) |19550824|
(409) 0010,0032 Patient's birth time VR: TM VM: 1
(409) (0000000) <null>
(409) 0010,0040 Patient's sex VR: CS VM: 1
(409) (0000001) |F|
(409) 0010,1000 Other patient IDs VR: LO VM: 1-n
(409) (0000000) <null>
(409) 0010,1001 Other patient names VR: PN VM: 1-n
(409) (0000000) <null>
.................
.................
(409) 0018,0010 Contrast/bolus agent VR: LO VM: 1
(409) (0000000) <null>
(409) 0018,0015 Body part examined VR: CS VM: 1

DICOM TD00-000.840.01.03.02 Page 64 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 65

(409) (0000007) |ABDOMEN|

..................
(409) 0018,1000 Device serial number VR: LO VM: 1
(409) (0000000) <null>
(409) 0018,1020 Software version(s) VR: LO VM: 1-n
(409) (0000007) |VA20A.1|
.................
(409) 0018,5100 Patient position VR: CS VM: 1
(409) (0000003) |HFS|
(409) 0020,000D Study instance UID VR: UI VM: 1
(409) (0000043) |1.3.12.2.1107.5.1.3.24013.4.0.2883410072770|
(409) 0020,000E Series instance UID VR: UI VM: 1
(409) (0000043) |1.3.12.2.1107.5.1.3.24013.4.0.2882929363340|
(409) 0020,0010 Study D VR: SH VM: 1
(409) (0000001) |1|
(409) 0020,0011 Series number VR: IS VM: 1
(409) (0000001) |1|
(409) 0020,0012 Acquisition number VR: IS VM: 1
(409) (0000001) |1|
(409) 0020,0013 Image number VR: IS VM: 1
(409) (0000001) |1|
(409) 0020,0032 Image position (patient) VR: DS VM: 3
(409) (0000048) |0|
(409) |-398|
(409) |-1|
(409) 0020,0037 Image orientation (patient) VR: DS VM: 6
(409) (0000096) |0|
(409) |1|
(409) |0|
(409) |0|
(409) |0|
(409) |-1|
(409) 0020,0052 Frame of reference UID VR: UI VM: 1
(409) (0000043) |1.3.12.2.1107.5.1.3.24013.4.0.2507320363132|
(409) 0020,0060 Laterally VR: CS VM: 1
(409) (0000000) <null>
(409) 0020,1002 Images in acquisition VR: IS VM: 1
(409) (0000001) |0|

Siemens AG TD00-000.840.01.03.02 Page 65 of 106 DICOM

Medical Solutions 06.04 CS SD 21
66 Appendix

(409) 0020,1040 Position reference indicator VR: LO VM: 1

(409) (0000000) <null>
(409) 0020,1041 Slice location VR: DS VM: 1
(409) (0000016) |-1|
(409) 0020,4000 Image comments VR: LT VM: 1
(409) (0000000) <null>
(409) 0028,0002 Samples per pixel VR: US VM: 1
(409) (0000002) |1|
(409) 0028,0004 Photometric interpretation VR: CS VM: 1
(409) (0000011) |MONOCHROME2|
(409) 0028,0010 Rows VR: US VM: 1
(409) (0000002) |512|
(409) 0028,0011 Columns VR: US VM: 1
(409) (0000002) |512|
(409) 0028,0030 Pixel spacing VR: DS VM: 2
(409) (0000032) |1|
(409) |1|
(409) 0028,0100 Bits allocated VR: US VM: 1
(409) (0000002) |16|
(409) 0028,0101 Bits stored VR: US VM: 1
(409) (0000002) |12|
(409) 0028,0102 High Bit VR: US VM: 1
(409) (0000002) |11|
(409) 0028,0103 Pixel representation VR: US VM: 1
(409) (0000002) |0|
.................
(409) 0028,1050 Window center VR: DS VM: 1-n
(409) (0000016) |50 |
(409) 0028,1051 Window width VR: DS VM: 1-n
(409) (0000016) |350|
(409) 0028,1052 Rescale intercept VR: DS VM: 1
(409) (0000016) |-1024|
(409) 0028,1053 Rescale slope VR: DS VM: 1
(409) (0000016) |1.0002441|
.......................
(409) 7FE0,0010 Pixel data VR: OW VM: 1
(409) <Callback routine>
(409) ===== End of Message ID: 100 =====

DICOM TD00-000.840.01.03.02 Page 66 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 67

5.) After each object (image), a response will be sent from the provider in which you
can see the status of the transfer (0 is success). A table of the status codes is avail-
able on the Intranet at http://dicom.med.siemens.de at DICOM - Glossary&Tables.
This 'Command Set' message can be seen on T7.
(409) 07-21 14:58:29.85 MC3 T7: Message (STANDARD_CT,C_STORE_RSP) sent on
context 5
(409) 07-21 14:58:29.85 MC3 T7: Group 0x0000 elements:
(409) 07-21 14:58:29.86 MC3 T7: (0000,0000) Group 0000 length
(409) 07-21 14:58:29.86 MC3 T7: (1): 126
(409) 07-21 14:58:29.86 MC3 T7: (0000,0002) Affected SOP class UID
(409) 07-21 14:58:29.86 MC3 T7: (1): 1.2.840.10008.5.1.4.1.1.2
(409) 07-21 14:58:29.86 MC3 T7: (0000,0100) Command field
(409) 07-21 14:58:29.86 MC3 T7: (1): 32769
(409) 07-21 14:58:29.86 MC3 T7: (0000,0120) Message ID being responded to
(409) 07-21 14:58:29.87 MC3 T7: (1): 0
(409) 07-21 14:58:29.87 MC3 T7: (0000,0800) Data set type
(409) 07-21 14:58:29.87 MC3 T7: (1): 257
(409) 07-21 14:58:29.87 MC3 T7: (0000,0900) Status
(409) 07-21 14:58:29.87 MC3 T7: (1): 0
(409) 07-21 14:58:29.87 MC3 T7: (0000,1000) Affected SOP instance UID
(409) 07-21 14:58:29.87 MC3 T7: (1): 1.3.12.2.1107.5.1.3.24013.4.0.2508718952428

6.) When you turn on trace level T9, you will also see the entire association on the
Packet Data Unit level (PDU). This will add a lot more information to the log file
which is just helpful in some special cases. E.g., if the transfer is interrupted, you
can see how many packets were successfully transferred.
The Association Release request and response can also be seen only on trace level
T9.
(409) 07-21 14:58:29.96 MC3 T9: PDU Type: 05 (Assoc_Rel_RQ) received
(409) 07-21 14:58:29.96 MC3 T9: Reserved byte: 00
(409) 07-21 14:58:29.96 MC3 T9: PDU length: 0000 0004 (4 bytes)
(409) 07-21 14:58:29.96 MC3 T9: Reserved bytes (7-10): 0000 0000
(409) 07-21 14:58:29.96 MC3 T9: PDU Type: 06 (Assoc_Rel_RP) sent
(409) 07-21 14:58:29.96 MC3 T9: Reserved byte: 00
(409) 07-21 14:58:29.96 MC3 T9: PDU length: 0000 0004 (4 bytes)

Siemens AG TD00-000.840.01.03.02 Page 67 of 106 DICOM

Medical Solutions 06.04 CS SD 21
68 Appendix

Merge_hc.log - Print Association T2, T3 and T7 0

This example shows the merge_hc.log with trace levels T2, T3, T7 and (only at the end)
T9.
Overview of the DICOM print services (which all belong to the Basic Gray Scale
Print Management Meta SOP Class
1. Printer Service (which syngo sends frequently to the camera)
2. Printer Service (which will be sent also in the beginning of each print session)
3. Basic Film Session Service (N_Create to set the camera parameter)
4. Basic Film Box Service (N_Create to set the film parameter)
5. Basic Gray scale Image Box Service (N_Set to send the image data)
6. Basic Film Box Service (N_Action to print the film)
7. Basic Film Box Service (N_Delete to delete the film box)
8. Basic Film Session Service (N_Delete to delete the print session)

1. a) Printer Service (which syngo frequently sends to the camera)

Syngo frequently sends a PRINTER request to the camera to get the status of the
camera. Because each is a DICOM communication, this request starts with the
Association Negotiation, which can be seen on trace level T3. The modality or
workstation (SCU) sends an Association Request message to the camera, where it
presents all supported services with a list of proposed transfer syntaxes. Each ser-
vice will be identified by a presentation context ID. In addition, the Application
Entity Titles (AETs) and the maximum Protocol Data Unit size (PDU) will be trans-
ferred.
(579) 03-26 17:58:12.25 MC3 T3: REQUEST Association parameters:
(579) 03-26 17:58:12.34 MC3 T3: Calling_presentation_address: csyngo2
(579) 03-26 17:58:12.34 MC3 T3: Called_presentation_address: PL102625:1024
(579) 03-26 17:58:12.34 MC3 T3: Called_application_title: SYNGO_8700
(579) 03-26 17:58:12.34 MC3 T3: Application_context_name: 1.2.840.10008.3.1.1.1
(579) 03-26 17:58:12.34 MC3 T3: Calling_application_title: CSYNGO2
(579) 03-26 17:58:12.34 MC3 T3: PDU_maximum_length: 28672
(579) 03-26 17:58:12.34 MC3 T3: Implem_class_uid: 1.3.12.2.1107.5.9.20000101
(579) 03-26 17:58:12.34 MC3 T3: Version_name: SIEMENS_SWFVB10A
(579) 03-26 17:58:12.34 MC3 T3: Max_operations_invoked: Not sent
(579) 03-26 17:58:12.34 MC3 T3: Max_operations_performed: Not sent
(579) 03-26 17:58:12.34 MC3 T3: PRESENTATION CONTEXTS:
(579) 03-26 17:58:12.34 MC3 T3: (1)Pres_context_id: 1
(579) 03-26 17:58:12.34 MC3 T3: (1)Abstract_syntax: 1.2.840.10008.5.1.1.9
(BASIC_GRAYSCALE_PRINT_MANAGEMENT)
(579) 03-26 17:58:12.34 MC3 T3: (1) Proposed transfer syntaxes:
(579) 03-26 17:58:12.34 MC3 T3: 1.2.840.10008.1.2.1 (explicit little Indian)

DICOM TD00-000.840.01.03.02 Page 68 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 69

(579) 03-26 17:58:12.34 MC3 T3: 1.2.840.10008.1.2 (implicit little Indian)

(579) 03-26 17:58:12.34 MC3 T3: 1.2.840.10008.1.2.2 (explicit big Indian)
(579) 03-26 17:58:12.34 MC3 T3: (1)SCU Role: Not sent (requester supports SCU)
(579) 03-26 17:58:12.34 MC3 T3: (1)SCP Role: Not sent (requester supportsSCP)
(579) 03-26 17:58:12.34 MC3 T3: (1) No extended application info
(579) 03-26 17:58:12.34 MC3 T3: (2) Pres_context_id: 3
(579) 03-26 17:58:12.34 MC3 T3: (2) Abstract_syntax: 1.2.840.10008.5.1.1.14
(PRINT_JOB)
(579) 03-26 17:58:12.34 MC3 T3: (2) Proposed transfer syntaxes:
(579) 03-26 17:58:12.34 MC3 T3: 1.2.840.10008.1.2.1 (explicit little Indian)
(579) 03-26 17:58:12.34 MC3 T3: | 1.2.840.10008.1.2 (implicit little Indian)
(579) 03-26 17:58:12.34 MC3 T3: 1.2.840.10008.1.2.2 (explicit big Indian)
(579) 03-26 17:58:12.34 MC3 T3: (2) SCU Role: Not sent (requester supports SCU)
(579) 03-26 17:58:12.34 MC3 T3: | (2) SCP Role: Not sent (requester supports SCP)
(579) 03-26 17:58:12.34 MC3 T3: (2) No extended application info
(579) 03-26 17:58:12.34 MC3 T3: (3) Pres_context_id: 5
(579) 03-26 17:58:12.34 MC3 T3: (3) Abstract_syntax: 1.2.840.10008.5.1.1.18
(BASIC_COLOR_PRINT_MANAGEMENT)
(579) 03-26 17:58:12.34 MC3 T3: (3) Proposed transfer syntaxes:
(579) 03-26 17:58:12.34 MC3 T3: 1.2.840.10008.1.2.1 (explicit little Indian)
(579) 03-26 17:58:12.34 MC3 T3: 1.2.840.10008.1.2 (implicit little Indian)
(579) 03-26 17:58:12.34 MC3 T3: 1.2.840.10008.1.2.2 (explicit big Indian)
(579) 03-26 17:58:12.35 MC3 T3: (3) SCU Role: Not sent (requester supports SCU)
(579) 03-26 17:58:12.35 MC3 T3: (3) SCP Role: Not sent (requester supports SCP)
(579) 03-26 17:58:12.35 MC3 T3: (3) No extended application info
(579) 03-26 17:58:12.35 MC3 T3: (4) Pres_context_id: 7
(579) 03-26 17:58:12.35 MC3 T3: (4) Abstract_syntax: 1.2.840.10008.5.1.1.23
(PRESENTATION_LUT)
(579) 03-26 17:58:12.35 MC3 T3: (4) Proposed transfer syntaxes:
(579) 03-26 17:58:12.35 MC3 T3: 1.2.840.10008.1.2.1 (explicit little Indian)
(579) 03-26 17:58:12.35 MC3 T3: 1.2.840.10008.1.2 (implicit little Indian)
(579) 03-26 17:58:12.35 MC3 T3: 1.2.840.10008.1.2.2 (explicit big Indian)
(579) 03-26 17:58:12.35 MC3 T3: (4) SCU Role: Not sent (requester supports SCU)
(579) 03-26 17:58:12.35 MC3 T3: (4) SCP Role: Not sent (requester supports SCP)
(579) 03-26 17:58:12.35 MC3 T3: (4) No extended application info

1. b) The response of the camera shows which services are supported (accepted)
and which one of the proposed transfer syntaxes will be used.
(579) 03-26 17:58:12.46 MC3 T3: RESPONSE Association Parameters:

Siemens AG TD00-000.840.01.03.02 Page 69 of 106 DICOM

Medical Solutions 06.04 CS SD 21
70 Appendix

(579) 03-26 17:58:12.46 MC3 T3: Calling_presentation_address: csyngo2

(579) 03-26 17:58:12.46 MC3 T3: Called_presentation_address: PL102625:1024
(579) 03-26 17:58:12.46 MC3 T3: Called_application_title: SYNGO_8700
(579) 03-26 17:58:12.46 MC3 T3: Calling_application_title: CSYNGO2
(579) 03-26 17:58:12.46 MC3 T3: Application_context_name: 1.2.840.10008.3.1.1.1
(579) 03-26 17:58:12.46 MC3 T3: PDU_maximum_length: 1000000
(579) 03-26 17:58:12.46 MC3 T3: Implem_class_uid: 1.2.840.113720.1.9410.2
(579) 03-26 17:58:12.46 MC3 T3: Version_name: IMN_PrintServer
(579) 03-26 17:58:12.46 MC3 T3: Max_operations_invoked: Not sent
(579) 03-26 17:58:12.46 MC3 T3: Max_operations_performed: Not sent
(579) 03-26 17:58:12.46 MC3 T3: PRESENTATION CONTEXTS:
(579) 03-26 17:58:12.46 MC3 T3: (1) Pres_context_id: 1
(579) 03-26 17:58:12.46 MC3 T3: (1) Abstract_syntax: 1.2.840.10008.5.1.1.9
(BASIC_GRAYSCALE_PRINT_MANAGEMENT)
(579) 03-26 17:58:12.46 MC3 T3: (1) Result_transfer_syntax: 1.2.840.10008.1.2.1
(explicit little Indian)
(579) 03-26 17:58:12.46 MC3 T3: (1) SCU role: Not sent (remote accepts requestor SCU
role)
(579) 03-26 17:58:12.46 MC3 T3: (1) SCP role: Not sent (remote accepts requestor
SCP role)
(579) 03-26 17:58:12.46 MC3 T3: (1) No extended application info
(579) 03-26 17:58:12.46 MC3 T3: (1) Negotiation result: accepted
(579) 03-26 17:58:12.46 MC3 T3: (2) Pres_context_id: 3
(579) 03-26 17:58:12.46 MC3 T3: (2) Abstract_syntax: 1.2.840.10008.5.1.1.14
(PRINT_JOB)
(579) 03-26 17:58:12.46 MC3 T3: (2) Result_transfer_syntax: 1.2.840.10008.1.2.1
(explicit little Indian)
(579) 03-26 17:58:12.46 MC3 T3: (2) SCU Role: Not sent (remote accepts requester SCU
role)
(579) 03-26 17:58:12.46 MC3 T3: (2) SCP Role: Not sent (remote accepts requester SCP
role)
(579) 03-26 17:58:12.46 MC3 T3: (2) No extended application info
(579) 03-26 17:58:12.46 MC3 T3: (2) Negotiation result: accepted
(579) 03-26 17:58:12.46 MC3 T3: (3) Pres_context_id: 5
(579) 03-26 17:58:12.46 MC3 T3: (3) Abstract_syntax: 1.2.840.10008.5.1.1.18
(BASIC_COLOR_PRINT_MANAGEMENT)
(579) 03-26 17:58:12.46 MC3 T3: (3) Negotiation result: REJECTED: abstract syntax
(579) 03-26 17:58:12.46 MC3 T3: (4) Pres_context_id: 7
(579) 03-26 17:58:12.46 MC3 T3: (4) Abstract_syntax: 1.2.840.10008.5.1.1.23

DICOM TD00-000.840.01.03.02 Page 70 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 71

(PRESENTATION_LUT)
(579) 03-26 17:58:12.46 MC3 T3: (4) Result_transfer_syntax: 1.2.840.10008.1.2.1
(explicit little Indian)
(579) 03-26 17:58:12.46 MC3 T3: (4) SCU role: Not sent (remote accepts requester SCU
role)
(579) 03-26 17:58:12.46 MC3 T3: (4) SCP Role: Not sent (remote accepts requester SCP
role)
(579) 03-26 17:58:12.46 MC3 T3: (4) No extended application info
(579) 03-26 17:58:12.46 MC3 T3: (4) Negotiation result: accepted
(579) 03-26 17:58:12.46 MC3 W: Presentation context 5 rejected, reason 0x03
(579) 03-26 17:58:12.46 MC3 W: Abstract syntax: 1.2.840.10008.5.1.1.18
(BASIC_COLOR_PRINT_MANAGEMENT
(579) 03-26 17:58:12.46 MC3 W: Abstract syntax rejected

1. c) After the Association Negotiation, the PRINTER service will be requested. This
request can be seen on trace level T7. All attributes within the command set belong
to group 0000 and indicate which kind of object will be sent (context ID and affected
SOP class UID) and the unique object identification (affected SOP instance UID)
(617) 03-26 17:58:29.54 MC3 T7: Message (PRINTER,N_GET_RQ) sent on context 1
(617) 03-26 17:58:29.54 MC3 T7: Group 0x0000 elements:
(617) 03-26 17:58:29.54 MC3 T7: (0000,0000) Group 0000 length
(617) 03-26 17:58:29.54 MC3 T7: (1): 90
(617) 03-26 17:58:29.54 MC3 T7: (0000,0003) Requested SOP class UID
(617) 03-26 17:58:29.54 MC3 T7: (1): 1.2.840.10008.5.1.1.16
(617) 03-26 17:58:29.54 MC3 T7: (0000,0100) Command field
(617) 03-26 17:58:29.54 MC3 T7: (1): 272 (N_GET)
(617) 03-26 17:58:29.54 MC3 T7: (0000,0110) Message ID
(617) 03-26 17:58:29.54 MC3 T7: (1): 0
(617) 03-26 17:58:29.54 MC3 T7: (0000,0800) Data set type
(617) 03-26 17:58:29.54 MC3 T7: (1): 257
(617) 03-26 17:58:29.54 MC3 T7: (0000,1001) Requested SOP instance UID
(617) 03-26 17:58:29.54 MC3 T7: (1): 1.2.840.10008.5.1.1.17 (always the same instance
UID)

1. d) On T7 you will see the 'Command Set' of the response from the camera
(618) 03-26 17:58:29.84 MC3 T7: Message received on context 1
(618) 03-26 17:58:29.84 MC3 T7: Group 0x0000 elements:
(618) 03-26 17:58:29.84 MC3 T7: (0000,0000) Group 0000 length
(618) 03-26 17:58:29.84 MC3 T7: (1): 100
(618) 03-26 17:58:29.84 MC3 T7: (0000,0002) Affected SOP class UID

Siemens AG TD00-000.840.01.03.02 Page 71 of 106 DICOM

Medical Solutions 06.04 CS SD 21
72 Appendix

(618) 03-26 17:58:29.84 MC3 T7: (1): 1.2.840.10008.5.1.1.16

(618) 03-26 17:58:29.84 MC3 T7: (0000,0100) Command field
(618) 03-26 17:58:29.84 MC3 T7: (1): 33040 (N_GET response)
(618) 03-26 17:58:29.84 MC3 T7: (0000,0120) Message ID being responded to
(618) 03-26 17:58:29.84 MC3 T7: (1): 0
(618) 03-26 17:58:29.84 MC3 T7: (0000,0800) Data set type
(618) 03-26 17:58:29.84 MC3 T7: (1): 65278
(618) 03-26 17:58:29.84 MC3 T7: (0000,0900) Status
(618) 03-26 17:58:29.84 MC3 T7: (1): 0 (SUCCESS)
(618) 03-26 17:58:29.84 MC3 T7: (0000,1000) Affected SOP instance UID
(618) 03-26 17:58:29.84 MC3 T7: (1): 1.2.840.10008.5.1.1.17

1. e) On trace level T2 you can again see the 'Command Set' (group 0000) and the
'Data Set' (group 0008 and higher) of the response from the camera. Because the
printer request has no data set, you will find no information on T2 trace level.
(618) 03-26 17:58:29.84 MC3 T2: Message (PRINTER,N_GET_RSP) received on context
1
(618) ============================================================
(618) Message ID: 118
(618) Service supported: PRINTER (0024)
(618) Command supported: N_GET_RSP
(618) Message attributes:
(618) 0000,0000 Group 0000 length VR: UL VM: 1
(618) (0000004) |100|
(618) 0000,0002 Affected SOP class UID VR: UI VM: 1
(618) (0000022) |1.2.840.10008.5.1.1.16|
(618) 0000,0100 Command field VR: US VM: 1
(618) (0000002) |33040|
(618) 0000,0120 Message ID being responded to VR: US VM: 1
(618) (0000002) |0|
(618) 0000,0800 Data Set Type VR: US VM: 1
(618) (0000002) |65278|
(618) 000,0900 Status VR: US VM: 1
(618) (0000002) |0|
(618) 0000,1000 Affected SOP instance UID VR: UI VM: 1
(618) (0000022) |1.2.840.10008.5.1.1.17|
(618) 0008,0070 Manufacturer VR: LO VM: 1
(618) (0000005) |Kodak|
(618) 0008,1090 Manufacturer's model name VR: LO VM: 1

DICOM TD00-000.840.01.03.02 Page 72 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 73

(618) (0000006) |M_8700|

(618) 0018,1020 Software version(s) VR: LO VM: 1-n
(618) (0000000) <null>
(618) 1001,0010 Private creator code VR: LO VM: 1
(618) (0000030) |IMATION1.2.840.113720.1.9410.2|
(618) 1001,1000 Non-standard attribute VR: IS VM: 1-n
(618) (0000001) |0|
(618) 2110,0010 Printer status VR: CS VM: 1
(618) (0000007) |WARNING|
(618) 2110,0020 Printer status Info VR: CS VM: 1
(618) (0000012) |SUPPLY EMPTY|
(618) 2110,0030 Printer name VR: LO VM: 1
(618) (0000011) |DryView8700|
(618) ===== End of Message ID: 118 =====

2.) Printer Service (which is also sent at the beginning of each print session)
If you print a film again, the association negotiation and a PRINTER request will be
performed.
This is the same procedure as shown above. Therefore only part of this service is
displayed.
(579) 03-26 18:00:03.67 MC3 T3: REQUEST association parameters:
(579) 03-26 18:00:03.67 MC3 T3: Calling_presentation_address: csyngo2
(579) 03-26 18:00:03.67 MC3 T3: Called_presentation_address: PL102625:1024
(579) 03-26 18:00:03.68 MC3 T3: Called_application_title: SYNGO_8700
(579) 03-26 18:00:03.68 MC3 T3: Calling_application_title: CSYNGO2
(579) 03-26 18:00:03.68 MC3 T3: Application_context_name: 1.2.840.10008.3.1.1.1
(579) 03-26 18:00:03.68 MC3 T3: PDU_maximum_length: 28672
(579) 03-26 18:00:03.68 MC3 T3: Implem_class_uid: 1.3.12.2.1107.5.9.20000101
(579) 03-26 18:00:03.68 MC3 T3: Version_name: SIEMENS_SWFVB10A
(579) 03-26 18:00:03.68 MC3 T3: Max_operations_invoked: Not Sent
(579) 03-26 18:00:03.68 MC3 T3: Max_operations_performed: Not Sent
(579) 03-26 18:00:03.68 MC3 T3: PRESENTATION CONTEXTS:
(579) 03-26 18:00:03.68 MC3 T3: (1) Pres_context_id: 1
(579) 03-26 18:00:03.68 MC3 T3: (1) Abstract_syntax: 1.2.840.10008.5.1.1.9
(BASIC_GRAYSCALE_PRINT_MANAGEMENT)
........
........
........

Siemens AG TD00-000.840.01.03.02 Page 73 of 106 DICOM

Medical Solutions 06.04 CS SD 21
74 Appendix

(691) 2110,0010 Printer status VR: CS VM: 1

(691) (0000007) WARNING
(691) 2110,0020 Printer status info VR: CS VM:1
(691) (0000012) SUPPLY EMPTY
(691) 2110,0030 Printer name VR: LO VM: 1
(691) (0000011) DryView8700
(691) ===== End of Message ID: 182 =====

3. a) Basic Film Session Service (N_Create to set the camera parameter)

After the PRINTER service, the BASIC FILM SESSION service is performed. This is
again a service of the Basic Gray scale Print Management Meta Service (context
ID 1).
In this service, global camera parameters are set.
The request can be seen on trace level T7 (Command Set)
(692) 03-26 18:00:13.10 MC3 T7: Message
(BASIC_FILM_SESSION,N_CREATE_RQ)sentoncontext1
(692) 03-26 18:00:13.12 MC3 T7: Group 0x0000 Elements:
(692) 03-26 18:00:13.12 MC3 T7: (0000,0000) Group 0000 length
(692) 03-26 18:00:13.12 MC3 T7: (1): 60
(692) 03-26 18:00:13.12 MC3 T7: (0000,0002) Affected SOP class UID
(692) 03-26 18:00:13.12 MC3 T7: (1): 1.2.840.10008.5.1.1.1
(692) 03-26 18:00:13.12 MC3 T7: (0000,0100) Command field
(692) 03-26 18:00:13.12 MC3 T7: (1): 320
(692) 03-26 18:00:13.12 MC3 T7: (0000,0110) Message ID
(692) 03-26 18:00:13.12 MC3 T7: (1): 2
(692) 03-26 18:00:13.12 MC3 T7: (0000,0800) Data set type
(692) 03-26 18:00:13.12 MC3 T7: (1): 0

3. b) Since this request includes also a 'Data Set' (group 2000), you will also see the
request on trace level T2.
(692) 03-26 18:00:13.12 MC3 T2: Message (BASIC_FILM_SESSION,N_CREATE_RQ)
sent on context 1
(692) ============================================================
(692) Message ID: 190
(692) Service supported: BASIC_FILM_SESSION (0003)
(692) Command supported: N_CREATE_RQ
(692) Message attributes:
(692) 0000,0000 Group 0000 length VR: UL VM: 1
(692) (0000004) |60|

DICOM TD00-000.840.01.03.02 Page 74 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 75

(692) 0000,0002 Affected SOP class UID VR: UI VM: 1

(692) (0000021) |1.2.840.10008.5.1.1.1|
(692) 0000,0100 Command field VR: US VM: 1
(692) (0000002) |320|
(692) 0000,0110 Message ID VR: US VM: 1
(692) (0000002) |2|
(692) 000,0800 Data set type VR: US VM: 1
(692) (0000002) |0|
(692) 2000,0010 Number of copies VR: IS VM: 1
(692) (0000001) |1|
(692) 2000,0030 Medium type VR: CS VM: 1
(692) (0000009) |BLUE FILM|
(692) 2000,0040 Film destination VR: CS VM: 1
(692) (0000009) |PROCESSOR|
(692) ===== End of Message ID: 190 =====

3. c) On T7 you will see the 'Command Set' of the response from the camera
(691) 03-26 18:00:13.40 MC3 T7: Message received on context 1
(691) 03-26 18:00:13.40 MC3 T7: Group 0x0000 elements:
(691) 03-26 18:00:13.40 MC3 T7: (0000,0000) Group 0000 length
(691) 03-26 18:00:13.40 MC3 T7: (1): 118
(691) 03-26 18:00:13.40 MC3 T7: (0000,0002) Affected SOP class UID
(691) 03-26 18:00:13.40 MC3 T7: (1): 1.2.840.10008.5.1.1.1
(691) 03-26 18:00:13.40 MC3 T7: (0000,0100) Command field
(691) 03-26 18:00:13.40 MC3 T7: (1): 33088
(691) 03-26 18:00:13.40 MC3 T7: (0000,0120) Message ID being responded to
(691) 03-26 18:00:13.40 MC3 T7: (1): 2
(691) 03-26 18:00:13.40 MC3 T7: (0000,0800) Data set type
(691) 03-26 18:00:13.40 MC3 T7: (1): 65278
(691) 03-26 18:00:13.40 MC3 T7: (0000,0900) Status
(691) 03-26 18:00:13.40 MC3 T7: (1): 0
(691) 03-26 18:00:13.40 MC3 T7: (0000,1000) Affected SOP instance UID
(691) 03-26 18:00:13.40 MC3 T7: (1): 1.2.840.113720.1.9410.2.20010326173705.5

4. d) On T2 you will again see the 'Command Set' as well as the 'Data Set' of the
response.
(691) 03-26 18:00:13.40 MC3 T2: Message
(BASIC_FILM_SESSION,N_CREATE_RSP) received on context 1

Siemens AG TD00-000.840.01.03.02 Page 75 of 106 DICOM

Medical Solutions 06.04 CS SD 21
76 Appendix

(691) ==========================================================
(691) Message ID: 191
(691) Service supported: BASIC_FILM_SESSION (0003)
(691) Command supported: N_CREATE_RSP
(691) Message attributes:
(691) 0000,0000 Group 0000 length VR: UL VM: 1
(691) (0000004) 118
(691) 0000,0002 Affected SOP class UID VR: UI VM: 1
(691) (0000021) 1.2.840.10008.5.1.1.1
(691) 0000,0100 Command field VR: US VM: 1
(691) (0000002) 33088
(691) 0000,0120 Message ID being responded to VR: US VM: 1
(691) (0000002) 2
(691) 0000,0800 Data set type VR: US VM: 1
(691) (0000002) 65278
(691) 0000,0900 Status VR: US VM: 1
(691) (0000002) 0
(691) 0000,1000 Affected SOP instance UID VR: UI VM: 1
(691) (0000040) 1.2.840.113720.1.9410.2.20010326173705.5
(691) 2000,0010 Number of copies VR: IS VM: 1
(691) (0000001) 1
(691) 2000,0020 Print priority VR: CS VM: 1
(691) (0000004) HIGH
(691) 000,0030 Medium type VR: CS VM: 1
(691) (0000009) BLUE FILM
(691) 2000,0040 Film destination VR: CS VM: 1
(691) (0000009) PROCESSOR
(691) ===== End of Message ID: 191 =====

4. a) Basic Film Box Service (N_Create to set the film parameter)

Following the Basic Film Session, the BASIC FILM BOX Service is performed,
which is again a service of the Basic Gray scale Print Management Meta Service
(context ID 1).
In this service, parameters for the film layout are set.
The request can be seen on trace level T7 (Command Set)
(692) 03-26 18:00:14.42 MC3 T7: Message (BASIC_FILM_BOX,N_CREATE_RQ) sent
on context 1
(692) 03-26 18:00:14.42 MC3 T7: Group 0x0000 Elements:
(692) 03-26 18:00:14.42 MC3 T7: (0000,0000) Group 0000 length

DICOM TD00-000.840.01.03.02 Page 76 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 77

(692) 03-26 18:00:14.42 MC3 T7: (1): 60

(692) 03-26 18:00:14.42 MC3 T7: (0000,0002) Affected SOP class UID
(692) 03-26 18:00:14.42 MC3 T7: (1): 1.2.840.10008.5.1.1.2
(692) 03-26 18:00:14.42 MC3 T7: (0000,0100) Command field
(692) 03-26 18:00:14.42 MC3 T7: (1): 320
(692) 03-26 18:00:14.42 MC3 T7: (0000,0110) Message ID
(692) 03-26 18:00:14.42 MC3 T7: (1): 3
(692) 03-26 18:00:14.42 MC3 T7: (0000,0800) Data set type
(692) 03-26 18:00:14.42 MC3 T7: (1): 0

4. b) Since this request includes also a 'Data Set' (group 2000), you will also see the
request on trace level T2.
(692) 03-26 18:00:14.42 MC3 T2: Message (BASIC_FILM_BOX,N_CREATE_RQ) sent
on context 1
(692) ===========================================================
(692) Message ID: 193
(692) Service supported: BASIC_FILM_BOX (0002)
(692) Command supported: N_CREATE_RQ
(692) Message attributes:
(692) 0000,0000 Group 0000 length VR: UL VM: 1
(692) (0000004) |60|
(692) 0000,0002 Affected SOP class UID VR: UI VM: 1
(692) (0000021) |1.2.840.10008.5.1.1.2|
(692) 0000,0100 Command field VR: US VM: 1
(692) (0000002) |320|
(692) 0000,0110 Message ID VR: US VM: 1
(692) (0000002) |3|
(692) 0000,0800 Data set type VR: US VM: 1
(692) (0000002) |0|
(692) 2010,0010 Image display format VR: ST VM: 1
(692) (0000012) |STANDARD\1,1|
(692) 2010,0040 Film orientation VR: CS VM: 1
(692) (0000008) |PORTRAIT|
(692) 2010,0050 Film size ID VR: CS VM: 1
(692) (0000009) |14INX17IN|
(692) 2010,0060 Magnification type VR: CS VM: 1
(692) (0000004) |NONE|
(692) 2010,0120 Min density VR: US VM: 1

Siemens AG TD00-000.840.01.03.02 Page 77 of 106 DICOM

Medical Solutions 06.04 CS SD 21
78 Appendix

(692) (0000002) |20|

(692) 2010,0130 Max density VR: US VM: 1
(692) (0000002) |280|
(692) 2010,0500 Referenced film session sequence VR: SQ VM: 1
(692) ============================================================
(692) <Sequence: Item 194 of message 193 (2010,0500)>
(692) ===========================================================
(692) Item ID: 194
(692) Item attributes:
(692) 0008,1150 Referenced SOP class UID VR: UI VM: 1
(692) (0000021) |1.2.840.10008.5.1.1.1|
(692) 0008,1155 Referenced SOP instance UID VR: UI VM: 1
(692) (0000040) |1.2.840.113720.1.9410.2.20010326173705.5|
(692) ===== End of Item ID: 194 =========
(692) Message ID: 193 (continued)
(692) ===== End of Message ID: 193 =====

4. c) On T7 you will see the 'Command Set' of the response from the camera
(691) 03-26 18:00:14.71 MC3 T7: Message received on context 1
(691) 03-26 18:00:14.71 MC3 T7: Group 0x0000 elements:
(691) 03-26 18:00:14.71 MC3 T7: (0000,0000) Group 0000 length
(691) 03-26 18:00:14.71 MC3 T7: (1): 120
(691) 03-26 18:00:14.71 MC3 T7: (0000,0002) Affected SOP class UID
(691) 03-26 18:00:14.73 MC3 T7: (1): 1.2.840.10008.5.1.1.2
(691) 03-26 18:00:14.73 MC3 T7: (0000,0100) Command field
(691) 03-26 18:00:14.73 MC3 T7: (1): 33088
(691) 03-26 18:00:14.73 MC3 T7: (0000,0120) Message ID being responded to
(691) 03-26 18:00:14.73 MC3 T7: (1): 3
(691) 03-26 18:00:14.73 MC3 T7: (0000,0800) Data set type
(691) 03-26 18:00:14.73 MC3 T7: (1): 65278
(691) 03-26 18:00:14.73 MC3 T7: (0000,0900) Status
(691) 03-26 18:00:14.73 MC3 T7: (1): 0
(691) 03-26 18:00:14.73 MC3 T7: (0000,1000) Affected SOP instance UID
(691) 03-26 18:00:14.73 MC3 T7: (1): 1.2.840.113720.1.9410.2.20010326173706.5.1

4. d) On T2 you will again see the 'Command Set' as well as the 'Data Set' of the
response.

DICOM TD00-000.840.01.03.02 Page 78 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 79

(691) 03-26 18:00:14.73 MC3 T2: Message (BASIC_FILM_BOX,N_CREATE_RSP)

received on context 1
(691) ============================================================
(691) Message ID: 195
(691) Service supported: BASIC_FILM_BOX (0002)
(691) Command supported: N_CREATE_RSP
(691) Message attributes:
(691) 0000,0000 Group 0000 length VR: UL VM: 1
(691) (0000004) |120|
(691) 0000,0002 Affected SOP class UID VR: UI VM: 1
(691) (0000021) |1.2.840.10008.5.1.1.2
(691) 0000,0100 Command field VR: US VM: 1
(691) (0000002) |33088|
(691) 0000,0120 Message ID being responded to VR: US VM: 1
(691) (0000002) |3|
(691) 0000,0800 Data set type VR: US VM: 1
(691) (0000002) |65278|
(691) 0000,0900 Status VR: US VM: 1
(691) (0000002) |0|
(691) 0000,1000 Affected SOP instance UID VR: UI VM: 1
(691) (0000042) |1.2.840.113720.1.9410.2.20010326173706.5.1 |
(691) 2010,0010 Image display format VR: ST VM: 1
(691) (0000012) |STANDARD\1,1|
(691) 010,0030 Annotation display format ID VR: CS VM: 1
(691) (0000004) |NONE|
(691) 2010,0040 Film orientation VR: CS VM: 1
(691) (0000008) |PORTRAIT|
(691) 010,0050 Film size ID VR: CS VM: 1
(691) (0000009) |14INX17IN|
(691) 2010,0060 Magnification type VR: CS VM: 1
(691) (0000004) |NONE|
(691) 2010,0100 Border density VR: CS VM: 1
(691) (0000005) |BLACK|
(691) 2010,0110 Empty image density VR: CS VM: 1
(691) (0000005) |BLACK|
(691) 2010,0130 Max density VR: US VM: 1
(691) (0000002) |280|
(691) 2010,0140 Trim VR: CS VM: 1

Siemens AG TD00-000.840.01.03.02 Page 79 of 106 DICOM

Medical Solutions 06.04 CS SD 21
80 Appendix

(691) (0000002) |NO|

(691) 2010,0150 Configuration information VR: ST VM: 1
(691) (0000000) <null>
(691) 2010,0500 Referenced film session sequence VR: SQ VM: 1
(691) ============================================================
(691) <Sequence: Item 196 of message 195 (2010,0500)>
(691) ============================================================
(691) Item ID: 196
(691) Item attributes:
(691) 0008,1150 Referenced SOP class UID VR: UI VM: 1
(691) (0000021) |1.2.840.10008.5.1.1.1|
(691) 0008,1155 Referenced SOP instance UID VR: UI VM: 1
(691) (0000040) |1.2.840.113720.1.9410.2.20010326173705.5|
(691) ===== End of Item ID: 196 =====
(691) Message ID: 195 (continued)
(691) 2010,0510 Referenced image box sequence VR: SQ VM: 1
(691) ============================================================
(691) <Sequence: Item 197 of message 195 (2010,0510)>
(691) ============================================================
(691) Item ID: 197
(691) Item attributes:
(691) 0008,1150 Referenced SOP class UID VR: UI VM: 1
(691) (0000021) |1.2.840.10008.5.1.1.4|
(691) 0008,1155 Referenced SOP instance UID VR: UI VM: 1
(691) (0000044) |1.2.840.113720.1.9410.2.20010326173706.5.1.1|
(691) ===== End of Item ID: 197 =========
(691) Message ID: 195 (continued)
(691) ===== End of Message ID: 195 =====

5. a) Basic Gray scale Image Box Service (N_Set to send the image data)
Following the Basic Film Box, the BASIC IMAGE BOX Service is performed.
In this Service parameters for the image including the pixel data will be sent.
The request can be seen on trace level T7 (Command Set)
(692) 03-26 18:00:17.04 MC3 T7: Message
(BASIC_GRAYSCALE_IMAGE_BOX,N_SET_RQ) sent on context
1
(692) 03-26 18:00:17.04 MC3 T7: (0000,0000) Group 0000 length
(692) 03-26 18:00:17.04 MC3 T7: (1): 112

DICOM TD00-000.840.01.03.02 Page 80 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 81

(692) 03-26 18:00:17.04 MC3 T7: (0000,0003) Requested SOP class UID
(692) 03-26 18:00:17.04 MC3 T7: (1): 1.2.840.10008.5.1.1.4
(692) 03-26 18:00:17.04 MC3 T7: (0000,0100) Command field
(692) 03-26 18:00:17.04 MC3 T7: (1): 288
(692) 03-26 18:00:17.04 MC3 T7: (0000,0110) Message ID
(692) 03-26 18:00:17.04 MC3 T7: (1): 4
(692) 03-26 18:00:17.04 MC3 T7: (0000,0800) Data set type
(692) 03-26 18:00:17.04 MC3 T7: (1): 0
(692) 03-26 18:00:17.04 MC3 T7: (0000,1001) Requested SOP instance UID
(692) 03-26 18:00:17.04 MC3 T7:(1):1.2.840.113720.1.9410.2.20010326173706.5.1.1

5. b) Since this request also includes a 'Data Set' (group 2020, group 0028), you will
also see the request on trace level T2.
(692) 03-26 18:00:17.04 MC3 T7: Group 0x0000 elements:
(692) 03-26 18:00:50.15 MC3 T2: Message
(BASIC_GRAYSCALE_IMAGE_BOX,N_SET_RQ) sent on context
1 (692)
============================================================
(692) Message ID: 200
(692) Service supported: BASIC_GRAYSCALE_IMAGE_BOX (0004)
(692) Command supported: N_SET_RQ
(692) Message attributes:
(692) 0000,0000 Group 0000 length VR: UL VM: 1
(692) (0000004) |112|
(692) 0000,0003 Requested SOP class UID VR: UI VM: 1
(692) (0000021) |1.2.840.10008.5.1.1.4| (MR image)
(692) 0000,0100 Command field VR: US VM: 1
(692) (0000002) |288|
(692) 000,0110 Message ID VR: US VM: 1
(692) (0000002) |4|
(692) 0000,0800 Data set type VR: US VM: 1
(692) (0000002) |0|
(692) 000,1001 Requested SOP instance UID VR: UI VM: 1
(692) (0000044) |1.2.840.113720.1.9410.2.20010326173706.5.1.1|
(692) 020,0010 Image position VR: US VM: 1
(692) (0000002) |1|
(692) 2020,0110 Basic Gray scale Image Sequence VR: SQ VM: 1
(692) ============================================================
(692) <Sequence: Item 201 of message 200 (2020,0110)>

Siemens AG TD00-000.840.01.03.02 Page 81 of 106 DICOM

Medical Solutions 06.04 CS SD 21
82 Appendix

(692) =============================================================
(692) Item ID: 201
(692) Item attributes:
(692) 0028,0002 Samples per pixel VR: US VM: 1
(692) (0000002) |1|
(692) 0028,0004 Photometric interpretation VR: CS VM: 1
(692) (0000011) |MONOCHROME2|
(692) 0028,0010 Rows VR: US VM: 1
(692) 0000002) |5220|
(692) 0028,0011 Columns VR: US VM: 1
(692) (0000002) |4096|
(692) 0028,0034 Pixel aspect ratio VR: IS VM: 2
(692) (0000002) |1| |1|
(692) 0028,0100 Bits allocated VR: US VM: 1
(692) (0000002) |8|
(692) 0028,0101 Bits stored VR: US VM: 1
(692) (0000002) |8|
(692) 0028,0102 High bit VR: US VM: 1
(692) (0000002) |7|
(692) 028,0103 Pixel representation VR: US VM: 1
(692) (0000002) |0|
(692) 7FE0,0010 Pixel data VR: OW VM: 1
(692) (21381120) <OB, OW, OL data>
(692) ===== End of Item ID: 201 =========
(692) Message ID: 200 (continued)
(692) ===== End of message ID: 200 =====

5. c) On T7 you will see the 'Command Set' of the response from the camera
(691) 03-26 18:00:50.57 MC3 T7: Message received on context 1
(691) 03-26 18:00:50.57 MC3 T7: Group 0x0000 elements:
(691) 03-26 18:00:50.57 MC3 T7: (0000,0000) Group 0000 length
(691) 03-26 18:00:50.57 MC3 T7: (1): 122
(691) 03-26 18:00:50.57 MC3 T7: (0000,0002) Affected SOP class UID
(691) 03-26 18:00:50.57 MC3 T7: (1): 1.2.840.10008.5.1.1.4
(691) 03-26 18:00:50.57 MC3 T7: (0000,0100) Command field
(691) 03-26 18:00:50.57 MC3 T7: (1): 33056
(691) 03-26 18:00:50.57 MC3 T7: (0000,0120) Message ID being responded to
(691) 03-26 18:00:50.57 MC3 T7: (1): 4

DICOM TD00-000.840.01.03.02 Page 82 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 83

(691) 03-26 18:00:50.57 MC3 T7: (0000,0800) Data set type

(691) 03-26 18:00:50.57 MC3 T7: (1): 65278
(691) 03-26 18:00:50.57 MC3 T7: (0000,0900) Status
(691) 03-26 18:00:50.57 MC3 T7: (1): 0
(691) 03-26 18:00:50.57 MC3 T7: (0000,1000) Affected SOP instance UID
(691) 03-26 18:00:50.57 MC3 T7:(1):1.2.840.113720.1.9410.2.20010326173706.5.1.1

5. d) On T2 you will again see the 'Command Set' as well as the 'Data Set' of the
response.
(691) 03-26 18:00:50.57 MC3 T2: Message
(BASIC_GRAYSCALE_IMAGE_BOX,N_SET_RSP) received on context
1
(691) ============================================================
(691) Message ID: 202
(691) Service supported: BASIC_GRAYSCALE_IMAGE_BOX (0004)
(691) Command supported: N_SET_RSP
(691) Message attributes:
(691) 0000,0000 Group 0000 length VR: UL VM: 1
(691) (0000004) 122
(691) 0000,0002 Affected SOP class UID VR: UI VM: 1
(691) (0000021) 1.2.840.10008.5.1.1.4
(691) 0000,0100 Command field VR: US VM: 1
(691) (0000002) |33056|
(691) 000,0120 Message ID Being responded to VR: US VM: 1
(691) (0000002) 4
(691) 0000,0800 Data set type VR: US VM: 1
(691) (0000002) 65278
(691) 0000,0900 Status VR: US VM: 1
(691) (0000002) 0
(691) 0000,1000 Affected SOP instance UID VR: UI VM: 1
(691) (0000044) 1.2.840.113720.1.9410.2.20010326173706.5.1.1
(691) 2010,0060 Magnification type VR: CS VM: 1
(691) (0000007) UNKNOWN
(691) 2020,0010 Image position VR: US VM: 1
(691) (0000002) 1
(691) 2020,0020 Polarity VR: CS VM: 1
(691) (0000006) NORMAL
(691) 2020,0030 Requested image size VR: DS VM: 1
(691) (0000002) -1

Siemens AG TD00-000.840.01.03.02 Page 83 of 106 DICOM

Medical Solutions 06.04 CS SD 21
84 Appendix

(691) 2020,0110 Basic Gray scale image sequence VR: SQ VM: 1

(691) ============================================================
(691) <Sequence: Item 203 of message 202 (2020,0110)>
(691) ============================================================
(691) Item ID: 203
(691) Item Attributes:
(691) 0028,0002 Samples per pixel VR: US VM: 1
(691) (0000002) 1
(691) 0028,0004 Photometric interpretation VR: CS VM: 1
(691) (0000011) MONOCHROME2
(691) 0028,0010 Rows VR: US VM: 1
(691) (0000002) 5220
(691) 0028,0011 Columns VR: US VM: 1
(691) (0000002) 4096|
(691) 0028,0034 Pixel aspect ratio VR: IS VM: 2
(691) 0000002) 1 1
(691) 0028,0100 Bits allocated VR: US VM: 1
(691) (0000002) 8
(691) 0028,0101 Bits stored VR: US VM: 1
(691) (0000002) 8
(691) 0028,0102 High bit VR: US VM: 1
(691) (0000002) 7
(691) 0028,0103 Pixel representation VR: US VM: 1
(691) (0000002) 1
(691) ===== End of Item ID: 203 ========
(691) Message ID: 202 (continued)
(691) ===== End of Message ID: 202 ====

6. a) Basic Film Box Service (N_Action to print the film)

Following the Basic Image Boxes (syngo always sends just one image for one film),
the BASIC FILM BOX service is performed again (N_Action) to print out the film.
The request can be seen on trace level T7 (Command Set)
(692) 03-26 18:00:51.60 MC3 T7: Message (BASIC_FILM_BOX,N_ACTION_RQ) sent on
context 1
(692) 03-26 18:00:51.60 MC3 T7: Group 0x0000 elements:
(692) 03-26 18:00:51.60 MC3 T7: (0000,0000) Group 0000 length
(692) 03-26 18:00:51.60 MC3 T7: (1): 120
(692) 03-26 18:00:51.60 MC3 T7: (0000,0003) Requested SOP class UID

DICOM TD00-000.840.01.03.02 Page 84 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 85

(692) 03-26 18:00:51.60 MC3 T7: (1): 1.2.840.10008.5.1.1.2

(692) 03-26 18:00:51.60 MC3 T7: (0000,0100) Command field
(692) 03-26 18:00:51.60 MC3 T7: (1): 304 (N_ACION)
(692) 03-26 18:00:51.60 MC3 T7: (0000,0110) Message ID
(692) 03-26 18:00:51.60 MC3 T7: (1): 5
(692) 03-26 18:00:51.60 MC3 T7: (0000,0800) Data set type
(692) 03-26 18:00:51.60 MC3 T7: (1): 257
(692) 03-26 18:00:51.60 MC3 T7: (0000,1001) Requested SOP instance UID
(692) 03-26 18:00:51.60 MC3 T7: (1): 1.2.840.113720.1.9410.2.20010326173706.5.1
(692) 03-26 18:00:51.60 MC3 T7: (0000,1008) Action type ID
(692) 03-26 18:00:51.60 MC3 T7: (1): 1

6. b) On T7 you will see the 'Command Set' of the response from the camera
(691) 03-26 18:00:52.40 MC3 T7: Message received on context 1
(691) 03-26 18:00:52.40 MC3 T7: Group 0x0000 elements:
(691) 03-26 18:00:52.40 MC3 T7: (0000,0000) Group 0000 length
(691) 03-26 18:00:52.40 MC3 T7: (1): 130
(691) 03-26 18:00:52.40 MC3 T7: (0000,0002) Affected SOP class UID
(691) 03-26 18:00:52.40 MC3 T7: (1): 1.2.840.10008.5.1.1.2
(691) 03-26 18:00:52.40 MC3 T7: (0000,0100) Command field
(691) 03-26 18:00:52.40 MC3 T7: (1): 33072
(691) 03-26 18:00:52.40 MC3 T7: (0000,0120) Message ID being responded to
(691) 03-26 18:00:52.40 MC3 T7: (1): 5
(691) 03-26 18:00:52.40 MC3 T7: (0000,0800) Data set type
(691) 03-26 18:00:52.40 MC3 T7: (1): 65278
(691) 03-26 18:00:52.40 MC3 T7: (0000,0900) Status
(691) 03-26 18:00:52.40 MC3 T7: (1): 0
(691) 03-26 18:00:52.40 MC3 T7: (0000,1000) Affected SOP instance UID
(691) 03-26 18:00:52.40 MC3 T7: (1): 1.2.840.113720.1.9410.2.20010326173706.5.1
(691) 03-26 18:00:52.40 MC3 T7: (0000,1008) Action type ID
(691) 03-26 18:00:52.40 MC3 T7: (1): 1

6. c) On T2 you will again see the 'Command Set' as well as the 'Data Set' of the
response.
(691) 03-26 18:00:52.40 MC3 T2: Message (BASIC_FILM_BOX,N_ACTION_RSP)
received on context 1
(691) ============================================================
(691) Message ID: 206

Siemens AG TD00-000.840.01.03.02 Page 85 of 106 DICOM

Medical Solutions 06.04 CS SD 21
86 Appendix

(691) Service supported: BASIC_FILM_BOX (0002)

(691) Command supported: N_ACTION_RSP
(691) Message attributes:
(691) 000,0000 Group 0000 length VR: UL VM: 1
(691) (0000004) |130|
(691) 0000,0002 Affected SOP class UID VR: UI VM: 1
(691) (0000021) |1.2.840.10008.5.1.1.2|
(691) 0000,0100 Command field VR: US VM: 1
(691) (0000002) |33072|
(691) 0000,0120 Message ID being responded to VR: US VM: 1
(691) (0000002) |5|
(691) 0000,0800 Data Set Type VR: US VM: 1
(691) (0000002) |65278|
(691) 0000,0900 Status VR: US VM: 1
(691) (0000002) |0|
(691) 0000,1000 Affected SOP instance UID VR: UI VM: 1
(691) (0000042) |1.2.840.113720.1.9410.2.20010326173706.5.1|
(691) 0000,1008 Action type ID VR: US VM: 1
(691) (0000002) |1|
(691) 2100,0500 Referenced print job sequence VR: SQ VM: 1
(691) ============================================================
(691) <Sequence: Item 207 of message 206 (2100,0500)>
(691) ============================================================
(691) Item ID: 207
(691) Item attributes:
(691) 0008,1150 Referenced SOP class UID VR: UI VM: 1
(691) (0000022) |1.2.840.10008.5.1.1.14|
(691) 0008,1155 Referenced SOP instance UID VR: UI VM: 1
(691) (0000044) |1.2.840.113720.1.9410.2.20010326173744.5.0.6|
(691) ===== End of Item ID: 207 =========
(691) Message ID: 206 (continued)
(691) ===== End of message ID: 206 =====

7. a) Basic Film Box Service (N_Delete to delete the session)

After printing the film, syngo will delete the FILM BOX service.
The request can be seen on trace level T7 (Command Set)
(692) 03-26 18:00:53.42 MC3 T7: Message (BASIC_FILM_BOX,N_DELETE_RQ) sent on
context 1

DICOM TD00-000.840.01.03.02 Page 86 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 87

(692) 03-26 18:00:53.42 MC3 T7: Group 0x0000 Elements:

(692) 03-26 18:00:53.42 MC3 T7: (0000,0000) Group 0000 length
(692) 03-26 18:00:53.42 MC3 T7: (1): 110
(692) 03-26 18:00:53.42 MC3 T7: (0000,0003) Requested SOP class UID
(692) 03-26 18:00:53.42 MC3 T7: (1): 1.2.840.10008.5.1.1.2
(692) 03-26 18:00:53.42 MC3 T7: (0000,0100) Command field
(692) 03-26 18:00:53.42 MC3 T7: (1): 336 (N_Delete)
(692) 03-26 18:00:53.42 MC3 T7: (0000,0110) Message ID
(692) 03-26 18:00:53.42 MC3 T7: (1): 6
(692) 03-26 18:00:53.42 MC3 T7: (0000,0800) Data set type
(692) 03-26 18:00:53.42 MC3 T7: (1): 257
(692) 03-26 18:00:53.42 MC3 T7: (0000,1001) Requested SOP instance UID
(692) 03-26 18:00:53.42 MC3 T7: (1): 1.2.840.113720.1.9410.2.20010326173706.5.1

7. b) On T7 you will see the 'Command Set' of the response from the camera
(691) 03-26 18:00:53.71 MC3 T7: Message received on context 1
(691) 03-26 18:00:53.71 MC3 T7: Group 0x0000 elements:
(691) 03-26 18:00:53.71 MC3 T7: (0000,0000) Group 0000 length
(691) 03-26 18:00:53.73 MC3 T7: (1): 120
(691) 03-26 18:00:53.73 MC3 T7: (0000,0002) Affected SOP class UID
(691) 03-26 18:00:53.73 MC3 T7: (1): 1.2.840.10008.5.1.1.2
(691) 03-26 18:00:53.73 MC3 T7: (0000,0100) Command field
(691) 03-26 18:00:53.73 MC3 T7: (1): 33104
(691) 03-26 18:00:53.73 MC3 T7: (0000,0120) Message ID being responded to
(691) 03-26 18:00:53.73 MC3 T7: (1): 6
(691) 03-26 18:00:53.73 MC3 T7: (0000,0800) Data set type
(691) 03-26 18:00:53.73 MC3 T7: (1): 257
(691) 03-26 18:00:53.73 MC3 T7: (0000,0900) Status
(691) 03-26 18:00:53.73 MC3 T7: (1): 0
(691) 03-26 18:00:53.73 MC3 T7: (0000,1000) Affected SOP instance UID
(691) 03-26 18:00:53.73 MC3 T7: (1): 1.2.840.113720.1.9410.2.20010326173706.5.1

8. a) Basic Film Session Service (N_Delete to delete the print session)

After deleting the film boxes (in this case only one film was printed), the FILM SES-
SION service is deleted.
The request can be seen on trace level T7 (Command Set)
(692) 03-26 18:00:55.73 MC3 T7: Message (BASIC_FILM_SESSION,N_DELETE_RQ)
sent on context 1

Siemens AG TD00-000.840.01.03.02 Page 87 of 106 DICOM

Medical Solutions 06.04 CS SD 21
88 Appendix

(692) 03-26 18:00:55.73 MC3 T7: Group 0x0000 elements:

(692) 03-26 18:00:55.73 MC3 T7: (0000,0000) Group 0000 length
(692) 03-26 18:00:55.73 MC3 T7: (1): 108
(692) 03-26 18:00:55.73 MC3 T7: (0000,0003) Requested SOP class UID
(692) 03-26 18:00:55.73 MC3 T7: (1): 1.2.840.10008.5.1.1.1
(692) 03-26 18:00:55.73 MC3 T7: (0000,0100) Command field
(692) 03-26 18:00:55.73 MC3 T7: (1): 336
(692) 03-26 18:00:55.73 MC3 T7: (0000,0110) Message ID
(692) 03-26 18:00:55.73 MC3 T7: (1): 7
(692) 03-26 18:00:55.73 MC3 T7: (0000,0800) Data set type
(692) 03-26 18:00:55.73 MC3 T7: (1): 257
(692) 03-26 18:00:55.73 MC3 T7: (0000,1001) Requested SOP instance UID
(692) 03-26 18:00:55.73 MC3 T7: (1): 1.2.840.113720.1.9410.2.20010326173705.5

8. b) On T7 you will see the 'Command Set' of the response from the camera
(691) 03-26 18:00:56.06 MC3 T7: Message received on context 1
(691) 03-26 18:00:56.06 MC3 T7: Group 0x0000 elements:
(691) 03-26 18:00:56.06 MC3 T7: (0000,0000) Group 0000 length
(691) 03-26 18:00:56.06 MC3 T7: (1): 118
(691) 03-26 18:00:56.06 MC3 T7: (0000,0002) Affected SOP class UID
(691) 03-26 18:00:56.06 MC3 T7: (1): 1.2.840.10008.5.1.1.1
(691) 03-26 18:00:56.06 MC3 T7: (0000,0100) Command field
(691) 03-26 18:00:56.06 MC3 T7: (1): 33104
(691) 03-26 18:00:56.06 MC3 T7: (0000,0120) Message ID being responded to
(691) 03-26 18:00:56.06 MC3 T7: (1): 7
(691) 03-26 18:00:56.06 MC3 T7: (0000,0800) Data set type
(691) 03-26 18:00:56.06 MC3 T7: (1): 257
(691) 03-26 18:00:56.06 MC3 T7: (0000,0900) Status
(691) 03-26 18:00:56.06 MC3 T7: (1): 0
(691) 03-26 18:00:56.06 MC3 T7: (0000,1000) Affected SOP instance UID
(691) 03-26 18:00:56.06 MC3 T7: (1):

When you turn on trace level T9, you will also see the whole association on the Pro-
tocol Data Unit level (PDU). This will add a lot more information to the log file, which
is just helpful in some special cases. E.g if the transfer is interrupted, you can see
how many packets were successfully transferred. The Association Release request
and response can also be seen only on trace level T9.
(409) 07-21 14:58:29.96 MC3 T9: PDU Type: 05 (Assoc_Rel_RQ) received
(409) 07-21 14:58:29.96 MC3 T9: Reserved byte: 00

DICOM TD00-000.840.01.03.02 Page 88 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 89

(409) 07-21 14:58:29.96 MC3 T9: PDU length: 0000 0004 (4 bytes)
(409) 07-21 14:58:29.96 MC3 T9: Reserved bytes (7-10): 0000 0000
(409) 07-21 14:58:29.96 MC3 T9: PDU Type: 06 (Assoc_Rel_RP) sent
(409) 07-21 14:58:29.96 MC3 T9: Reserved byte: 00
(409) 07-21 14:58:29.96 MC3 T9: PDU length: 0000 0004 (4 bytes)

The Basic Print session was performed successfully. Check the image quality!

Siemens AG TD00-000.840.01.03.02 Page 89 of 106 DICOM

Medical Solutions 06.04 CS SD 21
90 Appendix

DICOM UIDs 0

UID Value UID Name UID Type Part 4,5,7 C/N

1.2.840.10008.1.1 Verification SOP class SOP class A.4 C

1.2.840.10008.1.2 Implicit VR little Indian: Default trans- Transfer A.1 -

fer syntax for DICOM syntax
1.2.840.10008.1.2.1 Explicit VR little Indian Transfer A.2 -
syntax
1.2.840.10008.1.2.2 Explicit VR big Indian Transfer A.3 -
syntax
1.2.840.10008.1.2.4.50 JPEG Baseline (Process 1): default Transfer A.4.1 -
transfer syntax for lossy JPEG 8 Bit syntax
Image Compression
1.2.840.10008.1.2.4.51 JPEG extended (Process 2 & 4): Transfer A.4.1 -
default transfer syntax for JPEG 12 Bit syntax
image compression (process only)
1.2.840.10008.1.2.4.52 JPEG Extended (Process 3 & 5) Transfer A.4.1 -
syntax
1.2.840.10008.1.2.4.53 JPEG spectral selection, non-hierar- Transfer A.4.1 -
chical (Process 6 & 8) syntax
1.2.840.10008.1.2.4.54 JPEG spectral selection, non-hierar- Transfer A.4.1 -
chical (Process 7 & 9) syntax
1.2.840.10008.1.2.4.55 JPEG full progression, non-hierarchi- Transfer A.4.1 -
cal (Process 10 & 12) syntax
1.2.840.10008.1.2.4.56 JPEG full progression, non-hierarchi- Transfer A.4.1 -
cal (Process 11 & 13) syntax
1.2.840.10008.1.2.4.57 JPEG Lossless, non-hierarchical (Pro- Transfer A.4.1 -
cess 14) syntax
1.2.840.10008.1.2.4.58 JPEG Lossless, non-hierarchical (Pro- Transfer A.4.1 -
cess 15) syntax
1.2.840.10008.1.2.4.59 JPEG extended, Hierarchical (Process Transfer A.4.1 -
16 &18) syntax
1.2.840.10008.1.2.4.60 JPEG extended, hierarchical (Pro- Transfer A.4.1 -
cess 17 &19) syntax
1.2.840.10008.1.2.4.61 JPEG spectral selection, hierarchical Transfer A.4.1 -
(Process 20 & 22) syntax
1.2.840.10008.1.2.4.62 JPEG spectral selection, hierarchical Transfer A.4.1 -
(Process 21 & 23) syntax
1.2.840.10008.1.2.4.63 JPEG full progression, hierarchical Transfer A.4.1 -
(Process 24 & 26) syntax

DICOM TD00-000.840.01.03.02 Page 90 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 91

UID Value UID Name UID Type Part 4,5,7 C/N

1.2.840.10008.1.2.4.64 JPEG full progression, hierarchical Transfer A.4.1 -
(Process 25 & 27) syntax
1.2.840.10008.1.2.4.65 JPEG lossless, hierarchical (Process Transfer A.4.1 -
28) syntax
1.2.840.10008.1.2.4.66 JPEG lossless, hierarchical (Process Transfer A.4.1 -
29) syntax
1.2.840.10008.1.2.4.70 JPEG lossless, non-hierarchical, first Transfer A.4.1 -
order prediction (Process 14 (selection syntax
value 1)): JPEG image compression
1.2.840.10008.1.2.5 RLE lossless Transfer A.4.2 -
syntax
1.2.840.10008.1.20.1 Storage commitment push model SOP SOP class J.3.4 N
class
1.2.840.10008.1.20.1.1 Storage commitment push model SOP Well-known J.3.5. -
instance SOP
instance
1.2.840.10008.1.20.2 Storage commitment pull model SOP SOP class J.4.4 N
class
1.2.840.10008.1.20.2.1 Storage commitment pull model SOP Well-known J.4.5 -
instance SOP
instance
1.2.840.10008.1.3.10 Media storage directory storage SOP class I.4 C
1.2.840.10008.1.9 Basic study content notification SOP SOP class D.4.3 C
class
1.2.840.10008.3.1.1.1 DICOM application context name Application A.2.1 -
context
name
1.2.840.10008.3.1.2.1.1 Detached patient management stor- SOP class E.3.4 N
age) SOP Class
1.2.840.10008.3.1.2.1.4 Detached patient management meta SOP class E.5.1 N
SOP class
1.2.840.10008.3.1.2.2.1 Detached visit management (storage) SOP class E.4.4 N
SOP class
1.2.840.10008.3.1.2.3.1 Detached study management (stor- SOP class F.3.4 N
age) SOP class
1.2.840.10008.3.1.2.3.2 Study component management (stor- SOP class F.4.3 N
age) SOP class
1.2.840.10008.3.1.2.3.3 Modality performed procedure step SOP class F.7.3 N
SOP class

Siemens AG TD00-000.840.01.03.02 Page 91 of 106 DICOM

Medical Solutions 06.04 CS SD 21
92 Appendix

UID Value UID Name UID Type Part 4,5,7 C/N

1.2.840.10008.3.1.2.3.4 Modality performed procedure step SOP class F.8.3 N
retrieve SOP class
1.2.840.10008.3.1.2.3.5 Modality performed procedure step SOP class F.9.3 N
notification SOP class
1.2.840.10008.3.1.2.5.1 Detached results management (stor- SOP class G.3.4 N
age) SOP class
1.2.840.10008.3.1.2.5.4 Detached results management meta Meta SOP G.5.1 N
SOP class class
1.2.840.10008.3.1.2.5.5 Detached study management meta Meta SOP F.5.1 N
SOP class class
1.2.840.10008.3.1.2.6.1 Detached interpretation management SOP class G.4.4 N
(storage) SOP class
1.2.840.10008.5.1.1.1 Basic film session (storage) SOP class SOP class H.4.1.3 N
1.2.840.10008.5.1.1.14 Print job SOP class SOP class H.4.5.4 N
1.2.840.10008.5.1.1.15 Basic annotation box SOP class SOP class H.4.4.3 N
1.2.840.10008.5.1.1.16 Printer SOP class SOP class H.4.6.4 N
1.2.840.10008.5.1.1.16.376 Printer configuration retrieval SOP SOP class H.4.11.3 N
class
1.2.840.10008.5.1.1.17 Printer SOP instance Well-known H.4.6.5 -
printer SOP
instance
1.2.840.10008.5.1.1.17.376 Well-known printer configuration Well-known H.4.11.4 -
retrieval SOP instance printer SOP
instance
1.2.840.10008.5.1.1.18 Basic color print management meta Meta SOP H.3.2.2.2 N
SOP class class
1.2.840.10008.5.1.1.2 Basic film box (storage) SOP class SOP class H.4.2.3 N
1.2.840.10008.5.1.1.23 Presentation LUT SOP class SOP class H.4.9.2.4 N
1.2.840.10008.5.1.1.24.1 Basic print image overlay box SOP SOP class H.4.12.3 N
class
1.2.840.10008.5.1.1.25 Print queue SOP instance Well-known L.4.4 -
print queue
SOP
instance
1.2.840.10008.5.1.1.26 Print queue management SOP class SOP class L.4.3 N
1.2.840.10008.5.1.1.27 Stored print storage SOP class SOP class B.5 C

DICOM TD00-000.840.01.03.02 Page 92 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 93

UID Value UID Name UID Type Part 4,5,7 C/N

1.2.840.10008.5.1.1.29 Hardcopy Gray scale image storage SOP class B.5 C
SOP class
1.2.840.10008.5.1.1.30 Hardcopy color image storage SOP SOP class B.5 C
class
1.2.840.10008.5.1.1.31 Pull print SOP class SOP class H.4.10.4 N
1.2.840.10008.5.1.1.32 Pull stored print management meta SOP class H.3.2.2.5 N
SOP class
1.2.840.10008.5.1.1.4 Basic Gray scale image box (storage) SOP class H.4.3.1.3 N
SOP class
1.2.840.10008.5.1.1.4.1 Basic color image box (storage) SOP SOP class H.4.3.23.3 N
class
1.2.840.10008.5.1.1.9 Basic Gray scale print image manage- Meta SOP H.3.2.2.1 N
ment SOP class class
1.2.840.10008.5.1.4.1.1.1 Computed radiography image storage SOP class B.5 C
1.2.840.10008.5.1.4.1.1.1.1 Digital X-ray image storage - for pre- SOP class B.5 C
sentation
1.2.840.10008.5.1.4.1.1.1.1. Digital X-Ray Image Storage - For pro- SOP class B.5 C
1 cessing
1.2.840.10008.5.1.4.1.1.1.2 Digital mammography X-ray image SOP class B.5 C
storage - for presentation
1.2.840.10008.5.1.4.1.1.1.2. Digital mammography X-ray image SOP class B.5 C
1 storage - for processing
1.2.840.10008.5.1.4.1.1.1.3 Digital intra-oral X-ray image storage - SOP class B.5 C
for presentation
1.2.840.10008.5.1.4.1.1.1.3. Digital intra-oral X-ray image storage - SOP class B.5 C
1 for processing
1.2.840.10008.5.1.4.1.1.10 Stand-alone modality LUT storage SOP class B.5 C
1.2.840.10008.5.1.4.1.1.11 Stand-alone VOI LUT storage SOP class B.5 C
1.2.840.10008.5.1.4.1.1.11. Gray scale softcopy presentation state SOP class B.5 C
1 storage
1.2.840.10008.5.1.4.1.1.12. X-ray angiography image storage SOP class B.5 C
1
1.2.840.10008.5.1.4.1.1.12. X-ray radiofluoroscopic image storage SOP class B.5 C
2
1.2.840.10008.5.1.4.1.1.12. X-ray angiographic biplane image SOP class B.5 C
3 storage

Siemens AG TD00-000.840.01.03.02 Page 93 of 106 DICOM

Medical Solutions 06.04 CS SD 21
94 Appendix

UID Value UID Name UID Type Part 4,5,7 C/N

1.2.840.10008.5.1.4.1.1.128 Positron emission tomography image SOP class B.5 C
storage
1.2.840.10008.5.1.4.1.1.129 Stand-alone PET curve storage SOP class B.5 C
1.2.840.10008.5.1.4.1.1.2 CT image storage SOP class B.5 C
1.2.840.10008.5.1.4.1.1.20 Nuclear medicine image storage SOP class B.5 C
1.2.840.10008.5.1.4.1.1.3 Ultrasound multi-frame image storage SOP class B.5 C
(retired)
1.2.840.10008.5.1.4.1.1.3.1 Ultrasound multi-frame image storage SOP class B.5 C
1.2.840.10008.5.1.4.1.1.4 MR image storage SOP class B.5 C
1.2.840.10008.5.1.4.1.1.481 RT image storage SOP class B.5 C
.1
1.2.840.10008.5.1.4.1.1.481 RT dose storage SOP class B.5 C
.2
1.2.840.10008.5.1.4.1.1.481 RT structure set storage SOP class B.5 C
.3
1.2.840.10008.5.1.4.1.1.481 RT bones treatment record storage SOP class B.5 C
.4
1.2.840.10008.5.1.4.1.1.481 RT plan storage SOP class B.5 C
.5
1.2.840.10008.5.1.4.1.1.481 RT brachy treatment record storage SOP class B.5 C
.6
1.2.840.10008.5.1.4.1.1.481 RT treatment summary record storage SOP class B.5 C
.7
1.2.840.10008.5.1.4.1.1.5 Nuclear medicine image storage SOP class B.5 C
(retired)
1.2.840.10008.5.1.4.1.1.6 Ultrasound image storage (retired) SOP class B.5 C
1.2.840.10008.5.1.4.1.1.6.1 Ultrasound image storage SOP class B.5 C
1.2.840.10008.5.1.4.1.1.7 Secondary capture image storage SOP class B.5 C
1.2.840.10008.5.1.4.1.1.77. Visible light endoscopic image storage SOP class B.5 C
1.1
1.2.840.10008.5.1.4.1.1.77. Visible light microscopic image stor- SOP class B.5 C
1.2 age
1.2.840.10008.5.1.4.1.1.77. Visible light slide coordinates micro- SOP class B.5 C
1.3 scopic image storage
1.2.840.10008.5.1.4.1.1.77. Visible light photographic image stor- SOP class B.5 C
1.4 age

DICOM TD00-000.840.01.03.02 Page 94 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 95

UID Value UID Name UID Type Part 4,5,7 C/N

1.2.840.10008.5.1.4.1.1.8 Stand-alone overlay storage SOP class B.5 C
1.2.840.10008.5.1.4.1.1.88. Structured report basic text SOP class SOP class B.5 C
11
1.2.840.10008.5.1.4.1.1.88. Structured report enhanced SOP class SOP class B.5 C
22
1.2.840.10008.5.1.4.1.1.88. Structured report comprehensive SOP SOP class B.5 C
33 class
1.2.840.10008.5.1.4.1.1.9 Stand-alone curve storage SOP class B.5 C
1.2.840.10008.5.1.4.1.1.9.1. 12-lead ECG waveform storage SOP SOP class B.5 C
1 class
1.2.840.10008.5.1.4.1.1.9.1. General ECG waveform storage SOP SOP class B.5 C
2 class
1.2.840.10008.5.1.4.1.1.9.1. Ambulatory ECG waveform storage SOP class B.5 C
3 SOP class
1.2.840.10008.5.1.4.1.1.9.2. Hemodynamic waveform storage SOP SOP class B.5 C
1 class
1.2.840.10008.5.1.4.1.1.9.3. Cardiac electrophysiology waveform SOP class B.5 C
1 storage SOP class
1.2.840.10008.5.1.4.1.1.9.4. Basic voice audio waveform storage SOP class B.5 C
1 SOP class
1.2.840.10008.5.1.4.1.2.1.1 Patient root query/retrieve information SOP class C.6.1.3 C
model - FIND
1.2.840.10008.5.1.4.1.2.1.2 Patient root query/retrieve information SOP class C.6.1.3 C
model - MOVE
1.2.840.10008.5.1.4.1.2.1.3 Patient root query/retrieve information SOP class C.6.1.3 C
model - GET
1.2.840.10008.5.1.4.1.2.2.1 Study root Query/Retrieve Information SOP class C.6.2.3 C
model - FIND
1.2.840.10008.5.1.4.1.2.2.2 Study root query/retrieve information SOP class C.6.2.3 C
model - MOVE
1.2.840.10008.5.1.4.1.2.2.3 Study root query/retrieve information SOP class C.6.2.3 C
model - GET
1.2.840.10008.5.1.4.1.2.3.1 Patient/ study only query/retrieve SOP class C.6.3.3 C
Information model - FIND
1.2.840.10008.5.1.4.1.2.3.2 Patient/ study only query/retrieve infor- SOP class C.6.3.3 C
mation model - MOVE

Siemens AG TD00-000.840.01.03.02 Page 95 of 106 DICOM

Medical Solutions 06.04 CS SD 21
96 Appendix

UID Value UID Name UID Type Part 4,5,7 C/N

1.2.840.10008.5.1.4.1.2.3.3 Patient/ study only query/retrieve infor- SOP class C.6.3.3 C
mation model - GET
1.2.840.10008.5.1.4.31 Modality worklist information model - SOP class K.6.1.4 C
FIND

DICOM TD00-000.840.01.03.02 Page 96 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 97

Status Messages in merge.log File 0

Status Service Definition Hex Decimal

Type
Success all Success 0000 0
Failure all No such attribute 0105 261
Failure all Invalid attribute value 0106 262
Warning all Attribute list error 0107 263
Failure all Processing Error 0110 272
Failure all Duplicate SOP instance 0111 273
Failure all No such object instance 0112 274
Failure all No such event type 0113 275
Failure all No such argument 0114 276
Failure all Invalid argument value 0115 277
Warning all Attribute value out of range 0116 278
Failure all Invalid object instance 0117 279
Failure all No such SOP class 0118 280
Failure all Class instance conflict 0119 281
Failure all Missing attribute 0120 288
Failure all Missing attribute value 0121 289
Refused all SOP class not supported 0122 290
Failure all Duplicate invocation 0210 528
Failure all Unrecognized operation 0211 529
Failure all Mistyped argument 0212 530
Failure all Resource limitation 0213 531
Refused FIND Out of resources A700 42752
Refused MOVE-GET Out of resources: number of matches A701 42753
Refused MOVE-GET Out of resources: no sub-operations A702 42754
Refused STORE Out of resources A7xx 42752-43007
Refused MOVE Move destination unknown A801 43009
Failure FIND-MOVE- Identifier does not match SOP class A900 43264
GET
Failure STORE Data set does not match SOP class A9xx 43264-43519

Siemens AG TD00-000.840.01.03.02 Page 97 of 106 DICOM

Medical Solutions 06.04 CS SD 21
98 Appendix

Status Service Definition Hex Decimal

Type
Warning MOVE-GET Sub-operations complete: one or more fail- B000 45056
ures
Warning STORE Coercion of data elements B000 45056
Warning STORE Elements discarded B006 45062
Warning STORE Data set does not match SOP class B007 45063
Warning PRINT Memory allocation not supported B600 46592
Warning PRINT Film session printing (collation) is not sup- B601 46593
ported
Warning PRINT Film session SOP instance hierarchy does B602 46594
not contain image box SOP instances
(empty page)
Warning PRINT Film box SOP instance hierarchy does not B603 46595
contain image box SOP instances (empty
page)
Warning PRINT Image size is larger than image box size, B604 46596
the image has been demagnified
Warning PRINT Req. min or max density out of range. B605 46597
Printer will use its own values.
Warning PRINT Image size is larger than the image box B609 46601
size. The image has been cropped to fit.
Warning PRINT Image size or combined print image size is B60A 46602
larger than the image box size. Image or
combined print image has been cropped to
fit.
Failure PRINT Film session SOP instance hierarchy does C600 50688
not contain film box SOP instances.
Failure PRINT Unable to create print job SOP instance; C601 50689
print queue is full (film session)
Failure PRINT Unable to create print job SOP instance, C602 50690
print queue is full (film box)
Failure PRINT Image size is larger than image box size C603 50691
Failure PRINT Insufficient memory printer to store the C605 50693
image
Failure PRINT More than one VOI LUT box contained in C606 50694
image
Failure PRINT Combined print image size is larger than C613 50707
the image box size

DICOM TD00-000.840.01.03.02 Page 98 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 99

Status Service Definition Hex Decimal

Type
Failure PRINT There is an existing film box that has not C616 50710
been printed and N-action at the film ses-
sion level is not supported. A new film box
will not be created when a previous film box
has not been printed.
Failure FIND_MOVE- Unable to process Cxxx 49152-53247
GET
Failure STORE Cannot understand Cxxx 49152-53247
Cancel all Cancel FE00 65024
Pending FIND Matching continuing FF00 65280
Pending FIND-MOVE Matching continuing: Warning FF01 65281

Siemens AG TD00-000.840.01.03.02 Page 99 of 106 DICOM

Medical Solutions 06.04 CS SD 21
100 Appendix

DICOM Attributes in the Command Set (T7 in the merge.log File) 0

Message Field Tag VR VM Description of Field

Affected SOP class UID (0000,0002) UI 1 The affected SOP class UID
Requested SOP class UID (0000,0003) UI 1 The requested SOP class UID
command
Command field (0000,0100) US 1 Requested/responded command
Message ID (0000,0110) US 1 Implementation-specific value
Message ID responded to (0000,0120) US 1 Should be same as (0000,0110)
Move destination (0000,0600) AE 1 DICOM AE title of the destination
Priority (0000,0700) US 1 LOW = 0002H
MEDIUM = 000H
HIGH = 0001H
Data set type (0000,0800) US 1 no data set = 0101H
data set = any other
Status (0000,0900) US 1 OK = 0
Offending element (0000,0910) AT 1-n If status is Cxxx, list of the ele-
ments in which the error was
detected
Error comment (0000,0902) LO 1 Application-specific text
Error ID (0000,0903) US 1 Application-specific error code
Affected SOP instance ID (0000,1000) UI 1 SOP instance for this operation
Request SOP instance UID (0000,1001) UI 1 SOP instance for this operation
Event type ID (0000,1002) US 1 Application-specific
Attribute identifier list (0000,1005) AT 1-n Attribute tag for attribute applica-
ble
Action Type ID (0000,1008) US 1 Application-specific
Number of remaining (0000,1020) US 1 C-STORE sub-operations to be
Sub-operations invoked for the operation
Number of completed (0000,1021) US 1 C-STORE sub-operations which
sub-operations have completed successfully
Number of failed sub-oper- (0000,1022) US 1 The number of the C-STORE
ations sub-operations which have failed
Number of warning (0000,1023) US 1 The number of C-STORE
sub-operations sub-operations which generated
warning responses

DICOM TD00-000.840.01.03.02 Page 100 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Appendix 101

Message Field Tag VR VM Description of Field

Move originator application (0000,1030) AE 1 AE title which invoked C-MOVE,
entity title from which C-Store is being per-
formed
Move originator message (0000,1031) US 1 Message ID (0000,0110) of the
ID C-MOVE-RQ message from
which C-STORE is being per-
formed

Command Field Values (0000,0100)

Request Response Response

Meaning Request decimal
HEX decimal HEX
C-SEND 1 0001 32769 8001
C-GET 16 0010 32784 8010
C-FIND 32 0020 32800 8020
C-MOVE 33 0021 32801 8021
C-ECHO 48 0030 32816 8030
N-EVENT-REPORT 256 0100 33024 8100
N-GET 272 0110 33040 8110
N-SET 288 0120 33056 8120
N-ACTION 304 0130 33072 8130
N-CREATE 320 0140 33088 8140
N-DELETE 336 0150 33104 8150
C-CANCEL 4095 OFF

Siemens AG TD00-000.840.01.03.02 Page 101 of 106 DICOM

Medical Solutions 06.04 CS SD 21
102 Appendix

Dicom e-learning 0

Start the e-learning here:

DICOM TD00-000.840.01.03.02 Page 102 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Changes to Previous Version 103
13-
12Changes to Previous Version

Document completely rewritten.

Siemens AG TD00-000.840.01.03.02 Page 103 of 106 DICOM

Medical Solutions 06.04 CS SD 21
104 Index
14-
A
13Index

ARP (example) . . . . . . . . . . . . . . . . . . 51
ARP -A . . . . . . . . . . . . . . . . . . . . . . . . 44

B Basic Print . . . . . . . . . . . . . . . . . . . . . . 31

C Color images are not displayed correctly30

C_Echo fails . . . . . . . . . . . . . . . . . . . . 13

D DICOM Attributes in the Command Set100

DICOM Basic print Timeout Problems 32
DICOM Media Storage Troubleshooting43
DICOM Modality Performed Procedure Step 42
DICOM Storage Problem with Transferred Image17
DICOM Storage Troubleshooting . . . . 16
DICOM Test Tools - Storage send images52
DICOM Test Tools - Storage Simulate Local Receiver53
DICOM Test Tools - Storage Simulate Remote Receiver54
DICOM Test Tools - Verify network . . 52
DICOM UIDs . . . . . . . . . . . . . . . . . . . . 90
DICOM Verification fails . . . . . . . . . . . 13
DICOM Worklist Troubleshooting . . . . 39

I Image Presentation and Manipulation at the Local / Remote System is not Correct26
Image Quality Problems on DICOM Basioc Print33
Image Text does not display correct characters26
Image transfer to Camera . . . . . . . . . . 31
Image Transfer to Local System Fails. 20
Image Transfer to Remote System Fails16
Information System cannot Handle Worklist request41
IPCONFIG. . . . . . . . . . . . . . . . . . . . . . 44

M Merge Error Messages . . . . . . . . . . . . 55

merge.log (Status Messages) . . . . . . . 97
Merge_hc.log . . . . . . . . . . . . . . . . . . . 68
Merge_stu.log . . . . . . . . . . . . . . . . . . . 59
metric values . . . . . . . . . . . . . . . . . . . . 29
Missing Information in Worklist Response40
Multiframe images are not displayed correctly 30

N netstat . . . . . . . . . . . . . . . . . . . . . . 44, 47
netstat -rn . . . . . . . . . . . . . . . . . . . . . . 49
netstat -s . . . . . . . . . . . . . . . . . . . . . . . 49
Network Test Examples . . . . . . . . . . . 49
No Worklist in Scheduler Database . . 39
nslookup . . . . . . . . . . . . . . . . . . . . . . . 44

O Overlay missing. . . . . . . . . . . . . . . . . . 28

DICOM TD00-000.840.01.03.02 Page 104 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions
Index 105

P Patient Browser not correct . . . . . . . . .24

Ping . . . . . . . . . . . . . . . . . . . . . . . .44, 45
ping -l ; -n . . . . . . . . . . . . . . . . . . . . . . .49
Ping Fails . . . . . . . . . . . . . . . . . . . . . . .10
ping parameters . . . . . . . . . . . . . . . . . .46
Problem during the Association Negotiation (T3 level)31
Problem with Received Worklist Message39
Problem with the Association Negotiation (T3 level)20
Problem with Transfered Image . . . . . .21
Problem with Transferred Images Caused by Remote System19

Q Query / Retrieve . . . . . . . . . . . . . . . . . .35

R Remote System cannot Handle Query Request37

Retrieve of Selected Data Fails . . . . . .38

S Shutter is missing . . . . . . . . . . . . . . . . .29

Storage Commitment . . . . . . . . . . . . . .34
Study Browser not correct . . . . . . . . . .24

T TCP/IP Ping Fails . . . . . . . . . . . . . . . . .10

telnet. . . . . . . . . . . . . . . . . . . . . . . .44, 48
Text in Patient Browser is not ok . . . . .24
Timeout Problems at DICOM Worklist .40
Timeout Problems at Query/Retrieve . .37
Timeout Problems during Transfer to Local System22
Timeout Problems with DICOM Basic Print32
Timeout Problems with Transferred Images18
tracert . . . . . . . . . . . . . . . . . . . . . . . . . .44
Transfer to Camera . . . . . . . . . . . . . . .31
Transfer too Slow . . . . . . . . . . . . . . . . .12

V Verify network. . . . . . . . . . . . . . . . . . . .52

W Windowing is not correct . . . . . . . . . . .26

Worklist. . . . . . . . . . . . . . . . . . . . . . . . .39

Z Zoomed image is displayed in the original size30

Siemens AG TD00-000.840.01.03.02 Page 105 of 106 DICOM

Medical Solutions 06.04 CS SD 21
106 Index

DICOM TD00-000.840.01.03.02 Page 106 of 106 Siemens AG

06.04 CS SD 21 Medical Solutions