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

Alliance Physical Therapy Group, LLC — December 2021 breach

Clustered 8 filings across 7 jurisdictions · filing window Feb 23, 2022 → Jun 14, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

197,588

First → last filing

Feb 23, 2022 → Jun 14, 2022

Merge confidence

100%

incident inc_e1102ba748e646e1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion Dec 23, 2021–Dec 27, 2021, discovered Dec 27, 2021 — the first regulatory filing landed 58 days later; 1 later filing was flagged late. 197,588 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 111-day schedule across 8 filings beginning Feb 23, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
58days

Discovered → first regulatory filing

Discovery variance
32days

Range of discovered_at dates across filings

Filing span
111days

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 clocksWashington✗ WA AG >90dHIPAA✓ HHS notifiedMaine✓ ME AG ≤30d · 26dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 23, 2021breach begins
Dec 27, 2021discovered · members disagree
notification delay · 58 days
Feb 23, 2022first filing
Jun 14, 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. FEB 23HHS OCRHHS OCR noticefirst filing · states nationwide total 197,588day 0
  2. FEB 23ME AGME AG noticestates nationwide total 14,970day 0
  3. FEB 23MA AGMA AG notice2 MA residentsday 0
  4. FEB 28NH AGNH AG notice1 NH residents+5d
  5. JUN 10MT AGMT AG notice37 MT residents+107d
  6. JUN 10CA AGCA AG noticeno count stated+107d
  7. JUN 10WA AGWA AG notice2,162 WA residents+107d
  8. JUN 14NH AGNH AG noticemost recent · 36 NH residents+111d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 23, 2021 – Dec 27, 2021
ME AG
Discovered
Dec 27, 2021NH AG + MT AG + CA AG +1Jan 28, 2022ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + WA AG + NH AG +4
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)

197,588

Sum of filed state slices

2,238· 1.1% of stated

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

US197,588
WA2,162
MT37
NH36
MA2
ME1

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

111 days

Cadence

~1 / 15.9d

vs. multi-state median

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