Skip to content

Main content

Child Age Calendar Partial Interval Tool

Propagate supplied absolute calendar-day birth bounds without approximating months or developmental age.

Loading tool…

Description

Propagate supplied absolute calendar-day birth bounds without approximating months or developmental age.

Pediatric research records use chronological age, visit windows, measurement resolution, task observations, and caregiver reports. Missing observation differs from noncompletion, and a completeness share depends on its denominator. Arithmetic on supplied records is separate from a developmental or clinical assessment.

Propagate supplied absolute calendar-day birth bounds without approximating months or developmental age.

When to use this tool

Use Child Age Calendar Partial Interval when you need this age, observation, visit, measurement, or record-completeness calculation with supplied inputs.

How to use the tool and how it works

  1. Enter observationDay, birthEarliestDay, birthLatestDay. 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 ageLowerDays, ageUpperDays. Use the output convention below.

Require birthEarliestDay<=birthLatestDay<=observationDay and return ageLowerDays=observationDay-birthLatestDay and ageUpperDays=observationDay-birthEarliestDay.1

Input fieldMeaning and unitsAccepted input
observationDayObservation DayRequired. Safe integer.
birthEarliestDayBirth Earliest DayRequired. Safe integer.
birthLatestDayBirth Latest DayRequired. Safe integer.
Output fieldInterpretationReturned shape
ageLowerDaysAge Lower DaysRequired. Safe integer.
ageUpperDaysAge Upper DaysRequired. Safe integer.
json
{
  "input": {
    "observationDay": 1000,
    "birthEarliestDay": 900,
    "birthLatestDay": 910
  },
  "output": {
    "ageLowerDays": 90,
    "ageUpperDays": 100
  }
}

Limitations and assumptions

  • Inputs are integer day coordinates on one calendar basis, not partially specified date strings. Bounds reflect only supplied birth-date uncertainty, without gestational correction, probability weights, or clinical interpretation.
  • 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. Signed zero is exported as zero.

Alternative or Complementary methods

Use verified dates, measurement protocols, and observation definitions for the intended research question. A clinical interpretation needs the relevant age-specific assessment and context beyond the arithmetic record check.

References

  1. Calculation and input contract: pediatrics/child-age-calendar-partial-interval — tool.io

Similar or alternative tools

  • Research Age Anchor Gap

    Compare supplied civil-date research age with an explicit day anchor; no age-category or care rule.

  • Pediatric Research Followup Age Window Gap

    For nonnegative integer ageAtBaselineDays and elapsedDays and ordered nonnegative minimumAgeDays and maximumAgeDays return ageAtVisitDays=baseline+elapsed, minimumMargin=age-minimum, maximumMargin=maximum-age, and inside on both inclusive bounds.