Skip to content

Main content

Form Version Source Gap Tool

Compare literal research form source/version metadata without certifying a document.

Loading tool…

Description

Compare expected and actual form source/version labels.

Clinical research distinguishes supplied protocol metadata, participant/event records, allocation bookkeeping and an analysis target. A local count, permission flag or denominator choice can help reconcile records without establishing valid consent, randomization, regulatory compliance or a reliable treatment-effect estimate.

Compare expected and actual form source/version labels.

When to use this tool

Use Form Version Source Gap when checking the stated clinical-research record, allocation, timing, analysis or evidence-basis convention.

How to use the tool and how it works

  1. Enter expectedSource, actualSource, expectedVersion, actualVersion. 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 sameSource, sameVersion, exactMatch. Inspect sameSource, sameVersion, exactMatch before interpreting the associated values.

Compare expected and actual form source/version labels. sameSource and sameVersion use literal equality, exactMatch requires both.1

Input fieldMeaning and unitsAccepted input
expectedSourceExpected SourceRequired. Text; maximum UTF-16 length 8192.
actualSourceActual SourceRequired. Text; maximum UTF-16 length 8192.
expectedVersionExpected VersionRequired. Text; maximum UTF-16 length 8192.
actualVersionActual VersionRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
sameSourceSame SourceRequired. Boolean.
sameVersionSame VersionRequired. Boolean.
exactMatchExact MatchRequired. Boolean.
json
{
  "input": {
    "expectedSource": "A",
    "actualSource": "A",
    "expectedVersion": "v2",
    "actualVersion": "v1"
  },
  "output": {
    "sameSource": true,
    "sameVersion": false,
    "exactMatch": false
  }
}

Limitations and assumptions

  • Matching metadata does not verify form contents, approval, current applicability or authentic provenance.
  • 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

Use the complete approved protocol, authenticated source records and qualified clinical/statistical oversight for actual trial design, conduct and interpretation.

References

  1. Calculation and input contract: clinical-research/form-version-source-gap — tool.io

Similar or alternative tools