Full appointment context
Review the appointment facts, status, clinic, provider, records, and any cancellation reason throughout the whole appointment lifecycle.
Patient careAvailable
Appointment details
A complete view of one appointment, including timing, lifecycle status, versioned clinical intake, its issued prescription, attached records, preparation messages, requested information, and telemedicine readiness.
What you can do here
Revised provider timing
If the care team records that a virtual visit is running late, the current schedule revision shows a revised expected start in the appointment time zone. This does not reschedule the visit, prove that an in-app notice was delivered or read, or enable external channels.
Preparation thread
Before the session starts, add notes or answer requests from the clinic. Once the visit is in progress or terminal, the thread becomes read-only.
Secure care messages
For a booked, active, or completed virtual visit, use the separate appointment-bound care thread for non-urgent patient and care-team messages. It shows the current owner, open or closed state, and unread truth. No response time or business-hours coverage is configured, external notifications and proxy access are off, and attachments remain unavailable until a governed thread-specific grant is approved.
Records and requested information
Attach records from My Records before the session and review any information or lab report requests from the doctor.
Device readiness
For confirmed telemedicine visits, run an appointment-bound local camera, microphone, speaker, secure-context, client, and API-reachability check. Denied or dismissed permissions, missing or busy devices, offline state, and unsupported APIs have distinct recovery guidance. Backgrounding, resume, permission, device, or network changes release temporary media and require a rerun. The saved result is authoritative for local compatibility only and never enables clinical video.
Clinical intake
Answer the clinic's published visit questions, save a server revision, and submit it for clinician review. Required answers and clinical review signals remain visible. Submission does not authorize entry or replace the separate identity, location, consent, readiness, and provider checks.
Current visit safety
For a telemedicine appointment, confirm your current physical location, reachable callback, privacy, decision capacity, people present, required support, safety concerns, and the local emergency and disconnect plan. The form never copies a profile address or silently reads browser location.
Exact virtual-care consent
Read the booked, jurisdiction-specific consent text and explicitly grant, decline, or withdraw virtual-care consent. A grant is an electronic acknowledgement only and does not start video or approve recording, AI, added participants, or pharmacy transmission.
Visit prescription
After the visit, review the issued medication directions and open the patient copy in My Records when it is available.
Separate pharmacy permission
For an eligible virtual visit, choose only from clinic-reviewed destinations, read the destination-bound published text, and explicitly grant, decline, or withdraw permission. The decision does not send a prescription or prove pharmacy acceptance, fill, or dispensing.
Released after-visit instructions
A patient-visible summary appears only after a governed publication. Draft and clinician-reviewed text stays private. If the booked visit policy has an in-app summary-ready rule, only the exact current release event can create that care update; it does not enable export, email, or sharing.
Follow-up obligation
After the consultation, review the due window, visit format, and action recorded by the care team. When self-booking is allowed, choose an eligible time inside the exact plan window; the appointment and plan link commit together. The system records distinct due and overdue events and may create an in-app reminder only when the booked visit policy contains that optional rule. Communication history remains the delivery truth. Completed comes only from the exact linked appointment, while cancellation, no-show, reschedule, or a record mismatch stays visible for care-team review. You may also explicitly decline an offered plan.
Audited communication history
Review appointment-linked communication intent states without exposing recipient addresses or message content. Confirmation, reschedule, cancellation, reminder, and provider-delay updates come from exact appointment evidence. Summary-ready and result-ready updates require the exact current patient release, while follow-up reminders require the current due or overdue event. Scheduled, queued, provider accepted, delivered, failed, suppressed, and support-required states remain distinct; creating an intent is not delivery, local dispatch and expiry are evidence events, and delivered never means read. External channels remain disabled.
Protected care-update inbox
Open the notification bell to review delivered in-app care updates across your appointments. Unread and read come from durable clinical receipts, not the expiring alert row. Opening an update records one audited read receipt before navigating to the exact patient appointment.
Clinic-specific communication choices
Search the supported language and time-zone catalogs, then choose consent separately for care, appointment transactions, and marketing plus a preference for each channel. A channel preference does not enable an unavailable adapter and is never evidence of delivery.
Tips
- Speaker readiness is confirmed by you after the tone plays because browsers cannot prove that audio reached your speakers.
- The camera and microphone are tested independently and every temporary track is released after the probe or when the app moves to the background.
- The local check does not exercise deployed signaling, STUN, TURN, or the clinical media service. Use its support or appointment actions when entry remains blocked.
- Records attached here are granted only for the appointment scope.
- A Saved intake status means the server acknowledged the revision. If another revision wins, reload before continuing so no answer is silently overwritten.