Skip to content

Main content

GCP Reconsent Version Label

Qualify an explicit reconsent record by participant and version without deciding consent validity.

Loading tool…

Description

Identify a supplied clinical-research reconsent version.

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.

Identify a supplied clinical-research reconsent version.

When to use this tool

Use GCP Reconsent Version Label when checking the stated benign clinical-research record or date convention.

How to use the tool and how it works

  1. Enter participantId, consentVersion, reconsentRecordId. 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 participant ID, consent version and reconsent-record ID. Encode the ordered triple as JSON text.1

Input fieldMeaning and unitsAccepted input
participantIdParticipant IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
consentVersionConsent VersionRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
reconsentRecordIdReconsent Record IdRequired. 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": {
    "participantId": "P17",
    "consentVersion": "v2",
    "reconsentRecordId": "RC2"
  },
  "output": {
    "token": "[\"P17\",\"v2\",\"RC2\"]"
  }
}

Limitations and assumptions

  • No consent document is inspected and valid informed consent, actual reconsent or participant understanding is not established.
  • 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-reconsent-version-label — tool.io

Similar or alternative tools