DICOM Conformance Statement
Contents
1. 0028 0034 gt Bits Allocated 0028 0100 8 gt Bits Stored 0028 0101 8 gt High Bit 0028 0102 7 gt Pixel Representation 0028 0103 000H unsigned integer gt Pixel Data 7FE0 0010 Other Byte String 2 2 3 3 1 2 1 4 Printer SOP Class Attributes The UDI Print AE makes use of the following attributes and attributes values in this SOP class Attribute Name Tag Supported Values Printer Status 2110 0010 NORMAL WARNING FAILURE Printer Status Info 2110 0020 SUPPLY EMPTY SUPPLY LOW RECEIVER FULL Revision 1 0 MERIDIAN Medical Systems Document No f dk Page 32 of 56 Title Meridian UDI DICOM Conformance Statement rev 1 0 208 Revision 1 0 FILM JAM Printer Name 2110 0030 Long String Manufacturer 0008 0070 Long String Manufacturer Model Name 0008 1090 Long String Device Serial Number 0018 1000 Long String Software Versions 0018 1020 Long string s 2 2 3 4 Association Acceptance Policy The Print AE does not accept Associations 2 2 4 MPPS AE Specification The UDI AE is used to transmit performed procedure step events which are N CREATE and N SET to a remote DICOM device It performs the followings Establishes a DICOM Association with a remote DICOM device Sends DICOM MPPS Information to a remote DICOM device The UDI AE is a service class user SCU for2. MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Page aak Revision 1 0 Magnification Type 2010 0060 REPLICATE BILINEAR CUBIC NONE Smoothing Type 2010 0080 SCP specific Border Density 2010 0100 BLACK WHITE I where I represents the desired density in hundredths of OD BLACK WHITE I where I represents the desired Empi image Density eve density in hundredths of OD Min Density 2010 0120 Unsigned short Max Density 2010 0130 Unsigned short Trim 2010 0140 YES NO Configuration 2010 0150 SCP specific Information 2 2 3 3 1 2 1 3 Basic Grayscale Image Box SOP Class Attributes The UDI Print AE supports the following mandatory and optional attribute values in this SOP class Attribute Name Tag Supported Values Image Position 2020 0010 Unsigned short Polarity 2020 0020 NORMAL REVERSE Magnification Type 2020 0060 REPLICATE BILINEAR CUBIC NONE Smoothing Type 2020 0080 SCP specific Requested Image Size 2020 0030 Unsigned short Sequence gt Samples Per Pixel 0028 0002 1 ae 0028 0004 MONOCHROME1 MONOCHROME 2 Interpretation gt Planar configuration 0028 0006 1 gt Rows 0028 0010 Unsigned short gt Columns Unsigned short gt Pixel Aspect Ratio 1 1 0028 0034
3. ALWAYS AUTO Performed Station AE Title 0040 0241 AE ALWAYS AUTO Performed Station Name 0040 0242 SH ALWAYS AUTO Performed Location 0040 0243 SH ALWAYS AUTO Performed Procedure Step Start Date 0040 0244 DA ALWAYS AUTO Performed Procedure Step Start Time 0040 0245 TM ALWAYS AUTO Performed Procedure Step End Date 0040 0250 DA ALWAYS AUTO Performed Procedure Step End Time 0040 0251 TM ALWAYS AUTO Performed Procedure Step Status 0040 0252 CS IN PROGRESS ALWAYS AUTO Performed Procedure Step ID 0040 0253 SH ALWAYS AUTO Performed 0040 0254 LO ALWAYS AUTO Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Page 53 of 56 Revision 1 0 Procedure Step Description Performed 0040 0255 LO Procedure Step Type Description ALWAYS AUTO Performed 0040 0260 SQ Action Item Code Sequence ALWAYS AUTO gt Code Value 0008 0100 SH ALWAYS AUTO gt Coding 0008 0102 SH Scheme Designator ALWAYS AUTO gt Coding 0008 0103 SH Scheme Version ALWAYS AUTO gt Code 0008 0104 LO Meaning ALWAYS AUTO Performed 0040 0340 SQ Series Sequence ALWAYS AUTO gt Retrieve AE
4. Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage AE Revision 1 0 Procedure Step Start Date Performed 0040 0245 TM ALWAYS AUTO Procedure Step Start Time Performed 0040 0253 SH ANAP AUTO Procedure Step ID Performed 0040 0254 LO ALWAYS AUTO Procedure Step Description Organ Dose 0040 0316 DS ALWAYS AUTO Organ 0040 0318 CS ALWAYS AUTO Exposed Acquisition 0040 0555 SQ Empty Sequence ALWAYS AUTO Context Sequence Entrance Dose 0040 8302 DS ALWAYS AUTO in mGy View Code 0054 0220 SQ ALWAYS AUTO Sequence gt Code Value 0008 0100 SH ALWAYS AUTO gt Coding 0008 0102 SH ALWAYS AUTO Scheme Designator gt Code 0008 0104 LO ALWAYS AUTO Meaning gt View Modifier 0054 0222 SQ ALWAYS AUTO Code Sequence gt gt Code Value 0008 0100 SH ALWAYS AUTO gt gt Coding 0008 0102 SH ALWAYS AUTO Scheme Designator gt gt Code 0008 0104 LO ALWAYS AUTO Meaning Patient 0054 0410 SQ ALWAYS AUTO Orientation Code Sequence gt Code Value 0008 0100 SH ALWAYS AUTO gt Coding 0008 0102 SH ALWAYS AUTO Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Page score Revision 1 0
5. MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage noe Revision 1 0 MERIDIAN Medical Systems 325 Harris Drive Aurora Ohio 44202 Office 440 287 6801 Fax 440 287 6723 http www meridianmed net UDI Doc DICOM Conformance Statement Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage cAI Revision 1 0 Overview This document describes the DICOM v3 0 implementation supported by UDI 1 0 It documents conformance aspects required to interoperate with other DICOM v3 0 conformant devices The UDI implements the necessary DICOM services to download work lists from an information system to send MPPS messages to a network MPPS server to save commit acquired DX images to a network storage device to print acquired images to DICOM printers and to write to DICOM removable media Table 1 lists the supported Networking DICOM Service SOP classes SOP Classes User of Service Provider of SCU Service SCP Transfer Digital X Ray Image Storage For Presentation YES NO 1 2 840 10008 5 1 4 1 1 1 1 Digital X Ray Image Storage For Processing YES NO 1 2 840 10008 5 1 4 1 1 1 1 1 Grayscale Softcopy Presentation State Storage YES NO 1 2 840 10008 5 1 4 1 1 11 1 Workflow Management Storage Commitment Push Model YES
6. Title Meridian UDI DICOM Conformance Statement rev 1 0 Fage 0100 Revision 1 0 Date MWL Patient s Sex 0010 0040 CS VNAP USER or MWL KVP 0018 0060 DS ALWAYS AUTO Device Serial 0018 1000 LO ALWAYS AUTO Number Software 0018 1020 LO ALWAYS AUTO Versions Protocol Name 0018 1030 LO ALWAYS AUTO Distance 0018 1110 DS ALWAYS AUTO Source to Detector Exposure Time 0018 1150 IS ALWAYS AUTO X Ray Tube 0018 1151 IS ALWAYS AUTO Current Exposure 0018 1152 IS ALWAYS AUTO Imager Pixel 0018 1164 DS ALWAYS AUTO Spacing Focal Spot 0018 1190 DS ALWAYS AUTO Positioner 0018 1508 CS Length 0 ALWAYS AUTO Type View Position 0018 5101 CS ALWAYS AUTO Projection 0018 5104 SQ ALWAYS AUTO Eponymous Name Code Sequence gt Code Value 0008 0100 SH ALWAYS AUTO gt Coding 0008 0102 SH ALWAYS AUTO Scheme Designator gt Code 0008 0104 LO ALWAYS AUTO Meaning Detector Type 0018 7004 CS DIRECT ALWAYS AUTO Detector 0018 7005 CS ALWAYS AUTO Configuration Detector 0018 7006 LT ALWAYS AUTO Description Detector Mode 0018 7008 LT ALWAYS AUTO Detector ID 0018 702A SH ALWAYS AUTO Detector 0018 702B LO ALWAYS AUTO Manufacturer s Name Exposure 0018 7060 CS ALWAYS AUTO Control Mode Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Stateme
7. 0041 CS ALWAYS AUTO Horizontal Flip Image Rotation 0070 0042 US ALWAYS AUTO Display Area 0070 005A SQ ALWAYS AUTO Selection Sequence gt Displayed 0070 0052 SL ALWAYS AUTO Area Top Left Hand Corner gt Displayed 0070 0053 SL ALWAYS AUTO Area Bottom Right Hand Corner gt Presentation 0070 0100 CS ALWAYS AUTO Size Mode gt Presentation 0070 0101 CS ALWAYS AUTO Pixel Spacing gt Presentation 0070 0103 FL ALWAYS AUTO Pixel Magnification Ratio Graphic Layer 0070 0060 SQ ALWAYS AUTO Sequence gt Graphic Layer 0070 0002 CS ALWAYS AUTO gt Graphic Layer 0070 0062 IS ALWAYS AUTO Order Presentation 0070 0082 DA ALWAYS AUTO Greation Date Presentation 0070 0083 TM ALWAYS AUTO Creation Time Presentation 2050 0020 CS IDENTITY or ALWAYS AUTO LUT Shape INVERSE 6 1 1 3 MPPS N Create SOP Instance Attributes Attribute Tag V Value Presenc Source Name R e of Value Modality 0008 0060 CS DX ALWAYS AUTO Procedure 0008 1032 SQ ALWAYS AUTO Code Sequence Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Page 51 of 56 Revision 1 0 gt Code Value 0008 0100 SH ALWAYS AUTO gt Coding 0008 0102 SH ALWAYS AUTO Scheme Designator gt Code 0008 0104 LO ALWAYS AUTO Meaning Referenced 0008 1150 SQ ALWAYS AUTO Patien
8. Exception Behavior Timeout The Association is aborted using A ABORT and the worklist query marked as failed The reason is logged Association The worklist query is marked as failed The reason is logged aborted by the SCP or network layers Acquired images will always use the Study Instance UID specified for the Scheduled Procedure Step if available If an acquisition is unscheduled a Study Instance UID will be generated locally The table below provides a description of the Worklist AE Worklist Request Identifier and specifies the attributes that are copied into the images Unexpected attributes returned in a C FIND response are ignored Requested return attributes not supported by the SCP are set to have no value Non matching responses returned by the SCP due to unsupported option matching keys are ignored No attempt is made to filter out possible duplicate entries Worklist Request Identifier Module Name Tag VR M IR Q D I1OD Attribute Name SOP Common Specific Character Set 0008 0005 CS X Scheduled Procedure Step Scheduled Procedure Step Sequence 0040 0100 SQ X X gt Scheduled Station AET 0040 0001 AE S gt Scheduled Procedure Step Start Date 0040 0002 DA S gt Scheduled Procedure Step Start Time 0040 0003 TM X gt Modality 0008 0060 CS S X X gt Scheduled Performing Physician s Name 0040 0006 PN X gt Scheduled Procedure Step Description 0040 0007 LO X X gt Scheduled Station Name 0040 0010 SH S X gt Sche
9. Scheme Designator gt Code 0008 0104 LO ALWAYS AUTO Meaning Presentation 2050 0020 CS IDENTITY or ALWAYS AUTO LUT Shape INVERSE Pixel Data 7FE0 0010 O ALWAYS AUTO W 6 1 1 2 Grayscale Softcopy Presentation State SOP Instance Attributes Attribute Tag V Value Presenc Source Name R e of Value Image Type 0008 0008 CS ORIGINAL PRIMARY ALWAYS AUTO SOP Class 0008 0016 UI 1 2 840 10008 5 1 4 1 1 ALWAYS AUTO UID 11 1 SOP Instance 0008 0018 UI A unique UID for every ALWAYS AUTO UID new instance of image Study Date 0008 0020 DA ALWAYS AUTO Series Date 0008 0021 DA ALWAYS AUTO Study Time 0008 0030 TM ALWAYS AUTO Series Time 0008 0031 TM ALWAYS AUTO Accession 0008 0050 SH VNAP USER or Number MWL Modality 0008 0060 CS DX ALWAYS AUTO Referring 0008 0090 PN VNAP USER or Physician s MWL Name Study 0008 1030 LO ANAP USER or Description MWL Series 0008 103E LO ALWAYS USER or Description MWL Name of 0008 1060 PN ANAP USER Physician s Reading Study Operator s 0008 1070 PN ANAP AUTO Name Referenced 0008 1115 SQ ALWAYS AUTO Series Sequence Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage os Revision 1 0 gt gt Referenced 0008 1140 Ul ALWAYS AUTO Image Sequence
10. Storage AE initiates an Association to the archive and transfers the images to the archive upon success If the association or transfer is not successful the images are scheduled for transfer at the next auto send time interval 2 2 2 3 1 1 Description and Sequencing of Activities The Storage AE will initiate an association to an archive as a Storae SCU and send the images using C STORE operation The association is released after all images have been transferred 2 2 2 3 1 2 Proposed Presentation Contexts The Storage AE will propose Presentation Contexts as shown in the following table Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Name UID og UID List Negotiation 1 2 840 10008 1 2 DX Image 1 2 840 10008 5 1 4 1 1 1 1 Implicit SCU None Storage For Presentation Little Endian DX Image Storage For Processing 1 2 840 10008 5 1 4 1 1 1 1 1 Implicit Little Endian 1 2 840 10008 1 2 SCU None Grayscale Softcopy Presentation 1 2 840 10008 5 1 4 1 1 11 1 Implicit Little Endian 1 2 840 10008 1 2 SCU None Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage 2 Revision 1 0 State Storage 2 2 2 3 1 3 SOP Specific Conformance for DX Image Storage If DX Image Storage SOP Instances a
11. The implementation information written to the File Meta Header in each file is DICOM Implementation Class and Version for Media Storage Implementation Class UID 2 16 124 113531 9 Implementation Version Name OE DA ver 1 0 3 2 AE Specification 3 2 1 Media AE Specification The Media AE provides standard conformance to the DICOM Interchange Option of the Media Storage Service Class The Application Profiles and roles are listed below Application Profiles Real World Activity Role SOP Class Supported Option STD GEN CD Export to Media CD R CD FSC Interchange STD GEN DVD RW DVD R DVD RW 3 2 1 1 Real World Activities 3 2 1 1 1 Activity Export to Media Revision 1 0 MERIDIAN Medical Systems Document No sand Page f Title Meridian UDI DICOM Conformance Statement rev 1 0 gee a7 Ot 58 Revision 1 0 When Media AE first transfers study exams to a storage medium their files are added to the storage medium in DICOM Part 10 format and a valid DICOMDIR is created and saved into the medium disk The Media AE is a File Set Creator 3 2 1 2 Media Storage Application Profiles The Media AE supports the following application profiles STD GEN CD STD GEN DVD 3 2 1 2 1 Options The Media AE supports the SOP Classes and Transfer Syntaxes listed in the table below Information SOP Class UID Transfer Syntax Transfer Syntax UID Object Definition Name B
12. attributes are defined 6 3 Coded terminology and Templates Code Meaning values are not interpreted or displayed by the application Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Boge Skee Revision 1 0 6 4 Grayscale Image Consistency The UDI does not support the Grayscale Standard Display Function 6 5 Standard Extended Specialized Private SOP Classes The UDI does not claim conformance to any Extended Specialized or Private SOP Classes 6 6 Private Transfer Syntaxes The UDI does not employ any Private Transfer Syntaxes Revision 1 0
13. 0 0255 LO ALWAYS AUTO Performed Protocol Code Sequence 0040 0260 SQ ALWAYS AUTO gt Code Value 0008 0100 SH ALWAYS AUTO gt Coding Scheme Designator 0008 0102 SH ALWAYS AUTO gt Coding Scheme Version 0008 0103 SH ALWAYS AUTO gt Code Meaning 0008 0104 LO ALWAYS AUTO Performed Series 0040 0340 SQ ALWAYS AUTO Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Page DL Revision 1 0 Sequence gt Performing 0008 1050 PN ALWAYS AUTO Physician s Name gt Protocol 0018 1030 UI ALWAYS AUTO Name gt Operator s 0008 1070 PN ALWAYS AUTO Name gt Series 0020 000E Ul ALWAYS AUTO Instance UID gt Retrieve AE 0008 0054 AE ALWAYS AUTO Title gt Reference 0008 1140 SQ ALWAYS AUTO Image Sequence gt gt Referenced 0008 1150 Ul ALWAYS AUTO SOP Class UID gt gt Referenced 0008 1155 UI ALWAYS AUTO SOP Instance UID 6 1 2 Usage of Attributes From Received IOD s The UDI doesn t receive IOD from external source 6 1 3 Attribute Mapping The UDI does not perform any attribute mapping 6 1 4 Coerced Modified Fields The UDI doesn t receive IOD from external source It creates and sends out IOD 6 2 Data Dictionary of Private Attributes No private
14. 0008 0054 AE Title ALWAYS AUTO gt Series 0008 103E LO Description ALWAYS AUTO gt Performing 0008 1050 PN Physician s Name ALWAYS AUTO gt Operator s 0008 1070 PN Name ALWAYS AUTO gt Reference 0008 1140 SQ Image Sequence ALWAYS AUTO gt gt Referenced 0008 1150 Ul SOP Class UID ALWAYS AUTO gt gt Reference 0008 1155 UI SOP Instance UID gt Protocol 0018 1030 LO Name ALWAYS ALWAYS AUTO AUTO gt Series 000 000E Ul ALWAYS AUTO Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Page 54 of 56 Revision 1 0 Instance UID Procedure Code Sequence 0008 1032 SQ ALWAYS AUTO gt Code Value 0008 0100 SH ALWAYS AUTO gt Code Scheme Designator 0008 0102 SH ALWAYS AUTO gt Code Scheme Version 0008 0103 SH ALWAYS AUTO gt Code Meaning 0008 0104 LO ALWAYS AUTO Performed Procedure Step End Date 0040 0250 DA ALWAYS AUTO Performed Procedure Step End Time 0040 0251 TM ALWAYS AUTO Performed Procedure Step Status 0040 0252 CS COMPLETED ALWAYS AUTO Performed Procedure Step Description 0040 0254 LO ALWAYS AUTO Performed Procedure Type Description 004
15. 0008 1010 SH ALWAYS CONFIG Revision 1 0 MERIDIAN Medical Systems Document Revision 1 0 No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage o Revision 1 0 Study 0008 1030 LO ANAP USER or Description MWL Series 0008 103E LO ALWAYS USER or Description MWL Institutional 0008 1040 LO ALWAYS CONFIG Department Name Performing 0008 1050 PN ANAP USER Physician s Name Operator s 0008 1070 PN ANAP AUTO Name Manufacturer s 0008 1090 LO ALWAYS CONFIG Model Name Rerferenced 0008 1111 SQ ALWAYS AUTO Performed Procedure Step Sequence gt Referenced 0008 1150 Ul ALWAYS AUTO SOP Class UID gt Referenced 0008 1155 Ul ALWAYS AUTO SOP Instance UID Source Image 0008 2112 SQ Only set for FOR ANAP AUTO Reference PRESENTATION image and the referenced image is the FOR PROCESSING image raw image Anatomic 0008 2218 SQ ALWAYS AUTO Region Sequence gt Code Value 0008 0100 SH ALWAYS AUTO gt Coding 0008 0102 SH ALWAYS AUTO Scheme Designator gt Code 0008 0104 LO ALWAYS AUTO Meaning Patient s Name 0010 0010 PN VNAP USER or MWL Patient ID 0010 0020 LO VNAP USER or MWL Patient s Birth 0010 0030 DA VNAP USER or MERIDIAN Medical Systems Document No
16. Address Mapping The AE Title host names and port numbers of remote applications are configured using the service page interface 2 4 2 Parameters A number of parameters related to DICOM communication can be configured using preference and configuration files The following table shows those configuration parameters relevant to DICOM communication See the UDI Service Manual for details on configuration capabilities Parameter Configurable Default Yes No Value Max Send and Receive PDU Size No 65536 larger PDUs will never be sent even if the receiver supports a larger Max PDU Receive Size If the receiver supports a smaller Max PDU Receive Size then the Max PDU Send Size will be reduced accordingly for the duration of the Association Max PDU Receive Size information is exchanged during DICOM Association Negotiation in the Maximum Length Sub ltem of the A ASSOCIATION RQ and A ASSOCIATE AC Association Timeout and Inactivity Timeout No 30 seconds Time out waiting for a response to an Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Page ske Revision 1 0 Association Request or to a release request Time out waiting for completion of a TCP IP connect request Time out for waiting for data between TCP IP packets Worklist Auto Update Interval Yes 5 minutes Automatic worklist update request Stor
17. ICOM PPS manager When a user of UDI ends a study the UDI automatically issues a MPPS Completed procedure completed or Discontinued procedure discontinued message to queue designed for a remote DICOM PPS manager A configurable timer is used to send the queued messages to the remote DICOM PPS manager Since the messages are queued the remote PPS manager may receive both the In Progress and Completed at the same time All errors are logged in the UDI application 2 2 4 3 1 2 Proposed Presentation Contexts Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage see Revision 1 0 The MPPS AE will propose Presentation Contexts as shown in the following table Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Modality 1 2 840 10008 3 1 2 3 3 Implicit 1 2 840 10008 1 2 SCU None Performed Little Procedure Endian Step 2 2 4 3 1 2 1 SOP Specific Conformance MPPS AE involves the following two types of messages MPPS N Create operation MPPS N Set operation MPPS N Create and N Set messages are listed Annex 6 1 1 3 and 6 1 1 4 2 3 Network Interfaces 2 3 1 Physical Network Interface The UDI supports a single network interface One of the following physical network interfaces will be available depending on installed h
18. Modality Performed Procedure Step 2 2 4 1 SOP Classes The UDI MPPS AE provides standard conformance to the following DICOM SOP Classes as an SCU SOP Class Name SOP Class UID Modality Performed Procedure Step 1 2 840 10008 3 1 2 3 3 2 2 4 2 Association Establishment Policies 2 2 4 2 1 General The DICOM standard application context name for DICOM 3 0 is always proposed Application Context Name 1 2 840 10008 3 1 1 1 2 2 4 2 2 Number of Associations Revision 1 0 MERIDIAN Medical Systems Document Title No Meridian UDI DICOM Conformance Statement rev 1 0 Hage 33 of 56 Revision 1 0 MPPS AE initiates one service association at any given time 2 2 4 2 3 Asynchronous Nature The MPPS AE does not support asynchronous operations and will not perform asynchronous window negotiation 2 2 4 2 4 Implementation Identifying Information The application uses the following implementation identifying information Implementation Class UID 2 16 124 113531 9 Implementation Version Name OE ver 1 0 2 2 4 3 Association Initiation Policy This section describes the conditions under which the MPPS AE will initiate an association 2 2 4 3 1 Activities Send MPPS Messages 2 2 4 3 1 1 Description and Sequencing of Activities When a user of the UDI begins a new study the UDI automatically issues a MPPS In Progress message to a queue designated for a remote D
19. NO 1 2 840 10008 1 20 1 Modality Worklist Information Model FIND YES NO 1 2 840 10008 5 1 4 31 Modality Performed Procedure Step YES NO 1 2 840 10008 3 1 2 3 3 Print Management Print YES NO Table 1 Network Services Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage SALEN Revision 1 0 Table 2 lists the Supported Media Storage Application Profiles Media Storage Application Profile Write Files Read Files FSC or FSU FSR General Purpose CD R FSC NO CD R CD RW General Purpose DVD R FSC NO DVD DVD RW Table 2 Media Storage Application Profiles Revision 1 0 MERIDIAN Medical Systems Document Title No Meridian UDI DICOM Conformance Statement rev 1 0 Hage a Revision 1 0 1 Introduction The UDI integrates with X Ray generator and detector to acquire DX images The console should be connected to the X Ray generator and detector for acquisition The console should be connected to the information network for Modality Worklist DX Image Storage and or Storage Commitment Modality Performed Procedure Step and Print In addition the console should be configured with a local removable storage device for media archiving The use of this conformance statement by itself does not guarantee successful interoperability of the product with equipment from other v
20. UDI DICOM Conformance Statement rev 1 0 Boge aoe Revision 1 0 The abbreviations used in the Source column USER the attribute value source is from User input AUTO the attribute value is generated automatically MWL the attribute value is from MWL CONFIG the attribute value source is a configurable parameter 6 1 1 1 Image SOP Instance Attributes Attribute Tag V Value Presenc Source Name R e of Value Image Type 0008 0008 CS ORIGINAL PRIMARY ALWAYS AUTO SOP Class 0008 0016 Ul 1 2 840 10008 5 1 4 1 1 ALWAYS AUTO UID 1 1 or 1 2 840 10008 5 1 4 1 1 1 1 1 SOP Instance 0008 0018 UI A unique UID for every ALWAYS AUTO UID new instance of image Study Date 0008 0020 DA ALWAYS AUTO Series Date 0008 0021 DA ALWAYS AUTO Acquisition 0008 0022 DA ALWAYS AUTO Date Content Date 0008 0023 DA ALWAYS AUTO Study Time 0008 0030 TM ALWAYS AUTO Series Time 0008 0031 TM ALWAYS AUTO Acquisition 0008 0032 TM ALWAYS AUTO Time Content Time 0008 0033 TM ALWAYS AUTO Accession 0008 0050 SH VNAP USER or Number MWL Modality 0008 0060 CS DX ALWAYS AUTO Presentation 0008 0068 CS FOR PRESENTATION ALWAYS AUTO Intent Type or FOR PROCESSING Manufacturer 0008 0070 LO MERIDIAN MEDICAL ALWAYS AUTO Institution 0008 0080 LO ALWAYS CONFIG Name Institution 0008 0081 LO ALWAYS CONFIG Address Referring 0008 0090 PN VNAP USER or Physician s MWL Name Station Name
21. age Retry Time Yes 1 minute How long before resending a failed storage job Modality Performed Procedure Step Send Yes 10 minutes Message Interval How long between sending MPPS messages Storage Commitment Enabled Yes OFF Request storage commitment after successful C STORE response 3 Media Interchange 3 1 Implementation Model 3 1 1 Application Data Flow Diagram Export To Media Media AE Removable Media Dataflow of Media Application Entity 3 1 2 Functional Definition of Media AE Revision 1 0 MERIDIAN Medical Systems Document Title No Meridian UDI DICOM Conformance Statement rev 1 0 Hage 38 of 56 Revision 1 0 The user of the UDI Application uses the GUI to select a study s in the local UDI repository that will be exported to the media The user presses the button Transfer and the UDI Media AE component starts exporting the study to the media The media should not contain any existing File Set UDI Media AE acts as a FSC and always creates a new File Set 3 1 3 Sequencing of Real World Activity When Media AE is activated and Export to Media activity is invoked the user must ensure that a blank media is available User can optionally erase a non empty media prior to the media burning operation The Media AE will log all error related to media errors or user operation errors 3 1 4 File Meta Information for Implementation Class and Version
22. archive queue entry activates the Storage AE An association request is sent to the destination AE and upon successful negotiation the image transfer is started If the association cannot be opened the related archive queue entry will be scheduled for the next retry automatic If the destination AE is configured as a storage commitment device and the Storage AE has transferred the image to the destination a commitment confirmation is requested If a commitment is successfully confirmed the Storage AE will record this information in the local database Functional Definition of Print AE When an image is acquired and accepted by the user the application initiates auto print is configured a print request to the remote DICOM printer The print operation can also be requested by manual print Ul button An association request is sent to the remote DICOM printer AE Upon successful negotiation the image is sent to the printer Functional Definition of MPPS AE The UDI MPPS AE is used to transmit performed procedure step events which are the N CREATE and N SET to a remote DICOM device It therefore performs the following tasks Establishes a DICOM Association with a remote DICOM device Sends DICOM MPPS Information to a remote DICOM device 2 1 3 Sequencing of Real World Activities The Real World Activities are sequentially initiated in the user interface and another activity may not be initiated until the prior activity is com
23. ardware options Ethernet 100BaseT Gigabit Ethernet 2 3 2 Additional Protocols The UDI conforms to the System Management Profiles listed in the table below All requested transactions for the listed profiles and actors are supported Support for optional transactions are listed in the following table Profile Name Actor Protocols Optional Security Used Transactions Support Network Address DHCP Client DHCP N A Revision 1 0 Document MERIDIAN Medical Systems No Title Meridian UDI DICOM Conformance Statement rev 1 0 Page po Revision 1 0 Management DHCP Client DNS N A 2 3 2 1 DHCP DHCP can be used to obtain TCP IP network configuration information The network parameters obtainable via DHCP are shown in the Table below The Default Value column of the table shows the default used if the DHCP server does not provide a value Values for network parameters set in the Service Installation tool take precedence over values obtained from the DHCP server Support for DHCP is pre configured on the system If DHCP is not in use TCP IP network configuration information must be manually configured via the service interface DHCP Parameter Default Vale IP Address None Host Name Requested machine name List of NTP servers Empty List List of DNS servers Empty List Routers Empty List Static Routes None Domain name None Subnet M
24. asic Directory 1 2 840 10008 1 3 10 Explicit Little 1 2 840 10008 1 2 1 Endian Digital X Ray 1 2 840 10008 5 1 4 1 1 1 1 Implicit Little 1 2 840 10008 1 2 Image Storage Endian For Presentation Digital X ray Image 1 2 840 10008 5 1 4 1 1 1 1 1 Implicit Little 1 2 840 10008 1 2 Storage For Endian Processing Grayscale Softcopy 1 2 840 10008 5 1 4 1 1 11 1 Implicit Little 1 2 840 10008 1 2 Presentation State Endian Storage 3 3 Augmented and Private Application Profiles Media AE does not support any augmented and private application profiles 3 4 Configuration The Media AE requires user to pre set and to maintain configuration parameters of local media storage application entities The Media AE does not set the Application Entity Title in exported Part 10 option in DICOM Revision 1 0 Document MERIDIAN Medical Systems a Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage seer Revision 1 0 4 Support of Extended Character Sets The UDI system only supports the default DICOM character repertoire Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage L Revision 1 0 5 Security 5 1 Security Profiles The UDI does not support any specific security measures It is the user s responsibility to use the system within a secured environment and to maintain a secured environ
25. ask Derived from IP Address see service manual Broadcast address Derived from IP Address see service manual Default Router None Time Offset Site configurable from Time Zone MTU Network Hardware Dependent Auto IP permission No permission If the DHCP server refuses to renew a lease on the assigned IP address all active DICOM Associations will be aborted 2 3 2 2 DNS DNS can be used for address resolution If DHCP is not in use or the DHCP server does not return any DNS server addresses the identity of a DNS server can be configured in the system via the service interface If a DNS server is not in use local mapping between hostname and IP address can be manually configured via the service interface 2 3 3 IPv4 and IPv6 Support Revision 1 0 MERIDIAN Medical Systems dn Page 36 of 56 Title Meridian UDI DICOM Conformance Statement rev 1 0 Revision This product only supports IPv4 connections 2 4 Configuration 2 4 1 AE Title Presentation Address Mapping 2 4 1 1 Local AE Titles The UDI uses the Worklist AE Title Storage AE Title MPPS AE Title Print AE Title and their TCP IP Ports configured via the service page interface The Field Service Personnel can configure the TCP Ports via the service page interface No Default AE Title is provided The AE Titles must be configured during installation 2 4 1 2 Remote AE Title Presentation
26. ation Information 2010 0150 Basic Film Box SOP Class N CREATE Smoothing Type 2010 0080 Border Density 2010 0100 Empty Image Density 2010 0110 Min Density 2010 0120 Trim 2010 0140 N DELETE Polarity 2020 0020 Basic Grayscale Image Box N SET Magnification Type 2010 0060 SOP Class Smoothing Type 2010 0080 Requested Image Size 2020 0030 Printer SOP Class N GET 2 2 3 3 1 2 1 1 Basic Film Session SOP Class Attributes The UDI Print AE supports the following mandatory and optional attribute values in the SOP class Attribute Name Tag Supported Values Number of Copies 2000 0010 Integer String Print Priority 2000 0020 HIGH MED LOW Medium Type PAPER CLEAR FILM BLUE FILM Film Destination MAGAZINE PROCESSOR Film Session Label 2000 0050 Long string Memory Allocation 2000 0030 2000 0040 2000 0060 Integer string 2 2 3 3 1 2 1 2 Basic Film Box SOP Class Attributes The UDI Print AE supports the following mandatory and optional attribute values in this SOP class Attribute Name Tag Supported Values Image Display Format 2010 0010 STANDARD ROW COL SLIDE SUPERSLIDE CUSTOM Film Orientation 2010 0040 PORTRAID LANDSCAPE Film Size ID 2010 0050 8INX10IN 1OINX14IN 14INX14IN 24CMX24CM 1OINX12IN 11INX14IN 14INX17IN 240MX30CM Revision 1 0
27. ble of initiating multiple associations concurrently There is no real limit on the number of associations that can be originated There will be one association opened for each configured SCP 2 2 3 2 3 Asynchronous Nature The Print AE does not support asynchronous operations and will not perform asynchronous window negotiation 2 2 3 2 4 Implementation Identifying Information The application uses the following implementation identifying information Implementation Class UID 2 16 124 113531 1 1 1 Implementation Version Name ISG HCS V1 0 96 2 2 3 3 Association Initiation Policy This section describes the conditions under which the Print AE will initiate an association 2 2 3 3 1 Activities Print Images Revision 1 0 MERIDIAN Medical Systems E Page 29 of 56 Title Meridian UDI DICOM Conformance Statement rev 1 0 ao Revision 2 2 3 3 1 1 Description and Sequencing of Activities The user of the UDI Application selects the Print operation on the user interface The UDI maintains a list of valid hardcopy devices and can present that list to the users upon request When a user submits a print job designated for a listed hardcopy device the UDI Print AE will request an association with the selected hardcopy device 2 2 3 3 1 2 Proposed Presentation Contexts The Print AE will propose Presentation Contexts as shown in the following table Presentation Context Table Ab
28. ch association request This timer starts when the association request is sent and stops when the association response is received or an error occurs If a timeout occurs the connection is closed and the association is marked as failed The Association Timer value is not configurable and it has a default value of 30 seconds 2 2 2 4 Association Acceptance Policy The Storage AE will accept associations in order to receive responses to a Storage Commitment Request 2 2 3 Print AE Specifications The UDI Print AE provides the UDI application with print capabilities UDI Print AE acts independently of other DICOM applications that my be running on the same system It support printing to multiple DICOM hardcopy devices at the same time each hardcopy device being uniquely identified by an Application Entity Title 2 2 3 1 SOP Classes Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage ADEL Revision 1 0 The UDI provides standard conformance to the following DICOM SOP Classes as an SCU SOP Class Name SOP Class UID Basic Grayscale Print Management Meta 1 2 840 10008 5 1 1 9 2 2 3 2 Association Establishment Policies 2 2 3 2 1 General The DICOM standard application context name for DICOM 3 0 is always proposed Application Context Name 1 2 840 10008 3 1 1 1 2 2 3 2 2 Number of Associations The UDI Print AE is capa
29. ciation is aborted using A not match ABORT and the worklist query is marked SOP Class as failed Error information is logged Failed Unable to C000 The Association is aborted using A Process CFFF ABORT and the worklist query is marked as failed Error information is logged Cancel Matching FE00 If the query was cancelled due to too many terminated worklist items then the SCP has completed due to Cancel the matches Worklist items are available request for display Otherwise the Association is aborted using A ABORT and the worklist query is marked as failed Error information is logged Pending Matches are FFOO The worklist item contained in the Identifier continuing is collected for later display Pending Matches are FFO1 The worklist item contained in the Identifier continuing is collected for later display Errors are Warning that logged only once for each C FIND one or more operation Optional Keys were not supported Any The Association is aborted using A other ABORT and the worklist is marked as status failed Error information is logged code The behavior of Worklist AE during communication failure is summarized in the table below Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Boge KE Revision 1 0
30. d successful Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage oe Revision 1 0 i Any The Association is aborted using A other ABORT and the send job is marked as status failed Error information is logged and the code error is reported to the user via the Archive Status Ul The behavior of Storage AE during communication failure is summarized in the able below Storage Communication Failure Behavior Exception Behavior Timeout The Association is aborted using A ABORT and the send job is marked as failed Error information is logged and the error is reported to the user via the Archive Status Ul Association The send job is marked as failed The reason is logged and the aborted by the job failure is reported to the user via the job control application SCP or network layers 2 2 2 3 2 Activity Storage Commitment 2 2 2 3 2 1 Description And Sequencing of Activities Whenever a DX image is successfully sent to the archive the Storage AE automatically initiates a new association with the archive as a Storage Commitment SCU and sends an N ACTION command to request storage commitment for the DX image Upon receiving the N ACTION response the Storage AE releases the association The Storage AE always listens for connections from the archive on a pre configured port for storage commitm
31. duled Procedure Step ID 0040 0009 SH X X Requested Procedure Referenced Study Sequence 0008 1110 SQ X X Requested Procedure Description 0032 1060 LO X X Study Instance UID 0020 000D UI X X Requested Procedure Code Sequence 0032 1064 SQ X Imaging Service Request Accession Number 0008 0050 SH X X X X Revision 1 0 MERIDIAN Medical Systems Document No rT Page 22 of 56 Title Meridian UDI DICOM Conformance Statement rev 1 0 208 Revision 1 0 Referring Physician s Name 0008 0090 PN X X Requesting Physician 0032 1032 PN X X X Placer Order Number Imaging Service 0040 2016 LO X x Request Filler Order Number Imaging Service 0040 2017 LO X xX Request Patient Identification Patient Name 0010 0010 PN X X X X Patient ID 0010 0020 LO xIXIX X Patient Demographic Patient s Birth Date 0010 0030 DA X X X X Patient s Sex 0010 0040 CS X X X X Patient s Weight 0010 1030 DS X X Patient Comments 0010 4000 LT X X The above table should be read as follows Module Name attributes Attribute Name The name of the associated module for supported worklist Attributes supported to build a Worklist AE Worklist Request Identifier Tag DICOM tag for this attribute VR DICOM VR for this attribute M Matching keys for Worklist update A S will indicate that Worklist AE will supply an attribute
32. ecifies a variety of methods for encoding data denoted Transfer Syntaxes The Negotiation allows the initiating Application Entity to propose combinations of Abstract Syntax and Transfer Syntax to be used on the Association these combinations are called Presentation Contexts The receiving Application Entity accepts the Presentation Contexts it supports For each Presentation Context the Association Negotiation also allows the devices to agree on Roles which one is the Service Class User SCU client and which is the Service Class Provider SCP server Normally the device initiating the connection is the SCU i e the client system calls the server but not always The Association Negotiation finally enables exchange of maximum network packet PDU size security information and network service options called Extended Negotiation information The Application Entities having negotiated the Association parameters may now commence exchanging data Common data exchanges include queries for worklists and lists of stored images transfer of image objects and analyses structure reports and sending images to film printers Each exchangeable unit of data if formatted by the sender in accordance with the appropriate Information Object Definition and sent using the negotiated Transfer Syntax There is a Default Transfer Syntax that all systems must accept but it may not be the most efficient for some use case Each transfer is explici
33. eed to understand how the UDI will integrate into their healthcare facility This includes both those responsible for overall imaging network policy and architecture as well as integrators who need to have a detailed understanding of the DICOM features of the product This document contains some basic DICOM definitions so that any reader may understand how this product implements DICOM features However integrators are expected to fully understand all the DICOM terminology how the tables in this document relate to the product s functionality and how that functionality integrates with other devices that support compatible DICOM features Remarks The scope of this DICOM Conformance Statement is to facilitate integration between UDI and other DICOM products The Conformance Statement should be read and understood in conjunction with the DICOM Standard DICOM by itself does not guarantee interoperability The Conformance statement does however facilitate a first level comparison for interoperability between different applications supporting compatible DICOM functionality This Conformance Statement is not supposed to replace validation with other DICOM equipment to ensure proper exchange of intended information In fact the user should be aware of the following important issues The comparison of different Conformance Statements is just the first step towards assessing interconnectivity and interoperability between the product and the oth
34. endors The user or integrator of the UDI system should keep the following issues in mind Successful interoperability of the UDI system with other devices may require functions which are not specified within the scope of DICOM It is the user s or integrator s responsibility to ensure that the proper analysis and validation is performed to verify the connection Test procedures should be used to verify that data transferred into from the software is correct This is often done with the aid of phantom scans using a variety of clinical protocols Test procedures should be used to verify connectivity Issues such as power failure and broken connections should be verified The DICOM standard will continually evolve to meet new user requirements Meridian Medical Systems will follow the changes in the standard by implementing new features as specified by the standard The user or integrator should ensure that any non Meridian OEM device providers which connect with Meridian devices should also follow the standard Failure to do so will likely result in future connectivity problems 1 1 Revision History Version Type Date Description 1 0 Major Sept 15 2010 Initial Version 1 2 Audience Revision 1 0 MERIDIAN Medical Systems Document Title No Meridian UDI DICOM Conformance Statement rev 1 0 Hage go Revision 1 0 1 3 1 4 This document is written for the people that n
35. ent responses When the archive completes the storage commitment of one or more images it will connect to the Storage AE request an association and send the appropriate storage commitment result notifications The Storage AE will store the result of the storage commitment operation for each image The storage commitment functionality of the Storage AE can be turned off through configuration 2 2 2 3 2 2 Proposed Presentation Contexts Revision 1 0 MERIDIAN Medical Systems dn Title Meridian UDI DICOM Conformance Statement rev 1 0 Page 27 of 56 Revision 1 0 The Storage AE will propose Presentation Contexts as shown in the following table Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Storage 1 2 840 10008 1 20 1 Implicit Little 1 2 840 10008 1 2 SCU None Commitment Endian Push Model 2 2 2 3 2 3 SOP Specific Conformance for Storage Commitment Push SOP Class If the association with the archive fails the Storage AE logs an error message describing the error and will not retry If an N ACTION response has a status that is not Success the Storage AE will log an error message close the association and will not attempt to commit the image again The Storage AE will continue to send storage commitment requests for subsequent DX images The Storage AE supports an Association Timer for ea
36. er DICOM conformant equipment Test procedures should be defined and executed to validate the required level of interoperability with specific compatible DICOM equipment as established by the healthcare facility Terms and Definitions Informal definitions are provided for the following terms used in this Conformance Statement The DICOM Standard is the authoritative Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage SEU Revision 1 0 source for formal definitions of these terms Abstract Syntax the information agreed to be exchanged between applications generally equivalent to a Service Object Pair SOP Class Examples Verification SOP Class Modality Worklist Information Model Find SOP Class Computed Radiography Image Storage SOP Class Application Entity AE an end point of a DICOM information exchange including the DICOM network or media interface software i e the software that sends or receives DICOM information objects or messages A single device may have multiple Application Entities Application Entity Title the externally known name of an Application Entity used to identify a DICOM application to other DICOM applications on the network Application Context the specification of the type of communication used between Application Entities Example DICOM network protocol Association a network commun
37. formation System Secondary Capture Service Class Provider Service Class User Service Object Pair Scheduled Procedure Step Structured Report Transmission Control Protocol Internet Protocol Unique Key Attribute Upper Layer Value Representation Revision 1 0 Document MERIDIAN Medical Systems oe Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage LE Revision 1 0 1 7 References NEMA PS3 2008 Digital Imaging and Communication in Medicine DICOM standard available free at http medical nema org 2 Networking This section describes the networking related services of the UDI system 2 1 Implementation Model 2 1 1 Application Data Flow Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Page Pore Revision 1 0 DICOM Standard Interface Update Worklist Workilist Application Entity Accept Images Storage Application Entity Send images Commit Images Print Application Entity Print images Send MPPS uPPS Messages Application Entity Remote Application Entity Provides Worklist Items Remote Application Entity Receives Images Remote Application Entity Commits Images Remote Application Entity Prints Images Remote Application Entity accepts MPPS The Worklist AE receives Wor
38. gt gt Referenced 0008 1150 UI ALWAYS AUTO SOP Class UID gt gt Referenced 0008 1155 UI ALWAYS AUTO SOP Instance UID gt Series 0020 000E Ul ALWAYS AUTO Instance UID Patient s Name 0010 0010 PN VNAP USER or MWL Patient ID 0010 0020 LO VNAP USER or MWL Patient s Birth 0010 0030 DA VNAP USER or Date MWL Patient s Sex 0010 0040 CS VNAP USER or MWL Additional 0010 21BO LT ALWAYS MWL Patient s History Device Serial 0018 1000 LO ALWAYS AUTO Number Study Instance 0020 000D UI A UID is automatically ALWAYS MWL or UID generated for every AUTO instance Series 0020 000E UI A UID is automatically ALWAYS AUTO Instance UID generated for every instance Study ID 0020 0010 SH ALWAYS AUTO Series Number 0020 0011 IS ALWAYS AUTO Rescale 0028 1052 DS 0 ALWAYS AUTO Intercept Rescale Slope 0028 1053 DS 1 ALWAYS AUTO Rescale Type 0028 1054 LO US ALWAYS AUTO Softcopy VOI 0028 3110 SQ ALWAYS AUTO LUT Sequence gt Window 0028 1050 DS ALWAYS AUTO Center gt Window 0028 1051 DS ALWAYS AUTO Width Graphic 0070 0001 SQ ALWAYS AUTO Annotation Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage SE Revision 1 0 Sequence gt Graphic Layer 0070 0002 CS ALWAYS AUTO Image 0070
39. ication channel set up between Application Entities Attribute a unit of information in an object definition a data element identified by a tag The information may be a complex data structure Sequence itself composed of lower level data elements Examples Patient ID 0010 0020 Accession Number 0008 0050 Photometric Interpretation 0028 0004 Procedure Code Sequence 0008 1032 Information Object Definition IOD the specified set of Attributes that comprise a type of data object does not represent a specific instance of the data object but rather a class of similar data objects that have the same properties The Attributes may be specified as Mandatory Type 1 Required but possibly unknown Type 2 or Optional Type 3 and there may be conditions associated with the use of an Attribute Types 1C and 2C Examples MR Image IOD CT Image IOD Print Job IOD Joint Photographic Experts Group JPEG a set of standardized image compression techniques available for use by DICOM applications Revision 1 0 MERIDIAN Medical Systems Document Title No Meridian UDI DICOM Conformance Statement rev 1 0 Hage 2a Revision 1 0 Media Application Profile the specification of DIOCM information objects and encoding exchanged on removable media e g CDs Module a set of Attributes within an Information Object Definition that are logically related to each other Example Patient Modu
40. ist AE will update the Worklist control with the list of responses 2 2 1 3 1 2 Proposed Presentation Contexts The Worklist AE will propose Presentation Contexts as shown in the following table Presentation Context Table Abstract Syntax n Transfer Syntax Role Extended Name UID ee UID List Negotiation Modality 1 2 840 10008 5 1 4 31 Implicit 1 2 840 10008 1 2 SCU None Worklist Little Information Endian Model FIND 2 2 1 3 1 3 SOP Specific Conformance for Modality Worklist The behavior of Worklist AE when encountering status codes in a Modality Worklist C FIND response is summarized in the table below If any other SCP response status that Success or Pending is received by Worklist AE a Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Boge evo Revision message will appear on the user interface and the user interface will fall back to locally saved worklist items for display Modality Worklist C FIND Response Status Handling Behavior Service Further Error Behavior Status Meaning Code Success Matching is 0000 The SCP has completed the matches complete Worklist items are available for display Refused Out of A700 The Association is aborted using A Resources ABORT and the worklist query is marked as failed Error information is logged Failed Identifier does A900 The Asso
41. klist information from a remote AE It is associated with the Update Worklist local real world activity When the Update Worklist local real world activity is performed the Worklist AE queries a remote AE for worklist items and provides the set of worklist items matching the query request Update Worklist is performed as a result of an operator request or can be performed automatically at specific time intervals Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Page 13 of 56 Revision 2 1 2 2 1 2 1 The Storage AE sends images to a remote AE The remote AE could be an archive device or a PACS network The Storage AE is associated with the local real world activities Accept Images and Send Images On the Accept Images real world activity the Storage AE sends images immediately to a network storage device or PACS Send Images is activated by user settings auto send and when performed the Storage AE sends images to all remote AEs The Storage AE requests Storage Commitment if a remote AE is configured as a storage commitment device Only one storage commitment device may be active at a time The Storage AE is associated with the local real world activity Commit Images which is activated by user settings auto commit The Print AE sends images to a remote AE which is associated with a DICOM prin
42. le includes Patient Name Patient ID Patient Birth Date and Patient Sex Negotiation first phase of Association establishment that allows Application Entities to agree on the types of data to be exchanged and how that data will be encoded Presentation Context the set of DICOM network services used over an Association as negotiated between Application Entities includes Abstract Syntaxes and Transfer Syntaxes Protocol Data Unit a packet piece of a DICOM message sent across the network Devices must specify the maximum size packet they can receive for DICOM messages Security Profile a set of mechanisms such as encryption user authentication or digital signatures used by an Application Entity to ensure confidentiality integrity and or availability of exchanged DICOM data Service Class Provider SCP role of an Application Entity that provides a DICOM network service typically a server that performs operations requested by another Application Entity Service Class User Examples Picture Archiving and Communication System image storage SCP and image query retrieve SCP Radiology Information System modality Worklist SCP Service Class User SCU role of an Application Entity that uses a DICOM network service typically a client Examples imaging modality image storage SCU and modality Worklist SCU imaging workstation image query retrieve SCU Service Object Pair SOP Class the specifica
43. ment that includes at a minimum Firewall or router protections to ensure that only approved external hosts have network access to the system Firewall or router protections to ensure that the system only has network access to approved external hosts and services Any communication with external hosts and services outside the locally secured environment use appropriate secure network channels e g such as a Virtual Private Network VPN 5 2 Association Level Security None supported Revision 1 0 MERIDIAN Medical Systems Document Title No Meridian UDI DICOM Conformance Statement rev 1 0 Hage 42 of 56 Revision 1 0 5 3 Application Level Security The service page user interface that is used to configure the DICOM service is password controlled 6 Annexes 6 1 IOD Contents The UDI creates DX SOP instances and Grayscale Softcopy Presentation State SOP instances 6 1 1 Created SOP Instances The following tables use a number of abbreviations The abbreviations used in the Presence of Value column are VNAP Value Not Always Present attribute sent zero length if no value is present ANAP Attribute Not Always Present ALWAYS Always Present EMPTY Attribute is sent without a value Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian
44. nt rev 1 0 Bae orah Revision 1 0 Exposure 0018 7062 LT ALWAYS AUTO Control Model Description Phototimer 0018 7065 DS ALWAYS AUTO Setting Study Instance 0020 000D UI A UID is automatically ALWAYS MWL or UID generated for every AUTO instance Series 0020 000E UI A UID is automatically ALWAYS AUTO Instance UID generated for every instance Study ID 0020 0010 SH ALWAYS AUTO Series Number 0020 0011 IS ALWAYS AUTO Instance 0020 0013 IS ALWAYS AUTO Number Patient 0020 0020 CS ALWAYS AUTO Orientation Image 0020 0062 CS ALWAYS AUTO Laterality Samples Per 0028 0002 US 1 ALWAYS AUTO Pixel Photometric 0028 0004 CS MONOCHROME1 ALWAYS AUTO Interpretation Rows 0028 0010 US ALWAYS AUTO Columns 0028 0011 US ALWAYS AUTO Pixel Aspect 0028 0034 IS 1 1 ALWAYS AUTO Ratio Bits Allocated 0028 0100 US ALWAYS AUTO Bits Stored 0028 0101 US ALWAYS AUTO High Bit 0028 0102 US ALWAYS AUTO Pixel 0028 0103 US ALWAYS AUTO Representation Burned In 0028 0301 CS NO ALWAYS AUTO Annotation Pixel Intensity 0028 1040 CS LIN or LOG ALWAYS AUTO Relationship Pixel Intensity 0028 1041 SS ALWAYS AUTO Relationship Sign Rescale 0028 1052 DS 0 ALWAYS AUTO Intercept Rescale Slope 0028 1053 DS 1 ALWAYS AUTO Rescale Type 0028 1054 LO US ALWAYS AUTO Performed 0040 0244 DA ALWAYS AUTO Revision 1 0 MERIDIAN Medical Systems
45. on context name for DICOM 3 0 is always proposed Application Context Name 1 2 840 10008 3 1 1 1 2 2 1 2 2 Number of Associations The maximum number of simultaneous Associations is 1 2 2 1 2 3 Asynchronous Nature The Worklist AE does not support asynchronous operations and will not perform asynchronous window negotiation 2 2 1 2 4 Implementation Identifying Information The application uses the following implementation identifying information Implementation Class UID 2 16 124 113531 9 Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage EA Revision 1 0 Implementation Version Name OE ver 1 0 2 2 1 3 Association Initiation Policy This section describes the conditions under which the Worklist AE will initiate an association 2 2 1 3 1 Activity Worklist Update A Worklist Update occurs on user interaction pressing the Search button on the Worklist control or automatically at specific time intervals configurable by the user To specify query parameters the user types search criteria in the column headers of the worklist 2 2 1 3 1 1 Description and Sequencing of Activities Upon initiation of the request the Worklist AE will build an Identifier for the C FIND request which will initiate an Association to send the request and will wait for Worklist responses After retrieval of all responses the Workl
46. pleted The following diagram shows a typical acquisition workflow Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage ERE Revision 1 0 Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage Pcie Revision 1 0 Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Bae 10050 Revision 1 0 Department Imaging WORKLIST Scheduler Hardware Query Worklist I I I I I I I I I I Receive Worklist I I I I Select Worklist Item Start Acquisition Request Storage Commitment Print Images DICOM MPPS Mgr Send MPPS Messages Acquire images Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage Lect Revision 1 0 2 2 AE Specification 2 2 1 Worklist AE Specification 2 2 1 1 SOP Classes The Worklist AE provides Standard Conformance to the following SOP Classes SOP Class Name SOP Class UID SCU SCP Modality Worklist Information Model FIND 1 2 840 10008 5 1 4 31 Yes No 2 2 1 2 Association Establishment Policies 2 2 1 2 1 General The DICOM standard applicati
47. re included in the Send Job anda corresponding Presentation Context is not accepted then the Association is aborted using A ABORT and the send job is marked as failed The job failure is logged and reported to the user via the Archive Status dialog The behavior of Storage AE when encountering status codes in a C STORE response is summarized in the Table below Service Further Error Behavior Status Meaning Code Success Success 0000 The SCP has successfully stored the SOP Instance If all SOP Instances in a send job have status success then the job is marked as complete Refused Out of A700 The Association is aborted using A Resources A7FF ABORT and the send job is marked as failed Error information is logged and the error is reported to the user via the Archive Status UI Error Data Set does A900 The Association is aborted using A not match AQFF ABORT and the send job is marked as SOP Class failed Error information is logged and the error is reported to the user via the Archive Status UI Error Cannot C000 The Association is aborted using A Understand CFFF ABORT and the send job is marked as failed Error information is logged and the error is reported to the user via the Archive Status Ul Warning Coercion of B000 Image transmission is considered Data Elements successful Warning Data Set does B007 Image transmission is considered not match successful SOP Class Warning Elements B006 Image transmission is considered Discarde
48. stract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Basic 1 2 840 10008 5 1 1 9 Implicit 1 2 840 10008 1 2 SCU None Grayscale Little Print Endian Management 2 2 3 3 1 2 1 SOP Specific Conformance to Basic Grayscale Print Management Meta SOP Class The UDI Print AE supports the following mandatory SOP classes which are defined under the Basic Grayscale Print Management Meta SOP Class SOP Class Name SOP Class UID Basic Film Session 1 2 840 10008 5 1 1 1 Basic Film Box 1 2 840 10008 5 1 1 2 Basic Grayscale Image Box 1 2 840 10008 5 1 1 4 Printer 1 2 840 10008 5 1 1 16 The UDI Print AE supports the following SOP class attributes and DIMSE services for the Basic Grayscale Print Management Meta SOP Class SOP Class DIMSE Service Optional Attribute Tag Number of Copies 2000 0010 Print Priority 2000 0020 Basic Film Session SOP Class N CREATE Medium Type 2000 0030 Film Destination 2000 0040 Film Session Label 2000 0050 Revision 1 0 MERIDIAN Medical Systems Document No Title Page 30 of 56 1 0 Meridian UDI DICOM Conformance Statement rev 1 0 er Revision Memory Allocation 2000 0060 Film Orientation 2010 0040 Film Size ID 2010 0050 Magnification Type 2010 0060 Max Density 2010 0130 Configur
49. t Sequence gt Referenced 0008 1150 Ul ALWAYS AUTO SOP Class UID gt Referenced 0008 1155 Ul ALWAYS AUTO SOP Instance UID Patient s Name 0010 0010 PN VNAP USER or MWL Patient ID 0010 0020 LO VNAP USER or MWL Patient s Birth 0010 0030 DA VNAP USER or Date MWL Patient s Sex 0010 0040 CS VNAP USER or MWL Study ID 0020 0010 SH ALWAYS AUTO Scheduled 0040 0270 SQ ALWAYS AUTO Step Attribute Sequence gt Accession 0008 0050 SH ALWAYS AUTO Number gt Referenced 0008 1110 SQ ALWAYS AUTO Study Sequence gt gt Referenced 0008 1150 Ul ALWAYS AUTO SOP Class UID gt gt Referenced 0008 1155 Ul ALWAYS AUTO SOP Instance UID gt Study 0020 000D Ul ALWAYS AUTO Instance UID gt Scheduled 0040 0007 LO ALWAYS AUTO Procedure Step Description Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Page 520 56 Revision 1 0 gt Scheduled Protocol Code Sequence 0040 0008 SQ ALWAYS AUTO gt gt Code Value 0008 0100 SH ALWAYS AUTO gt gt Coding Scheme Designator 0008 0102 SH ALWAYS AUTO gt gt Coding Scheme Version 0008 0103 SH ALWAYS AUTO gt gt Code Meaning 0008 0104 LO ALWAYS AUTO gt Scheduled Procedure Step ID 0040 0009 SH ALWAYS AUTO gt Requested Procedure ID 0040 1001 SH
50. tation VR the format type of an individual DICOM data element such as text an integer a person s name or a code DICOM information objects can be transmitted with either explicit identification of the type of each data element Explicit VR or without explicit identification Implicit VR with Implicit VR the receiving application must use a DICOM data dictionary to look up the format of each data element Basics of DICOM Communication This section describes terminology used in this Conformance Statement for the non specialist The key terms used in the Conformance Statement are highlighted in italics below This section is not a substitute for training about DICOM and it makes many simplifications about the meanings of DICOM terms Two Application Entities devices that want to communicate with each Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Hage PA Revision 1 0 other over a network using DICOM protocol must first agree on several things during an initial network handshake One of the two devices must initiate an Association a connection to the other device and ask if specific services information and encoding can be supported by the other device Negotiation DICOM specifies a number of network services and types of information objects each of which is called an Abstract Syntax for the Negotiation DICOM also sp
51. ter The Print AE is associated with the local real world activity Print Images Print Images is triggered by user settings auto print or by user selection in user interface Once performed the Print AE sends all selected images to remote DICOM printer with selected printing options The MPPS AE sends messages to a remote AE which is a Modality Performed Procedure Step SCP The MPPS AE is associated with the local real world activity Send MPPS Messages Send MPPS Messages is activated by user settings auto send MPPS messages upon finishing an acquisition session When performed the MPPS AE sends N CREATE and N SET messages to the remote MPPS SCP Functional definition of AEs Functional Definition of Worklist AE Worklist Update attempts to download a Worklist from a remote node If the Worklist AE establishes an Association to a remote AE it will transfer all worklist items via the open Association The results will be displayed in a list to the user 2 1 2 2 Functional Definition of Storage AE When an image is acquired and accepted by the user the Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 Page SALE Revision 1 0 2 1 2 3 2 1 2 4 application stores the image in its local database and then initiates an archive queue entry in the local database with the associated network destination The existence of the
52. text name for DICOM 3 0 is always proposed Application Context Name 1 2 840 10008 3 1 1 1 2 2 2 2 2 Number of Associations The number of simultaneous associations is not limited by the application As an association initiator the AE creates at most one association per destination at a given time 2 2 2 2 3 Asynchronous Nature The Storage AE does not support asynchronous operations and will not perform asynchronous window negotiation 2 2 2 2 4 Implementation Identifying Information The application uses the following implementation identifying information Implementation Class UID 2 16 124 113531 9 Implementation Version Name OE ver 1 0 Revision 1 0 Document MERIDIAN Medical Systems oe Title Page 24 of 56 Meridian UDI DICOM Conformance Statement rev 1 0 Revision 1 0 2 2 2 3 Association Initiation Policy This section describes the conditions under which the Storage AE will initiate an association 2 2 2 3 1 Activities Accept Images and Send Images Auto Send Accept Images occurs when acauisition of image is done When Accept Images is performed the Storage AE immediately initiates an Association to the Storage SCP and transfers the images upon successful Association The Storage AE may be configured to send output images from application database to destination Storage SCPs at regular intervals When the Send Images auto send activity is performed the
53. tion of the network or media transfer service of a particular type of data object the fundamental unit of DICOM interoperability specification Examples Ultrasound Image Storage Service Basic Grayscale Print Revision 1 0 MERIDIAN Medical Systems Document Title No Meridian UDI DICOM Conformance Statement rev 1 0 Hage Ler Revision 1 0 1 5 Management Service Object Pair SOP Instance an information object a specific occurrence of information exchanged in a SOP Class Examples a specific x ray image Tag a 32 bit identifier for a data element represented as a pair of four digit hexadecimal numbers the group and the element If the group number is odd the tag is for a private manufacturer specific data element Examples 0010 0020 Patient ID 07FE 0010 Pixel Data 0019 0210 private data element Transfer Syntax A set of encoding rules that allow Application Entities to unambiguously negotiate the encoding techniques e g Data Element structure byte ordering compression they are able to support thereby allowing these Application Entities to communicate Examples JPEG Baseline Explicit VR Little Endian Unique Identifier UID a globally unique dotted decimal string that identifies a specific object or a class of objects an ISO 8824 Object Identifier Examples Study Instance UID SOP Class UID SOP Instance UID Value Represen
54. tly acknowledged by the receiver with a Response Status indicating success failure or that query or retrieve operations are still in process Two Application Entities may also communicate with each other by exchanging media such as a CD R Since there is no Association Negotiation possible they both use a Media Application Profile that specifies pre negotiated exchange media format Abstract Syntax Revision 1 0 MERIDIAN Medical Systems Document No Title Meridian UDI DICOM Conformance Statement rev 1 0 page pees Revision 1 0 and Transfer Syntax 1 6 Abbreviations AE AET DHCP DICOM DNS DX FSC HIS IOD IPv4 IPv6 ISO JPEG MPPS MSPS MTU MWL NTP O OSI PACS PDU R RIS SC SCP SCU SOP SPS SR TCP IP U UL VR Application Entity Application Entity Title Dynamic Host Configuration Protocol Digital Imaging and Communication in Medicine Domain Name System Digital X ray File Set Creator Hospital Information System Information Object Definition Internet Protocol version 4 Internet Protocol version 6 International Organization for Standards Joint Photographic Experts Group Modality Performed Procedure Step Modality Scheduled Procedure Step Maximum Transfer Unit Modality Worklist Network Time Protocol Optional Key Attribute Open Systems Interconnection Picture Archiving and Communication System Protocol Data Unit Required Key Attribute Radiology In
55. value for Single Value Matching R Return keys An X will indicate that Worklist AE will supply this attribute as Return Key with zero length for Universal Matching Q Interactive Query Key An X will indicate that Worklist AE will supply this attribute as matching key if entered in the Worklist user interface D Displayed keys An X indicates that this worklist attribute is displayed to the user during patient registration dialog IOD An X indicates that this Worklist attribute is included into all Object Instances created during performance of the related Procedure Step 2 2 1 4 Association Acceptance Policy The Worklist AE does not accept Associations Revision 1 0 MERIDIAN Medical Systems Document No ee Page 23 of 56 Title Meridian UDI DICOM Conformance Statement rev 1 0 gee o Revision 1 0 2 2 2 Storage AE Specification 2 2 2 1 SOP Classes The Storage AE provides Standard Conformance to the following SOP Classes SOP Class Name SOP Class UID SCU SCP Digital X Ray Image Storage For 1 2 840 10008 5 1 4 1 1 1 1 YES NO Presentation Digital X ray Image starage For 1 2 840 10008 5 1 4 1 1 1 1 1 YES NO Processing Grayscale Ar State 1 2 840 1008 5 1 4 1 1 11 1 YES NO Storage Commitment Push Model 1 2 840 10008 1 20 1 YES NO 2 2 2 2 Association Establishment Policies 2 2 2 2 1 General The DICOM standard application con
Download Pdf Manuals
Related Search