July 25, 2009
Why Get a Lab Interface and Cost of Implementation
Written by: JohnSign up to receive all the latest EMR, EHR, Simulus, and Healthcare IT Updates.
I’m always sad when I come across an EMR implementation that doesn’t have an interface between their EMR and their lab. I can appreciate someone having just implemented an EMR not having a lab interface. However, it should be one of the first things on your list to implement. It’s such a great compliment to your EMR software.
First thing I must suggest is that you get a bi-directional lab interface if at all possible. One way lab interfaces can work, but do take more management to make it work right.
Why Get a Lab Interface with Your EMR?
Lab interfaces are so seamless. The order is made in the EMR and it’s automatically is sent to the lab. Talk about removing a lot of the possibilities for error. In our case, we have an in house lab and so this saves a ton of time for the lab rat tech as well. No more data entry into the Lab’s LIS system. As a side note, we also use the lab order in our EMR to print out the labels for the specimen. This is an unbelievable time saver and much more accurate. Small things like this are just another hard to calculate benefit to an EMR.
The largest benefit to a lab interface is receiving the results back electronically. Compare this to receiving a paper copy of the lab results. Often this paper copy is sent to a fax machine and then the hunt begins to get that result to the right paper chart/person. The time savings here are apparent. With a lab interface, you no longer have to file the lab results in the paper chart (or scan them into your EMR). The results are automatically available in the EMR and routed to the ordering provider. They can be signed electronically and no one has to then go back and refile the chart.
What’s even more important is that with the lab interface all of those lab results are now stored in discrete values. Storing the lab results this way means that you can graph lab results over time, do studies on lab results across your patient population, and eventually may be needed to satisfy the government and insurance reporting requirements.
Cost of a Lab Interface
Many people are often surprised to find out that there’s sometimes a cost associated with implementing a lab interface. In fact, there could be multiple costs involved.
The costs depend a lot upon your EMR vendor and the lab with which you’d like to interface. Some EMR vendors will offer a lab interface for free (or part of the standard cost of the EMR) while others will charge. The same is true for labs. However, more labs are willing to offer their interface for free. Often that just requires the right negotiating skills. If you’re a large customer of that lab, then if you talk to the right people you can usually get the interface for free. Labs are easier to negotiate with since a lab interface benefits the lab as well. $5,000 seems like the standard charge (from what I’ve seen) for most interfaces. Yes, that’s possibly $5,000 to your EMR vendor and another $5,000 to your lab.
Related ArticlesLook for similar articles under these categories:
5 responses to "Why Get a Lab Interface and Cost of Implementation"
Leave a Reply
- » Recent articles
- $3 Billion Ambulatory EHR Market
- Reshuffling of Ambulatory Physicians Favors Large EHR Vendors
- Drummond Group and CCHIT Become First Official ONC EHR Certifying Bodies
- CCHIT Certified EHR Becoming ARRA Certified EHR
- Crazy Legislative Process
- One Way Of Measuring Meaningful Use Productivity Loss
- EMR Billing Matters
- EMR vs EHR
- EMR Vendor Recommendations
- Imagine an EMR without Billing
- Drugs for Sale - The Drug Company
- » Archive Calendar
-
Jobs by SimplyHired
The industry’s tendency to charge for interfaces really bothers me. Interoperability is a major component of the federal push for EMR adoption, and as you point out in this post, it’s a big source of the projected long-term cost savings. Yet with the status quo right now, just adopting an EMR doesn’t mean you’re interoperable – there are additional costs in time and money, if it’s even possible.
I can’t count how many times a customer of my mobile charge capture company has been shocked and appalled to learn that while we never charge for interfaces, their billing software / PMS / EMR demands $5000, $10000, or north of $15000 to begin the project. The interface cost alone dwarfs the cost of our software.
Cost is one consideration, but medical practices that are considering an interface should also do their research about a vendor’s interface management experience. Otherwise, you can end up sinking a lot of money into an interface that takes months to complete while developers are pointing fingers at each other and you’re left holding the bag. Questions to ask lab companies, EMR/PM vendors prior to beginning an interface: Do all vendors comply with industry standard coding languages (preferably Health Level 7)? How many successful integrations are under each vendor’s belt? (if they have not completed any, you may want to be wary). Is there a dedicated team of interface developers, or will your project get pushed onto the back burner in a busy Product department? What is the average timeline for completion? Once you’re satisfied with answers to those questions, it’s a good idea to check references. Until we have a truly interoperable system in place, the onus is on medical practices to be educated and savvy about the interface process.
Adam and Jennifer,
Thanks for rounding out the discussion of interfaces. We had to have our interface built from the ground up. We basically did all the testing for the lab interface ourselves since we didn’t trust the EMR company to make sure EVERYTHING went through correctly. Lab results were something we didn’t want to gamble on. It was a lot of work, but was some of the best work we did and well worth the effort.
John,
Great post. It motivated me to publish a similar post to my company’s blog, one that is a more tailored to the AE-EHR and its tasking and RIS integration capabilities. I also touched on the costs and benefits to an immunization data exchange with an immunization registry. You can find both here: http://blog.galenhealthcare.com/
As a follow-up to implementing a lab interface, I published an article on the ingredients to a successful interface project. In our experience, by following the keys to success outlined in the blog article, we were able to crash project time lines, accommodate for advance business logic via our advanced knowledge of the AE-EHR API, and also reduce implementation costs. You can find the blog article here: http://blog.galenhealthcare.com/