Barriers to telehealth are the reasons a patient who could benefit from a virtual visit never joins one, or joins and gives up. Most are practical: a weak connection, an old phone, an unfamiliar app, a visit offered only in English, or a screen that does not work with assistive technology.
This guide looks at those barriers from the patient's side, explains what causes each one, and sets out the design and operations choices that remove it. It ends with a barrier audit that a telehealth team can run against its own service.
What are the main barriers to telehealth for patients?
Designing a telehealth service more patients can use?
Agnotic builds telemedicine platforms with low-bandwidth modes, audio fallback, language support and accessible screens.
The main barriers to telehealth for patients are unreliable or unaffordable internet, no suitable device, limited confidence with apps, care offered in a language the patient does not read or speak well, screens that do not work for people with disabilities, and doubts about privacy or cost. Each barrier needs its own design fix.
Barriers stack. An older patient on a prepaid phone plan in a rural area may face four of them at once. Fixing one, such as adding an interpreter, does little if the visit link still fails on that patient's connection, so teams get the best results by testing the whole journey with the patients they serve.
The barriers are also measurable. Invitations sent, links opened, waiting rooms joined, visits completed and visits switched to phone each show where patients drop out, and that funnel is the starting point for every fix in this guide.
How does broadband limit telehealth access?
Broadband limits telehealth when a patient's connection is slow, unstable, capped or shared, and video freezes or drops. The FCC's 2024 Section 706 report raised its fixed broadband benchmark to 100 Mbps download and 20 Mbps upload, and many households still rely on mobile data or older fixed service instead.
A video visit does not need a benchmark-speed line, but it does need a steady one, and upload speed matters because the patient's camera sends video too. Patients on mobile data also worry about using up a monthly allowance.
- Adaptive video: Use a video stack that lowers resolution and frame rate when the connection weakens, instead of freezing.
- Pre-visit test: Offer a connection check before the appointment, with plain advice such as moving closer to the router.
- Audio fallback: Let the clinician switch to a phone call in one step when video fails, with the patient's callback number confirmed at check-in.
- Light pages: Keep the join page small, with no large images or scripts, so it loads on weak mobile signals.
- No-install join: Let patients join from a browser link, so they do not have to download a large app over mobile data.
Audio-only is not a lesser fallback for every patient. For some, it is the only option that works, and Medicare allows it in limited home cases when the patient cannot use or does not want video. The platform should record the reason so billing and quality reports stay accurate.
What if the patient has no suitable device?
When a patient has no suitable device, the service has three options: support the device they have, lend one, or bring the visit to a place that has one. Most services need all three for different patients.
Supporting older devices is the cheapest fix. Test on older phone operating systems, small screens and low-memory devices, and keep the browser join path working on them. A visit that fails because the app needs the newest phone excludes exactly the patients telehealth was meant to reach.
- Shared devices: Many patients borrow a family member's phone, so the visit link should not depend on the patient being logged in to an app on that device.
- Loaner programs: Tablets lent for remote monitoring or long courses of care need device management, preloaded apps and a return process.
- Community sites: Libraries, clinics and community centers can host private rooms with a device and a connection.
- Assisted visits: A staff member or community health worker sets up the device at the patient's home and steps back once the visit starts.
Digital literacy and the first visit
Digital literacy is the patient's confidence and skill with apps, links, logins, cameras and microphones. The first visit is where it matters most, because a patient who fails once often does not try again.
Reduce the number of steps. Every extra screen, password or permission prompt loses some patients. A one-time link sent by text, which opens a browser page asking for camera and microphone access with a clear picture of what to tap, is easier than an account, an app download and a password reset.
Offer a human backup. A short practice call with a staff member before the first visit, or a phone number on the waiting screen that reaches a person, solves problems that no help article will. Track which step patients get stuck on, and fix that step in the product rather than in the script.
Write for the reader. Instructions should use short sentences, plain words, large buttons and pictures of the actual screens. Test them with patients who are not comfortable with technology, not with the project team.
How should a telehealth service handle language access?
A telehealth service should offer interpreters and translated materials for patients with limited English proficiency from scheduling through the visit and follow-up. Under Section 1557, 45 CFR 92.201 requires covered entities to take reasonable steps to provide meaningful access, and critical machine-translated text must be reviewed by a qualified human translator.
- Language at booking: Capture the patient's preferred language when the visit is scheduled, so an interpreter is booked before the visit starts.
- Interpreter in the call: Let an interpreter join the video or audio call as a third party, with their identity recorded in the visit log.
- Translated messages: Send reminders, join instructions and after-visit summaries in the patient's language.
- Interface language: Translate the join page and waiting screen, and test that longer translated words do not break the layout.
- Human review: Have qualified translators review machine-translated clinical text before it reaches patients.
Family members are a common but poor substitute for interpreters, especially children. The platform can make the professional option easier than the shortcut by putting the interpreter request in the booking flow, not in a separate phone call.
Which accessibility needs come up in video visits?
Video visits raise accessibility needs for patients who are deaf or hard of hearing, blind or low vision, or who have motor or cognitive disabilities. Providers that receive HHS funding must meet WCAG 2.1 Level AA on their websites and apps under the HHS Section 504 rule, and the deadline is 11 May 2027 for organizations with 15 or more employees, or 10 May 2028 below that size.
- Hearing: Captions for the call, a chat panel, and support for sign language interpreters joining as a separate video feed.
- Vision: Screen reader labels on every control, keyboard access, enough color contrast and no information shown by color alone.
- Motor: Large targets, no time limits on forms, and controls that work with switch devices and voice control.
- Cognitive: Simple wording, one task per screen and a clear indication of what happens next.
Accessibility is cheapest in the design system, before screens multiply. Automated checks catch some issues, but testing with screen reader users and keyboard-only navigation catches the ones that stop a patient from joining.
Trust, privacy and cost worries
Some patients have the connection, the device and the skills, and still decline video. Common reasons are doubt that a remote visit is real care, worry about who can see or hear the call, and uncertainty about what the visit will cost.
Each worry has a product answer. Show the clinician's name, photo and credentials before the visit. Explain in one sentence how the call is protected and that it is not recorded unless the patient agrees. State the expected cost or coverage on the booking screen, and say what happens if the clinician decides the patient needs to be seen in person.
Trust also builds through follow-through. An after-visit summary that arrives the same day, a prescription that reaches the pharmacy and a referral that is actually booked tell the patient the visit counted.
A barrier audit for telehealth teams
Run this audit against the live service with real patient journeys, not a demo account. Each line names a barrier and the check that shows whether it has been removed.
- Connection: Join and complete a visit on a weak mobile signal, and confirm video degrades instead of dropping.
- Fallback: Switch a live visit to audio-only in one step, with the reason recorded.
- Old devices: Join from an older phone and a small screen through the browser link.
- First join: Count the steps and taps from reminder text to seeing the clinician, then remove any that are not needed.
- Human help: Reach a person from the waiting screen within the time patients will wait.
- Language: Book a visit in another language and confirm the interpreter, reminders and summary all follow.
- Accessibility: Complete the full journey with a screen reader and with keyboard only.
- Privacy prompt: Confirm patients are asked whether they can speak privately before sensitive questions.
- Funnel data: Report invitations, joins, completions and phone switches by patient group, so gaps show up.
How Agnotic can help
Removing barriers is mostly product and integration work that has to be planned from the first sprint. Agnotic Technologies builds telemedicine platforms for clients with adaptive video and audio fallback, browser-based joining, interpreter booking in the scheduling flow, translated patient messages, accessible screens and funnel reporting by patient group.
The client's clinical and community teams know which patients are being missed. Agnotic turns that knowledge into tested journeys, so each fix can be measured in the join and completion data.
Build a telehealth service that reaches more patients
See how Agnotic designs telemedicine platforms for patients on weak connections and older devices, or browse the HL7 hub.
Related reading on Agnotic
Continue with provider-side telehealth risks, federal requirements, Florida law, telemedicine apps and home health telehealth.
