Choosing Between kNN Imputation and Multiple Imputation for Prediction and Inference

introduction

Missing data handling should be aligned with the scientific goal of the analysis, the intended validation strategy, and the role of uncertainty in the final results. This section provides a decision framework to guide the choice between k-nearest neighbor (kNN) imputation and Multiple Imputation (MI).

---

Step 1: Clarify the Primary Goal of the Analysis

The first and most important question is:

Is the goal inference or prediction?

A. Inference-Focused Research

(Etiology, risk factors, hypothesis testing)

Goal:

• Estimate regression coefficients
• Obtain valid standard errors and confidence intervals
• Perform hypothesis testing

Recommended approach → Multiple Imputation (MI)

Reason:

• MI explicitly models uncertainty due to missing data
• Rubin’s rules provide valid variance estimates
• Designed for inferential statistics

B. Prediction-Focused Research

(Diagnostic or prognostic prediction models)

Goal:

• Predict outcomes for new individuals
• Evaluate discrimination (AUC) and calibration
• Perform internal validation (e.g., bootstrap)

Recommended approach → Bootstrap + kNN imputation

Reason:

• Prediction focuses on model performance, not coefficient inference
• Resampling already captures uncertainty
• Deterministic imputation improves stability during validation

---

Step 2: Decide How Uncertainty Should Be Represented

How MI Handles Uncertainty

• Adds stochastic variation during imputation
• Produces multiple datasets
• Pools results using Rubin’s rules
• Best suited for parameter uncertainty

How Bootstrap + kNN Handles Uncertainty

• kNN itself is deterministic
• Uncertainty comes from resampling the data
• Each bootstrap sample leads to:
  • Different observations
  • Different neighbors
  • Different imputations
• Best suited for prediction uncertainty

---

Step 3: Consider the Validation Strategy

If You Use Internal Validation With Bootstrap

Correct sequence:

Bootstrap → Imputation → Model fitting → Performance estimation

• Works naturally with single imputation methods (e.g., kNN)
• Avoids complex pooling rules
• Produces empirical performance distributions

Therefore:

If bootstrap validation is central → use bootstrap + kNN

If You Use Multiple Imputation

Correct sequence:

Imputation → Model fitting → Pool estimates (Rubin’s rules)

Important rule:

Do NOT bootstrap before MI

Why?

• MI already accounts for uncertainty
• Bootstrapping before MI double-counts variability
• Variance estimates become invalid

---

Step 4: Assess Practical and Modeling Considerations

When kNN Is Particularly Appropriate

• Prediction modeling
• Moderate to high missingness in predictors
• Complex or nonlinear predictor relationships
• Need for stable variable selection
• Desire for reproducible, deterministic preprocessing
• Bootstrap-based internal validation planned

When MI Is Particularly Appropriate

• Causal or explanatory modeling
• Moderate missingness under MAR
• Parametric models are well specified
• Focus on coefficient interpretation
• No resampling-based validation required

---

Summary Decision Table

---

Key Rules to Remember

• If inference is the goal → use MI
• If prediction + bootstrap validation is the goal → use bootstrap then kNN
• Never bootstrap before MI
• Never impute outcomes in prediction models
• The missing-data strategy must match the analysis goal, not researcher preference

One-Line Summary

“Multiple imputation is preferred for inferential analyses, whereas deterministic imputation combined with bootstrap resampling is often more appropriate for prediction modeling with internal validation.”