Description
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.
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 languageDirect for exact preferred/document language equality, interpretationMatched when interpreterUsed is true and interpreterLanguage exactly matches preference, and versionMatched for translation/required version equality.
When to use this tool
Use GCP Consent Language Document Pair when you need a literal clinical-trial metadata consistency check.
How to use the tool and how it works
- Enter preferredLanguage, documentLanguage, interpreterUsed, interpreterLanguage, translationVersion, requiredVersion. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read languageDirect, interpretationMatched, versionMatched. Inspect languageDirect, interpretationMatched, versionMatched before interpreting the associated values.
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.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| preferredLanguage | Preferred Language | Required. Text; maximum UTF-16 length 8192. |
| documentLanguage | Document Language | Required. Text; maximum UTF-16 length 8192. |
| interpreterUsed | Interpreter Used | Required. Boolean. |
| interpreterLanguage | Interpreter Language | Required. Text; maximum UTF-16 length 8192. |
| translationVersion | Translation Version | Required. Text; maximum UTF-16 length 8192. |
| requiredVersion | Required Version | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| languageDirect | Language Direct | Required. Boolean. |
| interpretationMatched | Interpretation Matched | Required. Boolean. |
| versionMatched | Version Matched | Required. Boolean. |
{
"input": {
"preferredLanguage": "fr",
"documentLanguage": "en",
"interpreterUsed": true,
"interpreterLanguage": "fr",
"translationVersion": "v2",
"requiredVersion": "v2"
},
"output": {
"languageDirect": false,
"interpretationMatched": true,
"versionMatched": true
}
}Limitations and assumptions
- The flags are independent; no combined acceptable-consent flag is returned. No language-tag normalization, interpreter competence, translation approval, comprehension, or consent validity 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.
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 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.
- 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.