{"id":167,"date":"2016-09-15T20:59:20","date_gmt":"2016-09-15T20:59:20","guid":{"rendered":"http:\/\/blogs.luc.edu\/compliance\/?p=167"},"modified":"2016-09-15T20:59:20","modified_gmt":"2016-09-15T20:59:20","slug":"ftc-final-order-against-labmd-the-intersection-of-unfair-practices-privacy-security-and-compliance","status":"publish","type":"post","link":"https:\/\/blogs.luc.edu\/compliance\/?p=167","title":{"rendered":"FTC Final Order against LabMD \u2013 The Intersection of Unfair Practices, Privacy, Security, and Compliance"},"content":{"rendered":"<p><em>Logan Parker<\/em><br \/>\n<em>Privacy Editor<\/em><br \/>\n<em>Loyola University Chicago School of Law, LL.M. in Health Law 2017<\/em><\/p>\n<p>&nbsp;<\/p>\n<p>The Federal Trade Commission (\u201cFTC\u201d) issued an <a href=\"https:\/\/www.ftc.gov\/system\/files\/documents\/cases\/160729labmd-opinion.pdf\">Opinion and Final Order<\/a> on July 29, 2016 against LabMD, <a href=\"http:\/\/www.modernhealthcare.com\/article\/20160729\/NEWS\/160729865\">a now defunct medical testing laboratory<\/a>, for its lax data security practices that constituted an unfair practice under Section 5 of the FTC Act. The FTC directed LabMD to take remediation efforts to ensure LabMD will protect sensitive consumer information going forward.<\/p>\n<p>The ruling effectively reversed an Administrative Law Judge\u2019s (\u201cALJ\u201d) decision that dismissed FTC\u2019s charges against LabMD. In the unanimous opinion, <a href=\"https:\/\/www.ftc.gov\/news-events\/press-releases\/2016\/07\/commission-finds-labmd-liable-unfair-data-security-practices\">the FTC stated<\/a> that the ALJ applied the wrong legal standard for unfairness and finds that \u201cLabMD\u2019s security practices were unreasonable, and lacking even basic precautions to protect the sensitive consumer information maintained on its computer system.\u201d<\/p>\n<p><strong>Unfair Practices under Section 5 of the FTC Act<\/strong><\/p>\n<p><a href=\"https:\/\/www.law.cornell.edu\/uscode\/text\/15\/45\">An act<\/a> may be deemed to be unfair if it causes or is \u201clikely\u201d to cause substantial injury to consumers that is neither reasonably avoidable by consumers nor outweighed by countervailing benefits to consumers or competition. The FTC\u2019s finding in determining whether LabMD\u2019s actions created an unfair practice under the Act focused on the word \u201clikely.\u201d The FTC read \u201clikely\u201d to mean \u201creasonably to be believed or expected.\u201d The FTC relied on case precedent set in <a href=\"https:\/\/www.ftc.gov\/sites\/default\/files\/documents\/commission_decision_volumes\/volume-104\/ftc_volume_decision_104__july_-_december_1984pages949_-_1088.pdf\"><em>International Harvester<\/em><\/a> and <a href=\"https:\/\/www.ftc.gov\/news-events\/press-releases\/2015\/12\/wyndham-settles-ftc-charges-it-unfairly-placed-consumers-payment\"><em>Wyndham<\/em><\/a> to conclude that the FTC does not have to prove that actual harm occurred to bring an Unfair Practices violation, but harm is proved if <a href=\"https:\/\/www.ftc.gov\/system\/files\/documents\/cases\/160729labmd-opinion.pdf\">\u201cthe magnitude of the potential injury is large, even if the likelihood of the injury occurring is low.\u201d<\/a><\/p>\n<p><strong>LabMD\u2019s Privacy &amp; Security Issues as they relate to an Unfair Practice<\/strong><\/p>\n<p>In reaching its conclusion, the <a href=\"https:\/\/www.ftc.gov\/news-events\/press-releases\/2016\/07\/commission-finds-labmd-liable-unfair-data-security-practices\">FTC found<\/a> that LabMD\u2019s lack of security controls led to failures to utilize intrusion detection systems or other forms of file monitoring, including traffic across its firewalls, providing no data security training to its employees, and never deleting any of the consumer data it had collected. The failures also resulted in the installation of file-sharing software that exposed the medical and other sensitive personal information\u201d of close to 10,000 consumers on a peer-to-peer network, accessible to its users for eleven (11) month. This led to the unauthorized disclosure of the information.<\/p>\n<p>Moreover, the FTC pointed out that this was <a href=\"https:\/\/www.ftc.gov\/system\/files\/documents\/cases\/160729labmd-opinion.pdf\">health data<\/a>. The disclosure of health data can result in greater likelihood of \u201cembarrassment or other negative outcomes including reputational harm\u201d that would be a violation of the Unfair Practices Act under the FTC Act. Improper disclosure could also lead to medical identity theft, which is almost impossible to correct and may result in misdiagnosis and mistreatment leading to direct physical harm. Finally, the Opinion and Final Order noted the importance of timely reporting under the breach notification rules of the Health Insurance Portability and Accountability Act, and how the fact that LabMD never notified consumers of the unauthorized disclosure of their health information limited the harm mitigation efforts the consumer could have pursued if notified properly and on time.<\/p>\n<p>Due to these inadequacies in LabMD\u2019s security program, FTC ordered the entity to:<\/p>\n<ul>\n<li>Establish a comprehensive information security program;<\/li>\n<li>Obtain periodic independent, third party assessments regarding the implementation of the information security program; and<\/li>\n<li>Notify those consumers whose personal information was misappropriated.<\/li>\n<\/ul>\n<p><strong>FTC\u2019s Authority <\/strong><\/p>\n<p>An interesting question of <a href=\"http:\/\/privacylaw.proskauer.com\/2016\/08\/articles\/online-privacy\/ftc-labmd-tests-positive-for-unfair-security-practices\/\">agency authority<\/a> arises in this case due to the mere fact that the consumer information at issue here is health data. Health information breaches typically fall within the jurisdiction of the Health and Human Services\u2019 (\u201cHHS\u201d) Office for Civil Rights. FTC expanding such jurisdiction over these types of cases could lead to further confusion in the future with notification standards, if FTC differs in its approach with HHS. However, intersections in different agencies\u2019 authority are not uncommon.<\/p>\n<p><strong>Appeal &amp; Stay<\/strong><\/p>\n<p>LabMD has 60 days from service of the Opinion and Final Order to appeal. <a href=\"http:\/\/www.nationallawjournal.com\/id=1202765441234\/LabMD-Bolsters-Defense-to-Appeal-FTC-DataPrivacy-Ruling?slreturn=20160809150615\">An appeal seems very likely<\/a> with <a href=\"http:\/\/www.modernhealthcare.com\/article\/20160729\/NEWS\/160729865\">LabMD CEO Michael Daugherty<\/a> saying that he\u2019s relieved to argue his case in federal court, away from the FTC\u2019s \u201cdirty system.\u201d Further evidence of an impending appeal came at the end of August 2016, when LabMD <a href=\"https:\/\/www.dataprivacyandsecurityinsider.com\/2016\/09\/labmd-seeks-stay-of-ftcs-final-order-pending-appeal\/\">filed<\/a> its Application for a Stay of the Final Order of the FTC.<\/p>\n<p><strong>Lessons Learned<\/strong><\/p>\n<p>Although this case is still evolving and the outcome is not yet determined, important yet basic elements of a compliance program could have helped prevent litigation at the out-set, such as having proper standards and procedures, adequate training, consistent and effective monitoring, and rapid response and prevention tactics. Healthcare providers should assess and update their privacy and data security policies and programs regularly to make improvements, as well as prepare for incidents such as those in this case. Finally, it is important to keep up-to-date on this developing case as this could mean tougher enforcement for providers in the future, amongst other things.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Logan Parker Privacy Editor Loyola University Chicago School of Law, LL.M. in Health Law 2017 &nbsp; The Federal Trade Commission (\u201cFTC\u201d) issued an Opinion and Final Order on July 29, 2016 against LabMD, a now defunct medical testing laboratory, for its lax data security practices that constituted an unfair practice under Section 5 of the &#8230;<br \/><a class=\"read-more-link btn btn-outline-secondary\" href=\"https:\/\/blogs.luc.edu\/compliance\/?p=167\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[914,1008,1216,1623,1795],"class_list":["post-167","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-ftc","tag-health-data","tag-labmd","tag-cybersecurity","tag-section-5"],"_links":{"self":[{"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/posts\/167","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=167"}],"version-history":[{"count":0,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=\/wp\/v2\/posts\/167\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=167"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=167"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.luc.edu\/compliance\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=167"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}