Skip to content

Main content

GCP Signature Authority Role

Qualify an explicit signature role by its authority source without authenticating a signature.

Loading tool…

Description

Record the stated authority role attached to a clinical-research signature.

Clinical-research records connect source fields, protocol dates, training, signatures, safety communications and consent versions. A recorded acknowledgment or date predicate does not establish valid consent, authorized delegation or compliance. Source documentation and substantive participant protections require separate review.

Record the stated authority role attached to a clinical-research signature.

When to use this tool

Use GCP Signature Authority Role when checking the stated benign clinical-research record or date convention.

How to use the tool and how it works

  1. Enter signatureRecordId, roleCode, authoritySource. 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 token. Use the output convention below.

Require nonempty signature-record ID, role code and authority source. Encode the ordered triple as JSON text.1

Input fieldMeaning and unitsAccepted input
signatureRecordIdSignature Record IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
roleCodeRole CodeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
authoritySourceAuthority SourceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenJSON-encoded ordered tuple or literal token under the convention above; not a database lookup or authentication result.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "signatureRecordId": "SIG17",
    "roleCode": "reviewer",
    "authoritySource": "Delegation record A"
  },
  "output": {
    "token": "[\"SIG17\",\"reviewer\",\"Delegation record A\"]"
  }
}

Limitations and assumptions

  • No signer identity, actual signature, delegation or lawful authority is authenticated.
  • 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 verified protocols, consent and source records under the applicable complete research requirements with qualified responsible personnel for actual study or participant decisions.

References

  1. Calculation and input contract: gcp/gcp-signature-authority-role — tool.io

Similar or alternative tools