Luscii - Status Page

For a number of care pathways, we saw that overdue alerts were not being processed automatically. This concerns a limited set of care pathways and is not the broader delay from last Thursday.

We have now found the underlying cause: during an earlier change, the correct setting was not carried over properly for a number of care pathways, which is why automatic processing was not working there. This has now been structurally fixed for the affected care pathways.

The open overdue alerts will unfortunately need to be closed manually this one time, the alerts themselves can simply be processed. We will continue to monitor this closely. We apologise for the inconvenience.

Update: The automatic processing of overdue alerts unfortunately experienced problems again today. This has now been fixed and we are monitoring the situation. We will continue to keep an eye on it over the weekend.

Unfortunately, some overdue alerts that should have been processed automatically were not, these will need to be closed manually by caregivers. We apologise for this inconvenience.

The issue has been resolved. A large volume of background tasks this morning caused a delay in processing. This was most noticeable in the forwarding of alerts to the EPD (HiX), and also affected (automatic) workflows and additional measurements. Everything has now been fully processed and the alerts in HiX have caught up, no data has been lost. We have scaled up capacity and moved the tasks in question so they no longer hold up regular processing. We are also taking steps to ensure this does not happen again. Thank you for your patience.

This message only applies to British customers using the SystmOne integration.

Update: In addition to the previously reported duplicate entries, we now see that for a number of organisations the processing of records to SystmOne has stopped entirely. As a result, new records for these organisations are temporarily not reaching SystmOne. Affected organisations are being contacted directly.

The cause is known: in some cases our SystmOne integration does not receive a response back when writing a record, causing processing to hang. Restarting the gateway PC running the Luscii service resumes processing. No records are lost, any pending records are processed correctly after the restart.

We are working on a permanent fix that improves the robustness of the SystmOne integration. This will be rolled out as a new version on the gateway PCs. We will provide a new update as soon as we have more information.

Update: we are in touch with the NHS and TPP SystmOne to identify the cause of this issue. The main cause is that Luscii is not receiving responses from SystmOne when writing to the patient record. Because no response is received Luscii attempts to retry the writing of the record resulting in a duplicate entry.