DICOM CONFORMANCE STATEMENT ANNEX

Table of contents :

INTRODUCTION

This document is an annex to the Conformance Statement of Medasys Digital Systems implementation of the DICOM standard into the DxNet application and is related to the definition of the privatizations done in this implementation.

DxArchive application is a general image server for the purpose of image information handling and archiving using the Medasys Digital Systems image database.
DxNet application is the subset of the DxArchive application related to network connections management.
The abbreviation MDS is used for Medasys Digital Systems company name.
The abbreviation DxDBase is used for Medasys Digital Systems image database name.

Note: The french ISO member body AFNOR has provided Medasys Digital Systems with an UID root. This UID root is only in numerical form as following: 1.2.250.1.38

PRIVATE SOP CLASS DEFINITIONS

ORIGINAL FORMAT (OF) IMAGE STORAGE SOP CLASS

The OF image Storage SOP Class is conformant to the DICOM standard, but implies restrictions on the use of transfer syntaxes as described here.

The OF image Storage SOP Class is conformant to the Storage Service Class as defined into the DICOM standard PS 3.4 Annex B part.

ORIGINAL FORMAT IMAGE INFORMATION OBJECT DEFINITION

OF image IOD description

The OF image Information Object Definition specifies an image file (as a set of pixel data and related information stored and referenced by the DxDBase) which has been imported using a specific procedure not based on the DICOM standard and for which original format retrieval capability is essential.

Such format is any of the existing standard formats " supported " (i.e. which can be imported) by the current implementation of the DxArchive application.

OF image IOD entity-relationship model

The E-R model in figure 1 de/picts those components of the DICOM Information Model which directly reference the OF image IOD. Only the Information Entities (IE) listed into the table 1 are components of the OF image IOD.

OF image IOD module table

The table 1 lists the IE modules which are components of the OF image IOD. This table refers to modules defined into the DICOM standard PS 3.3 Annex C part.

Table 1: OF image IOD modules

OF IMAGE MODULE DEFINITION

This section describes the OF image module. The table 2 contains the attibutes that are specific to the OF image module.
Table 2: OF image module attributes

OF image attribute descriptions

Identification code

The identification code (0009,00xx) is used to identify the creator of the private group elements. DxDCMserver application provides the following identifier for OF image private group:

1.2.250.1.38.1.5.1.4.1.1.1

Image Format

The image format (0009,xx00) uniquely identifies the format of the original image. DxDCMserver application provides the following list of identifiers:

1.2.250.1.38.1.2.1 = ACR-NEMA 2.0 - Little Endian byte ordering.

OF IMAGE DATA DICTIONARY

This section describes the properties of the attributes specific to the OF image module. The table 3 contains the description of the related data elements.

Table 3: OF image data dictionary

OF IMAGE TRANSFER SYNTAX RESTRICTIONS

OF image Storage SOP Class supports only non compressed transfer syntaxes, since the content of the Image Data attribute can be more than a " simple " set of pixels, and depends on the original image data format. Nevertheless, OF image Storage SOP class refers to the encapsulated image definition of the DICOM standard (see DICOM standard PS 3.5 Annex F " Encapsulated images as part of a DICOM message " introduction).

OF image Storage SOP Class supports the presentation contexts usage of the Image Transfer in the case of an Association Initiation as described into the document UL/95/XCA/13Jul95/129, and the following transfer syntaxes:

	DICOM implicit VR Little Endian transfer syntax.
	DICOM explicit VR Little Endian transfer syntax.
	DICOM explicit VR Big Endian transfer syntax.

However, the encoding process of data elements with a Value Representation OB has to be emphasize for Image Data (0009,xxF1) data element handling. Nevertheless, as described into the DICOM standard PS 3.5 part, OB is a VR which is insensitive to Little/Big Endian byte ordering.