Enforced10 records · 8 statesUnverified claimConfirmedEnforcedcritical sensitivity

Merged incident · 10 records

Solara Medical Supplies — April 2019 breach

Clustered 10 records across 9 jurisdictions: 9 filings and 1 enforcement record · filing window Nov 13, 2019 → Nov 22, 2019 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Enforced

Members

10 records

States

Affected · reported

114,227

First → last dated filing

Nov 13, 2019 → Nov 22, 2019

Merge confidence

100%

incident inc_6478fb43a8d64075 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 enforcement record. The filings describe social engineering. Intrusion Apr 1, 2019–Jun 30, 2019, discovered Apr 1, 2019. 114,227 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 6 more. Notifications rolled out on a 9-day schedule across 8 dated filings beginning Nov 13, 2019. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Discovery variance

88days

Range of discovered_at dates across filings

Filing span

9days

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 clocksCalifornia✗ CA 60-day late · 138dHIPAA✗ HHS report lateMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_governmentminor

Incident timeline

Apr 1, 2019breach begins

Apr 1, 2019discovered · members disagree

Nov 13, 2019first dated filing

Nov 22, 2019most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and enforcement record in this incident

JAN 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
NOV 13WA AGWA AG noticefirst filing · 138 WA residentsoperator-confirmedday 0
NOV 13CA AGCA AG noticeno count statedauto-linkedday 0
NOV 13MT AGMT AG notice351 MT residentsauto-linkedday 0
NOV 13MA AGMA AG notice31 MA residentsauto-linkedday 0
NOV 13HHS OCRHHS OCR noticestates nationwide total 114,007auto-linkedday 0
NOV 13OR AGOR AG noticestates nationwide total 114,227operator-confirmedday 0
NOV 21SC AGSC AG notice188 SC residentsoperator-confirmed+8d
NOV 22NH AGNH AG notice12 NH residentsauto-linked+9d
JAN 14HHS OCR enforcementHHS OCR enforcement noticemost recent · no count statedoperator-confirmed+1889d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Apr 2, 2019 – Jun 20, 2019
Discovered: Apr 1, 2019HHS OCRApr 2, 2019IL AGJun 28, 2019WA AG + CA AG + MT AG +2filings disagree on discovery
Data types: Credentials · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · Minor · PHI · PII
Attack vector: Phishing

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)

114,227

Sum of filed state slices

720· 0.6% of stated

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

US114,227

MT351

SC188

WA138

MA31

NH12

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 filing10 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 Sep 23, 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

9 days

Cadence

~1 / 1.3d

vs. multi-state median

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