The visit moved online; the interpreter and the lip-reading didn't come along. How to add a captioning and translation layer beside whatever platform the visit already uses.
A telehealth visit strips out most of what makes clinical conversation work: room presence, clear sightlines for lip-reading, an interpreter physically beside the patient. What's left is compressed audio through consumer hardware — and for a patient with limited English proficiency or hearing loss, that is often not enough to be safe. The fix is not a better telehealth platform; it is a captioning and translation layer running beside whichever platform the visit already uses. Here is how clinicians, interpreters, and patients set that up.
Telehealth access problems concentrate in two groups whose needs overlap but are not the same:
Add a third participant with the same problem: the remote medical interpreter, often joining by phone as a third leg of the call, working from the worst audio in the room.
A meaningful share of telehealth is not video at all — it is a phone call. Patients without reliable broadband, without a camera-equipped device, or without the patience for a portal login get the audio-only visit, and it removes every fallback at once: no faces, no lips, no chat window, no screen-shared instructions. Mishearing a dosage on a phone visit has no visual channel to catch it.
The good news is that a phone visit is still just audio reaching a device, and audio reaching a device can be captioned. The general patterns — same-device system audio, or speakerphone plus a second device — are covered in our guide to captioning phone calls in real time; everything there applies directly to audio-only telehealth.
The reason this works with every telehealth platform — the big EHR-integrated ones, the boutique ones, plain Zoom — is that nothing integrates with anything. The captioning tool reads the computer's audio; the platform never knows it is there.
No install, no IT ticket, no bot joining the visit. Unicaption runs in the browser (or as a desktop app) in a window next to the telehealth platform and the chart.
This is the step that makes the quality: the tool captions the far end's audio as transmitted, not a microphone's impression of your speakers. Room noise, typing, and echo never touch the transcript.
For an LEP visit, set the patient's language and yours; the original and the live translation appear side by side. Patients who code-switch mid-sentence are handled by automatic language detection.
Medication names, conditions, and the patient's name go into the custom dictionary before the visit. Built-in medical terminology covers the rest — drug names are exactly the words generic transcription mangles most.
The same tool serves three different seats in a telehealth visit, and it matters which seat you are setting up:
| Who | Setup | What it solves |
|---|---|---|
| Clinician | Unicaption beside the platform, system audio | Soft-spoken and accented patients become readable; nothing said gets lost while eyes are on the chart |
| Remote interpreter | Transcript running during the interpreted visit | A verification layer for dosages, spellings, and numbers — the details phone audio drops first |
| Patient (HoH or LEP) | Browser tab on their own device, captioning the visit audio | Captions of the clinician, or live translation into their own language, moments behind the speech |
Clinical language is a stress test for transcription — high stakes, dense terminology, zero tolerance for a misheard dosage. What makes Unicaption fit for that job:
The free tier gives you 30 minutes every week with no credit card — enough to run a real (or rehearsed) visit and judge the transcript against your own ear.
Any tool that processes visit audio is handling protected health information, and it should be interrogated like any other vendor in the care pathway: Is it HIPAA compliant? Is audio stored, and for how long? Are transcripts retained? Is session content used to train models? A tool with wonderful captions and vague retention answers does not belong in a clinical call.
Unicaption's answers are the short kind: audio is never stored, transcripts are deleted when the session ends, sessions are end-to-end encrypted, and content never trains models. The full checklist for evaluating captioning tools in clinical settings — BAAs, retention, the questions to put to any vendor — is in our HIPAA captioning guide. Treat this article as practical orientation, not legal or compliance advice for your organization.
Yes, without changing platforms. Run a captioning tool beside the telehealth platform and set its audio source to system or tab audio — it captions the visit's audio directly, and nothing joins the call. Unicaption does this in the browser with no install, at state-of-the-art streaming accuracy and real-time latency, which keeps captions usable in real conversation.
Set a source and target language in Unicaption (or leave automatic detection on) and it shows the original transcription and a live translation side by side, in 60+ languages. Clinicians use it to be understood by LEP patients; patients use it to read the clinician in their own language; interpreters use it as a verification layer during interpreted visits.
It depends entirely on the tool, and 'HIPAA compliant' on a marketing page is not the test. The questions that matter: is audio stored, are transcripts retained, is content used for model training, and will the vendor state all of it in writing. Unicaption's answers: end-to-end encrypted, audio never stored, transcripts deleted when the session ends, never used for training. Verify any tool — including us — against your organization's own compliance requirements.
Yes, and phone visits are where captions matter most, because there is no visual channel to catch a mishearing. If the call reaches a computer (softphone, VoIP), caption its system audio directly. If it lives on a phone, put the call on speaker and let a second device running Unicaption listen. Keep the devices close and the room quiet.
No. For consequential clinical conversations with LEP patients, a qualified medical interpreter carries meaning, culture, and clarification in both directions — captions and machine translation don't. The strongest setup is both: the interpreter interprets, and a live transcript holds dosages, names, and numbers still for everyone to verify.
Live captions and translation beside any telehealth platform — end-to-end encrypted, nothing stored. 30 free minutes every week, no credit card.
Start Free Trial →