Judith Faulkner, founder and CEO of Epic, is warming up to the media according to an interview in Forbes by Zina Moukheiber (see: An Interview With The Most Powerful Woman In Health Care). Here's the reason that she offers in the interview:
I’m recognizing that when we were small, we could stay under the radar, but now it’s harder. I get so many requests for interviews. If I talk to everyone, we can’t do our job with our customers and work on our software. It would be hard to stay focused.
Here's one of the many reactions to the piece by David Shaywitz, also of Forbes (see: Two Quick Reactions To Epic Faulkner Interview: SV Should Show Judy More Love; We Should Shouldn't Let Hospitals Off Hook)
Interoperability issues associated with Epic may reflect tacit preferences of hospital systems. Tory Wolff and I have discussed the interoperability challenges associated with Epic, and it’s potentially negative impact on the innovation ecosystem (see here and here). Faukner’s comments don’t particular assuage my concerns, but certainly highlight Epic’s laser-focus on delivering what customers want – and make no mistake, the customer isn’t the patient but the hospital. This is critical to appreciate. Thus, while it’s easy (and appropriate) to critique Epic for impeding data sharing, it’s probably also important to remember that if hospitals were all that keen to share data better, I suspect Epic would rapidly find a way to accomplish this. It’s almost as if Epic provides hospitals with plausible deniability. While it may be convenient to blame EMRs in general, and Epic in particular, for data access challenges, I suspect we also need to dig deeper, and hold hospital systems themselves far more – what’s the word? – accountable.
I couldn't agree with Shaywitz more. In fact, here's a quote from my note of September 14, 2011 (see: Judith Faulkner, EMR Interoperability, and Washington IT Politics)
Now comes a little secret that is not discussed much. Hospital CEOs and CIOs have little interest or enthusiasm for multivendor interoperability, either within their hospitals or hospital systems or across the outside hospital systems that they compete with. Customized interfaces between heterogeneous systems are a pain in the rear-end for the CIOs. They would thus rather have shrink-wrapped integration delivered by a vendor like Epic, the so-called "enterprise solution." Moreover, CEOs don't want to encourage broad patient and clinical data portability because it gives the payers (insurance companies and the federal government) a strategic advantage during negotiations about reimbursement.
So, when the feds raise the topic of interoperable EMR software, most hospital CEOs and CIOs will stand up and cheer. However, when they go out to purchase EMR software, they largely select Epic, particularly the larger ones that can afford it. Faulkner provides the non-interoperable product that they really want. She can also runs political interference for them. She donates generously to the Democratic party, she is tight with the Wisconsin congressional delegation, and takes no prisoners in her political feuds (see: Epic Flexes Its Political Muscle in Wisconsin with Boycott). And she can now try to block any inconvenient initiatives in the arise in the Health Information Technology Policy Committee.
Epic will provide some measure of interoperability to her hospital clients but slowly and most efficiently among Epic client hospitals. This is what her hospital clients want and this is what she will give to them. Here are the (slightly garbled) Epic "rules of the road" in terms of working with other HIT vendors, quoted from the Forbes interview:
We don’t let anyone write on top of our platform, come read our code and study our software. I worry about intellectual property at that point. With our customers, we make sure we have signed agreements. They know they have to respect our software. Customers can do it in a controlled environment, but not the whole world. You’ll see us do more and more of that.
Comments