SUMMA HEALTH
ent_019e0d4b458d0a96548713c66f92ac68
Disclosures
4
HHS OCR · State AG · 2 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
7,989
as filed · HHS OCR OH
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- SUMMA HEALTH
- Normalized
- summa health— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- 549300N4NP4BSOJ08A82
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (4)newest first
- OHHHS OCRas victim2025-01-10
Summa Health (OH) reported to HHS on 2025-01-10 an Unauthorized Access/Disclosure affecting 874 individuals. A workforce member impermissibly accessed PHI stored in Electronic Medical Records, including names, addresses, birthdates, Social Security numbers, diagnoses, lab results, medications, and other treatment information. The covered entity sanctioned the workforce member and implemented additional administrative safeguards. No business associate was involved.
- OHHHS OCRas victim2019-06-28
Summa Health (OH) reported to HHS on 2019-06-28 a Hacking/IT Incident (email phishing) affecting 7,989 individuals. Several employees were victims of an email phishing scheme. PHI exposed included names, dates of birth, Social Security numbers, health insurance information, email addresses, diagnoses/conditions, medications prescribed, and treatment information. The CE notified affected individuals, media, and provided substitute notice. OCR obtained assurances of corrective action. Breached information located on Email.
- OHHHS OCRas victim2019-06-28
Summa Health reported to HHS on 2019-06-28 a Hacking/IT Incident affecting 2904 individuals. Breached information located on Email. Employees were victims of an email phishing scheme exposing PHI including names, MRNs, DOB, SSN, driver's license, and financial data. The CE implemented safeguards and retrained staff.
- 🦫Oregon State AGas victim2019-06-28
Summa Health reported a data breach to the Oregon Attorney General. The breach was reported on 2019-06-28. The breach occurred during 3/11/2019 - 3/29/2019. The breach was discovered on 5/1/2019. 7,989 individuals were affected. Notice was sent on 6/28/2019.