This page (revision-37) was last changed on 26-Nov-2021 10:22 by rforbes

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
37 26-Nov-2021 10:22 20 KB rforbes to previous BSS_EVIDENCE_REQ(System_Preference) ==> BSS EVIDENCE REQ(System_Preference)
36 26-Nov-2021 10:22 20 KB jmyers to previous | to last BSS D REASON REQ ==> BSS D REASON REQ(System_Preference)
35 26-Nov-2021 10:22 20 KB jmyers to previous | to last BSS_EVIDENCE_REQ ==> BSS_EVIDENCE_REQ(System_Preference)
34 26-Nov-2021 10:22 20 KB jmyers to previous | to last
33 26-Nov-2021 10:22 20 KB jmyers to previous | to last
32 26-Nov-2021 10:22 20 KB jmyers to previous | to last
31 26-Nov-2021 10:22 29 KB jmyers to previous | to last
30 26-Nov-2021 10:22 32 KB jmyers to previous | to last
29 26-Nov-2021 10:22 35 KB jmyers to previous | to last
28 26-Nov-2021 10:22 37 KB jmyers to previous | to last
27 26-Nov-2021 10:22 37 KB jmyers to previous | to last
26 26-Nov-2021 10:22 38 KB jmyers to previous | to last
25 26-Nov-2021 10:22 39 KB jmyers to previous | to last
24 26-Nov-2021 10:22 43 KB jmyers to previous | to last
23 26-Nov-2021 10:22 43 KB jmyers to previous | to last
22 26-Nov-2021 10:22 43 KB jmyers to previous | to last
21 26-Nov-2021 10:22 43 KB jmyers to previous | to last

Page References

Incoming links Outgoing links
OPEN ENROLLMENT SET UP
OPEN ENROLLMENT SET UP

Version management

Difference between version and

At line 20 changed one line
A common requirement of benefit elections is that an employee is eligible to a set of plans that are offered from different carriers and are mutually exclusive of one another (the employee is only allowed to elect one plan from the set). The application is able to handle this requirement by grouping these plans into a “[Plan Election Set|PLAN_ELECTION_SET]”. A plan set code is used to group these plans together. The plan set code is user defined in a lexicon called [X_PLAN_ELECTION_SET] in [IMLN]. The plan set code should be reflective of the type of plans included in the set. The plan set code is then added to [IBPN] to each of the plans to be included in the set.
#A common requirement of benefit elections is that an employee is eligible to a set of plans that are offered from different carriers and are mutually exclusive of one another (the employee is only allowed to elect one plan from the set). The application is able to handle this requirement by grouping these plans into a “[Plan Election Set|PLAN_ELECTION_SET]”. A plan set code is used to group these plans together. The plan set code is user defined in a lexicon called [X_PLAN_ELECTION_SET] in [IMLN]. The plan set code should be reflective of the type of plans included in the set. The plan set code is then added to [IBPN] to each of the plans to be included in the set.
#Before employees can submit their elections, they may be prompted for a decline reason for the elections they declined. This decline reason is based on the lexicon [X_BE_DECLINE_REASON]. This is a user defined lexicon which clients should populate with suitable decline reasons, unless the client will not be requiring decline reasons in which case the lexicon does not need to be updated.
At line 22 removed one line
Before employees can submit their elections, they may be prompted for a decline reason for the elections they declined. This decline reason is based on the lexicon [X_BE_DECLINE_REASON]. This is a user defined lexicon which clients should populate with suitable decline reasons, unless the client will not be requiring decline reasons in which case the lexicon does not need to be updated.
At line 24 removed one line
This page (revision-37) was last changed on 26-Nov-2021 10:22 by rforbesTop