DisclosureLens
HHS OCRState AGConfirmed6 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 filings

Cross Timbers Health Clinics, Inc/ — December 2021 breach

Clustered 6 filings across 6 jurisdictions · filing window Feb 7, 2022 Feb 10, 2022. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

6 filings

States

6

Affected · reported

48,126

First → last filing

Feb 7, 2022 Feb 10, 2022

Merge confidence

100%

incident inc_3331c6fd255640f1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. Intrusion Dec 9, 2021–Dec 15, 2021, discovered Dec 15, 2021 — the first regulatory filing landed 54 days later. 48,126 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
54days

Discovered → first regulatory filing

Discovery variance
30days

Range of discovered_at dates across filings

Filing span
3days

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 clocksMaine ME AG ≤30d · 24dHIPAA HHS notifiedMassachusetts MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 9, 2021breach begins
Dec 15, 2021discovered · members disagree
notification delay · 54 days
Feb 7, 2022first filing
Feb 10, 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 7IN AGIN AG noticefirst filing · states nationwide total 48,126day 0
  2. FEB 7ME AGME AG noticestates nationwide total 48,126day 0
  3. FEB 7MT AGMT AG notice4 MT residentsday 0
  4. FEB 7HHS OCRHHS OCR noticestates nationwide total 48,126day 0
  5. FEB 8MA AGMA AG notice1 MA residents+1d
  6. FEB 10NH AGNH AG noticemost recent · 2 NH residents+3d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 9, 2021
IN AG
Discovered
Dec 15, 2021MT AG + NH AGJan 14, 2022ME AGfilings disagree on discovery
Data types
Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI
ME AG + MT AG + HHS OCR +2
Attack vector
Unauthorized Access
ME 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)

48,126

Sum of filed state slices

11· 0.0% of stated

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

US48,126
MT4
IN2
ME2
NH2
MA1

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

3 days

Cadence

~1 / 0.6d

vs. multi-state median

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