DICOM Conformance Statement. isite PACS 3.6. CREF Apr Philips Medical Systems Radiology Informatics

Transcription

1 DICOM Conformance Statement isite PACS 3.6 CREF Apr Philips Medical Systems Radiology Informatics

2 Radiology Informatics DICOM Conformance Statement isite PACS 3.6 CREF Apr Philips Healthcare is part of Royal Philips Electronics North America Philips Healthcare Informatics Radiology Informatics Business Unit 4100 East Third Ave., Suite 101 Foster City, CA USA Europe Philips Medical Systems Nederland B.V. PMS Quality & Regulatory Affairs Europe Veenpluis PC Best The Netherlands Copyright 2007 Koninklijke Philips Electronics N.V. All rights reserved. isite and i are registered trademarks of Koninklijke Philips Electronics N.V. TMP Jan 28

3 Table of Contents 1 Introduction Abbreviations and Symbols Implementation Model Application Data Flow Diagram Functional Definitions of AEs Sequencing of Real-World Activities AE Specifications isite DICOM Server AE Specification Association Establishment Policies Association Initiation by Real-World Activity Association Acceptance Policy isite DICOM QRSCP AE Specification Association Establishment Policies Association Initiation by Real-World Activity Association acceptance policy isite Worklist Server AE Specification Association Establishment Policies Association Initiation by Real-World Activity Association Acceptance Policy isite Radiology Client AE Specification Association Establishment Policies Association Initiation by Real-World Activity Association Acceptance Policy Communication Profiles Supported Communication Stacks (Parts 8,9) TCP/IP Stack API Physical Media Support Extensions/Specializations/Privatizations Standard Extended/Specialized/Private SOPs Private Transfer es CREF Apr Page i

4 7 Configuration Support of Extended Character Sets Codes and Controlled Terminology Security Profiles CREF Apr Page ii

5 1 Introduction The Philips isite Picture Archiving and Communication System (PACS) product is a medical image and information distribution system designed for integration into a medical institution s existing healthcare network. The product utilizes the medical industry standard DICOM 3.0 protocol to exchange information with other DICOM compliant devices on the network. The primary use of the DICOM protocol within the isite product is for local and remote storage of images, remote printing of images, remote query of image storage related information and local query of modality worklist information. 2 Abbreviations and Symbols Frequently used abbreviations or acronyms in this document are defined in the table below. All other abbreviations are defined at its first use in this document by the abbreviation followed by its full meaning enclosed in parentheses. Term AE API CT DICOM HIS RIS MR MWS PDU QRSCP RLE RT SCP SCU SOP TCP/IP Meaning Application Entity Application Programming Interface Computed Tomography Digital Imaging and Communications in Medicine Hospital Information System Radiology Information System Magnetic Resonance Modality Worklist Server Protocol Data Unit Query/Retrieve Service Class Provider Run Length Encoded Radiotherapy Service Class Provider Service Class User Service Object Pair Transmission Control Protocol/Internet Protocol CREF Apr Page 3

6 Term UID VR Meaning Unique Identifier Value Representation 3 Implementation Model The isite system consists of integrated client and server applications within the Philips product line. This system provides DICOM compliant interfaces for, Verification, Query/Retrieve, Printing and Modality Worklist services. 3.1 Application Data Flow Diagram The isite DICOM Server, isite Worklist Server, and isite Radiology Client Application Entities are all integrated parts of the isite product. DICOM Standard Interface Im age Converted and Stored at N o rm a l P rio rity Remote System Requests C o m m itm e n t Im age Converted and Stored at High Priority is ite C lie n t Q u e rie s Remote DICOM Device isite DICOM Server Performs Prefetch O p e ra tio n is ite C lie n t Request R e m o te Im a g e is ite D IC O M S e rv e r Remote System Requests MPPS Remote System Requests N orm a l P riority Im age Remote System R equests High P rio rity Im a g e Remote System Responds to DICOM Query/ Retrieve Requests Im age Stored on Rem ote DICOM System DICOM Service Verified is ite W o rklist S e rver Remote System Requests DICOM Verification Service is ite D a ta b a s e Q u e rie d fo r W o rk lis t D a ta Remote System Requests D ic o m M o d a lity W o rk lis t User Requests DICOM Printing isite Radiology Client Remote System Prints DICOM Im ages CREF Apr Page 4

7 3.2 Functional Definitions of AEs The isite DICOM Server can both initiate and receive DICOM association requests. It runs as a Windows 2003 Server service and will automatically be started as part of the operating system. Once started, the isite DICOM Server will wait for another application to connect to its DICOM service at the presentation address configured for it s high and low priority Application Entity Titles. isite client applications also have the ability to initiate DICOM associations by the isite DICOM Server to remote DICOM devices for and Query/Retrieve services. The isite Worklist Server runs as a Windows 2003 Server service and will be automatically started as part of the operating system. Once started, the isite Worklist Server will wait for another application to connect to it DICOM Modality Worklist service at the presentation address configured. The isite Radiology Client will initiate DICOM associations for DICOM Printing services on an as needed basis dependent upon interactive requests from users of the system. 3.3 Sequencing of Real-World Activities Not Applicable. 4 AE Specifications 4.1 isite DICOM Server AE Specification The isite DICOM Server AE provides standard conformance to the following DICOM V3.0 SOP class in the roles specified: Table 1: isite DICOM Server AE Standard Conformance SOP Class Name SOP Class UID Role Verification SOP Class SCP Commitment Push Model SOP Class SCP Modality Performed Procedure Step SOP Class SCP Stored Print SCU Hardcopy Grayscale SCU,SCP Harcopy Color SCU,SCP Computed Radiography SCU,SCP Digital X-Ray - For Presentation SCU,SCP Digital X-Ray - For Processing SCU,SCP Digital Mammography - For Presentation SCU,SCP Digital Mammography - For Processing SCU,SCP Digital Intra-oral X-Ray - For Presentation SCU,SCP CREF Apr Page 5

8 SOP Class Name SOP Class UID Role Digital Intra-oral X-Ray - For Processing SCU,SCP Standalone Modality LUT SCU,SCP Standalone VOI LUT SCU,SCP Grayscale Softcopy Presentation State SOP Class SCU,SCP X-Ray Angiographic SCU,SCP X-Ray Radiofluoroscopic SCU,SCP X-Ray Angiographic Bi-Plane SCU,SCP Positron Emission Tomography SCU,SCP Standalone PET Curve SCU,SCP CT SCU,SCP Nuclear Medicine SCU,SCP Ultrasound Multi-Frame (Retired) SCU,SCP Ultrasound Multi-Frame SCU,SCP MR SCU,SCP Enhance MR SCU,SCP MR Spectroscopy SCU,SCP RT SCU,SCP RT Dose SCU,SCP RT Structure Set SCU,SCP RT Beams Treatment Record SCU,SCP RT Plan SCU,SCP RT Brachy Treatment Record SCU,SCP RT Treatment Summary Record SCU,SCP Nuclear Medicine (Retired) SCU,SCP Ultrasound (Retired) SCU,SCP Ultrasound SCU,SCP Raw Data SCU,SCP Secondary Capture SCU,SCP Multi-frame Single Bit Secondary Capture SCU,SCP Multi-frame Grayscale Byte SC SCU,SCP Multi-frame Grayscale Word Secondary Capture SCU,SCP Mulfi-frame True Color Secondary Capture SCU,SCP VL Endoscopic SCU,SCP VL Microscopic SCU,SCP CREF Apr Page 6

9 SOP Class Name SOP Class UID Role VL Slide-Coordinates Microscopic SCU,SCP VL Photographic SCU,SCP Standalone Overlay SCU,SCP Basic Text Structured Reporting SOP Class SCU,SCP Enhanced Structured Reporting SOP Class SCU,SCP Comprehensive Structured Reporting SOP Class SCU,SCP Mammography CAD SR SOP Class SCU,SCP Key Object Selection Document SCU,SCP Chest CAD SR SCU,SCP Standalone Curve SCU,SCP 12-lead ECG Waveform SCU,SCP General ECG Waveform SCU,SCP Ambulatory ECG Waveform SCU,SCP Hemodynamic Waveform SCU,SCP Cardiac Electrophysiology Waveform SCU,SCP Basic Voice Audio Waveform SCU,SCP Patient Root Query/Retrieve Information Model - FIND SCU,SCP Patient Root Query/Retrieve Information Model - MOVE SCU,SCP Study Root Query/Retrieve Information Model - FIND SCU,SCP Study Root Query/Retrieve Information Model - MOVE SCU,SCP Patient/Study Only Query/Retrieve Information Model - FIND SCU,SCP Patient/Study Only Query/Retrieve Information Model - MOVE SCU,SCP GE Nuclear Medicine private SOP Class SCU,SCP Philips Private Gyroscan MR Spectrum SCU,SCP Philips Private Gyroscan MR Serie Data SCU,SCP Philips Private Specialized XA SCU,SCP Philips Private CX SCU,SCP Philips ie33 private 3D Object SCU,SCP Philips Private Volume SCU,SCP Philips Private Volume Reference SCU,SCP Philips Private MR Synthetic SCU,SCP Philips Private MR Cardio Analysis SCU,SCP Philips Private MR Cardio Analysis Data SCU,SCP Philips Private CX Synthetic SCU,SCP CREF Apr Page 7

10 SOP Class Name SOP Class UID Role Philips Private Perfusion Reference SCU,SCP Philips Private Perfusion Analysis Data SCU,SCP Philips Private 3D Object SCU,SCP Philips Private 3D Object SCU,SCP Philips Private Surface SCU,SCP Philips Private Surface SCU,SCP Philips Private Composite Object SCU,SCP Philips Private MR Cardio Profile SCU,SCP Philips Private MR Cardio SCU,SCP Philips Private CT Synthetic SCU,SCP Association Establishment Policies General The isite DICOM Server application will request associations and accept associations for DICOM and Query/Retrieve. The isite DICOM Server application supports a maximum PDU size of 63KB Number of Associations The isite DICOM Server application supports the initiation of a configurable number of simultaneous associations. The default is 3 for Service related transactions and 1 for Query/Retrieve Service related transactions. The isite DICOM Server application has no configurable upper limit on the number of simultaneous associations that it will accept. The upper limit of accepted associations is limited by the hardware platform and overall system performance requirements Asynchronous Nature The isite DICOM Server application does not support negotiation of multiple outstanding transactions Implementation Identifying Information The isite DICOM Server uses the following implementation identifying information. Table 2: isite DICOM Server Implementation Identifying Information Implementation Class UID CREF Apr Page 8

11 4.1.2 Association Initiation by Real-World Activity Real World Activity isite Client Queries Remote DICOM Device Associated Real-World Activity isite client applications use the iquery tool of the isite DICOM Server to initiate and manage DICOM associations with remote Application Entities that support the DICOM Query/Retrieve Service as a Service Class Provider. The iquery tool allows isite client applications to interact with the isite DICOM Server via a proprietary interface. The isite DICOM Server s iquery tool is an interactive enduser application and will generate DICOM transactions based upon end-user initiated activities Proposed Presentation Contexts Table 3: Proposed Presentation Contexts for isite DICOM Server and Real-World Activity isite Client Queries Remote DICOM Device Abstract Transfer Name UID Name List UID List Role Extended Negotiation Patient Root Query/Retrieve Information Model - FIND Patient Root Query/Retrieve Information Model - MOVE Study Root Query/Retrieve Information Model - FIND CREF Apr Page 9

12 Abstract Transfer Name UID Name List UID List Role Extended Negotiation Study Root Query/Retrieve Information Model - MOVE Patient/Study Only Query/Retrieve Information Model - FIND Patient/Study Only Query/Retrieve Information Model - MOVE SOP Specific Conformance Statement for SOP Class 'Patient Root Query/Retrieve Information Model - FIND' All DICOM attributes specified as valid keys for C-FIND messages are legal for Philips isite Server query keys as well. In practice, the set actually used is defined by client-side requests so only a pertinent subset would be used. Table 4 lists the essential tags that Philips isite Server will expect any Query/Retrieve SCP to support for the Patient Root Information Model. Table 4: DICOM data elements supported for SOP Class 'Patient Root Query/Retrieve Information Model - FIND' Level Description Tag Type Patient Patient s Name (0010,0010) R Patient Patient ID (0010,0020) U Study Study ID (0020,0010) R CREF Apr Page 10

13 Level Description Tag Type Study Study Instance UID (0020,000D) U Study Study Date (0020,0020) R Study Study Time (0020,0030) R Study Accession Number (0008,0050) R Study Referring Physician (0008,0090) O Study Study Description (0008,1030) O Series Modality (0008,0060) R Series Series Number (0020,0011) R Series Body Part Examined (0018,0015) O Series Series Instance UID (0020,000E) U SOP Specific Conformance Statement for SOP Class Study Root Query/Retrieve Information Model FIND" All DICOM attributes specified as valid keys for C-FIND messages are legal for Philips isite Server query keys as well. In practice, the set actually used is defined by client-side requests so only a pertinent subset would be used. Table 5 lists the essential tags that Philips isite Server will expect any Query/Retrieve SCP to support for the Study Root Information Model. Table 5: DICOM data elements supported for SOP Class Study Root Query/Retrieve Information Model - FIND' Level Description Tag Type Study Patient s Name (0010,0010) R Study Patient ID (0010,0020) U Study Study ID (0020,0010) R Study Study Instance UID (0020,000D) U Study Study Date (0020,0020) R Study Study Time (0020,0030) R Study Accession Number (0008,0050) R Study Referring Physician (0008,0090) O Study Study Description (0008,1030) O Series Modality (0008,0060) R CREF Apr Page 11

14 Level Description Tag Type Series Series Number (0020,0011) R Series Body Part Examined (0018,0015) O Series Series Instance UID (0020,000E) U SOP Specific Conformance Statement for SOP Class Patient/Study Only Query/Retrieve Information Model FIND" All DICOM attributes specified as valid keys for C-FIND messages are legal for Philips isite Server query keys as well. In practice the set actually used is defined by client-side requests so only a pertinent subset would be used. Table 6 lists the essential tags that Philips isite Server will expect any Query/Retrieve SCP to support for the Patient/Study Only Information Model. Table 6: DICOM data elements supported for SOP Class 'Patient Study Only Query/Retrieve Information Model - FIND' Level Description Tag Type Patient Patient s Name (0010,0010) R Patient Patient ID (0010,0020) U Study Study Date (0020,0020) R Study Study Time (0020,0030) R Study Accession Number (0008,0050) R Study Referring Physician (0008,0090) O Study Study Description (0008,1030) O Study Study ID (0020,0010) R Study Study Instance UID (0020,000D) U Real World Activity isite Client Requests Remote Associated Real-World Activity isite client applications use the iexport tool of the isite DICOM Server to initiate and manage DICOM associations with remote Application Entities that support the DICOM Service as a Service Class Provider. The iexport tool allows isite client applications to interact with the isite DICOM Server via a proprietary interface. The isite DICOM Server s iexport tool is an interactive end-user application and will generate DICOM transactions based upon end-user initiated activities. CREF Apr Page 12

15 Proposed Presentation Contexts Table 7: Proposed Presentation Contexts for isite DICOM Server and Real-World Activity isite Client Requests Remote Abstract Transfer Name UID Name List UID List Role Extended Negotiation Hardcopy Grayscale Hardcopy Color Computed Radiography Digital X-Ray - For Presentation Digital X-Ray - For Processing CREF Apr Page 13

16 Digital Mammography - For Presentation Digital Mammography - For Processing Digital Intra-oral X- Ray - For Presentation Digital Intra-oral X- Ray - For Processing Standalone Modality LUT CREF Apr Page 14

17 Standalone VOI LUT Grayscale Softcopy Presentation State (GSPS) SOP Class X-Ray Angiographic X-Ray Radiofluoroscopic X-Ray Angiographic Bi-Plane CREF Apr Page 15

18 Positron Emission Tomography Standalone PET Curve CT Nuclear Medicine Ultrasound Multi- Frame (Retired) Ultrasound Multi- Frame CREF Apr Page 16

19 MR Enhance MR MR Spectroscopy RT RT Dose CREF Apr Page 17

20 RT Structure Set RT Beams Treatment Record RT Plan RT Brachy Treatment Record RT Treatment Summary Record CREF Apr Page 18

21 Nuclear Medicine (Retired) Ultrasound (Retired) Ultrasound Raw Data Secondary Capture Multi-frame Single Bit Secondary Capture CREF Apr Page 19

22 Multi-frame True Color Secondary Capture VL Endoscopic VL Microscopic VL Slide- Coordinates Microscopic VL Photographic CREF Apr Page 20

23 Standalone Overlay Basic Text Structured Reporting SOP Class Enhanced Structured Reporting SOP Class Comprehensive Structured Reporting SOP Class Mammography CAD SR SOP Class CREF Apr Page 21

24 Key Object Selection Document Chest CAD SR Standalone Curve lead ECG Waveform General ECG Waveform Ambulatory ECG Waveform CREF Apr Page 22

25 Hemodynamic Waveform Cardiac Electrophysiology Waveform Basic Voice Audio Waveform GE Nuclear Medicine private SOP Class Philips Private Gyroscan MR Spectrum CREF Apr Page 23

26 Philips Private Gyroscan MR Series Data Philips Private Specialized XA Philips Private CX Philips Private ie33 3D Object Philips Private Volume CREF Apr Page 24

27 Philips Private Volume Reference Philips Private 3D Object Philips Private 3D Object Philips Private Surface Philips Private Surface Philips Private Composite Object CREF Apr Page 25

28 Philips Private MR Cardio Profile Philips Private MR Cardio Philips Private CT Synthetic Philips Private MR Synthetic Philips Private MR Cardio Analysis CREF Apr Page 26

29 Philips Private MR Cardio Analysis Data Philips Private CX Synthetic Philips Private Perfusion Reference Philips Private Perfusion Analysis Data CREF Apr Page 27

30 4.1.3 Association Acceptance Policy Real World Activity Remote System Requests Normal Priority Associated Real-World Activity The isite DICOM Server will accept DICOM Service association request that are initiated by remote DICOM entities. The isite DICOM Server will process the stored DICOM images and make them available for access by isite client applications Accepted Presentation Contexts Table 8: Accepted Presentation Contexts for isite DICOM Server and Real-World Activity Remote System Request Normal Priority Abstract Transfer Name UID Name List UID List Role Extended Negotiation Stored Print Transfer, CREF Apr Page 28

31 Hardcopy Grayscale Transfer, Hardcopy Color CREF Apr Page 29

32 Transfer, Computed Radiography Transfer CREF Apr Page 30

33 , Digital X-Ray - For Presentation Transfer, Digital X-Ray - For Processing CREF Apr Page 31

34 Transfer, Digital Mammography - For Presentation Transfer CREF Apr Page 32

35 , Digital Mammography - For Processing Transfer, CREF Apr Page 33

36 Digital Intra-oral X-Ray - For Presentation Transfer, Digital Intra-oral X-Ray - For Processing CREF Apr Page 34

37 Transfer Standalone Modality LUT Transfer, CREF Apr Page 35

38 Standalone VOI LUT Transfer, Grayscale Softcopy Presentation State (GSPS) SOP Class CREF Apr Page 36

39 Transfer, X-Ray Angiographic Transfer, CREF Apr Page 37

40 X-Ray Radiofluoroscopic Transfer, X-Ray Angiographic Bi- Plane CREF Apr Page 38

41 Transfer, Positron Emission Tomography Transfer CREF Apr Page 39

42 , Standalone PET Curve Transfer, CT CREF Apr Page 40

43 Transfer, Nuclear Medicine Transfer CREF Apr Page 41

44 , Ultrasound Multi- Frame (Retired) Transfer, CREF Apr Page 42

45 Ultrasound Multi- Frame Transfer, MR CREF Apr Page 43

46 Transfer, Enhance MR Transfer, CREF Apr Page 44

47 MR Spectroscopy Transfer, RT CREF Apr Page 45

48 RT Dose Transfer, Transfer CREF Apr Page 46

49 , RT Structure Set Transfer, RT Beams Treatment Record CREF Apr Page 47

50 RT Plan Transfer, Transfer CREF Apr Page 48

51 , RT Brachy Treatment Record Transfer, CREF Apr Page 49

52 RT Treatment Summary Record Transfer, Nuclear Medicine (Retired) CREF Apr Page 50

53 Transfer, Ultrasound (Retired) Transfer, CREF Apr Page 51

54 Ultrasound Transfer, Raw Data CREF Apr Page 52

55 Transfer, Secondary Capture Transfer CREF Apr Page 53

56 , Multi-frame Single Bit Secondary Capture Multi-frame Grayscale Byte Secondary Capture Transfer, CREF Apr Page 54

57 Multi-frame Grayscale Word Secondary Capture Transfer, Multi-frame True Color Secondary Capture CREF Apr Page 55

58 Transfer, VL Endoscopic Transfer CREF Apr Page 56

59 , VL Microscopic Transfer, VL Slide- Coordinates Microscopic CREF Apr Page 57

60 Transfer, VL Photographic Transfer CREF Apr Page 58

61 , Standalone Overlay Transfer, CREF Apr Page 59

62 Basic Text Structured Reporting SOP Class Transfer, Enhanced Structured Reporting SOP Class CREF Apr Page 60

63 Transfer, Comprehensive Structured Reporting SOP Class Transfer, CREF Apr Page 61

64 Mammography CAD SR SOP Class Transfer, Key Object Selection Document CREF Apr Page 62

65 Transfer, Chest CAD SR Transfer CREF Apr Page 63

66 , Standalone Curve Transfer, 12-lead ECG Waveform CREF Apr Page 64

67 Transfer, General ECG Waveform Transfer CREF Apr Page 65

68 , Ambulatory ECG Waveform Transfer, CREF Apr Page 66

69 Hemodynamic Waveform Transfer, Cardiac Electrophysiology Waveform CREF Apr Page 67

70 Transfer, Basic Voice Audio Waveform Transfer, CREF Apr Page 68

71 GE Nuclear Medicine private SOP Class Transfer, Philips Private Gyroscan MR Spectrum CREF Apr Page 69

72 Philips Private Gyroscan MR Series Data Transfer, Philips Private Specialized XA CREF Apr Page 70

73 Transfer, Philips Private CX Transfer, CREF Apr Page 71

74 Philips Private ie33 3D Object Transfer, Philips Private Volume CREF Apr Page 72

75 Transfer, Philips Private Volume Reference Transfer CREF Apr Page 73

76 , Philips Private 3D Object Transfer, Philips Private 3D Object CREF Apr Page 74

77 Transfer, Philips Private Surface Transfer CREF Apr Page 75

78 , Philips Private Surface Transfer, CREF Apr Page 76

79 Philips Private Composite Object Transfer, Philips Private MR Cardio Profile CREF Apr Page 77

80 Transfer, Philips Private MR Cardio Transfer, CREF Apr Page 78

81 Philips Private CT Synthetic Transfer, Philips Private MR Synthetic CREF Apr Page 79

82 Philips Private MR Cardio Analysis Transfer, Philips Private MR Cardio Analysis Data CREF Apr Page 80

83 Transfer, Philips Private CX Synthetic Transfer, CREF Apr Page 81

84 Philips Private Perfusion Reference Transfer, Philips Private Perfusion Analysis Data CREF Apr Page 82

85 Transfer, The accepted presentation contexts for DICOM storage Server are the same as listed in Table SOP Specific Conformance Statement for SOP Classes The isite DICOM Server conforms to the SOPs of the Service Class listed in Table 7 at Level 2 (Full). No elements are discarded, but the following demographic elements may be modified. Table 9: DICOM Data Elements that may be modified by the isite DICOM Server Name (Group, Element) Accession Number (0x0008, 0x0050) Referring Physician (0x0008, 0x0090) Procedure Sequence (0x0008, 0x1032) > Code Value (0x0008, 0x0100) > Code Meaning (0x0008, 0x0104) Patient Name (0x0010, 0x0010) CREF Apr Page 83

86 Name (Group, Element) Patient ID (0x0010, 0x0020) Patient Birth Date (0x0010, 0x0030) Patient Sex (0x0010, 0x0040) Requesting Physician (0x0032, 0x1032) Modification of data elements is initiated either by processing of manual edits initiated by end users of the system or automatic edits initiated by information received from ADT and Order Entry systems (HIS/RIS). Depending upon the system configuration, the isite DICOM Server application either performs lifetime persistence for the s received or manages an auto-deleted cache of the most recently active image studies. In the cache storage mode, images received will be deleted when the server disk space becomes full. Deletion will be performed based on a least accessed patient strategy. If an isite client has accessed any part of a patient s studies, all images associated with that patient have a lower probability of being deleted. The isite Server application entity returns the status code of 0 if the receipt of a C-STORE message was successful, otherwise it returns one of the following codes: Table 10: C-STORE Message Codes Code Standard Meaning Implementation Specific Meaning 0000 Success Message was received successfully A700 Out of Resources There is insufficient storage in the server. Try again later. A800 Illegal SOP Class SOP class that was not negotiated was received. A900 Data mismatch Missing type 1 or type 2 data element was detected, or other incorrect encoding in the DICOM data stream. C000 Cannot understand Part of the data could not be parsed. This usually indicates a serious DICOM encoding error in the SCU implementation or data stream corruption Presentation Context Acceptance Criterion The isite DICOM Server will accept all presentation contexts that are combinations of supported SOP Classes and Transfer es as presented in Table Transfer Selection Policies The isite DICOM Server will examine the Transfer es for a given proposed Presentation Context in the order that they are presented in the Association Request. The first proposed Transfer that matches a support Transfer will be accepted for each supported proposed Presentation Context. CREF Apr Page 84

87 Real World Activity Remote System Requests High Priority Associated Real-World Activity The DICOM specific conformance related to this real world activity is identical to the DICOM conformance presented in Real World Activity Remote System Requests Normal Priority. Please refer to that section for DICOM conformance details. Remote DICOM SCUs are able to request high priority processing of DICOM requests by negotiating their DICOM associations with the configurable high priority Application Entity Title of the isite DICOM Server. High priority DICOM storage requests are processed ahead of other pending requests for normal priority storage Real World Activity Remote System Requests Modality Performed Procedure Step (MPPS) Associated Real-World Activity The isite DICOM Server will accept DICOM Modality Performed Procedure Step association request that are initiated by remote DICOM entities. The isite DICOM Server will process the incoming MPPS messages and forward them to configured DICOM clients Accepted Presentation Contexts Table 11: Accepted Presentation Contexts for isite DICOM Server and Real-World Activity Remote System Request Modality Performed Procedure Step Abstract Transfer Name UID Name List UID List Role Extended Negotiation Modality Performed Procedure Step Forwarding MPPS The MPPS messages are forwarded as received; certain forwarding information is stored in the message as private Tags Presentation Context Acceptance Criterion The isite DICOM Server will accept all presentation contexts that are combinations of supported SOP Classes and Transfer es as presented in Table 11. CREF Apr Page 85

88 Transfer Selection Policies The isite DICOM Server will examine the Transfer es for a given proposed Presentation Context in the order that they are presented in the Association Request. The first proposed Transfer that matches a support Transfer will be accepted for each supported proposed Presentation Context Real World Activity Remote System Requests Commitment Associated Real-World Activity The isite DICOM Server will accept DICOM Commitment association requests that are initiated by remote DICOM entities. The isite DICOM Server will process the incoming requests and service them asynchronously if they are configured to do so and service synchronous responses otherwise Accepted Presentation Contexts Table 12: Accepted Presentation Contexts for isite DICOM Server and Real-World Activity Remote System Request Normal Priority Abstract Transfer Name UID Name List UID List Role Extended Negotiation Commitment Push Model Presentation Context Acceptance Criterion The isite DICOM Server will accept all presentation contexts that are combinations of supported SOP Classes and Transfer es as presented in Table Transfer Selection Policies The isite DICOM Server will examine the Transfer es for a given proposed Presentation Context in the order that they are presented in the Association Request. The first proposed Transfer that matches a support Transfer will be accepted for each supported proposed Presentation Context. CREF Apr Page 86

89 Real World Activity Remote System Requests DICOM Verification Service Associated Real-World Activity The isite DICOM Server will accept and process request for Verification Service that are initiated by remote DICOM entities Accepted Presentation Contexts Table 13: Accepted Presentation Contexts for isite DICOM Server and Real-World Activity Remote System Requests DICOM Verification Service Abstract Transfer Name UID Name List UID List Role Extended Negotiation Verification Proposed Presentation Contexts Presentation Context Acceptance Criterion The isite DICOM Server will only accept presentation contexts for the Verification Service that request the Verification SOP Class with Endian Transfer Transfer Selection Policies The isite DICOM Server will always select the for proposed presentation contexts for the Verification Service. 4.2 isite DICOM QRSCP AE Specification Table 14: QRSCP AE provides Standard conformance to the following DICOM V3.0 SOP Classes as a Query/Retrieve SCP. SOP Class UID SOP Class Name Patient Root Query/Retrieve Information Model Find* Patient Root Query/Retrieve Information Model Move* Study Root Query/Retrieve Information Model Find* Study Root Query/Retrieve Information Model Move* Patient/Study Only Query/Retrieve Information Model - Find Patient/Study Only Query/Retrieve Information Model Move CREF Apr Page 87

90 4.2.1 Association Establishment Policies General The QRSCP will listen for an association as an SCP for the Query/Retrieve SOP Class. The default maximum PDU size is Number of Associations The number of threads available to process associations is configurable, and defaults to five (5) threads. The number of simultaneous associations that can be serviced is unlimited, but performance will degrade proportionally to the number of simultaneous associations and the average activity per association. Higher performance can be achieved by increasing the number of processors, threads, and memory Asynchronous Nature Multiple transactions on a single association are not supported Implementation Identifying Information The isite QRSCP uses the following implementation identifying information. Table 15: isite QRSCP Implementation Identifying Information Implementation Class UID Association Initiation by Real-World Activity The QRSCP does not initiate associations Association acceptance policy QRSCP accepts associations for the Query/Retrieve Services Real-world activity for Find and Move commands Associations are accepted for the Query/Retrieve service. An accepted association is only closed after an error or when the client closes the association Associated Real-World Activity After an association has been accepted, the QRSCP will wait for messages appropriate for the Query/Retrieve Service. When valid messages are read from the association, they will be processed, and any required responses will be sent back on the association. CREF Apr Page 88

91 Table 16: Presentation Context Abstract Transfer Name UID Name UID Role Extended Negotiation Patient Root Query/Retrieve Information Model - Find Endian Endian SCP No Endian Patient Root Query/Retrieve Information Model - Move Endian Endian SCP No Endian Study Root Query/Retrieve Information Model - Find Endian Endian SCP No Endian Study Root Query/Retrieve Information Model - Move Endian Endian SCP No Endian Patient/Study Only Query/Retrieve Information Model Find Endian Endian Endian SCP No Patient/Study Only Query/Retrieve Information Model Move Endian Endian Endian SCP No CREF Apr Page 89

92 SOP Specific Conformance for Patient Root Query/Retrieve Information Model C-FIND Conformance Table 17: Optional keys are supported: Level Tag Description Matching Support PATIENT (0010,0030) Patient s Birth Date Matching/Existence (0010,0040) Patient s Sex Matching/Existence STUDY (0008,0090) Referring Physician Matching/Existence (0008,0061) Modalities in Study Matching/Existence (0020,1206) Num. Study Related Series Existence (0020,1208) Num. Series Related Instances Existence Retrieve AE Title attribute (0008,0054) is always returned in the Response Identifier C-MOVE Conformance The QRSCP does not perform C-STORE operations; an internal protocol is used to trigger these operations on the isite server AE. The supported Service Class SOP Classes for C-MOVE are the same as those supported by the isite server AE, and are covered in a separate conformance document. C-MOVE pending response messages are sent by QRSCP at a configurable interval, and always indicate the number of remaining, successful, failed, or warning sub-operations Presentation context acceptance criterion for Find and Move commands All presentation contexts listed in Table 16 will be accepted Transfer syntax selection policies for Find and Move commands Proposed transfer syntaxes are selected in the following order: 1. Endian Endian Endian SOP Conformance Statement SOP Specific Conformance for Study Root Query/Retrieve Information Model Complete behavior of the Patient Root SOP Classes is supported as an SCP. For a list of supported fields please consult the IHE technical specification. Only C- CREF Apr Page 90

93 FIND and C-MOVE related requests are handled, and the Priority Service parameter can be used C-FIND Conformance Table 18: Optional Keys Supported Level Tag Description Matching Support STUDY (0010,0030) Patient s Birth Date Matching/Existence (0010,0040) Patient s Sex Matching/Existence (0008,0090) Referring Physician Matching/Existence (0008,0061) Modalities in Study Matching/Existence (0020,1206) Num. Study Related Series Existence (0020,1208) Num. Series Related Instances Existence Relational queries are not supported. Retrieve AE Title attribute (0008,0054) is always returned in the Response Identifier C-MOVE Conformance The QRSCP does not perform C-STORE operations; an internal protocol is used to trigger these operations on the isite server AE. The supported Service Class SOP Classes for C-MOVE are the same as those supported by the isite server AE, and are covered in a separate conformance document. C-MOVE pending response messages are sent by QRSCP at a configurable interval, and always indicate the number of remaining, successful, failed, or warning sub-operations Presentation context acceptance criterion for Find and Move commands All presentation contexts listed in Table 16 will be accepted Transfer syntax selection policies for Find and Move commands Proposed transfer syntaxes are selected in the following order: 1. Endian Endian Endian SOP Conformance Statement SOP Specific Conformance for Patient/Study Only Query/Retrieve Information Model Complete behavior of the Patient/Study Only SOP Classes is supported as an SCP. For a list of supported fields please consult the IHE technical specification. CREF Apr Page 91

94 Only C-FIND and C-MOVE related requests are handled, and the Priority Service parameter can be used C-FIND Conformance Table 19: Optional Keys Supported Level Tag Description Matching Support PATIENT (0010,0030) Patient s Birth Date Matching/Existence (0010,0040) Patient s Sex Matching/Existence STUDY (0008,0090) Referring Physician Matching/Existence (0008,0061) Modalities in Study Matching/Existence (0020,1206) Num. Study Related Series Existence (0020,1208) Num. Series Related Instances Existence Relational queries are not supported. Retrieve AE Title attribute (0008,0054) is always returned in the Response Identifier C-MOVE Conformance The QRSCP does not perform C-STORE operations; an internal protocol is used to trigger these operations on the isite server AE. The supported Service Class SOP Classes for C-MOVE are the same as those supported by the isite server AE, and are covered in a separate conformance document. C-MOVE pending response messages are sent by QRSCP at a configurable interval, and always indicate the number of remaining, successful, failed, or warning sub-operations Presentation context acceptance criterion for Find and Move commands All presentation contexts listed in this document will be accepted Transfer syntax selection policies for Find and Move commands Proposed transfer syntaxes are selected in the following order: 4. Endian Endian Endian CREF Apr Page 92

95 4.3 isite Worklist Server AE Specification The isite Worklist Server AE provides standard conformance to the following DICOM V3.0 SOP class in the roles specified: Table 20: isite Worklist Server AE Standard Conformance SOP Class Name SOP Class UID Role Verification SCP Modality Worklist SCP Association Establishment Policies General The isite Worklist Server supports the acceptance of DICOM associations for the DICOM Modality Worklist Service and the DICOM Verification Service. The isite Worklist Server application supports a maximum PDU size of 30KB with a default of 16KB Number of Associations The isite Worklist Server application has no configurable upper limit on the number of simultaneous associations that it will accept. The upper limit of accepted associations is limited by the hardware platform and overall system performance requirements Asynchronous Nature The isite Worklist Server application does not support negotiation of multiple outstanding transactions Implementation Identifying Information The isite Worklist Server uses the following implementation identifying information. Table 21: isite Worklist Server Implementation Identifying Information Implementation Class UID Version Name IDX_MrgCOM3_ Association Initiation by Real-World Activity The isite Worklist Server application entity does not initiate DICOM associations. CREF Apr Page 93

96 4.3.3 Association Acceptance Policy Real World Activity Remote System Request DICOM Modality Worklist Associated Real-World Activity A remote application entity will establish an association with the isite Worklist Server entity in order to perform DICOM Modality Worklist operations. This activity is generally initiated by an end-user of the remote system interacting with some user interface to generate the requests. Table 22: Accepted Presentation Contexts for isite Worklist Server and Real-World Activity Remote System Request DICOM Modality Worklist Abstract Transfer Name UID Name List UID List Role Extended Negotiation Modality Worklist Implicit VR Little Endian Transfer Explicit VR Little Endian Transfer Explicit VR Big Endian Transfer SOP Conformance Statement SOP Specific Conformance to Modality Worklist SOP Class The isite Worklist Server (MWS) application entity conforms to the Modality Worklist SOP Class. Supported Matching and Return keys are listed in Table 23. MWS only supports required matching keys and return keys of Types 1, 1C, 2 and 2C. Some return keys of type 3 are also supported (see table below for the list of supported keys). It means that MWS will only accepts queries based on supported matching keys, any values provided in the return keys will be ignored which may potentially lead to larger sets of returned information. CREF Apr Page 94

97 Table 23: Supported Matching and Return Keys Description / Module Tag Matching Key Type Return Key Type Remark / Matching Type SOP Common Specific Character Set (0008,0005) O 1C Note: This attribute is omitted from the return data sets because expanded or replacement character sets are not used. Scheduled Procedure Step Scheduled Procedure Step Sequence >Scheduled Station AE Title >Scheduled Procedure Step Start Date >Scheduled Procedure Step Start Time (0040,0100) R 1 The Attributes of the Scheduled Procedure Step shall only be retrieved with Sequence Matching. The Scheduled Procedure Step Sequence shall contain only a single Item. (0040,0001) R 1 The Scheduled station AE title shall be retrieved with Single Value Matching only. (0040,0002) R 1 Scheduled Step Start Date shall be retrieved with Single Value Matching or Range Matching. See remark under Scheduled Procedure Step Start Time(0040,0003). (0040,0003) R 1 Scheduled Step Start Time shall be retrieved with Single Value Matching or Range Matching. Scheduled Step Start Date and Scheduled Step Start Time are subject to Range Matching. If both keys are specified for Range Matching, e.g. the date range "July5\July 7" and the time range "10am\6pm" specifies the time period starting on July 5, 10am until July 7, 6pm. >Modality (0008,0060) R 1 The Modality shall be retrieved with Single Value Matching. >Scheduled Performing Physician's Name >Scheduled Procedure Step Description >Scheduled Station Name >Scheduled Procedure Step Location (0040,0006) R 2 Scheduled Performing Physician's Name shall be retrieved with Single Value Matching or Wild Card Matching. Note: Though supported as a required key, using Scheduled Performing Physician Name with value other than * will cause returning no information. Imaging Suite does not schedule Performing Physicians for the exams. (0040,0007) O 1C Note: This return attribute is supported as Type 1. Its value always correspond to the value of Requested Procedure Description (0032,1060) (0040,0010) O 2 (0040,0011) O 2 Note: Supported, but will always be returned with zero length CREF Apr Page 95