Statistics diagnostic
Twenty-four questions covering everything a medical writer is expected to read, interpret and describe correctly — and a personal study order for the next four weeks
What this course assumes and what it does not
You are not going to become a statistician, and you do not need to. A medical writer needs to read statistical output correctly, describe it accurately, and recognise when a claim outruns the analysis. That is a different skill from generating the analysis, and it is the one that gets tested in interviews and enforced in QC.
No calculation by hand is required anywhere in this course. Every module works from output you would actually be handed — a table, a figure, a line from a statistical analysis plan.
Data types and descriptive statistics
Which summary belongs with which kind of data — and why reporting a mean for skewed survival data is the most common statistical error in clinical manuscripts
The four types of variable
Everything downstream — which summary, which test, which figure — follows from this classification. Get it wrong at the start and every choice after it is wrong too.
| Type | Clinical examples | Summarise with | Notes |
|---|---|---|---|
| Continuous | Age, weight, HbA1c, tumour diameter, blood pressure | Mean (SD) if symmetric Median (IQR) if skewed | Any value on a scale, with equal intervals. Differences are meaningful. |
| Ordinal | ECOG status, NYHA class, CTCAE grade, Likert scale | Median, or n (%) per category | Ordered, but gaps are not equal. Never report a mean CTCAE grade. |
| Nominal | Sex, tumour histology, country, treatment arm | n (%) | Categories with no order at all. |
| Binary | Responder, death, hospitalised, ≥ grade 3 event | n (%) with denominator | A special case of nominal with two levels. Always give the denominator. |
Write instead: median ECOG 1 (range 0–2), or the count in each category.
Mean or median: the skew test
The mean is dragged toward the tail; the median is not. When they diverge, the median is describing a typical patient and the mean is not.
Standard deviation is not standard error
| Standard deviation (SD) | Standard error (SE) | |
|---|---|---|
| Describes | Spread of individual patients around the mean | Precision of the estimated mean itself |
| As n grows | Stays roughly the same | Gets smaller |
| Use it for | Baseline tables, describing a population | Error bars on a mean, building confidence intervals |
| Answers | How variable are these patients? | How sure am I of this average? |
Drills
Age: mean 62.1, SD 9.4, median 62.0, IQR 55–69
Time since diagnosis (months): mean 31.4, SD 28.7, median 18.5, IQR 11.2–27.8
ECOG: 0 = 96 patients, 1 = 118, 2 = 26
Sex: male 141, female 99
Prior lines of therapy: median 2, IQR 1–3, range 0–7
“The median age was 62.0 years (IQR 55–69) and 141/240 patients (58.8%) were male. Median time since diagnosis was 18.5 months (IQR 11.2–27.8). ECOG performance status was 0 in 96 patients (40.0%), 1 in 118 (49.2%) and 2 in 26 (10.8%). Patients had received a median of 2 prior lines of therapy (IQR 1–3).”
The five decisions:
1. Age — mean 62.1 and median 62.0 are nearly identical, so the distribution is symmetric and either is defensible. Reporting the median throughout keeps the table internally consistent, which is usually the better choice.
2. Time since diagnosis — SD 28.7 is close to the mean 31.4, and the mean sits well above the median. Clear right skew. Median and IQR, not mean and SD.
3. ECOG — ordinal, so counts and percentages per category. No mean.
4. Sex — nominal binary, so n (%) with the denominator shown.
5. Prior lines — count data, skewed by a tail out to 7. Median and IQR. Note the range is given in the output but adds little; the IQR is more informative and less driven by one patient.
What separates a good writer here: not the paragraph, but noticing that time since diagnosis was skewed and querying it if the statistician had supplied only the mean. That query is the job.
Sampling, uncertainty and confidence intervals
Why every number in a trial is an estimate, what a confidence interval actually claims, and how to describe precision without saying something false
Every trial number is an estimate
A trial enrols a sample. The number you report — a median, a response rate, a hazard ratio — is an estimate of what would be seen in the whole population, and a different sample would have given a slightly different number. Everything in statistics is machinery for quantifying that wobble.
The technical meaning: if you repeated the study many times and computed a 95% CI each time, about 95% of those intervals would contain the true value. The confidence attaches to the procedure, not to any single interval.
This is why
there is a 95% probability the true value lies in this interval is wrong. The true value either is or is not in your particular interval — there is no probability about it once the study is done.Wrong: “95% of patients had a hazard ratio between 0.55 and 0.99.”
Wrong: “The true HR is 0.74.”
Right: “The hazard ratio was 0.74 (95% CI 0.55–0.99).”
Right: “The data are compatible with a hazard ratio between 0.55 and 0.99.”
Right: “The estimate was imprecise, and the upper limit of 0.99 does not exclude a clinically negligible benefit.”
In most documents you simply report the interval and let it speak. The interpretive sentences belong in a Discussion, where you are commenting on precision.
Reading width and position
A confidence interval carries two separate pieces of information, and writers usually read only one of them.
| What to look at | What it tells you | How to write about it |
|---|---|---|
| Does it cross the null? (1 for ratios, 0 for differences) | Whether no effect is compatible with the data | If it crosses, do not describe a benefit. Report the estimate and interval. |
| How wide is it? | How precisely the effect has been estimated | A wide interval warrants a precision comment even when it excludes the null. |
| Where is the far limit? | The most and least impressive effects still compatible with the data | An upper limit near the null means a trivial effect cannot be ruled out — say so. |
Drills
Key secondary (OS, immature): HR 0.82 (95% CI 0.61–1.10); p = 0.19
Prespecified subgroup, n = 28: HR 0.29 (95% CI 0.08–1.04)
Safety endpoint: risk difference 0.4 percentage points (95% CI −1.1 to 1.9)
Primary: “The study regimen reduced the risk of progression or death by 29% (HR 0.71, 95% CI 0.55–0.92; p = 0.009), with the interval excluding no effect across its full range.”
Key secondary: “Overall survival data were immature at this analysis; the hazard ratio of 0.82 (95% CI 0.61–1.10) is compatible with a moderate benefit but does not exclude no effect, and longer follow-up is required.”
Subgroup: “Although the point estimate in this subgroup was numerically favourable (HR 0.29), the confidence interval was very wide (95% CI 0.08–1.04) and includes no effect. With 28 patients, this analysis is hypothesis-generating only.”
Safety: “The risk difference was 0.4 percentage points (95% CI −1.1 to 1.9), a precise estimate that effectively excludes any clinically meaningful difference in this endpoint.”
The four different jobs:
1. Primary — a clean, precise result. State it plainly and do not over-qualify. Note the interval is described as excluding no effect, which is accurate.
2. Secondary — crosses 1 and is wide-ish. Name the reason (immaturity) and say what is needed.
3. Subgroup — the dramatic point estimate is the trap. Lead with the width and the n, not the 0.29.
4. Safety — crosses 0 but is narrow. This is the row most writers get wrong: a narrow interval around no difference is positive evidence of no difference, and saying so is more useful than “not significant”.
Check yourself: if your sentences for results 2 and 4 said roughly the same thing, re-read the four-interval table above. That distinction is the point of this module.
The p value
The most misused number in medicine — what it measures, the four things it does not, and how to write about significance without making a claim you cannot support
Everything hangs on that conditional. The p value is computed assuming there is no effect and asks how surprising your data would be under that assumption. A small p value means the data sit awkwardly with the null.
It does not tell you the probability that the null is true, the probability that the treatment works, or how large or important the effect is.
The four misreadings
This is why modern reporting standards ask for exact p values with effect sizes and intervals, rather than a bare significant or not significant. Write p = 0.048, not p < 0.05, unless the value is below 0.001.
Spin language, and what to write instead
All of these describe a non-significant result as though it were partly significant. Journals, regulators and MLR reviewers all treat them as spin, and BMJ and several others name them explicitly in their guidance.
Write instead: “The rate was numerically higher in the treatment arm (34% vs 28%), but the difference was not statistically significant (p = 0.09).”
Or, if the interval is informative: “The difference was 6 percentage points (95% CI −1 to 13), which does not exclude no effect.”
Statistical significance is not clinical significance
| Scenario | Statistically significant? | What to write |
|---|---|---|
| 1.2 point difference on a 100-point scale, n = 8,000, p < 0.001 | Yes | Report the effect size prominently. State that the difference is below the accepted minimal clinically important difference, if one exists. |
| 9-month median OS gain, n = 60, p = 0.08 | No | Report the estimate and interval. Note the study was underpowered rather than implying no effect. |
| HR 0.71, n = 800, p = 0.009 | Yes | Report both. Effect is meaningful and precisely estimated — the straightforward case. |
| 0.4 point difference, n = 4,000, p = 0.31 | No | A precise null. Say the data effectively exclude a meaningful difference. |
Drills
2. “The secondary endpoint showed a strong trend towards benefit and approached significance (p = 0.06).”
3. “With p = 0.02, there is a 98% probability that the drug is effective.”
4. “No difference was found between arms (p = 0.42).”
Context for 4: risk difference 3.1 percentage points, 95% CI −4.4 to 10.6, n = 180.
Why: highly significant attaches magnitude to a p value; proving is unavailable to a single trial; substantial clinical benefit is an unsupported judgement. Supply the effect size and let it carry the argument.
2. “The rate was numerically higher in the treatment arm (34% vs 28%); the difference was not statistically significant (p = 0.06).”
Why: strong trend and approached significance are both flagged as spin. Numerically higher states what was seen without implying a conclusion.
3. “The difference was statistically significant (p = 0.02).”
Why: the 98% claim inverts the conditional. There is no way to convert a p value into a probability that the drug works — that would require a Bayesian analysis with a stated prior, which this is not.
4. “The risk difference was 3.1 percentage points (95% CI −4.4 to 10.6); the study was not powered to exclude a clinically relevant difference.”
Why: this is the most important of the four. No difference was found asserts equivalence from a non-significant result. The interval runs from a 4-point harm to a 10-point benefit — the study is uninformative, not negative. Writing it as no difference is a false negative claim, and in a safety context that is a serious error.
Score yourself: if you fixed 1, 2 and 3 but wrote 4 as “no significant difference was observed,” you improved the wording without fixing the error. Sentence 4 is the one that separates people who have learned the vocabulary from people who have learned the logic.
Hypothesis testing, power and multiplicity
Why sample size is fixed before the first patient is enrolled, what 80% power actually promises, and why testing twelve endpoints without a plan produces a false positive almost half the time
The two errors
| Type I error (α) | Type II error (β) | |
|---|---|---|
| What happens | You conclude there is an effect when there is none | You miss a real effect |
| Everyday name | False positive | False negative |
| Conventional level | 0.05, usually two-sided | 0.20, giving 80% power |
| Who it harms | Patients given an ineffective drug; regulators guard this hard | Patients denied an effective drug; sponsors bear this risk |
| Controlled by | The significance threshold and multiplicity adjustment | Sample size and effect size assumptions |
1 − β.The word specified carries the whole meaning. A trial powered at 80% to detect a hazard ratio of 0.70 has considerably less than 80% power to detect a hazard ratio of 0.85. When someone says a trial was adequately powered, the correct follow-up question is: powered for what effect size?
Power depends on four things: the effect size you want to detect, the variability of the outcome, the significance level, and the sample size. Fix any three and the fourth follows.
If a reviewer asks why a result was non-significant, the answer is the confidence interval, not a retrospective power calculation. Several journals explicitly reject post hoc power analyses.
Multiplicity
Every additional test at α = 0.05 adds another chance of a false positive. The inflation is fast and it is not intuitive.
| Strategy | How it works | Where you will meet it |
|---|---|---|
| Bonferroni | Divide α by the number of tests. Simple and conservative. | Small numbers of comparisons; safety analyses. |
| Holm | Step-down version of Bonferroni. Uniformly more powerful, same protection. | Increasingly the default where Bonferroni was once used. |
| Fixed-sequence hierarchy | Endpoints tested in a prespecified order; testing stops at the first failure. | Most Phase III oncology and cardiovascular trials. |
| Alpha spending | The type I error budget is split across interim and final analyses. | Any trial with a formal interim analysis and a DSMB. |
| False discovery rate | Controls the proportion of significant findings that are false, rather than the chance of any. | Genomics, biomarker screening, high-dimensional data. |
Writing “significant” for an endpoint below a hierarchy break is one of the few statistical errors that can have regulatory consequences, and it is entirely avoidable by reading one page of the SAP.
- Frequentist (95% Confidence Interval): Assumes the true parameter is a fixed unknown constant. A 95% CI means that across repeated identical hypothetical trials, 95% of generated intervals would contain the true value.
- Bayesian (95% Credible Interval / CrI): Combines prior evidence with current trial data to produce a posterior probability distribution. A 95% Credible Interval means there is an actual 95% probability that the true parameter lies within that interval.
Drills
Output:
PFS: HR 0.68 (95% CI 0.54–0.86); p = 0.001
OS: HR 0.86 (95% CI 0.68–1.09); p = 0.21
ORR: 47% vs 31%; p = 0.002
PRO score change: −4.1 vs −1.2; p = 0.03
“The primary endpoint was met: median progression-free survival favoured the study regimen (HR 0.68, 95% CI 0.54–0.86; p = 0.001). Overall survival did not differ significantly between arms (HR 0.86, 95% CI 0.68–1.09; p = 0.21), and in accordance with the prespecified testing hierarchy, formal testing stopped at this endpoint. Objective response rate was 47% versus 31% (nominal p = 0.002) and the mean change in patient-reported outcome score was −4.1 versus −1.2 (nominal p = 0.03); as these endpoints fall below the hierarchy break, both are reported descriptively and are not controlled for type I error.”
The three things that make this correct:
1. PFS is the only endpoint described as met or significant.
2. The hierarchy break is stated explicitly, in the sentence where it happens.
3. ORR and PRO are reported in full with nominal p values and an explicit statement that they are uncontrolled. Not omitted, not called significant.
The trap: ORR at p = 0.002 is a smaller p value than the primary endpoint. It is very tempting to call it significant, and it is the strongest-looking secondary result in the set. That temptation is exactly what the hierarchy exists to defeat.
Choosing and naming the right test
You will not select the test — but you will describe it in Methods, and naming the wrong one is a QC finding. A decision table that covers almost everything you will meet
The decision table
Two questions determine almost every choice: what type is the outcome, and are the groups independent or paired.
| Outcome | Comparison | Standard test | Non-parametric alternative |
|---|---|---|---|
| Continuous | 2 independent groups | Independent t-test | Wilcoxon rank-sum (Mann–Whitney U) |
| 2 paired measurements | Paired t-test | Wilcoxon signed-rank | |
| 3+ groups | ANOVA | Kruskal–Wallis | |
| Categorical / binary | 2 independent groups | Chi-square | Fisher exact (small expected counts) |
| 2 paired measurements | McNemar test | — | |
| Ordinal | 2 groups | Wilcoxon rank-sum | Cochran–Armitage for trend |
| Time to event | 2+ groups | Log-rank test | Cox proportional hazards for adjusted estimates |
| Continuous, adjusted | 2+ groups + covariates | ANCOVA or linear regression | — |
| Binary, adjusted | 2+ groups + covariates | Logistic regression | — |
| Repeated over time | Within and between | Mixed model for repeated measures (MMRM) | — |
The practical signal, straight from Module 1.2: if the data were summarised with a median and IQR, the test is almost certainly non-parametric. If summarised with a mean and SD, it is probably parametric. This one heuristic will make your Methods sections consistent with your tables.
Chi-square where expected cell counts are under 5 — should be Fisher exact.
Unpaired test for paired data — before and after in the same patient is paired.
t-test for time-to-event data — impossible with censoring.
ANOVA reported without saying which post hoc comparison was used.
Multivariate when you mean multivariable — multivariable means several predictors and one outcome, which is nearly always what you mean. Multivariate means several outcomes.
Drills
• Primary endpoint PFS: Kaplan–Meier; stratified log-rank; HR from stratified Cox model. Stratification factors: region, prior lines.
• ORR: compared with chi-square; 95% CI by Clopper–Pearson.
• Change in EORTC QLQ-C30 score: MMRM with treatment, visit, treatment-by-visit interaction, and baseline score.
• Time since diagnosis (skewed): summarised as median (IQR); compared with Wilcoxon rank-sum.
• All tests two-sided at α = 0.05. Fixed-sequence hierarchy: PFS → OS → ORR.
“All tests were two-sided at a significance level of 0.05. Progression-free survival was estimated using the Kaplan–Meier method and compared between arms using a stratified log-rank test; hazard ratios with 95% confidence intervals were derived from a stratified Cox proportional hazards model, with region and number of prior lines of therapy as stratification factors. Objective response rate was compared using a chi-square test, with 95% confidence intervals calculated by the Clopper–Pearson method. Change from baseline in EORTC QLQ-C30 score was analysed using a mixed model for repeated measures including treatment, visit, treatment-by-visit interaction and baseline score. Continuous variables with skewed distributions were summarised as median (interquartile range) and compared using the Wilcoxon rank-sum test. Multiplicity was controlled by a fixed-sequence testing procedure in the order progression-free survival, overall survival, objective response rate.”
Five things to check in your version:
1. Stratified appears on both the log-rank test and the Cox model, and the stratification factors are named. Dropping the word stratified is a very common omission.
2. The CI method for ORR is named. Clopper–Pearson is not the only option and reviewers ask.
3. The MMRM terms are listed. An MMRM described without its model terms is not reproducible.
4. The Wilcoxon is tied to skewness, which keeps Methods consistent with the tables.
5. The multiplicity strategy is stated. This is the sentence most often missing from writer-drafted Methods, and its absence is a CONSORT gap.
Effect measures: RR, OR, HR and NNT
Four ways to express the same benefit, three of which are routinely described in language that belongs to one of the others — and the relative-versus-absolute distinction that drives most promotional review findings
The four measures
| Measure | What it is | Null value | How to describe it |
|---|---|---|---|
| Risk ratio (RR) | Risk in treated ÷ risk in control | 1 | “The risk was 30% lower” for RR 0.70. Relative language. |
| Odds ratio (OR) | Odds in treated ÷ odds in control | 1 | “The odds were 30% lower.” Odds, not risk — unless the outcome is rare. |
| Hazard ratio (HR) | Ratio of instantaneous event rates over time | 1 | “The risk of progression or death was reduced by 32%.” Not a ratio of medians. |
| Risk difference (ARR) | Risk in control − risk in treated | 0 | “4 fewer events per 100 patients treated.” Absolute language. |
| NNT | 1 ÷ absolute risk reduction | ∞ | “25 patients would need to be treated to prevent one event.” |
With a 5% baseline risk, OR 2.0 corresponds to roughly RR 1.9 — close enough that the shorthand is forgivable. With a 40% baseline risk, OR 2.0 corresponds to roughly RR 1.4. Describing that as doubling the risk overstates the effect by more than half.
Safe wording: “the odds of response were approximately twice as high.” Say odds when you have odds.
Correct: “a 32% reduction in the risk of progression or death.”
Wrong: “survival was 32% longer”, “32% of patients benefited”, “patients lived 32% longer”.
The relationship between a hazard ratio and a difference in median survival depends on the shape of the curves and is not fixed.
- Control Arm (1,000 patients): 40 strokes occur → Baseline Event Rate = 4.0% (0.040)
- Treatment Arm (1,000 patients): 20 strokes occur → Treatment Event Rate = 2.0% (0.020)
| Metric | Calculation | Value & Exact Medical Writing Interpretation |
|---|---|---|
| Relative Risk (RR) | 2.0% / 4.0% | 0.50 — Patients on drug had half the risk of stroke. |
| Relative Risk Reduction (RRR) | (4.0% - 2.0%) / 4.0% | 50% — Relative reduction in stroke rate. |
| Absolute Risk Reduction (ARR) | 4.0% - 2.0% | 2.0% — Absolute reduction in stroke incidence. |
| Number Needed to Treat (NNT) | 1 / ARR (1 / 0.02) | 50 — You must treat 50 patients to prevent 1 stroke. |
Drills
2. OR 1.85 (95% CI 1.21–2.83); baseline response rate 38%
3. HR 0.68 (95% CI 0.54–0.86); median PFS 8.2 vs 5.1 months
4. ARR 7.2 percentage points; NNT 14
Why: a lay summary converts the relative measure into natural frequencies. 24% × 0.70 ≈ 17%.
2. “People taking the study drug were more likely to respond; the odds of responding were about 1.9 times higher.”
Why: the outcome is common at 38%, so this OR must not be described as almost doubling the chance of response. If the audience needs a risk statement, request the adjusted risk difference.
3. “The study drug lowered the risk of the cancer getting worse, or of death, by about a third. On average, people taking it went about three months longer before their cancer worsened.”
Why: the HR becomes a risk reduction; the median difference is reported as an observed time difference, not derived from the HR.
4. “About 7 fewer events occurred for every 100 people treated. Put another way, about 14 people would need to take the drug for one additional person to avoid an event.”
Why: ARR and NNT are two views of the same number, and pairing them is more informative than either alone.
The common failure: using percentages for everything. Natural frequencies — 17 in 100 rather than 17% — are consistently better understood by patients and by clinicians, and health literacy research supports it. This matters for lay summaries, patient information and increasingly for plain-language abstracts.
Reporting precision and intervals
The conventions that make statistical text pass QC first time — decimals, denominators, intervals, and the CONSORT requirement that every effect estimate carries its uncertainty
The rules
| Rule | Right |
|---|---|
| Every effect estimate carries an interval. CONSORT item 17a. | HR 0.68 (95% CI 0.54–0.86) |
| Every percentage carries its denominator. | 18/240 (7.5%), not 7.5% |
| Match decimal places across arms and across a table. | 8.2 vs 5.1 months, not 8.2 vs 5 |
| Leading zero on values below 1. | 0.68, not .68 |
| Exact p values to three decimals; below that, use the inequality. | p = 0.009; p < 0.001; never p = 0.000 |
| State the confidence level. | 95% CI, not CI |
| En dash for intervals; to when a value is negative. | 0.54–0.86; −4.4 to 10.6 |
| Do not over-report precision beyond the measurement. | 62.1 years, not 62.1374 years |
| Percentages to one decimal at most, and to none if n < 100. | With n = 40, 3/40 (8%), not (7.5%) |
| Name the interval method where it is not obvious. | 95% CI by Clopper–Pearson |
Write −4.4 to 10.6. This applies to any interval containing a negative value — mean differences, risk differences, and change-from-baseline scores.
Convention: with n under 100, give percentages as whole numbers. With n under 20, many journals ask for counts only. Over-precise percentages are a common signal to reviewers that the writer is transcribing output rather than reading it.
Drills
Denominators: 240 randomised, 40 in the safety subgroup for grade 3+.
The twelve:
1. 5 months → 5.1 months — decimal precision must match across arms.
2. .68 → 0.68 — leading zero.
3. CI → 95% CI — state the level.
4. Hyphen → en dash in 0.54–0.86.
5. p=0.000 → p < 0.001, italic, with spaces.
6. 46.75% → one decimal at most, and add the count and denominator.
7. 7.5% on n = 40 → 3/40 (8%) — denominator and appropriate rounding.
8. 3.1374 → 3.1 — over-precision the interval contradicts.
9. -4.4-10.6 → −4.4 to 10.6 — negative limit takes to, and a true minus sign.
10. 18 patients → 18/240 (7.5%).
11. significant at p<0.05 → redundant once the exact p value is given; delete.
12. Median follow-up 24 months → give the IQR or reverse Kaplan–Meier interval; a bare median follow-up is uninterpretable.
Score yourself: 10 or more and your reporting will pass QC first time. Items 7, 9 and 12 are the ones experienced writers still miss.
Biomarkers, ROC curves and diagnostic accuracy
Sensitivity, specificity, predictive values, and AUC — the essential statistics of companion diagnostics, patient stratification, and precision oncology
1. The 2×2 Diagnostic Contingency Table
Every diagnostic test, companion diagnostic (CDx), and biomarker assay is evaluated against a Reference Standard (the clinical truth or gold standard). Results fall into four mutually exclusive cells:
Patient has disease & tests positive.
Patient is healthy & tests positive (Type I error).
Patient has disease & tests negative (Type II error).
Patient is healthy & tests negative.
2. Sensitivity and Specificity — Intrinsic Test Properties
Sensitivity and Specificity describe how well the assay itself performs. They are intrinsic to the test and do not change when the test is used in different populations.
Sensitivity = TP ÷ (TP + FN)Specificity = TN ÷ (TN + FP)3. PPV and NPV — The Clinical Reality (Prevalence Dependency)
Clinicians and patients don't know the truth in advance—they only have the test result in hand. They ask: "Given that my test is positive, what is the probability that I actually have the mutation?"
- Positive Predictive Value (PPV):
TP ÷ (TP + FP)— Probability that a test-positive patient truly has the disease. - Negative Predictive Value (NPV):
TN ÷ (TN + FN)— Probability that a test-negative patient is truly disease-free.
| Population | Prevalence | Test Sensitivity / Specificity | Resulting PPV |
|---|---|---|---|
| Oncology Clinic (High-risk) | 20% (200/1,000) | 90% Sensitivity / 95% Specificity | 81.8% PPV |
| General Screening (Low-risk) | 1% (10/1,000) | 90% Sensitivity / 95% Specificity | 15.3% PPV (85% of positives are false!) |
4. Receiver Operating Characteristic (ROC) Curves & AUC
When a biomarker is continuous (e.g., PSA level, ctDNA copy number, PD-L1 tumour proportion score), you must pick a cut-off threshold. Lowering the threshold increases sensitivity but reduces specificity. The ROC Curve plots this trade-off across every possible cut-off value.
X-Axis: 1 − Specificity (False Positive Rate, from 0 to 1.0).
• 0.50: No discrimination
• 0.70–0.80: Acceptable discrimination
• 0.80–0.90: Excellent discrimination
• >0.90: Outstanding discrimination
J = Sensitivity + Specificity − 15. Inter-Rater Agreement — Cohen's Kappa (κ)
In clinical trials involving pathology scoring (e.g., HER2 immunohistochemistry 0, 1+, 2+, 3+), two pathologists will review the same slide. Simple percentage agreement is misleading because two observers will agree on many cases purely by chance. Cohen's Kappa ($\kappa$) corrects for chance agreement:
| Kappa (κ) Value | Level of Agreement | Regulatory & Clinical Context |
|---|---|---|
| < 0.40 | Poor to Fair | Unacceptable for a clinical trial diagnostic endpoint. |
| 0.41 – 0.60 | Moderate | May require central laboratory re-adjudication. |
| 0.61 – 0.80 | Substantial | Standard regulatory benchmark for companion diagnostics. |
| 0.81 – 1.00 | Almost Perfect / Excellent | High concordance across independent central reviewers. |
6. Standard Sentence Templates for Medical Writers
ROC-AUC Discriminatory Power: "The novel plasma biomarker demonstrated excellent discriminatory accuracy for distinguishing responders from non-responders, with an area under the ROC curve of 0.88 (95% CI: 0.82–0.94; p < 0.001; Figure 3)."
Inter-Rater Concordance: "Inter-observer concordance between the two independent pathologists for HER2 expression scoring was substantial, with an overall agreement of 89.2% and a Cohen's kappa coefficient of 0.78 (95% CI: 0.70–0.86)."
Drills
Randomisation, blinding and allocation
Four separate safeguards that writers routinely collapse into one word — and the interview question that separates people who have read a protocol from people who have not
The four safeguards, in time order
| Safeguard | When it acts | What it prevents | Fails when |
|---|---|---|---|
| Randomisation | At assignment | Systematic differences between arms, including on factors nobody measured | Assignment follows a predictable pattern (alternate patients, date of birth) |
| Allocation concealment | Immediately before and at assignment | The enrolling investigator steering a patient into a preferred arm | The next assignment is guessable — unsealed lists, translucent envelopes |
| Blinding (masking) | After assignment, throughout | Differential treatment, reporting and outcome assessment | Distinctive side effects, differing formulations, unblinding events |
| Stratification | At assignment | Chance imbalance in known strong prognostic factors | Too many strata for the sample size, leaving thin cells |
Blinding is about everything afterwards: do the patient, investigator, and outcome assessor know which treatment was given?
An open-label trial can have perfect allocation concealment — the assignment is made by a central interactive response system and revealed only after the patient is irrevocably enrolled. Everyone then knows the treatment, but nobody could have gamed the assignment. Empirically, poor allocation concealment inflates effect estimates more than lack of blinding does.
Levels of blinding
| Term | What it usually means — but always check the protocol |
|---|---|
| Open-label | Everyone knows. Common where formulations differ, or in oncology where toxicity profiles are unmistakable. |
| Single-blind | Usually the patient is blinded. Ambiguous — CONSORT asks you to state who was blinded rather than use this label. |
| Double-blind | Usually patient and investigator. Also ambiguous; state the roles. |
| Blinded independent central review (BICR) | Radiological outcomes assessed centrally by assessors unaware of allocation. Standard in open-label oncology trials to protect the endpoint even when treatment is visible. |
| Double-dummy | Each arm receives active drug plus placebo matching the other arm, so the regimens look identical. |
Correct: “Participants, investigators and outcome assessors were blinded to treatment assignment; the study drug and placebo were identical in appearance.”
Judge imbalance by clinical importance, not by p value. If a strong prognostic factor is visibly imbalanced, the answer is a prespecified adjusted analysis, not a significance test.
Drills
• Randomised 1:1 via central IWRS, permuted blocks of 4, stratified by region (Asia / non-Asia) and prior lines (1 vs ≥2).
• Open-label. Patients and investigators aware of assignment.
• Primary endpoint PFS assessed by blinded independent central review per RECIST v1.1.
• Sequence generated by an independent statistician not otherwise involved in the trial.
“Patients were randomly assigned in a 1:1 ratio to the study regimen or control. The randomisation sequence was generated by an independent statistician not otherwise involved in the conduct of the trial, using permuted blocks of four, and was stratified by region (Asia versus non-Asia) and number of prior lines of therapy (1 versus ≥2). Allocation was implemented through a central interactive web response system, so that investigators were unaware of the next assignment before a patient was enrolled. The trial was open-label: patients and investigators were aware of treatment assignment after randomisation. To limit assessment bias, the primary endpoint of progression-free survival was assessed by blinded independent central review according to RECIST version 1.1.”
The four CONSORT items covered:
8a — method of sequence generation (permuted blocks, independent statistician).
8b — type of randomisation and stratification factors, with their levels spelled out.
9 — allocation concealment mechanism (central IWRS), stated explicitly as concealment rather than left implied.
11a — who was blinded and who was not, by role, plus the mitigation used for the endpoint.
What most drafts get wrong: writing “patients were randomised 1:1 in an open-label trial” and stopping. That sentence satisfies none of the four items, and it leaves a reviewer unable to judge the trial's internal validity. Note also that the block size is disclosed here — some sponsors withhold it during conduct to protect concealment, so check before publishing it.
Analysis populations
ITT, mITT, per-protocol, evaluable, safety — five populations, five different denominators, and the mistake of using the wrong one for adverse event tables
The five populations
| Population | Who is included | Analysed by | Used for |
|---|---|---|---|
| Intention-to-treat (ITT) | Everyone randomised, regardless of what they received or whether they were followed | Arm randomised to | Primary efficacy. Preserves randomisation. |
| Modified ITT (mITT) | Randomised patients meeting some minimum criterion — usually at least one dose and one post-baseline assessment | Arm randomised to | Efficacy where a definition is needed. Definition varies by trial — always check the SAP. |
| Per-protocol (PP) | Patients who completed treatment without major protocol deviations | Arm randomised to | Supportive analysis; primary in some non-inferiority settings. |
| Evaluable | Patients with an assessable outcome (e.g. measurable disease at baseline and one scan) | Arm randomised to | Response-rate endpoints. |
| Safety | All who received at least one dose | Treatment actually received | All adverse event reporting. |
A patient randomised to control who mistakenly received the study drug is counted in the control arm for efficacy and in the study drug arm for safety. This is not inconsistency — the two analyses answer different questions. Efficacy asks about a treatment strategy; safety asks about an exposure.
Excluding patients after randomisation breaks randomisation. Patients who deviate from protocol are systematically different — often sicker, or experiencing toxicity — and they do not deviate at equal rates in both arms. A per-protocol analysis therefore compares two non-randomly-selected groups.
PP is a supportive analysis. If ITT and PP disagree substantially, that discrepancy is itself a finding and belongs in the Discussion.
Because the definition is discretionary, mITT is the analysis population most open to criticism, and reviewers scrutinise it. Never write "mITT" without reproducing the trial's own definition in the same sentence, and check that your definition matches the SAP exactly.
Drills
Tables to produce: (1) primary PFS analysis, (2) objective response rate, (3) treatment-emergent adverse events, (4) supportive sensitivity analysis of PFS.
“Efficacy analyses were conducted in the intention-to-treat population, comprising all 240 randomised patients analysed according to the treatment arm to which they were assigned. The modified intention-to-treat population, used for response-rate analyses, comprised the 226 patients who received at least one dose and had at least one post-baseline tumour assessment. The safety population comprised the 233 patients who received at least one dose, analysed according to the treatment actually received; four patients randomised to control who received the study drug in error were included in the study-drug group for safety analyses. The per-protocol population, comprising the 198 patients who completed treatment without a major protocol deviation, was used for a supportive sensitivity analysis.”
The four denominators:
1. Primary PFS — ITT, n = 240 (120 per arm). Randomisation preserved.
2. Objective response rate — mITT, n = 226. Response cannot be assessed without a post-baseline scan, and the definition is stated explicitly.
3. Treatment-emergent adverse events — safety, n = 233, split 122 study drug and 111 control, not 118/115. The four cross-over patients move to the study-drug group because that is what they were exposed to.
4. Supportive sensitivity analysis — per-protocol, n = 198, explicitly labelled supportive.
The item that catches people: table 3. The instinct is to keep the arms at 118 and 115 because that is how the doses were assigned by randomisation. Safety follows exposure, so the four misdosed patients move. If your answer kept them in control, re-read the rule box above — this exact scenario appears in interviews and in real CSRs.
Estimands, intercurrent events and missing data
ICH E9(R1) — the framework that forces you to state precisely what question a trial is answering, before anyone looks at the data. Now expected in every regulatory submission
ICH E9(R1), the 2019 addendum to the statistical principles guideline, requires five attributes:
1. Population — which patients2. Variable — which endpoint3. Intercurrent events — what post-randomisation events might occur, and how each is handled4. Population-level summary — difference in means, hazard ratio, risk difference5. Treatment condition — the regimens being comparedAttribute 3 is the one that was previously left implicit, and it is where almost all the disagreement lived.
Intercurrent events
An intercurrent event is anything happening after randomisation that affects the interpretation or the very existence of the outcome. These are not protocol deviations and they are not missing data — though they can cause missing data.
| Event | Why it complicates the outcome |
|---|---|
| Discontinuation for toxicity | The patient is no longer on treatment; is their later score a treatment result? |
| Discontinuation for lack of efficacy | Same, but informatively — the reason is related to the outcome. |
| Rescue or additional medication | Any subsequent improvement may belong to the rescue, not the study drug. |
| Treatment switching or crossover | Common in oncology; dilutes an overall survival comparison. |
| Death from an unrelated cause | A symptom score cannot exist after death — the variable does not merely go missing, it ceases to be defined. |
The five strategies
| Strategy | How the Event is Handled | Concrete Clinical Analogy (Blood Pressure Trial) | The Question It Answers |
|---|---|---|---|
| Treatment policy | Ignore the event — collect and use the outcome regardless of what happened. | Patient develops mild cough at Week 4, stops study drug, and takes generic pill. Blood pressure is still measured at Week 12 and analysed. | What is the effect of prescribing the treatment strategy in real clinical practice? (Standard ITT). |
| Composite | Incorporate the intercurrent event directly into a composite binary endpoint. | Patient requires emergency antihypertensive rescue at Week 6. Patient is automatically classified as a "Treatment Failure / Non-responder". | Did the patient achieve target blood pressure without needing rescue medication? |
| Hypothetical | Estimate what the outcome would have been had the event not occurred. | Patient moves to another country or suffers an unrelated fracture. Statistical models estimate their Week 12 blood pressure had they stayed. | What would the drug effect be in the hypothetical scenario where no dropouts occurred? |
| While on treatment | Evaluate the outcome only up to the exact moment the intercurrent event occurred. | Patient takes drug for 5 weeks before discontinuing due to headache. Blood pressure reduction is evaluated up to Week 5 only. | What is the rate of benefit or adverse events while the patient is actively taking the drug? (Safety tables). |
| Principal stratum | Restrict the analysis to the subset of patients who would never experience the event under either treatment arm. | Identify the biological subpopulation that would not develop cough regardless of whether given drug or placebo. | What is the treatment effect in the specific biological subpopulation capable of tolerating the drug? |
Regulators now expect the estimand to be stated explicitly in the protocol, the SAP and the CSR. If you cannot find it, ask. Writing Results without knowing the estimand is writing an answer without knowing the question.
Missing data
| Mechanism | Meaning | Consequence |
|---|---|---|
| MCAR missing completely at random | Missingness unrelated to anything — a sample tube broke | Complete-case analysis is unbiased, just less precise. Rare in practice. |
| MAR missing at random | Missingness explained by observed variables — sicker patients drop out, and you measured sickness | Multiple imputation or MMRM are valid. The usual working assumption. |
| MNAR missing not at random | Missingness depends on the unobserved value itself — patients drop out because they deteriorated, unmeasured | No method fixes this. Requires sensitivity analysis under explicit assumptions. |
LOCF is now discouraged in regulatory settings. If you find it in a study you are writing up, that is a limitation to state, not a detail to pass over. Preferred approaches are multiple imputation, MMRM, or a prespecified estimand strategy that handles the event directly rather than patching the gap.
Drills
Endpoint: proportion achieving EASI-75 at week 16.
Intercurrent events: (a) use of rescue topical corticosteroids — handled as treatment failure; (b) permanent discontinuation of study drug — handled as treatment failure.
Summary: risk difference between arms.
“The primary estimand was defined as follows. The population was adults with moderate-to-severe atopic dermatitis meeting the trial eligibility criteria. The variable was achievement of at least a 75% improvement in Eczema Area and Severity Index score (EASI-75) at week 16. Two intercurrent events were addressed using a composite strategy: patients who used rescue topical corticosteroids, and patients who permanently discontinued study drug, were classified as not achieving EASI-75 regardless of their observed score. The population-level summary was the difference in the proportion achieving EASI-75 between arms. The treatment condition was drug X compared with placebo over 16 weeks.”
The five attributes, checked:
1. Population — stated, and tied to eligibility criteria.
2. Variable — named precisely, with the threshold and the timepoint.
3. Intercurrent events — both named, and the strategy named as composite. This is where most drafts fall short: they list the events without naming the strategy, or name a strategy without listing the events.
4. Summary — risk difference, stated explicitly. Not left to be inferred from the tables.
5. Treatment condition — both arms and the duration.
Why the composite strategy here: in dermatology, using rescue steroids is itself a sign the treatment is not working. Counting a patient as a responder because their skin improved on steroids would credit the study drug with the steroid effect. Composite folds the event into the definition of failure, which matches the clinical question. Note this also means the analysis needs no imputation for these patients — the composite strategy has answered the missing-data question by definition.
Time-to-event and survival analysis
Kaplan–Meier curves, censoring, hazard ratios and the proportional hazards assumption — the analysis you will describe more often than any other, and the one most often described wrongly
Censoring
Reasons: the study ended, the patient withdrew, they were lost to follow-up, or they reached a competing endpoint.
Censoring is not missing data and not failure. It is partial information, and survival methods exist precisely to use it. A t-test cannot — which is why time-to-event data need Kaplan–Meier and Cox, not a comparison of means.
That assumption breaks when patients are censored because they were deteriorating — dropping out from toxicity, or withdrawing as their disease worsened. When dropout rates differ between arms, informative censoring should be named as a limitation. Look at the disposition table before you write the survival section; if one arm lost noticeably more patients, that is your limitation paragraph.
Reading a Kaplan–Meier curve
| Feature | What it tells you |
|---|---|
| Each step down | An event occurred. Step height grows as fewer patients remain at risk. |
| Tick marks | Censored patients. Heavy early ticks mean a lot of early dropout — investigate why. |
| Where the curve crosses 0.5 | The median. If it never crosses, the median is not reached. |
| Numbers at risk | The most important row on the figure. When it falls into single figures, the tail of the curve is unreliable. |
| Curves that cross | Proportional hazards is violated. A single hazard ratio may be misleading. |
| Early separation then parallel | A one-off early benefit rather than a continuing one. |
| Late separation | Delayed effect, typical of immunotherapy. The log-rank test loses power here. |
Always check the numbers-at-risk row before describing the tail. If it reads 6 and 4, do not write about a plateau or a durable response rate. This is one of the most common overinterpretations in oncology communications.
The hazard ratio and its assumption
HR 0.68 means the rate of events in the treatment arm is 68% of the rate in the control arm at any given moment — a 32% reduction in the risk of the event.It is not a ratio of medians, not a proportion of patients who benefited, and not a percentage increase in survival time.
Signs of violation: curves that cross; curves that separate late (delayed effect); curves that converge after early separation.
What is done about it: report restricted mean survival time (RMST), which does not need the assumption; present milestone survival rates at fixed timepoints; or use a weighted log-rank test. Diagnostics include Schoenfeld residuals — you will see this named in SAPs.
If you are writing up a trial where the curves cross, a single hazard ratio in the abstract is not sufficient, and saying so is a genuinely senior contribution.
Drills
Median PFS: 9.4 months (95% CI 7.8–11.2) vs 5.6 months (95% CI 4.9–6.8)
HR 0.62 (95% CI 0.49–0.79); stratified log-rank p < 0.001
Median follow-up 22.4 months (IQR 18.1–26.9)
12-month PFS rate: 41% vs 19%
Median OS: not reached vs 24.1 months; HR 0.79 (95% CI 0.58–1.08); p = 0.14
Numbers at risk at 24 months: 18 vs 7
Schoenfeld residual test for PH: p = 0.61
Censoring: 34% treatment arm, 29% control arm
“At a median follow-up of 22.4 months (IQR 18.1–26.9), median progression-free survival was 9.4 months (95% CI 7.8–11.2) with the study regimen and 5.6 months (95% CI 4.9–6.8) with control, corresponding to a 38% reduction in the risk of progression or death (HR 0.62, 95% CI 0.49–0.79; stratified log-rank p < 0.001). The proportion free from progression at 12 months was 41% versus 19%. The proportional hazards assumption was supported by testing of Schoenfeld residuals (p = 0.61). Median overall survival was not reached in the study regimen arm and was 24.1 months in the control arm (HR 0.79, 95% CI 0.58–1.08; p = 0.14); overall survival data were immature at this analysis, with 18 and 7 patients respectively remaining at risk at 24 months.”
Seven things this paragraph does right:
1. Opens with median follow-up. Survival results are uninterpretable without it, and it belongs first.
2. HR described as a risk reduction, not as a ratio of medians or a percentage of patients.
3. Stratified log-rank named, matching the SAP.
4. Milestone rate given, which is more useful than the median alone when curves may not be proportional.
5. PH assumption addressed explicitly. Most writer drafts omit this even when the diagnostic is in the output.
6. Not reached used correctly, and immaturity stated as the reason rather than implied.
7. Numbers at risk quoted so the reader can judge the tail.
What to notice about the censoring figures: 34% versus 29% is a modest difference and probably does not need a limitation sentence. If it had been 45% versus 25%, informative censoring would belong in the Discussion. Knowing where that line sits comes with practice — but knowing to look at the numbers is the part you can adopt today.
Non-inferiority, confounding and IPW
Two designs where the usual logic inverts — non-inferiority trials, where a non-significant result is the goal, and observational studies, where the entire analysis exists to compensate for the absence of randomisation
Part one — non-inferiority
The margin must be prespecified and clinically justified, usually by preserving a defined fraction of the active comparator's established effect over placebo. A margin chosen after seeing the data is not a margin.
Non-inferiority is concluded when the confidence interval for the difference excludes the margin — not when p exceeds 0.05.
In a non-inferiority trial, failing to show a difference is not success either. Absence of evidence is not evidence of non-inferiority. A small, underpowered, sloppily conducted trial will fail to detect a difference and that is not a result — it is a lack of one.
Non-inferiority is established only when the interval is narrow enough to exclude the margin. Sloppiness therefore works in favour of a non-inferiority conclusion if you judge it by p values, which is exactly why regulators insist on interval-based decisions and on per-protocol analyses as co-primary.
In a non-inferiority trial that dilution pushes toward the desired conclusion. ITT is therefore anti-conservative, and regulators normally expect both ITT and per-protocol analyses to support non-inferiority. If only one does, that is a finding, not a footnote.
Part two — confounding in observational studies
Any raw comparison therefore mixes the effect of the drug with the effect of the reasons it was chosen. In a randomised trial this cannot happen — assignment is by chance and unrelated to prognosis. In real-world data it is the default state, and every method below exists to compensate for it.
| Method | How it works | Limitation |
|---|---|---|
| Multivariable regression | Include confounders as covariates in the outcome model | Assumes the model form is right; strains when there are many covariates and few events. |
| Propensity score matching | Estimate each patient's probability of receiving treatment given their covariates; match treated to untreated with similar scores | Discards unmatched patients, so the analysed population may no longer resemble the target population. |
| Propensity score stratification | Group patients into strata of similar score and compare within strata | Residual imbalance within strata. |
| IPW inverse probability of treatment weighting | Weight each patient by the inverse of their probability of receiving the treatment they actually got, creating a pseudo-population balanced on measured covariates | Patients with extreme scores get very large weights, destabilising the estimate. Usually handled by trimming or stabilised weights. |
| Instrumental variables | Exploit a factor that affects treatment but not outcome directly | Valid instruments are rare and the assumptions are untestable. |
Required limitation wording: “Although IPW balanced measured baseline characteristics, residual confounding by unmeasured factors cannot be excluded.”
This is also the second half of the interview question. Candidates who explain the method but omit this are marked down, because the omission suggests they learned the technique without understanding what it is for.
Unlike a p value, the SMD does not depend on sample size, which is why it is preferred here. If a paper reports p values to demonstrate balance after matching, that is a weakness worth noting.
Drills
Analysis: propensity score estimated by logistic regression including age, sex, ECOG, stage, histology, prior lines, comorbidity index and year of treatment. Stabilised IPW applied; weights trimmed at the 1st and 99th percentiles. Balance assessed by standardised mean differences (all <0.10 after weighting). Weighted Cox model for the hazard ratio.
Result: HR 0.81 (95% CI 0.68–0.96).
Not captured in the database: performance status trajectory, smoking history, patient preference, biomarker status.
“Propensity scores for receipt of regimen A were estimated using logistic regression including age, sex, ECOG performance status, disease stage, histology, number of prior lines of therapy, comorbidity index and year of treatment initiation. Stabilised inverse probability of treatment weights were derived from these scores and trimmed at the 1st and 99th percentiles to limit the influence of extreme weights. Covariate balance was assessed using standardised mean differences, with a value below 0.10 considered acceptable; all covariates met this criterion after weighting. Overall survival was compared using a weighted Cox proportional hazards model.”
Limitations:
“This analysis has several limitations inherent to its retrospective, database design. Although inverse probability weighting achieved balance across all measured baseline covariates, residual confounding by unmeasured factors cannot be excluded. In particular, performance status trajectory, smoking history, patient preference and biomarker status were not captured in the database, and each may plausibly have influenced both treatment selection and survival. The findings should therefore be regarded as hypothesis-generating and interpreted as an association rather than a causal effect.”
Six elements a reviewer checks for:
1. The covariates in the propensity model are listed, not summarised as “baseline characteristics”.
2. Stabilised weights and trimming are both named, with the trimming thresholds.
3. Balance is demonstrated by SMD with a stated threshold — not by p values.
4. The outcome model is named as weighted.
5. The unmeasured confounders are named specifically. A generic sentence about residual confounding is worth far less than naming the four variables that are actually absent.
6. The conclusion is framed as association, and the study is labelled hypothesis-generating.
The interview answer, in one sentence: IPW creates a pseudo-population in which measured confounders are balanced, so the comparison approximates what randomisation would have achieved on those variables — but it is powerless against anything the database did not record, which is why the limitation paragraph is not boilerplate.
Subgroups, forest plots and interaction
The most over-interpreted figure in medicine — how to read one properly, why the interaction p value matters more than any individual row, and what you are allowed to write
Reading a forest plot
| Element | What it tells you, and what it does not |
|---|---|
| Square | The point estimate for that subgroup. Its size usually reflects the number of patients or events — a small square is a warning. |
| Horizontal line | The confidence interval. Width is the first thing to look at, before position. |
| Vertical line at 1 | No effect. Whether a subgroup interval crosses it is not the main question. |
| Diamond | The overall estimate. This is the reliable number on the figure. |
| Interaction p value | Whether the effect genuinely differs between subgroups. This is the only test that matters, and it is usually printed small at the right. |
| Number of subgroups | The multiplicity denominator. Fifteen subgroups at α = 0.05 means roughly a 54% chance of at least one spurious result. |
Comparing whether one subgroup is significant and another is not is not a valid way to claim a difference between them. A subgroup with 34 patients will be non-significant almost regardless of the true effect, purely because it is small.
The interaction test asks the right question directly. Subgroup analyses are typically very underpowered for interaction — a trial powered for an overall effect has little power to detect a difference in that effect — so a non-significant interaction p value is the expected result and does not establish uniformity either.
2. Ignoring multiplicity. Fifteen subgroups means several will look extreme by chance. The most extreme row on a forest plot is, by construction, the one most likely to be a chance finding.
3. Ignoring width. HR 0.41 in 34 patients with an interval from 0.16 to 1.07 is not a strong effect. It is an unstable estimate that happens to have landed low.
1. Was it prespecified in the SAP, or found afterwards?
2. Was it one of few subgroups, or one of many?
3. Is the interaction test significant?
4. Is the direction consistent with the overall effect, or a reversal? Reversals are far less credible than differences in magnitude.
5. Is there a biological rationale that existed before the data?
6. Has it replicated in another trial?
A finding that satisfies one or two of these is hypothesis-generating. A finding that satisfies all six may be real — and that combination is rare.
Drills
Prespecified subgroups (n = 6):
Age <65 (n = 210): HR 0.68 (0.51–0.91)
Age ≥65 (n = 190): HR 0.77 (0.57–1.04) — interaction p = 0.58
PD-L1 <1% (n = 148): HR 0.94 (0.66–1.34)
PD-L1 ≥1% (n = 252): HR 0.58 (0.44–0.77) — interaction p = 0.02
Region Asia (n = 96): HR 0.51 (0.29–0.90)
Region non-Asia (n = 304): HR 0.79 (0.63–0.99) — interaction p = 0.14
“Treatment effect was examined in six prespecified subgroups. The benefit was generally consistent by age (interaction p = 0.58) and by region (interaction p = 0.14). A significant interaction was observed by PD-L1 expression (interaction p = 0.02): the hazard ratio was 0.58 (95% CI 0.44–0.77) in patients with PD-L1 expression of at least 1% and 0.94 (95% CI 0.66–1.34) in those below 1%.”
Discussion:
“The observed interaction by PD-L1 expression is consistent with the established role of PD-L1 as a predictive biomarker for checkpoint inhibition and was prespecified; nevertheless, the trial was not powered for subgroup comparisons, and this finding requires prospective confirmation before it can inform patient selection.”
The four judgements behind this:
1. Age and region are reported as consistent, with their interaction p values, and no individual rows are highlighted. The Asia subgroup at HR 0.51 looks striking and has an interaction p of 0.14 — it is not reportable as a differential effect.
2. PD-L1 is treated differently, because the interaction test is significant at 0.02. This is the one row that earns its own sentence.
3. Even so, the Discussion hedges it: prespecified and biologically plausible, but underpowered and unconfirmed. Two of six credibility criteria are not met.
4. Six subgroups, not fifteen. That matters and is worth stating, because it bears directly on how much multiplicity concern applies.
The trap in this drill: the Asia subgroup. HR 0.51 is the most impressive number on the list, it is nominally significant, and a medical affairs colleague will want a slide about it. The interaction p of 0.14 is the answer, and being able to say that clearly — and kindly — is a large part of the job.
Reading tables, figures and listings
The TFL pack is where your Results section comes from. Knowing how to navigate it, what to cross-check, and which discrepancies to query is the practical core of the job
How a TFL pack is organised
Numbering follows ICH E3 section order, so the pack maps onto the CSR itself. Once you know the mapping you can find anything.
| Series | Content | What you use it for |
|---|---|---|
| 14.1.x | Disposition, demographics, baseline characteristics, protocol deviations | Analysis population denominators; baseline paragraph; the disposition figure |
| 14.2.x | Efficacy — primary, secondary, subgroups, sensitivity analyses | The efficacy results, in SAP order |
| 14.3.x | Safety — exposure, TEAEs by SOC and PT, deaths, SAEs, discontinuations, labs, vitals | The safety results |
| 16.2.x | Patient-level listings — individual data | Narratives, checking individual cases, resolving a discrepancy |
2. Open the SAP and find the estimand, the testing hierarchy and the analysis population definitions. One page, and it governs every claim you can make.
3. Locate the primary endpoint table and the primary figure. Read them together.
4. Build a one-page number sheet: every figure you will quote, with its table number beside it.
That number sheet is what makes your draft checkable — by you, by QC, and by the statistician — and it is what stops you re-hunting the same figure four times.
The cross-checks
Run these on every pack. They catch most of what QC would otherwise send back, and occasionally they catch a real error in the outputs.
| Check | What a mismatch means |
|---|---|
| Do the arm totals in each table match the disposition table? | Wrong analysis population applied, or a table from an earlier data cut. |
| Does the safety denominator equal the treated population, not the randomised one? | The Module 3.2 error. Very common in first drafts. |
| Do the medians in the table match the point where the KM curve crosses 0.5? | Figure and table may come from different runs or different cut-off dates. |
| Do subgroup n values sum to the overall n? | Missing biomarker or covariate data — which needs stating. |
| Does the number of events match between the primary table and the KM figure? | Different censoring rules applied. |
| Does the abstract number match the table you cited? | The most common late-stage error, usually caused by a data refresh after the abstract was drafted. |
| Do percentages recompute from their counts? | Transcription error, or a different denominator than the column header states. |
Raise it, in writing, with the table numbers and the two conflicting values. Nine times out of ten there is an explanation — a different data cut, a different population, a footnote you missed. The tenth time you have found a real error, and you will have found it before a regulator did.
Writers who query well become the writers statisticians want to work with. This is the single fastest route to being trusted with more senior work.
- Column Header Inversion: Models frequently swap the Experimental and Placebo columns when table spacing is tight, reporting the active arm's results under control.
- Denominator Dropping: A model may extract "Grade 3 AEs: 24 (12.0%)" from Table 14.3.1 without verifying whether the denominator was the Randomized Set ($N = 220$) or the Safety Set ($N = 200$).
- Decimal Shift & P-Value Rounding: Extracting $p = 0.048$ as $p < 0.001$ or dropping leading zeros (0.05 → .05).
Privacy first: TFLs and SAS output are confidential trial data. Use only tools your sponsor or employer has approved for that data, and never paste unpublished or patient-level results into a public AI tool. If you are unsure whether a tool is approved, ask before you upload.
Drills
Table 14.2.1 Primary PFS (ITT): n = 428. Median 9.4 vs 6.1 months. HR 0.68 (95% CI 0.55–0.84). Events 142/198. Footer: data cut-off 15 Jan 2026.
Figure 14.2.2 KM curve for PFS: curve crosses 0.5 at approximately 8.6 months in the treatment arm. Footer: data cut-off 30 Sep 2025.
Table 14.3.1 TEAEs: n = 428 (214/214). Any grade 391 (91.4%). Grade ≥3 168 (39.3%).
Table 14.2.6 Subgroups by PD-L1: <1% n = 148; ≥1% n = 252.
1. Table 14.3.1 — wrong safety denominator. The TEAE table uses n = 428 (214/214), which is the randomised population. Safety must use the treated population: 419 (211/208). Every percentage in that table is therefore understated. This is the most serious of the four and it changes published numbers.
2. Figure 14.2.2 versus Table 14.2.1 — different data cut-offs. The table is cut at 15 January 2026 and the figure at 30 September 2025. That fully explains the 9.4 versus 8.6 month discrepancy. Request a refreshed figure at the current cut. Do not publish a figure and a table from different cuts.
3. Table 14.2.1 — events denominator unclear. Events are given as 142/198, but neither number corresponds to an arm size of 214. Ask whether these are events per arm (142 and 198) rather than a fraction, and confirm the intended presentation.
4. Table 14.2.6 — subgroup n values sum to 400, not 428. Twenty-eight patients presumably had no evaluable PD-L1 result. Confirm this and obtain the wording for the biomarker-evaluable population, which must be stated in Methods and in the subgroup results.
What you have also established, without querying: the 396 patients with a post-baseline assessment is the likely mITT denominator for response endpoints. Check the SAP definition before using it.
Score yourself: query 1 is the one that matters most — it is a real error that would reach publication. If you found queries 2 and 4 but not 1, re-read Module 3.2. If you found all four, you are working at the level agencies hire for.
Capstone and exit assessment
A full output pack, a Results section to write, and twenty seeded statistical errors in a draft to catch — the task an agency assessment actually sets
Reading the rubric first turns this into a comprehension exercise and measures nothing.
Disposition: 402 randomised (201/201). 389 treated (196/193). 371 with ≥1 post-baseline scan.
PFS (ITT, n = 402): median 8.9 (95% CI 7.4–10.3) vs 5.2 (95% CI 4.4–6.1) months. HR 0.66 (95% CI 0.53–0.82); stratified log-rank p < 0.001. Schoenfeld PH test p = 0.44.
OS (ITT): median not reached vs 21.7 months. HR 0.84 (95% CI 0.62–1.14); p = 0.26. At risk at 24 months: 41 vs 22.
ORR (mITT, n = 371): 44% vs 29%; p = 0.003.
PRO change: −5.2 vs −1.8; p = 0.02. Published MCID for the scale = 8 points.
Safety (n = 389): grade ≥3 TEAE 147 (37.8%). Discontinuation for AE 31 (8.0%).
Subgroups (6 prespecified): region Asia n = 88, HR 0.47 (0.26–0.85); non-Asia n = 314, HR 0.72 (0.56–0.93); interaction p = 0.19.
Median follow-up: 19.8 months (IQR 16.2–24.1).
Overall survival showed no benefit (HR 0.84, p = 0.26); median OS was not reached in the treatment arm, indicating the data are missing for that arm. Objective response rate was significantly higher (44% vs 29%, p = 0.003), as was quality of life, which improved significantly (p = 0.02), demonstrating a clinically meaningful benefit to patients.
Grade 3 or higher adverse events occurred in 36.6% of the 402 randomised patients, and 31 patients discontinued.
In subgroup analysis the treatment was particularly effective in Asian patients (HR 0.47, p = 0.01), suggesting that ethnicity predicts response and that this population should be prioritised. A total of 402 patients were randomised and the mITT population of 371 was used for all efficacy analyses.”
Claim calibration (5)
1. proves — no single trial proves anything. Replace with demonstrated, which the randomised design does license.
2. definitely improves outcomes — definitely has no place in a scientific claim, and outcomes is vague. Name the endpoint.
3. highly significant — attaches magnitude to a p value. Give the effect size instead.
4. OS showed no benefit — HR 0.84 with an interval of 0.62–1.14 is an immature, imprecise estimate, not a demonstration of no benefit. Write overall survival data were immature; the confidence interval does not exclude a benefit.
5. demonstrating a clinically meaningful benefit for the PRO — the change is −5.2 versus −1.8, a difference of 3.4 points against a published MCID of 8. It is statistically significant and below the threshold of clinical importance. This must be stated.
Statistical interpretation (6)
6. survival was 34% longer — a hazard ratio is not a percentage increase in survival time. Write a 34% reduction in the risk of progression or death.
7. median OS not reached, indicating the data are missing — the reverse. Fewer than half the patients had died; report as not reached and note immaturity.
8. ORR described as significantly higher — the hierarchy broke at OS (p = 0.26), so ORR was not formally tested. Report as nominal p = 0.003, descriptive.
9. PRO described as significant — same hierarchy problem, two steps further down. Nominal only.
10. subgroup: particularly effective in Asian patients — the interaction p is 0.19. There is no evidence the effect differs by region.
11. ethnicity predicts response / should be prioritised — a treatment recommendation from a non-significant interaction in an 88-patient subgroup. This is the most serious finding in the draft.
Populations and denominators (3)
12. 36.6% of the 402 randomised patients — safety uses the treated population, n = 389. And 147/389 is 37.8%, not 36.6%; the draft has computed against the wrong denominator.
13. 31 patients discontinued — no denominator and no percentage. Write 31/389 (8.0%).
14. mITT used for all efficacy analyses — false. PFS and OS used ITT (n = 402); only ORR used mITT (n = 371).
Reporting conventions (6)
15. 5 months → 5.2 months, matching the decimal precision of 8.9.
16. .66 → 0.66, leading zero.
17. CI → 95% CI.
18. Hyphen in 0.53-0.82 → en dash.
19. p=0.000 → p < 0.001, italic, with spaces.
20. Median follow-up omitted entirely — survival results are uninterpretable without it. Add at a median follow-up of 19.8 months (IQR 16.2–24.1).
Model corrected version
“At a median follow-up of 19.8 months (IQR 16.2–24.1), the study regimen demonstrated a benefit in progression-free survival: median PFS was 8.9 months (95% CI 7.4–10.3) versus 5.2 months (95% CI 4.4–6.1), corresponding to a 34% reduction in the risk of progression or death (HR 0.66, 95% CI 0.53–0.82; stratified log-rank p < 0.001). The proportional hazards assumption was supported (Schoenfeld p = 0.44).
Overall survival data were immature: median OS was not reached with the study regimen and was 21.7 months with placebo (HR 0.84, 95% CI 0.62–1.14; p = 0.26), with 41 and 22 patients respectively at risk at 24 months. As overall survival did not meet the prespecified threshold, formal testing stopped at this endpoint; subsequent endpoints are reported descriptively. Objective response rate was 44% versus 29% (nominal p = 0.003) in the modified intention-to-treat population (n = 371). The mean change in patient-reported outcome score was −5.2 versus −1.8 (nominal p = 0.02); the between-group difference of 3.4 points is below the published minimal clinically important difference of 8 points.
In the safety population (n = 389), grade 3 or higher treatment-emergent adverse events occurred in 147 patients (37.8%) and 31 patients (8.0%) discontinued because of an adverse event.
Treatment effect was consistent across the six prespecified subgroups, with no significant interaction by region (interaction p = 0.19).”
Scoring
16–20 — pass. You can be trusted to review statistical text unsupervised, and you would have caught findings 5, 11 and 12 before they reached a regulator.
11–15 — close. Note which of the four categories your misses fell in and re-do that week's drills.
Under 11 — repeat the sentence-level drills in Weeks 2 and 3 before retrying. Do not retake this immediately.
The three that matter most: finding 5 (statistical significance below the MCID), finding 11 (a treatment recommendation from a non-significant interaction), and finding 12 (the wrong safety denominator). Each of those reaches patients or regulators if nobody catches it. The reporting conventions matter for QC; those three matter for people.
Retake the diagnostic
Return to Module 1.1 and take the 24-item diagnostic again. Your first score was stored as the baseline; the difference is the only honest measure of what these four weeks changed.
Expect movement of one band. Band C to Band B is a normal and substantial four-week result.
Then pair this with the writing. The Scientific English course fixes how you write sentences; this course fixes what you are allowed to claim in them. Module 3.2 there and Modules 1.4 and 4.2 here are the same skill approached from two directions.
HEOR preview: from clinical to economic evidence
The statistical skills you have built read clinical data — but payers, HTA bodies, and formulary committees read economic data too. This bridge module shows you where the two meet.
From efficacy to value
A positive Phase III trial proves a treatment works. But a payer's question is different: how much additional health does it buy, and at what cost? This is the domain of Health Economics and Outcomes Research (HEOR).
HEOR writers take the clinical evidence you now understand — hazard ratios, response rates, safety profiles, quality-of-life scores — and translate it into economic models that inform pricing, reimbursement, and formulary decisions. If you have completed this statistics course, you already understand the inputs. This module shows you what happens to them next.
ICER (Incremental Cost-Effectiveness Ratio): the additional cost of the new treatment divided by the additional QALYs it produces versus the comparator. An ICER of £30,000/QALY means each extra year of perfect health costs £30,000.
NNT in economic context: you learned NNT as "how many patients must be treated for one to benefit." In HEOR, NNT feeds directly into budget impact: if NNT = 8 and the treatment costs £40,000 per patient per year, the cost per responder is £320,000.
How clinical statistics feed economic models
Every number you have learned to check in this course has a second life in a cost-effectiveness model:
Hazard ratios → applied to baseline survival curves to estimate the treatment arm's long-term trajectory. If the proportional hazards assumption fails (you tested this in Module 3.4), the model must use a different approach.
Utility values from PRO data → mapped to QALY weights. The EQ-5D is the instrument most HTA bodies accept. The PRO change of −5.2 versus −1.8 from the capstone? An economist would ask whether that maps to a utility difference, and whether that difference exceeds the minimum important difference — exactly the judgement you made in finding 5 of the capstone.
Safety rates → costed as adverse-event management. Grade ≥3 events carry hospital costs; discontinuation rates affect duration of treatment and therefore total drug cost.
Willingness-to-pay thresholds
An ICER is meaningless without a threshold. Different countries set different ceilings for what they will pay per QALY gained:
WHO benchmark: historically 1–3× GDP per capita, though this rule of thumb is increasingly debated.
US: no single threshold; ICER (the Institute) uses $50,000–$200,000 per QALY as a range. Payers negotiate individually.
Practical rule: if the ICER exceeds the threshold, the treatment is "not cost-effective" at its current price — which usually means the manufacturer must lower the price, offer a discount, or propose a managed-access scheme.
Budget impact versus cost-effectiveness
Cost-effectiveness asks "is it worth it per patient?" Budget impact asks "can we afford it across the whole eligible population?" Both matter, and they can point in opposite directions. A treatment can be cost-effective (good ICER) but have enormous budget impact because the eligible population is large.
As a medical writer, you may never build the model — but you will write the value dossier, the AMCP dossier, or the NICE submission that presents its results. Understanding what the numbers mean, where they come from, and how they connect to the clinical evidence is what separates a writer who transcribes from one who catches errors.
Incremental cost: $124,000 per patient over 5 years
PFS HR: 0.58 (95% CI 0.42–0.80)
OS HR: 0.79 (95% CI 0.58–1.08)
Mean utility on treatment: 0.68
Incremental life-years gained (modelled): 1.4 years
Incremental QALYs (modelled): 0.95
Calculate: the ICER. Then state which clinical input carries the most uncertainty and why that matters for the economic conclusion.
The most uncertain input is the OS hazard ratio — its confidence interval crosses 1.0 (0.58–1.08), meaning the survival benefit is not statistically established. The modelled 1.4 incremental life-years depend heavily on extrapolation beyond the trial, and the choice of survival curve (Weibull vs. log-normal vs. generalised gamma) will swing the ICER by tens of thousands of dollars.
This is exactly the kind of uncertainty an HTA committee will probe, and exactly the kind a medical writer must flag rather than gloss over.
Annual budget impact: 6,000 × €48,000 = €288 million.
This is a treatment that works (NNT of 12 is reasonable in oncology) but has a very large budget impact. The payer will negotiate a discount, a cap, or a performance-based scheme. As a writer, you will see these numbers in AMCP dossiers and NICE evidence submissions.
The sensitivity analysis is also misleading: saying the ICER "remained below $100,000" in 92% of simulations is a cherry-picked threshold. The relevant question is what percentage of simulations fell below the applicable willingness-to-pay threshold — and that threshold must be stated.
This is the economic equivalent of finding 3 from the capstone: highly significant attaching magnitude to a p value. Same error, different currency.
Your pathway forward
This preview scratched the surface. The full HEOR & Market Access Writing pathway in IMRAD Academy's professional tier covers:
Value dossiers and HTA submissions: AMCP Format, NICE evidence submissions, G-BA benefit assessments — the documents that get drugs onto formularies.
Systematic literature reviews for HEOR: how SLRs in the economic context differ from clinical SLRs, and why network meta-analyses (NMAs) feed economic models.
Budget impact modelling: the payer's spreadsheet — how it differs from cost-effectiveness analysis and when each is needed.
Real-world evidence in HEOR: claims data, registry data, and how they supplement trial-based models.