> For the complete documentation index, see [llms.txt](https://support-en.braver.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support-en.braver.net/guides/for-healthcare-professionals/care-channels/associate-clinical-discussion-thread-with-existing-care-channel.md).

# Create a Clinical Discussion Thread in an Existing Care Channel

## Step-by-Step

{% stepper %}
{% step %}
**From Patients tab, find and select the relevant patient.**

<div align="left"><figure><img src="/files/6HDy7Y7703QVqHgVY0C7" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**In patient file, in desired care channel, click discussion thread addition icon.**

<div align="left"><figure><img src="/files/7mLxgPBQYztCZ3XgAka3" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**At this stage, you can modify participating teams, but not individual participants.**

Click Modify.

<div align="left"><figure><img src="/files/AvJKwynp3cukcE3vsXY4" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Select team to remove.**

{% hint style="info" %}
Here, the doctor team is grayed out because the message author is part of it and therefore cannot remove themselves as a participant.
{% endhint %}

{% hint style="warning" %}
It is important to understand that teams you remove from the discussion will not be notified but will still have access to the thread content in care channel.
{% endhint %}

<div align="left"><figure><img src="/files/vhXt9hxIydeOrBBRDN0D" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**This is what your creation page will look like if you have modified participants.**

<div align="left"><figure><img src="/files/rJFSM8WC2RyPKbhYThHv" alt="" width="375"><figcaption></figcaption></figure></div>

You can add message of your choice, a title, and content before sending by clicking arrow-shaped send button.
{% endstep %}
{% endstepper %}


---

# 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 dynamically by asking a question.

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

```
GET https://support-en.braver.net/guides/for-healthcare-professionals/care-channels/associate-clinical-discussion-thread-with-existing-care-channel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
