Page 1 of 12 SonoWin Picture Archiving System DICOM SSCP Module Version 4.5 DICOM Conformance Statement
Page 2 of 12 Table of Contents 1 DOCUMENT HISTORY... 4 2 INTRODUCTION... 4 2.1 SOURCES OF INFORMATION... 4 2.2 ACRONYMS AND ABBREVIATIONS... 4 3 IMPLEMENTATION MODEL... 5 3.1 APPLICATION DATA FLOW DIAGRAM... 5 3.2 FUNCTIONAL DEFINITION OF APPLICATION ENTITY (AE)... 5 3.2.1 Storage SCP... 5 3.2.2 Modality Worklist SCP... 5 3.2.3 Verification SCP... 6 3.3 SEQUENCING OF REAL-WORLD ACTIVITIES... 6 4 AE SPECIFICATIONS... 7 4.1 AE SPECIFICATIONS FOR VERIFICATION SCP... 7 4.1.1 Association establishment policies... 7 4.1.1.1 General...7 4.1.1.2 Real-world activity for Echo Response...7 4.1.1.2.1 Presentation context table for Echo Response operation...7 4.2 AE SPECIFICATIONS FOR STORAGE SCP... 8 4.2.1 Association establishment policies... 8 4.2.1.1 General...8 4.2.1.2 Number of associations...8 4.2.1.3 Asynchronous nature...8 4.2.1.4 Implementation identifying information...8 4.2.1.5 Calling and called AE titles...8 4.2.2 Association initiation for SONOWIN_SSCP... 9 4.2.3 Association acceptance policy for SONOWIN_SSCP AE... 9 4.2.3.1 Real-World activity for Receive Image operations...9 4.2.3.1.1 Associated real-world activity for Receive Image operations...9 4.2.3.1.2 Presentation context table for Receive Image operations...9 4.2.3.1.2.1 SOP specific conformance for all storage SOP Classes...9 4.2.3.1.2.2 Presentation context acceptance criterion for Receive Image operations...10 4.2.3.1.2.3 Transfer syntax selection policies for Receive Image operations...10 4.2.3.1.2.4 Photometric interpretation...10 4.3 AE SPECIFICATIONS FOR MOALITY WORKLIST SCP... 10 4.3.1 Association establishment policies... 10 4.3.1.1 General...10 4.3.1.2 Number of associations...10 4.3.1.3 Implementation identifying information...10 4.3.1.4 Calling and called AE titles...10 5 PROFILES... 11 5.1 SUPPORTED COMMUNICATION STACKS... 11 5.2 TCP/IP STACK... 11 5.2.1 Physical Media Support... 11 6 EXTENSIONS/SPECIALIZATIONS/PRIVATIZATIONS... 11 6.1 STANDARD EXTENDED/SPECIALIZED/PRIVATE SOPS... 11 6.2 PRIVATE TRANSFER SYNTAXES... 11 7 CONFIGURATION... 11 7.1 SONOWIN_SSCP CONFIGURATION FILES... 11 7.1.1 AE title/presentation address mapping... 11 7.1.2 Configurable parameters... 11
Page 3 of 12 8 SUPPORT OF EXTENDED CHARACTER SETS... 12
Page 4 of 12 1 Document History Rev Date Author Comments 1 12/01/1998 C. Schwerin Created 1.1 16/04/1999 C. Schwerin Some Error corrections in chapter 7 Table 1: Document History 2 Introduction This is a conformance statement for the SonoWin DICOM Storage Service Class Provider (SONOWIN_ SSCP) and DICOM Modality Worklist Service Class Provider (SONOWIN_WLSCP) module. The DICOM functionality is based on the MergeCOM Toolkit of Merge Technologies Inc. The following functions are supported in SONOWIN_SSCP and SONOWIN_WLSCP: - Verifying DICOM 3.0 connectivity using Verification service class SCP - Importing images into SonoWin database using DICOM 3.0 Storage service class SCP - Importing measurements into SonoWin database using DICOM SR SCP - Delivering modality worklist as a DICOM Mocality worklist SCP. 2.1 Sources of information - Digital Imaging and Communication in Medicine (DICOM), NEMA Standard Publication No. PS 3.1~3.13, NEMA, 1300 North 17th Street, Suite 1847, Rosslyn, VA 22209, phone: (703)-841-3200. - World Wide Web: http://www.nema.org/medical/dicom.htm 2.2 Acronyms and Abbreviations AE DICOM IOD ISO NEMA PDU SCP SCU TCP/IP SOP UID Application Entity Digital Imaging and Communication in Medicine Information Object Definition International Standards Organization National Electrical Manufacturers Association Protocol Data Unit Service Class Provider (server) Service Class User (client) Transmission Control Protocol/Internet Protocol Service Object Pair Unique Identification
Page 5 of 12 3 Implementation model SONOWIN_SSCP implements a DICOM Storage Service Class Provider (SCP) which can receive DICOM images and structured reports from a DICOM Storage Service Class user (SCU). SONOWIN_WLSCP implements a DICOM Modality Worklist Service Class Provider (SCP) which can answer C- FIND requests from a DICOM Modality Worklist SCU. SONOWIN_SSCP also implements an DICOM Echo SCP for connection test. 3.1 Application data flow diagram Local Remote C-STORE Storage SCU SonoWin Archive SONOWIN_SSCP Module C-FIND Worklist SCU C-ECHO Verification SCU DICOM Standard Interface Figure 1: SONOWIN_SSCP application data flow diagram 3.2 Functional definition of Application Entity (AE) 3.2.1 Storage SCP All communications and image transfer with the remote application is accomplished utilizing the DICOM protocol over a network using the TCP/IP protocol stack. SONOWIN_SSCP waits for an association to accept at the TCP/IP port number that is configured at the time this application is initiated. When an association request is received with valid connections criteria, SONOWIN_SSCP responds with a list of SOP class UIDs that it will accept. It then waits for a C-STORE request. If a C-STORE is received, then all incoming images that are conformant to the association are stored in the SonoWin image database. 3.2.2 Modality Worklist SCP All communications and worklist transfer with the remote application is accomplished utilizing the DICOM protocol over a network using the TCP/IP protocol stack. SONOWIN_WLSCP waits for an association to accept at the TCP/IP port number that is configured at the time this application is initiated. When an association request is received with valid connections criteria, SONOWIN_WLSCP responds with the Modality Worklist SOP class UID as a SCP. It then waits for a C-FIND request. If a C-FIND is received, then it will respond with the corresponding C-FIND-RSP messages for all requested worklist entries.
Page 6 of 12 3.2.3 Verification SCP All communications with the remote application is accomplished utilizing the DICOM protocol over a network using the TCP/IP protocol stack. SONOWIN_SSCP will respond, if asked, with the Verification SOP Class UID as a SCP. 3.3 Sequencing of real-world activities See previous section.
Page 7 of 12 4 AE specifications 4.1 AE Specifications for Verification SCP SONOWIN_SSCP provides Standard Conformance to the following DICOM V3.0 Service Object Pair (SOP) Class as a Verification Service Class Provider (SCP). As an SCP it sends out an Echo response after it receives an Echo request from a remote AE. SOP Class UID SOP Class Name 1.2.840.10008.1.1 Verification SOP Class Table 2: Valid SCP Verification SOP Class for SONOWIN_SSCP 4.1.1 Association establishment policies 4.1.1.1 General The SONOWIN_SSCP application will wait for an association as an SCP of Verification Services. When a C-ECHO request is received, it will respond with a C-ECHO-RSP. 4.1.1.2 Real-world activity for Echo Response The SONOWIN_SSCP Application Entity waits for an association request and accepts associations to do, among other things, the Verification Service. The association is closed after an error or when the initiator requests that it be closed. 4.1.1.2.1 Presentation context table for Echo Response operation Only the presentation context listed in Table 4 will be accepted by the SONOWIN_SSCP for the Verification Service Class. Presentation Context Table Abstract Syntax Transfer Syntax Extended Role Name UID Name List UID List Negotiation Verification Service Class 1.2.840.10008.1.1 Explicit VR Little Endian Implicit VR Little Endian Explicit VR Big Endian Table 3: Echo Check Presentation Contexts of SONOWIN_SSCP 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 SCP None
Page 8 of 12 4.2 AE Specifications for Storage SCP SONOWIN_SSCP provides Standard Conformance to the following DICOM V3.0 Service Object Pair (SOP) Classes as a Storage Service Class Provider (SCP). The individually available SOP classes depend on configuration by service. SOP Class UID SOP Class Name 1.2.840.10008.5.1.4.1.1.6.1 Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6 Ultrasound Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.3.1 Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3 Ultrasound Multi-frame Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.7 Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.4 Multi-frame True Color Secondary Capture Image 1.2.840.10008.5.1.4.1.1.88.11 Basic Text SR 1.2.840.10008.5.1.4.1.1.88.22 Enhanced SR 1.2.840.10008.5.1.4.1.1.88.33 Comprehensive SR 1.2.840.10008.5.1.4.1.1.88.3 Special SR format for Acuson Sequoia 1.2.840.10008.5.1.4.1.1.1 Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.2 CT Image Storage 1.2.840.10008.5.1.4.1.1.2.1 Enhanced CT Image Storage 1.2.840.10008.5.1.4.1.1.4 MR Image Storage 1.2.840.10008.5.1.4.1.1.4.1 Enhanced MR Image Storage 1.2.840.10008.5.1.4.1.1.20 Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.12.1 X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1.1 Enhanced XA Image Storage Table 4: Valid SCP Storage SOP Classes for SONOWIN_SSCP 4.2.1 Association establishment policies 4.2.1.1 General The SONOWIN_SSCP application will wait for an association as an SCP of Storage Services. When a C-STORE request is received, the corresponding images are stored to SonoWin image database. The maximum PDU size is configurable from a minimum of 4,096 bytes. The default PDU size is 28,672 bytes. 4.2.1.2 Number of associations The SONOWIN_SSCP AE allows multiple simultaneous Store associations. The maximum number of simultaneous associations is 10. 4.2.1.3 Asynchronous nature The SONOWIN_SSCP AE does not support asynchronous communication (multiple outstanding transactions over a single association). 4.2.1.4 Implementation identifying information This implementation will be identified by: - Implementation Class UID: 2.16.840.1.113669.632.14.1.1 - Implementation Version Name: SONOWIN_SSCP_340 4.2.1.5 Calling and called AE titles The SONOWIN_SSCP called AE title is preconfigured to be SONOWIN_SSCP. The user can change it when needed. A calling AE title is'nt used by SONOWIN_SSCP.
Page 9 of 12 4.2.2 Association initiation for SONOWIN_SSCP The SONOWIN_SSCP does not initiate any assocoations. 4.2.3 Association acceptance policy for SONOWIN_SSCP AE The SONOWIN_SSCP client application accepts an association for the Storage Service Class. SONOWIN_SSCP is able to abort the association when an error occurs. 4.2.3.1 Real-World activity for Receive Image operations SONOWIN_SSCP waits for an association and offers to do the Image Storage service. The association is closed after an error or when the initiator requests that it be closed. 4.2.3.1.1 Associated real-world activity for Receive Image operations Once the association has been established, the SONOWIN_SSCP waits for transmission of conformant Storage Service messages. 4.2.3.1.2 Presentation context table for Receive Image operations For all entries is Role=SCP and Extended Negotiation=None Abstract Syntax Transfer Syntax Name UID Name List UID List 1.2.840.10008.5.1.4.1.1.6.1 Explicit VR Little Endian 1.2.840.10008.5.1.4.1.1.6 Implicit VR Little Endian 1.2.840.10008.5.1.4.1.1.3.1 Explicit VR Big Endian 1.2.840.10008.5.1.4.1.1.3 RLE Lossless 1.2.840.10008.5.1.4.1.1.7 JPEG Baseline Lossy 1.2.840.10008.5.1.4.1.1.7.4 Ultrasound Image Storage Ultrasound Image Storage (Retired) Ultrasound Multi-frame Image Storage Ultrasound MF Image Storage (Retired) Secondary Capture Image Storage Multi-frame True Color Secondary Capture Basic Text SR Enhanced SR Comprehensive SR Special SR Computed Radiography Image Storage CT Image Storage Enhanced CT Image Storage MR Image Storage Enhanced MR Image Storage Nuclear Medicine Image Storage X-Ray Angiographic Image Storage Enhanced XA Image Storage 1.2.840.10008.5.1.4.1.1.88.11 1.2.840.10008.5.1.4.1.1.88.22 1.2.840.10008.5.1.4.1.1.88.33 1.2.840.10008.5.1.4.1.1.88.3 1.2.840.10008.5.1.4.1.1.1 1.2.840.10008.5.1.4.1.1.2 1.2.840.10008.5.1.4.1.1.2.1 1.2.840.10008.5.1.4.1.1.4 1.2.840.10008.5.1.4.1.1.4.1 1.2.840.10008.5.1.4.1.1.20 1.2.840.10008.5.1.4.1.1.12.1 1.2.840.10008.5.1.4.1.1.12.1.1 Table 5: Receive Image Presentation Contexts of SONOWIN_SSCP Explicit VR Little Endian Implicit VR Little Endian Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian Explicit VR Big Endian RLE Lossless JPEG Baseline Lossy JPEG Lossless (Proc 14) 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 1.2.840.10008.1.2.5 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 1.2.840.10008.1.2.5 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.70 4.2.3.1.2.1 SOP specific conformance for all storage SOP Classes The SONOWIN_SSCP AE responds to a C-STORE request with one of these response codes: Service Status Code Status Description Status (0000,0900) Related Fields Refused Out of Resources There were insufficient resources to process the request. The request was not processed. A765 (0000,0902) contains a short description of the condition. Error Data Set does not match SOP Class A required A965 (0000,0901) contains a listing of attribute attribute is not present in the message. The request was not processed. tags missing. (0000,0902) contains a short description of the condition. Cannot understand The message was not properly DICOM-encoded. The request was not processed. C065 (0000,0902) contains a short description of the condition. Processing failure A condition arose which 0111 None prevented the processing of the request Success 0000 None Table 6: Response codes for SONOWIN_SSCP
Page 10 of 12 4.2.3.1.2.2 Presentation context acceptance criterion for Receive Image operations Not applicable since only a single presentation context for each Storage Service Class is supported. 4.2.3.1.2.3 Transfer syntax selection policies for Receive Image operations The order of the Transfer syntaxes are accepted in the following order: Transfer Syntax UID Transfer Syntax Name 1.2.840.10008.1.2.4.50 JPEG Baseline Lossy 1.2.840.10008.1.2.5 RLE Lossless 1.2.840.10008.1.2.4.70 JPEG Lossless (Process 14) 1.2.840.10008.1.2 Explicit Little Endian Syntax 1.2.840.10008.1.2.1 Implicit Little Endian Syntax 1.2.840.10008.1.2.2 Explicit Big Endian Syntax Table 7: Transfer syntax selection policies Note that this acceptance criteria can be overridden in the configuration. 4.2.3.1.2.4 Photometric interpretation Photometric Interpretation, i.e., color mode of the pixel image data, is not a negotiable parameter in DICOM 3.0. SONOWIN_SSCP imports color images in RGB and Palette Color mode and grayscale images in monochrome 2 or monochrome 1 mode. Bit Depth of 8, 10 and 12 bit are supported. Image Compression is supported as shown in Table 7. 4.3 AE Specifications for Moality Worklist SCP SONOWIN_WLSCP provides Standard Conformance to the following DICOM V3.0 Service Object Pair (SOP) Classes as a Storage Service Class Provider (SCP). SOP Class UID SOP Class Name 1.2.840.10008.5.1.4.31 Modality Worklist Information model - FIND 4.3.1 Association establishment policies 4.3.1.1 General The SONOWIN_WLSCP application will wait for an association as an Modality Worklist SCP. When a C-FIND request is received, the corresponding worklist entries are submitted as C-FIND-RSP. The maximum PDU size is configurable from a minimum of 4,096 bytes. The default PDU size is 28,672 bytes. There is a configuration entry which can restrict the worklist to the currently displayed patient only. 4.3.1.2 Number of associations The SONOWIN_WSCP AE allows multiple simultaneous Store associations. The maximum number of simultaneous associations is 10. 4.3.1.3 Implementation identifying information This implementation will be identified by: - Implementation Class UID: 2.16.840.1.113669.632.14.1.1 - Implementation Version Name: SONOWIN_SSCP_340 4.3.1.4 Calling and called AE titles The SONOWIN_WLSCP called AE title is preconfigured to be SONOWIN_WLSCP. The user can change it when needed. The calling AE title is'nt used by SONOWIN_WLSCP.
Page 11 of 12 5 Profiles 5.1 Supported Communication Stacks SONOWIN_SSCP provides DICOM V3.0 TCP/IP Network Communication Support as defined in PS 3.8. 5.2 TCP/IP Stack SONOWIN_SSCP communicates over the TCP/IP protocol stack on any physical interconnection media supporting the TCP/IP stack. It inherits the TCP/IP stack from the Microsoft Windows host operating system upon which it executes. 5.2.1 Physical Media Support SONOWIN_SSCP AE is indifferent to the physical medium over which TCP/IP executes; it inherits this from the operating system on which it exists. 6 Extensions/specializations/privatizations 6.1 Standard extended/specialized/private SOPs None supported. 6.2 Private Transfer Syntaxes None supported. 7 Configuration 7.1 SONOWIN_SSCP Configuration files The SONOWIN_SSCP module references 4 configuration files. The first, dcmsscp.ini, has to be in the module directory. dcmsscp.ini dcmsscp.pro dcmsscp.app dcmsscp.srv Specifies the names of the other 3 configuration files and also contains message logging parameters. Specifies run-time parameters for the SONOWIN_SSCP module. Defines applications on other network nodes, to which connections are possible. Service and sequence definitions. 7.1.1 AE title/presentation address mapping Presentation address mapping is configured in the dcmsscp.app file. The Presentation Address of an SCP application as a provider is specified by configuring the Listen Port in the dcmsscp.pro file, and specifying the AE title for the SCP within the SonoWin configuration application. 7.1.2 Configurable parameters The dcmsscp.pro configuration file can be used to set or modify other lower-level communication parameters. This includes time-outs and other parameters. Some information about supported SOP classes is also stored here. Most parameters in this file should NEVER be changed. Doing so could break DICOM conformance. Before modifying any parameters, such as time-out, be sure to have a backup of the originally supplied dcmsscp.pro file. Also, before modifying other parameters, you should consider contacting for advice.
Page 12 of 12 8 Support of extended Character sets Not supported.