PACSware Migration Toolkit (MDIG)

Transcription

1 PACSware Migration Toolkit (MDIG) DICOM Conformance Statement 1

2 MDIG DICOM Conformance Statement ( A) MDIG DICOM 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. DICOM is the registered trademark of the National Electrical Manufacturers Association for its standards publications relating to digital communications of medical information. Other product names mentioned in this document may be registered trademarks of their respective companies and are hereby acknowledged. Revision Table Rev Date Comments A January 20, 2009 Document created for MDIG

3 Table of Contents 1 INTRODUCTION IMPLEMENTATION MODEL APPLICATION DATA FLOW DIAGRAM FUNCTIONAL DEFINITIONS OF APPLICATION ENTITIES SEQUENCING OF REAL-WORLD ACTIVITIES AE SPECIFICATIONS VERIFY TOOL AE SPECIFICATION Association Establishment Policies General Number of Associations Asynchronous Nature Implementation Identifying Information Association Initiation Policy Associated Real-World Activity Proposed Presentation Contexts SOP Specific Conformance to Query/Retrieve SOP Classes for C-FIND Association Acceptance Policy DICOM SOURCE ROUTER SERVICE AE SPECIFICATION Association Establishment Policies General Number of Associations Asynchronous Nature Implementation Identifying Information Association Initiation Policies Associated Real-World Activity Proposed Presentation Contexts SOP Specific Conformance to Query/Retrieve SOP Classes for C-MOVE Association Acceptance Policy Associated Real-World Activity Proposed Presentation Contexts SOP Specific Conformance for Verification SOP Classes SOP Specific Conformance for All Supported Image Storage SOP Classes Presentation Context Acceptance Criterion Transfer Syntax Selection Policies TARGET PACS ROUTER SERVICE AE SPECIFICATION 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 DICOM PRE-FETCH INTERFACE SERVICE AE SPECIFICATION Association Establishment Policies General Number of Associations Asynchronous Nature Implementation Identifying Information

4 3.4.2 Association Initiation Policy Associated Real-World Activity Proposed Presentation Contexts SOP Specific Conformance to Query/Retrieve SOP Classes for C-FIND Association Acceptance Policy COMMUNICATION PROFILES SUPPORTED COMMUNICATION STACKS TCP/IP STACK Physical Media PROPRIETARY STACKS EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS CONFIGURATION SUPPORT OF EXTENDED CHARACTER SETS

5 List of Figures FIGURE 2.1-1: APPLICATION DATA FLOW... 7 List of Tables TABLE 3.1-1: SOP CLASSES SUPPORTED AS AN SCU BY THE VERIFY TOOL AE TABLE 3.1-2: PRESENTATION CONTEXT TABLE FOR THE VERIFY TOOL AE FOR QUERYING A REMOTE AE TABLE 3.1-3: PATIENT LEVEL VERIFY TOOL AE QUERY ATTRIBUTES TABLE 3.1-4: STUDY LEVEL VERIFY TOOL AE QUERY ATTRIBUTES TABLE 3.1-5: SERIES LEVEL VERIFY TOOL AE QUERY ATTRIBUTES TABLE 3.1-6: IMAGE LEVEL VERIFY TOOL AE QUERY ATTRIBUTES TABLE 3.2-1: STORE PROVIDER SUPPORTED DEFAULT SOP CLASSES TABLE 3.2-2: SOP CLASSES SUPPORTED AS AN SCU BY THE DICOM SOURCE ROUTER SERVICE AE TABLE 3.2-3: PRESENTATION CONTEXT TABLE FOR THE DICOM SOURCE ROUTER SERVICE AE FOR RETRIEVING IMAGES FROM AN AE TABLE 3.2-4: STORE PROVIDER PRESENTATION CONTEXT TABLE TABLE 3.2-5: STORE PROVIDER OPTIONAL COMPRESSED TRANSFER SYNTAXES TABLE 3.2-6: STORAGE RESPONSE CODES TABLE 3.3-1: TARGET PACS ROUTER SERVICE AE PRESENTATION CONTEXT TABLE TABLE 3.4-1: SOP CLASSES SUPPORTED AS AN SCU BY THE DICOM PRE-FETCH INTERFACE SERVICE AE TABLE 3.4-2: PRESENTATION CONTEXT TABLE FOR THE DICOM PRE-FETCH INTERFACE SERVICE AE FOR QUERYING A REMOTE MWL AE TABLE 3.4-3: DICOM PRE-FETCH INTERFACE SERVICE AE MWL QUERY ATTRIBUTES

6 1 INTRODUCTION The DeJarnette PACSware Migration Toolkit (MDIG) is a product designed to migrate DICOM image data from a legacy image archive system (known as a source PACS). Image data is migrated to an active or alternate image archive system (known as a target PACS). The MDIG product is designed to be flexible, thus it supports a number of different migration models. DICOM Indirect Migration In this model, the MDIG retrieves studies of images from the source PACS via Query / Retrieve. Studies are then processed and forwarded to a target PACS via the DICOM Storage service. An initial inventory of the source PACS is performed via Query / Retreive. DICOM Direct Migration In this model, the MDIG system moves studies of images directly from the source PACS to the target PACS via the Query / Retrieve service. An initial inventory of the source PACS is performed via Query / Retreive. Assisted Media Migration In this model, DICOM image files are recovered directly from source PACS media. This media could be tapes, optical disks or hard drive based storage. The DICOM files are imported in bulk by a user. Media Direct Migration In this model, DICOM media files are retrieved and imported directly from a source PACS archive automatically. To facilitate automatically migrating media files, the migration queue is populated directly from the source PACS database. 6

7 2 IMPLEMENTATION MODEL The MDIG consists of a number of integrated applications and Windows services which run concurrently on one computer system. The product provides DICOM interfaces for Storage, Verification, Query/Retrieve and Modality Worklist services. 2.1 Application Data Flow Diagram The MDIG consists of four application entities: the Verify Tool AE, the DICOM Source PACS Router Service AE, the DICOM Target PACS Router Service AE and the DICOM Pre-Fetch Interface Service AE. Figure does not detail Verification as an individual Real-World activity; however the Verify Tool AE and the DICOM Source PACS Router Service AE support the DICOM Verification service. Figure 2.1-1: Application Data Flow 7

8 2.2 Functional Definitions of Application Entities The MDIG includes four DICOM application entities (AEs). 1. The Verify Tool is a GUI tool which runs on an MDIG device. The Verify Tool allows a user to perform an inventory of a source PACS archive device and populate a migration queue with the contents of that inventory. The tool also allows a user to reconcile the contents of the migration queue with a target PACS archive device, to verify that studies have been migrated successfully. The Verify Tool allows a user to configure a date range, a DICOM Query / Retrieve provider and several query options. 2. The DICOM Source PACS Router Service is a Window service application which runs on an MDIG device. The Source Router issues move requests to source PACS archive devices and provides the storage service to receive the images which were requested. The Source Router processes and stores images locally and queues them for migration to a target PACS archive device. Optionally, the Source Router can issue move requests which direct a source PACS archive device to store images directly to a target PACS archive device. 3. The DICOM Target PACS Router Service is a Windows service application which runs on an MDIG device. The Target Router supports the storage service as a service class user. The Target Router processes studies which are queued for migration by storing images to a target PACS archive device. 4. The DICOM Pre-Fetch Interface Service is a Windows service application which runs on an MDIG device. The Pre-Fetch Service supports the Modality Worklist Query / Retrieve service as a service class user. The Pre-Fetch Service issues MWL query requests to configured modality Worklist providers. The Pre-Fetch Service stores the results of Worklist queries locally and uses them to flag studies in the migration queue for pre-fetch (priority migration). 2.3 Sequencing of Real-World Activities The sequence of real-world activities which occur on an MDIG device varies depending on the migration model used. DICOM Indirect Migration When the DICOM indirect migration model is used, the following sequence of realworld activities applies: 1. The Verify Tool is used to query the source PACS for studies. The results are used to build a migration queue. 2. The DICOM Source PACS Router Service issues a move request to the source PACS archive device for one study from the migration queue. 3. The DICOM Source PACS Router Service receives and stores images for one study from the migration queue. 4. The DICOM Target PACS Router Service stores images for one study to a target PACS archive device. 5. Steps 2-4 are repeated for each additional study in the migration queue. 6. The DICOM Pre-Fetch Interface Service issues Modality Worklist queries to remote Worklist providers. This occurs concurrently and repeatedly with steps 2-4. The results are used to prioritize the processing order of the migration queue. 8

9 DICOM Direct Migration When the DICOM direct migration model is used, the following sequence of realworld activities applies: 1. The Verify Tool is used to query the source PACS for studies. The results are used to build a migration queue. 2. The DICOM Source PACS Router Service issues a move request to the source PACS archive device for one study from the migration queue. The move requests that images are stored directly from the source PACS archive device to a target PACS archive device. 3. Step 2 is repeated for each additional study in the migration queue. 4. The DICOM Pre-Fetch Interface Service issues Modality Worklist queries to remote Worklist providers. This occurs concurrently and repeatedly with steps 2. The results are used to prioritize the processing order of the migration queue. Assisted Media Migration When the DICOM assisted media migration model is used, the following sequence of real-world activities applies: 1. The Verify Tool may be used to query the source PACS for studies. The results are used to build a migration queue. The migration queue may also be populated by a process which does not make use of DICOM services. 2. Images for one study are imported to the MDIG device. This process does not require use of DICOM services. 3. The DICOM Target PACS Router Service stores images for one study to a target PACS archive device. 4. Steps 2-3 are repeated for each additional study in the migration queue. 5. The DICOM Pre-Fetch Interface Service issues Modality Worklist queries to remote Worklist providers. This occurs concurrently and repeatedly with steps 2-3. The results are used to prioritize the processing order of the migration queue. Media Direct Migration When the DICOM media direct migration model is used, the following sequence of real-world activities applies: 1. The migration queue is populated by a process which does not make use of DICOM services. 2. Images for one study are imported to the MDIG device. This process does not require use of DICOM services. 3. The DICOM Target PACS Router Service stores images for one study to a target PACS archive device. 4. Steps 2-3 are repeated for each additional study in the migration queue. 5. The DICOM Pre-Fetch Interface Service issues Modality Worklist queries to remote Worklist providers. This occurs concurrently and repeatedly with steps 2-3. The results are used to prioritize the processing order of the migration queue. 9

10 3 AE SPECIFICATIONS 3.1 Verify Tool AE Specification The Verify Tool AE does not operate as an SCP but only as an SCU. The Verify Tool AE provides standard conformance to the following DICOM V3.0 SOP classes as an SCU. SOP Class Name SOP Class UID Patient Root Query/Retrieve Information Model FIND Study Root Query/Retrieve Information Model FIND Patient/Study Only Query/Retrieve Information Model FIND Table 3.1-1: SOP Classes supported as an SCU by the Verify Tool AE Association Establishment Policies General The maximum PDU size offered is configurable, but the default is 4096 bytes Number of Associations The Verify Tool AE can support only 1 simultaneous outgoing DICOM association Asynchronous Nature The Verify Tool AE will not perform asynchronous operations window negotiation Implementation Identifying Information The implementation UID supplied is There is no implementation version name Association Initiation Policy The Verify Tool AE will initiate associations when the user attempts to query a remote source PACS DICOM node Associated Real-World Activity The Verify Tool issues queries by study date at the STUDY, SERIES and / or IMAGE levels. The Verify Tool issues queries based on the date range specified by a user of the tool. Normally, one query is issued for each study date in the specified date range. Alternatively, the Verify Tool may be configured to Query by Patient ID. When this option is configured, the Verify Tool issues a number of queries for each study date. The patient ID field is included in the query as well. One query is issued for each possible last character in a patient ID. I.E. Queries are issued for studies whose patient ID values match *0, *1,, *a, *b,, *A, *B, etc. 10

11 Proposed Presentation Contexts The Query/Retrieve User AE will propose the Presentation Contexts listed 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 Patient/Study Only Query/Retrieve Information Model FIND DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR SCU None SCU None SCU None Table 3.1-2: Presentation Context Table for the Verify Tool AE for Querying a Remote AE SOP Specific Conformance to Query/Retrieve SOP Classes for C-FIND When the Verify Tool AE queries a remote AE, all Query/Retrieve Information Models will be offered. The Verify Tool AE supports relational queries. The Verify Tool AE can perform study, series and image level relational and hierarchical queries. By default, the Verify Tool AE will request the DICOM attributes listed in the following three tables for the patient, study, series and image levels. However, it may be configured to request the values of virtually any DICOM attribute. It is left to the user to ensure that the Query/Retrieve SCP supports any additional attributes that are added. The Verify Tool AE will issue queries which request matching of the values specified as Matching in the tables below. Description Type Tag Used For Matching Patient s Name R (0010,0010) Patient ID U (0010,0020) Yes Patient s Birth Date O (0010,0030) Patient s Sex O (0010,0040) Table 3.1-3: Patient Level Verify Tool AE Query Attributes Description Type Tag Used For Matching Study Date R (0008,0020) Yes Study Time R (0008,0030) Accession Number R (0008,0050) Referring Physician s Name O (0008,0090) Study Description O (0008,1030) Procedure Code Sequence O (0008,1032) Study Instance UID U (0020,000D) Yes Study ID O (0020,0010) Table 3.1-4: Study Level Verify Tool AE Query Attributes Description Type Tag Used For Matching Modality R (0008,0060) 11

12 Series Instance UID U (0020,000E) Yes Series Number O (0020,0011) Table 3.1-5: Series Level Verify Tool AE Query Attributes Description Type Tag Used For Matching SOP Class UID O (0008,0016) SOP Instance UID U (0008,0018) Yes Image Number R (0020,0013) Table 3.1-6: Image Level Verify Tool AE Query Attributes Association Acceptance Policy The Verify Tool AE does not accept associations. 3.2 DICOM Source Router Service AE Specification The DICOM Source Router Service AE provides standard conformance to the following DICOM V3.0 SOP classes as an SCP. SOP Class Name SOP Class UID Verification 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 Multi-frame Image Storage (US) Magnetic Resonance Image Storage (MR) Nuclear Medicine (RET) Image Storage (NM) Ultrasound Image Storage (US) Secondary Capture Image Storage X-Ray Angiographic Image Storage (XA) X-Ray Radiofluoroscopic Image Storage (RF) X-Ray Angiographic Bi-Plane Image Storage (XA) Nuclear Medicine Image Storage (NM) Positron Emission Tomography Image Storage (PT) Other Instance Storage SOP Classes (the DICOM Source Router Service can be configured to accept any SOP Class). All other valid Instance Storage SOP Class UIDs Table 3.2-1: Store Provider Supported Default SOP classes 12

13 The DICOM Source Router Service AE provides standard conformance to the following DICOM V3.0 SOP classes as an SCU. SOP Class Name SOP Class UID Patient Root Query/Retrieve Information Model - MOVE Study Root Query/Retrieve Information Model - MOVE Patient/Study Only Query/Retrieve Information Model MOVE Table 3.2-2: SOP Classes supported as an SCU by the DICOM Source Router Service AE Association Establishment Policies The DICOM Source Router established query / retrieve associations with source PACS archive devices to issue move requests for each study queued for migration. As move requests are issued, the DICOM Source Router accepts incoming storage associations from the source PACS archive devices General The maximum PDU size offered is configurable, but the default is 4096 bytes Number of Associations The number of simultaneous associations used by the DICOM Source Router Service AE is configurable. The DICOM Source Router Service AE can accommodate up to 32 simultaneous associations Asynchronous Nature The DICOM Source Router Service AE will not perform asynchronous operations window negotiation Implementation Identifying Information The implementation UID supplied is There is no implementation version name Association Initiation Policies The DICOM Source Router Service AE will initiate query / retrieve associations and send move requests to configured source PACS archive devices Associated Real-World Activity The DICOM Source Router Service processes a migration queue. A query / retrieve association is opened and a move request is sent to a source PACS archive device for each study in the migration queue Proposed Presentation Contexts The DICOM Source Router Service AE will propose the Presentation Contexts listed in the table below, but only the MOVE related contexts apply to this activity. 13

14 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 Patient/Study Only Query/Retrieve Information Model MOVE DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR SCU None SCU None SCU None Table 3.2-3: Presentation Context Table for the DICOM Source Router Service AE for Retrieving Images from an AE SOP Specific Conformance to Query/Retrieve SOP Classes for C-MOVE The DICOM Source Router Service AE provides standard conformance to the all three MOVE SOP Classes listed above as an SCU Association Acceptance Policy The DICOM Source Router Service AE accepts an association if the proposed presentation context is found in its local presentation context table, if the targeted AE title is the DICOM Source Router Service AE and if the application context is The DICOM Source Router Service AE can be configured per Abstract Syntax to accept other then the default transfer syntax as well, however at this point the application level acceptance of the data is not guaranteed Associated Real-World Activity The DICOM Source Router Service AE accepts and stores DICOM object instances from configured source PACS archive devices to which it has issued move requests. The DICOM Source Router Service AE also accepts and responds to verification service associations Proposed Presentation Contexts The default DICOM presentation contexts offered by the DICOM Source Router Service are listed in Table DICOM Source Router Service configuration settings provide the facility to add other presentation contexts. All the presentation contexts defined will be offered, and the first one accepted will be used to transmit the message. Acceptance presentation contexts can be turned on or off in DICOM Source Router configuration settings. If this option is turned on, abstract syntaxes listed in Table and marked as optionally supporting compressed transfer syntaxes, will be supported in conjunction with all the compressed transfer syntaxes listed in Table Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Verification DICOM Implicit VR Computed Radiography (CR) Image Storage DICOM Implicit VR 14

15 Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Digital Radiography (DX) Image Storage Mammography (MG) Image Storage Digital Intra-Oral X-ray Image Storage Computed Tomography (CT) Image Storage DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR 15

16 Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Ultrasound (US) Multiframe Storage (Retired) Ultrasound (US) Multiframe Storage Magnetic Resonance (MR) Image Storage Ultrasound (US) Image Storage DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR 16

17 Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Secondary Capture Image Storage 12-lead ECG Waveform Storage General ECG Waveform Storage Ambulatory ECG Waveform Storage Hemodynamic Waveform Storage Cardiac Electrophysiology Waveform Storage Basic Voice Audio Waveform Storage DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR 17

18 Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Grayscale Softcopy Presentation State Color Softcopy Presentation State Storage Pseudo-Color Softcopy Presentation State Storage Blending Softcopy Presentation State Storage X-Ray Angiography (XA) Image Storage X-Ray Radiofluoroscopic Image Storage DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR 18

19 Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation X-Ray Angiographic Biplane Image Storage Nuclear Medicine (NM) Image Storage Text SR Storage Trial (Retired) DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR Audio SR Storage Trial (Retired) DICOM Implicit VR Detail SR Storage Trial (Retired) DICOM Implicit VR 19

20 Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Comprehensive SR Storage Trial (Retired) Basic Text Structured Report Storage Enhanced Structured Report Storage Comprehensive Structured Report Storage Mammography CAD Structured Report Storage Key Object Selection Document Positron Emission Tomography (PET) Image Storage DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR DICOM Implicit VR 20

21 Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Table 3.2-4: Store Provider Presentation Context Table Transfer Syntax Name JPEG Baseline (Process 1): Default Transfer Syntax for Lossy JPEG 8 Bit Image Compression JPEG Extended (Process 2 & 4): Default Transfer Syntax for Lossy JPEG 12 Bit Image Compression (Process 4 only) JPEG Extended (Process 3 & 5) (Retired) JPEG Spectral Selection, Non-Hierarchical (Process 6 & 8) (Retired) JPEG Spectral Selection, Non-Hierarchical (Process 7 & 9) (Retired) JPEG Full Progression, Non-Hierarchical (Process 10 & 12) (Retired) JPEG Full Progression, Non-Hierarchical (Process 11 & 13) (Retired) JPEG Lossless, Non-Hierarchical (Process 14) JPEG Lossless, Non-Hierarchical (Process 15) (Retired) JPEG Extended, Hierarchical (Process 16 & 18) (Retired) JPEG Extended, Hierarchical (Process 17 & 19) (Retired) JPEG Spectral Selection, Hierarchical (Process 20 & 22) (Retired) JPEG Spectral Selection, Hierarchical (Process 21 & 23) (Retired) JPEG Full Progression, Hierarchical (Process 24 & 26) (Retired) JPEG Full Progression, Hierarchical (Process 25 & 27) (Retired) JPEG Lossless, Hierarchical (Process 28) (Retired) JPEG Lossless, Hierarchical (Process 29) (Retired) JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]): Default Transfer Syntax for Lossless JPEG Image Compression RLE Lossless DRS Wavelet Compression Transfer Syntax UID Table 3.2-5: Store Provider Optional Compressed Transfer Syntaxes SOP Specific Conformance for Verification SOP Classes The DICOM Source Router Service AE provides standard conformance for the Verification SOP Class as an SCP SOP Specific Conformance for All Supported Image Storage SOP Classes The DICOM Source Router Service provides Level 2 (full) conformance as an SCP of the Storage SOP Classes. All received Attributes are stored and maybe subsequently accessed, including Private and other Type 3 Attributes that exist in Standard Extended SOP Instances. 21

22 All stored SOP instances are accessible from the MDIG device at least until they are routed to a target PACS archive device. The images are aged off the MDIG after that. The duration of data reception is determined by the bandwidth and actual load of the local area network, extended with the processing time of the item by the DICOM Source Router Service. The processing time itself is typically much less than 1 second. The DICOM Source Router Service will return an unsuccessful or C-STORE warning response in accordance with Unsuccessful/Warning Storage Responses. In all error cases, the SOP Instance is not permanently stored. Status Code Description 0106 (Invalid Attribute Tag) Indicates that the DICOM Command was neither a C-ECHO nor a C-STORE. Those are the only Service classes supported by the DICOM Source Router Service AE. The SCU must send one of the supported Service Classes. A700 (Out of Resources) Indicates the DICOM Source Router Service AE is running low on memory or disk space. This also may indicate a network or computer system error that caused the failure. The user should use the system s log files to get more specific information about the nature of the error and try to resolve it. A701 (Missing Parameter) Indicates that a required parameter was not passed properly between software modules within the DICOM Source Router Service AE. The user should use the system s log files to get more specific information about the nature of the error and try to resolve it. A702 (Creation Error) Indicates that the DICOM Source Router Service AE failed to create an object or structure internally. This error is usually caused by low memory. A703 (File Open Error) Indicates that the DICOM Source Router Service AE failed to open an image file on disk. The user should use the system s log files to find the name of the file that it failed to open and make sure that it exists. A704 (Database Access Error) Indicates that the DICOM Source Router Service AE failed to access the local database. The user should verify the database is running and that the configured username and password are correct. C100 (Missing Command Attribute) Indicates that the Attribute Command Field (0000,0100) was not present in the storage request message. This indicates a problem with the SCU of the Service Class. C106 (Invalid Attribute) Indicates that the DICOM Source Router Service AE failed to parse or process a DICOM message. This usually indicates a problem with the SCU of the Service Class. C120 (Missing Attribute) Indicates that the Attribute Series Instance UID (0020,000E) was not present in the storage request message. This indicates a problem with the SCU of the Service Class. F000 (Uncategorized Error) Uncategorized Error. See log files for more information to try to determine the cause of the problem. Table 3.2-6: Storage Response Codes 22

23 Presentation Context Acceptance Criterion The DICOM Source Router Service AE will accept all supported presentation contexts that are listed in the configuration and match those offered by the requesting entity Transfer Syntax Selection Policies The transfer syntax accepted and applied to the presentation context will be the first one listed in the configuration that matches one offered by the requesting entity. The list is checked in the order they are offered by the requesting entity. 3.3 Target PACS Router Service AE Specification The Target PACS Router Service AE does not operate as an SCP but only as an SCU. The Target PACS Router Service AE provides standard conformance to all storage SOP classes. The SOP Class UID is specified in the header of the image file to be transferred Association Establishment Policies General The maximum PDU size offered is configurable, but the default is 4096 bytes Number of Associations The Target PACS Router Service AE can support up to 32 simultaneous associations Asynchronous Nature The Target PACS Router Service AE will not perform asynchronous operations window negotiation Implementation Identifying Information The implementation UID supplied is There is no implementation version name Association Initiation Policy The Target PACS Router Service AE initiates storage associations based on configured schedule parameters and the contents of a migration queue Associated Real-World Activity The Target PACS Router Service AE is responsible for storing images to target PACS archive devices for each study in the migration queue Presentation Context Table The Target PACS Router Service will present the object to the destination using the transfer syntax that was used when the object was transmitted to the MDIG as the default transfer syntax. The Target PACS Router Service can be configured to present additional transfer syntaxes. 23

24 The transfer syntaxes are listed in Table Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation See Note See Note DICOM Implicit VR Note: The Abstract Syntax of the SOP Class UID is specified in the header of the image file to be transferred. Table 3.3-1: Target PACS Router Service AE Presentation Context Table SOP Specific Conformance for all Storage Service SOP Classes The Target PACS Router Service AE does not support extended negotiations Association Acceptance Policy The Target PACS Router Service AE does not accept associations. 3.4 DICOM Pre-Fetch Interface Service AE Specification The DICOM Pre-Fetch Interface Service AE does not operate as an SCP but only as an SCU. The DICOM Pre-Fetch Interface Service AE provides standard conformance to the following DICOM V3.0 SOP classes as an SCU. SOP Class Name SOP Class UID Modality Worklist Management SOP Class Table 3.4-1: SOP Classes supported as an SCU by the DICOM Pre-Fetch Interface Service AE Association Establishment Policies General The maximum PDU size offered is configurable, but the default is 4096 bytes Number of Associations The number of simultaneous associations that the DICOM Pre-Fetch Interface Service AE uses is based on configuration parameters. The DICOM Pre-Fetch Interface Service AE can accommodate up to 32 simultaneous associations Asynchronous Nature The DICOM Pre-Fetch Interface Service AE will not perform asynchronous operations window negotiation Implementation Identifying Information The implementation UID supplied is There is no implementation version name. 24

25 3.4.2 Association Initiation Policy The DICOM Pre-Fetch Interface Service AE will initiate associations to perform Modality Worklist queries of a remote Modality Worklist provider for the purpose of recording the results in the MDIG database and prioritizing migration of related studies Associated Real-World Activity The DICOM Pre-Fetch Interface Service follows configured routing rules and periodically issues queries to configured DICOM Modality Worklist sources Proposed Presentation Contexts The DICOM Pre-Fetch Interface Service AE will propose the Presentation Contexts listed in the table below. Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Modality Worklist Management SOP Class DICOM Implicit VR SCU None Table 3.4-2: Presentation Context Table for the DICOM Pre-Fetch Interface Service AE for Querying a Remote MWL AE SOP Specific Conformance to Query/Retrieve SOP Classes for C-FIND When the DICOM Pre-Fetch Interface Service AE queries a remote AE for DICOM MWL, the AE will request the DICOM elements listed in the following three tables for the patient, study and series levels. The DICOM Pre-Fetch Interface Service will issue queries which request matching of the values specified as Matching in the tables below. Description Type Tag Used For Matching Patient s Name R (0010,0010) Patient ID R (0010,0020) Patient s Date Of Birth O (0010,0030) Patient s Sex O (0010,0040) Accession Number O (0008,0050) Requesting Physician O (0032,1032) Referring Physician O (0008,0090) Requested Procedure O (0032,1060) Description Requested Procedure Code O (0032,1064) Sequence >Code Value O (0008,0100) Scheduled Procedure Step Sequence >Scheduled Procedure Start Date >Scheduled Procedure Start Time R (0040,0100) R (0040,0002) yes R (0040,0003) 25

26 >Modality R (0008,0060) >Scheduled Performing R (0040,0006) Physician s Name >Scheduled Station AE Title R (0040,0001) Table 3.4-3: DICOM Pre-Fetch Interface Service AE MWL Query Attributes Association Acceptance Policy The DICOM Pre-Fetch Interface Service AE does not accept associations. 26

27 4 COMMUNICATION PROFILES 4.1 Supported Communication Stacks The MDIG supports DICOM TCP/IP Network Communication Support as defined in Part 8 of the DICOM Standard. 4.2 TCP/IP Stack The MDIG uses the TCP/IP stack installed on the system Physical Media The MDIG 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 MDIG does not use proprietary protocol stacks. 5 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS The MDIG does not implement any extensions, specializations or privatizations. 6 CONFIGURATION Consult the MDIG User and System Manual for information about configuration procedures. 7 SUPPORT OF EXTENDED CHARACTER SETS No extended character sets are supported. 27