Types of Telehealth and How to Choose a Care Model
Compare types of telehealth, including live consultations, asynchronous care, remote monitoring and hybrid delivery, with guidance for US and Canadian services.
Table of Contents▼

Muhammad Bin Habib
AuthorChief Growth Officer
Chief Growth Officer at Launch Flow Inc. An elite organic growth architect and revenue operator with a pedigree of scaling market-leading digital enterprises to $40M+ ARR. Having served as Head of Organic Growth across category-defining innovators including Tekrevol, Qordata, Imagine.Art, and Chatly.ai, Muhammad engineers proprietary demand-generation flywheels, high-barrier SEO moats, and institutional customer acquisition infrastructure.
A telehealth platform can accept messages and home readings before the organisation has agreed who reviews them or how quickly patients should expect a response.
Choosing the care model resolves those responsibilities. It establishes how patients participate, when clinicians provide input and what happens when remote care cannot complete the service.
The main approaches involve live interaction or information reviewed later. Remote patient monitoring and combinations of virtual and in-person care introduce additional operating requirements.
This guide explains those relationships and helps you choose a starting model for a service in the US or Canada before selecting software.
Key Takeaways
The care model should describe the service patients receive and the work your team is prepared to perform.
- Distinguish communication methods from specialties, software products and deployment choices.
- Compare live interaction with information submitted for later review.
- Define staffing, response windows and escalation before introducing asynchronous services.
- Include review responsibilities and device support when assessing remote monitoring.
- Explain how patients move between remote and in-person care.
- Translate the chosen model into requirements before approving development.
Planning a Custom Healthcare Software Project?
Turn your clinical workflows, HIPAA/PIPEDA compliance requirements, and EHR integrations into a clear, reviewable development scope.
Why Choosing the Model Matters Before Choosing Telehealth Software
The same patient need can create different service arrangements.
A scheduled consultation requires patient and clinician availability together. Submitted information requires a review queue, an assigned professional and an agreed response process.
Home measurements introduce further responsibilities around devices, missing readings and action after review.
If those commitments remain unclear, the software can create demand that the organisation is not prepared to handle.
The consequences may include unanswered submissions, duplicated documentation or patients unsure whether someone is monitoring their information.
A defined model gives the telehealth development brief a practical foundation, including the service boundaries and work behind the interface.
What the Different Types of Telehealth Describe
Telehealth supports healthcare delivered remotely through communication and information-sharing technologies. Telemedicine generally refers more specifically to remote clinical care.
HHS distinguishes synchronous and asynchronous telehealth, meaning live interaction and information exchanged at different times.
Remote patient monitoring can operate asynchronously. Hybrid care combines virtual and in-person delivery, rather than describing another communication method.
Other labels answer different questions.
- Mental health and dermatology describe areas of care.
- Mobile health describes uses of mobile or wearable technology.
- Cloud-based software describes a deployment choice.
- AI-assisted documentation describes a supporting capability.
Keeping these distinctions clear allows one service to combine approaches without treating them as competing categories.
The Main Telehealth Approaches and What They Require
The following sections explain each approach through its patient experience, operating demands and limitations. The examples illustrate planning considerations. Clinical suitability still needs assessment for the actual service and patient.
1. Synchronous Telehealth for Live Consultations
Synchronous telehealth involves participants interacting at the same time, including video or audio consultations.
A scheduled therapy session is one example. The clinician and patient need a shared appointment, a working connection and access to relevant information.
Where it can help
Live interaction allows questions and clarification during the appointment. It can also support participation by an interpreter or caregiver where appropriate.
What the service needs to organise
- Appointment availability and participant access.
- Relevant clinical information during the visit.
- Preparation and technical assistance.
- An agreed response to interruption.
- Documentation and follow-up responsibilities.
Video is not the only synchronous option.
A Statistics Canada report released in June 2026, using 2023 survey data, found telephone-only appointments predominated among virtual visits with family doctors or nurse practitioners.
That finding does not determine the right modality for your service. It shows why patient access and actual care requirements deserve consideration before assuming video-only delivery.
The limitation to address
Live availability does not remove the limitations of a remote assessment. The service needs a route to further examination or other appropriate care when required.
2. Asynchronous Telehealth for Information Reviewed Later
Asynchronous telehealth allows information to be submitted and reviewed at different times.
Examples include images, questionnaires and secure messages. HHS describes these uses within its asynchronous telehealth guidance.
A dermatology service might receive images and relevant history before assigning the submission for review.
Where it can help
Patients and clinicians do not need simultaneous availability. Structured submissions can also prepare information before a later consultation.
What the service needs to organise
The review queue needs an owner, staffing capacity and a response window.
Patients should understand whether their submission has been received, whether information is missing and when they can expect the next step.
The limitation to address
Submitting information is not the same as receiving immediate clinical attention.
The organisation needs an approved process for unsuitable submissions, unclear information and situations requiring a different form of care.
The corresponding telehealth software features should represent those responsibilities, rather than provide an unassigned inbox.
3. Remote Patient Monitoring Between Appointments
Remote patient monitoring, or RPM, involves collecting and transmitting patient measurements for review.
Examples include readings from blood-pressure monitors, glucose meters or connected scales.
HHS identifies RPM as a form of asynchronous telehealth. It warrants separate planning because devices and repeated measurements introduce additional responsibilities.
Where it can help
Measurements collected between appointments can provide information for an agreed monitoring programme.
The programme needs to explain what is collected and how the care team uses it.
What the service needs to organise
- Device setup and patient instruction.
- Reliable association of readings with the correct person.
- Review frequency and responsible staff.
- Handling of missing or questionable readings.
- Clinically approved escalation arrangements.
The limitation to address
A stream of readings does not establish continuous observation.
Patients need an accurate explanation of monitoring coverage and what to do when they need assistance outside that arrangement.
Device support and review workload belong in the operating plan alongside the software.
4. Hybrid Care Connecting Virtual and In-Person Services
Hybrid care combines remote and in-person interactions within the service.
HHS describes it as a combination of virtual and in-person appointments, with decisions about appropriate delivery made by the patient and provider.
For example, an organisation might provide selected follow-up remotely while retaining in-person assessment when needed.
Where it can help
The service can use different delivery methods across the patient journey, rather than expect one method to handle every interaction.
What the service needs to organise
The transition needs an accountable team, accessible information and a clear next action.
An onward referral should not disappear into a separate process without confirmation of responsibility.
The limitation to address
Adding an in-person option does not automatically create continuity.
The organisation needs practical arrangements for access, records and follow-up. A defined telehealth EHR integration can support the agreed information exchange.
Synchronous vs Asynchronous Telehealth at a Glance
The most important difference is when clinical work occurs and how that work is organised.
| Decision | Synchronous Care | Asynchronous Care |
|---|---|---|
| Participation | Participants interact together | Information is exchanged at different times |
| Capacity planning | Appointment or live-service availability | Submission volume and review capacity |
| Patient expectation | Interaction during the session | A defined response process and window |
| Common operational risk | Failed joining or interrupted contact | Unassigned or delayed review |
| Follow-up requirement | Actions after the interaction | Resolution or escalation after review |
A single service can combine both approaches.
For instance, a live consultation may use information submitted beforehand and approved messages afterwards. Those activities still need their own responsibilities.
How to Choose the Right Starting Model
The choice should follow the intended care service, patient population and resources available to operate it. The questions below help turn a broad idea into decisions a clinical and product team can assess.
What Interaction Does the Service Require?
Establish which activities need live discussion, which information can be reviewed later and where an in-person assessment may be necessary.
The answer should come from the service’s clinical requirements, rather than the capabilities of a selected platform.
Can the Team Meet the Response Commitment?
An asynchronous service needs review capacity. An RPM programme needs monitoring coverage. Live care needs appropriate availability.
For an illustrative queue receiving 30 submissions per day, an average 10-minute review represents five hours before additional administration or follow-up.
Those are planning assumptions, not a clinical workload benchmark.
Can Patients Use the Proposed Approach?
Consider connectivity, privacy, language, accessibility, caregiver involvement and preferences.
The service needs a way to identify assistance requirements without assuming that every patient will use the same device or communication method.
Who Maintains Continuity?
An ongoing service and a one-off consultation create different expectations about records and follow-up.
The organisation should explain who remains responsible after the interaction, including outstanding results, referrals or patient questions.
What Needs Separate Assessment in the US and Canada?
The model’s operational fit does not establish permission to practise or payment eligibility.
In the US, HHS guidance explains that cross-state practice arrangements vary and advises verifying patient location before appointments.
For Canadian services, the launch assessment should identify relevant provincial or territorial professional requirements and service arrangements.
The Canadian Medical Association’s telehealth overview also explains that availability and coverage can differ by provider and location.
Privacy, consent, vendor responsibilities and reimbursement need assessment for the actual service.
The broader healthcare compliance guide provides context without turning a care-model label into a claim of compliance.
Connect the Care Model With Its Operating Budget
Each approach creates a different cost structure.
Live consultations involve communication services and appointment support. Asynchronous care involves review capacity and queue management.
RPM adds device arrangements, data handling and monitoring work. Hybrid care needs workable handoffs between remote and physical services.
The telehealth development cost guide explains how to connect those assumptions with build and operating expenditure.
Custom development becomes useful when those arrangements require workflows or connections that existing software cannot adequately support.
The scope should follow the chosen service rather than include every possible delivery method at launch.
Choose a Care Model Your Team Can Deliver Consistently
The right starting model explains what patients receive, when the team responds and where responsibility continues after each interaction.
With those commitments established, software planning can focus on supporting the service instead of leaving operating decisions to be discovered after launch.
Before approving the product scope, the following points should be clear.
- Match each care activity with an appropriate interaction method and an accountable clinical team.
- Define response windows and staffing coverage before accepting submissions or introducing monitoring services.
- Establish how patients access further care when the remote interaction cannot complete the service.
- Connect records and follow-up responsibilities across every delivery method included in the launch scope.
- Assess operating capacity and patient access before adding more services to the initial platform.
Launch Flow can help turn those decisions into a development brief. Bring the care model, existing systems and operating requirements to your telehealth project discussion.
Frequently Asked Questions
These questions clarify related terms and choices that do not determine the care model by themselves.
Is a patient portal a type of telehealth?
A patient portal is a software interface that may support appointments, messages, records or other services. The care model depends on how those capabilities are used and supported.
What is a provider-to-provider eConsult?
An eConsult allows one professional to request input from another, such as a specialist. It can operate asynchronously, with defined information, review and follow-up responsibilities.
Does adding AI create another type of telehealth?
AI is a supporting capability rather than a communication model. An AI telehealth integration may assist intake or documentation within live, asynchronous or combined services.
Build Compliant Healthcare Software
Stop managing patient referrals, workflows, and clinical records through manual workarounds. Partner with Launch Flow to engineer compliant, integrated healthcare software tailored to your organization.

Muhammad Bin Habib
Chief Growth Officer• Launch Flow Inc.
Chief Growth Officer at Launch Flow Inc. An elite organic growth architect and revenue operator with a pedigree of scaling market-leading digital enterprises to $40M+ ARR. Having served as Head of Organic Growth across category-defining innovators including Tekrevol, Qordata, Imagine.Art, and Chatly.ai, Muhammad engineers proprietary demand-generation flywheels, high-barrier SEO moats, and institutional customer acquisition infrastructure.
