Skip to main content
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
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

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
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