Description
Return certainlyInside when the entire visit interval is contained and possiblyInside when their closed intervals overlap inclusively.
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.
Return certainlyInside when the entire visit interval is contained and possiblyInside when their closed intervals overlap inclusively.
When to use this tool
Use GCP Visit Window Precision Token when you need a literal clinical-trial metadata consistency check.
How to use the tool and how it works
- Enter visitLower, visitUpper, allowedLower, allowedUpper. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read certainlyInside, possiblyInside. Inspect certainlyInside, possiblyInside before interpreting the associated values.
Require ordered visit and allowed intervals. Return certainlyInside when the entire visit interval is contained and possiblyInside when their closed intervals overlap inclusively.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| visitLower | Visit Lower | Required. Safe integer. |
| visitUpper | Visit Upper | Required. Safe integer. |
| allowedLower | Allowed Lower | Required. Safe integer. |
| allowedUpper | Allowed Upper | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| certainlyInside | Certainly Inside | Required. Boolean. |
| possiblyInside | Possibly Inside | Required. Boolean. |
{
"input": {
"visitLower": 10,
"visitUpper": 12,
"allowedLower": 9,
"allowedUpper": 13
},
"output": {
"certainlyInside": true,
"possiblyInside": true
}
}Limitations and assumptions
- Touching endpoints count as possible overlap. These are supplied precision bounds rather than probability distributions; neither flag verifies protocol eligibility, visit completion, or an approved deviation.
- 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
Similar or alternative tools
- GCP Consent Version Visit Date Order
Compare consentVersion exactly with requiredVersion, test signedDay no later than visitDay and no earlier than versionEffectiveDay, and return recordMatches only when all checks pass and withdrawn is false.
- GCP Site Contact Safe Window
Test a start-inclusive end-exclusive window, optionally across midnight, plus exact day and channel membership; matches is their conjunction.