{"id":3365,"date":"2026-10-26T16:45:00","date_gmt":"2026-10-26T16:45:00","guid":{"rendered":"https:\/\/www.bestheartsurgery.com\/blog\/?p=3365"},"modified":"2026-10-26T16:45:00","modified_gmt":"2026-10-26T16:45:00","slug":"chatops-night-team-cardiac-story","status":"publish","type":"post","link":"https:\/\/www.bestheartsurgery.com\/blog\/chatops-night-team-cardiac-story\/","title":{"rendered":"ChatOps on a Cardiac Ward: A Night Team’s Story"},"content":{"rendered":"

Handoffs decide outcomes on a cardiac ward. Day shift hands the monitor alarms, the pending echocardiograms and the anxious families to a night team that was not in the room when any of it started. At one mid-sized heart hospital \u2014 the names in this story are invented, the pattern is not \u2014 those handoffs used to travel by sticky note, private message and a group mailbox nobody owned. The clinical systems team, four people with day jobs elsewhere in the building, decided to move that traffic into shared chat instead, adopting ChatOps<\/strong>: a shared channel carrying the operational load, where a bot announces events, permitted commands act, and the whole trail \u2014 action, outcome, discussion \u2014 remains visible, permissioned and logged. Their touchstone document was the Ops Atlas entry on ChatOps<\/a>, which they printed and taped inside a cupboard door.<\/p>\n

The Night a Page Went to an Empty Desk<\/h2>\n

The incident that forced the change was ordinary, which is what made it frightening. A bed-management alert went out at 02:14 as a direct message to the one coordinator who always answered \u2014 except that week she was on leave, and the message sat unread beside a holiday autoreply. Nobody else knew the alert existed, because private channels are invisible by design. The patient was fine; the transfer was delayed by ninety minutes and nobody could afterwards explain why. In the review, the team wrote one sentence on the whiteboard and never erased it: work that only one person can see is work that only one person can do.<\/p>\n

Three ChatOps Surfaces, One Channel<\/h2>\n

What the team built followed the shape the reference describes, and it helped to name the parts explicitly:<\/p>\n