Gynecologic Study Contact Consent Match Tool

Description

Compare them with supplied permitted lists, test expiry under inclusive, and set eligible only when active and all comparisons pass.

Gynecologic research and care records can contain specimen labels, questionnaire states, source keys, and consent flags. A local metadata check preserves a supplied convention without determining a clinical finding or verifying permission.

Compare them with supplied permitted lists, test expiry under inclusive, and set eligible only when active and all comparisons pass.

When to use this tool

Use Gynecologic Study Contact Consent Match when you need one explicit research-record or permission-metadata component.

How to use the tool and how it works

Enter purposes, channels, purpose, channel, active, day, expiryDay, inclusive. Keep parallel arrays aligned. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read purposeMatch, channelMatch, unexpired, eligible. Inspect purposeMatch, channelMatch, unexpired, eligible before interpreting the associated values.

Require nonempty purpose and channel. Compare them with supplied permitted lists, test expiry under inclusive, and set eligible only when active and all comparisons pass.^[1]

Input field	Meaning and units	Accepted input
purposes	Purposes	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
channels	Channels	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
purpose	Purpose	Required. Text; maximum UTF-16 length 8192.
channel	Channel	Required. Text; maximum UTF-16 length 8192.
active	Active	Required. Boolean.
day	Numeric day coordinate; not a parsed calendar date unless stated above.	Required. Safe integer.
expiryDay	Supplied numeric expiry-day coordinate; endpoint inclusion follows the stated rule.	Required. Safe integer.
inclusive	Inclusive	Required. Boolean.

Output field	Interpretation	Returned shape
purposeMatch	Purpose Match	Required. Boolean.
channelMatch	Channel Match	Required. Boolean.
unexpired	Unexpired	Required. Boolean.
eligible	Eligible	Required. Boolean.

json

{
  "input": {
    "purposes": [
      "followup"
    ],
    "channels": [
      "email"
    ],
    "purpose": "followup",
    "channel": "email",
    "active": true,
    "day": 100,
    "expiryDay": 110,
    "inclusive": false
  },
  "output": {
    "purposeMatch": true,
    "channelMatch": true,
    "unexpired": true,
    "eligible": true
  }
}

Limitations and assumptions

The result reflects supplied consent metadata rather than proving informed consent, current permission, legal authority, or that contact is safe.
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 verified records, privacy and consent requirements, and appropriate professional interpretation before clinical or contact decisions.

References

Calculation and input contract: gynecology/gynecologic-study-contact-consent-match — tool.io

Similar or alternative tools

Health Diary Safe Contact Time Window
Test start-inclusive/end-exclusive membership, allowing wrap across midnight; equal endpoints define an empty window.
Authorized Item Access Scope
Check requestedPurpose against allowedPurposes.