The customer experienced a hyperglycemic event and subsequently administered insulin.However, they then encountered a hypoglycemic episode leading to a serious adverse event where ambulance was called (complaintrec-.43869 / bfarm ref : (b)(4)) the initial investigation was performed on the user synced glucose data on data management system (dms), which is a cloud platform for eversense systems.Based on the initial analysis, the customer reported sensor glucose (sg) value of 341 mg/dl was confirmed.No blood glucose (bg) value was reported or was entered into the system.The customer received multiple high glucose alerts as the sg value crossed above the set high glucose alert threshold.A review of the overall system performance suggested a deviation from the typical behavior.Due to this deviation and to determine the root cause, a return material authorization (rma) was issued for sensor return and replacement.The returned sensor was investigated and found to be performing as expected 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.However, a further analysis of the in-vivo glucose data revealed noise in the glucose channel for days until the hypoglycemic event.The potential root cause of the noise could be due to transient issue with sensor electronics, for example the led behavior at the time of incident, or the in-vivo state of sensor hydrogel (chemical component of the sensor), which cannot be reproduced in the laboratory.As part of resolution, the customer was inserted with a new sensor to continue using eversense e3 continuous glucose monitoring (cgm) system.B4.Date of this report 26 april 2024 g3 date received by the manufacturer ?12 feb 2024 h3.Device evaluated by manufacturer? yes h6.Type of investigation updated to 10 h6.Investigation findings updated to 4203 h6.Investigation conclusions updated to 4307.
|