get_user_profile
Returns the account’s tier, capabilities, connections, patients, region support, and health-record counts.
Each entry in
capabilities has ready: true, or ready: false with needs; some entries also include better. The source labels explain how an input can be supplied:
capabilities.visit.atPayment lists the identity fields still needed at the payment page. A provider visit needs first name, last name, date of birth, gender, and a home address. The payment page collects missing values; save them in the profile first to avoid entering them there.
Example response
update_patient_info
Updates patient demographics, contact details, or medical history. Fields are optional; use patientId from get_user_profile to target a dependent. Without it, the account’s default patient is updated.
Medical-history lists merge by title by default: matching titles are updated, additional titles are appended, and unmentioned entries remain. Set
replaceMedicalHistory: true when supplying a complete list.
The result includes success, patientId, and updatedFields. Medical-history field names in updatedFields use medication, condition, and allergy.