Elgon Information Systems
bd_54176d80952b292b · schema v1 · pii pii-v2
Full breach record for Elgon Information Systems →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 with Elgon Information Systems for $80,000 regarding a 2023 ransomware attack. Elgon, a business associate providing EMR services, failed to conduct a required risk analysis. The attack affected approximately 31,248 individuals, exposing PHI including demographic and clinical data. Elgon agreed to a corrective action plan including updated risk analysis, workforce training, and policy revisions.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jan 7, 2025
Filed
—
Corroborated · see linked filings
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.
Linked disclosures
Why this link?Regulatory filings (1) · sorted by filing gap
- HHS OCRbd_0e9c9a47103d985e2023-06-02 · +585dCandidate
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Jun 2 (MA), last Jan 7 — a 585-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.