> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/care/encounters/encounters-in-the-patient-profile.md).

# Encounters in the Patient Profile

## Overview

All encounters for a patient are accessible directly from the patient's profile. The Encounters tab provides a comprehensive history of every interaction – past, present, and scheduled – for that patient.

## Accessing Encounters from the Patient Profile

1. Open the patient profile
2. Click the **Encounters** tab
3. All encounters are listed in reverse chronological order

## Encounter List Display

Each encounter in the list shows:

* **Encounter type** (e.g., Initial Intake, Follow-up, Telehealth)
* **Date and time** – when the encounter occurred or is scheduled
* **Assigned care team member** – the clinician or coordinator who owns the encounter
* **Status** – Scheduled, In Progress, Draft, Completed, or Cancelled
* **Summary** – key notes or assessment highlights

Click any encounter to open the full detail view.

## Filtering and Sorting Encounters

Use the filter controls above the encounter list to:

* Filter by **status** (show only Completed, only Draft, etc.)
* Filter by **encounter type** (show only telehealth visits, for example)
* Filter by **date range** (show encounters from the last 30 days, last 6 months, etc.)
* **Sort** by date (newest or oldest first)

## Creating a New Encounter

To schedule a new encounter directly from the patient profile:

1. Click **+ New Encounter** in the Encounters tab
2. Complete the encounter details
3. Save or schedule the encounter

For full instructions on creating and completing encounters, see [Create, Modify, Complete Encounters](/care/encounters/encounters-create-modify-complete.md).


---

# 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.welkinhealth.com/care/encounters/encounters-in-the-patient-profile.md?ask=<question>&goal=<user_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.