Clustered 4 filings across 3 jurisdictions · filing window Feb 6, 2024 → May 24, 2024. View entity profile → Other incidents for this victim →
incident inc_7636e37f72eb4f3e · merge_method human · confidence 100%
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
MT PA
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 20, 2024
When the intrusion reportedly occurred, per the linked filings
Hypertension Nephrology Associates, a medical practice, is committed to being the region's pre-eminent provider of care to patients with kidney disease and high blood pressure.
Hypertension Nephrology Associates, a medical practice, is committed to being the region's pre-eminent provider of care to patients with kidney disease and high blood pressure.
Hypertension-Nephrology Associates, P.C. reported to HHS on 2024-05-14 a Hacking/IT Incident affecting 39,491 individuals. Breached information located on Electronic Medical Record, Network Server. The incident involved ransomware encrypting PHI including clinical, demographic, and financial data. The entity provided credit monitoring and implemented additional safeguards.
Hypertension-Nephrology Associates reported a data breach to the Montana Attorney General. The breach was reported on 2024-05-24. The breach occurred from 1/20/2024 to 2/6/2024. 2 Montana residents were affected.
Affected (this filing):
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.
Affected (this filing): 39,491