Introducing Direct Doxy.me Integration in Scriber

If you see behavioral health clients over telehealth, you already know the problem. You have one window open for Doxy.me and another for your EHR or your notes. You've tried propping your phone next to the laptop to capture audio. You may have installed a browser extension that worked until Doxy shipped an update. You've pasted session summaries across tabs. The technology exists to do all of this in one place, and until today, no AI scribe had built it. Starting April 28, 2026, Scriber does. The Doxy.me integration ships in production for all paid plans. Your Doxy room lives inside Scriber, session audio is captured natively by the browser, and the note is generated the same way it would be for an in-person session — no second device, no extension, no workaround.

What the Integration Actually Does

The Doxy.me integration is not a button that opens Doxy in a new tab and tells you to copy your notes over when you're done. It is a native embed.

When you open the Telehealth recorder in Scriber, your Doxy.me patient room loads in a frame inside the Scriber interface. The waiting room, video feed, and call controls are all visible without leaving Scriber. When you click Start visit + recording, your browser asks you to share a tab — you select the Scriber tab and tick Share audio. From that point, the call audio from both you and your client flows into Scriber's transcription pipeline, exactly as it would from a microphone in an in-person session.

When the session ends, you choose your note template — BIRP, DAP, SOAP, intake assessment, or any custom template you've saved — and Scriber generates the first draft. You review, edit, and sign off. The workflow from call end to finalized note is identical to how Scriber works for in-person sessions. Nothing new to learn.

How It Works Under the Hood

This is worth explaining clearly because the implementation has direct implications for reliability, compatibility, and compliance.

Doxy.me provides an SDK for developers who want to embed its video call UI. However, that SDK is sandboxed — it does not expose a MediaStream that a consuming application can access. There is no documented API that would let Scriber tap into the audio from a Doxy SDK session. This is by design, and it means that any scribe claiming a "Doxy integration" via the SDK alone cannot actually capture call audio.

Scriber uses the browser's standard getDisplayMedia API instead. This is the same API your browser uses when you share a tab for a Zoom presentation. The user initiates the share — selecting the Scriber tab and enabling the "Share audio" checkbox — and the browser hands a full audio track to Scriber's capture pipeline. No Doxy SDK key, no partnership agreement with Doxy, and no browser extension required. The integration works with any Doxy.me account, including the free tier, because it operates at the browser layer rather than the application layer.

The captured audio goes through the same transcription infrastructure as every other Scriber recording. Azure Speech and Speechmatics handle production workloads, both under active BAAs. Audio is processed and not retained beyond what is needed to generate the transcript.

One important detail about setup: because getDisplayMedia requires the user to actively select the tab and enable audio sharing, it is a deliberate, visible act. The browser permission is explicit. If the Share audio checkbox is not ticked, the recording captures silence. Scriber shows a real-time audio level indicator so you can confirm capture is working before the session begins.

HIPAA Compliance for Doxy Telehealth Sessions

Two BAAs are in scope for a compliant Doxy + Scriber workflow.

The Doxy.me BAA covers the video call itself. Doxy.me provides HIPAA-compliant video infrastructure and signs BAAs on its professional and enterprise plans. If you are already seeing clients on Doxy.me in a clinical context, you likely have this in place.

The Scriber BAA covers audio capture, transcription, note generation, and storage. Scriber includes a signed BAA with every paid plan at signup — no separate request required.

One engine is explicitly excluded from Doxy telehealth sessions: xAI Grok. xAI does not currently hold a general HIPAA BAA for clinical use. When the Doxy integration is active, Scriber enforces BAA-covered engines — Azure Speech and Speechmatics — at the system level. No configuration is needed on your end; the enforcement happens automatically.

Metadata stored with each Doxy session is deliberately minimal: the room identifier, session start and end timestamps, and the optional patient ID from the Doxy room URL if one is present. No patient name, diagnosis, or other PHI is stored in session metadata. Clinical content lives only in the generated note.

For a detailed walkthrough of Scriber's compliance posture, see our HIPAA-compliant scribe solution page and the BAA information page.

Why No Other Scribe Has Done This

"Compatible with Doxy" appears on several AI scribe marketing pages. In practice, compatibility has meant one of three things: record separately and upload the file; use a phone next to the laptop; or install a browser extension that captures tab audio at the OS level.

None of these is an integration. They are workarounds, and they carry real costs. A phone next to the laptop introduces microphone distance and background noise. Browser extensions require maintenance to stay functional as Chrome and Doxy both update. File upload workflows mean audio files exist outside the scribe platform long enough to create compliance exposure. And none of the workaround approaches enforce BAA-covered transcription automatically.

The reason no one had built the real integration comes down to the SDK limitation described above. Once it's clear that the Doxy SDK does not expose a MediaStream, the options are either to abandon the integration or find a different path. Scriber found the different path: use getDisplayMedia, which is a browser standard, is maintained by browser vendors, and does not depend on Doxy's SDK stability.

The tradeoff is that getDisplayMedia is a desktop-only API. Mobile browsers do not support tab audio sharing, so the Doxy integration is available on desktop Chrome, Edge, and Firefox. Mobile in-person recording using the device microphone continues to work as before. See how Scriber works for telehealth providers for the full feature breakdown.

Setup: Three Steps

Setup is a one-time process that takes under two minutes.

Step 1. Go to Settings → Telehealth in your Scriber account and paste your Doxy.me room URL — the same URL you share with clients, for example doxy.me/yourname. Scriber saves the room slug. You won't need to paste it again.

Step 2. When you are ready to start a telehealth session, open the Telehealth recorder and click Start visit + recording. Your browser will show a share picker. Select the Scriber tab and tick Share audio before clicking Share.

Step 3. Watch the audio level indicator in Scriber to confirm audio is being captured. Begin your session. Scriber records in the background; you focus on your client.

When the session ends, stop the recording and select your note template. The draft is generated in the same time as any other session — typically under 30 seconds for a 50-minute session.

What This Means for Telehealth Clinicians

Post-2020 surveys consistently put telehealth at 40 to 60 percent of behavioral health sessions. A scribe that handles in-person sessions well but requires a workaround for telehealth is a half-solution. For a clinician seeing 20 to 30 clients per week, half of them via Doxy.me, "use a separate device for those sessions" is not a workable answer.

The Doxy.me integration means the documentation workflow is the same regardless of whether the session is in-person or telehealth. Same template library. Same transcription pipeline. Same note quality. The modality of the session does not change the documentation workflow.

If you practice in behavioral health, psychiatry, substance use disorder treatment, or any telehealth-heavy specialty, this is the integration that has been missing. It is available now on all paid Scriber plans.

To try it: Log in to your Scriber account, go to Settings → Telehealth, and paste your Doxy room URL. If you are not yet a Scriber subscriber, start a 7-day trial and see pricing for plan details. Questions about the Doxy integration or your BAA can be directed to support.

Related reading: AI Scribe for Telehealth with Doxy.me · HIPAA-Compliant AI Scribe · Behavioral Health Specialty · Psychiatry Specialty