Skip to content

Main content

Pharmacogenomic Test Method Label

Preserve an explicit pharmacogenomic test-method label without inferring assay coverage or performance.

Loading tool…

Description

Preserve an explicit pharmacogenomic test-method label.

Pharmacogenomic records require a gene, reference build, version, assay method and stated allele/phasing convention. A star-allele string is not meaningful independently of its gene and authoritative definition. Syntax, separator and copy-count labels do not establish a genotype, phenotype, assay coverage or appropriate prescribing recommendation.

Preserve an explicit pharmacogenomic test-method label.

When to use this tool

Use Pharmacogenomic Test Method Label when you already have testId, methodWording, source and need to preserve an explicit pharmacogenomic test-method label.

How to use the tool and how it works

  1. Enter testId, methodWording, source. 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 token. Use the output convention below.

Enter testId, methodWording, source using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1

Input fieldMeaning and unitsAccepted input
testIdTest IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
methodWordingMethod WordingRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
sourceSourceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "testId": "T17",
    "methodWording": "targeted panel",
    "source": "Lab A"
  },
  "output": {
    "token": "[\"T17\",\"targeted panel\",\"Lab A\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without inferring assay coverage or performance. Sources and asserted relationships are not independently authenticated.
  • 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

Resolve allele definitions against the correct gene, reference build, assay scope and authoritative version. Treat syntax parsing and no-call/phasing labels as record checks; applying a clinical guideline requires the complete verified genetic and clinical context.

References

  1. Calculation and input contract: pharmacogenomics/pharmacogenomic-test-method-label — tool.io

Similar or alternative tools