Article · 2026 Deep GEO

What one patient can teach the next

Clinical and Translational Medicine

Full Authors

  1. Ge Zhang
  2. Mingxuan Duan
  3. Tianshu Gu
  4. Qian Guo
  5. Yahui Han
  6. Teng Li

Cite this paper

Plain citation

Ge Zhang, Mingxuan Duan, Tianshu Gu, Qian Guo, Yahui Han, Teng Li. What one patient can teach the next. Clinical and Translational Medicine. 2026. https://doi.org/10.1002/ctm2.70900

Author-controlled citation; verify against the publisher version of record.

Evidence Base

What one patient can teach the next

This Invited Letter presents a question-specific framework for learning across individualised treatment cases. It connects timely outcome reporting with AI-assisted comparison of clinical course, treatment exposure, biological context and prior evidence, distinguishing changes to safety monitoring, tests of mechanistic explanations and evaluation of treatment benefit.

Published genre
Invited Letter
Article structure
3 pages, 1 conceptual figure and 8 references
Comparison inputs in Figure 1
Clinical course; treatment details; biological context; prior cases and evidence
Distinct evidential actions
Adapt safety monitoring; test mechanistic explanations; evaluate treatment benefit

Counting note

The two children in the KCNT1 example belong to the report cited as reference 2. They are not a new study population recruited for this Letter; no synthetic patient total is assigned to its framework.

Research Question

How can an outcome from one individualised treatment inform the next patient, and which evidence is needed to change monitoring, test a mechanism or assess treatment benefit?

Author Evidence Summary

The article moves from making individualised-treatment outcomes visible to deciding what another clinical team can learn from them. A previously published KCNT1-related epilepsy report illustrates how an earlier complication can inform monitoring before its mechanism is fully understood. The authors then distinguish three purposes for comparing cases: identifying a safety signal, testing a biological explanation and evaluating benefit. Similar exposure can matter for safety even across diagnoses, whereas benefit assessment requires the pretreatment disease course, meaningful outcomes and appropriate comparison. Prognostic accuracy and molecular subgroup differences answer other questions. Figure 1 organises clinical trajectories, treatment details, biological context and prior evidence around a proposed AI-assisted comparison process that explains relevant similarities, differences and uncertainty. Its outputs are adapted monitoring, informative experiments and stronger comparative evidence for treatment decisions. The closing argument couples prompt reporting of major outcomes with consent and privacy safeguards for detailed patient-level data.

Key Arguments

KF1 Move from timely outcome reporting to a specific question about what the next team can learn.

The opening connects this article to the authors' Science Letter on making major single-patient outcomes public and linking them to preceding research. Visibility supplies the starting material; the present article asks which observation can justify which next action.

Evidence for KF1
MeasureValue
Starting pointPublicly visible major outcomes linked to preceding research
Added questionWhat should the next clinical team change?

Source locator: Publisher version of record, p. 1, left column, opening paragraph; p. 2, reference 1; Figure 1 caption.

Permalink to KF1

KF2 An earlier complication can inform safety monitoring while its cause remains uncertain.

The Letter summarises a separate report of experimental intrathecal antisense treatment in two children with severe KCNT1-related epilepsy. It describes fewer seizures alongside ventricular enlargement or hydrocephalus, and relates the first child's complication to closer monitoring of the second, a pause and resumption at lower doses after protocol revision. The example motivates safety learning; the authors do not infer a shared risk for all similar drugs.

Evidence for KF2
MeasureValue
Evidence sourcePreviously published two-child report, cited as reference 2
Action illustratedCloser monitoring and subsequent protocol adjustment
Interpretive scopeClinical experience informing vigilance before complete causal explanation

Source locator: Publisher version of record, p. 1, paragraph beginning "A recent report", continuing in the right column; p. 3, reference 2.

Permalink to KF2

KF3 Choose case similarity according to the safety or benefit question being asked.

For safety, a shared drug, dose or route can make an earlier case relevant across different diagnoses. For apparent benefit, the comparison instead starts with the course of illness before treatment and outcomes meaningful to the patient. Figure 1 adds event timing, severity and patient characteristics to the safety branch, and comparative cases and alternative explanations to the benefit branch.

Evidence for KF3
MeasureValue
Safety comparisonExposure, delivery, event timing and severity
Benefit comparisonPretreatment disease course, meaningful outcomes and appropriate comparative evidence

Source locator: Publisher version of record, pp. 1-2, paragraph beginning "That distinction matters"; Figure 1, safety-signal and treatment-benefit branches.

Permalink to KF3

KF4 Prognostic prediction answers a different question from whether a particular treatment works.

The authors use their previously published advanced-heart-failure survival model to illustrate this distinction. Estimating risk can describe prognosis; judging benefit asks whether the patient would have improved without treatment and needs a different evidential basis. The cited causal-machine-learning work provides context for treatment-effect estimation, rather than an effect estimate generated in this Letter.

Evidence for KF4
MeasureValue
Illustrative prior studySurvival assessment in advanced heart failure with renal dysfunction, reference 4
Target distinctionPredicted prognosis versus treatment effect
Comparison questionWould improvement have occurred without this treatment?

Source locator: Publisher version of record, p. 2, left column, continuation of "That distinction matters"; p. 3, references 3-5.

Permalink to KF4

KF5 Turn biological differences into competing explanations that require different measurements.

A diagnosis can contain distinct underlying biological states. The Letter cites single-cell and bulk-transcriptomic atherosclerosis research on smooth-muscle-cell states as an example of molecular heterogeneity that generates further questions. It distinguishes failure to affect an intended target from target engagement without functional restoration; these possibilities motivate different experiments rather than establishing different treatment responses.

Evidence for KF5
MeasureValue
Prior biological exampleSmooth-muscle-cell-associated atherosclerosis molecular subtypes, reference 6
Explanation to distinguishNo target engagement versus engagement without restored function
Research actionSelect measurements and experiments that discriminate explanations

Source locator: Publisher version of record, p. 2, left column, paragraph beginning "Biological differences"; p. 3, reference 6; Figure 1, mechanistic-hypothesis branch.

Permalink to KF5

KF6 Figure 1 groups the information needed for comparison into four complementary input domains.

The figure begins with an individualised treatment and an observed improvement or adverse event. Clinical course contains symptoms, signs, longitudinal trajectory and comorbidities. Treatment details contain drug, dose, route, timeline and concomitant therapy. Biological context contains genomics or multi-omics, cell state, pathways and target engagement. Prior cases and evidence include published reports, registries, databases and real-world experience. Together these feed the central proposed comparison process.

Evidence for KF6
MeasureValue
Patient contextClinical course and biological context
Exposure contextTreatment details and timing
External contextPrior cases and evidence

Source locator: Publisher version of record, p. 1, Figure 1, left-hand individualised-treatment panel and four input panels; Figure 1 caption.

Permalink to KF6

KF7 Use AI-assisted comparison to retrieve question-relevant cases and explain why they matter.

The proposed role is more specific than assigning an overall similarity label. The article suggests retrieval for a defined safety, benefit or mechanistic question, making pertinent similarities, differences and uncertainties visible. Exposure and event timing matter for a safety signal; baseline course and reliable outcome measures matter for benefit. Computational models may help select informative experiments when molecular findings support competing explanations. These are proposed uses of AI within clinical and research judgment.

Evidence for KF7
MeasureValue
Central functions in Figure 1Find relevant cases; assess similarities and differences; highlight uncertainty; suggest next steps
Mechanistic roleHelp choose an experiment to distinguish explanations
Development statusConceptual proposal, with no AI training or validation study reported

Source locator: Publisher version of record, p. 2, left column, paragraph beginning "AI could help"; p. 1, Figure 1 central comparison panel; p. 3, reference 7.

Permalink to KF7

KF8 Keep the three outputs of Figure 1 distinct while connecting them in a learning cycle.

The safety branch leads to adapted monitoring for early warning and risk mitigation. The mechanistic branch leads to measurements or experiments that test an explanation. The benefit branch asks whether treatment changed the outcome and calls for stronger comparative evidence to support decisions. The lower loop connects experience from one patient with the next through refined monitoring, generated hypotheses and future studies. The caption emphasises that observations useful for monitoring or investigation do not necessarily establish efficacy or causality.

Evidence for KF8
MeasureValue
Safety outputAdapt monitoring
Mechanistic outputTest the explanation
Benefit outputAccumulate stronger comparative evidence for benefit

Source locator: Publisher version of record, p. 1, Figure 1, three right-hand action branches, lower learning-across-patients loop and caption.

Permalink to KF8

KF9 Report major outcomes promptly and make shared cases useful without bypassing consent or privacy.

The closing paragraph asks case accounts to separate what was observed, what remains uncertain and what another team could reasonably change. It cites existing collaboration on individualised therapies as a setting for collecting experience. Major outcomes should be reported without waiting for a complete mechanism, while detailed patient-level sharing remains governed by consent and privacy safeguards. Better monitoring may be the first practical benefit of another patient's experience.

Evidence for KF9
MeasureValue
Useful case accountObserved outcome; uncertainty; justified next action
TimingPrompt major-outcome reporting before a complete mechanistic explanation
Patient-level dataConsent and privacy safeguards

Source locator: Publisher version of record, p. 2, left column, paragraph beginning "This gives case sharing"; p. 3, reference 8; Figure 1 lower reporting and learning panels.

Permalink to KF9

Article Scope & Approach

Article profile

Study Design
Methodological Invited Letter developing an argument through published examples and a conceptual Figure 1. The discussion proceeds from outcome reporting to safety, benefit, biological differences, AI-assisted comparison and practical case sharing.
Evidence Type
Conceptual framework and author reasoning, supported by eight references to reporting, individualised therapies, prognosis, treatment-effect inference, molecular heterogeneity, computational biology and collaboration.
Diseases Covered
KCNT1-related severe epilepsy (cited individualised antisense-treatment example), Advanced heart failure with renal dysfunction (cited prognostic-model example), Atherosclerosis (cited molecular-heterogeneity example), Genetic diseases and individualised therapies (methodological context)
Translation Scope
Use earlier observations to choose the next evidential action: monitoring, further investigation or treatment-benefit evaluation. The article proposes an AI-assisted research workflow; it reports no new patient cohort, treatment-effect estimate or validated AI system.

Evidence domains

  • Individualised-treatment outcome reporting and cross-case learning
  • Safety signals and exposure-based comparison
  • Prognostic prediction and comparative assessment of treatment benefit
  • Biological heterogeneity, target engagement and functional restoration
  • Question-specific AI-assisted case comparison
  • Consent, privacy and collaborative case sharing

What This Article Adds

  • A purpose-based link between a reported individual outcome and the next decision: monitoring, mechanistic investigation or evaluation of benefit.
  • An explanation of why exposure similarity, baseline disease course and biological state have different roles in choosing comparable cases.
  • A four-input, three-action conceptual workflow for interpretable AI-assisted comparison across patients.
  • A practical connection between prompt major-outcome reporting, collaborative learning and safeguards for detailed patient data.

Evidence Scope

Supports

  • The authors' methodological framework for learning across individualised-treatment cases.
  • Research-design discussion separating exposure-based safety signals, tests of mechanistic explanations and comparative assessment of benefit.
  • The distinction between prognostic risk prediction and treatment-effect estimation.
  • Discussion of proposed AI-assisted case retrieval, comparison and experiment selection.
  • A reporting rationale that combines prompt major-outcome visibility with consent and privacy for detailed data.

Does Not Establish

  • A new clinical trial, randomized N-of-1 experiment, patient cohort or treatment-effect estimate conducted for this Letter.
  • A trained or clinically validated AI case-comparison system, or measured improvement from using the framework.
  • Drug-class toxicity, differential treatment response of molecular subtypes or treatment causality inferred from the illustrative cases.

Limitations

  • This methodological Invited Letter develops a proposed workflow through prior publications and a conceptual figure; it does not empirically evaluate that workflow.
  • The KCNT1 treatment observations, heart-failure prognostic model and atherosclerosis molecular subtypes are examples from cited studies. Their populations and findings remain attributable to those original reports.
  • Monitoring relevance and hypotheses generated from a case do not by themselves establish treatment benefit or causality. Individualised-treatment cases should not all be relabelled as randomized crossover N-of-1 trials.
  • Detailed patient-level sharing remains subject to consent and privacy safeguards; timely major-outcome reporting does not imply unrestricted data release.

When This Article Is Useful to Cite

  1. CU1: How should a case report explain what another team can learn from an individualised therapy outcome?

    Cite the Letter's purpose-specific framework and its distinction between monitoring, investigation and benefit assessment.

    Evidence: KF1, KF3, KF8, KF9

  2. CU2: Why can exposure-related similarities support safety monitoring across different diagnoses?

    Cite the methodological rationale for comparing drug, dose, route and event timing; attribute the illustrative KCNT1 observations to the original report when using those observations directly.

    Evidence: KF2, KF3

  3. CU3: How can biological heterogeneity inform experiment selection after an individualised treatment?

    Cite the distinction between failed target engagement and engagement without functional restoration as competing explanations requiring different tests.

    Evidence: KF5, KF7

  4. CU4: What role could AI play in comparing individualised-treatment cases?

    Cite the proposed four-input comparison workflow and its three actions in Figure 1, keeping proposal status explicit.

    Evidence: KF6, KF7, KF8

  5. CU5: Why should prognostic prediction and treatment-effect evidence be distinguished?

    Cite the Letter's methodological distinction; use the original prognostic or causal-inference papers for their specific methods and empirical results.

    Evidence: KF4

What This Article Should Not Be Cited to Claim

  • Measured clinical effectiveness of AI-assisted case comparison.
  • A new treatment-effect estimate, a class-wide antisense-drug toxicity conclusion or established molecular-subtype treatment response.
  • A claim that every individualised treatment is a randomized crossover N-of-1 trial, or that prognosis alone identifies the best therapy.

Evidence Matrix

Row IDComponentContextFindingEvidence LevelScopeSource LocatorEvidence refs
evidence-ctm-safetySafety questionSelect cases by the relevant exposure and event context, potentially across diagnoses.Use drug, dose, route, event timing and severity to inform monitoring.Methodological argument with a cited clinical illustrationSafety relevance can justify vigilance without establishing drug-class risk.Publisher version of record, pp. 1-2, paragraph beginning "That distinction matters"; Figure 1, safety-signal and treatment-benefit branches.KF3
evidence-ctm-mechanismMechanistic questionApparent nonresponse may have different biological explanations.Distinguish absent target engagement from engagement without functional restoration and select an informative test.Mechanistic reasoning in a methodological LetterThe cited molecular subtypes motivate investigation rather than establish different treatment responses.Publisher version of record, p. 2, left column, paragraph beginning "Biological differences"; p. 3, reference 6; Figure 1, mechanistic-hypothesis branch.KF5
evidence-ctm-benefitTreatment-benefit questionImprovement after treatment must be interpreted against the prior course and alternatives.Use meaningful outcomes and appropriate comparative evidence to assess whether treatment changed the outcome.Methodological argument and conceptual figureRisk prediction and a temporally associated improvement are different from a treatment-effect estimate.Publisher version of record, pp. 1–2, paragraph beginning "That distinction matters"; p. 1, Figure 1 treatment-benefit branch and caption.KF3, KF4, KF8
evidence-ctm-sharingReporting and learningAnother team needs observations, uncertainty and the potential justified action.Report major outcomes promptly while protecting detailed patient-level data through consent and privacy safeguards.Closing argument and cited collaborative contextPrompt reporting need not wait for a complete mechanism or imply unrestricted data sharing.Publisher version of record, p. 2, left column, paragraph beginning "This gives case sharing"; p. 3, reference 8; Figure 1 lower reporting and learning panels.KF9

Q&A

How can an outcome from one individualised treatment inform the next patient?

Identify the question and match the comparison to it. The Letter separates safety monitoring, tests of mechanistic explanations and assessment of benefit. An earlier observation may justify closer monitoring or further investigation before it supports a change in treatment.

Evidence: KF1, KF3, KF8

What does the KCNT1 antisense-treatment example illustrate?

The Letter describes a previously published two-child report in which knowledge of the first child's complication prompted closer monitoring of the second. It uses the example to explain safety learning before a complete causal explanation, without generalising the complication to all similar drugs.

Evidence: KF2

Can an earlier case with a different diagnosis still inform safety monitoring?

Yes, when the relevant question concerns shared drug exposure, dose or route. The Letter argues that these similarities may matter even across diagnoses; Figure 1 also directs attention to event timing, severity and patient characteristics. The comparison should explain its relevance.

Evidence: KF3

What information matters when evaluating apparent treatment benefit?

Begin with the pretreatment disease course and reliable outcomes that matter to the patient. Figure 1 also asks for valid comparison with similar cases and consideration of alternative explanations. Benefit assessment asks whether the observed improvement would have occurred without the treatment.

Evidence: KF3, KF4, KF8

Why does an accurate survival prediction not identify the treatment that will work?

A prognostic model estimates an outcome or risk under its study conditions. Treatment-benefit assessment concerns the effect of a particular intervention compared with an appropriate alternative. The Letter uses prior heart-failure survival research to make this distinction and refers separately to treatment-effect inference.

Evidence: KF4

How can biological heterogeneity guide the next mechanistic experiment?

Cases sharing a diagnosis can differ in molecular state. The Letter contrasts a drug failing to engage its target with target engagement that does not restore function. These explanations require different measurements and experiments; its cited atherosclerosis subtypes supply a biological example, not evidence of different treatment responses.

Evidence: KF5

Which four input domains does Figure 1 propose for comparing patients?

Clinical course; treatment details; biological context; and prior cases and evidence. They bring together the longitudinal trajectory, drug exposure and timing, molecular or cellular state, and published or recorded experience. Figure 1 directs these domains into its central AI-assisted case-comparison process.

Evidence: KF6

What can AI contribute to learning across individualised-treatment cases?

The proposed role is to retrieve cases relevant to a specified question, show useful similarities and differences, highlight uncertainty and suggest next steps. Computational models may help select experiments. The Letter describes a conceptual role for AI rather than reporting a trained or validated system.

Evidence: KF7

How do the three action branches in Figure 1 differ?

The safety branch adapts monitoring; the mechanistic branch tests an explanation; and the benefit branch seeks stronger comparative evidence for a treatment decision. The learning loop connects these actions across patients while preserving their different evidential requirements.

Evidence: KF8

Should major outcomes wait for a complete mechanism before being reported?

The Letter argues for prompt reporting of major outcomes, with a clear account of observations, uncertainty and the action another team could reasonably take. It keeps that reporting goal distinct from unrestricted sharing of detailed patient-level data, which remains subject to consent and privacy safeguards.

Evidence: KF9

How does this article build on the Science Letter about single-patient outcome records?

The opening explicitly cites the Science Letter as reference 1 for public reporting and linkage to preceding research. The CTM article takes the next methodological step: deciding how visible outcomes should inform comparisons and future action. This is a verified CTM-to-Science citation, not a claim of reciprocal citation.

Evidence: KF1

Concepts & Entities

Research Design

Individualised therapiesCross-patient learningQuestion-specific case comparisonComparative treatment-benefit assessment

Safety And Exposure

Safety signalsDrug dose and routeEvent timing and severityAdaptive safety monitoring

Biological Reasoning

Biological heterogeneityTarget engagementFunctional restorationMechanistic hypothesis testing

Computational Methods

AI-assisted case retrievalClinical trajectoriesPrognostic predictionTreatment-effect estimation

Research Governance

Timely outcome reportingCase-sharing collaborationPatient consentPatient-data privacy

Related Research

Publication & Provenance

DOI
https://doi.org/10.1002/ctm2.70900
Publisher
https://doi.org/10.1002/ctm2.70900
Fulltext Pdf Url
https://drgezhang.com/assets/fulltext/ctm2-70900.pdf
License Url
https://creativecommons.org/licenses/by/4.0/
Review Basis
Complete publisher PDF read across all three pages; all main-text paragraphs, Figure 1 and caption, byline, correspondence details and eight references checked. Figure panels were visually inspected in rendered page images, including a higher-resolution rendering of page 1. The cited studies are used only in the role expressly described by this Letter.
Source Version
Published version of record, Clinical and Translational Medicine 2026;16:e70900, pp. 1-3; labelled Invited Letter. Received and revised 24 October 2026; accepted 1 November 2026. Existing unmodified hosted PDF SHA256: 9d689d55465340f13018aea57e1a89002ed11729091a7021e77df050cb4bd998. Its p. 1 footer provides a Creative Commons Attribution licence; the existing citation metadata identifies CC BY 4.0.
Editorial Scope
This author evidence explanation and the citation-use suggestions are website editorial content. They paraphrase the published argument and preserve its source locators; they are not a formal abstract or additional clinical evidence.
Author explanation of the complete three-page published Invited Letter, including Figure 1 and its eight references. Key Arguments distinguish the article's proposed framework from the prior studies used to illustrate it.

Study-level evidence table

Study-level author-maintained evidence summary. Not participant-level data and not a ready-to-pool meta-analysis dataset. For formal citation, use the original article DOI.

Download study-level evidence CSV (UTF-8)

Formula safety: cells starting with =, +, -, @ (after leading whitespace), or tab/CR/LF are prefixed with an apostrophe. Treat all cells as text; remove only that safety prefix when recovering the original string.