Finally released, ZiKiT 2020, now available on our web site

This was a race against the clock but finally its on our downloads web site.

Check it out.

Here's the link.

HL7Kit Pro 2.0

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

At last, HL7Kit pro 2.0 is out! The new kit features complete integration between DICOM and HL7 and comes up with the DICOM Modality Worklist SCU (as an option) fully pre-configured out of the box. After installation, the package can serve both HL7 orders and DICOM modality worklist queries with no additional configuration. To complete the package we've added the Modality Worklist client so you can see the full cycle.
As before, the kit comes with free evaluation download. The price for the kit has not change but the DICOM Server comes as an extra. More updates soon as we complete new video tutorials and users manual.
The kit relays on SQL Server and installer looks for a pre-installed SQLEXPRESS instance. Check the downloads on roniza.com

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.

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.

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

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.

Healthcare Software Integration Engines are grossly over priced

"Healthcare Software Integration Engines are grossly over priced"

These are not my words. This is an exact quote of a very well recognized healthcare IT professional.

And I fully agree. After all, what's the big deal, Aha? It's just moving fields and attributes from one place to another, change some formats maybe, some XML tricks, database. Really, no big deal, right?

You maybe think to yourself that I'm joking but I'm not. After all, I have developed an HL7 Integration Engine of my own that I'm very proud of, HL7Kit Pro. This little devil is not a show off. It's a tool designed to do one thing - build a two way road, a bridge, between your SQL Server database and HL7. 

In modern design, less is more. When going over the features list of some of these products, I can't avoid the comparison with a 'do it all 149 peaces hardware tool kit' perfect package on TV Shop America.

When shopping for an integration engine it's important to remember that there's always the other road. The one of developing custom interfaces. Good programmers nowadays are not that expensive to hire and the software tools we have today are efficient and easy to use. So when you are facing an integration challenge, you should compare the options and don't get tempted to purchase a multi K$ package bundled with a big unknown figure of expert consultation, maintenance and support fees to feed the monster.

Instead, take the right HL7 tool in your hands and finish the work in no time.

The new 1.3 release of HL7Kit Pro adds hot folders integration. The runtime service can be configured to digest HL7 messages from an inbox folder and write outgoing messages to an Out-box directory.

There's also better support for running multiple HL7 runtime services on a single computer, each using it's own queue.

... And there's many bug fixes and little improvements like the ability to read and write directly from views ...

All in all, the new release is a direct continuation of the old one and that's simply because there's no need for major changes when a tool is doing the work. Simple work, but still work.

Ask every professional: working with quality tools designed for the task is great fun.

To get you started, there are two example projects on the HL7 support page. One for incoming messages and one for outgoing messages that you can download and try with the evaluation copy.

"Hacking" HL7Kit Pro Runtime Service to work with multiple HL7 applications

I know that it's not very common to show how to hack your own application but since this issue has been circling for a while, I'd like to show a workaround that will allow you to use the kit to integrate with many HL7 applications simultaneously.

The kit original design is to communicate with one remote application.

The workaround is to have multiple instances of the HL7 service running. The services can connect to the same database but each mush have it's own queue table.

Each will have it's own configuration file and it's own mapping rules file and mapping definitions but they will all write to the same log file and there can be only one active tray icon.

Here's how to set this up step by step:

1. Stop the HL7 Service.
2. In windows explorer navigate to the installation folder (default is c:\program files\rz software services\hl7) and make a copy of the folder, so you have hl7 and hl72.
3. Create a copy of the HL7_QUEUE table so you have two queue tables or if you prefer, use each service on a different database schema.
4. Use the HL7ServiceConfiguration.exe application in each folder to configure the port settings, mapping files and queue table names. Alternatively you can edit the HL7Service.exe.config file manually.
5. Test your setup by running "HL7Service.exe -run" from two separate command line windows.
6. Configure the new service to run on system startup. This is a bit tricky but here's a way that works:
1. Run regedit
2. navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HL7Service and export it.
3. Edit the reg file and replace all "HL7Service" with "HL7Service2"
4. Save it and double click it to import it to the registry.
5. In regedit change the ImagePath entry of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HL7Service2 to the copied HL7 Folder (hl72)
6. Restart the computer.

Now you should have two services installed: HL7Service and HL7Service2. 

Of course, you can duplicate them as well.

I hope to have a new release soon that will allow multiple destinations and sources of messages.

Roni

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.

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.

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.