DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed11 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedrhysidahigh sensitivity
Merged incident · 11 filings

Bayhealth Medical Center — July 2024 breach

Clustered 11 filings across 10 jurisdictions · filing window Aug 7, 2024 → Feb 3, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

497,047

First → last filing

Aug 7, 2024 → Feb 3, 2025

Merge confidence

100%

incident inc_39c4400ac0e84dd9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jul 27, 2024–Jul 31, 2024, discovered Jul 27, 2024 — the first regulatory filing landed 69 days later (flagged late). 497,047 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 179-day schedule across 10 filings beginning Aug 7, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
69days

Discovered → first regulatory filing

Discovery variance
4days

Range of discovered_at dates across filings

Leak precedence
57days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
179days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksCalifornia✗ CA 60-day late · 187dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 187dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 27, 2024breach begins
Jul 27, 2024discovered · members disagree
notification delay · 69 days
Oct 4, 2024first filing
Feb 3, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. AUG 7Leak siterhysida postfirst filing · attacker claim · unverifiedday 0
  2. OCT 4HHS OCRHHS OCR noticestates nationwide total 497,047+57d
  3. FEB 1IL AGIL AG noticeno count stated+177d
  4. FEB 3NE AGNE AG notice66 NE residents+179d
  5. FEB 3NH AGNH AG notice185 NH residents+179d
  6. FEB 3CA AGCA AG noticeno count stated+179d
  7. FEB 3VT AGVT AG noticeno count stated+179d
  8. FEB 3MA AGMA AG notice894 MA residents+179d
  9. FEB 3DE AGDE AG noticeno count stated+179d
  10. FEB 3MT AGMT AG notice61 MT residents+179d
  11. FEB 3ME AGME AG noticemost recent · 257 ME residents+179d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 27, 2024 – Jul 31, 2024
NE AG
Discovered
Jul 27, 2024IL AGJul 31, 2024NE AG + NH AG + CA AG +4filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + NE AG + NH AG +6
Attack vector
Unauthorized Access
HHS OCR

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

497,047

Sum of filed state slices

1,463· 0.3% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US497,047
MA894
ME257
NH185
NE66
MT61

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing10 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 17, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

179 days

Cadence

~1 / 17.9d

vs. multi-state median

19.9× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.