Skip to content

Main content

Clinical Study Sample Matrix Code Pair Tool

Compare supplied sample-matrix codes under an explicit vocabulary.

Loading tool…

Description

Compare sample-matrix codes with a supplied vocabulary and expected code.

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 sample-matrix codes with a supplied vocabulary and expected code.

When to use this tool

Use Clinical Study Sample Matrix Code Pair 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 recordCode, labelCode, vocabulary, expectedCode. 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 recordKnown, labelKnown, pairMatches, expectedMatches. Inspect recordKnown, labelKnown, pairMatches, expectedMatches before interpreting the associated values.

Compare sample-matrix codes with a supplied vocabulary and expected code. recordKnown/labelKnown test membership, pairMatches compares both codes, expectedMatches requires both equal expectedCode.1

Input fieldMeaning and unitsAccepted input
recordCodeRecord CodeRequired. Text; maximum UTF-16 length 8192.
labelCodeLabel CodeRequired. Text; maximum UTF-16 length 8192.
vocabularyVocabularyRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
expectedCodeExpected CodeRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
recordKnownRecord KnownRequired. Boolean.
labelKnownLabel KnownRequired. Boolean.
pairMatchesPair MatchesRequired. Boolean.
expectedMatchesBoth codes equal expectedCode; this does not imply either code is present in vocabulary.Required. Boolean.
json
{
  "input": {
    "recordCode": "A",
    "labelCode": "A",
    "vocabulary": [
      "A",
      "B"
    ],
    "expectedCode": "A"
  },
  "output": {
    "recordKnown": true,
    "labelKnown": true,
    "pairMatches": true,
    "expectedMatches": true
  }
}

Limitations and assumptions

  • Expected agreement can coexist with unknown codes; no actual specimen identity, matrix suitability or vocabulary authority is verified.
  • 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/clinical-study-sample-matrix-code-pair — tool.io

Similar or alternative tools