The process of transitioning several hundred
interfaces from eGate to Rhapsody required MSHMC
to individually migrate their two sets of servers so
that if any unforeseen issues occurred, MSHMC
could revert its interfaces back to their current state
without affecting patients.
“We migrated the first interfaces one at a time,” said
Kruse, “but by the time we were finishing up, we’d
found ourselves migrating 10 to 20 interfaces at a
time because it was working so well and going so
smoothly. There were no problems whatsoever.”
Once implemented, Kruse was immediately struck
by Rhapsody’s visual programming environment.
“All my working life, I’ve heard people talk about
visual programming,” said Kruse. “Every health IT
vendor says their solution has helpful tools that
visually represent component details, control
structures, and more. With Rhapsody, you simply
put the components on the screen, connect them
together, and everything begins to flow. It just works.
I’ve never seen a tool do that. I’d never imagined that
Today, when an admission, discharge, or transfer
(ADT) notification’s fields from one EHR vendor’s
solution are presented in a sequence that doesn’t
match the sequence preferred by a different
EHR vendor’s solution, Kruse can easily make
adjustments within Rhapsody.
“The code is almost self-documenting, because
interfaces that come in at least weekly, sometimes
daily, and Rhapsody has empowered us to keep up
with the demand and satisfy our users.”
Further, when MSHMC acquired another Rhapsody
user, St. Joseph Regional Health Network, the
experience of onboarding the network into the
MSHMC system was completely straightforward—
much more, said Kruse, than it would’ve been with
“I just opened up the port and the IP and let the data
flow,” said Kruse.