Chimerism & Xenograft Analysis: Advanced STR Applications in Oncology

Mixture samples aren't edge cases in oncology—they're the rule. Patient-derived xenografts (PDX) combine human tumor tissue with a mouse stromal/host environment. Post-transplant and cell therapy research routinely yields donor–recipient mixtures in a single specimen. In both settings, short tandem repeat (STR) profiling remains a practical, auditable way to confirm identity, detect additional contributors, and provide semi-quantitative estimates within validated limits. This guide clarifies what STR chimerism analysis can and cannot do in human–mouse and human–human mixtures, how to pair STR with complementary methods, and how to report results that stand up to peer and QA review. Research use only (RUO).


1. Why This Matters in Oncology: When Samples Are Mixtures by Design

PDX and chimerism studies succeed or fail on the quality of their identity and mixture controls. Without a defensible identity baseline and a repeatable way to interpret mixtures, downstream genomic readouts, drug-response studies, and longitudinal inferences can be misleading.

1.1 PDX and xenograft reality: human tumor + mouse host signal overlap

In PDX workflows, human tumor tissue is engrafted into immunodeficient mice. Over passages, mouse stromal replacement typically increases, shifting the apparent human-to-mouse content. STR profiling of human markers verifies the identity of the human component and detects extra human contributors (e.g., cross-contamination by another human line), but STR is not a species quantification method. When percent content or spatial localization matters, labs commonly complement STR with species-specific qPCR/dPCR, dual-genome NGS alignment, or in situ hybridization (ISH).

1.2 Post-transplant chimerism: mixed donor/recipient DNA in a single specimen

After allogeneic transplantation or cell therapy research, donor and recipient DNA coexist in peripheral blood or marrow. STR panels can identify informative loci (alleles unique to donor or recipient) and estimate relative contribution using peak heights or peak areas. Sensitivity for minor contributors is typically in the single-digit percent range in validated RUO workflows; microchimerism below about 1% generally requires alternative methods.

Caption: Mixture landscape. STR profiles reveal human identity and multi-human mixtures; human STR does not quantify mouse. Typical STR minor-contributor LOD: ~1–5% (validate locally).

1.3 What STR can and cannot do in mixture contexts

What STR does well:

  • Authenticate the human component in PDX, linking back to reference samples or database profiles.
  • Detect the presence of more than one human contributor via >2 alleles at a locus, discordant genotypes, or characteristic imbalance patterns.
  • Provide semi-quantitative donor–recipient estimates at informative loci using RFU-based calculations (within lab-validated bounds).

Where STR is not the right tool alone:

  • Detecting sub-percent minor contributors or microchimerism: consider qPCR/dPCR or NGS.
  • Species-level quantitation of human vs mouse in PDX: consider species-specific qPCR/dPCR or dual-genome NGS read fraction analysis.
  • Spatial localization of species or donor/recipient compartments in tissue: consider ISH-based methods.

2. Key Concepts and Methods for STR Chimerism Analysis in Mixtures

2.1 Qualitative: "Is there more than one contributor?"

First, answer the qualitative question. Indicators of multiple human contributors include:

  • More than two alleles at one or more autosomal loci.
  • Marked heterozygote imbalance and pattern inconsistencies across loci not explained by degradation or inhibition artifacts.
  • Discordance versus a known reference profile beyond expected drift in cancer lines.

If you want a refresher on reading STR loci, alleles, and peak patterns, start here: If you want a refresher on reading STR loci, alleles, and peak patterns, start here.

2.2 Semi-quantitative: estimating mixture proportion using peak height/area logic

STR chimerism analysis typically labels informative alleles at each locus as donor-only, recipient-only, or shared, then computes a percentage using RFU values:

Percent donor at a locus ≈ (sum of donor-specific allele RFUs) / (sum of donor-specific + recipient-specific allele RFUs) × 100%

  • Use either peak height or area consistently across all loci and timepoints.
  • Average across multiple informative loci to report an overall value; provide the list of loci used.
  • Near the laboratory's limit of detection (LOD), replicate injections and confirmatory sampling improve reliability.

Practical note: To interpret the report columns and example electropherograms step by step, see this applied guide: How to Interpret STR Analysis Reports: A Guide for QA and Research Teams.

2.3 Pitfalls: differential amplification, degraded input, locus dropout

Several factors bias measurements if unrecognized:

  • Preferential amplification: Smaller alleles often amplify more efficiently, skewing ratios.
  • Degradation and inhibitors: FFPE fragmentation or heme contamination elevate dropout risk, especially at larger loci.
  • Stutter and dye pull-up: PCR slippage and spectral overlap can mimic minor alleles; apply validated stutter filters and spectral calibrations.
  • Instrument/injection variance: Keep injection time/voltage and run conditions consistent; re-inject suspect samples.

Document your analytical thresholds (per dye channel), stutter filters, and injection settings in every report for auditability.


3. Xenograft-Specific Workflows: Identifying Human vs Mouse (and Mixed) Signals

3.1 Sample types: tumor chunk, blood, FFPE sections, cultured explants

Each sample type brings different pre-analytical risks and opportunities:

  • Fresh tumor chunks: High-quality DNA but variable human fraction; histology helps estimate tumor cellularity.
  • FFPE sections: Fragmented DNA; anticipate dropout and consider replicate amplifications.
  • Mouse blood or tissues used as "mouse-only" controls: Treat as contamination-sensitive; process with unidirectional workflows.
  • Cultured explants: Risk of human cell line cross-contamination during passaging; STR is well-suited to detect extra human contributors.

3.2 Human vs mouse discrimination strategies (what STR is used for vs when species ID is needed)

  • Use human STR panels to authenticate the human component and detect additional human contributors.
  • For species discrimination and quantitation in PDX, pair STR with:
    • Species-specific qPCR/dPCR assays to quantify human vs mouse DNA fractions.
    • NGS with dual-genome alignment to estimate read fractions mapping to human vs mouse.
    • ISH when spatial localization of species is critical.

Caption: Decision tree. STR authenticates human identity and detects multi-human mixtures; species quantitation/localization typically relies on qPCR/dPCR, NGS, or ISH.

3.3 Interpreting "unexpected human STR" in mouse-only controls (contamination vs carryover)

Finding human STR peaks in a sample that should be mouse-only is a red flag that requires a structured, documented investigation. The goal is to determine whether the signal represents true human DNA contamination (biological carryover), a procedural mix‑up, or an analytical artifact (stutter, pull‑up, dye blob). Below is a prioritized, evidence‑driven workflow labs can follow; treat all steps as RUO troubleshooting and record every action in the project log.

Likely causes (ranked by frequency)

  • Cross‑sample carryover during dissection, passaging, or aliquoting (most common).
  • Plate/column or instrument contamination (shared pipettes, multi‑use tubes, autosampler carryover).
  • Sample mislabeling or plate map errors (human sample placed in adjacent well or wrong barcode scan).
  • True biological carryover (human stromal fragments in a mouse sample from adjacent tissue).
  • Analytical artifacts: spectral pull‑up, stutter peaks, dye blobs, or baseline noise mimicking low‑level alleles.

Immediate triage (same day)

1. Check controls: review no‑template controls (NTCs) and negative extraction controls from the same run for human peaks. If NTCs show human signal, quarantine the run and stop downstream reporting.

2. Inspect plate map and LIMS entries: confirm tube/plate barcodes, operator sign‑offs, and well positions for adjacent human samples.

3. Re‑view raw electropherograms (FSA): inspect peak morphology, channel assignment, and dye‑specific patterns consistent with pull‑up or dye blobs.

Confirmatory testing (priority order)

  • Re‑extract DNA from the original tissue using a fresh consumables set and run the same human STR panel in duplicate; consistent human peaks in independent extracts increase likelihood of true contamination.
  • Run a mouse STR panel or mouse‑specific PCR to verify that the dominant biological signal is mouse (helps confirm species identity rather than human contamination artifact).
  • Run a species‑specific qPCR or dPCR assay (human and mouse targets) to estimate human:mouse fraction; qPCR/dPCR sensitivity typically exceeds STR near the low percent range and helps quantify contamination.
  • If uncertainty remains, submit a small aliquot for dual‑genome NGS or shallow shotgun sequencing and compute human vs mouse read fractions (highly informative for PDX contexts).

Decision criteria

  • Artifact: single‑channel anomalous peaks, inconsistent peak shapes, or peaks that disappear on re‑injection indicate analytical artifact (document instrument settings and spectral calibration).
  • Procedural contamination: human peaks that appear in samples adjacent to a human‑positive well, repeat across multiple aliquots, or persist after re‑extraction usually indicate cross‑sample carryover or mislabeling.
  • True biological carryover: reproducible human STR across independent extractions, concordant species qPCR/NGS fractions, and histology evidence of human cells support true human presence.

Corrective actions and containment

  • Quarantine affected samples and runs; re‑run from a fresh aliquot only after confirming clean reagents and workspace.
  • Perform instrument decontamination and autosampler cleaning; replace shared consumables and re‑calibrate spectral matrices.
  • If mislabeling is identified, reconcile with submitter and correct LIMS entries; document root cause and corrective action in the incident log.
  • For PDX lines with confirmed human carryover, consider re‑deriving tumor material (fresh passage or microdissection/FACS separation) and re‑bank authenticated material.

Prevention and quality program measures

  • Enforce unidirectional workflows and physical separation of pre‑ and post‑PCR areas; dedicate equipment where feasible and use single‑use consumables for high‑risk steps.
  • Barcoded sample handling with two‑person checks at receipt, aliquot, and plate setup; integrate barcode scans with LIMS to prevent plate map mismatch.
  • Include extraction negatives and NTCs on every plate; monitor trend logs for sporadic low‑level human signal and investigate increases promptly.
  • Bank and reference patient/donor DNA early during PDX establishment to provide authoritative baselines for future matching.

Reporting and traceability

  • In the final RUO report, include locus‑level allele calls, per‑allele RFUs, raw FSA files, results of orthogonal assays (qPCR/NGS), and a concise incident note if contamination was observed and how it was resolved.
  • Archive all raw and processed files, corrective actions, and root‑cause analysis documentation so results remain re‑auditable.

Practical help for submitters: follow the lab's sample submission checklist and metadata requirements (host strain, passage, collection site, and estimated tumor fraction) to reduce downstream ambiguity; see the sample submission guidelines for recommended fields and packaging instructions: Sample submission guidelines (CD Genomics).

4. Chimerism Applications: Transplant and Cell Therapy Research

4.1 Donor/recipient tracking: baseline genotypes and post-event monitoring

Build a solid baseline before the event (e.g., donation, infusion):

  • Profile donor and recipient with the same STR kit and instrument.
  • Identify informative loci (non-overlapping alleles) and list them in the method file.
  • If relevant, sort or enrich lineages (e.g., CD3+, CD19+) to focus on compartments of interest.
  • Set analytical thresholds and stutter filters during validation; document them.

4.2 Longitudinal reporting: how to present change over time

Plot percent donor (or recipient) against time using a consistent set of informative loci and the same calculation method. Flag estimates near the LOD, replicate critical timepoints, and keep instrument/run conditions constant across visits when feasible.

Caption: Example longitudinal trend (RUO). Values are averaged across informative loci using peak height ratios; validate locally.

4.3 Defining "action thresholds" for research protocols (example tiers)

In RUO contexts, avoid universal clinical cutoffs. Instead, consider policy tiers that you validate locally, such as:

  • Review zone: When a sustained ≥5% directional change appears across at least two informative loci in two consecutive timepoints, schedule confirmatory testing.
  • Confirm with orthogonal method when values drift toward laboratory LOD or when microchimerism is suspected.
  • Use lineage-specific chimerism when compartment-specific dynamics matter.

Clearly label any thresholds as research-only examples requiring local verification.


5. Data Traceability and Database Matching for High-Value Samples

5.1 Linking mixture interpretation back to known references

For PDX identity and donor/recipient baselines, use ≥13 core human loci and align with community guidance (e.g., ANSI/ATCC and ICLAC). For tumor lines prone to drift, document passage numbers and environmental conditions. Where applicable, compare profiles to public databases and include accession IDs in your report.

5.2 Why global database interoperability reduces disputes ("whose sample is this?")

Aggregators like Cellosaurus compile STR profiles from repositories (ATCC, DSMZ, JCRB), helping labs triangulate provenance, resolve historic misidentifications, and document sample lineages across sources. Cross-referencing reduces room for dispute when collaborations or multi-center projects are involved.

How DSMZ/ATCC/JCRB matching works and how to document provenance: How DSMZ/ATCC/JCRB matching works and how to document provenance.

Practical reporting tips:

  • Include the exact loci used, allele calls, RFU tables, and match criteria (e.g., match ratio rule) in the PDF report.
  • Add database accession IDs and the date you accessed each record.
  • Archive raw FSA/electropherogram files and allele tables so results are re-auditable.

6. Practical Submission Notes for PDX/Chimerism Studies

6.1 What metadata to include

At minimum, include the following in your submission or internal LIMS record:

  • Host strain, passage number, collection method, and histology-based tumor fraction estimate (for PDX).
  • Sample type (gDNA/FFPE/cell pellet), extraction kit, and any known inhibitors.
  • Donor/recipient baseline STR profiles, informative loci list, and software versions used for allele calling.
  • Database references and accession IDs (ATCC, DSMZ, JCRB, Cellosaurus) used for matching.
  • Run conditions (kit lot, instrument model, injection settings) and analytical thresholds/stutter filters.

Sample requirements for gDNA, FFPE, and cell pellets (quick checklist): Sample requirements for gDNA, FFPE, and cell pellets (quick checklist).

6.2 How to avoid avoidable failures (low input, inhibitors, mixed labeling)

PDX and chimerism projects often fail or produce ambiguous STR results because pre-analytical and laboratory controls were incomplete. The recommendations below prioritize reproducibility, chain-of-custody, and clear audit trails; treat all numerical suggestions as typical research-practice examples that require local validation.

Low-input and degraded DNA (FFPE, trace samples)

  • Pre-submission QC: measure DNA concentration and fragment size (e.g., Qubit for quantity, a Bioanalyzer or TapeStation trace for integrity). Record kit, extraction method, and extraction date in metadata.
  • Minimums and fallback options: while many STR workflows accept 1 ng input for human panels, aim for ≥5–10 ng when possible for robust peak balance; for FFPE or degraded extracts, use short-amplicon STR kits or replicate amplifications to reduce locus dropout.
  • Validation runs: perform serial-dilution validation (≥3 independent samples) to document stochastic effects, peak-height ratio (PHR) behavior, and locus dropout rates across the lab's chosen kit and instrument.
  • Practical mitigations: if dropout is observed, re-extract from an independent punch/aliquot, run replicate PCRs, or use a short-amplicon panel. Document any allele calls that come from low-RFU peaks and flag them in the report.

Inhibitors and extraction artifacts

  • Screening and remediation: include an internal amplification control (IAC) or spike-in to reveal inhibition; if inhibition is detected, repeat extraction with cleanup (e.g., silica-column re-purification, magnetic-bead cleanup) or dilute template and re-run with adjusted cycle numbers.
  • FFPE-specific notes: anticipate cytosine deamination and fragmentation; prefer polymerases/kits optimized for damaged DNA and shorter amplicons.

Contamination control and carryover prevention

  • Physical layout and workflow: enforce strict unidirectional workflow with separate pre-PCR (reagent prep, sample setup) and post-PCR (product handling) rooms or benches. Use dedicated pipettes and filtered tips for each zone.
  • Molecular controls: adopt UNG/dUTP carryover prevention in PCR mixes where compatible, include no-template controls (NTCs) on every plate, and run positive and negative extraction controls with each batch.
  • Monitoring and audit: log NTC outcomes, maintain an incident register for any contamination events, and perform root-cause analyses (e.g., air sampling, surface swabs) if unexpected peaks appear in NTCs.
  • When contamination is flagged: quarantine the affected run, re-extract from the original specimen when possible, and re-test from fresh reagents and clean workspaces. Report the event and corrective actions in the project record.

Labeling, chain-of-custody and LIMS verification

  • Two-person checks and barcoding: require two-person verification at critical handoffs (receipt, aliquoting, and plate loading) and use 2D barcoded tubes/plates to minimize manual labeling errors.
  • LIMS-linked SOPs: record sample metadata (source, passage, host strain, extraction kit, concentration, operator) in a LIMS entry before testing. Lock LIMS records after assignment to a run to prevent silent edits.
  • Acceptance criteria: check that the submitted metadata include donor/passage identifiers and any baseline reference profiles; if required fields are missing, place the sample on hold and contact the submitter rather than proceeding.
  • Reconciliation: reconcile plate maps to LIMS exports before PCR setup; capture photos/scans of plates and labels as an auditable checkpoint.

Species confusion and PDX-specific mitigations

  • Pair STR with species-quant assays: when human vs mouse fraction affects downstream analysis, run a species-specific qPCR/dPCR or include a dual-genome NGS fraction estimate to quantify human content. STR alone should not be used to report precise human:mouse percentages near the assay LOD.
  • Interpret mixed profiles carefully: multi-allelic patterns may indicate human contamination rather than true chimerism; check histology-based tumor fraction estimates or orthogonal species assays before concluding.
  • Reference panels: when available, submit matched host and donor/reference DNA so the lab can select informative loci and avoid misattribution.

QC reporting and traceability

  • Report contents: include locus-level allele calls, per-allele RFUs, stutter filters used, analytical thresholds, and which loci were informative vs dropped. Archive raw FSA electropherogram files for future reanalysis.
  • Example research-practice thresholds (validate locally): analytical allele-calling threshold 50–100 RFU; consider locus-level LODs from dilution validation (reported as % minor contributor). Always annotate values near thresholds with caution notes.

Troubleshooting checklist (quick)

1. Unexpected extra alleles: check plate map, confirm barcode scans, review NTCs, and re-extract if contamination suspected.

2. High locus dropout: inspect DNA fragment distribution; consider re-extraction or short-amplicon panel.

3. Poor peak balance/high stochasticity: verify input quantity/quality and repeat with replicate amplifications.

4. Discordance vs reference: confirm reference provenance (passage, source) and consider repeat testing or orthogonal confirmation.

These steps reduce common avoidable failures in PDX and chimerism STR testing while preserving an auditable trail for QA. For submitters, consult the lab's sample-submission checklist (e.g., DNA concentration, volume, host/passage metadata) before shipping to minimize delays.


7. Method Comparison at a Glance

Below is a compact comparison of methods often paired with STR in xenograft and chimerism studies (typical ranges; validate locally and see references).

Method Core purpose Typical sensitivity (minor component) Strengths Limits
STR via capillary electrophoresis Human identity/authentication; detect multi-human mixtures; semi-quant at informative loci ~1–5% (sometimes ~0.8% with optimized workflows) Fast TAT, cost-effective, standardized, database-compatible Not species quantitation; microchimerism below ~1% is challenging; susceptible to artifacts if not filtered
Species-specific qPCR/dPCR Quantify human vs mouse DNA fractions ~0.01–1% (assay-dependent) Low LOD, rapid Single-target; no genome-wide context
NGS with dual-genome alignment Quantify read fractions mapping to human vs mouse; broader genomic context Often ≤1% with sufficient depth Rich information, trendable across passages Computational overhead, alignment/mapping biases
ISH (e.g., RNAscope) Spatial localization of species/cell types in tissue Semi-quantitative Visual context in tissue Not a bulk DNA quantitation tool

8. Where STR Fits into a Real Workflow (Neutral Example)

Disclosure: CD Genomics is our product.

A typical RUO PDX identity/QC loop might look like this:

  • On receipt of a new passage, generate a human STR profile using your validated kit and instrument.
  • Compare the profile against the original patient tumor or prior passage, and optionally query public repositories (ATCC/DSMZ/JCRB via Cellosaurus) for external corroboration.
  • If an extra human contributor is suspected (e.g., >2 alleles at multiple loci), perform a contamination review and re-derive explants as needed; optionally add SNP panel or WES alignment checks.
  • If human-to-mouse percentage is decision-critical for downstream omics, add species qPCR/dPCR or dual-genome NGS.

For labs seeking an external RUO provider for the identity/authentication portion of this loop, see the STR cell line authentication service overview, including deliverables and database matching notes: STR cell line authentication service. Use this as a reference point for structuring your own report templates and QC disclosures.


Related Services


Author

Yang H. — Senior Scientist, CD Genomics; University of Florida.

Yang is a genomics researcher with over 10 years of research experience in genetics, molecular and cellular biology, sequencing workflows, and bioinformatic analysis. Skilled in both laboratory techniques and data interpretation, Yang supports RUO study design and NGS-based projects.


References

Please validate all thresholds locally; references below support concepts and example ranges.

Notes on usage: External links in the body are limited to essential citations; full bibliographic details with DOIs are provided here for transparency and replication. All methods and example thresholds are for research use only and require local validation.

For research purposes only, not intended for clinical diagnosis, treatment, or individual health assessments.
PDF Download
* Email Address:

CD Genomics needs the contact information you provide to us in order to contact you about our products and services and other content that may be of interest to you. By clicking below, you consent to the storage and processing of the personal information submitted above by CD Genomcis to provide the content you have requested.

×
Quote Request
! For research purposes only, not intended for clinical diagnosis, treatment, or individual health assessments.
Contact CD Genomics
Terms & Conditions | Privacy Policy | Feedback   Copyright © CD Genomics. All rights reserved.
Top