North Kansas City Hospital Case Study
www.nkch.org Kansas City, Missouri
“There are a lot of changes that will be coming our way with Meaningful Use and I expect a lot of interface needs in the future. With Corepoint Health, we are using an integration engine that gets information where it needs to be.”
North Kansas City Hospital is a 451-licensed bed acutecare facility ranked as one of the largest hospitals in the Kansas City metro area. Patients receive a full continuum of services including care provided through five Centers of Excellence: Northland Cancer Center, Northland Women’s Center, Northland Cardiac Center, Northland Orthopedic Center and Northland Emergency Center.
The Hospital is one of the largest employers in the Kansas City metro area with over 3,000 employees.
Healthcare Interfacing Challenges
Wanted a vendor that would continue to grow and develop with the hospital and focus diligently on healthcare integration to proactively enhance functionality and meet new demands.
Needed a stable integration engine to replace the legacy solution, without losing any existing functionality.
Required an interfacing solution where little programming knowledge was required to develop and maintain interfaces.
Sought a vendor with comprehensive availability to support continuous data activity and to limit down-time if support was needed.
Wanted to improve on auditing and data base writing capabilities and the ability to flexibly accommodate HL7 and X12 message structures.
Wanted an integration engine with the flexibility to do something custom that wasn’t a part of the interoperability solution.
Replaced legacy engine with Corepoint Integration Engine. Using Corepoint Health’s interface engine, North Kansas City Hospital is successfully maintaining interfaces to applications such as Cerner, McKesson, Dictaphone and Softmed, in addition to other applications.
Corepoint Integration Engine has supported North Kansas City Hospital’s objectives by:
Improving upon the auditing and database capabilities without compromising the functionality of the legacy engine.
Providing 24/7 support availability for interface conversions and development and providing help and resolution in a timely manner.
Delivering custom, one-on-one training at Corepoint Health headquarters.
Creating a multi-client receiver gear that allows the systems to connect and receive multiple inbound results from wireless vitals devices.
North Kansas City Hospital Insights
Kelley McFarland is the interface analyst at North Kansas City Hospital. Kelley offers her insights:
“Corepoint Integration Engine is easy to use and it is intuitive. Even when you don’t know how to do something, you can find information in the help files or online user community.
One thing I really like, that makes it so easy to develop interfaces, is the ability to test messages while building interfaces before saving anything. That is one of the most valuable shortcuts I have experienced with the interface engine.
We have called support as needed since purchasing Corepoint Integration Engine and our experience has always been positive, with fast and thorough resolution. We have also scheduled upgrades with the assistance of Corepoint Health support and have been very pleased with that as well.
We recently had a visit from Phil Guy and Dave Shaver. They sat down with our interface team and discussed any questions that we had as well as things that we would like to see in the integration engine in the future. In my experience, it is unique for a company CEO and CTO to visit and just sit down for a chat with users to get their insight and feedback.
There are a lot of changes that will be coming our way with Meaningful Use, and I expect a lot of interface needs in the future. Corepoint Health will be in the center of these changes, delivering at each step of the way.
Our integration engine will always play a very important role in our IT plan, because it will always be necessary to move information from system to system, both inside and outside of the hospital. With Corepoint Health, we are confident that we will be able to meet future healthcare interoperability requirements.”