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

Resource Anesthesiology Associates of CA PC — July 2022 breach

Clustered 5 filings across 3 jurisdictions · filing window Sep 23, 2022 Nov 7, 2022. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

5 filings

States

3

Affected · reported

15,507

First → last filing

Sep 23, 2022 Nov 7, 2022

Merge confidence

100%

incident inc_abc4afa6d52e4c73 · merged by llm · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. Intrusion Jul 9, 2022, discovered Jul 11, 2022 — the first regulatory filing landed 74 days later (flagged late). 15,507 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 45-day schedule across 5 filings beginning Sep 23, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
74days

Discovered → first regulatory filing

Discovery variance
73days

Range of discovered_at dates across filings

Filing span
45days

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 clocksCalifornia CA 60-day late · 105dMaine ME AG >30d · 33dHIPAA HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 9, 2022breach begins
Jul 11, 2022discovered · members disagree
notification delay · 74 days
Sep 23, 2022first filing
Nov 7, 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. SEP 23HHS OCRHHS OCR noticefirst filing · states nationwide total 15,507day 0
  2. OCT 24MT AGMT AG notice7 MT residents+31d
  3. OCT 25ME AGME AG noticestates nationwide total 15,507+32d
  4. OCT 25CA AGCA AG noticeno count stated+32d
  5. NOV 7HHS OCRHHS OCR noticemost recent · states nationwide total 1,308+45d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 11, 2022
MT AG
Discovered
Jul 11, 2022CA AGSep 22, 2022MT AG + ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR + MT AG + CA AG +1
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)

15,507

Sum of filed state slices

10· 0.1% 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
llm
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

45 days

Cadence

~1 / 11.3d

vs. multi-state median

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