For telehealth and virtual care platforms
A pre-visit connection check for telehealth
A short test the patient runs in your portal, your reminder link or your virtual waiting room. Download, upload, latency and jitter come back to your platform, so a visit that would fail is caught while there is still time to fix it.
30-day free trial · 100 API calls · No credit card · Plans from $49/month
This is the check a patient would run. In your platform the numbers go to your code and your dashboard.
Offer the check before the visit
In the appointment reminder, on the check-in page or in the waiting room. One script tag; nothing for the patient to install.
Compare with what the visit needs
Your callback receives download, upload, latency and jitter. Video visits need upload and stability more than headline speed.
Guide, switch or reschedule
Clear the patient into the visit, show a plain-language fix, offer audio-only, or move the slot. Keep the numbers with the appointment.
The failed visit nobody planned for
A video visit that freezes is not a technical glitch to the patient; it is a missed appointment, often one they waited weeks for, and a clinician's slot spent on reconnecting. The cause is usually the patient's own connection or Wi-Fi, which nobody on your side can see until the visit is already failing.
A connection check before the visit turns that into a message the patient can act on: move closer to the router, switch off the other video stream, or join by phone. It runs in the browser they will use for the visit, usually in under a minute, and it needs no app.
What a video visit needs
| Metric | What it affects | Typical requirement |
|---|---|---|
| Upload | The patient's video and audio to the clinician | 1.5 to 3 Mbps for HD video |
| Download | Seeing and hearing the clinician; shared results and images | 1.5 to 3 Mbps |
| Latency | Conversation flow; the pause before an answer | Under 150 ms |
| Jitter | Frozen frames and broken audio on an otherwise fast line | Under 30 ms |
Use the figures your video vendor publishes, with headroom, and let a good audio-only path count as a pass when video would not hold: a visit that happens by voice beats one that does not happen.
Built for patients, not engineers
The check runs in any modern browser, including older phones and tablets, with nothing to download and no account. The API is headless, so the page the patient sees is yours: your wording, large type, one button, a result in plain language. The vanilla example is a complete page to start from.
What your platform receives, and what it does not
| Property | Type | What it means |
|---|---|---|
| download | number | Average download speed in Mbps |
| upload | number | Average upload speed in Mbps |
| maxDownload, maxUpload | number | Peak speeds in Mbps |
| latency | number | Minimum round trip in milliseconds |
| jitter | number | Latency variance in milliseconds |
| testServer | string | Which test server the browser reached |
| ip_address, hostname, userAgent | string | Who ran it, for your records |
The test measures the connection only: throughput, latency and jitter. It never touches the visit, the video stream or anything clinical. The result carries the connection's IP address and device details, and it lands in your callback and in your analytics dashboard; what you attach it to inside your own systems is your decision.
Hiring platforms, contact centres and ISPs have run their connection checks on this API since 2013.
What it costs
Every completed test is one API call. The 30-day trial includes 100 calls and needs no card. Paid plans start at $49 a month for 1,000 calls (Startup), then $149 for 10,000 (Business) and $599 for 100,000 (Pro); enterprise volume is priced on request. The full table is on the API page.
Questions people ask
Does the check handle any patient health information?
No. It measures the connection and returns throughput, latency and jitter with the connection's IP address and device details. It has no access to the visit, the video or any clinical data. What your platform stores the result against is entirely within your systems.
Will it work for patients on older phones?
Yes. It runs in any modern browser, including phone and tablet browsers, and needs no app or plugin. The page can be as simple as one button and a sentence.
Can we send it in the appointment reminder?
Yes. A link to your check page in the reminder lets the patient test the night before, from the room and device they will use, which is when there is still time to fix a problem.
What if the connection is too slow?
Your page decides. Most platforms show a short fix (move nearer the router, pause other streams), offer an audio-only visit, or let the patient reschedule, and keep the result with the appointment.
Can clinic staff run the check for the patient?
Only from the patient's side. The test measures the connection it runs on, so a check run at the clinic measures the clinic. The link in the reminder or the portal is what gets it run from the patient's home, on the device they will use for the visit.
30-day free trial · 100 API calls · No credit card · Plans from $49/month