4.6 Communicating Software Updates, IT Troubleshooting & Escalation

Test plan task 1.J — "share information about updates to EHR software and the implications for workflow" — pairs with knowledge statements 1.K19 through 1.K22: procedures to disseminate updated information, basic IT troubleshooting techniques, IT escalation procedures, and the EHR software reference library. Together they describe the experienced specialist's second job: being the bridge between the IT department and the people using the system.

Communicating an Update

A vendor release note says "Enhanced results routing logic for orders with multiple performing labs." A clinician needs to know "starting Tuesday, split lab orders will appear as two separate results in your inbox instead of one." Translating the first into the second is the work.

Every update notice should answer five questions:

Delivery channels

No single channel reaches everyone. Combine at least two:

• Email or intranet post for the full detail and the job aid attachment
• A short in-application message or login banner on the day of the change
• Huddle and staff-meeting talking points so managers can reinforce it
• Printed job aids at the workstations where the change occurs
• At-the-elbow support during the first shifts after a significant change

Timing matters: send advance notice far enough ahead for questions, then a same-day reminder. For changes that alter a safety-relevant behavior — alert logic, order routing, medication display — advance notice is not optional.

Downtime notices

Planned downtime notices carry extra content: the exact window, which systems are affected, which downtime forms to use, where to find them, and the reconciliation expectation after restoration. Section 9.8 covers the downtime procedures themselves.

First-Line Troubleshooting

Knowledge statement 1.K20 covers basic IT troubleshooting. The goal is not to fix the network; it is to determine quickly whether the problem is local and to gather what the help desk needs.

1. Scope it. Is it one user, one workstation, one department, or everyone? A single user with a problem no one else has is usually credentials, permissions, or a local device. Everyone at once is a system or interface issue.
2. Check the physical layer. Cables seated, device powered, printer online and stocked, scanner lid closed, signature pad connected, network cable in the right port.
3. Check the obvious software layer. Correct application and environment (production versus training), user logged in as themselves, session not timed out, correct patient and encounter selected.
4. Try the standard resets permitted by policy — log out and back in, restart the application, restart the workstation, reconnect the peripheral.
5. Capture the evidence. Find the computer name and IP address (the help desk needs both to locate the machine), take a screenshot of the exact error, and note the exact time.

Escalation

Knowledge statement 1.K21 covers escalation procedures. A ticket that gets solved quickly contains:

• Who: user name and role, plus the reporter if different
• Where: computer name, IP address, department, and location
• When: exact date and time of the error, and whether it repeats
• What: the verbatim error message, a screenshot, and the exact steps to reproduce
• Context: the patient or encounter involved, referenced by MRN or encounter number rather than by pasting clinical detail into the ticket
• Impact: how many users are affected and whether patient care is delayed

Severity and channel

Never wait for a ticket queue when patient safety is involved. A missing result or a chart displaying another patient's data is a phone call and a manager notification, followed by documentation.

PHI in tickets

Include the minimum necessary to resolve the issue. An MRN or encounter number identifies the case for the analyst; pasting an entire progress note into a ticketing system that may not be covered by a business associate agreement is an unnecessary disclosure.

The EHR Reference Library

Knowledge statement 1.K22 refers to the EHR software reference library — the organization's curated set of vendor documentation, release notes, configuration guides, workflow documents, job aids, and known-issue lists. Its value depends on discipline:

• One authoritative location, not a folder on each manager's drive
• Version-labeled documents so users can tell current from superseded
• Retired material archived rather than left in circulation
• A known-issues page with current workarounds, which prevents the same ticket from being opened forty times
• Ownership assigned, so the library is updated as part of every release rather than whenever someone remembers

When a user asks "how do I do this," the right answer points at the library and, if the library does not answer it, produces a new job aid — which is exactly the material-development source described in Section 4.5.