Skip to content
Datasets/cervix_msk_2023

Cervical Cancer (MSK, Clin Cancer Res 2023)

OpenMachine-extracted
Investigator-initiated cohort (harmonized in cBioPortal)Available from cBioPortal

Targeted sequencing of 177 cervical tumors and their matched normal samples via MSK-IMPACT.

Can it answer your research question?

2 of 6 supported
  • Overall survival

    Supported

    Vital status and time are populated; median follow-up 2.1 years; 174 cases with follow-up; endpoint: overall survival.API

  • Progression or recurrence

    Not measured

    This field was not among those probed for this repository.

  • Treatment response

    Not supported

    No treatment response is recorded in the harmonized records.API

  • Which drug was given

    Not measured

    This field was not among those probed for this repository.

  • Stage-adjusted modelling

    Not measured

    This field was not among those probed for this repository.

  • Analysis by race or ethnicity

    Supported

    ETHNICITY is informative for 97% of cases.API

Judged from the repository’s own field completeness (thresholds). “Not measured” means we have not probed that field for this record, not that the data lack it.

At a glance

Every percentage is the repository’s own record of what is filled in
CasesAPI
177
177 samples
Measurement types
3
Follow-upAPI
2.1 years
for 174 of 177 cases; overall survival
Treatment responseAPI
Not recorded

SubjectCALC

Cervix

As filed by the repository

Cervixtissue

Who is in the cohortAPI

A usable value“Not reported” or “unknown”No value recorded
  • Sex177 Female
  • Race131 WHITE · 14 BLACK OR AFRICAN AMERICAN · 12 ASIAN-FAR EAST/INDIAN SUBCONT · 12 2 other · 6 PT REFUSED TO ANSWER · 2 no value recorded
  • Ethnicity153 Non-Spanish; Non-Hispanic · 16 Spanish NOS; Hispanic NOS, Latino NOS · 1 Dominican Republic · 1 1 other · 2 Unknown whether Spanish or not · 4 no value recorded
  • Vital status102 DECEASED · 73 LIVING · 2 no value recorded

What was measured, and on how many

3 measurement types, 2 covering the whole cohort.

  • Mutation calls (panel, exome or genome)177 of 177 samples · 100%
  • Copy number alterations177 of 177 samples · 100%
  • Structural variants / fusionscount not published
Platform, files and data levels
AssayPlatformFilesLevels
Mutation calls (panel, exome or genome)API--processed matrix
Copy number alterationsAPI--processed matrix
Structural variants / fusionsAPI-25-
How complete all 7 clinical fields are - 7 informative for at least 80% of cases

A field counts as informative only when it holds a real value. “Not reported” blocks an analysis just as a missing field does. Fields marked 1:n can hold several records per case, so they show the share of cases with any record.

Informative - a usable valuePresent but uninformative - “not reported” or “unknown”Absent - no value recorded

Outcome

  • Overall Survival StatusAPI99%

Follow-up

  • Overall Survival (Months)API98%

Diagnosis

  • Oncotree CodeAPI100%
  • Primary Tumor SiteAPI100%

Demographics

  • SexAPI100%
  • Ethnicity CategoryAPI97%
  • Race CategoryAPI96%

Access

OpenDownload without an account.API

Processed data download from the cBioPortal study page or its public REST API; no account required. Primary raw data remain wherever the original investigators deposited them.

Open components
harmonized mutation, copy-number, expression and clinical files
License
Per-study terms; cBioPortal asks that the original study be cited
Citation requirement
Cite the original publication, and cite cBioPortal if the portal's harmonized files were used.

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.

Analyzed the dataCALC
-
could not be measured for this dataset
Declared using it
-
named in a data availability statement
Cited the paper
20
attention to the publication, not reuse of the data
Against expectation
Not assessed
Reuse cannot be traced for this dataset
No accession is specific enough to search the literature for, so we cannot tell how often these data have been reused. That is a limit of the measurement, not a finding about the dataset. It is also a barrier in itself: a researcher cannot find prior work to build on.
Reuse assessment
  • Not assessed: this dataset has no accession specific enough for citation-based reuse tracing, so a shortfall cannot be measured.

Compared against rgi-huber-v2. See Methods for the model.

Original publication

  • 37643132
    Friedman et al. Clin Cancer Res 2023PMID 37643132API

Articles that analyzed the data

Not searchable. See the note above.

Community examples

Share your example

Analyses 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

cBioPortal: clinical data and the full study bundlepython
import requests, pandas as pd

STUDY = "cervix_msk_2023"
base = "https://www.cbioportal.org/api"
clin = requests.get(f"{base}/studies/{STUDY}/clinical-data",
                    params={"clinicalDataType": "PATIENT", "projection": "SUMMARY"}, timeout=60).json()
patients = pd.DataFrame(clin).pivot_table(index="patientId", columns="clinicalAttributeId",
                                          values="value", aggfunc="first")
print(patients.shape)
profiles = requests.get(f"{base}/studies/{STUDY}/molecular-profiles", timeout=60).json()
print([p["molecularProfileId"] for p in profiles])
# Whole study as flat files: https://cbioportal-datahub.s3.amazonaws.com/cervix_msk_2023.tar.gz
This page as data: limitations firstbash
curl -s https://cd2s.vercel.app/data/datasets/cbio-cervix-msk-2023.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

  1. 1
    Open the study in cBioPortalFor people5 minutes

    Harmonized molecular and clinical files are open. Cite the original publication, and cite cBioPortal if the portal's harmonized files were used.

    https://www.cbioportal.org/study/summary?id=cervix_msk_2023

    Generated from repository policy. Check the linked policy before downloading.

  2. 2
    Download the whole study as a zipFor peopleminutes

    The datasets page carries the staging files used by the portal.

    https://www.cbioportal.org/datasets

    Generated from repository policy. Check the linked policy before downloading.

  3. 3
    Or pull the staging files with git-lfsFor people

    Study folders are named by study id under public/.

    git clone https://github.com/cBioPortal/datahub.git && cd datahub
    git -c lfs.fetchexclude="" lfs pull -I public/cervix_msk_2023
    https://github.com/cBioPortal/datahub

    Generated from repository policy. Check the linked policy before downloading.

  4. 4
    Read the study straight from the REST APIFor agents

    No key is required; pace requests when sweeping many studies.

    curl -s 'https://www.cbioportal.org/api/studies/cervix_msk_2023/clinical-data?clinicalDataType=PATIENT&projection=SUMMARY'
    https://docs.cbioportal.org/web-api-and-clients/

    Generated from repository policy. Check the linked policy before downloading.

Provenance

All of it, and more, is in this record’s JSON.

Identifiers

Versions and verification

Metadata retrieved
18 Sept 2026
Review status
Machine-extracted
Data generation funding
Funded data generation

Funding

Awards resolved through NIH RePORTER. Awards that paid to generate these data are listed apart from awards that paid to reuse them. Both are returns on NCI investment, but different ones.

Funded data generation

  • P30CA008748Antitumor AssessmentElisa de Stanchina, FRANCESCA M GANYFY2025-2026API

For softwarerecord JSON