I'm not saying there aren't opportunities to improve healthcare using
information technology--I worked in healthcare IT for seven years and
still consult in the field from time to time--but I think that this
approach (a typical techie approach, incidentally) of "what are the
opportunities" is part of the problem. I think that approach is
commonly a problem, in that it ignores the special circumstances of any
industry, and also that it tends to activate the very attitudes that
Robert identifies as being problematic. He's correct--they
are--but they can be minimized by adopting an entirely different
approach to integrating information technology than his conventional
approach.
Many people are just completely put off when someone, anyone, comes in
with little or no knowledge of their job or industry and starts
spouting ideas for improvement. We in the technical world
recognize this as open-ended brainstorming, and are less defensive
about it than many. But when you try it on someone who may be
apprehensive about technology in the first place, say a medical
professional, and worried about their job in the second, you've got a
recipe for rejection.
In my experience, it's better to start the other way around--learn the
industry and listen to what the people who know it are saying.
Don't be aggressive and far-reaching, and for the love of all that is
holy, don't try anything on the edges of functional technology.
This is especially true in the medical industry. The sorts of
teething pains and integration issues that we in technology accept as
the price of doing business are completely unacceptable in medicine,
due to a number of factors: One, HIPAA regulation is stringent
and far-reaching, and is going to have some teeth when enforcement
really kicks in; Two, the pucker factor of messing up information
storage and retrieval goes up considerably when you have lives on the
line; and three, staffing shortages and revenue demands stretch nerves
to the breaking point where a single hiccup in an electronic chart can
throw the entire clinic/floor/whathaveyou into chaos and condemnation.
That's why prototyping 50 beds is a lousy idea... it's not so much the
small roll out as a demonstration of technology feasability (which is a
good idea) but the thought of charging into it without dotting every I
and crossing every T. The bugs that we considerable inevitable
will condemn the entire project from the point of view of the medical
staff who have to work with it; and word travels quickly.
Then, too, there is the rapid rate of change in medicine that makes it
difficult to implement complex, regimented IT systems to handle.
Other than IT itself, there may be no other general field which
reinvents itself so quickly and so often. New procedures,
methods, and practices cascade down regularly, and computers are
frankly horrible at accomodating them. There are places where the
flexibility of a human mind and hand will always outpace a computerized
system in efficiency.
When you start mucking with billing systems, then the patients get the good news as well....
At any rate; don't assume that the failure rates which we have come to
accept in other industries are tolerable here, and don't underestimate
the repercussions of even ONE goof on a Tablet PC that a pen and paper
chart would have handled with elan. If technology in the
healthcare industry seems Dark Age to us, it's exactly because previous
crusaders have failed to recognize or adhere to these principles, and
the backlash is with us all today.
Get to know the systems you propose to replace, and alter them only in
moderation and with thorough bullet-proofing. Don't try to
replace manual systems that cannot be documented in sufficiently
regimented detail, and accept that computers are not always the
appropriate answer to certain muddled situations. Sometimes, the
muddle really is the most appropriate system.