<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "http://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="other" dtd-version="1.2" xml:lang="en">
    <front>
        <journal-meta>
            <journal-id journal-id-type="pmc">F1000Research</journal-id>
            <journal-title-group>
                <journal-title>F1000Research</journal-title>
            </journal-title-group>
            <issn pub-type="epub">2046-1402</issn>
            <publisher>
                <publisher-name>F1000 Research Limited</publisher-name>
                <publisher-loc>London, UK</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="doi">10.12688/f1000research.177717.1</article-id>
            <article-categories>
                <subj-group subj-group-type="heading">
                    <subject>Software Tool Article</subject>
                </subj-group>
                <subj-group>
                    <subject>Articles</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>Medibot AI: a web-based software tool integrating Gemini API for informational over-the-counter medication guidance</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 1; peer review: awaiting peer review]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Llanos-S&#x00e1;nchez</surname>
                        <given-names>Piero</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Espinoza-Franco</surname>
                        <given-names>Arianna</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0009-0008-4417-9969</uri>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Portugu&#x00e9;z-Villa</surname>
                        <given-names>Fabi&#x00e1;n</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0009-0006-1646-7045</uri>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>Fern&#x00e1;ndez-Guti&#x00e9;rrez</surname>
                        <given-names>Gustavo</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-8437-5122</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Pacheco</surname>
                        <given-names>Alex</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-9721-0730</uri>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>Professional School of Systems Engineering, Universidad Nacional de Ca&#x00f1;ete, San Vicente de Ca&#x00f1;ete, Lima, 15701, Peru</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:2101080126@undc.edu.pe">2101080126@undc.edu.pe</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>19</day>
                <month>4</month>
                <year>2026</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2026</year>
            </pub-date>
            <volume>15</volume>
            <elocation-id>572</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>26</day>
                    <month>3</month>
                    <year>2026</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2026 Llanos-S&#x00e1;nchez P et al.</copyright-statement>
                <copyright-year>2026</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://f1000research.com/articles/15-572/pdf"/>
            <abstract>
                <title>Abstract*</title>
                <sec>
                    <title>Background</title>
                    <p>Self-medication for common illnesses remains widespread and may lead to inappropriate drug selection, incorrect dosage, adverse interactions, and delayed professional care. In this context, artificial intelligence (AI) can provide informational support to promote safer therapeutic decisions. This paper presents Medibot AI, a web-based intelligent system designed to generate informational over-the-counter (OTC) medication recommendations from user-reported symptoms using Google&#x2019;s Gemini API, with an emphasis on transparency, traceability, and safety warnings.</p>
                </sec>
                <sec>
                    <title>Methods</title>
                    <p>The system was developed iteratively using agile principles and implemented with a three-layer architecture: (i) user interface, (ii) recommendation and validation logic, and (iii) data persistence. The frontend was built using Next.js 18, React 18, and Tailwind CSS 3, while backend services were implemented with Node.js 20 and Prisma ORM 6.8 connected to PostgreSQL 17 (Neon). User inputs are transformed into a structured JSON prompt, and Gemini responses are constrained to return strict JSON outputs. A server-side validation layer verifies both JSON integrity and schema compliance before results are displayed or stored. The system also implements safety-oriented rules that suppress recommendations in high-risk scenarios and generate visible warnings.</p>
                </sec>
                <sec>
                    <title>Results</title>
                    <p>Medibot AI enables users to register, submit symptom descriptions with optional clinical context, obtain structured recommendations with dosage instructions and warnings, and download PDF reports. Functional integration testing confirmed stable data flow across modules and consistent schema-compliant outputs.</p>
                </sec>
                <sec>
                    <title>Conclusions</title>
                    <p>Medibot AI provides a reproducible and auditable approach for AI-assisted OTC medication guidance. While it does not replace clinical diagnosis or professional medical advice, it offers an educational tool that supports more informed and responsible self-medication practices.</p>
                </sec>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>artificial intelligence; OTC medication guidance; Gemini API; digital health; structured prompting; schema validation; Next.js; PostgreSQL</kwd>
            </kwd-group>
            <funding-group>
                <award-group id="fund-1">
                    <funding-source>This work was funded by the Directorate of Innovation and Technology Transfer of the Vice Presidency for Research at the Universidad Nacional de Ca&#x00f1;ete (UNDC) as part of the &#x201c;First Research Competition for the Development of Innovations and Intellectual Property&#x201d; [contract number 014-2024].</funding-source>
                    <award-id>contractnumber014-2024</award-id>
                </award-group>
                <funding-statement>This work was funded by the Directorate of Innovation and Technology Transfer of the Vice Presidency for Research at the Universidad Nacional de Ca&#x00f1;ete (UNDC) as part of the &#x201c;First Research Competition for the Development of Innovations and Intellectual Property&#x201d; [contract number 014-2024].&#13;
</funding-statement>
                <funding-statement>
                    <italic>The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.</italic>
                </funding-statement>
            </funding-group>
        </article-meta>
    </front>
    <body>
        <sec id="sec5" sec-type="intro">
            <title>Introduction</title>
            <p>Artificial intelligence is redefining digital health by enabling applications to interpret natural language, process clinical context, and generate user-tailored guidance.
                <sup>
                    <xref ref-type="bibr" rid="ref1">1</xref>
                </sup> Several studies have combined large language models (LLMs) with medical ontologies to support the identification of pathologies from clinical reports, capturing attributes such as type, severity, and location.
                <sup>
                    <xref ref-type="bibr" rid="ref2">2</xref>
                </sup> Moreover, recent evidence suggests that prompting strategies can improve LLM performance in clinical reasoning tasks,
                <sup>
                    <xref ref-type="bibr" rid="ref3">3</xref>
                </sup> reinforcing their ability to interpret symptom descriptions and produce contextual responses that may support automated medical guidance tools.
                <sup>
                    <xref ref-type="bibr" rid="ref1">1</xref>,
                    <xref ref-type="bibr" rid="ref4">4</xref>
                </sup> These advances are particularly valuable for making pharmaceutical knowledge more accessible to the general population in a responsible manner.</p>
            <p>Common illnesses&#x2014;such as influenza-like syndromes, cough, fever, and mild pain&#x2014;represent a frequent reason for primary care consultation. For example, acute respiratory symptoms (e.g., cough and dyspnea) and upper respiratory infections were reported among the most frequent causes of consultation in a survey of primary care professionals (34.8% of responses).
                <sup>
                    <xref ref-type="bibr" rid="ref5">5</xref>
                </sup> At the same time, self-medication without professional supervision remains widespread and is associated with risks such as incorrect self-diagnosis, inappropriate treatment selection, incorrect dosage, harmful drug interactions, and masking of more serious conditions.
                <sup>
                    <xref ref-type="bibr" rid="ref6">6</xref>,
                    <xref ref-type="bibr" rid="ref7">7</xref>,
                    <xref ref-type="bibr" rid="ref8">8</xref>
                </sup> In this context, intelligent medication guidance systems may serve as informational tools to help users make safer decisions, particularly when dealing with over-the-counter (OTC) medicines.</p>
            <p>Internationally, systems with similar objectives have been explored. For example,
                <sup>
                    <xref ref-type="bibr" rid="ref9">9</xref>
                </sup> developed a pharmaceutical conversational agent integrated with Micromedex to answer medication-related queries using natural language processing. In Europe, AI-supported clinical reasoning approaches have been studied to analyze pharmacological emergency data and support treatment decision-making.
                <sup>
                    <xref ref-type="bibr" rid="ref10">10</xref>
                </sup> In the Netherlands, intelligent systems have been shown to optimize medication alerts and recognize drug interactions using AI.
                <sup>
                    <xref ref-type="bibr" rid="ref11">11</xref>
                </sup> Similarly, research in Egypt has reported advances in predicting drug interactions using deep learning models.
                <sup>
                    <xref ref-type="bibr" rid="ref12">12</xref>
                </sup> However, many of these systems rely on complex infrastructures, closed models, or limited customization based on user profiles.</p>
            <p>In Latin America, the development of AI-assisted pharmacological tools remains at an early stage. Regional analyses indicate that AI health projects are fragmented, experimental, and often limited to isolated applications rather than integrated solutions.
                <sup>
                    <xref ref-type="bibr" rid="ref13">13</xref>
                </sup> In Colombia, for example,
                <sup>
                    <xref ref-type="bibr" rid="ref14">14</xref>
                </sup> conducted a bibliometric review showing that health chatbots are expanding&#x2014;especially in mental health and medical education&#x2014;while highlighting the need for stronger scientific justification prior to large-scale deployment. Overall, few systems in the region integrate open and modular architectures that enable personalization based on user context, which can limit scalability in academic and low-resource settings.</p>
            <p>In Peru, digital health has progressed in areas such as telemedicine and the adoption of information technologies for health services. Teleconsultation services expanded during the COVID-19 pandemic to improve access in areas with limited in-person coverage.
                <sup>
                    <xref ref-type="bibr" rid="ref15">15</xref>
                </sup> Nevertheless, institutional, regulatory, and structural challenges continue to hinder the full adoption of digital health solutions.
                <sup>
                    <xref ref-type="bibr" rid="ref16">16</xref>,
                    <xref ref-type="bibr" rid="ref17">17</xref>
                </sup> Despite this progress, initiatives specifically focused on AI-assisted OTC medication guidance appear to remain limited. Although the present development was implemented in Peru, its modular web-based design makes it potentially applicable in other contexts with similar needs.</p>
            <p>To address this gap, we propose an Intelligent System for the Recommendation of Medicines for Common Diseases using the Gemini API. This work focuses on the design and architecture of a web-based system rather than a clinical pilot implementation. The system processes user-reported symptoms and contextual information (e.g., age, allergies, and pre-existing conditions) and generates informational OTC medication recommendations and safety warnings using Google&#x2019;s Gemini API. The system is intended for informational and educational purposes only and does not provide medical diagnosis or replace professional medical advice. Users are encouraged to consult a qualified healthcare professional, particularly when symptoms are severe, persistent, or unclear.</p>
            <p>
The proposed system emphasizes transparency, adaptability, and ethical design by incorporating strict structured prompting, server-side JSON/schema validation, and safety rules that suppress recommendations in high-risk scenarios. The main contributions of this work are: (i) a modular web-based architecture for symptom-driven OTC medication guidance, (ii) structured prompt engineering with schema-constrained JSON outputs for reproducibility, and (iii) safety-oriented warning generation and risk-based recommendation suppression.</p>
        </sec>
        <sec id="sec6" sec-type="methods">
            <title>Methods</title>
            <p>In this section, we describe the methods used for the design, implementation, and operation of the Intelligent System for the Recommendation of Medicines for Common Diseases. The system is a web-based application that collects patient-reported symptoms and basic clinical context (e.g., age, sex, allergies, and pre-existing conditions), structures this information into a standardized JSON prompt, and uses the Gemini API to generate informational drug recommendations and safety warnings. The output is validated server-side and can be stored for traceability and future analysis.</p>
            <sec id="sec7">
                <title>Implementation</title>
                <p>

                    <bold>Technologies and library integration</bold>
                </p>
                <p>The system was developed using a modular and scalable architecture. The frontend was implemented with Next.js 18 and React 18, enabling hybrid SSR/CSR rendering for responsive interaction and improved performance. Tailwind CSS 3 was used to implement a responsive user interface, while ShadCN/UI provided accessible and consistent UI components.</p>
                <p>The backend logic was implemented using Next.js API routes running on Node.js 20. Data persistence was implemented with PostgreSQL 17 as the relational database management system, accessed through Prisma ORM 6.8. Input validation and response verification were implemented using Zod 3.25, ensuring strict data integrity at each stage of the workflow. Communication with the Gemini API and internal services was performed using Fetch for asynchronous HTTP requests. A singleton Prisma Client instance was used to prevent connection exhaustion in serverless deployments.</p>
                <p>

                    <bold>Deployment and file generation</bold>
                </p>
                <p>The system was deployed using Vercel (application hosting, optimized for Next.js serverless environments) and Neon (PostgreSQL database-as-a-service), enabling scalability and high availability. The system also supports automatic generation of downloadable PDF reports containing the generated recommendations and safety warnings using jsPDF 3.0.2.</p>
                <p>
                    <xref ref-type="fig" rid="f1">
Figure 1</xref> presents the general system architecture, showing the interaction between the user interface, backend services, database layer, Gemini API, and PDF generation module.</p>
                <fig fig-type="figure" id="f1" orientation="portrait" position="float">
                    <label>
Figure 1. </label>
                    <caption>
                        <title>Diagram of the architecture of the intelligent system for drug recommendations.</title>
                        <p>Source: Own elaboration.</p>
                        <p>Note: Representation of the flow between the main modules (frontend, backend, database, Gemini API, and jsPDF), from symptom entry to recommendation download by the user.</p>
                    </caption>
                    <graphic id="gr1" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/195984/ae143ced-4522-4eab-ba67-ca4c0598620d_figure1.gif"/>
                </fig>
                <p>

                    <bold>System design and development workflow</bold>
                </p>
                <p>The system was implemented iteratively using agile principles to ensure stability of the data flow and progressive validation of each module. The development workflow followed an incremental approach inspired by the five-stage model proposed by Ramos-Miller and Pacheco
                    <sup>
                        <xref ref-type="bibr" rid="ref18">18</xref>
                    </sup> (analysis, planning, implementation, review, and deployment), adapted to the requirements of a modular AI-based clinical recommendation system. The process focused on: (i) defining the architecture and security model, (ii) implementing the Gemini API integration, (iii) implementing structured persistence in PostgreSQL, (iv) implementing safety rules and warnings, and (v) validating the end-to-end integration through functional testing.</p>
                <p>

                    <bold>Database schema and persistence strategy</bold>
                </p>
                <p>The system uses PostgreSQL 17 to store user and interaction data. The relational model is structured to preserve traceability between patient data, symptom evaluations, and generated recommendations, as shown in 
                    <xref ref-type="fig" rid="f2">
Figure 2</xref>.</p>
                <fig fig-type="figure" id="f2" orientation="portrait" position="float">
                    <label>
Figure 2. </label>
                    <caption>
                        <title>Relational model of the drug recommendation system.</title>
                        <p>Source: Own elaboration.</p>
                        <p>Note: The diagram illustrates the relationships between User, Patient, Evaluation, Recommendation, and MedicationRecommendation, supporting end-to-end traceability of each interaction.</p>
                    </caption>
                    <graphic id="gr2" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/195984/ae143ced-4522-4eab-ba67-ca4c0598620d_figure2.gif"/>
                </fig>
                <p>The main entities include:
                    <list list-type="bullet">
                        <list-item>
                            <label>&#x2022;</label>
                            <p>

                                <bold>Users:</bold> Stores account data (name, email, role).</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>

                                <bold>Patients:</bold> Stores identification type, identification number, and full name.</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>

                                <bold>Evaluations:</bold> Stores structured symptom and context information (symptoms, allergies, pre-existing conditions, severity, duration, and optional clinical fields).</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>

                                <bold>Recommendations:</bold> Stores the overall model response (reason field and metadata).</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>

                                <bold>MedicationRecommendation:</bold> Stores each recommended medication entry with dosage and warnings.</p>
                        </list-item>
                    </list>
                </p>
                <p>To ensure data consistency, patients are created or updated using an upsert strategy based on identification number. Each system interaction generates a new evaluation record. Recommendations and medication entries are only stored if the AI output is valid and successfully validated against the expected schema. If either the form validation or AI response validation fails, no recommendation is persisted.</p>
                <p>

                    <bold>User interface and processing flow</bold>
                </p>
                <p>
The application provides an accessible interface where users enter symptoms in natural language and optionally provide additional context such as age, sex, weight, allergies, pregnancy status, symptom duration, severity, and current medication.</p>
                <p>The processing flow is summarized below:
                    <list list-type="order">
                        <list-item>
                            <label>1.</label>
                            <p>

                                <bold>Symptom input:</bold> The user enters free-text symptoms (e.g., &#x201c;I have a very itchy throat and a dry cough&#x201d;).</p>
                        </list-item>
                        <list-item>
                            <label>2.</label>
                            <p>

                                <bold>Prompt structuring:</bold> The system converts the input into a standardized JSON object.</p>
                        </list-item>
                        <list-item>
                            <label>3.</label>
                            <p>

                                <bold>AI processing:</bold> The structured JSON prompt is sent to the Gemini API, which returns a structured JSON response containing recommendations and warnings.</p>
                        </list-item>
                        <list-item>
                            <label>4.</label>
                            <p>

                                <bold>Server-side validation:</bold> The response is parsed as JSON and validated against the expected schema. Invalid responses are rejected and are not stored.</p>
                        </list-item>
                        <list-item>
                            <label>5.</label>
                            <p>

                                <bold>Presentation of results:</bold> The system displays an interactive panel with recommendations, instructions, and safety warnings, including reminders such as &#x201c;Consult a specialist if symptoms persist.&#x201d;</p>
                        </list-item>
                        <list-item>
                            <label>6.</label>
                            <p>

                                <bold>Persistence:</bold> Valid evaluations and recommendations are stored in PostgreSQL.</p>
                        </list-item>
                        <list-item>
                            <label>7.</label>
                            <p>

                                <bold>Export:</bold> The user can generate and download a PDF report of the results.</p>
                        </list-item>
                    </list>
                </p>
                <p>
                    <xref ref-type="fig" rid="f3">
Figure 3</xref> illustrates the general workflow from data entry to recommendation generation and presentation.</p>
                <fig fig-type="figure" id="f3" orientation="portrait" position="float">
                    <label>
Figure 3. </label>
                    <caption>
                        <title>General flow of the intelligent drug recommendation system.</title>
                        <p>Source: Own elaboration.</p>
                        <p>Note: Outline of the main stages: data entry, AI processing, and presentation of results.</p>
                    </caption>
                    <graphic id="gr3" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/195984/ae143ced-4522-4eab-ba67-ca4c0598620d_figure3.gif"/>
                </fig>
                <p>

                    <bold>Prompt Structuring</bold>
                </p>
                <p>To ensure consistency and machine-readability, the system generates a structured instruction that is sent to the Gemini API. The instruction is designed to reduce ambiguity by avoiding ranges or approximate values. The structured input is built using user-provided fields such as age, sex, symptoms, allergies, pre-existing conditions, current medication, symptom duration, and severity.</p>
                <p>The instruction embeds explicit safety constraints to prevent recommendations in high-risk scenarios (e.g., pregnancy with insufficient context, pediatric cases without weight, severe symptoms or red-flag conditions, relevant allergies, potential drug interactions, or decompensated chronic disease). In such cases, the system returns an empty recommendations list (
                    <monospace>recommendations: []</monospace>) and provides an explanatory 
                    <monospace>reason</monospace> field.</p>
                <p>The Gemini API is instructed to return only a strict JSON object following the schema below:
                    <preformat orientation="portrait" position="float" preformat-type="computer code" xml:space="preserve">

                        <monospace>
                            <styled-content style="color:#CCCCCC">{</styled-content>
                        </monospace>
&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#9CDCFE">"recommendations"</styled-content>
                            <styled-content style="color:#CCCCCC">: [</styled-content>
                        </monospace>
&#x2003;&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#CCCCCC">{</styled-content>
                        </monospace>
&#x2003;&#x2003;&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#9CDCFE">"medication"</styled-content>
                            <styled-content style="color:#CCCCCC">:</styled-content> 
                            <styled-content style="color:#CE9178">"string"</styled-content>
                            <styled-content style="color:#CCCCCC">,</styled-content>
                        </monospace>
 &#x2003;&#x2003;&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#9CDCFE">"form"</styled-content>
                            <styled-content style="color:#CCCCCC">:</styled-content> 
                            <styled-content style="color:#CE9178">"string"</styled-content>
                            <styled-content style="color:#CCCCCC">,</styled-content>
                        </monospace>
 &#x2003;&#x2003;&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#9CDCFE">"via"</styled-content>
                            <styled-content style="color:#CCCCCC">:</styled-content> 
                            <styled-content style="color:#CE9178">"string"</styled-content>
                            <styled-content style="color:#CCCCCC">,</styled-content>
                        </monospace>
 &#x2003;&#x2003;&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#9CDCFE">"amount_value"</styled-content>
                            <styled-content style="color:#CCCCCC">:</styled-content> 
                            <styled-content style="color:#F44747">number</styled-content>
                            <styled-content style="color:#CCCCCC">,</styled-content>
                        </monospace>
 &#x2003;&#x2003;&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#9CDCFE">"amount_unit"</styled-content>
                            <styled-content style="color:#CCCCCC">:</styled-content> 
                            <styled-content style="color:#CE9178">"string"</styled-content>
                            <styled-content style="color:#CCCCCC">,</styled-content>
                        </monospace>
 &#x2003;&#x2003;&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#9CDCFE">"every_hour"</styled-content>
                            <styled-content style="color:#CCCCCC">:</styled-content> 
                            <styled-content style="color:#F44747">number</styled-content>
                            <styled-content style="color:#CCCCCC">,</styled-content>
                        </monospace>
 &#x2003;&#x2003;&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#9CDCFE">"duration_days"</styled-content>
                            <styled-content style="color:#CCCCCC">:</styled-content> 
                            <styled-content style="color:#F44747">number</styled-content>
                            <styled-content style="color:#CCCCCC">,</styled-content>
                        </monospace>
 &#x2003;&#x2003;&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#9CDCFE">"moment"</styled-content>
                            <styled-content style="color:#CCCCCC">:</styled-content> 
                            <styled-content style="color:#CE9178">"string"</styled-content>
                            <styled-content style="color:#CCCCCC">,</styled-content>
                        </monospace>
&#x2003;&#x2003;&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#9CDCFE">"instructions"</styled-content>
                            <styled-content style="color:#CCCCCC">:</styled-content> 
                            <styled-content style="color:#CE9178">"string"</styled-content>
                            <styled-content style="color:#CCCCCC">,</styled-content>
                        </monospace>
&#x2003;&#x2003;&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#9CDCFE">"warnings"</styled-content>
                            <styled-content style="color:#CCCCCC">: [</styled-content>
                            <styled-content style="color:#CE9178">"string"</styled-content>
                            <styled-content style="color:#CCCCCC">]</styled-content>
                        </monospace>
&#x2003;&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#CCCCCC">}</styled-content>
                        </monospace>
&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#CCCCCC">],</styled-content>
                        </monospace>
&#x2003;&#x2003;
                        <monospace>
                            <styled-content style="color:#9CDCFE">"reason"</styled-content>
                            <styled-content style="color:#CCCCCC">:</styled-content> 
                            <styled-content style="color:#CE9178">"string|null"</styled-content>
                        </monospace>

                        <monospace>
                            <styled-content style="color:#CCCCCC">}</styled-content>
                        </monospace>
</preformat>
                </p>
                <p>

                    <bold>AI generation configuration and response validation</bold>
                </p>
                <p>To minimize variability and improve reproducibility, the system uses a fixed generation configuration when calling the Gemini API (model: gemini-2.5-flash-lite). The request is sent to the generateContent endpoint using structured prompts and is configured with temperature&#x00a0;=&#x00a0;0.2 and maxOutputTokens&#x00a0;=&#x00a0;768.</p>
                <p>To reduce malformed outputs, the system explicitly requests JSON output using responseMimeType&#x00a0;=&#x00a0;&#x2018;application/json&#x2019; and constrains the response using a predefined schema (responseSchema). After receiving the response, the system performs server-side validation in two steps:
                    <list list-type="order">
                        <list-item>
                            <label>1.</label>
                            <p>

                                <bold>JSON validation:</bold> the response must be valid JSON; otherwise, it is rejected.</p>
                        </list-item>
                        <list-item>
                            <label>2.</label>
                            <p>

                                <bold>Schema validation:</bold> the JSON structure must match the expected schema; otherwise, it is rejected.</p>
                        </list-item>
                    </list>
                </p>
                <p>Only validated responses are displayed to the user and stored in the database. This validation ensures that only well-formed and schema-compliant outputs are persisted, improving traceability and reducing the risk of unsafe or malformed recommendations.</p>
                <p>

                    <bold>Safety rules and warning generation</bold>
                </p>
                <p>The system implements safety rules to reduce harmful or misleading outputs. The system applies rule-based safety checks to identify contraindication patterns, high-severity symptom indicators, and potentially unsafe combinations. When triggered, the interface displays prominent warnings and the system may suppress medication recommendations by returning an empty list. Additionally, the system enforces strict output formatting (JSON-only responses) and applies internal validation rules to ensure that generated recommendations remain consistent and clinically cautious.</p>
                <p>

                    <bold>System testing and validation</bold>
                </p>
                <p>To verify correct system behavior and ensure the reliability of AI-generated outputs, Medibot AI was evaluated through functional and integration testing across its main modules: (i) user interface, (ii) recommendation and validation logic, and (iii) data persistence. The testing strategy focused on validating end-to-end execution, schema compliance, and safety-oriented behavior rather than clinical effectiveness.</p>
                <p>A set of synthetic test scenarios was designed to cover typical use cases and edge cases, including mild symptoms (e.g., headache, mild fever, common cold), moderate symptoms with contextual risk factors (e.g., allergies, chronic conditions), and high-risk presentations (e.g., severe symptoms, prolonged duration, contraindication flags). Each scenario was submitted through the web interface, verifying that user inputs were correctly validated and transformed into structured prompts.</p>
                <p>The following validation checks were systematically performed:
                    <list list-type="bullet">
                        <list-item>
                            <label>&#x2022;</label>
                            <p>

                                <bold>Form-level validation:</bold> Client-side input validation was enforced using schema-based constraints to prevent incomplete or inconsistent clinical context submission.</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>

                                <bold>Response integrity validation:</bold> Gemini outputs were required to return strict JSON. Responses that were not valid JSON were rejected.</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>

                                <bold>Schema compliance validation:</bold> A server-side schema validation layer verified that responses matched the expected structure (recommendation list, dosage fields, warnings, and optional reason field). Outputs failing schema validation were not displayed or persisted.</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>

                                <bold>Safety rule enforcement:</bold> The system was tested to confirm that recommendations are suppressed in high-risk cases (e.g., severe symptoms or contraindication flags), returning warnings and explanatory messages instead of medication suggestions.</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>

                                <bold>Persistence consistency:</bold> Only validated outputs were stored. If either form validation or AI response validation failed, no recommendation record was persisted in PostgreSQL, ensuring database consistency.</p>
                        </list-item>
                    </list>
                </p>
                <p>
Functional integration testing confirmed stable data flow across modules, consistent schema-compliant outputs, and correct behavior of safety rules. This validation approach supports transparency and reproducibility by ensuring that all system outputs displayed to the user correspond to auditable and schema-validated responses.</p>
            </sec>
            <sec id="sec8">
                <title>Operation</title>
                <p>

                    <bold>System Requirements</bold>
                </p>
                <p>The system requires:
                    <list list-type="bullet">
                        <list-item>
                            <label>&#x2022;</label>
                            <p>Node.js v20+ and Next.js 18</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>PostgreSQL 17 database (Neon)</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>Prisma ORM 6.8</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>Zod 3.25 for validation</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>Modern web browser compatible with ES6+ (Chrome, Edge, Firefox)</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>Stable internet connection for Gemini API interaction</p>
                        </list-item>
                    </list>
                </p>
                <p>

                    <bold>User interaction and operational flow</bold>
                </p>
                <p>The system allows users to register, provide clinical information, and obtain automated medication guidance in a structured manner. The operational workflow is as follows:
                    <list list-type="order">
                        <list-item>
                            <label>1.</label>
                            <p>

                                <bold>Registration and login:</bold> Users create an account by entering their name, email address, and password.</p>
                        </list-item>
                        <list-item>
                            <label>2.</label>
                            <p>

                                <bold>Identification data entry:</bold> After authentication, users enter an identification number, which is validated and used to automatically complete the associated name.</p>
                        </list-item>
                        <list-item>
                            <label>3.</label>
                            <p>

                                <bold>Symptom entry:</bold> Users describe their symptoms in free text and may optionally provide additional information such as age, weight, sex, allergies, and current medication.</p>
                        </list-item>
                        <list-item>
                            <label>4.</label>
                            <p>

                                <bold>Structured prompt construction:</bold> The system transforms the collected input into a standardized JSON object compatible with the Gemini API.</p>
                        </list-item>
                        <list-item>
                            <label>5.</label>
                            <p>

                                <bold>Processing via the Gemini API:</bold> The prompt is sent to the API, which returns a response constrained to JSON format.</p>
                        </list-item>
                        <list-item>
                            <label>6.</label>
                            <p>

                                <bold>Presentation of results:</bold> Recommendations and safety warnings are displayed in a results panel within the user interface.</p>
                        </list-item>
                        <list-item>
                            <label>7.</label>
                            <p>

                                <bold>Internal recording:</bold> Each interaction is stored in the database along with the date, identification number, and the generated output.</p>
                        </list-item>
                        <list-item>
                            <label>8.</label>
                            <p>

                                <bold>Completion or new query:</bold> The user may restart the form to submit a new query.</p>
                        </list-item>
                    </list>
                </p>
            </sec>
        </sec>
        <sec id="sec9">
            <title>Use cases</title>
            <p>This section presents the main use cases of the intelligent drug recommendation system for common diseases powered by the Gemini API. The scenarios illustrate typical interactions between users and the platform, from account creation to the generation of structured over-the-counter (OTC) medication guidance. Each use case describes how the system captures user inputs, processes clinical context, produces recommendations, and displays safety warnings, maintaining an informative and educational purpose.</p>
            <sec id="sec10">
                <title>Case 1. User registration</title>
                <p>In this use case, the user accesses the registration page and provides their name, email address, and password (
                    <xref ref-type="fig" rid="f4">
Figure 4</xref>). Once registration is completed, the user can authenticate and access the medication recommendation module. User credentials are securely stored to enable personalized access in future sessions.</p>
                <fig fig-type="figure" id="f4" orientation="portrait" position="float">
                    <label>
Figure 4. </label>
                    <caption>
                        <title>User registration form with fields for name, email, and password.</title>
                        <p>Source: Own elaboration.</p>
                        <p>Note: Screenshot of the registration interface used to create user accounts and enable authenticated access to the system.</p>
                    </caption>
                    <graphic id="gr4" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/195984/ae143ced-4522-4eab-ba67-ca4c0598620d_figure4.gif"/>
                </fig>
            </sec>
            <sec id="sec11">
                <title>Case 2. Data entry for medication recommendations</title>
                <p>In this use case, the user accesses the main consultation form and enters their identification number. The system validates the document and automatically completes the associated full name. The user then provides additional clinical context, including symptoms, age, weight, sex, allergies, current medication, symptom duration, and perceived severity (
                    <xref ref-type="fig" rid="f5">
Figure 5</xref>).</p>
                <fig fig-type="figure" id="f5" orientation="portrait" position="float">
                    <label>
Figure 5. </label>
                    <caption>
                        <title>User data entry form with automatic name validation based on ID number.</title>
                        <p>Source: Own elaboration.</p>
                        <p>Note: Screenshot of the main consultation form showing symptom input and optional clinical context fields (e.g., age, sex, weight, allergies, duration, severity). The system validates the identification number and auto-completes the associated full name.</p>
                    </caption>
                    <graphic id="gr5" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/195984/ae143ced-4522-4eab-ba67-ca4c0598620d_figure5.gif"/>
                </fig>
                <p>After completing the form, the user selects &#x201c;Generate Recommendation&#x201d;, which triggers prompt structuring and submission to the Gemini API.</p>
            </sec>
            <sec id="sec12">
                <title>Case 3. Displaying results and warnings</title>
                <p>In this use case, the system processes the submitted information and presents the generated recommendations in a results panel. The output includes suggested medications, dosage and usage instructions, and safety warnings (e.g., contraindications or recommendations to consult a healthcare professional if symptoms persist). Additionally, the user can export the results as a downloadable PDF report for personal reference (
                    <xref ref-type="fig" rid="f6">
Figure 6</xref>).</p>
                <fig fig-type="figure" id="f6" orientation="portrait" position="float">
                    <label>
Figure 6. </label>
                    <caption>
                        <title>Results panel with drug recommendations and informational warnings.</title>
                        <p>Source: Own elaboration.</p>
                        <p>Note: Example output view displaying schema-validated OTC medication recommendations, dosage instructions, and safety warnings. Users can export the results as a downloadable PDF report.</p>
                    </caption>
                    <graphic id="gr6" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/195984/ae143ced-4522-4eab-ba67-ca4c0598620d_figure6.gif"/>
                </fig>
            </sec>
            <sec id="sec13">
                <title>Case 4. Severity management and critical warnings</title>
                <p>In this use case, when the system detects high-risk or severe symptom descriptions (e.g., &#x201c;severe headache&#x201d;), it prioritizes user safety by generating a prominent warning that encourages immediate medical evaluation. In these situations, the system may suppress medication recommendations and instead return an explanatory message indicating that self-medication is not advised (
                    <xref ref-type="fig" rid="f7">
Figure 7</xref>).</p>
                <fig fig-type="figure" id="f7" orientation="portrait" position="float">
                    <label>
Figure 7. </label>
                    <caption>
                        <title>Warning generated by the system for symptoms of high severity.</title>
                        <p>Source: Own elaboration.</p>
                        <p>Note: Example of safety-oriented behavior where the system detects high-risk symptom descriptions and prioritizes warnings. In such cases, medication recommendations may be suppressed, and the user is advised to seek professional medical evaluation.</p>
                    </caption>
                    <graphic id="gr7" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/195984/ae143ced-4522-4eab-ba67-ca4c0598620d_figure7.gif"/>
                </fig>
                <p>Overall, these use cases demonstrate that the system supports a clear and safety-oriented user experience. By combining structured data capture, AI-based processing, and explicit warnings, the platform delivers informative medication guidance while reinforcing that outputs do not replace professional medical assessment. The modular design also supports scalability and future extensions.</p>
            </sec>
        </sec>
        <sec id="sec14" sec-type="discussion">
            <title>Discussion</title>
            <p>Medibot AI was developed to address the need for accessible and structured medication guidance, particularly in contexts where timely access to professional medical consultation may be limited. By integrating Google&#x2019;s Gemini API, the system leverages large language model capabilities to interpret patient-reported symptoms and clinical context and generate over-the-counter (OTC) medication recommendations accompanied by safety warnings. Unlike traditional clinical decision support tools that rely on fixed rule-based engines or curated drug databases, Medibot AI is designed as a modular web-based system that emphasizes structured prompting, response validation, and traceability of outputs.</p>
            <p>A key contribution of this work is the adoption of a structured JSON-based prompting strategy combined with server-side response verification. The system constrains model outputs through strict formatting rules, schema expectations, and validation procedures, reducing the likelihood of malformed or ambiguous recommendations. This is particularly relevant in health-related applications, where unconstrained natural language generation may lead to unclear dosage instructions or unsafe guidance. In addition, the system includes safety-oriented behavior such as suppressing recommendations and returning explanatory reasons when risk conditions are detected (e.g., severe symptoms, red flags, pediatric cases without sufficient context, pregnancy with incomplete information, relevant allergies, or potential drug interactions).</p>
            <p>Despite these design measures, the effectiveness of Medibot AI remains dependent on multiple factors. First, the accuracy and safety of recommendations are strongly influenced by the quality and completeness of user-provided data, since missing or incorrect clinical context may limit the system&#x2019;s ability to detect contraindications or high-risk scenarios. Second, although the Gemini API provides advanced language understanding and reasoning capabilities, its coverage of drug interactions and clinical edge cases may not be fully comprehensive, which can reduce reliability in complex situations.
                <sup>
                    <xref ref-type="bibr" rid="ref19">19</xref>
                </sup> Therefore, Medibot AI should be interpreted as a guidance-oriented tool, rather than a substitute for professional diagnosis or prescription.</p>
            <p>From a data quality perspective, the METRIC framework proposed by
                <sup>
                    <xref ref-type="bibr" rid="ref20">20</xref>
                </sup> highlights essential dimensions such as accuracy, completeness, and representativeness. These dimensions are directly relevant to Medibot AI, since the system operates on patient-reported symptom narratives and contextual inputs that may vary widely across users. Ensuring structured input capture and validation is therefore critical to reduce noise and improve the consistency of generated outputs.</p>
            <p>Ethical and professional considerations are central to the responsible deployment of AI in healthcare. The system must preserve patient autonomy, ensure transparency regarding its limitations, and reinforce that outputs do not replace expert evaluation. In this regard, Medibot AI incorporates warnings and safety rules to encourage users to seek professional assistance when symptoms are severe, persistent, or unclear. Additionally, professional responsibility remains essential: healthcare personnel should treat Medibot AI as a complementary decision-support mechanism rather than a replacement for clinical judgment. Adequate training and clear usage protocols are necessary to improve acceptance and prevent misuse.
                <sup>
                    <xref ref-type="bibr" rid="ref21">21</xref>,
                    <xref ref-type="bibr" rid="ref22">22</xref>
                </sup>
            </p>
            <p>Future work could strengthen the system by improving clinical reliability and expanding its scope. Potential enhancements include integrating additional automated safety layers (e.g., stronger contraindication detection), expanding the coverage of medication scenarios, and incorporating mechanisms that align recommendations with updated scientific evidence. Collaboration with academic institutions and hospitals would be particularly valuable for expert-driven validation, iterative improvement, and formal evaluation of system performance in real-world settings.
                <sup>
                    <xref ref-type="bibr" rid="ref23">23</xref>
                </sup> Moreover, evaluating the system from the perspective of multiple stakeholders&#x2014;patients, clinicians, and administrators&#x2014;could support improvements in usability, integration into healthcare workflows, and long-term sustainability.
                <sup>
                    <xref ref-type="bibr" rid="ref23">23</xref>
                </sup>
            </p>
            <p>Overall, Medibot AI represents a relevant step toward practical AI-assisted medication guidance through a modular architecture and safety-oriented design. While important limitations remain, the system provides a structured and auditable foundation for future research and development aimed at improving access to reliable health information in a responsible manner.</p>
        </sec>
        <sec id="sec15" sec-type="conclusions">
            <title>Conclusions</title>
            <p>This study presented the design and implementation of Medibot AI, a web-based intelligent system for informational over-the-counter (OTC) medication guidance using the Gemini API. The system demonstrates that large language models can be integrated into a modular architecture capable of transforming user-reported symptoms and clinical context into structured prompts, producing schema-constrained JSON outputs, and delivering recommendations accompanied by safety warnings. The incorporation of server-side validation, persistence mechanisms, and traceability supports robustness and reproducibility of the generated results.</p>
            <p>Despite these contributions, the system is subject to limitations inherent to LLM-based solutions. Recommendation quality depends on the accuracy and completeness of user-provided inputs and on the model&#x2019;s ability to generate consistent structured responses. Although the proposed validation and safety rules reduce the risk of malformed or unsafe outputs, Medibot AI is not intended to provide diagnosis or replace professional medical advice. Therefore, its outputs should be interpreted as educational guidance, and users should consult healthcare professionals when symptoms are severe, persistent, or unclear.</p>
            <p>Future work may focus on strengthening clinical reliability and scalability. This includes expanding the medication knowledge base, improving safety coverage for contraindications and drug interactions, and integrating retrieval-based strategies (e.g., RAG) to ground recommendations in verified pharmacological sources. Additional improvements could include multilingual support, more refined risk stratification, and systematic evaluation protocols involving expert review and real-world usability studies.</p>
            <p>Overall, Medibot AI provides a practical contribution toward responsible AI-assisted medication guidance by combining structured prompting, validation, and safety-oriented design. These elements support the development of transparent and auditable systems that can enhance access to reliable health information while maintaining ethical and clinical caution.</p>
        </sec>
        <sec id="sec16">
            <title>Ethics and consent</title>
            <p>This article describes the development of a software tool and does not report results from a clinical study or interventions involving patients. The system is intended for informational and educational purposes only and does not provide medical diagnosis, clinical decision-making, or professional medical advice. Medibot AI is not a medical device. Users voluntarily enter information to obtain guidance related to over-the-counter medications. The interface includes visible safety warnings encouraging consultation with a healthcare professional, particularly when symptoms are severe, persistent, or unclear.</p>
        </sec>
        <sec id="sec17">
            <title>Software availability*</title>
            <p>

                <italic toggle="yes">Software available from:</italic> 
                <ext-link ext-link-type="uri" xlink:href="https://medibot-ai-prod.vercel.app/">

                    <italic toggle="yes">https://medibot-ai-prod.vercel.app/</italic>
</ext-link>
            </p>
            <p>

                <italic toggle="yes">Source code available from:</italic> 
                <ext-link ext-link-type="uri" xlink:href="https://github.com/PIEROLS15/medibot-ai">

                    <italic toggle="yes">https://github.com/PIEROLS15/medibot-ai
</italic>
</ext-link>
            </p>
            <p>

                <italic toggle="yes">Archived source code at time of publication:</italic> 
                <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5281/zenodo.17714829">

                    <italic toggle="yes">https://doi.org/10.5281/zenodo.17714829</italic>
</ext-link>

                <italic toggle="yes">.</italic>
                <sup>
                    <xref ref-type="bibr" rid="ref25">25</xref>
                </sup>
            </p>
            <p>

                <italic toggle="yes">License:*</italic> MIT License &#x2014; 
                <ext-link ext-link-type="uri" xlink:href="https://opensource.org/license/MIT">

                    <italic toggle="yes">https://opensource.org/license/MIT</italic>
</ext-link>
            </p>
        </sec>
        <sec id="sec18">
            <title>Data privacy and security</title>
            <p>The system stores user account information (e.g., name and email) and consultation history (e.g., symptoms and related form fields) in a PostgreSQL database to support traceability and reproducibility of outputs. Access requires authentication. API credentials are protected using environment variables, and input validation is enforced using Zod to reduce the risk of malformed data submissions.</p>
            <p>No real patient data were used or publicly shared. The publicly archived dataset consists exclusively of synthetic scenarios intended for reproducibility and validation purposes.</p>
        </sec>
    </body>
    <back>
        <sec id="sec21" sec-type="data-availability">
            <title>Data availability*</title>
            <sec id="sec22">
                <title>Underlying data</title>
                <p>This work describes a software package. No real-world clinical datasets were generated or collected, and no patient-identifiable data were obtained.</p>
                <p>
To support transparency and reproducibility, we provide a set of synthetic test scenarios and validation artifacts (e.g., JSON cases, expected outputs, and schema definitions) archived in Zenodo. These files enable independent verification of the input/output structure and safety-related behaviors of Medibot AI without exposing sensitive clinical information.</p>
                <p>Underlying data available from: Zenodo: Medibot AI: Synthetic Test Scenarios and Validation Artifacts (Underlying Data), 
                    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5281/zenodo.18437408">https://doi.org/10.5281/zenodo.18437408</ext-link>.
                    <sup>
                        <xref ref-type="bibr" rid="ref24">24</xref>
                    </sup>
                </p>
                <p>Data are available under the terms of the 
                    <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International license (CC BY 4.0)</ext-link>. 
                    <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>
                </p>
            </sec>
        </sec>
        <ack>
            <title>Acknowledgements</title>
            <p>
We would like to express our sincere gratitude to the Universidad Nacional de Ca&#x00f1;ete (UNDC) and to the teachers, students, and collaborators who contributed to the development of this work as part of the academic training process.</p>
        </ack>
        <ref-list>
            <title>References*</title>
            <ref id="ref1">
                <label>1</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Aracena</surname>
                            <given-names>C</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Villena</surname>
                            <given-names>F</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Arias</surname>
                            <given-names>F</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Aplicaciones de aprendizaje autom&#x00e1;tico en salud.</article-title>
                    <source>

                        <italic toggle="yes">Rev. Med. Clin. Condes.</italic>
</source>
                    <year>Nov. 2022</year>;<volume>33</volume>(<issue>6</issue>):<fpage>568</fpage>&#x2013;<lpage>575</lpage>.
                    <pub-id pub-id-type="doi">10.1016/j.rmclc.2022.10.001</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref2">
                <label>2</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Torre</surname>
                            <given-names>L-PS</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Quir&#x00f3;s</surname>
                            <given-names>P</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Mieres</surname>
                            <given-names>HG</given-names>
                        </name>
</person-group>:
                    <article-title>Detecci&#x00f3;n Autom&#x00e1;tica de Patolog&#x00ed;as en Notas Cl&#x00ed;nicas en Espa&#x00f1;ol Combinando Modelos de Lenguaje y Ontolog&#x00ed;as M&#x00e9;dicos.</article-title>
                    <year>Oct. 2024</year>;<fpage>24</fpage>&#x2013;<lpage>27</lpage>. Accessed: Oct. 16, 2025.
                    <ext-link ext-link-type="uri" xlink:href="https://arxiv.org/pdf/2410.00616">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref3">
                <label>3</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Wu</surname>
                            <given-names>C-K</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Chen</surname>
                            <given-names>W-L</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Chen</surname>
                            <given-names>H-H</given-names>
                        </name>
</person-group>:
                    <article-title>Large Language Models Perform Diagnostic Reasoning.</article-title>
                    <year>Jul. 2023</year>.
                    <pub-id pub-id-type="doi">10.48550/arXiv.2307.08922</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref4">
                <label>4</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Chocr&#x00f3;n</surname>
                            <given-names>P</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Abella</surname>
                            <given-names>&#x00c1;</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Maeztu</surname>
                            <given-names>G</given-names>
                            <prefix>de</prefix>
                        </name>
</person-group>:
                    <article-title>ContextMEL: Classifying Contextual Modifiers in Clinical Text.</article-title>
                    <source>

                        <italic toggle="yes">Procesamiento del Lenguaje Natural.</italic>
</source>
                    <year>Sep. 2020</year>;<volume>65</volume>:<fpage>45</fpage>&#x2013;<lpage>52</lpage>.
                    <pub-id pub-id-type="doi">10.26342/2020-65-5</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref5">
                <label>5</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Abdel-Aal</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lisspers</surname>
                            <given-names>K</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Williams</surname>
                            <given-names>S</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Prioritising primary care respiratory research needs: results from the 2020 International Primary Care Respiratory Group (IPCRG) global e-Delphi exercise.</article-title>
                    <source>

                        <italic toggle="yes">NPJ Prim. Care Respir. Med.</italic>
</source>
                    <year>Jan. 2022</year>;<volume>32</volume>(<issue>1</issue>):<fpage>6</fpage>.
                    <pub-id pub-id-type="pmid">35091570</pub-id>
                    <pub-id pub-id-type="doi">10.1038/s41533-021-00266-4</pub-id>
                    <pub-id pub-id-type="pmcid">PMC8799668</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref6">
                <label>6</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Panda</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Pradhan</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Mohapatra</surname>
                            <given-names>G</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Drug-related problems associated with self-medication and medication guided by prescription: A pharmacy-based survey.</article-title>
                    <source>

                        <italic toggle="yes">Indian J. Pharm.</italic>
</source>
                    <year>2016</year>;<volume>48</volume>(<issue>5</issue>):<fpage>515</fpage>&#x2013;<lpage>521</lpage>.
                    <pub-id pub-id-type="pmid">27721536</pub-id>
                    <pub-id pub-id-type="doi">10.4103/0253-7613.190728</pub-id>
                    <pub-id pub-id-type="pmcid">PMC5051244</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref7">
                <label>7</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Ruiz</surname>
                            <given-names>M</given-names>
                        </name>
</person-group>:
                    <article-title>Risks of Self-Medication Practices.</article-title>
                    <source>

                        <italic toggle="yes">Curr. Drug Saf.</italic>
</source>
                    <year>Oct. 2010</year>;<volume>5</volume>(<issue>4</issue>):<fpage>315</fpage>&#x2013;<lpage>323</lpage>.
                    <pub-id pub-id-type="doi">10.2174/157488610792245966</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref8">
                <label>8</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zeid</surname>
                            <given-names>W</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hamed</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Mansour</surname>
                            <given-names>N</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Prevalence and associated risk factors of self-medication among patients attending El-Mahsama family practice center, Ismailia, Egypt.</article-title>
                    <source>

                        <italic toggle="yes">Bull. Natl. Res. Cent.</italic>
</source>
                    <year>Dec. 2020</year>;<volume>44</volume>(<issue>1</issue>):<fpage>92</fpage>.
                    <pub-id pub-id-type="doi">10.1186/s42269-020-00351-7</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref9">
                <label>9</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Preininger</surname>
                            <given-names>AM</given-names>
                        </name>

                        <name name-style="western">
                            <surname>South</surname>
                            <given-names>B</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Heiland</surname>
                            <given-names>J</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Artificial intelligence-based conversational agent to support medication prescribing.</article-title>
                    <source>

                        <italic toggle="yes">JAMIA Open.</italic>
</source>
                    <year>Jul. 2020</year>;<volume>3</volume>(<issue>2</issue>):<fpage>225</fpage>&#x2013;<lpage>232</lpage>.
                    <pub-id pub-id-type="pmid">32734163</pub-id>
                    <pub-id pub-id-type="doi">10.1093/jamiaopen/ooaa009</pub-id>
                    <pub-id pub-id-type="pmcid">PMC7382615</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref10">
                <label>10</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Hartjes</surname>
                            <given-names>MG</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Richir</surname>
                            <given-names>MC</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Cazaubon</surname>
                            <given-names>Y</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Enhancing therapeutic reasoning: key insights and recommendations for education in prescribing.</article-title>
                    <source>

                        <italic toggle="yes">BMC Med. Educ.</italic>
</source>
                    <year>Nov. 2024</year>;<volume>24</volume>(<issue>1</issue>):<fpage>1360</fpage>.
                    <pub-id pub-id-type="pmid">39587582</pub-id>
                    <pub-id pub-id-type="doi">10.1186/s12909-024-06310-4</pub-id>
                    <pub-id pub-id-type="pmcid">PMC11590475</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref11">
                <label>11</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Graafsma</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Murphy</surname>
                            <given-names>RM</given-names>
                        </name>

                        <name name-style="western">
                            <surname>van de Garde</surname>
                            <given-names>EMW</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>The use of artificial intelligence to optimize medication alerts generated by clinical decision support systems: a scoping review.</article-title>
                    <source>

                        <italic toggle="yes">J. Am. Med. Inform. Assoc.</italic>
</source>
                    <year>May 2024</year>;<volume>31</volume>(<issue>6</issue>):<fpage>1411</fpage>&#x2013;<lpage>1422</lpage>.
                    <pub-id pub-id-type="pmid">38641410</pub-id>
                    <pub-id pub-id-type="doi">10.1093/jamia/ocae076</pub-id>
                    <pub-id pub-id-type="pmcid">PMC11105146</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref12">
                <label>12</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Marzouk</surname>
                            <given-names>NH</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Selim</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Elattar</surname>
                            <given-names>M</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>A comprehensive landscape of AI applications in broad-spectrum drug interaction prediction: a systematic review.</article-title>
                    <source>

                        <italic toggle="yes">Aust. J. Chem.</italic>
</source>
                    <year>Sep. 2025</year>;<volume>17</volume>(<issue>1</issue>):<fpage>141</fpage>.
                    <pub-id pub-id-type="pmid">40973960</pub-id>
                    <pub-id pub-id-type="doi">10.1186/s13321-025-01093-2</pub-id>
                    <pub-id pub-id-type="pmcid">PMC12447627</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref13">
                <label>13</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Saban</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Esteban</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Rubinstein</surname>
                            <given-names>A</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>The Impact of Artificial Intelligence on Healthcare: Perspectives and Approaches for Latin America and the Caribbean.</article-title>
                    <year>2023</year>.
                    <pub-id pub-id-type="doi">10.48060/tghn.126</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref14">
                <label>14</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Cort&#x00e9;s Torres</surname>
                            <given-names>JE</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Salda&#x00f1;a Moreno</surname>
                            <given-names>CE</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Mendoza Moncada</surname>
                            <given-names>JS</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>El chatbot aplicado a salud. Una revisi&#x00f3;n bibliom&#x00e9;trica.</article-title>
                    <source>

                        <italic toggle="yes">Rev Comun Salud.</italic>
</source>
                    <year>Dec. 2024</year>;<volume>15</volume>:<fpage>1</fpage>&#x2013;<lpage>18</lpage>.
                    <pub-id pub-id-type="doi">10.35669/rcys.2025.15.e355</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref15">
                <label>15</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Rees</surname>
                            <given-names>GH</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Peralta</surname>
                            <given-names>F</given-names>
                        </name>
</person-group>:
                    <article-title>Telemedicine in Peru: origin, implementation, pandemic escalation, and prospects in the new normal.</article-title>
                    <source>

                        <italic toggle="yes">Oxford Open Digital Health.</italic>
</source>
                    <year>Jan. 2024</year>;<volume>2</volume>.
                    <pub-id pub-id-type="pmid">40230963</pub-id>
                    <pub-id pub-id-type="doi">10.1093/oodh/oqae002</pub-id>
                    <pub-id pub-id-type="pmcid">PMC11932397</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref16">
                <label>16</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Curioso</surname>
                            <given-names>WH</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Coronel-Chucos</surname>
                            <given-names>LG</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Henr&#x00ed;quez-Suarez</surname>
                            <given-names>M</given-names>
                        </name>
</person-group>:
                    <article-title>Integrating Telehealth for Strengthening Health Systems in the Context of the COVID-19 Pandemic: A Perspective from Peru.</article-title>
                    <source>

                        <italic toggle="yes">Int. J. Environ. Res. Public Health.</italic>
</source>
                    <year>May 2023</year>;<volume>20</volume>(<issue>11</issue>):<fpage>5980</fpage>.
                    <pub-id pub-id-type="pmid">37297584</pub-id>
                    <pub-id pub-id-type="doi">10.3390/ijerph20115980</pub-id>
                    <pub-id pub-id-type="pmcid">PMC10252887</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref17">
                <label>17</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Ponce de Le&#x00f3;n Sierra</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Merma Pillaca</surname>
                            <given-names>A</given-names>
                        </name>
</person-group>:
                    <article-title>Transformaci&#x00f3;n digital en el sector salud peruano: retos y avances recientes.</article-title>
                    <source>

                        <italic toggle="yes">Rev. Panam. Salud Publica.</italic>
</source>
                    <year>Dec. 2024</year>;<volume>48</volume>:<fpage>1</fpage>.
                    <pub-id pub-id-type="doi">10.26633/RPSP.2024.138</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref18">
                <label>18</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Ramos-Miller</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Pacheco</surname>
                            <given-names>A</given-names>
                        </name>
</person-group>:
                    <article-title>Towards inventory control excellence: An innovative approach based on a web-based platform.</article-title>
                    <source>

                        <italic toggle="yes">F1000Res.</italic>
</source>
                    <year>Dec. 2023</year>;<volume>12</volume>:<fpage>1471</fpage>.
                    <pub-id pub-id-type="doi">10.12688/f1000research.140745.2</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref19">
                <label>19</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Khosravi</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zare</surname>
                            <given-names>Z</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Mojtabaeian</surname>
                            <given-names>SM</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Artificial Intelligence and Decision-Making in Healthcare: A Thematic Analysis of a Systematic Review of Reviews.</article-title>
                    <source>

                        <italic toggle="yes">Health Serv. Res. Manag. Epidemiol.</italic>
</source>
                    <year>Jan. 2024</year>;<volume>11</volume>.
                    <pub-id pub-id-type="doi">10.1177/23333928241234863</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref20">
                <label>20</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Schwabe</surname>
                            <given-names>D</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Becker</surname>
                            <given-names>K</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Seyferth</surname>
                            <given-names>M</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>The METRIC-framework for assessing data quality for trustworthy AI in medicine: a systematic review.</article-title>
                    <source>

                        <italic toggle="yes">NPJ Digit. Med.</italic>
</source>
                    <year>Aug. 2024</year>;<volume>7</volume>(<issue>1</issue>):<fpage>203</fpage>.
                    <pub-id pub-id-type="pmid">39097662</pub-id>
                    <pub-id pub-id-type="doi">10.1038/s41746-024-01196-4</pub-id>
                    <pub-id pub-id-type="pmcid">PMC11297942</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref21">
                <label>21</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Harishbhai Tilala</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Kumar Chenchala</surname>
                            <given-names>P</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Choppadandi</surname>
                            <given-names>A</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Ethical Considerations in the Use of Artificial Intelligence and Machine Learning in Health Care: A Comprehensive Review.</article-title>
                    <source>

                        <italic toggle="yes">Cureus.</italic>
</source>
                    <year>Jun. 2024</year>;<volume>16</volume>:<fpage>e62443</fpage>.
                    <pub-id pub-id-type="pmid">39011215</pub-id>
                    <pub-id pub-id-type="doi">10.7759/cureus.62443</pub-id>
                    <pub-id pub-id-type="pmcid">PMC11249277</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref22">
                <label>22</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Dankwa-Mullan</surname>
                            <given-names>I</given-names>
                        </name>
</person-group>:
                    <article-title>Health Equity and Ethical Considerations in Using Artificial Intelligence in Public Health and Medicine.</article-title>
                    <source>

                        <italic toggle="yes">Prev. Chronic Dis.</italic>
</source>
                    <year>Aug. 2024</year>;<volume>21</volume>:<fpage>240245</fpage>.
                    <pub-id pub-id-type="pmid">39173183</pub-id>
                    <pub-id pub-id-type="doi">10.5888/pcd21.240245</pub-id>
                    <pub-id pub-id-type="pmcid">PMC11364282</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref23">
                <label>23</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Giebel</surname>
                            <given-names>GD</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Raszke</surname>
                            <given-names>P</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Nowak</surname>
                            <given-names>H</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Improving AI-Based Clinical Decision Support Systems and Their Integration Into Care From the Perspective of Experts: Interview Study Among Different Stakeholders.</article-title>
                    <source>

                        <italic toggle="yes">JMIR Med. Inform.</italic>
</source>
                    <year>Jul. 2025</year>;<volume>13</volume>:<fpage>e69688</fpage>.
                    <pub-id pub-id-type="doi">10.2196/69688</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref24">
                <label>24</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Llanos-S&#x00e1;nchez</surname>
                            <given-names>PD</given-names>
                        </name>
</person-group>:
                    <article-title>Medibot AI: Synthetic Test Scenarios and Validation Artifacts (Underlying Data).</article-title>
                    <year>Jan. 30, 2026</year>.
                    <pub-id pub-id-type="doi">10.5281/zenodo.18437408</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref25">
                <label>25</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Llanos-S&#x00e1;nchez</surname>
                            <given-names>PD</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Espinoza-Franco</surname>
                            <given-names>AA</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Portugu&#x00e9;z-Villa</surname>
                            <given-names>FA</given-names>
                        </name>
</person-group>:
                    <article-title>Medibot AI.</article-title>
                    <source>

                        <italic toggle="yes">Zenodo.</italic>
</source>
                    <year>Nov. 25, 2025</year>.
                    <pub-id pub-id-type="doi">10.5281/zenodo.17714829</pub-id>
                </mixed-citation>
            </ref>
        </ref-list>
    </back>
</article>
