Description
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.
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.
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.
When to use this tool
Use GCP Consent Version Visit Date Order when you need a literal clinical-trial metadata consistency check.
How to use the tool and how it works
- Enter consentVersion, requiredVersion, signedDay, visitDay, versionEffectiveDay, withdrawn. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read versionMatches, signedBeforeVisit, signedAfterEffective, recordMatches. Inspect versionMatches, signedBeforeVisit, signedAfterEffective, recordMatches before interpreting the associated values.
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.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| consentVersion | Consent Version | Required. Text; maximum UTF-16 length 8192. |
| requiredVersion | Required Version | Required. Text; maximum UTF-16 length 8192. |
| signedDay | Signed Day | Required. Safe integer. |
| visitDay | Visit Day | Required. Safe integer. |
| versionEffectiveDay | Version Effective Day | Required. Safe integer. |
| withdrawn | Withdrawn | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| versionMatches | Version Matches | Required. Boolean. |
| signedBeforeVisit | Signed Before Visit | Required. Boolean. |
| signedAfterEffective | Signed After Effective | Required. Boolean. |
| recordMatches | Record Matches | Required. Boolean. |
{
"input": {
"consentVersion": "v2",
"requiredVersion": "v2",
"signedDay": 105,
"visitDay": 110,
"versionEffectiveDay": 100,
"withdrawn": false
},
"output": {
"versionMatches": true,
"signedBeforeVisit": true,
"signedAfterEffective": true,
"recordMatches": true
}
}Limitations and assumptions
- Equality passes both date boundaries. These supplied record checks do not verify informed consent, signature authenticity, capacity, language comprehension, or whether a participant may undergo a procedure.
- 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
- Consent Language Version Gap
Find the requested language exactly, return known status, compare its required version, and otherwise use an empty expectedVersion with versionMatches false.
- GCP Consent Language Document Pair
Return languageDirect for exact preferred/document language equality, interpretationMatched when interpreterUsed is true and interpreterLanguage exactly matches preference, and versionMatched for translation/required version equality.