One-on-One with Lutheran Medical Center CIO Steve Art, Part II | Healthcare Informatics Magazine | Health IT | Information Technology Skip to content Skip to navigation

One-on-One with Lutheran Medical Center CIO Steve Art, Part II

May 21, 2009
by root
| Reprints
In this part of our interview, Art talks about managing user expectations when replacing a niche system with core clinicals.

Lutheran Medical Center (LMC) is part of Brooklyn, N.Y.-based Lutheran HealthCare, an organization which also includes the Lutheran Family Health Centers network and Lutheran Augustana Center for Extended Care & Rehabilitation. LMC is a 476-bed Level I Trauma Center providing ambulatory surgery, cardiac care, neuroscience services, obstetrics/gynecology, spinal surgery, perinatology (maternal/fetal medicine) and oncology (cancer diagnosis and treatment). Recently, HCI Editor-in-Chief Anthony Guerra had a chance to talk with CIO Steve Art about his facility’s plans to implement the VA’s VistA open-source software supported by MedSphere.

Part I

AG: And that would be a core EMR that also is useful in the ED?

SA: Correct. It doesn’t make sense to have multiple systems. So although we needed ED system for a number of years – and I don’t remember what year I bought that thing – when we bring up the new EMR, it will replace the old departmental EMR.

AG: Is it inevitable that, because you’re going with a wider system, you will lose a bell or whistle or two from that particular ED system? Will the ED folks balk at that loss of functionality?

SA: Absolutely you are right, that was a concern of mine. I told the ED early on that I would not make them move unless I can give them all the functionality that they had today. And that’s what we did. We started out with some kind of analysis system side by side to see what the gaps were, and we realized that the new system actually was going to give them more than the old system. It had much more functionality than the old system did, but there was one piece that was missing, and it was a tracking board.

There is a board that when you go in the ED and an outside attendant comes in, he can find out the bay or room the patient who he sent is in. So if you want to know that your patient is in 812, you go to the board, you find your name, you find the patient’s name, and you go to 812 and find your patient. So that component was not part of the system I bought. What we’re doing is we’re developing with my open-source vendor, the tracking board here, and then I will give it to them, they will QC it, and incorporate it into the product for all of their clients. That’s the cool part about open source; I have the software and I can develop it.

AG: So it sounds like CIOs have to be sensitive about taking away functionality from departments when they replace niche systems with larger core rollouts?

SA: Yes and the only caveat to that was all EMR systems require you to use their pharmacy, because pharmacy is the one piece that is a whole closed loop. You have to make sure that you’ve got the right drug to the right patient at the right time and all that the orders that flow into the pharmacy flow out correctly to the patients. I believe all of the vendors require you to use their pharmacy.

So this whole decision turned on the fact that I had to get the pharmacy to agree that the new system was no worse than their current system, or I couldn’t have done it at all.

AG: And were they on McKesson? The pharmacy?

SA: No, they were on Mediware. They’re still on Mediware. They are on the Mediware Pharmacy and they were the only ones I actually had to change because I could have figured out interfaces for all the others. The other ones were manageable. Pharmacy was absolutely critical to the process.

AG: So you’re saying they’re not on Medsphere pharmacy at this point?

SA: No, I’m not on Medsphere yet. I’m going to it. I’m going live. We don’t have the final lease of it yet.

AG: Okay, but you will be going to Medsphere pharmacy?

SA: We will be going to Medsphere pharmacy, yes.

AG: Because you’re saying you can’t go to a new system and not take the pharmacy?

SA: Yes. In our case, our labs guys objected, they didn’t like the lab system that Medsphere had. So we’re writing interfaces for them so they can stay on the SunQuest pharmacy product. The old Sunquest pharmacy is what we had here, and they're staying on that lab system. We built an interface between the lab system that’s in Medsphere and the lab system I have here, so people will order labs in Medsphere and labs and orders will go over to the lab system and the results will come back.

But pharmacy I couldn’t do that with. Pharmacy, we had to use the Medsphere Pharmacy. Like I say, I think that’s universally true of all EMRs, you have to use their pharmacy.

AG: Do you think it’s a losing argument for CIO to say to a department, ‘I’m switching you off your current system to another system, it’s better for the organization, but you’re going to lose some functionality?’ Is that too hard to sell to make?

SA: I always say it’s their decision. I always try to lead every department to the correct decision. I think I know what the correct decision is in terms of how these things all work together, but I try to give them the information that they need to make the decision, because if you tell them what you want them to do, most people won’t do it. You have to let them decide it. I try to give them the information they need and that’s what the process is, to bring these systems in, to let the departments make that decision. If it’s not a good decision for the department, then it’s not a good decision for anybody.

AG: That’s a good point.


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.

Learn More