Clustered 2 filings across 1 jurisdiction · filing window Dec 8, 2023 → Dec 14, 2023. View entity profile → Other incidents for this victim →
incident inc_f2de1e2aee554e59 · merge_method llm · confidence 66%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID
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.
ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 31, 2023
When the intrusion reportedly occurred, per the linked filings
Oct 27, 2023
Reported by MAINE AG filings
Florida Community Care, LLC, a healthcare provider, experienced an external hacking incident that was discovered on October 27, 2023. The breach, which occurred on May 31, 2023, compromised the names and Social Security numbers of individuals. In response, the company offered two years of credit monitoring services through TransUnion / Cyberscout's Identity Force to the 2 affected Maine residents.
Affected (this filing): 2
Florida Community Care, LLC, a healthcare entity based in Miami, FL, reported an external system breach (hacking) occurring on May 31, 2023, discovered on October 27, 2023. The incident affected 30,891 individuals, including 2 Maine residents. The breach involved the acquisition of personal identifiers and government IDs. The entity provided written notification and offered two years of credit monitoring services through TransUnion/Cyberscout.
Affected (this filing): 30,891
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.