Clustered 2 filings across 2 jurisdictions · filed Jan 19, 2018. View entity profile → Other incidents for this victim →
incident inc_08f37f4f81e8407a · 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.
Health (basic) · Identity (basic) · Government ID
MD MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 21, 2017
When the intrusion reportedly occurred, per the linked filings
Westminster Ingleside King Farm Presbyterian Retirement Communities, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2018-01-19. The breach occurred on 11/21/2017. 6 Montana residents were affected.
Affected (this filing): 6
Westminster Ingleside King Farm Presbyterian Retirement Communities, Inc. (MD) reported to HHS OCR on 2018-01-19 a Hacking/IT Incident affecting 5,228 individuals. An unauthorized external user accessed the CE's IT network and infected it with malware. Breached PHI was located on Desktop Computer and Network Server, and included names, addresses, dates of birth, Social Security numbers, and clinical information. The CE notified HHS, affected individuals, and media, and offered free credit monitoring. Post-breach, the CE implemented dual-factor authentication and unauthorized-access monitoring. OCR reviewed HIPAA policies and risk analysis.
Affected (this filing): 5,228
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.