View
20
Download
0
Category
Preview:
Citation preview
DE32-DCM-1.0
2015-12-15
DentalEye 3.2
DICOM conformance statement
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
1 (40)
Table of contents
1. INTRODUCTION ............................................................................................................................ 4
1.1. DentalEye Enterprise Application .............................................................................................. 4
1.2. About this Document .................................................................................................................. 4
1.3. Integration and Validation .......................................................................................................... 4
1.4. Future Evolution ......................................................................................................................... 5
1.5. Sources for this Document .......................................................................................................... 5
2. IMPLEMENTATION MODEL ........................................................................................................ 5
2.1. Application Data Flow Diagram ................................................................................................. 5
2.2. Receive Images ........................................................................................................................... 7
2.3. Query to/from Other Devices ..................................................................................................... 7
2.4. Retrieve Images from Other Devices .......................................................................................... 7
2.5. Transmit Images ......................................................................................................................... 7
2.6. Storage Commitment .................................................................................................................. 7
2.7. Print to Other Devices ................................................................................................................ 7
2.8. Query Modality Worklist ............................................................................................................ 7
2.9. Functional Definitions of AEs .................................................................................................... 8
2.9.1. DentalEye Enterprise .............................................................................................................. 8
2.10. Sequencing of Real-World Activities ......................................................................................... 9
3. AE SPECIFICATIONS .................................................................................................................. 10
3.1. DentalEye Enterprise Specifications......................................................................................... 10
3.1.1. Association Establishment Policies ...................................................................................... 12
3.1.2. Association Initiated by Real-World Activity ...................................................................... 13
3.1.3. Association Acceptance Policy ............................................................................................ 15
4. COMMUNICATIONS PROFILES ................................................................................................ 34
4.1. Supported Communication Stacks ............................................................................................ 34
4.2. TCP/IP Stack ............................................................................................................................ 34
4.3. Physical Media Support ............................................................................................................ 34
5. EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS ....................................................... 35
6. Media Interchange .......................................................................................................................... 35
6.1. Implementation Model .............................................................................................................. 35
6.1.1. Application Data Flow Diagram .......................................................................................... 35
6.1.2. Functional Definitions of AEs .............................................................................................. 35
6.1.3. Sequencing of Real World Activities ................................................................................... 36
6.1.4. File Meta Information Options ............................................................................................. 36
6.2. AE Specifications ..................................................................................................................... 36
6.2.1. DentalEye Enterprise AE ..................................................................................................... 36
6.3. Augmented and Private Application Profiles ........................................................................... 37
6.3.1. Augmented Application Profiles .......................................................................................... 37
6.3.2. Private Application Profiles ................................................................................................. 37
6.4. Extensions, Specializations and Privatizations of SOP Classes and Transfer Syntaxes ........... 37
6.5. Media Configuration ................................................................................................................. 37
6.6. Character Sets ........................................................................................................................... 37
6.7. Codes and Controlled Terminology .......................................................................................... 38
7. CONFIGURATION ........................................................................................................................ 38
8. SUPPORT FOR EXTENDED CHARACTER SETS ..................................................................... 38
9. CODES AND CONTROLLED TERMINOLOGY ........................................................................ 38
10. SECURITY ..................................................................................................................................... 38
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
2 (40)
10.1. ASSOCIATION LEVEL SECURITY ...................................................................................... 38
10.2. APPLICATION LEVEL SECURITY ...................................................................................... 38
11. ACRONYMS AND ABBREVIATIONS ....................................................................................... 40
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
3 (40)
Labelling and symbols
DentalEye 3.2 is a medical device, CE-marked according to the directive
93/42/EEC.
Manufacturer:
DentalEye AB
Kavallerivägen 30
SE-174 58 SUNDBYBERG
SVERIGE
Tel: +46 (0)8-621 07 00
Fax: +46 (0)8-621 07 55
Email: info@dentaleye.com
www.dentaleye.com
The date of manufacture is shown in the software.
Read all instructions before use!
The catalog number is DentalEye 3.2.
Current product version is shown in the software (DentalEye 3.2.x).
This version of the installation instructions is valid for product versions
from DentalEye 3.2.1.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
4 (40)
1. INTRODUCTION
1.1. DentalEye Enterprise Application
DentalEye Enterprise is a multi-functional application for dental practice and digital radiography. It can
be configured to be an acquisition/modality station where it can capture images directly from digital
sensors or phosphorus plate scanners.
The application also has the support for importing JPEG, TIFF, BMP and other common raster formats
plus capturing images from video capture devices and scanned films or images from TWAIN devices. It
can create a DICOM dataset from the captured images by associating patient identification information
passed to it, either via user input or a patient management system through different interfaces it exposes
or a user querying a Modality Worklist server and selecting a scheduled procedure. The type of IOD class
it uses to create DICOM is configurable and is based on the selected template. The application can also be
configured to store a series of images to multiple DICOM servers using DICOM C-STORE services for
this process. It can also be configured as a diagnostic/review station where users can query and retrieve
images from DICOM storage servers or print selected images or a series of images to DICOM Print
Servers.
DentalEye Enterprise can also import images from DICOM Media or stand-alone DICOM files and can
export selected images or a series of images of a patient as DICOM Part 10 Media format.
The DentalEye Enterprise communication is based on the DICOM v3.0 standard in order to communicate
with any DICOM v3.0 compliant products, e.g. a DICOM Storage server or a DICOM Print Server.
DentalEye Enterprise functions generally as a DICOM service class user, but other stations can store
DICOM storage instances/images to it via the C-STORE service. The communication protocol uses
TCP/IP as the transport layer.
1.2. About this Document
This document is a standard DICOM Conformance Statement for the DentalEye Enterprise application,
and its purpose is to outline its conformance to different DICOM services. It is assumed that the reader of
this document is familiar with the DICOM v3.0 standards and with the terminology and concepts used in
those standards.
DentalEye Enterprise is a SCP (Service Class Provider) and a SCU (Service Class User) for services
relating to DICOM data storage and retrieval.
This DICOM Conformance Statement is intended for:
• Customers or potential customers
• System integrators of dental equipment
• Software designers implementing DICOM interfaces
1.3. Integration and Validation
The use of this Conformance Statement, in conjunction with the DICOM v3.0 standard, is intended to
facilitate communication with DentalEye Enterprise. The integration of any device into a system of
interconnected devices goes beyond the scope of the DICOM v3.0 standard when interoperability is
desired. The user needs to proceed with caution and be aware of some issues:
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
5 (40)
• It is the user’s responsibility to analyze the application requirements and to design a solution that
integrates DentalEye Enterprise properly with the network.
• Testing the complete range of possible interactions between the DentalEye Enterprise and other
devices should not be overlooked by the user.
1.4. Future Evolution
DICOM v3.0 standard evolves over time in order to meet user requirements and in order to add new
technologies and features. To keep up with these changes, DentalEye AB will follow the evolution of the
standard. This evolution may require modifications to any device that has implemented DICOM v3.0
standard. In the same time the user should ensure that any other provider that DentalEye Enterprise
connects to follows this evolution.
1.5. Sources for this Document
• American College of Radiology-National Electrical Manufacturers Association (ACR-NEMA)
Digital Imaging and Communications V2.0, 1988.
• ACR-NEMA Digital Imaging and Communications in Medicine (DICOM) V3.0. 1993 - 2003.
2. IMPLEMENTATION MODEL
DentalEye Enterprise is a Microsoft Windows based application for capturing images from dental
hardware and creating DICOM files to store to any DICOM Storage Server. It can query a Clinical
Information System for scheduled worklist and patient information using the DICOM Modality Worklist
Find service. It can also query and retrieve images from a PACS using DICOM query retrieve service and
C-MOVE service.
DentalEye Enterprise is a DICOM image store and query/retrieve Service Class User (SCU) and also
Service Class Provider (SCP) to DICOM Storage Service.
2.1. Application Data Flow Diagram
DentalEye Enterprise normally has only one single application entity, which is configurable by the system
administrator. It uses the preconfigured single application entity (AE) for providing all DICOM services
that are required to support the “send”, “query”, “retrieve”, “print”, and ”verification” services.
When DentalEye Enterprise is installed on Citrix terminal server to run as a thin client application, it can
be set up to use a different application entity and port (SCP listen port) for each user that logs into the
application.
Figure 2.1 shows all of the Application Entities and the application data flow in the implementation.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
6 (40)
Figure 2.1 – Application Data Flow Diagram
The DentalEye Enterprise Application Entity (AE) is the only AE which handles all DICOM protocol
communications. All remote DICOM devices that are to be used by DentalEye Enterprise must be
manually configured via a graphical user interface, and the system administrator handles this during
installation.
There are six local real-world activities that occur in DentalEye Enterprise - Image Send, Image Print, Get
Modality Worklist, Image Query, Image Retrieve and Connection Verification. Get Modality Worklist,
Image Send, Image Print and Image Retrieves are done in manual mode. Image query is automated when
DentalEye Enterprise is launched from a CIS/patient management application that passes the patient
identifying parameters to DentalEye via exposed interfaces. If the patient management integration is not
configured, the user can manually query the remote SCP for patient images. DentalEye Enterprise AE as
a SCU uses the remote SCP Query/Retrieve Service Class functionality to query for remote images.
When the user manually selects a series to retrieve, DentalEye Enterprise AE as a SCU uses the remote
SCP Query/Retrieve Service Class functionality to retrieve remote images (C-MOVE Service).
The user can also query the DICOM Modality Worklist Service of a CIS/Patient Management System for
a scheduled worklist from DentalEye Enterprise.
DentalEye Enterprise also supports the DICOM standard Storage Service class as a SCP so that the
requesting SCP can store images to the DentalEye Enterprise database.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
7 (40)
DentalEye Enterprise can be configured to automatically transfer images to a remote Storage SCP as soon
as a series is validated to be a DICOM file. A user can also manually push a series to a remote Storage
SCP. DentalEye Enterprise AE as an SCU uses the remote SCP Storage Service Class functionality to
store local images on a remote database.
DentalEye Enterprise AE as a SCU uses the remote Print Management Service Class to print local, user
selected images and to verify the printer status.
DentalEye Enterprise uses the Verification service as a SCU to test the basic communication checks
between DentalEye Enterprise and other network devices or connections for remote AEs. Remote AEs as
SCUs can also test the connection to DentalEye Enterprise via the standard DICOM Verification service.
2.2. Receive Images
DentalEye Enterprise stores any received image, in its entirety, to its internal local data store. Also,
DentalEye Enterprise extracts the query information and stores the patient, study, series, and image data
in its internal database.
2.3. Query to/from Other Devices
DentalEye Enterprise will query any pre-configured SCP with patient demographic information passed to
it from a Patient Management system (if so configured) or allow users to enter patient identifying
parameters for a query. DentalEye Enterprise will display all the matches in the local and remote SCP to
the user basing its decisions on the records stored in the local database and the query response from the
remote SCP(s).
2.4. Retrieve Images from Other Devices
DentalEye Enterprise sends C-MOVE commands to a remote SCP in order to retrieve images to its local
database and displays them to the user. It uses the information it retrieves from the previous query
response from the SCP for the C-MOVE operation.
2.5. Transmit Images
DentalEye Enterprise will transmit images to other compatible devices as a SCU of the C-STORE
service.
2.6. Storage Commitment
This functionality is not yet implemented in DentalEye Enterprise 3.2.
2.7. Print to Other Devices
DentalEye Enterprise will print images to other compatible devices as SCU of Print Management Service
Class. The DentalEye Enterprise AE as a SCU uses the remote Print Management Service Class for the
printing of user-selected images and to request the printer status.
2.8. Query Modality Worklist
DentalEye Enterprise will query a preconfigured Modality Worklist SCP for scheduled procedures as a
SCU. The user initiates a modality worklist query to the remote worklist SCP with a given set of query
parameters entered by the user. The remote worklist SCP returns responses which match the query
parameters. Items from the returned worklist responses are presented to the user as a list of scheduled
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
8 (40)
procedure for selection option. The user select a scheduled procedure from the list and a subset of the
returned worklist responses are included in acquired DICOM images.
2.9. Functional Definitions of AEs
2.9.1. DentalEye Enterprise
The DentalEye Enterprise AE is the one and only application entity within the DentalEye Enterprise
application. It includes the following service classes:
Verification Service Class
The DentalEye Enterprise AE can perform the Verification service as a SCP and a SCU.
DentalEye Enterprise AE as a SCU can initiate an association with a remote SCP for the Verification SOP
class. After receiving acceptance, it will send a verification request (C-ECHO) and expect a response.
After a successful response, it will send a release request to close the connection.
A remote SCU shall request an association with the DentalEye Enterprise AE for the Verification SOP
class. After accepting the association, the DentalEye Enterprise AE shall receive and respond to the
Verification request and release the association when requested.
Storage Service Class
The DentalEye Enterprise AE can perform the Storage service as a SCP and a SCU. A remote SCU shall
request an association with the DentalEye Enterprise AE for the Storage SOP classes. After accepting the
association, the DentalEye Enterprise AE shall receive the Storage requests, store the data in the local
database, send the applicable Storage responses, and release the association when requested. This could
be the result of a user sending a request from the DentalEye Enterprise application to a remote storage
server.
The DentalEye Enterprise AE as a SCU shall request an association with a preconfigured or user selected
remote Storage SCP for all applicable Storage SOP classes. When the association is accepted, the
DentalEye Enterprise AE shall send the Storage requests, receive the Storage responses and act
accordingly, and release the association.
Query/Retrieve Service Class
The DentalEye Enterprise AE can perform the Query/Retrieve service as a SCU. The DentalEye
Enterprise AE shall request an association with the selected remote SCP for the applicable
Query/Retrieve SOP class. When the association is accepted, the DentalEye Enterprise AE shall send the
Query/Retrieve requests, receive the Query/Retrieve responses and act accordingly, and finally release the
association.
The DentalEye Enterprise AE as SCU will initiate an association for retrieving images from a remote
server. It shall send a C-MOVE request to the remote SCP to retrieve images to its local database. After
receiving a C-MOVE response, DentalEye Enterprise AE shall send a release request and will release the
connection.
The DentalEye Enterprise AE fully supports the Cancel functionality as a SCU for the Query/Retrieve
service.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
9 (40)
Print Management Service Class
The DentalEye Enterprise AE can perform the Print service as a SCU. The DentalEye Enterprise AE shall
request an association with the selected remote DICOM Print SCP for all applicable SOP classes of the
applicable Print Management Meta SOP class. When the association is accepted, the DentalEye
Enterprise AE shall send the Print requests, receive the Print responses and act accordingly, and finally
release the association. The remote Service Class Provider of the Basic Print Management Meta SOP
Class can send N-EVENT-REPORT to DentalEye Enterprise to report execution status changes of a print
request in an asynchronous way.
The DentalEye Enterprise AE can perform the Printer service, as a SCU. The DentalEye Enterprise AE
shall request an association with the selected remote Print SCP for the Printer SOP class. When the
association is accepted, the DentalEye Enterprise AE shall send the N-GET request, receive the Printer
responses (Event Report) and act accordingly, and finally release the association.
Modality Worklist Service Class
The DentalEye Enterprise AE conforms to the Modality Worklist SOP Class as a SCU. When the user
initiates a modality worklist query, the DentalEye Enterprise AE shall request an association with
preconfigured remote Modality Worklist SCP for the Modality Worklist Information Model – FIND SOP
class. When the association is accepted, the DentalEye Enterprise AE shall send the C-FIND command
with user entered query parameters. When the remote worklist SCP returns responses, which match the
query parameters, the DentalEye Enterprise AE acts accordingly and finally releases the association.
Items from the returned worklist responses are presented to the user as a list of scheduled procedures for
selection. The user selects a scheduled procedure from the list and a subset of the returned worklist
responses is included in the acquired DICOM image object.
2.10. Sequencing of Real-World Activities
The DentalEye Enterprise AE supports the following functions:
• Manually or automatically initiates a DICOM association to send images
• Manually initiates a DICOM association for Modality Worklist query
• Manually or automatically initiates a DICOM association to query retrieve images
• Manually initiates a DICOM association to print images
• Automatically initiates a DICOM association for Printer Status
• Manually initiates a DICOM verification to assist in network diagnostics
• Automatically processes Association request as a SCP from remote AEs for the Storage Service.
• Automatically processes Association request as a SCP from remote AEs for the verification
service
• Automatically processes Association request from remote AEs for notification event processing.
• Responds to DICOM verification requests from other remote AE(s).
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
10 (40)
The following diagram describes the real world sequencing for the image printing process.
Figure 2.2 – Sequencing For Image Printing and Print Status
3. AE SPECIFICATIONS
3.1. DentalEye Enterprise Specifications
DentalEye Enterprise supports the following transfer syntaxes to communicate with DICOM peer AEs:
Table 3.1 – Standard Transfer Syntax
Transfer Syntax Name Transfer Syntax UID
Implicit VR Little Endian (DICOM Default) 1.2.840.10008.1.2
Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
Table 3.2 – Extended Transfer Syntaxes for Storage Service
Transfer Syntax Name Transfer Syntax UID
Implicit VR Little Endian 1.2.840.10008.1.2
Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
JPEG Baseline, Lossy (Process 1) 1.2.840.10008.1.2.4.50
JPEG Lossy (Process 4) (12 bit) 1.2.840.10008.1.2.4.51
JPEG Lossless, Non-Hierarchical (Process 14) 1.2.840.10008.1.2.4.57
JPEG Lossless, Non-Hierarchical, First-Order Prediction
(Process 14 [Selection Value 1]) 1.2.840.10008.1.2.4.70
JPEG 2000 Image Compression (Lossless Only) 1.2.840.10008.1.2.4.90
JPEG 2000 Image Compression 1.2.840.10008.1.2.4.91
RLE Lossless (Pack Bits) 1.2.840.10008.1.2.5
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
11 (40)
DentalEye Enterprise provides Standard Conformance to the following DICOM V3.0 SOP Classes as
SCP and SCU:
Table 3.3 – Verification SOP Class
SOP Class SOP Class UID
Verification 1.2.840.10008.1.1
DentalEye Enterprise provides Standard Conformance to the following DICOM V3.0 Storage SOP
Classes as SCP and SCU:
Table 3.4 – SOP Classes for Storage Services
SOP Class Name SOP Class UID
Hardcopy Grayscale Image Storage Class 1.2.840.10008.5.1.1.29
Hardcopy Color Image Storage Class 1.2.840.10008.5.1.1.30
Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1
Computed Tomography Image Storage 1.2.840.10008.5.1.4.1.1.2
Secondary Capture Multi-frame Grayscale Byte Image
Storage 1.2.840.10008.5.1.4.1.1.7.2
Secondary Capture Multi-frame Grayscale Word Image
Storage 1.2.840.10008.5.1.4.1.1.7.3
Magnetic Resonance Image Storage 1.2.840.10008.5.1.4.1.1.4
Secondary Capture Multi-Frame True Color Image
Storage 1.2.840.10008.5.1.4.1.1.7.4
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 X-Ray Image Storage - For Processing 1.2.840.10008.5.1.4.1.1.1.1.1
Grayscale Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.1
Digital Intra-oral X-Ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.3
Digital Intra-oral X-Ray Image Storage - For Processing 1.2.840.10008.5.1.4.1.1.1.3.1
Visible Light Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.77.1
Visible Light Multiframe Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.77.2
Visible Light Endoscopic Image Storage Class 1.2.840.10008.5.1.4.1.1.77.1.1
Visible Light Microscopic Image Storage Class 1.2.840.10008.5.1.4.1.1.77.1.2
Visible Light Slide-Coordinates Microscopic Image
Storage Class 1.2.840.10008.5.1.4.1.1.77.1.3
Visible Light Photographic Image Storage Class 1.2.840.10008.5.1.4.1.1.77.1.4
DentalEye Enterprise provides Standard Conformance to the following DICOM V3.0 SOP Classes as a
SCU:
Table 3.5 – SOP Classes for Query Retrieve and Print Services
SOP Class Name SOP Class UID
Patient Root Query/Retrieve Information Model – FIND 1.2.840.10008.5.1.4.1.2.1.1
Patient Root Query/Retrieve Information Model – MOVE 1.2.840.10008.5.1.4.1.2.1.2
Study Root Query/Retrieve Information Model – FIND 1.2.840.10008.5.1.4.1.2.2.1
Study Root Query/Retrieve Information Model – MOVE 1.2.840.10008.5.1.4.1.2.2.2
Presentation LUT 1.2.840.10008.5.1.1.23
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
12 (40)
SOP Class Name SOP Class UID
Basic Grayscale Print Management (Meta) 1.2.840.10008.5.1.1.9
> Basic Grayscale Image Box 1.2.840.10008.5.1.1.4
Basic Color Print Management (Meta) 1.2.840.10008.5.1.1.18
> Basic Color Image Box 1.2.840.10008.5.1.1.4.1
> Basic Film Session 1.2.840.10008.5.1.1.1
> Basic Film Box 1.2.840.10008.5.1.1.2
> Printer 1.2.840.10008.5.1.1.16
Modality Worklist Information Model FIND 1.2.840.10008.5.1.4.31
3.1.1. Association Establishment Policies
3.1.1.1. General
The Maximum Length PDU negotiation is included in all association establishments’ requests. The
maximum length PDU for an association initiated by DentalEye Enterprise is 16384. The DICOM
standard Application Context Name proposed and recognized by DentalEye Enterprise is:
Application Context: 1.2.840.10008.3.1.1.1
Note that the Max PDU length is not configurable. The SOP Class Extended Negotiation is supported for
Query/Retrieve services. Note that the same Abstract Syntax may be offered multiple times with different
Transfer Syntaxes.
The user information Items sent by the DentalEye Enterprise AE are:
Maximum PDU Length: 16384
Implementation UID: 1.2.840.114257.3.6.3.2
Implementation Version Name: DentalE3.2.x (where x is the current version revision)
3.1.1.2. Number of Associations
The DentalEye Enterprise AE will initiate only one DICOM association at a time to perform an image
Store, Query, Retrieve, Print or Verify. The DentalEye Enterprise AE will accept up to ten DICOM
associations at a time from remote AEs to perform an image Verify, Store, Printer.
3.1.1.3. Asynchronous Nature
DentalEye Enterprise will only allow a single outstanding operation on an association. Therefore,
DentalEye Enterprise will not perform asynchronous operations negotiation other than the default
specified by the DICOM standard.
3.1.1.4. Implementation Identifying Information
DentalEye Enterprise requests and responds with the following implementation identifying parameters:
Implementation Class UID: 1.2.840.114257.3.6.3.2
Implementation Version Name: DentalE3.2.x (where x is the current version revision)
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
13 (40)
3.1.1.5. Called/Calling Titles
Calling AE title is configurable in DentalEye Enterprise and any user with administrative rights can
configure the AE and listening port settings. Also DentalEye Enterprise validates the Called Title and IP
address of the requesting SCU during association negotiation, providing a first pass level of security.
3.1.2. Association Initiated by Real-World Activity
3.1.2.1. Real-World Activity – Verification
3.1.2.1.1. Associated Real-World Activity – Verification
DentalEye Enterprise will commit Verification requests as a response to the user mediated requests via
GUI, in order to test the validity of the current DICOM connection.
3.1.2.1.2. Proposed Presentation Contexts
Table 3.6 – Proposed Presentation Contexts
Abstract Syntax Name Abstract Syntax UID Transfer Syntax Role Extended Negotiation
Verification SOP Class 1.2.840.10008.1.1 All from Table 3.1 SCU None
3.1.2.1.3. SOP Specific Conformance – Verification
DentalEye Enterprise provides standard conformance to the Verification Service Class from DICOM v3.0
as a SCU.
3.1.2.2. Real-World Activity – Storage
3.1.2.2.1. Associated Real-World Activity – Storage
DentalEye Enterprise can be configured to automatically transfer images to a remote Storage SCP as soon
as a series is validated to be stored as DICOM. A user can also manually push a DICOM series to a
remote Storage SCP. Although there are two different ways for the operator to initiate an image
transmission, the DICOM initiation and transfer process are identical.
When a user validates a series or manually selects a series to store to a remote DICOM Storage Server,
DentalEye Enterprise AE initiates an association to a preconfigured remote Storage Server AE and uses it
to send C-STORE requests and receive the associated C-STORE responses. The association is released
when all selected images in the series have been transmitted.
By default, DentalEye Enterprise sends an IOD using the transfer syntax that was used when the image
was originally created or imported. DentalEye Enterprise can be configured to offer the original transfer
syntax in the stored DICOM dataset and Implicit Little Endian (DICOM default) transfer syntax per
presentation context to remote SCP. If the SCP accepts Implicit Little Endian transfer syntax, DentalEye
Enterprise will convert the IOD from the original transfer syntax to Implicit Little Endian.
The DentalEye Enterprise AE will stop the transfer of the images and release the association as soon as it
receives an unsuccessful store response status.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
14 (40)
3.1.2.2.2. Presentation Context Table – Storage
Table 3.7 – Presentation Contexts for Storage
SOP Class Transfer Syntax Role Extended Negotiation
All from Table 3.4 All from Table 3.2 SCU None
3.1.2.2.3. SOP Specific Conformance – Storage
DentalEye Enterprise as a SCU conforms to the DICOM Storage Service Class.
Use of optional, private, and retired attributes
The following Private tags are used for encoding proprietary annotation information:
Table 3.8 – Tags Used for Encoding Proprietary Annotation Information
Attribute Name Tag Value
Private Identification Code 0051,0010 LEAD_ANNOTATION_0013
LEADTOOLS Annotation Data 0051,1000
DentalEye Enterprise may transmit Storage SOP instances with all the optional elements specified in the
DICOM standard, depending on the source of the images.
The transmitted Storage SOP instances may contain Retired and Private data elements, depending on the
source of the images. DentalEye Enterprise may store and transmit proprietary annotation information in
Storage SOP instances as private elements.
Table 3.9 – DICOM C-STORE Response Handling Behavior
Service
Status Further Meaning
Status
Code Behavior
Success Storage is complete 0000 Continues with next store until completed
and thereafter association is released
Refused Out of Resources A7XX User notified and/or reason is logged. Store
job fails and connection closed
Error
Dataset does not match SOP Class A9XX User notified and/or reason is logged. Store
job fails and connection closed
Cannot understand CXXX User notified and/or reason is logged. Store
job fails and connection closed
Warning
Coercion of Data Elements B000 Continues with next store until completed
and thereafter association is released
Data Set does not match SOP Class B006 Continues with next store until completed
and thereafter association is released.
Elements Discarded B007 Continues with next store until completed
and thereafter association is released.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
15 (40)
3.1.3. Association Acceptance Policy
3.1.3.1. Real-World Activity – Verification
3.1.3.1.1. Associated Real-World Activity – Verification
DentalEye Enterprise shall accept associations only from known remote AEs that wish to verify
application level communication. DentalEye Enterprise performs the Verification Service Class by
responding with C-ECHO RSP, in order to provide a SCU the state of being able to receive DICOM
requests.
3.1.3.1.2. Associated Acceptance Policy
DentalEye Enterprise shall reject association requests from unknown AEs, i.e. AEs that offer “calling AE
titles” that are not preconfigured in DentalEye Enterprise.
Also, DentalEye Enterprise shall reject association requests from applications that do not use the proper
“called AE title” which is also preconfigured in DentalEye Enterprise.
3.1.3.1.3. Presentation Context Table – Verification
Table 3.10 – Acceptable Presentation Contexts
Abstract Syntax Name Abstract Syntax UID Transfer Syntax Role Extended Negotiation
Verification SOP Class 1.2.840.10008.1.1 Any from Table 3.1 SCP None
3.1.3.1.4. SOP Specific Conformance – Verification
DentalEye Enterprise provides standard conformance to the DICOM V3.0 Verification Service Class as a
SCP for the Verification SOP Class, UID=1.2.840.10008.1.1.
3.1.3.1.5. Presentation Context Acceptance Criterion – Verification
DentalEye Enterprise will accept any Presentation Context from Table 3.10.
3.1.3.1.6. Transfer Syntax Selection Policies
DentalEye Enterprise shall support only the default DICOM Transfer Syntax for the Verification
command.
3.1.3.2. Real-World Activity – Storage (Import Images)
A remote system requests image storage to DentalEye Enterprise using the C-STORE command.
3.1.3.2.1. Associated Real-World Activity – Storage
The Real-World Activity associated with the C-STORE operation is the storage of the image in the
DentalEye Enterprise’s local database. DentalEye Enterprise will issue a failure status if it is unable to
store the image in its local database.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
16 (40)
3.1.3.2.2. Association Acceptance Policy
DentalEye Enterprise shall reject association requests from unknown AEs, i.e. AEs that offer “calling AE
titles” that are not preconfigured in DentalEye Enterprise.
Also, DentalEye Enterprise shall reject association requests from applications that do not use the proper
“called AE title” which is also preconfigured in DentalEye Enterprise.
3.1.3.2.3. Accepted Presentation Contexts- Storage
DentalEye Enterprise AE shall be able to accept the presentation contexts as specified in the following
table.
Table 3.11 – Acceptable Presentation Contexts
Abstract Syntax Transfer Syntax Role Extended Negotiation
Any from Table 3.4 Any from Table 3.2 SCP FULL SCP
DentalEye Enterprise provides standard conformance to the DICOM V3.0 Storage Service Class as a SCP
for any of the SOP Classes from table 3.2.
3.1.3.2.4. SOP Specific Conformance – Storage
DentalEye Enterprise conforms to the FULL DICOM Storage Service Class (Level 2). No elements are
discarded. Also DentalEye Enterprise conforms to the DICOM File Management Roles and Services as a
FSC and FSR, as defined in Part 10 of the DICOM v3.0 specifications. DentalEye Enterprise stores all
DICOM images along with the File Meta Information Header.
The response status behavior of DentalEye Enterprise is as described in the following table.
Table 3.12 – DICOM C-STORE Response Handling Behavior
Service
Status Further Meaning
Status
Code Behavior
Success Storage is complete 0000 The image (s) shall be stored in DentalEye
Enterprises local database
Refused Out of Resources A700 Database is full. Response with this status
sent to AE and condition logged
Error
Dataset does not match SOP Class A900
SOP Class of the image does not match the
abstract syntax.
Connection notified and reason is logged
Cannot understand C000 Error in parsing dataset. Connection
notified and reason is logged
Warning
Coercion of Data Elements B000 N/A
Data Set does not match SOP Class B006 N/A
Elements Discarded B007 N/A
3.1.3.2.5. Presentation Context Acceptance Criterion - Storage
DentalEye Enterprise will accept any number of Storage Presentation Contexts per association request.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
17 (40)
3.1.3.2.6. Transfer Syntax Selection Policies – Storage
DentalEye Enterprise has no preference on Transfer Syntax encoding. If offered a choice of Transfer
Syntax's in a Presentation Context, it will pick the first Transfer Syntax it encounters from Table 3.2 in a
Presentation Context.
3.1.3.3. Real-World Activity – Find (Query Remote Images)
3.1.3.3.1. Associated Real-World Activity – Find
There are two different real world activities, automated and manual, that could cause DentalEye
Enterprise AE to initiate the association to query remote SCP to find matching images.
Automated mode is when the patient management integration is enabled in DentalEye Enterprise. In this
scenario, DentalEye Enterprise is launched from a patient management application that passes the patient
identifying parameters to it via different interfaces exposed by DentalEye Enterprise. DentalEye
Enterprise AE automatically initiates the association with pre-configured selected peer entity and uses it
and patient identifying parameters (passed to it from Patient Management application) to send Query (C-
FIND) requests. The association is released when the execution of the query completes.
The manual process is when the patient management integration is not configured and the user uses a GUI
query dialog to query a remote SCP for patient images. In this scenario, DentalEye Enterprise AE initiates
the association with selected peer entities when a user clicks on the “Find” button in the query dialog and
uses it and user entered patient identifying parameters to send Query (C-FIND) requests. DentalEye
Enterprise shall send a C-FIND-Cancel request if the user selects “Cancel” option in GUI any time before
execution of the query completes.
The association is released when the execution of the query completes. In case of Refused, Failed or
Cancel status response from SCP, DentalEye Enterprise will proceed to close the connection by sending a
release request to the SCP and shall act accordingly after a response from the SCP.
3.1.3.3.2. Presentation Context Table – Find
DentalEye Enterprise will propose any of the Presentation Contexts listed in Table 3.13 for Query.
Table 3.13 – Proposed Presentation Contexts
Abstract Syntax Name Abstract Syntax UID Transfer Syntax Role Extended
Negotiation
Patient Root
Query/Retrieve – FIND
1.2.840.10008.5.1.4.1.2.1.1
Any from Table
3.1 SCU None
Study Root
Query/Retrieve – FIND
1.2.840.10008.5.1.4.1.2.2.1
Any from Table
3.1 SCP None
DentalEye Enterprise AE initiates associate request with an extended negotiation stub for C-Find
Extended Negotiation to use relational queries. If it receives an associate acceptance with an extended
negotiation stub for relational queries, it will issue a C-FIND request following the DICOM relational
queries rule. Otherwise it shall be capable of generating query requests, which meet the requirements of
C-FIND baseline Hierarchical Search. Associate request will have the following information for
appropriate presentation context:
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
18 (40)
Table 3.14 – Find extended negotiation
Field Name Value Description Field
Relational-queries 1 Relational queries are supported
3.1.3.3.3. SOP Specific Conformance – Find
DentalEye Enterprise provides standard conformance to the DICOM V3.0 Query/Retrieve Service Class
as a SCU for the SOP Class listed in Table 3.12 via the DIMSE C-FIND.
The DentalEye Enterprise AE will generate queries containing zero length optional keys. The DentalEye
Enterprise AE does not assume the SCP will process an Optional Key in the same manner as a Required
Key. The DentalEye Enterprise AE prefers Relational Search Method, when the SCP accepts extended
negotiation for appropriate Abstract Syntax. Otherwise, it will generate baseline queries based on
Hierarchical Search Method.
In the following table the supported query keys for each query level are described. Universal matching
shall be supported as default. DentalEye Enterprise supports all the four levels of query using the
respective keys.
DentalEye Enterprise transmits the following attributes of the Patient Root Query/Retrieve Information
Model-FIND SOP Class:
Table 3.15 – Patient Level Attributes
Attribute Type of Matching Tag Type
Patient's Name Wild Card (0010,0010) Required
Patient ID Wild Card (0010,0020) Unique
Patient's Birth Date - (0010,0030) Optional
Patient's Birth Time - (0010,0032) Optional
Patient's Sex - (0010,0040) Optional
Other Patient Ids - (0010,1000) Optional
Other Patient Names - (0010,1001) Optional
Ethnic Group - (0010,2160) Optional
Patient Comments - (0010,4000) Optional
Number of Patient Related Studies - (0020,1200) Optional
Number of Patient Related Series - (0020,1202) Optional
Number of Patient Related Instances - (0020,1204) Optional
Table 3.16 – Study Level Attributes
Attribute Type of Matching Tag Type
Study Date Date Range / Single Value (0008,0020) Required
Study Time - (0008,0030) Required
Accession Number Wild Card (0008,0050) Required
Study ID Wild Card (0020,0010) Required
Study Instance UID Single Value (0020,000D) Unique
Modalities in Study - (0008,0061) Optional
Referring Physician's Name - (0008,0090) Optional
Study Description Wild Card (0008,1030) Optional
Name of Physician(s) Reading Study Wild Card (0008,1060) Optional
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
19 (40)
Attribute Type of Matching Tag Type
Admitting Diagnoses Description - (0008,1080) Optional
Patient's Age - (0010,1010) Optional
Patient's Size - (0010,1020) Optional
Patient's Weight - (0010,1030) Optional
Occupation - (0010,2180) Optional
Additional Patient History - (0010,21B0) Optional
Number of Study Related Series - (0020,1206) Optional
Number of Study Related Instances - (0020,1208) Optional
DentalEye Enterprise transmits the attributes listed in the following table for Series Level Study Root
Query/Retrieve Information Model – FIND request:
Table 3.17 – Series Level Attributes
Attribute Query Keys Return Tag Type
Modality Single Value (0008,0060) Required
Series Number - (0020,0011) Required
Series Instance UID Single Value (0020,000E) Unique
Number of Series Related Instances - (0020,1209) Optional
DentalEye Enterprise transmits the attributes listed in the following table for Image Level Study Root
Query/Retrieve Information Model – FIND request.
Table 3.18 – Composite Object Instance Level Attributes
Attribute Query Keys Return Tag Type
Instance Number - (0020,0013) Required
SOP Instance UID Single Value (0008,0018) Unique
DentalEye Enterprise transmits the following attributes of the Study Root Query/Retrieve Information
Model – FIND SOP Class:
Table 3.19 – Study Level Attributes for Study Root- FIND
Attribute Name Type of Matching Tag Type
Study Date Date Range (0008,0020) Required
Study Time - (0008,0030) Required
Accession Number - (0008,0050) Required
Query/Retrieve Level Enumerated value:
STUDY (0008,0052) Required
Modalities in Study - (0008,0061) Optional
Referring Physician’s Name - (0008,0090) Optional
Study Description - (0008,1030) Optional
Patient’s Name Wild Card (0010,0010) Required
Patient ID Wild Card (0010,0020) Required
Patient’s Birth Date Single Value (0010,0030) Optional
Patient’s Sex Single Value (0010,0040) Optional
Study Instance UID - (0020,000D) Unique
Study ID - (0020,0010) Optional
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
20 (40)
Attribute Name Type of Matching Tag Type
Number of Patient Related Studies - (0020,1200) Optional
Number of Patient Related Series - (0020,1202) Optional
Number of Patient Related Instances - (0020,1204) Optional
Number of Study Related Series - (0020,1206) Optional
Number of Study Related Instances - (0020,1208) Optional
The following are the status codes that are more specifically processed when receiving messages from a
C-FIND SCP:
Table 3.20 – DICOM C-FIND Response Handling Behavior
Service
Status Further Meaning
Status
Code Behavior
Success Matching is complete 0000 Find results are displayed
Refused Out of Resources A700 User notified, reason is logged
and connection closed
Failed
Identifier Does not match SOP Class A900 User notified, reason is logged
and connection closed
Unable to process CXXX User notified, reason is logged
and connection closed
Cancel Matching terminated due to user cancel
request Fe00
User notified, reason is logged
and connection closed
Pending
Matches are continuing – Current Match is
supplied and any Optional Keys were
supported in the same manner as Required
Keys.
FF00 Find command continues
Matches are continuing – Warning that one or
more Optional Keys were not supported for
existence and/or matching for this identifier
FF01 Find command continues
3.1.3.4. Real-World Activity – Move
3.1.3.4.1. Associated Real-World Activity – Move
The Real-World Activity Retrieve Images involves the retrieve of images on a remote system by moving
matching images from the remote database to DentalEye Enterprise’s database.
When a user opens a patient’s folder or queries for images of a patient, DentalEye Enterprise queries all
user selected AE(s) down to image level to present the user with a combined list of available images
(instances) in series level view. In this process it also collects the information (Retrieves AE Title) about
AEs that have the actual instances.
The user is able to select a series of image(s) in a patient folder from a remote database to the local
database in the following two ways:
When DentalEye Enterprise is not configured with a Patient Management system, a user can retrieve
images by means of selecting a series and double clicking on the series or clicking on retrieve button from
the query dialog in DentalEye Enterprise.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
21 (40)
A user can also retrieve images from a remote DICOM Server whether the Patient Management system is
enabled or not by clicking on a series list (Series View) in a patient folder.
When a user triggers the image retrieval in any of the above mentioned processes, DentalEye Enterprise
will initiate association with the remote AE and uses it to send a retrieve (C-MOVE) request. It specifies
its own AE Title as the destination AE during C-MOVE command for retrieval.
DentalEye Enterprise sends a series level C-MOVE request to retrieve all images/instances under the
series with one request. The association is released after the final Retrieve (C-MOVE) response from the
remote AE.
3.1.3.4.2. Proposed Presentation Context Table – Move
DentalEye Enterprise will use Presentation Contexts listed in Table 3.21 for retrieval.
Table 3.21 – Proposed Presentation Contexts
Abstract Syntax Name Abstract Syntax UID Transfer
Syntax Role
Extended
Negotiation
Patient Root Query/Retrieve –
MOVE 1.2.840.10008.5.1.4.1.2.1.2
All from
Table 3.1 SCU None
Study Root Query/Retrieve –
MOVE 1.2.840.10008.5.1.4.1.2.2.2
All from
Table 3.1 SCU None
DentalEye Enterprise prefers relational queries and will send an associate request with an extended
negotiation stub. If the accepting SCP supports extended negotiations for abstract syntax listed in Table
3.21, DentalEye Enterprise shall send C-MOVE request using Relational-Retrieve option, otherwise it
will conform to baseline SCU behavior. DentalEye Enterprise will send an associate request with
extended negotiation stub with the following information:
Table 3.22 – Move extended negotiation
Field Name Value Description Field
Relational-queries 1 Relational queries are supported
3.1.3.4.3. SOP Specific Conformance – Move
DentalEye Enterprise provides both the baseline and extended behavior of the C-MOVE SCU. The
extended behavior of Relational-Retrieve is used only if properly associated with SCP.
Study Root Information Model – MOVE SOP Class:
DentalEye Enterprise transmits the following attributes of the Study Root Information Model – MOVE
SOP Class. It uses only the Series Level move.
Table 3.23 – Attributes for Move Study Root Information Model - MOVE
Attribute Value Tag Type
Study Instance UID Single Value 0020,000D Unique
Series Instance UID Single Value 0020,000E Unique
Query/Retrieve Level SERIES 0008,0052 Required
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
22 (40)
Patient Root Information Model – MOVE SOP Class:
DentalEye Enterprise transmits the following attributes of the Patient Root Information Model – MOVE
SOP Class. It uses only the Series Level move.
Table 3.24 – Attributes for Move Patient Root Information Model – MOVE
Attribute Value Tag Type
Patient ID Single Value 0010,0010 Required
Study Instance UID Single Value 0020,000D Unique
Series Instance UID Single Value 0020,000E Unique
Query/Retrieve Level SERIES 0008,0052 Required
The following are the details regarding response behavior of different status code.
Table 3.25 – C-MOVE status
Service Status Further Meaning Status
Code Behavior
Success Sub-operations Complete – No Failures 0000
Retrieved images are
displayed. Association is
released
Refused
Out of Resources – Unable to calculate number
of matches A701
User notified, reason is
logged and connection closed
Out of Resources – Unable to perform sub-
operations A702
User notified, reason is
logged and connection closed
Move Destination unknown A801 User notified, reason is
logged and connection closed
Failed
Identifier Does not match SOP Class A900 User notified, reason is
logged and connection closed
Unable to process CXXX User notified, reason is
logged and connection closed
Warning Sub-operations Complete – One or more
Failures B000
User notified, Retrieved
images are displayed.
Association is released
Cancel Matching terminated due to user cancel request FE00 User notified, reason is
logged and connection closed
Pending Sub-operations are continuing FF00 User notified, Move
command continues.
3.1.3.5. Real-World Activity – Query Modality Worklist
3.1.3.5.1. Associated Real-World Activity – Modality Worklist
The Real-World Activity Query Modality Worklist involves the retrieval of scheduled procedures on a
remote system by querying for matching scheduled procedures from the remote database to DentalEye
Enterprise’s database.
When user selects the Modality Worklist Query option from the menu or clicks on the Modality Worklist
button in DentalEye Enterprise, the user is presented with a dialog box to enter query parameters listed in
Table 3.26 and Table 3.27 and a “Query” button to initiate the query. When user clicks the query button,
DentalEye Enterprise initiates an association with a preconfigured Modality Worklist SCP for the
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
23 (40)
Modality Worklist service. Once the association is accepted by the SCP for the appropriate SOP class,
DentalEye Enterprise sends the C-FIND command with the query parameters entered by the user. The
remote worklist SCP returns responses, which match the query parameters. Once the matching is
complete, DentalEye Enterprise closes the association.
Matching items from the returned worklist responses are presented to the user as list of scheduled
procedures for the user to select. The user can select a scheduled procedure item from the list to capture
image(s) for the selected procedure. DentalEye Enterprise shall create appropriate SOP instances using
the corresponding IOD class matching the modality specified in the scheduled procedure and auto
populating the dataset using information from the selected scheduled procedure item.
Table 3.26 – Matching Key Attributes for Patient-based Query
Matching Key Attributes Tag
Patient’s Name (0010,0010)
Patient ID (0010,0020)
Accession Number (0008,0050)
Requested Procedure ID (0040,1001)
Table 3.27 – Matching Key Attributes for Broad Query
Matching Key Attributes Tag
Scheduled Station AE Title (0040,0001)
Scheduled Procedure Step Start Date (0040,0002)
Modality (0008,0060)
3.1.3.5.2. Proposed Presentation Context Table – Query Modality Worklist
DentalEye Enterprise will use Presentation Contexts listed in Table 3.28 for Modality worklist query.
Table 3.28 – Proposed Presentation Contexts
Abstract Syntax Name Abstract Syntax UID Transfer Syntax Role Extended
Negotiation
Modality Worklist Information
Model – FIND
1.2.840.10008.5.1.4.31
All from Table
3.1 SCU None
3.1.3.5.3. SOP Specific Conformance – Modality Worklist Information Model – FIND
DentalEye Enterprise provides both the baseline and extended behavior of the Modality Worklist
Information Model – FIND.
Table 3.29 – Attributes for Modality Worklist Information Model – FIND
Attribute Tag Match Return
Patient Identification Module
Patient ID 0010,0020 Single Value 1
Patient's Name 0010,0010 Wild Card 1
Other Patient IDs 0010,1000 3
Other Patient Names 0010,1001 3
Patient Demographic Module
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
24 (40)
Attribute Tag Match Return
Patient's Birth Date 0010,0030 2
Patient's Sex 0010,0040 2
Patient's Weight 0010,1030 2
Patient's Address 0010,1040 3
Patient Comments 0010,4000 3
Confidentiality Constraint on Patient Data Description 0040,3001 3
Patient Medical Module
Medical Alerts 0010,2000 2
Contrast Allergies 0010,2110 2
Additional Patient History 0010,21B0 2
Pregnancy Status 0010,21C0 2
Special Needs 0038,0050 2
Patient State 0038,0500 2
Visit Relationship Module
Referenced Patient Sequence 0008,1120 Sequence Matching 2
> Referenced SOP Class UID 0008,1150 1c
> Referenced SOP Instance UID 0008,1155 1c
Visit Identification Module
Institution Name 0008,0080 3
Institution Address 0008,0081 3
Admission ID 0038.0010 2
Visit Status Module
Current Patient Location 0038,0300 2
Visit Admission
Referring Physician's Name 0008,0090 3
Scheduled Procedure Step Module
Scheduled Procedure Step Sequence 0040,0100 Sequence Matching 1
>Comments on the Scheduled Procedure Step 0040,0400 3
>Modality 0008,0060 Single Value 1
>Pre-Medication 0040,0012 2c
>Requested Contrast Agent 0031,1070 2c
>Scheduled Performing Physician's Name 0040.0006 2
>Scheduled Procedure Step Description 0040,0007 1c
>Scheduled Procedure Step ID 0040,0009 1
>Scheduled Procedure Step Location 0040,0011 2
>Scheduled Procedure Step Start Date 0040,0002 Date Range 1
>Scheduled Procedure Step Start Time 0040,0003 1
>Scheduled Procedure Step Status 0040,0020 3
>Scheduled Protocol Code Sequence 0040,0008 Sequence Matching 1c
>Scheduled Station AE Title 0040,0001 Single Value 1
>Scheduled Station Name 0040,0010 3
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
25 (40)
Attribute Tag Match Return
Requested Procedure Module
Study Instance UID 0020,000D 1
Requested Procedure Description 0032,1060 1C
Requested Procedure Code Sequence 0032,1064 Sequence Matching 1C
Requested Procedure ID 0040,1001 Single Value 1
Reason for the Requested Procedure 0040,1002 3
Requested Procedure Priority 0040,1003 3
Names of Intended Recipients of Results 0040,1010 3
Requested Procedure Comments 3
Referenced Study Sequence 0008,1110 Sequence Matching 2
Imaging Service Request Module
Accession Number 0008,0050 Single Value 2
Referring Physician's Name 0008,0090 2
Requesting Physician 0032,1032 2
Requesting Service 0032,1033 3
Reason for the Imaging Service Request 0040,2001 3
Placer Order Number / Imaging Service Request 0040,2016 3
Filler Order Number / Imaging Service Request 0040,2017 3
Imaging Service Request Comments 0040,2400 3
SOP Common Module
Specific Character Set 0008,0005 1C
In the following table are the details regarding response behavior of different status codes:
Table 3.30 – Modality Worklist – FIND status
Service
Status Further Meaning
Status
Code Behavior
Success Matching is complete- no final identifier is
supplied 0000
Matching scheduled
responses are displayed.
Association is released
Refused Out of Resources A700
User notified, reason is
logged and connection
closed
Cancel Matching terminated due to user cancel request FE00
User notified, reason is
logged and connection
closed
Failed
Identifier Does not match SOP Class A900
User notified, reason is
logged and connection
closed
Unable to process CXXX
User notified, reason is
logged and connection
closed
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
26 (40)
Service
Status Further Meaning
Status
Code Behavior
Pending
Sub-operations are continuing FF00 User notified, C-FIND
command continues.
Sub-operations are continuing – Warning that one
or more optional keys are not supported for
existence for this identifier.
FF01 User notified, C-FIND
command continues.
3.1.3.6. Real-World Activity - Storage Commitment (optional)
This functionality is not yet implemented in DentalEye Enterprise 3.2.
3.1.3.7. Real-World Activity – Print
3.1.3.7.1. Description and Sequencing of Activity
The DentalEye Enterprise AE initiates a DICOM association with the selected printer AE
when the user selects DICOM print option from GUI.
The DentalEye Enterprise AE selects the appropriate Abstract and Transfer Syntax from
those accepted by the remote SCP of Print Management Meta SOP Classes.
The DentalEye Enterprise AE uses the N-GET to retrieve a Printer SOP Instance.
If the user selected images are grayscale and the SCP accepts appropriate abstract syntax,
DentalEye Enterprise shall use N-CREATE to create Presentation LUT SOP Instance.
The DentalEye Enterprise AE uses the N-CREATE to create a Basic Film Session SOP
Instance.
The DentalEye Enterprise AE uses the N-SET to update a Basic Film Session SOP Class
The DentalEye Enterprise AE uses the N-CREATE to create a Basic Film Box SOP
Instance.
The DentalEye Enterprise AE uses the N-SET to update the Basic Image Box IOD for each
image box instance created by SCP.
The DentalEye Enterprise AE uses the N-ACTION (PRINT, Basic Film Box SOP Instance)
command to print the image.
DentalEye Enterprise AE uses the N-DELETE to delete the Film Box SOP Instance
The DentalEye Enterprise AE uses the N-DELETE to delete the Film Session SOP
Instance.
The DentalEye Enterprise AE uses the N-DELETE Service Element to request the SCP to
delete the Presentation LUT SOP Instance.
The DentalEye Enterprise AE shall send confirmation of the N-EVENT-REPORT
operation.
After the successful print process, DentalEye Enterprise shall send release request and close
the association properly.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
27 (40)
Figure 3.1 – Sequencing of Print (*Presentation LUT SOP Class is only used for grayscale images)
3.1.3.7.2. Proposed Presentation Context
DentalEye Enterprise will use Presentation Contexts listed in the following Table for Print service:
Table 3.34 – Proposed Presentation Contexts
Abstract Syntax Name Abstract Syntax UID Transfer
Syntax Role
Extended
Negotiation
Presentation LUT 1.2.840.10008.5.1.1.23 All from
Table 3.1 SCU None
Basic Grayscale Print Management
Meta SOP Class 1.2.840.10008.5.1.1.9
All from
Table 3.1 SCU None
Basic Grayscale Image Box SOP
Class 1.2.840.10008.5.1.1.4
All from
Table 3.1 SCU None
Basic Color Print Management
Meta SOP Class 1.2.840.10008.5.1.1.18
All from
Table 3.1 SCU None
Basic Color Image Box SOP Class 1.2.840.10008.5.1.1.4.1 All from
Table 3.1 SCU None
Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 All from
Table 3.1 SCU None
Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 All from
Table 3.1 SCU None
Printer SOP Class 1.2.840.10008.5.1.1.16 All from
Table 3.1 SCU None
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
28 (40)
3.1.3.7.3. SOP Specific Conformance for SOP Class
DentalEye Enterprise provides standard conformance to the DICOM 3.0 Print Management Service Class
by supporting the Basic Grayscale Print Management Meta SOP Class and Basic Color Print
Management Meta SOP Class.
DentalEye Enterprise transmits the following attributes of the Basic Film Session SOP Class in N-
CREATE and N-SET commands:
Table 3.35 – Basic Film Session SOP Class Attributes transmitted in N-CREATE Command
Attribute Name Tag Value
Number of Copies 2000,0010 Enumerated Values: 1 to 5, Default 1
Print priority 2000,0020 Enumerated Values: (User Configurable) LOW,
MED, HIGH;
Medium Type 2000,0030 Enumerated Values: (User Configurable) BLUE
FILM, CLEAR FILM, and PAPER.
Film destination 2000,0040 Enumerated Values: (User Configurable)
PROCESSOR, MAGAZINE
Film Session Label (see Note) 2000,0050 Patient ID, Study date
Proposed Study Sequence 2130,00A0
>Patient’s Name 0010,0010 Obtained from DICOM dataset
>Patient ID 0010,0020 Obtained from DICOM dataset
>Patient’s Birth Date 0010,0030 Obtained from DICOM dataset
>Patient’s Sex 0010,0040 Obtained from DICOM dataset
>Study Instance UID 0020,000D Obtained from DICOM dataset
>Study Date 0008,0020 Obtained from DICOM dataset
>Referring Physician’s Name 0008,0090 Obtained from DICOM dataset
>Study ID 0020,0010 Obtained from DICOM dataset
>Accession Number 0008,0050 Obtained from DICOM dataset
>Study Description 0008,1030 Obtained from DICOM dataset
>Series Number 0020,0011 Obtained from DICOM dataset
DentalEye Enterprise transmits the following attributes of the Basic Film Box SOP Class in N-CREATE
Command:
Table 3.36 – Basic Film Box SOP Class Attributes transmitted in N-CREATE Command
Attribute Name Tag Value
Image Display Format 2010,0010 Enumerated Values: (User Configurable)
STANDARD\1,1;
STANDARD\C,R
Film Orientation 2010,0040 Enumerated Values: (User Configurable)
PORTRAIT, LANDSCAPE
Film Size ID 2010,0050 Defined Terms: (User Configurable)
8INX10IN, 8_5INX11IN, 10INX12IN,
10INX14IN, 11INX14IN, A4, A3
Magnification Type 2010,0060 Enumerated Values: (User Configurable)
REPLICATE, BILINEAR, CUBIC, NONE.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
29 (40)
Attribute Name Tag Value
Smoothing Type 2010,0080 Fixed 150 and only valid for Magnification Type
(2010,0060) = CUBIC
Border Density 2010,0100 Defined Term Used: (User Configurable).
BLACK, WHITE, DEFAULT
Empty Image Density 2010,0110 Defined Term Used: (User Configurable).
BLACK, WHITE, DEFAULT
Min Density 2010,0120 0 - 500 (User Configurable)
Max Density 2010,0130 0 - 500 (User Configurable)
Trim 2010,0140 Fixed NO
Configuration Info 2010,0150 Use Printer Defined String. Max 64 Characters.
Referenced Film Session Sequence 2010,0500 Referenced Film Session
> Referenced SOP Class 0008,1150 1.2.840.10008.5.1.1.1
> Referenced SOP Instance 0008,1155 Provided by SCP
Referenced Presentation LUT
Sequence
2050,0500 If Presentation LUT SOP class supported by
SCP
> Referenced SOP Class 0008,1150 1.2.840.10008.5.1.1.23
> Referenced SOP Instance 0008,1155 Provided by SCP
DentalEye Enterprise does not transmit any attributes during an N-Action Command for the Basic Film
Box SOP Class. Action type ID is set to 1 for Print.
SOP Specific Conformance for Basic Grayscale Print Management:
DentalEye Enterprise AE provides standard conformance to Basic Grayscale Print Management Meta
SOP Class as a SCU. The DentalEye Enterprise AE provides all mandatory elements for film sessions,
basic film boxes, and basic grayscale images boxes. DentalEye Enterprise transmits the following
attributes of the Basic Grayscale Image Box SOP Class in the N-SET Command:
Table 3.37 – Basic Grayscale Image Box SOP Class Attributes Transmitted in N-SET Command
Attribute Name Tag Value
Image Position 2020,0010 Based on image number or position on template
Polarity 2020,0020 Default NORMAL
Requested Image Size 2020,0030 User Configurable and based on desired image
width on film in mm. (True size printing)
Pre-formatted Grayscale Image
Sequence
2020,0110
> Samples per pixel 0028,0002 Fixed 1
>Photometric Interpretation 0028,0004 Enumerated Values:
MONOCHROME1, MONOCHROME2
> Rows 0028,0010 Based on image and desired image width
> Columns 0028,0011 Based on image and desired image width
> Pixel Aspect Ratio 0024,0034 1/1
> Bits Allocated 0026,0100 8
> Bits Stored 0028,0101 8
> High Bit 0028,0102 7
> Pixel Representation 0028,0103 Fixed 0 for unsigned
> Pixel Data 7FE0,0010 VR is OB
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
30 (40)
SOP Specific Conformance for Basic Color Print Management:
DentalEye Enterprise AE provides standard conformance to Basic Color Print Management Meta SOP
Class as an SCU. The DentalEye Enterprise AE provides all mandatory elements for film sessions, basic
film boxes and basic color images boxes.
DentalEye Enterprise transmits the following attributes of the Basic Color Image Box SOP Class in the
N-SET Command:
Table 3.38 – Basic Color Image Box SOP Class Attributes transmitted in N-SET Command
Attribute Name Tag Value
Image Position 2020,0010 Based on image number or position on template
Polarity 2020,0020 Default NORMAL
Requested Image Size 2020,0030 User Configurable and based on desired image
width on film in mm. (True size printing)
Basic Color Image Sequence 2020,0111
> Samples per pixel 0028,0002 Fixed 3
>Photometric Interpretation 0028,0004 Fixed RGB
>Planar Configuration 0028,0006 Enumerated Value: 1 (frame interleave)
> Rows 0028,0010 Based on image and desired image width
> Columns 0028,0011 Based on image and desired image width
> Pixel Aspect Ratio 0024,0034 1/1
> Bits Allocated 0026,0100 8
> Bits Stored 0028,0101 8
> High Bit 0028,0102 7
> Pixel Representation 0028,0103 Fixed 0 for unsigned
> Pixel Data 7FE0,0010 VR is OB
SOP Specific Conformance for Presentation LUT SOP Class:
Standard conformance is provided to the Presentation LUT SOP Class as a SCU. DentalEye Enterprise
transmits the following attributes of the Presentation LUT SOP Class in the N-CREATE command.
Table 3.39 – Presentation LUT SOP Class Attributes transmitted in N-CREATE Command
Attribute Name Tag Value
Presentation LUT Shape (2050,0020) Enumerated value: IDENTITY and LIN OD
SOP Specific Conformance for Printer SOP Class:
DentalEye Enterprise AE provides Standard conformance to the Printer SOP Class. DentalEye Enterprise
transmits the following attributes of the Printer SOP Class:
Table 3.40 – Printer SOP Class Attributes transmitted by DentalEye Enterprise
Attribute Name Tag Value
Printer Status 2110,0010 Obtained from SCP
Printer Status Info 2110,0020 Obtained from SCP
Printer Name 2110,0030 Obtained from SCP
Manufacturer 0008,0070 Obtained from SCP
Manufacturer Model Name 0008,1090 Obtained from SCP
Device Serial Number 0018,1000 Obtained from SCP
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
31 (40)
Attribute Name Tag Value
Software Versions 0018,1020 Obtained from SCP
Date Of Last Calibration 0018,1200 Obtained from SCP
Time Of Last Calibration 0018,1201 Obtained from SCP
DICOM Command Response Status Handling Behavior:
The following tables detail the response behavior of DentalEye Enterprise to all status codes received in
the Basic Print Management Meta SOP Classes:
Table 3.41 – Printer N-GET Command Response Status Handling
Service Status Further Meaning Status Code Behavior
Success Successful operation 0000 Print process continues
Warning Any warning XXXX Print process continues and
warning is logged
Failure Any failure XXXX Association closed, Reason is
logged, user notified.
Table 3.42 – Presentation LUT N-CREATE Command Response Status Handling
Service Status Further Meaning Status Code Behavior
Success Presentation LUT successfully
created 0000 Print process continues.
Warning
Requested Min Density or Max
Density outside of printer’s
operating range. The printer will
use its respective minimum or
maximum density value instead.
B605 Reason is logged, print process
continues
Failure Any failure XXXX Reason is logged, print process
continues
Table 3.43 – Film Session N-CREATE Command Response Status Handling
Service Status Further Meaning Status Code Behavior
Success Film session successfully created 0000 Print process continues.
Warning Memory allocation not supported B605 Reason is logged, print process
continues
Failure Any failure XXX Association released, Reason is
logged, user notified.
Table 3.44 – Film Box N-CREATE Command Response Status Handling
Service Status Further Meaning Status Code Behavior
Success Film Box successfully created 0000 Print process continues.
Warning
Requested Min Density or Max
Density outside of printer’s
operating range. The printer will
use its respective minimum or
maximum density value instead.
B605 Reason is logged, print process
continues
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
32 (40)
Service Status Further Meaning Status Code Behavior
Failure
There is an existing Film Box that
has not been printed and N-
ACTION at the Film Session level
is not supported. A new Film Box
will not be created when a previous
Film Box has not been printed
C616 Association released, Reason is
logged, user notified.
Table 3.45 – Image Box N-SET Command Response Status Handling
Service Status Further Meaning Status Code Behavior
Success Image successfully stored in Image
Box 0000 Print process continues.
Warning
Image size larger than Image Box
size, the image has been
demagnified.
B604
Reason is logged, print process
continues
Requested Min Density or Max
Density outside of printer’s
operating range. The printer will
use its respective minimum or
maximum density value instead.
B605
Image size is larger than the image
Box size. The image has been
cropped to fit.
B609
Image size or Combined Print
Image size is larger than the Image
Box size. The Image or Combined
Print Image has been decimated to
fit.
B60A
Failure
Image size is larger than Image
Box size C603
Association released, Reason is
logged, user notified.
Insufficient memory in printer to
store the image
C605
Combined Print Image size is
larger than the Image Box size
C613
Table 3.46 – Film Box N-ACTION Command Response Status Handling
Service Status Further Meaning Status Code Behavior
Success
Film belonging to the film session
are accepted for printing; if
supported, the Print Job SOP
Instance is created
0000 Print process continues.
Warning
Film Box SOP Instance hierarchy
does not contain Image Box SOP
Instances (empty page)
B603 Reason is logged, print process
continues
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
33 (40)
Service Status Further Meaning Status Code Behavior
Image size larger than Image Box
size, the image has been
demagnified.
B604
Image size larger than Image Box
size. The image has been cropped
to fit.
B609
Image size or Combined Print
Image size is larger than Image
Box size. The image or Combined
Print Image has been decimated to
fit.
B60A
Failure
Image size is larger than Image
Box size C603
Association released, Reason is
logged, user notified.
Unable to create Print Job SOP
Instance; print queue is full C602
Combined Print Image size is
larger than the Image Box size
C613
Table 3.47 – Printer N-EVENT-REPORT Status Handling
Service Status Further Meaning Status Code Behavior
Normal Successful operation 0000 Print process marked as completed
Warning (Any warning) XXXX Reason is logged, print process
marked as completed
Failure (Any failure) XXXX
Association released, Reason is
logged, user notified. Print process
marked as failed.
3.1.3.8. Real-World Activity – Printer Status
3.1.3.8.1. Description and Sequencing of Activity
The Printer Status Real-World Activity involves the request for the printer status of the configured Print
Management SCPs (i.e. printers). The DentalEye Enterprise AE shall request the printer status before any
print process. The Printer Status info attribute is not included in this process. If there is an error or
warning condition in the Printer Status, DentalEye Enterprise shall initiate a new association for Printer
Status and send attributes listed in the table below with Printer Status Info attribute. The status codes and
values of the Printer status info as returned by the printer shall be logged and shall not be shown on the
GUI. The Log Tool may be used to reveal the received printer status.
3.1.3.8.2. Proposed Presentation Context
DentalEye Enterprise shall use the Presentation Context listed in the following table:
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
34 (40)
Table 3.48 – Presentation Context for Printer SOP Class
Abstract Syntax Name Abstract Syntax UID Transfer
Syntax Role
Extended
Negotiation
Printer 1.2.840.10008.5.1.1.16 All from
Table 3.1 SCU None
3.1.3.8.3. SOP Specific Conformance for Printer SOP Class
The DentalEye Enterprise AE provides standard conformance to the Printer SOP class. DentalEye
Enterprise transmits the following attributes of the Printer SOP Class in the N-GET Command:
Table 3.49 – Printer SOP Class Attributes transmitted in N-GET Command
Attribute Name Tag Value
Printer Status 2110,0010 Obtained from SCP
Printer Status Info 2110,0020 Obtained from SCP
Printer Name 2110,0030 Obtained from SCP
Manufacturer 0008,0070 Obtained from SCP
Manufacturer Model Name 0008,1090 Obtained from SCP
Device Serial Number 0018,1000 Obtained from SCP
Software Versions 0018,1020 Obtained from SCP
Date Of Last Calibration 0018,1200 Obtained from SCP
Time Of Last Calibration 0018,1201 Obtained from SCP
The following table details response behavior to all status codes:
Table 3.50 – N-GET Status Handling for Printer SOP Class
Service Status Further Meaning Status Code Behavior
Success Operations Complete 0000 Print process continues
Warning (Any warning) XXXX Reason is logged. Print process
continues
Error (Any failure) XXX Reason is logged. Print job marked
as failed. Association released.
4. COMMUNICATIONS PROFILES
4.1. Supported Communication Stacks
The TCP/IP Network Communication Support stack is the only supported protocol according to DICOM
v3.0.
4.2. TCP/IP Stack
All the Application Entities in DentalEye Enterprise inherit their TCP/IP stack.
4.3. Physical Media Support
DentalEye Enterprise is indifferent to the physical medium over which TCP/IP operates.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
35 (40)
5. EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS
Not applicable.
6. Media Interchange
6.1. Implementation Model
DentalEye Enterprise allows the user to read stand-alone DICOM files or from DICOM media and to
import them to its local database. It also allows the user to select images of a patient for exporting to a
disk in DICOM Media compatible format. It can process any instances of SOP classes listed in table 3.4.
6.1.1. Application Data Flow Diagram
DentalEye Enterprise consists of only one single application entity: DentalEye Enterprise Entity
(DentalEye Enterprise AE).
The following figure shows the Media Interchange application dataflow as functional overview of
DentalEye Enterprise AE:
Figure 6.1 – Media Interchange application dataflow
When user selects to browse content of a DICOM Media, DentalEye Enterprise AE loads the DICOM
Basic Directory and displays user information encoded in each directory key along with thumbnail
images for the user to select. DentalEye Enterprise gives the user the option to import selected images to
its local database. In this process, DentalEye Enterprise AE acts as a FSR of DICOM Media profile.
When the user selects a patient’s DICOM files for export as DICOM Media compatible format,
DentalEye Enterprise AE creates a DICOM Basic Directory file (DICOMDIR) for the selected images in
the root directory and copies all selected DICOM files to a folder under the root folder. In this process
DentalEye Enterprise AE acts as a FSC of DICOM Media profile.
6.1.2. Functional Definitions of AEs
DentalEye Enterprise has only one application entity: DentalEye Enterprise Entity (DentalEye Enterprise
AE).
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
36 (40)
DentalEye Enterprise can perform the following functions:
It can write a new DICOM file-set onto a media
It can copy SOP instances from piece of media to its local storage.
6.1.3. Sequencing of Real World Activities
User activates the reading, importing, and exporting images to and from DICOM media. DentalEye
Enterprise will compile the DICOMDIR and all referenced images into a CD session image. The CD
session image will be written to CD. There are no other sequencing requirements.
6.1.4. File Meta Information Options
File Meta Information version: 00, 01
Implementation Class UID: 1.2.840.114257.3.6.3.2
Implementation Version Name: DentalE3.2.x (where x is the current version revision)
6.2. AE Specifications
6.2.1. DentalEye Enterprise AE
The DentalEye Enterprise AE provides Standard Conformance to the DICOM Interchange Option of the
DICOM Media Storage Service. The Application Profiles and Roles are listed in Table 6.1.
Table 6.1 – Application Profiles, Activities, and Roles
Supported Application Profile Real-World Activity Role SC Option
STD-GEN-CD
STD-DEN-CD
Display Directory FSR Interchange
Import to Local Storage FSR Interchange
Create Media FSC Interchange
6.2.1.1. File Meta Information for the Application Entity DentalEye Enterprise AE
The Source Application Entity Title is configurable by the user.
6.2.1.2. Real-World Activities
6.2.1.2.1. Real-World Activity - Display Directory
This functionality is not yet implemented in DentalEye Enterprise 3.2.
6.2.1.2.2. Real-World Activity - Import to Local Storage
The DentalEye Enterprise Application acts as an FSR when copying from the DICOM Media CD to local
storage.
DentalEye Enterprise shall copy any SOP Instance files defined for the Application Profile specified in
table 6.1 or Storage SOP class listed in table 3.4 using any of the transfer syntaxes listed in table 3.2
selected from a DICOM Media CD Directory list from the media to the local storage upon user request.
Media Storage Application Profile
As depicted in table 6.1, the DentalEye Enterprise AE supports the Real-World Activity – Read Images
for the STD-GEN-CD and STD-DEN-CD Application Profile.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
37 (40)
6.2.1.2.3. Real-World Activity - Create Media
When an image transfer to CD-R is initiated then DentalEye Enterprise acts as a FSC using the
interchange option to export SOP Instances from the local database to a CD-R medium. DentalEye
Enterprise AE copies the SOP Instances to the media and creates a corresponding DICOMDIR. It is up to
the user to finalize the physical volume at the completion of the write session. Multiple volumes (i.e. a
logical volume that can cross multiple physical media) are not supported by DentalEye Enterprise AE.
Determination of the potentially applicable Application Profile depends on the IOD type of SOP
Instances selected by user for media creation. As for example, if all selected images are Intraoral and
Digital X-Ray IOD type then DentalEye Enterprise shall create DICOM Media using Dental Radiograph
Interchange Application profile (STD-DEN-CD).
Media Storage Application Profile
As depicted in Table 6.1, the DentalEye Enterprise AE supports the Real-World Activity – Write Images
for the STD-GEN-CD and STD-DEN-CD Application Profiles.
6.3. Augmented and Private Application Profiles
6.3.1. Augmented Application Profiles
None
6.3.1.1. SOP Class Augmentations
None
6.3.1.2. Directory Augmentations
None
6.3.1.3. Other Augmentations
None
6.3.2. Private Application Profiles
None
6.4. Extensions, Specializations and Privatizations of SOP Classes and Transfer
Syntaxes
None
6.5. Media Configuration
Any configuration issues may be found in section 7 (Configuration) of this document.
6.6. Character Sets
DentalEye Enterprise will only support the copy of SOP Instances containing the DICOM default
character set (ISO-IR 6) and ISO-IR 100 as defined in PS 3.5.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
38 (40)
6.7. Codes and Controlled Terminology
The SOP Classes supported by this implementation do not support the use of Codes and Controlled
Terminology.
7. CONFIGURATION
The following parameters of DentalEye Enterprise are configurable.
Table 7.1 – Configuration Parameters
Parameter Possible Values Default Value
AE Title Configurable via GUI <none>
Port Number Configurable via GUI 104
Transfer Syntax for new images Configurable via GUI Depends on SOP class
Server Connection Timeout 3s … 240s 10s
Alert user when free disk space is low 0 MB … 500MB
Local database and image folder Configurable via GUI No default
Log User Activities Yes / No No
Log DICOM Messages Yes / No No
Log Security Messages Yes / No No
Root UID 1.2.840.* 1.2.840.114257.3.6
8. SUPPORT FOR EXTENDED CHARACTER SETS
The following character set is supported:
• Basic G0 Set of the International Reference Version of ISO 646:1990 (ISO-IR 6).
9. CODES AND CONTROLLED TERMINOLOGY
This application makes use of the Baseline Context Groups as specified in the IODs for the SOP Classes
supported, and uses SNOMED DICOM Microglossary Version 3 as a Mapping Resource.
No Private mapping or Coding Schemes are used. DentalEye Enterprise selects codes based on
preconfigured template or user selectable pick list.
10. SECURITY
10.1. ASSOCIATION LEVEL SECURITY
DentalEye Enterprise provides association level security by only accepting connections from the
preconfigured AE(s) and the AE(s) that addresses the DentalEye Enterprise AE properly (i.e. AE that
offers a wrong “called AE title”). The DentalEye Enterprise AE title is defined during configuration of
the application.
10.2. APPLICATION LEVEL SECURITY
DentalEye Enterprise can be configured to use Windows login or application level login. The system
administrator of DentalEye Enterprise can control the following user rights. User accounts can also be
password protected.
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
39 (40)
Table 10.1 – Configurable user rights
User Rights Further Meaning WS Type
Administrate Security User can change the security configuration
and user rights All
Administrate Application User can change the application
configuration All
Administrate Plugins User can change the configuration of the
image capture plugins Capture station
Approve Images User can create DICOM Image instances
Capture Station/
Diagnostic/Validation
Stations
Unapprove Images User can revert the approval Administrative/Validation
Stations
Delete Images
User can delete images from local DB. User
can also crop images depending on
configuration
All
Edit Images User can modify captured images, layouts
and meta-data before approval All
Print with patient info User can print images along with patient
demographic information All
Export Images User can create DICOM Media and export
to file All
Import Images User can import DICOM from media or file All
Capture Images User can capture images from connected
hardware device Capture Station
Configure and view audit trail User can change the configuration for the
logging and view the reports All
DentalEye 3.2
DICOM conformance statement
DE32-DCM-1.0
2015-12-15
40 (40)
11. ACRONYMS AND ABBREVIATIONS
AAO American Academy of Ophthalmology
ACR American College of Radiology
ADA American Dental Association
AE Application Entity
DICOM Digital Imaging and Communications in Medicine
DIMSE DICOM Message Service Element
DIMSE-C DICOM Message Service Element Composite
DIMSE-N DICOM Message Service Element Normalized
DX Digital Radiography
FSC File-set Creator
FSR File-set Reader
FSU File-set Updater
GUI Graphical User Interface
IOD Information Object Definition
NEMA National Electrical Manufacturers Association
PACS Picture Archiving and Communication System
PDU Protocol Data Unit
RLE Run Length Encoding
RSNA Radiological Society of North America
SCP Service Class Provider
SCU Service Class User
SNOMED Systematized Nomenclature of Medicine
SOP Service-Object Pair
TCP/IP Transmission Control Protocol/Internet Protocol
UID Unique Identifier
VL Visible Light
VR Value Representation
Recommended