Description
Preserve an explicit research contact preference.
Research records need explicit date origins, visit definitions, consent context and observation states. Study day one can omit day zero, whereas ordinary elapsed-day arithmetic starts at zero. A supplied report label or date difference is not a validated clinical finding or a complete research endpoint.
Preserve an explicit research contact preference.
When to use this tool
Use Research Participant Contact Preference when you already have participantId, methodWording, preferenceSource and need to preserve an explicit research contact preference.
How to use the tool and how it works
- Enter participantId, methodWording, preferenceSource. 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 participantId, methodWording, preferenceSource 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 |
|---|---|---|
| participantId | Participant Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| methodWording | Method Wording | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| preferenceSource | Preference 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": {
"participantId": "P17",
"methodWording": "email",
"preferenceSource": "Participant form"
},
"output": {
"token": "[\"P17\",\"email\",\"Participant form\"]"
}
}Limitations and assumptions
- The result records supplied values without sending messages or assessing consent. 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
Review the protocol, source documents and study-day convention before combining records. Use the complete research and clinical assessment for interpretation; local labels, offsets and comparisons do not establish data validity, participant status or an outcome.
References
Similar or alternative tools
- Research Instrument Edition Token
Qualify an explicit research instrument identifier by edition.
- Clinical Study Screen Fail Code
Qualify an explicit screening failure code by source.