DICOM Conformance Statement D-No.

: 1070525
DBSWIN Rev: C

DUERR DENTAL SE

DICOM Conformance Statement

DBSWIN

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 1 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

Conformance Statement Overview

DBSWIN implements the necessary DICOM services to download worklist items from an information
system, acquire images using DUERR DENTAL imaging equipment, transfer them to storage servers or
export them as DICOM files or media.

The following table provides an overview of the services provided by DBSWIN:

SOP Classes User of Service Provider of Service

(SCU) (SCP)
Transfer
Digital X-Ray Image Storage – For Presentation Yes1 No
Digital Intra-oral X-Ray Image Storage – Yes1 No
For Presentation
Secondary Capture Image Storage Yes1 No
Workflow Management
Modality Worklist Information Model – FIND Yes1 No
1
Modality Performed Procedure Step SOP Class Yes No
Storage Commitment Push Model SOP Class Yes1 No
Print Management
Basic Grayscale Print Management Meta SOP Class Yes2 No

1
Available with the DICOM Starter license option of the DICOM Interface
2
Available with the DICOM Print license option of the DICOM Interface.

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 2 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

Table of Contents

1 Introduction ....................................................................................................................5

1.1 Revision History ............................................................................................................... 5

1.2 Audience ......................................................................................................................... 5

1.3 Remarks .......................................................................................................................... 5

1.4 Terms and Definitions ...................................................................................................... 5

1.5 Basics of DICOM Communication ..................................................................................... 7

1.6 Terms and Definitions ...................................................................................................... 8

1.7 References ...................................................................................................................... 9

2 Networking ................................................................................................................... 10

2.1 Implementation Model .................................................................................................. 10

2.1.1 Application Data Flow .................................................................................................... 10
2.1.2 Functional Definition ..................................................................................................... 11

2.2 DICOM AE Networking Specification .............................................................................. 12

2.2.1 SOP Classes ................................................................................................................... 12
2.2.2 Association Policies........................................................................................................ 12
2.2.3 Association Initiation Policy ........................................................................................... 13
2.2.4 Association Acceptance Policy........................................................................................ 22

2.3 Network Interfaces ........................................................................................................ 23

2.3.1 Physical Network Interface ............................................................................................ 23
2.3.2 Additional Protocols ...................................................................................................... 23
2.3.3 IPv4 and IPv6 Support .................................................................................................... 23

2.4 Configuration ................................................................................................................ 23

2.4.1 AE Title/Presentation Address Mapping ......................................................................... 23
2.4.2 Parameters.................................................................................................................... 23

3 Media Interchange ........................................................................................................ 24

3.1.1 Implementation Model .................................................................................................. 24
3.1.2 Application Data Flow .................................................................................................... 24
3.1.3 Functional Definition ..................................................................................................... 24
3.1.4 File Meta Information Options ....................................................................................... 24

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 3 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

3.1.5 Activity – Export to File System ...................................................................................... 24

3.1.6 Activity – Import from File System ................................................................................. 25

4 Support of Character Sets ............................................................................................. 26

5 Security......................................................................................................................... 27

6 Annexes ........................................................................................................................ 28

6.1 Standard Extended/Specialized/Private SOP Classes ....................................................... 28

6.2 Private Transfer Syntaxes............................................................................................... 28

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 4 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

1 Introduction

1.1 Revision History

Revision Date of Issue Description
- 07.04.2008 Released version for DBSWIN 4.5 or higher
A 10.06.2010 Released version for DBSWIN 5.0.2 or higher
B 14.03.2022 No functional changes, valid for DBSWIN 5.0.2 or higher

1.2 Audience
This document is written for people that need to understand how DBSWIN will integrate into their
healthcare facility. This includes both those responsible for overall imaging network policy and
architecture, as well as integrators who need to have a detailed understanding of the DICOM
features of the product. This document contains some basic DICOM definitions so that any reader
may understand how this product implements DICOM features. However, integrators are expected
to fully understand all the DICOM terminology, how the tables in this document relate to the
product's functionality, and how that functionality integrates with other devices that support
compatible DICOM features.

1.3 Remarks
The scope of this DICOM Conformance Statement is to facilitate integration between DBSWIN and
other DICOM products. The Conformance Statement should be read and understood in conjunction
with the DICOM Standard. DICOM by itself does not guarantee interoperability. The Conformance
Statement does, however, facilitate a first-level comparison for interoperability between different
applications supporting compatible DICOM functionality.
This Conformance Statement is not supposed to replace validation with other DICOM equipment to
ensure proper exchange of intended information. In fact, the user should be aware of the following
important issues:
• The comparison of different Conformance Statements is just the first step towards assessing
interconnectivity and interoperability between the product and other DICOM conformant
equipment.
• Test procedures should be defined and executed to validate the required level of interoperability
with specific compatible DICOM equipment, as established by the healthcare facility.

1.4 Terms and Definitions

Informal definitions are provided for the following terms used in this Conformance Statement. The
DICOM Standard is the authoritative source for formal definitions of these terms.
Abstract Syntax The information agreed to be exchanged between applications,
generally equivalent to a Service/Object Pair (SOP) Class. Examples:
Verification SOP Class, Modality Worklist Information Model Find SOP

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 5 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

Class, Computed Radiography Image Storage SOP Class.

Application Entity (AE) An end point of a DICOM information exchange, including the DICOM
network or media interface software; i.e., the software that sends or
receives DICOM information objects or messages. A single device may
have multiple Application Entities.
Application Entity Title The externally known name of an Application Entity, used to identify a
(AET) DICOM application to other DICOM applications on the network.
Application Context The specification of the type of communication used between
Application Entities. Example: DICOM network protocol.
Association A network communication channel set up between Application
Entities.
Attribute A unit of information in an object definition; a data element identified
by a tag. The information may be a complex data structure
(Sequence), itself composed of lower level data elements. Examples:
Patient ID (0010,0020), Accession Number (0008,0050), Photometric
Interpretation (0028,0004), Procedure Code Sequence (0008,1032).
Information Object The specified set of Attributes that comprise a type of data object;
Definition (IOD) does not represent a specific instance of the data object, but rather a
class of similar data objects that have the same properties. The
Attributes may be specified as Mandatory (Type 1), Required but
possibly unknown (Type 2), or Optional (Type 3), and there may be
conditions associated with the use of an Attribute (Types 1C and 2C).
Examples: MR Image IOD, CT Image IOD, Print Job IOD.
Joint Photographic Experts A set of standardized image compression techniques, available for use
Group (JPEG) by DICOM applications.
Media Application Profile The specification of DICOM information objects and encoding
exchanged on removable media (e.g., CDs).
Module A set of Attributes within an Information Object Definition that are
logically related to each other. Example: Patient Module includes
Patient Name, Patient ID, Patient Birth Date, and Patient Sex.
Negotiation First phase of Association establishment that allows Application
Entities to agree on the types of data to be exchanged and how that
data will be encoded.
Presentation Context The set of DICOM network services used over an Association, as
negotiated between Application Entities; includes Abstract Syntaxes
and Transfer Syntaxes.
Protocol Data Unit (PDU) A packet (piece) of a DICOM message sent across the network. Devices
must specify the maximum size packet they can receive for DICOM
messages.
Security Profile A set of mechanisms, such as encryption, user authentication, or
digital signatures, used by an Application Entity to ensure
confidentiality, integrity, and/or availability of exchanged DICOM data.
Service Class Provider Role of an Application Entity that provides a DICOM network service;
(SCP) typically, a server that performs operations requested by another
Application Entity (Service Class User). Examples: Picture Archiving and

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 6 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

Communication System (image storage SCP, and image query/retrieve

SCP), Radiology Information System (modality worklist SCP).
Service Class User (SCU) Role of an Application Entity that uses a DICOM network service;
typically, a client. Examples: imaging modality (image storage SCU, and
modality worklist SCU), imaging workstation (image query/retrieve
SCU).
Service/Object Pair Class The specification of the network or media transfer (service) of a
(SOP Class) particular type of data (object); the fundamental unit of DICOM
interoperability specification. Examples: Ultrasound Image Storage
Service, Basic Grayscale Print Management.
Service/Object Pair An information object; a specific occurrence of information exchanged
Instance (SOP Instance) in a SOP Class. Examples: a specific x-ray image.
Tag A 32-bit identifier for a data element, represented as a pair of four
digit hexadecimal numbers, the "group" and the "element". If the
"group" number is odd, the tag is for a private (manufacturer-specific)
data element. Examples: (0010,0020) [Patient ID], (07FE,0010) [Pixel
Data], (0019,0210) [private data element].
Transfer Syntax The encoding used for exchange of DICOM information objects and
messages. Examples: JPEG compressed (images), little endian explicit
value representation.
Unique Identifier (UID) A globally unique "dotted decimal" string that identifies a specific
object or a class of objects; an ISO-8824 Object Identifier. Examples:
Study Instance UID, SOP Class UID, SOP Instance UID.
Value Representation (VR) The format type of an individual DICOM data element, such as text, an
integer, a person's name, or a code. DICOM information objects can be
transmitted with either explicit identification of the type of each data
element (Explicit VR), or without explicit identification (Implicit VR);
with Implicit VR, the receiving application must use a DICOM data
dictionary to look up the format of each data element.

1.5 Basics of DICOM Communication

This section describes terminology used in this Conformance Statement for the non-specialist. The
key terms used in the Conformance Statement are highlighted in italics below. This section is not a
substitute for training about DICOM, and it makes many simplifications about the meanings of
DICOM terms.
Two Application Entities (devices) that want to communicate with each other over a network using
DICOM protocol must first agree on several things during an initial network "handshake". One of the
two devices must initiate an Association (a connection to the other device), and ask if specific
services, information, and encoding can be supported by the other device (Negotiation).
DICOM specifies a number of network services and types of information objects, each of which is
called an Abstract Syntax for the Negotiation. DICOM also specifies a variety of methods for encoding
data, denoted Transfer Syntaxes. The Negotiation allows the initiating Application Entity to propose
combinations of Abstract Syntax and Transfer Syntax to be used on the Association; these
combinations are called Presentation Contexts. The receiving Application Entity accepts the
Presentation Contexts it supports.

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 7 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

For each Presentation Context, the Association Negotiation also allows the devices to agree on Roles
- which one is the Service Class User (SCU - client) and which is the Service Class Provider (SCP -
server). Normally the device initiating the connection is the SCU, i.e., the client system calls the
server, but not always.
The Association Negotiation finally enables exchange of maximum network packet (PDU) size,
security information, and network service options (called Extended Negotiation information).
The Application Entities, having negotiated the Association parameters, may now commence
exchanging data. Common data exchanges include queries for worklists and lists of stored images,
transfer of image objects and analyses (structured reports), and sending images to film printers. Each
exchangeable unit of data is formatted by the sender in accordance with the appropriate Information
Object Definition, and sent using the negotiated Transfer Syntax. There is a Default Transfer Syntax
that all systems must accept, but it may not be the most efficient for some use cases. Each transfer is
explicitly acknowledged by the receiver with a Response Status indicating success, failure, or that
query or retrieve operations are still in process.
Two Application Entities may also communicate with each other by exchanging media (such as a CD-
R). Since there is no Association Negotiation possible, they both use a Media Application Profile that
specifies "pre-negotiated" exchange media format, Abstract Syntax, and Transfer Syntax.

1.6 Terms and Definitions

Abbreviations used in this document are:

ACR American College of Radiology

AE DICOM Application Entity
C-STORE DICOM service for storing of objects (e.g. images)
C-ECHO DICOM service to verify that a peer application is up and running
CD-R Compact Disk Recordable
DICOM Digital Imaging and Communication in Medicine
DX Digital X-Ray Information Object
FSC File Set Creator
FSU File Set Updater
HIS Hospital Information System
IO Digital Intra-oral X-Ray Information Object
IOD DICOM Information Object Definition
IS Information System (HIS, RIS, PACS within hospital)
Modality Worklist Service class to inform the modality about new examinations
MPPS Modality Performed Procedure Step,
NEMA National Electrical Manufacturers Association
PACS Picture Archiving and Communication System
PPS Performed Procedure Step
RIS Radiology Information System
SC Secondary Capture Information Object

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 8 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

SCP Service Class Provider

SCU Service Class User
SPS Scheduled Procedure Step
SOP DICOM Service-Object Pair
UID Unique Identifier, string unique throughout the entire network

1.7 References
[1] DICOM PS3 - Digital Imaging and Communications in Medicine https://www.dicomstandard.org/

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 9 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

2 Networking

2.1 Implementation Model

2.1.1 Application Data Flow

Verify Remote AE
Communication Receives
Partner C-ECHO

Remote AE
Send Images Receives
Images

DBSWIN

Remote AE
DICOM AE
Update Worklist Provides
Worklist Items

Remote AE
Create/Update Receives MPPS
MPPS Create/Update

Remote AE
Prints Film Sheets
Film Images

DICOM Standard Interface

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 10 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

2.1.2 Functional Definition

The following activities are triggered by DBSWIN user interactions:

• Verify Communication Partner
• Send Images
• Update Worklist
• Create/Update MPPS
• Film Images

The DICOM AE sends an association request to the destination AE, negotiates a Presentation Context
and closes the association after the transfer of images, MPPSes or commands.
All activities are performed in a synchronous manner and an error dialog is displayed to the user if a
DICOM service could not be successfully completed. No automatic retry mechanism is implemented.
DBSWIN users can configure DICOM communication partners and verify whether they are able to
respond to C-ECHO messages. Conversely, the DICOM AE can be configured to act as a Verification
SCP and respond to C-ECHO requests from the Remote AE.
To send images to a remote Storage SCP, the user selects one or more images which are transferred
to the remote AE. The user is informed about the progress of the transfer. DBSWIN can be configured
to send images automatically to one or more Storage SCPs upon completion of the current image
acquisition operation. If the Storage SCP is configured to act as a Storage Commitment SCP, then
each store operation is followed by a Storage Commitment request.
DBSWIN can download Modality Worklists from a remote Modality Worklist SCP either interactively
on user request, or automatically in regular time intervals or whenever the user enters the Worklist
page of the DBSWIN user interface. In addition, the user can perform ad-hoc queries to find and
download Modality Scheduled Procedure Steps that have been scheduled for a specific patient,
station or physician.
When the user starts one of the worklist steps, and the worklist SCP is configured to act as a MPPS
SCP, then a corresponding MPPS is created on the worklist SCP with status IN PROGRESS.
Subsequently acquired images are assigned to this MPPS until a different MPPS is selected by the
user, or the user has marked the MPPS as completed or aborted. In the latter case, a command is
sent to the MPPS SCP which sets the status to COMPLETED or DISCONTINUED, respectively.
To print a film sheet, the user selects one or more images to be sent to a DICOM printer and,
optionally, defines the annotations to be added. When finished, the DICOM AE initiates an
association, starts the transfer of the annotated image and informs the user about the progress.

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 11 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

2.2 DICOM AE Networking Specification

2.2.1 SOP Classes

The DICOM Interface Application Entity provides standard conformance to the following SOP Classes
as an SCU:

SOP Class Name SOP Class UID

Verification 1.2.840.10008.1.1
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7
Digital X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.1
Digital Intra-oral X-Ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.3
Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31
Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3
Basic Directory Storage 1.2.840.10008.1.3.10
Storage Commitment Push Model SOP Class 1.2.840.10008.1.20.1
Basic Grayscale Print Management Meta 1.2.840.10008.5.1.1.9
Basic Film Session 1.2.840.10008.5.1.1.1
Basic Film Box 1.2.840.10008.5.1.1.2
Basic Grayscale Image Box 1.2.840.10008.5.1.1.4
Printer 1.2.840.10008.5.1.1.16

2.2.2 Association Policies

2.2.2.1 General

The DICOM standard application context name for DICOM 3.0 is always proposed:
1.2.840.10008.3.1.1.1

2.2.2.2 Number of Associations

The DICOM Interface initiates one association at a time. The maximum number of simultaneous
associations that will be accepted by the DICOM Interface can be configured to be any number
between 1 (default) and 256. Association acceptance can be fully disabled via configuration UI.

Max. number of simultaneous associations initated 1

Max. number of simultaneous associations accepted 1 – 256 (configurable)

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 12 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

It is not possible to run multiple instances of the DICOM Interface on one computer at the same time.

2.2.2.3 Asynchronous Nature

The DICOM Interface does not support asynchronous communication (multiple outstanding
transactions over a single association).

2.2.2.4 Implementation Identifying Information

The implementation information for the DICOM Interface Application Entity is:

Implementation Class UID 1.2.276.0.82.1.1

Implementation Version Name DD_DICOM_20

2.2.3 Association Initiation Policy

2.2.3.1 Activity – Verify Communication Partner

2.2.3.1.1 Description and Sequencing of Activities

When a Remote AE is being configured, the DBSWIN user can check whether an association can be
established between the DICOM Interface and the Remote AE using the specified AE Title, IP address
and TCP/IP port number.
The DICOM Interface opens an association to the remote AE and sends a verification message (C-
ECHO request) to check whether the remote application entity can be reached and is able to respond
to DICOM messages (C-ECHO response).

2.2.3.1.2 Proposed Presentation Contexts

The DICOM Interface is capable of proposing the Presentation Contexts shown in the following table:
Presentation Context Table
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name List UID List Neg.

Verification 1.2.840.10008.1. Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None

Service Class 1 Implicit VR Little Endian 1.2.840.10008.1.2
Explicit VR Big Endian 1.2.840.10008.1.2.2

2.2.3.2 Activity - Send Images

2.2.3.2.1 Description and Sequencing of Activities

The DBSWIN user selects images and requests them to be sent to a remote AE. The images are
forwarded to the DICOM Interface together with related patient and acquisition data. Worklist data
is added to the images if they have been acquired in response to a Scheduled Procedure Step.
X-Ray Images are converted to DICOM SC, DX or IO images depending on the acquisition modality
and the configuration of the DICOM Interface. If the Remote AE does not support DX or IO Image
Storage, the images will be transferred as SC Images. Video captures are always transferred as SC

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 13 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

Images.
DBSWIN can be configured to send images automatically to one or more Remote AEs after the
images have been saved in the X-Ray or Video module of the DBSWIN software (“Auto-Export”).
For every image to be sent, the DICOM Interface initiates a new association, issues a C-STORE
request and releases the association. If the Remote AE is configured as an archive device, the DICOM
Interface opens a new association, sends a Storage Commitment Request for the current image via
N-ACTION command and waits for a configurable amount of time for a corresponding N-EVENT-
REPORT from the Remote AE to notify the result of the Storage Commitment operation. If no such N-
EVENT-REPORT is received within this time period, the association will be released and N-EVENT-
REPORT requests will be accepted by the DICOM Interface on new associations initiated by the
Remote AE.

DICOM AE Image
Manager

Open Association

C-STORE (IO Image)

Close Association

Open Association

N-ACTION (Storage Commitment Request)

N-EVENT-REPORT (Storage Commitment Response)

Close Association

Open Association

C-STORE (SC Image)

Once the DICOM Interface received a Storage Commitment Result with status SUCCESS for a
particular image, a DBSWIN user can delete the pixel data of that image on the local machine. When
needed, the DICOM Interface will automatically retrieve the image pixel data from the Remote AE by
acting as a Storage SCP and initiating a C-MOVE to transfer the image from the Remote AE back to
the DICOM Interface. Any number of Storage SCPs can be configured as archive devices, i.e. AEs
acting as Storage Commitment SCPs.
In order to support full WYSIWYG functionality independent of third-party DICOM viewer capabilities,
overlay graphics and image transformations will be “burned” into the image pixel data unless export

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 14 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

mode “Original” is used. In “Original” mode, the linear windowing data (window center and width)
and photometric interpretation are exported separately using the respective DICOM attributes.

2.2.3.2.2 Proposed Presentation Contexts

The DICOM Interface is capable of proposing the Presentation Contexts shown in the following table:
Presentation Context Table
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name List UID List Neg.

Secondary 1.2.840.10008.5.1. Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None

Capture 4.1.1.7 Implicit VR Little Endian 1.2.840.10008.1.2
Image Explicit VR Big Endian 1.2.840.10008.1.2.2
Storage
Digital X-Ray 1.2.840.10008.5.1. Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
Image 4.1.1.1.1 Implicit VR Little Endian 1.2.840.10008.1.2
Storage - For Explicit VR Big Endian 1.2.840.10008.1.2.2
Presentation
Digital Intra- 1.2.840.10008.5.1. Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
oral X-Ray 4.1.1.1.3 Implicit VR Little Endian 1.2.840.10008.1.2
Image Explicit VR Big Endian 1.2.840.10008.1.2.2
Storage – For
Presentation
Storage 1.2.840.10008.1.2 Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
Commitment 0.1 Implicit VR Little Endian 1.2.840.10008.1.2
Push Model Explicit VR Big Endian 1.2.840.10008.1.2.2

2.2.3.3 Activity - Update Worklist

2.2.3.3.1 Description and Sequencing of Activities

The modality worklist service class defines an application-level class of service which facilitates the
transfer of worklists from an information system to the imaging modality. The DICOM Interface
supports the worklist service in the role of a SCU.
The DICOM Interface supports two types of worklist update operations: interactive ad-hoc queries
initiated by the user (“Worklist Query”), and non-interactive updates of the local worklist in the
background (“Worklist Update”). Both types have their own search criteria.
With “Worklist Query”, an input mask to enter the search criteria is presented and an interactive
query can be performed. When the query is started on user request, the data from the input mask
will be inserted as matching keys for the query. The user selects the Remote AE to be queried from
the list of DICOM partners that have been configured as Worklist SCP. In addition, the following keys
can be specified by the user: Patient Name, Patient ID, Scheduled Procedure Step Start Date,
Modality, Scheduled Station AE Title and Performing Physician’s Name. In a second step, the user
selects the Scheduled Procedure Steps to be added to the modality’s local list of procedure steps.
With “Worklist Update”, a query is performed in the background and the returned procedure steps
are added to the local worklist. The search criteria for worklist updates can be configured in DBSWIN
using the following attributes: Worklist SCP, Scheduled Procedure Step Start Date, Modality,
Scheduled Station AE Title and Performing Physician. Worklist updates can be triggered manually by
the user, or automatically by DBSWIN in regular time intervals or whenever the user enters the page

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 15 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

that is displaying the local worklist.

Upon initiation of the request, the DICOM Interface will build an Identifier for the C-FIND request,
will initiate an association to send the request and will wait for worklist responses. After retrieval of
all responses, the DICOM Interface adds the Scheduled Procedure Steps to the local worklist and
persistently saves them for further processing, e.g. subsequent Image storage or MPPS creation. If an
error occurs or the Remote AE does not respond within a configurable amount of time, an error is
displayed to the user and the association is closed.
To protect the system from overflow, the DICOM Interface will limit the number of processed
worklist responses to a configurable maximum. During receiving, the worklist response items are
counted and the query processing is cancelled by issuing a C-FIND-CANCEL if the configurable limit of
items is reached.

DICOM AE RIS/HIS

Open Association

C-FIND Request (Worklist Query)

C-FIND Response (Worklist Item)

C-FIND Response (Worklist Item)

C-FIND Response (Success)

Close Association

Proposed Presentation Contexts

The DICOM Interface is capable of proposing the Presentation Contexts shown in the following table:
Presentation Context Table
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name List UID List Neg.

Modality 1.2.840.10008.5.1. Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None

Worklist 4.31 Implicit VR Little Endian 1.2.840.10008.1.2
Information Explicit VR Big Endian 1.2.840.10008.1.2.2
Model – FIND

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 16 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

2.2.3.4 Activity – Create/Update MPPS

2.2.3.4.1 Description and Sequencing of Activities

The DICOM Interface supports the Modality Performed Procedure Step service class in the role of an
SCU. With this service, the application can inform an MPPS SCP within an Information System about
the Procedure Steps that have been performed by the modality and the Images that have been
acquired in each step.
When the DBSWIN user selects to start processing an SPS from a recent worklist query, the DICOM
Interface initiates an association to the Remote AE, creates an MPPS for the corresponding SPS via N-
CREATE command and closes the association. Subsequently acquired images are assigned to this
MPPS until a different MPPS is selected by the user, or the user has marked the MPPS as completed

DICOM AE RIS/HIS

Open Association

N-CREATE (MPPS) – IN PROGRESS

Close Association

Acquire Images

Open Association

N-SET (MPPS) – COMPLETED

Close Association

or aborted. In the latter case, a new association is established and an N-SET command is sent to the
Remote AE which sets the status to COMPLETED or DISCONTINUED, respectively. Associations are
not kept open for the whole lifetime of an MPPS. A new association is opened for every single N-
CREATE or N-SET command.
The DICOM Interface allows the completion of an MPPS even if no Image has been acquired.
The current version of the DICOM Interface preserves a 1-to-1 relationship between a Scheduled
Procedure Step from a Worklist SCP and a resulting MPPS (Normal Case). Grouped Case (one MPPS
for multiple SPSes), Unscheduled Case (MPPS without SPS) and Append Case (multiple MPPSes for
the same SPS) are not supported.
The DICOM Interface assumes that the receiver of the MPPS is the same Application Entity as the
provider of the corresponding SPS. In other words, an MPPS is always sent back to the Application
Entity from which the corresponding SPS has been received. Multiple Worklist/MPPS Providers can
be configured within the DICOM Interface, though.

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 17 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

2.2.3.4.2 Proposed Presentation Contexts

The DICOM Interface is capable of proposing the Presentation Contexts shown in the following table:

Presentation Context Table

Abstract Syntax Transfer Syntax Role Ext.
Name UID Name List UID List Neg.
Modality 1.2.840.10008.3.1.2.3.3 Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
Performed Implicit VR Little Endian 1.2.840.10008.1.2
Procedure Explicit VR Big Endian 1.2.840.10008.1.2.2
Step

2.2.3.5 Activity – Film Images

2.2.3.5.1 Description and Sequencing of Activities

The DICOM Interface provides standard conformance to the Basic Grayscale Print Management Meta
SOP Class as an SCU.
A user selects one or more images to be printed on film sheet, defines how to preformat and
annotate them, selects the desired film format and number of copies, and finally requests them to be
sent to a specific hardcopy device. The film sheet is internally processed, converted to a
STANDARD/1,1 page and then the page image is sent.
Once the Print Image association has been established, the DICOM Interface sends a Basic Film
Session N-CREATE message to the DICOM printer. This is followed by a Basic Film Box N-CREATE
message. In each case, only one Film Box is created and used. The DICOM Interface then sends a
Basic Grayscale Image Box N-SET message. Finally, an N-ACTION message is sent to instruct the Basic
Grayscale Print SCP to print at Basic Film Box level. The association is closed when the image has been
printed and the print job has completed.

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 18 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

DICOM AE Printer

Open Association

N-CREATE (Basic Film Session)

N-CREATE (Basic Film Box)

N-SET (Basic Grayscale Image Box)

N-ACTION (Basic Film Box)

Print Film
Sheets
N-DELETE (Basic Film Box)

N-DELETE (Basic Film Session)

Close Association

2.2.3.5.2 Proposed Presentation Contexts

The DICOM Interface is capable of proposing the Presentation Contexts shown in the following table:

Presentation Context Table

Abstract Syntax Transfer Syntax Role Ext.
Name UID Name List UID List Neg.
Basic 1.2.840.10008.3.1.2.3.3 Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
Grayscale Implicit VR Little Endian 1.2.840.10008.1.2
Print Explicit VR Big Endian 1.2.840.10008.1.2.2
Management
Meta SOP
Class

2.2.3.5.3 SOP Specific Conformance for Basic Grayscale Print Management Meta SOP Class
The DICOM Interface provides standard conformance to the Basic Grayscale Print Management Meta
SOP Class as an SCU. This implies standard conformance for the following SOP classes:
• Basic Film Session SOP Class
• Basic Film Box SOP Class
• Basic Grayscale Image Box SOP Class
• Printer SOP Class

2.2.3.5.4 SOP Specific Conformance for Basic Film Session SOP Class
The DICOM Interface supports the following DIMSE operations for the Basic Film Session SOP Class:

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 19 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

• N-CREATE
• N-DELETE
The following table lists the supported N-CREATE Request Attributes:
(“Auto”: value is determined by the application, “ANAP”: Attribute Not Always Present)

Attribute Name Tag Value Default Presence of Source

Value
Number of Copies (2000,0010) 1 to many 1 ALWAYS User
Print Priority (2000,0020) LOW LOW ALWAYS Auto
Medium Type (2000,0030) PAPER printer setting ANAP User
CLEAR FILM
BLUE FILM
printer setting
Film Destination (2000,0040) MAGAZINE CURRENT ALWAYS User
PROCESSOR
CURRENT

2.2.3.5.5 SOP Specific Conformance to Basic Film Box SOP Class

The DICOM Interface supports the following DIMSE operations for the Basic Film Box SOP Class:
• N-CREATE
• N-DELETE
The following table lists the supported N-CREATE Request Attributes:
(“Auto”: value is determined by the application, “ANAP”: Attribute Not Always Present)

Attribute Name Tag Value Default Presence of Source

Value
Image Display Format (2010,0010) STANDARD\1,1 STANDARD\1,1 ALWAYS Auto
Referenced Film Session (2010,0500) ALWAYS Auto
Sequence
>Referenced SOP Class UID (0008,1150) 1.2.840.10008. ALWAYS Auto
5.1.1.1
>Referenced SOP Instance (0008,1155) ALWAYS Auto
UID
Film Orientation (2010,0040) PORTRAIT LANDSCAPE ALWAYS User
LANDSCAPE
Film Size ID (2010,0050) 8INX10IN ALWAYS User
85INX11IN1
8_5INX11IN
10INX12IN
11INX11IN
11INX14IN
11INX17IN
14INX14IN

1
Support for Agfa DRYSTAR 2000

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 20 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

14INX17IN
24CMX24CM
24CMX30CM
A3
A4
Magnification Type (2010,0060) NONE NONE ALWAYS User
REPLICATE
BILINEAR
CUBIC
Smoothing Type (2010,0080) ANAP User
Border Density (2010,0100) BLACK printer setting ANAP User
WHITE
printer setting
Requested Resolution ID (2020,0050) STANDARD printer setting ANAP User
HIGH
printer setting

2.2.3.5.6 SOP Specific Conformance to Basic Grayscale Image Box SOP Class
The DICOM Interface supports the following DIMSE operations for the Basic Grayscale Image Box SOP
Class:
• N-SET
The following table lists the supported N-CREATE Request Attributes:
(“Auto”: value is determined by the application, “ANAP”: Attribute Not Always Present)

Attribute Name Tag Value Default Presence of Source

Value
Image Position (2020,0010) 1 1 ALWAYS Auto
Basic Grayscale Image (2020,0110) ALWAYS Auto
Sequence
>Samples Per Pixel (0028,0002) 1 1 ALWAYS Auto
>Photometric (0028,0004) MONOCHROM MONOCHROM ALWAYS Auto
Interpretation E2 E2
>Rows (0028,0010) ALWAYS Auto
>Columns (0028,0011) ALWAYS Auto
>Bits Allocated (0028,0100) 8 or 16 8 ALWAYS Auto
>Bits Stored (0028,0101) 8, 12 or 16 8 ALWAYS Auto
>High Bit (0028,0102) 7, 11 or 15 7 ALWAYS Auto
>Pixel Representation (0028,0103) 0 0 ALWAYS Auto
>Pixel Data (7FE0,0010) ALWAYS Auto
Requested Decimate/Crop (2020,0040) DECIMATE printer setting ANAP User
Behavior CROP
FAIL
printer setting

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 21 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

2.2.4 Association Acceptance Policy

The DICOM Interface accepts associations for the following activities:

• Send Verification Response
• Receive Storage Commitment Response

2.2.4.1 Activity – Send Verification Response

2.2.4.1.1 Description and Sequencing of Activities

The DICOM Interface can be configured to act as a Verification SCP. The remote AE opens an
association (using the DICOM Interface’s configured AE Title, IP address and TCP/IP port), sends a C-
ECHO request and closes the association upon receiving the C-ECHO response from the DICOM
Interface.

2.2.4.2 Activity – Receive Storage Commitment Response

2.2.4.2.1 Description and Sequencing of Activities

The DICOM Interface will accept associations in order to receive responses to a Storage Commitment
Request. The Storage Commitment SCP (e.g. an image manager or PACS) opens an association, sends
an N-EVENT-REPORT notifying the DICOM Interface of the status of a previous Storage Commitment
request and closes the association.

DICOM AE Image
Manager

Open Association

N-EVENT-REPORT (Storage Commitment Response)

Close Association

2.2.4.2.2 Accepted Presentation Contexts

The DICOM Interface accepts the following transfer syntaxes:

Presentation Context Table

Abstract Syntax Transfer Syntax Role Ext.
Name UID Name List UID List Neg.
Storage 1.2.840.10008.1.20.1 Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
Commitment Implicit VR Little Endian 1.2.840.10008.1.2
Push Model Explicit VR Big Endian 1.2.840.10008.1.2.2
The DICOM Interface will prefer to select the Explicit VR Little Endian Transfer Syntax if multiple

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 22 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

transfer syntaxes are offered.

2.3 Network Interfaces

The DICOM Interface provides DICOM V3.0 TCP/IP network communication support as defined in PS
3.8 of [1].

2.3.1 Physical Network Interface

The DICOM Interface runs on any physical media supported by the TCP/IP stack that runs on the local
machine.

2.3.2 Additional Protocols

No Additional Protocols are supported.

2.3.3 IPv4 and IPv6 Support

The DICOM Interface only supports IPv4 connections.

2.4 Configuration

2.4.1 AE Title/Presentation Address Mapping

The DICOM Interface uses the AE Title and TCP/IP Port configured in the DICOM configuration panel
of the DBSWIN software application.
The default value for the local AE Title is “DBSWIN_<compname>” where <compname> is the name
of the local machine. The default TCP/IP port number is 8104.
The AE Titles, IP addresses, TCP/IP port numbers and capabilities of the remote AEs are configured
using the DICOM configuration panel of the DBSWIN software application.

2.4.2 Parameters

The DICOM configuration parameters are described in the DICOM user manual.

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 23 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

3 Media Interchange

3.1.1 Implementation Model

3.1.2 Application Data Flow

Export to
File System
DBSWIN

DICOM AE File System

Import from
File System

3.1.3 Functional Definition

The DICOM Interface supports DICOM Media export only and acts as a FSC (File Set Creator).

3.1.4 File Meta Information Options

The implementation information written to the File Meta Header in each file is:

Attribute Name Attribute Value

File Meta Information Version 00\01
Implementation Class UID 1.2.276.0.82.1.1
Implementation Version Name DD_DICOM_20

3.1.5 Activity – Export to File System

The user selects the images to be exported and chooses whether to export as standard DICOMDIR or
as individual DICOM dataset files. If exported as DICOMDIR, the user can choose to either create a
new DICOMDIR, or to override or extend an existing DICOMDIR (see DICOM user manual for details).
In order to support full WYSIWYG functionality independent of third-party DICOM viewer capabilities,
overlay graphics and image transformations will be “burned” into the image pixel data unless export
mode “Original” is used. In “Original” mode, the linear windowing data (window center and width)
and photometric interpretation are exported separately using the respective DICOM attributes.
The DICOM Interface cannot write directly onto CD-R or DVD, it can only write to media that
supports standard random access file I/O (e.g. harddisk or formatted MOD). Writing directly onto CD-
R/DVD requires additional software and hardware.

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 24 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

If the file system is used only as temporary storage for a subsequent CD-R/DVD archiving step (using
some third-party CD-R/DVD recording software), the user must be aware that the exported amount
of data can exceed the size limits of the actual archive media.
The DICOM Interface can export the following IODs:

SOP Class Name SOP Class UID

Basic Directory Storage 1.2.840.10008.1.3.10
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7
Digital X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.1
Digital Intra-oral X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.3

Transfer Syntax Transfer Syntax UID

Explicit VR Little Endian 1.2.840.10008.1.2.1

3.1.6 Activity – Import from File System

The DBSWIN user can select to import one or more DICOM image dataset files. The DICOM Interface
currently does not support the import of a DICOMDIR. Only individual DICOM image dataset files can
be selected and imported.
The DICOM Interface can import the following IODs:

SOP Class Name SOP Class UID

Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7
Digital X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.1
Digital Intra-oral X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.3

Transfer Syntax Transfer Syntax UID

Explicit VR Little Endian 1.2.840.10008.1.2.1
Implicit VR Little Endian 1.2.840.10008.1.2
Explicit VR Big Endian 1.2.840.10008.1.2.2
JPEG Baseline (Process 1) 1.2.840.10008.1.2.4.50
JPEG Extended (Process 2 & 4) 1.2.840.10008.1.2.4.51
JPEG Spectral Selection, Non-Hierarchical (Process 6 & 8) 1.2.840.10008.1.2.4.53
JPEG Full Progression, Non-Hierarchical (Process 10 & 12) 1.2.840.10008.1.2.4.55
JPEG Lossless, Non-Hierarchical (Process 14) 1.2.840.10008.1.2.4.57
JPEG Lossless, Hierarchical, First-Order Prediction 1.2.840.10008.1.2.4.70
(Process 14 [Selection Value 1])

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 25 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

4 Support of Character Sets

The DICOM Interface supports the following character sets:
• ISO_IR 100
• ISO 2022 IR 13 (Katakana und Romaji)
• ISO 2022 IR 87 (Kanji)

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 26 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

5 Security
No Security Profiles are supported.

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 27 of 28
 DICOM Conformance Statement D-No.: 1070525
DBSWIN Rev: C

6 Annexes

6.1 Standard Extended/Specialized/Private SOP Classes

No Standard Extended, Specialized or Private SOP Classes are supported.
In addition to the standard SC IOD the DICOM Interface can supply the following Tag as defined in
PS3.3, C.7.6.2 of [1].

Attribute Name Tag Description

Pixel Spacing (0028,0030) Physical distance in the patient between the center of
each pixel, specified by a numeric pair - adjacent row
spacing (delimiter) adjacent column spacing in mm.

6.2 Private Transfer Syntaxes

No Private Transfer Syntaxes are supported.

Superior document: PLM and Design Controls 3292461 D-No. Template: 3811640 Template effective from: 01.08.2018
Responsible department: R&D Revision Template: - Page 28 of 28