Description
Qualify an explicit gene label by assembly and annotation namespace.
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.
Qualify an explicit gene label by assembly and annotation namespace.
When to use this tool
Use Pharmacogene Build Namespace when you already have geneLabel, assemblyLabel, annotationVersion and need to qualify an explicit gene label by assembly and annotation namespace.
How to use the tool and how it works
- Enter geneLabel, assemblyLabel, annotationVersion. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter geneLabel, assemblyLabel, annotationVersion 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 field | Meaning and units | Accepted input |
|---|---|---|
| geneLabel | Gene Label | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| assemblyLabel | Assembly Label | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| annotationVersion | Annotation Version | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"geneLabel": "GENE-A",
"assemblyLabel": "Assembly X",
"annotationVersion": "v2"
},
"output": {
"token": "[\"GENE-A\",\"Assembly X\",\"v2\"]"
}
}Limitations and assumptions
- The result records supplied values without mapping coordinates. 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
Similar or alternative tools
- Pharmacogene Reference Version Token
Qualify an explicit pharmacogene reference by version.
- Pharmacogenomic No Call Token
Preserve explicit no-call wording and its source.