TelePax DICOM Conformance Statement - healthy-it.com · PDF fileDCS2004/003 TelePax DICOM Conformance Statement

DCS2004/003

TelePax DICOM ConformanceStatement

http://www.healthy-it.com

Table of Contents

Chapter I Document Identification 4

Chapter II Introduction 6..................................................................................... 61 Scope and Field of Application

..................................................................................... 62 References

..................................................................................... 63 Important Consideration

..................................................................................... 64 Acknowledgement of Trade names

Chapter III Implementation model 8..................................................................................... 81 Application Dataflow Diagram

..................................................................................... 82 Functional Definitions of Application Entities

..................................................................................... 93 Sequencing of Real World Activities

Chapter IV Application Entity Specifications 12..................................................................................... 121 TelePax 1.0 DICOM services AE specifications

..................................................................................... 13Association Establishment Policies

..................................................................................... 13General

..................................................................................... 13Number of Associations

..................................................................................... 13Asynchronous Nature

..................................................................................... 13Implementation Identifying Information

..................................................................................... 13Association Initiation Policy

..................................................................................... 14Verify Communication with a Remote System

..................................................................................... 14Associated Real World Activity

..................................................................................... 14Accepted Presentation Contexts

..................................................................................... 14SOP Specific Conformance Statement for SOP Class Verification

..................................................................................... 14Send Images to a Remote System


..................................................................................... 14Proposed Presentation Contexts

..................................................................................... 15Query a Remote Database



..................................................................................... 15SOP Specific Conformance Statement for SOP Class Query

..................................................................................... 16Retrieve from a Remote System



..................................................................................... 16SOP Specific Conformance Statement for SOP Class Retrieve

..................................................................................... 16Print to a remote Laser Imager



IContents

..................................................................................... 17SOP Specific Conformance Statement for Meta SOP Classes BasicGrayscale and Color Print Management

..................................................................................... 17Conformance for SOP Class Basic Film Session

..................................................................................... 17Conformance for SOP Class Basic Film Box

..................................................................................... 18Conformance for SOP Class Basic Grayscale Image Box

..................................................................................... 18Optional Meta SOP Classes for Basic Grayscale Print Management

..................................................................................... 18Optional Meta SOP Classes for Basic Color Print Management

..................................................................................... 182 TelePax DICOM Media Server AE

..................................................................................... 18Implementation Model

..................................................................................... 18Application Data Flow

..................................................................................... 18File Meta Information Options

..................................................................................... 18AE Specifications

..................................................................................... 18Application Entity TelePax Database Service Specification

..................................................................................... 19Real-World Activities

..................................................................................... 19Real World Activity: Display Directory of CD-R disk

..................................................................................... 19Real World Activity Read images from CD-R disk

..................................................................................... 20Real World Activity: Write images

..................................................................................... 21Character Sets

Chapter V Communication Profile 24..................................................................................... 241 Supported Communication Stacks

..................................................................................... 242 OSI Stack

..................................................................................... 243 TCP/IP Stack

..................................................................................... 24Physical Media Support

..................................................................................... 244 Point-to-Point Stack

Chapter VI EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS 26..................................................................................... 261 Standard Extended / Specialized / Private SOPs

..................................................................................... 262 Private Transfer Syntaxes

Chapter VII CONFIGURATION 28..................................................................................... 281 AE Title / Presentation Address Mapping

..................................................................................... 282 Configurable Parameters

Chapter VIII SUPPORT OF EXTENDED CHARACTER SETS 30

TelePax DICOM Conformance StatementII

DocumentIdentification

I

4 TelePax DICOM Conformance Statement

© 2001 ... Healthy Information Technology, H.I.T. Inc.

1 Document Identification

DICOM Conformance Statement

for

TelePax Product Line

Implementation Class UID1.2.826.0.1.3680043.2.260

Product line TELEPAX

Version 1.0

Status Final

Date 2000

Rev 2.0

Product TELEPAX

Date 2003

Document : DCS-2000-001

IntroductionII



2 Introduction

2.1 Scope and Field of Application

This document is the DICOM conformance statement to describes version 1.0 of TelePaxproducts of "Healthy Information Technology" (HIT). The purpose of this document is to describehow TelePax product collaborates in a DICOM network with other medical imaging applicationsthat conform to the DICOM 3.0 standards.

2.2 References

Digital Imaging and Communications in Medicine (DICOM), parts 1through 14 (NEMA PS 3.1-14)

2.3 Important Consideration

This DICOM Conformance Statement by itself is not sufficient to guarantee successfulconnectivity between TelePax and equipment from other vendors.

The integration of equipment from different vendors (including HIT) goes beyond the scope of theDICOM 3.0 standard and the DICOM Conformance Statements from HIT and other vendors.

It is the responsibility of the user (or user' s agent) to assess the application requirements and todesign a solution that integrates HIT equipment with equipment from other vendors.

When the comparison of this DICOM Conformance Statement with a DICOM ConformanceStatement from another vendor indicates that connectivity should be possible it is theresponsibility of the user (or user' s agent) to verify this by carrying out validation tests and tocheck whether all required functionality (such as cutlines) is met.

With regard to the future evolution of the DICOM 3.0 standard HIT reserves the right to makechanges to the TelePax architecture described in this document. The user (or user' s agent)should ensure that any equipment connected via DICOM to HIT equipment also follows the futureevolution of the DICOM 3.0 standard. Failure to do so may result in (partial) loss of connectivity.

2.4 Acknowledgement of Trade names

All trade names mentioned in this document are recognized.TelePax is a registered trademark of Healthy Information Technology.

Implementationmodel

III



3 Implementation model

3.1 Application Dataflow Diagram

The TelePax DICOM services are implemented as a separate Windows NT Services (store SCP)that run as background processes. It starts automatically during system start-up and will remainactive until shutdown. This means that store-requests can be accepted at all times when thesystem is up and running regardless of whether the TelePax application is active or not.

The TelePax Services are responsible for image reception and transmission in addition toaccepting requests for database queries and retrieves.

Figure 1: TelePax application data flow diagram

3.2 Functional Definitions of Application Entities

The Application Entity (AE) of the TelePax 1.0 Connection Service acts as an SCU for theverification, storage, and storage commitment SOP classes and as an SCP for verification,storage, query, retrieve, and storage commitment SOP classes.

The Application Entity (AE) of the TelePax 1.0 Print Service acts as an SCU for the basicgrayscale print management meta SOP classes.

9Implementation model


3.3 Sequencing of Real World Activities

Not applicable.

Application EntitySpecifications

IV



4 Application Entity Specifications

4.1 TelePax 1.0 DICOM services AE specifications

The TelePax 1.0 DICOM services provide support for the following DICOM V3.0 SOP Classes asan SCU:

SOP Classes as SCU

SOP Class Name SOP Class UIDVerification 1.2.840.10008.1.1CR/DR (Computed/Digital Radiography) Image Storage 1.2.840.10008.5.1.4.1.1.1DX (Digital X-Ray for presentation) ImageStorage 1.2.840.10008.5.1.4.1.1.1.1MG (Digital X-Ray Mammography for presentation) ImageStorage1.2.840.10008.5.1.4.1.1.1.2IO (Digital X-Ray Intra-Oral for presentation) Image Storage 1.2.840.10008.5.1.4.1.1.1.3CT (Computer Tomography) Image Storage 1.2.840.10008.5.1.4.1.1.2MR (Magnetic Resonance) Image Storage 1.2.840.10008.5.1.4.1.1.4US (Ultra Sound) Image Storage(Retired) 1.2.840.10008.5.1.4.1.1.6US (Ultra Sound) ImageStorage 1.2.840.10008.5.1.4.1.1.6.1US (Ultra Sound) Multi-Frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1SC (Secondary Capture) Image Storage 1.2.840.10008.5.1.4.1.1.7NM (Nuclear Medicine) Image Storage 1.2.840.10008.5.1.4.1.1.20XA (X-Ray Angiographic) ImageStorage 1.2.840.10008.5.1.4.1.1.12.1RF (X-Ray Radiofluoroscopic) Image Storage 1.2.840.10008.5.1.4.1.1.12.2Patient Root Query/Retrieve Model – FIND 1.2.840.10008.5.1.4.1.2.1.1Patient Root Query/Retrieve Model – MOVE 1.2.840.10008.5.1.4.1.2.1.2Study Root Query/Retrieve Model –FIND 1.2.840.10008.5.1.4.1.2.2.1Study Root Query/Retrieve Model – MOVE 1.2.840.10008.5.1.4.1.2.2.2Patient/Study Only Query/Retrieve Model –FIND 1.2.840.10008.5.1.4.1.2.3.1Patient/Study Only Query/Retrieve Model – MOVE 1.2.840.10008.5.1.4.1.2.3.2

The TelePax 1.0 DICOM services provide support for the following DICOM 3.0 SOP Classes asan SCP:

SOP Classes as SCP

SOP Class Name SOP Class UIDVerification 1.2.840.10008.1.1CR/DR (Computed/Digital Radiography) Image Storage 1.2.840.10008.5.1.4.1.1.1DX (Digital X-Ray for presentation) ImageStorage 1.2.840.10008.5.1.4.1.1.1.1MG (Digital X-Ray Mammography for presentation) ImageStorage1.2.840.10008.5.1.4.1.1.1.2IO (Digital X-Ray Intra-Oral for presentation) Image Storage 1.2.840.10008.5.1.4.1.1.1.3CT (Computer Tomography) Image Storage 1.2.840.10008.5.1.4.1.1.2MR (Magnetic Resonance) Image Storage 1.2.840.10008.5.1.4.1.1.4US (Ultra Sound) Image Storage(Retired) 1.2.840.10008.5.1.4.1.1.6

13Application Entity Specifications


US (Ultra Sound) ImageStorage 1.2.840.10008.5.1.4.1.1.6.1US (Ultra Sound) Multi-Frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1SC (Secondary Capture) Image Storage 1.2.840.10008.5.1.4.1.1.7NM (Nuclear Medicine) Image Storage 1.2.840.10008.5.1.4.1.1.20XA (X-Ray Angiographic) ImageStorage 1.2.840.10008.5.1.4.1.1.12.1RF (X-Ray Radiofluoroscopic) Image Storage 1.2.840.10008.5.1.4.1.1.12.2

4.1.1 Association Establishment Policies

4.1.1.1 General

The configuration of the TelePax 1.0 DICOM services shall define such parameters as AE title,host name, and port number that are shared by the Connection

4.1.1.2 Number of Associations

The TelePax 1.0 Connection Service supports multiple associations both as an SCU andSCP. The TelePax accepts multiple associations from different remote AE's at a time. There maybe several concurrent associations active and processed in parallel.

The number of simultaneous associations that may be supported is limited by the availableresources supported by the underlying operating system.

4.1.1.3 Asynchronous Nature

There is no asynchronous activity in this implementation.

4.1.1.4 Implementation Identifying Information

The Implementation Class UID is : 1.2.826.0.1.3680043.2.260

4.1.2 Association Initiation Policy

The TelePax "C-Send" service initiates associations for the followingactivities:· The TelePax user wants to verify the DICOM communication with a remote system.· The TelePax user wants to send images from the local database to a remote system.

The TelePax "Query / Retrieve Service" initiates associations for thefollowing activities:· The TelePax user wants to query the contents of a remote database.· The TelePax user wants to retrieve images from a remote database to the localTelePax

database.

The TelePax "Print Service" initiates associations for the followingactivities:· The TelePax user wants to print images to a DICOM laser imager.



4.1.2.1 Verify Communication with a Remote System

4.1.2.1.1 Associated Real World Activity

The TelePax 1.0 Connection Service sends out a request to test DICOM communication with aremote DICOM system.

4.1.2.1.2 Accepted Presentation Contexts

Abstract Syntax: VerificationAbstract Syntax UID: 1.2.840.10008.1.1Transfer Syntax Name: Implicit VR, Little EndianTransfer Syntax UID: 1.2.840.10008.1.2Role: SCUExtended Negotiation: NONE

4.1.2.1.3 SOP Specific Conformance Statement for SOP Class Verification

The TelePax Connection Service provides standard conformance.

4.1.2.2 Send Images to a Remote System


The user of the TelePax system makes a selection of one or more studies and series in the localDatabase and subsequently presses the Send button which will initiate the transfer of imagesfrom the local database of TelePax to the remote system using TelePax DICOM send wizard.

4.1.2.2.2 Proposed Presentation Contexts

Presentation Context Table for Send To Remote System

Abstract Syntax Name Abstract Syntax UID Transfer SyntaxRole Extended NegotiationCR/DR Image Storage 1.2.840.10008.5.1.4.1.1.1 See below SCU NoneDX Image Storage 1.2.840.10008.5.1.4.1.1.1.1 See below SCU NoneMG Image Storage 1.2.840.10008.5.1.4.1.1.1.2 See below SCU NoneIO Image Storage 1.2.840.10008.5.1.4.1.1.1.3 See below SCU NoneCT Image Storage 1.2.840.10008.5.1.4.1.1.2 See below SCU NoneMR Image Storage 1.2.840.10008.5.1.4.1.1.4 See below SCU NoneUS Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.6 See below SCU NoneUS Image Storage 1.2.840.10008.5.1.4.1.1.6.1 See below SCU NoneUS Multi-Frame Image St. 1.2.840.10008.5.1.4.1.1.3.1 See below SCU NoneSC Image Storage 1.2.840.10008.5.1.4.1.1.7 See below SCU NoneNM Image Storage 1.2.840.10008.5.1.4.1.1.20 See below SCU NoneXA X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 See below SCU NoneRF X-Ray Radiofluoroscopic Image Storage 1.2.840.10008.5.1.4.1.1.12.2 See below SCU None

Transfer Syntaxes for Send To Remote System

Name UIDImplicit VR, LittleEndian 1.2.840.10008.1.2Explicit VR, Little Endian 1.2.840.10008.1.2.1Explicit VR, Lossy JPEG 8-Bit Image Compression 1.2.840.10008.1.2.4.50Explicit VR, Lossy JPEG 12-Bit Image Compression 1.2.840.10008.1.2.4.51Explicit VR, JPEG Lossless, Non-Hierarchical, First-Order Prediction 1.2.840.10008.1.2.4.70



4.1.2.3 Query a Remote Database


The user of the TelePax system wants to have a view on a remote DICOM database. This is donevia the TelePax Query / Retrieve wizard, which enables the TelePax user either Query all theremote database list, or select criteria based on Patient root variables as patient name, date ofbirth, sex and Patient ID, or study UID, Date, and description. Also, a "Study root" query isavailable by modality name and body part.


Presentation Context Table for Remote Database Query

Abstract Syntax Abstract Syntax UID Transfer Syntax Name TransferSyntax UIDPatient Root Query/Retrieve Model – FIND 1.2.840.10008.5.1.4.1.2.1.1 Implicit VR, LittleEndian 1.2.840.10008.1.2Study Root Query/Retrieve Model – FIND 1.2.840.10008.5.1.4.1.2.2.1 Implicit VR, LittleEndian 1.2.840.10008.1.2Patient/Study Only Query/Retrieve Model – FIND 1.2.840.10008.5.1.4.1.2.3.1 Implicit VR, LittleEndian 1.2.840.10008.1.2

4.1.2.3.3 SOP Specific Conformance Statement for SOP Class Query

The TelePax Database Service does not support Relational Queries.The following keys are supported for the Patient Root Query:

Supported keys for Patient Root Query

Level Description Tag TypePatient Patient' s Name (0010,0010) RPatient Patient ID (0010,0020) UPatient Patient' s Birth Date (0010,0030) OPatient Patient' s Sex (0010,0040) OStudy Study Date (0008,0020) RStudy Study Time (0008,0030) RStudy Accession Number (0008,0050) RStudy Study ID (0020,0010) RStudy Study Instance UID (0020,000D) UStudy Referring Physician' s Name (0008,0090) OStudy Study Description (0008,1030) OStudy Modalities in Study (0008,0061) OStudy Number of Study Related Series (0020,1206) OStudy Number of Study Related Instances/Images (0020,1208) OSeries Modality (0008,0060) RSeries Series Number (0020,0011) RSeries Series Instance UID (0020,000E) USeries Number of Series Related Instances/Images (0020,1209) OImage Image Number (0020,0013) RImage SOP Instance UID (0008,0018) UImage Rows (0028,0010) OImage Columns (0028,0011) OImage Bits Stored (0028,0101) O

The Patient/Study levels in the table above are also supported for thePatient/Study Query.

For a "Study Root" Query the following keys are supported:

Level Description Tag Type



Study Study Date (0008,0020) RStudy Study Time (0008,0030) RStudy Accession Number (0008,0050) RStudy Patient' s Name (0010,0010) RStudy Patient ID (0010,0020) RStudy Study ID (0020,0010) RStudy Study Instance UID (0020,000D) UStudy Referring Physician' s Name (0008,0090) OStudy Study Description (0008,1030) OStudy Patient' s Birth Date (0010,0030) OStudy Patient' s Sex (0010,0040) OStudy Modalities in Study (0008,0061) OStudy Number of Study Related Series (0020,1206) OStudy Number of Study Related Instances/Images (0020,1208) OSeries Modality (0008,0060) RSeries Series Number (0020,0011) RSeries Series Instance UID (0020,000E) USeries Number of Series Related Instances/Images (0020,1209) OImage Image Number (0020,0013) RImage SOP Instance UID (0008,0018) UImage Rows (0028,0010) OImage Columns (0028,0011) OImage Bits Stored (0028,0101) O

The TelePax expects the remote Query SCP to perform any of the followingmatching methods:· Single Value matching· Wild-Card matching (using [*] or [?])

4.1.2.4 Retrieve from a Remote System


After a view on a remote DICOM database has been obtained the user makes a selection of oneor more studies, series or images and subsequently presses the [Retrieve] button. This will initiatethe transfer of images from the remote system to the local database of TelePax.


Abstract Syntax Name Abstract Syntax UID Transfer Syntax Name TransferSyntax UIDPatient Root Query/Retrieve Model – MOVE 1.2.840.10008.5.1.4.1.2.1.2 Implicit VR, LittleEndian 1.2.840.10008.1.2Study Root Query/Retrieve Model – MOVE 1.2.840.10008.5.1.4.1.2.2.2 Implicit VR, LittleEndian 1.2.840.10008.1.2Patient/Study Only Query/Retrieve Model – MOVE 1.2.840.10008.5.1.4.1.2.3.2 Implicit VR, LittleEndian 1.2.840.10008.1.2

4.1.2.4.3 SOP Specific Conformance Statement for SOP Class Retrieve

The TelePax Database Service provides standard conformance.

4.1.2.5 Print to a remote Laser Imager


The TelePax user selects a study in the local database and submits it to the Print Service as a jobfor the desired laser imager.




Abstract Syntax Name Abstract Syntax UID Transfer Syntax Name Transfer SyntaxUIDBasic grayscale Print Management 1.2.840.10008.5.1.1.9 Implicit VR, Little Endian 1.2.840.10008.1.2

4.1.2.5.3 SOP Specific Conformance Statement for Meta SOP Classes Basic Grayscale and Color Print Management

The TelePax Print Service supports the following mandatory SOP classes as definedby the Basic Grayscale Print Management Meta class:

SOP Class Name SOP Class UIDBasic Film Session 1.2.840.10008.5.1.1.1Basic Film Box 1.2.840.10008.5.1.1.2Basic Grayscale Image Box 1.2.840.10008.5.1.1.4Printer 1.2.840.10008.5.1.1.16

For the Basic Color Print Management Meta SOP class it supports:

SOP Class Name SOP Class UIDBasic Film Session 1.2.840.10008.5.1.1.1Basic Film Box 1.2.840.10008.5.1.1.2Basic Color Image Box 1.2.840.10008.5.1.1.4.1Printer 1.2.840.10008.5.1.1.16

4.1.2.5.3.1 Conformance for SOP Class Basic Film Session

The TelePax Print Service includes the following attributes in the N-CREATE for the Basic FilmSession SOP class:

Description Tag Range of valuesNumber of Copies (2000,0010) 1-10000 (Max. user value configurable, default 5)Print Priority (2000,0020) "LOW", "MED", "HIGH"Medium Type (2000,0030) <configurable>Film Destination (2000,0040) "MAGAZINE", "PROCESSOR", <more configurable>Film Session Label (2000,0050) <configurable>

The N-DELETE is used to delete the complete Basic Film Session SOP instance hierarchy.

4.1.2.5.3.2 Conformance for SOP Class Basic Film Box

The TelePax Print Service includes the following attributes in the N-CREATE for the Basic FilmBox SOP class:

Description Tag Usage Range of valuesFilm Orientation (2010,0040) A "PORTRAIT", "LANDSCAPE"Film Size ID (2010,0050) A <configurable>Magnification Type (2010,0060) C "BILINEAR", "CUBIC", "NONE", <moreconfigurable>Max Density (2010,0130) C <configurable>Configuration Information (2010,0150) C <configurable>Smoothing Type (2010,0080) C <configurable>Border Density (2010,0100) C <configurable>Empty Image Density (2010,0110) C <configurable>Min Density (2010,0120) C <configurable>Trim (2010,0140) C "YES", "NO"

The N-SET is currently unused. The N-ACTION is used to print a complete Basic Film Box SOP



instance and N-DELETE is used to delete it after printing.

4.1.2.5.3.3 Conformance for SOP Class Basic Grayscale Image Box

The TelePax Print Service includes the following attributes in the N-SET for the Basic GrayscaleImage SOP class:

Description Tag UsagePolarity (2020,0020) A

4.1.2.5.4 Optional Meta SOP Classes for Basic Grayscale Print Management

Currently these are not supported by the TelePax Print Service.

4.1.2.5.5 Optional Meta SOP Classes for Basic Color Print Management

Currently these are not supported by the TelePax Print Service.

4.2 TelePax DICOM Media Server AE

TelePax provides standard conformance to the DICOM Media Storage Service and File Formatand the Media Storage Application Profiles, with the following considerations:· Uncompressed Images· JPEG Lossless compressed images

4.2.1 Implementation Model

4.2.1.1 Application Data Flow

The TelePax Read-CD application flow consists of the following items:· The TelePax Database serves and it is able to

Read directory information from the storage medium,Import images from the storage medium andWrite images and directory information to the storage medium.

· The Real World Activities involved are available through the TelePax AE' s user interface.

TelePax does not support writing of multi session CD-R disks.

4.2.1.2 File Meta Information Options

The Implementation Class UID is 1.2.826.0.1.3680043.2.260

4.2.2 AE Specifications

4.2.2.1 Application Entity TelePax Database Service Specification

TelePax supports the following application profile:

Description 3.2.2.1.1 IdentifierGeneral Purpose CD-R Image Interchange profile STD-GEN-CD



4.2.2.2 Real-World Activities

TelePax supports the following Real World Activities within the profile mentioned above:

Supported Application Profiles Real World Activity Role SC OptionSTD-GEN-CD Display Directory of CD-R diskFSR Interchange

Read image(s) from CD-R disk FSR InterchangeWrite image(s) on CD-R disk FSC Interchange

4.2.2.2.1 Real World Activity: Display Directory of CD-R disk

TelePax will act as a FSR when reading the directory of the medium. This will result in anoverview of the patients, studies, series and images in the TelePax Remote View area.

The display is structured in one of the following ways:

Type of query LevelsStudy Root Query Study, SeriesPatient Root Query Patient, Study, Series

At least the Patient Name and Patient ID fields are necessary for a correct display of the directoryinformation. The following DICOMDIR keys are used for the user to be able to distinguish betweenthe objects.

Type of query Level Displayed fields TagPatient root Patient Patient Name (0010,0010)Patient root Patient Patient ID (0010,0020)Patient root Patient Patient Date of Birth (0010,0030)Patient root Patient Patient Sex (0010,0040)Study root Study Patient Name (0010,0010)Study root Study Patient ID (0010,0020)Study root Study Patient Date of Birth (0010,0030)Study root Study Patient Sex (0010,0040)

4.2.2.2.2 Real World Activity Read images from CD-R disk

TelePax will act as a FSR when reading all/selected images from the CD-R medium. This featurewill be available through the Import command from the Remote View area. The followingmandatory attributes of the DICOM images are required for the correct storage of the images inthe TelePax Local Database.

IOD Field description TagPATIENT Patient Name (0010,0010)PATIENT Patient ID (0010,0020)STUDY Study Date (0008,0020)STUDY Study Time (0008,0030)STUDY Study ID (0020,0010)STUDY Accession Number (0008,0050)STUDY Study UID (0020,000D)SERIES Modality (0008,0060)SERIES Series UID (0020,000E)SERIES Series Number (0020,0011)IMAGE Referenced SOP Class UID In File (0004,1510)IMAGE Referenced SOP Instance UID In File (0004,1511)IMAGE Referenced Transfer Syntax UID In File (0004,1512)IMAGE Referenced File ID (0004,1500)IMAGE Image Number (0020,0013)



4.2.2.2.3 Real World Activity: Write images

TelePax will act as a FSC when writing all or selected patients, studies or series from the localdatabase view to random access archive media (like MODs). TelePax does not write CD-R' sitself, but it is able to prepare the contents for a single session CD-R in a way that third partysoftware could create a DICOM Part 10 compliant CD-R volume, merely by copying the contentsof a designated directory on the PC' s hard disk to the CD-R. In addition to this TelePax providesfacilities

· to start this CD-creation process,· to temporarily lock the database in order to keep the archive stable during the process, and· to check the contents of the CD after it has been created.

If images are stored non-compressed in the TelePax local database, and JPEG Losslesscompressed is configured for writing DICOM Part 10 studies, the compression is performed priorto saving the images. Please note that this feature lies outside the scope of the STD-GEN-CDApplication Profile. If a requested compression is not possible for some reason, the images will besaved non-compressed with Explicit VR and Little Endian transfer syntax. Writing studies to aDICOM Part 10 Volume is an optional feature of TelePax, which requires a separate license.

TelePax creates DICOMDIR files for the DICOM Part 10 Volumes, containing the following keys:

Record Type Key description Tag TypePATIENT Referenced SOP Class UID In File (0004,1510) 1CPATIENT Referenced SOP Instance UID In File (0004,1511) 1CPATIENT Referenced Transfer Syntax UID In File (0004,1512) 1CPATIENT Referenced File ID (0004,1500) 1CPATIENT Patient Name (0010,0010) 2PATIENT Patient ID (0010,0020) 1PATIENT Patient Date of Birth (0010,0030) 3PATIENT Sex (0010,0040) 3PATIENT Patient Time of Birth (0010,0032) 3PATIENT Referenced Patient Sequence (0008,1120) 3PATIENT Other Patient Ids (0010,1000) 3PATIENT Other Patient Names (0010,1001) 3PATIENT Ethnic Group (0010,2160) 3PATIENT Comments (0010,4000) 3STUDY Referenced SOP Class UID In File (0004,1510) 1CSTUDY Referenced SOP Instance UID In File (0004,1511) 1CSTUDY Referenced Transfer Syntax UID In File (0004,1512) 1CSTUDY Referenced File ID (0004,1500) 1CSTUDY Study Date (0008,0020) 1STUDY Study Time (0008,0030) 1STUDY Study ID (0020,0010) 1STUDY Accession Number (0008,0050) 2STUDY Study UID (0020,000D) 1CSTUDY Study Description (0008,1030) 3STUDY Referring Physician (0008,0090) 3STUDY Reading Physician (0008,1060) 3STUDY Referenced Study Sequence (0008,1110) 3SERIES Referenced SOP Class UID In File (0004,1510) 1CSERIES Referenced SOP Instance UID In File (0004,1511) 1CSERIES Referenced Transfer Syntax UID In File (0004,1512) 1CSERIES Referenced File ID (0004,1500) 1CSERIES Modality (0008,0060) 1SERIES Series UID (0020,000E) 1SERIES Series Number (0020,0011) 1SERIES Laterality (0020,0060) 3SERIES Series Date (0008,0021) 3SERIES Series Time (0008,0031) 3SERIES Performing Physician (0008,1050) 3SERIES Protocol (0018,1030) 3SERIES Description (0008,103E) 3SERIES Operator (0008,1070) 3SERIES Body Part (0018,0015) 3SERIES Patient Position (0018,5100) 3SERIES Smallest Pixel (0028,0108) 3SERIES Largest Pixel (0028,0109) 3IMAGE Referenced SOP Class UID In File (0004,1510) 1C



IMAGE Referenced SOP Instance UID In File (0004,1511) 1CIMAGE Referenced Transfer Syntax UID In File (0004,1512) 1CIMAGE Referenced File ID (0004,1500) 1CIMAGE Image Type (0008,0008) 3IMAGE Referenced Image Sequence (0008,1140) 3IMAGE Image Number (0020,0013) 1IMAGE Rows (0028,0010) 3IMAGE Columns (0028,0011) 3

TelePax is not able to update DICOMDIR files originally created by other vendors.

4.2.3 Character Sets

TelePax does not change the character set on incoming studies before they are written to aDICOM Part 10 Medium. Therefore the character set depends on the system creating the DICOMimages to be stored.

CommunicationProfile

V



5 Communication Profile

5.1 Supported Communication Stacks

The TelePax DICOM services provide DICOM V3.0 TCP/IP Network Communication Support asdefined in Part 8 of the DICOM Standard.

5.2 OSI Stack

Not supported

5.3 TCP/IP Stack

The TelePax DICOM services use the TCP/IP stack from the Microsoft Windows NT operatingsystem upon which it executes.

5.3.1 Physical Media Support

The TelePax DICOM services are not dependent on the physical medium over which the TCP/IPexecutes.

5.4 Point-to-Point Stack

Not supported.

EXTENSIONS /SPECIALIZATIONS/ PRIVATIZATIONS

VI



6 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS

6.1 Standard Extended / Specialized / Private SOPs

Not applicable.

6.2 Private Transfer Syntaxes

Not applicable.

CONFIGURATIONVII



7 CONFIGURATION

The configuration of the TelePax DICOM services are stored in the Windows NTRegistry. Only accounts (secured by passwords) with the right level of security will beable to change the configuration. This will typically be done by support personnel.

7.1 AE Title / Presentation Address Mapping

The AE title shared by the TelePax DICOM services is configurable and defaults toAE_TELEPAX. The port on which the Connection Service listens is also configurable and defaultsto 4000.

All remote systems that want to communicate with the TelePax Connection Service have to beconfigured. For systems that want to act as SCUs of the Connection Service SCP SOP classesthe following information may be needed:

· The AE title.· The host name.· The port number.

For systems with which the TelePax DICOM services want to act as SCU the following informationis needed:· The AE title.· The host name.· The port number.

7.2 Configurable Parameters

TelePax offers configuration of the following parameters, as far as the DICOM Communication isconcerned.

SUPPORT OFEXTENDED

CHARACTER SETS

VIII



8 SUPPORT OF EXTENDED CHARACTER SETSTelePax offers full support for the following character sets:

Name ValueDefault Character repertoire ISO-IR 6Latin – 1 character repertoire ISO-IR 100

Notes

31



Documents

TelePax DICOM Conformance Statement - healthy-it.com · PDF fileDCS2004/003 TelePax DICOM Conformance Statement