Skip to content

Main content

Public Health Report Delay Censor Window Tool

Report an observed reporting delay or an explicit right-censor duration.

Loading tool…

Description

Report an observed reporting delay or an explicit right-censor duration.

Public-health summaries depend on who is counted, which observations are verified, and the period and population used as the base. Shares, weighted contributions, and inventory balances describe supplied records; they do not by themselves establish a health outcome or a clinical recommendation.

Report an observed reporting delay or an explicit right-censor duration.

When to use this tool

Use it for public health report delay censor window when the required inputs and conventions are already available.

How to use the tool and how it works

  1. Enter onsetDay, reportDay, cutoffDay, reported. Use the stated units and boundary conventions.
  2. Run the calculation. Correct any input error before interpreting a result.
  3. Read delayDays, exact, included. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.

Require cutoffDay>=onsetDay and, when reported, reportDay>=onsetDay. For reported events use reportDay for delayDays and exact true; otherwise use cutoffDay with exact false. Included requires reported and reportDay<=cutoffDay.1

Input fieldMeaning and unitsAccepted input
onsetDayOnset DayRequired. Safe integer.
reportDayReport DayRequired. Safe integer.
cutoffDayCutoff DayRequired. Safe integer.
reportedReportedRequired. Boolean.
Output fieldInterpretationReturned shape
delayDaysDelay DaysRequired. Safe integer.
exactWhether delay ends at an actual supplied report rather than censoring at cutoff.Required. Boolean.
includedWhether an actual report was recorded on or before cutoffDay.Required. Boolean.
json
{
  "input": {
    "onsetDay": 100,
    "reportDay": 108,
    "cutoffDay": 110,
    "reported": true
  },
  "output": {
    "delayDays": 8,
    "exact": true,
    "included": true
  }
}

Limitations and assumptions

  • A report after cutoff retains its actual delay but is not included. An unreported delay is follow-up to cutoff, not an observed reporting delay or an estimated eventual report date.
  • The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
  • Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.

Alternative or Complementary methods

For public health report delay censor window, check the source records and the supplied rule before comparing the result with another method. Use an appropriately validated measurement or analysis method for clinical interpretation.

References

  1. Calculation and input contract: public-health/public-health-report-delay-censor-window — tool.io

Similar or alternative tools