> 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/for-healthcare-professionals/patient-and-caregivers.md). # Patient and Caregiver Communication A healthcare professional or an organization can invite the patient or external collaborators who are not part of the Braver network but are still involved with the patient (e.g., parents, caregivers) to communicate and exchange information. 1. A patient or caregiver is always invited from one or more [patient files](/for-healthcare-professionals/patient-files.md) 2. To communicate with them, [care channels](/for-healthcare-professionals/care-channels.md) are created, specifically inviting them 3. These care channels gather all the information exchanged with the patient and their caregivers in a way that distinguishes them from other interprofessional exchange channels, helping to avoid errors **Feel free to consult** [**our dedicated guides**](https://support-en.braver.net/guides/for-professionals/patient-caregiver-communication) **to quickly understand how to communicate with patients and caregivers.** --- # 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://support-en.braver.net/for-healthcare-professionals/patient-and-caregivers.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.