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 CT-20160525-stamford-podiatry-group-pcHHS OCR Breach Register, Connecticut

Breach filing

Archived

Stamford Podiatry Group .P.C: 40,491 individuals, May 2016.

Stamford Podiatry Group .P.C reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 25 May 2016. The filing records the organisation as a healthcare provider in Connecticut and lists 40,491 individuals affected, which makes it the 21st largest of the 144 Connecticut filings on the register and the 28th largest of the 328 filings submitted nationally in 2016. Among the 6 Connecticut filings made in 2016 it ranks 1st.

Individuals affected

40,491

As reported to HHS

Modelled cost (IBM 2025)

$6.48M

Method shown, not disclosed

Rank in CT

21st

of 144 Connecticut filings

Rank in 2016

28th

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
40,491
Breach submission date
25 May 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 Connecticut by size
21st of 144
Rank in 2016 nationally
28th of 328
Connecticut median filing
5,000 individuals
Register id (derived)
CT-20160525-stamford-podiatry-group-pc

Section F.2 / In context

Where this filing sits in Connecticut 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 91 of the 144 Connecticut filings (63%) and on 35% of all filings submitted in 2016. Network Server appears on 44% of Connecticut filings.

No business associate is recorded on the filing; 35% of Connecticut filings do involve one. At 40,491 individuals the breach is 8.1 times the Connecticut median filing of 5,000 and 10 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.

Connecticut's breach notification statute (Conn. Gen. Stat. 36a-701b) requires notice to affected residents without unreasonable delay, no later than 60 days after discovery. Its attorney general threshold: all breaches (no minimum resident threshold). 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 40,491 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 $6.48M; the 2026 edition's $192 gives $7.77M. Both are modelled estimates with the method shown, not costs disclosed by Stamford Podiatry Group .P.C. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 1.2 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 April 14, 2016, the covered entity (CE), Stamford Podiatry Group P.C., learned that an unauthorized individual(s) had gained privileged access and compromised its computer server between February 2, 2016 and April 14, 2016, including its electronic record database. The breach affected 40,491 individuals and included demographic, financial, and clinical information. OCR reviewed the CE's policies and procedures as relevant to this breach and they appeared to be in compliance with the Privacy and Security Rule. The CE retrained staff, implemented an upgraded, more secure data backup solution, and enhanced safeguards for its information technology (IT) system, including completely rebuilding its IT operating environment. The CE implemented new risk management policies and plans, improved its processes for managing and monitoring its vendors, and reduced the amount of PHI and personally identifiable information in its possession. OCR obtained assurances that the CE provided breach notification to affected individuals and the media in accordance with the Breach Notification Rule.

Section F.5 / Modelled cost

40,491 individuals through IBM's per-record figures

Modelled cost / method shown, not a disclosed cost

Modelled

IBM 2025 customer PII, $160 per record

$6.48M

40,491 x $160

IBM 2026 customer PII, $192 per record

$7.77M

40,491 x $192

Method: individuals affected, as reported by Stamford Podiatry Group .P.C 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

Connecticut statute and the HIPAA rule

State notification statute

Connecticut: Conn. Gen. Stat. 36a-701b

Notice to individuals
Without unreasonable delay, no later than 60 days after discovery
Attorney general threshold
All breaches (no minimum resident threshold) (No later than the time notice is provided to affected residents)
Private right of action
No: Non-compliance is an unfair trade practice; only the AG enforces
Penalty
Up to $5,000 per willful violation under CUTPA, plus injunctive relief and restitution

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

Connecticut filings closest in size

Neighbours by size rank among Connecticut 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
Tobin, Carberry, O'Malley, Riley & Selinger, P.C.Business Associate47,10617 Apr 2024
Connecticut GI, PLLCHealthcare Provider46,35419 Aug 2024
Saint Francis Healthcare PartnersBusiness Associate38,5294 May 2020
Aetna Inc.Business Associate18,85428 Nov 2016
Group Life Hospital and Medical ProgramHealth Plan3,00029 Feb 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 5559.

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.