Skip to content

Main content

Case Definition Revision Onset Boundary Tool

Choose an explicitly supplied case-definition revision side by onset date and boundary-equality policy without determining case status.

Loading tool…

Description

Compare an onset date with a supplied case-definition revision boundary.

Epidemiological reporting depends on case-definition versions, observation windows, censoring, person/test denominators and time-bin boundaries. Missing and indeterminate results differ, while multiple tests can belong to one person. Local record arithmetic does not diagnose infection, establish transmission or select a public-health rule.

Compare an onset date with a supplied case-definition revision boundary.

When to use this tool

Use Case Definition Revision Onset Boundary when checking the stated benign surveillance record, time, exposure or denominator convention.

How to use the tool and how it works

  1. Enter onsetDate, revisionBoundaryDate, boundaryUsesNew. 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 useNewDefinition. Inspect useNewDefinition before interpreting the associated values.

Parse real onset/revision-boundary YYYY-MM-DD dates. useNewDefinition means onset>boundary, adding equality only when boundaryUsesNew=true.1

Input fieldMeaning and unitsAccepted input
onsetDateOnset DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
revisionBoundaryDateRevision Boundary DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
boundaryUsesNewBoundary Uses NewRequired. Boolean.
Output fieldInterpretationReturned shape
useNewDefinitionUse New DefinitionRequired. Boolean.
json
{
  "input": {
    "onsetDate": "2026-11-01",
    "revisionBoundaryDate": "2026-11-01",
    "boundaryUsesNew": true
  },
  "output": {
    "useNewDefinition": true
  }
}

Limitations and assumptions

  • This selects a supplied temporal branch; no case definition is loaded or applied and current public-health reporting rules are not determined.
  • 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.

Alternative or Complementary methods

Use verified source records, current authoritative definitions and appropriate complete epidemiological/statistical methods with qualified public-health interpretation for actual decisions.

References

  1. Calculation and input contract: epidemiology/case-definition-revision-onset-boundary — tool.io

Similar or alternative tools