# Before comparing HRV numbers, check what was measured

*Draft • Research checked 4 October 2026 • AI-assisted DomDNA editorial content. No independent clinical review or publication is claimed. General education, not individual medical advice.*

Two people compare their wearable dashboards over breakfast. One reports a heart-rate variability number twice as high as the other. Within seconds, a casual conversation has turned into a verdict about recovery, fitness or stress.

There is a question to ask before any verdict: are the two devices reporting the same measurement, collected over the same kind of period? A shared label and the same unit do not guarantee an equal comparison.

## HRV has more than one calculation

Apple's HealthKit documentation identifies its HRV quantity as SDNN, calculated from the variation in intervals between normal heartbeats. Oura describes its HRV using RMSSD and reports an average across the night. These labels describe different ways of summarising beat-to-beat timing. [Apple documentation](https://developer.apple.com/documentation/healthkit/hkquantitytypeidentifier/heartratevariabilitysdnn); [Oura metric explanation](https://ouraring.com/blog/west-virginia-university-validates-oura/); [Oura measurement guide](https://support.ouraring.com/hc/en-us/articles/360025441974-Heart-Rate-Variability).

The point is not to nominate a winner. Before putting two numbers on one chart, establish what each one represents. A daily summary, a brief reading and a night-time average are not automatically interchangeable because an app places them under “HRV”.

You do not need to learn the equations to ask that question. Look for the metric name, collection window and explanation in the device documentation. If a third-party dashboard imports the data, check which source it is displaying.

## What a validation study can tell you

A 2022 laboratory study compared six wearable devices with reference measurements in 53 healthy young adults. Participants spent a single night in the laboratory. The researchers matched reference measurement periods to those used by each wearable when analysing heart-rate metrics. [Original study](https://mdpi-res.com/d_attachment/sensors/sensors-22-06317/article_deploy/sensors-22-06317.pdf).

That design highlights the importance of matching the question and measurement conditions. It does not certify every later device generation or firmware version. A study of healthy young adults in a laboratory also cannot settle performance in every medical condition or everyday setting.

When a product page says “validated”, look for the exact device, population, reference method and metric. Agreement for average heart rate does not establish agreement for every other number on the dashboard. A broad adjective can hide several separate tests.

## Make your own record interpretable

Suppose you change devices and the next month's HRV values look different. Mark the date of the switch before interpreting the line as a change in your body. Keep the old and new sources identifiable rather than blending them into a single uninterrupted series.

The same principle applies when an app changes the way a metric is presented. Save a note about the update if the display changes. That note does not prove the update caused the difference, but it stops an important possibility from disappearing out of the record.

For everyday use, decide what you want the record to help with. You might want to describe a pattern to a clinician or understand when the device collected data. Those are more specific goals than trying to make the highest possible number appear tomorrow.

## Missing data deserves a label

Oura explains that gaps in its night-time heart-rate graphs can arise when pulse monitoring is disrupted. A gap should remain a gap rather than be treated as a low or zero value. [Oura troubleshooting](https://support.ouraring.com/hc/en-us/articles/360025446954-Troubleshooting-Gaps-in-Heart-Rate-Graphs).

If you export a record, preserve dates and source labels. Do not quietly fill missing nights with nearby values and then describe the resulting smooth curve as observed data. A modest, incomplete record can be more honest and useful than a beautiful invented one.

Finally, symptoms matter outside the dashboard. Do not use a reassuring HRV number to dismiss feeling unwell or delay appropriate medical advice. This article does not set a diagnostic threshold or prescribe training from a score.

A better breakfast conversation starts with curiosity: “Which metric is that, and when was it measured?” It may produce fewer rankings, but it leaves both people with a more accurate understanding of their devices.

[Explore DomDNA’s free educational health quiz](https://domdna.com/quiz). It explores lifestyle topics from answers; it does not calculate HRV, analyse DNA or diagnose recovery problems.