Logic: Start time = when 2 participants are present in the Meet. End time = when one/both leave for >60 seconds (ignore brief drops).

Edge case: If frequent disconnect/rejoin events occur, display a warning next to the end time and prompt clinician to verify/override.

Goal: Reduce manual note edits, improve accuracy for documentation/billing, and maintain auditability.

Feature request: Auto-capture telehealth start/end times via Google Meet

Summary

Add an optional setting that automatically records actual session start and end times for Google Meet telehealth appointments by reading Meet call presence/participant events, then writes those timestamps into the appointment/note for billing, documentation, and operational accuracy.

Problem

For telehealth sessions, the scheduled appointment time often differs from when the session actually starts/ends due to:

late arrivals

brief disconnections

early wrap-ups

tech issues

Clinicians then have to manually estimate time in the note, which is:

inaccurate

burdensome

inconsistent across providers

Proposed behavior

1) Determine session start time

When two participants are simultaneously present in the associated Google Meet (client + clinician), set:

Call Start Time = timestamp when the 2nd participant joins

Notes:

This should work whether the clinician or client joins first.

If a 3rd party joins (e.g., parent, partner), logic should still treat “session started” as the moment the minimum threshold is met.

2) Determine session end time with a 1-minute grace window

When one or both required participants leave the Meet:

start a timer

if they do not rejoin within 60 seconds, set:

Call End Time = timestamp when presence dropped (or after the 60s threshold—either is fine as long as it’s consistent and documented)

Rationale:

This avoids ending the session for normal brief drops, audio reconnects, device switches, etc.

Modifier: flag unreliable end time (frequent disconnect pattern)

Warning logic

If the session has repeated short disconnects, auto-captured end time becomes less trustworthy.

Example trigger (implementer’s choice):

≥ 3 disconnect/rejoin events during the call, OR

≥ 5 minutes cumulative disconnect time, OR

disconnect within last 2 minutes of the session

UI behavior

Show a warning badge next to the auto end time:

“Frequent disconnects—please verify end time”

Allow clinician to:

accept the auto time

override manually (with a one-click “Edit”)

Data fields and auditability

Store both:

Auto-captured times (read-only, system-generated)

Final charted times (editable)

And keep an audit trail:

timestamp of override

who edited

prior value

This keeps documentation defensible.

Admin & privacy controls

Opt-in per practice and optionally per clinician.

Clear disclosure in settings: this records presence timestamps only, not content/audio/video.

Graceful fallback: if Meet data is unavailable, default to current manual workflow.