<?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>Crazy Like That Blog &#187; HIPAA</title>
	<atom:link href="http://www.crazylikethat.com/blog/tag/hipaa/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.crazylikethat.com/blog</link>
	<description>There is a fine line between extreme intelligence and insanity</description>
	<lastBuildDate>Tue, 20 Jul 2010 21:58:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Web Development: Avoiding HIPAA Issues</title>
		<link>http://www.crazylikethat.com/blog/2009/12/web-development-avoiding-hipaa-issues/</link>
		<comments>http://www.crazylikethat.com/blog/2009/12/web-development-avoiding-hipaa-issues/#comments</comments>
		<pubDate>Tue, 29 Dec 2009 03:23:32 +0000</pubDate>
		<dc:creator>5x5</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[golf]]></category>
		<category><![CDATA[HIPAA]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://www.crazylikethat.com/blog/?p=502</guid>
		<description><![CDATA[As a web developer, you need to be aware of the line between allowing patients to share information by way of support groups or testimonial and having private information displaying on the Internet. ]]></description>
			<content:encoded><![CDATA[<div id="attachment_503" class="wp-caption alignleft" style="width: 330px"><img class="size-full wp-image-503 " title="geener-days" src="http://www.crazylikethat.com/blog/wp-content/uploads/2009/12/geener-days.png" alt="Green Days' Website" width="320" height="120" /><p class="wp-caption-text">Green Days&#39; Website</p></div>
<p>The Health Insurance Portability and Accountability Act (<a title="HIPAA" href="http://www.hhs.gov/ocr/privacy/">HIPPA</a>) regulates health information and ensures your private health information does not end up in the hands of people you don&#8217;t wish to have it.</p>
<p>As a web developer, you need to be aware of the line between allowing patients to share information by way of support groups or testimonial and having private information displaying on the Internet.   Let&#8217;s use a fictitious Greener Day Vasectomy Clinic as an example.  After having a procedure performed, doctors at Greener Day ask their patients to check-in on a yearly basis to ensure there have been no slip-ups with the procedure.  At the bottom of the form, patients are given the option to share their message with other patients.  This is a great opportunity for patients to give each other support like, &#8220;You go tiger!&#8221;, but it also opens them to a disaster waiting to happen with private information only meant for the doctor, &#8220;I slept with 14 women in the past year and not one got pregnant! t14@happygolfer.com&#8221;, to end up in the public domain.</p>
<div id="attachment_506" class="wp-caption alignleft" style="width: 410px"><img class="size-full wp-image-506" title="greener-day-sample" src="http://www.crazylikethat.com/blog/wp-content/uploads/2009/12/greener-day-sample.png" alt="Dangerous territory" width="400" height="127" /><p class="wp-caption-text">Dangerous territory</p></div>
<p><strong>Tips for playing it safe:</strong></p>
<p>1) Do not include items for testimonials or sharing type information on any page where a patient will be submitting information to the doctor.  These pages need to be secure and transmitted to the doctor in an encrypted manner. Either separate the pages or if patients select &#8220;yes&#8221;, meaning they wish to share information, take them to a second page, restating the information shared on that page will be public. This will prevent information a patient never wanted to share from becoming public due to hurrying through a form or forgetting to click &#8220;No&#8221;.</p>
<p>2) If clients are sharing testimonials, do not display their e-mail address or other contact information in the page.  While they may have agreed to say good things about your company, they probably did not agree to have their e-mail out there for every spam bot in the universe to pick up.</p>
<p>3) When collecting patient information, do not automatically generate a &#8220;hidden&#8221; web page for each submission.  There might not be any direct links off the website going to it, but search engines and any cracker trying to dig around the site can still find the information.</p>
<p>4) Avoid short cuts if they threaten privacy.  Having everything in one form might be convenient for the web developer, but if it opens any chance for private information to accidentally become public, scratch it and rethink it.</p>
<p>5) Do not rely on robots.txt to keep information private.</p>
<p>6) If you really want something to be kept private, do not store the information on any computer that is connected to the Internet.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.crazylikethat.com/blog/2009/12/web-development-avoiding-hipaa-issues/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
