Skip to content

Main content

Consent Purpose Cardinality Gap Tool

Calculate consent purpose cardinality gap from explicit caller-supplied inputs.

Loading tool…

Description

Return consent-purpose counts and requested omissions.

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.

Return consent-purpose counts and requested omissions.

When to use this tool

Use Consent Purpose Cardinality Gap when checking the stated permission, disclosure, timing or ethical-review record convention.

How to use the tool and how it works

  1. Enter requestedPurposes, consentedPurposes. 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 requestedCount, consentedCount, missingCount. Use the output convention below.

Return consent-purpose counts and requested omissions. Count distinct requested and consented labels, missingCount is distinct requested purposes absent from consented.1

Input fieldMeaning and unitsAccepted input
requestedPurposesRequested PurposesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
consentedPurposesConsented PurposesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
requestedCountRequested CountRequired. Safe integer.
consentedCountConsented CountRequired. Safe integer.
missingCountMissing CountRequired. Safe integer.
json
{
  "input": {
    "requestedPurposes": [
      "a",
      "b"
    ],
    "consentedPurposes": [
      "b",
      "c"
    ]
  },
  "output": {
    "requestedCount": 2,
    "consentedCount": 2,
    "missingCount": 1
  }
}

Limitations and assumptions

  • Counts do not establish informed consent, semantic purpose compatibility, withdrawal status or lawful processing.
  • 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/consent-purpose-cardinality-gap — tool.io

Similar or alternative tools