Skip to content

The Cellular Geography of Therapeutic Resistance in Cancer

MixedProject-curated
Human Tumor Atlas NetworkAvailable from HTANDana-Farber Cancer Institute, Broad Institute

An HTAN atlas built explicitly around therapeutic resistance, with multiplexed imaging, single-cell RNA sequencing and the richest clinical annotation of any atlas here - and no publications recorded in the network's own manifest.

Can it answer your research question?

0 of 6 supported
  • Overall survival

    Limited

    A follow-up table exists for 100% of cases; its individual fields were not measured.API

  • Progression or recurrence

    Limited

    A follow-up table exists for 100% of cases; its individual fields were not measured.API

  • Treatment response

    Limited

    A therapy table exists for 100% of cases; its individual fields were not measured.API

  • Which drug was given

    Limited

    A therapy table exists for 100% of cases; its individual fields were not measured.API

  • Stage-adjusted modelling

    Limited

    A diagnosis table exists for 100% of cases; its individual fields were not measured.API

  • Analysis by race or ethnicity

    Limited

    A demographics table exists for 100% of cases; its individual fields were not measured.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
156
Measurement types
3
20,350 files
Follow-upAPI
Present
no survival endpoint
Treatment responseAPI
Unknown

SubjectCALC

Subject derived from title

Derived from the title, not stated by the repository, and never used to place this dataset in an answer shortlist.

As filed by the repository

The repository publishes no disease classification.

Who is in the cohort

The repository’s harmonized records carry no demographics for this dataset.

What was measured, and on how many

3 measurement types, none covering the whole cohort.

  • Multiplexed tissue imagingscarcecount not published
  • Single-cell / single-nucleus RNA sequencingcount not published
  • Bulk DNA sequencingcount not published
Platform, files and data levels
AssayPlatformFilesLevels
Multiplexed tissue imagingAPI-16,811level 2, level 3, level 4
Single-cell / single-nucleus RNA sequencingAPI-408level 1, level 2, level 3, level 4
Bulk DNA sequencingAPI-341level 2, level 3
How complete all 8 clinical fields are - 6 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

Follow-up

  • Follow-up1:nAPI100%

Treatment

  • Therapy1:nAPI100%

Diagnosis

  • Diagnosis1:nAPI100%

Demographics

  • DemographicsAPI100%

Exposure

  • Exposure historyAPI64%

Molecular markers

  • Clinical molecular testAPI41%

Other

  • Extended clinical data (tier 2)1:nAPI100%
  • Family history1:nAPI100%

Access

MixedSome components are open; others need approval.API

Level 1-2 sequencing data are controlled through dbGaP; level 3-4 derived data and most imaging are downloadable from Synapse after registering and accepting the HTAN data use terms.

Open components
level 3-4 derived data; most imaging
Controlled components
level 1-2 sequencing (dbGaP)
License
HTAN data use terms; CC BY 4.0 for many level 3-4 products
Citation requirement
Cite the atlas publication and acknowledge HTAN per the network's publication policy.

What it is good for

Written and checked by a reviewer, not generated from metadata.

  1. 1. Where within a tumor do cells that survive therapy actually reside?

    Needs approved accessHUMAN

    Multiplexed tissue imaging with single-cell RNA sequencing on the same specimens, in an atlas designed around this question, with therapy records available as a clinical component to define the treatment context.

    Statistical note: Spatial analyses are specimen-level; patient numbers are small and the appropriate unit of inference is the region or cell neighborhood, with patient as a random effect.

    NeedsMultiplexed tissue imagingSingle-cell RNA sequencingTreatment records
  2. 2. Do spatial niches associated with resistance recur across cancer types, or are they tissue-specific?

    Needs another datasetHUMAN

    Neighborhood definitions derived here can be tested against other HTAN atlases that share the multiplexed imaging component, giving cross-atlas comparison within a single access framework and a common data model.

    NeedsMultiplexed tissue imaging
  3. 3. Can the extended clinical tier be used to relate spatial organization to real treatment sequences rather than to treatment as a single binary?

    Needs approved accessHUMAN

    This atlas carries the extended clinical data tier that most atlases lack, alongside therapy and follow-up. That is what allows spatial features to be related to what was actually given and what happened next.

    Statistical note: Confirm the completeness of the extended clinical fields in Synapse before designing; the portal metadata records their presence but not their coverage.

    NeedsMultiplexed tissue imagingTreatment recordsClinical data

What it cannot tell you

1 blocking

Written by a reviewer against the source, not inferred from what is missing.

BlockingStatistical powerHUMAN

HTAN atlases profile few patients deeply. 20,350 files does not mean many participants, and participant counts are not exposed in the portal metadata.

Affects: Cohort-level association; Powered biomarker discovery

Mitigation: Obtain participant counts from Synapse first; design within-patient or region-level comparisons.

MajorAnnotation qualityHUMAN

No publication is recorded for this atlas in HTAN's own manifest, so there is no marker paper to read for design details, quality caveats or the intended interpretation of the clinical fields.

Affects: Interpreting cohort design; Understanding sampling

Mitigation: Contact the atlas team through the HTAN portal before investing in an analysis. The absence of a marker paper is the main practical barrier to reusing this resource.

MajorAccess constraintHUMAN

Level 1 and 2 sequencing is controlled through dbGaP; derived data and imaging need a Synapse account and acceptance of the HTAN terms.

Affects: Raw sequence analysis

Mitigation: Start with the Synapse tier.

MajorHarmonizationHUMAN

Assay coverage varies by specimen across the three modalities.

Affects: Multimodal integration

Mitigation: Build the specimen intersection from Synapse manifests.

Not appropriate for

  • Cohort-level statistical inference. - Deep sampling of few patients; the design does not support it.HUMAN
  • Assuming clinical field completeness from their presence in the metadata. - The portal metadata records which clinical components exist, not how completely they are populated. Verify in Synapse.HUMAN

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
-
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.

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.

advanced

Given a research goal, which dataset should an agent choose, and what must it refuse to do with it?

Select a dataset the way an agent should

CD2S workbooks · ran 21 Sept 2026
pythonunder a minuteexecuted
Required inputs
  • The CD2S structured export
  • pandas
Expected outputs
  • Contrast between a size-ranked and a capability-ranked selection
  • A transparent fit score favoring under-used resources
  • Blocking limitations read before committing
  • A machine-readable task brief for the next step
  • A chart of the ranked fit scores with the selected cohort highlighted
Steps
  1. Load the structured index
  2. Show what a naive size-ranked selection returns
  3. Filter on measured capability rather than description
  4. Rank on fit, rewarding under-used datasets
  5. Read blocking limitations from the full record
  6. Emit a task brief including what the agent must not do

Start here

Starter code generated from this record’s own identifiers, then the access steps.

Get the data in code

HTAN: fetch files from Synapsepython

pip install synapseclient. Register at synapse.org and accept the HTAN terms first. Level 1 and 2 sequencing is controlled through dbGaP.

import synapseclient

syn = synapseclient.login()          # uses ~/.synapseConfig or SYNAPSE_AUTH_TOKEN
for sid in ["syn39259236","syn39259256","syn39259280","syn39259513"]:
    entity = syn.get(sid, downloadLocation="./htan")
    print(sid, entity.name)
# Browse the atlas at https://humantumoratlas.org/explore
This page as data: limitations firstbash
curl -s https://cd2s.vercel.app/data/datasets/htan-the-cellular-geography-of-therapeutic-resistance-in-cancer.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
    Contact the atlas team through the HTAN portalFor peopledays

    With no marker publication recorded, this is the fastest route to the design details you would normally get from a paper.

    https://humantumoratlas.org/
  2. 2
    Register with Synapse and accept the HTAN data use termsFor people1 day

    Requires: Synapse account

    https://humantumoratlas.org/data-access
  3. 3
    Verify participant counts and clinical field coverage before designingFor people2-3 hours
  4. 4
    Give an agent a Synapse token, not a passwordFor agents

    Unauthenticated calls return metadata and no files, so an agent should report the credential requirement explicitly.

    Requires: SYNAPSE_AUTH_TOKEN

    export SYNAPSE_AUTH_TOKEN=...
    synapse get syn39259236
    https://help.synapse.org/docs/Getting-Started.2055471150.html

    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
Project-curatedCD2S project curation on 18 Sept 2026
Data generation funding
Funded data generation
Open questions from review
  • This atlas has no entry in the HTAN publication manifest, so we cannot identify its marker publication or confirm whether one exists yet. Confirm with the atlas team.
  • Participant counts are not exposed in the portal metadata; obtain them from Synapse.

For softwarerecord JSON