Slashdot Mirror


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."

398 comments

  1. Transferability by oldhack · · Score: 5, Interesting

    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.
    1. Re:Transferability by Psaakyrn · · Score: 1

      Apparently they did it wrong then. Sounds like it's more of spent on improving work-flow/patient-flow.

    2. Re:Transferability by ximenes · · Score: 2, Informative

      Your records belong to you. You can request them (and depending on the hospital / doctor's office, they may claim you can only receive copies or that they will only send them directly to your new healthcare provider) at any time and take them with you.

    3. Re:Transferability by oldhack · · Score: 1

      They don't necessarily keep good track of your x-rays and such, I was given the impression from an orthopedic guy. Not to mention hand-written notes that are impossible to decipher. But good to know the rules, though.

      --
      Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
    4. Re:Transferability by jma05 · · Score: 5, Informative

      Nope. The current Electronic Medical Record systems are not capable of exchanging information freely. There is no standard data format that everyone can exchange.
      There are a few standards that can package data, but they are not adequately specified for seamless interoperability.
      If you request records, they can print them out quickly for you though.

    5. Re:Transferability by jma05 · · Score: 2, Informative

      One would wish. Doctors either spend more time with electronic systems than with paper systems... or if it is a good system... about the same time.
      The current systems haven't made doctors more productive. There may be an exception or two though in select settings where considerable grant dollars were poured in to build a locally optimized system.
      Building good clinical systems is hard.

    6. Re:Transferability by AK+Marc · · Score: 5, Informative

      "The problem "is mainly that computer systems are built for the accountants and managers and not built to help doctors, nurses and patients," the report's lead author, Dr. David Himmelstein, said in an interview with Computerworld."

      The systems aren't put in help the doctors. They are put in by the non-medical managers to help their jobs. And they fail at that. A system designed for doctors with the goal of reducing error and improving care could work. But that's not what the systems are. 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. Then processes and systems that are designed to help the medical care should be used to put that information to good use and let patience get improved care for a lower cost. But the systems are all billing systems first, and care second. And that's why they fail, and always will. Improving billing doesn't help care, and can often make it worse, as having a doctor or nurse putting in billing codes will only slow down the process.

    7. Re:Transferability by Z00L00K · · Score: 1

      If they don't save money - do they use the computers in an efficient manner or are they just advanced typewriters?

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    8. Re:Transferability by Anonymous Coward · · Score: 1, Interesting

      I would like to see him try to do0 the mapping of a genome with paper and pencil.

      This article is stupid.

    9. Re:Transferability by wisty · · Score: 4, Funny

      But what if it's in XML? It would inter-operate then.

      Or better still, a binary blob wrapped in XML. That would really make it easy to use!

    10. Re:Transferability by Linker3000 · · Score: 1

      A good point. I have been working on a committe developing standards for the transmission of information between veterinary records in the UK (and we have interest from other countries). The so-called VetXML standard is already being used for insurance claims and lab results, with referrals on advanced testing.

      As per /. standards, I did not RTFA, but I would suggest that "Poorly designed computer systems do not save money" would be a better title.

      I have just finished phase 1 of the roll out of a new clinic management package within our group - we have 31 veterinary clinics in the UK and 9 are now on a new system with improved workflow, easier client and patient management and better management reporting. We can see and benchmark clear benefits in time and cost - fair enough, the major benefits are at the back end (reporting etc), but clinic staff have already praised things like quicker patient searches and more accurate billing, stock management and recalls administration.

      There are clear benefits of the new system so I am confident to say that not only is it more efficient and will save money compared to a manual system, but it will also do the same compared to our other two clinic management packages - one is old and reliable (accessed through VT220 terminals or PCs running an emulation package) but very outdated and has no serious reporting or connectivity abilities, the other is 'modern' but buggy (crashes often), poorly written with a bad database schema that is totally space inefficient.

      I think it's wrong to dismiss computerisation per-se, but there are good and bad examples of system implementations to be seen everywhere.

      --
      AT&ROFLMAO
    11. Re:Transferability by adolf · · Score: 1

      But what if it's in XML? It would inter-operate then.

      Or better still, a binary blob wrapped in XML. That would really make it easy to use!

      I don't know whether to laugh, or to cry.

    12. Re:Transferability by Anonymous Coward · · Score: 0

      Nope. The current Electronic Medical Record systems are not capable of exchanging information freely. There is no standard data format that everyone can exchange.
      There are a few standards that can package data, but they are not adequately specified for seamless interoperability.
      If you request records, they can print them out quickly for you though.

      er... what's DICOM. HL7?

      If they aren't standards for information interchange in PACS systems then I must have dreamt the last few years.

    13. Re:Transferability by malkavian · · Score: 4, Insightful

      That's only part of the story. A LOT of systems are put in by heads of medical departments who engage directly with vendors, who tell them this system will cure all their ills and make the world a better place.
      They then buy in this system without asking anybody, and turn up at IT saying "We've bought this, put it in now please". Most hospital directorates back the clinicians (politics, gotta love it) and force IT to support this, even though it may duplicate information held elsewhere, or not be able to communicate with anything else. This crucifies efforts to create an enterprise class architecture.
      That being said, there are (in the NHS) many moves towards having everything standardised and digital (PACS, for example, works nicely; Dicom imagery across all hospitals connected to the NHS network. That's your XRay and MRI imagery right there).

      The problem is that very few places take IT seriously. It's viewed as a "wave a magic wand and things happen" discipline. Few want to hire system admins, let alone systems architects.
      And without people to actually work at integrating IT to the business, and without them having the remit to be able to affect business processes to help this symbiotic relationship take hold, then places will continue to scrabble ineffectually.
      If you're building a house, hire an architect. If you're building an IT system to prop up your business correctly, hire a systems architect.
      You could, of course, be happy with your IT system being the logical equivalent of a house built on mud with 22 windows on one side of it (never facing the sun) and no stairs to the upper floor that can be used.. But hey. You choose the path you walk.

    14. Re:Transferability by Anonymous Coward · · Score: 0

      what bull!
      hl7 has been around for donkeys years. I work with it on a daily basis and it pretty much provided me with everything I needed.

    15. Re:Transferability by terryducks · · Score: 1

      XML ha! Amateurs. The "Health Care Industry" uses something even more powerful than a fully armed and operational battle station. HL7.

    16. Re:Transferability by hairyfeet · · Score: 1

      While this may be true, my mom (a retired nurse) laughed her ass off when some politician came on TV talking about the savings there would be in having the medical field completely computerized. She said the FIRST THING a doctor does when they take over your case is print every. damned. single. bit. of your info out and stick it in the chart and while they are caring for you they scribble on the things all kinds of orders, notes, etc which then some poor nurse has to come along and put BACK into the computer.

      She said the computers slowed the nurses down more than anything they had. Having to re-input doctor's notes, bad permissions where nurse A can only get to A when she is assigned to B and has to wait on a nurse with B permissions to log her in, etc. My own doc is constantly complaining about being held up or not being able to get the full info on a patient because the ancient mainframe that everything goes through "gets cranky" and they have to wait on the one old guy that can get the old POS to "play nice". From what I gathered hospitals in general are just a mess.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    17. Re:Transferability by Anonymous Coward · · Score: 0

      The so-called VetXML standard is already being used for insurance claims ...

      Yes, dear Americans, in real civilized countries even animals have health coverage.

    18. Re:Transferability by Bert64 · · Score: 3, Insightful

      There are clear benefits of the new system so I am confident to say that not only is it more efficient and will save money compared to a manual system, but it will also do the same compared to our other two clinic management packages - one is old and reliable (accessed through VT220 terminals or PCs running an emulation package) but very outdated and has no serious reporting or connectivity abilities, the other is 'modern' but buggy (crashes often), poorly written with a bad database schema that is totally space inefficient.

      I encounter situations like this a LOT... There will be an old system which is perfectly reliable, has been running for years and everyone can access it using whatever ancient terminals they have at their disposal. And it will usually be quite efficiently written because it runs on old hardware.
      Then some vendor will come along and blind management with a pretty graphical frontend, so they sign up and begin a transition to a new fancy looking graphical system which looked very pretty to the management types who quickly demoed it at the vendors offices...

      Of course, the vendors setup will have a very small data set, will be carefully set up to look as good as it can (they might not even let you touch it, just demo it themselves being very careful to avoid features which are known to be buggy), and the management types won't have tested it for very long (or at all) before they decided to buy, and these same management types won't have to use the resulting system once it's installed.

      Costs will rapidly escalate as you have to replace all your ancient terminals with new fancy equipment designed to handle the pretty graphics...
      You start loading your live data into the new system and find that when it has actual data in it, the new system is very slow and inefficient (but still looks nice!) because it was never tested under any realistic usage cases...
      You find that the original quoted hardware requirement was already insufficient (to make it look cheaper), and coupled with how slow the new system runs with real data you now have to increase your hardware budget...

      And once the system is finally installed and people start using it, you find that...
      While the app looks very pretty to management types, the people who actually have to use it find that the pretty graphics get in the way, and that the new app is far less usable than the old one.
      Your users were used to the old system, and don't like the new one, but this gets dismissed as "users dont like change" and blamed on them wether that's the case or not.
      Even new users who weren't used to the old system have trouble with the new one..
      When under actual load, the performance issues are even worse..
      The new system has lots of bugs, which the vendor expects you to adjust your working practice around rather than bothering to fix them...
      The new system also has a different workflow, which again the vendor expects you to adjust your working practice around.
      The new system brings with it a lot of unnecessary functionality which you don't need, and which will get abused by staff and external hackers alike (people didn't spend all day using facebook on green screen terminals, and didn't browse websites or view files which try to exploit your machine and own it)..
      As a result of the unnecessary functionality and new security risks, your administrative burden is now much higher (or the vendor convinces you otherwise, and you coast along for a while before you start having major problems).

      There's a lot to be said for keeping it simple!

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    19. Re:Transferability by Bozdune · · Score: 2, Informative

      "The problem "is mainly that computer systems are built for the accountants and managers and not built to help doctors, nurses and patients," the report's lead author, Dr. David Himmelstein, said in an interview with Computerworld."

      That's not the problem, and doctors aren't going to make money-saving decisions anyway (what planet is this guy from). The real problem is that hospital administrators are uninformed and powerless. For example, most hospitals use Group Purchasing Organizations (GPOs) that actually don't save them money, yet the administrators are convinced that everything's just fine and that they're all set. And most hospitals don't intervene in the purchasing decisions made by doctors -- they think, "zomg what if our Star Doctor leaves us and goes with Hospital X" -- so it's hands off on anything the prima donna decides to do. The result is that the hospital will not buy software that could save them money immediately on every purchase decision, and it will not second-guess any purchasing decisions made by its doctors.

      Bottom line: they have met the enemy, and he is them.

    20. Re:Transferability by recrudescence · · Score: 2, Insightful

      actually, you're almost there.

      The conservatism in the medical sector is so extreme, that even when a new technology appears, the old technology is *still* retained, usually for legal purposes. An example from my hospital for instance, it used to be that blood results would arrive in small pieces of paper that a secretary would affix to a special page with in-built stickers on the back of the patient's notes, and the doctor would inspect and sign it there. Other than calling the lab in very urgent cases, that was the only system to check bloods, so the reports were delivered asap. Now the blood results are computerised instead, meaning you can look them up on a screen rather than wait for a secretary to affix them to patient notes when the reports arrive. As a result, the delivery of the paper reports is less urgent and takes days. However, the doctors are now responsible to MANUALLY COPY all results from the computer screen, into a page on the back of the notes, which can take several minutes. Then the old-style paper reports *still* arrive, and the doctors have to spend several minutes again signing them to prove that they have been inspected (even though they have already manually copied them in the notes as well). This is done for both legal reasons, and the pretext that the bloods need to be available in time for the ward round in the patient's notes. (ironically, a mobile workstation is used to view the Xrays through PACS though.)

      I don't really blame doctors and nurses that much then, when they appear resistant to new technologies, because in the short term, they're introduced so clumsily that they only cause trouble, and their design isn't always ideal to predict if it will be worth it in the long term. I remember I did a project on the state of computerization of the NHS, and I came across doctors who were adamant computers should be banned from the workplace; except, apparently for "the dot-matrix printers which produce sticky labels with the patient's names on them. Those are a lifesaver!" (sigh)

      The other reason, of course, is that, due to litigation on one hand, and blatant lack of clearly defined job responsibilities on the other, people adopt a 'it's not in my job description' attitude, and require formal training for every minor thing they do. Nurses in my hospital for instance only administer a drug if it's on their training list; any other drug they call a doctor (not that I've had training in administering that drug, but I'm the scapegoat; the patient needs the drug and I'm the last person in the chain.) This attitude makes it particularly difficult to introduce anything new in the workplace, and even such ridiculously "for-justification-purposes-only" training sessions, cost a lot time and money to a trust.

      I am one of those rare breeds of doctors that have briefly gone into computing, in the hope of returning to the NHS and making a difference from the clinician's (rather than manager's) point of view. Alas, I now realise changes are more about politics than about actual progress. There is in fact a wealth of innovative ideas within the clinician collective, which will never see the light of day because applying them would involve inconveniencing certain vociferous individuals for a short period of time.

    21. Re:Transferability by jma05 · · Score: 1

      HL7 3.0 is XML. But not enough adopted it. And it's not all the fault of XML... really :-).

    22. Re:Transferability by AK+Marc · · Score: 4, Insightful

      Seriously - when are you slashdotters going to realize that part of the reason that nobody takes you seriously is because your analysis is so junior high level?

      I have a masters in business. When the people making the business decisions are divorced from the operations of the business, the item that helps them most may not help the company at all. Having seen the results of such decisions, I assure you the consequences are quite real, and because of poor managerial decisions.

    23. Re:Transferability by Grygus · · Score: 4, Insightful

      There's even more to be said for well-written software. What your post boils down to is, "poorly written software will not work as advertised." You're not going to get much argument on that here. The problem with the article (and your conclusion) is that they implicitly assume that all computer-based solutions are equal in quality. Since that isn't true, the analysis is ignoring a crucial component.

    24. Re:Transferability by arth1 · · Score: 3, Interesting

      I would like to see him try to do0 the mapping of a genome with paper and pencil.

      Yes, that would be as unbelievable as designing the Eiffel tower without a computer.
      The number of pieces in the Eiffel tower is in the same order of magnitude as the number of human genes (the bolts can be compared to base pairs). Clearly not doable.

      The old saying that "when all you have is a hammer, every problem starts looking like a nail" is true for computers too. We think of a computer solution first without even considering how something can be done other ways.

    25. Re:Transferability by MattSausage · · Score: 5, Interesting

      As a personal anecdote, computerized medical records most likely saved my father's life.

      He woke up in the middle of the night with unbearable pain in his abdomen, and when he didn't fight my mom about going to the hospital she knew it was serious. Five hours later and untold scans and prodding later (not to mention a significant amount of morphine) they determined a blood vessel leading to my father's colon had been blocked and basically part of his colon was dead or dying. Not having the facilities or expertise to handle the necessary surgery in my mid-size town of Owensboro, KY, they sent him to the University of Louisville Medical center telling us that basically, even done by the best surgeons in the business there is a 3 out of 4 chance he wouldnt' make it through surgery unless it was done in the next few hours. The trip to Louisville takes two hours. Following the ambulance we arrived in Louisville in an hour and a half, and he was in his room and being prepped when the doctors realized they didn't have any scans of his abdomen, the EMTs had left them behind in their rush to get us all there. Faxing them was the only option, and to do that they would have to get in touch with someone in Owensboro, convince them who they were, have them look up the records, and then get them to a fax machine that could handle the scans. It could take another hour.

      Except my mother (who, frankly, is the smartest person I know) insisted that she be given a copy of the CD with all the electronic scans and data the doctors had collected that morning. I thought the surgeon was going to kiss her. 20 minutes later my father is in surgery, and 5 hours after that (or so, it was a long day) he was back out and kept in ICU for two weeks before finally coming home. The doctor had said if he'd had to wait much longer chances would have shot up considerably that my father would have died. So, there is at least one example of how Electronic Medical Records did help a doctor save a life.

    26. Re:Transferability by CAIMLAS · · Score: 1

      Except all those tests are money makers for hospitals. So, in this case, digitization of records and the increase in technology has decreased revenue for the hospitals/doctors (never mind the chart transfer fees they can't charge).

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    27. Re:Transferability by arth1 · · Score: 1

      If they don't save money - do they use the computers in an efficient manner or are they just advanced typewriters?

      They're just advanced typewriters that throw a hissy fit if what you type doesn't match what it thinks you should type.

      Seriously, any large computer system is just glorified storage that has more in common with a black hole than a filing cabinet -- even though you can supposedly search for something, you don't know just in what table a piece of information was entered, or how it was entered (in order to bypass shortcoming with GUIs, field lengths and idiosyncracies). Yes, there may be a line in there that says that your mother had arthritis in the back and your father suffered from podagra, but that won't do the doctor any good if he doesn't know that the doctor who treated your mom abbreviated it "S.RA" and the one who treated your dad never entered a diagnosis but wrote a comment on "pat. compl. on gout pains". So the good doctor is one that asks his staff to print out everything, and then reads through it, looking for something to catch the eye in a way that a SELECT statement never can. Which makes it less accurate than paper files, because with paper, what was entered wasn't modified to fit the fields that existed at the time -- the input is accepting, not restricting.

    28. Re:Transferability by sheph · · Score: 1

      I see the benefit in having your records readily available, but with security being what it is I'm not sure it's worth it. If we were to do that I don't think medical records should be transfered over the Internet. It should be a closed system with hard links between locations, and never connected to the Internet. I might be alright with it then.

      A system is only as good as its design. I've seen many cases where an outside company is called in to put in a system. With no knowledge of the workflow, or processes in place at the organization they have a billion meetings trying to discover what they need to know to build a quality system. None of the stakeholders can agree on what should be done, so there is compromise every step of the way. When the organization finally gets their system they hate it because it doesn't do what they need and what it does do is not efficient. Yes it's cheaper to have an outside company come in and build it, but in the end you always get what you paid for. I suspect it's no different in the medical industry. If you want a quality complex system it takes years of dedicated development, and an in depth knowledge of the internal workings of the company. You can't hire a team of monkeys to come in and stick a bunch of building blocks together.

      --
      I don't believe in karma, I just call it like I see it.
    29. Re:Transferability by Anonymous Coward · · Score: 0

      No, they succeeded at helping the accountants and managers. I would say if the system does exactly what it was designed for then it is a success. Just because helping the actual doctors was out of scope doesn't mean it automatically failed. In IT we work with all kinds of applications that are focused on only a small subset of the employees (like accounting and HR systems) These systems might intercommunicate (Like HR feeding back to a payroll system) but they are not designed with that as their goal.

      If you want to help the doctors then get a system designed for doctors.

    30. Re:Transferability by Anonymous Coward · · Score: 4, Insightful

      Wow, I so just NEVER post anonymously but... I work at a healthcare company. Specifically, a Healthcare IT company. A very big one. One which develops an elctronic medical record, amongst other things, and is joined at the hip by several hospitals (we are a non-profit, they founded us)...

      Think about the flaws in how the government works, and you can start to grasp the problem. These institutions are setup, not to make a profit, but to do a job. To that end, they are going to do that job... come hell or high water. Its noble, its great, its a bureaucratic wet dream. They even budget the same way. In fact, last year is the FIRST TIME IN MY CAREER that when the end of the fiscal year rolled around, we did NOT hear talk of needing to use up the rest of our budget before we lose it.

      The problem is, that they create a whole bunch of fiefdoms, give them a mission, and then let them just creep that mission over the years. New servers, new disaster recovery plans. More security.

      Then we interact with government, and everyone has a stake in healthcare so...more regulations? Ever heard of hippa? No? Then you don't work in healthcare. We have yearly ethics classes, a whole department whose job is to police ethics internally. Increasing regulations seem to push us forward a lot.

      We are a mini-government. In many ways, I like it. How many other workplaces have an appeals process on disciplinary that can go all the way to an employee review board of randomly selected employees from other departments? We essentially have a jury system built into the company!

      And while governments have a feedback loop through voting, we do too. We have the board, which is chaired by big wig stakeholders, many of whom are hospital administrators and power player doctors. They allocate our budgets, they push agendas... which feed through us, and back to the hospitals, and their management.... which is our feedback loop.

      Its a labyrinth of departments, groups, teams, on down the line. An undulating stack of bureaucrats each moving forward, increasing his scope. Every department knows money is being wasted. However, its the other guy wasting it, because we are on a mission. We have to deliver this service right here, no matter what it costs.

      I wish I had time for more but, my group has a mission. Maybe later I can wax poetic about how "middle heavy" institutions like this grow. Remember those articles on the Gervais principal and how it relates to "The Office". Google it and reread it... realize that these organizations work under those dynamics, but remove the "organization falls apart" feedback loop. Imagine that model running its course for the 150 years that some hospitals have been around.

      Of course, theres been corruption too. We grumble about not even being able to take pens or free classes from vendors anymore. A whole host of new policies, all because a couple of guys were scamming contracts. These policies will never go away... only grow. (something which I have seen at 2 of the places that I have worked. In one they were fresh policies from a scandal that happened while I was there, and one from a scandal 20 years prior)

      THAT is where the problem is. This constant slow creep of policies, regulations, departments.

    31. Re:Transferability by Ex-MislTech · · Score: 1

      I think the author of the article is a Phd.

      So while YOU might consider him junior high level,
      I am going to consider you a moron, and his analysis
      has a lot of evidence to lend it credibility.

      --
      google "32 trillion offshore needs IRS attention"
    32. Re:Transferability by Ex-MislTech · · Score: 1

      MOD PARENT UP !

      --
      google "32 trillion offshore needs IRS attention"
    33. Re:Transferability by SerpentMage · · Score: 2, Insightful

      Sorry I am going to disagree here...

      The problem with the IT industry is that it does not solve problems for users. Programmers for the most part have very little domain knowledge, and it shows. About 5 years ago I saw the trend of shifting from general knowledge to specific and shifted to the investment banking industry.

      You might oh you f***d up big time. Ha, on the contrary. I actually got in at the right time. They are now looking for people who can write code and trade. Not an easy combination, but something I acquired and it has paid off handsomely.

      Open source and closed source has plenty of examples of people who know tech, but know squat in the domain. Once at a speakers table I even had one speaker tell me, "oh you can learn a domain in about 8 weeks." Really? Yeah RIGHT!

      When you say, "If you're building a house, hire an architect" I would disagree. I would argue hire a local contractor who has built a few dozen homes. For an architect will cost too much for what its worth. Of course if you are a billionaire, then by all means hire one. Or if you are building something unique, by all means. Otherwise hiring an architect will cause you to overpay and under deliver.

      --

      "You can't make a race horse of a pig"
      "No," said Samuel, "but you can make very fast pig"
    34. Re:Transferability by modmans2ndcoming · · Score: 1

      Menon PTR does a good job of packaging data into PDFs. Most EMR systems are capable of importing PDF data. The process of indexing that data might be manual, or, depending on the quality of the EMR/ EDM system, could auto index the material.

      Your opinion as to the quality of their project staff may vary though.

    35. Re:Transferability by melstav · · Score: 1

      Nope. The current Electronic Medical Record systems are not capable of exchanging information freely. There is no standard data format that everyone can exchange.
      There are a few standards that can package data, but they are not adequately specified for seamless interoperability.
      If you request records, they can print them out quickly for you though.

      Such as HL7 which, from the reading I've been doing is actually quite thorough. And if both sides are using HL7 v3, which is XML-based, you can overcome formatting issues between software packages through the use of XSL stylesheets.

    36. Re:Transferability by modmans2ndcoming · · Score: 1

      30 years of pid based interface messages and some how someone expected HL7 3 to take off?

    37. Re:Transferability by ILongForDarkness · · Score: 1

      But the new systems could make doctors more accurate. Sure a doctor can scribble on a page vary fast probably faster than you can enter data into an electronic form, but ones electronic form will read the same way as the next guys, at least the text will look exactly the same etc. So no more problem with messy handwritting. Then you can also validate things, no more doctor missing a digit on an insurance form and not being able to get the claim. Finally, it is much much easier to do quantitative research against a database of records than it is to do it by having to manually search through paper work. This in turn makes medical research cheaper and adds the potential to look at things more closely, for example is using this drug really better than the surgical procedure? Does night shift have a higher mortality rate because the cases are different (DUI, gunshot wounds etc.) or because less experienced staff tend to get stuck on that shift? Until you analyze the data who knows.

    38. Re:Transferability by hesiod · · Score: 1

      Ever heard of hippa? No? Then you don't work in healthcare

      Ever misspelled "HIPAA" as "hippa"? Then you don't work in health care either. It's a pet peeve of many people in that industry. Before you go off about how much you know about health care services, you might want to make sure you don't make yourself look like a moron in the process.

    39. Re:Transferability by hesiod · · Score: 2, Informative

      Cool story bro, though that probably wasn't an EMR: just some DICOM images. Of course I can't say that with full certainty, just with what I know from working IT in a hospital. But it's still cool that it helped save his life.

    40. Re:Transferability by SenFo · · Score: 1

      Exactly...it's the same thing I've seen over and over, again. I've worked on a number of projects, from commercial contracts, to government and health care projects. By far, the ones that have been the most difficult to work with are the clients that have strict bureaucracies (read government and health care). I'm sure hospitals are very similar, in this sense. It's incredibly difficult to convince streamlining a workflow with people that have become accustomed to a strict bureaucratic process. In many peoples eyes, the process is gospel: ye shall not challenge thy process. As such, when software replaces antiquated systems, they implement the same failed processes that existed before they got there.

      In order for a new system to be successful, people need to learn to accept change.

    41. Re:Transferability by Anonymous Coward · · Score: 0

      can't tell if you're joking, but I can tell you that's exactly how data (or at least what I've observed) is stored using Cerner - http://www.cerner.com/public/ Granted not all fields, but too many for good measure.

      But, hey, Freedom is a blob.

    42. Re:Transferability by jhoegl · · Score: 1

      To get a PhD you must write a 500 page paper on something in your field. 500 pages... so 80/20 rule. So, about 80 pages are actual information and the rest is B.S. PhD.... if you know how to Bull shit, you can get some more letters after your name. WOOO!

    43. Re:Transferability by tsstahl · · Score: 1

      Are you me from a parallel universe?

    44. Re:Transferability by orangedan · · Score: 1

      To view the parent's words in another way that might hit home for /.'ers is that we always complain that tech decisions are usually made by uninformed, technically illiterate people. By the same logic, let the business decisions be made by business people.

      That said, the world isn't so simple, and these decisions really need the input of several viewpoints.

    45. Re:Transferability by Anonymous Coward · · Score: 0

      I would laugh if it didn't hurt so much.

      We see this a lot. Not only that but... time goes by. We look at all the various flavors of OS we support and try to cut back. Try to push people forward. Machines still running ancient versions of redhat that are well out of support. We call them on it. They call the vendor for their app. The vendor says they can't upgrade or they lose support, and of course it is an FDA certified app..... eventually it just dies and well... is it any wonder we still run OpenVMS systems?

    46. Re:Transferability by Anonymous Coward · · Score: 0

      This is why I always tell people that the TRUE key to success in any new IT implementation (such as an ERP) is OCM (Organizational Change management) ... but that if the new system is judged to be a failure, the TECHNOLOGY will get the blame while the OCM folks quietly slink out the back door.

    47. Re:Transferability by Alpha830RulZ · · Score: 2, Insightful

      The systems aren't put in help the doctors. (...). But that's not what the systems are. 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.

      I'm going to argue just a bit. My wife just went through breast cancer this summer. The records, MRIs and actions that took place -were- electronic, and at more than one point -were- used to facilitate actions between a group of physicians that were part of her care. Meds were ordered electronically, and the new records generated from the process are all electronic. She had MRI's taken across town, and the pics were sent in electronic form to her surgeon and oncologist, who conferred via something like Net Meeting on them (don't know if it was net meeting or what, just that they had a con call and viewed the films together). One of the challenges that was presented was that she had old records from a prior incidence of cancer ten years ago, which are all still on paper/fiche. These had to get pulled and sent via courier. Overall, the experience that we had was highly electronic, and by and large was pretty efficient.

      I won't dispute that a large amount of the systems are oriented towards capturing billing information. This is necessary because of the US's insistence on individual insurance plans, so for every action, someone has to get billed, which means a record has to be made of the actions. I think these systems still arguably help patient care, because they do still aid the physician and nurses in capturing the information, which would likely be slower if they had to use paper. I think it's a flaw to criticize hospital administrators for designing/using these systems, though. The hospitals are just following the mandate of the compensation system that they work under in the US.

      --
      I was taught to respect my elders. The trouble is, it's getting harder and harder to find some.
    48. Re:Transferability by eightball · · Score: 1

      Sorry you are off by 3 orders of magnitude (2.5 million rivets vs 3 billion base pairs). Also, since the tower has four-fold symmetry and each corner also has right-left symmetry, you can effectively lower it to 300k sets (4 order of magnitude off).

    49. Re:Transferability by JWSmythe · · Score: 2, Informative

          But, those records weren't available to be sent over when required. Your mom did it. If she hadn't, regardless if they were paper or electronic, they would have gotten there too late.

          That's a change that has to happen. I'm starting to build my own patient file on myself. Every time there's a test, or anything more interesting than "I have a cold, gimme some antibiotics", I get my own copy of their records. Unfortunately, I didn't start doing this years ago. I've tried to track down some records from 8 years ago, and they can't be found. It's not just that it fell outside of their document retention policy, but the doctor is no longer practicing. The lab was a mobile unit, who I don't know the name of. So, those records are lost, even though they'd be great for identifying change over time.

      --
      Serious? Seriousness is well above my pay grade.
    50. Re:Transferability by Anonymous Coward · · Score: 0

      Sorry I didn't have time to check my state imposed acronyms as I was furiously typing while trying to get out the door this morning. I am not some administrator who gets a stiffy for this stuff, I know about as much about it as I need to to do my job, and thats not much. I mostly hear it in conversations and the yearly refresher training on how we are all supposed to be careful with patient data.

      Though, thats all hipaa is to me. This big thing outside that everyone talks about. Its one of the forces that shapes our policies. I am glad that I don't need to understand it personally.

      but what do I know? I only work here. Feel free not to listen to me, management certainly doesn't. Shit, I am just now entering pilot phase on a project to implement what I suggested and had rejected at least two years ago, the project itself was re-proposed a year ago, and took 6 months to get started, and now like 3 months to get to pilot phase.

      The whole project would have been about two weeks work for 3 people if it hadn't been for the need for business cases, discussion, approvals, meetings, and miscommunication.

    51. Re:Transferability by ColdWetDog · · Score: 1

      You forgot the other problem. The healthcare system in the US is crazy complex and structured on historical grounds rather than logical or systematic ones. So it's chaos.

      When you computerize chaos you get - wait for it - computerized chaos. Not an improvement in the process, just another layer.

      --
      Faster! Faster! Faster would be better!
    52. Re:Transferability by Will.Woodhull · · Score: 1

      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?

      No.

      Even if both healthcare facilities are using the same software, the data transferred is going to be incomplete and unreliable. First, medical imaging has become a significant player in many diagnostic workups, but medical imagery data is bulky and formats are proprietary to the imagery machine (not the facility's medical management software, which probably cannot access it either). What is going to be transferred is the report about the image, which does the new physician no good at all when he is wanting the raw image as a baseline. So your basic MRI data and digital xrays are not going to transfer in a meaningful way.

      This is also true to a great extent to laboratory findings, since even when the same equipment is being used, different laboratories use different calibration procedures resulting in different ranges of normal values. One facility's dangerously low Hgb/Hct values may be within the normal range of another facility. There may even be differences in the way basic vital signs (temperature, pulse, respiration, blood pressure) are presented, making even these unreliable.

      Yet the more common case is that each facility will be using software from different vendors, or incompatible versions of the same vendor's software. Take the above mentioned problems and increase them exponentially. And remember, an error in some of the details, like drug allergy information, may cause the patient's death. But which of those details is critical is going to be different for each patient, so you can't afford to err on any part of the transcription.

      Health care reform is going to require some high level work: forcing standards on the software developers similar to the SAE standards for the nuts and bolts that hold your Chevies and Fords together [obligatory car analogy: done]. There needs to be a normalized way of reporting all lab results, for instance. There also needs to be common data centers for all bulky medical data like raw MRIs and digital xrays. These can never fit within a healthcare facility's basic IT structure: safe and efficient handling of these terabytes needs to be done on a regional basis.

      However all this means applying FOSS type thinking (TCP/IP, HTML, CSS, similar standards) to the healthcare industry. But that industry is now completely profit driven and sees the Microsoft model of proprietary formats as the way to best monetize the fine art of mending sick and broken people.

      I am not saying that the healthcare providers are at fault. Physicians, nurses, and allied health personnel are performing artists who have little interest and no training in managing the theaters they work in. It would be easier to teach ballerinas how to work up the cost estimate for a ten week tour of Swan Lake than to get a good physician or nurse up to speed on digital data management. The fault lies squarely on those who have chosen healthcare administration as a career. We need persons with the same kind of mind set as civil engineers and architects in these roles, but mostly we have been filling these roles with persons who are oriented toward maximizing short term profits (to earn their bonuses, or position themselves for the crossover step to a higher job with a pharmaceutical house, etc).

      </rant>(Sorry, 35 years of increasing frustration with a sick system may have introduced a little bias toward the end.)

      --
      Will
    53. Re:Transferability by Anonymous Coward · · Score: 0

      Something *original* in the field that is peer reviewed by others in the field who have to accept that it's up to their standard. It takes an incredible amount of research to even get to the stage of writing a PhD thesis. While a PhD is not the be all and end all, to trivialize it to a percentage of the thesis page count is totally a misrepresentation.

    54. Re:Transferability by Strange+Ranger · · Score: 1

      Cool story. Glad your dad is ok.
      You know the most striking thing to me in this story is the absence of a helicopter.
      If Owensboro is big enough to have it's own hospital it's big enough to have a LifeFlight Helicopter. I've seen them in some pretty rural areas.

      --

      Operator, give me the number for 911!
    55. Re:Transferability by iluvcapra · · Score: 1

      Mod parent Up

      --
      Don't blame me, I voted for Baltar.
    56. Re:Transferability by Archangel+Michael · · Score: 1

      Having both a degree in Busineess Admin, and having worked in IT for over 25 years, I can assure you, you are dead on.

      The problem isn't just with Administration, though a lions share of it is, the problem also lies with IT departments not understanding business at all.

      This is where a CIO or CTO or both are needed as bridges between IT and Business services (accountants, finance, records etc).

      Yes, IT is often "magic wand" stuff, and what we can do is sometimes amazing.

      The whole problem is, you have people who are not really "technical" (doctors, nurses, staff) being required to use highly technical and often complicated computer systems, that are difficult even for trained people to use correctly.

      What usually happens is either you're good at the Tech, or you're good at patient care. Guess who keeps their job or promoted when the time comes?

      This affects patient care in ways nobody really can understand, unless you're actually skilled in both. The geeky nurse ends up sitting clicking away at the mouse and keyboard, filling in all the data points, and looks great from Business Services, but patients aren't actually getting the care they need.

      What I don't understand, is why there aren't computer terminals in every room, with touch screens or nurses walking around with PDA type devices with check boxes to check off as they make their rounds.

      The main screens for these need to follow KISS, so that anyone can read, and check things. They shouldn't be designed for every off case, and all options available at all times.

      The inefficiencies of modern info systems always astound me, often making more work than they save. They should save time, and be more accurate most of the time than not. Any system that fails on both accounts is a failure, regardless how much data is collected.

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    57. Re:Transferability by goarilla · · Score: 1

      a phd is not a masters' degree with an end year thesis
      a phd still requires a professor that wants to promote you and you doing research
      and delivering results periodically so they can be reviewed by your peers and promotor

      if they're not happy with the results then you're not getting your phd!
      don't dismiss it because you blew your chance

    58. Re:Transferability by Jah-Wren+Ryel · · Score: 1

      The thing I like best about your story - the medical records were directly under the control of the patient.
      Sneakernet is great when the person wearing the sneakers is personally invested in the data being transferred.

      All of the privacy problems with electronic records pretty much go away if we put the responsibility for keeping track of the records in the hands of those who have the most to lose (as in lost privacy if they are disclosed to the wrong people and lost life if they are not disclosed to the right people).

      --
      When information is power, privacy is freedom.
    59. Re:Transferability by Anonymous Coward · · Score: 0


      The number of pieces in the Eiffel tower is in the same order of magnitude as the number of human genes (the bolts can be compared to base pairs).

      There are 3 billion base pairs in the human genome. The number of bolts in the Eiffel tower is not in the same order of magnitude. I understand your point, but your example is flawed.

    60. Re:Transferability by scorp1us · · Score: 1

      I am actually employed by an effort to do just this. IHE is an effort to use standard interfaces to facilitate patient management.

      The thing you (and other /.ers) don't appropriate is how our current situation came to be. It evolved organically, bottom up. My company specifically makes products to enable data sharing. The problem is every hospital has different software packages and does it in slightly different ways. This IHE is the first attempt (that I know of) to give some standard at all points in the clinical health setting. We *are* using SOAP and XML (today), but are encumbered by legacy databases, formats, and protocols.

      But what is worse, the Federal government in initiatives being advanced right now, are not using the IHE standards. So we already have fragmentation. But we'll get things there.

      Adding to the complexity is access isn't just like using a web server. We have HIPPA to worry about. And a simple thing like getting your doctor who is affiliated with the local hospital is way more complicated than just installing a VPN and some certs. The coding schemes may not match up and have to be translated between offices, and then there is the whole security thing. Just because Dr Brown and Dr Stewart are linked to the local hospital, doesn't mean that Dr Brown should have access to Dr Stewart's files... but he might.

      My company is actually achieving cost savings for our customers, but so far it is limited to linking similar geographically disperse systems, which, actually happens a lot in countries with socialized medicine. We will be able to do the same in the US once IHE has matured. Several areas are functional now, but several are under development.

      --
      Slashdot's rate-of-post filter: Preventing you from posting too many great ideas at once.
    61. Re:Transferability by greyhueofdoubt · · Score: 1

      having a doctor or nurse putting in billing codes will only slow down the process.

      It's worse than that. I used to work for an insurance company* and although I can't talk about specifics, I would see errors all the time. For instance, there are several different diagnosis codes for neck pain; the differences involve severity, location, cause, etc. Chiropractors (they were the worst offenders for some reason) would send in claims forms that had the 'wrong' code entered- what I mean is that an insurance plan might cover a specific back problem but not the general, catch-all code for 'back pain' or whatever the office entered. Bam, claim denied.

      There are also codes for treatments. Maybe you take your kid to get a scheduled check-up and instead of a level 1 or 2 doctor consultation code you get the well child exam code. Bam, claim denied. Or you take your kid in for a check-up and the office puts in the level 1 doc consult but leaves the diagnosis blank if there's nothing wrong. Bam, claim denied.

      A big part of why I left was my misgivings over the ethics of the job. On the surface my job was to correct transcription errors or omissions on claims forms, but really what I was doing was covering the companies ass for each denied claim. I would see 5-figure bills come through and know that they were going to be denied for something as trivial as a missing drug code.

      -b

      *"which insurance company?" "a major one."

      --
      No offense, but I've stopped responding to AC's.
    62. Re:Transferability by SonnyDog09 · · Score: 1

      Not quite 30 years....HL7 has only been around for 22 years or so...I remember the 20th anniversary happening. But there are working interfaces that appear not to have changed for at least fifteen years. They've been doing this stuff before you young whippersnappers could spell "ex em el"....besides, it's not "transferability", the correct word is "interoperability" ... now get off my lawn.

      --
      Your "fair share" is NOT in my wallet.
    63. Re:Transferability by benjamindees · · Score: 2, Interesting

      I agree completely that accountants have screwed up both IT and many business processes, in lots of industries. I see tiny little microcosms of the fiscal and accounting scandals everywhere I go. It's one thing to track costs and enable billing. It's quite another to design an entire company's information technology around some vendor's proprietary system that's designed only to do one thing well (financial engineering) and not to be interoperable.

      I have told every one of my clients "invest in IT to improve efficiency". And what have they done? They hire an IT guy, stick him in a broom closet, hand him the latest version of Microsoft Whatever(TM) and tell him to use it. Few take it seriously.

      One of the major problems is that really implementing IT to improve efficiency requires change. Having domain knowledge means that you aren't taken seriously by the IT people. Having IT knowledge means that you aren't taken seriously by those with domain knowledge. Having both means you aren't taken seriously by anyone.

      Telling everyone that they need to re-think major processes from scratch gets you laughed out of the room. At this point, IT has been sold for so long as a magical cure-all that will make the world a better place that you basically have to sell IT as a magical cure-all if you want your solutions to even be considered.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    64. Re:Transferability by drosboro · · Score: 1

      Umm, sorry, but your numbers are a bit off. There's 18,000 pieces or so in the Eiffel tower - which is indeed in the same order of magnitude as the number of human genes. But there's a lot of the genome that falls outside those genes, and there's a lot more base pairs per gene than bolts per piece. According to the Eiffel tower's website, there's 2.5 million rivets holding it together. There's 3.2 billion base pairs. Not exactly a comparable situation.

    65. Re:Transferability by Anonymous Coward · · Score: 0

      Thanks to a little thing called symmetry made the Eiffel tower is much much simpler to design than you are making it out to be. A better example would be the designs of the Saturn 5 systems with over a million parts. Even then, that pales in comparison of mapping a genome by hand.

    66. Re:Transferability by b4upoo · · Score: 1

      I think that computers are helping in health care. As an example whenever I get a script both my doctor and my pharmacy run programs that detect any conflicts or hazards in my medications. That is a life saver and clearly superior to an over worked doctors memory.
                        I also have both knees replaced by artificial joints. Parts for those joints are machined during the surgery as they are custom fit. Computer controlled machines create those parts. Can you imagine if you had to remain under anesthesia while a machinist messed about trying to machine a good fit for those joints. As it is a double knee replacement took over six hours under anesthesia which is life threatening in itself.

    67. Re:Transferability by Anonymous Coward · · Score: 0

      oh, i see you've transitioned to sap.

    68. Re:Transferability by coolsnowmen · · Score: 1

      And pass qualifying exams and meat other requirements dictated by the other phD at the institution.
      Examples:
      1) have an accredited journal accept a paper of yours take and pass 30 classes)
      2) take&pass 6 classes and write 5 journal accepted papers in rated journals

    69. Re:Transferability by Grishnakh · · Score: 1

      As the husband of a helicopter pilot, I have to agree. Why drive someone in critical condition 2 hours by ambulance when helicopters are so much faster? Even if it has to fly from Louisville, it's probably significantly faster.

    70. Re:Transferability by hackingbear · · Score: 1

      Your mom could have taken a copy of the real film (if done in X-ray) like patients around the world who carry their own records to the doctors (I did that when I was not in this country.) If the image is in MRI or other new computerized scans, the output is digitized, it has nothing to do with the Electronic Medical Record we talked about here. EMR is about sharing of medical records, don't confuse it with a CD -- or a wagon of tapes -- with digital data. In your case, EMR is obviously not used.

      In this country, it is the legal liability that prevents medical record sharing -- in paper or electronic -- and repeats testing. Doctors will not let you automatically take all records or share all records with other doctors in fear of being accused of errors. Similarly, the best assurance of accurate diagnostics is up-to-date testing. (I used to switch several doctors for the same condition, and all of them repeated the same test even if I presented the previous test results.)

    71. Re:Transferability by Anonymous Coward · · Score: 0

      s/fiscal/financial/

    72. Re:Transferability by demonlapin · · Score: 1

      Patient sticky labels are a little piece of heaven. Compared to Address-o-Graphs... well, there is no comparison.

    73. Re:Transferability by AK+Marc · · Score: 1

      As a personal anecdote, computerized medical records most likely saved my father's life.

      I guess I'm just a cynic. Your story was about how you should take your records with you and if you had to rely on computerized medical records to be shared between providers, you father would be dead. The sharing wasn't there. It was taking your records around with you everywhere you go, the exact opposite of electronic records, that saved his life. Whether hard copy film or soft copy images on a CD, they still had to be carried by hand or he would have been dead.

    74. Re:Transferability by AK+Marc · · Score: 1

      No, they succeeded at helping the accountants and managers. I would say if the system does exactly what it was designed for then it is a success. Just because helping the actual doctors was out of scope doesn't mean it automatically failed.

      Except this study says they didn't help those they were trying to help. So you are wrong on that point. Whether it is an automatic failure or not, it is an actual failure.

    75. Re:Transferability by Pentavirate · · Score: 1

      That is a fantastic story. My family has had great experiences with hospitals using EMRs in the past. Particularly, the St. Vincent Hospital system in Portland, OR was fantastic. My wife had to have some MRIs and CT Scans and then talk to specialists. As soon as she registered at the first doctor she saw in the system, she never had to re-register at any of the other doctor's offices. They always had all of her medical information that any of the other facilities in the system had including the MRI and CT Scans. It was a dream from the patient's standpoint.

      Other medical systems have had horrible EMRs. We've always tried to get copies of all medical records for the family wherever we've lived and it's appalling how many have no capability to give it to you in an electronic form so we have a file folder 12 inches deep filled with paper copies which are almost as useless as not having any at all because they're in a format that's extremely hard to find information and to look back over time to identify trends.

      The one good thing the government does is establish standards. They've been doing it at least as long as when they established a standard size for railroad tracks in the 19th century. If the government can establish a standard for all doctors/medical facilities to interchange information in an electronic form, it would make gathering and storing information for a patient extremely easy and it transferring information to new doctors and facilities extremely easy. The biggest problem with the current EMRs is the lack of standardized interfaces. If the government can facilitate that, we'd be light-years ahead in being able to manage our own health care.

    76. Re:Transferability by Anonymous Coward · · Score: 0

      HL-7 (which sux IMHO) will talk between systems. A pain to set up -but we use it where I work.

    77. Re:Transferability by Dragonslicer · · Score: 1

      500 pages... so 80/20 rule. So, about 80 pages are actual information and the rest is B.S.

      Maybe you should consider a Ph.D. in mathematics

    78. Re:Transferability by demonlapin · · Score: 1

      Most of what you say is totally true, but DICOM does work for images. It's about the only electronic health record system that transfers in and out well.

    79. Re:Transferability by sjames · · Score: 1

      Typically management will like the "prettiest" software. Typically the prettiest software got that way because that's where all of the development effort went. The ones where the primary effort was to be fast, reliable, and useful didn't spend as much time on pretty.

      Thus management will typically select the bug ridden inefficient but pretty package over the fast, reliable, and useful, but not so pretty one.

    80. Re:Transferability by Hognoxious · · Score: 1

      Firstly, he was quite clearly talking about slashdotters, not the author.

      Secondly, a PhD in what? Last time I looked, they were subject specific rather than a mark of omniscience.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    81. Re:Transferability by icebrain · · Score: 1

      "I have a cold, gimme some antibiotics"

      Why are you getting antibiotics, which kill bacteria, when colds are caused by a virus? The antibiotics aren't going to help; if anything, you're just wasting up the doctor's time, your time, amd your money, and contributing to the spread of antibiotic-resistant bacteria.

      --
      The meek may inherit the earth, but the strong shall take the stars.
    82. Re:Transferability by JWSmythe · · Score: 1

          {sigh}

          I don't actually say that. I give the doctor the symptoms, and he gives me what's appropriate. But I was saying, I'm not tracking those. Results to tests, and other interesting things, I'm recording. If I have a cold, and a doctor gives me something, and I'm better in a week, no one cares after that. If I'm still taking them, or have recently taken them, I have the bottles to bring with me to show "This is what I've been taking, and it isn't working", but that's never happened with me.

      --
      Serious? Seriousness is well above my pay grade.
    83. Re:Transferability by doesnothingwell · · Score: 1

      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?

      After a four year lapse my hospital remembered all my outdated insurance data and almost none of my medical data. The priority seems to be money and how to keep the profits flowing. No?

      --
      They can have my command prompt when they pry it from my cold dead fingers.
    84. Re:Transferability by modmans2ndcoming · · Score: 1

      your mothers experience is an example of WHY the systems cost more... idiot users and idiot systems that let idiot users behave like idiots.

    85. Re:Transferability by arth1 · · Score: 1

      You are (incorrectly) applying the qualifier of the main sentence to the parenthesed sub-sentence. If I write "The dog looked ugly (and its owner was pale)", it doesn't imply that the owner was ugly.

      To elucidate: The claim about order of magnitude was made for the number of pieces in the Eiffel tower, not the number of rivets/bolts.

      As for excluding the symmetrical faces of the Eiffel tower as redundant, surely you then also want to exclude all the redundant and repeating parts of DNA? Just for consistency?

    86. Re:Transferability by jsebrech · · Score: 1

      The systems aren't put in help the doctors. They are put in by the non-medical managers to help their jobs.

      I've seen this in action now several times, even at my current job. Management often don't understand the job of the people they're supposed to manage, so they introduce these systems that cater to managers in the hope that it will make up for their lack of understanding. Quite often it doesn't help. This is why companies that require their management to regularly work "on the factory floor" generally do better.

      Another big problem is misapplication of tools. Using software aimed at one problem domain in a closely adjoining problem domain might not be a good solution. It's like using the wrong type of screw driver. "It turns screws, that's good enough" doesn't cut it in the real world.

      Then again, much business software is designed without really understanding what it is that is supposed to be done with the software when it is finished, mostly because the problem domains are heavily underestimated. I've had to fight epic battles to actually get to speak to end users before I start on the functional design of an app module. The only constant is that users will always tell you some new aspect of the problem that you didn't know about yet.

    87. Re:Transferability by jsebrech · · Score: 1

      By the same logic, let the business decisions be made by business people.

      What's a "business" person? What knowledge falls under "business"? There's no such thing as a business decision. There are H.R. decisions, product strategy decisions, accounting decisions. But these are all disparate domains with specific knowledge. It's like saying "hey, the decision has to be made by an I.T. person". What good is it letting a sysadmin decide on the development framework of a new application? Might as well let a "business" person do it. Odds are their choice will be just as good (or bad).

      By which I only mean to say that the problem with modern business is too many people knowing too little having too much decision-making power.

    88. Re:Transferability by eightball · · Score: 1

      I did get distracted by the switch from genes to base pairs. However, you did make a direct comparison between base pairs and [bolts], so I did not apply the qualifier to the wrong part of the sentence, but I did perhaps only address a side point.

      As explained by drosboro, comparing a hunk of iron (which are almost certainly duplicated elsewhere) with a gene is not a valid comparison when we are talking about complexity. I don't think anyone knows how many parts are in the Eiffel tower, however I think it is likely that the bolts are if not the most numerous, they are at least fairly close in number to the most numerous.

      I have no problem with excluding the redundant and repeating parts of DNA. Your problem is that while I can trivially identify where most parts are transcribed on the superstructure of the Eiffel tower with a minimum of structural engineering knowledge, you would have to transcribe all of the base pairs to identify the parts you don't need to map (or come up with a protocol that is sure to win you fame and fortune (and no fair using a computer :)).

    89. Re:Transferability by Duncan+J+Murray · · Score: 1

      As a physician who has worked at several hospitals, I would be inclined to agree with you.

      A distinction should be made between a computer system designed to improve patient care, and one to save money. One may lead on to another, but they aren't the same thing.

      The problem, as I see it, is that computer systems are designed without enough consultation or observance of the people using it. A computer system is installed in order to solve a problem, but without speaking to those who will be using the system, it will never solve the unknown problem.

      In the UK, the hospital doctor's time is extremely limited. We want to see relevant information immediately, without having to spend time doing a manual search. In the past, this was achieved by getting the most junior doctor to put the elbow work in to preparing the information for the seniors to view. Nowadays, with effectively less doctors around (i.e. doctors not working 100 hour weeks anymore) with higher standards of care expected, efficiency has to come from somewhere. I would say that computer systems make a huge efficiency saving in my daily work. Where previously I would have had to find and obtain physical X-rays from the department, collate them, and take them to the ward, and then return them, now I can call them up on any computer terminal. The same applies to blood results. The potential for the system can go much further than is realised now.

      The problem is that we are not consulted on what we need the system for. Most systems are primarily for the use of junior and middle grade doctors to obtain information on their patients (usually only more experience nurses have access to and interpret radiology or pathology results). Consultant clinicians usually rely on their team to provide the information to them, but they also, on occasion (for example clinics) need access to the same information. And yet, I have never been consulted or shadowed regarding the development or use of these systems. From my perspective, this is a conversation that happens between the managers and the IT department.

      At a hospital I worked at recently, a new system was introduced for electronic discharge summaries (paperwork completed by the doctor, which gives a summary of the admission and is sent to the GP/community practitioner). I received an email asking for personal feedback on the system _after_ it was put in place. I wasn't able to give personal feedback, either, because no one in the department had the time to speak to me. The change in the system was disastrous - it was a completely new system which was not intuitive to the doctors who needed to use it. The extra time and stress on the doctors which resulted, added to the risk to patients and detriment of patient care in convoluted ways (think of the butterfly effect).

      In the future, I see the computer system eventually becoming a true way to improve patient care. It will do this be reducing the amount of admin work and inefficiencies in the clinical workers day, allowing more time to see the patient, think about the patient and discuss the patient with colleagues. Just in case anyone reading this is happening to be working on the NHS information system here is what I would like to see: (ideally, of course)

      1. Instantaneous access. With this comes intuitiveness. Every second wasted is another second lost looking after my patients, and can be crucial in life-threatening situations.

      2. 100% reliable.

      3. Comprehensive. The more I can access, the less time I will waste using other systems. I want to know the patient details, ward, BP, pulse, respiratory rate, temperature, oral intake, bowel motions, urinary output, any other parameter we might be measuring (see 4) medication (and all their changes and whether they were given), clinicians notes (both recent and old), clinical letters, allergies, radiology - everything!!!!!!

      4. Flexible. Hospitals take in everyone with any complaint, and medicine is pretty much infinitely complex, and continually

    90. Re:Transferability by drfreak · · Score: 1

      A lot of people still use HL7 2.4 because they don't want to switch to XML, but the format is not the challenge. The issue is the receiver's interpretation of the data.

      For instance, one EMR puts the doctor for an Appointment in one HL7 field, and the system it sends to looks in another. These are the sort or impedance mismatches I work on every day as a developer. The issue is really healthcare-wde, not just EMRs. ANSI transactions (such as 837 claims) are hugely open to interpretation. One workaround a lot of entities have come up with is to write up a "Companion Guide" which lays out what they expect in each data element.

    91. Re:Transferability by CAIMLAS · · Score: 1

      You're telling it straight. I was the sysadmin for a small hospital - pretty much the only person who took care of servers and workstations - and I came in several mornings (well, on two separate occasions) to find new systems (and their respective vendors) in "my" server room. Apparently this-or-that department needed something and paid for it, and didn't let me know. There was very little I had any control of there, and despite the title and job description, the institutional attitude was "let me have my WeatherBug on my computer, or you'll get it from the higher-ups". And that's ultimately what happened, I think (more or less).

      Having an IT Manager who's only qualification for the position was holding the position, and some secretarial work *cough* years ago probably didn't help. God I'm glad I'm not there, even though it's tarnished my record seemingly permanently.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    92. Re:Transferability by dave87656 · · Score: 1

      In Germany, the health care system is actually pretty efficient. You have a standardized card which all the insurers use. All the doctors, hospitals and other providers are linked and there is a standard reader for the card.

      I had a chance to compare the two systems once. I went to the emergency room in Germany late at night. Within a few minutes a nurse put me on a gurney, brought me to a doctor and, while I was being treated, asked who my insurer was and took my card and information. I was sent to radiology, back to the doctor and was finished in less than an hour.

      One time in the states, I also had a nightly visit to the emergency room. First, I had to call my insurer to get the okay that I could go. I was on hold for 20 minutes and decided to just go and risk having to pay for it my self. I didn't hang up, I just left the phone on the table. I drove to the hospital. I filled out forms with the same personal information three times, no exaggeration. After a long wait of over two hours, I got to see the doctor for five minutes. The whole process took three hours. When I got back home I was still on hold waiting for the next available representative to take my call.

    93. Re:Transferability by CAIMLAS · · Score: 1

      And it's at least another level of magnitude to try and reverse engineer something (vs. engineer it). Ever work on a vehicle? Yeah, it's much, much easier to put it back together once you know how it goes together than it is to take it apart.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    94. Re:Transferability by Anonymous Coward · · Score: 0

      Hey, I work in NHS IT too, and that's exactly my experience. Galling, ain't it?

      We've had three big successes in recent years - PACS for digital X-rays, which is *excellent*, a similar system for cardiology, and a little home-grown replacement for an admin package that was failing to scale.

      We've definitely had more expensive failures.

    95. Re:Transferability by MattSausage · · Score: 1

      Well, I honestly appreciate your cynicism, being an avowed cynic myself. But the fact I was hoping to point out was that these images and records were digital, and were easily copied and handed to my mother. The tech simply had to type '2' instead of '1' in the number of copies field. Copying Xray film or hardcopy cat scan results is onerous when under a time constraint. Digital records are copied in minutes or less compared to paper records where someone has to stand over a copying machine and can do nothing else while they wait.

      Plus a CD fit in my mom's purse while xray film and a file full of paperwork most definitely would not. Sure it's not a nationwide database of info based on an RFID tag in your wrist, but I cannot see how paper records are preferable in any circumstance unless you're worried about ID theft. But even so, keep them on a CD or Thumbdrive they are just as safe as any paper record.

    96. Re:Transferability by MattSausage · · Score: 1

      That would be a question for whoever arranges the transport I suppose. Knowing the doctors at this particular hospital, they expected him to die anyway and didn't see the need. And for what it's worth, I had NO problem at all with the EMTs involved in the transport, they got there ASAP and were extremely helpful getting my mom where she needed to go while I found someplace to park the car we followed in. I have nothing but good things to say about those EMTs and whatever they make it's not enough in my opinion.

    97. Re:Transferability by Anonymous Coward · · Score: 0

      How often does one switch doctors?
      But the fact that the systems are designed to help management and not the line people is a problem with all businesses not just medicine. Pleasing management while adding inefficiencies to the workers is an Accenture specialty.

    98. Re:Transferability by JimFive · · Score: 1
      You are, of course, being absurdly unrealistic.

      1. Instantaneous access. With this comes intuitiveness.

      This is really two things. Instantaneous access is impossible, ease of use isn't. As for

      Every second wasted is another second lost looking after my patients, and can be crucial in life-threatening situations.

      Looking at a paper file doesn't change this.

      2. 100% reliable.

      Not possible. What you want is "At least as reliable as paper"

      3. Comprehensive. The more I can access, the less time I will waste using other systems. I want to know the patient details, ward, BP, pulse, respiratory rate, temperature, oral intake, bowel motions, urinary output, any other parameter we might be measuring (see 4) medication (and all their changes and whether they were given), clinicians notes (both recent and old), clinical letters, allergies, radiology - everything!!!!!!

      4. Flexible. Hospitals take in everyone with any complaint, and medicine is pretty much infinitely complex, and continually changing. You would not believe how frustrating it is when a computer system has a pre-defined list of diagnoses from the WHO list, and no way to add your own diagnosis - I used to have to phone up the IT department and ask them to put in a new diagnosis, just so I could write a discharge summary!

      These conflict with ease of use/intuitiveness from #1. You can't have comprehensive or flexible and easy to use.

      5. Involved in all aspects of patient care. I don't want the system to just give me information - I want to be able to easily input information. I also want to carry out tasks with the system - referrals, requests for investigations etc..

      Also not possible to make easy.

      The best you can hope for out of an EMR is "better than paper". But, you can only really get that if your formal paper process actually works well. And it almost certainly doesn't. If your personnel followed the formal process to the letter then that process would be easy to computerize. However, what really happens is that the people implementing the process make decisions that aren't formalized all the time. These ad-hoc, one-off, or just undocumented decision making processes are what kill the electronic process. It is nearly impossible to catch all of these exceptions without sitting down and learning the job of each person in the chain. (That doesn't mean the analyst would have to become a doctor, but they would have to become the doctor's scribe for a while.) Even then, the real one-off situations don't come around often enough for them to be captured on schedule.

      And that doesn't even count trying to create a record that is transferrable between entities with completely different informational needs.

      When I was implementing ERP systems it was practically a natural law that if the paper system doesn't work then the the electronic system wouldn't either. Now that I'm working in a hospital, I haven't seen anything that changes that.
      --
      JimFive

      --
      Please stop using the word theory when you mean hypothesis.
    99. Re:Transferability by Anonymous Coward · · Score: 0

      Not as easily as it sounds. First there may be transfer costs. Than there may be interface issues. Than there may be aggragation issues related to the collection of your medical data from four different internal data sets. Not to mention that without tort reform in health care, your new doctor will most likely order a new panel of tests or images just to make sure that liability is covered as best it can be.

      Your data may be yours, but in health care today it isn't about you.

  2. Don't just computerize the process by WuphonsReach · · Score: 4, Insightful

    There's an old saw we had back in the 90s at UPS.

    Don't just computerize a process (or blindly apply technology to replicate an existing process) and expect to see savings.

    --
    Wolde you bothe eate your cake, and have your cake?
    1. Re:Don't just computerize the process by x_IamSpartacus_x · · Score: 1

      Michael Scott stands justified! Real business is done on paper!

      There are four kinds of business: tourism, food service, railroads and sales... and hospitals slash manufacturingand air travel

    2. Re:Don't just computerize the process by Fotograf · · Score: 0, Troll

      google lols at you

      --
      God's gift to chicks
    3. Re:Don't just computerize the process by tg123 · · Score: 1

      There's an old saw we had back in the 90s at UPS.
      Don't just computerize a process (or blindly apply technology to replicate an existing process) and expect to see savings.

      Please mod the previous poster up.

      Having just done a semester of "Systems analysis and Design" to create a computer system as complex as a health care system take lots of time and resources.

      Cycles of Planning , prototyping ,design and testing then you have to do it all over again ... again and again.......

      Just Computerising a process means a change to rid the company of inefficient processes is wasted.

    4. Re:Don't just computerize the process by craagz · · Score: 1

      Just Computerising a process means a chance to rid the company of inefficient processes is wasted.

      Did I fix it for you?

    5. Re:Don't just computerize the process by Yvanhoe · · Score: 1

      Exactly. The huge savings from computers come from the fact that totally new procedures can be made. It is slower for most people to use a tablet PC or a laptop than a paper notebook, the savings are not made there and if it is the only part that is changed, you'll loose money by doing so.

      * Use open standards (so that old and new equipement can easily communicate, and so that different departments can share information)
      * Network everything that is not life-critical.
      * Define clear access rights enforced through cryptography.
      * Have an efficient search engine. That's what computers do well, that is where the time saving is. Digitazing non-searchable data is only doing half of the work.
      * Publicize the data that you have available. Often it is not enough to be able to provide information to someone. Informing about the kind of information one can provide is the first step for an efficient search.

      I think that doctors, like too many people, dismissed the fact that computers were merely a tool, not pixie dust, and that a tool has limitation and strength one has to understand. I am not saying that every nurse and doctor should know how to program a search engine, but at least understand what it is, and why it is useful. Failing that, they will probably be more efficient with a pen and paper.

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    6. Re:Don't just computerize the process by Api+Dan+Air · · Score: 1

      Joseph Weizenbaum described something similar in "Die Macht der Computer und die Ohnmacht der Vernunft" (I don't know the real English title, it translates to smthg. like 'the power of computer and the powerlessness of sanity'). He complaints that often computers are used to "keep alive" already existing processes that were already outdated. But with the help of computing power, you would be able to "keep it alive". Nevertheless, redefining the process would we more effective. IMHO computers are a tool that tempts people to act with too little considering what they are doing. I wouldn't exclude myself ;)

      --
      Whatever...
    7. Re:Don't just computerize the process by Bert64 · · Score: 1

      Open standards also apply to the efficient search engine, the more the search engine knows about the structure of the data, the more efficiently it can index it (assuming the data structure is sane in the first place)...

      Another very important point you missed tho, keep it simple!
      Don't provide lots of functionality people don't need...

      If you provide people access to the internet, then you now have significant administrative and technical overhead to ensure they don't introduce malware into the network...
      Similarly with removable media devices....
      If you provide full blown fat clients, you have a lot of additional work to ensure people don't run their own programs (either intentionally or otherwise) on them...

      I very much see your point tho, common implementations get staff to write their notes into a proprietary application, which stores files in a proprietary format probably located on the workstation itself rather than somewhere centrally, it provides no benefit but is slower... Consequently, people just circumvent the inefficient system and write their notes by hand instead thus wasting all the money spent on it. Also, doctors handwriting is notoriously difficult to read...

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    8. Re:Don't just computerize the process by tg123 · · Score: 1

      Just Computerising a process means a chance to rid the company of inefficient processes is wasted.

      Did I fix it for you?

      kudos thankyou

    9. Re:Don't just computerize the process by elrous0 · · Score: 1

      You forgot one:

      Have God make the nurses, doctors, and secretaries as computer savvy as the programmers THINK they are.

      --
      SJW: Someone who has run out of real oppression, and has to fake it.
    10. Re:Don't just computerize the process by Anonymous Coward · · Score: 0

      lol welcome

    11. Re:Don't just computerize the process by TheLink · · Score: 1

      Here's how you improve a process at a hospital:

      http://www.post-gazette.com/pg/06318/738252-114.stm

      --
  3. I work in a major hospital by Anonymous Coward · · Score: 4, Interesting

    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.

    1. Re:I work in a major hospital by Anonymous Coward · · Score: 0

      An image forms in my mind, the image of an employee working at Medical Software Inc., stiffly reading the newest marketing brochure.

      A flash of light, then another image: a management representative of Major Hospital (a Microsoft subsidiary) lazily lying on the beach during his Medical Software Inc.-sponsored vacation trip, unmotivatedly repeating the words he was trained to say.

    2. Re:I work in a major hospital by hax4bux · · Score: 1

      Ya, I don't understand the conclusion either.

      I have nothing to do w/health care, but bar codes alone should have been a big help.

    3. Re:I work in a major hospital by Anonymous Coward · · Score: 0

      The problem I have observed is that administration uses computerization as a means to cut payroll by reducing staff. We don't realize an efficiency benefit because the 2 of the three lab workers who can now do their work in 1/3 the time thanks to bar codes have been laid off. The problem is almost always administration. They understand only jack and shit.

    4. Re:I work in a major hospital by Anonymous Coward · · Score: 0

      Speaking as a pharmacy technician, barcodes have not improved my job in the slightest (at least, not as currently implemented).

      Our buyer always seems to be shifting brands of drugs according to what is available and what is cheapest, and all those new drugs have to be inputted into the system before you can properly use them.

      Plus, the scanners we have to use are slow and unreliable; this past weekend, all but one of them were broken.

      Using the new system is at best not any more efficient than the old system, and often takes me about twice as long.

    5. Re:I work in a major hospital by jma05 · · Score: 1

      If they were big help, nurses would not be *working around* them.

      http://scholar.google.com/scholar?q=Workarounds+to+Barcode+Medication+Administration+Systems

      The trouble is... clinical care settings are not like business systems. Solutions that work in one place don't transfer over.

    6. Re:I work in a major hospital by Anonymous Coward · · Score: 0

      The study mentions that computers don't save the hospitals money, the cause being that computerisation is implemented by and for managers, and badly at that. If your hospital uses computers differently, then the Harvard study doesn't apply. Also, the study didn't take into account patient safety etc. but only cost and managerial efficiency.
      Take a look at the things that would be impossible without computers (in the broad sense): MRI machines, pinhole surgery with a camera, pacemakers, all kinds of medical analysis equipment, surgical equipment barcode checking... don't take the study to mean "stop using computers". Take it as "lots of hospitals are using computers ineffectively".

    7. Re:I work in a major hospital by Anonymous Coward · · Score: 0

      > 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.

      You have not clearly stated whether you *input* the data yourself. Generally speaking, clinicians like consuming electronic data. It's the creating part that they are not so hot about.
      If you are mostly looking at data entered by interns or nurses, I can see why you would like your system.

      > I don't know where Dr. harvard did his research but maybe he just has bad software.

      Your personal, subjective, anecdotal experience vs. statistical analysis on well defined variables across multiple software systems.
      To know where, you just need to read his methods section. It's cost data across sites that met their inclusion criteria.

      Also, it is not a satisfaction survey. There are other studies for that.

    8. Re:I work in a major hospital by BVis · · Score: 1

      Our buyer always seems to be shifting brands of drugs according to what is available and what is cheapest, and all those new drugs have to be inputted into the system before you can properly use them.

      Then your buyer needs retraining. You're not wholesaling rubber washers here, you're affecting people's lives. Sure, buy what's cheapest IF IT MEETS THE REQUIREMENTS, which should be set by a pharmacist or doctor, not some sleazebag buyer douche.

      Plus, the scanners we have to use are slow and unreliable; this past weekend, all but one of them were broken.

      This is a failure of management, not a failure of technology. If the equipment is defective, REPLACE IT. Oh wait, it might cut into their bonus. Nevermind.

      --
      Never underestimate the power of stupid people in large groups.
    9. Re:I work in a major hospital by Anonymous Coward · · Score: 0

      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.

      What system are you using at your hospital? You guys should write a rebuttal to this guys claim and share the info of your success!

    10. Re:I work in a major hospital by tsstahl · · Score: 1

      You would think. However, a surprising number of people object to being tattooed with a bar code. Especially older folks with accents. Go figure. /sarcasm

    11. Re:I work in a major hospital by colinrichardday · · Score: 1

      If it's only a few defective scanners, sure, replace them. But what if eighty percent of the scanners are defective? How is "good" management going to help you?

    12. Re:I work in a major hospital by tsstahl · · Score: 1

      I would hope the reporting functions are easier with a computer. However, what about the processes that input the data? Are they better than paper? Did they require paper first then an input session after acquisition? How many QC checks are required before the data are accepted?

      There are plenty of benefits in computerized health care systems. The study confirms that they are not a panacea for uber cheap healthcare and perpetual youthful health.

    13. Re:I work in a major hospital by BVis · · Score: 1

      By suing the vendor that sold them the defective crap in the first place, and replacing them with stuff that works.

      --
      Never underestimate the power of stupid people in large groups.
    14. Re:I work in a major hospital by Anonymous Coward · · Score: 0

      Should have been.

      You and the first poster are helping to illustrate exactly what the problem is. If done right, computers can greatly improve medical efficiency and accuracy. What this study shows is that most hospitals haven't done it right. The conclusions are spot on for the typical case; Hospitals purchase systems designed by and for accountants and managers instead of systems designed by and for physicians. So you see systems that are well designed for scheduling work hours and billing, but terrible for record keeping and completely counterproductive for scheduling for patients who, surprise, have no responsibility to keep the schedule your software "efficiently" calculated for them.

      To be done right, this "ERP for hospitals" needs to be designed by people with experience working in a hospital, including people with experience from all divisions and occupations in the hospital. M.D.s don't like being told this, but they are not experts on what physical therapy or radiology (as two examples) need any more than an accountant would be.

      It should be common sense: Let experts design the system. But this common sense is, as always, uncommon.

    15. Re:I work in a major hospital by colinrichardday · · Score: 1

      And if isn't just one vendor's scanners?

    16. Re:I work in a major hospital by Bourdain · · Score: 1

      what hospital is this even?

    17. Re:I work in a major hospital by modmans2ndcoming · · Score: 1

      Nurses and Doctors hate change. Unless you make them do something tehy will work around it. Weak administration policies and enforcment are the cause of the problems, not the systems themselves (for the most part)

    18. Re:I work in a major hospital by budgenator · · Score: 1

      At least with a bar code tattooed it's not going to change, nothing is more disconcerting than being prepped for surgery and noticing the name on your bar-coded wrist-band isn't yours, except for maybe noticing after surgery!

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    19. Re:I work in a major hospital by jma05 · · Score: 1

      I disagree. It believe it is *mostly* the fault of systems. Nurses and Doctors will embrace technology if they feel it is working for them. It is the systems that don't adequately take into account the nature of the work that they do. Good technologies are viral. They don't need enforcement.

    20. Re:I work in a major hospital by modmans2ndcoming · · Score: 1

      I accept that.

      Most Health Care IT systems are to make billing more accurate and to make the lives of the bean counters and managers easier. Most of the systems my group deploy are used to support the patient care process. almost all of them are built to provide better billing and data tracking and are not meant to make the lives of the care giver easier. That situation has caused Doctors and Nurses to be skeptical of new systems.

      One area where we have had a lot of Physician excitement though has been our HIM-EDMS. They love that their chart deficencies are sent to their centricity inbox and they just click on the deficiency alert, get taken into the app for completion , complete the deficiency and they are done. No more going to HIM being handed a huge stack of charts to sift through with post-it tabs for hours.

      Now, if we can just get Centricity Home-Base to work well and get the charge nurses to use it properly, the nursing staff might see some great efficiency improvements.

  4. Well by ShooterNeo · · Score: 5, Insightful

    Here's a relevant quote from "Superfreakonomics" :

    The diagnosis was clear: the WHC emergency department had a severe case of "datapenia," or low data counts. (Feied invented this word as well, stealing the suffix from "leucopenia," or low white-blood-cell counts.) Doctors were spending about 60 percent of their time on "information management," and only 15 percent on direct patient care. This was a sickening ratio. "Emergency medicine is a specialty defined not by an organ of the body or by an age group but by time," says Mark Smith. "It's about what you do in the first sixty minutes."

    Smith and Feied discovered more than three hundred data sources in the hospital that didn't talk to one another, including a mainframe system, handwritten notes, scanned images, lab results, streaming video from cardiac angiograms, and an infection-control tracking system that lived on one person's computer on an Excel spreadsheet. "And if she went on vacation, God help you if you're trying to track a TB outbreak," says Feied.

    To give the ER doctors and nurses what they really needed, a computer system had to be built from the ground up. It had to be encyclopedic (one missing piece of key data would defeat the purpose); it had to be muscular (a single MRI, for instance, ate up a massive amount of data capacity); and it had to be flexible (a system that couldn't incorporate any data from any department in any hospital in the past, present, or future was useless).

    It also had to be really, really fast. Not only because slowness kills in an ER but because, as Feied had learned from the scientific literature, a person using a computer experiences "cognitive drift" if more than one second elapses between clicking the mouse and seeing new data on the screen. If ten seconds pass, the person's mind is somewhere else entirely. That's how medical errors are made.

    END QUOTE
    I agree wholeheatedly with the last bit : I can't count how many times I've been to a doctors office or library or other institution and had to wait for a person to pull up my information on "the system". If you're gonna build a friggin computer system to handle local records, for the love of God don't scrimp on the hardware! Optimize the software! It should be INSTANTANEOUSLY fast!

    1. Re:Well by Anonymous Coward · · Score: 0

      Your talk will offend the abstract programming, managed code, XML parsing, virtual machine overlords.

    2. Re:Well by Sarten-X · · Score: 2, Insightful

      ...But it has to look pretty, or the folks with access to the bank account will never buy it! It also needs animated sliding panels, customizable positions for all controls, and must fit the graphical style of Windows 7, so the office staff don't get confused. When the programmers are done with those important goals, then they can work on the petty stuff like speed and usability.

      Let's not forget, it also absolutely MUST interface with the mainframe they kept records on in the 80's, just in case they need that information (but there's no budget for migration), and according to the boss's nephew who "knows computers", the next big thing will be X, whatever that is, so the system must use X, to do whatever it is that X does.

      --
      You do not have a moral or legal right to do absolutely anything you want.
    3. Re:Well by greenguy · · Score: 5, Informative

      I work in a hospital as an interpreter, so I see a lot of how people use computers... and how they don't. Generally in the ER, the patient first sees the triage nurse, who asks a series of questions. The answers all get entered into the computer. Then the patient sees their actual nurse, who asks many of the same questions again. This information may or may not get entered in the computer. Then the PA comes in and asks the same questions a third time. This time, the information gets written on a piece of paper, or maybe a tablet computer. Eventually, the attending physician stops in just long enough to ask the same questions a fourth time, and doesn't enter the info anywhere. If the patient is admitted and sent to another department, the process starts over.

      --
      What if I do the same thing, and I do get different results?
    4. Re:Well by jamesh · · Score: 5, Insightful

      I made a call to HP (abbreviated to protect the company :) recently to have a failed disk replaced under warranty. I went to great lengths to explain that I was a consultant acting on behalf of the customer, gave HP all of my details and all of the customers details etc. I could hear constant typing in the background so something was being entered somewhere. About 20 minutes later I got a call from my office saying they had HP on the line asking who the onsite contact was, who the customer was, and where the part should be sent.

      It's not just hospitals... I think I can generalise the conclusion of the article - if the solution (IT or otherwise) isn't designed/built right, and people don't know how to use it right, then it isn't going to work right and is going to make peoples lives harder not eaiser. Seems kind of obvious when you put it that way though.

    5. Re:Well by martin-boundary · · Score: 1
      Could you explain why this is a bad thing? The way you describe it, there are four people who each independently verify the information, instead of what? One person who enters some data into the computer and three people who read it back?

      If each person has a 25% misdiagnostic rate, then four independent people asking questions gives a combined misdiagnostic rate of less than 1%. If three people trust the diagnosis of the first person, then the combined rate is 25%. Regardless of the actual numbers involved, many people talking to the patient independently should improve the chance of a successful treatment.

    6. Re:Well by Anonymous Coward · · Score: 0

      And another anecdotal data point: 20 plus years ago, a cerebral aneurysm took me down hard - while still conscious, I had to explain my entire medical history and personal symptoms to SIX consecutive attendants, from the ambulance drivers through ER and finally the neurosurgeon, all whilst in quite uncomfortable pain. And there weren't any computers to speak of at all at the time. The computers slow it all down even further, BUT would be much more convenient in the scenario had I fallen unconscious after the first such inquiry. As others have remarked, though, the computer system screw-ups are more often a combination of officiousness, inefficiencies, poor design, poor management decisions and bad implementation through poor commissioning and training procedures. Not to forget that medical info is a BIG ball of wax and getting everyone in a modern hospital to sing from the same song sheet is nigh impossible in the first place.

    7. Re:Well by Angostura · · Score: 1

      That's an interesting comment and it made me think. Initially my thought was that that the system you describe sounds silly and wasteful (I'm an IT-focussed guy and I hate the thought of information being captured multiple times and rekeyed).

      But then I thought - perhaps it's actually quicker for those doctors to simply ask the question again, rather than to find a workstation and query the patient record. Perhaps by asking the question themselves they garner additional information from the way that the patient reponds. Perhaps the initial triage nurse was entering data for hospital; adminstrivia, whereas the doctor needs to interact directly with the patient to make an informed diagnosis. Would the triage nurse's data help him/her? Perhaps, marginally, but perhaps it's quicker and more human to say "Good Morning Mrs Jones, what seems to be the problem?".

      The repeated questioning is undoubtedly annoying for the patient but it seems inefficient prima facie - but perhaps it isn't *actually* inefficient.

      Hmmm.

    8. Re:Well by Anonymous Coward · · Score: 0

      I can give insight on this particular facet of care by way of my medical school orientation dinner many years ago:

      "The truth comes out as the white coats get longer."

      which I'll amend from my personal experience with the prefix "More of..."

      Many patients, for a host of reasons which also include very real human shame, pride, regret, are reluctant to give the full story. As they are slowly integrated into the clinical setting, the barriers almost invariably drop as they are further removed from the everyday: the waiting room chair gives way to an emergency room bed, street clothing is removed and a gown is put on. The actual nurse repeats the questions, and almost invariably the answers are more detailed than the tiage notes.

      Enter the PA, with a short white coat. At this point, the patient has been hooked up to the usual suite of automatic diagnostic equipment and the reality of the Emergency Dept has begun to sink in, with its smells, sounds and, of course, waiting. Inhibitions falls, and the story may change completely.

      Finally, someone enters the room with, 'I'm Dr. ..." as the patient now has an IV established, lab draws taken, injuries fully exposed and, again, with plenty of time to think about what has happened, it real story only now begins to emerge.

      I don't say this in any way to slight anyone, it would be impossibly inaccurate to claim the physician is the only person capable of getting the truth for as anyone who has done time in a hospital knows, the charge nurse, the janitorial staff and the on-call maintenance guy make or break the emergency department, but I do claim the repeated questioning is more necessary due to human, not technological, barriers.

    9. Re:Well by Grygus · · Score: 1

      What diagnosis is happening here? He didn't say anything about data interpretation, he's talking about data collection. Unless patients are changing their stories between interviews, there is no benefit to asking them where it hurts four times. Certainly if you have different clarifying questions so that you can make a diagnosis, ask away, but gathering the basic complaint four times does not sound useful to me, and likely doesn't inspire confidence in your patient at the very moment that they are putting all their trust in you.

    10. Re:Well by Anonymous Coward · · Score: 0

      Don't blame HP for that blunder. When your company (Company ABC) sold the customer (Company XYZ) their equipment, they should have registered the equipment's HP Warranties with the Customer Details. Instead, your company registered the equipment in yourown name (Company ABC). So when you called for support, the equipment wasn't where HP's Warranty system thought it should be. Therefore, who the hell are you, and why are you logging a call from Company XYZ, when the equipment is "owned" (in the eyes of HP) by Company ABC. HP promptly call Company ABC, and ask for advice. At this point, your office direct the parts to the customer.

      The poor drone on the end of the phone is just working in a support centre. They don't have the authorisation to change warranty details without going through the official channels (what if it was stolen gear, or gray imports, or whatever?). If you purchasing manager wasn't so lazy, those carepack warranties would be completed properly & all of this could have been avoided.

    11. Re:Well by Anonymous Coward · · Score: 1, Interesting

      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 =\

    12. Re:Well by tomhath · · Score: 2, Informative

      But it has to look pretty, or the folks with access to the bank account will never buy it! It also needs animated sliding panels, customizable positions for all controls, and must fit the graphical style of Windows, so the office staff don't get confused. When the programmers are done with those important goals, then they can work on the petty stuff like speed and usability.

      Oh, don't worry about that part, the system Smith and Feied are talking about is their own product, that they sold to Microsoft.

    13. Re:Well by pnutjam · · Score: 1

      cognitive drift ...
      The story of my life...

    14. Re:Well by pnutjam · · Score: 1

      ding..ding..ding, it not that there isn't room to improve, it's just that nobody does...

    15. Re:Well by pnutjam · · Score: 1

      Your misdiagnosis rates don't stack that way. They are not proofing the previous asker's entry, like they would be if they were reading the answers and asking the patient to verify. They are not even sharing what they learn.

    16. Re:Well by curare19 · · Score: 1
      I'm an EMT. When I was first certified, we had to go through a practical test of asking the patient medical history, what happened, allergies, medications, etc. Through the course of the test, we probably asked "what happened" two or three times. I knew the ER would ask again. And again. I thought it was wasteful and said so.

      The EMT who was training us explained that stories often change through those multiple askings. My experience confirmed her explanation. As another commenter mentioned, the truth GRADUALLY comes out. Though many people will answer "What's your medical history?" accurately each time, some will change the story based on who is there, how much time they've had to think about it, once they've calmed down, and whether something else you've said reminded them.

      "Do you have any medications or history I should know about?" once turned from "No" into "I have a chronic medical condition and take numerous medications for the condition" based on some gentle reminders. "Could you be pregnant?" turns from "No" into "Yes" once family members are no longer within hearing range.

      A lot of medical inefficiencies make more sense when the soft squishy human side is taken into account.

    17. Re:Well by tibman · · Score: 1

      There seems to be many ways to implement the features they want too. My hospital has all digital records and their solution to MRI storage is have the MRI interpreted on the spot and draft a text report on the findings. One page of text versus a huge MRI. The actual MRI itself is probably deleted and only the text remains after the "case is closed".

      This also means that when i visit a distant lab they can pull up my "MRI" instantly because all the important facts are there in a tiny text file.

      --
      http://soylentnews.org/~tibman
    18. Re:Well by Anonymous Coward · · Score: 0

      I have ran into that a couple of times with various vendors. HP in my experience is really good (unless you are talking to consumer level support then it is hit or miss depending on who you are talking to)

      The best thing to do is to find a good local ASP and deal with them instead of having to call HP directly, they can usually save you time having to futz around with Tech support (which if you already know the issue is a huge time saver)

    19. Re:Well by ColdWetDog · · Score: 1

      The repeated questioning is undoubtedly annoying for the patient but it seems inefficient prima facie - but perhaps it isn't *actually* inefficient.

      It's a bit more subtle than that. The clerk asks the question "Where does it hurt?" - the patients points somewhere, the clerk puts 'abdominal pain'. The nurse comes in asks "Where does it hurt?, How long? What helps?" and perhaps a few more questions. If it's a teaching institution or a place that uses midlevels (Physician Assistants, Nurse Practitioners) The PA / Intern sees that, expands on it, asks more questions, gets more detailed answers. The Attending (senior level) physician comes in, hopefully just checks up on everything if the story and exam fit and wanders off. If not, they (hopefully) ask even more detailed questions / do more tests / whatever to get to the issue.

      So it's easy to pretend that the patient gets the 'same' questioned asked several times, but in reality, it's a stepped system of increasing discriminating power. Or at least it's supposed to be. Patients sometimes get annoyed at it, clinical staff often get frustrated when the story changes significantly from questioner to questioner, but that's life.

      --
      Faster! Faster! Faster would be better!
    20. Re:Well by Bourdain · · Score: 1

      join the club :)

    21. Re:Well by Anomalyst · · Score: 1

      I'm sorry, what were we talking about?

      --
      There is no right to feel safe thru security vaudeville at the expense of everyone's freedom, privacy and tax money.
    22. Re:Well by Anonymous Coward · · Score: 0

      "My hospital has all digital records and their solution to MRI storage is have the MRI interpreted on the spot and draft a text report on the findings."

      Which hospital is this? I want to be sure never to go there. If you really needed an MRI, then your doctor will want to read it themselves. If they can't, they probably didn't need it or they told you take a hard copy to the specialist who can read it. Radiologist reports are like assholes....

      "...because all the important facts are there in a tiny text file."

      And if you believe that, I have an excellent investment opportunity in Dubai...

    23. Re:Well by demonlapin · · Score: 1

      It should be INSTANTANEOUSLY fast!

      Don't get me started. In our EHR, changing the visit # (which is needed to make sure that that patient is billed correctly, i.e. the charge for anesthesia isn't associated with your clinic visit but instead with your actual surgery) takes almost twenty seconds of waiting for the system. The actual clicking part takes less than five.

    24. Re:Well by drinkypoo · · Score: 1

      But then I thought - perhaps it's actually quicker for those doctors to simply ask the question again, rather than to find a workstation and query the patient record.

      That's why patients have wristbands, and why you can get a PDA or tablet with an attached bar code reader. (Or, these days, RFID scanner.)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    25. Re:Well by CodeBuster · · Score: 1

      So lets recap here: really fast, can handle any data from any time, and a complete compendium of all human knowledge. How much did you say was budgeted for this system again? If you have a practically unlimited budget then such a system might be possible, but if you want to get it done before some time next century and at a reasonable price there have to be compromises.

    26. Re:Well by ShooterNeo · · Score: 1

      Google's this quick. I can think of a lot of tweaks, from using SSDs and servers with lots of RAM, to actually optimizing the OS image that goes on the various PCs in the hospital/clinic for speed. Make sure not to scrimp on the RAM for anything. To ameliorate network congestion, you'd need some kind of quality of service architecture.

      Anyways, if you read the rest of the quote, they succeeded in building a working piece of software that met their expectations.

    27. Re:Well by ShooterNeo · · Score: 1

      Think about the problem for a moment. The basic action of healthcare is to bring up the records for only one patient, read the records to learn what you need to learn, and then to perform an intervention to slow the rate that the patient is dying at. After you perform the intervention, you should report your findings by adding more information to the patient's record.

      So, this already radically makes the problem easier. It doesn't have to contain all human knowledge : your database should be able to put on the screen of the termnal the records for JUST THAT PATIENT within 1 second. So no expensive, slow searches of all the records.

      In addition, it doesn't even need to bring up large files like the MRI right away. The way the software should work, once a user requests the records of a patient, the software should immediatly put up a summary screen with the information organized by priority. For MRIs and videos and such, only a preview of the full image need be displayed unless the user actually clicks it.

      If I were designing the software, I would have it start downloading the full patient record in the background, with a low priority quality of service designation on the packets, to cache in the client machine. That way if a user left a patient record open for a while (say on a computer that's at a nurse's station) then browsing around the record would become instantaneous.

      For the server side : I'd use idle cycles on the server hardware to optimize the layout on the hard disks and to pre-calculate things like preview images.

      Anyways, I'm not a software developer, but I think it's obvious that if extremely high performance from the perspective of a user were a design goal, it would be possible to deliver.

    28. Re:Well by tibman · · Score: 1

      Veteran Affairs hospital in Louisville. But i'm told the system spans across all VA hospitals in the US, plus labs and all those little tiny clinics.

      I think your medical experiences are different than mine. I usually see specialists.. like i go see the Ear/Nose/Throat guy and he says.. your lymphnodes are swolen (extremely simplified), go down to MRI (and gives directions). I go there with no paperwork or appointment.. say "hi, i'm blah blah" and they go "Right this way sir" stick me.. make me feel like i'm pissing all over myself and do the MRI thing. They analize it there with the MRI specialist and he writes the report. I can then go back to the E/N/T and he can immediately pull up the report.

      I have never been assigned a doctor before. There is a case worker that keeps track of appointments and makes sure everything is moving along smoothly but he/she doesn't need medical knowledge (imo).

      The whole process seems very streamlined. Perhaps very non-personal but i don't mind. There seems to be enough oversight and checkpoints that people don't fall through the cracks.

      --
      http://soylentnews.org/~tibman
    29. Re:Well by Anonymous Coward · · Score: 0

      you're a fag

  5. I would also guess... by joocemann · · Score: 1, Insightful

    That some of this has to do with the staff being largely of the 35+ crowd and the propensity of that crowd to not know how to use computers even remotely as well as, say, a 16 year old kid does right now.

    Computers take more work to use when you don't have a nice grasp on not only the software or function you're doing, but the regular logical deductions you make from repeated observation and experience.

    From my experience in life, most older people have somehow adapted themselves to 'get by' with technology, but without actually knowing what is really going on. Many will think the monitor is the computer. Many have no idea what the basic components are. And, hell, many are even clueless at the overly-simplified layouts of hardware nowadays with color coding and the square-peg-square-hole approach to basically everything.

    Make the majority of a staff fill this description and you can be damned sure plenty of time is being spent moving the mouse around cautiously while looking down the nose in deep confusion and wonder.

    question: is a hotkey actually hot? which one is it?

    1. Re:I would also guess... by Anonymous Coward · · Score: 0

      Am I in the "older" generation? I'm 41+9/12 years old, but I've been programming as a hobby since I was 13. I am quite comfortable with technology, and I can tell you from personal experience the vast majority of health care related software SUCKS despite vast millions of $$$ in expenditures. In my view, some big issues are (1) the problem is actually harder than it seems , given the extreme flexibility needed, (2) this is not understood by the designers, leading to horrible usability & functionality issues and (3) the good software engineers seem to go to other fields. There are lots others, but I agree this is a very solvable problem. I often wonder what would happen if we had a game design team on the job.

    2. Re:I would also guess... by jma05 · · Score: 3, Insightful

      > That some of this has to do with the staff being largely of the 35+ crowd and the propensity of that crowd to not know how to use computers even remotely as well as, say, a 16 year old kid does right now.

      That used to be a favorite argument to explain away poor clinical system adoption. But it does not hold true anymore. An average doctor today is at least as computer savvy as an average teenager. They may not use SMS, twitter or use facebook as much as the teens, but they certainly know how a computer works. This isn't the 90s when computers were optional in life.

      > Computers take more work to use when you don't have a nice grasp on not only the software or function you're doing, but the regular logical deductions you make from repeated observation and experience.

      Good clinical software should not need you to be an expert in computers... just that software... the one they use for several hours each day. And if it takes considerable experience to get up to speed... that's a usability problem... not a user problem.

    3. Re:I would also guess... by el_tedward · · Score: 0

      Not everyone is like this. We have someone (of the walking-slow old variety) at the doctors office i work at who has trouble with computers sometimes. However, she learned things in DOS & had a lot of trouble moving to the GUI. I think you could say learning and being comfortable with DOS would be easier once the learning process is over.

      A GUI can be extremely inefficient, though more intuitive, depending on it's design. Dragging and dropping a file, though.. that's easier than using mv blahfile toblah

    4. Re:I would also guess... by Frosty+Piss · · Score: 1

      35+ old fogies that don't know that IE isn't the Intertubes? Good grief! How old are you? Oh, wait, there's a MySpace linky in your sig.

      --
      If you want news from today, you have to come back tomorrow.
    5. Re:I would also guess... by tg123 · · Score: 1

      ........ In my view, some big issues are (1) the problem is actually harder than it seems , given the extreme flexibility needed, (2) this is not understood by the designers, leading to horrible usability & functionality issues and (3) the good software engineers seem to go to other fields. There are lots others, but I agree this is a very solvable problem. I often wonder what would happen if we had a game design team on the job.

      Your right when computer systems get this complex you need good project management , systems analysis and design.

      (Just did a semester of this subject.)

      You need to build the system from scratch and the people doing it need to work out what processes are needed and what are not and they need to talk the users of the system then (the poor people) have do it all over again till the system works.

      http://en.wikipedia.org/wiki/Iterative_and_incremental_development

    6. Re:I would also guess... by Spliffster · · Score: 2, Informative

      That some of this has to do with the staff being largely of the 35+ crowd and the propensity of that crowd to not know how to use computers even remotely as well as, say, a 16 year old kid does right now.

      This is exactly what I witness. I am working as a Software developer in a University Hospital in Europe. Just an example:

      It often happens here, That some one enters data into a system. Then another devision needs said data and guess what they do? Data is printed out, faxed internally to another devision and usually a subset of the data is entered manually into another system again. Despite the fact that all involved users have access to both systems and if they'd use the systems appropriate, data would be exchanged automatically between theses systems (data exchange doesn't always happen automatically for several logical or obscure reasons).

      As it looks like (from talks with IT stuff from other hospitals) we are not a special case. Especially non academic employees in a hospital are really resistant in learning how to use these "new" technologies (it works much better with younger employees).

    7. Re:I would also guess... by Anonymous Coward · · Score: 0

      As a 40-year-old who has been programming since about 8 years old, and lived through generation after generation of computers with my classmates, I have yet to meet a 16-year-old who has the vaguest idea what a computer is or how it does its magic. Seriously. They know the UI of the devices we 40-year-olds create for them, but could never write it themselves. There was a window where computers were simple enough to know completely, and a generation of kids who had those Vic-20's, TRS-80's, Apple II's, and the like when they could absorb them and then track forward to today's computers and embedded devices. The current generation, even with the same talent, will never have the chance to have a simple device they learn thoroughly, and then half a lifetime to learn more complex systems as they evolved from those original systems. You missed the boat kid, sorry. Hell, my parents in their 70's have about half a dozen systems, most of those Linux and self administered. *They* have the time now to learn the UI to all sorts of social networking toys and financial analysis software that those of us in the middle of our careers don't have the time for.

    8. Re:I would also guess... by colinrichardday · · Score: 1

      If I want to move all of my *.tex files from one directory to another, I do

      cd source_directory

      mv *.tex target_directory

      How do I do this on a GUI?

    9. Re:I would also guess... by foniksonik · · Score: 1

      Sounds like software companies designing these systems didn't really do an thorough analysis of how hospitals work - not that it's likely to be their fault, more likely is that they were tasked with one set of operations and the hospitals are using the system for several additional operations they didn't tell anyone about.

      A simple fix for this situation is to enable the emailing (internally only of course) of the data and the import of said data into other systems. Everyone knows how to use email... and it's a typical scenario to have a structured text format in an email be parsed for data and added to a database.

      This would decentralize the import/export of the data and allow on site IT workers to create new import macros for additional systems on demand.

      --
      A fool throws a stone into a well and a thousand sages can not remove it.
    10. Re:I would also guess... by joocemann · · Score: 1

      *Wooooooooooooooooosh*

    11. Re:I would also guess... by pwfffff · · Score: 1

      In Vista: Win Key, "C:\source_directory", enter, click 'Type' to sort by extension, drag to select, drag and drop.

      Mine is 20 keystrokes, 3 clicks; yours is about 50, maybe 40 if you tab complete. Of course, since you assume you're in the correct root directory anyways I could go ahead and replace my first two steps with "double click 'source_directory'" and bring it down to a simple 5 clicks.

      Is this stuff really that hard to figure out?

    12. Re:I would also guess... by colinrichardday · · Score: 1

      Of course, since you assume you're in the correct root directory

      When I said source directory, I assumed it as an absolute path.

      Also, one can program my method in bash; how do you get the computer to mouse click?

      It probably isn't hard to figure out how to do that in Vista, but is it obvious?

    13. Re:I would also guess... by el_tedward · · Score: 0

      I guess was more talking about ease of use for someone like me or (I'm assuming) the old lady who would basically be a command line n00b. I think that the command line is a lot more efficient, but it's no where near as intuitive as a GUI. You can always teach yourself things, but it's generally easier to teach yourself something visually if you don't have very much experience with it.

    14. Re:I would also guess... by Spliffster · · Score: 1

      I think your intent is to help and not to troll, maybe I gave too little detail about our problem.

      The main problems are not of technical nature but social. We have a well defined set of HL7[1] Messages for exchanging record sets (HL7), binary data which might contain a record set (HL7 MDM) as well as Messages/Events (HL7 ORU).

      The real problem lies in the fact, that hospital personal (except doctors) are primarily focused at treating the patient. Everything technical is seen as just another annoyance. Today's management expects a lot of reporting, which forces said workers into entering and mangeing a lot of data. Something they don't want to do (sometimes can't). It is an annoyance to them which they want just to go away as quickly as possible. Therefore they often use systems inappropriately.

      [1] HL7 is data exchange format primarily used in medical environments across the globe.

  6. The key being ... by devloop · · Score: 5, Interesting

    "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.

    1. Re:The key being ... by malkavian · · Score: 4, Interesting

      Wow, in the hospital where I work, the doctors frequently turn up to the IT department saying how they've just bought in a new system and they need it supported. If they get told 'no', they complain to the directorate that IT aren't supporting a system based on IT. The directorate lean on IT (with not so veiled threats) until IT support a system they'd have vetoed if they'd be involved in procurement..

      The problem that has been evaluated is that the research was done on an organisation with no true enterprise architecture (at the business silo stage at best). In other words, somewhere that hasn't invested in IT (and likely has the doctors doing what they feel like, with 'homegrown' Access databases and applications, trusting what the vendors say when they produce shiny pamphlets, and either not hiring people who understand how business and tech should map, or not giving them the clout to be able to change the way the organisation works to successfully be able to change things so that they do).

    2. Re:The key being ... by Antiocheian · · Score: 1

      Please back that up.

    3. Re:The key being ... by wisty · · Score: 1

      I'd believe it. But whether it's doctors getting conned by vendors, or administrators (or IT) making decisions without the inputs of doctors the result is the same - useless and troublesome IT systems.

    4. Re:The key being ... by martyros · · Score: 4, Interesting
      Best quote from the article:

      Himmelstein said that only a handful of hospitals and clinics realized even modest savings and increased efficiency -- and those hospitals custom-built their systems after computer system architects conducted months of research.

      He pointed to Brigham and Women's Hospital in Boston, Latter Day Saints Hospital in Salt Lake City and Regenstrief Institute in Indianapolis as facilities with some success in deploying efficient e-health systems. That's because they were intuitive and aimed at clinicians, not administrators.

      Programmers of the successful systems told Himmelstein that they didn't write manuals or offer training. "If you need a manual, then the system doesn't work. If you need training, the system doesn't work," he said.

      In other words, computers are not a magic bullet. They only work well when you actually invest the time to find out what you need them to do, and then make them do that.

      --

      TCP: Why the Internet is full of SYN.

    5. Re:The key being ... by somersault · · Score: 1

      I think as well as any savings or efficiency increases, they should also take into account the relative ease with which electronic records can be backed up and restored in case of fire or flooding, etc. At the very least, there should be scans of any paper documents. Full hardcopy backups would take up a lot of space, and they're not very easy to replicate if you do end up losing the originals.

      --
      which is totally what she said
    6. Re:The key being ... by Anonymous Coward · · Score: 0

      Exactly. Having asked my doctors outright why they still rely so heavily on paper records carried around in file folders, the answer was universally that it was much easier to make quick notes on paper than to enter patient data into any software foisted upon them.

    7. Re:The key being ... by Anonymous Coward · · Score: 0

      As a former RN I can attest that nothing entered the mind of management regards software for use by staff except to use it as a tool to detect errors by staff or to in some way make the staff do work for management not related to patient care. The whole purpose was to catch you making an error rather than to help you do your job so that you didn't get into an error position in the first place. For example, they would time the posting of MD orders and punish for posting them later than a certian amount of time after they were written even if you didn't arrive in your hands prior to that time. If the orders were unclear or illegible that wasn't the problem you were. Suppose a medicine didn't arrive from pharmacy in time, you were late and wrong. No they wouldn't have the MD post his own orders and let the system propigate them down. We had to transcribe the. This is all a farce. I am skilled in software design. If there was a system designed to assist in making the job work faster, easier etc management has no interest.

      Examples of such a system include the ability to post pharmacy orders and check interactions electronically. They include systems to bring ordered supplies to the RN on time. They include systems to cross check what needs to be done at the time it is to be done. These do not exist and are not going to exist.

    8. Re:The key being ... by indiechild · · Score: 1

      The "magic bullet" is usability. Those who understand the power of usability and high quality user-friendly interfaces are those who succeed in an otherwise mediocre marketplace.

    9. Re:The key being ... by Anonymous Coward · · Score: 0

      Best quote from the article:

      Himmelstein said that only a handful of hospitals and clinics realized even modest savings and increased efficiency -- and those hospitals custom-built their systems after computer system architects conducted months of research.

      He pointed to Brigham and Women's Hospital in Boston, Latter Day Saints Hospital in Salt Lake City and Regenstrief Institute in Indianapolis as facilities with some success in deploying efficient e-health systems. That's because they were intuitive and aimed at clinicians, not administrators.

      Programmers of the successful systems told Himmelstein that they didn't write manuals or offer training. "If you need a manual, then the system doesn't work. If you need training, the system doesn't work," he said.

      In other words, computers are not a magic bullet. They only work well when you actually invest the time to find out what you need them to do, and then make them do that.

      It's not surprising the systems became cost effective / efficient once they were accurately aimed at the end user, as they should have always been.

    10. Re:The key being ... by Vindicator9000 · · Score: 2, Insightful
      Ho. Lee. Crap.

      I do IT for a major regional hospital chain, and all this time, I thought it was just my company that was this fucked up.

      What you're talking about is EXACTLY what happens. Doctors, managers, vendors, whoever CONSTANTLY show up with junk hardware and software, throw it at us, and expect us to support it. The organization is so bloated around the middle that no one has the authority to tell anyone else no. We have hundreds of Access databases, SQL servers running on people's desktops, and apps that we've never heard of turning up constantly.

      And it all happens so fast, and we're SO understaffed (4 IT staff for 2000+ devices in my hospital) that we don't have a prayer of keeping track of it all.

      And the understaffing is a problem in and of itself. The organization as a whole has around 30K total employees, of which 700 are IT staff. Probably 10% of the IT staff does next to nothing. Another 30% does nothing beneficial to patient care, or actively makes patient care harder. 20% are redundant management. For example: my particular part of the company, staffed by 4 IT grunts such as myself, has 4 managers directly over me: 1 team lead, 2 Project Managers, and an Account Executive. All of whom often want conflicting things done at the same time. Finally, the last 50% of IT here is made up of everybody else working their asses off to make up for the rest of the crap.

      No wonder heatlh care costs are sky-high. IT is indicative of the whole mess... the company is a gigantic mish-mash of hacks thrown together at the last minute to satisfy the newest bureaucratic requirement, public opinion, expensive doctor, negative news story, malpractice suit, or demands from the board or rich donors. There's no way anything like this could run efficiently.

    11. Re:The key being ... by evilRhino · · Score: 1

      This article ignores the free-market aspect of how much things cost. If administrative costs can be billed at $X, it doesn't matter if it really is more efficient, it will still cost $X. It does however state that there is a modest improvement in *quality* of the data, which is a win.

    12. Re:The key being ... by colinrichardday · · Score: 1

      Where is this planet that has a free market in health care?

    13. Re:The key being ... by Anonymous Coward · · Score: 0

      Examples of such a system include the ability to post pharmacy orders and check interactions electronically. They include systems to bring ordered supplies to the RN on time. They include systems to cross check what needs to be done at the time it is to be done. These do not exist and are not going to exist.

      They are coming slowly... More hospitals are coming online with CPOE (we are about 80% doctor entry with full interaction checking on pharmacy orders, and a electronic MAR) , and as that trickles down it IS making a difference. Like others have said hospitals are EXTREMELY resistant to change of any kind. That's changing though, mostly do to the generational changes in the doctors.

      I've seen a HUGE change at my organization in the past 5 years regarding Doctor/nurse attitude towards technology. Before it was "I don't want to have to look in a computer" now it's "why isn't this online?" "Why can't I sign it in the computer?" It just takes much longer then other businesses, comparing hospitals to "mini-governments" in much more accurate then comparing them to a normal "business" model

    14. Re:The key being ... by Anonymous Coward · · Score: 0

      It doesn't help that they only typical want IT folk with experience in the medical field. It's just a process and data guys, might get better result if the didn't subset the IT labor pool. Just a thought.

    15. Re:The key being ... by Anonymous Coward · · Score: 0

      Programmers of the successful systems told Himmelstein that they didn't write manuals or offer training. "If you need a manual, then the system doesn't work. If you need training, the system doesn't work," he said.

      This is true, but they should still have them. The true key to good software design is thorough documentation that effectively never gets used. Even better if it is integrated into a help feature.

      I have thrown more OSS solutions away because of lack of/poor documentation because (I assume) the writer assumed everything to be intuitive, and maybe with the right background it is, but that doesn't excuse the lack.

    16. Re:The key being ... by Cytotoxic · · Score: 1

      Different industry, same problem. In fact, we are currently being forced to implement and support a crap "workflow" program that we specifically vetoed as insecure, inefficient, unmanageable and unmaintainable. Even better, the "evaluation committee" - all non-IT people - touts their success in automating their demonstration process in only 3 months!

      They complained about having to click through to enter a date on a different screen (2 clicks on a very rare event occurrence - about 5-10 times per year). Their new solution replaces their one screen queue (with 2 extra clicks 5 times per year) with a 9-page scripted workflow that has to be followed for every single item - tens of thousands. Brilliant!!! And people wonder why they need IT help?

      Even better, management is on board and very impressed that they were able to solve their problem without IT intervention. Now they have 9 input screens to maintain, as well as the connections between those input screens, as well as the integration to the existing system. I figure they probably cost themselves about 10-20 hours per week in end user "wait time" for the new process once it goes into production, plus another entire salary for maintenance on the system. Plus, they are demanding read-write access to every table in our carefully secured system - to be managed on the business side by an advanced clerical worker who is "good with computers." So much for data validation and security audits... But they are thrilled because their process manages "millions of dollars" and is too important to fail! Huh?

      The complete inability of most people to follow even rudimentary logic astounds me. These are highly paid, well educated executives at a billion dollar company, not rubes. Even if they can't figure out tech stuff, they should at least be able to understand that they might want to listen to their CIO and his executive team who each have 20-30 years of experience in exactly this sort of system design. But I'm convinced that this capability just doesn't exist. Because they can enter data in a form on a web page, everyone thinks they are a systems architect.

    17. Re:The key being ... by Anonymous Coward · · Score: 0

      Doctors and other medical personnel do not typically hold much power
      when it comes to IT.

      You do not work in a hospital environment do you? Right now I am scanning a doctors laptop for viruses, instead of working on a important project (anesthesia related), just so he can continue surfing porn. Remember that the Doctors are the breadwinners for hospitals, so their words hold much sway.

      Software vendors aim to please management, they are the ones who take
      the purchasing decisions.

      This is true, more accurately it is accounting that does this. But after they buy the software, its up to the staff to dictate what you do with your schedule after.

    18. Re:The key being ... by atamido · · Score: 1

      In other words, somewhere that hasn't invested in IT (and likely has the doctors doing what they feel like, with 'homegrown' Access databases and applications, trusting what the vendors say when they produce shiny pamphlets, and either not hiring people who understand how business and tech should map, or not giving them the clout to be able to change the way the organisation works to successfully be able to change things so that they do.

      It is pretty bizarre how many crappy home grown medical applications there that people are buying for tens of thousands of dollars. It is like all laws of capitalism and economics break down when you walk into a hospital.

    19. Re:The key being ... by jollyreaper · · Score: 1

      In other words, computers are not a magic bullet. They only work well when you actually invest the time to find out what you need them to do, and then make them do that.

      That's what I try to tell people at my place. If an EMP hit tomorrow and we were going to move all our business processes back to paper, we'd still be dealing with the same basic theory of information management. Customer ID number? They existed before computers. Why? You tell me which John Smith we're talking about, we've got ten in the files. Double-entry bookkeeping? We had that long before we had computers. Standardizing the records? You'd be doing that with 3x5's and card files. Last name, first name, middle initial, do it the same for all of them.

      You can't automate a broken process. Get the logic working so that you can run it on paper, then we can talk about putting it in a computer. At best all a computer can do with a broken process is fuck it to pieces.

      --
      Kwisatz Haderach
      Sell the spice to CHOAM
      This Mahdi took Shaddam's Throne
    20. Re:The key being ... by quixote9 · · Score: 1

      Wow, in the hospital where I work, the doctors frequently turn up to the IT department saying how they've just bought in a new system and they need it supported. If they get told 'no', they complain...

      The point the article made was that system works even a little bit only when doctors,-- doctors, not management, not IT, not enterprise architecture, not business silos, doctors -- can say what they need and get told "yes."

    21. Re:The key being ... by ShakaUVM · · Score: 1

      >>In other words, computers are not a magic bullet. They only work well when you actually invest the time to find out what you need them to do, and then make them do that.

      Right, but there's actually quite a bit of research showing tremendous benefits for computer systems implemented well in hospitals. Without computers, doctors can spend as much as 75% of their time away from patients, fucking around with paperwork.

      At my wife's hospital, they don't have the best system in the world, but they have an electronic drug ordering system, automated drug vending machines on each floor for commonly used drugs which tie into the hospital-wide inventory database, have electronic files, etc. The thing goes down waay too often for something that is marketed toward hospitals, but at least the company provides 24 on-call support.

    22. Re:The key being ... by Anonymous Coward · · Score: 0

      Well, of course it didn't save them money or make them more efficient...they're using Microsoft junk, right? :-)

      Well, duh...anyone knows MS junk makes you inefficient, wastes time and costs money.

      They obviously didn't do their research...linux is the answer, not windose...:-)
      http://www.desktoplinux.com/articles/AT7753498575.html
      http://www.guardiandigital.com/company/casestudies/hipaa.html

      Etc., et cetera :-)

    23. Re:The key being ... by Nethemas+the+Great · · Score: 1

      Medical IT began more than 25 years ago when ACR and NEMA decided it'd be a grand idea to get together a band of inept folks to come up with what would become the standard for handling/communicating medical data. Completely vacant of knowledge pertaining to the engineering of standards/protocols, especially those involving software this group came up with a poorly scoped, self-conflicting, and outrageously cumbersome to implement standard eventually known as DICOM. At the time, hospitals and clinics were forced to either pick a single modality (device) vendor and be locked-in for life or have a host of devices that couldn't talk to one another. DICOM was supposed to enable cross-vendor interoperability. It failed. Vendors lobbied the standards committee heavily having the expected results. Adoption was slow, incomplete, and/or simply inaccurate. As well, the DICOM standard allowed proprietary communication to still take place. While you got your image, that CT scan just never was the same once it left vendor X's equipment.

      With the conversion of most of Europe and now a push for computerization in the U.S. movement is afoot through organizations such as IHE to finally mature this industry after some 25 years of infancy. However, doing so will be tough and doubtless protracted. For hospitals, replacing multi-million dollar equipment even in a good economy isn't easy and vendors are expected to remain consistent in their nature. The open-source community has been stepping up to the plate where they can and this might net some interesting results on the software side down the road but glue and viewers will only go so far. Archival (PACS) software could achieve much but is well beyond the reach of unorganized hobbyists.

      --
      Two of my imaginary friends reproduced once ... with negative results.
    24. Re:The key being ... by Vindicator9000 · · Score: 1
      Yes, but the article doesn't take into account that your average doctor knows SHIT about IT, and is often asking for the IT equivalent of us grafting a third leg onto a patient's forehead.

      Perfect (true-life) example from my job: A doctor saw a package product at a trade show for $100K. He came back to us and wanted us to recreate it for $10K. We told him it wasn't possible. He went to our Account Executive, who told us that we would be doing it, and for $10K.

      The crux of this project was a specialized medical camera that cost $10K, and would not work with our PC hardware. We suggested that he buy an off-the-shelf DSLR, which he refused. Again, went to the Account Executive, who okayed it. Great, now we're over budget, and we have a $10K device that doesn't work.

      So, we go to the camera hardware manufacturer, who now has us by the short hairs, and they tell us that they can write us a driver for $30K. Which is again okayed. The project is now 30K over budget, we still haven't bought the hardware for it, and they have us doing the project off the clock because they haven't budgeted for any labor costs.

      Two years later, it still doesn't work right. The doctor loudly proclaims to anyone who will listen about how the IT department doesn't care about his needs, and articles like this get written.

    25. Re:The key being ... by Vindicator9000 · · Score: 1

      furthermore, to clarify: there was nothing special about the medical camera that made it necessary. It was just a camera, made by a MAJOR electronics vendor, and rebadged by a major medical company, but requiring proprietary connectors and proprietary software to work. He had to have THAT ONE because it was part of the package he saw, even though it was 10x more expensive, and not as good as what we could have bought him from, say... Wal Mart.

    26. Re:The key being ... by Anonymous Coward · · Score: 0

      "If you need training, the system doesn't work"

      Maybe we should start by getting rid of all these cars, they obviously don't work because they require training to operate ...

    27. Re:The key being ... by Anonymous Coward · · Score: 0

      I can chime in here too. It works this way even with small medical outfits.

      We get no respect in IT because we don't carry fancy titles next to our names. One Doc goes to a conference, spends tens of thousands without consulting anyone. Now they're stuck with their shitty FileMaker database. Also office is a mix of Macs and PC's because one Doc decided he won't use anything but Macs. Their billing software is Mac-only and requires OS 9 or Classic 10.4. Fucking A.

    28. Re:The key being ... by Anonymous Coward · · Score: 0

      That is exactly what my teachers tried to jam into my brain the first day I showed up for a medical informatics course.

      As a doctor / tech geek myself, I believe any IT system should also cater to the doctor's and nurse's needs.

    29. Re:The key being ... by cavebison · · Score: 1

      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

      That's interesting, as I'm currently helping maintain a small EPI reporting system at a Perth hospital, aimed at checking isolates for emerging trends across different hospitals. This is directly used by the Microbiology lab technicians. It's in Access 97, believe it or not, running on last-decade PCs. Goes to show how much you can do by simply focussing on immediate goals with existing tech, instead of spending $millions on grand schemes concocted by grand consultants.

      I've also written an online system used by many hospital labs in Oz to share information about Staph infections and outcomes. Sounds grand perhaps, but it's not - again, a small, focussed web app addressing specific needs.

      For me, this is the work that satisfies. Focussed projects, working with the end users, helping them do what they want to do. But then I'm a freelancer, not an IT Solutions Consultancy with a big office and staff to pay.

    30. Re:The key being ... by oldhack · · Score: 1

      It's like the hopspitals are the restaurants of the economy where the numbers...

      --
      Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
  7. no shit by PhrostyMcByte · · Score: 5, Insightful

    Almost everyone who's ever used a line of business app could have told you this. Good LOB apps will ask the question "how can we use PC to make the experience more efficient?". Bad ones will just say "paper sucks, lets make it digital!" have the exact same fields a paper would have, but make you type it. The bad ones might be marginally easier for management because of their rudimentary search and reporting, but are usually no different or even worse for the actual day to day users.

    Yet management is continually suckered into thinking less paper == more efficient, and there are _a lot_ of bad LOB apps out there because of it.

  8. Uggggghhhh by WiiVault · · Score: 2, Funny

    Seriously having a centralized database won't save time tracking down something vs a massive filing "complex" in the basement? I'm sorry but that is just bullshit no matter what the study says. Thats like saying I would be better off with a folder full of images as opposed to Picasa and iPhoto to help manage. Perhaps the time spent would similar if I were a retard or a caveman unfamiliar with a PC. But I assumed people in the medical profession had some semblance of intelligence. At worst a computer should be no less effective, and hey it lets you sit on your fat lazy ass too!

    1. Re:Uggggghhhh by Anonymous Coward · · Score: 0

      If entering something into your precious database takes longer than before and documents have to be retrieved only seldomly, than you lose efficiency. If the system is designed to please management or whoever manages funds, it degrades efficiency of it's actual users.

      Last I talked to a doctor about hospital IT, he basically said they now have to scan in every paper form and manage digital duplicates of most of their data. Real hospitals aren't the pretty showcase nirvanas where every nurse, doctor and cleaner runs around with a laptop/pda and no paper in sight.

      Don't forget that medical records have to satisfy a host of regulations that your holiday photos can ignore. You can't just throw a database at every problem and call it a day.

    2. Re:Uggggghhhh by WiiVault · · Score: 1

      Yes, but you must young if you have never encountered the problem of lost paperwork. Anybody older than 50 is likely to have had this happen at least a handfull of times. Digital covers this problem (if done right), which I'm pretty sure was a major element of the pitch in the first place. Efficiency doesn't mean shit when the info is already lost.

    3. Re:Uggggghhhh by DuChamp+Fitz · · Score: 1

      Perhaps the time spent would similar if I were a retard or a caveman unfamiliar with a PC.

      And if you were a retarded caveman, what then?

    4. Re:Uggggghhhh by roguetrick · · Score: 1

      Then you're an illegal time immigrant and a drain on our health care system!

      --
      -The world would be a better place if everyone had a hoverboard
    5. Re:Uggggghhhh by PopeRatzo · · Score: 1

      I'm also surprised at Harvard's study. Just earlier this week an MIT study said exactly the opposite. That electronic records would also bring productivity enhancements that would save a bundle. The MIT study mentioned 40 billion over 10 years if I remember correctly.

      --
      You are welcome on my lawn.
    6. Re:Uggggghhhh by Anonymous Coward · · Score: 0

      You can buy an iMac and use iPhoto instead of putting your pictures in a paper album, but it won't save you money.

    7. Re:Uggggghhhh by Anonymous Coward · · Score: 0

      "Digital covers this problem (if done right), which I'm pretty sure was a major element of the pitch in the first place."

      This is where your premise fails. Everybody CLAIMS to do it right but nobody seems to actually deliver. Somehow, in the end, digital never seems to deliver what it promises.

      Paper is hard to screw up. If a paper record is lost, it is probably misplaced. If it is really lost, you probably know it (flood, fire, etc.) They can also be backed up.

      Digital is easy to screw up. If it is lost, it is really gone. It has all the same failure modes as paper plus additional ones.

      EVERY doctor I have every seen will ask for the same information whether or not it is in their files ALREADY. This includes facilities that have EMR's. I used to think long term health data would be nice but once again doctors don't seem to care. Blood work hasn't been done in a year, retest. Slight symptom change, new expensive test. What are you here for (ignoring the referral paperwork they required)? What does my health history matter aside from the stuff I can carry around on a single page (meds, surgeries, allergies, etc.)

      EMR's are a solution looking for a problem. Or more correctly, crappy software companies looking for a payday.

    8. Re:Uggggghhhh by Anonymous Coward · · Score: 0

      "The MIT study mentioned 40 billion over 10 years if I remember correctly."

      That would be considered a rounding error in our current health care expenditures. At once a large sum of money yet an insignificant expenditure in the grand scheme of things. You would probably be better off denying half of the scheduled back surgeries every year, at random. You would likely save more money and provide better outcomes.

    9. Re:Uggggghhhh by PopeRatzo · · Score: 1

      That would be considered a rounding error in our current health care expenditures.

      40 billion is nearly 20 percent of the cuts in Medicare Advantage that would be required by the Health Care Reform bill before the Senate. That's more than a "rounding error".

      When you figure that only about $.14 of every dollar Medicare Advantage pays to insurance companies actually goes to patient care, that 40 billion has just wiped out any reduction in benefits that keeping the HCR bill "deficit neutral" would require.

      The money paid to insurance companies is a much less efficient way to pay for medical care for citizens than even the worst government bureaucracy.

      --
      You are welcome on my lawn.
  9. All depends on how it is implamented by wisnoskij · · Score: 1

    I know when I did some work for a school library one part that stood out as very inefficient was the registering of new books.
    They had a word document template, like one that could be printed off, you had to fill them in then email them to the main office (so that is 200 documents if their are 200 new books).
    Then they would go threw them and enter them into a database.

    And i am sure a lot of people even printed off the sheet.

    It does not matter how fast and efficient using a computer is, if everyone continues to treat them as electronic paper or do everything in paper and then transfer it over.

    No technology will instantly make huge advancements in efficiency if the users do not know to use it properly.

    --
    Troll is not a replacement for I disagree.
  10. Of course... by Anonymous Coward · · Score: 4, Insightful

    If you hand a bunch of Luddites a computer system they will tell you it isn't saving them any time.

    The system has to meet the needs of the users.

    The users have to want to use the system.

    If you don't meet both of these requirements it will fail.

  11. Workflow by Anonymous Coward · · Score: 0

    It has to do with adhering to the old systems workflow, and not adapting new workflow systems to the new technology.

    End of story, nobody thought to update the workflow, so of course, it won't be any faster.

  12. like rain by saiha · · Score: 1, Interesting

    So which is it, irony or coincidence that I am reading this online within minutes of this being posted?

    1. Re:like rain by el_tedward · · Score: 0

      I had to wait several minutes to be able to respond to your comment.

  13. Wow, gee, really? by PakProtector · · Score: 1

    Just because something's new doesn't mean it's necessarily better than the old?

    ...And the Bureaucracy died in a landslide of paperwork...

    --

    Edward@Tomato - /home/Edward/ man woman
    man: no entry for woman in the manual.
    "Qua!?"

  14. Computers != Saving money by AmigaHeretic · · Score: 1

    Computers in hospitals have never been about saving money. Of course they cost more than writing stuff down on paper and shoving it in a folder.

    Computers are about 'patient safety' and are a tool to help elminate errors. Test results came back from the lab? Computer system gives messages/popup reminders to actually CALL the patient and let them know the results are in. Non computer system, a piece of paper comes back saying you have cancer and the nurse files it and thinks "I'll call when I get back from lunch" and then forgets to every call you and let you know the bad news.

    So, yeah of course a computer system cost more, but computers 'can' do some neat things.

    1. Re:Computers != Saving money by el_tedward · · Score: 0

      they save money on time, not paper

    2. Re:Computers != Saving money by Spliffster · · Score: 1

      I am working in a large Hospital as software engineer. I can tell you, that it's more safe to give a nurse a piece of paper than a computer. why? because the nurse's primary goal is to treat the patient and to to use this scary computer thing!

      It might be about safety (i don't answer you the answer) but -- as I see it -- it is about having alot of data (especially history and current results) at your fingertips (from the perspective of a doctor). This safes time and enables them to see the bigger picture in less time. However, most of the data doesn't enter itself into the systems.

      Cheers,
      -S

  15. Like my Father Said ... by foobsr · · Score: 2, Interesting

    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)
    1. Re:Like my Father Said ... by Idiomatick · · Score: 1

      Yet my grandfather bought a mainframe for his tile distributor and it saved him tons of money.

      Reminds me of... "Its not the size it's how you use it."

    2. Re:Like my Father Said ... by An+anonymous+Frank · · Score: 1

      I don't think computers ever saved anyone "work"; we're able to do so much more and/or do it faster, but we're then expected to do that much more, and/or do it that much faster, and often cannot ever conceive of "going back".

  16. Surgically Remove One Myth... by BlueBoxSW.com · · Score: 1

    ... and surgically insert another.

  17. Corporate is as corporate does by GodfatherofSoul · · Score: 1

    From what I've seen of the corporate world, these decisions are made by two groups of competing bullshit artists who've worked their way up to command decisions. One is trying to sell you a product that may or may not do what you need and the other is trying to low ball you *regardless* of what the sticker price is. Management needs to either promote more techies to these levels or put them in places where they can make *real* feedback on the process.

    --
    I swear to God...I swear to God! That is NOT how you treat your human!
  18. Let me add to this by Etrias · · Score: 2, Interesting

    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.

    1. Re:Let me add to this by Anonymous Coward · · Score: 2, Interesting

      Little known fact: we doctors are encouraged to use sloppy handwriting as a way to prevent drug order forgeries. We're like rockstars, we have public and personal signatures.

    2. Re:Let me add to this by demonlapin · · Score: 1

      don't want to learn a different system for keeping records.

      Well, isn't it obvious? Many private-practice physicians work at multiple hospitals as well as their own clinics. They get little or no benefit from electronic records, but there is a very definite cost in having to learn how that hospital's system works, remembering their username/password (often username is assigned by IT and passwords have differing requirements for complexity, frequency of change, etc.), where certain pieces of information have to be entered...

      By contrast a paper chart is simple and straightforward; the only difference is whether it's front-to-back or back-to-front for oldest to most recent notes.

      I can easily get everything I need from a dictated clinic note or admission/discharge note, which is already available in the EHR - so why would I make my life harder by becoming a typist as well as a physician?

  19. The crux of the matter by stimpleton · · Score: 1

    Larger modern health care environments such as large hospitals, regional health committees, working groups etc, largely boil down to two Us-and-Them viewpoints.

    One is Management and the other is doctors/nurses, the later arguing they should make the health care decisions, and essentially have primary say in the implementation of said environment.

    The result from an Information Systems viewpoint is that it is pushed from management with little buy-in from health professionals.

    With all due respect to Dr Himmelstein he firmly sits in the second camp - doctors should have the say in the running of a hospital. He is also against "administrative waste" - the old "too many admins in the hospital" arguement.

    Thats all well and good, but when the balloon goes up, and there are questions to answer, administrator's administrate, while doctors do what they should be doing: patient facing time.

    --

    In post Patriot Act America, the library books scan you.
    1. Re:The crux of the matter by MichaelSmith · · Score: 1

      Its funny because I have to go to the local public hospital regularly for my broken arm. Renovations are under way and the Fracture Clinic has acquired a nice new office since I started going there. The new office has attracted a manager who divides his time between chatting up the receptionist (he must be desperate) and standing outside empty consulting rooms saying c'mon, a patient could be in here.

    2. Re:The crux of the matter by Another,+completely · · Score: 1

      Maybe I'm misinformed, but don't most (private) U.S. hospitals treat doctors like customers? In several computer systems that I saw in New York state, they were providing different report styles and different input methods (from e-mail to hand-written) for the different doctors. The reason I was given was that they had to do this, since doctors who didn't feel the hospital system suited their unique requirements would suggest different hospitals to their patients. The resulting computer systems were very inefficient, compared with what they could be with more cohesive planning.

      Also, isn't a large part of paperwork involved with billing, and filing the right forms with the various payers? I don't suppose the insurance and government agencies publish WSDL interfaces for their claims, so that probably needs to be transcribed to paper, right? What portion of administrative cost goes to copying data by hand from the computer?

      It would be interesting to see the same study in a single-payer environment; or even in a simpler mixed-payer environment where supplementary coverage claims are filed by the patient, rather than the hospital, and the competition between hospitals for the preference of independent doctors is a bit less fierce. It may be that the U.S. healthcare system is just an extreme case.

    3. Re:The crux of the matter by DuChamp+Fitz · · Score: 1

      Is it the Michael Scott Fracture Clinic, perchance?

  20. It is all really a pretty rainbow? by Anonymous Coward · · Score: 0

    I wanna know the specs for a computerized hospital wide system, service interruptions (hardware failure, ...)? My life is not just in the hands of a doctor, a 7 year or so trained medical professional, but a misanthropic programmer that drinks to much coffee. All i am saying there are cons to a computer system as well.

    1. Re:It is all really a pretty rainbow? by tg123 · · Score: 1

      I wanna know the specs for a computerized hospital wide system, service interruptions (hardware failure, ...)? My life is not just in the hands of a doctor, a 7 year or so trained medical professional, but a misanthropic programmer that drinks to much coffee. All i am saying there are cons to a computer system as well.

      Having worked in medical records with a paper based system your life is also in the hands of the clerk who handles your records.

      You just gotta hope that the clerk can find your chart that one of the nurses or a specialist as locked in there office when your sitting in emergency wondering why the doctor has not seen you yet. "Can not see the patient without there chart".

  21. Yeah but... by zenasprime · · Score: 1

    ...have you actually seen the so called "software" that hospitals are running their businesses with? I'm lucky if our software doesn't crash, lag, not save records, etc while I'm trying to do my work. And don't even get me started on our "administrator", who routinely doesn't even bother to test whether or not an upgrade is going to work on the test server, if they even had a test server (which they don't).

    1. Re:Yeah but... by nedlohs · · Score: 1

      If he doesn't have a test server, then of course he routinely doesn't test upgrades on it - it would be physically impossible to do so after all.

    2. Re:Yeah but... by zenasprime · · Score: 1

      That would be my point. It's impossible for them to test upgrade on a mission critical system because they don't even have a testing environment to make sure the entire thing doesn't crash after the upgrade. You'd think they would invest in one considering that every time they do an upgrade, teh system crashes and it doesn't come back up for a week as they try and figure out what went wrong. ./sigh

    3. Re:Yeah but... by MichaelSmith · · Score: 1

      When I broke my arm there was a long wait for X-Ray because their system had a virus. Later I got my X-Rays on CD and it came with convenient DLL files to help load the data. If I ran windows I would have been a bit worried about that.

    4. Re:Yeah but... by nedlohs · · Score: 1

      I've never seen a place where the administrator gets to spend money/time on the stuff he wants to.

      But yes you could have a moron who decided the test server budget was better spent on Twinkies.

  22. wrong metric by timmarhy · · Score: 1

    to hell with wether it saved a dime. did it improve patient outcome? cost saving it the wrong wrong WRONG aim of a hospital.

    --
    If you mod me down, I will become more powerful than you can imagine....
    1. Re:wrong metric by gzipped_tar · · Score: 1

      Are for-profit hospitals illegal in the USA?

      --
      Colorless green Cthulhu waits dreaming furiously.
  23. okay, this really bothers me by el_tedward · · Score: 0

    But I'm glad it says that these systems are targeted towards management. It sounds to me like a lot of the people running hospitals enjoy buying themselves fancy toys.

    I work as a go-fer at a doctors office. There's two doctors there with roughly a dozen nurses. I wouldn't have a job if we didn't have the shit paper filing system we currently have. Several people who work there wouldn't have jobs if we didn't have the shit filing system we have there. It's a waste of my time that I could be spending at collage not doing homework. Is that a bad thing? No, I'm gana grow up to be a l33t computer hacker and get lots and lots of money. Those nurses that get fired when the office gets the electronic records keeping may go on to get licensed as hardcore full on RNs. There's plenty of room in the expanding healthcare system for more nurses. It's not going to kill jobs, but a system of server to server sharing (yeah, someone needs to find a way for this to work so doctor in california can find out about the STDs I got diagnosed with here in [place where the job market is bad]) mah patient info would eliminate errors when things are coded properly (I do get quite annoyed with myself when I find a file I put in the wrong place, but our file system has more room for error than you think it does. Files just take... a long time to find).

    Also, we have an accountant who is going over all this stuff, so hopefully they read this article and not waste money on things the doctors really don't need. Like buying a sports car, a prius, and then a new battery prius to save the environment.. The doctors are currently in a legal battle of who has the biggest e-peen though, (50-50 share in the company, tee hee) so I really don't care that much about how things turn out at the office.

    Also, I know all this stuff because I work for my mommy.

  24. Designed for Entrepreneurs by wrook · · Score: 4, Insightful

    Computerized health care systems are not designed for the benefit of hospitals. They are designed for the benefit of entrepreneurs.

    Health care is a multi-bazillion dollar industry where information is managed via bearskins and stone knives. Development of an integrated computerized health care system will net the intelligent investor more money than even Microsoft can dream about.

    This is the message that people I will call "serial entrepreneurs" pitch. Their intent is not to build such a system (that would be nigh on impossible given the absolute chaos of incompatible processes that currently exist in hospitals). They simply want to build a system that looks close enough that stupid investors will throw millions of dollars at it. The potential payoff is so big (seemingly) that people will keep throwing money at it even after said entrepreneurs have razed and burned a stack of companies.

    Of course, eventually there *will* be a company that succeeds (mostly by accident). That company will run suspiciously like SAP where there will be a very complex set of computer programs designed to support an even more complex set of processes. These processes in turn will have nothing to do with the underlying business of providing health care. However senior management will be ecstatic that they finally have a unifying computer based process, and the only people who fully realize its true futility will be the people doing the work. They, of course, will be ignored.

    1. Re:Designed for Entrepreneurs by terryducks · · Score: 1

      Computerized health care systems are not designed for the benefit of hospitals. They are designed for the benefit of entrepreneurs.

      Yes & No.

      Hospital Information Systems suffer from the "Enterprise"y bug. This is no different from any huge enterprise software system (I'm looking at ERP) in scope. Each vendor wants to rule the roost so the stuff barely talks to itself. Granted I did this in the late 90's / 00's.

      For example, the hospital already had a clinical, lab, financial and registration system in place. (quite nice BTW - terabyte database supported 400 people simultaneously with SUB-SECOND response time). they brought in another enterprise wide "health care management system" with the same "features" but need a massive data center to support the activity on a Windows Server 2000 (i think). Think hundreds of servers stacked like Legos to get close to the throughput and disk of 1 medium sized mainframe

      Problems: 1. you cant' get the data out of the old system (w/out massive time/human inputs) 2. both systems had incompatible registration/account management "ideas". 3. tied everything together with a big buck passer (see eGate talking HL7 - exact same functionality of Java Messaging Service (queues, guaranteed delivery etc)) 4. a lab "silo" hanging off the side. (complete registration, billing, reporting etc)

      Basically, the systems fought. The clinical system wanted the episode of care tied to a ICD9 code (what's your diagnosis/problem). The registration/financial system wanted the episode of care tied to dates. So the patient's records would bomb in the clinical side when the patient was readmitted for the same diagnosis on a different day. Mothers in labor typically did this. False labor pains in the night, come in & admitted. Nothing to worry about so the mothers were checked out. Next day mother checks in with real labor starting and boom the clinical system rejected the record.

      Most of us in IT (lots of nurses) - "fuck registration" make sure that patient gets care. We'll fix registration/billing later.

      Insurance co.s - Fuck you. "I'm sorry this bill has a wrong sub-sub-sub code - rejected". Fix the "error" w/ medical staff investigation and "I'm sorry this bill is rejected because it's one minute past the 30 day date for care". Fix resubmit. Oh, we'll can't pay everything - you're late and by contract we'll pay $$CARE - $$FEE = .25. Call someone who cares. Because we're the phone coinsurance company *snort*.

      Granted nothings perfect 100% of the time but you get tired of the ins cos. real quick.

    2. Re:Designed for Entrepreneurs by some-old-geek · · Score: 1

      Computerized systems are not designed for the benefit of users. They are designed for the benefit of entrepreneurs.

      Fixed that for you.

    3. Re:Designed for Entrepreneurs by Anonymous Coward · · Score: 0
      Should be read in the narrators voice from "The Hitchhiker's Guide to the Galaxy"

      Of course, eventually there *will* be a company that succeeds (mostly by accident). That company will run suspiciously like SAP where there will be a very complex set of computer programs designed to support an even more complex set of processes. These processes in turn will have nothing to do with the underlying business of providing health care. However senior management will be ecstatic that they finally have a unifying computer based process, and the only people who fully realize its true futility will be the people doing the work. They, of course, will be ignored.

  25. What about VISTA? by Anonymous Coward · · Score: 0

    Did the Harvard study include the computer system used in the Veterans' Administration hospitals?
    It is an in-house system started in about 1980.
    It seems to serve the VA particularly well -- doctors, patients, labs as well as management.
    It is known as VISTA, and it can be tried and downloaded from a VA server.

    1. Re:What about VISTA? by cashman73 · · Score: 1

      You mean, something called "Vista" actually works?!?! This is news!!!! ;-)

    2. Re:What about VISTA? by Shane+dot+H · · Score: 1

      Not to mention its source is available as public domain code. Part of the problem is that the VA has different incentives than most hospitals. The VHA is an insurance company that owns the hospitals, the equipment, and pays the doctors a fixed salary. It keeps the same patients for decades, and has an incentive to get records right from the get-go, because they know they'll be paying for that patient's treatment down the line. In that sense, some of the benefits of the VA's electronic health records system aren't easily mimicked by the private sector, but it certainly is a good start.

      In any case, I'm curious too as to how VistA fares compared to these other systems.

  26. Timing by snorris01 · · Score: 1

    This study sure seems conveniently timed in relation to the current healthcared 'debate'.

    Here's to hoping it is good science and not mostly partisan.

    I'm getting tired of that crap.

  27. Let me explain... by denzacar · · Score: 4, Insightful

    You: Computers have made my life much easier.
    Harvard study: Computers don't save hospitals money.

    Note the slight difference there?

    --
    Mit der Dummheit kämpfen Götter selbst vergebens
    1. Re:Let me explain... by Rakshasa+Taisab · · Score: 1

      So what you're saying is that doctors used that efficiency increase to improve patient care, rather than cost cutting. This be good no?

      --
      - These characters were randomly selected.
    2. Re:Let me explain... by daveb · · Score: 5, Insightful

      >You: Computers have made my life much easier.
      >Harvard study: Computers don't save hospitals money.

      >Note the slight difference there?

      yes - but you missed the bit about efficiency. "Computers have made my life much easier." is usually how we express efficiency.

      Over a decade ago I did a stint at a hospital looking after the pathology database. When it was down and paper records were required then lives were at risk due to the lack of efficiency (time spent accessing paper). It honestly scared me!

        I'm sure things are much much more reliant on computers now. Computers are not just for the hospital admins.

    3. Re:Let me explain... by denzacar · · Score: 3, Funny

      Good? For whom? Patients? Screw them!

      We are talking bottom line here sunny.
      And that bottom line better be in black and with plenty of big numbers.

      Now get out of my way, I have to practice my for the annual Doctor's Golf TournamentTM. It is for some charity or some other bullshit excuse.

      --
      Mit der Dummheit kämpfen Götter selbst vergebens
    4. Re:Let me explain... by Anonymous Coward · · Score: 0

      "much easier" would save them more money if absolutely nothing changed besides removing the paper and adding the computers.

      But considering how they are capable of taking on more patients in a shorter time thanks to the more efficient method of computing, more money will obviously be spent.

      I can spend barely 5-15 minutes seeing the doctor if i'm a little ill, previously that would have been much higher.
      And with cancellations taken in to consideration, the amount of wasted time would be far worse.
      Not to mention that the fast access time of computing databases for patients in emergencies, all those seconds count.

      (mind you, this is from the UK here, not sure if that would count)

    5. Re:Let me explain... by Anonymous Coward · · Score: 0

      You've been watching way too much Scrubs...

    6. Re:Let me explain... by colinrichardday · · Score: 1

      When it was down and paper records were required then lives were at risk due to the lack of efficiency (time spent accessing paper). It honestly scared me!

      I'm sure things are much much more reliant on computers now.

      Except when the computers go down.

    7. Re:Let me explain... by Anonymous Coward · · Score: 0

      At least part of the difference may be that becoming more efficient can actually cost them money due to fee-for-service.

    8. Re:Let me explain... by Anonymous Coward · · Score: 0

      Answer: Bureaucracy, and keeping too many people employed who are not part of the primary function of the business.

      These same numbnuts are busy buying things they know nothing about.

    9. Re:Let me explain... by budgenator · · Score: 1

      Nature abhors a vacuum. For example in 4 B.C. a typical Roman Legionnaire carried 60 to 80 pounds of armor and equipment into battle, today over 2000 years later with our lighter and stronger materials the typical US infantryman carries 60 to 80 pounds of equipment and armor into battle! Obviously as equipment weight was reduced due to technology it created a vacuum that filled in with more equipment! Same thing happens in medical care and hospital care as efficiency increases, additional requirements will at least equal the savings.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    10. Re:Let me explain... by CAIMLAS · · Score: 1

      Not if the dropping patient care quality statistics are any indication, no. "Patient care" is not getting better.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
  28. Wrong question addressed in study: by oDDmON+oUT · · Score: 1

    Background/true story:

    Mid 1990s.

    Large hospital invests in an extremely expensive computerized charting system.

    Staff were not paid to chart after their shift concluded. Instead, despite being overworked, they were expected to chart as they went through the day.

    Said charting system had a key combination called "Magic Lookup", whereby pressing two keys for a given patient data field inserted the value put there from a previous charting input (i.e. temperature, blood pressure, ambulated, etc., etc., etc.). When used, this combo would give an audible chirp, of a quite different sound than that of regular input.

    At the end of shift one could stand in the hallway and listen, while a five minute or so chorus of crickets erupted as staff made heavy use of "Magic Lookup" in order to get the hell out the door.

    This was an excellent opportunity for such charting f*ck ups such as "Ambulated = YES" a bilateral stroke patient to occur.

    It was also an excellent reason for my choosing a career in IT, rather than the nursing degree I was going for at the time.

    I would love to see Yale do a study measuring the negative patient outcomes affected by IT systems put in place by hospital administrators who've been served vendor Kool-Aid® over the last 15 years.

    --
    Some days it's just not worth
    chewing through my restraints.
  29. Parkinson's laws by vurtigalka · · Score: 5, Insightful
    Results like these shouldn't surprise anyone aware of Parkinson's laws. From Why it is Important that Software Projects Fail:

    The boundless creativity of politicians and bureaucrats to develop new and more complex regulation is bounded only by the bureaucracy's inability to implement them. The absolute size of the bureaucracy is constrained by external factors, so the only effect of automation can be to increase bureaucratic complexity.

    Parkinson's laws are as valid and insightful as always. If someone by chance have missed them, here they are:

    Parkinson's First Law:
    Work expands or contracts in order to fill the time available.

    Parkinson's Second Law:
    Expenditures rise to meet income.

    Parkinson's Third Law:
    Expansion means complexity; and complexity decay.

    Parkinson's Fourth Law:
    The number of people in any working group tends to increase regardless of the amount of work to be done.

    Parkinson's Fifth Law:
    If there is a way to delay an important decision the good bureaucracy, public or private, will find it.

    Parkinson's Law of Delay:
    Delay is the deadliest form of denial.

    Parkinson's Law of Triviality:
    The time spent in a meeting on an item is inversely proportional to its value (up to a limit).

    Parkinson's Law of 1,000:
    An enterprise employing more than 1,000 people becomes a self-perpetuating empire, creating so much internal work that it no longer needs any contact with the outside world.

    Parkinson's Coefficient of Inefficiency:
    The size of a committee or other decision-making body grows at which it becomes completely inefficient.

    1. Re:Parkinson's laws by Anonymous Coward · · Score: 1, Informative

      One thing that always amused me is the jaw-dropping amounts of money spent by bureaucracies, especially large government, on enforcing rules designed to increase efficiency.

      For some large government projects, it gets to the point that it would be cheaper to simply hire 10 different companies to all produce the software product that you wanted, and then simply pick the best one.

      Meanwhile, in the supposedly efficient government system, the actual project is done by 1 software team that is red-taped to death, it ends up costing 20x more than it should have, and then still fails.

      Even if in my hypothetical scenario of using 10 different companies it turns out that 9 of them produce a rubbish product, you'd still be better off than spending 20x the sane amount and failing. You could literally have some huge fraction of your suppliers simply pocketing tax payers' money and walking off with it and still save money by firing all the paper-pushers.

      Posted as AC as currently I'm a subcontractor to an outsourced supplier providing services to a branch of a department investigating... you get the idea.

    2. Re:Parkinson's laws by tomhath · · Score: 3, Insightful

      For some large government projects, it gets to the point that it would be cheaper to simply hire 10 different companies to all produce the software product that you wanted, and then simply pick the best one.

      Bingo. You have just pointed out why capitalism beats socialism. Nine private companies fail, one emerges as the industry leader.

    3. Re:Parkinson's laws by dschmit1 · · Score: 1

      Or, just go with what you want, you have a choice: fast, good, cheap. Pick two.

    4. Re:Parkinson's laws by jollyreaper · · Score: 2, Insightful

      Bingo. You have just pointed out why capitalism beats socialism. Nine private companies fail, one emerges as the industry leader.

      Then the industry leader becomes so large it steamrolls competition while at the same time producing flabby, uninspired software. This bloated behemoth will persist long past when it should have mercifully died in its sleep and it takes ages for incompetence to erode that market lead, to allow competitors back into the marketplace. And when you think it might finally take in that final breath, the capitalists running the thing will successfully lobby the government for a bailout, not even blinking as they suck the government welfare teat. But you can bet they'll look down on poor people who might do the same.

      --
      Kwisatz Haderach
      Sell the spice to CHOAM
      This Mahdi took Shaddam's Throne
    5. Re:Parkinson's laws by happyhamster · · Score: 1

      Except that the work on the same project was done TEN times at TEN TIMES THE COST. Either the client pays for 10 projects itself, or, if the client only pays the winner, then investors take the hit, who pass it to workers and other members of the society in many ways. Ultimately, the cost is paid by the society either way. You would be much better off developing one or two projects under socialism instead.

      Yes, socialism has its inefficiencies, but capitalism has its own problems that rival or exceed those of socialism. Just look at the crisis we are living through right now.

      Mindless bashing of socialism is pointless.

    6. Re:Parkinson's laws by mjwx · · Score: 1

      Mindless bashing of socialism is pointless.

      But liberal use of irony isn't. I think the GP was pointing out that pure capitalism fails for the same reason as pure socialism, both philosophies end up with a single vendor that inevitably lowers quality, capitalism just takes the long road to a single vendor world.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
  30. They save lives, not money by Anonymous Coward · · Score: 0

    Remember - Harvard has other agendas beside the public good.

  31. Computers let you employ dumber, cheaper people by petes_PoV · · Score: 1
    Most IT is about dumbing down. It lets you shed highly trained, expensive staff who are hard to recruit by replacing them with some electronic "brains" and a pair of minimum-wage hands to carry out the machine's orders. For most organisations the key driver is not cost (no matter what they tell you), it's risk. Risk that people will fail, risk that someone else will get to market before them, risk that their tame geek will walk away and take all their I.P. with them, risk that they aren't seen to be using "best practice" and risk that the shareholders will ask why they're doing what everyone else is doing. If that means following the herd and computerising everything - then so be it.

    It's a bit like having an autopilot on a plane, it does most of the work (thank god) and only needs a pilot to make sure everything is running properly and to reassure the pax that there's a credible-looking face at the pointy end of the plane.

    There are a few places were employing IT has, genuinely made things faster or reduced their cost to a point where they can be deployed more readily. Crime detection: fingerprints, DNA and surveillance cameras (with facial recognition) are the most ovbious. Whether that can be considered progress, is however, another question entirely.

    --
    politicians are like babies' nappies: they should both be changed regularly and for the same reasons
  32. Bollocks by iamacat · · Score: 1

    Palo Alto medical foundation implemented online system to allow any doctor or patient to access patient's records and exchange e-mails. If you see a specialist and then go to a primary care physician for annual exam, he/she immediately sees what happened to you and what tests need to be done. Many routine matters like prescription renewals or questions about OTC drugs can be handled without revisiting the clinic. How is that not saving money or even health/lives?

  33. Monetary efficiency by Mathinker · · Score: 1

    > an efficiency benefit

    Your post assumes that efficiency is measured in units of lives saved or care given, but the administration is measuring efficiency in units of money. If your observations were widespread, the computerization should save the hospital money, but the study says otherwise.

  34. Computers need to be implemented correctly... by mgchan · · Score: 3, Interesting

    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.

  35. Remote access to specialists by The+Famous+Druid · · Score: 2, Informative

    I recently showed up at the ER late at night, with a broken wrist.
    The ER doctor looked at the X-rays, then called the fracture specialist at home, who looked at the X-rays on his home computer, and passed on his advice to the ER doctor.

    Let's see them do that without computers.

    --
    Quidquid Latine dictum sit, altum videtur (anything said in Latin sounds important)
    1. Re:Remote access to specialists by smellsofbikes · · Score: 1
      I had a similar experience. No paper anywhere: the PA asked me what hurt, sent me to the x-ray department. The nice lady there looked at her computer, where she saw my description and the PA's inspection, took some pictures, and sent me back. The doctor looked at the x-ray pictures and gave me instructions on how to deal with a separated shoulder.

      Even better is the family physician I go to. He says "okay, I'm prescribing you this. What pharmacy do you use?" I say "uh, this supermarket that's about at State Street and Governor's Street" and he hits a button on his laptop and says "it'll be waiting for you when you get there." Now that's just flat-out awesome.

      --
      Nostalgia's not what it used to be.
    2. Re:Remote access to specialists by winwar · · Score: 1

      "The ER doctor looked at the X-rays, then called the fracture specialist at home, who looked at the X-rays on his home computer, and passed on his advice to the ER doctor.

      Let's see them do that without computers."

      You do realize that they successfully treated wrist fractures all the time before computers? My brother was one of them. Of course, in the "olden days" doctors didn't need an expensive online consult to do their job. I don't recall my brother needing an ER doctor and a fracture specialist for a routine fracture. Perhaps they should spend less on tech and more on good doctors....

    3. Re:Remote access to specialists by mgchan · · Score: 1

      I'm guessing it wasn't an obvious fracture, the ED is pretty good at picking up most fractures on their own. Or else they were looking specifically for something like a hidden scaphoid fracture which mandates much more aggressive treatment.

      Your point is taken, though. Without computers management of that patient probably wouldn't have changed. Except that if a homeless guy shows up like that, they say wear this splint and see the orthopedist tomorrow, and it turns out he needs quick surgery but he never shows so he has some bad outcome, the ED is now liable for not keeping him there.

  36. How you save money in the health system by prefec2 · · Score: 1

    Honestly if you want to increase the average health care, which means the health care for most people and only pay 50% of what you pay now, just change your health care system to any system in West Europe (except the British one). Even the German one is better and that still sucks. BTW computer can be a helpful tool to manage data, but that is often not the real problem. In most cases it is bad management, induced by the wrong goals.

  37. Depends by Mathinker · · Score: 1

    > Dragging and dropping a file, though.. that's easier than using mv blahfile toblah

    IMO, that's only true if both the source and destination windows are already open in the GUI (and even then, perhaps only if the file you want to drag is already visible in the source window and you don't have to scroll or resort to find it). Or, of course, if you are typing-challenged. Otherwise, typing

            mv /path/to/source/file /another/path/to/destination/directory

    is almost certainly easier than find+clicking the seven (or more, depending on how you do it) parents of the paths in question and then dragging and dropping.

    1. Re:Depends by ickpoo · · Score: 1

      Particularly as you would be typing tab in there to auto complete most of the path.

      --
      I am not a script! .Sig?
    2. Re:Depends by pwfffff · · Score: 1

      Wow, no wonder you don't like GUIs; you suck at them. If I have my music folder open and I want to move it all to a directory deep in my phone, all I have to do is look to the left of the window where the directory structure is, scroll up to the root drives, click a few plus signs, and then drag and drop. You should also never have to scroll or sort to find a file (though you might want to sort if moving several files by date modified or something). Just start typing it's name, the window will find it for you, or at the very least put you in the right ballpark. And really how many times do you blindly copy things via command line anyways? At least half the time you're going to do an ls and some scrolling and sorting anyways.

      So it's either 50-ish keystrokes or a scroll and four clicks. I'd rather not take my hand off the mouse. Probably the MOST work you could do without doing something stupid would be to open up a new window and manually type the directory name. Of course, that's still only about half the work of typing out BOTH directory names.

  38. NHS Comparison by asc99c · · Score: 1

    For a while in the UK, the government has been spending billions of pounds on NHS IT systems. There is enormous potential to improve the situation, but so far it just hasn't been used. The prime example is electronic medical notes as mentioned in the article.

    Currently, I live and work 22 miles apart. I'm only allowed to use the doctor near my home, even though they are only open during working hours. The reason for this is my medical notes - f I need an emergency home visit (I never have) they will need my medical notes. Therefore it's essential my doctor is the one near my home. The government has spent millions on electronic systems for keeping these medical notes electronically, instead of paper based. Yet they somehow can't share the notes between two surgeries. If they could, it would vastly improve patient care. I could have a half hour trip to the doctor for my asthma checkup, instead of needing half a day off work. And if I ever visited hospital they would be able to see all notes taken about me by my GP. Although in my case there's nothing really to know.

    In terms of saving money, I actually agree with the current intended usage. Computers currently will only be able to save money on administration type work. I don't think they will be able to significantly help doctors save money on direct patient care. That task is too difficult for computers right now, which is why we pay doctors a lot of money to do the job. I suppose it depends on where you draw the line between admin / patient care. What would scheduling operations, along with marshalling the resources of operating rooms, and correctly trained doctors and nurses fall under? I'd call that admin and say that it's the sort of thing a computer could probably do better than a person.

  39. Efficiency? by denzacar · · Score: 1

    "Lives were at risk due to the lack of efficiency"?
    What part of "money" did you not understand?

     
    See... the good Doctor Himmelstein would like to run a hospital (whose job is to save lives and provide the unquantifiable product such as health) as a slaughterhouse.
    Bodies come in - work is done on them - bodies come out and you get money. Simple and straightforward.

    Aaah... but hospitals can't be run as a profit-based business - cause they are not. Hospitals provide "service" needed to run the society.
    You know... just like other public service "businesses" like police, fire department, army, public education...

    So, your idea of efficiency having to do with providing the said service, and idea of efficiency Doctor Himmelstein has (I can't help imagining thunder and lightning in the background every time I say that name) - are two VERY different things.
    His efficiency calculation only has to do with money spent per body coming in and money gained per body coming out.

    Now... if you could somehow CHARGE the patients for every time a computer is used... Hmmm...

    --
    Mit der Dummheit kämpfen Götter selbst vergebens
    1. Re:Efficiency? by Anonymous Coward · · Score: 0

      >"Lives were at risk due to the lack of efficiency"?
      >What part of "money" did you not understand?

      The summary (who rtf anyway) claimed " The study also showed most of the IT systems were aimed at improving efficiency for hospital management — not doctors, nurses, and medical technicians."

      The guy talking about being worried about downtime is calling BS on that claim. The article is not just about the $$ as you suggest

    2. Re:Efficiency? by Random_Goblin · · Score: 1

      See... the good Doctor Himmelstein

      it's pronounced "Homm-el-steen" ...

    3. Re:Efficiency? by Kierthos · · Score: 1

      Do you also say Froaderick?

      --
      Mr. Hu is not a ninja.
    4. Re:Efficiency? by LordKronos · · Score: 1

      >>Lives were at risk due to the lack of efficiency
      >What part of "money" did you not understand?

      I guess I've always had this silly idea in my head that "patient life at risk" = "hospital at risk of losing money in lawsuit".

    5. Re:Efficiency? by denzacar · · Score: 1

      Not if the patient is just mostly dead.

      And there is more than one way to "skin a patient".
      Plenty of diseases and injuries heal by themselves and leave only very slight marks on the body. Save on "free" medication and nurses.
      Broken leg - don't waste a cast, give him a bandage. It can be reused later. Syringes and needles too. Just boil them a little.

      And in most cases, it pays to gamble. Out of 1000 patients with a cold, only 1 or 2 may actually die from it - and there is always a chance that they wont sue.
      Just rush them through the system as fast as possible, and if they do happen to sue - hospitals can afford better lawyers.

      --
      Mit der Dummheit kämpfen Götter selbst vergebens
    6. Re:Efficiency? by budgenator · · Score: 1

      Aaah... but hospitals can't be run as a profit-based business - cause they are not.

      That's because of IRS regulations in the US, they literally have to spend all of the money on some kind of expense real or imagined. That's why there is no incentive to save money, they are happy to spend US$150,000.00 on a fund raises that raises $30,000.00

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
  40. So? by UnixUnix · · Score: 1

    They save lives, not money.

  41. OT but you can probably help by MichaelSmith · · Score: 1

    I get my X-Rays in DICOM format from my public hospital. I convert them to PNG and post them on my blog. I must have a DICOM library loaded because gimp will read those files on ubuntu but it refuses to load some of the files, in particular the more recent ones.

    Do you have any suggestions for reading DICOM which don't involve running windows and using the DLLs on the CD from the hospital? Thanks.

    1. Re:OT but you can probably help by peter+sisk · · Score: 1

      JDicom is a free, Java based DICOM library. You should be able to do pretty much anything you need to with that. Get it at http://members.chello.at/petra.kirchdorfer/jdicom/

    2. Re:OT but you can probably help by MichaelSmith · · Score: 1

      Thanks. I will take a look.

    3. Re:OT but you can probably help by mgchan · · Score: 1

      JDicom works, there are many other stand-alone DICOM viewers. I've used a command line program, I think dicom2 or something, that would extract images directly from the DICOM file into a regular image format. DCM4che is a fairly large open source collection of utilities which may also have something useful, though I am only now getting familiar with it.

      There are a couple native linux GUI viewers but none of them were particularly good in my opinion.

  42. Hospitals implement tech badly. Lose benefits by syousef · · Score: 1

    News at 11.

    Seriously, if you don't have improved efficiency after a tech implementation, you've done it wrong. Try tying vendor's and staff's earnings to efficiency.

    --
    These posts express my own personal views, not those of my employer
    1. Re:Hospitals implement tech badly. Lose benefits by twoshortplanks · · Score: 1

      The trouble with that is that you're then forcing them to be assessed on the metric you're assessing on them or inadvertently game the system (intentionally or not). I can think of plenty ways to make hospitals more "efficient" if you can compromise patient care...

      --
      -- Sorry, I can't think of anything funny to say here.
    2. Re:Hospitals implement tech badly. Lose benefits by syousef · · Score: 1

      The trouble with that is that you're then forcing them to be assessed on the metric you're assessing on them or inadvertently game the system (intentionally or not). I can think of plenty ways to make hospitals more "efficient" if you can compromise patient care...

      That's just a question of setting the metrics correctly. Include patient satisfaction, patient waiting times, quality of care when they see a physician are all measurable. The metrics for the administrators can also be skewed to favour patient care. Ultimately the top level administrator has to be interested in patient care, and not just to set up the metrics, or it won't happen.

      --
      These posts express my own personal views, not those of my employer
  43. What is the cost of a life ? by oneguess · · Score: 1

    Firstly, like most statistical analysis this one is also flawed because it does not take into effect any other increase in costs. e.g. Population increase, inflation, swine flu, etc.. Secondly there is no analysis of the value of the information being provided by computerisation. What is the value of BI? Thirdly most CIO's are poor at managing IT and its costs. In my experience they have no idea how much it should cost and pay millions/billions for a person in a nice suit to rip them off. The price being paid for the computerisation is too high. Fourthly computers are only useful if they are made useful to all users and it is used by all users. In my experience the product is dropped and everyone else is expected to pick up pieces while the people at the top enjoys the credit and bonuses. Finally what is the price of a life or the price of a mistake? How many are saved or made by computerisation ? This is only one study and provides more questions than answers. However it may open some eyes and force people to improve their computerisation or maybe just their CIO ?

  44. Maybe in America, but look at Belgium! by Anonymous Coward · · Score: 0

    Doctors do not hold much power when it comes to IT.

    Excuse me? In Belgium, IT transition was bottom-up; it started with the GPs. This is because our health care system is also heavily based on the work of GPs, they are the most basic and essential doctors for a well-working system. There are loads of software companies making tools for keeping track of patient records. In later stages, these companies developed intercommunication protocols, so a follow-up on a patient with another doctor is easy as hell.

    My dad is a GP. He keeps track of all examinations, medication prescribed, etc within an integrated environment. Pharmacists run different software, but intercommunication protocols make sure the GP gets a message when the patient picked up his prescribed pills. When the GP refers someone to a specialist, he gets a detailed report in his software environment about the examination the specialist performed. Same with bloodwork, urine analysis, ...
    This software propagated to hospitals, so it is now omni-present throughout all levels of health care. Management probably uses the most basic information from this system to provide financial reports to the government or university.

    Of course, in a country where health care is driven by monetary gain, IT transitions will be driven by management. And will fail horribly. Dr. Himmelstein would do good to look at a country like Belgium; we are regarded as the best, most efficient health-care in Europe. Looks like you Americans finally took your first steps in our direction, but you're still not quite there...

  45. Difficult measure by OpenSourced · · Score: 1

    How to say if computers save money to a hospital? Do you take into account reduction in errors, perhaps malpractice errors that could cost millions? Do you take into account expanded possibilities? If you now have a service that wouldn't be possible without computers, are the profits of that service included in the study?

    I once made a program for a manufacturing company, that sequenced the production in the different machines. They had at the time one person making the sequence for the machines manually. They had like 14 machines, and things were starting to go a bit out of hand, so the program idea. Now the company has grown, they have two different plants and about 40 machines, that work much faster than before, so the workload is even bigger. There are now two persons making the sequence. They have payed a lot for the program and changes and maintenance through the years. They have saved a lot also by reduced inventories and less errors. They have one person more, but probably they'd have needed more if it weren't for the program. But more important than that, is that they have changed procedures _because_ they had the program. They have reduced the size of manufacturing runs. They have achieved some quality certifications that have won them (who knows how many?) clients. I'm not just trying to say that computers save money, but that I wouldn't know even how to start to measure how much. I much fear that the study is a bit shallow. A similar study could conclude that this company has lost money by getting the program because they have doubled the personnel costs. As the article is skimpy on details of procedure, one is left to wonder, but my main idea is that it's practically impossible to conduct a meaningful study in search of that answer.

    --
    Rome taught me patience and assiduous application to detail. Virtues which temper the boldness of great, general views.
  46. building bad clinical systems is harder by r00t · · Score: 5, Interesting

    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.

    1. Re:building bad clinical systems is harder by sevenofnine · · Score: 1

      The main problem is that hospitals use old standards, while a xml version of hl7 is out. No one supports it, old segmented textfiles are used to transport information to/from systems. The protocol for transmitting the information (MLLP) is as archaic as they come.
      This tends to make things very complicated when dealing with things that needs to be there in todays hospital software (digital signing of requests / studies and reports) and leads to the software developers having to make hacks here and there to support this old framework of communication.
      Yet another issue here in Europe is that all software development teams must have the CE marking for medical devices with an extra attachment for medical software. This is very expensive and removes any new companies entering the field, so the competition is between already established players. Big companies that are uneasy with change in their software to make things better for the staff at the hospital.

      Yes, I work in this field making software for radiology and mammography departments. While not a huge company (we were just at the right place at the right time), we put a lot of effort into the workflow just right for the staff at the hospital, and not the hospital management.

    2. Re:building bad clinical systems is harder by Sniper98G · · Score: 1

      Then you need to keep medical staff away from both paper and computers. Data entry is for data entry specialists.

      How would you propose to get the medical data to these data entry personnel if medical staff are not allowed to record it? Are they going to need to dictate it to the data entry personnel? I suppose you could argue that you could have the data entry personnel trained up on medical matters so they could collect the data too, but at that point they would kind of be "Medical staff."

    3. Re:building bad clinical systems is harder by Lord+Ender · · Score: 2, Interesting

      Here's what I want:

      • The federal government creates one big wiki-like system with strong (2-factor) authentication. There is an entry for each person, with full name, birthday, location of birth, SSN, and photograph.
      • All hospitals would be required to upload X-ray data, test results, and other important notes to the patient wiki.
      • When you go to any hospital anywhere, doctors would immediately have access to your medical history. You would never get extra X-rays, never have to fill out pointless "list every medical condition you or your family have ever had" forms

      That would be incredibly easy to implement. The most expensive part would be getting smart cards and SecurIDs to hospitals, but if stock trading sites can do it, a government program could.

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    4. Re:building bad clinical systems is harder by hesiod · · Score: 2, Interesting

      Perhaps he meant unnecessary paperwork, not all paper... but even so, hospitals DO have transcriptionists. The doctor picks up a phone, dials a couple numbers (or uses a bar code reader or something, given the right equipment) and starts reading off their diagnosis. Then a transcriptionist somewhere else (perhaps around the world) gets that recording and types out what the doctor said into the phone. Ideally, the doctor gets that document back and approves it, though that part rarely happens. Then it's attached to your medical record.

      Having worked with older doctors, I know how hard it is to get them to look at a computer, much less get them to use one. And I don't think it would improve their work flow anyway; in fact it would probably hinder them.

      Old dog, new tricks, and all of that. But newer doctors are becoming more receptive... to having their own staff use computers. They still don't like to use them themselves.

    5. Re:building bad clinical systems is harder by Anonymous Coward · · Score: 0

      do none of you use the internet?

      http://www.epic.com/

      take a look it works, people are doing it

    6. Re:building bad clinical systems is harder by MobyDisk · · Score: 1

      What you are talking about is removing the metadata from the system and just having the staff use ad-hoc decisions. There are several reasons those types of systems won't work in a medical system:

      - They require the users to conform to ad-hoc standards like "always enter the SS# with dashes" or "without dashes" or "enter a 9999 for an unknown" or something like that. Inevitably the users don't conform, so you have to search for something 10 different ways to find it.
      - Without dedicated fields, a search can't tell a first name from a last name or a middle name. Many types of numbers (phone, SS #, driver's license #, medical record #, dates) have similar formats or number of digits and a search will give you wrong results.
      - Such a system can't connect to a billing system, which is how the hospital makes money. To bill properly, the names must be spelled the same in every place. It has to be able to tell first, middle, and last. Many fields are required, or must follow certain rules. Some times it needs to be able to tell the mother's name -vs- the father's name -vs- the responsible party's name.

    7. Re:building bad clinical systems is harder by anglico · · Score: 1
      yeah it works alright but it doesn't mean it works good. We just adopted this system and I honestly don't see a time savings, not for the doctor and not for the staff.

      What I told my boss when I started to get to know the program was it's as if they said "Ok we're all done we have an EMR product, oh wait we need a lab component" and 5 minutes later they had a lab component. The typical response I get is "well it solves some problems like chasing down doctors to get them to give you a Diagnosis code" but what they aren't seeing is the paperwork I have to do later when the doctor used a code that is never covered and it was denied.

      My best example of the lack of forethought in the programming is I have to type in 'yellow' and 'clear' for every urine I examine. A drop down box would save me so many keystrokes in a day, but it's electronic so it must be better.

      Bottom line they bought a system that solved some problems but created whole new ones where none existed before.

      /. car analogy: I complained about a car with no brakes so they gave me a car with brakes but no steering.

    8. Re:building bad clinical systems is harder by prgrmr · · Score: 1

      You'd be better off with relatively "dumb" software, almost like a wiki, that lets you efficiently handle arbitrary text and arbitrary data blobs

      You couldn't be any more incorrect if you tried. The majority of data generated and used in a hospital is of a well-known classified type: personal information like name and address; medical indexing information like diagnosis codes and procedure codes that convey paragraphs of standard information with a simple alpha-numeric designator; drug names and dosage instructions; and yes, insurance and billing information. The non-text data like MRI, X-Ray, and other imaging have been cast into industry-standard data formats. The problem is most decidedly not the data, either in its volume or diversity, but with perspective.

      Hospital Admins making short-term management decisions need a different view of the data than do the doctors, who need a different view than the folks in finance making long-term budget decisions, who need a different view than the billing department making immediate cash-flow-impacting decisions. What should be one of the primary goals of any medical software, that of providing the correct perspective for the given audience, is often lost in the attempt for software companies to produce an all-things-to-all-people suite of applications. The apps may or may not inter-operate as advertised, and (in my limited experience, having worked at one hospital) fall short of meeting the need for proper perspectives of the data.

      A wiki of data would be the worst of all worlds, as the one of the functions a wiki completely fails at is providing customized perspectives of data sets. Sure, you can specifically link related data, but there's no way of presenting that link as being a strongly coupled relationship or weak one, or something in-between. There's also no way of prioritizing the data: all of the data is all equal, all of the time, to all people. Wiki's are wonderful frameworks for presenting reference data, but horrible frameworks for dealing with procedural data. And like it or not, a hospital setting is nothing more than a venue for never-ending processes.

    9. Re:building bad clinical systems is harder by cayenne8 · · Score: 1
      "Here's what I want:

      * The federal government creates one big wiki-like system with strong (2-factor) authentication. There is an entry for each person, with full name, birthday, location of birth, SSN, and photograph.

      * All hospitals would be required to upload X-ray data, test results, and other important notes to the patient wiki.

      * When you go to any hospital anywhere, doctors would immediately have access to your medical history. You would never get extra X-rays, never have to fill out pointless "list every medical condition you or your family have ever had" forms

      That would be incredibly easy to implement. The most expensive part would be getting smart cards and SecurIDs to hospitals, but if stock trading sites can do it, a government program could."

      My basic problem with this is, where is the Federal government constitutionally authorized to do all of this? I mean, the Federal government really can't order a state to do anything, they have to use witholding of tax monies as a method to strong arm a state into doing something (like raising the drinking age to 21). How can they force state hospitals or private ones to participate in this? Where is their jurisdiction to create and force individuals and their private information into such a system? Heck, look at the RealID system they tried getting out there to create a national ID...that is largely failed, and many states openly said 'screw it, we're not participating and you can't force us'.

      About the only way the Feds could try to force this upon us, is to somehow mangle the interstate commerce act to cover it, but man, I don't see how it could with medical record transfers...where is the commerce dependent upon this? This is information amalgamation and transfer, not monetary transactions.

      I know the Feds do WAY more they they are supposed to, as mandated by the constitution, but more and more (like with the RealID act, and some states trying to bypass federal gun laws) states getting weary of the Feds overstepping their bounds, I think you might need to go back to look at a Constitutional Amendment to push forward this kind of national mandate. I think states will fight it, heck, if the current healthcare bills pass that mandate a citizen HAS to purchase some kind of insurance, I think it will be challenged and be thrown out by the SCOTUS...at least I see a good chance of it. I know people are preparing to challenge it already since it appears it might get passed.

      Remember, you are a citizen of your state first, and then a citizen of the United States second. At least, that's how it is supposed to work.

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    10. Re:building bad clinical systems is harder by r00t · · Score: 1

      Have a secretary work with the doctor. (probably reporting to him and standing next to him as he works)

      Keyboards spread disease. They are covered in germs. Doctors shouldn't be touching them.

    11. Re:building bad clinical systems is harder by r00t · · Score: 1

      The majority of data generated and used in a hospital is of a well-known classified type: personal information like name and address; medical indexing information like diagnosis codes and procedure codes that convey paragraphs of standard information with a simple alpha-numeric designator; drug names and dosage instructions; and yes, insurance and billing information. The non-text data like MRI, X-Ray, and other imaging have been cast into industry-standard data formats. The problem is most decidedly not the data, either in its volume or diversity, but with perspective.

      And... you FAIL.

      The patient gives you the WRONG name. A new procedure is invented. The WRONG code is used; it's easier to screw up a code than a plain-English description.

      If you need that translated into billing data, have a non-doctor do that. They can do this the next day.

    12. Re:building bad clinical systems is harder by prgrmr · · Score: 1

      The WRONG code is used; it's easier to screw up a code than a plain-English description.

      Do you seriously believe that?

      Take the phrase "Topiramate-associated acute, bilateral, secondary angle-closure glaucoma". Do you know what happens to treatment, billing, medical procedure preparations and follow-on care instructions if you leave out the work "bilateral" at any part of the process? Having a code that automatically puts the correct description on the billing statements, the patient record, and calls up the appropriate follow-up care instructions for the patient to take home eliminates that one mistake that has a significant cascade across all facets of the patient's hospital stay.

      Of course if you've ever worked in a hospital or other medical facility, or worked for an insurance company or other related third-party, you'd already have known that.

    13. Re:building bad clinical systems is harder by r00t · · Score: 1

      Uh, sure...

      Instead a mere typo turns that (number 932574)
      into leg amputation (number 923574) and you lop
      off the poor guy's leg.

      Really, numeric codes are terrible. It's hard to
      imagine a worse way to do things.

      Then there's that popular code (number 572962)
      which means "other", and all the times somebody
      picks the closest match because no code exists.

  47. But they save lives !!!! by tommeke100 · · Score: 1

    When "computerizing" medical facilities, the argument is not about how much cheaper treatment is going to be, but how much better it will be for the patients.
    So, computers are "bad", right?
    How about scanners, computerized microscopes, computer assisted operation tools and/or any other monitoring system?
    Sure, they cost more than if they were not used/purchased, but aren't all these meant for BETTER healthcare, and not cost reduction ???

  48. No computers was used to perform this study. by HollyMolly-1122 · · Score: 0

    All calculations was made by hand, saving money for calculators as well.

  49. The title is acurate by Cawas · · Score: 1

    But the whole text is not.

    If you go to the original post linked in it from computerworld, you'll have a different impression on that research. I am amazed nobody commented about this so far (although I haven't read all comments). Regardless of it all being well done or not, it is very sensate if you read it through, unlike the slashdot text from Lucas, which generated some angry comments.

    It is true the research showed computers don't save money for hospitals. Absolute majority of them, but not all. And Dr. David Himmelstein quote is also there, but in the end, after everything else was explained. Anyway I don't blame Lucas123 for the same reason I won't try to sum it up. It is a complicated subject. Just wanted to point people to actually go and read the source.

    I will just say that it is evident computers are bluntly necessary nowadays and there is no way for any research to show otherwise. Of course the only way to truly show computers are not a good option, in that case, is to have at least two similar hospitals running side by side, one computer-less. And nobody will do this as it is clear water that the second won't be sustainable.

  50. Variables... by Bert64 · · Score: 2, Insightful

    There are too many variables...

    Computers installed and maintained in a competent fashion, running software which is appropriate to the job at hand and being used by staff who are proficient with that software can save money, potentially a lot of it...

    On the other hand, many IT projects are terribly mismanaged, poorly budgeted, installed by cheap unqualified staff, running unsuitable software which expects people to adapt to its way of doing things rather than the other way round, and used by staff who are unsure how to use the system correctly and are often too fearful to touch it unless forced to..
    Ask the average joe on the street, and they will tell you that computers are extremely unreliable black boxes, they have no idea how they work and are very fearful of touching them incase they break, especially at work where they're likely to face disciplinary action for breaking the computers.

    In a lot of cases, computers are simply not appropriate, and in many more cases computers in the form that get installed are completely unsuitable for the task and are actually inferior to what they replaced.

    You also have the attitude of third party suppliers and corrupt people high up in the client organizations where the situation changes from "what do we need" to "how can we justify purchasing something from "... IT is one of the worst affected industries for this, because people generally have less understanding and are therefore easier to fool.

    The goals of these people is not to save money, it's not their money to save, it's someone else's money that they are in charge of, and their primary goal is to siphon as much of it out and into their own pockets as possible.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    1. Re:Variables... by geekoid · · Score: 1

      The problem is that management software must be custom per business. Not off the shelf 'customizable' software.

      Of course your rant about it being other peoples money is woefully ignorant point of view.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  51. Claims by Bel+Riose · · Score: 1

    "So the first thing we need to do is stop claiming things there's no evidence for."

    That would rule out 99 % of all claims.

  52. possible reasons why by viralMeme · · Score: 2, Insightful

    "The study also showed most of the IT systems were aimed at improving efficiency for hospital management -- not doctors, nurses, and medical technicians"

    1. Re:possible reasons why by King_TJ · · Score: 1

      This is exactly the quote I keyed in on, that I think explains it all.

      I ran into the same type of fiasco at my workplace, last year, when we looked into replacing our paper time cards with a computerized system. Initially, the argument for doing it was "it'll save money on all the paper cards, storage of them in boxes for years, and stops cheating the system when employees punch their buddy's cards for them". Great! So I researched the options and found many workable solutions, including an ethernet-connected fingerprint reader and a card swiping type of reader that fed data back to software on a back-end PC.

      But before a purchase was approved, management latched onto the whole project and decided, "Hey, if we're going to track people's clocking in and out on the computer, we should tie this into our whole accounting system and make something that lets us track exactly how long they spend on specific jobs we ask them to do! Let them punch in codes to define the cost center of whatever project they're currently doing, and then we can make GREAT reports that show us how efficient we are at various tasks!" Next thing you know, it turned into a nightmare. User-friendliness of the system suddenly plummeted. (What union shop worker do you know who would be happy to look up or memorize dozens of cost center codes and keep running back to a keypad, swiping his/her card and keying in the correct codes for each little job he/she does? And who is going to cross-check all those entries to be sure they're even entering correct data?) The cost of implementing it skyrocketed too, because all of a sudden, you're looking at having card readers/keypads placed near all the places people might be working. You can't have them hike half way across the shop floor just to swipe a card and enter a code because they're done sawing pipes, and want to move on to drilling holes in beams, right? That meant running cat5 cabling all through the shop for the readers, etc.

      In the end, the whole project was scrapped due to "high cost of implementation" and "inadequate software for handling our reporting needs". Just as well, really ....

  53. What b*llsh*t on a stick (forgive my french) by forgot_my_username · · Score: 1

    No, they dont save time.
    But, they do save people....
    Sigh... Vista... the VA's medical informatic system reduced dispensing (medicine) errors by something like 90%.




    So in the words of my forefathers... Intercourse Efficiency

  54. The question that they forgot to ask .... by CalcuttaWala · · Score: 1

    was whether the Hospitals could have at all managed to deliver the kind of services WITHOUT the systems that they are using today. We know that hospitals can operate without computer ( there are enough of them where I live, in India ) but the real question is how efficiently do these computer-less hospitals operate ? the queues ? the chaos ? if not the gross corruption ? We know that computer system cannot solve a problem when the underlying physical system is broken but it sure helps to have a computer around -- a computer is necessary, but not sufficient to solve major business problems. And do not expect to calculate a Return-On-Investment on IT systems ( of the kind that can be done with other machines ) .... consultants and CIO have tried for years to do so and have realised that the answer simply does not exist.

    --
    Insight into much, Influence over nothing !
  55. Hidden intent: by Anonymous Coward · · Score: 0

    "Bottom line: they have met the enemy, and he is them."

    Bottom line: Doctors don't want medical treatment to be more efficient.

    1. Re:Hidden intent: by hesiod · · Score: 1

      Doctors don't want medical treatment to be more efficient.

      That is completely ridiculous!!!! The more efficiently they can treat one patient (for the same price), the more patients they can see in a day, making them more money. And maybe one or two of them want people to be healthier. Maybe.

  56. I recall a similar study on household appliances by erroneus · · Score: 1

    Many many years ago, a study over the modernization of household appliances and stuff affected the workload of the average housewife. In the end, it showed the amount of work that could be done in a day was just about the same.

  57. Hospital Systems DO SAVE MONEY by Anonymous Coward · · Score: 0

    Let's start off with the basics.
    Time = Money.
    Mistakes = Money

    There are actions that need to be complete and the longer actions take the more people are needed to perform these actions. Therefore... the longer actions take to complete the more money it costs the hospital. Think "Nurse what drugs has this patient been given?". Most hospitals keep digital records of all medications given which helps doctors make decisions. This simple task could take 5-10 minutes pouring through 200 pages of charts and possibly missing pages.

    Think bad handwriting where the nurse AND the doctor can't read what it is. Get the idea?

    Mistakes also cost money. One of the biggest benefits is that Doctors can quickly see what Jonny has been taking and don't accidentally prescribe something that will kill him when mixed with other things. It also helps the doctor quickly see trends and change their decisions quickly whereas with paper records they might not as easily notice.

    This paper is written by someone who hates computer systems and doesn't take into account how medicine has changed in the last 20 years.

    This is just coming from a guy who works at a Veterinary College... our patients are cats and dogs. Our system has been attributed to saving hundreds of lives because of how statistics can be generated on the fly. Comparing test results with a click of a button and seeing trends, easily, efficiently... without error. The ability for alerts to come up letting a doctor know that a drug they are prescribing may cause an allergic reaction with this patient.

    I can easily say Dr. David Himmelstein has flawed research with far too many missing puzzle pieces and flawed logic. This system has saved our hospital MILLIONS in potential lawsuits alone.

  58. False premise... by PinchDuck · · Score: 1

    in the title. I've been around Hospital IT quite a bit in my career, and have never seen a system sold on saving money. They're sold on getting clinical data to the physician as soon as possible. A computer system and network costs far more money than a slip of paper, but I still want my lab results stored and transmitted electronically because it is faster and more efficient, both in a particular moment and over the span of various visits.

  59. My experience in medical information mgt ... by LaughingCoder · · Score: 3, Insightful

    I developed products in this space for a number of years. One big problem we always encountered was the in-house proprietary systems. Time and again we would hear "we'll buy your system as long as it can interface with this shiny, homegrown monstrosity that we developed". Of course the person most responsible for the purchasing decision (at least from the technical end) was also usually the manager who was responsible for creating (or at least maintaining) the inhouse monstrosity. To throw it out is to admit a giant mistake, to potentially cut staff (and hence reduce power) and so instead they try to make vendors jump through hoops. Our natural response was to wrap our products with integration services, which breeds a support nightmare (no two customers have the same thing) and is also very labor intensive, and hence expensive, making it very hard to justify for the projected "savings". As an example, I once spent a year (mostly on my own time each night at home) logging in remotely to a hospital system, running migration scripts to move image data from an inhouse system into our system. Each morning I would tell the customer's technician to load a new batch of disks, then I would kick off the migration each night. And mind you, this is ONE customer at ONE hospital. And of course first I had to write the migration scripts ... another sunk cost.

    --
    The more you regulate a company, the worse its products become.
    1. Re:My experience in medical information mgt ... by Eskarel · · Score: 1

      Hospitals have always been best of breed, that's just the way they work. They don't buy the medical equipment from one manufacturer, so they don't buy their software from one developer either, that's just not the way they think.

      As a software developer in the health care world you MUST make your system compatible with any standard you can find, AND your integration services have to actually work properly. I do integrations and presentation layers for health care fore a living, trust me on this.

      I would also like to say that if you spent a year doing a simple repeatable task instead of just building a system where your customer could do it themselves, especially in your own time, then you're an idiot. It takes a couple of days to knock up a system where if the customer sticks their images in a certain location your system will suck them up and convert them. Maybe a month if you're trying to build something that will never require support again. If you went and did it manually you were doing it wrong.

    2. Re:My experience in medical information mgt ... by LaughingCoder · · Score: 1

      First, I said nothing about standards. Our systems used standards. The problem was the homegrown, non-standard systems.

      Second, as regards your assumption about how easy it would be to bang out a script to automate the nightly activity, you do not have enough information to make that statement. Now, I am the first one to automate any task if it is possible. As it happens, each nightly episode had unique twists that required some human intervention. For example, their home-grown system had, imagine this, human data entry errors. One thing I would need to do, for example, was check the meta-data for the images and make sure it matched the actual images, reconciling the differences if it didn't, before importing.

      Anyhow, if you work in medical information integration services I am sure you have run into your share of home-grown, non-standard systems that needed to be accomodated.

      --
      The more you regulate a company, the worse its products become.
    3. Re:My experience in medical information mgt ... by Eskarel · · Score: 1

      I have indeed, and plenty of useless end users who can't follow instructions too.

      My point was more that that's how the industry works and you've got to accomodate it, it's part of the cost of doing business.

  60. Re:Let me explain further... by Anonymous Coward · · Score: 0

    Let's say you have $5 in your pocket, and you somehow manage to spend $10 of it. Now how much money do you have? If you can answer this question correctly, then you are far too smart to work at any level of the US government...

  61. Medical record ownership by sjbe · · Score: 1

    Your records belong to you.

    Not really. In the United States the DATA in your medical record belongs to you. The physical medium on which the record is stored belongs to the entity responsible for maintaining that record. A close analogy is that you own the copyright but they own the physical copy. You have a right to inspect your medical record and petition your health care provider to correct factually incorrect data.

    In the United Kingdom NHS medical records belong to the Department of Health.

  62. Consider the source? Do doctors love secrets? by walterbyrd · · Score: 1

    I don't know, but I have heard that doctors love a system of badly filed, illegibly scrawled, notes - a system that only they can understand. Doctors do not want a system where data can be easily transfered, or easily reviewed. Doctor's want to protect their turf, and they want to be immune from any possibly legalities.

    Whenever I see a "study" in a pop-media publication, my first thought is: who funded this, and why? IMO, there is usually some agenda involved.

    1. Re:Consider the source? Do doctors love secrets? by mgchan · · Score: 1

      Doctors don't need bad handwriting to keep secrets. And bad handwriting is not going to keep someone who wants to sue you from doing so. It does help to prevent mistakes when you can read the previous doctor's note (even if it's from an ophthalmologist whose notes are just a long string of acronyms in English and Latin). I don't know what this guy's agenda is other than to get his name out by putting out proof against common sense.

  63. In a related story... by Halotron1 · · Score: 1

    MIT releases research proving that lawyers don't save hospitals money either.

    Suck it Harvard!

  64. The Meaning of Life by Snufu · · Score: 1

    Of course the hospitals in the study could not afford good software. They spent all their money on "the machine that goes 'ping'".

  65. Paperless office by p51d007 · · Score: 1

    In the mid 80's, I first heard the notion of a paperless office. Friends of mine told me I better find a new line of work (I repair office machines). Well, here we are 20+ years later & I'm still doing the same thing. Not only did we not get a paperless office, we have MORE. Every time the government comes up with a new regulation, my business goes UP. Add to that, these machines are now interconnected and do multiple tasks. All a computer does is make it easier for bureaucrats to justify themselves by producing more and more detailed reports on the tookpick inventory. Unfortunately, they still don't understand how a computer or interconnected device can help the guys in the trenches do their job. Most of my career has been spent inside a large hospital complex, and a few years ago they started computerizing everything. Now it appears that it takes the nurses longer to do their jobs because of the do-dads they have to carry around and scan everything they do. Does it help cut down on mistakes, more than likely, but, if you want to see things really slow down, watch what happens when the entire system goes down, and the younger nurses/staff don't know how to treat someone the old fashioned way, by writing everything down and doing everything by hand. It's the same principal as why teachers require you to "show your work". You could punch something into a hand held calculator all day long but if you don't know the basics of how to do something, you're screwed.

  66. They surveyed the wrong hospitals... by wzinc · · Score: 1

    I took a tour of our local hospital's IT facilities. The main thing they've saved money on is not having to reorder blood tests; computers mean less errors reading doctor's handwriting. That, alone, helps save lives by having fast, accurate results. There are several other efficiencies, such as storage and backup of patient data, CT and MRI modeling, etc. Those may not save money (maybe they do), but they make saving lives drastically more efficient.

    They shouldn't make sweeping generalizations that no one is saving money or becoming more efficient.

  67. Anyone who's surprised by this... by JonStewartMill · · Score: 1

    ... has never been involved in an IT project in a medium-to-large organization. The sheer overhead involved in "managing" a project invariably sucks up any potential cost savings that might be realized. Combine people's natural desire to get paid handsomely for a job that consists solely of going to meetings with IT leadership's quixotic attempts to turn their department into a revenue source, and you have a recipe for inertia that 19th-century Russian bureaucrats would envy.

  68. often the users by ILongForDarkness · · Score: 2, Interesting

    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".

  69. A conspiracy? A "Solution"? by mhollis · · Score: 1

    Did nobody read Nicholas Negroponte's Being Digital ? I think I re-read his book once every two years just to remind myself why this computing stuff is not intuitive and to remember that I have developed a skill set that does not relate to any reality other than that of the computer.

    I don't want to take anything away from physicians. They're smart people and every one I have been to recently is capable of dealing with a personal computer. Some have dedicated touchscreen systems to help to record patient information and to write prescriptions. Others use computers to reduce the need for office staff to push paperwork. Still others have gone "paperless," and are trying to keep all records electronically so that they don't have to have a room just for patient records.

    I also don't want to take anything away from hospital administrators who have to handle the tremendous losses of an emergency room with 9 to 12% of cases coming in with no insurance and no ability to pay for necessary treatment, combined with a mandate that they take all comers, regardless of whether or not the hospital will wind up picking up the tab. They're trying to reduce the steps necessary to manage a pretty large organization that must be large in order to be able to stay afloat.

    But I'm looking at this Harvard study in the same way that I've been looking at the Women's breast exam and mammography study as well as the recent pap smear study where statistics are being slightly misused. And the end result of this study will be used to invalidate the Administration's claims that computerization will result in a savings, just as the last two studies have been used to claim that any health insurance reform that passes the House and Senate will be used to limit care. Never mind that it's false.

    The administration's computerization proposal is all about patient care and not administration. The Harvard study covered computerization of administrative tasks. Will there be a savings? That is yet to be seen.

    A computer application needs to be easy to use. It needs to be so analogous to the types of everyday tasks that the nurses, doctors and support staff does that they can readily understand and work with it. That's Negroponte's point. Furthermore, any application (and user interface) written to streamline patient care needs to actually make things easier to provide patient care than the methods currently being used. If this is not the case, it will take a long time for any savings to be seen because adoption will be very slow.

    If you are a programmer and you are working on something like this, you need to spend a day with a nurse. You need to spend a day with a doctor. You need to observe their procedures and really understand them, which means they need to explain things that they did to you. And that's a problem because no nurse or doctor really has time in their day "for this nonsense." So, what's probably needed here is a programmer who actually studied medicine, which is probably a seriously small subset of all programmers out there.

    I work in television. And I remember when the first computerized video editors came out that changed the editing paradigm for us. they were pretty slow. It took a long time to load material into them and then the end result had such low resolution that you could not determined whether or not the camera's focus was properly pulled. You had to take the end result and go into a very expensive suite and reassemble everything with a computer list created for that purpose. Of course personal computers got faster. And their capabilities got better. And compression of pictures got a lot better. Today, there are a number of video editing tools out there that enable us to do our jobs very well and everyone understands the worth of loading material into the systems. Additionally, there are different editing systems available that use different paradigms for e

    --
    Gods don't kill people, people with gods kill people.
  70. They don't have "money" by agentc0re · · Score: 1

    I work in a clinic that is inside of a Hospital. Our Docs have Hospital duty, basically on call during the day/nights and weekends. So what i see in the clinic could be different than a Hospital but i bet you it boils down to the same old thing. Money.

    I was very lucky this year and finally received the 'OK' to upgrade my servers from Server 2000, to Server 2008. It took me several years to buy the two servers necessary to host the new 2008 servers(will be virtual servers). With Medicare cut's, echo, cath, nuc, we'll even have more of a hard time with that. Anything labeled "Medical" is 30x more expensive. And Doctors tend to work as much as they want. This is a huge problem since if they are okay with earning 50k, 100k less than the company as a whole suffers. There are multiple docs like this. You can't tell them what to do because it's their company.

    Our EMR software is more guided to our line of work as well. However it still has major flaws and could preform better. The problem with it is that it was designed by doctors. At first it sounds good until you see the SQL end. Doctors designed that too. So the whole program, designed by these docs(not mine some can barely can turn on a PC), really is a mess that no one can fix but they just keep piling on to it. It's bloated to all hell.

    I think the key to success is to break the EMR system down to individual sectional needs. Like a TV. a TV isn't built (or a good one at least) with a DVD/blu-ray player, xbox306, ps3, wii, cable tuner, etc. etc., inside of it. No it has ports to link it all to the TV. EMR software should be similar in the fact that there should be a standard "Link" so that when you have your Cardio EMR and you need to link it to your Lab EMR, you can. The billing side of all of this is probably the worst joke as i would say it's the hardest of all of this.

    --
    Sometimes, the answer is to just destroy it all.
  71. The survey says... by Anonymous Coward · · Score: 0

    So this is all based on survey data that hasn't been verified as true. So, based on the PERCEPTIONS of the people taking the survey this might be true, but I have a real hard time believing that the "old way" was as efficient as using computers. Every other industry has benefited from computerization so why has the medical field not?

  72. This study is garbage by Anonymous Coward · · Score: 0

    This is the biggest load of bone headed Harvard BS I've ever seen. Let's see some university hospitals throw out their billing systems. Start sending insurance claims on paper. But wait, there is a LAW that doesn't allow paper billing! This study is crap! Sure hospitals waste a ton in IT. I wonder if that is related to the fact that hospital IT is the lowest paid of any industry that employs IT.

  73. Baloney by C10H14N2 · · Score: 2, Interesting

    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.

    1. Re:Baloney by AK+Marc · · Score: 1

      They already do. It's called HL7.

      Having a standard and using it are unrelated. Aside from moving records within the same building, I've never had doctors able to share any information other than via fax. And every one of them had electronic records. But most (all?) were able to submit billing electronically.

      It's been around for twenty years.

      Twenty years, and yet in the last 10 doctors I've seen for myself or with my family were all incapable of sharing information electronically with anyone outside their building except for insurance companies. I don't think the implementations are going so well.

      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.

      You missed it. My point is that administrators are often business focused, not care focused, and so they pick systems that have billing as a focus, rather than care. I expect that the doctors know the codes. However, a system designed with care as a focus may accept "bad" inputs and flag them so that billing reviews them before acting, and one designed for billing would stop the doctor during treatment and force him to enter a valid code. Not that they don't know them, but that they could make an error or provide inputs the system thinks aren't compatible. If you have the doctor take 30 seconds to deal with it at care time, then I assert the system is billing oriented. And if the system would just flag the entry and let the treatment continue, but take 10 minutes from a billing assistant to clear up, then it's more care oriented.

  74. Watered-down quality results? by yamfry · · Score: 1

    I read the linked Harvard study (I know, unprecedented!). I found the measurements a little misleading -- and I'd appreciate any contrary opinions on this. The degree of computerization was measured by taking the number of electronic systems that the hospital uses and dividing it by 24 (the total number of computer systems they measured). These computer systems included things like "patient billing", "staff scheduling", and "materials management". Not that those things are unimportant in and of themselves, but when we count those towards being a "computerized" hospital, it tends to water down the importance of other computer systems. For example, a hospital that uses a computer to make their nurse schedules and credit collection is considered as computerized as a hospital that uses computerized physician order entry (CPOE) and electronic medical records (EMR). I don't think you can group those two together and say they belong in the same category when analyzing quality of healthcare at a hospital.
    The study actually presents a sub-analysis of quality measures for hospital that use CPOE and EMR and shows that there are significant quality improvements when these systems are used. I think that when we talk about computerizing hospital processes, these are the systems that we consider -- not whether HR uses computers for payroll. I think it is a little disengenuous for the conclusions of this study (and reporting thereof) to state that there is no relationship between computerization and quality of care.
    Disclaimer: Without CPOE and EMR, I would be unemployed :)

  75. Bullshit by Anonymous Coward · · Score: 0

    I work for a company which provides a unique remote ICU solution. We have proven that it signifigantly reduces mortality, and shortens length of stay, as well as allowing more beds to be monitored with fewer intensivists.

    If you're simply talking about 'electronic records' a la Obama, well yeah, that's a load of hooey and is more about the government having easier access to your data (for non health purposes).

  76. It doesn't shock annyone by geekoid · · Score: 1

    that management software doesn't work well.
    The best way to get maximum possible benefit from management software is to write it in house.

    Every company does management differently, and has specific business rules the go all the way to the center of their business.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  77. Try the Scientific Method by Rambo+Tribble · · Score: 1

    To test this theory, go into a hospital and unplug all the IT systems. I'm willing to bet costs go up.

  78. Who wrote the requirements? by foniksonik · · Score: 1

    Computers and machines in general just do what you tell them to do. So who wrote up the requirements? It's very likely that an administrator did... so no wonder the systems were designed to make administration more efficient. This means that the inputs and outputs were designed for good bookkeeping - not efficient medical practice. Doctors and nurses now have to learn to do things the 'administrative' way rather than the 'practitioner' way... and likely it is not very efficient for them.

    A good fix for this would be to develop a new view of the system which is organized and designed for the doctors and nurses but translates to a view for administrators.

    Unfortunately this will up the cost and now that the work is being done twice will likely swallow up the savings for the near term... so the hospital board is unlikely to approve it and simply insist on more 'training' for Doctors and Nurses.

    --
    A fool throws a stone into a well and a thousand sages can not remove it.
  79. re: the ones who can't keep up get filtered out .. by King_TJ · · Score: 1

    My mom is a retired R.N. and she's friends with quite a few older doctors out there. One of the big complaints she's heard repeatedly from them is, hospitals are starting to demand they get on-board with using their computer systems. If they refuse, and want to keep track of things on pen and paper, or using their own favorite methods, the hospital simply bars them from working there anymore.

    So the computer illiterate doctors are often voluntarily retiring, rather than deal with the learning curve this late into their careers. A few just run their private practice and stay out of the hospitals, so they can do things the "old fashioned way" for a few more years until they're ready to retire.

  80. Money? by DarthVain · · Score: 1

    I'm from Soviet Canuckistan you insensitive clods!

    Seriously though, I would think that IT and the health industry would be about increased service (say in patient records) not about saving money.

  81. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  82. Regulations by Anonymous Coward · · Score: 0

    Another false argument. The author fails to account for the massive increases in regulations and the resultant paperwork it produces. He's living in a dreamworld where everything has been the same for 45 years especially with regard to drugs and compounding. You can call his research poor at best. He's the type of doctor that prescribes medications having no idea what their effects are resulting in an immediate call from the pharmacist downstairs, "Dr., you can't prescribe that medication X when he's still taking Y. We went over this last week. It will kill your patient." "Oh well, just fix it then."

  83. Get a real job by Anonymous Coward · · Score: 0

    What would Harvard know about saving money? It's easy to tell other people how to do it if you just get hand-outs from the government and 'generous donations' from parents of students who otherwise wouldn't graduate high-school. Besides, I would like to see a hospital make a profit after they get sued by the family of a patient because someone misplaced a clipboard or an X-ray. Oh, and I wonder if Harvard heard of HIPAA and HiTRUST - good luck protecting patient records by encrypting paper copies. Can you believe someone up there gets paid to suck stuff like this out of their finger?

  84. Computers in medicine by Anonymous Coward · · Score: 0

    I'm a practicing surgeon - I graduated from medical school in 1985 and have seen a lot of change in those 2+ decades. (I'm also a C programmer and maintainer of a couple of widely-used OSS projects - basically spent lots of time wondering whether I should have continued in CS instead of going to medical school).

    The real improvements I see are:
    1. Dramatically faster/easier access to patients' lab results, imaging, and previous reports and consults. As a student, I used to have to walk to the basement and copy numbers from printouts posted on a wall, swipe the X rays for my attendings to look at, etc. I know it sounds like "walking five miles to school in the snow", but anyone who denies that computers make clinical info more accessible is really full of it. I'm not so certain that the better access to records has always improved medical decisions, but it certainly hasn't hurt.
    2. Mind-boggling advances in imaging technology - CT, MRI, ultrasound - the speed and quality of modern imaging would have seemed like something straight out of science fiction years ago. Again, the better pictures don't always lead to better decisions, but they often are really helpful, and provide answers that used to require much more invasive or painful studies.
    3. Surgical technology - laparoscopy and related advances.

    So computers haven't saved hospitals money? Well, they haven't eliminated world hunger or global warming, either. I think this study has the wrong end point.

  85. EHR's do some things better, but not saving money. by Gerakon · · Score: 1

    Electronic Health Records are generally not marketed as a way to save money. They make it easier to get reports and make it safer for the patient. Whether or not this is enough to justify the cost, who knows.

    Things EHRs do better than paper charts -
    With paper charts it's much easier to lose or miss place a chart - This probably happens more than you think.

    Drug interaction checking with an EHR can make sure that a med someone put you on a year ago and didn't get into the chart is less likely to conflict a new med because the EHR will tell the doc that when he/she tries to prescribe it.

    Making sure that people with chronic problems such as diabetes are scheduled to get in for they're check ups rather than slipping through the cracks. This also generates more revenue for the hospital.

  86. Harvard MBA's fail again. by fast+turtle · · Score: 1

    No I didn't RTFA, just the damn summary yet it looks as though Harvard's MBA's screwed up another investigation. Instead of looking for hospitals where patient care had been improved, they cut costs and screwed the entire study by looking at how computers helped save money. Stupid Gits. Even I know that if you look at how computers saved money, you aint going to get anything on how the computers improved patient care. As an example, my local hospital has dramatically upgraded their entire IT infrastructure and gone to E-records. My mothers primary care doc, is part of this system and has 24/7 access to all lab reports, X-Rays/MRI's/CatScans and anything else that's in the sytem, which has helped tremendously and this is an example of how computers and IT has improved patient care. Yes the evidence is ancedotal but it certainly has improved things for her.

    As others have said, the systems are out there and it's just a matter of knowing who's got them. If we bother taking the time to really learn from those who've improved levels of care, we might finally be able to get some type of Universal health care that provides basic coverage in the United States, which should improve the overall health of the country. Yea I know, wishful thinking as to many people want access to those records.

    --
    Mod me up/Mod me down: I wont frown as I've no crown
  87. Usability by Anonymous Coward · · Score: 0

    One problem is that some of the software that is used might not be so great. There's this one piece of software that I use that is ridiculously inefficient. When you do a electronic medication review, the software opens up an internal Internet Explorer browser window that medications administered for the current day. So to get to a particular day, you have to click a link in the browser window. So if you want to see information from several months ago, it takes a considerable amount of time. And that doesn't even factor in the times that the program doesn't respond when you click the link.

    The human resource software can also be problematic. Set up is a pain. One particular web staffing solution I've used is so poorly designed that it's barely usable. But by far the worst one I've seen is this one staff scheduling software. It was clearly first written for DOS, because the calendars and job statuses are still represented using single characters, including symbols. So to decipher what they mean you need a friggin' rosetta stone. An "#" might be used to represent "out sick" for example. Then you get such fun situations with upper and lower case letters. So "A" could mean "Annual Leave" while "a" could mean "Absent". To make things even more complicated, there are several different calendars, from a preliminary one to a final one. So you could conceivably get confused and make changes to preliminary calendar thinking that it's the final one. Couple this with the fact that you have to select a date range, and it gets confusing real fast. It literally takes months to train people to use this piece of garbage.

    Why the heck can't you just have one calendar for one employee? And instead of representing schedules using dollar signs and exclamation points, why can't each day just say a full word or phrase like "7 AM - 3 PM"? Or "tentatively scheduled for 11 AM - 7 PM"?

    In this day and age, we have display devices with thousands and pixels and user interfaces that allow you to zoom in and zoom out. We have plenty of metrics of usability. Yet we're still stuck with the lousy design paradigms of yesterday. It's no wonder that this technology costs so much but does so little.

  88. Manager-Centrism by Tablizer · · Score: 1

    The study also showed most of the IT systems were aimed at improving efficiency for hospital management -- not doctors, nurses, and medical technicians.

    That's true in just about ANY industry. Managers are prima-donna's who think they are the center of the universe, and everything else is relegated to Pluto. If that happens, it's not the fault of "computers" per se, but of how they are used.

  89. Missed the point of hospital systems by smammon · · Score: 1

    I've been in IT for more than 20 years and very very rarely have I seen automation be a money saver. No matter the industry.

    Automation does enable other things however. Many businesses would not be possible without automation. For example global overnight shipping...and large hospitals. I work for an average size metropolitan hospital and I can tell you - even at our modest size - the business of tracking patients, all their meds, tests and even what room they are in would not be possible. At least not without a staff that would dwarf what we currently have. Processing the mess that is the medical "reimbursement" system in the US is a whole other topic. Even WITH automation that requires a staff of about a third as many individuals as we have inpatients.

    Health care IT is finally starting to get to the point where there is a definite direct benefit to the patient too. For example - medical imaging has reached a point where it's virtually all digital. The patients studies are pushed back and forth between providers (hospitals). In our case we recieve patient transfers from a very wide rural area. The smaller hospitals and clinics send us the patients scans digitally and most of the time the surgeons at our hospital have been able to plan treatment before the patient even arrives.

    We also have IV pumps that know the safe levels of the drugs they are putting into the patients. If a nurse makes a mistake - say not moving a decimal appropriately when she is setting up the infusion rate (very common error) - the pump will not allow her to put 10x the drug into your vein... We can also get the infusion information pulled back to the patient record and even locate where the pumps physically are thanks to their wireless connection.

    Saving money is truly the last thing that should be considered for hospital automation.

    --
    "Smile, listen, agree, and then do whatever the fuck you wanted to do anyway." ~Robert Downey Jr.
  90. Can't support the docs if they won't cooperate. by Hasai · · Score: 1

    "....most of the IT systems were aimed at improving efficiency for hospital management — not doctors, nurses, and medical technicians...."

    And there's your problem. Ask any hospital chief of staff, and they'll tell you that most doctors think the sun rises and sets over their arses. Trying to get a bunch of them to participate as stakeholders in an IT project is something I wouldn't want to wish on anyone . . . . Except for the twits who wrote this article.

    --

    Regards;

    Hasai

  91. The reason for inefficiency by Anonymous Coward · · Score: 0

    is that the doctors are rewarded for inefficiency.

    Today doctors are being paid on a "per visit" basis. So, doctors get paid more if they take a long time to diagnose.

    Given that this is a problem with the doctors, EMR or no EMR, the efficiency will not increase.

    System should move towards the British NHS approach. Doctors need to get paid on a "Per person/per Year" basis. The "Per person" approach will ensure that the doctor has no incentive to treat you forever. The "Per year" clause will ensure that the patient can switch doctors in case he is not happy.

  92. Hello kids by blue_teeth · · Score: 1

    Implementation of Information Systems is not just technology, cool displays, reports and widgets. Repeat after me: It is CHANGE MANAGEMENT! Your lowest common denominator user can fail the system if the change is not managed.

  93. Re:Staffing by winwar · · Score: 1

    "At the end of the day the only way that "computers" save a business money is if they allow for staffing levels to be cut."

    I think we have a winner. Unless computers/tech increase the amount of patients you can process (which is part of the problem in primary care and just not an issue in hospitals) or reduce costs (less errors, waste, etc) they must lead to increased cost. If they make it easier to bill for more unneeded crap (automated or easy billing codes) they almost certainly will massively increase cost. Talk about unintended consequences.

  94. I don't think that's correct. by Futurepower(R) · · Score: 1

    I don't think that's correct. The end result of medical treatment being more efficient is that there will be a lot less opportunity to bill for unnecessary procedures, for example.

    Efficient medical treatment would cause prices to drop.

    1. Re:I don't think that's correct. by hesiod · · Score: 1

      bill for unnecessary procedures

      Most of those procedures don't make the doctor any money, since he doesn't perform them. Unless a doctor has a direct financial interest in the growth of the hospital the procedure is performed at (shareholder, etc), he has no financial interest in ordering those procedures. Many doctors are not even employed by the hospitals at which they work.

    2. Re:I don't think that's correct. by Shane+dot+H · · Score: 1

      You might want to look into the stats at how many hospitals are doctor owned. This article from June was passed around a LOT in policy circles, showing how the incentives are for doctors to drive up costs:
      McAllen, Texas and the high cost of health care - Atul Gawande

  95. Read this a few days ago and had to laugh by CoffeePlease · · Score: 1

    About 5 years ago I attended a dinner in Michigan where Senator Debbie Stabenow gave a speech on how we would save the auto industry by switching to electronic medical records. The theory was that that would reduce the 1200 or more per car that GM was spending on health insurance and pensions for retirees.

  96. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  97. Not that convincing, sorry by Mathinker · · Score: 1

    I hate to tell you, but you're not very convincing. You've made a lot of assumptions which are probably correct for you, but stack things in your favor. Well, I agree with you, then. But the whole point of my post, quite a bit of which was in the title "Depends" (for which I apologize, it's bad form to use the title as an essential part of a post), is that, well, it does depend on quite a few factors.

    The assumptions you make:

    • The file system GUI is structured like the default Windows Explorer layout. IIRC, the default Windows layout is not like that, and doesn't have a directory structure pane on the left side of each directory window.
    • When you advise using typing to locate a file in a window into a large directory, you assume that the filename is very unique, and that the sorting which has been set on the files in the window is alphabetical, and not by date or something else.
    • You make the valid point that switching your hand between mouse and keyboard is major overhead (at least I assume that's why you'd rather not take your hand of the mouse), yet you try to counter my point that it could take scrolling to find the file in question by proposing starting to type its name.
    • Your last paragraph blithely ignores/forgets my assumption that neither the source nor the destination GUI windows are already open. In my post, I obviously agree with you that if all you have to do to move the file/directory is a single drag-and-drop, then the GUI wins.

    As to how often one does "cold" moves of files deep within filesystems to other directories which are also deep within filesystems, well, I actually do type things like "scp uid@remote:/this/is/a/fairly/long/pathto/file ~/Desktop" quite a bit, because I know that if I open the remote filesystem in a GUI window, even if I have the exact source location bookmarked, the file manager will often have to wait quite a while while all of the directory information travels over the network (e.g., if the directory contains a lot of files, or the connection is slow). I admit it's less common for me to type two long paths, since I mainly use Emacs' dired mode as my file manager (and yes, it does have a kind of GUI-like flavor even if given the way I use it, its input is almost totally text/typing-based).

  98. Smell The Freakin' Java by DynaSoar · · Score: 1

    During the process of getting 3 degrees and a state state practice certification, I also go an MHA. That's a master's in healthcare administration, an MBA for health care industry (as opposed to providers) management. So I know whereof TFA speaks. I was also a charter member of the international professional group concerned with healthcare IT and associated things, the HIMMS http://www.himss.org/ASP/index.asp Take a peek for yourself and see whether you think they're relevant. TFA did beause they use HIMMS data collected with HIMMS analytics tools. In my over-educated opinion, they did pretty much all the right things for getting data and making use of it to answer their question. But.

    I often admit to having signed up for a neuroscience program before even finishing the MHA because I knew I had a defect that prevented me from making use of it as a functioning member of the health care "industry" -- a conscience. And it's true. And that only came about because of what they taught me. Some of that stuff explains why things are as they are, and why TFA failed to note it.

    The health are industry became a larger piece of our GNP than defense decades ago. It did so because it was wanted, so people offered it, and made a lot of money. They made more and better care available, and it got used, and they made lots more money. This continued until it got to the size it is now. There was never any intention of making it cheaper. It was a growth economy of its own no different in principle than the economy of an emerging nation. It would be irresponsible to build a tidal pool into the cash flow, and ridiculous to build a pocket of poverty into the model when one is not needed. What is needed is maximized growth. Right about now folks from all sorts of different viewpoints wave their arms like they're putting out a fire in their hair, and making a shape with their pie hole so it can make noises about, well whatever is their rant du jour. But they are not in possession of all the facts. Those come from geriatric and population epidemiology, and are related to the "boomer bulge" or 'greying' of the population.

    The health care industry has grown around the population and its needs ever since it was allowed to privatize (as opposed to prior government and churches' subsidies). It would be ridiculous to expect otherwise. And it did so by people who already had their eye on the future. The conditions there were so skewed that the industry had to prepare itself or vanish. Losing money is no big deal. The big piles are already hidden under someone else's mattress. But to vanish from the users' grasp -- that could not be allowed.

    Picture it. A cake chart. A horizontal line is made on the bottom row, centered, its width representing the people born that year. The next year the same happens, the first gets pushed up. Repeat every year. When there's no more people in an age bracket, that line disappears. The result, in a growing population, is a pyramid. There's more people born every year than the one before. In a stable population, it'd have parallel, vertical sides. Fine. So the US had this pyramid cake going until WW II. Afterwards, from around 1945 to 1965 there were far more babies born than fit the pyramid, and that year's line stuck out too far. After these 20 years was over and the birth rate was brought back down, there was a large bulge in the pyramid. Year by year this moved up. The bulge is now placed about where the people from within it are retiring (or of that age). And now comes the fun part.

    As the boomers leave the work force, the income available for taxing or paying for health care drops. These people begin to pile into the already overburdened government subsidized programs for social security and medicare. There will be less income per yer due to more boomers going into the 'retired' bracket, more money required for more treatment for more people who are living longer than ever before, and fewer to draw on.

    From 2030 to 2050 there will

    --
    "I may be synthetic, but I'm not stupid." -- Bishop 341-B
  99. It's all economics by Henk+Postma · · Score: 1

    IT will only save you money if you can do the same work faster and/or more cheaply than the competition. If all hospitals implement similar systems, that is now the new standard and you don't have a competitive edge that allows you to lower your operating expenses as compared to other hospitals. This is basically one of Parkinson's laws, as mentioned below.

    Of course there may be problems with the IT systems in hospitals. So at some point in the future, one company will make a product that works really well and solves these problems. The first hospital to acquire the system will lower operating expenses, increase their efficiency. They can then attract more 'business' by lowering their price. Then the same company sells the system to all the other hospitals, and all their operating expenses will be reduced, efficiencies increased. Prices drop, new baseline reached. Lather, rinse, repeat.

  100. Bumrungrad Hospital (Bangkok) by aaarrrgggh · · Score: 1

    If you want to see computers saving hospitals money, get a physical at Bumrungrad Hospital in Bangkok. The system is multi-lingual, and you get results almost immediately. I don't know that a legacy hospital can pull off the same things, but it is truly amazing to see.

    Compared to my physician's scribbles on pre-printed form letters, it really does a lot to make it look like the doctor knows what they are doing and communicate effectively.

  101. I can fix that by rcharbon · · Score: 1

    It's not the systems. Replace the people with competent workers. Then you'll see real gains!

  102. Yet another reason not to send my kid to Harvard? by watsonoo7 · · Score: 1

    Yeah. Let's just drop kick all of those pesky little clinical applications that help the care givers deliver the right medications to the right patients. It's probably a lot cheaper just to pay the attorneys and plaintiffs. I'll admit it. I haven't read the Harvard report. Nor will I. Nothing personal against Harvard but if the report is actually as stupid as the slashdot teaser indicates then it would be just a waste of time. While we're at it let's get rid of all of the technological devices that dump our medical data into the clinical apps too. Those really expensive MRI machines are only creating huge data files that make the clinical applications even more inefficient and expensive.

  103. Unstructured data by mahadiga · · Score: 1

    Information in most of the medical records is unstructured. I believe http://www.mediawiki.org/ is right solution for unstructured information instead of multi-million dollar solutions vendors are offering.

    --
    I'd like to buy homeland for our 10 million people. http://twitter.com/mahadiga
  104. Accountability by huckamania · · Score: 1

    So much for a noble profession. The new millennium is starting off by killing any pretense that a noble profession of any sort exists.

    We can't trust politicians, that's a no-brainer. The press, don't make me laugh. Lawyers in general, judges? No trust there. Teachers and professors don't seem to command much respect these days. We're all for law and order, but how much do you really trust the cops? How about the cops in NYC or LA or NO? Scientists apparently have egos that allow them to do anything to further their cause. And now doctors would rather CYA then have their medical opinions opened to scrutiny.

    Firefighters, that might be the last noble profession. Cue the scandal in 5...4...3...2...1...grrr!

  105. Genetics student here by Gaffod · · Score: 1

    Sequencing the genome with paper... Hahaha, oh wow. Do you realize that there are, to go by your car-analogy-without-the-car, millions of Eiffel Towers and each is different in as of yet unpredicatble ways? Do you realize that the entire hierarchical structure of the Eiffel Tower was simple enough to be understood by the architects, and indeed was understood, whereas there has been a whole branch of science expressly devoted to that task for the last half century with genetics?

    I'd go and bring secondary structure and "Eiffel tower hairpins" into this, but I'll spare you the mind blow.

  106. Somthing's Wrong... by Anonymous Coward · · Score: 0

    "Computers Don't Save Hospitals Money"

    let me fix that for you....

    "Crappy Software Doesn't Save Hospitals Money"

    there, that's better

  107. Ideally by Geminii · · Score: 1

    Short of a full-hospital AI, there needs to be some way to allow doctors and other medical staff to call up any relevant information for a given case - potentially meaning anything at all which has been presented to hospital staff or approved external medical channels. Every question asked, every scan done with any instrument, every moment that a patient is on a security, ER, or ambulance camera, needs to be able to be summoned up with a snap of the fingers or a flicker of the eye. Information is no good if it never goes anywhere, or goes into a dead end in some physical or digital filing cabinet.

    Staff could even have their infocloud viewpoint personalised based on their hospital function, personal qualifications, and previous patterns of search/use, edged with additional data drawn from likely helpful sources based on the use-patterns of other staff, the similarities between positions and processes between them, and even a patient's particular medical history. That way, a fresh newbie with a particular job title would start with a default set of views based on the averages of other people who have been doing the job for a while, and which would rapidly adjust and speed up as they establish personal methodologies.