(b)(6) reported on (b)(6) 2018 that their pu-621ra (sn: (b)(6)) was alarming for tachycardia, but the patient's hr was not that fast based on nurse checking.Service requested: troubleshooting.The customer sent a text with a photo of the patient's waves and the t-waves were peaked.Clinical application specialist kim bates recommended that the customer monitor another lead for trace 1 instead of lead ii.The customer changed trace 1 to lead i and this resolved the issue.The patient's hr displayed dropped from 200 to 115, which was correct according to the hospital staff.Clinical application specialist then explained to the customer that if the t-wave is peaked, this can be recognized as another qrs complex, resulting in double-counting.Investigation result(s): peaked t-waves can be caused by the patient if they are: hyperkalemic; have pericarditis; taking certain medications (such as digoxin, quinide, overdosing on medication); cardiac issues; ecg lead misplacement; and etcetera.In this case, the customer had chosen the incorrect lead settings for monitoring their patient.The issue was resolved through the customer choosing a different lead for trace 1 that allowed proper monitoring of the patient.The device serial number history shows that there have been no further/previously reported issues nor servicing for this device double counting.The root cause of the issue has been identified to be user error/user education as the incorrect lead settings had been chosen to monitor the patient.Clinical application specialist educated the customer on how to get a more accurate reading and how double counting can result from peaked t-waves.Trending analysis found two similarly reported issues regarding pu-621ra and double counting hr.All three of the reported issues were at different facilities and resolved through adjusting lead configuration.There is no suspected adverse trend nor indication of design deficiency.Investigation by qe has been completed as the root cause of the issue has been identified and investigational information within the record documents that the issue was resolved through customer choosing a proper lead configuration to monitor their patient.Corrected information: g4.Date received by manufacturer: should be 05/31/2018 not 06/29/2018 as listed on mdr initial report.
|