EHR: Managing the changes to your organization

I reside where those who refuse to drink the Kool Aid reside. For those who haven’t been there, it’s a small space where only those who place principle over fees dare to tread.

Where to begin? How to build your team? (Those who wish to throw cabbages should move closer to the front of the room so as not to be denied a decent launching point.) There are two executives, I hasten to add, who will defend what I am about to offer, a CIO, and a CMIO, ideas from both of whom you’ve probably read.

I comment on behalf of those in the majority who have either not started or hopefully have not reached the EHR points of no return—those are points at which you realize that without a major infusion of dollars and additional time the project will not succeed. Those who have completed their implementation, I dare say for many no amount of team building will help. Without being intentionally Clintonian—well, maybe a little—I guess it depends on what your definition of completed is.

If I were staffing, to be of the most value to the hospital, I’d staff to overcome whatever is lying in wait on the horizon. I believe that staffing only to execute today’s perceived demands will get me shot and will fail to meet the needs of hospital. I need to exercise an understanding of what is about to happen to healthcare and to build a staff to meet those implications for healthcare IT.

Several CEOs have shared that they are at a total loss when it comes to understanding the healthcare issues from an IT perspective. They’ve also indicated that—don’t yell at me for this—they don’t think their IT executives understand the business issues surrounding EHR and reform. I disagree with that position.

Here’s a simplified version of the targets I think most of today’s CIOs are trying to hit.

1. Certification
2. Meaningful use
3. Interoperability—perhaps
4. Budget
5. Timing
6. Vendor management
7. Training
8. User acceptance
9. Change management
10. Work flow improvement
11. Managing upwards

There are plenty of facts that could allow one to conclude that these targets have a Gossamer quality to them. Here’s what I think. You don’t have to believe this, and you can argue this from a technology viewpoint—and you will win the argument. I recently started to raise the following ideas, and they seem to be finding purchase—I like that word, and since I’m writing, I used it.

Before I go there, may I share my reasoning? From a business perspective, many would say the business of healthcare (how it is run) is being moved from 0.2 to 2.0. The carrot? Stimulus funding—an amount—should you earn it, and you will probably want to since your CFO has already built it in to the budget—that will prove to be more of a rounding error than a substantive rebate. Large providers are being asked to hit complex, undefined, and moving targets. They are making eight and nine figure purchase decisions based in part on solving business problems they don’t articulate. If success is measured as on time, in budget, and functional and accepted, I estimate for any project in excess of $10,000,000, the chances of failure are far greater than the chances of success.

The overriding business driver seems to be that the government has told providers to do this. Providers are making purchasing decisions without defining their requirements. Some will spend more on EHR than they would to build a new hospital wing. They don’t know what it should cost, yet they have a budget. They don’t know if they need a blue one or a green one, if it comes in a box, or if they need to water it.

So, where would I staff—this is sort of like Dr. Seuss’, “If I ran the Circus”—the one with Sneelock in the old vacant lot. I’d staff with a heavy emphasis on the following subject matter experts:

  • PMO
  • Planning & Innovation
  • Flexibility
  • Change Management
  • PR & Marketing
  • And..Disaster Recovery

None of these high-level people need to have much if any understanding of healthcare or IT. You probably already have enough medical and IT expertise to last a lifetime. That will account for about fifty percent of the success factors.

Here’s why I think this is important. Here’s what I believe will happen. Three to five years from now there will not be a network of articulated EHRs with different standards, comprised of hundreds of vendor products, connected to hundred of Rhios, and mapped into a NHIN. Under the current model, standardization will not occur if only for the fact that there is no monetary value to those whose standards are not standard to make them so. This discussion is orders of magnitude more complex than cassettes and 8-tracks.

Interoperability, cost, and the lack of standardization will force a different solution. I think the solution will have to be something along the lines of a single, national, open, browser-based EHR. Can an approach to solving this be pieced together by looking at existing examples like airline reservations, ATM, OnStar, Amazon, FaceBook, and others? I believe so. Are some of my words and examples wrong? Count on it. Please don’t pick a fight over my lack of understanding of the technology.

The point I am trying to drive home is that from a staffing perspective, lean towards staffing the unknown. Staff it with leaders, innovators, and people who can turn on a dime. Build like turning on a dime is the number one requirement. Don’t waste all of your resources on certification or meaningful use. If anyone asks you why, you can blame me. If you want a real reason, I have two. First, they won’t mean a thing three years from now. Second, if I am the person writing a rebate check, I want to know one and only one thing; can your system connect with the other system for which I am also writing a check.

However, when all is said and done, I call upon us to remember the immortal words of Mel Brooks “Could be worse, could be raining.”

 

EHR: When you’re in a hole, stop digging

rappelling_1_1I was thinking about the time I was teaching rappelling in the Rockies during the summer between my two years of graduate school.  The camp was for high school students of varying backgrounds and their counselors.  On more than one occasion, the person on the other end of my rope would freeze and I would have to talk them down safely.

Late in the day, a thunderstorm broke quickly over the mountain, causing the counselor on my rope to panic.  No amount of talking was going to get her to move either up or down, so it was up to me to rescue her.  I may have mentioned in a prior post that my total amount of rappelling experience was probably no more than a few more hours than hers.  Nonetheless, I went off belay, and within seconds, I was shoulder to shoulder with her.

The sky blackened, and the wind howled, raining bits of rock on us.  I remember that only after I locked her harness to mine did she begin to relax.  She needed to know that she didn’t have to go this alone, and she took comfort knowing someone was willing to help her.

That episode reminds me of a story I heard about a man who fell in a hole—if you know how this turns out, don’t tell the others.  He continues to struggle but can’t find a way out.  A CFO walks by.  When the man pleads for help the CFO writes a check and drops it in the hole.  A while later the vendor walks by—I know this isn’t the real story, but it’s my blog and I’ll tell it any way I want.  Where were we?  The vendor.  The man pleads for help and the vendor pulls out the contract, reads it, circles some obscure item in the fine print, tosses it in the hole, and walks on.

I walk by and see the man in the hole.  “What are you doing there?”  I asked.

“I fell in the hole and don’t know how to get out.”

I felt sorry for the man—I’m naturally empathetic—so I hopped into the hole.  “Why did you do that?  Now we’re both stuck.”

“I’ve been down here before” I said, “And I know the way out.”

I know that’s a little sappy and self-serving.  However, before you decide it’s more comfortable to stay in the hole and hope nobody notices, why not see if there’s someone who knows the way out?

Merely appointing someone to run your EHR effort doesn’t do anything other than add a name to an org chart.

EHR: Every time you redesign, God kills a kitten

Again on the project failure?  Yes.  Why?  Trying to head it off at the pass.  Source, The Bull Report.

Fifty-seven percent of failures are due to bad communication.  What’s that?  Poor grammar?  No.  Not enough meetings?  Doubtful.

It’s about PMO.  A hired gun?  Perhaps.  An advocate who will manage the vendor on your behalf.  What’s the rest of the hired gun’s job description?  It is all the blue stuff in the graph.

And now it is time to view this discussion in light of healthcare.  The chances of your ‘two-comma’ project failing are legion.  Why? Nobody has a good history of having done EHR; if they have experience it is likely because their first implementation failed.  EHR is not like implementing ERP.  The is no ROI at the end of the rainbow.  The business driver seems to be Meaningful Use which has caused many hospitals to glide over things like process improvement and change management and breaking down the tribal barriers among organizations.

The good news is that being a bad dresser will not hurt the project.

 

 

The real impact of the EHR resource shortage

(AP) New York.  It is Reservoir Dogs 2.0 only this time the terrorists appear to be a clean-shaven group of EPCI subject matter experts. Reuters is reporting that early this morning the group of EPIC consultants, each one armed to the teeth with iPads and wireless mice and Blackberrys was last seen forcing a rag-tag group of hospitalists and CIOs into a windowless, upper floor room of the convention center.  It is rumored that a senior analyst from McKesson was also a member of the terrorist group, albeit in a non-billable role.

CMS has long been suggesting that with the huge shortage of skilled EHR specialists that sooner or later those with the knowledge would rise up and hold the providers hostage.

A spokesperson for the terrorists with a background in CPOE released a list of their demands.  They demand to have their rates tripled, to have an organic smoothie machine placed in the hospital cafeteria, and the right to remain employed even though the EHR will drop productivity by thirty percent.

One terrorist who demanded anonymity stated “I do not know why everyone looks so surprised that their EHR software does not work.  Nobody asked if it would work, they just wanted us to install it.”

EHR: What are your Bona Fides?

The photo comes from my Robert Redford look alike period.

Do you ever awaken wishing you were all you used to think you were before you figured out you weren’t?  Me either.  I’m someone who has these kind of days when it’s best to keep me away from shiny objects.

During college, I spent several summers volunteering for a group called Young Life at their camps throughout the US.  Silver Cliff was one of their camps in the mountains of Colorado.  Each week we’d take in a few hundred high school kids from throughout the US, and give them the opportunity to do things and challenge themselves in new ways; everything from riding horses to rappelling.

The prior summer I was the head wrangler at one of their camps—I had never ridden a horse prior to being placed in charge of the riding program.  This summer is was the person running the rappelling program.  Needless to say, I had never done that before either.

We received a day’s worth of instruction before we were turned loose on the kids.  One of the first things we had to learn was that the ropes and harness, if properly secured to the carabineers and figure eight, would actually keep you from falling to your death.  The first test was jumping from a platform way up in a tree while on belay.  After a few moments of white-knuckle panic, I stepped over the edge and was belayed safely to the ground.

From there, we scouted a place for the rappel, and found two suitable cliffs, each with about a hundred foot vertical drop.  Watching my first rappel must have reminded others of what it would have been like watching a chimp learn how to use tools for the first time.  After several tentative descents, I was able to make it safely to the bottom in a single jump.

Each day we’d run a few dozen kids through the course, ninety-nine percent of whom had never rappelled, or ever wanted to rappel.  To convince them that it was safe and that they could complete it, I would instruct them in the technique as I hung backwards over the chalk face of the limestone cliff.

Each day we’d have one or two kids who wanted nothing to do with my little course.  Occasionally, while on belay, one of them would freeze half way down the cliff, and I’d have to belay down and rescue them.

Once or twice I’d have an attractive female counselor on belay, her knowing that I was the only thing keeping her from being a Rorschach stain on the rocks below.  Scared, and looking for a boost of confidence, “She’d ask, how long have you been doing this?” I’d look at my watch and ask her how many days ago was Sunday.  I viewed it as an opportunity to have a little fun with her—sort of like turning to your friend in the checkout line in 7-eleven and saying loud enough for others to hear, “I thought we agreed we weren’t going to use our guns.” I also hoped maybe even having to go on a heroic rescue.

How long have you been doing this?  That’s seems like a fair question to ask of anyone in a clinical situation.  It’s more easily answered when you are in someone’s office and are facing multiple framed and matted attestations of their skills.  Seen any good EHR or HIT certificates on the walls of the people entrusted with the execution of the EHR endowment?  Me either.  I have a cardiologist and he has all sorts of paper hanging from his wall.  Helps to convince me he knows his stuff.  Now, if I were to pretend to be a cardiologist—I’ve been thinking of going to night school—I’d expect people would expect to see my bona fides.

Shouldn’t the same logic apply to spending millions of EHR dollars?  Imagine this discussion.

“What do you do?”

“I’m buying something for the hospital I’ve never bought.”

“Why?”

“The feds say we’ve got to have it.”

“Oh.  What’s it do?”

“Nobody really knows.”

“How long have you been doing this?”

“How many days ago was Sunday?”

“What’s it cost?”

“Somewhere between this much,” he stretches out his arms, “And this much,” stretching them further.

“Do the doctors want this?”

“Some do.  A lot don’t.”

“How will you know when you’re done if you got it right?”

“Beats me.”

“Sounds like fun,” she said, trying to fetter a laugh.

Sounds like fun to me too.

EHR: the Prefect Problem

A perfect problem, in its existing state, is unsolvable.  The way most of us handle it is to click our heels together three times and hope it goes away.  We tend to work on imperfect problems, those that can be solved.

One of my college professors—way back when we still had inkwells on our desks—told me that if you cannot solve the problem the way it is stated, it is to your advantage to restate the problem.  I tried this on a final exam; the problem as it was stated was to contrast two philosophers, one of whom, having not read the book, I had no idea who he was. I restated the problem to contrast two philosophers I knew.  He wrote back on my exam saying I had made a nice effort at using the technique but that the philosopher I chose was the wrong one.

What is the difference between the two problem types?  The first step is the ability to understand what makes the perfect problem uniquely unfixable.  Perhaps a few examples would help.

  • The CEO imposed a deadline for the implementation of EHR.
  • CMS Meaningful Use rules do not fit with our operational strategy.
  • If we do not implement EHR by this date, we do not get the money.
  • We must meet Meaningful Use
  • We do not have enough resources from the EHR users to understand their processes.
  • We cannot continue to support these low-margin services
  • We do not have enough time to define our requirements
  • We cannot afford to spend the time required to assess our processes before we bring in the EHR vendor.

What can be done?  The easy answer is to plan for failure and do your best to minimize it.

What is another way to describe the above examples?  They are constraints.  They can all be rewritten using the word “can’t”.  Rewritten, we might say, “We had a chance to succeed, but because of X, Y, and Z we can’t.”  If that assessment is correct, you will fail, or at least under-deliver at a level that will be remembered for years to come.  That’s a legacy none of us wants.

There are a few solutions to this scenario.  You can eliminate the seemingly intractable constraints; the organization can determine to re-implement EHR and hope for different results; or they can simply find someone else to solve the perfect problem.

Experience teaches good leaders really want reasoned advice.  They want the members of the C-suite to tell them what must be done to be successful.  Good leaders do not accept “can’t”—not on the receiving end, not on the delivering end.

Some will argue, “This is the way our organization works.”  Even if that is true one must consider what is needed to make an exception to the constraint.  Would you accept this logic from a subordinate?  Of course not.  You’d demand a viable solution.  If you are being constrained in your efforts to solve a perfect problem, perhaps it is time to restate the constraints.

Maybe the solution to the perfect problem is to restate it in a manner that makes it imperfect—solvable.

 

Shift Happens: A little IT knowledge can kill you

It almost killed me.  Curious?  I lived in Colorado for a dozen years, and spent almost every other weekend in the mountains, fly-fishing, skiing, climbing, and painting—any excuse would do.  Colorado has 54 peaks above fourteen thousand feet.  In my twelve years I climbed most of them.  Some solo; some with friends.

I owned almost everything North Face made, including a down sleeping bag with thermal protection which would have made me sweat on the moon and a one-burner propane stove which cranked out enough BTUs to smelt aluminum.  Two of my friends and I felt we needed a bigger challenge than what Colorado’s peaks offered.

The dot in the photo is me.

We decided on a pair of volcanoes in Mexico, Pico de Orizaba and Popocatépetl—both over 18,000’.  We trained hard because we knew that people who didn’t train died.  We trained with ropes, ice axes, carabineers, and crampons.  One day in early May we arrived at the base of Pico de Orizaba.  The man who drove us to the mountain made us sign the log book, that way they’d know who they were burying.  After a six hour ride from a town with less people than you’d find inside a rural K-Mart, we were deposited at a windowless cinder-block hut—four walls, tin roof, dirt floor.  Base camp.

Before the sun rose we were hiking up ankle-deep volcanic ash; gritty, coarse, black sand.  The sand soon turned in to thigh-deep snow.  We took turns breaking trail, stopping only long enough to refill our water bottles by hand-pumping glacier melt from the runoff in the bottom of cobalt blue ice caverns carved from solid glacier.

Ice Cave we used to collect drinking water

Throughout the trek we passed crude wooden crosses stuck into the ash and snow, serving as grim reminders of those who’d gone before us.

We knew the signs of pulmonary edema, but were reluctant to acknowledge them when we first saw it.  It was about one the following morning when we decided to make camp.  My roommate was having trouble concentrating, and his speech was slightly slurred.  When we asked him if he was ill, he responded much like one would expect an alcoholic would respond when asked if he was okay to drive.  “I’m fine.”

We were at 16,000’, the wind chill had the temperature slightly warmer than a Siberian winter, and the snow made for a whiteout.  The slope seemed to be at about forty-five degrees.  The sheet of ice upon which we stood was slicker than a car salesman selling Corvairs out of his basement.  I removed my tent pole from my pack and placed it on the ice—we were going to camp for the night.  We watched in intellectual confusion as the tent pole gained speed quickly and hurtled down the side of the volcano, quickly lost in the darkness.

Realizing my friend wasn’t doing well, and that I was now feeling somewhat punkish, we made the difficult decision to turn back.  The only survival for edema is to lose enough altitude until you reach one where there is enough air pressure to force the oxygen into the blood.  Eighteen hours of climbing.  Pitch black.  We headed down, me carrying my pack and his, he with our friend.

We arrived at the block hut around four that morning.  By then I was no longer making any sense.  My roommate had recovered, but I had become somewhat delirious—at least that’s what they told me later.  Not knowing right from left or wrong, I was determined to keep walking.  The two of them took turns laying on me to prevent me from sneaking out during the night.

A little knowledge almost killed us.  The scary thing is that we knew what we were doing.  We had trained at altitude, had a plan, worked the plan.  The plan shifted.  Sometimes shift happens.

It happens more with IT.  Much more.  Do you know what the chances are of any IT project ‘working’ that costs more than$7-10 million?  (Working is defined as having a positive ROI, a project that was delivered on time, withing the budget, and delivered the expected results.) (IT includes workflows, change management, training, etc.)  Two in ten.  Twenty percent.  That’s below the Mendosa Line—non baseball fans may have to look up that one.  Remember the last industry conference you attended?  Was it about EHR?  Pretty scary knowing most of them were planning for a failure.

Put your best efforts, your brightest people on planning the EHR.  Make them plan it, then make them plan it again, and then make them defend it, every piece of it.  If they don’t convince you they can do it in their sleep, you had better redo it.  Do they know what they’re planning to do?  Do they know why they’re planning to do it that way?  If they haven’t done it before, this may not be the best time for them to practice.  EHR is not a good project for stretching someone’s capabilities.

Planning is difficult to defend twice during the life of a large program.  First, at the beginning of the program when the C-Suite is in a hurry to see people doing things and signing contracts.  The second time planning is difficult to defend is the moment the C-I-Told-You-Sos are calling for your head for having such an inadequate plan.

How would I approach planning an EHR program for a hospital?  If we started in September, my goal would be to;

  • Have a dedicated and qualified PMO in place in four weeks
  • Begin defining workflows and requirements by October (I’m curious.  For those who have done or are doing this piece, how many FTE’s participated?  I ask because i think chances are good that your number is far fewer than I think would be needed.)
  • Issue a requirements document by mid-January.
  • Be able to recommend a vendor by the end of March.

That seems like a lot of time.  There are plenty who will tell you they can do ‘it’ quicker.  Good for them.  The best factor in your favor right now is time.

Reread this in a year and see where you are…

…See, I told you so.  Anyone want to go hiking?

Who lost the ‘R’ in EHR’s ROI?

This is my latest post in healthsystemcio.com.

http://healthsystemcio.com/2011/07/14/standardization-lies-beyond-the-clinical-realm/#

As a parent I’ve learned there are two types of tasks–those my children won’t do the first time I ask them, and those they won’t do no matter how many times I ask them.  Here’s the segue.

Let’s agree for the moment that workflows can be parsed into two groups—Easily Repeatable Processes (ERPs) and Barely Repeatable Processes (BRPs). (I read about this concept online via Sigurd Rinde.)

An example of an ERP industry is manufacturing. Healthcare, in many respects, is a BRP industry. BRPs are characterized by collaborative events, exception handling, ad-hoc activities, extensive loss of information, little knowledge acquired and reused, and untrustworthy processes. They involve unplanned events, knowledge work, and creative work—artistes.

Then there are the ERPs.  Remember The Flintstones and I Love Lucy?  Fred Flintstone was looking at a job advert for someone to put cotton in pill bottles; and Lucy got a job boxing bon bons.  ERPs are the easy business process to map, model, and structure. They are the perfect processes for large enterprise software vendors to automate.

EHRs contain both types of business processes, BRPs and ERPs.

How can you tell what type of business processes you are trying to incorporate in your EHR? Here’s one way. If the person standing next to you at Starbucks could watch you work and accurately describe the process, it’s probably an ERP.

So, why discuss ERP and BRP in the same sentence with EHR?  The reason is simple. The taxonomy of most, if not all EHR systems, is that EHRs are designed to support ERPs. Unfortunately, most of the business processes that the EHR has to model are one-off processes, BRPs.  Healthcare providers are faced with the quintessential square peg in a round hole conundrum; trying to fit BRPs into an ERP system.

Since much of the ROI in the EHR comes from being able to redesign the workflows, it stands to reason that the ‘R’ in ROI will be sacrificed, and the ‘I’ will be much higher than planned.

On the other hand, if one looks at a hospital’s non-clinical business processes almost all of those are ERPs.  Many of them are some combination of being outdated, duplicated, and rework.  If you are looking to recover your ROI and to decrease cost, these ERPs offer a good opportunity to do both.

What do you think?

 

EHR: Going the Last Mile

Summer vacations via car.  Makes me wonder what ever happened to station wagons—anyone who does not remember Richard Nixon may want to use Google to the term ‘station wagon’.  We had a sky blue Ford; others had the one with the faux wood-grain side panels like the one Chevy Chase drove in the movie Vacation.

I noticed last week as we drove from Pennsylvania and crossed into Maryland how the blacktop improved and that the shoulder plantings were more numerous and spiffier as though Maryland was showing off, to make you feel you are entering a better place and leaving a worse one. On the return trip the same scenario was reversed as the road for the first mile back into Pennsylvania was much nicer than was the last mile of road in Maryland.

It makes me wonder why states do not put the same level of effort into the last mile instead to make you miss the place you were leaving.

Now let us think about your healthcare IT vendors.  Remember those guys?  The ones who when they courted you took you to dinners and baseball games and golfing.  You probably have one of their coffee mugs on your desk and a few dozen of their Rollerball pens and a commemorative golf towel clipped to you golf bag.  At the get-go everything was first class.  The vendor hoard was attentive and still picking up the lunch tab.

Then they left; all of them.  You surmised the project must be over.  The vendor’s project manager no longer had you on his speed-dial—your number had been replaced with the number of his new golfing buddy, the CIO at Our Lady of Perpetual Implementations.

It makes me wonder why vendors do not put the same level of effort into the last mile of their implementation as they did the first mile.  If they did maybe your perception of them would be better.  Maybe the implementation would have gone better.

HIT: Your most solvable big problem

Two incompatible things are a type A personality and heart disease—I speak from experience.  I usually run six miles a day, three miles out and three miles back.  A few weeks ago I started hitting a wall after two to three miles and found myself having to jog/walk back to the car.  Wednesday I hit the wall after a mile, hands on my knees and gasping for air.

The air thing bothered me because that is what happened during my heart attack in 2002.  As I tried to make it back to my car I had to stop every few steps to catch my breath.  As I made it to a field and lay down several people stopped to ask if I needed help—this is where the incompatibility I mentioned comes into play.

I did not want to impose.  One of those who stopped happened to be a cardiology nurse and she was not taking no for an answer.  Dialing 911 she stated “I have an older gentleman, 60-65 having trouble breathing.”  That got my attention—all of a sudden my age seemed to be a much more important consideration to me than whether or not I could breathe.  “I am 55,” I corrected her.

Knowing how close I was to my home I tried unsuccessfully to get the EMTs to stop by my house before going to the hospital so I could get my laptop.  After three hours of tests, and without concluding why I had trouble breathing, they ruled out anything to do with my heart and sent me home.

I think knowing when to ask for help and accepting help relates a lot to healthcare IT; EHR, Meaningful Use, ICD-10.  These are each big, ugly projects.  There are several things that can happen on big, ugly projects, and most of them are bad.  This is especially true when the project involves doing something for the first time and when the cost of the project involves more than one comma.

Now we both know there is nobody with years of experience with Meaningful Use or ICD-10, and there are not many people who have one year’s experience.  So why ask for or accept help?  The truthful answer is because there are some people who know enough to know what to do tomorrow, and from where I sit the toughest part of every project is knowing what to do tomorrow—how to get started, and what to do the next day and the day after that.