Description
Either cap eligibleAmount before applying the fraction or cap the resulting member amount, according to capBeforeShare.
Health-benefit calculations depend on explicit eligibility flags, coverage periods, caps, exclusions, and payment order. Applying supplied arithmetic is separate from determining actual insurance terms or a legally payable claim.
Either cap eligibleAmount before applying the fraction or cap the resulting member amount, according to capBeforeShare.
When to use this tool
Use Claim Coinsurance Cap Order when you need one transparent benefit or reimbursement component under a declared rule.
How to use the tool and how it works
- Enter eligibleAmount, memberFraction, capAmount, capBeforeShare. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read memberAmount. Use the output convention below.
Require nonnegative eligibleAmount and capAmount and memberFraction in [0, 1]. Either cap eligibleAmount before applying the fraction or cap the resulting member amount, according to capBeforeShare.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| eligibleAmount | Eligible Amount | Required. Finite number; minimum 0. |
| memberFraction | Member Fraction | Required. Finite number; minimum 0; maximum 1. |
| capAmount | Cap Amount | Required. Finite number; minimum 0. |
| capBeforeShare | Cap Before Share | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| memberAmount | Member Amount | Required. Finite number. |
{
"input": {
"eligibleAmount": 1000,
"memberFraction": 0.2,
"capAmount": 100,
"capBeforeShare": true
},
"output": {
"memberAmount": 20
}
}Limitations and assumptions
- The operation order changes the result; policy order, claim eligibility, insurer liability, and monetary rounding are supplied or assessed separately.
- 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. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Confirm policy terms, verified enrollment, claim eligibility, and appropriate accounting or legal interpretation before relying on a payment result.
References
Similar or alternative tools
- Deductible Coinsurance Order One Bill
Apply deductible first, then coinsurance to the excess, limiting patient payments by remainingOutOfPocket and assigning the remainder to insurerPaid.
- Insurance Copayment Cap One Claim Term
When covered, patientPaid is their minimum and insurerPaid is the remainder, with cap reduced by patientPaid; otherwise patient pays allowed and cap is unchanged.