A plain-language guide

A positive test.
Should you panic?

A test that's 99% accurate just said you have a rare disease. Here's the surprising โ€” and reassuring โ€” truth about what that really means.

See why not
The surprising truth

A 99%-accurate "yes" can still be wrong โ€” usually.

Picture a disease that just 1 in 1,000 people have, and a test that's right 99% of the time. You test positive. Your gut screams "I'm 99% done for." But the real chance you're sick is closer to 9%.

Nothing is broken about the test. The twist comes from something quietly powerful โ€” how rare the disease was to begin with. The easiest way to believe it is to watch it happen to a thousand people at once.

Try it ยท 1,000 people

Meet 1,000 people. Watch who tests positive.

Every dot is a person. Drag the two dials and watch the crowd sort itself: the few blue dots truly have the disease, the amber dots got a false alarm. The question that matters isn't "is the test good?" โ€” it's "if my dot is coloured, which colour is it likely to be?"

1 in 1,000
99%

Of the 11 people who test positive, only 1 is actually sick.

9%chance you're actually sick after a positive result

So a positive result is overwhelmingly a false alarm. Breathe.

The coloured dots at the top are everyone who tested positive. Notice how the amber false alarms can completely swamp the handful of real cases โ€” that gap is the whole idea.

Why it happens

The disease is rare. That quietly changes everything.

When almost nobody has the disease, the handful of real cases are easy to drown out. A 99% test still gets it wrong for 1 in every 100 healthy people โ€” and there are a lot of healthy people.

Out of 1,000 folks where only one is truly sick, that "tiny" 1% error rate produces about ten false alarms. Ten false positives against one real case: even a great test leaves you outnumbered ten to one. Make the disease more common, or the test sharper, and the balance tips back โ€” exactly what you just felt on the dials.

Where this shows up

It isn't just doctors.

The same trap springs anywhere you screen a big crowd for something rare. The rarer the thing, the more the alarms are false.

๐Ÿฉบ

Medical screening

Mammograms, genetic panels, mass disease screens โ€” a positive is a reason to look closer, not a diagnosis.

๐Ÿ›‚

Airport & security alerts

Scan millions of harmless bags for the rare dangerous one and most alarms will, thankfully, be false.

๐Ÿ“ง

Spam & fraud filters

Flagging the rare bad email or transaction means the same balancing act between catches and false flags.

๐Ÿ””

Any rare-event alarm

Earthquake warnings, fault detectors, AI moderation โ€” rarity makes "it went off" weaker evidence than it feels.

The trap: it's tempting to read "99% accurate" as "99% sure I'm sick." But those answer two different questions. "How often is the test right?" is about the test. "Given a positive, am I sick?" is about you โ€” and it depends on how rare the disease was before you ever walked in.

Carry this with you

How to read any alarm, in three moves.

1

Start with the base rate

How common is the thing before any test? That's your honest starting point.

2

Let the result nudge it

A positive pushes your belief up โ€” by a lot or a little, depending on how good the test is.

3

Update, don't replace

You land between the base rate and certainty โ€” rarely all the way at "definitely."