A department resists a change to the electronic health record (EHR). Nobody is refusing to use it. The problem is that routine work has become slower. A task that took a minute on the old screen now takes four clicks and a search, and the unit is already short of time. Staff completed the training, and they remember that they were shown the new screens. What they were not asked to do is carry out their own shift's tasks in the new system and say what gets in the way.
This is an illustrative situation, not a documented customer case. It describes the gap that EHR change management training is meant to close: the distance between having seen a new workflow and being able to practise it, with feedback, in a way that also surfaces the barriers that stop people adopting it.
This guide is for hospital L&D directors and the informatics or compliance leads who work with them. It covers how to describe the performance problem, diagnose learning and context gaps, design preparation and practice, work through a case and assess transfer. It is about training design. It does not replace usability testing, workflow redesign or your organisation's own change programme, and it makes no promise about outcomes.
What is EHR change management training?
EHR change management training prepares the people who use the record to work in a changed system or workflow. Its task is to practise new workflows and surface adoption barriers. The learner performs a realistic task for their own role, receives feedback on it, and reports where the workflow, the tools or the policy made it hard. The second half matters as much as the first. Practice that only checks whether people can follow steps misses the barriers that decide whether they will.
Quick facts
| Question | Short answer |
|---|---|
| What is the task? | Practise new workflows and surface adoption barriers. |
| What do you score? | Task proficiency, and a log of unresolved workflow barriers. |
| Is a demonstration plus a quiz enough? | It can show prerequisites. It does not show that someone can do their own role's task at speed. |
| Who validates the content? | An informatics or compliance lead, using invented or deidentified cases. |
| What can training not fix? | A slow screen, a missing order set, an unclear policy or too little staff time. |
| How do you know it worked? | A new, unseen case scored against agreed criteria, plus the barriers still open after practice. |
1. Describe the performance problem
Start with the task: practise new workflows and surface adoption barriers. Two parts carry the weight. Practising means doing the work of the role, not watching it. Surfacing barriers means the training produces information about what is slowing people down, so that someone with authority can act on it.
Write it as one sentence for each role and have an informatics lead check it: "Given a typical task for this role, such as admitting a patient, documenting a handover or placing a standard order, the learner completes it in the new workflow, records the points of friction and says what support would help."
Roles differ. A nurse, a unit clerk and a physician use different parts of the record, so a single generic session practises none of their real tasks. A scoping review of EHR training programmes for inpatient nurses (30 studies) lists "not splitting up training sessions by role type" (Nguyen and colleagues, JAMIA, 2024). The review covers nurses in inpatient settings, so read it as a pointer for design and check it against your own population.
2. Diagnose the learning and context gaps
Before you build anything, compare the task with what your current programme practises and assesses. Three questions usually separate a training gap from something else:
- Does current practice use the real task? If the programme demonstrates the screens and ends with a recall quiz, learners have practised recognising the interface, not completing their own shift's work.
- What is the cognitive demand? In Bloom's revised taxonomy, carrying out a procedure in a new situation and analysing why it went wrong sit above recall. Matching activities to those levels is covered in our guide to matching learning activities to Bloom's Taxonomy.
- Is something other than skill getting in the way? Check staffing, tools and procedures before prescribing training. If a screen is slow, a needed order set is missing or the policy forces a duplicate entry, a better session will not change what happens on the ward. Report those causes to the people who can fix them.
The same scoping review lists practice access among the factors it identified: "not being able to practice in sandbox" appears as a barrier and "letting nurses practice in EHR after training" as a facilitator. If your learners have no safe environment to practise in, that is a context gap, not a motivation problem.
3. Design preparation and practice
Once you know which gaps training can close, give each stage a distinct job. Our guide to building EHR onboarding that reduces documentation burden covers the first-weeks design. This section is about the change itself.
Preparation. Check prerequisites with a short diagnostic: the old-to-new differences that affect each role, the terms your organisation uses and where to get help on the day. Targeted self-paced study suits this stage. A recall check confirms prerequisites only.
Practice. Use interdisciplinary quality improvement capstones and role-based case practice. Learners from different roles work one patient journey together, for example admission, a medication order, a handover and discharge, each doing their own part in a practice environment. Seeing where the handoff between roles stalls often reveals a workflow problem that no single role would report alone. Observe representative tasks and record errors and friction as you go.
Feedback. Link it to decisions rather than a total score. "You found the correct order but took the long route, and you chose to work around the alert rather than ask" teaches more than "3 out of 5". Include plausible wrong paths that explain why they tempt people. Our guide to designing interactive practice with useful feedback shows how to write feedback that links to decisions.
Live input or asynchronous review? Live coaching adds most value where a task is ambiguous, where roles must coordinate and where people need to say what is not working. Asynchronous review is enough for comparing a learner's recorded steps with an annotated model path. Many teams use both: self-paced preparation first, then facilitated sessions on the hardest workflows.
Timing. The scoping review reports barriers such as too much content in a short period and a long gap between training and go-live. Plan practice close to when people will use the workflow, and break it into sessions short enough to take in.
4. Work through a realistic example
Illustrative. An informatics or compliance lead should validate the case and the answer criteria before use.
The case. A medical-surgical unit has moved to a new documentation workflow for the shift handover. Staff say it takes longer than before. Policy requires the handover note to be complete before the outgoing nurse leaves.
The task. The learner completes a handover for a practice patient in the new workflow, records each point of friction, says what they would do about it and says what further information or support they need.
A first attempt. The learner completes the note but skips two fields that "nobody reads" and records no friction. They say the new way is "just slower". The note is incomplete against policy, and the barrier is described as an opinion with no detail.
Feedback and retry. The coach points out that the two fields are part of the policy and asks the learner to find where in the screen each one sits and how long the step takes. The retry asks the learner to complete the note again and to log, for each point of friction, what they did, how long it took and what would make it quicker.
A stronger attempt. "I completed all fields. The medication summary needs a separate search each time, which added about two minutes. I did not skip it because policy requires it. Could the summary be pre-populated, or is there an approved shortcut? I do not know whether this has already been reported, so I would raise it with the unit's super user and the informatics team." This answer meets the policy, records specific evidence and uses an approved route.
Why each response is defensible or incomplete. Judge each against approved criteria, not a coach's preference. The first attempt is a common response to a slower task, but it cuts policy fields and gives the project nothing to fix. The stronger attempt keeps to policy, stays within the learner's role and turns a complaint into evidence. The two minutes in the example is an invented figure to show the type of detail to record, not a benchmark.
5. Assess capability and plan transfer
Evidence of capability is performance on a case the learner has not seen. Score task proficiency and keep a separate log of unresolved workflow barriers. A simple rubric uses a 0 to 2 scale per criterion:
| Criterion | Observable evidence |
|---|---|
| Task execution | Completes the new workflow and records the action and evidence supporting it. |
| Reasoning | Explains relevant constraints, alternatives and what remains uncertain. |
| Boundaries | Uses approved procedures and seeks help when information or authority is insufficient. |
Anchors: 0 is absent or unsupported, 1 is partial with relevant omissions, and 2 is complete and justified against the agreed criteria. Define critical errors separately, such as skipping a policy-required field, so an overall score cannot hide one. This rubric is a proposal, not a validated readiness standard. Adapt it with an informatics or compliance lead and pilot it.
Plan transfer deliberately. After learners have been back at work for a while, add a short follow-up such as a unit huddle where people bring one real task, with details removed, and walk through how they now do it. Observe a sample of real work if your organisation's rules allow it.
Where interactive delivery helps
Interactive formats help where everyone should commit before they hear the answer. In a live session, a facilitator can show a short case, ask each person to choose their next step and type the friction they would expect, and then show the spread before the discussion. Anonymous responses can make it easier to admit that a workflow is not working. The same case can run self-paced for preparation. AhaSlides supports interactive learning and moving between live and self-paced delivery. Keep real incidents and patient information out of it, check any specific authoring, feedback or reporting function you plan to rely on against your own workflow, and treat AI, simulators and EHR integrations as external or unconfirmed until you have seen them work. For guidance on choosing formats, see our article on when to use adaptive, interactive and live learning.
Measure what changed
Decide in advance what would show that learners can do the task. Compare task proficiency and the barrier log on an unseen case with a baseline, and keep the barrier log open after training as its own measure. Define who is included, the denominator and the timing. If results improve, check what else changed in the same period, such as a software update, a staffing change or a workflow redesign, before crediting the training.
Constraints that may remain
- Usability. If a screen needs too many steps, training can teach the shortcut but cannot remove the steps.
- Staffing and time. Practice does not help if there is no protected time to do it.
- Policy clarity. A case cannot resolve a policy that duplicates entries or is ambiguous. Fix the policy.
- Case coverage. One case shows one workflow. A score does not describe a person's performance in general.
- Transfer. Performance on a practice case is not the same as performance with a full ward and a ringing phone.
Name these to sponsors early and plan separate fixes. Training improves what learners can do. It does not change the conditions around the task.
Frequently asked questions
What is EHR change management training?
It prepares staff to work in a changed EHR or workflow through role-based practice and feedback, and it collects the barriers that practice reveals so someone can act on them.
Does passing the training mean staff have adopted the change?
No. A score shows how a person handled one training case. Adoption shows up in real work and depends on usability, staffing and policy as well as skill.
How do you assess readiness for a new workflow?
Give a case the learner has not seen and score task proficiency against agreed criteria, then log the barriers that remain. A recall quiz confirms prerequisites only.
Can you use real patient cases for practice?
Only with details removed and your compliance lead's approval. Invented cases built on common workflows are safer, and patient information should stay out of training tools.
Where to start
Pick one workflow people say has become slower. Write the performance statement for each role, have an informatics or compliance lead validate an invented case and the answer criteria, and draft a three-criterion rubric with a 0 to 2 scale, a list of critical errors and a barrier log. Pilot it with a small group before you roll it out.
To see how a case could run live with your own team, and be reused self-paced afterwards, explore AhaSlides.
