00 441024 01 FluorostarDicomConfStat 051219

GE Medical Systems DICOM CONFORMANCE GE OEC Fluorostar Systems
STATEMENT Page 1 of 34
Technical
Publications
00-441024-01
Revision 051219
GE OEC Fluorostar
CONFORMANCE STATEMENT
for DICOM
Copyright 2004 by General Electric Co.

1 INTRODUCTION ......................................................................................................................................... 6
1.1 REVISION HISTORY .................................................................................................................................. 6
1.2 AUDIENCE ................................................................................................................................................ 6
1.3 SCOPE AND FIELD OF APPLICATION.............................................................................................. 6
1.4 IMPORTANT REMARKS...................................................................................................................... 6
1.5 DEFINITIONS, TERMS AND ABBREVIATIONS ............................................................................................. 7
1.6 REFERENCES ............................................................................................................................................ 7
1.7 FUNCTIONALITY IN BRIEF ......................................................................................................................... 7
2 NETWORKING ............................................................................................................................................ 9
2.1 IMPLEMENTATION MODEL .............................................................................................................. 9
2.1.1 Application Data Flow .................................................................................................................... 9
2.1.2 Functional Definitions of the FLUOROSTAR AE............................................................................ 9
2.2 AE SPECIFICATIONS ......................................................................................................................... 10
2.2.1 FLUOROSTAR AE Specification................................................................................................... 10
2.3 NETWORK INTERFACES .......................................................................................................................... 11
2.3.1 Physical Network Interface............................................................................................................ 11
2.3.2 Additional Protocols...................................................................................................................... 12
2.3.3 SUPPORT OF CHARACTER SETS .............................................................................................. 12
2.4 CONFIGURATION .................................................................................................................................... 12
2.4.1 AE Connection Parameter ............................................................................................................. 12
2.5 DICOM MESSAGE TRANSFER IN DETAIL ............................................................................................... 13
3 FLUOROSTAR REALIZED DICOM SERVICES.................................................................................. 14
3.1 DICOM ECHO........................................................................................................................................ 14
3.1.1 General Echo Features.................................................................................................................. 14
3.1.2 Limitations of Echo Service ........................................................................................................... 14
3.1.3 Description and Sequencing of Activities ...................................................................................... 14
3.1.4 SOP Specific Conformance............................................................................................................ 14
3.2 DICOM PRINT SERVICE ......................................................................................................................... 14
3.2.1 General Print Features.................................................................................................................. 14
3.3 DICOM IMAGE STORE SERVICE ....................................................................................................... 16
3.3.1 General Image Store Features....................................................................................................... 16
3.3.2 Limitations of Image Store Service................................................................................................ 16
3.4 DICOM WORKLIST SERVICE ................................................................................................................. 21
3.4.1 General Worklist Features ............................................................................................................ 21
3.4.2 Limitations of Worklist Service...................................................................................................... 21
4 ERROR HANDLING.................................................................................................................................. 25
4.1 APPLICATION ERROR MESSAGES............................................................................................................ 25
4.2 PROGRAM INTERNAL ERROR CODES ...................................................................................................... 25
4.3 DICOM ERROR CODES .......................................................................................................................... 26
4.4 ERROR TRACES ...................................................................................................................................... 30
5 SECURITY .................................................................................................................................................. 31
6 ANNEXES .................................................................................................................................................... 32
6.1 IOD CONTENTS ...................................................................................................................................... 32
6.1.1 Usage of attributes from received IOD’s....................................................................................... 32
6.1.2 Attribute Mapping.......................................................................................................................... 32
6.1.3 Coerced/Modified fields................................................................................................................. 32
6.2 DATA DICTIONARY OF PRIVATE ATTRIBUTES ........................................................................................ 32
6.3 CODED TERMINOLOGIES AND TEMPLATES ............................................................................................. 32
6.4 GRAYSCALE IMAGE CONSISTENCY ......................................................................................................... 32
6.5 STANDARD EXTENDED / SPECIALIZED / PRIVATE SOP CLASSES ............................................................ 32

6.6 PRIVATE TRANSFER SYNTAXES .............................................................................................................. 32
MergeCOM is a registered trademark of Merge Technologies Incorporated (d/b/a Merge eFilm)

Linux is a registered trademark of Linus Torwalds.
WINDOWS is a registered trademark of Microsoft Corporation
Document Id.: GE-OEC-FluorostarConfStat-2730
Project: 2730-DICOM-Communication Library
Author: U. Fleisch (UF)

Version: 0.8
Pages: 34
Status: DRAFT
Date: 19.12.05
Changes:
UF: 21.02.2005 Samples of Message Transfer
New: Device Name Filter for Worklist (0040,0001 Scheduled Station AE Title)
UF/MK:19.12.2005 CHANGED: SOP Specific Conformance for Print, Store and Worklist
ToDo Detailed list of all used message tags for all defined services (currently incomplete)
Part-Number 00-441024-01
Conformance Statement Overview

Fluorostar is a mobile X-Ray system.
Fluorostar implements the necessary services to communicate via DICOM
• to request Worklists from the Worklist Servers

• to find studies on a DICOM connected database
• to upload selected images to the DICOM-Image Server
• to print fluoroscopic grayscale images at a DICOM printer
This document is intended to describe Fluorostar conformance to DICOM.
Table 1-1 provides an overview of the network services supported by Fluorostar

SOP Classes
Store
Computed Radiography Image Storage
Print
Basic Grayscale Print
Worklist
Modality Worklist Information Model – FIND
1 Introduction
1.1 Revision History

Document Version Date of issue Author Description
0.1 09/2004 UF Initial Version
0.7 12/2005 UF Buffer Size Description Changed
0.8 12/2005 UF
1.2 Audience
This document is indented for hospital staff, health system integrators, software designers or implementers. The
reader of this document is concerned with software design and/or system integration issues. It is assumed that the
reader of this document is familiar with the DICOM Standard and with the terminology and concepts that are
used in that Standard.
If readers are unfamiliar with DICOM terminology they should first refer to the GE document listed below, then
read the DICOM Standard itself, prior to reading this DICOM Conformance Statement document.
1.3 SCOPE AND FIELD OF APPLICATION

It is the intent of this document, in conjunction with the GE document, Introduction to the Integrated
DICOM/Network v3.0 (ID/Net v3.0) Conformance Statement, Direction: 2118780, to provide an unambiguous
specification for GE implementations. This specification, called a Conformance Statement, includes a DICOM
Conformance Statement and is necessary to ensure proper processing and interpretation of GE medical data
exchanged using DICOM. The GE Conformance Statements are available to the public.
The reader of this DICOM Conformance Statement should be aware that different GE devices are capable of
using different Information Object Definitions. For example, a GE CT Scanner may send images using the CT
Information Object, MR Information Object, Secondary Capture Object, etc.
Included in this DICOM Conformance Statement are the Module Definitions, which define all data elements,
used by this GE implementation. If the user encounters unspecified private data elements while parsing a GE
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 GE devices.
1.4 IMPORTANT REMARKS

The use of these DICOM Conformance Statements, in conjunction with the DICOM Standards, is intended to
facilitate communication with GE imaging equipment. However, by itself, it is not sufficient to ensure that
inter-operation will be successful. The user (or user's agent) needs to proceed with caution and address at
least four issues:
• Integration - The integration of any device into an overall system of interconnected devices goes beyond
the scope of standards (DICOM), and of this introduction and associated DICOM Conformance Statements
when interoperability with non-GE equipment is desired. The responsibility to analyze the applications
requirements and to design a solution that integrates GE imaging equipment with non–GE systems is the
user's responsibility and should not be underestimated. The user is strongly advised to ensure that such an
integration analysis is correctly performed.
• Validation - Testing the complete range of possible interactions between any GE device and non–GE
devices, before the connection is declared operational, should not be overlooked. Therefore, the user should
ensure that any non–GE provider accepts full responsibility for all validation required for their connection
with GE devices. This includes the accuracy of the image data once it has crossed the interface between the
GE imaging equipment and the non–GE device and the stability of the image data for the intended
applications. Such a validation is required before any clinical use (diagnosis and/or treatment) is performed.
It applies when images acquired on GE imaging equipment are processed/displayed on a non-GE device, as
well as when images acquired on non-GE equipment is processed/displayed on a GE console or workstation.
• Future Evolution – GE understands that the DICOM Standard will evolve to meet the user's growing
requirements. GE is actively involved in the development of the DICOM Standards. DICOM will
incorporate new features and technologies and GE may follow the evolution of the Standard. The GE
protocol is based on DICOM as specified in each DICOM Conformance Statement. Evolution of the
Standard may require changes to devices which have implemented DICOM. In addition, GE reserves the
right to discontinue or make changes to the support of communications features, on its products, as
described by these DICOM Conformance Statements. The user should ensure that any non–GE provider,
which connects with GE devices, also plans for the future evolution of the DICOM Standards. Failure to do
so will likely result in the loss of function and/or connectivity as the DICOM Standards change and GE
products are enhanced to support these changes.
• Interaction - It is the sole responsibility of the non–GE provider to ensure that communication with the
interfaced equipment does not cause degradation of GE imaging equipment performance and/or function.
1.5 Definitions, Terms and Abbreviations

Definitions, terms and abbreviations used in this document are defined within the different part of the DICOM
standard.
AE DICOM Application Entity
IE Information Entity
IOD (DICOM) Information Object Definition
ISO International Standard Organization
NEMA National Electrical Manufactures Association
PACS Picture Archiving and Communication System
PDU Protocol Data Unit
SCU DICOM Service Class User (DICOM client)
SCP DICOM Service Class Provider (DICOM server)
SOP DICOM Service-Object Pair
VR Value Representation
1.6 References
[DICOM] Digital Imaging and Communications in Medicine (DICOM), NEMA PS 3.1-3.16, 2003
MergeCOM-3 Advanced Integrator’s Tool Kit User’s Manual
1.7 Functionality in brief
• PRINT
Print Grayscale Images with 1x1 – 4x5 pictures at one film.
DicomService: PRINTER, BASIC_FILM_SESSION_CREATE, BASIC_FILM_SESSION_SET, BASIC_FILM_BOX_CREATE,
BASIC_FILM_BOX_SET, BASIC_GRAYSCALE_IMAGE_BOX
• WORKLIST
Manually get worklist from worklist server, specify date, set filter for station name and physician name.
DicomService: MODALITY_WORKLIST_FIND, SCHEDULED_PROCEDURE_STEP
• STORE
Store Images for a defined patient to a new or existing study
DicomService: STANDARD_XRAY_RF - C_STORE_RQ, PREFORMATTED_GRAYSCALE_IMAGE
2 NETWORKING
2.1 IMPLEMENTATION MODEL

Fluorostar is implemented in one Application entity.
2.1.1 Application Data Flow

FLUOROSTAR initiates the association to remote PACS. When the association is established, FLUOROSTAR
may request the storing of an image or request to receive patient data or to print images to the remote
Application Entity.
Association Initiation
Grayscale Remote
PRINT PRINT Real-World
AE Activity X
Remote
Worklist Worklist Real-World
AE Activity Y
Store Remote
Image Image Real-World
AE Activity Z
DICOM
Standard
Association Acceptance Interface
2.1.2 Functional Definitions of the FLUOROSTAR AE

FLUOROSTAR supports the export of all images generated with FLUOROSTAR via a DICOM online
communication.
If an image export request is made, FLUOROSTAR sends an association request to the destination
AE. If an association has been established successfully, FLUOROSTAR translates the image and
image related data into a DICOM message and sends it. After the images have been sent
FLUOROSTAR closes the association. If the association cannot be opened, the related export attempt
is cancelled.
Worklist requests are not done periodically by FLUOROSTAR. For each worklist request,
FLUOROSTAR sends an association request to the destination AE. If an association has been
established successfully, FLUOROSTAR queries the worklist data. After the requested worklist data
have been received, FLUOROSTAR closes the association. If the association cannot be opened, the
related worklist request attempt is cancelled.
2.2 AE SPECIFICATIONS
This section describes the FLUOROSTAR Application Entity
2.2.1 FLUOROSTAR AE Specification

2.2.1.1 SOP Classes
FLUOROSTAR provides Standard Conformance always as an user of Service (SCU) to the following
DICOM SOP Classes:
Table 2-1: SOP classes for FLUOROSTAR AE
SOP Classes SOP Class UIP

Transfer
X-Ray Radiofluoroscopic Image Storage 1.2.840.10008.5.1.4.1.1.12.2
Worklist
Modality Worklist Information Model – FIND 1.2.840.10008.5.1.4.31
Print
Printer SOP Class 1.2.840.10008.5.1.1.16
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
Echo
STANDARD ECHO 1.2.840.10008.1.1
2.2.1.2 Association Policies
2.2.1.2.1 General
The DICOM standard application context name for DICOM 3.0 is always proposed and accepted.
Application Context Name 1.2.840.10008.3.1.1.1
FLUOROSTAR provides Standard Conformance always as an User Of Service (SCU) and uses
always the Transfer Syntax Implicit Little Endian! Extended Negotiation is not supported
General FLUOROSTAR Presentation Context

Transfer Syntax
Name List UID List Role Extended Negotiation
Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
2.2.1.2.2 Number of Associations

FLUOROSTAR initiates one simultaneous association at a time for each destination to which a request is being
processed.
2.2.1.2.3 Asynchronous Nature

The FLUOROSTAR does not support asynchronous operations (multiple outstanding transactions over a single
association).
2.2.1.2.4 Implementation Identifying Information

Implementation Class UID 1.2.840.113780.100
Implementation Version Name 1.2.840.10008.3.1.1.1
Service Notice: Implementation Information can be found inside the ASSOC_PARMS of the
MergeCom- Initialisation file “MergeCom.Pro”
[ASSOC_PARMS]
IMPLEMENTATION_CLASS_UID = 1.2.840.113780.100
IMPLEMENTATION_VERSION = OEC_FLUOROSTAR
LOCAL_APPL_CONTEXT_NAME = 1.2.840.10008.3.1.1.1
2.2.1.3 Association Initiation Policy
2.2.1.3.1 Activity – Export Images
2.2.1.3.1.1 Description and Sequencing of Activities

FLUOROSTAR supports the manual image export.
If an image should be stored on a PACS, FLUOROSTAR makes a C-STORE request to the

destination AE. If the association cannot be opened, the export is cancelled.
If an association has been established successfully, FLUOROSTAR translates the image and image
related data into a DICOM message and sends it.
2.2.1.3.1.2 Proposed Presentation Contexts

FLUOROSTAR is capable of proposing the presentation contexts shown below.
Presentation Context Table
Abstract Syntax Transfer Syntax Role Extended
Negotiation
Name UID Name List UID List
X-Ray 1.2.840.10008. Implicit VR 1.2.840.10008.1.2 SCU None
Radiofluoroscopic 5.1.4.1.1.12.2 Little Endian
Image Storage
The presentation context actually proposed depends on a setting in FLUOROSTAR.

2.2.1.3.1.2.1 Transfer Syntax Selection Policies
To external systems, FLUOROSTAR selects only “Implicit Little Endian” as Transfer Syntax.
2.3 Network Interfaces
2.3.1 Physical Network Interface

All physical network interfaces supported by the LINUX System can be used.
2.3.2 Additional Protocols

Where host names rather than IP addresses are used in the configuration properties to specify
presentation addresses for remote AE’s, the application is dependent on the name resolution
mechanism of the underlying operating system.
2.3.3 SUPPORT OF CHARACTER SETS

FLUOROSTAR supports the character set “ISO 8859 Latin 1 (ISO-IR 100)”.
2.4 Configuration
2.4.1 AE Connection Parameter

FLUOROSTAR can use different AE titles for different connections. Following AE Titles and communication
Parameters can be administered using the FLUOROSTAR-DICOM-Setup.
2.4.1.1 Local Application Title

A different AE Title has to be administered for each FLUOROSTAR workstation. This setting can be changed in
FLUOROSTAR DICOM-Setup.
2.4.1.2 Remote Application Title

AE Title of the service class provider. A special AE Title (different from the FLUOROSTAR workstations) has
to be set to communicate with this provider. This setting can also be changed in FLUOROSTAR DICOM-Setup.
2.4.1.3 Host Name

I/P-Address (format: nnn.nnn.nnn.nnn where 0<= nnn <=255)
If a Domain Name Server is active you can use the domain name instead of the ip address!
2.4.1.4 Port Number

Enter the port which is defined at the provider for the required service. The default port reserved for NEMA
applications is 104
You can configure up to 10 servers for each of the DICOM Services PRINT and STORE.
You can configure 1 server for the DICOM Service WORKLIST.
The Server Parameters can be edited by FLUOROSTAR and are stored inside the device dependent
configuration files.
You can add an TIMEOUT-Parameter to define a special timeout for each defined server.
Server-aliasname.ini:
[CONNECTION]
HOST_NAME=192.168.0.117
REMOTE_TITLE=CONQUESTSRV
PORT_NUMBER=1109
LOCAL_TITLE=FLUOROSTAR
SERVICE_LIST=Storage_SCU_Service_List
DEFAULT_INI=default_storage
TIMEOUT=120
The AE Titles mentioned above are used for identification of the communication component as described in
DICOM standard.
2.5 DICOM Message Transfer in Detail

ACR-NEMA Standards Publication No. 300-1985, Version 1.0.
ACR-NEMA Standards Publication No. 1, October 1986
ACR-NEMA Standards Publication No. 2, January 1988.
ACR-NEMA Standards Publication No. 300-1988, Version 2.0
Supported DICOM Standards:
Used Support Library:
FLUOROSTAR never acts as a SCP! For all dicom services supported by FLUOROSTAR, it is a
SCU!
Message Content can be changed in different ways:
• (CV) Configuration Value :

Add or edit the Default-Ini Files for each Service
You can enable and disable the transfer of tag codes and you can edit, add or delete constant
message contents of tags. The default files are device independent for all devices which read this
service.
Sample: default_worklist.wkl
Be sure that your changes are necessary and correct, before you change the default files!
Normally you should change only the device specific configuration files.
You can generate a device specific configuration file. The defined tag codes overwrites the tag
codes of the default configuration file. The name of the configuration file must be identically to it’s
alias name and is exclusive designed for this device:
Sample: Alias = KodakPrinter Configuration file name = KodakPrinter.prn
•
• (SC) Software Controlled
Some of the Values are generated by the Software and can not be changed. The Software
overwrites all values defined in the default and device specific configuration files.
• (UD) User Defined

The content of these tags can be defined by the user at runtime via the dialog screens.
3 Fluorostar realized DICOM Services
3.1 DICOM Echo

ECHO Presentation Context
Abstract Syntax
Name STANDARD ECHO
UID 1.2.840.10008.1.1
3.1.1 General Echo Features

Fluorostar tests the availability of each DICOM - provider after each configuration chances with a TCP/IP-Ping
and a DICOM-Echo command. The echo timeout can be configured via configuration file.
3.1.2 Limitations of Echo Service

- none -
3.1.3 Description and Sequencing of Activities
3.1.4 SOP Specific Conformance

STANDARD ECHO (C_ECHO_RQ)
TAG-Code
0000,0002 Affected SOP Class UID
0000,0100 Command Field
0000,0110 Message ID
0000,0800 Data Set Type
3.2 DICOM Print Service

WORKLIST Presentation Context
Abstract Syntax
Printer SOP Class 1.2.840.10008.5.1.1.16
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
3.2.1 General Print Features

Fluorostar tests the availability of each DICOM - provider after each configuration chances with a TCP/IP-Ping
and a DICOM-Echo command. The echo timeout can be configured via configuration file.

1
PRINTER - N_GET_RQ CALL RET
0000,0003 Requested SOP Class UID = 1.2.840.10008.5.1.1.16 *
0000,1001 Requested SOP Instance UID = 1.2.840.10008.5.1.1.17 *
0008,0070 Manufacturer
0008,1090 Manufacturer's Model Name
0018,1000 Device Serial Number
0018,1020 Software Version(s)
0018,1200 Date of Last Calibration
0018,1201 Time of Last Calibration

2110,0010 Printer Status= *
2110,0020 Printer Status Info
2110,0030 Printer Name
1
BASIC_FILM_SESSION - N_CREATE_RSP CALL RET
2000,0010 Number of Copies=1 *
2000,0020 Print Priority (HIGH, MED, LOW)=MED *
2000,0030 Medium Type (PAPER, CLEAR FILM, BLUE FILM)=
2000,0040 Film Destination (MAGAZINE, PROCESSOR)=PROCESSOR *
2000,0050 Film Session Label
2000,0060 Memory Allocation
2050,0500 Referenced Presentation LUT Sequence
2100,0160 Owner ID
2130,00A0 Proposed Study Sequence
1
BASIC_FILM_SESSION - N_SET_RQ CALL RET
0008,0005 Specific Character Set = ISO_IR 100 *
0008,0012 Instance Creation Date
0008,0013 Instance Creation Time
0008,0014 Instance Creator UID
0008,0016 SOP Class UID
0008,0018 SOP Instance UID
2000,0010 Number of Copies
2000,0020 Print Priority (HIGH, MED, LOW)
2000,0030 Medium Type (PAPER, CLEAR FILM, BLUE FILM)
2000,0040 Film Destination (MAGAZINE, PROCESSOR)
2000,0050 Film Session Label
2000,0060 Memory Allocation
2000,0500 Referenced Film Box Sequence
1
BASIC_FILM_BOX - N_CREATE_RSP CALL RET
2010,0010 Image Display Format (STANDARD\n,n) *
2010,0030 Annotation Display Format ID
2010,0040 Film Orientation (PORTRAIT, LANDSCAPE)=PORTRAIT
2010,0050 Film Size ID (8INX10IN, 10INX14IN, 14INX14IN, 24CMX24CM, 10INX12IN,
11INX14IN, 14INX17IN,24CMX30CM)=8INX10IN
2010,0060 Magnification Type (REPLICATE, BILINEAR, CUBIC, NONE)
2010,0080 Smoothing Type
2010,0100 Border Density (BLACK, WHITE)=WHITE
2010,0110 Empty Image Density (BLACK, WHITE)
2010,0120 Min Density = 5
2010,0130 Max Density = 20
2010,0140 Trim (YES, NO)
2010,0150 Configuration Information
2010,015E Illumination
2010,0160 Reflected Ambient Light
2010,0500 Referenced Film Session Sequence
2010,0510 Referenced Image Box Sequence
2010,0520 Referenced Basic Annotation Box Sequence
2020,0050 Requested Resolution ID (STANDARD, HIGH)
1
BASIC_FILM_BOX - N_SET_RQ CALL RET
2010,0100 Border Density (BLACK, WHITE)
2010,0110 Empty Image Density (BLACK, WHITE)

2010,0120 Min Density
2010,0130 Max Density
2010,0140 Trim (YES, NO)
2010,015E Illumination
2010,0160 Reflected Ambient Light
1
BASIC_GRAYSCALE_IMAGE_BOX - N_SET_RQ CALL RET
2010,0120 Min Density
2010,0130 Max Density
2020,0010 Image Position
2020,0020 Polarity (NORMAL, REVERSE)=NORMAL *
2020,0030 Requested Image Size
2020,0040 Requested Decimate/Crop Behavior (DECIMATE, CROP, FAIL)
2020,0110 Basic Grayscale Image Sequence (PREFORMATTED_GRAYSCALE_IMAGE) *
2020,0130 Referenced Image Overlay Box Sequence
2130,00C0 Original Image Sequence
1
PREFORMATTED_GRAYSCALE_IMAGE CALL RET
0028,0002 Samples per Pixel (1)=1 *
0028,0004 Photometric Interpretation (MONOCHROME1, *
MONOCHROME2)=MONOCHROME2
0028,0010 Rows=512|1024 *
0028,0011 Columns=512|1024 *
0028,0034 Pixel Aspect Ratio
0028,0100 Bits Allocated (8, 16)=8|16 *
0028,0101 Bits Stored (8, 12)=8|16 *
0028,0102 High Bit (7, 11)=7|15 *
0028,0103 Pixel Representation (0000)=0 *
3.3 DICOM IMAGE STORE Service

Abstract Syntax
Name X-Ray Radiofluoroscopic Image Storage
UID 1.2.840.10008.5.1.4.1.1.12.2
3.3.1 General Image Store Features
3.3.2 Limitations of Image Store Service

1
PREFORMATTED_GRAYSCALE_IMAGE CALL RET
0008,0005 Specific Character Set = ISO_IR 100 *
0008,0008 Image Type (ORIGINAL, DERIVED)(PRIMARY,SECONDARY)(SINGLE PLANE, *

BIPLANE A, BIPLANE B, BIPLANE)=ORIGINAL
0008,0012 Instance Creation Date *
0008,0013 Instance Creation Time *
0008,0014 Instance Creator UID
0008,0016 SOP Class UID *
0008,0018 SOP Instance UID *
0008,0020 Study Date *
0008,0021 Series Date *
0008,0022 Acquisition Date
0008,0023 Content/Image Date
0008,002A Acquisition Datetime
0008,0030 Study Time *
0008,0031 Series Time *
0008,0032 Acquisition Time
0008,0033 Content/Image Time
0008,0050 Accession Number *
0008,0060 Modality = RF *
0008,0070 Manufacturer = GE MEDICAL SYSTEMS *
0008,0080 Institution Name *
0008,0081 Institution Address
0008,0090 Referring Physician's Name *
0008,0096 Referring Physician Identification Seque
0008,0110 Coding Scheme Identification Sequence
0008,0201 Timezone Offset From UTC
0008,1010 Station Name *
0008,1030 Study Description *
0008,103E Series Description *
0008,1040 Institutional Department Name
0008,1048 Physician(s) of Record
0008,1049 Physician(s) of Record Identification Se
0008,1050 Performing Physician's Name
0008,1052 Performing Physician Identification Sequence
0008,1060 Name of Physician(s) Reading Study
0008,1062 Physician(s) Reading Study Identification
0008,1070 Operators' Name
0008,1072 Operator Identification Sequence
0008,1080 Admitting Diagnosis Description
0008,1090 Manufacturer's Model Name
0008,1110 Referenced Study Sequence (REF_STUDY)
0008,1111 Referenced Study Component Sequence (REF_STUDY_COMPONENT)
0008,1120 Referenced Patient Sequence (REF_PATIENT)
0008,113A Referenced Waveform Sequence
0008,1140 Referenced Image Sequence (REF_IMAGE)
0008,2111 Derivation Description
0008,2112 Source Image Sequence (SOURCE_IMAGE)
0008,2142 Start Trim
0008,2143 Stop Trim
0008,2144 Recommended Display Frame Rate
0008,2218 Anatomic Region Sequence
0008,2228 Primary Anatomic Structure Sequence
0008,9215 Derivation Code Sequence
0010,0010 Patient's Name *
0010,0020 Patient ID *
0010,0030 Patient's Birth Date *
0010,0032 Patient's Birth Time
0010,0040 Patient's Sex (M,F,O) **

0010,1000 Other Patient IDs
0010,1001 Other Patient Names
0010,1010 Patient's Age
0010,1020 Patient's Size
0010,1030 Patient's Weight
0010,2160 Ethnic Group
0010,2180 Occupation
0010,21B0 Additional Patient History
0010,4000 Patient Comments
0012,0010 Clinical Trial Sponsor Name
0012,0020 Clinical Trial Protocol ID
0012,0021 Clinical Trial Protocol Name
0012,0030 Clinical Trial Site ID
0012,0031 Clinical Trial Site Name
0012,0040 Clinical Trial Subject ID
0012,0042 Clinical Trial Subject Reading ID
0012,0050 Clinical Trial Time Point ID
0012,0051 Clinical Trial Time Point Description
0012,0060 Clinical Trial Coordinating Center Name
0018,0010 Contrast/Bolus Agent
0018,0012 Contrast/Bolus Agent Sequence
0018,0014 Contrast/Bolus Administration Route Sequ
0018,0015 Body Part Examined
0018,0022 Scan Options
0018,0036 Interventional Therapy Sequence
0018,0040 Cine Rate
0018,0060 KVP *
0018,0072 Effective Series Duration
0018,1000 Device Serial Number
0018,1020 Software Version(s) *
0018,1030 Protocol Name
0018,1040 Contrast/Bolus Route
0018,1041 Contrast/Bolus Volume
0018,1042 Contrast/Bolus Start Time
0018,1043 Contrast/Bolus Stop Time
0018,1044 Contrast/Bolus Total Dose
0018,1046 Contrast Flow Rate(s)
0018,1047 Contrast Flow Duration(s)
0018,1048 Contrast/Bolus Ingredient
0018,1049 Contrast/Bolus Ingredient Concentration
0018,1050 Spatial Resolution
0018,1063 Frame Time
0018,1065 Frame Time Vector
0018,1066 Frame Delay
0018,1067 Image Trigger Delay
0018,1110 Distance Source to Detector
0018,1111 Distance Source to Patient
0018,1114 Estimated Radiographic Magnification Fac
0018,1134 Table Motion (STATIC, DYNAMIC)
0018,1135 Table Vertical Increment
0018,1136 Table Lateral Increment
0018,1137 Table Longitudinal Increment
0018,1138 Table Angle
0018,1147 Field of View Shape (ROUND, RECTANGLE)
0018,1149 Field of View Dimension(s)
0018,1150 Exposure Time

0018,1151 X-ray Tube Current *
0018,1152 Exposure
0018,1153 Exposure in uAs
0018,1154 Average Pulse Width
0018,1155 Radiation Setting (SC, GR) = SC *
0018,115A Radiation Mode (CONTINUOUS, PULSED)
0018,115E Image Area Dose Product *
0018,1161 Type of Filters
0018,1162 Intensifier Size
0018,1164 Imager Pixel Spacing
0018,1166 Grid (IN, NONE)
0018,1190 Focal Spot(s)
0018,1200 Date of Last Calibration
0018,1201 Time of Last Calibration
0018,1242 Actual Frame Duration
0018,1244 Preferred Playback Sequencing (0,1)
0018,1400 Acquisition Device Processing Descriptio
0018,1450 Column Angulation
0018,1460 Tomo Layer Height
0018,1470 Tomo Angle
0018,1480 Tomo Time
0018,1490 Tomo Type (LINEAR, SPIRAL, POLYCYCLOIDAL, CIRCULAR)
0018,1491 Tomo Class (MOTION, TOMOSYNTHESIS)
0018,1495 Number of Tomosynthesis Source Images
0018,1600 Shutter Shape (RECTANGULAR, CIRCULAR, POLYGONAL)
0018,1602 Shutter Left Vertical Edge
0018,1604 Shutter Right Vertical Edge
0018,1606 Shutter Upper Horizontal Edge
0018,1608 Shutter Lower Horizontal Edge
0018,1610 Center of Circular Shutter
0018,1612 Radius of Circular Shutter
0018,1620 Vertices of Polygonal Shutter
0018,1622 Shutter Presentation Value
0018,1700 Collimator Shape (RECTANGULAR, CIRCULAR, POLYGONAL)
0018,1702 Collimator Left Vertical Edge
0018,1704 Collimator Right Vertical Edge
0018,1706 Collimator Upper Horizontal Edge
0018,1708 Collimator Lower Horizontal Edge
0018,1710 Center of Circular Collimator
0018,1712 Radius of Circular Collimator
0018,1720 Vertices of the Polygonal Collimator
0018,5100 Patient Position
0018,A001 Contributing Equipment Sequence
0020,000D Study Instance UID *
0020,000E Series Instance UID *
0020,0010 Study ID *
0020,0011 Series Number *
0020,0012 Acquisition Number
0020,0013 Instance Number *
0020,0020 Patient Orientation
0020,0060 Laterality
0020,1002 Images in Acquisition
0020,4000 Image Comments
0028,0002 Samples per Pixel=1 *
0028,0004 Photometric Interpretation (MONOCHROME2)=MONOCHROME2 *
0028,0006 Planar Configuration

0028,0008 Number of Frames
0028,0009 Frame Increment Pointer
0028,0010 Rows *
0028,0011 Columns *
0028,0034 Pixel Aspect Ratio
0028,0100 Bits Allocated (8,16) *
0028,0101 Bits Stored (8, 10, 12, 16) *
0028,0102 High Bit (7, 9, 11, 15) *
0028,0103 Pixel Representation = 0 *
0028,0106 Smallest Image Pixel Value
0028,0107 Largest Image Pixel Value
0028,0108 Smallest Pixel Value in Series
0028,0109 Largest Pixel Value in Series
0028,0120 Pixel Padding Value
0028,0300 Quality Control Image (YES, NO)
0028,0301 Burned In Annotation (YES, NO)
0028,1040 Pixel Intensity Relationship (LIN, LOG, DISP)=LIN *
0028,1050 Window Center *
0028,1051 Window Width *
0028,1052 Rescale Intercept
0028,1053 Rescale Slope
0028,1054 Rescale Type
0028,1055 Window Center and Width Explanation
0028,1090 Recommended Viewing Mode (SUB, NAT)
0028,1101 Red Palette Color Lookup Table Description
0028,1102 Green Palette Color Lookup Table Description
0028,1103 Blue Palette Color Lookup Table Descript
0028,1201 Red Palette Color lookup Table Data
0028,1202 Green Palette Color lookup Table Data
0028,1203 Blue Palette Color Lookup Table Data
0028,2110 Lossy Image Compression
0028,2112 Lossy Image Compression Ratio
0028,3000 Modality LUT Sequence
0028,3010 VOI LUT Sequence
0028,6010 Representative Frame Number
0028,6020 Frame Numbers of Interest (FOI)
0028,6022 Frame(s) of Interest Description
0028,6040 R Wave Pointer
0028,6100 Mask Subtraction Sequence
0040,0244 Performed Procedure Step Start Date
0040,0245 Performed Procedure Step Start Time
0040,0253 Performed Procedure Step ID
0040,0254 Performed Procedure Step Description
0040,0275 Request Attributes Sequence
0040,A170 Purpose of Reference Code Sequence
0050,0004 Calibration Image (YES, NO) = NO
0050,0010 Device Sequence
0100,0410 SOP Instance Status (NS,OR,AO,AC)
0100,0420 SOP Authorization Date and Time
0100,0424 SOP Authorization Comment
0100,0426 Authorization Equipment Certification Number
0400,0500 Encrypted Attributes Sequence
4FFE,0001 MAC Parameters Sequence
5000,0005 Curve Dimensions
5000,0010 Number of Points
5000,0020 Type of Data (TAC, PROF, HIST, ROI,...)

5000,0022 Curve Description
5000,0030 Axis Units (SEC, CNTS, MM, PXEL, ...)
5000,0040 Axis Labels
5000,0103 Data Value Representation (0000, - 0004)
5000,0104 Minimum Coordinate Value
5000,0105 Maximum Coordinate Value
5000,0106 Curve Range
5000,0110 Curve Data Descriptor (0000,0001)
5000,0112 Coordinate Start Value
5000,0114 Coordinate Step Value
5000,2500 Curve Label
5000,2600 Curve Referenced Overlay Sequence
5000,3000 Curve Data
6000,0010 Overlay Rows
6000,0011 Overlay Columns
6000,0015 Number of Frames in Overlay
6000,0022 Overlay Description
6000,0040 Overlay Type (G,R)
6000,0045 Overlay Subtype
6000,0050 Overlay Origin
6000,0051 Image Frame Origin
6000,0100 Overlay Bits Allocated
6000,0102 Overlay Bit Position
6000,1100 Overlay Descriptor - Gray RETIRED
6000,1101 Overlay Descriptor - Red RETIRED
6000,1102 Overlay Descriptor - Green RETIRED
6000,1103 Overlay Descriptor - Blue RETIRED
6000,1200 Overlays - Gray RETIRED
6000,1201 Overlays - Red RETIRED
6000,1202 Overlays - Green RETIRED
6000,1203 Overlays - Blue RETIRED
6000,1301 ROI Area
6000,1302 ROI Mean
6000,1303 ROI Standard Deviation
6000,1500 Overlay Label
6000,3000 Overlay Data
0009,001x Private Field (see 6.6 )
** O (other, if patient was created on FLUOROSTAR, else information is copied from the worklist.)
3.4 DICOM Worklist Service

Abstract Syntax
Name Modality Worklist Information Model – FIND
UID 1.2.840.10008.5.1.4.31
3.4.1 General Worklist Features

FLUOROSTAR is able to get Worklist information from one Worklist provider.
3.4.2 Limitations of Worklist Service

There is no automatic Worklist transfer from the Service Class Provider to FLUOROSTAR. This means worklist
must be requested manually by the user.
For this version FLUOROSTAR can define filter except date, station name and physicians name for the Worklist
results only via the initialization files.

FLUOROSTAR can be configured to request Worklist information from one Worklist server.
The AE’s, for which FLUOROSTAR should request worklist, can be configured. FLUOROSTAR does not
periodically queries the system acting as worklist server for worklists.
The worklist results are written to a result file and can be displayed to select patients from the worklist.
Filename of the default Worklist Context Table: default_worklist.wkl

Filename of the Worklist Result File: worklist.result
It is not possible to cancel the query process.

FLUOROSTAR does not limit the number of processed worklist responses. If worklist query fails in error
information is written into a log file.

The table below provides a description of the FLUOROSTAR worklist identifier. Only a subset is used.
The table shows all possible Tag-Codes for this Service. The default configuration activates only a subset.
1
MODALITY_WORKLIST_FIND CALL RET
TAG-Code
0008,0005 Specific Character Set = ISO_IR 100 CV
0008,0050 Accession Number (NULL) *
0008,0080 Institution Name
0008,0081 Institution Address
0008,0082 Institution Code Sequence
0008,0090 Referring Physician's Name
0008,0092 Referring Physician's Address
0008,0094 Referring Physician's Telephone Numbers
0008,0096 Referring Physician Identification Sequence
0008,1080 Admitting Diagnosis Description
0008,1084 Admitting Diagnosis Code Sequence
0008,1110 Referenced Study Sequence
0008,1120 Referenced Patient Sequence
0008,1125 Referenced Visit Sequence
0010,0010 Patient's Name (NULL) *
0010,0020 Patient ID (NULL) *
0010,0021 Issuer of Patient ID
0010,0030 Patient's Birth Date (NULL) *
0010,0032 Patient's Birth Time
0010,0040 Patient's Sex (M;F;O) (NULL) *
0010,0050 Patient's Insurance Plan Code Sequence
0010,1000 Other Patient IDs
0010,1001 Other Patient Names
0010,1005 Patient's Birth Name
0010,1010 Patient's Age
0010,1020 Patient's Size
0010,1030 Patient's Weight
0010,1040 Patient's Address
0010,1060 Patient's Mother's Birth Name
0010,1080 Military Rank
0010,1081 Branch of Service
0010,1090 Medical Record Locator
0010,2000 Medical Alerts

0010,2110 Contrast Allergies
0010,2150 Country of Residence
0010,2152 Region of Residence
0010,2154 Patient's Telephone Numbers
0010,2160 Ethnic Group
0010,2180 Occupation
0010,21A0 Smoking Status (YES, NO, UNKNOWN)
0010,21B0 Additional Patient History
0010,21C0 Pregnancy Status (0001, 0002, 0003, 0004)
0010,21D0 Last Menstrual Date
0010,21F0 Patient's Religious Preference
0010,4000 Patient Comments
0020,000D Study Instance UID
0032,1031 Requesting Physician Identification Sequence
0032,1032 Requesting Physician
0032,1033 Requesting Service
0032,1060 Requested Procedure Description
0032,1064 Requested Procedure Code Sequence
0038,0004 Referenced Patient Alias Sequence
0038,0008 Visit Status ID
0038,0010 Admission ID
0038,0011 Issuer of Admission ID
0038,0016 Route of Admissions
0038,0020 Admitting Date
0038,0021 Admitting Time
0038,0050 Special Needs
0038,0300 Current Patient Location
0038,0400 Patient's Institution Residence
0038,0500 Patient State
0038,4000 Visit Comments
0040,0100 Scheduled Procedure Step Sequence (NULL) *
0040,1001 Requested Procedure ID
0040,1002 Reason for the Requested Procedure
0040,1003 Requested Procedure Priority (STAT, HIGH, ROUTINE, MEDIUM, LOW)
0040,1004 Patient Transport Arrangements
0040,1005 Requested Procedure Location
0040,1006 Placer Order Number / Procedure RETIRED
0040,1007 Filler Order Number Procedure RETIRED
0040,1008 Confidentiality Code
0040,1009 Reporting Priority (HIGH, ROUTINE, MEDIUM, LOW)
0040,1010 Names of Intended Recipients of Results
0040,1011 Intended Recp of Results Identification
0040,1400 Requested Procedure Comments
0040,2001 Reason for the Imaging Service Request
0040,2004 Issue Date of Imaging Service Request
0040,2005 Issue Time of Imaging Service Request
0040,2008 Order Entered By
0040,2009 Order Enterer's Location
0040,2010 Order Callback Phone Number
0040,2016 Placer Order Number / Imaging Service Re
0040,2017 Filler Order Number / Imaging Service Re
0040,2400 Imaging Service Request Comments
0040,3001 Confidentiality Constraint on Patient Data
SCHEDULED_PROCEDURE_STEP
TAG-Code Description
0008,0060 Modality = RF CV *
0032,1070 Requested Contrast Agent
0040,0001 Scheduled Station AE Title
0040,0002 Scheduled Procedure Step Start Date DU *
0040,0003 Scheduled Procedure Step Start Time
0040,0004 Scheduled Procedure Step End Date
0040,0005 Scheduled Procedure Step End Time
0040,0006 Scheduled Performing Physician's Name
0040,0007 Scheduled Procedure Step Description (NULL) *
0040,0008 Scheduled Action Item Code Sequence
0040,0009 Scheduled Procedure Step ID (NULL) *
0040,000B Scheduled Performing Phys Identification
0040,0010 Scheduled Station Name SU *
0040,0011 Scheduled Procedure Step Location
0040,0012 Pre-Medication
0040,0020 Scheduled Procedure Step Status
0040,0400 Comments on the Scheduled Procedure Step
1) CV= Configuration Value: can only be defined via the configuration file with constant data
PV= Program Value: this attribute is overwritten by the software, you can not change it!
DU= Defined by User: User can define the content of the Attribute via the application program
SV= Setup Value; SU Setup -> System Configuration
4 Error Handling
The error messages of the dicom communication and the dicom interface routines are detailed listed at the logfile
dicom.log for the service technician. See the description Program Internal Error Codes and DICOM Error Codes
below. This errors are classified and filtered for the normal end user, because there is no need for detailed error
messages for the user. See 4.1 Application Error Messages below.
Error codes from the dicom communication interface and error codes transfered from the communication partner
to Fluorostar are listed with their codes inside the log-file
4.1 Application Error Messages
Code Short Name Description

0 No Error Action completion code, no Message to user
1 Configuration Error Missing or wrong program files, configuration files or version conflict
2 Server Error DICOM-Server not ready or no access right for this server
3 Service Error DICOM reports communication errors
4 End Of Action Not an Error, no more Data available (only program internal use)
5 FileIO Error Access to data files not possible, maybe hard disk full
6 Message Error Message transfer error, maybe timeout or line break
7 Store Error Data store impossible, data format incompatible for database
8 Data Error Message incomplete or required fields not filled
4.2 Program Internal Error Codes

Code Meaning Code Meaning
4000 ALREADY REGISTERED 4070 NULL POINTER PARM
4001 ASSOCIATION ABORTED 4071 NULL VALUE
4002 ASSOCIATION CLOSED 4072 PROTOCOL ERROR
4003 ASSOCIATION REJECTED 4073 REQUIRED ATTRIBUTE MISSING
4004 ATTRIBUTE HAS VALUES 4074 REQUIRED DATASET MISSING
4005 BUFFER TOO SMALL 4075 REQUIRED VALUE MISSING
4006 CALLBACK CANNOT COMPLY 4076 STATE VIOLATION
4007 CALLBACK DATA SIZE NEGATIVE 4077 SYSTEM CALL INTERRUPTED
4008 CALLBACK DATA SIZE UNEVEN 4078 SYSTEM ERROR
4009 CALLBACK PARM ERROR 4079 TAG ALREADY EXISTS
4010 CALLBACK REGISTERED 4080 TEMP FILE ERROR
4011 CANNOT COMPLY 4081 TIMEOUT
4012 CANT ACCESS PROFILE 4082 TOO FEW VALUES
4013 CONFIG INFO ERROR 4083 TOO MANY BLOCKS
4014 CONFIG INFO MISSING 4084 TOO MANY VALUES
4015 DDFILE ERROR 4085 UNABLE TO CHECK CONDITION
4016 DOES NOT VALIDATE 4086 UNACCEPTABLE SERVICE
4017 EMPTY VALUE 4087 UNEXPECTED EOD
4018 END OF DATA 4088 UNKNOWN ITEM
4019 EXT INFO UNAVAILABLE 4089 UNKNOWN SERVICE
4020 FOUND 4090 VALUE MAY NOT BE NULL
4021 FUNCTION UNAVAILABLE 4091 VALUE NOT ALLOWED
4022 INCOMPATIBLE VR 4092 VALUE OUT OF RANGE
4023 INCOMPATIBLE VALUE 4093 VALUE TOO LARGE
4024 INVALID APPLICATION ID 4094 VR ALREADY VALID
4025 INVALID APPLICATION TITLE 4095 LIBRARY ALREADY INITIALIZED
4026 INVALID ASSOC ID 4096 LIBRARY NOT INITIALIZED
4027 INVALID CHARS IN VALUE 4097 INVALID DIRECTORY RECORD OFFSET
4028 INVALID COMMAND 4098 INVALID FILE ID
4029 INVALID DATA TYPE 4099 INVALID DICOMDIR ID
4030 END OF LIST 4100 INVALID ENTITY ID
4031 INVALID GROUP 4101 INVALID MRDR ID
4032 INVALID HOST NAME 4102 UNABLE TO GET ITEM ID
4033 INVALID ITEM ID 4103 INVALID PAD
4034 INVALID LENGTH FOR TITLE 4104 ENTITY ALREADY EXISTS
4035 INVALID LENGTH FOR VR 4105 INVALID LOWER DIR RECORD
4036 INVALID LICENSE 4106 BAD DIR RECORD TYPE
4037 INVALID MESSAGE ID 4107 UNKNOWN HOST CONNECTED

4038 INVALID MESSAGE RECEIVED 4108 INACTIVITY TIMEOUT
4039 INVALID PARAMETER NAME 4109 INVALID SOP CLASS UID
4040 INVALID PORT NUMBER 4110 INVALID VERSION
4041 INVALID PRIVATE CODE 4111 OUT OF ORDER TAG
4042 INVALID SERVICE LIST NAME 4112 CONNECTION FAILED
4043 INVALID TAG 4113 UNKNOWN HOST NAME
4044 INVALID TRANSFER SYNTAX 4114 INVALID FILE
4045 INVALID VALUE FOR VR 4115 NEGOTIATION ABORTED
4046 INVALID VALUE NUMBER 4116 INVALID SR ID
4047 INVALID VR CODE 4117 UNABLE TO GET SR ID
4048 LOG EMPTY 4118 DUPLICATE NAME
4049 MESSAGE EMPTY 4119 DUPLICATE SYNTAX
4050 MESSAGE VALIDATES 4120 EMPTY LIST
4051 MISSING CONFIG PARM 4121 MISSING NAME
4052 MSGFILE ERROR 4122 INVALID SERVICE NAME
4053 MUST BE POSITIVE 4123 SERVICE IN USE
4054 NETWORK SHUT DOWN 4124 INVALID SYNTAX NAME
4055 NO APPLICATIONS REGISTERED 4125 SYNTAX IN USE
4056 NO CALLBACK 4126 NO CONTEXT
4057 NO CONDITION FUNCTION 4127 OFFSET TABLE TOO SHORT
4058 NO FILE SYSTEM 4128 MISSING DELIMITER
4059 NO INFO REGISTERED 4129 COMPRESSION FAILURE
4060 NO LICENSE 4130 END OF FRAME
4061 NO MERGE INI 4131 MUST CONTINUE BEFORE READING
4062 NO MORE ATTRIBUTES 4132 COMPRESSOR REQUIRED
4063 NO MORE VALUES 4133 DECOMPRESSOR REQUIRED
4064 NO PROFILE 4134 DATA AVAILABLE
4065 NO REQUEST PENDING 4135 ZLIB ERROR
4066 NON SERVICE ATTRIBUTE 4136 NOT META SOP
4067 NOT FOUND 4137 INVALID ITEM TRANSFER SYNTAX
4068 NOT ONE OF ENUMERATED VALUES 4138 LICENSE ERROR
4069 NOT ONE OF DEFINED TERMS
4.3 DICOM Error Codes

Storage Service Class: C_STORE_RSP Codes
SUCCESS code
C_STORE_SUCCESS 0x0000
WARNING codes
C_STORE_WARNING_ELEMENT_COERCION 0xB000
C_STORE_WARNING_INVALID_DATASET 0xB007
C_STORE_WARNING_ELEMENTS_DISCARDED 0xB006
FAILURE codes
C_STORE_FAILURE_REFUSED_NO_RESOURCES 0xA700
C_STORE_FAILURE_INVALID_DATASET 0xA900
C_STORE_FAILURE_CANNOT_UNDERSTAND 0xC000
C_STORE_FAILURE_PROCESSING_FAILURE 0x0110
Study Content NotificationService Class: C_STORE_RSP Codes
SUCCESS codes
C_STORE_SUCCESS_COMPLETE_STUDY_EXISTS 0x0000
C_STORE_SUCCESS_PARTIAL_STUDY_EXISTS 0x0001
C_STORE_SUCCESS_STUDY_DOES_NOT_EXIST 0x0002
C_STORE_SUCCESS_UNKNOWN_EXISTENCE 0x0003
FAILURE code
C_STORE_FAILED_OPERATION 0xC002
Verification Service Class: C_ECHO_RSP Codes
SUCCESS code
C_ECHO_SUCCESS 0x0000
Query/Retrieve Service Class: C_FIND_RSP Codes
SUCCESS code
C_FIND_SUCCESS 0x0000
PENDING codes
C_FIND_PENDING 0xFF00
C_FIND_PENDING_NO_OPTIONAL_KEY_SUPPORT 0xFF01
FAILURE codes
C_FIND_FAILURE_REFUSED_NO_RESOURCES 0xA700
C_FIND_FAILURE_INVALID_DATASET 0xA900
C_FIND_FAILURE_UNABLE_TO_PROCESS 0xC001
CANCEL code
C_FIND_CANCEL_REQUEST_RECEIVED 0xFE00
Query/Retrieve Service Class: C_MOVE_RSP Codes
SUCCESS code
C_MOVE_SUCCESS_NO_FAILURES 0x0000
WARNING code
C_MOVE_WARNING_ONE_OR_MORE_FAILURES 0xB000
PENDING code
C_MOVE_PENDING_MORE_SUB_OPERATIONS 0xFF00
FAILURE codes
C_MOVE_FAILURE_REFUSED_CANT_CALCULATE 0xA701
C_MOVE_FAILURE_REFUSED_CANT_PERFORM 0xA702
C_MOVE_FAILURE_REFUSED_DEST_UNKNOWN 0xA801
C_MOVE_FAILURE_INVALID_DATASET 0xA900
C_MOVE_FAILURE_UNABLE_TO_PROCESS 0xC001
CANCEL code
C_MOVE_CANCEL_REQUEST_RECEIVED 0xFE00
Query/Retrieve Service Class: C_GET_RSP Codes
SUCCESS code
C_GET_SUCCESS_NO_FAILURES_OR_WARNINGS 0x0000
WARNING code
C_GET_WARNING_SOME_FAILURES_WARNINGS 0xB000
PENDING code
C_GET_PENDING_MORE_SUB_OPERATIONS 0xFF00
FAILURE codes
C_GET_FAILURE_REFUSED_CANT_CALC_MATCHES 0xA701
C_GET_FAILURE_REFUSED_CANT_PERFORM 0xA702
C_GET_FAILURE_INVALID_DATASET 0xA900
C_GET_FAILURE_UNABLE_TO_PROCESS 0xC001
CANCEL code
C_GET_CANCEL_REQUEST_RECEIVED 0xFE00
N_EVENT_REPORT_RSP Response Codes
SUCCESS code
N_EVENT_SUCCESS 0x0000
FAILURE codes
N_EVENT_CLASS_INSTANCE_CONFLICT 0x0119
N_EVENT_DUPLICATE_INVOCATION 0x0210
N_EVENT_INVALID_ARGUMENT_VALUE 0x0115
N_EVENT_MISTYPED_ARGUMENT 0x0212
N_EVENT_NO_SUCH_ARGUMENT 0x0114
N_EVENT_NO_SUCH_EVENT_TYPE 0x0113
N_EVENT_NO_SUCH_SOP_CLASS 0x0118
N_EVENT_NO_SUCH_SOP_INSTANCE 0x0112
N_EVENT_PROCESSING_FAILURE 0x0110
N_EVENT_RESOURCE_LIMITATION 0x0213
N_EVENT_UNRECOGNIZED_OPERATION 0x0211
N_GET_RSP Response Codes
SUCCESS code
N_GET_SUCCESS 0x0000
WARNING codes
N_GET_WARNING_OPT_ATTRIB_UNSUPPORTED 0x0001
N_GET_ATTRIBUTE_LIST_ERROR 0x0107
FAILURE codes
N_GET_CLASS_INSTANCE_CONFLICT 0x0119
N_GET_DUPLICATE_INVOCATION 0x0210
N_GET_MISTYPED_ARGUMENT 0x0212
N_GET_NO_SUCH_SOP_CLASS 0x0118
N_GET_NO_SUCH_SOP_INSTANCE 0x0112
N_GET_PROCESSING_FAILURE 0x0110
N_GET_RESOURCE_LIMITATION 0x0213
N_GET_UNRECOGNIZED_OPERATION 0x0211
N_SET_RSP Response Codes
SUCCESS code
N_SET_SUCCESS 0x0000
WARNING codes
N_SET_REQUESTED_MIN_OR_MAX_DENSITY_OUTSIDE_RANGE 0xB605
N_SET_ATTRIBUTE_VALUE_OUT_OF_RANGE 0x0116
N_SET_ATTRIBUTE_LIST_ERROR 0x0107
FAILURE codes
N_SET_CLASS_INSTANCE_CONFLICT 0x0119
N_SET_DUPLICATE_INVOCATION 0x0210
N_SET_INVALID_ATTRIBUTE_VALUE 0x0106
N_SET_MISTYPED_ARGUMENT 0x0212
N_SET_INVALID_OBJECT_INSTANCE 0x0117
N_SET_MISSING_ATTRIBUTE_VALUE 0x0121
N_SET_NO_SUCH_ATTRIBUTE 0x0105
N_SET_NO_SUCH_SOP_CLASS 0x0118
N_SET_NO_SUCH_SOP_INSTANCE 0x0112
N_SET_PROCESSING_FAILURE 0x0110
N_SET_RESOURCE_LIMITATION 0x0213
N_SET_UNRECOGNIZED_OPERATION 0x0211
Print Management Service Classes WARNING codes
N_SET_WARNING_IMAGE_CROPPED_TO_FIT 0xB609
N_SET_WARNING_IMAGE_DECIMATED_TO_FIT 0xB60A
Print Management Service Classes FAILURE codes
N_SET_INSUFFICIENT_PRINTER_MEMORY 0xC605
N_SET_MORE_THAN_ONE_VOID_LUT_BOX 0xC606
N_SET_FAILURE_IMAGE_LARGER_THAN_BOX 0xC603
N_SET_FAILURE_COMBINED_LARGER_THAN_BOX 0xC613
Modality Performed Procedure Step FAILURE codes
N_SET_OBJECT_MAY_NO_LONGER_BE_UPDATED 0x0110
Modify GP Performed Procedure Step REFUSED codes
N_SET_REFUSED_PPS_NOT_IN_PROGRESS 0xA506
N_ACTION_RSP Response Codes
SUCCESS code
N_ACTION_SUCCESS 0x0000
FAILURE codes
N_ACTION_CLASS_INSTANCE_CONFLICT 0x0119
N_ACTION_DUPLICATE_INVOCATION 0x0210
N_ACTION_INVALID_ARGUMENT_VALUE 0x0115
N_ACTION_MISTYPED_ARGUMENT 0x0212
N_ACTION_NO_SUCH_ARGUMENT 0x0114
N_ACTION_NO_SUCH_SOP_CLASS 0x0118
N_ACTION_NO_SUCH_SOP_INSTANCE 0x0112
N_ACTION_PROCESSING_FAILURE 0x0110
N_ACTION_RESOURCE_LIMITATION 0x0213
N_ACTION_UNRECOGNIZED_OPERATION 0x0211
N_ACTION_WARNING_NO_COLLATION_SUPPORT 0xB601
N_ACTION_WARNING_SESSION_EMPTY_PAGE 0xB602
N_ACTION_WARNING_BOX_EMPTY_PAGE 0xB603
N_ACTION_WARNING_IMAGE_CROPPED_TO_FIT 0xB609
N_ACTION_WARNING_IMAGE_DECIMATED_TO_FIT 0xB60A
N_ACTION_FAILURE_NO_FILM_SOP_INSTANCES 0xC600
N_ACTION_FAILURE_SESSION_PRINT_Q_FULL 0xC601
N_ACTION_FAILURE_BOX_PRINT_Q_FULL 0xC602
N_ACTION_FAILURE_SIZE_LARGER_THAN_BOX 0xC603
N_ACTION_FAILURE_IMAGE_POS_COLLISION 0xC604
N_ACTION_FAILURE_COMBINED_SIZE_LARGER_THAN_BOX 0xC613
Print Queue Management Service Classes FAILURE codes
N_ACTION_FAILURE_PRINT_QUEUE_IS_HALTED 0xC651
N_ACTION_FAILURE_MISMATCH_OF_OWNER_IDS 0xC652
N_ACTION_FAILURE_JOB_IN_PROCESS 0xC653
Pull Print Request WARNING codes
N_ACTION_MEMORY_ALLOCATION_NOT_SUPP 0xB600
N_ACTION_WARNING_ANNOTATION_NOT_SUPP 0xB604
N_ACTION_WARNING_IMAGE_OVERLAY_NOT_SUPP 0xB605
N_ACTION_WARNING_PRES_LUT_NOT_SUPP 0xB606
N_ACTION_WARNING_IMAGE_BOX_LUT_NOT_SUPP 0xB608
Pull Print Request FAILURE codes
N_ACTION_FAILURE_INSUFFICIENT_MEMORY 0xC605
N_ACTION_FAILURE_NO_STORED_PRINT_AT_AE 0xC607
N_ACTION_FAILURE_NO_IMAGE_AT_AE 0xC608
N_ACTION_FAILURE_RETRIEVING_STORED_PRINT 0xC609
N_ACTION_FAILURE_RETRIEVING_IMAGE 0xC60A
N_ACTION_FAILURE_UNKNOWN_RETREIVE_AE 0xC60B
N_ACTION_FAILURE_PRINTER_CANNOT_ACCEPT_COLOR 0xC60C
N_ACTION_FAILURE_EMPTY_PAGE 0xC60D
N_ACTION_FAILURE_ANNOTATION_NOT_SUPP 0xC60E
N_ACTION_FAILURE_IMAGE_OVERLAY_NOT_SUPP 0xC60F
N_ACTION_FAILURE_PRES_LUT_NOT_SUPP 0xC610
N_ACTION_FAILURE_IMAGE_BOX_LUT_NOT_SUPP 0xC614
N_ACTION_FAILURE_UNABLE_TO_OPEN_ASSOC 0xC615
Modify GP Scheduled Procedure Step REFUSED codes
N_ACTION_REFUSED_MAY_NO_LONGER_BE_UPDATED 0xA501
N_ACTION_REFUSED_WRONG_TRANSACTION_ID 0xA502
N_ACTION_REFUSED_ALREADY_IN_PROGRESS 0xA503
N_CREATE_RSP Response Codes
SUCCESS code
N_CREATE_SUCCESS 0x0000
FAILURE codes
N_CREATE_CLASS_INSTANCE_CONFLICT 0x0119
N_CREATE_DUPLICATE_INVOCATION 0x0210
N_CREATE_DUPLICATE_SOP_INSTANCE 0x0111
N_CREATE_INVALID_ATTRIBUTE_VALUE 0x0106
N_CREATE_MISSING_ATTRIBUTE 0x0120
N_CREATE_MISSING_ATTRIBUTE_VALUE 0x0121
N_CREATE_MISTYPED_ARGUMENT 0x0212
N_CREATE_NO_SUCH_ATTRIBUTE 0x0105
N_CREATE_NO_SUCH_SOP_CLASS 0x0118
N_CREATE_NO_SUCH_SOP_INSTANCE 0x0112
N_CREATE_PROCESSING_FAILURE 0x0110
N_CREATE_RESOURCE_LIMITATION 0x0213
N_CREATE_UNRECOGNIZED_OPERATION 0x0211
N_CREATE_NO_MEMORY_ALLOCATION_POSSIBLE 0x0106
N_CREATE_TEMPORARILY_NO_MEMORY 0x0213
N_CREATE_MEMORY_ALLOCATION_NOT_SUPPORTED 0xB600
N_CREATE_REQUESTED_MIN_OR_MAX_DENSITY_OUTSIDE_RANGE 0xB605
N_CREATE_ATTRIBUTE_VALUE_OUT_OF_RANGE 0x0116
N_CREATE_ATTRIBUTE_LIST_ERROR 0x0107
Basic Print Image Overlay Box FAILURE codes
N_CREATE_FAILURE_COMBINED_REQUIRES_CROPPING 0xC616
Modify GP Performed Procedure Step REFUSED codes
N_CREATE_REFUSED_SPS_NOT_IN_PROGRESS 0xA504
N_CREATE_REFUSED_UNMATCHED_TRANSACTION_ID 0xA505
N_DELETE_RSP Response Codes
SUCCESS code
N_DELETE_SUCCESS 0x0000
FAILURE codes
N_DELETE_CLASS_INSTANCE_CONFLICT 0x0119
N_DELETE_DUPLICATE_INVOCATION 0x0210
N_DELETE_MISTYPED_ARGUMENT 0x0212
N_DELETE_NO_SUCH_SOP_CLASS 0x0118
N_DELETE_NO_SUCH_SOP_INSTANCE 0x0112
N_DELETE_PROCESSING_FAILURE 0x0110
N_DELETE_RESOURCE_LIMITATION 0x0213
N_DELETE_UNRECOGNIZED_OPERATION 0x0211
4.4 Error Traces

For service technicians all errors are reported inside a log file (dicom.log and dicom.bak for older
versions). You can also find information messages and warning messages, see the sample below:
[11:50:33 - 0000] LOG => *****************************************************************

[11:50:33 - 0000] LOG => Logging Stopped *************************************************
[11:50:49 - 0000] LOG => Logging Started *************************************************
[11:50:49 - 0000] LOG => *****************************************************************
[11:50:49 - 0000] INFO => DICOM: Device = 'ConquestQuery' RemotePort = 1105 Host =
'192.168.0.139'
[11:50:49 - 0000] INFO => DICOM: MyTitle = 'B380' RemoteTitle = 'CONQUESTSRV1' ServiceList =
'Query_SCU_Service_List'
[11:50:50 - 0000] INFO => Service PATIENT_STUDY_ONLY_QR_FIND available
[11:50:50 - 0000] INFO => Service PATIENT_STUDY_ONLY_QR_MOVE available
[11:50:50 - 0000] INFO => Service STUDY_ROOT_QR_FIND available
[11:50:50 - 0000] INFO => Service STUDY_ROOT_QR_MOVE available
[11:50:50 - 0000] INFO => Service PATIENT_ROOT_QR_FIND available
[11:50:50 - 0000] INFO => Service PATIENT_ROOT_QR_MOVE available
[11:50:55 - 0000] WARN => File ./datafiles/conquestquery.qry Section STUDY_ROOT_QR_FIND not
found!
[11:50:55 - 0000] WARN => File ./datafiles/conquestquery.qry Section REF_STUDY not found!
5 Security
FLUOROSTAR does not support any specific security measures.
It is assumed that FLUOROSTAR 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
FLUOROSTAR.
• Firewall or router protections to ensure that FLUOROSTAR only has network access to approved external
hosts.
• Any communication with external hosts and services outside the locally secured environment use
appropriate secure network channels (e.g. such as a Virtual Private Network (VPN)).
Other network security procedures such as automated intrusion detection may be appropriate in some
environments. Additional security features may be established by the local security policy and are beyond the
scope of this conformance statement.
6 Annexes
6.1 IOD Contents
6.1.1 Usage of attributes from received IOD’s

No SOP Class specific fields are required.
6.1.2 Attribute Mapping

Not applicable.
6.1.3 Coerced/Modified fields.

No coercion is performed.
6.2 Data Dictionary of Private Attributes

No private attributes are defined.
6.3 Coded Terminologies and Templates

Not applicable.
6.4 Grayscale image consistency

Not applicable.
6.5 Standard Extended / Specialized / Private SOP Classes

No private SOP classes are supported.
Extensions and specializations are summarized below.
6.6 Private Transfer Syntaxes

*)Private DICOM Attribute für FLUOROSTAR
Section: STANDARD_XRAY_RF for Store Image and Image to File
TAG- Content Example **)

Code
0009,0010 Identifier/Version-String GEOEC-FLUOROSTAR-RF-IMAGE-PARAMETERS
V1.00
0009,0011 PICDEF1=F1;F2;F3;F4;F5; PICDEF1=1.23;1.23;2.23;3.46;4.57;
F1-F5 = Floating Point Parameter
Meaning
F1: ZoomX F2: ZoomY
F3: AutoWnd F4:
RegelWnd
F5: IrisWnd
0009,0012 PICDEF2=V1;V2;V3;V4;V5;V6;V7; PICDEF2=0;0;45;12;4;22;23;
V1-v7=Integer Values
Meaning:
V1: GreyW V2: GreyL
V3: Rotation V4: Zoom
V5: Filter V6:
FilterDepth
V7: Integration
0009,0013 PICDEF3= V1;V2;V3;V4;V5;V6;V7; PICDEF3=1;0;0;0;0;12;3;
V1-V7=Integer Values
Meaning:
V1: AutoWindow V2:
InversePic
V3: FlipH V4: FlipV
V5: PicNum V6:
NullRot
V7: Mode
0009,0014 PICDEF4= PICDEF4=1200;24;6;7;8;12;9;14;15;
V1;V2;V3;V4;V5;V6;V7;V8;V9
V1-V9=Integer Values
Meaning:
V1: kV V2: mA
V3: kVMan V4: IISize
V5: DAPSnap V6:
DAPSnapTime
V7: DAPSession V8:
DAPTime
V9: DAPFilm

00 441024 01 FluorostarDicomConfStat 051219

Uploaded by

Copyright:

Available Formats

00 441024 01 FluorostarDicomConfStat 051219

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

00 441024 01 FluorostarDicomConfStat 051219

Uploaded by

Copyright:

Available Formats

GE Medical Systems DICOM CONFORMANCE GE OEC Fluorostar Systems

Copyright 2004 by General Electric Co.

6.5 STANDARD EXTENDED / SPECIALIZED / PRIVATE SOP CLASSES ............................................................ 32

MergeCOM is a registered trademark of Merge Technologies Incorporated (d/b/a Merge eFilm)

Document Id.: GE-OEC-FluorostarConfStat-2730

Project: 2730-DICOM-Communication Library

Author: U. Fleisch (UF)

Conformance Statement Overview

Fluorostar implements the necessary services to communicate via DICOM

• to request Worklists from the Worklist Servers

This document is intended to describe Fluorostar conformance to DICOM.

Table 1-1 provides an overview of the network services supported by Fluorostar

1.1 Revision History

1.3 SCOPE AND FIELD OF APPLICATION

1.4 IMPORTANT REMARKS

integration analysis is correctly performed.

1.5 Definitions, Terms and Abbreviations

1.7 Functionality in brief

2.1 IMPLEMENTATION MODEL

2.1.1 Application Data Flow

2.1.2 Functional Definitions of the FLUOROSTAR AE

2.2.1 FLUOROSTAR AE Specification

SOP Classes SOP Class UIP

2.2.1.2 Association Policies

General FLUOROSTAR Presentation Context

2.2.1.2.2 Number of Associations

2.2.1.2.3 Asynchronous Nature

2.2.1.2.4 Implementation Identifying Information

2.2.1.3 Association Initiation Policy

2.2.1.3.1 Activity – Export Images

2.2.1.3.1.1 Description and Sequencing of Activities

If an image should be stored on a PACS, FLUOROSTAR makes a C-STORE request to the

2.2.1.3.1.2 Proposed Presentation Contexts

The presentation context actually proposed depends on a setting in FLUOROSTAR.

2.3 Network Interfaces

2.3.1 Physical Network Interface

2.3.2 Additional Protocols

2.3.3 SUPPORT OF CHARACTER SETS

2.4.1 AE Connection Parameter

2.4.1.1 Local Application Title

2.4.1.2 Remote Application Title

2.4.1.3 Host Name

2.4.1.4 Port Number

2.5 DICOM Message Transfer in Detail

Supported DICOM Standards:

Used Support Library:

Message Content can be changed in different ways:

• (CV) Configuration Value :

• (UD) User Defined

3 Fluorostar realized DICOM Services

3.1 DICOM Echo

3.1.1 General Echo Features

3.1.2 Limitations of Echo Service

3.1.3 Description and Sequencing of Activities

3.1.4 SOP Specific Conformance

3.2 DICOM Print Service

3.2.1 General Print Features

3.2.2 SOP Specific Conformance

0018,1201 Time of Last Calibration

2010,0110 Empty Image Density (BLACK, WHITE)