Meet growing data-exchange demands while maintaining business continuity and minimizing infrastructure downtime
UnityPoint Health is an integrated health system in the Midwest. Years ago, it had ambitious plans to improve and expand its patient care services but found itself handicapped by inconsistent support and excessive unplanned downtimes from its previous integration engine. Many of the downtimes resulted from an inability to prioritize maintenance and upgrades.
In 2011, the health system entered into a Joint Operation Agreement (JOA) with UW Health and Meriter Hospital in Madison, Wis., a Corepoint customer. During the JOA, UnityPoint Health decided to standardize its integrations on Corepoint, in large part because of Corepoint’s reputation for client support.
UnityPoint Health wanted to minimize downtime and automate many time-consuming regular maintenance processes. With two production engines with six nodes each, the IT team was spending a lot of time and skilled effort on maintenance.
Using more than one integration engine and maintaining them with various product and infrastructure updates, UnityPoint Health IT was spending a lot of time not only on updates but also managing interfaces in each system. With a growing healthcare system, UnityPoint Health knew that an enterprise approach was necessary to set things in place to support rapid interface development and a low maintenance future.
Why UnityPoint Health chose Corepoint
Corepoint lowers the barriers to interoperability by making interface building accessible to a wider range of skill sets. Corepoint integrates both the usual hospital data from ADT orders, results, scheduling, and charges, and the new data from biomedical device interfaces, which provide data at various volumes and rhythms. It not only captures, stores, and moves all that data, it also provides useful information about that data to those who need it most.
UnityPoint Health had approximately 300 interfaces and 600 connections when it started with Corepoint. Corepoint Support trained UnityPoint Health staff onsite on best practices as they shared the effort of setting interfaces and connections up in the integration engine. Since that time, UnityPoint Health has seen a 50% reduction in interface development time and cost. It now processes more than 13 million messages with Corepoint daily.
Using the Corepoint Administrative API
The new Corepoint Admin API allows organizations to interact with the engine programmatically, enabling them to retrieve important engine health information easily and manage their operations in a more holistic way.
The Corepoint REST-based Admin API makes it possible to integrate Corepoint with UnityPoint Health internal reporting and automation, and so feed engine and connection-state data directly into their centralized monitoring system.
The Admin API and PowerShell scripts enable the UnityPoint Health integration team to automate their maintenance, and to stop and start services. Even when dealing with Windows patching and reboot process for 12 servers, they have been able to go from two hours down to a total of 10-15 minutes for monthly patching.
“I can tell you about the satisfaction the team has now, from the ease of use that has been created by these processes,” Joe Hamilton, interoperability manager at UnityPoint Health, said.
Outside of maintenance automation, the team has used the Admin API to write to a database every time an alert happens that pages an on-call developer. This provides the ability to extract data and correlate the state of the engine and connections with the nature of the alert. They use Power BI to slice and dice the data, ensuring that they are driving at the problem connections and observing trends over a large time scale.
They also use the API to have Corepoint provide information itself, so they can audit the production engines from the test engines. And the knowledge the Admin API provides has helped the team dramatically reduce unplanned downtime.