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

Florida Digestive Health Specialists — December 2020 breach

Clustered 6 filings across 6 jurisdictions · filing window Dec 27, 2021 → Jan 5, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

6

Affected · reported

212,509

First → last filing

Dec 27, 2021 → Jan 5, 2022

Merge confidence

100%

incident inc_6e60b742bf3e489e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. Intrusion Dec 16, 2020–Dec 21, 2020, discovered Dec 16, 2020 — the first regulatory filing landed 376 days later (flagged late). 212,509 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 9-day schedule across 6 filings beginning Dec 27, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
376days

Discovered → first regulatory filing

Discovery variance
5days

Range of discovered_at dates across filings

Filing span
9days

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 clocksMaine✗ ME AG >90d · 371dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 16, 2020breach begins
Dec 16, 2020discovered · members disagree
notification delay · 376 days
Dec 27, 2021first filing
Jan 5, 2022most 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. DEC 27MT AGMT AG noticefirst filing · 2 MT residentsday 0
  2. DEC 27ME AGME AG noticestates nationwide total 212,509day 0
  3. DEC 27NH AGNH AG notice21 NH residentsday 0
  4. DEC 27HHS OCRHHS OCR noticestates nationwide total 212,509day 0
  5. DEC 27IN AGIN AG noticestates nationwide total 212,509day 0
  6. JAN 5MA AGMA AG noticemost recent · 51 MA residents+9d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 16, 2020 – Dec 21, 2020
MT AG
Discovered
Dec 16, 2020MT AG + NH AGDec 21, 2020ME AGfilings disagree on discovery
Data types
Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI
MT AG + ME AG + NH AG +2
Attack vector
Phishing
MT 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)

212,509

Sum of filed state slices

122· 0.1% of stated

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

US212,509
MA51
IN37
NH21
ME11
MT2

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

9 days

Cadence

~1 / 1.8d

vs. multi-state median

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