<?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>hipaaaudit.com</title>
	<atom:link href="http://hipaaaudit.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://hipaaaudit.com</link>
	<description>HIPAA Answers</description>
	<lastBuildDate>Mon, 14 May 2012 14:55:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Why You Should be Scared</title>
		<link>http://hipaaaudit.com/2012/05/14/why-you-should-be-scared/</link>
		<comments>http://hipaaaudit.com/2012/05/14/why-you-should-be-scared/#comments</comments>
		<pubDate>Mon, 14 May 2012 14:55:16 +0000</pubDate>
		<dc:creator>HIPAA Admin</dc:creator>
				<category><![CDATA[HIPAA Headlines]]></category>
		<category><![CDATA[Company Policy]]></category>
		<category><![CDATA[Computer Policy]]></category>
		<category><![CDATA[Data Theft]]></category>
		<category><![CDATA[Disaster Plan]]></category>
		<category><![CDATA[Hard Drive Encryption]]></category>
		<category><![CDATA[HIPAA Audit]]></category>
		<category><![CDATA[HIPAA Compliance]]></category>
		<category><![CDATA[HIPAA Policies]]></category>
		<category><![CDATA[HIPAA Risk Analysis]]></category>
		<category><![CDATA[Laptop Encryption]]></category>
		<category><![CDATA[Stolen data]]></category>

		<guid isPermaLink="false">http://hipaaaudit.com/?p=1485</guid>
		<description><![CDATA[Up to this point, most private practice physicians treat HIPAA compliance as&#8230;&#8221;something we&#8217;ll get to.&#8221; Most docs think their practice is compliant&#8230;they are wrong. I&#8217;ve mentioned before the threat of lawsuits and now this article. If this quote doesn&#8217;t send chills up your spine, then I don&#8217;t know what will: &#8220;“The privacy data breach area [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>Up to this point, most private practice physicians treat HIPAA compliance as&#8230;&#8221;something we&#8217;ll get to.&#8221;</p>
<p>Most docs <em>think</em> their practice is compliant&#8230;they are wrong.</p>
<p>I&#8217;ve mentioned before the threat of lawsuits and now <a title="HIPAA compliance policies" href="http://www.ctlawtribune.com/getarticle.aspx?ID=42168" target="_blank">this article</a>.</p>
<p>If this quote doesn&#8217;t send chills up your spine, then I don&#8217;t know what will:</p>
<blockquote><p><em>&#8220;“The privacy data breach area offers some <strong>new opportunities</strong> to expand the types of cases that we’re handling,” said Eric Grover, partner at the seven-lawyer California law firm Keller Grover.&#8221;</em></p></blockquote>
<p>So what should I do?</p>
<p>The first thing you need to do is accept the fact that HIPAA compliance is a reality<em>&#8230;</em>and that is a threat.  Next you need to stop looking at HIPAA compliance as this &#8220;BS red-tape government program&#8221; and accept that, like taxes, this isn&#8217;t going away.</p>
<p>Now, switch your thinking from &#8220;having to do this&#8221; to <em>How do I reduce my risk</em>?</p>
<p>Let me break this down as simple as I can:</p>
<ul>
<li>You need to do a risk assessment on your practice or you have no clue where you stand</li>
<li>You need to have current HIPAA policies in place or your staff doesn&#8217;t know where you stand</li>
<li>You need to ensure <a title="online hipaa training" href="http://hipaaaudit.com/2012/05/11/phone-phactory-reset/" target="_blank">HIPAA training</a> occurs on regular basis &#8211; along with HIPAA security reminders</li>
</ul>
<p>Take care of these first few items and everything will start falling into place.</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaaudit.com/2012/05/14/why-you-should-be-scared/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Phone Phactory Reset</title>
		<link>http://hipaaaudit.com/2012/05/11/phone-phactory-reset/</link>
		<comments>http://hipaaaudit.com/2012/05/11/phone-phactory-reset/#comments</comments>
		<pubDate>Fri, 11 May 2012 15:57:44 +0000</pubDate>
		<dc:creator>HIPAA Admin</dc:creator>
				<category><![CDATA[HIPAA Headlines]]></category>
		<category><![CDATA[Company Policy]]></category>
		<category><![CDATA[Computer Policy]]></category>
		<category><![CDATA[Data Theft]]></category>
		<category><![CDATA[HIPAA Compliance]]></category>
		<category><![CDATA[HIPAA Policies]]></category>
		<category><![CDATA[HIPAA Training]]></category>
		<category><![CDATA[Stolen data]]></category>

		<guid isPermaLink="false">http://hipaaaudit.com/?p=1480</guid>
		<description><![CDATA[If you haven&#8217;t seen the article in USA Today, it is a good wake up call for everyone. The short version of the story is this: Guy trades in old phone for new phone Guy didn&#8217;t remove his info from the old phone Store employee notices this and begin to make posts on Guy&#8217;s Facebook [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>If you haven&#8217;t seen the <a href="http://www.usatoday.com/tech/news/story/2012-05-04/facebook-best-buy-man-outed/54761236/1" target="_blank">article in USA Today</a>, it is a good wake up call for everyone.</p>
<p>The short version of the story is this:</p>
<ul>
<li>Guy trades in old phone for new phone</li>
<li>Guy didn&#8217;t remove his info from the old phone</li>
<li>Store employee notices this and begin to make posts on Guy&#8217;s Facebook page.</li>
</ul>
<p>Except for the fact that the posts made by the &#8220;imposter&#8221; were quite embarrassing to the Guy, no real harm was done.</p>
<h3>What could have been done?</h3>
<p>Many things could have been done.  Pictures sent out.  I&#8217;m sure the owner&#8217;s home address and of course all his contacts, were still in the phone.  He could have had his online banking info readily available.  If he was a physician, he might have had access to his EHR on the phone.</p>
<p>This can get real ugly real fast.</p>
<h3>How to prevent this?</h3>
<p>First, if you don&#8217;t password protect your phone, it is your fault.  The information in your phone is too valuable to NOT password protect your phone.  Typically being relieved of your phone is by your own choice, but theft of smart phones is huge right now, so you better password protect that phone.</p>
<p>Second, whether you are turning in your phone to a store or mailing it someone, heck even if giving it to your child, you need to accomplish a factory reset.  Each phone is different, but in general, in the settings area on your phone, there will be an option to reset your phone to factory settings.  This is kind of like reformatting a hard drive.  All you data will be gone.</p>
<p>Of course, someone with the right tools still may be able to grab information from the phone, which is why the best idea is to wipe the phone of all data using an app for that.</p>
<p>So Doc, a quick review:</p>
<ul>
<li>Password protect your phone&#8230;</li>
<li>Factory reset phone before turning in&#8230;</li>
<li>Use a phone wiping program before turning in.</li>
</ul>
<p>Realize this, your office should have a <a title="HIPAA computer policy" href="http://hipaaaudit.com/hipaa-products/hipaa-employee-computer-policy/" target="_blank">HIPAA policy</a> on this exact issue.  If you are using your phone for work at all, you better have a policy for what steps to take when a phone is stolen or turned in.</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaaudit.com/2012/05/11/phone-phactory-reset/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My PHI Breach Part 2</title>
		<link>http://hipaaaudit.com/2012/05/07/my-phi-breach-part-2/</link>
		<comments>http://hipaaaudit.com/2012/05/07/my-phi-breach-part-2/#comments</comments>
		<pubDate>Mon, 07 May 2012 13:28:16 +0000</pubDate>
		<dc:creator>HIPAA Admin</dc:creator>
				<category><![CDATA[HIPAA Headlines]]></category>
		<category><![CDATA[Company Policy]]></category>
		<category><![CDATA[Computer Policy]]></category>
		<category><![CDATA[Data Theft]]></category>
		<category><![CDATA[Hard Drive Encryption]]></category>
		<category><![CDATA[HIPAA Compliance]]></category>
		<category><![CDATA[HIPAA Policies]]></category>
		<category><![CDATA[HIPAA Risk Analysis]]></category>
		<category><![CDATA[HIPAA Training]]></category>
		<category><![CDATA[HIPAA Violations]]></category>
		<category><![CDATA[Stolen data]]></category>

		<guid isPermaLink="false">http://hipaaaudit.com/?p=1476</guid>
		<description><![CDATA[In part 1 of my PHI breach story I mentioned that I&#8217;d keep an update running, specifically that I&#8217;d write an update &#8220;in a few days&#8221;. Well, that didn&#8217;t happen. Mainly because after I filled out my paperwork and send it in&#8230;nothing has happened. I suppose this is a good thing. But this article reminded [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>In <a title="phi breach part 1" href="http://hipaaaudit.com/2011/11/22/my-phi-breach-part-1" target="_blank">part 1</a> of my PHI breach story I mentioned that I&#8217;d keep an update running, specifically that I&#8217;d write an update &#8220;in a few days&#8221;.</p>
<p>Well, that didn&#8217;t happen.</p>
<p>Mainly because after I filled out my paperwork and send it in&#8230;nothing has happened.</p>
<p>I suppose this is a good thing.</p>
<p>But <a title="tricare id theft" href="http://articles.boston.com/2012-05-05/nation/31574536_1_pentagon-contractor-privacy-and-identity-theft-personal-data" target="_blank">this article</a> reminded me of the situation.</p>
<p>First a quick reminder of what happened:</p>
<blockquote><p><em>&#8220;a Pentagon contractor left 25 computer tapes in the back seat of a Honda Civic in Texas&#8221;</em></p></blockquote>
<p>From this, upward of 70,000 people had their personal data stolen.</p>
<p>Obviously the main thing we focus on here is patient health information (PHI), but the reality is thieves are not really interested in the medical condition of the people on these tapes, no&#8230;they are interested in the identity theft value of these names.</p>
<p>It is the fact that there is a black market for people&#8217;s personal information so identity theft can occur that is typically the greater threat.</p>
<p>There are now 3 lawsuits regarding this data breach.</p>
<p>The deeper the pockets the more lawyers you attract&#8230;and you know that lawyers view doctors as having deep pockets.</p>
<p>Let&#8217;s take this to the local level now.</p>
<p>If you (or a business associate) have a data breach what do you need to do?  <a title="HITECH Act" href="http://www.hhs.gov/ocr/privacy/hipaa/administrative/breachnotificationrule/index.html" target="_blank">Section 13402</a> of the HITECH Act give the direction:</p>
<ul>
<li>Covered entities must notify affected individuals following the discovery of a breach of unsecured protected health information.</li>
<ul>
<li>must provide this individual notice in written form by first-class mail, or alternatively, by e-mail if the affected individual has agreed to receive such notices electronically.</li>
<li>IF you have out of date contact information for more than 10 individuals you must provide details by:</li>
<ul>
<li>Posting the details of your breach on the home page of your website, or</li>
<li>Provide the notice in major print or broadcast media where the affected individuals likely reside</li>
</ul>
</ul>
</ul>
<p>This is just the beginning (we haven&#8217;t even gotten into posting your breach in the HHS site), but let&#8217;s take a look a the scrutiny, ridicule and potential lawsuits you now opened yourself up to.</p>
<p><strong>Public Relations</strong>: there is no getting around the fact that a data breach is a public relations nightmare.  It is one thing to be a big &#8220;faceless&#8221; company when a breach happens, but when it is <em>your</em> practice in <em>your</em> town&#8230;everybody will know and everybody will be talking about this.</p>
<p><strong>Practice Value</strong>: I&#8217;m no expert in practice valuations, but I am confident that if you have a breach, the value of your practice will surely take a hit.</p>
<p><strong>Lawsuits</strong>: once word gets out that you have had a data breach, I imagine lawyers will be getting in line to sue you for damages.  So, piled upon the embarrassment is the cost of defending yourself in one, and potentially multiple lawsuits.</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaaudit.com/2012/05/07/my-phi-breach-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stolen Laptops and the Whole Ball of Wax</title>
		<link>http://hipaaaudit.com/2012/05/03/stolen-laptops-and-the-whole-ball-of-wax/</link>
		<comments>http://hipaaaudit.com/2012/05/03/stolen-laptops-and-the-whole-ball-of-wax/#comments</comments>
		<pubDate>Thu, 03 May 2012 15:27:11 +0000</pubDate>
		<dc:creator>HIPAA Admin</dc:creator>
				<category><![CDATA[HIPAA Headlines]]></category>
		<category><![CDATA[Company Policy]]></category>
		<category><![CDATA[Computer Policy]]></category>
		<category><![CDATA[Data Theft]]></category>
		<category><![CDATA[EHR]]></category>
		<category><![CDATA[Hard Drive Encryption]]></category>
		<category><![CDATA[HIPAA Compliance]]></category>
		<category><![CDATA[HIPAA Policies]]></category>
		<category><![CDATA[HIPAA Risk Analysis]]></category>
		<category><![CDATA[HIPAA Training]]></category>
		<category><![CDATA[HIPAA Violations]]></category>
		<category><![CDATA[Laptop Encryption]]></category>
		<category><![CDATA[Stolen data]]></category>
		<category><![CDATA[thumb drive encryption]]></category>

		<guid isPermaLink="false">http://hipaaaudit.com/?p=1471</guid>
		<description><![CDATA[Most of the time when I read a story on a stolen laptop, it is just the singular topic &#8211; Hey genius, if you encrypted your laptop this wouldn&#8217;t be an issue. The latest story I&#8217;ve come across pulls pieces in from multiple issues that a medical practice needs to consider.  Though the incident revolves [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>Most of the time when I read a story on a stolen laptop, it is just the singular topic &#8211; <em>Hey genius, if you encrypted your laptop this wouldn&#8217;t be an issue</em>.</p>
<p>The <a href="http://www.twincities.com/ci_20498186/july-theft-computer-fairview-patient-data-stolen-wasnt" target="_blank">latest story</a> I&#8217;ve come across pulls pieces in from multiple issues that a medical practice needs to consider.  Though the incident revolves around a hospital and a contractor, this same situation plays out daily at all sizes of private practices.</p>
<p>This all began, sort of, in the summer of 2011 when Fairview Health System of Minnesota hired a contractor from Chicago to work on some billing issues.</p>
<p>In 2010 this contractor had a laptop stolen from an employee&#8217;s car.  Fortunately this <a title="hipaa laptop encryption" href="http://hipaaaudit.com/hipaa-products/hard-drive-encryption/" target="_blank">laptop was encrypted</a>, granting them &#8220;safe harbor&#8221;, which simple means this incident does not need to be reported as the patient health information (PHI) is not readable.</p>
<p>Back to 2011 &#8211; this same contractor had another laptop stolen from another locked car.  The problem this time is the laptop was <strong>not encrypted</strong> &#8211; OOPS!  Now thousands of patients have to be notified along with the CMS.<em></em></p>
<blockquote><p><em>&#8220;During the theft in Minneapolis, an Accretive Health employee left his laptop in plain view of a thief who broke into the car and stole the computer, the report states. The laptop contained confidential data on about 23,000 patients of Fairview, North Memorial Health Care, as well as data from a hospital in Detroit.&#8221;</em></p></blockquote>
<p>Well, it turns out that this contractor has actually lost multiple laptops, enough in fact to catch the ear of a U.S. Senator who then got involved.</p>
<p>As you can see, this is not going well and I&#8217;m sure you wouldn&#8217;t want your practice to get sidetracked by this kind of issue.</p>
<p>This topic could easily turn into a multi-hour discussion, but here are the major issues from this story that concern every private practice physician AND how to deal with them:</p>
<ul>
<li><strong>Contractors</strong> &#8211; every contractor you hire that has any possible access to PHI should sign an <a title="hipaa associates agreement" href="http://hipaaaudit.com/hipaa-products/hipaa-associates-agreement/" target="_blank">Associates Agreement</a>.  This agreement should specify that if any PHI will be stored on a portable device, that entire device <em>must</em> be encrypted.</li>
<li><strong>Encryption</strong> &#8211; This is a no-brainer.  Every laptop in an office should be encrypted.</li>
<li><strong>Computer Policies</strong> &#8211; It is apparent from reading the article that the contractor did not have a clear policy as to how employees dealt with laptops.  To think management had to tell employees not to leave laptops in plain site of their car is scary.  As I always say, your <a title="HIPAA Computer policy" href="http://hipaaaudit.com/hipaa-products/hipaa-employee-computer-policy/" target="_blank">computer policy</a> is the foundation to the way your office operates.  If you are not crystal clear you will have problems.</li>
<li><strong>Whistle blowers</strong> &#8211; Note that much of the extra information about this contractor was via whistle blowers.  If you are not concerned about a whistle blower, you are kidding yourself.  Take a look at my recent <a title="HIPAA whistle blower" href="http://hipaaaudit.com/2012/04/26/hipaa-whistleblowers/">whistle blower article</a> and don&#8217;t be ignorant enough to dismiss it.</li>
</ul>
<p>Most major HIPAA issues are easy to fix, but they are not always simple to implement.  Without a clear set of policies your office is heading down the road to disaster.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaaudit.com/2012/05/03/stolen-laptops-and-the-whole-ball-of-wax/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google is Dangerous</title>
		<link>http://hipaaaudit.com/2012/04/30/google-is-dangerous/</link>
		<comments>http://hipaaaudit.com/2012/04/30/google-is-dangerous/#comments</comments>
		<pubDate>Mon, 30 Apr 2012 14:17:31 +0000</pubDate>
		<dc:creator>HIPAA Admin</dc:creator>
				<category><![CDATA[HIPAA Headlines]]></category>
		<category><![CDATA[Company Policy]]></category>
		<category><![CDATA[Computer Policy]]></category>
		<category><![CDATA[EHR]]></category>
		<category><![CDATA[Google Drive]]></category>
		<category><![CDATA[HIPAA Audit]]></category>
		<category><![CDATA[HIPAA Compliance]]></category>
		<category><![CDATA[HIPAA Policies]]></category>
		<category><![CDATA[HIPAA Risk Analysis]]></category>

		<guid isPermaLink="false">http://hipaaaudit.com/?p=1464</guid>
		<description><![CDATA[This is for the paranoid out there, and if you are a physician, you need to be paranoid about how your practice handles patient health information (PHI). Cloud computing is the hip, in-thing right now. Cloud storage is where things can get tricky&#8230;note: you better have a HIPAA office policy on this matter. What is [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>This is for the paranoid out there, and if you are a physician, you need to be paranoid about how your practice handles patient health information (PHI).</p>
<p>Cloud computing is the hip, in-thing right now.</p>
<p>Cloud storage is where things can get tricky&#8230;note: you better have a <a href="http://hipaaaudit.com/hipaa-products/hipaa-employee-computer-policy/">HIPAA office policy</a> on this matter.</p>
<h2>What is Cloud Storage?</h2>
<p>At its most basic level, cloud storage makes it very easy to share documents among staff and computers by creating a &#8220;virtual hard drive&#8221; that many people can access.</p>
<p>Google&#8217;s version of cloud storage is called Google Drive.</p>
<p>Whether or not you believe Google is trying to take over the world by having as much knowledge as possible, you can&#8217;t ignore some recent issues.</p>
<p>First, let me say this: You should not store any PHI in a system like Google Drive.  Also, I don&#8217;t think it is smart business either.</p>
<h2>So, What is the Problem?</h2>
<p>The real problem is the creeping of privacy guidelines by Google.  What starts as &#8220;we don&#8217;t look at your data&#8221; over time becomes something quite different.</p>
<p>Take for example this latest bit of info: Google is currently going through more drama about gathering personal information.  This current hoo-ha is based around the issue that when Google&#8217;s cars that drive around the world mapping everything, they also connect to unsecured WiFi networks and gather whatever data they can.</p>
<p>So, now you want to store your business information on Google hard drives?</p>
<p>Bad idea for HIPAA compliance.</p>
<p>Not a smart business decision.</p>
<h2>But my EHR is Cloud Based</h2>
<p>Apples &amp; Oranges my friend.  The fact that your electronic health records (EHR) system is cloud based &#8211; also called web-based or Software as a Service (SaaS) is completely different.  Though, something to realize &#8211; many free EHRs will mine your patient data.  This may not be anything you really care about, but de-personalized patient health information (PHI) can be quite valuable for research.  Many physicians who have a server based EHR get paid to allow research institutions to mine their patient data.</p>
<h2>What About Off Site Backup?</h2>
<p>Also different&#8230;.usually.  If you are using an <a href="http://hipaaaudit.com/hipaa-products/hipaa-compliant-computer-backup/" target="_blank">off site backup service</a>, you must ensure they are HIPAA compliant.  No data should leave your property that isn&#8217;t completely encrypted &#8211; this also prevents unwanted data mining.</p>
<p>The moral of this story is, the easiest solution tends NOT to be HIPAA compliant.</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaaudit.com/2012/04/30/google-is-dangerous/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

