Are Healthcare Integration Engines Needed?

Posted on March 13, 2017 I Written By

John Lynn is the Founder of the blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of and John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

In a perfect world, we might ask why health systems need to purchase an integration engine. The standards used by integration engines are pretty widespread and every EHR and Healthcare IT vendor uses that standard. Why then do we need an integration engine in the middle?

I’m sure there are a lot of reasons, but two reasons stand out the most to me are: integration costs and flavors of standards.

Integration Costs
It’s amazing how expensive it is to build integrations with EHR and other healthcare IT software. I still look back on the first lab interface integration I did. I couldn’t believe how expensive it was to do the integration and how the vendors were happy to nickle and dime you all along the way. Many of them look at it as a secondary business model.

While an integration engine can’t solve all these costs, if you have a large number of integrations, the integration engine can save you a lot of money. This includes the integration engine’s experience integrating with multiple vendors, but it also means you can often only pay your EHR vendor one time instead of getting charged for every integration.

Flavors of Standards
If you’ve ever managed an integration, you know how miserable it can be. Each side of the integration implements their own “flavor” of the standard (which makes no sense, but is reality) and that flavor can often change as the various software gets updated. It’s no fun to manage and often leads to interface downtime. You know the impact interface downtime can have on your providers who don’t understand the intricacies of an interface. No one likes something that previously just worked to stop working.

This is where integrations engines definitely shine. Their whole job is to manage these types of changes and ensure that they’re prepared for the change. If they can’t do this right, then you should search for a new integration engine. Plus, integration engines usually have tools to help you manage this and to update this as vendors change (and they will change).

Will Integration Engines Survive?
In the perfect world, we wouldn’t need an integration engine. Healthcare is not a perfect world. In fact, it’s far from it, so I see integration engines sticking around for a long while to come. They’re quite entrenched in the business processes of most large healthcare organizations.

While at the HIMSS Conference, I was talking with Summit Healthcare and they noted that they have 1 client that’s sending 5 million messages per day (Yes, I said per day!). That’s a lot of messages and that’s only one client from one integration engine. Hearing that number illustrated how valuable these integration engines are to an organization. It also flew in the face of healthcare not being interoperable. However, it illustrates how much data needs to be shared if we had true interoperability since those 5 million messages only includes a small portion of health data that could be shared.

We’ll look at diving into integration engines in more detail in future posts. I think they’re an important backbone of what’s happening in healthcare IT and many don’t realize it.