What a Prediction Table Is Predicting
A competing-risk prediction table compresses several decisions into each entry: which population is being described, which event is counted, and by what time. A number such as 0.18 is not interpretable on its own. It could be the predicted probability of one event by a particular horizon for a person with specified covariates, or an average risk for a defined population. Those are different prediction targets, even when the numerical values happen to be similar.
The central quantity for event type \(k\) is its cumulative incidence by time \(t\): the probability that event \(k\) is the first event to occur by \(t\). A competing event is not simply an observation that disappears from the target. Its occurrence prevents the event of interest from being the first event later, and therefore affects the absolute risk being predicted.
The phrase “by time \(t\)” includes an event occurring at \(t\). In practice, tables may use horizons such as 1 year or 5 years; the time unit and the precise horizon must be read from the heading or footnote. A cause-specific risk of 0.18 at 3 years means a predicted probability of 18% of experiencing that cause as the first event within 3 years, for the stated target population. It does not mean an 18% instantaneous event rate or an 18% risk per year.
Read the Target Before the Number
A table may report predictions for specified covariate profiles or for a population. A profile-specific entry, \(F_k(t\mid x)\), is conditional: it describes individuals represented by that particular covariate profile under the fitted prediction model. A population-standardized entry averages predictions over the covariate distribution of a named target population. These quantities answer different questions and need not agree.
For a target population with covariate profiles \(x_1,\ldots,x_n\) and specified weights \(w_i\) summing to 1, a standardized prediction is the weighted average of profile-specific predictions:
The weights define the population to which the result applies. Equal weights describe the empirical cohort when every person is included once; other weights may represent a different target distribution. Thus, “standardized risk” is incomplete unless the table or its documentation identifies the population being standardized to. It is not automatically the risk for every person, nor does it necessarily describe the sample used to fit the model.
Worked Example: Interpreting a Profile-Specific Row
Suppose a hypothetical table gives the following model predictions for a patient profile defined as age 70, with a specified baseline condition. The outcomes are mutually exclusive first events.
| Horizon | Cause A risk | Cause B risk | Event-free probability |
|---|---|---|---|
| 2 years | 0.12 | 0.08 | 0.80 |
| 5 years | 0.25 | 0.15 | 0.60 |
At 2 years, the predicted probability of Cause A being the first event is 0.12, or 12%, for individuals with this profile. The corresponding probability for Cause B is 8%, and the probability of having experienced neither event is 80%. These entries concern a covariate profile, not necessarily a population average.
At 5 years, the table predicts a 25% probability of Cause A as the first event and a 15% probability of Cause B as the first event. The event-free probability is 60%. Each entry is tied to its own horizon; the 5-year risks include events occurring by 2 years as well as those occurring later, not just events during years 2 through 5.
The rows pass the basic coherence check: at 2 years, \(0.12+0.08+0.80=1.00\); at 5 years, \(0.25+0.15+0.60=1.00\). This check supports the interpretation that the entries partition outcomes by the first event status at each horizon.
Why the Probabilities Fit Together
At a fixed horizon, an individual has experienced exactly one of the following: cause 1 first, cause 2 first, continuing through cause \(K\) first, or no event yet. These categories are mutually exclusive and collectively exhaustive, assuming the listed causes include every event type being counted. Therefore, for a given profile and horizon:
This identity is a useful interpretation aid. The event-free probability is not the complement of one cause-specific risk unless there is only one possible event type. Instead, it is the complement of the risks for all listed event types combined:
The identity also explains why the competing events matter for absolute risk. A person who experiences Cause B first is not event-free at a later horizon and cannot subsequently experience Cause A as the first event. A table’s cause-A risk is therefore not interpreted as though Cause B could be removed while leaving all else unchanged.
Worked Example: Reading a Standardized Population Prediction
Consider a hypothetical target cohort of 100 people, split into two equally weighted profiles. At 3 years, a prediction model gives Cause A risks of 0.10 for Profile 1 and 0.30 for Profile 2. The cohort-standardized risk is the average across the target cohort:
The standardized prediction is 0.20, or 20% by 3 years, for the specified 50:50 target cohort. It is not the risk for either profile: the profile-specific predictions are 10% and 30%. If the target population instead had 80% Profile 1 and 20% Profile 2, the appropriate average would be:
That target population would have a standardized predicted risk of 14% by 3 years. The difference between 20% and 14% comes from the target populations’ different profile weights, not a change in the two profile-specific predictions. For a full competing-risk table, the same averaging is applied to each cause-specific risk and to event-free probability; the resulting entries retain the probability identity when the profile-level predictions satisfy it.
Intervals, Comparisons, and Checks
A prediction table may give an uncertainty interval alongside each estimated risk. For example, a 95% confidence interval of 0.14 to 0.24 around an estimated 3-year risk of 0.19 indicates uncertainty in the estimated risk under the stated statistical procedure and assumptions. In repeated applications of that procedure, 95% of intervals constructed this way would cover the fixed target quantity. It is not correct to say there is a 95% probability that the fixed risk lies in this particular interval.
Check whether the interval is described as pointwise or simultaneous. A pointwise interval addresses one specified estimate, such as one cause at one horizon. A collection of pointwise 95% intervals does not generally provide 95% coverage for the entire set of causes and horizons together. Also check whether the uncertainty includes model fitting, baseline-risk estimation, and any standardization step; the table’s methods or footnote should clarify what was accounted for.
Intervals for separate cause-specific risks may not add with an event-free interval to exactly 1. The probability identity applies to the point predictions, not necessarily to the endpoints of separately calculated marginal intervals. A mismatch among interval endpoints alone is not evidence that the point estimates violate probability coherence.
Worked Example: Interpreting Uncertainty Without Overclaiming
Suppose a hypothetical table reports a standardized 4-year Cause B risk of 0.16, with a 95% confidence interval from 0.11 to 0.22, for a defined clinic population. The point estimate is a predicted 16% probability of Cause B as the first event by 4 years in that population. The interval describes sampling and estimation uncertainty for that target risk, under the procedure’s assumptions; it does not mean that 95% of people have individual risks between 11% and 22%.
A second population has an estimated 4-year risk of 0.20 with interval 0.14 to 0.27. The intervals overlap, but overlap alone is not a formal test of equality. To make a statistical comparison, one needs an uncertainty calculation for the difference, including the dependence between the estimates if they come from the same data. The table supports a descriptive comparison of 16% versus 20%; it does not by itself establish that the populations’ risks differ statistically.
Common checks help detect misread or potentially problematic tables. First, verify that units and horizons match: 0.12 at 2 years is not comparable to 0.12 at 5 years without specifying the different horizons. Second, for a single profile or consistently standardized target, each cause-specific cumulative incidence should be nondecreasing across increasing horizons, while event-free probability should be nonincreasing. Third, at each horizon, the point predictions should be between 0 and 1 and should satisfy the probability identity up to rounding. Fourth, confirm that the target population and event definitions are stated; otherwise, a precise interpretation may not be possible. Limited follow-up support, model uncertainty, or an unclear target can make a numerically tidy table misleading.
Different table types answer different questions. A profile-specific prediction answers what the model predicts for that covariate profile. A standardized prediction answers what the model predicts on average for a specified covariate distribution. A table of cause-specific hazards describes instantaneous event rates among those still event-free, rather than the probability of an event by a horizon. A single-cause net-risk quantity also has a different interpretation from a competing-risk cumulative incidence because it does not represent the observed-world probability of that cause occurring first in the presence of competing events. Read the column label and estimand, not just the word “risk.”
For instance, with a 2-year Cause A risk of 0.12 and a 5-year risk of 0.25, the difference is \(0.25-0.12=0.13\), or 13 percentage points of the original target population experiencing Cause A first between those horizons. Among people still event-free at 2 years, the conditional probability of Cause A during the next 3 years would instead divide that increment by the 2-year event-free probability, provided the same target and model apply. Using the example’s \(S(2)=0.80\), this is \(0.13/0.80=0.1625\), or 16.25%. The denominator is essential because the conditional target is the subset event-free at 2 years.
Check Your Understanding
Answer each question by identifying the target and the quantity being described. Solutions follow each prompt.
- A table reports a 6-year Cause C risk of 0.09 for a specified covariate profile. What does 0.09 mean? Solution: For individuals represented by that profile, the model predicts a 9% probability that Cause C is the first event by 6 years.
- At one horizon, two cause-specific risks are 0.17 and 0.08. What is the corresponding event-free probability if these are the only event types? Solution: \(1-0.17-0.08=0.75\), so the predicted probability of no event by that horizon is 75%.
- Two profiles have risks of 0.12 and 0.32. What is their standardized risk when the target population weights are 25% and 75%, respectively? Solution: \(0.25(0.12)+0.75(0.32)=0.03+0.24=0.27\), or 27% for that weighted target population.
- A table reports a 2-year risk of 0.10 and a 5-year risk of 0.24. Is the 5-year risk the probability of the event during years 2 through 5? Solution: No. It is the probability of the event by 5 years. The increase in cumulative incidence over years 2 to 5 is \(0.24-0.10=0.14\), or 14 percentage points of the original target population.
- What is the correct interpretation of a reported 95% confidence interval of 0.10 to 0.20 for a fixed-horizon risk estimate? Solution: Under the procedure’s assumptions, repeated intervals constructed in this manner would cover the fixed target risk 95% of the time. The interval is not a statement that the parameter has a 95% probability of lying within these particular endpoints.