Insurance Copayment Cap One Claim Term Tool

Description

When covered, patientPaid is their minimum and insurerPaid is the remainder, with cap reduced by patientPaid; otherwise patient pays allowed and cap is unchanged.

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.

When covered, patientPaid is their minimum and insurerPaid is the remainder, with cap reduced by patientPaid; otherwise patient pays allowed and cap is unchanged.

When to use this tool

Use Insurance Copayment Cap One Claim Term when you need one transparent benefit or reimbursement component under a declared rule.

How to use the tool and how it works

Enter allowed, copay, remainingCap, covered. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read patientPaid, insurerPaid, capRemaining. Use the output convention below.

Require nonnegative allowed, copay, and remainingCap. When covered, patientPaid is their minimum and insurerPaid is the remainder, with cap reduced by patientPaid; otherwise patient pays allowed and cap is unchanged.^[1]

Input field	Meaning and units	Accepted input
allowed	Allowed	Required. Finite number; minimum 0.
copay	Copay	Required. Finite number; minimum 0.
remainingCap	Remaining Cap	Required. Finite number; minimum 0.
covered	Covered	Required. Boolean.

Output field	Interpretation	Returned shape
patientPaid	Patient Paid	Required. Finite number.
insurerPaid	Insurer Paid	Required. Finite number.
capRemaining	Cap Remaining	Required. Finite number.

json

{
  "input": {
    "allowed": 100,
    "copay": 25,
    "remainingCap": 15,
    "covered": true
  },
  "output": {
    "patientPaid": 15,
    "insurerPaid": 85,
    "capRemaining": 0
  }
}

Limitations and assumptions

This is one supplied copayment model rather than actual adjudication, deductible processing, exclusions, or a legally binding allocation.
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

Calculation and input contract: health-policy/insurance-copayment-cap-one-claim-term — tool.io

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.
Claim Coinsurance Cap Order
Either cap eligibleAmount before applying the fraction or cap the resulting member amount, according to capBeforeShare.