Description
Isolate the effect of a supplied coverage-denominator change with the numerator held fixed.
A policy scenario makes eligibility bases, rates, thresholds, periods, and costs explicit. A calculated share or balance follows those assumptions. It does not select the governing policy or establish what caused an observed program outcome.
Isolate the effect of a supplied coverage-denominator change with the numerator held fixed.
When to use this tool
Use it for policy coverage denominator change when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter covered, oldDenominator, newDenominator. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read oldShare, newShare, shareChange. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require positive integer oldDenominator and newDenominator and a nonnegative integer covered count no greater than either. Return both shares and shareChange=newShare-oldShare.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| covered | Covered | Required. Safe integer; minimum 0. |
| oldDenominator | Old Denominator | Required. Safe integer; minimum 1. |
| newDenominator | New Denominator | Required. Safe integer; minimum 1. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| oldShare | Old Share | Required. Finite number. |
| newShare | New Share | Required. Finite number. |
| shareChange | Share Change | Required. Finite number. |
{
"input": {
"covered": 40,
"oldDenominator": 100,
"newDenominator": 80
},
"output": {
"oldShare": 0.4,
"newShare": 0.5,
"shareChange": 0.09999999999999998
}
} Limitations and assumptions
- Covered stays fixed, so the change isolates denominator arithmetic rather than a change in service delivery. ShareChange is a fraction, not percentage points until multiplied by 100.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For policy coverage denominator change, check the source records and the supplied rule before comparing the result with another method. Consult the applicable authoritative rule when deciding eligibility, legal timing, fees, or obligations.
References
Similar or alternative tools
- Policy Coverage Gap One Group
Calculate policy coverage gap one group from explicit caller-supplied inputs.
- Policy Band Boundary Distance
Calculate policy band boundary distance from explicit caller-supplied inputs.