TCGA Breast Cancer Proteome
Can it answer your research question?
3 of 6 supportedOverall survival
SupportedVital status and time are populated; median follow-up 3.1 years; 105 cases with follow-up; endpoint: overall survival.API
Progression or recurrence
Not supportedprogression_or_recurrenceis informative for no case in the harmonized records.APITreatment response
Not supportedtreatment_outcomeis populated for no case in the harmonized records.APIWhich drug was given
Not supportedtherapeutic_agentsis recorded for no case in the harmonized records.APIStage-adjusted modelling
Supportedtumor_stageis informative for 95% of cases.APIAnalysis by race or ethnicity
SupportedRace is informative for 86% of cases.API
At a glance
Every percentage is the repository’s own record of what is filled inSubjectCALC
As filed by the repository
Who is in the cohortAPI
- Sex103 female · 2 male · 4 not reported
- Race69 white · 15 asian · 9 black or african american · 1 1 other · 15 not reported
- Ethnicity80 not hispanic or latino · 3 hispanic or latino · 26 not reported
- Vital status92 Alive · 13 Dead · 4 no value recorded
What was measured, and on how many
- Proteome mass spectrometry (iTRAQ4 / DDA)109 of 109 · 100%
Platform, files and data levels
| Assay | Platform | Files | Levels |
|---|---|---|---|
| Proteome mass spectrometry (iTRAQ4 / DDA)API | iTRAQ4 | - | raw, peptide/protein matrix |
How complete all 27 clinical fields are - 12 informative for at least 80% of cases
Access
Direct download from the PDC portal or its API; no account required
- Open components
- 1 analytical fraction studies
- License
- Open access under the PDC data use terms
- Citation requirement
- Cite the PDC study identifier and the study's primary publication; PDC asks that the consortium be acknowledged.
What it is good for
Written and checked by a reviewer, not generated from metadata.
No reviewed research questions yet. The measurements and field completeness above are machine-extracted and still useful for judging fit.
What it cannot tell you
Written by a reviewer against the source, not inferred from what is missing.
No reviewed limitations yet. Check the field completeness chart above before committing to an analysis. Low coverage on an endpoint you need is the most common blocker.
Who has used it
Articles that analyzed these data, counted separately from articles that only cited the paper. Only the first counts as reuse.
What articles did with it
- Mentioned the dataset0
- Accession found in text0
- Declared using it7
- Analyzed the data18
Against comparable datasets
- Analyzed it18
- Expected~4
- Reuse is within the expected range for comparable datasets (index +1.88).
Articles that analyzed the data
Community examples
Share your exampleAnalyses someone ran on these data end to end, each with a receipt recording when it ran, against which packages and for how long.
Nobody has shared an analysis of this dataset yet. The examples on other datasets cover the common patterns and can be adapted - and if you adapt one, it belongs here.
Start here
Starter code generated from this record’s own identifiers, then the access steps.
Get the data in code
PDC: file manifest through the GraphQL APIpython
import requests
PDC_STUDY = "PDC000173"
API = "https://proteomic.datacommons.cancer.gov/graphql"
def gql(query, **variables):
r = requests.post(API, json={"query": query, "variables": variables}, timeout=180)
r.raise_for_status()
body = r.json()
if body.get("errors"):
raise RuntimeError(body["errors"][0]["message"])
return body["data"]
# filesPerStudy only fills its fields when given the study UUID: called with the
# pdc_study_id it returns the right number of rows with every column null.
study = gql("""query ($id: String!) {
study(pdc_study_id: $id acceptDUA: true) { study_id study_name }
}""", id=PDC_STUDY)["study"][0]
files = gql("""query ($sid: String!) {
filesPerStudy(study_id: $sid acceptDUA: true) {
file_id file_name file_type data_category md5sum file_size signedUrl { url }
}
}""", sid=study["study_id"])["filesPerStudy"]
print(study["study_name"], "-", len(files), "files")
for f in files[:3]:
print(f["file_name"], f["data_category"], f["file_size"])
# Each signedUrl.url is a time-limited download link; stream it to disk with requests.get(url, stream=True).This page as data: limitations firstbash
curl -s https://cd2s.vercel.app/data/datasets/pdc-tcga-breast-cancer-proteome.json | python3 -c '
import json, sys
r = json.load(sys.stdin)
for l in r["limitations"]:
print(l["severity"].upper(), "-", l["statement"][:120])
print("survival endpoint:", r["longitudinal"]["has_survival_endpoint"], "| treatment response:", r["longitudinal"]["has_treatment_response"])'Access steps
- Open the study in the PDC portalFor people
Proteomic data are released open; the portal's use guidelines still apply.
https://pdc.cancer.gov/pdc/study/PDC000173 - Accept the data use guidelines and downloadFor people
The portal asks for acknowledgement and citation, not a data access request.
https://pdc.cancer.gov/pdc/data-use-guidelines - Resolve the study UUID, then fetch the file manifestFor agents
filesPerStudy keys on the study UUID, not on PDC000173: called with the pdc_study_id it returns the right number of rows with every column null. Resolve the UUID first and pass the terms acknowledgement.
https://pdc.cancer.gov/data-dictionary/publicapi-documentation/python - <<'PY' import requests API = "https://proteomic.datacommons.cancer.gov/graphql" def gql(query, **variables): r = requests.post(API, json={"query": query, "variables": variables}, timeout=180) r.raise_for_status() body = r.json() if body.get("errors"): raise RuntimeError(body["errors"][0]["message"]) return body["data"] study = gql('query($id:String!){ study(pdc_study_id:$id acceptDUA:true){ study_id } }', id="PDC000173")["study"][0] files = gql('query($sid:String!){ filesPerStudy(study_id:$sid acceptDUA:true)' '{ file_id file_name file_size } }', sid=study["study_id"])["filesPerStudy"] print(len(files), "files") PY
Provenance
All of it, and more, is in this record’s JSON.
Versions and verification
- Released
- 1 Jan 2022
- Metadata retrieved
- 18 Sept 2026
- Review status
- Machine-extracted
- Data generation funding
- Funded data generation
Funding
Funded reuse of these data
- R21CA274620Predicting actionable cancer vulnerabilities enabled by mutant-directed protein-protein interactionsANDREY IVANOVAPI
- R01CA258857Targeting posttranslational modifications of CD73 in TNBCsYong Wan, Bin ZhangAPI
- R01CA258765Targeting posttranslational modifications of B7-H4 in carcinogenesis and therapyYong WanAPI
- R01CA250110Targeting Posttranslational Modifications in Breast CarcinogenesisYong WanAPI
- R01CA250101The distinct role of cysteinyl leukotriene receptor for myeloid-derived suppressive cellsBin ZhangAPI
- R01CA222963WEE1 inhibition and tumor immunityBin ZhangAPI
- R01CA202963Targeting interplay between KLF4 and PRMT5 in carcinogenesisYong WanAPI
- R01CA202948Interplay between ER and TGF-b in carcinogenesisYong WanAPI
- R01CA252713Canine MHC-I genotyping and tumor specific neoantigen determinationWilliam Hildebrand, SHAYING ZHAOAPI
- R50CA265089Definition and perturbation of cell-regulatory heterogeneities in solid tumorsLixin WangAPI
Funded infrastructure or harmonization
- P50CA217691Project 3: Targeting Bax signaling to overcome treatment resistance in NSCLCXingming Deng, Haian FuAPI
- P30CA138292Clinical Protocol and Data ManagementR. Donald Harvey, THERESA W GILLESPIEAPI
- P30CA060553Cancer Center AdministrationAleksandar Zafirovski, LEONIDAS C. PLATANIASAPI
- U54CA274499Systems Analysis of Stress-adapted Cancer Organelles (SASCO) CenterKevin A Janes, Matthew J LazzaraAPI
- P30CA044579BSR - SR ComponentHong Zhu, Nicholas Eugene ShermanAPI