Skip to content

Main content

Research Contact Date Redaction Shift Tool

Shift a supplied research contact date by explicit signed UTC calendar days without claiming complete deidentification.

Loading tool…

Description

Shift a research contact date by a supplied signed number of calendar days.

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.

Shift a research contact date by a supplied signed number of calendar days.

When to use this tool

Use Research Contact Date Redaction Shift when checking the stated benign surveillance record, time, exposure or denominator convention.

How to use the tool and how it works

  1. Enter contactDate, suppliedShiftDays. 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 shiftedDate. Use the output convention below.

Parse a real contact YYYY-MM-DD date and require signed whole suppliedShiftDays. Shift its UTC date by that many days and require the resulting year within 0000..9999; return YYYY-MM-DD.1

Input fieldMeaning and unitsAccepted input
contactDateContact DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
suppliedShiftDaysSigned whole UTC date shift with resulting year restricted to 0000..9999; not guaranteed anonymization.Required. Safe integer.
Output fieldInterpretationReturned shape
shiftedDateShifted DateRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "contactDate": "2026-10-28",
    "suppliedShiftDays": 4
  },
  "output": {
    "shiftedDate": "2026-11-01"
  }
}

Limitations and assumptions

  • A uniform date shift is not proven anonymization or lawful disclosure; no identity risk or public-health event is evaluated.
  • 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 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/research-contact-date-redaction-shift — tool.io

Similar or alternative tools