List every patient the logged-in account can act on.

Returns the account holder plus any linked dependents (e.g. children). Each entry has a stable patient_id (MRN) used by all other tools, and is_account_holder marks the logged-in user. Use these IDs — never names — for the patient-scoped tools.

List a patient's appointments (upcoming by default).

Each appointment includes an opaque appointment_id (pass it to reschedule_appointment) and a can_reschedule flag. Read-only.

Resolve names → IDs from a patient's own visit history.

Returns the specialties, doctors, clinics and regions seen in this patient's appointments, each as {id, name}. Use this to discover the opaque IDs that search_slots needs (e.g. the region id and a specialty id), then narrow further with list_search_filters. Read-only.

List the clinics, doctors and languages bookable for a region + specialty selection.

Use this after picking a region and specialty to enumerate valid clinic and doctor IDs before calling search_slots. Read-only.

Find available appointment slots for a specialty/region (optionally doctor/clinic).

Each returned slot carries a booking_string — the single-use handle you pass to book_appointment or reschedule_appointment, and a visit_type (Center | Phone | PhoneAdvice). The portal has no visit-type search filter, so to get in-person ("Center") visits, choose an in-person specialty and/or filter the returned slots by visit_type. next_search_date hints the StartTime to use to page further into the future. Re-run this immediately before booking, because a booking_string can expire. Read-only.

Book an available slot for a specific patient.

patient_id is mandatory so a booking can never land on the wrong person's record. The portal validates the slot at booking time (read-before-write); if the slot is gone you get a clear error and nothing is booked. Returns the new appointment id on success.

Note: reporting_id defaults to empty. It's unverified whether the API requires it (the captured bookings carried one from the out-of-scope triage flow); if booking fails citing it, that's the likely cause.

Move an existing appointment to a different slot (atomic; never cancels without rebooking).

Only moves to the slot you explicitly pass. With require_earlier (default), it first confirms the new slot is strictly earlier than the current appointment and otherwise refuses — so an unattended 'earlier slot' routine can't accidentally move an appointment later. The portal re-validates the slot at reschedule time.