> For the complete documentation index, see [llms.txt](https://docs.omnivatelehealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnivatelehealth.com/consulting-provider/appointment/pending-appointments.md). # Pending Appointments View and manage pending appointments, confirm or approve them, and associate with the relevant case number. ## Overview

* In the Pending Appointments tab, you will see a list of appointments awaiting confirmation. * Patient information, including name and contact details, will be visible, along with specific appointment details such as date and time. * Under the **Pending Tab** of appointments, the provider can: * See a **dropdown** of the list of patients with cases tied to the same clinic and provider. * Change the case number before approving an appointment. Once a case number is selected and the appointment is approved, it is moved under that case. * To approve an appointment, click on the "Approve" button next to the appointment details. * If approved, the appointment will move to the Upcoming section, and the patient will be notified of the confirmation.

* To decline an appointment, click on the "Decline" button next to the appointment details. * If declined, the appointment will move to the Cancelled section, and the patient will be notified of the cancellation.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.omnivatelehealth.com/consulting-provider/appointment/pending-appointments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.