DEJARNETTE RESEARCH SYSTEMS DICOM/FFP DICOM Conformance Statement
DICOM/FFP Conformance Statement Document Number 090-00-0001 A 7 October 1996 (090-00-0001 A) DICOM_FFP DICOM Conformance Statement.doc DeJarnette Research Systems, Inc. 401 Washington Avenue, Suite 700 Towson, Maryland 21204 Copyright 1995-1996 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 publication may include technical inaccuracies and/or typographical errors. Changes are periodically made to the information herein and incorporated into new editions of the publication. DeJarnette Research Systems may make improvements and/or changes to the product(s) and/or the program(s) described in this publication at any time. It is possible that this publication 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. Revision Table Revision Date Comments 1.0 13 Jul 1995 Document created 1.1 25 Sep 1995 Updated for addition of private data element (0009,1001) 1.2 7 Oct 1996 Updated to reflect software change Version 1.2.4 ii
Table of Contents Introduction...1 1 Implementation Model...1 1.1 Application Data Flow Diagram...1 1.2 Functional Definitions of AEs...1 1.3 Sequencing of Real World Activities...2 2 AE Specifications...2 2.1 AE Specification - Message Client...2 2.1.1 Association Establishment Policies...2 2.1.1.1 General...2 2.1.1.2 Number of Associations...2 2.1.1.3 Asynchronous Nature...2 2.1.1.4 Implementation Identifying Information...2 2.1.2 Association Initiation Policy...3 2.1.2.1 Real-World Activity...3 2.1.2.1.1 Associated Real-World Activity...3 2.1.2.1.2 Presentation Context Table...3 2.1.2.1.2.1 Computed Radiography Image Storage SOP Class Conformance...3 2.1.3 Association Acceptance Policy...5 3. Communication Profiles...5 3.1 Supported Communication Stacks...5 3.1.1 TCP/IP Stack...5 3.1.1.1 Physical Media...5 4 Extensions/Specializations/Privatizations...5 5 Configuration...6 6 Support of Extended Character Sets...6 iii
iv
Introduction DeJarnette s DICOM/FFP Message Format Converter is an independent executable that converts Computed Radiography (CR) images from Film Format Protocol (FFP) to DICOM Storage SOP class messages. DICOM/FFP is a DICOM conformant client that reads FFP control files, converts the data, and sends it to a destination entity as indicated by DICOM s Storage SOP class service class user (SCU) specification. DICOM/FFP is capable of supporting DICOM Upper Layer Services over the following communication protocols: TCP/IP. The message exchange formats that DICOM/FFP supports are: DICOM. 1 Implementation Model DeJarnette s DICOM/FFP is an application composed of a single module: message client. The DICOM/FFP message client operates in the capacity of a DICOM application entity (AE). The message client is an AE that sends Storage objects to remote AEs. 1.1 Application Data Flow Diagram Once the DICOM/FFP message client is started it waits for an FFP control file to arrive in the directory specified on the command line. When a control file arrives, the data is read and the message client proposes an association based on the information specified on the command line. If the association is accepted, a DICOM CR Storage message is sent to the accepting AE for each image listed in the control file. The DICOM/FFP message client's implementation diagram is show below. FFP Control File Stored DICOM/FFP Message Client DICOM Storage Requests Sent Figure 1.1-1 1.2 Functional Definitions of AEs The DICOM/FFP message client waits for FFP control files to arrive in the specified directory. When a control file arrives the message client AE will attempt to make a connection over the specified protocol stack. (The Introduction lists the supported protocols.) The message client AE proposes connections requesting a DICOM CR Storage SOP Class. The message client sends CR image storage requests to the accepting AE. 1
1.3 Sequencing of Real World Activities Not applicable. 2 AE Specifications The DICOM functionality of DICOM/FFP can be defined as a single AE: message client. The message client is responsible for sending CR Storage requests over the protocol stack and in the message format specified on the command line. The message client AE has a default Application Title of dicomffp. The Application Title can be changed using a command line argument. 2.1 AE Specification - Message Client This application entity provides Standard Extended conformance to the following DICOM SOP classes as an SCU: Table 2.1-1 SOP Class Name SOP Class UID Computed Radiography Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.1 This AE does not operate as an SCP of any SOP class. 2.1.1 Association Establishment Policies 2.1.1.1 General The message client AE will attempt to initiate an association whenever it has successfully read and processed an FFP control file. The maximum PDU size offered is 8198 bytes. 2.1.1.2 Number of Associations The message client AE will only make one association at any given time. 2.1.1.3 Asynchronous Nature Not applicable. 2.1.1.4 Implementation Identifying Information The implementation UID supplied is 2.16.840.1.113664.1.1. There is no implementation version name. 2
2.1.2 Association Initiation Policy The message client AE will initiate an association whenever it successfully processes an FFP control file. The association will be initiated with an application context of 1.2.840.10008.3.1.1, an abstract syntax of 1.2.840.10008.5.1.4.1.1.1, and a transfer syntax of 1.2.840.10008.1.2. The association will be initiated with the default calling AE Title unless there is a calling AE Title specified on the command line. 2.1.2.1 Real-World Activity 2.1.2.1.1 Associated Real-World Activity The real-world activity associated with the message client initiating an association and sending CR Storage requests to a remote AE is detecting and successfully reading an FFP file. 2.1.2.1.2 Presentation Context Table The presentation contexts that the message client may propose are listed in the following table. Table 2.1-2 Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1 DICOM Implicit VR Little Endian 1.2.840.10008.1.2 SCU None 2.1.2.1.2.1 Computed Radiography Image Storage SOP Class Conformance The message client AE provides Standard Extended conformance to the Computed Radiography Image Storage SOP Class as an SCU. The Standard Extended information object generated by DICOM/FFP is specified in Table 2.1.2.1.2.1-1. The information object is extended by the addition of the type 3 private data element, (0009,1001). Table 2.1-3 DICOM/FFP Information Object Attribute Description Tag Type Notes Group 8 Length 0008 0000 1 SOP Class UID 0008 0016 1 =1.2.840.10008.5.1.4.1.1.1 SOP Instance UID 0008 0018 1 Study Date 0008 0020 2 Date film is scanned Acquisition Date 0008 0022 3 Date film is scanned Image Date 0008 0023 2 Date film is scanned Study Time 0008 0030 2 Time film is scanned Acquisition Time 0008 0032 3 Time film is scanned Image Time 0008 0033 2 Time film is scanned Accession Number 0008 0050 2 3
Attribute Description Tag Type Notes Modality 0008 0060 1 =CR Manufacturer 0008 0070 2 Institution Name 0008 0080 3 Referring Physician Name 0008 0090 2 Study Description 0008 1030 3 Name of Physician(s) Reading Study 0008 1060 3 Admitting Diagnosis 0008 1090 3 Group 9 Length 0009 0000 3 Private Creator Data Element 0009 0010 3 = FFP DATA CR Header Information 0009 1001 3 Group 10 Length 0010 0000 1 Patient s Name 0010 0010 2 Patient ID 0010 0020 2 Patient s Birth Date 0010 0030 2 Patient s Birth Time 0010 0032 3 Patient s Sex 0010 0040 2 Patient s Age 0010 1010 3 Patient s Size 0010 1020 3 Patient s Weight 0010 1030 3 Patient Comments 0010 4000 3 Group 18 Length 0018 0000 1 Contrast/Bolus Agent 0018 0010 2 Body Part 0018 0015 2 Filter Type 0018 1060 3 Grid Name 0018 1080 3 Focal Spot 0018 1090 3 Screen Type 0018 1260 3 Phosphur Type 0018 1261 3 View Position 0018 5101 2 Group 20 Length 0020 0000 1 Study Instance UID 0020 000D 1 Series Instance UID 0020 000E 1 Study ID 0020 0010 2 4
Attribute Description Tag Type Notes Series Number 0020 0011 2 Image Number 0020 0013 2 Patient Orientation 0020 0020 2 Laterality 0020 0060 2 Group 28 Length 0028 0000 1 Samples Per Pixel 0028 0002 1 =1 Photometric Interpretation 0028 0004 1 =MONOCHROME1 Rows 0028 0010 1 Columns 0028 0011 1 Bits Allocated 0028 0100 1 =16 Bits Stored 0028 0101 1 =10 High Bit 0028 0102 1 =9 Pixel Representation 0028 0103 1 =0 (unsigned integer) Group 7FE0 Length 7FE0 0000 1 Pixel Data 7FE0 0010 1 2.1.3 Association Acceptance Policy The message client AE does not accept any associations. 3. Communication Profiles 3.1 Supported Communication Stacks DeJarnette s DICOM/FFP supports DICOM TCP/IP Network communication as defined in Part 8 of the DICOM Standard. 3.1.1 TCP/IP Stack DeJarnette s DICOM/FFP uses the TCP/IP installed on the system. 3.1.1.1 Physical Media DeJarnette s DICOM/FFP makes no assumptions and has no limitation pertaining to the physical media over which the TCP/IP stack is running. 4 Extensions/Specializations/Privatizations Not applicable 5
5 Configuration There is no configuration of DICOM/FFP required. 6 Support of Extended Character Sets No extended character sets are supported. 6