Skip to content

Main content

Star Allele Token Parser

Split a supplied numeric star-allele label into its number and optional suballele text without recognizing an allele definition.

Loading tool…

Description

Split a restricted star-allele token into allele and optional suballele text.

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.

Split a restricted star-allele token into allele and optional suballele text.

When to use this tool

Use Star Allele Token Parser when you already have alleleToken and need to split a restricted star-allele token into allele and optional suballele text.

How to use the tool and how it works

  1. Enter alleleToken. 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 alleleNumberText, suballeleText. Use the output convention below.

Require * followed by a nonzero-leading decimal integer, optionally a dot and one or more digits. Remove * and split once at the dot; absent suballele returns empty text.1

Input fieldMeaning and unitsAccepted input
alleleTokenAllele TokenRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
alleleNumberTextMain allele number retained as text; no gene-specific registry validation.Required. Text; maximum UTF-16 length 8192.
suballeleTextDigits after the dot, preserving zeros, or empty text when omitted.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "alleleToken": "*4.001"
  },
  "output": {
    "alleleNumberText": "4",
    "suballeleText": "001"
  }
}

Limitations and assumptions

  • Allele numbers remain text and suballele zeros are preserved; no gene, registry, valid allele designation, diplotype or phenotype is resolved.
  • 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/star-allele-token-parser — tool.io

Similar or alternative tools