Behind the Scenes: Crucial Work on 3rd-party Applications

Christopher Carroll, Director, Ancillary Applications, UConn HealthONE (Photo by Chris DeFrancesco)

The HealthONE Epic software does not work by itself, it relies on a number of third-party systems and must integrate with these non-Epic systems.

Between existing and new systems, the HealthONE directors, with support from Procurement Operations and Contracts (and sometimes Epic), had to negotiate contracts with about 70 vendors. We’re close to having these contracts finalized, which is a major milestone.

More than 40 of the 70 systems required test systems to be in place. This would allow the interfacing between Epic and the third-party system in a non-production environment, while the current production systems were left intact.

Once the contracts were signed, we were able to get started on many mini-projects. This involves project teams including:

UConn Health One badge

  • Departmental subject matter experts (SMEs)
  • Server team
  • Desktop team
  • Networking
  • Project managers
  • Analysts
  • Clinical engineers
  • Integration specialists
  • Vendors

When a test system was needed, we assessed and ordered the hardware, and put a test system in place. When necessary, we initiated project upgrades.

What Do They Mean by That?

See this guide to HealthONE terms.

It’s a complex task to move through these steps. If information is to flow accurately between HealthONE and the third-party application, often there is “translation” work involved, since architecture in each application is different. This translation of the data requires considerable analysis. We built and tested interfaces, with a deadline for all the test systems and functionally tested interfaces to be ready at the start of the Integrated testing, July 31.

All this was done while balancing the other normal hospital functions, other Epic-related SME responsibilities, Epic build, and testing. SMEs from the departments have been, and will continue to be, involved in validation of the interfacesd test results. Validation will continue as the project progresses.

As you can see, it is a true team effort across UConn Health. Just as “Rome was not built in a day,” nor will be the HealthONE project.

–Christopher Carroll, Director, Ancillary Applications, UConn HealthONE

Watch for additional HealthONE updates in Lifeline, in the Pulse, and at uconnhealthexpress.uchc.edu/emr.


This entry was posted in EPIC.