Imagepilot

IMAGEPILOT
Important Notes
- Konica Minolta Medical & Graphic, Inc. retains copyright of this manual.
- The contents of this manual may be subject to change without prior notice.
- Unauthorized reproduction of any part of this manual is prohibited.
- Konica Minolta Medical & Graphic, Inc. will not be responsible for any damage or loss caused or
claims from a third party resulting from operating this product.
Windows is a registered trademark of Microsoft Corporation in the United States and other countries. All
other trademarks or registered trademarks are property of their respective owners. ® and TM marks are
not indicated in this manual. Copyright © Konica Minolta Medical & Graphic, Inc. 2006. All Rights
Reserved.
DICOM Conformance Statement
Revision History
Date Version Edited by Description
xx/05/2007 Ver.1.00 KONICA MINOLTA Version for Draft Text
MEDICAL & GRAPHIC, INC
i
CONFORMANCE STATEMENT OVERVIEW

This document “Conformance Statement” describes the compatibility of DICOM Interface for REGIUS Unitea with DICOM
PS3.2.
Services provided by REGIUS Unitea are listed below.
Table1-1: NETWORK SERVICES
User of Service Provider of Service

SOP Classes
(SCU) (SCP)
Storage
CR(Computed Radiography) Image Yes Yes
CT Image Information Object Storage Yes Yes
US Multi-Frame Image Storage Yes Yes
MR Image Information Object Storage Yes Yes
US Image Storage Yes Yes
SC (Secondary Capture) Image Storage Yes Yes
VL Endoscopic Image Storage Yes Yes
VL Microscopic Image Storage Yes Yes
VL Slide-Coordinates Microscopic Image Storage Yes Yes
VL Photographic Image Storage Yes Yes
Grayscale Softcopy Presentation State Storage Yes Yes
Storage Commitment
Storage Commitment Push Model No No
Print Management
Basic Grayscale Print Management Meta Yes No
Presentation LUT Yes No
Workflow Management
Modality Worklist Information Model-Find No No
Modality Performed Procedure Step No No
ii
Table of Contents
Important Notes
Revision History...........................................................................................................................i
CONFORMANCE STATEMENT OVERVIEW............................................................... ii
1 　 INTRODUCTION............................................................................. 1
1.1 　 AUDIENCE ...............................................................................................................1
1.2 　 REMARKS ................................................................................................................1
1.3 　 DEFINITIONS, TERM AND ABBREVIATIONS ........................................................1
2 　 NETWORKING................................................................................ 2
2.1 　 IMPLEMENTATION MODEL ....................................................................................2
2.1.1 　 Application Data Flow .................................................................................................... 2
2.1.2 　 Function Definition of AEs.............................................................................................. 3
2.1.2.1 　 Function Definition of STORAGE-SCP Application Entity .................................. 3
2.1.2.2 　 Function Definition of QUERY/RETRIEVE-SCP Application Entity .................... 3
2.1.2.3 　 Function Definition of PRINT MANAGE-SCP Application Entity......................... 3
2.1.3 　 Sequencing of Real-World Activities .............................................................................. 3
2.2 　 AE SPECIFICATIONS ..............................................................................................4
2.2.1 　 STORAGE-SCP Application Entity ................................................................................ 4
2.2.1.1 　 SOP Class .......................................................................................................... 4
2.2.1.2 　 Association Policies ............................................................................................ 5
2.2.1.2.1 　 General .................................................................................................. 5
2.2.1.2.2 　 Number of Associations......................................................................... 5
2.2.1.2.3 　 Asynchronous Nature ............................................................................ 5
2.2.1.2.4 　 Implementation Identifying Information.................................................. 5
2.2.1.3 　 Association Initiation Policy ................................................................................ 6
2.2.1.4 　 Association Acceptance Policy ........................................................................... 6
2.2.1.4.1 　 Activity-Storage Image Requested by an External Peer AE .................. 6
2.2.1.4.1.1 　 Description and Sequencing of Activity ............................................. 6
2.2.1.4.1.2 　 Accepted Presentation Contexts ....................................................... 6
2.2.1.5 　 STORAGE-SCU Application Entity ..................................................................... 8
2.2.1.5.1 　 SOP Class ............................................................................................. 8
2.2.1.6 　 Association Establishment Policies..................................................................... 9
2.2.1.6.1 　 General .................................................................................................. 9
2.2.1.6.2 　 Number of Associations......................................................................... 9
2.2.1.6.3 　 Asynchronous Nature ............................................................................ 9
2.2.1.6.4 　 Implementation Identifying Information.................................................. 9
2.2.1.7 　 Association Initiation Policy .............................................................................. 10
2.2.1.7.1 　 Activity-Send Image Requested by an External Peer AE .................... 10
2.2.1.7.1.1 　 Description and Sequencing of Activity ........................................... 10
2.2.1.7.1.2 　 Proposed Presentation Contexts ......................................................11
2.2.1.8 　 Association Acceptance Policy ..........................................................................11
2.2.2 　 Print MANAGE-SCU Application Entit ..........................................................................11
2.2.2.1 　 SOP Class .........................................................................................................11
2.2.2.2 　 Association Establishment Policies................................................................... 12
2.2.2.2.1 　 General ................................................................................................ 12
2.2.2.2.2 　 Number of Associations....................................................................... 12
2.2.2.2.3 　 Asynchronous Nature .......................................................................... 12
iii
2.2.2.2.4 　 Implementation Identifying Information................................................ 12

2.2.2.3 　 Association Initiation Policy .............................................................................. 12
2.2.2.3.1 　 Activity-Print Image Requested to an External Peer AE...................... 12
2.2.2.3.1.1 　 Description and Sequencing of Activity ........................................... 12
2.2.2.3.1.2 　 Proposed Presentation Contexts ..................................................... 13
2.2.2.3.1.3 　 SOP Specific Conformance for the Printer SOP Class .................... 14
2.2.2.3.1.3.1 　 Printer SOP Class Operations (N-GET) ....................................... 14
2.2.2.3.1.4 　 SOP Specific Conformance for the Film Session SOP Class .......... 14
2.2.2.3.1.4.1 　 Film Session SOP Class Operations (N-CREATE) ...................... 14
2.2.2.3.1.5 　 SOP Specific Conformance for the Presentation LUT SOP class ... 15
2.2.2.3.1.5.1 　 Presentation LUT SOP Class Operations (N-CREATE) ............... 15
2.2.2.3.1.6 　 SOP Specific Conformance for the Film Box SOP class ................. 16
2.2.2.3.1.6.1 　 Film Box SOP Class Operations (N-CREATE) ............................. 16
2.2.2.3.1.6.2 　 Film Box SOP Class Operations (N-ACTION) .............................. 16
2.2.2.3.1.7 　 SOP Specific Conformance for the Image Box SOP class .............. 17
2.2.2.3.1.7.1 　 Image Box SCP Class Operations (N-SET) ................................. 17
2.2.2.4 　 Association Acceptance Policy ......................................................................... 17
2.3 　 NETWORKING INTERFACE.................................................................................. 18
2.3.1 　 Supported Communications Stacks (parts8, 9)............................................................ 18
2.3.2 　 TCP/IP Stacks .............................................................................................................. 18
2.3.2.1 　 Physical Network Interface ............................................................................... 18
2.4 　 CONFIGURATION.................................................................................................. 18
2.4.1 　 AE Title/Presentation Address Mapping ...................................................................... 18
2.4.1.1 　 Local AE Titles .................................................................................................. 18
2.4.2 　 Parameters .................................................................................................................. 18
3 　 SUPPORT OF CHARACTER SETS ............................................. 19
4 　 SECURTIY .................................................................................... 19
4.1 　 ASSOCIATION LEVEL SECURTIY ........................................................................ 19
iv
DICOM Conformance Statement 1. INTRODUCTION
1. INTRODUCTION
1.1 AUDIENCE
This document is prepared for hospital staff, medical device suppliers and software engineers/implementers, presuming
they are familiar with DICOM Standard.
1.2 REMARKS
First of all, it should be noted that DICOM Standard itself does not guarantee interoperability of medical devices.
However, it allows with ease, implementing first validity verification of interoperating medical devices that support the
same DICOM Services.
“Conformance Statement” is prepared to help networking “ImagePilot” to other DICOM devices, and it is presumed that
the reader reads this document while referring to other documents describing DICOM Standard as well.
1.3 DEFINITIONS, TERM AND ABBREVIATIONS

AE Application Entity
CD-R Compact Disk Recordable
CR Computerized radiography
CT Computerized Tomography
DICOM Digital Imaging and Communications in Medicine
DVD-R DVD-Recordable
FSC File-Set Creator
FSR File-Set Reader
FSU File-Set Updater
IE Information Entity
IOD Information Object Definition
ISO International Standards Organization
MR Magnetic Resonance
PDU Protocol Data Unit
SC Secondary Capture
SCP Service Class Provider
SCU Service Class User
SOP Service-Object Pair
TCP/IP Transmission Control Protocol/Internet Protocol
UID Unique Identifier
US Ultrasound
VM Value Multiplicity
VR Value Representation
1
2. NETWORKING DICOM Conformance Statement
2. NETWORKING
2.1 IMPLEMENTATION MODEL

AE implemented in DICOM Interface for ImagePilot allows receiving and requesting Association to/from external AE
using DICOM Storage SCP/SCU Service Class.
2.1.1 Application Data Flow
2
DICOM Conformance Statement 2. NETWORKING
2.1.2 Function Definition of AEs
2.1.2.1 Function Definition of STORAGE-SCP Application Entity

KC_UNITEA_P001(:Default AE Title for STORAGE-SCP) runs as background process and becomes ready to
receive signal as soon as the system is started up.
KC_UNITEA_P001 operates as DICOM Storage Service Class SCP. KC_UNITEA_P001 starts reception
against C-STORE-RQ from external AE after accepting Association Establishment Request.
Completion of image transfer from external AE is defined as when the Association is released.
External AE from which the Association Request should be received and accepted is set in configuration.
2.1.2.2 Function Definition of QUERY/RETRIEVE-SCP Application Entity

KC_UNITEA_U001(:Default AE Title for STORAGE-SCU) runs as communication process and starts sending
the image using STORAGE-SCU Service after the Association Request to external AE is accepted.
External AE that should send Association Request is set in configuration.
2.1.2.3 Function Definition of PRINT MANAGE-SCP Application Entity

KC_PLNK5_SCU(:Default AE Title for PRINT MANAGE-SCU) runs as communication process and starts
hard copy transmission using N-CREATE-RQ after the Association Request to external AE is accepted.
External AE that should send Association Request is set in configuration.
2.1.3 Sequencing of Real-World Activities

Those AEs do not support Sequencing of Real-World Activities.
3
2.2 AE SPECIFICATIONS
2.2.1 STORAGE-SCP Application Entity

KC_UNITEA_P001 has been set as default for STORAGE-SCP AE Title in ImagePilot.
2.2.1.1 SOP Class

KC_UNITEA_P001 supports following DICOM V3.0 SOP Classes as an SCP.
SOP Class name SOP Class UID SCU SCP

CR (Computed Radiography) Image 1.2.840.10008.5.1.4.1.1.1 NO YES
CT Image Information Object Storage 1.2.840.10008.5.1.4.1.1.2 NO YES
US Multi-Frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 NO YES
MR Image Information Object Storage 1.2.840.10008.5.1.4.1.1.4 NO YES
US Image Storage 1.2.840.10008.5.1.4.1.1.6.1 NO YES
SC (Secondary Capture) Image Storage 1.2.840.10008.5.1.4.1.1.7 NO YES
VL Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1 NO YES
VL Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2 NO YES
VL Slide-Coordinates Microscopic Image 1.2.840.10008.5.1.4.1.1.77.1.3 NO YES
Storage
VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 NO YES
Grayscale Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.1 NO YES
4
2.2.1.2 Association Policies
2.2.1.2.1 General
KC_UNITEA_P001 starts receiving the image data after Association is established. AE Title and Port
No. from which the Association is accepted are set in configuration.
Application Context Name supports DICOM V3.0 SOP Class listed below.
Application Context Name 1.2.840.10008.3.1.1.1
2.2.1.2.2 Number of Associations

KC_UNITEA_P001 is capable of accepting Associations from maximum 5 external AEs including
Associations for different services at the same time. Parallel processing will be implemented for each AE
whose Association has been established.
Maximum number of simultaneous Associations 5
2.2.1.2.3 Asynchronous Nature

Asynchronous processing is not supported.
Maximum number of simultaneous Associations 1 (Not Configurable)
2.2.1.2.4 Implementation Identifying Information

Implementation Class UID Refer to description for Instance UID below
Implementation Version Name KC_UNITEA_X.XX
X.XX represents software version.
SOP Instance UID is defined as follows.

• 1.2.392.200036.9107.[DivCode].[Device].[Serial No.].[yyyymmdd].[hhmmss].[Unique No.]
Study Instance UID is defined as follows.
• 1.2.392.200036.9107.[DivCode].[11+Study No.]
Series Instance UID is defined as follows.
• 1.2.392.200036.9107.[DivCode].[Device].[Serial No.].[Study No.].[12+Series No.]
Notes） [DivCode] ： Section code 500

[Device] ： Device type of source 220
[Serial No.] ： Serial No. of the Device is specified.
[yyyymmdd] ： Date is specified.
[hhmmss] ： Time is specified.
[Study No.] ： Study ID
[Series No.] ： Series Number
[Unique No.] ： Unique No. internally issued by the Device is specified.
5
2.2.1.3 Association Initiation Policy

KC_UNITEA_P001 does not request Association.
2.2.1.4 Association Acceptance Policy
2.2.1.4.1 Activity-Storage Image Requested by an External Peer AE
2.2.1.4.1.1 Description and Sequencing of Activity

KC_UNITEA_P001 becomes stand-by as soon as the system is started up so that it can receive
request for Association from external AE. KC_UNITEA_P001 starts receiving images only after
accepting the Association.
KC_UNITEA_P001 shall release the Association when the image transfer is completed.
Registration of the image shall not be made if a request for release is not received.
Sequence of Image Storage requested from external AE in the above is described below.
1． External AE sends a request for Association to KC_UNITEA_P001.
2． External AE sends images to KC_UNITEA_P001.
3． External AE sends a request for release to KC_UNITEA_P001.
2.2.1.4.1.2 Accepted Presentation Contexts

KC_UNITEA_P001 is capable of accepting Presentation Contexts listed below.
Abstract Syntax
Extended
Name UID Role
Negotiation
CR Image Storage Service class 1.2.840.10008.5.1.4.1.1.1 SCP None
CT Image Information Object Storage 1.2.840.10008.5.1.4.1.1.2 SCP None
US Multi-Frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 SCP None
MR Image Information Object Storage 1.2.840.10008.5.1.4.1.1.4 SCP None
US Image Storage 1.2.840.10008.5.1.4.1.1.6.1 SCP None
SC (Secondary Capture) Image 1.2.840.10008.5.1.4.1.1.7 SCP None
Storage
VL Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1 SCP None
6
Abstract Syntax
Extended
Name UID Role
Negotiation
VL Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2 SCP None
VL Slide-Coordinates Microscopic 1.2.840.10008.5.1.4.1.1.77.1.3 SCP None
Image Storage
VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 SCP None
Grayscale Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.1 SCP None
Storage
KC_UNITEA_U001 supports following Transfer Syntax for Abstract Syntax mentioned above.
Transfer Syntax
Name List UID List
Implicit VR Little Endian 1.2.840.10008.1.2
Explicit VR Big Endian 1.2.840.10008.1.2.2
Explicit VR Little Endian 1.2.840.10008.1.2.1
JPEG Baseline (Process1) 1.2.840.10008.1.2.4.50
JPEG Extended (Process2 & 4) 1.2.840.10008.1.2.4.51
JPEG Lossless 1.2.840.10008.1.2.4.70
7
2.2.1.5 STORAGE-SCU Application Entity

KC_UNITEA_U001 has been set as default for STORAGE-SCU AE Title in ImagePilot.
2.2.1.5.1 SOP Class

KC_UNITEA_U001 supports following DICOM V3.0 SOP Classes as an SCP.

CR (Computed Radiography) Image 1.2.840.10008.5.1.4.1.1.1 YES NO
CT Image Information Object Storage 1.2.840.10008.5.1.4.1.1.2 YES NO
US Multi-Frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 YES NO
MR Image Information Object Storage 1.2.840.10008.5.1.4.1.1.4 YES NO
US Image Storage 1.2.840.10008.5.1.4.1.1.6.1 YES NO
SC (Secondary Capture) Image Storage 1.2.840.10008.5.1.4.1.1.7 YES NO
VL Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1 YES NO
VL Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2 YES NO
VL Slide-Coordinates Microscopic Image 1.2.840.10008.5.1.4.1.1.77.1.3 YES NO
Storage
VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 YES NO
Grayscale Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.1 YES NO
Storage
8
2.2.1.6 Association Establishment Policies
2.2.1.6.1 General
KC_UNITEA_U001 starts sending the image data after Association is established. AE Title and Port No.
from which the Association is accepted are set in configuration.
KC_UNITEA_U001 dose not accept Association Request from the external AEs.

KC_UNITEA_U001 is capable of sending Association Requests to maximum 5 external AEs including



• 1.2.392.200036.9107.[DivCode].[11+Study No.]

9
2.2.1.7.1 Activity-Send Image Requested by an External Peer AE

STORAGE-SCU of ImagePilot will be started up when the image is sent to the external AEs.
STORAGE-SCU Service requests Association to external AEs, and sends the image after the
request is accepted. Release will be made after the image transfer is completed.
Sequence of Image Transfer Request to the external AE in the above is described below.
1． KC_UNITEA_U001 sends Association Request to external AE.
2． KC_UNITEA_U001 sends the image requested by C-STORE Command of STORAGE SOP
Class.
3． KC_UNITEA_U001 sends Release Request to external AE.
10
2.2.1.7.1.2 Proposed Presentation Contexts

KC_UNITEA_U001 proposes following Presentation Contexts as necessary.
Abstract Syntax
Extended
Name UID Role
Negotiation
CR Image Storage Service class 1.2.840.10008.5.1.4.1.1.1 SCU None
CT Image Information Object Storage 1.2.840.10008.5.1.4.1.1.2 SCU None
US Multi-Frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 SCU None
MR Image Information Object Storage 1.2.840.10008.5.1.4.1.1.4 SCU None
US Image Storage 1.2.840.10008.5.1.4.1.1.6.1 SCU None
SC (Secondary Capture) Image 1.2.840.10008.5.1.4.1.1.7 SCU None
Storage
VL Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1 SCU None
VL Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2 SCU None
VL Slide-Coordinates Microscopic 1.2.840.10008.5.1.4.1.1.77.1.3 SCU None
Image Storage
VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 SCU None
KC_UNITEA_U001 supports following Transfer Syntax for Abstract Syntax mentioned above.
Transfer Syntax
Name List UID List
Explicit VR Big Endian 1.2.840.10008.1.2.2
Explicit VR Little Endian 1.2.840.10008.1.2.1
JPEG Baseline (Process1) 1.2.840.10008.1.2.4.50
JPEG Extended (Process2 & 4) 1.2.840.10008.1.2.4.51
JPEG Lossless 1.2.840.10008.1.2.4.70

STORAGE-SCU Service does not accept Association Request.
2.2.2 Print MANAGE-SCU Application Entit

KC_PLNK5_SCU has been set as default for PRINT MANAGE-SCU AE Title in ImagePilot.
2.2.2.1 SOP Class
ImagePilot supports following DICOM V3.0 SOP Classes in PRINT MANAGE-SCU Service.

Basic Grayscale Print Management Meta 1.2.840.10008.5.1.1.9 YES NO
Presentation LUT 1.2.840.10008.5.1.1.23 YES NO
11
2.2.2.2 Association Establishment Policies
2.2.2.2.1 General
KC_PLNK5_SCU starts sending the image data after Association is established. AE Title and Port No.
from which the Association is accepted are set in configuration.
KC_PLNK5_SCU dose not accept Association Request from the external AEs.

KC_PLNK5_SCU is capable of sending Association Requests for maximum 1 external AE including



• 1.2.392.200036.9107.[DivCode].[11+Study No.]

2.2.2.3.1 Activity-Print Image Requested to an External Peer AE

KC_PLNK5_SCU sends Association Request to Print Service Request origin, and sends Print
Service Request after Association Request is accepted.
12
Sequence of Print Service requested from external AE in the above is described below.
1． KC_PLNK5_SCU sends Association Request to external AE.
2． Creates Film Session using N-CREATE command of Film Session SOP Class.
3． Creates Presentation LUT using N-CREATE command of Presentation LUT SOP Class
(assuming the Printer supports this command)
4． Creates File Box associated with Film Session using N-CREATE command of Film Box
SOP Class.
5． Sends a sheet containing the data to be output from the Printer using N-SET command of
Image Box SOP Class. If Presentation LUT is not supported, processing shall be continued
using LUT that has been already received.
6． Sends a request for printing Film Box to the Printer using N-ACTION command of Film
Box SOP Class.
7． Printer outputs the requested sheet.
8． KC_PLNK5_SCU sends Release Request to external AE.
2.2.2.3.1.2 Proposed Presentation Contexts

ImagePilot sends Association Request using Presentation Contexts listed below in PRINT
MANAGE-SCU.
Abstract Syntax
Extended
Name UID Role
Negotiation
Basic Grayscale Print Management Meta 1.2.840.10008.5.1.1.9 SCU None
Presentation LUT 1.2.840.10008.5.1.1.23 SCU None
ImagePilot supports following Transfer Syntax for Abstract Syntax mentioned above.
13
Transfer Syntax
Name List UID List
2.2.2.3.1.3 SOP Specific Conformance for the Printer SOP Class

KC_PLNK5_SCU supports following DIMSE.
‐ N-GET
Details of DIMSE is described in the following paragraph.
2.2.2.3.1.3.1 Printer SOP Class Operations (N-GET)

SCU is capable of using N-GET to send Request for Print SOP Instance to SCP.
<< Printer SOP Class>>
N-GET successful Successful Printlink5-IN(SCP) searched SOP Instance

N-GET failed Failure Printlink5-IN(SCP) did not search SOP Instance
Printlink5-IN （SCP） returns either of the following status codes to HOST(SCP).

<< Status Codes common to Print Manage Service Class>>
0000H(successful) U/M : Imager status, imager status information.

U/U : Manufacturer, product model name, installation serial No.,
software version, imager name.
<< Specific Status Code>>
No specific status code
2.2.2.3.1.4 SOP Specific Conformance for the Film Session SOP

Class
KC_PLNK5_SCUsupports following DIMSE.
‐ N-CREATE
2.2.2.3.1.4.1 Film Session SOP Class Operations (N-CREATE)

Attributes of N-CREATE are listed below.
Tag Name VR VM Permitted Value

(2000, 0010) Number Of Copies IS 1 Print count.
1 ～ 99
(2000, 0020) Print Priority CS 1 Priority in print.
LOW
MED
HIGH
(2000, 0030) Medium Type CS 1 Type of media.
CLEAR FILM = Clear base
BLUE FILM = Blue base
DR BLUE FILM = DR blue base
(2000, 0040) Film Destination CS 1 Film output destination.
MAGAZINE
PROCESSOR
BIN_1 ～ BIN_6
14

(2000, 0060) Memory Allocation LO 1 Memory allocation.
Set the necessary memory contents.
Value is displayed in KB.
Tags other than the above are not checked.

Header information that is not maintained yet will be maintained as necessary.
2.2.2.3.1.5 SOP Specific Conformance for the Presentation LUT SOP

class
‐ N-CREATE
2.2.2.3.1.5.1 Presentation LUT SOP Class Operations (N-CREATE)

Attributes that are sent by N-CREATE are listed below.

(2050, 0010) Presentation LUT SQ 1 Presentation LUT Sequence
Sequence
(0028, 3002) LUT Descriptor US\ 1 LUT descriptor
US
(0028, 3003) Explanation LO 1 LUT explanation
(0028, 3006) LUT Data US 1-n LUT data
or SS
(2110, 0030) Presentation LUT Shap CS 1 Presentation LUT shape
IDENTITY/LIN OD
15
2.2.2.3.1.6 SOP Specific Conformance for the Film Box SOP class
‐ N-CREATE
‐ N-ACTRION
2.2.2.3.1.6.1 Film Box SOP Class Operations (N-CREATE)

Attribute that is sent using N-CREATE is listed below.

(2010,0010) Image Display Format ST 1 STANDARD\1,1 ～ STANDARD\5.4
(2010,0040) Film Orientation CS 1 Film orientation.
PORTRAIT
LANDSCAPE
(2010,0050) Film Size ID CS 1 Film size (imager-dependent)
8INX10IN
10INX12IN
11INX14IN
14INX14IN
14INX17IN
(2010,0060) Magnification Type CS 1 Magnification type.
REPLICATE = 0-dimensional interpolation
CUBIC = 3-dimensional B-Spline
interpolation.
(2010,0080) Smoothing Type CS 1 Smoothing type : 1 ～ 7
Valid only for the magnification type (2010,
0060) = CUBIC.
(2010,0100) Borders CS 1 Border density: BLACK/ WHITE
(2010,0120) Min Density US 1 10 ～ 459 (imager-dependent)
(2010,0130) Max Density US 1 11 ～ 460 (imager-dependent)
(2010,0140) Trim US 1 Trimming frame
YES
NO
(2010,0150) Configuration Information ST 1 Imager LUT description is as follows;
KC_LUT=1 ～ 7
(2010,015E) Illuminatio US 1 Illumination
(2010,0160) Reflected Ambient Light US 1 Reflected ambient light

2.2.2.3.1.6.2 Film Box SOP Class Operations (N-ACTION)

N-ACTION requests SCP to print the contents of Film Box.
However, it does not evaluate the contents returned as the response from N-ACTION.
16
2.2.2.3.1.7 SOP Specific Conformance for the Image Box SOP class
‐ N-SET
2.2.2.3.1.7.1 Image Box SCP Class Operations (N-SET)

Attributes of N-SET are listed below.

(0028, 0002) Samples per Pixel US 1 Samples per pixel.
(0028, 0002) PhotometricInterpretation CS 1 Photometric interpretation.
Minimum VOI pixel value= White
MinimumVOI pixel value = Black
(0028, 0002) Rows US 1 Image pixels in Y-axis direction.
(0028, 0002) Columns CS 1 Image pixels in X-axis direction.
(0028, 0002) Pixel Aspect Ratio IS 2 Pixel aspect ratio.
(0028, 0002) Bits Allocated US 1 Bits allocated to pixel.
Vacant bits included.
0008:8 (8 bits)
000A:16 (12 bits)
Returns an error for those other than the
above.
(0028, 0002) Bits Stored US 1 Bits per pixel.
0008:8 bits
000C:12 bits
(0028, 0002) High Bi US 1 High bit.
MSB (Most Significant Bit) of pixel data.
0007: （Bits Stored = 8）
000B: （Bits Stored = 12
(0028, 0002) Pixel Representation US 1 Presentation of pixel data.
0000 = integer without sign
(0028, 0002) Image Position US 1 Image position.
Position of images comprising the page.
(0028, 0002) Polarity CS 1 Polarity
NORMAL
REVERSE
(0028, 0002) Requested Image Size CS 1 Requested image size (imager-dependent)
(0028, 0002) Requested Decimate/Crop CS 1 Requested behavior (imager-dependent)
Behavior
(0028, 0002) Pixel Data OW 1 Pixel data.
OB


KC_PLNK5_SCU does not accept Association Request.
17
2.3 NETWORKING INTERFACE
2.3.1 Supported Communications Stacks (parts8, 9)

Provides higher-level protocols that are defined by DICOM PS3.8 for DICOM TCP/IP.
2.3.2 TCP/IP Stacks
2.3.2.1 Physical Network Interface

ImagePilot supports following Network Interface configuration.
Recommended is Ethernet 1000Base-TX. 100Base-TX can be an alternative as an option.
1000Base-TX
100Base-TX
2.4 CONFIGURATION
2.4.1 AE Title/Presentation Address Mapping
2.4.1.1 Local AE Titles

All Application Entities for DICOM Service in ImagePilot are set in configuration file.
AE setting shall be made in configuration by the service engineer.
Making the setting in configuration file allows the same AE Title to be applied to each service within the local
network.
2.4.2 Parameters
Parameter Default Value Range

General Parameters
Max PDU Size (Kbytes) 64 1 ~ 64Kbytes
Reception Time-Out for General 180000 0 ~ 2147483648
Communication (ms)
Auto Release Time (sec) 600000 0 ~ 2147483648
STORAGE-SCU AE Parameters
Transfer Syntax 0 0 ： Implicit VR little endian
1 ： Explicit VR little endian
2 ： Explicit VR big endian
3 ： Reversible JPEG
4 ： Irreversible JPEG8 bits
5 ： Irreversible JPEG12 bits
6 ： JPEG2000-compatible, reversible
JPEG
7 ： JPEG2000-compatible, irreversible
JPEG
Print Manage-SCP AE Parameters
Reception Time-Out for General 180000
Communication (ms)
Print Status Notification ON/OFF 0 0 : OFF, 1: ON
18
DICOM Conformance Statement 3. SUPPORT OF CHARACTER SETS
Parameter Default Value Range

Presentation LUT AV/NA 0 0 : Available, 1 : Not available
Max Copies 99 Printer max copies
Memory Allocation 512 Printer setting
Requested Image Size AV/NA 0 0 : Available, 1 : Not available
Retry Process －－
3. SUPPORT OF CHARACTER SETS

Following expanded character set is supported.
Default Single-byte Character Sets
• ISO-IR6 　　 (ISO 646) 　 default
• ISO-IR100 　 (ISO 8859-1)
Default Multi-byte Character Sets
• ISO-IR13 　 (JIS X 0201)
• ISO-IR87 　 (JIS X 0208)
4. SECURTIY
ImagePilot does not support special security measures presuming the system is protected by the institute’s security measures.
4.1 ASSOCIATION LEVEL SECURRIY

In the process of each DICOM Service provided by ImagePilot, checks on Calling AE Title, Called AE Title and
Application Contexts are made depending on its contents. Doing so helps protect from illegal access from AE that is not
set in configuration.
19
0604-YA320A
070816TE

Imagepilot

Uploaded by

Copyright:

Available Formats

Imagepilot

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Imagepilot

Uploaded by

Copyright:

Available Formats

IMAGEPILOT

CONFORMANCE STATEMENT OVERVIEW

Table1-1: NETWORK SERVICES

User of Service Provider of Service

2.2.2.2.4 Implementation Identifying Information................................................ 12

3 SUPPORT OF CHARACTER SETS ............................................. 19

1.3 DEFINITIONS, TERM AND ABBREVIATIONS

2.1 IMPLEMENTATION MODEL

2.1.1 Application Data Flow

2.1.2 Function Definition of AEs

2.1.2.1 Function Definition of STORAGE-SCP Application Entity

2.1.2.2 Function Definition of QUERY/RETRIEVE-SCP Application Entity

2.1.2.3 Function Definition of PRINT MANAGE-SCP Application Entity

2.1.3 Sequencing of Real-World Activities

2.2.1 STORAGE-SCP Application Entity

2.2.1.1 SOP Class

SOP Class name SOP Class UID SCU SCP

2.2.1.2 Association Policies

Application Context Name 1.2.840.10008.3.1.1.1

2.2.1.2.2 Number of Associations

Maximum number of simultaneous Associations 5

2.2.1.2.3 Asynchronous Nature

Maximum number of simultaneous Associations 1 (Not Configurable)

2.2.1.2.4 Implementation Identifying Information

SOP Instance UID is defined as follows.

Notes） [DivCode] ： Section code 500

2.2.1.3 Association Initiation Policy

2.2.1.4 Association Acceptance Policy

2.2.1.4.1 Activity-Storage Image Requested by an External Peer AE

2.2.1.4.1.1 Description and Sequencing of Activity

2.2.1.4.1.2 Accepted Presentation Contexts

2.2.1.5 STORAGE-SCU Application Entity

2.2.1.5.1 SOP Class

SOP Class name SOP Class UID SCU SCP

2.2.1.6 Association Establishment Policies

Application Context Name 1.2.840.10008.3.1.1.1

2.2.1.6.2 Number of Associations

Maximum number of simultaneous Associations 5

2.2.1.6.3 Asynchronous Nature

Maximum number of simultaneous Associations 1 (Not Configurable)

2.2.1.6.4 Implementation Identifying Information

SOP Instance UID is defined as follows.

Notes） [DivCode] ： Section code 500

2.2.1.7 Association Initiation Policy

2.2.1.7.1 Activity-Send Image Requested by an External Peer AE

2.2.1.7.1.1 Description and Sequencing of Activity

2.2.1.7.1.2 Proposed Presentation Contexts

2.2.1.8 Association Acceptance Policy

2.2.2 Print MANAGE-SCU Application Entit

2.2.2.1 SOP Class

SOP Class name SOP Class UID SCU SCP

2.2.2.2 Association Establishment Policies

Application Context Name 1.2.840.10008.3.1.1.1

2.2.2.2.2 Number of Associations

Maximum number of simultaneous Associations 1

2.2.2.2.3 Asynchronous Nature

Maximum number of simultaneous Associations 1 (Not Configurable)

2.2.2.2.4 Implementation Identifying Information

SOP Instance UID is defined as follows.

2.2.2.2.4 　 Implementation Identifying Information................................................ 12

3 　 SUPPORT OF CHARACTER SETS ............................................. 19