Description
Return purpose membership and uncertain expiry flags independently.
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.
Return purpose membership and uncertain expiry flags independently.
When to use this tool
Use Consent Purpose Expiry Gap when checking the stated permission, withdrawal, retention or disclosure-record convention.
How to use the tool and how it works
- Enter requestedPurpose, recordedPurposes, checkDay, expiryLower, expiryUpper, consentKnown. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read purposeListed, certainlyBeforeBoundary, ambiguousExpiry, consentUnresolved. Inspect purposeListed, certainlyBeforeBoundary, ambiguousExpiry, consentUnresolved before interpreting the associated values.
Return purpose membership and uncertain expiry flags independently. Require expiryLower <= expiryUpper; certainlyBeforeBoundary uses check < lower, ambiguousExpiry includes both bounds, consentUnresolved means not consentKnown.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| requestedPurpose | Requested Purpose | Required. Text; maximum UTF-16 length 8192. |
| recordedPurposes | Recorded Purposes | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| checkDay | Check Day | Required. Safe integer. |
| expiryLower | Expiry Lower | Required. Safe integer. |
| expiryUpper | Expiry Upper | Required. Safe integer. |
| consentKnown | Consent Known | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| purposeListed | Purpose Listed | Required. Boolean. |
| certainlyBeforeBoundary | Certainly Before Boundary | Required. Boolean. |
| ambiguousExpiry | checkDay lies within both endpoints of the supplied expiry envelope; independent of purpose membership and consent knowledge. | Required. Boolean. |
| consentUnresolved | Consent Unresolved | Required. Boolean. |
{
"input": {
"requestedPurpose": "research",
"recordedPurposes": [
"research"
],
"checkDay": 110,
"expiryLower": 100,
"expiryUpper": 120,
"consentKnown": true
},
"output": {
"purposeListed": true,
"certainlyBeforeBoundary": false,
"ambiguousExpiry": true,
"consentUnresolved": false
}
}Limitations and assumptions
- These independent flags are not a combined permission decision; no valid consent, expiry rule or actual specimen-use right is established.
- 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.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
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
- Biobank Consent Withdrawal Use Boundary
Check a supplied withdrawal boundary and prior approval.
- Biobank Pseudonym Release Scope Check
Check a pseudonymized release record against supplied purpose/audience flags.