HIStalk Interviews Bert Reese
Bert Reese is senior vice president and CIO of Sentara Healthcare of Norfolk, VA.
You’ve been at Sentara forever. What’s the secret to CIO longevity?
I think the secret is to make sure that the technology is aligned with the enterprise, both the clinical and business initiatives that the company is addressing. So the closer the IT is aligned to the business and the more you are able to deliver on that, the more successful a CIO would be.
Sentara was mentioned recently for developing its own interface from Epic to Picis LYNX. Tell me a little bit about that project.
We were a Picis LYNX customer before we did Epic. The problem that we were trying to solve with LYNX was our inability to code properly in the ED, and therefore, our billings were inaccurate.
What the Picis LYNX software did for us, prior to Epic, was give us the ability to properly code the patient during the visit. We saw that in the old world, prior to LYNX, that we were under-coding, which actually meant that we were understating our revenue potentials from the ED, and from a clinical perspective, not really indicating the proper problem that the patient was being treated for. With the LYNX software, since it’s a logical part of work in ED, it was more convenient for the nurses to code as part of the care process, so it’s worked out very well for us.
We went to Epic, and we wanted to preserve the capability of LYNX, so we developed an interface between LYNX and Epic to allow us to move information from Epic down to LYNX so that they could continue to use the coding software in a convenient way. One of the issues that you have is that nurses and caregivers don’t see coding as value-added to the care process; it’s more an administrative function. So when you want them to do something like that, if you can make it a byproduct of how you treat the patient. Then it’s a lot more convenient and they’ll do it. That’s what we did. It’s pretty straightforward; that’s the real secret sauce is in the Picis LYNX software.
Your EMR project is said to have cost $237 million. How will you measure its benefits?
That’s a great question. So it’s $270 million over ten years. The first thing was we set an expectation that a project of this magnitude goes out over an extended period of time and that you have to set the expectations of the company that they will be spending this kind of money for awhile.
The second piece of it is that when we started the project, we identified 18 major clinical processes that drive about a $35 million-a-year annual return of investment. We have identified those, we have four of our eight hospitals up, and we have seen benefits this year – `09 – at around $16.7 million.
So we know from a dollars-and-cents perspective that electronic medical records do create economic value. If you take that $35 million over the $270 million investment, that’s like an internal rate of return of about 12.3%. That’s a good return of your investment.
The other part of it relates to clinical quality indicators. If you follow the clinical quality indicators and see some level of improvement in clinical quality activity — that is, you see the patients are being better cared for under electronic medical record — then there is that benefit as well.
We have seen great clinical quality. I’ll give you an example of one. In the old world, it would take 137 minutes for the doctor to enter a medication in the hospital before it was administered to the patient. Now, it’s less than five. And there’s tons of stuff on turnaround time and length of stay and things like that.
The key to this — in looking at the return of investment, you look for where there is hunting and gathering of information, i.e., you’re looking for the old paper chart and/or whether there will be hand-offs between one care partner to another care partner. That is where the opportunities are for both economic and clinical quality savings.
What are your overall impressions of the Epic system and its implementation?
First of all, in the way of background, I’ve got experience with Cerner, Eclipsys, Epic and GE’s IDX/Centricity, so I’ve seen a lot of them. I will tell you coming out of the chute that you can have the best software in the world, but if you do a sloppy install where you support it in an inappropriate way, you’re going to have a failure.
Part of the secret sauce is in the quality of the software. I would say the other part of the secret sauce is in the quality of the local IT staff. Then, the culture of the company who’s adopting the technology.
In the case of Epic, Epic is a superb piece of software. It’s not buggy. It comes very, very clean. They’re a very collaborative company. That makes it easier. It’s less mysterious on the IT side about what it is you’re going to get and what you’re trying to do with the software when you get it fixed, or an upgrade or something like that.
But I will tell you that the responsibility, ultimately, is at the hospital or health system level. They need to make sure they made the right investment in order to have a varsity team to be able to support an application, either in the Cerner, Eclipsys, or an Epic type of venue.
Did you use outsourcing for the implementation?
I used it in an unusual way. In the old world, I was converting from a TDS 7000 to Epic and I had a choice: I could either bring in new staff, or outsource staff to help me with Epic, or I could take my Eclipsys support and give it to an outsourcer — it will move my old staff to learn Epic.
I elected to do the latter. We hired Perot Systems to commit and run our Eclipsys environment for us while we took our old medical systems team, retooled them on the Epic toolset, and had them support the implementations. Perot is still with us today because we have a couple more hospitals to do on the Eclipsys side, and so they’ve been with me for about five years or so. They do a great job.
How have your IT strategies changed, or have they changed, with the economic climate?
First of all, I want to make a comment. What we’re doing is not about electronic medical records. In our view, in our culture, an electronic medical record — when you have it implemented, most organizations will become a technology-driven company, and our advice is: skate to where the puck is.
The puck is not being a technology-driven company. The puck is going to be when you are a data-driven company, meaning that in order to use the data, a prerequisite is to have the electronic medical record.
When you have the data, the advantage will go not to the organization that has the EMR. It will go to the organization who can convert data to information, to knowledge, to action the quickest both business-wise and clinically.
I’ll give you an example. In the old paper world, I could tell whether you had been in the hospital, whether you had pneumonia, and whether you had an antibiotic administered; but, I couldn’t tell you when I gave you the antibiotic. I can’t tell you the outcome. The outcome would manifest itself. Does it shorten the length of your stay? Did you have more doctors’ office visits at the end of your hospital episode? Because I couldn’t see across the continuum of care.
Now we know when we study the data that when you present with pneumonia in the doctor’s office or in the ED, and the doctor concludes that it’s serious enough that he wants to have you admitted, to onboard the antibiotic as soon as possible. So if I know you’re in the practice or in the ED, and I’m going to send you to the hospital, I’m going to give the antibiotic immediately, because we know that getting the antibiotic onboard will start the curative process, will shorten the length of stay, and shorten the subsequent doctor office visits that are required.
That improves the care for that patient and reduces the cost. You can’t do that without having the data. You can’t do that without having electronic medical record, so that when you decide to tell the care delivery team if you’ve got a diagnosis of pneumonia, "Give the antibiotic now," because you can communicate it electronically to all sites — you can’t do it without that.
So the electronic medical record in our view is, "Welcome to the starting line." It’s going to revolutionarily change healthcare. As it relates to my current level of investment given the current economics, they’re giving us more money. They believe in what I just stated. They believe it’s all about data and the new information that will be created.
So if I was going to summarize it for you: electronic medical records improve quality and make money and they position you for extraordinary opportunities that you’ve never imagined.
You have to have administration that supports that concept?
Yes, absolutely. I think what the role of IT is in the future is that a lot of times, our customers are a rearview mirror. They’re not a guide to the future. So a customer, perhaps, would have never invented the television set, the microwave, the iPhone. It was technologists who invented those technologies and innovations, right?
And so it is the role of technology in the enterprise or in the health system to create a new reality for the company based on the technologies that are available. That’s a big statement. I don’t wait for my administrative staff to create a new reality. I, because I understand the technology, create a new reality on their behalf.
Back to your first question about how it is that you last so long as a CIO in the organization, it’s because I’ve been able to innovate in front of the company to improve what it is that they wanted to do.
Tell me about your internal work with standardization.
You’re right on point. That is part of the secret sauce. If you’re going to report on data, that means that you have to call the same thing the same thing across the enterprise. So a chest bilateral is a chest bilateral, not a chest x-ray. And, more importantly, you have to have the same lab normal values across the enterprise. One pathologist may say with a CBC, "This is a normal value," and another pathologist may say, "That is a different value from the normal limit."
One of the discussions you have to have early on is — what are you going to call things? What will be the standard of practice within the enterprise? So from the Sentara perspective, we are heavily standardized. We took a page out of the banking business back in the late 80s, early 90s where bank mergers took place and went through a heavy standardization. You’ve seen it with stimulus packages and banking consolidations. We took a page out of how they did their conversions and we decided to go that way.
When we affiliate with a new hospital or a doctor’s group, we bring them onto our standards suite with their application. In the case of my eight hospitals, there are no Norfolk General status set screens, there are no Sentara Careplex status screens; there are only Sentara Healthcare status screens. All those hospitals collaborate in what those screen flips look like, which means heavy dialogue, heavy participation, great collaboration, and a lot of fun.
How important are mobile devices for your clinical projects?
Not so much. The biggest extent of mobile devices we have are WOWs, workstations on wheels. Medical staff is not pushed to move them to phones or tablets or anything like that. At the doctor practice level, inside the practices, we experimented with mobile devices and we found, based on the workflow, that the fixed workstation worked best.
Let me describe that for you. If you’re a patient going to one of our doctors and you go into the exam room, you’re normally accompanied by the doctor’s nurse, who then logs on to the system and then enters your problem, enters any of your vital signs, any of your current meds, any changes in your physiology, and brings everything up to date. She then locks the workstation; she bookmarks where she is on your record, and locks it. When the doctor comes in to see you, he logs right on, right where the nurse picked up. So he doesn’t have to reacquire you as a patient, doesn’t have to ask any additional questions. He’s right where she left off, right where his workflow starts.
If he was walking from exam room to exam room with a mobile device, he’d have to log on every time and reacquire the patient. I wade through all the patients I’m going to see that day. And so we found it to be faster if the nurse does her work like she normally would, locks the workstation — he comes in, logs on, and he just picks up right where her summary of the information is and carries on the conversation with the patient. So mobile devices have been interesting for us, but that’s where we are right now.
Anything else that you want to add?
The only other thing I would say around community physicians and electronic medical record — there’s stimulus money out there for doctors that go up on electronic medical record. I would say to the hospitals and the health systems that they have a responsibility to guide that conversation in their communities that they reside on behalf of their community-based physicians. They should become the rallying point, they should become the center of truth, and to help the doctors with the decisions they have to make on the electronic medical record, because they have the capability of doing it.
What I don’t want to have happen is I don’t want a doctor, because he’s anxious about the stimulus money or losing Medicare funding, to make a knee-jerk reaction to a decision. I believe in the theme of better together, and I’d like to have my community doctors as close to us as possible so we can all go there together. And that if we make a mistake, well, we’d all make it together, and hopefully we’d have the power of crowds, maybe we’ll learn from each other.
I would encourage everybody to take on the responsibility of helping to guide the community physicians as to what they should do with the electronic medical record. There is certainly benefit for the hospital, but there’s also certainly a benefit for the patient. If you control the conversation or help guide the conversation, you’ll probably minimize the number of technologies that you have in your community. That means we can start to solve the interoperability problem when you have to hand the data off from a primary care doctor who’s on the XYZ system to a specialist who’s on another system, that the chances of that being done successfully and clinically correct is improved.
So I think the patient benefits, and then ultimately the hospital and the caregivers, because they’re able to have more information in order to care for the patient better. Ultimately, it’s all about the patient.
Going to ask again about HealWell - they are on an acquisition tear and seem to be very AI-focused. Has…