Skip to content

Main content

Speech Audio Consent Token

Record an explicit speech-audio purpose and permission flag without determining consent validity.

Loading tool…

Description

Record an explicit speech-audio purpose and permission flag.

Speech records use different observational units: words, morphemes, tokens, time spans, frequency and symbol-code versions. A duration share differs from a count-based speech measure, and a transcription remains a supplied annotation. Recorded practice completion and communication preferences need their original assessment and consent context before clinical interpretation.

Record an explicit speech-audio purpose and permission flag.

When to use this tool

Use Speech Audio Consent Token when you already have recordingId, purposeCode, permissionRecorded and need to record an explicit speech-audio purpose and permission flag.

How to use the tool and how it works

  1. Enter recordingId, purposeCode, 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 token. Use the output convention below.

Enter recordingId, purposeCode, permissionRecorded 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. Boolean permission or verification fields are recorded assertions, not authorizations.1

Input fieldMeaning and unitsAccepted input
recordingIdRecording IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
purposeCodePurpose CodeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
permissionRecordedPermission RecordedRequired. Boolean.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "recordingId": "REC17",
    "purposeCode": "teaching",
    "permissionRecorded": true
  },
  "output": {
    "token": "[\"REC17\",\"teaching\",true]"
  }
}

Limitations and assumptions

  • The result records supplied values without determining consent validity. 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

Use the original audio, transcription and annotation manual when counts or intervals need verification. Apply a complete instrument's stated scoring method for an assessment; retain source-defined word, morpheme, time and symbol conventions throughout.

References

  1. Calculation and input contract: speech-therapy/speech-audio-consent-token — tool.io

Similar or alternative tools