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-20170309-primary-care-specialistsHHS OCR Breach Register, Tennessee

Breach filing

Archived

Primary Care Specialists, Inc.: 65,000 individuals, Mar 2017.

Primary Care Specialists, Inc. reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 9 March 2017. The filing records the organisation as a healthcare provider in Tennessee and lists 65,000 individuals affected, which makes it the 36th largest of the 196 Tennessee filings on the register and the 18th largest of the 358 filings submitted nationally in 2017. Among the 11 Tennessee filings made in 2017 it ranks 1st.

Individuals affected

65,000

As reported to HHS

Modelled cost (IBM 2025)

$10.4M

Method shown, not disclosed

Rank in TN

36th

of 196 Tennessee filings

Rank in 2017

18th

of 358 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
65,000
Breach submission date
9 March 2017
Submission year
2017
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
36th of 196
Rank in 2017 nationally
18th of 358
Tennessee median filing
3,371 individuals
Register id (derived)
TN-20170309-primary-care-specialists

Section F.2 / In context

Where this filing sits in Tennessee and in 2017

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 42% of all filings submitted in 2017. Network Server appears on 43% of Tennessee filings.

No business associate is recorded on the filing; 36% of Tennessee filings do involve one. At 65,000 individuals the breach is 19 times the Tennessee median filing of 3,371 and 16 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 65,000 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 $10.4M; the 2026 edition's $192 gives $12.5M. Both are modelled estimates with the method shown, not costs disclosed by Primary Care Specialists, Inc.. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 1.9 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.

On February 27, 2017, the covered entity (CE), Primary Care Specialists, Inc., experienced a cyber-attack in which an unauthorized user accessed the CE's system by hacking a user account that had been granted administrative privileges. The CE initially reported that approximately 65,000 individuals were affected and the protected health information (PHI) involved included names, addresses, dates of birth, drivers' license numbers, social security numbers, claims information, diagnoses, lab results, and medications. However, after completing its investigation into the incident, which included a forensic analysis and the assistance of a third party IT service partner, the CE concluded that there was a low probability of compromise to any PHI. The CE provided OCR with documentation of its investigation and conclusion. To prevent a similar type of attack in the future, the CE reset all passwords, implemented new password requirements, reviewed and restructured domain administrator groups, disabled all external remote desktop access, retired the computer server from which the attacker gained access to the CE's system and deployed additional malware protections. The CE also instituted quarterly security reviews and revised its annual HIPAA training program. Additionally, though the CE ultimately determined there was no reportable breach, it provided individual notification of the incident to its current patients, HHS, the media, and on its website. OCR obtained assurances that the CE implemented the corrective actions listed above.

Section F.5 / Modelled cost

65,000 individuals through IBM's per-record figures

Modelled cost / method shown, not a disclosed cost

Modelled

IBM 2025 customer PII, $160 per record

$10.4M

65,000 x $160

IBM 2026 customer PII, $192 per record

$12.5M

65,000 x $192

Method: individuals affected, as reported by Primary Care Specialists, Inc. 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 2017, topped up from other years where 2017 has too few. Filings of 10,000 or more link to their own page.

Covered entityTypeIndividualsSubmitted
Mid-South Pulmonary & Sleep Specialists P.C.OpenHealthcare Provider70,21130 Dec 2025
Tri-Cities GastroenterologyOpenHealthcare Provider67,11529 Apr 2026
State of Tennessee State Insurance PlanHealth Plan60,58215 Aug 2014
Cleveland Medical Associates, PLLCHealthcare Provider22,00020 Jun 2017
American Home PatientHealthcare Provider13,7096 Mar 2017

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

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.