DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed35 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 35 filings

Harvard Pilgrim Health Care — March 2023 breach

Clustered 35 filings across 10 jurisdictions · filing window May 24, 2023 → Nov 13, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

35 filings

States

10

Affected · reported

2,967,396

First → last filing

May 24, 2023 → Nov 13, 2025

Merge confidence

100%

incident inc_e18630ff1bcc4480 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 35 regulatory filings. Intrusion Mar 28, 2023–Apr 17, 2023, discovered Apr 17, 2023 — the first regulatory filing landed 37 days later (flagged late). 2,967,396 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 904-day schedule across 35 filings beginning May 24, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
37days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
904days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 94dOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 304dWashington⏱ WA AG >30dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 28, 2023breach begins
Apr 17, 2023discovered
notification delay · 37 days
May 24, 2023first filing
Nov 13, 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. MAY 24HHS OCRHHS OCR noticefirst filing · states nationwide total 2,662,337day 0
  2. JUN 15DE AGDE AG noticeno count stated+22d
  3. JUN 15WA AGWA AG notice8,358 WA residents+22d
  4. JUN 15VT AGVT AG noticeno count stated+22d
  5. JUN 15DE AGDE AG noticeno count stated+22d
  6. JUN 15MT AGMT AG notice1,415 MT residents+22d
  7. JUN 15ME AGME AG noticestates nationwide total 2,550,922+22d
  8. JUN 15OR AGOR AG noticestates nationwide total 2,550,922+22d
  9. JUN 20NH AGNH AG notice206,752 NH residents+27d
  10. JUL 20CA AGCA AG noticeno count stated+57d
  11. JUL 20NH AGNH AG noticeno count stated+57d
  12. JUL 20ME AGME AG noticestates nationwide total 2,550,922+57d
  13. JUL 20VT AGVT AG noticeno count stated+57d
  14. JUL 20DE AGDE AG noticeno count stated+57d
  15. AUG 15DE AGDE AG noticeno count stated+83d
  16. AUG 24NH AGNH AG noticeno count stated+92d
  17. AUG 25ME AGME AG noticestates nationwide total 2,550,922+93d
  18. AUG 25CA AGCA AG noticeno count stated+93d
  19. AUG 25VT AGVT AG noticeno count stated+93d
  20. FEB 15ME AGME AG noticestates nationwide total 2,632,275+267d
  21. FEB 15DE AGDE AG noticeno count stated+267d
  22. FEB 15CA AGCA AG noticeno count stated+267d
  23. FEB 15NH AGNH AG notice1,347 NH residents+267d
  24. MAR 27CA AGCA AG noticeno count stated+308d
  25. MAR 27ME AGME AG noticestates nationwide total 2,860,795+308d
  26. MAR 27DE AGDE AG noticeno count stated+308d
  27. MAR 27NH AGNH AG notice9,766 affected+308d
  28. MAR 27VT AGVT AG noticeno count stated+308d
  29. OCT 3CA AGCA AG noticeno count stated+498d
  30. OCT 3ME AGME AG noticestates nationwide total 2,967,396+498d
  31. OCT 3NH AGNH AG noticeno count stated+498d
  32. OCT 3DE AGDE AG noticeno count stated+498d
  33. JAN 21VT AGVT AG noticeno count stated+608d
  34. JAN 21CA AGCA AG noticeno count stated+608d
  35. NOV 13MD AGMD AG noticemost recent · 8 MD residents+904d
  36. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 28, 2023 – Apr 17, 2023
DE AG
Discovered
Apr 17, 2023· 20d undetected
DE AG + WA AG + VT AG +6
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + DE AG + WA 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)

2,967,396

Sum of filed state slices

426,887· 14.4% of stated

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

US2,967,396
ME210,354
NH206,752
WA8,358
MT1,415
MD8

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing35 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 10, 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

904 days

Cadence

~1 / 26.6d

vs. multi-state median

113.0× 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.