DisclosureLens
GEORGIAMalwareHealthcareHealthcareRansomwareData EncryptedRansom DemandedCustomer Data InvolvedHealth (basic)Identity (basic)MediumResolved

Emory Healthcare

bd_b26522070c7a1d9d · schema v1 · pii pii-v1

Severity

Medium

Discovered

Filed

Feb 21, 2017

To disclose

Affected

79,930

Linked

2 filings

Confidence

50%
Full breach record for Emory Healthcare4 incidents on file

Emory Healthcare reported to HHS on 2017-02-21 a ransomware attack affecting 79,930 individuals. The breach involved protected health information, including names and dates of birth, located on a network server. In response, Emory Healthcare implemented additional security safeguards and received technical assistance from the Office for Civil Rights.

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

Feb 21, 2017

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

Filing propagation · 2 filings · 2 states

View merged incident ↗
Montana State AGFeb 21 · first
HHS OCRFeb 21 · first · this page

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.