<?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 for EMR Straight Talk</title>
	<atom:link href="http://blog.srssoft.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.srssoft.com</link>
	<description>From Evan Steele, CEO SRSsoft</description>
	<lastBuildDate>Wed, 15 May 2013 18:18:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>Comment on Physicians Spooked by Failure Stories—EHR Adoption Suffers by EHR Market Analyst</title>
		<link>http://blog.srssoft.com/2013/05/physicians-spooked-by-failure-stories-ehr-adoption-suffers/comment-page-1/#comment-17340</link>
		<dc:creator>EHR Market Analyst</dc:creator>
		<pubDate>Wed, 15 May 2013 18:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.srssoft.com/?p=2327#comment-17340</guid>
		<description>There&#039;s a missing piece here as well - the culture of providers - a culture that stresses autonomy and medicine as an art over regulation and medicine as a commodity.  Technology is seen as a third-wheel in the patient/provider relationships, and any inclination that it has affects on clinical decision making is sure to deter providers.  Most physicians (particularly small practice ones) see the MU requirements as excessive and inappropriate, and protest government regulation of their industry.  Much of the dissatisfaction can be found with the policies forcing EHR adoption as much as the EHRs themselves.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a missing piece here as well &#8211; the culture of providers &#8211; a culture that stresses autonomy and medicine as an art over regulation and medicine as a commodity.  Technology is seen as a third-wheel in the patient/provider relationships, and any inclination that it has affects on clinical decision making is sure to deter providers.  Most physicians (particularly small practice ones) see the MU requirements as excessive and inappropriate, and protest government regulation of their industry.  Much of the dissatisfaction can be found with the policies forcing EHR adoption as much as the EHRs themselves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Physicians Spooked by Failure Stories—EHR Adoption Suffers by Susan D Thomas Parrott</title>
		<link>http://blog.srssoft.com/2013/05/physicians-spooked-by-failure-stories-ehr-adoption-suffers/comment-page-1/#comment-17331</link>
		<dc:creator>Susan D Thomas Parrott</dc:creator>
		<pubDate>Mon, 13 May 2013 17:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.srssoft.com/?p=2327#comment-17331</guid>
		<description>I see the good &amp; the bad of EHR.  The good is having a patient&#039;s full medical history available ASAP, creating little or no delay in treatment of a patient&#039;s condition(s), particularly those that are sudden &amp;/or serious.  The secure access and exchange of information can only benefit everyone involved.  The bad is in inproper training of individuals handling records, which is probably more applicable to the &quot;infancy&quot; period, and the possibility of down-time on any EHR system, which I feel we have had more than our fair share of for whatever reason.  I feel that this will all improve over time &amp; anyone not currently involved will eventually be left behind since everyone else will have this method of communication and information exchange.</description>
		<content:encoded><![CDATA[<p>I see the good &amp; the bad of EHR.  The good is having a patient&#8217;s full medical history available ASAP, creating little or no delay in treatment of a patient&#8217;s condition(s), particularly those that are sudden &amp;/or serious.  The secure access and exchange of information can only benefit everyone involved.  The bad is in inproper training of individuals handling records, which is probably more applicable to the &#8220;infancy&#8221; period, and the possibility of down-time on any EHR system, which I feel we have had more than our fair share of for whatever reason.  I feel that this will all improve over time &amp; anyone not currently involved will eventually be left behind since everyone else will have this method of communication and information exchange.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Physicians Spooked by Failure Stories—EHR Adoption Suffers by Andrew McAdams</title>
		<link>http://blog.srssoft.com/2013/05/physicians-spooked-by-failure-stories-ehr-adoption-suffers/comment-page-1/#comment-17329</link>
		<dc:creator>Andrew McAdams</dc:creator>
		<pubDate>Mon, 13 May 2013 13:12:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.srssoft.com/?p=2327#comment-17329</guid>
		<description>I&#039;m going to say that a key here with physician dissatisfaction with an EMR is primarily one of setting appropriate expectations.  I was a consultant for several years, and during that time analyzed workflows from hundreds of different physician offices all over the country.  Amongst all of them, there is surprisingly little that&#039;s the same.  What that does is present EMR devs with a bear of a task to write software that actually fills the workflow needs of physicians with wildly different workflows.  It&#039;s not easy.  

I think a key piece that&#039;s often left out of discussions on EMR adoption is that an EMR - ANY EMR will fundamentally change the way your practice works.  Many physicians approach an EMR implementation with the assumption that software can immediately imitate their workflows with no issue whatsoever.  I think more physicians would be satisfied with their current EMRs if they had realistic expectations of what installing an EMR means for them as an organization, and the kinds of organization changes that an EMR will bring with it.  

If you couple that with the sales people who no doubt &#039;fudge&#039; the facts, promise things without checking with their developers to see if its possible resulting in things being promised to physicians that were never possible to begin with -- and you&#039;ve got a lot of dissatisfied people.  On every install I worked on, I said time and time again that communication from the CIO all the way down to the part time scheduler is imperative to have a successful implementation.</description>
		<content:encoded><![CDATA[<p>I&#8217;m going to say that a key here with physician dissatisfaction with an EMR is primarily one of setting appropriate expectations.  I was a consultant for several years, and during that time analyzed workflows from hundreds of different physician offices all over the country.  Amongst all of them, there is surprisingly little that&#8217;s the same.  What that does is present EMR devs with a bear of a task to write software that actually fills the workflow needs of physicians with wildly different workflows.  It&#8217;s not easy.  </p>
<p>I think a key piece that&#8217;s often left out of discussions on EMR adoption is that an EMR &#8211; ANY EMR will fundamentally change the way your practice works.  Many physicians approach an EMR implementation with the assumption that software can immediately imitate their workflows with no issue whatsoever.  I think more physicians would be satisfied with their current EMRs if they had realistic expectations of what installing an EMR means for them as an organization, and the kinds of organization changes that an EMR will bring with it.  </p>
<p>If you couple that with the sales people who no doubt &#8216;fudge&#8217; the facts, promise things without checking with their developers to see if its possible resulting in things being promised to physicians that were never possible to begin with &#8212; and you&#8217;ve got a lot of dissatisfied people.  On every install I worked on, I said time and time again that communication from the CIO all the way down to the part time scheduler is imperative to have a successful implementation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Physicians Spooked by Failure Stories—EHR Adoption Suffers by Dr. Siegel, Peds Ophthal.</title>
		<link>http://blog.srssoft.com/2013/05/physicians-spooked-by-failure-stories-ehr-adoption-suffers/comment-page-1/#comment-17323</link>
		<dc:creator>Dr. Siegel, Peds Ophthal.</dc:creator>
		<pubDate>Sun, 12 May 2013 01:29:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.srssoft.com/?p=2327#comment-17323</guid>
		<description>Promises, promises, all the things the EMR was supposed to do, all the support that disappeared once the product was bought.  We have many &quot;EMR compatible machines (visual fields, ocular pressures...) &quot; none easily communicate with the EMR which touted being able to support inputing the information.... yes they will support it, if you pay not only the EMR company but the Machine company as well, thousands, yes thousand of dollars... per machine.  Not to mention that our office works with over 18 different hospitals and labs, none of which can communicate with us or each other, without buying and installing proprietary software....FOR EACH COMPUTER/USER  that may log in.  Yes we have an EMR, but we do our notes by hand, and just scan them in....too much BS trying to develop a program that will allow the tech, the ancillary staff, and the MD, to all work on the same shared chart, electronically, as well as do drawings... EMR is not ready for the real Doctors office.</description>
		<content:encoded><![CDATA[<p>Promises, promises, all the things the EMR was supposed to do, all the support that disappeared once the product was bought.  We have many &#8220;EMR compatible machines (visual fields, ocular pressures&#8230;) &#8221; none easily communicate with the EMR which touted being able to support inputing the information&#8230;. yes they will support it, if you pay not only the EMR company but the Machine company as well, thousands, yes thousand of dollars&#8230; per machine.  Not to mention that our office works with over 18 different hospitals and labs, none of which can communicate with us or each other, without buying and installing proprietary software&#8230;.FOR EACH COMPUTER/USER  that may log in.  Yes we have an EMR, but we do our notes by hand, and just scan them in&#8230;.too much BS trying to develop a program that will allow the tech, the ancillary staff, and the MD, to all work on the same shared chart, electronically, as well as do drawings&#8230; EMR is not ready for the real Doctors office.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Physicians Spooked by Failure Stories—EHR Adoption Suffers by Dr. Gregg</title>
		<link>http://blog.srssoft.com/2013/05/physicians-spooked-by-failure-stories-ehr-adoption-suffers/comment-page-1/#comment-17321</link>
		<dc:creator>Dr. Gregg</dc:creator>
		<pubDate>Fri, 10 May 2013 22:39:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.srssoft.com/?p=2327#comment-17321</guid>
		<description>Smarter systems, smarter systems, smarter systems. Starting with the user experience and workflow requirements and programming to match rather than vice versa (as is true for the VAST majority of current EHRs) is key. There are but a few such systems out there that are designed as such, but they are all about the provider experience and they are a joy to use.

Sorry to hear that Richard feels as he does. Using an EHR isn&#039;t about the money, at least in my humble opinion it isn&#039;t. It&#039;s about being a part of doing the right thing. We&#039;re still in the infancy of healthcare digitization, so of course it&#039;s painful. Raising baby isn&#039;t about cost savings or avoiding sleepless nights and parental angst. It&#039;s about doing what&#039;s right, doing what&#039;s needed, to raise a child that will become a well-adjusted addition to the world. And, honestly, is there any way to say that the &quot;adult&quot; paper medical record has any real remaining value given our full-blown and ever-growing information explosion? None that I can see, at least not if you look past the very short term and exquisitely localized view.</description>
		<content:encoded><![CDATA[<p>Smarter systems, smarter systems, smarter systems. Starting with the user experience and workflow requirements and programming to match rather than vice versa (as is true for the VAST majority of current EHRs) is key. There are but a few such systems out there that are designed as such, but they are all about the provider experience and they are a joy to use.</p>
<p>Sorry to hear that Richard feels as he does. Using an EHR isn&#8217;t about the money, at least in my humble opinion it isn&#8217;t. It&#8217;s about being a part of doing the right thing. We&#8217;re still in the infancy of healthcare digitization, so of course it&#8217;s painful. Raising baby isn&#8217;t about cost savings or avoiding sleepless nights and parental angst. It&#8217;s about doing what&#8217;s right, doing what&#8217;s needed, to raise a child that will become a well-adjusted addition to the world. And, honestly, is there any way to say that the &#8220;adult&#8221; paper medical record has any real remaining value given our full-blown and ever-growing information explosion? None that I can see, at least not if you look past the very short term and exquisitely localized view.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
