OSF HEALTHCARE SYSTEM
bd_7fbc6210e9c1f4d5 · schema v1 · pii pii-v1
Full breach record for OSF HEALTHCARE SYSTEM →Regulator'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.
P pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jul 29, 2026
Filed
—
No linked breach filing · watching
Compliance clocks stay unassessable until a breach filing is linked. This record is the regulator's action, not a breach notice. Dashed segments fill in automatically when corroboration arrives.
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.