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

NextGen Healthcare, Inc. — March 2023 breach

Clustered 10 filings across 10 jurisdictions · filing window Apr 27, 2023 → May 5, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

1,049,375

First → last filing

Apr 27, 2023 → May 5, 2023

Merge confidence

100%

incident inc_bde4f28dd3d74c2d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Mar 29, 2023–Apr 14, 2023, discovered Mar 30, 2023 — the first regulatory filing landed 28 days later. 1,049,375 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 8-day schedule across 10 filings beginning Apr 27, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
28days

Discovered → first regulatory filing

Discovery variance
25days

Range of discovered_at dates across filings

Filing span
8days

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 bdayWashington⏱ WA AG >30dMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dCalifornia✓ CA 60-day OK · 29dMaine✓ ME AG ≤30d · 11dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 29, 2023breach begins
Mar 30, 2023discovered · members disagree
notification delay · 28 days
Apr 27, 2023first filing
May 5, 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. APR 27VT AGVT AG noticefirst filing · no count statedday 0
  2. APR 28MT AGMT AG notice3,343 MT residents+1d
  3. APR 28IN AGIN AG noticestates nationwide total 1,049,375+1d
  4. APR 28DE AGDE AG noticeno count stated+1d
  5. MAY 2MA AGMA AG notice16,228 MA residents+5d
  6. MAY 3WA AGWA AG notice21,981 WA residents+6d
  7. MAY 4OR AGOR AG noticestates nationwide total 1,049,375+7d
  8. MAY 5CA AGCA AG noticeno count stated+8d
  9. MAY 5NH AGNH AG notice1,094 NH residents+8d
  10. MAY 5ME AGME AG noticemost recent · states nationwide total 1,049,375+8d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 29, 2023 – Apr 14, 2023
VT AG
Discovered
Mar 30, 2023VT AG + MT AG + DE AG +3Apr 24, 2023OR AG + ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
VT AG + MT AG + DE AG +5
Attack vector
Unauthorized Access
VT 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)

1,049,375

Sum of filed state slices

63,560· 6.1% of stated

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

US1,049,375
WA21,981
IN17,001
MA16,228
ME3,913
MT3,343
NH1,094

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

8 days

Cadence

~1 / 0.9d

vs. multi-state median

1.0× faster

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.