# Patient branch transfer

You can move a patient’s **home branch** to another location your practice owns—for example when they routinely visit a different clinic or after onboarding corrections.

### Who can initiate it

From **Patients**, open the row **⋮** menu or the patient profile and choose **Transfer Patient to a Branch**. The action is available when the patient already has a **`branch_id`** (anonymous draft rows without a branch may show the control disabled).

Tier note: **manual transfer** from the patient UI is not limited to Growth; **Free** and **Starter** can still move patients between branches you already use.

### Practice inbox (Growth)

When patients **request** a transfer through channels your deployment exposes (for example via mobile), pending requests can appear in the **header bell / practice inbox** for staff on **Growth** or higher. Selecting an item can deep-link into the transfer dialog with the suggested destination filled in.

Realtime updates for those inbox items align with **Growth**-tier navigation (same inbox used for appointment-related alerts where enabled).

### After a transfer

Downstream features—appointments, attachments, treatment records—respect the patient’s **current** branch context. If something looks wrong after a move, confirm the **header branch** matches where you expect to work.

### History

The transfer dialog may link to **history** so you can audit prior moves between branches.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://associhealth.gitbook.io/associhealth-docs/patients/branch-transfer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.