Skip to content

Main content

Pharmacogene Phenotype Caller Rule Match Tool

Match supplied half-open phenotype-rule intervals without embedding clinical rules.

Loading tool…

Description

Match supplied half-open phenotype-rule intervals without embedding clinical rules.

Pharmacogenomic records distinguish allele labels, copy counts, reference-sequence versions, coordinate systems, and evidence about chromosome phase. A balanced count or matching token can check a record without establishing the underlying genotype. Supplied activity values and interpretation rules remain separate from a current gene-specific clinical guideline.

Match supplied half-open phenotype-rule intervals without embedding clinical rules.

When to use this tool

Use Pharmacogene Phenotype Caller Rule Match when you need this specific allele-token, reference-coordinate, copy-budget, or source-support check.

How to use the tool and how it works

  1. Enter activity, lower, upper, labels. 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 matches, ambiguous. Inspect ambiguous before interpreting the associated values.

Require aligned lower, upper, and labels arrays with each upper>=lower. Return every label whose interval satisfies lower<=activity<upper, and ambiguous when more than one interval matches.1

Input fieldMeaning and unitsAccepted input
activityActivityRequired. Finite number.
lowerInclusive lower endpoints for caller-supplied rule intervals.Required. Array of finite number; maximum items 256.
upperExclusive upper endpoints; equal endpoints form empty intervals.Required. Array of finite number; maximum items 256.
labelsLabelsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
matchesMatchesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
ambiguousMore than one rule row matches, even when labels repeat.Required. Boolean.
json
{
  "input": {
    "activity": 1,
    "lower": [
      0,
      1,
      2
    ],
    "upper": [
      1,
      2,
      3
    ],
    "labels": [
      "A",
      "B",
      "C"
    ]
  },
  "output": {
    "matches": [
      "B"
    ],
    "ambiguous": false
  }
}

Limitations and assumptions

  • Rules are supplied, overlaps and zero-width intervals are allowed, and no match is possible. Labels can repeat; this is not a current gene-specific clinical phenotype guideline lookup.
  • 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.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Signed zero is exported as zero.

Alternative or Complementary methods

Use a current gene-specific nomenclature and a validated interpretation process when allele identity, phase, function, or clinical decisions matter. Verify source versions and reference coordinates before combining records.

References

  1. Calculation and input contract: pharmacogenomics/pharmacogene-phenotype-caller-rule-match — tool.io

Similar or alternative tools