> 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.md). # Entering and structuring data in reports


Creating parent-child reports	Parent-child reports include additional fileds for parent information.	/pages/PM66oqBgqAKYRnjGodQo
Linking related reports	It is possible to link two or more reports if they concern the same patient or a cluster of cases.	/pages/6ZFWUh9hmzIORe32WE3H
Recording information for reports from studies and clinical trials	Use the "Study information" tab.	/pages/svuUED3PEb793xcyqciZ
Attaching additional documents to a report	Addtional documents must be of one of the supported file types and less than 15 MB.	/pages/88XzVZ1ufx1kf0juV7kM
Using the reporter address book	If the same reporter sends multiple reports, use the “Reporter address book”.	/pages/fNPa4pxS56YFiZuDiGGw
Recording patient information	Patient information is found primarily in the “Patient” section of reports.	/pages/iN1LYm3OXFWDWpfFcAxL
Coding adverse event information	Coding adverse event information with MedDRA enables users to find reports in searches and queries and allows for computer processing of cases	/pages/Yg4lRc5XscaDC5jYOXy2
Entering dechallenge and rechallenge information	Where and how to enter dechallenge and rechallenge information.	/pages/iHA3uPiyy7cC7dxNjp4x
Coding drug information with WHODrug	Coding drugs and vaccines with WHODrug enables users to find reports in searches and queries and allows for computer processing of cases.	/pages/vpBjVHkTndL83zxxPVNP
Documenting causality assessments	Casuality assessments can be documented in VigiFlow using several different methods.	/pages/Q1WtBABirSIFh9JnIS7S

--- # 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.who-umc.org/vigiflow/entering-and-structuring-data-in-reports.md?ask=&goal= ``` `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.