Advanced Care Hospital of Southern New Mexico reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-29. The breach occurred from 1/16/2024 to 2/4/2024. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Mar 29, 2024. View entity profile → Other incidents for this victim →
incident inc_78828ca7611a41eb · 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.
PHI · Identity (basic) · Government ID
MT NM
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 16, 2024
When the intrusion reportedly occurred, per the linked filings
Advanced Care Hospital of Southern New Mexico reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-29. The breach occurred from 1/16/2024 to 2/4/2024. 1 Montana residents were affected.
Affected (this filing): 1
Advanced Care Hospital of Southern New Mexico reported a ransomware incident affecting PHI of 1,162 individuals. Exposed data included names, dates of birth, Social Security and driver's license numbers, addresses, claims information, medications, and diagnoses/treatment information. The hospital notified HHS, affected individuals, and the media, posted substitute notice, offered free credit monitoring, implemented additional safeguards, and retrained staff.
Affected (this filing): 1,162
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.