Description
Count consent coverage for distinct required purposes.
Consent, privacy and retention records encode supplied purposes, audiences, withdrawal status and timing rules. Literal membership or a true local predicate can organize these assertions while valid informed consent, adequate de-identification and lawful processing require separate contextual assessment.
Count consent coverage for distinct required purposes.
When to use this tool
Use Consent Explicit Purpose Count when checking the stated permission, withdrawal, retention or disclosure-record convention.
How to use the tool and how it works
- Enter requiredPurposes, explicitlyConsented, withdrawn. Follow any array-alignment requirements below. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read covered, missing, withdrawnRequired. Use the output convention below.
Count consent coverage for distinct required purposes. A required purpose is missing if not explicitly consented or withdrawn; return covered, missing and withdrawnRequired counts.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| requiredPurposes | Required Purposes | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| explicitlyConsented | Explicitly Consented | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| withdrawn | Withdrawn | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| covered | Covered | Required. Safe integer. |
| missing | Missing | Required. Safe integer. |
| withdrawnRequired | Withdrawn Required | Required. Safe integer. |
{
"input": {
"requiredPurposes": [
"A",
"B"
],
"explicitlyConsented": [
"A",
"B"
],
"withdrawn": [
"B"
]
},
"output": {
"covered": 1,
"missing": 1,
"withdrawnRequired": 1
}
}Limitations and assumptions
- Withdrawal overrides a listed grant; assertions do not establish consent validity or authorize actual 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 original permissions, participant choices and applicable organizational/legal requirements with the responsible professionals before actual use, disclosure or deletion.
References
Similar or alternative tools
- Consent Scope Purpose Subsumption
Check requested purposes against granted and expressly excluded labels.
- Consent Recontact Scope Flag
Check a requested recontact purpose and knowledge flags.