DICOM CONFORMANCE STATEMENT

Transcription

1 DICOM CONFORMANCE STATEMENT PRODUCT DETAILS: Product type: Data Analysis Software Product Name: TOMTEC-ARENA TTA2 MANUFACTURER: TOMTEC IMAGING SYSTEMS GMBH Edisonstrasse Unterschleissheim USED STANDARDS: ACR-NEMA Digital Imaging and Communications in Medicine, DICOM V3.0 We declare under sole responsibility that the product listed above is in compliance with DICOM 3.0 Unterschleissheim, ROLF BAUMANN, CTO TOMTEC IMAGING SYSTEMS GMBH Edisonstrasse Unterschleissheim Deutschland/Germany o f e info@tomtec.de w

2 1 TABLE OF CONTENTS 1 TABLE OF CONTENTS Introduction Intended Audience Acronyms, Abbreviations References 3 3 SOP Classes Support for Extended Character Sets Overview Character Sets Character Set Configuration 5 5 Security Annexes IOD Contents Usage of attributes from received IOD s Attribute Mapping Coerced / Modified Fields Data Dictionary of Private Attributes Coded Terminology and Templates Grayscale Image Consistency Standard Extended / Specialized / Private SOP Classes Private Transfer Syntaxes Private Context Mapping Resources 6 Copyright 2016 TOMTEC IMAGING SYSTEMS GMBH ALL RIGHTS RESERVED D DICOM_CONF_TOMTEC-ARENA_TTA2 PAGE 2/6

3 2 INTRODUCTION This document describes the conformance of the product TOMTEC-ARENA to the ACR-NEMA DICOM standard and satisfies the DICOM requirement for a vendor conformance specification. 2.1 INTENDED AUDIENCE The reader of this document is involved with design of medical software or medical system integration. We assume that the reader is familiar with the DICOM 3.0 standard terminology and concepts. Experience and familiarity with DICOM conformance statements in general is helpful but not necessarily required. 2.2 ACRONYMS, ABBREVIATIONS The following acronyms and abbreviations are used in this document: ACR American College of Radiology AE Application Entity DICOM Digital Imaging and Communications in Medicine DIMSE DICOM Message Service Element FSC File-set Creator FSR File-set Reader FSU File-set Updater GUI Graphic User Interface IHE Integrating the Healthcare Enterprise IOD Information Object Definition ISO International Standards Organization MPPS Modality Performed Procedure Step MWL Modality Worklist NEMA National Electrical Manufacturers Association PDU Protocol Data Unit PIR Patient Information Reconciliation SCU Service Class User SCP Service Class Provider SOP Service-Object Pair TCP/IP Transmission Control Protocol/Internet Protocol UID Unique Identifier VM Value Multiplicity VR Value Representation 2.3 REFERENCES [DICOM] This document is written with respect to the ACR-NEMA Digital Imaging and Communications in Medicine (DICOM) version number 3.0. [IHE] IHE Cardiology Technical Framework Year 2: , Volume I Integration Profiles, Revision 2.0, Trial Implementation Version, Publication Date: June 27, 2005 D DICOM_CONF_TOMTEC-ARENA_TTA2 PAGE 3/6

4 3 SOP CLASSES TOMTEC-ARENA provides Standard Conformance regarding import and display to the following DICOM V3.0 Storage SOP Classes: SOP Class UID Description Toshiba Private Data Storage EncapsulatedPDFStorage XRayAngiographicImageStorage Nuclear Medicine Image Storage RETIRED_UltrasoundMultiframeImageStorag UltrasoundMultiframeImageStorage RETIRED_UltrasoundImageStorage UltrasoundImageStorage Enhanced US Volume Storage RawDataStorage (Files are accepted but not imported) SecondaryCaptureImageStorage MultiframeSingleBitSecondaryCaptureImageStorage MultiframeGrayscaleByteSecondaryCaptureImageStorage MultiframeGrayscaleWordSecondaryCaptureImageStorage MultiframeTrueColorSecondaryCaptureImageStorage BasicTextSR EnhancedSR DRAFT_SRTextStorage DRAFT_SRAudioStorage DRAFT_SRDetailStorage ComprehensiveSR HP_LIVE_3D_ HP_LIVE_3D_ HAM Line Data (105) HAM Line Data (110) TOMTEC-ARENA provides Standard Conformance regarding creation and export to the following DICOM V3.0 Storage SOP Classes: SOP Class UID Description SecondaryCaptureImageStorage MultiframeTrueColorSecondaryCaptureImageStorage ComprehensiveSR D DICOM_CONF_TOMTEC-ARENA_TTA2 PAGE 4/6

5 4 SUPPORT FOR EXTENDED CHARACTER SETS 4.1 OVERVIEW TOMTEC-ARENA supports a couple of extended character sets defined in the DICOM 3.0 standard, including singlebyte and multi-byte character sets as well as code extension techniques using ISO 2022 escapes. Support extends to correctly decoding and displaying the correct symbol for all names and strings found in the DICOMDIR, in storage instances from media and received over the network, and in the local database. No specific support for sorting of strings other than in the default character set is provided in the browsers. 4.2 CHARACTER SETS In addition to the default character repertoire, the Defined Terms for Specific Character Sets in Table are supported. TOMTEC-ARENA uses the Qt Development Toolkit to decode and visualize extended character sets. Character Set Description Defined Term Qt Codec Used Latin alphabet No. 1 ISO_IR 100 ISO Latin alphabet No. 2 ISO_IR 101 ISO Latin alphabet No. 3 ISO_IR 109 ISO Latin alphabet No. 4 ISO_IR 110 ISO Latin alphabet No. 5 ISO_IR 148 ISO Latin ISO 2022 IR 100 TIS-620 ÂSCII ISO_IR 6 UTF-8 UTF-8 ISO_IR 192 UTF-8 Cyrillic ISO_IR 144 ISO Arabic ISO_IR 127 ISO Greek ISO_IR 126 ISO Hebrew ISO_IR 138 ISO Chinese GB18030 GB Default repertoire ISO 2022 IR 6 ISO 2022-JP Japanese ISO 2022 IR 13 ISO 2022-JP Japanese ISO 2022 IR 87 ISO 2022-JP Japanese ISO 2022 IR 149 ISO 2022-JP Japanese ISO 2022 IR 159 ISO 2022-JP Thai ISO 2022 IR 166 TIS-620 Thai ISO_IR 166 TIS-620 Table 6.2-1: Supported Specific Character Set Defined Terms 4.3 CHARACTER SET CONFIGURATION Whether or not characters are displayed correctly depends on the presence of font support in the underlying operating system. Typically, it may be necessary for the user to add some Unicode fonts to their system configuration in order to correctly display characters that would not typically be used in the default locale. D DICOM_CONF_TOMTEC-ARENA_TTA2 PAGE 5/6

6 5 SECURITY TOMTEC-ARENA does not support any specific security measures. Application level security: not supported. 6 ANNEXES 6.1 IOD CONTENTS Usage of attributes from received IOD s The local database uses the conventional identification attributes to distinguish patients, studies, series and instances. If two patients have the same values for all identification fields they will be treated as the same in the local database. If only part of these coincide, they will be treated as two separate patients Attribute Mapping Attribute mapping does not take place Coerced / Modified Fields TOMTEC-ARENA does not modify any fields, no coercion is performed. 6.2 DATA DICTIONARY OF PRIVATE ATTRIBUTES TOMTEC-ARENA does not write any private attributes. 6.3 CODED TERMINOLOGY AND TEMPLATES TOMTEC-ARENA does not use any codes or controlled terminology. 6.4 GRAYSCALE IMAGE CONSISTENCY TOMTEC-ARENA does not make use of the DICOM Grayscale Standard Display Function. 6.5 STANDARD EXTENDED / SPECIALIZED / PRIVATE SOP CLASSES Not applicable. 6.6 PRIVATE TRANSFER SYNTAXES TOMTEC-ARENA does not use any private transfer syntaxes. 6.7 PRIVATE CONTEXT MAPPING RESOURCES TOMTEC-ARENA does not use any private context mapping resources. D DICOM_CONF_TOMTEC-ARENA_TTA2 PAGE 6/6