DRX Viewer. DICOM Conformance Statement

Transcription

1 DRX Viewer DICOM Conformance Statement

2 DRX Viewer DICOM Conformance Statement ( B) DRX Viewer DICOM Conformance Statement.doc DeJarnette Research Systems, Inc. 401 Washington Avenue, Suite 1010 Towson, Maryland Copyright All Rights Reserved 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 available such products or services to these locations. DeJarnette is a trademark of DeJarnette Research Systems, Inc. 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 trademarks of their respective companies and are hereby acknowledged. Revision Table Revision Date Comments A December 19, 2001 Document created for V1.0. B April 29, 2004 Added Store SCU for V Washington Avenue, Suite 1010 Towson, Maryland Tel.: +1(410) Fax: +1(410) Document B 29-Apr-2004 Page 2 of 9

3 Table of Contents 1 Introduction Implementation Model Application Data Flow Diagram Functional Definitions of AEs Sequencing of Real World Activities File Meta Information AE Specifications File Reader AE Specification File Meta Information Real-World Activities StoreSCU AE Specification Association Establishment Policies Association Initiation by Real-World Activity Association Acceptance Policy Augmented and Private Application Profiles Extensions, Specializations and Privatizations Configuration Support of Extended Character Sets Washington Avenue, Suite 1010 Towson, Maryland Tel.: +1(410) Fax: +1(410) Document B 29-Apr-2004 Page 3 of 27

4

5 1 Introduction The DRX Viewer is an application that provides DICOM File Reader and DICOM Store SCU services to the user. The DRX Viewer can read DICOMDIR and DICOM formatted image files, providing the user with image display and manipulation capabilities. It also allows the user to send image series and studies via DICOM Store SCU services. The DRX Viewer is capable of supporting DICOM Upper Layer Services over the following communication protocols: TCP/IP. The message exchange formats that the DRX Viewer supports are: DICOM. 2 Implementation Model The DRX Viewer application consists of two DICOM application entities (AE): the File Reader AE and the StoreSCU AE. The File Reader AE reads DICOM files. The Store SCU AE sends image series and studies to a destination. 2.1 Application Data Flow Diagram When the user uses the DRX Viewer GUI to open a file the File Reader AE acts as a FSR to read the specified file. See Figure User Opens File File Reader AE FSR DICOM Storage Medium Figure Implementation Diagram of the DRX Viewer When the user requests that a group of images be sent to a remote destination the StoreSCU AE will send each image to the remote destination. See Figure Washington Avenue, Suite 1010 Towson, Maryland Tel.: +1(410) Fax: +1(410) Document B 29-Apr-2004 Page 1 of 27

6 User Requests Image Storage StoreSCU AE Image Stored DICOM Storage Interface Figure Implementation Data Flow Diagram of StoreSCU AE 2.2 Functional Definitions of AEs The File Reader AE supports any medium supported by the host computer. The File Reader AE can display a list of the studies available in the File-set on the media and can display images stored on the media. The StoreSCU AE sends a series or study of images to a destination. The user specifies the series or study to be sent, as well as the destination. The StoreSCU AE determines the appropriate Presentation Context from the header of the first image in the series or study and proposes an appropriate association for the transfer of the images to the destination. 2.3 Sequencing of Real World Activities There are no sequencing requirements. 2.4 File Meta Information The File Reader AE is purely a FSR that does not create DICOM files. Therefore it does not require an Implementation Class UID. 3 AE Specifications 3.1 File Reader AE Specification The File Reader AE provides standard conformance to the DICOM Interchange Option of the Media Storage Service Class. The Application Profiles and roles are listed in Table Washington Avenue, Suite 1010 Towson, Maryland Tel.: +1(410) Fax: +1(410) Document B 29-Apr-2004 Page 2 of 9

7 Table Application Profiles Supported Real World Activity Role SC Option STD-GEN-CD User Requests File Open FSC Interchange Note: The File Reader AE can read DICOMDIR files or Image Storage SOP Instances stored on any medium accessible to the computer on which the DRX Viewer is running File Meta Information The File Reader AE is purely a FSR that does not create DICOM files. Therefore no File Meta Information is required Real-World Activities There is only one real world activity associated with the File Reader AE. That is when the user opens a file Real World Activity: User Opens File The File Reader AE acts as an FSR using the Interchange option when the user opens a file. When the user opens a DICOMDIR file the DRX Viewer displays a list of the studies in the File-set. The user may click on a study to display a list of the available series within that study. The user may click on one of the series to view all the images in that series. When the user opens an image file, the image file is opened and the image is displayed Media Storage Application Profile For the list of Application Profiles that invoke this AE for the User Opens File Real World Activity, see Table There are no extensions or specializations. 3.2 StoreSCU AE Specification The SOP Classes that the StoreSCU AE uses to send images is determined by the content of the images in the series or study selected by the user. Therefore the SOP Classes that the StoreSCU AE supports as a SCU is determined by the SOP Classes of the images on the media that is being read by the DRX Viewer, which could be virtually any SOP Class. Using that logic, the following statements can be made. By default, the StoreSCU AE provides standard conformance to all DICOM Image Storage SOP as an SCU. Note, however, that the SOP Class must be configured in the DRX Viewer s syntax file for this to be true. Note also that if the image(s) on the media being read are not conformant to their SOP Class then the StoreSCU AE will not provide proper conformance to that SOP Class as an SCU when it sends the images to the destination. This is because the StoreSCU AE does not attempt to alter images to make them DICOM conformant. The StoreSCU AE does not provide conformance to any DICOM V3.0 SOP Classes as a SCP. 401 Washington Avenue, Suite 1010 Towson, Maryland Tel.: +1(410) Fax: +1(410) Document B 29-Apr-2004 Page 3 of 27

8 3.2.1 Association Establishment Policies General The maximum PDU size offered is 4096 bytes Number of Associations The number of simultaneous associations that the StoreSCU AE can support is one Asynchronous Nature The StoreSCU AE will not perform asynchronous operations window negotiation Implementation Identifying Information The implementation UID supplied is There is no implementation version name Association Initiation by Real-World Activity The StoreSCU AE will initiate associations when the user attempts to send a series or study of image(s) to a destination Sending an Image to a Remote AE Associated Real-World Activity When the user chooses to send a series or study of image(s) to a remote AE the StoreSCU AE will initiate an association or associations Proposed Presentation Contexts The StoreSCU AE will propose the Presentation Contexts list in Table 8. Table 8 Presentation Context Table for the StoreSCU AE for a Sending an Image Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation See Note See Note DICOM Implicit VR Little Endian SCU None Note: The Abstract Syntax Corresponds to the SOP Class UID specified in the header of the image file being transferred. 401 Washington Avenue, Suite 1010 Towson, Maryland Tel.: +1(410) Fax: +1(410) Document B 29-Apr-2004 Page 4 of 9

9 SOP Specific Conformance to Storage Service SOP Classes The StoreSCU AE conforms to the SOPs of the Storage Service Class as long as the image that it is trying to send meets the requirements of the IOD associated with the SOP Class associated with the image. The StoreSCU AE does not validate the conformance of the images it is sending and therefore will not conform to the SOP Class if the image does not conform to the SOP Class. When a successful or warning response to a C-STORE operation is received, the StoreSCU AE continues on to process the next image if one exists. When a failed or refused response to a C-STORE operation is received, the StoreSCU AE displays an error message to the user, disconnects from the destination and does not try to send the rest of the images. The StoreSCU AE does not attempt any extended negotiation. The StoreSCU AE does not change any elements in the images it transfers. Therefore the set of optional attributes depends entirely on the contents of the images it is asked to transfer Association Acceptance Policy The StoreSCU AE does not accept associations. 4 Augmented and Private Application Profiles The DRX Viewer does not use any augmented or private Application Profiles. 5 Extensions, Specializations and Privatizations The DRX Viewer contains no Extensions, Sepcializations or Privatizations of SOP Classes or Transfer Syntaxes. 6 Configuration The DRX Viewer may not properly interpret DICOM tags that are not included in its datadict file. At the time of release all known DICOM tags are included in the datadict file. If new DICOM tags are created after that time, or if private tags are in use in the files being read then the user should add those tags to the datadict file. The datadict file is located in the same directory as the DRX Viewer application. Similarly, the DRX Viewer may not properly interpret images of an image storage SOP Class if it is not included in its syntax file. New or private SOP Classes being used should be added to the syntax file. The syntax file is located in the same directory as the DRX Viewer application. 7 Support of Extended Character Sets No extended character sets are supported. 401 Washington Avenue, Suite 1010 Towson, Maryland Tel.: +1(410) Fax: +1(410) Document B 29-Apr-2004 Page 5 of 27