<?xml version="1.0" encoding="UTF-8" ?>
<xml>
<records>
<record>
<title>A GWAS data fetcher with AI for Mendelian Randomization analysis</title>
<authors>
<author>WenJun Zhang</author>
</authors>
<affiliations>
<affiliation>
School of Life Sciences, Sun Yat-sen University, Guangzhou 510275, China
</affiliation>
</affiliations>
<journal>Network Pharmacology</journal>
<issn>ISSN 2415-1084</issn>
<homepage>http://www.iaees.org/publications/journals/np/online-version.asp</homepage>
<year>2026</year>
<volume>11</volume>
<issue>3-4</issue>
<startpage>62</startpage>
<endpage>89</endpage>
<publisher>International Academy of Ecology and Environmental Sciences</publisher>
<location>Hong Kong</location>
<date>
<received>28 September 2025</received>
<accepted>10 October 2025</accepted>
<published>1 December 2026</published>
</date>
<keywords>
<keyword>GWAS</keyword>
<keyword>data fetcher</keyword>
<keyword>Artificial Intelligence (AI)</keyword>
<keyword>Large Model (LM)</keyword>
<keyword>web-based tool</keyword>
<keyword>Mendelian
 Randomization (MR)</keyword>
</keywords>
<abstract>
In present study, a GWAS (Genome-Wide Association Study) data fetcher with AI was developed. It is a web-based tool that generates genetic variant data for Mendelian Randomization (MR) analysis using AI language models. It supports several AI services as DeepSeek, Google Gemini, and OpenAI GPT, etc. The fetcher supports both univariate and multivariate MR analyses. In the fetcher, the input are exposure variable(s) and outcome variable, the output are GWAS exposure and outcome data files. By leveraging AI to generate realistic data, users can practice MR analysis without accessing restricted genetic databases, test analysis pipelines safely, learn GWAS data structure and format, experiment with different exposure-outcome combinations, and develop and validate bioinformatics tools.
</abstract>
<url>http://www.iaees.org/publications/journals/np/articles/2026-11(3-4)/a-GWAS-data-fetcher-with-AI.pdf</url>
</record>
</records>
</xml>
