> 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/ursa-ri/health-data-partners/data-requests.md).
# Data Requests
The Brown Center for Biomedical Informatics (BCBI) and the Advance RI-CTR Biomedical Informatics, Bioinformatics and Cyberinfrastructure Enhancement (BIBCE) Core serve as liaisons between researchers and health data partners to create and submit accurate and complete data requests as well as oversee the governance of health data transferred to and accessed at Brown University. Each health data partner has unique administrative processes for requesting their data as well as guidelines for working with the data and sharing results.
Please submit an [Advance RI-CTR Service Request Form](https://advancectr.brown.edu/schedule-service-consultation) to start the process.
Example Health Research Process
## Types of Data Requests
**Aggregate Statistics** – basic counts and descriptive statistics to characterize a population of interest (e.g., number of patients or encounters meeting specified criteria).
**De-Identified Dataset** – as defined by the HIPAA Privacy Rule, excludes the 18 protected health information ([**PHI**](https://docs.bcbi.brown.edu/codiac-for-health/observational-research/best-practices/protected-health-information-phi)) elements that could be used to identify individuals or the individual's relatives, employers, or household members.
**Limited Dataset** – as defined by the HIPAA Privacy Rule, includes a limited set of identifiable information that excludes 16 direct identifiers but may include city, state, zip code, elements of date, and other numbers, characteristics, or codes not listed as direct identifiers.
**Identified Dataset** – in some cases, direct identifiers may be needed (e.g., street addresses for geocoding or demographics for linking datasets) that may be subsequently removed to create a limited or de-identified dataset.
## URSA Data Request Form
The URSA Data Request Form (UDRF) was designed by the Advance RI-CTR BIBCE Core and BCBI for requests made to Rhode Island health data partners. The UDRF is used to structure the cohort definition and dataset extraction fields in a computable manner. It can also be used to document a research study extraction specification or communicate extraction details to research team programmers. Each section should be reviewed and approved by the study PI.
Contact the Advance RI-CTR BIBCE Core via the [Advance RI-CTR Service Request Form](https://advancectr.brown.edu/schedule-service-consultation) to initiate a new data request. The BIBCE Core will provide a copy of the URSA Data Request Form as well as additional data request process details.
---
# 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/ursa-ri/health-data-partners/data-requests.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.
