Wyoming Medical Center Case Study
www.wmcnet.org Casper, Wyoming
“Corepoint Integration Engine is a great product, very well designed and intuitive to use. It’s actually fun to develop interfaces.”
Wyoming Medical Center is a 209 bed not-for-profit (501c3) acute care hospital in the center of Wyoming. The campus covers approximately four city blocks with 912,109 square feet of space. Our central location in Wyoming is convenient and easy-to-access for the thousands of patients we are entrusted to care for each year. With its 192 physicians on staff, Wyoming Medical Center offers more than 50 specialties with two Centers of Excellence: The Heart Center of Wyoming and Wyoming Neuroscience and Spine Institute. Both centers have received national rankings and recognition for quality measures, outstanding care and service
Interview with Julie Pratt, Integration Analyst, Wyoming Medical Center
What were the most important criteria to you in a new integration engine vendor?
Pratt: “Our previous interfacing solution was a good product, but it was always difficult for me to develop new interfaces using it. I didn’t find it easy to use, and it had a high learning curve. The product was going to be eventually sunsetted, and the vendor’s replacement product didn’t appear to be any easier, so we decided to explore other options.”
What led to your decision to evaluate Corepoint Integration Engine as an integration solution?
Pratt: “I heard about Corepoint Integration Engine from another Corepoint Health customer and she gave it rave reviews. I did a site visit to their facility and really liked everything they had to say about the software. They had also replaced the same legacy engine we were looking to replace, so it helped to compare apples-to-apples. She showed me how easy it was to build an interface, and the number of interfaces they converted in a short amount of time was mind boggling for me.”
“We compared Corepoint to another product and, in a side-by-side comparison including customer recommendations, Corepoint won hands down. Shortly after, we began the process to replace our legacy interface engine with Corepoint Integration Engine.”
What features influenced your decision to select Corepoint Integration Engine?
Pratt: “The interface development using Corepoint Integration Engine was what sold us on the product. That was huge for us. And, the fact that it won the KLAS® award for interface engines market spoke volumes to us as well.”
“We also found Corepoint Health was a solid value. We liked the high availability solution Corepoint offered, their version control functionality, the monitoring tools and the supporting documentation. I have found the documentation is incredibly extensive. I always remind myself – just hit the “F1” key, and I can always find what I need!”
“Now, we’re able to distribute the monitoring to some of our super users; for example, the pharmacist who handles the pharmacy systems we interface with can view his connections, review his logs and do some of his own troubleshooting. That’s a very nice feature we have not had before. The graphing is useful, the ability to filter and find specific messages easily is very helpful, and the interface alerting tools are great as well.”
How was the adjustment in building interfaces with Corepoint Integration Engine?
Pratt: “Corepoint Integration Engine exceeded our expectations. During the replacement process we were also implementing CPOE, or a computerized physician order entry system, as a part of Meaningful Use. Implementing CPOE meant we would change our ordering system. Therefore all the orders interfaces needed to be rewritten at the same time we were converting all the other interfaces for the interface engine conversion. At first I was overwhelmed, thinking it was too much. However it turned out to be a non-issue because we were able to convert the interfaces so easily.”
“Being able to manage all these different interfacing projects easily is the incredible value that Corepoint Integration Engine delivers.”
What are examples of applications you are connected to today?
Pratt: “Currently, we are connected to many McKesson applications and other products such as Sunquest Laboratory™, Midas+™, Omnicell® medication/supply stations, in addition to many others.”
Have you had any complex projects for which you have used Corepoint Integration Engine?
Pratt: “There was one complex project where we had 18 interfaces that needed to go into production simultaneously. If an allergy was entered in one system it needed to go out to several other systems, and vice versa, and a number of other interfaces piggy-backed on those. Because they were all related and for ease of testing, I decided to convert all interfaces and coordinate the production for the same time.”
“Corepoint Health support helped with the more complex interfaces, but the development of the others went quickly and the production turned out to be a non-issue. Taking the interfaces live with Corepoint Integration Engine was so easy that we experienced no problems. It would have been very difficult to do this same project using our previous interface engine.”
Have you or your team had any experience with the Corepoint Health support team or professional services team?
Pratt: “Our experience with Corepoint Health has been great. The implementation team from Corepoint who converted some of our interfaces, trained us and now continues to educate us has been wonderful. I’ve had to call support a couple of times, and they’ve been outstanding in helping us solve issues. They’re also proactive in their approach, which means a lot to us.”
One example of where Corepoint Health’s support team proactively helped was in our test environment. One system was sending us empty messages and it caused the engine service to stop. Thankfully it was on the test server and the downstream vendor eventually fixed the issue so I basically forgot about it. However Corepoint Health pointed out that the original problem should not have caused the system to stop and they wanted to make sure the problem wouldn’t happen again. Even though it wasn’t an issue with us anymore, Corepoint wanted to figure out why it happened. That really impressed me.”
What has your experience with A2 been like?
Pratt: “We haven’t needed A2, or Assured Availability, for its intended purpose but we have been able to leverage the functionality of A2 for other projects. Just a few weeks ago we were having an issue and we purposefully failed over to A2 while we re-booted the primary server and then returned the processing back to the primary server. During that process, not a single message was lost. The native high availability functionality in Corepoint Integration Engine delivers flawlessly.”
“We decided to purchase the A2 solution because of the importance of the data. We had lost data with our other interface engine, important data like pharmacy orders and lab results. When you’re talking patient lives, you can’t lose data.”
What advice do you have for a peer evaluating their integration environment?
Pratt: “They need to decide what their priorities are in an integration engine and look at the various products. I think Corepoint Integration Engine is a very, very good product. Honestly, I don’t know if you could get a better product if you paid more. Corepoint Integration Engine is a great product, very well designed and intuitive to use. It’s actually fun to develop interfaces. I enjoy my job again.”