Study guide

6.3 Point-of-Care EHR Support & Telehealth Workflows

NHA Certified Electronic Health Records Specialist CEHRS

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About the NHA CEHRS Exam The CEHRS Test Plan & How to Use This Guide

2 Chapter 1: Foundations — Medical Terminology, Health Care Settings & the EHR

1.1 Medical Terminology I: Roots, Prefixes, Suffixes & Combining Forms 1.2 Medical Terminology II: Body Systems, Directional Terms & Clinical Abbreviations 1.3 Health Care Systems, Settings, Personnel & Credentials 1.4 Parts of the EHR & Core Functions of the Electronic Record 1.5 Regulatory Agencies, Professional Standards & Population Health Concepts

3 Chapter 2: Non-Clinical Operations — Patient Registration & Scheduling

2.1 Patient Registration & Intake Workflows 2.2 Master Patient Index (MPI) & Demographic Management 2.3 Appointment Scheduling & Resource Management 2.4 Patient Communication, Portals & Front-Office Operations 2.5 Encounter Documentation: Face Sheets, Labels, Armbands & Check-Out

4 Chapter 3: Non-Clinical Operations — Health Record Administration & Archiving

3.1 Health Record Types, Hybrid Systems & Data Conversion 3.2 Record Retention, Storage & Archival Policies 3.3 Release of Information (ROI) & Authorization Procedures 3.4 Auditing, Chart Maintenance & Record Integrity

5 Chapter 4: Non-Clinical Operations — Data Sources, Devices & EHR User Support

4.1 Retrieving Patient Data from Internal Databases (Provider, Payer & Financial) 4.2 Acquiring Patient Data from External Sources 4.3 Importing from Integrated Devices & Managing EHR Hardware Inventory 4.4 Identifying, Reporting & Reconciling Data Discrepancies 4.5 End-User EHR Training, Competency & Training Documentation 4.6 Communicating Software Updates, IT Troubleshooting & Escalation

6 Chapter 5: Clinical Operations — Clinical Intake, Point-of-Care & Vitals

5.1 Clinical Intake, Rooming & Vital Signs Documentation 5.2 Chief Complaint, History of Present Illness (HPI) & ROS 5.3 Physical Exam Documentation & Clinical Notes Formatting (SOAP) 5.4 Allergy Documentation, Adverse Reaction Logging & Safety Alerts 5.5 Problem Lists, Medical History & Immunization Tracking 5.6 Patient Education Materials in the EHR & Scope of Practice

7 Chapter 6: Clinical Operations — Templates, Documentation Review & Data Retrieval

6.1 Developing Clinical Templates for Data Capture 6.2 Reviewing Clinical Documentation for Completeness & Accuracy 6.3 Point-of-Care EHR Support & Telehealth Workflows 6.4 Navigating the EHR to Retrieve Requested Patient Data 6.5 Securely Transmitting & Exchanging Patient Data

8 Chapter 7: Clinical Operations — CPOE, Orders & Decision Support

7.1 Computerized Provider Order Entry (CPOE) Fundamentals 7.2 Laboratory & Diagnostic Test Order Entry and Results Tracking 7.3 Medication Reconciliation, e-Prescribing & Formulary Checks 7.4 Clinical Decision Support Systems (CDSS) & Practice Guidelines 7.5 Clinical Care Coordination, Referrals & Discharge Planning

9 Chapter 8: Revenue Cycle & Financial Management

8.1 Insurance Verification, Eligibility (EDI 270/271) & Prior Authorization 8.2 Superbills, Charge Capture & Encounter Form Management 8.3 Coding Fundamentals for EHR: ICD-10-CM, CPT & HCPCS Level II 8.4 Claim Submission (EDI 837), Remittance (EDI 835) & Revenue Cycle 8.5 Providing Estimated Patient Costs & Good Faith Estimates 8.6 Patient Statements, Payment Collection & Balance Reconciliation

10 Chapter 9: Regulatory Compliance, HIPAA & Security

9.1 HIPAA Privacy Rule & Protected Health Information (PHI) 9.2 Minimum Necessary Rule, Permitted Uses & Patient Rights 9.3 HIPAA Security Rule: Administrative, Physical & Technical Safeguards 9.4 HITECH Act, Breach Notification Rule & Business Associate Agreements (BAAs) 9.5 Information Blocking Rules, 21st Century Cures Act & Compliance Audits 9.6 Allocating & Verifying EHR Access Controls and Role-Based Privileges 9.7 Educating Staff, Identifying Non-Compliant Behavior & Escalation 9.8 Abbreviation Policies, Professional Standards & EHR Downtime Procedures

11 Chapter 10: Data Management, Reporting & Health IT Standards

10.1 Health IT Interoperability: HL7, FHIR & Health Information Exchanges (HIE) 10.2 Standardized & Ad Hoc Financial Reports 10.3 Standardized & Ad Hoc Clinical Reports 10.4 Verifying Report Accuracy & Avoiding Common Reporting Errors 10.5 Quality Reporting, MIPS, Promoting Interoperability & Clinical Dashboards 10.6 Data Abstraction, Quality Improvement Studies & EHR System Security Management

6.3 Point-of-Care EHR Support & Telehealth Workflows

Key Takeaways Explain This Topic AI

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.

Last updated: August 2026

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.