Skip to content

Main content

Biobank Pseudonym Release Scope Check Tool

Check supplied release-purpose/audience and pseudonym/withdrawal flags.

Loading tool…

Description

Check a pseudonymized release record against supplied purpose/audience 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 pseudonymized release record against supplied purpose/audience flags.

When to use this tool

Use Biobank Pseudonym Release Scope Check when checking the stated permission, withdrawal, retention or disclosure-record convention.

How to use the tool and how it works

  1. Enter recordPurpose, permittedPurposes, audience, permittedAudiences, pseudonymPresent, withdrawn. 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 scopeMatches, eligibleUnderFlags. Inspect scopeMatches, eligibleUnderFlags before interpreting the associated values.

Check a pseudonymized release record against supplied purpose/audience flags. scopeMatches needs both memberships, eligibleUnderFlags also requires pseudonymPresent and no withdrawal.1

Input fieldMeaning and unitsAccepted input
recordPurposeRecord PurposeRequired. Text; maximum UTF-16 length 8192.
permittedPurposesPermitted PurposesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
audienceAudienceRequired. Text; maximum UTF-16 length 8192.
permittedAudiencesPermitted AudiencesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
pseudonymPresentPseudonym PresentRequired. Boolean.
withdrawnWithdrawnRequired. Boolean.
Output fieldInterpretationReturned shape
scopeMatchesScope MatchesRequired. Boolean.
eligibleUnderFlagsPurpose/audience match, asserted pseudonym present and no withdrawal; not authorization or anonymization.Required. Boolean.
json
{
  "input": {
    "recordPurpose": "study",
    "permittedPurposes": [
      "study"
    ],
    "audience": "team",
    "permittedAudiences": [
      "team"
    ],
    "pseudonymPresent": true,
    "withdrawn": false
  },
  "output": {
    "scopeMatches": true,
    "eligibleUnderFlags": true
  }
}

Limitations and assumptions

  • A pseudonym flag does not prove anonymity, valid consent or lawful disclosure; no release is performed.
  • 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

  1. Calculation and input contract: biobanking/biobank-pseudonym-release-scope-check — tool.io

Similar or alternative tools