Friday, 8 March 2013

Twitter EHR "revolt": #EHRbacklash

Twitter EHR "revolt": #EHRbacklash - Hi, friend befluster.me, in this article entitled Twitter EHR "revolt": #EHRbacklash, we have prepared this article well and concise to be easy to understand for you to read and can be taken inside information. hopefully the contents of the post Article #EHRbacklash, Article healthcare IT difficulties, Article IEEE, Article Twitter, that we write this you can understand and useful. okay, happy reading.

As noted at the new IEEE Spectrum piece "U. S. Electronic Health Record Initiative: A Backlash Growing?"  (worth reading in its entirety along with its hyperlinks), the following is noted:

There seems to be a slow but steady backlash growing among healthcare providers against the U.S. government’s $30 billion initiative to get all its citizens an electronic health record, initially set to happen by 2014 but now looking at 2020 or beyond. The backlash isn’t so much about the need for, or eventual benefits of, electronic health records but more about the perceived (and real) difficulties caused by the government's incentive program and a growing realization of the actual financial and operational costs involved in rolling out, using, and paying for EHR systems.

The first hyperlink (on the word "backlash") is to a Twitter "revolt" marked by tweets using the hash tag (index tag) "#EHRbacklash." 

I did not start the use of this tag, although have started "tweeting" using it.

The link to tweets made with the tag is:  https://twitter.com/search?q=%23EHRbacklash&src=hash

This is certainly a "first", and should be an industry and pundit wake-up call.

-- SS

Addendum:  easier to follow at this link:  http://tweetchat.com/room/EHRbacklash



Thank You and Good article Twitter EHR "revolt": #EHRbacklash this time, hopefully can benefit for you all. see you in other article postings.

You are now reading the articleTwitter EHR "revolt": #EHRbacklash with the link address http://www.befluster.me/2013/03/twitter-ehr-ehrbacklash.html

0 comments

Post a Comment