The customer reported complaint for the autopulse platform stopped compressions and displayed a user advisory (ua) 17 (max motor on time exceeded during active operation) error message was confirmed during archive review and not during initial functional testing.There were no device deficiencies found during evaluation of the returned console that could have caused or contributed to the reported complaint.Visual inspection was performed and found damaged load plate cover on the autopulse platform, unrelated to the reported complaint.This type of damage can occur likely due to mishandling.Review of the archive data indicated user advisory (ua) 17 errors occurred on the reported event date, thus confirming customer complaint.Base on the archive, the autopulse platform performed 256 compressions on the medium size patient.The device has stopped compressing due to (ua) 17.The user pressed restart to clear the fault and the autopulse platform was used again and stopped three more time due to (ua) 17.The user advisory (ua) 17 error message alerts the user that the drive motor did not reach the target compression depth within specification when used on a medium/large size stiff patient or when the battery being used has a low voltage or the lifeband is twisted.The reason the autopulse platform stops after a few compressions, it is trying to build up to the 20% compression depth and cannot do it in the specific time frame but did not have enough power to achieve this compression rate within 0.38 seconds.The lifeband was not returned for evaluation.The brake gap inspection was performed and verified the gap was within the specification.The platform was further tested with large resuscitation testing fixture, (lrtf) equivalent to the 250-pound patient and passed all functional testing criteria and met all required specifications.Historical complaints were reviewed for service information related to the reported complaint and there was one similar complaint reported for autopulse platform with serial number (b)(4).Reported on (b)(6) 2018.Defective cable was replaced to remedy the issue.
|