All incidents View linkage analytics →Get the evidence package — $79

Confirmed2 filings · 2 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 2 filings

Medical Management, LLC — February 2013 breach

Clustered 2 filings across 2 jurisdictions · filing window May 13, 2015 → May 15, 2015. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

20,512

First → last filing

May 13, 2015 → May 15, 2015

Merge confidence

100%

incident inc_dfe5f4a48eb84da7 · merged by deterministic · confidence 100%

Confirmed breach. One breach, 2 legal records. Intrusion Feb 1, 2013–Mar 1, 2015, discovered Mar 16, 2015 — the first regulatory filing landed 58 days later. 20,512 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

58days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

2days

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 report on timeFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 1, 2013breach begins

Mar 16, 2015discovered

notification delay · 58 days

May 13, 2015first filing

May 15, 2015most recent filing

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

Member cascade — every filing about this breach

MAY 13NH AGNH AG noticefirst filing · 10 NH residentsauto-linkedday 0
MAY 15HHS OCRHHS OCR noticemost recent · states nationwide total 20,512auto-linked+2d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Feb 1, 2013 – Mar 1, 2015
Discovered: Mar 16, 2015· 773d undetected
Data types: Identity (basic) · Government ID
Attack vector: Insider
Response: Notified each CE of the breach · Established a call center · Sent letters to the potentially affected individuals on behalf of its CEs

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)

20,512

Sum of filed state slices

10· 0.0% 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 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

2 days

vs. multi-state median

2.5× faster

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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.