Technical Publications - PDF Free Download

GE Medical Systems

THIS PAGE LEFT INTENTIONALLY BLANK

REVISION HISTORY Revision Date Description 1 2011/02/07 Release for Voluson S6/S8 M3

CONFORMANCE STATEMENT OVERVIEW The VOLUSON S6/S8 is a self-contained networked computer system used for acquiring ultrasound diagnostic medical images. The system implements the necessary DICOM services to download work list from an information system, save acquired US images to a network storage device or media, print to a networked hardcopy device, query and move US images from a networked storage and inform the information system about the work actually done. The system conforms to the DICOM standard to allow the sharing of medical information with other digital imaging systems. Table A.1 provides an overview of the network services supported by Voluson S6/S8. SOP Classes Table A.1 Network Services User of Service (SCU) Provider of Service (SCP) Transfer Verification Yes Yes US Image Storage Yes Yes US Multi-frame Storage Yes Yes Enhanced US Volume Storage Yes Yes Secondary Capture Image Storage Yes Yes Query/Retrieve Study Root Q/R FIND Yes No Study Root Q/R MOVE Yes No Print Management Basic Grayscale Print Management Yes No Basic Color Print Management Yes No Workflow Management Modality Worklist Yes No Modality Performed Procedure Yes No Storage Commitment Push Model Yes No Notes, Reports, Measurements Transfer Comprehensive SR Storage Yes No Table A.2 provides an overview of the Media Storage Application Profile supported by VOLUSON S6/S8. Table A.2 Media Services Media Storage Augmented Profile Compact Disk - R AUG-US-SC-SF-CDR, AUG-US-SC-MF-CDR DVD AUG-US-SC-SF-DVD, AUG-US-SC-MF-DVD Write Files (FSC or FSU) Yes Yes Read Files (FSR) No No

TABLE OF CONTENTS 1. INTRODUCTION... 1 1.1 OVERVIEW... 1 1.2 OVERALL DOCUMENT STRUCTURE... 2 1.3 INTENDED AUDIENCE... 3 1.4 SCOPE AND FIELD OF APPLICATION... 3 1.5 IMPORTANT REMARKS... 3 1.6 REFERENCES... 4 1.7 DEFINITIONS... 4 1.8 SYMBOLS AND ABBREVIATIONS... 6 2. NETWORK CONFORMANCE STATEMENT... 8 2.1 INTRODUCTION... 8 2.2 IMPLEMENTATION MODEL... 8 2.2.1 Application Data Flow Diagram... 8 2.2.2 Functional Definition of AE's... 10 2.2.3 Sequencing of Real-World Activities... 10 2.3 AE SPECIFICATIONS... 11 2.3.1 VOLUSON S6/S8 AE Specification... 11 2.4 COMMUNICATION PROFILES... 20 2.4.1 Supported Communication Stacks (PS 3.8)... 20 2.4.2 TCP/IP Stack... 20 2.5 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS... 20 2.6 CONFIGURATION... 20 2.6.1 AE Title/Presentation Address Mapping... 20 i

2.6.2 Configurable Parameters... 20 2.7 SUPPORT OF EXTENDED CHARACTER SETS... 21 2.8 CODES AND CONTROLLED TERMINOLOGY... 21 2.9 SECURITY PROFILES... 21 3. MEDIA STORAGE CONFORMANCE STATEMENT... 22 3.1 INTRODUCTION... 22 3.2 IMPLEMENTATION MODEL... 22 3.2.1 Application Data Flow Diagram... 22 3.2.2 Functional Definition of AE s... 22 3.2.3 Sequencing Requirements... 22 3.3 File Meta Information Options (See PS3.10)... 22 3.4 AE SPECIFICATIONS... 23 3.4.1 VOLUSON S6/S8 AE Specification... 23 4. ULTRASOUND (US) INFORMATION OBJECT IMPLEMENTATION... 24 4.1 INTRODUCTION... 24 4.2 US IOD IMPLEMENTATION... 24 4.3 US ENTITY-RELATIONSHIP MODEL... 24 4.3.1 Entity Descriptions... 24 4.3.2 VOLUSON S6/S8 Mapping of DICOM Entities... 24 4.4 IOD MODULE TABLE... 24 4.5 INFORMATION MODULE DEFINITIONS... 25 4.5.1 Common Patient Entity Modules... 25 4.5.2 Common Study Entity Modules... 26 4.5.3 Common Series Entity Modules... 26 4.5.4 Common Equipment Entity Modules... 27 ii

4.5.5 Common Image Entity Modules... 27 4.5.6 General Modules... 29 4.5.7 US Modules... 29 5. ULTRASOUND MULTIFRAME (US MF) INFORMATION OBJECT IMPLEMENTATION32 5.1 INTRODUCTION... 32 5.2 US MF IOD IMPLEMENTATION... 32 5.3 US MF ENTITY-RELATIONSHIP MODEL... 32 5.3.1 Entity Descriptions... 32 5.3.2 VOLUSON S6/S8 Mapping of DICOM entities... 32 5.4 IOD MODULE TABLE... 32 5.5 INFORMATION MODULE DEFINITIONS... 33 5.5.1 Common Image Modules... 33 6. ENHANCED ULTRASOUND (US) VOLUME INFORMATION OBJECT IMPLEMENTATION... 35 6.1 INTRODUCTION... 35 6.2 Enhanced US Volume IOD IMPLEMENTATION... 35 6.3 Enhanced US Volume ENTITY-RELATIONSHIP MODEL... 35 6.3.1 Entity Descriptions... 35 6.3.2 VOLUSON S6/S8 Mapping of DICOM entities... 35 6.4 IOD MODULE TABLE... 35 6.5 INFORMATION MODULE DEFINITIONS... 36 6.5.1 Patient Entity Module... 36 6.5.2 Study Entity Modules... 36 6.5.3 Series Entity Modules... 36 6.5.4 Frame of Reference Modules... 37 iii

6.5.5 Equipment Entity Modules... 37 6.5.6 Image Entity Modules... 38 7. SC INFORMATION OBJECT IMPLEMENTATION... 43 7.1 INTRODUCTION... 43 7.2 SC IOD IMPLEMENTATION... 43 7.3 SC ENTITY-RELATIONSHIP MODEL... 43 7.3.1 Entity Descriptions... 43 7.3.2 VOLUSON S6/S8 Mapping of DICOM Entities... 43 7.4 IOD MODULE TABLE... 43 7.5 INFORMATION MODULE DEFINITIONS... 44 7.5.1 SC Modules... 44 8. SR INFORMATION OBJECT IMPLEMENTATION... 45 8.1 INTRODUCTION... 45 8.2 COMPREHENSIVE SR IOD IMPLEMENTATION... 45 8.3 COMPREHENSIVE SR ENTITY-RELATIONSHIP MODEL... 45 8.3.1 Entity Descriptions... 45 8.3.2 VOLUSON S6/S8 Mapping of DICOM Entities... 45 8.4 IOD MODULE TABLE... 46 8.5 INFORMATION MODULE DEFINITIONS... 46 8.5.1 SR Document Series Module... 46 8.5.2 SR Document General Module... 47 8.5.3 SR Document Content Module... 48 8.6 STANDARD EXTENDED AND PRIVATE CONTEXT GROUPS... 48 8.7 STANDARD EXTENDED AND PRIVATE TEMPLATES... 48 9. MODALITY WORKLIST INFORMATION MODEL DEFINITION... 49 iv

9.1 INTRODUCTION... 49 9.2 MODALITY WORKLIST INFORMATION MODEL DESCRIPTION... 49 9.3 MODALITY WORKLIST INFORMATION MODEL ENTITY-RELATIONSHIP MODEL... 49 9.3.1 Entity Descriptions... 49 9.3.2 VOLUSON S6/S8 Mapping of DICOM entities... 49 9.4 INFORMATION MODEL MODULE TABLE... 50 9.5 INFORMATION MODEL KEYS... 51 9.5.1 Supported Matching... 51 9.5.2 Scheduled Procedure Step Entity... 51 9.5.3 Requested Procedure Entity... 52 9.5.4 Imaging Service Request Entity... 53 9.5.5 Visit Entity... 53 9.5.6 Patient Entity... 54 10. MODALITY PERFORMED PROCEDURE STEP SOP CLASS DEFINITION... 56 10.1 INTRODUCTION... 56 10.2 MODALITY PERFORMED PROCEDURE STEP SOP CLASS DEFINITION... 56 10.2.1 IOD Description... 56 10.2.2 Operations... 57 11. STORAGE COMMITMENT PUSH MODEL SOP CLASS DEFINITION... 59 11.1 INTRODUCTION... 59 11.2 STORAGE COMMITMENT PUSH MODEL SOP CLASS DEFINITION... 59 11.2.1 IOD Description... 59 11.2.2 DIMSE Service Group... 59 11.2.3 Operations... 60 11.2.4 Notifications... 60 v

12. PRINT MANAGEMENT SOP CLASS DEFINITION... 62 12.1 INTRODUCTION... 62 12.2 BASIC PRINT MANAGEMENT META SOP CLASSES... 62 12.2.1 Basic Grayscale Print Management Meta SOP Class... 62 12.2.2 Basic Color Print Management Meta SOP Class... 62 12.3 PRINT MANAGEMENT SOP CLASS DEFINITIONS... 62 12.3.1 Basic Film Session SOP Class... 62 12.3.2 Basic Film Box SOP Class... 63 12.3.3 Image Box SOP Class... 63 12.3.4 Printer SOP Class... 64 12.4 PRINT MANAGEMENT IODS... 64 12.4.1 Film Session IOD Module... 65 12.4.2 Basic Film Box IOD Module Table... 65 12.4.3 Basic Image Box IOD Module Table... 65 12.4.4 Printer IOD Module Table... 65 12.5 INFORMATION MODULE DEFINITIONS... 65 12.5.1 General Modules... 65 13. STUDY ROOT QUERY/RETRIEVE INFORMATION MODEL DEFINITION... 69 13.1 INTRODUCTION... 69 13.2 STUDY ROOT INFORMATION MODEL DESCRIPTION... 69 13.3 STUDY ROOT INFORMATION MODEL ENTITY-RELATIONSHIP MODEL... 69 13.3.1 Entity Descriptions... 69 13.3.2 VOLUSON S6/S8 Mapping of DICOM entities... 69 13.4 INFORMATION MODEL KEYS... 69 13.4.1 Study Level... 69 vi

13.4.2 Series Level... 70 A. STANDARD EXTENDED AND PRIVATE CONTEXT GROUPS... 72 B. STANDARD EXTENDED AND PRIVATE CONTEXT GROUPS... 95 vii

1. INTRODUCTION 1.1 OVERVIEW This DICOM Conformance Statement is divided into Sections as described below: Section 1 (Introduction), which describes the overall structure, intent, and references for this Conformance Statement. Section 2 (Network Conformance Statement), which specifies the GEMS equipment compliance to the DICOM requirements for the implementation of Networking features. Section 3 (Media Storage Conformance Statement), which specifies the GEMS equipment compliance to the DICOM requirements for the implementation of Media Storage features. Section 4 (Ultrasound Information Object Implementation), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of an Ultrasound Medicine Information Object. Section 5 (Ultrasound Multi-Frame Information Object Implementation), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of an Ultrasound Multi-Frame Information. Section 6 (SC Object Implementation), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of a Secondary Capture Information Object. Section 7 (SR Object Implementation), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of a Comprehensive Structured Reporting Information Object. Section 8 (Basic Directory Information Object Implementation), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of a Basic Directory Information Object. Section 9 (Modality Worklist Information Model), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of the Modality Worklist service. Section 10 (Modality Performed Procedure Step SOP Class Definition), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of Modality Performed Procedure Step Service. Section 11 (Storage Commitment Push Model SOP Class Definition), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of the Storage Commitment Push Model Service. Section 12 (Basic Print Meta SOP Class Information Object Implementation), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of Basic Print Meta SOP Classes (Gray and Color). Section 13 (Study Root Query/Retrieve Information Model), which specifies the GEMS equipment compliance to DICOM requirements for the Study Root Query/Retrieve Information Model. 1

1.2 OVERALL DOCUMENT STRUCTURE The Documentation Structure of the GEHC Conformance Statements and their relationship with the DICOM Conformance Statements is shown in the Illustration below. GEHC DICOM Conformance Statements @ http://www.ge.com/dicom APPLICATION ENTITY SPECIFICATION (SERVICE CLASSES, INFORMATION OBJECTS, MESSAGE EXCHANGES, ETC.) Product Implementation: CT Ad vantage Co MR Advantage S emen Co Voluson S6/S8 S Conformance Statement Direction: DOC0913087... Conformance Statement Direction:... DICOM STANDARD Standard Specification: DI CO M Part 1 M 2 M 3 M 4 DICOM Part 16 2

This document specifies the DICOM implementation. It is entitled: VOLUSON S6/S8 version 11.x.x Conformance Statement for DICOM DOC0913087 This DICOM Conformance Statement documents the DICOM Conformance Statement and Technical Specification required to inter-operate with the VOLUSON S6/S8 network interface. The VOLUSON S6/S8 Conformance Statement, contained in this document, also specifies the Lower Layer communications, which it supports (e.g. TCP/IP). However, the Technical Specifications are defined in the DICOM Part 8 standard. For more information regarding DICOM, copies of the Standard may be obtained on the Internet at http://medical.nema.org. Comments on the Standard may be addressed to: DICOM Secretariat NEMA 1300 N. 17 th Street, Suite 1752 Rosslyn, VA 22209 USA Phone: +1.703.841.3200 1.3 INTENDED AUDIENCE 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, which are used in this standard. 1.4 SCOPE AND FIELD OF APPLICATION It is the intent of this document, to provide an unambiguous specification for GE Healthcare implementations. This specification, called a Conformance Statement, includes a DICOM Conformance Statement and is necessary to ensure proper processing and interpretation of GE Healthcare medical data exchanged using DICOM. The VOLUSON S6/S8 Conformance Statements are available to the public. Included in this DICOM Conformance Statement are the Module Definitions, which define all data elements, used by the VOLUSON S6/S8 implementation. If the user encounters unspecified private data elements while parsing a VOLUSON S6/S8 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 the VOLUSON S6/S8. 1.5 IMPORTANT REMARKS The use of these DICOM Conformance Statements, in conjunction with the DICOM Standards, is intended to facilitate communication with the VOLUSON S6/S8 equipment. However, by itself, it is not sufficient to ensure that interoperation 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 v3.0), and of this introduction and associated DICOM Conformance Statements when interoperability with non-ge equipment is desired. The responsibility to analyze the applications 3

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 Standard. DICOM will incorporate new features and technologies and GE may follow the evolution of the Standard. The GEHC 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) 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 Standard. Failures to do so will likely result in the loss of function and/or connectivity as the DICOM Standard changes 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.6 REFERENCES NEMA PS3 Digital Imaging and Communications in Medicine (DICOM) Standard, available free at http://medical.nema.org/ 1.7 DEFINITIONS Informal definitions are provided for the following terms used in this Conformance Statement. The DICOM Standard is the authoritative source for formal definitons of these terms. Abstract Syntax the information agreed to be exchanged between applications, generally equivalent to a Service/Object Pair (SOP) Class. Examples: Verification SOP Class, Modality Worklist Information Model Find SOP Class, Computed Radiography Image Storage SOP Class. Application Entity (AE) an end point of a DICOM information exchange, including the DICOM network or media interface software; i.e., the software that sends or receives DICOM information objects or messages. A single device may have multiple Application Entities. Application Entity Title the externally known name of an Application Entity, used to identify a DICOM application to other DICOM applications on the network. Application Context the specification of the type of communication used between Application Entities. Example: DICOM network protocol. Association a network communication channel set up between Application Entities. 4

Attribute a unit of information in an object definition; a data element identified by a tag. The information may be a complex data structure (Sequence), itself composed of lower level data elements. Examples: Patient ID (0010,0020), Accession Number (0008,0050), Photometric Interpretation (0028,0004), Procedure Code Sequence (0008,1032). Information Object Definition (IOD) the specified set of Attributes that comprise a type of data object; does not represent a specific instance of the data object, but rather a class of similar data objects that have the same properties. The Attributes may be specified as Mandatory (Type 1), Required but possibly unknown (Type 2), or Optional (Type 3), and there may be conditions associated with the use of an Attribute (Types 1C and 2C). Examples: MR Image IOD, CT Image IOD, Print Job IOD. Joint Photographic Experts Group (JPEG) a set of standardized image compression techniques, available for use by DICOM applications. Media Application Profile the specification of DICOM information objects and encoding exchanged on removable media (e.g., CDs) Module a set of Attributes within an Information Object Definition that are logically related to each other. Example: Patient Module includes Patient Name, Patient ID, Patient Birth Date, and Patient Sex. Negotiation first phase of Association establishment that allows Application Entities to agree on the types of data to be exchanged and how that data will be encoded. Presentation Context the set of DICOM network services used over an Association, as negotiated between Application Entities; includes Abstract Syntaxes and Transfer Syntaxes. Protocol Data Unit (PDU) a packet (piece) of a DICOM message sent across the network. maximum size packet they can receive for DICOM messages. Devices must specify the Security Profile a set of mechanisms, such as encryption, user authentication, or digital signatures, used by an Application Entity to ensure confidentiality, integrity, and/or availability of exchanged DICOM data Service Class Provider (SCP) role of an Application Entity that provides a DICOM network service; typically, a server that performs operations requested by another Application Entity (Service Class User). Examples: Picture Archiving and Communication System (image storage SCP, and image query/retrieve SCP), Radiology Information System (modality worklist SCP). Service Class User (SCU) role of an Application Entity that uses a DICOM network service; typically, a client. Examples: imaging modality (image storage SCU, and modality worklist SCU), imaging workstation (image query/retrieve SCU) Service/Object Pair (SOP) Class the specification of the network or media transfer (service) of a particular type of data (object); the fundamental unit of DICOM interoperability specification. Examples: Ultrasound Image Storage Service, Basic Grayscale Print Management. Service/Object Pair (SOP) Instance an information object; a specific occurrence of information exchanged in a SOP Class. Examples: a specific x-ray image. Tag a 32-bit identifier for a data element, represented as a pair of four digit hexadecimal numbers, the group and the element. If the group number is odd, the tag is for a private (manufacturer-specific) data element. Examples: (0010,0020) [Patient ID], (07FE,0010) [Pixel Data], (0019,0210) [private data element] Transfer Syntax the encoding used for exchange of DICOM information objects and messages. Examples: JPEG compressed (images), little endian explicit value representation. Unique Identifier (UID) a globally unique dotted decimal string that identifies a specific object or a class of objects; an ISO-8824 Object Identifier. Examples: Study Instance UID, SOP Class UID, SOP Instance UID. 5

Value Representation (VR) the format type of an individual DICOM data element, such as text, an integer, a person s name, or a code. DICOM information objects can be transmitted with either explicit identification of the type of each data element (Explicit VR), or without explicit identification (Implicit VR); with Implicit VR, the receiving application must use a DICOM data dictionary to look up the format of each data element. 1.8 SYMBOLS AND ABBREVIATIONS A list of symbols and abbreviations, which is applicable to all GEMS Conformance Statements, is included in the Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0) Conformance Statement, Direction: 2118780. Additional abbreviations and terms used in this Conformance Statement document are listed below: TERM AE CD-R DVD CT DICOM FSC IOD ISO JPEG LUT MPPS MR O PDU R SC SCP SCU SOP SR TCP/IP U US DESCRIPTION Application Entity Compact Disk Recordable Digital Video Disc Computed Tomography Digital Imaging and Communications in Medicine File-Set Creator Information Object Definition International Organization for Standards Joint Photographic Experts Group Look-up Table Modality Performed Procedure Step Magnetic Resonance Imaging Optional (Key Attribute) Protocol Data Unit Required (Key Attribute) Secondary Capture Service Class Provider Service Class User Service-Object Pair Structured Reporting Transmission Control Protocol/Internet Protocol Unique (Key Attribute) Ultrasound 6

VR Value Representation 7

2. NETWORK CONFORMANCE STATEMENT 2.1 INTRODUCTION This section of the DICOM Conformance Statement specifies the compliance to DICOM conformance requirements for the relevant Networking features for VOLUSON S6/S8 version R11.x.x. Note that the format of this section strictly follows the format defined in DICOM Standard PS 3.2 (Conformance). Please refer to that part of the standard while reading this section. VOLUSON S6/S8 is an Ultrasound scanner running on a commercial computer. It allows for the following DICOM functionality: Sending and receiving Echo messages to and from DICOM Verification SCP and client. Exporting DICOM images and results to a DICOM SCP. Querying and retrieving DICOM Modality Worklist from a Worklist SCP. Sending start and end of examination to a DICOM Modality Performed Procedure Step SCP. Sending storage commitment requests to and receiving replies from a DICOM Storage Commitment SCP. Printing images to a DICOM Printer. Querying and retrieving for examinations from a DICOM Query/Retrieve SCP. 2.2 IMPLEMENTATION MODEL 2.2.1 Application Data Flow Diagram The Basic and Specific Application models for this device are shown in Figure 1: 8

DICOM Standard Interface The arrows indicate the direction of association initiation Image Send Storage SCP Verification SCU/SCP Verify VOLUSON S6/S8 Modality Worklist SCP Query Worklist Modality PPS SCP Start/End Exam Storage Commit SCP Image Print Print SCP Query/ Retrieve Images Query/ Retrieve SCP Receive Image Storage SCU Figure 1: Application Data Flow Diagram 9

There are seven local real-world activities that occur in VOLUSON S6/S8- Image Send, Verify, Query Worklist, Start/End Exam, Print Image, Query/Retrieve and Receive Image. Image Send spools images or SR documents into a send queue. The queue manager then initiates a connection with the DICOM SCP and transmits the images and SR documents to the DICOM SCP. If Storage Commitment is configured, a commitment request will be sent for the images, SR documents and results. Verify initiates a connection with the DICOM SCP, posts a Verification request and closes the connection. It also responds to incoming Verification requests. Query Worklist initiates a connection with the DICOM SCP, performs a query and retrieves the matching entries to the product. Start/End exam: If Modality Performed Procedure Step is configured N-CREATE and N-SET messages will be sent for the exam. Print Image will send images to a DICOM Print SCP. It uses the same spooling mechanism as Image Send. Query/Retrieve will send queries to a DICOM Query/Retrieve SCP and retrieve examinations/images. Receive Image: The modality will accept requests for DICOM image storage and store the received images into a local database. 2.2.2 Functional Definition of AE's Application Entity VOLUSON S6/S8 supports the following functions: Initiates a DICOM association to send images and SR documents. Transmits DICOM images and SR documents to the DICOM Storage SCP. Initiates a DICOM verification to assist in network diagnostics. Responds to DICOM verification requests from other devices. Initiates a DICOM worklist query to receive worklist information. Initiates a DICOM association to notify start of examination. Initiates a DICOM association to notify end of examination. Initiates a DICOM association to request storage commitment of images and SR documents. Responds to replies from DICOM Storage SCPs, for storage commitment requests of images and SR documents sent by VOLUSON S6/S8. Initiates a DICOM association to print images. Initiates a DICOM association to query for and retrieve images. Responds to Image Storage requests from Storage SCU (as part of examination retrieve) 2.2.3 Sequencing of Real-World Activities Not applicable. 10

2.3 AE SPECIFICATIONS 2.3.1 VOLUSON S6/S8 AE Specification This Application Entity provides Standard Conformance to the following DICOM SOP Classes as an SCU: SOP Class Name Table 2.3-1: SCU SOP Classes SOP Class UID Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Enhanced Ultrasound Volume Storage 1.2.840.10008.5.1.4.1.1.6.2 Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Verification SOP Class 1.2.840.10008.1.1 Modality Worklist Information Model FIND 1.2.840.10008.5.1.4.31 Modality Performed Procedure Step SOP Class 1.2.840.10008.3.1.2.3.3 Storage Commitment Push Model SOP Class 1.2.840.10008.1.20.1 Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9 Basic Color Print Management Meta SOP Class 1.2.840.10008.5.1.1.18 Study Root Query/Retrieve Information Model FIND 1.2.840.10008.5.1.4.1.2.2.1 Study Root Query/Retrieve Information Model MOVE 1.2.840.10008.5.1.4.1.2.2.2 Comprehensive Structured Report Storage 1.2.840.10008.5.1.4.1.1.88.33 This Application Entity provides Standard Conformance to the following DICOM SOP Classes as an SCP: SOP Class Name Table 2.3-2: SCP SOP Classes SOP Class UID Verification SOP Class 1.2.840.10008.1.1 Ultrasound Multi-Frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Enhanced Ultrasound Volume Storage 1.2.840.10008.5.1.4.1.1.6.2 Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 2.3.1.1 Association Establishment Policies 2.3.1.1.1 General The DICOM Application Context Name (ACN), which is always proposed, is: Table 2.3-3: Application Context Name Application Context Name 1.2.840.10008.3.1.1.1 The Maximum Length PDU negotiation is included in all association establishment requests. The maximum length PDU for an association initiated by the equipment is: 11

Table 2.3-4: PDU Size Maximum Length PDU The maximum length PDU is a fixed number - not configurable. 28872 bytes The SOP Class Extended Negotiation is not supported. The user information Items sent by this product are: Maximum PDU Length Implementation UID Implementation Name 2.3.1.1.2 Number of Associations and Error Processing The VOLUSON S6/S8 AE will initiate multiple DICOM associations. The maximum numbers of associations are based on the connectivity service configuration. The default connection time out value is 45 second. User can configurable this value from 30 to 120 second. There is no response during the time out value, the request service is treated failure and forced to terminate and cancel. This Error processing provide common through the user configuration interface and effect to all requested service. Also, any unknown status values received in response to any request will be treated as failed. 2.3.1.1.3 Asynchronous Nature Asynchronous mode is not supported. All operations will be performed synchronously. 2.3.1.1.4 Implementation Identifying Information The Implementation UID for this DICOM Implementation is: VOLUSON S6/S8 Implementation UID 1.2.276.0.26.20010718.240 The Implementation Name for this DICOM Implementation is: VOLUSON S6/S8 Implementation Name KRETZDICOM_240 Note: The Implementation Name may change in the future without modification of this document. 2.3.1.2 Association Initiation Policy The VOLUSON S6/S8 AE attempts to establish a new association with a remote device due to six Real-World Activities: Image Send initiated by the operator for images and SR documents and sending requests for Storage Commitment. Verification, which verifies application level communication between peer DICOM AE's for service purposes. Worklist initiated by the operator for receiving worklist information. 12

Start/End Exam sending messages to Modality Performed Procedure Step. Print initiated by the operator for a specific image or group of images. Query/Retrieve initiated by the operator for querying and receiving images. 2.3.1.2.1 Real-World Activity A ( Image Send Operation) 2.3.1.2.1.1 Associated Real-World Activity Upon a request by the operator (manual or automatic), images or SR documents will be sent a DICOM Storage SCP. 2.3.1.2.1.2 Proposed Presentation Context Tables The Proposed Presentation Context Table depends on compression according to the following tables: Secondary Capture Image Storage Table 2.3-5: Presentation Context Table Presentation Context Table - Proposed Abstract Syntax Transfer Syntax Name Role Ext Name UID Name List UID List Neg. 1.2.840.10008.5.1.4.1.1.7 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian Enhanced US Volume Storage 1.2.840.10008.5.1.4.1.1.6.2 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian Ultrasound Multi-frame Image Storage Ultrasound Image Storage (retired) Ultrasound Multi-frame Image Storage (retired) 1.2.840.10008.5.1.4.1.1.3.1 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.5.1.4.1.1.6 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.5.1.4.1.1.3 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian Presentation Context Table for Compression set to JPEG Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 JPEG Baseline(Lossy) JPEG Lossless Non Hierarchical (Process14) Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 JPEG Baseline(Lossy) JPEG Lossless Non Hierarchical (Process14) Enhanced US Volume Storage 1.2.840.10008.5.1.4.1.1.6.2 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian Ultrasound Multi-frame Image Storage Ultrasound Multi-frame Image Storage (retired) 1.2.840.10008.5.1.4.1.1.3.1 JPEG Baseline(Lossy) JPEG Lossless Non Hierarchical (Process14) 1.2.840.10008.5.1.4.1.1.3 JPEG Baseline coding Process 1 Presentation Context Table for Structured Reports Comprehensive Structured Report 1.2.840.10008.5.1.4.1.1.88.33 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.70 SCU SCU SCU SCU SCU SCU SCU SCU SCU SCU None None None None None None None None None None 1.2.840.10008.1.2.4.50 SCU None 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 SCU None 13

The operation also sends a Storage Commitment Request, with the following proposed presentation context. The result from the SCP is expected on another association for the Storage Commitment result. Table 2.3-6: Presentation Context Table - Proposed - Storage Commitment Abstract Syntax Name Abstract Syntax UID Transfer Syntax Name Transfer Syntax UID Storage Commitment Push Model SOP Class 1.2.840.10008.1.20.1 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 Role SCU Ext Neg. None 2.3.1.2.1.2.1 SOP Specific DICOM Conformance Statement for all Storage SOP Classes For these SOP classes (Storage and Storage Commitment), all status codes with status Refused or Error are treated as failures and terminate the association and operation. On a failure, the request will be put in a holding queue for the user to manually retry the request. All status codes with status Warning or Success are treated as successes. If the storage SCP does not support service, Voluson S6/S8 issues an association was aborted message and does not send image and close the connection in negotiation step. 2.3.1.2.2 Real-World Activity B ( Verify Operation) 2.3.1.2.2.1 Associated Real-World Activity The user may initiate a DICOM Verification Request in the Config screen. Associations will be released upon the receipt of each C-ECHO confirmation. In the event that the SCP does not respond, the operation will time out and the VOLUSON S6/S8 close the association and inform the user. 2.3.1.2.2.2 Proposed Presentation Context Table Table 2.3-7: Presentation Context Table - Proposed Abstract Syntax Name Abstract Syntax UID Transfer Syntax Name Transfer Syntax UID Verification SOP Class 1.2.840.10008.1.1 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 Role SCU Ext Neg. None 2.3.1.2.3 Real-World Activity C ( Query Worklist Operation) 2.3.1.2.3.1 Associated Real-World Activity The user may initiate a DICOM Worklist Query in Search screen, which will send a C-FIND-RQ to the Worklist SCP. Associations will be released upon the receipt of C-FIND-RSP confirmation. 2.3.1.2.3.2 Proposed Presentation Context Tables Table 2.3-8: Presentation Context Table - Proposed Abstract Syntax Name Abstract Syntax UID Transfer Syntax Name Transfer Syntax UID Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 2.3.1.2.3.2.1 SOP Specific DICOM Conformance Statement for Worklist SOP Classes Role SCU Ext Neg. None The VOLUSON S6/S8 includes matching keys in the Modality Worklist queries as described in Section 9.5. 14

All status codes with status Refused or Error are treated as failures and terminate the association and operation. On a failure, the user will be informed and the last successful query will be used as Worklist. All status codes with status Warning or Success are treated as successes. In the event of exceed time value while query service, VOLUSON S6/S8 terminate and cancel service automatically. Service Status Status Code Further Meaning Application Behaviour When receiving Status Codes Related Fields Processed if received Refused A700 Out of resources Terminate the association (0000,0902) and operation 0122 SOP Class not Terminate the (0000,0902) Supported association and operation Failed A900 Identifier does not Terminate the (0000, 0901) match SOP Class association and operation (0000, 0902) Cxxx Unable to process Terminate the (0000,0901) association and operation (0000,0902) Cancel FE00 Matching terminated Terminate the (0000, 0901) due to exceed max association and operation (0000, 0902) retries and timeout. Success 0000 Matching is complete No final identifier is supplied None Pending FF00 Matches are continuing Current Match is supplied and any Optional Keys were supported in the same manner FF01 Matches are continuing Warning that one or more Optional Keys were not supported for existence for this Identifier Receiving process of the matches continues. Receiving process of the matches continues without any warnings or errors Identifier Identifier 2.3.1.2.4 Real-World Activity D ( Start/End Exam Operation) 2.3.1.2.4.1 Associated Real-World Activity The Modality Performed Procedure Step messages are sent when the exam is started by the user after a worklist entry has been selected or patient data have been entered on the patient data entry screen. At this time the N-CREATE message is sent. The N-SET will be sent when 'End Exam' is being pressed. The status is set to COMPLETED by default, however the operator may choose to manually set the status to DISCONTINUED and select the discontinuation reason from a predefined list. 2.3.1.2.4.2 Proposed Presentation Context Table Table 2.3-9: Presentation Context Table Proposed Abstract Syntax Name Abstract Syntax UID Transfer Syntax Name Transfer Syntax UID Modality Performed Procedure Step SOP Class 1.2.840.10008.3.1.2.3.3 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 Role SCU Ext Neg. None 2.3.1.2.4.2.1 SOP Specific DICOM Conformance Statement for Modality Performed Procedure Step Class The VOLUSON S6/S8 includes Attributes in the Modality Performed Procedure Step N-CREATE as described in Section 10.2.1. 15

The VOLUSON S6/S8 includes Attributes in the Modality Performed Procedure Step N-SET as described in Section 10.2.1. The mapping from Worklist attributes is described in Section 9.5. VOLUSON S6/S8 sends N-SET after the exam is ended. The N-SET will include all acquired images SOP Instance UIDs and the status of COMPLETED or DISCONTINUED. For this SOP class, all status codes with status Refused or Error are treated as failures and terminate the association and operation. All status codes with status Warning or Success are treated as successes. 2.3.1.2.5 Real-World Activity E ( Image Print Operation) 2.3.1.2.5.1 Associated Real-World Activity Upon a request by the operator, print jobs will be sent to a DICOM Print SCP. The jobs are entered into a send queue and processed by the spool manager. If an error occurs during the transmission the operation may be retried manually. The number of automatic entries is configurable. The maximum number of retries is configurable. 2.3.1.2.5.2 Proposed Presentation Context Tables Table 2.3-10: Presentation Context Table Proposed Abstract Syntax Name Abstract Syntax UID Transfer Syntax Name Transfer Syntax UID Basic Grayscale Print 1.2.840.10008.5.1.1.9 Management Meta SOP Class Basic Color Print Management Meta SOP Class Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.5.1.1.18 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 Role SCU SCU Ext Neg. None None 2.3.1.2.5.2.1 SOP Specific DICOM Conformance Statement for all Print Management SOP Classes The VOLUSON S6/S8 treats all status codes with status Refused or Error are treated as failures and the spool manager reties the operation. After the configurable number of retires has been exceeded the spooler s job status is set to FAILED and the print job may be retired manually. Please refer to section 12 Print Management SOP Class Definition for more details about printing implementation. 2.3.1.2.6 Real-World Activity F ( Query/Retrieve Images Operation) 2.3.1.2.6.1 Associated Real-World Activity The user may initiate a DICOM Exam Query in Search screen, which will send a C-FIND-RQ to the Query/Retrieve SCP. Associations will be released upon the receipt of C-FIND-RSP confirmation. The user may then select an examination to be retrieved, using the C-MOVE-RQ command to the Query/Retrieve SCP. The result from the SCP is expected on another association for the retrieved examinations. 2.3.1.2.6.2 Proposed Presentation Context Tables Table 2.3-11: Presentation Context Table - Proposed Abstract Syntax Name Abstract Syntax UID Transfer Syntax Name Transfer Syntax UID Study Root Query/Retrieve Information Model - FIND Study Root Query/Retrieve Information Model MOVE Explicit VR Little Endian 1.2.840.10008.5.1.4.1.2.2.1 Explicit VR Big Endian Implicit VR Little Endian Explicit VR Little Endian 1.2.840.10008.5.1.4.1.2.2.2 Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 Role SCU SCU Ext Neg. None None 16

2.3.1.2.6.2.1 SOP Specific DICOM Conformance Statement for Study Root Query/Retrieve SOP Classes Only a single information model, Study Root is supported. All queries are initiated at the highest level of the information model (the STUDY level), and then for each response received, recursively repeated at the next lower level (SERIES). The user then can select one "Exam" (Series) and retrieve it. Retrieving is being done at the SERIES level. CANCEL requests can be issued during the queries via graphical user interface. The VOLUSON S6/S8 treats all status codes with status Refused or Error as failures and terminates the association and operation. All status codes with status Warning or Success are treated as success. Table 2.3-12: Study Root Request Identifier for Query Attribute Name Tag Types of Matching Filtering is supported STUDY Level Study Date (0008,0020) R Study Time (0008,0030) R Yes Referring Physicians Name (0008,0090) S,*, U Yes Accession Number (0008,0050) S,*, U Patient Name (0010,0010) *, U Yes Patient ID (0010,0020) *, U Yes Patient Birth Date (0010,0030) R Yes Patient Sex (0010,0040) S,*,U Yes Study Instance UID (0020,000D) UNIQUE Number of Patient Related Studies (0020,1200) U Number of Patient Related Series (0020,1202) U SERIES Level Modality (0008,0060) S always "US" Series Date (0008,0021) R Series Time (0008,0031) R Series Instance UID (0020,000E) UNIQUE Number of Series Related Instances (0020,1209) U Types of Matching Single Value Matching (S) Universal Matching (U) Wildcard Matching (*) Date, Time Range Matching (R) The types of Matching supported by the C-FIND SCU are: `S' indicates the identifier attribute uses Single Value Matching, an `R' indicates Range Matching, a "*" indicates wildcard matching, a `U' indicates Universal Matching, and `UNIQUE' indicates that this is the Unique Key for 16 that query level, in which case Universal Matching or Single Value Matching is used depending on the query level. "Filtering is supported" means that matching strings can be controlled from the Search screen. 2.3.1.2.6.2.2 SOP Specific DICOM Conformance Statement for Study Root Query/Retrieve Information SOP Classes The VOLUSON S6/S8 all status codes with status Refused or Error are treated as failures and terminate the association and operation. All status codes with status Warning or Success are treated as successes. 2.3.1.3 Association Acceptance Policy The VOLUSON S6/S8 AE accepts an association when it receives a Verification Request from another network device, an 17

image storage request from an SCU or a Storage Commitment result from a Storage Commitment SCP. 2.3.1.3.1 Real-World Activity A ( Verify operation) 2.3.1.3.1.1 Associated Real-World Activity An incoming Verification Request will cause the AE to accept the association and respond with a Verification Response. 2.3.1.3.1.2 Accepted Presentation Context Table Table 2.3-13: Presentation Context Table - Accepted Abstract Syntax Name Abstract Syntax UID Transfer Syntax Name Transfer Syntax UID Verification SOP Class 1.2.840.10008.1.1 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 Role SCP Ext Neg. None 2.3.1.3.1.2.1 SOP Specific DICOM Conformance Statement for Verify SOP Class The AE provides standard conformance to the Verification SOP Class as an SCP. The port number used is configured on Config screen, default is 104. 2.3.1.3.1.3 Presentation Context Acceptance Criterion No criterion. 2.3.1.3.1.4 Transfer Syntax Selection Policies The selected transfer syntax is based on the proposed transfer syntax list. The priority order is Explicit VR Little Endian, Explicit VR Big Endian and Implicit VR Little Endian. 2.3.1.3.2 Real-World Activity B ( End Exam Operation) 2.3.1.3.2.1 Associated Real-World Activity VOLUSON S6/S8 will only listen for an N-EVENT-REPORT (Storage Commitment Result) from a Storage Commitment SCP in a new association. 2.3.1.3.2.2 Accepted Presentation Context Table Table 2.3-14: Presentation Context Table - Accepted - Storage Commitment Abstract Syntax Name Abstract Syntax UID Transfer Syntax Name Transfer Syntax UID StorageCommitment Push Model SOP Class 1.2.840.10008.1.20.1 Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 Role SCU Ext Neg. None 2.3.1.3.2.2.1 SOP Specific DICOM Conformance Statement for the Storage Commitment Push Model SOP Class SCU The VOLUSON S6/S8 will only accept the SCU role (which must be proposed via SCP/SCU Role Selection Negotiation) within a Presentation Context for the Storage Commitment Push Model SOP Class. The result from the SCP is expected on another association for the Storage Commitment result. The VOLUSON S6/S8 behavior after receiving an N-EVENT-REPORT (Storage Commitment Result) is described in Section 9.5. 18

For this SOP class, all status codes with status Refused or Error are treated as failures and terminate the association and operation. All status codes with status Warning or Success are treated as successes. Below are all possible status codes which VOLUSON S6/S8 would send upon N-EVENT-REPORT request as EVENT- REPORT response. The port number used is configured on Config screen, default is 104. Service Status Status Code Conditions Failed 0110H Processing Error Success 0000 N-Even Report received successfully. 2.3.1.3.3 Real-World Activity C ( Receive Image Operation) 2.3.1.3.3.1 Associated Real-World Activity VOLUSON S6/S8 will accept associations for C-STORE-RQs. The received images will be stored into a local database. 2.3.1.3.3.2 Accepted Presentation Context Table Table 2.3-15: Presentation Context Table - Accepted Abstract Syntax Name Abstract Syntax UID Transfer Syntax Name Transfer Syntax UID Ultrasound Image Storage Ultrasound Multi-frame Image Storage Ultrasound Image Storage (retired) Enhanced US Volume Storage 1.2.840.10008.5.1.4.1.1.6.2 Secondary Capture Image Storage JPEG Baseline (Lossy) 1.2.840.10008.5.1.4.1.1.6.1 JPEG Lossless Non Hierarchical (Process 14) Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian JPEG Baseline (Lossy) 1.2.840.10008.5.1.4.1.1.3.1 JPEG Lossless Non Hierarchical (Process 14) Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian JPEG Baseline (Lossy) 1.2.840.10008.5.1.4.1.1.6 JPEG Lossless Non Hierarchical (Process 14) Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian JPEG Baseline (Lossy) JPEG Lossless Non Hierarchical (Process 14) Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian JPEG Baseline (Lossy) 1.2.840.10008.5.1.4.1.1.7 JPEG Lossless Non Hierarchical (Process 14) Explicit VR Little Endian Explicit VR Big Endian Implicit VR Little Endian 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.1 1.2.840.10008.1.2.2 1.2.840.10008.1.2 Role SCP SCP SCP SCP SCP Ext Neg. None None None None None 2.3.1.3.3.2.1 SOP Specific DICOM Conformance Statement for Storage SOP Classes The AE provides standard conformance to the Storage SOP Classes as an SCP. The port number used is configured on Config screen, default is 104. The storage level is 0. 2.3.1.3.3.2.2 Presentation Context Acceptance Criterion No criterion. 19

2.3.1.3.3.2.3 Transfer Syntax Selection Policies The accepted transfer syntaxes are based on the proposed transfer syntax list. There is no defined priority order. All supported transfer syntaxes are accepted. 2.4 COMMUNICATION PROFILES 2.4.1 Supported Communication Stacks (PS 3.8) DICOM Upper Layer (PS 3.8) is supported using TCP/IP. 2.4.2 TCP/IP Stack The TCP/IP stack is inherited from the product s operating s yste m. Please refer to product documentation f o r more information. 2.4.2.1 API Not applicable to this product. 2.5 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS The product will send ultrasound raw volume data information in private data elements designated by the private tag 7FE1,00xx VR OB, VM 1. 2.6 CONFIGURATION 2.6.1 AE Title/Presentation Address Mapping The Local AE title is configurable through the Config screen, see below. 2.6.2 Configurable Parameters Network: Local IP address Local IP netmask Local routing table information Local: Local AE Title Local TCP Port Number Verification: The AE Title, IP address and port number of the SCP Modality Worklist: The AE Title, IP address and port number of the SCP Storage 20