Patient use case
Log patient in using SSO, create an intake, then create an asynchronous e-consult. Providers assigned to the room will see it and can accept it.
POST /users/sso · auth: API Key + Secret
Call SSO with patient details (type=200). Use ?fields=vsee to include VSee ID and token in the response.
headers:
| Field | Required | Description |
|---|---|---|
X-ApiKey | yes | API Key |
X-ApiSecret | yes | API Secret |
X-AccountCode | yes | Account code |
queryParams:
| Field | Required | Description |
|---|---|---|
fields | no | Set to 'vsee' to include VSee ID and token |
bodyFields:
| Field | Required | Description |
|---|---|---|
first_name | yes | Patient's first name |
last_name | yes | Patient's last name |
type | yes | User type: 200 = Patient |
email | no | Patient email address |
code | yes | Unique patient identifier on your end (max 128 chars) |
POST /intakes · auth: User Token
Create an intake data object to capture the reason for visit. Uses the patient's access token from Step 1.
headers:
| Field | Required | Description |
|---|---|---|
X-ApiToken | yes | User access token from SSO response |
X-AccountCode | yes | Account code |
bodyFields:
| Field | Required | Description |
|---|---|---|
type | yes | Intake type (1 = standard) |
room_code | yes | Room code for the waiting room |
reason_for_visit | no | Reason for visit / chief complaint |
POST /visits/add_econsult · auth: User Token
Create an asynchronous e-consult. Only intake_id and room_code are needed.
headers:
| Field | Required | Description |
|---|---|---|
X-ApiToken | yes | User access token from SSO response |
X-AccountCode | yes | Account code |
bodyFields:
| Field | Required | Description |
|---|---|---|
intake_id | yes | Intake ID from Step 2 |
room_code | yes | Room code — all providers in this room will see the e-consult |
The e-consult can be viewed by the patient through the Patient Dashboard. Follow the "Patient Dashboard" use case to redirect the patient to their dashboard where they can track the e-consult status.