Own Occ vs Any Occ Definition Lookup
Compare actual duty-ability annotations against caller own/any-occupation required-duty maps with explicit unknowns; no inferred income/vocational skills or disability diagnosis/benefit eligibility.
Description
Own-occupation and any-occupation definitions can require different duty sets.
Own-occupation and any-occupation definitions can require different duty sets. An evidence audit separates known inability from unknown ability.1
The returned values include Caller own occ unmet duty ids, Caller any occ unmet duty ids, Unknown duty ability ids. The How section below explains the calculation, input rules and interpretation.
When to use Own Occ vs Any Occ Definition Lookup
Use Own Occ vs Any Occ Definition Lookup when you need to evaluate the supplied records under the calculation and evidence rules below. No occupation classification, income/vocational inference, diagnosis or disability entitlement is supplied.
Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.
How to use Own Occ vs Any Occ Definition Lookup and understand its results
- Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.
- Enter callerDutyIds, callerOwnOccupationRequiredDutyFlags, callerAnyOccupationRequiredDutyFlags, observedDutyAbilityFlags, dutyAbilityEvidenceFlags using the field table and calculation rules, then run the tool.
- Read callerOwnOccUnmetDutyIds, callerAnyOccUnmetDutyIds, unknownDutyAbilityIds. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| callerDutyIds | Caller duty ids | list of string | Required |
| callerOwnOccupationRequiredDutyFlags | Caller own occupation required duty flags | list of number | Required |
| callerAnyOccupationRequiredDutyFlags | Caller any occupation required duty flags | list of number | Required |
| observedDutyAbilityFlags | Observed duty ability flags | list of number | Required |
| dutyAbilityEvidenceFlags | Duty ability evidence flags | list of number | Required |
Enter aligned nonempty unique nonblank duty IDs and binary own-required, any-required, ability and evidence flags. Return each requirement set’s known unmet IDs and every unknown-ability ID.
unmetSet=required duties with evidence1 and ability0; unknownSet=duties with evidence0 Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| callerOwnOccUnmetDutyIds | Caller own occ unmet duty ids | list of string |
| callerAnyOccUnmetDutyIds | Caller any occ unmet duty ids | list of string |
| unknownDutyAbilityIds | Unknown duty ability ids | list of string |
{
"input": {
"callerDutyIds": [
"a",
"b"
],
"callerOwnOccupationRequiredDutyFlags": [
1,
0
],
"callerAnyOccupationRequiredDutyFlags": [
1,
1
],
"observedDutyAbilityFlags": [
1,
0
],
"dutyAbilityEvidenceFlags": [
1,
1
]
},
"output": {
"callerOwnOccUnmetDutyIds": [],
"callerAnyOccUnmetDutyIds": [
"b"
],
"unknownDutyAbilityIds": []
}
} Limitations and assumptions
No occupation classification, income/vocational inference, diagnosis or disability entitlement is supplied.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Benefit Period To Age Options Lookup: Benefit-to-age options compare remaining years with a requested horizon. Expired options have zero remaining years. For a complementary task, use Elimination Period Benefit Gap Days Calculator: An elimination period may count qualifying days cumulatively or require an uninterrupted run. Both observed counts help explain the outcome.
References
-
Own Occ vs Any Occ Definition Lookup — tool.io
Similar or alternative tools
- Benefit Period To Age Options Lookup
Benefit-to-age options compare remaining years with a requested horizon. Expired options have zero remaining years.
- Elimination Period Benefit Gap Days Calculator
An elimination period may count qualifying days cumulatively or require an uninterrupted run. Both observed counts help explain the outcome.