<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;A0YGRncyfip7ImA9WhRaFE8.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934</id><updated>2012-02-16T13:52:07.996-08:00</updated><category term="Breach Notification" /><category term="HITECH HIPAA Security" /><category term="AHIMA Sequestering" /><title>HIPAA Security and Privacy</title><subtitle type="html">This site is dedicated to Healthcare Security and Privacy with a focus on HIPAA and Federal Legislation (HITECH)</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://www.hipaasecurityandprivacy.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>199</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/HipaaSecurityAndPrivacy" /><feedburner:info uri="hipaasecurityandprivacy" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;DU8DSXs-fip7ImA9WhRbGEU.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-710931428996057192</id><published>2012-02-10T07:31:00.000-08:00</published><updated>2012-02-10T07:31:18.556-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-10T07:31:18.556-08:00</app:edited><title>Health data breaches in the U.S. increased 97 percent in 2011</title><content type="html">CARPINTERIA, CA – Health data breaches in the U.S. increased 97 percent in 2011 over the year before, according to a new report by Redspin, a leading provider of IT security assessments.&lt;br /&gt;
&lt;br /&gt;
The annual survey, "Breach Report 2011, Protected Health Information,” found breaches in all 50 states, and examined a total of 385 incidents affecting over 19 million individuals since the HITECH Act's breach notification rule went into effect in August 2009.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.healthcareitnews.com/news/health-data-breaches-97-percent-2011"&gt;http://www.healthcareitnews.com/news/health-data-breaches-97-percent-2011&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-710931428996057192?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/UsJKwEmfMHcL6_h0rFAUHVCi-pA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/UsJKwEmfMHcL6_h0rFAUHVCi-pA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/UsJKwEmfMHcL6_h0rFAUHVCi-pA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/UsJKwEmfMHcL6_h0rFAUHVCi-pA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/mt2ryby3cWk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/710931428996057192/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=710931428996057192&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/710931428996057192?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/710931428996057192?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/mt2ryby3cWk/health-data-breaches-in-us-increased-97.html" title="Health data breaches in the U.S. increased 97 percent in 2011" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2012/02/health-data-breaches-in-us-increased-97.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUcDRnY_fyp7ImA9WhRbGEU.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-1579043933627418119</id><published>2012-02-10T07:17:00.000-08:00</published><updated>2012-02-10T07:17:57.847-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-10T07:17:57.847-08:00</app:edited><title>Text Messaging: HHS (Text4Health Task Force Members)</title><content type="html">&lt;a href="http://www.hhs.gov/open/initiatives/mhealth/recommendations.html"&gt;http://www.hhs.gov/open/initiatives/mhealth/recommendations.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;&lt;u&gt;Recommendation 6: Delineating Privacy/Security Issues&lt;/u&gt;. The Task Force recommends that HHS conduct further research into the privacy and security risks associated with text messaging of health information and establish guidelines for managing such privacy/security issues. Furthermore, mHealth issues should be discussed within the HHS Inter-Division Health IT Policy and Security Task Force.&lt;/strong&gt; The exchange of health information via text messages raises privacy and security issues specific to this medium.&amp;nbsp; Text messaging programs may be subject to numerous privacy and security laws, including the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Privacy and Security Rules&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-1579043933627418119?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Rq7c6yXkQwPleA6h49G39qonTP4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Rq7c6yXkQwPleA6h49G39qonTP4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Rq7c6yXkQwPleA6h49G39qonTP4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Rq7c6yXkQwPleA6h49G39qonTP4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/eIyJyZQ4kv4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/1579043933627418119/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=1579043933627418119&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1579043933627418119?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1579043933627418119?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/eIyJyZQ4kv4/text-messaging-hhs-text4health-task.html" title="Text Messaging: HHS (Text4Health Task Force Members)" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2012/02/text-messaging-hhs-text4health-task.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUMFQnw_fSp7ImA9WhRbGEU.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-1658002501065803298</id><published>2012-02-09T07:20:00.000-08:00</published><updated>2012-02-10T07:23:33.245-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-10T07:23:33.245-08:00</app:edited><title>US hospital hit by data-stealing malware (Mystery "virus" hits hospital server)</title><content type="html">An Indiana hospital has had to write to 12,000 people after &lt;strong&gt;malware&lt;/strong&gt; breached its security defences to compromise a server used to collect personal data from web forms.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The affected individuals were mostly people who might have applied for jobs at &lt;strong&gt;Goshen Hospital&lt;/strong&gt; in recent years plus some outpatients. Information put at risk includes names, addresses, and social security numbers, the hospital has told local media.&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;The malware remains unidentified beyond it being described as “a relatively common virus that is malicious,”&lt;/strong&gt; which suggests an infection that remained undetected for some time. Patient records are isolated from the Internet and were never at risk&lt;br /&gt;
&lt;a href="http://news.techworld.com/security/3335408/us-hospital-hit-by-data-stealing-malware/"&gt;http://news.techworld.com/security/3335408/us-hospital-hit-by-data-stealing-malware/&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-1658002501065803298?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/mQY-ThrxvBqQLy2IK3Tai9Da4S0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/mQY-ThrxvBqQLy2IK3Tai9Da4S0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/mQY-ThrxvBqQLy2IK3Tai9Da4S0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/mQY-ThrxvBqQLy2IK3Tai9Da4S0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/T7e2a9qOdLg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/1658002501065803298/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=1658002501065803298&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1658002501065803298?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1658002501065803298?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/T7e2a9qOdLg/us-hospital-hit-by-data-stealing.html" title="US hospital hit by data-stealing malware (Mystery &quot;virus&quot; hits hospital server)" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2012/02/us-hospital-hit-by-data-stealing.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUYFQHc4fip7ImA9WhRbGEU.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-3181565061772344280</id><published>2012-02-08T07:14:00.000-08:00</published><updated>2012-02-10T07:18:31.936-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-10T07:18:31.936-08:00</app:edited><title>Minnesota Attorney General Sues for Lost Laptop</title><content type="html">The consulting firm that lost a laptop computer with medical data on 23,500 Minnesotans last summer has been sued by Minnesota Attorney General Lori Swanson, who says it violated health privacy laws and state consumer protections.&lt;br /&gt;
&lt;br /&gt;
Swanson said Accretive Health Inc., hired by two Twin Cities hospitals, was compiling individual medical checklists that included a "frailty'' evaluation, a "complexity" score of patients' physical condition and a prediction of whether a person would be hospitalized&lt;br /&gt;
&lt;a href="http://www.startribune.com/local/137678533.html"&gt;http://www.startribune.com/local/137678533.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
The lawsuit stems from an investigation into an unencrypted laptop that was stolen July 25 in Minneapolis from the parked rental car of an Accretive employee.&lt;br /&gt;
&lt;br /&gt;
The computer contained sensitive information on 23,500 Minnesota patients of two &lt;strong&gt;Minnesota hospital systems, Fairview Health Services and North Memorial Health Care.&lt;/strong&gt; Both organizations had contracts with Accretive to help cut costs and boost revenues. Fairview's contract is even deeper, giving Accretive a management role in Fairview's "total cost of care.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;MIAOULIS NOTE:&lt;/strong&gt; This may be a trend in the future.&amp;nbsp; Do due deligence when sharing your patient information with business associates.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-3181565061772344280?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/7HrO6OBIG6Yz1nesGtZIz40eoe4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/7HrO6OBIG6Yz1nesGtZIz40eoe4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/7HrO6OBIG6Yz1nesGtZIz40eoe4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/7HrO6OBIG6Yz1nesGtZIz40eoe4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/_FjYW6KMU7A" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/3181565061772344280/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=3181565061772344280&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/3181565061772344280?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/3181565061772344280?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/_FjYW6KMU7A/minnesota-attorney-general-sues-for.html" title="Minnesota Attorney General Sues for Lost Laptop" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2012/02/minnesota-attorney-general-sues-for.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUEBSXg5cSp7ImA9WhRbGEU.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-8352887533081680537</id><published>2012-01-30T07:25:00.000-08:00</published><updated>2012-02-10T07:27:38.629-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-10T07:27:38.629-08:00</app:edited><title>Contractor Post Information on Public Website</title><content type="html">REDWOOD CITY -- A contractor working for &lt;strong&gt;Sequoia Hospital&lt;/strong&gt; inadvertently posted the names and Social Security numbers of 391 current and former hospital employees on a &lt;strong&gt;public website, where it stayed for four years. &lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
An employee for Towers Watson, an international professional services firm, posted the information in October 2007, according to a statement issued Thursday by hospital CEO Glenna Vaskelis. It was removed Dec. 2 after the hospital learned of the error.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.mercurynews.com/san-mateo-county-times/ci_19829283"&gt;http://www.mercurynews.com/san-mateo-county-times/ci_19829283&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;MIAOULIS NOTE:&lt;/strong&gt; WATCH YOUR VENDORS&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-8352887533081680537?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/n_6NXiOY80eiV33H0JospPLUbdg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/n_6NXiOY80eiV33H0JospPLUbdg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/n_6NXiOY80eiV33H0JospPLUbdg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/n_6NXiOY80eiV33H0JospPLUbdg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/gAkV63ZhIdU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/8352887533081680537/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=8352887533081680537&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/8352887533081680537?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/8352887533081680537?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/gAkV63ZhIdU/contractor-post-information-on-public.html" title="Contractor Post Information on Public Website" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2012/01/contractor-post-information-on-public.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUQCQH06eyp7ImA9WhRVGEw.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-2963251722605287802</id><published>2012-01-17T08:22:00.000-08:00</published><updated>2012-01-17T08:22:41.313-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-17T08:22:41.313-08:00</app:edited><title>Smartphones blamed for increasing risk of health data breaches</title><content type="html">&lt;h1 id="Head" style="background-color: white; font-family: Arial, san-serif; font-size: 20px; line-height: 21px; margin-bottom: 5px; margin-left: 0px; margin-right: 0px; margin-top: 0px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;"&gt;Smartphones blamed for increasing risk of health data breaches&lt;/h1&gt;&lt;div&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div&gt;&lt;div id="Btext1" style="background-color: white; border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-width: 0px; border-right-width: 0px; border-style: initial; border-top-width: 0px; font-family: 'Times New Roman', Times, serif; font-size: 16px; margin-bottom: 10px; padding-top: 0.7em;"&gt;The number of physicians using smartphones has reached a near-saturation point. Meanwhile, the number of data breaches is going up.&lt;/div&gt;&lt;div id="Btext1" style="background-color: white; border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-width: 0px; border-right-width: 0px; border-style: initial; border-top-width: 0px; font-family: 'Times New Roman', Times, serif; font-size: 16px; margin-bottom: 10px; padding-top: 0.7em;"&gt;&lt;span style="text-indent: 10px;"&gt;Coincidence? Leading experts think not.&lt;/span&gt;&lt;/div&gt;&lt;div id="Btext1" style="background-color: white; border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-width: 0px; border-right-width: 0px; border-style: initial; border-top-width: 0px; font-family: 'Times New Roman', Times, serif; font-size: 16px; margin-bottom: 10px; padding-top: 0.7em;"&gt;&lt;span style="text-indent: 10px;"&gt;Recent reports by Manhattan Research have found more than 81% of physicians use a smartphone, up from 72% in 2010. Also on the rise have been data breaches, which, according to research released in December by Ponemon Institute, have risen 32% in the past year. Ponemon found that 96% of all health care organizations surveyed said they had experienced at least one data breach in the past two years.&lt;/span&gt;&lt;/div&gt;&lt;div id="Btext1" style="background-color: white; border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-width: 0px; border-right-width: 0px; border-style: initial; border-top-width: 0px; font-family: 'Times New Roman', Times, serif; font-size: 16px; margin-bottom: 10px; padding-top: 0.7em;"&gt;&lt;a href="http://www.ama-assn.org/amednews/2011/12/19/bil21219.htm"&gt;http://www.ama-assn.org/amednews/2011/12/19/bil21219.htm&lt;/a&gt; &lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-2963251722605287802?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/A3rQvfcHo0CT6ZrCGzEYuFqdmM4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/A3rQvfcHo0CT6ZrCGzEYuFqdmM4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/A3rQvfcHo0CT6ZrCGzEYuFqdmM4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/A3rQvfcHo0CT6ZrCGzEYuFqdmM4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/eBlKBkUQ6ng" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/2963251722605287802/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=2963251722605287802&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/2963251722605287802?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/2963251722605287802?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/eBlKBkUQ6ng/smartphones-blamed-for-increasing-risk.html" title="Smartphones blamed for increasing risk of health data breaches" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2012/01/smartphones-blamed-for-increasing-risk.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DQ345fip7ImA9WhRVGEw.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-1707623065935720210</id><published>2012-01-05T08:14:00.000-08:00</published><updated>2012-01-17T08:14:32.026-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-17T08:14:32.026-08:00</app:edited><title>Loma Linda hospital worker fired for taking home private records</title><content type="html">&lt;span style="background-color: white; color: #333333; font-family: arial, helvetica, clean, sans-serif; font-size: 13px; line-height: 22px; text-align: left;"&gt;The private medical records belonging to some 1,300 patients and/or their guarantors at Loma Linda University Medical Center in California were compromised when a former hospital employee violated policy and brought the data home.&lt;/span&gt; &lt;br /&gt;
&lt;b style="background-color: white; color: #333333; font-family: arial, helvetica, clean, sans-serif; font-size: 13px; line-height: 22px; text-align: left;"&gt;What was the response?&lt;/b&gt;&lt;span style="background-color: white; color: #333333; font-family: arial, helvetica, clean, sans-serif; font-size: 13px; line-height: 22px; text-align: left;"&gt;&amp;nbsp;The worker was fired, and the hospital is investigating. Victims will receive one year of credit monitoring services.&lt;/span&gt;&lt;br /&gt;
&lt;a href="http://www.scmagazine.com/loma-linda-hospital-worker-fired-for-taking-home-private-records/article/221841/"&gt;http://www.scmagazine.com/loma-linda-hospital-worker-fired-for-taking-home-private-records/article/221841/&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-1707623065935720210?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/qPgO0jhvO3JnIWLz8LE4XcH7i6A/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/qPgO0jhvO3JnIWLz8LE4XcH7i6A/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/qPgO0jhvO3JnIWLz8LE4XcH7i6A/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/qPgO0jhvO3JnIWLz8LE4XcH7i6A/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/uyZMRiOD260" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/1707623065935720210/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=1707623065935720210&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1707623065935720210?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1707623065935720210?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/uyZMRiOD260/loma-linda-hospital-worker-fired-for.html" title="Loma Linda hospital worker fired for taking home private records" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2012/01/loma-linda-hospital-worker-fired-for.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUUDQHo8eCp7ImA9WhRVGEw.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-1306998558443615659</id><published>2011-12-23T08:19:00.000-08:00</published><updated>2012-01-17T08:21:11.470-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-17T08:21:11.470-08:00</app:edited><title>Federal agency could investigate online security breach of Lawrence Memorial Hospital</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://static4.eeiplatform.com/files/fbi-hat.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" src="http://static4.eeiplatform.com/files/fbi-hat.jpg" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;span style="background-color: white; color: #333333; font-family: Arial, Arial, Helvetica, sans-serif; font-size: 13px; line-height: 19px;"&gt;&lt;br /&gt;
&lt;/span&gt;&lt;br /&gt;
&lt;span style="background-color: white; color: #333333; font-family: Arial, Arial, Helvetica, sans-serif; font-size: 13px; line-height: 19px;"&gt;Officials at the US Lawrence Memorial Hospital said&lt;/span&gt;&lt;span style="background-color: white; color: #333333; font-family: Arial, Arial, Helvetica, sans-serif; font-size: 13px; line-height: 19px;"&gt;&amp;nbsp;they are anticipating a federal investigation and possible fine after an online security breach potentially compromised 8,000 patients’ financial information.&lt;/span&gt; &lt;br /&gt;
&lt;span style="background-color: white; color: #333333; font-family: Arial, Arial, Helvetica, sans-serif; font-size: 13px; line-height: 19px;"&gt;&lt;br /&gt;
&lt;/span&gt;&lt;br /&gt;
&lt;span style="background-color: white; color: #333333; font-family: Arial, Arial, Helvetica, sans-serif; font-size: 13px; line-height: 19px;"&gt;O&lt;/span&gt;&lt;span style="background-color: white; color: #333333; font-family: Arial, Arial, Helvetica, sans-serif; font-size: 13px; line-height: 19px;"&gt;fficials from the Lawrence Memorial Hospital also believe there was a way to access a database that contained information&amp;nbsp;&lt;/span&gt;&lt;strong style="background-color: white; color: #333333; font-family: Arial, Arial, Helvetica, sans-serif; font-size: 13px; font-weight: bold; line-height: 19px;"&gt;on every patient who had used the online bill pay system since it was first offered in 2005 from that portal.&amp;nbsp;&lt;/strong&gt;&lt;br /&gt;
&lt;strong style="background-color: white; color: #333333; font-family: Arial, Arial, Helvetica, sans-serif; font-size: 13px; font-weight: bold; line-height: 19px;"&gt;&lt;br /&gt;
&lt;/strong&gt;&lt;br /&gt;
&lt;span style="background-color: white; color: #333333; font-family: Arial, Arial, Helvetica, sans-serif; font-size: 13px; line-height: 19px;"&gt;The hospital learned about the security breach on 28 October. And guess how:&amp;nbsp;&lt;/span&gt;&lt;strong style="background-color: white; color: #333333; font-family: Arial, Arial, Helvetica, sans-serif; font-size: 13px; font-weight: bold; line-height: 19px;"&gt;a patient using Google to search her husband’s name found his own financial information online.&lt;/strong&gt;&lt;span style="background-color: white; color: #333333; font-family: Arial, Arial, Helvetica, sans-serif; font-size: 13px; line-height: 19px;"&gt;&amp;nbsp;&lt;/span&gt;&lt;br /&gt;
&lt;span style="background-color: white; color: #333333; font-family: Arial, Arial, Helvetica, sans-serif; font-size: 13px; line-height: 19px;"&gt;&lt;br /&gt;
&lt;/span&gt;&lt;br /&gt;
&lt;a href="http://eeiplatform.com/6525/fbi-to-investigate-security-breach-in-hospital-e-billing-system/"&gt;http://eeiplatform.com/6525/fbi-to-investigate-security-breach-in-hospital-e-billing-system/&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-1306998558443615659?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/AOHIOQ_rfm75Cle7LXo_ohSBIq0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/AOHIOQ_rfm75Cle7LXo_ohSBIq0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/AOHIOQ_rfm75Cle7LXo_ohSBIq0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/AOHIOQ_rfm75Cle7LXo_ohSBIq0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/Lh2OlzEOFag" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/1306998558443615659/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=1306998558443615659&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1306998558443615659?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1306998558443615659?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/Lh2OlzEOFag/federal-agency-could-investigate-online.html" title="Federal agency could investigate online security breach of Lawrence Memorial Hospital" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2012/01/federal-agency-could-investigate-online.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkYER3szcCp7ImA9WhRQGUs.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-6579054238983530539</id><published>2011-12-15T06:40:00.000-08:00</published><updated>2011-12-15T06:41:46.588-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-15T06:41:46.588-08:00</app:edited><title>HHS Audits the 1% … and the Rest: First HIPAA Privacy and Security Audits Begin</title><content type="html">By Adam H. Greene&lt;br /&gt;
12.13.11 &lt;br /&gt;
The U.S. Department of Health and Human Services (HHS) Office for Civil Rights (OCR) has begun the process of notifying covered entities that they are among the unlucky few who have been selected for the first Health Insurance Portability and Accountability Act of 1996 (HIPAA) privacy and security audits under the Health Information Technology for Economic and Clinical Health (HITECH) Act. The selected entities represent a cross sample of the health care industry—from billion-dollar health care systems to small physician practices. Audited entities will undergo comprehensive reviews of their privacy and security policies and procedures, documentation, and operations.&lt;br /&gt;
&lt;br /&gt;
While the first twenty covered entities have been selected, approximately another 130 remain in this audit round. HHS has indicated that it hopes to continue with proactive audits in the future and expects to become more aggressive in its enforcement of complaints. &lt;br /&gt;
&lt;a href="http://www.dwt.com/LearningCenter/Advisories?find=450543"&gt;http://www.dwt.com/LearningCenter/Advisories?find=450543&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-6579054238983530539?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/6tlvx8ltWiCq-QJYZ-f9qggk3-Q/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/6tlvx8ltWiCq-QJYZ-f9qggk3-Q/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/6tlvx8ltWiCq-QJYZ-f9qggk3-Q/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/6tlvx8ltWiCq-QJYZ-f9qggk3-Q/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/ta34W6DUHHA" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/6579054238983530539/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=6579054238983530539&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/6579054238983530539?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/6579054238983530539?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/ta34W6DUHHA/hhs-audits-1-and-rest-first-hipaa.html" title="HHS Audits the 1% … and the Rest: First HIPAA Privacy and Security Audits Begin" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/12/hhs-audits-1-and-rest-first-hipaa.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE4NQno6fip7ImA9WhRQEUU.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-4540868797292538396</id><published>2011-12-06T07:56:00.000-08:00</published><updated>2011-12-06T07:56:33.416-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-06T07:56:33.416-08:00</app:edited><title>NIST: New FREE HIPAA Tool Helps Organizations Meet Security Requirements</title><content type="html">From NIST Tech Beat: November 22, 2011&lt;br /&gt;
&lt;br /&gt;
Contact: Evelyn Brown &lt;br /&gt;
301-975-5661&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;A new tool, &lt;/strong&gt;developed by the National Institute of Standards and Technology (NIST) and &lt;strong&gt;offered for free&lt;/strong&gt;, can help public and private organizations, large and small, to understand and implement the requirements of the Health Insurance Portability and Accountability Act (HIPAA) Security Rule.&lt;br /&gt;
&lt;br /&gt;
Congress enacted HIPAA to, among other things, promote efficiency in the health care industry through the use of standardized electronic transactions, while protecting the privacy and security of health information.&lt;br /&gt;
&lt;br /&gt;
The Secretary of Health and Human Services (HHS) published the HIPAA Security Rule, a national set of standards for protecting electronic protected health information (EPHI) that is created, transmitted, or maintained by covered entities and their business associates. HHS recognizes the value of NIST's information security standards and guidelines, and has recommended these as valuable resources for organizations to consider as they implement the HIPAA Security Rule.&lt;br /&gt;
&lt;br /&gt;
The law requires "covered entities" and business associates to follow the HIPAA Security Rule. Covered entities include government agencies involved in health records, health care providers, health plans such as health insurance issuers and Medicaid and Medicare programs, health care clearinghouses and Medicare prescription drug card sponsors. "&lt;strong&gt;Our HIPAA Security Rule Toolkit is designed to help organizations of all sizes and with varying levels of security expertise to better protect electronic health information," says NIST information security specialist Kevin Stine.&lt;/strong&gt; "It leverages many existing security resources and tailors them for use within the context of HIPAA security." He emphasizes that the application is meant as a self-assessment tool, and does not indicate HIPAA Security Rule compliance.&lt;br /&gt;
&lt;br /&gt;
The toolkit is intended to be a resource that organizations can use to &lt;strong&gt;support their risk assessment processes&lt;/strong&gt; by identifying areas where security safeguards may be needed to protect EPHI, or where existing security safeguards may need to be improved. The self-assessment tool presents a series of questions in groups related to each of the HIPAA Security Rule standards and implementation specifications. For simplicity, the toolkit follows the established HIPAA structure of administrative, physical and technical safeguards, organizational requirements, and policies, procedures and documentation requirements.&lt;br /&gt;
&lt;br /&gt;
The target audience includes HIPAA-covered entities and business associates, and organizations that provide Security Rule implementation, assessment and compliance services. Target user organizations can range in size from a large nationwide health plan with vast information technology (IT) resources to a small two-doctor health care provider with limited access to IT expertise.&lt;br /&gt;
&lt;br /&gt;
The free toolkit comes with a comprehensive User Guide and a self-contained, stand-alone software application that can run on Windows, Mac and Linux operating systems. It is available at &lt;a href="http://scap.nist.gov/hipaa"&gt;http://scap.nist.gov/hipaa&lt;/a&gt;&amp;nbsp;. Funding for the toolkit was provided by the American Recovery and Reinvestment Act of 2009.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.nist.gov/itl/csd/20111122_hipaa_tools.cfm"&gt;http://www.nist.gov/itl/csd/20111122_hipaa_tools.cfm&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-4540868797292538396?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/BvUG3wiHoirW_lvb-OvFFikACHs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/BvUG3wiHoirW_lvb-OvFFikACHs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/BvUG3wiHoirW_lvb-OvFFikACHs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/BvUG3wiHoirW_lvb-OvFFikACHs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/LWQjeFalQwA" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/4540868797292538396/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=4540868797292538396&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/4540868797292538396?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/4540868797292538396?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/LWQjeFalQwA/nist-new-free-hipaa-tool-helps.html" title="NIST: New FREE HIPAA Tool Helps Organizations Meet Security Requirements" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/12/nist-new-free-hipaa-tool-helps.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0MFQHs6eSp7ImA9WhRRFUo.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-3174008724764042507</id><published>2011-11-29T07:10:00.000-08:00</published><updated>2011-11-29T07:10:11.511-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-29T07:10:11.511-08:00</app:edited><title>Sutter Health Hit With $1B Class-Action Lawsuit</title><content type="html">&lt;strong&gt;Miaoulis Note: &lt;/strong&gt;Hospitals better take extra care, like many profession, Attorney's are aware of this lawsuit and will be evaluating similar type cases.&amp;nbsp; Many questions can be asked, but my first question is why is this much data on a DESKTOP computer and not in the computer room.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Conduct your risk analysis now, that starts with knowing where your data is located.&amp;nbsp; That is the key, identify data on Desktops, Laptops, Flash Drives, Home Computers, Business Associates, Servers, Cell Phones and within application systems&amp;nbsp;and then create strategies to minimize the risks to this data.&lt;br /&gt;
------------------&lt;br /&gt;
SACRAMENTO, Calif. (KCRA) -- A class-action complaint was filed Monday in Sacramento Superior Court on behalf of Karen Pardieck and 944,000 other patients, KCRA 3 learned Tuesday. &lt;br /&gt;
&lt;br /&gt;
A desktop computer was stolen from a Sutter Medical Foundation administrative office Oct. 15. &lt;br /&gt;
&lt;br /&gt;
Stolen Sutter Computer Has Millions of Patients' Info &lt;br /&gt;
&lt;br /&gt;
It contained a patient database with information including names, addresses, birthdays, email addresses, phone numbers and descriptions of medical diagnoses and procedures. &lt;br /&gt;
&lt;br /&gt;
The lawsuit cites a “failure to safeguard and secure patients’ private information” and “negligent storage practices” that led to an increased risk of a serious information breach. &lt;br /&gt;
&lt;br /&gt;
Sutter has admitted the information lost was &lt;strong&gt;&lt;span style="font-size: large;"&gt;unencrypted.&lt;/span&gt;&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
Read more: &lt;a href="http://www.kcra.com/news/29835846/detail.html#ixzz1f6i7o4GI"&gt;http://www.kcra.com/news/29835846/detail.html#ixzz1f6i7o4GI&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-3174008724764042507?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ERxPyaFvKXCpUu_TyMvWwFAcbFk/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ERxPyaFvKXCpUu_TyMvWwFAcbFk/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ERxPyaFvKXCpUu_TyMvWwFAcbFk/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ERxPyaFvKXCpUu_TyMvWwFAcbFk/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/_wrZoOEzxtA" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/3174008724764042507/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=3174008724764042507&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/3174008724764042507?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/3174008724764042507?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/_wrZoOEzxtA/sutter-health-hit-with-1b-class-action.html" title="Sutter Health Hit With $1B Class-Action Lawsuit" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/11/sutter-health-hit-with-1b-class-action.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkENQX8yfCp7ImA9WhRRFk0.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-4762848921555815101</id><published>2011-11-26T12:36:00.000-08:00</published><updated>2011-11-29T13:04:50.194-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-29T13:04:50.194-08:00</app:edited><title>25 "Worst Passwords" of 2011</title><content type="html">If you see your password below, STOP! &lt;br /&gt;
Do not finish reading this post and immediately go change your password -- before you forget. You will probably make changes in several places since.....................&lt;br /&gt;
&lt;br /&gt;
Here&amp;nbsp;is a&amp;nbsp;lists compiled by SplashData: &lt;a href="http://www.splashdata.com/"&gt;http://www.splashdata.com/&lt;/a&gt;&lt;br /&gt;
1. password &lt;br /&gt;
2. 123456 &lt;br /&gt;
3.12345678 &lt;br /&gt;
4. qwerty &lt;br /&gt;
5. abc123&lt;br /&gt;
6. monkey&lt;br /&gt;
7. 1234567 &lt;br /&gt;
8. letmein &lt;br /&gt;
9. trustno1&lt;br /&gt;
10. dragon &lt;br /&gt;
11. baseball&lt;br /&gt;
12. 111111&lt;br /&gt;
13. iloveyou&lt;br /&gt;
14. master&lt;br /&gt;
15. sunshine &lt;br /&gt;
16. ashley &lt;br /&gt;
17. bailey &lt;br /&gt;
18. passwOrd &lt;br /&gt;
19. shadow s&lt;br /&gt;
20. 123123 &lt;br /&gt;
21. 654321 &lt;br /&gt;
22. superman &lt;br /&gt;
23. qazwsx &lt;br /&gt;
24. michael &lt;br /&gt;
25. football &lt;br /&gt;
&lt;a href="http://finance.yahoo.com/news/25-worst-passwords-2011-revealed-202955980.html"&gt;http://finance.yahoo.com/news/25-worst-passwords-2011-revealed-202955980.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;MIAOULIS NOTES: &lt;/strong&gt;Passwords are one of the two most critical access controls (not logging off is the other) that users must understand to assist their organizations in protecting information (ePHI).&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Many organizations have decided (statisticians) that to prevent the above type passwords, that you should change your password every 60-90 days, have a different password for every system you access, have a length between 8 and 12, not allow you to use previous passwords (10 is a common number), require caps, numbers and special characters to force users to use stronger passwords.&amp;nbsp;&amp;nbsp;The problem is that users often use passwords such as their last name and #1.&amp;nbsp; If my password was Miaoulis#1 and I am forced to change it in 60 days, many users simple change the last character Miaoulis#2.&amp;nbsp; This of course defeats the controls that security admininstrators are trying to implement.&amp;nbsp; Some systems require you to change more than a certain number of characters.&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Although these technical measures help, it is TRAINING that can change human behavior.&amp;nbsp; HIPAA requires training on passwords, but are employees&amp;nbsp;trained on how to select a good password or just on what NOT to do?&lt;br /&gt;
------------------------------------------------------------------------&lt;br /&gt;
&lt;strong&gt;MIAOULIS NOTE: ONE&amp;nbsp;TECHNIQUE &lt;/strong&gt;FOR SELECTING A PASSWORD: &lt;br /&gt;
There are many ways to select good passwords.&amp;nbsp; One technique that I have used is take a sentence and use the first letter of each word, add a special character and a number. &lt;br /&gt;
&amp;nbsp; &lt;br /&gt;
Bill loves to play golf every day &lt;br /&gt;
Becomes &lt;strong&gt;BLTPGED#4&lt;/strong&gt; &lt;br /&gt;
There are other techniques such as combining words and mispelling words in combination with the rules.&lt;br /&gt;
------------------------------------&lt;br /&gt;
&lt;strong&gt;Microsoft &lt;/strong&gt;offers these hints on selecting a strong password:&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.microsoft.com/security/online-privacy/passwords-create.aspx"&gt;http://www.microsoft.com/security/online-privacy/passwords-create.aspx&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Create strong passwords: &lt;/strong&gt;&lt;br /&gt;
A strong password is an important protection to help you have safer online transactions. Here are steps you can take to create a strong password. Some or all might help protect your online transactions:&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Length.&lt;/strong&gt; Make your passwords long with eight or more characters.&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Complexity.&lt;/strong&gt; Include letters, punctuation, symbols, and numbers. Use the entire keyboard, not just the letters and characters you use or see most often. The greater the variety of characters in your password, the better. However, password hacking software automatically checks for common letter-to-symbol conversions, such as changing "and" to "&amp;amp;" or "to" to "2."&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Variation.&lt;/strong&gt; To keep strong passwords effective, change them often. Set an automatic reminder for yourself to change your passwords on your email, banking, and credit card websites about every three months.&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Variety.&lt;/strong&gt; Don't use the same password for everything. Cybercriminals steal passwords on websites that have very little security, and then they use that same password and user name in more secure environments, such as banking websites.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-4762848921555815101?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/WUvNrxj2cIHl4RrzYZsL_R1vfuo/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/WUvNrxj2cIHl4RrzYZsL_R1vfuo/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/WUvNrxj2cIHl4RrzYZsL_R1vfuo/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/WUvNrxj2cIHl4RrzYZsL_R1vfuo/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/X2newrfgjZQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/4762848921555815101/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=4762848921555815101&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/4762848921555815101?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/4762848921555815101?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/X2newrfgjZQ/25-worst-passwords-of-2011.html" title="25 &quot;Worst Passwords&quot; of 2011" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/11/25-worst-passwords-of-2011.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkYCQXkzfyp7ImA9WhRRFUU.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-4699557439472473321</id><published>2011-11-10T07:20:00.000-08:00</published><updated>2011-11-29T07:22:40.787-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-29T07:22:40.787-08:00</app:edited><title>UCLA - warns patients personal information was stolen</title><content type="html">November 05, 2011&lt;br /&gt;
&lt;br /&gt;
By Anna Gorman, Los Angeles Times&lt;br /&gt;
&lt;br /&gt;
Officials say the data, from 2007 through 2011, included first and last names as well as some birth dates, medical record numbers, addresses and medical information. It did not include Social Security numbers, credit card numbers or insurance details. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The UCLA Health System is warning thousands of patients that their personal information was stolen and they are at risk of possible identity theft, officials said in a statement released Friday.&lt;br /&gt;
&lt;br /&gt;
Officials don't believe the information has been accessed or misused but are referring patients to a data security company if their name and credit are affected.&lt;br /&gt;
&lt;a href="http://articles.latimes.com/2011/nov/05/local/la-me-ucla-medical-data-20111105"&gt;http://articles.latimes.com/2011/nov/05/local/la-me-ucla-medical-data-20111105&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-4699557439472473321?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ROZdZv04zyLP_drIrnzp4KCke_U/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ROZdZv04zyLP_drIrnzp4KCke_U/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ROZdZv04zyLP_drIrnzp4KCke_U/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ROZdZv04zyLP_drIrnzp4KCke_U/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/EbeVXFr2gfc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/4699557439472473321/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=4699557439472473321&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/4699557439472473321?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/4699557439472473321?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/EbeVXFr2gfc/ucla-warns-patients-personal.html" title="UCLA - warns patients personal information was stolen" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/11/ucla-warns-patients-personal.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEUBR3s7fSp7ImA9WhRTGEg.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-1318987891902400612</id><published>2011-11-09T07:12:00.000-08:00</published><updated>2011-11-09T07:24:16.505-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-09T07:24:16.505-08:00</app:edited><title>OCR Launches Privacy and Security Audits (Announcement)</title><content type="html">November 8, 2011&lt;br /&gt;
&lt;br /&gt;
The American Recovery and Reinvestment Act of 2009, in Section 13411 of the HITECH Act, requires HHS to provide for periodic audits to ensure covered entities and business associates are complying with the HIPAA Privacy and Security Rules and Breach Notification standards. To implement this mandate, OCR is piloting a program to &lt;strong&gt;perform up to 150 audits&lt;/strong&gt; of covered entities to assess privacy and security compliance. Audits conducted during the pilot phase will begin in &lt;strong&gt;November 2011 and conclude by December 2012&lt;/strong&gt;.&lt;br /&gt;
&lt;br /&gt;
More information regarding OCR’s Pilot Audit Program is available on the OCR website at &lt;a href="http://www.hhs.gov/ocr/privacy/hipaa/enforcement/audit/index.html"&gt;http://www.hhs.gov/ocr/privacy/hipaa/enforcement/audit/index.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;MIAOULIS NOTE:&lt;/strong&gt; The link is a must read for everyone.&amp;nbsp; Major components are provided below.&lt;br /&gt;
--------------------------------------&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Program Objectives:&lt;/strong&gt; The audit program serves as a new part of OCR’s health information privacy and security compliance program. OCR will use the audit program to assess HIPAA compliance efforts by a range of covered entities, Audits present a new opportunity to examine mechanisms for compliance, identify best practices and discover risks and vulnerabilities that may not have come to light through OCR’s ongoing complaint investigations and compliance reviews. OCR will broadly share best practices gleaned through the audit process and guidance targeted to observed compliance challenges via this web site and other outreach portals.&lt;br /&gt;
----------------------------------&lt;br /&gt;
&lt;strong&gt;Who Will Be Audited?&lt;/strong&gt;&lt;br /&gt;
Every covered entity and business associate is eligible for an audit. Selections in the initial round will be designed to provide a broad assessment of a complex and diverse health care industry. OCR is responsible for selection of the entities that will be audited. OCR will audit as wide a range of types and sizes of covered entities as possible; covered individual and organizational providers of health services, health plans of all sizes and functions, and health care clearinghouses may all be considered for an audit. We expect covered entities to provide the auditors their full cooperation and support and remind them of their cooperation obligations under the HIPAA Enforcement Rule.&lt;br /&gt;
&lt;br /&gt;
Business Associates will be included in future audits.&lt;br /&gt;
---------------------------------&lt;br /&gt;
&lt;strong&gt;When Will Audits Begin?&lt;/strong&gt;&lt;br /&gt;
The pilot audit program is a three step process. The first step entailed developing the audit protocols. Next, a limited number of audits will be conducted in an initial wave to test these protocols. OCR expects the initial audits to begin in November 2011.The results of the initial audits will inform how the rest of the audits will be conducted. The last step will include conducting the full range of audits using revised protocol materials. All audits in this pilot will be completed by the end of December, 2012.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://www.hhs.gov/ocr/privacy/hipaa/enforcement/audit/three_step-process_timeline.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="205" ida="true" src="http://www.hhs.gov/ocr/privacy/hipaa/enforcement/audit/three_step-process_timeline.jpg" width="320" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;
-------------------&lt;br /&gt;
&lt;strong&gt;How Will the Audit Program Work?&lt;/strong&gt;&lt;br /&gt;
The privacy and security performance audit process will include generally familiar audit mechanisms. Entities selected for an audit will be informed by OCR of their selection and asked to provide documentation of their privacy and security compliance efforts. In this pilot phase, every audit will include a site visit and result in an audit report. During site visits, auditors will interview key personnel and observe processes and operations to help determine compliance. Following the site visit, auditors will develop and share with the entity a draft report; audit reports generally describe how the audit was conducted, what the findings were and what actions the covered entity is taking in response to those findings. Prior to finalizing the report, the covered entity will have the opportunity to discuss concerns and describe corrective actions implemented to address concerns identified. The final report submitted to OCR will incorporate the steps the entity has taken to resolve any compliance issues identified by the audit, as well as describe any best practices of the entity&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://www.hhs.gov/ocr/privacy/hipaa/enforcement/audit/audit_timeline.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="174" ida="true" src="http://www.hhs.gov/ocr/privacy/hipaa/enforcement/audit/audit_timeline.jpg" width="320" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-1318987891902400612?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ezSM8GCA9uAhk6d5bE2a1KAlqEA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ezSM8GCA9uAhk6d5bE2a1KAlqEA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ezSM8GCA9uAhk6d5bE2a1KAlqEA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ezSM8GCA9uAhk6d5bE2a1KAlqEA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/g__x6RisJeU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/1318987891902400612/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=1318987891902400612&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1318987891902400612?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1318987891902400612?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/g__x6RisJeU/ocr-launches-privacy-and-security.html" title="OCR Launches Privacy and Security Audits (Announcement)" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/11/ocr-launches-privacy-and-security.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkcGQn48eSp7ImA9WhRRFUU.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-5938910560099804856</id><published>2011-11-08T07:14:00.000-08:00</published><updated>2011-11-29T07:20:23.071-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-29T07:20:23.071-08:00</app:edited><title>Co-worker Looking at Records Leads to Notification Letters</title><content type="html">&lt;strong&gt;MIAOULIS NOTE: What steps are you taking to prevent authorized users from viewing records?&amp;nbsp; You need strong policies, sanctions and&amp;nbsp;regular review of system activity (HIPAA Requirements).&amp;nbsp; &lt;/strong&gt;&lt;br /&gt;
&lt;strong&gt;------------------------------------&lt;/strong&gt;&lt;br /&gt;
On October 31, 2011, notification letters were sent to &lt;strong&gt;175 persons whose Deaconess Health System&lt;/strong&gt; medical records were inappropriately accessed by a now former employee.&lt;br /&gt;
&lt;br /&gt;
The accesses occurred from April through September of 2011. The problem was discovered September 12, 2011, when a &lt;strong&gt;department manager reported&lt;/strong&gt; that an employee may have made inappropriate access to the record of a co-worker. An initial audit &lt;strong&gt;confirmed&lt;/strong&gt; this and other improper accesses, and the employee was terminated. Deaconess continued its investigation by auditing all electronic record activity by the employee for the duration of her employment. This led to the finding of 175 inappropriately accessed records.&lt;br /&gt;
&lt;br /&gt;
Information viewed by the employee included name, address, dates of birth, last four digits of the Social Security Number and, where available, portions of the clinical records of the affected patients. &lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.deaconess.com/body.cfm?id=3351"&gt;http://www.deaconess.com/body.cfm?id=3351&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-5938910560099804856?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/FZ0uHi2MmpeFI2feZA1nFWTLWW0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/FZ0uHi2MmpeFI2feZA1nFWTLWW0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/FZ0uHi2MmpeFI2feZA1nFWTLWW0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/FZ0uHi2MmpeFI2feZA1nFWTLWW0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/SSw9AnfzwNE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/5938910560099804856/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=5938910560099804856&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/5938910560099804856?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/5938910560099804856?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/SSw9AnfzwNE/co-worker-looking-at-records-leads-to.html" title="Co-worker Looking at Records Leads to Notification Letters" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/11/co-worker-looking-at-records-leads-to.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU8GSHo7eyp7ImA9WhdaGE8.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-6365096047677950636</id><published>2011-10-28T11:48:00.000-07:00</published><updated>2011-10-28T11:50:29.403-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-28T11:50:29.403-07:00</app:edited><title>Leak of Emory patient records could affect thousands</title><content type="html">Nine Emory Healthcare patients have become victims of identity theft in a case that could affect the records of thousands, Channel 2 Action News reported Monday.&lt;br /&gt;
&lt;br /&gt;
The hospital bills of 32 patients at Emory’s orthopedic clinic were taken, and the Social Security numbers, dates of birth and other confidential information were used to file fraudulent tax returns in nine patients’ names, the hospital confirmed.&lt;br /&gt;
&lt;br /&gt;
"Because of the heightened level of importance Emory Healthcare places on the protection of private patient data, we have taken the additional measure of notifying by letter more than 7,300 other patients of this situation -– although we have no reason to believe any of these individuals have been impacted in any way," Emory spokesman Lance Skelley said in a prepared statement.&lt;br /&gt;
&lt;br /&gt;
In September, Emory sent a letter out to about 7,000 people -- all of the orthopedic clinic patients from 2008 -- notifying them about the breach of security. The letter advised patients to be vigilant about monitoring their credit and personal data.&lt;br /&gt;
&lt;br /&gt;
"This issue is in no way a breach of Emory’s electronic medical records system, but rather a human failure to properly follow Emory Healthcare’s prescribed duties and responsibilities for protecting private patient information," Skelley said in the prepared statement.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.ajc.com/news/dekalb/leak-of-emory-patient-1209097.html"&gt;http://www.ajc.com/news/dekalb/leak-of-emory-patient-1209097.html&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-6365096047677950636?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/56hrCko7DBzN1fIbDVCP7dUVGTg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/56hrCko7DBzN1fIbDVCP7dUVGTg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/56hrCko7DBzN1fIbDVCP7dUVGTg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/56hrCko7DBzN1fIbDVCP7dUVGTg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/jAWBuet-BFU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/6365096047677950636/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=6365096047677950636&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/6365096047677950636?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/6365096047677950636?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/jAWBuet-BFU/leak-of-emory-patient-records-could.html" title="Leak of Emory patient records could affect thousands" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/10/leak-of-emory-patient-records-could.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUQDRXg-fip7ImA9WhdaGE8.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-8092261229228919243</id><published>2011-10-28T11:42:00.000-07:00</published><updated>2011-10-28T11:42:54.656-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-28T11:42:54.656-07:00</app:edited><title>Monroeville Man Sentenced To Probation For HIPAA Violation</title><content type="html">PITTSBURGH, Pa. - In the first HIPAA prosecution in the Western District of Pennsylvania, a resident of Monroeville, Pa., has been sentenced in federal court to one year of probation on his conviction of knowingly disclosing patient health information to another person in violation of law, United States Attorney David J. Hickton announced today.&lt;br /&gt;
&lt;br /&gt;
The Health Insurance Portability and Accountability Act of 1996 (HIPAA) law passed by Congress provides for national standards for electronic health care transactions, and protects patients from the unauthorized disclosure of personal medical information without their consent.&lt;br /&gt;
&lt;br /&gt;
Senior United States District Judge Maurice B. Cohill, Jr. imposed the sentence on Paul C. Pepala, 35.&lt;br /&gt;
&lt;br /&gt;
According to information presented to the court, &lt;strong&gt;Pepala disclosed the names and social security numbers of patients at Shadyside Hospital, many of which were then used by other persons to file unauthorized form 1040 electronic tax returns in 2008, in which the filers sought tax refunds.&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
Prior to imposing sentence, Judge Cohill considered the remorsefulness of the defendant and that the maximum sentence was only one year in prison for the HIPAA violation.&lt;br /&gt;
&lt;br /&gt;
Assistant United States Attorney Gregory C. Melucci prosecuted this case on behalf of the government.&lt;br /&gt;
&lt;br /&gt;
United States Attorney Hickton commended the United States Postal Inspection Service, Internal Revenue Service and Secret Service for the investigation leading to the successful prosecution of Pepala.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.justice.gov/usao/paw/news/2011/2011_october/2011_10_20_01.html"&gt;http://www.justice.gov/usao/paw/news/2011/2011_october/2011_10_20_01.html&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-8092261229228919243?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/CYumrRj4bLza3EhRtZGnORbHoJg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/CYumrRj4bLza3EhRtZGnORbHoJg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/CYumrRj4bLza3EhRtZGnORbHoJg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/CYumrRj4bLza3EhRtZGnORbHoJg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/PECx4UKm9yc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/8092261229228919243/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=8092261229228919243&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/8092261229228919243?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/8092261229228919243?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/PECx4UKm9yc/monroeville-man-sentenced-to-probation.html" title="Monroeville Man Sentenced To Probation For HIPAA Violation" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>2</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/10/monroeville-man-sentenced-to-probation.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEIGQHo6cSp7ImA9WhdaGE8.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-2726440729730569771</id><published>2011-10-21T11:26:00.000-07:00</published><updated>2011-10-28T11:28:41.419-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-28T11:28:41.419-07:00</app:edited><title>FBI Investigating Florida Hospital Breach</title><content type="html">CELEBRATION, Fla. -- Osceola County deputies on Wednesday identified three people accused of stealing private information from patients at Florida Hospital in Celebration, which is now being investigated by the FBI.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Former hospital employees April Baker and Katrina Munroe, and her husband, Dale Munroe, were fired after 2,252 patients, mostly victims of car accidents, had their information siphoned to an attorney referral service, deputies said.&lt;br /&gt;
&lt;br /&gt;
The breach started in January 2010, however, the hospital did not notify the public until September when it took out a small ad in the Orlando Sentinel.&lt;br /&gt;
&lt;br /&gt;
Now, the FBI is investigating.&lt;br /&gt;
&lt;br /&gt;
“The Orlando FBI office recently received information alleging that patient records may have been compromised and we are coordinating with Florida Hospital representatives to investigate the matter,” an FBI spokesman said in a statement.&lt;br /&gt;
&lt;br /&gt;
Investigators said Wednesday that they could not find anything criminal, because privacy laws prevent the hospital from releasing patients' personal information. So far, the hospital has not found any cases of fraud. It has also restricted office workers from getting access to patient records. &lt;br /&gt;
&amp;nbsp; &lt;br /&gt;
&lt;a href="http://www.clickorlando.com/health/29535235/detail.html"&gt;http://www.clickorlando.com/health/29535235/detail.html&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-2726440729730569771?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/nI-_fweNCDCzIsqzlHHu31ARs-M/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/nI-_fweNCDCzIsqzlHHu31ARs-M/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/nI-_fweNCDCzIsqzlHHu31ARs-M/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/nI-_fweNCDCzIsqzlHHu31ARs-M/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/GwHBYec0xAg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/2726440729730569771/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=2726440729730569771&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/2726440729730569771?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/2726440729730569771?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/GwHBYec0xAg/fbi-investigating-florida-hospital.html" title="FBI Investigating Florida Hospital Breach" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/10/fbi-investigating-florida-hospital.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEAER3Y4fip7ImA9WhdaGE8.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-9182816377525252804</id><published>2011-10-10T11:29:00.000-07:00</published><updated>2011-10-28T11:31:46.836-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-28T11:31:46.836-07:00</app:edited><title>Stanford Hospital sued $20M over data breach</title><content type="html">Twenty million dollars for 20,000 patients: That's how much Stanford Hospital &amp;amp; Clinics stands to owe if the patients win the class-action lawsuit against the leading hospital. Stanford is vowing to fight the lawsuit filed by the patient, who represents thousands of patients whose information was exposed online for almost an entire year, reports Palo Alto Daily News.&lt;br /&gt;
&lt;br /&gt;
The data breach was discovered on Aug. 22, and the information was removed the next day when Stanford Hospital began an "aggressive investigation," according to a Stanford press release. &lt;br /&gt;
&lt;br /&gt;
Stanford pointed to the billing contractor (and co-defendant) Multi-Specialty Collection Services LLC (MSCS) as the culprit for mishandling patients' data. The hospital sent the encrypted data to MSCS, according to Stanford Hospital. MSCS's executive vice president allegedly created an unencrypted electronic spreadsheet and sent it to an unauthorized person to create bar graphs and charts. The unnamed third party allegedly posted it to the public Student of Fortune, a homework help site.&lt;br /&gt;
&lt;br /&gt;
Read more: Stanford Hospital sued $20M over data breach, faults billing contractor - FierceHealthcare http://www.fiercehealthcare.com/story/stanford-hospital-sued-20m-over-data-breach-faults-billing-contractor/2011-10-07#ixzz1c6QcGZdb &lt;br /&gt;
&lt;br /&gt;
Subscribe: http://www.fiercehealthcare.com/signup?sourceform=Viral-Tynt-FierceHealthcare-FierceHealthcare&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-9182816377525252804?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Eb3REm5Nm-0wFqMxNdvqomApWA0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Eb3REm5Nm-0wFqMxNdvqomApWA0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Eb3REm5Nm-0wFqMxNdvqomApWA0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Eb3REm5Nm-0wFqMxNdvqomApWA0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/yvL_ZZtQtHo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/9182816377525252804/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=9182816377525252804&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/9182816377525252804?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/9182816377525252804?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/yvL_ZZtQtHo/stanford-hospital-sued-20m-over-data.html" title="Stanford Hospital sued $20M over data breach" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>2</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/10/stanford-hospital-sued-20m-over-data.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEAMQ308fip7ImA9WhdaGE8.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-1830300680567871791</id><published>2011-10-03T11:31:00.000-07:00</published><updated>2011-10-28T11:33:02.376-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-28T11:33:02.376-07:00</app:edited><title>TRICARE breach puts 4.9M military clinic, hospital patients at risk</title><content type="html">FAllS CHURCH, VA – TRICARE, which provides civilian health benefits for military personnel, military retirees and their dependents, announced on Wednesday that Science Applications International has reported a data breach involving personally identifiable and protected health information (PII/PHI) impacting an estimated 4.9 million military clinic and hospital patients. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The breach was reported by SAIC on Sept. 14 and involved backup tapes from an electronic healthcare record used in the military health system (MHS) to capture patient data from 1992 through Sept. 7, 2011, from patients who received care in the San Antonio area military treatment facilities (including the filling of pharmacy prescriptions) and others whose laboratory workups were processed in these same facilities even though the patients were receiving treatment elsewhere. &lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://healthcareitnews.com/news/tricare-breach-puts-49m-milatry-clinic-hospital-patients-risk"&gt;http://healthcareitnews.com/news/tricare-breach-puts-49m-milatry-clinic-hospital-patients-risk&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-1830300680567871791?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/XCuJvc43sE6HkV8leoRtllKYbqw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/XCuJvc43sE6HkV8leoRtllKYbqw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/XCuJvc43sE6HkV8leoRtllKYbqw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/XCuJvc43sE6HkV8leoRtllKYbqw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/JYhzbLq2POo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/1830300680567871791/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=1830300680567871791&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1830300680567871791?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1830300680567871791?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/JYhzbLq2POo/tricare-breach-puts-49m-military-clinic.html" title="TRICARE breach puts 4.9M military clinic, hospital patients at risk" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/10/tricare-breach-puts-49m-military-clinic.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEIDQX4-cCp7ImA9WhdWFU0.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-3329064113080043939</id><published>2011-09-08T11:29:00.000-07:00</published><updated>2011-09-08T11:29:30.058-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-08T11:29:30.058-07:00</app:edited><title>Annual Report to Congress on HIPAA Privacy Rule and Security Rule Compliance</title><content type="html">Get the full report (PDF) Here:&lt;br /&gt;
&lt;a href="http://www.hhs.gov/ocr/privacy/hipaa/enforcement/compliancerept.pdf"&gt;http://www.hhs.gov/ocr/privacy/hipaa/enforcement/compliancerept.pdf&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
For Calendar Years 2009 and 2010: &lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: small;"&gt;&lt;span style="font-size: small;"&gt;The Department investigated and resolved over 150 cases involving allegations of violations of the Security Rule by requiring changes in security practices and other corrective actions by covered entities. The Department has successfully enforced the Security Rule in all cases where an investigation indicated noncompliance by providing technical assistance to and requiring the covered entity to take corrective actions. Corrective actions taken by covered entities include: correcting any problems indicated by evidence in the investigation; training employees; sanctioning employees; revising policies and procedures; and mitigating any alleged harm. Corrective actions obtained by the Department from covered entities have improved the privacy protection of health information for individuals served by such covered entities. The Department has investigated complaints against many different types of entities including: national pharmacy chains, major medical centers, group health plans, hospital chains, and small provider offices.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In another 139 cases, investigations by the Department found that no violation of the Security Rule occurred.&lt;br /&gt;
&lt;br /&gt;
Other Security Rule Resolutions&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: small;"&gt;From April 20, 2005, the compliance date of the HIPAA Security Rule, to December 31, 2010, OCR received 803 complaints alleging violations of the Security Rule. The Department resolved 577, or seventy-two percent, of the complaints received. &lt;br /&gt;
&lt;br /&gt;
In the remaining 288 resolved cases, the Department determined that the complaints did not present eligible cases for enforcement of either the Security Rule or the Privacy Rule. In these cases, the Department also lacked jurisdiction under the Rules, &lt;span style="font-size: small;"&gt;because the complaint alleged a violation prior to the compliance date, alleged a violation by an entity not covered by the Rules, was untimely or withdrawn, or because the activity described in the complaint did not violate the Rules. Also during this time period, the Department opened 38 compliance reviews and closed 23 compliance reviews.&lt;/span&gt; &lt;br /&gt;
&lt;span style="font-size: small;"&gt;&lt;/span&gt;&amp;nbsp; &lt;br /&gt;
&lt;span style="font-size: small;"&gt;Case Examples &lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following examples are summaries of actual Privacy and Security Rule cases investigated and resolved by the Department in 2009 and 2010.&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;An individual filed&lt;/strong&gt; a complaint with OCR alleging that a private practice physician denied her access to her medical records because she had an outstanding balance for services the physician had provided. During OCR’s investigation, the physician confirmed that the individual was not given access to her medical record because of the outstanding balance. OCR provided technical assistance to the physician, explaining that, in general, the Privacy Rule requires that a covered entity provide an individual with access to her medical record within 30 days of a request, regardless of whether or not the individual has a balance due. Once the physician learned that he could not withhold access until payment was made, the physician provided the complainant a copy of her medical record.&lt;/li&gt;
&lt;/ul&gt;&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;An individual who was both a &lt;strong&gt;patient and an employee&lt;/strong&gt; of the hospital filed a complaint with OCR alleging that her PHI was impermissibly disclosed to her supervisor. OCR’s investigation revealed that the hospital distributed an Operating Room (OR) schedule to employees via e-mail; this OR schedule contained information about the individual’s upcoming surgery. While the Privacy Rule may permit the disclosure of an OR schedule containing PHI, in this case, a hospital employee shared the OR schedule with the individual’s supervisor, who was not part of the employee’s treatment team, and did not need the information for payment, health care operations, or other permissible purposes. The hospital disciplined and retrained the employee who made the impermissible disclosure. Additionally, in order to prevent similar incidents, the hospital undertook a complete review of the distribution of the OR schedule. As a result of this review, the hospital revised the distribution of the OR schedule, limiting it to those who have “a need to know.”&lt;/li&gt;
&lt;/ul&gt;&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;A physician practice&lt;/strong&gt; requested that patients sign an agreement entitled “Consent and Mutual Agreement to Maintain Privacy.” The agreement prohibited the patient from directly or indirectly publishing or airing commentary about the physician, his expertise, and/or treatment in exchange for the physician’s compliance with the Privacy Rule. A patient’s rights under the Privacy Rule are not contingent on the patient’s agreement with a covered entity. A covered entity’s obligation to comply with all requirements of the Privacy Rule cannot be conditioned on the patient’s silence. OCR required the covered entity to cease using the patient agreement that conditioned the entity’s compliance with the Privacy Rule. Additionally, OCR required the covered entity to revise its Notice of Privacy Practices.&lt;/li&gt;
&lt;/ul&gt;&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Media reports&lt;/strong&gt; indicated that computer backup tapes containing electronic PHI for two million individuals were stolen from a vehicle used by a hospital’s off-site storage vendor. OCR investigated the surrounding circumstances and subsequently instituted a compliance review to evaluate the hospital’s overall compliance with the Security Rule. The compliance review revealed gaps in the hospital’s Security Rule compliance program. As a result of the review, the hospital developed a corrective action plan, which included: the adoption of encryption technologies on all backup tapes that contained electronic PHI; termination of the off-site storage contract and reevaluation of contactor requirements to transport and store backup tapes; improvements to security awareness training policies; and revision of the process for periodic review and updates of policies and procedures.&lt;/li&gt;
&lt;/ul&gt;&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;An individual filed a complaint with OCR after receiving a letter from a health care clinic reporting the theft of a computer that held PHI&lt;/strong&gt;. OCR’s investigation determined that the computer had been stolen while a reception desk was left unattended and that the electronic PHI on the computer’s hard drive was not encrypted. OCR’s investigation revealed that, following the theft, the covered entity took corrective actions to improve its physical security safeguards and prevent similar unauthorized disclosures from occurring in the future. The entity retrained its employees on privacy and security policies and procedures, encrypted its computers and electronic devices, installed locking mechanisms, and instituted a policy of closing and locking doors when offices were unattended.&lt;/li&gt;
&lt;/ul&gt;&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;An individual filed a complaint with OCR alleging that the &lt;strong&gt;PHI of health plan members was available on the internet through online searches.&lt;/strong&gt; OCR’s investigation of the complaint revealed gaps in the covered entity’s Security Rule compliance program. Specifically, the entity implemented system changes to its web servers without analyzing the associated risks, and without performing an evaluation of how well its securitymeasures responded to the changes, as required by the Security Rule. As a result, the entity was unaware that unsecured member information was exposed on the internet and did not take actions to evaluate and revise its practices until several months later, when it was notified of the impermissible disclosure. At the conclusion of the investigation, OCR obtained assurances from the entity that it had initiated evaluations of its existing security measures and modifications of its policies, procedures, and system designs to secure its members’ PHI.&lt;/li&gt;
&lt;/ul&gt;&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;An individual filed a complaint with OCR alleging that a mental health center (the "Center") refused &lt;strong&gt;to provide her with a copy of her medical record,&lt;/strong&gt; including psychotherapy notes. OCR’s investigation revealed that the Center provided the complainant with an opportunity to review her medical record, including the psychotherapy notes, with her therapist, but the Center did not provide her with a copy of her records. The Privacy Rule requires covered entities to provide individuals with access to their medical records; however, the Privacy Rule exempts psychotherapy notes from this requirement. Although the Center gave the complainant the opportunity to review her medical record, this did not negate the Center’s obligation to provide the complainant with a copy of her records. Among other corrective action taken, the Center provided the complainant with a copy of her medical record and revised its policies and procedures to ensure that it provides timely access to all individuals.&lt;/li&gt;
&lt;/ul&gt;&lt;div align="left"&gt;&lt;/div&gt;&lt;span style="font-size: small;"&gt;&lt;ul&gt;&lt;li&gt;A &lt;strong&gt;private practice physician who was the principal investigator of a clinical research study disclosed a list of patients and diagnostic codes&lt;/strong&gt; to a contract research organization to telephone patients for recruitment purposes. The disclosure was not consistent with documents approved by the Institutional Review Board (IRB). The private practice maintained that the disclosure to the contract research organization was permissible as a review preparatory to research. Activities considered "preparatory to research" include: preparing a research protocol; developing a research hypothesis; and identifying prospective research participants. Further, a researcher may not remove PHI from the covered entity. To remedy this situation, the private practice revised its policies and procedures regarding the disclosure of PHI and trained all physicians and staff members on the new policies and procedures. Under the revised policies and procedures, the practice may disclose PHI to an outside researcher for research recruitment, only if a valid authorization is obtained from each individual or if the covered entity obtains documentation that an alteration to or a waiver of the authorization requirement has been approved by an IRB or a Privacy Board. &lt;/li&gt;
&lt;/ul&gt;&lt;/span&gt;&lt;/span&gt;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-3329064113080043939?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Qw2id6_qpgCB8KVXrhl_8PppJEI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Qw2id6_qpgCB8KVXrhl_8PppJEI/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Qw2id6_qpgCB8KVXrhl_8PppJEI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Qw2id6_qpgCB8KVXrhl_8PppJEI/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/G2G7x3YDhEY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/3329064113080043939/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=3329064113080043939&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/3329064113080043939?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/3329064113080043939?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/G2G7x3YDhEY/annual-report-to-congress-on-hipaa.html" title="Annual Report to Congress on HIPAA Privacy Rule and Security Rule Compliance" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/09/annual-report-to-congress-on-hipaa.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D08DRHY8fCp7ImA9WhdWFU0.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-527394506507516046</id><published>2011-09-08T11:17:00.000-07:00</published><updated>2011-09-08T11:17:55.874-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-09-08T11:17:55.874-07:00</app:edited><title>Annual Report to Congress on Breaches of Unsecured Protected Health Information</title><content type="html">September 8, 2011&lt;br /&gt;
&lt;br /&gt;
The Department of Health and Human Services' Office for Civil Rights provided a report to Congress on health information breaches from September 2009 through 2010, as required under the HITECH Act. Nearly 7.9 million Americans were affected by almost 30,800 health information breaches, according to the report.&lt;br /&gt;
You can register and get a copy here:&lt;br /&gt;
&lt;a href="http://www.govinfosecurity.com/regulations.php?reg_id=2539"&gt;http://www.govinfosecurity.com/regulations.php?reg_id=2539&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Nearly 7.9 million Americans were affected by almost 30,800 health information breaches between September 2009, when a federal healthcare breach notification rule took effect, and the end of 2010, according to a new report to Congress. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The report from the Department of Health and Human Services' Office for Civil Rights shows about 7.8 million individuals were affected by 252 major breaches (incidents affecting 500 or more). In addition, about 62,000 individuals were affected by 30,521 smaller incidents. &lt;br /&gt;
&lt;br /&gt;
OCR reveals in the report that it has closed its investigation of only about 30 percent of the larger incidents, confirming that corrective action is complete. &lt;br /&gt;
&lt;br /&gt;
The office regularly updates a list of major healthcare information breaches on its website. That "wall of shame" now shows 314 major breaches from September 2009 to July 2011, affecting a total of almost 11.7 million individuals. &lt;br /&gt;
&lt;br /&gt;
Under the HITECH Act, enacted in early 2009 as part of the economic stimulus package, OCR was required to provide Congress with annual updates about breach reports it receives as a result of the HITECH-mandated breach notification rule. This week's report, however, is the first OCR has submitted to Congress.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.govinfosecurity.com/articles.php?art_id=4032"&gt;http://www.govinfosecurity.com/articles.php?art_id=4032&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-527394506507516046?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ZwazBm54YenDjXoA9xnDlojytXY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ZwazBm54YenDjXoA9xnDlojytXY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ZwazBm54YenDjXoA9xnDlojytXY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ZwazBm54YenDjXoA9xnDlojytXY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/ErdE5Ori1Ok" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/527394506507516046/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=527394506507516046&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/527394506507516046?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/527394506507516046?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/ErdE5Ori1Ok/annual-report-to-congress-on-breaches.html" title="Annual Report to Congress on Breaches of Unsecured Protected Health Information" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/09/annual-report-to-congress-on-breaches.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0YHRH84eCp7ImA9WhdXGE8.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-1634854985161316663</id><published>2011-08-31T14:11:00.000-07:00</published><updated>2011-08-31T14:12:15.130-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-31T14:12:15.130-07:00</app:edited><title>Hospital reports security breach: 1,500 Mills-Peninsula Health Services patients</title><content type="html">August 02, 2011, 03:12 AM By Michelle Durand Daily Journal Staff &lt;br /&gt;
&lt;br /&gt;
Documents containing personal information of approximately 1,500 Mills-Peninsula Health Services patients were removed from the facility over the course of a year and taken home by a mailroom employee, according to a hospital spokeswoman.&lt;br /&gt;
&lt;br /&gt;
The worker, who has since been terminated, took the documents between November 2009 and September 2010. The Burlingame hospital learned of the breach June 17 when a relative of the employee &lt;strong&gt;discovered the documents at the worker’s home and returned them to the hospital.&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
The reason for the removal is murky.&lt;br /&gt;
&lt;br /&gt;
“We don’t believe they’ve been used for anything. We believe they just sat in a box,” said Margie O’Clair, vice president of communications for Mills-Peninsula Health Services. &lt;br /&gt;
The hospital reported the incident to the &lt;strong&gt;Burlingame police who are pursuing a criminal investigation&lt;/strong&gt;, O’Clair said.&lt;br /&gt;
&lt;br /&gt;
All of the patients whose information was taken have been notified by mail although anyone with questions can contact Mills-Peninsula. The hospital is also offering one year of free credit monitoring and identity protection to the patients whose registration information, including addresses, insurance identification and Social Security numbers, were taken.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.smdailyjournal.com/article_preview.php?id=164202"&gt;http://www.smdailyjournal.com/article_preview.php?id=164202&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-1634854985161316663?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/EZ_pmmYiD13VRtXLAcD4f8AvUMw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/EZ_pmmYiD13VRtXLAcD4f8AvUMw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/EZ_pmmYiD13VRtXLAcD4f8AvUMw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/EZ_pmmYiD13VRtXLAcD4f8AvUMw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/Dtx7y_kvzqg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/1634854985161316663/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=1634854985161316663&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1634854985161316663?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/1634854985161316663?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/Dtx7y_kvzqg/hospital-reports-security-breach-1500.html" title="Hospital reports security breach: 1,500 Mills-Peninsula Health Services patients" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>2</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/08/hospital-reports-security-breach-1500.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0YCSX48eip7ImA9WhdXEUw.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-2292768358824827236</id><published>2011-08-23T07:51:00.000-07:00</published><updated>2011-08-23T07:52:48.072-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-23T07:52:48.072-07:00</app:edited><title>OCR HIPAA HotSpots</title><content type="html">Nice article from our friends at HCPRO.. Find additional detail at: &lt;a href="http://blogs.hcpro.com/hipaa/2011/08/breaking-down-ocrs-hipaa-hotspots/"&gt;http://blogs.hcpro.com/hipaa/2011/08/breaking-down-ocrs-hipaa-hotspots/&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
The Office for Civil Rights has revealed the top areas of interest on its HIPAA privacy and security compliance radar.&lt;br /&gt;
&lt;br /&gt;
Adam Greene, former senior health information technology and privacy advisor at OCR and now partner at the law firm Davis Wright Tremaine in Washington, D.C., recently discussed each hot topic with HealthLeaders Media.&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;&lt;li&gt;Hotspot: Incident detection and response (OCR’s top issue) &lt;/li&gt;
&lt;li&gt;Hotspot: Review of log access&lt;/li&gt;
&lt;li&gt;Hotspot: Secure wireless network&lt;/li&gt;
&lt;li&gt;Hotspot: Management of user access and passwords&lt;/li&gt;
&lt;li&gt;Hotspot: Theft or loss of mobile devices&lt;/li&gt;
&lt;li&gt;Hotspot: Up-to-date software&lt;/li&gt;
&lt;li&gt;Hotspot: Role based access – lack of information access management&lt;/li&gt;
&lt;/ul&gt;&lt;strong&gt;MIAOULIS NOTE&lt;/strong&gt;: Great place to focus your current risk assessment.&amp;nbsp; Ask yourself, how are you doing in each of these areas.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-2292768358824827236?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/fJ6REHxxSQx1sW9zX-a3sQFH4oU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/fJ6REHxxSQx1sW9zX-a3sQFH4oU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/fJ6REHxxSQx1sW9zX-a3sQFH4oU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/fJ6REHxxSQx1sW9zX-a3sQFH4oU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/g6TOk2cPYHM" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/2292768358824827236/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=2292768358824827236&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/2292768358824827236?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/2292768358824827236?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/g6TOk2cPYHM/ocr-hipaa-hotspots.html" title="OCR HIPAA HotSpots" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/08/ocr-hipaa-hotspots.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU8CR3s4cCp7ImA9WhdQEEs.&quot;"><id>tag:blogger.com,1999:blog-2169903479250175934.post-773502442241059172</id><published>2011-08-11T06:03:00.000-07:00</published><updated>2011-08-11T06:04:26.538-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-11T06:04:26.538-07:00</app:edited><title>HIPAA Auditors Responsible For A HIPAA Breach</title><content type="html">The company hired by the Office for Civil Rights (OCR) to conduct nationwide HIPAA privacy and security compliance audits was responsible for a breach that includes the loss of an unencrypted flash drive and affects more than 4,500 patient records.&lt;br /&gt;
&lt;br /&gt;
OCR’s request for audit proposals came in February 2011, about eight months after KPMG, LLP, reported its breach to the New Jersey healthcare system. &lt;br /&gt;
&lt;br /&gt;
KPMG, which won OCR’s $9.2 million contract for HITECH-required HIPAA audits in June 2011, told the Saint Barnabas Health Care System of West Orange, NJ, in June 2010 that a KPMG employee lost an unencrypted flash drive that may have contained a list with some patient names and information about their care, Saint Barnabas reported on its website. &lt;br /&gt;
&lt;a href="http://www.healthleadersmedia.com/page-1/PHY-269480/HIPAA-Auditor-Involved-in-Own-Data-Breach"&gt;http://www.healthleadersmedia.com/page-1/PHY-269480/HIPAA-Auditor-Involved-in-Own-Data-Breach&lt;/a&gt;##&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2169903479250175934-773502442241059172?l=www.hipaasecurityandprivacy.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ObTmdigt7cQBDKN0jAS0HTFsU9E/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ObTmdigt7cQBDKN0jAS0HTFsU9E/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ObTmdigt7cQBDKN0jAS0HTFsU9E/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ObTmdigt7cQBDKN0jAS0HTFsU9E/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/HipaaSecurityAndPrivacy/~4/KQNwujwgVV8" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.hipaasecurityandprivacy.com/feeds/773502442241059172/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2169903479250175934&amp;postID=773502442241059172&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/773502442241059172?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2169903479250175934/posts/default/773502442241059172?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/HipaaSecurityAndPrivacy/~3/KQNwujwgVV8/kpmg-hipaa-auditors-had-their-own-hipaa.html" title="HIPAA Auditors Responsible For A HIPAA Breach" /><author><name>HIPAA Security and Privacy</name><uri>http://www.blogger.com/profile/14079509898420089715</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.hipaasecurityandprivacy.com/2011/08/kpmg-hipaa-auditors-had-their-own-hipaa.html</feedburner:origLink></entry></feed>

