<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>HIPAA Update</title>
	
	<link>http://blogs.hcpro.com/hipaa</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Thu, 19 Nov 2009 14:34:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/hipaa" type="application/rss+xml" /><feedburner:emailServiceId>hipaa</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
		<title>Eight tips to polish your hospital’s patient breach response</title>
		<link>http://feedproxy.google.com/~r/hipaa/~3/z4yU4H_aJEE/</link>
		<comments>http://blogs.hcpro.com/hipaa/2009/11/eight-tips-to-polish-your-hospitals-patient-breach-response/#comments</comments>
		<pubDate>Thu, 19 Nov 2009 14:34:35 +0000</pubDate>
		<dc:creator>Dom Nicastro</dc:creator>
				<category><![CDATA[Breach Notification]]></category>
		<category><![CDATA[Business Associates]]></category>
		<category><![CDATA[HHS]]></category>
		<category><![CDATA[HIPAA Violations]]></category>
		<category><![CDATA[HIPAA privacy]]></category>
		<category><![CDATA[HIPAA security]]></category>
		<category><![CDATA[HITECH Act]]></category>
		<category><![CDATA[Unsecure PHI]]></category>

		<guid isPermaLink="false">http://blogs.hcpro.com/hipaa/?p=1315</guid>
		<description>Editor&amp;#8217;s note: This is the third in a three-part series about breach notifications. Part one focused on how to prevent breaches. Part two tackled how to handle breaches. This installment offers some final tips if a breach occurs. focused on how to prevent breaches.
Now that you&amp;#8217;ve followed protocol—the government&amp;#8217;s and your facility&amp;#8217;s—consider these final checklist [...]&lt;img src="http://feeds.feedburner.com/~r/hipaa/~4/z4yU4H_aJEE" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blogs.hcpro.com/hipaa/2009/11/eight-tips-to-polish-your-hospitals-patient-breach-response/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.hcpro.com/hipaa/2009/11/eight-tips-to-polish-your-hospitals-patient-breach-response/</feedburner:origLink></item>
		<item>
		<title>Four steps to manage patient information breaches</title>
		<link>http://feedproxy.google.com/~r/hipaa/~3/ZTRgyNJRC0c/</link>
		<comments>http://blogs.hcpro.com/hipaa/2009/11/four-steps-to-manage-patient-information-breaches/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 14:17:25 +0000</pubDate>
		<dc:creator>Dom Nicastro</dc:creator>
				<category><![CDATA[Breach Notification]]></category>
		<category><![CDATA[Business Associates]]></category>
		<category><![CDATA[HHS]]></category>
		<category><![CDATA[HIPAA Violations]]></category>
		<category><![CDATA[HIPAA privacy]]></category>
		<category><![CDATA[HIPAA security]]></category>
		<category><![CDATA[HITECH Act]]></category>
		<category><![CDATA[Unsecure PHI]]></category>

		<guid isPermaLink="false">http://blogs.hcpro.com/hipaa/?p=1311</guid>
		<description>Editor&amp;#8217;s note: This is the second in a three-part series about breach notifications. This installment focuses on handling breaches.
Your facility has a breach of unsecure PHI. What do you do?
In addition to following requirements spelled out in HHS&amp;#8217; interim final rule on breach notification, consider these tips for handling the breach:

Initiate an investigation immediately. The [...]&lt;img src="http://feeds.feedburner.com/~r/hipaa/~4/ZTRgyNJRC0c" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blogs.hcpro.com/hipaa/2009/11/four-steps-to-manage-patient-information-breaches/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.hcpro.com/hipaa/2009/11/four-steps-to-manage-patient-information-breaches/</feedburner:origLink></item>
		<item>
		<title>Five ways to prevent patient information breaches</title>
		<link>http://feedproxy.google.com/~r/hipaa/~3/YsZNhK9xJ_A/</link>
		<comments>http://blogs.hcpro.com/hipaa/2009/11/five-ways-to-prevent-patient-information-breaches/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 05:00:47 +0000</pubDate>
		<dc:creator>Dom Nicastro</dc:creator>
				<category><![CDATA[Breach Notification]]></category>
		<category><![CDATA[Business Associates]]></category>
		<category><![CDATA[HIPAA privacy]]></category>
		<category><![CDATA[HIPAA security]]></category>
		<category><![CDATA[HITECH Act]]></category>

		<guid isPermaLink="false">http://blogs.hcpro.com/hipaa/?p=1304</guid>
		<description>Editor&amp;#8217;s note: This is the first in a three-part series about breach notifications. The first installment focuses on preventing breaches.
The U.S. Department of Health and Human Services (HHS) on August 19 released its interim final rule on breach notification of unsecure protected health information (PHI) and the acceptable methods for covered entities (CE) and business [...]&lt;img src="http://feeds.feedburner.com/~r/hipaa/~4/YsZNhK9xJ_A" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blogs.hcpro.com/hipaa/2009/11/five-ways-to-prevent-patient-information-breaches/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://blogs.hcpro.com/hipaa/2009/11/five-ways-to-prevent-patient-information-breaches/</feedburner:origLink></item>
		<item>
		<title>Check out this major breach</title>
		<link>http://feedproxy.google.com/~r/hipaa/~3/Zt4JLbV7cPw/</link>
		<comments>http://blogs.hcpro.com/hipaa/2009/11/check-out-this-major-breach/#comments</comments>
		<pubDate>Mon, 16 Nov 2009 05:00:06 +0000</pubDate>
		<dc:creator>Dom Nicastro</dc:creator>
				<category><![CDATA[Breach Notification]]></category>
		<category><![CDATA[HIPAA News]]></category>

		<guid isPermaLink="false">http://blogs.hcpro.com/hipaa/?p=1298</guid>
		<description>If you think your facility is safe because of strong breach prevention programs, think again.  It can happen &amp;#8212; anywhere, from one simple mistake.&lt;img src="http://feeds.feedburner.com/~r/hipaa/~4/Zt4JLbV7cPw" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blogs.hcpro.com/hipaa/2009/11/check-out-this-major-breach/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://blogs.hcpro.com/hipaa/2009/11/check-out-this-major-breach/</feedburner:origLink></item>
		<item>
		<title>Q&amp;A: How CMS responds to HIPAA complaints</title>
		<link>http://feedproxy.google.com/~r/hipaa/~3/SigfKbaigAg/</link>
		<comments>http://blogs.hcpro.com/hipaa/2009/11/qa-how-cms-responds-to-hipaa-complaints/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 05:00:00 +0000</pubDate>
		<dc:creator>Dom Nicastro</dc:creator>
				<category><![CDATA[Compliance Monitor]]></category>

		<guid isPermaLink="false">tag:www.hcpro.com://5b00ad6864ba28f7c74c56c4aa19c154</guid>
		<description>&lt;p&gt;&amp;#160;&lt;strong&gt;Q:&lt;/strong&gt; How does CMS handle a Health Insurance Portability and Accountability Act (HIPAA) complaint once received?&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;A:&lt;/strong&gt; Upon receipt of a complaint, CMS will notify the filed against entity of the complaint, and provide them with an opportunity to demonstrate compliance, or to submit a corrective action plan. CMS has the discretion to conduct compliance reviews or on-site evaluations of covered entities' procedures to verify that they are compliant with the standard transactions or use the national identifiers. CMS also has the authority to impose financial penalties on any entity that is not compliant and has failed to correct their systems.&lt;/p&gt;
 &lt;p&gt;&lt;em&gt;This Q&amp;#38;A is adapted from the CMS FAQ website page. To view this and other FAQs &lt;a href="http://questions.cms.hhs.gov/cgi-bin/cmshhs.cfg/php/enduser/std_adp.php?p_faqid=1331&amp;#38;p_created=1034777776&amp;#38;p_sid=R-vARyMj&amp;#38;p_accessibility=0&amp;#38;p_redirect=&amp;#38;p_lva=&amp;#38;p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PTQ6MiZwX3Jvd19jbnQ9MzksMzkmcF9wcm9kcz0wJnBfY2F0cz0mc"&gt;click here&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/hipaa/~4/SigfKbaigAg" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blogs.hcpro.com/hipaa/2009/11/qa-how-cms-responds-to-hipaa-complaints/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.hcpro.com/hipaa/2009/11/qa-how-cms-responds-to-hipaa-complaints/</feedburner:origLink></item>
		<item>
		<title>Burning medical records to CD</title>
		<link>http://feedproxy.google.com/~r/hipaa/~3/Upz60C74zIE/</link>
		<comments>http://blogs.hcpro.com/hipaa/2009/11/burning-medical-records-to-cd/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 04:00:49 +0000</pubDate>
		<dc:creator>kmeyer</dc:creator>
				<category><![CDATA[Provider Posts]]></category>

		<guid isPermaLink="false">http://blogs.hcpro.com/hipaa/?p=1277</guid>
		<description>I was just informed from our compliance manager that in February of 2010 – due to HIPAA changes – that the medical records need to be burned to a CD before being sent out.
Is this a true statement?
Karen Meyer
 Health Information Services Supervisor
 Summit Orthopedics
 Woodbury,  MN&lt;img src="http://feeds.feedburner.com/~r/hipaa/~4/Upz60C74zIE" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blogs.hcpro.com/hipaa/2009/11/burning-medical-records-to-cd/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		<feedburner:origLink>http://blogs.hcpro.com/hipaa/2009/11/burning-medical-records-to-cd/</feedburner:origLink></item>
		<item>
		<title>HIPAA Q&amp;A: Red Flags Rule</title>
		<link>http://feedproxy.google.com/~r/hipaa/~3/DvLd5M0gguE/</link>
		<comments>http://blogs.hcpro.com/hipaa/2009/11/hipaa-qa-red-flags-rule/#comments</comments>
		<pubDate>Wed, 11 Nov 2009 04:00:00 +0000</pubDate>
		<dc:creator>Dom Nicastro</dc:creator>
				<category><![CDATA[HIPAA Weekly Advisor]]></category>

		<guid isPermaLink="false">tag:www.hcpro.com://ab335e661d3d5eca2348073d0fa6e6aa</guid>
		<description>&lt;p&gt;&lt;strong&gt;Q. How does the HIPAA privacy rule coincide with the new Red Flags Rule, which requires providers with covered accounts to contact law enforcement if the provider suspects identity theft? May providers release PHI or discuss the patient&amp;#8217;s case with law enforcement officials?&lt;br /&gt;
 &lt;br /&gt;
 A. &lt;/strong&gt;The Red Flags Rule does not require you to notify law enforcement officials of suspected identify theft. Instead, the rule permits you to do so. Most states' identity theft protection laws allow this as well. Informing law enforcement officials about a PHI breach and its nature does not violate HIPAA. Patient authorization is necessary before you disclose any specific identifiable information to law enforcement officials. Absent specific authorization, release of PHI to law enforcement would violate the HIPAA privacy rule.&lt;br /&gt;
 &lt;br /&gt;
 Advising patients to contact law enforcement is the best course of action. If warranted, notify law enforcement of the breach and provide the perpetrator&amp;#8217;s name if known, but don&amp;#8217;t provide a list of affected patients.&lt;br /&gt;
 &lt;em&gt;&lt;br /&gt;
 Editor&amp;#8217;s note: &lt;a href="http://www.apgarandassoc.com/about/"&gt;Chris Apgar, CISSP&lt;/a&gt;, answered this question. This is not legal advice. Consult your attorney regarding legal matters.&lt;br /&gt;
 &lt;/em&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/hipaa/~4/DvLd5M0gguE" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blogs.hcpro.com/hipaa/2009/11/hipaa-qa-red-flags-rule/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.hcpro.com/hipaa/2009/11/hipaa-qa-red-flags-rule/</feedburner:origLink></item>
		<item>
		<title>Calling all ‘meaningful use’ experts</title>
		<link>http://feedproxy.google.com/~r/hipaa/~3/BAOEumQJL6g/</link>
		<comments>http://blogs.hcpro.com/hipaa/2009/11/calling-all-meaningul-use-experts/#comments</comments>
		<pubDate>Tue, 10 Nov 2009 16:40:20 +0000</pubDate>
		<dc:creator>Dom Nicastro</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.hcpro.com/hipaa/?p=1280</guid>
		<description>Anyone out there interested in working with us on an audio conference in early February, based on the interim final rule on the definition of meaningful use of EHRs?&lt;img src="http://feeds.feedburner.com/~r/hipaa/~4/BAOEumQJL6g" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blogs.hcpro.com/hipaa/2009/11/calling-all-meaningul-use-experts/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://blogs.hcpro.com/hipaa/2009/11/calling-all-meaningul-use-experts/</feedburner:origLink></item>
		<item>
		<title>Guidance on HIPAA implications of H1N1</title>
		<link>http://feedproxy.google.com/~r/hipaa/~3/-sat3lVztTI/</link>
		<comments>http://blogs.hcpro.com/hipaa/2009/11/guidance-on-hipaa-implications-of-h1n1/#comments</comments>
		<pubDate>Tue, 10 Nov 2009 04:00:00 +0000</pubDate>
		<dc:creator>fruelas</dc:creator>
				<category><![CDATA[HIPAA News]]></category>
		<category><![CDATA[HIPAA Weekly Advisor]]></category>

		<guid isPermaLink="false">tag:www.hcpro.com://5aab36ad69b4c75f441ddaca6cfb9757</guid>
		<description>&lt;p&gt;Following the recent declaration for H1N1 flu as a national health emergency, the government posted a number of documents that have HIPAA implications, says Frank Ruelas, director of compliance and risk management at Maryvale Hospital and principal, HIPAA Boot Camp, in Casa Grande, AZ.&lt;br /&gt;
 &lt;br /&gt;
 Ruelas points &lt;a href="http://www.cdc.gov/h1n1flu/vaccination/pdf/List_of_Annotated_CMS_Links_102609_rev.pdf"&gt;to this document on the CDC Web site&lt;/a&gt; that summarizes other related documents online.&lt;br /&gt;
 &lt;br /&gt;
 &amp;#8220;Many of these documents help clear up questions on whether the subsequent 1135 waivers suspend HIPAA, the time frame related to these waivers, and those provisions of the HIPAA privacy rule where the Secretary of HHS may waive sanctions and penalties,&amp;#8221; Ruelas says.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/hipaa/~4/-sat3lVztTI" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blogs.hcpro.com/hipaa/2009/11/guidance-on-hipaa-implications-of-h1n1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.hcpro.com/hipaa/2009/11/guidance-on-hipaa-implications-of-h1n1/</feedburner:origLink></item>
		<item>
		<title>New HIPAA whitepaper!</title>
		<link>http://feedproxy.google.com/~r/hipaa/~3/YySbeLzBtLs/</link>
		<comments>http://blogs.hcpro.com/hipaa/2009/11/new-hipaa-whitepaper/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 19:56:03 +0000</pubDate>
		<dc:creator>Dom Nicastro</dc:creator>
				<category><![CDATA[Breach Notification]]></category>
		<category><![CDATA[HHS]]></category>
		<category><![CDATA[HIPAA News]]></category>
		<category><![CDATA[HIPAA privacy]]></category>
		<category><![CDATA[HIPAA security]]></category>
		<category><![CDATA[HITECH Act]]></category>
		<category><![CDATA[Unsecure PHI]]></category>

		<guid isPermaLink="false">http://blogs.hcpro.com/hipaa/?p=1258</guid>
		<description>Check out our new white HIPAA whitepaper, &amp;#8220;HHS breach notification interim final rule: Form your incident response team, set policies and procedures to comply with new federal HIPAA Regulations. November, 2009.&amp;#8221;
Download a free copy of the whitepaper.&lt;img src="http://feeds.feedburner.com/~r/hipaa/~4/YySbeLzBtLs" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blogs.hcpro.com/hipaa/2009/11/new-hipaa-whitepaper/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blogs.hcpro.com/hipaa/2009/11/new-hipaa-whitepaper/</feedburner:origLink></item>
	</channel>
</rss><!-- Dynamic page generated in 0.612 seconds. --><!-- Cached page generated by WP-Super-Cache on 2009-11-19 09:34:45 -->
