As reported last year at HIMSS and by many online news and opinion sources since, physician dissatisfaction with EHRs is growing. Indeed, while this blog post doesn’t focus on the broader picture, general physician career dissatisfaction is disconcertingly high.
The breakneck push for more and better EHR use as a component of regular medical care is a significant part of that malaise, but it is insufficient as an explanation. For the most part, doctors really don’t like what the health IT industry is giving them to work with. The HIMSS survey proves it, showing that around 40 percent of physicians would not recommend their EHR to a colleague.
One would expect an industry to develop better products and improve usability, acceptance and satisfaction over time. In health IT, the opposite has occurred, with most pointing fingers at Meaningful Use as the culprit for awkward workflows and Rube Goldberg solutions cobbled together so everyone can get paid in a timely manner.
It seems EHRs are taking more time to use rather than less, which was the original goal.
Secretary of Defense Chuck Hagel’s long-awaited (in health IT circles, anyway) decision on the Department of Defense’s core health IT system has been made. The VA’s VistA system is out as the preferred DoD. Unless it’s not.
In his May 21 memo, Hagel directed the DoD to initiate a competitive process for a commercially available electronic health record (EHR) solution. Understandably, the secretary has to create a level playing field, a competitive process, so he can tell Congress with certainty that due diligence was done. Hate it a lot or hate it a little, this is the nature of our political process.
Already, many are spinning Hagel’s decision as a huge win for proprietary solutions; popular blogger Mr. HIStalk has already established Epic as the frontrunner in the upcoming DoD derby.
But before we simply anoint Judy Faulkner the queen of American health IT, I want, as the Brits say, to throw a spanner in the works.
Commercial ≠ Proprietary
A careful review of the Hagel memo and other recent statements from his top lieutenants reveal a more progressive vision and clear requirements for an open architecture and service model.
From the Hagel memo:
I am convinced that a competitive process is the optimal way to ensure we select the best value solution for DoD … A competitive process will allow DoD to consider commercial alternatives that may offer reduced cost, reduced schedule and technical risk, and access to increased current capability and future growth in capability by leveraging ongoing advances in the commercial marketplace … Also, based on DoD’s market research, a VistA-based solution will likely be part of one or more competitive offerings that DoD receives.
To sum up, the secretary has directed the DoD to go commercial instead of developing and maintaining their own VistA-based solution, but commercialized VistA-based solutions will be included in the competitive process.
Dr. P patted the middle aged patient on the back, helped him off the elevated exam table and guided him to the chair by the sink. He picked up the chart and using the exam table as his desk he flipped through the chart, pulling out several pieces of paper, spreading them to his right, while making small talk with his patient. He reached into his pocket and pulled out a battered silver recorder and without any warning started dictating: “Mr. H is a 60 year old mildly obese gentleman presenting with…..“.
He had a pen now in his right hand, and as he was talking into his recorder, shuffling the various papers in front of him, he was also writing orders and prescriptions as fast as he was dictating. “….follow up in two weeks” was the last thing he said. He didn’t write that one down, but turned around, handed the patient a bunch of scripts, told him to stop by the front desk and make an appointment two weeks out and stop by the lab on the fourth floor to pick up a container for the urine test. Two minutes, tops, including the small talk. It was my turn now and I was sweating bullets because I knew exactly what he is about to say. “Can I do this in the EMR?”
EHR usability has finally arrived to Washington as the guest of honor at the most recent ONC HIT Policy Committee hearing. ONC seems to be considering the regulation and certification of EHR usability. NIST has created a testing procedure and just like its Meaningful Use testing procedures, it is superficial and doesn’t really test anything of any consequence. Those who represented “providers” and patients argued for the need to improve usability and those who represented academia and grant funded research argued for more funded research. Predictably, usability experts, argued for hiring more usability experts. Large vendors eloquently stated their objections to government mandating what EHRs should look like and small vendors argued that the more mandates, the better, since this will automatically remove the built-in competitive advantage of those with larger budgets and larger usability departments. As is customary, EHRs were compared to ATM machines, cars, iPhones, Google and a variety of “other industries” that are all so much more advanced than health care when it comes to usability.Continue reading…
No, you didn’t miss anything, there is no Government EHR. But should there be one? And if so, what should it look like?
The argument in favor of a Government EHR goes something like this: If we have 19 Billion dollars to spend on EHR adoption, why not spend a small fraction of that money and buy or build an EHR and make it freely available to all physicians and hospitals? Not a bad idea. I would add that, if we must, we could spend the rest of those billions on training and supporting physicians in their efforts to computerize their records. So how would a Government go about accomplishing such monumental task?Continue reading…