Description
Qualify an explicit trial-consent version by supplied language code.
Trial records distinguish protocol labels, participant events, supply balances and cutoff policies. An inclusive cutoff differs from an exclusive one, and a drug-accountability balance does not establish adherence or a suitable dose. Supplied consent and observation states are not independently verified by a local calculation.
Qualify an explicit trial-consent version by supplied language code.
When to use this tool
Use Trial Consent Language Label when you already have trialId, consentVersion, languageCode and need to qualify an explicit trial-consent version by supplied language code.
How to use the tool and how it works
- Enter trialId, consentVersion, languageCode. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter trialId, consentVersion, languageCode using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| trialId | Trial Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| consentVersion | Consent Version | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| languageCode | Language Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"trialId": "TR17",
"consentVersion": "v2",
"languageCode": "es"
},
"output": {
"token": "[\"TR17\",\"v2\",\"es\"]"
}
}Limitations and assumptions
- The result records supplied values without assessing translation or consent validity. Sources and asserted relationships are not independently authenticated.
- 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
Check the controlled protocol, source records, accountability logs and applicable oversight requirements. Use the full trial workflow and analysis for participant or study decisions; local date comparisons and labels do not determine safety, eligibility or treatment.
References
Similar or alternative tools
- Trial Randomization Stratum Label
Qualify an explicit randomization stratum code by source.
- Trial Outcome Blinding Tag
Preserve explicit outcome-rater blinding status.