Sensitivity, also known as the true positive rate (TPR) or recall, is calculated as the proportion of actual positives correctly identified by a diagnostic test. Mathematically, it is expressed as True Positives / (True Positives + False Negatives). A highly sensitive test produces very few false negatives, making it critical for screening applications where missing a diagnosis carries severe clinical consequences.
Glossary
Sensitivity

What is Sensitivity?
Sensitivity is a statistical measure of a binary classification test's ability to correctly identify true positives, quantifying how effectively a diagnostic model detects a disease when it is actually present.
In the context of Software as a Medical Device (SaMD) and FDA clearance pathways, sensitivity is a primary endpoint in clinical validation study design. It is evaluated alongside specificity and plotted on a ROC curve to determine the overall diagnostic accuracy of an AI-driven imaging or pathology tool. A locked algorithm's sensitivity must be rigorously demonstrated in its analytical validation before a 510(k) or De Novo submission.
Sensitivity vs. Specificity
A comparative analysis of the two foundational statistical measures used to evaluate the clinical validity of a binary diagnostic test or Software as a Medical Device (SaMD).
| Feature | Sensitivity | Specificity |
|---|---|---|
Primary Definition | Proportion of actual positives correctly identified | Proportion of actual negatives correctly identified |
Core Question Answered | How well does the test detect the disease? | How well does the test exclude the disease? |
Target Condition Status | Disease is present | Disease is absent |
Statistical Formula | True Positives / (True Positives + False Negatives) | True Negatives / (True Negatives + False Positives) |
Clinical Impact of High Value | Rules OUT the disease (high Negative Predictive Value) | Rules IN the disease (high Positive Predictive Value) |
Consequence of Low Value | Missed diagnoses (False Negatives) | False alarms (False Positives) |
Primary Trade-Off | Increases as the decision threshold is lowered | Increases as the decision threshold is raised |
Regulatory Focus (FDA) | Critical for screening SaMD to ensure no case is missed | Critical for confirmatory SaMD to prevent unnecessary intervention |
Key Characteristics of Sensitivity
Sensitivity is a critical statistical measure in diagnostic medicine that quantifies a test's ability to correctly identify patients who have a specific disease. A highly sensitive test minimizes false negatives, making it essential for screening where missing a diagnosis carries severe consequences.
The True Positive Rate
Sensitivity is mathematically defined as the True Positive Rate (TPR). It is calculated by dividing the number of correctly identified positive cases by the total number of actual positive cases.
- Formula: Sensitivity = True Positives / (True Positives + False Negatives)
- Interpretation: A sensitivity of 99% means the test correctly flags 99 out of 100 sick patients, missing only 1.
- Clinical Context: This metric answers the question: 'If a patient has the disease, how likely is the test to be positive?'
The Trade-Off with Specificity
Sensitivity exists in a fundamental inverse relationship with Specificity, the true negative rate. Adjusting a diagnostic threshold to catch more true positives inevitably increases false positives.
- Screening Priority: High sensitivity is prioritized for initial screening tests (e.g., HIV ELISA) to cast a wide net.
- Confirmatory Priority: High specificity is prioritized for confirmatory tests (e.g., Western Blot) to rule out false alarms.
- The Yerkes-Dodson Balance: You cannot maximize both simultaneously; the clinical context dictates the acceptable trade-off.
SNOut: Ruling Out Disease
A highly sensitive test is clinically useful for its negative predictive value. The mnemonic 'SNOut' (Sensitive test, Negative result rules Out disease) captures this principle.
- Clinical Utility: A negative result on a 100% sensitive test definitively excludes the target condition.
- Example: A negative D-dimer test (high sensitivity) effectively rules out deep vein thrombosis in low-risk patients.
- Safety Net: This makes sensitivity the paramount metric for screening life-threatening conditions where a missed diagnosis is unacceptable.
Sensitivity in AI Model Evaluation
In machine learning, sensitivity is synonymous with Recall. It is a primary metric for evaluating models trained on imbalanced datasets, common in medical imaging where disease prevalence is low.
- Imbalanced Data: Accuracy is a misleading metric when 99% of scans are normal; a model predicting 'normal' always has 99% accuracy but 0% sensitivity.
- Threshold Tuning: Data scientists adjust the classification threshold of a neural network to achieve a target sensitivity, often guided by an ROC Curve.
- Regulatory Requirement: The FDA requires explicit validation of sensitivity at a predefined operating point for SaMD clearance.
Factors Degrading Sensitivity
Several technical and biological variables can artificially lower the measured sensitivity of a diagnostic system.
- Spectrum Bias: Evaluating a test only on severe, late-stage cases inflates sensitivity; it drops when applied to early-stage or mild disease.
- Technical Error: Poor sample handling, low image resolution, or motion artifacts in radiology can cause the system to miss a visible lesion.
- Reader Variability: In imaging AI, the 'ground truth' is often a human radiologist's annotation, which itself has imperfect sensitivity, creating a noisy ceiling for the model.
Analytical vs. Clinical Sensitivity
Regulatory science distinguishes between two layers of sensitivity validation.
- Analytical Sensitivity: The test's ability to detect a physical analyte (e.g., a specific protein concentration) in a controlled lab sample.
- Clinical Sensitivity: The test's ability to correctly identify patients with the actual disease in a real-world population.
- The Gap: A device can have perfect analytical sensitivity but poor clinical sensitivity if the biomarker is not present in all patients with the disease, highlighting the need for rigorous Clinical Validation Study Design.
Frequently Asked Questions
Explore the critical metric of sensitivity in medical diagnostics, its calculation, and its role in FDA clearance pathways for Software as a Medical Device (SaMD).
Sensitivity is the proportion of true positives correctly identified by a diagnostic test, measuring its ability to detect a disease when it is present. A highly sensitive test produces few false negatives, making it clinically valuable for ruling out a condition when the result is negative. The metric is calculated as True Positives / (True Positives + False Negatives). In the context of Software as a Medical Device (SaMD), demonstrating high sensitivity during analytical validation is a cornerstone of a successful 510(k) Premarket Notification or De Novo Classification Request, as it directly supports the intended use statement for screening or diagnostic aid.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Understanding sensitivity requires a holistic view of diagnostic performance. These related concepts define the statistical and clinical framework for evaluating AI-driven medical imaging tools.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us