R1 RCM Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2023-01-30 and was reported on 2024-03-11. 4 Indiana residents were affected. 16,121 individuals affected in total.
Affected (this filing): 16,121
Clustered 2 filings across 2 jurisdictions · filed Mar 11, 2024. View entity profile → Other incidents for this victim →
incident inc_eaf34d9199e44f93 · 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)
IL IN
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 30, 2023
When the intrusion reportedly occurred, per the linked filings
R1 RCM Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2023-01-30 and was reported on 2024-03-11. 4 Indiana residents were affected. 16,121 individuals affected in total.
Affected (this filing): 16,121
R1 RCM Inc. (Business Associate, IL) reported to HHS on 2024-03-11 a Hacking/IT Incident affecting 16,121 individuals. Breached information was located on a Network Server. The PHI involved included names, addresses, dates of birth, social security numbers, diagnoses, and conditions. The BA notified HHS, affected individuals, and the media, and implemented additional administrative and technical safeguards as mitigation.
Affected (this filing): 16,121
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.