Confirmed breach. Intrusion Apr 17, 2021–May 5, 2021, discovered May 1, 2021 — the first regulatory filing landed 150 days later (flagged late). 951 individuals reported across the linked filings.
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 clocksMaine✗ ME AG >90d · 150dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
951
Data types
—
Jurisdictions
2
KY ME
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Apr 17, 2021 → May 5, 2021
When the intrusion reportedly occurred, per the linked filings
Breach discovered
May 1, 2021
Reported by MAINE AG filing
150 days
🦞Maine State AGFirst filinglinked via same-victim cross-source · 100%
Humana, a healthcare business associate, reported an internal system breach affecting 3 Maine residents. The breach occurred between April 17, 2021, and May 5, 2021, and was discovered on May 1, 2021. The company offered a minimum of 12 months of free credit monitoring to affected individuals.
Affected (this filing): 3
ME AG >90d · 150d
🇺🇸KYHHS OCRMost recentlinked via same-victim cross-source · 100%
Humana Inc. (Health Plan, KY) reported to HHS on 2021-09-28 an Unauthorized Access/Disclosure affecting 948 individuals. A business associate employee inadvertently mailed PHI — including names, addresses, dates of birth, diagnoses, conditions, and other treatment information — to wrong recipients via paper/films. Humana notified HHS and affected individuals; the BA strengthened administrative safeguards in response.
Affected (this filing): 948
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.