Description
Compare supplied witness and interpreter identifiers in a consent record.
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.
Compare supplied witness and interpreter identifiers in a consent record.
When to use this tool
Use Consent Witness Versus Interpreter Role when you already have recordId, witnessId, interpreterId and need to compare supplied witness and interpreter identifiers in a consent record.
How to use the tool and how it works
- Enter recordId, witnessId, interpreterId. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read sameRecordedPerson, rolesKey. Inspect sameRecordedPerson before interpreting the associated values.
Require recordId, witnessId and interpreterId nonempty; return exact witness/interpreter equality and serialize the three identifiers in a roles key.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| recordId | Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| witnessId | Witness Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| interpreterId | Interpreter Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| sameRecordedPerson | Same Recorded Person | Required. Boolean. |
| rolesKey | Roles Key | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"recordId": "R17",
"witnessId": "P2",
"interpreterId": "P3"
},
"output": {
"sameRecordedPerson": false,
"rolesKey": "[\"R17\",\"P2\",\"P3\"]"
}
}Limitations and assumptions
- Equality reflects identifiers only; distinct strings need not identify distinct people. No identity, role suitability, consent validity or legal permission is established.
- 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
- Proxy Consent Relationship Source Code
Qualify an explicit proxy relationship code by supplied source.
- Consent Audio Recording Permission Field
Preserve a supplied recording-permission assertion and purpose.