Skip to content

Main content

Consent Audio Recording Permission Field

Record an explicit purpose-specific audio permission flag without establishing consent validity or recording audio.

Loading tool…

Description

Preserve a supplied recording-permission assertion and purpose.

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.

Preserve a supplied recording-permission assertion and purpose.

When to use this tool

Use Consent Audio Recording Permission Field when you already have recordId, purposeWording, permissionRecorded and need to preserve a supplied recording-permission assertion and purpose.

How to use the tool and how it works

  1. Enter recordId, purposeWording, permissionRecorded. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read permissionToken. Use the output convention below.

Require recordId and purposeWording nonempty; serialize [recordId,purposeWording,permissionRecorded] as JSON text.1

Input fieldMeaning and unitsAccepted input
recordIdRecord IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
purposeWordingPurpose WordingRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
permissionRecordedPermission RecordedRequired. Boolean.
Output fieldInterpretationReturned shape
permissionTokenPermission TokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "recordId": "R17",
    "purposeWording": "analysis",
    "permissionRecorded": true
  },
  "output": {
    "permissionToken": "[\"R17\",\"analysis\",true]"
  }
}

Limitations and assumptions

  • A boolean records an assertion without checking scope, voluntariness, identity, lawful basis or permission for actual recording or reuse.
  • 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

  1. Calculation and input contract: bioethics/consent-audio-recording-permission-field — tool.io

Similar or alternative tools