Sapphire Community Health reported a data breach to the Montana Attorney General. The breach was reported on 2021-04-18. The breach occurred on 2/18/2021. 3,751 Montana residents were affected.
Affected (this filing): 3,751
Clustered 2 filings across 1 jurisdiction · filing window Apr 18, 2021 → Apr 21, 2021. View entity profile → Other incidents for this victim →
incident inc_14e7f2b8e5a74b71 · merge_method deterministic · confidence 100%
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.
MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 18, 2021
When the intrusion reportedly occurred, per the linked filings
Sapphire Community Health reported a data breach to the Montana Attorney General. The breach was reported on 2021-04-18. The breach occurred on 2/18/2021. 3,751 Montana residents were affected.
Affected (this filing): 3,751
Sapphire Community Health, a Montana-based healthcare provider, reported a ransomware attack affecting the ePHI of 3,751 individuals. The breach exposed names, addresses, DOBs, SSNs, and financial information. The entity notified HHS, individuals, and media, and provided credit monitoring. Remediation included strengthening administrative and technical safeguards.
Affected (this filing): 3,751
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.