AGFA HEALTHCARE DICOM Conformance Statement · HE/001359 Page 1 of 33 Document No. 001359-Revision:...

HE/001359 of 33Document No. 001359 - Revision: 1.1

Livelink NodeID: 32940311Agfa HealthCare

AGFA HEALTHCAREDICOM Conformance Statement

IMPAX EE Mammography

Document No. 001359Revision: 1.1Livelink NodeID: 32940311

When printed, this is NOT a controlled copy


Livelink NodeID: 32940311Agfa HealthCare 23 May, 2011

Document Information

Service-related contact information worldwide

All service-related contact information is available on this URL

http://www.agfahealthcare.com/global/en/main/contact/index.jsp

Issued by:Agfa HealthCareSIV ConnectivitySeptestraat 27B-2640 MortselBelgium

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.

tel: +32 (0)3 444 7588email: [email protected]

Copyright May, 11Agfa HealthCare

All rights reserved



mailto:[email protected]



Conformance Statement Overview

This DICOM conformance Statement refers to IMPAX EE Mammography.

IMPAX EE Mammography conforms DICOM 3.0 2009 standard.

IMPAX EE Mammography supports Standard Conformance to the SOP classes of Table 1.1-1. TheseSOP classes are included in DICOM Supplement 64.

Table 1.1-1: Network Services Supported

SOP Classes User of Service (SCU)

Provider of Service (SCP)

Display

VerificationVerification Yes Yes N/A

TransferComputed Radiography Image Storage Yes Yes YesDigital Mammography X-Ray Image Storage – ForPresentation Yes Yes Yes

Ultrasound Multi-frame Image Storage Yes Yes YesSecondary Capture Image Storage Yes Yes YesMulti-frame Grayscale Byte Secondary Capture Image Storage Yes Yes Yes

Multi-frame Grayscale Word Secondary Capture Image Storage Yes Yes Yes

Multi-frame True Color Secondary Capture Image Storage Yes Yes Yes

Grayscale Softcopy Presentation State Storage SOP Class Yes Yes Yes

Basic Text SR Storage Yes Yes YesEnhanced SR Storage Yes Yes YesComprehensive SR Storage Yes Yes YesKey Object Selection Document Storage Yes Yes Yes

Query/RetrievePatient Root Query/Retrieve Information Model –FIND Yes No N/A

Patient Root Query/Retrieve Information Model –MOVE Yes No N/A

Study Root Query/Retrieve Information Model –FIND Yes No N/A

Study Root Query/Retrieve Information Model –MOVE Yes No N/A

Workflow ManagementModality Worklist Information Model – FIND Yes No N/AStorage Commitment Push Model SOP Class Yes No N/AModality Performed Procedure Step SOP Class Yes No N/A



Table 1.1-2: Media Service Supported

Media Storage Application Profile Write Files (FSCor FSU)

Read Files (FSR)

Compact Disk - RecordableGeneral Purpose CD-R No Yes



Table of Contents

1 Introduction ............................................................................................71.1 Revision Record ................................................................................................... 71.2 Purpose and Intended Audience of this Document................................................ 71.3 General Remarks ................................................................................................. 71.3.1 Integration and Validation Activities.................................................................. 71.3.2 Future Evolution .............................................................................................. 71.4 Acronyms and Abbreviations ................................................................................ 81.5 Related Documents .............................................................................................. 8

2 Networking .............................................................................................92.1 Implementation Model .......................................................................................... 92.1.1 Application Data Flow Diagram.......................................................................102.1.2 Functional Definitions of AE’s .........................................................................112.1.2.1 Functional Capability of IMPAX EE Mammography CLIENT.......................112.1.3 Sequencing of Real World Activities................................................................112.2 AE Specifications.................................................................................................122.2.1 IMPAX EE Mammography CLIENT Specification ............................................122.2.1.1 SOP Classes Supported ............................................................................122.2.1.2 Association Establishment Policies ............................................................132.2.1.2.1 General ................................................................................................132.2.1.2.2 Number of Associations ........................................................................132.2.1.2.3 Asynchronous Nature ...........................................................................132.2.1.2.4 Implementation Identifying Information..................................................132.2.1.3 Association Initiation Policies .....................................................................142.2.1.3.1 Verify Connection (SCU).......................................................................142.2.1.3.1.1 Description and Sequencing of Activity 142.2.1.3.1.2 Proposed Presentation Contexts 142.2.1.3.1.3 SOP Specific Conformance – Verification 142.2.1.3.2 Query images, KO, GSPS and SR........................................................142.2.1.3.2.1 Description and Sequencing of Activity 142.2.1.3.2.2 Proposed Presentation Contexts 152.2.1.3.2.3 SOP Specific Conformance Statement for Q/R Study Root Information Model – FIND 162.2.1.3.2.4 SOP Specific Conformance Statement for Q/R Patient Root Information Model – FIND 172.2.1.3.3 Retrieve images, KO, GSPS and SR.....................................................172.2.1.3.3.1 Description and Sequencing of Activity 172.2.1.3.3.2 Proposed Presentation Contexts 172.2.1.3.4 Store images, GSPS, KO and SR .........................................................182.2.1.3.4.1 Description and Sequencing of Activity 182.2.1.3.4.2 Proposed Presentation Contexts 182.2.1.3.5 Storage Commitment (Request)............................................................182.2.1.3.5.1 Description and Sequencing of Activity 182.2.1.3.5.2 Proposed Presentation Contexts 182.2.1.3.6 Query Modality Worklist ........................................................................192.2.1.3.6.1 Description and Sequencing of Activity 192.2.1.3.6.2 Proposed Presentation Contexts 202.2.1.3.6.3 SOP Specific Conformance – Modality Worklist Information Model –FIND 202.2.1.3.7 Modality Performed Procedure Step (SCU)...........................................212.2.1.3.7.1 Description and Sequencing of Activity 21



2.2.1.3.7.2 Proposed Presentation Contexts 212.2.1.3.7.3 SOP Specific Conformance – MPPS 212.2.1.4 Association Acceptance Policies................................................................242.2.1.4.1 Verify Connection .................................................................................242.2.1.4.1.1 Description and Sequencing of Activity 242.2.1.4.1.2 Accepted Presentation Contexts 242.2.1.4.2 Receive images, GSPS, KO and SR.....................................................242.2.1.4.2.1 Description and Sequencing of Activity 242.2.1.4.2.2 Accepted Presentation Contexts 242.2.1.4.2.3 SOP Specific Conformance Statement for Storage SOP classes 252.2.1.4.3 Storage commitment (Report) ...............................................................252.2.1.4.3.1 Description and Sequencing of Activity 252.2.1.4.3.2 Accepted Presentation Contexts 252.2.1.4.3.3 SOP Specific Conformance Statement for Storage Commitment (Report) 262.3 Network Interfaces...............................................................................................262.3.1 Physical Medium Support ...............................................................................262.4 Configuration.......................................................................................................272.4.1 AE Title/ Presentation Mapping.......................................................................272.4.1.1 Local AE Titles ..........................................................................................272.4.1.2 Remote AE Titles.......................................................................................272.4.2 Configuration Parameters...............................................................................27

3 Media Interchange................................................................................283.1 Implementation Model .........................................................................................283.1.1 Application Data Flow Diagram.......................................................................283.1.2 Functional Definition of IMPAX EE Mammography CLIENT AE.......................283.1.3 Sequencing of Real World Activities................................................................293.1.4 File Meta Information for Implementation Class and Version ...........................293.2 AE Specifications.................................................................................................293.2.1 IMPAX EE Mammography CLIENT AE Specification ......................................293.2.1.1 File Meta Information for Implementation IMPAX EE Mammography CLIENT

293.2.1.2 Real World Activities..................................................................................293.2.1.2.1 Real World Activity – Import DICOM objects from CD ...........................293.2.1.2.1.1 Media Storage Application Profile 293.2.1.2.2 Real World Activity – Load DICOM objects from CD..............................303.2.1.2.2.1 Media Storage Application Profile 30

4 Support for Extended Character Sets...................................................31

5 Security ................................................................................................325.1 Security Profiles ..................................................................................................325.2 Association Level Security ...................................................................................325.3 Application Level Security....................................................................................32

6 Annexes ...............................................................................................336.1 IOD Contents.......................................................................................................336.1.1 Coerced/ Modified Fields ................................................................................336.2 Grayscale Image Consistency .............................................................................33



1 INTRODUCTION

1.1 Revision Record

Dicom Conformance Statement IMPAX EE Mammography

Revision Number Date Reason for Change

1.0 2011-03-31 Initial version1.1 2011-05-12 Update document after review

1.2 Purpose and Intended Audience of this DocumentThis document is a DICOM Conformance Statement for the DICOM Services of the IMPAX EE Mammography 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 EE Mammography, 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

1.3.1 Integration and Validation ActivitiesThe 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.

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 EvolutionAs 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 AbbreviationsDefinitions, 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

CD-R Compact Disk Recordable

DICOM Digital Imaging and Communications in Medicine

DIMSE DICOM Message Service Element

DVD Digital Versatile Disc or Digital Video Disc

FSC File-Set Creator

FSR File-Set Reader

FSU File-Set Updater

GSPS Grayscale Softcopy Presentation State

IE Information Entity

IOD (DICOM) Information Object Definition

IP Internet Protocol

ISO International Standard Organization

KO Key Object

MPPS Modality Performed Procedure Step

PDU DICOM Protocol Data Unit

SCP DICOM Service Class Provider (DICOM server

SCU DICOM Service Class User (DICOM client)

SMTP Simple Mail Transfer Protocol

SOP DICOM Service-Object Pair

SR Structure Report

S/MIME Secure/Multipurpose Internet Mail Extensions

TCP Transmission Control Protocol

UID Unique Identifier

VR Value Representation

1.5 Related Documents

ACR-NEMA Digital Imaging and Communications in Medicine (DICOM) V3.0.

IHE Radiology Technical Framework Revision 10 – Final Text, Feb 2011



2 NETWORKING

2.1 Implementation ModelAll DICOM Services provided by IMPAX EE Mammography are implemented in one process, which is launched and terminated by the user.

This process hosts a DICOM server listening on different ports that requires the assignation of an Application Entity Title to the application. That motivates to describe the DICOM functionality of IMPAX EE Mammography as provided an Application Entity:

IMPAX EE Mammography CLIENT provides DICOM Services related with images and DICOM Structured Report Documents that includes Storage Services to receive images of MG, CR, US modalities, Grayscale Presentation States (GSPS), Key Object (KO) and Structure Report (SR) Documents. Selection Documents, but also the Storage Commitment Push Model Service as Service Class User (SCU), and Query/Retrieve Services, to query archives for available images, GSPS and KO objects and repositories for available SR documents. These Services also retrieve such DICOM information objects triggered by user interactions.



2.1.1 Application Data Flow Diagram

.

IMPAX EE Mammography

CLIENT

QueryKO,GSPS, Images and

SR

Retrieve KO,GSPS, Images and

SR

Receive KO, GSPS, Images and

SR

VerifyConnection

VerifyConnection

ModalityPerformedProcedure

Step

Storage Commitment

LoadImages, KOGSPS and

SR

DisplayImages, KOGSPS and

SR

FindObjects

MoveObjects

Dicom Interface

Query ModalityWorklist



2.1.2 Functional Definitions of AE’s

2.1.2.1 Functional Capability of IMPAX EE Mammography CLIENT

Verify the connection to DICOM peer Application Entities (AEs) by acting as DICOM Verification SCU and SCP

Query and retrieve images, SR, GSPS and KO from DICOM peer AEs by acting as DICOM Query/Retrieve SCU.

Receive images, GSPS, KO and SR from DICOM peer AEs by acting as SCP for various Image Storage SOP Classes, DICOM Grayscale Presentation State Storage SOP Class, and KO Selection Document Storage SOP Class.

Request storage commitment of image, KO, SR and GSPS Information Entities (IEs) to DICOM peer AEs by acting as DICOM Storage Commitment Push Model SCU.

Send query to a Modality Worklist by acting as SCU and then sends a Modality Performed Procedure Step (MPPS) message to a remote AE.

2.1.3 Sequencing of Real World Activities

Any retrieval of images by the IMPAX EE Mammography AE from a peer AE has preceded by – one or several – query requests to the peer AE, to get information about available images and values of study/series/image identifiers necessary for creating retrieve requests.Typically the receipt of images by the IMPAX EE Mammography AE from a peer AE is caused by an Image Retrieve Request to this peer AE by the IMPAX EE Mammography AE.The IMPAX EE Mammography AE creates derived images from source images.

Image IEs have to be received by the IMPAX EE Mammography AE, before they can be stored to or printed at peer AEs.



2.2 AE Specifications

2.2.1 IMPAX EE Mammography CLIENT Specification

2.2.1.1 SOP Classes Supported

IMPAX EE Mammography implements DICOM Verification Service, Query/Retrieve Services, Storage, Services for Image, Key Objects, SR Documents, Grayscale Presentation State IEs, the Storage Commitment Push Model SOP Class.

Table 2.2-1: SOP Class(es) for IMPAX EE Mammography CLIENT

SOP Class Name SOP Class UID SCU SCP

VerificationVerification SOP Class 1.2.840.10008.1.1 Yes Yes

TransferComputed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1 Yes YesDigital Mammography X-ray Image Storage For Presentation 1.2.840.10008.5.1.4.1.1.1.2 Yes YesSecondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Yes YesMulti-frame Grayscale Byte Secondary Capture ImageStorage

1.2.840.10008.5.1.4.1.1.7.2 Yes Yes

Multi-frame Grayscale Word Secondary Capture ImageStorage

1.2.840.10008.5.1.4.1.1.7.3 Yes Yes

Multi-frame True Color Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.4 Yes YesUltrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Yes YesUltrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 Yes YesGrayscale Softcopy PresentationState Storage SOP Class

1.2.840.10008.5.1.4.1.1.11.1 Yes Yes

Key Object Selection Document Storage 1.2.840.10008.5.1.4.1.1.88.59 Yes YesBasic Text SR Storage 1.2.840.10008.5.1.4.1.1.88.11 Yes YesEnhanced SR Storage 1.2.840.10008.5.1.4.1.1.88.22 Yes YesComprehensive SR Storage 1.2.840.10008.5.1.4.1.1.88.33 Yes Yes

Workflow ManagementModality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31 Yes NoModality Performed Procedure Step SOP Class 1.2.840.10008.3.1.2.3.3 Yes NoStorage Commitment Push Model SOP Class 1.2.840.10008.1.20.1 No Yes

Query RetrievePatient Root Query/Retrieve Information Model – FIND 1.2.840.10008.5.1.4.1.2.1.1 Yes NoPatient Root Query/Retrieve Information Model – MOVE 1.2.840.10008.5.1.4.1.2.1.2 Yes NoStudy Root Query/Retrieve Information Model – FIND 1.2.840.10008.5.1.4.1.2.2.1 Yes NoStudy Root Query/Retrieve Information Model – MOVE 1.2.840.10008.5.1.4.1.2.2.2 Yes No



2.2.1.2 Association Establishment Policies

2.2.1.2.1 GeneralThe DICOM standard application context name, which is always proposed, is listed in next Table 2.2-2.

Table 2.2-2: DICOM Application context

Application Context Name 1.2.840.10008.3.1.1.1

The maximum PDU length is 16384 bytes.SOP Class extended negotiation is supported.

2.2.1.2.2 Number of AssociationsTypically the IMPAX EE Mammography AE initiates only one DICOM Association concurrently, but potentiality the number of parallel associations is only limited by the resources of the underlying operating system.

Several DICOM Associations will be initiated concurrently, if the user launches a new Query/Retrieve, before an already performing Query/Retrieve operation was finished.

Several open DICOM Associations may also occur during Storage Commitment, if the Storage Commitment SCP peer AE sends the Commitment Result in a separate Association – initiated by the peer AE and accepted by the IMPAX EE Mammography AE.

2.2.1.2.3 Asynchronous NatureConfigurable via configurations file. At default, asynchronous mode is disabled.

2.2.1.2.4 Implementation Identifying Information

Table 2.2-3: DICOM implementation Class and Version for IMPAX EE Mammography CLIENT

Implementation Class UID 1.2.40.0.13.1.1

Implementation Version Name dcm4che-2.0



2.2.1.3 Association Initiation Policies

2.2.1.3.1 Verify Connection (SCU)

2.2.1.3.1.1 Description and Sequencing of ActivityThe user of the IMPAX EE Mammography Application initiates a Verification Request by selecting the corresponding button in the AE Configuration Panel on the user interface.

2.2.1.3.1.2 Proposed Presentation Contexts

Table 2.2-4: Presentation Contexts Proposed by IMPAX EE Mammography CLIENT

Presentation Context Table

Abstract Syntax Transfer Syntax

Name UID Name List UID ListRole Extended

Negotiation

Verification SOP Class

1.2.840.10008.1.1 Implicit VR, Little Endian

1.2.840.10008.1.2 SCU None

2.2.1.3.1.3 SOP Specific Conformance – VerificationIMPAX EE Mammography CLIENT provides standard conformance to the DICOM Verification SOP Class as SCU.

2.2.1.3.2 Query images, KO, GSPS and SR

2.2.1.3.2.1 Description and Sequencing of ActivityThe user of the IMPAX EE Mammography Application initiates the Query Request by selecting the corresponding button or expanding a node in the Patient/Study Folder on the user interface. Wild card or specific information can be specified for various Patient, Study, Series and/or Image attributes. If the user triggers a query in sequence level, than the user also triggered a retrieve and a receive for KO and GSPS (if existing).

The user of IMPAX EE Mammography Application initiates the Query Request by selecting an entry representing one Study in the Patient Folder



2.2.1.3.2.2 Proposed Presentation ContextsThe default behavior of IMPAX EE Mammography is to propose as SCU both Presentation Contexts.

Table 2.2-5: Proposed Presentation Contexts




Negotiation

Query/Retrieve Patient Root Info. Model –FIND

1.2.840.10008.5.1.4.1.2.1.1 Implicit VR, Little Endian

1.2.840.10008.1.2 SCU Yes

Query/Retrieve Study Root Info. Model – FIND


1.2.840.10008.1.2 SCU Yes

If both presentation contexts are accepted by the peer AE, IMPAX EE Mammography will use the Query/Retrieve Study Root Info. Model – FIND SOP class for query requests. The used query level depends on the selection or the type of node at the Patient/Study Folder on the user interface which was expanded:

Table 2.2-6: Expanded item for used query level

selected/expanded item corresponds used Query LevelNone PATIENT / STUDY (SOP specific)Patient STUDYStudy STUDYSeries SERIESImage IMAGE



Following keys are supported by the SCU of both SOP classes:

Table 2.2-7: Attributes for FIND

The types of matching are: “*” is Wild Card matching, “R” is Range matching, “L” is List of UID Matching and Sequence matching, “S” is Single value matching.

2.2.1.3.2.3 SOP Specific Conformance Statement for Q/R Study Root Information Model – FINDQueries initiated by the user without selection of any Patient/Study entry are performed with query level STUDY.

When querying SR objects, queries are initiated by the user selection of the Study entry (as indicated in Table 2.2-6 are performed with query level SERIES) and matching key Modality (0008,0060) = SR. If the Query Response contains entries for matching Series, a Retrieve for the SR Objects of this Series will be initiated.

Level Attributes Name Tag MatchingPatient Name (0010,0010) * Patient ID (0010,0020) S, * Issuer of Patient ID (0010,0021) SPatient’s Birth Date (0010,0030) R, S

Patient

Patient’s Sex (0010,0040) SStudy Date (0008,0020)Study Time (0008,0030)

R, S

Study Description (0008,1030) S, *Accession Number (0008,0050) S, *Study ID (0020,0010) S, *Study Instance UID (0020,000D) LModalities in Study (0008,0061) S

Study

Referring Physician’s Name (0008,0090) *Modality (0008,0060) SBody Part examined (0018,0015) S, *Requesting physician (0032,1032) *Requesting service (0032,1033) S, *Institution name (0008,0080) S, *Station Name (0008,1010) S, *Series Number (0020,0011) S, *Series Instance UID (0020,000E) LRequest Attribute Sequence (0040,0275) Sequence>Requested Procedure ID (0040,1001) S>Scheduled Procedure Step ID (0040,0009) SPerformed Procedure Step Start Date (0040,0244)Performed Procedure Step Start Time (0040,0245)

R, S

Series

Institutional Department Name (0008,1040) S, *Instance Number (0020,0013) S, * Content Date (0008,0023) R, SVerification Flag (0040,A493) S

Image

SOP Instance UID (0008,0018) L



2.2.1.3.2.4 SOP Specific Conformance Statement for Q/R Patient Root Information Model – FINDBy default, IMPAX EE Mammography Application uses Query/Retrieve Study Root Info. Model – FIND. In case that server does not support this SOP Class, IMPAX EE Mammography uses Query/Retrieve Patient Root Info. Model – FIND.

Queries initiated by the user without selection of any Patient/Study entry are performed with query level STUDY.

When querying SR objects, queries are initiated by the user selection of the Study entry (as indicated in Table 2.2-6 are performed with query level SERIES) and matching key Modality (0008,0060) = SR. If the Query Response contains entries for matching Series, a Retrieve for the SR Objects of this Series will be initiated.

2.2.1.3.3 Retrieve images, KO, GSPS and SR

2.2.1.3.3.1 Description and Sequencing of ActivityThe user of the IMPAX EE Mammography Application initiates the Retrieve Images, KO and GSPS Request by selecting the corresponding button in the Patient/Study Folder on the user interface, after selecting KO, studies/sequences with GSPS, single images, series or whole studies which shall be retrieved. The reception of images is reflected by a status change of the corresponding item in the Patient/Study Folder.

Retrieve SR will be triggered by a preceding Query SR, with non empty Response.

2.2.1.3.3.2 Proposed Presentation ContextsThe default behavior of IMPAX EE Mammography is to propose as SCU followingPresentation Context.





Negotiation

Query/Retrieve Study Root Info. Model – MOVE


1.2.840.10008.1.2 SCU None

If the presentation context is accepted by the peer AE, IMPAX EE Mammography will use the Query/Retrieve Study Root Info. Model – MOVE SOP class for retrieve requests. The used retrieve level depends on the selection at the Patient/Study Folder on the user:

Table 2.2-9: Selected item for used Retrieve Level

selected/expanded item corresponds used Query LevelNone PATIENT / STUDY (SOP specific)Patient STUDYStudy STUDYSeries SERIESImage IMAGE



2.2.1.3.4 Store images, GSPS, KO and SR

2.2.1.3.4.1 Description and Sequencing of ActivityThe user of the IMPAX EE Mammography Application selects single images, series or complete studies and the destination AE in the local Patient/Study Folder before initiating the Image Storage by selecting the corresponding button on the user interface. Importing images, GSPS, KO and SR from external source or archive is the only possible way for storing such objects.

At default, all Grayscale Presentation State Objects associated with selected images will be stored to the selected import destination. Also the selected Key Objects will be stored.

The storage of images is reflected by a status change of the corresponding item in the Patient/Study Folder.

If the destination AE also supports the Storage Commitment Push Model service - or a separate AE is associated with the destination AE to perform the Storage Commitment operation -, at default configuration, IMPAX EE Mammography sends a Storage Commitment request for the transmitted images and GSPS objects immediately after the storage operation was finished.

2.2.1.3.4.2 Proposed Presentation ContextsThe default behavior of IMPAX EE is to propose as SCU following Presentation Context:





Negotiation

All Storage SOP Classes listed in Table 2.2-1 Implicit VR, Little Endian

1.2.840.10008.1.2 SCU None

2.2.1.3.5 Storage Commitment (Request)

2.2.1.3.5.1 Description and Sequencing of ActivityAt default configuration, IMPAX EE Mammography sends a Storage Commitment request for the transmitted images and GSPS objects immediately after the storage operations was finished to the destination AE - or to an associated AE responsible for performing the Storage Commitment operation. The commitment result is reflected by a status change of the corresponding item in the Patient/Study Folder.


IMPAX EE Mammography will propose the single Presentation Context of next

Table 2.2-11.







Negotiation

Storage Commitment Push Model SOP Class

1.2.840.10008.1.20.1 Implicit VR, Little Endian

1.2.840.10008.1.2 SCU None

The following elements are sent as part of the N-ACTION request:

Table 2.2-12: Attributes for N-ACTION

Attribute TagTransaction UID (0008,1195)Referenced SOP Sequence (0008,1199)>Referenced SOP Class UID (0008,1150)>Referenced SOP Instance UID (0008,1155)

At default, IMPAX EE Mammography releases the association immediately after it receives the N-ACTION RSP to the initial Storage Commitment N-ACTION Request. That forces the peer AE, to send the N-EVENT-REPORT request containing the commitment result in a separate association, which has to be initiated – and released – by the peer AE.

The default behavior can be changed, that IMPAX EE Mammography keeps the initial association open until the corresponding N-EVENT-REPORT request was received and immediately confirmed by IMPAX EE Mammography – no matter if in the same or in a separate association.

If a complete success of the requested Storage Commitment is notified by the N-EVENT-REPORT, the status of the concerned image and presentation state objects changes to “committed”, which enables the user to delete these objects.

If existing failure of the requested Storage Commitment is notified by the N-EVENT-REPORT, the user will be asked, if the status of image and presentation state objects for which a successful commitment was reported, shall be changed to “committed”.

2.2.1.3.6 Query Modality Worklist

2.2.1.3.6.1 Description and Sequencing of ActivityThe user of IMPAX EE Mammography Application initiates a Query request to a modality worklist when selecting in the import dialog the option import via modality worklist. Wild card or specific information can be specified for the searched attributes.




Table 2.2-13: Presentation Context Proposed by IMPAX EE Mammography CLIENT




Negotiation

Modality Worklist Information Model –FIND

1.2.840.10008.5.1.4.31 Implicit VR, Little Endian

1.2.840.10008.1.2 SCU None

2.2.1.3.6.3 SOP Specific Conformance – Modality Worklist Information Model –FINDDICOM Message Service Element (DIMSE) Service C-FIND Attributes:

Table 2.2-14: Supported Attributes from Modality Worklist Information Model

Attribute TagAccession Number (0008,0050)Admission ID (0038,0010)Admitting Date (0038,0020)Admitting Diagnoses Description (0008,1080)Current Patient Location (0038,0300)Institution Name (0008,0080)Issuer of patient ID (0010,0021)Modality (0008,0060)Patient’s Birth Date (0010,0030)Patient’s Name (0010,0010)Patient’s Sex (0010,0040)Patient ID (0010,0020)Performing Physician’s Name (0008,1050)Referring Physician’s Name (0008,0090)Requested Contrast Agent (0032,1070)Requested Procedure Description (0032,1060)Requested Procedure ID (0040,1001)Requested Procedure Priority (0040,1003)Requesting Physician (0032,1032)Scheduled Procedure Step Start Date (0040,0002)Scheduled Procedure Step Description (0040,0007)Scheduled Procedure Step Status (0040,0020)Scheduled Station AE Title (0040,0001)Scheduled Procedure Step ID (0040,0009)



Attribute TagStation name (0008,1010)Study Instance UID (0020,000D)Visit Status ID (0038,0008)

2.2.1.3.7 Modality Performed Procedure Step (SCU)

2.2.1.3.7.1 Description and Sequencing of ActivityIMPAX EE Mammography sends a DICOM MPPS message to the server after importing via Modality worklist if this option is active in the configuration panel of the user interface.


Table 2.2-15: Presentation Context Proposed by IMPAX EE Mammography CLIENT




Negotiation

Modality Performed Procedure Step

1.2.840.10008.3.1.2.3.3 Implicit VR, Little Endian

1.2.840.10008.1.2 SCU None

2.2.1.3.7.3 SOP Specific Conformance – MPPSIMPAX EE Mammography supports the next DIMSE Service N-CREATE MPPS Attributes:

Table 2.2-16: Supported Attributes for MPPS N-CREATE

Attribute TagSpecific Character Set (0008,0005)SOP Class UID (0008,0016)SOP Instance UID (0008,0018)Modality (0008,0060)Procedure Code Sequence (0008,1032)>Code Value (0008,0100)>Coding Scheme Designator (0008,0102)>Code Meaning (0008,0104)Patient's Name (0010,0010)Patient ID (0010,0020)Issuer of Patient ID (0010,0021)Patient's Birth Date (0010,0030)Patient's Sex (0010,0040)Patient's Mother's Birth Name (0010,1060)Study ID (0020,0010)Admission ID (0038,0010)Performed Station AE Title (0040,0241)Performed Station Name (0040,0242)Performed Location (0040,0243)Performed Procedure Step Start Date (0040,0244)



Attribute TagPerformed Procedure Step Start Time (0040,0245)Performed Procedure Step End Date (0040,0250)Performed Procedure Step End Time (0040,0251)Performed Procedure Step Status (0040,0252)Performed Procedure Step ID (0040,0253)Performed Procedure Step Description (0040,0254)Performed Procedure Type Description (0040,0255)Performed Protocol Code Sequence (0040,0260)>Code Value (0008,0100)>Coding Scheme Designator (0008,0102)>Code Meaning (0008,0104)Scheduled Step Attributes Sequence (0040,0270)>Accession Number (0008,0050)>Referenced Study Sequence (0008,1110)>>Referenced SOP Class UID (0008,1150)>>Referenced SOP Instance UID (0008,1155)>Study Instance UID (0020,000D)>Requested Procedure Description (0032,1060)>Requested Procedure Code Sequence (0032,1064)>>Code Value (0008,0100)>>Coding Scheme Designator (0008,0102)>>Code Meaning (0008,0104)>Scheduled Procedure Step Description (0040,0007)>Scheduled Protocol Code Sequence (0040,0008)>>Code Value (0008,0100)>>Coding Scheme Designator (0008,0102)>>Code Meaning (0008,0104)>Scheduled Procedure Step ID (0040,0009)>Requested Procedure ID (0040,1001)Performed Procedure Step Discontinuation Reason Code Sequence

(0040,0281)

>Code Value (0008,0100)>Coding Scheme Designator (0008,0102)>Code Meaning (0008,0104)Performed Series Sequence (0040,0340)>Retrieve AE Title (0008,0054)>Series Description (0008,103E)>Performing Physician's Name (0008,1050)>Operator's Name (0008,1070)>Referenced Image Sequence (0008,1140)>>Referenced SOP Class UID (0008,1150)>>Referenced SOP Instance UID (0008,1155)>Protocol Name (0018,1030)>Series Instance UID (0020,000E)>Referenced Non-Image Composite SOP Instance Sequence

(0040,0220)

>>Referenced SOP Class UID (0008,1150)



Attribute Tag>>Referenced SOP Instance UID (0008,1155)

IMPAX EE Mammography supports the next DIMSE Service N-SET MPPS Attributes:

Table 2.2-17: Supported Attributes for MPPS N-SET

Attribute TagProcedure Code Sequence (0008,1032)>Code Value (0008,0100)>Coding Scheme Designator (0008,0102)>Code Meaning (0008,0104)Performed Procedure Step Start Date (0040,0244)Performed Procedure Step Start Time (0040,0245)Performed Procedure Step End Date (0040,0250)Performed Procedure Step End Time (0040,0251)Performed Procedure Step Status (0040,0252)Performed Procedure Step Description (0040,0254)Performed Procedure Type Description (0040,0255)Performed Procedure Step Discontinuation Reason Code Sequence

(0040,0281)

>Code Value (0008,0100)>Coding Scheme Designator (0008,0102)>Code Meaning (0008,0104)Performed Series Sequence (0040,0340)>Retrieve AE Title (0008,0054)>Series Description (0008,103E)>Performing Physician's Name (0008,1050)>Operator's Name (0008,1070)>Referenced Image Sequence (0008,1140)>>Referenced SOP Class UID (0008,1150)>>Referenced SOP Instance UID (0008,1155)>Protocol Name (0018,1030)>Series Instance UID (0020,000E)>Referenced Non-Image Composite SOP Instance Sequence

(0040,0220)

>>Referenced SOP Class UID (0008,1150)>>Referenced SOP Instance UID (0008,1155)



2.2.1.4 Association Acceptance PoliciesThe accepted calling and the called application entity titles – as the single TCP port number on which the application is listening for incoming association requests – can be configured in the AE configuration panel of the user interface. It accepts any association for which at least one presentation context is accepted.

2.2.1.4.1 Verify Connection

2.2.1.4.1.1 Description and Sequencing of ActivityIMPAX EE Mammography CLIENT responds to a Verification request from a DICOM SCU.

2.2.1.4.1.2 Accepted Presentation Contexts

Table 2.2-18: Acceptable Presentation Context for IMPAX EE Mammography CLIENT




Negotiation



1.2.840.10008.1.1 SCP None

2.2.1.4.2 Receive images, GSPS, KO and SRIMPAX EE Mammography CLIENT accepts an association when it receives an association request from a DICOM Storage SCU.

2.2.1.4.2.1 Description and Sequencing of ActivityThe receipt of an Image Storage Request is typically caused by a Retrieve Images Request issued by the IMPAX EE Mammography application entity to the remote system.

When IMPAX EE Mammography accepts an association, it will receive any image, GSPS,KO or SR transmitted on that association and store the image locally and register it in the local database. The IMPAX EE Mammography application entity informs the user of the receipt of new objects.

2.2.1.4.2.2 Accepted Presentation Contexts IMPAX EE Mammography accepts only presentation contexts for supported SOP classes containing the DICOM default transfer syntax:

Table 2.2-19: Acceptable Presentation Context for IMPAX EE Mammography CLIENT




Negotiation

All supported storage SOP classes listed in table 2.2-1

Implicit VR, Little Endian

1.2.840.10008.1.2 SCP no



2.2.1.4.2.3 SOP Specific Conformance Statement for Storage SOP classesIMPAX EE Mammography implements Level2 (Full) conformance for the Storage SOP Class. IMPAX EE Mammography will issue a failure status if it is unable to store a DICOM object on disk. If the database contains already an entry referencing an image with the equal SOP Instance UID as the new received image, the image will not be stored. IMPAX EE Mammography will issue also a storage success status in this case. The following error/warning status codes can be sent by IMPAX EE Mammography in the context of a C-STORE- RSP message:

Table 2.2-20: Response Status for Storage

Service Status

Further Meaning Error Code Reason

Refused Out of Resources A700 Out of ResourcesError Data Set does not

match SOP ClassA900 Data Set does not match SOP Class

Error Cannot understand C000Success 0000Warning Data Set does not

match SOP ClassB007 Data Set does not match SOP Class

2.2.1.4.3 Storage commitment (Report)

2.2.1.4.3.1 Description and Sequencing of Activity

A Storage Commitment Report is caused by a former Storage Commitment Request issuedby the IMPAX EE Mammography application entity to the remote system.

At default, IMPAX EE Mammography releases the association immediately after it receives the N-ACTION RSP to the initial Storage Commitment N-ACTION Request. That forces the peer AE, to send the N-EVENT-REPORT request containing the commitment result in a separate association, which has to be initiated – and released – by the peer AE.

The default behavior can be changed, that IMPAX EE Mammography keeps the initial association open until the corresponding N-EVENT-REPORT request was received and immediately confirmed by IMPAX EE Mammography – no matter if in the same or in a separate association.

2.2.1.4.3.2 Accepted Presentation Contexts

Table 2.2-21: Acceptable Presentation Contexts for IMPAX EE Mammography CLIENT




Negotiation



1.2.840.10008.1.1 SCP None

Storage Commitment Push Model SOP Class

1.2.840.10008.1.20.1 Implicit VR, Little Endian

1.2.840.10008.1.1 SCU None



2.2.1.4.3.3 SOP Specific Conformance Statement for Storage Commitment (Report)If a complete success of the requested Storage Commitment is notified by the N-EVENT-REPORT, the status of the concerned image and presentation state objects changes to “committed”, which enables the user to delete these objects.

If existing failures of the requested Storage Commitment is notified by the N-EVENT-REPORT, the user will be asked, if the status of image and presentation state objects for which a successful commitment was reported, shall be changed to “committed”.

2.3 Network InterfacesIMPAX EE Mammography provides DICOM V3.0 TCP/IP (Transmission Control Protocol / Internet Protocol) Network Communication Support as defined in PS 3.8 of the DICOM Standard. IMPAX EE Mammography inherits its TCP/IP stack from the computer system upon which it executes.

2.3.1 Physical Medium SupportIMPAX EE Mammography 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.4 Configuration

2.4.1 AE Title/ Presentation MappingThe mapping of application entity titles to presentation addresses is configurable from IMPAX EE Mammography’s user interface in the configuration database.

2.4.1.1 Local AE Titles

Table 2.4-1: AE Title Configuration Table

Application Entity Default AE Title Default TCP/IP PortIMPAX EE Mammography Client Hostname of computer 5515

The local AE Titles are configurable through web interface.

2.4.1.2 Remote AE Titles

2.4.2 Configuration Parameters

Table 2.4-1: Configuration Parameters Table

Parameter Configurable (Yes/No)

Default Value

General ParametersCalling AE Title Yes Hostname of computerPort YesRead Timeout YesDefault character Encoding No Latin 1Packet Size No 16384

Modality Performed Procedure Step Specific ParametersRemote host YesRemote port YesMPPS called AE Title Yes



3 MEDIA INTERCHANGE

3.1 Implementation Model

3.1.1 Application Data Flow Diagram

Figure 3-1: Application Data Flow Diagram

3.1.2 Functional Definition of IMPAX EE Mammography CLIENT AEThe selection of the option “Import CD/DVD” or “Import from CD” gives the possibility to import the selected patients and studies. These selected instances are transmitted to CLIENT AE.

The user has the possibility to select any patient DICOM object contained in the CD and visualize it when selecting the CD drive or the path of the DICOMDIR object of the media as search node.

LoadObjects from

CD Import

Objects fromCD

IMPAX EEMammography

CLIENT AE



3.1.3 Sequencing of Real World ActivitiesWhen importing from CD, IMPAX EE Mammography CLIENT searches the desired patient and study in the DICOM DIR. Then, an import is executed via C-Store.

3.1.4 File Meta Information for Implementation Class and Version

Table 3.1-1: File Meta Information for Implementation Class and Version

File Meta Information Version 00x01

Implementation Class UID 1.2.40.0.13.1.1

Implementation Version Name dcm4che-2.0

3.2 AE Specifications

3.2.1 IMPAX EE Mammography CLIENT AE Specification

Table 3.2-1: AE Related Application Profiles, Real World Activities and Roles

Supported Application Profile Real-World Activity Role SC OptionImport DICOM Objects to CD FSR,FSU InterchangeSTD-GEN-CDLoad DICOM Objects to CD FSR Interchange

3.2.1.1 File Meta Information for Implementation IMPAX EE MammographyCLIENTThere is no File Meta Information that pertains to Application Entity IMPAX EE Mammography CLIENT.

3.2.1.2 Real World Activities

3.2.1.2.1 Real World Activity – Import DICOM objects from CDIMPAX EE Mammography CLIENT AE works as FSR during the import from CD. It obtains the CD information data from the DICOMDIR structure and once selected the desired patient and study(s) it imports via DICOM C-Store. Optionally, it can act as FSU when user chooses the option to change some DICOM attributes of the imported data.

3.2.1.2.1.1 Media Storage Application ProfileIMPAX EE Mammography CLIENT AE supports STD-GEN-CD Application Profile. The SOP classes supported are listed in Table 1.1-1: Network Services Supported. The used Transfer Syntax is Explicit VR Little Endian with Transfer Syntax UID 1.2.840.10008.1.2.1.



3.2.1.2.1.1.1 Options

User of IMPAX EE Mammography has three options to import: Direct Import, Ad Hoc and Import via Modality Worklist. When user chooses Ad Hoc or Via Modality Worklist some DICOM attributes from the imported image are changed, then, IMPAX EE Mammography is working as FSU.

3.2.1.2.1.1.1.1 Direct Import:

All DICOM Attributes will remain as original data from CD.

3.2.1.2.1.1.1.2 Ad Hoc:

Some DICOM Attributes will be substituted by the User of IMPAX Mammography. Theseattributes are:

Table 3.2-2: Attributes modified by the user

Attribute Name TagPatient Name (0010,0010)Patient ID (0010,0020)Patient’s Birth Date (0010,0030)Patient’s Sex (0010,0040)Accession Number (0008,0050)

3.2.1.2.1.1.1.3 Import via Modality Worklist:

DICOM Attributes will be substituted by the obtained attributes from a modality worklist query. These attributes are listed in Table 2.2-14: Supported Attributes from Modality Worklist Information Model.

3.2.1.2.2 Real World Activity – Load DICOM objects from CDIMPAX EE Mammography CLIENT AE works as FSR when loading data from a CD. It obtains the CD information data from the DICOMDIR structure and the user can choose which information is loaded.

3.2.1.2.2.1 Media Storage Application ProfileIMPAX EE Mammography CLIENT AE supports STD-GEN-CD Application Profile. The SOP classes supported are listed in Table 1.1-1: Network Services Supported. The used Transfer Syntax is Explicit VR Little Endian with Transfer Syntax UID 1.2.840.10008.1.2.1.



4 SUPPORT FOR EXTENDED CHARACTER SETSIMPAX EE Mammography supports the following character sets:

Character Set Description Defined TermLatin alphabet No. 1 ISO-IR 100Thai ISO-IR 166Cyrillic ISO-IR 144Arabic ISO-IR 127Korean ISO-IR 149Greek ISO-IR 126Hebrew ISO-IR 138UTF-8 ISO-IR 192JIS X 0208 Japanese Kanji ISO-IR 87JIS X 0201 Japanese Katakana

ISO-IR 13

Chinese GB18030

Character Set Description Defined TermBasic G0 Set ISO-IR 6 ISO 8859-1 Latin Alphabet No. 1 ISO-IR 100 (default)Latin Alphabet No. 2 ISO-IR 101



5 SECURITY

5.1 Security ProfilesIMPAX EE Mammography supports secure DICOM communication in conformance with the Secure Profiles:

Basic TLS Secure Transport Connection Profile

User of IMPAX EE Mammography can activate the use of TLS security.

AES TLS Secure Transport Connection Profile

User of IMPAX EE Mammography can activate the use of AET TLS security complying with TLS_RSA_WITH_AES_128_CBC_SHA profile.

Basic User Identity Association Profile

IMPAX EE Mammography can be configured to use Basic User Identity Association Profile.

User Identity plus Pass code Association Profile

IMPAX EE Mammography can be configured to use User Identity plus Pass code Association Profile.

Basic Network Address Management Profile

IMPAX EE Mammography supports Basic Network Address Management Profile acting as DNS Client and DHCP Client

Basic Time Synchronization Profile

IMPAX EE Mammography supports Basic Time Synchronization Profile acting as NTP client.

5.2 Association Level SecurityIMPAX EE Mammography does not support any Association Level Security.

5.3 Application Level SecurityIMPAX EE Mammography application access requires a valid user and password in order to login.



6 ANNEXES

6.1 IOD Contents

6.1.1 Coerced/ Modified FieldsAs specified in Chapter 3.2 IMPAX EE Mammography acting as SCU can modify attributeswhen importing. These attributes are listed in Table 3.2-2: Attributes modified by the user.

6.2 Grayscale Image ConsistencyThe high resolution display monitor attached to the product can be calibrated according tothe Grayscale Standard Display Function (GSDF).

Details as of PDF Creation DateDocument Metadata

This document was approved by:

Signatures:

1. Bruno Laffin (nawyv) on 2011/05/16 04:42 PM CET 2. Peter Steiger (awpqz) on 2011/05/17 04:12 PM CET 3. Sabine Kolics (awppx) on 2011/05/17 07:35 PM CET 4. Sebastian Zambal (axdhg) on 2011/05/23 09:34 AM CET

Detailed Approver History:

Approval Workflow started on 2011/05/16 10:47 AM CET Approval task originally assigned to and completed by Peter Steiger (awpqz)

on 2011/05/17 04:12 PM CET Approval task originally assigned to and completed by Bruno Laffin (nawyv)

on 2011/05/16 04:42 PM CET Approval task originally assigned to and completed by Sebastian Zambal

(axdhg) on 2011/05/23 09:34 AM CET Approval task originally assigned to and completed by Sabine Kolics

(awppx) on 2011/05/17 07:35 PM CET

Version & Status History

Title: 001359_IMPAX EE Mammography DICOM Conformance Statement

Livelink ID: 32940311Version#: 3Version Date: 2011/05/16 10:43 AM CETStatus: Approved on 2011/05/23 10:01 AM CET Owner: Peter Buytaert (awabr)Created By: Peter Buytaert (awabr)Created Date: 2011/04/06 10:11 AM CETPDF Creation Date: 2011/05/23 10:03 AM CET

Version# Date Created Status3 2011/05/16 10:43 AM CET Approved - 2011/05/23

2 2011/04/11 03:05 PM CET Rejected - 2011/04/261 2011/04/06 10:11 AM CET

AGFA HEALTHCARE DICOM Conformance Statement · HE/001359 Page 1 of 33 Document No. 001359-Revision:...

Documents

Transcript of AGFA HEALTHCARE DICOM Conformance Statement · HE/001359 Page 1 of 33 Document No. 001359-Revision:...