PACSMail DICOM Conformance Statement Version 1.05 January 2009 Sybermedica Ltd St John s Innovation Centre Cowley Road Cambridge CB4 0WS Telephone: 01223 421996 Web: www.sybermedica.com Email: info@sybermedica.com
CONTENTS 1 INTRODUCTION...2 1.1 OVERVIEW...2 1.2 CHANGE HISTORY...2 1.3 DEFINITIONS...2 2 IMPLEMENTATION MODEL OF THE APPLICATION...4 2.1 APPLICATION FLOW DIAGRAM...4 2.2 FUNCTIONAL DEFINITIONS OF APPLICATION ENTITIES...5 2.2.1 Functional Definition of Verify...5 2.2.2 Functional Definition of Send...5 2.2.3 Functional Definition of Query-Retrieve...5 2.2.4 Functional Definition of Listen...5 2.2.5 Function Definition of Auto Send...5 2.2.6 Functional Definition of Auto Listen...5 2.2.7 Summary of AETs offered by PACSMail...5 2.3 SEQUENCING OF REAL WORLD ACTIVITIES...5 2.4 DEFAULT ASSOCIATION POLICIES...5 3 APPLICATION ENTITY SPECIFICATIONS...6 3.1 APPLICATION ENTITY VERIFY...6 3.1.1 SOP Classes...6 3.1.2 Association Policies...6 3.2 APPLICATION ENTITY SEND...8 3.2.1 SOP Classes...8 3.2.2 Association Policies...8 3.3 APPLICATION ENTITY QUERY RETRIEVE...11 3.3.1 SOP Classes...11 3.3.2 Association Policies...11 3.4 APPLICATION ENTITY STORAGE AS SCP...14 3.4.1 SOP Classes...14 3.4.2 Association Policies...14 3.5 APPLICATION ENTITY LISTEN...16 3.6 APPLICATION ENTITY AUTO LISTEN...16 3.7 APPLICATION ENTITY AUTO SEND...16 4 COMMUNICATION PROFILES...17 3.1. SUPPORTED COMMUNICATIONS STACKS (PART 8)...17 3.2. TCP/IP STACK...17 3.3. PHYSICAL MEDIA SUPPORT...17 5 EXTENSIONS/SPECIALIZATIONS/PRIVATIZATIONS...17 6 CONFIGURATION...17 7 SUPPORT OF EXTENDED CHARACTER SETS...17 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 1
1 Introduction 1.1 Overview PACSMail is a DICOM 3 compliant medical device that allows disparate users to share any DICOM data for review and reporting. PACSMail relies on the DICOM standard to acquire data from a variety of sources including, PACS, workstations, modalities, removable media (CDs etc) and any DICOM compliant software device. For the purpose of this document PACSMail refers to a group of Windows programs and services that are part of the PACSMail managed service designed and developed by Sybermedica Ltd. Note that PACSMailPro and PACSMailMobile support the same functionality as PACSMail. 1.2 Change History Version Author Reason Date 01_00DICOM Conformance Alan Grace Initial Version 21-Jan-09 Statement 01_02DICOM Conformance Andrea Harry Review 25-Jan-09 Statement 01_03DICOM Conformance Dave Harvey Review 02-Feb-09 Statement 01_04DICOM Conformance Alan Grace Revision 02-Feb-09 Statement 01_04DICOM Conformance Statement Alan Grace Final Version 03-Feb-09 1.3 Definitions ACR AE AET ASCII DB DICOM DIMSE DIMSE-C DIMSE-N GUI HIS IOD ISO NEMA RIS OSI PACS PDU American College of Radiology Application Entity Application Entity Title American Standard Code for Information Interchange Database Digital Imaging and Communications in Medicine DICOM Message Service Element DICOM Message Service Element- Composite DICOM Message Service Element- Normative Graphical User Interface Hospital Information System Information Object Definition International Standard Organization National Electrical Manufacturers Association Radiology Information System Open Systems Interconnection Picture Archive & Communication System Protocol Data Unit 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 2
SCU SCP SOP Tag TCP/IP UID VR VM Service Class User (DICOM client) Service Class Provider (DICOM server) Service-Object Pair A 32 bit integer consisting of a group/element pair Transmission Control Protocol/Internet Protocol Unique Identifier Attribute Value Representation Value Multiplicity 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 3
2 Implementation Model of the Application 2.1 Application Flow Diagram The diagram below shows the DICOM services provided by PACSMail. PACSMail windows client Verify Echo SCP C-ECHO Echo SCU Echo SCU C-ECHO Echo SCP C-STORE Send Store SCU Store SCP QR Query Retrieve SCU C-FIND C-GET Query Retrieve SCP Listen Store SCP C-STORE Store SCU PACSMail auto services Auto Listen Store SCP C-STORE Store SCU Auto Send Store SCU C-STORE Store SCP DICOM Interface 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 4
2.2 Functional Definitions of Application Entities 2.2.1 Functional Definition of Verify This functionality allows the user to check remote AETs are configured and responding. 2.2.2 Functional Definition of Send This function allows the user to send images to a remote AET. 2.2.3 Functional Definition of Query-Retrieve This function allows the user to search remote AETs for patients by name, date of birth or patient number. Images can be retrieved using a DICOM Move request. 2.2.4 Functional Definition of Listen The user can set PACSMail to manually listen for incoming DICOM Images. transferred via the C-store method with PACSMail acting as a SCP. Images are 2.2.5 Function Definition of Auto Send This is a Windows service that can be configured to auto route DICOM Images to a remote AET. This does not require user intervention. Logs are updated where applicable. 2.2.6 Functional Definition of Auto Listen This is a Windows service that can be configured to permanently listen for incoming DICOM images to a particular port. The images are stored in a configured directory for future processing. Logs are updated where applicable. 2.2.7 Summary of AETs offered by PACSMail SCU C-ECHO C-FIND C-GET C-STORE SCP C-ECHO C-STORE 2.3 Sequencing of Real World Activities Table 2.1. Summary of AETs Not applicable. 2.4 Default Association Policies 2.4.1.1 General Application Context Name 1.2.840.10008.3.1.1.1 Table 2.2. Default DICOM Application Context 2.4.1.2 Default Implementation Identifying Information Implementation Class UID 1.2.826.0.1.3680043.1.1.4.3.28.2 Implementation Class Name DCMOBJ4.3.88.2 Table 2.3. Default DICOM Implementation Class 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 5
3 Application Entity Specifications 3.1 Application Entity Verify This is the detailed specification for the Verify AE for PACSMail. 3.1.1 SOP Classes This Application Entity provides Standard Conformance to the following SOP Class: SOP Class UID SOP Class Name SCU SCP 1.2.840.10008.1.1 Verification Yes Yes Table 3.1.1. SOP Class for Verify AE Note: Any SOP specific behavior is documented later in the conformance statement in the applicable SOP specific conformance section. 3.1.2 Association Policies 3.1.2.1 Number of Associations. Maximum number of simultaneous associations 1 Table 3.1.2. Number of associations as an association initiator for AE Verify Maximum number of simultaneous associations 1 Table 3.1.3. Number of associations as an association acceptor for AE Verify 3.1.2.2 Asynchronous Nature Does not apply 3.1.2.3 Association Initiation Policy 3.1.2.3.1 User Initiates a Verify AE 3.1.2.3.1.1 Description and Sequencing of Activities The user initiates a verify or C-ECHO command to a defined Application Entity. The Application Entity titles and details are set in the PACSMail address book. When the AE has been set up the user can click the Verify button to check the requested AE is responding. 3.1.2.3.1.2 Proposed Presentation Contexts Each time an association is initiated, the Association Initiator proposes a number of Presentation Contexts to be used on that association. In this subsection, the Presentation Contexts proposed by Verify for activity Verify shall be defined in a table with the following format: 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 6
Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name UID Role Extended Negotiation Verification 1.2.840.10008.1.1 Implicit VR, 1.2.840.10008.1.2 Both None Little Endian Explicit VR 1.2.840.10008.1.2.1 Little Endian Explicit VR Big Endian 1.2.840.10008.1.2.2 Table 3.1.4. Proposed presentation contexts for AE Verify Presentation Context Table 3.1.2.4 Association Acceptance Policy PACSMail accepts all connections from all AE titles. 3.1.2.5 Specific Conformance for SOP Class Service Status Further Meaning Error Code Behaviour Success Confirmation 0000 User is informed Table 3.1.5. DICOM command response status handling behavior Exception Timeout Behavior The user is informed there has been a communication error Table 3.1.6. DICOM command communication failure behavior 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 7
3.2 Application Entity Send This is the detailed specification for the Send AE for PACSMail. 3.2.1 SOP Classes This Application Entity provides Standard Conformance to the following SOP Classes: See Table 3.2.3 3.2.2 Association Policies 3.2.2.1 Number of Associations. Maximum number of simultaneous associations 1 Table 3.2.1. Number of associations as an association initiator for AE Send Maximum number of simultaneous associations 1 Table 3.2.2. Number of associations as an association acceptor for AE Send 3.2.2.2 Asynchronous Nature Does not apply 3.2.2.3 Association Initiation Policy 3.2.2.3.1 User Initiates a Send AE C-Store 3.2.2.3.1.1 Description and Sequencing of Activities The user initiates a Send command to a defined Application Entity. The Application Entity titles and details are set in the PACSMail address book. When the AE has been set up the user can click the Send button in the Xray module to send the image(s) to the selected AET. 3.2.2.3.1.2 Proposed Presentation Contexts Each time an association is initiated, the Association Initiator proposes a number of Presentation Contexts to be used on that association. In this subsection, the Presentation Contexts proposed by Send for activity Send Image(s) shall be defined in a table with the following format: Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Role Syntax Computed Radiography 1.2.840.10008.5.1.4.1.1.1 See below SCU None Digital Xray Presentation 1.2.840.10008.5.1.4.1.1.1.1 See below SCU None Digital Xray Processing 1.2.840.10008.5.1.4.1.1.1.1.1 See below SCU None Digital Mammography Xray Presentation 1.2.840.10008.5.1.4.1.1.1.2 See below SCU None Digital Mammography Xray Processing 1.2.840.10008.5.1.4.1.1.1.2.1 See below SCU None Digital Intraoral XRay Presentation 1.2.840.10008.5.1.4.1.1.1.3 See below SCU None Digital Intraoral XRay Processing 1.2.840.10008.5.1.4.1.1.1.3.1 See below SCU None CT 1.2.840.10008.5.1.4.1.1.2 See below SCU None Ultrasound Multiframe (retired) 1.2.840.10008.5.1.4.1.1.3 See below SCU None Extended Negotiation 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 8
Ultrasound Multiframe 1.2.840.10008.5.1.4.1.1.3.1 See below SCU None MR 1.2.840.10008.5.1.4.1.1.4 See below SCU None Nuclear Medicine (retired) 1.2.840.10008.5.1.4.1.1.5 See below SCU None Ultrasound (retired) 1.2.840.10008.5.1.4.1.1.6 See below SCU None Ultrasound 1.2.840.10008.5.1.4.1.1.6.1 See below SCU None Secondary Capture 1.2.840.10008.5.1.4.1.1.7 See below SCU None Stand alone Overlay 1.2.840.10008.5.1.4.1.1.8 See below SCU None Stand alone Curve 1.2.840.10008.5.1.4.1.1.9 See below SCU None 12 lead ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.1 See below SCU None General ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.2 See below SCU None Ambulatory ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.3 See below SCU None Hemodynamic Waveform 1.2.840.10008.5.1.4.1.1.9.2.1 See below SCU None Cardiac Electrophysiology Waveform 1.2.840.10008.5.1.4.1.1.9.3.1 See below SCU None Basic Voice Audio Wave form 1.2.840.10008.5.1.4.1.1.9.4.1 See below SCU None Stand alone Modality LUT 1.2.840.10008.5.1.4.1.1.10 See below SCU None Grayscale Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.1 See below SCU None Stand alone VOI LUT 1.2.840.10008.5.1.4.1.1.11 See below SCU None Xray Angiographic 1.2.840.10008.5.1.4.1.1.12.1 See below SCU None Xray Radiofluoroscopic 1.2.840.10008.5.1.4.1.1.12.2 See below SCU None Xray Angiographic BiPlane 1.2.840.10008.5.1.4.1.1.12.3 See below SCU None Nuclear Medicine 1.2.840.10008.5.1.4.1.1.20 See below SCU None VL Endoscopic 1.2.840.10008.5.1.4.1.1.77.1.1 See below SCU None VL Microscopic 1.2.840.10008.5.1.4.1.1.77.1.2 See below SCU None VL Slide Coordinates Microscopic 1.2.840.10008.5.1.4.1.1.77.1.3 See below SCU None VL Photographic 1.2.840.10008.5.1.4.1.1.77.1.4 See below SCU None Basic Text SR 1.2.840.10008.5.1.4.1.1.88.11 See below SCU None Enhanced SR 1.2.840.10008.5.1.4.1.1.88.22 See below SCU None Comprehensive SR 1.2.840.10008.5.1.4.1.1.88.33 See below SCU None Positron Emission Tomography 1.2.840.10008.5.1.4.1.1.128 See below SCU None Standalone PET Curve 1.2.840.10008.5.1.4.1.1.129 See below SCU None RT 1.2.840.10008.5.1.4.1.1.481.1 See below SCU None RT Dose 1.2.840.10008.5.1.4.1.1.481.2 See below SCU None RT Structure Set 1.2.840.10008.5.1.4.1.1.481.3 See below SCU None RT Beams Treatment Record 1.2.840.10008.5.1.4.1.1.481.4 See below SCU None RT Plan 1.2.840.10008.5.1.4.1.1.481.5 See below SCU None RT Brachy Treatment Record 1.2.840.10008.5.1.4.1.1.481.6 See below SCU None RT Treatment Summary Record 1.2.840.10008.5.1.4.1.1.481.7 See below SCU None Table 3.2.3. Proposed Presentation Contexts for AE Send Transfer Syntaxes Name UID Implicit VR, Little Endian 1.2.840.10008.1.2 Explicit VR, Little Endian 1.2.840.10008.1.2.1 JPEGExtended 1.2.840.10008.1.2.4.51 JPEG Lossles, NH, Process 14 1.2.840.10008.1.2.4.57 JPEG Lossless, NH, FOP, Process 14 1.2.840.10008.1.2.4.70 JPEG 2000 Image Compression Lossless 1.2.840.10008.1.2.4.90 JPEG 2000 Image Compression 1.2.840.10008.1.2.4.91 RLE Lossless 1.2.840.10008.1.2.5 Table 3.2.4. Transfer Syntaxes for AE Send 3.2.2.4 Specific Conformance for SOP Class Service Status Further Meaning Error Code Behaviour Success Sub-operations complete-no Failures 0000 The send panel hides, logs are updated. Refused Out of Resources - A701 Unable to calculate number of matches Out of Resources - A702 Refused Unable to perform suboperations Refused A801 Failed Identifier Does Not A900 Match SOP Class Failed Unable to process Cxxx 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 9
Warning Pending Sub Operations Complete - One or more Failures Sub Operations are continuing B000 FF00 Table 3.2.5. DICOM command response status handling behavior Exception Timeout Aborted Behavior The user is informed there has been a communication error The user aborts the operation, the association is aborted. 3.2.2.5 Association Acceptance Policy PACSMail accepts connections from all AE titles. Table 3.2.6 DICOM command communication failure behavior 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 10
3.3 Application Entity Query Retrieve This is the detailed specification for the Query Retrieve AE for PACSMail. 3.3.1 SOP Classes This Application Entity provides Standard Conformance to the following SOP Classes: See Table 3.3.3 Note: Any SOP specific behavior is documented later in the conformance statement in the applicable SOP specific conformance section. 3.3.2 Association Policies 3.3.2.1 Number of Associations. Maximum number of simultaneous associations 1 Table 3.3.1. Number of associations as an association initiator for AE Query Retrieve Maximum number of simultaneous associations 1 Table 3.3.2. Number of associations as an association acceptor for AE Query Retrieve 3.3.2.2 Asynchronous Nature Does not apply 3.3.2.3 Association Initiation Policy 3.3.2.3.1 User Initiates a Query AE 3.3.2.3.1.1 Description and Sequencing of Activities The user initiates a Query command to a defined Application Entity. The Application Entity titles and details are set in the PACSMail address book. When the AE has been set up the user can click the Retrieve button in the Xray module. The user can then select Date of Birth, Surname and Firstname, or Patient Number. Clicking the Search button start the query process with the chosen AET. 3.3.2.3.1.2 Proposed Presentation Contexts Each time an association is initiated, the Association Initiator proposes a number of Presentation Contexts to be used on that association. In this subsection, the Presentation Contexts proposed by Query shall be defined in a table with the following format: Proposed Presentation Contexts Patient Root Query/Retrieve Information Model C-FIND Study Root Query/Retrieve Information Model C-Find Presentation Context Table Abstract Syntax Transfer Role Extended Syntax Negotiation 1.2.840.10008.5.1.4.1.2.1.1 See below SCU None 1.2.840.10008.5.1.4.1.2.2.1 See below SCU None Table 3.3.3. Proposed presentation contexts for AE Query 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 11
Transfer Syntaxes Name UID Implicit VR, Little Endian 1.2.840.10008.1.2 Explicit VR, Little Endian 1.2.840.10008.1.2.1 3.3.2.4 Specific Conformance for SOP Class(es) Table 3.3.4. Transfer Syntaxes for AE Send Service Status Further Meaning Error Code Behaviour Success Sub-operations complete-no Failures 0000 The send panel hides, logs are updated. Refused Out of Resources - A701 Unable to calculate number of matches Out of Resources - A702 Refused Unable to perform suboperations Refused A801 Failed Identifier Does Not A900 Match SOP Class Failed Unable to process Cxxx Warning Sub Operations B000 Complete - One or more Failures Pending Sub Operations are continuing FF00 Table 3.3.5. DICOM command response status handling behavior Exception Timeout Aborted Behavior The user is informed there has been a communication error The user aborts the operation, the association is aborted. Table 3.3.6. DICOM command communication failure behavior 3.3.2.4.1 User Initiates a Get Images AE 3.3.2.4.1.1 Description and Sequencing of Activities The user initiates a Get Images command to a defined Application Entity. The Application Entity titles and details are set in the PACSMail address book. The user chooses which images to download then clicks the Get Images button. 3.3.2.4.1.2 Proposed Presentation Contexts Each time an association is initiated, the Association Initiator proposes a number of Presentation Contexts to be used on that association. In this subsection, the Presentation Contexts proposed by Query shall be defined in a table with the following format: Proposed Presentation Contexts Patient Root Query/Retrieve Information Model C-Move Study Root Query/Retrieve Information Model C-MOVE Presentation Context Table Abstract Syntax Transfer Role Extended Syntax Negotiation 1.2.840.10008.5.1.4.1.2.1.2 See below SCU None 1.2.840.10008.5.1.4.1.2.2.2 See below SCU None Table 3.3.7. Proposed Presentation Contexts for AE Query. 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 12
Transfer Syntaxes Name UID Implicit VR, Little Endian 1.2.840.10008.1.2 Explicit VR, Little Endian 1.2.840.10008.1.2.1 JPEGExtended 1.2.840.10008.1.2.4.51 JPEG Lossles, NH, Process 14 1.2.840.10008.1.2.4.57 JPEG Lossless, NH, FOP, Process 14 1.2.840.10008.1.2.4.70 JPEG 2000 Image Compression Lossless 1.2.840.10008.1.2.4.90 JPEG 2000 Image Compression 1.2.840.10008.1.2.4.91 RLE Lossless 1.2.840.10008.1.2.5 3.3.2.5 Specific Conformance for SOP Class(es) Table 3.3.8. Transfer Syntaxes for AE Query. Service Status Further Meaning Error Code Behaviour Success Sub-operations complete-no Failures 0000 The send panel hides, logs are updated. Refused Out of Resources - A701 Unable to calculate number of matches Out of Resources - A702 Refused Unable to perform suboperations Refused A801 Failed Identifier Does Not A900 Match SOP Class Failed Unable to process Cxxx Warning Sub Operations B000 Complete - One or more Failures Pending Sub Operations are continuing FF00 Table 3.3.9. DICOM command response status handling behavior Exception Timeout Aborted Behavior The user is informed there has been a communication error The user aborts the operation, the association is aborted. Table 3.3.10. DICOM command communication failure behavior 3.3.2.5.1 User Initiated C-Store after a C-Move request See the section on C-Store as SCP 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 13
3.4 Application Entity Storage as SCP This is the detailed specification for the Storage AE for PACSMail. 3.4.1 SOP Classes This Application Entity provides Standard Conformance to the following SOP Classes: See Table 3.4.3 Note: Any SOP specific behavior is documented later in the conformance statement in the applicable SOP specific conformance section. 3.4.2 Association Policies 3.4.2.1 Number of Associations. Maximum number of simultaneous associations 1 Table 3.4.1. Number of associations as an association initiator for AE Storage Maximum number of simultaneous associations 1 Table 3.4.2. Number of associations as an association acceptor for AE Storage 3.4.2.2 Asynchronous Nature Does not apply 3.4.2.3 Association Initiation Policy 3.4.2.3.1 Incoming C-Store request from remote AE 3.4.2.3.1.1 Description and Sequencing of Activities A remote application wants to send image data to PACSMail. This occurs either after a C-Move request has been manually initiated or the remote AE sends unsolicited data to a PACSMail service. 3.4.2.3.1.2 Proposed Presentation Contexts Each time an association is initiated, the Association Initiator proposes a number of Presentation Contexts to be used on that association. In this subsection, the Presentation Contexts proposed by storage when receiving images shall be defined in a table with the following format: Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Role Syntax Computed Radiography 1.2.840.10008.5.1.4.1.1.1 See below SCP None Digital Xray Presentation 1.2.840.10008.5.1.4.1.1.1.1 See below SCP None Digital Xray Processing 1.2.840.10008.5.1.4.1.1.1.1.1 See below SCP None Digital Mammography Xray Presentation 1.2.840.10008.5.1.4.1.1.1.2 See below SCP None Digital Mammography Xray Processing 1.2.840.10008.5.1.4.1.1.1.2.1 See below SCP None Digital Intraoral XRay Presentation 1.2.840.10008.5.1.4.1.1.1.3 See below SCP None Digital Intraoral XRay Processing 1.2.840.10008.5.1.4.1.1.1.3.1 See below SCP None CT 1.2.840.10008.5.1.4.1.1.2 See below SCP None Ultrasound Multiframe (retired) 1.2.840.10008.5.1.4.1.1.3 See below SCP None Ultrasound Multiframe 1.2.840.10008.5.1.4.1.1.3.1 See below SCP None MR 1.2.840.10008.5.1.4.1.1.4 See below SCP None Nuclear Medicine (retired) 1.2.840.10008.5.1.4.1.1.5 See below SCP None Ultrasound (retired) 1.2.840.10008.5.1.4.1.1.6 See below SCP None Extended Negotiation 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 14
Ultrasound 1.2.840.10008.5.1.4.1.1.6.1 See below SCP None Secondary Capture 1.2.840.10008.5.1.4.1.1.7 See below SCP None Stand alone Overlay 1.2.840.10008.5.1.4.1.1.8 See below SCP None Stand alone Curve 1.2.840.10008.5.1.4.1.1.9 See below SCP None 12 lead ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.1 See below SCP None General ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.2 See below SCP None Ambulatory ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.3 See below SCP None Hemodynamic Waveform 1.2.840.10008.5.1.4.1.1.9.2.1 See below SCP None Cardiac Electrophysiology Waveform 1.2.840.10008.5.1.4.1.1.9.3.1 See below SCP None Basic Voice Audio Wave form 1.2.840.10008.5.1.4.1.1.9.4.1 See below SCP None Stand alone Modality LUT 1.2.840.10008.5.1.4.1.1.10 See below SCP None Grayscale Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.1 See below SCP None Stand alone VOI LUT 1.2.840.10008.5.1.4.1.1.11 See below SCP None Xray Angiographic 1.2.840.10008.5.1.4.1.1.12.1 See below SCP None Xray Radiofluoroscopic 1.2.840.10008.5.1.4.1.1.12.2 See below SCP None Xray Angiographic BiPlane 1.2.840.10008.5.1.4.1.1.12.3 See below SCP None Nuclear Medicine 1.2.840.10008.5.1.4.1.1.20 See below SCP None VL Endoscopic 1.2.840.10008.5.1.4.1.1.77.1.1 See below SCP None VL Microscopic 1.2.840.10008.5.1.4.1.1.77.1.2 See below SCP None VL Slide Coordinates Microscopic 1.2.840.10008.5.1.4.1.1.77.1.3 See below SCP None VL Photographic 1.2.840.10008.5.1.4.1.1.77.1.4 See below SCP None Basic Text SR 1.2.840.10008.5.1.4.1.1.88.11 See below SCP None Enhanced SR 1.2.840.10008.5.1.4.1.1.88.22 See below SCP None Comprehensive SR 1.2.840.10008.5.1.4.1.1.88.33 See below SCP None Positron Emission Tomography 1.2.840.10008.5.1.4.1.1.128 See below SCP None Standalone PET Curve 1.2.840.10008.5.1.4.1.1.129 See below SCP None RT 1.2.840.10008.5.1.4.1.1.481.1 See below SCP None RT Dose 1.2.840.10008.5.1.4.1.1.481.2 See below SCP None RT Structure Set 1.2.840.10008.5.1.4.1.1.481.3 See below SCP None RT Beams Treatment Record 1.2.840.10008.5.1.4.1.1.481.4 See below SCP None RT Plan 1.2.840.10008.5.1.4.1.1.481.5 See below SCP None RT Brachy Treatment Record 1.2.840.10008.5.1.4.1.1.481.6 See below SCP None RT Treatment Summary Record 1.2.840.10008.5.1.4.1.1.481.7 See below SCP None Table 3.4.3. Proposed Presentation Contexts for C-Store as SCP Transfer Syntaxes Name UID Implicit VR, Little Endian 1.2.840.10008.1.2 Explicit VR, Little Endian 1.2.840.10008.1.2.1 JPEGExtended 1.2.840.10008.1.2.4.51 JPEG Lossles, NH, Process 14 1.2.840.10008.1.2.4.57 JPEG Lossless, NH, FOP, Process 14 1.2.840.10008.1.2.4.70 JPEG 2000 Image Compression Lossless 1.2.840.10008.1.2.4.90 JPEG 2000 Image Compression 1.2.840.10008.1.2.4.91 RLE Lossless 1.2.840.10008.1.2.5 Table 3.4.4. Transfer Syntaxes for C-Store SCP 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 15
3.4.2.4 Specific Conformance for SOP Class(es) Service Status Further Meaning Error Code Behaviour Success Sub-operations complete-no Failures 0000 The send panel hides, logs are updated. Refused Out of Resources - A701 Unable to calculate number of matches Out of Resources - A702 Refused Unable to perform suboperations Refused A801 Failed Identifier Does Not A900 Match SOP Class Failed Unable to process Cxxx Warning Sub Operations B000 Complete - One or more Failures Pending Sub Operations are continuing FF00 Table 3.4.5. DICOM command response status handling behavior Exception Timeout Aborted Behavior The user is informed there has been a communication error The user aborts the operation, the association is aborted. Table 3.4.6. DICOM command communication failure behavior 3.4.2.5 Association Acceptance Policy PACSMail accepts all connections from all AE titles. 3.5 Application Entity Listen This is the detailed specification for the Manual Listen AE for PACSMail. The user clicks the Listen option in the PACSMail Xray panel. The workstation will now be listening for incoming DICOM Data. The specification is the same as the manual listen entry, see section 3.4. 3.6 Application Entity Auto Listen This is the detailed specification for the Auto Listen AE for PACSMail. Auto Listen is a windows service that is configured to listen for incoming DICOM data and store images to a defined disk storage area. The specification is the same as the manual listen entry, see section 3.5 except that the service is always on and no manual intervention is required. 3.7 Application Entity Auto Send This is the detailed specification for the Auto Send AE for PACSMail. Auto Send is a windows service that is configured to send DICOM data to a remote AET. The specification is the same as the manual send entry, see section 3.2 except that the service is always on and no manual intervention is required. 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 16
4 Communication Profiles 3.1. Supported Communications Stacks (Part 8) PACSMail V2.0 provides DICOM V3.0 TCP/IP Network Communication Support as defined in PS 3.8. 3.2. TCP/IP Stack PACSMail V2.0 inherits its TCP/IP stack from the Windows system upon which it executes. 3.3. Physical Media Support Not Applicable. 5 Extensions/Specializations/Privatizations No Extensions, Specializations or Privatizations are used. 6 Configuration PACSMail client application is configured via the address book wizard. This allows the user to configure DICOM connections with the following parameters: PACSMail AE Title IP Address Port Number Remote AET AE Title IP Address Port Number PACSMail Services are configured via configuration file. 7 Support of Extended Character Sets PACSMail does not itself use any extended character sets, but stores and passes any received through unchanged. Document Ends. 01_05DICOM CONFORMANCE STATEMENT PACSMAIL V01.DOC 17