CIO Don Reichert: Why OnBase and integration is important to MetroHealth

Hear Don Reichert, CIO of the MetroHealth System, explain why MetroHealth’s long-term vision for OnBase goes beyond clinical and business system integration to solve problems across the entire enterprise.

Video Transcript

Don Reichert, VP and CIO of The MetroHealth System

OnBase’s long term vision for MetroHealth is more than just a Vendor Neutral Archive. It involves clinical system integration; it involves business system integration as well. It’s looking at the whole enterprise and trying to solve problems of inefficiencies, eliminate paper, and by having a partner in this and having a clear vendor that can augment and assist in that delivery is extremely important to the Metro system.

The importance of having Epic and OnBase tied to our VNA solution is an extremely important one. First and foremost, we want to make sure that our clinicians have the access to the information that they need in a very logical, simplistic format. The last thing we want to have is that while they’re in front of a patient they’re spending a lot of time trying to dig and find information versus just having the information there.

So, our long-term medical imaging strategy is first and foremost to make it easier for our staff to access information. In addition to that, one of the things that we’re also looking to do is to remove the walls and barriers of the typical information that is shared. So, when you look at cardiology film or radiology film, it’s usually housed in their own environment. Our goal is to remove those walls, so that physicians, clinicians of any type will not have to go into multiple systems and can access any information tied via an API to a patient and therefore information is at their fingertips.

Even though we have policies in place, we never follow those policies. One of the things we felt that we needed to do is architecturally look at our solution and as information became older it moved from a priority 1 tier storage solution to a 3 as it aged. Less expensive. But then also at the same time we would put in place the ability that the data would have a “death” and we would take it out of the organization. It does a couple things; number 1 it keeps the most recent information fresh, but number 2 what it does, it also overall reduces our risk as an organization.

Because information is available to anyone even though it may have passed its life cycle, it’s still discoverable. So, we felt that in moving forward with this it would reduce our risk to the organization. In addition, it solves the cost to our solution from a storage standpoint, eliminating the constant, close to a million dollars a year, spend in storage that now we can do better forecasting and put money elsewhere in the organization to make our system better. We’re trying to simplify things, as I mentioned earlier, we’re trying to remove the walls of data.