6.3 Point-of-Care EHR Support & Telehealth Workflows
Key Takeaways
- At-the-elbow support places a specialist beside the clinician during live care to resolve EHR problems without interrupting the visit.
- Point-of-care support requires patient consent to the observer's presence, strict scope-of-practice limits, and never documenting under the clinician's credentials.
- Remote support uses screen sharing and remote control tools that must be logged, consented to by the user, and covered by a business associate agreement when a vendor is involved.
- Telehealth workflows add technology checks, patient location verification, consent to virtual care, and modality documentation to the standard encounter.
- Support interactions that reveal recurring problems become training topics, template fixes, or tickets rather than repeated one-off rescues.
Test plan task 2.D — "provide point-of-care EHR support (e.g., at-the-elbow, remote) for clinical documentation" — puts the specialist in the room, or on the screen, while care is happening. Knowledge statement 2.K4 adds telehealth and telemedicine workflows. This is the highest-stakes support setting in the blueprint, because a mistake happens in front of a patient and inside a live record.
At-the-Elbow Support
At-the-elbow (ATE) support means a knowledgeable EHR user stands beside a clinician during real patient care to answer questions and resolve problems immediately. It is deployed after go-lives, after major upgrades, when a new clinician joins, and when audit data shows a workflow is failing.
Before entering the room
- Obtain patient permission. The clinician introduces the support person and confirms the patient is comfortable with an additional person present. A patient may decline, and that decision is honored.
- Confirm the purpose. Support is present for the system, not the care.
- Position deliberately — beside or behind the clinician, with the screen visible to the supporter but not exposed to the waiting area or a doorway.
Rules inside the room
| Do | Do Not |
|---|---|
| Guide the clinician to the correct screen and click path | Take the keyboard and document clinical content yourself |
| Answer "where is this field" and "how do I do that here" | Answer "what should I order" or "what does this result mean" |
| Note the issue for follow-up | Interrupt the clinical conversation to teach |
| Escalate a defect while the clinician continues care on a workaround | Log in under the clinician's credentials for any reason |
The credential rule is absolute and is tested repeatedly: every EHR action is attributed to the credential that performed it, and unique user identification is a Required Security Rule specification (Section 9.3). If the supporter must enter something, they enter it under their own login within their own scope, and the clinician authenticates their own clinical entries.
Documentation and confidentiality
The supporter sees PHI. That access is permissible as a health care operations use, but the minimum necessary standard still applies: view what the task requires and nothing more. Support notes should capture the workflow issue and the resolution, referencing the encounter by number rather than copying clinical content into a ticket (Section 4.6).
Remote Point-of-Care Support
Remote support extends the same service by screen share or remote control. Additional controls apply:
- User consent to the session. The clinician explicitly accepts the connection; silent remote viewing of a clinical workstation is not acceptable.
- Session logging. Who connected, to which workstation, when, and for how long.
- Vendor access controls. When a software vendor connects, a business associate agreement must be in place (Section 9.4), access is time-limited and supervised, and the session is recorded or logged per policy.
- Screen hygiene. Close unrelated charts before sharing; a shared screen showing a different patient's chart is an unauthorized disclosure.
- Recording restrictions. Do not record sessions that display PHI unless policy explicitly permits it and the recording is stored as protected data.
Telehealth and Telemedicine Workflows
Knowledge statement 2.K4 makes telehealth a named topic. A virtual visit is a real encounter with extra steps, and the specialist usually owns most of them.
Before the visit
- Verify the platform is compliant. The video service must be covered by a business associate agreement and must support encrypted transmission. Consumer video tools without a BAA are not acceptable for routine telehealth.
- Confirm technology readiness. Test the patient's ability to connect, ideally with a pre-visit test link; confirm audio, video, and portal access.
- Verify licensure and location. The provider generally must be licensed where the patient is located at the time of service, which is why patient location is verified and documented at every visit.
- Obtain and document consent to receive care by telehealth, including any limitations and the plan if the connection fails.
- Confirm coverage. Telehealth benefits, cost sharing, and originating-site rules vary by payer and change over time; verify eligibility as in Section 8.1.
During the visit
- Verify identity using two identifiers, exactly as in an in-person rooming (Section 5.1).
- Confirm and document the patient's physical location and who else is present in the room on either end.
- Confirm the provider is in a private location and the patient is somewhere they can speak freely.
- Capture patient-reported data — home blood pressure, weight, glucose readings — into the appropriate structured fields, flagged as patient-reported rather than clinic-measured.
- Document the modality — synchronous audio-video, audio-only, or store-and-forward — because it affects both clinical interpretation and billing.
After the visit
- Deliver the After Visit Summary through the portal.
- Route e-prescriptions, orders, and referrals as in an in-person visit.
- Document any technology failure and how it was handled, including conversion to audio-only or to an in-person appointment.
Turning Support Into Improvement
The point of tracking support interactions is to stop repeating them. Recurring questions become job aids and training topics (Section 4.5); recurring workflow failures become template or configuration changes (Section 6.1); recurring defects become tickets with reproduction steps (Section 4.6). A support program that never reduces its own call volume is not working.
During at-the-elbow support, a physician is running behind and asks the specialist to log in with the physician's credentials and enter the orders. How should the specialist respond?
A telehealth visit is scheduled for a patient who will be traveling in another state that day. Why must the patient's physical location be verified and documented at the time of service?
A software vendor's support engineer requests remote access to a clinical workstation to troubleshoot an EHR defect. Which control is required before the session begins?