Skip to content

Main content

Query Resolution Cycle Duration Tool

Reconcile one supplied reopened administrative query cycle without protocol-compliance inference.

Loading tool…

Description

Sum both open periods as activeDuration; optionally add the closed gap to countedDuration and return that gap separately.

Clinical-trial record intervals track events, query clocks, pauses, and delegation periods. Duration arithmetic requires a common time origin and policy for excluded intervals; it does not authenticate records or establish acceptable trial conduct.

Sum both open periods as activeDuration; optionally add the closed gap to countedDuration and return that gap separately.

When to use this tool

Use Query Resolution Cycle Duration when you need an explicit clinical-trial record-duration or overlap calculation.

How to use the tool and how it works

  1. Enter opened, firstClosed, reopened, finalClosed, countClosedGap. 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 activeDuration, countedDuration, closedGap. Use the output convention below.

Require opened no later than firstClosed, then reopened, then finalClosed. Sum both open periods as activeDuration; optionally add the closed gap to countedDuration and return that gap separately.1

Input fieldMeaning and unitsAccepted input
openedOpenedRequired. Finite number.
firstClosedFirst ClosedRequired. Finite number.
reopenedReopenedRequired. Finite number.
finalClosedFinal ClosedRequired. Finite number.
countClosedGapCount Closed GapRequired. Boolean.
Output fieldInterpretationReturned shape
activeDurationActive DurationRequired. Finite number.
countedDurationCounted DurationRequired. Finite number.
closedGapClosed GapRequired. Finite number.
json
{
  "input": {
    "opened": 0,
    "firstClosed": 10,
    "reopened": 20,
    "finalClosed": 30,
    "countClosedGap": false
  },
  "output": {
    "activeDuration": 20,
    "countedDuration": 20,
    "closedGap": 10
  }
}

Limitations and assumptions

  • Times share one unit and origin and endpoints are subtracted without inclusive-day counting. countClosedGap is caller policy rather than an official monitoring deadline rule.
  • 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 trial protocol, controlled records, and relevant procedures for actual decisions. Resolve time units, clock references, pause authorization, and source evidence before applying a timing rule.

References

  1. Calculation and input contract: gcp/query-resolution-cycle-duration — tool.io

Similar or alternative tools