Skip to content

Main content

Confidentiality Exception Scope Token Tool

Evaluate caller-supplied exception-purpose flags; does not establish confidentiality law or release records.

Loading tool…

Description

Check confidentiality purpose membership and a supplied exception.

Applied-ethics records capture supplied permissions, disclosures, criteria and time or cost assumptions. A checklist, Boolean condition or numerical margin can reveal a local inconsistency without determining ethical acceptability, valid consent or lawful authority. Context, evidence and the interests of affected people remain essential.

Check confidentiality purpose membership and a supplied exception.

When to use this tool

Use Confidentiality Exception Scope Token when checking the stated permission, disclosure, timing or ethical-review record convention.

How to use the tool and how it works

  1. Enter purpose, permitted, exceptionPurposes, exceptionAuthorized. Follow any array-alignment requirements below. 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 permittedByTokens, exceptionUsed. Inspect permittedByTokens, exceptionUsed before interpreting the associated values.

Check confidentiality purpose membership and a supplied exception. Normal permitted membership passes directly; exceptionUsed requires no normal permission, exceptionAuthorized and listed exception purpose; permittedByTokens combines them.1

Input fieldMeaning and unitsAccepted input
purposePurposeRequired. Text; maximum UTF-16 length 8192.
permittedPermittedRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
exceptionPurposesException PurposesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
exceptionAuthorizedException AuthorizedRequired. Boolean.
Output fieldInterpretationReturned shape
permittedByTokensPermitted By TokensRequired. Boolean.
exceptionUsedTrue only when ordinary permission is absent and an authorized exception-purpose match supplies permission.Required. Boolean.
json
{
  "input": {
    "purpose": "audit",
    "permitted": [
      "care"
    ],
    "exceptionPurposes": [
      "audit"
    ],
    "exceptionAuthorized": true
  },
  "output": {
    "permittedByTokens": true,
    "exceptionUsed": true
  }
}

Limitations and assumptions

  • No exception is authorized or disclosure performed; actual confidentiality duties and valid legal/ethical permission are not verified.
  • 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 original evidence, participant choices and governing requirements with the responsible ethics and professional teams for substantive decisions.

References

  1. Calculation and input contract: applied-ethics/confidentiality-exception-scope-token — tool.io

Similar or alternative tools