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

Regal Medical Group, Inc. — December 2022 breach

Clustered 6 filings across 4 jurisdictions · filing window Feb 1, 2023 → Apr 11, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

3,685,626

First → last filing

Feb 1, 2023 → Apr 11, 2023

Merge confidence

100%

incident inc_4fdfdc67980d44b0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. Intrusion Dec 1, 2022–Dec 2, 2022, discovered Dec 8, 2022 — the first regulatory filing landed 55 days later (flagged late). 3,685,626 individuals reported across the linked filings. Data reported: Government ID, PHI, Identity (basic), and 2 more. Notifications rolled out on a 69-day schedule across 6 filings beginning Feb 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
55days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
69days

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 clocksVermont✗ VT AG >45 bdayOregon✗ OR AG >45dWashington✗ WA AG >90dCalifornia✓ CA 60-day OK · 55dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 1, 2022breach begins
Dec 8, 2022discovered
notification delay · 55 days
Feb 1, 2023first filing
Apr 11, 2023most 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 1CA AGCA AG noticefirst filing · no count statedday 0
  2. FEB 1HHS OCRHHS OCR noticestates nationwide total 3,388,856day 0
  3. MAR 28VT AGVT AG noticeno count stated+55d
  4. MAR 29CA AGCA AG noticeno count stated+56d
  5. APR 11OR AGOR AG noticestates nationwide total 3,685,626+69d
  6. APR 11WA AGWA AG noticemost recent · 2,224 WA residents+69d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 1, 2022 – Dec 2, 2022
CA AG
Discovered
Dec 8, 2022· 7d undetected
CA AG + VT AG + OR AG +1
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
CA AG + WA AG + VT AG +1
Attack vector
Ransomware
CA 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)

3,685,626

Sum of filed state slices

2,224· 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 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

69 days

Cadence

~1 / 13.8d

vs. multi-state median

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