4.5 End-User EHR Training, Competency & Training Documentation

Test plan task 1.I — "provide initial and ongoing end-user training of EHR software to maintain competency (e.g., for new hires, upgrades and deployments)" — makes the experienced EHR specialist a trainer. Knowledge statements 1.K14 through 1.K18 fill in the specifics: considerations for remote and virtual training, coaching and mentoring techniques, training documentation requirements, available training material, and resources for developing new material.

When Training Happens

Access should never be granted before training is complete. Provisioning a login on day one and scheduling training for week three creates a window in which an untrained user is documenting in a legal record.

Role-Based Curriculum

Training is built to the role, and the curriculum should mirror exactly the privileges the user will hold. A registration clerk does not need order-entry training and should not have order-entry access; a nurse needs medication administration and flowsheet documentation but not charge master maintenance. Aligning curriculum to the role-based access control model described in Section 9.6 has a useful side effect: a training request for a workflow the role cannot perform is a signal that the access assignment or the job description is wrong.

Adult Learning and Coaching Techniques

Knowledge statements 1.K15 and 4.K11 cover coaching, mentoring, and adult education. A few principles carry most of the weight:

• Adults learn what they can immediately use. Teach the workflow the learner will perform tomorrow, in the order they will perform it, rather than touring the software menu by menu.
• Demonstrate, then let them do it. Watching is not competence. The learner should complete the workflow unaided before the session ends.
• Use realistic scenarios. "Register a walk-in whose insurance card does not match the subscriber name" teaches more than "click the Registration tab."
• Teach the exception, not just the happy path. Most errors happen when something is unusual — the patient has two coverages, the scanner jams, the interface is down.
• Follow up at the elbow. A short post-go-live rounding visit catches misunderstandings before they become habits. Section 6.3 covers at-the-elbow support in the clinical setting.

Remote and virtual training

Knowledge statement 1.K14 addresses remote and virtual training. Virtual sessions work when the design compensates for the missing room:

• Keep groups small enough that every learner can share their screen and be observed doing the work.
• Require hands-on practice in the training environment during the session, not afterward.
• Confirm connectivity, audio, and training-domain access before the session starts.
• Record sessions for reference, but never record a session in which real PHI is displayed.
• Provide a job aid the learner can keep, because remote learners cannot lean over and ask a neighbor.

The Training Environment

Training is conducted in a dedicated training or sandbox domain loaded with realistic test patients — never in production. Two rules are absolute:

1. Do not train on a real patient's chart. Opening a live record to demonstrate a feature is an access without a treatment, payment, or operations purpose, and it appears in the audit log exactly as snooping does.
2. Do not share credentials. A trainee never works under the trainer's login, and a trainer never enters production data under a trainee's login. Every EHR action is attributed to the credential that performed it, which is why unique user identification is a Required Security Rule specification (Section 9.3).

Available training material (1.K17) typically includes vendor-supplied courses and release notes, the organization's workflow documents and job aids, recorded sessions, and the in-application help. When existing material does not fit, new material is developed from the sources in knowledge statement 1.K18: frequently asked questions collected from the help desk, actual error patterns seen in audits, and a curriculum built around the role's task list.

Training Documentation

Knowledge statement 1.K16 makes documentation an explicit requirement. A defensible training record answers four questions:

These records are pulled during accreditation surveys, HIPAA security evaluations, and after adverse events, where the first question is almost always whether the involved user had been trained on the workflow. Retain them according to the organization's retention schedule; HIPAA training documentation specifically falls under the six-year rule described in Section 3.2.