Strategizing on IT for ACO Development
Keith FiglioliHCI: What has the dialogue been like among members of the workgroup?Figlioli: I think everybody involved in this ACO area is looking for answers. And we think about how long it took just to get the consensus on how to go forward on EMRs. And I think it’s a very similar analogy to what’s happening in the ACO market on all fronts. Specific to the CIO, they’re getting the message from higher-ups that they have to facilitate this work; but they need clarity about what the phenomenon is. We’re talking to some folks who want to move forward on the ACO front but who aren’t even stable yet in terms of EMR development.So part of the creation of this model has to do with helping people with baseline issues. For example, if you don’t have a standard EMPI [enterprise master-patient index] across all your systems, don’t even think about ACOs. And in terms of HIE [health information exchange], there are multiple layers to what that means. There’s one layer specifically proprietary to your provider, so that you first have to simply get your own house in order, before you can go regional. And what we’re trying to do with ACOs is what we’ve tried to do with all our broad initiatives, and that is to really help our membership base get ahead of the curve in terms of the regulatory environment these days and overall in the industry.Randy Thomas: And CIOs know they’re going to have to be dealing with data sets that they don’t have to deal with today—particularly the connectivity with physicians and with the whole payer side of the equation. And how do you do the types of business modeling and clinical performance measurement, and so on? We’re hearing from the CIOs asking us to help them figure this out. It’s hard enough in the acute-care space, but beyond that, in the non-acute space, the fragmentation is just extreme. And that’s why we’re working with IBM to collaborate on analytics. That’s the kind of work that ACOs will require.