Skip to content

Main content

GCP Training Protocol Version Match Tool

Compare supplied staff training versions to an explicit protocol version.

Loading tool…

Description

Partition IDs by exact equality with requiredVersion.

Good clinical practice record checks compare supplied versions, language labels, roles, dates, and source links. A local metadata match can reveal consistency but does not establish valid consent, competent authorization, or regulatory compliance.

Partition IDs by exact equality with requiredVersion.

When to use this tool

Use GCP Training Protocol Version Match when you need a literal clinical-trial metadata consistency check.

How to use the tool and how it works

  1. Enter staffIds, trainedVersions, requiredVersion. Keep parallel arrays aligned. 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 matchedIds, mismatchedIds. Use the output convention below.

Require equally long staffIds and trainedVersions with unique staff IDs. Partition IDs by exact equality with requiredVersion.1

Input fieldMeaning and unitsAccepted input
staffIdsStaff IdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
trainedVersionsTrained VersionsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
requiredVersionRequired VersionRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
matchedIdsMatched IdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
mismatchedIdsMismatched IdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
json
{
  "input": {
    "staffIds": [
      "A",
      "B"
    ],
    "trainedVersions": [
      "v1",
      "v2"
    ],
    "requiredVersion": "v2"
  },
  "output": {
    "matchedIds": [
      "B"
    ],
    "mismatchedIds": [
      "A"
    ]
  }
}

Limitations and assumptions

  • Version equality does not verify training completion, competence, effective dates, delegation, or protocol authorization. Identifiers and versions are compared as supplied strings.
  • 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 the complete controlled trial records and applicable professional process. Verify authenticity, protocol scope, consent, competence, and effective versions through the appropriate responsible reviewers.

References

  1. Calculation and input contract: gcp/gcp-training-protocol-version-match — tool.io

Similar or alternative tools

  • GCP Consent Version Visit Date Order

    Compare consentVersion exactly with requiredVersion, test signedDay no later than visitDay and no earlier than versionEffectiveDay, and return recordMatches only when all checks pass and withdrawn is false.

  • Consent Language Version Gap

    Find the requested language exactly, return known status, compare its required version, and otherwise use an empty expectedVersion with versionMatches false.