ImagePort IQ v2.0 DICOM Conformance Statement. ImagePort IQ. Radiance PACS Archive Server DICOM Conformance Statement

Transcription

1 ImagePort IQ Radiance PACS Archive Server DICOM Conformance Statement 1

2 ImagePort IQ v2.0 DICOM Conformance Statement A ( A) ImagePort IQ v2.0 - Conformance Statement.doc DeJarnette Research Systems, Inc. 401 Washington Avenue, Suite 1010 Towson, Maryland Copyright This document and the associated software are copyrighted by DeJarnette Research Systems, Inc. of Towson, Maryland. Neither this document nor the associated software may be reproduced or copied without the expressed written consent of DeJarnette Research Systems, Inc. This document may include technical inaccuracies and/or typographical errors. Changes are periodically made to the information herein and incorporated into new editions of the document. DeJarnette Research Systems may make improvements and/or changes to the product(s) and/or the program(s) described in this document at any time. This document may contain reference to or information about DeJarnette Research Systems products (hardware or software) or services that are not available in all countries. Such references or information do not imply any intent on DeJarnette s part to make such products or services available to these locations. DeJarnette, Radiance, NetShare, MediShare and ImagePort are trademarks or registered trademarksof DeJarnette Research Systems, Inc. Other product names mentioned in this document may be registered trademarks of their respective companies and are hereby acknowledged. Revision Table Rev Date Comments 0.9 June 22, 1998 Draft Document created 1.0 March 24, 2000 Revised, updated document according to latest FRS and HLD-s A December 18, 2003 Revised, updated document according to Version 2.0 of the ImagePort IQ 2

3 Table of Contents 1 INTRODUCTION IMPLEMENTATION MODEL APPLICATION DATA FLOW DIAGRAM FUNCTIONAL DEFINITIONS OF AES SEQUENCING OF REAL-WORLD ACTIVITIES AE SPECIFICATIONS AE SPECIFICATION QUERY/RETRIEVE PROVIDER (QRP) Association Establishment Policies General Number of Associations Asynchronous Nature Implementation Identifying Information Association Acceptance Policy Transfer syntax Acceptance Criteria Serving Query Requests Associated Real-World Activity Proposed Presentation Contexts SOP Specific Conformance to Query/Retrieve SOP Classes for C-FIND Serving Move Requests Associated Real-World Activity Proposed Presentation Contexts SOP Specific Conformance to Query/Retrieve SOP Classes for C-MOVE AE SPECIFICATION STOREU AE Association Establishment Policies General Number of Associations Asynchronous Nature Implementation Identifying Information Association Initiation Policy Associated Real-World Activity Presentation Context Table SOP Specific Conformance for all Storage Service SOP Classes Association Acceptance Policy COMMUNICATION PROFILES SUPPORTED COMMUNICATION STACKS TCP/IP STACK Physical Media PROPRIETARY STACKS EXTENSIONS/SPECIALIZATIONS/PRIVATIZATIONS STANDARD EXTENDED STORAGE SOP CLASSES DEJARNETTE WAVELET PRIVATE TRANSFER SYNTAX CONFIGURATION SUPPORT OF EXTENDED CHARACTER SETS

4 List of Tables TABLE 3.1-1: QRP-AE SUPPORTED SOP CLASSES...8 TABLE 3.1-2: PRESENTATION CONTEXT TABLE FOR THE QRP-AE WHEN SERVING A REMOTE AE...9 TABLE 3.1-3: PATIENT LEVEL QUERY ATTRIBUTES OF THE PATIENT-ROOT QUERY/RETRIEVE INFORMATION MODEL...10 TABLE 3.1-4: STUDY LEVEL QUERY ATTRIBUTES OF THE PATIENT-ROOT QUERY/RETRIEVE INFORMATION MODEL...11 TABLE 3.1-5: SERIES LEVEL QUERY ATTRIBUTES OF THE PATIENT-ROOT QUERY/RETRIEVE INFORMATION MODEL...11 TABLE 3.1-6: IMAGE LEVEL QUERY ATTRIBUTES OF THE PATIENT-ROOT QUERY/RETRIEVE INFORMATION MODEL...12 TABLE 3.1-7: STUDY LEVEL QUERY ATTRIBUTES OF THE STUDY-ROOT QUERY/RETRIEVE INFORMATION MODEL...13 TABLE 3.1-8: SERIES LEVEL RELATIONAL-QUERY ATTRIBUTES...14 TABLE 3.1-9: OTHER RESPONSE IDENTIFIER ATTRIBUTES SUPPORTED IN ALL SUCCESSFUL C-FIND RESPONSES14 TABLE : QUERY RESPONSE CODES...15 TABLE : PRESENTATION CONTEXT TABLE OF THE QRP-AE FOR MOVING IMAGES FROM AN AE...16 TABLE STORE USER PRESENTATION CONTEXT TABLE...20 TABLE : MOVE RESPONSE CODES...20 TABLE 3.2-1: DEFAULT SOP CLASSES SUPPORTED BY THE STORE AE...21 TABLE 3.2-2: STOREU AE PRESENTATION CONTEXT TABLE...23 TABLE 3.2-3: OPTIONAL ATTRIBUTES ADDED TO SECONDARY CAPTURE OBJECTS CREATED FROM MULTIFRAME OBJECTS...23 TABLE 5.1-1: PRIVATE ATTRIBUTES ADDED TO STANDARD STORAGE SOP CLASSES

5 1 INTRODUCTION The DeJarnette Radiance PACS is a centralized/distributed 3 rd generation PACS architecture. The Radiance architecture is centralized in the logical sense and distributed in terms of physical data storage. The MediShare IQ (MS IQ) contains the Radiance PACS database. The MS IQ stores all relevant information about the PACS system in the Radiance database, including exam order information received from a HIS/RIS, but does not store the images themselves. In the Radiance architecture images reside in short-term and/or long-term storage devices distributed about the system. The NetShare IQ (NS IQ) is the short-term storage device for Radiance. The NS IQ receives images from various modality equipment, rationalizes the incoming data with the relevant RIS order information in the Radiance database, and after enriching the DICOM header of the incoming image, temporarily stores the data on its shortterm, reliable storage unit. There can be several Netshare IQ devices deployed in a Radiance PACS implementation, each serving a number of modalities, giving Radiance its distributed data storage. At a later time (that is programmable on the MS IQ) the image data is archived on Radiance s long-term archive device, the ImagePort IQ. There can be several ImagePort IQ (IP IQ) devices deployed in a Radiance PACS implementation. All information processed by an IP IQ is merged/rationalized in an MS IQ database. The IP IQ is an archive server component of the Radiance PACS system. The IP IQ provides DICOM Storage services to the NS IQ devices and is also capable of responding to DICOM Query/Move requests from other medical imaging devices. The IP IQ accepts images in the form of DICOM C-STORE Storage requests and serves queries and moves to other devices in the form of DICOM C-FIND and C-MOVE SOP classes. The IP IQ also assumes that all images received by it are already introduced to the RP IQ DataBase by the sending NS IQ device. The IP IQ DICOM Upper Layer Services are provided over the TCP/IP communication protocol, the message exchange formats that the ImagePort IQ supports are according to DICOM V3.0. This document specifies the IP IQ's DICOM conformance. 2 IMPLEMENTATION MODEL The IP IQ is a server front-end gateway to a Hierarchical Storage Management (HSM) organized archive device. It can receive image data via DICOM, it stores this data in the HSM and informs the central Radiance knowledge base (KB of MS IQ) database about the fact that the Item is archived. The entire MS IQ KB can be browsed and the safely archived imagery can be accessed via the IP IQ Query/Retrieve server facility. 2.1 Application Data Flow Diagram The primary functionality of an IP IQ is to store and serve image data. Most commonly used image modalities are supported; new ones can be dynamically configured. When an image arrives to an IP IQ, the MS IQ s knowledge base is searched for matching image file entry. If the matching entry is found, IP IQ stores the image file permanently on the Archive device and modifies the KB entry for the new archived location of the object. DICOM header information is untouched. Figure illustrates the activity of the IP IQ DICOM AE entities. Also, a built-in Storage Commit SCP, as part of the Store SCP AE, is provided to manage transfer of ownership of archived DICOM image objects. Typically, modality devices are seeking for transfer of ownership and those are directly connected to NetShare IQ devices, which are capable of the identical functionality. 5

6 SQL (MS IQ DB) Store, Rationalize Image Find archived Item(s) StoreP- Store Modality Image Transfer Data Ownership Query Retrieve Lists/data QRP-AE Move/ Retrieve IP IQ DICOM Standard Interface Receive Images Figure 2.1-1: Application Data Flow The Query/Retrieve SCP is capable of serving multiple (maximum 32) query and/or move requests in the same time. The Move SCP portion of the QRP AE can be used when an external entity issues a Retrieve or Move request to the QRP AE. This is a built-in function of the IP IQ where an internal DICOM Move SCU initiates routing of local images to predefined destinations. All data and state information is stored in a robust (Oracle KB) database on the MS IQ, only DICOM image objects are stored on the archive device hooked to the IP IQ for long term and/or on various NS IQ-s for short-term. It is the caller s responsibility to contact the proper DICOM AE for image object retrieval 1. When data is retrieved by the IP IQ, on any failure, all operations are resumed from where they were stopped, meaning if moving of an item was interrupted that operation is considered not done. IP IQ does not need operator intervention after the system is configured properly. Figure does not detail DICOM Verification as an individual Real-World activity, however all SCP AEs (Store/ Storage Commitment and Q/R) on IP IQ have the Verification SCP incorporated. The MS IQ and IP IQ configuration files and database records contain all the supported destinations. Refer to the MediShare and ImagePort System Manuals for information on configuration. 2.2 Functional Definitions of AEs The IP IQ has two DICOM Application Entities (AEs). The SCP AE has the verification SCP embedded. The IP IQ has a third AE, the Storage Provider (SP) AE. It can only receive images from a NS IQ and therefore it is not listed here. 1. The first AE is the Query/Retrieve Provider (QRP). The QRP is a Q/R SCP waiting for DICOM query and move requests. Patient, Study and Patient/Study root queries are permitted on Patient/Study/Series/Image levels. Relational queries are supported. 1 This implies that the Query requestor has the knowledge how to connect to any of the RP IQ resident DICOM Query/Retrieve AE-s. 6

7 The built in Move SCU of the IP IQ requests auto-routes of local images from the QRP SCP. The QRP AE uses information from the IP IQ and MS IQ configuration settings to establish a DICOM association for the subsequent Store SCU operations. 2. The second AE is the Storage User (StoreU). The StoreU AE is used by the Q/R SCP to move images to destinations when requested. 2.3 Sequencing of Real-World Activities There are two precedence issues in terms of IP IQ AEs. One obvious issue is that the Query/Retrieve provider cannot query or retrieve an item that was not fully processed (stored locally and introduced into the Knowledge Base) by the Store Provider. The other one is that storage commitment cannot be done for an item before it is fully processed by the store provider. 7

8 3 AE SPECIFICATIONS 3.1 AE Specification Query/Retrieve Provider (QRP) The IP IQ administrator has the ability to configure multiple QRP-AE titles, the default setting is 1. Each QRP (QRP-AE) provides conformance to the following DICOM SOP classes as an SCP: SOP Class Name SOP Class UID Verification Patient Root Find Patient Root Move Study Root Find Study Root Move Table 3.1-1: QRP-AE Supported SOP classes Association Establishment Policies General The maximum PDU size offered is configurable. The default setting is 32,768 bytes Number of Associations The maximum number of simultaneous associations that the QRP AE can support is 32. Also, if needed, more QRP- AEs can be started via configuration settings. The number of associations is practically limited by the system resources only Asynchronous Nature The QRP-AE does not support asynchronous operations Implementation Identifying Information The implementation UID supplied is There is no implementation version name Association Acceptance Policy The QRP-AE accepts an association if the proposed presentation context is found in its local presentation context table. The targeted AE title is the StoreP-AE, the application context is Transfer syntax Acceptance Criteria Each presentation context uses the DICOM default transfer syntax exclusively (Implicit VR, Little-Endian). 8

9 Serving Query Requests Associated Real-World Activity The associated real-world activities that occur after successful reception of a Query request is searching the Radiance database, composing the DICOM Query Response message and finally returning the response. For a move/retrieve request the Radiance database searched again to know what image objects should be moved. The Radiance database always knows where the actual data is and, if there is more than one location, which location provides quicker access Proposed Presentation Contexts The default DICOM presentation contexts are always accepted by the QRP-AE. By default only the DICOM Implicit VR, little-endian transfer syntax is accepted. These default values specified in the base configuration correspond to the entries in Table Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Patient Root Query/Retrieve Information Model FIND Study Root Query/Retrieve Information Model FIND DICOM Implicit VR DICOM Implicit VR Table 3.1-2: Presentation Context Table for the QRP-AE when serving a Remote AE SOP Specific Conformance to Query/Retrieve SOP Classes for C-FIND The QRP-AE can process patient-root, study-root and patient/study-root C-FIND requests. The level of the query depends on the level requested by the user; it can be Patient, Study, Series or Image. The QRP-AE also support relational-queries for series level only, using extended negotiation, according to the DICOM standard specification. The QRP-AE does not support priority processing. Supported Optional Keys (only 3) are marked in the Restrictions/Comments field of the tables below. All matches are case insensitive. The following tables itemize the attributes that the QRP-AE supports in all possible cases. 9

10 Description Type Tag Restrictions / Comments Patient's Name R (0010,0010) Patient ID U (0010,0020) Referenced Patient Sequence O (0008,1120) not supported >Referenced SOP Class UID O (0008,1150) not supported >Referenced SOP Instance UID O (0008,1155) not supported Patient's Birth Date O (0010,0030) Patient's Birth Time O (0010,0032) Patient's Sex O (0010,0040) Other Patient Ids O (0010,1000) Other Patient Names O (0010,1001) Ethnic Group O (0010,2160) Patient Comments O (0010,4000) Value only, no matching Number of Patient Related Studies O (0020,1200) not supported Number of Patient Related Series O (0020,1202) not supported Number of Patient Related Instances (Images) O (0020,1204) not supported Table 3.1-3: Patient level Query Attributes of the Patient-Root Query/Retrieve Information Model Description Type Tag Restrictions / Comments Study Date R (0008,0020) Study Time R (0008,0030) Accession Number R (0008,0050) Modalities in Study O (0008,0061) not supported Referring Physician s Name O (0008,0090) Study Description O (0008,1030) Procedure Code Sequence O (0008,1032) >Code Value O (0008,0100) Value only, no matching >Code Scheme Designator O (0008,0102) Value only, no matching >Code Scheme Version O (0008,0103) Value only, no matching >Code Meaning O (0008,0104) Value only, no matching Name of Physician(s) Reading Study O (0008,1060) Admitting Diagnoses Description O (0008,1080) Referenced Study Sequence O (0008,1110) not supported >Referenced SOP Class UID O (0008,1150) not supported >Referenced SOP Instance UID O (0008,1155) not supported 10

11 Study Instance UID U (0020,000D) Study ID R (0020,0010) Patient's Age O (0010,1010) Patient's Size O (0010,1020) Patient's Weight O (0010,1030) Occupation O (0010,2180) Additional Patient History O (0010,21B0) Value only, no matching Other Study Numbers O (0020,1070) not supported Number of Study Related Series O (0020,1206) not supported Number of Study Related Instances (Series) O (0020,1208) not supported Interpretation Author O (4008,010C) not supported Table 3.1-4: Study level Query Attributes of the Patient-Root Query/Retrieve Information Model Description Type Tag Restrictions / Comments Modality R (0008,0060) Series Date O (0008,0021) Series Time O (0008,0031) Series Description O (0008,103E) Performing Physicians Name O (0008,1050) Operators' Name O (0008,1070) Body Part Examined O (0018,0015) Protocol Name O (0018,1030) Series Number R (0020,0011) Series Instance UID U (0020,000E) Laterality O (0020,0060) Number of Series Related Instances (Images) O (0020,1209) Not Supported Table 3.1-5: Series level Query Attributes of the Patient-Root Query/Retrieve Information Model 11

12 Description Type Tag Restrictions / Comments SOP Instance UID U (0008,0018) Image Type O (0008,0008) Image Date O (0008,0023) Acquisition Date O (0008,0022) Acquisition Time O (0008,0032) Acquisition Number O (0020,0012) Instance (Image) Number R (0020,0013) Images in Acquisition O (0020,1002) Overlay Number O (0020,0022) Curve Number O (0020,0024) LUT Number O (0020,0026) Image Comments O (0020,4000) Lossy Image Compression O (0028,2110) Table 3.1-6: Image level Query Attributes of the Patient-Root Query/Retrieve Information Model Description Type Tag Restrictions / Comments Study Date R (0008,0020) Study Time R (0008,0030) Accession Number R (0008,0050) Modalities in Study O (0008,0061) Referring Physician s Name O (0008,0090) Study Description O (0008,1030) Procedure Code Sequence O (0008,1032) >Code Value O (0008,0100) Value only, no matching >Code Scheme Designator O (0008,0102) Value only, no matching >Code Scheme Version O (0008,0103) Value only, no matching >Code Meaning O (0008,0104) Value only, no matching Name of Physician(s) Reading Study O (0008,1060) Admitting Diagnoses Description O (0008,1080) Referenced Study Sequence O (0008,1110) not supported >Referenced SOP Class UID O (0008,1150) not supported >Referenced SOP Instance UID O (0008,1155) not supported Referenced Patient Sequence O (0008,1120) not supported >Referenced SOP Class UID O (0008,1150) not supported >Referenced SOP Instance UID O (0008,1155) not supported Patient's Name R (0010,0010) 12

13 Patient ID R (0010,0020) Patient's Birth Date O (0010,0030) Patient's Birth Time O (0010,0032) Patient's Sex O (0010,0040) Other Patient IDs O (0010,1000) Other Patient Names O (0010,1001) Patient's Age O (0010,1010) Patient's Size O (0010,1020) Patient's Weight O (0010,1030) Ethnic Group O (0010,2160) Occupation O (0010,2180) Additional Patient History O (0010,21B0) Value only, no matching Patient Comments O (0010,4000) Value only, no matching Study Instance UID U (0020,000D) Study ID R (0020,0010) Number of Patient Related Studies O (0020,1200) not supported Number of Patient Related Series O (0020,1202) not supported Number of Patient Related Instances (Images) O (0020,1204) not supported Number of Study Related Series O (0020,1206) not supported Number of Study Related Instances (Series) O (0020,1208) not supported Interpretation Author O (4008,010C) not supported Table 3.1-7: Study level Query Attributes of the Study-Root Query/Retrieve Information Model Series Level attributes for the Series Level of the Study Root Query/Retrieve Information Model are the same as the Attributes for the Series Level of the Patient Root Query/Retrieve Information Model described above. Image Level attributes for the Image Level of the Study Root Query/Retrieve Information Model are the same as the Attributes for the Image Level of the Patient Root Query/Retrieve Information Model described above. Patient Level attributes for the Patient Level of the Patient/Study Only Query/Retrieve Information Model are the same as the Attributes for the Patient Level of the Patient Root Query/Retrieve Information Model described above. 13

14 The following table is for all Series Level relational queries: Description Type Tag Restrictions Study Date R (0008,0020) Series Date O (0008,0021) Study Time R (0008,0030) Series Time O (0008,0031) Accession Number R (0008,0050) Modality O (0008,0060) Referring Physician s Name O (0008,0090) Series Description O (0008,103E) Performing Physicians Name O (0008,1050) Name of Physician(s) Reading Study O (0008,1060) Operators' Name O (0008,1070) Patient's Name R (0010,0010) Patient ID R (0010,0020) Patient's Birth Date O (0010,0030) Patient's Birth Time O (0010,0032) Patient's Sex O (0010,0040) Body Part Examined O (0018,0015) Protocol Name O (0018,1030) Study Instance UID O (0020,000D) Series Number R (0020,0011) Series Instance UID U (0020,000E) Laterality O (0020,0060) Table 3.1-8: Series Level Relational-Query Attributes Description Tag Conditions / Comments Specific Character set (0008,0005) No special character set supported Retrieve AE Title (0008,0054) Always returned Table 3.1-9: Other Response Identifier Attributes supported in all successful C-FIND responses The QRP-AE supports Range Matching for Date and Time as independent keys. That is, if either date range or time range are specified in the request identifier, the matches date will be strictly within the requested key date range, or the matches time will be strictly within the requested key time range. EXCEPT THE FOLLOWING CASES, when they are evaluated as a combination of specified matching ranges, that is, the date has both upper and lower range and the time has either an upper or a lower range. 14

15 All the possible cases are: 1) Date : datefrom-dateto Time: timefrom- The above request set is interpreted as all the records in the database which are no earlier than datefrom,timefrom and no later than dateto. 2) Date : datefrom-dateto Time: -timeto The above request set is interpreted as all the records in the database which are no earlier than datefrom and no later than dateto,timeto. 3) Date : datefrom-dateto Time: timefrom-timeto The above request set is interpreted as all the records in the database which are no earlier than datefrom,timefrom and no later than dateto,timeto. Service Status Further Meaning, Status Related Fields Corrective Action Codes Error Unable to Process (SOP class not supported, C000 (0000,0901) Missing required UID, Unable to build SQL (0000,0902) command from the request, Database access failure) For Missing required UID it indicates that one of the following required attributes was missing from the storage request: (0008,0018), (0020,000d) or (0020,000e). The SCU must include all of those elements in the storage request. Success 0000 None Table : Query Response Codes Serving Move Requests Associated Real-World Activity When a Remote AE chooses to move images to a specified AE the QRP AE will negotiate with the requesting (and the requested destination) AE for an association. The associated real-world activities that occur after successful reception of a Move request are: searching the MS IQ Radiance database for the requested instances and the AE parameters of the destination AE, and starting a store SCU sub-operation toward the destination AE. 2 Local access/retrieval of the DICOM formatted data items is part of the real-world activity as well. In case the data is not on ON-LINE media in the archive unit, the Move SCP will wait a configurable amount of seconds before it times out. It is suggested that the Move SCU should have at least as large a timeout setting as the ORP-AE has. Please refer to the ImagePort System Manual for configuration settings. The typical worst case retrieval time of a NEAR-LINE object is minutes. Notes: It is assumed that when a Move request is issued to the QRP AE the source images are on archive storage device of the IP IQ. This statement subsequently implies that the Query SCU, upon receiving its query response, is 2 If the move operation is higher than image level, the store SCU opens the association, sends all objects and, finally, closes the association (instead of opening and closing association for each item). 15

16 capable of issuing the actual Retrieve/Move request to the destination AE specified in the Retrieve AE Title (0008,0054) of the query response item. Obviously that also implies that the Retrieve/Move requestor entity must be aware of all possible Radiance Move SCP AEs. In addition the Radiance Database must be aware of each possible Store SCP destination the Retrieve/Move SCP might request Proposed Presentation Contexts The QRP-AE will accept the Presentation Contexts listed in Table , but only the MOVE related contexts apply to the activity of querying a remote AE. Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Patient Root Query/Retrieve Information Model MOVE Study Root Query/Retrieve Information Model MOVE DICOM Implicit VR DICOM Implicit VR Table : Presentation Context Table of the QRP-AE for Moving Images from an AE SOP Specific Conformance to Query/Retrieve SOP Classes for C-MOVE The QRP-AE provides standard conformance to the Patient-Root and Study Root Query/Retrieve Information Model MOVE SOP Class as an SCP. The QRP-AE does not support priority processing. The QRP-AE supports relational-retrieves on series level only, using extended negotiation. The QRP AE uses the Storage SOP Classes defined in Table to support C-STORE SCU sub-operations of the Retrieve SOP Classes. The IP IQ configuration settings provide the facility to add other presentation contexts. 16

17 Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Verification DICOM Implicit VR Computed Radiography (CR) Image Storage Digital Radiography (DX) Image Storage Mammography (MG) Image Storage DICOM Implicit VR Big Endian Extended (Process 2 & 4) Lossless, Non- Hierarchical, First- Order Prediction SCP None SCP None SCP None SCP None DeJarnette Wavelet SCP None DICOM Implicit VR Big Endian Extended (Process 2 & 4) Lossless, Non- Hierarchical, First- Order Prediction SCP None SCP None SCP None SCP None DeJarnette Wavelet SCP None DICOM Implicit VR Big Endian Extended (Process 2 & 4) Lossless, Non- Hierarchical, First- Order Prediction SCP None SCP None SCP None SCP None DeJarnette Wavelet SCP None 17

18 Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Computed Tomography (CT) Image Storage Magnetic Resonance (MR) Image Storage Ultrasound (US) Image Storage DICOM Implicit VR Big Endian Extended (Process 2 & 4) Lossless, Non- Hierarchical, First- Order Prediction DICOM Implicit VR SCP None SCP None SCP None SCP None DeJarnette Wavelet SCP None Big Endian Extended (Process 2 & 4) Lossless, Non- Hierarchical, First- Order Prediction DICOM Implicit VR SCP None SCP None SCP None SCP None DeJarnette Wavelet SCP None Big Endian Extended (Process 2 & 4) Lossless, Non- Hierarchical, First- Order Prediction SCP None SCP None SCP None SCP None DeJarnette Wavelet SCP None 18

19 Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Secondary Capture Image Storage X-Ray Angiography (XA) Image Storage DICOM Implicit VR Big Endian Extended (Process 2 & 4) Lossless, Non- Hierarchical, First- Order Prediction DICOM Implicit VR SCP None SCP None SCP None SCP None DeJarnette Wavelet SCP None Big Endian Extended (Process 2 & 4) Lossless, Non- Hierarchical, First- Order Prediction SCP None SCP None SCP None SCP None DeJarnette Wavelet SCP None 19

20 Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Ultrasound Multiframe (US MF) Image Storage Nuclear Medicine (RET) Image Storage X-Ray Radiofluoroscopy (RF) Image Storage X-Ray Angiography Bi-Plane (XA BP) Image Storage Nuclear Medicine (NM) Image Storage Positron Emission Tomography (PET) Image Storage Storage Commitment Push Model DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR Table Store User Presentation Context Table The Move response codes are listed in Table Service Status Further Meaning, Corrective Action Status Codes Related Fields Failed The store user unable to send files A900 (0000,0901) (0000,0902) Error Unable to Process (sop class not supported, C000 (0000,0901) Move destination not known, Missing (0000,0902) required UID, Error finding the image files required by the user) Success 0000 None Table : Move Response Codes 20

21 3.2 AE Specification StoreU AE When the Query/Move AE (QRP AE) must transfer image objects it makes use of the StoreU AE. This may happen when an external entity performs a Query/Retrieve operation. However, the QRP AE is also used internally by the Radiance PACS to automatically route images to configured destinations according to routing and pre-fetch rules. To facilitate image routing, a routing module initiates DICOM Move requests to the QRP AE. When any Retrieve or Move request is processed, the QRP AE makes use of the StoreU AE to actually send the images to the requested destination. The SOP Classes that the StoreU AE uses to send images is determined by the content of the images the ImagePort IQ has stored on its local storage. Therefore the SOP Classes that the StoreU AE supports as an SCU is determined by the SOP Classes the StoreP AE supports as a SCP. Using that logic, the following statements can be made. By default, the StoreU AE provides standard conformance to the DICOM SOP classes listed in Table as an SCU. In addition, the Router AE may also provide standard conformance to any image object of the Storage Service Class, including private SOP Classes, if the StoreP AE was ever configured to receive those SOP Classes and subsequently received an image of that SOP Class. Note also that if the StoreP AE receives an image that is not conformant to its SOP Class then the StoreU AE will not provide proper conformance to that SOP Class as an SCU when it sends that image to a remote entity. This is because the StoreU AE does not attempt to alter images to make them DICOM conformant. SOP Class Name SOP Class UID Computed Radiography Image Storage (CR) Digital Radiography Image Storage (DX) Digital Radiography Processed Image Storage (DX) Mammography Image Storage (MG) Mammography Processed Image Storage (MG) Computed Tomography Image Storage (CT) Ultrasound Multiframe Image Storage (US) Magnetic Resonance Image Storage (MR) Nuclear Medicine (RET) Image Storage (NM) Ultrasound Image Storage (US) Secondary Capture Image Storage X-Ray Angiography Image Storage X-Ray Radiofluoroscopy Image Storage X-Ray Angiography Bi-Plane Image Storage Nuclear Medicine Image Storage Positron Emission Tomography Image Storage Table 3.2-1: Default SOP Classes supported by the Store AE 21

22 3.2.1 Association Establishment Policies General The StoreU AE will attempt to establish an association whenever the QRP AE initiates the sending of images to a destination. The maximum PDU size offered is configurable, but the default is bytes Number of Associations The StoreU AE will only initiate one association per destination simultaneously. However, multiple instances of the StoreU AE may exist at one time. For example, when images are being routed to two destinations simultaneously. Ultimately the number of simultaneous StoreU AE associations is limited by system resources Asynchronous Nature The StoreU AE does not support asynchronous operations window negotiation Implementation Identifying Information The implementation UID supplied is There is no implementation version name Association Initiation Policy The StoreU AE will initiate an association when the QRP AE initiates the sending of images to a destination Associated Real-World Activity The associated real-world activity that causes the initiation of an association is when an external entity issues a Retrieve or Move request to the QRP AE Presentation Context Table If the images to be routed are stored in a compressed format (one of the supported Transfer Syntaxes) the StoreU AE will negotiate for the related presentation first and if it succeeds it will send the compressed data. On failure to negotiate, the default Transfer Syntax is proposed without compression and it will decompress each frame before transfer. The StoreU AE will propose the default presentation context and the optional compressed Transfer Syntax variety of the same SOP classes. The transfer syntaxes are listed in Table

23 Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation See Note See Note DICOM Implicit VR See Note See Note Extended (Process 2 & 4) See Note See Note Lossless, Non- Hierarchical, First- Order Prediction SCP None SCP None See Note See Note DeJarnette Wavelet SCP None Note: The Abstract Syntax of the SOP Class UID is specified in the header of the image file to be transferred. Table 3.2-2: StoreU AE Presentation Context Table SOP Specific Conformance for all Storage Service SOP Classes The StoreU AE does not support extended negotiations. The StoreU AE is essentially an image router and therefore does not alter the optional attributes in the images that it routes. The optional attributes contained in the images sent by the Router AE are controlled by the AE that sent the images to the ImagePort IQ and the receiving StoreP AE. The only exception to this rule is when the NetShare IQ (the NS IQ that originally sent the images to the IP IQ) has converted an uncompressed multi-frame image to a series of Secondary Capture images so that they can be sent to a Storage Class Provider that is not able to handle multi-frame images. In that case some optional attributes may be removed from the original image and the optional attributes listed in Table will be added to each individual Secondary Capture object. Tag Name (0018,1016) Secondary Capture Device Manufacturer (0018,1018) Secondary Capture Device Manufacturer's Model Name (0018,1019) Secondary Capture Device Software Version(s) Table 3.2-3: Optional Attributes Added to Secondary Capture Objects Created from Multiframe Objects Association Acceptance Policy The StoreU AE does not accept associations. 23

24 4 COMMUNICATION PROFILES 4.1 Supported Communication Stacks The IP IQ supports DICOM TCP/IP Network Communication Support as defined in Part 8 of the DICOM Standard. 4.2 TCP/IP Stack The IP IQ uses the TCP/IP installed on the system Physical Media The IP IQ makes no assumptions and has no limitation pertaining to the physical Ethernet media over which the TCP/IP is running. 4.3 Proprietary Stacks The IP IQ does not use of proprietary stacks. 5 EXTENSIONS/SPECIALIZATIONS/PRIVATIZATIONS The ImagePort IQ implements both a Standard Extended SOP Class and a Private Transfer Syntax. These are described here. 5.1 Standard Extended Storage SOP Classes When the ImagePort IQ s StoreU AE sends image objects in compressed format the Standard Storage SOP Classes are extended by the use of Private Attributes. The following table describes the Private Attributes added to the Standard Storage SOP Classes: 24

25 Tag Name VR Description (0029,0010) Private Creator Data Element LO Always set to DeJarnette Private Group. (0029,1000) Compression Factor Used US The Compression Quality Index used in the compression. This number ranges from 1 to 1000 with one being highest quality and therefore least compression. (0029,1002) Compression Ratio LO The compression ratio achieved, expressed in the format x:1. (0029,1010) Compression Type CS One of the following values (in quotes): LOSSLESSJPEG Lossless JPEG LOSSYJPEG Lossy JPEG WAVELET DeJarnette Wavelet (0029,1014) Signed Data Compression Adjustment US This attribute is only present when lossy compression is used. Lossy compression algorithms are unable to compress signed data. Therefore, before lossy compressing signed data it is necessary to change the signed data into unsigned data. This is achieved by adding an adjustment factor to each pixel value. This attribute contains the value added to each signed pixel value before lossy compression is applied. This allows the receiver to change the pixel data back to signed pixel data after decompression if desired. Table 5.1-1: Private Attributes Added to Standard Storage SOP Classes 5.2 DeJarnette Wavelet Private Transfer Syntax DeJarnette has defined a Transfer Syntax for lossy Wavelet Image Compression. It is identified by the Private Transfer Syntax UID = and is supported by every DeJarnette product that supports lossy Wavelet Image Compression. This Transfer Syntax follows the rules for Transfer Syntaxes for Encapsulation of Encoded Pixel Data set forth in PS CONFIGURATION Consult the Medishare and Netshare System Manual for information about the IP IQ configuration procedures. 7 SUPPORT OF EXTENDED CHARACTER SETS No extended character sets are supported. 25