Question 6 of 6 Advanced Scenario
How would you detect data shift before deploying a biological model?
Short answer
Compare the deployment population, measurement pipeline and feature distributions with training data, then test performance and calibration when representative labeled outcomes are available.
Why
A classifier trained on hospital A may face hospital B with different disease prevalence, staining reagents and specimen handling. Define the intended population and compare case mix, instrument metadata, missing values and per-feature distributions before use. Distinguish covariate shift, label prevalence changes and concept shift.
A single drift score does not prove degraded predictions. Monitor calibration, subgroup errors and clinically relevant operating thresholds on independent prospective or external data when ground truth is available. Check for silent feature changes such as gene identifiers, assay version, unit conversions or batch correction applied differently.
Set actionable drift thresholds, owners and procedures for investigation or rollback before launching. Unknown outcomes may require delayed labeling and sentinel monitoring. Distribution similarity is useful but not evidence of clinical safety on its own.
Common mistakes
- Approving deployment solely because overall feature means match the training cohort
The interviewer might ask next
How would you monitor shift when clinical outcomes arrive several months after predictions?