Skip to content
What night shifts on a cardiology ward taught me about alert fatigue
experience2 min read378 viewsAug 28, 2026

What night shifts on a cardiology ward taught me about alert fatigue

Hannah Weiss@hannahweiss

August 28, 2026 · 2 min read

#1 in Vitals and Variables

378 views7 comments

Before I became an engineer I was a nurse for six years, the last three on a cardiology ward. I want to describe one thing from that time, because I see the same pattern now in software: in dashboards, in on-call rotations, and in the apps we build for clinicians.

On a night shift you hear alarms all the time. The monitor alarms when a patient turns over and an electrode slips. It alarms when the saturation probe loses contact for a few seconds. Infusion pumps alarm when a bag is nearly empty, which is useful, and then again with the same sound for things that are not urgent at all. After some weeks your brain does something you do not decide: it starts to filter. You hear the alarm, you know which bed, you know it is "probably the probe again", and you finish what you are doing first.

Most of the time this is correct, and exactly that is the danger. The one alarm that matters sounds the same as the forty that did not. The literature calls it alarm fatigue, and studies on monitored wards keep finding that most alarms are not clinically actionable. I did not need a study. I could feel it in my shoulders.

What helped on the ward was never "try harder to pay attention". It was changing the system:

  • thresholds adjusted per patient instead of the default for everyone
  • short delays for conditions that resolve by themselves within seconds
  • changing electrodes every day, so the false alarms went down
  • different sounds and escalation for the things that really cannot wait

When I now see a Slack channel with three hundred automated messages per day, or a clinical app with a red warning banner on every second screen, I recognise it immediately. If everything alarms, nothing alarms. People are not lazy when they ignore your alerts. They are adapting, the same way I did, and the adaptation is rational.

So my rule, for clinical software and for monitoring: every alert must be actionable, must go to someone who can act on it, and must be rare enough that it still surprises. If an alert fires and the right response is "ignore it", delete the alert or fix the cause. There is no third option that works for long.

Written by

Hannah Weiss

Clinical informatics engineer in Berlin. I build integrations between hospital systems: HL7v2, FHIR, and a lot of patience. Formerly a nurse, which explains my opinions about alert fatigue.

Get the best of #vitals_and_variables weekly

One email each Monday with the most useful posts. No spam; unsubscribe in one click.

Comments

7

Sign in to join the conversation.

Sign in to comment
Marcus Johnson@marcus_oncall#2 in Vitals and Variables
this is the best description of on-call i have ever read and its about nurses. we had ~300 alerts a day, the team had the channel muted. we cut it down to 9 alerts that each have a runbook and someone actually gets woken up for them. time to acknowledge went from "whenever" to minutes
0 net votes
Hannah Weiss@hannahweiss#1 in Vitals and Variables
Nine alerts with a runbook each is exactly the ward version of changing the electrodes every day. Boring, and it works.
1 net votes
Siobhan O'Rourke@siobhan_tests#3 in Vitals and Variables
same with test suites. if CI is red every day people stop reading it. one red that means something is worth ten that dont
0 net votes
Mariana Costa@mari_costa#3 in Vitals and Variables
From design side we see this with warning banners. We made a research in our checkout and people closed the yellow banner without reading in less than one second. Now we use it only for payment problems. Thank you for this text, I will share with my team
0 net votes
Fatima Al-Sayed@fatima_appsec#8 in Vitals and Variables
Security tooling is the worst offender. A SAST scan with 2,000 "medium" findings is not a security program, it's a noise generator. Triage once, suppress with a written justification, and only page on what is actually exploitable.
1 net votes
Rachel Kim@rachelkim#8 in Vitals and Variables
Saving this for the next time someone asks for "just one more notification" in a spec. If everything alarms, nothing alarms.
2 net votes
Kevin Tran@kevtran_dev#3 in Vitals and Variables
i worked in a restaurant kitchen for years and the ticket printer was exactly this lol. by friday night you literally dont hear it anymore. didnt know there was a name for it
1 net votes