> For the complete documentation index, see [llms.txt](https://docs.bcbi.brown.edu/codiac-for-health/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bcbi.brown.edu/codiac-for-health/contributors.md).

# Contributors

Editors and other contributors to CODIAC for Health include faculty, staff, and students from: 

* Brown Center for Biomedical Informatics ([BCBI](https://bcbi.brown.edu/))
* Brown Research on Implementation and Dissemination to Guide Evidence Use ([BRIDGE](https://psych.med.brown.edu/research/research-core-facilities-and-resources/brown-research-implementation-and-dissemination))
* Advance RI-CTR Biomedical Informatics, Bioinformatics, and Cyberinfrastructure Enhancement ([BIBCE](https://advancectr.brown.edu/research-services/informatics-implementation-science)) Core 
* Scholarly Concentration in Biomedical Informatics ([SC-BMI](https://education.med.brown.edu/scholarly-concentrations))
* Methods in Informatics and Data Science for Health ([BIOL 1555/PHP 2561](https://bcbi.brown.edu/education))
* Data Science Fellows ([DATA 1150)](https://dsi.brown.edu/academics/data-science-fellows)

## Current Contributors <a href="#editors" id="editors"></a>

* [Liz Chen](https://vivo.brown.edu/display/echen13), PhD, FACMI (Founding Co-Editor, 2017-)
* [Neil Sarkar](https://vivo.brown.edu/display/isarkar), PhD, MLIS, ACHIP, FACMI, FAMIA (Founding Co-Editor, 2017-)
* [Karen Crowley](https://bcbi.brown.edu/people/karen-crowley-ms-phd), MS, PhD (Co-Editor, 2023-)
* [Ruben Martinez](https://vivo.brown.edu/display/rmarti64), PhD (Co-Editor - Implementation Science, 2024-)
* [Farahnaz Maroof](https://bcbi.brown.edu/people/farahnaz-maroof-ms), MS (Health Data Engineer, 2024-)
* [Paul Stey](https://it.brown.edu/people/paul-stey), PhD (Assistant CIO of Research Software Engineering and Data Science, 2017-)
* Ashok Ragavendran, PhD (Assistant Director of Computational Biology and Data Science, 2023-)
* Cole Roddy, BS (Co-Editor and Research Assistant, 2026)
* [Lauren Chiu](https://www.linkedin.com/in/laurenchiu1), BS (Research Assistant, 2026)
* [Karan Prajapati](https://www.linkedin.com/in/karanprajapati11), BS (Research Assistant, 2026)
* Emma Gilmore, BS (Research Assistant, 2026)
* Julien Song (Research Assistant, 2026)
* Camila Valdes (Research Assistant, 2026)
* Emaan Syed Ather (Research Assistant, 2026)
* [Eugenia Ampofo](http://www.linkedin.com/in/eugenia-ampofo77), BA (Research Assistant, 2026)

## Former Contributors <a href="#editors" id="editors"></a>

* [Aaron Eisman](https://aaroneisman.com/), MD, PhD (Co-Editor, 2020-2023)
* [Katie Brown](https://www.linkedin.com/in/katie-brown-rn/), MSN, RN, PhD (Co-Editor, 2020-2023)&#x20;
* [Dilum Aluthge](https://www.linkedin.com/in/dilumaluthge/), PhD, MD Candidate (Co-Editor, 2020-2023)
* Sotiris Karagounis (Research Assistant - Python Basics, 2020)
* My Vu (Research Assistant - R Basics, 2020)
* Elizabeth Song (Data Science Fellow - ML, 2021)
* Zach Sickles (Data Science Fellow, 2023)
* Kaitlyn Williams (Data Science Fellow, 2023)
* Jonah Bradenday, BA (Co-Editor and Illustrator, 2023-2025)
* Mounika Thakkallapally, MS (Health Data Engineer, 2024-2025)
* [Chris Kourkoulakos](https://www.linkedin.com/in/chris-kourkoulakos-3916aa259/) (Data Science Fellow - Python, 2024)
* [Thomas Leonard](https://www.linkedin.com/in/thomas-leonard1a/) (Data Science Fellow - R, 2024)


---

# 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://docs.bcbi.brown.edu/codiac-for-health/contributors.md?ask=<question>&goal=<user_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.