planning

My remarks to Brian Ahier’s insightful interview of Dr. Blumenthal

Posted by

1

I encourage those who have not read Brian’s interview of Dr. Blumenthal on HealthSystemCIO.com to make time to read it.  http://healthsystemcio.com/2010/03/27/chatting-with-the-national-coordinator-for-health-it/#comments

Brian also has a link to the audio.

Brian asked me to comment, and I was pleased to do so.  Here is what I wrote.

I enjoyed reading your interview with Dr. Blumenthal. Clearly he and the members of his team are working very hard on a number of difficult and rather diverse issues.

I have been wondering, how does one tell the story of EHR to someone who has no understanding of EHR? Not the story about the EHR system in a physician’s office, or the ungainly one in a hospital. The story to which I refer is the story of the national rollout of EHR and the drive for interoperability.

For me, the question of how to tell the story in a way to make it understandable raises a number of other questions. Is there a story, or is it a collection of short stories written by different people, guided by different principles and goals? Is there a plot? Does the story come together in a natural manner?

Sticking with the story theme for a moment—who are the main characters, do they relate to one another? Does it come to a meaningful conclusion, in fact, does it conclude?

Look at the various antagonists—EMR, EHR, PRH, Meaningful Use, Certification, HIEs, RECs, the N-HIN, interoperability, the ONC, CMS, ARRA, standards, vendors, and PR. I am sure I missed several.

Imagine if Random House allocated millions of dollars to publish and market a book which had yet to be put to paper. No plot, no outline. What if they hired a dozen writers, each with their own areas of expertise—and lack of expertise—and crossed their fingers.

Would they be more successful if they offered penalties and incentives to the writers—a garrote and stick approach? What if they changed the rules after the writers started? What if they left undefined numerous areas of rules, rules which will impact the story, and told the writers to keep pushing ahead?

I do not see how the national EHR rollout story comes together. Now or some distant tomorrow—at least not under this approach. Is the approach viable? Having a few disparate successes does not make me a believer. Call me a cock-eyed nihilist.
Once every so often, an announcement is made that another single hospital reached Stage 7. One among thousands. Why do I view this from the vantage point of a glass half-empty? For me, the existing approach is one of guidance and facilitation. There are no long lines of providers trying to beat the others to the front of the EHR line. There have been several hundred million dollar do-overs.

If we circle back to the providers for a second, three of the largest causes of failure include the arbitrary setting of go-live dates without knowing what needs to be done or can be done in that time frame; second, letting IT and the vendor drive and manage the project; third, not getting users to define what they need and then having IT replicate those needs. IT does not need an EHR.

As I look at the government’s national rollout of EHR I see the same three problems. Who are the government’s users? Doctors, clinicians, and hospitals. There are fixed dates, many having undefined requirements. These are causing some providers to dash for the cash. Who is driving the rollout—the government’s users, or the government. They way the rollout is structured, the users have all of the responsibility and little of the authority. This is a government led IT project. Where are their users? They are running their practices and hospitals. They have one ear open towards, reform, another to the garrote and stick project rollout approach, another to EHR, and yet another to their business model. They have run out of ears.

Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942

My profiles: WordPressLinkedInTwitterMeetupBlog RSS

EHR-the 40 chicken crocodile

Posted by

3

Got a couple hundred million burning a hole in your pocket?  Why not buy an EHR?  Indeed.

Riddle me this Batman, “What is a 40 chicken crocodile?”

It is the number of chickens you have to feed it each day to keep it from eating you. What is the crocodile at your hospital?  Is it your EHR?

Let me recount to you a true story about the details of one of the EHR “success” stories.  A major hospital who selected their EHR from among one of what I like to call the oligopoly EHR Flavor of the Month Club.  You know the suspects.

Permit me to throw a wrench to those clairvoyants who think they know where this is going before I’ve even written it.  Admittedly, I have a tendency to throw metaphorical tomatoes in one direction—that of the vendors.  That’s because, they are often easy targets.  Slow down Pepito.

This hospital, and from what I was told, the vendor, did it right.  I am not sure I would have differed from the approach of either.  The hospital spent a few years in its vendor selection process, and they were very thorough.  They spent two years building their process maps, ensuring the vendor implemented the EHR to meet their needs, not the other way around.  Operations led the nine-figure project.

They implemented many of the support functions and a few of the specialty functions.  Here come the chickens.  After implementation, cash flow dropped by 80 percent for several months due to significant issues they encountered cleaning up the revenue side.  Doctors were instructed to cut their hours by fifty percent to allow them to learn to use the system.  Hours are still down by twenty percent, well more than a year later.  Users use about one-third of the functionality, even after a rigorous training program.

The hospital held off doing most of the clinical implementations for two years.

I asked for some recommendations.  What would you have done differently?  Here’s what I learned.  If you have a research organization you need to spend extra special attention to their workflows.  Managing post-go-live was a big issue to begin to offset productivity losses. Without a continuous process improvement program the EHR would not have been accepted. Do not pick a go-live date at the outset of the project as it causes the organization to be paralyzed simply to hit the date.  Testing was compromised to meet the go-live date. The post go-live issues are still being fought.  Do not let the design or build teams skimp on either reporting or testing, they are still playing catch-up.

So, after doing a pretty bang up job, at least from where I sit, there are still a lot of chickens being fed to the crocodile.  Wonder how many chickens it would have taken had the users not been as involved as they were.  How many had the users not spent two years pre-build defining processes?  A lot.  Now comes the rest of the clinical effort.  See you at the poultry counter.

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

What if hospital business models weren’t so tribal?

Posted by

0

I tend to look at it from the perspective of the business model of many hospitals.  How does one transform a 0.2 business model to function in today’s let alone tomorrow’s changing healthcare model?

The clinical side of healthcare, the healthcare business, in juxtaposition to the business of healthcare, would never quarter to the idea of buying millions of dollars of technology without first knowing how they were going to use it.

Plenty can be gained by applying what other industries have done to become more effective.  In some respects the inherent structure, cost duplication, and rigid departmental silos remind me a lot of how the various agencies under Homeland Security function, operating in isolation, performing much of the same work, and not sharing information.

Other industries operate with a much less tribal model than healthcare.  Hospitals have created tribes and tribal chiefs.  In some hospitals the tribes have names like radiology, general surgery, psychiatry, and OBG/YN.  Other hospitals have redundant tribes named admissions, human resources, IT, and payroll.  Each tribe is run by the tribe’s chief.  The chief’s dominant weapon is his or her budget which is lorded over its individual tribe, and a dispute vehicle of the other tribes.

The tribal organization is more a reflection of how the hospital evolved over the years, not a result of an inept business strategy.  Nobody set out to build an ineffective and internally competitive model, or one that duplicated support functions.  Acquisitions have reinforced and exacerbated the problem, duplicating and increasing costs without yielding a resultant increase in value.

Before the business of healthcare is prepared to cope with the unknowns of the myriad of external influences it will face in the next few years, it must first change how it functions under its current structure.  It might begin by revisiting its present structure and making sure that its performance and quality precede the application of technology.

I frown on using the term efficient.  To me, efficiency implies speed, and doing bad things faster is no solution.  Let us work at improving effectiveness and good things will happen.

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

The Wildebeest Postulate

Posted by

0

The Kalahari; vast, silent, deadly. The end of the rainy season, the mid-day heat surpasses a hundred and twenty. One of the varieties of waterfowl, most notably the flame red flamingo that nested in the great salt pans in Botswana, has begun its annual migration. In the muck of one of the fresh-water pools that had almost completely evaporated, writhes a squirming black mass of underdeveloped tadpoles. A lone Baobab tree pokes skyward from the middle of the barren savanna. In its shade, standing shoulder to shoulder and facing out, a herd of wildebeest surveys the landscape for predators.  Sir David Attenborough and PBS can’t be far away.

Some things never change. I make my way across the freshly laid macadam to meet the school bus. Fifty feet in front of me is a young silver maple tree, the buds of its green leaves yielding only the slightest hint of spring hidden deep within. The late afternoon sun casts a slender shadow across the sodded common area. One by one they come—soccer moms; big moms, little moms, moms who climb on rocks; fat moms, skinny moms, even moms with chicken pox—sorry, I couldn’t stop myself—as they will every day at this same time, seeking protection in its shade. My neighbors.  It’s only sixty-five today, yet they seek protection from the nonexistent heat, a habit born no doubt from bygone sweltering summer days. A ritual. An inability to change. In a few weeks the leaves will be in their full glory, and the moms will remain in the shadow of what once was, standing shoulder to shoulder facing outward, scanning the horizon for the bus. A herd. Just like wildebeest.

The children debus–I invented the word.  Mine hand me their backpacks, lunch boxes, and musical instruments.  I look like a Sherpa making my way home from K-2.

I shared this analogy with the neighborhood moms—the bruises will fade gradually. I can state with some degree of certainty they were not impressed with being compared to wildebeest. So here we go, buckle up. By now you’re thinking, “There must be a pony in here somewhere.”

Some things never change; it’s not for lack of interest, but for lack of a changer.  For real change to occur someone needs to be the changer, otherwise it’s just a bunch of people standing shoulder to shoulder looking busy. How are you addressing the change that must occur for EHR to be of any value?  EHR is not about the EHR.  It’s not about ARRA money, and it is not about IT.  It is about moving from a 0.2 business model to 2.0.  You need someone who sees the vision of what is is—sorry, too Clintonian—must lead.  Be change.

One of the great traits of wildebeest is that they are great followers.

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

Puppy Training Your Vendor

Posted by

3

Carrie Vaughan, a senior editor of HealthLeaders Magazine published an article in the December 8, 2009 issue titled, “Tips to Build a Successful Vendor-Provider Partnership.”  The link to her article is http://www.healthleadersmedia.com/page-2/MAG-243167/Avoid-the-Vendor-Upsell.

The points about which Carrie wrote are spot on.  I asked Carrie if she would permit me to use those same points as a foundation for this posting, to which she was kind enough to agree.  The four points come from her article.  I encourage you to read her piece, as any points with which you may take umbrage are mine, not hers.

To ensure we take an accurate look at the provider-vendor relationship, we must be willing to acknowledge that healthcare providers are from Mercury and the EHR vendors are from Pluto.  They exist in different orbits, and their business models are very far apart—they never intersect; not in space, and not on your project.

1. Have your own inside expert. Don’t rely on the vendor to tell you what you should be doing.  Never.  Ever.  Unless of course you think the vendor knows more about how you want to run your hospital than you do.  Remember, you select them—not the other way around.

Bringing a vendor into your hospital is a lot like bringing home a new puppy. Both need to know who runs the show. Don’t roll over.  They may not be looking to be led, but if you don’t lead them they will lead you.

You should have the expert on board at the outset, before you select the EHR vendor.  The expert should be your advocate.

2. Establish a specific executive liaison with your vendor.  This is not your new tennis partner.  This should be the person who has the authority to ensure your quantifiable wishes are being met, and whose responsibility it is to deliver the message to his troops, and marshal the resources necessary to get the job done.

3. Specify your contractual objectives. Ensure that the contract is aligned with the clinical and business objectives of the healthcare organization, not the vendor.  Before you can accomplish this, you have a lot of work to do with your team.  You must define your clinical and business objectives.  Often these two groups also have a Mercury and Pluto relationship.  Once you have these, your next task is to deliver these objectives to the vendor and have the vendor tell you in writing what they will meet, what they might meet, and what they can’t meet.  It would be nice to know these before you sign their contract.

4. Involve more people than just the IT staff. Need a rule of thumb, involve as many users as IT people—Mercury and Pluto.  You will need new processes, not just to squeeze an ROI from the EHR, but because many of your old ones have probably been around since the invention Band-Aid.

Each of these recommendations will actually help you and help your vendor be successful.  It will not be an adversarial relationship as long as you manage it.  If you don’t manage the relationship, you won’t have to worry about meeting Meaningful Use—you’ll be too busy selecting a replacement vendor.

One final thought, don’t let the vendor loose unsupervised on the oriental rugs.

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

Users are from Mercury, IT is from Pluto

Posted by

4

The two groups are often far apart.

I learned an interesting word which led to some very interesting reading on the topic.  The word and topic are qualia (pl).  There are several wordy explanations with which I won’t waste your time.

Daniel Dennett identified four properties that are commonly ascribed to qualia. According to him, qualia are:

  1. ineffable—they cannot be communicated, or apprehended by any other means than direct experience—see, touch, taste, hear, smell.
  2. intrinsic—they are what they are independent of anything else.
  3. private—interpersonal comparisons of qualia are impossible.
  4. directly or immediately apprehensible in consciousness—to experience a quale is to know one and to know all there is to know about that quale.

Got it?  That didn’t do it for me either.  Here are a few examples that helped me understand it.

  • How does wet feel?
  • What does blue look like?
  • What is the smell of mowed grass?
  • How does salt taste?
  • What is the sound of a whisper?

Common things.  Our brain knows what they are, yet to describe them to someone who has not experienced them, almost indescribable.  Your brain processes it one way, your mind processes it another.  Take a look at these pictures.

Now let’s look at healthcare IT projects, to be more particular, implementing an electronic health records system, an EHR system.  When you pictured the implementation in your mind, when you studied the implementation plan it painted a nice picture.  All the pieces made sense—sort of like the picture on the left.

At some point after most EHR implementations, the IT department still sees a pony.  The users can’t see the pretty picture.  Trying to explain what went wrong to the steering committee is like trying to describe to them the color blue.

IT people are able to look at the picture on the left and visualize the picture on the right.  When IT people talk to users, to the users it sounds like the picture on the left…

…and it feels like this.

It matters what the users think, and see, and feel.  If IT waits until the end to involve the users, the users will never see a pretty picture.  I’ll let you in on a secret.  In many hospitals the users (doctors and nurses) do not think IT has any understanding of their business.  Why prove them correct by keeping them out of the loop.  Their input is at least as important as IT’s and the vendor’s—probably more so.

“Look what we built for you” is not what the users need to hear.  “Look what we did together” has a much better chance of succeeding.

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 85-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

How to handicap selecting your EHR

Posted by

0

Several years ago I was invited to go on the ultimate boys’ toys, weekend getaway. A dozen of us flew from Denver to Utah, and then drove to a point somewhere west of Bozeman Montana. It was to be a weekend of sport, a weekend of competition, and a more than occasional libation. To say that the people who organized the trip came from money would be a major understatement. They were in the oil bid’ ness. The father of one of the guys was the CEO of the second or third largest petroleum company in North America. We stayed at his ranch, a 12 bedroom log cabin in the middle of Nowhere, Montana, which is about 20 miles west of Next to Nowhere, Montana.

The weekend’s activities included fly fishing, duck hunting, and Gin Rummy. Each participant was given a handicap rating in each event. The idea behind the rating was that if you are weak in one event, you were paired with an individual who is skilled in that event. In theory, that would level the playing field among the teams. Since I have never fly-fished or hunted I was odd man out. But I was game, and it’s amazing how good one can become at something when one has to fight their way through it.

Let the games begin. We started the competition with a full day of fly-fishing. Our destination was the Madison River, an impressive, fast running, expanse of snow melt. The stretch we would finish was about 150 feet wide, and its average depth was somewhere between waist and chest high. As I would soon learn the bottom was covered with what appeared to be the equivalent of moss covered bowling balls. I was instructed by one of the more experienced fishermen to tie a nymph to the end of the tippet. For those of you who are as novice to the sport as I was, a nymph is an artificial lure which mimics an insect larva. It is designed to lure fish who feed along the bottom, not the nubile young woman referenced in Greek mythology.

We fished for several hours. My legs ached from trying to maintain my balance in the strong current. I was about ready to admit defeat when the tip of my rod bent sharply into the water. Standing perpendicular to the current, I could see as the brightly speckled back of a large rainbow trout turned upstream. Naturally, I turned upstream with it and began to try to reel him in. First mistake. It was at that point that I first realized that the height of the water was now about level with my chest waders. Second mistake. The guys on the other part of the river and along the bank were yelling at me. I thought it was words of encouragement. Final mistake. As it turns out, they were trying to convince me not to turn upstream. At the exact moment that I faced stream head on, was the exact moment my feet lost purchase with those moss covered bowling balls of which I wrote. Turning yet again to my physics, I quickly recalled the equation; force equals mass times acceleration. Instantaneously, I was swept downstream, still clutching my fly rod in my right hand.

Wayne Newton’s first law of fluid mechanics took over; waders, no matter how good they are, if positioned in a plane that is horizontal to the river will fill rapidly with water, just as mine did. The choice with which I was faced was do I save myself and lose the fish, or do I try and land the fish? One of the shortcomings of maleness—I was going to use maledom until I Googled it—is that we rarely have actual choices, especially when we are around other males or for that matter, females. Naturally, I opted to land the fish. My reel had become dislocated from my rod. I remember grabbing the reel and stuffing it down my waders, and as I tried to float my body as though it was a raft without a rudder towards the river’s nearest bank, I began to reel in the monofilament with a hand over hand motion. After several minutes I was standing dripping wet and proudly displaying a 19 inch rainbow trout.

We cooked the fish and played Rummy until about three in the morning, awoke at four, grabbed our shotguns and headed out into the darkness without so much as a cup of coffee. Round three of the competition was to be duck hunting. To this day I’m still unclear as to why we had to hunt ducks while it was still dark. Weren’t there any ducks who needed shooting at brunch time, I inquired? Twelve guys, who collectively smelled like a distillery, and who are operating on an hour of sleep, armed with loaded shotguns, trod through a willow thicket as dawn approached. As I neared the river bank, a startled duck shot skyward. I raised my over and under twelve-gauge shotgun, sort of took aim, and fired a volley. The duck seemed to pause in midair, and then fell like a rock into the racing water. I watched helplessly as my quarry floated away from me. I looked downstream and was pleased to see two men fishing from a rowboat. The duck floated right towards them. A man reached down, retrieved my duck, and dropped it in his boat. He then waved to me. Thinking he was being friendly I returned his wave. He then rowed away with my duck.

It was a great three days. Part of what made the weekend fun with not having to excel at each event. It helped knowing that in areas where my skills were not as good, I could count on the skills of others and vice versa. The idea behind this approach was to build competitive and level teams. That approach works well in mano y mano events like those I described. It works much less well in EHR, HIT and healthcare reform in general.  I’m trying to recall if I wrote previsouly about a meeting I attended with a former hospital CEO.  His take on EHR was the total inability of his peers to have any precience regarding their approach to EHR.  According to him, very intelligent people were making very unintelligent decisions, committing their entire institution to strategies made with almost no data.  Some people can give a better explanation for why they bought their car than they can for why they selected their EHR.   That’s the wrong way to handicap this event.

There are two ways to handicap your EHR.  One way is to look at the program from the perspective of risk assessment and assess–handicap–the risks.  The other way to to be a detriment to the program’s success.  One of these is bad.

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 85-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

Parallel universes–replacing one EHR for another

Posted by

4

Some providers are changing their EHR system.  Why?

Why indeed?  What precipitates the need to change?  I bet if you take the top five or seven EHRs, and compare them to a rigorous set of requirements you will find they all score within one standard deviation of the norm.  You won’t hear that from the vendors, but they are the same with regard to the major functionality.

There is no single vendor who scores head over heels above the others.

I bet if you interviewed their customers you will not find a customer which thinks their vendor is the be-all end-all of healthcare.  In fact, you will learn at best most clients will score their satisfaction with their vendor mediocre. Depending on what numbers you read, you will see failure rates in excess of fifty percent.  Failure, by my metric, has more to do with what someone did or did not do to the application than it has to do with the application itself.  This is a “Do these pants make me look fat?” issue.  Guess what, it’s not the pants.

Is there a single vendor who can state that none of their clients has ever replaced them with one of their competitors? That means if you are thinking of replacing EHR A with EHR B, another hospital is thinking of replacing EHR B with EHR A.  Parallel universes, or is it universi?

The grass will not be greener.  Here is what will.  A lot of hospitals operate with what can best be described as anything but best processes–worst processes.  No EHR can handle those.  Before you begin again, evaluate your processes. Weed out the bad ones, do away with the duplicates.

Are you willing to spend another hundred million or two hundred million dollars to get marginally higher satisfaction? Instead, how much would you have to spend to change your processes, implement a change process, retrain your people, and devise a system to bring in your ambulatory doctors?  It would certainly not exceed nine figures.

EHR need not be a do-over.  For those just getting started, do process prior to implementation, not after.

It’s not the pants.

How should a provider approach Meaningful Use?

Posted by

0

New Headquarters?

The following is my reply to a post in HealthcareITNews from March 8.  The title of the post is, CONSUMERS WEIGH IN ON TOP 10 MEANINGFUL USE ARGUMENTS.  The link is, http://www.healthcareitnews.com/news/consumers-weigh-top-10-meaningful-use-arguments#comment-574

Of cabbages—and kings—

And why the sea is boiling hot—and whether pigs have wings. Lewis Carroll, Out of the Looking Glass. It is a nonsense story, one which cannot be argued.

As are Electronic Health Records (EHR) and Meaningful Use (MU)—at least to date. Measured against any reasonable set of standards, except on a one-off basis, the national rollouts of EHR and MU have failed. I expect it will be even more so next year.
You, the public, have the right to comment, and we have the right to tell you why your comments hold no water. I think it is the inverse of you have the right to remain silent, you just don’t have the ability. I am writing about the ONC and the bone they tossed calling for public comment. They are required to provide for public comment in order to remove the N and the P from the NPRM.

Who among us believes the rule making will markedly shift direction as a result of any of the public comments? That is unfortunate for if they were to shift direction they might find a direction. We don’t know where we are going, but we are making good time getting there. Figures suggest a failure rate of EHR implementations of somewhere between fifty and seventy percent. As healthcare IT resources become scarcer, I expect the failure rate to increase. As providers rush into EHR without a detailed strategy simply to grab the incentive money, there will be more expensive failures. More failed EHRs is not a way to measure progress.
The current cover of Government Health HIT magazine depicts a foot race to meet MU. There is no race if there are no entrants. There may be more people on the cover than will actually qualify for the race, even fewer who will reach the end.

We would be better served if the plan for national rollout of EHR were not written on an Etch-A-Sketch. We don’t know what will be included in Stages 2 and 3 of MU. When will fifty percent of providers have an EHR, not just the software, but one that actually boosts productivity? How about 70% or 80%? Ten years? I ask the same question of the Health Information Exchanges (HIEs). Without unilateral adoption there will be large gaps. Will the national network function with these gaps? To what extent? Will the records only make it part of the way from Patient A to Doctor X?

Having not solved the EHR program on their own, and having no viable plan, the government laid the burden of making EHR successful on the backs of the providers. The government tries to offset the burden by offering financial gratuities—and penalties—to the providers. Not exactly the second coming of the Three Wise Men. Trying to hit the ONC’s targets is a little like playing the confidence game, the shell game. Under which shell will providers find the rules, the plan?
What to do?

It is easy to criticize. Permit me to offer a few suggestions. To the hospitals, if you are not well along the EHR path, do not make a difficult effort more difficult by chasing Gossamer incentive dollars. Stick to your plan. You have multiple failure points which three years from now will make chasing those dollars look like a pipe dream. The failure points? Your plan, the implementation, meeting the MU requirements, passing the MU audit. It does not look very promising to me.

To those hospitals which haven’t started their EHR initiative, or are less than halfway through the passing the failure points, don’t cancel your summer vacation. You have a lot more time to get it right then you have to get it wrong. Pay no attention to the man—or woman; even I can have a moment—handing out the Monopoly money. You won’t be receiving any. From where I sit, that is good news. It will cost a lot more to perform disaster recovery on a poor implementation than the funds you would have received by meeting MU.

How long does a hospital spend planning to build a new hospital wing? For large hospitals, the cost of your EHR will likely exceed the cost of the new wing. Plan accordingly. Invest six or nine months building a plan that might succeed.

For medium and small practices and solo providers you have nothing to lose by waiting a year months other than the resource problem. By then you will find very viable ASP and shrink-wrapped solutions.

Those who follow my blog, healthcareitstrategy.com, know I don’t write to garner favorable replies from those who think they’ve already got it figured out. I write for those who because of EHR have difficulty sleeping. Thanks for reading. As always, I appreciate your comments and disagreements.  

EHR–the five stages of grief

Posted by

0

The Kübler-Ross model, commonly known as the five stages of grief, was first introduced by Elisabeth Kübler-Ross in her 1969 book, On Death and Dying.  I heard a story about this on NPR, and it made me think about other scenarios where these stages might apply.

My first powered form of transport was a green Suzuki 250cc motorcycle.  My girlfriend knitted me a green scarf to match the bike.  One afternoon my mother walked into the family room, saw me, and burst into tears.  When I asked her what was wrong, she told me that one her way home she saw a green motorcycle lying on the road surrounded by police cars and an ambulance—she thought I had crashed.  I asked her why, if she thought that was me lying on the road, she did not stop.

My girlfriend’s mother, didn’t like my motorcycle—nor did she like me.  Hence, my first car; a 1969 Corvair.  Three hundred and fifty dollars.  Bench seats, AM radio.  Maroon—ish.  It reminded me a lot of Fred Flintstone’s car in that in several places one could view the street through the floor.  Twenty miles per gallon of gas, fifty miles per quart of oil.

Buyer’s remorse.  We’ve all had it.  There is a lot of buyer’s remorse going around with EHR, a lot of the five stages of grief.  I see it something like this:

  • Denial—the inability to grasp that you spent a hundred million dollars or more on EHR the wrong EHR, one that will never meet your needs
  • Anger—the EHR sales person received a six-figure bonus, and you got a commemorative coffee mug.  The vendor’s VP of Ruin MY life, took you off his speed dial, unfriended you in Facebook, and has blocked your Tweets. You phone calls to the vendor executive go unanswered, and are returned by a junior sales rep who thinks the issue may be that you need to purchase additional training.
  • Bargaining—when you have to answer to your boss, likely the same person who told you which system to purchase, as to why productivity is below what it was when the physicians charted in crayon.
  • Depression—you come in at least fifteen minutes late, and use the side door, taking the stairs so you won’t see anyone.  You just stare at your desk; but it looks like you are working. You do that for probably another hour after lunch, too. You estimate that in a given week you probably only do about fifteen minutes of real, actual, work. (Borrowed from the movie, Office Space.)
  • Acceptance—the EHR does not work, it will never work, you won’t be around to see it if it ever does.  Your hospital won’t see a nickel of the ARRA money.  You realize the lake house you were building will never be yours, but the mortgage will be.

The five stages of EHR grief.  Where are you in the grieving process?

True, there are a handful of EHR successes.  Not nearly as many as the vendors would have you believe.  More than half of hospital EHR implementations are considered to have failed.

If you are just starting the process, or are knee-deep in vendor apathy you have two options.  You can bring in the A-team, people who know how to run big ugly projects, or you prepare to grieve.

If it was me, I’d be checking my list of friends on Facebook to see if I was still on my vendor’s list of friends.