Frederick Memorial Hospital Q&A
Ease of use: 134 JCAPS interfaces replaced in less than 4 months
In 2014, Frederick Memorial Hospital in Maryland upgraded their integration engine platform from JCAPS to Corepoint Integration Engine. PAT (Port Address Translation) is a type of network address translation in which each device on a LA... More Whitmore, Senior Systems Analyst, has been using some iteration of DataGate/eGate/JCAPS at Frederick Memorial since 1999. Along with fellow System Analyst, Mutaz Awad, and a little guidance from a Corepoint Health Professional Services team member, they converted over 100 interfaces in 3 and a half months.
The following Q&A with PAT (Port Address Translation) is a type of network address translation in which each device on a LA... More Whitmore focuses on the experience of learning a new integration platform after 15 years working in a JCAPS environment, the features that helped make choice, and the impact a contemporary integration engine has had for Hospital Information System (HIS) is the main system in a hospital used by most caregivers. Sends AD... More hospital.
The following Q&A was conducted with PAT (Port Address Translation) is a type of network address translation in which each device on a LA... More Whitmore, Senior Systems Analyst at Frederick Memorial Hospital.
Summarize your experience selecting Corepoint Health, learning to use the engine, and converting over 100 JCAPS interfaces in just 3 and a half months.
We had been using JCAPS since it was STC (1998–1999). Once support for the product was to be sunsetted, it was time to find a replacement. Working with interface engines this long, we knew which engines were out there. As a MEDITECH shop we have a very active user forum to reference. That along with KLAS rankings helped us narrow our list. So the fact that Corepoint Health had been #1 the past five years had to speak to something.
There was some trepidation in migrating interfaces from the programming environment of JCAPS to the more drag and drop world of Corepoint. After seeing all the benefits Corepoint Health offered though, it was pretty easy to see that it would be worth it.
Alex from Corepoint Professional Services came on-site for 3 days, and he didn’t just do the work for us. He basically taught us to use the engine as we converted over 100 interfaces ourselves. We started with the easy interfaces and saved the hard ones for last. It didn’t take long to become proficient using the engine. As of the end of November (2014) we have converted or built 134 interfaces.
What were some major factors that led to choosing Corepoint Integration Engine during evaluation?
One of the things that really stood out to us was the derivative builder. It was mind-blowing how easy it was to create a derivative. Working in a MEDITECH environment, we are surrounded by the need for derivatives since MEDITECH doesn’t always “play nice” with standards.
The monitoring tool really stood out from other engines we were evaluating as well, and the testing features make it really easy to debug code.
After using JCAPS for more than a decade, was it difficult getting used to working with Corepoint Integration Engine?
It was a challenge at first, but you know, it wasn’t nearly as hard as I thought it was going to be. We were concerned that some of our harder translations would be difficult to convert. We had a few interfaces that were pretty intense, but we were able to work through them and figure it out every time.
For years I was used to just getting in there and writing code, doing things quickly from a command line. But there was so much code to write and you had to build in so many levels of error checking in java just to make sure it wouldn’t blow up for some reason while it was running. All that was eliminated with the move to Corepoint Health. It really sped things up for us to be able to just drop commands in without having to worry about writing conditional code to protect yourself.
Have any features had a particularly positive impact on workflow or performance?
Alerting in Corepoint Integration Engine has been very good, especially for queue-depth issues, which was already a weakness in JCAPS.
Also, anyone in the JCAPS world will tell you that monitoring is very limited. With the way Corepoint Health works, now we have a much better and more proficient monitoring process.
Troubleshooting is great. I can’t tell you how easy it is. I can get a call where someone says, “I sent this report from my system and it’s not showing up in MEDITECH, can you tell me what happened?” and I can find it and track its progress so much easier and so much faster than before. Just recently I got a call and needed to perform a task that in JCAPS would have taken 20–30 minutes, but with Corepoint, I was able to find the message, resend it and fix the problem in 2–3 minutes. Having Corepoint is such a big difference.
Anything else to add?
Just a shout out to the REST (Representational State Transfer) is a web services approach used heavily in social media sites... More of the eGate/JCAPS world—it’s time to switch, time to move on. There are better platforms out there. I think JCAPS users are going to find Corepoint Health to be a really great world to work in.