| Model Number |
AVALON FM50 FETAL MONITOR |
| Medical Device Problem Code |
Unable to Obtain Readings (1516)
|
| Health Effect - Clinical Codes |
Encephalopathy (1833); Hypoxia in Utero (2210)
|
| Date of Event |
05/14/2025
|
|
Type of Reportable Event
|
Death
|
|
Event or Problem Description
|
|
Philips received a complaint on an avalon fm50 fetal monitor indicating that the fetal heart rate (fhr) was not able to be measured and the baby passed away after birth.The mother at 37 weeks plus 4 days gestation presented with an intermittent category 2 tracing (neither reassuring nor non-reassuring trace) with improvement over 24 hours with position changes.The patient then had a quick change to a category 3 tracing (prolonged decelerations) and was transferred emergently to the or, where the fetal heart rate improved so a vacuum-assisted delivery was attempted, which was unsuccessful, and the mother was reluctant to go to c-section.During these attempts the fhr was lost for more than 8 minutes so an emergent c-section was performed.The baby was cyanotic and unresponsive and required resuscitation.Emergent intubation and transfer to nicu and active cooling was attempted.Care was subsequently withdrawn and death was due to severe hypoxic-ischemic encephalopathy.The maternal heart rate (mhr) was monitored at the time, and it was thought because the mhr and fhr were being picked up interchangeably, there was a delay in care, which affected the outcome.Based on this information, the customer believes the device may have contributed to the reported event.A philips technical consultant (tc) went to the customer site, and was unable to duplicate the issue that the audible heart rate was half the rate that showed on the monitor display.The tc noted that the clinicians had difficulty discerning the maternal and fetal hr.
|
| |
|
Additional Manufacturer Narrative
|
|
Philips is in the process of obtaining additional information concerning this event and the complaint is still under investigation.A final report will be submitted once the investigation is complete.
|
| |
|
Additional Manufacturer Narrative
|
|
The philips technical consultant (tc) went to the customer site and performed scans of the network connectivity.Philips national service support (nss) reviewed the data obtained by the tc.There was an issue with the network signal in the affected area, which was determined to be related to a non-philips product in the customer environment.The installation was completed without issues originally; the non-philips product in the customer environment may have changed causing the technical issue.Fm monitor channels were adjusted by the tc to follow guidelines in the service manual using data from the rf environment collected from the fm scans.This resolved the technical issue.Double counting was part of the main complaint and it was noted by the nss that philips does outline mitigations for this in the instructions for use (ifu) for the product.Based on the information available and the testing conducted we were unable to replicate initial reported problem.However, it was noted that a non-philips product in the customer environment may have changed causing the technical issue.The device was operational after adjusting the fm monitor channels.The investigation concludes that no further action is required at this time.If additional information is received the complaint file will be reopened.
|
| |
|
Search Alerts/Recalls
|