Modern Healthcare: Not enough time for PCAST goals?

Below are the comments I submitted to their recent article–http://www.modernhealthcare.com/article/20101222/BLOGS02/312229999&newCommentId=4948192#comments

It is difficult being the lone duck screaming “the sky is falling,” but, I feel someone has to be the schismatist before we all wind up drowning in the Kool-Aid.

It is not that I do not think ideas like a universal exchange language are not important; I think the fact this discussion even exists is because we have kidded ourselves for so long about how well EHR and interoperability are working that we have hung ourselves on our own petard.

Have we put the cart so far ahead of the horse that we have caught the horse from behind?  The discussion seems to be about walking before most have learned to crawl.  Lest we forget the issues, here are some observations we must keep at the forefront—what most hospital executives and CIOs face daily.

  • EHRs are not standard
  • Many EHR implementations have failed
  • More will fail Meaningful Use
  • Some hospitals are on EHR 2.0, switching from Vendor A to Vendor B, while others are switching from Vendor B to Vendor A—what does that tell us?
  • The current hospital business model is dysfunctional; as compared to other industries, hospitals are run more like a 0.2 model than a 2.0 model
  • EHRs were built to support a dysfunctional model, and those EHRs are built using outdated architectures
  • An ACO business model is not compatible with the present crop of EHRs—EHRs were not built with ACOs in mind—they are mutually exclusive concepts, at least with regard to today’s EHRs
  • For and ACO to be of value, to be effective to an organization, they must be joined to a different business model

Before we worry ourselves with future issues like compatibility with the EU and a universal exchange language, ought we not come up with a plan to make EHR viable one hospital at a time?

 

Hospital CIOs: Something to think about

My new post in healthsystemCIO.com CIOs Must Paint a Real EMR/ACO Picture…http://ow.ly/3w7Al

Patient Experience Management-there are some easy answers

There’s a reason penguins don’t play the viola—maybe that’s why they don’t have a home page. I used to try to approach things with an open mind, but people kept trying to put things like that in it. Did you ever notice that it’s difficult to encourage people to think outside the box especially if you haven’t seen evidence that the people inside the box are thinking? I’m sure there are those who think these ideas are mere snake oil, but who among you has ever seen a rusty snake?

There is often an inverse relation between the relevance of a document and its brevity. Roemer’s Law 17: the value of a patient user manual used in your call centers is approximately equal to the square root of the number of chapters. (That bit of insight is the equivalent of 4.6 raiments, where one raiment has been universally established as the amount of consulting insight needed to awe a frog for one hour.)

How many different patient user manuals are there in your patient call center? How many pages do those manuals occupy? I think user manuals are so long because call center managers believe busy people are effective people. People who aren’t busy all the time might start to think, and what good has ever come from that?

The United States Constitution is about 9,000 words—that’s about thirty pages. What is it about the interactions between patients and call center reps that requires more verbiage than the amount needed to keep 350,000,000 people living in prosperity and at peace with one another for more than 220 years?

For some people, work takes place in the fast lane. For me, it often takes place in oncoming traffic. To conclude, let’s agree to quit viewing things from the dark side of the sun. Sometimes instead of complaining about the darkness, it’s better to ignite a flame. The next time you are at your desk, open the user manuals, take out all the pages, and replace them with this one rule:

DO WHATEVER IT TAKES TO SOLVE THE PATIENT’S PROBLEM.

I guarantee that will improve performance. Some executives argue that the chances of something so patently absurd actually being true are a million to one. But consultants have calculated that million-to-one chances crop up nine times out of ten. It’s also fair to state that all mushrooms are edible, however it’s equally fair to state that some mushrooms aren’t edible more than once.

To those who want to prove me wrong, go ahead. Destroy the fabric of the universe, then call me.

 

New thoughts on EHR and ARRA money

So, there I was, laying out my plans for 2011.  I had started training to become the first person to cross the English Channel on horseback, but I was having difficulty finding a company to sponsor me.  Given my reputation as a water-walker, several firms indicated they would sponsor me to walk it, but I have never been one to do things the easy way.

Scratch the horse idea.

Then it hit me.  I’ve decided to retrace the footsteps of the Norwegian explorer Thor Heyerdahl in his quest to travel from Peru to Pacific Polynesia on a raft made from natural materials.  His book Kon-Tiki narrates his 101 day journey.

But since balsa wood is scarce, I will need some other readily available material I can lash together to build my vessel.  (Have you figured out where this is headed?)

With so many broken EHRs littering the dustbins, I figured why not?  I bought them for pennies on the million and had them shipped to the seaport of Callao.  I hired a few systems integrators to integrate the various platforms; McKesson and EPIC formed the major components of the hull, and several copies of AllScripts served as decking.

Launch is set for April 1 of this year.  My backup plan in case this fails is to use all of the unclaimed ARRA money, convert it into single dollar bills, and lay it on the water in front of me, bill by bill, for 4,000 miles.  I know this is a bit extravagant, but I hate to see all that money go to waste.

 

 

Zen Project Management–Rule 1, don’t steal the plants

(I sometimes find it helpful to recite my blogs using different voices, like Neil Diamond.  You?)

Do you ever look back with amazement on how naïve you were in your first job?  You walk in, your head so full of knowledge it feels like it should explode.  You’re just waiting for that first opportunity to release the pearls of wisdom accumulated during all those years of schooling.  I was pretty sure I knew almost everything that needed knowing.

With my newly minted MBA, I worked as the assistant to the CFO of a large petroleum services firm in Fort Worth, Texas.  Lot’s of visibility, lot’s of people watching my every move.

My first day on the job, I was expected to attend a meeting at 7:30 AM.  Overtime.  I brought donuts, knowing how hungry everyone must be because they hadn’t had time to eat breakfast.  As I soon learned, the others in the room had been there since 6 AM for another meeting—they were not impressed by my offer of donuts.  My boss walked me over to an east-facing window an pointed at the orange ball of light floating above the horizon.

“That’s the sun,” he said.  “It’s been up two hours—so have we.  It comes up this time every morning.  Get used to it.”

That went well.  I noted later that five PM had come and gone and nobody made any attempt to rush the doors.  I decided to leave around seven.  As I waited for the elevator I noticed that two very large plants in very attractive pots were being thrown away.  They’d be perfect for my barren apartment.  It took me several trips to get the plants and pots situated in my TR-7 convertible.  Over the next several days I noticed that next to the elevator bays on the other floors were identical plants in identical pots.  What was the likelihood that these were all being thrown away?  Probably zero I surmised–if you steal something without knowing you were stealing, is it really stealing (think Limewire)?

So, my first day on the job I unknowingly stole the company’s plants.  What would day two offer, a walnut credenza, brass lamps?  Gonna’ need a bigger car.

Do you know people like that on your project, those who portend to know everything that don’t?  Plant thieves.  Sometimes they masquerade as program managers, sometimes as vendors.  They hide what they don’t know behind a flurry of meetings, a full calendar, reams of emails.

It’s easier to spot the plant thieves than it is to stop them from adversely affecting your project.  It’s easy to observe, easier to complain about.  What to do about it?  Why are you asking me?  That’s why they pay you the big bucks.

 

Patient Relationship Management-Master of the Jedi Order

They don’t call me Yoda for nothing. This little rant is for those acolytes drinking the Kool Aid of disbelief, the recipe that says one day, if we stay the course, this will all get better.  These are those who believe the light at the end of the tunnel isn’t a train.
For the next few minutes try and disassociate yourself from your responsibilities at work and become a patient.  Recall a time when you’ve been a dissatisfied patient and afterward felt the need to interact with your provider. If you’re totally honest, the forthcoming interaction should quicken your pulse. Cold beads of sweat appear on your forehead, your palms feel a little clammy, and you feel an unexplained need to microwave your neighbor’s cat.

The transition is faster than Clark Kent in a phone booth. A mild mannered and pedestrian acolyte transformed into a right-winged, Myers-Briggs INTJ A-Type with a passion for metaphorically devouring the unfortunate person awaiting your phone call.

As you think about managing the equity of your patients think about it from the perspective of the patient, goodness knows they do. That relationship is black and white—there are no shades of gray. It’s good versus evil, Yoda versus Darth Vader.

Patients Experience Management versus Patient Experience Management.  See that little ‘s’ tacked on to the word patient?  One letter makes a world of difference.  Patients do experience the decisions of your hospital’s management, and oftentimes that experience is unpleasant.  That experience can involve a broad range of issues–billing, insurance, dispute management, scheduling, prescriptions.

I think with most patient interactions the patients believe that the person on the other end of the line (think hospital customer service person) is incented to make them go away as quickly as possible and at the lowest possible expense to the provider.

For most patients, patient loyalty is a thing of the past.

With whom do you do business? Why? For any product that is even close to being a commodity, I deal with the firm who I find to be the least offensive, the one that will irritate me the least. That’s why I buy cars on eBay so I never again have to hear the phrase, “What’s it going to take to get you into that car?” If you find yourself doing that, why is it such a stretch to believe so many patients feel the same way? That said, could it be rather naïve to believe your hospital’s current approach to patient relationship management will make any difference?

Patients Experience Management-why not think like one?

I met last week with a number of 1st Year MBA students who have a consulting club to help them figure out if they are suited for this noblest of all professions–supposedly the second oldest profession. “How can you tell if you’ll be any good at it?” They asked.

As far as I can tell, there are two basic requirements. One, you have to be a bit out of kilter, a strong dose of ADHD doesn’t hurt either. You have to hate repetition.   Second, it helps if you have a belief that there is almost nothing you couldn’t figure out how to improve. While thinking it doesn’t make it true, the attitude is a critical success factor.  It will also require being rather thick-skinned as some clients will require you to yell “unclean, unclean” as you walk their halls.

For example, last week I was at the post office.  Noon on the Wednesday before the holiday–lunch time rush hour.  I’m standing in a long line underneath a banner with a message emphasizing quality.

There are two clerks, postmen, postpersons, postladies–I’m not sure which one is most appropriate, but as we both know, I’m not going to lose any sleep over it either. The line is out the door. Clerk ‘A’ tells clerk ‘B’, “I’m going on break.” At which point I turned to the person next to me and uttered, “And I’m going to UPS.”   It’s not that difficult to improve.  Not letting half of your customer-facing employees go on break during your busiest time would be a good way to start to improve things.

It’s not rocket surgery. The title of the piece is not a typo.  Patients really do experience management, at least they experience many of their ill-conceived processes and rules.  Patient Experience Management, Patient Equity Management. Whatever you call it, big inroads can be made.  Quit thinking like an executive and start thinking like a patient and you’ll have plenty of ideas.

 

Today is not a dress rehearsal, or is it?

Or is it? Who makes that determination? This is probably the one area of your job over which you still have the most control.

CIO shift, happens–or shift happens

Another comment of mine to Barbara Quack’s post; http://ducknetweb.blogspot.com/2010/12/cio-confidence-in-meaningful-use-drops.html#comment-form

I think you hit the nail on the head.  I think a lot of this can be attributed to the fact that stuff rolls down hill and that shift happens.

In healthcare, as in every significant industry, part of the problem seems to come from the fact that CIOs are often considered to be part of the C-suite in name only.  There are several notable exceptions to this observation, CIOs who drive business strategy instead of merely implementing the business strategy that was developed in the “real” C-suite.  Many C-suiters perceive the real role of the CIO is to apply technology to accomplish what they (the C-suite) want done.

Many executives, CFOs, CMOs, COOs, and CEOs regard the position of CIO such that the “C” (chief) and “O” (officer) are honorariums; officers in name only, officers with commensurately sized offices located on the third floor or in an offsite location.  Responsibility often without authority.

I think the issue of Meaningful Use is a clear example of how the practice works.  I worked with a large group of hospitals whose CIO had a detailed IT strategy and plan—projects, ROIs, resources, and capital.  His plan was tied to the business plan which he helped author.

He did EHR and CPOE before EHR was de rigueur.  Then along came Meaningful Use.  Without any understanding of the business issues or consequences associated with meeting Meaningful Use, the C-er’s and the board decided that not meeting Meaningful Use was not up for discussion.  The analysis was thorough, but unimportant.

In a nutshell, the organization which had already implemented EHR and CPOE because of his thought leadership—and long before DC got into the EHR thought leadership business—was instructed to meet Meaningful Use, all else be damned.  The “all else” included whatever it was that eighty percent of his IT staff would have worked on during the next three years.

For the sake of a check, the IT strategy was sacrificed, and the IT strategy’s alignment to the business strategy was sacrificed.  Did they get the check?  Will they pass the Meaningful Use audit?  IT will be blamed if they fail to meet Meaningful Use.  They will be blamed when they fail to deliver all of the other parts of their original plan.  And, they will be blamed if the standards shift in mid-stream.  Why?  Shift happens.  Responsibility often without authority.

“Memo from the CFO: How’s that whole ICD-10 initiative coming?  Holler if I can do anything.”

And guess what’s coming around the corner?  The new hot topic to roll down hill will be the decision that comes out something like this; “Memo from the CEO: The board decided we need to be seen as an Accountable Care Organization by the end of 2012.  Holler if I can do anything.”

Information Technology—IT.  “That must be where we keep all the technology in case we need it.”  Just send out a request and one of those technology guys will put it in for us.

There is only one thing that will stop this train from making the office of the CIO the bucket into which the downhill water is running.  Lead.  Plan.  Instead of planning for what technology and IT resources you need to deliver to meet their orders, draft a healthcare strategy instead of an IT strategy.  Bring forth a business plan addressing business problems that uses technology as a solution to solve the problems.

Define what is needed, on top of what you already need, to meet ICD-10.

Define what is needed, on top of what you already need, to make ACOs viable.

If you wait to respond to their IT orders, it will be too late.

Healthcare Hero

Hero is such a disposable word.  I thought it might be of interest to share the meaning of the word from the eyes of a ten year old.

Forgive me for stealing a minute of your time for these few paragraphs.  Although I rant about the healthcare system, and independent of whether it needs changing and how to change it, I am quite a fan.

Two years ago my 10-year-old son was given a writing assignment to draft a paragraph about his hero.  He wrote the following about an event that happened when he was 4,  which I subsequently framed and placed on my night stand—the spelling errors help authenticate the narrative:

“An amblence driver is my hero. He saved one of my familys members lives, My Dad. One late night my dad had a hart attack (I had a horrible ear ake.  We called the hospital and an amblence came to take my dad.  The driver took him to the hospital (it takes 30 minutes to get there going 60 miles an hour.)

I love to read and write, and as you know, I can be critical of those who do and don’t, but this is the best piece I’ve ever read.