DisclosureLens
HHS OCRState AGConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 2 filings

Sonoma Valley Hospital — February 2013 breach

Clustered 2 filings across 1 jurisdiction · filing window May 24, 2013 → Jul 10, 2013. View entity profile → Other incidents for this victim →

✓ affected count, data types agreeMerge53%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

1,386

First → last filing

May 24, 2013 → Jul 10, 2013

Merge confidence

53%

incident inc_53092c8673844a1b · merged by llm · confidence 53%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes a misconfiguration. Intrusion Feb 14, 2013–Apr 17, 2013, discovered Apr 17, 2013 — the first regulatory filing landed 37 days later. 1,386 individuals reported across the linked filings. Data reported: PHI, Health (basic), and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
37days

Discovered → first regulatory filing

Filing span
47days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✓ HHS notifiedCalifornia✓ CA 60-day OK · 9dFull clock table in Litigation Timeline

Incident timeline

Feb 14, 2013breach begins
Apr 17, 2013discovered
notification delay · 37 days
May 24, 2013first filing
Jul 10, 2013most 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. MAY 24HHS OCRHHS OCR noticefirst filing · states nationwide total 1,386day 0
  2. JUL 10CA AGCA AG noticemost recent · no count stated+47d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 14, 2013 – Apr 17, 2013
CA AG
Discovered
Apr 17, 2013· 62d undetected
CA AG
Data types
Health (basic) · Identity (basic) · PHI
HHS OCR + CA AG
Attack vector
Misconfiguration
CA AG

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 claim

No leak-site claim on record for this incident.

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
llm
Confidence
0.53 · below the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (53% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

47 days

vs. multi-state median

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