Not satisfied with accepting the storage solution offered with McKesson's PACS, Steve Huffman, director of IT at Memorial Hospital in South Bend, Ind., challenged the software company to partner with IBM and come up with a uniquely designed solution. The non-profit, 526-bed regional referral center went live with IBM's tiered storage solution and McKesson's PACS last November. HCI's Stacey Kramer learns about the processes and challenges involved in the implementation of both solutions from Huffman.
I see that you were previously using an "in-house" PACS system, when did you know you were hitting the ceiling as far as its functionality?
PACS systems change very frequently and new functionalities come out all the time. Our existing PACS system worked fine, but we were hitting a support limit. We've had our previous system for five years, so we needed to either upgrade to the newest and greatest version, which was essentially a forklift upgrade, or replace it. In the end, we opted to replace it.
What was the rationale behind replacing the system rather than just upgrading the existing technology?
It was costly. I mean, literally it was a forklift upgrade. It was a fairly substantial software change, and so the question came up, 'If it's that big of a change, should we look at other products in the market?'
Can you tell me about the process you went through to select IBM, why did you select IBM over EMC?
We're an IBM shop, so the majority of our data center is IBM. We do have EMC and it's a great product, but what we challenged McKesson with is to partner with IBM and Memorial to come up with the configuration that we had, which in the end, they did.
I want to make sure that it doesn't come across that Memorial doesn't like EMC products, because we're an EMC customer as well, and it works very well. For our support needs, IBM just felt more solid from a disaster recovery standpoint. The solution IBM had at the time had a much stronger disaster recovery solution that we're now implementing, and we felt a lot more comfortable with the IBM product for this solution.
Why did you choose to create a storage solution and not just go with the initial system offered by McKesson?
At the most rudimentary level, PACS is keeping electronic images for radiologists and referring physicians in an organized, easy to retrieve electronic warehouse. McKesson or any other PACS vendor provides a boiler plate storage solution, which is what McKesson does. We went back to challenge them, along with IBM, to come up with an IBM storage solution for McKesson PACS.
It was a challenge getting over that first hurdle of getting those organizations to work together to a great solution.
Did you ever consider going with another PACS vendor?
In the very beginning of the reevaluation process, we looked at a number of different vendors, but we went through what I would refer to as Memorial's normal process of vendor selection. It just wasn't a, 'McKesson offers it, so we're going to buy it from McKesson'.
Do you have a long-term strategy for having images from your PACS flow into an electronic medical record system?
The eventual strategy is to have a medical record and have all necessary medical information housed in that electronic medical record. There's a million integration points that any hospital would say 'Boy I wish that would integrate better.' We, as every hospital does, just continue to plug through those integration points. The long term strategy is to have those images tied into electronic medical records.
Get the latest information on Health IT and attend other valuable sessions at this two-day Summit providing healthcare leaders with educational content, insightful debate and dialogue on the future of healthcare and technology.