Optimizing Telehealth Workflows in ChARM EHR

TL;DR

Telehealth in ChARM works when someone decides, in concrete terms, how a virtual visit should flow and then encodes those decisions in the system: one default visit type, scheduling blocks that match reality, intake and consent attached automatically, a single way to join, templates written for remote care, orders and follow-ups as tasks instead of messages, billing defaults tied to visit types, and a short monthly audit loop. This checklist walks each of those in order.

ChARM Telehealth Done Right: A Working Checklist

Telehealth is rarely failing your clinic because of video quality or patient demand. It fails in the gaps around the visit: clumsy scheduling rules, patient confusion, staff chasing links, double documentation, billing misses, and no clean way to prove what happened if you are audited.

The core question this checklist answers:

How do you configure ChARM so telehealth visits run as cleanly as in-person visits, without burning staff time or leaking revenue?

I write from the perspective of someone pulled into clinics after telehealth go-lives that quietly wrecked throughput and staff morale. ChARM can support clean, scalable telehealth, but not by default. Walk this line by line with your team, and anywhere you cannot say “yes, we do that, and we know why,” you have found a real source of friction.

1. Define One Telehealth Operating Model, Not Five

If your team cannot describe in one sentence how a telehealth visit flows from scheduling to payment, your ChARM configuration will reflect that confusion.

1.1 Decide what telehealth means in your clinic

Before touching ChARM settings, answer these with your lead clinician and leadership:

Which visit reasons are telehealth only?
Which can be either in-person or telehealth?
Which must never be telehealth?
Which states can we legally see patients in?
Which payers do we bill for telehealth, and which do we not?

That short list is your telehealth policy. If eligibility lives only in someone’s head or a Word doc on a shared drive, expect recurring mistakes, so push it into the system: separate telehealth locations where needed so reporting and claims stay clean, patient tags or custom fields for in-person-only patients and payer notes, and internal notes on visit types so staff see the rules at booking time.

1.2 Lock the model into visit types

Start with exactly one default telehealth visit type covering 80 to 90 percent of your remote volume, then add only what you can justify. A workable minimum set is new patient telehealth, follow-up telehealth, and telehealth urgent or same-day. For each:

The name is obvious to staff and patients, for example “Telehealth - Established Patient” or “New Patient Telehealth - 60 min.”
Duration matches how clinicians actually work, not what someone wishes were true.
Buffer time is built in for documentation or quick follow-ups.
The default billing profile is correct: codes, modifiers, or cash fee schedule.
Patient portal visibility is configured deliberately.

What I see in failed deployments is five or six telehealth types with tiny differences. Front desk staff guess, providers run behind, reporting gets muddy. If staff have to remember that a “Video 30” is really a 25-minute visit starting on the half hour, that is a workflow smell. The rules belong in the configuration.

1.3 Give each visit type a master template

Each provider has a default telehealth encounter template tied to that visit type.
The template captures what you need for billing, audit readiness, and continuity.
In-person-only sections have been removed, not just ignored.

If your telehealth note still shows palpation and gait for migraine follow-ups, clinicians will either skip half the template or free-text over everything, and that is how audit risk sneaks in. One or two strong templates per visit type beat a dozen barely different versions.

2. Make Scheduling Error-Proof

Most telehealth chaos starts when the visit is booked. Clean that step and the rest simplifies itself.

2.1 Separate telehealth and in-person availability

Your schedule should answer three questions at a glance: when is this provider doing telehealth, how long are the slots really, and who can book into them.

We use separate sessions or blocks in ChARM for telehealth hours.
Telehealth blocks are labeled so staff can tell what is what without opening the slot.
Double-booking rules are locked down.
Slot durations respect real visit length plus admin overhead.

Avoid mixed blocks like “9 to 12, in-person or telehealth” unless your team has extremely tight discipline; every flexible rule becomes an edge case in real life. When “just squeeze a telehealth in between” becomes a habit, that provider’s day collapses by early afternoon.

2.2 Standardize who is allowed to schedule what

Decide how telehealth visits may enter your system, then set hard rules:

Can patients self-schedule telehealth, and for which visit types only?
Can MAs or nursing staff schedule directly, or must it route through the front desk?
Can a provider flip an in-person visit to telehealth same-day, and under what conditions?

Implement guardrails rather than reminders: disable self-scheduling for visit types that require pre-screening, confirm location, provider, and telehealth mode auto-populate on every pathway, keep a one-page “Telehealth Scheduling Rules” reference, and review the appointment list periodically to catch mis-typed visit types. Repeated incorrect bookings are a configuration problem, not a staff problem.

Telehealth breaks down when intake becomes a game of catch-up in the first five minutes. Providers should not spend that time hunting for meds, allergies, and the chief complaint.

3.1 Attach the right forms to the right visit types

For each telehealth visit type, confirm in ChARM:

The telehealth consent form is auto-attached.
The right clinical intake form is attached, and it differs for new versus follow-up.
Payer-specific or program-specific forms attach by rule, not by memory.
Demographics, insurance updates, and payment on file or a self-pay agreement are part of the default flow.

Keep the questionnaire lean and write it for patient comprehension, not internal shorthand. Reusing in-person intake forms that assume a front desk handoff produces confusion and missing fields. Strip it to what the provider needs before joining: reason for visit, interval history, key patient-reported outcomes, and a safety screen where relevant.

Then test it with a dummy patient: schedule each telehealth visit type, log in as the patient, and confirm that emails, portal prompts, and form visibility match what you believe is configured. If staff routinely say “they didn’t fill that out, I’ll just ask on the call,” that is unbilled time and documentation risk.

3.2 Set timelines, reminders, and an intervention cutoff

Timing matters more in telehealth because there is no front desk interaction to catch gaps. Define how far ahead intake becomes available, what reminders fire, and when staff intervene manually. A pattern that works in most ambulatory clinics: new telehealth forms open three days before with reminders at 48 and 24 hours; follow-up forms open 24 hours before with a reminder at 12 hours. Then decide what staff do if forms are still incomplete two hours out. Without a defined intervention point, intake gets done live on the call, every time.

3.3 Name the owner of pre-visit review

It is explicitly clear who reviews pre-visit intake: MA, nurse, or provider, and that sits in a protocol rather than a verbal habit.
A ChARM task or flag marks “pre-visit review completed.”
One to two business days out, someone confirms forms are done, insurance is valid or a cash agreement is in place, and the callback number is current.
If any of those fail, staff follow a scripted protocol: reschedule, convert to in-person, or flag the provider.

When “someone” is supposed to review intake, nobody owns it. That is the difference between a focused 15-minute visit and a rushed 25-minute one with no extra reimbursement.

4. Make Joining The Visit Boringly Reliable

The goal is not fancy features. The goal is that nobody has to ask where the link is or which platform you are using today.

4.1 One primary channel, one entry point

We picked one primary method: ChARM’s built-in telehealth module, or one tightly standardized external tool.
The link or module is automatically associated with the telehealth visit type.
The patient-facing reminder contains a single clear path to join.
Everyone uses the same entry point in ChARM to start the session.
Providers do not fall back to ad hoc Zoom or FaceTime except as a documented last resort.

If you must support a backup platform, define when it is used and how the link is stored in ChARM. When a clinic allows three or four launch habits, support requests and no-show confusion spike.

Clean up the notification templates while you are there. Include the date and time with time zone, exactly how the patient will join, and any pre-visit requirements, and strip out ambiguous language like “you will receive a link soon,” which generates support calls. Keep one sequence: confirmation at booking, reminder 24 hours before, reminder one hour before.

4.2 Define roles for the visit window

A good workflow says who does what in the 15 minutes around the scheduled time: who checks whether the patient has joined or is struggling, who triggers a backup phone or text contact, and who documents no-shows and late cancels. If MAs perform remote rooming, give them dedicated schedule time for it, and use visit status fields or tags for states like “in virtual waiting room,” “roomed,” and “with provider.” If your MA is also covering the front desk and the fax queue, telehealth will always feel like an interruption.

4.3 Write down the no-show rule

Define a telehealth no-show concretely, for example the patient has not joined by X minutes. Make sure staff know how to mark it in ChARM using visit status or cancellation reason, and keep the rescheduling rule simple enough that it needs no case-by-case judgment. Telehealth no-shows feel less visible than an empty exam room, and if you do not capture them accurately you cannot measure provider utilization or tune reminders.

5. Documentation That Is Telehealth-Native

Documentation is where clinics either become audit-ready or accumulate risk. Telehealth charts tend to be messier because providers are multitasking in a browser instead of a controlled exam room.

5.1 Separate what you observed from what you could not assess

Templates clearly distinguish “observed via video” from “not assessed remotely.”
Providers have quick text or macros for standard telehealth exam language.
We do not copy-forward in-person exam elements into telehealth notes.

In audits, the problem is never that you used telehealth. It is documentation implying you did things that are impossible through a screen. Build templates that make that structurally difficult.

5.2 Put billing-critical elements in the normal note flow

Time documentation is captured where appropriate.
Modality, video versus audio-only, is trivial to record.
Medical decision making is structured, not free text.
Telehealth consent is captured reliably inside the encounter.

If a provider has to scroll to some out-of-the-way section for consent or time, they will forget on busy days. Move these into the natural sequence: HPI, assessment, plan, consent and time.

And keep the flow linear. If providers routinely have five ChARM tabs open per visit, manually attach templates, or copy-paste from other notes, that is a system design issue, not a discipline issue. Fix it with cleaner defaults, templates pre-assigned per visit type, and staff prepping charts beforehand.

6. Orders, Follow-Ups, and Messages Stay Inside ChARM

Work generated during a telehealth visit either flows to staff cleanly or piles up as invisible to-dos.

Providers create real ChARM tasks for follow-ups that need staff action, using consistent task types such as “Telehealth lab follow-up” and “Telehealth Rx check-in.”
Someone owns the task queue every day, with defined backup coverage.
All labs, imaging, and referrals are ordered in ChARM, not by email or personal messaging apps.
Patient-facing follow-up instructions go through ChARM communication tools or attached documents.

Telehealth amplifies the temptation to do quick off-platform work, and over time that breaks reporting, legal defensibility, and team trust. Tasks give you visibility, routing, and a backlog you can manage.

Codify follow-up intervals too. Providers should pick from a short, pre-agreed menu, and ChARM appointment types should reflect those intervals: a new medication start in this class gets a telehealth check at two weeks, then in-person at three months. Then audit a sample week and confirm you can trace note to order to communication on every visit.

7. Close The Billing Loop On Every Visit

If your telehealth volume grew fast, your billing setup is probably a patchwork, and that is where revenue goes missing. With your biller, define for each telehealth visit type the default service code, required modifiers, and place of service. Then bake it in:

Billing profiles are linked directly to visit types.
Defaults cover at least 80 percent of expected cases.
The remaining cases have a short decision guide and a defined escalation path.
At checkout, staff choose from a defined list that already includes the needed modifiers.

The objective is not to automate every edge case but to remove enough variability that staff touch far fewer encounters. If billing staff regularly fix telehealth encounters downstream, that is a configuration problem, not a training problem.

Then tag telehealth visits as a distinct cohort so you can watch no-show rate, denial rate, average reimbursement versus in-person, and time between service and claim submission. If denials or lag days run higher, work backward from the data to the failing step: scheduling, documentation, coding, or claims configuration.

8. Be Audit-Ready By Default

If telehealth is a material part of your revenue, assume it will be scrutinized. At a minimum, your workflow should reliably capture:

Patient location at the time of service, where required.
Provider location, where relevant to your jurisdiction.
Modality used: video or audio.
Start and end times, or total time, if used for coding.
Confirmation of telehealth consent, stored in a consistent place.

Configure templates and forms so none of that is optional or scattered. Regulators care less about how your staff felt than about whether these data points exist in the record every time.

You also want to reconstruct the visit trail: when it was scheduled, how the patient was notified, when they checked in, what was documented, and what was billed. ChARM stores most of this natively; you widen the margin by avoiding undocumented off-platform work and keeping messages in the record instead of private email or chat.

9. Plan For The Failure Modes You Will Actually Hit

Bandwidth drops, browsers misbehave, patients use outdated devices. You need defined fallback paths, not improvisation:

Patient cannot join: staff call within a defined window, troubleshoot, then convert to a phone visit where compliant or reschedule.
Video fails mid-visit: the provider documents the switch to phone, staff note it in the encounter, and audio-only billing rules are applied consistently.
Provider cannot connect: a named staff member notifies patients and reschedules, with consistent status changes in ChARM.
Platform outage: a predefined backup tool or conversion rule, plus its documentation requirements.

Give staff short scripts for explaining telehealth to a first-time patient, troubleshooting before escalating, and what to say when the connection drops. You should also be able to answer at any moment how many patients are waiting, which visits are late, and how many no-shows you have had today.

10. Automate Only Where It Pays For Itself

Telehealth tends to trigger an automation arms race, with texts, bots, and reminders layered on before the basic workflow is stable. That accelerates the mess.

Light automation that pays off: attaching specific intake forms to specific visit types, triggering an internal task when a visit is booked under particular payer rules, and a small library of templates for the messages that repeat constantly, such as normal lab, abnormal lab with instructions, and refill. Avoid routing logic staff cannot override, automations that silently change visit types or modifiers, and templating everything.

Before designing reminder timing, know your actual no-show and late-cancel rate from ChARM data, and make sure messaging distinguishes telehealth from in-person. If staff feel more in control and spend less time per visit, keep the automation. If they spend more time chasing it, roll it back.

11. Measure A Few Things, Train, Then Scale

If you are not looking at telehealth regularly it will drift, and ChARM will happily let that continue for years. Pull a small, consistent sample of encounters every month and check documentation completeness, consent wording, and billing accuracy, and turn findings into template or workflow changes rather than verbal feedback.

Track two or three operational metrics, not a dashboard forest: no-show and late-cancel rate against in-person, average visit length against scheduled duration, and time from visit to completed documentation. If scheduled duration is 20 minutes and the actual average is 28, that is a workflow issue, not a work-harder issue. When numbers look off, check configuration first and process second.

Make sure the workflow does not live in a few people’s heads. For each major step, scheduling, intake, pre-visit review, visit, follow-up, know which role owns it and what the backup is. Have staff practice inside ChARM in a test environment, including how to recover when something goes wrong, and refresh training whenever templates or appointment types change. I often find MA teams doing quiet, unrecognized work to keep telehealth moving; that is fragile and it burns people out.

Then run one iteration cycle before you scale: one provider, one visit type, two to four weeks. Track how many visits start on time, how many need intervention for tech issues, and how many are clean on the first pass. Tune what broke, then roll out the improved pattern rather than the original.

Closing: A Quick Self-Audit

You do not have to fix everything at once. Start with five questions:

Are your telehealth visit types clean, distinct, and mapped to the right locations and billing rules?
Are intake and consent forms attached automatically, and have you tested that from the patient side?
Can a brand-new patient join from your reminders without calling the front desk?
Do your note templates capture consent, location, modality, and time every time?
Does your team know what to do when video fails, and is that documented?

Sort every item above into “yes, consistently,” “we kind of do this,” and “we do not.” The middle pile is where time, money, and morale leak out, and it is your roadmap.

The end state is not exciting. It is a telehealth day that feels like any other clinic day: staff know how visits are booked, prepped, and closed; providers move from patient to patient without hunting for links; billing flows predictably; and if someone asks you to prove what happened last month, you can. ChARM supports that only if the workflows are designed with the same care you use everywhere else.

Optimizing Telehealth Workflows in ChARM EHR

TL;DR

ChARM Telehealth Done Right: A Working Checklist

1. Define One Telehealth Operating Model, Not Five