<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Get Ready for EHR Failures, But Don&#8217;t Blame the Software</title>
	<atom:link href="http://www.softwareadvice.com/articles/medical/get-ready-for-ehr-failures-but-dont-blame-the-software-2031209/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.softwareadvice.com/articles/medical/get-ready-for-ehr-failures-but-dont-blame-the-software-2031209/</link>
	<description>Software Advice Articles, News &#38; Best Practices Guides</description>
	<lastBuildDate>Fri, 12 Mar 2010 16:40:21 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The Medical Quack: Software Upgrade could cost Chicago 4 Clinics &#8211; Software Issues with bills not being submitted reflects an adjusted budget</title>
		<link>http://www.softwareadvice.com/articles/medical/get-ready-for-ehr-failures-but-dont-blame-the-software-2031209/comment-page-1/#comment-281</link>
		<dc:creator>The Medical Quack: Software Upgrade could cost Chicago 4 Clinics &#8211; Software Issues with bills not being submitted reflects an adjusted budget</dc:creator>
		<pubDate>Thu, 09 Apr 2009 18:56:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwareadvice.com/articles/?p=597#comment-281</guid>
		<description>[...] Get Ready for EHR Failures, But Don&#8217;t Blame the Software [...]</description>
		<content:encoded><![CDATA[<p>[...] Get Ready for EHR Failures, But Don&#8217;t Blame the Software [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don&#8217;t blame the software for EHR failure &#171; WhiteCoat&#8217;s Call Room</title>
		<link>http://www.softwareadvice.com/articles/medical/get-ready-for-ehr-failures-but-dont-blame-the-software-2031209/comment-page-1/#comment-275</link>
		<dc:creator>Don&#8217;t blame the software for EHR failure &#171; WhiteCoat&#8217;s Call Room</dc:creator>
		<pubDate>Sat, 04 Apr 2009 12:12:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwareadvice.com/articles/?p=597#comment-275</guid>
		<description>[...] Software Advice, a website that offers reviews of electronic medical records, suggests that “free” EHR software will result in a lot of failed implementations over the next few years. They’re concerned that the subsidies won’t change healthcare providers’ late adopter mindsets about information technology. They have outlined their thoughts on why IT projects fail and how providers can avoid that fate while capitalizing on the subsidy: “Get Ready for EHR Failures, But Don’t Blame the Software.” [...]</description>
		<content:encoded><![CDATA[<p>[...] Software Advice, a website that offers reviews of electronic medical records, suggests that “free” EHR software will result in a lot of failed implementations over the next few years. They’re concerned that the subsidies won’t change healthcare providers’ late adopter mindsets about information technology. They have outlined their thoughts on why IT projects fail and how providers can avoid that fate while capitalizing on the subsidy: “Get Ready for EHR Failures, But Don’t Blame the Software.” [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Yellowlees</title>
		<link>http://www.softwareadvice.com/articles/medical/get-ready-for-ehr-failures-but-dont-blame-the-software-2031209/comment-page-1/#comment-258</link>
		<dc:creator>Peter Yellowlees</dc:creator>
		<pubDate>Mon, 30 Mar 2009 21:59:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwareadvice.com/articles/?p=597#comment-258</guid>
		<description>I agree with your list, but think that the issue of being prepared to practice differently should be at the top. We all know that healthcare is a very inefficient provider focussed industry, and when moving to implement any major type of application it is crucial to re-engineer the work process before choosing the application - there is no point in trying to put in an electronic application to solve a business process problem - the end result will be worse.</description>
		<content:encoded><![CDATA[<p>I agree with your list, but think that the issue of being prepared to practice differently should be at the top. We all know that healthcare is a very inefficient provider focussed industry, and when moving to implement any major type of application it is crucial to re-engineer the work process before choosing the application &#8211; there is no point in trying to put in an electronic application to solve a business process problem &#8211; the end result will be worse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: InterOpNurse &#187; Blog Archive &#187; Article by Software Advice</title>
		<link>http://www.softwareadvice.com/articles/medical/get-ready-for-ehr-failures-but-dont-blame-the-software-2031209/comment-page-1/#comment-232</link>
		<dc:creator>InterOpNurse &#187; Blog Archive &#187; Article by Software Advice</dc:creator>
		<pubDate>Fri, 20 Mar 2009 08:09:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwareadvice.com/articles/?p=597#comment-232</guid>
		<description>[...] the article, &#8220;Get Ready for EHR Failures, But Don&#8217;t Blame the Software&#8221; we present 5 critical steps for a smooth, successful EMR implementation. If you follow these [...]</description>
		<content:encoded><![CDATA[<p>[...] the article, &ldquo;Get Ready for EHR Failures, But Don&rsquo;t Blame the Software&rdquo; we present 5 critical steps for a smooth, successful EMR implementation. If you follow these [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EHR Technology Implementation Failure Issues : MyDocHub Blog - Online Health Community</title>
		<link>http://www.softwareadvice.com/articles/medical/get-ready-for-ehr-failures-but-dont-blame-the-software-2031209/comment-page-1/#comment-217</link>
		<dc:creator>EHR Technology Implementation Failure Issues : MyDocHub Blog - Online Health Community</dc:creator>
		<pubDate>Sat, 14 Mar 2009 16:17:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwareadvice.com/articles/?p=597#comment-217</guid>
		<description>[...] (EHR) part of the Stimulus Bill, and the failures it may face. The company Software Advice says, if EHR implementation fails, don’t blame the software. What do you think? Read the full blog post [...]</description>
		<content:encoded><![CDATA[<p>[...] (EHR) part of the Stimulus Bill, and the failures it may face. The company Software Advice says, if EHR implementation fails, don’t blame the software. What do you think? Read the full blog post [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ignacio Valdes, MD, MS</title>
		<link>http://www.softwareadvice.com/articles/medical/get-ready-for-ehr-failures-but-dont-blame-the-software-2031209/comment-page-1/#comment-208</link>
		<dc:creator>Ignacio Valdes, MD, MS</dc:creator>
		<pubDate>Thu, 12 Mar 2009 23:07:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwareadvice.com/articles/?p=597#comment-208</guid>
		<description>This is from another conversation I wrote but I think it fits here:

Years from now I hope that people will laugh at these debates in the same way that today we think the alchemists where misguided. I hope
that laugh will happen in just a few years, and not 20. Do you remember the Steve Martin &#039;Medieval Barber&#039; skits in which he does blood letting on customers then starts talking into the camera, lays out the discovery of the scientific method then grins into the camera and says &#039;naaaah!&#039; and continues doing dreadful things?  That&#039;s what seems to be going on here a kind of &#039;Medieval Barber&#039; type thing that is occurring with many people in thinking about Health IT. That this proprietary vs. Free/Open Source licensing is even debated just seems so odd to me.

Mandating seat belt use for cars isn&#039;t a good thing because &#039;one size does not fit all&#039; and people should be allowed to be &#039;thrown clear&#039; in a crash. You know that lead paint is pretty good for some applications and it is just too bad if it poisons children and the environment
around it. Banning lead paint and faulty medications is not a good solution because it works for some people and &#039;one size does not fit all&#039;.  Freedom of speech should be you know optional because &#039;one size does not fit all&#039;, the scientific method for finding truth is really superfluous because &#039;one size does not fit all&#039;. Proprietary EMR&#039;s should be allowed to be paid for with federal funds because &#039;one size does not fit all&#039; even though there is manifest evidence over at least
a decade that they do not work very well in practice for most of medicine and there is a good deal of evidence over decades that
Free/Open Source ones do.

How is it possible that the VA computerized themselves very effectively as far as anyone can tell without proprietary EMR&#039;s and proprietary EMR vendors? That a large reason for their success is that they made a conscious decision long ago to do something that pre-dates Free/Open Source and looks very much like Free/Open Source? Or is this yet another instance of &#039;one size does not fit all&#039;? For the VA, one size very much does fit all as long as software freedom is safeguarded in both the hospitals and clinics with demonstrable superiority.

I&#039;ll repeat that it isn&#039;t what you see with proprietary EMR systems, it is what you do not see: rapid innovation, choice, actual scientific comparison, real privacy, security, derivative works, the right to fix and extend the software, low or no cost, good service, real progress in medicine. What you do not see with Wal-Mart and eClinical is the poisoning of the health IT software ecosystem and the stifling of innovation and derivative works while we collectively go &#039;Look over there! Something shiny!&#039;

Overall, the private sector Health Information Technology seems to drink the same polluted proprietary water over and over again and
wonders why it is sick. Does anyone wonder why it is necessary for a $19 billion hammer to mash that proprietary square peg into the round
hole? Could it be that one size fits all rights to run, copy, distribute, study, change and improve the software are really essential just like the scientific method, and public safeguards banning harmful things like lead paint and mandating seat belts?

-- IV</description>
		<content:encoded><![CDATA[<p>This is from another conversation I wrote but I think it fits here:</p>
<p>Years from now I hope that people will laugh at these debates in the same way that today we think the alchemists where misguided. I hope<br />
that laugh will happen in just a few years, and not 20. Do you remember the Steve Martin &#8216;Medieval Barber&#8217; skits in which he does blood letting on customers then starts talking into the camera, lays out the discovery of the scientific method then grins into the camera and says &#8216;naaaah!&#8217; and continues doing dreadful things?  That&#8217;s what seems to be going on here a kind of &#8216;Medieval Barber&#8217; type thing that is occurring with many people in thinking about Health IT. That this proprietary vs. Free/Open Source licensing is even debated just seems so odd to me.</p>
<p>Mandating seat belt use for cars isn&#8217;t a good thing because &#8216;one size does not fit all&#8217; and people should be allowed to be &#8216;thrown clear&#8217; in a crash. You know that lead paint is pretty good for some applications and it is just too bad if it poisons children and the environment<br />
around it. Banning lead paint and faulty medications is not a good solution because it works for some people and &#8216;one size does not fit all&#8217;.  Freedom of speech should be you know optional because &#8216;one size does not fit all&#8217;, the scientific method for finding truth is really superfluous because &#8216;one size does not fit all&#8217;. Proprietary EMR&#8217;s should be allowed to be paid for with federal funds because &#8216;one size does not fit all&#8217; even though there is manifest evidence over at least<br />
a decade that they do not work very well in practice for most of medicine and there is a good deal of evidence over decades that<br />
Free/Open Source ones do.</p>
<p>How is it possible that the VA computerized themselves very effectively as far as anyone can tell without proprietary EMR&#8217;s and proprietary EMR vendors? That a large reason for their success is that they made a conscious decision long ago to do something that pre-dates Free/Open Source and looks very much like Free/Open Source? Or is this yet another instance of &#8216;one size does not fit all&#8217;? For the VA, one size very much does fit all as long as software freedom is safeguarded in both the hospitals and clinics with demonstrable superiority.</p>
<p>I&#8217;ll repeat that it isn&#8217;t what you see with proprietary EMR systems, it is what you do not see: rapid innovation, choice, actual scientific comparison, real privacy, security, derivative works, the right to fix and extend the software, low or no cost, good service, real progress in medicine. What you do not see with Wal-Mart and eClinical is the poisoning of the health IT software ecosystem and the stifling of innovation and derivative works while we collectively go &#8216;Look over there! Something shiny!&#8217;</p>
<p>Overall, the private sector Health Information Technology seems to drink the same polluted proprietary water over and over again and<br />
wonders why it is sick. Does anyone wonder why it is necessary for a $19 billion hammer to mash that proprietary square peg into the round<br />
hole? Could it be that one size fits all rights to run, copy, distribute, study, change and improve the software are really essential just like the scientific method, and public safeguards banning harmful things like lead paint and mandating seat belts?</p>
<p>&#8211; IV</p>
]]></content:encoded>
	</item>
</channel>
</rss>
