HE/001212
Page 1 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
AGFA HEALTHCARE DICOM Conformance Statement
IMPAX RIS v5.4.3; v5.5.x; v5.6.x; v5.7.x Document No. 001212 Revision 2.2 NodeID LiveLink : 19530802
When printed, this is NOT a controlled copy
HE/001212
Page 2 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
Document Information
Service-related contact information worldwide
Issued by: Agfa HealthCare SIV Connectivity Septestraat 27 B-2640 Mortsel Belgium
tel: +32 3 444 75 88 email:
[email protected]
All service-related contact information is available on this URL
http://www.agfa.com/en/he/support/support_service/index.jsp
Agfa shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this publication. Agfa reserves the right to revise this publication and to make changes to its content at any time, without obligation to notify any person or entity of such revisions and changes. This publication may only be used in connection with the promotion, sales, installation and use of Agfa equipment. Copyright December, 09 Agfa HealthCare All rights reserved
HE/001212
Page 3 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
Conformance Statement Overview IMPAX RIS Dicomserver is the imaging device connectivity service of Agfa's RIS system and acts as a Modality Worklist Management Service Class Provider and a Modality Performed Procedure Step Manager. IMPAX RIS Dicomserver is only installed when MPPS is required or when there’s no Agfa PACS, otherwise the worklists are provided by Connectivity Manager or PACS Broker. Custom worklists can be configured per modality. Modality performed procedure step information is only used to update procedure statuses and to store radiation dose information in the RIS. Image Availability Notification is used to update availability status of the images in RIS database.
Table 1.1-1: Network Services Supported SOP Classes
User of Service (SCU)
Provider of Service (SCP)
Transfer
No
No
Query/Retrieve
No
No
No Yes No No
Yes Yes Yes No
Workflow Management Modality Worklist Information Model – FIND Modality Performed Procedure Step Instance Availability Notification Print Management
Table 1.1-2: Media Services Supported Media Storage Application Profile
Write Files (FSC or FSU)
Read Files (FSR)
Compact Disk - Recordable
No
No
Magneto-Optical Disk
No
No
DVD
No
No
HE/001212
Page 4 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
Table of Contents 1 1.1 1.2 1.3 1.3.1 1.3.2 1.4 1.5
2
Introduction ............................................................................................6 Revision Record ................................................................................................... 6 Purpose and Intended Audience of this Document ................................................ 6 General Remarks ................................................................................................. 6 Integration and Validation Activities.................................................................. 6 Future Evolution .............................................................................................. 7 Acronyms and Abbreviations ................................................................................ 7 Related Documents .............................................................................................. 8
Networking .............................................................................................9
2.1 Implementation Model .......................................................................................... 9 2.1.1 Application Data Flow Diagram........................................................................ 9 2.1.2 Functional Definitions of AE’s .......................................................................... 9 2.1.2.1 Functional Capability of C-FIND Modality Worklist....................................... 9 2.1.3 Functional Capability of N-CREATE and N-SET Modality Performed Procedure Step. 10 2.1.3.1 Functional Capability of N-CREATE Instance Availability Notification. ........10 2.1.4 Sequencing of Real World Activities................................................................10 2.2 AE Specifications.................................................................................................11 2.2.1 IMPAX-RIS Specification ................................................................................11 2.2.1.1 SOP Classes Supported ............................................................................11 2.2.1.2 Association Establishment Policies ............................................................11 2.2.1.2.1 General ................................................................................................11 2.2.1.2.2 Number of Associations ........................................................................11 2.2.1.2.3 Asynchronous Nature ...........................................................................11 2.2.1.2.4 Implementation Identifying Information..................................................12 2.2.1.3 Association Initiation Policies .....................................................................12 2.2.1.3.1 Forwarding MPPS messages................................................................12 2.2.1.3.1.1 Description and Sequencing of Activity 12 2.2.1.3.1.2 Proposed Presentation Contexts 13 2.2.1.4 Association Acceptance Policies................................................................13 2.2.1.4.1 Receive Query for Modality Worklist......................................................13 2.2.1.4.1.1 Description and Sequencing of Activity 13 2.2.1.4.1.2 Accepted Presentation Contexts 14 2.2.1.4.1.3 SOP Specific Conformance for Modality Worklist SOP Class 14 2.2.1.4.2 Receive MPPS Request .......................................................................17 2.2.1.4.2.1 Description and Sequencing of Activity 17 2.2.1.4.2.2 Accepted Presentation Contexts 18 2.2.1.4.2.3 SOP Specific Conformance for MPPS SOP Class 18 2.2.1.4.3 Receive Instance Availability Notification...............................................19 2.2.1.4.3.1 Accepted Presentation Contexts 20 2.2.1.4.3.2 SOP Specific Conformance for IAN SOP Class 20 2.3 Network Interfaces...............................................................................................20 2.3.1 Physical Medium Support ...............................................................................20 2.3.2 Additional Protocols........................................................................................20 2.4 Configuration.......................................................................................................21 2.4.1 AE Title/ Presentation Mapping.......................................................................21 2.4.1.1 Local AE Titles ..........................................................................................21
HE/001212
Page 5 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
2.4.1.2 2.4.1.2.1 2.4.2
Remote AE Titles.......................................................................................21 Remote SCP ........................................................................................21 Configuration Parameters...............................................................................21
3
Media Interchange................................................................................22
4
Support for Extended Character Sets...................................................23
5
Security ................................................................................................24
5.1 5.2 5.3
6 6.1 6.1.1 6.1.2 6.1.3
Security Profiles ..................................................................................................24 Association Level Security ...................................................................................24 Application Level Security....................................................................................24
Annexes ...............................................................................................25 IOD Contents.......................................................................................................25 Usage of Attributes from Basic Worklist Management IOD ..............................25 Usage of Attributes from Modality Performed Procedure Step IOD..................25 Usage of Attributes from Instance Availability Notification IOD ........................25
HE/001212
Page 6 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
1
INTRODUCTION
1.1
Revision Record Revision Number 1.0 1.1 2.0 2.1 2.2
1.2
Date
Reason for Change
February 26, 2003 July 3, 2006 January 24 , 2008 September 02 , 2009 December 02 , 2009
Initial version Updated layout Update Information and layout Update for RIS 5.6, add table 1.3-1, update table 2.2-14 Update conformance statement overview text and update table 1.3-1 for IMPAX RIS v5.7
Purpose and Intended Audience of this Document This document is a DICOM Conformance Statement for the DICOM Services of the IMPAX RIS product. The user of this document is involved with system integration and/or software design. We assume that the reader is familiar with the terminology and concepts that are used in the DICOM 3.0 standard and the IHE Technical Framework. Readers not familiar with DICOM 3.0 terminology should first read the appropriate parts of the DICOM standard itself, prior to reading this conformance statement. Although the use of this conformance statement in conjunction with the DICOM 3.0 standard is intended to facilitate communication with Agfa IMPAX RIS, it is not sufficient to guarantee, by itself, the inter-operation of the connection. The following issues need to be considered:
1.3
General Remarks IMPAX RIS Dicomserver is part of the 2005.3.1 ; 2005.3.3 and 2005.3.4 Connectivity Suite. Table 1.3-1 RIS version overview
RIS version
1.3.1
5.4.3 (incl. I-Plan 6.3) 5.5 (incl. I-Plan 6.3) 5.5.1 (incl. I-Plan 6.3) 5.6 (incl. I-Plan 6.3) 5.7 (incl. I-Plan 6.3)
2005.2.0 X
Connectivity Version 2005.3.1 2005.3.3 2005.3.4 X X X X X X X X
Integration and Validation Activities The integration of any device into a system of interconnected devices goes beyond the scope of the DICOM 3.0 standard and this conformance statement when interoperability is desired. The responsibility for analyzing the applications requirements and developing a solution that integrates the Agfa equipment with other vendors’ systems is the user’s responsibility and should not be underestimated.
HE/001212
Page 7 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
In some circumstances it might be necessary to perform a validation to make sure that functional interoperability between the Agfa equipment and non-Agfa devices works as expected. The user should ensure that any non-Agfa provider accepts responsibility for any validation required for their connection with the Agfa equipment.
1.3.2
Future Evolution As the DICOM 3.0 standard evolves to meet the user’s growing requirements and to incorporate new features and technologies, Agfa will follow the evolution of the standard. This evolution of the standard may require changes to devices that have implemented DICOM 3.0. The user should ensure that any non-Agfa provider, who connects with Agfa devices, also plans for future evolution of the DICOM standard. A refusal to do so may result in the loss of functionality and/or connectivity between the different products.
1.4
Acronyms 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
DICOM Application Entity
AET
Application Entity Title
ASCE
Association Control Service Element
CD-R
Compact Disk Recordable
DICOM
Digital Imaging and Communications in Medicine
FSC
File-Set Creator
FSU
File-Set Updater
FSR
File-Set Reader
GSDF
Grayscale Standard Display Function
GSPS
Grayscale Softcopy Presentation State
IAN
Instance Availability Notification
IE
Information Entity
IOD
(DICOM) Information Object Definition
ISO
International Standard Organization
MPPS
Modality Performed Procedure Step
MSPS
Modality Scheduled Procedure Step
PDU
DICOM Protocol Data Unit
SCU
DICOM Service Class User (DICOM client)
SCP
DICOM Service Class Provider (DICOM server)
SOP
DICOM Service-Object Pair
UID
Unique Identifier
VR
Value Representation
HE/001212
Page 8 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
1.5
10 December, 2009
Related Documents ACR-NEMA Digital Imaging and Communications in Medicine (DICOM) V3.0. IHE Radiology Technical Framework Revision 6 – Final Text, May 2005
HE/001212
Page 9 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
2
NETWORKING
2.1
Implementation Model
2.1.1
Application Data Flow Diagram
Remote Verification Real World Activity
Local Real World Activity (e.g., sql query database)
Remote DICOM MWL SCU
IMPAX-RIS Legend Local Application Entity Real World Activity
Remote DICOM MPPS SCU
Association Negotiation DICOM Standard Interface
Internal Communication
Figure 2.1-1: Functional Overview – Application Data Flow
The DICOM Query is translated into a SQL Query which is executed on the RIS database. The result of the query is translated into a DICOM response.
The DICOM instance availability is used to track image availability in the RIS database.
The DICOM MPPS is used to update the procedure status in the RIS database.
2.1.2
Functional Definitions of AE’s
2.1.2.1
Functional Capability of C-FIND Modality Worklist. IMPAX RIS Dicomserver will accept requests to C-FIND a modality work list. These modality work lists are queried from the database through a SQL interface.
HE/001212
Page 10 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
2.1.3
10 December, 2009
Functional Capability of N-CREATE and N-SET Modality Performed Procedure Step. IMPAX RIS Dicomserver accepts N-CREATE and N-SET Modality Performed Procedure Steps. The IMPAX RIS Dicomserver updates the procedure status in the IMPAX RIS database.
2.1.3.1
Functional Capability of N-CREATE Instance Availability Notification. IMPAX RIS Dicomserver accepts N-CREATE Instance Availability Notifications and updates image availability status in the RIS database.
2.1.4
Sequencing of Real World Activities IMPAX RIS Dicomserver must have an installed/working connection with the IMPAX RIS database and with one or more suitable SCU. Query information is formed on the SCU and then sent to IMPAX RIS Dicomserver. The requesting device must have the DICOM parameters set and configured prior to using the modality's query facilities. The set and configuration of DICOM Modality Worklist SCUs is done using the tools provided by the device's vendor. As a result of the request IMPAX RIS Dicomserver queries the RIS database and sends a list of tasks that have been scheduled for the requesting modality out of which the device's operator can select the item which is to be performed in reality. If IMPAX RIS Dicomserver receives an N-CREATE, at the start of the imaging, or a N-SET, at the end of the imaging, it updates the procedure status in the RIS database.
Figure 2.1-2: sequencing constraints
HE/001212
Page 11 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
2.2
AE Specifications
2.2.1
IMPAX-RIS Specification
2.2.1.1
SOP Classes Supported This Application Entity provides Standard Conformance to the following SOP Class(es): Table 2.2-1: SOP Class(es) SOP Class Name
SOP Class UID
SCU
SCP
Workflow Management Modality Worklist Information Model - FIND Modality Performed Procedure Instance Availability Notification
1.2.840.10008.5.1.4.31 1.2.840.10008.3.1.2.3.3 1.2.840.10008.5.1.4.33
2.2.1.2
Association Establishment Policies
2.2.1.2.1
General
No No No
Yes Yes Yes
The DICOM standard Application context shall be specified. Table 2.2-2: DICOM Application Context Application Context Name
2.2.1.2.2
1.2.840.10008.3.1.1.1
Number of Associations Table 2.2-3: Number of Associations as an Association Initiator Maximum number of simultaneous associations initiated
1
Table 2.2-4: Number of Associations as an Association Acceptor Maximum number of simultaneous associations accepted
2.2.1.2.3
32
Asynchronous Nature Table 2.2-5: Asynchronous Nature as an Association Initiator Maximum number of outstanding asynchronous transactions
X
IMPAX RIS Dicomserver allows a single outstanding operation on any association. Therefore, IMPAX RIS Dicomserver does not support asynchronous operations window negotiation, other than the default as specified by the DICOM specification.
HE/001212
Page 12 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
2.2.1.2.4
10 December, 2009
Implementation Identifying Information Table 2.2-6: DICOM implementation Class and Version Implementation Class UID
1.3.51.0.1.3
Implementation Version Name
AGFA DTF1.0.64
2.2.1.3
Association Initiation Policies
2.2.1.3.1
Forwarding MPPS messages
2.2.1.3.1.1
Description and Sequencing of Activity The IMPAX RIS Dicomserver Application Entity forwards the MPPS received from the Modality to the PACS (image manager). This functionality is required in case IMPAX RIS plays the role of IHE MPPS Manager Actor for the IHE profile “Scheduled Workflow” and “Patient Information Reconciliation”.
RIS AE
Modality
PACS
1. Open 2. N-CREATE (MPPS) - IN PROGRESS
N-CREATE (MPPS) - IN PROGRESS
3. Close
4. Aquire Images()
5. Open 6. N-SET (MPPS) COMPLETED
N-SET (MPPS) - COMPLETED
7. Close
Figure 2.2-1: IMPAX-RIS MPPS forwarding Sequencing Diagram
HE/001212
Page 13 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
2.2.1.3.1.2
10 December, 2009
Proposed Presentation Contexts Table 2.2-7: Presentation Contexts Presentation Context Table Abstract Syntax
Name Modality Performed Procedure
Transfer Syntax
UID 1.2.840.10008.3.1.2.3.3
Name List Implicit VR Little Endian Explicit VR Little Endian
2.2.1.4
Association Acceptance Policies
2.2.1.4.1
Receive Query for Modality Worklist
2.2.1.4.1.1
UID List 1.2.840.10008.1.2
Role SCU
Extended Negotiation None
1.2.840.10008.1.2.1
Description and Sequencing of Activity
Imaging Modality
IMPAX-RIS
1. Open Association 2. C-FIND(query parameters)
3. C-FIND-RSP (Intermediate Response with dataset)
4. C-FIND-RSP (Final Response)
5. Close Association
Figure 2.2-2: IMPAX-RIS Sequencing Diagram
HE/001212
Page 14 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
2.2.1.4.1.2
Accepted Presentation Contexts Table 2.2-8: Presentation Contexts Presentation Context Table Abstract Syntax
Name
Transfer Syntax
UID
Modality Worklist Information Model - FIND
Name List
1.2.840.10008.5.1.4.31
2.2.1.4.1.3
Implicit VR Little Endian Explicit VR Little Endian
Extended Negotiation
Role
UID List 1.2.840.10008.1.2
SCP
None
1.2.840.10008.1.2.1
SOP Specific Conformance for Modality Worklist SOP Class IMPAX RIS Dicomserver supports all required matching key types: Table 2.2-9: Matching Key Types Matching Key Types SV
single valued match
WC SQ DR
wild card match sequence match date range match
IMPAX RIS Dicomserver accepts the following elements and applies the following matching for this SOP class: Table 2.2-10: Dicomserver Elements and matching Module Scheduled Procedure Step
Requested Procedure Imaging Service Request Patient Identification
Attribute Name
Tag
Scheduled Procedure Step Sequence
(0040,0100)
>Scheduled Station AE Title >Scheduled Procedure Step Start Date >Modality Requested Procedure ID Accession Number Patient Name Patient ID
(0040,0001) (0040,0002) (0008,0060) (0040,1001) (0008,0050) (0010,0010) (0010,0020)
Match
Return 1
SV DR SV SV SV WC SV
1 1 1 1 2 1 1
IMPAX RIS Dicomserver supports the following elements in the response: Table 2.2-11: Dicomserver Supported elements Module SOP Common Scheduled Procedure Step
Attribute Name Specific Character Set Query/Retrieve Level Scheduled Procedure Step Sequence
Tag (0008,0005) (0008,0052) (0040,0100)
Return SV Zero length SQ
HE/001212
Page 15 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
Module
Requested Procedure
Imaging Service Request
10 December, 2009
Attribute Name
Tag
Return
>Scheduled Station AE Title >Scheduled Procedure Step Start Date >Scheduled Procedure Step Start Time >Scheduled Procedure Stop End Date >Scheduled Procedure Stop End Time >Modality >Scheduled Performing Physician >Scheduled Procedure Step Desc. >Scheduled Station Name >Scheduled Procedure Step Location >Scheduled Action Item Code Seq. >>Code Value >>Coding Scheme Designator >>Code Meaning >Pre-Medication >Scheduled Procedure Step ID >Requested Contrast Agent >Scheduled Procedure Step Status >Comments on the Scheduled Procedure Step Requested Procedure ID Requested Procedure Description Reason for Requested Procedure Requested Procedure Code Sequence >Code Value >Coding Scheme Designator >Code Meaning Study Instance UID Referenced Study Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Requested Procedure Priority Patient Transport Arrangements Requested Procedure Location Requested Procedure Comments Confidentiality Code Reporting Priority Names of Intended Recipients of Results Accession Number Imaging Service Request Comments Requesting Physician Requesting Service Referring Physician Name Issue Date of Imaging Service Request Issue Time of Imaging Service Request Placer Order Number / Imaging Service Request Filler Order Number / Imaging Service Request Reason for Imaging Service Request Order Entered by …
(0040,0001) (0040,0002) (0040,0003) (0040,0004) (0040,0005) (0008,0060) (0040,0006) (0040,0007) (0040,0010) (0040,0011) (0040,0008) (0008,0100) (0008,0102) (0008,0104) (0040,0012) (0040,0009) (0032,1070) (0040,0020) (0040,0400) (0040,1001) (0032,1060) (0040,1002) (0032,1064) (0008,0100) (0008,0102) (0008,0104) (0020,000D) (0008,1110) (0008,1150) (0008,1155) (0040,1003) (0040,1004) (0040,1005) (0040,1400) (0040,1008) (0040,1009) (0040,1010) (0008,0050) (0040,2400) (0032,1032) (0032,1033) (0008,0090) (0040,2004) (0040,2005) (0040,2016) (0040,2017) (0040,2001) (0040,2008)
SV or Zero length SV or Zero length SV or Zero length SV or Zero length SV or Zero length SV or Zero length SV or Zero length SV or Zero length SV or Zero length SV or Zero length SQ SV or Zero length SV or Zero length SV or Zero length Zero length SV or Zero length Zero length SV or Zero length Zero length SV or Zero length SV or Zero length Zero length SQ SV or Zero length SV or Zero length SV or Zero length SV or Zero length Zero length SV SV SV or Zero length Zero length Zero length SV or Zero length Zero length Zero length Zero length SV or Zero length SV or Zero length SV or Zero length SV or Zero length SV or Zero length Zero length Zero length Zero length SV or Zero length Zero length Zero length
HE/001212
Page 16 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
Module
Visit Identification
Visit Status Visit Relationship
Visit Admission Patient Identification
Patient Demographic
Patient Medical
Attribute Name Order Enterer's Location Order Callback Phone Number Admission ID Issuer of Admission ID Institution Name Institution Address Current Patient Location Referenced Patient Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Admitting Diagnosis Description Patient Name Patient ID Issuer of Patient ID Ethnic Group Other Patient ID Other Patient Name Patient Address Patient Birth Date Patient Sex Patient Weight Patient's Size Confidentiality Constraint Region of Residence Military Rank Patient Comments Patient State Smoking Status Additional Patient History Pregnancy Status Last Menstrual Date Medical Alerts Contrast Allergies Special Needs
Tag
Return
(0040,2009) (0040,2010) (0038,0010) (0038,0011) (0008,0080) (0008,0081) (0038,0300) (0008,1120) (0008,1150) (0008,1155) (0008,1080) (0010,0010) (0010,0020) (0010,0021) (0010,2160) (0010,1000) (0010,1001) (0010,1040) (0010,0030) (0010,0040) (0010,1030) (0010,1020) (0040,3001) (0010,2152) (0010,1080) (0010,4000) (0038,0500) (0010,21A0) (0010,21B0) (0010,21C0) (0010,21D0) (0010,2000) (0010,2110) (0038,0050
Zero length Zero length SV or Zero length Zero length Zero length Zero length SV or Zero length Zero length Zero length Zero length Zero length SV or Zero length SV or Zero length SV or Zero length Zero length Zero length Zero length SV or Zero length SV or Zero length SV or Zero length Zero length Zero length Zero length Zero length Zero length Zero length Zero length Zero length Zero length Zero length Zero length Zero length Zero length Zero length
Table 2.2-12: IMPAX RIS Dicomserver Response Status Service Status Success Error Pending
Further Meaning Success Processing Failure More matches to come
Error Code 0000 C000 FF00
Reason Operation performed properly, all matches were returned No access to RIS database This status is returned with each matching response
HE/001212
Page 17 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
2.2.1.4.2 2.2.1.4.2.1
10 December, 2009
Receive MPPS Request Description and Sequencing of Activity After a modality has started the performance of a Procedure Step it should inform the RIS by sending an N-CREATE service request to the RIS Application Entity. An N-CREATE event with status “IN PROGRESS” will update the procedure status in IMPAX RIS to “PROCEDURE STARTED”. At the end of the Performed Procedure Step the modality should send a N-SET command with all other mandatory attributes to RIS Application Entity. An N-SET event with status “COMPLETED” will update the procedure status in IMPAX RIS to “PROCEDURE COMPLETE”.
Modality
RIS AE
1. Open 2. N-CREATE (MPPS) - IN PROGRESS 3. Close
4. Aquire Images()
5. Open 6. N-SET (MPPS) COMPLETED 7. Close
Figure 2.2-3: IMPAX-RIS Sequencing Diagram
HE/001212
Page 18 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
2.2.1.4.2.2
Accepted Presentation Contexts Table 2.2-13: Presentation Contexts Presentation Context Table Abstract Syntax
Name
Transfer Syntax
UID
Modality Performed Procedure
Name List
1.2.840.10008.3.1.2.3.3
2.2.1.4.2.3
Implicit VR Little Endian Explicit VR Little Endian
UID List 1.2.840.10008.1.2
Role SCP
Extended Negotiation None
1.2.840.10008.1.2.1
SOP Specific Conformance for MPPS SOP Class IMPAX RIS Dicomserver supports all attributes as described in the Dicom Standard part 3.3 for MPPS, however IMPAX RIS Dicomserver only stores the attributes mentioned in the table below. Table 2.2-14: Attributes supported Attribute Name
Tag
N-Create
N-Set
Comments
PERFORMED PROCEDURE STEP INFORMATION MODULE ATTRIBUTES Schedule Step Attribute Sequence >Study Instance UID >Accession Number >Scheduled Protocol Code Sequence >>Code Value >>Code Meaning Patient ID Patient Name
(0040,0270) (0020,000d) (0008,0050) (0040,0008) (0008,0100) (0008,0104) (0010,0020) (0010,0010)
X X X X X X X X
Patient Birth Date Patient Sex Performed Procedure Step ID
(0010,0030) (0010,0040) (0040,0253)
X X X
Performed Procedure Step Start Date Performed Procedure Step Start Time Performed Procedure Step Status Procedure Code Sequence >Code Value
(0040,0244) (0040,0245) (0040,0252) (0008,1032) (0008,0100)
X X X X X
>Code Meaning Modality Performed Protocol Code Sequence
(0008,0104) (0008,0060) (0040,0260)
X X X
X
>Code Value >Code Meaning
(0008,0100) (0008,0104)
X X
X X
X X X
X
RADIATION DOSE MODULE ATTRIBUTES Total Number of Exposures
(0040,0301)
X
X
Entrance Dose
(0040,0302)
X
X
Only used if (0040,8302) is empty
HE/001212
Page 19 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
Attribute Name
Tag
N-Create
N-Set
Entrance Dose in mGy Image and Fluoroscopy Area Dose Product Comments on Radiation Dose
(0040,8302) (0018,115E)
X X
X X
(0040,0310)
X
X
Exposure Dose Sequence >KVp
(0040,030E) (0018,0060)
X X
X X
>Exposure Time
(0018,1150)
X
X
Comments
Used by certain modalities
Only used if (0018,8150) is empty
CR IMAGE MODULE ATTRIBUTES KVP X-ray Tube Current
(0018,0060) (0018,1151)
X X
X X
Exposure
(0018,1152)
X
X
Exposure in μAs
(0018,1153)
X
X
Only used if (0018,1153) is empty
Table 2.2-15: IMPAX RIS Dicomserver MPPS Response Status Service Status Success Error
2.2.1.4.3
Further Meaning Success Processing Failure
Error Code 0000 C000
Reason Operation performed properly, all matches were returned No access to RIS database
Receive Instance Availability Notification
PACS
RIS AE
Instance Availability Notification (N-CREATE)
Figure 2.2-4: Instance Availability Notification Sequencing Diagram
HE/001212
Page 20 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
2.2.1.4.3.1
10 December, 2009
Accepted Presentation Contexts Table 2.2-16: Presentation Contexts Proposed Presentation Context Table Abstract Syntax
Name Instance Availability Notification
2.2.1.4.3.2
UID 1.2.840.10008.5.1.4.33
Transfer Syntax Name List Implicit VR Little Endian Explicit VR Little Endian
UID List 1.2.840.10008.1.2
Role SCP
Extended Negotiation None
1.2.840.10008.1.2.1
SOP Specific Conformance for IAN SOP Class Only Study Instance UID (0020,000D) is used by IMPAX RIS to update a flag in the database to indicate that images are available.
2.3
Network Interfaces IMPAX RIS Dicomserver provides DICOM V3.0 TCP/IP Network Communication Support as defined in PS 3.8 of the DICOM Standard. IMPAX-RIS inherits its TCP/IP stack from the computer system upon which it resides.
2.3.1
Physical Medium Support IMPAX RIS Dicomserver is indifferent to the physical medium over which TCP/IP executes; it inherits the medium from the computer system upon which it is being executed.
2.3.2
Additional Protocols
HE/001212
Page 21 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
2.4
Configuration
2.4.1
AE Title/ Presentation Mapping
2.4.1.1
Local AE Titles Table 2.4-1: AE Title Configuration Table
Application Entity
Default AE Title
IMPAX RIS Dicomserver
2.4.1.2
Default TCP/IP Port
RIS_QUADRAT
2250
Remote AE Titles Remote AE titles are stored in a configuration file and are entered via the GUI.
2.4.1.2.1
Remote SCP Remote AET port number, host-names and IP addresses are stored in a configuration file, either the IP address or host-name is needed.
2.4.2
Configuration Parameters Table 2.4-2: Configuration Parameter Table Parameter
Configurable (Yes/No)
Default Value
General Parameters Time-out waiting for acceptance or rejection Response to an Association Open Request. (Application Level timeout) General DIMSE level time-out values Time-out waiting for response to TCP/IP connect request. (Low-level timeout) Time-out waiting for acceptance of a TCP/IP message over the network. (Low-level timeout) Time-out for waiting for data between TCP/IP packets. (Lowlevel timeout) Any changes to default TCP/IP settings, such as configurable stack parameters. Other configurable parameters
No
100 seconds
No No
100 seconds 100 seconds
No
100 seconds
No
100 seconds
No
100 seconds
Logging on/off
off
AE Specific Parameters Size constraint in maximum object size (see note 1) Maximum PDU size the AE can receive Maximum PDU size the AE can send AE specific DIMSE level time-out values Number of simultaneous Associations by Service and/or SOP Class (e.g. Multi-frame vs. single frame vs. SC support), when configurable , e.g. JPEG, Explicit VR, when configurable Other parameters that are configurable
No No No No No
65542 65542
No No
Implicit VR Little Endian
HE/001212
Page 22 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
3
10 December, 2009
MEDIA INTERCHANGE Not supported.
HE/001212
Page 23 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
4
10 December, 2009
SUPPORT FOR EXTENDED CHARACTER SETS IMPAX RIS Dicomserver supports the following character sets:
ISO-IR 6 (default)
Basic G0 Set
ISO-IR 100
Latin Alphabet No. 1
HE/001212
Page 24 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
5
SECURITY
5.1
Security Profiles
5.2
Association Level Security IMPAX RIS Dicomserver keeps a list of allowed AE-titles. When the list is empty, all AE-titles are accepted.
5.3
Application Level Security The RIS database is password protected.
HE/001212
Page 25 of 25 Document No. 001212 Revision 2.2 NodeID Livelink : 19530802
Agfa HealthCare
10 December, 2009
6
ANNEXES
6.1
IOD Contents
6.1.1
Usage of Attributes from Basic Worklist Management IOD IMPAX RIS Dicomserver provides standard conformance to the DICOM Basic Worklist Management Service Class.
6.1.2
Usage of Attributes from Modality Performed Procedure Step IOD IMPAX RIS Dicomserver provides standard conformance to the DICOM Modality Performed Procedure Step Service Class.
6.1.3
Usage of Attributes from Instance Availability Notification IOD IMPAX RIS Dicomserver provides standard conformance to the DICOM Instance Availability Notification Service Class. IMPAX RIS Dicomserver uses the following elements for this SOP class (other elements are ignored): Attribute Name Study Instance UID
Tag (0020,000D)
Details as of PDF Creation Date Document Metadata Title:
001212_IMPAX RIS v5.4.3 ; v5.5.x ; v5.6.x ; v5.7.x DICOM Conformance Statement
Livelink ID:
19530802
Version#:
10
Version Date:
2009/12/02 03:54 PM CET
Status:
Approved on 2009/12/10 12:57 PM CET
Owner:
Peter Buytaert (awabr)
Created By:
Bruno Laffin (nawyv)
Created Date:
2007/10/04 01:50 PM CET
PDF Creation Date:
2009/12/10 12:58 PM CET
This document was approved by: Signatures: 1. Sofie Neyrinck (amirm) on 2009/12/10 12:04 PM CET 2. Ann De Roose (amiqe) on 2009/12/03 05:16 PM CET 3. Bruno Laffin (nawyv) on 2009/12/03 04:09 PM CET Detailed Approver History:
Approval task originally assigned to and completed by Sofie Neyrinck (amirm) Approval task originally assigned to and completed by Bruno Laffin (nawyv) Approval task originally assigned to and completed by Ann De Roose (amiqe)
Version & Status History Version# Date Created
Status
10
2009/12/02 03:54 PM CET
Approved - 2009/12/10
9
2009/11/30 10:15 AM CET
Reviewed - 2009/12/01
8
2009/09/02 02:56 PM CET
Approved - 2009/09/21 Reviewed - 2009/09/10
7
2008/02/13 02:35 PM CET
Approved - 2008/02/14
6
2008/02/12 03:48 PM CET
Rejected - 2008/02/13
5
2008/02/11 05:01 PM CET
4
2008/01/31 12:42 PM CET
3
2008/01/24 05:21 PM CET
2
2007/10/04 02:05 PM CET
1
2007/10/04 01:50 PM CET
Reviewed - 2008/02/11