DxMM/DxWin DICOM 3.0 Conformance Statement. Document Reference (Référence du document) : 99/ Oct30/ABA/MM103/398B

Similar documents
DxServer for Windows NT DICOM 3.0 Conformance Statement. Document Reference (Référence du document): 00/ Dec28/ABA/MM100/410A

AVIA (Dx MM) DICOM 3.0 Conformance Statement

DICOM 3.0 Conformance Statement DXIMAGE RIS

1 Introduction Scope and audience References Acronyms and abbreviations 3. 2 Implementation model... 4

SCORE 3D Workstation DICOM CONFORMANCE STATEMENT

Dx Server for Windows NT DICOM 3.0 Conformance Statement

Dx Server for Windows NT DICOM 3.0 Conformance Statement

Surgimap. DICOM Conformance Statement. Revision 2.0

Punctual Dicom Workstation

Matrix Server and Client DICOM Conformance Statement

QPC XSCAN32 DICOM 3.0 Conformance Statement Document Version October 2004

Dx Server for Windows NT DICOM 3.0 Conformance Statement

Technical Publication. DICOM Conformance Statement. Patient Browser 2.1. Document Revision 2. April 13, Copyright BrainLAB AG

XPACS DICOM 3.0 Conformance Statement Document Version October 2004

SonoWin Picture Archiving System

Infinity Medical Soft, Inc ,Higashinaganuma,Inagishi, Tokyo JAPAN

Media Writer DICOM Conformance Statement

Aloka ProSound DICOM

StellarPACS DICOM Conformance Statement. Version 1.3, August 2008 SoftTeam Solutions

ASTERIS MDS. DICOM Conformance Statement. for. Asteris Modality Distribution System (MDS) Software. Last Document Update: July 22, 2008.

DICOM Conformance Statement (DCS) Rev 1.1. Surgimap Nemaris Inc. 475 Park Ave S, 11 th Fl. New York, NY 10016

No. MIIMS0009EA DICOM CONFORMANCE STATEMENT FOR MODEL TFS-3000 (MIIMS0009EA) TOSHIBA CORPORATION 2001 ALL RIGHTS RESERVED

SYNAPSE 3D Conformance Statement FUJIFILM SYNAPSE 3D V3.0. Conformance Statement. Revision Z45N

DICOM Conformance Statement for PenFetch

DICOM Conformance Statement (DCS) Rev 1.2. Surgimap Nemaris Inc. 475 Park Ave S, 11 th Fl. New York, NY 10016

Technical Publications

Technical Publications

Digital Lightbox 1.0

DICOM 3.0 Conformance Statement for PlatinumOne Systems

WINRAD-32 Teleradiology System Conformance Claim

HCP DICOM Net DICOM Conformance Statement

Technical Publications

Technical Publications

Technical Publications

Technical Publications

Technical Publications

No. : S Rev. : A. DICOM Conformance Statement For Side Station Rev02.00

DICOM CONFORMANCE STATEMENT. BrainLAB PatientBrowser 1.0

Technical Publications

Technical Publications

Technical Publications

Hologic Physician s Viewer 5.0 DICOM Conformance Statement

STaR. DICOM Conformance Statement. September 2009 Version NO COPIES PERMITTED

Technical Publications

ETIAM Nexus. DICOM Conformance Statement.

Medical Imaging Consultants, Inc.

Technical Publications

Version 9 DICOM Conformance Statement. Version 3.05, September 2015

Patterson DICOM Imaging. DICOM Conformance Statement

DICOM 3.0 Conformance Statement **

DICOM Conformance Statement Product Name HCP DICOM Net Version

PRO DATA Srl. DICOM MODALITY WORKLIST SCU Conformance Statement (MicroPrint-modality-worklist-scu.sxw)

DICOM Conformance Statement

Technical Publication. DICOM Conformance Statement. Trauma 3.0. Document Revision 2. October 5 th, 2010

ModLink DICOM Conformance Statement

GEMINI DICOM Conformance Statement 16 Power PET/CT Imaging System Configuration

Technical Publication. DICOM Conformance Statement. DICOM Proxy 4.0. Document Revision 11. May 18, Copyright Brainlab AG

Version 7 DICOM Conformance Statement. Document Version 3.02, June 2009

1 CONFORMANCE STATEMENT OVERVIEW

DICOM CONFORMANCE STATEMENT FOR ZIOBASE 4.0

Abstract DCV DICOM CONFORMANCE. XrayVision DCV DICOM Conformance Statement. Abstract

HEALTHCARE DICOM Conformance Statement

DICOM 3.0. ENsphere CONFORMANCE STATEMENT. Physician s Workstation

DICOM Conformance Statement

Privilege/Prestige. DICOM Conformance Statement. Version Algotec Systems Ltd.

TOSHIBA AMERICA MEDICAL SYSTEMS

DICOM CONFORMANCE STATEMENT. BrainLAB PatXfer 5

Technical Publication. DICOM Conformance Statement. iplan 3.0. Document Revision 1. November 17, Copyright BrainLAB AG

DICOM Conformance Statement

DICOM Conformance Statement

Technical Publications

Technical Publications

No. MIIMS0002EAG TOSHIBA MEDICAL SYSTEMS CORPORATION ALL RIGHTS RESERVED

CADstream DICOM Conformance Statement

Whole Body X-ray CT System Supria. DICOM Conformance Statement

DAR Revision Date: July,

Conformance Statements for DICOM PaCentric Connect / Traveler

Philips Medical Systems. Xcelera R1.1L1. Document Number XPR July 2003

OASIS V4.0 DICOM Conformance Statement Rev. 3

POP-Net Essential DICOM Conformance Statement

Technical Publications

Uscan. DICOM Conformance Statement

PRO DATA Srl. MicroPrint. DICOM STORE SCU Conformance Statement (MicroPrint-prnsrv-store-scu.sxw)

NumaStore 1.0 DICOM 3.0 Conformance Statement

Technical Publications

FONAR Sympulse Dicom 3.0 Conformance Statement January 4, 2005

DICOM Conformance Statement

DICOM Conformance Statement. Konica Minolta Healthcare Americas, Inc. VZ0162UG

DICOM Conformance Statement

DICOM Conformance Statement. EasyGuide R2.1

DICOM Conformance Statement. EasyWeb 3.0. Document Number XZR January Copyright Philips Medical Systems Nederland B.V.

Application Launcher 2.2 DICOM Conformance Statement

Philips Medical Systems DICOM Conformance Statement. EasyWeb 2.0. Document Number April 1999

XPLORE GESTION SCP WORKLIST CONFORMANCE STATEMENT

DICOM 3.0 Conformance Statement. For. DCM v2.93. Revision 1.0 October 23, 2003

DICOM Conformance Statement. Forum

Sep, th Edition 897N101668H

Technical Publications

Technical Publications

DBSWIN DICOM Conformance Statement. DBSWIN DD-DICOM Interface. DICOM Conformance Statement V2.1

Transcription:

DxMM/DxWin DICOM 3.0 Conformance Statement Document Reference (Référence du document) : 99/ Oct30/ABA/MM103/398B

Table of Contents (Table des Matières) 1 Introduction 6 1.1 Scope and Audience 6 1.2 References 6 1.3 Acronyms and abbreviations 6 2 Implementation Model 7 2.1 Application Data Flow Diagram 7 2.2 Functional Definition of Application Entities 8 2.3 Sequencing of Real World Activities 8 3 DxDCMCLIENT Ae specifications 9 3.1 Association Establishment Policies 10 3.1.1 General 10 3.1.2 Number of Associations 10 3.1.3 Asynchronous Nature 10 3.1.4 Implementation Identifying Information 10 3.2 Association Initiation Policy 11 3.2.1 Storage 11 3.2.1.1 Associated Real-World Activity 11 3.2.1.2 Proposed Presentation Contexts 11 3.2.1.3 Specific SOP Class Conformance 11 3.2.2 Query/Retrieve 12 3.2.2.1 Associated Real-World Activity 12 3.2.2.2 Proposed Presentation Contexts 12 2/19

3.2.2.3 Specific SOP Class Conformance 12 3.2.3 Print Management 12 3.2.3.1 Associated Real-World Activity 12 3.2.3.2 Proposed Presentation Contexts 12 3.2.3.3 Specific SOP Class Conformance 12 3.2.4 Verification 13 3.2.4.1 Associated Real-World Activity 13 3.2.4.2 Proposed Presentation Contexts 13 3.2.4.3 Specific SOP Class Conformance 13 3.3 Association Acceptance Policy 14 3.3.1 Storage 14 3.3.1.1 Associated Real-World Activity 14 3.3.1.2 Proposed Presentation Contexts 14 3.3.1.3 Specific SOP Class Conformance 14 4 DxDCMSERVER Ae specifications 15 4.1 Association Establishment Policies 15 4.1.1 General 15 4.1.2 Number of Associations 15 4.1.3 Asynchronous Nature 15 4.1.4 Implementation Identifying Information 16 4.2 Association Initiation Policy 17 4.3 Association Acceptance Policy 17 4.3.1 Storage 17 4.3.1.1 Associated Real-World Activity 17 4.3.1.2 Proposed Presentation Contexts 17 4.3.1.3 Specific SOP Class Conformance 17 4.3.2 Verification 18 4.3.2.1 Associated Real-World Activity 18 4.3.2.2 Proposed Presentation Contexts 18 4.3.2.3 Specific SOP Class Conformance 18 5 Communication profiles 19 5.1 Supported Communications Stacks 19 5.2 TCP/IP Stack 19 5.3 Physical Media Support 19 3/19

6 Extensions / Specializations / Privatizations 19 7 configuration 19 4/19

Document History (Historique du Document) Indice Date Modification Author A 00/10/30 Creation for DxMM/DxWin V4.1 ABA B 00/10/31 Update for DxMM/DxWin V4.2 ABA 5/19

1 INTRODUCTION 1.1 Scope and Audience This document is a DICOM Conformance Statement for DxMM/DxWin. DxMM/DxWin is a DICOM viewer that can retrieve images from a DICOM server and receive images from modalities. This document has been written using the guidelines provided in the DICOM standard [2 part 2]. 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 1.2 References [1] DxMM/DxWin User Guide [2] ACR/NEMA Standards Publications, No PS3, DICOM Standards: Part 1 - Introduction Part 2 - Conformance Part 3 - Information Object Definitions Part 4 - Service Class Specifications Part 5 - Data Structures and Encoding Part 6 - Data Dictionary Part 7 - Message Exchange Part 8 - Network Communication Support Part 9 - Point to Point Communication Support for Message Exchange Part 10 - Media Storage and File Format for Media Interchange Part 11 - Media Storage Application Profiles Part 12 - Storage Functions and Media Formats for Data Interchange Part 13 - Print Management Point-to-Point Communication Support 1.3 Acronyms and abbreviations The following symbols and abbreviations are used in this conformance statement: AE: DICOM: DIMSE: SCP: SCU: SOP: TCP/IP: UID Application Entity Digital Imaging and Communication in Medicine DICOM Message Service Element Service Class Provider Service Class User Service-Object Pair Transmission Control Protocol / Internet Protocol Unique Identifier 6/19

2 IMPLEMENTATION MODEL The application Entity DxDCMclient is the part of the DxMM/DxWin application that is responsible for the DICOM client side information exchanges. The application Entity DxDCMserver is the part of the DxMM/DxWin application that is responsible for the DICOM server side information exchanges. 2.1 Application Data Flow Diagram Find, move, store, echo, print local request DxDCMclient Find, move, store, echo, print remote execution Store, local execution Store, local execution DICOM Standard Interface Figure 1: DxDCMclient Application Data Flow Diagram As depicted in figure 1, a remote real-world activity for image handling (e.g. image storage/retrieval/query or printing), will cause DxDCMclient local application entity to initiate an association, for the purpose of causing equivalent remote real-world activity to occur. Store, echo, local execution DxDCMserver Store, echo, remote request DICOM Standard Interface Figure 2: DxDCMserver Application Data Flow Diagram As depicted in figure 2, a remote real-world activity for image handling (e.g. image storage), by initiating and association, will cause DxDCMserver local application entity to accept this association for the purpose of causing equivalent real-world activity to occur. 7/19

2.2 Functional Definition of Application Entities DxDCMclient application entity acts as a Service Class User (SCU) for the following service classes: Verification Service Class Storage Service Class Query/Retrieve Service Class Print Service Class DxDCMserver application entity acts as a Service Class Provider (SCP) for the following service classes: Verification Service Class Storage Service Class 2.3 Sequencing of Real World Activities Not applicable. 8/19

3 DXDCMCLIENT AE SPECIFICATIONS The DxDCMclient application entity provides Standard Conformance to the following DICOM V3.0 SOP Classes as an SCU: Table 1: Storage SOP Classes SOP Class Name SOP Class UID CR Image Storage 1.2.840.10008.5.1.4.1.1.1 CT Image Storage 1.2.840.10008.5.1.4.1.1.2 US Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3 US Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 MR Image Storage 1.2.840.10008.5.1.4.1.1.4 NM Image Storage 1.2.840.10008.5.1.4.1.1.5 NM Image Storage 1.2.840.10008.5.1.4.1.1.20 US Image Storage 1.2.840.10008.5.1.4.1.1.6 US Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 XA Image Storage 1.2.840.10008.5.1.4.1.1.12.1 RF Image Storage 1.2.840.10008.5.1.4.1.1.12.2 XA Bi-Plane Image Storage 1.2.840.10008.5.1.4.1.1.12.3 Table 2: Query/Retrieve SOP Classes SOP Class Name SOP Class UID Patient Root Query/Retrieve Information Model 1.2.840.10008.5.1.4.1.2.1.1 FIND Patient Root Query/Retrieve Information Model 1.2.840.10008.5.1.4.1.2.1.2 MOVE Patient Root Query/Retrieve Information Model 1.2.840.10008.5.1.4.1.2.1.3 GET Study Root Query/Retrieve Information Model 1.2.840.10008.5.1.4.1.2.2.1 FIND Study Root Query/Retrieve Information Model 1.2.840.10008.5.1.4.1.2.2.2 MOVE Study Root Query/Retrieve Information Model 1.2.840.10008.5.1.4.1.2.2.3 GET Table 3: Print Management (Meta) SOP Classes (Meta) SOP Class Name SOP Class UID Basic Grayscale Print Management Meta SOP 1.2.840.10008.5.1.1.9 Class Basic Color Print Management Meta SOP Class 1.2.840.10008.5.1.1.18 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 Basic Color Image Box SOP Class 1.2.840.10008.5.1.1.4.1 Print Job SOP Class 1.2.840.10008.5.1.1.14 Printer SOP Class 1.2.840.10008.5.1.1.16 Hardcopy Grayscale Image Storage SOP Class 1.2.840.10008.5.1.1.29 Hardcopy Color Image Storage SOP Class 1.2.840.10008.5.1.1.30 Printer Configuration Retrieval SOP Class 1.2.840.10008.5.1.1.16.376 9/19

Table 4: Verification SOP Class SOP Class Name SOP Class UID Verification SOP Class 1.2.840.10008.1.1 Table 5: Media Storage Directory Storage SOP Class SOP Class Name SOP Class UID Media Storage Directory Storage 1.2.840.10008.1.3.10 3.1 Association Establishment Policies 3.1.1 General DxDCMclient application entity initiates associations for the following purposes: Invokes the C-ECHO service to allow end-to-end verifications. Invokes the C-STORE service to store images into a remote database. Invokes the C-FIND service to query a remote database. Invokes the C-MOVE service to retrieve and forward images from a remote database. Invokes the Basic Grayscale or Color Print Management service to print images to a remote printer. The maximum length PDU negotiation shall be included in all association establishments. The SCU/SCP Role Negotiation is not supported. Refer to the following paragraph for extensions, specializations, and privatizations management. 3.1.2 Number of Associations Not applicable 3.1.3 Asynchronous Nature Not applicable 3.1.4 Implementation Identifying Information By default, DxDCMclient will be identified by: Implementation Class UID: 1.2.250.1.38.1.3.1.1.1 Implementation Version Name: DxDCMclient4.1 10/19

3.2 Association Initiation Policy DxDCMclient AE initiates associations for the purpose of communication verification or image transfers to a remote database, or image retrieval from a remote database, or image forwarding (migration) from a remote database to a third application acting as a DICOM server, as operations of remote real-world activities. It also initiates associations for the purpose of image printing to a remote printer. 3.2.1 Storage 3.2.1.1 Associated Real-World Activity DxDCMclient AE initiates associations to remote systems in order to transfer to those systems images using the C-STORE DIMSE-C service. 3.2.1.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Name UID Name list UID list Role DICOM Implicit VR Little Endian 1.2.840.10008.1.2 Little Endian 1.2.840.10008.1.2.1 Big Endian 1.2.840.10008.1.2.2 See See Little Endian, JPEG Note Note baseline encoded 1.2.840.10008.1.2.4.50 SCU Little Endian, JPEG 1.2.840.10008.1.2.4.70 lossless encoded Little Endian, RLE 1.2.840.10008.1.2.5 lossless Table 6: DxDCMclient Storage Presentation Context Extended Negotiation None Note: Abstract syntaxes of Storage SOP Classes listed into Table 1. 3.2.1.3 Specific SOP Class Conformance The following DIMSE Service is supported: C-STORE 11/19

3.2.2 Query/Retrieve 3.2.2.1 Associated Real-World Activity DxDCMclient application entity initiates associations to remote systems in order to query from those systems image information using the C-FIND DIMSE-C service, and retrieve the images using the C-MOVE or C-GET DIMSE-C service. 3.2.2.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Extended Name UID Name list UID list Role Negotiation See See DICOM Implicit VR 1.2.840.10008.1.2 SCU None Note Note Little Endian Table 7: DxDCMclient Query/Retrieve Presentation Context Note: Abstract syntaxes listed into table 2 are supported. 3.2.2.3 Specific SOP Class Conformance The following DIMSE Services are supported: C-FIND C-MOVE C-GET 3.2.3 Print Management 3.2.3.1 Associated Real-World Activity DxDCMclient application entity initiates associations to remote printers in order to print images on those printers. 3.2.3.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Extended Name UID Name list UID list Role Negotiation See See DICOM Implicit VR 1.2.840.10008.1.2 SCU None Note Note Little Endian Table 8 : DxDCMclient Print Management Presentation Context Note: Abstract syntaxes listed into table 3 are supported. 3.2.3.3 Specific SOP Class Conformance The following DIMSE Services are supported: N-ACTION N-CREATE N-DELETE N-GET N-SET 12/19

3.2.4 Verification 3.2.4.1 Associated Real-World Activity DxDCMclient application entity initiates associations to remote systems in order to get information about their possibilities. 3.2.4.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Name UID Name list UID list Role See See DICOM Implicit VR Note Note Little Endian Note: Abstract syntax listed in table 4 is supported. 3.2.4.3 Specific SOP Class Conformance The following DIMSE Service is supported: C-ECHO Extended Negotiation 1.2.840.10008.1.2 SCU None 13/19

3.3 Association Acceptance Policy DxDCMclient AE accepts associations for the purpose of image transfers from the remote systems, as sub-operations of a remote real-world activity of image retrieval. 3.3.1 Storage 3.3.1.1 Associated Real-World Activity DxDCMclient AE accepts associations from remote systems in order to retrieve from those systems images using the C-STORE DIMSE-C service. 3.3.1.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Name UID Name list UID list Role DICOM Implicit VR Little Endian 1.2.840.10008.1.2 Little Endian 1.2.840.10008.1.2.1 Big Endian 1.2.840.10008.1.2.2 See See Little Endian, JPEG Note Note baseline encoded 1.2.840.10008.1.2.4.50 SCP Little Endian, JPEG 1.2.840.10008.1.2.4.70 lossless encoded Little Endian, RLE 1.2.840.10008.1.2.5 lossless Table 9: DxDCMclient Storage Presentation Context Extended Negotiation None Note: Abstract syntaxes of Storage SOP Classes listed into Table 1. 3.3.1.3 Specific SOP Class Conformance The following DIMSE Service is supported: C-STORE 14/19

4 DXDCMSERVER AE SPECIFICATIONS The DxDCMserver application entity provides Standard Conformance to the following DICOM V3.0 SOP Classes as an SCP: Table 10: Storage SOP Classes SOP Class Name SOP Class UID CR Image Storage 1.2.840.10008.5.1.4.1.1.1 CT Image Storage 1.2.840.10008.5.1.4.1.1.2 US Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3 US Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 MR Image Storage 1.2.840.10008.5.1.4.1.1.4 NM Image Storage 1.2.840.10008.5.1.4.1.1.5 NM Image Storage 1.2.840.10008.5.1.4.1.1.20 US Image Storage 1.2.840.10008.5.1.4.1.1.6 US Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 XA Image Storage 1.2.840.10008.5.1.4.1.1.12.1 RF Image Storage 1.2.840.10008.5.1.4.1.1.12.2 XA Bi-Plane Image Storage 1.2.840.10008.5.1.4.1.1.12.3 Table 11: Verification SOP Class SOP Class Name SOP Class UID Verification SOP Class 1.2.840.10008.1.1 4.1 Association Establishment Policies 4.1.1 General DxDCMserver AE accepts associations for the following purposes: Supports the C-ECHO service to allow end-to-end verifications. Invokes the C-STORE service to store images into a remote database. The maximum length PDU negotiation shall be included in all association establishments. The SCU/SCP Role Negotiation is not supported. Refer to the following paragraph for extensions, specializations, and privatizations management. 4.1.2 Number of Associations The number of simultaneous DICOM associations that is accepted is theoretically unlimited, but is actually limited by the OS parameters of the TCP/IP implementation. A new process is created for each new association. 4.1.3 Asynchronous Nature Not supported. 15/19

4.1.4 Implementation Identifying Information By default, DxDCMserver will be identified by: Implementation Class UID: 1.2.250.1.38.1.3.1.1.1 Implementation Version Name: DxDCMclient4.1 Note: uses the same configuration file than DxDCMclient. 16/19

4.2 Association Initiation Policy DxDCMserver AE does not initiate associations. 4.3 Association Acceptance Policy DxDCMserver AE accepts associations for the purpose of communication verification or image storage. 4.3.1 Storage 4.3.1.1 Associated Real-World Activity DxDCMserver AE accepts associations from remote systems that want to store images into the local DICOMDIR using the C-STORE DIMSE-C service. 4.3.1.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Name UID Name list UID list Role DICOM Implicit VR Little Endian 1.2.840.10008.1.2 Little Endian 1.2.840.10008.1.2.1 Big Endian 1.2.840.10008.1.2.2 See See Little Endian, JPEG Note Note baseline encoded 1.2.840.10008.1.2.4.50 SCP Little Endian, JPEG 1.2.840.10008.1.2.4.70 lossless encoded Little Endian, RLE 1.2.840.10008.1.2.5 lossless Table 12: DxDCMserver Storage Presentation Context Extended Negotiation None Note: Abstract syntaxes of Storage SOP Classes listed into Table 10. 4.3.1.3 Specific SOP Class Conformance The following DIMSE Service is supported: C-STORE 17/19

4.3.2 Verification 4.3.2.1 Associated Real-World Activity DxDCMserver application entity accepts associations from remote systems that want to verify application level communication using the C-ECHO DIMSE-C service. 4.3.2.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Name UID Name list UID list Role See See DICOM Implicit VR Note Note Little Endian Note: Abstract syntax listed in table 11 is supported. 4.3.2.3 Specific SOP Class Conformance The following DIMSE Service is supported: C-ECHO Extended Negotiation 1.2.840.10008.1.2 SCP None 18/19

5 COMMUNICATION PROFILES 5.1 Supported Communications Stacks Both DxDCMclient and DxDCMserver provide DICOM V3.0 TCP/IP Network Communication Support as defined in PS 3.8. 5.2 TCP/IP Stack DxDCMclient and DxDCMserver inherit their TCP/IP stack from the MS Windows system upon which they execute. 5.3 Physical Media Support DxDCMclient and DxDCMserver are indifferent to the physical medium over which TCP/IP executes; they inherit this from the MS Windows system upon which they execute. 6 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS Not applicable. 7 CONFIGURATION See [1] for full details. 19/19