> 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/codiac-for-health/ursa-ri/datasets/surveillance-epidemiology-and-end-results-seer.md).

# Surveillance, Epidemiology, and End Results (SEER)

## Overview

The Surveillance, Epidemiology, and End Results (SEER) Program provides information on cancer statistics in an effort to reduce the cancer burden among the U.S. population. SEER collects cancer incidence data from population-based cancer registries covering approximately 47.9 percent of the U.S. population. The SEER datasets include data on patient demographics, primary tumor site, tumor morphology, stage at diagnosis, and first course of treatment. [\[1\]](#references)

SEER offers the following datasets:

* **SEER Research Data**
  * Register with any valid email
  * Excludes geography, month and year of diagnosis, and other demographic fields
* **SEER Research Plus and NCCR Data**
  * Requires user authentication through eRA Commons or an HHS account.
  * Includes geography, month, and year of diagnosis, other demographic fields
  * Includes [National Childhood Cancer Registry (NCCR) data](https://nccrexplorer.ccdi.cancer.gov/data-products.html) excluding geography

Visit [SEER](https://seer.cancer.gov/data/) for a deeper comparison of the datasets. Learn more about SEER and SEER Datasets on the [SEER website](https://seer.cancer.gov/).

## References

1. National Cancer Institute. (n.d.).[ SEER Data](https://seer.cancer.gov/data/). Retrieved May 1, 2024.

## Resources

### Links

* [SEER Website](https://seer.cancer.gov/)
* [SEER Data Products](https://seer.cancer.gov/data/)
* [SEER Data Access Request Process](https://seerdataaccess.cancer.gov/seer-data-access)


---

# 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/codiac-for-health/ursa-ri/datasets/surveillance-epidemiology-and-end-results-seer.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.
