Harvard Says Computers Don't Save Hospitals Money
Lucas123 writes "Researchers at Harvard Medical School pored over survey data from more than 4,000 'wired' hospitals and determined that computerization of those facilities not only didn't save them a dime, but the technology didn't improve administrative efficiency either. The study also showed most of the IT systems were aimed at improving efficiency for hospital management — not doctors, nurses, and medical technicians. 'For 45 years or so, people have been claiming computers are going to save vast amounts of money and that the payoff was just around the corner. So the first thing we need to do is stop claiming things there's no evidence for. It's based on vaporware and [hasn't been] shown to exist or shown to be true,' said Dr. David Himmelstein, the study's lead author."
Well, that's mouthful, but with electronic records you can at least switch doctors without having to take X-rays, tests, and other records again. No?
Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
And have significant responsibilities for patient care and management. Computers have made my life much easier. With electronic charting I can follow all of my patients directly from a terminal that I carry with me. The charting software we have includes basic spreadsheet and summary functions that are highly customizable. I am able to track trends and make decisions for my patients based on sight and intuition rather than having to sort through paper charts and bad handwriting. Its all at my fingertips. I don't know where Dr. harvard did his research but maybe he just has bad software. My computer system is outstanding and I honestly don't know if I'll ever be able to work in another hospital.
"IT systems were aimed at improving efficiency for hospital management"
Doctors and other medical personnel do not typically hold much power
when it comes to IT.
Software vendors aim to please management, they are the ones who take
the purchasing decisions.
Your typical Lab software for example might not have a straightforward
way to cross-check isolates for emerging resistance trends,
run critical screens or automatically report to a global EPI database,
but it sure has 1,000 ways to generate Aging Reports and auto resubmit insurance claims.
So which is it, irony or coincidence that I am reading this online within minutes of this being posted?
TFS: For 45 years or so, people have been claiming computers are going to save vast amounts of money
Reminds my of ancient times (yes, about 45 years ago) when my father was sitting over nicely striped printouts (blue and white) at home in the (late) evenings, swearing about the introduction of (then) a mainframe for bookkeeping. He was not convinced that the thing would save either work nor money and never changed his opinion.
CC.
TaijiQuan (Huang, 5 loosenings)
Having worked in an academic medical center and having a bit of exposure to doctors, I can say this...they may be able to patch you up but most doctors don't know shit about computers. It's the reason that most of them still scribble things down in some incomprehensible handwriting--they either don't have the time or don't want to learn a different system for keeping records.
Actual savings probably won't be realized until everyone in the system starts to use it and have information that is easily transferable between clinics/doctors/hospitals. Another hoop to jump through are the HIPPA requirements, not only on the federal level but on individual states as well.
The other thing I looked for but didn't find in the surprisingly short study (only 7 page PDF) is any type of linking the potential administrative gains which were offset by IT costs. The study glances at this question, but admits it doesn't know why the costs had not decreased. Not that this isn't the case, but it's just guesswork which takes a fair amount of bite out of the report. If they could definitely say that yes, IT costs are eating up the savings, then that's something. But with the way our health system is run here in the States, I wouldn't say that our system couldn't be improved upon...of course, that's a whole different discussion.
And they usually aren't.
I'm a radiologist and computers have definitely improved patient care and saved the hospital money (or alternatively made the hospital more money) in our field. From digitized images and the ability to outsource to overnight coverage to voice recognition to get turnaround for finalized reports in an hour it has undoubtedly worked. And that's with in most cases only fair implementation of a computer system.
With most hospitals, the problem is that they like to do a piecemeal transition. Digitize a subset of notes and vital signs, half the time what you need isn't there so you have to look through the paper chart AND the computer chart. Or the vital signs are only half in the computer and half on a chart, so nurses double their workload. And when it's set up, they do it with an IT-centric interface that doesn't make intuitive sense to most users. When I use them I can see through my background in computer science and engineering why things are done a certain way, but it doesn't make any sense to physicians, nurses, etc.
Then they add in a new piece, such as more vital signs (but in a different section), some dictated notes, some linking to the outside. Outpatient notes are digitized, inpatient notes are still handwritten, etc. ED notes are separate, with their own system. It's a complete mess. This method is a waste of money and time, all for the sake of early deployment of a suboptimal system and minimal re-training of the staff to use a new system.
The VA had a decent attempt with CPRS. They digitized everything - from physician admission notes to clergy notes. At least everything is in one place, but people are overwhelmed with data and it's too easy to copy and paste incorrect or inaccurate information. The interface is also suboptimal (graphing lab values involves selecting a range of tests, building a worksheet, etc. much like you'd expect an engineer to make it for maximum flexibility, but minimal ease of use). And connecting to other VA systems is hit or miss.
Perhaps the best method is to build a new hospital from the ground up. All patient records get digitized (scanned, at least, if not run through some OCR). Have a tightly integrated medical record system developed in collaboration with health care practitioners. That would save the hospital money, in the long run, compared to them starting from scratch with paper records.
We are over ambitious. The more code we write, the more bugs we create.
The trouble with hospital data is that it is messy. You have to accept that.
It's tempting to design a hospital data system with specific fields for each item, every procedure enumerated, and every field validated. You want to normalize your data. You want it neat and tidy. You can work very hard trying to enforce this. You're screwed though, because life isn't like that.
You'd be better off with relatively "dumb" software, almost like a wiki, that lets you efficiently handle arbitrary text and arbitrary data blobs. It needs fast Google-style search. It needs to allow arbitrary associations so you can handle stuff like a patient claiming to have the same social security number as a different patient or a patient who claims to have a different identity than he did the last time he visited.
Then you need to keep medical staff away from both paper and computers. Data entry is for data entry specialists.
We had the same experience signing up for insurance with State Farm. We got 3 types of insurance from them, and the lady sat there and asked us our name, address, phone number, and many other questions 3 times in a row.
She also had her sweater on inside out and typed with only 1 finger on each hand.
Not only that, but when my wife filled out a customer satisfaction survey describing the experience, State Farm sent it directly to the lady we complained about, who then called my wife about it. WTF State Farm?!
I was sorely tempted to change insurance right then, but laziness got the better of me =\
Are extremely change adverse as well. I worked at a large cancer centre. After a software upgrade that added a lot of extremely helpful features I still got tonnes of complaints for things like "the close dialog button moved from the bottom left of the form to the bottom right". Sure you have muscle memory, but it is an extremely minor difference and you still know what you need to do, but still it was a big deal for them. It was sometimes to the point where doctors just didn't want to deal with any change so they had a nurse do all the computer stuff for him like open the patient image and "click the button show image for me and call me when the image is on the screen".
I worked on an EHR procurement process for the last several years and, yes, there's a LOT of crapware out there, but I have seen systems deployed that were almost entirely reliant on the input of the actual front-line providers and they'd sooner saw off their own arms than go back to paper records.
"They should start working now to have all records be electronic, X-rays, MRIs, personal history, etc. should be in formats that can be directly shared between doctors."
They already do. It's called HL7. It's been around for twenty years. Teleradiology is nothing terribly new anymore either.
As for "having a doctor or nurse putting in billing codes," look, if they're worth half their salt, they can already rattle off the ICD9/10 codes with sufficient accuracy from memory that it's actually faster than scribbling the condition on paper.
Yes, even GOOD systems can fail if deployed poorly. ITFA they admitted "we sucked when we used paper, then we went to computers and lo-and-behold, we still sucked just as badly, almost precisely so, ergo, we're pretty sure it was the computer's fault." This is a typical case of bad management pointing the finger at the technology to cover their own incompetence. I'm sure when they were on paper they blamed the f'ing pencils.