**Updated as of March 4, 2024. We will provide updates as more information becomes available.**

UPDATE 3/04/2024 – 10 AM Pacific

This is an emerging issue, and the full extent of the issue is not yet known by Alegeus or CHC. As of right now, there is no confirmed breach or disclosure of information – all we know is what has been provided on the Optum website, as well as what was reported in the K-8 filing (a new SEC reporting requirement for public companies impacted by a security incident).

Participants are experiencing a delay in receiving reimbursement checks. Our team is working on an alternative and secure solution to deliver reimbursement checks. Direct deposit disbursements have not been impacted.

UnitedHealthcare’s Information on the Change Healthcare Cyber Response

UPDATE 2/28/2024 – 5 PM Pacific

On Friday, February 23, 2024, Navia Benefit Solutions, Inc.’s (also the parent company of TRI-AD Actuaries, LLC) privacy officer was alerted to a “Cyber Security Issue” at Change Healthcare (CHC), a print partner of Alegeus responsible for printing reimbursement checks and other documents. CHC is part of Optum and is owned by UnitedHealth Group. Alegeus is the underlying reimbursement recordkeeping software utilized by TRI-AD. As a result of the “cyber security issue” (as described by CHC), they experienced a network interruption. As a result, no checks have been processed since on or about Monday, February 19, 2024. Alegeus is neither sending data to nor receiving data from CHC. You can view the latest status updates from Optum Solutions on their incident reports page.

While no breach or disclosure has been reported, and CHC has characterized this as a cyber security “issue” versus an “incident,” we are providing this information to keep you informed. We continue to monitor the issue closely and are evaluating various options to pay participants as quickly as possible, including printing checks in-house.

We apologize for the inconvenience. Thank you for your patience and understanding as we work to have this issue resolved.