DisclosureLens
Leak SiteHHS OCRState AGConfirmed3 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedbianlianhigh sensitivity
Merged incident · 3 filings

Advantage Orthopedic & Sports Medicine Clinic — January 2024 breach

Clustered 3 filings across 2 jurisdictions · filing window Feb 15, 2024 Jul 29, 2024. View entity profile → Other incidents for this victim →

affected count agreeMerge100%

Determination

Confirmed

Members

3 filings

States

1

Affected · reported

1,937

First → last filing

Feb 15, 2024 Jul 29, 2024

Merge confidence

100%

incident inc_4b362fd9d5384141 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings and 1 unverified claim. The filing describes unauthorized access. Intrusion Jan 29, 2024–Feb 12, 2024, discovered Feb 11, 2024 — the first regulatory filing landed 169 days later (flagged late). 1,937 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
169days

Discovered → first regulatory filing

Leak precedence
164days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
164days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delayno SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksOregon OR AG >45dLeak gap Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 29, 2024breach begins
Feb 11, 2024discovered
notification delay · 169 days
Jul 29, 2024first filing
watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. FEB 15Leak sitebianlian postfirst filing · attacker claim · unverifiedday 0
  2. JUL 29OR AGOR AG noticestates nationwide total 1,937+164d
  3. JUL 29HHS OCRHHS OCR noticemost recent · states nationwide total 1,914+164d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 29, 2024Feb 12, 2024
OR AG
Discovered
Feb 11, 2024· 13d undetected
OR AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR
Attack vector
Unauthorized Access
HHS OCR

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing2 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 May 26, 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

164 days

Cadence

~1 / 82d

vs. multi-state median

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