Enforced4 filings · 3 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 4 filings

Health Fitness Corporation — August 2015 breach

Clustered 4 filings across 3 jurisdictions · filing window Oct 5, 2018 → Mar 21, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Enforced

Members

4 filings

States

Affected · reported

614

First → last filing

Oct 5, 2018 → Mar 21, 2025

Merge confidence

100%

incident inc_2f602fe21c16437b · merged by llm · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe a misconfiguration. Intrusion Aug 1, 2015, discovered Jun 27, 2018 — the first regulatory filing landed 100 days later (flagged late). 614 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 1 more. Notifications rolled out on a 2359-day schedule across 4 filings beginning Oct 5, 2018. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

100days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

2359days

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

Sensitive data

identity_government

Incident timeline

Aug 1, 2015breach begins

Jun 27, 2018discovered

notification delay · 100 days

Oct 5, 2018first filing

Mar 21, 2025most recent filing

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

Member cascade — every filing about this breach

OCT 5MA AGMA AG noticefirst filing · 175 MA residentsauto-linkedday 0
OCT 15HHS OCRHHS OCR noticestates nationwide total 550auto-linked+10d
OCT 28HHS OCRHHS OCR noticestates nationwide total 614+23d
MAR 21HHS OCR enforcementHHS OCR enforcement noticemost recent · no count statedoperator-confirmed+2359d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Aug 1, 2015
Discovered: Jun 27, 2018· 1061d undetected
Data types: Health (basic) · Identity (basic) · Government ID · PHI
Attack vector: Misconfiguration

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)

614

Sum of filed state slices

175· 28.5% of stated

71% 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 filing4 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: 1.00 · above the 0.85 auto-merge floor
Reviewed: operator-reviewed Aug 21, 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

2359 days

Cadence

~1 / 786.3d

vs. multi-state median

294.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.