Anthem's $16 Million HIPAA Settlement Is Largest in History | Practical Law

Anthem's $16 Million HIPAA Settlement Is Largest in History | Practical Law

The Department of Health and Human Services (HHS), Office for Civil Rights (OCR) has announced a $16 million settlement with Anthem, the largest settlement ever for violations of the Health Insurance Portability and Accountability Act (HIPAA), following cyber attacks resulting in the theft of the electronic protected health information (ePHI) of nearly 79 million individuals. The settlement also requires Anthem to carry out a corrective action plan that includes a comprehensive risk analysis.

Anthem's $16 Million HIPAA Settlement Is Largest in History

Practical Law Legal Update w-017-0624 (Approx. 6 pages)

Anthem's $16 Million HIPAA Settlement Is Largest in History

by Practical Law Employee Benefits & Executive Compensation
Published on 17 Oct 2018USA (National/Federal)
The Department of Health and Human Services (HHS), Office for Civil Rights (OCR) has announced a $16 million settlement with Anthem, the largest settlement ever for violations of the Health Insurance Portability and Accountability Act (HIPAA), following cyber attacks resulting in the theft of the electronic protected health information (ePHI) of nearly 79 million individuals. The settlement also requires Anthem to carry out a corrective action plan that includes a comprehensive risk analysis.
On October 15, 2018, HHS announced a $16 million settlement with Anthem, Inc. – the largest HIPAA settlement in history – following targeted cyberattacks in 2014 and 2015 that resulted in the theft of the ePHI of nearly 79 million individuals. (The previous record HIPAA settlement, for $5.55 million, was paid to HHS in 2016; see Legal Update, HHS Claims a Record Haul With $5.55 Million HIPAA Settlement and Practice Note, HIPAA Enforcement: Settlement Agreements.) Anthem is a widely known health insurer and administrative services provider for many employment-based health plans. From a HIPAA perspective, and for purposes of the HHS settlement, Anthem is a business associate regarding the ePHI it maintained for Anthem's affiliated health plans (as HIPAA covered entities) (see Practice Note, HIPAA Privacy Rule: Affiliated Covered Entities and Standard Document, HIPAA Business Associate Agreement).

Background

HHS began investigating Anthem in early 2015 after media reports and information on Anthem's website indicated that the company had sustained an external cyber attack, which HHS characterized as an "advanced persistent threat attack" (see Article, Expert Q&A on the Impact of Cyber Attacks on Employer Group Health Plans and Related HIPAA Compliance). According to HHS, Anthem's systems were also compromised by "spear phishing" emails sent to a subsidiary; an employee responded to a malicious email and the attacks proliferated. In March 2015, Anthem provided HHS a breach notification informing the agency that cyber attackers had gained impermissible access to the company's IT system that maintained the ePHI of nearly 79 million individuals (see Practice Note, HIPAA Breach Notification Rules). The stolen ePHI included individuals' names, social security numbers, health identification numbers, birth dates, physical and email addresses, and employment information.
HHS's investigation identified potential violations of the HIPAA Privacy Rule and Security Rule, including requirements to:
  • Perform an accurate and thorough risk analysis of potential risks to ePHI held by Anthem.
  • Adopt adequate procedures to regularly review records of information system activity.
  • Identify and address advance detections of the security incident that resulted in the breach.
  • Implement sufficient technical policies and procedures for electronic information systems that maintain ePHI to restrict access to the individuals or software programs that were granted access rights.
  • Prevent unauthorized access to individuals' ePHI (as maintained on Anthem's "enterprise data warehouse").

Corrective Action Plan

In addition to the $16 million settlement payment, Anthem agreed to carry out a corrective action plan (CAP) addressing several aspects of HIPAA compliance (see HIPAA Privacy, Security, and Breach Notification Toolkit).

Security Management Process / Risk Analysis

Anthem must perform an accurate and thorough risk analysis of potential risks to ePHI that it holds, including an intermediate "statement of work" (SOW) for the risk analysis (see Article, HIPAA Compliance and the Limits of Gap Analyses). HHS will provide written technical assistance concerning the SOW, and HHS and Anthem will exchange updated versions of the SOW to address HHS's feedback until HHS approves it.
Anthem must furnish HHS its risk analysis within 210 days of when HHS approves the SOW. The risk analysis will also be subject to a back-and-forth feedback process, culminating in HHS's determination that the analysis was completed consistent with the SOW and the HIPAA Security Rule.

Policies and Procedures / Distribution

The CAP requires Anthem to review and revise its written policies and procedures to ensure compliance with HIPAA's Security Rule, including to specifically address certain topics (see Minimum Content Requirements). Anthem must submit its updated policies and procedures to HHS for feedback, and the parties will engage in a review process until HHS determines that the policies and procedures satisfy the Security Rule.
Anthem must distribute its revised policies and procedures to its existing workforce members who are subject to the policies and procedures (and who use or disclosure ePHI) within 30 days of when the policies and procedures are adopted. New workforce members must be furnished the policies and procedures after they join the company.

Minimum Content Requirements

Anthem's policies and procedures must specifically address the following Security Rule provisions:

Reportable Events and Other CAP Requirements

Anthem must investigate situations where a workforce member may have violated its policies and procedures. Anthem must timely notify HHS in writing of any material failures to comply with the policies and procedures, with materiality defined as a violation resulting in the presumed breach of unsecured PHI. Violations disclosed to HHS, referred to as reportable events, must satisfy specified content requirements (for example, what action Anthem will take to mitigate any harm resulting from the violation).
Anthem must also satisfy additional requirements under the CAP, including submission of an implementation report and annual reports for the duration of the CAP. (The CAP's compliance term is scheduled to last for two years from the agreement's effective date, unless Anthem violates the agreement during that time.) The CAP also requires Anthem to document its compliance with the agreement for a six-year recordkeeping period.
In addition, HHS may impose civil money penalties if it believes Anthem has violated the CAP and Anthem does not otherwise demonstrate its compliance with the CAP or fails to cure an alleged breach (see Legal Update, HHS Increases Civil Money Penalties for HIPAA Noncompliance, Effective October 11, 2018).

Practical Impact

The $16 million question for health plan covered entities and their business associates in light of this latest HHS settlement is easier stated than resolved: how do we prevent ourselves from becoming the next target of cyber attackers bent on infiltrating our systems and stealing individuals' ePHI? HHS has begun providing tools for addressing cyber attacks, though some of these resources are geared more toward incident response than to preventing an attack in the first place (see Article, Expert Q&A on the Impact of Cyber Attacks on Employer Group Health Plans and Related HIPAA Compliance). In the Anthem settlement, HHS focuses on at least two compliance shortfalls that contributed to the breach – not conducting an accurate and thorough risk analysis of potential risks to ePHI and not regularly reviewing records of information system activity. Regarding the phishing emails described in this settlement, a recent HHS cybersecurity newsletter addressed tips for avoiding such an attack (for example, using multi-factor authentication).