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 7 changed one line
!Step 1: IBPT – Define Benefit Plan Types
!Step 1: IBPT – Define Benefit Plan Types
At line 9 changed 2 lines
;[Plan Type|PLAN_TYPE_CODE]:This field holds the defined plan type code that uniquely identify the plan type. The Plan Type will be displayed in the [WEBOEE] form so it should be reflective of the plans within the type.
;[Plan Type|PLAN_TYPE_CODE]:This field uniquely identifies the plan type. The Plan Type will be displayed in the [WEBOEE] form so it should be reflective of the plans within the type.
At line 12 removed one line
;[Recipient Type|RECIPIENT_TYPE]:This field is used by the BSS module only. This can be used to define a recipient type if all of the plans linked to the plan type allow the same type of recipient to be enrolled. If an employee is only allowed to elect themselves in the plan, ‘Not Applicable’ should be used. If the plans allow for different participant types a recipient type can be defined at the coverage level. The type of recipient defined will filter the list of benefit recipients available to the employee for that plan during the election period. The filtration is done by comparing the recipient type lexicon values to the stored values of the [relation lexicon|X_RELATION] in [IECT]. The system will check for a recipient type at the coverage first, if none are found it will then check the plan type to see if one has been defined at that level. If the system cannot locate a recipient type for either the coverage or plan type, all of the employee’s contacts defined in [IECT] will be listed for the employee to elect. The page [Benefit Recipient Matrix for Open Enrollment|BENEFIT RECIPIENT MATRIX FOR OPEN ENROLLMENT] shows which relation values fall under each of the recipient types.
At line 14 removed one line
;[Plan Type URL |PLAN_TYPE_URL]:A URL can be defined to provide the employees with a link in to external documentation that may provide additional information on each plan within the plan type, or to a carrier’s website. This will be displayed on the SS election form [WEBOEE] beneath the Election Intro ext.
At line 16 removed one line
;[Description|DESCRIPTION]:Ensure a description has been defined and is reflective of the plans within the plan type as this will be visible in [WEBOEE]. Basic HTML tags can be used to tailor the look of the text.
At line 14 added 3 lines
;[Recipient Type|RECIPIENT_TYPE]:This field is used by the BSS module only. This can be used to define a recipient type if all of the plans linked to the plan type allow the same type of recipient to be enrolled. If an employee is only allowed to elect themselves in the plan, ‘Not Applicable’ should be used. If the plans allow for different participant types a recipient type can be defined at the coverage level. The type of recipient defined will filter the list of benefit recipients available to the employee for that plan during the election period. The filtration is done by comparing the recipient type lexicon values to the stored values of the [relation lexicon|X_RELATION] in [IECT]. The system will check for a recipient type at the coverage first, if none are found it will then check the plan type to see if one has been defined at that level. If the system cannot locate a recipient type for either the coverage or plan type, all of the employee’s contacts defined in [IECT] will be listed for the employee to elect. The page [Benefit Recipient Matrix for Open Enrollment|BENEFIT RECIPIENT MATRIX FOR OPEN ENROLLMENT] shows which relation values fall under each of the recipient types.
;[Plan Type URL |PLAN_TYPE_URL]:A URL can be defined to provide the employees with a link in to external documentation that may provide additional information on each plan within the plan type, or to a carrier’s website. This will be displayed on the SS election form [WEBOEE] beneath the Election Intro ext.
;[Description|DESCRIPTION]:Ensure a description has been defined and is reflective of the plans within the plan type as this will be visible in [WEBOEE]. Basic HTML tags can be used to tailor the look of the text.
At line 20 added one line
At line 22 added 5 lines
;Sequence:A sequence should be defined as this will determine the order the plan types are displayed to the employee in the election form. If a sequence is not defined, the plan types will display in alphabetical order.
;Recipient Type:This can be used to define a recipient type if all of the plans linked to the plan type allow the same type of recipient to be enrolled. If an employee is only allowed to elect themselves in the plan, ‘Not Applicable’ should be used. If the plans allow for different participant types a recipient type can be defined at the coverage level.
;Plan Type URL:A URL can be defined to provide the employees with a link to external documentation that may provide additional information on each plan within the plan type, or to a carrier’s website. This will be displayed on the SS election form beneath the Election Intro ext.
;Description:Ensure a description has been defined and is reflective of the plans within the plan type as this will be visible in WEBOEE. Basic HTML tags can be used to tailor the look of the text.
;Election Intro Text:This field is used to include introductory text to the plans. This can be used to provide additional instructions to employees. Basic HTML tags can be used to tailor the look of the text.
At line 136 removed 7 lines
!Step 1: IBPT – Define Benefit Plan Types
;Plan Type:This type should be descriptive of the plans associated to it as it is displayed in WEBOEE.
;Sequence:A sequence should be defined as this will determine the order the plan types are displayed to the employee in the election form. If a sequence is not defined, the plan types will display in alphabetical order.
;Recipient Type:This can be used to define a recipient type if all of the plans linked to the plan type allow the same type of recipient to be enrolled. If an employee is only allowed to elect themselves in the plan, ‘Not Applicable’ should be used. If the plans allow for different participant types a recipient type can be defined at the coverage level.
;Plan Type URL:A URL can be defined to provide the employees with a link to external documentation that may provide additional information on each plan within the plan type, or to a carrier’s website. This will be displayed on the SS election form beneath the Election Intro ext.
;Description:Ensure a description has been defined and is reflective of the plans within the plan type as this will be visible in WEBOEE. Basic HTML tags can be used to tailor the look of the text.
;Election Intro Text:This field is used to include introductory text to the plans. This can be used to provide additional instructions to employees. Basic HTML tags can be used to tailor the look of the text.
At line 143 added one line
This page (revision-37) was last changed on 26-Nov-2021 10:22 by rforbesTop