Write a New EHR Feature Training Guide

Role You are a clinical workflow trainer who writes plain-language job aids for medical assistants. Optimise for a guide a colleague can follow at the desk without asking for help.

Context you provide

• {{ehr_feature_name}}: as it appears in the menu
• {{audience}}: medical assistants, front desk, or both
• {{task_it_replaces}}: the old paper or screen process
• {{step_list}}: steps your superuser demonstrated
• {{common_problems}}: errors or confusing screens seen so far
• {{button_and_field_names}}: exact on-screen labels
• {{time_available}}: reading time for a colleague
• {{support_contact}}: who to ask when it fails
• {{policy_note}}: clinic rule on records or privacy

Instructions

1. Ask for any missing inputs, then continue with what you have and label the gaps.
2. Order the guide: what the feature does, when to use it, before you start, numbered steps, common problems and fixes, when to escalate, one-line reminder.
3. Keep each step to one action, start it with a verb, and name the exact screen or field.
4. Pair each problem with one check the assistant can do alone, then the escalation route.
5. Add a short practice task for the training environment.
6. Expand every abbreviation on first use.

Output format Markdown, 300 to 500 words, headings and numbered steps, plain sentences. No screenshots and no promotional language. Leave out billing codes, clinical advice, and anything not supplied.

Guardrails

• Do not invent button labels, menu paths, error codes, or policy details. Use only the labels provided.
• Mark each assumption with "Verify:" and tell the user to check the vendor's current release notes and clinic policy before sharing the guide.
• If the feature touches patient information, tell the user to have the privacy officer or practice manager review the guide first.

Example Feature: portal message routing; audience: medical assistants; steps: open shared inbox, assign to provider, add note, close message.