TP, the true positives, are the people with the condition whom the test flags; FN, the false negatives, are the people with the condition it misses. The denominator is everyone who has the condition, and the sensitivity is the share of them the test finds.
A worked example
Of 100 people with a condition, a test flags 90 and misses 10: Se = 90 / (90 + 10) = 0.90, or 90%. Turned round, a test with a sensitivity of 0.80 that missed 10 people found 0.80 · 10 / 0.20 = 40, as the card above works out.
The table it comes from
|
Condition present |
Condition absent |
| Test positive |
TP |
FP |
| Test negative |
FN |
TN |
Sensitivity reads down the first column. Specificity reads down the second: TN / (TN + FP), the share of healthy people the test clears. The two describe the test and do not change with how common the condition is.
What it does not say
A sensitivity of 90% says the test rarely misses a case. It says nothing about what a positive result means for the person holding it: that is the positive predictive value, TP / (TP + FP), which reads across the first row and depends on how many of the people tested had the condition. A test that finds 90% of cases can still be wrong in most of its positives when the condition is rare.
Common mistakes
- Dividing by the positives. TP / (TP + FP) is the predictive value, not the sensitivity.
- Reading it as the share of correct results. Accuracy counts the whole table; sensitivity counts one column.
- Quoting it without the threshold. A test with a tunable cut-off has a sensitivity at each setting, and raising it lowers the specificity.
Frequently asked questions
What is a good sensitivity?
High enough that a missed case is rare for the purpose: a screening test for a serious disease is set
for sensitivity, at the cost of more false alarms.
Sensitivity or recall?
The same number. Machine learning calls it recall, or the true positive rate.
Where do I get the interval?
The sensitivity and specificity calculator gives a 95% Wilson interval from the counts.