> 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/vigilyze/algorithms-used-in-vigilyze/fatal-algorithm.md). # Fatal algorithm An algorithm has been developed to capture reports indicating that the patient died, regardless of whether the death was related to the reported adverse event. A case is considered fatal when any of the following is reported in the corresponding structured fields: * A death date * A cause of death * A cause of death after autopsy * An autopsy was performed * Seriousness classified as death * At least one reaction outcome of *fatal* * At least one reaction corresponding to a fatal term (e.g. Completed suicide, Death neonatal, Sudden infant death syndrome. For a complete list, contact Uppsala Monitoring Centre) Note that not all the above scenarios are available for every reporting format. --- # 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/vigilyze/algorithms-used-in-vigilyze/fatal-algorithm.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.