Dicom Conformance Statement dicomPACS DX-R 2018-03-01
Dicom Conformance Statement dicomPACS DX-R 2018-03-01
1. Introduction ..................................................................................................................... 3
1.1. Abbreviations and Acronyms................................................................................... 3
2. Implementation Model .................................................................................................... 4
2.1. Application Data Flow Diagram............................................................................... 4
2.2. Functional Definitions of AEs................................................................................... 4
3. AE Specifications.............................................................................................................. 5
3.1. Common information ............................................................................................. 5
3.2. ConsoleSCU............................................................................................................. 5
3.2.1. Send Image (StoreSCU) ................................................................................... 5
3.2.2. Request Storage Commitment ........................................................................ 5
3.3. Console ................................................................................................................... 6
3.3.1. Send Echorequest (EchoSCU) .......................................................................... 6
3.3.2. Worklist query (FindSCP) ................................................................................. 6
3.3.3. Send MPPS message ........................................................................................... 7
3.3.4. Dicom Media Service ........................................................................................... 8
3.3.5. Gray Scale Standard Display Function.............................................................. 8
3.3.6. Implementation Class UID ............................................................................... 8
3.4. ORPrintSCU ............................................................................................................. 9
1. Introduction
This DICOM/DICONDE/DICOS conformance statement specifies the behaviour and functionality of the
following application:
• dicomPACS® DX-R
• OR inspect
• OR secure
The Software uses the DICOM software development kit (DCMTK) from OFFIS e. V. Oldenburg.
(see http://dicom.offis.de/software.php.en)
Web: http://www.or-technology.com
2. Implementation M odel
Query C-Find
Worklist Server
Worklist
C-Store
Send SC N-Action
Object
DICOM Archive
SC N-Event-Report
ConsoleSCU
Print to
DICOM
DICOM
Print SCP
Printer ORPrintSCU
Program ConsoleSCU is used to send images to remote AEs and to verify storage with storage
commitment service class.
ORPrintSCU implements the Basic Grayscale Print Management service class as SCU. The process
is used by dicomPACS®DX-R to send print jobs to DICOM printers.
3. AE Specifications
3. 1. C ommon information
3. 2. C onsoleSCU
The StoreSCU function creates only one association at a time. Supported DICOM SOP classes are:
Storage Commitment request is automatically send about 1 minute after successful sending image to
remote AE if storage commitment is configured for this AE. Console SCU expects storage commitment
result on a new association from remote AE. If storage commitment re quest fails or no response is re-
ceived then the request is repeated after 5 minutes.
Storage Commitment is requested for SOP classes listed in section 3.2.1 ConsoelSCU does not support
the optional Storage Media File-Set & UID Attributes.
3. 3. C onsole
The EchoSCP function sends a C-Echo request if user test connection to AE.
dicomPACS® DX-R queries the configured DICOM worklist server in an interval of 30 seconds.
dicomPACS® DX-R supports the Modality Performed Procedure Step SOP class as SCU.
The function sends the state of currently open examination to a MPPS server. The state messages are
sent on following operations:
State Operation
IN PROGRESS - if study was planned via Worklist server and study is opened first time
- if first examination is planned for a study
COMPLETED - if all images of an study are committed
DISCONTINUED - if all examinations are removed from study
dicomPACS® DX-R conforms to the DICOM Media Storage Service and File Format (PS 3.10) and the Me-
dia Storage Application Profiles (PS 3.11) for creating file sets on CD-Recordable media.
Following application profiles are supported:
To create media user can add studies of different patients to a media collection. Then the user can cre-
ate the medium from the collection.
Outside of the DICOM/DICONDE/DICOS standard the medium contains a viewing software and a pre-
view of images.
The digital imaging and communication in medicine (DICOM) grayscale standard display function (GSDF)
defines the luminance response of a display such that an observer’s perception of image contrast is con-
sistent throughout the pixel value range of a displayed image. The GSDF ensures that the perceived con-
trast is consistent throughout the grayscale range of a given display, but displays that have substantially
different maximum luminance values or contrast ratios will not provide an exact perceptual match.
dicomPACS® DX-R conforms to the Grayscale standard display function (PS 3.14) on pre -calibrated single
display systems with the function for daily visual check for approval of display luminance to check visual
consistency. The accurate display of greyscales has to be checked by sight at least once a day. Right after
starting the application a test image is used for this purpose.
The following data is used when sending with ORDicomSCP.dll and when saving (as in the dicomCC,
worklist server, worklist queries, MPPS, storage commit and find / retrieve in the viewer):
3. 4. ORPrintSCU
The ORPrintSCU provides standard conformance to the Basic Grayscale Print Management Meta SOP
class as SCU.:
ORPrintSCU attempts to initiate a new association if a print job is generated by a dicomPACS® Viewer.
Print jobs are queued by the software and processed sequential.
The maximum PDU length can be configured in the range 4096..131072 bytes. The default is 16384
bytes. ORPrintSCU establishes only one association at a time. The software does not support asynchro-
nous transactions.
ORPrintSCU supports the following mandatory SOP classes as defined by the Basic Grayscale Print Man-
agement Meta Class:
It is configured by the file ‘PrinterConfig.xml’ which is located in the installation directory of the dicom-
PACS® Viewer. The following tables list the attributes supported for the different SOP classes. The values
in the Usage column are used as follows:
Usage Meaning
A Attribute is always sent
C The attribute is only send if it is defined in the print job