Healthcare IT Strategy

January 18, 2012

Can you blame providers if they fail Meaningful Use?

I don’t wake up each day planning to be at odds with ninety-eight percent—I’m probably being overly generous assuming two percent of the people are as jaded as me—of the HIT community, maybe I just come by it naturally.

The first time I heard of RECs (regional extension centers) the first thing that came to mind was playgrounds, something akin to what the Police Athletic League might find useful.  Five hundred and ninety-eight million dollars.  They tried 597 and determined it wouldn’t be enough and figured 599 would be too much, but 598 million was just right.  Then Goldilocks made her way over to the porridge—sorry for turning left at the fairy tale ramp.

A large part of the success or failure of reform hinges on the success or failure of EHR.  Accordingly, the government made the egregious decision to manage the process of building and rolling out a national EHR down at the molecular level.  They have involved themselves at the front-end, at the vendor level, and at the back-end.  The more anxious they become, the more money they waste, adding another guise to get the healthcare providers to take their eyes off the ball.  Five hundred ninety-eight million “we’re just here to help you” dollars.

This money could be spent to pay the top EHR vendors to create one set of standards and modify their systems to fit those standards.

Meaningful Use.  Don’t get me started.  How can I fault thee; let me count the ways.  Those tested early for Meaningful Use will be examined less rigorously than those tested later.  This is like the IRS saying that if you file your taxes in February, don’t worry about those silly little math errors.  Healthcare will be the only industry whose software quality assurance check occurs after they pass the fail-safe point, the point of no return.

With good leadership providers should know EHR will pass meaningful use before implementing the system. If they fail to pass Meaningful Use, shame on them.

January 12, 2012

Will National EHR Work?

I’ve never been mistaken as one who is subtle.  Gray is not in my patois.  I am guilty of seeing things as right and left and right and wrong.  Sometimes I stand alone, sometimes with others, but rarely am I undecided, indecisive, or caught straddling the fence.  When I think about the expression, ‘lead, follow, or get out of the way,’ I see three choices, two of which aren’t worth getting me out of bed.

I do it not of arrogance but to stimulate me, to make a point, to force a dialog, or to cause action.  Some prefer dialectic reasoning to try to resolve contradictions, that’s a subtlety I don’t have.  Like the time I left the vacuum in the middle of the living room for two weeks hoping my roommates would get the hint.  That was subtle and a failure.  I hired a housekeeper and billed them for it.

Take healthcare information technology, HIT.  One way or another I have become the polemic poster child of dissent, HIT’s eristical heretic.  I’ve been consulting for quite a while—twenty-five plus years worth of while.  Sometimes I see something that is so different from everything else I’ve seen that it causes me to pause and have a think.  Most times, the ball rattles around in my head like it’s auditioning for River Dance, and when it settles down, the concept which had led to my confusion begins to make sense to me.

This is not most times.  No matter how hard I try, I am not able to convince myself that the national EHR rollout strategy has even the slightest chance of working as designed.  Don’t tell me you haven’t had the same concern—many of you have shared similar thoughts with me.  The question is, what are we going to do about it?

Here’s my take on the matter, no subtlety whatsoever.  Are you familiar with the children’s game Mousetrap?  It’s an overly designed machined designed to perform a simple task.

Were it simply a question of how to view the current national EHR roll out strategy I would label it a Rube Goldberg strategy.  Rube’s the fellow noted for devising complex machines to perform simple tasks.  No matter how I diagram it, the present EHR approach comes out looking like multiple implementations of the same Rube Goldberg strategy.  It is over designed, overly complex.  For it to work the design requires that the national EHR system must complete as many steps as possible, through untold possible permutations, without a single failure.

Have you ever been a part of a successful launch of a national IT system that:

  • required a hundred thousand or so implementations of a parochial system
  • has been designed by 400 vendors
  • has 400 applications based on their own standards
  • has to transport different versions of health records in and out of hundreds of different regional health information networks
  • has to be interoperable
  • may result in someone’s death if it fails

Me either.

Worse yet, for there to be much of a return on investment from the reform effort, the national EHR roll out must work.  If the planning behind the national ERH strategy is indicative of the planning that has gone into reform, we should all have a long think.

I hate when people throw stones without proposing any ideas.  I offer the following—untested and unproven.  Ideas.  Ideas which either are or aren’t worthy of a further look.  I think they may be; you may prove me wrong.

For EHR to interoperate nationally, some things have to be decided.  Somebody has to be the decider.  This feel good, let the market sort this out approach is not working.  As you read these ideas, please focus on the whether the concept could be made to work, and whether doing so would increase the likelihood of a successful national EHR roll out.

  • Government redirects REC funds plus whatever else is needed to quickly mandate, force, cajole, a national set of EHR standards
    • EHR vendors who account for 90%–pick a number of you don’t like mine—use federal funds to adapt their software to the new standard
    • What happens to the other vendors—I have no idea.  Might they go out of business?  Yup.
    • EHR vendors modify their installed base to the standard
  • Some organization or multiple organizations—how many is a tactic so let’s not get caught up in who, how many, or what platform (let’s focus on whether the idea can be tweaked to make sense)—will create, staff, train its employees to roll out an EHR shrink-wrapped SaaS solution for thousands and thousands of small and solo practice
    • What package—needs to be determined
    • What cost—needs to be determined
    • How will specialists and outliers be handled—let’s figure it out
  • Study existing national networks—do not limit to the US—which permit the secure transfer of records up and down a network.  This could include businesses like airline reservations, telecommunications, OnStar, ATM/finance, Amazon, Gmail—feel free to add to the list.  It does no good to reply with why any given network won’t work.  Anyone can come up with reasons why this won’t work or why it will be difficult or costly to build or deploy.  I want to hear from people who are willing to think about how to do it.  The objective of the exercise is to see if something can be cobbled together from an existing network.  Can a national EHR system steal a group of ideas that will allow the secure transport of health records and thereby eliminate all the non-value-added middle steps (HIEs and RHIOs)?  Can a national EHR system piggyback carriage over an existing network?

We have reached the point of lead, follow, or get out of the way, and two of these are no good.

January 6, 2012

The Physics of EHR

To read and complete this post you may use the following tools; graph paper, compass, protractor, slide ruler, a number two pencil, and a bag of Gummy Bears—from which to snack.  The following problem was on the final exam in my eleventh grade physics class.  Let us give this a shot and then see if we can tie it into anything relevant.

A Rhesus monkey is in the branch of a tree thirty-seven feet above the ground.  The monkey weights eight pounds.  You are hunting in Africa, and are three hundred and twenty yards from the monkey.  You have a bolt-action, reverse-bore (spins the shell counter-clockwise as it leaves the gun barrel) Huntington rifle capable of delivering a projectile at 644 feet per second.  The bullet weighs 45 grams.  The humidity is seventy percent, and the temperature in Scotland is twelve degrees Celsius.

At the exact moment the monkey hears the rifle fire it will jump off the branch and begin to fall.  Using this information, exactly where do you have to aim to make sure you hit the monkey?

I used every piece of information available to try to solve this.  I made graphs and ran calculations until there was no more data left to crunch, computing angles and developing new formulas.  I calculated the curvature of the earth, and the effect Pluto’s gravitational pull had on the bullet.

The one thing that never occurred to me was that since the monkey was falling to the ground, so was the bullet—gravity.  The bullet and the monkey both fall at the same rate because gravity acts on both the same way.  So, where to aim to hit the monkey?  Aim at the monkey.

All of the other information was irrelevant, extraneous.  The funny thing about extraneous information is that it causes us to look at it, to focus on it.  We think it must be important, and so we divert attention and resources to it, even when the right answer is staring us in the eye.

Attempting to implement EHR is a lot like hunting monkeys.  We know what we need to do and yet we are distracted by all of this extraneous information that will hamper our chances of being successful with the EHR.  Two of the most obvious distractions are Meaningful Use and Certification.  The overarching goal of EHR is EHR; one that does what you need it to do.  If the EHR does not do that, everything else has no meaning.

January 4, 2012

EHR: How is your EHR vendor performing?

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

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

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

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

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

The brother thought about it and apologized.

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

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

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

January 3, 2012

Who was the person who put in your first EHR system?

Filed under: Rants & Musings — Paul Roemer @ 2:16 pm

The first home I bought was in Denver.  Built in 1898, it lacked so many amenities that it seemed better suited as a log cabin.  There was not a single closet, perhaps because that was a time when Americans were more focused on hunting than gathering.  Compared to today’s McMansions, it was doll-house sized.

It needed work—things like electricity, water—did I mention closets?  I stripped seven coats of paint from the stairs.  Hand-built a fireplace mantle and a deck.  One day I arrived home only to find my dog had eaten through the lath and plaster wall of the space which served as my foyer/family room/ living room-cum-hallway.  I discovered the plaster and lathe hid a fabulous brick wall.

My choice was to patch the small hole, or remove the rest of the plaster.  I knew nothing of patching holes, but felt pretty confident about my demolition skills.  Within an hour I had purchased man-tools; two mauls, chisels, and a sledge hammer.  I worked through dinner and through the night.  The only scary moment came as the steel chisel I was using connected to the wiring of two sconces which were embedded in the plaster.  On cold nights I can still feel the tingling in my left shoulder.

As the first rays of dawn carved their way through the frosted beveled glass of the front door, I wondered why I never before had noticed that the glass was frosted.  I wiped two fingers along the frost.  A fine coating of white powder came off the glass leaving two parallel tracks resembling a cross-country ski trail.  I surveyed the room only to see that the air made it look like I was standing inside of a cloud.  The fine white powder was everywhere, covering my Salvation Army sofa, a semi-matching machine-loomed Oriental rug from the Far East (of Nebraska), a two-ton Sony television, and a component stereo system that had consumed most of my earnings.

Bachelor living can be entertaining.  One of my climbing buddies moved in with me.  The idea was I’d keep the rent low, and he’d help me by maintaining the house.  He didn’t help.  I made a list of duties; he didn’t help.  I left the vacuum in the middle of the floor, for two weeks and he walked around it.  I made him move out, and advertised for a female roommate—an idea I now wish I’d marketed.  A girl from church came over to see the place.  I turned my back on her to allow her to view the house with a degree of privacy.  When I returned I found her on her hands and knees cleaning the bathroom.  I was in love.  It was like having a big sister and mother.  She even asked if it was okay if since she was doing her laundry if she did mine at the same time.  Life was oh so good.

Sometimes when one approach isn’t working it’s real easy to try something else.  And sometimes the something else gives you a solution in the form of a water-walker.  Healthcare IT and EHR aren’t ever going to be one of those sometimes.  There will be no water-walkers, no easy do-overs.  There won’t be anyone walking your hallways talking about their first wildly unsuccessful EHR implementation.  Nobody gets to wear an EHR 2.0 team hat.  Those who fail will become the detritus of holiday party conversations.  Who will be the topic of future holiday parties?  I’m just guessing, but I’m betting it will be those who failed to develop a viable Healthcare IT plan, whoever selected the EHR without developing an RFP, the persons who decided Patient Experience Management (PEM) was a waste of money.  The good news is that with all of those people leaving your organization there will be more shrimp for everyone else to eat.

I’d better go.  I just noticed somebody left the vacuum in the middle of the floor so I need to get cracking before my wife advertises for a female roommate.

December 28, 2011

Your EHR Works As Designed, And That’s The Problem

Filed under: EHR,EMR,Hospital,informatics,innovation,productivity,Rants & Musings,Strategy — Paul Roemer @ 9:23 am

This is my newest contribution to HealthsystemCIO.com.

What could we have done differently, is the question I hear from many of the healthcare executives with whom I speak about the productivity loss resulting from their EHR.

My answer, nothing. I am willing to bet that in most cases your EHR was implemented correctly. I am just as willing to bet that the training was executed well. “If we did everything correctly, then why is the EHR performing so poorly?”

Fair question. The EHR is not performing poorly. It is performing exactly as it was written to perform. If that is true, why is there such a dichotomy between how it is working and how we need it to work? That is the perfect question to be asking. Here is why. If you interviewed your EHR vendor and asked them to tell you how the system is supposed to work when a nurse or doctor is with a patient they will tell you something like this:

We wrote the system to mimic what doctors and nurses need to do during an examination. Start with getting a history of the present illness (HPI). Then get vital signs, list of allergies, significant events, medical history, current meds, and lab and test results. Then write any prescriptions, order tests, and end the visit.

Very neat, very orderly. Linear. Move from Task 1, to Task 2. Just the way the EHR was written, just the way doctors were trained to conduct an exam.

Unfortunately, most exams do not follow that flow. Why? Patients. Somebody forgot to tell the patients and the clinicians that, in order for the EHR to work in anything that could be construed to be an effective and efficient manner, the exam must be conducted according to the EHR’s script. In order to minimize the number of screen navigations and clicks, you must complete all of Task 1 before moving on to Task 2. Linear. Front to back.

Exams are not linear. Patients generally dictate much of the order of an exam. They move indiscriminately and randomly from one task to the other. This randomness causes the clinician to hop about the screens in the EHR in an ad-hoc manner. Data entry and screen navigation are neither orderly nor complete. Nor are they front to back. The patient may start the exam with a question about lab result or about a side-effect of a medication.

All of this jumping around adds time, more time than what was allotted for the exam. Imagine that on your desktop you have several programs running; PowerPoint, Word, Excel, and email. Instead of completing what you hoped to accomplish in one program, closing it, and moving on to your next task, you were forced after each minute to stop what you were doing in one program and go work on something different in the next program.

Is there anyone who doubts that it would have taken less time to complete all your tasks if you were allowed to complete one before starting the other?

You EHR was not designed to work efficiently in an non-linear exam. Chances are good that your EHR was never really designed at all. Were designers, professionals with advanced degrees in human factors — cognitive psychology, heuristics, taxonomy, and anthropology — asked to determine how the EHR would need to work? Did they watch users work prior to writing code? Did the EHR firm iteratively build prototypes and then measure how users used it in a research lab that tracked hand and eye movements? If not, that is why I think it is fair to characterize EHRs as having been built, not designed.

The good news is that even at this point, even as you continue to watch productivity drop, you can choose to bring design in to solve the problem. Retraining will not solve the problem. After all, it was trained users who helped bring about the productivity loss.

December 21, 2011

EHR: How Important is Due Diligence?

What was your first car?  Mine was a 60’ something Corvair–$300.  Four doors, black vinyl bench seating that required hours of hand-stitching to hide the slash marks made by the serial killer who was the prior owner, an AM and a radio, push-button transmission located on the dash.  Maroon-ish.  Fifty miles to the quart of oil—I carried a case of oil in the trunk.  One bonus feature was the smoke screen it provided to help me elude potential terrorists.

I am far from mechanically inclined.  In high school I failed the ASVAB, Armed Services Vocational Aptitude Battery—the put the round peg in the round hole test.  Just to understand how un-complex the Corvair was, I, who hardly knows how to work the radio in a new car, rebuilt the Corvair’s alternator—must not have had many working parts.  Due the the excessive amount of rusting I could see the street from the driver’s side foot well.

However, it had one thing going for it; turning the key often made it go—at least for the first three or four months.  Serves me right.  The guy selling the car pitched it as a date-mobile, alluding to the bench front seat.  Not wanting to look stupid, I bought it.  Pretty poor due diligence.  An impulse purchase to meet what I felt was a social imperative—a lean, mean, dating machine.

The last time I made a good impulse purchase was an ice cream sandwich on a hundred degree day.  Most of my other impulse decisions could have used some good data.  The lack of good data falls on one person, me.

How good is the data you have for deciding to implement an EHR?  In selecting an EHR?  Did you perform the necessary due diligence?  How do you know?  Gathering good data is tedious, and it can lack intellectual stimulation.  I think it affects the same side of our brain as when our better half asks us to stop and ask someone for directions; we like being impulsive, and have built a career based on having made decisions on good hunches.

The difference between you buying and EHR and me buying a clunker is that when I learned I’d made a poor decision I was able to buy a different car.  You can’t do that with an EHR that has more zeros in the price tag than the national deficit.  Plenty of hospitals are on EHR 2.0–they also happen to be on CIO 2.0. while CIO 1.0 is out shopping for a Corvair.

December 20, 2011

EHR–WWOD (What would Oprah do?)

Filed under: consulting,EHR,informatics,planning,Strategy,Who's Running the Show? — Paul Roemer @ 12:13 pm

So, I’m watching a football game on television and it suddenly strikes me, there are probably a lot of people trying to understand what it is a consultant does that we can’t do for ourselves.

For those who have a life, those who missed the game, Alabama opens the game with several well-scripted opening plays and grabbed an early lead.

Their first ‘n’ offensive plays were brilliant.  They were planned perfectly.

It became apparent they had not planned the however many of the ‘n + 1′ plays.  Their plan failed to go beyond what they’d already accomplished.

How does that apply to what you do, what I do, and why I think I can help you?  It is best described by comparing your brain to a consultant’s brain.  Your work brain functions exactly as it should.  It’s comprised of little boxes of integrated work activities, one for admissions and registration, one for diagnosis, another for care.  There’s probably another box for whatever it is the newsletter stated IT was doing three months ago and how that impacts what you do.  That’s your job.

Your boxes interface in some form or fashion with the boxes of the person next to you in the hospital’s basement cafeteria who is paying for her chicken, broccoli, and rice dish that reminds you of what you ate at crazy Uncle Bob’s wedding reception.  That interface is the glue that makes the hospital work.  It’s also the synapse, the connective tissue—I know it’s a weak metaphor, but it’s a holiday weekend—give me some slack—that tries to keep healthcare functioning in an 0.2 business model.

There are names for the connective tissue, you know it and I know it.  It’s called politics.  It’s derived from antiquated notions like, “this is how we’ve always done it”, “that’s radiology’s problem”, and “nobody asked me”,

At some point over the next week or two the inevitable happens; the need arises for you to add some tidbit of information.  Do you add it to an existing box, put it in an empty box, or ignore it?  This is where you must separate the wheat from the albumen—just checking to see how closely you’re following.

Your personal warehouse of boxes looks like the final scene in Raiders of the Lost Ark—acre after acre of dusty, full boxes, no Dewy-decimal filing system, and no empty box.  There are two rules at the hospital; one, bits of information must go somewhere, and two, nobody can change rule one.

The difference, and it’s a big one, is that consultants have an empty box.  It’s our Al Gore lockbox.  We were born that way.  It’s like having a cleft chin.  We also have no connective tissue to your organization.  No groupthink.  No Stepford Wives. No Invasion of the Body Snatchers to turn us into mindless pods.  Consultants may be the only people who don’t care.  Let me rephrase that.  We don’t care about the politics.  We don’t care that the reason the hospital has four IT departments is because the hospital’s leadership was afraid to tell the siloed docs that they couldn’t buy or build whatever they wanted.

Sometimes it comes down to your WWOD (what would Oprah do) moment.  Not ‘what do they want me to do’, not ‘what would they do’, not ‘what is the least disruptive’, not ‘what goes best with what the other hospital did’.

At some point it comes down to, what is the right thing to do; what should we do.

Big, hairy healthcare IT projects come out of the shoot looking like Alabama did.  The first however many moves are scripted perfectly.  Heck, you can download them off Google.  Worse yet, you can get your EHR vendor to print them for you.

The wheat from the albumen moment comes when you have to come up with an answer to the questions, “What do we do next,” and “Why doesn’t it work like they said it would?”

That’s why consultants have an open box.  You know what we are doing when our brain takes us to the open box?  Thinking.  No company politics to sidetrack us.  Everybody knows the expected answers, but often the expected answer is not the best answer.  Almost everybody knows what comes after A, B, C, and D.

Sometimes…E is not the right answer or the best answer.

December 19, 2011

HIT/EHR: Adult supervision required

Among other things, EHR requires adult supervision–kind of like parenting.

My morning was moving along swimmingly.  The kids were almost out the door and I thought I’d get a batch of bread underway before heading out for my run.  I was at the step where you gradually add three cups of flour—I was in a hurry and dumped it all in at once.  This is when the eight-year-old hopped on the counter and turned on the mixer.  He didn’t just turn it on, he turned it ON—power level 10.

If you’ve ever been in a blizzard, you are probably familiar with the term whiteout.   On either side of the mixer sat two of my children, the dog was on the floor.  In an instant the three of them looked like they had been flocked—like the white stuff sprayed on Christmas trees—those of you more politically astute would call them evergreens—to make them look snow-covered.  (I just em-dashed an em-dash, wonder how the AP Style Book likes that.)  So, the point I was going for is that sometimes, adult supervision is required.

What exactly is Health IT, or HIT?  It may be easier asking what HIT isn’t.  One way to look at it is to consider the iPhone.  For the most part the iPhone is a phone, an email client, a camera, a web browser, and an MP3 player.  The other 85,000 things it can be are things that happen to interact with or reside on the device.

In order for us to implement correctly (it sounds better when you spilt the infinitive) HIT and EHR, a little focus on blocking and tackling are in order.  Some write that EHR may be used to help with everything from preventing hip fractures to diagnosing the flu—you know what, so can doctors.  There are probably things EHR can be made to do, but that’s not what they were designed to do, not why you want one, and not why Washington wants you to want one.  No Meaningful Use bonus point will be awarded to providers who get ancillary benefits from their EHR especially if they don’t get it to do what it is supposed to do.

EHR, if done correctly, will be the most difficult, expensive, and far reaching project undertaken by a hospital.  It should prove to be at least as complicated as building a new hospital wing.  If it doesn’t, you’ve done something wrong.

EHR is not one of those efforts where one can apply tidbits of knowledge gleaned from bubblegum wrapper MBA advice like “Mongolian Horde Management” and “Everything I needed to know I learned playing dodge ball”.

There’s an expression in football that says when you pass the ball there are three possible outcomes and only one of them is good—a completion.  EHR sort of works the same, except the range of bad outcomes is much larger.

December 15, 2011

EHR: What are the voices in your head telling you?

Filed under: EHR,Hospital,innovation,Rants & Musings,usability,Who's Running the Show? — Paul Roemer @ 11:06 am

My favorite thing about healthcare is having witnessed it up close and personal both as a cancer patient in the 80’s and as the survivor of a heart attack seven years ago.

I was fortunate enough to have testicular cancer before Lance Armstrong made it seem kind of stylish.  Caught early, it’s one of the most curable cancers.  As those who’ve undergone the chemo will attest, the cure is almost potent enough to kill you.

I self-diagnosed while watching a local news cast in Amarillo where I was stationed on one of my consulting engagements.  As we were having dinner, my fellow consultants voted to change the channel—I however had lost my appetite.  I went to my room, looked in Yellow Pages—see how times have changed—and called the first doctor I found.  This is one of those times when Never Wrong Roemer hated being right.

So, yada, yada, yada; my hair falls out in less time than it took to shower.  A few more rounds of chemo, the cancer’s gone and I start my see America recovery Tour, my wig and I visiting friends throughout the southeast.  If I had it to do over, I would go without the wig, but at twenty-seven the wig was my security blanket.  I don’t think it ever fooled anyone or anything—even my house plants snickered when I wore it around them.

I owned a TR-7 convertible—apparently it never lived up to its billing as the shape of things to come, more like the shape of things that never were.  My wig blew out of the convertible as I made my way through Smokey Mountain National Park.  I spent twenty minutes walking along the highway until I spotted what looked like a squirrel laying lifelessly on the shoulder—my wig.

The last stop on my tour was at a friend’s apartment in Raleigh.  Overheated from the long drive and the August sun, I decided to take a few laps in her pool.  I dove in the shallow end, swam the length of the pool, performed a near-flawless kick-turn and eased in to the Australian Crawl.  As I turned to gasp for air, I noticed I was about to lap my hair.  I also noticed a small boy, his legs dangling in the water, with a look of astonishment on his face.

My ego had reached rock bottom and had started to dig.  Realizing my wig wasn’t fooling anyone but me, I had one of those “know when to hold ‘em, know when to fold ‘em moments” and never again wore the wig after learning it was such a poor swimmer.

Do you get those moments, or get the little voice telling you that your EHR that the users would rather enter patient data on an Etch-A-Sketch?  It’s okay to acknowledge the voices as long as you don’t audibly reply to them during meetings—I Twitter mine.

Sometimes the voices ask why we didn’t include the users in the design of the EHR.  Other times they want to know how that correspondence course in project management is coming along.  It’s okay.  As long as you’re hearing the voices you still have a shot at recovery.  It’s only when they quit talking that you should start to worry.  Either that, or try wearing a wig.

Next Page »

Theme: Rubric. Blog at WordPress.com.

Follow

Get every new post delivered to your Inbox.

Join 34 other followers