Luscii - Notice history

Luscii Integrations experiencing degraded performance

Luscii Web App - Operational

100% - uptime
Feb 2026 · 99.81%Mar · 100.0%Apr · 100.0%
Feb 2026
Mar 2026
Apr 2026

Luscii Android App - Operational

100% - uptime
Feb 2026 · 100.0%Mar · 100.0%Apr · 100.0%
Feb 2026
Mar 2026
Apr 2026

Luscii iOS App - Operational

100% - uptime
Feb 2026 · 100.0%Mar · 100.0%Apr · 100.0%
Feb 2026
Mar 2026
Apr 2026

Luscii Integrations - Degraded performance

100% - uptime
Feb 2026 · 100.0%Mar · 99.91%Apr · 100.0%
Feb 2026
Mar 2026
Apr 2026

Luscii Metabase - Operational

Customer portal - Operational

100% - uptime
Feb 2026 · 100.0%Mar · 100.0%Apr · 100.0%
Feb 2026
Mar 2026
Apr 2026

Notice history

Apr 2026

HiX integration disabled due to security incident at ChipSoft
  • Update
    Update

    Update: We are in contact with ChipSoft and are awaiting clarity on timelines for ZorgPlatform to come back online. We will provide an update as soon as we know more.

  • Identified
    Identified

    Update: We have just received notice from ChipSoft that they are taking the entire ZorgPlatform offline. This means the HiX integration with Luscii is once again unavailable. Unfortunately, we do not have further details at this time. We are closely monitoring our own systems and will provide an update as soon as we know more.

  • Resolved
    Resolved

    Update: Good news: the HiX integration is back online. The integration between Luscii and HiX runs via ZorgPlatform. We have received confirmation from ChipSoft that ZorgPlatform has not been compromised and have decided to reactivate the integration.

    As shared earlier, there are a few points of attention following the reactivation:

    • Patients registered via the web version will need to be manually linked to HiX. Alerts created before the linking will not be forwarded retroactively. Only alerts created after the link has been established will appear on the orderlist.

    • Alerts for already connected patients that were processed in the web version during the downtime may still appear as open in HiX and will not be automatically updated. -

    • Measurements (such as blood pressure) taken during the downtime will not be synced to HiX retroactively.

    Steps to connect a patient in HiX:

    1. Open HiX

    2. Open the patient profile

    3. Go to 'Externe activiteitendefinities'

    4. Start a new 'Externe activiteitendefinitie' for the care path the patient needs

    5. A new window will open: if the patient already exists, connect the patient to the existing account. Matching is based on last name, date of birth, and email.

    For any questions, please reach out to support@luscii.com or support@luscii.co.uk. Thank you for your patience.

  • Update
    Update

    Update: Before re-enabling the HiX integration, we are awaiting a response from ChipSoft. At this point, we do not have sufficient insight into the situation on their end to responsibly bring the integration back online. Additionally, we will only restore the connection with new security certificates once we have received these from ChipSoft. These are the digital keys that secure the connection between Luscii and HiX. We would rather take extra time than take unnecessary risks with patient data. We will share a new update as soon as we know more.

    HiX is an electronic health record system used by many Dutch healthcare organisations. If your organisation does not use HiX, you can safely ignore this notification.

  • Update
    Update

    Update: An overview of the impact while the HiX integration is disabled:

    • Patients registered via the web version will need to be manually linked to HiX once the integration is restored. Alerts created before the linking will not be forwarded retroactively. Only alerts created after the link has been established will appear on the orderlist.

    • Alerts for already connected patients are currently not being forwarded to the orderlist. Because the integration is disabled, alerts are not being queued. Alerts that have already been processed in the web version may still appear as open in HiX and will not be automatically updated after the integration is re-enabled.

    • Measurements (such as blood pressure) are not being synced to HiX. No backlog will be processed after reactivation either.

    Luscii itself is functioning normally. Only the data transfer to HiX is temporarily interrupted. We understand that this is really inconvenient, but we do not want to take any unnecessary risks when it comes to data protection. We will provide an update as soon as there is more clarity on when the integration can be safely re-enabled.

  • Identified
    Identified

    Status: Identified

    Complication: Due to a security incident at ChipSoft (supplier of HiX), we have proactively disabled the Luscii–HiX integration. Luscii itself is not affected and all Luscii data is safe. Organisations using the HiX integration can temporarily switch to the web version of Luscii.

    Next steps: We disconnected database access last night immediately after publication and took additional protective measures this morning. We are closely monitoring developments at ChipSoft and will provide an update as soon as more information becomes available.

Mar 2026

Priority 3: Alerts not being forwarded to HiX
  • Resolved
    Resolved

    We are fully caught up again. All alerts have been forwarded to HiX.

  • Monitoring
    Monitoring

    The issue has been resolved. We are now reviewing the alerts that were not forwarded yet and will re-submit them.

    Alerts already completed in the web version will be marked as completed in HiX. Any remaining open alerts will also appear as open in the HiX orderlist.

  • Identified
    Identified

    We see that alerts have not been forwarded to HiX since yesterday afternoon. We found the issue and are working on a fix. For now, we recommend using Luscii Web and not working from the HiX orderlist. This issue does not affect other integrations, such as EPIC.

    Questions? Contact support@luscii.com.

  • Monitoring
    Monitoring

    Situation: Alerts generated from measurements taken between 14:45 and 16:45 CET may have been delivered with a delay. Everything is stable now.

    Complication: This may make it appear that some alerts arrived later than expected.

    Next steps: No action is required. We will continue monitoring. When reviewing alerts from this time window, please consider possible delivery delays.

    Questions? Contact support@luscii.com.

Feb 2026

Priority 1: “Overdue” alerts are being generated significantly less often
  • Resolved
    Resolved

    This incident has been resolved.

    The Post-Mortem will be shared via this page.

  • Monitoring
    Monitoring

    We have rolled back to the previous stable version in the production environment and are closely monitoring the situation. Today’s “Overdue” alerts are being generated correctly again.

    Unfortunately, we cannot retroactively generate the alerts that were missed on Wednesday afternoon and Thursday.

    In addition, we will proactively reach out to organizations with more than 100 missed alerts: today, over the weekend, and no later than Monday.

    If your organization has not received an email by Monday evening, you can assume there were fewer than 100 missed alerts. You are, of course, still welcome to request the data manually via support.

    We will continue to monitor the situation closely.

  • Identified
    Identified

    We are working on a solution, which is currently being thoroughly tested.

    Missing “Overdue” alerts can be requested via support@luscii.com. Please specify which program(s) you would like the data for.

  • Investigating
    Investigating

    Situation

    • We’ve observed that “Overdue” type of alerts have been generated significantly less frequently than usual since Thursday, February 5, 2026.

    Impact

    • As a result, care teams may receive fewer alerts when patients do not submit required actions, which can affect follow-up.

    • That’s why this has Priority 1.

    Next steps

    • Luscii’s developers are actively investigating the root cause.

    For questions: support@luscii.co.uk or support@luscii.com

Feb 2026 to Apr 2026

Next