MICHIGANHackingHealthcareHealthcarePhishingCustomer Data InvolvedIdentity (basic)Health (basic)MediumResolved

BEAUMONT HEALTH

bd_7667c2c21e38ca8a · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Jul 28, 2020

To disclose

—

Affected

6,073

Linked

2 filings

Confidence

50%

Full breach record for BEAUMONT HEALTH →5 incidents on file

Beaumont Health reported to HHS on 2020-07-28 a hacking/IT incident affecting 6,073 individuals. The breach resulted from an email phishing scheme targeting employees. Breached information, located on email and network servers, included names, addresses, dates of birth, clinical information, and medical record numbers.

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

Jul 28, 2020

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

New Hampshire State AGbd_7ff328d3f611f72b2020-08-10 · +13dVerified

Name: BEAUMONT HEALTH
norm: beaumont health
Industry: Health Care Services

Name: BEAUMONT HEALTH
norm: beaumont health
Industry: Health Care Services
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 6,073nationwide
Data types: Identity (basic)Health (basic)
HHS breach type: Hacking / IT incident
Where the data lived: EmailNetwork server
Covered-entity type: Healthcare provider
Attack vector: Unauthorized Access
Threat actor: External

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 · 2 states

View merged incident ↗

HHS OCRJul 28 · first · this page

New Hampshire State AG+13d

Pattern: first filing Jul 28 (MI), last Aug 10 (NH) — a 13-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: Jul 28, 2020
Raw hash: ad911984fced4d43d0c5956bf3833163735a41ae8ae44c3e8de4ebb93159e577

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.7 KB

Download View at source

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityBEAUMONT HEALTH

Victim entityBEAUMONT HEALTH

IncidentUnauthorized Access

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing