Skip to content

Main content

GCP Source Field Verification Tag

Preserve an explicit source-field verification tag without performing verification.

Loading tool…

Description

Record a supplied verification tag for a clinical-research source field.

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 a supplied verification tag for a clinical-research source field.

When to use this tool

Use GCP Source Field Verification Tag when checking the stated benign clinical-research record or date convention.

How to use the tool and how it works

  1. Enter recordId, sourceFieldId, verificationWording. 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 record ID, source-field ID and verification wording. Encode the ordered triple as JSON text.1

Input fieldMeaning and unitsAccepted input
recordIdNonempty caller-supplied record label; not independently resolved.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
sourceFieldIdSource Field IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
verificationWordingVerification WordingRequired. 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": {
    "recordId": "R17",
    "sourceFieldId": "F2",
    "verificationWording": "verified record"
  },
  "output": {
    "token": "[\"R17\",\"F2\",\"verified record\"]"
  }
}

Limitations and assumptions

  • Verification wording is an assertion, not source-data verification or a determination of GCP compliance.
  • 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-source-field-verification-tag — tool.io

Similar or alternative tools