Description
Check a requested recontact purpose and knowledge flags.
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.
Check a requested recontact purpose and knowledge flags.
When to use this tool
Use Consent Recontact Scope Flag when checking the stated permission, withdrawal, retention or disclosure-record convention.
How to use the tool and how it works
- Enter requestedPurpose, permittedPurposes, recontactKnown, recontactGranted. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read purposeListed, permittedUnderFlags, unresolved. Inspect purposeListed, permittedUnderFlags, unresolved before interpreting the associated values.
Check a requested recontact purpose and knowledge flags. purposeListed tests membership; permittedUnderFlags also requires recontactKnown and recontactGranted, unresolved means knowledge is absent.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| requestedPurpose | Requested Purpose | Required. Text; maximum UTF-16 length 8192. |
| permittedPurposes | Permitted Purposes | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| recontactKnown | Recontact Known | Required. Boolean. |
| recontactGranted | Recontact Granted | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| purposeListed | Purpose Listed | Required. Boolean. |
| permittedUnderFlags | Permitted Under Flags | Required. Boolean. |
| unresolved | Unresolved | Required. Boolean. |
{
"input": {
"requestedPurpose": "followup",
"permittedPurposes": [
"followup"
],
"recontactKnown": true,
"recontactGranted": true
},
"output": {
"purposeListed": true,
"permittedUnderFlags": true,
"unresolved": false
}
}Limitations and assumptions
- Known denial differs from unresolved status; no actual recontact permission, participant understanding or lawful use is 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
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 Intersection Size
Return the number of distinct scope labels shared by two consent lists.
- Consent Scope Purpose Subsumption
Check requested purposes against granted and expressly excluded labels.