ie8 fix

The health IT archipelago

By | November 2, 2008, 10:56am PST

Summary: How is health care technology in the U.S. like the Philippines? It’s an archipelago, islands of technology, often unconnected, linked by ferry lines of bureaucracy and paper.

Philippines map, 1992 from Magellan GeographixHow is health care technology in the U.S. like the Philippines? (This Philippine map appeared in a CNN story back in 1996.)

It’s an archipelago, islands of technology, often unconnected, linked by ferry lines of bureaucracy and paper.

That’s my conclusion after reading the final report of the Healthcare Information and Management System Society (HIMSS) Analytics group. It’s in line with results from an earlier survey published in the New England Journal of Medicine.

About one-third of respondents said some components of a computerized system were in place at their locations. HIMSS Analytics said there was “purchasing hesitation,” with just 13% saying they planned to buy an EMR system in the next year.

There is no dominant vendor in the market, the survey added, the most common application is basic charting, but three-quarters use computers to get paid.

Why? Cost and “lack of interest,” the report said.

It’s worse if you’re looking to get rid of those scribbled prescriptions. Only one practice in four uses e-prescribing, and most who don’t have no plans to buy it.

My best guess as to this state of affairs is the old, “What’s in it for me?” And it’s a valid objection.

Doctors are being told to pay for automation, but the benefits are not going to their own bottom lines. They’re going to insurance companies or hospital groups. Thus those doctors who do automate do so under pressure from such groups.

Will government pressure accelerate the trend? Only if it comes with more carrot than stick.

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Disclosure

Dana Blankenhorn

Dana Blankenhorn has been a journalist, writer and part-time futurist for over 30 years. At the present moment I run only a personal blog in addition to my ZDNet open source blog. DanaBlankenhorn.Com has the subtitle The War Against Oil. In the past I have used it to write about political history, e-commerce, personal matters, some ideas related to open source, and The World of Always On, which is the idea of using sensors, motes and RFID to turn WiFi links into platforms for applications which live in the air. My IRA account at Schwab holds a few tech shares, most notably some Intel and Applied Materials, but there are no open source companies in it. I don’t even own any CBS stock.

Biography

Dana Blankenhorn

Dana Blankenhorn has been a business journalist since 1978, and has covered technology since 1982. He launched the Interactive Age Daily, the first daily coverage of the Internet to launch with a magazine, in September 1994.
5
Comments

Join the conversation!

Just In

RE: The health IT archipelago
jake48 7th Nov 2008
There are three fundamental problems with healthcare IT
today:
1. No working model for interoperability. One cannot
export a clinical record from system A and move it to
system B. Therefore, evolution is slowed considerably
because of the huge cost of migration from an older
system to a newer one, and generally with a lot of misery
with the older vendor.

2. Poor user interface design. Most EMR's are designed to
capture task-based information using the most
rudimentary user interface. As a result, the physician
interaction is slow, cumbersome, and reduces rather than
increases the useful information available in the record.

3. Integrated vs modular in design. To use most of today's
software requires an installation of an entirely new
application, and frequently migration of data files. As a
result, steps forward are generally planned, budgeted,
scheduled, implemented, tested, and activated over a
much longer work cycle. Incremental changes are virtually
impossible.
0 Votes
+ -
If doctors are going to spend money on a
computer based system then the first
thing they need to be assured of is that
there will be no problem interfacing with
other doctor's systems when needed.
Then there is the need to interface with
the systems at hospitals and insurance
companies.

I guess in the end it will mean that the
federal government will need to set design
standards through working with the health
care and medical insurance groups.

There is also a need to have standardized
formats in areas like Imaging. I get digital
copies of all x-rays, CT Scans, etc. and
keep them on my computer (as a Mac user
I use OsiriX). The CD of my last x-ray
didn't work as the format was not
compatible. While that might not be a
problem for me it does represent a
problem in terms of a doctor's office
having a digital copy of the x-ray. My
response was simply to scratch that
radiology office off of my list of places to
use.

I'll soon be able to keep OsiriX files on my
iPhone (free) and can see that as a good
move. Far better would be the ability to
keep all important medical information on
my notebook and iPhone. Why can't I
download all of the last lab reports? Or
have read only links to my medical
records at the doctor's office and hospital?

If I go to an emergency room at another
hospital that information on my iPhone
could save my life.

The potential for all of this is huge, but it
all gets down to standardized formats and
a means of ensuring that data is available
within the privacy environment that the
medical systems have to work in.
0 Votes
+ -
RE: The health IT archipelago
apostle02 3rd Nov 2008
Standards are the first step but a big stick should be step 2. Most of the older Doctors need to be forced to use new technology.
0 Votes
+ -
A balance of old and new
Ken_z 3rd Nov 2008
The best real story I've been told was one my wife
said happened when she was going through
Physical Thereapy training. The students went into
see a lot of surgery. This was one a fellow student
was in on:

Open heart surgery being carried by one of the
brightest young heart surgeons, assisted by one of
the "older doctors". The bypass machine crapped
out after the heart had been opened and the bad
valve had been cut out. First time for the young
doc, but the older doctor was able to step in and
get the job done within the necessary time frame.
Why? Because when he was younger there was no
bypass machines and you had to have the heart
closed up within about 3 minutes.

We're in an odd time for medicine. The younger
docs played with video games when they were
young and are leading the profession in "remote"
surgery, like laparoscopic surgery. The older docs
have more exposure simply because of experience
and often have a different approach to treatments.

My wife was the same before having to quit
practicing because of leukemia. There are
machines that will finely calibrate improvements in
gross motor functions, but she preferred to feel
them herself.

Moving an older doc (or any other medical
professional) to total technology may not always
be an easy thing to do unless the screen interface
is in a format he or she is used to using. It might
require the doc learning to type when his
experience with hand skills are surgical related.

As I said, medicine is a strange (unique?) field
where we can't anticipate all practitioners to adapt
with equal ease. Sometimes we'll just have to
settle with the doc's office staff adapting.
0 Votes
+ -
RE: The health IT archipelago
connectologist 4th Nov 2008
Health care is more than just a tech archipelago - it's a
cottage industry. Each entity has its own tech because they're
independent entities. And consistently they are parties who
are loath to underwrite costs for the benefit of other "islands"
in the health care system.

Certainly government could impose its will to resolve many of
these issues. But it would be a messy business with a
suboptimal outcome.
0 Votes
+ -
RE: The health IT archipelago
jake48 7th Nov 2008
There are three fundamental problems with healthcare IT
today:
1. No working model for interoperability. One cannot
export a clinical record from system A and move it to
system B. Therefore, evolution is slowed considerably
because of the huge cost of migration from an older
system to a newer one, and generally with a lot of misery
with the older vendor.

2. Poor user interface design. Most EMR's are designed to
capture task-based information using the most
rudimentary user interface. As a result, the physician
interaction is slow, cumbersome, and reduces rather than
increases the useful information available in the record.

3. Integrated vs modular in design. To use most of today's
software requires an installation of an entirely new
application, and frequently migration of data files. As a
result, steps forward are generally planned, budgeted,
scheduled, implemented, tested, and activated over a
much longer work cycle. Incremental changes are virtually
impossible.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix
ie8 fix