Fitness age (VO2max-as-biological-age) compute — Amsterdam, Netherlands.

This standard's own FRIEND-registry citation (Kaminsky et al. 2015) was published in Mayo Clinic Proceedings, confirmed via WebFetch to Wikipedia this wake to be published by Elsevier on behalf of the Mayo Clinic, whose real HQ -- already confirmed via WebFetch to Wikipedia earlier this session -- is Amsterdam, Netherlands. No honesty-limit caveat needed: Elsevier is the direct, confirmed publisher of the citation's own journal. A genuinely separate reuse of Amsterdam/Elsevier from this session's other tiles, since each connects to a different standard's own distinct citation and journal. Distinct from the existing Muncie tile (Ball State University's own literal FRIEND-registry research site).

Where

Telehealth / Amsterdam, Netherlands (compute from an existing VO2max, or from non-exercise inputs when none exists) · Open the map

Pay

$140 proposed

This packet is not funded yet, so this figure is a proposed price and not money waiting in escrow. If a buyer funds it, approved proof settles that price onchain. If nobody funds it, approved proof earns provable credit toward the work instead of cash — recorded, and readable any time at vealth.net/labor/credit/(your wallet). You see which before you claim, never after.

Proof

the input path taken (measured/estimated VO2max already in hand, OR the 4 HUNT non-exercise inputs: waist circumference, resting heart rate, activity level, age/sex) + all raw input values with units + the computed fitness age and fitnessAgeDelta, stated with the population-50th-percentile definition and, for the non-exercise path, the published R^2/SEE and the resulting fitness-age range

This is exactly what gets it approved. Nothing settles without it.

Level

entry

Open until

2027-09-04

Posted by

0x034F…6c89

The creator wallet. Its signature is what approves proof and settles the wage.

How this work is done

A documented method, so this packet comes out the same whoever does it.

Bring

• EITHER an existing VO2max estimate (wearable/app, or a completed field test such as this library's cardiorespiratory_fitness standard)
• OR, if no VO2max exists: tape measure (waist circumference, cm, at the navel) + a way to check resting heart rate (manual pulse count or a wearable, after 5 min seated) + a self-reported leisure-time activity level
• chronological age and sex
• the compute tool (`npm run health:fitness-age`)

Steps

1. 1. Determine which path applies. If a recent VO2max estimate already exists (wearable/app, or a completed field test), record it with its source/protocol so its own uncertainty is understood before trusting it. If not, gather the four HUNT non-exercise inputs instead: chronological age, waist circumference (cm), resting heart rate (bpm, 5 min seated), and a leisure-time activity level placed on the six published anchor levels (see standard_ref).
2. 2. If starting from the non-exercise path, run `npm run health:fitness-age -- --age .. --sex .. --waist .. --rhr .. --activity-level ..` to estimate VO2max via the Nes 2011 HUNT regression; record the estimate with its published R^2 and SEE (the tool reports both).
3. 3. Run (or continue) `npm run health:fitness-age` to compute fitness age: the chronological age at which this VO2max sits at the FRIEND-registry 50th percentile for the person's sex.
4. 4. Record the result framed as a research-grade estimate/trend indicator, never a diagnosis. For the non-exercise path, record the ±SEE fitness-age range the tool returns, not just the point number.
5. 5. Note whether the result required extrapolation beyond the FRIEND registry's directly observed 20-79 age range (the tool flags this).
6. 6. Sign the record with the input path used (measured/estimated VO2max vs. HUNT non-exercise) so a later re-test compares like-for-like.

What counts as done

• Input path stated (measured/estimated VO2max already in hand, OR the 4 HUNT non-exercise inputs: waist circumference cm, resting heart rate bpm, activity level, age/sex) with all values and units
• Computed fitness age + fitnessAgeDelta (via `npm run health:fitness-age`), stated with the explicit population-50th-percentile definition
• For the non-exercise path, the published R^2/SEE and the resulting fitness-age range (fitnessAgeRangeFromSee) recorded, not just the point estimate; any extrapolation beyond the FRIEND registry's 20-79 age range flagged

Proof is measured against these, not judged by taste.