<?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: MD Leader 1/27/09</title>
	<atom:link href="http://histalk2.com/2009/01/26/md-leader-12709/feed/" rel="self" type="application/rss+xml" />
	<link>http://histalk2.com/2009/01/26/md-leader-12709/</link>
	<description>Healthcare IT News and Opinion</description>
	<lastBuildDate>Thu, 09 Feb 2012 01:56:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Martin Coyne</title>
		<link>http://histalk2.com/2009/01/26/md-leader-12709/comment-page-1/#comment-3253</link>
		<dc:creator>Martin Coyne</dc:creator>
		<pubDate>Tue, 03 Feb 2009 16:17:37 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/26/md-leader-12709/#comment-3253</guid>
		<description>I totally agree.  And I totally disagree.  First, I do agree with the point that a tool does not by itself make things better.  That tool must become part of a bigger workflow and process to leverage its capabilities.  Many, it seems, think that procuring (or developing) a solution will fix everything.  If leadership doesn&#039;t drive process improvements - it won&#039;t.
Now, at this point in time, even the big boys like Microsoft are struggling to keep up in sw development despite having deep pockets and tons of very talented resources. Can a user really develop a best in class solution. Let&#039;s pretend they have the skills.  I cannot imagine they don&#039;t have a better use of their internal resources.
Lots of issues here.  Willingness to change the process? SaaS? Customization?  Local Integrators?  Cost and funding source?  Who derives the value?  All possible reasons for low EMR adoption rates.</description>
		<content:encoded><![CDATA[<p>I totally agree.  And I totally disagree.  First, I do agree with the point that a tool does not by itself make things better.  That tool must become part of a bigger workflow and process to leverage its capabilities.  Many, it seems, think that procuring (or developing) a solution will fix everything.  If leadership doesn&#8217;t drive process improvements &#8211; it won&#8217;t.<br />
Now, at this point in time, even the big boys like Microsoft are struggling to keep up in sw development despite having deep pockets and tons of very talented resources. Can a user really develop a best in class solution. Let&#8217;s pretend they have the skills.  I cannot imagine they don&#8217;t have a better use of their internal resources.<br />
Lots of issues here.  Willingness to change the process? SaaS? Customization?  Local Integrators?  Cost and funding source?  Who derives the value?  All possible reasons for low EMR adoption rates.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art_Vandelay</title>
		<link>http://histalk2.com/2009/01/26/md-leader-12709/comment-page-1/#comment-3204</link>
		<dc:creator>Art_Vandelay</dc:creator>
		<pubDate>Thu, 29 Jan 2009 01:14:03 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/26/md-leader-12709/#comment-3204</guid>
		<description>If what some physicians want was in existence, a number of those who have built their solution likely would not have made that choice.</description>
		<content:encoded><![CDATA[<p>If what some physicians want was in existence, a number of those who have built their solution likely would not have made that choice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Weider</title>
		<link>http://histalk2.com/2009/01/26/md-leader-12709/comment-page-1/#comment-3198</link>
		<dc:creator>Will Weider</dc:creator>
		<pubDate>Wed, 28 Jan 2009 20:53:25 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/26/md-leader-12709/#comment-3198</guid>
		<description>I don&#039;t think Pete is advocating internal development.  He is stating that we did not think that would be where we ended.  We need to guard against these pre-conceived notions.  We miss a lot of opportunities because of cliches that we rattle off as if they were laws of physics....you never get fired for buying IBM...Integrated solutions are always better than best of breed...there is no room for open source in the enterprise...most of our patients wouldn&#039;t go online...blah, blah, blah.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think Pete is advocating internal development.  He is stating that we did not think that would be where we ended.  We need to guard against these pre-conceived notions.  We miss a lot of opportunities because of cliches that we rattle off as if they were laws of physics&#8230;.you never get fired for buying IBM&#8230;Integrated solutions are always better than best of breed&#8230;there is no room for open source in the enterprise&#8230;most of our patients wouldn&#8217;t go online&#8230;blah, blah, blah.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Weider</title>
		<link>http://histalk2.com/2009/01/26/md-leader-12709/comment-page-1/#comment-3197</link>
		<dc:creator>Will Weider</dc:creator>
		<pubDate>Wed, 28 Jan 2009 20:43:29 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/26/md-leader-12709/#comment-3197</guid>
		<description>Dr. Sanderson&#039;s point was the EHR alone cannot achieve the desired results.  There needs to be a lot of work around leveraging the technology.  Do people disagree with that?  Are people unaware of the numerous spectacular failures in healthcare IT?</description>
		<content:encoded><![CDATA[<p>Dr. Sanderson&#8217;s point was the EHR alone cannot achieve the desired results.  There needs to be a lot of work around leveraging the technology.  Do people disagree with that?  Are people unaware of the numerous spectacular failures in healthcare IT?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evan Steele, CEO, SRSsoft</title>
		<link>http://histalk2.com/2009/01/26/md-leader-12709/comment-page-1/#comment-3173</link>
		<dc:creator>Evan Steele, CEO, SRSsoft</dc:creator>
		<pubDate>Tue, 27 Jan 2009 22:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2009/01/26/md-leader-12709/#comment-3173</guid>
		<description>Dr. Sanderson drives the case for being both the developer and vendor of an EMR product, as well as the user. Is this a practical way to go? I&#039;m sure the substantial resources consumed in developing, testing and quality assuring the product have focused on his clinic&#039;s preferences. As all of us who have spent a lifetime providing services and products to the medical community know, each practice is unique in its way of doing business, right down to templates and workflows. EMR&#039;s by their nature have to be flexible and adaptable to accommodate this; but that configurability is what makes them more difficult to use &quot;out of the box.&quot; There are tradeoffs at every turn--easy to configure or more rigid in design? Either way, practices must change the way the doctor-patient encounter has traditionally taken place.   
  
With traditional EMR&#039;s, that often means putting a technology device between the patient and the doctor, ergo the slowdown and loss of productivity that has so marred the EMR experience up to this point. In many ways, this explains why EMR adoption continues to be very low. That&#039;s why hybrid EMR is rapidly gaining traction, especially in higher volume, multi-doctor practices and clinics. The trade-offs are much easier and do not hamper the patient-doctor encounter or slow it down.  
   
Practices should not have to develop their own products. That takes time, capital and resources which are then not available for providing better patient care. If traditional EMR worked like PHYSICIANS wanted them to, there would be no need for what Dr. Sanderson has tried to do. We need our physicians to keep spending quality time with us and giving us great care. Hopefully tools like hybrid EMR will allow them to do that without having to spend so much on building their own tools.</description>
		<content:encoded><![CDATA[<p>Dr. Sanderson drives the case for being both the developer and vendor of an EMR product, as well as the user. Is this a practical way to go? I&#8217;m sure the substantial resources consumed in developing, testing and quality assuring the product have focused on his clinic&#8217;s preferences. As all of us who have spent a lifetime providing services and products to the medical community know, each practice is unique in its way of doing business, right down to templates and workflows. EMR&#8217;s by their nature have to be flexible and adaptable to accommodate this; but that configurability is what makes them more difficult to use &#8220;out of the box.&#8221; There are tradeoffs at every turn&#8211;easy to configure or more rigid in design? Either way, practices must change the way the doctor-patient encounter has traditionally taken place.   </p>
<p>With traditional EMR&#8217;s, that often means putting a technology device between the patient and the doctor, ergo the slowdown and loss of productivity that has so marred the EMR experience up to this point. In many ways, this explains why EMR adoption continues to be very low. That&#8217;s why hybrid EMR is rapidly gaining traction, especially in higher volume, multi-doctor practices and clinics. The trade-offs are much easier and do not hamper the patient-doctor encounter or slow it down.  </p>
<p>Practices should not have to develop their own products. That takes time, capital and resources which are then not available for providing better patient care. If traditional EMR worked like PHYSICIANS wanted them to, there would be no need for what Dr. Sanderson has tried to do. We need our physicians to keep spending quality time with us and giving us great care. Hopefully tools like hybrid EMR will allow them to do that without having to spend so much on building their own tools.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

