> 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/completed-appointments.md). # Completed Appointments View completed appointments, chat history, appointment details, and download relevant documents like summaries and prescriptions. ## Overview Completed appointments are those that have successfully occurred, either as a referral or appointment. All appointments marked as **completed** will be listed in the **Completed Tab**. You can view patient details, including summaries from the completed appointment. Appointment information such as date, time, and relevant notes are accessible through the appointment summary.

## Actions in the Completed Tab: * **Chat**: You can chat with the patient for up to **3 more days** after the appointment. After this period, you can only view previous chat history.

* **Eye Icon**: View detailed information about the appointment, including **appointment notes**, **prescriptions**, **lab notes**, **radiology notes**, and **referral details**. * **Three Dots**: Access the **PDF** of the **appointment summary**, **prescription**, **lab notes**, and **radiology notes.** --- # 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/completed-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.