Skip to content

Main content

Surveillance Reporting Delay One Case Tool

Correct a pair of local-clock epoch-like timestamps by subtracting report-minus-onset UTC-offset difference; negative delays remain audit-visible.

Loading tool…

Description

Return report-minus-onset seconds minus timezoneOffsetDifferenceSeconds, then divide by 86400 for delayDays.

Epidemiological windows encode observation and classification rules on a timeline. Endpoint inclusion, late entry and supplied washout periods change counts, but a local timing flag does not establish infection, clinical risk or a validated case definition.

Return report-minus-onset seconds minus timezoneOffsetDifferenceSeconds, then divide by 86400 for delayDays.

When to use this tool

Use Surveillance Reporting Delay One Case when you need a supplied surveillance-time or risk-window calculation.

How to use the tool and how it works

  1. Enter onsetSeconds, reportedSeconds, timezoneOffsetDifferenceSeconds. 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 correctedDelaySeconds, delayDays. Use the output convention below.

Return report-minus-onset seconds minus timezoneOffsetDifferenceSeconds, then divide by 86400 for delayDays.1

Input fieldMeaning and unitsAccepted input
onsetSecondsOnset SecondsRequired. Finite number.
reportedSecondsReported SecondsRequired. Finite number.
timezoneOffsetDifferenceSecondsTimezone Offset Difference SecondsRequired. Finite number.
Output fieldInterpretationReturned shape
correctedDelaySecondsCorrected Delay SecondsRequired. Finite number.
delayDaysDelay DaysRequired. Finite number.
json
{
  "input": {
    "onsetSeconds": 0,
    "reportedSeconds": 172800,
    "timezoneOffsetDifferenceSeconds": 0
  },
  "output": {
    "correctedDelaySeconds": 172800,
    "delayDays": 2
  }
}

Limitations and assumptions

  • Days are fixed 24-hour durations, not calendar date changes. Offsets and clocks are supplied; reporting quality, infection timing and clinical interpretation are not assessed.
  • 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

Apply the appropriate study protocol or public-health definition to verified records. Resolve calendar, clock, follow-up and censoring conventions before interpreting timing as epidemiological evidence.

References

  1. Calculation and input contract: epidemiology/surveillance-reporting-delay-one-case — tool.io

Similar or alternative tools

  • Surveillance Week Origin Gap

    Subtract safe numeric day indexes with exact integer arithmetic, return decimal day gap and integer quotient, and aligned when the remainder is zero.

  • Risk Window Left Entry Offset

    Return max(0,enteredAt-windowStart) and max(0,windowEnd-max(windowStart,enteredAt)).