DisclosureLens
All incidentsView linkage analytics →
HHS OCRHHS OCR enforcementState AGEnforced10 filings · 7 statesLifecycle stage 3 of 3: EnforcedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

Premera Blue Cross — May 2014 breach

Clustered 10 filings across 7 jurisdictions · filing window Mar 17, 2015 → Sep 25, 2020. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Enforced

Members

10 filings

States

7

Affected · reported

11,000,000

First → last filing

Mar 17, 2015 → Sep 25, 2020

Merge confidence

100%

incident inc_1624ac02d5794e20 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion May 1, 2014–Jan 1, 2015, discovered Jan 1, 2015 — the first regulatory filing landed 75 days later. 11,000,000 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 2019-day schedule across 10 filings beginning Mar 17, 2015. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
75days

Discovered → first regulatory filing

Discovery variance
28days

Range of discovered_at dates across filings

Filing span
2019days

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 clocksHIPAA✓ HHS notifiedHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 1, 2014breach begins
Jan 1, 2015discovered · members disagree
notification delay · 75 days
Mar 17, 2015first filing
Sep 25, 2020most 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. MAR 17NH AGNH AG noticefirst filing · no count statedday 0
  2. MAR 17HHS OCRHHS OCR noticestates nationwide total 11,000,000day 0
  3. MAR 17CA AGCA AG noticeno count statedday 0
  4. MAR 18MA AGMA AG notice173 MA residents+1d
  5. MAR 19SC AGSC AG noticeno count stated+2d
  6. MAR 24HI AGHI AG notice19,174 HI residents+7d
  7. MAR 27NH AGNH AG noticeno count stated+10d
  8. APR 2NH AGNH AG noticeno count stated+16d
  9. MAY 4NH AGNH AG noticestates nationwide total 717+48d
  10. SEP 25HHS OCR enforcementHHS OCR enforcement noticemost recent · no count stated+2019d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 5, 2014
NH AG
Discovered
Jan 1, 2015HHS OCRJan 9, 2015NH AGJan 29, 2015NH AG + SC AG + HI AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NH AG + HHS OCR + CA AG +3
Attack vector
Unauthorized Access
NH 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)

11,000,000

Sum of filed state slices

19,348· 0.2% of stated

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

US11,000,000
HI19,174
MA173
NH1

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 7, 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

2019 days

Cadence

~1 / 224.3d

vs. multi-state median

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