Why Phenotype Adjudication Matters
A pharmacogenomic association is only as clear as the outcome being compared. “Drug toxicity” may refer to a laboratory abnormality, a symptom documented in a note, a clinician’s diagnosis, or a serious event that prompted treatment discontinuation. These are not interchangeable outcomes. If researchers combine them without rules, or count an event that occurred before the patient took the drug, the resulting association may be difficult to interpret even when the statistical calculation is correct.
Phenotype adjudication makes the outcome definition operational: reviewers apply prespecified criteria to available clinical records, while exposure confirmation establishes that the person received the drug during the period in which the outcome could occur. The aim is not to make every record certain. It is to apply transparent rules consistently, record uncertainty, and assess whether classification errors could change the estimated association.
Specify the Phenotype Before Reviewing Records
A useful phenotype protocol states what qualifies as an event and when it must occur. For a hypothetical drug-associated liver injury outcome, the protocol might specify the laboratory thresholds, the required timing after treatment initiation, how alternative documented causes are handled, and whether an event is definite, probable, possible, or absent. The exact criteria should follow the clinical question and available measurements; a label such as “liver toxicity” alone is not a reproducible rule.
Also specify how the analysis treats borderline and incomplete records. For example, a primary binary outcome might count definite and probable cases as events, classify clearly documented non-cases as no event, and leave records with insufficient evidence indeterminate. Indeterminate records should not silently be treated as unaffected. Their number and characteristics should be reported, with a sensitivity analysis when a plausible alternative classification could affect the result.
Reviewers should use the same evidence window and case rules for every participant. When feasible, they should be blinded to genotype and to the association result being evaluated. Blinding reduces the risk that knowledge of a genotype or hypothesis influences how ambiguous evidence is interpreted. It does not correct missing or inaccurate records, and it does not guarantee that reviewers will agree.
Specify the clinical features, measurements, timing, severity, exclusions, and handling of uncertain evidence before reviewing records.
Check whether treatment began, whether it was received during the relevant window, and whether the event occurred after exposure began.
Use trained reviewers, a common abstraction form, and blinding to genotype when feasible; retain the evidence supporting each decision.
Apply a prespecified consensus or third-reviewer process, then record the final classification and remaining uncertainty.
Report reviewer agreement and, where possible, compare classifications with an independent validation standard.
Agreement Is Not the Same as Validity
Two reviewers can agree because the records are clear, because they share the same interpretation, or because most records are non-cases. Agreement is useful evidence about reproducibility, but it does not establish that the resulting phenotype is clinically correct. If a validation standard is available, sensitivity is the proportion of true cases classified as cases, and specificity is the proportion of true non-cases classified as non-cases.
For a simple summary of two reviewers’ agreement beyond chance, Cohen’s kappa is \( \kappa=(P_o-P_e)/(1-P_e) \), where \(P_o\) is the observed proportion of matching classifications and \(P_e\) is the proportion expected to match from the reviewers’ marginal classification proportions. Kappa depends on the prevalence of classifications and the reviewers’ marginal rates, so it should be reported with the underlying counts rather than treated as a universal quality threshold.
Worked Example: Reviewing Agreement for a Hypothetical Toxicity Outcome
Two blinded reviewers independently assess 40 hypothetical records for a prespecified drug-toxicity phenotype. Reviewer A and reviewer B both classify 12 records as cases and 20 as non-cases. They disagree on the other 8 records: A calls 5 cases that B calls non-cases, and B calls 3 cases that A calls non-cases. A third reviewer applies the written rules to these 8 records and classifies 3 as cases and 5 as non-cases.
Observed agreement. The reviewers agree on \(12+20=32\) of 40 records, so \(P_o=32/40=0.800\).
Expected agreement from the margins. A classifies \(12+5=17\) records as cases and 23 as non-cases. B classifies \(12+3=15\) as cases and 25 as non-cases. Thus:
Kappa. Substituting these values gives:
After the third-reviewer process, 15 records meet the case definition: the 12 agreed cases plus 3 disagreements resolved as cases. This resolution supplies a final classification under the stated process; it does not prove that all 15 are true cases. Kappa describes reviewer agreement beyond the chance agreement calculated from these margins, not accuracy against an independent clinical standard.
Confirm Drug Exposure in the Risk Window
A prescription order establishes that treatment was intended, not necessarily that treatment was dispensed, administered, or taken. The appropriate evidence depends on the setting. An inpatient study may have medication-administration records; an outpatient study may use dispensing data, patient reports, or other documentation. Each source has limitations. A dispensing record does not prove ingestion, while an order alone may include people who never started treatment.
Define the exposure window in relation to the outcome window. If the endpoint is a toxicity that can arise only after treatment starts, an event documented before the first confirmed dose should not be counted as an incident on-treatment toxicity. Conversely, a gap in records should not automatically be interpreted as proof that exposure stopped. The protocol should state how uncertain starts, interruptions, and timing are handled. The eligible denominator must match the estimand: for example, risk among confirmed drug initiators is different from risk among everyone for whom a prescription was written.
Worked Example: How Unconfirmed Prescriptions Change the Risk Estimate
Suppose a hypothetical record review begins with 100 people with genotype group A and 200 with genotype group B, all of whom have a prescription order for the same drug. Administration records confirm that 90 in group A and 120 in group B received the drug during the defined window. Among these confirmed recipients, 18 in group A and 12 in group B meet the adjudicated toxicity definition. Assume, for this example, that no unconfirmed person is known to have received the drug and that the outcome of interest is risk among confirmed recipients.
If everyone with an order is incorrectly used as the denominator, the apparent risks are \(18/100=0.180\) in group A and \(12/200=0.060\) in group B. The apparent risk ratio is:
Among confirmed recipients, the risks are \(18/90=0.200\) and \(12/120=0.100\). The corresponding risk ratio is:
Under the stated target, \(RR_{\text{confirmed}}=2.00\) is the relevant crude comparison: the observed toxicity risk among confirmed recipients in group A is twice that in group B. Using the order-based denominators gives a different estimate because the proportions with confirmed exposure differ between groups. This calculation does not establish a causal genetic effect: confounding, selection, and other design issues still matter. It shows why an exposure definition and denominator should be aligned with the scientific question.
How Outcome Misclassification Changes an Association
Let \(Y\) denote the true binary toxicity outcome and \(Y^*\) the recorded or adjudicated binary outcome. Within genotype group \(g\), define sensitivity \(Se=P(Y^*=1\mid Y=1,g)\) and specificity \(Sp=P(Y^*=0\mid Y=0,g)\). If sensitivity and specificity are the same across genotype groups, classification errors are independent of genotype conditional on the true outcome, and the outcome is binary, then the observed case proportion \(q_g=P(Y^*=1\mid g)\) satisfies:
where \(p_g=P(Y=1\mid g)\) is the true risk in that group. The first term counts true cases correctly classified as cases; the second counts true non-cases incorrectly classified as cases. Rearranging gives:
Subtract the expression for genotype group 0 from the expression for group 1. When the same \(Se\) and \(Sp\) apply in both groups, the constant term cancels:
The quantity \(Se+Sp-1\) is Youden’s index. If classification is better than chance, so \(Se+Sp>1\), this model scales the observed risk difference toward zero. This result is specific to the stated assumptions and the risk-difference scale. It does not justify saying that every kind of nondifferential misclassification always attenuates every effect measure. For example, risk ratios and odds ratios need not be changed by the same factor, and genotype-dependent sensitivity or specificity can distort comparisons in other directions.
If \(Se\) and \(Sp\) are known or estimated in a suitable validation sample and \(Se+Sp>1\), the equation can also be rearranged to estimate the true risk:
This is a correction of point estimates under a measurement model, not a substitute for validation. It can yield values outside the interval from 0 to 1 when the observed data and assumed error rates are incompatible, and uncertainty in the validation estimates should be carried into uncertainty intervals for corrected associations. The validation sample must provide relevant estimates of classification performance for the population and review process being studied.
Worked Example: Correcting Genotype-Stratified Risks for Misclassification
In a hypothetical validation study, reviewers’ binary toxicity classifications have estimated sensitivity \(Se=0.80\) and specificity \(Sp=0.95\), assumed to apply equally in two genotype groups. In an analysis of 200 confirmed drug recipients in each group, the recorded outcome counts are 55 cases in group 1 and 25 in group 0. Assume the validation estimates are applicable to this analysis and that outcome errors are independent of genotype conditional on the true outcome.
The observed risks are \(q_1=55/200=0.275\) and \(q_0=25/200=0.125\). The observed risk difference is \(0.275-0.125=0.150\), and the observed risk ratio is \(0.275/0.125=2.20\).
For the correction, \(Se+Sp-1=0.80+0.95-1=0.75\). The estimated corrected risk in group 1 is:
The estimated corrected risk in group 0 is:
Thus the corrected risk difference is \(0.300-0.100=0.200\), and the corrected risk ratio is \(0.300/0.100=3.00\). Under the assumed error model, the observed data understate this risk difference: the observed difference of 0.150 equals \(0.75\) times the corrected difference of 0.200. The corrected figures are estimates conditional on the assumed sensitivity and specificity; they are not known true risks. A complete analysis would quantify sampling uncertainty, including uncertainty in the validation estimates.
Common Pitfalls and Reporting Priorities
- Treating the prescription as exposure. The wrong reasoning is that an order proves the patient took the drug. The correction is to define the exposure evidence required and use a denominator aligned with the target population.
- Using an outcome label without operational criteria. The wrong reasoning is that a diagnosis code or note label means the same thing in every record. The correction is to prespecify measurable or documented criteria and a rule for uncertain cases.
- Equating agreement with accuracy. The wrong reasoning is that high reviewer agreement establishes a valid phenotype. The correction is to report agreement separately from validation against an independent standard, when available.
- Assuming misclassification always biases toward no association. The wrong reasoning ignores the effect measure and the error process. The correction is to state the assumptions and scale, as in the risk-difference derivation, and consider differential errors explicitly.
- Letting genotype knowledge influence chart review. The wrong reasoning is that a plausible genotype makes ambiguous symptoms more likely to be a case. The correction is to blind reviewers to genotype when feasible and apply identical criteria across groups.
A clear report describes the case definition, timing rules, exposure evidence, reviewer training and blinding, disagreement resolution, and number of indeterminate records. If validation data exist, report how they were obtained and whether classification performance could differ across genotype groups or clinical settings. These details help readers judge whether the estimated association concerns the intended toxicity phenotype among the intended exposed population, rather than an artefact of inconsistent charting or exposure assignment.
Check Your Understanding
Use the definitions and assumptions in this tutorial to answer the following questions.
- Why should a study distinguish an order for a drug from confirmed treatment when defining risk among drug recipients?
- Two reviewers agree on 90% of records. What does this establish, and what does it not establish about phenotype validity?
- Under the binary outcome model, state the assumptions needed for \(q_1-q_0=(Se+Sp-1)(p_1-p_0)\).
- If sensitivity and specificity differ by genotype, why may the observed risk difference no longer be a simple scaled version of the true risk difference?
- When is it appropriate to classify an uncertain record as indeterminate rather than as a non-case?