<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Are Rules Destroying Value?</title>
	<atom:link href="http://tcummins.wordpress.com/2008/07/11/are-rules-destroying-value/feed/" rel="self" type="application/rss+xml" />
	<link>http://tcummins.wordpress.com/2008/07/11/are-rules-destroying-value/</link>
	<description>Managing Relationships in the Global Networked Economy</description>
	<lastBuildDate>Mon, 02 Nov 2009 21:48:49 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Over complicating things is a bad idea &#124; AccMan</title>
		<link>http://tcummins.wordpress.com/2008/07/11/are-rules-destroying-value/#comment-400</link>
		<dc:creator>Over complicating things is a bad idea &#124; AccMan</dc:creator>
		<pubDate>Wed, 06 Aug 2008 01:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://tcummins.wordpress.com/?p=69#comment-400</guid>
		<description>[...] an interesting topic and the original post by Tim Cummins raises useful points, especially when dealing with US organizations. It plays directly to the [...]</description>
		<content:encoded><![CDATA[<p>[...] an interesting topic and the original post by Tim Cummins raises useful points, especially when dealing with US organizations. It plays directly to the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Mark Anderman</title>
		<link>http://tcummins.wordpress.com/2008/07/11/are-rules-destroying-value/#comment-397</link>
		<dc:creator>Jason Mark Anderman</dc:creator>
		<pubDate>Mon, 28 Jul 2008 04:01:41 +0000</pubDate>
		<guid isPermaLink="false">http://tcummins.wordpress.com/?p=69#comment-397</guid>
		<description>Perhaps a good example of the problem noted in this posting is the HIPAA business associate contract.  This is a contract required under the HIPAA Privacy Rule (&quot;Rule&quot;) adopted by the U.S. Department of Health and Human Services (&quot;HHS&quot;).  All health care providers covered by HIPAA, as well as health plans and health care clearinghouses, must force any third party service provider accessing a patient&#039;s health data to sign this contract, which includes provisions protecting the privacy of the patient.  While an interesting debate could be held as to whether this contracting requirement should exist in the first place, assuming the requirement is appropriate, its implementation has resulted in a tremendous waste of resources.  The Rule describes the clauses that must be included in the contract, but allows covered entities to write those clauses as they see fit.  As a result, soon after the Rule came into force, covered entities and service providers confronted each other with a dizzying variety of clauses which led to long debates and negotiations as to whose incarnation best reflected the Rule.  Even worse, HHS then proposed a sample contract which itself did not match the exact language of the Rule.  Ultimately, many lawyers in the health care, health insurance, pharmaceutical and medical device industries have spent countless hours negotiating these contracts.  This is time that could have been much better spent elsewhere, and HHS could have prevented all of this waste quite simply by just mandating that everyone sign the HHS sample contract, which is more or less palatable to all parties.  In sum, the HIPAA business associate contract offers a tale of a regulation out of balance with the needs of those whom HHS regulates.  More importantly, the collateral cost of time and legal expense to comply with this requirement is a good example of how such a financial drain limits choices we can make with our limited dollars, thereby constraining our freedoms.</description>
		<content:encoded><![CDATA[<p>Perhaps a good example of the problem noted in this posting is the HIPAA business associate contract.  This is a contract required under the HIPAA Privacy Rule (&#8220;Rule&#8221;) adopted by the U.S. Department of Health and Human Services (&#8220;HHS&#8221;).  All health care providers covered by HIPAA, as well as health plans and health care clearinghouses, must force any third party service provider accessing a patient&#8217;s health data to sign this contract, which includes provisions protecting the privacy of the patient.  While an interesting debate could be held as to whether this contracting requirement should exist in the first place, assuming the requirement is appropriate, its implementation has resulted in a tremendous waste of resources.  The Rule describes the clauses that must be included in the contract, but allows covered entities to write those clauses as they see fit.  As a result, soon after the Rule came into force, covered entities and service providers confronted each other with a dizzying variety of clauses which led to long debates and negotiations as to whose incarnation best reflected the Rule.  Even worse, HHS then proposed a sample contract which itself did not match the exact language of the Rule.  Ultimately, many lawyers in the health care, health insurance, pharmaceutical and medical device industries have spent countless hours negotiating these contracts.  This is time that could have been much better spent elsewhere, and HHS could have prevented all of this waste quite simply by just mandating that everyone sign the HHS sample contract, which is more or less palatable to all parties.  In sum, the HIPAA business associate contract offers a tale of a regulation out of balance with the needs of those whom HHS regulates.  More importantly, the collateral cost of time and legal expense to comply with this requirement is a good example of how such a financial drain limits choices we can make with our limited dollars, thereby constraining our freedoms.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
