Description
Compare supplied source-version tokens and resolved day indices without clinical guideline interpretation.
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.
Compare supplied source-version tokens and resolved day indices without clinical guideline interpretation.
When to use this tool
Use Guideline Source Version Dategap 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 firstVersion, secondVersion, firstDay, secondDay. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read sameVersion, dayGap. Inspect sameVersion before interpreting the associated values.
Return sameVersion on exact firstVersion/secondVersion equality and dayGap=secondDay-firstDay.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstVersion | First Version | Required. Text; maximum UTF-16 length 8192. |
| secondVersion | Second Version | Required. Text; maximum UTF-16 length 8192. |
| firstDay | First numeric day coordinate, not a parsed calendar date. | Required. Safe integer. |
| secondDay | Second numeric day coordinate on the same origin. | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| sameVersion | Same Version | Required. Boolean. |
| dayGap | Day Gap | Required. Safe integer. |
{
"input": {
"firstVersion": "v1",
"secondVersion": "v2",
"firstDay": 100,
"secondDay": 130
},
"output": {
"sameVersion": false,
"dayGap": 30
}
}Limitations and assumptions
- Days are supplied numeric day coordinates rather than parsed calendar dates. Version equality and age do not establish guideline currency, authority, allele interpretation, or applicability to a patient.
- 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
Similar or alternative tools
- 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.
- Drug Code Vintage Gap
Compare supplied deidentified vocabulary vintage years without resolving a drug code.