Service Class User - Agfa HealthCare · DIGINET: For questions regarding the ... The user of this...

HE/JJ/OZ/RH/000457 Page 1 of 36 Document No. 000457, Revision 2.4

Agfa HealthCare This information is Company Confidential

AGFA HEALTHCARE DICOM Conformance Statement

Paxport V2.3.01 Service Class User

Status: Released

Document No. 000457, Revision 2.4

Jos Jennes Otto Zerdoner Ron Hitzelberger

a b


Agfa HealthCare This information is Company Confidential 1 October, 2002

Document Information

Author Jos Jennes Tel +32 (3) 444 6218 Email: [email protected]

Co-Author Otto Zerdoner

Ron Hitzelberger

Tel: +32 (0)3 444 8227 Email: [email protected] Tel: +1 864 943 1940 Email: [email protected]

Editing & Layout Carsten Weise Email: [email protected] Product Manager Hugo Van Boven Tel: +32 (0)3 444 73 19

Email: [email protected] Service-related issues North America

Agfa Customer Solutions Center USA

Tel: 1 (877) 777-AGFA http://www.agfamedical.com/support/support.asp

Service-related issues Outside North America

MI-CSO, Munich Tel: +49 89 6207 3020 Fax: +49 89 6207 7710 DIGINET: http://www.diginet-agfa.de

For questions regarding the technical content of this document, please contact:

Jos Jennes or Jos De Baerdemaeker

tel: +32 3 444 6321 tel: +32 3 444 6288

Issued by: Agfa Medical Imaging Septestraat 27 B-2640 Mortsel Belgium

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 by Agfa personnel. The information presented herein is sensitive and is classified Company Confidential. Without written authority from the proprietor, further distribution outside the company is not allowed.

tel: +32 3 444 8221 fax: +32 3 444 8211 email: [email protected]

Copyright October, 02 Agfa Medical Imaging

All rights reserved

a b

mailto:[email protected]




http://www.agfamedical.com/support/support.asp

http://www.diginet-agfa.de/


MED/PC/000457 Page 3 of 36 Document N0. 000457, Revision 2.3

Agfa HealthCare 1 October, 2002

Table of Contents

1 Introduction..............................................................................................6

1.1 Intended Audience.......................................................................................................... 6 1.1.1 Integration.................................................................................................................... 6 1.1.2 Validation ..................................................................................................................... 6 1.1.3 Future Evolution........................................................................................................... 6 1.2 Purpose of this Document .............................................................................................. 7 1.3 Sources for this Document ............................................................................................. 7

2 Implementation Model .............................................................................8

2.1 Application Data Flow Diagram ...................................................................................... 8 2.2 Functional Definitions of AE’s......................................................................................... 9 2.2.1 Verification SCU .......................................................................................................... 9 2.2.2 Storage SCU................................................................................................................ 9 2.2.3 Storage Commitment SCU.......................................................................................... 9 2.2.4 Print SCU..................................................................................................................... 9 2.2.5 MPPS SCU................................................................................................................ 10 2.2.6 Modality Worklist SCU............................................................................................... 10 2.3 Sequencing of Real World Activities............................................................................. 11 2.3.1 Verification ................................................................................................................. 11 2.3.2 Transmitting images .................................................................................................. 11 2.3.3 Storage Commitment................................................................................................. 11 2.3.4 Printing images.......................................................................................................... 11 2.3.5 MPPS Management .................................................................................................. 11 2.3.6 Modality Worklist Retrieve ......................................................................................... 11

3 AE Specifications...................................................................................12

3.1 Supported Services ...................................................................................................... 12 3.1.1 Association Establishment Policies ........................................................................... 13 3.1.1.1 General ................................................................................................................... 13 3.1.1.2 Number of Associations.......................................................................................... 13 3.1.1.3 Asynchronous Nature ............................................................................................. 13 3.1.1.4 Implementation Identifying Information .................................................................. 14 3.1.2 Association Initiation Policy ....................................................................................... 14 3.1.2.1 Proposed Presentation Contexts............................................................................ 14 3.1.2.2 Called/Calling AE-Titles.......................................................................................... 14 3.1.2.3 Association Initiation by Real World Activity........................................................... 14 3.1.2.3.1 Verification........................................................................................................... 14 3.1.2.3.2 Storage ................................................................................................................ 14 3.1.2.3.3 Storage Commitment........................................................................................... 15 3.1.2.3.4 Print 15 3.1.2.3.5 Modality Performed Procedure Step ................................................................... 15 3.1.2.3.6 Modality Worklist ................................................................................................. 15 3.1.3 SOP Specific Conformance....................................................................................... 15 3.1.3.1 SOP Specific Conformance –Verification SCU ...................................................... 15

a b



3.1.3.2 SOP Specific Conformance – Storage SCU .......................................................... 17 3.1.3.2.1 Supported attributes ............................................................................................ 17 3.1.3.2.2 Supported Return Codes..................................................................................... 19 3.1.3.3 SOP Specific Conformance – Storage Commitment SCU..................................... 19 3.1.3.3.1 Supported attributes ............................................................................................ 19 3.1.3.4 SOP Specific Conformance – Print Management SCU ......................................... 20 3.1.3.4.1 SOP Specific Conformance - Basic Grayscale Print Mgt Meta SOP Class ........ 20 3.1.3.4.1.1 Basic Film Session SOP Class (1.2.840.10008.5.1.1.1) 20 3.1.3.4.1.2 Basic Film Box SOP Class (1.2.840.10008.5.1.1.2) 21 3.1.3.4.1.3 Basic Grayscale Image Box SOP Class (1.2.840.10008.5.1.1.4) 24 3.1.3.4.1.4 Printer SOP Class (1.2.840.10008.5.1.1.16) 26 3.1.3.4.2 Presentation LUT SOP Class (1.2.840.10008.5.1.1.23) ..................................... 26 3.1.3.4.3 SOP Specific Conformance to Basic Color Print Management Meta SOP Class27 3.1.3.4.3.1 Basic Film Session SOP Class (1.2.840.10008.5.1.1.1) 27 3.1.3.4.3.2 Basic Film Box SOP Class (1.2.840.10008.5.1.1.2) 27 3.1.3.4.3.3 Basic Color Image Box SOP Class (1.2.840.10008.5.1.1.4.1) 27 3.1.3.4.3.4 Printer SOP Class (1.2.840.10008.5.1.1.16) 29 3.1.3.4.4 SOP Specific Conformance to Basic Annotation Box SOP Class....................... 29 3.1.3.5 SOP Specific Conformance – MPPS SCU............................................................. 29 3.1.3.5.1 Supported attributes ............................................................................................ 29 3.1.3.5.2 Supported Return Codes..................................................................................... 32 3.1.3.6 SOP Specific Conformance – Modality Worklist SCU............................................ 32 3.1.3.6.1 Query Key Types................................................................................................. 32 3.1.3.6.2 Query Keys Matching .......................................................................................... 33 3.1.3.6.3 Displayed Return Keys ........................................................................................ 34 3.1.4 Association Acceptance Policy.................................................................................. 34

4 Communication Profiles.........................................................................35

4.1 Supported Communications Stacks ............................................................................. 35 4.2 TCP/IP Stack ................................................................................................................ 35 4.3 Physical Medium Support............................................................................................. 35

5 Extensions / Specializations / Privatizations..........................................35

6 Configuration .........................................................................................35

6.1 Configurable Parameters.............................................................................................. 35

7 Support for Extended Character Sets....................................................35

8 Acronyms and Abbreviations.................................................................35

a b



Revision Record

Revision Number Date Author Reason for Change 1.00 03/08/98 Athooft Create the Conformance Claim for the “Paxport” 1.01 24/08/98 Athooft Minor modifications 1.02 31/08/98 Athooft Add Stored Print Component 1.03 17/11/98 Athooft MaxPduLen is 65542 bytes 1.04 24/11/98 Athooft Basic Film Session and Basic Film Box SOP Classes

Worklist Management SOP Class 1.05 01/02/99 Athooft Changed division name to "Agfa Medical Imaging" 1.06 20/05/99 Gdebeerst Removal of Print Job SOP Class

Update supported attributes for SOP Classes 1.07 20/10/99 JJennes Reviewed by Philips Medical Systems 1.0 3/02/00 Amorris Latest style implemented and incorporated into

mPower 1.1 23/02/00 Amorris Title and author updated 1.2 8/03/00 Amorris Released 16.2.00 2.0 5/09/00 Amorris Seminar comments to be incorporated 2.1 5/09/00 Amorris Seminar comments incorporated 2.2 7/09/00 Cweise New conventions implemented 2.3 26/06/00 R. Hitzelberger Initial revision for IHE (doc 000454) 2.4 11/03/02 JJennes Add IHE

a b



1 INTRODUCTION

1.1 Intended Audience 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 ADC imaging equipment, it is not sufficient to guarantee, by itself, the inter-operation of the connection. The following issues need to be considered:

1.1.1 Integration 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.

1.1.2 Validation Testing the complete range of possibilities between the Agfa equipment and non-Agfa devices, before the connection is declared operational, is deemed to be a necessity. The user should ensure that any non-Agfa provider accepts full responsibility for all validation required for their connection with the Agfa equipment. The accuracy of image data once it has crossed the interface between the Agfa equipment and the non-Agfa device as well as the stability of the image data for the intended applications is the responsibility of the non-Agfa provider.

1.1.3 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 future evolution of the DICOM standard. A refusal to do so may reflect in the loss of functionality and/or connectivity between the different products.

a b



1.2 Purpose of this Document This document is the DICOM Conformance Statement for the DICOM services of the Agfa PAXPORT as an Acquisition Modality. It is implemented in accordance with the IHE Technical Framework and its purpose is to specify compliance with the DICOM standard on the following PAXPORT supported service classes:

> Verification Service Class as an SCU.

> Secondary Capture Storage Management Service Class as an SCU.

> Storage Commitment Service Class Push Model as an SCU.

> Print Management Service Class as an SCU.

> Modality Perform Procedure Step Service as an SCU.

> Modality Worklist Service Class as an SCU.

1.3 Sources for this Document > ACR-NEMA Digital Imaging and Communications in Medicine (DICOM) V3.0. Current.

> IHE Technical Framework Year 2, Revision 4.0, March 28, 2000

a b



2 IMPLEMENTATION MODEL The Agfa PAXPORT is a point-to-point image acquisition device for image transmission, storage, and printing between non-DICOM (digital and video) modalities and the DICOM network.

2.1 Application Data Flow Diagram

External Image

Mgr/ArchiveSCP

Storage AE SCU

Local Applic. & Storage Activity

DICOM Standard Interface

Verification AE SCU

External Printer Device SCP

Storage Commit Mgt. AE SCU

External DICOM Device SCP

Print Mgt. AE SCU

MPPS Mgt. AE SCU

External DSS/OF Device SCP

MWL Mgt. AE SCU

External MPPS Mgr

Device SCP

Figure 2.1 Application data flow diagram.

a b



2.2 Functional Definitions of AE’s

2.2.1 Verification SCU PAXPORT/Verification is implemented as an application for testing DICOM devices. The DICOM C-Echo Service is used to test the presence of a DICOM application on an external DICOM device.

> Initiate a DICOM association to send the request

> Issue a C-ECHO request

> Wait for the response

> Close the Association

2.2.2 Storage SCU PAXPORT/C-Store SCU is implemented as an application entity for transmitting SC images. The DICOM Storage Service of SC images is used to send demographic information and pixel data to an external image manager/archive.

> Initiate a DICOM association to send the SC IOD

> Issue a C-STORE service

> Send the IOD with the pixel data processed as defined in the configuration of the external user

> Access the local database to update the patient demographic data


2.2.3 Storage Commitment SCU PAXPORT/Storage Commitment SCU is implemented to request a SCP to commit to the safekeeping of a set of SOP instances.

> Initiate a DICOM association for a Storage Commitment Push to the SCP

> Issue an N-ACTION request

> Accept N-ACTION response to determine if the SCP will commit to the storage of the SOP instances referenced

> Close the association

> The PaxPort listens to N-EVENT-REPORT

All printed and stored images remain in a ring-buffer or FIFO on the harddisk of the PaxPort, to enable reprints or re-stores at a later time. When this buffer is full, the first image needs to be removed permanently. This action will be delayed when its corresponding SOP instance UID was reported in the N-EVENT-REPORT with ‘failure’ status. These images will be retransmitted when the PaxPort is powered-up again.

2.2.4 Print SCU PAXPORT/Print SCU is implemented as an application entity for printing SC images. The Basic Grayscale Print Management and Basic Color Print SOP classes are used to send print jobs to a DICOM printer.

a b



> Initiate a DICOM association for a Basic Grayscale print job.

> Issue a N-GET request to get the printer information (when previously N_GET returned ‘failure’).

> Issue an N-CREATE of the Basic Film Session.

> Issue an N-CREATE of the Presentation LUT.

> Issue an N-CREATE of the Basic Film Box.

> Issue an N-SET for all the Basic Image Boxes.

> Issue an N-SET for all the Annotation Boxes (optionally)

> Issue a N-GET request to get the printer information (when previously N_GET returned no ‘failure’).

> Issue an N-ACTION of the Basic Film Box (or selectable of Basic Film Session).

> Issue an N-DELETE of the Basic Film Box (or selectable of Basic Film Session).

> Issue an N-DELETE of the Presentation LUT.

> Close the Association.

> The PaxPort Print Management will accept N-EVENT-REPORTs from the Print SCP, but will ignore them.

2.2.5 MPPS SCU PAXPORT/MPPS SCU is implemented as an application entity for MPPS management. The DICOM N-Create/N-Set Service of MPPS is used to send performed procedure step information to an MPPS manager.

> Initiate a DICOM association to send the MPPS IOD

> Issue an N-Create/N-Set request

> Send the IOD to the MPPS Manager

> Access the local database to update the performed procedure step data


2.2.6 Modality Worklist SCU PAXPORT/Modality Worklist SCU is implemented as an application entity for retrieving the modality worklist from the Department System Scheduler/Order Filler. The DICOM C-Find Service of MWL is used to request the scheduled procedure steps.

a b



> Initiate a DICOM association to request the Modality Worklist

> Issue a C-FIND request with the requested attributes IOD

> Send the IOD to the Department System Scheduler/Order Filler

> Access the local database to add or update the scheduled objects


2.3 Sequencing of Real World Activities

2.3.1 Verification The verification is a manually activated via a browser or via the user keypad.

2.3.2 Transmitting images Images are acquired via a user keypad or via a Remote Control link and will be transmitted by configuring the storage device with a browser.

2.3.3 Storage Commitment The Storage Commit N-ACTION will automatically be initiated after all the images of a Scheduled Procedure Step have been successfully transmitted to the Archive.

2.3.4 Printing images Images are acquired via a user keypad or via a Remote Control link and printed by configuring for the desired format and destination with a browser.

2.3.5 MPPS Management The MPPS N-CREATE is initiated at the moment the first image capture of images is started. The MPPS N-SET is initiated after all the images are transmitted – successfully or not.

2.3.6 Modality Worklist Retrieve The MWL retrieve can be initiated on a regular time base as defined in the PAXPORT Task Browser : Broad Query.

a b



3 AE SPECIFICATIONS

3.1 Supported Services PAXPORT provides Standard Conformance to the DICOM V3.0 SOP Classes as an SCU listed in the tables below:

SOP Class SOP Class UID Verification 1.2.840.10008.1.1 Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9 Basic Color Print Management Meta SOP Class 1.2.840.10008.5.1.1.18 Basic Annotation Box SOP Class 1.2.840.10008.5.1.1.15

Table 1 Print Management SOP classes

Support for Basic Grayscale Print Management as SCU also implies support for the SOP Classes as SCU listed in Table 2 below:

SOP Class SOP Class UID Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4 Printer SOP Class 1.2.840.10008.5.1.1.16 Presentation LUT SOP Class 1.2.840.10008.5.1.1.23

Table 2 Supported Basic Grayscale Print Management SOP Classes

Support for Basic Color Print Management as SCU also implies support for the SOP Classes as SCU listed in Table 3 below:

SOP Class SOP Class UID Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Basic Color Image Box SOP Class 1.2.840.10008.5.1.1.4.1 Printer SOP Class 1.2.840.10008.5.1.1.16

Table 3 Supported Basic Color Print Management SOP Classes

Support for Secondary Capture Image Storage as SCU is listed in Table 4 below:

SOP Class SOP Class UID Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Storage Commitment Push Model 1.2.840.10008.1.20.1

Table 4 Supported Secondary Capture Image Storage SOP Classes

a b



Support for Modality Performed Procedure Step as SCU is listed in Table 5 belo:

SOP Class SOP Class UID Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3

Table 5 Modality Performed Procedure Step SOP Class

Support for Modality Worklist Information Management as SCU is listed in Table 6 below:

SOP Class SOP Class UID Modality Worklist Information Model – Find 1.2.840.10008.5.1.4.31

Table 6 Modality Worklist Information Management SOP class as SCU

3.1.1 Association Establishment Policies

3.1.1.1 General > Before any SOP Classes can be exchanged between the PaxPort (SCU) and the SCP AE, an

association stage takes place to negociate the capabilities of the SCU and SCP

> The maximum PDU length for an association initiated by the PAXPORT is 65542 bytes

> Only PAXPORT shall release an Association. PAXPORT or the SCP AE may abort the Association

3.1.1.2 Number of Associations The Paxport opens one association for querying worklist items, but can open different associations for printing and/or archiving to multiple destinations simultaneously. There is no inherent limit to the number of associations other than limits imposed by the computer operating system.

3.1.1.3 Asynchronous Nature PAXPORT allows a single outstanding operation on any association. The PAXPORT will wait for a response from the SCP AE before attempting another operation during the same association.

However, the PAXPORT Worklist Management Component may cancel the C-FIND service by issuing a C-CANCEL-FIND request any time during the processing of the C-FIND service by the SCP.

a b



3.1.1.4 Implementation Identifying Information The PAXPORT SCU will respond with the following implementation identifying parameters:

> Implementation Class UID: 1.3.51.0.1.3

> Implementation Version Name: AGFAPAXPORT 1.0

> Application Context Name : 1.2.840.10008.3.1.1.1

> All associations will use a single implementation Class UID.

3.1.2 Association Initiation Policy PAXPORT attempts to initiate a new association for every service.

3.1.2.1 Proposed Presentation Contexts PAXPORT proposes the presentation context listed in Table 7 below:

SOP Class Transfer Syntax

SOP Class SOP Class UID Name UID

Role Extended Negotiation

See Tables 1-6 See Tables 1-6 DICOM Implicit VR Little Endian

1.2.840.10008.1.2 SCU None

Table 7 Transfer Syntax

Note : Presentation Context shall use Abstract Syntax IDs which correspond to the SOP Classes UID of the Meta SOP Class specified in the first column of the Transfer Syntax Table or included SOP Classes. None of the included SOP Classes supports extended negociation.

3.1.2.2 Called/Calling AE-Titles The default calling AE title is ‘PAXPORT’. This can be modified during configuration via a browser. The calling AE title is always in uppercase.

The called AE title that PAXPORT will use can be configurable after application startup, via a browser.

3.1.2.3 Association Initiation by Real World Activity

3.1.2.3.1 Verification The PAXPORT Verification AE initiates a new association for each request.

3.1.2.3.2 Storage The PAXPORT SC Image Storage AE initiates a new association for each set of images it needs to transfer.

a b



If the SCP AE rejects the Association, then the PAXPORT issues a warning message. In case of a time-out (e.g. no answer from the SCP AE) or a warning message the request will be retried after at least 20 seconds. In the mean time requests to other destinations will be handled.

3.1.2.3.3 Storage Commitment The PAXPORT Storage Commitment AE initiates a new association after the successful transmission of all the images belonging to a Performed Procedure Step.

3.1.2.3.4 Print The PAXPORT Print Management Component (SCU) will initiate a separate Association for each Print Session.

If the SCP AE rejects the Association, then the PAXPORT issues a warning message. In case of a time-out (e.g. no answer from the SCP AE) or a warning message the request will be retried after at least 20 seconds. In the mean time requests to other destinations will be handled.

After an association is established, the PAXPORT Print Management Component will send print jobs to the DICOM Print Server.

The Paxport Print Management Component will accept N-EVENT-REPORTs from the Print SCP but will ignore them.

3.1.2.3.5 Modality Performed Procedure Step The PAXPORT Performed Procedure Step AE initiates a new association due to Initiation of the N-SET after the approval by the operator of the Performed Procedure Step.

3.1.2.3.6 Modality Worklist The PAXPORT Worklist Management Component (SCU) will initiate a separate Association for each Worklist of items to be obtained. The frequency of these queries can be configured (in minutes).

If the SCP AE rejects the Association, then the PAXPORT issues a warning message. In case of a time-out (e.g. no answer from the SCP AE) or a warning message the request will be retried during the next query cycle. In the mean time requests to other destinations will be handled.

3.1.3 SOP Specific Conformance

3.1.3.1 SOP Specific Conformance –Verification SCU The PAXPORT Print Management Component provides standard conformance to the DICOM Verification Service Class (1.2.840.10008.1.1) as SCU.

C-ECHO: The Verification Service Class defines a service that verifies the application level communication between DICOM Application Entities. The verification is accomplished on an established Association using C-ECHO.

The PAXPORT Print Management Component (SCU) will process the C-ECHO confirmation and response Status codes. The status codes listed below in Table 8 are recognized :

Code Status Meaning 0000H Success Normally returned by the SCP AE.

a b



Code Status Meaning Error If the SCP AE returns any other error or warning status the PAXPORT Print

Management Component will abort the association.

Table 8 C-Echo SCU Status Codes

a b



3.1.3.2 SOP Specific Conformance – Storage SCU

3.1.3.2.1 Supported attributes PAXPORT supports the standard DICOM elements for SC Image Storage SOP Class as an SCU as listed in Table 9 below:

Module Attribute Name Group,Tag Default Value Patient Patient’s name 0010,0010 2 Patient ID 0010,0020 2 Patient’s birth date 0010,0030 2 Patient’s sex 0010,0040 2 General Study Study instance UID 0020,000D 1 Study date 0008,0020 2 Study time 0008,0030 2 Referring physician’s name 0008,0090 2 Study ID 0020,0010 2 Accession number 0008,0050 2 Reading study physician 0008,1060 3 Study description 0008,1030 3 Referenced Study Sequence 0008,1110 IHE Patient Study Not supported General Series Modality 0008,0060 1 Series description 0008,103E 3 Series instance UID 0020,000E 1 Series number 0020,0011 2 Performing Physician’s Name 0008,1050 3 Note 6 Laterality 0020,0060 2c Protocol Name 0018,1030 IHE Performed Procedure Step ID 0040,0253 IHE Performed Procedure Step Start Date 0040,0244 IHE Performed Procedure Step Start Time 0040,0245 IHE Performed Procedure Description 0040,0254 IHE Referenced Study Component Sequence 0008,1111 IHE Requested Attribute Sequence 0040,0275 IHE Performed Protocol Code Sequence 0040,0260 IHE General Equipment Manufacturer 0008,0070 2 Note 1 Manufacturer ModelName 0008,1090 3 Note 1 Station name 0008,1010 3 Note 2 Institution name 0008,0080 3 Institution address 0008,0081 3 Institution department name 0008,1040 3 SC Equipment Conversion Type 0008,0064 1

“DV” - Note 1

Secondary Capture Device ID 0018,1010 3 “4416” - Note 1 Secondary Capture Device Manufacturer 0018,1016 3 “AGFA” - Note 1 Secondary Capture Device Manufacturer’s Model

Name 0018,1018 3 “PAXPORT” -Note

1

a b



Module Attribute Name Group,Tag Default Value Secondary Capture Device Software Version 0018,1019 3 PAXx.x.xx - Note 2 General Image Instance number 0020,0013 2 1 Patient orientation 0020,0020 2c Content Date 0008,0022 2c Note 6 Content Time 0008,0032 2c Note 6 Image Pixel Samples per pixel 0028,0002 1 1 Photometric interpretation 0028,0004 1 PALETTE not

supported

Planar Configuration 0028,0006 1c Note 3 Rows 0028,0010 1 Columns 0028,0011 1 Pixel Aspect Ratio 0028,0034 1c Note 4 Bits allocated 0028,0100 1 Bits stored 0028,0101 1 High bit 0028,0102 1 Pixel representation 0028,0103 1 Pixel data 7FE0,0010 1 SC Image Secondary Capture Date 0018,1012 3 Secondary Capture Time 0018,1014 3 Overlay Plane Not Supported Modality LUT Rescale intercept 0028,1052 1 “0.0” Rescale slope 0028,1053 1c “1.0” Rescale type 0028,1054 1c “US” VOI LUT Window center 0028,1050 3 Note 5 Window width 0028,1051 1c Note 5 SOP Common SOP Class UID 0008,0016 1.2.840.10008.5.1.4.1.1.7

Image Instance UID (Unique identifier) 0008,0018 Specific character set 0008,0005 1c ISO_IR 100 Instance creation date 0008,0012 3 Instance creation time 0008,0013 3

Table 9 C-Store SCU Standard DICOM Attributes

Notes: 1. The value filled-in is the default value. This can be modified via a browser.

2. PAXx.x.xx is the actual software version in the PAXPORT and is not re-editable.

3. Planar Configuration (0028,0006) is required if Samples per Pixel (0028,0002) has a value greater than 1.

4. Pixel Aspect Ratio (0028,0034) is required if the aspect ratio is not 10000/10000

5. If Window Width/Center is different from default, it will be pre-processed on the image before it will be sent. So these values will always be default.

6. These attributes (indicated in gray) will be available in next PaxPort releases.

a b



3.1.3.2.2 Supported Return Codes PAXPORT supports the standard DICOM return codes for this SOP Class as an SCU as listed in Table 10 below: Code Status Meaning

0000H Success Normally returned by the SCP AE: the image was stored successfully on the SCP system. The PAXPORT SC Image Storage Component will send a C-STORE for the next study.

A7xxH Error Refused: SCP was out of resources. Status message will be logged by the PAXPORT SC Image Storage Component. The PAXPORT SC Image Storage Component will retry a C-STORE command for this study, until success or a status different from A7xxH is returned.

A9xxH Error Data Set does not match SOP Class (indicates that the Data Set does not encode an instance of the SOP Class specified according to the SCP). Status message will be logged by the PAXPORT SC Image Storage Component. The PAXPORT SC Image Storage Component will stop sending C-STORE commands for this study.

CxxxH Error Can not understand (indicates that the Data Set could not be parsed into elements by the SCP). Status message will be logged by the PAXPORT SC Image Storage Component. The PAXPORT SC Image Storage Component will stop sending C-STORE commands for this study.

B000H Warning Coercion of Data Elements. Status message will be logged by the PAXPORT SC Image Storage Component. The PAXPORT SC Image Storage Component will send a C-STORE command for the next study.

B007H Warning Data Set does not match SOP Class Status message will be logged by the PAXPORT SC Image Storage Component. The PAXPORT SC Image Storage Component will send a C-STORE command for the next study.

B006H Warning Elements discarded Status message will be logged by the PAXPORT SC Image Storage Component. The PAXPORT SC Image Storage Component will send a C-STORE command for the next study.

Table 10 C-STORE SCU Status Codes

3.1.3.3 SOP Specific Conformance – Storage Commitment SCU

3.1.3.3.1 Supported attributes PAXPORT supports the standard DICOM elements for this SOP Class as an SCU (N-ACTION) as listed in Table 11 below:

Action Type Name/ID Attribute Name Group,Tag Remarks Request Storage Commitment /1 Transaction UID 0008,1195 Retrieve AE-Title 0008,0054 Referenced SOP Sequence 0008,1199 >Referenced SOP Class UID 0008,1150 >Referenced SOP Instance UID 0008,1155 Referenced Study Component

Sequence 0008,1111

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

Table 11 Storage Commitment SCU N-ACTION Standard DICOM Attributes

a b



PAXPORT supports the standard DICOM elements for this SOP Class as an SCU (N-EVENT-REPORT) as listed in Table 12 below:

Action Type Name/ID Attribute Name Group,Tag Remarks Storage Commitment Request Successful /1

Transaction UID 0008,1195

Retrieve AE-Title 0008,0054 Referenced SOP Sequence 0008,1199 >Referenced SOP Class UID 0008,1150 >Referenced SOP Instance UID 0008,1155 Storage Commitment Request Complete – Failure exists /2

Transaction UID 0008,1195

Referenced SOP Sequence 0008,1199 >Referenced SOP Class UID 0008,1150 >Referenced SOP Instance UID 0008,1155 Failed SOP Sequence 0008,1198 >Referenced SOP Class UID 0008,1150 >Referenced SOP Instance UID 0008,1155

Table 12 Storage Commitment SCU N-EVENT-REPORT Standard DICOM Attributes

3.1.3.4 SOP Specific Conformance – Print Management SCU

3.1.3.4.1 SOP Specific Conformance - Basic Grayscale Print Mgt Meta SOP Class The PAXPORT Print Management Component provides Standard conformance to the DICOM Basic Grayscale Print Management Class (1.2.840.10008.1.1.9) as SCU.

Support for Basic Grayscale Print Management as SCU also implies support for the following SOP Classes as SCU.

3.1.3.4.1.1 Basic Film Session SOP Class (1.2.840.10008.5.1.1.1) The PAXPORT Print Management Component (SCU) can send the following DIMSE services:

> N-CREATE

> N-ACTION

N-CREATE is issued by the PAXPORT Print Management Component (SCU) to create a Basic Film Session SOP instance, when an Association has been established. The N-CREATE causes the Basic Film Session (root element) to be created by the SCP AE and its attributes initialized. The following attributes in Table 13 below are supported:

Attribute Name Tag Value

Number of Copies (2000,0010) Default 1 Print priority (2000,0020) Default LOW, HIGH in case of emergency Medium Type (2000,0030) CLEAR FILM, BLUE FILM, PAPER, empty string Film destination (2000,0040) Fixed PROCESSOR Film Session Label (2000,0050) See Note 1

Table 13 Supported N-CREATE Attributes for a Basic Film Session

a b



Note: Film Session Label (2000,0050) contains the Patient Name or the calling AE title in case of absence of Patient Name.

The PAXPORT Print Management Component (SCU) will process the N-CREATE confirmation and response Status codes. The following status codes in Table 14 are recognized:

Code Status Meaning

0000H Success Normally returned by the SCP AE. 0116H Warning The SCP AE returns attribute ”Value Out of Range” if the value of an attribute is out of range.

The PAXPORT Print Management Component will continue when its destination is an AGFA printers, but stops (ABORT) when its destination is an non-AGFA printer (might lead to unacceptable image quality).

0107H Warning The SCP AE returns attribute ”Attribute list error” . Then the PAXPORT Print Management Component will continue. A warning message will be printed in the logfile.

0213H Error Resource Limitation is returned by the SCP AE for the Basic Film Session SOP Class to indicate that the requested allocation can temporarily not be provided. The PAXPORT Print Management Component will retry the current print Job.

Error If the SCP AE returns any other error or warning status the PAXPORT Print Management Component will abort the association.

Table 14 N-CREATE Status Codes

N-ACTION is issued by the PAXPORT Print Management Component (SCU) to print a Film Session. This means that all subordinate Basic Film Boxes will be assembled into a print job for printing. (The job can therefore contain more than one film.)

The PAXPORT Print Management Component (SCU) will process the N-ACTION confirmation and response Status codes. The following status codes in Table 15 below are recognized:

Code Status Meaning

0000H Success Normally returned by the SCP AE. Error If the SCP AE returns any other error or warning status the PAXPORT Print Management

Component will abort the association.

Table 15 N-ACTION Status Codes

3.1.3.4.1.2 Basic Film Box SOP Class (1.2.840.10008.5.1.1.2) The PAXPORT Print Management Component (SCU) can send the following DIMSE services:

> N-CREATE

> N-ACTION

> N-DELETE

a b



N-CREATE is issued by the PAXPORT Print Management Component (SCU) to create a Basic Film Box under the created Film Session and initialize its attributes. (The creation of a Basic Film Box also causes the subordinate Basic Image Boxes to be created for each location in the film format.) The Basic Film Box contains the presentation parameters common for all images on a given sheet of film.

The Film Box N-Create attributes are listed below in Table 16:


Image Display Format (2010,0010) STANDARD, ROW, COL, SLIDE, SUPERSLIDE Annotation Display Format ID (2010,0030) See Note 1 Film Orientation (2010,0040) PORTRAIT,LANDSCAPE Film Size ID (2010,0050) 8INX10IN, 10INX12IN, 10INX14IN, 11INX14IN, 14INX14IN,

14INX17IN, A4, A3, 24CMX24CM, 24CMX30CM, empty string (see Note 2)

Border Density (2010,0100) BLACK or ODx100 (configurable) Empty Image Density (2010,0110) BLACK or ODx100 (configurable) Min Density (2010,0120) Configurable Max Density (2010,0130) Configurable Trim (2010,0140) NO, YES (configurable) Configuration Information (2010,0150) PERCEPTION_LUT, CS_TABLE (see Note 3) Illumination (2010,015E) 2000 for Transmissive Film, 150 for Reflective Film (these are

default values – configurable) Reflective Ambient Light (2010,0160) 10 (this is a default value – configurable) Referenced Film Session Sequence

(2010,0500)

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

Table 16 Supported N-CREATE Attributes for a Basic Film Box

Note 1. In case of Agfa printer, Annotation Display Format ID (2010,0030) is supported when the Annotation

SOP Class is accepted during Association set-up (cfr. SOP specific Conformance to Basic Annotation Box SOP Class). In case of non-Agfa printers, Annotation Display Format ID (2010,0030) can be editted via the browser.

2. It is possible to select an undefined Film Size ID. In that case AGFA printers will take whatever Film Size that is available in the tray.

3. In case of Agfa printer, Configuration Information (2010,0150) is used to define the Perception LUT and the Color Separation Table. The individual parameters defined are separated by the "\" (BACKSLASH) character. In case of non-Agfa printers, this field can be filled-in via the system configurator.

> Perception LUT Supported values: PERCEPTION_LUT=LINEAR Linear Perception LUT PERCEPTION_LUT=KANAMORI Kanamori Perception LUT PERCEPTION_LUT=n LUT defined by value 'n', n is of VR type IS. PERCEPTION_LUT=OEMxxx EOM LUT table no xxx is used, which is available in the

printer.

When "PERCEPTION_LUT=n" is used, 'n' is defined in the range 75 to 220 as follows:

a b



n Meaning 100 Exact Kanamori Curve (same as "PERCEPTION_LUT=KANAMORI") 200 Exact Linear Curve (same as "PERCEPTION_LUT=LINEAR") 100..200 Curve between Kanamori and Linear < 100 Hyper-Kanamori Curve > 200 Hypo-Linear Curve

The Perception LUT is not used for color images or when PLUT Values are sent. > Color Separation table

Supported values: CS_TABLE = n n is defined in the range 0..18.

Color Separation is used to choose the Color Separation Table in the Drystar, Agfa’s Thermal Sublimation Printer. The Color Separation Table (CS_TABLE) is only used for color images. Minimum Density Value, Maximum Density Value and Perception LUT are ignored for color images.

The PAXPORT Print Management Component (SCU) will process the N-CREATE confirmation and response Status codes. The status codes below in Table 17 are recognized: Code Status Meaning

0000H Success Normally returned by the SCP AE. 0116H Warning The SCP AE returns attribute Value Out of Range if an attribute value is out of range.




Table 17 N-CREATE Status Codes

N-ACTION is issued by the PAXPORT Print Management Component (SCU) to print the hierarchy from the Basic Film Box level. This means that the Basic Film Box will be assembled into a print job for printing. The print job will therefore contain one or more copies of a single film of the Film Session, when all desired Image Boxes in the Basic Film Box have been set.

The PAXPORT Print Management Component (SCU) will process the N-ACTION confirmation and response Status codes. The status codes listed below in Table 18 are recognized: Code Status Meaning

0000H Success Normally returned by the SCP AE. Error If the SCP AE returns any other error or warning status the PAXPORT Print Management

Component will abort the association.

Table 18 N-ACTION Status Codes

a b



3.1.3.4.1.3 Basic Grayscale Image Box SOP Class (1.2.840.10008.5.1.1.4) The Basic Grayscale Image Box SOP instance is created by the SCP AE at the time the Basic Film Box SOP instance is created (N-CREATE). The Basic Grayscale Image Box contains the presentation parameters and image pixel data that applies to a single image of a sheet of film.

The PAXPORT Print Management Component (SCU) can send the following DIMSE services:

> N-SET

N-SET is issued by the PAXPORT Print Management Component (SCU) to change some of the Basic Grayscale Image Box attribute values. In Basic Print Management, N-SET is also used to define the Image Module (this contains image related attributes and the actual image pixel data). If no pixel data is supplied with the N-SET, the current Image Module should be deleted from the hierarchy.

When all needed Basic Grayscale Image Boxes have been set, the PAXPORT Print Management Component (SCU) issues a print command. There can be empty image positions. By using N-SET the PAXPORT Print Management Component (SCU) can instruct the SCP to erase the image in the image position by setting a zero length and no value in the attribute Basic Grayscale Image Sequence. The N-Set attributes for the Basic Grayscale Image Box are listed in Table 19 below:


Image Position (2020,0010) 1 - x (depending layout) Polarity (2020,0020) NORMAL, REVERSE Magnification Type (2010,0060) REPLICATE, BILINEAR, CUBIC, empty string (see Note 2) Smoothing Type (2010,0080) In case of CUBIC (see Note 3) Basic Grayscale Image Sequence (2020,0110) >Samples Per Pixel (0028,0002) 1 >Photometric Interpretation (0028,0004) MONOCHROME2 / MONOCHROME1 >Rows (0028,0010) larger than 0 >Columns (0028,0011) larger than 0 >Pixel Aspect Ratio (0028,0034) 10000\10000 (default – see note 1) >Bits Allocated (0028,0100) 8 >Bits Stored (0028,0101) 8 >High Bit (0028,0102) 7 >Pixel Representation (0028,0103) 0 >Pixel Data (7FE0,0010)

Table 19 Supported N-SET Attributes for a Basic Grayscale Image Box

Note: 1. Pixel Aspect Ratio is only sent when its value differs from the standard valu : 10000\10000.

2. It is possible to select an undefined Magnification Type. In that case AGFA printers will take Magnification Type that is configured in the printers (configurable per AE title). “empty string” can only be used for AGFA printers.

3. Smoothing Type (2010,0080) is used if Magnification Type is "CUBIC". The following values defined for the Smoothing Type have a special meaning:

"0" - Unsharp smoothing

"140" - Sharp (Hi-resolution) smoothing

a b



Besides the above-specified standard attributes the ‘Basic Grayscale Image Sequence’ is also extended with the DICOM attributes listed in Table 20 below:


>Window Center (0028,1050) See Note >Window Width (0028,1051) See Note >Rescale Intercept (0028,1052) 0.0 >Rescale Slope (0028,1053) 1.0 >Rescale Type (0028,1054) US

Table 20 Extended Standard Attributes for a Basic Grayscale Image Box

Window Center (0028,1050) and Window Width (0028,1051) are not sent. When one or more of following parameters differ from the default, the image will be transformed on the Paxport before transferring it to the printer. This counts for following parameters:

> Window Center and Window Width result in a different from the complete data range.

> Image needs to be rotated and/or flipped

> Image cropping is needed

The PAXPORT Print Management Component (SCU) will process the N-SET confirmation and response Status codes. The status codes listed below in Table 21 are recognized:

Code Status Meaning




C605H Error Returned by the SCP AE if there is insufficient memory in the printer to store images. The PAXPORT Print Management Component will retry the current Print Job.

Error If the SCP AE returns any other error or warning status this PAXPORT Print Management Component will abort the association.

Table 21 N-SET Status Codes

a b



3.1.3.4.1.4 Printer SOP Class (1.2.840.10008.5.1.1.16) The Printer SOP Class is used to monitor the status of the printer.

The PAXPORT Print Management Component (SCU) will accept the following DIMSE services:

> N-EVENT-REPORT


> N-GET

N-EVENT-REPORT: at any time during the Association, the PAXPORT Print Management Component (SCU) is able to accept the N-EVENT-REPORT from the SCP AE, but will not use it in the application software.

N-GET is issued by the PAXPORT Print Management Component (SCU) to retrieve an instance of the Printer SOP class. The supported N-Get attributes are listed in Table 22:

Attribute Name Tag Value Printer Status (2110,0010) NORMAL, WARNING, FAILURE Printer Status Info (2110,0020) Printer Name (2110,0030) Manufacturer (0008,0070) Manufacturer Model Name (0008,1090) Device Serial Number (0018,1000) Software Versions (0018,1020) Date Last Calibration (0018,1200) Last Calibration (0018,1201)

Table 22 Supported Attributes for N-GET on a Printer

3.1.3.4.2 Presentation LUT SOP Class (1.2.840.10008.5.1.1.23) N-CREATE is issued by the PAXPORT Print Management Component (SCU) to create a Presentation LUT SOP Instance. The supported Presentation LUT attributes are listed below in Table 23:

Tag Name Supported Default

(2050,0010) Presentation LUT Seq. (0028,3002) >LUT Descriptor LUT Entry count

LUT First Pixel Value Mapped LUT Bits Count

256 (8bit/pixel) (fixed) 0 (fixed) 15 (fixed)

(0028,3003) >LUT Explanation (0028,3006) >LUT Data (2050,0020) Presentation LUT Shape IDENTITY (Note)

Table 23 Supported Attributes for Presentation LUT

a b



Note: ‘Presentation LUT Shape’ is not supported.

The PAXPORT Print Management Component (SCU) will process the N-CREATE confirmation and response Status codes. The status codes listed below in Table 24 are recognized:

Code Status Meaning 0000H Success Normally returned by the SCP AE. 0116H Warning The SCP AE returns attribute Value Out of Range if an attribute value is out of range.

The PAXPORT Print Management Component will continue without P Luts. B605H Warning The SCP AE returns Requested Min or max density out of range. The PAXPORT Print

Management Component will continue without P Luts. Error If the SCP AE returns any other error or warning status the PAXPORT Print Management

Component will continue without P Luts.

Table 24 N-CREATE confirmation and response Status codes

3.1.3.4.3 SOP Specific Conformance to Basic Color Print Management Meta SOP Class

The PAXPORT Print Management Component provides Standard conformance to the DICOM Basic Color Print Management Class (1.2.840.10008.1.1.18) as SCU.

3.1.3.4.3.1 Basic Film Session SOP Class (1.2.840.10008.5.1.1.1) Refer to the Basic Film Session SOP Class for Basic Grayscale Print Management.

3.1.3.4.3.2 Basic Film Box SOP Class (1.2.840.10008.5.1.1.2) Refer to the Basic Film Box SOP Class for Basic Grayscale Print Management.

3.1.3.4.3.3 Basic Color Image Box SOP Class (1.2.840.10008.5.1.1.4.1) The Basic Color Image Box SOP instance is created by the SCP AE at the time the Basic Film Box SOP instance is created (N-CREATE). The Basic Color Image Box contains the presentation parameters and image pixel data that applies to a single image of a sheet of film.


> N-SET

N-SET is issued by the PAXPORT Print Management Component (SCU) to change some of the Basic Color Image Box attribute values. (Refer to Table 25 for a list of these attributes.) In Basic Print Management, N-SET is also used to define the Image Module (this contains image related attributes and the actual image pixel data). If no pixel data is supplied with the N-SET, the current Image Module is deleted from the hierarchy.

a b



When all needed Basic Color Image Boxes have been set, the PAXPORT Print Management Component can issue a print command. There can be empty image positions. By using N-SET the PAXPORT Print Management Component can instruct the SCP to erase the image in the image position by setting a zero length and no value in the attribute Basic Color Image Sequence.

The N-SET attributes supported are listed below in Table 25 :


Image Position (2020,0010) 1 - x (depending layout) Polarity (2020,0020) NORMAL, REVERSE Requested Image Size (2020,0030) Basic Color Image Sequence (2020,0111) >Samples Per Pixel (0028,0002) 3 >Photometric Interpretation (0028,0004) RGB > Planar Configuration (0028,0006) >Rows (0028,0010) larger than 0 >Columns (0028,0011) larger than 0 >Pixel Aspect Ratio (0028,0034) 10000\10000 (default – see note) >Bits Allocated (0028,0100) 8 >Bits Stored (0028,0101) 8 >High Bit (0028,0102) 7 >Pixel Representation (0028,0103) 0 >Pixel Data (7FE0,0010)

Table 25 Supported N-SET Attributes for a Basic Color Image Box

Note: Pixel Aspect Ratio is only sent when its value differs from the standard value: 10000\10000.

The PAXPORT Print Management Component (SCU) will process the N-SET confirmation and response Status codes. The status codes listed below in Table 26 are recognized:

Code Status Meaning



0107H Warning The SCP AE returns attribute ”Attribute list error” . Then the PAXPORT Print Management Component will continue. A warning message will be printed in the log file.

C605H Error Returned by the SCP AE if there is insufficient memory in the printer to store images. The PAXPORT Print Management Component will retry the current Print Job.


Table 26 Supported N-SET Status Codes

a b



3.1.3.4.3.4 Printer SOP Class (1.2.840.10008.5.1.1.16) Refer to the Printer SOP Class for Basic Grayscale Print Management.

3.1.3.4.4 SOP Specific Conformance to Basic Annotation Box SOP Class

The PAXPORT Print Management Component provides standard conformance to the DICOM Basic Annotation Box Class (1.2.840.10008.5.1.1.15) as SCU.

If the SCP AE supports the DICOM Basic Annotation Box Service Class, the PAXPORT Print Management Component (SCU) issues data for the Basic Annotation Box.


> N-SET

N-SET is used by the PAXPORT Print Management Component (SCU) to update the Basic Annotation Box SOP Instance. The PAXPORT Print Management Component (SCU) can set all Basic Annotation Box Instances. Supported Annotation Box attributes are listed in Table 27 below:


Annotation Position (2030,0010) 1-x (number of annotations) Text String (2030,0020)

Table 27 Supported Attributes for a Basic Annotation Box

3.1.3.5 SOP Specific Conformance – MPPS SCU

3.1.3.5.1 Supported attributes PAXPORT supports the standard DICOM elements for this SOP Class as an SCU as listed in Table 28 below:

Module Attribute Name Group,Tag Remarks

Performed Procedure Step Relationship

Scheduled Step Attribute Sequence 0040,0270

>Study Instance UID 0020,000D From MWL when retrieved, but generated by the equipment when not provided by MWL or when several SPS belonging to different Requested Procedures are satisfied by one PPS

>Referenced Study Sequence 0008,1110 From MWL when retrieved. Zero length when PPS is unscheduled

>>Referenced SOP Class UID 0008,1150 >>Referenced SOP Instance UID 0008,1155 >Accession Number 0008,0050 From MWL when

a b




a b

retrieved. Zero length when PPS is unscheduled

>Placer Order Number/Imaging Service Request

0040,2006 From MWL when retrieved

>Filler Order Number/Imaging Service Request


>Requested Procedure ID 0040,1001 From MWL when retrieved

>Requested Procedure Description 0032,1060 From MWL when retrieved.

>Placer Order Number/Procedure 0040,1007 From MWL when retrieved

>Scheduled Procedure Step ID 0040,0009 From MWL when retrieved

>Scheduled Procedure Step Description


>Scheduled Action Item Code Sequence

0040,0008 From MWL when retrieved, except when changed by operator

>>Code Value 0008,0100 >>Coding Scheme Designator 0008,0102 >>Code Meaning 0008,0104 Patient’s name 0010,0010 From MWL when

retrieved Patient ID 0010,0020 From MWL when

retrieved Patient’s birth date 0010,0030 From MWL when

retrieved Patient’s sex 0010,0040 From MWL when

retrieved Performed Procedure Step Information

Performed Procedure Step ID 0040,0253 Equated to the Scheduled Procedure Step ID from the MWL when retrieved, otherwise generated by the equipment.

Performed Station AE –Title 0040,0241 Performed Station Name 0040,0242 Performed Location 0040,0243 Performed Procedure Step Start Date 0040,0244 Date of the N-Create of

the MPPS Performed Procedure Step Start Time 0040,0245 Time of the N-Create

MPPS Performed Procedure Step Status 0040,0252 Performed Procedure Step Description 0040,0254 Equated to the

Scheduled Procedure Description from MWL when retrieved, except when unscheduled or changed by the operator.

Performed Procedure Type Description 0040,0255




Procedure Code Sequence 0008,1032 Equated to Requested Procedure Code Sequence; set to zero length if Performed Action Item Code differs from the scheduled one.

>Code Value 0008,0100 >Coding Scheme Designator 0008,0102 >Code Meaning 0008,0104 Performed Procedure Step End Date 0040,0250 Date of approval of the

Performed Procedure Step

Performed Procedure Step End Time 0040,0251 Time of approval of the Performed Procedure Step.

Image Acquisition Results Modality 0008,0060 Study ID 0020,0010 Equated to the

Requested Procedure ID from the MWL when retrieved except when unscheduled or SPS grouped in one PPS, then it’s equipment generated.

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

Sequence 0040,0220

Table 28 MPPS SCU Standard DICOM Attributes

a b



3.1.3.5.2 Supported Return Codes PAXPORT supports the standard DICOM return codes for this SOP Class as an SCU as listed in Table 29 below: Service Status Further Meaning Protocol

Codes Related Fields

Description

Error Performed Procedure Step object may no longer be updated.

0110H An N-Set is performed after the Performed Procedure Step was set on “Completed”

Success 0000H

Table 29 MPPS SCU Standard DICOM Attributes

3.1.3.6 SOP Specific Conformance – Modality Worklist SCU PAXPORT provides standard conformance to the DICOM Basic Worklist Management Service Class as an SCU. PAXPORT supports the Broad Query.

A wildcard “*” is always appended to all the Patient’s Name components. The supported Query keys for the Broad Query are listed in Table 30 below:

Matching Key Attribute Name Tag Scheduled Procedure Step Sequence (0040,0100) > Scheduled Station AE Title (0040,0001) > Scheduled Procedure Step Start Date (0040,0002) > Scheduled Procedure Step Start Time (0040,0003) > Scheduled Procedure Step Status (0040,0020) > Modality (0008,0060) > Scheduled Performing Physician’s Name (0040,0006) > Scheduled Station Name (0040,0010) > Schedule Procedure Step Location (0040,0011) Accession Number (0008,0050) Current Patient Location (0038,0300) Patient Name (0010,0010) Patient ID (0010,0020)

Table 30 MWL Keys for Broad Worklist Query

3.1.3.6.1 Query Key Types The PAXPORT requests the Query Key Types for the MWL Query keys listed in Table 31 below:

Matching Key Types

SV Single valued match

RM Range Matching

SM Sequence Matching

Table 31 MWL Keys for Broad Worklist Query

a b



3.1.3.6.2 Query Keys Matching The PAXPORT requests the following matching keys and returns them in the MWL C-FIND service as listed in Table 32 below:

Module Attribute Name Tag Match SOP Common Specific Character Set (0008,0005) SV (ISO_IR 100)

Scheduled Procedure Step Sequence (0040,0100) SM > Scheduled Station AE Title (0040,0001) SV or Zero-length > Scheduled Procedure Step Start Date (0040,0002) SV or RM > Scheduled Procedure Step Start Time (0040,0003) Zero-length > Modality (0008,0060) SV or Zero-length > Scheduled Performing Phys. Name (0040,0006) Zero-length > Scheduled Procedure Step Description (0040,0007) Zero-length > Scheduled Station Name (0040,0010) Zero-length > Scheduled Procedure Step Location (0040,0011) Zero-length > Scheduled Protocol Code Sequence (0040,0008) Zero length >> Code Value (0008,0100) --- >> Coding Scheme Version (0008,0103) --- >> Code Scheme Designator (0008,0102) --- >> Code Meaning (0008,0104) --- > Pre Medication (0040,0012) Zero-length > Scheduled Procedure step ID (0040,0009) Zero-length > Requested Contrast Agent (0032,1070) Zero-length

Scheduled Procedure Step

> Scheduled Procedure Step Status (0040,0020) Zero-length Requested Procedure ID (0040,1001) SV or Zero-length Reason for requested procedure (0040,1002) Zero-length Requested Procedure Description (0032,1060) Zero-length Requested Procedure Code Sequence (0032,1064) Zero-length > Code Value (0008,0100) -- > Coding Scheme Designator (0008,0102) -- > Coding Scheme Version (0008,0103) -- > Code Meaning (0008,0104) -- Study Instance UID (0020,000D) Zero-length Referenced Study Sequence (0008,1110) Zero-length > Referenced SOP Class UID (0008,1150) -- > Referenced SOP Instance UID (0008,1155) -- Requested Procedure Priority (0040,1003) Zero-length

Requested Procedure

Patient Transport Arrangements (0040,1004) Zero-length Accession Number (0008,0050) SV or Zero-length Requesting Physician’s Name (0032,1032) Zero-length Requesting Service (0032,1033) Zero-length Image Service Report Comments (0040,2400) Zero-length

Imaging Service Request

Referring Physician’s Name (0008,0090) Zero-length Visit Identification Admission ID (0038,0010) Zero-length Visit Status Current Patient Location (0038,0300) Zero-length

Referenced Patient Sequence (0008,1120) Zero-length > Referenced SOP Class UID (0008,1150) --

Visit Relationship

> Referenced SOP Instance UID (0008,1155) --

a b



Module Attribute Name Tag Match Patient’s Name (0010,0010) SV with * wildchar

on each component or Zero-length

Patient ID (0010,0020) SV or Zero-length

Patient Identification

Other Patient IDs (0010,1000) Zero-length Patient’s Birth Date (0010,0030) Zero-length Patient’s Sex (0010,0040) Zero-length Patient’s Weight (0010,1030) Zero-length Confidentiality Constraint on Patient Data (0040,3001) Zero-length Patient’s Size (0010,1020) Zero-length Ethnic Group (0010,2160) Zero-length Patients occupation (0010,2180) Zero-length Patient’s Birth Time (0010,0032) Zero-length Military Rank (0010,1080) Zero-length

Patient Demographic

Patient Comments (0010,4000) Zero-length Patient State (0038,0500) Zero-length Pregnancy Status (0010,21C0) Zero-length Medical Alerts (0010,2000) Zero-length Contrast Allergies (0010,2110) Zero-length Special Needs (0038,0050) Zero-length

Patient Medical

Additional Patient History (0010,21B0) Zero-length

Table 32 Modality Worklist Information model attributes.

3.1.3.6.3 Displayed Return Keys The PAXPORT displays following returned keys on the user keypad. See Table 33 below:

Module Attribute Name Tag Scheduled Procedure Step > Scheduled Procedure Step Description

(Series description) (0040,0007)

Requested Procedure Requested Procedure Description (Study description)

(0032,1060)

Imaging Service Request Accession Number (0008,0050)

Patient’s Name (0010,0010) Patient Identification Patient’s ID (0010,0020) Patient’s Birth Date (0010,0030) Patient Demographic Patient’s Sex (0010,0040)

Table 33 Displayed Return Keys

3.1.4 Association Acceptance Policy Not applicable because the PAXPORT (SCU) cannot accept an Association.

a b



4 COMMUNICATION PROFILES

4.1 Supported Communications Stacks PAXPORT provides DICOM V3.0 TCP/IP Network Communication Support as defined in PS 3.8 of the DICOM standard.

4.2 TCP/IP Stack The PAXPORT (SCU) uses TCP/IP for the protocol stacks.

4.3 Physical Medium Support PAXPORT supports 10Base2, 10BaseT, 100BaseT and MII. They are automatically configured via a detection mechanism and are galvanically isolated for IEC601 compliance (not for MII).

5 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS None.

6 CONFIGURATION

6.1 Configurable Parameters See PAXPORT Reference Manual for configuration.

7 SUPPORT FOR EXTENDED CHARACTER SETS None.

8 ACRONYMS AND ABBREVIATIONS The following acronyms and abbreviations are used in this document:

Abstract Syntax A DICOM term which is identical to a DICOM SOP Class, a combination of service class and a type of information object.

ACR American College of Radiology Annotation Box A DICOM name for the equivalent of LINX “text-on-film”. Application Entity (AE) A DICOM term for defining a particular user at an IP address. Association A DICOM term for a communication context which is used by two Application Entities to

“talk to” one another. Association Negotiation The handshaking that occurs between two DICOM Application Entities to set up an

Association. Attributes Each DICOM information object has its own set of characteristics or attributes. Each

attribute may have a value (See IOD), depending on its category. Big Endian A term for encoding the most-significant byte first and remaining bytes in descending

order of significance.

a b



a b

Calling AE Title The name used by the receiver in DICOM protocol to indicate which Application Entity it received the data from. It is also the AE that is initiating the transfer.

Called AE Title The name used by the sender in DICOM protocol to indicate which Application Entity it wants to transmit its data to. It is also the AE that is receiving the transfer.

Conformance Statement A document whose organization and content are mandated by the DICOM Standard, which allows users to communicate how they have chosen to comply with the Standard in their implementations.

DICOM Digital Imaging and Communications in Medicine DIMSE DICOM Message Service Elements: represents an abstraction of a common set of

things that a user would do, in different contexts, to a data element, and would likely use over and over.

DIMSE-C DIMSE Services that are performed on Composite Information Objects. DIMSE-N DIMSE Services that are performed on Normalized Information Objects. IHE Integrating the Healthcare Enterprise IOD Information Object Definition: a software representation of a real object. An information

object is generally a list of characteristics (attributes) which completely describe the object as far as the software is concerned.

Little Endian A term for encoding the least-significant byte first and remaining bytes in ascending order of significance.

Meta SOP Class A group of SOP Classes which are used together to provide a high-level functionality. Module A logical group of the valid attributes of DICOM information objects. NEMA National Electrical Manufacturers Association Presentation Context The combination of Transfer Syntax and Abstract Syntax. The Presentation Context

defines both what data will be sent (Abstract Syntax) and how the data are encoded (Transfer Syntax).

Print Job SOP Class A DICOM representation of a Print Job which consists of a set of IODs which describe a Print Job and a set of services which can be performed on those IODs.

Printer SOP Class A DICOM representation of a Printer which consists of a set of IODs which describe a Printer and a set of services which can be performed on those IODs.

PDU Protocol Data Unit: a data object that is exchanged by protocol machines (entities) within a given layer of the protocol stack.

Service Class A DICOM method for describing a group of operations that a user might want to perform on particular information objects.

SCP Service Class Provider: a device which provides the services of a DICOM Service Class.

SCU Service Class User: a device which utilizes the DICOM Service Class provided by another device.

SOP Service-Object Pair: the combination of a DICOM Information Object and the Service Class which operates upon that object.

TCP/IP Transmission Control Protocol/Internet Protocol Transfer Syntax A part of the DICOM Presentation Context that indicates how an operation and a data

object should be encoded. UID Unique Identifier: a globally unique identifier which is assigned to every DICOM

information object. Value Representation A VR is the defined format of a particular data element. VOI LUT Value of Interest Look-up Table.

Date post:	07-May-2018
Category:	Documents
Upload:	doanduong
View:	219 times
Download:	1 times

Service Class User - Agfa HealthCare · DIGINET: For questions regarding the ... The user of this...

Documents