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!

Why Might Intermountain Have Chosen Cerner Over Epic?

An anonymous person on HIStalk gave some really interesting insights into Intermountain’s decision to go with Cerner instead of Epic.

Re: Intermountain. The short-term choice (three or so years) would have been Epic, but we went with Cerner because of Epic’s dated technology, Cerner’s openness, and the feeling that we would be more of a partner than a customer with Cerner. The partnership is more than words. We’re working closely with Cerner and their horde of sharp, dedicated people on the implementation. We have some pieces they don’t and those are being built into the Cerner system, while some of our own development efforts have been redirected since Cerner already has that functionality. The first rollout is scheduled for December and I think it will go well due to the way the teams are working together. Unverified.

This is the best analysis of Intermountain’s decision to go with Cerner that I’ve seen. As in every billion dollar procurement decision, it’s always got other nuances and pieces that go into the decision making process. However, the above analysis gives us a good place to start.

Let’s look at the main points that are made:

1. Is Epic technology more dated than Cerner?

2. Is Cerner more open than Epic?

3. Will Cerner be more of a partner than Epic would have been?

I’d love to see Judy’s (Epic CEO’s) comments on all of these. I’m sure she’d have a lot to say about each of them. For example, you may remember that Judy described Epic as the most open system she knows. Ask someone who wants to get Epic certified if they’re open. Ask a health IT vendor that wants to work together if Epic is open. Ask even some of their smaller customers who want to do things with Epic if Epic is open. They’d all likely disagree that Epic is the most open system.

I’d love to hear people’s thoughts on each of these three points. I think it will make for a really lively discussion that will help us get closer to understanding the reality of these assertions.

However, reality aside, I can tell you that the public image of Epic vs Cerner certainly confirms all three of these points. Whether Intermountain indeed used these points as part of their decision process or not, I don’t know. What I do know is that it wouldn’t surprise me at all if they did think this way since there are many in the market that believe and share all of the above three impressions.

July 14, 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 14 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John launched two new companies: InfluentialNetworks.com and Physia.com, and is an advisor to docBeat. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and Google Plus.

Epic’s 13 Principles

I recently came across this blog called “Life After Epic” which has the subtitle, “For the soon-to-be-Ex Epic Employee.” Although, if you look at the blog address it’s FiredFromEpic.blogspot.com. I assume Fired from Epic was the original blog name, but was likely changed for obvious reasons.

I’m sure I’ll reference more articles from this blog in the future, but I was really intrigued by the 13 Epic Principles that the blog’s been covering recently. Epic’s 13 Principles definitely provide some interesting insight into the EHR vendor Epic.

1. Do not go public.
2. Do not be acquired.
3. Expectations = reality.
4. Keep commitments.
5. Be frugal.
6. Have standards. Don’t do deals.
7. Create innovative and helpful products.
8. Have fun with customers.
9. Follow processes. Find root causes. Fix processes.
10. Don’t take on debt for operations, no matter how good the deal.
11. Focus on competency. Do not tolerate mediocrity.
12. Teach philosophy and culture.
13. If you disagree, dissent. Once decided, support.

What do you think of these principles? If you’ve dealt with Epic, you’ve no doubt seen a lot of them in action.

June 17, 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 14 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John launched two new companies: InfluentialNetworks.com and Physia.com, and is an advisor to docBeat. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and Google Plus.

The Best Thing For Epic Might Be to NOT Win the DoD Contract

For those not familiar with the Department of Defence (DoD) EHR contract that’s being bid on right now, check out our post about the $11 billion EHR contract. Yes, you’re reading that right. That’s $11 billion with a B. I believe that would be the largest single EHR contract ever (I believe Kaiser was $4 billion to start).

Needless to say, this is an enormous contract that will make some outside companies very rich. I can’t even imagine what $11 billion of EHR consultants and software would look like. That’s a lot of EHR jobs to go around, but I digress.

Most people in the industry seem to believe that Epic is the front runner in the race. Considering the number of large deals that Epic has won, Epic winning the DoD EHR contract would be a safe bet. Although, I wonder if the best thing for Epic would be for them to not win the DoD contract.

Sure, Epic would take a short term PR hit if someone else like Cerner wins the DoD contract. You can already predict the press headlines talking about the fall from power as Epic loses to Cerner (similar to when Cerner won the Intermountain deal over Epic). That would have some damage to Epic’s reputation, but not really. It’s not like any other hospital in the US thinks that their contract would be anything like the DoD EHR contract. In fact, many of the hospitals purchasing Epic EHR will be grateful that Epic resources aren’t being tied up on a new $11 billion contract while their “small” $100 million EHR project languishes.

Indeed, the best thing for Epic might be for it to NOT win the DoD EHR contract. Let’s remember that Epic has a really good history of successful EHR implementations. Sure, there are a few examples where the Epic implementation hasn’t gone so well. However, I think the general view of the industry is that Epic implementations generally go well. In fact, there are stories of Epic contracts so stringent that when an Epic implementation starts to go bad, Epic comes in and takes over to make sure that the implementation goes well.

Long story short, Epic has the best reputation of any hospital EHR vendor when it comes to successful EHR implementations (especially large ones). Epic winning the DoD EHR contract could do a lot to tarnish that reputation.

One might argue that if Epic’s successful with the $11 billion DoD EHR contract, that it will be a boon to their current reputation. That’s fair, but the DoD EHR implementation would be unlike most other EHR implementations. First, the DoD doesn’t have a sterling reputation for successful healthcare software projects. That will likely become an issue for anyone who wins the contract. Second, we’re talking about a government entity with layers of red tape and bureaucracy. A small company like Epic (small in government contractor terms) isn’t going to carry the same weight as they usually do in their other hospital EHR implementations. Epic, the control company, won’t be able to control the DoD EHR project the same way they usually do.

One could use the same argument I used above about why even if Epic gets the DoD contract and fails, it won’t tarnish their reputation since hospitals realize that the DoD is unique. However, the difference between losing a bid and a failed $11 billion project is very different. The failed DoD EHR bid will be covered once and then generally forgotten. A failed $11 billion contract can carry on for years as timelines are delayed, budget overruns are reported, discontent leaks out, he said-she said occurs, and the media churns and speculates on what’s happening with the DoD EHR project.

We all think that winning an $11 billion contract would be great. Indeed, that’s a lot of money and would be an enormous win worth celebrating. The only question is how long will the celebration continue? If I’m Epic, I wouldn’t be too sad if I didn’t win the contract. In the long term, it might be for the best.

June 2, 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 14 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John launched two new companies: InfluentialNetworks.com and Physia.com, and is an advisor to docBeat. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and Google Plus.

Epic Insider Article

If you read this blog, then you’re probably as interested in the secretive Epic as me. So, you’ll love this article in the Madison paper from a former Epic employee talking about what it was like for him to work at Epic.

I’m sure I’ll do some more posts about a number of topics in this article in the future, but I was most intrigued by the strong culture that they’ve created at Epic. I always knew that it was the case, but it was really interesting to see it described first hand.

The donut day story in the article was a great example. You have to read the whole story in the article to know what I mean (go ahead and read it and I’ll be here when you get back).

While I’m someone who agrees that the company should be looking at the root causes for “Why” you do something, the story also makes me wonder if they get blinded by one vision and can’t see that there could by multiple Why’s for a certain task. I think this could apply to Epic and interoperability. They’ve taken a hard line because of a certain why that they have, but it seems to ignore the other 10 reasons why they should be more open. I think that this type of thinking will eventually catch up to them.

The other part of the article which struck me was all of the different ways that they approached hiring, managing, promotion, etc. No doubt hiring and firing the right people is the hardest thing to do in any business. Although, this insight from the article made me wonder if Epic is missing out on an opportunity to be even more than they are today:

Epic is teeming with talent but every year the company loses many employees it would have preferred to keep. There’s no silver-bullet solution to the turnover problem, but one place to start might be hiring more people who have worked in health care and can leverage their experience to connect with end users. One person from my project team who worked as a nurse before Epic hired him demonstrated exceptional rapport with a roomful of practitioners because he’d actually performed the relevant work in a clinical setting.

Diversity can be really beneficial to a company and I wonder if Epic couldn’t benefit from some diversity.

May 30, 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 14 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John launched two new companies: InfluentialNetworks.com and Physia.com, and is an advisor to docBeat. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and Google Plus.

Moving Hospital EHR to the Cloud

I’ve long been interested to see how hospitals were going to handle the shift to “the cloud.” Obviously, most hospitals have made a big infrastructure investment in huge data centers and so I’ve always known that the shift to the cloud would be slow. However, it also seemed like it was inevitable.

I was interested to hear Jason Mendenhall talk in our Healthcare Data Center Google Plus hangout about healthcare entities moving their technology infratructure into their data center. Plus, I pair that with the smaller rural hospital CIO I met who balked at the idea of having a data center or really even having any sys admin people on staff.

Plus, I’m reminded of this quote I heard Dr. Andy Litt tell me about when hospitals will start using Dell to host their Epic EHR:

The opportunity to host an Epic or other EHR is in first install, not for existing ones that have invested in a data center already. -Andy Litt, MD, Dell

I can’t imagine that many institutions really want to move their Epic EHR hosted locally into the cloud. That just doesn’t happen. At least it doesn’t right now. Will we see this change?

I think the answer to that is that we will see it change. There’s a really good argument to make that hospitals shouldn’t be building data centers and that there’s tremendous value to using an outside provider. Plus, many of these “data center” companies are becoming more than just a set of rails, power, and cooling. They are now working with a variety of cloud providers that can provide you more than just a place to put your own servers.

I’ll be interested to see how this plays out, but I think we’ll see fewer and fewer hospital data centers. The outside options and connectivity to those outside data centers is so good that there’s going to be no need to do it on your own.

March 24, 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 14 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John launched two new companies: InfluentialNetworks.com and Physia.com, and is an advisor to docBeat. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and Google Plus.

Epic to Epic Conversion

Gabriel Perna has a great article on Healthcare Informatics discussing an EHR conversion that I hadn’t considered. What happens when a hospital system acquires another hospital system and they both use the Epic EHR? Here’s the challenge as described in the article:

“As we got into it, we realized Epic had done [a conversion from] IC Chart [InteGreat from Med3000] before, they had done Cerner-to-Epic conversions, they had done McKesson-to-Epic conversions. They had done those before, and they do them well. They hadn’t done Epic-to-Epic before. That was the area where they were least experienced in. It was a lot more work to do,” says [Bob] DeGrand, who assumed the position of CIO [of Froedtert Health] in January of 2009, a few months after the West Bend affiliation became official.

As we continue on our path of hospital system consolidation, this is going to become more and more of an issue. As those familiar with Epic know, every Epic installation is unique. I was recently told by someone that even within the all Epic Kaiser there are multiple Epic installations and they have a challenge communicating with each other. Now think about what that means if you’re trying to merged two different Epic installations.

The article also points out that one of the biggest challenges in a merge like this is overlapping patients and ensuring that you merge them properly. Patient identity is a big challenge in any hospital system, but even more important when you’re looking to merge two large hospital systems that have relatively close proximity with similar patient populations.

I’d be interested to hear from other people who might have gone through an Epic to Epic conversion. What challenges did you face? Would you have rather had a Cerner to Epic conversion?

December 30, 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 14 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John launched two new companies: InfluentialNetworks.com and Physia.com, and is an advisor to docBeat. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and Google Plus.

What Can Go Wrong With An Epic Implementation

With Epic owning the lion’s share of new EMR implementations — it has as many in progress or planned as all other major vendors combined — it’s good to stop and look at just what can go wrong with an Epic implementation.

After all, while Epic installations are a fact of life, all of the news they generate isn’t good. In fact, a growing number of stories of botched Epic installs and institutional fallout are beginning to mount.

In an effort to do learn more about Epic’s strengths and weaknesses, researchers at The Advisory Board Company interviewed some of Epic’s most experienced U.S. hospital customers, as well as some of the busiest Epic implementation consultants, writes senior research director Doug Thompson.

As Thompson points out, the problems Advisory Board identified could impact any big EMR install, but with Epic in the lead, it doesn’t hurt to focus on its products specifically.  (By the way, according to the Advisory Board, there were 194 Epic installs in process or contracted for 2012 and 2013; the closest competitor, MEDITECH, had 59 and Cerner came in at 55.)

So what’s behind the stumbling? Thompson names several limitations to Epic’s own approach to implementation, including the following:

* Its young implementation staffers may be enthusiastic, but some lack operational experience in hospitals or medical practices, which means they rely heavily on Epic’s standard methods and tools –and that may not be adequate for some situations.

* Though Epic’s recommended implementation staffing numbers are higher than that of most other EMR vendors, their estimate nonetheless falls short often by 20 percent to 30 percent of the need.

*Epic’s “foundation” (model) installation plan limits customization or extensive configuration until after the EMR has gone live, which can lead to less physician buy-in and end-user cooperation.

To address these concerns, Thompson offers fourteen techniques to help hospitals get the value they want.  Some of my favorites include:

Begin with the end in mind: Make sure your facility has specific, measurable benefits they hope to achieve with your Epic implementation, and prepare to measure and manage progress in that direction.

Governance: Make sure you assign appropriate roles and responsibilities in managing your Epic rollout and ongoing use. While IT will serve as the linchpin of the project, of course, it’s critical to make sure the appropriate operations leaders have a clear sense of how Epic can and should affect their areas of responsibility.

Get outside input on project staffing: While Epic is upfront about the need for extensive staffing in its implementation, as noted its estimates still come in rather low. It’s a good idea to get in objective outside estimate as to how big the project staff really needs to be.

For more information, I highly recommend you read the full Advisory Board brief. But in short, as  the report concludes, it seems that relying too much on Epic’s approach, staff and tools can lead to problems. Surprised?

December 9, 2013 I Written By

Anne Zieger is veteran healthcare consultant and analyst with 20 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.

Has Epic Grown Too Big, Too Fast?

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.

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 14 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John launched two new companies: InfluentialNetworks.com and Physia.com, and is an advisor to docBeat. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and Google Plus.

Lessons Learned from Sutter’s EHR Implementation Challenges

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.

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 14 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John launched two new companies: InfluentialNetworks.com and Physia.com, and is an advisor to docBeat. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and Google Plus.

Stanford Uses Epic Feature To Conduct Web Visits

Stanford Hospital & Clinics has rolled out a new primary care service, powered by a feature available within its Epic EMR, offering medical visits via web video.

The new service allows patients to schedule video visits via the hospital website, using a scheduling application available on the site, InformationWeek reports. At the scheduled time, patient and doctor meet together in a web-based video conference.

The service, which Stanford dubs “eCare,” takes advantage of Epic’s software for video consultations. The video consult is integrated into the patient’s Epic medical record automatically. eCare also integrates third–party identity verification services in an effort to make sure the patient is who they say they are.

According to Stanford CIO Pravene Nath, M.D., who spoke with InformationWeek, video visits are medically appropriate for a range of noncritical visits and follow-ups. For example, one of the service’s first patients had an eye condition; the doctor was able to help simply by looking into the camera at the patient’s eyes. Another example of condition appropriate for web conferencing is treatment of a skin rash, Nath said.

“These are cases where a quick visual is all that is needed, followed by a quick interaction of the patient talking with the doctor,” Nath told InformationWeek.

Stanford is offering eCare first to employees of self insured firms who contract with the hospital. That way, neither the employer nor Stanford has to worry about whether a managed-care company will reimburse the doctors for the video visits. But Stanford’s intent is to make video consults available to everyone, InformationWeek says.

Stanford’s care program is just one of several virtual healthcare services the hospital’s developing, IW reports. The organization is also looking into secure messaging between doctors and patients and a service which involves submitting a still photo of them conducting a live videoconference, the magazine says.

If Stanford can make the integrated EMR and web visits work, it may be breaking new ground. A few months ago, I wrote a piece noting that many telemedicine providers are very reluctant to integrate with EMRs, given that the need for interoperability with so many systems could choke their development efforts.

While enabling telemedicine isn’t going to offer Epic any huge advantage it doesn’t have already, it does offer some intriguing possibilities. If thought leaders like Stanford make a success of web visits, using Epic technology, it might force other competitors into the telemedicine arena as well. It will be interesting to see how influential Stanford’s experiment turns out to be.

September 20, 2013 I Written By

Anne Zieger is veteran healthcare consultant and analyst with 20 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.