<?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/"
	>

<channel>
	<title>HIPAA Email</title>
	<atom:link href="http://hipaaemail.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://hipaaemail.com</link>
	<description></description>
	<pubDate>Wed, 14 Dec 2011 22:17:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Solar Phone Charger - For HIPAA &amp; Other Uses</title>
		<link>http://hipaaemail.com/solar-phone-charger-for-hipaa-other-uses/</link>
		<comments>http://hipaaemail.com/solar-phone-charger-for-hipaa-other-uses/#comments</comments>
		<pubDate>Wed, 14 Dec 2011 22:17:54 +0000</pubDate>
		<dc:creator></dc:creator>
		
		<category><![CDATA[Green Power]]></category>

		<guid isPermaLink="false">http://hipaaemail.com/?p=41</guid>
		<description><![CDATA[


With a solar phone charger you can keep the power coming throughout the day to your cell phone. I remember when there were no cell phones. Once you left the house no one could get a hold of you until you returned home. Those days are certainly long gone and I am definitely dating myself. [...]]]></description>
			<content:encoded><![CDATA[<p>With a solar phone charger you can keep the power coming throughout the day to your cell phone. I remember when there were no cell phones. Once you left the house no one could get a hold of you until you returned home. Those days are certainly long gone and I am definitely dating myself. Today, we cannot live without having our phones with us 24/7 it seems, at least for a large number of the population. Anywhere you go there are people using their cell phones.</p>
<p>Keeping these cell phones charged for when you want to use them can be a challenge. If you are out and about you either have to limit yourself on the phone or have a car charger or a solar phone charger with you. The problem with the car charger is that you can only use it while in the car. The solar one though, you can carry with you. You can have it wherever you go.</p>
<p>Some of the chargers come in the way of phone cases. They protect the phones from getting harmed. A solar panel is also installed on the back cover of the case. When the sunlight hits the panel it generates a charge for the phone. These come in a variety of colors to suit your taste. Black, white, blue and green are available the last I checked anyway.</p>
<p>Other styles of solar chargers also can charge the phones. There are bags and backpacks that will handle charging certain phones. These both contain panels on them to collect the sun&#8217;s energy. Just place the phone in these bags or backpacks according to the enclosed instructions, and as you carry them around the phone will charge.</p>
<p>A solar phone charger can come in the form of a solar vest. This vest will charge many of your portable electronics including cell phones. These are usually bright colored and are worn for a variety of reasons, one profession that wears them are construction workers, who aren&#8217;t always near an electrical outlet.</p>
<p>There are some compact solar panels that can be hooked to your cell phone. These come in a variety of sizes and styles. It is amazing how far the solar panel has progressed. It used to just be big and bulky, now it can even be small and lightweight.</p>
<p>Whichever of these choices of the solar phone charger you choose; you will have power all day long for your communication needs. You won&#8217;t miss any important calls and you will be able to answer any and all text messages you get. This heightens your cell-phone experience. It is also safer to always have a charge on your phone in case of emergencies. Just think if the car stalls out and you need a tow, or you have a medical emergency and have to call one of the relatives about it. Don&#8217;t you want the cell phone charged and ready to use? Of course you do!</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaemail.com/solar-phone-charger-for-hipaa-other-uses/feed/</wfw:commentRss>
		</item>
		<item>
		<title>HIPPA, Email Archiving, and Web Design</title>
		<link>http://hipaaemail.com/hippa-email-archiving-and-web-design/</link>
		<comments>http://hipaaemail.com/hippa-email-archiving-and-web-design/#comments</comments>
		<pubDate>Wed, 04 May 2011 11:16:28 +0000</pubDate>
		<dc:creator></dc:creator>
		
		<category><![CDATA[Web Design]]></category>

		<category><![CDATA[email]]></category>

		<category><![CDATA[email laws]]></category>

		<category><![CDATA[hipaa]]></category>

		<category><![CDATA[hipaa email]]></category>

		<category><![CDATA[hipaa laws]]></category>

		<category><![CDATA[news]]></category>

		<category><![CDATA[tech]]></category>

		<category><![CDATA[tech news]]></category>

		<guid isPermaLink="false">http://hipaaemail.com/?p=37</guid>
		<description><![CDATA[


Including Usability In The Web Design Process
Whether you want a website for a personal project or as part of a  business venture, the process of web design is critically important. The  idea, of course, is for the end result to be an attractive, fully  functional website which attracts visitors and in the [...]]]></description>
			<content:encoded><![CDATA[<h3>Including Usability In The Web Design Process</h3>
<p>Whether you want a website for a personal project or as part of a  business venture, the process of <a href="http://www.rtdesigngroup.com/orlando-web-design/">web design</a> is critically important. The  idea, of course, is for the end result to be an attractive, fully  functional website which attracts visitors and in the case of business  oriented sites, customers. Part of designing an effective website is to  pay close attention throughout the design process to the goal of making  the site user-friendly; if your site isn&#8217;t easy for visitors to navigate  and find the content or access the functions they&#8217;re looking for,  they&#8217;ll be looking elsewhere.</p>
<p>If you&#8217;d like to learn more about making your website easier to use  and a generally more inviting destination for visitors, read on. Whether  you&#8217;re building a new website from the ground up or if you&#8217;d like to  make some changes to an existing website to enhance its usability, the  suggestions below can help you to make your site more appealing to users  and thus, more successful overall.</p>
<p><strong>Be Concise:</strong></p>
<p>Your site needs to communicate clearly and quickly to visitors in both <a href="http://en.wikipedia.org/wiki/Web_design">design</a>, <a href="http://www.archivecompliance.com/20110502107/Press-Releases/Top-Myths-of-Email-Archiving.html">email archiving</a>, and <a href="http://www.hhs.gov/ocr/privacy/">HIPAA</a>.  People are impatient, especially when they&#8217;re online. With literally  millions of other websites out there to visit, if you take too long to  get your point across, you&#8217;ve lost your visitors; and if your website is  part of your business, this means that you&#8217;ve lost them to your  competitors.</p>
<p>Tell your visitors what they need to know without unnecessary  padding; they&#8217;ll appreciate that you get right to the point and will be  more likely to return for repeat visits. If your site is a ecommerce  site, make sure that the checkout process is quick and easy and that any  forms that customers need to fill out are as short as possible. The  longer it takes them to complete the process, the more likely they are  to decide to take their business elsewhere.</p>
<p><strong>Clarity and Intuitive Navigation:</strong></p>
<p>Apply what is known as the &#8220;alien test&#8221; to your website. Imagine that  you are an alien visitor who just landed on the planet; can you look at  your website and tell in 10 seconds or less what it&#8217;s all about?</p>
<p>The point of this test is to show the importance of making your site  as self explanatory and easy to understand as possible. Your visitors  should know at a glance what your site offers and how to find what  they&#8217;re looking for.  This refers to both the content on your site,  which should be as clear as possible and your site&#8217;s navigation, which  should be equally straightforward. Include a navigation bar on every  page with clearly labeled links to the pages and other content on your  site which your visitors want. If visitors can&#8217;t figure out quickly  where to find the information they&#8217;re looking for or your site is  difficult and confusing to navigate, they&#8217;re not going to stick around  for long.</p>
<p><strong>Content:</strong></p>
<p>Content isn&#8217;t a matter of web design in the strictest sense, but it  is so important to your <a href="http://www.thoughtmechanics.com/">Dallas Web Design</a> site&#8217;s usability and its ability to draw  visitors that it should be given the same kind of attention and care.  Content is king on the web, just as it always has been and having well  written content on topics which are relevant to your visitors can go a  long way towards helping you attract an audience, especially through  organic search engine optimization. You don&#8217;t need to flood your site  with content, but adding some new and informative pieces to your site on  occasion can help to drive traffic as well as making your site more  useful to your readers.</p>
<p><strong>Security and privacy:</strong></p>
<p>Consumers are becoming more savvy about online security and  especially if you have an ecommerce site, you need to pay a lot of  attention to ensuring that your site is secure enough that visitors will  feel comfortable doing business there. Even if your site is not overtly  commercial, your visitors want to know that their privacy is as  important to you as it is to them; unless you have a legitimate reason  for doing so, don&#8217;t ask your visitors to give out personal information  or you may risk losing them. If you&#8217;re selling something, your visitors  will be willing to share contact information with you once they decide  to make a purchase from you - no one is too eager to give out this kind  of information unless they need to, even if your site&#8217;s security is  impeccable.</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaemail.com/hippa-email-archiving-and-web-design/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Benefits of an In-house Email Archiving Solution</title>
		<link>http://hipaaemail.com/benefits-of-an-in-house-email-archiving-solution/</link>
		<comments>http://hipaaemail.com/benefits-of-an-in-house-email-archiving-solution/#comments</comments>
		<pubDate>Fri, 15 Apr 2011 05:15:42 +0000</pubDate>
		<dc:creator></dc:creator>
		
		<category><![CDATA[hipaa email]]></category>

		<category><![CDATA[archive emails]]></category>

		<category><![CDATA[email archive]]></category>

		<category><![CDATA[email archiving]]></category>

		<category><![CDATA[emails]]></category>

		<category><![CDATA[hipaa]]></category>

		<category><![CDATA[hipaa emails]]></category>

		<guid isPermaLink="false">http://hipaaemail.com/?p=34</guid>
		<description><![CDATA[

Much is said about the relative benefits of cloud computing. The ability to offload the responsibility of maintaining IT infrastructures, email archiving, system upgrades, patching and IT departments is an attractive one. But it isn’t necessarily the right one.
Software as a Service (SaaS) makes a compelling case for using cloud computing to solve many computing [...]]]></description>
			<content:encoded><![CDATA[<p><center><script type="text/javascript"><!--
google_ad_client = "pub-2986691626316353";
/* 468x60, created 2/5/10 */
google_ad_slot = "5257352844";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></center></p><p><!--[if gte mso 9]><xml> <o:OfficeDocumentSettings> <o:AllowPNG /> </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val=" " /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--><!--[if gte mso 10]><br />
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:10.0pt;
	mso-para-margin-left:0in;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
</style>
<p> <![endif]--></p>
<h1></h1>
<p class="MsoNormal"><span>Much is said about the relative benefits of cloud computing. The ability to offload the responsibility of maintaining IT infrastructures, email archiving, system upgrades, patching and IT departments is an attractive one. But it isn’t necessarily the right one.</span></p>
<p class="MsoNormal"><span>Software as a Service (<a href="http://www.saas.com/ta/hp.jsp">SaaS</a>) makes a compelling case for using cloud computing to solve many computing problems. There is a low startup cost, monthly billing, low overheads, and reliable systems. It turns what is a considerable investment into an annualized cost. However, it isn’t for everybody. Large organizations with existing infrastructures will benefit little from offloading some services to outside vendors. </span></p>
<p class="MsoNormal"><span>There are two main advantages for keeping the <a href="https://www.smarsh.com/">email archive</a> in-house. Security and convenience.</span></p>
<p class="MsoNormal"><span>Security is a consideration for all of us. It has been the most-used term in our country since 9/11. In this context is was Enron that caused the word to be used around business, and particularly, email. It wasn’t the only high profile case in Wall Street that caused scandal, but it was the highest profile one.</span></p>
<p class="MsoNormal"><span>You don’t have to deal in PFI or financial data to need an effective email archiving system nowadays. <a href="http://www.law.cornell.edu/rules/frcp/">FRCP</a>, <a href="http://sox.sourceforge.net/">SOX</a>, <a href="http://www.hhs.gov/ocr/privacy/">HIPAA</a> and <a href="http://www.hhs.gov/ocr/privacy/">FINRA</a> are only four of many pieces of legislation that demand businesses from all industries maintain a coherent email archiving system in order to facilitate court proceedings.</span></p>
<p class="MsoNormal"><span>Email data has become the new DNA evidence in civil and criminal litigation. Some e-discovery requests are fishing trips, some are to procure evidence, others are just for the sake of it. Whatever the motive behind them, companies still have to comply within a short space of time. </span></p>
<p class="MsoNormal"><span>Many companies don’t want to offload that responsibility to a third-party. They want to maintain their own email security, and control how, when and where their email data is archived and stored.</span></p>
<p class="MsoNormal"><span>Convenience should not be understated. The ability to integrate an email archive into an existing system is a great convenience. It means it can run in tandem with other services, piggy-back the network, be stored locally, and within the security confines of a secure network.</span></p>
<p class="MsoNormal"><span>It’s also useful to have your own people, people you trust, manage and monitor your company’s email traffic. That’s true of any company, not just those who are transmitting secure emails or proprietary information over networks.</span></p>
<p class="MsoNormal"><span>Some companies just want to control everything that goes on within their environment. That may not necessarily be for any specific reason, just because they can, or want to. That’s a laudable reason, as long as the email archive works, and abides by the appropriate legislation. It contains a significant overhead in time, money and resources, but some companies are more comfortable than others expending it.</span></p>
<p class="MsoNormal"><span>The ability to completely control your own email traffic, manage your own email archive and satisfy any e-discovery request is an overriding factor in many decisions to manage email in-house. After all, when the buck stops with you, you may as well control the outcome first.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaemail.com/benefits-of-an-in-house-email-archiving-solution/feed/</wfw:commentRss>
		</item>
		<item>
		<title>HIPAA requirements, safeguards, and laws.</title>
		<link>http://hipaaemail.com/hipaa-requirements-safeguards-and-laws/</link>
		<comments>http://hipaaemail.com/hipaa-requirements-safeguards-and-laws/#comments</comments>
		<pubDate>Mon, 08 Jun 2009 20:28:25 +0000</pubDate>
		<dc:creator></dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[hipaa]]></category>

		<category><![CDATA[hipaa laws]]></category>

		<category><![CDATA[hipaa rules]]></category>

		<guid isPermaLink="false">http://hipaaemail.com/?p=32</guid>
		<description><![CDATA[Below are the administrative and physical safeguards as outlined in the Federal Register. These requirements are items that must generally be addressed internally, even if you are outsourcing your email.



Standard:  ADMINISTRATIVE SAFEGUARDS
Sections
Implementation Specification
Required or Addressable


Security Management Process
164.308(a)(1)
Risk Analysis
R




Risk Management
R




Sanction Policy
R




Information System Activity Review
R


Assigned Security Responsibility
164.308(a)(2)

R


Workforce Security
164.308(a)(3)
Authorization and/or Supervision
A




Workforce Clearance Procedures
R




Termination Procedures
A


Information Access Management
164.308(a)(4)
Isolating Health [...]]]></description>
			<content:encoded><![CDATA[<p>Below are the administrative and physical safeguards as outlined in the Federal Register. These requirements are items that must generally be addressed internally, even if you are outsourcing your email.</p>
<table border="1" cellspacing="0" cellpadding="3" width="100%">
<tbody>
<tr valign="top" bgcolor="#eeeeee">
<td><strong>Standard:  ADMINISTRATIVE SAFEGUARDS</strong></td>
<td><strong>Sections</strong></td>
<td><strong>Implementation Specification</strong></td>
<td><strong>Required or Addressable</strong></td>
</tr>
<tr valign="top">
<td>Security Management Process</td>
<td>164.308(a)(1)</td>
<td>Risk Analysis</td>
<td>R</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Risk Management</td>
<td>R</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Sanction Policy</td>
<td>R</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Information System Activity Review</td>
<td>R</td>
</tr>
<tr valign="top">
<td>Assigned Security Responsibility</td>
<td>164.308(a)(2)</td>
<td></td>
<td>R</td>
</tr>
<tr valign="top">
<td>Workforce Security</td>
<td>164.308(a)(3)</td>
<td>Authorization and/or Supervision</td>
<td>A</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Workforce Clearance Procedures</td>
<td>R</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Termination Procedures</td>
<td>A</td>
</tr>
<tr valign="top">
<td>Information Access Management</td>
<td>164.308(a)(4)</td>
<td>Isolating Health Care Clearinghouse Function</td>
<td>R</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Access Authorization</td>
<td>A</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Access Establishment and Modification</td>
<td>A</td>
</tr>
<tr valign="top">
<td>Security Awareness and Training</td>
<td>164.310(a)(5)</td>
<td>Security Reminders</td>
<td>A</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Protection from Malicious Software</td>
<td>A</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Log-in Monitoring</td>
<td>A</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Password Management</td>
<td>A</td>
</tr>
<tr valign="top">
<td>Security Incident Procedures</td>
<td>164.308(a)(6)</td>
<td>Response and Reporting</td>
<td>R</td>
</tr>
<tr valign="top">
<td>Contingency Plan</td>
<td>164.308(a)(7)</td>
<td>Data Backup Plan</td>
<td>R</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Disaster Recovery Plan</td>
<td>R</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Emergency Mode Operation Plan</td>
<td>R</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Testing and Revision Procedure</td>
<td>A</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Applications and Data Criticality Analysis</td>
<td>A</td>
</tr>
<tr valign="top">
<td>Evaluation</td>
<td>164.308(a)(8)</td>
<td></td>
<td>R</td>
</tr>
<tr valign="top">
<td>Business Associates Contracts and Other Arrangement.</td>
<td>164.308(b)(1)</td>
<td>Written Contract or Other Arrangement</td>
<td>R</td>
</tr>
<tr valign="top" bgcolor="#dddddd">
<td><strong>Standard:  PHYSICAL SAFEGUARDS</strong></td>
<td><strong>Sections</strong></td>
<td><strong>Implementation Specification</strong></td>
<td><strong>Required or Addressable</strong></td>
</tr>
<tr valign="top">
<td>Facility Access Controls</td>
<td>164.310(a)(1)</td>
<td>Contingency Operations</td>
<td>A</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Facility Security Plan</td>
<td>A</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Access Control and Validation Procedures</td>
<td>A</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Maintenance Records</td>
<td>A</td>
</tr>
<tr valign="top">
<td>Audit Controls</td>
<td>164.312(b)</td>
<td></td>
<td>R</td>
</tr>
<tr valign="top">
<td>Integrity</td>
<td>164.312(c)(1)</td>
<td>Mechanism to Authenticate EPHI</td>
<td>A</td>
</tr>
<tr valign="top">
<td>Workstation Use</td>
<td>164.310(b)</td>
<td></td>
<td>R</td>
</tr>
<tr valign="top">
<td>Workstation Security</td>
<td>164.310(c)</td>
<td></td>
<td>R</td>
</tr>
<tr valign="top">
<td>Device and Media Controls</td>
<td>164.310(d)</td>
<td>Disposal</td>
<td>R</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Media Re-use</td>
<td>R</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Accountability</td>
<td>A</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Data Backup and Storage</td>
<td>A</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://hipaaemail.com/hipaa-requirements-safeguards-and-laws/feed/</wfw:commentRss>
		</item>
		<item>
		<title>How to make a complaint</title>
		<link>http://hipaaemail.com/how-to-make-a-complaint/</link>
		<comments>http://hipaaemail.com/how-to-make-a-complaint/#comments</comments>
		<pubDate>Wed, 27 May 2009 20:40:16 +0000</pubDate>
		<dc:creator></dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[complaints]]></category>

		<category><![CDATA[email hipaa]]></category>

		<category><![CDATA[hipaa]]></category>

		<category><![CDATA[hipaa complaint]]></category>

		<guid isPermaLink="false">http://hipaaemail.com/?p=29</guid>
		<description><![CDATA[If it is believed privacy rights have been violated by an HIPAA covered entity then patients have the right to complain about it.  A little research is necessary before filing a complaint is necessary to ensure the organization or individual believed contravened these rights are subject to HIPAA, and is a covered entity.
Once it has [...]]]></description>
			<content:encoded><![CDATA[<p><img class="size-full wp-image-30 alignleft" style="margin-left: 8px; margin-right: 8px;" title="complaint" src="http://hipaaemail.com/wp-content/uploads/2009/05/complaint.jpg" alt="complaint" width="307" height="425" />If it is believed privacy rights have been violated by an HIPAA covered entity then patients have the right to complain about it.  A little research is necessary before filing a complaint is necessary to ensure the organization or individual believed contravened these rights are subject to HIPAA, and is a covered entity.</p>
<p>Once it has been ascertained that a covered entity has indeed broken the privacy rules then a complaint needs to be filed with the Office for Civil Rights.  The complaint must be in writing, but may be in email form or fax if preferred, and be sent to the correct regional office.  It must name the entity involved and contain a complete and lucid description of events and the reason why the rules have been broken.  A complainant has one hundred eighty days from the day of the incident to be accepted by the Office for Civil rights.</p>
<p>The complainant should not be scared of complaining if they firmly believe their rights have been contravened.  There is a specific clause in the rules that prohibit any kind of retaliation for filing a complaint.  If the Office for Civil Rights get to hear about any retaliations, they take a very dim view and the entity involved can get themselves into real trouble.</p>
<p>A good first step for any complainant is the Office for Civil Rights website where as much information as possible has been posted, and there is a complaint pack with guidance on how to complete it.  Some entities like Universities and some hospitals have their own HIPAA complaint procedures.  A complainant can choose which body to complain to, but if the entity itself is contacted it must be given adequate time to investigate and address the issue before complaining to the Office of Civil Rights.</p>
<p>As with any bureaucracy it will take time to process any complaint so this should be borne in mind once the complaint is made.  Adequate time must be allowed to pass to ensure the OCR can do its job.</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaemail.com/how-to-make-a-complaint/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The practicality of sharing PHI</title>
		<link>http://hipaaemail.com/the-practicality-of-sharing-phi/</link>
		<comments>http://hipaaemail.com/the-practicality-of-sharing-phi/#comments</comments>
		<pubDate>Wed, 27 May 2009 20:33:36 +0000</pubDate>
		<dc:creator></dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[hipaa]]></category>

		<category><![CDATA[hipaa email]]></category>

		<category><![CDATA[phi]]></category>

		<guid isPermaLink="false">http://hipaaemail.com/?p=26</guid>
		<description><![CDATA[There will be circumstances when it is necessary to share PHI with a patient’s family and friends.  This is permitted under the HIPAA as long as the information is needed, and pertinent to the ongoing care of the patient.
Practical examples would be if a patient’s family are waiting in an ER or outside an operating [...]]]></description>
			<content:encoded><![CDATA[<p>There will be circumstances when it is necessary to share PHI with a patient’s family and friends.  This is permitted under the HIPAA as long as the information is needed, and pertinent to the ongoing care of the patient.</p>
<p>Practical examples would be if a patient’s family are waiting in an ER or outside an operating theatre and the doctor or surgeon wants to update them on the patient’s condition, treatment or medical procedure.</p>
<p>Or if a patient is being looked after by a friend or family member, they are going to need to know the condition and types of care needed.  For example the type of medication, or particular type of care.  Any symptoms or side affects to be aware of, or how to provide a certain treatment at home.</p>
<p>These kinds of things are practical to the continued care and wellbeing of the patient and are permitted to be shared with (generally designated) family and friends.  These circumstances do not necessarily need the patients consent either.  In some circumstances the patient may not be able to offer their consent, if they are incapacitated or unfit.  The medical personnel are then permitted to make a judgement call of what information to share and with whom to share it.</p>
<p>There are also permitted discussions and use of PHI if a family member or friend is assisting or arranging payment for the treatment.  Some sharing of the medical information is going to be necessary to justify the bill, or allow the person to involve the insurance company.  Again, a good practical reason for sharing the information allowed under HIPAA.</p>
<p>So although the HIPAA is fairly stringent in controlling access to PHI, it tries to add a practical approach to how it handles things.  It is designed to protect the information as much as possible while not interfering with the actual care of the patient.</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaemail.com/the-practicality-of-sharing-phi/feed/</wfw:commentRss>
		</item>
		<item>
		<title>State Law or HIPAA?</title>
		<link>http://hipaaemail.com/state-law-or-hipaa/</link>
		<comments>http://hipaaemail.com/state-law-or-hipaa/#comments</comments>
		<pubDate>Wed, 27 May 2009 20:30:45 +0000</pubDate>
		<dc:creator></dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[hipaa state law]]></category>

		<category><![CDATA[hipaa states]]></category>

		<category><![CDATA[state hipaa law]]></category>

		<category><![CDATA[state law]]></category>

		<category><![CDATA[state laws]]></category>

		<category><![CDATA[states hipaa]]></category>

		<guid isPermaLink="false">http://hipaaemail.com/?p=22</guid>
		<description><![CDATA[If State law and HIPAA got into a fight, who would win?
As a general guide, the law that offers the most protection to the patient in question wins.  The whole idea of HIPAA is to increase the privacy of medical records.  It doesn’t always succeed in its aims, but that’s beside the point.
There are clauses [...]]]></description>
			<content:encoded><![CDATA[<p><img class="size-full wp-image-23 alignleft" style="margin-left: 8px; margin-right: 8px;" title="hipaalaw" src="http://hipaaemail.com/wp-content/uploads/2009/05/hipaalaw.jpg" alt="hipaalaw" width="225" height="337" />If State law and HIPAA got into a fight, who would win?</p>
<p>As a general guide, the law that offers the most protection to the patient in question wins.  The whole idea of HIPAA is to increase the privacy of medical records.  It doesn’t always succeed in its aims, but that’s beside the point.</p>
<p>There are clauses written in to the HIPAA Administrative Simplification Rules that will either override or be subject to State law depending on which law offers the most protection to the patient and their PHI.  These kind of judgements are generally made by a judge or the Department of Health and Human Services (HHS) who administer HIPAA.  Even if state law contravenes HIPAA, a judgement may be made against HIPAA or for it depending on this decision.</p>
<p>There is a whole raft of criteria to be taken into account when making a decision, which is why it is reserved for judges and HHS officials.  HIPAA can certainly be curtailed if there is a risk of fraud or a compelling public health, or safety reason.  Prevention of crimes or abuses would certainly qualify.</p>
<p>So, like everything else that concerns HIPAA, it is complicated, convoluted and never straight forward.  However the first statement is as accurate an assessment a layman can make.  Whichever law protects the privacy of PHI the most wins.  So as with most things HIPAA, it’s heart may appear to be in the right place, even if it’s brain isn’t.</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaemail.com/state-law-or-hipaa/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Can a patient inspect their own records?</title>
		<link>http://hipaaemail.com/can-a-patient-inspect-their-own-records/</link>
		<comments>http://hipaaemail.com/can-a-patient-inspect-their-own-records/#comments</comments>
		<pubDate>Wed, 27 May 2009 20:18:05 +0000</pubDate>
		<dc:creator></dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[hipaa law]]></category>

		<category><![CDATA[hipaa laws]]></category>

		<category><![CDATA[hipaa patient]]></category>

		<category><![CDATA[hipaa patient rules]]></category>

		<category><![CDATA[hipaa rules]]></category>

		<category><![CDATA[rules]]></category>

		<guid isPermaLink="false">http://hipaaemail.com/?p=18</guid>
		<description><![CDATA[
The HIPAA concentrates a lot on protecting PHI from other people, but can a patient see their own records?  In a word yes, after all the patient is the one being talked about in them!
A patient has the right to inspect a copy of their own PHI without charge at any time within reason.  A [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-19" title="secret" src="http://hipaaemail.com/wp-content/uploads/2009/05/secret.jpg" alt="secret" width="550" height="253" /></p>
<p>The HIPAA concentrates a lot on protecting PHI from other people, but can a patient see their own records?  In a word yes, after all the patient is the one being talked about in them!</p>
<p>A patient has the right to inspect a copy of their own PHI without charge at any time within reason.  A patient also has the right to obtain a copy of their records, again within reason.  An organization has the right to charge a fee for making a copy, ostensibly to cover the administration cost of the request.  As a record can in some cases be thousands of pages long, the patient should perhaps be selective about what is requested.</p>
<p>Apart from general curiosity there are many reasons why a patient would want to access their PHI.  The records can be used to seek a second opinion on a diagnosis or treatment, having a copy of the record would speed things up considerably.  As would having a copy when accessing a new doctor if a patient changed area or state.  Records are transferred as part of the procedure when changing practitioners, but having a copy of a record would speed things up if something was needed instantly.</p>
<p>Many decisions are based on the contents of a medical record.  If a patient believes they have had decisions that seem incorrect or unfair, then it is logical to find out on what information that decision is based.  If a patient was refused insurance, or the insurance refused a payout then it would also be a good idea to check the records. There may be mistakes or incorrect information in the record that needs to be changed that only you would recognize.  Although having a medical record amended can be a bit of a pain&#8230;</p>
<p>Then there is the thorny issue of malpractice.  The PHI may form either the basis or evidence towards a malpractice suit.  Having a copy will aid this both for the patient and their lawyers.</p>
<p>In the end, the patient has the right to view or copy their own medical records.  They don’t even have to have a reason, or disclose it if they don’t want to.</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaemail.com/can-a-patient-inspect-their-own-records/feed/</wfw:commentRss>
		</item>
		<item>
		<title>HIPAA Overview</title>
		<link>http://hipaaemail.com/hipaa-overview/</link>
		<comments>http://hipaaemail.com/hipaa-overview/#comments</comments>
		<pubDate>Wed, 27 May 2009 20:14:06 +0000</pubDate>
		<dc:creator></dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[email hipaa]]></category>

		<category><![CDATA[hipaa]]></category>

		<category><![CDATA[hipaa email]]></category>

		<category><![CDATA[hipaa laws]]></category>

		<category><![CDATA[how does hipaa work]]></category>

		<guid isPermaLink="false">http://hipaaemail.com/?p=14</guid>
		<description><![CDATA[This innocuous acronym stands for Health Insurance Portability and Accountability Act.  This is a federal statute that was enacted in 1996 to attempt to protect the medical records of citizens.  The Act itself is massive, and covers many aspects of medical care and the handling of records and information.  The two that are relevant to [...]]]></description>
			<content:encoded><![CDATA[<p><img class="size-full wp-image-15 alignleft" style="margin-left: 8px; margin-right: 8px;" title="hipaa" src="http://hipaaemail.com/wp-content/uploads/2009/05/hipaa.gif" alt="hipaa" width="319" height="281" />This innocuous acronym stands for Health Insurance Portability and Accountability Act.  This is a federal statute that was enacted in 1996 to attempt to protect the medical records of citizens.  The Act itself is massive, and covers many aspects of medical care and the handling of records and information.  The two that are relevant to our needs are the privacy rule and the security rule.  Both of which will be covered in depth later.  There are other rules provided under the act and they are the Enforcement Rule, the Transactions and Code Sets Rule and the Unique Identifiers rule.</p>
<p>The idea was to have an all encompassing act that covered as much ground as possible with regards patient privacy and confidentiality.  As expected the act is complicated and convoluted even for lawyers to work with, let alone the people it is designed to protect.  It serves to protect any medical record that an individual may have and attempts to afford these records as much control and privacy as possible. The people responsible for enforcing the privacy aspect of HIPAA is the Office for Civil Rights (OCR) and took effect in April 2003.</p>
<p>Within the act, patients are called ‘individuals’ and their medical records are called ‘PHI’ or ‘Personal Health Information’.  Any organization who handles PHI, or pays or receives electronic payment from an organization that conforms to HIPAA is subject to it.  PHI itself is regarded as any “individually identifiable health information” used, stored or transferred by any organization or entity, in any form.</p>
<p>There was a myth that the HIPAA only covered electronic information, but this is false.  It covers medical information as above in any form or media.  It doesn’t matter if it is electronic, paper or oral, the act applies.</p>
<p>The PHI itself is anything that could even loosely identify an individual and associate them with medical information.  It includes any past, present or future medical conditions, any healthcare provision information and any payments related to any healthcare provision.</p>
<p>Basically this all means that an organization covered by HIPAA is not permitted to disclose medical information to anybody unless the individual authorizes it or the privacy rule itself requires it.</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaemail.com/hipaa-overview/feed/</wfw:commentRss>
		</item>
		<item>
		<title>HIPAA and email</title>
		<link>http://hipaaemail.com/hipaa-and-email/</link>
		<comments>http://hipaaemail.com/hipaa-and-email/#comments</comments>
		<pubDate>Tue, 17 Mar 2009 11:43:55 +0000</pubDate>
		<dc:creator></dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[act]]></category>

		<category><![CDATA[archive]]></category>

		<category><![CDATA[Archive Compliance]]></category>

		<category><![CDATA[archive exchange]]></category>

		<category><![CDATA[archiving]]></category>

		<category><![CDATA[archiving compliance]]></category>

		<category><![CDATA[backup]]></category>

		<category><![CDATA[backups]]></category>

		<category><![CDATA[compliance]]></category>

		<category><![CDATA[email]]></category>

		<category><![CDATA[email archive]]></category>

		<category><![CDATA[email archiving]]></category>

		<category><![CDATA[email archiving compliance]]></category>

		<category><![CDATA[email discovery]]></category>

		<category><![CDATA[email host]]></category>

		<category><![CDATA[email hosting]]></category>

		<category><![CDATA[emails]]></category>

		<category><![CDATA[Exchange 2007]]></category>

		<category><![CDATA[exchange mail archive]]></category>

		<category><![CDATA[finra]]></category>

		<category><![CDATA[frcp]]></category>

		<category><![CDATA[government]]></category>

		<category><![CDATA[Health Insurance Portability and Accountability Act]]></category>

		<category><![CDATA[hipaa]]></category>

		<category><![CDATA[hosting]]></category>

		<category><![CDATA[hosting for email]]></category>

		<category><![CDATA[how to]]></category>

		<category><![CDATA[laws]]></category>

		<category><![CDATA[mail]]></category>

		<category><![CDATA[Microsoft Exchange]]></category>

		<category><![CDATA[Microsoft Exchange 2007]]></category>

		<category><![CDATA[phi]]></category>

		<category><![CDATA[policy]]></category>

		<category><![CDATA[rules]]></category>

		<category><![CDATA[saas]]></category>

		<category><![CDATA[sec]]></category>

		<category><![CDATA[server]]></category>

		<category><![CDATA[soc]]></category>

		<category><![CDATA[sox]]></category>

		<category><![CDATA[system]]></category>

		<category><![CDATA[what are the laws]]></category>

		<category><![CDATA[what is email archiving]]></category>

		<guid isPermaLink="false">http://hipaaemail.com/?p=4</guid>
		<description><![CDATA[

As discussed last time HIPAA email is regarded as anything that contains any information relating to your medical records.  They don&#8217;t have to be the records themselves, they can be anything from your address or phone number, date of birth, social security number, next of kin, insurance information administrative or otherwise and even your admission [...]]]></description>
			<content:encoded><![CDATA[<p><a href="https://www.archivecompliance.com/Order.html"><br />
</a></p>
<p>As discussed last time HIPAA email is regarded as anything that contains any information relating to your medical records.  They don&#8217;t have to be the records themselves, they can be anything from your address or phone number, date of birth, social security number, next of kin, insurance information administrative or otherwise and even your admission information for any medical visits or stays.</p>
<p>It isn&#8217;t only clinics, hospitals or doctors that are subject to this.  Your employer is too if you have a health or medical plan.  If email is becoming an increasingly popular medium for transmitting your information then it is logical that those mails are stored somewhere.  Companies who handle this kind of information have to have an information storage strategy that complies with HIPAA and many other pieces of legislation.  Many companies handle this in-house with their existing staff and infrastructure.</p>
<p>Some outsource this burden to companies like Archive Compliance who will take care of their secure storage for them.  Companies like this have to demonstrate that their storage and retrieval methods are secure to be able to remain in business.</p>
<p>This method may not be palatable to everyone as you are paying out, but own nothing.  One the other hand you are paying someone to take all the hassle out of not just HIPAA email storage but all of your email storage needs.</p>
]]></content:encoded>
			<wfw:commentRss>http://hipaaemail.com/hipaa-and-email/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>

