DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed10 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 10 filings

Cardiovascular Associates Holdings, LP — November 2022 breach

Clustered 10 filings across 9 jurisdictions · filing window Feb 3, 2023 → Mar 17, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

9

Affected · reported

441,640

First → last filing

Feb 3, 2023 → Mar 17, 2023

Merge confidence

100%

incident inc_2ad818638daa4ac6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Nov 28, 2022–Dec 5, 2022, discovered Dec 5, 2022 — the first regulatory filing landed 60 days later. 441,640 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 6 more. Notifications rolled out on a 42-day schedule across 10 filings beginning Feb 3, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
60days

Discovered → first regulatory filing

Discovery variance
73days

Range of discovered_at dates across filings

Filing span
42days

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 >14 bdaySouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedCalifornia✓ CA 60-day OK · 60dMaine✓ ME AG ≤30d · 29dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_governmentminor

Incident timeline

Nov 28, 2022breach begins
Dec 5, 2022discovered · members disagree
notification delay · 60 days
Feb 3, 2023first filing
Mar 17, 2023most 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. FEB 3SC AGSC AG noticefirst filing · 2,037 SC residentsday 0
  2. FEB 3VT AGVT AG noticeno count statedday 0
  3. FEB 3MA AGMA AG notice188 MA residentsday 0
  4. FEB 3HHS OCRHHS OCR noticestates nationwide total 433,348day 0
  5. FEB 3MT AGMT AG notice9 MT residentsday 0
  6. FEB 3CA AGCA AG noticeno count statedday 0
  7. FEB 6NH AGNH AG notice91 NH residents+3d
  8. MAR 17CA AGCA AG noticeno count stated+42d
  9. MAR 17IN AGIN AG noticestates nationwide total 441,640+42d
  10. MAR 17ME AGME AG noticemost recent · states nationwide total 441,640+42d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 28, 2022 – Dec 5, 2022
SC AG
Discovered
Dec 5, 2022SC AG + VT AG + MT AG +2Feb 16, 2023ME AGfilings disagree on discovery
Data types
Financial · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · Minor · PHI · PII
SC AG + VT AG + HHS OCR +5
Attack vector
Unauthorized Access
SC AG

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)

441,640

Sum of filed state slices

2,369· 0.5% of stated

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

US441,640
SC2,037
MA188
NH91
IN42
MT9
ME2

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 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 12, 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

42 days

Cadence

~1 / 4.7d

vs. multi-state median

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