This report is being submitted retrospectively as part of internal review.The initial investigation was performed on the user synced glucose data on data management system (dms), which is an eversense cloud platform.Based on the dms analysis, the system was not in use at the time of the event.A review of the sensor alert history revealed that the sensor was already retired as the system asserted an early sensor replacement alert on (b)(6) 2023.The sensor was replaced on (b)(6) 2023.Due to early sensor retirement, the rma was issued for return of sensor for further investigation.Investigation of the returned sensor did not reveal any malfunction as it passed all the functional tests.This may occur in some instances where the failure mode that presents itself in the body cannot be reproduced in the lab.A further review of the glucose plot revealed that on (b)(6) 2023, there were 4 consecutive suspicious calibrations which led to sensor suspend per design.This feature allows the system to re-evaluate its performance and re-start in initialization phase, while the sensor glucose is blinded to the user for 6 hours.After the system was out of the sensor suspend phase, it restarted in initialization phase and on the (b)(6) 2023, there were another 4 consecutive suspicious calibrations leading to another sensor suspend.As per design, if there are two sensor suspend alerts asserted within 14 days, then the system will retire the sensor and assert a sensor replacement alert.A review of the in-vivo glucose data revealed that the historical calibration entries were not accurate i.E, the customer was entering the sensor glucose (sg) readings for calibration.Entering anything other than true fingerstick blood glucose (bg) reading would disrupt the normal functioning of the sensor and cause significant inaccuracies.
|