<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SPHER</title>
	<atom:link href="http://amsspher.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://amsspher.com</link>
	<description></description>
	<lastBuildDate>Fri, 24 May 2013 22:40:59 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Health Breach Tally: Cause for Optimism?</title>
		<link>http://amsspher.com/health-breach-tally-cause-for-optimism/</link>
		<comments>http://amsspher.com/health-breach-tally-cause-for-optimism/#comments</comments>
		<pubDate>Fri, 24 May 2013 22:40:59 +0000</pubDate>
		<dc:creator>ray.ribble</dc:creator>
				<category><![CDATA[Breach Detection Guides]]></category>
		<category><![CDATA[Healthcare Industry]]></category>
		<category><![CDATA[Privacy & Security Documents]]></category>

		<guid isPermaLink="false">http://amsspher.com/?p=784</guid>
		<description><![CDATA[<p>The Stats Are Improving, But What&#8217;s Ahead? So far, the statistics on major health data breaches for 2013 look encouraging. And the stats for 2012 showed substantial improvement vs. 2011. But could we see a surge in breach reports after &#8230; <a href="http://amsspher.com/health-breach-tally-cause-for-optimism/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://amsspher.com/health-breach-tally-cause-for-optimism/">Health Breach Tally: Cause for Optimism?</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></description>
				<content:encoded><![CDATA[<h3>The Stats Are Improving, But What&#8217;s Ahead?</h3>
<p>So far, the statistics on major health data breaches for 2013 look encouraging. And the stats for 2012 showed substantial improvement vs. 2011. But could we see a surge in breach reports after organizations begin using updated federal guidance about how to assess whether to report a breach? Only time will tell.</p>
<p>First, let&#8217;s take a look at the latest breach statistics. We&#8217;ve been crunching the numbers monthly since the Department of Health and Human Services&#8217; Office for Civil Rights began posting its &#8220;wall of shame&#8221; on its website. That tally, mandated by the HITECH Act, includes breaches affecting 500 or more individuals that have been confirmed by federal investigators since late September 2009, when the original breach notification rule kicked in.</p>
<p>&#8221; What&#8217;s incredible is that the problem of lost or stolen unencrypted devices and media shows no sign of fading away. &#8221;<br />
Related Content</p>
<p>Let&#8217;s start with the big picture. As of May 21, the ongoing tally lists 600 breaches affecting more than 22 million people. More than half of breaches have involved lost or stolen unencrypted computer devices or media. And more than 20 percent have involved a business associate of some sort.</p>
<p>The wall of shame now shows more than 140 breaches occurred in 2012, affecting a total of almost 2.6 million individuals. Only six breaches affected at least 100,000; those incidents impacted a combined total of 1.7 million individuals.</p>
<p>The 2012 figures represent a significant improvement from 2011, when there were about 160 breaches affecting roughly 11 million individuals &#8211; including eight incidents impacting an astounding combined total of about 10 million.</p>
<p>Although federal officials continually add incidents &#8211; sometimes dating back a year or more &#8211; to the tally, it&#8217;s clear that the breach numbers look a lot better for 2012 than 2011. And that&#8217;s good news, indeed. But what about 2013?</p>
<p>So far, the tally lists about 29 breaches affecting a total of more than 120,000 individuals this year. That&#8217;s right, no whopper breaches are on the list &#8211; at least not yet. But it&#8217;s still way too early to jump to any conclusions about how the breach numbers will look for this year.</p>
<p>What&#8217;s incredible, however, is that the problem of lost or stolen unencrypted devices and media shows no sign of fading away. For 2013, almost 60 percent of incidents stemmed from this cause. Last year, the percentage was about the same. And the lack of improvement in this arena is mind boggling.<br />
Hopeful Signs</p>
<p>Our recent Healthcare Information Security Today survey offers hope that healthcare organizations are taking the right steps to address this issue. The top two breach prevention action items for this year are stepping up training on privacy and security issues and encrypting mobile devices and removable media.</p>
<p>If encrypted devices are lost or stolen, the information they contain is far less likely to be breached. As a result, such losses or thefts don&#8217;t have to be reported to authorities.</p>
<p>Another important breach prevention strategy, but one that is not always practical, is to ban the storage of patient information on portable devices. Roughly half of the organizations we surveyed prohibit storage of patient data on mobile devices.</p>
<p>But training is also an essential breach prevention step. Folks need constant reminders; let&#8217;s face it, we&#8217;re all forgetful. Staff members needs to be reminded not to leave their laptops in plain view inside their parked cars. They need to be reminded to make sure any patient data on their computers is encrypted. They need to be told again and again that that they must use only secure e-mail for transmitting sensitive data. Annual training is insufficient.<br />
Notification Guidance</p>
<p>But even if breach prevention efforts improve, we could soon see an increase in the number of major breaches reported to federal authorities. That&#8217;s because the HIPAA Omnibus Rule spells out objective guidance for how to assess whether a security incident is a reportable breach. The vague &#8220;harm standard&#8221; language in the original breach notification rule was far too tough to interpret. The new guidance outlines how to do a more precise risk assessment to size up the threat to patient data. And that guidance was long overdue.</p>
<p>Will the new breach notification guidance, in fact, lead to more breaches making their way to the federal wall of shame? That&#8217;s the expectation of many regulatory experts. We&#8217;ll have to wait and see. The omnibus rule won&#8217;t be enforced until September, and organizations can use the old &#8211; or the new &#8211; notification guidance until then.</p>
<p>My fingers are crossed that the trend toward far fewer gigantic breaches that we saw in 2012 will carry over into this year. And as federal officials continue to ramp up HIPAA enforcement and publicize hefty fines for violations, that will go a long way, indeed, toward motivating healthcare organizations of all sizes to ramp up breach prevention efforts.</p>
<p>Follow Howard Anderson on Twitter: @HealthInfoSec</p>
<p>The post <a href="http://amsspher.com/health-breach-tally-cause-for-optimism/">Health Breach Tally: Cause for Optimism?</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://amsspher.com/health-breach-tally-cause-for-optimism/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ISU hands over $400K for HIPAA violation</title>
		<link>http://amsspher.com/isu-hands-over-400k-for-hipaa-violation/</link>
		<comments>http://amsspher.com/isu-hands-over-400k-for-hipaa-violation/#comments</comments>
		<pubDate>Thu, 23 May 2013 21:58:46 +0000</pubDate>
		<dc:creator>ray.ribble</dc:creator>
				<category><![CDATA[Healthcare Industry]]></category>
		<category><![CDATA[HIPAA Breach Reports]]></category>
		<category><![CDATA[Privacy & Security Documents]]></category>

		<guid isPermaLink="false">http://amsspher.com/?p=776</guid>
		<description><![CDATA[<p>Clinic disabled server firewall for nearly one year Pocatello, ID  &#124;  May 23rd, 2013 Idaho State University (pictured above)  will pay $400,000 to the U.S. Department of Health Human Services to settle alleged violations of the HIPAA Security Rule. The &#8230; <a href="http://amsspher.com/isu-hands-over-400k-for-hipaa-violation/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://amsspher.com/isu-hands-over-400k-for-hipaa-violation/">ISU hands over $400K for HIPAA violation</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></description>
				<content:encoded><![CDATA[<h2 id="page-subheader"><em>Clinic disabled server firewall for nearly one year<br />
</em></h2>
<p>Pocatello, ID  |  May 23rd, 2013</p>
<div><img alt="" src="http://www.healthcareitnews.com/sites/default/files/companion_images/idaho_state_univ._admin_bldg.jpg" /></div>
<div id="node-subheader-wrapper">
<div>
<div></div>
<div>Idaho State University (pictured above)  will pay <strong>$400,000 to the U.S. Department of Health Human Services to settle alleged violations of the HIPAA Security Rule.</strong> The settlement comes after ISU’s Pocatello Family Medicine Clinic disabled server firewall protections for a period of at least 10 months, resulting in the<strong> breach of electronic protected health information for 17,500 patients. </strong></div>
</div>
</div>
<p>ISU operates 29 outpatient clinics and is required to provide health information technology systems security at those clinics. Between four and eight of the ISU clinics are subject to the HIPAA Privacy and Security Rules, including the clinic where the breach occurred, <a href="http://www.healthcareitnews.com/directory/department-health-human-services-hhs" target="_blank">HHS</a> officials say.</p>
<div>The HHS Office for Civil Rights opened an investigation in November 2011 after ISU&#8217;s August 2011 notification of the breach, which resulted from disabling of firewall protections at servers maintained by ISU. Over the course of the investigation, agency officials say it found that, for more than three years, ISU’s risk analyses and assessments of its clinics were incomplete and inadequately identified potential risks or vulnerabilities. ISU also failed to assess the likelihood of potential risks occurring.</div>
<div></div>
<div></div>
<div><b>[See also: <a href="http://www.healthcareitnews.com/news/get-set-new-hipaa-has-teeth" target="_blank">Get set: New HIPAA has teeth</a>.]</b></div>
<div></div>
<div>OCR concluded that ISU did not apply proper security measures and policies to address risks to ePHI and did not have procedures for routine review of its information system in place, which could have detected the firewall breach much sooner.</div>
<div></div>
<div></div>
<div>“Risk analysis, ongoing risk management, and routine information system reviews are the cornerstones of an effective HIPAA security compliance program,” said OCR Director Leon Rodriguez, in a May 21 press statement. “Proper security measures and policies help mitigate potential risk to patient information.”</div>
<div></div>
<div></div>
<div>ISU has agreed to a comprehensive corrective action plan to address the issues uncovered by the investigation and its failure to ensure uniform implementation of required HIPAA Security Rule protections at each of its covered clinics.</div>
<div></div>
<div></div>
<div>To date, OCR has collected $15.3 million relating to HIPAA violations and settlements.</div>
<div></div>
<div></div>
<div>“The real purpose of breach notification is for covered entities to identify the vulnerabilities that resulted in the breach, (and) remedy those vulnerabilities in an immediate and decisive manner,” said Rodriguez, in a HIPAA session at HIMSS13. “And also for us to learn from those breach reports where those vulnerabilities are.”</div>
<div></div>
<div></div>
<div>Rodriguez pointed out that although some 65,000 breach reports have been filed with the OCR since 2009, only a handful of those have resulted in enforcement action.</div>
<div></div>
<div></div>
<div>With that said, lax policies, irresponsible behavior and the lack of proper risk analyses are nothing to joke about. Some groups have had to pay serious money for improperly handling data breaches. “We are now at a point where we have collected a total of over $15 million from our enforcement activity,” said Rodriguez, with the lion’s share coming from resolution agreements with the covered entity.</div>
<div></div>
<div></div>
<div>He cited the case of Alaska Department of Health and Social Services, which handed over $1.7 million to the OCR in June relating to a stolen USB device containing the personal health information of some 2,000 patients. This is not the typical fine, however, Rodriguez added. “A lot of the deficiencies and violations that we identified in that case,” he said, “continued well beyond the reported breach, and there was weak evidence of an effort to remedy that breach.”</div>
<div></div>
<div>
<p>Just this January, in what&#8217;s been billed as the first HIPAA breach settlement involving fewer than 500 patients, Hospice of North Idaho payed $50,000 to the Department of Health and Human Services, settling potential HIPAA violations stemming from a 2010 incident. After an unencrypted company laptop containing the electronic protected health information of 441 patients had been stolen in June 2010, officials at the HHS Office for Civil Rights began its investigation and found that HONI had not conducted adequate risk analysis to safeguard patient ePHI.</p>
</div>
<p>The post <a href="http://amsspher.com/isu-hands-over-400k-for-hipaa-violation/">ISU hands over $400K for HIPAA violation</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://amsspher.com/isu-hands-over-400k-for-hipaa-violation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>LSU database gaffe leads to HIPAA breach</title>
		<link>http://amsspher.com/lsu-database-gaffe-leads-to-hipaa-breach/</link>
		<comments>http://amsspher.com/lsu-database-gaffe-leads-to-hipaa-breach/#comments</comments>
		<pubDate>Fri, 17 May 2013 19:00:50 +0000</pubDate>
		<dc:creator>ray.ribble</dc:creator>
				<category><![CDATA[Healthcare Industry]]></category>
		<category><![CDATA[HIPAA Breach Reports]]></category>

		<guid isPermaLink="false">http://amsspher.com/?p=761</guid>
		<description><![CDATA[<p>8,300 Patients Notified SHREVEPORT, LA &#124; May 17, 2013 Siemens Healthcare and Louisiana State University at Shreveport are notifying 8,330 patients of a HIPAA breach following a database mishap that resulted in billing and treatment information being mailed to the &#8230; <a href="http://amsspher.com/lsu-database-gaffe-leads-to-hipaa-breach/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://amsspher.com/lsu-database-gaffe-leads-to-hipaa-breach/">LSU database gaffe leads to HIPAA breach</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></description>
				<content:encoded><![CDATA[<div>
<h2 id="page-subheader">8,300 Patients Notified</h2>
<p>SHREVEPORT, LA | May 17, 2013</p>
</div>
<div></div>
<div>
<p><a href="http://www.healthcareitnews.com/directory/siemens" target="_blank">Siemens</a> Healthcare and Louisiana State University at Shreveport are notifying 8,330 patients of a HIPAA breach following a database mishap that resulted in billing and treatment information being mailed to the wrong patients.</p>
<p>Officials discovered the breach March 18 after LSU began receiving calls from patients saying their bills were incorrect. &#8220;After an investigation, it was discovered that an error had occurred in one computer data entry field,&#8221; a LSU website notice reads. &#8220;When printing statements, this error caused the names and treatment information for one patient to incorrectly align with another person’s mailing address.&#8221;</p>
</div>
<div></div>
<div>LSU Shreveport Spokesperson Sally Croom said a variety of medical treament data was compromised in the breach, such as complete blood count tests, vaccinations and other medical tests. The letters did not contain Social Security numbers, financial data and dates are birth, Croom confirmed.</div>
<div></div>
<div></div>
<div>Notification letters were mailed to affected patients May 15.</div>
<div></div>
<div></div>
<div>When asked whether Siemens Healthcare or LSU were responsible for the database error, Croom said, &#8220;Our focus has been on fixing the problem . . . and that involves safeguards for the database on both our parts,&#8221; in an emailed statement to <em>Healthcare IT News</em>.</div>
<div></div>
<div></div>
<div>Added Croom, &#8220;Patient privacy is very important to us at LSU Health Shreveport, and we will continue to work with Siemens to ensure that the billing process executes correctly and without errors.&#8221;</div>
<p>The post <a href="http://amsspher.com/lsu-database-gaffe-leads-to-hipaa-breach/">LSU database gaffe leads to HIPAA breach</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://amsspher.com/lsu-database-gaffe-leads-to-hipaa-breach/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OCR HIPAA Audits – We Now Know the Protocols</title>
		<link>http://amsspher.com/ocr-hipaa-audits-we-now-know-the-protocols/</link>
		<comments>http://amsspher.com/ocr-hipaa-audits-we-now-know-the-protocols/#comments</comments>
		<pubDate>Tue, 14 May 2013 16:47:10 +0000</pubDate>
		<dc:creator>ray.ribble</dc:creator>
				<category><![CDATA[Breach Detection Guides]]></category>
		<category><![CDATA[Healthcare Industry]]></category>
		<category><![CDATA[HIPAA Breach Reports]]></category>
		<category><![CDATA[Privacy & Security Documents]]></category>

		<guid isPermaLink="false">http://amsspher.com/?p=756</guid>
		<description><![CDATA[<p>On 05.13.13 by Gerry Blass and Susan Miller Background Congress had long grumbled that HIPAA enforcement had no teeth, so within the HITECH Act they mandated that the OCR develop an audit program for all CEs and BAs, of all &#8230; <a href="http://amsspher.com/ocr-hipaa-audits-we-now-know-the-protocols/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://amsspher.com/ocr-hipaa-audits-we-now-know-the-protocols/">OCR HIPAA Audits – We Now Know the Protocols</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></description>
				<content:encoded><![CDATA[<p><em>On 05.13.13 by <a title="Posts by Gerry Blass" href="http://blog.complyassistant.com/author/gerry/">Gerry Blass</a> and <a title="Posts by Susan Miller" href="http://blog.complyassistant.com/author/susan/">Susan Miller</a></em></p>
<p><strong>Background</strong></p>
<p><strong></strong>Congress had long grumbled that HIPAA enforcement had no teeth, so within the HITECH Act they mandated that the OCR develop an audit program for all CEs and BAs, of all sizes.</p>
<p>The OCR began this program in 2011 with 20 audits, and found that some covered entities had done very little to fulfill the HIPAA privacy, security,  and breach requirements. No surprise perhaps!</p>
<p>In 2012 the OCR did 95 more audits and found the same thing, even though  the healthcare industry had seen the results of the 2011 audits. Perhaps the missing ingredients surrounding the OCR audits were the audits themselves. How were they being conducted?</p>
<p><strong>Good News – Published Protocols</strong></p>
<p>The good news is that in the summer of 2012 the OCR published the audit protocols that the OCR  through KPMG, are using to audit the healthcare industry. The protocols were updated in September 2012. There are a total of 169 protocols – 78 for HIPAA security, 81 for HIPAA privacy, and 10 for HIPAA breach.</p>
<p>You can find the protocols <a href="http://www.hhs.gov/ocr/privacy/hipaa/enforcement/audit/protocol.html">here</a>.</p>
<p>Susan McAndrew, JD, leader of all things HIPAA – HITECH at the Office for Civil Rights has been out talking at conferences about both the audits and the Omnibus rules since 2009, saying that HIPAA CEs and BAs  should have a robust HIPAA Privacy and Security compliance program, including:</p>
<ul>
<li>employee training.</li>
<li>vigilant implementation of policies and procedures.</li>
<li>a prompt action plan to respond to incidents and breaches.</li>
<li>regular internal audits.</li>
</ul>
<p>You might remember that these bullets are 4 of the 7 parts that the Department of Health and Human Services (HHS), Office of Inspector General (OIG) had recommended for a healthcare compliance program beginning in 1999.</p>
<p>So why do we think all of this is good news?  Because now all CEs and BAs are in a position to know how to prepare for an OCR audit, and have another motivating factor to overcome organizational challenges that they may be dealing with, such as a limited budget or lack of an organizational mandate.</p>
<p>The combination of the OCR audits, the potential large financial penalties and lawsuits and bad press for a breach of protected health information along with CE attestation for Meaningful Use measures, including information security risk analysis, we believe that the healthcare industry is finally sensing a higher financial risk for non-compliance vs. the cost to comply.</p>
<p><em><strong>For example, a recent industry survey found that the cost is an average of $200 per individual if you have a breach.  This alone is $100.000 if you have a violation of no more than 500 individuals.  Add to this the millions in fines that OCR is now handing out, plus the cost of mitigation.  So, the loss of a laptop may cost many large CEs $2 million, even if they self report.</strong></em></p>
<p><strong>The OCR Audit Letter</strong></p>
<p>The first thing that arrives when you are audited is a letter from OCR and its contractor, KPMG, which includes a  two (2)-page list of requested documentation. The obvious requests are for policies and procedures. In addition there are requests for documentation that shows evidence of operational compliance with policies and procedures, such as ‘HITECH breach notification process, entity-level risk assessment documentation and capabilities’<em>. </em>Some documentation in the protocol list may need to be created from scratch based on actual processes. So it will take time to get it all together.</p>
<p>You can attain a copy of the 2-page document request free for download <a href="http://www.malverngroup.com/Briefings.html">here</a>. (Refer to the OCR Audit Document Request section).</p>
<p><strong>Interesting Points</strong></p>
<p>Here are some interesting points regarding the OCR audits. First, the mandate for the audits is within a law only, the HITECH Act. Second, the audits are not part of the HIPAA general administrative requirements that outline HIPAA enforcement, preemption of state law, compliance and enforcement, imposition of civil money penalties, and procedures for hearing.</p>
<p><em>However, there is an interconnection between the OCR audits and HIPAA enforcement in that if major HIPAA compliance gaps are identified during an audit OCR will do a further investigation as outlined in the HIPAA enforcement regulation.</em></p>
<p><strong>Doing nothing can cost a lot!</strong></p>
<p>While it is true that CEs and BAs are never 100% vulnerability free with HIPAA-HITECH compliance especially due to the need for change management,  doing little to nothing can no longer be perceived as a low risk / low cost decision. In other words, the cost of doing nothing is potentially and dramatically much higher than the cost of implementing a culture of compliance (aka-the opposite of willful neglect).  And if you have a good culture of compliance within your organization you should have less risk for security incidents or breach violations.</p>
<p>To implement a culture of compliance, CEs and BAs need to monitor HIPAA compliance continuously and mitigate gaps, especially the high and medium risk gaps. The key word is continuously which means that the process never ends.</p>
<p>Here are some of the elements that lead to a culture of compliance:</p>
<ul>
<li>Implementing written policies, procedures and standards of conduct.</li>
<li>Designating a compliance officer and a compliance committee.</li>
<li>Designating privacy and security officers.</li>
<li>Conducting effective and on-going training and education of all of the HIPAA privacy, security, and breach requirements.</li>
<li>Enforcing the HIPAA security, breach and privacy standards and implementation specifications through well-publicized disciplinary guidelines and developing policies and procedures that address sanctioning the workforce.</li>
<li>Conducting periodic assessments, audits and mitigation.</li>
<li>Responding promptly to detected offenses, developing corrective action, and reporting to OCR.</li>
<li>Document, document, and then document.</li>
</ul>
<p><strong>2013 – More to come!</strong></p>
<p>In 2013 the OCR may begin auditing BAs in addition to  CEs. Plus, the OCR has promised to review the 2012 audits against its audit protocols and update the protocols accordingly. We can expect to see a continual increase in the number of audits conducted each year going forward which increases the likelihood that your organization will eventually be audited.</p>
<p><strong>Conclusion</strong></p>
<p>The time to prepare for an OCR audit is now, if not yesterday. We recommend that CEs and BAs conduct internal audits based on the published OCR protocols and mitigate the gaps found. CEs and BAs may be surprised to see how difficult it is to show documented evidence of due diligence for compliance with their policies and procedures. Processes that support policies may be in place, but gathering documented evidence of the processes can be time consuming. So begin now. Two weeks is not enough time to prepare. And CEs and BAs should consider hiring an independent third party for guidance and to assess their audit readiness.</p>
<p><strong><em>About the Authors</em></strong></p>
<p>Gerry Blass has over 35 years of experience in healthcare IT and compliance. Gerry provides IT and compliance consulting services and software called ComplyAssistant that automates the management and documentation of healthcare compliance activities. Gerry is the President &amp; CEO of <a href="http://www.blassaffiliates.com">Blass Consulting and Compliance LLC</a>.</p>
<p>Susan A Miller, JD has 40 years of professional leadership experience spanning teaching, biochemistry research and law. Since 2002, Susan has provided independent consultation and legal services to numerous healthcare entities including NIST and HHS.  She has co-authored two OCR audit protocol prep-books, HIPAA Security Audit Prep Book, and HIPAA Breach &amp; Privacy Audit Prep Book. They are published at <a href="http://www.malverngroup.com/New_Publications.html">http://www.malverngroup.com/New_Publications.html</a>.</p>
<p><em>Blass and Miller are co-founders of HIPAA 411, a linked-in group.</em></p>
<p>The post <a href="http://amsspher.com/ocr-hipaa-audits-we-now-know-the-protocols/">OCR HIPAA Audits – We Now Know the Protocols</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://amsspher.com/ocr-hipaa-audits-we-now-know-the-protocols/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Half of healthcare orgs aren’t sure they can detect all patient data privacy &amp; security breaches</title>
		<link>http://amsspher.com/half-of-healthcare-orgs-arent-sure-they-can-detect-all-patient-data-privacy-security-breaches/</link>
		<comments>http://amsspher.com/half-of-healthcare-orgs-arent-sure-they-can-detect-all-patient-data-privacy-security-breaches/#comments</comments>
		<pubDate>Wed, 08 May 2013 20:22:20 +0000</pubDate>
		<dc:creator>ray.ribble</dc:creator>
				<category><![CDATA[Healthcare Industry]]></category>
		<category><![CDATA[HIPAA Breach Reports]]></category>
		<category><![CDATA[Privacy & Security Documents]]></category>

		<guid isPermaLink="false">http://amsspher.com/?p=749</guid>
		<description><![CDATA[<p>by Deanna Pogorelc As the use of mobile devices, file-sharing software and cloud services has been on the rise among healthcare providers, data breaches have been rising steadily along with them. A hefty 94 percent of healthcare organizations who participated &#8230; <a href="http://amsspher.com/half-of-healthcare-orgs-arent-sure-they-can-detect-all-patient-data-privacy-security-breaches/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://amsspher.com/half-of-healthcare-orgs-arent-sure-they-can-detect-all-patient-data-privacy-security-breaches/">Half of healthcare orgs aren’t sure they can detect all patient data privacy &#038; security breaches</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>by <a title="Posts by Deanna Pogorelc" href="http://medcitynews.com/author/dpogorelc/" rel="author">Deanna Pogorelc</a></p>
<div>
<div>
<div>
<p><img alt="Computer-Data-Privacy-and-Secu-940581" src="http://medcitynews.wpengine.netdna-cdn.com/wp-content/uploads/Computer-Data-Privacy-and-Secu-940581.jpg" width="472" height="316" /></p>
<p>As the use of <a href="http://medcitynews.com/tag/health-it/">mobile devices, file-sharing software and cloud services</a> has been on the rise among healthcare providers, data breaches have been rising steadily along with them. A hefty 94 percent of healthcare organizations who participated in an annual survey said they had at least one data breach in the past two years.</p>
<p>What’s more startling is that 45 percent said they’d had more than five incidents, and half reported little or no confidence that their organization had the ability to detect all patient data loss or theft.</p>
<p>For its <a href="http://www2.idexpertscorp.com/ponemon2012/">Third Annual Study on Patient Privacy &amp; Data Security</a>, published in December, the Ponemon Institute surveyed 324 administrative and clinical personnel at healthcare facilities – most of them hospitals or clinics that are part of a network or integrated delivery systems. Those personnel reported that the most commonly breached data are medical files and billing and insurance records, lost or stolen most often from a desktop, laptop or smartphone.</p>
<p>Interestingly, although the number of data breaches has gone up, those surveyed reported increasing confidence that patient billing information and medical records would not be susceptible to loss or theft. In contrast, many more felt that employee records were the most susceptible data.</p>
<p>While many new technology applications pose the advantage of greater efficiency and convenience to healthcare providers, they also open the door for the unsecure transmission of data that may be behind some of these breaches. For example, eight of 10 organizations surveyed allow personnel to <a href="http://medcitynews.com/2013/02/dont-wait-for-lawmakers-set-up-network-security-standards-for-the-byod-era-now/">bring their own devices</a> and use them to connect to the organization’s network. More than 60 percent of the organizations surveyed also reported moderate or heave cloud usage, although almost 50 percent said they weren’t confident that the cloud was secure.</p>
<p>While most organizations reported compliance with periodic HIPAA privacy and security awareness training for staff, they still reported that the second-most-common cause of lost or stolen data was an employee mistake, following a lost or stolen computing device.</p>
<p>The graphic below, put together by BackgroundCheck.org, highlights some of the other interesting points from this survey.</p>
<p><a href="http://www.backgroundcheck.org/94-of-healthcare-organizations-breached/"><img alt="94% of Healthcare Organizations Breached" src="https://s3.amazonaws.com/infographics/Healthcare-Breaches-800.png" width="500" border="0" /></a></p>
<p><em>[Computer privacy photo from <a href="http://www.bigstockphoto.com/image-940581/stock-photo-computer-data-privacy-and-security">BigStock Photos</a>]</em></p>
</div>
</div>
</div>
<p>&nbsp;</p>
<p>The post <a href="http://amsspher.com/half-of-healthcare-orgs-arent-sure-they-can-detect-all-patient-data-privacy-security-breaches/">Half of healthcare orgs aren’t sure they can detect all patient data privacy &#038; security breaches</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://amsspher.com/half-of-healthcare-orgs-arent-sure-they-can-detect-all-patient-data-privacy-security-breaches/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Survey reveals healthcare data security priorities</title>
		<link>http://amsspher.com/survey-reveals-healthcare-data-security-priorities/</link>
		<comments>http://amsspher.com/survey-reveals-healthcare-data-security-priorities/#comments</comments>
		<pubDate>Tue, 07 May 2013 17:30:23 +0000</pubDate>
		<dc:creator>ray.ribble</dc:creator>
				<category><![CDATA[Breach Detection Guides]]></category>
		<category><![CDATA[Healthcare Industry]]></category>
		<category><![CDATA[Privacy & Security Documents]]></category>

		<guid isPermaLink="false">http://amsspher.com/?p=742</guid>
		<description><![CDATA[<p>Written by: Patrick Ouellette   &#124;   Date May 7, 2013 The second annual Healthcare Information Security Today survey revealed six emerging healthcare security trends. It hit on all of the key healthcare security pain points for professionals and showed &#8230; <a href="http://amsspher.com/survey-reveals-healthcare-data-security-priorities/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://amsspher.com/survey-reveals-healthcare-data-security-priorities/">Survey reveals healthcare data security priorities</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>Written by: <strong>Patrick Ouellette</strong>   |   Date May 7, 2013<strong><br />
</strong></p>
<p>The second annual <em><a title="Healthcare Information Security" href="http://docs.ismgcorp.com/files/handbooks/HIS-Survey-2012/HIS_Survey_Report_2012.pdf">Healthcare Information Security Today</a></em><a href="http://docs.ismgcorp.com/files/handbooks/HIS-Survey-2012/HIS_Survey_Report_2012.pdf"> survey</a> revealed six emerging healthcare security trends. It hit on all of the key healthcare security pain points for professionals and showed how organizations are dealing with new HIPAA rules and what they’re doing policy and technology-wise to improve their patient data security methods.</p>
<p>Participants in the survey gave responses during the fall of 2012 and hold titles that range from director of IT security to chief information officer, but all 200 respondents have a heavy hand in securing their organization’s health data.</p>
<p><strong>1. <a title="Glossary: Data Breach" href="http://healthitsecurity.com/glossary/data-breach/">Data breach</a> prevention</strong></p>
<p>Organizations believe training is the key to avoiding health data breaches, as 73 percent of respondents said they planned on ramping up internal privacy and security training.</p>
<p><a href="http://healthitsecurity.com/2013/04/15/survey-reveals-healthcare-data-security-priorities-concerns/breachprevention1/" rel="attachment wp-att-7758"><img title="BreachPrevention1" alt="" src="http://healthitsecurity.com/wp-content/uploads/BreachPrevention1.jpg" width="500" height="400" /></a></p>
<p>Some other noteworthy data breach numbers included:</p>
<p>- 40 percent of respondents saying that they experienced misdirected fax or incidental postal mailing breaches in the past year, as opposed to only 8 percent suffering hacker attacks.</p>
<p>- Only 6 percent of respondents referred to their organization’s capabilities to prevent internal security threats as “excellent.”</p>
<p>- 60 percent of organizations say their training and awareness rank as needing improvement-to-adequate.</p>
<p><strong>2. Data <a title="Glossary: Encryption" href="http://healthitsecurity.com/glossary/encryption/">encryption</a> still lagging</strong></p>
<p>The encryption section explained that while organizations seem to be aware of the need to implement encryption, finding the best ways to deploy these <a title="Glossary: Technical Safeguards" href="http://healthitsecurity.com/glossary/technical-safeguards/">technical safeguards</a> seems to elude many of them. One surprising statistic was only 45 percent saying their organization encrypts mobile <a title="Glossary: Storage" href="http://healthitsecurity.com/glossary/storage/">storage</a> media and only 47 percent encrypt data being sent across their virtual private network (VPN). These numbers will have to continue to improve if healthcare organizations are going to keep up with enterprise and bank security innovation.</p>
<p><strong>3. Risk assessment education need improvement</strong></p>
<p>About one-third of respondents have not conducted a detailed information technology security risk assessment/analysis within the past year and the majority of those (62 percent) of those organizations were spurred by the HITECH EHR Incentive Program. And while 83 percent of organizations updated their security policies in the past year, a mere 53 percent have enhanced security education as result of their risk assessments.</p>
<p><strong>4. Data security priorities</strong></p>
<p>The three highest-ranked priorities for healthcare security professionals were refining regulatory compliance efforts (55 percent), bettering security awareness/education (45 percent) and spotting data breaches (34 percent).</p>
<p><strong>5. <a title="Glossary: BYOD" href="http://healthitsecurity.com/glossary/byod/">BYOD</a> emerging as popular option</strong></p>
<p>Not exactly a shocking development here, as 58 percent said they allow clinical staff to BYOD and about half use an automatic timeout technology or use remote wipe to safeguard the devices. But only 46 percent encrypt them, which should be a concern as BYOD numbers increase.</p>
<p>Remote access is another area of interest to security pros:</p>
<p><a href="http://healthitsecurity.com/2013/04/15/survey-reveals-healthcare-data-security-priorities-concerns/breachprevention2/" rel="attachment wp-att-7759"><img title="BreachPrevention2" alt="" src="http://healthitsecurity.com/wp-content/uploads/BreachPrevention2.jpg" width="500" height="400" /></a></p>
<p><strong>6. Cloud security still a worry</strong></p>
<p>Because many organizations view security policy and HIPAA enforcement as barriers, only 64 percent store health data in the cloud and only 14 percent of those who do have high confidence in maintaining secure data. Out of all these categories, the cloud bears the most watching because implementing these technologies will continue to make more and more fiscal sense and technical safeguards for cloud data have improved more than most organizations realize. But with the new HIPAA omnibus rule in effect, there will be more pressure on cloud vendors (<a title="Glossary: Business Associate" href="http://healthitsecurity.com/glossary/business-associate/">business associates</a>) to prove they’ll sign a business associate agreement (BAA) and truly keep the data safe.</p>
<p>The post <a href="http://amsspher.com/survey-reveals-healthcare-data-security-priorities/">Survey reveals healthcare data security priorities</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://amsspher.com/survey-reveals-healthcare-data-security-priorities/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Utah health data breach: A lesson in the myriad benefits of prevention</title>
		<link>http://amsspher.com/utah-health-data-breach-a-lesson-in-the-myriad-benefits-of-prevention/</link>
		<comments>http://amsspher.com/utah-health-data-breach-a-lesson-in-the-myriad-benefits-of-prevention/#comments</comments>
		<pubDate>Mon, 06 May 2013 21:31:07 +0000</pubDate>
		<dc:creator>ray.ribble</dc:creator>
				<category><![CDATA[Healthcare Industry]]></category>
		<category><![CDATA[HIPAA Breach Reports]]></category>
		<category><![CDATA[Privacy & Security Documents]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://amsspher.com/?p=726</guid>
		<description><![CDATA[<p>May 1, 2013 &#124; By Susan D. Hall The theft of Social Security numbers provides cyber criminals a gift that keeps on giving, posing the potential for fraud for years. When Eastern European hackers gained access to healthcare information for &#8230; <a href="http://amsspher.com/utah-health-data-breach-a-lesson-in-the-myriad-benefits-of-prevention/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://amsspher.com/utah-health-data-breach-a-lesson-in-the-myriad-benefits-of-prevention/">Utah health data breach: A lesson in the myriad benefits of prevention</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>May 1, 2013 | By <a title="View author profile." href="http://www.fiercehealthit.com/author/Susan%20D.%20Hall" rel="author">Susan D. Hall</a></p>
<div>The theft of Social Security numbers provides cyber criminals a gift that keeps on giving, posing the potential for fraud for years. When <a href="http://www.fiercehealthit.com/story/health-department-breach-impacts-24k-medicaid-patients/2012-04-05" target="_blank">Eastern European hackers gained access to healthcare information for roughly 780,000 Medicaid participants in Utah in March 2012</a>, the Social Security numbers for 280,000 beneficiaries were compromised.Al Pascual (pictured), a senior analyst of security, risk and fraud at Javelin Strategy &amp; Research, analyzed that breach, among others, for a Data Breach Fraud Impact Report, due out later this month.&#8221;Data breaches are precursors to fraud, and failing to protect [personally identifiable information] exposes everyone to pain, Pascual wrote in a blog <a href="http://www.javelinstrategy.com/blog/2013/04/28/financial-pain-ensues-when-custodians-of-health-fail-to-be-good-stewards-of-privacy/" target="_blank">post</a>. Pascual spoke to <em>FierceHealthIT</em> about the Utah breach.</p>
<div>
<div>
<div>
<p><img alt="" src="http://assets.fiercemarkets.com/public/newsletter/alpascual.jpg" width="200" height="265" align="right" />The theft of Social Security numbers provides cyber criminals a gift that keeps on giving, posing the potential for fraud for years. When <a href="http://www.fiercehealthit.com/story/health-department-breach-impacts-24k-medicaid-patients/2012-04-05" target="_blank">Eastern European hackers gained access to healthcare information for roughly 780,000 Medicaid participants in Utah in March 2012</a>, the Social Security numbers for 280,000 beneficiaries were compromised.</p>
<p>Al Pascual (pictured), a senior analyst of security, risk and fraud at Javelin Strategy &amp; Research, analyzed that breach, among others, for a Data Breach Fraud Impact Report, due out later this month.</p>
<p>&#8220;Data breaches are precursors to fraud, and failing to protect [personally identifiable information] exposes everyone to pain, Pascual wrote in a blog <a href="http://www.javelinstrategy.com/blog/2013/04/28/financial-pain-ensues-when-custodians-of-health-fail-to-be-good-stewards-of-privacy/" target="_blank">post</a>. Pascual spoke to <em>FierceHealthIT</em> about the Utah breach.</p>
<p><strong><em>FierceHealthIT</em>: What did your analysis of the Utah breach reveal?</strong></p>
<p><strong>Pascual</strong><strong>:</strong> We looked at a number of breaches across various industries and found that if you were a data breach victim in 2010, the odds that you could become a victim of fraud were better than one in 10. This past year, if you were a data breach victim, the odds that you would become a victim of fraud were one in 4. What we&#8217;re finding is that criminals are getting better at using data breach information to commit fraud. They&#8217;re getting better and finding it, better at selling it. Criminals aren&#8217;t digging through trash anymore, they&#8217;re not stealing your mail to get your information. They&#8217;re getting it through data breaches and malware.</p>
<p>We want to talk about not only what the state of Utah could have done better, but also, now that the breach has happened, what that means for the financial industry. The industry is pretty mindful of potential breaches with [credit card] information, but when a breach occurs and they don&#8217;t have confirmation that it ties in with any of your accounts, they don&#8217;t do anything at all. Financial institutions in Utah need to be reaching out to customers and telling them that if they were a victim of that breach, here&#8217;s what they need to do to protect their accounts. Especially with it being Social Security numbers. That&#8217;s like the keys to the castle.</p>
<p>We looked at account takeovers last year and over half of those victims had their Social Security number breached. That Social Security number can be used to lock consumers out of their accounts, to wire large sums of money … In the age of voice recognition and other technologies, we&#8217;re still relying on nine digits and putting consumers at risk.</p>
<p><strong><em>FierceHealthIT</em>: After the breach, did the state of Utah react appropriately?</strong></p>
<p><strong>Pascual</strong><strong>: </strong>I think the state of Utah approached it the right way. Of course, the CTO resigned. He basically took responsibility for what happened. It happened because they didn&#8217;t follow some very basic steps.</p>
<p>After the fact, they&#8217;ve hired an auditor, they&#8217;re setting up a panel to look at best practices, they launched IRIS (an identity theft reporting information system), they&#8217;ve increased their budget and staff. They&#8217;ve done what they need to do post-breach. That it had to happen afterward is a shame. Now they&#8217;re pulling out the stops. They&#8217;ve had a couple of incidences since&#8211;no system is perfect&#8211;but they&#8217;ve done quite a few things that they should have done earlier.</p>
<p><strong><em>FierceHealthIT</em>: What should have been done to prevent the breach?</strong></p>
<p><strong>Pascual</strong><strong>:</strong> They didn&#8217;t have system lifecycle management in place&#8211;some controls or a checklist. In decommissioning a server and lighting up a test server and transferring information from one to the other, without that checklist in place, they didn&#8217;t realize that their contractor never changed default settings on [the new server.] It likely had a default password on it, so that opened them up to this breach.</p>
<p>They didn&#8217;t do a risk assessment. If they had done a risk assessment, they would have realized they were storing 280,000 Social Security numbers that were not encrypted. Yet they&#8217;re under the heavy hand of regulation. They have to worry about HIPAA, about HITECH. If you&#8217;re holding something of value and you could be held liable and fined for not protecting it, then you&#8217;re going to protect it. So these are things that businesses that are storing extensive amounts of consumer information should be doing. It&#8217;s costing between $2 million and $10 million to resolve this, but it would have cost only a fraction of that to do what they needed to do in the first place.</p>
<p><strong><em>FierceHealthIT</em>: Has any identify theft been reported as a result of that breach?</strong></p>
<p><strong>Pascual</strong><strong>:</strong> It has not. It&#8217;s very, very difficult, though, to tie any piece of information to a breach in and of itself. A Social Security number can be lost through a variety of channels. Though a Social Security number was lost, it could have been through malware, it could have been stolen from a healthcare office somewhere else. When we ask consumers precisely how their information was lost when a fraud has been committed, we can only get an answer four out of 10 times. That&#8217;s not an easy thing for law enforcement, either.</p>
<p>But the information lost in this case is Social Security numbers. They&#8217;re good for a lifetime. Although we haven&#8217;t seen any crime yet that we can tie back, we still have 20, 30, 40 years to watch and see.</p>
<p>We&#8217;re projecting 122,000 cases of fraud as a result. Data breach victims who later become victims of fraud will end up each spending $770 out of pocket to resolve the fraud. They&#8217;re going to spend about 20 hours each resolving it. Then there&#8217;s the cost of fraud that&#8217;s borne by the business. For each incidence of fraud, we&#8217;re projecting it will cost of $3,327.</p>
</div>
</div>
</div>
</div>
<p>The post <a href="http://amsspher.com/utah-health-data-breach-a-lesson-in-the-myriad-benefits-of-prevention/">Utah health data breach: A lesson in the myriad benefits of prevention</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://amsspher.com/utah-health-data-breach-a-lesson-in-the-myriad-benefits-of-prevention/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Perspective on healthcare data breaches: Verizon report</title>
		<link>http://amsspher.com/perspective-on-healthcare-data-breaches-verizon-report/</link>
		<comments>http://amsspher.com/perspective-on-healthcare-data-breaches-verizon-report/#comments</comments>
		<pubDate>Thu, 02 May 2013 17:14:49 +0000</pubDate>
		<dc:creator>ray.ribble</dc:creator>
				<category><![CDATA[Breach Detection Guides]]></category>
		<category><![CDATA[Healthcare Industry]]></category>
		<category><![CDATA[HIPAA Breach Reports]]></category>
		<category><![CDATA[Privacy & Security Documents]]></category>

		<guid isPermaLink="false">http://amsspher.com/?p=732</guid>
		<description><![CDATA[<p>By: Patrick Ouellette, Health IT Security (A Perspective on healthcare data breaches)  A common refrain among those outside the healthcare industry is that healthcare has a ways to go in catching up with the enterprise in security technology. While this &#8230; <a href="http://amsspher.com/perspective-on-healthcare-data-breaches-verizon-report/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://amsspher.com/perspective-on-healthcare-data-breaches-verizon-report/">Perspective on healthcare data breaches: Verizon report</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>By: <strong>Patrick Ouellette, Health IT Security</strong></p>
<p>(<em>A Perspective on healthcare data breaches)</em>  A common refrain among those outside the healthcare industry is that healthcare has a ways to go in catching up with the enterprise in security technology. While this is largely true, Verizon’s <em><a href="http://www.verizonenterprise.com/resources/reports/rp_data-breach-investigations-report-2012-press_en_xg.pdf">2012 </a><a title="Glossary: Data Breach" href="http://healthitsecurity.com/glossary/data-breach/">Data Breach</a> Investigations Report</em> revealed that healthcare is far from the most-afflicted industry when it comes to data breaches. A mere 7 percent of the industry groups represented in the study came from healthcare/social assistance. Instead, accommodation and food services led the way with 54 percent of total data breaches in 2012.</p>
<p>Though healthcare didn’t play a big part in the results, it’s important to look at other industries’ data breach struggles. The results didn’t deviate much from Verizon’s 2011 report, with the exception of new hacking technologies as hacking was involved in 52 percent of the 2012 report’s 621 confirmed data breaches and 47,000 reported <a title="Glossary: Security Incident" href="http://healthitsecurity.com/glossary/security-incident/">security incidents</a>. Another 40 percent used malware, 35 percent were physical attacks and 29 percent involved phishing.</p>
<p><a href="http://healthitsecurity.com/2013/04/24/perspective-on-healthcare-data-breaches-verizon-report/verizonbreach1/" rel="attachment wp-att-7939"><img title="VerizonBreach1" alt="" src="http://healthitsecurity.com/wp-content/uploads/VerizonBreach1.jpg" width="500" height="150" /></a></p>
<p>Figure 3: Data Breaches: Including Healthcare</p>
<p><strong>Threat agents</strong></p>
<p>The report specifies three primary categories of threat agents, external, internal and partner.</p>
<p><em>- External threats originate from sources outside of the organization and its network of partners. Examples include former employees, lone hackers, organized criminal groups, and government entities, External agents also include environmental events such as floods, earthquakes and power disruptions.</em></p>
<p><em>- Internal threats are those originating from within the organization. This encompasses company executives, employees, independent contractors, interns, etc…, as well as internal infrastructure. Insiders are trusted and privileged (some more than others).</em></p>
<p><em>- Partners include any third party sharing a business relationship with the organization. This includes suppliers, vendors, hosting providers, outsourced IT support, etc. Some level of trust and privilege is usually implied between business partners.</em></p>
<p><em></em><a href="http://healthitsecurity.com/2013/04/24/perspective-on-healthcare-data-breaches-verizon-report/verizonbreach_threatagents/" rel="attachment wp-att-7942"><img title="VerizonBreach_ThreatAgents" alt="" src="http://healthitsecurity.com/wp-content/uploads/VerizonBreach_ThreatAgents.jpg" width="500" height="300" /></a></p>
<p>Figure:  Healthcare Data Breaches &#8211; Threat agents over time</p>
<p><strong>Malware</strong></p>
<p>Common malware functions are logging keystrokes (and other forms of user input), sending data to external locations, and backdoors. None of these functionalities are mutually exclusive and it’s common for a single piece of malware to feature several components.</p>
<p><a href="http://healthitsecurity.com/2013/04/24/perspective-on-healthcare-data-breaches-verizon-report/verizonbreach_malware/" rel="attachment wp-att-7940"><img title="VerizonBreach_Malware" alt="" src="http://healthitsecurity.com/wp-content/uploads/VerizonBreach_Malware.jpg" width="500" height="200" /></a></p>
<p>Figure:  Healthcare Data Breaches &#8211; Malware</p>
<p>New hacking methods are also a factor:</p>
<p><a href="http://healthitsecurity.com/2013/04/24/perspective-on-healthcare-data-breaches-verizon-report/verizonbreach_hackingmethods/" rel="attachment wp-att-7941"><img title="VerizonBreach_HackingMethods" alt="" src="http://healthitsecurity.com/wp-content/uploads/VerizonBreach_HackingMethods.jpg" width="500" height="300" /></a></p>
<p>The post <a href="http://amsspher.com/perspective-on-healthcare-data-breaches-verizon-report/">Perspective on healthcare data breaches: Verizon report</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://amsspher.com/perspective-on-healthcare-data-breaches-verizon-report/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>EXPERT PANEL PROJECTS GROWTH IN IN THE ADOPTION AND MEANINGFUL USE OF ELECTRONIC HEALTH RECORDS (EHRs)</title>
		<link>http://amsspher.com/expert-panel-projects-growth-in-in-the-adoption-and-meaningful-use-of-electronic-health-records-ehrs/</link>
		<comments>http://amsspher.com/expert-panel-projects-growth-in-in-the-adoption-and-meaningful-use-of-electronic-health-records-ehrs/#comments</comments>
		<pubDate>Tue, 30 Apr 2013 17:34:20 +0000</pubDate>
		<dc:creator>ray.ribble</dc:creator>
				<category><![CDATA[Healthcare Industry]]></category>

		<guid isPermaLink="false">http://amsspher.com/?p=716</guid>
		<description><![CDATA[<p>The authors of “Forecasting the Use of Electronic Health Records: An Expert Opinion Approach,” published in Volume 3, Issue 2 of the Medicare &#38; Medicaid Research Review, convened a group of 18 experts from industry, academia, and government to forecast &#8230; <a href="http://amsspher.com/expert-panel-projects-growth-in-in-the-adoption-and-meaningful-use-of-electronic-health-records-ehrs/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://amsspher.com/expert-panel-projects-growth-in-in-the-adoption-and-meaningful-use-of-electronic-health-records-ehrs/">EXPERT PANEL PROJECTS GROWTH IN IN THE ADOPTION AND MEANINGFUL USE OF ELECTRONIC HEALTH RECORDS (EHRs)</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>The authors of “<a title="Full Article Download" href="http://http://www.cms.gov/Research-Statistics-Data-and-Systems/Research/MMRR/Downloads/MMRR2013_003_02_a02.pdf">Forecasting the Use of Electronic Health Records: An Expert Opinion Approach,” published in Volume 3, Issue 2 of the Medicare &amp; Medicaid Research Review</a>, convened a group of 18 experts from industry, academia, and government to forecast the adoption and meaningful use of EHRs among office-based physicians from 2012 to 2019.</p>
<p>The expert panel projects that 65 percent of primary care physicians in large group practices, 45 percent of primary care physicians in small group practices, and 44 percent of all other specialists could achieve the meaningful use of certified EHR technology by 2015. The expert panel also predicts that meaningful use rates could increase to 80 percent, 65 percent, and 66 percent in 2019 for these three groups, respectively. The information from this study is particularly valuable due to a high degree of uncertainty in a new policy environment and could help inform and evaluate CMS and ONC programs.</p>
<p>Click <a title="Panel report findings - EHR" href="http://http://www.cms.gov/Research-Statistics-Data-and-Systems/Research/MMRR/Downloads/MMRR2013_003_02_a02.pdf">here </a>or on the link above to view the entire report.</p>
<p>&nbsp;</p>
<p>The post <a href="http://amsspher.com/expert-panel-projects-growth-in-in-the-adoption-and-meaningful-use-of-electronic-health-records-ehrs/">EXPERT PANEL PROJECTS GROWTH IN IN THE ADOPTION AND MEANINGFUL USE OF ELECTRONIC HEALTH RECORDS (EHRs)</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://amsspher.com/expert-panel-projects-growth-in-in-the-adoption-and-meaningful-use-of-electronic-health-records-ehrs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pairing HIPAA and HITECH Compliance</title>
		<link>http://amsspher.com/pairing-hipaa-and-hitech-compliance/</link>
		<comments>http://amsspher.com/pairing-hipaa-and-hitech-compliance/#comments</comments>
		<pubDate>Mon, 29 Apr 2013 22:19:24 +0000</pubDate>
		<dc:creator>ray.ribble</dc:creator>
				<category><![CDATA[Breach Detection Guides]]></category>
		<category><![CDATA[Healthcare Industry]]></category>
		<category><![CDATA[HIPAA Breach Reports]]></category>
		<category><![CDATA[Privacy & Security Documents]]></category>

		<guid isPermaLink="false">http://amsspher.com/?p=723</guid>
		<description><![CDATA[<p>Federal Privacy Officer Offers Insights The privacy and security provisions of the HIPAA Omnibus Rule and the HITECH Act electronic health record incentive program &#8220;dovetail together quite nicely,&#8221; says Joy Pritts, chief privacy officer at the HHS Office of the &#8230; <a href="http://amsspher.com/pairing-hipaa-and-hitech-compliance/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://amsspher.com/pairing-hipaa-and-hitech-compliance/">Pairing HIPAA and HITECH Compliance</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></description>
				<content:encoded><![CDATA[<h3>Federal Privacy Officer Offers Insights</h3>
<p>The privacy and security provisions of the <a href="http://www.healthcareinfosecurity.com/agency-releases/hipaa-omnibus-final-rule-r-2760"><b>HIPAA Omnibus Rule</b></a> and the HITECH Act electronic health record incentive program &#8220;dovetail together quite nicely,&#8221; says Joy Pritts, chief privacy officer at the HHS Office of the National Coordinator for Health IT.</p>
<p>The &#8220;meaningful use&#8221; EHR incentive program &#8220;doesn&#8217;t make providers do anything differently than they&#8217;re already required to do under the HIPAA Security Rule,&#8221; Pritts notes. But the program&#8217;s rules highlight the importance of certain HIPAA compliance issues, especially the need for a <a href="http://www.healthcareinfosecurity.com/risk-assessment-c-44"><b>risk assessment</b></a>, she stresses.</p>
<p>Pritts also points out in an <a href="http://www.healthcareinfosecurity.com/interviews/joy-pritts-on-hipaa-hitech-compliance-i-1847"><b>interview</b></a> with <i>HealthcareInfoSecurity</i> (transcript below) that the <a href="http://www.healthcareinfosecurity.com/agency-releases/hitech-act-stage-2-ehr-incentive-program-software-certification-r-2724"><b>EHR software certification rule</b></a> for Stage 2 of the HITECH incentive program, which begins in 2014, requires that &#8220;if an end-use device maintains protected health information after that device has signed off, it must be encrypted. &#8230; That&#8217;s one of the things that&#8217;s really a move forward because that&#8217;s where we&#8217;re having a lot of breaches right now &#8230; devices that are lost and stolen.&#8221;</p>
<h3>Business Associates</h3>
<p>The HIPAA Omnibus Rule &#8220;really expands the type of organizations and people that are directly responsible for protecting privacy and security of health information,&#8221; Pritts notes.</p>
<p>&#8220;All of the contractors [business associates] of health plans and healthcare providers who are covered by HIPAA are now going to be directly responsible for following all the security rules and many of the use and disclosure rules under the [HIPAA] privacy rule,&#8221; she says. &#8220;What this means is if there&#8217;s a breach at the business associate level, then HHS will be able to enforce directly against the party that&#8217;s responsible for it. That&#8217;s a great improvement over how things are now.&#8221;</p>
<p>In the interview, Pritts also:</p>
<ul>
<li>Says that the rule for Stage 3 of the HITECH EHR incentive program likely will include guidelines for robust authentication of providers remotely accessing records;</li>
<li>Emphasizes that although the HIPAA Omnibus Rule requires providing patients with an electronic copy of their records, the patient can opt to receive their records without encryption or other security measures;</li>
<li>Discusses how the upcoming voluntary ONC guidelines for health information exchange will include tips on giving patients the opportunity to make a &#8220;meaningful choice&#8221; on whether to have their data exchanged.</li>
</ul>
<p>Pritts joined ONC, a unit of the Department of Health and Human Services, in 2010 as the office&#8217;s first chief privacy officer. In that role, Pritts provides advice to the HHS secretary and the National Coordinator for Health IT about developing and implementing ONC&#8217;s privacy and security programs under HITECH. Pritts also works closely with the Office for Civil Rights and other divisions of HHS, as well as with other government agencies, to help ensure a coordinated approach to key privacy and security issues. Before joining ONC, Pritts held a joint appointment as a senior scholar with the O&#8217;Neill Institute for National and Global Health Law and as a research associate professor at the Health Policy Institute, Georgetown University.</p>
<h3>HITECH and Omnibus</h3>
<p><b>HOWARD ANDERSON:</b> I want to talk about how the HIPAA Omnibus Rule helps reinforce some of the privacy and security requirements of the HITECH Act electronic health record meaningful use incentive program, or vice-versa. How do they help each other?</p>
<p><b>JOY PRITTS:</b> They really dovetail together quite nicely. One of the things that the [HIPAA Omnibus] rule does is it really expands the type of organizations and people that are directly responsible for protecting privacy and security of health information. All of the contractors [business associates] of health plans and healthcare providers who are covered by HIPAA are now going to be directly responsible for following all the security rules and many of the use and disclosure rules under the [HIPAA] privacy rule. What this means is if there&#8217;s a breach at the business associate level, then HHS will be able to enforce directly against the party that&#8217;s responsible for it. That&#8217;s a great improvement over how things are now.</p>
<p>When you look at the breaches that have been reported to HHS to date, more and more of them are coming at the business associate level, and that shouldn&#8217;t be surprising, given the way that things are evolving.</p>
<p>It segues very nicely with the [HITECH] meaningful use criteria. Meaningful use doesn&#8217;t make providers do anything differently than they&#8217;re already required to do under the HIPAA Security Rule. It is shining the light on some of the requirements in the security rule that providers may or may not have been aware of. For example, the security risk assessment is something that people should have been doing for many years, but time and again you see in these surveys where a good portion of providers still are not conducting a security risk assessment years after this was a requirement. We&#8217;ve reached a great opportunity that when people are starting to adopt clinical health information technology, they recognize, &#8220;I need to do this, and I probably should have been doing it with my billing data already.&#8221; But it&#8217;s a fine moment for getting people involved with this activity so that they know that they need to be doing it going forward.</p>
<h3>Key Security Steps</h3>
<p><b>ANDERSON:</b> What are some of the key steps organizations should be taking now to prepare to meet the privacy and security requirements of Stage 2 of the meaningful use program under HITECH? Are these the same steps that should be taken to comply with HIPAA Omnibus or different?</p>
<p><b>PRITTS:</b> There are some additional things that they should be aware of. For example, you have to use EHR technology that&#8217;s been certified for the meaningful use program. One of the key components of meaningful use and the certification criteria is that if an end-user device maintains protected health information after that device has signed off from an EHR, it must be encrypted. For example, if [someone] is using a laptop to access an electronic health record and it keeps that information, that device has to be encrypted. That&#8217;s one of the things that&#8217;s really a move forward, because that&#8217;s where we&#8217;re having a lot of breaches right now &#8211; with devices that are lost and stolen. This should really help because that&#8217;s going to make it much easier for the provider. They might not know about it, but in the background, if they&#8217;re buying certified EHR technology, they should feel comfortable that there should be some encryption already baked in which will make their life a little easier.</p>
<h3>HITECH Stage 3</h3>
<p><b>ANDERSON:</b> What do you think are some of the key privacy and security requirements that might be added for Stage 3? What&#8217;s left that needs to be added?</p>
<p><b>PRITTS:</b> We&#8217;ve heard from the policy committee that they&#8217;re very interested in exploring the level of authentication that providers need to have in order to be able to access an EHR system, particularly from a remote place. That&#8217;s an area that has been explored in the request for comments.</p>
<p><b>ANDERSON:</b> So more details about authentication could be more prominent in Stage 3?</p>
<p><b>PRITTS:</b> It&#8217;s one of the recommendations that we received as to if the technology would need to enable that and that providers would need to use it. Particularly, what they&#8217;re focusing on is moving toward two-factor authentication. That&#8217;s where the recommendations have been headed.</p>
<p><b>ANDERSON:</b> That&#8217;s primarily for clinicians, not necessarily for patients, right?</p>
<p><b>PRITTS:</b> Oh, yes. That&#8217;s primarily for clinicians because that&#8217;s how MU is set up. The meaningful use criteria focus on how the physicians are accessing the system. You raise an interesting issue about when providers in particular have to secure information when they send it to a patient. There&#8217;s a lot of information in the introductory section to the Omnibus Rule about how OCR views that issue. It&#8217;s a very interesting area because it&#8217;s a tradeoff between security and a patient&#8217;s right to access their own information. The bottom line is that if a patient is notified that sending information may not be secure, via e-mail for example, and the patient still wants to get it that way, then the provider is pretty much off the hook if they send it to the patient that way.</p>
<h3>Health Information Exchange</h3>
<p><b>ANDERSON:</b> ONC is developing voluntary guidelines for health information exchange. What do you see as the most important steps to ensure information remains secure and the data remains private when it&#8217;s exchanged?</p>
<p><b>PRITTS:</b> We look at the governance guidelines as a way for these organizations to start really building a network of trust. One of the ways of doing that is to make sure that everybody understands what their practices actually are &#8211; not what they&#8217;re legally allowed to do but what their practices actually are with respect to the information. Notice is one of the components of them.</p>
<p>Another piece of this is, depending on what kind of architectural model is being used, the policy committee has felt very strongly about patients having meaningful choice as to whether they participate in certain types of exchange, and that&#8217;s another key element &#8211; to make sure that there&#8217;s been buy-in by the patients in the system. That&#8217;s an essential element of trust, that the patients that you&#8217;re serving actually know what you&#8217;re doing and are comfortable with it.</p>
<p>&nbsp;</p>
<p>The post <a href="http://amsspher.com/pairing-hipaa-and-hitech-compliance/">Pairing HIPAA and HITECH Compliance</a> appeared first on <a href="http://amsspher.com">SPHER</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://amsspher.com/pairing-hipaa-and-hitech-compliance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
