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 TN-20161230-bryan-myers-md-pc-ashley-dewitt-do-pc-miHHS OCR Breach Register, Tennessee

Breach filing

Archived

Bryan Myers, MD PC, Ashley DeWitt, DO PC, Michael Nobles, MD PC: 13,150 individuals, Dec 2016.

Bryan Myers, MD PC, Ashley DeWitt, DO PC, Michael Nobles, MD PC reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 30 December 2016. The filing records the organisation as a healthcare provider in Tennessee and lists 13,150 individuals affected, which makes it the 65th largest of the 196 Tennessee filings on the register and the 69th largest of the 328 filings submitted nationally in 2016. Among the 7 Tennessee filings made in 2016 it ranks 1st.

Individuals affected

13,150

As reported to HHS

Modelled cost (IBM 2025)

$2.10M

Method shown, not disclosed

Rank in TN

65th

of 196 Tennessee filings

Rank in 2016

69th

of 328 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
Healthcare Provider
Individuals affected
13,150
Breach submission date
30 December 2016
Submission year
2016
Type of breach
Hacking/IT Incident
Location of breached information
Network Server
Business associate present
No
Portal status
listed in the HHS OCR breach portal archive
Rank in Tennessee by size
65th of 196
Rank in 2016 nationally
69th of 328
Tennessee median filing
3,371 individuals
Register id (derived)
TN-20161230-bryan-myers-md-pc-ashley-dewitt-do-pc-mi

Section F.2 / In context

Where this filing sits in Tennessee and in 2016

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 121 of the 196 Tennessee filings (62%) and on 35% of all filings submitted in 2016. Network Server appears on 43% of Tennessee filings.

No business associate is recorded on the filing; 36% of Tennessee filings do involve one. At 13,150 individuals the breach is 3.9 times the Tennessee median filing of 3,371 and 3.3 times the national median of 4,000 across all 7,884 filings. It sits in the 10,000 to 99,999 band, which holds 1,938 filings.

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.

Tennessee's breach notification statute (Tenn. Code Ann. 47-18-2107) requires notice to affected residents immediately, but no later than 45 days from discovery or notification. Its attorney general threshold: no mandatory AG notification for private-sector breaches. 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 13,150 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 $2.10M; the 2026 edition's $192 gives $2.52M. Both are modelled estimates with the method shown, not costs disclosed by Bryan Myers, MD PC, Ashley DeWitt, DO PC, Michael Nobles, MD PC. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 0.4 times the sector average.

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.

The covered entity (CE), Premier Women's Health Center, discovered on November 2, 2016, that its EHR server had been infected with malware, affecting the electronic protected health information (ePHI) of 13,150 individuals. Information stored on the affected server included names, addresses, dates of birth, social security numbers, diagnoses/conditions, lab results, medications and other treatment information. The CE was able to disconnect the server from the network before any data was exfiltrated. The CE provided breach notification to HHS, to affected individuals, and to the media. OCR provided technical assistance to the CE regarding media notice and the performance of risk analyses. In response to the breach, the CE improved technical safeguards on its information system including upgrading firmware and software. The CE also implemented all new HIPAA policies and re-trained its workforce in May 2017. It initiated an enterprise-wide risk analysis through the aid of legal counsel. OCR obtained assurances that the CE implemented the corrective actions listed above.

Section F.5 / Modelled cost

13,150 individuals through IBM's per-record figures

Modelled cost / method shown, not a disclosed cost

Modelled

IBM 2025 customer PII, $160 per record

$2.10M

13,150 x $160

IBM 2026 customer PII, $192 per record

$2.52M

13,150 x $192

Method: individuals affected, as reported by Bryan Myers, MD PC, Ashley DeWitt, DO PC, Michael Nobles, MD PC 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

Tennessee statute and the HIPAA rule

State notification statute

Tennessee: Tenn. Code Ann. 47-18-2107

Notice to individuals
Immediately, but no later than 45 days from discovery or notification
Attorney general threshold
No mandatory AG notification for private-sector breaches
Private right of action
Yes: Affected customers may sue to recover damages and obtain injunctive relief
Penalty
AG may pursue civil penalties, injunctive relief, and restitution; class actions restricted

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

Tennessee filings closest in size

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

Covered entityTypeIndividualsSubmitted
Hamilton County GovernmentHealthcare Provider14,0813 Apr 2025
American Home PatientHealthcare Provider13,7096 Mar 2017
SEES Group, LLCHealthcare Provider13,00031 Dec 2019
Fred's Stores of Tennessee, IncorporatedHealthcare Provider9,62429 Sep 2016
Grace Primary Care, PCHealthcare Provider6,8537 Jun 2016

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 5354.

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.