Skip to main content
Techdome
All Insights/Healthcare AI

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.

Techdome Engineering
Techdome EngineeringEngineering Team
Oct 28, 20262 min read
Verified Architecture

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

AsynchronousSynchronous
How care happensPatient submits intake, clinician reviews and decidesPatient and clinician meet live
Patient effortFill in a form when convenientBook a slot and be there
Clinician timeA short review of a prepared caseA full appointment
What you buildIntake, rules, a review queue, signaturesScheduling, video, waiting room, notes
Where it breaksA slow queue, or intake that misses somethingNo-shows, calendar gaps, connection problems
Best forRoutine, protocol-driven careCases 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

  1. Is the care protocol-driven? If a clinician mostly confirms eligibility and signs off, start asynchronous.
  2. Is every visit a conversation? If so, start with video.
  3. 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.
  4. 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.

FAQ

Questions readers ask

What is asynchronous telehealth?

Care without a live appointment: the patient completes an intake questionnaire, and a clinician reviews the case and responds later.

What is synchronous telehealth?

A live appointment by video or phone, at a scheduled time.

Which should I build first?

Asynchronous first if clinicians mostly confirm eligibility and sign off a protocol; video first if every visit is a conversation. Many platforms add the other later.

Can one platform do both?

Yes. The common design is an asynchronous review queue with a one-step escalation to a video visit, which is how our platform works.

Do the rules differ by location?

Yes. Rules for asynchronous care differ by US state and in the UK, so check each jurisdiction you serve.

Continue reading

More foundry teardowns

View all
Isometric illustration of one platform split into separate clinic compartments, with a shield, an access gate and an audit log
Healthcare AIAugust 2026·8 min read

Engineering HIPAA-ready telehealth platforms: the decisions we make first

How tenant isolation, access control, audit logging, identity and vendor agreements shape a HIPAA-ready telehealth system, with what each looked like on three clinical platforms we built.

Rahul Joshi
Rahul JoshiChief Executive Officer
+
+
+
+
Healthcare AIOct 28, 2026·4 min read

Telehealth compliance checklist for the US and UK

An engineering checklist for a telehealth platform serving US and UK patients: contracts, access and audit, clinic isolation, licensing by jurisdiction, prescribing, signatures, payments and incidents.

Techdome Engineering
Techdome EngineeringEngineering Team
+
+
+
+
Healthcare AIOct 28, 2026·3 min read

How to build a GLP-1 telehealth platform

A builder's guide to a GLP-1 telehealth platform: compliance, multi-tenant clinics, eligibility checks, licensing by jurisdiction, chart review, pharmacy routing, cold chain and billing.

Techdome Engineering
Techdome EngineeringEngineering Team
+
+
+
+
Healthcare AIOct 28, 2026·2 min read

Telehealth metrics and KPIs: the numbers that matter

The 15 telehealth metrics an operator should track, from intake completion to time to physician decision and cold-chain excursions, with real figures from a US and UK GLP-1 platform.

Techdome Engineering
Techdome EngineeringEngineering Team
A technical illustration comparing queued task delivery with retained event streaming.
System DesignOct 26, 2026·3 min read

Message queues vs event streams: SQS, RabbitMQ, Kafka

Use SQS or RabbitMQ for work distribution; use Kafka when you need retained event logs, replay, fan-out, and per-key ordering.

Techdome Engineering
Techdome EngineeringEngineering Team
Illustration of webhook retry flow using a stable idempotency key, de-duplication store, and dead-letter queue.
System DesignOct 26, 2026·3 min read

Webhook retries and idempotency keys, together

Webhook retries need stable idempotency keys so repeated deliveries are safe, deduplicated, observable, and recoverable through DLQs.

Techdome Engineering
Techdome EngineeringEngineering Team
Blueprint-style illustration of a server rack behind a layered firewall shield, with a PHP version badge being upgraded
Engineering PracticeOct 22, 2026·6 min read

PHP2Shell: how to check and protect your PHP site

PHP2Shell (CVE-2026-109618 and CVE-2026-109619): how to check your PHP version, patch it or shield it with a WAF, with two real cases.

Techdome Engineering
Techdome EngineeringEngineering Team
Computer screen filled with code
Engineering Practice8 min read

API testing explained: types, what to automate, and tools

API testing checks an interface directly, below the UI. Learn the five main types, how mocking and test data fit in, and which tests to automate first.

Techdome Engineering
Techdome EngineeringEngineering Team
Computer screen with data
n8n Automation7 min read

"Automating mortgage back-office work with n8n"

Mortgage back offices drown in documents. A staged n8n workflow can handle intake, classification, extraction and validation, and route exceptions to people with a full audit trail.

Techdome Engineering
Techdome EngineeringEngineering Team
Interface illustration of a browser window with three gauge dials, a heavy block swapped for a light placeholder, and images compressed
Engineering PracticeSeptember 2026·6 min read

Making a Next.js site fast: the fixes that moved Core Web Vitals on techdome.io

Hero images that wait for JavaScript, an embedded scheduler that blocked the page, oversized images and bloated page data: the real fixes behind our site's performance work, and a checklist for yours.

Rahul Joshi
Rahul JoshiChief Executive Officer
3D illustration of an AI agent connected to calendar, database and phone tools, with a sound wave and a small knowledge graph
Studio ArchitectureSeptember 2026·7 min read

Building AI agents that hold up in production: what we learned from voice, interviews and GraphRAG

Narrow jobs, grounded answers, deterministic scoring, a latency budget, full logs and a human handoff: the patterns behind our voice agents, AI interviewer and GraphRAG platform.

Rahul Joshi
Rahul JoshiChief Executive Officer
Pipeline illustration of an automation workflow with a queue feeding two workers, a retry loop, an alert bell and a review tray
n8n AutomationAugust 2026·7 min read

Production n8n: the patterns that keep automation from failing quietly

Idempotent triggers, retries with limits, failure alerts, human review and workflows kept in Git: the patterns we use to run n8n automation in production, with the builds they come from.

Rahul Joshi
Rahul JoshiChief Executive Officer
Blueprint-style illustration of five phases from a drawing board to a launched product, rising along a path
Studio ArchitectureAugust 2026·7 min read

The Techdome Blueprint: how we take a product from a blank repo to production in eight weeks

The five steps of our Blueprint, what each one delivers, how fixed-scope sprints and engineering pods are priced, and how recent builds ran from kickoff to production.

Rahul Joshi
Rahul JoshiChief Executive Officer