Telehealth in family medicine: video visit workflows

The clinic waiting room is half-empty on a Tuesday afternoon — not because patients stopped needing care, but because half of them are at home, sitting in their kitchens, waiting for a video link to connect them to the same physician who used to see them in person. Telehealth did not arrive in family medicine gently; it arrived in a pandemic-driven avalanche that forced every clinic in the country to figure out, in a matter of days, how to deliver care through a screen. Years later, the dust has settled, and what remains is a hybrid reality: some visits belong in person, some belong on video, and some belong in the gray zone in between. The clinics that thrive in this new landscape are not the ones with the most expensive technology — they are the ones that have thought through the workflows that make telehealth efficient, safe, and satisfying for both patient and physician. Building those workflows is not a one-time project; it is an ongoing process of refinement that touches every part of the practice, from the front desk to the billing department to the exam room that is now a webcam on a desk.

Why telehealth is not just a shorter in-person visit

The most common mistake practices make when adopting telehealth is treating the video visit as a truncated version of the office visit. The assumption is that everything works the same — scheduling, rooming, documentation, billing — just with a camera instead of a stethoscope. This assumption produces workflows that are clunky, frustrating, and financially underperforming. The video visit is a different clinical encounter with different requirements, different opportunities, and different limitations — and the workflow must be designed for the medium, not retrofitted from the in-person template.

The differences begin before the visit starts. An in-person visit requires the patient to travel, park, check in, and wait in a room — a process that eats 30 to 60 minutes of the patient's time before the physician even enters. The video visit eliminates the travel but introduces a new variable: technology readiness. Does the patient have a smartphone? Does the patient know how to join the video platform? Is the internet connection stable? Is the lighting adequate for the physician to assess the patient's appearance? These questions must be answered before the appointment — not at the moment the visit is supposed to begin, when a technology failure turns a 20-minute slot into a 45-minute troubleshooting session.

During the visit, the differences continue. The physical exam — the cornerstone of in-person medicine — is limited to what the patient can demonstrate and the physician can observe through a screen. The physician cannot listen to the heart, palpate the abdomen, or assess reflexes — but the physician can observe gait, facial expression, skin color, respiratory effort, and the patient's home environment in a way that the exam room never reveals. The video visit shifts the clinical emphasis from the physical exam to the history, the visual assessment, and the shared decision-making conversation. Workflows that do not account for this shift — that try to replicate the in-person exam checklist on video — produce visits that feel incomplete to both physician and patient.

After the visit, the differences extend to documentation, billing, and follow-up. The documentation for a telehealth visit includes consent, modality (audio-video vs. audio-only), patient location at the time of service, and technology used — elements that do not exist in in-person documentation. The billing rules are different, the coding options are different, and the reimbursement rates vary by payer and by state. The follow-up may involve sending the patient to a lab for bloodwork that could not be done at home, arranging a device for remote monitoring, or scheduling an in-person visit for a hands-on exam that the video visit could not replace.

Determining which visits belong on video and which do not

Not every visit translates to telehealth, and one of the most important workflow decisions a practice makes is defining which visit types are appropriate for video and which require in-person care. This decision is not static — it evolves as the practice gains experience, as technology improves, and as patient comfort with virtual care grows. The goal is not to maximize telehealth volume but to match each visit to the modality that delivers the best care most efficiently.

The visits that work best on video are those where the clinical decision depends primarily on the history and visual assessment, where the physical exam is either unnecessary or can be patient-assisted, and where the logistics of an in-person visit add burden without value. Medication management for chronic conditions — hypertension, diabetes, hypothyroidism, depression — is ideal for video when the patient has home blood pressure readings, glucose data, or symptom self-reports. Results review — lab results, imaging reports, pathology — is efficient on video because the discussion is the visit, not the exam. Behavioral health integration — therapy sessions, medication titration for anxiety or depression, motivational interviewing for lifestyle change — translates well to video because the therapeutic conversation is the intervention.

The visits that do not work on video are those where the physical exam is essential to the clinical decision, where procedures are needed, where the patient's technology or cognitive limitations prevent effective video communication, and where the complexity of the presentation requires hands-on assessment. A new breast lump, acute abdominal pain, a suspected fracture, a skin lesion that needs biopsy, a pediatric ear exam — these are in-person visits regardless of how sophisticated the telehealth platform is.

Building the pre-visit workflow: the hidden engine of telehealth efficiency

The efficiency of a telehealth program is determined before the video connection is ever made. The pre-visit workflow — the sequence of steps that prepares the patient and the physician for the virtual encounter — is where most practices lose time, lose patients, and lose money. A video visit that starts 15 minutes late because the patient could not connect, or that is canceled because the patient's insurance does not cover telehealth, or that is downcoded because the physician did not document consent, is a failure of the pre-visit workflow — not of the visit itself.

The pre-visit workflow has four components: scheduling and triage, technology verification, insurance verification, and patient preparation. Each component must be designed, staffed, and standardized — not left to the physician to manage between patients.

To understand how a well-designed telehealth pre-visit workflow operates, it helps to examine each step and the role responsible for it.

The pre-visit workflow should be staffed by roles other than the physician — because every minute the physician spends troubleshooting technology or verifying insurance is a minute of clinical capacity lost. The medical assistant or telehealth coordinator is the linchpin of the workflow: this person conducts the technology check, confirms the patient's readiness, and ensures that when the physician joins the video, everything is in place for a productive encounter. Practices that assign this role to the physician produce burned-out physicians and inefficient telehealth; practices that invest in dedicated telehealth support produce visits that run on time and feel professional.

The technology stack: what you need and what you do not

The telehealth technology stack has three layers: the video platform, the remote monitoring infrastructure, and the integration with the electronic health record. Each layer must function reliably, and the weakest layer determines the quality of the experience — a superb video platform that does not integrate with the EHR produces duplicate documentation; an EHR-integrated platform that drops connections produces frustrated patients.

The video platform is the most visible layer and the one that patients interact with directly. The platform must be accessible without requiring the patient to download an application, create an account, or remember a password — every additional step in the connection process increases the no-show rate. Browser-based platforms that launch from a text message link have the lowest barrier to entry. The platform must support group visits, screen sharing for reviewing results, and the ability for the physician to bring a second participant — a family member, an interpreter, or a specialist — into the call. Video quality must adapt to low-bandwidth environments, because rural patients on satellite internet cannot sustain high-definition streams.

Remote patient monitoring (RPM) is the second layer, and it is where telehealth transitions from a visit modality to a continuous care model. RPM uses connected devices — blood pressure cuffs, glucometers, scales, pulse oximeters, spirometers — that transmit data to the clinic between visits. The data flows into a dashboard that the care team monitors, and abnormal readings trigger alerts that prompt intervention. RPM is not the same as a patient self-reporting readings during a video visit; RPM is automated, continuous, and clinician-monitored — and it is reimbursed separately from the video visit under current Medicare and many commercial payer policies.

EHR integration is the third layer, and it is the layer that most practices underestimate. A telehealth platform that operates as a standalone system — separate from the EHR — requires the physician to document the visit twice: once in the telehealth platform and once in the EHR. This duplicate documentation is the single most common reason physicians cite for disliking telehealth. The platform must either embed within the EHR or transmit data seamlessly so that the visit note, the consent documentation, and the billing codes flow into the EHR without manual entry.

Staffing the telehealth workflow: who does what

The staffing model for telehealth is different from the in-person model, and practices that try to run telehealth with the in-person staffing template produce inefficient workflows and frustrated staff. The key difference is that telehealth shifts work from the exam room to the pre-visit preparation and the post-visit follow-up — and the staff roles must reflect this shift.

Several staff roles are essential to a well-functioning telehealth program, and each role's responsibilities must be clearly defined.

Before designing the telehealth staffing model, practices should map out the specific roles and responsibilities that make virtual care work.

Essential staff roles for a telehealth workflow:

• Telehealth coordinator (medical assistant or dedicated staff) — conducts the 24-to-48-hour technology check, confirms patient readiness, troubleshoots connection issues on the day of the visit, and manages the audio-only fallback. This role is the difference between a telehealth program that runs on time and one that runs 20 minutes behind.
• Scheduler with telehealth training — understands which visit types are appropriate for video, knows the payer-specific telehealth rules, and books the visit in the correct slot type with the correct flags in the EHR. A scheduler who books a video visit for a complaint that requires an exam creates a wasted slot and a frustrated patient.
• Billing specialist with telehealth expertise — verifies telehealth coverage before the visit, applies the correct modifiers and place-of-service codes, and tracks denials to identify patterns. Telehealth billing is more complex than in-person billing because the rules vary by payer, by state, and by visit modality — and a billing specialist who does not understand the nuances will leave revenue on the table.
• Physician or advanced practice provider — conducts the visit, but with a modified workflow: joins the video after the medical assistant has roomed the patient virtually, reviews the pre-visit data, and documents with telehealth-specific elements (consent, modality, patient location).
• Care manager or nurse care coordinator — monitors the RPM dashboard, reviews incoming device data, triages alerts, and contacts patients with abnormal readings. This role is essential for RPM programs because the data volume exceeds what a physician can monitor between visits.
• IT support liaison — serves as the point of contact for technology issues that the telehealth coordinator cannot resolve. This may be an internal IT staff member or a vendor support contract — but there must be a identified person who can be reached when the platform fails mid-visit.

These roles do not necessarily require additional headcount — in many practices, existing staff take on telehealth-specific responsibilities within their current roles. The medical assistant who rooms patients in person can conduct the virtual rooming; the billing specialist who verifies in-person coverage can verify telehealth coverage with additional training. What matters is that the responsibilities are explicitly assigned, trained, and held accountable — not absorbed into the general workflow without definition.

The virtual rooming process: replicating the in-person encounter prep

In an in-person visit, the medical assistant rooms the patient: takes vitals, reconciles medications, updates the problem list, confirms the visit agenda, and prepares the patient for the physician. This rooming process is so ingrained that practices do not think about it — it just happens. In telehealth, the rooming process does not happen automatically; it must be deliberately designed and executed, or the physician joins a video visit with a patient who has not had their blood pressure checked, whose medication list is outdated, and who does not know what they want to discuss.

The virtual rooming process should begin 24 to 48 hours before the visit, not at the time of the visit. The medical assistant calls the patient, confirms the technology is working, reviews the medication list, asks for home vitals if applicable, and confirms the visit agenda. On the day of the visit, the medical assistant joins the video first, spends three to five minutes with the patient, verifies identity and location, documents consent for telehealth, and then hands off to the physician. The physician joins a visit that is already prepared — rather than spending the first five minutes doing the rooming that should have been done before.

The virtual rooming process also includes the consent documentation that is required for telehealth. Consent must be obtained and documented for each visit — or at minimum, at the first telehealth visit and annually thereafter, depending on payer requirements. The consent includes acknowledgment that the patient understands the visit is being conducted via telehealth, that there are limitations to virtual care, and that the patient can request an in-person visit at any time. The medical assistant who documents this consent during rooming saves the physician from having to remember it during the visit — and prevents the downcoding or denial that results from missing consent documentation.

Remote patient monitoring: from data collection to clinical action

Remote patient monitoring is the component of telehealth that has the greatest potential to transform chronic disease management — and the component that is most frequently implemented poorly. RPM is not about collecting data; it is about acting on data. A practice that gives patients Bluetooth blood pressure cuffs, receives hundreds of readings per week, and does nothing with them until the next office visit has created a data cemetery, not a monitoring program.

The RPM workflow has four stages: device setup, data review, clinical action, and patient communication. Each stage must be designed, staffed, and standardized.

Device setup occurs at the time the patient is enrolled in the RPM program. The patient receives the device — by mail, at the clinic, or from a pharmacy partner — and is trained on its use. The device must be paired with the clinic's RPM platform, which requires either patient-side setup (downloading an app, connecting via Bluetooth) or clinic-side setup (pre-configuring the device before it is sent). The setup is the most labor-intensive part of RPM and the point where most patients drop out — if the setup is complicated, the patient never starts using the device.

Data review is the ongoing process of monitoring the incoming data. This is not a physician task — the physician does not have time to review 200 blood pressure readings per week. The care manager or nurse reviews the data on a defined schedule — daily for high-risk patients, weekly for stable patients — and identifies readings that fall outside the target range. The review is not about every reading; it is about trends, outliers, and alerts.

Clinical action is the response to abnormal data. The action may be a phone call to adjust medication, a message to the patient with reassurance or guidance, a scheduled video visit to discuss a trend, or an escalation to the physician for a complex case. The action must be timely — within 24 to 48 hours for most alerts, immediately for critical values — and documented in the EHR.

Patient communication closes the loop. The patient who submits blood pressure readings and hears nothing back stops submitting readings. The patient who receives a message saying "Your readings look great, keep going" continues. The feedback does not need to be detailed or clinical — it needs to be consistent, so the patient knows that someone is looking at the data and that their effort is valued.

Billing and reimbursement: navigating the telehealth coding landscape

Telehealth billing is the area where practices lose the most money — not because the reimbursement rates are low, but because the coding and documentation requirements are complex and frequently misunderstood. A telehealth visit that is coded as an in-person visit, or that is missing the required modifiers, or that is not documented with the patient's location, is a visit that will be denied — and the denial may not arrive until months after the visit, when the practice has already written off the revenue.

The billing rules for telehealth are determined by three factors: the payer (Medicare, Medicaid, commercial), the modality (audio-video or audio-only), and the patient's location (home, clinic, or other). Each combination has different requirements, and the practice's billing team must understand all of them.

For Medicare, video visits are billed using the same CPT codes as in-person visits (99202–99215 for office visits), with a modifier 95 (synchronous telemedicine) appended. Audio-only visits are billed with modifier 93, and Medicare has permanently retained audio-only coverage for a defined set of services — but the documentation must specify that audio-only was used and why (patient lacked video capability, patient declined video, connection failed). The patient's location is documented using a place-of-service code — POS 10 for the patient's home, POS 02 for other locations — and the choice of POS affects reimbursement.

Commercial payers follow Medicare's general framework but have variations. Some payers require prior authorization for telehealth; some have different reimbursement rates for video vs. audio-only; some do not cover telehealth for certain visit types. The practice's billing team must maintain a current matrix of payer-specific requirements and update it as rules change — because the telehealth regulatory landscape is not static.

RPM billing is separate from video visit billing and uses different CPT codes. RPM codes cover device setup, data review, and care management — and they can be billed monthly for patients enrolled in the program. The reimbursement for RPM can be significant — $50 to $100 per patient per month — but the documentation requirements are strict, and the practice must demonstrate that the data was reviewed and acted upon, not just collected.

Common workflow failures and how to fix them

Even well-designed telehealth workflows develop problems over time, and the practices that maintain efficient telehealth programs are the ones that regularly audit their workflows and fix the failures before they become entrenched. The most common failures fall into several categories, and each has a specific fix that restores efficiency.

Before troubleshooting a telehealth workflow, it helps to identify the most frequent failure points and the specific interventions that address them.

Common telehealth workflow failures and their solutions:

• High no-show rate for video visits — typically caused by technology barriers or lack of pre-visit contact. Fix: implement a 48-hour technology check and a 1-hour connection reminder via text message. If the no-show rate remains above 15%, offer audio-only as a default for patients who struggle with video.
• Visits running late due to technology issues — caused by patients who join the platform for the first time at the moment of the visit. Fix: require a technology check before the first video visit; provide a test link that patients can use to verify their setup independently.
• Physician burnout from documentation burden — caused by duplicate documentation in the telehealth platform and the EHR. Fix: ensure the platform is EHR-integrated so the visit note flows into the chart without manual entry; use telehealth-specific templates that include consent, modality, and location fields automatically.
• Downcoded or denied claims — caused by missing consent documentation, incorrect modifiers, or wrong place-of-service codes. Fix: build telehealth-specific charge capture into the EHR template so the modifier and POS are auto-populated; audit denials monthly to identify patterns and retrain staff.
• RPM data not being acted upon — caused by assigning data review to the physician, who does not have time. Fix: assign data review to the care manager with a defined schedule and a protocol for escalation; set alerts for readings outside target ranges so the reviewer does not have to scan every reading manually.
• Patients dissatisfied with video visits — often caused by the physician treating the video visit as a lesser encounter, rushing through without building rapport. Fix: train physicians on telehealth-specific communication skills — eye contact through the camera, verbal acknowledgment of visual cues, explicit articulation of the clinical plan since the physical exam is absent.
• Inappropriate visit triage — scheduling video visits for complaints that require physical exam, resulting in a second in-person visit. Fix: develop a triage protocol with specific complaints that are appropriate and inappropriate for telehealth; train schedulers on the protocol; review inappropriate triages monthly and provide feedback.
• Device enrollment drop-off — patients receive RPM devices but never start using them. Fix: simplify the setup process; have the medical assistant guide the patient through setup during a phone call or video visit; follow up within one week to confirm the device is transmitting data.
• Audio-only visits billed as video — caused by the physician not documenting that the connection failed and the visit was conducted by phone. Fix: train physicians to document the actual modality used, not the modality scheduled; build a prompt in the EHR that requires the physician to confirm modality before signing the note.
• Lack of patient awareness of telehealth option — patients do not know they can request a video visit, so the telehealth slots go unfilled. Fix: include telehealth as an option on the practice website, in the appointment reminder system, and in the after-visit summary; train front desk staff to offer telehealth when scheduling follow-ups for chronic disease management.

These failures are not hypothetical — they are the patterns that emerge in every practice that adopts telehealth, and the practices that address them proactively build telehealth programs that are sustainable, profitable, and clinically effective.

Telehealth communication skills: what changes when the patient is on a screen

The clinical content of a telehealth visit is similar to an in-person visit, but the communication dynamics are fundamentally different. The physician who excels in the exam room may struggle on video because the cues that guide in-person communication — body language, eye contact, physical proximity — are altered or absent in the virtual environment. Telehealth communication is a learnable skill, and practices that invest in training their physicians produce visits that patients rate as highly as in-person encounters.

Eye contact is the most obvious difference. In person, the physician looks at the patient; on video, the physician looks at the patient's image on the screen — but the camera is above the screen, so the patient sees the physician looking down. The fix is simple but unnatural: look at the camera, not the screen, when speaking. The patient perceives eye contact even though the physician is not looking at the patient's face. This takes practice, and physicians who do not practice it produce video visits that feel impersonal.

Verbal articulation replaces physical examination as the primary source of clinical information. In person, the physician palpates the abdomen and assesses tenderness; on video, the physician asks the patient to press on their own abdomen and describe what they feel. The physician must guide the self-exam verbally — "Press firmly here and tell me if it hurts more when you press or when you release" — and interpret the patient's description, which is less reliable than a direct exam. This verbal guidance is a skill that must be developed through practice.

The closing of the visit also changes. In person, the physician stands up, the patient stands up, and the visit ends with a shared physical moment of transition. On video, the visit ends with a click — abrupt, sometimes awkward. The physician who explicitly closes the visit — "Before we end, do you have any other questions? I'll send your after-visit summary through the portal, and I'll see you in three months" — creates a more natural ending and reduces the risk of the patient calling back with a question that should have been addressed during the visit.

The hybrid schedule: designing a day that includes both in-person and video visits

The most sustainable telehealth model is not all-video or all-in-person — it is a hybrid schedule that blends both modalities in a way that optimizes the physician's time and the patient's access. The design of the hybrid schedule is a workflow decision that affects everything from room utilization to staff allocation to physician satisfaction.

The two most common hybrid models are the block model and the integrated model. In the block model, the physician has dedicated telehealth blocks — for example, Monday and Wednesday mornings are video visits, and the rest of the week is in-person. This model is simple to schedule and staff, but it reduces flexibility — a patient who needs a video visit on Thursday has to wait until the following Monday. In the integrated model, video and in-person visits are interleaved throughout the day — the physician sees an in-person patient, then a video patient, then an in-person patient. This model is more flexible but requires more sophisticated scheduling and can create context-switching fatigue for the physician.

The block model works best for practices with high telehealth volume and dedicated telehealth staff. The integrated model works best for practices where telehealth is a smaller portion of the schedule and where the physician moves between modalities without significant workflow disruption. The choice depends on the practice's patient population, the payer mix, and the physician's preference — and it should be revisited regularly as telehealth volume evolves.

Measuring telehealth success: metrics that matter

A telehealth program that is not measured is a telehealth program that cannot improve. The metrics that matter for telehealth are not the same as the metrics for in-person care, and tracking the right indicators is what allows the practice to identify problems and demonstrate value to payers and leadership.

The core telehealth metrics fall into four categories: access, efficiency, quality, and financial. Access metrics include the percentage of visits conducted via telehealth, the no-show rate for video vs. in-person visits, and the time to third-next-available appointment for video vs. in-person. Efficiency metrics include visit length, on-time start rate, and the number of visits per session. Quality metrics include patient satisfaction scores for telehealth visits, the rate of follow-up needed after a video visit (a high rate suggests the video visit did not fully address the problem), and the rate of inappropriate triage. Financial metrics include telehealth revenue per visit, denial rate for telehealth claims, and the cost per telehealth visit (including technology, staffing, and device costs).

Tracking these metrics monthly — not annually — allows the practice to identify trends early and intervene before small problems become structural. A rising no-show rate for video visits may indicate that the technology check process has degraded; a rising denial rate may indicate that a payer has changed its telehealth policy; a rising follow-up rate may indicate that the triage protocol is sending the wrong visit types to video. Each metric tells a story, and the practice that reads the stories can adjust the workflow before the metrics become failures.

The future of telehealth in family medicine

Telehealth is not a temporary adaptation — it is a permanent component of family medicine that will continue to evolve. The technologies will improve: better integration, AI-assisted documentation, wearable devices that transmit more data with less patient effort. The regulatory landscape will stabilize as temporary pandemic-era waivers are made permanent or replaced with new frameworks. The reimbursement picture will clarify as payers and providers reach consensus on the value of virtual care.

But the fundamentals will not change. Telehealth works when the workflow is designed for the medium, when the staff is trained and roles are defined, when the technology supports rather than hinders the clinical encounter, and when the physician communicates with the same skill and compassion through a screen as in an exam room. The practices that master these fundamentals will offer their patients something that was not possible a decade ago: access to their family physician without leaving home, continuity of care without the barrier of distance, and a clinical relationship that adapts to the patient's life rather than demanding the patient adapt to the clinic's schedule. That is the promise of telehealth in family medicine — and building the workflows that deliver it is the work that matters now.