Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
8,157
Data types
2
PHI · PII
Jurisdictions
1
WI
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Apr 30, 2026
When the intrusion reportedly occurred, per the linked filings
61 days
🧀Wisconsin State AGFirst filinglinked via same-victim cross-source · 100%
Wisconsin Department of Health Services reported a data breach to the Wisconsin DATCP. The public was notified on 2026-06-30. The incident occurred on April 30, 2026. Data accessed: Unknown. 8,157 individuals were affected. 8,157 Wisconsin residents were affected.
Wisconsin Department of Health Services reported an unauthorized access/disclosure involving 8,157 individuals. The breach involved paper/films and did not involve a business associate. The incident was submitted to HHS on July 1, 2026.
Affected (this filing): 8,157
HHS notified
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.