> For the complete documentation index, see [llms.txt](https://library.xrguild.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.xrguild.org/neurotechnology-brain-tech-and-ethical-challenges/episode-17-q-and-a-with-dr.-cristin-welle-associate-professor-university-of-colorado.md). # Episode 17: Q\&A with Dr. Cristin Welle, Associate Professor, University of Colorado ## Overview **Authors:** IEEE Brain Podcast Series **Publication Date:** 10 November 2020 **Link:** **Keywords:** neuroscience, neural technology, diversity in STEM, regulatory challenges **Type:** Audio/Podcasts ## Summary In this episode, Cristin Welle explores her groundbreaking research at the intersection of neural device technology and its effects on the nervous system. Drawing on her experience at the FDA, where she specialized in neural interface technology, Cristin shares valuable perspectives on entrepreneurial opportunities, navigating regulatory challenges, and the critical need to foster diversity within the neuroscience community. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://library.xrguild.org/neurotechnology-brain-tech-and-ethical-challenges/episode-17-q-and-a-with-dr.-cristin-welle-associate-professor-university-of-colorado.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.