The ambiguity & apathy of user acceptance

ambiguity

Why write if you can cut and paste.  The comments listed below are extracted directly from a blog titled SmartBlogs Work Force, http://smartblogs.com/workforce/2009/10/05/why-well-miss-ambiguity/#comment-19170.  The blog attacks Generation Why (my term) for being ambiguous in the workforce.  It seems to me that they can just as well be applied to why EHR has a low acceptance level.

  • Animosity between workers and bosses in business will increase. Ambiguity often looks pretty darn black-and-white to the worker who doesn’t see the nuance. And when workers think management is overanalyzing/dragging its feet/fumbling a simple problem, they lose patience with, and lose faith in, management’s ability to perform.
  • Many younger employees will “opt out” of a corporate system they don’t fully understand. This will ultimately prolong their own learning curve as they try to re-create a “better” structure without realizing that a number of the problems with our current structure will exist in any system populated by humans because the problems stem from our human nature, not our system design.
  • Leadership will suffer. Take ambiguity away from leadership, and you take away tough decisions and responsibility. What you’re left with is overpaid administration. That’s the image many young professionals today seem to have of leadership, so that’s what they’ll create.
  • The Applization of design will get more expensive, as companies that try to build simple products with minimal learning curves find they lack employees who can accurately predict real-world user behavior.
  • Individuals will double down on what they are good at, which in this case is solving problems by working HARDER BETTER FASTER SMARTER. This will rob many companies of their “manager class,” as people who stay in the system opt for specialist roles rather than managerial roles that come with more — yep, you guessed it — ambiguity.
  • Career paths will become more fixed. Our ability to process ambiguity extends to our ability to assess other people. Already, resume readers look for specific patterns, jettisoning capable applicants with “non-conforming” histories. This trend will continue to amplify for awhile.
  • Companies will ruthlessly centralize their decision-making functions, concentrating power with a few select people who “get it.”
  • Individuals will become more system dependent, just as people who aren’t good at division become more dependent on their calculators. This will create feelings of frustration and resentment.
  • Stress levels will explode further. If you think it’s bad now, just wait. There is a lot of unresolved fear out there. Mix in a dash of helplessness (which is a often a synonym for “unable to handle ambiguity”) and you’ve got a potent mix.

black saint 2

Universal Patient Record-can that save EHR?

fermat800Today is the anniversary of the solving of Fermat’s last theorem.  As a long recovering mathematician, these types of thing interest me so I sought a copy of the proof and began reading.  The mathematics for librarians description of the proof is something like this:

  • The Pythagorean theorem states that for a right triangle the sum of the squares of the sides equals the square of the hypotenuse.
  • Fermat stated that the theorem only holds for a coefficient of 2, squaring, and that no other coefficient will work
  • This went unproven until recently

One might have thought that the solution could be solved by brute force using a computer.  How many numbers are there to be dealt with? If you approach the problem this way you’ve got to do it for infinitely many numbers. So, after you’ve done it for one, how much closer have you got? Well, there’s still infinitely many left. After you’ve done it for a thousand numbers, how many, how much closer have you got? Well, there’s still infinitely many left. After you’ve done it for a million, well, there’s still infinitely many left. In fact, you haven’t done very many, have you?  In fact, using this approach, you’ll never finish.  This got me thinking about our EHR system.

I think something has been lost in the confusion about a national EHR system.  After all, that’s the target right, a national system?  We only unleash the power of EHR if we are able to make it work out outside of the provider’s four walls.  Is it possible that perhaps the logic of how we have been viewing developing a solution for the problem is wrong?  I think it is.  Since the outset, the problem has been defined as how do we develop a system that will enable us to get everyone’s health records (let’s call an individual record A) to some arbitrary set of healthcare providers, call them P.  There are some 350 million A’s and for simplicity let’s agree that there are 100,000 P’s.  So now, the system to which everyone is working is the system that will enable all of the A’s to get to any combination of P’s.

See?  Now what happens if we place a few hundred Rhios and health information exchanges (HIEs) in between the A’s and the P’s?  Let’s label them G’s for gatekeepers.  So, in the current framework all the A’s (everybody’s health records) have to pass through all the G’s, make it up to the national network, then back through all the G’s and then sorted through all the P’s to the correct P.

How can we know this design will work for every possibility?  The only way is to test every combination of A’s, G’s and P’s.  It’s a difficult problem.  It becomes more difficult when we acknowledge that there are hundreds of EHR vendors supplying software to all of those P’s.  Many of those P’s will have modified the software, meaning that there are probably thousands of variations of EHR systems.  Oh, and did I mention that all of this is being done without any single set of standards?  That means my stuff will look different from your stuff, and the G’s will have to move different stuff, and from an “IT” perspective the EHRs at the end of the food chain will have to interpret different stuff and then update your stuff with their stuff.  That’s a lot of stuff.

So, if that is where things are, what can be done about it?  My take on a solution is that the problem with this model lies with the word in italics, ‘everyone’.  Every possible patient with every possible need getting to every possible provider.  How to solve this or at least simplify the magnitude of the problem?  One possible solution is to build out the EHR system and the network such that one patient’s record can go to one provider and have that record updated.  Would it not make more sense to build it for a single patient, create a universal patient record (UPR) that can handle all instances?  Do it right once.  Prove that it works and then replicate it instead of building millions of different ones and hoping they work?

021_18A

Acronym-free EHR–Same Great Taste, Less Confusing

acronymsI raised the following question on Twitter:  Who blieves the current approach (PR, EMR, EHR, Rhio, to NHIN) will actually work in 3, 4, or 5 years?  Will you state why.  I do no think it will.

I raise it here as well.  Can you make an agrument to help me understand what needs to happen for this to possibly work?

 

  • 400 vendors
  • 300-400 RHIOs–some home made
  • a few hundred standards groups
  • a few hundred thousand instnaces of EHRs
  • 300 million patients

 

The combinatorics alone of getting my PR up the food chain and back down to the right place should be enough to bring it to the idea to its knees.

Remember that ice-breaker kids play at parties where they sit in a circle?  A phrase is whispered in the ear of one child, and each child in turn whispers the phrase to the person next to them.  By the time the phrase returns to the originator, it sounds nothing like to original.

A colleague whose opinion I respect wrote that I’d get better responses if I explain the acronyms, so that why we’re here.

The offending terms are:

PR–Patient Record

EMR–Electronic Medical Record

EHR–Electronic Health Record

RHIO–Regional Health Information Organization

NHIN–National Health Information Network

Does anyone know of a link to a good healthcare IT/EHR acronym glossary?

My work here today is done.

021_18A