Async vs Synchronous Telehealth Visits
How the platform decides between store-and-forward review and live audio-video visits — clinical fit, documentation, coverage, and system design implications.
Modality is a product decision with clinical, regulatory, and infrastructure consequences. Choosing well per condition is what keeps a telehealth platform both safe and efficient at volume.
What async is good at
Store-and-forward review fits stable, protocol-driven care: refills, routine dermatology, ongoing therapy management. Structured intake produces discrete clinical data, and a licensed provider reviews it against explicit red-flag rules. The system carries the consistency that a rushed live visit often cannot.
What requires live video
New diagnoses, symptom ambiguity, mental-health assessments, and many state establishment-of-care requirements call for synchronous audio-video. The platform treats video as a clinical instrument — consent, recording policy, transcript retention, and connection quality all have documented behavior.
Documentation parity
Whatever the modality, the record must show the same things: what was asked, what was observed, what was decided, and why. Async cases carry the intake payload and rule evaluations; synchronous cases carry the visit note and structured observations. Both feed one patient record.
Coverage and billing implications
Payer coverage differs by modality and by code, and policies change. Keeping modality, place-of-service, and code mapping in a data layer means a coverage update does not require touching clinical code paths.
System design consequences
Async is a queue problem: throughput, SLA timers, escalation, and reviewer load balancing. Synchronous is a realtime problem: signaling, media servers, waiting rooms, and failure recovery. A full-stack platform runs both, and routes each case to the modality it belongs in.
Sources
External sources are provided for reference. Regulations change; this article is engineering commentary, not legal or medical advice.