A second sample id is not a second patient: three of the interesting pairs in GSE252378 are one patient twice, and reading them as independent doubles the apparent n
Datasets often list two samples that came from the same person at two different moments. Counting them as two people makes a study look twice as large as it is.
The same thing, for a scientist
**The concrete case.** GSE252378 contains three lineage-switching pairs, each of which is **one patient sampled twice**, stated in GEO's own `!Sample_description` field: | pair | fusion | states | what a careless read gives | |---|---|---|---| | `p279` / `p318` | KMT2A-AFF1 | infant B-ALL, then the AML it became | 2 patients instead of 1 | | `148752` / `152985` | KMT2A-ENL | infant B-ALL, then AML, **both under a menin inhibitor** | 2 patients instead of 1 | | `R3595` / `R3652` | KMT2A-EPS15 | infant B-ALL, lineage-switching | 2 patients instead of 1 | The paper says so too: it profiled "36 broadly representative MLL-rearranged leukemia samples, **including three samples that underwent a lymphoid-to-myeloid lineage-switching event**" - three switching events, six sample ids [E2]. **This corpus already contains the mistake in a mild form.** The existing entry recording this deposit's menin arm describes `148752` and `152985` as "two primary infant lineage-switching patient samples", which is literally true and reads as two patients. The dispatch brief for this beat stated that the drug-treated samples "belong to two different patients" and that the AFF1 arm contains "three PRIMARY patient samples". **Both are one patient short.** The correct counts are: menin under drug, **n = 1 patient**; AFF1 in primaries, **n = 2 patients in 3 states**. **The general rule.** Before counting samples as independent, read `!Sample_description` and `!Sample_source_name_ch1` for the words *paired*, *matched*, *relapse*, *diagnosis*, *pre-*, *post-*, *timepoint*, *switch*. GEO puts the pairing in prose, not in a structured field, so no parser finds it and no metadata table shows it. The consequence is not cosmetic: an n of 2 read as 4 halves every standard error and turns a paired design into an unpaired one.
Where it bites hardest in this project
Bounded absences and coverage claims of the form 'N patients have been profiled' are exactly the statements that inflate. It also changes which statistical comparison is correct: p279 versus p318 is a within-patient, across-lineage comparison and should never be used as a reproducibility check, which is how a between-sample agreement analysis would naturally treat it.
A related trap in the same fields
GSM8006563-GSM8006567 are titled A95941_* while their characteristics field names the sample A93949 - the same id as GSM8006558-GSM8006562. The identical defect appears again at GSM8006598-GSM8006602, titled TB995291_* with characteristics naming TB-00-0694, which is the sample id of GSM8006568-GSM8006572. So in that deposit the title and the characteristics disagree about which patient a library came from, in ten samples across two patient pairs. It is the mirror image of the pairing problem: here two different ids are used for what the characteristics field says is one patient, and it cannot be resolved from the deposit.
- How many 'N patients profiled' statements in this corpus were counted from sample ids rather than from patient ids?
- E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.dataset
GSE252378's per-sample description fields state that p279 is paired with p318, 148752 with 152985, and R3595 with R3652, each pair being one lineage-switching patient in two states; and ten samples - five titled A95941 and five titled TB995291 - carry characteristics naming the patients A93949 and TB-00-0694 respectively.
GSE252378 - AutoCUT&RUN and AutoCUT&Tag profiles of 36 MLL-rearranged leukemia samples (171 GSMs, hg38) · Janssens DH, Henikoff S (Fred Hutchinson Cancer Center / Van Andel Institute) · NCBI Gene Expression Omnibus 2024What this evidence cannot show
Read from the deposited metadata for all 171 samples. The A95941/A93949 and TB995291/TB-00-0694 discrepancies are reported as observed; which field is correct cannot be determined from the deposit. Neither pair is in the KMT2A::AFF1 arm used for this beat's measurements.
Evidence that argues against this (1)
- 'Paired with' could in principle denote a matched control rather than a same-patient timepoint; the paper's sentence that p318 is the AML resulting from the lineage switch of p279 settles it for that pair, but the other two pairs rest on the GEO wording alone. Janssens DH et al. 2024
- E2established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.paper
The source paper profiled 36 MLL-rearranged samples including three that underwent a lymphoid-to-myeloid lineage switch.
MLL oncoprotein levels influence leukemia lineage identities · Janssens DH, Duran M, Otto DJ, Wu W, Xu Y, Kirkey D, Mullighan CG, Yi JS, Meshinchi S, Sarthy JF, Ahmad K, Henikoff S · Nature Communications 15:9341 2024What this evidence cannot show
From the abstract and results of PMC11522475.
Evidence that argues against this (1)
- Three switching events and six sample ids is consistent with three paired patients, but the paper does not enumerate which six ids, so the mapping onto the three GEO pairs is an inference. Janssens DH et al. 2024
three paired lineage-switching patients, six sample ids
the menin arm of that deposit is n = 1 patient, not 2
sets the n for the menin arm
- ← supportsp279 and p318: one infant, two diseases, and an oncoprotein target map that does not carry over
p279 and p318 are the worked case of that rule