Description
Check a supplied withdrawal boundary and prior approval.
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 supplied withdrawal boundary and prior approval.
When to use this tool
Use Biobank Consent Withdrawal Use Boundary when checking the stated permission, withdrawal, retention or disclosure-record convention.
How to use the tool and how it works
- Enter useDay, withdrawalDay, withdrawn, equalityBlocked, previouslyApproved. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read afterBoundary, permittedUnderFlags. Inspect afterBoundary, permittedUnderFlags before interpreting the associated values.
Check a supplied withdrawal boundary and prior approval. afterBoundary requires withdrawn and useDay >= withdrawalDay when equalityBlocked, otherwise >; permittedUnderFlags = previouslyApproved and not afterBoundary.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| useDay | Use Day | Required. Safe integer. |
| withdrawalDay | Withdrawal Day | Required. Safe integer. |
| withdrawn | Withdrawn | Required. Boolean. |
| equalityBlocked | Equality Blocked | Required. Boolean. |
| previouslyApproved | Previously Approved | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| afterBoundary | After Boundary | Required. Boolean. |
| permittedUnderFlags | Permitted Under Flags | Required. Boolean. |
{
"input": {
"useDay": 100,
"withdrawalDay": 100,
"withdrawn": true,
"equalityBlocked": true,
"previouslyApproved": true
},
"output": {
"afterBoundary": true,
"permittedUnderFlags": false
}
}Limitations and assumptions
- The boundary policy is supplied; consent validity, retroactivity, legal rights and actual specimen use are not decided.
- 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 Pseudonym Release Scope Check
Check a pseudonymized release record against supplied purpose/audience flags.
- Consent Purpose Expiry Gap
Return purpose membership and uncertain expiry flags independently.