Specialty rankings are useful until somebody treats them like a launch plan. A high virtual-visit share for mental health does not tell you whether your intake can route acuity, whether support can see case status, or whether a provider has a safe escalation path. A low virtual-visit share for wound care does not mean the category has no virtual workflow. It may mean the virtual work sits around the in-person step, not instead of it.
Epic Research analyzed 475,229,277 encounters from Q2 2019 through Q3 2023. Its interactive chart reports the five highest Q3 2023 telehealth shares as mental health (36.8%), infectious disease (10.6%), obstetrics (10.0%), transplant (9.9%), and neurology (9.5%). ENT (1.7%), orthopedics (1.1%), ophthalmology (0.6%), wound care (0.2%), and podiatry (0.2%) were the five lowest. OpenLoop’s March 28, 2024 article turned that chart into a high-five and low-five list.
Those numbers are a Q3 2023 utilization snapshot, not a current 2026 ranking and not a clinical-suitability score. The article keeps the original slug for queue continuity, but the copy does not present old encounter data as today’s market order.
This guide is not legal, clinical, billing, or compliance advice. Specialty scope, prescribing rules, licensure, escalation paths, privacy review, and in-person referral rules need review by the teams responsible for them. Use this as a platform checklist before a telehealth launch or replacement project.
Table of contents
This guide explains what specialty rankings can and cannot tell you, how to evaluate the five high-use categories, what lower-use categories still need from virtual workflows, which vendor questions to ask before launch, where Remedora fits, and how to avoid turning a ranking table into a weak operating plan.
Specialty utilization is not platform readiness
A telehealth ranking usually measures use. It does not measure workflow difficulty.
That distinction matters. Mental health may have a high share of virtual visits because many sessions can happen remotely. But the operating load still includes eligibility rules, provider matching, repeat visits, patient privacy, crisis escalation, payments, documentation, and support. If those parts live in separate tools, a high-fit specialty can still become a hard launch.
The opposite is also true. Podiatry, wound care, and ophthalmology may have low virtual-visit shares because they often need physical exams, imaging, procedures, measurements, or hands-on treatment. But those categories may still use virtual workflows for triage, follow-up, education, remote monitoring, second opinions, status updates, and support coordination.
A telehealth platform should be evaluated around the work that happens before, during, and after the virtual encounter. Video is one piece. The platform also needs intake logic, routing, provider queues, payment state, prescribing or order workflows when they apply, partner handoffs, support visibility, role-based access, and audit history.
If the platform cannot carry those states, staff become the integration layer. That works for a pilot. It gets ugly after volume arrives.
What the 2023 encounter data can tell you
The Epic chart is useful because it separates specialties with different virtual-care shapes. Mental health is not infectious disease. Transplant care is not neurology. ENT is not wound care. Each category can create a different set of patient-selection rules, provider handoffs, data requirements, and post-visit work.
The source list also forces a good buyer question: are you choosing a specialty because the market says it is popular, or because your team can operate the workflow safely?
That question should come before vendor demos. A polished demo path can make any specialty look easy. The launch plan needs to show the awkward cases: a patient who should be redirected, a provider who needs clarification, a prescription or order that is blocked, a payment that fails, a partner system that does not update, and a support ticket where the agent needs status without opening unrestricted clinical detail.
High-use specialty 1: mental health needs continuity and escalation design
HHS says telehealth remains widely used for behavioral health and can support individual therapy, group therapy, substance-use treatment, and integrated behavioral and primary care. That does not make the platform simple.
The intake flow needs to do more than collect a name, state, and preferred appointment time. It may need age rules, acuity screening, consent, care-type selection, provider-type matching, medication history, emergency instructions, and safety-routing logic. The exact workflow depends on the program. The buyer should still ask where each decision lives.
Mental health also puts pressure on continuity. If a patient has repeat visits, medication questions, missed appointments, provider changes, or support issues, the team needs a shared record of status and ownership. A scheduling tool can book the session. It may not show whether the patient is waiting on outreach, provider review, payment, refill clarification, or escalation.
Demo this with an uncomfortable case. A patient completes intake but gives an answer that should not move into a standard appointment path. What happens? Who sees it? What does the patient receive? What can support see? What gets logged? If the answer is “the team handles that manually,” the platform is not carrying the risk the specialty creates.
High-use specialty 2: infectious disease workflows depend on triage and isolation context
HHS lists infections, medication management, lab or imaging review, and post-surgical check-ins among uses that may fit telehealth. Infectious-disease programs can also create bad patient expectations if the workflow does not make boundaries clear.
The platform should separate low-acuity virtual paths from cases that need urgent in-person evaluation, testing, procedures, isolation instructions, public-health reporting, or specialist escalation. The patient should not have to guess. Support should not have to invent the rule during a live chat.
This category also tests communication discipline. A patient may be waiting on a test result, treatment instruction, provider message, pharmacy status, or follow-up window. The platform should show which owner has the next action and which information can safely appear in patient messages.
For teams comparing vendors, ask for the quarantine or exposure scenario. Then ask for the failed scenario: the patient reports a red-flag symptom, chooses the wrong path, or needs redirection after intake. The platform should stop, route, or escalate the case according to the care model the clinical team approved.
High-use specialty 3: obstetrics needs clear boundaries around remote and in-person care
Obstetrics is a good example of hybrid care. The HHS maternal telehealth guide covers high-risk pregnancy support, postpartum care, and maternal mental health, while leaving clinical teams to define what still requires local or in-person care. The danger is treating virtual convenience as if it removes those boundaries.
A telehealth platform supporting OB-related workflows needs strong patient instructions, careful intake, state and provider routing, role visibility, and escalation design. It also needs to avoid turning support into clinical interpretation. A patient asking about symptoms, blood pressure readings, fetal movement, medication, or postpartum concerns may need a clearly defined path, not a generic support answer.
The operating question is whether the platform can show the right context to the right role. A provider needs clinical detail. Support may need status, next step, owner, and safe scripts. Operations needs queue health, exceptions, and handoff visibility. Compliance and leadership need evidence of access controls and audit history.
Before launch, walk through a normal prenatal check-in, a postpartum support question, a missing reading, and a symptom that should not stay virtual. If those paths all look the same in the system, the workflow is too flat.
High-use specialty 4: transplant care creates frequent follow-up and fragile handoffs
Transplant care is not a simple consumer telehealth category. Epic’s utilization figure says only that 9.9% of encounters in its Q3 2023 dataset were virtual. It does not establish which transplant services belong online or whether a general telehealth vendor has the specialist network to deliver them. Clinical leadership has to define the allowed visit types, local escalation path, medication and lab ownership, and referral boundaries.
For platform evaluation, focus on handoffs and visibility. Can the case show what the patient is waiting on? Can lab or partner status attach to the right workflow? Can support answer operational questions without seeing more clinical information than its role requires? Can a provider request clarification and get the updated case back in the right queue?
This is also where partner systems become visible. A transplant-related workflow may depend on labs, pharmacies, specialty providers, care coordinators, or external records. If those systems do not update the platform, staff will chase status manually.
Ask the vendor to show a blocked follow-up case. Not the clean visit. Show the patient who needs an outside result, the provider who needs one more detail, the partner delay, and the support ticket asking what is happening. The answer will reveal whether the platform manages the workflow or only hosts the interaction.
High-use specialty 5: neurology needs data, follow-up, and escalation ownership
Neurology can include follow-up care, medication management, chronic-condition check-ins, specialist access, telestroke support, rehab coordination, and review of patient-reported data. Some use cases fit virtual care well. Others require in-person testing, imaging, emergency evaluation, or specialist intervention.
The platform should not blur those paths. Intake needs to identify urgent symptoms and stop the wrong virtual path early. Follow-up workflows need provider context. Patient-reported data should land somewhere a clinician or care team can review according to the program’s rules. Support needs safe status visibility, not a blank dashboard and a Slack thread.
Neurology also exposes a common platform gap: the visit is documented, but the next step is not owned. A patient may need a medication change, referral, rehab instruction, data upload, follow-up appointment, or urgent redirection. If those states are invisible, the team can still work the case, but only through manual cleanup.
A good demo script includes a routine follow-up, a concerning intake answer, a missed data upload, and a patient question after the visit. Each one should have a state, owner, patient message, and audit trail.
Lower-use specialties are not automatic no-go categories
A low virtual-use share usually means the specialty has more physical-world dependency. It does not mean the category has no telehealth value.
ENT and orthopedics often need exams, imaging, procedures, range-of-motion checks, or hands-on treatment. Ophthalmology may need device-based exams, imaging, measurements, and urgent triage rules. Wound care and podiatry may need high-quality images, in-person debridement, offloading decisions, measurement, infection checks, or local treatment.
The virtual opportunity may sit around the clinical encounter. Depending on the service line, that can include intake, photo collection, post-procedure follow-up, education, escalation routing, medication or supply coordination, and support updates. Clinical leaders still need to decide when the patient must move to local or in-person care.
The mistake is forcing a high-use specialty playbook onto a lower-use category. A mental health style scheduling flow will not solve wound-image review. A general urgent-care intake may not work for foot ulcers, post-op orthopedic questions, vision complaints, or ENT red flags. The platform needs the care model’s boundaries, not a generic virtual-care form.
What to test before launching any specialty
Build the evaluation around patient scenarios, not feature names. A vendor can say it has intake, messaging, payments, APIs, and dashboards. The useful question is how those parts behave when the specialty gets messy.
Intake logic
- Ask: Which answers route, stop, escalate, or request more information?
- Why it matters: Specialty fit starts before provider review.
Provider queue
- Ask: Which provider type, state, credential, schedule, and backup owner receive the case?
- Why it matters: Coverage on paper is not usable capacity.
Visit mode
- Ask: Does the workflow support async, synchronous, hybrid, or referral-based care?
- Why it matters: Different specialties fail in different visit modes.
Post-visit work
- Ask: What happens after approval, decline, no-show, clarification, referral, order, or prescription?
- Why it matters: Patients judge the full journey, not the visit alone.
Support visibility
- Ask: What can support see without unrestricted clinical access?
- Why it matters: Status questions should not become clinical-record scavenger hunts.
Partner handoff
- Ask: Where do labs, imaging, pharmacy, fulfillment, or external referrals update the case?
- Why it matters: Partner delays need owners and patient communication.
Compliance evidence
- Ask: Can the team review roles, access, consent, audit logs, vendor responsibilities, and message history?
- Why it matters: Compliance review depends on workflow evidence, not only policies.
Change control
- Ask: How fast can operations change intake, routing, messages, or escalation rules after launch?
- Why it matters: Specialty workflows change after real patients expose edge cases.
Run the table against at least five cases. Include an eligible patient, an ineligible patient, incomplete intake, provider clarification, failed payment, partner delay, support escalation, and a case that should move to in-person care. A platform that only handles the first case is not ready for launch.
Where Remedora fits
Remedora currently positions itself as an all-in-one platform for branded health businesses, with a storefront, intake, an included provider network, e-prescribing, pharmacy fulfillment, payments, and support on one ledger. That is relevant when the proposed service line fits Remedora’s clinical and pharmacy scope. This article does not claim that Remedora supports every specialty in the Epic chart. Buyers should confirm provider coverage, protocols, visit mode, prescribing scope, and escalation requirements for the exact care model.
This is where patient intake software matters. Specialty intake is not a generic questionnaire. It can collect eligibility information, route by state or service line, keep incomplete cases out of provider queues, ask for missing details, and create the first record support and clinical teams can trust.
Remedora’s current telehealth API and webhooks page says the product does not offer a general REST API. It provides signed, retried webhooks for defined intake, provider, prescription, shipment, and billing events. That may be enough when internal systems only need to react to those events. A program that needs arbitrary data access, write operations, or specialty-specific integrations should confirm the fit before buying.
A narrow video or scheduling tool may be enough for a clinic that already has intake, documentation, prescribing, support, compliance evidence, and follow-up handled elsewhere. OpenLoop or another services-heavy vendor may fit teams that want outsourced clinicians, credentialing, payer work, RCM, legal operations, or practice management. Remedora fits when the service line is in scope and the buyer wants the branded commerce and care journey on one operating ledger.
Common mistakes when using telehealth specialty rankings
The first mistake is treating popularity as proof of fit. A specialty can be popular virtually and still require difficult intake, provider matching, escalation, and follow-up design.
The second mistake is ignoring the lower-use categories. A specialty with low virtual-visit share may still have useful virtual workflows around triage, education, review, and follow-up. The platform has to support that narrower shape instead of pretending every case is a full virtual replacement.
The third mistake is buying for the visit instead of the work around it. In most specialty launches, the failure points are incomplete intake, unclear ownership, payment or refund questions, prescriptions or orders, partner delays, support visibility, and compliance evidence.
The fourth mistake is letting every exception become a human workaround. Workarounds feel flexible early. Later they become private knowledge, duplicate documentation, slow support answers, and risk the team cannot audit.
Vendor questions for specialty telehealth demos
Use demo questions that force the platform to show workflow state. Slides about specialty access are not enough.
Show a patient who should not continue virtually
A good answer should show the platform stopping, routing, or escalating the case with clear patient instructions and an auditable record.
Show incomplete specialty intake
A good answer should show the case staying out of the wrong queue, requesting the missing detail, and giving support accurate status.
Show provider clarification and patient response
A good answer should show the response returning to the same case with its context intact.
Show a prescription, order, lab, imaging, or fulfillment delay
A good answer should show the patient message, support view, provider queue, and partner status without conflicts.
Show a support agent answering a status question
A good answer should show support the safe operational state without unrestricted clinical-note access.
Show an intake or routing change two weeks after launch
A good answer should show operations changing the workflow without breaking reporting, audit history, or patient messaging.
If the vendor cannot demo messy cases, assume the team will solve them manually. That may be acceptable for a narrow pilot. It is not a strong plan for a branded telehealth business that expects volume.
FAQ
What are the most popular specialties for telehealth?
In Epic Research’s Q3 2023 encounter data, the five highest telehealth shares were mental health, infectious disease, obstetrics, transplant, and neurology. Those figures are historical utilization rates, not a current popularity poll or a clinical recommendation. Each category still needs its own intake logic, provider routing, escalation rules, support visibility, and post-visit workflow.
What are the least popular specialties for telehealth?
Epic’s Q3 2023 chart placed ENT, orthopedics, ophthalmology, wound care, and podiatry at the bottom of the measured specialties. Epic says the sub-1% rates for ophthalmology, podiatry, and wound care likely reflect the hands-on nature of the care. The ranking does not decide which virtual triage, follow-up, or support workflows are clinically appropriate.
Should a telehealth startup only launch high-use specialties?
No. High-use categories may have stronger virtual-care fit, but they can still be operationally hard. Lower-use categories may have narrower but useful virtual workflows. Start with the care model, patient-selection rules, provider coverage, escalation paths, payment flow, prescribing or order needs, support plan, and compliance review.
How should operators compare telehealth specialties before launch?
Map patient scenarios before comparing platforms. Include eligible patients, ineligible patients, incomplete intake, provider clarification, urgent redirection, payment failure, partner delay, and support escalation. Then ask each vendor to show those cases inside the platform. A clean demo path is not enough.
Can a video visit tool support specialty telehealth?
Sometimes. A video tool can work when an existing clinic already handles intake, routing, documentation, prescribing, support, follow-up, and compliance evidence elsewhere. It is weaker for digital health brands that need the platform itself to coordinate the patient journey, especially when prescriptions, orders, fulfillment, or partner systems are involved.
Where does Remedora fit in a specialty telehealth launch?
Remedora fits when the service line is within its provider and pharmacy scope and a branded health business needs connected intake, review, payments, prescriptions, fulfillment, and support. It is less necessary for a clinic that only needs a virtual appointment layer. Buyers with specialty-specific integrations or a broad REST API requirement should confirm the current product boundary before choosing it.
Sources reviewed
- Epic Research’s telehealth utilization study supplies the 475,229,277-encounter dataset, Q3 2023 percentages, and historical limits.
- OpenLoop’s 2024 specialty article supplied the market framing and shows where its managed-services model differs from a software-led evaluation.
- HHS’s behavioral health guide supports the discussion of virtual behavioral care models.
- HHS’s maternal health guide supports the hybrid pregnancy and postpartum discussion.
- HHS’s patient telehealth guide provides current examples of care that may occur through telehealth and tells patients to confirm fit with their provider.
Related resources
- Start with Remedora if your specialty launch needs connected intake, review, payment, support, prescribing, fulfillment, and integration state in one operating workflow.
- Use the telehealth platform page to compare specialty workflows against the full patient journey, not only video-visit access.
- Read the patient intake software page before building eligibility, acuity, missing-information, or state-specific routing paths.
- Review Remedora’s webhooks to see the defined event model and the current no-REST-API boundary.
- Check the telehealth psychiatry page for a narrower behavioral-health workflow example.
- Use the remote patient monitoring software page when the care model depends on data collected between encounters.
- Compare the service model on the OpenLoop alternative page if staffing, licensing, credentialing, or RCM are central requirements.
Talk with Remedora
Talk to Remedora about whether the proposed service line fits its provider, pharmacy, intake, and workflow scope. Bring the cases that require local referral, specialist escalation, missing data, or a partner handoff. Those are the cases the platform has to carry before patients arrive.
