StayWell Health Management, LLC reported to HHS on 2014-02-25 a Unauthorized Access/Disclosure affecting 1511 individuals. Breached information located on Network Server.
Affected (this filing): 1,511
Clustered 2 filings across 1 jurisdiction · filing window Feb 25, 2014 → Mar 18, 2014. View entity profile → Other incidents for this victim →
incident inc_ed656a79843e47e4 · merge_method deterministic · confidence 88%
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.
Health (basic) · Identity (basic) · Metadata
MN
all HHS OCR
Earliest sighting first · deep chronology in Litigation Timeline
StayWell Health Management, LLC reported to HHS on 2014-02-25 a Unauthorized Access/Disclosure affecting 1511 individuals. Breached information located on Network Server.
Affected (this filing): 1,511
StayWell Health Management LLC (Business Associate, MN) was reported to HHS on 2014-03-18 for an Unauthorized Access/Disclosure affecting 1,746 individuals. The BA disclosed PHI on the internet, including names, email addresses, unique StayWell identification numbers, and wellness program participation data. The covered entity QBE Holdings, Inc. filed the report. OCR investigated and obtained assurances that corrective actions — including risk assessment, updated policies, and employee training — were implemented. Breached information was located on a Network Server.
Affected (this filing): 1,746
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.