Asynchronous vs synchronous telehealth: which to build first
Asynchronous telehealth means a clinician reviews a prepared case; synchronous means a live visit. How they differ, what each changes in the build, and why most platforms end up with both.
Build asynchronous care first if your clinicians review structured intake and decide, and add video for the cases that need a conversation. Build synchronous video first only if every visit is a live consultation. Most platforms end up with both, joined by an escalation path from the asynchronous queue to a video visit.
The difference in one line
Asynchronous telehealth means the patient completes an intake questionnaire, and a clinician reviews the case and responds later. Synchronous telehealth means a live appointment by video or phone, at a scheduled time.
Side by side
| Asynchronous | Synchronous | |
|---|---|---|
| How care happens | Patient submits intake, clinician reviews and decides | Patient and clinician meet live |
| Patient effort | Fill in a form when convenient | Book a slot and be there |
| Clinician time | A short review of a prepared case | A full appointment |
| What you build | Intake, rules, a review queue, signatures | Scheduling, video, waiting room, notes |
| Where it breaks | A slow queue, or intake that misses something | No-shows, calendar gaps, connection problems |
| Best for | Routine, protocol-driven care | Cases that need a conversation or an exam |
What changes in the build
Asynchronous shifts the work into rules and the review screen:
- A structured intake that checks eligibility before a clinician sees the case. In our weight-management platform that includes a BMI check against the protocol and a screen for contraindications.
- A review queue that routes each case to a prescriber licensed where the patient lives.
- A screen that puts the whole case in front of the physician at once. We designed around a 45-second review target.
- A signature and an audit log for every decision.
Synchronous shifts the work into time and connection:
- Scheduling with availability, reminders and rescheduling.
- A reliable video session, and a plan for when it drops.
- Notes during and after the visit.
Why most platforms end up with both
Asynchronous review is efficient, but some cases need a conversation. The practical answer is an escalation path: the physician reviewing a case can send it to a video visit in one step. That is how our platform works. The asynchronous queue handles the routine cases, and video is there when a clinician wants it.
How to decide
- Is the care protocol-driven? If a clinician mostly confirms eligibility and signs off, start asynchronous.
- Is every visit a conversation? If so, start with video.
- Which rules apply where you operate? Rules for asynchronous care differ by US state and in the UK, so check each jurisdiction before you commit.
- What will you measure? For asynchronous, time to physician decision and queue age. For synchronous, no-show rate and visit completion.
How we have applied it
Our US and UK GLP-1 platform is built around asynchronous review with escalation to video. See the case study, the overview of telehealth software development, and the guide to telehealth metrics and KPIs.
