Doctors, let's be honest, usually run the show. Physicians who generate significant revenues are treated like royalty, especially at non-elite medical institutions. But, alas, that is not where the majority of medicine is practiced. For most acute-care organizations, it's about how much hospital leaders can do for the doctors, not to them.
At least in its current iteration, CPOE is something doctors largely feel is being done to them. Perhaps this is due to immature user interfaces, or amateurish methods of obtaining clinician buy-in. (Though well intentioned, I'm not sure if buying a doctor dinner constitutes advanced implementation methodology.)
For the latter, there are consultancies that claim to have perfected rollout.
To address the former, CIOs try switching vendor systems (the grass is always greener), upgrading with the same vendor (the devil you know) or implementing add-ons (Web-native applications that sit between physicians and core clinical systems). In all cases, the goal is identical - giving docs a Web-like CPOE experience, with IT tying everything together behind the scenes.
While KLAS confirms that the much-anticipated HITECH buying frenzy has yet to materialize (http://www.healthcare-informatics.com/adam_gale), many are investigating the upgrade path. One can imagine the discussions CIOs are having with their vendors:
“My doctors absolutely hate your CPOE.”
“How about upgrading to version X.2?”
“Is it any better?”
“But we just spent a few million for X.1 and wrote all the interfaces between it and our ancillaries.”
“Oh, yes. That's true.”
“And going to X.2 requires me to reconfigure my whole server environment.”
“Yes. I didn't think of that.”
“And I'd have to retrain all my clinicians, which they certainly won't like.”
“They sure can be ornery.”
“So what am I supposed to do?”
“Why not buy the docs dinner to convince them?”
If, at that dinner, the local cardio-thoracic superstar surgeon (CTSS) repeats that he “didn't go through 10-plus years of education to do data entry,” what will you do? What will your organization do? Will you banish his millions to the hospital across town which might be far more sympathetic to his position?
Perhaps that facility is playing the HITECH game more adroitly. You see, the initial definition of meaningful use only requires that hospitals have 10 percent of their orders going in through CPOE by 2011. Will slick hospitals get to that 10 percent on the backs of their junior (lower revenue generating) docs, while leaving Mr. CTSS alone as long as they can? Will crafty hospital administrators lure Mr. CTSS to the “more understanding” environment of their facility?
“Of course we don't expect you to do data entry. You'll find a home here.”
The games will get even more interesting next year, when CMS informs the industry exactly how hospitals are to prove their compliance with HITECH's meaningful use and certification requirements. Will it be a simple attestation signed by the CIO, CEO and CFO? Will there be some inspection process for everyone or will reporting be like filing taxes, done on the honor system with the threat of audits as a looming stick?
Whatever is ultimately decided, there will be wiggle room in both achieving compliance with the objectives (getting to 10 percent) and in the reporting (we're at 9 percent, they'll never audit us). As usual, the uber-scrupulous may suffer for their veracity, while those with a more flexible interpretation of reality could find that approach yielding fatter margins.
It's incumbent upon HHS, CMS and ONCHIT to scenario-play their meaningful use certification requirements all the way down the line to find the wiggle room some will exploit. With special interest prodding (see HIMSS), the government has started the EMR/CPOE ball rolling, so it has an obligation to ensure the honest aren't left in fiscal disarray.
With so much money on the line, someone is going to figure out how to make Mr. CTSS happy. When it's time to talk to him about CPOE, tread lightly, or someone else will.
Anthony Guerra, Editor-in-Chief