Description
Combine supplied blinding-code access assertions.
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.
Combine supplied blinding-code access assertions.
When to use this tool
Use Trial Blinding Code Access Scope when checking the stated clinical-research record, allocation, timing, analysis or evidence-basis convention.
How to use the tool and how it works
- Enter role, permittedRoles, purpose, permittedPurposes, emergency, emergencyAuthorized. 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 roleAllowed, purposeAllowed, emergencyOverride, accessible. Inspect roleAllowed, purposeAllowed, emergencyOverride, accessible before interpreting the associated values.
Combine supplied blinding-code access assertions. roleAllowed and purposeAllowed test vocabularies, emergencyOverride requires emergency AND emergencyAuthorized; accessible means both ordinary permissions or the override.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| role | Role | Required. Text; maximum UTF-16 length 8192. |
| permittedRoles | Permitted Roles | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| purpose | Purpose | Required. Text; maximum UTF-16 length 8192. |
| permittedPurposes | Permitted Purposes | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| emergency | Emergency | Required. Boolean. |
| emergencyAuthorized | Emergency Authorized | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| roleAllowed | Role Allowed | Required. Boolean. |
| purposeAllowed | Purpose Allowed | Required. Boolean. |
| emergencyOverride | Emergency Override | Required. Boolean. |
| accessible | Local assertion predicate only; no actual blinding-code access is granted. | Required. Boolean. |
{
"input": {
"role": "monitor",
"permittedRoles": [
"monitor"
],
"purpose": "audit",
"permittedPurposes": [
"audit"
],
"emergency": false,
"emergencyAuthorized": false
},
"output": {
"roleAllowed": true,
"purposeAllowed": true,
"emergencyOverride": false,
"accessible": true
}
}Limitations and assumptions
- No actual access is granted and asserted emergency authorization is not verified; blinding, privacy and clinical emergency decisions require appropriate procedures.
- 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
- Pharmacy Record Collection Authority Window
Combine collection identity, time window and revocation flags.
- Collection Authority Unknown Token
Combine supplied collection-authority and identity knowledge flags.