How PlainHealth Comparison Works

The comparison tool lets you stack two or more records side by side so you can see their key metrics at the same time. Comparisons are produced deterministically from the underlying dataset — the same inputs always produce the same output — so you can cite them, bookmark them, and return later with confidence that the numbers have not been quietly edited by an algorithm tuned for engagement.

Reading a Comparison Page Well

Comparison tables highlight differences first and similarities second. Pay attention to the time frame each column covers — records refreshed at different cadences can appear more different than they really are. Look at the denominator of any rate-based field; a record with a small denominator can show a dramatic rate from a handful of observations. Where a metric is known to be noisy, we flag it on the page. The goal is to help you triage quickly, then click through to the full records for the substantive detail.

When to Use Compare

Comparison is most useful early in research — when you want to shortlist candidates, narrow a geography, or decide which records deserve a deeper read. It is less useful as the final step of a consequential decision. Once you have shortlisted records from the comparison view, click through to the full record page to see every field, the methodology notes, and any warnings we attach to the data quality of that specific record. For legal, medical, financial, safety, or employment decisions, verify the underlying fact with the issuing agency before acting.

Methodology Notes

The comparison page pulls live from the same canonical dataset that powers the rest of the site. We do not re-rank, re-weight, or post-process values for the comparison view — every cell you see is the same value you would see on the individual record page. When a field is missing on one of the compared records, we show an em dash rather than a zero, so that "absent" is never confused with "zero." If a comparison appears to contradict a record page, email us the specific record IDs and we will triage within the next refresh cycle.