scanora 5.0 dicom conformance statement - Soredex

SOREDEX 

SCANORA 5.0 

DICOM CONFORMANCE STATEMENT 

Technical 

Publications 

D507638,1 

Revision 0.15 

29.3.2011 



Copyright © 2011 by PaloDEx Group Oy. 

1 / 55

SOREDEX 



1 CONFORMANCE STATEMENT OVERVIEW 

SCANORA 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 SCANORA. 

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 

Meta SOP Class 

Yes 

No 

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 

SOP Class 

Yes 

No 

Basic Color Image Box SOP Class Yes No 

Transfer 

Computed Radiography Image Storage Yes Yes 

Digital X-ray Image Storage – For 

Presentation 

Yes 

Yes 

Digital X-ray Image Storage – For 

Processing 

Yes 

Yes 

Digital Intra-oral X-ray Image Storage 

– For Presentation 

Yes 

Yes 

Digital Intra-oral X-ray Image Storage 

– For Processing 

Yes 

Yes 

CT Image Storage Yes Yes 

Enhanced CT Image Storage Yes Yes 

Secondary Capture Image Storage Yes Yes 

Multi-frame Grayscale Byte 

Secondary Capture Image 

Yes 

Yes 

Storage 

2 / 55

SOREDEX 



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 

Information Model – FIND 

Yes 

No 

Patient Root Query/Retrieve 

Information Model – MOVE 

Yes 

No 

Study Root Query/Retrieve 

Information Model – FIND 

Yes 

No 

Study Root Query/Retrieve 

Information Model – MOVE 

Yes 

No 

Table 1-2 provides an overview of the Media Storage Application profiles supported by SCANORA. 

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 / 55

SOREDEX 



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 ................................................................................................................................ 13 

4.1.3 Sequencing of Real World Activities ...................................................................................................................... 15 

4.2 AE SPECIFICATIONS ................................................................................................................................................. 16 

4.2.1 SCANORA Client AE ............................................................................................................................................. 16 

4.2.2 SCANORA Storage SCP AE .................................................................................................................................. 33 

4.2.3 SCANORA Storage SCU AE .................................................................................................................................. 36 

4.3 NETWORK INTERFACES ................................................................................................................................................... 41 

4.3.1 Physical Network Interface .................................................................................................................................... 41 

4.4 CONFIGURATION ...................................................................................................................................................... 41 

4.4.1 AE title / presentation address mapping ................................................................................................................ 41 

4.4.2 Parameters ............................................................................................................................................................. 42 

5 MEDIA INTERCHANGE .............................................................................................................................................. 47 

5.1 IMPLEMENTATION MODEL .............................................................................................................................................. 47 

5.1.1 Application Data Flow Diagram ........................................................................................................................... 47 

5.1.2 Functional Definitions of AEs ................................................................................................................................ 47 

5.1.3 Sequencing of Real-World Activities ..................................................................................................................... 48 

5.1.4 File Meta Information Options .............................................................................................................................. 48 

5.2 AE SPECIFICATIONS ................................................................................................................................................. 49 

5.2.1 Application Entity Specification of SCANORA Media AE ..................................................................................... 49 

5.3 AUGMENTED AND PRIVATE APPLICATION PROFILES ..................................................................................... 51 

5.4 MEDIA CONFIGURATION ......................................................................................................................................... 52 

6 SUPPORT OF CHARACTER SETS ............................................................................................................................. 53 

7 SECURITY PROFILES .................................................................................................................................................. 54 

8 ANNEXES ........................................................................................................................................................................ 55 

8.1 IOD CONTENTS........................................................................................................................................................... 55 

8.2 DATA DICTIONARY AND PRIVATE ATTRIBUTES .............................................................................................. 55 

8.3 CODED TERMINOLOGY AND TEMPLATES .......................................................................................................... 55 

8.4 GRAYSCALE IMAGE CONSISTENCY ..................................................................................................................... 55 

8.5 STANDARD EXTENDED/SPECIALIZED/PRIVATE SOP CLASSES ..................................................................... 55 

8.6 PRIVATE TRANSFER SYNTAXES ............................................................................................................................ 55 

4 / 55

SOREDEX 



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 SCANORA software compliance to the DICOM requirements for the 

implementation of networking features. 

Section 5 Media Interchange, which specify the SCANORA 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 

http://dicom.nema.org. Comments on the Standard may be addressed to: 

DICOM Secretariat 

NEMA, Suite 1752 

1300 North. 17 th Street 

Rosslyn, VA 22209 

USA 

Phone: +1.703.841.3285 

5 / 55

SOREDEX 



3.2 REVISION HISTORY 

Revision Date Reason for Change Pages 

0.10 15.4.2008 First draft for Scanora. 29 

0.11 13.6.2008 Major editing, chapters rearranged, sequence diagrams added, 

data flow diagram redrawn and configurable parameters 

added. 

45 

0.12 18.9.2008 Document finalized for Scanora 3.1. 45 

0.13 30.9.2009 New features added: Storage Commitment SCU, ECT, 

Secondary Captures and CR. 

0.14 9.12.2010 N-Action of printing corrected. Added info of overlay 

graphics. New worklist query mode added. 

56 

55 

0.15 29.3.2011 Updated for SCANORA 5.0. 55 

6 / 55

SOREDEX 



3.3 AUDIENCE 

This document is written for the people that need to understand how SCANORA 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 SCANORA software 

implementation. This specification includes a DICOM Conformance Statement and is necessary to ensure 

proper processing and interpretation of SCANORA medical data exchanged using DICOM v3.0. The 

SCANORA 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 SCANORA implementation. If the user encounters unspecified private data elements while 

parsing a SCANORA 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 SCANORA software. 

3.5 REMARKS 

The scope of this DICOM Conformance Statement is to facilitate integration between SCANORA 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 / 55

SOREDEX 



3.6 REFERENCES 

NEMA PS3 Digital Imaging and Communications in Medicine (DICOM) Standard, available free at 

http://medical.nema.org/ 

SCANORA User Manual, available on the product CD-ROM. 

SCANORA Installation Manual, available on the product CD-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 / 55

SOREDEX 



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 / 55

SOREDEX 



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 / 55

SOREDEX 



4 NETWORKING 

4.1 IMPLEMENTATION MODEL 

4.1.1 Application Data Flow Diagram 

The network application model for SCANORA is shown in the following Illustration: 

11 / 55

SOREDEX 



12 / 55

SOREDEX 



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. 

SCANORA implementation utilizes MergeCOM-3 Tool Kit to accomplish the DICOM Services 

4.1.2.1 Functional Definition of SCANORA Client AE 

When an activity is invoked, SCANORA Client AE sends an association request to the remote application. If 

the association is accepted SCANORA 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, SCANORA 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 SCANORA 

— 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 SCANORA. 

4.1.2.2 Functional Definition of SCANORA Storage SCP AE 

SCANORA 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 SCANORA Storage SCU AE 

When an activity is invoked, SCANORA Storage SCU sends an association request to the remote 

application. If the association is accepted SCANORA requests for a DICOM operation related to the DICOM 

service that was invoked by the local real world activity. 

13 / 55

SOREDEX 



If the negotiated service is accepted, SCANORA transfers the real world activities to the specified remote 

Application Entity according to the DICOM protocol. 

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. 

SCANORA 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. 

14 / 55

SOREDEX 



4.1.3 Sequencing of Real World Activities 

A typical sequence of Real World Activities is shown in the diagram below: 

Storage SCP AE 

Storage SCU AE 

Client A 

Worklist provider 

PACS 

Printer 

Remote AE 

Verification 

Verification 

Request Worklist 

Receive Worklist 

Select Worklist item 

Acquire images 

Store images 

Request Storage Commitment 

Receive Storage Commitment Report 

Delete images from local database 

Print images 

Query for data 

Receive data 

Select images 

Request for image retrieve 

Receive Image 

Verification 

Receive Image 

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. 

• Storage Commitment Request needs to made before Storage Commitment Report can be 

received. 

— All other activities are independent of each other. 

15 / 55

SOREDEX 



— 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: SCANORA Client AE, Storage SCP AE and Storage SCU AE. 

4.2.1 SCANORA Client AE 

4.2.1.1 SOP Classes 

SCANORA Client AE provides standard conformance to the following Service Object Pair (SOP) Classes. 

TABLE 4-1: SOP CLASSES FOR SCANORA 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 


1.2.840.10008.5.1.4.1.1.7.2 Yes No 


Storage 


1.2.840.10008.5.1.4.1.1.7.3 Yes No 


Storage 


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 

Patient Root Query/Retrieve Information Model – 

MOVE 

1.2.840.10008.5.1.4.1.2.1.2 Yes No 

16 / 55

SOREDEX 



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 

SCANORA supports multiple associations as an SCU and SCP. When sending images SCANORA 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 SCANORA APPLICATION ENTITY 

SCANORA Implementation UID 1.2.246.512.3.1.2.0 

SCANORA Implementation Version Name 

SC_100 

17 / 55

SOREDEX 



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: 

Application Entity 

PACS 

Open association 

C-STORE 

Close association 

FIGURE 4-3: SEQUENCE OF ACTIVITY – STORAGE SCU 

The operator of SCANORA system initiates digital images storage on remote SCP from SCANORA 

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 

SCANORA Client AE is capable of proposing the Presentation Contexts shown in the following table: 

18 / 55

SOREDEX 



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 

Radiography 

1.2.840.10008. 

5.1.4.1.1.1 

Explicit VR Little Endian, 

Implicit VR Little Endian, 

Explicit VR Big Endian 

1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 

Digital X-Ray Image 

Storage – For 

Presentation 

1.2.840.10008. 

5.1.4.1.1.1.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 



Processing 

1.2.840.10008. 

5.1.4.1.1.1.1.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 

Digital Intra-oral X- 

Ray Image Storage - 

For Presentation 

1.2.840.10008. 

5.1.4.1.1.1.3 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 



For Processing 

1.2.840.10008. 

5.1.4.1.1.1.3.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 

CT Image Storage 1.2.840.10008. 

5.1.4.1.1.2 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 

Enhanced CT Image 

Storage 

1.2.840.10008. 

5.1.4.1.1.2.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 

Secondary Capture 

Image Storage 

1.2.840.10008. 

5.1.4.1.1.7 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 

Multi-frame 

Grayscale Byte 


Image 

Storage 

Multi-frame 

Grayscale Word 


Image 

Storage 

Multi-frame True 

Color 


Image 

Storage 

VL Photographic 

Image Storage 

1.2.840.10008. 

5.1.4.1.1.7.2 

1.2.840.10008. 

5.1.4.1.1.7.3 

1.2.840.10008. 

5.1.4.1.1.7.4 

1.2.840.10008. 

5.1.4.1.1.77.1. 

4 













1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

SCU 

SCU 

SCU 

None 

None 

None 

None 

19 / 55

SOREDEX 



4.2.1.3.1.3 SOP Specific Conformance 

The abstract syntax used, is based on the image type in Scanora, 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. 




— 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. 

4.2.1.3.2 Activity – Send Print Request 


A typical sequence is shown below. There can be several N-SET (Image Box) operations. 

20 / 55

SOREDEX 




Printer 


N-GET (Printer) 

N-CREATE (Film Session) 

N-CREATE (Film Box) 

N-SET (Image Box) 

N-ACTION (Film Box) 

Print film sheets 

N-EVENT-REPORT (Printer) 

N-DELETE (Film Session) 


FIGURE 4-4: SEQUENCE OF ACTIVITY – PRINT 

SCANORA operator selects the images to be printed to the remote Print SCP in SCANORA 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 

Print Management 

Meta 

1.2.840.10008. 

5.1.1.9 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 

Basic Color Print 

Management Meta 

1.2.840.10008. 

5.1.1.18 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 

21 / 55

SOREDEX 




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 

SCANORA 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 

SCANORA 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 

22 / 55

SOREDEX 



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 

SCANORA 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 

Format 

Annotation Display 

Format ID 

(2010,0010) ST STANDARD\1,1 STANDARD\C,R, 

where C is number of 

columns and R is the 

number of rows. 

(2010,0030) CS "" 

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 

Density 

(2010,0110) CS n/a BLACK, WHITE, I, where 

0..300 

Max Density (2010,0130) US 300 0..300 

Trim (2010,0140) CS n/a YES, NO 

23 / 55

SOREDEX 



Configuration 

Information 

Referenced Film 

Session Sequence 

Referenced SOP 

Class UID 

Referenced SOP 

Instance UID 

(2010,0150) ST LUT=0,3 

(2010,0500) SQ 

(0008,1150) UI 1.2.840.10008.5.1.1.1 

(0008,1155) UI n/a 

4.2.1.3.2.3.3 SOP Specific Conformance for the Basic Grayscale Image Box 

SCANORA 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.3.1 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 

Information 

(2010,0150) ST n/a 

Image Position (2020,0010) US 1 1..32 

Polarity (2020,0020) CS NORMAL NORMAL, REVERSE 

Requested Image 

Size 

Requested 

Decimate/Crop 

Behavior 

Basic Grayscale 

Image Sequence 

(2020,0030) DS n/a 

(2020,0040) CS n/a DECIMATE, CROP, FAIL 

(2020,0110) SQ n/a 

Samples Per Pixel (0028,0002) US 1 1 

Photometric 

Interpretation 

(0028,0004) CS MONOCHROME2 MONOCHROME2 

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 

24 / 55

SOREDEX 



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.4 SOP Specific Conformance for the Basic Color Image Box SOP Class 

SCANORA 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.4.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 

Decimate/Crop 

Behavior 

Basic Color Image 

Sequence 

(2020,0040) CS n/a DECIMATE, CROP, FAIL 

(2020,0111) SQ 

Samples Per Pixel (0028,0002) US 3 3 

Photometric 

Interpretation 

(0028,0004) CS RGB RGB 

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 

25 / 55

SOREDEX 



4.2.1.3.2.3.5 SOP Specific Conformance for the Printer SOP Class 

SCANORA 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.5.1 Printer SOP Class Operations (N-GET) 

SCANORA ClientAE uses the Printer SOP Class N-GET operation to obtain information about the current 

printer status. 

4.2.1.3.2.3.5.2 Printer SOP Class Notifications (N-EVENT-REPORT) 

SCANORA 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. 


Worklist provider 


C-FIND request 

C-FIND response(s) - Status=Pending 

C-FIND response - Status=Completed 


Select worklist item 

FIGURE 5: SEQUENCE OF ACTIVITY – WORKLIST 

SCANORA may be configured to poll the worklist provider for worklist data in intervals or only when the 

operator needs the latest worklist. 

26 / 55

SOREDEX 



4.2.1.3.3.2 Proposed Presentation Contexts 

SCANORA Client AE proposes the Presentation Context shown in the following table: 

TABLE 4-12: PRESENTATION CONTEXT TABLE OF WORKLIST 



Negotiation 


Modality Worklist 

Information Model – 

FIND 

1.2.840.10008. 

5.1.4.31 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 

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 

Time 

(0040,0003) TM R R 

Modality (0008,0060) CS (S) (S) x 

Scheduled Performing Physician’s 

Name 

Scheduled Procedure Step 

Description 

(0040,0006) PN (S,*) x 

(0040,0007) LO x 

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 

27 / 55

SOREDEX 



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 

Sequence 

(0032,1064) SQ x 

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 

Data Description 

(0040,3001) LO x 

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 

28 / 55

SOREDEX 



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 SCANORA 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 

SCANORA 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 SCANORA 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. 

29 / 55

SOREDEX 




Archive 


C-FIND Request 

C-FIND Response(s) 


Select images 


C-MOVE Request 

C-MOVE Response 


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 

Query/Retrieve 


FIND 

1.2.840.10008. 

5.1.4.1.2.1.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 

30 / 55

SOREDEX 



Patient Root 



MOVE 

Study Root 



FIND 

Study Root 



MOVE 

1.2.840.10008. 

5.1.4.1.2.1.2 

1.2.840.10008. 

5.1.4.1.2.2.1 

1.2.840.10008. 

5.1.4.1.2.2.2 










1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

SCU 

SCU 

None 

None 

None 

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 

Matching 

Patient level 

Study level 

Series level 

Image level 

Available in 

the GUI 

Patient Name 0010,0010 PN S,*,U Yes 

Patient ID 0010,0020 LO S,*,U Yes 



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 



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 



31 / 55

SOREDEX 




Matching 

Patient level 

Available in 

the GUI 



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 

Study level 

Series level 

Image level 

Available in 

the GUI 



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 



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 



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. 

32 / 55

SOREDEX 



SCANORA AE does not support relational queries. SCANORA 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 


SCANORA Client AE initiates Associations for the purpose of verifying a DICOM connection. 

4.2.1.3.5.2 Proposed presentation context 

SCANORA 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. 

1.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 

4.2.1.3.5.3 SOP specific conformance 

SCANORA Client AE provides standard conformance to the DICOM Verification Service Class as an SCU. 

4.2.1.4 Association Acceptance Policy 

SCANORA Client AE does not accept any associations. 

4.2.2 SCANORA Storage SCP AE 


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 

Presentation 

1.2.840.10008.5.1.4.1.1.1.3 No Yes 

33 / 55

SOREDEX 



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 


1.2.840.10008.5.1.4.1.1.7.2 No Yes 


Storage 


1.2.840.10008.5.1.4.1.1.7.3 No Yes 


Storage 


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. 


SCANORA 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 



Remote AE 


C-STORE 


FIGURE 7: SEQUENCE OF ACTIVITY – STORAGE SCP 

Associations are accepted in order to receive images from remote AEs. The received images are stored in 

SCANORA database. 

34 / 55

SOREDEX 



4.2.2.4.1.2 Accepted Presentation Contexts 

SCANORA AE will accept Presentation Contexts as shown in the table below. 

TABLE 4-19: PRESENTATION CONTEXT TABLE OF STORAGE SCP 



Negotiation 


Computed Radiography 

Image Storage 

1.2.840.10008. 

5.1.4.1.1.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCP 

None 



Presentation 

1.2.840.10008. 

5.1.4.1.1.1.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCP 

None 



Processing 

1.2.840.10008. 

5.1.4.1.1.1.1.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCP 

None 



For Presentation 

1.2.840.10008. 

5.1.4.1.1.1.3 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCP 

None 



For Processing 

1.2.840.10008. 

5.1.4.1.1.1.3.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCP 

None 

CT Image Storage 1.2.840.10008. 

5.1.4.1.1.2 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCP 

None 

Enhanced CT Image 

Storage 

1.2.840.10008. 

5.1.4.1.1.2.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCP 

None 


Image Storage 

1.2.840.10008. 

5.1.4.1.1.7 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCP 

None 

Multi-frame Grayscale 

Byte 


Image 

Storage 

Multi-frame Grayscale 

Word 


Image 

Storage 



Image 

Storage 

1.2.840.10008. 

5.1.4.1.1.7.2 

1.2.840.10008. 

5.1.4.1.1.7.3 

1.2.840.10008. 

5.1.4.1.1.7.4 










1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCP 

SCP 

SCP 

None 

None 

None 

35 / 55

SOREDEX 



VL Photographic 

Image Storage 

1.2.840.10008. 

5.1.4.1.1.77.1. 

4 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCP 

None 


To be defined. 

4.2.2.4.2 Activity – Receive Verification 


SCANORA 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. 

1.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCP 

None 


SCANORA 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 SCANORA Storage SCU AE 


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 

36 / 55

SOREDEX 



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 


1.2.840.10008.5.1.4.1.1.7.2 Yes No 


Storage 


1.2.840.10008.5.1.4.1.1.7.3 Yes No 


Storage 


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: 

37 / 55

SOREDEX 



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. 


SCANORA 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 

Push Model 

1.2.840.10008. 

1.20.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 


The supported operations are described below. 

38 / 55

SOREDEX 



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 

Commitment 

Request Successful 

Storage 

Commitment 

Request Complete - 

Failures Exist 

1 The References SOP Instances under References SOP Sequence 

(0008,1199) are considered as 'Committed' in the SCANORA database. 

SCANORA 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. 

2 The References SOP Instances under References SOP Sequence 

(0008,1199) are treated the same way as in the success case (Event Type 

1). The referenced SOP Instances under Failed SOP Sequence 

(0008,1198) are considered as 'Commitment failed''. These images will 

not be deleted. SCANORA 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. 

39 / 55

SOREDEX 




4.2.3.4.1 Activity – Receive Storage Commitment Result 



FIGURE 9: SEQUENCE OF ACTIVITY – RECEIVING STORAGE COMMITMENT RESULT 

SCANORA 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. 


SCANORA 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 

Push Model 

1.2.840.10008. 

1.20.1 




1.2.840.10008.1.2, 

1.2.840.10008.1.2.1, 

1.2.840.10008.1.2.2 

SCU 

None 

40 / 55

SOREDEX 




SCANORA 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 

SCANORA uses the AE Titles configured via the settings dialog of SCANORA 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 

SCANORA Client AE SCANORA_DICOM n/a 

SCANORA 

SCP AE 

SCANORA 

SCU AE 

Storage 

Storage 

SCANORA_DICOM 105 

no default value 106 

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 SCANORA software. 

41 / 55

SOREDEX 



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 SCANORA 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 3 s 

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 

42 / 55

SOREDEX 



Parameter 

Configurable 

(Yes/No) 

Write timeout Yes 15 s 

Inactivity timeout Yes 15 s 

Default Value 

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 

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 


28672 bytes 

send 











Retry count due to failed storage Yes 2 

Retry interval due to failed storage Yes 30 

43 / 55

SOREDEX 



Parameter 

Configurable 

(Yes/No) 

Default Value 


Service 

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 


28672 bytes 

send 











44 / 55

SOREDEX 



Parameter 

Number of simultaneous associations by 

Service 

Basic grayscale print management and/or 

basic color print management 

Configurable 

(Yes/No) 

No 1 

Query / Retrieve Parameters 

Default Value 

Yes Basic Grayscale Print 

Management 


28672 bytes 

send 











Query Model Yes Patient 

Scheduled retrieve task retry limit Yes 2 

Scheduler retrieve task retry interval Yes 30 


Service 

Storage SCP Parameters 


28672 bytes 

send 











Number of simultaneous associations by 

Service 

No 1 

45 / 55

SOREDEX 



The following retired tags can be selected for use: 

— 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. 

46 / 55

SOREDEX 



5 MEDIA INTERCHANGE 

This section of the DICOM conformance statement specifies the SCANORA 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 

SCANORA Media AE displays the contents of DICOM Storage Medium and reads the images saving them 

to local database. 

SCANORA 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 SCANORA, 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 SCANORA, 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. 

For importing and exporting individual image files, please refer to the SCANORA user manual. 

47 / 55

SOREDEX 



5.1.3 Sequencing of Real-World Activities 

Media AE 

Medium 

Create Media 

Display Directory 

Display Directory 

Read Media 

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: 

SCANORA Implementation UID 1.2.246.512.3.1.2.0 

SCANORA Implementation Version Name 

SC_102 

48 / 55

SOREDEX 



5.2 AE SPECIFICATIONS 

5.2.1 Application Entity Specification of SCANORA Media AE 

The SCANORA 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 

Application Profile 

Real World 

Activity 

Role SC Option 

STD-GEN-CD Display Directory FSR Interchange 

STD-GEN-DVD-RAM 

STD-GEN-CD Create Media FSC Interchange 


STD-GEN-CD Read Media FSR Interchange 


5.2.1.1 File Meta Information for the application entity 

When File Meta Information is created the SC_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 

SCANORA Media AE acts as an FSR when requested to view SOP instances from DICOM storage media. 

The SCANORA 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 

SCANORA 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. 

49 / 55

SOREDEX 



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 

Presentation 

Digital X-Ray Image Storage – For 

Processing 

Digital Intra-oral X-Ray Image Storage 

- For Presentation 

Digital Intra-oral X-Ray Image Storage 

- For Processing 

1.2.840.10008.5.1.4.1.1.1.1 Explicit VR 

Little Endian 

1.2.840.10008.5.1.4.1.1.1.1.1 Explicit VR 

Little Endian 

1.2.840.10008.5.1.4.1.1.1.3 Explicit VR 

Little Endian 

1.2.840.10008.5.1.4.1.1.1.3.1 Explicit VR 

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 



Storage 



Storage 



Storage 

1.2.840.10008.5.1.4.1.1.7.2 Explicit VR 

Little Endian 

1.2.840.10008.5.1.4.1.1.7.3 Explicit VR 

Little Endian 

1.2.840.10008.5.1.4.1.1.7.4 Explicit VR 

Little Endian 

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 

SCANORA Media AE acts as an FSR when requested to read SOP instances from DICOM storage media. 

The SCANORA 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 

SCANORA software user interface. After the operator selects the information from the SCANORA software 

user interface, the information is stored in local SCANORA database. 


See application profile table in chapter: 5.2.1. 

50 / 55

SOREDEX 



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 

SCANORA Media AE acts as an FSC when requested to export SOP instances from local database to 

DICOM storage medium. 

SCANORA operator selects from the SCANORA 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, SCANORA 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 Scanora, and can be configured as follows: 

— Panoramic and cephalometric images: 




— Intraoral images: 

o Digital Intra-oral X-Ray Image Storage - either For Presentation or For Processing, 

depending on 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. 

51 / 55

SOREDEX 



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. 

52 / 55

SOREDEX 



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 

53 / 55

SOREDEX 



7 SECURITY PROFILES 

SCANORA 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)) 

54 / 55

SOREDEX 



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 SC_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 

SCANORA does not support the Grayscale Standard Display Function 

8.5 STANDARD EXTENDED/SPECIALIZED/PRIVATE SOP CLASSES 

SCANORA does not claim conformance to any Extended, Specialized or Private SOP Classes. 

8.6 PRIVATE TRANSFER SYNTAXES 

SCANORA does not employ any Private Transfer Syntaxes. 

55 / 55

scanora 5.0 dicom conformance statement - Soredex

Create successful ePaper yourself

Delete template?

Save as template?