Sunday, April 19, 2009

Win32 registration problem in v 1.0.0.5

A problem registering and using version 1.0.0.5 from the download page was reported.
Please use the updated v 1.0.0.6 patch from the download page.

Monday, March 30, 2009

Known bug: Linking tables using same key field

The following problem was reported and identified ion HL7Kit Pro.
The program fails to identify a parent-child relationship between two tables where the relationship columns have the same name for example if two tables have a foreign key where the primary key column name is 'id' and the foreign key column is also called 'id'.

Workaround: rename one of the columns.

Ticket #: 146

HL7Kit Pro Example project

[update 24 March 2023: latest HRZ ZiKiT Server can be found on HRZ website - www.hrzkit.com]

Following the release of HL7Kit Pro, we'll be uploading sample projects to demonstrate the functionality of this great product.

The first example, just uploaded today, shows how to use HL7Kit Pro to process an incomming patient admit message (ADT^A01 Event).

The example includes a zip file with readme instructions, a SQL script to create the example database, a mapping file and a test message.

Just follow the instructions in the readme file.

Friday, March 27, 2009

New Release of RZDCX 1.0.0.5

RZDCX 1.0.05 is release with new features and bug fixes.
Most noteable are the new compression options and fixes to enable better creation of DICOM Image Objects.

Here are the new features and bug fixes:

135 Save file does not create Part 10 Meta Header
136 Sequence Elements are not encoded correctly when saving
137 Added compression options for Jpeg Lossless and Jpeg Lossy
138 OnStoreDone is not called if C-STORE failed
139 CommitFiles and CommitInstances return empty string
140 Added C++ Image Example
141 Query sends cancel when it should continue (true/false mismatch)
142 Float-2-String test failes due to double-float mismatch
143 Setting sequence with empty iterator never returns

Tuesday, March 24, 2009

HL7Kit Pro 1.2 Released!

We're proud to announce the release of HL7Kit Pro.
This product is the full version of HL7Kit and HL7FreeSender that were released in 2008.

With HL7Kit Pro you're just 20 minutes away from HL7 Integration.
No programming required!

Checkout the product site at [update 24 March 2023: latest HRZ ZiKiT Server can be found on HRZ website - www.hrzkit.com]

Here's a screen shot of the GUI Interface Design Tool.

Monday, November 17, 2008

HL7Kit 1.0.0.0 - a new HL7 Software

HL7Kit is a continuation of the HL7Sender that was released almost a month ago. This package is a subset of our upcoming HL7 Interface Development Suite and Integration Services carrying the same name (with optional Pro/Enterprise edition).
The current package can be downloaded  [update 24 March 2023: latest HRZ ZiKiT Server can be found on HRZ website - www.hrzkit.com]  from our web site and includes two applications for validating, editing, sending, receiving and processing HL7 v2.x messages.


The first application, HL7Sender, is an improved version with message editing area featuring Synchronized Structure and Content views of the HL7 Message and a save as XML option (from File/Save As menu item) for creating comprehensive and very useful representation of HL7 v2.x messages as HL7 XML. Clicking a node on the left panel tree view highlights the corresponding text in the right panel text box and vice versa. HL7Sender is currently a freeware.


The second application, HL7Reciever, is a powerful brand new application for receiving, validating and processing HL7 messages over TCP/IP connections. HL7Reciver runs a network listener and waits for incoming connections. When a message is received it can be saved automatically either as HL7 or as XML file (or both). In addition, you can configure HL7Reciever to start a new process and pass the saved message as a parameter (by default, the message is saved in XML format and opened using internet explorer). The behavior of HL7Reciver is controlled by no less than 6 Checkboxes! But don’t worry, it is rather straight forward and the tooltips explains it all. HL7Reciever can save logs to text files and has an event log as well that can be used for monitoring and auditing (Vista users, when running HL7Reciver for the first time, run it as administrator so it can create the event log).
As you can read, HL7Reciever is a very handy tool with lots of useful options. This package includes a 30 days fully functional free trial version that requires online registration. The licensed software is currently sold online for $150 USD. For purchase please follow this link.

One last note about the message structure. Check this post for a short explanation of how to modify the message structure definition files. Note also that the XML hierarchical structure is defined by this configuration. The field names in the XML are defined in the segment definition file and can be modified as well.


As already mentioned above, HL7Kit is a subset of HL7 Integration Suite that is coming very soon. Check this blog for updates or reigster for the feed to get updates on this product, how to use it and more.

Editing the message rules used by HL7Kit



The message rules configuration file msgRules.251 is using a similar notation to the one used in the HL7 Standard documentation.
Every line in the file represents one message definition.
The first element is the event type.
When the event type is followed by a semicolon and another event type that means that the structure of the message is defined by the event type on the left is identical to the one with event type on the right. In the example above ADT^A03 is defined to have an identical structure as ADT^A02.
When the event type is followed by a colon, a list of segment names and special grouping characters follow.
The special grouping characters are:




Aliases
Elements that are not special characters or a valid segment names are regarded as aliases. Aliases are used to group segments into entities. For example, in the ADT^A01 an alias called ‘patient’ is defined. Note that the alias name comes AFTER the segments group.