Description
Check supplied model stage/version succession within an explicit case match.
Dental model and device records use coordinate frames, image scale, dimensions, force references, and observation schedules. A projection, gap, ratio, or metadata order checks a particular supplied representation. These local calculations do not establish a treatment plan or the clinical suitability of a device.
Check supplied model stage/version succession within an explicit case match.
When to use this tool
Use Orthodontic Record Stage Version Pair when you need this particular model geometry, device budget, observation share, or record comparison.
How to use the tool and how it works
- Enter stage, version, parentStage, parentVersion, sameCase. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read sameStage, laterVersion, followsParent. Inspect sameStage, laterVersion, followsParent before interpreting the associated values.
For nonnegative integer stage, version, parentStage, and parentVersion return sameStage, laterVersion=(version>parentVersion), and followsParent when sameCase and stage is later or the same stage has a later version.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| stage | Stage | Required. Safe integer; minimum 0. |
| version | Version | Required. Safe integer; minimum 0. |
| parentStage | Parent Stage | Required. Safe integer; minimum 0. |
| parentVersion | Parent Version | Required. Safe integer; minimum 0. |
| sameCase | Same Case | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| sameStage | Same Stage | Required. Boolean. |
| laterVersion | Numeric version comparison independent of case and stage. | Required. Boolean. |
| followsParent | Follows Parent | Required. Boolean. |
{
"input": {
"stage": 2,
"version": 3,
"parentStage": 2,
"parentVersion": 2,
"sameCase": true
},
"output": {
"sameStage": true,
"laterVersion": true,
"followsParent": true
}
}Limitations and assumptions
- LaterVersion is independent of stage and case, so it is not a complete ordering by itself. This compares supplied metadata rather than treatment progression, record authenticity, or clinical appropriateness.
- 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 validated measurement or device model and appropriate source records for the full task. Check coordinate systems, calibration, geometric assumptions, and observation denominators before interpreting the term.
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.
- Guideline Source Version Dategap
Compare supplied source-version tokens and resolved day indices without clinical guideline interpretation.