> 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/datasets/syntheticri-2026-synthetic-healthcare-records-for-rhode-island.md).

# SyntheticRI 2026: Synthetic Healthcare Records for Rhode Island

## Overview

The SyntheticRI 2026 datasets consist of patient-centric synthetic health records representing the population of Rhode Island. The data was generated using Synthea™, an open-source simulation framework that models the clinical journey of synthetic patients from birth to death. The primary objective of these datasets is to provide a realistic environment for healthcare research, software development, and clinical informatics training.

These datasets contains no real-world patient data. Because all individuals and clinical events are computationally generated from the ground up, the records are entirely free of personally identifiable information (PII). This allows for unrestricted sharing and analysis in compliance with HIPAA and GDPR standards.

To use these datasets for educational or reseach purposes, please contact <bcbi@brown.edu>&#x20;

## Methodology and Generation

The patient population and their respective health trajectories were simulated using the Synthea™ generator (Walonoski et al., 2018). The simulation utilizes a modular, logic-based approach where clinical outcomes are driven by transition-based state machines.

Demographics: Patient demographics, including age, gender, race, and socio-economic status, are statistically aligned with the United States Census Bureau data for the state of Rhode Island to ensure regional representativeness.

Clinical Logic: Disease progression, treatment pathways, and clinical encounters are dictated by over 80 validated clinical modules. These modules are developed based on peer-reviewed clinical guidelines and public health statistics from sources such as the CDC, NIH, and various specialty medical associations.

The commands used to generate these datasets, including the specific seed, are as follows:

```
./run_synthea -s 20260508 -p 1000 "Rhode Island"
./run_synthea -s 20260508 -p 300000 "Rhode Island"
```

## Standardized Healthcare Vocabularies&#x20;

SyntheticRI records include codes from the following vocabularies:

* Conditions and Diagnoses: SNOMED-CT (Systematized Nomenclature of Medicine – Clinical Terms)
* Observations and Vitals: LOINC (Logical Observation Identifiers Names and Codes)
* Medications: RxNorm
* Vaccines: CVX (Clinical Vaccine) codes

## Resources

### Articles

* Walonoski, J., Klaus, M., Granger, E., Hall, D., Gregorowicz, A., Neyarapally, G., Watson, A., & McLachlan, J. (2018). [Synthea: An approach, method, and software mechanism for generating synthetic electronic health records](https://www.google.com/search?q=https://doi.org/10.1093/jamia/ocx079). Journal of the American Medical Informatics Association, 25(3), 230–238.

### Links

* Synthea Documentation & Wiki: Synthetic Health Research. (n.d.). [Synthea Wiki](https://www.google.com/search?q=https://github.com/synthetichealth/synthea/wiki)[.](https://www.google.com/search?q=https://github.com/synthetichealth/synthea/wiki)
* Source Code: Synthetic Health. (2024). [Synthea Patient Population Simulator](https://github.com/synthetichealth/synthea).


---

# 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/datasets/syntheticri-2026-synthetic-healthcare-records-for-rhode-island.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.
