CLINIVIEW 11 DICOM Conformance Statement R3

CLINIVIEW 11
Instrumentarium Dental DICOM CONFORMANCE STATEMENT
Technical
Publications
D529800,3
Revision 0.19
3.11.2021
CLINIVIEW 11
DICOM CONFORMANCE STATEMENT
Copyright © 2021 Instrumentarium Dental, PaloDEx Group Oy
1 / 56
CLINIVIEW 11
1 CONFORMANCE STATEMENT OVERVIEW
CLINIVIEW is a digital dental X-ray imaging system:

— It uses DICOM services to send/receive image to/from remote workstations.
— It allows a user to query for and display modality worklist information from a remote hospital or
radiology department information system computer
— It is capable of printing images to DICOM printers
Table 1-1 provides an overview of the network services supported by CLINIVIEW.
TABLE 1-1: NETWORK SERVICES

SOP Classes User of Service (SCU) Provider of Service
(SCP)
Workflow Management
Modality Worklist Information Model Yes No
– FIND
Storage Commitment Push Model Yes No
Print Management
Printer SOP Class Yes No
Basic Grayscale Print Management Yes No
Meta SOP Class
Basic Film Session SOP Class Yes No
Basic Film Box SOP Class Yes No
Basic Grayscale Image Box SOP Class Yes No
Basic Color Print Management Meta Yes No
SOP Class
Basic Color Image Box SOP Class Yes No
Transfer
Computed Radiography Image Storage Yes Yes
Digital X-ray Image Storage – For Yes Yes
Presentation
Digital X-ray Image Storage – For Yes Yes
Processing
Digital Intra-oral X-ray Image Storage Yes Yes
– For Presentation
Digital Intra-oral X-ray Image Storage Yes Yes
– For Processing
CT Image Storage Yes Yes
Enhanced CT Image Storage Yes Yes
Secondary Capture Image Storage Yes Yes

Multi-frame Grayscale Byte Yes Yes
Secondary Capture Image
Storage
2 / 56
CLINIVIEW 11
SOP Classes User of Service (SCU) Provider of Service

(SCP)
Multi-frame Grayscale Word Yes Yes
Storage
Multi-frame True Color Yes Yes
Storage
VL Photographic Image Storage Yes Yes
Query / Retrieve
Patient Root Query/Retrieve Yes No
Information Model – FIND
Patient Root Query/Retrieve Yes No
Information Model – MOVE
Study Root Query/Retrieve Yes No
Information Model – FIND
Study Root Query/Retrieve Yes No
Information Model – MOVE
Table 1-2 provides an overview of the Media Storage Application profiles supported by CLINIVIEW.
TABLE 1-2: MEDIA SERVICES

Media Storage Application Profile Write Files (FSC) Read Files (FSR)
Compact Disk - Recordable
General Purpose CD-R Yes Yes
Magneto-Optical Disk
Not supported
DVD
General Purpose DVD-RAM Yes Yes
3 / 56
CLINIVIEW 11
2 TABLE OF CONTENTS
1 CONFORMANCE STATEMENT OVERVIEW ............................................................................................................ 2
2 TABLE OF CONTENTS .................................................................................................................................................. 4
3 INTRODUCTION ............................................................................................................................................................. 5
3.1 OVERVIEW .................................................................................................................................................................... 5
3.2 REVISION HISTORY ........................................................................................................................................................... 6
3.3 AUDIENCE ..................................................................................................................................................................... 7
3.4 SCOPE AND FIELD OF APPLICATION ....................................................................................................................... 7
3.5 REMARKS ......................................................................................................................................................................... 7
3.6 REFERENCES ................................................................................................................................................................ 8
3.7 TERMS AND DEFINITIONS ........................................................................................................................................... 8
3.8 ABBREVIATIONS ............................................................................................................................................................. 10
4 NETWORKING .............................................................................................................................................................. 11
4.1 IMPLEMENTATION MODEL ..................................................................................................................................... 11
4.1.1 Application Data Flow Diagram ........................................................................................................................... 11
4.1.2 Functional Definition of AE's ................................................................................................................................ 12
4.1.3 Sequencing of Real World Activities ...................................................................................................................... 14
4.2 AE SPECIFICATIONS .................................................................................................................................................. 15
4.2.1 CLINIVIEW Client AE ........................................................................................................................................... 15
4.2.2 CLINIVIEW Storage SCP AE ................................................................................................................................ 32
4.2.3 CLINIVIEW Storage SCU AE ................................................................................................................................ 35
4.3 NETWORK INTERFACES .................................................................................................................................................. 40
4.3.1 Physical Network Interface .................................................................................................................................... 40
4.4 CONFIGURATION....................................................................................................................................................... 40
4.4.1 AE title / presentation address mapping ................................................................................................................ 40
4.4.2 Parameters ............................................................................................................................................................. 41
5 MEDIA INTERCHANGE .............................................................................................................................................. 46
5.1 IMPLEMENTATION MODEL .............................................................................................................................................. 46
5.1.1 Application Data Flow Diagram ........................................................................................................................... 46
5.1.2 Functional Definitions of AEs ................................................................................................................................ 46
5.1.3 Sequencing of Real-World Activities ...................................................................................................................... 47
5.1.4 File Meta Information Options .............................................................................................................................. 47
5.2 AE SPECIFICATIONS .................................................................................................................................................. 48
5.2.1 Application Entity Specification of CLINIVIEW Media AE ................................................................................... 48
5.3 AUGMENTED AND PRIVATE APPLICATION PROFILES ..................................................................................... 50
5.4 MEDIA CONFIGURATION ......................................................................................................................................... 51
6 SUPPORT OF CHARACTER SETS ............................................................................................................................. 52
7 SECURITY PROFILES .................................................................................................................................................. 53
8 ANNEXES ........................................................................................................................................................................ 54
8.1 IOD CONTENTS ........................................................................................................................................................... 54
8.2 DATA DICTIONARY AND PRIVATE ATTRIBUTES ............................................................................................... 54
8.3 CODED TERMINOLOGY AND TEMPLATES .......................................................................................................... 54
8.4 GRAYSCALE IMAGE CONSISTENCY ..................................................................................................................... 54
8.5 STANDARD EXTENDED/SPECIALIZED/PRIVATE SOP CLASSES ...................................................................... 54
8.6 PRIVATE TRANSFER SYNTAXES ............................................................................................................................ 56
4 / 56
CLINIVIEW 11
3 INTRODUCTION
3.1 OVERVIEW
This DICOM Conformance Statement is divided into Sections as described below:
Section 3 Introduction, which describes the overall structure, intent, and references for this Conformance
Statement
Section 4 Networking, which specify CLINIVIEW software compliance to the DICOM requirements for the
implementation of networking features.
Section 5 Media Interchange, which specify the CLINIVIEW software compliance to the DICOM
requirements for the implementation of Media Storage features.
Section 6 Supported Character Sets.
Section 7 Security.
Annexes.
For more information regarding DICOM, copies of the Standard may be obtained on the Internet at
https://www.dicomstandard.org/. Comments on the Standard may be addressed to:
dicom@dicomstandard.org
c/o Medical Imaging & Technology Alliance (MITA)
1300 North 17th Street, Suite 900
Arlington, VA 22209, USA
5 / 56
CLINIVIEW 11
3.2 REVISION HISTORY
Revision Date Reason for Change Pages
001 02.03.2004 First draft 25
002 15.03.2004 Second 24
003 22.03.2004 Third 30
004 23.03.2004 Fourth 30
005 16.04.2004 Comment fixes 30
006 6.5.2004 Comment fixes 32
007 27.10.2005 Final 30
008 03.07.2007 Minor improvements 30
009 26.02.2008 VT features added. Media Storage Application profile 32

for Read Media, table added. Print priority and film
session label changed.
010 15.4.2008 Changes in document structure. 30
011 13.6.2008 Major editing, chapters rearranged, sequence diagrams 45

added, data flow diagram redrawn and configurable
parameters added.
012 18.9.2008 Document finalized for CliniView 8.1. 46
013 30.9.2009 New features added: Storage Commitment SCU, 56

Secondary Captures and CR.
014 9.12.2010 N-Action of printing corrected. Added info of overlay 55

graphics. New worklist query mode added.
015 29.3.2011 Enhanced CT Image Storage SOP Class added. 55
016 6.7.2016 Updated versions for CliniView 11.1 55
017 8.1.2020 Added information related to DIN 6862-2 to chapter 8.5. 56

VT features removed (not supported).
018 18.2.2021 Added default AE titles to chapter 4.4.1. Added ISO IR 56

192 to supported character sets to chapter 6.
019 3.11.2021 Updated version to CliniView 11 56
6 / 56
CLINIVIEW 11
3.3 AUDIENCE
This document is written for the people that need to understand how CLINIVIEW 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.
3.4 SCOPE AND FIELD OF APPLICATION

It is the intent of this document to provide an unambiguous specification for CLINIVIEW software
implementation. This specification includes a DICOM Conformance Statement and is necessary to ensure
proper processing and interpretation of CLINIVIEW medical data exchanged using DICOM v3.0. The
CLINIVIEW Conformance Statements are available to the public.
Included in this DICOM Conformance Statement are the Module Definitions, which define all data elements,
used by this CLINIVIEW implementation. If the user encounters unspecified private data elements while
parsing a CLINIVIEW Data Set, the user is well advised to ignore those data elements (per the DICOM
standard). Unspecified private data element information is subject to change without notice. If, however, the
device is acting as a "full fidelity storage device", it should retain and re-transmit all of the private data
elements, which are sent by CLINIVIEW software.
3.5 REMARKS
The scope of this DICOM Conformance Statement is to facilitate integration between CLINIVIEW 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.
7 / 56
CLINIVIEW 11
3.6 REFERENCES
NEMA PS3 Digital Imaging and Communications in Medicine (DICOM) Standard, available free at
https://www.dicomstandard.org/
CLINIVIEW User Manual, available on the product DVD-ROM.
CLINIVIEW Installation Manual, available on the product DVD-ROM.
3.7 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 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 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 Definition (IOD) – the specified set of Attributes that comprise a type of data object;
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 Group (JPEG) – a set of standardized image compression techniques,
available for use 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
8 / 56
CLINIVIEW 11
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 (SCP) – role of an Application Entity that provides a DICOM network service;
typically, a server that performs operations requested by another Application Entity (Service Class User).
Examples: Picture Archiving and 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 (SOP) Class – the specification of the network or media transfer (service) of a
particular type of data (object); the fundamental unit of DICOM interoperability specification. Examples:
Ultrasound Image Storage Service, Basic Grayscale Print Management.
Service/Object Pair (SOP) Instance – an information object; a specific occurrence of information

exchanged 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.
9 / 56
CLINIVIEW 11
3.8 ABBREVIATIONS
AE Application Entity
CD-R Compact Disk Recordable
CR Computed Radiography
CT Computed Tomography
DHCP Dynamic Host Configuration Protocol
DICOM Digital Imaging and Communications in Medicine
DNS Domain Name System
DX Digital X-ray
ECT Enhanced Computed Tomography
FSC File-Set Creator
FSU File-Set Updater
FSR File-Set Reader
HIS Hospital Information System
IOD Information Object Definition
ISO International Organization for Standards
IO Intra-oral X-ray
JPEG Joint Photographic Experts Group
OSI Open Systems Interconnection
PACS Picture Archiving and Communication System
PDU Protocol Data Unit
RIS Radiology Information System.
SC Secondary Capture
SCP Service Class Provider
SCU Service Class User
SOP Service-Object Pair
TCP/IP Transmission Control Protocol/Internet Protocol
VL Visible Light
VR Value Representation
10 / 56
CLINIVIEW 11
4 NETWORKING
4.1 IMPLEMENTATION MODEL
4.1.1 Application Data Flow Diagram

The network application model for CLINIVIEW is shown in the following Illustration:
11 / 56
CLINIVIEW 11
FIGURE 4-1: APPLICATION DATA FLOW DIAGRAM
— The Client AE provides the following DICOM network services: retrieves worklist, stores images
(when storage commitment -feature is disabled), prints images, queries for information and sends
verifications.
Query and retrieve activities are drawn as overlapping, because query is needed to be made before the
retrieve can be initiated.
— Storage SCP AE receives images from remote AEs and stores them to local database. They can be
results of the Retrieve activity initiated by the Client AE.
It also answers to connectivity verifications.
— Storage SCU AE is used only when the Storage Commitment -feature is enabled. It is then used to both
store images (instead of the Client AE), sends storage commitment requests, receives storage
commitment reports and answers to connectivity verifications. The commitment requests can be sent
for each image after it has been sent to storage.
4.1.2 Functional Definition of AE's

All communication is accomplished utilizing the DICOM protocol over a network using the TCP/IP protocol
stack.
CLINIVIEW implementation utilizes MergeCOM-3™ Tool Kit to accomplish the DICOM Services
4.1.2.1 Functional Definition of CLINIVIEW Client AE

When an activity is invoked, CLINIVIEW Client AE sends an association request to the remote application.
If the association is accepted CLINIVIEW requests for a DICOM operation related to the DICOM service
that was invoked by the local real world activity.
If the negotiated service is accepted, CLINIVIEW transfers the real world activities to the specified remote
Application Entity according to the DICOM protocol.
The following services are implemented in the Client AE:

— Verification SCU: test if the remote AE can be connected
— Worklist SCU: Worklist items are received from Worklist provider to CLINIVIEW
— Storage SCU: Images are sent to e.g. PACS
— Print SCU: Images are printed on film or paper
— Query SCU: Patient, study, series and image data is received from e.g. PACS
— Move SCU: Moving of an image from e.g. PACS to CLINIVIEW.
4.1.2.2 Functional Definition of CLINIVIEW Storage SCP AE

CLINIVIEW Storage SCP accepts associations from remote AEs, and provides the following services when
requested:
— Verification SCP: answer for a connectivity verification initiated by remote AE
— Storage SCP: receive images from e.g. PACS.
4.1.2.3 Functional Definition of CLINIVIEW Storage SCU AE

When an activity is invoked, CLINIVIEW Storage SCU sends an association request to the remote
application. If the association is accepted CLINIVIEW requests for a DICOM operation related to the
DICOM service that was invoked by the local real world activity.
If the negotiated service is accepted, CLINIVIEW transfers the real world activities to the specified remote
Application Entity according to the DICOM protocol.
12 / 56
CLINIVIEW 11
Association requests are send for the following services:

— Storage SCU: Images are sent to e.g. PACS
— Storage Commitment Push Model SCP: sends storage commitment requests to e.g. PACS.
CLINIVIEW Storage SCU AE also accepts associations from remote AEs, and provides the following
services when requested:
— Verification SCP: answer for a connectivity verification initiated by remote AE
— Storage Commitment Push Model SCP: receive storage commitment reports from e.g. PACS.
13 / 56
CLINIVIEW 11
4.1.3 Sequencing of Real World Activities

A typical sequence of Real World Activities is shown in the diagram below:
FIGURE 4-2: SEQUENCE DIAGRAM
— The following constraints apply to the sequencing of the Real World activities
▪ Query needs to be made before Retrieving of the images.
▪ Storage needs to be made before Storage Commitment Request.
14 / 56
CLINIVIEW 11
▪ Storage Commitment Request needs to made before Storage Commitment Report can be
received.
— All other activities are independent of each other.
— Patient demographics need not to be selected through Worklist, but can also be opened from local
database, imported along with an image, retrieved from Archive, received from a 3 rd party patient
management software or fed in manually.
— Image saving and storing an image to PACS, can be automated, so that no user actions are required.
— Image retrieve can be scheduled to take place at an operator selected time.
— Storage Commitment Request is automatically sent when Storage Commitment service is enabled.
— Failed Storage, Storage Commitment and Retrieve requests can be configured to be resent in case of an
failure.
4.2 AE SPECIFICATIONS
There are 3 AEs: CLINIVIEW Client AE, Storage SCP AE and Storage SCU AE.
4.2.1 CLINIVIEW Client AE
4.2.1.1 SOP Classes

CLINIVIEW Client AE provides standard conformance to the following Service Object Pair (SOP) Classes.
TABLE 4-1: SOP CLASSES FOR CLINIVIEW APPLICATION ENTITY

SOP Class Name SOP Class UID SCU SCP
Verification
Verification SOP Class 1.2.840.10008.1.1 Yes No
Storage
Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1 Yes No
Digital X-ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.1 Yes No
Digital X-ray Image Storage – For Processing 1.2.840.10008.5.1.4.1.1.1.1.1 Yes No
Digital Intra-oral X-ray Image Storage – For 1.2.840.10008.5.1.4.1.1.1.3 Yes No
Presentation
Digital Intra-oral X-ray Image Storage – For 1.2.840.10008.5.1.4.1.1.1.3.1 Yes No
Processing
CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Yes No
Enhanced CT Image Storage 1.2.840.10008.5.1.4.1.1.2.1 Yes No
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Yes No
Multi-frame Grayscale Byte 1.2.840.10008.5.1.4.1.1.7.2 Yes No
Storage
Multi-frame Grayscale Word 1.2.840.10008.5.1.4.1.1.7.3 Yes No
Storage
Multi-frame True Color 1.2.840.10008.5.1.4.1.1.7.4 Yes No
Storage
VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 Yes No
Query / Retrieve
Patient Root Query/Retrieve Information Model – 1.2.840.10008.5.1.4.1.2.1.1 Yes No
FIND
15 / 56
CLINIVIEW 11
Patient Root Query/Retrieve Information Model – 1.2.840.10008.5.1.4.1.2.1.2 Yes No

MOVE
Study Root Query/Retrieve Information Model – 1.2.840.10008.5.1.4.1.2.2.1 Yes No
FIND
Study Root Query/Retrieve Information Model – 1.2.840.10008.5.1.4.1.2.2.2 Yes No
MOVE
Modality Worklist
Modality Worklist 1.2.840.10008.5.1.4.31 Yes No
Print
Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Yes No
Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Yes No
Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4 Yes No
Basic Color Image Box SOP Class 1.2.840.10008.5.1.1.4.1 Yes No
Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9 Yes No
Printer SOP Class 1.2.840.10008.5.1.1.16 Yes No
Basic Color Print Management Meta SOP Class 1.2.840.10008.5.1.1.18 Yes No
4.2.1.2 Association Policies
4.2.1.2.1 General
The DICOM standard application context name for DICOM 3.0 is always proposed:
TABLE 4-2: DICOM APPLICATION CONTEXT

Application Context Name 1.2.840.10008.3.1.1.1
4.2.1.2.2 Number of Associations

CLINIVIEW supports multiple associations as an SCU and SCP. When sending images CLINIVIEW may
start a new thread for image print association. Also during sending images and / or printing, a worklist query
may be initiated. However multiple send, print or query jobs will be performed sequentially.
4.2.1.2.3 Asynchronous Nature

Asynchronous mode is not supported. All operations will be performed synchronously.
4.2.1.2.4 Implementation Identifying Information

Implementation information for this application entity is:
TABLE 4-3: DICOM IMPLEMENTATION CLASS AND VERSION FOR CLINIVIEW APPLICATION ENTITY
CLINIVIEW Implementation UID 1.2.840.113999.42.6.0
CLINIVIEW Implementation Version Name CV_102
16 / 56
CLINIVIEW 11
4.2.1.3 Association Initiation Policy
4.2.1.3.1 Activity – Send Store Request
4.2.1.3.1.1 Description and Sequencing of Activities

A sequence of interactions is shown in the sequence diagram below:
FIGURE 4-3: SEQUENCE OF ACTIVITY – STORAGE SCU
The operator of CLINIVIEW system initiates digital images storage on remote SCP from CLINIVIEW
software user interface. This can be done for the active image only, for the selected images of the patient or
for all images of one the patient that are not yet stored.
Also an auto storage option may be set, which sends each new image to the storage without any operator
actions.
Several storage SCPs can be defined, but only one is always the default storage SCP, which is used when the
storage is made using the auto storage feature.
If several images are selected for sending, then new associations are opened for sending the C-Store requests
for each of them.
Images selected for sending are shown in the graphical queue, along with their sending status: pending,
sending, sent or error. Images can be resent from the queue by the operator as well as removed from the
queue. Automatic resending can also be configured.
This activity is not being used by Client AE, if the storage commitment activity of the Storage SCU AE has
been configured to be used.
4.2.1.3.1.2 Proposed Presentation Context

CLINIVIEW Client AE is capable of proposing the Presentation Contexts shown in the following table:
17 / 56
CLINIVIEW 11
TABLE 4-4: PRESENTATION CONTEXT TABLE OF STORAGE SCU

Presentation Context Table
Abstract Syntax Transfer Syntax Role Extended
Negotiation
Name UID Name List UID List
Computed 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Radiography 5.1.4.1.1.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Explicit VR Big Endian 1.2.840.10008.1.2.2
Digital X-Ray Image 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Storage – For 5.1.4.1.1.1.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Presentation Explicit VR Big Endian 1.2.840.10008.1.2.2
Digital X-Ray Image 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Storage – For 5.1.4.1.1.1.1.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Processing Explicit VR Big Endian 1.2.840.10008.1.2.2
Digital Intra-oral X- 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Ray Image Storage - 5.1.4.1.1.1.3 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
For Presentation Explicit VR Big Endian 1.2.840.10008.1.2.2
Digital Intra-oral X- 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Ray Image Storage - 5.1.4.1.1.1.3.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
For Processing Explicit VR Big Endian 1.2.840.10008.1.2.2
CT Image Storage 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
5.1.4.1.1.2 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Enhanced CT Image 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Storage 5.1.4.1.1.2.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Secondary Capture 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Image Storage 5.1.4.1.1.7 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Multi-frame 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Grayscale Byte 5.1.4.1.1.7.2 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Secondary Capture Explicit VR Big Endian 1.2.840.10008.1.2.2
Image
Storage
Multi-frame 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Grayscale Word 5.1.4.1.1.7.3 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Image
Storage
Multi-frame True 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Color 5.1.4.1.1.7.4 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Image
Storage
VL Photographic 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Image Storage 5.1.4.1.1.77.1. Implicit VR Little Endian, 1.2.840.10008.1.2.1,
4 Explicit VR Big Endian 1.2.840.10008.1.2.2
18 / 56
CLINIVIEW 11
4.2.1.3.1.3 SOP Specific Conformance

The abstract syntax used, is based on the image type in CliniView, and can be configured as follows:
— Panoramic and cephalometric images:
o Digital X-Ray Image Storage - either For Presentation or For Processing, depending on the
user setting.
o Computed Radiography
— Intraoral images:
o Digital Intra-oral X-Ray Image Storage - either For Presentation or For Processing,
depending on the user setting.
user setting.
— Cone Beam 3D images:
o CT Image Storage
o Enhanced CT Image Storage
— Cone Beam 3D Scout images:
user setting
— Photographic images:
o VL Photographic Image Storage
o Secondary Capture Image Storage
o Multi-frame Grayscale Byte Secondary Capture Image Storage
o Multi-frame Grayscale Word Secondary Capture Image Storage
o Multi-frame True Color Secondary Capture Image Storage
Overlay graphics drawn on the image are saved using the Overlay plane module, DICOM tags 6000,xxxx.
This includes e.g. lines and texts, but does not include ROIs or pseudo-colorization.
4.2.1.3.2 Activity – Send Print Request

A typical sequence is shown below. There can be several N-SET (Image Box) operations.
19 / 56
CLINIVIEW 11
FIGURE 4-4: SEQUENCE OF ACTIVITY – PRINT
CLINIVIEW operator selects the images to be printed to the remote Print SCP in CLINIVIEW user
interface.
Operator can choose lay out the images freely in a single image box or select the number of image boxes and
then assign zero or one images to each image box.
A graphical print job queue is provided, where the operator can see the status of the print jobs, change the
odder of the print jobs in the queue, or delete or restart a print job.
4.2.1.3.2.2 Proposed presentation contexts

TABLE 4-5: PRESENTATION CONTEXT TABLE OF PRINT

Negotiation
Basic Grayscale 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Print Management 5.1.1.9 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Meta Explicit VR Big Endian 1.2.840.10008.1.2.2
Basic Color Print 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Management Meta 5.1.1.18 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
20 / 56
CLINIVIEW 11

Basic Grayscale Print Management Meta SOP Class is defined by the following set of supported SOP
Classes:
TABLE 4-6: SUPPORTED SOP CLASSES AS BASIC GRAYSCALE PRINT MANAGEMENT

SOP Class Name SOP Class UID
Basic Film Session SOP Class 1.2.840.10008.5.1.1.1
Basic Film Box SOP Class 1.2.840.10008.5.1.1.2
Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4
Printer SOP Class 1.2.840.10008.5.1.1.16
TABLE 4-7: SUPPORTED SOP CLASSES AS BASIC COLOR PRINT MANAGEMENT

SOP Class Name SOP Class UID
Basic Film Session SOP Class 1.2.840.10008.5.1.1.1
Basic Film Box SOP Class 1.2.840.10008.5.1.1.2
Basic Color Image Box SOP Class 1.2.840.10008.5.1.1.4.1
Printer SOP Class 1.2.840.10008.5.1.1.16
CLINIVIEW Client AE does not support any optional SOP Classes.
4.2.1.3.2.3.1 SOP Specific Conformance for the Film Session SOP Class
CLINIVIEW Client AE supports the following DIMSE operations and notifications for the Film Session
SOP Class:
— N-Create
— N-Action
— N-Delete
4.2.1.3.2.3.1.1 Film Session SOP Class Operations (N-CREATE)

The attributes supplied in an N-CREATE Request are listed in the Table below:
TABLE 4-8: BASIC FILM SESSION SOP CLASS N-CREATE REQUEST ATTRIBUTES
Attribute Name Tag VR Default Value Valid Range
Number of Copies (2000,0010) IS 1 1..99
Print Priority (2000,0020) CS HIGH HIGH, MED, LOW
Medium Type (2000,0030) CS PAPER PAPER, CLEAR FILM,
BLUE FILM
21 / 56
CLINIVIEW 11
Film Destination (2000,0040) CS PROCESSOR PROCESSOR,

MAGAZINE, BIN_i
Film Session Label (2000,0050) LO DPM Print Value is fixed.
Owner ID (2100,0160) SH n/a
4.2.1.3.2.3.1.2 Basic Film Box SOP Class Operations (N-ACTION)

An N-ACTION Request is issued to instruct the Print SCP to print the contents of the Film Box.
4.2.1.3.2.3.1.3 Film Session SOP Class Operations (N-DELETE)

An N-DELETE operation is issued at the end if film session.
4.2.1.3.2.3.2 SOP Specific Conformance for the Film Box SOP Class
CLINIVIEW Client AE supports the following DIMSE operations and notifications for the Film Box SOP
Class:
— N-Create
4.2.1.3.2.3.2.1 Basic Film Box SOP Class Operations (N-CREATE)

The attributes supplied in an N-CREATE Request are listed in the Table below:
TABLE 4-9: BASIC FILM BOX SOP CLASS N-CREATE REQUEST ATTRIBUTES
Image Display (2010,0010) ST STANDARD\1,1 STANDARD\C,R,
Format where C is number of
columns and R is the
number of rows.
Annotation Display (2010,0030) CS ""
Format ID
Film Orientation (2010,0040) CS PORTRAIT PORTRAIT, LANDSCAPE
Film Size ID (2010,0050) CS A4 8INX10IN, 8_5INX11IN,
10INX12IN, 10INX14IN,
24CMX24CM,
24CMX30CM, A4, A3
Magnification Type (2010,0060) CS CUBIC REPLICATE, BILINEAR,
CUBIC, NONE
Smoothing Type (2010,0080) CS 1
Border Density (2010,0100) CS WHITE BLACK, WHITE, I, where
0..300
Empty Image (2010,0110) CS n/a BLACK, WHITE, I, where
Density 0..300
Max Density (2010,0130) US 300 0..300
Trim (2010,0140) CS n/a YES, NO
Configuration (2010,0150) ST LUT=0,3
22 / 56
CLINIVIEW 11
Information
Referenced Film (2010,0500) SQ
Session Sequence
Referenced SOP (0008,1150) UI 1.2.840.10008.5.1.1.1
Class UID
Referenced SOP (0008,1155) UI n/a
Instance UID
4.2.1.3.2.3.3 SOP Specific Conformance for the Basic Grayscale Image Box
CLINIVIEW Client AE supports the following DIMSE operations and notifications for the Basic Grayscale
Image Box SOP Class:
— N-Set
4.2.1.3.2.3.4 Basic Grayscale Image Box SOP Class Operations (N-SET)
TABLE 4-10: BASIC GRAYSCALE IMAGE BOX SOP CLASS N-SET REQUEST ATTRIBUTES
Magnification Type (2010,0060) CS n/a REPLICATE, BILINEAR,
CUBIC, NONE
Smoothing Type (2010,0080) CS n/a
Configuration (2010,0150) ST n/a
Information
Image Position (2020,0010) US 1 1..32
Polarity (2020,0020) CS NORMAL NORMAL, REVERSE
Requested Image (2020,0030) DS n/a
Size
Requested (2020,0040) CS n/a DECIMATE, CROP, FAIL
Decimate/Crop
Behavior
Basic Grayscale (2020,0110) SQ n/a
Image Sequence
Samples Per Pixel (0028,0002) US 1 1
Photometric (0028,0004) CS MONOCHROME2 MONOCHROME2
Interpretation
Rows (0028,0010) US n/a 1..32767
Columns (0028,0011) US n/a 1..32767
Bits Allocated (0028,0100) US n/a 8
Bits Stored (0028,0101) US n/a 8
High Bit (0028,0102) US n/a 7
23 / 56
CLINIVIEW 11
Pixel Presentation (0028,0103) US n/a 0

Pixel Data (7EE0,0010) OW n/a
Requested Image Size (2020,0030) is send optionally. When it is send its value is either the width of the
selected media, the width of the image or user selected width.
4.2.1.3.2.3.5 SOP Specific Conformance for the Basic Color Image Box SOP Class
CLINIVIEW Client AE supports the following DIMSE operations and notifications for the Basic Color
Image Box SOP Class:
— N-Set
4.2.1.3.2.3.5.1 Basic Color Image Box SOP Class Operations (N-SET)
TABLE 4-11: BASIC COLOR IMAGE BOX SOP CLASS N-SET REQUEST ATTRIBUTES
Magnification Type (2010,0060) CS n/a REPLICATE, BILINEAR,
CUBIC, NONE
Smoothing Type (2010,0080) CS n/a
Image Position (2020,0010) US 1 1..32
Polarity (2020,0020) CS NORMAL NORMAL, REVERSE
Requested (2020,0040) CS n/a DECIMATE, CROP, FAIL
Decimate/Crop
Behavior
Basic Color Image (2020,0111) SQ
Sequence
Samples Per Pixel (0028,0002) US 3 3
Photometric (0028,0004) CS RGB RGB
Interpretation
Planar Configuration (0028,0006) US 1 1
Rows (0028,0010) US n/a 1..32767
Columns (0028,0011) US n/a 1..32767
Bits Allocated (0028,0100) US n/a 8
Bits Stored (0028,0101) US n/a 8
High Bit (0028,0102) US n/a 7
Pixel Presentation (0028,0103) US n/a 0
Pixel Data (7EE0,0010) OW n/a
24 / 56
CLINIVIEW 11
4.2.1.3.2.3.6 SOP Specific Conformance for the Printer SOP Class

CLINIVIEW Client AE supports the following DIMSE operations and notifications for the Printer SOP
Class:
— N-Get
— N-Event-Report
4.2.1.3.2.3.6.1 Printer SOP Class Operations (N-GET)

CLINIVIEW ClientAE uses the Printer SOP Class N-GET operation to obtain information about the current
printer status.
4.2.1.3.2.3.6.2 Printer SOP Class Notifications (N-EVENT-REPORT)

CLINIVIEW Client AE is capable of receiving an N-EVENT-REPORT request at any time during an
association.
4.2.1.3.3 Activity – Query Worklist

Typical sequence is depicted below. There can be several C-FIND requests during single association,
depending on the configuration of the Matching Keys.
FIGURE 5: SEQUENCE OF ACTIVITY – WORKLIST
CLINIVIEW may be configured to poll the worklist provider for worklist data in intervals or only when the
operator needs the latest worklist.
25 / 56
CLINIVIEW 11
4.2.1.3.3.2 Proposed Presentation Contexts

CLINIVIEW Client AE proposes the Presentation Context shown in the following table:
TABLE 4-12: PRESENTATION CONTEXT TABLE OF WORKLIST

Negotiation
Modality Worklist 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Information Model – 5.1.4.31 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
FIND Explicit VR Big Endian 1.2.840.10008.1.2.2
4.2.1.3.3.3 SOP specific conformance for Worklist
TABLE 4-13: WORKLIST REQUEST IDENTIFIER

Module Attribute Name Tag VR B I R
SOP Common
Specific Character Set (0008,0005) CS x
Scheduled Procedure Step
Scheduled Procedure Step Sequence (0040,0100) SQ x
Scheduled Station AE Title (0040,0001) AE (S) (S,*) x
Scheduled Procedure Step Start Date (0040,0002) DA R (S, R) x
Scheduled Procedure Step Start (0040,0003) TM R R
Time
Modality (0008,0060) CS (S) (S) x
Scheduled Performing Physician’s (0040,0006) PN (S,*) x
Name
Scheduled Procedure Step (0040,0007) LO x
Description
Scheduled Station Name (0040,0010) SH x
Scheduled Procedure Step Location (0040,0011) SH x
Scheduled Protocol Code Sequence (0040,0008) SQ x
Pre-Medication (0040,0012) LO x
Scheduled Procedure Step ID (0040,0009) SH x
Requested Contrast Agent (0032,1070) LO x
26 / 56
CLINIVIEW 11
Module Attribute Name Tag VR B I R

Requested Procedure
Requested Procedure ID (0040,1001 SH (S) x
Requested Procedure Description (0032,1060) LO x
Requested Procedure Code (0032,1064) SQ x
Sequence
Study Instance UID (0020,000D) UI x
Referenced Study Sequence (0008,1110) SQ x
Requested Procedure Priority (0040,1003) SH x
Patient Transport Arrangements (0040,1004) LO x
Patient Identification
Patient's Name (0010,0010) PN (S,*) x
Patient ID (0010,0020) LO (S,*) x
Patient Demographic
Patient's Birth Date (0010,0030) DA x
Patient's Sex (0010,0040) CS x
Patient's Weight (0010,1030) DS x
Confidentiality Constraint on Patient (0040,3001) LO x
Data Description
Patient Medical
Patient State (0038,0500) LO x
Pregnancy Status (0010,21C0) US x
Medical Alerts (0010,2000) LO x
Contrast Allergies (0010,2110) LO x
Special Needs (0038,0050) LO x
Imaging Service Request
Accession Number (0008,0050) SH (S) x
Requesting Physician (0032,1032) PN x
Referring Physician’s Name (0008,0090) PN x
Visit Identification
Admission ID (0038,0010) LO x
Visit Status
Referenced Patient Sequence (0008,1120) SQ x
Current Patient Location (0038,0300) LO x
27 / 56
CLINIVIEW 11
The above table should be read as follows:

Module Name: The name of the associated module for supported worklist attributes.
Attribute Name: Attributes supported to build CLINIVIEW Worklist Request Identifier.
Tag: DICOM tag for this attribute.
VR: DICOM VR for this attribute.
B: Matching keys in the Broad Query -mode. An "S" will indicate that
CLINIVIEW will supply an attribute value for Single Value Matching,
an “R” will indicate Range Matching. Optional Matching keys are
indicated with "()".
I: Matching keys in the Interactive Query -mode.
R: Return keys. An "x" will indicate that CLINIVIEW will supply this
attribute as Return Key with zero length for Universal Matching, if the
attribute was not used for Single Value Matching, Range Matching or
Wild Card Matching.
In the Broad Query mode:

— It can be configured whether “Scheduled Station AE Title” is additionally supplied and if Modality
is set to DX, PX, IO, CR, XC, CT or any user specified value.
— If more than one Modality value is defined, a C-FIND request is sent for each of them.
— The operator can furthermore filter the results of C-FIND query, locally, using these attributes:
• Patient Name
• Patient ID
• Accession Number
• Requested Procedure ID
• Scheduled Performing Physician’s Name
In the Interactive Query mode:

— If more than one Modality value is defined, a C-FIND request is sent for each of them.
For default values see chapter 4.4.2.
4.2.1.3.4 Activity – Query/Retrieve

Typical sequence is depicted below.
28 / 56
CLINIVIEW 11
FIGURE 6: SEQUENCE OF ACTIVITY – QUERY/RETRIEVE
First a C-FIND message is sent to query for patient, study, series or image data. After this the operator can
either stop the activity or select data to be retrieved.
The retrieved data are requested from the archive by a C-MOVE message. The retrieving can be scheduled
to a selected date and time, to be performed after a specified delay or requested immediately.
Retry limit and retry interval can be configured for the retrieve tasks.
A graphical queue is provided, that shows a list of the scheduled retrieve tasks.

TABLE 4-14: PRESENTATION CONTEXT TABLE OF QUERY/RETRIEVE

Negotiation
Patient Root 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Query/Retrieve 5.1.4.1.2.1.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Information Model – Explicit VR Big Endian 1.2.840.10008.1.2.2
FIND
29 / 56
CLINIVIEW 11
Patient Root 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None

MOVE
Study Root 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
FIND
Study Root 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
MOVE
4.2.1.3.4.3 SOP specific conformance
The keys used in the C-FIND requests, by default, are shown in the tables below:
TABLE 4-15: PATIENT ROOT REQUEST IDENTIFIER

Module Attribute Name Tag VR Types of Available in
Matching the GUI
Patient level
Patient Name 0010,0010 PN S,*,U Yes
Patient ID 0010,0020 LO S,*,U Yes
Study level
Study Date 0008,0020 DA S,U Yes
Study ID 0020,0010 SH S,*,U Yes
Accession Number 0008,0050 SH S,*,U Yes
Study Instance UID 0020,000D UI S,U No
Series level
Study Date 0008,0020 DA S,U Yes
Modality 0008,0060 CS S,*,U Yes
Series Number 0020,0011 IS S,*,U Yes
Series Instance UID 0020,000E UI S,U No
Image level
30 / 56
CLINIVIEW 11

Matching the GUI
Patient level
Instance Number 0020,0013 IS S,*,U No
SOP Instance UID 0008,0016 UI S,U No
TABLE 4-16: STUDY ROOT REQUEST IDENTIFIER

Matching the GUI
Study level
Study Date 0008,0020 DA S,*,U Yes
Study ID 0020,0010 SH S,*,U No
Accession Number 0008,0050 SH S,*,U Yes
Study Instance UID 0020,000D UI S, U No
Series level
Study Date 0008,0020 DA S,*,U Yes
Study Instance UID 0020,000D UI S,U No
Modality 0008,0060 CS S,*,U Yes
Series Number 0020,0011 IS S,*,U Yes
Image level
Instance Number 0020,0013 IS S,*,U No
SOP Instance UID 0008,0016 UI S,U No
Types of Matching:
S Single Value Matching
* Wild Card Matching
U Universal Matching
R Range Matching
Additional keys can be added by the operator.
31 / 56
CLINIVIEW 11
CLINIVIEW AE does not support relational queries. CLINIVIEW AE does not support extended negotiation
of combined date-time matching or fuzzy semantic matching of person names.
4.2.1.3.5 Activity – Send Verification

CLINIVIEW Client AE initiates Associations for the purpose of verifying a DICOM connection.
4.2.1.3.5.2 Proposed presentation context

CLINIVIEW Client AE is capable of proposing the Presentation Contexts as shown in the following table:
TABLE 4-17: PRESENTATION CONTEXT TABLE OF VERIFICATION SCU

Negotiation
Verification 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
1.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
4.2.1.3.5.3 SOP specific conformance

CLINIVIEW Client AE provides standard conformance to the DICOM Verification Service Class as an SCU.
4.2.1.4 Association Acceptance Policy

CLINIVIEW Client AE does not accept any associations.
4.2.2 CLINIVIEW Storage SCP AE
4.2.2.1 SOP Classes

Storage SCP AE provides standard conformance to the following Service Object Pair (SOP) Classes.

Verification
Verification SOP Class 1.2.840.10008.1.1 No Yes
Storage
Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1 No Yes
Digital X-ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.1 No Yes
Digital X-ray Image Storage – For Processing 1.2.840.10008.5.1.4.1.1.1.1.1 No Yes
Digital Intra-oral X-ray Image Storage – For 1.2.840.10008.5.1.4.1.1.1.3 No Yes
Presentation
32 / 56
CLINIVIEW 11
Digital Intra-oral X-ray Image Storage – For 1.2.840.10008.5.1.4.1.1.1.3.1 No Yes

Processing
CT Image Storage 1.2.840.10008.5.1.4.1.1.2 No Yes
Enhanced CT Image Storage 1.2.840.10008.5.1.4.1.1.2.1 No Yes
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 No Yes
Multi-frame Grayscale Byte 1.2.840.10008.5.1.4.1.1.7.2 No Yes
Storage
Multi-frame Grayscale Word 1.2.840.10008.5.1.4.1.1.7.3 No Yes
Storage
Multi-frame True Color 1.2.840.10008.5.1.4.1.1.7.4 No Yes
Storage
VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 No Yes

Same as in chapter 4.2.1.2 Association Policies.

CLINIVIEW Storage SCP AE does not initiate associations.
4.2.2.4.1 Activity – Receive Storage Request
4.2.2.4.1.1 Description and sequencing of Activities

FIGURE 7: SEQUENCE OF ACTIVITY – STORAGE SCP
Associations are accepted in order to receive images from remote AEs. The received images are stored in
CLINIVIEW database.
33 / 56
CLINIVIEW 11
4.2.2.4.1.2 Accepted Presentation Contexts

CLINIVIEW AE will accept Presentation Contexts as shown in the table below.
TABLE 4-19: PRESENTATION CONTEXT TABLE OF STORAGE SCP

Negotiation
Computed Radiography 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
Digital X-Ray Image 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
Storage – For 5.1.4.1.1.1.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Presentation Explicit VR Big Endian 1.2.840.10008.1.2.2
Digital X-Ray Image 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
Storage – For 5.1.4.1.1.1.1.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Processing Explicit VR Big Endian 1.2.840.10008.1.2.2
Digital Intra-oral X- 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
Ray Image Storage - 5.1.4.1.1.1.3 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
For Presentation Explicit VR Big Endian 1.2.840.10008.1.2.2
Digital Intra-oral X- 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
Ray Image Storage - 5.1.4.1.1.1.3.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
For Processing Explicit VR Big Endian 1.2.840.10008.1.2.2
CT Image Storage 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
5.1.4.1.1.2 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Enhanced CT Image 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
Storage 5.1.4.1.1.2.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Secondary Capture 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
Multi-frame Grayscale 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
Byte 5.1.4.1.1.7.2 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Image
Storage
Multi-frame Grayscale 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
Word 5.1.4.1.1.7.3 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Image
Storage
Multi-frame True Color 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
Secondary Capture 5.1.4.1.1.7.4 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
Image Explicit VR Big Endian 1.2.840.10008.1.2.2
Storage
VL Photographic Image 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
Storage 5.1.4.1.1.77.1. Implicit VR Little Endian, 1.2.840.10008.1.2.1,
4 Explicit VR Big Endian 1.2.840.10008.1.2.2
34 / 56
CLINIVIEW 11

To be defined.
4.2.2.4.2 Activity – Receive Verification

CLINIVIEW AE accepts Associations for the purpose of verifying a DICOM connection.
TABLE 4-20: PRESENTATION CONTEXT TABLE OF VERIFICATION SCP

Negotiation
Verification 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCP None
1.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,

CLINIVIEW AE provides standard conformance to the Verification SOP Class as an SCP. If the C-ECHO request
was successfully received, a 0000 (Success) status code will be returned in the C-ECHO response.
4.2.3 CLINIVIEW Storage SCU AE
4.2.3.1 SOP Classes

Storage SCU AE provides standard conformance to the following Service Object Pair (SOP) Classes.

Verification
Verification SOP Class 1.2.840.10008.1.1 Yes Yes
Storage
Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1 Yes No
Digital X-ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.1 Yes No
Digital X-ray Image Storage – For Processing 1.2.840.10008.5.1.4.1.1.1.1.1 Yes No
Digital Intra-oral X-ray Image Storage – For 1.2.840.10008.5.1.4.1.1.1.3 Yes No
Presentation
Digital Intra-oral X-ray Image Storage – For 1.2.840.10008.5.1.4.1.1.1.3.1 Yes No
Processing
35 / 56
CLINIVIEW 11
CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Yes No

Enhanced CT Image Storage 1.2.840.10008.5.1.4.1.1.2.1 Yes No
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Yes No
Multi-frame Grayscale Byte 1.2.840.10008.5.1.4.1.1.7.2 Yes No
Storage
Multi-frame Grayscale Word 1.2.840.10008.5.1.4.1.1.7.3 Yes No
Storage
Multi-frame True Color 1.2.840.10008.5.1.4.1.1.7.4 Yes No
Storage
VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 Yes No
Storage Commitment SCU
Storage Commitment Push Model 1.2.840.10008.1.20.1 Yes No

Same as in chapter 4.2.1.2 Association Policies.
4.2.3.3.1 Activity – Send Store Request

The Storage SCU activity of Storage SCU AE is used as an alternative for the Storage SCU activity of Client
AE. See chapter 4.2.1.3.1 Activity – Send Store Request. The same behavior applies to this activity.
4.2.3.3.2 Activity – Requesting Storage Commitment

The sequence of interactions is shown in the sequence diagram below:
36 / 56
CLINIVIEW 11
Application Entity PACS
Open association
N-ACTION
N-EVENT_REPORT
Close association
FIGURE 8: SEQUENCE OF ACTIVITY – REQUESTING STORAGE COMMITMENT
The N-ACTION message is sent automatically, after an image is stored, after a configurable time period. The
AE then waits for a N-EVENT-REPORT from the SCP during the same association. This wait time can be
configured. If the N-EVENT-REPORT message is not received, the association is closed, and the Storage
Commitment SCP is expected to initiate another association for sending the N-EVENT-REPORT, see
4.2.3.4.1 Activity – Receive Storage Commitment Result.
The status of the Storage Commitment is displayed for the operator: commitment pending, waiting for
storage commitment retry, committed or storage commitment failed.
The request can be resent or aborted by the user.

CLINIVIEW Storage SCU AE is capable of proposing the Presentation Contexts shown in the following
table:
TABLE 4-22: PRESENTATION CONTEXT TABLE OF REQUESTING STORAGE COMMITMENT

Negotiation
Storage Commitment 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Push Model 1.20.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,

The supported operations are described below.
37 / 56
CLINIVIEW 11
4.2.3.3.2.3.1 Storage Commitment Operations (N-ACTION)

The storage Commitment request can be configured to be sent automatically, after the storing of an image.
Only one SOP Instance is included in one request. The request can be sent for all the same SOP Classes as
can be stored, see 4.2.3.3.1 Activity – Send Store Request.
The request can be configured to be resent until a successful N-ACTION Response or N-EVENT-REPORT
with Event Type ID equal to 1 is received. The maximum retry limit and retry interval can be configured. A
new Transaction UID is used for the retries.
The request can also be resent manually by the operator.
The Storage Media File-Set ID and UID attributes are not supported.
4.2.3.3.2.3.2 Storage Commitment Operations (N-EVENT-REPORT)
Event Type Name Event Type ID Behavior
Storage 1 The References SOP Instances under References SOP Sequence

Commitment (0008,1199) are considered as 'Committed' in the CLINIVIEW database.
Request Successful CLINIVIEW can be configured to automatically delete these images
immediately or after a delay of either 12, 24 or 48 hours. A log entry is
written of each deleted image.
Storage 2 The References SOP Instances under References SOP Sequence

Commitment (0008,1199) are treated the same way as in the success case (Event Type
Request Complete - 1). The referenced SOP Instances under Failed SOP Sequence
Failures Exist (0008,1198) are considered as 'Commitment failed''. These images will
not be deleted. CLINIVIEW can be configured to automatically resend
the Commitment Request (N-ACTION), after Event Type ID equal to 2
is received. The maximum retry limit and retry interval can be
configured. The operator can also manually resend the Commitment
Request.
4.2.3.3.3 Activity – Send Verification

Same as in 4.2.1.3.5 Activity – Send Verification.
38 / 56
CLINIVIEW 11
4.2.3.4.1 Activity – Receive Storage Commitment Result

Application Entity PACS
Open association
N-EVENT_REPORT
Close association
FIGURE 9: SEQUENCE OF ACTIVITY – RECEIVING STORAGE COMMITMENT RESULT
CLINIVIEW Storage SCU AE waits for associations from the remote AE, when the storage commitment
result (N-EVENT-REPORT) was not received during the same association as the Storage Commitment
request (N-ACTION).
The status of the storage commitment is displayed to the operator: waiting for storage commitment report,
storage commitment error or committed.

CLINIVIEW Storage SCU AE will accept Presentation Contexts as shown in the table below.
TABLE 4-23: PRESENTATION CONTEXT TABLE OF RECEIVING STORAGE COMMITMENT

Negotiation
Storage Commitment 1.2.840.10008. Explicit VR Little Endian, 1.2.840.10008.1.2, SCU None
Push Model 1.20.1 Implicit VR Little Endian, 1.2.840.10008.1.2.1,
39 / 56
CLINIVIEW 11

CLINIVIEW Storage SCU AE waits for association for the Storage Commitment Result message (N-
EVENT-REPORT) after each Storage Commitment Request (N-ACTION), to which it did not receive the
result message already within the same association.
4.2.3.4.1.3.1 Storage Commitment Operations (N-EVENT-REPORT)

Same as in 4.2.3.3.2.3.2 Storage Commitment Operations (N-EVENT-REPORT).
4.2.3.4.2 Activity – Receive Verification

Same as in 4.2.2.4.2 Activity – Receive Verification.
4.3 NETWORK INTERFACES
4.3.1 Physical Network Interface

The DICOM Upper Layer Protocol is supported using TCP/IP, as specified in Part 8 of the DICOM Standard
4.4 CONFIGURATION
4.4.1 AE title / presentation address mapping
4.4.1.1 Local AE Titles

CLINIVIEW uses the AE Titles configured via the settings dialog of CLINIVIEW software. An AE Title can
be configured for all of the AEs: Client AE, Storage SCP AE and Storage SCU AE. All of these local AE
Titles can be configured independently of each other. Identical AE Titles should not be used for the Storage
SCP AE and Storage SCU AE. Likewise, identical TCP/IP ports should not be used for them.
TABLE 4-24: AE TITLE CONFIGURATION TABLE

Application Entity Default AE Title Default TCP/IP Port
CLINIVIEW Client AE CV_DICOM n/a
CLINIVIEW Storage CV_DICOM 105
SCP AE
CLINIVIEW Storage no default value 106
SCU AE
4.4.1.2 Remote AE Title/ Presentation Address Mapping

The AE Titles, host names and port numbers of remote applications are configured using the settings dialog
of CLINIVIEW software.
40 / 56
CLINIVIEW 11
4.4.1.2.1 Worklist SCP

One Worklist SCP can be defined.
These parameters must be defined for it: AE title, IP address and port.
4.4.1.2.2 Storage SCP

Several Storage SCPs can be defined. One of them is always a default Storage SCP, which is used when the
auto storage feature of CLINIVIEW is being used.
For each Storage SCP these parameters must be defined: destination name, AE title, IP address and port.
4.4.1.2.3 Storage Commitment SCP

Corresponding to each Storage SCP, optionally one Storage Commitment SCP can be defined, consisting of
these parameters: AE title, IP address and port.
4.4.1.2.4 Print SCP

Several Print SCPs can be defined.
For each Print SCP these parameters must be defined: printer name, AE title, IP address and port.
4.4.1.2.5 QueryRetrieve (C-FIND SCP and Storage SCU)

One Query/Retrieve SCP can be defined.
These parameters must be defined for it: AE title, IP address and port.
An AE title for the Move Service must be defined (move destination).
4.4.2 Parameters
TABLE 4-25: CONFIGURATION PARAMETERS TABLE

Parameter Configurable Default Value
(Yes/No)
Worklist SCU Parameters
Maximum PDU size the AE can receive and Yes 28672 bytes
send
Process priority Yes Below normal
SCP timeout Yes 3s
Verify Timeout Yes 15 s
Association request timeout Yes 30 s
Association response timeout Yes 15 s
Connection timeout Yes 15 s
Release timeout Yes 15 s
Write timeout Yes 15 s
41 / 56
CLINIVIEW 11

(Yes/No)
Inactivity timeout Yes 15 s
Work buffer Yes 28672 byes
Send buffer Yes 29696 byes
Receive buffer Yes 29696 byes
Refresh Timeout Yes 30 s
Search method Yes Refresh from worklist
SCP
Number of simultaneous associations by No 1
Service
Polling interval Yes 60 s
Modalities Yes DX, PX and IO
Scheduled Station AE Title Yes <empty>
Search for worklist items by date, days Yes 0 days
before today
Search for worklist items by date, days after Yes 0 days
today
Copy Scheduled Procedure Step Description Yes Disabled
to Study Description
Copy Requested Procedure Description to Yes Disabled
Study Description
Study date/time Yes Use current date and
time.
Storage SCU Parameters
send
Retry count due to failed storage Yes 2
Retry interval due to failed storage Yes 30
Service
42 / 56
CLINIVIEW 11

(Yes/No)
SOP Classes (see also 4.2.1.3.1.3 SOP
Specific Conformance):
panoramic images Yes Digital X-Ray Image
Storage For processing
(PX)
cephalometric images Yes Digital X-Ray Image
Storage For processing
(DX)
intra-oral images Yes Digital Intra-oral X-Ray
Image Storage For
processing
photographs Yes VL Photographic Image
Storage
CB3D Yes Enhanced CT Image
Storage
CB3D Scout Yes Digital X-Ray Image
Storage For Processing
(DX)
Storage Commitment SCU Parameters
Retry count due to failed request Yes 2
Retry interval due to failed request Yes 30 min
Wait for Commitment Report in N-ACTION Yes 2 sec
association
Wait time for storage commitment Yes 30 min
Delay between Storage and Commitment Yes 60 min
Print SCU Parameters
send
Service
43 / 56
CLINIVIEW 11

(Yes/No)
Basic grayscale print management and/or Yes Basic Grayscale Print
basic color print management Management
Query / Retrieve Parameters
send
Query Model Yes Patient
Scheduled retrieve task retry limit Yes 2
Scheduler retrieve task retry interval Yes 30
Service
Storage SCP Parameters
send
Service
The following retired tags can be selected for use:
44 / 56
CLINIVIEW 11
— initiator name of command messages

— receiver name of command messages
— length to end in command messages
— recognition code in command messages
— message id in command response messages
— priority in command response messages
These are not used by default.
45 / 56
CLINIVIEW 11
5 MEDIA INTERCHANGE
This section of the DICOM conformance statement specifies the CLINIVIEW compliance to DICOM
requirements for Media Interchange. It details the DICOM Media Storage Application Profiles and roles
which are supported by this product.
5.1 IMPLEMENTATION MODEL
5.1.1 Application Data Flow Diagram
FIGURE 10: MEDIA STORAGE APPLICATION DATA FLOW DIAGRAM
CLINIVIEW Media AE displays the contents of DICOM Storage Medium and reads the images saving them
to local database.
CLINIVIEW Media AE writes data from the local database to the DICOM Storage Medium.
5.1.2 Functional Definitions of AEs

Using the Import - DICOMDIR command of CLINIVIEW, the operator can browse to the location of the
DICOM Storage Media, and view the patients, studies and images it contains. The operator can then select
the patients, studies and images for importing. The data is then saved to the local database and available for
viewing and editing.
Using the Export - DICOMDIR command of CLINIVIEW, the operator can choose the patients from the
local database and select their studies and images for exporting. The data is then saved to the operator
defined directory on the local hard drive, from where the data can be stored to a disc using appropriate tools.
Writing directly to CD or DVD media is not supported by this application entity.
46 / 56
CLINIVIEW 11
For importing and exporting individual image files, please refer to the CLINIVIEW user manual.
5.1.3 Sequencing of Real-World Activities
No other activity can be initiated until a prior activity has been completed.
Display Directory activity is needed before Read Media can be started.
5.1.4 File Meta Information Options

The implementation information written to the File Meta Header in each file is:
CLINIVIEW Implementation UID 1.2.840.113999.42.6.0
CLINIVIEW Implementation Version Name CV_102
47 / 56
CLINIVIEW 11
5.2 AE SPECIFICATIONS
5.2.1 Application Entity Specification of CLINIVIEW Media AE

The CLINIVIEW Media AE provides standard conformance to the Media Storage Service Class. Supported
Application Profiles, Real World Activities and their Roles are listed in table below.
TABLE 5-1: APPLICATION PROFILES, ACTIVITIES AND ROLES

Supported Real World Role SC Option
Application Profile Activity
STD-GEN-CD Display Directory FSR Interchange
STD-GEN-DVD-RAM
STD-GEN-CD Create Media FSC Interchange
STD-GEN-DVD-RAM
STD-GEN-CD Read Media FSR Interchange

STD-GEN-DVD-RAM
5.2.1.1 File Meta Information for the application entity

When File Meta Information is created the CV_102 source AE Title is used. Private information is not used
in the application profile.
5.2.1.2 Real-World Activities
5.2.1.2.1 Activity – Display Directory

CLINIVIEW Media AE acts as an FSR when requested to view SOP instances from DICOM storage media.
The CLINIVIEW operator inserts the media in the appropriate removable media device and invokes the
media directory reading operation. Patient, their study and image related information is visible in
CLINIVIEW software user interface.
5.2.1.2.1.1 Media Storage Application Profiles

The application entity supports the application profiles specified in chapter: 5.2.1.
48 / 56
CLINIVIEW 11
5.2.1.2.1.1.1 Options
The application entity supports the SOP Classes and Transfer Syntaxes listed in the table below:
TABLE 5-2: PRESENTATION CONTEXT TABLE OF DISPLAY DIRECTORY

Abstract Syntax Transfer Syntax
SOP Class SOP Class UID
Media Storage Directory Storage 1.2.840.10008.1.3.10 Explicit VR
Little Endian
Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1 Explicit VR
Little Endian
Digital X-Ray Image Storage – For 1.2.840.10008.5.1.4.1.1.1.1 Explicit VR
Presentation Little Endian
Digital X-Ray Image Storage – For 1.2.840.10008.5.1.4.1.1.1.1.1 Explicit VR
Processing Little Endian
Digital Intra-oral X-Ray Image Storage 1.2.840.10008.5.1.4.1.1.1.3 Explicit VR
- For Presentation Little Endian
Digital Intra-oral X-Ray Image Storage 1.2.840.10008.5.1.4.1.1.1.3.1 Explicit VR
- For Processing Little Endian
CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Explicit VR
Little Endian
Enhanced CT Image Storage 1.2.840.10008.5.1.4.1.1.2.1 Explicit VR
Little Endian
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Explicit VR
Little Endian
Multi-frame Grayscale Byte 1.2.840.10008.5.1.4.1.1.7.2 Explicit VR
Secondary Capture Image Little Endian
Storage
Multi-frame Grayscale Word 1.2.840.10008.5.1.4.1.1.7.3 Explicit VR
Storage
Multi-frame True Color 1.2.840.10008.5.1.4.1.1.7.4 Explicit VR
Storage
VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 Explicit VR
Little Endian
5.2.1.2.2 Activity – Read Media

CLINIVIEW Media AE acts as an FSR when requested to read SOP instances from DICOM storage media.
The CLINIVIEW operator inserts the media in the appropriate removable media device and invokes the
media directory reading operation. Patient, their study and image related information is visible in
CLINIVIEW software user interface. After the operator selects the information from the CLINIVIEW
software user interface, the information is stored in local CLINIVIEW database.

See application profile table in chapter: 5.2.1.
49 / 56
CLINIVIEW 11
5.2.1.2.2.1.1 Options
The application entity supports the same SOP Classes and Transfer Syntaxes as the Display Activity, see
Table 5-2.
5.2.1.2.3 Activity – Create Media

CLINIVIEW Media AE acts as an FSC when requested to export SOP instances from local database to
DICOM storage medium.
CLINIVIEW operator selects from the CLINIVIEW software user interface image to be stored and invokes
the export operation. The images are written into a single file set on a local hard drive. If the DICOM file set
already contains data, CLINIVIEW software warns the user about it.
Then the operator uses a separate media writing application, to create the physical volume on CD or DVD
disc. The operator can then define a label for the volume.

See application profile table in chapter: 5.2.1.
5.2.1.2.3.1.1 Options
The application entity supports the same SOP Classes and Transfer Syntaxes as the Display Activity, see
Table 5-2.
The abstract syntax used, is based on the image type in CliniView, and can be configured as follows:
— Panoramic and cephalometric images:
o Digital X-Ray Image Storage - either For Presentation or For Processing, depending on
the user setting.
— Intraoral images:
o Digital Intra-oral X-Ray Image Storage - either For Presentation or For Processing,
depending on the user setting.
the user setting.
— Cone Beam 3D images:
o CT Image Storage
o Enhanced CT Image Storage
— Cone Beam 3D Scout images:
the user setting
— Photographic images:
o VL Photographic Image Storage
o Secondary Capture Image Storage
o Multi-frame Grayscale Byte Secondary Capture Image Storage
o Multi-frame Grayscale Word Secondary Capture Image Storage
o Multi-frame True Color Secondary Capture Image Storage
Overlay graphics drawn on the image are saved using the Overlay plane module, DICOM tags 6000,xxxx.
This includes e.g. lines and texts, but does not include ROIs or pseudo-colorization.
5.3 AUGMENTED AND PRIVATE APPLICATION PROFILES

None supported.
50 / 56
CLINIVIEW 11
5.4 MEDIA CONFIGURATION

It can be configured, which SOP Class is used for writing images to media, see 5.2.1.2.3.1.1.
51 / 56
CLINIVIEW 11
6 SUPPORT OF CHARACTER SETS
This implementation supports the following extended character set:

— ISO-IR 6 - default character set
— ISO-IR 13 - Japanese, JIS X 0201: Katakana
— ISO-IR 100 - Latin alphabet No. 1, supplementary set
— ISO-IR 144 - Cyrillic, supplementary set
— ISO_IR 192 - Unicode in UTF-8
52 / 56
CLINIVIEW 11
7 SECURITY PROFILES
CLINIVIEW does not conform to any defined DICOM Security Profiles.
It is assumed that the product is used within a secured environment. It is assumed that a secured environment
includes at a minimum:
— Firewall or router protections to ensure that only approved external hosts have network access to the
product.
— Firewall or router protections to ensure that the product only has network access to approved external
hosts and services.
— Any communications with external hosts and services outside the locally secured environment use
appropriate secure network channels (such as a Virtual Private Network (VPN))
53 / 56
CLINIVIEW 11
8 ANNEXES
8.1 IOD CONTENTS

To be defined.
8.2 DATA DICTIONARY AND PRIVATE ATTRIBUTES

The private attributes added to created SOP instances are listed below:
TABLE 8-1: PRIVATE ATTRIBUTES

Tag Name VR VM
000D,0010 INSTRU_PRIVATE_IDENT_CODE LO 1
000D,1000 ImageXmlData OB 1
No private SOP Classes or Transfer Syntaxes are used.
8.3 CODED TERMINOLOGY AND TEMPLATES

None supported.
8.4 GRAYSCALE IMAGE CONSISTENCY

CLINIVIEW does not support the Grayscale Standard Display Function
8.5 STANDARD EXTENDED/SPECIALIZED/PRIVATE SOP CLASSES

CLINIVIEW does not claim conformance to any Extended, Specialized or Private SOP Classes.
In accordance with DIN 6862-2 the following DICOM tags are missing because they are either technically
not available or not applicable:
Tag Name
0008,2112 Source Image Sequence
0008,1140 Referenced Image Sequence
0018,7050 Filter Material
0018,1405 Relative X-Ray Exposure
0018,1411 Exposure Index
54 / 56
CLINIVIEW 11
0018,1412 Target Exposure Index
0018,1413 Deviation Index
0040,0302 Entrance Dose
0018,1191 Anode Target Material
0018,11A0 Body Part Thickness
0040,0300 Total Time of Fluoroscopy
0040,0301 Total Number of Exposures
0018,1155 Radiation Setting
0008,9410 Referenced Other Plane Sequence
0028,6100 Mask Subtraction Sequence
0028,6101 Mask Operation
0028,6102 Applicable Frame Range
0028,6110 Mask Frame Numbers
0028,1090 Recommended Viewing Mode
0018,1134 Table Motion
0018,1135 Table Vertical Increment
0018,1137 Table Longitudinal Increment
0018,1136 Table Lateral Increment
0018,1500 Positioner Motion
0018,1520 Positioner Primary Angle Increment
0018,1521 Positioner Secondary Angle Increment
0018,0040 Cine Rate
0018,9302 Acquisition Type
0018,9346 CTDI Phantom Type Code Sequence
0018,9334 Fluoroscopy Flag
0018,9303 Tube Angle
0018,9327 Table Position
55 / 56
CLINIVIEW 11
0018,9318 Reconstruction Target Center (Patient)
0018,9360 CT Additional X-Ray Source Sequence
8.6 PRIVATE TRANSFER SYNTAXES

CLINIVIEW does not employ any Private Transfer Syntaxes.
56 / 56

CLINIVIEW 11 DICOM Conformance Statement R3

Uploaded by

Copyright:

Available Formats

You might also like

CLINIVIEW 11 DICOM Conformance Statement R3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CLINIVIEW 11 DICOM Conformance Statement R3

Uploaded by

Copyright:

Available Formats

CLINIVIEW 11

Instrumentarium Dental DICOM CONFORMANCE STATEMENT

Copyright © 2021 Instrumentarium Dental, PaloDEx Group Oy

1 CONFORMANCE STATEMENT OVERVIEW

CLINIVIEW is a digital dental X-ray imaging system:

TABLE 1-1: NETWORK SERVICES

Secondary Capture Image Storage Yes Yes

SOP Classes User of Service (SCU) Provider of Service

TABLE 1-2: MEDIA SERVICES

1 CONFORMANCE STATEMENT OVERVIEW ............................................................................................................ 2

2 TABLE OF CONTENTS .................................................................................................................................................. 4

7 SECURITY PROFILES .................................................................................................................................................. 53

Section 6 Supported Character Sets.

3.2 REVISION HISTORY

Revision Date Reason for Change Pages

001 02.03.2004 First draft 25

002 15.03.2004 Second 24

003 22.03.2004 Third 30

004 23.03.2004 Fourth 30

005 16.04.2004 Comment fixes 30

006 6.5.2004 Comment fixes 32

007 27.10.2005 Final 30

008 03.07.2007 Minor improvements 30

009 26.02.2008 VT features added. Media Storage Application profile 32

010 15.4.2008 Changes in document structure. 30

011 13.6.2008 Major editing, chapters rearranged, sequence diagrams 45

012 18.9.2008 Document finalized for CliniView 8.1. 46

013 30.9.2009 New features added: Storage Commitment SCU, 56

014 9.12.2010 N-Action of printing corrected. Added info of overlay 55

015 29.3.2011 Enhanced CT Image Storage SOP Class added. 55

016 6.7.2016 Updated versions for CliniView 11.1 55

017 8.1.2020 Added information related to DIN 6862-2 to chapter 8.5. 56

018 18.2.2021 Added default AE titles to chapter 4.4.1. Added ISO IR 56

019 3.11.2021 Updated version to CliniView 11 56

3.4 SCOPE AND FIELD OF APPLICATION

CLINIVIEW User Manual, available on the product DVD-ROM.

CLINIVIEW Installation Manual, available on the product DVD-ROM.

3.7 TERMS AND DEFINITIONS

Association – a network communication channel set up between Application Entities.

of data to be exchanged and how that data will be encoded.

Service/Object Pair (SOP) Instance – an information object; a specific occurrence of information

4.1 IMPLEMENTATION MODEL

4.1.1 Application Data Flow Diagram

FIGURE 4-1: APPLICATION DATA FLOW DIAGRAM

4.1.2 Functional Definition of AE's

4.1.2.1 Functional Definition of CLINIVIEW Client AE

The following services are implemented in the Client AE:

4.1.2.2 Functional Definition of CLINIVIEW Storage SCP AE

4.1.2.3 Functional Definition of CLINIVIEW Storage SCU AE

Association requests are send for the following services:

4.1.3 Sequencing of Real World Activities

FIGURE 4-2: SEQUENCE DIAGRAM

4.2.1 CLINIVIEW Client AE

4.2.1.1 SOP Classes

TABLE 4-1: SOP CLASSES FOR CLINIVIEW APPLICATION ENTITY

Patient Root Query/Retrieve Information Model – 1.2.840.10008.5.1.4.1.2.1.2 Yes No

4.2.1.2 Association Policies

TABLE 4-2: DICOM APPLICATION CONTEXT