The Cellular Geography of Therapeutic Resistance in Cancer
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 supportedOverall survival
LimitedA follow-up table exists for 100% of cases; its individual fields were not measured.API
Progression or recurrence
LimitedA follow-up table exists for 100% of cases; its individual fields were not measured.API
Treatment response
LimitedA therapy table exists for 100% of cases; its individual fields were not measured.API
Which drug was given
LimitedA therapy table exists for 100% of cases; its individual fields were not measured.API
Stage-adjusted modelling
LimitedA diagnosis table exists for 100% of cases; its individual fields were not measured.API
Analysis by race or ethnicity
LimitedA demographics table exists for 100% of cases; its individual fields were not measured.API
At a glance
Every percentage is the repository’s own record of what is filled inSubjectCALC
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
- Multiplexed tissue imagingscarce
- Single-cell / single-nucleus RNA sequencing
- Bulk DNA sequencing
How complete all 8 clinical fields are - 6 informative for at least 80% of cases
Access
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. Where within a tumor do cells that survive therapy actually reside?
Needs approved accessHUMANMultiplexed 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 records2. Do spatial niches associated with resistance recur across cancer types, or are they tissue-specific?
Needs another datasetHUMANNeighborhood 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 imaging3. 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 accessHUMANThis 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
Written by a reviewer against the source, not inferred from what is missing.
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.
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.
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.
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.
- Not assessed: this dataset has no accession specific enough for citation-based reuse tracing, so a shortfall cannot be measured.
Articles that analyzed the data
Not searchable. See the note above.
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.
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
- The CD2S structured export
- pandas
- 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
- Load the structured index
- Show what a naive size-ranked selection returns
- Filter on measured capability rather than description
- Rank on fit, rewarding under-used datasets
- Read blocking limitations from the full record
- 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
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/exploreThis 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
- Contact the atlas team through the HTAN portalFor people
With no marker publication recorded, this is the fastest route to the design details you would normally get from a paper.
https://humantumoratlas.org/ - Register with Synapse and accept the HTAN data use termsFor peoplehttps://humantumoratlas.org/data-access
- Verify participant counts and clinical field coverage before designingFor people
- 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.
https://help.synapse.org/docs/Getting-Started.2055471150.htmlexport SYNAPSE_AUTH_TOKEN=... synapse get syn39259236
Provenance
All of it, and more, is in this record’s JSON.
Identifiers
- IdentifierHTA5API
- Synapsesyn39259236API
- Synapsesyn39259256API
- Synapsesyn39259280API
- Synapsesyn39259513API
- Synapsesyn39259855API
- Synapsesyn50549510API
- Synapsesyn51185203API
- Synapsesyn51218193API
- Synapsesyn51218570API
- Synapsesyn51360919API
- Synapsesyn51360962API
- Synapsesyn51364711API
Versions and verification
- Metadata retrieved
- 18 Sept 2026
- Review status
- Project-curatedCD2S project curation on 18 Sept 2026
- Data generation funding
- Funded data generation
- 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.