Breach filing
ArchivedJewish Home Lifecare, Inc.: 104,234 individuals, Mar 2024.
Jewish Home Lifecare, Inc. reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 8 March 2024. The filing records the organisation as a healthcare provider in New York and lists 104,234 individuals affected, which makes it the 51st largest of the 511 New York filings on the register and the 123rd largest of the 741 filings submitted nationally in 2024. Among the 47 New York filings made in 2024 it ranks 10th.
Individuals affected
104,234
As reported to HHS
Modelled cost (IBM 2025)
$16.7M
Upper bound, method shown
Rank in NY
51st
of 511 New York filings
Rank in 2024
123rd
of 741 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
- 104,234
- Breach submission date
- 8 March 2024
- Submission year
- 2024
- Type of breach
- Hacking/IT Incident
- Location of breached information
- Network Server
- Business associate present
- No
- State
- New York (NY)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in New York by size
- 51st of 511
- Rank in 2024 nationally
- 123rd of 741
- New York median filing
- 5,338 individuals
- Register id (derived)
- NY-20240308-jewish-home-lifecare
Section F.2 / In context
Where this filing sits in New York and in 2024
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 328 of the 511 New York filings (64%) and on 83% of all filings submitted in 2024. Network Server appears on 49% of New York filings.
No business associate is recorded on the filing; 30% of New York filings do involve one. At 104,234 individuals the breach is 20 times the New York median filing of 5,338 and 26 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.
New York's breach notification statute (N.Y. Gen. Bus. Law 899-aa) requires notice to affected residents in the most expedient time possible and without unreasonable delay, no later than 30 days after discovery. Its attorney general threshold: all breaches (AG, Dept. of State, State Police). 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 104,234 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 $16.7M; the 2026 edition's $192 gives $20.0M. Both are modelled estimates with the method shown, not costs disclosed by Jewish Home Lifecare, Inc.. 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.
The covered entity (CE), Jewish Home Lifecare, reported that it experienced a ransomware incident that affected the protected health information (PHI) of 104,234 individuals. The PHI involved included names, addresses, dates of birth, Social Security numbers, claims information, diagnoses, and medications. The CE notified HHS, affected individuals, the media, and posted substitute notice on its website. In response to the breach, the CE offered free credit monitoring services and implemented additional administrative, technical, and security safeguards.
Section F.5 / Modelled cost
104,234 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
Upper boundIBM 2025 customer PII, $160 per record
$16.7M
104,234 x $160
IBM 2026 customer PII, $192 per record
$20.0M
104,234 x $192
Method: individuals affected, as reported by Jewish Home Lifecare, 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
New York statute and the HIPAA rule
State notification statute
New York: N.Y. Gen. Bus. Law 899-aa
amended by the SHIELD Act
- Notice to individuals
- In the most expedient time possible and without unreasonable delay, no later than 30 days after discovery
- Attorney general threshold
- All breaches (AG, Dept. of State, State Police) (Aligned with timing and content of individual notices)
- Private right of action
- Limited: Actual damages only; no statutory damages and no attorney-fee recovery; enforced primarily by the AG
- Penalty
- Greater of $5,000 or $20 per failed notification, capped at $250,000; safeguard violations up to $5,000 each
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
New York filings closest in size
Neighbours by size rank among New York filings in 2024, topped up from other years where 2024 has too few. Filings of 10,000 or more link to their own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| General Physician, P.C. | Healthcare Provider | 167,387 | 4 Oct 2024 | |||
| Long Island Plastic Surgical Group, P.C. | Healthcare Provider | 161,707 | 4 Oct 2024 | |||
| UNITE HERE | Business Associate | 95,797 | 23 Feb 2024 | |||
| Maternal Fetal Medicine Associates, PLLC, Carnegie Hill Imaging for Women, and Carnegie Women's Health (collectively, "the Practices") | Healthcare Provider | 79,691 | 15 Nov 2024 |
Index / Companion schedules
13 HHS breach register
→Hub: every filing, by state, year and entity.
04 Biggest breaches
→Mega-breaches with primary-source cost figures.
Industry / Healthcare
→IBM 2026: $6.64M average, 13 years at #1.
Regulation / HIPAA penalties
→OCR enforcement tiers and the 60-day rule.
11 50-state laws
→Deadline, AG threshold and penalties per state.
Cost / Per record
→Where the per-record model is reliable.
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 1128.
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.