> For the complete documentation index, see [llms.txt](https://support.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.braver.net/training/pour-les-patients-et-proches-aidants.md).

# Pour les patients et proches aidants

- [Bienvenue](https://support.braver.net/training/pour-les-patients-et-proches-aidants/bienvenue.md): Nous sommes ravis de vous accueillir dans la section Formation! Cette section comprend un outil de formation qui peut s'adapter aux besoins des futurs utilisateurs de la plateforme.
- [Formation essentielle pour patients et proches aidants](https://support.braver.net/training/pour-les-patients-et-proches-aidants/formation-guidee.md): Cette formation peut être complétée de manière autonome en moins de 30 minutes. Elle vous permettra de connaitre les bases essentielles pour débuter avec Braver.


---

# 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.braver.net/training/pour-les-patients-et-proches-aidants.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.