DisclosureLens
OHIOHackingHealthcareHealthcarePhishingCustomer Data InvolvedPHIHealth (basic)Identity (basic)MediumContained

Aultman Hospital

bd_942abb41fd568e2b · schema v1 · pii pii-v1

Severity

Medium

Discovered

Filed

Jul 3, 2024

To disclose

Affected

6,892

Linked

3 filings

Confidence

68%
Full breach record for Aultman Hospital4 incidents on file

Aultman Hospital reported to HHS on 2024-07-03 a Hacking/IT Incident affecting 6,892 individuals. Breached information located on Email. The incident involved an email phishing scheme exposing PHI including names, medical record numbers, and treatment information.

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

Jul 3, 2024

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 3 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Filing propagation · 3 filings · 2 states

View merged incident ↗
HHS OCRJun 21 · first
HHS OCR+12d · this page

Pattern: first filing Jun 21 (OH), last Jul 3 (OH) — a 12-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.