Description
Qualify an explicit randomization stratum code by source.
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 randomization stratum code by source.
When to use this tool
Use Trial Randomization Stratum Label when you already have trialId, stratumCode, codeSource and need to qualify an explicit randomization stratum code by source.
How to use the tool and how it works
- Enter trialId, stratumCode, codeSource. 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, stratumCode, codeSource 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. |
| stratumCode | Stratum Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| codeSource | Code Source | 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",
"stratumCode": "S2",
"codeSource": "Protocol v2"
},
"output": {
"token": "[\"TR17\",\"S2\",\"Protocol v2\"]"
}
}Limitations and assumptions
- The result records supplied values without assigning trial participants. 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 Consent Language Label
Qualify an explicit trial-consent version by supplied language code.
- Trial Participant Flow Status
Preserve an explicit participant-flow code by source.