Skip to content

Main content

Dietary Record Coverage Fraction Tool

Audit supplied record-day completion without inferring dietary intake.

Loading tool…

Description

Return dietary-record coverage after excluded days.

Dietary-record coverage concerns which planned days, serving amounts or sample weights are represented. A denominator-specific share is separate from the nutrient content and representativeness of an intake assessment.

Return dietary-record coverage after excluded days.

When to use this tool

Use Dietary Record Coverage Fraction when checking a supplied dietary-record support convention.

How to use the tool and how it works

  1. Enter recordedDays, expectedDays, excludedDays. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read denominatorDays, fraction, defined. Inspect defined before interpreting the associated values.

Return dietary-record coverage after excluded days. Require nonnegative whole expectedDays, excludedDays <= expectedDays and recordedDays <= expectedDays-excludedDays; divide recorded by eligible days, otherwise return zero with defined = false.1

Input fieldMeaning and unitsAccepted input
recordedDaysRecorded DaysRequired. Safe integer; minimum 0.
expectedDaysExpected DaysRequired. Safe integer; minimum 0.
excludedDaysExcluded DaysRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
denominatorDaysDenominator DaysRequired. Safe integer.
fractionrecordedDays/(expectedDays-excludedDays), or zero when defined is false.Required. Finite number.
definedWhether the stated denominator is nonzero; inspect this before using the associated ratio.Required. Boolean.
json
{
  "input": {
    "recordedDays": 5,
    "expectedDays": 7,
    "excludedDays": 1
  },
  "output": {
    "denominatorDays": 6,
    "fraction": 0.8333333333333334,
    "defined": true
  }
}

Limitations and assumptions

  • Zero eligible days are undefined; recorded-day coverage does not establish representative intake.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review the collection method and missingness pattern, and use an appropriate intake assessment for usual-diet or individual conclusions.

References

  1. Calculation and input contract: dietetics/dietary-record-coverage-fraction — tool.io

Similar or alternative tools