HEALTHCARE DICOM Conformance Statement

MED/RH/000411 Page 1 of 39 Document No. 000411, Revision 1.2

HealthCare 1 October, 2002

HEALTHCARE DICOM Conformance Statement

LINX Networking System V3.0 Status: Released

Document No. 000411, Revision 1.2

Page 2 of 39 MED/RH/000411 Document No. 000411, Revision 1.2

1 October, 2002 HealthCare

Document Information

Author Rob Horn Tel: 1 (97) 658-0200 x5355 Email: [email protected]

Editing & Layout Lauren Wasserman Email: [email protected] Product Manager Jeff Yorker Tel: 1 (302) 631-3123

Fax: 1(302) 631-3447 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

Issued by: HealthCare Connectivity Division P.O. Box 6020 640 Technology Drive Newark, DE 19714-6020 USA

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.

Tel: 1 (302) 631-3494 Fax: 1 (302) 631-3145 Email: [email protected]

Copyright October, 02 HealthCare

All rights reserved

mailto:[email protected]

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

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

mailto:[email protected]



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 DICOM Background ........................................................................................ 6 1.3 Purpose of this Document ............................................................................... 7 1.4 Sources for this Document .............................................................................. 7 1.5 LINX 3.0 DICOM Storage Client (User)........................................................... 7 1.6 LINX 3.0 DICOM Print Client (User)................................................................ 7 1.7 LINX 3.0 DICOM Print Server (Provider)......................................................... 7 1.8 Important Considerations for the Reader ........................................................ 8

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

2.1 LINX 3.0 DICOM Clients (Storage or Print) ..................................................... 8 2.2 Application Data Flow Diagram: LINX DICOM Clients .................................... 8 2.3 LINX 3.0 DICOM Print Server ......................................................................... 9 2.4 Application Data Flow Diagram: LINX 3.0 DICOM Print Server .................... 10 2.5 Functional Description of AEs ....................................................................... 10 2.6 Sequencing of Real World Activities ............................................................. 11 2.6.1 LINX 3.0 DICOM Clients ........................................................................................ 11 2.6.2 LINX 3.0 DICOM Print Server ................................................................................ 11

3 AE SPECIFICATIONS .................................................................................. 12

3.1 LINX 3.0 DICOM Client AE Specification ...................................................... 12 3.1.1 Association Establishments 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 UID .......................................................................................................... 13 3.1.2 Association Initiation Policy .................................................................................... 13 3.1.2.1 LINX 3.0 DICOM Storage Client ....................................................................................... 13 3.1.2.2 LINX 3.0 DICOM Print Client ............................................................................................ 14 3.1.3 Association Initiation by Real World Activity........................................................... 14 3.1.3.1 LINX 3.0 DICOM Storage Client - Proposed Presentation Contexts................................ 14 3.1.3.2 LINX 3.0 DICOM Print Client-Proposed Presentation Contexts ....................................... 14 3.1.4 Association Acceptance Policy............................................................................... 15 3.1.5 SOP Specific Conformance to Storage SOP Class (LINX 3.0 Storage Client) ...... 15 3.1.5.1 SC Image IOD................................................................................................................... 15 3.1.6 SOP Specific Conformance to Print SOP Classes (LINX 3.0 Print Client) ............. 20



3.1.6.1 SOP Specific Conformance to Basic Film Session SOP Class........................................ 20 3.1.6.2 SOP Specific Conformance to Basic Film Box SOP Class............................................... 21 3.1.6.3 SOP Specific Conformance to Basic Image Box SOP Class ........................................... 22 3.1.6.4 SOP Specific Conformance to Annotation Box SOP Class.............................................. 23 3.1.6.5 SOP Specific Conformance to Printer SOP Class............................................................ 23 3.1.6.6 SOP Specific Conformance to PrintJob SOP Class ......................................................... 24 3.2 LINX 3.0 DICOM Print Server AE Specification ............................................ 25 3.2.1 Association Establishment Policies ........................................................................ 26 3.2.1.1 General ............................................................................................................................. 26 3.2.1.2 Number of Associations .................................................................................................... 26 3.2.1.3 Asynchronous Nature ....................................................................................................... 26 3.2.1.4 Implementation UID .......................................................................................................... 26 3.2.1.5 Association Initiation Policy............................................................................................... 26 3.2.2 Association Acceptance ......................................................................................... 26 3.2.2.1 Association Acceptance by Real-World Activity ............................................................... 26 3.2.2.2 Presentation Context Acceptance Criteria........................................................................ 27 3.2.3 SOP Specific Conformance (LINX 3.0 Print Server) .............................................. 27 3.2.3.1 SOP Specific Conformance to Basic Film Session SOP Class........................................ 27 3.2.3.2 SOP Specific Conformance to Basic Film Box SOP Class............................................... 28 3.2.3.3 SOP Specific Conformance to Basic Image Box SOP Class ........................................... 30 3.2.3.4 SOP Specific Conformance to Annotation Box SOP Class.............................................. 32 3.2.3.5 SOP Specific Conformance to Printer SOP Class............................................................ 33 3.2.3.6 SOP Specific Conformance to PrintJob SOP ................................................................... 34 3.2.3.7 SOP Specific Conformance to Verification SOP Class..................................................... 35

4 Communication Profiles............................................................................. 36

4.1 TCP/IP Stack................................................................................................. 36 4.2 Physical Media Support ................................................................................ 36

5 Extensions/Specializations/ Privatizations............................................... 36

6 Configuration............................................................................................... 36

6.1 LINX 3.0 DICOM Storage Client Configuration ............................................. 36 6.2 LINX 3.0 DICOM Print Client Configuration................................................... 36 6.3 LINX 3.0 DICOM Print Server Configuration ................................................. 37 6.4 Configuration Defaults................................................................................... 38

7 Acronyms and Abbreviations .................................................................... 38



Revision Record

Revision Date Author Reason for Change 1.0 12 April 2000 Initial revision-document converted to Agfa template 1.1 08 September 2000 A. Morris New conventions implemented 1.3 20 August 2002 L. Wasserman Reformatted, Released



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.

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 user of this conformance statement, in conjunction with the DICOM 3.0 standard, is intended to facilitate communication with other medical 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.

1.2 DICOM Background In the 1980s, the American College of Radiology (ACR) and the National Electrical Manufacturer’s Association (NEMA) formed a joint committee to develop a standard for Digital Imaging and Communication in Medicine (DICOM).

The DICOM standard is developed in conjunction with other standardization organizations, including CEN TC251 in Europe and JIRA in Japan, with review by other organizations, including IEEE HL7 and ANSI in the USA. This standard defines classes of information that are common to many modalities of medical imaging.

A requirement of DICOM is to maintain a compliance document that outlines a subset of DICOM services and data classes supported by an application. The purpose of this document is to define a subset of DICOM for the exchange of information with the DICOM Print Server and the printers that it supports.



1.3 Purpose of this Document This document is a provisional DICOM Conformance Statement for the storage services of the LINX Networking System. The LINX Networking System will be referred to as the LNS.

This document describes the LNS conformance to the ACR-NEMA DICOM (Digital Imaging and Communications in Medicine) standard, and satisfies the DICOM requirement for a vendor conformance specification.

The LINX Networking System (LNS) is a modular system used for storage, processing, printing or otherwise communicating medical image data, primarily for the purpose of printing to Laser Film Printers.

1.4 Sources for this Document The following documents contain provisions that, through reference in this text, should be considered to be provisions of this document: > > > > > > > > > > > >

ACR NEMA PS 3.1-Part 1: Introduction ACR NEMA PS 3.2-Part 2: Conformance ACR NEMA PS 3.3-Part 3: Information Object Definitions ACR NEMA PS 3.4-Part 4: Service Class Specifications ACR NEMA PS 3.5-Part 5: Data Structures and Encoding ACR NEMA PS 3.6-Part 6: Data Dictionary ACR NEMA PS 3.7-Part 7: Message Exchange ACR NEMA PS 3.8-Part 8: Network Communications Support for Message Exchange LNS Image Gateway User Manual: January 1997 LNS Image Gateway Service Manual: January 1997 LINX Planning Guide II: 1996 Agfa Medical Imaging Document No. 000410 (LINX V2.8.1 modifications): original document dated October 1998

1.5 LINX 3.0 DICOM Storage Client (User) The LINX 3.0 DICOM Storage Client is a software function the LINX 486/66 Image Gateway, or the iiSYS pacLINX product for interfacing a LINX 3.0 network to a TCP/IP network with DICOM Storage Servers. This allows the LINX 3.0 DICOM Storage Client to send medical images and related data to a non-LINX DICOM Storage Server (Provider).

1.6 LINX 3.0 DICOM Print Client (User) The LINX 3.0 DICOM Print Client is a software function of the LINX 486/66 Image Gateway, LINX 486/66 DPU, LINX DPU or the iiSYS pacLINX product for interfacing a LINX network to a TCP/IP network with DICOM Print Servers. This allows the LINX 3.0 DICOM Print Client to send medical images and related data to a DICOM Print Server (Provider) for printing.

1.7 LINX 3.0 DICOM Print Server (Provider) The Sterling Diagnostic Imaging LINX 3.0 DICOM Print Server is a software function of the LINX 486/66 Image Gateway product, the LINX 486/66 DPU product, or the iiSYS pacLINX product for interfacing a LINX 3.0 network to a TCP/IP network with DICOM Print Clients. This allows the LINX 3.0 DICOM Print Server (Provider) to accept medical images and related data from a DICOM Print Client (User) for printing.



NOTE: For the purposes of this Conformance Claim, the Helios 1417 Laser Imager's DICOM Print Provider is not considered part of the LNS. There is a separate Conformance Claim for the Helios product.

1.8 Important Considerations for the Reader There is no concept in DICOM of a singular "monolithic" compliance with the Standard. The DICOM Conformance Statement, which is a document whose organization and content are mandated by the Standard, allows users to communicate how they comply with the Standard in their implementations. The presence of specific DICOM functionality in a Conformance Statement is not sufficient to guarantee inter-operability between components. The following should be considered when evaluating network inter-operability: >

>

>

The LINX 3.0 DICOM Conformance Claim is a good starting point for ascertaining whether LINX 3.0 can communicate with a particular component on a protocol level. The only way to know for certain whether LINX 3.0 can inter-operate with other DICOM components is to perform a connectivity test. This test must be completed before a field installation can occur. Agfa is equipped to do this testing in cooperation with the suppliers of other DICOM components. This document is Agfa's best effort at documenting the DICOM functionality of commercial versions of LNS, and is not a functional specification of any LINX 3.0 component or product. Agfa is committed to following the evolution of the DICOM Standard with either modifications or additions to the LNS DICOM functionality.

2 IMPLEMENTATION MODEL LINX 3.0 DICOM Clients (storage and print) and Servers (print only) are implemented as independent, functional blocks and are each separately configured.

2.1 LINX 3.0 DICOM Clients (Storage or Print) A LINX 3.0 Networking System may have installed, zero or more DICOM clients. Each LINX 3.0 DICOM Client is implemented as a single Application Entity. Each client may be configured to provide access to one or more remote DICOM servers. Access to remote DICOM servers is supported only over TCP/IP network connections. Multiple LINX 3.0 clients may concurrently initiate and/or maintain associations from one TCP/IP host address; however, at any time each client will maintain no more than one active DICOM association. The maximum number of DICOM clients that can exist on one 486 LINX 3.0 Network node or host is configurable, up to a maximum of four. The maximum number of DICOM clients that can exist on one iiSYS pacLINX node is ten.

A LINX 3.0 DICOM client is configured with a list of possible destinations. The LINX 3.0 user is presented with this list of destinations and can select one or more for any set of images to be transmitted. A LINX 3.0 DICOM Client may send to multiple destinations; this is referred to as a “multicast transmission”.

The LINX 3.0 DICOM Storage and Print Clients are accessed from within the LINX 3.0 Networking System as spooled output devices, in the same manner as traditional hardcopy devices (laser film imagers, postscript printers, etc), and other softcopy devices (non-DICOM imaging workstations, teleradiography transmission systems, etc). The user submits a request to a spooled output device for transmission of images or other objects to some remote device. The user is then free to perform other functions.

2.2 Application Data Flow Diagram: LINX DICOM Clients This implementation model of the LINX 3.0 DICOM Clients is depicted in the following figure:



Figure 2.1 Application data flow diagram.

2.3 LINX 3.0 DICOM Print Server A LINX 3.0 Networking System may have zero or more LINX 3.0 DICOM Print Servers installed. Each LINX 3.0 DICOM Print Server supports multiple Application Entities. One or more Application Entities are available through the Print Server for each physical output device that DICOM Print Clients may address. Multiple DICOM Print Clients may concurrently initiate and/or maintain associations to the LINX 3.0 DICOM Print Server. These associations can be for the same or different Application Entities. The number of associations to the LINX 3.0 DICOM Print Server that can be simultaneously active is configurable, up to a maximum of four associations on the LINX 3.0 486 platform, and up to a maximum of ten on the iiSYS pacLINX Dell platform. After the maximum number of associations are established, the LINX 3.0 DICOM Print Server will reject any further client association requests that are received until an association is released.

By means of the DICOM association, the LINX 3.0 DICOM Print Server accepts jobs from DICOM Print Clients and enters those jobs into the output queues for the physical LINX 3.0 devices that were configured for the Called Application Entity. Once a complete job is transmitted to the LINX 3.0 DICOM Print Server, LNS takes over the tasks of completing the print. The DICOM Print Client is then free to perform other functions. To ascertain when the job is complete, the DICOM Print Client may keep the association open and may query the LINX 3.0 DICOM Print Server using the Print Job SOP Class. The LINX 3.0 DICOM Print Server can be configured to support sending N-EVENT-REPORTs to the DICOM Print Client.



2.4 Application Data Flow Diagram: LINX 3.0 DICOM Print Server This implementation model of the LINX 3.0 DICOM Print Server is depicted in the following figure:

Figure 2.1 Supported SOP Classes.

2.5 Functional Description of AEs Each installed LINX 3.0 DICOM Client functions as a single Application Entity, maintaining, at most, one association. The AE functions as a Service Class User (SCU) for one of the following service classes, depending on the output request that is being serviced: > > >

Secondary Capture Image Storage Basic Grayscale Print Management MetaSOP Class Optional SOPs: Annotation Box SOP Class and Print Job SOP Class



Each installed LINX 3.0 DICOM Print Server functions as up to four Application Entities on the 486 platform, and ten on the iiSYS pacLINX product. Each of these Print Servers maintains, at most, one association. Each AE functions as a Service Class Provider (SCP) for one of the following service classes, depending on the incoming request that is being serviced: > > > >

>

>

> >

>

> >

Basic Grayscale Print Management MetaSOP Class Optional SOPs: Annotation Box SOP Class and Print Job SOP Class Basic Color Print Management MetaSOP Class Optional SOPs: Annotation Box SOP Class and Print Job SOP Class

2.6 Sequencing of Real World Activities

2.6.1 LINX 3.0 DICOM Clients The Application Entity corresponding to the desired physical output device must be configured into the LINX 3.0 DICOM Client’s network database to be used as the "Called Application Entity." The remote host name(s) and IP address(es) must also be configured into the LINX 3.0 DICOM Client’s network database.

A user initiates a DICOM transfer by “printing” from a LINX Keypad or other LNS capture device to a LINX output that has been configured as a DICOM Client. The following steps then occur:

Depending on the type of selected LINX 3.0 output device (storage, print, etc.), the LINX 3.0 DICOM Client will request an association to the Called AE of the DICOM Server corresponding to that output device. The desired SOP classes are negotiated and utilized to perform either a print job or storage job as requested by the LINX 3.0 DICOM Client. The use of optional Print Management SOP classes by the LINX 3.0 DICOM Print Client is configurable. The LINX 3.0 DICOM Client transfers the images to the DICOM Server using the negotiated SOP Classes. If the Print Job SOP Class has been negotiated, the LINX 3.0 DICOM Print Client will perform N-GETs on the Print Job to obtain status from the DICOM Print Server for a period equal to the configured timeout or until the Print Job status is DONE or FAILURE. If the Print Job SOP Class has not been negotiated, the LINX 3.0 DICOM Client disconnects the association once all tasks are completed, or after a configurable timeout period expires. If one of the Storage SOPs is used and there is a zero timeout value configured, the LINX 3.0 DICOM Storage SCU will disconnect the association immediately after acknowledgement of the C-STORE command by the Storage SCP. If a non-zero timeout is configured, the association is left open for the duration of the timeout and is used to transfer subsequent images in the study.

In the case of errors during a job with a transmission from a LINX 3.0 DICOM Client, the following applies: With a LINX 3.0 DICOM Storage SCU, the job will always be automatically retried. With a LINX 3.0 DICOM Print SCU, the job will be re-tried if it contains a temporary error condition, otherwise it will be aborted (see Section xx for a description of such error conditions).

For a multicast job, only the destination(s) that failed will be included in the list of destinations for a retry job. In all cases, the user is notified of an error and may abort the job if desired.

2.6.2 LINX 3.0 DICOM Print Server The “Called AE Titles” which are to be requested by remote DICOM Print Clients (SCUs) must be configured into the LINX 3.0 DICOM Print Server’s local user record database. The remote hostnames and IP addresses of DICOM Print Clients need not be configured into the LINX 3.0 Print Server’s network database, since no validation of these is done by LINX. The TCP port on which the LINX 3.0 DICOM Print Server will listen for association requests is configured into the Print Server, along with additional configuration parameters such as whether to allow the optional Print SOPs. A physical LINX output device(s) is “connected” with a configured Called AE Title(s) on the LINX 3.0 Print Server using a network setup menu.



The DICOM Print Client requests an association to the LINX 3.0 DICOM Print Server using the Application Entity corresponding to the desired output device. The DICOM Print Client negotiates for the desired SOP classes to be utilized to perform print jobs. The LINX 3.0 DICOM Print Server will grant the association request based on its own configuration and will accept the transfer of DICOM Print objects, storing them in its local database. After the successful issuing of an N-ACTION (Print) on the Film Box by the DICOM Print Client, the LINX 3.0 DICOM Print Server will place an entry for the print job on the LINX queue of the output device associated with the DICOM Called AE. The LINX 3.0 DICOM Print Server will inform the DICOM Print Client of status by answering N-GET requests on either the Printer SOP or Print Job SOP, or by issuing N-EVENT-REPORTs (if configured to do so), as long as the association is open. The LINX 3.0 DICOM Print Server will not currently allow an N-ACTION (Print) on a Film Session (future enhancement). It will allow the DICOM Print Client to over-write the image data in an existing Film Box (template mode). The LINX 3.0 DICOM Print Server expects the DICOM Print Client to disconnect the association once all tasks are completed; however, it can be configured to disconnect associations after a timeout period.

In case of errors, the following applies: >

>

During a DICOM transmission and while the association is open, the LINX 3.0 DICOM Print Server supports the full range of DICOM Printer and Print Job status codes and will return these to the DICOM Print Client (see Section x SOP-specific conformance). After the DICOM transmission is completed and the association is closed, it is not possible, per the DICOM Standard, for the LINX 3.0 DICOM Print Server to communicate any job status to a DICOM Print Client. However, LINX handles the print jobs created by the DICOM Print Server exactly as any other within LINX. The print job is entered into the LINX database, and the extensive capabilities of LNS are available to monitor and control the print job’s status.

3 AE SPECIFICATIONS As described in Section 2, multiple LINX 3.0 DICOM Clients (print or storage) and Servers (print only) may be installed in a LINX 3.0 Network, or even on a single node of a LINX 3.0 Network. The functional specification of each node typesets limits on the maximum possible number of clients and servers on a given node. Separate sections below specify the conformance of LINX 3.0 DICOM Clients and Servers.

Multiple Called AE Titles may be configured on a single LINX 3.0 DICOM Client. AE Titles may be assigned as required on an implementation basis to different physical output devices. A single physical device may have more than one Application Entity assigned.

A single Print Service Class AE may also have more than one physical output device assigned. This allows a DICOM Print Client to send print jobs concurrently to multiple LINX output devices.

3.1 LINX 3.0 DICOM Client AE Specification The LINX 3.0 DICOM Clients (Storage and Print) provide Standard Conformance to the following DICOM Version 3.0 SOP Classes as a Service Class User (SCU):

SOP Class Name UID Usage Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 U

Table 3.1 Supported Storage SOP Classes.

NOTE: DICOM-specific usage Mandatory (M) and User Option (U) is used in the following tables:

SOP Class Name UID Usage Basic Grayscale Print Management MetaSOP 1.2.840.10008.5.1.1.9 M

Table 3.2 Supported Print MetaSOP Classes.



SOP Class Name UID Usage Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 M Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 M Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4 M Basic Printer SOP Class 1.2.840.10008.5.1.1.16 M

Table 3.3 Mandatory SOP Classes in Grayscale Print MetaSOP Class.\

The LINX 3.0 DICOM Print Client will support the following optional SOP classes if specifically configured to do so:

SOP Class Name UID Usage Print Job SOP Class 1.2.840.10008.5.1.1.14 U Basic Annotation Box SOP Class 1.2.840.10008.5.1.1.15 U

Table 3.4 Supported Optional Print SOP Classes.

3.1.1 Association Establishments Policies

3.1.1.1 General The LINX 3.0 DICOM Storage Client initiates associations as needed with Storage SCPs. The LINX 3.0 DICOM Print Client initiates associations as needed with Print SCPs.

The maximum PDU size that can be transmitted by the LINX 3.0 DICOM Storage Client is configurable, with a default (and maximum) value of 4096 bytes.

The maximum PDU size that can be transmitted by the LINX 3.0 DICOM Print Client is configurable, with a default (and maximum) value of 16384 bytes.

3.1.1.2 Number of Associations LINX 3.0 DICOM Client AEs maintain at most one active association.

3.1.1.3 Asynchronous Nature LINX 3.0 DICOM Client AEs do not support asynchronous operations.

3.1.1.4 Implementation UID

3.1.2 Association Initiation Policy

3.1.2.1 LINX 3.0 DICOM Storage Client The LINX 3.0 DICOM Storage Client attempts to establish an association with a remote Storage SCP when it receives an internal request to transmit an image to that SCP. To reduce the overhead of association establishment, if the remote host address, port, AE name, and required SOP class have not changed from the last image transmitted, an attempt may be made to reuse the last association. This implies that associations can be left open after an image is transmitted. If the last association cannot be used for the current image transfer request, it is released, and a new one is established.

The LINX 3.0 DICOM Storage Client will release the association after a period of inactivity. The length of this period is configurable via an association timeout parameter (see Section configuration section below).



3.1.2.2 LINX 3.0 DICOM Print Client The LINX 3.0 DICOM Print Client attempts to establish an association with a remote Print SCP when it receives an internal request to transmit a sheet to that SCP. Established associations will remain active until the print job is complete (as communicated from the Print SCP), or until a configurable amount of idle time has elapsed. There are two separate timers which control how long the LINX 3.0 DICOM Print Client holds an association open waiting for the print job to complete (see Section x configuration below):

Print Job Timeout - For the Print Job SOP Class only, the period of time in seconds that LINX will hold an association open after a successful N-ACTION (Print) in order to query the Print Job SOP Class for a “DONE” or a “FAILURE” status.

>

> Association Timeout - The period of time that LINX will hold an association open after the above timer expires. This allows re-using of open associations to avoid the overhead of association establishment.

3.1.3 Association Initiation by Real World Activity LNS identifies which DICOM Client to use by the user’s selection of a LINX output device on the network for print jobs. The user’s selection implies either the “storage” of an object, via a DICOM Storage Job to a workstation or archive, or the “printing” of an object, via a DICOM Print Job to an output device.

3.1.3.1 LINX 3.0 DICOM Storage Client - Proposed Presentation Contexts For storage jobs on all LINX 3.0 capture nodes, the LINX 3.0 DICOM Storage Client will initiate an association to the Storage SCP using the SC SOP Class. If the association is successfully created, the C-STORE request is made to effectively transfer the IOD to the destination. The LINX 3.0 DICOM Storage Client then waits for the C-STORE response to be returned.

The LINX 3.0 DICOM Storage Client will attempt to establish an association by proposing the presentation context listed below:

Presentation Context Table Abstract Syntax Transfer Syntax

Name UID Name List UID List Role Ext. Neg.

Secondary Capture Image Storage

1.2.840.10008.5.1.4.1.1.7 DICOM Implicit VR Little Endian

1.2.840.10008.1.2 SCU None

Table 3.5 Proposed Storage Presentation Contexts.

3.1.3.2 LINX 3.0 DICOM Print Client-Proposed Presentation Contexts For a given sheet to be printed, the LINX 3.0 DICOM Print Client will request the establishment of an association with the DICOM Print SCP using the Basic Grayscale Print Management SOP Class. Additionally, if configured to do so, the LINX 3.0 DICOM Print Client will negotiate for the optional Print Job SOP Class and the Annotation Box SOP Class.

After an association is established, the LINX 3.0 DICOM Print Client will send print jobs to the DICOM Print Server. Each print job consists of the following steps: >

>

The LINX 3.0 Print Client sends the server an N-GET request to ascertain that the status of the printer is NORMAL. The LINX 3.0 Print Client requests the server to N-CREATE a film session SOP instance. The LINX 3.0 Print Client then requests the server to N-CREATE a film box SOP instance containing the appropriate number of image box SOP instances and annotation box SOP instances. The LINX 3.0 Print Client always uses one film box per film session. For each image to be printed as part of a film box, the LINX 3.0 Print Client requests the server to N-SET (update) the appropriate image box with the image information. This causes the transfer of the image and pixel data from the client to the server. For an optional annotation box to be included on the film, the LINX 3.0 Print Client requests the server to N-SET the appropriate annotation box with text.



> Once all the images have been transferred, the LINX 3.0 Print Client requests the server to N-ACTION the film box. This causes the film to be printed.

NOTE: Collation is not supported. That is, the LINX 3.0 Print Client will not request an N-ACTION on a film session.

> If the Print Job SOP class has been negotiated, the LINX 3.0 Print Client will poll the SCP using the N-GET DIMSE on the Print Job and Printer SOPs until an execution status of either “FAILURE” or “DONE” is received on the Print Job or until a configurable timeout expires. If the Print Job SOP class has not been negotiated, the LINX 3.0 Print Client will consider the print to be complete as soon as the confirmation of the N-ACTION (Print) is received. The LINX 3.0 Print Client will accept N-EVENT-REPORTs from the Print SCP but will ignore them.

The LINX 3.0 DICOM Print Client utilizes the presentation contexts listed below:


Name UID Name List UID List Role Ext.

Neg. Basic Grayscale Print Management Meta SOP

1.2.840.10008.5.1.9 DICOM Implicit VR Little Endian

1.2.840.10008.1.2 SCU None

Print Job SOP 1.2.840.10008.5.1.14 DICOM Implicit VR Little Endian

1.2.840.10008.1.2 SCU None

Basic Annotation Box SOP 1.2.840.10008.5.1.15 DICOM Implicit VR Little Endian

1.2.840.10008.1.2 SCU None

Table 3.6 Proposed Print Presentation Contexts.

3.1.4 Association Acceptance Policy LINX 3.0 DICOM Clients do not accept incoming associations.

3.1.5 SOP Specific Conformance to Storage SOP Class (LINX 3.0 Storage Client)

Name Usage Description C-STORE M Stores the image

Table 3.7 Storage SOP Class: Supported DIMSE Services.

3.1.5.1 SC Image IOD The DICOM Standard (PS 3.3-1998) specifies that the following IOD modules are included in the SC Image IOD. The LINX 3.0 DICOM Storage Client supports attributes within the modules which appear in bold in the following table.

IE Module DICOM Standard Reference DICOM Standard SC IOD Support Patient Patient PS 3.3-C.7.1.1 Required

General Study PS 3.3-C.7.2.1 Required Study Patient Study PS 3.3-C.7.2.2

Series General Series PS 3.3-C.7.3.1 Required General Equipment PS 3.3-C.7.5.1 Equipment SC Equipment PS 3.3-C.8.6.1 Required



IE Module DICOM Standard Reference DICOM Standard SC IOD Support General Image PS 3.3-C.7.6.1 Required Image Pixel PS 3.3-C.7.6.3 Required SC Image PS 3.3-C.8.6.2 Required Overlay Plane PS 3.3-C.9.2 Modality LUT PS 3.3-C.11.1 VOI LUT PS 3.3-C.11.2

Image

SOP Common PS 3.3-C.12.1 Required

Table 3.8 Storage SOP Class: Supported DIMSE Services.

The LINX 3.0 DICOM Storage Client supports the specific attributes in the SC Image IOD identified in the tables below. Attributes which appear in bold in Tables xx are supported; those not in bold are not supported. Type 1 attributes are always filled in. Unless otherwise noted below, Type 2 and Type 3 attributes are present and filled in if information is available for them, but will be present and blank if there is no attribute information available.

The “Source” column refers to the LINX application that supplies the attribute: > > >

SID: Supplied by LINX SID at capture time XNI: Supplied by LINX SID Extended Node Information File entry PIM: Supplied by LINX Patient Information Management Database

DICOM Attribute Name DICOM Tag DICOM Type Source Attribute Description

Referenced Patient Sequence (0008,1120) 3 >Referenced SOP Class UID (0008,1150) 1C >Referenced SOP Instance UID (0008,1155) 1C Patient's Name (0010,0010) 2 PIM Patient's full legal name. Patient ID (0010,0020) 2 PIM Primary hospital ID for the patient. Patient's Birth Date (0010,0030) 2 PIM Birth date of the patient. Patient's Birth Time (0010,0032) 3 PIM Birth time of the patient. Patient's Sex (0010,0040) 2 PIM Sex of the named patient. Enumerated values are:

M = male F = female O = other Note: U = unknown (HL7) becomes O (other)

Other Patient ID (0010,1000) 3 PIM Other identification numbers or codes used to identify the patient.

Other Patient Names (0010,1001) 3 PIM Other names used to identify the patient. Ethnic Group (0010,2160) 3 PIM Ethnic group or race of the patient. Patient Comments (0010,4000) 3 PIM User-defined additional information about the patient.

Table 3.9 Patient Module Attributes (SC Image IOD).


Admitting Diagnoses Description (0008,1080) 3 PIM Description of the admitting diagnosis (diagnoses) Patient's Age (0010,1010) 3 PIM Age of the patient. Patient's Size (0010,1020) 3 PIM Length or size of the patient, in meters. Patient's Weight (0010,0030) 3 PIM Weight of the patient, in kilograms. Occupation (0010,2180) 3 PIM Occupation of the patient. Additional Patient's History (0010,21B0) 3 PIM Additional info about the patient's medical history.

Table 3.10 Patient Study Module Attributes (SC Image IOD).




Study Date (0008,0020) 2 SID Date the Study started. Study Time (0008,0030) 2 SID Time the Study started. Accession Number (0008,0050) 2 PIM An RIS generated number, which identifies the order

for the Study. Referring Physician's Name (0008,0090) 2 PIM Patient's referring physician. Study Description (0008,1030) 3 PIM Institution-generated description or classification of

the Study (component) performed. Physician(s) of Record (0008,1048) 3 Name of Physician(s) Reading Study

(0008,1060) 3 PIM Physician(s) reading the Study.

Referenced Study Sequence (0008,1110) 3 >Referenced SOP Class UID (0008,1150) 1C >Referenced SOP Instance UID (0008,1155) 1C Study Instance UID (0020,000D) 1 SID Unique identifier for the Study. Study UID (0020,0010) 2 SID User or equipment generated Study Identifier.

Table 3.11 General Study Module Attributes (SC Image IOD).


Series Date (0008,0021) 3 Series Time (0008,0031) 3 Modality (0008,0060) 1 XNI Configurable: Equipment that originally acquired

the data used to create the images in this Series. Defined Terms: CR, CT, MR, NM, US, OT, AS, BI, CD, CP, CS, DD, DG, DM, EC, ES, FA, FS, LP, LS, MA, MS, PT, RG, ST, TG, XA, RF

Series Description (0008,103E) 3 PIM User provided description of the Series. Performing Physicians' Name (0008,1050) 3 PIM Name of the physicians administering the Series. Operators' Name (0008,1070) 3 PIM Technologist(s) supporting the Series. Referenced Study Component Sequence

(0008,1111) 3

>Referenced SOP Class UID (0008,1150) 1C >Referenced SOP Instance UID (0008,1155) 1C Body Part Examined (0018,0015) 3 PIM Text description of the part of the body examined.

Defined Terms: SKULL, CSPINE, TSPINE, LSPINE, SSPINE, COCCYX, CHEST, CLAVICLE, BREAST, ABDOMEN, PELVIS, HIP, SHOULDER, ELBOW, KNEE, ANKLE, HAND, FOOT, HEART, NECK, LEG, ARM

Protocol Name (0018,1030) 3 PIM User-defined description of the conditions under which the Series was performed.

Patient Position (0018,5100) 2C PIM Patient position descriptor relative to the equipment. Not required for SC images but can be inserted in PIM DB by the IS.

Series Instance UID (0020,000E) 1 SID Unique identifier of the Series. Series Number (0020,0011) 2 SID A number that identifies the Series. Laterality (0020,0060) 2C PIM Laterality of (paired) body part examined. Can be

inserted in PIM DB by the IS. Enumerated Values: R = right, L = left

Smallest Pixel Value in Series (0028,0108) 3 Largest Pixel Value in Series (0028,0109) 3 Request Attributes Sequence (0040,0275) 3 >Requested Procedure ID (0040,1001) 1C >Scheduled Procedure Step ID (0040,0009) 1C >Scheduled Procedure Step Desc. (0040,0007) 3




>Scheduled Action Item Code Seq. (0040,0008) 3 >>Code Value (0008,0100) 1C >>Code Scheme Designator (0008,0102) 1C >>Code Meaning (0008,0104) 3 Performed Procedure Step ID (0040,0253) 3 Performed Procedure Step Start Date

(0040,0244) 3

Performed Procedure Step Start Time

(0040,0245) 3

Performed Procedure Step. Desc. (0040,0254) 3 Table 3.12 General Series Module Attributes (SC Image IOD).

DICOM Attribute Name DICOM Tag DICOM Type Source Attribute Description Manufacturer (0008,0070) 2 XNI Configurable: Manufacturer of the equipment

that produced the digital images. Institution Name (0008,0080) 3 XNI Institution Address (0008,0081) 3 XNI Station Name (0008,1010) 3 XNI Institutional Department Name (0008,1040) 3 XNI Manufacturer's Model Name (0008,1090) 3 XNI Device Serial Number (0018,1000) 3 Software Versions (0018,1020) 3 Spatial Resolution (0018,1050) 3 Date of Last Calibration (0018,1200) 3 Time of Last Calibration (0018,1201) 3 Pixel Padding Value (0028,0120) 3

Table 3.13 General Equipment Module Attributes (SC Image IOD).

DICOM Attribute Name DICOM Tag DICOM Type Source Attribute Description Modality (0008,0060) 3 XNI Configurable: Source equipment for the image. Conversion Type (0008,0064) 1 XNI Configurable: Describes the image conversion.

Defined Terms are: DV = Digitized Video DI = Digital Interface DF = Digitized Film WSD = Workstation

Secondary Capture Device ID (0018,1010) 3 Secondary Capture Device Manufacturer

(0018,1016) 3 XNI Configurable: Manufacturer of the Secondary Capture Device.

Secondary Capture Device Manufacturer's Model Name

(0018,1018) 3 XNI Configurable: Manufacturer's model number of the Secondary Capture Device.

Secondary Capture Device Software Version

(0018,1019) 3 XNI Configurable: Manufacturer's designation of software version of the Secondary Capture Device.

Video Image Format Acquired (0018,1022) 3 Digital Image Format Acquired (0028,1023) 3

Table 3.14 SC Image Equipment Module Attributes (SC Image IOD).




Image Number (0020,0013) 2 SID Number of this image in a series. Patient Orientation (0020,0020) 2C SID Always L\F Image Date (0008,0023) 2C Required for temporally related images in a series.Image Time (0008,0033) 2C Required for temporally related images in a series.Image Type (0008,0008) 3 Acquisition Number (0020,0012) 3 Acquisition Date (0008,0022) 3 Acquisition Time (0008,0032) 3 Reference Image Sequence (0008,1140) 3 >Referenced SOP Class UID (0008,1150) 1C >Referenced SOP Class Instance UID

(0008,1155) 1C

Derivation Description (0008,2111) 3 Source Image Sequence (0008,2112) 3 >Referenced SOP Class UID (0008,1150) 1C >Referenced SOP Instance UID (0008,1155) 1C Images in Acquisition (0020,1002) 3 Image Comments (0020,4000) 3 Lossy Image Compression (0028,2110) 3

Table 3.15 General Image Module Attributes (SC Image IOD).


Samples per Pixel (0028,0002) 1 SID 1 Photometric Interpretation (0028,0004) 1 SID Monochrome2 Rows (0028,0010) 1 SID Number of rows in the image. Columns (0028,0011) 1 SID Number of columns in the image. Bits Allocated (0028,0100) 1 SID Number of bits allocated for each pixel sample.

8 or 16 Bits Stored (0028,0101) 1 SID Number of bits stored for each pixel sample.

8 or 12 High Bit (0028,0102) 1 SID Most significant bit for pixel sample data.

7 or 11 Pixel Representation (0028,0103) 1 SID Data representation of the pixel samples.

0000H (unsigned integer) Pixel Data (7FE0,0010) 1 SID Pixel data stream. Planar Configuration (0028,0006) 1C Required only when (0028,0002) > 1 Pixel Aspect Ratio (0028,0034) 1C SID Ratio of vertical and horizontal size of pixels Smallest Image Pixel Value (0028,0106) 3 Largest Image Pixel Value (0028,0107) 3 Red Palette Color Lookup Table Descriptor

(0028,1101) 1C

Green Palette Color Lookup Table Descriptor

(0028,1102) 1C

Blue Palette Color Lookup Table Descriptor

(0028,1103) 1C

Red Palette Color Lookup Table Data (0028,1201) 1C Green Palette Color Lookup Table Data (0028,1202) 1C Blue Palette Color Lookup Table Data (0028,1203) 1C

Table 3.16 Image Pixel Module Attributes (SC Image IOD).




Date of Secondary Capture (0018,1012) 3 SID The date the Secondary Capture Image was captured. Time of Secondary Capture (0018,1014) 3 SID The time the Secondary Capture Image was captured.

Table 3.17 SC Image Module Attributes (SC Image IOD).


Specific Character Set (0008,0005) 1C Instance Creation Date (0008,0012) 3 Instance Creation Time (0008,0013) 3 Instance Creator UID (0008,0014) 3 SOP Class UID (0008,0016) 1 SID Uniquely identifies the SOP Class. SOP Instance UID (0008,0018) 1 SID Uniquely identifies the SOP Instance.

Table 3.18 SOP Common Attributes (SC Image IOD).

DICOM Attribute Name DICOM Tag (see Note 1)

DICOM Type Source Attribute Description Module Name

Medical Record Locator (0010,1090) 3 PIM Other identification code (e.g., SSN) used to identify the patient.

Patient Identification

Window Center (see Note 2) (0028,1050) 3 SID Calculated as the center of the data window for display.

VOI LUT

Window Width (see Note 2) (0028,1051) 3 SID Calculated as the width of the data window for display.

VOI LUT

Table 3.19 SOP Common Attributes (SC Image IOD).

NOTES: 1. Since the attributes are not defined in the SC IOD, this column is essentially undefined. 2. These attributes are typically part of the VOI LUT Module, which is optional and not supported. These

are calculated and sent for the convenience of a Display Workstation. Window_Width = 2 (Bits_Stored); Window_Center = Window_Width/2.

3.1.6 SOP Specific Conformance to Print SOP Classes (LINX 3.0 Print Client) The LINX 3.0 DICOM Print Client supports various printer types that are each defined by a unique set of configurable attributes. These configurable attributes appear in a model file for each DICOM printer type. This section describes the DIMSEs and supported attributes for the various DICOM Print SOPs and includes the particular attributes that are configurable via a LINX model file.

3.1.6.1 SOP Specific Conformance to Basic Film Session SOP Class

Name Usage Description N_CREATE M Creates the film session N_SET M Not used N_DELETE M Deletes the film session N_ACTION U Not used

Table 3.20 Basic Film Session SOP Class: Supported DIMSE Services. Attribute Name (Tag) Possible Values Model File Entry Comment



Attribute Name (Tag) Possible Values Model File Entry Comment NUMBER OF COPIES (2000,0010)

1-99

HIGH MED

PRINT PRIORITY (2000,0020)

LOW

PAPER BLUE FILM

MEDIUM TYPE (2000,0030)

CLEAR FILM

X

FILM DESTINATION (2000,0040)

Not Used

FILM SESSION LABEL (2000,0050)

64 characters max.

MEMORY ALLOCATION (2000,0060)

Not Used

Table 3.21 Basic Film Session SOP Class: Supported Attributes.

3.1.6.2 SOP Specific Conformance to Basic Film Box SOP Class

Name Usage Description N_CREATE M Creates the film session N_SET U Not used N_DELETE M Deletes the film session N_ACTION M Prints the film box

Table 3.22 Basic Film Box SOP Class: Supported DIMSE Services.

Attribute Name (Tag) Possible Values Model File Entry Comment STANDARD\C,R ROW\R1,R2,R3… COL\C1,C2,C3… SLIDE

IMAGE DISPLAY FORMAT (2010,0010)

SUPERSLIDE

X

ANNOTATION DISPLAY FORMAT ID (2010,0030)

0-12 Result depends on PSC Server support. Indicates number of Annotation Boxes in the Film Box.

PORTRAIT FILM ORIENTATION (2010,0040) LANDSCAPE

X

8” x 10” LETTER 10” x 12” A3 10” x 14” LEGAL 11” x 14” 14” x 17” SUPER_A4

FILM SIZE ID (2010,0050)

24cm x 30cm

Internal LINX paper size will be mapped to the closest fit DICOM FILM SIZE ID. If ANY LINX paper size selected, the DICOM Basic Film Session Attribute MEDIUM TYPE will be set to “PAPER”

A4 REPLICATE BILINEAR CUBIC

MAGNIFICATION TYPE (2010,0060)

NONE

X

SMOOTHING TYPE (2010,0080)

Not Used



Attribute Name (Tag) Possible Values Model File Entry Comment BLACK WHITE

BORDER DENSITY (2010,0100)

numeric, OD x 100(ex. 1.5 OD = 150)

X

EMPTY IMAGE DENSITY (2010,0110)

Not used

MIN DENSITY (2010,0120)

numeric, OD x 100 X

MAX DENSITY (2010,0130)

numeric, OD x 100 X

YES TRIM (2010,0140) NO

If any image in a film box requires trim, all will get trim.

CONFIG. INFORMATION (2010,0150)

CSxxx X xxx = Code Value, settings obtained from SCPs

REF. FILM SESSION SEQ. (2010,0500)

REF. IMAGE BOX SEQ. (2010,0510)

REF. ANNOTATION BOX SEQ. (2010,0520)

Table 3.23 Basic Film Box SOP Class: Supported Attributes.

3.1.6.3 SOP Specific Conformance to Basic Image Box SOP Class

Name Usage Description N_SET M Updates an image box in a previously created film box.

Table 3.24 Basic Film Image Box SOP Class: Supported DIMSE Services.

Attribute Name (Tag) Possible Values Comment IMAGE POSITION (2020,0010)

0,1,2…

NORMAL Pixels are printed as by PHOTOMETRIC INTERPRETATION POLARITY (2020,0020) REVERSE Pixels are printed opposite of PHOTOMETRIC INTERPRETATIONPREFORMATTED GRAYSCALE IMAGE SEQUENCE (2020,0110)

>SAMPLES PER PIXEL (0028,0002)

1 Indicates 1 color plane.

>PHOTOMETRIC INTERPRETATION (0028,0004)

MONOCHROME2 Means min. pixel in black

>ROWS (0028,0010)

nnn Number of lines in image

>COLUMNS (0028,0011)

nnn Number of pixels in line

>PIXEL ASPECT RATIO (0028,0034)

rrr\ccc Row\Column



Attribute Name (Tag) Possible Values Comment >BITS ALLOCATED (0028,0100)

8,16

>BITS STORED (0028,0101)

8,12

>HIGH BIT (0028,0102)

7,11

>PIXEL REPRESENTATION (0028,0103)

0000 Indicates unsigned integer

>PIXEL DATA (7FE0,0010)

000-FFF (hex) The actual pixel data stream

REPLICATE BILINEAR CUBIC


NONE

Will override corresponding Film Box attribute


Not used

REQUESTED IMAGE SIZE (2020,0030)

Not used

REFERENCED OVERLAY SEQ (0008,1130)

Not used

Table 3.25 Basic Grayscale Image Box SOP Class: Supported Attributes.

3.1.6.4 SOP Specific Conformance to Annotation Box SOP Class


Table 3.26 Annotation Box SOP Class: Supported DIMSE Services.

Attribute Name (Tag) Possible Values Model File Entry ANNOTATION POSITION (2030,0010)

1-12 X

TEXT STRING (2030,0020)

Text (max 64 characters) X

Table 3.27 Annotation Box SOP Class: Supported Attributes.

3.1.6.5 SOP Specific Conformance to Printer SOP Class

Name Usage Description N_EVENT_REPORT M Ignored N_GET U Retrieves an instance of a physical printer

Table 3.28 Printer SOP Class: Supported DIMSE Services.

The LINX 3.0 DICOM Print Client will attempt to display human readable text corresponding to various PRINTER_STATUS_INFO values that may be retrieved from the DICOM Print Server using an N-GET. The following table provides the mapping between these values and displayed text.



NOTE: If the DICOM Print Server sends a PRINTER_STATUS_INFO value that is not in the table, the LINX 3.0 Print Client will simply display that value as-is.

Printer Status Printer Status Info Displayed Text NORMAL NORMAL

SUPPLY EMPTY Supply magazine is empty SUPPLY LOW Media supply is low RECEIVER FULL Receive magazine is full FILM JAM A film jam occurred NO SUPPLY MGZ No supply magazine NO RECEIVE MGZ No receive magazine REQ MEDIA UNAVAI Requested media unavailable PRINTER OFFLINE Printer is offline PRINTER INIT Printer is initializing PROC DOWN Film processor down PROC INIT Film processor initializing CHECK MAGAZINE Check printer magazine EXPOSURE FAILURE Printer exposure failure COMMUNICAT ERROR Printer communication error COVER OPEN Printer cover open MECH DOWN Printer mechanical failure ELEC DOWN Printer electrical failure CHECK PRINTER Check printer

WARNING

(Anything else) (Anything else) EXPOSURE FAILURE Printer exposure failure CALIBRATION ERROR Calibration error PRINTER DOWN Printer is down

FAILURE

(Anything else) (Anything else)

Table 3.29 PRINTER_STATUS_INFO: Attribute Values for Printer Module.

3.1.6.6 SOP Specific Conformance to PrintJob SOP Class

Name Usage Description N_EVENT_REPORT M Ignored N_GET U Retrieves an instance of a previously created print job

Table 3.30 Print Job Box SOP Class: Supported DIMSE Services.

The LINX 3.0 DICOM Print Client will attempt to display human readable text corresponding to various EXECUTION_STATUS_INFO values that may be retrieved from the DICOM Print Server using an N-GET. The following table provides the mapping between these values and displayed text.

NOTE: If the DICOM Print Server sends an EXECUTION_STATUS_INFO value that is not in table, the LINX 3.0 Print Client will simply display that value as-is.



Printer Status Printer Status Info Displayed Text DONE NORMAL

QUEUED Job is queued NO SUPPLY MGZ Supply magazine is missing NO RECEIVE MGZ Receive magazine is missing SUPPLY EMPTY Supply magazine is empty RECEIVER FULL Receiver magazine is full FILM JAM A film jam occurred

PENDING

(Anything else) (Anything else) ELEC SW ERROR Software error DISK ERROR Disk error INVALID PAGE DES Invalid sheet description NETWORK ERROR Network error FILM JAM A film jam occurred INSUFFIC MEMORY Insufficient memory IMAGE XFER ERROR Image transfer error SETUP ERROR Setup error PRINTER DOWN Printer is down

FAILURE

(Anything else) (Anything else) Table 3.31 EXECUTION_STATUS_INFO: Attribute Values for Print Job Module.

3.2 LINX 3.0 DICOM Print Server AE Specification The LINX 3.0 DICOM Print Server provides standard conformance to the following DICOM Version 3.0 SOP Classes as an SCP:

SOP Class Name UID Usage Verification SOP 1.2.840.10008.1.1 U Basic Grayscale Print Management Meta SOP 1.2.840.10008.5.1.1.9 M Basic Color Print Management Meta SOP 1.2.840.10008.5.1.1.18 U

Table 3.32 Supported Print SOP Classes.

NOTE: Table 3.33

Table 3.33 Mandatory SOP Classes in Grayscale Print Meta SOP Class.

and contain lists of the mandatory SOP Classes implied by the Print Meta SOP Classes.

Table 3.34

Table 3.34 Mandatory SOP Classes in Color Print Meta SOP Class.

SOP Class Name UID Usage Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 M Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 M Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4 M Basic Printer SOP Class 1.2.840.10008.5.1.1.16 M

SOP Class Name UID Usage Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 M Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 M Basic Color Image Box SOP Class 1.2.840.10008.5.1.4.1 M Basic Printer SOP Class 1.2.840.10008.5.1.1.16 M



The LINX 3.0 DICOM Print Server will support the following optional SOP classes if specifically configured to do so:

SOP Class Name UID Usage Print Job SOP Class 1.2.840.10008.5.1.1.14 U Basic Annotation Box SOP Class 1.2.840.10008.5.1.1.15 U

Table 3.35 Supported Optional Print SOP Classes.

3.2.1 Association Establishment Policies

3.2.1.1 General The LINX 3.0 DICOM Print Server (SCP) accepts associations from DICOM Print Clients (SCUs). If the maximum number of concurrent associations is already in use, then the association is refused. The association remains connected until the client disconnects; however, if the print job is complete and the association remains idle for a configurable period of time the association will be broken by the LINX 3.0 DICOM Print Server.

The maximum PDU size that can be received by the LINX 3.0 DICOM Print Server is configurable, with a default value of 16,384 (16K) bytes.

3.2.1.2 Number of Associations The LINX 3.0 DICOM Print Server can support multiple associations. The number of independent concurrent associations is configurable up to a maximum of four on the LINX 3.0 486 platform, and ten on the iiSYS pacLINX Dell platform.

3.2.1.3 Asynchronous Nature With the exception of sending N-EVENT-REPORTS to a DICOM Print Client, the LINX 3.0 DICOM Print Server does not support asynchronous operations.

3.2.1.4 Implementation UID

3.2.1.5 Association Initiation Policy The LINX 3.0 DICOM Print Server does not initiate associations.

3.2.2 Association Acceptance

3.2.2.1 Association Acceptance by Real-World Activity After an association is established, the LINX 3.0 DICOM Print Server will accept print jobs from the DICOM Print Client. Each print job normally consists of the following steps: >

>

>

>

The client may request the status of the printer by sending N-GET (Printer SOP instance) and the server returns the current instance of the Printer SOP Class. The client requests the server to N-CREATE a Film Session SOP instance. The server returns the Film Session SOP instance UID. For each film to be printed as part of the Film Session, the client requests the server to N-CREATE a Film Box SOP instance containing the appropriate number of Image Box SOP instances and, optionally, Annotation Box SOP instances. The server returns the appropriate SOP instance UIDs to the client. For each image to be printed as part of a Film Box, the client requests the server to N-SET (update) the appropriate Image Box with the image information. This causes the transfer of the image and pixel data from the client to the server. For each annotation box to be printed as part of a Film Box, the client requests the server to N-SET (update) the appropriate Annotation Box with text information.



>

>

>

If the sheet to be printed contains color images, the print client may negotiate for the Basic Color Print Management SOP Class. The LINX 3.0 DICOM Print Server will accept the proposed Basic Color Print Management SOP Class. If a color printer is attached to the Called AE, color images will be sent to the printer. If a grayscale printer is attached to the Called AE, and the images are converted to grayscale on output. Once all the images have been transferred, the client requests the server to N-ACTION (Print) the Film Box. This causes the film to be printed in an uncollated fashion. The LINX 3.0 Print Server does not currently support an N-ACTION (Print) on the Film Session (printing of collated sheets) but will in a future release. The LINX 3.0 Print Server will send the instance of the Print Job SOP Class or the Printer SOP Class in response to client requests using the N-GET DIMSE as long as the association is active. The LINX 3.0 Print Server will send N-EVENT-REPORTs to the DICOM Print Client if configured to do so.

3.2.2.2 Presentation Context Acceptance Criteria The LINX 3.0 DICOM Print Server will accept association establishment, using one of the presentation contexts listed below:


Name UID Name List UID List Role Ext.

Neg.Verification SOP Class (Echo)

1.2.840.10008.1.1 DICOM Implicit VR Little Endian

1.2.840.10008.1.2 SCP None

Basic Grayscale Print Management MetaSOP


1.2.840.10008.1.2 SCP None

Basic Color Print Management MetaSOP


1.2.840.10008.1.2 SCP None

Print Job SOP 1.2.840.10008.5.1.14 DICOM Implicit VR Little Endian

1.2.840.10008.1.2 SCP None

Basic Annotation Box SOP 1.2.840.10008.5.1.15 DICOM Implicit VR Little Endian

1.2.840.10008.1.2 SCP None

Table 3.36 Supported Print Presentation Contexts.

3.2.3 SOP Specific Conformance (LINX 3.0 Print Server) The LINX 3.0 DICOM Print Server represents all of the printers (or output devices) that connect to the LINX 3.0 Networking System. Certain attributes that are valid for some printer destinations may not be valid for others. For example, some printers support 4 lines of text annotation, some support 2 lines, and others do not support any text annotation. The LINX 3.0 Print Server will utilize reasonable default values for any attribute which is not valid for a given destination and will, in general, always try to complete a print job rather than failing it. The attributes that are printer-dependent are noted in . Table 3.38

3.2.3.1 SOP Specific Conformance to Basic Film Session SOP Class

Name Usage Description N_CREATE M Creates the film session N_SET M Updates the film session N_DELETE M Deletes the film session N_ACTION U Not Supported (currently)

Table 3.37 Basic Film Session SOP Class: Supported DIMSE Services.



Attribute Name (Tag) Possible Values Printer Dependent Comment NUMBER OF COPIES (2000,0010)

1-99

HIGH MED


LOW

PAPER BLUE FILM

MEDIUM TYPE (2000,0030)

CLEAR FILM

X Only Agfa LP400 supports selection of this parameter-other LNS printers do not.

FILM DESTINATION (2000,0040)

Not used. The printers attached to LNS do not allow control of film destination.

FILM SESSION LABEL (2000,0050)

64 characters max.

MEMORY ALLOCATION (2000,0060)

Not used

Table 3.38 Basic Film Session SOP Class: Supported Attributes.

3.2.3.2 SOP Specific Conformance to Basic Film Box SOP Class

Name Usage Description N_CREATE M Creates the film box N_SET U Updates the film box N_DELETE M Deletes the film box N_ACTION M Prints the film box

Table 3.39 Basic Film Box SOP Class: Supported DIMSE Services.

Attribute Name (Tag) Possible Values Printer

Dependent (see below)

Comment

STANDARD\ C,R ROW\ R1,R2,R3,… COL\ C1,C2,C3,… SLIDE

IMAGE DISPLAY FORMAT (2010,0010)

SUPERSLIDE

X

ANNOTATION DISPLAY FORMAT ID (2010,0030)

1-12 Result depends on PSC Server support. Indicates the number of Annotation Boxes in the Film Box.

MAX DENSITY (2010,0130)

Numeric, OD times 100 X

PORTRAIT FILM ORIENTATION (2010,0040) LANDSCAPE

X

TRIM (2010,0140)

CONFIG. INFORMATION (2010,0150)

CSxxx X xxx = Code Value (see Section )

REF. FILM SESSION SEQ. (2010,0500)

REF. IMAGE BOX SEQ. (2010,0510)



Attribute Name (Tag) Possible Values Printer

Dependent (see below)

Comment

REF. ANNOTATION BOX SEQ. (2010,0520)

Optional SOP Class

8X10IN 10X12IN 10X14IN 11X14IN 14X17IN

FILM SIZE ID (2010,0050)

24CMX30CM

X Provided the DICOM Basic Film Session Attribute MEDIUM TYPE is "PAPER", the DICOM FILM SIZE will be mapped internally to the closest fit LINX paper size. A DICOM FILM SIZE ID of "8X10IN" will be mapped internally to paper size "LETTER", "10X12IN" to paper size "A3", "10X14IN" to paper size "LEGAL", 14X17IN" to paper size "SUPER_A4", and "24CMX30CM" to paper size "A4". Any other DICOM FILM SIZE ID will be mapped to the default paper size of "LETTER". If the DICOM Basic Film Session Attribute MEDIUM TYPE is "BLUE FILM" or "CLEAR FILM", the DICOM FILM SIZE ID sizes supported are: "8X10IN", "10X12IN", "11X14IN", and "14X17IN". Any other DICOM FILM SIZE ID will be mapped to the default film size of "14X17IN".



NONE

X


Not Used

BORDER DENSITY (2010,0100)

BLACK WHITE Numeric, OD times 100 (1.5 OD = 150)

X

EMPTY IMAGE DENSITY (2010,0110)

Not Used.

MIN DENSITY (2010,0120)

Numeric, OD times 100 X

Table 3.40 Basic Film Box SOP Class: Supported Attributes.

Configuration Information Attribute

The DICOM Standard for Print SOP classes lacks separate attributes for both a Contrast Setting and LUT Select Code. Therefore, the LINX 3.0 DICOM Print Server interprets the DICOM Configuration Information attribute in a way that allows both Contrast Setting and LUT Select Code to be conveyed to physical destination printers that utilize both, such as the Agfa LP400. The CSxxx field is parsed in the following manner: > The lower “nibble” (values 0 to 15) of the number “xxx” is mapped to a contrast setting in the range of

0 to 15; the rest of “xxx” is shifted right by four bits and that value is mapped to a numeric LP400 LUT Select Code. For example, CS056 maps to LUT Select Code = 3 and a Contrast Setting = 8 (which are default settings for the LP400). To calculate the value of CSxxx for a Sterling LP400 use the formula: • (LUT_Select_Code * 16) + Contrast_Setting

Other LNS printers (ex. 3M Lasers) do not utilize LUT Select Codes. Therefore, the values CS000



through CS015 are available to designate curve/contrast settings for these printers.

The following rules apply to the CSxxx codes: > >

If only one CSxxx code is sent, it will be applied to all images on the sheet. If multiple CSxxx codes are sent, they will be matched up and applied to images in the order in which the images are N-SET. Codes should not be sent for blank images.

The following table lists the specific parameters and their permissible values for each LINX Laser Printer that may be associated with a LINX Called AE:

DICOM Parameter (Tag) LINX Printing Device Parameter LINX LP400 3M 3M

Sheet Formats of Images 11X14

11X14

14X17

14X17

8X 10

8X 10

14X 17

14X17

14X17

14X17IMAGE DISPLAY

FORMAT (2010,0010) N-up Col x Row P L P L P L P L P L STANDARD\1,1 1up 1x1 X X X X X X X X X X STANDARD\1,2 2up 1x2 X X X X X X X X STANDARD\2,1 2up 2x1 X X X X X X X X STANDARD\2,2 4up 2x2 X X X X X X X X X X STANDARD\2,3 6up 2x3 X X X X X X X X X X STANDARD\2,4 8up 2x4 X X X X X STANDARD\3,2 6up 3x2 X X X X X X STANDARD\3,3 9up 3x3 X X X X X X X X STANDARD\3,4 12up 3x4 X X X X X X X STANDARD\3,5 15up 3x5 X X X STANDARD\4,2 8up 4x2 X X X STANDARD\4,3 12up 4x3 X X X STANDARD\4,4 16up 4x4 X X X X X X STANDARD\4,5 20up 4x5 X X X STANDARD\4,6 24up 4x6 X STANDARD\5,3 15up 5x3 STANDARD\5,4 20up 5x4 X STANDARD\6,4 24up 6x4 X STANDARD\8,5 40up 8x5 STANDARD\8,6 48up 8x6 STANDARD\10,8 80up 10x8 ROW\3,3,1 3x2 over 1x1 X X X X ROW\1,3,3 1x1 over 3x2 X X ROW\4,4,1 4x2 over 1x1 X X X X ROW\1,4,4 1x1 over 4x2 X X X X ROW\3,3,3,2 3x3 over 3x1 X X X X ROW\2,3,3,3 2x1 over 3x3 X X ROW\4,4,4,2 4x3 over 2x1 X X X X ROW\2,4,4,4 2x1 over 4x3 X X X X COL\C1,C2,C3,… Mapped as sparse standard formats SLIDE 12up 3x4 X X X X X X X X X X SUPERSLIDE 12up 3x4 X X X X X X X X X X

Table 3.41 Printer Dependent Parameters within the Film Box SOP.

3.2.3.3 SOP Specific Conformance to Basic Image Box SOP Class

Name Usage Description




Table 3.42 Basic Image Box SOP Class: Supported DIMSE Services. Attribute Name (Tag) Possible Values Comment

IMAGE POSITION (2020,0010)

1,2…

NORMAL Pixels are printed as by PHOTOMETRIC INTERPRETATION POLARITY (2020,0020) REVERSE Pixels are printed opposite of PHOTOMETRIC

INTERPRETATION REQUESTED IMAGE SIZE (2020,0030)

numeric Defined as the length in mm of an image row (used for true size printing).

PREFORMATTED GRAYSCALE IMAGE SEQUENCE (2020,0110)


1 Indicates 1 color plane


MONOCHROME2 MONOCHROME2 means min. pixel is black

>ROWS (0028,0010)

nnn Number of lines in image (See maximums below)

>COLUMNS (0028,0011)

nnn Number of pixels in line (See maximums below)


rrr/ccc Row\Column

>BITS ALLOCATED (0028,0100)

8, 16


8, 12

>HIGH BIT (0028,0102)

7, 11


0000 Indicates unsigned integer.


000-FFF (hex) The actual pixel data stream.


MAGNIFCATION TYPE (0028,0060)

NONE

Will override corresponding Film Box attribute.


Not Used

REFERENCED OVERLAY SEQUENCE (0008,1130)

Not Used

Table 3.43 Basic Grayscale Image Box SOP Class: Supported Attributes.

Attribute Name (Tag) Possible Values Comment IMAGE POSITION (2020,0010)

1,2…

NORMAL Pixels are printed as by PHOTOMETRIC INTERPRETATION

POLARITY (2020,0020)

REVERSE Pixels are printed opposite of PHOTOMETRIC INTERPRETATION



Attribute Name (Tag) Possible Values Comment REQUESTED IMAGE SIZE (2020,0030)

numeric Defined as the length in mm of an image row (used for true size printing).

PREFORMATTED COLOR IMAGE SEQ (2020,0111)


3 Indicates 3 color planes


RGB RGB describes red, green and blue color planes with min. value = min. color intensity

>PLANAR CONFIGURATION (0028,0006)

0001 Indicates R1,R2,…, G1,G2,…B1,B2,…

>ROWS (0028,0010)

nnn Number of lines in image (See maximums below)

>COLUMNS (0028,0011)

nnn Number of pixels in line (See maximums below)


rrr/ccc Row\Column

>BITS ALLOCATED (0028,0100)

8


8

>HIGH BIT (0028,0102)

7 Indicates which bit is the MSB


0000 Indicates unsigned integer.


000-FFF (hex) The actual pixel data stream.


MAGNIFCATION TYPE (0028,0060)

NONE

Will override corresponding Film Box attribute.


Not Supported

REFERENCED OVERLAY SEQ (0008,1130)

Not Supported

Table 3.44 Basic Color Image Box SOP Class: Supported Attributes.

Since LNS handles a variety of physical output devices, the maximum permissible image size depends on the printer selected (and possibly on other printer configuration selections such as memory, borders, etc.). The following table gives general limits for image sizes for the printers that may be connected to a LINX DICOM Print Server Called AE:

Attribute Name (Tag) LP400-14x17 LP400-8x10 3M-14x17 COLUMNS (0028,0011) (Number of pixels in image line)

5250 2048 2048

ROWS (0028,0010) (Number of lines in range)

6374 3072 2048

Table 3.45 General Image Size Limits for LNS Printers.

3.2.3.4 SOP Specific Conformance to Annotation Box SOP Class

Name Usage Description



Name Usage Description N_SET M Updates an annotation box in a previously created film box.

Table 3.46 Annotation Box SOP Class: Supported DIMSE Services.

Attribute Name (Tag) Possible Values Printer Dependent

ANNOTATION POSITION (2030,0010)

1-12 X

TEXT STRING (2030,0020)

Text (max 64 characters) X

Table 3.47 Annotation Box SOP Class: Supported Attributes.

A single annotation display format is supported for all printers capable of printing text-on-film. The format describes a text area consisting of 4 lines, each of which is the width of the film. Three columns of annotation positions are available. The left-most column will be left justified text. The center column will be center-justified text. The right-most column will be right-justified text. The annotation position sequence is in row-major order (from left-to-right, top-to-bottom). For 2 line annotation, only the first 2 lines are used.

The numbers inside the boxes below indicate the annotation position IDs that are available:

1 2 3 4 5 6 7 8 9 10 11 12

Additional rules: > >

>

The maximum number of characters for any annotation position is 64. The sum of the number of characters for all the used annotation positions on a row must be less than or equal to 124. The client is responsible for ensuring that adjacent used annotation positions on a row do not overlap. If an overlap occurs, no warnings or errors will be given.

An example is shown below:

LINX Hospital, Wilmington, DE Sheet 76 of study 132 Captured 09/12/95 2:31pm Set 1 of 1 CT ROOM #1 Printed 09/12/95 2:32pm

In this example, annotation positions 1, 3, 5, 10, 11, and 12 are blank. Position 2 contains the string “LINX Hospital, Wilmington, DE”. Position 7 contains the string “Set 1 of 1”, etc.

3.2.3.5 SOP Specific Conformance to Printer SOP Class

Name Usage Description N_EVENT_REPORT M Sends an instance of a Printer SOP to a DICOM Print Client. N_GET M Retrieves an instance of a Printer SOP for a DICOM Print Client.

Table 3.48 Printer SOP Class: Supported DIMSE Services.

Attribute Name (Tag) Possible Values Comment PRINTER STATUS NORMAL



Attribute Name (Tag) Possible Values Comment WARNING FAILURE

PRINTER STATUS INFO (2110,0020)

16 characters max. (See ) Depends on PRINTER STATUS.

PRINTER NAME (2110,0030)

16 characters max. LINX printer alias.

MANUFACTURER (0008,0070)

16 characters max.

MANUFACTURER MODEL NAME (0008,1090)

16 characters max. "LINX NS400"

DEVICE SERIAL NUMBER (0018,1000)

r_id of LINX NCU

SOFTWARE VERSION (0018,1000)

16 characters max. Current LINX version.

DATE LAST CALIBRATION (0018,1200)

Not Supported (Field not returned)

TIME LAST CALIBRATION (0018,1201)

Not Supported (Field not returned)

(2110,0110)

Table 3.50

Table 3.50 PRINTER_STATUS_INFO: Attribute Values for Printer Module.

Table 3.49 Printer SOP Class: Supported Attributes.

Printer Status Printer Status Info Description NORMAL NORMAL Normal operation. WARNING SUPPLY EMPTY Supply magazine is empty. SUPPLY LOW Media supply is low. RECEIVER FULL Receive magazine is full. FILM JAM A film jam occurred. NO SUPPLY MGZ No supply magazine. NO RECEIVE MGZ No receive magazine. REQ MEDIA UNAVAI Required media unavailable. PRINTER OFFLINE Printer is offline. PRINTER INIT Printer is initializing. PROC DOWN Film processor down. PROC INIT Film processor initializing. CHECK MAGAZINE Check printer magazine. EXPOSURE FAILURE Printer exposure failure. COMMUNICAT ERROR Printer communication error. COVER OPEN Printer cover open. MECH DOWN Printer mechanical failure. ELEC DOWN Printer electrical failure. CHECK PRINTER Check printer. FAILURE EXPOSURE FAILURE Printer exposure failure. CALIBRATION ERROR Calibration error. PRINTER DOWN General printer failure.

3.2.3.6 SOP Specific Conformance to PrintJob SOP

Name Usage Description N_EVENT_REPORT M Sends an instance of a Print Job SOP to a DICOM Print Client.



Name Usage Description N_GET M Retrieves an instance of a Print Job SOP for a DICOM Print Client.

Table 3.51 Print Job SOP Class: Supported DIMSE Services.

Attribute Name (Tag) Possible Values Comment PENDING DONE

EXECUTION STATUS (2100,0020)

FAILURE

EXECUTION STATUS INFO (2100,0030)

16 characters max. (See ) Depends on EXECUTION STATUS.

HIGH MED


LOW

CREATION DATE (2100,0020)

yyyymmdd Date of print job creation.

CREATION TIME (2110,0050)

hhmmss Time of print job creation--24 hour clock assumed.

PRINTER NAME (2110,0030)

16 characters max. LINX printer alias.

ORIGINATOR (2100,0070)

16 characters max. "Calling" AE Title.

Table 3.53

Table 3.53 EXECUTION_STATUS_INFO: Attribute Values for Print Job Module.

Table 3.52 Print Job SOP Class: Supported Attributes.

Printer Status Printer Status Info Description DONE NORMAL No alarm (print job complete) PENDING QUEUED No alarm (print job queued) NO SUPPLY MGZ Supply magazine is missing. NO RECEIVE MGZ Receive magazine is missing. SUPPLY EMPTY Supply magazine is empty. RECEIVER FULL Receive magazine is full. FILM JAM A film jam occurred. FAILURE ELEC SW ERROR Software error. DISK ERROR Disk error. INVALID PAGE DES Invalid sheet description. NETWORK ERROR Network error. FILM JAM A film jam occurred. INSUFFIC MEMORY Insufficient memory. IMAGE XFER ERROR Image transfer error. SETUP ERROR Setup error. PRINTER DOWN Printer is down.

3.2.3.7 SOP Specific Conformance to Verification SOP Class The Verification SOP Class is a feature used for network diagnostic purposes. The Verification SOP Class consists of C-ECHO DIMSE-C Service. The Verification SOP Class is supported by the LINX 3.0 DICOM Print Server.



4 COMMUNICATION PROFILES

4.1 TCP/IP Stack The LINX 3.0 DICOM Client and Server provide DICOM V3.0 TCP/IP Network Communication Support as defined in Part 8 of the DICOM Standard.

4.2 Physical Media Support LINX 3.0 supports DICOM over Ethernet and token ring networks. DICOM using IP over token ring is only valid in interoperability situations in which a legacy LINX system at 2.8.1 and above needs to communicate with the LINX 3.0 system.

5 EXTENSIONS/SPECIALIZATIONS/ PRIVATIZATIONS The LINX 3.0 DICOM Storage Clients do not define any private elements.

6 CONFIGURATION

6.1 LINX 3.0 DICOM Storage Client Configuration The following items are configurable for an individual LINX 3.0 DICOM Storage Client from within LNS.

NOTE: The items with an asterisk (*) will have the same value for all storage clients configured on a given node.

Parameter Description Range Application Entities (Called AEs)

Application Entities representing physical devices can be configured at installation. More than one application entity can be assigned to a physical device.

Remote Host/IP Address

A valid IP address and hostname associated with the Storage SCP and its Application Entity.

Remote Port Number A valid port number to be used when establishing TCP/IP connection to the Storage SCP. Range = 1 to 32767

Calling AE Title* Calling Application Entity Title of the Presentation Address for this instance of the Storage Client.

Local Hostname* For logging purposes only, the local hostname portion of the Presentation Address. This does not travel across the DICOM association.

Max PDU size* 1024 to 4096 Association Timeout Period*

Number of seconds following the transmission of an image before the client will release an open association. 0 = Immediately release association, i.e. do not reuse them. -1 = Never release association (unless a new destination is specified, or an error has occurred).1..32000 = Wait this many seconds before automatically releasing the last association.

Table 6.1 LINX 3.0 DICOM Storage Client Configuration.

6.2 LINX 3.0 DICOM Print Client Configuration The following items are configurable for an individual LINX 3.0 DICOM Print Client from within LNS:

Parameter Description Range



Parameter Description Range Printer Type The specific printer type that the LINX DICOM Print Client will communicate with. This is chosen

by selecting a LINX DICOM Imager Control Channel at configuration and affects some parameters and ranges of values available to send to the DICOM Print Server.

Application Entities (Called AEs)

Application Entities Representing physical devices can be configured at installation. More than one application entity can be assigned to a physical device.

Remote Host/IP Address

A valid IP address and hostname associated with the physical printer and its Application Entity.

Remote Port Number A valid port number to be used when establishing TCP/IP connection to the physical printer Range = 1 to 32767

Calling AE Title Calling Application Entity Title of the Presentation Address for this instance of the Print Client. Local Hostname For logging purposes only, the local hostname portion of the Presentation Address. This does

not travel across the DICOM association. Max PDU size 1K to 16K Association Control The print client can be configured to control associations by:

- Requesting the use of the optional Annotation Box SOP class - Requesting the use of the optional Print Job SOP class.

Print Job Poll Period This parameter controls the number of seconds between the issuing of N-GETs by the LINX Print Client after a successful N-ACTION (Print) for either the Printer SOP or Print Job SOP Class (if negotiated).

Print Complete Timeout Period

Only if the Print Job SOP is negotiated, this parameter controls the total amount of time after a successful N-ACTION (Print) that the LINX Print Client will poll the Print Job SOP before releasing the association. -1 = Wait indefinitely 0 = Immediate timeout 1 to 32767 (seconds) timeout period

Association Timeout Period

This parameter controls the amount of time that the client will keep an association active after receiving a print complete. -1 = Never automatically release association (unless a new destination is specified, or an error has occurred) 0 = Immediate timeout (default) 1 to 32767 (seconds) timeout period.

Table 6.2 LINX 3.0 DICOM Print Client Configuration.

6.3 LINX 3.0 DICOM Print Server Configuration The following items are configurable by service for an individual LINX 3.0 DICOM Print Server from within the LINX 3.0 Networking System.

Parameter Description Range

Local User Record (Called AE Titles)

Application Entities which will be called by a DICOM Print Client. These Called AE Titles are then associated with physical output devices on the LINX Network using a keypad configuration procedure.

TCP Port The TCP port on which the LINX Print Server will listen for incoming DICOM Print Association requests. Range = 1 to 32767

IP Address (NIC Driver)

The IP Address of the LINX Print Server.

Max PDU size 1K to 16K (default = 16K) Association Timeout Period

Maximum number of seconds that the LINX Print Server will allow a client to maintain an association after sending confirmation of a print complete. -1 = Never release association, unless a new destination is specified, or an error has occurred. 0 = Time-out immediately 1 to 3600 (seconds) = Seconds to wait before releasing the association.



Table 6.3 LINX 3.0 DICOM Print Server Configuration.

6.4 Configuration Defaults The LINX 3.0 DICOM Clients and Print Server are setup with reasonable default settings for the configurable parameters above.

7 ACRONYMS AND ABBREVIATIONS ACR American College of Radiology AE Application Entity ANSI American National Standards Institute C or c Column CEN TC251 Comité Européen de Normalisation-Technical Committee 251-Medical Informatics CR Computed Radiography CS Contrast Setting CT Computed Tomography DE Delaware DICOM Digital Imaging and Communications in Medicine DIMSE DICOM Message Service Element DIMSE-C DICOM Message Service Element-Composite E Error HL7 Health Level 7 IEEE Institute of Electrical and Electronics Engineers IOD JIRA Japanese Industry Radiology Apparatus L Landscape LNS LINX Networking System LP Laser Printer LUT Look Up Table M Mandatory NCU NEMA National Electrical Manufacturers Association OD Optical Density P Portrait PDU Protocol Data Unit PIM Patient Information Management PSC Print Service Class R or r Row RGB Red, Green, Blue SC Secondary Capture SCP Service Class Provider SCU Service Class User SID SOP Service-Object Pair TCP/IP Transmission Control Protocol/Internet Protocol U User Option UID Unique Identifier VOI VR Value Representation



W Warning XNI

Documents

HEALTHCARE DICOM Conformance Statement