Sometimes the alarm limits are set incorrectly by the RT or aren’t forgiving enough to allow some motion. When you see an entire ward of nurses totally ignoring alarms it’s a management failure. Either there aren’t enough nurses available to manage the issue or there aren’t enough technicians to properly configure the equipment for each patient. If someone dies because of that then it’s ultimately the hospital’s fault.

I will not say it was a management failure because I don't know if management could have done anything about it. Given the total indifference of the nurses I strongly suspect they couldn't do anything.

Alarms with incessant false positives are inherently dangerous. Sure, there's some threshold of false positives, under which we should still expect people to investigate all alarms. But above that threshold, how can we continue to blame the people involved? The hardware is at fault.

Seriously, what would motivate you to make a comment like that? Do you think medical device engineers and clinicians are unaware of the false alarm issue and haven't already tried a variety of improvements? There is an inherent trade-off between false alarms and missing a real problem. And devices need to be not only accurate but also affordable, durable, and cost effective. It's not easy to get this right.

Three times as many leads would be pretty annoying, though.

I remember an accident report. It was about a container ship which had a bad flooding incident in their engineering spaces. One thing the report pointed out that the engineers had ways to fight the flooding, but they were not doing them because they were playing whack-a-mole with all the alarms caused by the flood. If i recall correctly the engineers kept ignoring the waist deep and rising water and prioritised silencing the alarms. (And not because they were stupid, but just because the many independent blaring alarms task-saturated them.)

That's common in computer monitoring systems, at my last job when we had a serious outage, we'd get dozens of pager alerts, it was hard to figure out the root cause because so many alerts fired that were caused by the root cause. I.e. like if the root cause was a root volume was out of disk space, the "unable to log in" alert was superfluous and not helpful. Eventually we moved to a better system that had a betrer sense of hierarchy for alerts as well as a way to easily silence them.