View Image

One of the most complex aspects of configuring, and maintaining, healthcare applications is interpreting the semantics of the data being exchanged. HL7Spy has been designed to help HL7 analysts and programmers quickly interpret, and characterize very large HL7 message streams. It quickly reads in 1000s of messages and provides statistics at the message, field, component and subcomponent levels providing great insight into the nature of the data exchange.

HL7 Spy can answer quite complex questions about a set of HL7 transactions. For example, with a sample HL7 message file, HL7Spy can answer the following questions:
“What are the values being transmitted for Order Status (ORC-5), and what are the distributions for each value?”
“How large is the largest message in the stream?”
"Are there any ORM messages where ORC-3 is null?"
“How often is patient sex (PID-8) filled in ADT^A08 messages?”
“What are the maximum and minimum lengths of the patient identifier (PID-3.1)?”
“Are there any patient encounters where the report status (OBR-25) incorrectly transitioned from ‘Final’ to ‘Preliminary’?”
These are only a sampling of the questions that many analysts want answered when trying to interpret, troubleshoot, and configure HL7 interfaces. With just a few clicks HL7 Spy can easily provide this information, and much more.

While HL7Spy was designed by HL7 Analysts, for HL7 Analysts, it is also an invaluable tool for novice users and developers.

For the novice user, HL7Spy provides a great platform for learning HL7. There is nothing like going through a large data stream with HL7Spy and following an exchange of messages for a specific patient to learn about HL7.

For developers and power users, there is a custom code editor. Custom functions unleash the maximum capabilities of the product. Users can accomplish complex tasks in a simple programming environment. With the custom code editor it is possible to: generate a CSV file of patient attributes that match some criteria, file data into a database, analyze complex message exchanges, or any task that isn't directly supported by the product.