DisclosureLens
MINNESOTAHackingHealthcareHealthcareBusiness Associate (HIPAA)Customer Data InvolvedData ExfiltratedPHIHealth (basic)Identity (basic)Financial accountMediumContained

EpiSource

bd_2b5d69aa74007bf3 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Jun 2, 2023

To disclose

—

Affected

23,557

Linked

4 filings

Confidence

68%
Full breach record for EpiSource →3 incidents on file

Episource reported to HHS on 2023-06-02 a Hacking/IT Incident affecting 23,557 individuals. Breached information located on Network Server. The cyber-attack compromised PHI including names, DOB, addresses, MRNs, insurance info, diagnoses, and treatment data.

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

Jun 2, 2023

Filed

No interval is drawn: no breach start or discovery date is on record for this filing.

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

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

Filing propagation · 4 filings · 4 states

View merged incident ↗
California State AGJun 2 · first
HHS OCRJun 2 · first · this page

Pattern: first filing Jun 2 (CA), last Jun 9 (OR) — a 7-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.