Sensitivity and specificity answer two conditional questions. Among people who truly have the target condition, what proportion test positive? Among people who truly do not have it, what proportion test negative? Those definitions are simple. Using them well requires more care, because a test result is meaningful only in relation to a threshold, a reference standard, a clinical setting, and the probability of the condition before testing.
The practical answer comes first: sensitivity and specificity describe how a test sorted a studied group. They do not, by themselves, give the chance that one positive result is a true positive; that second question requires the condition's frequency in the tested population, or a defensible pretest probability, as well as the test's error pattern.
Build the two-by-two table first#
A diagnostic accuracy study compares an index test with a reference standard, the method used to classify whether the target condition is present. Each participant belongs in one of four cells:
- a true positive has the condition and tests positive;
- a false positive does not have the condition but tests positive;
- a false negative has the condition but tests negative;
- a true negative does not have the condition and tests negative.
Sensitivity equals true positives divided by true positives plus false negatives. Specificity equals true negatives divided by true negatives plus false positives. The false negative proportion is one minus sensitivity, and the false positive proportion is one minus specificity.
Suppose 100 of 1,000 people have a condition. In this constructed example, the test detects 92 of those 100 and misses 8, so sensitivity is 92%, and it correctly returns a negative result for 792 of the 900 people without the condition and returns 108 false positives, so specificity is 88%.
| Test result | Condition present | Condition absent |
|---|---|---|
| Test positive | True positive92 | False positive108 |
| Test negative | False negative8 | True negative792 |
- Sensitivity
- 92%
- Specificity
- 88%
- Positive predictive value
- 46%
- Negative predictive value
- 99%
The arithmetic exposes a fact that percentages can hide. There are 200 positive results, but only 92 are true positives. Positive predictive value is therefore 92 divided by 200, or 46%. A positive result is not meaningless. It is a signal you have to interpret and, often, confirm with a more specific process.
Predictive values answer the result-facing question#
Positive predictive value asks: among everyone who tested positive, what proportion truly had the condition? Negative predictive value asks the parallel question among negative results. Their denominators start with the test result, which is usually how you meet the problem.
Now hold sensitivity and specificity at the same constructed values, but change the hypothetical setting so 400 of 1,000 people have the condition; the test produces many more true positives, while the smaller condition-absent group produces fewer false positives.
| Test result | Condition present | Condition absent |
|---|---|---|
| Test positive | True positive368 | False positive72 |
| Test negative | False negative32 | True negative528 |
- Sensitivity
- 92%
- Specificity
- 88%
- Positive predictive value
- 83.6%
- Negative predictive value
- 94.3%
Positive predictive value is now 368 divided by 440, or 83.6%. Negative predictive value remains high at 528 divided by 560, or 94.3%, but it is lower than in the first setting. The test characteristics were held constant by construction. Only the proportion with the condition changed.
In real studies, sensitivity and specificity can also shift with case mix. Disease severity, coexisting conditions, the timing of testing, specimen quality, prior treatment, and how borderline results are handled may all affect performance. It is safer to call sensitivity and specificity properties of a test procedure in a defined population than timeless properties of a device or assay.
Thresholds trade one error for another#
Many tests begin with a continuous measurement, such as a concentration, image score, or model probability. A threshold converts that measurement into positive and negative results. Lowering the threshold labels more people positive. That usually catches more people with the condition, increasing sensitivity, while also creating more false positives, decreasing specificity. Raising the threshold usually does the reverse.
There is no universally best point on that trade-off. The appropriate threshold depends on the intended role and the consequences of errors. A preliminary test for a serious, treatable condition may prioritize avoiding false negatives. A confirmatory test that leads to an invasive procedure may prioritize avoiding false positives. Costs, delays, anxiety, adverse effects, and missed opportunities belong in the decision.
A receiver operating characteristic curve plots sensitivity against the false positive proportion across thresholds. Its area summarizes ranking across the tested range, but it does not choose a clinical threshold, show predictive value in a new setting, or prove that testing improves outcomes. A useful report gives results at prespecified, clinically relevant thresholds and shows uncertainty for each estimate.
Likelihood ratios connect test performance to prior probability#
The positive likelihood ratio is sensitivity divided by one minus specificity. The negative likelihood ratio is one minus sensitivity divided by specificity. In the constructed examples, the positive likelihood ratio is 0.92 divided by 0.12, about 7.7, and the negative likelihood ratio is 0.08 divided by 0.88, about 0.09.
Likelihood ratios update odds. Convert pretest probability to odds, multiply by the relevant likelihood ratio, then convert the resulting odds back to probability. A calculator or nomogram prevents arithmetic errors. The central concept matters more than memorizing the formulas: a test modifies what was plausible before the sample was collected.
Likelihood ratios do not rescue a weak study. Verification bias occurs when the decision to perform the reference standard depends on the index-test result. Incorporation bias occurs when the reference standard includes information from the index test. Review bias can occur when interpreters know the other result. Each can make accuracy look better than it will be in practice.
The reference standard can be imperfect#
Calling one method a reference standard does not make it error-free. Some conditions have no single definitive test. Pathology can be limited by sampling. Imaging interpretation can vary. Clinical follow-up can misclassify people who leave the system. Composite standards can embed subjective decisions.
Read how and when the reference assessment was performed, whether interpreters were masked to the index result, and whether every participant received the same standard. A long delay between tests creates another problem because the condition may change, and STARD asks authors to report these details so you can reconstruct the pathway rather than accept a single accuracy percentage.
Indeterminate and missing results also matter. Excluding unreadable images or invalid samples can produce an attractive estimate for the subset the test handled. Deployment performance includes those failures. A transparent report states how many tests failed, why they failed, what happened to those participants, and how alternative assumptions changed the estimates.
Confidence intervals show how much the study learned#
Sensitivity is estimated only from participants with the condition. Specificity is estimated only from participants without it. A study may enroll hundreds of people yet have very few outcome cases, leaving sensitivity imprecise. The same problem appears in reverse when almost everyone has the condition.
Confidence intervals should accompany sensitivity, specificity, likelihood ratios, and predictive values. Subgroup estimates need their own denominators and intervals. A difference between two point estimates is not automatically evidence of a subgroup difference, especially when intervals are wide or comparisons were not planned.
A disciplined reading sequence#
Start with the test's intended role in your setting: screening, triage, replacement, add-on, or confirmation. Define the target condition, population, setting, threshold, and reference standard. Rebuild the two-by-two table from reported counts when possible. Then calculate or verify sensitivity, specificity, predictive values, and likelihood ratios.
Next, inspect case spectrum, missing and indeterminate results, masking, timing, and verification. Look for confidence intervals rather than a lone percentage. Finally, ask whether the result changes a decision you would make, and whether evidence of diagnostic accuracy comes with evidence about benefits, harms, and implementation.
The articles on communicating risk with natural frequencies and reading a calibration plot extend this reasoning. The site's research overview explains the broader evidence-literacy focus.
References#
- Cochrane Handbook for Diagnostic Test Accuracy Reviews
- STARD 2015 diagnostic accuracy reporting guideline
- Likelihood ratios in diagnostic testing
- Variation in sensitivity and specificity across populations
- Sensitivity, specificity, and predictive values
Questions and answers
Is a test with 95% sensitivity 95% accurate?
Not necessarily. Sensitivity concerns only people who truly have the condition. Overall correct classification also depends on specificity and the mix of people tested, while clinical usefulness depends on the consequences of each error.
Does high specificity mean a positive result is probably true?
It helps, but pretest probability still matters. In a very low-prevalence setting, false positives from a large condition-absent group can outnumber true positives.
Are sensitivity and specificity unaffected by prevalence?
Their formulas do not contain prevalence, but observed values can change across populations because disease spectrum, thresholds, verification, and other features differ. Transporting estimates requires clinical similarity, not just matching prevalence.
What is the difference between prevalence and pretest probability?
Prevalence is the proportion with the condition in a defined population and period, while pretest probability is the estimated chance for the person or subgroup before this test, using setting, symptoms, history, and prior information.
Can one test result prove or exclude a diagnosis?
Sometimes a result can be highly informative, but proof depends on the test, threshold, setting, reference evidence, and alternatives. Most results update a probability and must be interpreted in the full clinical context.