DICOM Conformance Statement

Transcription

1 DICOM Conformance Statement HI VISION Ascendus Special Notes to Operators and Maintenance Managers Before using this system, be sure to thoroughly read this DICOM Conformance Statement and make yourself familiar with this system. After reading this DICOM Conformance Statement, keep it in an easily accessible place close to the system. Tokyo, Japan E1EEZ15926 Hitachi, Ltd. 2013, All rights reserved.

2 Cautions on exportation: When exporting this equipment, be sure to check the Foreign Exchange and Foreign Trade Control Law and the regulations related to export control in the United States of America, and perform the necessary procedures. Contact Hitachi or an authorized representative if you have further inquiries. Revision history: First edition: September 2010 Fourth edition: December 2012 Sixth edition: April 2016

3 CONFORMANCE STATEMENT OVERVIEW The HI VISION Ascendus system implements the necessary DICOM services to download work lists from an information system, save acquired US images to a network storage device, DVD, USB memory, USB HDD or network folder, save acquired Structured Reports to a network storage device, print to a networked hardcopy device and inform the information system about the work actually done. Following Table provides an overview of the network services. Table 1 NETWORK SERVICES SOP Classes User of Service (SCU) Provider of Service (SCP) Transfer Ultrasound Image Storage Yes (Note 1) No Ultrasound Image Storage (Retired) Yes (Note 1) No Ultrasound Multiframe Image Storage Yes (Note 1) No Ultrasound Multiframe Image Storage (Retired) Yes (Note 1) No Comprehensive SR Yes (Note 1) No Storage Commitment Push Model Yes (Note 1) No Workflow Management Modality Worklist Yes (Note 2) No Modality Performed Procedure Step Yes (Note 2) No Print Management Basic Grayscale Print Management Yes (Note 3) No Basic Color Print Management Yes (Note 3) No Query/Retrieve Study Root Information Model FIND Yes (Note 4) No Study Root Information Model MOVE Yes (Note 4) No Ultrasound Image Storage No Yes (Note 4) Ultrasound Image Storage (Retired) No Yes (Note 4) Ultrasound Multiframe Image Storage No Yes (Note 4) Ultrasound Multiframe Image Storage (Retired) No Yes (Note 4) CT Image Storage No Yes (Note 4) E1EEZ1592 i

4 SOP Classes User of Service (SCU) Provider of Service (SCP) MR Image Storage No Yes (Note 4) Secondary Capture Image Storage No Yes (Note 4) NOTE 1: Separately licensable option DICOM Software (Transfer and Media Storage) EZUFC12. NOTE 2: Separately licensable option DICOM Software (Worklist) EZUFC12W. NOTE 3: Separately licensable option DICOM Software (Printer) EZUFC12P. NOTE 4: Separately licensable option DICOM Software (Query/Retrieve) EZUFC12Q. Following Table provides an overview of the Media Storage Application Profiles. Table 2 Media Services Media Storage Application Profile Write Files Read Files Update Files (FSC) (FSR) (FSU) DVD General Purpose DVDRAM Yes (Note 1) Yes (Note 1) Yes (Note 1) General Purpose DVDR Yes (Note 1) Yes (Note 1) No ii E1EEZ1592

5 TABLE OF CONTENTS CONFORMANCE STATEMENT OVERVIEW...i TABLE OF CONTENTS... iii Chapter 1 INTRODUCTION AUDIENCE REMARKS DEFINITIONS, TERMS AND ABBREVIATIONS...1 Chapter 2 NETWORKING IMPLEMENTATION MODEL Application Data Flow Sequencing of RealWorld Activities AE SPECIFICATIONS Storage Application Entity Specification Workflow Application Entity Specification Hardcopy Application Entity Specification Query/Retrieve Application Entity Specification NETWORK INTERFACES Physical Network Interface IPv4 and IPv6 Support CONFIGURATION AE Title Parameters...43 Chapter 3 MEDIA INTERCHANGE IMPLEMENTATION MODEL Application Data Flow...45 E1EEZ1592 iii

6 3.1.2 File Meta Information Options AE SPECIFICATIONS Media Application Entity Specification Chapter 4 SUPPORT OF CHARACTER SETS...47 Chapter 5 SECURITY...49 Chapter 6 ANNEXES IOD CONTENTS Created SOP Instances Attribute mapping Coerced/Modified Fields DATA DICTIONARY OF PRIVATE ATTRIBUTES CODED TERMINOLOGY AND TEMPLATES OBGYN REPORT TEMPLATES (OB_SR_II) ECHOCARDIOGRAPHY PROCEDURE REPORT TEMPLATES (Cardiac_SR_II) OBGYN REPORT TEMPLATES (OB_SR) VASCULAR ULTRASOUND REPORT TEMPLATES (Vascular_SR) ECHOCARDIOGRAPHY PROCEDURE REPORT TEMPLATES (Cardiac_SR) GRAYSCALE IMAGE CONSISTENCY STANDARD EXTENDED / SPECIALIZED / PRIVATE SOP CLASSES PRIVATE TRANSFER SYNTAXES INDEX iv E1EEZ1592

7 Chapter 1 INTRODUCTION 1.1 AUDIENCE Chapter 1 INTRODUCTION This document is intended for hospital staff, health system integrators, software designers or implementers. It is assumed that the reader has a working understanding of DICOM. 1.2 REMARKS DICOM, by itself, does not guarantee interoperability. However, the Conformance Statement facilitates a firstlevel validation for interoperability between different applications supporting the same DICOM functionality. This Conformance Statement is not intended to replace validation with other DICOM equipment to ensure proper exchange of information intended. The scope of this Conformance Statement is to facilitate communication with this system and other DICOM systems. The Conformance Statement should be read and understood in conjunction with the DICOM Standard [DICOM]. However, by itself it is not guaranteed to ensure the desired interoperability and a successful interconnectivity. The user should be aware of the following important issues: The comparison of different conformance statements is the first step towards assessing interconnectivity between this system and other DICOM systems. Test procedures should be defined to validate the desired level of connectivity. 1.3 DEFINITIONS, TERMS AND ABBREVIATIONS Definitions, terms and abbreviations used in this document are defined within the different parts of the DICOM standard. Abbreviations and terms are as follows: AE Application Entity DICOM Digital Imaging and Communication in Medicine FSC FSU FSR IOD MPPS MWL FileSet Creator FileSet Updater FileSet Reader Information Object Definition Modality Performed Procedure Step Modality Worklist E1EEZ1592 1

8 Chapter 1 INTRODUCTION PDU SCU SCP SOP SR TCP/IP TID UID VR Protocol Data Unit Service Class User (DICOM client) Service Class Provider (DICOM server) ServiceObject Pair Structured Report Transmission Control Protocol / Internet Protocol Identifier of Template Unique Identifier Value Representation 2 E1EEZ1592

9 Chapter 2 NETWORKING Chapter 2 NETWORKING 2.1 IMPLEMENTATION MODEL Application Data Flow Send Images, Reports & Commits Storage Application Entity Remote Application Entity Receives Images, Reports & Commits; Returns Commitments Query Worklist Start Exam & End Exam Workflow Application Entity Remote Application Entity Provides Worklist Items Remote Application Entity Receives MPPS Create / Set Film Images Hardcopy Application Entity Remote Application Entity Prints Film Sheets Query Image Information Retrieve Images Query/Retrieve Application Entity Remote Application Entity Provides Image Information Remote Application Entity Provides Image DICOM Standard Interface Figure 2.11 Application Data Flow Diagram E1EEZ1592 3

10 Chapter 2 NETWORKING Sequencing of RealWorld Activities Query/ Retrieve Storage Hardcopy Workflow Department Scheduler Printer Image Manager 1. Query Worklist 2. Receive Worklists 3. Select Worklist item 4. Start Exam (Create MPPS) 5. Acquire Images 6. End Exam (Finalize MPPS) 7. Film Images 8. Send Images & Reports 9. Send Commits 10. Query Image Information 11. Retrieve Images Figure 2.12 Sequencing Constraints 4 E1EEZ1592

11 Chapter 2 NETWORKING 2.2 AE SPECIFICATIONS Storage Application Entity Specification (1) SOP Classes Storage AE provides Standard Conformance to the following SOP Classes: Table 2.21 SOP Classes for AE Storage SOP Class Name SOP Class UID SCU SCP Ultrasound Image Storage Yes No Ultrasound Image Storage (Retired) Yes No Ultrasound Multiframe Image Storage Yes No Ultrasound Multiframe Image Storage (Retired) Yes No Comprehensive SR Yes No Storage Commitment Push Model Yes No Verification Yes No (2) Association Establishment Policies [1] General The DICOM standard application context name is always proposed: Table 2.22 DICOM APPLICATION CONTEXT FOR AE STORAGE Application Context Name [2] Number of Associations Storage AE initiates one Association at a time. Table 2.23 NUMBER OF ASSOCIATIONS INITIATED FOR AE STORAGE Maximum number of simultaneous Associations 1 [3] Asynchronous Nature Storage AE does not support asynchronous communication. Table 2.24 ASYNCHRONOUS NATURE AS A SCU FOR AE STORAGE Maximum number of outstanding asynchronous transactions 1 E1EEZ1592 5

12 Chapter 2 NETWORKING [4] Implementation Identifying Information The implementation information for Storage AE is: Table 2.25 DICOM IMPLEMENTATION CLASS AND VERSION FOR AE STORAGE Implementation Class UID Implementation Version Name HMC14.15 (3) Association Initiation Policy [1] Activity Send Images, Reports and Commits [11] Sequencing of Activities Storage AE Image Manager 1. Send Images and Reports 1. Open Association 2. CSTORE (Image or Report) 3. Close Association 4. Open Association 5. NACTION (Storage Commitment Request for Image) 6. Close Association 7. Open Association 8. NEVENTREPORT (Storage Commitment Response) 9. Close Association Figure 2.21 SEQUENCING OF ACTIVITY SEND IMAGES, REPORTS AND COMMITS The sequence of interactions between the Storage AE and an Image Manager is illustrated in Figure above. Note that commits can only be sent for images. Reports are not supported. [12] Proposed Presentation Contexts Storage AE will propose the Presentation Contexts shown in the following table. 6 E1EEZ1592

13 Chapter 2 NETWORKING Table 2.26 Proposed Presentation Contexts for RealWorld Activity Send Images, REPORTS AND COMMITS Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Ext. Neg. Ultrasound Image Storage Ultrasound Image Storage (Retired) Implicit VR Ultrasound Multiframe Image Storage Little Endian JPEG Lossy Baseline SCU None Ultrasound Multiframe Image Storage (Retired) Comprehensive SR Implicit VR Little Endian SCU None Storage Commitment Push Model Implicit VR Little Endian SCU None [13] SOP Specific Conformance for Image and SR SOP Class All Image and Structured Report SOP Classes supported by the Storage AE exhibit the same behavior. The behavior of Storage AE when encountering status codes in a CSTORE response is summarized in the table below: Table 2.27 STORAGE CSTORE RESPONSE STATUS HANDLING BEHAVIOR Service Status Further Meaning Error Code Behavior Success Success 0000 The SCP has successfully stored the SOP Instance. E1EEZ1592 7

14 Chapter 2 NETWORKING Service Status Further Meaning Error Code Behavior * * Any Other status code. The Association is aborted using AABORT. The behavior of Storage AE during communication failure is summarized in the table below: Table 2.28 Storage Communication Failure Behavior Exception Behavior Timeout Association aborted by the SCP or network layers The Association is aborted using AABORT. The Association is aborted using AABORT. [14] SOP Specific Conformance for Storage Commitment SOP Class [141] Storage Commitment Operations (NACTION) The behavior of Storage AE when encountering status codes in an NACTION response is summarized in the table below: Table 2.29 STORAGE COMMITMENT NACTION RESPONSE STATUS HANDLING BEHAVIOR Service Further Status Meaning Error Code Behavior Success Success 0000 The request for storage commitment is considered successfully sent. A timer is started which will expire if no NEVENTREPORT for the Transaction UID is received within a configurable timeout period. * * Any other status code. The Association is aborted using AABORT and the request for storage commitment is marked as failed. 8 E1EEZ1592

15 Chapter 2 NETWORKING The behavior of Storage AE during communication failure is summarized in the table below: Table STORAGE COMMITMENT COMMUNICATION FAILURE BEHAVIOR Exception Behavior Timeout Association aborted by the SCP or network layers The Association is aborted using AABORT. The send job is marked as failed. [142] Storage Commitment Notifications (NEVENTREPORT) The Storage AE is capable of receiving an NEVENTREPORT notification if it has successfully negotiated a Presentation Context for the Storage Commitment Push Model. The reasons for returning specific status codes in an NEVENTREPORT response are summarized in the table below. Table STORAGE COMMITMENT NEVENTREPORT RESPONSE STATUS REASONS Service Further Status Meaning Error Code Reasons Success Success 0000 The storage commitment result has been successfully received. [15] SOP Specific Conformance for Verification SOP Class The Storage AE provides standard conformance to the Verification SOP Class as an SCP. If the CECHO request was successfully received, a 0000 (Success) status code will be returned in the CECHO response. Otherwise, a C000 (Error Cannot Understand) status code will be returned in the CECHO response. E1EEZ1592 9

16 Chapter 2 NETWORKING Workflow Application Entity Specification (1) SOP Classes Workflow AE provides Standard Conformance to the following SOP Classes: Table SOP CLASSES FOR AE WORKFLOW SOP Class Name SOP Class UID SCU SCP Modality Worklist Information Model FIND Yes No Modality Performed Procedure Step Yes No (2) Association Establishment Policies [1] General The DICOM standard application context name is always proposed: Table DICOM APPLICATION CONTEXT FOR AE WORKFLOW Application Context Name [2] Number of Associations Workflow AE initiates one Association at a time. Table NUMBER OF ASSOCIATIONS INITIATED FOR AE WORKFLOW Maximum number of simultaneous Associations 1 [3] Asynchronous Nature Workflow AE does not support asynchronous communication. Table ASYNCHRONOUS NATURE AS A SCU FOR AE WORKFLOW Maximum number of outstanding asynchronous transactions 1 [4] Implementation Identifying Information The implementation information for Workflow AE is: 10 E1EEZ1592

17 Chapter 2 NETWORKING Table DICOM IMPLEMENTATION CLASS AND VERSION FOR AE WORKFLOW Implementation Class UID Implementation Version Name HMC14.15 (3) Association Initiation Policy [1] Activity Query Worklist [11] Sequencing of Activities Workflow AE Department Scheduler 1. Query Worklists 2. Open Association 3. CFIND Request (Worklist Query) 4. CFIND Response (Worklist Item) Status=Pending 5. CFIND Response (Worklist Item) Status=Pending 6. CFIND Response Status=Success 7. Close Association 8. Select Worklist Item 9. Query Worklists 10. O pen Association 11. C FIND Request (Worklist Query) 12. C CANCEL FIND Request 13. C FIND Response Status=Cancel 14. Close Association Figure 2.22 Sequencing of Activity Query Worklist E1EEZ

18 Chapter 2 NETWORKING The sequence of interactions between the Workflow AE and a Departmental Scheduler is illustrated in the Figure above. [12] Proposed Presentation Contexts Workflow AE will propose Presentation Contexts as shown in the following table: Table PROPOSED PRESENTATION CONTEXTS FOR REALWORLD ACTIVITY QUERY WORKLIST Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Ext. Neg. Modality Worklist Information Implicit VR Little Endian SCU None Model FIND [13] SOP Specific Conformance for Modality Worklist SOP Class The behavior of Workflow AE when encountering status codes in a Modality Worklist CFIND response is summarized in the table below. Table MODALITY WORKLIST CFIND RESPONSE STATUS HANDLING BEHAVIOR Service Further Error Code Behavior Status Meaning Success Matching is complete 0000 The SCP has completed the matches. Worklist items are available for display or further processing. Refused Out of A700 The Association is aborted using AABORT. The Resources status meaning is logged. Any additional error information in the Response will be logged. Failed Identifier A900 The Association is aborted using AABORT. The does not status meaning is logged. Any additional error match SOP information in the Response will be logged. Class 12 E1EEZ1592

19 Chapter 2 NETWORKING Service Status Further Meaning Error Code Behavior Failed Unable to C000 CFFF The Association is aborted using AABORT. The Process status meaning is logged. Any additional error information in the Response will be logged. Cancel Matching FE00 If the query was cancelled due to too may worklist terminated items then the SCP has completed the matches. due to Worklist items are available for display or further Cancel processing. Otherwise, the Association is aborted request using AABORT and the worklist query is marked as failed. The status meaning is logged. Pending Matches are FF00 The worklist item contained in the Identifier is continuing collected for later display or further processing. Pending Matches are FF01 The worklist item contained in the Identifier is continuing collected for later display or further processing. Warning that The status meaning is logged. one or more Optional Keys were not supported * * Any other status code. The Association is aborted using AABORT. The status meaning is logged. Any additional error information in the Response will be logged. The behavior of Workflow AE during communication failure is summarized in the table below. Table MODALITY WORKLIST COMMUNICATION FAILURE BEHAVIOR Exception Behavior Timeout Association aborted by the SCP or network layers The Association is aborted using AABORT and the worklist query marked as failed. The reason is logged. The error message is displayed. The reason is logged. E1EEZ

20 Chapter 2 NETWORKING Acquired images will use the Study Instance UID specified for the Scheduled Procedure Step. If Scheduled Procedure Step has no Study Instance UID or an acquisition is unscheduled, a Study Instance UID will be generated by the system. The table below provides a description of the Worklist Matching Keys and specifies the attributes that are copied into the images. Unexpected attributes returned in a CFIND response are ignored. Nonmatching responses returned by the SCP due to unsupported optional matching keys are ignored. Table WORKLIST MATCHING KEYS Module Name Attribute Name Tag VR MK RK WS IS AS DK IOD SOP Common Specific Character Set (0008,0005) CS x Scheduled Procedure Step Scheduled Procedure Step Sequence > Scheduled Station AET (0040,0100) SQ x x (0040,0001) AE R x S S x > Scheduled Procedure (0040,0002) DA R x S/ S RV x Step Start Date RV > Scheduled Procedure Step Start Time (0040,0003) TM R x RV x > Modality (0008,0060) CS R x S S x > Scheduled Performing Physician s Name > Scheduled Procedure Step Description > Scheduled Station Name > Scheduled Procedure Step Location > Scheduled Protocol Code Sequence (0040,0006) PN R x W W x (0040,0007) LO x x x (0040,0010) SH x x (0040,0011) SH x x (0040,0008) SQ x x x > PreMedication (0040,0012) LO x x > Scheduled Procedure Step ID (0040,0009) SH x x x 14 E1EEZ1592

21 Chapter 2 NETWORKING Module Name Attribute Name > Requested Contrast Agent Tag VR MK RK WS IS AS DK IOD (0032,1070) LO x x Requested Procedure Requested Procedure ID (0040,1001) SH x S S x x Requested Procedure Description Requested Procedure Code Sequence (0032,1060) LO x x x (0032,1064) SQ x x x Study Instance UID (0020,000D) UI x x x Referenced Study Sequence Requested Procedure Priority Patient Transport Arrangements Name of Intended Recipients of Results (0008,1110) SQ x x x (0040,1003) SH x x (0040,1004) LO x x (0040,1010) PN x x x Imaging Service Request Accession Number (0008,0050) SH x S S x x Requesting Physician (0032,1032) PN x x x Referring Physician's Name (0008,0090) PN x x x Requesting Service (0032,1033) LO x x x Visit Identification Admission ID (0038,0010) LO x x x Visit Status Current Patient Location (0038,0300) LO x x Visit Relationship Referenced Patient Sequence (0008,1120) SQ x x x E1EEZ

22 Chapter 2 NETWORKING Module Name Attribute Name Tag VR MK RK WS IS AS DK IOD Patient Identification Patient s Name (0010,0010) PN R x W W x x Patient ID (0010,0020) LO R x S S x x Other Patient IDs (0010,1000) LO x x x Patient Demographic Patient s Birth Date (0010,0030) DA x x x Patient s Sex (0010,0040) CS x x x Patient s Weight (0010,1030) DS x x x Confidentiality constraint on patient data (0040,3001) LO x x Patient s Size (0010,1020) DS x x x Ethnic Group (0010,2160) SH x x x Patient Comments (0010,4000) LT x x x Patient s Age (0010,1010) AS x x x Patient Medical Patient State (0038,0500) LO x x x Pregnancy Status (0010,21C0) US x x x Medical Alerts (0010,2000) LO x x x Contrast Allergies (0010,2110) LO x x x Special Needs (0038,0050) LO x x x Additional Patient History (0010,21B0) LT x x x Last Menstrual Date (0010,21D0) DA x x x The above table should be read as follows: Module Name: The name of the associated module for supported worklist attributes. Attribute Name: Attributes supported to build a Matching Keys. Tag: VR: DICOM tag for this attribute. DICOM VR for this attribute. 16 E1EEZ1592

23 Chapter 2 NETWORKING S: DICOM Single value matching. RV: DICOM Range value matching. W: DICOM Wild card matching. "*" or "?" can be set. MK: RK: WS: IS: AS: DK: IOD: Matching keys for Query Worklist. An "R" will indicate that Workflow AE will supply an attribute value for Required Matching key. This is set as a matching key by default in the Matching Key window. Return keys. An "x" will indicate that Workflow AE will supply this attribute as Return Key with zero length for Universal Matching. Worklist query setting. An "S" or "RV" will indicate that Workflow AE will supply this attribute as matching key, if set in the Worklist query setting window. This is for the Broad Queries. For example, the combination of Scheduled Date, Modality and AE Title can be entered thereby restricting Worklist responses. Interactive Search. An "S" or "W" will indicate that Workflow AE will supply this attribute as matching key, if entered in the Search item in the Worklist tab on a Patient Information window. For example, the Patient Name can be entered thereby restricting Worklist responses. Advanced Search. An "S", "RV" or "W" will indicate that Workflow AE will supply this attribute as matching key, if entered in the Advanced Search window. For example, the Combination of Patient ID and Patient Name can be entered thereby restricting Worklist responses. Displayed keys. An "x" indicates that this Return Key attribute is displayed to the user during a Detail Information window. An "x" indicates that this Worklist attribute is included into all Object Instances created during performance of the related Procedure Step. E1EEZ

24 Chapter 2 NETWORKING [2] Activity Start Exam and End Exam [21] Sequencing of Activities Workflow AE Department Scheduler 1. Start Exam 2. Open Association 3. N CREATE (MPPS) IN PROGRESS 4. Close Association 5. Acquire Images 6. End Exam 7. Open Association 8. N SET (MPPS) COMPLETED/DISCONTINUED 9. Close Association Figure 2.23 Sequencing of Activity Start Exam and End Exam The sequence of interactions between the Workflow AE and a Departmental Scheduler is illustrated in the Figure above. 18 E1EEZ1592

25 Chapter 2 NETWORKING [22] Proposed Presentation Contexts Workflow AE will propose Presentation Contexts as shown in the following table: Table PROPOSED PRESENTATION CONTEXTS FOR REALWORLD ACTIVITY Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Ext. Neg. Modality Performed Procedure Step Implicit VR Little Endian SCU None [23] SOP Specific Conformance for MPPS SOP Class The behavior of Workflow AE when encountering status codes in an MPPS NCREATE or N SET response is summarized in table below. Table MPPS NCREATE / NSET RESPONSE STATUS HANDLING BEHAVIOR Service Further Status Meaning Error Code Behavior Success Success 0000 The SCP has completed the operation successfully. * * Any other status code. The SCP has completed the operation successfully. The behavior of Workflow AE during communication failure is summarized in the table below. Table MPPS COMMUNICATION FAILURE BEHAVIOR Exception Behavior Timeout Association aborted by the SCP or network layers The Association is aborted using AABORT. The reason is logged. The Association is aborted using AABORT. The reason is logged. E1EEZ

26 Chapter 2 NETWORKING Table below provides a description of the MPPS NCREATE and NSET request identifiers. "X" will indicate that the attribute is not sent in the NCREATE and NSET columns. Table MPPS NCREATE / NSET REQUEST IDENTIFIER Attribute Name Specific Character Set Scheduled Step Attributes Sequence Tag VR NCREATE NSET (0008,0005) CS AUTO generated. X (0040,0270) SQ From MWL. X > Study Instance UID (0020,000D) UI From MWL or AUTO generated. X > Referenced Study Sequence >> Referenced SOP Class UID >> Referenced SOP Instance UID (0008,1110) SQ From MWL. X (0008,1150) UI From MWL. X (0008,1155) UI From MWL. X From MWL or USER input on the Patient > Accession Number (0008,0050) SH Information window. The user can modify X values provided via Modality Worklist. > Requested Procedure ID > Requested Procedure Description > Scheduled Procedure Step ID (0040,1001) SH From MWL. X (0032,1060) LO From MWL. X (0040,0009) SH From MWL. X 20 E1EEZ1592

27 Chapter 2 NETWORKING Attribute Name > Scheduled Procedure Step Description > Scheduled Protocol Code Sequence Tag VR NCREATE NSET (0040,0007) LO From MWL. X (0040,0008) SQ From MWL. X >> Code Value (0008,0100) SH From MWL. X >> Coding Scheme Designator >> Coding Scheme Version >> Code Meaning ( ) SH From MWL. X (0008,0103) SH From MWL. X (0008,0104) LO From MWL. X Patient s Name (0010,0010) PN Patient ID (0010,0020) LO From MWL or user input on the Patient Information window. The user can modify values provided via Modality Worklist. From MWL, user input on the Patient Information window or auto generated. The user can modify values provided via Modality Worklist. X X From MWL or user input on the Patient Patient s Birth Date (0010,0030) DA Information window. The user can modify X values provided via Modality Worklist. E1EEZ

28 Chapter 2 NETWORKING Attribute Name Tag VR NCREATE NSET Patient s Sex (0010,0040) CS From MWL or user input on the Patient Information window. The user can modify values provided via Modality Worklist. X Admission ID (0038,0010) LO From MWL. X Referenced Patient Sequence > Referenced SOP Class UID > Referenced SOP Class UID Performed Procedure Step ID (0008,1120) SQ From MWL. X (0008,1150) UI From MWL. X (0008,1155) UI From MWL. X (0040,0253) SH AUTO generated. X Performed USER input "AE Title" Station AE (0040,0241) AE on the Setup Filing X Title window. Performed Station Name (0040,0242) SH User input "Computer Name" on the System Settings window. X Performed Location (0040,0243) SH USER input "Hospital Name" on the System Settings window. X Performed Procedure Step Start Date Performed Procedure Step Start Time (0040,0244) DA AUTO generated. X (0040,0245) TM AUTO generated. X Performed Procedure Step Status (0040,0252) CS "IN PROGRESS" "DISCONTINUED" or "COMPLETED" 22 E1EEZ1592

29 Chapter 2 NETWORKING Attribute Name Tag VR NCREATE NSET From MWL Scheduled Procedure Step From MWL Scheduled Performed Description Procedure Step Description Procedure Step (0040,0254) LO (0040,0007) or USER (0040,0007) or USER input Description input from Study from Study Description Description (0008,1030). (0008,1030). Performed Procedure Type Description (0040,0255) LO Zero length. X Procedure Code Sequence (0008,1032) SQ From MWL Requested Procedure Code Sequence (0032,1064). From MWL Requested Procedure Code Sequence (0032,1064). > Code Value (0008,0100) SH From MWL Requested Procedure Code Sequence (0032,1064). From MWL Requested Procedure Code Sequence (0032,1064). > Coding From MWL Requested From MWL Requested Scheme ( ) SH Procedure Code Procedure Code Sequence Designator Sequence (0032,1064). (0032,1064). > Coding From MWL Requested From MWL Requested Scheme (0008,0103) SH Procedure Code Procedure Code Sequence Version Sequence (0032,1064). (0032,1064). > Code Meaning (0008,0104) LO From MWL Requested Procedure Code Sequence (0032,1064). From MWL Requested Procedure Code Sequence (0032,1064. Performed Procedure Step End Date Performed Procedure Step End Time (0040,0250) DA Zero length. AUTO generated. (0040,0251) TM Zero length. AUTO generated. Modality (0008,0060) CS US X Study ID (0020,0010) SH AUTO generated. X E1EEZ

30 Chapter 2 NETWORKING Attribute Name Performed Protocol Code Sequence Performed Series Sequence > Performing Physician s Name > Protocol Name Tag VR NCREATE NSET (0040,0260) SQ Zero length. X (0040,0340) SQ Zero length. AUTO generated. (0008,1050) PN X Zero length. (0018,1030) LO X AUTO generated. > Operator s Name (0008,1070) PN X USER input "Examined by" on the Patient Information window. > Series Instance UID > Series Description (0020,000E) UI X AUTO generated. (0008,103E) LO X Zero length. > Retrieve AE Title (0008,0054) AE X USER input "AE Title" on the Setup Filing window. > Referenced Image Sequence >> Referenced SOP Class UID >> Referenced SOP Instance UID > Referenced NonImage Composite SOP Instance Sequence (0008,1140) SQ X AUTO generated. (0008,1150) UI X AUTO generated. (0008,1155) UI X AUTO generated. (0040,0220) SQ X Zero length. 24 E1EEZ1592

31 Chapter 2 NETWORKING (4) Association Acceptance Policy The Workflow AE does not accept Associations Hardcopy Application Entity Specification (1) SOP Classes Hardcopy AE provides Standard Conformance to the following SOP Classes: Table SOP CLASSES FOR AE HARDCOPY SOP Class Name SOP Class UID SCU SCP Basic Grayscale Print Management Meta Yes No Basic Color Print Management Meta Yes No (2) Association Establishment Policies [1] General The DICOM standard application context name is always proposed: Table DICOM APPLICATION CONTEXT FOR AE HARDCOPY Application Context Name [2] Number of Associations Hardcopy AE initiates one Association at a time. Table NUMBER OF ASSOCIATIONS INITIATED FOR AE HARDCOPY Maximum number of simultaneous Associations (number of configured hardcopy devices) [3] Asynchronous Nature Hardcopy AE does not support asynchronous communication. Table ASYNCHRONOUS NATURE AS A SCU FOR AE HARDCOPY Maximum number of outstanding asynchronous transactions 1 [4] Implementation Identifying Information The implementation information for this Application Entity is: E1EEZ

32 Chapter 2 NETWORKING Table DICOM IMPLEMENTATION CLASS AND VERSION FOR AE HARDCOPY Implementation Class UID Implementation Version Name HMC14.15 (3) Association Initiation Policy [1] Activity Film Images [11] Sequencing of Activities Hardcopy AE Printer 1. Film Images 2. Open Association 3. N GET (Printer) 4. N CREATE (Film Session) 5. N CREATE (Film Box) 6. N SET (Image Box) 7. N ACTION (Film Box) 8. Print film sheets 9. N DELETE (Film Session) 10. Close Association Figure 2.24 SEQUENCING OF ACTIVITY FILM IMAGES The sequence of interactions between the Hardcopy AE and a Printer is illustrated in Figure above: 26 E1EEZ1592

33 Chapter 2 NETWORKING [12] Proposed Presentation Contexts Hardcopy AE will propose the Presentation Contexts shown in the following table. Table PROPOSED PRESENTATION CONTEXTS FOR REALWORLD ACTIVITY FILM IMAGES Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Ext. Neg. Basic Grayscale Print Management Implicit VR Little Endian SCU None Meta Basic Color Print Management Implicit VR Little Endian SCU None Meta [13] Common SOP Specific Conformance for all Print SOP Classes The behavior of Hardcopy AE during communication failure is summarized in the table below. This behavior is common for all SOP Classes supported by Hardcopy AE. Table HARDCOPY COMMUNICATION FAILURE BEHAVIOR Exception Behavior Timeout Association aborted by the SCP or network layers The Association is aborted using AABORT. The Association is aborted using AABORT. [14] SOP Specific Conformance for the Printer SOP Class Hardcopy AE supports the following DIMSE operations and notifications for the Printer SOP Class. NGET NEVENTREPORT Details of the supported attributes and status handling behavior are described in the following subsections. E1EEZ

34 Chapter 2 NETWORKING [141] Printer SOP Class Operations (NGET) Hardcopy AE uses the Printer SOP Class NGET operation to obtain information about the current printer status. The attributes obtained via NGET are listed in the table below. Table PRINTER SOP CLASS NGET REQUEST ATTRIBUTES Attribute Name Tag VR Value Presence of Value Source Printer Status (2110,0010) CS Provided by Printer ALWAYS Printer Printer Status Info (2110,0020) CS Provided by Printer ALWAYS Printer The behavior of Hardcopy AE when encountering status codes in a NGET response is summarized in the table below: Table PRINTER SOP CLASS NGET RESPONSE STATUS HANDLING BEHAVIOR Service Further Status Meaning Error Code Behavior Success Success 0000 The request to get printer status information was success. * * Any other status code. The Association is aborted using AABORT. [142] Printer SOP Class Notifications (NEVENTREPORT) Hardcopy AE is capable of receiving an NEVENTREPORT request at any time during an association. The behavior of Hardcopy AE when receiving Event Types within the NEVENTREPORT is summarized in the table below: Table PRINTER SOP CLASS NEVENTREPORT BEHAVIOUR Event Type Name Event Type ID Behavior Normal 1 The printjob continues to be printed. Warning 2 The printjob continues to be printed. The contents of Printer Status Info (2110,0020) is logged. Failure 3 The printjob is marked as failed. The contents of Printer Status Info (2110,0020) is logged. * * An invalid Event Type ID will cause a status code of 0113H to be returned in a NEVENTREPORT response. 28 E1EEZ1592

35 Chapter 2 NETWORKING The reasons for returning specific status codes in an NEVENTREPORT response are summarized in the table below: Table PRINTER SOP CLASS NEVENTREPORT RESPONSE STATUS REASONS Service Further Error Reasons Status Meaning Code Success Success 0000 The notification event has been successfully received. Failure No Such 0113H An invalid Event Type ID was supplied in the Event Type NEVENTREPORT request. Failure Processing 0110H An internal error occurred during processing of the Failure NEVENTREPORT. A short description of the error will be returned in Error Comment (0000,0902). [15] SOP Specific Conformance for the Film Session SOP Class Hardcopy AE supports the following DIMSE operations for the Film Session SOP Class: NCREATE NDELETE Details of the supported attributes and status handling behavior are described in the following subsections. [151] Film Session SOP Class Operations (NCREATE) The attributes supplied in an NCREATE Request are listed in the table below: Table FILM SESSION SOP CLASS NCREATE REQUEST ATTRIBUTES Attribute Name Tag VR Value Presence of Value Source Number of Copies (2000,0010) IS "1".. "10" ALWAYS USER Print Property (2000,0020) CS "MED" ALWAYS AUTO Medium Type (2000,0030) CS "BLUE FILM", "CLEAR FILM" or "PAPER" ALWAYS USER Film Destination (2000,0040) CS "MAGAZINE", "PROCESSOR" or "BIN_1".. "BIN_10" ALWAYS USER E1EEZ

36 Chapter 2 NETWORKING The behavior of Hardcopy AE when encountering status codes in an NCREATE response is summarized in the table below: Table FILM SESSION SOP CLASS NCREATE RESPONSE STATUS HANDLING BEHAVIOR Service Status Further Meaning Error Code Behavior Success Success 0000 The SCP has completed the operation successfully. Warning Attribute Value Out 0116H The NCREATE operation is of Range considered successful. Warning Attribute List Error 0107H The NCREATE operation is considered successful. * * Any other status code. The Association is aborted using AABORT. [152] Film Session SOP Class Operations (NDELETE) The behavior of Hardcopy AE when encountering status codes in an NDELETE response is summarized in the table below: Table PRINTER SOP CLASS NDELETE RESPONSE STATUS HANDLING BEHAVIOR Service Further Status Meaning Error Code Behavior Success Success 0000 The SCP has completed the operation successfully. * * Any other status code. The Association is aborted using AABORT. [16] SOP Specific Conformance for the Film Box SOP Class Hardcopy AE supports the following DIMSE operations for the Film Box SOP Class: NCREATE NACTION Details of the supported attributes and status handling behavior are described in the following subsections. 30 E1EEZ1592

37 Chapter 2 NETWORKING [161] Film Box SOP Class Operations (NCREATE) The attributes supplied in an NCREATE Request are listed in the table below: Table FILM BOX SOP CLASS NCREATE REQUEST ATTRIBUTES Attribute Name Tag VR Value Presence of Value Source Image Display Format Referenced Film Session Sequence >Referenced SOP Class UID (2010,0010) CS "STANDARD\C,R" ALWAYS USER (2010,0500) SQ ALWAYS AUTO (0008,1150) UI " " ALWAYS AUTO >Referenced SOP Instance UID (0008,1155) UI From created Film Session SOP Instance ALWAYS AUTO Film Orientation (2010,0040) CS "PORTRAIT" or "LANDSCAPE" ALWAYS USER "8INX10IN", "8_5INX11IN", "10INX12IN", "10INX14IN", Film Size ID (2010,0050) CS "11INX14IN", "11INX17IN", "14INX14IN", "14INX17IN", ALWAYS USER "24CMX24CM", "24CMX30CM", "A4", "A3" Magnification Type (2010,0060) CS "REPLICATE", "BILINEAR", "CUBIC" or" NONE" ANAP USER Border Density (2010,0100) CS "BLACK" or "WHITE" ANAP USER Empty Image Density (2010,0110) CS "BLACK" or "WHITE" ANAP USER Max Density (2010,0130) US "0.1".. "3.0" ANAP USER Min Density (2010,0120) US "0.0".. "2.9" ANAP USER Trim (2010,0130) CS "YES" or "NO" ANAP USER The behavior of Hardcopy AE when encountering status codes in an NCREATE response is summarized in the table below: E1EEZ

38 Chapter 2 NETWORKING Table FILM BOX SOP CLASS NCREATE RESPONSE STATUS HANDLING BEHAVIOR Service Status Further Meaning Error Code Behavior Success Success 0000 The SCP has completed the operation successfully. Warning Requested Min Density or Max B605H The NCREATE operation Density outside of printer s is considered successful. operating range * * Any other status code. The Association is aborted using AABORT. [162] Film Box SOP Class Operations (NACTION) An NACTION Request is issued to instruct the Print SCP to print the contents of the Film Box. The Action Reply argument in an NACTION response is not evaluated. The behavior of Hardcopy AE when encountering status codes in an NACTION response is summarized in the table below: Table FILM BOX SOP CLASS NACTION RESPONSE STATUS HANDLING BEHAVIOR Service Error Further Meaning Status Code Behavior Success Success 0000 The SCP has completed the operation successfully. The film has been accepted for printing. Warning Film Box SOP Instance hierarchy B603H The Association is aborted does not contain Image Box SOP using AABORT. Instances (empty page) Warning Image size is larger than Image Box B604H The NACTION operation is size. The image has been considered successful. demagnified. Warning Image size is larger than Image Box B609H The NACTION operation is size. The image has been cropped to considered successful. fit. 32 E1EEZ1592

39 Chapter 2 NETWORKING Service Status Further Meaning Error Code Behavior Warning Image size or Combined Print Image B60AH The NACTION operation is Size is larger than Image Box size. considered successful. The image or combined Print Image has been decimated to fit. Failure Unable to create Print Job SOP C602 The Association is aborted Instance; print queue is full. using AABORT. Failure Image size is larger than Image Box C603 The Association is aborted size. using AABORT. Failure Combined Print Image Size is larger C613 The Association is aborted than Image Box size. using AABORT. * * Any other status code. The Association is aborted using AABORT. [17] SOP Specific Conformance for the Image Box SOP Class Hardcopy AE supports the following DIMSE operations for the Image Box SOP Class: NSET Details of the supported attributes and status handling behavior are described in the following subsections. [171] Image Box SOP Class Operations (NSET) The attributes supplied in an NSET Request are listed in the table below: Table IMAGE BOX SOP CLASS NSET REQUEST ATTRIBUTES Attribute Name Tag VR Value Presence of Value Source Image Position (2020,0010) US ALWAYS AUTO Basic Grayscale Image Sequence (2020,0110) SQ ALWAYS AUTO >Samples Per Pixel (0028,0002) US "1" ALWAYS AUTO >Photometric Interpretation (0028,0004) CS "MONOCHROME2" ALWAYS AUTO >Rows (0028,0010) US Depends on image. ALWAYS AUTO E1EEZ

40 Chapter 2 NETWORKING Attribute Name Tag VR Value Presence of Value Source >Columns (0028,0011) US Depends on image. ALWAYS AUTO >Pixel Aspect Ratio (0028,0034) IS Depends on image. ALWAYS AUTO >Bits Allocated (0028,0100) US Depends on image. ALWAYS AUTO >Bits Stored (0028,0101) US Depends on image. ALWAYS AUTO >High Bit (0028,0102) US Depends on image. ALWAYS AUTO >Pixel Representation (0028,0103) US Depends on image. ALWAYS AUTO >Pixel Data (7FE0,0010) OB Depends on image. ALWAYS AUTO Basic Color Image Sequence (2020,0111) SQ ALWAYS AUTO >Samples Per Pixel (0028,0002) US "3" ALWAYS AUTO >Photometric Interpretation (0028,0004) CS "RGB" ALWAYS AUTO >Planar Configuration (0028,0006) CS "0" ALWAYS AUTO >Rows (0028,0010) US Depends on image. ALWAYS AUTO >Columns (0028,0011) US Depends on image. ALWAYS AUTO >Pixel Aspect Ratio (0028,0034) IS Depends on image. ALWAYS AUTO >Bits Allocated (0028,0100) US Depends on image. ALWAYS AUTO >Bits Stored (0028,0101) US Depends on image. ALWAYS AUTO >High Bit (0028,0102) US Depends on image. ALWAYS AUTO >Pixel Representation (0028,0103) US Depends on image. ALWAYS AUTO >Pixel Data (7FE0,0010) OB Depends on image. ALWAYS AUTO 34 E1EEZ1592

41 Chapter 2 NETWORKING The behavior of Hardcopy AE when encountering status codes in an NSET response is summarized in the table below: Table IMAGE BOX SOP CLASS NSET RESPONSE STATUS HANDLING BEHAVIOR Service Error Further Meaning Status Code Behavior Success Success 0000 The SCP has completed the operation successfully. Image successfully stored in Image Box. Warning Image size is larger than Image Box B604H The NSET operation is size. The image has been considered successful. demagnified. Warning Requested Min Density or Max B605H The NSET operation is Density outside of printer s operating considered successful. range. Warning Image size is larger than Image Box B609H The NSET operation is size. The image has been cropped considered successful. to fit. Warning Image size or Combined Print Image B60AH The NSET operation is Size is larger than Image Box size. considered successful. The image or combined Print Image has been decimated to fit. Failure Image size is larger than Image Box C603 The Association is aborted size. using AABORT. Failure Insufficient memory in printer to C605 The Association is aborted store the image. using AABORT. Failure Combined Print Image Size is larger C613 The Association is aborted than Image Box size. using AABORT. * * Any other status code. The Association is aborted using AABORT. E1EEZ

42 Chapter 2 NETWORKING Query/Retrieve Application Entity Specification (1) SOP Classes Query/Retrieve AE provides Standard Conformance to the following SOP Classes: Table SOP CLASSES FOR AE QUERY/RETRIEVE SOP Class Name SOP Class UID SCU SCP Study Root Information Model FIND Yes No Study Root Information Model MOVE Yes No Ultrasound Image Storage No Yes Ultrasound Image Storage (Retired) No Yes Ultrasound Multiframe Image Storage No Yes Ultrasound Multiframe Image Storage (Retired) No Yes CT Image Storage No Yes MR Image Storage No Yes Secondary Capture Image Storage No Yes 36 E1EEZ1592

43 Chapter 2 NETWORKING (2) Association Establishment Policies [1] General The DICOM standard application context name is always proposed: Table DICOM APPLICATION CONTEXT FOR AE QUERY/RETRIEVE Application Context Name [2] Number of Associations Query/Retrieve AE initiates one Association at a time. Table NUMBER OF ASSOCIATIONS INITIATED FOR AE QUERY/RETRIEVE Maximum number of simultaneous Associations 1 [3] Asynchronous Nature Query/Retrieve AE does not support asynchronous communication. Table ASYNCHRONOUS NATURE AS A SCU FOR AE QUERY/RETRIEVE Maximum number of outstanding asynchronous transactions 1 [4] Implementation Identifying Information The implementation information for this Application Entity is: Table DICOM IMPLEMENTATION CLASS AND VERSION FOR AE QUERY/RETRIEVE Implementation Class UID Implementation Version Name HMC14.15 E1EEZ

44 Chapter 2 NETWORKING (3) Association Initiation Policy [1] Activity Query Image Information and Retrieve Images [11] Sequencing of Activities Q/R AE Image Manager SCP Image Manager SCU 1. Query Image Information 2. Open Association 3. CFIND Request (Study Root) 4. CFIND Response (Image Information) Status=Pending 5. CFIND Response (Image Information) Status=Pending 6. CFIND Response? Status=Pending 7. Close Association 8. Retrieve Images 9. Open Association 10. CMOVE Request (Images) 11. Open Association 12. CStore Request 13. C MOVE Response (Image) Status=Pending 14. CStore Response Status=Success 15. Close Association 16. C MOVE Response (Image) Status=Success 17. Close Association Figure 2.25 SEQUENCING OF ACTIVITY QUERY IMAGE INFORMATION AND RETRIEVE IMAGES 38 E1EEZ1592 The sequence of interactions between the Query/Retrieve AE and an Image Manager is illustrated in Figure above.

45 Chapter 2 NETWORKING [12] Proposed Presentation Contexts Query/Retrieve AE will propose the Presentation Contexts shown in the following table. Table Proposed Presentation Contexts for RealWorld Activity Query Image Information Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Ext. Neg. Study Root Information Model FIND Study Root Information Implicit VR Little Endian SCU None Model MOVE Table Proposed Presentation Contexts for RealWorld Activity Retrieve Images Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name UID List List Role Ext. Neg. Ultrasound Image Implicit VR SCP None Storage Little Ultrasound Image Storage (Retired) Ultrasound Multiframe Image Storage Endian Explicit VR Little Endian JPEG Lossy Baseline E1EEZ

46 Chapter 2 NETWORKING Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Ext. Neg. Ultrasound Multiframe Image Storage (Retired) RLE Lossless CT Image Storage Implicit VR MR Image Storage Secondary Capture Image Storage Little Endian Explicit VR Little Endian SCP None [13] SOP Specific Conformance for Query/Retrieve SOP Class The behavior of Query/Retrieve AE when encountering status codes in a Query Image Information CFIND response is summarized in the table below. Table QUERY IMAGE INFORMATION CFIND RESPONSE STATUS HANDLING BEHAVIOR Service Further Error Code Behavior Status Meaning Success Matching is complete 0000 The SCP has completed the matches. Worklist items are available for display or further processing. * * Any other status code. The Association is aborted using AABORT. The behavior of Query/Retrieve AE during communication failure is summarized in the table below: 40 E1EEZ1592

47 Chapter 2 NETWORKING Table QUERY/RETRIEVE COMMUNICATION FAILURE BEHAVIOR Exception Behavior Timeout Association aborted by the SCP or network layers The Association is aborted using AABORT. The Association is aborted using AABORT. The table below provides a description of the Study Root Query/Retrieve Information Model. Unexpected attributes returned in a CFIND response are ignored. Nonmatching responses returned by the SCP due to unsupported optional matching keys are ignored. Table STUDY ROOT QUERY/RETRIEVE INFORMATION MODEL Query/Retrieve Level Attribute Name Tag VR MK RK IS DK Study Level Keys Study Date (0008,0020) DA R x S x Study Time (0008,0030) TM R x x Accession Number (0008,0050) SH R x R x Patient s Name (0010,0010) PN x W x Patient ID (0010,0020) LO x S x Study ID (0020,0010) SH R x x Study Instance UID (0020,000D) UI x Modalities in Study (0008,0061) CS x S x Referring Physician s Name (0008,0090) PN x x Study Description (0008,1030) LO x x Patient s Birth Date (0010,0030) DA x x Patient s Sex (0010,0040) CS x x Series Level Keys Modality (0008,0060) CS R x S x Series Number (0020,0011) IS R x x Series Instance UID (0020,000E) UI x L Body Part Examined (0018,0015) CS x x Series Description (0008,103E) LO x x E1EEZ