<?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: Do electronic medical records raise malpractice risk?</title>
	<atom:link href="http://www.kevinmd.com/blog/2007/07/do-electronic-medical-records-raise.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.kevinmd.com/blog/2007/07/do-electronic-medical-records-raise.html</link>
	<description>medical blog</description>
	<lastBuildDate>Sun, 22 Nov 2009 14:15:05 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anonymous</title>
		<link>http://www.kevinmd.com/blog/2007/07/do-electronic-medical-records-raise.html/comment-page-1#comment-77543</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 11 Jul 2007 17:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/kevinmd/2007/07/do-electronic-medical-records-raise-malpractice-risk.html#comment-77543</guid>
		<description>The potential hazard is clear.  The physician has a limited amount of time that can be spent in the care of any one patient.  The attorney has screened for a damaged, sympathetic client and has by comparison unlimited time to comb through medical records. The incredibly vast reams of data, most clinically meaningless, allow any tale to be spun for the jury.</description>
		<content:encoded><![CDATA[<p>The potential hazard is clear.  The physician has a limited amount of time that can be spent in the care of any one patient.  The attorney has screened for a damaged, sympathetic client and has by comparison unlimited time to comb through medical records. The incredibly vast reams of data, most clinically meaningless, allow any tale to be spun for the jury.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
