Free Hospital EMR and EHR Newsletter Want to receive the latest news on EMR, Meaningful Use, ARRA and Healthcare IT sent straight to your email? Join thousands of healthcare pros who subscribe to Hospital EMR and EHR for FREE!

Epic Wants to Be Known for Interoperability – Are They Interoperable?

Posted on September 19, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit.

Epic has been fighting the stigma of being a closed system for a while now. It seems that Epic isn’t happy about this characterization and they’re coming out guns blazing to try and show how Epic is interoperable. They’re so interested in changing this perception that Epic recently hired a lobbyist to change how they’re viewed by the people in DC.

A recent tweet highlighted a slide from the Epic user conference (Epic UGM) that shows how many Epic patient records they’re exchanging per month. Here’s the tweet and graph below:

Farzad Mostashari asks a very good question, “Does that graph help?” I find Farzad’s tweet also interesting because just over a year ago Farzad tweeted another Epic interoperability chart when he was still National Coordinator at ONC. I’ll embed the previous chart below so you can easily compare the two graphs side by side:
Epic Data Sharing Chart

I think Farzad is right to be skeptical about Epic’s claims to interoperability. First, it seems Epic is finally making some progress with Epic to Epic interoperability, but Epic to Non-Epic systems is still far behind. Second, Epic loves to claim how they have charts for some huge percentage of the US population (currently about 314 million people). I bet if we looked at the percentage of total Epic charts that have been exchanged, it would be an extremely small number. I also wonder if the charts above count a full patient chart or something simple like a lab result or prescription.

I don’t want to harp on this too much, because this is a step forward for Epic. Even if they’re not as interoperable as they could be and as we’d like them to be, I’m excited that they’re now at least open to the idea of interoperability.

With that said, I wish that Epic would spend more time and effort on actually being interoperable and not just trying to say that they’re interoperable. This includes committing the resources required to support connections outside of Epic. I’ve heard over and over from health IT vendor after health IT vendor about how hard it is to get Epic to work with them in any form or fashion. There’s a way that Epic could scale their effort to hundreds of other health IT vendors, but they haven’t made the commitment to do so.

Think about the opportunity that Epic has available to them. They have enough scale, reach and clout that they could by force of size establish a standard for interoperability. Many health IT vendors would bend over backwards to meet whatever standard Epic chose. That’s a powerful position to be in if they would just embrace it. I imagine the reason they haven’t done so yet is because the market’s never demanded it. Sometimes companies like Epic need to embrace something even if it doesn’t drive short term sales. I think this is one of those choices Epic should make.

I’m sure that lobbyists can be an effective solution to change perceptions in Washington. However, a far more effective strategy would be to actually fully embrace interoperability at every level. If they did so, you can be sure that every news outlet would be more than excited to write about the change.

Pay at Epic – Did You Know There’s an Epic Reddit?

Posted on August 11, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit.

HIStalk recently pointed to a reddit post about the Salary, Raise and bonus structure at Epic. It’s a fascinating look at what you get paid to work at Epic. I’ll be covering that topic in detail on our Healthcare IT Today career blog. However, did you know that there’s a subreddit on Epic?

In some ways, I think this says a lot about how far reddit has come, but it also says something about the size of Epic and the type of employee they attract. The younger reddit generation is their hiring strategy.

The subreddit is quite interesting. They talk about things like lunch at Epic (cheap and good), what it’s like to be a mom at Epic, and even topics like whether you can have a tattoo at Epic. Although, this one talking about the creepy customer announcements made me laugh:

The customer announcements over the loud speaker are so bizarre. It makes me feel like I’m in a1984-esque reality with an unsilenceable propaganda machine.
I doubt they intend it to be this way, but it is all I ever feel when it occurs.
Does anyone not find them creepy?

Looks like they even preach the Epic culture over the loud speaker. I do like that their celebrating each customer win since an Epic customer win is a really big deal. Although, the description makes me wish I could hear one of these announcements.

The Epic subreditt isn’t super active, but I’ll have to keep an eye on it to see any other interesting topics that are started. Maybe start a few of my own.

Has Epic Grown Too Big, Too Fast?

Posted on November 8, 2013 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit.

We’ve written a lot of posts over the years about some of the challenges that Epic has faced as it’s grown its EHR business. In fact, Anne Zieger’s post yesterday about a Hospital Credit Rating Lowered due to their Epic Project is one example. However, I was really struck by this reader submitted article on HIStalk.

The article is written by a “Long-Time Epic Customer”. You don’t get the sense that this customer is bitter or has any real dog in the fight. In fact, if anything this customer seems to have a love for Epic and they want Epic to win the EHR battle. However, they’re concerned by the changes that they’ve seen in Epic as its grown. His a paragraph from the article:

We installed Epic years ago, but have seen a vast difference between our prior experience and a recent rollout of newer products. The method where time was taken to help us build our own system has been replaced by a rushed, prefab Model system installed by staff where even the advisers and escalation points at Epic have little knowledge of their applications. Epic has always had newer people, but it was much more common to have advisers during the install who did have experience to watch for pitfalls.

The writer then goes on to describe how Epic seems to be investing in the wrong things. “We’re getting answers, solutions, fixes, and reports slower than ever.”

I think the reason many of things really struck a chord with me is that they’re matching up with many of the things I’ve seen and heard. Based on some real anecdotal things I’ve heard I won’t be surprised if Judy decides to get out of the day to day work at Epic sometime soon. We’ll see how it plays out, but an Epic without Judy at the helm will be quite different.

EMR Upgrade Cycles are Painful – Are You Prepared for Them?

Posted on October 7, 2013 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit.

Everyone gets so excited and worked up about the initial EMR implementation, but so many discount the effort that’s required for every EMR update cycle as well. Dr. Jayne from HIStalk gave a great first person perspective on EMR update cycles:

I figure I’ve got about two weeks of the good life left and then I’m going to be back in an upgrade cycle with all the standing meetings that entails. I’ll be back in the trenches testing workflows and trying to find defects as quickly as possible so that our vendor can roll them into patches before we go live. Every time we upgrade it reminds me more and more of some kind of military assault. I’m not sure if it’s just the way we run them or a little bit of post-traumatic stress. Maybe it’s a little of both.

I’m also reminded of Heather Haugen’s comments about EHR upgrade cycles: “software upgrades erode adoption over time and so with every upgrade you need a commensurate effort to retrain adoption.” Far too often organizations underestimate the impact and challenge associated with EMR upgrades.

Over the next couple years, those upgrades will likely be tied to an organization’s meaningful use plan. So, those will likely go better than some nebulous EMR upgrade plan. However, those organizations who underestimate the impact of EMR upgrades on their organization will pay the price later.

I know that many believe that in the large hospital space it’s a two horse race between Cerner and Epic. However, when you consider the challenges and costs associated with upgrading those software, don’t be surprised if some smaller scrappy startup can exploit the EMR upgrade opportunity. I don’t think it will happen until after meaningful use and EHR incentive money run their course, but it will happen.

Lessons Learned from Sutter’s EHR Implementation Challenges

Posted on September 25, 2013 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit.

One of our more popular recent posts was published on EMR and HIPAA and was titled, “Adding Insult To Injury, Sutter’s Epic EMR Crashes For A Day.” When the post was shared on LinkedIn, it prompted a really insightful discussion on EMR training and Sutter’s approach to EHR implementation. A few of the comments were so good that I wanted to share them for more people to read and learn.

The first comment is from Scott Kennedy, an Epic Stork Trainer:

I was an Epic training consultant on the E. Bay Sutter EHR implementation and I can tell you first hand that Sutter Admin, and the Nurses are at odds. This unfortunate relationship made it difficult to train the staff. Epic itself is not to blame. Those who are using the Epic EHR are not as trained as they should be.

Sutter used an “in house” training team rather than bringing on a full consulting team with much more experience in training and educating end users. The “in house’ trainers included some nurses, RTs, and the like as well as a host of newly graduated college students who had less to no experience with conducting a formal training presentation on a multidisciplinary EHR.

Hiring and training “in house” is a great addition to bringing on an experienced, skilled, professional team of Epic credentialed trainers, like myself who do this as a profession all over the country.

We were also directed by Sutter EHR implementation Administration to “facilitate” rather than “train.” “Facilitate included passing out exercise booklets to the clinical end users and having them work on their own, rather than conducing concise, lectured, guided practice prior to each exercise. Hands on exercises are an essential part of the training, but should not be the complete focus of training.

The learner is left on their own to figure out the system, which is counter productive. That approach only builds anxiety, confusion and eventual resentment for the system and the administration who have chosen the EHR they are fumbling through.

I empathize with the clinical end users. There training experience could have been much more instrumental in getting them off on the right foot with their new EHR, had the training approach been more adult learning theory based rather than self-learning based.

I only wish I could come back to Sutter and retrain the nurses and other clinicians from the proven, consistent, progressive, successful adult learning approach, which enables and empowers the end user to grasp, comprehend and assimilate the EHR system into their daily shift work flow. That is not to say that there are not implementation bumps and optimization needs that have to be addressed, but they are far less impactful when the clinician is properly trained.

I am so sorry Sutter nurses and staff that I trained, but I was firmly told to “facilitate” your learning rather than “train” you. I tried to implement adult learning methodology, but was told by your EHR administration to “stop talking and let them do it on their own.”

Epic EHR is not to blame here. Epic is a sound, EHR system that is serving the needs of millions of patients and their care providers around the world, without incidents such as those being experienced at Sutter.

There is a right way to implement and train and a wrong way. Sorry Sutter EHR implementation administration, but “I told you so!”

I asked Scott Kennedy if he’d thought of leaving the project since it was being done the wrong way and he offered the following response:

@ John, yes I did come very close to leaving the project. As a matter of fact after I was verbally “scolded” for lecturing to much I phoned my recruiter and asked to be placed on another project, but then, after careful thought, I decided to stay on the project and attempt to train and support as much as I could. But it seems that my individual efforts were not enough to counter the original training “facilitation” focus.

To add insult to injury those of us trainers who were there for the Sutter E. Bay implementation were told not to return for the W. Bay implementation. The EHR administration wanted an entirely new outside consulting team.

I got a fellow colleague on the project, hoping that the E. Bay administration would have learned from and the current W. Bay implementation would be better. The training colleague I got on the W. Bay project shared with me that it was worse than the E. Bay implementation. They kept the experienced Epic trainers as support and utilized them as little as possible for actual front end training. So sad, really.

The EHR administration at Sutter tried to cut every financial corner possible and lost sight of the long run implications of improper front end training. Now they are paying the price.

Michael A. P., an EMR consultant offered this insight as well:

I’ve also had the misfortune of working with Sutter for a (thankfully) brief period. In their long history of attempting to implement Epic, they could be counted on to make the wrong decision in almost every situation. Their internal politics trump the advice they receive from vendors and highly experienced consultants. The result is an implementation that serves neither the patient or the users best interests.

Then, Ryan Thousand, an IT Architect at Athens Regional Medical Center, offered a broader view of what’s happening in health IT and EHR:

I hate to say it but most large healthcare organizations are getting like this as well…. There are WAY too many layers in these organizations and sometimes to get work done can mean 4 weeks of executive meetings and in the end no decision or 100% opposite of the recommended direction given. That being said, with the rapid change in healthcare and the mergers and acquisitions occurring right now, I fear the worries for Healthcare in general over the next couple of years. We cannot continue to try to meet mandates the government is making while still ensuring 100% utmost patient care; and in the end that is really all I care about.. the patient in the bed who is BENEFITING from my implementation. Change is always tough but done the right way with the right people (as you all stated above was not done correctly) we will continue to see great things happen on the HIT side. But unless Epic/Cerner all the big players in the markets as well as the local clinician and providers work together and decide the best outcomes for our patients, we will all one day suffer, as we will all one day be patients.

In all the years I’ve been writing about EMR and EHR, the biggest problem with most EMR implementations is lack of EHR training or poor EHR training. It’s really amazing the impact quality EHR training can have on an implementation. However, many organizations use that as a way to save money. If they could only see the long term costs of that choice.

Judy Faulkner Interoperability Chart

Posted on September 18, 2013 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit.

Farzad Mostashari shared the following tweet which includes a picture of the growth in standards-based exchange per Judy Faulkner.

Here’s a blown up version of the chart (click on the image for an even larger version):
Epic Data Sharing Chart

As Farzad notes in the tweet, the patient records exchanged per month is now up to 1.25 million. It’s also worth noting that the red bar in the chart is exchange of records from Epic to Epic. The Green bar in the charts is from Epic to Non-Epic. I hope that green bar continues to grow since as the chart displays, that’s a definite shift in strategy for Epic. Let’s hope this shift continues until the data in healthcare is available where it’s needed when it’s needed.

Epic Rollout Contributes To $55M Loss At NC Hospital

Posted on September 10, 2013 I Written By

Anne Zieger is veteran healthcare editor and analyst with 25 years of industry experience. Zieger formerly served as editor-in-chief of FierceHealthcare.com and her commentaries have appeared in dozens of international business publications, including Forbes, Business Week and Information Week. She has also contributed content to hundreds of healthcare and health IT organizations, including several Fortune 500 companies. She can be reached at @ziegerhealth or www.ziegerhealthcare.com.

It’s no secret that rolling out an Epic EMR is a big-ticket investment. What’s also becoming apparent is that some of the hospitals that take the plunge can’t really afford to pay for what they’ve bought, much less staff and develop an Epic presence.

The latest Epic EMR financial casualty to cross my desk is Wake Forest Baptist Medical Center which, according to the Winston-Salem Journal, saw a $55.1 million operational loss partly due its Epic rollout during fiscal 2012-13.

In a regulatory filing directed to bond investors, Wake Forest Baptist said that the Epic implementation had a substantial negative impact on fiscal 2013 due to both direct implementation costs and associated indirect expenses, according to the Winston-Salem Journal.

While the hospital’s stock investment gains of about $54 million helped offset most of the operational loss, leaving the overall loss at a much smaller $571,000, this fiscal year’s performance is still much worse than the previous year, when Wake Forest had $45.8 million in operational revenue and overall excess revenue of $88.7 million, the newspaper reports.

But the direct expenses and development costs weren’t the real capper, the newspaper said. The biggest Epic-related blow to Wake Forest Baptist came from $53.7 million in indirect impact, including $36.9 million of lost margin due to volume disruptions during the initial go-live and post go-live optimization. On top of that, the hospital reported $16.8 million in other Epic-related implementation expenses.

And that led to a shakeup in the C-suite. Giving the lie to the notion that nobody ever got in trouble for buying Epic, earlier this year, the hospital’s chief information officer of Wake Forest Baptist resigned in the middle of the troubled Epic launch.

In the article, the newspaper reports that Wake Forest Baptist “remains confident in Epic’s long-term benefit to the center”, and that hospital CEO Dr. John McConnell believes that the install “was absolutely necessary for patient safety,” he told the Winston-Salem Journal .

While it may turn out to be true that Wake Forest Baptist will be able to improve patient safety using its Epic EMR, in the mean time it’s having cut back on staff to pay for that gain. According to the newspaper, the center had planned to eliminate at least 950 jobs during the recent fiscal year;  some were not eliminated but may be during this fiscal year.

Hospital EMR and EHR Stats

Posted on July 3, 2013 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit.

Today I wanted to take a minute to spotlight the advertisers that support the work we do here at Hospital EMR and EHR. This site has grown much faster than I could have imagined. Considering the shift from ambulatory to hospital environments, this probably should be a surpise. Regardless, thanks so much for reading, sharing and commenting.

Since Hospital EMR and EHR started, we’ve had 264,953 pageviews to the site. Not too bad for this being the 399th post and we’ve had 689 comments. As an interesting side note we’ve had 48,091 spam comments. Thank goodness for spam filters. Here are the top 5 blog posts based on number of views:
Why Is It So Hard to Become a Certified Epic consultant?
Could Epic End Up The Victim Of Its Own EMR Success?
Soarian: Does Siemens Finally Have an Epic-Killer?
Why Do People Dislike Epic So Much? Let Me Count The Ways
Did Epic Kiss Off A California Customer (And Try to Get Its CIO Fired)?

All of the posts are from the middle of 2011. So, maybe the top posts idea isn’t fair to those posts that were recently posted. Plus, from this list we can garner that our readers are very interested in Epic. In fact, the top post about becoming a Certified Epic consultant has had 3 times as much traffic as the other posts. Whether you like how Epic handles their certification, a lot of people seem interested in obtaining the Epic certification.

I also want to take a moment to recognize the advertisers who support all the work we do at Hospital EMR and EHR. The content here wouldn’t exist if it wasn’t for their support. If you enjoy what we do, check out their products and see what they have to offer your hospital.

Canon – This company really needs no introduction. They have some great scanner products. I have one on my desk and I love it. Heavy duty scanners are a must in the hospital EHR environment. Paper is still coming into your office, and with an EHR you usually want that paper stored electronically instead of in the now extinct paper chart. Just make sure you get a quality scanner so you don’t burn through a cheap one like I did when I first implemented an EHR many years ago.

Caristix – Need an HL7 interface? Check out Caristix to get it done faster. It’s always great for a hospital to have someone to look to when they need an HL7 interface done quickly. HL7 is going to be the dominate interface standard for the forseeable future. If you don’t have a good strategy for managing all the HL7 interfaces you have and the ones you’ll have in the future, then talk to Caristix.

GE Centricity Business – With Healthcare Reform circling over head and PPACA (Patient Protection an Affordable Care Act) upon us, we’re getting ready for a sea of changes when it comes to managing your revenue. The future of healthcare revenue is going to require a revenue management software like the one that GE business offers. Plus, the beauty of revenue cycle management software is that the purchase can be directly tied to profitability of your organization.

Thanks to those advertisers. If you’re interested in supporting the work we do, check out more details on our Hospital EMR and EHR advertising page. We’ve also recently started some email blasts, content marketing, and whitepaper lead generation.

What If EMR Interoperability Was Mandatory?

Posted on June 5, 2013 I Written By

Anne Zieger is veteran healthcare editor and analyst with 25 years of industry experience. Zieger formerly served as editor-in-chief of FierceHealthcare.com and her commentaries have appeared in dozens of international business publications, including Forbes, Business Week and Information Week. She has also contributed content to hundreds of healthcare and health IT organizations, including several Fortune 500 companies. She can be reached at @ziegerhealth or www.ziegerhealthcare.com.

For decades, industries have haggled and coded and bargained their way into shared data standards.  Each agreement has made great technical advances possible and grown markets into forms which could hardly have been imagined before.

Traditionally, the idea has been agreeing on interoperable standards is a form of enlightened self-interest.  The equasion “interoperability=larger markets=more pie for everyone” has nearly always managed to take root even in industries as brutally competitive as networking.  Consider where we’d be without 802.11 for WiFi, for example. If WiFi manufacturers had staged a prolonged battle over standards, and the reach of WiFi didn’t blossom everywhere, the Internet as we know it might not exist.

Well, here in EMR vendor land, we’ve somehow passed the exit marked “coopetition” and wandered off into interoperability nowhere land.  Sure, tell me about the CommonWell Alliance, which looks, on the surface, something like industry cooperation, and I’ll retort, “too little, too late.”  And do I even have to say that the idea that Epic supports everybody is something of a laughing matter?

Maybe, after seeing how miserably the EMR vendor industry has failed to come together to share data, it’s time to force the matter.  I read that ONC  honcho Farzad Mostashari has occasionally threatened to do just that, but hasn’t followed through with any proposed regs on the subject.

What if the FCC, the FDA and the ONC (which are now taking comments on a regulatory framework for health IT) decide to look at standards, pick a winner and shove it down the ever-living throat of every uncooperative vendor hoping to create dependency on their way of doing things?  That would include Epic, of course, which today, hears countless hospital CIOs say they had to buy their product because everybody else did.

Don’t get me wrong, this is a very, very serious matter; any regs that attempted to force interoperability would impose untold billions in costs on vendors, not to mention their customers. But if interoperability is the real prize we’re ultimately hoping to gain — the big EMR enchilada — is it possible that it’s time to take the risk anyway?  I don’t know, but I certainly wonder.  How about you, readers?

Judy Calls Epic “Most Open System I Know”

Posted on May 16, 2013 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit.

After Zina Moukheiber from Forbes was declined an interview with Judy Faulkner, CEO of Epic, last year Judy decided to talk to Zina about Epic in this article “An Interview With The Most Powerful Woman In Health Care.” Zina does a nice job on the interview and raises some of the questions many people have about Epic. It’s worth a read if you like to follow the hospital EHR world.

Many people are likely going to latch on to Zina calling Judy Faulkner the “most powerful woman in health care.” I don’t think that’s really up for discussion. Judy is the most powerful woman in healthcare and so I’m really glad that Judy is starting to join the discussion about Epic and healthcare. She has an important voice in the discussion and we need her participation. Although, I’m sure she’ll hate being called a billionaire in the article. The reality is we don’t know how much Judy’s really worth until we know how much Epic is worth and I’m not sure Epic plans to go public anytime soon.

Semantics aside, the most important part of the interview was the discussion of Epic being a closed system to which Judy frankly replied, “We are the most open system I know because we’re built as a database management system, and database management systems need to allow their users to mold it to what they need.” I think she really believes that Epic is an open system and quite frankly there aren’t that many in healthcare she can look to that are more open. Sure, a number of EHR vendors have worked to be more open, but even they aren’t as open as many other non health IT software systems. Maybe Judy hasn’t looked at the APIs outside of healthcare.

The real disconnect I had when reading Judy’s thoughts on being open is her lack of understanding of how a truly open API works. In a well implemented API, you can allow any and all programmers to be able to build applications on top of your software without those programmers needing to read your code and study your internal software. I’m not saying you don’t want and need to have an application and verification process for those people who want to tap into your API. This can be part of the process, but a well implemented and documented API can be open to everyone interested in building on top of your software. The value Epic would receive from so many companies iterating and extending the core Epic functionality would be amazing.

The other facet of Epic openness discussed in the article was around interoperability. Judy offered these comments on Epic’s ability to share patient records:

As of March 2013, our customers exchanged 760,000 patient records per month; about one-third were with non-Epic systems. Based on the historical trajectory, we expect that we’re closer to exchanging approximately one million records per month. We are currently exchanging data with Allscripts, Cerner, Department of Defense, Veteran Affairs Administration, Social Security Administration, eHealth Exchange (formerly Nationwide Health Information Network), Greenway, MEDITECH, NextGen and others. We expect to be exchanging data soon with eClinicalWorks, General Electric, Surescripts, and others.

This sounds good on face, but lets consider how many records Epic is sharing. Let’s use the round number of 1 million patient records shared per month. The article says that Epic has about half of the US population on Epic, or about 150 million patients. That means that about 0.67% of Epic’s patient records are being shared.

I’m happy to applaud Epic for sharing 1 million records a month with so many different vendors. My only complaint is that they could do so much more. For example, if you can share records between Epic and Cerner now, does that work for all Epic hospitals or do you have to do the new integration with every hospital that says they want to share records with Cerner? If it was a turn key way to integrate with Cerner, I’m quite sure that instead of 1% of Epic’s patient records being shared we’d see tens of millions of patient records flowing where they needed to go.

Many might remember my surprise breakfast with Judy Faulkner at the CHIME Forum. From my personal experience, Judy is not the black widow that I’ve heard many portray her to be. In fact, I found her incredibly thoughtful, caring, and really interested in quality patient care. That’s why I hope Judy will see that she’s sitting on an opportunity to do so much more than she’s doing now. Although, it will take a shift in her understanding of what it means to be an open EHR. Right now it seems her mostly unfounded fears won’t let her see the possibilities.