A nurse manager once told me about a shift where a critical lab result got relayed through four different people before reaching the attending physician, and by the time it did, nobody could say for certain who had actually seen it first. The result was fine. The patient was fine. But the near-miss shook the whole floor, because it revealed something uncomfortable: their communication system had no memory. Nobody could trace who knew what, when.
That gap between information moving and information being accountable turns out to matter far beyond hospitals, too.
Accountability isn’t the same thing as speed
Healthcare communication systems get judged, usually, on how fast a message travels. Did the nurse get the alert in time. Did the on-call physician respond quickly. Speed matters, obviously. But speed without a record of who saw what, and when, creates a system that feels responsive while actually being untraceable, which is a dangerous combination when something goes wrong and someone needs to reconstruct exactly what happened.
This is the argument for building or choosing a HIPAA-compliant messaging app with accountability baked into the architecture, not added as an afterthought. Read receipts, timestamped delivery, audit trails that show exactly which staff member acknowledged a critical result and at what time. A hospital I worked with rolled out exactly this kind of system after that near-miss, and the change wasn’t really about speed at all. It was about closing the gap between “the message was sent” and “someone is accountable for having received it.” Those are very different guarantees, and most consumer-grade texting tools only offer the first one.
The staff pushback was minimal, which surprised the administration. Turns out clinicians want the accountability too. Nobody wants to be the unnamed link in a chain when a lab result gets missed.
A completely different field runs into the same design question
Video game designers, of all people, have spent the last decade wrestling with something structurally similar, even if the stakes are nowhere near comparable.
Games where choices matter live or die on whether the player’s decisions actually produce traceable consequences later in the story. Early branching narrative games often faked this. A choice would appear meaningful in the moment, two dialogue options, a dramatic pause, and then the story would quietly funnel back to the same outcome regardless of what the player picked. Players noticed. They always notice. A choice that doesn’t change anything downstream isn’t really a choice. It’s decoration.
The games that get real loyalty from players, the ones people replay specifically to see what happens differently, are built with actual state tracking under the hood. The system remembers what you did in chapter two and lets it quietly reshape a conversation in chapter nine. That’s a lot of invisible engineering for something a player might not consciously register. But they feel its absence immediately when it’s missing, the same way that nurse manager’s team felt the absence of a traceable record the moment something almost went wrong.
Why invisible structure is the hardest thing to sell internally
Here’s the problem both fields share: nobody budgets enthusiastically for the part of the system that just remembers things correctly. It doesn’t demo well. A flashy new alert sound gets applause in a product meeting. A properly architected audit log gets a shrug, right up until it’s the only thing standing between an organization and a lawsuit, or between a game studio and a wave of one-star reviews complaining that choices didn’t matter.
I’ve sat in meetings where this exact tension played out, engineering time getting pulled from state-tracking infrastructure toward a more visible feature, because the visible feature was easier to justify to a stakeholder who wasn’t going to see the consequences until much later.
What both fields eventually learn the hard way
The hospital that experienced the near-miss didn’t overhaul their communication system because a vendor pitched them well. They did it because the alternative, another incident with no clear record of who saw what, was unacceptable once they’d seen how close the first one came to real harm. Game studios learn a milder version of the same lesson through player backlash instead of malpractice risk, but the underlying mechanism is identical. Systems that don’t remember, that don’t hold anyone or anything accountable for what happened earlier, eventually get caught out by the exact scenario they were never built to handle.
The through-line here isn’t really about hospitals or games at all. It’s about the difference between a system that moves information and one that actually stands behind it, and how rarely that distinction gets attention until the moment it’s needed most.
This content is provided for informational purposes only and is not a substitute for professional advice. AFP editorial staff were not involved in the creation of this content.
Share
