Slashdot Mirror


Major Health Organization Stops Forcing Doctors To Adopt New Technology (internalmedicinenews.com)

nbauman writes: The administrator of the Centers for Medicare & Medicaid Services, told an investors' conference that they will be backing off the unpopular requirement that doctors show "meaningful use" of their new computer systems. Andy Slavitt, acting administrator, admitted that "physician burden and frustration levels are real. Programs that are designed to improve often distract. Done poorly, measures are divorced from how physicians practice and add to the cynicism that the people who build these programs just don't get it."

Dr. James L. Madara, CEO of the American Medical Association, agreed that EHRs were having a negative impact on physicians' practices. Many physicians are spending at least two hours each workday using their EHR and may click up to 4,000 times per 8-hour shift, he said. Instead, CMS will reward health care providers for patient outcomes through the merit-based incentive pay systems created by last year's Medicare Access and CHIP Reauthorization Act (MACRA) legislation.CMS is calling on the private sector to create apps and analytic tools that will keep data secure while fostering true and widespread interoperability.

111 comments

  1. CMS? by Anonymous Coward · · Score: 0

    Centers for Medicare & Medicaid Services

    Shouldn't that be CMMS? Or are they really talking about Content Management Systems?

    1. Re:CMS? by Anonymous Coward · · Score: 0

      I'm sure he's just glad not to be talking about healthcare.gov for a change

    2. Re:CMS? by kelemvor4 · · Score: 1

      I'm sure he's just glad not to be talking about healthcare.gov for a change

      What's that?

    3. Re:CMS? by ColdWetDog · · Score: 2

      It's all mumble mouth buzzwords, but yes, for some bog knows reason, it's typically referred to as CMS. Or other words inappropriate for a family oriented web site.

      --
      Faster! Faster! Faster would be better!
    4. Re:CMS? by Ungrounded+Lightning · · Score: 1

      Centers for Medicare & Medicaid Services

      Shouldn't that be CMMS? Or are they really talking about Content Management Systems?

      I THINK the government had the TLA first. (Like before the passage of Medicaid, when there WAS only one M in the acronym.)

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  2. Meanwhile in France... by Anonymous Coward · · Score: 0

    Carte Vitale is working fine.

  3. Doctors: Whiny bitches, all of 'em. by mythosaz · · Score: 5, Insightful

    I spent about a decade doing high-level end-user compute management for a large healthcare organization.

    There are two major forces at play.

    Doctors just want fancy equipment so they can keep up status.
    Doctors are lazy and entitled, and can't be bothered to do anything beneath them.

    I've been on countless projects for SSO or (reduced signon, anyway) and context management. I've had to make sure countless pretty-boy doctors could get the new device that the OTHER hospital gave THEIR doctors. It's **all** about physician satisfaction. It's a seller's market, and if you don't give the doctors every last thing they demand they will go to work at the other hospital down the street. Of course, doctors know EVERYTHING, so there's no negotiating with them at any level. Site managers know they're fucked, and we know site managers are fucked, so we bend over and take it.

    The context management systems (that keep patients synchronized across multiple clinical apps -- your EMR, or your radiology app, or your bed placement app, or your 10 other non-integrated apps) all suck and are fantastic boondoggles. SSO works for major systems, but unless you're AMAZING and have every last system in Cerner (or whatever you use), your docs will fuck that up too and blame IT.

    Whiny bitches, all of 'em.

    1. Re:Doctors: Whiny bitches, all of 'em. by Thud457 · · Score: 4, Funny

      I'm a Doctor Jim, not some e-paper pushing records clerk!

      --

      the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

    2. Re:Doctors: Whiny bitches, all of 'em. by Anonymous Coward · · Score: 0

      If anyone has mod points give it to this man.

      My experiences were the same.

      I once saw a doctor drop 5k on his personal computer and then buy the people who run his business ever day a 14 inch black and white monitor (the price diff was 2 dollars, for 17 and color).

    3. Re:Doctors: Whiny bitches, all of 'em. by Anonymous Coward · · Score: 0

      If the systems are so easily fuck-upable, doesn't that say something about the systems setup? I'm not specifically blaming IT, but you seem to shirk off ALL blame.

    4. Re:Doctors: Whiny bitches, all of 'em. by Anonymous Coward · · Score: 0

      so... you are whining that others are not taking to your method of doing their jobs... entitled much

      also why are you pushing such, and i quote, sucky and fantastically boondoggled apps and then complain when they get fucked...

      sounds like an entitled IT issue to me

    5. Re:Doctors: Whiny bitches, all of 'em. by Anonymous Coward · · Score: 0

      When was this? The 1980s? I think I saw a Computer Chronicles episode about this; Stewart Cheifet's combover was in it.

    6. Re:Doctors: Whiny bitches, all of 'em. by Rei · · Score: 5, Insightful

      I've also worked in the industry, and I'm of the opposite view: a lot of interface designers have given doctors crappy interfaces that don't take into account real-world use cases.

      My particular field was psychiatry, so a lot of the software was tablet-based and focused on asking subjects questions and recording observations of the subjects. The important thing was to realize that these aren't some sort of web-poll - the real world is complex. Maybe the subject will throw a fit and walk out partway through or refuse to answer questions, or only give answers that don't make sense or aren't clear. Perhaps a question's answer choices don't reflect all of the nuances of the situation, something the form designer didn't think of. Perhaps something important or unusual happens in the interview that the doctor needs to note. It's important that software be as flexible as pencil and paper - that they can "pick it up" and "set it down" whenever they want, that they can add answers or scribble notes wherever, etc, and all of this gets recorded, is available to others, and doesn't just "disappear" on them.

      Much of modern data-collection interface design is about trying to constrain people - you must do X, Y, and Z, in this order, with some nicely laid out plan of how everything's supposed to be done, etc. But sometimes that's just not practical in the real world. We found that when we made the software have the same "features" as paper, while still collecting data, acceptance was quite good.

      Be nice to your users. You can point out possible errors or omissions (so long as you're not being a pest about it), but don't constrain them, don't try to *make* the data be "perfect". Just trust that they'll record the data as best they can. And be ready to handle any imperfect or incomplete data because well, congrats, we live in the real world so sometimes data is just simply going to be imperfect.

      --
      He's the sort of person who would sell the Red Cross to Dracula.
    7. Re:Doctors: Whiny bitches, all of 'em. by Locke2005 · · Score: 0

      Doctors do what they have always done: push everything they don't want to do off on the nurses, who push everything they don't want to do off on CNAs, etc. Every time I visit my physician now, first I wait for the nurse to come in, take vitals, and enter all information in the computer, then I wait for the Doctor to come in and talk for 5 minutes. The only thing the Doctor using the computer for is printing prescriptions. Isn't this just human nature, anybody that can get someone else to do the tedious tasks for them... does! Case in point: my dad is the best cook in the family, and I'm the worst, but my dad used to make me cook for him, just so he wouldn't have to do it himself!

      --
      I've abandoned my search for truth; now I'm just looking for some useful delusions.
    8. Re:Doctors: Whiny bitches, all of 'em. by ColdWetDog · · Score: 5, Insightful

      Well mine are somewhat different. I'm a physician and have been working with EHRs since the late 1990s. When we had 386 processors and liked it. Yep, there are asshole entitled doctors (and $your_favorite_whipping_person). Lots of physicians would like an EHR that would, you know, help out. Instead we get systems that are designed to 1) help the billing department (an important aspect of medicine, but not the most important) and 2) get little gold stars by following the Meaningless Abuse, er, Meaningful Use "guidelines'.

      Medicine is not an easy subject to computerize. For one thing, the old saying 'whey you computerize chaos you end up with computerized chaos" is quite true. Much of medicine is still hunches, witchcraft and showmanship - things most computer systems really don't deal with well. The rest is completely driven to insanity by several decades of Medicare and Medicaid rulemaking on top of often completely contradictory rules by Congress. In it's current state, you can't possibly do everything correctly because you would run afoul of something along the way. I've often thought that if you tried to program an AI to follow Medicare rules it would eventually just unplug itself as the only rational approach.

      And no, Obamacare didn't really change much - just added a few more insane rules to the giant pile.

      Meaningful Use was one of those things that might have been a good idea if one person set it up and left it in a corner. But it morphed into a giant committee that had inordinate power over EHRs and singlehandedly did more to screw up the advancement of electronic health records than any other single decision by the US government.

      There is a god. I will sacrifice a whole box of Rigatoni to His Noodliness in thanks.

      --
      Faster! Faster! Faster would be better!
    9. Re:Doctors: Whiny bitches, all of 'em. by weszz · · Score: 0

      Impressive physician... I'm on the IT side of healthcare, just thinking about the years and tons of money on servers and software we have put in to make meaningful use happen.

      it was a TON.

    10. Re:Doctors: Whiny bitches, all of 'em. by Solandri · · Score: 4, Insightful

      There are two major forces at play.

      Doctors just want fancy equipment so they can keep up status.
      Doctors are lazy and entitled, and can't be bothered to do anything beneath them.

      You've just broken the cardinal rule of User Interface design. The user does not exist to use the device; the device exists to be used by the user. If the user is unable or unwilling to quickly adapt to the device's UI, the fault is in the UI, not the user. It doesn't matter if they're lazy, entitled, stuck-up, whatever. If you want your device to be successful, you have to make them want to use it.

      I've been helping several doctors set up and transition over the EHR systems. The thing I keep hearing over and over again is, why do they have to do this when paper records were working just fine? In other words, the cost of computerizing their patient records is exceeding the benefit they're seeing. And this isn't doctors and nurses who are trying to learn a new EHR system. Most of them have been using a EHR for 2-3 years now. They know how to use the systems, they systems are just so convoluted that it's impeding their workflow compared to paper records. That's a massive failure of user interface and software design.

      Why do you think Apple is so successful despite selling technically inferior products? Because they get this - they make their devices dirt simple to use.

    11. Re:Doctors: Whiny bitches, all of 'em. by ColdWetDog · · Score: 5, Interesting

      Yep, I spent all summer of 2013, and I mean all summer, trying to beat our POS EHR into some semblance of utility. It was a total failure and it looks like I will be spending the entire summer of 2016 trying to figure out how we disentangle ourselves from this mess. A complete was of a lot of time and money that could have been spent doing something useful.

      And "Meaningful Use" was a big part of the reason that our vendor screwed the pooch. It wasn;t a very good system to begin with (Healthland Centriq), had been developed before Meaningful Use was a gleam in the committee's eye and the vendor spent precious (well, cheap Indian) developer hours trying to shoehorn MU requirements into the system instead of getting it to just work. And that little game was repeated all over the country.

      --
      Faster! Faster! Faster would be better!
    12. Re:Doctors: Whiny bitches, all of 'em. by Anonymous Coward · · Score: 0

      i didn't write it, i just do in-house support for it because its what management paid for the users to use. any bugs or discrepancies go to our in-house application analysts and clinical informatics teams. if they don't like the software, they can talk to my management because it's not my decision to make. captcha: passive... touche slashdot.

    13. Re:Doctors: Whiny bitches, all of 'em. by The-Ixian · · Score: 1

      Yep, I spent all summer of 2013, and I mean all summer, trying to beat our POS EHR into some semblance of utility.

      I am going to go ahead and assume that is not Point Of Sale.

      --
      My eyes reflect the stars and a smile lights up my face.
    14. Re:Doctors: Whiny bitches, all of 'em. by The-Ixian · · Score: 1

      I am the opposite.

      If you want something done right, you do it yourself.

      That pretty much sums me up as a person. I don't like the way anyone else does laundry, vacuuming, dishes, cooking, you name it. I do not delegate and I do not multitask.

      --
      My eyes reflect the stars and a smile lights up my face.
    15. Re:Doctors: Whiny bitches, all of 'em. by Applehu+Akbar · · Score: 0

      "Doctors are lazy and entitled, and can't be bothered to do anything beneath them."

      During my IT consulting years, I saw this all the time. Regional medical systems are implementing electronic record systems, but the industry is still in the islands-of-automational era that other lines of business passed through years ago on their way to higher levels of technology.

      Whenever you are referred to a specialist and see that wall of paper patient jackets behind the receptionist, you have encountered another prima donna who can't be bothered to join an integrated records system. As a new patient, you will have to fill out another one of those paper forms with medical history diseases and dates that should be being pulled from the central records system at the push of a button. If it's important that the doctor know how old you were when you had chicken pox, it's important to save that information once and not run the risk that the patient will eventually forget it.

    16. Re:Doctors: Whiny bitches, all of 'em. by X-Ray+Artist · · Score: 2

      I once thought similarly. I'm not so convinced now. I once thought that healthcare technology was just going to take awhile to get better at communicating. I now think the lack of communicating between various systems using the same standard (DICOM, HL7,etc) is intentional to get the Healthcare providers to only buy their product. HL7 is supposed to be a standard, but you have to look in multiple places for the data. One system will use one field and another will use another field for the same data. When you call the companies, they all want the other guys to change their system.

      So the technology isn't helping the Provider's work flow.

      Banks got their technology right. You can go to almost any bank and access your money. Not the same with healthcare. It just goes to prove you can mess with people's health and lives, but don't you dare mess with their money.

      --
      I would have a sig but I am too busy updating programs and restarting my computer
    17. Re: Doctors: Whiny bitches, all of 'em. by guruevi · · Score: 1

      Your own fault for trying to integrate an endless amount of closed source, unsupported software packages. If hospitals would stop buying shit from these companies, these issues wouldn't be nearly as complex.

      I work with some of these and have on my side (a small center, no budget) an open source PACS, data receivers, scheduling system, device and patch management, the whole kaboodle. Now we are getting patient data and need to implement HIPAA regulations. This will take me a few days tops because I can write my own plugins that searches old data and does the required things to new data. My counterparts in a hospital have been HIPAA regulated for years and still are waiting to get their vendor that they payed millions to support the specifics. Having access to the system, besides the "branding" it doesn't actually do anything beyond what I do and the hospital is rife with middleware to get data in and out of the system. And no, the vendor isn't responsible for data stored at the covered entity.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    18. Re: Doctors: Whiny bitches, all of 'em. by Anonymous Coward · · Score: 0

      Medical software is the absolute worst garbage I have ever seen period. It would be pointless to try and explain why as anyone who has had the displeasure of having to use it needs no convincing and those that haven't wouldn't believe the problems without seeing it first hand.

    19. Re:Doctors: Whiny bitches, all of 'em. by Anonymous Coward · · Score: 0

      you can interface systems together fairly easy with a scripting engine. we interface about 400 different systems, between HL7, MAGIC, DICOM, and several other formats. i don't know the specifics on all the systems, but it can be done, at a minimal hardware cost of running the engine.

    20. Re:Doctors: Whiny bitches, all of 'em. by Anonymous Coward · · Score: 0

      Be nice to your users. You can point out possible errors or omissions (so long as you're not being a pest about it), but don't constrain them, don't try to *make* the data be "perfect". Just trust that they'll record the data as best they can. And be ready to handle any imperfect or incomplete data because well, congrats, we live in the real world so sometimes data is just simply going to be imperfect.

      The users are assholes.

      EMR UIs are largely the clusterfuck they are because of the users. Every hospital is a special snowflake that has its own way of doing things and who the hell are you to tell them otherwise? As a result, every dialog in every application must be configurable: the data collected, the order in which it is collected, and how the data maps to the EMR's internal data. This makes setting up the system incredibly complex. Invariably, nearly every hospital will have a few applications which aren't configured correctly for any number of reasons (can't be bothered to pay for enough/competent people to set it up, can't be bothered to monitor the system to see when/where things fail, etc.).

      What's needed to make the systems truly intuitive and easy to use is to create standard practices that the systems can then implement. This will require doctors use a little less witchcraft (as mentioned above) and more data-driven medicine. You'd think they would have learned back when it was proven washing your hands before surgery reduced the fatality rate.

    21. Re:Doctors: Whiny bitches, all of 'em. by turbidostato · · Score: 1

      "The user does not exist to use the device; the device exists to be used by the user."

      Right.

      "If the user is unable or unwilling to quickly adapt to the device's UI, the fault is in the UI, not the user."

      Wrong.

      "If you want your device to be successful, you have to make them want to use it."

      Right.

      What do all these teach us, children? That things depend if you are to produce a device to be successful or to produce one to be useful.

    22. Re:Doctors: Whiny bitches, all of 'em. by arglebargle_xiv · · Score: 1

      I'm a Doctor Jim, not some e-paper pushing records clerk!

      Exactly. You're not in Guatemala now.

    23. Re:Doctors: Whiny bitches, all of 'em. by arglebargle_xiv · · Score: 1

      If you want something done right, you do it yourself.

      Exactly, that way you know your medical procedure will work out. I once performed an appendectomy on myself with a rusty sardine can. Another time I was caught short without instrument one and removed a uterine tumor with my teeth. But that was in the Upper Effendi.. in any case DIY medicine is perfectly practical, you just need to remember to wash the suction cup by swishing it around in the toilet-bowl before you use it for heart massage.

    24. Re:Doctors: Whiny bitches, all of 'em. by Anonymous Coward · · Score: 0

      Wow. You are whining about whiny doctors. What you just described is the condition known as humanity. IT guys who know it all blame doctors. Doctors who know it all blame patients / and or incompetent IT guys or nurses. Nurses who know it all blame incompetent EMS guys. Everyone in my experience always has all the answers and it is always the fault of the next guys who fucks it up for the rest of us. I know I have some health issues, and I can always get good medical advice about what I should be eating from the convenience store clerk who knows it all. However I do not really believe she knows any less than the certified dietician who has gone to school and received the official canonical science certified gods honest truth about the proper diet, because this diet will be superseded a week from now when a new study comes out telling people to eat the exact opposite of what previous sciencey nutritionists certified study told you to be eating.

      EVERYONE is full of shit and is convinced the next guy does not know what the fuck is going on, and everyone is probably correct about this one fact.

    25. Re:Doctors: Whiny bitches, all of 'em. by Anonymous Coward · · Score: 0

      1) help the billing department (an important aspect of medicine, but not the most important)

      I write medical software. billing is the most important thing to the people paying me.

    26. Re:Doctors: Whiny bitches, all of 'em. by pnutjam · · Score: 1

      Yes, once again we see that despite the rhetoric, "Doctors are too full of themselves...", the real problem is Management. They only worry about the bottom line, give into unreasonable demands (arbitrarily, because they'll fight it if they feel like it), and engage in cronyism. All of this destroys any chance for EMR to work.
      For similar examples of Management screw ups with different whipping boys see:
      * Automaker Unions
      * Unions in General
      * Teachers in American schools
      *Too big to fail banks

      Our system is not capitalism, it is (mis)managementism, and we need a change. Corporations are the main driver of this travesity, let fix things.

    27. Re:Doctors: Whiny bitches, all of 'em. by pnutjam · · Score: 1

      Don't forget all the big data proponents. You can't easily pack free form data into a database and crunch it up. Data analysts think everything can be chopped up and analyzed. They are a big driving force in the travesty of EMR.

    28. Re:Doctors: Whiny bitches, all of 'em. by pnutjam · · Score: 1

      Yeah, most EMR seems to be entered by the person who least understands what they are entering.

    29. Re:Doctors: Whiny bitches, all of 'em. by david_thornley · · Score: 1

      If something isn't successful, it isn't useful. If the records are supposed to be on the software, and it's too much of a pain to use, records will be kept on paper instead.

      We're talking about people who were doing nicely pre-EHR. Give them something that's actually better from their point of view and they'll use it. Give them something that slows them down and makes them worse at caring for patients, and it will not be properly used.

      The effective features a system has isn't the list of features, it's the list of features that most people are willing to figure out how to use. In the 1940 Battle of France, the French had tanks that were superior in gun and armor, but couldn't be used at full potential because of all the demands placed on the commander in a one-man turret. German tanks were effectively superior because they had three men in the turrets and radios. Smartphone cameras can't be as good as standalone cameras, but they are so useful because they're attached to something wildly successful. I almost always have my phone with me, so I can photograph anything I see.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    30. Re:Doctors: Whiny bitches, all of 'em. by luis_a_espinal · · Score: 1

      "The user does not exist to use the device; the device exists to be used by the user."

      Right.

      "If the user is unable or unwilling to quickly adapt to the device's UI, the fault is in the UI, not the user."

      Wrong.

      No. Right. The term "user" does not represent the ubiquitous lazy a-hole who is always difficult to work with. This term represents the broad sample of users, good, average, and bad (because, in general, not every user, or the majority, in a sample population, are bad or lazy or stupid.)

      So, in general case, if the "user", meaning the sample population the term represents, is unable or unwilling to use a UI solution, then it is the UI's fault (or the system in question is not solving the problems that truly need solving.)

      "If you want your device to be successful, you have to make them want to use it."

      Right.

      What do all these teach us, children? That things depend if you are to produce a device to be successful or to produce one to be useful.

      It doesn't matter if a system is useful if it is not successful. Barring coercion from above, a successful system is adopted for allowing users to be useful with it.

    31. Re:Doctors: Whiny bitches, all of 'em. by turbidostato · · Score: 1

      "It doesn't matter if a system is useful if it is not successful. Barring coercion from above..."

      There: that's exactly the point. There's a lot of things that get done because they need to be done. Taxes is the first thing that comes to my head, whatever is needed to acomplish your job comes second.

      Not that I (fully) disagree with your obvious point but that quite a lot of times I've seen users moaning when related to computers' interfaces to a level that would just sound ridiculous on basically any other level of your professional live: I don't see, i.e. bulldozer operators moaning about how difficult is to drive their machines despite of the fact that a) is much more difficult than the vast majority of computer UIs and b) bulldozer operators don't usually are extracted from the top 10 IQ percentile. How in damn hell is it possible that somebody capable of sucessfull brain surgery finds some forms on a computer unbearable? Except because of arrogance, that is.

    32. Re:Doctors: Whiny bitches, all of 'em. by sribe · · Score: 1

      Yeah, I write EHR software for a living, and I firmly believe that assholes like you are one of the major problems with EHR software. Doctors have a tough job, and jerk-off entitled know-it-all developers with bachelor's (or associate's, or no) degrees who don't listen and get defensive at every little criticism of the shit-ass god-awful workflow monstrosities they create, are a huge problem.

    33. Re:Doctors: Whiny bitches, all of 'em. by Anonymous Coward · · Score: 0

      Medicine is one of the easiest subjects to computerize. Medical diagnosis is basically a decision tree, it's the exact type of problem that computers excel wildly beyond humans at. The people practicing it with hunches and showmanship are the problem, but they don't realize it because they generally aren't trained in anything that would enable them to problem solve at that level. Unfortunately the same type of people are also managing our healthcare and have the keys to the gateways that prevent much meaningful change.

      Eventually people will see the light and realize how ridiculous it is to have doctors diagnosing health issues when we could already do it so much better with computers, but until then it will be slow going.

    34. Re:Doctors: Whiny bitches, all of 'em. by JimFive · · Score: 1

      We're talking about people who were doing nicely pre-EHR.

      Unless you asked them questions that go across their patient population such as, "How many of your patients are overdue for their mammogram?" or "What percentage of your diabetes patients are successfully managing their A1C levels?" or even, "How many of your patients had a wellness appointment last year?"

      Without an EHR you basically can't answer those questions. The benefit of an EHR isn't at the bedside.
      Having said that, the problems with EHR interfaces certainly exists and hopefully will be improved over the next ten years.
      --
      JimFive

      --
      Please stop using the word theory when you mean hypothesis.
  4. Interoperability starts at the server by xxxJonBoyxxx · · Score: 4, Insightful

    >> CMS is calling on the private sector to create apps and analytic tools that will keep data secure while fostering true and widespread interoperability.

    If they were serious about interoperability, the Feds would go after Epic Systems, GE and every other provider of incompatible and ridiculously expensive health care software first. Interoperability ain't a problem to be solved with the next crappy Fitbit clone...

    1. Re:Interoperability starts at the server by zlives · · Score: 1

      so what we need is a single managed healthcare system :)

    2. Re:Interoperability starts at the server by Anonymous Coward · · Score: 0

      No, what you need is to force every doctor to document the same way so that every system has the same data to share.

      Oh, you're a neurologist? Great, your software now has a box for cervical dilation in the event that an obgyn ever needs to share data with you. It's after the one for Lung Capacity in case you get a chart from a pulmonologist, next to the box for ...

      That's setting aside the documentation style, one doctor writes out a three page history and physical, the next has a single sheet of paper he made in Word that he circles "Rash", "Fever" and crosses out "Nausea" then underlines scarlet fever and checks off a few blood tests and some pills.

    3. Re:Interoperability starts at the server by Anonymous Coward · · Score: 2, Insightful

      CMS Should have Published "Record Format" and "Data "interchange" formats DECADES ago. Then, anyone could make EMR products, and create a market that appeals to the Physician, the Patients AND the Payers. But, No-o-o. We have elected officials who won't allow government agencies do anything that would interfere with what are, in practice, software product monopolies.

    4. Re: Interoperability starts at the server by Anonymous Coward · · Score: 0

      Exactly!

    5. Re:Interoperability starts at the server by techoi · · Score: 1

      There are options being looked at that don't go as far as forcing a single system. One is this: http://www.commonwellalliance....

      If I am not mistaken I believe Canada is supporting multiple EMRs using standardized record and interchange formats for some amount of the patient record. CMS also sets standards if you want to send to them electronically.

      Until we have easily transportable records and the ability for a consumer to actually shop their need for medical services to the "best" (however said consumer defines that) provider, then all this talk about letting the market drive down costs is kind of BS. Now of course the hospitals/networks don't want this and the big EMR companies don't want this, so that leaves the government to force it. I just don't see it happening anytime soon in this country.

    6. Re:Interoperability starts at the server by zlives · · Score: 1

      woosh

    7. Re: Interoperability starts at the server by Anonymous Coward · · Score: 0

      Nope Canada is shit, ehealth wasted billions, current systems are garbage. Slow buggy garbage at that. Ehrs impede work flow here. I have spent 80 grand so far on my current setup and it kills productivity. It looks fancy though.

    8. Re: Interoperability starts at the server by guruevi · · Score: 1

      There are a few number of standards, there is DICOM and HL7 to name the biggest ones you come across. The problem is that if you support a standard, you can't lock your customer into it.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    9. Re: Interoperability starts at the server by Anonymous Coward · · Score: 0

      let me guess, epic?

    10. Re:Interoperability starts at the server by pnutjam · · Score: 1

      Yep, and everytime you pull up a past patient interaction, it will show pages of data, including that, No, the cervix was not dilated... Doesn't matter if the patient is a 12 year old boy with a sore throat.

    11. Re: Interoperability starts at the server by X-Ray+Artist · · Score: 1

      They call them "standards" but they are very configurable. I can't even count the number of times, I was unable to import "DICOM" images to our "DICOM" PACS because of some slight change in the way the "Standard" was configured. Also we exchange images with some other facilities, and certain studies of ours arrive at their destination and can't be displayed. The "Standard" isn't all that standard.

      --
      I would have a sig but I am too busy updating programs and restarting my computer
  5. Who knew? by gstoddart · · Score: 4, Insightful

    Instead, CMS will reward health care providers for patient outcomes

    Which is the only meaningful way to do it.

    All of this bullshit about forcing people to use bad software is just pointless. I only wish more organizations would do this.

    On more than one occasion I've been pushed to "contribute" to SharePoint or otherwise use a piece of software which in no way actually helps me do my actual job. Because someone was more concerned with showing how a useless piece of software was being adopted than understanding why it's not being adopted.

    Yawn, you're going to give me a fucking badge for posting to a forum which nobody is reading and which won't solve my problem, because you stupidly believe "teh soshul networking" is going to solve all your problems, when all it's doing is creating new ones.

    And I've seen far too many systems intended to replace something already in use, which clearly are written by people who just don't get it. It's an often ignored dirty little secret that absolutely crappy interfaces don't get people to use the software because you go through far too much garbage to do anything.

    I've seen stuff which tried to replace custom software, with well written GUIs, for crap which mapped everything to try to look like a spreadsheet ... and which was utterly un-usable. It was like some moron wrote the software with no consideration for what it was being used for.

    --
    Lost at C:>. Found at C.
    1. Re:Who knew? by Junta · · Score: 2

      Particularly in professional software, this is all too common. The pitiable users subjected to it have very little say in the matter, and that reality is reflected in the quality of the software. It's bad enough for common enterprise products from various vendors (IBM and MS commonly), but it just goes completely hellish when we start looking at custom software for particular businesses.

      Like you, I've seen consequences of marching orders that serve more to make people provide supporting evidence to vindicate a decision to spend money rather than actually focusing on providing an experience the end users would actually want...

      --
      XML is like violence. If it doesn't solve the problem, use more.
    2. Re:Who knew? by Billly+Gates · · Score: 1

      Sorry but I do not want my social security number, credit card, or any other personal info expeosed based on a 5 year old XP and IE 7 bug which was patched years ago, but can't be installed because the government won't certify them without spending millions every year.

      Yes hospital networks and computers should be the most up to date outside the tech industry. HA! I know, but really dealing with HIPPA and high tech equipment should have the opposite with up to date software and hardware.

      MRI machines and everything use integrated imaging systems for video and email to patients.

      Hospitals should not be using XP still. No, it doesn't just work as XP is notoriously insecure even if patched.

    3. Re:Who knew? by BitZtream · · Score: 1, Flamebait

      Which is the only meaningful way to do it.

      All of this bullshit about forcing people to use bad software is just pointless. I only wish more organizations would do this.

      I'm sorry, that doesn't mean what you think it means.

      What the new 'preferred' way to do it is ... give financial incentive for doctors to have patients using EHR. Which means the doctor forces patients to put their records on the 'web portal' ... which then promptly gets fucking hacked.

      So no ... its not actually better. You may think its better because it sounds good, but what they said, what you imagined (and most people), and what was done are 3 entirely different things, and the end result sucks for you and me.

      And if I sound pissed off, I am. My 2 year old had his EHR forced onto a portal which was hacked and suddenly the email account I put down for my 2 year old at that office started getting spammed. Took a fucking judge to get them to admit to the issue even happening.

      So pardon me, but FUCK ELECTRONIC HEALTH RECORDS. I want all of mine in dead tree format, making them uneconomical to steal. I want it to remain this way for the rest of my life and the lives of all my descendants ... not because I'm a luddite, but because I'm fucking tired of shitty people writing shitty software that gets hacked and doesn't cost them a damn dime, but costs me time and money. Reference: I work on the billing software for a large phone company, I'm aware of the difficulties in getting properly written software to market when security isn't a concern and when it is ... and until there are harsh fines for leaking information regardless of reason, this shit will continue, and I'll continue to want my records in dead tree format.

      I haven't even begun to point out that there is exactly 0 interoperability in EHR right now, even within different versions of the same software from the same vendor! If you thought Word compatibility was bad, you've not even begun to imagine the bullshit that is EHR.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  6. Studies have shown computers distract doctors by WillAffleckUW · · Score: 2, Interesting

    One of the major problems is people think doctors are just doing checklists, but most of what they do is observe. You're not observing while you're fiddling with your tablet and looking away from the patient. Strangely, having paper is less of a distraction.

    Also, it can create HIPPA security issues.

    --
    -- Tigger warning: This post may contain tiggers! --
    1. Re:Studies have shown computers distract doctors by gstoddart · · Score: 3, Informative

      Exactly, trying to force the tasks required for a specialized task to fit into a GUI designed by someone who has no idea of what that task actually entails is madness.

      Would you do complex engineering with a checklist which looks like it was written as a first year project and which imposes the process on you, but can't me made to actually match the real world?

      Hell, on numerous occasions I've been on the receiving end of some bloody accountant trying to apply his idiotic metrics to something which can't be quantified readily ... why, no, I can't quantify the way in which I will find and fix bugs in a way which is meaningful to an accountant ... and, no, your standard template document has nothing to do with be solving a tricky problem of semantics.

      One size really doesn't fit all. Some sizes don't fit anybody.

      --
      Lost at C:>. Found at C.
    2. Re:Studies have shown computers distract doctors by Bugler412 · · Score: 1

      and if they don't record/chart their observations for the next health care professional to use, using the systems agreed upon by whatever health care establishment they are working at, then communications of sometimes VERY vital information fails and patients die, become injured or fail to get well. Blame the designers (or project managers, whatever) for poor systems, but "opting out" by the doctors is a poor solution to the problem.

    3. Re:Studies have shown computers distract doctors by WillAffleckUW · · Score: 1

      I made an observation. You jumped to a diagnosis without considering the totality of patient care.

      See why computerized systems can be bad for patients?

      The capture points vary, depending on the situations. Think about the total process. A checklist is useful, but we tend to code things that are too restrictive. Restrictive code can distract from observation.

      But then, I work with one of the top research hospitals in the world, so obviously my viewpoint is suspect. Who do you think came up with the checklists in the first place ...

      --
      -- Tigger warning: This post may contain tiggers! --
    4. Re:Studies have shown computers distract doctors by Anonymous Coward · · Score: 0

      Strangely, having paper is less of a distraction.

      Maybe that's what explains the classic doctor's handwriting, never looking to see what you've written.

    5. Re:Studies have shown computers distract doctors by Anonymous Coward · · Score: 0

      Would you do complex engineering with a checklist

      The company for whom I worked my first engineering job had exactly this complete with metrics. Step 1. xxx(5 minutes) Actual:____, Step2. xxx (18 minutes) Actual:____, ....Step 45. Enter metrics into tracking system (4 minutes).

      They had hundreds of these step by step how to engineer processes. I eventually left that company, but returned a few years later and they'd gotten rid of it.

    6. Re:Studies have shown computers distract doctors by Locke2005 · · Score: 1

      Can you name any buyer of software (meaning the guy signing the checks) that isn't just doing checklists? Certainly every marketing department I've worked with seemed to think checklists were the meaning for their existence.

      --
      I've abandoned my search for truth; now I'm just looking for some useful delusions.
  7. Useless Metrics by ranton · · Score: 4, Insightful

    EHRs were having a negative impact on physicians' practices. Many physicians are spending at least two hours each workday using their EHR and may click up to 4,000 times per 8-hour shift, he said. -- Dr. James L. Madara, CEO of the American Medical Association

    How does this metric identify a negative impact in any way? If those clicks are keyboard clicks it doesn't even sound high at all. How about something like "doctors among the top 20% of EHR adoption misdiagnosed 10% more often", or something similar? I'm have no idea if pushing adoption of EHRs is beneficial, but based on the metrics Dr. Madara chose to use they don't seem to have any idea either.

    --
    -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    1. Re:Useless Metrics by Anonymous Coward · · Score: 0

      Even if they are mouse clicks, that's only 1 click per 3.6 seconds. Most people do more than that.

      Also, since when do American doctors work 8 hour shifts? Twelve and Fourteen hour shifts are common for hospitalists last time I checked.

    2. Re:Useless Metrics by freeze128 · · Score: 3, Insightful

      Medical management software is not designed for speed or ease of use. For instance, you work in the Emergency Room and need to log in a new patient, and list symptoms. What you're doing is data entry. You are using the keyboard to enter this information. If you need to click on other pages or tabs, you are taking your hands off the keyboard and moving to the mouse. Then you are moving the mouse to the precise location, and clicking a button. Then you are moving your hands back to the keyboard so you can enter more text. Now do that hundreds (if not thousands) of times a day. This is a ***HUGE*** slowdown, all because the software devs don't bother to integrate keyboard shortcuts or alt-key assignments in their software. They just don't get it.

    3. Re:Useless Metrics by Anonymous Coward · · Score: 1

      I do IT for my parents' small medical practice. They went for meaningful use phase 1, which was something like 30k to cover new equipment, training and software. They did not go for phase 2 and phase 3, since there were a bunch of additional requirements that they did not believe would add anything to patient outcome.

      As a result, they started receiving something like 2% less reimbursement from medicaid and medicare (like 80% of their practice.) So, for my parents, the "negative impact" was worth slightly less than 2% of their income. My mom mentioned that she'd let it get to about -5%, and then reevaluate.

      This is another attempt by the Feds to become involved in things which generally do not make any sense. There is not any kind of meaningful comparison that can be made between a physician's practice in rural Texas, as compared to one at Mayo Clinic in Washington, D.C., in terms of "EHR negative impact." The difference in electronic health record systems is insane, and compound that with the difference between practice sizes, available resources, and base population, make it so the Federal "one size fits all" bureaucratic program is simply not worth it for people to participate in. Eventually, the Federal pressures will become so high that doctors simply will not accept the crappy Federal insurances, such as has been happening in Alaska.

    4. Re:Useless Metrics by Anonymous Coward · · Score: 0

      He actually says it. That's an anecdote and not a study; a quote from the CEO of the AMA who's in a place to know, but he states exactly what he's talking about.

      A big metric that's tracked in hospitals is workflow and procedure efficiency, because there's a lot to do in a hospital and there's only so much staff. What he's saying is doctors are spending 2 hours out of an 8 hour shift working with their EMRs, and his point is that is 25% of the time the doctor is not seeing patients. For the business of hospitals that's a big deal, especially with the current payer system that is entirely procedure based. That's 1 out 4 patients that the doctor can't perform procedures on and get paid for; that's 2 hours per shift of a doctor's time that he's not able to charge reimbursement codes for, so it just adds to the overall problem of increasing healthcare costs because the hospital has to make up the doctor and staff's salary through overhead and not on something that generates revenue, a paid procedure.

      Of course the argument there is to remove the procedure based payment system and move to an outcome based system, but that of course is a highly political discussion for another day.

    5. Re:Useless Metrics by ranton · · Score: 2

      What he's saying is doctors are spending 2 hours out of an 8 hour shift working with their EMRs, and his point is that is 25% of the time the doctor is not seeing patients.

      So what? I spend far less than 50% of my time physically typing software code (as a software developer). The rest of my time is spent in design meetings, user requirement discovery, project management tasks, etc. That is not wasted time. If I spent 100% of my time typing code the quality of my work would take a nose dive.

      Maybe doctors spending 25% of their time keeping good records is too much time. Maybe it is far too little. Nothing in the article shows these people have any idea either. I guess there is no way to know if it was poor reporting or clueless interviewees. But absolutely nothing in the article demonstrates anyone has any idea if these EMRs are actually helping or hurting doctor performance. Its just a bunch of anecdotes from annoyed doctors and meaningless statistics that give the illusion they are doing their job.

      I am not claiming they are wrong about EMR systems hurting the industry. I have no idea. But their choice of comments used to back up their claims gives me near 0% confidence they have any idea how to improve the system.

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    6. Re:Useless Metrics by Anonymous Coward · · Score: 0

      For some private practice doctors, shifts are more like 6 hours a day, 4 days a week.

    7. Re:Useless Metrics by Anonymous Coward · · Score: 0

      Yeah, sure...writing software is just as time-urgent as the patient on the gurney gasping for breath! And, I'll wager, you've never had to install, teach users how to use, or maintain any commercial EMR, and meet all the ICD and other legal requirements.

      Dumbass.

    8. Re:Useless Metrics by Anonymous Coward · · Score: 0

      outside of IT people how many people do you see using keyboard shortcuts? even for things such as copy and pasting? it amazes me how often i see users right click or use the mouse in the Edit menu to copy and paste in a Browser, Email, or word processor, and those typically all have the same keyboard shortcut for this function.

    9. Re:Useless Metrics by ColdWetDog · · Score: 1

      You're correct - he's just blowing steam. The biggest problem is that we don't know what is 'good' health care or 'good' use of an EHR. Doctors tend to view EHRs useful if it decreases 'paperwork' - stuff that is generally not thought to be helpful - but often is. Managers and accountants view EHRs useful if it either saves money by lowering expenses or increases revenue by better billing. Neither have anything necessarily to do with quality of care. The feds look at EHRs as useful if - well, nobody knows. It was supposed to magically improve quality and decrease cost. There was very little real data to suggest that they do either.

      Personally, I think a useful EHR makes my day easier and helps with patient care. If I can get old results quickly, if I can view new results sensibly and if I can more easily communicate what I'm doing to other health care providers and the patient, then a number of vexing problems get better. Unfortunately, current EHRs don't do much of any of those things.

      --
      Faster! Faster! Faster would be better!
    10. Re:Useless Metrics by Anonymous Coward · · Score: 0

      As a physician I Use an EHR, for each click I wait 10 seconds. do the math.

    11. Re:Useless Metrics by ranton · · Score: 1

      This is another attempt by the Feds to become involved in things which generally do not make any sense.

      Improving intercommunication between hospitals and doctors throughout the country seems to be the exact type of thing the Feds should be involved in. Perhaps their implementation so far has been poor, but they certainly shouldn't stop trying. If the medical industry was self governing well and communication between doctors was easy, then the Feds wouldn't need to get involved. But communications standards in the medical industry are abhorrent.

      They did not go for phase 2 and phase 3, since there were a bunch of additional requirements that they did not believe would add anything to patient outcome.

      This is why better metrics are needed, because who knows if your parents are correct in this assessment. If Ford asked people what they want they would have asked for a faster horse, and likewise asking doctors whether improved documentation is helpful for overall public health is not nearly sufficient. A good start perhaps but their view of the problem is far too narrow to be ultimately relied upon.

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    12. Re:Useless Metrics by Anonymous Coward · · Score: 0

      Those are mouse clicks. Typing is extra. Do you know of any other programs where you have to click that much, IN ADDITION to typing? Maybe data entry people, but even then, they probably use tabs a lot more.

    13. Re:Useless Metrics by ranton · · Score: 1

      As a physician I Use an EHR, for each click I wait 10 seconds. do the math.

      Then you need much better EHR software. An EHR is not a complicated piece of software, it is mostly data entry. It needs to be more heavily tested than most software, but it usually isn't doing anything algorithmically complex. There is no excuse for response times above perhaps a tenth of a second for anything but reporting or search features. I have developed EHR and patient monitoring software and have never seen response times like you mention.

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    14. Re:Useless Metrics by tlhIngan · · Score: 1

      Personally, I think a useful EHR makes my day easier and helps with patient care. If I can get old results quickly, if I can view new results sensibly and if I can more easily communicate what I'm doing to other health care providers and the patient, then a number of vexing problems get better. Unfortunately, current EHRs don't do much of any of those things.

      And even more, have the ability to SHARE the information. The problem with current EHR systems is each doctor's system is a data island, which is completely useless!

      EHR systems need to interoperate. If you go to the hospital, the hospital's EHR system should be able to fetch the record from your doctor's office to figure out if it's something your doctor is monitoring, to get what medications you're on, etc. And if your doctor ordered tests, to get a view into those test results and compare them with results now, because that can provide insight into why you're visiting the hospital.

      Then when you visit your doctor, they can pull all the data from the hospital and see how things are going as well.

      It's the sharing of information that makes EHR valuable. A data island means an EHR is just a fancy paperwork keeping system.

      But sharing it among doctors, hospitals and so makes it more valuable. Perhaps you're travelling and have to visit the doctor - the local doctor can pull up your file and review it - perhaps you had a medication conflict. And when you get back, the doctor's notes are also there for your regular doctor.

      And that's the problem - EHR systems are designed purposefully to NOT interoperate by their greedy vendors, meaning they're completely useless systems.

      Perhaps instead of EHR systems, we call it "medical internet" where the goal is to share patient information in ways that help patients. Unfortunately, this will never happen because insurance companies and everyone else will try to hijack it for everything BUT medical care.

    15. Re:Useless Metrics by Anonymous Coward · · Score: 0

      I use ABELMED, Review takes 5 seconds, sign off takes 5 seconds, I have a thinkserver with 32 gb of ram it is fairly new, the raid is quite fast, the workstations are gigabit networked, response time does not vary (I have a mix of workstations, some surface pro's in docks, an hp z workstation and a dell workstation laptop (32gb ram 512 ssd, its quite fast for just about everything except my damn ehr (its my rad viewing station)), all ssd's, windows 8.1 pro for everything. It is a maddening wait game. The software has no reason to be slow, the hardware is just relaxing, chilling. RDPing into the server and running that way produces no performance gain. I am a single provider, I have a nurse and a receptionist. after hours when I am reviewing 100 + documents (~16 min / day) it adds up, plus all the time wasted through the day waiting for that damned blue circle. Previous ehr's were just as shitty, I have used cerner, epic, centricity, touchworks (best one was protouch (an old one, text based, very fast and easy to use, blue screen with white text was a bit annoying though)) among others. Fact of the matter is, EHR software is buggy, slow, full of random reasons to hang and just plain annoy you.

      Yes it is data entry and it sucks!

    16. Re: Useless Metrics by Anonymous Coward · · Score: 0

      What? Lol you assumed a whole lot there. maybe i heard a whoosh. Did I hear a whoosh?

    17. Re:Useless Metrics by Anonymous Coward · · Score: 0

      SO what? The answer is in my post. Your analogy is not the same because your pay structure is different.

      You write code for a living. You spend 50% of your time in meetings and planning meetings and doing all this other stuff. Now imagine you only get paid for the 50% you code. The planning meetings are all critical to success, but you only get paid per line of code. Suddenly you'll avoid all the planning meetings and maximize exactly how many lines of code you write regardless of plan, because that's what your incentivized to do. Your project will bloat, the end use won't make sense or work, and it'll have billions of lines of code, because you're paid by the line of code.

      That's how a doctor is paid. 40% of the doctors in this country are employees of a healthcare system earning a salary. THe other 60% are independent contractors and the hospital acts like a service business to support the service the doctor provides to patients. The doctor's business is paid by procedures run; did he admit a new patient, did he take blood, did he order a lab test, did he perform a colonoscopy, did he give you a heart stint? There's specific forms of insurance reimbursement attached to that, and that's how a doctor is paid. It's not a salary. So the doctors are complaining that they spend 25% of their time doing work on things that are NOT chargeable to a payer because there's no CPT code attached to working with EMR systems, when the way doctors are paid they are incentivized to spend their time finding as many procedures to run on their patients as possible.

    18. Re: Useless Metrics by Anonymous Coward · · Score: 0

      Security. No way we can build a system like that. If a lot of people have access it will be hacked. Imagine if every doctor could log in and pull data. You know how many will deligate it to nurses? Users end up having weak passwords. One cracked account has access to every medical record of every person.

    19. Re:Useless Metrics by ShoulderOfOrion · · Score: 1

      There should be a clear and inviolable line of demarcation between the attempt to improve hospital/doctor intercommunication and the attempt to cut government outlays on medical costs. If not, both efforts are doomed to failure, and in bad ways. However, that's rarely the way the government bureaucrats see it.

    20. Re:Useless Metrics by ranton · · Score: 1

      I completely agree that the way doctors are paid is broken. Doctor incentives are one major reason why EMR systems are disliked (not the only reason, EMR vendors have a huge responsibility too).

      This is why we need organizations like the FED to set up ways for doctors to either be paid based on results or at least have public ratings based on results. And for that to ever happen we need the FED to mandate EMR systems because otherwise we have a chicken or the egg problem (not enough data without EMR to have accurate ratings).

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
  8. Great idea killed by implementation by Anonymous Coward · · Score: 0

    "Provide an encounter summary within X business days" (X = 3 or 1, depending). A lot of the doctors I know don't even finish documenting the encounter until the weekend, and that includes doctors who work on paper and are certain that they'd be even slower if they had to deal with a computer.

    "Beg patients to please log into your portal and download their record and send you messages" Good luck with that, though I heard that the doctors were rioting over requiring 5% of the patients to use their webpage and now they just have to get a single patient to use it.

    They've been absolutely huge on "interoperability" but people who have no idea how doctors document are frequenty amazed at how hard it is to share documents electronically. "What you do mean the cardiologist's computer system has no place to store the brain tumor measurements from my neurologist?! How can my neurologist's software not have a place to hold my chest wall thickness measurements made during my cardiologist's echocardiogram?!!?! INTEROPERATE GODDAMMIT!" Every specialty has their own documentation needs and the software is going to address that.

    There had been some really good stuff in here. Convincing doctors to submit prescriptions electronically instead of scrawled and submit and receive blood tests electronically so they can be shared, these are good stuff. The problem is after they got everyone to do that, they needed new things to force doctors to do.

    1. Re:Great idea killed by implementation by Locke2005 · · Score: 1

      There is another huge benefit from computerizing prescriptions: there are already available expert system that can point out possibly harmful drug interactions, as long as it knows all the prescriptions the patient is already taking. Of course, this check is done again at the pharmacy, but it would make the whole system more efficient if it was caught at the time the doctor wrote the prescription (Ever try to get in touch with a doctor to fix their mistake?)

      --
      I've abandoned my search for truth; now I'm just looking for some useful delusions.
  9. Just solve the problem already by Taxman415a · · Score: 4, Insightful

    EHR systems are a horrible burden on healthcare providers and as they are currently implemented they offer very little of the benefits to the patient that they could. The UI of the EHR system is implemented essentially only for back office use and the provider interface is bolted on as an after thought. It's extremely clear from even a cursory look at the EHR systems that there was little if any thought given to optimize the workflow for the provider. In a given patient appointment, the provider has to click through various functions each of which requires descending 8 levels of menus to click, then wait for the several second delay and back out 8 levels and decent 5 or more levels for the next round. Patient report not being happy that their doctors are staring at a screen the whole appointment, but with the inefficiencies built into the UI it's literally impossible not to. In addition one of the main theoretical benefits of EHR systems that providers can pull up your health history and make decisions based on all of the information doesn't work because the different systems don't really interoperate as they were supposedly required to do. If you see a specialist that's on a different EHR system you either can't actually access the information without sending IT a request for that information and waiting for it to be made available or it will be in some even more horribly inaccessible format such as an image. Instead of wasting time on apps and analytic tools there should be some real teeth implemented into the interoperability requirement. Instead of being paid Billions of dollars to make systems that have only fake compatibility, they should be required to come up with systems that interoperate seamlessly. I'm going to take a bet that if there were some real, serious teeth implemented such as no government payments to the EHR providers anymore, the interoperability problem will suddenly vanish. I'm not a fan of heavy regulation in general, but when the companies have taken Billions to meet a requirement and they have managed to implement it in name only, then it's time to pull out the big guns. Don't get involved in the details of fixing the interoperability unless they fail again after being faced with serious consequences. Thing is they probably won't, the problem isn't really that hard to solve given the amounts of money spent. The companies currently don't want there to be interoperability because the current lock in benefits them. When that benefit is eliminated they'll fix the problem quickly.

    1. Re:Just solve the problem already by Anonymous Coward · · Score: 0

      the interoperability problem will suddenly vanish

      The interoperability problem won't vanish until the government dictates exactly how every doctor will complete their documentation.

      I've already been dealing with clinics screaming over just the stage 2 "menu" item for structured family history, they don't understand why they have to spend any extra click(s) to specify which family member(s) had a particular disease. It's not even the doctors complaining about this, patient history is usually collected by a receptionist or maybe a medical assistant.

      You'd need thousands of pooperscoopers to clean up after the shitfit the doctors themselves will throw when the government mandates a totally structured chart.

      Until then, the structures in my chart have no relation at all to the structures in your chart, and we haven't even gone into what happens if I'm an obgyn and you're a neurologist.

  10. sounds like they dont know computers by peter303 · · Score: 0

    Kaiser was doing fine with computerized records 15 years ago and before the Obama stimulus.

    1. Re:sounds like they dont know computers by Anonymous Coward · · Score: 0

      Congratulations, you win the ignorance prize for the first attempt at linking this to Obamacare. The prize for this is the offer to buy a powerball ticket at ONLY 3x the retail cost.

    2. Re:sounds like they dont know computers by James+Carnley · · Score: 1

      Meaningful Use = Obama stimulus package. Nobody even mentioned Obamacare.

    3. Re:sounds like they dont know computers by zlives · · Score: 1

      umm you know anything after Oba... is troll bait.

  11. Shit computers and software. by Anonymous Coward · · Score: 2, Informative

    The problems I have seen when around nurses and doctors is usually that the computer systems themselves are horribly done, and the software is even worse at that. (a common issue I have heard is "this computers going so slow", or "the networks down")
    It is basically the reason there is no paperless office because software and hardware simply isn't as easy to use as paper, nor is it as stable and reliable.
    This is even more apparent in medical situations due to the sort of data they manage.
    The cost to make a very reliable computer-based system is incredibly higher than paper and cabinets in every department.
    Medical systems need to be stupidly reliable so that cost balloons to even higher values than a typical systems installation in even large business.

    Until developer start to make programs that mimic how easy it is to use paper, it will never happen any time soon.
    There are plenty of great programs for editing all kinds of stuff, but so many of them blow 10 kinds of ass.
    Worse yet, most of those are ones done by professionals for large businesses. Half-assed ActiveX crap was one of the worst cases of this. These days it is more half-assed Java, PHP and MySQL.

    Good use of tooltips, an easy-to-access help system (the question-mark feature in some programs where you click it, then click an interface item, is the best in that regard), DESCRIPTIVE menu items.
    So many programs lack these very basic things.
    You shouldn't NEED to do much learning when using an interface.
    If you do, you shouldn't need to read some included PDF or some other readme crap, that is distracting and the user might not have a clue how to describe a visual element on the screen. Having to look through pictures of the UI instead of JUST USING THE UI is stupid, all kinds of stupid.
    JUST BUILD A HELP SYSTEM.

    tl;dr.
    If a system isn't intuitive, it is shit.
    This is the reason most people hate upgraded systems.
    It is the reason WinXP is still a significant OS today despite being over a decade old.

    As usual, change for the sake of change pisses everyone off, not just autistic geeks and Luddites.

  12. Easy to believe. by Viewsonic · · Score: 1

    A lot of health care providers have been moving to newer patient management systems. I have yet to see any nurse, doctor, or anyone else that has to use these systems actually LIKE them. I know two nurses who absolutely HATE the new systems, that doing it on paper and pencil is far quicker, easier, and more efficient than what was put in. Their opinions are echoed across the industry. It's not an age thing, either. These new management systems are trash, and cost millions to implement and install. All it does is factor in our costs going up more and more.

  13. MU Is A Fraud by Anonymous Coward · · Score: 1

    I have been writing clinical software applications since 1983 and have seen a lot. I spent about a year and a half as a Principal Software Engineer at a Meaningful Use vendor. In that time it became quite clear that just about every MU metric can be and is being gamed by hospital administrators to maximize their medicare revenues at no perceptible benefit to (and sometimes to the severe detriment of) the patient. Meaningful use is a farce. It's yet another case of human nature rearing its ugly head: if the people responsible for administering a system can benefit from gaming the system, then the system will be well and truly gamed.

  14. EHR Developers are not EHR Daily Drivers by ErichTheRed · · Score: 5, Interesting

    The state university health system that most of my doctors belong to started using EHR software in earnest about 6 or 7 years ago. It amazes me that the designers and developers of EHR software seem like they design stuff that's intentionally frustrating to use. I've seen worse UIs, but they tend to be for things like buzzword-compliant ITIL based service desk ticketing software, or things that are so proprietary that a functional GUI is not something the customers will pay for. Every time I've gone for an appointment, especially when I'm a new patient (even within the same health system,) the first 10 minutes of the appointment is a frustrated doctor asking question after question, followed by 6 keystrokes, 20 clicks, dropdown here, expand button there, etc. etc. etc. It's as if an offshore code factory was handed a spec, coded exactly to that, and no integration work was done to ensure it would be usable -- and I wouldn't be surprised if that was the case. You might say doctors are a pampered, privileged class who are used to having nurses and medical assistants to do all the "work" but from what I've seen the software is a mess. My dermatologist gave me a "tour" when he found out I was an IT guy -- if I were a doctor I'd be running back to the paper charts in a flash.

    Contrast this with the industry I work in -- airlines. Yes, it's old, proprietary, ancient, slow dinosaur technology.at the core, but the GUIs are designed for maximum throughput. An experienced reservation agent can do a booking in under a minute without taking their hands off the keyboard, and everything in the application is actually designed to minimize cognitive load. As an example, I've never worked behind the counter on real passengers, but I can sit down in front of the GUI and understand the flow, look stuff up, etc. That's because the reservation system companies do actual time-and-motion studies and watch real people use the product. I highly doubt the EHR companies do this, nor do they have anyone on staff who uses their software regularly.

    1. Re:EHR Developers are not EHR Daily Drivers by neapolitan · · Score: 1

      +1 to above. This is exactly my complaint. Lots of doctor-hate above which is weird, but look at the flip side, from a doctor who also does programming and studied CS. The EMRs are TERRIBLE. All of them. However, I don't rant about the incompetence of the IT programmers, because it is a gulf that we both need to address (physicians and IT designers).

      I don't see this staying this way forever, but fixing usability issues are long overdue. In one Epic Fail system (those in the industry know what I mean), there is difficulty in even searching for a drug, you have to do old-style SQL type queries "starts with" or "contains", and spell rythmol as rhythmol and it can't figure it out. Obviously there are dangers to auto-correct with drug names, but finding the correct drug with a simple verification should be facile.

      The UI designers also think that "clicking" is easier, but when you do something 100 times a day, as others have said, having full keyboard control is desired.

      Finally, to load a patient or switch a context might take 20 seconds. Imagine that you have time-sensitive tasks and each time you do something there is 20 seconds of not-really-usable time wasted where you have to sit there and check the screen to see if it is updated? It is beyond frustration and doesn't work into the workflow of seeing patients.

      Granted, I had the same complaints in 2005, and can't believe 11 years later I have the exact. same. complaints.

      --
      Slashdotter, ID #101. UIDs are in binary, right?
    2. Re:EHR Developers are not EHR Daily Drivers by nbauman · · Score: 2

      You may know that doctors used the aircraft industry as a model of rational system design.

      Anesthesiologists lowered their malpractice rate from one of the highest to one of the lowest of the medical specialties by adopting standard aircraft engineering principles. One of their problems was that different hospitals had different anesthesiology equipment, and the controls were all different. Anesthesiologists would often work in more than one hospital in a single day, so they would be moving among different controls. It was like the early days of aircraft, when controls like throttles weren't standardized, so the controls on one plane would make it point up, while the same motion on another plane would make it point down. Since then, aircraft engineers have standardized the controls.

      The conventional wisdom in medicine now is that they should adopt the methods of the aircraft industry. It doesn't always work, maybe because of cultural differences. It's hard to stop prescribing antibiotics inappropriately and sometimes fatally, when patients demand antibiotics for every ill, and give doctors a bad writeup on Yelp when they don't agree to those demands. It's hard to stop unnecessary surgery when a high volume surgeon can make upwards of $300,000 a year, and a low volume surgeon can be asked to leave the practice.

      Interestingly, quality management seems to work well in the government-run British NHS and the US VA hospital system.

      One of the best critics of EMRs is Robert Wachter, a professor of medicine at UCSF, who wrote a book called The Digital Doctor which has a chapter on Epic. Wachter went to Boeing and spent time with the engineers who designed the cockpits.

      Wachter btw wrote this http://www.nytimes.com/2015/03...

      At my own hospital, in 2013 we gave a teenager a 39-fold overdose of a common antibiotic. The initial glitch was innocent enough: A doctor failed to recognize that a screen was set on “milligrams per kilogram” rather than just “milligrams.” But the jaw-dropping part of the error involved alerts that were ignored by both physician and pharmacist. The error caused a grand mal seizure that sent the boy to the I.C.U. and nearly killed him.

      How could they do such a thing? It’s because providers receive tens of thousands of such alerts each month, a vast majority of them false alarms. In one month, the electronic monitors in our five intensive care units, which track things like heart rate and oxygen level, produced more than 2.5 million alerts. It’s little wonder that health care providers have grown numb to them.

    3. Re:EHR Developers are not EHR Daily Drivers by Anonymous Coward · · Score: 0

      I highly doubt the EHR companies do this

      Actually, part of the "Stage 2" certification requirement was to perform recorded user testing for certain tasks to collect # errors, time taken to complete task and so on. No requirement for the users to be able to complete the task quickly or without errors, only that you checked to see if it was doable.

      A bigger problem with meaningful use is the mandate that doctors must use certified software all the time. For the original stage when they were only required to use it 3 months to qualify, this wasn't a problem, but once every single one of my customers had to be using certified software at all times, I had a very, very tiny pool of doctors (almost all pediatricians who see no Medicare patients and therefore weren't required to use certified software) to draw on for testing new features etc. Nobody wants to do duplicate work in two systems just to make sure the second one works better.

    4. Re:EHR Developers are not EHR Daily Drivers by Anonymous Coward · · Score: 0

      you are correct, tehy all fail, not just "epic...Fail"

    5. Re:EHR Developers are not EHR Daily Drivers by sribe · · Score: 1

      I had a very, very tiny pool of doctors (almost all pediatricians who see no Medicare patients...

      Yeah, if not for that loophole, I would have been driven out of the business years ago... The biggest problem is the requirement for re-certification after *any* code change, which basically requires waterfall style development with at most 3 releases, maybe 4 if you have god-like competence in your project management, per year. That's a near-perfect way to completely disallow any and all innovation.

  15. Opposite view by Anonymous Coward · · Score: 0

    I've worked with MD's for many years. Yes, they complain about many EHR things...but only when the EHR does not serve them or their patients, but is instead use to make them into secretaries and used as a means to sue them or rate them poorly.
    If the purpose of EHR's is to increase the speed of patient care, then great. Most docs LOVE being able to access patient records from home or from the office or from the hospital.
    My personal physician had his practice go through THREE different medical records systems in less than two years. It's a waste of his time every time he's got to learn a new system!

    If it's to rate doctors, there are much better ways.

    BTW, the original article asked about making EHR's more universal or more secure...they can't be both. The more people who can access EHR's, the less secure they will be. If every pharmacist, doctor, nurse, social worker, psychologist, nursing assistant, EMT, etc. can read everyone's EHR, how many people will have secure med records? Answer: close to ZERO.

    So which is more important to you, interoperability or security of your medical records?

  16. Let's Start with Something Simple by Anonymous Coward · · Score: 0

    How about getting doctors to print legibly? When they clear that hurdle, then they can move onto computers.

  17. That's good, but EHRs are needed... by ndykman · · Score: 1

    Look, the truly awful, horribly expensive solutions that lock people into insanely overpriced development projects are truly bad. Federal investigation into this company for ripping people off bad. No question. For the very few hospital systems that had their own home-grown systems, they do and still do okay.

    But, the law had a purpose. Not having access to a comprehensive medical records causes injury and death from decisions made without the full record. It's a fairly well researched fact. But, nothing about the current systems address that need in any real way. Frankly, vendors have made claims that are (in my mind) almost criminally false.

    It'd be nice to point and say that engineers are programmers are at fault, but if you look at those vendors and the medical informatics field in general, those who make the decisions are often doctors, nurses and other health professionals. The field is littered those who are unhappy with practicing medicine and think they can be software engineers and researchers instead and the result is an unspeakable mess.

    The first step is that doctors, nurses, and so on will have to work with software engineers, system analysts, interaction designers and so on as peers. Not as contractors, not as subordinates, but as peers. And there are way too few doctors, etc. that can accept that a set of programmers can have just as much of an impact on the health of our population as they can. For better or for worse. And, yes, sadly, too many engineers have too much hubris and disrespect for how hard the care of other human beings truly is.

    And, until we in America accept that access to universal, affordable healthcare is a fundamental right, we won't look far enough past profit to make a difference anyway. So, in the meantime, people will get needlessly hurt, will needlessly suffer and needlessly die.

  18. Yeah - that's the ticket by m0s3m8n · · Score: 1

    Let's take the people with the training, the only revenue generators in a practice, and make them enter data. That's a great use of resources. Now let's make them link all their computer systems to the internet and then fuck them when something goes wrong and data leaks to the intra-webs. Then let's change the billing coding system, ICD-10, that adds almost an insane amount of possible diagnosis codes. Yes, that will bring down the cost of health care. Sure, sure it will.

    --
    Conservative, mod down for violating /. political norms.
  19. It's NOT even a "right" way by Ungrounded+Lightning · · Score: 1

    Instead, CMS will reward health c.are providers for patient outcomes

    Which is the only meaningful way to do it.

    I was onboard with the changes until I hit that one. It is NOT the "only meaningful" - or even a "right" - way.

    As with most things involving punishments for undesired behavior, such a system creates unintended consequences.

    This one would reward doctors who only accept patients with mild illnesses or hypochondria and punish those who take on patients with severe illnesses. The result would be the sicker you are, the harder it would be to find someone to treat you.

    Just as a similar rating system, punishing doctors for "overprescribing" painkillilng medications, has decimated the ranks of pain specialists and led to under-prescription, suffering, and a drastic rise in PTSD (which appears to be prevented by adequate opioid doses in the first week or so after a trauma), this bright idea will lead to increased suffering, disease, and death.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  20. Computerized healthcare by phorm · · Score: 1

    I think some of the most useful - and oft overlooked - advances are in records-keeping and information-sharing. Unfortunately, it also seems that in general there is often a poor track-record of security when it comes to keeping such things private, but it's a trade-off.
    I'm Canadian, so my experience is going to be different than the U.S, but here I can
    a) Go see my doctor's clinic, which recommends an X-ray
    b) Go to a hospital, where they read my script but also can get more details on the request/history from my medical log
    c) Get the X-ray, which gets stored in the computer system both for my doctor to access nearly immediately, but also potentially for any future physicians/specialists
    d) Get a prescription based on the results of the above, and see a pharmacist which checks the current prescription against the records of anything else I may be taking (or known allergies) to prevent dangerous interactions/conflicts

    The system isn't perfect, but technology saves a *lot* of time shuffling paperwork between physicians/locations and can save lives by revealing potentially life-threatening drug-interactions or previous medical history/conditions

  21. I'm Torn by Anonymous Coward · · Score: 0

    On the one hand, I understand the frustration if an EHR/EMR isn't working well. Doctors really should not have to deal with that.

    On the other hand, there is reality. Vendors won't work on workflow optimization unless they have customers to pay for that and are willing to become actively involved. As in, the customer will call the vendor and point out specifically what is wrong, and how they'd like to see it changed. And if that doesn't work (it doesn't always work, it must be said), then the customer moves to a different company or product. That sends a message to uncooperative vendors. A strong message!

    There is a segment of the medical community that is p'eed off because they aren't quite seen with the deference they used to get. Now information is cheap and readily available. The average citizen has a decent education. And medical services are expensive, expensive enough that it's a problem for average citizens.

    You saw the result with ICD-10. There was an elaborate game of "Crying Wolf" among the American Medical Association and various retrograde supporters, claiming the sky would fall, medicine would stop, and patients would be hurt or worse. Instead it went ahead with relatively few problems.

    Why? It was a political football. And a power grab by the AMA.

    The EMRs will get better, it's only a matter of time. So will I defend poorly designed software? Hell no! But I know that this is a temporary situation. And I also know there's a strong will among the least progressive clinicians, to turn back time. And that's not going to happen. The cost of healthcare and footdragging in the medical community has ensured they no longer have control of the public agenda.

    Want to have a positive impact? Contact the people responsible for the software. Bend their ear and try to make a difference. That's what moves the world forward, not bitching on social media to millions of people with no power or involvement.