Techdome
All Insights/Healthcare AI

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
Oct 28, 20262 min read
Verified Architecture

A telehealth operator needs about a dozen numbers: how many patients start and finish intake, how fast a physician decides, how many prescriptions reach a patient on time, what each encounter earns, and whether data stays isolated and audited. Track them per clinic, not only for the whole platform.

Why track per clinic

A multi-tenant platform hides problems in an average. One clinic with slow reviews or a high drop-off rate disappears into a network-wide figure. Every metric below should be filterable by clinic (tenant), by prescriber and by jurisdiction.

Acquisition and intake

  1. Intake start rate: visitors who begin the questionnaire divided by visitors to the intake page.
  2. Intake completion rate: completed questionnaires divided by started ones. A low number usually means a long form or an unclear step. Our platform's intake is designed to take under about three minutes.
  3. Eligibility screen-out rate: the share stopped by the automated checks (for GLP-1 care, BMI and contraindication rules). It tells you whether marketing is bringing the right patients.

Clinical throughput

  1. Time to physician decision: from completed intake to an approved or declined case. Ours is built around a 45-second chart-review target once a physician opens the case.
  2. Physician-approved encounters per month: the volume figure. One month on our platform: 311 physician-approved encounters.
  3. Escalation rate: the share of asynchronous cases a physician sends to a video visit. A rising rate can mean the intake questions are missing something.
  4. Queue age: the oldest case still waiting, per jurisdiction. Licensing rules mean a US state or the UK can run short of prescribers while the rest is idle.

Fulfilment

  1. Order-to-dispatch time: from signature to the pharmacy receiving the order. Ours targets a dispatch in about a second once the order is signed.
  2. On-time delivery rate: shipments delivered inside the promised window.
  3. Cold-chain excursions: shipments that left the 36 to 46°F range, and how many were caught before breach rather than after.

Money

  1. Revenue per encounter: on our platform, about $233 per encounter.
  2. Monthly platform revenue: about $76K in the reported month.
  3. Refund and chargeback rate: split billing settles at capture, so disputes show up fast.

Trust and compliance

  1. Audit-log coverage: every access to patient data should be in an append-only log. Track gaps, not just totals.
  2. Tenant-isolation checks passing: automated tests that a user in one clinic cannot read another's records.

How to use them

Pick five to start: intake completion, time to physician decision, encounters per month, order-to-dispatch time and revenue per encounter. Review them weekly per clinic. Add the rest as the network grows.

Our worked example

Our US and UK GLP-1 platform runs 38 clinic tenants, 10 of them at scale, with 12,400+ patients. Read the full case study or the overview of telehealth software development.

FAQ

Questions readers ask

Which telehealth KPIs should I start with?

Start with five: intake completion rate, time to physician decision, physician-approved encounters per month, order-to-dispatch time and revenue per encounter. Review them weekly for each clinic, then add the rest as the network grows.

Why track telehealth metrics per clinic and not only overall?

A network-wide average hides a clinic with slow reviews or a high drop-off rate. In a multi-tenant platform every metric should be filterable by clinic, prescriber and jurisdiction.

What is a good intake completion rate for telehealth?

There is no single benchmark that fits every clinic. Track your own rate per clinic over time: a falling rate usually points to a long form or an unclear step, not to the patients.

How is time to physician decision measured?

From the moment a patient completes intake to the moment a physician approves or declines the case. Our platform is built around a 45-second chart-review target once a physician opens the case.

Which compliance numbers matter for a telehealth platform?

Audit-log coverage and tenant-isolation checks. Every access to patient data should be in an append-only log, and automated tests should prove that one clinic cannot read another clinic's records.

Continue reading

More foundry teardowns

View all
Three stacked layers: tenant isolation, PHI sanitization, physician sign-off
Healthcare AIAugust 2026

Engineering Zero-Trust HIPAA Compliant AI Architectures for Telemedicine

Rahul Joshi
Rahul JoshiChief Executive Officer
+
+
+
+
Healthcare AIOct 28, 2026

Telehealth compliance checklist for the US and UK

Techdome Engineering
Techdome EngineeringEngineering Team
+
+
+
+
Healthcare AIOct 28, 2026

How to build a GLP-1 telehealth platform

Techdome Engineering
Techdome EngineeringEngineering Team
+
+
+
+
Healthcare AIOct 28, 2026

Asynchronous vs synchronous telehealth: which to build first

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

Message queues vs event streams: SQS, RabbitMQ, Kafka

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

Webhook retries and idempotency keys, together

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

PHP2Shell: how to check and protect your PHP site

Techdome Engineering
Techdome EngineeringEngineering Team
API testing explained: types, what to automate, and tools
Engineering Practice

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

Techdome Engineering
Techdome EngineeringEngineering Team
"Automating mortgage back-office work with n8n"
n8n Automation

"Automating mortgage back-office work with n8n"

Techdome Engineering
Techdome EngineeringEngineering Team
Five numbered phase nodes on a connecting line: de-risk, foundation, core workflows, hardening, cutover
Studio ArchitectureAugust 2026

The Techdome Blueprint: How We Build & Launch Software Ventures in 8 Weeks

Rahul Joshi
Rahul JoshiChief Executive Officer
Webhook ingestion workers feeding a Redis queue, fanning out to two worker pools with a dead-letter path
n8n AutomationAugust 2026

Production n8n Architecture: Hardened Patterns for Enterprise Pipelines

Rahul Joshi
Rahul JoshiChief Executive Officer
Multi-agent orchestration state machine with supervisor engine and sandboxed tool execution
Studio ArchitectureSeptember 2026

Autonomous Multi-Agent Orchestration: Production Patterns Beyond LangChain

Rahul Joshi
Rahul JoshiChief Executive Officer
Next.js 15 monorepo architecture showing edge caching, React Server Components and design tokens
Studio ArchitectureSeptember 2026

Optimizing Next.js 15 Monorepos for Sub-Second TTFB at Scale

Rahul Joshi
Rahul JoshiChief Executive Officer