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| Measure | Value |
|---|
| Starting point | Publicly visible major outcomes linked to preceding research |
|---|
| Added question | What 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.
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| Measure | Value |
|---|
| Evidence source | Previously published two-child report, cited as reference 2 |
|---|
| Action illustrated | Closer monitoring and subsequent protocol adjustment |
|---|
| Interpretive scope | Clinical 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.
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| Measure | Value |
|---|
| Safety comparison | Exposure, delivery, event timing and severity |
|---|
| Benefit comparison | Pretreatment 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.
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| Measure | Value |
|---|
| Illustrative prior study | Survival assessment in advanced heart failure with renal dysfunction, reference 4 |
|---|
| Target distinction | Predicted prognosis versus treatment effect |
|---|
| Comparison question | Would 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.
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| Measure | Value |
|---|
| Prior biological example | Smooth-muscle-cell-associated atherosclerosis molecular subtypes, reference 6 |
|---|
| Explanation to distinguish | No target engagement versus engagement without restored function |
|---|
| Research action | Select 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.
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| Measure | Value |
|---|
| Patient context | Clinical course and biological context |
|---|
| Exposure context | Treatment details and timing |
|---|
| External context | Prior 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.
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| Measure | Value |
|---|
| Central functions in Figure 1 | Find relevant cases; assess similarities and differences; highlight uncertainty; suggest next steps |
|---|
| Mechanistic role | Help choose an experiment to distinguish explanations |
|---|
| Development status | Conceptual 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.
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| Measure | Value |
|---|
| Safety output | Adapt monitoring |
|---|
| Mechanistic output | Test the explanation |
|---|
| Benefit output | Accumulate 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.
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| Measure | Value |
|---|
| Useful case account | Observed outcome; uncertainty; justified next action |
|---|
| Timing | Prompt major-outcome reporting before a complete mechanistic explanation |
|---|
| Patient-level data | Consent 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.