The Terrorists Will Have Won…

Windows XP Logo
 

We’ve all heard the refrain, a thousand times:

“If [insert your most hated thing here], then the terrorists will have won!”

For example,

  • “If we restrict our civil liberties (read: “If BushHitler doesn’t stop checking the child porno sites I visit”), the terrorists will have won!”
  • “If we don’t preserve freedom of the press (read: “Leak top-secret info about our war plans to the NYT”), the terrorists will have won!”
  • “If we don’t save the snail darter from extinction, the terrorists will have won!”

Etcetera, etcetera.

Of course, we’ve been hunting for this guy Osama, who hides in caves and makes videos (hint: check out Michelle Malkin’s basement–she may be Osama in drag). But we’ve been hunting the wrong guy: the guy we really should be going after (not to kill or anything, but surely to “bring him to justice”) is Bill Gates. This man is far more dangerous than any white-berobed, gray-bearded, Koran totin’, cave-dwellin’ movie mogul, ’cause he’s the guy who’s really trying to destroy Western civilization.

So I’m adding my own refrain to the litany:

  • “If we don’t all switch to Macs, the terrorists will have won!”

Case in point: yesterday. Time: After hours. Place: My office.

Situation: Dell network client, front desk scheduling and demographics input. Plain Jane machine, function critical. Windows 2000. Doesn’t play well with the new scanner for insurance cards.

Game plan: Update to Windows XP. Anticipate best case 45-60 minutes.

Time: 1700.

Preparation: all driver disks available. New XP copy with license.

Outcome: Disaster. Unmitigated.

Pop in the XP disk, and reboot from the CD. Installer comes up as expected. Options are new install, or upgrade. Pick upgrade, of course, so settings and preferences are preserved. Let ‘er rip.

Smooth so far, go catch up with some charts and other after-hours chores. Mosey back to the machine 20 minutes later.

Time: 1730. There’s a dialog open, asking for Intel Extreme Graphics driver file “ialmnt5.sys.” No problem, built-in video, it’s on the driver disk from Dell.

Or not–insert the CD, nowhere to be found. We’re 1/3 of the way into the install. Search the web at Dell’s impossible site from another machine, can’t locate the driver. Several driver sites have it, but require paid subscription. OK, skip it, and Windows will install a generic video driver, find it later. Click on “Skip this file”, the install marches on.

Time: 1830.

Install finishes, license entered, a few simple configuration steps (Date & Time, language) done. Reboot the machine.

Time: 1845.

Boots fine to login screen. Login to domain. Hourglass. Blue screen.

Blue screen. Maybe it’s configuring stuff before the desktop shows.

Blue screen.

Time: 1900. DOA.

Reboot. Same drill. Dies in blue screen at desktop.

Reboot. Login to local machine, not domain. Blue screen.

Horse turds.

Time: 1920. Call my wife, gonna be late, not sure how long.

Windows install CD goes in again. Disconnect scanner. Boot from CD.

Choice menu comes up: New install. Repair damaged install. Type “r” for repair.

Poorly worded menu. “Repair damaged install” really means “Reinstall a damaged system which won’t boot, either.” Install repair starts anew. Sit and watch the annoying marketing blather on screen about how great XP is, how easy to use.

Time: 1945.

It’s the damn “Intel Extreme Graphics driver file ‘ialmnt5.sys'” screen again. Have to find this sucker now. Pop the Dell driver CD into another machine: the file’s not on the disk. But you can unpack the compressed video drivers to the other, working machine. Big flippin’ help that is.

The perfect Catch-22: can’t install Windows XP without the driver. Can’t install the driver on the target machine until XP is installed. More horse turds, larger and steaming–kinda like the steam wafting from my ears.

Time: 2015.

Skip the video driver again. Install completes. Enter license again. Reboot. Blue screen at the desktop.

What are they feeding this horse?

Time: 2100.

Call the wife: may be home by April 2008. Leave a light on.

Gonna have to do a fresh XP install. That means: reinstalling Windows; reinstalling the applications, the scanner driver and software; finding the lost license for the billing software terminal application; configuring the network, the printers, the internet; salvaging the favorites, the preference files, custom registry settings. Mapping network drives. Changing the desktop appearance and shortcuts. Testing the software, the EMR database connection, the unix terminal, the scanner.

This machine has to be online at 8:00 AM. Ain’t no goin’ home ’till that happens.

Major horse turds.

Time: 0145. Just got home. Woke the dogs up. They think it’s 8 am and want to play. I feel like its 8 AM and I never slept. 9 hours of my life–a full work day–gone. After a full work day. Jeez.

I’ve installed Windows on dozens of machines, a hundred times. More often than not, this is just how it goes. And don’t even ask about installing Windows Server 2000 or 2003, with RAID drives, users and groups, priviledges, security configuration. Three-day weekend is about right–if all goes well.

Two months ago, I installed Mac OS X Tiger on several home and office Macs. Stuck the DVD in the drive, set a few options, clicked Install–and came back 30 minutes later, ready to use. On the network. Connect to the ‘net. Printers work. Scanners work. Peripherals work. RAID drives just fine. The only restarts I ever need are for major security updates, about once a month. It never crashes–ever. But the world runs on Windows. Suck it up.

This is 2006do ya’ think we could get an OS which could be installed and operated without a PhD. from MIT, in less than a day’s time?

I’m convinced that when the Islamists take over our country, no one will notice. We’ll all be trying to get our Windows machines running. And the terrorists will have won…

Virtual Paris

Eiffel Tower
Here’s a quick one–take a virtual tour of Paris from the Eiffel Tower. There are many benefits to such an approach:

  • No air fare
  • No jet lag
  • No snooty Parisians looking down on you for your multi-colored jogging suit couture
  • You’re really far from the Muslim neighborhoods, greatly decreasing your chances of having a car fire.

Voice Recognition Redux

trollSeveral months ago, I upgraded my voice recognition software to Dragon NaturallySpeaking version 8. I have been using voice recognition software for over five years now, and have been very satisfied with it, although older versions could be maddening at times–and hilarious at others. This version is amazingly accurate–my only complaint since upgrading is that I am not having nearly as much fun proofreading my notes as I have the past.

Voice recognition software is rather remarkable technology, and to watch the medical version crank out complex terms with aplomb is almost magical. The software does not make spelling errors, but contextual errors are relatively common, and need to be carefully screened before sending your documents out the door.

A few of the contextual swaps I have encountered are as follows:

What I said: The patient said Viagra wasn’t working, and wanted to try Cialis.

What it typed: The patient said Viagra wasn’t working, and wanted to try and see Alice.

What I said: The patient was thoroughly reevaluated by her previous physician.

What it typed: The patient was thoroughly violated by her previous physician.

What I said: The patient will be started on depot testosterone.

What it typed: The patient will be started on devil testosterone.

What I said: The patient has prepubertal pubic hair changes.

What it typed: The patient had puréed pubic hair oranges.

The accuracy of this latest version has made such–ahem!–interesting errors quite a bit less common — to the point where I was becoming a bit complacent about careful proofreading. That is, until today:

What I said: The patient was seen several years ago for problems of urge incontinence, and has been on Detrol with good symptom relief.

What it typed: The patient was seen several years ago for problems of urge incontinence, and has been on a troll with good symptom relief.

And you thought they spent their entire lives living under bridges

EMR Blues

I’ve been following in pained silence the saga of Medpundit and her transition to an EMR (electronic medical record). If it’s any comfort to her, I feel her pain.

The computerization of medical records has been the Holy Grail of medicine for many years now, the answer to all manner of problems in health care delivery. Yet while we scan our groceries, submit taxes online, get money from a teller machine thousands of miles from the bank where our account resides, print detailed driving instructions to an obscure address in a strange town, and enjoy many other marvels of computerization and networks, the sad and sorry fact is that most physicians today document your health care in much the same way their grandfathers did: scribbling with pen on paper, filing the paper in a manila folder, and placing the chart (eventually) in a massive rack of other records organized using an obscure color chart based on the first letter of your first name. In a profession so utterly transformed by technology — CT scanners, minimally invasive surgery, gene therapy, etc. — it is nothing short of amazing that such an anachronism remains the norm. Yet only about 10% of physicians use an EMR in their practices. So, wassup?

The answer — like most things in medicine — is far more complicated than it looks.

The appeal of an EMR is obvious, and akin to the benefits derived from computerization in general: instant access to information, organized and readily available. Piles of paper and disorganized files disappear, replaced by the warm glow of a computer monitor. Smiling, relaxed staff no longer run around like rats in some twisted neurophysiology study, demanding to know for the very last time where you’ve hidden Mrs. Jones’ chart. Lab results at your fingertips, sorted by date and test, annotated with appropriate alerts to notify Mr Smith about his elevated blood sugar. The doctor spends more time with you, sees you on time, goes home at 5 pm, and plays with his children until bedtime, arriving back at the office rested with his morning coffee just before the first appointment.

At least, that’s what they tell you. The reality is vastly different.

This is a subject with which I have a more than a passing familiarity, having designed and developed an EMR software application for my practice over the past 12 years. Using an obscure but wonderful database application platform called 4th Dimension, I began in the early 1990’s to seek a solution for the repetitive mindlessness of dictating or hand-writing charts. Needless to say, a small project to create a database of chart notes and templates got wildly out of hand, and has now grown to well over 100,000 lines of code. Don’t try this at home, folks — at least if you want a life. I became so engrossed in this project that I even considered abandoning medicine and doing it full-time — a delusion which by God’s grace has since passed. But the logical-sequential perfectionistic obsessive-compulsive in me found a natural home in software development.

Now, apart from the huge black hole of time and effort in its development, my EMR is about as good as it gets. The software is designed specifically for the way I practice, right down to the dictation, data entry, templates and formatting style. I know exactly how it works; no training or familiarization necessary (my staff begs to differ, of course). I can — at least in theory — make it perform any task, exactly the way I want. And don’t get me wrong: it’s my baby, and I love it, and couldn’t get by without it. But it largely disproves many of the purported benefits of an EMR. So where’s the problem? What happened to Nirvana? Hmm, where to begin — here’s a few thorns in the flesh for starters:

 • Data Entry — That cryptic scribble that doctors are known for — sometimes called handwriting — is actually a very efficient shorthand; it is one of the few things doctors learn in medical school that is useful later in life. Sure, it’s impossible for others to read, terse, loaded with obscure acronyms, but it’s fast. And those little sketches in the chart communicate a world of information. Now move to the computer: you have to sit at a keyboard, type full words, and have no easy way to reproduce your descriptive drawing. Sure, there’s lot’s of software tricks to speed things up, such as popup menus, glossaries (short phrases which expand to full text), checkboxes, etc. But it’s still tedious, and takes much more time for the same information. Granted, the information is readable and can be easily organized. But it adds a lot of time to a too-short day.

 • Depersonalization — I can make quick shorthand notes while still maintaining a conversation — and eye contact — with my patient (and yes, I know a lot of doctors stare at the chart, with no patient eye contact: BAD doctor! Shame!). Now bring a laptop, or even a new tablet computer in the room, and the dynamic changes: the focus is on the machine, the technology, the keyboard. The patient begins to feel like a spectator, akin to talking to someone who’s using a speaker phone: you know their focus is on something other than you. One more barrier has been thrown up in the relationship between doctor and patient.

 • What about the paper? — We’ve been hearing for years about the paperless office. Ever seen one? Neither have I. Even in a small solo practice, with an entirely electronic medical record, the amount of paper arriving daily is nothing short of staggering. Lab reports. Insurance forms. Hospital dictations. Work releases. Physician letters. Record requests. Notes and med lists from patients. It’s endless, and it’s brutal. It all has to be reviewed by somone (often the physician), and filed. Most of these items have to be associated with a specific patient’s chart, and this means one thing: scanning. The paper must be converted to a digital image — and that’s just the beginning. It has to be linked or imported to the patient’s record in the database, and then categorized and named. You see, an image is just that: a bunch of random dots which only have meaning when interpreted by the human eye and brain. Want to get the results of Mrs. Jones’ lab test you’ve scanned in last week? Computers are great at searching for text strings, but have no clue that this binary collection of black and white pixels contains your blood count results. A human has to enter linked information associated with the binary file in order to retrieve it. Yes, there are OCR (optical character recognition) programs to convert images to text, but they have an unacceptable error rate even on high-quality typed originals, and are useless for low-quality copies or faxes, or complex reports like lab. So the quick-and-dirty routine of read, pull chart, sign off, and stuff in the folder, becomes: read, scan, import, query database, link, name, categorize, save, sign off. Doesn’t sound too bad until you’re dealing with hundreds of pages a day, but there’s more steps, and each one is more time-consuming. Only after this process does the benefit of rapid information access accrue.

 • What about the old charts? — Oh yeah, those: thousands of ’em, with thick piles of paper in each. Loads of junk, like duplicate copies, insurance forms from 5 years ago, post-it notes, and lab results pasted like shingles on single pieces of colored paper, 5 or 10 to a page, different tests, different dates. And the staples — all have to be removed before scanning, lest the scanner jam and devour your only copy of a pathology report faster than a Rose Law Firm shredder. These charts are an absolute nightmare to convert to digital form for any size practice moving from paper to EMR. But if you don’t tackle this, you end up with a orcish mutant, with some information on paper and some on computer — the worst of both worlds. You can contract this job out, but it’s prohibitively expensive, quality is spotty, and the results are either unorganized or mis-organized. It has to be done in-house, in my opinion. And it’s not a job for your father’s scanner, the one you use to e-mail that 3×5 print of Junior to Grandma. High-speed document scanners are a must, and they are very expensive.

 • Legacy software — Almost all physicians have existing software in their office to handle insurance billing. It’s usually butt-ugly but functional, understood only by those coding specialists plying their arcane craft, squeezing blood out of Prudential’s rock. And the information therein — demographics, insurance data, coding information, phone numbers — is needed by your spiffy new EMR software. Simple data transfer? Fugeddaboutit. No electronic data export option available – or your billing software company will write a custom job for you (something which should take, oh, an hour of a competent programmer’s time) for a mere $10-20,000. Right. It’s called Square One: you have to manually enter all your names, insurance info, and — God forbid — accounting and ageing information into your new software. Cancel all staff vacations, call for Chinese carry out, limit bathroom breaks, and be prepared to spend many nights and weekends in the office.

 • Design issues — Did I mention that EMR software is very hard to design well, and very rarely well-designed? Medicine and health care problems don’t fit well into standard, cookie-cutter design models, unlike, say, accounting, banking or payroll. Lots of people and countless man-hours have been spent on medical informatics — the technology of mapping health care to computers — and there are miles to go before we sleep. Different areas of medicine are widely divergent problem domains: a pediatrician, a heart surgeon, a radiologist, an anesthesiologist, and a pathologist all have vastly different requirements for managing, organizing, and retrieving health information, and shoehorning them into a single off-the-shelf software package just doesn’t work.

And there’s another problem: the people who are skilled at designing software don’t understand the problem domain of medicine, and the users (doctors and office staff) on the medical side don’t understand or communicate their work flow well to the software designers. The result is software with lots of bells and whistles that programmers love, but which is hard to learn and use, and forces users to work inefficiently. This is a widespread problem in the software development world, and one reason why a staggering percentage of large custom software projects – greater than 80% – never reach completion.

 • Cost — In the final analysis, it is in large part about cost. The financial hurdles are legion: hefty hardware to run the applications; firewalls and tight security for protected health care information; fast networks to handle images and other large files; redundant and offsite backup; staff training and support; expensive software packages (often over $100,000); the enormous number of man-hours to input and archive legacy data. Are there huge benefits to be had once the transition to EMR has been made? Absolutely, but the time line is very long and the cost-benefit ratio simply does not make much sense for many physician practices. Margins are tight in health care, and growing tighter. Investing huge resources in information technology is not a high priority when many practices are struggling to meet payroll.

So, will we ever get there? Yes, eventually — I anticipate 10 or more years before this is nearly universally implemented. And don’t be surprised if the touted benefits for cost reduction and efficiency never materialize as predicted, although the clinical benefits will be substantial. Blending the art and science of medicine in this area is a formidable task. Like emulsifying lemon and egg yolk in a fine Bearnaise, this transition will take lots of patience and see slow progress, with lots of scrambled eggs in the interim, but the results will be well worth the wait.