Description
Find the requested language exactly, return known status, compare its required version, and otherwise use an empty expectedVersion with versionMatches 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.
Find the requested language exactly, return known status, compare its required version, and otherwise use an empty expectedVersion with versionMatches false.
When to use this tool
Use Consent Language Version Gap when you need a literal clinical-trial metadata consistency check.
How to use the tool and how it works
- Enter language, acknowledgedVersion, requiredVersions, languages. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read languageKnown, versionMatches, expectedVersion. Inspect languageKnown, versionMatches before interpreting the associated values.
Require equally long languages and requiredVersions with unique language strings. Find the requested language exactly, return known status, compare its required version, and otherwise use an empty expectedVersion with versionMatches false.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| language | Language | Required. Text; maximum UTF-16 length 8192. |
| acknowledgedVersion | Acknowledged Version | Required. Text; maximum UTF-16 length 8192. |
| requiredVersions | Required Versions | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| languages | Languages | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| languageKnown | Language Known | Required. Boolean. |
| versionMatches | Version Matches | Required. Boolean. |
| expectedVersion | Configured version or empty-string unknown-language placeholder; inspect languageKnown. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"language": "en",
"acknowledgedVersion": "v1",
"requiredVersions": [
"v2",
"v1"
],
"languages": [
"en",
"fr"
]
},
"output": {
"languageKnown": true,
"versionMatches": false,
"expectedVersion": "v2"
}
}Limitations and assumptions
- The empty expectedVersion is a placeholder for an unknown language but may also be an actual configured version; read languageKnown. No translation quality, effective date, language equivalence, or consent validity 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.
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 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.
- Consent Language Support Share
Count distinct participants and distinct IDs with at least one row matching both language and version; divide the latter by the former or return zero with defined false when empty.