Skip to content

Main content

Protocol Window Boundary Distance Tool

Compare supplied research schedule coordinates with explicit endpoint rules.

Loading tool…

Description

Return signed distances from protocol-window boundaries.

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.

Return signed distances from protocol-window boundaries.

When to use this tool

Use Protocol Window Boundary Distance 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 observedAt, lower, upper, inclusiveUpper. 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 lowerDistance, upperDistance, withinWindow. Inspect withinWindow before interpreting the associated values.

Return signed distances from protocol-window boundaries. Require upper >= lower; lowerDistance = observedAt-lower, upperDistance = upper-observedAt; withinWindow includes lower and uses inclusiveUpper for the upper edge.1

Input fieldMeaning and unitsAccepted input
observedAtObserved AtRequired. Finite number.
lowerLowerRequired. Finite number.
upperUpperRequired. Finite number.
inclusiveUpperInclusive UpperRequired. Boolean.
Output fieldInterpretationReturned shape
lowerDistanceLower DistanceRequired. Finite number.
upperDistanceUpper DistanceRequired. Finite number.
withinWindowWithin WindowRequired. Boolean.
json
{
  "input": {
    "observedAt": 15,
    "lower": 10,
    "upper": 20,
    "inclusiveUpper": true
  },
  "output": {
    "lowerDistance": 5,
    "upperDistance": 5,
    "withinWindow": true
  }
}

Limitations and assumptions

  • A negative distance means outside that edge; no actual protocol or permissible visit timing is established.
  • 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/protocol-window-boundary-distance — tool.io

Similar or alternative tools