The investigation was completed by conducting a thorough evaluation of the product and the reported information.The customer sent two fields with mu prescription of 130.0 and 23.0 respectively to the machine for treatment.The fields were treated but mosaiq recorded 260.0mu for first field and 0mu for the second field.The customer said that there was no error or interruption during the treatment.Based on the audit logs, mosaiq ran into an error while it was processing dicom beam records from truebeam.The 'loadbeamhistory' shows that there were two beam records for the first field and nothing for second field which explains why the first field was recorded twice.There was also a failure in the 'flushsegmentdatalist' which shows the error in the logs which contributed to the recording issue.This was a recording issue and did not reflect the real treatment since the dicom beam records show that all fields were treated fully and correctly.There was no patient mistreatment.It has not been possible to establish the root cause.This recording issue is detectable post treatment and does not affect or lead to patient mistreatment.Mosaiq detects this issue of the monitor units being delivered less than or more than the prescribed mu at the end of the session by displaying a message.If this message is ignored by the user, the next time the patient is treated, the treatment chart will display in 'red' indicating to the user that something mismatched as opposed to displaying black for a completed field.The 'red' will not only display on the session from the previous day but also for the future sessions until the chart is corrected to no longer having more or less monitor units.Mosaiq has multiple ways to mitigate a difference in the monitored units being received versus expected.If the initial message is received, the customer needs to verify the amount delivered via the dicom beam record or ask elekta for assistance.If the dicom beam record does not exist, the customer must request assistance from varian.
|