<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Avoid Breach Notification - Experior helps PHI Encryption &#187; ARRA</title>
	<atom:link href="http://www.experiordata.com/blog/tag/arra/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.experiordata.com/blog</link>
	<description>Encrypt your PHI, and avoid breach notification</description>
	<lastBuildDate>Tue, 18 May 2010 04:09:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Healthleaders Media Predicts Strict Enforcement of ARRA and HITECH Act</title>
		<link>http://www.experiordata.com/blog/2009/12/08/healthleaders-media-predicts-strict-enforcement-of-arra-and-hitech-act/</link>
		<comments>http://www.experiordata.com/blog/2009/12/08/healthleaders-media-predicts-strict-enforcement-of-arra-and-hitech-act/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 05:16:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ARRA]]></category>
		<category><![CDATA[HIPAA]]></category>

		<guid isPermaLink="false">http://www.experiordata.com/blog/?p=286</guid>
		<description><![CDATA[According to HealthLeaders Media
&#160;
&#34;As for enforcement, Congress promised in ARRA &#34;periodic audits&#34; to ensure HIPAA compliance. Government officials told HealthLeaders Media in September they weren&#39;t sure what that meant, and Apgar says OCR still does not have a definitive plan. Likely, they will not publish a plan until second quarter 2010.&#34;
&#160;
Sounds like 2009 was the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.healthleadersmedia.com/content/242913/page/2/topic/WS_HLM2_TEC/Flurry-of-HIPAA-Activity-Expected-Over-Next-Three-Months.html" target="_blank">According to HealthLeaders Media</a></p>
<p>&nbsp;</p>
<p>&quot;<span class="Apple-style-span" style="color: rgb(74, 72, 64); font-family: tahoma, Verdana, sans-serif; line-height: 16px; ">As for enforcement, Congress promised in ARRA &quot;periodic audits&quot; to ensure HIPAA compliance. Government officials told HealthLeaders Media in September they weren&#39;t sure what that meant, and Apgar says OCR still does not have a definitive plan. Likely, they will not publish a plan until second quarter 2010.&quot;</span></p>
<p>&nbsp;</p>
<p>Sounds like 2009 was the year of the healthcare law revisions. 2010 looks like it may be the year of enforcement.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.experiordata.com/blog/2009/12/08/healthleaders-media-predicts-strict-enforcement-of-arra-and-hitech-act/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Breach notification goes into effect on September 23, 2009</title>
		<link>http://www.experiordata.com/blog/2009/09/02/breach-notification-goes-into-effect-on-september-23-2009/</link>
		<comments>http://www.experiordata.com/blog/2009/09/02/breach-notification-goes-into-effect-on-september-23-2009/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 03:50:52 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ARRA]]></category>
		<category><![CDATA[Encyption]]></category>
		<category><![CDATA[HIPAA]]></category>
		<category><![CDATA[Rulings]]></category>
		<category><![CDATA[Section 13402]]></category>
		<category><![CDATA[13402]]></category>
		<category><![CDATA[breach notification]]></category>
		<category><![CDATA[encryption]]></category>

		<guid isPermaLink="false">http://www.experiordata.com/blog/?p=102</guid>
		<description><![CDATA[The new breach notification guidelines go into effect on September 23rd, 2009. Even though breach notification goes into effect on 9/23/09, the Interim Rule states that civil penalties will not be imposed until February 18th, 2010. The government is aware of the ambiguity and clearly states that it has discretion on imposing sanctions for failure [...]]]></description>
			<content:encoded><![CDATA[<p>The new breach notification guidelines go into effect on September 23rd, 2009. Even though breach notification goes into effect on 9/23/09, the <a title="Experior resoures on Interim Final Rule on Breach Notification" href="http://experiordata.com/resources.php">Interim Rule</a> states that civil penalties will not be imposed until February 18th, 2010. The government is aware of the ambiguity and clearly states that it has discretion on imposing sanctions for failure to provide notification in case of a breach notification for breaches occurring before 2/18/10.</p>
<p><span style="color: #ffffff;">..</span></p>
<p>During the 180 period between 8/2009 and  2/2010 covered entities have the perfect opportunity to review the data stored on their IT systems. The Interim Rule is concerned specifically with <a title="What is Data in Motion encryption?" href="http://www.experiordata.com/data_motion.php" target="_blank">Data in Motion</a>, <a title="What is Data in Motion encryption?" href="http://www.experiordata.com/data_use.php" target="_blank">Data in Use</a>, <a title="What is Data at Rest encryption?" href="http://www.experiordata.com/data_rest.php" target="_blank">Data at Rest</a>, and <a title="How to protect Data Disposed" href="http://www.experiordata.com/data_disposed.php" target="_blank">Data Disposed.</a> Experior can help  determine the best plan of action to implement encryption  in your IT systems to protect   your organization from breach notification requirements.</p>
<p><br class="spacer_" /></p>
<p><br class="spacer_" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.experiordata.com/blog/2009/09/02/breach-notification-goes-into-effect-on-september-23-2009/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Protected Health Information &#8211; What is it?</title>
		<link>http://www.experiordata.com/blog/2009/08/24/protected-health-information-what-is-it/</link>
		<comments>http://www.experiordata.com/blog/2009/08/24/protected-health-information-what-is-it/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 03:54:58 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ARRA]]></category>
		<category><![CDATA[HIPAA]]></category>
		<category><![CDATA[Rulings]]></category>
		<category><![CDATA[PHI]]></category>

		<guid isPermaLink="false">http://www.experiordata.com/blog/?p=36</guid>
		<description><![CDATA[The term Protected Health Information (PHI) has its roots in the term &#8220;Individually Identifiable Information&#8221; that was first used in the context of privacy regulation in the Health Insurance Portability and Accountability Act of 1996 (HIPAA).
..
HIPAA explicitly defines this Information as &#8220;&#8230;any information, including demographic information collected from an individual, that&#8211;&#8221;(A) is created or received by [...]]]></description>
			<content:encoded><![CDATA[<p>The term Protected Health Information (PHI) has its roots in the term &#8220;Individually Identifiable Information&#8221; that was first used in the context of privacy regulation in the <a href="http://www.cms.hhs.gov/HIPAAGenInfo/Downloads/HIPAALaw.pdf">Health Insurance Portability and Accountability Act of 1996</a> (HIPAA).</p>
<p><span style="color: #ffffff;">..</span><br />
HIPAA explicitly defines this Information as &#8220;&#8230;any information, including demographic information collected from an individual, that&#8211;&#8221;(A) is created or received by a health care provider, health plan, employer, or health care clearinghouse; and &#8221;(B) relates to the past, present, or future physical or mental health or condition of an individual, the provision of health care to an individual, or the past, present, or future payment for the provision of health care to an individual, and&#8211;&#8221;(i) identifies the individual; or &#8221;(ii) with respect to which there is a reasonable basis to believe that the information can be used to identify the individual.&#8221;</p>
<p><span style="color: #ffffff;">..</span></p>
<p>Protected  Health Information takes that definition and applies and electronic twist to it. The <a href="http://www.experiordata.com/images/interim_final_ruling.pdf">Interim Final Rule on Breach Notification for Unsecured Protected Health Information</a> on page 4 of the preamble defines protected health information as:  &#8220;<strong>individually identifiable health information</strong> held or transmitted in any form or medium by HIPAA covered entities and business associates, subject to certain limited exceptions&#8221;.</p>
<p><span style="color: #ffffff;">..</span></p>
<p>&#8220;Subject to certain limited exceptions&#8221; can be interpreted to mean additional exclusions listed in <a href="http://www.hhs.gov/ocr/privacy/hipaa/administrative/privacyrule/privrulepd.pdf">Standards for Privacy of Individually Identifiable Health Information; Final Rule, 45 CFR Parts 160 and 164</a>, ss 164.501. Exclusions as written are an employer in its role as a covered entity (covered entities are employers as well) and education records specified in the Family Education Rights and Privacy Act, 20 U.S.C. 1232g.</p>
<div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px;">&#8216;individually</div>
<div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px;">identifiable health information&#8217; means any information, including demographic</div>
<div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px;">information collected from an individual, that&#8211;</div>
<div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px;">&#8220;(A) is created or received by a health care provider, health plan, employer, or</div>
<div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px;">health care clearinghouse; and</div>
<div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px;">&#8220;(B) relates to the past, present, or future physical or mental health or condition of</div>
<div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px;">an individual, the provision of health care to an individual, or the past, present, or</div>
<div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px;">future payment for the provision of health care to an individual, and&#8211;</div>
<div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px;">&#8220;(i) identifies the individual; or</div>
<div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px;">&#8220;(ii) with respect to which there is a reasonable basis to believe that the information</div>
<div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px;">can be used to identify the individual</div>
]]></content:encoded>
			<wfw:commentRss>http://www.experiordata.com/blog/2009/08/24/protected-health-information-what-is-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HHS Ruling on Encryption &#8211; ARRA/HITECH ACT subsection 13402</title>
		<link>http://www.experiordata.com/blog/2009/08/24/hhs-ruling-on-encryption-arrahitech-act-subsection-13402/</link>
		<comments>http://www.experiordata.com/blog/2009/08/24/hhs-ruling-on-encryption-arrahitech-act-subsection-13402/#comments</comments>
		<pubDate>Mon, 24 Aug 2009 04:46:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[ARRA]]></category>
		<category><![CDATA[Rulings]]></category>
		<category><![CDATA[Section 13402]]></category>
		<category><![CDATA[13402]]></category>
		<category><![CDATA[breach notification]]></category>

		<guid isPermaLink="false">http://www.experiordata.com/blog/?p=3</guid>
		<description><![CDATA[On Thursday, August 20th, 2009, the U.S. Department of Health and Human Services (HHS) issued the Interim Final Rule on Breach Notification.
 An important part the interim final rule is the decision that encryption is the only acceptable technology to make protected health information (essentially, patient records) &#8220;unusable, unreadable, or indecipherable to unauthorized individuals&#8221;. The [...]]]></description>
			<content:encoded><![CDATA[<p>On Thursday, August 20th, 2009, the U.S. Department of Health and Human Services (HHS) issued the <a href="http://www.hhs.gov/ocr/privacy/hipaa/understanding/coveredentities/breachnotificationifr.html">Interim Final Rule on Breach Notification.</a><br />
<br/><a href="http://www.hhs.gov/ocr/privacy/hipaa/understanding/coveredentities/breachnotificationifr.html"></a> An important part the interim final rule is the decision that encryption is the only acceptable technology to make protected health information (essentially, patient records) &#8220;unusable, unreadable, or indecipherable to unauthorized individuals&#8221;. The preamble to the rule explains that even though other methods (such as access control) can continue to be used, if a breach occurs and the protected health information is disclosed to unauthorized individuals a breach notification is required.<br />
<br/>Breach notifications are essentially categorized as &#8220;under 500&#8243; and &#8220;over 500&#8243; records. If a breach occurred to under 500 records then covered entities must maintain a log of the breach and notify the patients. If a breach over 500 records has occurred then not only patients need to be notified but also major media outlet and HHS. In addition, a hotline must be established so that people can call and obtain more information about the breach (notification procedures are specified in the HITECH Act, Section 13402). HHS can issue fines and attorneys general of each state are empowered to pursue these types of breaches on a criminal level.<br/><br />
The government is clearly serious about patient record privacy to encourage covered entities to move paper records to electronic records as part of its overall healthcare reform efforts.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.experiordata.com/blog/2009/08/24/hhs-ruling-on-encryption-arrahitech-act-subsection-13402/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
