Skip to content

Main content

Referral Consent Scope Expiry Tool

Evaluate supplied purpose and expiry flags; no legal consent authority is inferred.

Loading tool…

Description

Evaluate supplied purpose and expiry flags; no legal consent authority is inferred.

Support-service records distinguish appointments, action times, review windows, consent annotations, and allocation of shared resources. A supplied flag or time margin can support bookkeeping while case evidence, professional judgment, and applicable obligations remain separate.

Evaluate supplied purpose and expiry flags; no legal consent authority is inferred.

When to use this tool

Use Referral Consent Scope Expiry when you need one explicit service-record, clock, consent-annotation, or resource-allocation check.

How to use the tool and how it works

  1. Enter purpose, allowedPurposes, withdrawn, queryDay, expiresDay, inclusive. 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, current, eligibleUnderFlags. Inspect scopeMatches, current, eligibleUnderFlags before interpreting the associated values.

Compare purpose with allowedPurposes and test current from not withdrawn and the selected inclusive or exclusive expiry rule. Return eligibleUnderFlags only when both scopeMatches and current.1

Input fieldMeaning and unitsAccepted input
purposePurposeRequired. Text; maximum UTF-16 length 8192.
allowedPurposesAllowed PurposesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
withdrawnWithdrawnRequired. Boolean.
queryDayQuery DayRequired. Safe integer.
expiresDayExpires DayRequired. Safe integer.
inclusiveInclusiveRequired. Boolean.
Output fieldInterpretationReturned shape
scopeMatchesScope MatchesRequired. Boolean.
currentCurrentRequired. Boolean.
eligibleUnderFlagsConjunction of supplied scope and expiry flags, not legal authorization.Required. Boolean.
json
{
  "input": {
    "purpose": "housing",
    "allowedPurposes": [
      "housing"
    ],
    "withdrawn": false,
    "queryDay": 10,
    "expiresDay": 10,
    "inclusive": true
  },
  "output": {
    "scopeMatches": true,
    "current": true,
    "eligibleUnderFlags": true
  }
}

Limitations and assumptions

  • No start date, capacity, informed-consent process, source authenticity, or governing law is checked. EligibleUnderFlags summarizes supplied conditions and is not an authorization to share information or act.
  • The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
  • 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. Signed zero is exported as zero.

Alternative or Complementary methods

Check source records, case context, and the applicable professional or legal requirements before using these flags or margins for a service decision.

References

  1. Calculation and input contract: social-work/referral-consent-scope-expiry — tool.io

Similar or alternative tools

  • Consent Review Window Remainder

    Track supplied consent-review scheduling metadata without deciding consent validity or extension authority.

  • Referral Available Window Share

    Intersect available and requested windows, return availableOverlap and its share of the requested window, and calculate durationSlack=overlap-requiredDuration.