CPTAC HNSCC Discovery Study
Can it answer your research question?
4 of 6 supportedOverall survival
SupportedVital status and time are populated; median follow-up 2.0 years; 106 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
Supportedtreatment_outcomeis populated for 0.8% of cases; criteria: Complete Response.APIWhich drug was given
Not supportedtherapeutic_agentsis recorded for no case in the harmonized records.APIStage-adjusted modelling
Supportedajcc_pathologic_stageis informative for 89% of cases.APIAnalysis by race or ethnicity
SupportedRace is informative for 87% 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
- Sex97 male · 15 female · 12 not reported
- Race68 white · 33 other · 7 asian · 16 not reported
- Ethnicity2 hispanic or latino · 122 not reported
- Vital status66 Alive · 41 Dead · 17 Not Reported
What was measured, and on how many
- Phosphoproteome mass spectrometry (TMT11 / DDA)124 of 124 · 100%
- Proteome mass spectrometry (TMT11 / DDA)124 of 124 · 100%
How complete all 27 clinical fields are - 11 informative for at least 80% of cases
Access
Direct download from the PDC portal or its API; no account required
- Open components
- 2 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 dataset1
- Accession found in text0
- Declared using it7
- Analyzed the data18
Against comparable datasets
- Analyzed it18
- Expected~14
- Reuse is within the expected range for comparable datasets (index +0.30).
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 = "PDC000222"
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-cptac-hnscc-discovery-study.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. This record spans 2 PDC studies; repeat for each.
https://pdc.cancer.gov/pdc/study/PDC000222 - 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 PDC000222: 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="PDC000222")["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 2021
- Metadata retrieved
- 18 Sept 2026
- Review status
- Machine-extracted
- Data generation funding
- Funded data generation
Funding
Funded reuse of these data
- T32CA203690Translational Breast Cancer Research Training ProgramSuzanne AW Fuqua, Mothaffar Fahed RimawiAPI
Funded infrastructure or harmonization
- U24CA271037Michigan Center for Translational Cancer ProteogenomicsSaravana Mohan Dhanasekaran, Alexey I NesvizhskiiAPI
- U24CA210993Systems Biology based Proteogenomic Translator for Cancer Marker Discovery towards Precision MedicineERIC E SCHADT, Pei WangAPI
- U24CA210986Center of Excellence for High Throughput Proteogenomic CharacterizationSTEVEN A CARR, MICHAEL A GILLETTEAPI
- U24CA210985The Comprehensive Proteome Characterization Center at Johns Hopkins: High Precision Discovery and Confirmation of Genoproteomic TargetsDANIEL Wanyui CHAN, ZHEN ZHANGAPI
- U24CA210979Integrated high throughput proteogenomic data analysis center for CPTACChet Birger, GAD A GETZAPI
- U24CA210972Proteogenomic Data Analysis for Cancer Systems Biology and Clinical TranslationLi Ding, David FenyoAPI
- U24CA210967University of Michigan Proteogenomics Data Analysis CenterARUL M CHINNAIYAN, Saravana M DhanasekaranAPI
- U24CA210955PNNL Proteome Characterization CenterTao Liu, RICHARD D SMITHAPI
- U24CA210954iPGDAC, An Integrative Proteogenomic Data Analysis Center for CPTACBing ZhangAPI
- U01CA214125MICROSCALED PROTEOGENOMICS FOR CANCER CLINICAL TRIALSMeenakshi Anurag, STEVEN A CARRAPI