DICOM Conformance Statement. DPI DICOM Conformance Statement. Document Number: Rev. A (New Platform) 1/6/2006 JBC

Transcription

1 Document Number: Rev. A (New Platform) 1/6/2006 JBC Copyright Eigen, Inc. 2006

2 A.1 Conformance Statement Overview The Eigen implements the necessary DICOM services to download work lists from an information system and save acquired XA images to a network storage device or CD-R. Table A.1-1 provides an overview of the network services supported by the Eigen. SOP Classes Transfer Table A.1-1 NETWORK SERVICES User of Service (SCU) X-Ray Angiographic Image Storage Yes No Workflow Management Modality Worklist Yes No Provider of Service (SCP) Table A.1-2 provides an overview of the Media Storage Application Profiles supported by the Eigen. Table A.1-2 MEDIA SERVICES Media Storage Application Profile Compact Disk Recordable Write Files (FSC or FSU) Read Files (FSR) General Purpose CD-R Yes No Page 1

3 A.2 TABLE OF CONTENTS A.2 TABLE OF CONTENTS... 2 A.3 INTRODUCTION... 4 A.3.1 Revision History... 4 A.3.2 Audience... 4 A.3.3 Remarks... 4 A.3.4 Definitions, Terms and Abbreviations... 4 A.3.5 References... 5 A.4 NETWORKING... 6 A.4.1 IMPLEMENTATION MODEL... 6 A Application Data Flow... 6 A Sequencing of Real-World Activities... 7 A.4.2 AE SPECIFICATIONS... 8 A Storage Application Entity Specification... 8 A Workflow Application Entity Specification...12 A.4.3 NETWORK INTERFACES...18 A Physical Network Interface...18 A Additional Protocols...18 A.4.4 CONFIGURATION...19 A AE Title/Presentation Address Mapping...19 A Parameters...20 A.5 MEDIA INTERCHANGE A.5.1 IMPLEMENTATION MODEL...22 A Application Data Flow...22 Page 2

4 A Functional Definition of AEs...22 A Sequencing of Real-World Activities...22 A File Meta Information Options...22 A.5.2 AE SPECIFICATIONS...23 A Offline-Media Application Entity Specification...23 A.5.3 AUGMENTED AND PRIVATE APPLICATION PROFILES...24 A.5.4 MEDIA CONFIGURATION...24 A.6 SUPPORT OF CHARACTER SETS A.7 SECURITY A.8 ANNEXES A.8.1 IOD CONTENTS...27 A Created SOP Instances...27 A Used Fields in received IOD by application...32 A Coerced/Modified Fields...32 A.8.2 DATA DICTIONARY OF PRIVATE ATTRIBUTES...32 A.8.3 CODED TERMINOLOGY AND TEMPLATES...32 A.8.4 STANDARD EXTENDED / PRIVATE SOP CLASSES...33 A.8.5 PRIVATE TRANSFER SYNTAXES...33 Page 3

5 A.3 INTRODUCTION A.3.1 REVISION HISTORY Document Revision Date of Issue Author Description Rev. A Jan 6, 2006 JBC Initial Release. (New Platform) A.3.2 AUDIENCE 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. A.3.3 REMARKS DICOM, by itself, does not guarantee interoperability. However, the Conformance Statement facilitates a first-level 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 echange of information intended. The scope of this Conformance Statement is to facilitate communication with the Eigen and other vendors Medical equipment. The Conformance Statement should be read and understood in conjunction with the DICOM Standard. 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 the Eigen and non Eigen devices. Test procedures should be defined to validate the desired level of connectivity. The DICOM standard will evolve to meet the users future requirements. The Eigen is actively involved in developing the standard further and therefore reserves the right to make changes to its products or to discontinue its delivery. A.3.4 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 AET DICOM Application Entity Application Entity Title Page 4

6 ASCE DIT DN CD-R CSE FSC FSU FSR GSDF GSPS IOD ISO LDAP LDIF MPPS MSPS R O PDU RDN SCU SCP SOP U Association Control Service Element Directory Information Tree (LDAP) Distinguished Name (LDAP) Compact Disk Recordable Customer Service Engineer File-Set Creator File-Set Updater File-Set Reader Grayscale Standard Display Function Grayscale Softcopy Presentation State (DICOM) Information Object Definition International Standard Organization Lightweight Directory Access Protocol LDAP Data Interchange Format Modality Performed Procedure Step Modality Scheduled Procedure Step Required Key Attribute Optional Key Attribute DICOM Protocol Data Unit Relative Distinguished Name (LDAP) DICOM Service Class User (DICOM client) DICOM Service Class Provider (DICOM server) DICOM Service-Object Pair Unique Key Attribute A.3.5 REFERENCES [DICOM] Digital Imaging and Communications in Medicine (DICOM), NEMA PS , 2004 Page 5

7 A.4 NETWORKING A.4.1 IMPLEMENTATION MODEL A Application Data Flow Send Images Storage Application Entity Remote Application Entity Receives Images Update Worklist Workflow Application Entity Remote Application Entity Provides Worklist Items DICOM Standard Interface Figure A APPLICATION DATA FLOW DIAGRAM The Storage Application Entity sends images to a remote AE. It is associated with the local real-world activity Send Images. Send Images is performed upon user request for each study completed or for specific images selected. When activated by user s settings (auto-send), each marked set of images can be immediately stored to a preferred destination whenever a Patient/Study is closed by the user. The Workflow Application Entity receives Worklist information from a remote AE. It is associated with the local real-world activity Update Worklist. When the Update Worklist local real-world activity is performed the Workflow Application Entity 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. Page 6

8 A Functional Definition of AEs A Functional Definition of Storage Application Entity The eistence of a send-job queue entry with associated network destination will activate the Storage AE. An association request is sent to the destination AE and upon successful negotiation of a Presentation Contet the image transfer is started. If the association cannot be opened, the related send-job is set to an error state and can be restarted by the user via job control interface. By default, the Storage AE will not try to initiate another association for this send-job automatically. However, an automatic retry (retry-timer, retry-count) can be configured by a CSE. A Functional Definition of Workflow Application Entity Worklist Update attempts to download a Worklist from a remote node. If the Workflow AE establishes an Association to a remote AE, it will transfer all worklist items via the open Association. During receiving the worklist response items are counted and the query processing is canceled if the configurable limit of items is reached. The results will be displayed in a separate list, which will be cleared with the net Worklist Update. A Sequencing of Real-World Activities Storage Workflow Department Scheduler Image Storage Manager 1. Query Worklist 2. Receive Worklist 3. Select Workitem 4. Acquire Images 5. Complete Acquisition 6. Store Acquired Images Figure A SEQUENCING CONSTRAINTS Under normal scheduled workflow conditions the sequencing constraints illustrated in Figure A apply: Page 7

9 1. Query Worklist 2. Receive Worklist of Modality Scheduled Procedure Steps (MSPS) 3. Select Workitem (MSPS) from Worklist 4. Acquire Images 5. Complete acquisition 6. Store acquired images Other workflow situations (e.g. unscheduled procedure steps) will have other sequencing constraints. The user may optionally enter procedure information manually, however this is only recommended for unscheduled procedures and/or hospitals that do not have a modality worklist SCP. A.4.2 AE SPECIFICATIONS A Storage Application Entity Specification A SOP Classes The Eigen provides Standard Conformance to the following SOP Classes: Table A SOP CLASSES FOR AE STORAGE SOP Class Name SOP Class UID SCU SCP X-Ray Angiographic Image Storage Yes No A A Association Policies General The DICOM standard application contet name for DICOM 3.0 is always proposed: Table A DICOM APPLICATION CONTEXT FOR AE STORAGE Application Contet Name A Number of Associations The Eigen initiates one Association at a time for each destination to which a transfer request is being processed in the active job queue. Only one job will be active at a time, the other remains pending until the active job is completed or failed. Page 8

10 Table A NUMBER OF ASSOCIATIONS INITIATED FOR AE STORAGE Maimum number of simultaneous Associations 1 A Asynchronous Nature The Eigen does not support asynchronous communication (multiple outstanding transactions over a single Association). A Implementation Identifying Information The implementation information for this Application Entity is: Table A DICOM IMPLEMENTATION CLASS AND VERSION FOR AE STORAGE Implementation Class UID Implementation Version Name EIGEN_353 A A A Association Initiation Policy Activity Send Images Description and Sequencing of Activities A user can select images and presentation states and request them to be sent. Each request is forwarded to the job queue and processed individually. When the Auto-send option is active, each marked instance or marked set of instances stored in database will be forwarded to the network job queue for a pre-configured auto-send target destination. It can be configured which instances will be automatically marked and the destination where the instances are automatically sent to. The Auto-send is triggered by the End Case function in the application. The Storage AE is invoked by the job control interface that is responsible for processing network archival tasks. The job consists of data describing the instances marked for storage and the destination. An internal daemon process triggered by a job for a specific network destination initiates a C-STORE request to store images. If the process successfully establishes an Association to a remote Application Entity, it will transfer each marked instance one after another via the open Association. Only one job will be active at a time. If the C-STORE Response from the remote Application contains a status other than Success or Warning, the Association is aborted and the related Job is switched to a failed state. It can be restarted any time by user interaction or, if configured, by automated retry. The Storage AE attempts to initiate a new Association in order to issue a C- STORE request. If the job contains multiple images then multiple C-STORE requests will be issued over the same Association. Page 9

11 S torage AE Im age Storage M anager 1. O pen Association 2. C -STO RE (XA Im age) 3. C -STO RE (XA Im age) 4. C lose A ssociation Figure A SEQUENCING OF ACTIVITY SEND IMAGES A possible sequence of interactions between the Storage AE and an Image Manager is illustrated in Figure A.4.2-1: 1. The Storage AE opens an association with the Image Storage Manager 2. An acquired XA image is transmitted to the Image Manager using a C- STORE request and the Image Manager replies with a C-STORE response (status success). 3. Another acquired XA image is transmitted to the Image Manager using a C-STORE request and the Image Manager replies with a C-STORE response (status success). 4. The Storage AE closes the association with the Image Manager. A Proposed Presentation Contets The Eigen is capable of proposing the Presentation Contets shown in the following table: Table A PROPOSED PRESENTATION CONTEXTS FOR ACTIVITY SEND IMAGES Abstract Synta Presentation Contet Table Transfer Synta Name UID Name List UID List X-Ray Angiographic Image Storage Implicit VR Little Endian Eplicit VR Little Endian Role Et. Neg. SCU None Page 10

12 Presentation Contets for X-Ray Angiographic Storage will only be proposed if the Send Job contains instances for these SOP Classes. Service Status A SOP Specific Conformance Image Storage SOP Classes All Image Storage SOP Classes supported by the Storage AE ehibit the same behavior, ecept where stated, and are described together in this section. If X-Ray Angiographic Image Storage SOP Instances are included in the Send Job and a corresponding Presentation Contet is not accepted then the Association is aborted using AP-ABORT and the send job is marked as failed. The job failure is logged and reported to the user via the job manager application. The behavior of Storage AE when encountering status codes in a C-STORE response is summarized in the Table below: Table A STORAGE C-STORE RESPONSE STATUS HANDLING BEHAVIOR Further Meaning Error Code Behavior 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 Error Error Out of Resources Data Set does not match SOP Class Cannot Understand A700- A7FF A900- A9FF C000- CFFF * * Any other status code. The Association is aborted using A-ABORT and the send job is marked as failed. The status meaning is logged and the job failure is reported to the user via the job control application. This is a transient failure. The Association is aborted using A-ABORT and the send job is marked as failed. The status meaning is logged and the job failure is reported to the user via the job control application. The Association is aborted using A-ABORT and the send job is marked as failed. The status meaning is logged and the job failure is reported to the user via the job control application. The Association is aborted using A-ABORT and the send job is marked as failed. The status code is logged and the job failure is reported to the user via the job control application. The behavior of Storage AE during communication failure is summarized in the Table below: Page 11

13 Timeout Table A STORAGE COMMUNICATION FAILURE BEHAVIOR Eception Association aborted by the SCP or network layers Behavior The Association is aborted using A-ABORT and the send job is marked as failed. The reason is logged and the job failure is reported to the user via the job control application. The send job is marked as failed. The reason is logged and the job failure is reported to the user via the job control application. A failed send job can be restarted by user interaction. The system can be configured to automatically resend failed jobs if a transient status code is received. The delay between resending failed jobs and the number of retries is also configurable. The contents of X-Ray Angiographic Image Storage SOP Instances created by the Eigen conform to the DICOM X-Ray Angiographic Image IOD definition and are described in section 8.1. A Workflow Application Entity Specification A SOP Classes The Eigen provides Standard Conformance to the following SOP Classes: Table A SOP CLASSES FOR AE WORKFLOW SOP Class Name SOP Class UID SCU SCP Modality Worklist Information Model FIND Yes No A A Association Policies General The DICOM standard application contet name for DICOM 3.0 is always proposed: Table A DICOM APPLICATION CONTEXT FOR AE WORKFLOW Application Contet Name A Number of Associations The Eigen initiates one Association at a time for a Worklist request. Page 12

14 Table A NUMBER OF ASSOCIATIONS INITIATED FOR AE WORKFLOW Maimum number of simultaneous Associations 1 A Asynchronous Nature The Eigen does not support asynchronous communication (multiple outstanding transactions over a single Association). A Implementation Identifying Information The implementation information for this Application Entity is: Table A DICOM IMPLEMENTATION CLASS AND VERSION FOR AE WORKFLOW Implementation Class UID Implementation Version Name EIGEN_353 A A A Association Initiation Policy Activity Worklist Update Description and Sequencing of Activities The request for a Worklist Update is initiated by user interaction, i.e. pressing the buttons Populate Fields from Worklist -> Query Worklist while in the patient information dialog. If a user does not enter any specific information to search for, the entire Worklist will be shown. The Worklist may also be queried for specific information such as Patient Name, Date, Doctor, or Modality. The Eigen will initiate an Association in order to issue a C-FIND request according to the Modality Worklist Information Model. Page 13

15 W orkflow AE D epartm ent Scheduler 1. O pen Association 2. C -FIN D R equest (W orklist Q uery) 3. C -FIN D R esponse (W orklist Item ) Status = P ending 4. C -FIN D R esponse (W orklist Item ) Status = P ending 5. C -FIN D R esponse S tatus = Success 6. C lose Association 7. S elect W orklist Item Figure A SEQUENCING OF ACTIVITY WORKLIST UPDATE A possible sequence of interactions between the Workflow AE and a Departmental Scheduler (e.g. a device such as a RIS or HIS which supports the Modality Worklist SOP Class as an SCP) is illustrated in the Figure above: 1. The Worklist AE opens an association with the Departmental Scheduler 2. The Worklist AE sends a C-FIND request to the Departmental Scheduler containing the Worklist Query attributes. 3. The Departmental Scheduler returns a C-FIND response containing the requested attributes of the first matching Worklist Item. 4. The Departmental Scheduler returns another C-FIND response containing the requested attributes of the second matching Worklist Item. 5. The Departmental Scheduler returns another C-FIND response with status Success indicating that no further matching Worklist Items eist. This eample assumes that only 2 Worklist items match the Worklist Query. 6. The Worklist AE closes the association with the Departmental Scheduler. 7. The user selects a Worklist Item from the Worklist and prepares to acquire new images. Page 14

16 A Proposed Presentation Contets The Eigen will propose Presentation Contets as shown in the following table: Table A PROPOSED PRESENTATION CONTEXTS FOR ACTIVITY WORKLIST UPDATE Abstract Synta Presentation Contet Table Transfer Synta Name UID Name List UID List Modality Worklist Information Model FIND Implicit VR Little Endian Eplicit VR Little Endian Role Et. Neg. SCU None A SOP Specific Conformance for Modality Worklist The behavior of the Eigen when encountering status codes in a Modality Worklist C-FIND response is summarized in the Table below. If any other SCP response status than "Success" or "Pending" is received by the Eigen, a message query failed will appear on the user interface. Table A MODALITY WORKLIST C-FIND RESPONSE STATUS HANDLING BEHAVIOR Service Status Further Meaning Success Matching is complete Refused Out of Resources Failed Failed Cancel Identifier does not match SOP Class Unable to Process Matching terminated due to Cancel request Error Code Behavior 0000 The SCP has completed the matches. Worklist items are available for display or further processing. A700 A900 C000 CFFF FE00 The Association is aborted using A-ABORT and the worklist query is marked as failed. The status meaning is logged and reported to the user if an interactive query. Any additional error information in the Response will be logged. The Association is aborted using A-ABORT and the worklist query is marked as failed. The status meaning is logged and reported to the user if an interactive query. Any additional error information in the Response will be logged. The Association is aborted using A-ABORT and the worklist query is marked as failed. The status meaning is logged and reported to the user if an interactive query. Any additional error information in the Response will be logged. If the query was cancelled due to too may worklist items then the SCP has completed the matches. Worklist items are available for display or further processing. Otherwise, the Association is aborted using A-ABORT and the worklist query is marked as failed. The status meaning is logged and reported to Page 15

17 Pending Matches are continuing Pending Matches are continuing Warning that one or more Optional Keys were not supported FF00 FF01 * * Any other status code. the user if an interactive query. The worklist item contained in the Identifier is collected for later display or further processing. The worklist item contained in the Identifier is collected for later display or further processing. The status meaning is logged only once for each C-FIND operation. The Association is aborted using A-ABORT and the worklist is marked as failed. The status meaning is logged and reported to the user if an interactive query. Any additional error information in the Response will be logged. Timeout The behavior of The Eigen during communication failure is summarized in the Table below. Table B MODALITY WORKLIST COMMUNICATION FAILURE BEHAVIOR Eception Association aborted by the SCP or network layers Behavior The Association is aborted using A-ABORT and the worklist query marked as failed. The reason is logged and reported to the user if an interactive query. The worklist query is marked as failed. The reason is logged and reported to the user if an interactive query. 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 Eigen Worklist Request Identifier and specifies the attributes that are copied into the images. Unepected 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 optional matching keys are ignored. No attempt is made it filter out possible duplicate entries. Page 16

18 Module Name Attribute Name Table A WORKLIST REQUEST IDENTIFIER Tag VR R Q D IOD SOP Common Specific Character Set (0008,0005) CS Scheduled Procedure Step Scheduled Procedure Step Sequence > Scheduled Station AET > Scheduled Procedure Step Start Date > Scheduled Procedure Step Start Time > Modality > Scheduled Performing Physician s Name > Scheduled Procedure Step Description > Scheduled Station Name > Scheduled Procedure Step Location > Pre-Medication > Scheduled Procedure Step ID > Requested Contrast Agent Requested Procedure Requested Procedure ID Requested Procedure Description Study Instance UID Requested Procedure Priority Imaging Service Request Accession Number Requesting Physician Patient Identification Patient Name Patient ID Patient Demographic Patient s Birth Date Patient s Se Patient Medical Medical Alerts Contrast Allergies (0040,0100) (0040,0001) (0040,0002) (0040,0003) (0008,0060) (0040,0006) (0040,0007) (0040,0010) (0040,0011) (0040,0012) (0040,0009) (0032,1070) (0040,1001) (0032,1060) (0020,000D) (0040,1003) (0008,0050) (0032,1032) (0010,0010) (0010,0020) (0010,0030) (0010,0040) (0010,2000) (0010,2110) SQ AE DA TM CS PN LO SH SH LO SH LO SH LO UI SH SH PN PN LO DA CS LO LO 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 an Eigen Worklist Request Identifier. Tag: VR: DICOM tag for this attribute. DICOM VR for this attribute. R: Return keys. An "" indicates that the Eigen will supply this attribute as Return Key with zero length for Universal Matching. The Eigen supports only DICOM formatted date (YYYYMMDD) and time (HHMMSS) values. Page 17

19 Q: Interactive Query Key. An indicates that the Eigen will supply this attribute as a matching key, if entered in the Populate Fields from Worklist dialog. For eample, the Patient Name can be entered thereby restricting Worklist responses to Procedure Steps scheduled for the patient. D: Displayed keys. An indicates that this worklist attribute is displayed to the user during a patient registration dialog. For eample, Patient Name will be displayed when registering the patient prior to an eamination. While a user is viewing a list of patients they may hide unwanted fields in order to make the patient selection process easier. IOD: An "" indicates that this Worklist attribute is included into all Object Instances created during performance of the related Procedure Step. The default Query Configuration is set to "Modality" (XA) and "Date" (current day). Optionally, additional matching for the Scheduled Station AET is configurable. A Association Acceptance Policy The Workflow Application Entity does not accept Associations. A.4.3 NETWORK INTERFACES A Physical Network Interface The Eigen supports a single network interface. One of the following physical network interfaces will be available depending on installed hardware options: Ethernet 1000baseT Ethernet 100baseT Ethernet 10baseT Table A SUPPORTED PHYSICAL NETWORK INTERFACES A Additional Protocols The Eigen 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 Table below: Table A SUPPORTED SYSTEM MANAGEMENT PROFILES Profile Name Actor Protocols Used Optional Transactions Security Support Network Address Management DHCP Client DNS Client DHCP DNS N/A N/A Page 18

20 A 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 Windows Network Configuration Utility take precedence over values obtained from the DHCP server. Support for DHCP can be configured via Windows. If DHCP is not in use, TCP/IP network configuration information can be manually configured via the Windows Network Configuration Utility. Table A SUPPORTED DHCP PARAMETERS IP Address Hostname List of NTP servers List of DNS servers Routers Static routes Domain name Subnet mask Broadcast address Default router Time offset MTU Auto-IP permission DHCP Parameter None Default Value Requested machine name Empty list Empty list Empty list None None None None None Site configurable (from Timezone) Network Hardware Dependent No permission If the DHCP server refuses to renew a lease on the assigned IP address all active DICOM Associations will be aborted. A 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 via the Windows network configuration utility. If a DNS server is not in use, local mapping between hostname and IP address can be manually configured via the Windows network configuration utility. A.4.4 CONFIGURATION A AE Title/Presentation Address Mapping A Local AE Titles All local applications use the AE Titles and TCP/IP Ports configured via the configuration menu. The Field Service Engineer can configure the TCP Port via the configuration menu. No Default AE Titles are provided. The AE Titles must be configured during installation. The local AE Title used by each individual Page 19

21 application can be configured independently of the AE Title used by other local applications. If so configured, all local AEs are capable of using the same AE Title. Table A AE TITLE CONFIGURATION TABLE Application Entity Default AE Title Default TCP/IP Port Storage No Default No Default Workflow No Default No Default A Remote AE Title/Presentation Address Mapping The AE Title, host names and port numbers of remote applications are configured using the configuration menu in the DICOM send dialog. A Storage The Eigen network configuration dialog must be used to set the AE Title, port-number and host-name for the remote Storage SCP. The Eigen can only be configured to send data to a single Storage SCP. A Workflow A The Eigen modality worklist configuration dialog must be used to set the AE Title, port-number, host-name and capabilities of the remote Modality Worklist SCP. Only a single remote Modality Worklist SCP can be defined. Parameters A large number of parameters related to acquisition and general operation can be configured using the Service/Installation Tool. The Table below only shows those configuration parameters relevant to DICOM communication. See the Eigen Installation Manual for details on general configuration capabilities. Table A CONFIGURATION PARAMETERS TABLE Parameter General Parameters Ma PDU Send Size (larger PDUs will never be sent, even if the receiver supports a larger Ma PDU Receive Size. If the receiver supports a smaller Ma PDU Receive Size then the Ma PDU Send Size will be reduced accordingly for the duration of the Association. Ma PDU Receive Size information is echanged during DICOM Association Negotiation in the Maimum Length Sub-Item of the A- ASSOCIATION-RQ and A-ASSOCIATE-AC) Time-out waiting for a acceptance or rejection response to an Association Request (Application Level Timeout) Time-out waiting for a response to an Association release request (Application Level Timeout) Configurable (Yes/No) Default Value Yes Bytes (128 kb) No No 15 s 15 s Page 20

22 Parameter Time-out waiting for completion of a TCP/IP connect request (Low-level timeout) Time-out awaiting a Response to a DIMSE Request (Low- Level Timeout) Time-out for waiting for data between TCP/IP-packets (Low Level Timeout) Storage Parameters Storage SCU time-out waiting for a response to a C- STORE-RQ Configurable (Yes/No) No No No No Default Value 15 s 360 s 30 s 120 s Number of times a failed send job may be retried Yes 0 (Failed send jobs are not retried) Delay between retrying failed send jobs Yes 60 s Maimum number of simultaneously initiated Associations by the Storage AE No 1 Supported Transfer Syntaes No Eplicit VR Little Endian Modality Worklist Parameters Modality Worklist SCU time-out waiting for the final response to a C-FIND-RQ No 300 s Maimum number of Worklist Items No 5000 Supported Transfer Syntaes for Modality Worklist No Eplicit VR Little Endian Query Worklist for specific Modality Value Yes XA Page 21

23 A.5 MEDIA INTERCHANGE A.5.1 IMPLEMENTATION MODEL A Application Data Flow User Clicks Write DICOM CD Offline-Media Application Entity CD-R Storage Medium Figure A APPLICATION DATA FLOW DIAGRAM FOR MEDIA STORAGE The Offline-Media Application Entity eports images to a CD-R Storage medium. It is associated with the local real-world activity Write DICOM CD. Write DICOM CD is performed upon user request for a selected case. A Functional Definition of AEs A Functional Definition of Offline-Media Application Entity Activation of the Write DICOM CD button will pass the currently selected case to the Offline-Media Application Entity. The SOP Instances associated with the selection will be collected into one or more eport jobs. The contents of each eport job will be written to a CD-R. If a case will not fit on a single CD-R then the user will be prompted to insert several disks until the case is completely eported. A Sequencing of Real-World Activities At least one image must eist and be selected before the Offline-Media Application Entity can be invoked. The operator can insert a new CD-R media at any time before or after invocation of the Offline-Media Application Entity. The Offline-Media Application Entity will wait indefinitely for a media to be inserted before starting to write to the CD-R device. If no CD-R media is available the eport job can be canceled. A File Meta Information Options The implementation information written to the File Meta Header in each file is: Table A DICOM IMPLEMENTATION CLASS AND VERSION FOR MEDIA STORAGE Implementation Class UID Implementation Version Name EIGEN_353 Page 22

24 A.5.2 AE SPECIFICATIONS A Offline-Media Application Entity Specification The Offline-Media Application Entity provides standard conformance to the DICOM Interchange Option of the Media Storage Service Class. The Application Profiles and roles are listed below: Table A APPLICATION PROFILES, ACTIVITIES AND ROLES FOR OFFLINE-MEDIA Application Profiles Supported Real World Activity Role SC Option STD-GEN-CD Eport to CD-R FSC Interchange A File Meta Information for the Application Entity The Source Application Entity Title included in the File Meta Header is not configurable. A Real-World Activities A Activity Eport to CD-R The Offline-Media Application Entity acts as an FSC using the interchange option when requested to eport SOP Instances from the local database to a CD-R medium. If the contents of the current selection do not fit on a single media an automatic separation into multiple eport jobs will be suggested which can be adapted by the user. The user will be prompted to insert an empty CD-R for each eport job. The contents of the eport job will be written together with a corresponding DICOMDIR to a single-session CDR. Writing in multi-session mode is not supported. The user can cancel an eport job. A Media Storage Application Profiles The Offline-Media Application Entity supports the STD-GEN-CD Application Profile. A Options The Offline-Media Application Entity supports the SOP Classes and Transfer Syntaes listed in the Table below: Table A IODS, SOP CLASSES AND TRANSFER SYNTAXES FOR OFFLINEMEDIA Information Object Definition SOP Class UID Transfer Synta Transfer Synta UID Media Storage Directory Storage Eplicit VR Little Endian X-Ray Angiographic Image Storage Eplicit VR Little Endian Page 23

25 A.5.3 AUGMENTED AND PRIVATE APPLICATION PROFILES The Eigen does not support any augmented for private application profiles. A.5.4 MEDIA CONFIGURATION The AE Title of the Offline-Media FSC is not configurable. The default value is listed in the following table: Table A AE TITLE TABLE Offline-Media Application Entity AE Title EIGEN_MEDIA_EXPORT Page 24

26 A.6 SUPPORT OF CHARACTER SETS All Eigen DICOM applications support the: ISO_IR 100 (ISO :1987 Latin Alphabet No. 1 supplementary set) Page 25

27 A.7 SECURITY The Eigen does not support any specific security measures. It is assumed that the Eigen is used within a secured environment. It is assumed that a secured environment includes at a minimum: a. Firewall or router protections to ensure that only approved eternal hosts have network access to the. b. Firewall or router protections to ensure that the only has network access to approved eternal hosts and services. c. Any communication with eternal hosts and services outside the locally secured environment use appropriate secure network channels (e.g. such as a Virtual Private Network (VPN)) Other network security procedures such as automated intrusion detection may be appropriate in some environments. Additional security features may be established by the local security policy and are beyond the scope of this conformance statement. Page 26

28 A.8 ANNEXES A.8.1 IOD CONTENTS A Created SOP Instances Eamples of X-Ray Angiographic images created by the Eigen can be obtained by contacting Eigen. More information is available at: Table A specifies the attributes of an X-Ray Angiographic Image transmitted by the storage application. The abbreviations used in the Presence of column are: ALWAYS EMPTY Always Present Attribute is sent without a value The abbreviations used in the Source column: MWL USER AUTO CONFIG the attribute value source Modality Worklist the attribute value source is from User input the attribute value is generated automatically the attribute value source is a configurable parameter NOTE: All dates and times are encoded in the local configured calendar and time. Date, Time and Time zone are configured using control panel. A X-Ray Angiographic Image IOD Table A IOD OF CREATED XA SOP INSTANCES IE Module Reference Presence of Module Patient Patient Table A ALWAYS Study General Study Table A ALWAYS Series General Series Table A ALWAYS Equipment General Equipment Image Table A ALWAYS General Image Table A ALWAYS Image Piel Table A ALWAYS Contrast/Bolus Table A Cine Table A ALWAYS Multi-Frame X-Ray Image Table A ALWAYS Table A ALWAYS Page 27

29 X-Ray Acquisition SOP Common VOI LUT XA Positioner Table A ALWAYS Table A ALWAYS Table A ALWAYS Table A ALWAYS Table A PATIENT MODULE OF CREATED SOP INSTANCES Attribute Name Tag VR Value Patient s Name Patient ID Patient s Birth Date Patient s Se (0010,0010) PN (0010,0020) LO (0010,0030) DA (0010,0040) CS From Modality Worklist or user input. Values supplied via Modality Worklist will be entered as received. Maimum 64 characters. From Modality Worklist or user input. Maimum 64 characters. From Modality Worklist or user input From Modality Worklist or user input Presence of Value ALWAYS ALWAYS ALWAYS ALWAYS Source MWL/ USER MWL/ USER MWL/ USER MWL/ USER Table A GENERAL STUDY MODULE OF CREATED SOP INSTANCES Attribute Name Tag VR Value Study Instance UID (0020,000D) UI From Modality Worklist or generated by device Presence of Value ALWAYS Source MWL/ AUTO Study Date (0008,0020) DA <yyyymmdd> ALWAYS AUTO Study Time (0008,0030) TM <hhmmss> ALWAYS AUTO Referring Physician s Name Study ID (0008,0090) PN From Modality Worklist VNAP MWL (0020,0010) SH Requested Procedure ID from Worklist or User Input VNAP MWL/ USER Accession Number (0008,0050) SH From Modality Worklist VNAP MWL Study Description (0008,1030) LO Comment tet bo in study list. Maimum 1024 characters. VNAP USER Page 28

30 Table A GENERAL SERIES MODULE OF CREATED SOP INSTANCES Attribute Name Tag VR Value Presence of Value Source Modality (0008,0060) CS XA ALWAYS AUTO Series Instance UID (0020,000E) UI Generated by device ALWAYS AUTO Series Number (0020,0011) IS Generated by device ALWAYS AUTO Series Date (0008,0021) DA <yyyymmdd> ALWAYS AUTO Series Time (0008,0031) TM <hhmmss> ALWAYS AUTO Performing Physician s Name Series Description (0008,1050) PN (0008,103E) LO Physician field in Study list. Maimum 64 characters. User selected description. Maimum 512 characters. VNAP VNAP USER USER Attribute Name Table A GENERAL EQUIPMENT MODULE OF CREATED SOP INSTANCES Tag VR Value Presence of Value Manufacturer (0008,0070) LO EIGEN ALWAYS AUTO Institution Name Institution Address Source (0008,0080) LO From Configuration ALWAYS CONFIG (0008,0081) ST From Configuration ALWAYS CONFIG Station Name (0008,1010) SH From Configuration ALWAYS CONFIG Manufacturer s Model Name Device Serial Number Software Version (0008,1090) LO _ ( indicates version number) ALWAYS AUTO (0018,1000) LO From Configuration ALWAYS CONFIG (0018,1020) LO From Configuration ALWAYS CONFIG Attribute Name Instance Number Patient Orientation Table A GENERAL IMAGE MODULE OF CREATED SOP INSTANCES Tag VR Value Presence of Value Source (0020,0013) IS Generated by device ALWAYS AUTO (0020,0020) CS Zero length EMPTY AUTO Content Date (0008,0023) DA <yyyymmdd> ALWAYS AUTO Page 29

31 Content Time (0008,0033) TM <hhmmss> ALWAYS AUTO Acquisition Number Image Comments (0020,0012) IS Generated by device ALWAYS AUTO (0020,4000) LT From user input. Maimum 1024 characters. VNAP USER Attribute Name Table A IMAGE PIXEL MODULE OF CREATED SOP INSTANCES Tag VR Value Presence of Value Source Piel Data (7FE0,0010) OB Piel Data ALWAYS AUTO Piel Aspect Ratio (0028,0034) IS / ALWAYS AUTO Attribute Name Contrast/Bolus Agent Table A CONTRAST/BOLUS MODULE OF CREATED SOP INSTANCES Tag VR Value Presence of Value Source (0018,0010) LO Empty ALWAYS AUTO Attribute Name Table A CINE MODULE OF CREATED SOP INSTANCES Tag VR Value Presence of Value Source Frame Time (0018,1063) DS Depends on acquisition rate. ALWAYS AUTO Cine Rate (0018,0040) IS Depends on acquisition rate ALWAYS AUTO Effective Duration (0018,0072) DS Empty ALWAYS AUTO Frame Delay (0018,1066) DS Empty ALWAYS AUTO Attribute Name Number of Frames Table A MULTI-FRAME MODULE OF CREATED SOP INSTANCES Tag VR Value Presence of Value Source (0028,0008) IS Number of frames in image. ALWAYS AUTO Page 30

32 Attribute Name Frame Increment Pointer Table A X-RAY IMAGE MODULE OF CREATED SOP INSTANCES Tag VR Value Presence of Value Source (0028,0009) AT <0018,1063> ALWAYS AUTO Image Type (0008,0008) CS ORIGINAL\PRIMARY\SINGLE PLANE ALWAYS AUTO Piel Intensity Relationship Samples Per Piel Photometric Interpretation (0028,1040) CS DISP ALWAYS AUTO (0028,0002) US 1 ALWAYS AUTO (0028,0004) CS MONOCHROME2 ALWAYS AUTO Rows (0028,0010) US Depends on video source ALWAYS CONFIG Columns (0028,0011) US Depends on video source ALWAYS CONFIG Bits Allocated (0028,0100) US 8 ALWAYS AUTO Bits Stored (0028,0101) US 8 ALWAYS AUTO High Bit (0028,0102) US 7 ALWAYS AUTO Piel Representation (0028,0103) US 0 ALWAYS AUTO Attribute Name Table A X-RAY ACQUISITION MODULE OF CREATED SOP INSTANCES Tag VR Value Presence of Value Source KVP (0018,0060) DS Empty ALWAYS AUTO Radiation Setting X-Ray Tube Current (0018,1155) CS SC ALWAYS AUTO (0018,1152) IS Empty ALWAYS AUTO Attribute Name SOP Class UID SOP Instance UID Table A SOP COMMON MODULE OF CREATED SOP INSTANCES Tag VR Value Presence of Value Source (0008,0016) UI ALWAYS AUTO (0008,0018) UI Generated by device ALWAYS AUTO Page 31

33 Attribute Name Window Center Window Width Table A VOI LUT MODULE OF CREATED SOP INSTANCES Tag VR Value Presence of Value Source (0028,1050) DS 128 ALWAYS AUTO (0028,1051) DS 256 ALWAYS AUTO Attribute Name Positioner Motion Positioner Primary Angle Positioner Secondary Angle Table A XA POSITIONER MODULE OF CREATED SOP INSTANCES Tag VR Value Presence of Value Source (0018,1500) CS Empty ALWAYS AUTO (0018,1510) DS Empty ALWAYS AUTO (0018,1511) DS Empty ALWAYS AUTO A Used Fields in received IOD by application The Eigen does not receive SOP Instances. The usage of attributes received via Modality Worklist is described in section A Coerced/Modified Fields The Modality Worklist AE will truncate attribute values received in the response to a Modality Worklist Query if the value length is longer than the maimum length permitted by the attribute s VR. A.8.2 DATA DICTIONARY OF PRIVATE ATTRIBUTES The Eigen does not use any private attributes. A.8.3 CODED TERMINOLOGY AND TEMPLATES No Coded Terminology or Templates are supported. Page 32

34 A.8.4 STANDARD EXTENDED / PRIVATE SOP CLASSES No Specialized or Private SOP Classes are supported. A.8.5 PRIVATE TRANSFER SYNTAXES No Private Transfer Syntaes are supported. Page 33