Form: Cost-of-Breach DisclosureSource: IBM Cost of a Data BreachFiled: 28 Apr 2026
DataBreachCost.comOpen calc
Independent breach-cost research, read by security and risk leaders.Sponsor this site →
Filing VA-20150312-virginia-department-of-medical-assistancHHS OCR Breach Register, Virginia

Breach filing

Archived

Virginia Department of Medical Assistance Services (VA-DMAS): 697,586 individuals, Mar 2015.

Virginia Department of Medical Assistance Services (VA-DMAS) reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 12 March 2015. The filing records the organisation as a health plan in Virginia and lists 697,586 individuals affected, which makes it the 7th largest of the 157 Virginia filings on the register and the 7th largest of the 270 filings submitted nationally in 2015. Among the 3 Virginia filings made in 2015 it ranks 1st.

Individuals affected

697,586

As reported to HHS

Modelled cost (IBM 2025)

$112M

Upper bound, method shown

Rank in VA

7th

of 157 Virginia filings

Rank in 2015

7th

of 270 filings nationally

Section F.1 / The filing

As posted by HHS OCR

Every value below is the portal's own field for this filing, plus its rank within the register.

Covered entity type
Health Plan
Individuals affected
697,586
Breach submission date
12 March 2015
Submission year
2015
Type of breach
Hacking/IT Incident
Location of breached information
Network Server
Business associate present
Yes
Portal status
listed in the HHS OCR breach portal archive
Rank in Virginia by size
7th of 157
Rank in 2015 nationally
7th of 270
Virginia median filing
4,441 individuals
Register id (derived)
VA-20150312-virginia-department-of-medical-assistanc

Section F.2 / In context

Where this filing sits in Virginia and in 2015

OCR classifies the incident as a hacking or IT incident, with the breached information held in a network server. Hacking/IT Incident is the type recorded on 99 of the 157 Virginia filings (63%) and on 21% of all filings submitted in 2015. Network Server is the most common location in the state, appearing on 53% of Virginia filings.

A business associate is recorded as present on the filing, as it is on 39% of Virginia filings. At 697,586 individuals the breach is 157 times the Virginia median filing of 4,441 and 174 times the national median of 4,000 across all 7,884 filings. It is one of 801 filings of 100,000 or more individuals.

As of 28 August 2026 the case is listed in the HHS OCR breach portal archive. OCR's closing summary of the case is reproduced in full below.

Virginia's breach notification statute (Va. Code 18.2-186.6) requires notice to affected residents without unreasonable delay. Its attorney general threshold: all breaches (concurrent with individual notice). The HIPAA Breach Notification Rule ran alongside it: notice to affected individuals and to HHS without unreasonable delay and no later than 60 days after discovery, which is the clock that put this filing on the portal.

Multiplying 697,586 individuals by IBM's $160 customer-PII cost per record (Cost of a Data Breach 2025, the figure the site's calculator uses) gives a modelled $112M; the 2026 edition's $192 gives $134M. Both are modelled estimates with the method shown, not costs disclosed by Virginia Department of Medical Assistance Services (VA-DMAS). Because the filing is above the roughly 100,000-record range in which the per-record figure is reliable, the result is an upper bound, not an estimate: fixed costs are spread across far more records at this scale.

Section F.3 / OCR closing summary

The portal's archived description, in full

Written by the Office for Civil Rights when the case was closed and reproduced verbatim from the HHS export.

Healthkeepers, a business associate (BA) of Virginia Department of Medical Assistance Services, the covered entity (CE), stored the CE's electronic protected health information (ePHI) on computer servers belonging to its parent corporation, Anthem, Inc. Anthem experienced a series of cyberattacks which exposed the electronic protected health information (ePHI) of almost 79 million people, affecting 697,586 individuals who received health insurance from the CE. The ePHI involved included names, social security numbers, medical identification numbers, addresses, dates of birth, email addresses, and employment information. OCR reviewed the BA agreement and determined that it appeared to comply with the requirements of the HIPAA Privacy and Security Rules. OCR opened a separate review of Anthem, which resulted in Anthem agreeing to pay a monetary settlement and undertaking a robust corrective action plan to comply with the HIPAA Rules.

Section F.5 / Modelled cost

697,586 individuals through IBM's per-record figures

Modelled cost / method shown, not a disclosed cost

Upper bound

IBM 2025 customer PII, $160 per record

$112M

697,586 x $160

IBM 2026 customer PII, $192 per record

$134M

697,586 x $192

Method: individuals affected, as reported by Virginia Department of Medical Assistance Services (VA-DMAS) to HHS, multiplied by IBM's customer-PII cost per record (Cost of a Data Breach 2025 Figure 6 and the 2026 edition). No cost has been disclosed by the entity for this filing; the figure is a planning estimate, not a fact about the breach. IBM's per-record figures come from mid-volume breaches and IBM cautions against applying them to breaches involving millions of records; the site's per-record page explains where the multiplication holds and where it breaks down.

Context: IBM's average cost of a healthcare breach is $6.64M in the 2026 report ($7.42M in 2025); the global average across all sectors was $4.44M in 2025.

Cost per record: method and limits / Healthcare breach cost, IBM 2026

Section F.6 / Notification clock

Virginia statute and the HIPAA rule

State notification statute

Virginia: Va. Code 18.2-186.6

Notice to individuals
Without unreasonable delay
Attorney general threshold
All breaches (concurrent with individual notice) (Concurrent with individual notification)
Private right of action
Limited: Individuals may recover direct economic damages (no non-economic damages)
Penalty
AG may impose civil penalties up to $150,000 per breach

The HIPAA Breach Notification Rule runs alongside the state statute: notice to affected individuals and to HHS without unreasonable delay and no later than 60 days after discovery.

Section F.7 / Peer filings

Virginia filings closest in size

Neighbours by size rank among Virginia filings in 2015, topped up from other years where 2015 has too few. Filings of 10,000 or more link to their own page.

Covered entityTypeIndividualsSubmitted
Virginia Department of Medical Assistance ServicesHealth Plan1,229,33318 Sep 2023
Inova Health SystemHealthcare Provider1,045,2709 Sep 2020
R&B Corporation of Virginia d/b/a Credit Control CorporationBusiness Associate607,78713 May 2023
Heartland Health ClinicHealthcare Provider3,65021 Sep 2015
Sentara HealthcareHealthcare Provider1,0402 Oct 2015

Index / Companion schedules

Provenance

Source: U.S. Department of Health and Human Services, Office for Civil Rights, Breach Portal (breaches affecting 500 or more individuals), retrieved 2026-08-28. Public domain. Individuals affected and dates as reported by the covered entity.

Portal: ocrportal.hhs.gov breach report. Statutory basis: HITECH Act section 13402(e)(4): the Secretary must post a list of breaches of unsecured protected health information affecting 500 or more individuals. Breaches affecting fewer than 500 individuals are reported to OCR annually and are not posted, so they are not on this register. Status wording follows the portal's two tabs ("Cases Currently Under Investigation" and "Archive") as of 28 August 2026; a filing moves to the archive when OCR closes the case. Modelled costs on this site are a method applied to the reported count, using IBM Cost of a Data Breach per-record figures, and are never a cost disclosed by the entity. This row: hhs-breach-archive__2026-08-28.csv, export row 5904.

Corrections: if you represent a listed entity and the portal row has been amended, email [email protected] with the portal entry and we will re-pull the export.