CCHIT, what's that smell?
First, I work for an Open Source start-up EHR "vendor" (we don't use that term). Second, I am a fan of standards where it makes sense. A standard is the coin of the realm in the Open Source community. So, the efforts of organizations like CCHIT to certify standards in HIT products is a great idea. I'm wondering if the good idea of CCHIT has been soured by the influence of large, established vendors with perhaps a tad of self-interest. There are those who think so when the "standard" dictates adherence to criteria that read like feature function lists in a product brochure. Innovators, start-up, and specialty IT services providers are concerned about being locked out by onerous, proprietary requirements imposed by CCHIT. That said, the following is particularly disturbing.
From HISTalk News: http://histalk2.com/
"Herb Conaway, Jr., a private practice physician, attorney, and Democratic assemblyman from New Jersey, introduces a bill that would make it illegal to sell or use non-CCHIT certified systems in the state. He previously introduced the New Jersey Health Information Technology Promotion Act that appears to mandate EMR use. HIMSS loves him, of course, having given him a 2008 State Advocacy Award and put him on the podium at the annual conference in Chicago. I found it interesting that his own practice’s EMR vendor went belly-up, maybe leading him to favor the larger vendors that can afford CCHIT certification fees and who wouldn’t mind seeing a bunch of competitors knocked out of the arena for one reason or another. "
"Sensible Certification http://www.sensiblecertification.com/ , on the other hand, is trying to rally support to scale back grand certification ideas. I was skeptical until I read its six suggestions, of which I agree with every one: (1) stop the rush to certification; (2) don’t define requirements until ‘meaningful use’ is defined; (3) certify only basic capabilities, such as data sharing; (4) use NIST’s Laika http://laika.sourceforge.net/ as the certification requirement; (5) don’t certify functionality because the market should decide that; and (6) certification CCHIT-style will stifle innovation. They’re petitioning David Blumenthal at ONCHIT."

General comments
Terry,
Do you feel the certification process will cost more money than an open-source based product or company would be unwilling to pay? My thoughts in general are that certification should cover basic functionality. The end user (hospital, etc) needs to know the product they are buying has met some minimum standards. This is the main problem in the healthcare industry. We have standards of care to treat patients, now we need standards for the supporting systems. Mind you I am not advocating 1000 pages of criteria that need to be met, but some general concepts.