CMIO Magazine: How has the CCIO role evolved for you?
Jerry: I studied Electrical Engineering to pursue my passion for systems design and improvement, and then Internal Medicine for the healing interpersonal connections it provides. An informatics fellowship brought these elements together, and started me on the course of helping to address pressing performance challenges in our healthcare system through better clinical information management. Initially this played out through independent consulting, then working with the American College of Physicians, and then with a start-up that was subsequently acquired by Micromedex (a clinical decision support company known to many of your readers) in 2002.
In 2003, I was appointed to the newly-created CCIO position to help accelerate the evolution of Micromedex from a vendor of clinical knowledge bases to a provider of clinical performance improvement solutions. Over the next several years, several businesses within Thomson Corporation (now Thomson Reuters) came together to round out the performance improvement portfolio. For example, with analytic, benchmarking and reporting solutions from Medstat and Solucient, and workflow solutions from MercuryMD. So, during the last 6 years the role has grown with the organization, i.e. guiding the development and dissemination of a broad array of services and tools to help our customers realize measurable performance improvement. There may be something of a parallel here with some CMIOs in provider organizations, whose roles have grown along with their institutions.
CMIO Magazine: How would you categorize your roles and responsibilities as CCIO?
Jerry: I’d say it starts with our customers and the tremendous performance challenges they face, and works backwards from there. At a high level, my role is to help ensure that we fully leverage our assets and capabilities in helping care delivery organizations provide care that is safe, high quality and cost effective. That includes helping to enhance, communicate and deliver on our value proposition, which involves working closely with our strategy, product management, marketing, sales and services functions, among others. My personal expertise is focused on clinical decision support, so I work particularly close with that part of our organization. For example, making sure we get the right information to the right person in the care delivery team (including the patient), in the right format, through the right channel, at the right point in workflow – to support better decisions and outcomes. So I help enhance and disseminate our current CDS solution portfolio which includes applications for clinical surveillance, order set management, alerting, reference information and workflow support, and many others. I also work closely with the part of our business that provides performance benchmarking, analytic and reporting solutions, which are important to measurable performance improvement. There’s interplay with these issues and the Payer side of our business, and I work closely with those teams as well.
Complementing this customer-facing work is fairly deep engagement at the national level on efforts to ensure that CDS is fully leveraged to drive widespread performance improvement. This includes helping develop roadmaps for national action on CDS, publishing guidebooks to support successful CDS deployment and the like. Of course there are great synergies between these customer-facing and national efforts – each supports the other. I collaborate with many provider-based CMIOs in this national work who similarly realize synergies with their ‘day jobs,’ again reinforcing the parallels between the CCIO /CMIO roles in vendor and provider organizations.
CMIO Magazine: Who do you report to?
Jerry: Currently I report to the Executive Vice President who oversees our CDS business unit, and he reports to the CEO of our Healthcare and Science business. However, as I noted earlier, success in my role as CCIO for a vendor (as with CMIOs in provider organizations), is largely defined by the ability to coordinate, guide, and support many diverse functions across the business.
CMIO Magazine: If the CIO is clinical, is there a need for a CMIO?
Jerry: I think the functions are different. My sense is that the most effective CMIOs take a more cross-functional approach to leveraging technology to measurably improve key organizational outcomes. CIOs are typically more directly responsible for the care and feeding of the technology itself – though clearly they too need to be sharply focused on the organizational value. I would imagine that a typical CIO would not have the bandwidth or focus to pay full attention to the details of HIT-enabled quality improvement (and evaluation of these efforts) as a CMIO should.
CMIO Magazine: from CPOE and EMR perspective, do you see a value behind it?
Jerry: in short I would say “Absolutely yes”. There is a huge upside for CPOE and EMRs. That being said, it can also backfire if not implemented correctly, since the modifications it causes in workflow are substantial and complex. We’ve written about keys to success – focusing on the CDS components of these systems – in the implementer’s guidebooks I mentioned earlier. These success factors include working with the users of these tools to jointly addressed shared goals, rather than doing the implementations to them. This is a lofty goal, but the most successful implementations come closest, while the most problematic are often the farthest. The technology is a means to an end, not an end in itself, so the ends need to be explicit and shared, and guide implementation at each step. We need to ask, ‘what are the stakeholders’ goals, and how do we best leverage the technology to achieve them?” For example in many cases, implementers focus excessively on intrusive alerting – instead of leveraging the full complement of CDS interventions – which results in end-user frustration, overrides, and failure to accomplish the desired objective (such as reducing ADEs). Effective CMIOs ask the right questions, drive toward shared answers, and support technology execution that delivers results.
CMIO Magazine: Any closing remarks?
A little more about my title – we decided to use ‘clinical’ and not ‘medical’ to emphasize that the role’s scope extends beyond matters pertinent to just physicians; my role addresses the needs of all care delivery stakeholders. Similarly, the term ‘informatics’ is used to emphasize the critical importance of people, process and technology in supporting the improved outcomes the CCIO role helps drive.
I’d conclude with the assertion, echoed in your other writings, that at its core, the CCIO/CMIO role is about driving meaningful and measureable improvements in key organizational and patient outcomes. Our success really is a matter of life and death; for our organizations, the patients they serve, and ultimately for the broader healthcare system.