One-on-One With Kings County Hospital Center Medical Director (and former CMIO) Abha Agrawal, M.D., Part I

So I think it’s better for the CMIO to report to the CMO. I think it’s better for the CMIO’s professional career and growth. I think it’s better for the CMIO not to be seen as just an ‘IT doc’ or ‘the doc who does IT.’ It has to do with how you look at the overall role of the CMIO in the hospital. The old thinking was that a CMIO is sort of a liaison or a bridge between the IT world and the physician world. And that’s fine when we were interested in just making sure the hospital does a reasonably good job of EHR implementation or workflow analysis or making sure the CPOE order sets are clinically realistic and meaningful. But as we grow and evolve, and as health IT becomes integral to the business of the hospital, to the operations of the hospital, the CMIO role is to be a leader, an agent for change. That vision is much bigger than this liaison and bridge business. You need to be able to lead, you need to be able to motivate, you need to be able to inspire, you need to be able to sell, you need to be able to make the clinical staff, the administration, the board believe in the value of health IT, show that you’re realistic, show that you’re confident.

So we look at the CMIO role in a larger context, on a larger playing field. I think that’s the playing field the CMIO has. A CIO has his or her own technical expertise around the infrastructure and hardware and the tremendous sophisticated knowledge about the intricacy of the IT integrated system. I had a great relationship with our CIO, we felt tremendous mutual respect. He could walk into my office, and I used to walk into his office all the time.

GUERRA: It sounds like you’re saying that someday — perhaps five, 10 years into the future — the CMIO role won’t be necessary because every CMO will have to be so steeped in IT that essentially both positions will merge into one?

AGRAWAL: No, not necessarily. I’m in this new job and I desperately need a CMIO, even having been one. I could have been so naïve to say I wouldn’t five months ago, but we just had a medical informatics meeting, which I used to chair as CMIO (which I’m still chairing until we find a CMIO) and there are projects that are coming up which I used to spearhead. Some of those projects were CPOE implementation, barcode med admin, physician documentation implementation. So I would chair a steering committee, workgroup or task force, depending on how big or complicated the project was. I was essentially the owner of the project. So it was my responsibility to make sure everyone was doing what they said they would do, everyone is making sure the timelines are met. I had project managers help, but I was accountable.

Now that we don’t have a CMIO, I’ll give you some practical examples of what happens. If you want to add some Web-based orders, there’s nobody to take ownership. The pharmacy IT person is saying, “I’m happy to do the configuration, but the doctors are not listening to me. They don’t come when I ask them to come for testing.” The IT analyst says the same thing. The physician or director says, “I’m happy to do the testing,” but there’s no owner of this project. So that’s part of the tremendous value of a CMIO. You need somebody who can own this, and I think the CMIO is really a very logical, very good owner of these projects who will make sure that everyone works collaboratively.

GUERRA: It sounds like sophisticated project management skills are so important to this role. Do you look for someone who has formal training in that area?

AGRAWAL: In terms of the attributes of a CMIO, I completely agree with you. It’s as important as their clinical skills and technical skills are, but far more important is to have interpersonal skills. I want the CMIO to play a critical role in transforming how we do business and bringing about a cultural change where they can make people believe in the value of what they’re doing. So they need great interpersonal skills to be able to talk to not just physicians but nurses, social workers, the CEO, the COO, the CIO. So that’s one very strong attribute.

They also have to be visible. I don’t think the CMIO should be a person who is happy sitting in the office and making sure all the technical and business aspects for CPOE, for example, are done and tested and carried out. They should be willing to go into different town hall meetings and other meetings and articulate why we should be doing different work, why we should be asking you to change the way you document, the way you practice, and what’s the value to the institution and to you.