The Verification Gap: Why Medication Errors Survive Good Software

For as long as I've been in senior living, the industry's response to medication errors has followed a familiar pattern.

An error happens. Leadership responds. A root cause gets identified, usually something in the documentation workflow. A new requirement gets added. More fields, more mandatory sign-offs, more checkboxes before the pass can be marked complete. The assumption underneath all of it is that if we document more carefully, errors will happen less often.

I understand why that assumption took hold. It feels logical. Documentation is visible, auditable, and improvable. And the regulatory environment rewards it. State surveyors look at records. Accreditation bodies review process documentation. So the industry built better and better systems for capturing what was supposed to happen.

What it didn't build was a reliable way to confirm that it did.

That distinction, between recording intent and verifying outcome, is where I think the industry has been looking in the wrong direction for a long time. And it's why errors survive in communities with excellent software, well-trained teams, and thorough documentation. The process looks right on paper because the paper is the only thing anyone has been measuring.

When we started working with pilot communities, one of the things that stood out immediately had nothing to do with error rates or compliance metrics. It was how the med techs felt during the pass.

They were faster. Significantly faster. And not because we asked them to rush. Because the friction was gone. No manual data entry. No stopping to search for a resident's file or pull up an order. The system already knows. A bubble pack goes into the scanner, the resident's active order is matched automatically, the dose is confirmed in real time, and the pass moves forward. What used to require several manual steps now happens in the background without interrupting anyone.

That matters for a reason that goes beyond convenience. A medication pass happens under real time pressure, often with a cart that's running behind, often with a team that's one person short. Every manual step is a moment where cognitive load increases and the conditions for error improve. Removing that friction doesn't just make the pass faster. It makes it structurally safer.

The other thing that came into focus through the pilot work was how much variation exists across communities in how the medication pass actually gets done. Not in the EMAR, which tends to be consistent. In the physical workflow. The sequence of steps a med tech follows, the habit patterns that develop over months of doing the same pass, the informal adaptations that accumulate when no one is standardizing the physical process. Some of that variation is harmless. Some of it creates exactly the conditions where an error can slip through unnoticed.

A real verification layer doesn't just catch errors in the moment. It brings the same process to every community, every shift, every med tech regardless of tenure. A first-week hire and an eleven-year veteran run through the same verification steps in the same order every time. That consistency is its own form of protection, and it's something no amount of documentation software can provide, because documentation captures what people record, not what people do.

This is what I mean when I talk about intelligent care verification as a category. Not a smarter screen. Not a more thorough checklist. A layer built specifically for the physical moment that everything else was designed around but never designed to reach.