Strategy

EHR–where do you place the emphasis?

Posted by

0

You said I stole the money. Sometimes it all depends on what you emphasize. For example, say the sentence aloud to a friend, and each time place the emphasis on a new word. You said I stole the money. You said I stole the money. You said I stole the money. You said I stole the money. You said I stole the money. The meaning changes as you change your emphasis. You said I stole the money? You can even change it so that it reads like a question.

The same is true with providers and the level of success a firm has working with EHR. Where is your emphasis? If you believe there is a correlation between emphasis and spending, I bet we can prove your firm’s is much more closely aligned to technology than it is to process. What does technology address? Let’s list how deploying technology makes your firm better, or does it?  Millions followed by millions more. Redesign the patient portal.  Add EHR. Mine the data—heck, strip mine it. Show me the ROI. Isn’t that a lot of money to spend without a corresponding business justification?

The technology that is tossed at the problem reminds me of the scene from the “Wizard of Oz” when the Wizard instructs Dorothy and the others, “Pay no attention to the man behind the curtain.” When Toto pulls the curtain aside, we see a nibblet—I love that word—of a man standing in front of a technological marvel. What’s he doing? He’s trying to make an impression with smoke and mirrors, and he’s hoping nobody notices that the Great Oz is a phony, that his technology brings nothing to help them complete their mission.

From whose budget do these technology dollars usually come? IT. From the office of the CIO. What did you get for those millions?  Just asking.

Part of the problem with doing something worth doing on the EHR front is that it requires something you can’t touch, there’s no brochure for it, and you can’t plug it in. It’s process. It requires soft skills and the courage to change your firm’s emphasis. They won’t like doing it, but they will love the results.

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

Tidbits

Posted by

1

I rarely write on Sunday, but with my wife and the kids in Miami for the month while I serve as the EHR Czar, I thought I would share a few thoughts with you.

I went to a reception a few nights ago with some healthcare executives in the Philly area.  It was one of those events whereby the caterer thought the chi-chi crowd would do back-flips over canapés of fava beans stuffed with cheese made from the breast milk of yaks.  One of those events where you can’t complain without being as obvious as someone walking the streets of Tehran wearing a Star of David T-shirt.

Sometimes  you get an ah-ha about life which is so profound it must be shared with friends.  I got one of those today while making a breakfast of smoked salmon, capers, and New York bagels.  I retrieved a clean plate from the dishwasher.  I knew when I finished breakfast I would have to empty the dishwasher–a task that always irks me.  The lights brightened, the sky opened, and I learned something most consultants would try to kiss their elbows to understand.

We have two dishwashers–machines, not people.  Naturally, that cuts down on the number of times we have to empty the dishwasher.  Mind you, my discovery only works for people whose spouse is out T town and for homes who have two dishwashers.  Here’s the deal.  Wash the dishes in one dishwasher.  Sooner or later you get hungry.  You think about going to the cabinet to grab a plate and the it occurs to you that you already have a clean plate in the dishwasher; along with a drinking glass, and utensils.  Why not use them?  And after dining–and this is the revelation–place the newly soiled dishes in the other dishwasher.  Guys, this re-engineering of the traditional kitchen processes eliminates the need to ever empty the dishwasher.  Everything in the dishwasher is caught in an infinite loop, eliminating the need for kitchen cabinets.

This new process brought to mind an episode of ‘Happy Days’ when The Fonz explains to Ritchie how bachelors make a salad to conserve wasting time on extraneous business processes.  The Fonz told Ritchie to hold the head of lettuce above the sink and pour salad dressing on the lettuce, thereby eliminating the need for a plate.

Where were we?  That is unplanned an alliteration.  Given that, how do I make this worth your time?

Permit me to address the C-suite.  Does it seem to you that those people in your firm are paid for working hard, or for delivering results?  I think they are paid for working hard, for looking like they are working hard, for doing the things people in their esteemed position ought to be doing.

They are busy.  Why?  Because those who are not perceived as being busy are fired.

Who at your firm is delivering results?  Who is defining what the results needs to be?

Someone needs to define the ah-ha moments for your organization.  Somebody needs to take charge, to know that it is possible not to unload the dishwasher, to know that there is no value in stuffing the fava beans with the cheese.

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

Where workflow goes to die

Posted by

0

There are two types of business processes; easily repeatable processes (ERP), and Barely repeatable processes.   Most of the real work that needs to be done in EHR workflow improvement happens in the blank white space between the boxes on the org chart.  That’s where you’ll find a lot of the BRPs–Barely Repeatable Processes.

It is easy to automate the ERPs, and nearly impossible to automate the BRPs.  If you can’t reform either set of processes with your EHR all you have implemented is a very expensive chart scanner.

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

EHR’s Gordian Knot

Posted by

0

There were four of us, each wearing dark suits and sunglasses, uniformly walking down the street, pausing at a cross-walk labeled “consultants only”—I think it’s a trick because a lot of drivers seem to speed up when they see us. We looked like a bad outtake from the movie Reservoir Dogs. We look like that a lot.

Why do you consult, some ask? It beats sitting home listening to Michael Bolton or practicing my moves for, So You Think You Can Dance, I tell them.

Listening to the BBC World News on NPR whilst driving, there’s one thing I always come away with—they’re always so…so British. No matter the subject—war or recession—I feel like I should be having a proper pot of tea and little cucumber sandwiches with the crusts removed; no small feat while navigating the road.

Today’s conversation included a little homily about the Gordian knot with which the company Timberland is wrestling, questioning whether as a company Timberland should do well, or do good. (Alexander the Great attempted to untie such a knot, and discovered it had no end (sort of like a Möbius strip, a one-sided piece of paper–pictured above. (For the truly obtuse, among which I count myself, the piece of paper can be given a half twist in two directions; clockwise and counter-clockwise, thereby giving it handedness, making it chiral—when the narrative gets goofy enough, sooner or later the Word dictionary surrenders as it did with chiral.))) I’m done speaking in parentheses.

Should they do well or good? Knowing what little command some people have of the English language, those listeners must have wondered, why ask a redundant question. Why indeed? That’s why I love the English, no matter the circumstances they, they refuse to stoop to speaking American.

Back to Gordo and his knot. That was the point of the knot. One could not have both—sorry for the homonym. Alexander knew that since the knot had no end, the only way to untie it was to cut it. The Gordian knot is often used as a metaphor for an intractable problem, and the solution is called the “Alexandrian solution”.

To the question; Well or good. Good or evil. Are the two choices mutually exclusive? For an EHR? They need not be. The question raised by the BBC was revenue-focused (doing well) versus community or green-focused (doing good). My question to the reader is what happens if we view EHR with this issue as an implication, a la p→q.Let’s review a truth table:

if P equals if Q equals p→q is
define requirements increase revenues TRUE
play vendor darts increase revenues FALSE
ignore change management increase revenues FALSE
no connectivuty increase revenues FALSE
new EHR software increase revenues FALSE
change processes increase revenues TRUE
eliminate waste increase revenues TRUE
decrease redundancy increase revenues TRUE
Strong PMO increase revenues TRUE

From a healthcare provider’s perspective the answers can be surprising; EHR can be well and good, or not well and not good.  The Alexandrian solution for EHR is a Alexandrian PMO.

Have your people call my people–we’ll do lunch.

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 EHR Certification Myth

Posted by

0

EHR certification inspectors will be dropping in on hospitals like UN inspectors looking for WMDs, only they’ll be slightly less congenial–like Kojak without the warmth.

Why is this a part of the overall plan?  Is this planned failure?  Do they have reason to believe that a certain percentage of EHRs will fail the inspection?

Of course they do.

Let’s describe two failure types; certification and Full test.  The certification test, by definition, is necessary.  The Full test is both necessary and sufficient.  It is possible to pass certification without passing the Full test.  Therefore, the Full test is a stricter test.  Build out to pass the Full test, and by default, one should pass the Certification test.

What is the full test?  Same as always.  Fully functional, on time, within budget, and user accepted.  Functional, for purposes of this discussion includes updated workflows, change management, and interoperability, and a slew of other deliverables.

Here’s what can be concluded just based on the facts.

Fact:  One-third to two-thirds of EHRs are listed as having failed—this statistic will get smaller over time.

Opinion:  The reason the failure rate will get smaller is that the failure rate will be artificially diluted by a large number of successful small-sized implementations.  Large implementations, those have far-reaching footprints for their outpatient doctors, Rhios, and other interfaces requiring interoperability will continue to fail if their PMO is driving for certification.  (Feel free to add meaningful use to the narrative, it doesn’t change the result.)

Fact:  Most large, complex, expensive IT projects fail—they just do.  This statistic has remained constant for years, and it is higher than the percentage of EHR projects that have failed.  Even a fairly high percentage of those projects which set out to pass the Full test.

Opinion:  Failure rate for large EHR projects—let’s say those above $10,000,000 (if you don’t like that number, pick your own)—as measured by the Full test, will fail at or above the rate for non-EHR IT projects.)

Bleak?  You bet.  Insurmountable?  Doesn’t have to be.

What can you do to improve your chances of success?  Find, hire, invent a killer PMO executive out of whole cloth who knows the EHR Fail Safe Points.  EHR Fail Safe Points?  The points, which if crossed unsuccessfully, place serious doubt about the project’s ability to pass the Full test.  The points which will cause success factors to be redefined, and cause one or more big requirements—time, budget, functionality—to be sacrificed.

This person need not and perhaps should not be the CMIO, the CIO, or an MD.  They need not have a slew of EHR implementation merit badges.  The people who led the Skunk Works had had zero experience managing the types of planes and rockets they built.  They were leaders, they were idea people, they were people who knew how to choose among many alternatives and would not be trapped between two.

The person need not be extremely conversant in the technical or functional intricacies of EMR.  Those skills are needed—in spades—and you need to budget for them.  The person you are looking for must be able to look you in the eye and convince you that they can do this; that they can lead, that these projects are their raison d’etre.  They will ride heard over the requirements, the selection process, the vendors, the users, and the various teams that comprise the PMO.

What do you think?

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 GM were involved in EHR?

Posted by

0

Goodness knows, the whole car thing did not work our too well for them

Do you ever think about the origination of some of your ideas?  For me, the good and the bad just seem to materialize.  Like the time a friend and I were hiking a peak in the Sangre de Cristo range in Colorado.  It had taken the better part of six hours of circuitous climbing to reach the summit.  It was late in the fall, and the temperatures were around freezing.  Roiling storm clouds were racing towards us from the west.

If we returned by the same route we knew we’d be caught up in a storm that we were neither prepared nor dressed to handle.  I spotted our car about six thousand feet below us.  If we headed straight to it, I thought we could cut our descent time by about an hour.  To do this though required that we make our own trail via a hunt and peck route of whatever the terrain permitted.  We dropped the first fifteen hundred feet in a matter of twenty minutes using a glissade.  This technique allows you to moonwalk and slide down a scree field, using your ice ax as a break.

After an hour we reached a point about two thousand feet above our car.  It was sleeting, and the wind was whipping around the face of the mountain.  There in the middle of nowhere stood a sign from the sheriff that read, “Devil’s Gulch, turn back.”  Our choice was to reclimb the mountain or to ignore the sign and press on.  I hate do-overs.  How tough can this be, I goaded him?  Be smart, kick it into high gear, and we’ll be done.

We pressed forward.  Fifteen minutes later, we reached a four hundred foot limestone cliff.  Between us and the next semi-reasonable terrain was a rather deadly looking wall of rock and scrub pine.  My pack made me feel like it was forcing me forward, so I removed it and tossed it over, thinking I’d retrieve it later.  Watching my pack bound from rock to rock for what seemed like more than a minute did nothing for putting me at ease.

We spent more time discussing each step than we spent taking it.  Those four hundred feet took us two hours.  Not my best idea, but it didn’t kill us.

So, during my run today, I had another idea.  This one is about OnStar, the GM tracking system.  I typed in to Google, “How does OnStar Work?”  Lots of hits.  The more I read, the more I began to feel like if one ignored the technology and focused on the concept a real argument could be made for pairing the idea, and a few others, and seeing what type of EHR network might be possible using a similar set of tools.

The OnStar concept is termed telematics, a combination of telecommunications and informatics.  Telematics is the integration of computing, wireless communications, and GPS.  It provides information to a mobile service like a phone, PDA, or laptop.  It is used for sending, receiving, and storing information over very large networks.  So, why is nobody having the conversation that says what if we image a similar network with added security that works from a healthcare provider’s office rather than a car.

OnStar doesn’t need Rhios.  OnStar has a single set of standards.  Now, instead of arguing why something like this can’t work in healthcare, isn’t there argument is seeing if it can?

saintPaul M. Roemer
Chief Imaginist, Healthcare IT Strategy

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

What did you budget for EHR?

Posted by

0

Okay, so today was going to be one of those days when I wasn’t going to allow myself to be stupified–at least no more than was really required.

Then it sneaks up smack dab in the middle of a call, and from what I’ve been able to determine, people find it annoying if you burst out laughing on the call.  (They are not annoyed at all if you simply write about them provided they don’t read it.)

What got me going is this statement, “We’ve budgeted $X for EHR.”

Really?  You did this all by yourself?

The facts as I understood them are as follows:

  • Never bought an EHR
  • Don’t know how big they are, if they are blue or green, come gift-wrapped, or if you need two people to carry it
  • No input from vendors about EHR
  • no discussions with others abot what an EHR system costs

So, with absolutely no information how does one determine how much they need to spend?  This is not like going to the supermarket for a gallon of Soy Milk–not that anyone would want to do that.

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

Is the C-suite fiddling while EHR burns?

Posted by

0

There is an adage in the military—different spanks for different ranks.  If speaks to a double standard, the less egregious their punishment for similar offenses, similar misjudgments.

We see that every day in business, and we see it a lot in healthcare, especially in hospitals.  Physicians are held accountable for medical errors.  Hospitals pay millions for malpractice insurance knowing that mistakes will be made and people will be held accountable for their mistakes.

But what about on the business side?  Who is held accountable for business mistakes?  An acquisition that failed to deliver.  An expensive new service offering that bled the company dry.  A decline in the number of patients. The failure of a major IT initiative to deliver results.

Take EHR.  Some of you are saying, “Yes, please take it.”

  • Around sixty percent of the large EHR projects have failed in one respect or another
  • Most will not receive ARRA incentives
  • A large number of hospitals are on their second implementation of EHR
  • Some have productivity losses of thirty percent

Who is going to be fired for the two hundred dollar misstep?  The board?  Never.  The CEO—no.  The COO or CFO?  Unlikely.  The CIO?  That is the safe bet.

Did the CIO authorize the expenditure?  Nope.  Did the CIO get all the dollars needed to be successful, all the user support?  Unlikely.

In most cases the CIO has all of the responsibility and only some of the authority.  There are a handful of people in each organization tasked with the oversight of the large project.  They are the ones who should be asking the right questions, the ones who should be demanding answers.

A failed project, a failed strategy should not come as a surprise.  The only people who will be wearing EHR 2.0 T-shirts are those who authorized EHR 1.0.  How come these individuals are not accountable?

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

Are hospitals making the the same mistake as BP?

Posted by

0

“The time has come,” the Walrus said, “To talk of many things: Of shoes and ships and sealing-wax, of cabbages and kings—…

A lot of the strategic issues in healthcare are not easily explained.  One issue can be explained to a fifth-grader.  So, get your crayons out and follow along.

Fifty-some days and counting.  Say it with me—BP.  In many respects healthcare’s approach to social media is analogous to BP’s—the major difference is that neither the payors, pharma, nor the providers has yet to wipe out an entire geography—but the week is not over yet.

BP is offering an MBA in how not to use social media.  Nobody is queuing up on Amazon to buy the book, “BP’s ten pointers on crisis management.”

The funny thing about disasters is being able to schedule them in Outlook.  There are no pop-ups fifteen minutes before the big bang reminding you to get ready—“pipeline blows up in 15 minutes.”

We both know, sooner or later you will have one.  While yours may not crater the shrimping industry, it may be enough to do some serious damage to your business.  Most hospitals have a risk management group.  BP has one.  The mission statement of risk management is to assess and mitigate risks.

BP’s group probably had a plan in place to address a number of risks—risks like OPEC, an expansive war in the middle east, a tanker collision.  Apparently, they overlooked the risk of having a blowout a mile under the ocean.  Who’da thunk it?

If you Google “oil spill” there are fifty million hits.  Add “BP” to the search and the results narrow to a mere forty million.  That toothpaste is never going back in the tube.  People who can’t find the Gulf of Mexico on a map know that BP ruined it.  Thirty years from now people will still know the name of the firm that poisoned the Gulf, destroyed businesses, ruined vacations, made people sick, and cratered home sales along hundreds of miles of shoreline.

No matter what type of disaster BP could have faced, they demonstrated they were not prepared.  Even if it is proven that the disaster was not BP’s fault, it is too late to change their ownership of it.  Nobody is ever going to delete those forty million Google pieces linking BP to failure.  If BP hired a thousand workers whose only job was to try to counter each piece of negative media it would take them decades.

What is the one word to describe BP’s social media strategy?  LATE.

There is no useful social media strategy worth anything that begins after a disaster, none worth anything that begins after a misstep, after a faux pas.  Dictionary.com defines a faux pas as a social error—a boo-boo.

Unlike Meaningful Use, a good social media strategy can have an almost infinite ROI.  A good social media strategy, in addition to adding revenues and capturing patients, can help assuage the bleeding.  A good social media strategy played out in advance creates allies.

Let us look at this from the perspective of large healthcare providers.  What types of unfavorable events could negatively affect a hospital?

  • A medical disaster
  • Fraud
  • Medical errors
  • Reform
  • Scandal
  • Medical malpractice
  • Natural disasters
  • A data breech

While all negative events are not the same, many aspects of a good social media strategy apply regardless of the type of problem.

There are two major components of a good healthcare social media strategy:

  1. It should be pro-active.  Your social media strategy should be building goodwill each day.  Google the name of your hospital and see how many hits you get.  Next, see how many thousands of those hits are attributable to people outside your organization—too many to count.  You are already late.  People are already posting videos and writing about you.
  2. It should be reactive.  Make sure your “What are we going to do now?” account has a positive balance.  At the very least make sure you can push a button and unleash a plague of social media “I feel your pain” initiatives.

I’d wager a hospital could develop an outstanding social media strategy for less than one-tenth of what it pays in legal fees.

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

A Perfect Metaphor

Posted by

0

Few things are perfect, and when you find something that is, it is worth examining.  One thing that is perfect is baseball, at least some aspects of it.

Think with me for a minute. 1845.  How much has changed since then?  Just about everything.  Do you know what has not changed—the distance between the bases—90 feet?  This distance may seem insignificant or inconsequential.

In the last 165 years the distance between the bases remained unchanged.  Equipment changed, improved.  The players got bigger, faster, and stronger.  It never dropped to eighty-nine feet; it never jumped to ninety-one feet.

To those who follow baseball, have you noticed how close many of the plays are at first base, or the closeness of the steals of second base?  Can you imagine what would happen to the game of baseball if the distance was shortened to eighty-nine feet?  Almost everyone stealing second base would be safe.  If the distance was ninety-one feet they would all be out.

Somehow, 165 years ago those people got it right, got it absolutely right.  Something as simple as a measurement along a dirt path has stood the test of time.  There are not even any discussions about trying to improve it.

Remember the Titanic?  If one measured all the time spent in its design, and all of the time it sailed before it sank, if you were a betting person you would have bet on the boat.  Reasonable people would have bet on the boat.  You would have been a fool to have bet it would have sunk.

You know what; the Titanic’s sinking was not a fluke. The laws of physics and ship design did not suddenly cease to work.  Do not blame the iceberg.  The Titanic was designed to sink—otherwise it would not have sunk.

What is often misjudged in business is the ill-informed notion that just because something has not collapsed it is not broken.  Hospitals are starting to collapse.  The business model of most of them almost ensures that left unchanged, many, many more will collapse.  They have been designed to collapse.  Just because they have yet to collapse does not mean they won’t, all it means is that they have not—yet.

Few things are perfect.  What discussions there are about the business model are not about improving the model, they are about cutting costs.  What do you have when there are no more costs to cut?  You have a less costly dysfunctional model.

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