Description
Count distinct requested purposes present or absent in a supplied consent-support list.
Clinical research distinguishes supplied protocol metadata, participant/event records, allocation bookkeeping and an analysis target. A local count, permission flag or denominator choice can help reconcile records without establishing valid consent, randomization, regulatory compliance or a reliable treatment-effect estimate.
Count distinct requested purposes present or absent in a supplied consent-support list.
When to use this tool
Use Consent Purpose Support Count when checking the stated clinical-research record, allocation, timing, analysis or evidence-basis convention.
How to use the tool and how it works
- Enter requestedPurposes, supportedPurposes. 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 supportedCount, missingCount. Use the output convention below.
Count distinct requested purposes present or absent in a supplied consent-support list. Deduplicate requested labels after partitioning by literal membership.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| requestedPurposes | Requested Purposes | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| supportedPurposes | Supported Purposes | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| supportedCount | Distinct requested labels listed in supportedPurposes; no legal or informed-consent verification. | Required. Safe integer. |
| missingCount | Missing Count | Required. Safe integer. |
{
"input": {
"requestedPurposes": [
"a",
"b"
],
"supportedPurposes": [
"b"
]
},
"output": {
"supportedCount": 1,
"missingCount": 1
}
}Limitations and assumptions
- A listed purpose does not establish informed consent, lawful processing, withdrawal status or a participant's actual authorization.
- 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
Use the complete approved protocol, authenticated source records and qualified clinical/statistical oversight for actual trial design, conduct and interpretation.
References
Similar or alternative tools
- Trial Consent Reconsent Version Gap
Compare consent versions and signature timing.
- Research Instrument Edition Token
Qualify an explicit research instrument identifier by edition without scoring or validating an instrument.