Monday, January 23, 2012

DICOM Query/Retrieve Part I


It all started when I was sitting in a cubicle with a customer, looking at the code of their workstation performing a Query/Retrieve cycle and though everything did look familiar and pretty much straight forward something bothered me.

Query/Retrieve, or Q/R for short, is the DICOM service for searching images on the PACS and getting a copy of them to the workstation where they can be displayed.

Q/R is a fundamental service and every workstation implements it. This sounds like a trivial task, just like downloading a zip file from a web site but there are a lot of details to take care of and while writing this post I realized that I will have to split it to a little sub-series. Today's post will be about the Query part and in the next post I'll get to the Retrieve.

To search the PACS we use the DICOM command C-FIND. This command takes as an argument a DICOM object that represent a query. The PACS transforms the object that we send to a query, probably to SQL, runs it and then transform every result record back into a DICOM object and send it back to us in a C-FIND response. The PACS sends one C-FIND response for every result record. While still running, the status field of the C-FIND response command is pending (0xFF00). The last response has a status success. It may of course fail and then RZDCX will throw an exception with the failure reason and status. It may also succeed but with no matches (empty results set).

Let's do some examples. This code constructs a query for searching patients:

            // Fill the query object
            DCXOBJ obj = new DCXOBJ();
            DCXELM  el = new DCXELM();

            el.Init((int)DICOM_TAGS_ENUM.QueryRetrieveLevel);
            el.Value = "PATIENT";
            obj.insertElement(el);

            el.Init(0x00100010);
            el.Value = "R*";
            obj.insertElement(el);

            el.Init(0x00100020);
            obj.insertElement(el);

            el.Init((int)DICOM_TAGS_ENUM.PatientsSex);
            obj.insertElement(el);

            el.Init((int)DICOM_TAGS_ENUM.PatientsBirthDate);
            obj.insertElement(el);

Monday, January 9, 2012

Introduction to DICOM - Chapter 6 - Transfer Syntax

Transfer syntax defines how DICOM objects are serialized. When holding an object in memory, the only thing that matters is that your application can use it. The internal representation of the object is your own business. However, when sharing objects with other applications, everyone should be able to use the same object. The common solution for such problems is serialization.

Serialization is the process of writing a data structure or object state to wire i.e in a format that can be stored in a file or memory buffer, or transmitted across a network so it can be read on the other side of the wire or later by the same or by another process.

There's no shared memory in DICOM but it can be easily made using the same mechanism that is utilized for networking and files alike i.e. serializing the object into memory according to the rules dictated by the standard i.e. using transfer syntax.

In this post I'll cover the following issues:
  • Present the term Transfer Syntax, 
  • Why Transfer Syntax is required 
  • What is Transfer Syntax used for 
  • How Transfer Syntax is set when using 
    • DICOM files 
    • DICOM network
So, as I said, the serialization in DICOM is governed by a term called Transfer Syntax.

Transfer Syntax is defined at the object level and is the syntax for serializing a DICOM object. We have seen transfer syntaxes already in chapter 5 when dealing with association negotiation but did not discuss them. In order for an application to read a DICOM object from a network wire, it has to know the rules that were used to write the object into the wire. In the association request the calling AE sends a list of abstract syntaxes with SOP Class UID's. For every SOP Class, the calling AE sends a list of transfer syntax UID's. In the association response the called AE selects one of the transfer syntax UID's for every SOP class it accepts.


Thursday, November 17, 2011

Special offer for the new HL7Kit Pro 1.5

The new version 1.5 of HL7Kit Pro - HL7 to Database Integration Engine was released today. To celebrate the new release, the new version is offered at only $249 and includes all 4 applications in a single installation package. We've come to realize that our users prefer having the entire product installed on the production server including the HL7 Sender, HL7 Receiver and the HL7 Mapping Tool.

The main new feature of the new release is the support of multiple protocol versions and multiple mapping rules for a single runtime service. The runtime service can be configured to use different message definition files and different mapping XML for every remote application. This feature was requested long ago by many customers and a workaround to allow this was introduced in version 1.2. Now this feature is fully integrated into the product. The new release can be downloaded here.

Friday, October 28, 2011

HL7Kit Video Tutorials

If one picture worth a thousand words, how much does a 20 minutes video tutorials worth?
The HL7Kit web site promise that "You are 20 minutes away from HL7 integration!" I checked that again, this time on film.
From download to runtime deployment, a series of five detailed videos showing step by step how to set up a ADT^A01 message interface using HL7Kit.
Here it is. Comments and questions are most welcome.


Sunday, September 25, 2011

Open Source HL7 Sender

[update 24 March 2023: Latest releases of HRZ software can be found on HRZ website - www.hrzkit.com]




HL7 Sender source code is now available for free download.
The full source code of the HL7 editor / HL7 sender application can be obtained from the product web site

Sunday, May 15, 2011

RZDCX DICOM Library Release 2.0.0.8

The new release of RZDCX - Fast Strike DICOM Toolkit addresses customers change requests and enhancements.
The change log is detailed in the following table.

#TypeStatusCreatedBySubsysChangedAssignedSvrPriTitle
253newfixedMar 23zroniRZDCXMar 23zroni53Limit log file sizeedit
254newfixedApr 20zroniRZDCX10:52zroni33Support Unicode filenamesedit











256newfixedMay 14zroniRZDCXMay 14zroni53Add Status Detail to Error Messageedit


All changes does not affect the default behavior of the DICOM Library.

Change #253 addresses the size of the log file. This change enables the user to set a size limit in terms of number of messages in the file. The change introduces new methods to the DCXAPP interface that control the log file size and filename. For more information please read the DICOM Library Documentation page dealing with DICOM Diagnostics and Logging.

Change #254 adds support for Unicode filenames. After this change, all method parameters that carry filenames (e.g. OnStoreSetup, OnStoreDone, SaveFile, openFile, Send, CommitFiles) may use Unicode filenames strings. For example, if your application requires to save DICOM files with names with Mandarin characters, this is now supported.

Change #256 adds more information to the error description that is provided when a DICOM command fails by dumping all optional command attributes that were provided by the peer application into the error description string. The status details attributes are optional elements that a SCP may provide when commands fail. These may be a list of offending elements or other information that can help diagnose the problem. See for example DICOM Stabdard part 7, Section 10.1.5.1.6 describing N-CREATE Status Detail.

Tuesday, February 1, 2011

New HL7Kit Release 1.4 adds multiple destinations

We're happy to announce the new release 1.4 of HL7Kit, HL7 Integration Engine.
This release takes HL7Kit a major step forward with the new multiple-destinations feature.
With multiple destinations, HL7Kit can serve as a dispatcher for HL7 messages, sending the same message to multiple applications.
Every destination is monitored independently and has it's own retry counter, logging and error handling.
Users may select to send messages to all configured destinations or just to specific ones, depending on integration needs.
In addition, this release includes new message structure definitions for MDM messages.
A complete list of the features can be found in the updated user's manual available for download from the product support page at http://www.hl7kit.com/support.html.