<?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>HIPAA Information &#187; HIPAA Compliance</title>
	<atom:link href="http://www.hipaastore.com/info/category/hipaa-compliance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hipaastore.com/info</link>
	<description>HIPAA Training, Compliance &#38; Awareness</description>
	<lastBuildDate>Tue, 29 Sep 2009 07:52:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</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" />
		<item>
		<title>&#8220;Workforce Clearance&#8221;&#8230; Ignore It at Your Own Peril!</title>
		<link>http://www.hipaastore.com/info/workforce-clearance/</link>
		<comments>http://www.hipaastore.com/info/workforce-clearance/#comments</comments>
		<pubDate>Sun, 23 Aug 2009 23:40:02 +0000</pubDate>
		<dc:creator>Abner</dc:creator>
				<category><![CDATA[Employers & HIPAA]]></category>
		<category><![CDATA[HIPAA Compliance]]></category>
		<category><![CDATA[Covered Entities]]></category>
		<category><![CDATA[Employers]]></category>
		<category><![CDATA[Legal Issues]]></category>
		<category><![CDATA[Safeguards]]></category>

		<guid isPermaLink="false">http://www.hipaastore.com/info/?p=20</guid>
		<description><![CDATA[One of the least understood and most ignored requirements in HIPAA is called "Workforce Clearance" (WC). This "addressable" requirement is part of the Security Rule's Administrative Safeguards, and appears at 164.308(a)(3).


No related posts.

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p>One of the least understood and most ignored requirements in HIPAA is called &#8220;Workforce Clearance&#8221; (WC). This &#8220;addressable&#8221; requirement is part of the Security Rule&#8217;s Administrative Safeguards, and appears at <a title="Security Rule's Administrative Safeguard" href="http://www.bricker.com/legalservices/practice/hcare/hipaa/164.308.asp" target="_blank">164.308(a)(3)</a>.</p>
<blockquote><p><em>&#8220;Workforce clearance procedure (Addressable). Implement procedures to determine that the access of a workforce member to electronic protected health information is appropriate.&#8221;</em></p></blockquote>
<h3></h3>
<h3>A Danger and an Opportunity</h3>
<p>Hidden in these few words is one of the greatest dangers &#8211; and opportunities &#8211; for both Covered Entities and Business Associates. The danger and the opportunity both derive from the fact that many data breaches and thefts of PHI are perpetrated by <em>insiders</em>.</p>
<ul>
<li>Insiders at Tenet were recently charged with <a title="Insiders at Tenet charged with theft and HIPAA violations" href="http://www.healthleadersmedia.com/content/233655/topic/WS_HLM2_LED/Tenet-Employee-Charged-with-Theft-HIPAA-Violations.html" target="_blank">theft and HIPAA violations</a>.</li>
<li>A Johns Hopkins employee who worked in the hospital&#8217;s patient registration area was recently <a title="charged with fraud after stealing patient files" href="http://www.computerworld.com/s/article/9132860/Johns_Hopkins_tells_patients_Employee_stole_data_for_fraud" target="_blank">charged with fraud after stealing patient files</a>.</li>
<li>Kaiser Permanente&#8217;s Bellflower Hospital was recently <a title="Kaiser Permanente Fined 250K" href="http://latimesblogs.latimes.com/lanow/2009/05/nadya-suleman.html" target="_blank">fined $250,000</a> because employees were snooping into an octuplet mom&#8217;s (&#8220;Octomom&#8221;) medical records.</li>
</ul>
<p>The danger to CEs is that some trusted insider will be tempted to steal, sell, or hold Protected Health Information (PHI) hostage for personal gain. The opportunity is the chance to avoid HIPAA violations and bad publicity by making sure the people inside your entity are trustworthy and responsible.</p>
<h3>&#8220;Workforce Clearance&#8221; Really Means &#8220;Background Checks&#8221;</h3>
<p>In truth, many of these incidents might have been prevented if the entities involved had followed HIPAA&#8217;s &#8220;Workforce Clearance&#8221; requirement more strictly. The essence of Workforce Clearance is really background screening of employees, often referred to as &#8220;background checks.&#8221;</p>
<p>While many entities do perform some background screening for new hires, many entities do only a cursory check, and often with the lowest bidder. Unfortunately, this is a recipe for disaster.</p>
<h4>People with Problems are More Prone to Crime</h4>
<p>The simple fact is, people with criminal backgrounds and those with huge amounts of debt are more often involved in PHI thefts and breaches than those without such problems. And well-done background checks frequently identify high-risk individuals.</p>
<h4>Background Screening &#8211; Rule of Thumb</h4>
<p>A general rule of thumb is that the positions that carry the greatest responsibility should have the most intensive background checks. Positions such as IT Director, Senior Admin, Security Director, Medical Records Director and Manager should all have thorough background screening performed for applicants before they are hired. Some HIPAA entities are also re-screening workers in key positions periodically, to discover potential people problems in advance.</p>
<p><strong>Background screenings for critical positions should include:</strong></p>
<ul>
<li>Confirmation of previous employment history.</li>
<li>Multi-state, or nationwide criminal background checks.</li>
<li>Credit history reports.</li>
<li>Driving history and violation reports.</li>
</ul>
<h4>Don&#8217;t Cut Costs on Workforce Clearance</h4>
<p>While many CEs and BAs try to rein in costs by cutting back on background screening, the smartest entities are stepping up their use of background checks. They are moving to comply with HIPAA&#8217;s addressable &#8220;Workforce Clearance&#8221; requirement. They are also being smart, by reducing the risk from another &#8220;reasonably anticipated&#8221; threat to the PHI they are entrusted with.</p>


<p>No related posts.</p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.hipaastore.com/info/workforce-clearance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HIPAA Enforcement Is Heating Up!</title>
		<link>http://www.hipaastore.com/info/hipaa-enforcement/</link>
		<comments>http://www.hipaastore.com/info/hipaa-enforcement/#comments</comments>
		<pubDate>Sun, 23 Aug 2009 23:01:16 +0000</pubDate>
		<dc:creator>Abner</dc:creator>
				<category><![CDATA[HIPAA Compliance]]></category>
		<category><![CDATA[HIPAA Enforcement]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[enforcement]]></category>
		<category><![CDATA[HHS]]></category>
		<category><![CDATA[OCR]]></category>

		<guid isPermaLink="false">http://www.hipaastore.com/info/?p=18</guid>
		<description><![CDATA[CEa and BAa simply must get  their HIPAA "ducks in a row" as we approach 2010. The major provisions of the ARRA and the HITECH Act kick in on February 18th 2010, and HIPAA enforcement will continue to heat up. Be ready and be careful!


No related posts.

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p>After years of easy-going (some would say non-existent) enforcement, HIPAA enforcement finally appears to be heating up. Consider the following&#8230;</p>
<ul>
<li>HHS conducted it&#8217;s first-ever, on-site inspection for HIPAA compliance in March 2007 at Piedmont Hospital in Atlanta, Georgia.</li>
<li>In 2007 HHS granted new and expanded subpoena authority to the Office for Civil Rights to use in HIPAA violation investigations.</li>
<li>As of 2009, over 400 cases have now been referred to the US Department of Justice over possible criminal violations of HIPAA.</li>
<li>The 2009 HITECH Act, part of the ARRA, expanded HIPAA investigations and enforcement, to include, for the first time, mandatory investigations and penalties for cases involving &#8220;willful neglect&#8221;.</li>
<li><a title="HHS re-delegated HIPAA Security enforcement" href="http://www.hhs.gov/ocr/privacy/hipaa/administrative/srdelegationofauthoritytoocr.html" target="_blank">HHS re-delegated HIPAA Security enforcement</a> in August 2009, moving it from the CMS to the OCR. The OCR now handles investigations and enforcement for <em>both </em>the Privacy and Security Rules.</li>
<li>Announced August 2009, <a title="HHS is hiring more investigators" href="http://www.healthleadersmedia.com/content/237367/topic/WS_HLM2_PHY/Office-for-Civil-Rights-to-Hire-HIPAA-Privacy-Enforcers.html" target="_blank">HHS is hiring more investigators</a> to accommodate the growing number of <a title="HHS Complaints" href="http://www.cms.hhs.gov/Enforcement/11_HIPAAEnforcementStatistics.asp" target="_blank">complaints</a> and it&#8217;s new, combined Privacy and Security enforcement duties.</li>
</ul>
<p>Combine these with the ever-growing number of breaches, and the ARRA changes to HIPAA enforcement, and you have an blossoming enforcement situation every Covered Entity (CE) and Business Associate (BA) should be concerned about.</p>
<p>CEa and BAa simply must get  their HIPAA &#8220;ducks in a row&#8221; as we approach 2010. The major provisions of the ARRA and the HITECH Act kick in on February 18th 2010, and HIPAA enforcement will continue to heat up. Be ready and be careful!</p>


<p>No related posts.</p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.hipaastore.com/info/hipaa-enforcement/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Digital Devices Create Privacy Challenges</title>
		<link>http://www.hipaastore.com/info/digital-devices-privacy/</link>
		<comments>http://www.hipaastore.com/info/digital-devices-privacy/#comments</comments>
		<pubDate>Sun, 23 Aug 2009 22:31:38 +0000</pubDate>
		<dc:creator>Abner</dc:creator>
				<category><![CDATA[HIPAA Compliance]]></category>
		<category><![CDATA[HIPAA Security]]></category>
		<category><![CDATA[Patients & Consumers]]></category>
		<category><![CDATA[Digital Devices]]></category>
		<category><![CDATA[Legal Issues]]></category>
		<category><![CDATA[Safeguards]]></category>
		<category><![CDATA[Security Rule]]></category>

		<guid isPermaLink="false">http://www.hipaastore.com/info/?p=15</guid>
		<description><![CDATA[It seems like every new cellphone model these days comes with a camera. And many, like the Apple iPhone, also contain audio recorders. In fact, it's getting hard to find digital devices that don't record images, video, or audio. But for Covered Entities (CEs) and Business Associates (BAs) trying to protect PHI, these devices create serious privacy and security challenges.


No related posts.

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p>It seems like every new cellphone model these days comes with a camera. And many, like the Apple iPhone, also contain audio recorders. In fact, it&#8217;s getting hard to find digital devices that <em>don&#8217;t</em> record images, video, or audio. But for Covered Entities (CEs) and Business Associates (BAs) trying to protect PHI, these <a title="devices create serious privacy and security challenges" href="http://news.nurse.com/apps/pbcs.dll/article?AID=2008801280301" target="_blank">devices create serious privacy and security challenges</a>.</p>
<h2>&#8220;Reasonably Anticipated&#8221; Threats</h2>
<p><a title="HIPAA requires CEs and BAs to protect PHI against all " href="http://www.bricker.com/legalservices/practice/hcare/hipaa/164.306.asp" target="_blank">HIPAA requires CEs and BAs to protect PHI against all &#8220;reasonably anticipated&#8221; threats</a>. The problem is, many CEs and BAs <em>don&#8217;t know</em> how serious the &#8220;digital device&#8221; threat is to their PHI. On the other hand, HIPAA entities can&#8217;t claim that these threats couldn&#8217;t be &#8220;reasonably anticipated&#8221;, because this  issue is being covered in the general, technical and medical media increasingly often.</p>
<p>So what&#8217;s a concerned CE or BA to do?</p>
<h3>What Can Be Done?</h3>
<p><strong>The first step is to research the potential for abuse in your organization. You should be able to answer the following questions:</strong></p>
<ol>
<li>How and where are digital devices and recordings being used in your facility now?</li>
<li>How will you deal with employees and physicians&#8217; use of digital devices for recording images, video, and audio?</li>
<li>How will you deal with patients and visitors using these devices?</li>
<li>What are the legitimate recording uses, if any, for such devices in your facility?</li>
</ol>
<p>Based on the answers to these questions, you should create clear policies and guidance for the workforce, patients and visitors. Policies should be circulated to everyone and employee &#8220;sign-offs&#8221; should be obtained to establish workforce &#8220;agreement&#8221; to abide by the policies. Consider having patients sign a form laying out the rules and restrictions on recording with digital devices. And consider posting signs in patient and visitor areas that say &#8220;No Photography Allowed&#8221;,  &#8220;Recordings Prohibited&#8221;, or something similar.</p>
<h3>A Variety of Approaches</h3>
<p>CEs and BAs today are taking a variety of approaches to digital devices and the recordings they can produce, including:</p>
<ul>
<li>Banning all cameras, camera-phones, and audio recording devices from the premises. (Very hard to enforce.)</li>
<li>Banning digital devices from patient-care areas. (Easier to enforce, but still problematic.)</li>
<li>Establishing clear policies and restrictions on usage, but not banning the <em>physical presence</em> of relevant digital devices. (More realistic, but still difficult to enforce, as many devices are small and can be used surreptitiously.)</li>
<li>Ignoring the problem or deferring the issue till &#8220;later.&#8221; (The riskiest approach of all.)</li>
</ul>
<h3>No &#8220;Magic Bullet&#8221;</h3>
<p>There is no &#8220;magic bullet&#8221; solution for the privacy and security challenges posed by digital recording devices. Nevertheless, CEs and BAs <em>must attempt </em>to address these challenges somehow, even if only to demonstrate to a judge or jury &#8212; after a breach &#8212; that they were not guilty of &#8220;willful neglect&#8221;. Remember, <a title="HIPAA violations that involve " href="http://www.hospitalreviewmagazine.com/news-and-analysis/legal-and-regulatory/what-hospitals-need-to-know-about-the-arra-and-the-hipaa-updates.html" target="_blank">HIPAA violations that involve &#8220;willful neglect&#8221; carry new investigative and penalty requirements</a> under the recent ARRA expansion to HIPAA. Be careful!</p>


<p>No related posts.</p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.hipaastore.com/info/digital-devices-privacy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
