7.6 Telehealth, Patient Portals, and Electronic Communication
Key Takeaways
- Before a telehealth visit, verify identity with two identifiers, confirm the patient's physical location and a callback number, and ensure a private setting.
- Patient portals support appointment info, visit summaries, secure messaging, lab routing, prescription refills, and forms.
- All electronic communication must comply with HIPAA; use the secure portal, not personal text or standard email, for protected health information.
- Clinical questions arriving by portal message are routed to the provider when they exceed the CCMA scope, and urgent symptoms are escalated, not left in the inbox.
- Telehealth requires verifying the patient is in a state where the provider is licensed and confirming technology access (camera, audio, login, interpreter).
Virtual Care, Same Rules
Telehealth delivers care over secure video or phone. The privacy, identity, and scope rules from in-person care still apply, plus new logistics the CCMA manages.
Telehealth Visit Setup Checklist
| Step | Why It Matters |
|---|---|
| Verify identity (two identifiers) | Prevent wrong-patient encounters when you cannot see an ID at the desk |
| Confirm physical location | Needed for emergencies (dispatch) and for provider licensure (the provider must be licensed where the patient is) |
| Obtain a callback number | Reconnect if the connection drops |
| Ensure privacy on both ends | The patient should be in a private space; you must be too (HIPAA) |
| Test technology | Camera, microphone, login, bandwidth; arrange interpreter access if needed |
| Confirm consent | Telehealth consent per policy |
A dropped call mid-visit is a logistics problem the CCMA solves with the callback number, not a reason to abandon the encounter.
Patient Portal Functions
The patient portal is the secure, patient-facing window into the EHR. Tested functions include:
- Viewing appointments, visit summaries, and after-visit instructions
- Secure two-way messaging with the care team
- Reviewing lab and imaging results released to the patient
- Requesting prescription refills
- Completing intake forms and updating demographics
- Paying bills
HIPAA and Electronic Communication
Protected health information must travel over secure channels.
| Channel | Acceptable for PHI? |
|---|---|
| Secure patient portal | Yes |
| Encrypted/secure email per policy | Yes, if the system is secure and consent exists |
| Standard unencrypted email | No |
| Personal cell phone text message | No |
| Social media / direct message | No |
Never send results, diagnoses, or chart details by personal text or open email. Verify identity before discussing PHI by phone. Auto-forwarding a work inbox to a personal account is a HIPAA risk.
Triaging Portal Messages
Portal messages are not all routine. The CCMA reads, categorizes, and routes:
- Administrative (reschedule, form request): handle within scope.
- Clinical, within scope (relay a provider-approved instruction): handle and document.
- Clinical, beyond scope ("Is this rash an allergic reaction?"): route to the provider or nurse.
- Urgent / emergency ("I'm having chest pain right now"): do not leave in the queue; escalate immediately and direct the patient to emergency care.
A message is not "answered" because it was read. Document the action and the routing.
Accessibility and Worked Example
Offer phone-visit alternatives for patients without a camera, portal help for those new to technology, and interpreter access for limited-English patients. Worked example: a portal message reads, "My new blood pressure pill makes me dizzy and my heart is racing." The trap is to reply "keep taking it as directed." The correct CCMA action is to route this medication-reaction concern to the provider promptly and, if the patient reports severe or emergency symptoms, escalate to urgent care or 911 per protocol, then document.
Telehealth Modalities
The exam distinguishes types of virtual care:
| Modality | Description |
|---|---|
| Synchronous | Real-time audio/video visit between patient and provider |
| Asynchronous (store-and-forward) | Patient or clinic sends images/data for later review |
| Remote patient monitoring | Devices transmit vitals (BP, glucose, weight) to the care team |
| Audio-only | Phone visit, used when video is unavailable |
Knowing these helps you choose the right accommodation: a patient without a camera may still complete an audio-only visit; a wound photo can be handled store-and-forward.
Pre-Visit Workflow in Order
A defensible telehealth setup sequence: confirm consent on file, verify identity with two identifiers, confirm the patient's physical location and a callback number, ensure privacy on both ends, test the connection, arrange an interpreter if needed, and load the chart. If the connection drops, you reconnect using the callback number rather than abandoning the visit; if technology fails entirely, you offer an audio-only or in-person alternative per policy.
Portal Etiquette and Turnaround
Portal messaging is convenient but is not a substitute for emergency care, and patients must be told so. Practices set message turnaround expectations (commonly one to two business days for routine messages) and direct emergencies to 911. The CCMA monitors the message queue during business hours, never lets a clinical or urgent message sit unrouted, and documents the action taken.
Privacy on Both Ends
HIPAA applies to your environment too. Position screens away from other patients, lock the workstation when you step away, and do not conduct a telehealth visit where others can overhear protected information. Verify identity before discussing any results by phone or portal. A strong electronic-communication answer keeps protected health information on secure channels, verifies identity, routes clinical questions appropriately, escalates emergencies, and documents; a weak answer trades privacy or scope for convenience.
Documentation in Virtual Care
Telehealth and portal encounters are charted like any visit. Record the modality (video, audio-only, store-and-forward), confirmation of identity and location, who participated (including an interpreter), the content handled or routed, and the patient's response. A portal message you route to the provider is documented with the action and timestamp so the audit trail shows it was not dropped. The same scope rules apply: you may relay provider-approved instructions and handle administrative items, but a clinical judgment leaves your lane and goes to the nurse or provider.
Treating a virtual encounter as "less official" than an in-person one is a trap; the legal and privacy standards are identical.
Before starting a telehealth video visit, why must the CCMA confirm the patient's current physical location?
A patient asks the CCMA to text lab results to their personal cell phone. What is the correct response?
A portal message states, "My new heart medication is making me dizzy and my heart is pounding." What should the CCMA do?