|
H11 updated: the customer asked if it is possible to update a record in mosaiq, following a treatment where mosaiq indicates that the gantry did not start at 0.The investigation was completed by conducting a thorough evaluation of the products and the reported information.This case meets the exception scenario: communication error (any machine) including citrix.A communication error occurs and the treatment delivery is or is not recorded.Incident/problem reporting evaluation: the prescribed treatment is delivered, as intended; however, due to the communication error the linac may or may not transmit the treatment data to the sequencer application for recording.Review of the record and user notifications make clear to the user that the provided treatment is not recorded.The user will recognize the incorrect recording and either contact elekta product support for assistance or correct the errant recording.As the treatment is delivered as prescribed, no serious injury nor death occurs, nor would either be foreseeable if the event were to recur.The machine and audit logs from 12 march 2026 show that field 1.1 (arc) was selected for treatment around 09:32:07.When a field containing multiple control points (e.G.Vmat) is sent to the treatment machine, only the first control point is verified by mosaiq.The mosaiq sequencer confirmed that all settings including the gantry position had gone into tolerance before beam on, allowing the machine to enter a ready state.The audit log shows approximately a 7 second gap between 9:32:40 and 9:32:47 when all background processing stopped.The cause of the lapse in processing is unknown.Currently, mosaiq is only able to detect that a lapse in processing occurred and alert/record with the error but cannot say definitively what is causing the lapse.It was during this 7 second period that beam on began (09:32:43).This indicates that there was a delay or latency in capturing actual values at the initial beam on and is the reason a start gantry position of 354.3 was recorded.This is only a recording issue.With vmat the gantry is typically moving from the start, so if the beam on was not reported or detected immediately in mosaiq, the gantry had already moved away from its starting point in the initial point recorded.The logs confirm that the gantry started at 359.9 and the prescribed 285.5 mu to field 1.1 (arc) was fully delivered.At the end of treatment, the user received an application communications time out error, and completed the treatment recording via the abnormal termination window presented in mosaiq.It is not possible to amend the gantry position of the historic record through the user interface.There was no mistreatment.Mosaiq worked as intended.
|