OSF HEALTHCARE SYSTEM
bd_7fbc6210e9c1f4d5 · schema v1 · pii pii-v1
Full breach record for OSF HEALTHCARE SYSTEM →10 incidents on fileRegulator's decision — not a breach notification
This record is a regulator's decision, not the organisation's own breach notice. Breach-notification fields (discovery date, notification clock) are structurally absent — what this source establishes is the outcome and the provisions the decision cites.
HHS OCR settled a ransomware investigation with OSF Healthcare System regarding a 2021 breach affecting 53,907 patients. OSF agreed to pay $552,250 and implement a Corrective Action Plan addressing risk analysis, risk management, and notification failures.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jul 29, 2026
Filed
—
Corroborated · see linked filings
This record is the regulator's action, not a breach notice; its own dates cannot anchor compliance clocks. See the linked filings.
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitexinglockerbd_f8ace411af1e1abf2021-05-18 · +1898dVerified by operator
Regulatory filings (7) · sorted by filing gap
- Montana State AGbd_642aeb97e779372a2021-10-01 · +1762dVerified by operator
- Massachusetts State AGbd_b288deb4577e5ece2021-10-01 · +1762dVerified
- HHS OCRbd_bf20565c237987762021-10-01 · +1762dVerified by operator
- Illinois State AGbd_14299358f0ba63fe2021-01-01 · +2035dVerified by operator
Show 3 more filings ↓Show fewer ↑up to 2109d gap
- Illinois State AGbd_c91f7fe398e530012021-01-01 · +2035dVerified by operator
- Montana State AGbd_08d288f3d1ac951e2020-10-19 · +2109dCandidate
- HHS OCRbd_83807d832a08bc802020-10-19 · +2109dVerified
Filing propagation · 7 filings · 3 states
View merged incident ↗Pattern: first filing Oct 19 (MT), last Oct 1 (IL) — a 347-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- instrument + outcome
- amount as filed (USD)
- CFR provisions
- the breach it recites
- discovery date
- notification clock
The dates the agreement recites belong to the underlying breach, years earlier, and are kept as evidence of WHICH breach rather than as this record’s timeline.