| Model Number |
104208-600 |
| Medical Device Problem Code |
Imprecision (1307)
|
| Health Effect - Clinical Code |
Hyperglycemia (1905)
|
| Date of Event |
04/04/2025
|
|
Type of Reportable Event
|
Serious Injury
|
|
Event or Problem Description
|
|
On 05 april 2025,senseonics was made aware of an incident where user reported a high glucose event on 4-apr-2025 at 4:00 pm where user's sg was 80 mg/dl and bg was 547 mg/dl.After dms review, we confirmed that on (b)(6) 2025 at 4:00 pm where user's sg was 64 mg/dl and bg was not entered.After dms review, we confirmed that the user didn't receive a high glucose alert at the time of event because the sg never went above the alert level.The user didn't seek for medical treatment and didn't treat himself and waited for his glucose to go down naturally, as the authorized representative explained during the latest interaction that user was afraid of "crashing out" if user treated himself with insulin with his bg at that level.The user's hcp isn't aware of the event and was advised to follow up with the hcp for further medical guidance.
|
| |
|
Additional Manufacturer Narrative
|
|
The manufacturer is currently performing an investigation and will provide the results with the supplemental report.
|
| |
|
Additional Manufacturer Narrative
|
|
The user reported a high glucose event on apr-04-2025 at 4:00 pm where user's sg was 80 mg/dl and bg was 547 mg/dl.A review of the data management system (dms) revealed that sg was 64 mg/dl and no bg was entered at the reported time.In an associated case for the user's complaint about sensor inaccuracy, a review of the sensor in vivo data showed transient optical instability, which was most likely due to the system stabilizing following insertion on 01 april 2025.The observed optical instability likely contributed to the sensor inaccuracy.A review of the sensor data from the two weeks following the event confirmed good agreement between sg and bg values, indicating that the system had stabilized and was performing within expected parameters.B4.Date of this report 04 july 2025.G3.Date received by the manufacturer? 04 july 2025.H3.Device evaluated by manufacturer?yes.H6.Component code updated to 510.H6.Type of investigation updated to 4121.H6.Investigation findings updated to 3224.H6.Investigation conclusions updated to 4315.
|
| |
|
Search Alerts/Recalls
|