DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 2 filings

San Francisco Department of Public Health — November 2017 breach

Clustered 2 filings across 1 jurisdiction · filing window May 11, 2018 → Jun 25, 2018. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

900

First → last filing

May 11, 2018 → Jun 25, 2018

Merge confidence

100%

incident inc_b8c67d5eb30943f2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. Intrusion Nov 20, 2017–Dec 27, 2017, discovered Dec 22, 2017 — the first regulatory filing landed 140 days later (flagged late). 900 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
140days

Discovered → first regulatory filing

Discovery variance
5days

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 delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksCalifornia✗ CA 60-day late · 140dHIPAA✗ HIPAA individual notice late · 135dFull clock table in Litigation Timeline

Incident timeline

Nov 20, 2017breach begins
Dec 22, 2017discovered · members disagree
notification delay · 140 days
May 11, 2018first filing
Jun 25, 2018most 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 11CA AGCA AG noticefirst filing · no count statedday 0
  2. JUN 25HHS OCRHHS OCR noticemost recent · states nationwide total 900+45d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 20, 2017 – Dec 9, 2017
CA AG
Discovered
Dec 22, 2017CA AGDec 27, 2017HHS OCRfilings disagree on discovery
Data types
PHI · Health (basic) · Identity (basic)
CA AG + HHS OCR
Attack vector
Third-Party / Supply Chain
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
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

45 days

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.