Free EMR Newsletter Want to receive the latest news on EMR, Meaningful Use, ARRA and Healthcare IT sent straight to your email? Join thousands of healthcare pros who subscribe to EMR and EHR for FREE!

EHR Code of Conduct – Siemens Healthcare

Posted on June 25, 2013 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

Here at EMR Thoughts we’re going to do our best to keep track of which EHR vendors and other healthcare IT companies choose to adopt the EHR Code of Conduct. Hopefully by doing so we can offer at least one small part in helping to hold EHR vendors accountable for the code.

Today, Siemens Healthcare Adopted the EHR Developer Code of Conduct. Siemens was a major part of the effort to create the EHR code of conduct, so this doesn’t come as a surprise. Unfortunately, the press release didn’t have any details or a link to a website or anything to show how they’ve actually implemented the EHR code of conduct.

If you’re someone who uses a Siemens Healthcare product, I’d love to see if you think that they’re following the EHR Code of Conduct or if they still have room to improve. Hopefully we can get more exposure for those EHR vendors that really implement the spirit of the EHR Code of Conduct and expose those who do so only with their lips.

EMR Vendors Want Meaningful Use Stage 3 Delay

Posted on January 29, 2013 I Written By

Anne Zieger is veteran healthcare consultant and analyst with 20 years of industry experience. Zieger formerly served as editor-in-chief of FierceHealthcare.com and her commentaries have appeared in dozens of international business publications, including Forbes, Business Week and Information Week. She has also contributed content to hundreds of healthcare and health IT organizations, including several Fortune 500 companies. Contact her at @ziegerhealth on Twitter or visit her site at Zieger Healthcare.

A group of EMR vendors have joined the chorus of industry organizations asking that Meaningful Use Stage 3 deadlines be moved up to a later date.  The vendors also want to see the nature of Stage 3 requirements changed to put a greater emphasis on interoperabilityInformation Week reports.

The group, the HIMSS EHR Association (EHRA), represents 40 vendors pulled together by HIMSS.  Members include both enterprise and physician-oriented vendors, including athenahealth, Cerner, Epic, eClinicalWorks, Emdeon, Meditech, McKesson, Siemens GE Healthcare IT and Practice Fusion.

In comments submitted to HHS, the vendors argue that MU Stage 3 requirements should not kick in until three years after a provider reaches Stage 2, and start no earlier than 2017. But their larger request, and more significant one, is that they’d like to see Meaningful Use Stage 3’s focus changed:

“The EHRA strongly recommends that Stage 3 focus primarily on encouraging and assisting providers to take advantage of the substantial capabilities established in Stage 1 and especially Stage 2, rather than adding new meaningful use requirements and product certification criteria. In particular, we believe that any meaningful use and functionality changes should focus primarily on interoperability and building on accelerated momentum and more extensive use of Stage 2 capabilities and clinical quality measurement.”

So, we’ve finally got vendors like walled-garden-player Epic finding a reason to fight for interoperability. It took being clubbed by the development requirements of Stage 3, which seems to have EHRA members worried, but it happened nonetheless.

While there’s obviously self-interest in vendors asking not to strain their resources on new development, they still have a point which deserves considering.  Does it really make sense to push the development curve as far as Stage 3 requires before providers have gotten the chance to leverage what they’ve got?  Maybe not.

Now, the question is whether the vendors will put their code where their mouth is. Will the highly proprietary approach taken by Epic and some of its peers become passe?