Clustered 4 filings across 4 jurisdictions · filing window Oct 25, 2024 → Nov 6, 2024. View entity profile → Other incidents for this victim →
incident inc_74740173e46b4920 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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.
HI IN MT VT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 20, 2024
When the intrusion reportedly occurred, per the linked filings
Aug 26, 2024
Reported by VERMONT AG filing
Hawaii Radiologic Associates Ltd reported a data breach to the Indiana Attorney General. The breach occurred on 2024-08-20 and was reported on 2024-10-25. 6 Indiana residents were affected. 22,915 individuals affected in total.
Affected (this filing): 22,915
Hawaii Radiologic Associates, Ltd. reported to HHS on 2024-10-25 a Hacking/IT Incident affecting 23205 individuals. Breached information located on Network Server.
Affected (this filing): 23,205
Hawaii Radiological Associates, Ltd. reported a data breach to the Montana Attorney General. The breach was reported on 2024-11-05. The breach occurred from 8/20/2024 to 8/25/2024. 10 Montana residents were affected.
Affected (this filing): 10
Hawaii Radiologic Associates, Ltd. notified consumers of a security incident where an unknown actor gained unauthorized access to systems between August 20-25, 2024. Suspicious activity was detected on August 26, 2024. Impacted data included names, dates of birth, health insurance subscriber IDs, and exam details. No evidence of misuse was found. The company reported the incident to federal law enforcement and is reviewing security protocols.
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.