Skip to content

Main content

Neonatal Record Consent Scope Intersection Tool

Intersect supplied scope tokens with explicit withdrawal flags.

Loading tool…

Description

Reject duplicate entries within either scope list.

Recorded permissions are metadata with a declared scope, purpose, audience, and withdrawal status. Boolean consistency checks can expose gaps without establishing valid authorization.

Reject duplicate entries within either scope list.

When to use this tool

Use Neonatal Record Consent Scope Intersection when you need to compare supplied permission or disclosure records.

How to use the tool and how it works

  1. Enter firstScopes, secondScopes, firstWithdrawn, secondWithdrawn. Keep parallel arrays aligned. 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 shared, usable. Use the output convention below.

Reject duplicate entries within either scope list. Intersect them in firstScopes order; usable is that intersection unless either withdrawal flag is true, in which case it is empty.1

Input fieldMeaning and unitsAccepted input
firstScopesFirst ScopesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
secondScopesSecond ScopesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
firstWithdrawnFirst WithdrawnRequired. Boolean.
secondWithdrawnSecond WithdrawnRequired. Boolean.
Output fieldInterpretationReturned shape
sharedSharedRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
usableUsableRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
json
{
  "input": {
    "firstScopes": [
      "research",
      "audit"
    ],
    "secondScopes": [
      "research"
    ],
    "firstWithdrawn": false,
    "secondWithdrawn": false
  },
  "output": {
    "shared": [
      "research"
    ],
    "usable": [
      "research"
    ]
  }
}

Limitations and assumptions

  • Scopes and withdrawal flags are supplied assertions; string intersection does not determine lawful consent or permitted data use.
  • 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 the original consent record and applicable policy with the responsible professional before relying on a permission flag.

References

  1. Calculation and input contract: neonatology/neonatal-record-consent-scope-intersection — tool.io

Similar or alternative tools