| Model Number |
104208-600 |
| Medical Device Problem Code |
Imprecision (1307)
|
| Health Effect - Clinical Code |
Hypoglycemia (1912)
|
| Date of Event |
01/09/2025
|
|
Type of Reportable Event
|
Serious Injury
|
|
Additional Manufacturer Narrative
|
|
The manufacturer is currently performing an investigation and will provide the results with the supplemental report.
|
| |
|
Event or Problem Description
|
|
Senseonics was made aware of an incident where user reported a low glucose event on (b)(6) 2025 between 02:00 am to 04:00 pm where user's sg was 57 mg/dl and bg was 120 mg/dl.Since user couldn't provide a specific date of event, the following information was confirmed in dms using the information value provided, where sg was 57 mg/dl confirmed on (b)(6)2025 at 2:35 am and bg 120 mg/dl wasn't entered into the system.The user received the first low glucose alert at 2:10 am, when the sg was at 58 mg/dl, and kept receiving alerts every 15 minutes.The user didn't seek for medical treatment and resolved the event because he had no symptoms of a low glucose event.The user was advised to follow up with the hcp for further medical guidance.
|
| |
|
Additional Manufacturer Narrative
|
|
The user reported a low glucose event on (b)(6) 2025 between 2:00 am - 4:00 am where user's sg was 57 mg/dl and bg was 120 mg/dl.A review of the data management system (dms) data revealed that on (b)(6) 2025 at 2:35 am user's sg was 57 mg/dl and bg was not entered.A review of the alert history revealed that the user received multiple low glucose alerts since 2:10 am as user's sg value was below the threshold of 60 mg/dl.The user did not seek medical treatment and believed that they were not having a low glucose event.The user's hcp was not aware of the event and was advised to follow up with their hcp for medical guidance.An case (b)(4) was created to address the sensor inaccuracies related issues, inclusive of the hypoglycemia event.A review of the in-vivo data revealed transient optical instability as the system adjusted from implant on the (b)(6) 2024.This most likely contributed to the sg/bg mismatch at the time of the low glucose event.A review of 2 weeks' worth data post escalation ((b)(6) 2025) was analyzed, and the system had stabilized with good agreement between bg/sg.The user did not report any additional hypoglycemia/inaccuracies related issues and is currently using the same system, by closure of this complaint.B4.Date of this report (b)(6) 2025.G3.Date received by the manufacturer? 08 april 2025.H3.Device evaluated by manufacturer?yes.H6.Health effect -impact code updated to 4613.H6.Component code updated to 510.H6.Investigation findings updated to 114.H6.Investigation conclusions updated to 4315.
|
| |
|
Search Alerts/Recalls
|