Description
Count supplied locus-call and reference-matching support without phenotype or medication recommendations.
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.
Count supplied locus-call and reference-matching support without phenotype or medication recommendations.
When to use this tool
Use Genotype Panel Support Share when you need this specific allele-token, reference-coordinate, copy-budget, or source-support check.
How to use the tool and how it works
- Enter requiredLoci, calledLoci, referenceMatchedLoci. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read required, called, supported, share, defined. Inspect defined before interpreting the associated values.
Deduplicate requiredLoci, count those present in calledLoci, and count those also present in referenceMatchedLoci. Return required, called, supported, and share=supported/required when nonempty, otherwise zero with defined=false.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| requiredLoci | Required Loci | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| calledLoci | Called Loci | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| referenceMatchedLoci | Reference Matched Loci | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| required | Required | Required. Safe integer. |
| called | Called | Required. Safe integer. |
| supported | Supported | Required. Safe integer. |
| share | Dimensionless share under the stated denominator; not a percent numeral. | Required. Finite number. |
| defined | Whether the associated denominator or quantity is defined; read before using a zero placeholder. | Required. Boolean. |
{
"input": {
"requiredLoci": [
"a",
"b"
],
"calledLoci": [
"a",
"b"
],
"referenceMatchedLoci": [
"a"
]
},
"output": {
"required": 2,
"called": 2,
"supported": 1,
"share": 0.5,
"defined": true
}
}Limitations and assumptions
- Unexpected loci do not increase the numerator and support lists are trusted. This is locus coverage, not allele call accuracy, phase confidence, or completeness of a clinically relevant panel.
- 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 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
Similar or alternative tools
- Pharmacogenomic Assay Covered Variant Check
Audit explicitly supplied assay-coverage IDs without predicting assay sensitivity.
- Allele Source Edition Gap
Count rows with an edition different from requiredEdition, rows whose allele is absent from verifiedAlleles, and rows meeting both checks as fullySupported.