<?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>Privacy Risk Report &#187; medical information</title>
	<atom:link href="https://privacyriskreport.com/tag/medical-information/feed/" rel="self" type="application/rss+xml" />
	<link>https://privacyriskreport.com</link>
	<description></description>
	<lastBuildDate>Fri, 03 Feb 2023 16:49:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Emerging Privacy Issues In Discovery Of Social Media</title>
		<link>https://privacyriskreport.com/emerging-privacy-issues-in-discovery-of-social-media/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=emerging-privacy-issues-in-discovery-of-social-media</link>
		<comments>https://privacyriskreport.com/emerging-privacy-issues-in-discovery-of-social-media/#comments</comments>
		<pubDate>Wed, 01 Mar 2017 22:33:25 +0000</pubDate>
		<dc:creator><![CDATA[Tressler LLP]]></dc:creator>
				<category><![CDATA[Protecting Against the Risk]]></category>
		<category><![CDATA[class action]]></category>
		<category><![CDATA[corporate]]></category>
		<category><![CDATA[cyber]]></category>
		<category><![CDATA[cyber insurance]]></category>
		<category><![CDATA[cyber security]]></category>
		<category><![CDATA[cyberliability]]></category>
		<category><![CDATA[discovery]]></category>
		<category><![CDATA[government]]></category>
		<category><![CDATA[insurance]]></category>
		<category><![CDATA[Internet of Things]]></category>
		<category><![CDATA[medical information]]></category>
		<category><![CDATA[social media]]></category>

		<guid isPermaLink="false">https://privacyriskreport.com/?p=1123</guid>
		<description><![CDATA[<div class="e-mailit_top_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/emerging-privacy-issues-in-discovery-of-social-media/' data-emailit-title='Emerging Privacy Issues In Discovery Of Social Media'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>By Danita L. Davis Sudac Individuals’ willingness to share detailed accounts of their lives on social media sites, such as Facebook, has created an unparalleled source of evidence for lawyers seeking discovery.   There is little question that social media evidence... <a class="more-link" href="https://privacyriskreport.com/emerging-privacy-issues-in-discovery-of-social-media/">Continue Reading &#8594;</a>
<div class="e-mailit_bottom_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/emerging-privacy-issues-in-discovery-of-social-media/' data-emailit-title='Emerging Privacy Issues In Discovery Of Social Media'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>The post <a rel="nofollow" href="https://privacyriskreport.com/emerging-privacy-issues-in-discovery-of-social-media/">Emerging Privacy Issues In Discovery Of Social Media</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></description>
				<content:encoded><![CDATA[<div class="e-mailit_top_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/emerging-privacy-issues-in-discovery-of-social-media/' data-emailit-title='Emerging Privacy Issues In Discovery Of Social Media'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p><em>By Danita L. Davis Sudac</em></p>
<p><span style="font-family: Calibri;"><span style="color: #000000;">Individuals’ willingness to share detailed accounts of their lives on social media sites, such as Facebook, has created an unparalleled source of evidence for lawyers seeking discovery.   There is little question that social media evidence can be helpful in the areas of civil litigation.  For example, it can be used to discredit a litigant or contradict allegations of damages. Recently, in the high profile matter of <i>Brown v. City of Ferguson</i></span><span style="color: #000000;">, 15-cv-831, (E.D. Mo., E Div. Jan. 27, 2017), U.S. District Judge E. Richard Webber ordered that the family of Michael J. Brown, Jr., the unarmed black teenager killed in 2014 by police in Ferguson, must disclose all relevant Facebook posts in their wrongful death action against the city.   The court disagreed with Brown’s family members’ claims that they had a right to privacy for notes sent through Facebook Messenger.  The court likened Messenger to a “personal diary” which the court found must be disclosed if it has entries relevant to a case.  The court reasoned that the social media posts would show the family members’ relationships with Brown, which will help calculate pain, suffering and psychological damages, as well as provide evidence that could be used by the City and other Defendants to impeach or show bias.  In addressing concerns as to overbreadth and relevance, the court noted that the disclosure was limited in time and the entry of a protective order would safeguard any remaining privacy concerns.  </span></span></p>
<p><span style="font-family: Calibri;"><span style="color: #000000;">In cases where the production of social media information is challenged, most courts note that discovery of such information is governed by the same legal principles that guide more traditional forms of discovery.   As one New York Superior Court opinion recognized, “fishing expeditions” of social media accounts are just as objectionable as their “analog  antecedents.”   <i>Winchell v. Lopiccolo,</i></span><span style="color: #000000;"> 954 N.Y.S.2d 421 (2012).  Relevance is still a perquisite before broad social media discovery is allowed.  Once relevance is established, however, the  traditional rules of civil procedure generally apply.</span></span></p>
<p><span style="color: #000000; font-family: Calibri;">Despite the fact that social media users may try to self-regulate their privacy settings to restrict public disclosure, in the litigation context, these posts may be deemed relevant and discoverable regardless of the users’ privacy intentions.  Further, when seeking social media discovery, attorneys should also think twice about “friending” a represented adverse policy. Such activity likely violates  the Rules of Professional Conduct which addresses communications with represented parties.  As it pertains to their own clients, attorneys must also be aware of issues related to the preservation of social media evidence.   Once involved in a lawsuit, a litigant cannot delete relevant social media evidence at issue in the litigation.</span></p>
<p><span style="color: #000000; font-family: Calibri;">In sum, as social media continues to be a popular and accessible mode of communication, discovery of social media information will become more prominent. Attorneys and their insurer clients should familiarize themselves with rules and recent decisions regarding the production of social media information as  issues surrounding such discovery will  likely be the subject of objection and motion practice. </span></p>
<p>&nbsp;</p>
<div class="e-mailit_bottom_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/emerging-privacy-issues-in-discovery-of-social-media/' data-emailit-title='Emerging Privacy Issues In Discovery Of Social Media'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>The post <a rel="nofollow" href="https://privacyriskreport.com/emerging-privacy-issues-in-discovery-of-social-media/">Emerging Privacy Issues In Discovery Of Social Media</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://privacyriskreport.com/emerging-privacy-issues-in-discovery-of-social-media/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Let’s Get Ready to Rumble: Gloves Come Off in Data Breach Standing Case</title>
		<link>https://privacyriskreport.com/lets-get-ready-to-rumble-gloves-come-off-in-data-breach-standing-case/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=lets-get-ready-to-rumble-gloves-come-off-in-data-breach-standing-case</link>
		<comments>https://privacyriskreport.com/lets-get-ready-to-rumble-gloves-come-off-in-data-breach-standing-case/#comments</comments>
		<pubDate>Tue, 10 Nov 2015 19:28:33 +0000</pubDate>
		<dc:creator><![CDATA[Todd Rowe]]></dc:creator>
				<category><![CDATA[Protecting Against the Risk]]></category>
		<category><![CDATA[class action]]></category>
		<category><![CDATA[damages]]></category>
		<category><![CDATA[data breach]]></category>
		<category><![CDATA[insurance]]></category>
		<category><![CDATA[lawsuit]]></category>
		<category><![CDATA[legislation]]></category>
		<category><![CDATA[litigation]]></category>
		<category><![CDATA[medical information]]></category>
		<category><![CDATA[personal information]]></category>
		<category><![CDATA[privacy]]></category>

		<guid isPermaLink="false">https://privacyriskreport.com/?p=453</guid>
		<description><![CDATA[<div class="e-mailit_top_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/lets-get-ready-to-rumble-gloves-come-off-in-data-breach-standing-case/' data-emailit-title='Let’s Get Ready to Rumble: Gloves Come Off in Data Breach Standing Case'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>While we have seen defendants in data breach cases argue that plaintiffs were not injured and therefore lack standing to bring suit, litigants in a recent data breach case have directly addressed issues some litigants have previously danced around. On August... <a class="more-link" href="https://privacyriskreport.com/lets-get-ready-to-rumble-gloves-come-off-in-data-breach-standing-case/">Continue Reading &#8594;</a>
<div class="e-mailit_bottom_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/lets-get-ready-to-rumble-gloves-come-off-in-data-breach-standing-case/' data-emailit-title='Let’s Get Ready to Rumble: Gloves Come Off in Data Breach Standing Case'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>The post <a rel="nofollow" href="https://privacyriskreport.com/lets-get-ready-to-rumble-gloves-come-off-in-data-breach-standing-case/">Let’s Get Ready to Rumble: Gloves Come Off in Data Breach Standing Case</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></description>
				<content:encoded><![CDATA[<div class="e-mailit_top_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/lets-get-ready-to-rumble-gloves-come-off-in-data-breach-standing-case/' data-emailit-title='Let’s Get Ready to Rumble: Gloves Come Off in Data Breach Standing Case'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>While we have seen defendants in data breach cases argue that plaintiffs were not injured and therefore lack standing to bring suit, litigants in a recent data breach case have directly addressed issues some litigants have previously danced around.</p>
<p>On August 6, 2015, Pamela Chambliss and Scott Adamson (Plaintiffs) filed a <a href="https://privacyriskreport.com/wp-content/uploads/2015/11/Chambliss-Complaint.pdf" target="_blank">class action complaint</a> in a Maryland District Court against Carefirst, Inc. (which operates under the tradename Carefirst Blue Cross Blue Shield) related to a data breach at Carefirst in 2014. The Plaintiffs claim they have health insurance through Carefirst and, therefore, were required to furnish private information to Carefirst. The class action complaint seeks damages based on allegations that Carefirst failed to adequately secure its computer hardware that stored the Plaintiffs’ personal information. Carefirst discovered this breach on May 20, 2015. The breach released the names, birthdates, email addresses and “subscriber information” of 1.1 million individuals. The class action complaint indicates Carefirst did not encrypt the stored data and was viewed as a “soft target” by hackers.</p>
<p>The first cause of action was based on allegations that Carefirst was negligent by failing to safely store personal information and “potentially confidential health information” of its members. The class action Plaintiffs further claimed this breach “proximately caused an unauthorized disclosure” of Plaintiffs’ information. The second cause of action was based on allegations that Plaintiffs’ relied on Carefirst’s representations concerning its privacy and security before they purchased health insurance. The third cause of action alleged Carefirst was unjustly enriched when it did not pay for the security and protection promised to the Plaintiffs. Finally, the Plaintiffs alleged Carefirst’s conduct constitutes a violation of the Maryland Personal Information Protection Act.</p>
<p>On September 24, 2015, Carefirst filed its motion to dismiss the class action complaint, asserting Plaintiffs&#8217; action is defective because “Plaintiffs have not alleged that they suffered an injury cognizable under Article III of the Constitution.” That is, Carefirst claims the Plaintiffs lacked standing to bring the action because the Plaintiffs’ data was not alleged to be misused in any manner.  In <a href="https://privacyriskreport.com/wp-content/uploads/2015/11/Chambliss-Memorandum.pdf" target="_blank">its supporting brief</a>, Carefirst points out the difficulty class action plaintiffs are having surviving motions to dismiss:</p>
<blockquote>
<p style="text-align: justify;"><em>Data theft is an unfortunate and increasingly common occurrence in contemporary life, victimizing literally millions of Americans. Fortunately, data loss does not always produce actual harm. Just as companies are learning how to harden their defenses against cyber theft, our Nation’s courts are learning to sort out the claims of truly injured victims from those who launch class actions without having suffered any real harm. This action falls into the latter category. </em></p>
</blockquote>
<p>On November 5, 2015, the Plaintiffs filed their <a href="https://privacyriskreport.com/wp-content/uploads/2015/11/Chambliss-Response.pdf" target="_blank">opposition to Carefirst’s motion to dismiss</a>. The Plaintiffs wasted no time addressing what appeared to be the current trend of plaintiffs having difficulties showing damage from a data breach. The opening paragraphs take aim at Carefirst’s argument as follows:</p>
<blockquote>
<p style="text-align: justify;"><em>Defendants, in their Motion, assert that data theft is a “common occurrence” as if that somehow excuses them from culpability for failing to take the reasonable, necessary steps to protect the plethora of sensitive, highly confidential personal and medical information in their possession and the harms that their insureds suffer as a result of that failure. Brief at 1.1 Defendants cannot get off so easily. In fact, the commonness of such breaches actually makes each subsequent breach all the more egregious. Just as the landlord in a high-crime area can be held liable when he fails to install a secure lock on a tenant’s door and a criminal breaks into a tenant’s apartment and harms her as a result, see e.g. <span style="text-decoration: underline;">Lay v. Dworman</span>, 732 P.2d 455 (Okla. 1987), so, too, can a health insurer, who knows of the risk of cyberattack, be liable when it fails to secure its insureds’ confidential personal information.</em></p>
</blockquote>
<p>Of course, the current dispute in the <em>Carefirst</em> case is based on what is becoming a substantial body of law concerning standing for data breach cases. In just the last year, we have seen the following developments on the standing issue:</p>
<ul>
<li><strong>7th U.S. Circuit Court of Appeals</strong>: On July 20, 2015, the 7th Circuit issued its decision in <a href="https://privacyriskreport.com/seventh-circuit-weighs-in-on-article-iii-standing-for-data-breach-plaintiffs/" target="_blank"><em>Remijas v. Neiman Marcus Group</em>, <em>LLC</em></a>, directly addressing Article III of the U.S. Constitution, the standing for data breach plaintiffs. In reversing the District Court, the 7th Circuit held that “[a]llegations of future harm can establish Article III standing if that harm is ‘certainly impending,’ but ‘allegations of possible future injury are not sufficient.’” In short, the 7th Circuit found the plaintiffs met the requirement under <em>Clapper </em>“that injury either already [has] occurred or [was] ‘certainly impending.’”</li>
<li><strong>District Court for Southern District of Texas</strong>: In <a href="https://privacyriskreport.com/another-court-dismisses-data-breach-class-action-on-12b1-standing-grounds/" target="_blank"><em>Peters v. St. Joseph Serv., Corp</em></a>., the District Court dismissed plaintiff’s claims on a 12(b)(1) Motion after finding that allegations of an increased risk of future harm were not sufficient to confer standing.</li>
<li><strong>District Court for Northern District of Georgia</strong>: Home Depot filed a <a href="https://privacyriskreport.com/home-depot-breach-litigation-goes-down-well-worn-path/" target="_blank">motion to dismiss</a> asserting the Class Action Plaintiffs lacked standing to bring suit for its data breach.</li>
<li><strong>District Court for Minnesota</strong>: In the <em>Target</em> litigation, the District Court <a href="http://www.cyberrisknetwork.com/2014/12/04/banks-breach-suit-target-will-proceed/" target="_blank">held the Financial Institutions’ action survived</a> Target’s Motion to Dismiss.</li>
</ul>
<p>All of these cases trace their origins back to the Supreme Court’s 2013 opinion in <a href="http://www.privacyriskreport.com/wp-content/uploads/2015/02/11-1025.pdf" target="_blank"><em>Clapper v. Amnesty Int’l</em></a> finding that the mere increased risk of future harm does not confer Article III standing.</p>
<p>The briefs in the <em>Carefirst</em> case demonstrate that litigants are starting to directly address the difficult questions related to data breach cases as courts gain a better understanding of these cases. While plaintiffs have hit a number of hurdles in establishing damages, defendants’ argument that everyone is suffering a data breach may lose credibility with courts.</p>
<div class="e-mailit_bottom_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/lets-get-ready-to-rumble-gloves-come-off-in-data-breach-standing-case/' data-emailit-title='Let’s Get Ready to Rumble: Gloves Come Off in Data Breach Standing Case'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>The post <a rel="nofollow" href="https://privacyriskreport.com/lets-get-ready-to-rumble-gloves-come-off-in-data-breach-standing-case/">Let’s Get Ready to Rumble: Gloves Come Off in Data Breach Standing Case</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://privacyriskreport.com/lets-get-ready-to-rumble-gloves-come-off-in-data-breach-standing-case/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Insurance Implications of Recent Federal Government Data Breaches</title>
		<link>https://privacyriskreport.com/insurance-implications-of-recent-federal-government-data-breaches/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=insurance-implications-of-recent-federal-government-data-breaches</link>
		<comments>https://privacyriskreport.com/insurance-implications-of-recent-federal-government-data-breaches/#comments</comments>
		<pubDate>Tue, 09 Jun 2015 15:51:00 +0000</pubDate>
		<dc:creator><![CDATA[Todd Rowe]]></dc:creator>
				<category><![CDATA[Protecting Against the Risk]]></category>
		<category><![CDATA[cybersecurity]]></category>
		<category><![CDATA[data breach]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[medical information]]></category>
		<category><![CDATA[Obama]]></category>

		<guid isPermaLink="false">https://privacyriskreport.com/?p=103</guid>
		<description><![CDATA[<div class="e-mailit_top_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/insurance-implications-of-recent-federal-government-data-breaches/' data-emailit-title='Insurance Implications of Recent Federal Government Data Breaches'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>Last week, the Obama Administration announced one of the largest breaches ever of federal employees’ data. This latest breach, involving records of nearly four million current and former government workers, originated in China. There are reports that this breach may have... <a class="more-link" href="https://privacyriskreport.com/insurance-implications-of-recent-federal-government-data-breaches/">Continue Reading &#8594;</a>
<div class="e-mailit_bottom_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/insurance-implications-of-recent-federal-government-data-breaches/' data-emailit-title='Insurance Implications of Recent Federal Government Data Breaches'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>The post <a rel="nofollow" href="https://privacyriskreport.com/insurance-implications-of-recent-federal-government-data-breaches/">Insurance Implications of Recent Federal Government Data Breaches</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></description>
				<content:encoded><![CDATA[<div class="e-mailit_top_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/insurance-implications-of-recent-federal-government-data-breaches/' data-emailit-title='Insurance Implications of Recent Federal Government Data Breaches'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>Last week, the Obama Administration announced <a href="http://www.nytimes.com/2015/06/05/us/breach-in-a-federal-computer-system-exposes-personnel-data.html?_r=0" target="_blank">one of the largest breaches ever of federal employees’ data</a>. This latest breach, involving records of nearly four million current and former government workers, originated in China. There are reports that <a href="http://thehill.com/policy/cybersecurity/244254-report-data-breach-not-limited-to-federal-employees" target="_blank">this breach may have included information from background checks</a> and, therefore, may impact families of federal workers as well. This follows a <a href="https://privacyriskreport.com/death-taxes-and-cybersecurity-new-incident-at-irs-illustrates-evolution-of-cyber-crime/" target="_blank">breach in late May of IRS records</a> where criminals accessed information related to at least 100,000 taxpayers. While the American taxpayers may be on the hook rather than insurers, these breaches provide insight on how the targets for cyber criminals may be shifting from financial information, such as credit card data, to personal/health information. There is also information indicating medical devices in hospitals pose a significant risk.<strong><br />
</strong></p>
<p><strong>Medical Records/Personnel Data </strong></p>
<p>The recent breaches in the federal government contribute to a growing trend of hackers targeting data beyond credit card information. Experts believe the shift away from credit card information may be due to the black market becoming oversaturated with credit card information from breaches at big retailers. Hackers seem to be using smaller, more surgical attacks. At present, estimates indicate that medical information may be worth 10 times more than credit card information.<strong><br />
</strong></p>
<p><strong>Medical Devices</strong></p>
<p>A recent <a href="http://deceive.trapx.com/AOAMEDJACK_210_Landing_Page.html">Report</a> indicates that medical devices used in hospitals and clinics may present the weakest point in healthcare’s defense systems. Commentators point out that <a href="http://www.computerworld.com/article/2932371/cybercrime-hacking/medjack-hackers-hijacking-medical-devices-to-create-backdoors-in-hospital-networks.html" target="_blank">these newest targets may not be limited to only medical information</a>, but may include diagnostic equipment (PET scanners, CT scanners, MRI machines, etc.), therapeutic equipment (infusion pumps, medical lasers and LASIK surgical machines) and life support equipment (heart-lung machines, medical ventilators, extracorporeal membrane oxygenation machines and dialysis machines).</p>
<p>The Report provides details on the following three “real-world targeted hospital attacks:”</p>
<ul>
<li><em>Hospital Lab Blood Gas Analyzer Attack</em>: Blood gas analyzers are devices used during surgery. The Report found attackers “were moving laterally through the networks due to three malware-infected blood gas analyzers that had ‘enabled backdoors into the hospital networks’” and were able to obtain unencrypted data and send that data to sources in Europe.</li>
<li><em>Hospital Radiology</em>: In the second example, the Report discusses an intrusion through equipment in a hospital’s radiology department. The source of the intrusion was a nurse’s workstation which had been used on the internet.</li>
<li><em>X-ray Systems</em>: The Report also found an example of malware on a hospital’s system that was installed through a backdoor on the hospital’s x-ray equipment.</li>
</ul>
<p>Based on these scenarios, commentators caution that hackers could do more damage than merely stealing valuable medical data. For example, vulnerable medical devices could give access to drug infusion pumps which would allow drug dosage to be remotely controlled by a person that may not have the best intentions. As for the insurance industry, these scenarios show that a criminal’s access to an insured’s data may not be limited to only a computer network. Electronic devices used by an insured may provide another path to the insured’s assets.</p>
<p>These recent breaches in the federal government, while perhaps having no immediate impact on insurers, show the early stages of how the threat against insureds has evolved past large-scale credit card data theft. Large-scale credit card theft from big box stores such as Home Depot or Target may become less frequent. As seen with the breach on Sony pictures in December 2014, insurers and insureds have to consider a number of potentially valuable assets while considering insurance coverage for data storage risks. Further, the insurance industry may need to consider the impact of smaller attacks rather than only bracing for the “big one.” Consequently, these breaches at the federal government just made assessing the risk more difficult for the insurance industry.</p>
<div class="e-mailit_bottom_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/insurance-implications-of-recent-federal-government-data-breaches/' data-emailit-title='Insurance Implications of Recent Federal Government Data Breaches'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>The post <a rel="nofollow" href="https://privacyriskreport.com/insurance-implications-of-recent-federal-government-data-breaches/">Insurance Implications of Recent Federal Government Data Breaches</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://privacyriskreport.com/insurance-implications-of-recent-federal-government-data-breaches/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Modification of Data Breach Laws Directly Impacts Insurers and Insureds</title>
		<link>https://privacyriskreport.com/modification-of-data-breach-laws-directly-impacts-insurers-and-insureds/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=modification-of-data-breach-laws-directly-impacts-insurers-and-insureds</link>
		<comments>https://privacyriskreport.com/modification-of-data-breach-laws-directly-impacts-insurers-and-insureds/#comments</comments>
		<pubDate>Thu, 05 Mar 2015 20:06:39 +0000</pubDate>
		<dc:creator><![CDATA[Todd Rowe]]></dc:creator>
				<category><![CDATA[Protecting Against the Risk]]></category>
		<category><![CDATA[data breach]]></category>
		<category><![CDATA[Illinois]]></category>
		<category><![CDATA[medical information]]></category>
		<category><![CDATA[personal information]]></category>

		<guid isPermaLink="false">https://privacyriskreport.com/?p=51</guid>
		<description><![CDATA[<div class="e-mailit_top_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/modification-of-data-breach-laws-directly-impacts-insurers-and-insureds/' data-emailit-title='Modification of Data Breach Laws Directly Impacts Insurers and Insureds'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>We have previously reported on other states, including California and New Jersey, strengthening their data breach notification laws. Illinois Attorney General, Lisa Madigan, is now proposing similar steps be taken in Illinois. In support of her attempt to modify the 2005 law, Madigan stated: “In... <a class="more-link" href="https://privacyriskreport.com/modification-of-data-breach-laws-directly-impacts-insurers-and-insureds/">Continue Reading &#8594;</a>
<div class="e-mailit_bottom_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/modification-of-data-breach-laws-directly-impacts-insurers-and-insureds/' data-emailit-title='Modification of Data Breach Laws Directly Impacts Insurers and Insureds'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>The post <a rel="nofollow" href="https://privacyriskreport.com/modification-of-data-breach-laws-directly-impacts-insurers-and-insureds/">Modification of Data Breach Laws Directly Impacts Insurers and Insureds</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></description>
				<content:encoded><![CDATA[<div class="e-mailit_top_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/modification-of-data-breach-laws-directly-impacts-insurers-and-insureds/' data-emailit-title='Modification of Data Breach Laws Directly Impacts Insurers and Insureds'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>We have previously reported on other states, including <a href="https://privacyriskreport.com/california-attorney-general-provides-sage-advice-regarding-data-breach-protection/">California</a> and <a href="https://privacyriskreport.com/new-jersey-considers-amendments-to-its-data-breach-laws/">New Jersey</a>, strengthening their data breach notification laws. Illinois Attorney General, Lisa Madigan, is now <a href="http://www.chicagotribune.com/business/breaking/ct-consumer-complaints-0303-biz-20150302-story.html">proposing</a> similar steps be taken in Illinois. In support of her attempt to modify the 2005 law, Madigan stated: “In light of last year’s massive data breaches, it is clearer than ever that much more must be done to protect sensitive data while ensuring that people know when their information has been compromised….”</p>
<p>In particular, the Attorney General is proposing the following modifications to Illinois’ Personal Information Protection Act (<a href="http://www.ilga.gov/legislation/ilcs/ilcs3.asp?ActID=2702&amp;ChapterID=67">PIPA</a>):</p>
<ul>
<li>Expanding the definition of “personal information” to include medical information, biometric data, geolocation information, certain consumer marketing data, contact information when combined with other identifying information;</li>
<li>Requirements that businesses take reasonable steps to protect personal information coverage under PIPA; and</li>
<li>Requirement that the Attorney General’s office be notified of any breach involving information of Illinois residents.</li>
</ul>
<p>Of course, while these heightened standards may be good for Illinois residents, anyone holding personal information of Illinois residents will be responsible for meeting the current and, at some point, the proposed requirements. The expanded definition of “personal information” will increase the number of entities subject to the current version of PIPA<em>.</em>Therefore, the best strategy is to continue to review your breach response plan to confirm it reflects the current laws.</p>
<p>Additionally, these proposals in Illinois and other states will have a direct impact on insurance coverage for data breaches. First, these proposals require insureds to inform not only their insurance carrier of a breach, but also the Attorney General’s office in addition to those individuals involved in the breach. Second, the risk to insureds increases as the scope of data breach notification laws widens. Therefore, we can expect the need for cyber insurance to continue to increase as more states strengthen their laws.</p>
<div class="e-mailit_bottom_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/modification-of-data-breach-laws-directly-impacts-insurers-and-insureds/' data-emailit-title='Modification of Data Breach Laws Directly Impacts Insurers and Insureds'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>The post <a rel="nofollow" href="https://privacyriskreport.com/modification-of-data-breach-laws-directly-impacts-insurers-and-insureds/">Modification of Data Breach Laws Directly Impacts Insurers and Insureds</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://privacyriskreport.com/modification-of-data-breach-laws-directly-impacts-insurers-and-insureds/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Another Court Dismisses Data Breach Class Action on 12(b)(1) Standing Grounds</title>
		<link>https://privacyriskreport.com/another-court-dismisses-data-breach-class-action-on-12b1-standing-grounds/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=another-court-dismisses-data-breach-class-action-on-12b1-standing-grounds</link>
		<comments>https://privacyriskreport.com/another-court-dismisses-data-breach-class-action-on-12b1-standing-grounds/#comments</comments>
		<pubDate>Fri, 20 Feb 2015 20:08:42 +0000</pubDate>
		<dc:creator><![CDATA[Todd Rowe]]></dc:creator>
				<category><![CDATA[Protecting Against the Risk]]></category>
		<category><![CDATA[California]]></category>
		<category><![CDATA[class action]]></category>
		<category><![CDATA[data breach]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[identity theft]]></category>
		<category><![CDATA[medical information]]></category>
		<category><![CDATA[personal information]]></category>
		<category><![CDATA[Texas]]></category>

		<guid isPermaLink="false">https://privacyriskreport.com/?p=53</guid>
		<description><![CDATA[<div class="e-mailit_top_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/another-court-dismisses-data-breach-class-action-on-12b1-standing-grounds/' data-emailit-title='Another Court Dismisses Data Breach Class Action on 12(b)(1) Standing Grounds'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>In a case of first impression within the Fifth Circuit, a district court has dismissed a putative class action complaint brought after a data breach against one of the larger health organizations operating in California and Texas. In Peters v. St.... <a class="more-link" href="https://privacyriskreport.com/another-court-dismisses-data-breach-class-action-on-12b1-standing-grounds/">Continue Reading &#8594;</a>
<div class="e-mailit_bottom_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/another-court-dismisses-data-breach-class-action-on-12b1-standing-grounds/' data-emailit-title='Another Court Dismisses Data Breach Class Action on 12(b)(1) Standing Grounds'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>The post <a rel="nofollow" href="https://privacyriskreport.com/another-court-dismisses-data-breach-class-action-on-12b1-standing-grounds/">Another Court Dismisses Data Breach Class Action on 12(b)(1) Standing Grounds</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></description>
				<content:encoded><![CDATA[<div class="e-mailit_top_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/another-court-dismisses-data-breach-class-action-on-12b1-standing-grounds/' data-emailit-title='Another Court Dismisses Data Breach Class Action on 12(b)(1) Standing Grounds'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>In a case of first impression within the Fifth Circuit, a district court has dismissed a putative class action complaint brought after a data breach against one of the larger health organizations operating in California and Texas. In <a href="http://www.privacyriskreport.com/wp-content/uploads/2015/02/peters-v-st-joseph.pdf"><em>Peters v. St. Joseph Services Corp.</em></a>, the District Court for the Southern District of Texas dismissed plaintiff’s claims upon a 12(b)(1) Motion after finding that allegations of an increased risk of future harm were not sufficient to confer standing.</p>
<p>Plaintiff Beverly Peters alleged that hackers had accessed and stolen her information after breaching St. Joseph Health Systems’ data network. Peters alleged that someone had attempted – albeit unsuccessfully – to make purchases on her Discover card and had attempted to access her Amazon account using a family member’s name. Peters claimed these incidents as evidence that she was at an increased risk of imminent harm stemming from the breach. In dismissing the complaint for lack of standing, the court joined the Third Circuit, as well as district courts in Ohio, New Jersey, and the District of Columbia, in finding that Peters’ allegations of an increased risk of future identify theft and fraud were insufficient to survive a motion to dismiss. “’Unless and until these conjectures become true’…Peters’ alleged future injuries are speculative – even hypothetical – but certainly not imminent.” The decision relied upon the Supreme Court’s 2013 opinion in <a href="http://www.privacyriskreport.com/wp-content/uploads/2015/02/11-1025.pdf"><em>Clapper</em> <em>v. Amnesty International</em></a> in finding that the mere increased risk of future harm does not confer Article III standing. In doing so, the Southern District of Texas argued that the <em>Clapper</em> decision had “arguably resolved the circuit split” as to whether allegations of risk of future harm were sufficient to confer standing in data breach cases.</p>
<p>Despite the <a href="http://www.privacyriskreport.com/wp-content/uploads/2015/02/peters-v-st-joseph.pdf">court’s opinion</a> that <em>Clapper</em><em> </em>has resolved the circuit split over standing in data breach lawsuits, there remains significant division among circuit courts (and even, post-<em>Clapper</em>, among district courts within the same circuit) as to whether an alleged increased risk of future harm stemming from a data breach constitutes imminent injury under Article III. While the Seventh and Ninth Circuits held that such allegations were sufficient to confer standing, both decisions were issued prior to <em>Clapper</em><em> </em>and district courts within those circuits have decided the issue both ways since the Supreme Court’s opinion. What does appear clear is that plaintiffs in data breach cases face a significant hurdle in a motion to dismiss for lack of standing in the wake of <em>Clapper</em>, and that absent allegations of actual harm already suffered (rather than an increased risk of harm), defendants stand a good chance of dismissing class actions at an early stage.</p>
<div class="e-mailit_bottom_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/another-court-dismisses-data-breach-class-action-on-12b1-standing-grounds/' data-emailit-title='Another Court Dismisses Data Breach Class Action on 12(b)(1) Standing Grounds'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>The post <a rel="nofollow" href="https://privacyriskreport.com/another-court-dismisses-data-breach-class-action-on-12b1-standing-grounds/">Another Court Dismisses Data Breach Class Action on 12(b)(1) Standing Grounds</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://privacyriskreport.com/another-court-dismisses-data-breach-class-action-on-12b1-standing-grounds/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Apple Watch Poses a Number of New Privacy Risks</title>
		<link>https://privacyriskreport.com/apple-watch-poses-a-number-of-new-privacy-risks/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=apple-watch-poses-a-number-of-new-privacy-risks</link>
		<comments>https://privacyriskreport.com/apple-watch-poses-a-number-of-new-privacy-risks/#comments</comments>
		<pubDate>Fri, 12 Sep 2014 16:40:31 +0000</pubDate>
		<dc:creator><![CDATA[Todd Rowe]]></dc:creator>
				<category><![CDATA[Protecting Against the Risk]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[insurance]]></category>
		<category><![CDATA[medical information]]></category>

		<guid isPermaLink="false">https://privacyriskreport.com/?p=202</guid>
		<description><![CDATA[<div class="e-mailit_top_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/apple-watch-poses-a-number-of-new-privacy-risks/' data-emailit-title='Apple Watch Poses a Number of New Privacy Risks'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>Apple unveiled its first “smartwatch” on September 9, 2014 and it will be available to the public in early 2015. It is widely reported that, in order for the Apple Watch to be a success, Apple will need to partner with health... <a class="more-link" href="https://privacyriskreport.com/apple-watch-poses-a-number-of-new-privacy-risks/">Continue Reading &#8594;</a>
<div class="e-mailit_bottom_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/apple-watch-poses-a-number-of-new-privacy-risks/' data-emailit-title='Apple Watch Poses a Number of New Privacy Risks'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>The post <a rel="nofollow" href="https://privacyriskreport.com/apple-watch-poses-a-number-of-new-privacy-risks/">Apple Watch Poses a Number of New Privacy Risks</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></description>
				<content:encoded><![CDATA[<div class="e-mailit_top_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/apple-watch-poses-a-number-of-new-privacy-risks/' data-emailit-title='Apple Watch Poses a Number of New Privacy Risks'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>Apple unveiled its first “smartwatch” on September 9, 2014 and it will be available to the public in early 2015. It is <a href="http://www.nytimes.com/2014/09/08/technology/can-apple-build-a-cool-and-convenient-iwatch.html?_r=0" target="_blank">widely reported</a> that, in order for the Apple Watch to be a success, Apple will need to partner with health insurance carriers to use the device to monitor and collect private health data. Fitness tracking devices are already being used to gauge health insurance premiums. For example, British Petroleum has used a fitness bracelet to <a href="http://www.dailyherald.com/article/20140901/business/140909985/http:/" target="_blank">track the health data of its employees</a> and their spouses in order to lower its health insurance premiums.</p>
<p>Whether people will use health monitoring devices such as the Apple Watch to the extent they have used iTunes or other apps remains to be seen. Beyond the ethical questions, there are a number of questions of whether this data has value and will be targeted by hackers. One thing is certain, the risks for a data breach increases with each new method for data collection and storage.</p>
<div class="e-mailit_bottom_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/apple-watch-poses-a-number-of-new-privacy-risks/' data-emailit-title='Apple Watch Poses a Number of New Privacy Risks'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>The post <a rel="nofollow" href="https://privacyriskreport.com/apple-watch-poses-a-number-of-new-privacy-risks/">Apple Watch Poses a Number of New Privacy Risks</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://privacyriskreport.com/apple-watch-poses-a-number-of-new-privacy-risks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Class Action Alleges Breach of Data for 4.5 Million Patients</title>
		<link>https://privacyriskreport.com/class-action-alleges-breach-of-data-for-4-5-million-patients/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=class-action-alleges-breach-of-data-for-4-5-million-patients</link>
		<comments>https://privacyriskreport.com/class-action-alleges-breach-of-data-for-4-5-million-patients/#comments</comments>
		<pubDate>Thu, 11 Sep 2014 16:41:52 +0000</pubDate>
		<dc:creator><![CDATA[Todd Rowe]]></dc:creator>
				<category><![CDATA[Protecting Against the Risk]]></category>
		<category><![CDATA[Alabama]]></category>
		<category><![CDATA[class action]]></category>
		<category><![CDATA[damages]]></category>
		<category><![CDATA[data breach]]></category>
		<category><![CDATA[FCRA]]></category>
		<category><![CDATA[medical information]]></category>

		<guid isPermaLink="false">https://privacyriskreport.com/?p=204</guid>
		<description><![CDATA[<div class="e-mailit_top_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/class-action-alleges-breach-of-data-for-4-5-million-patients/' data-emailit-title='Class Action Alleges Breach of Data for 4.5 Million Patients'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>Patients of Community Health Systems filed a Complaint initiating a class action in the Northern District of Alabama against the hospital system on August 20, 2014. The class action arises out of the breach of an estimated 4.5 million patients’ protected data.... <a class="more-link" href="https://privacyriskreport.com/class-action-alleges-breach-of-data-for-4-5-million-patients/">Continue Reading &#8594;</a>
<div class="e-mailit_bottom_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/class-action-alleges-breach-of-data-for-4-5-million-patients/' data-emailit-title='Class Action Alleges Breach of Data for 4.5 Million Patients'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>The post <a rel="nofollow" href="https://privacyriskreport.com/class-action-alleges-breach-of-data-for-4-5-million-patients/">Class Action Alleges Breach of Data for 4.5 Million Patients</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></description>
				<content:encoded><![CDATA[<div class="e-mailit_top_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/class-action-alleges-breach-of-data-for-4-5-million-patients/' data-emailit-title='Class Action Alleges Breach of Data for 4.5 Million Patients'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>Patients of Community Health Systems filed a <a href="http://pdfserver.amlaw.com/nlj/CAPL%20HOSPITAL%200825.pdf" target="_blank">Complaint</a> initiating a class action in the Northern District of Alabama against the hospital system on August 20, 2014. The class action arises out of the breach of an estimated 4.5 million patients’ protected data. Plaintiffs allege claims typical to those in other data breach cases, including breach of contract, negligence, and unjust enrichment. However, Plaintiffs additionally assert claims for willful and negligent violations of the Fair Credit Reporting Act, alleging that Community Health Systems is a consumer reporting agency covered by the FCRA. Courts have yet to address the viability of claims against healthcare institutions under the FCRA, as only a handful of data breach complaints have actually stated claims for damages under the Act.</p>
<p>If the Court allows Plaintiffs’ claims under the FCRA to stand in this action, healthcare providers will face significantly greater statutory damages in the event of a data breach.</p>
<div class="e-mailit_bottom_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/class-action-alleges-breach-of-data-for-4-5-million-patients/' data-emailit-title='Class Action Alleges Breach of Data for 4.5 Million Patients'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>The post <a rel="nofollow" href="https://privacyriskreport.com/class-action-alleges-breach-of-data-for-4-5-million-patients/">Class Action Alleges Breach of Data for 4.5 Million Patients</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://privacyriskreport.com/class-action-alleges-breach-of-data-for-4-5-million-patients/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>District Court Analyzes Requirements to Establish Standing For Data Breach Cases</title>
		<link>https://privacyriskreport.com/district-court-analyzes-requirements-to-establish-standing-for-data-breach-cases/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=district-court-analyzes-requirements-to-establish-standing-for-data-breach-cases</link>
		<comments>https://privacyriskreport.com/district-court-analyzes-requirements-to-establish-standing-for-data-breach-cases/#comments</comments>
		<pubDate>Tue, 12 Aug 2014 17:36:30 +0000</pubDate>
		<dc:creator><![CDATA[Todd Rowe]]></dc:creator>
				<category><![CDATA[Protecting Against the Risk]]></category>
		<category><![CDATA[data breach]]></category>
		<category><![CDATA[government]]></category>
		<category><![CDATA[identity theft]]></category>
		<category><![CDATA[litigation]]></category>
		<category><![CDATA[medical information]]></category>
		<category><![CDATA[personal information]]></category>

		<guid isPermaLink="false">https://privacyriskreport.com/?p=220</guid>
		<description><![CDATA[<div class="e-mailit_top_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/district-court-analyzes-requirements-to-establish-standing-for-data-breach-cases/' data-emailit-title='District Court Analyzes Requirements to Establish Standing For Data Breach Cases'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>In finding plaintiffs lacked standing to bring an action for a data breach, the U.S. District Court for the District of Columbia held the “increased likelihood” of personal information being used was insufficient to establish a viable cause of action. In... <a class="more-link" href="https://privacyriskreport.com/district-court-analyzes-requirements-to-establish-standing-for-data-breach-cases/">Continue Reading &#8594;</a>
<div class="e-mailit_bottom_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/district-court-analyzes-requirements-to-establish-standing-for-data-breach-cases/' data-emailit-title='District Court Analyzes Requirements to Establish Standing For Data Breach Cases'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>The post <a rel="nofollow" href="https://privacyriskreport.com/district-court-analyzes-requirements-to-establish-standing-for-data-breach-cases/">District Court Analyzes Requirements to Establish Standing For Data Breach Cases</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></description>
				<content:encoded><![CDATA[<div class="e-mailit_top_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/district-court-analyzes-requirements-to-establish-standing-for-data-breach-cases/' data-emailit-title='District Court Analyzes Requirements to Establish Standing For Data Breach Cases'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>In finding plaintiffs lacked standing to bring an action for a data breach, the U.S. District Court for the District of Columbia held the “increased likelihood” of personal information being used was insufficient to establish a viable cause of action. <em>In re Sci. Applications Int’l Corp. (SAIC) Backup Tape Data Theft Litig</em>., 2014 U.S. Dist. LEXIS 64125 (D.D.C. May 9, 2014), the plaintiffs’ medical information was stolen from a car owned by an employee of the Science Applications International Corporation, a company that handles data for the U.S. Government.</p>
<p>The<em> </em><em>SAIC</em> Court held the majority of the plaintiffs lacked standing because they could not show they had suffered any injuries. The fact that the plaintiffs may be more likely to be subjected to identity theft or that the plaintiffs may need to incur costs related to monitoring their credit did not establish that the plaintiffs had suffered a compensable injury.</p>
<p>The <em>SAIC</em><em> </em>Court also found the minority of plaintiffs that could show they suffered some form of an injury from identity theft could not establish such injuries were directly caused by the theft of the tapes. Here, the <em>SAIC</em><em> </em>Court held that even if the plaintiffs suffered injury, the alleged injury was caused by the theft of financial information and the plaintiffs alleged only that thief obtained unrelated medical data from the car.</p>
<p>The <em>SAIC</em> Court noted there was evidence submitted that approximately 3.3% of the population will experience some form of identity theft. Therefore, it was not unexpected to see some of the plaintiffs had suffered identity theft. The plaintiffs were not able to show this identity theft was caused by their medical information being stolen from the car.</p>
<p>Consequently, at a bare minimum, to establish standing in a data breach case, a party must demonstrate actual injury that was directly caused by the data breach.</p>
<div class="e-mailit_bottom_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/district-court-analyzes-requirements-to-establish-standing-for-data-breach-cases/' data-emailit-title='District Court Analyzes Requirements to Establish Standing For Data Breach Cases'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>The post <a rel="nofollow" href="https://privacyriskreport.com/district-court-analyzes-requirements-to-establish-standing-for-data-breach-cases/">District Court Analyzes Requirements to Establish Standing For Data Breach Cases</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://privacyriskreport.com/district-court-analyzes-requirements-to-establish-standing-for-data-breach-cases/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
