<?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: Privacy Law Showdown? Legal and Policy Analysis.</title>
	<atom:link href="http://e-CareManagement.com/privacy-law-showdown-legal-and-policy-analysis/feed/" rel="self" type="application/rss+xml" />
	<link>http://e-CareManagement.com/privacy-law-showdown-legal-and-policy-analysis/</link>
	<description>Chronic Disease Management • Technology • Strategy • Issues and Trends</description>
	<lastBuildDate>Sat, 11 Feb 2012 04:21:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: medlaw</title>
		<link>http://e-CareManagement.com/privacy-law-showdown-legal-and-policy-analysis/comment-page-1/#comment-12684</link>
		<dc:creator>medlaw</dc:creator>
		<pubDate>Fri, 23 Apr 2010 18:10:36 +0000</pubDate>
		<guid isPermaLink="false">http://e-CareManagement.com/?p=779#comment-12684</guid>
		<description>I am kind of at a loss to see the evil to be alleviated by the proposal to create a second level of medical privacy laws applicable only to &quot;PHRs Primarily for Patient Benefit&quot;.  Besides the evident difficulty in defining that term, it&#039;s no small task involved in crafting a new regulatory scheme only to be used by this new class.  Also, any PHR set up to benefit the patient can only fulfill that promise by being accessible to said patient&#039;s health care providers.  The main benefit to the patient is rapid access to the patient&#039;s complete history by any provider no matter where located.  Meaning health care providers (covered entities) must interactive with all PHRs for them to have any utility.  Perhaps a better approach would be to lobby for a few limited exceptions to specific HIPAA provisions that the industry feels are the most burdensome.</description>
		<content:encoded><![CDATA[<p>I am kind of at a loss to see the evil to be alleviated by the proposal to create a second level of medical privacy laws applicable only to &#8220;PHRs Primarily for Patient Benefit&#8221;.  Besides the evident difficulty in defining that term, it&#8217;s no small task involved in crafting a new regulatory scheme only to be used by this new class.  Also, any PHR set up to benefit the patient can only fulfill that promise by being accessible to said patient&#8217;s health care providers.  The main benefit to the patient is rapid access to the patient&#8217;s complete history by any provider no matter where located.  Meaning health care providers (covered entities) must interactive with all PHRs for them to have any utility.  Perhaps a better approach would be to lobby for a few limited exceptions to specific HIPAA provisions that the industry feels are the most burdensome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Howard</title>
		<link>http://e-CareManagement.com/privacy-law-showdown-legal-and-policy-analysis/comment-page-1/#comment-13082</link>
		<dc:creator>Andrew Howard</dc:creator>
		<pubDate>Wed, 22 Apr 2009 05:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://e-CareManagement.com/?p=779#comment-13082</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Deven McGraw (of @CenDemTech) offers lucid analysis of what new health privacy provisions in ARRA/HITECH might mean:  http://bit.ly/dApoX&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Deven McGraw (of @CenDemTech) offers lucid analysis of what new health privacy provisions in ARRA/HITECH might mean:  <a href="http://bit.ly/dApoX" >http://bit.ly/dApoX</a></span></span></span></p>
]]></content:encoded>
	</item>
</channel>
</rss>

