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!

Hospital Takes Step Forward Using Patient-Reported Outcome Data

Posted on December 6, 2017 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.

I don’t usually summarize stories from other publications — I don’t want to bore you! — and I like to offer you a surprise or two. This time, though, I thought you might want to hear about an interesting piece appearing in Modern Healthcare. This item offers some insight into how understanding patient-generated determinants of health could improve outcomes.

The story tells the tale of the Hospital for Special Surgery, an orthopedics provider in New York City which provides elective procedures to treat joint pain and discomfort. According to the MH editor, HSS has begun collecting data on patient-reported outcomes after procedures to see not only how much pain may remain, but also how their quality of life is post-procedure.

This project began by doing a check in with the patient before the procedure, during which nurses went over important information and answered any questions the patient might have. (As readers may know, this is a fairly standard approach to pre-surgical patient communication, so this was something of a warm-up.)

However, things got more interesting a few months later. For its next step, the hospital also began surveying the patients on their state of mind and health prior to the procedure, asking 10 questions drawn from the Patient-Reported Outcomes Measurement Information System, or Promis.

The questions captured not only direct medical concerns such as pain intensity and sleep patterns, but also looked at the patient’s social support system, information few hospitals capture in a formal way at present.

All of the information gathered is being collected and entered into the patient’s electronic health record. After the procedure, the hospital has worked to see that the patients fill out the Promis survey, which it makes available using Epic’s MyChart portal.

Getting to this point wasn’t easy, as IT leaders struggled to integrate the results of the Promis survey into patient EHRs. However, once the work was done, the care team was able to view information across patients, which certainly has the potential to help them improve processes and outcomes over time.

Now, the biggest challenge for HSS is collecting data after the patients leave the hospital. Since kicking off the project in April, HSS has collected 24,000 patient responses to nursing questions, but only 15% of the responses came from patients who submitted them after their procedure. The hospital has seen some success in capturing post-surgical results when doctors push patients to fill out the survey after their care, but overall, the post-surgical response rate has remained low to date.

Regardless, once the hospital improves its methods for collecting post-surgical patient responses, it seems likely that the data will prove useful and important. I hope to see other hospitals take this approach.

When It Comes To Meaningful Use, Some Vendors May Have An Edge

Posted on December 1, 2017 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.

A new article appearing in the Journal of the American Medical Informatics Association has concluded that while EHRs certified under the meaningful use program should perform more or less equally, they don’t.

After conducting an analysis, researchers found that there were significant associations between specific vendors and level of hospital performance for all six meaningful use criteria they were using as a yardstick. Epic came out on top by this measure, demonstrating significantly higher performance on five of the six criteria.

However, it’s also worth noting that EHR vendor choice by hospitals accounted for anywhere between 7% and 34% of performance variation across the six meaningful use criteria. In other words, researchers found that at least in some cases, EHR performance was influenced as much by the fit between platform and hospital as the platform itself.

To conduct the study, researchers used recent national data on certified EHR vendors hospitals and implemented, along with hospital performance on six meaningful use criteria. They sought to find out:

  • Whether certain vendors were found more frequently among the highest performing hospitals, as measured by performance on Stage 2 meaningful use criteria;
  • Whether the relationship between vendor and hospital performance was consistent across the meaningful use criteria, or whether vendors specialized in certain areas; and
  • What proportion of variation in performance across hospitals could be explained by the vendor characteristics

To measure the performance of various vendors, the researchers chose six core stage two meaningful use criteria, including 60% of medication orders entered using CPOE;  providing 50% of patients with the ability to view/download/transmit their health information; for 50% of patients received from another setting or care provider, medication reconciliation is performed; for 50% of patient transitions to another setting or care provider, a summary of care record is provided; and for 10% of patient transitions to another setting or care provider, a summary of care record is electronically transmitted.

After completing their analysis, researchers found that three hospitals were in the top performance quartile for all meaningful use criteria, and all used Epic. Of the 17 hospitals in the top performance quartile for five criteria, 15 used Epic, one used MEDITECH and one another smaller vendor. Among the 68 hospitals in the top quartile for four criteria, 64.7% used Epic, 11.8% used Cerner and 8.8% used MEDITECH.

When it came to hospitals that were not in the top quartile for any of the criteria, there was no overwhelming connection between vendor and results. For the 355 hospitals in this category, 28.7% used MEDITECH, 25.1% used McKesson, 20.3% used Cerner, 14.4% used MEDHOST and 6.8% used Epic.

All of this being said, the researchers noted that news the hospital characteristics nor the vendor choice explained were then a small amount of the performance variation they saw. This won’t surprise anybody who’s seen firsthand how much other issues, notably human factors, can change the outcome of processes like these.

It’s also worth noting that there might be other causes for these differences. For example, if you can afford the notably expensive Epic systems, then your hospital and health system could likely afford to invest in meaningful use compliance as well. This added investment could explain hospitals meaningful use performance as much as EHR choice.

Amazon May Soon Announce Major Cloud Deal With Cerner

Posted on November 27, 2017 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.

As I’ve previously noted, Amazon is making increasingly aggressive moves into the healthcare space of late. While it hasn’t been terribly public with its plans—and why should it, honestly?— there been some talk of its going into the healthcare technology space. There’s also much talk about angles from which Amazon could attack healthcare sectors, including its well-publicized interest in the pharmacy business.

Though interesting, all of this has been vaguely defined it best. However, a new deal may be in the works which could have a very concrete effect. It could change not only the future of Amazon’s healthcare industry efforts but also, potentially, have an impact on the entire health IT world.

Think I’m exaggerating? Check this out. According to a story on the CNBC site, Amazon is about to announce a “huge” deal with Cerner under which the two will work together on building a major presence in enterprise health IT for Amazon Web Services. Put that way, this sounds a bit hyperbolic, but let me lay this out a bit further.

As things stand, the online retailer’s Amazon Web Services is already generating almost $20 billion a year, boasting clients across major industries such as technology, energy and financial services. Its only stumbling point to date is that it’s had trouble cracking the healthcare market.

Apparently, at the re:Invent conference in Las Vegas next week, AWS’s CEO will announce that Amazon is teaming up with Cerner to convince senior healthcare leaders to use AWS for key initiatives like population health management.

Sources who spoke to CNBC that the partnership will initially focus on Cerner’s HealtheIntent population health product, presumably as a door into convincing hospitals shift more of the cloud-based business to AWS.

Now why, you ask, is this deal bigger than the average bear?  is it one of those vaporware partnerships that fly a flag and promise a lot but don’t really go anywhere?

Yes, I admit that’s always possible, but in this case, I don’t think it’s going to turn out that way. The fit simply seems to work too well for this to be one of those much-ballyhooed deals that fade away quietly. (In fact, I could visualize a Cerner/Amazon merger in the future, as crazy as that might sound. It’s certainly less risky than the Whole Foods deal.)

For one thing, both Amazon and Cerner have significant benefits they can realize. For example, as the story notes, Amazon hasn’t gotten far in the healthcare market, and given its talent for doing the impossible, it must be really stuck at this point. Cerner, meanwhile, will never pull together the kind of cloud options AWS can offer, and I doubt Epic could either, which gives Cerner a boost in the always next-and-neck competition with its top rival.

If this agreement goes through, the ripples could be felt throughout the healthcare industry, if for no other reason than the impact it will have on the enterprise EHR market. This one should be fun to watch. I’m pulling out the popcorn.

Surescripts Deal Connects EMR Vendors And PBMs To Improve Price Transparency

Posted on November 22, 2017 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.

I’m no expert on the pharmacy business, but from where I sit as a consumer it’s always looked to me as though pharmaceutical pricing is something of a shell game. It makes predicting what your airline ticket will cost seem like child’s play.

Yes, in theory, the airlines engage in demand-oriented pricing, while pharma pricing is based on negotiated prices spread among multiple contracted parties, but in either case end-users such as myself have very little visibility into where these numbers are coming from.  And in my opinion, at least, that’s not good for anyone involved. You can say “blah blah blah skin in the game” all you want, but co-pays are a poor proxy for making informed decisions as a patient as to what benefits you’ll accrue and problems you face when buying a drug.

Apparently, Surescripts hopes to change the rules to some degree. It just announced that it has come together with two other interest groups within the pharmacy supply chain to offer patient-specific benefit and price information to providers at the point of care.

Its partners in the venture include a group of EMR companies, including Cerner, Epic, Practice Fusion and Aprima Medical Software, which it says represent 53% of the U.S. physician base. It’s also working with two pharmacy benefit managers (CVS Health and Express Scripts) which embrace almost two-thirds of US patients.

The new Surescripts effort actually has two parts, a Real-Time Prescription Benefit tool and an expanded version of its Prior Authorization solution.  Used together, and integrated with an EHR, these tools will clarify whether the patient’s health insurance will cover the drug suggested by the provider and offer therapeutic alternatives that might come at a lower price.

If you ask me, this is clever but fails to put pressure on the right parties. You don’t have to be a pharmaceutical industry expert to know that middlemen like PBMs and pharmacies use a number of less-than-visible stratagems jack up drug prices. Patients are forced to just cope with whatever deal these parties strike among themselves.

If you really want to build a network which helps consumers keep prices down, go for some real disclosure. Create a network which gathers and shares price information every time the drug changes hands, up to and including when the patient pays for that drug. This could have a massive effect on drug pricing overall.

Hey, look at what Amazon did just by making costs of shipping low and relatively transparent to end-users. They sucked a lot of the transaction costs out of the process of shipping products, then gave consumers tools allowing them to watch that benefit in action.

Give consumers even one-tenth of that visibility into their pharmacy supply chain, and prices would fall like a hot rock. Gee, I wonder why nobody’s ever tried that. Could it be that pharmaceutical manufacturers don’t want us to know the real costs of making and shipping their product?

Epic Mounts Clumsy Public Defense On False Claims Lawsuit

Posted on November 6, 2017 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.

A former employee of a health system using Epic filed a False Claims Act whistleblower suit claiming that the vendor’s platform overbills for anesthesia services by default. The suit claims that Epic’s billing software double-bills both Medicare and Medicaid for anesthesia, as well as commercial payers.

At this point, let me be clear that I’m not accusing anyone of anything, but in theory, this could be a very big deal. One could certainly imagine a scenario in which multiple Epic customers colluded to permit this level of overbilling, which could generate staggering levels of overpayment. If so, one could imagine hospitals and health systems paying out judgments that add up to billions of dollars. To date, though, nobody’s made such a suggestion. In fact, Epic has said essentially the opposite and pointed to the need to understand how medical billing works, but we’ll get to that.

In the suit, which was filed in 2015 but unsealed this month, Geraldine Petrowski contended that Epic’s software was billing for both the base units of anesthesia for procedures and the time the procedure took.

Petrowski, a former employee with the compliance team at Raleigh, N.C.-based WakeMed Health & Hospitals, alleges that setting the billing to these defaults has resulted in “hundreds of millions of dollars in fraudulent bills” submitted to Medicare, Medicaid and other payers. (WakeMed is an Epic customer.)

According to an article appearing in Modern Healthcare, Petrowski developed these concerns when she worked with Epic as the provider’s liaison for its software implementation between 2012 and 2014. In the complaint, she says that she raised these concerns with Epic, but got a dismissive response. Eventually, after Petrowski kept up the pressure for a while, Epic fixed the billing issue — but only for WakeMed.

Apparently, the U.S. Department of Justice reviewed Petrowski’s case and decided not to intervene, a fact which Epic has not-surprisingly mentioned every chance it gets. Perhaps more tellingly, the vendor has suggested that Petrowski filed the suit largely because she’s clueless. “The plaintiff’s assertions represent a fundamental misunderstanding of how claims software works,” Epic spokesperson Meghan Roh told the magazine.

Now, I don’t want to go off on a rant here, but if the best public defense Epic can mount in this case is to offer some mixture of “everybody’s doing it” and “you’re a big dummy,” you’ve got to wonder what it’s got to hide.

Not only that, trying to brush off the suit as the product of ignorance or inexperience makes no sense given what’s involved. While False Claims whistleblowers can collect a very large payoff, getting there can take many years of grueling work, and their odds of prevailing aren’t great even if they make it through the torturous litigation process.

No, I’m more inclined to think that Epic has tipped its hand already. I’d argue that fixing only the WakeMed billing system shows what the legal folks call mens rea – a guilty mind — or at least a willingness to ignore potential wrongdoing. Not only that, if the system was operating as expected, why would Epic have gotten involved in the first place? Its consulting services don’t come cheap, and I’m guessing that Petrowski didn’t have the authority to pay for them.

It doesn’t look good, people…it just doesn’t look good.

Sure, the hospitals and health systems using Epic’s billing solution are ultimately responsible for the results. Maybe Epic is completely blameless in the matter this case. Regardless, if Epic’s hands are clean, it could do a better job of acting like it.

Is Allscripts An Also-Ran In The Hospital EMR Business?

Posted on August 18, 2017 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 all began with a question, as many classic tales do. Someone writing for the HIStalk.com website  – I think it was ever-anonymous, eponymous  leader Mr. HISTalk – asked readers to answer the question “Who will benefit most from the proposed acquisition of McKesson EIS by Allscripts?”

The survey results were themselves worth a read:

* Approximately 29% voted for “McKesson customers”
* About 27% voted for “Allscripts customers”
* 8.4% voted for “McKesson shareholders”
* Roughly 23% voted for “Allscripts shareholders”
* About 13% voted for “Allscripts competitors”

Two things about these responses interested me. One is that almost a third of respondents seem to think McKesson will make the bigger score after being acquired by Allscripts. The other is that a not-inconsiderable 13% of the site’s well-informed readers think the deal will help Allscripts’ competitors. If these readers are right, perhaps Allscripts should rethink the deal.

I was even more engaged by the analysis that followed, which the writer took a close look at the dynamics of the hospital EMR market and commented on how Allscripts fit in. The results weren’t surprising, but again, if I were running Allscripts I’d take the following discussion seriously.

After working with data supplied by Blain Newton, EVP of HIMSS Analytics, the writer drew some firm conclusions. Here are some of the observations he shared:

  • While McKesson has twice as many hospitals as Allscripts, most of these hospitals have less than 150 beds, which means that the acquisition may offer less benefit, he suggests.
  • In addition to having only 3% of hospitals overall, Allscripts controls only 6% of the 250+ bed hospital market, which probably doesn’t position it for success. In contrast, he notes, Epic controls 20% of this market and Meditech 19%.
  • His sense is that while hospitals typically want a full suite of products when they work with Epic, Cerner or Meditech, Allscripts customers may be more prone to buying just a few key systems.
  • Ultimately, he argues, Cerner, Epic and Meditech have a commanding lead in this market, for reasons which include that the three are well ahead when it comes to the overall number of hospital served.
  • Given his premise, he believes that Epic is at the top of the pyramid, as it has almost double the number of hospitals with 500+ beds that Cerner does.

To cap off his analysis, Mr. HISTalk concludes that market forces make it unlikely that a dark horse will squeeze out one of the top hospital EMR vendors: “Everybody else is eating their dust and likely to lose business due to hospital consolidation and a shift toward the most successful vendors as much as all of us who – for our own reasons – wish that weren’t the case.”

It would take a separate analysis to predict whether the top three hospital EMR vendors are likely to win out over each other, but Epic seems to hold the most cards. Last year, I wrote a piece suggesting that Cerner was edging up on Epic, but I’m not sure whether or not my logic still holds. Epic may indeed be King of the (HIT) Universe for the foreseeable future.

Is It Time To Put FHIR-Based Development Front And Center?

Posted on August 9, 2017 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.

I like to look at questions other people in the #HIT world wonder about, and see whether I have a different way of looking at the subject, or something to contribute to the discussion. This time I was provoked by one asked by Chad Johnson (@OchoTex), editor of HealthStandards.com and senior marketing manager with Corepoint Health.

In a recent HealthStandards.com article, Chad asks: “What do CIOs need to know about the future of data exchange?” I thought it was an interesting question; after all, everyone in HIT, including CIOs, would like to know the answer!

In his discussion, Chad argues that #FHIR could create significant change in healthcare infrastructure. He notes that if vendors like Cerner or Epic publish a capabilities-based API, providers’ technical, clinical and workflow teams will be able to develop custom solutions that connect to those systems.

As he rightfully points out, today IT departments have to invest a lot of time doing rework. Without an interface like FHIR in place, IT staffers need to develop workflows for one application at a time, rather than creating them once and moving on. That’s just nuts. It’s hard to argue that if FHIR APIs offer uniform data access, everyone wins.

Far be it from me to argue with a good man like @OchoTex. He makes a good point about FHIR, one which can’t be emphasized enough – that FHIR has the potential to make vendor-specific workflow rewrites a thing of the past. Without a doubt, healthcare CIOs need to keep that in mind.

As for me, I have a couple of responses to bring to the table, and some additional questions of my own.

Since I’m an HIT trend analyst rather than actual tech pro, I can’t say whether FHIR APIs can or can’t do what Chat is describing, though I have little doubt that Chad is right about their potential uses.

Still, I’d contend out that since none other than FHIR project director Grahame Grieve has cautioned us about its current limitations, we probably want to temper our enthusiasm a bit. (I know I’ve made this point a few times here, perhaps ad nauseum, but I still think it bears repeating.)

So, given that FHIR hasn’t reached its full potential, it may be that health IT leaders should invest added time on solving other important interoperability problems.

One example that leaps to mind immediately is solving patient matching problems. This is a big deal: After all, If you can’t match patient records accurately across providers, it’s likely to lead to wrong-patient related medical errors.

In fact, according to a study released by AHIMA last year, 72 percent of HIM professional who responded work on mitigating possible patient record duplicates every week. I have no reason to think things have gotten better. We must find an approach that will scale if we want interoperable data to be worth using.

And patient data matching is just one item on a long list of health data interoperability concerns. I’m sure you’re aware of other pressing problems which could undercut the value of sharing patient records. The question is, are we going to address those problems before we began full-scale health data exchange? Or does it make more sense to pave the road to data exchange and address bumps in the road later?

The EHR Dress Rehearsal: Because Practice Makes Perfect

Posted on July 14, 2017 I Written By

For the past twenty years, I have been working with healthcare organizations to implement technologies and improve business processes. During that time, I have had the opportunity to lead major transformation initiatives including implementation of EHR and ERP systems as well as design and build of shared service centers. I have worked with many of the largest healthcare providers in the United States as well as many academic and children’s hospitals. In this blog, I will be discussing my experiences and ideas and encourage everyone to share your own as well in the comments.

Over the past year I have been leading the implementation of Epic for University Medical Center of Southern Nevada (UMC). On July 1st, we went live at our primary care and urgent care clinics. The go-live was a great success. While no go-live is flawless, we encountered minimal issues that could not be quickly resolved and user adoption was excellent despite the majority of the users using an EHR for the first time.

Today is July 8th, and I’m spending a quiet day in our command center just one week after go-live and reflecting on the factors that made this transition exceed even our optimistic projections. By Day 3, users were comfortable with basic workflows and bills were going out the door. One week into go-live, we are scaling back our on-site support and discussing closing down the command center earlier then expected. Our team universally agrees that the most significant factor in our success was a last minute addition to the methodology – what I refer to as the Workflow Dress Rehearsal.

In my experience regardless of the quality of training that is provided, the classroom is not enough to prepare the staff for what happens when the patients start to walk in the door. Learning in your actual environment helps staff to gain comfort and uncovers challenges in technology and workflow that even the best testing will not reveal.

The concept of doing a true dress rehearsal that mirrors the real experience as closely as possible is one that dates back to retail point of sale and inventory implementations that I did 20 years ago. During those projects, we would shut the doors of the operation and have the staff go through a “day in the life” on the new system – doing everything as they would do it on go-live day – using their actual workstations and logging into the production system. We decided to apply this same concept to an EHR implementation and provide a full-day experience for the entire clinic staff as the final component of their training.

The logistics of making this happen across 8 physical locations and 15 busy clinics required extensive planning and execution. We created a full-day experience starting with scripted patients who would be represented by a clipboard that moved from the front desk and to triage before being roomed. Nurses and physicians went in and out of rooms as they would with real patients, completing the appropriate steps in each room. Later as they gained more comfort, we substituted the clip boards with actual people who represented patients – making up symptoms to help the staff learn how to navigate the EMR and be prepared for what would happen with a real person answering questions, such as providing information out of order of the screens. By the end of the day, the staff was gaining confidence in the application and in themselves. They were also learning how to work as a team in an EMR environment. Most of all, they found the experience more fun, and more directly beneficial then their classroom experience.

The benefits to this process were numerous, and the key contributor to the reduction in our support needs at go-live. Here are just a few examples of the benefits it provided:

1) Security was validated – Every user had the chance to log into production and do actual work just as they would on go-live day. As a result, security issues were resolved during the rehearsal and we had less then a dozen security calls during the first week.
2) Hardware was tested – Taking the previously completed technical dress rehearsal one step further, every workstation and ancillary hardware device was used just as it would be on go-live day. The result was we identified gaps in available hardware, incorrectly mapped printers, and configuration issues that could be resolved the same day, eliminating issues during the actual go-live.
3) End to End Workflow Validation – Nurses, Front Desk, and Physicians had received training individually as each had different content to learn, but didn’t fully appreciate how it all came together. The Workflow Dress Rehearsal allowed them to understand the full life cycle of the patient in the clinic and how their documentation impacts others later in the process. Through this process, they gained an appreciation for each of their respective roles in the EHR experience.
4) Practice, Comfort, and Speed – Working on the system in their actual work environment helped them to gain confidence and get faster using the application. While our mock patient experience is not the same as having a real sick patient in front of them – it was the closest experience that we could create so when the actual patients walked in the door, they knew what to do.
5) Content – We encouraged physicians and nurses to try common orders and medications that they use on a regular basis to make sure they were available and setup properly. Inevitably, we uncovered missing or incorrect information and were able to correct them well before go-live. The result was minimal missing content at go-live as we had already worked out those issues.

The Workflow Dress Rehearsal process allowed us to uncover many of the issues that would have happened at go-live while also allowing the staff to gain comfort with the new solution in a lower-pressure environment. The result? A quiet go-live with minimal complications and a happier staff. Encounters were all being closed the same day, and staff were going home on schedule. These rehearsals also created an educational experience that was fun and motivating to the staff and was of more value to them then another day in the classroom would have been.

I believe that this process can be applied to the implementation of any software solution in any environment. Its not always easy, and we realize that it will be much more complicated to create this experience as part of our hospital go-live later this year. However, the time invested paid off as it saved us so much time in the support of the system during go-live, and created a better experience for our patients during our first week on Epic.

Consider how you can create a Workflow Dress Rehearsal experience for your ERP, EHR, and other solution deployments and you may find that it is a critical success factor to your go-live as well.

If you’d like to receive future posts by Brian in your inbox, you can subscribe to future Healthcare Optimization Scene posts here. Be sure to also read the archive of previous Healthcare Optimization Scene posts.

We Can’t Afford To Be Vague About Population Health Challenges

Posted on June 19, 2017 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.

Today, I looked over a recent press release from Black Book Research touting its conclusions on the role of EMR vendors in the population health technology market. Buried in the release were some observations by Alan Hutchison, vice president of Connect & Population Health at Epic.

As part of the text, the release observes that “the shift from quantity-based healthcare to quality-based patient-centric care is clearly the impetus” for population health technology demand. This sets up some thoughts from Hutchison.

The Epic exec’s quote rambles a bit, but in summary, he argues that existing systems are geared to tracking units of care under fee-for-service reimbursement schemes, which makes them dinosaurs.

And what’s the solution to this problem? Why, health systems need to invest in new (Epic) technology geared to tracking patients across their path of care. “Single-solution systems and systems built through acquisition [are] less able to effectively understand the total cost of care and where the greatest opportunities are to reduce variation, improve outcomes and lower costs,” Hutchison says.

Yes, I know that press releases generally summarize things in broad terms, but these words are particularly self-serving and empty, mashing together hot air and jargon into an unappetizing patty. Not only that, I see a little bit too much of stating as fact things which are clearly up for grabs.

Let’s break some of these issues down, shall we?

  • First, I call shenanigans on the notion that the shift to “value-based care” means that providers will deliver quality care over quantity. If nothing else, the shifts in our system can’t be described so easily. Yeah, I know, don’t expect much from a press release, but words matter.
  • Second, though I’m not surprised Hutchison made the argument, I challenge the notion that you must invest in entirely new systems to manage population health.
  • Also, nobody is mentioning that while buying a new system to manage pop health data may be cleaner in some respects, it could make it more difficult to integrate existing data. Having to do that undercuts the value of the new system, and may even overshadow those benefits.

I don’t know about you, but I’m pretty tired of reading low-calorie vendor quotes about the misty future of population health technology, particularly when a vendor rep claims to have The Answer.  And I’m done with seeing clichéd generalizations about value-based care pass for insight.

Actually, I get a lot more out of analyses that break down what we *don’t* know about the future of population health management.

I want to know what hasn’t worked in transitioning to value-based reimbursement. I hope to see stories describing how health systems identified their care management weaknesses. And I definitely want to find out what worries senior executives about supporting necessary changes to their care delivery models.

It’s time to admit that we don’t yet know how this population health management thing is going to work and abandon the use of terminally vague generalizations. After all, once we do, we can focus on the answering our toughest questions — and that’s when we’ll begin to make real progress.

VA (Veteran’s Administration) Chooses Cerner EHR

Posted on June 5, 2017 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 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 and LinkedIn.

Some really big news just dropped from the VA Secretary, Dr. David J. Shulkin, that the VA has selected Cerner as their EHR replacement to VistA. You can see the full press release at the bottom of this email which outlines the VA Secretary’s reasoning for going with Cerner and the expedited process.

Without getting too much into the details of government procurement, the VA secretary has decided to use a “Determination and Findings” or “D&F” that allows him to avoid the government requirement for a full and open EHR selection and instead be able to solicit the EHR from Cerner directly. I’m pretty sure this will have many of the VistA and even the Epic people up in arms. We may even see some lawsuits out of it, but I don’t expect they’ll go anywhere. Of course, I think most of the VistA people knew this was coming ever since the VA secretary said they’d be pursuing a commercial EHR.

I think most people in the industry thought that the VA would and should go with Cerner for their EHR once the DoD chose Cerner and has since started implementing the Cerner Millennium EHR in what is now known as MHS GENESIS. The only naysayers suggested that the VA might choose Epic over Cerner just because they wanted to be different. That always seemed like a bit of a stretch to me, but it is government and so you can never know what to expect.

You can read the full press release below, but the reasons for choosing Cerner are pretty clear. The release does say that the VA will have its own instance of Cerner. So, they’ll still have to build interoperability between the DoD implementation of Cerner and the VA implementation of Cerner. This isn’t really a surprise when you think about their unique needs and the size of their implementations. Watch for the Cerner interoperability chart to go through the roof once they start sharing records between the DoD and VA.

I also found it interesting to note that the VA has a lot of community partners who are on other EHR platforms. We’ll see how interoperability goes for them. I expect they’ll likely use the standard interoperability options that are out there today.

The VA Secretary did note the concern of many VistA users when he said that “In many ways VA is well ahead of DoD in clinical IT innovations and we will not discard our past work. And our work will help DoD in turn.” I know many VistA fans who suggested that Cerner and Epic were way behing VistA in many areas and so moving to either commercial EHR would be a frustrating thing for many VA VistA users. We’ll see how well the VA Secretary can incorporate their current IT innovation into Cerner. I expect this will be an extremely hard challenge.

Not being an expert on government procurement, I’m interested to know how the VA will handle the rest of the procurement process. If you remember, the DoD’s massive EHR contract was really led by Leidos and not Cerner. Of the $9 billion contract, there were estimates that Cerner would only see $50-100 million per year of the $9 billion. The VA announcement only talks about a contract with Cerner for their EHR. Will they have to do an open bid process for all the services that Leidos and their rainbow of other partners are providing the Cerner DoD implementation?

Those are some initial high level views on this big announcement. What do you think of the announcement? Any other details I missed? Any other questions you have about it?

VA Press Release on Selection of Cerner EHR:

Today U.S. Secretary of Veterans Affairs Dr. David J. Shulkin announced his decision on the next-generation Electronic Health Record (EHR) system for the Department of Veterans Affairs (VA) at a news briefing at VA headquarters in Washington.

Secretary Shulkin’s full statement is below.

I am here today to announce my decision on the future of the VA’s Electronic Health Record system, otherwise known as EHR.

I wanted to say at the outset that from the day he selected me for this position, the President made clear that we’re going to do things differently for our Veterans, to include in the area of EHR.

I had said previously that I would be making a decision on our EHR by July 1st, and I am honoring that commitment today.

The health and safety of our Veterans is one of our highest national priorities.

Having a Veteran’s complete and accurate health record in a single common EHR system is critical to that care, and to improving patient safety.

Let me say at the outset that I am extremely proud of VA’s longstanding history in IT innovation and in leading the country in advancing the use of EHRs.

  • It was a group of courageous VA clinicians that began this groundbreaking work in the basements of VA’s in the 1970’s that led to the system that we have today, known as the Veterans Health Information Systems and Technology Architecture, or VistA.
  • It has been this system that led to the incredible achievements made by VA clinicians and researchers and resulted in VA’s ability to perform as well or better than the private sector in patient safety and quality of care.

That said, our current VistA system is in need of major modernization to keep pace with the improvements in health information technology and cybersecurity, and software development is not a core competency of VA.

I said recently to Congress that I was committed to getting VA out of the software business, that I didn’t see remaining in that business as benefitting Veterans.  And, because of that, we’re making a decision to move towards a commercial off-the-shelf product.

I have not come to this decision on EHR lightly.

I have reviewed numerous studies, reports and commissions, on this topic, including the recent commission on care report.

  • I’ve spent time talking with clinicians, and I use our legacy VistA system myself as a current practicing VA physician.
  • We have consulted with Chief Information Officers from around the country, and I’ve met personally with CEO’s from leading health systems to get their own thoughts on the best next-generation EHR for VA.
  • We’ve studied reports from management consulting companies and from the GAO and the IG on VA’s IT systems.
  • I can count no fewer than 7 Blue Ribbon Commissions, and a large number of congressional hearings that have called for VA to modernize its approach to IT.

At VA, we know where almost all of our Veteran patients is going to come from — from the DoD, and for this reason, Congress has been urging the VA and DoD for at least 17 years — from all the way back in 2000 — to work more closely on EHR issues.

To date, VA and DoD have not adopted the same EHR system. Instead, VA and DoD have worked together for many years to advance EHR interoperability between their many separate applications — at the cost of several hundred millions of dollars — in an attempt to create a consistent and accurate view of individual medical record information.

While we have established interoperability between VA and DOD for key aspects of the health record, seamless care is fundamentally constrained by ever-changing information sharing standards, separate chains of command, complex governance, separate implementation schedules that must be coordinated to accommodate those changes from separate program offices that have separate funding appropriations, and a host of related complexities requiring constant lifecycle maintenance.

And the bottom line is we still don’t have the ability to trade information seamlessly for our Veteran patients and seamlessly execute a share plan of acre with smooth handoffs.

Without improved and consistently implemented national interoperability standards, VA and DoD will continue to face significant challenges if the Departments remain on two different systems.

For these reasons, I have decided that VA will adopt the same EHR system as DoD, now known as MHS GENESIS, which at its core consists of Cerner Millennium.

VA’s adoption of the same EHR system as DoD will ultimately result in all patient data residing in one common system and enable seamless care between the Departments without the manual and electronic exchange and reconciliation of data between two separate systems.

It’s time to move forward, and as Secretary I was not willing to put this decision off any longer.  When DoD went through this acquisition process in 2014 it took far too long.  The entire EHR acquisition process, starting from requirements generation until contract award, took approximately 26 months.

We simply can’t afford to wait that long when it comes to the health of our Veterans.

Because of the urgency and the critical nature of this decision, I have decided that there is a public interest exception to the requirement for full and open competition in this technology acquisition.

Accordingly, under my authority as Secretary of Veterans Affairs, I have signed what is known as a “Determination and Findings,” or D&F, that is a special form of written approval by an authorized official that is required by statute or regulation as a prerequisite to taking certain contract actions.

The D&F notes that there is a public interest exception to the requirement for full and open competition, and determines that the VA may issue a solicitation directly to Cerner Corporation for the acquisition of the EHR system currently being deployed by DoD, for deployment and transition across the VA enterprise in a manner that meets VA needs, and which will enable seamless healthcare to Veterans and qualified beneficiaries.

Additionally we have looked at the need for VA to adopt significant cybersecurity enhancements, and we intend to leverage the architecture, tools and processes that have already been put in place to protect DoD data, to include both physical and virtual separation from commercial clients.

This D&F action is only done in particular circumstances when the public interest demands it, and that’s clearly the case here.  Once again, for the reasons of the health and protection of our Veterans, I have decided that we can’t wait years, as DoD did in its EHR acquisition process, to get our next generation EHR in place.

Let me say what lies ahead, as this is just the beginning of the process.

  • VA has unique needs and many of those are different from the DoD.
  • For this reason, VA will not simply be adopting the identical EHR that DoD uses, but we intend to be on a similar Cerner platform.
  • VA clinicians will be very involved in how this process moves forward and in the implementation of the system.
  • In many ways VA is well ahead of DoD in clinical IT innovations and we will not discard our past work.  And our work will help DoD in turn.
  • Furthermore VA must obtain interoperability with DoD but also with our academic affiliates and community partners, many of whom are on different IT platforms.
  • Therefore we are embarking on creating something that has not been done before — that is an integrated product that, while utilizing the DoD platform, will require a meaningful integration with other vendors to create a system that serves Veterans in the best possible way.
  • This is going to take the cooperation and involvement of many companies and thought leaders, and can serve as a model for the federal government and all of healthcare.

Once again, I want to thank the President for his incredible commitment to helping our Veterans and his support for our team here at the VA as we undertake this important work.

This is an exciting new phase for VA, DOD, and for the country.  Our mission is too important not to get this right and we will.