Artesia General Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2019-08-27. The breach occurred from 6/11/2019 to 6/18/2019. 5 Montana residents were affected.
Affected (this filing): 5
Clustered 2 filings across 2 jurisdictions · filed Aug 27, 2019. View entity profile → Other incidents for this victim →
incident inc_b96b6b719ca447e2 · 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.
Identity (basic) · Government ID · Health (basic)
MT NM
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 11, 2019
When the intrusion reportedly occurred, per the linked filings
Artesia General Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2019-08-27. The breach occurred from 6/11/2019 to 6/18/2019. 5 Montana residents were affected.
Affected (this filing): 5
Artesia General Hospital (Artesia, NM) reported to HHS on 2019-08-27 a Hacking/IT Incident (email phishing) affecting 13,905 individuals. An employee fell victim to a phishing scheme, exposing ePHI including names, birthdates, diagnoses, addresses, and Social Security numbers stored in Email systems. The CE notified HHS, affected individuals, and media, then implemented additional administrative/technical safeguards and retrained staff. OCR obtained corrective-action assurances.
Affected (this filing): 13,905
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.