> 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/patients/patient-creation-and-search.md).

# My Patients: Create and Search

## Overview

The My Patients view provides your personalized patient list and tools for finding and creating patient records in Welkin.

## Searching for Patients

### Quick Search

Use the search bar at the top of the Patients section to find patients by:

* First Name + Middle Name + Last Name
* Phone
* Secondary Phone
* Email
* Secondary Email
* MRN
* NRIC
* Access Code

Results appear as you type. Click a result to open the patient profile.

### Advanced Filters

Use the **Filter** panel to narrow your patient list by:

* DOB
* Program
* Phase
* Region
* Territory
* Timezone
* Care Member

The **Phase** filter becomes active after you select a **Program**.

## Creating a New Patient

1. Click the **Create** button
2. Fill in the required fields:

* **First Name** and **Last Name**
* Any other fields configured as required in Designer

3. Optionally add additional demographic information
4. Click **Create** to add the new patient

## My Patients vs. All Patients

* **My Patients** shows only patients directly assigned to you or your care team
* **All Patients** shows the full patient population (subject to role permissions)

To switch between these views, use the **Care Member** filter: with your user selected, you see **My Patients**; remove your user from the filter to see **All Patients**.

{% embed url="<https://www.youtube.com/watch?v=Ak682txfU3s>" %}


---

# 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/patients/patient-creation-and-search.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.