Virginia Commonwealth University Health System (VCUHS) is an academic medical center that has served the Richmond, Va. area for more than160 years. The VCU Health System’s academic mission supports and is directly linked to Virginia Commonwealth University. As the clinical delivery component of the VCU Medical Center, VCUHS is a regional referral center for the state. MCV Hospitals is the teaching hospital component of the VCU Health System, which also includes several outpatient clinics and MCV Physicians, a 600-physician, faculty group practice. Also included in the system is the 779-bed Medical College of Virginia Hospitals (MCVH) and VCU’s Massey Cancer Center, a National Cancer Institute designated facility. The VCUHS treats more than 80,000 patients annually in its emergency department, which is the region’s only Level I Trauma Center. Recently, HCI Associate Editor Kate Huvane Gamble spoke with Alistair Erskine, M.D., who serves as CMIO and Internal Medicine Hospitalist at VCUHS, about his role with the organization, his thoughts on pushing forward during tough economic times, and how his organization is leveraging technology to improve the safety and quality of care.
KG: Our target audience is CIOs, and while a number of them have a CMIO at their organization, there are many that do not. For their benefit, can you talk a little bit about your role?
AE: It’s probably a formulization of the physician champion component of clinical information systems. It’s taking somebody and protecting their time so they can spend more time wrestling with the translation of what the clinicians really need into IT specifications. And then in the other direction, making sure all the work IT is doing is well-marketed and communicated out to the physicians.
KG: While still seeing patients, at least in your case.
AE: Yeah, on average I do about two weeks of wards for 15 days straight, anywhere between every other month or once a quarter. And recently it’s been more than usual, so that ends up being in terms of, if you look at full-time equivalent, somewhere between 30 or 40 percent of clinical practice.
The big joke with CMIOs is you’re 30 percent clinical, 100 percent CMIO — so it doesn’t quite add up.
KG: So there are definitely several different components of your job.
AE: It’s interesting also because a lot of people wrestle with 'Do I give up clinical practice?' Because it really ends up being a full-time job. And I think if you look at the Gartner survey, somewhere around 75 percent of CMIOs continue clinical practice. It has a lot to do with the system you help design. When you go into your practice, you either realize that it works, or realize you didn’t know what you had done. I’ve put some rules in place, then I’ve thought when I’m on the computer in front of the patient, 'what was I thinking?' And so I’d take it back out.
So there’s that, and there’s also the fact that if I’m on the wards and I’m a medicine consultant and I’m helping out my orthopedic surgeon, that is a very different conversation I have with him around clinical information system issues than if I’m on the other side of the fence as a suit, saying, here’s what you’re going to have to do. So it’s a lot of street credibility and just collegiality with the other physicians wearing a white coat as opposed to wearing a suit.
KG: So the clinicians respect you as a member of the C-suite, but they also feel they can relate to you a little more easily?
AE: Right. I’m on the board of the practice plan as well, so that helps in terms of the leadership aspect. We have 551 physicians in the practice plan — they’re all employed physicians of our health system, so we’re a little peculiar for an academic medical center in the sense that we don’t have any independent physicians that come into our organization. So if you work as a physician here on your credential, then you’re part of the practice plan.
KG: As CMIO, who do you report to — the CIO or CEO?
AE: I officially report to the corporate chief medical officer. I can tell you that I’m very lucky to have a very close and tight relationship with the CEO of the health system as well as the CEO of the hospital. And frankly, especially in the past few weeks, with the recovery act activity associated with health information exchange and effective use of an EHR, that activity has significantly increased as they’re trying to figure out how to position themselves as an organization, to maximize the dollars that would come in 2011 from Medicare and Medicaid.
My relationship with the CIO is, in a way, more of a peer relationship. It may be that we tackle certain problems together, whereby he may defer to me on clinical perspectives and issues, and I’ll defer to him on technical infrastructure issues such as servers, networks and desktops, and so forth. We sort of rely on each other for the different subject matter expertise when it comes to clinical versus technical issues.