HL7® Survival Guide: Chapter 12, Definitions

By | Published: June 18th, 2013


This is a type of de-identification where all sensitive data is removed.  More details and a definition of anonymization are available in a previous blog post.

Code set

Also referred to as HL7® tables, vocabulary or code table. It is a list of codes and their meanings used to codify information included in HL7® messages. Codes could be defined by the HL7® standard itself or information systems.

For instance, here is the list of suggested values for patient gender as proposed by HL7® [...]

Read More
Categories : HL7 Survival Guide

HL7® Survival Guide: Chapter 11 Maintenance, Troubleshooting, Monitoring

By | Published: May 30th, 2013

Now we’re coming full circle. Throughout Chapters 6 through 10, we talked about creating interfacing artifacts, assets, and documentation: profiles, gap analyses, test plans, test messages, test systems, and workflow maps. In this chapter, we explain how you can get maximum value from all the work you put into creating all of those. 

Why Document?

By documenting your profiles and specs, you can much more easily troubleshoot issues and tweak configuration once your interface is live. Plus, if you created electronic – [...]

Read More 2 Comment(s)
Categories : HL7 Survival Guide

HL7® Survival Guide: Chapter 10 Process and Workflow

By | Published: May 13th, 2013

In the last chapter, we explained what to aim for in test messages and message samples. Next you need to map out your processes and workflows to understand how your interface can support them.

For example, your clinical workflow may look like this: a patient is admitted in the Emergency Department via the departmental ADT system. The doctor on duty orders lab work and the patient is admitted to the hospital. The admission is now recorded as an in-patient in the [...]

Read More
Categories : HL7 Survival Guide

HL7® Survival Guide: Chapter 9 Message Samples and Test Messages

By | Published: March 26th, 2013

In the previous chapter, we covered what you need to know when testing your interface. While the right test tool is helpful, you need to feed it the right message samples and test messages. After all, messages impact the entire interfacing lifecycle.

So what makes messages “right”? Namely, you need message samples and test messages that reflect your environment: your ADT message flow, your specific lab codes, and your case mix – whatever information your interface is intended to share.

Just as [...]

Read More 2 Comment(s)
Categories : HL7 Survival Guide

HL7® Survival Guide — Chapter 8: Test Scenarios and Test Systems

By | Published: March 5th, 2013

The HL7® interface lifecycle. You need to test during Configuration, Validation, and Maintenance.

In the last two chapters, we covered some of the requirements-related artifacts you need. Now it’s time for testing, which you conduct at different phases in the interface lifecycle: during configuration and development; during the formal validation phase; and during maintenance.

“Why test?,” you ask. When you start to develop and iterate on your interface, you run tests to avoid introducing new problems – you check and test [...]

Read More 2 Comment(s)

HL7® Survival Guide — Chapter 7: Gap Analysis

By | Published: February 21st, 2013

This chapter helps you set up a crucial HL7® requirements document: the gap analysis. Once you have profiles for your source and destination systems, you need to capture a list of all the gaps existing between the two systems in a requirements document. You unearth this list by conducting a gap analysis, which will tell you what’s missing and what needs to be bridged by the interface. In essence, a gap analysis captures the differences in messaging between the new [...]

Read More
Categories : HL7 Survival Guide

Caristix Message Player Software Now Available

By | Published: February 18th, 2013

No-brainer Message Player buttons

Message Player, our free HL7 listener/router utility designed for HIT software developers, interface developers, and interface analysts, is now out.

You might have seen other HL7 listeners and routers out there. What makes Message Player different is that it’s dead-easy to use. There are no bells and whistles. It’s independent of other software and engines, so once you’ve downloaded the installation package, you can run it on a desktop machine and get going quickly.

Why Use Message Player

first [...]

Read More

HL7® Survival Guide — Chapter 6, Interfacing Artifacts: HL7® Conformance Profiles and Interface Specifications

By | Published: February 6th, 2013

The first five chapters of this Survival Guide have helped you think strategically about your interfacing project. Now we’re going to dive into the nitty-gritty of what you need in an interface specification and/or HL7® profile (note: we use the terms specification, conformance profile, and profile interchangeably in this chapter).

An HL7® interface specification should list:

1. Interface name

How do you refer to your interface in your integration environment? Some organizations manage thousands of interfaces. If you’ve got 10 or 20 interfaces, [...]

Read More
Categories : HL7 Survival Guide

HL7® Survival Guide — Chapter 5: Vendors, Consultants, and Interface Specifications

By | Published: January 18th, 2013

After you’ve assessed clinical interoperability issues (covered in Chapter 4 ), you’ll be ready to start building interfaces. If you’re building your interfaces in house, you’ll be dealing with clinical system vendors. And if you’re outsourcing interface development, you’ll be working with consultants. Either way, you want to know what issues to avoid. That’s where this chapter comes in handy.

Make Sure You Check Off These Boxes

Conduct your due diligence on the following points and your interface project is much more [...]

Read More 2 Comment(s)
Categories : HL7 Survival Guide

The HL7® Survival Guide — Chapter 4: Your EHR Strategy and Working with Vendors

By | Published: January 11th, 2013

With Meaningful Use in full swing, chances are your hospital organization is implementing an EHR or converting to a new system or upgrade. Watch out: when you implement a new system or migrate from one to another, it can impact your systems’ ability to continue exchanging information. That’s why many organizations call upon third-party vendors for guidance and project assistance. You just need to make sure you stay in control and avoid hidden expenses as you work with these vendors. [...]

Read More 2 Comment(s)
Categories : HL7 Survival Guide
All posts