| Catalog Number |
SCCS1002 |
| Medical Device Problem Code |
Computer Operating System Problem (2898)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
07/22/2024
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
The investigation is still in progress.Once the investigation is complete a supplemental report will be filed.Udi format updated with available product information per gudid.H11: section a through f - the information provided by bd represents all the known information at this time.Despite good faith efforts to obtain additional information, the complainant / reporter was unable or unwilling to provide any further patient, product, or procedural details to bd.
|
| |
|
Event or Problem Description
|
|
It was reported that the biomed stated that the sensica urine output device was sent down to biomed with issues starting a session.It was determined that the device had a damaged load cell with pins potentially bent.The customer reported that the device was logging urine output incorrectly and taking a long time to connect to start once the urine bag was connected.They have asked for more technical clarification regarding this information.
|
| |
|
Additional Manufacturer Narrative
|
|
This mdr is being retracted as it is a cascading event of a record already submitted 1018233-2024-04830.
|
| |
|
Event or Problem Description
|
|
It was reported that the biomed stated that the sensica urine output device was sent down to biomed with issues starting a session.It was determined that the device had a damaged load cell with pins potentially bent.The customer reported that the device was logging urine output incorrectly and taking a long time to connect to start once the urine bag was connected.They have asked for more technical clarification regarding this information.
|
| |
|
Event or Problem Description
|
|
It was reported that the biomed stated that the sensica urine output device was sent down to biomed with issues starting a session.It was determined that the device had a damaged load cell with pins potentially bent.The customer reported that the device was logging urine output incorrectly and taking a long time to connect to start once the urine bag was connected.They have asked for more technical clarification regarding this information.
|
| |
|
Additional Manufacturer Narrative
|
|
This record is being submitted as a correction to the date received by manufacturer previously submitted.Upon further review, bd has determined that this mdr was reported in error as it was found to be a cascading failure of an event previously reported.Udi format updated with available product information per gudid.Correction: g.H11: section a through f - the information provided by bd represents all the known information at this time.Despite good faith efforts to obtain additional information, the complainant / reporter was unable or unwilling to provide any further patient, product, or procedural details to bd.
|
| |
|
Search Alerts/Recalls
|