> For the complete documentation index, see [llms.txt](https://support.who-umc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.who-umc.org/vigiflow/entering-and-structuring-data-in-reports/documenting-causality-assessments.md).
# Documenting causality assessments
Casuality assessments can be documented using several different methods.
VigiFlow allows you to record causality assessment results using four different methods:
* WHO-UMC
* Naranjo
* French Method (Bégaud’s imputability method)
* WHO AEFI (for adverse events following immunisation)
{% hint style="success" %}
If your organisation uses a different method, you can write it in the *Comments* field at the bottom of the section.
{% endhint %}
To register an assessment, go to the “Assessment” section of the report:
Multiple assessments can be added, if required, using the plus sign. This is useful if the reporter or sender made their own causality assessment, but the national centre uses a different method or disagrees with the initial assessment.
{% hint style="info" %}
Refer to the VigiFlow Intermediate Course: “**ICSR processing and content**” section → “Assessment”
**Note**: VigiFlow online courses are only available to VigiFlow users. Check with your national regulatory authority for access.
{% endhint %}
---
# 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.who-umc.org/vigiflow/entering-and-structuring-data-in-reports/documenting-causality-assessments.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.
