Description
Qualify an explicit proxy relationship code by supplied source.
Research records distinguish a participant's stated preference, a recorded permission assertion, version dates and professional roles. A label does not authenticate consent or authority, while travel minutes and compensation shares capture only selected aspects of burden or payment. Ethical interpretation requires the surrounding circumstances and evidence.
Qualify an explicit proxy relationship code by supplied source.
When to use this tool
Use Proxy Consent Relationship Source Code when you already have participantId, relationshipCode, authoritySource and need to qualify an explicit proxy relationship code by supplied source.
How to use the tool and how it works
- Enter participantId, relationshipCode, authoritySource. 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, relationshipCode, authoritySource 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. |
| relationshipCode | Relationship Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| authoritySource | Authority 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",
"relationshipCode": "REL2",
"authoritySource": "Recorded source A"
},
"output": {
"token": "[\"P17\",\"REL2\",\"Recorded source A\"]"
}
}Limitations and assumptions
- The result records supplied values without deciding proxy authority. 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 original consent, preference, version and role records with the applicable oversight process. Evaluate understanding, voluntariness, scope and actual circumstances rather than treating a local flag, date gap or financial fraction as an ethical determination.
References
Similar or alternative tools
- Incidental Finding Return Choice Token
Preserve an explicit incidental-finding return preference.
- Withdrawal Limited Retention Status Tag
Preserve an explicit withdrawal and limited-retention status record.