|
Reportedly, during lbbot case in hospital (b)(6) in (b)(6), v6-v1 could never be measured, as v1 was always negative.Also, there was v6wrpt measurement since the very placement of the leads, even before the physicians started to operate.After contacting and discusing with the spanish clinical team, already experienced in the use of lbbot in the clinical phase, the hypothesis was that qrs from lead iii was so sharp that it was being detected as a spike.Then, after changing spike detection channel to either i or v1, the spike detection and the measurements stopped.
|
|
Analysis synthesis:
review of the software analysis confirmed the reported behavior during the lbbot procedure, with spontaneous qrs complexes incorrectly detected as pacing spikes, leading to inappropriate measurements.The investigation showed that a specific qrs morphology on lead iii (narrow, high-amplitude qrs) generated sufficient high-frequency content to exceed the spike detection threshold.As a result, the software classified these signals as spikes, although no actual pacing spikes were present.This behavior is consistent with the current system specifications.The issue was attributed to the software spike detection algorithm and not to any smart ecg hardware malfunction.No patient safety risk or cybersecurity concern was identified during the investigation.This case will be retained for trending and monitoring purposes.
|