Source
The meeting itself — found from sitemap — VSee
Checked for VSee on 10 Nov 2026
- Page
- https://developers.vsee.com/use-cases/patient-video-session
- Checked
- 10 Nov 2026, 18:09 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:f388a0efbfd03f78f0905351da704407d2f2f4541855c1e579a3a584f5296eff
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Patient video session flow Report an error
“Log patient in using SSO, create an intake and walk-in visit, then redirect them directly into a video call with a provider.”
-
SSO patient endpoint Report an error
“Call SSO with patient details (type=200). Use ?fields=vsee to include VSee ID and token in the response.”
-
Required credentials Report an error
“This use case requires the following credentials: X-ApiKey Issued during API access onboarding X-ApiSecret Issued during API access onboarding X-AccountCode Your clinic account code, issued during onboarding”
-
Intakes endpoint Report an error
“Create an intake data object to capture the reason for visit. Uses the patient's access token from Step 1.”
-
Walkin visit endpoint Report an error
“Create a walk-in visit. The intake_id links the intake data from Step 2.”
-
Video redirect URL Report an error
“https://{your_clinic}.vseepreview.com/auth?sso_token={sso_token}&next=/visits/start/{visit_id}”
-
Patient code max length Report an error
“Unique patient identifier on your end (max 128 chars)”
-
Walkin video or chat Report an error
“Redirect the patient directly into the video call/chat page for their visit.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Skeptic The meeting itself