Consent Language Support Share Tool

Description

Count distinct participants and distinct IDs with at least one row matching both language and version; divide the latter by the former or return zero with defined false when empty.

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.

Count distinct participants and distinct IDs with at least one row matching both language and version; divide the latter by the former or return zero with defined false when empty.

When to use this tool

Use Consent Language Support Share when you need a literal clinical-trial metadata consistency check.

How to use the tool and how it works

Enter participantIds, preferredLanguages, consentLanguages, consentVersions, requiredVersions. 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 participants, languageAndVersionSupported, share, defined. Inspect defined before interpreting the associated values.

Require parallel participant, preferred-language, consent-language, consent-version, and required-version arrays. Count distinct participants and distinct IDs with at least one row matching both language and version; divide the latter by the former or return zero with defined false when empty.^[1]

Input field	Meaning and units	Accepted input
participantIds	Participant Ids	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
preferredLanguages	Preferred Languages	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
consentLanguages	Consent Languages	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
consentVersions	Consent Versions	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
requiredVersions	Required Versions	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.

Output field	Interpretation	Returned shape
participants	Participants	Required. Safe integer.
languageAndVersionSupported	Distinct participant IDs with at least one row matching language and version.	Required. Safe integer.
share	Dimensionless share on the numerator and denominator basis stated above.	Required. Finite number.
defined	Whether the stated denominator or normalization exists; inspect before interpreting a zero placeholder.	Required. Boolean.

json

{
  "input": {
    "participantIds": [
      "p1",
      "p2"
    ],
    "preferredLanguages": [
      "en",
      "fr"
    ],
    "consentLanguages": [
      "en",
      "en"
    ],
    "consentVersions": [
      "v2",
      "v2"
    ],
    "requiredVersions": [
      "v2",
      "v2"
    ]
  },
  "output": {
    "participants": 2,
    "languageAndVersionSupported": 1,
    "share": 0.5,
    "defined": true
  }
}

Limitations and assumptions

Any matching row supports a participant even if another row conflicts, and duplicates do not increase distinct counts. Exact metadata matches are not evidence of comprehension or valid informed consent; the zero share needs its defined flag.
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

Calculation and input contract: gcp/consent-language-support-share — tool.io

Similar or alternative tools

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.
GCP Consent Language Document Pair
Return languageDirect for exact preferred/document language equality, interpretationMatched when interpreterUsed is true and interpreterLanguage exactly matches preference, and versionMatched for translation/required version equality.