DisclosureLens
HHS OCRState AGConfirmed5 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

Lifespan Physicians Group of Massachusetts, Inc. — December 2025 breach

Clustered 5 filings across 4 jurisdictions · filing window Jul 1, 2026 Jul 16, 2026. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

5 filings

States

4

Affected · reported

311,760

First → last filing

Jul 1, 2026 Jul 16, 2026

Merge confidence

100%

incident inc_dd30ebda59674313 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Dec 15, 2025–Dec 16, 2025, discovered Dec 16, 2025 — the first regulatory filing landed 197 days later. 311,760 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 5 more. Notifications rolled out on a 15-day schedule across 5 filings beginning Jul 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
197days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
15days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksHIPAA HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 15, 2025breach begins
Dec 16, 2025discovered
notification delay · 197 days
Jul 1, 2026first filing
Jul 16, 2026most 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. JUL 1MA AGMA AG noticefirst filing · no count statedday 0
  2. JUL 16VT AGVT AG notice86 VT residents+15d
  3. JUL 16NE AGNE AG noticeno count stated+15d
  4. JUL 16HHS OCRHHS OCR noticestates nationwide total 311,760+15d
  5. JUL 16NH AGNH AG noticemost recent · 1,129 NH residents+15d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 15, 2025Dec 16, 2025
MA AG
Discovered
Dec 16, 2025· 1d undetected
MA AG + NE AG + NH AG
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
MA AG + NE AG + HHS OCR +2
Attack vector
Unauthorized Access
MA 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)

311,760

Sum of filed state slices

1,215· 0.4% of stated

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

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 filing5 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
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

15 days

Cadence

~1 / 3.8d

vs. multi-state median

1.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.