Skip to content

Main content

GCP Site Contact Safe Window Tool

Check supplied local clock/day/channel contact permissions without named-zone inference.

Loading tool…

Description

Test a start-inclusive end-exclusive window, optionally across midnight, plus exact day and channel membership; matches is their conjunction.

Good clinical practice record checks compare supplied versions, language labels, roles, dates, and source links. A local metadata match can reveal consistency but does not establish valid consent, competent authorization, or regulatory compliance.

Test a start-inclusive end-exclusive window, optionally across midnight, plus exact day and channel membership; matches is their conjunction.

When to use this tool

Use GCP Site Contact Safe Window when you need a literal clinical-trial metadata consistency check.

How to use the tool and how it works

  1. Enter localMinute, startMinute, endMinute, permittedDays, localDay, channel, allowedChannels. Keep parallel arrays aligned. 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 timeAllowed, dayAllowed, channelAllowed, matches. Inspect timeAllowed, dayAllowed, channelAllowed, matches before interpreting the associated values.

Require localMinute, startMinute, and endMinute as integers in [0, 1439] and localDay in [0, 6], with permitted day values in that range. Test a start-inclusive end-exclusive window, optionally across midnight, plus exact day and channel membership; matches is their conjunction.1

Input fieldMeaning and unitsAccepted input
localMinuteLocal MinuteRequired. Safe integer; minimum 0; maximum 1439.
startMinuteStart MinuteRequired. Safe integer; minimum 0; maximum 1439.
endMinuteEnd MinuteRequired. Safe integer; minimum 0; maximum 1439.
permittedDaysPermitted DaysRequired. Array of safe integer; maximum items 256.
localDayCaller-assigned day index 0-6; no fixed weekday naming or overnight previous-day adjustment is inferred.Required. Safe integer; minimum 0; maximum 6.
channelChannelRequired. Text; maximum UTF-16 length 8192.
allowedChannelsAllowed ChannelsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
timeAllowedTime AllowedRequired. Boolean.
dayAllowedDay AllowedRequired. Boolean.
channelAllowedChannel AllowedRequired. Boolean.
matchesMatchesRequired. Boolean.
json
{
  "input": {
    "localMinute": 600,
    "startMinute": 540,
    "endMinute": 1020,
    "permittedDays": [
      1,
      2,
      3,
      4,
      5
    ],
    "localDay": 2,
    "channel": "phone",
    "allowedChannels": [
      "phone"
    ]
  },
  "output": {
    "timeAllowed": true,
    "dayAllowed": true,
    "channelAllowed": true,
    "matches": true
  }
}

Limitations and assumptions

  • Equal start/end defines an empty window. The supplied local day applies directly even for the after-midnight portion; no timezone conversion, previous-day association, consent, or actual contact safety is verified.
  • 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

Review the complete controlled trial records and applicable professional process. Verify authenticity, protocol scope, consent, competence, and effective versions through the appropriate responsible reviewers.

References

  1. Calculation and input contract: gcp/gcp-site-contact-safe-window — tool.io

Similar or alternative tools

  • Query Resolution Cycle Duration

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

  • GCP Visit Window Precision Token

    Return certainlyInside when the entire visit interval is contained and possiblyInside when their closed intervals overlap inclusively.