<?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 Software Specialist - Dr David Kent</title>
	<atom:link href="http://emrman.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://emrman.net</link>
	<description>Electronic Medical Software</description>
	<lastBuildDate>Wed, 02 Dec 2009 09:52:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>Comment on Is there a dark side to cloud computing? by Luke</title>
		<link>http://emrman.net/is-there-a-dark-side-to-cloud-computing/comment-page-1/#comment-13</link>
		<dc:creator>Luke</dc:creator>
		<pubDate>Wed, 02 Dec 2009 09:52:38 +0000</pubDate>
		<guid isPermaLink="false">http://emrman.net/?p=69#comment-13</guid>
		<description>I&#039;m very new to EMR but I&#039;m sold on your approach to this.  There&#039;s tall grass here.  

As a user interface designer, I am tasked with solving end user problems and sending the solution to software engineers for implementation as code.  Now that the market is flooded with cheap cloud computing resources, lots of vendors are popping up selling software services like financial management (Mint) and data backup (Jungle Drive.)  Some make sense, but some are worth being concerned about.

For example, consider an EMR delivered via the web.  If the data is sent via the web to a remote data storage facility, there&#039;s not only the bandwidth bottleneck to contend with (diagnostic images won&#039;t exactly be small files), but there&#039;s the undeniable fact that the data is no longer in your hands.  Indeed, who regulates the cloud?  Sure, it&#039;s possible to encrypt data in transit and transmit that data via secure networking protocols. Yet, for all the VPNs, firewalls and intrusion detection systems in a Fort Knox data center, any data transferred offsite is still offsite.  

For that reason alone, an EMR application served on a secure local network, on hardened local servers, is the most practical implementation.  It gives doctors this new technology that can help them, without taking away, letting them benefit from information technology but still retain physical control and ownership of their medical records data.  Plus, the local connection will let office staff continue to work instead of watching upload progress bars pack.

It simply isn&#039;t practical to expect physicians to adopt an EMR software that forces them to change the way they handle patient information, let alone defies them to even use it.</description>
		<content:encoded><![CDATA[<p>I&#8217;m very new to EMR but I&#8217;m sold on your approach to this.  There&#8217;s tall grass here.  </p>
<p>As a user interface designer, I am tasked with solving end user problems and sending the solution to software engineers for implementation as code.  Now that the market is flooded with cheap cloud computing resources, lots of vendors are popping up selling software services like financial management (Mint) and data backup (Jungle Drive.)  Some make sense, but some are worth being concerned about.</p>
<p>For example, consider an EMR delivered via the web.  If the data is sent via the web to a remote data storage facility, there&#8217;s not only the bandwidth bottleneck to contend with (diagnostic images won&#8217;t exactly be small files), but there&#8217;s the undeniable fact that the data is no longer in your hands.  Indeed, who regulates the cloud?  Sure, it&#8217;s possible to encrypt data in transit and transmit that data via secure networking protocols. Yet, for all the VPNs, firewalls and intrusion detection systems in a Fort Knox data center, any data transferred offsite is still offsite.  </p>
<p>For that reason alone, an EMR application served on a secure local network, on hardened local servers, is the most practical implementation.  It gives doctors this new technology that can help them, without taking away, letting them benefit from information technology but still retain physical control and ownership of their medical records data.  Plus, the local connection will let office staff continue to work instead of watching upload progress bars pack.</p>
<p>It simply isn&#8217;t practical to expect physicians to adopt an EMR software that forces them to change the way they handle patient information, let alone defies them to even use it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Psychiatrists- a breed unto themselves by david</title>
		<link>http://emrman.net/psychiatrists-a-breed-unto-themselves/comment-page-1/#comment-9</link>
		<dc:creator>david</dc:creator>
		<pubDate>Tue, 16 Jun 2009 23:46:30 +0000</pubDate>
		<guid isPermaLink="false">http://emrman.net/?p=75#comment-9</guid>
		<description>Thank you!  I will keep writing and hopefully keep you interested!</description>
		<content:encoded><![CDATA[<p>Thank you!  I will keep writing and hopefully keep you interested!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on By Design! by david</title>
		<link>http://emrman.net/by-design/comment-page-1/#comment-8</link>
		<dc:creator>david</dc:creator>
		<pubDate>Tue, 16 Jun 2009 23:34:57 +0000</pubDate>
		<guid isPermaLink="false">http://emrman.net/?p=64#comment-8</guid>
		<description>You mean is the post copy right protected? No.</description>
		<content:encoded><![CDATA[<p>You mean is the post copy right protected? No.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Psychiatrists- a breed unto themselves by GarykPatton</title>
		<link>http://emrman.net/psychiatrists-a-breed-unto-themselves/comment-page-1/#comment-7</link>
		<dc:creator>GarykPatton</dc:creator>
		<pubDate>Tue, 16 Jun 2009 14:59:24 +0000</pubDate>
		<guid isPermaLink="false">http://emrman.net/?p=75#comment-7</guid>
		<description>Hi. I like the way you write. Will you post some more articles?</description>
		<content:encoded><![CDATA[<p>Hi. I like the way you write. Will you post some more articles?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on By Design! by KattyBlackyard</title>
		<link>http://emrman.net/by-design/comment-page-1/#comment-6</link>
		<dc:creator>KattyBlackyard</dc:creator>
		<pubDate>Mon, 15 Jun 2009 17:06:38 +0000</pubDate>
		<guid isPermaLink="false">http://emrman.net/?p=64#comment-6</guid>
		<description>I really like your post. Does it copyright protected?</description>
		<content:encoded><![CDATA[<p>I really like your post. Does it copyright protected?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on By Design! by AndrewBoldman</title>
		<link>http://emrman.net/by-design/comment-page-1/#comment-4</link>
		<dc:creator>AndrewBoldman</dc:creator>
		<pubDate>Fri, 05 Jun 2009 02:30:25 +0000</pubDate>
		<guid isPermaLink="false">http://emrman.net/?p=64#comment-4</guid>
		<description>da best. Keep it going! Thank you</description>
		<content:encoded><![CDATA[<p>da best. Keep it going! Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ChartShare &#8211; EMR Practice Software by KrisBelucci</title>
		<link>http://emrman.net/chartshare-emr-practice-software/comment-page-1/#comment-3</link>
		<dc:creator>KrisBelucci</dc:creator>
		<pubDate>Tue, 02 Jun 2009 18:07:33 +0000</pubDate>
		<guid isPermaLink="false">http://emrman.net/?p=17#comment-3</guid>
		<description>Hi, good post. I have been wondering about this issue,so thanks for posting. I’ll definitely be coming back to your site.</description>
		<content:encoded><![CDATA[<p>Hi, good post. I have been wondering about this issue,so thanks for posting. I’ll definitely be coming back to your site.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

