Do EHR vendors have a built-in bias?

I write from the perspective of hospitals and physicians who are required to pass tests of certifiable, meaningful use, and interoperability. As would be expected, comments made by EHR vendors are quite different from miine.   Forgive me for stating the obvious–their job is to get you to buy what their firm sells, to make you a believer.

There are more than four hundred firms who have something to sell you, something they believe will make your life better. How do you know which one of them is offering something that may work for you? How can you tell? Heck, how can you tell which product will still be viable in three years?

A question worth considering.  As passionate as the vdenors’ sales reps are, when a sales rep moves from Vendor A to Vendor B, does their passion remain with Vandor A?  Of course not.  The new “best thing since slided bread” is the thing offered by Vendor B.

Where does that leave you?  For starters, don’t buy it on faith.  Don’t buy it just because somebody else bought it–is their judgement better than yours?  You need a way to make an objective decision about some very subjective information.  One way to do that is to turn the subjective issues into quantifiable business requirements.

What do you think?

What should you budget for change management and work flows?

fruitflyhumor

They came in waves from just over the horizon, each wave approaching from different elevations, and different points on the compass. They were legion; too many to count, too many for which to be able to set a winning defense. We marshaled our forces, knowing we were helpless. As I sat there awaiting the final assault I was reminded of some of the great World War II black and white movies; Midway, Twelve O’clock High, Tora, Tora, Tora. Wave after wave of Japanese and German fighters attacking the apparently helpless US forces.


Our defense perimeter established, we waited and watched. The first wave circled twice above the cellophane covered bowl. Tiny holes were cut into the cellophane allowing the fumes from the apple cider vinegar to waft upwards. The lead fruit-fly banked left and made his assault on the target. He bounced off the cellophane, as did most of the initial flight. One by one, they recovered and made their way through the pin-prick holes. The second and third waves approached the half-covered Tupperware that held the pineapple slices. After several minutes passed we slapped the lid onto the container, trapping scores of them.

“It’s those Concord grapes,” my wife asserted, implicating the helpless grapes.

“Don’t blame the fruit,” I replied. “They’re just fruit.”  Here’s the segue, try to stay with me.

If you’ve ever flown into Chicago’s O’Hare airport you may have witnessed scores of planes stacked in the air space awaiting permission to land.  I recently made reservations for a trip to Chicago. I used Southwest’s web site to make my flight to Midway—they don’t fly into O’Hare but the illustration still works. I’m the type of person who is more suited to using a well-functioning online service to complete my business. Even so, it would not be unusual for me to be having an animated one-way conversation with my computer. I started talking to the website after having to enter the same data time after time. Don’t get me wrong; I got a great deal on the airfare—three tickets for less than I paid for one last time. The site’s design allowed me to book a hotel. I entered data to reserve three rooms to coincide with the dates of my flights. A nanosecond later, I had a confirmation code for one non-refundable, no cancellation allowed room for the night before my plane even went to Chicago. By now I was speaking to my computer in tongues.

Like with the fruit, don’t blame the computer. The software did as it was programmed.  A lot of healthcare providers are going to be amazed by what they do and don’t see from their EHR system.  The system will do exactly what it programmed to do.  That’s great news if your organization’s work flows are an exact match for those built into the code.  We both know they aren’t.  That when it becomes necessary to build work arounds.  Unfortunately, you’re building them to match your work flows to their code.  For those new to the process, you are now designing your organization to move even further away from how it presently runs.  The further away you move, the more you will require change management.  Unless you budgeted correctly months earlier, you have probably already run out of funds for work arounds and change management.  If that’s the case, your EHR system is approaching its do-over point.   For each dollar of IT spend, it probably makes sense to budget at least two dollars for these tasks.  I guess you can budget those dollars for EHR 2.0, but it may be someone else whose running the implementation.

black saint 2

How’s the EHR vendor performing?

cat

Many organizations have a Program Management Office and a Program Steering Committee to oversee all aspects of the EHR.  Typically these include broad objectives like defining the functional and technical requirements, process redesign, change management, software selection, training, and implementation.  Chances are that neither the PMO or the steering committee has ever selected or implemented an EHR.  As such, it can be difficult to know how well the effort is proceeding.  Simply matching deliverables to milestones may be of little value if the deliverables and milestones are wrong.  The program can quickly take on the look and feel of the scene from the movie City Slickers when the guys on horseback are tyring to determine where they are.  One of the riders replies, “We don’t know where we’re going, but we’re making really good time.”

One way to provide oversight is to constantly ask the PMO “why.”  Why did we miss that date?  Why are we doing it this way?  Tell me again, why did we select that vendor?  Why didn’t we evaluate more options?  As members of the steering committee you are responsible for being able to provide correct answers to those questions, just as the PMO is responsible for being able to provide them to you.  The PMO will either have substantiated answers, or he or she won’t.  If the PMO isn’t forthcoming with those answers, in effect you have your answer to a more important question, “Is the project in trouble?”  If the steering committe is a rubber stamp, everyone loses.  To be of value, the committee should serve as a board of inquiry.  Use your instincts to judge how the PMO responds.  Is the PMO forthcoming?  Does the PMO have command of the material?  Can the PMO explain the status in plain English?

So, how can you tell how the EHR effort is progressing?  Perhaps this is one way to tell.

A man left his cat with his brother while he went on vacation for a week. When he came back, he called his brother to see when he could pick the cat up. The brother hesitated, then said, “I’m so sorry, but while you were away, the cat died.”

The man was very upset and yelled, “You know, you could have broken the news to me better than that. When I called today, you could have said the cat was on the roof and wouldn’t come down. Then when I called the next day, you could have said that he had fallen off and the vet was working on patching him up. Then when I called the third day, you could have said he had passed away.”

The brother thought about it and apologized.

“So how’s Mom?” asked the man.

“She’s on the roof and won’t come down.”

If you ask the PMO how the project is going and he responds by saying, “The vendor’s on the roof and won’t come down,” it may be time to get a new vendor.

black saint 2

If a Certified system is so special, offer a certification warranty

I think that certifying the EHR product prior to installing it is worthless. Certification to me means that the product is capable of performing some function.   If certification is of any value, the fact that it’s certified means it should still be certifiable after it’s installed.

We all know that that is not the case. If the feds think it’s so important to certify the EHR products, let’s certify them after installation.   The large vendors are the ones pushing certification.  They do it for one reason, to limit competition.  If the vendors think certification somehow implies that their product is somehow better because it has been certified, let them offer a cost free warranty and re-certify it after installation.

It’s an easy test.  Let’s see how many of them respond to this plan.

021_18A

How do I know if we’re in trouble?

FunnyCheckDoes anyone remember how many of each type of animal God told Moses to put on the ark? Are you sure? For those who missed it, Noah built the Ark, Charlton Heston built the stone tablets.

One word can make the difference between right and wrong, especially if the question is big enough. Who is asking the questions that are shaping your firm’s EHR strategy? Are they asking the right ones?  What are the right questions?  If your the person responsible for the money that will be spent on EHR, any of these deserve an answer;

  • If the ARRA money went away tomorrow, would we still be doing EHR?
  • May I see a copy of our EHR plan?
  • Who vetted the plan?
  • If so, would we still be doing it the same way?
  • Would we still have selected this vendor?
  • Did we issue an RFP?
  • How did we choose who received the RFP?
  • What criteria did we use to select the vendor?
  • Who in our shop had any experience writing an RFP of this nature?
  • Who has ever evaluated an RFP like this?
  • What commitments do we have from the vendor about meaningful use?
  • What commitments do we have from the vendor if meaningful use changes?

These are very basic questions, but I bet if you ask them of your team, you will not be pleased with several of the answers.  If they can answer all of them to your satisfaction, they may proceed to step two.  If not, send them back for another try.draft_lens5971462module46826602photo_1247932409Creative_Loafing_-_Hanging_out_-_GBowen

A thought about EHR companies

Just a brief note to provide a link to my comments on the blog EHR Blog about EHR Vendors.

http://www.ehrscope.com/blog/electronic-medical-records-companies/comment-page-1/#comment-792

saint