Skip to content Skip to navigation

Opening Up Certification to Competitors

May 21, 2009
by David Raths
| Reprints

Nothing in the current debate over how to proceed on widespread EHR implementation seems to generate as much heat as the issue of certification.
If you do a Google search on the term CCHIT, you very quickly come across articles and blog posts by people who adamantly believe certifying EHR products is wrong-headed or that one organization is being given too much power. Some argue that certification should be focused at the provider level, not the vendor level. Organizations with open source variations or home-grown clinical information systems or ones cobbled together from multiple vendors wonder how they will be assessed.
Others criticize CCHIT’s relationship with HIMSS (HIMSS was one of its co-founders and provided seed money, although CCHIT is now an independent entity). Still others say that it favors large vendors, who can create soup-to-nuts offerings, over smaller software companies and entrepreneurs.
One of our own bloggers, Holzer Clinic CIO Mark Harvey, argues that because general adoption rates are still far too low, setting the certification bar high initially is a mistake. “Help us digitize first,” Harvey wrote recently. “More sophisticated functionality will follow naturally.”
I have interviewed CCHIT Chair Dr. Mark Leavitt on several occasions and he usually makes the case that the organization is evolving to meet the needs of the industry and points to the number of small vendors that have achieved certification.
I like the suggestion of a recent Markle Foundation report that responsibility for certification shouldn’t reside with a single organization. The Markle report makes the case for letting a government entity such as NIST (National Institute of Standards and Technology) set the core criteria for certification of meaningful-use functionality, and then allowing multiple entities, both public and private, to do the actual certification testing.
“So long as these testing services all work on the same definition, these entities can then compete on their ability to provide value-added services above the minimum requirements,” the report continues. “Once the certification protocols are defined, the door should be left open to a plurality of private certification organizations, including ones like CCHIT, to compete for public and private sector business, as there are now for other IT products and services.”
While it wouldn’t address all the criticisms of CCHIT, opening up the process of certification to multiple organizations sounds reasonable to me. It might ease the fears of a monolithic, bureaucratic organization with too much power. I would be interested to hear what others think.
The Markle report goes on to point out that there also must be a validation mechanism. Certification only checks that a system has the capability to help an organization achieve the meaningful-use objectives. HHS must now develop mechanisms to determine whether organizations are using it in that fashion. Making sure those reporting schemes and attestations are not a huge burden on clinicians and CIOs will be a huge challenge.





Topics

Comments

I feel the discussion should not be who does the testing but more about every one that does follow set criteria (use cases) so that we are comparing apples with apples.

Additionally, the certification should also allow home grown solutions to be tested at a reasonable cost.

Dave,
Thanks for your post. The Markle approach to certification sounds like the automotive emissions testing system, which I believe works well.

In response to one of your earlier posts, I wrote "Big decisions - Certification and Evaluation?" ( http://tinyurl.com/phxdkd )

The bottom line is that, like certification, there is mature prior work available when it comes to evaluation. Classen and team at CSC showed the evaluation is vital. It also suggests, as David Blumenthal has publicly commented, that the usability of some modern CDS is a big problem.

David Raths

Contributing Editor

David Raths

@DavidRaths

www.linkedin.com/in/davidraths

David Raths’ blog focuses on health IT policy issues ranging from patient privacy to health...