TENNESSEEHackingHealthcareHealthcareBusiness Associate (HIPAA)Customer Data InvolvedData ExfiltratedPHIHealth (basic)Identity (basic)MediumContained

Erlanger Health

bd_34fde71941b72042 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

May 28, 2025

To disclose

—

Affected

3,371

Linked

2 filings

Confidence

69%

Full breach record for Erlanger Health →5 incidents on file

Erlanger Health reported to HHS on 2025-05-28 a Hacking/IT Incident affecting 3371 individuals. Breached information located on Network Server. The incident involved a business associate whose cybersecurity event exposed PHI (names, birthdates, medical record numbers, dates of service, sleep study info). Erlanger Health notified HHS, individuals, and media, and provided substitute notice on its website.

J jump to incidentP pin to compareR raw source

HIPAA clock✓ HHS notified

⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

⚠ No discovery dateThe OCR public portal omits the discovery date, so the 60-day notification clock cannot be evaluated from this source — only that the filing was submitted.

Incident timeline — partial

? — ?

Breach window unknown

May 28, 2025

Filed

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

This filing is one of 2 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

HHS OCRbd_2149d969ce7273d92025-04-10 · +48dCandidate

Name: Erlanger Health
norm: erlanger health
Industry: Health Care Services

Name: Erlanger Health
norm: erlanger health
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 3,371nationwide
Data types: PHIHealth (basic)Identity (basic)
HHS breach type: Hacking / IT incident
Where the data lived: Network server
Covered-entity type: Healthcare providerBusiness associate involved
Attack vector: Unauthorized Access
MITRE ATT&CK: T1041 Exfiltration Over C2 Channel
Threat actor: External
Regulator citations: Notified HHSOCR provided technical assistance regarding the HIPAA Rules

During the incident: Notified HHS
Notified affected individuals
Notified the media
Provided substitute notice on its website
Received technical assistance from OCR
Source: Quoted from the filing itself, not independently verified.

Compliance flags: HHS notified
Discovery-date grounding: no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.
Clock breakdown: Statute Window Elapsed Threshold Status
HIPAA
Discovered: not extracted
→ Notified: not extracted
— regulatory submission HHS notified

Statute	Window	Elapsed	Threshold	Status
HIPAA	Discovered: not extracted → Notified: not extracted	—	regulatory submission	HHS notified

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings

View merged incident ↗

HHS OCRApr 10 · first

HHS OCR+48d · this page

Pattern: first filing Apr 10 (TN), last May 28 (TN) — a 48-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://ocrportal.hhs.gov/ocr/breach/breach_report.jsf
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: May 28, 2025
Raw hash: 803f485600e0a644e00b4982614bfbcbae7b3768502c02d6611d3c20ade7d479

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html1.5 KB

Download View at source

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityErlanger Health

Victim entityErlanger Health

IncidentUnauthorized Access

Stated responseNotified HHS

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing