Skip to content

Main content

Research Visit Window Edge Closure Tool

Apply explicitly supplied research visit-window endpoint conventions.

Loading tool…

Description

Check a visit against an explicitly bounded research window.

Clinical research distinguishes supplied protocol metadata, participant/event records, allocation bookkeeping and an analysis target. A local count, permission flag or denominator choice can help reconcile records without establishing valid consent, randomization, regulatory compliance or a reliable treatment-effect estimate.

Check a visit against an explicitly bounded research window.

When to use this tool

Use Research Visit Window Edge Closure when checking the stated clinical-research record, allocation, timing, analysis or evidence-basis convention.

How to use the tool and how it works

  1. Enter visit, start, end, startIncluded, endIncluded. 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 within, atBoundary. Inspect within, atBoundary before interpreting the associated values.

Check a visit against an explicitly bounded research window. Require start <= end; within uses each inclusion flag independently, atBoundary tests exact equality with either endpoint.1

Input fieldMeaning and unitsAccepted input
visitVisitRequired. Finite number.
startStartRequired. Finite number.
endEndRequired. Finite number.
startIncludedStart IncludedRequired. Boolean.
endIncludedEnd IncludedRequired. Boolean.
Output fieldInterpretationReturned shape
withinWithinRequired. Boolean.
atBoundaryAt BoundaryRequired. Boolean.
json
{
  "input": {
    "visit": 10,
    "start": 10,
    "end": 20,
    "startIncluded": true,
    "endIncluded": false
  },
  "output": {
    "within": true,
    "atBoundary": true
  }
}

Limitations and assumptions

  • Boundary labels and window values are supplied; protocol eligibility, date conventions and suitable clinical timing are not inferred.
  • 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 approved protocol, authenticated source records and qualified clinical/statistical oversight for actual trial design, conduct and interpretation.

References

  1. Calculation and input contract: clinical-research/research-visit-window-edge-closure — tool.io

Similar or alternative tools