How CliniSys uses Rhapsody
CliniSys embeds the Rhapsody Integration
Engine into its solutions to translate and
transform clinical data.
“Out of the box, Rhapsody brings us all the
goodness that an integration engine should,”
Markham said. “We know immediately we’ve
got guaranteed message delivery. We’ve got
the availability. We’ve got the performance.
We’ve got the resilience.”
Using Rhapsody, CliniSys can deploy a series
of communication points, routes, and message
definitions onto every site, creating touch points
back into its core products. “We then look at what
the customer needs so that we can drop specific
interfaces — which are bundles of communication
points, routes, and filters — that serve a specific
purpose,” Markham explained.
More specifically, CliniSys exposes functionality
through a series of APIs. “We use Rhapsody to talk
to those APIs on one side, and we’ll use Rhapsody
to talk to other systems on the other side,” Markham
said. These could include a patient administration
system, results reporting system, vendor-specific
system (such as NPEx), or national reporting system
such as the cancer registry.
CliniSys also partners with other health IT vendors
that require specific interfaces. Using Rhapsody
allows them to create a building-block approach
for repeatable configurations across sites,
Markham said. “Rhapsody reduces the deployment
time and testing time and creates a much more
robust and resilient solution.”