All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed3 filings · 3 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 3 filings

Highlands-Cashiers Hospital — May 2012 breach

Clustered 3 filings across 3 jurisdictions · filing window Nov 26, 2014 → Dec 11, 2014. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

26,115

First → last filing

Nov 26, 2014 → Dec 11, 2014

Merge confidence

100%

incident inc_26c02c8da9234605 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe an accidental exposure. Intrusion May 1, 2012–Sep 1, 2014, discovered Sep 29, 2014 — the first regulatory filing landed 58 days later. 26,115 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 1 more. Notifications rolled out on a 15-day schedule across 3 filings beginning Nov 26, 2014. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

58days

Discovered → first regulatory filing

Filing span

15days

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 notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 1, 2012breach begins

Sep 29, 2014discovered

notification delay · 58 days

Nov 26, 2014first filing

Dec 11, 2014most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

NOV 26NH AGNH AG noticefirst filing · 5 NH residentsday 0
NOV 28MA AGMA AG notice26 MA residentsauto-linked+2d
DEC 11HHS OCRHHS OCR noticemost recent · states nationwide total 26,115auto-linked+15d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: May 1, 2012 – Sep 1, 2014
Discovered: Sep 29, 2014· 881d undetected
Data types: Identity (basic) · Government ID · Health (basic) · Financial account
Attack vector: Third-Party / Supply Chain

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)

26,115

Sum of filed state slices

31· 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 filing3 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

15 days

Cadence

~1 / 7.5d

vs. multi-state median

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