How EHR Training Turns Into Institutional Folklore

Somewhere around month six or nine, someone on your team resigned. A scheduler, maybe a clinical lead. Someone who sat through the go-live training, understood the reasoning behind how things were configured, and carried that context in their head every day.

Their replacement learned from someone else in the office who knew the area of the system they’d be working in. That person had already built a few workarounds of their own. Workarounds that made sense at the time but were never written down, never validated against the original configuration, and never reviewed by anyone who remembered why the system was set up the way it was.

A few months after that, three people were using the same feature three different ways. None of it was documented.

I’ve spent 30 years on the vendor side building, implementing, and optimizing post-acute EHR platforms. This pattern shows up in nearly every organization I work with. Not because the go-live training was bad. Usually it was good. Structured sessions, dedicated super-users, real documentation, protected time for clinical staff. The problem is what happens next.

The math is working against you

This isn’t a discipline problem. It’s a structural one.

Anyone who has worked in home health or hospice knows that turnover is part of the operating reality. Clinical staff, aides, schedulers, and office coordinators, the people you trained at go-live, are not the same people using the system a year later. In many agencies, on average, a quarter to a third of them are gone within twelve months.

Every one of those departures takes institutional knowledge with them. Every replacement inherits someone else’s workaround instead of the original workflow. The drift is cumulative, and it’s quiet. Nobody notices it happening because the system still functions. People log in, do their work, and close their tasks. The fact that they’re doing it differently than the system was designed for doesn’t surface until something breaks.

Where it shows up

By year two or three, the original configuration has faded into background noise. A new scheduler doesn’t understand why visits are verified a certain way. They only know that it’s how it’s always been done. A clinician knows where to enter a note, but not what downstream process depends on that field being complete. A biller knows which errors usually need manual cleanup, but not that those errors trace back to inconsistent documentation upstream.

Two of the most common areas are billing and financial reporting. In billing, people know which buttons to push and how to generate claims, but they have no idea what really happens when they push those buttons or why they do each one. Financial reports are the same: someone runs a report a certain way, but how the number actually got on that report is a mystery. The steps get passed along. The reasoning behind them doesn’t.

The most important thing that gets lost is not always the step itself. It’s the reasoning behind the step. People know what they do. They don’t know why they do it that way, what it may affect downstream, or whether it’s what the system was built to support.

That’s how EHR training turns into institutional folklore. Everyone learned from someone who sounded confident. The system still functions. Claims still go out. Patients still get seen. But the organization has lost control of its own workflows, and the problem doesn’t announce itself as a system issue. It shows up as rework, billing delays, inconsistent documentation, avoidable support tickets, or managers saying “that’s just how we do it here.”

When documentation practices drift far enough from what was originally configured and validated, it eventually shows up in your claims. CMS has made it clear that insufficient documentation is the single largest driver of improper Medicare payments in home health. Not fraud. Not intent. Documentation that didn’t support what was billed. In hospice, the numbers are just as significant.

That doesn’t mean every documentation gap is a training problem. But I spent years on the vendor side fielding calls about “system issues” that turned out to be exactly this. Billing errors traced back to staff who never updated their configuration after regulatory changes. They didn’t realize an update was needed because they were pushing the same buttons they’d always pushed. Survey deficiencies reported as software bugs that we’d review line by line and respond to with the same note: “Training item. Staff education.” Row after row.

The tools exist. The gap is ownership.

Every major post-acute EHR vendor now offers ongoing training programs, certification tracks, and learning platforms. The resources are there. But anyone who has ever answered a support line knows that a significant share of those calls are really training questions, not technical issues. Agencies end up using vendor support as a de facto training department, which is expensive for both sides and doesn’t build internal capability.

The gap isn’t that vendors haven’t built the resources. It’s that most agencies budget for training as a project cost, close it out at go-live, and never reopen it. Training becomes an implementation expense instead of an operating practice. And nobody clearly owns what comes after.

Here’s what I think agencies most often miss: their EHR is a core system to their operations. Probably the most important one. It may also be their largest software spend. They wouldn’t think of missing an oil change or skipping an annual HVAC inspection. Yet no one will stand up and say “we need to plan to spend a percentage of this annual software cost on continuing consulting and training.”

Agencies actually do a tremendous amount of training each year. It’s just rarely on the EHR itself. And when it is, they’re often training on the drifted practice instead of the designed workflow, which actually reinforces the drift rather than correcting it. Fresh insight and knowledge from the vendor, or from an independent review, is what breaks that cycle.

Who owns EHR training after go-live? Who decides when workflows need to be reviewed? Who confirms that new hires are learning the current process, not a workaround from three managers ago? Who checks whether the live workflow still matches the system configuration?

If the answer to any of those is “nobody, specifically,” the agency should assume drift is already happening.

Four questions worth asking

If you’re a director of nursing, a clinical informatics lead, or an agency administrator, here’s where I’d start:

1. How are new hires actually learning your EHR right now? Not how the policy says they’re trained. How are they actually learning it today? If the honest answer is “shadow someone for a week,” your workflows have already diverged from what was originally configured. That’s not a criticism. It’s what happens when training isn’t built into operations. But it means you’re running on inherited knowledge, and you should know what’s in it.

2. Where are multiple people performing the same workflow in different ways? Pick one high-volume workflow and ask three people to walk you through it. If you get three different answers, that’s not just a training issue. That’s a workflow governance issue. The referral process is a good place to start. It’s costly, there are almost always efficiencies to be gained, and yet ask three of the departments involved and none of them can accurately describe what the upstream or downstream department does. The inputs and outputs.

3. When was the last time anyone compared your live workflows to the original go-live documentation? If nobody can find that documentation, you have your answer. If someone can find it but it hasn’t been touched in two years, you also have your answer.

4. Is training a line item in your operating budget, or was it a line item in your implementation budget? There’s a meaningful difference. One treats competency as ongoing. The other treats it as a completed deliverable.

How to start fixing it

If this sounds familiar, don’t start by trying to retrain the entire organization.

Start with one workflow. Choose something high-volume, high-risk, or frequently misunderstood. Map how it’s supposed to happen. Then compare that to how it actually happens today. If you didn’t map your workflows at implementation, there’s no time like the present. Hospice organizations that just went through the HOPE changes have a natural starting point: start with mapping those, because the pain is fresh and the motivation is already there.

Every agency has a quality team and a quality process. Take those same tools and apply them to your software workflows. The Plan-Do-Study-Act (PDSA) cycle works here the same way it works in clinical quality improvement. Define the standard, measure current performance against it, implement changes, and verify results.

Look at where staff are using workarounds. Look at where the documentation no longer matches reality. Look at which steps people follow without understanding why. Look at whether the system configuration still supports the current operational need.

That exercise usually reveals the real issue quickly. Sometimes the fix is training. Sometimes it’s a workflow redesign or better documentation. Sometimes the system configuration needs to be adjusted, and sometimes the agency has outgrown the way the system was originally built.

Two areas where agencies can most easily measure the return on this work are AR days outstanding and claim rejection rates. The root causes almost always trace upstream to documentation or workflow issues, and the improvement can be measured in dollars and days.

The important thing is to stop assuming that a successful go-live means the organization is still using the EHR correctly two or three years later. In post-acute care, the organization keeps changing. Training has to keep up.

The agencies I’ve seen handle this well don’t treat training as a one-time event. They treat it as a maintenance function. They keep onboarding structured, review high-risk workflows on a regular cadence, and make sure new hires understand not just what to do, but why it matters. It’s not complicated. But it does require someone to own it.

Where I help

I spent three decades building and implementing post-acute EHR platforms from the vendor side. I’ve seen this cycle from the inside: the strong go-live, the early stability, the turnover, the workarounds, the drift, and the point where leaders realize the system they configured is no longer the system their teams are using.

Today I work in partnership with HealthTECH Resources to help post-acute organizations close that gap. That might mean a workflow audit, a training reset, ongoing optimization support, or evaluating whether the current system still fits the organization’s needs. I’m also trained and experienced in Lean Six Sigma techniques, which I apply directly to agency workflow and operational problems. But the starting point is usually the same: understanding the difference between how the EHR was designed to work and how it’s actually being used in the field.

If any of this sounds familiar, I’m happy to talk it through.

Connect with Stephen | Contact HealthTECH Resources

What are you seeing in your own organizations? Is training something your agency has figured out how to sustain, or does it still end at go-live? We’d like to hear what’s working.