The visit stays in Nextvisit.
Start a video visit from the encounter. The patient joins from a link, AriaMD transcribes both sides, and telehealth place-of-service lands on the claim when you sign.
No patient app. No second video license. Same workspace boundary as the chart.
Click Waiting room and In session to see both surfaces. Sample patient and transcript, drawn to match the recorder mocks on this site.
Open the chart. Admit. Talk. Sign.
The same four beats as an in-person session. The camera is the only new piece, and the billing fields come along for the ride.
-
Step one
Start the visit from the encounter.
Pick the patient and the template the way you already do, then start a Nextvisit visit instead of opening a second video app. Service location is Telehealth from the first field, so the billing side is right before anyone says hello.
- The patient and template you already use
- Service location set to Telehealth on the encounter
- A browser join link you can send in a click
- No Zoom or Doxy license for the visit itself
nextvisit.app / encounterNew encounterNot startedScheduled 3:00 PM- Template
- SOAP Note (2026)
- Service location
- Telehealth
- Visit type
- Established · follow-up
Patient join linkBrowser · nothing to installnextvisit.app/j/9f4-2kd -
Step two
The patient joins. You admit when you are ready.
They open the link in a browser on a phone, tablet, or laptop and land in the waiting room. You see who is ready, what they are on, and whether camera and microphone came through before you let them in.
- Waiting room with device, browser, and connection detail
- Camera and microphone permission is the only prompt they see
- Admit on your clock, not on the join time
- Nothing to install on the patient side
nextvisit.app / visitMarcus HayesNot startedPOS 10 · homeConsent on fileHIPAA -
Step three
You talk. AriaMD writes.
The audio is already in the visit, so both sides transcribe at line level instead of arriving as speaker bleed. Mid-visit scales and staged codes work exactly the way they do in an in-person session.
- Both sides captured at line level
- Timestamped transcript beside the video
- Scales scored from the live transcript
- SOAP draft building while you talk
nextvisit.app / visitMarcus Hayes00:18:42POS 10 · homeConsent on fileHIPAA -
Step four
End. The note and the claim already know it was telehealth.
The SOAP draft lands on the encounter with the telehealth billing fields already set, so nobody reconstructs place of service from memory a week later. Sign once you have reviewed it.
- SOAP draft on the encounter
- POS 10 or 02 from where the patient actually sat
- Modifier 95 attached when the payer wants it
- Consent stored as a field, not as free text
nextvisit.app / encounter / billingEncounter · billingReady to sign00:18:42- Service location
- Telehealth
- Place of service
- 10
- Modifier
- 95
- Consent
- Confirmed
Patient not at home on the day of service? The encounter switches to POS 02 and the claim follows.
Claim previewDrafts on sign99214+95F33.1F41.1POS 10Fields land from the visit. You can still change them before you sign.
One room for the visit, the note, and the claim.
A video visit that lives on the encounter, so documentation and billing do not have to catch up after you hang up.
-
The visit runs in the chart
Start video from the encounter. No Zoom license, no Doxy tab, no second login. The patient, the note, and the claim stay on one record.
-
Waiting room and a join link
Send a link. The patient waits in the browser on a phone or laptop. You admit when you are ready. Nothing to install on their side.
-
AriaMD already listening
Both sides transcribe at line level because the audio never leaves the visit. Scales, codes, and the SOAP draft run the same way they do in the room.
Same workspace auth, same BAA, same US-hosted stack as the rest of Nextvisit. The visit is live; the transcript and the note are the record.
- HIPAA
- SOC 2 Type II
- BAA
- US-hosted
Place of service is part of the encounter.
Telehealth and in-office claims do not look the same on the wire. The visit sets the fields so billing does not reconstruct them from memory.
Service location is a first-class object, the same list that filters the panel and fires Service Location Assigned automations. Built-in visits assign Telehealth and choose POS 10 or 02 from where the patient actually is. Modifier 95 attaches when the payer wants the synchronous-video flag.
- Service location
- Telehealth
- Place of service
- 10
- Modifier
- 95
- Consent
- Confirmed
Patient not at home on the day of service? The encounter switches to POS 02 and the claim follows.
Fields land from the visit. You can still change them before you sign.
Built-in is one path. The recorder still covers the other.
Some clinics keep Zoom for groups, interpreters, or a hospital contract. Nextvisit does not force a rip-and-replace. Start the outside call, flip Telehealth Mode on session setup, and share the tab with audio. When you are ready to drop the second tab, start the visit here instead.
- Line-level patient audio from the call tab (Zoom, Doxy, Teams, Google Meet)
- Mic and tab audio mixed in the browser before transcription
- Per-session toggle on the Session Information screen
- Same note workflow, same templates, same encounter
Telehealth Mode on the recorder
Prefer a written walkthrough? Recording a session covers the share-picker path in the help center.
| Medication | Sig | Started | Prescriber |
|---|---|---|---|
| Acamprosate | 666mg BID | 11/01/23 | Katie |
Common questions about built-in telehealth.
Built-in telehealth is a video visit that runs inside the Nextvisit workspace. You start it from the encounter. The patient joins from a browser link. AriaMD transcribes both sides and drafts the note. Place-of-service and telehealth modifiers land on the claim when you sign. You do not need a separate Zoom or Doxy account for the visit itself.
No. The join link opens in a modern browser on a phone, tablet, or laptop. Camera and microphone permission is the only prompt they see.
Telehealth Mode captures patient audio from a Zoom, Doxy, Teams, or Meet tab and mixes it with your microphone so the transcript is clean. Built-in telehealth is the video visit itself: waiting room, camera, and audio live in Nextvisit, so there is no second tab to share. Use Telehealth Mode when you still want the outside video app. Use built-in telehealth when you want the visit to stay here.
Yes. It sits inside the same workspace boundary as the chart: HIPAA, SOC 2 Type II, a BAA by default, and US hosting. The visit is live. Nextvisit persists the transcript and the note, not a second copy of the video call on a consumer platform.
The encounter carries a Telehealth service location. That assignment selects place-of-service 10 when the patient is at home, or 02 when they are not, and attaches modifier 95 for synchronous video when the payer requires it. Signed encounters with ICD-10 codes still auto-create claims in the insurance module.
Yes. Transcription, scale scoring, and code staging run the same way they do for an in-person recorder session. Both sides are captured at line level because the audio is already in the visit, not playing through a speaker.
Clinicians should use a current desktop Chromium browser (Chrome, Edge, Brave, Arc, Opera) for the most reliable camera, microphone, and waiting-room controls. Patients can join from those browsers or from current Safari on iOS. Firefox works for many patients; if a join fails, send them back on Chrome.
No. You remain responsible for being licensed in the state where the patient is sitting. Nextvisit documents the visit, the consent, and the place of service. It does not replace a compact, a license, or a payer contract.
Twenty minutes, one mock visit. You leave with a note in your template.
Book fifteen minutes. We start a mock visit, admit a sample patient, and show the note and the claim fields that come with it.