Skip to content

Main content

Follow Up Visit Window Offset

Compare an observed follow-up day with an explicitly supplied asymmetric inclusive visit window.

Loading tool…

Description

Check a supplied visit day within asymmetric inclusive allowances.

Statistical record calculations depend on risk-set boundaries, cluster assumptions, missingness codes and exposure definitions. Entry can be excluded while exit inclusion is a policy choice, and one design-effect formula assumes equal cluster sizes. A local flag or contribution does not fit a model or establish a clinical result.

Check a supplied visit day within asymmetric inclusive allowances.

When to use this tool

Use Follow Up Visit Window Offset when you already have actualDay, targetDay, earlyAllowanceDays, lateAllowanceDays and need to check a supplied visit day within asymmetric inclusive allowances.

How to use the tool and how it works

  1. Enter actualDay, targetDay, earlyAllowanceDays, lateAllowanceDays. 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 offsetDays, withinWindow. Inspect withinWindow before interpreting the associated values.

Require nonnegative early/late allowances; offset=actual-target, within requires target-early<=actual<=target+late.1

Input fieldMeaning and unitsAccepted input
actualDayActual DayRequired. Finite number.
targetDayTarget DayRequired. Finite number.
earlyAllowanceDaysEarly Allowance DaysRequired. Finite number; minimum 0.
lateAllowanceDaysLate Allowance DaysRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
offsetDaysOffset DaysRequired. Finite number.
withinWindowtargetDay-earlyAllowanceDays<=actualDay<=targetDay+lateAllowanceDays, including both boundaries.Required. Boolean.
json
{
  "input": {
    "actualDay": 32,
    "targetDay": 30,
    "earlyAllowanceDays": 2,
    "lateAllowanceDays": 5
  },
  "output": {
    "offsetDays": 2,
    "withinWindow": true
  }
}

Limitations and assumptions

  • Both boundaries count and fractional days are accepted. No clinical visit, protocol, acceptable allowance, safety or analysis eligibility is established.
  • 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

Use the complete study design, data and statistical model for inference. Check censoring, clustering, visit windows, exposure and missingness conventions before combining these terms, and assess uncertainty with the full analysis.

References

  1. Calculation and input contract: biostatistics/follow-up-visit-window-offset — tool.io

Similar or alternative tools