Slashdot Mirror


IT and Health Care

Punk CPA writes "Technology Review has some thoughts about why the health care industry has been so slow to adopt IT, while quick to embrace high technology in care and diagnosis. Hypothesis: making medical records available for data analysis might expose redundancy, over-testing, and other methods of extracting profits from the fee-for-service model. My take is that it might also make it much easier to gather and evaluate quality of care information. That would be chum in the water for malpractice suits."

17 of 294 comments (clear)

  1. Electronic Health Records is very hard by dreadlord76 · · Score: 5, Informative

    Having worked in development of EMRs, it was an extremely challenging area to work in. Trying to get 3 highly paid doctors to agree on a single thing was very difficult, and it was harder still to convince them to enter the same data the same way. In a particular area, such as diabetic care, it was possible to templatize the intake notes. But when dealing with general care, it became a very difficult data input issue, and meaningful data extraction was messy.
    A very large HMO has spent Billions on an EMR, with major IT consulting involved, and little to show for it. The benefits were very clear over 15 years ago. The medical community wants it to save money, and also to document against malpractice suits. The OP's take on why it has not been adopted was definitely not the view at the VP levels of the HMOs...

    1. Re:Electronic Health Records is very hard by ILongForDarkness · · Score: 5, Informative
      I worked at a cancer centre and controlled the treatment planning, delivery and records. In my experience if something was going to get screwed up across the board it would have to be me that does it. Individual doctors and therapists just had access to one patients "file" at a time. Technology also makes it much easier to fix problems. For example, we had to report the time that a patient had to wait for treatment. The definition of the start date changed (can't remember something like it used to be when the treatment plan was approved by the oncologist, but became the date that the oncologist consult happened), anyways with a half hour of thinking and a couple lines of SQL I was able to change this value to the new definition on 10k+ patient files. With a paper chart they probably would have had an intern sitting around for weeks updating charts rather than practicing medicine. Manual practices are just that, manual, lots of health care provider time is wasted waiting for a chart that someone else has. With an electronic chart everyone can view the same chart at the same time (they usually lock the chart so only one person has write permission at a time though).

      As for hardware reliablity: I had 5 servers, 60 workstations, a CT, and 5 radiation therapy machines (which themselves have 3 computers running in a voting redundant system), in the two years I was there we had 1 day that we were down because our database came back with an inconsistancy after its backup. Patients were then treated with the paper method and it was much much slower, treatments easily took twice as long because of waiting for charts etc. It actually turned out not to be bad, it probably was your stray neutrino scenario, anyways we left it in the state we found it in so that the vendor and database supplier could find the problem so it wouldn't happen again. We could of been back up in an hour because we had tape backups of the system. What happens if someone spills their lunch on a paper chart? Also, for another 50k or so you can get a hot standby server to failover to.

      Also reporting is much easier from electronic systems. I got questions all the time like "what percentile of breast cancer patients getting 20 or more sessions waited for more than one week to start treatment?", I was able to have the answer over a 5 year period in less than an hour. It was much harder for a physician to bullshit his way into justifying his performance when any claim he made could be verified that quickly. In a paper system it would take days of someone's time to verify that stuff and so it probably wouldn't happen until someone had a bad outcome or a malpractice suit was filed.

    2. Re:Electronic Health Records is very hard by Yoozer · · Score: 5, Insightful

      Strange things can really happen with computers, as stray neutrino can strike a transistor and change it's state and either cause a system to crash or the wrong prescription to be issued.

      Why blame computers (and why go the lengths to blame stray neutrons) when humans themselves can screw up far more often and far better?

    3. Re:Electronic Health Records is very hard by adavies42 · · Score: 5, Informative

      neutrino? i think the odds of a neutrino hitting a transistor are about the same as the odds of a 1000-bed hospital's patients all going into spontaneous remission from everything simultaneously, then living to 120. photons or cosmic rays or something maybe, but neutrinos have a 50-50 chance of getting from here to alpha centauri through solid lead.

      --
      Media that can be recorded and distributed can be recorded and distributed.
      -kfg
    4. Re:Electronic Health Records is very hard by c0p0n · · Score: 5, Informative

      I would imagine the picture is very different depending on the country. I work on long term conditions monitoring systems in the UK and obviously our main client is the NHS. Even though our systems (or similar systems from other companies) will save the NHS a lot of money in the medium term it's been very slow to adapt due to the layers and layers and layers of management and middle management which also has a high rotation rate. It's not phobia to tech but politics (ie predecessor project on hold while I get mine to completion type of thing) for the most part.

      About the article, it's fairly misleading and uninformed in my experience:

      Too bad the medical industry has a vested interest in inefficiency.

      Please spare me the conspiration theories. A sizeable chunk of the medical industry is composed of small companies whose main selling point is precisely efficiency and subsequent cost savings. This, the big medical companies can't provide anyway, there's no conspiration, you wouldn't believe the amount of paperwork you need to keep up to date to comply with regulations in this industry and especially with new products, therefore they simply sell same old.

      --

      Your head a splode
    5. Re:Electronic Health Records is very hard by lurker412 · · Score: 5, Insightful

      I, too, spent many years working as a developer and IT administrator. While there are certainly some technical problems--security, privacy, and especially finding a sufficiently expressive standardized vocabulary--the primary issue in implementing computer systems in hospitals is cultural and behavioral. Doctors are accustomed to a great deal of autonomy, and many do not care for the structure that systems impose. The VA has been more successful than most organizations because they can impose systems by fiat. Doctors are often subject to intense time pressure and will resist anything that slows them down. In the short term, it is much faster to scribble a prescription on a piece of paper than to navigate the widgets of any order entry system. Many don't care about the long-term problems that this creates. While administrators are more likely to be aware of the long-term benefits, there is generally little they can do when doctors threaten that babies will die if doctors have to change their ways.

      The premise of the the original article appeals to conspiracy theorists, but I have to say I have never seen any evidence that supports it. The author also fails to provide any. Rather than look to greed, it makes more sense to look at the UI failures of most commercial systems and the inadequate attention given to training and support during implementation.

  2. Re:one word: protectionism by dmr001 · · Score: 5, Informative

    Parent either is full of it or lives in a parallel universe.

    1. Cost is not a barrier? Our EMR costs each physician many tens of thousands a dollar a year in application support, licensing, databases, and for a phalanx of IS personnel in various departments (local, regional, EMR, hospital IS).
    2. MD's have a monopoly? What planet are you on? DO's have had precisely equivalent standing for decades in medical practice in the United States, and NP's are far from being "wiggled in." As a primary care physician, when I send a patient to the cardiologist or pulmonologist, half the time the entire consult is done by a PA or NP.
    3. Please direct me to the land you describe where I can have control over my care environment and take home most of the money. I can't get a contracting pregnant lady into labor and delivery without asking for permission from two nurses, and I'm not aware that the balance of power in any health system I've worked in has been any different before and after transition from paper records. Medical care in most locales in the US has long been collaborative, team-based system, even if you've met a few physicians who are jerks or drive nice cars. (I am looking forward to upgrading my '94 Corolla by 2014.)

    EMR systems have poor market penetration, in my direct experience over the last 9 years, because:
    1. Many, if not most, suck in a medium to large way;
    2. They are incredibly expensive;
    3. They can often be hard to use, and are typically more labor-intensive than paper charts for most physicians in the US;
    4. They don't inter-operate. (When I request old records from other physicians with electronic charts, I enter the pertinent data into my electronic chart by typing it in.)
    If any skilled group of software engineers were to write a decent, usable EMR that was extensible, and didn't cost an arm and a leg, with an eye to being excellent first and profitable as a consequence, they could be up for a Nobel prize.
    TFA refers to cardiac CT to prevent heart attacks. The author, too, lives in a dream world - contrary to her thesis, this test has been shown to help with the boat payments of radiologists and equipment manufacturers, but there is no evidence it helps prevent heart attacks.

  3. As someone who has worked on it... by freedom_india · · Score: 5, Informative

    ...there are multiple reasons and road blocks (natural and artificial):
    1) Healthcare is about making profit. It is not about caring for health. I have seen many IT companies bite the dust during proposals by stating their systems could help caring for health quicker and much better. That's the last thing Blue Cross or anyone else wants.
    The idea for IT companies is to open a presentation with how to increase profits. That, as far as i know, is the only presentation which interests the healthcare company.
    2) There are combinational factors; for instance doctors and software don't go well together psychologically except in times of peace, which is rare. Instead of adopting touch screen systems and throw-away laptops small enough and tough enough, most companies insist on producing massive software run in PCs and Servers in a serene a/c room. Excuse me, which doctor has sanguinely traversed through a maze of Visual Basic or PowerBuilder application menus?
    3) IT companies should seriously stop considering "integrated" systems which connect doctors with nurses with patients with pharmacies. No, for the last fcuking time, no we don't need integrated crap. All we need is a simple system that can be accessed with a max of three clicks and accepts voice input.
    4) Record management: HIPAA is not exactly an easy job. Any standard created by a committee is, by definition, an as$ to work with.
    5) Changes in systems result in changes in behavior and processes: something hated by surgeons, doctors and hospitals.
    Don't attribute to malice what can be explained by stupidity.

    --
    "Doing what i can, with what i have." ~ Burt Gummer
  4. IT is only one facet of healthcare by Anonymous Coward · · Score: 5, Informative

    I think there has always been a serious barrier to the uptake of new information technologies among the medical profession. Most HATE taking notes which is why note taking is left to the junior medical staff on ward rounds. Most clinicians take very brief notes, especially surgeons and only verbose when practicing defensive medicine. Most have a personal way to annotate their notes which cannot fit into any template (eg. unconventitional acronyms, stylized diagrams etc) and are loath to learn new ways of doing things. Sometimes surgical notes only make sense to that particular surgeon or surgeons of that sub-specialty (eg. ophthalmic vitreal surgery... very difficult to decipher...pain in the arse reading their notes.. ) Why? I think some of you guys need to see the amount of stuff medical specialists have to learn and the years of training (at least five here in Australia for specialty training, ( that is after 5-6 years medical school and another 1-3 years as general intern and resident) and then another 2-3 years for sub-specialty training which can involve 2-5 exams and possibly a PHD during the training). There is an incredible amount of stress on the person and their families. (Yes, I think the high standard of medical training IS necessary and not just economic gate-keeping by the medical colleges). During all that training before you are a qualified specialist, your hourly rate can be lower than the hospital cleaners or even not allowed to claim paid overtime at all, as the public hospitals here in Australia frequently runs out of money.

    At the end of all that, I don't think many like to be told how to take their notes.

    I don't think you need conspiracy theories to explain poor uptake of EMRs. In NZ where basically doctors can't get sued (generally speaking), doctors STILL hate EMRs and do poor job of entering data into systems. I once worked for an older surgeon and we got called for an emergency laparotomy on a drunk 19 yo male who lacerated his spleen in a car accident. The surgeon hated taking notes and hated talking to patients but was one hell of a surgeon. All his patient notes consisted of scribbles on flashcards. The young guy's abdomen was full of blood. We had no idea at the time where the bleeding was coming from. The surgeon was clamping major arteries by feel blindly as the suckers couldn't keep up. After five hours the surgery was over and the young guy lived. I tell ya, I had a new found respect for the "old school" surgeon. There are times when you REALLY don't care whether a surgeon is good at filling out forms or has polished bed-side manners.

  5. Who keeps the records? by www.sorehands.com · · Score: 5, Interesting

    I had an interesting experience in China. In 1996, when I received treatment, I kept my own records (they gave me a little paper booklet). This eliminates all the record keeping costs of the doctors and hospitals.

    It might be an interesting model to look into here.

  6. Re:I have a different theory by nikolag · · Score: 5, Informative

    I don't have a theory I have experience.

    I work for hospital that went digital (for patient recodrs) in 2006. All (billing) administration was internally digital (using different, obsolete system working on DOS and floppy disks) from 1997 and to outside world also, depending to health insurance company involved.
    After 6 months of education, switch was made in one day. It was horrible, but after two weeks things were looking just as before. After several months, 75% of administration was more efficient than before, and now, 3 years later, we still print outgoing documentation, but doctors rarely look at papers. Nevertheless, printing expenses went 30% down this year.

    Last year all waiting lists were computerized, and made available (with no patient data) at the web pages. That saved us so many work hours at all departments, but two people switched to that department. This year we are looking into making all internal administrative procedures digital. Hospital restaurant was really happy after we made their menu available online at intranet.

    Several months before introducing the system, all work places received computers with unified user interface, and demo program installed. It was made really clear that someone should consider finding another job if they refused to work with system. People near the retirement (2-3 years) were exempt from this rule.

    The problem very often lies in wanting too much (all). Process should be step-by-step. Billing first, patient records second, intra-hospital administration third or any other way. Every step should be planned, because people will suffer at it, and don't rush it. It takes months, sometimes years for one (new) work flow to settle in.

    Radiology department is still not filmless, probably because it costs as much as putting all patient records in computer. Volume of data that our radiology department produces in one day is equal to 1-2 years of data from whole hospital. On the other hand, introducing PACS and RIS is so much more widespread, but the volume of data makes project harder in the long run. After testing almost a dozen of PACS/RIS demonstrations, one free PACS amazed us with results, holding test data (0.5T of images) and working better than some very expensive solutions.

    --
    Doing a good job is like spilling coffee on a dark suit, you feel warm all over, but nobody notices.
  7. Compter illiteate & overstretched staff more l by yes+it+is · · Score: 5, Insightful
    (Disclaimer: IHAPSITF - I have a PhD scholarship in this field).

    In most healthcare systems, staff are very busy, and computer illiteracy is rife. To get good with these electronic systems you've got to use them constantly, and when half the staff or more don't understand why they're doing a particular thing in a particular way. There's also a workplace culture of written notes, and often a limited number of computer terminals per staff member. So with queuing for terminals, fairly high friction processes for retrieving data and so on and so forth, there are quite high barriers to entry from a human point of view.

    Don't get me wrong, EHRs have potential, and can reap benifits (especially for management - they can also make floor staff's job harder). Some kind of robust iphone-like device which is a secure platform for data entry and retrieval, might make it sufficiently easy and efficient from an end-user's perspective to decrease implementation barriers.

  8. Too few computers, too little bandwidth by ldrydenb · · Score: 5, Insightful

    I can't speak for the US or private medicine but I've seen numerous electronic record systems piloted in the NHS.

    My colleagues would love to have fast access to up-to-date clinical notes rather than play pass-the-parcel (or more often, hide & seek) with a patient's paper case-file(s), but wards tend to have one or two computers per ward and community services may have one computer between three to five staff. So at the end of a shift, when ward staff would be writing their notes, there'd be a queue for the computer. Similarly, before setting out on their visits at the start of the day and after returning from their visits at the end of the day, all community staff want access to the computer at the same time. Also, security dictates that as little information as possible is stored on the user's machine, so the intranet is swamped at these times and users face frustrating lags (I've been unable to access records in time for an appointment as the system was "oversubscribed").

    To increase computer access to usable levels in my former service would have required a 3-400% increase in the number of computers provided to healthcare staff. I have no idea what the resource implications would have been for the service's intranet, but I imagine that a commensurate increase in server capacity (and in the IT department staffing, to take care of all of this) wouldn't be cheap. As a health service manager, having to decide between enough hospital beds or enough computers, which do you suppose is more likely to keep you in your job?

  9. The Many Layers of Complexity by trydk · · Score: 5, Insightful

    As always this is a relatively simple problem wrapped in layers of -- to a certain extent unnecessary -- complexity.

    The simple idea is to have a system that records the patients history of illnesses and treatment (including medication, obviously) and which is easily communicated across different places of diagnose and treatment (GP, specialists, consultants, hospitals, ...).

    This specific problem could easily be solved with standard software like Lotus Notes, Microsoft SharePoint and similar systems, but that is where the simplicity stops and the layers of complexity start.

    Sorry if I am going down a well-travelled trail here.

    Firstly, it is very difficult to get people and organisations to standardise on a single system for good and for bad reasons. (Like "We've already got Lotus Notes, why should we get a Microsoft product?" -- plug in whatever conflicting product/system names you can think of.) This means that a single system probably is out of the question, which leaves us with a standardised interchange format instead.

    OK, now we have a gazillion systems happily exchanging information in a standardised format, so everybody is happy, right?

    Wrong!

    Because secondly, who is responsible for the safekeeping of the data? This is two-fold: Who is responsible for storing the data and who is responsible for who has access to the data?

    So 2a, Responsibility for storing the data: If every place of diagnose and treatment is responsible for storing own data, how can a patient be sure that any specific institution treating her has access to all the information? This needs some centralised storage or at least "mediating" (much like peer-to-peer systems, e.g. torrents, need a "meeting place", like The Pirate Bay, where they can find the trackers so they know where to find the peers). Either system suffers from the problem of connectivity dependence, i.e. if they cannot get access to either the storage, the "mediator" or the peers, information cannot be retrieved. This is still better than paper-based systems, if you are treated in different places, geographically.

    This leads to 2b, Responsibility for who has access to the data: I would obviously like for my GP to send information directly to the hospital and for the nurses, doctors, consultants and surgeons treating me to see my records, but -- being the famous person, I am ... not -- I would be quite weary if just about anyone could look at my records. How is this problem solved?

    Thirdly, who would be responsible for correcting errors and mistakes in the records? This problem is not really an issue relating only to electronic records, but is a general issue, which crops up all the time. Should you, as the patient, be allowed to correct mistakes you know about? If that is the case, how do the professionals make sure that you are not trying to tamper with the system for some ulterior motive (everything from trying to cover medical problems for insurance purposes to hypochondria)? If you are not allowed to correct mistakes, how do you tell them that you did not receive a certain medication two years ago and, in fact, is allergic to it?

    Fourthly, a system relying on doctors, specialists and consultants to type would probably be doomed, at least for now. It seems that doctors, etc. at all the hospitals I have seen, rely on dictation, having a pool of secretaries typing it in and updating the records, which introduces unnecessary delays and adds an extra risk of introducing errors.

    These are some of the many problems facing such a system and I am sure I have left out many, just as relevant. I honestly do not believe that the fear of transparency regarding the treatment is the major stumbling block for the introduction of electronic medical records, but rather the diverse types of problems facing the system.

  10. wrong answer by August_zero · · Score: 5, Insightful

    "Hypothesis: making medical records available for data analysis might expose redundancy, over-testing, and other methods of extracting profits from the fee-for-service model"

    Besides being perhaps the most ignorant thing I have read this morning, this statement reminds me of the irony inherent in listening to tech people whine about how medical caregivers have no trust or knowledge of IT, while the caregivers complain non-stop that IT has no idea how to design a decent medical record system.

    --
    On Wall Street they say "buy low, sell high" On the pad we say, "buy high, sell high" Isn't that somehow better?
  11. IT and Medicine are a Bad Fit by smug_lisp_weenie · · Score: 5, Informative

    One thing everyone seems to be missing here (including the author of the article) is that medical data is an odd duck that just doesn't fit easily into a digital record. (I'm an MD, a medical informatics guy and CTO at a medical software company)

    If you're running a McDonalds you can easily computerize everything: You have a fixed menu your customers can choose from, and every purchase can easily be stuffed into a relational table. Medicine isn't like that.

    Trying to enter a patient encounter into a contemporary medical record system is an extremely unsatisfying experience: Humans are just weird and idiosyncratic and every time you treat someone there will be parts of the patient visit you can't represent symbolically in a piece of software. This is still largely an unsolved problem- If you read the literature on Description Logics you'll see that even PhD logicians have a hard time symbolically storing this kind of abstract data into a piece of software, let alone a doc with little computer training.

    Because of this, most current record systems use a lot of "free text" for storing medical info, which is a pretty ugly hack and everyone realizes this.

    I think this is a major reason for the problems people have with digital records: They don't work very well right now for fully capturing a patient encounter in a rigorous, symbolic fashion.

  12. Re:Hanlon's Razor by TheLoinKing · · Score: 5, Funny

    The Allergists voted to scratch it and the Dermatologists advised against rash moves. The Gastroenterologists had a gut feeling about it, but the Neurologists thought the administration had a lot of nerve, and the Obstetricians stated they were all laboring under a misconception. The Ophthalmologists considered the idea short-sighted, the Pathologists yelled, "Over my dead body", while the Pediatricians said, "Grow up!" The Psychiatrists thought the whole idea was madness, the surgeons decided to wash their hands of the whole thing and the Radiologists could see right through it! The physicians thought it was a bitter pill to swallow, and the Plastic Surgeons said, "This puts a whole new face on the matter." The Podiatrists thought it was a step forward, but the Urologists felt the scheme wouldn't hold water. The Anesthesiologists thought the whole idea was a gas and the Cardiologist didn't have the heart to say no. In the end, the Proctologists left the decision up to some butt hole in Obama Administration.