Please data transform 'Enrollment COBRA Qualifying Event Name' to the numeric values below or let us know if there is another solution.
Example, the field should contain 1,2,3 etc

1 - Termination of Employment
2 - Retirement
3 – Medicare Entitlement
4 – Death
5 - Ceasing to be an eligible dependent
6 - Reduced Hours
8 - Divorce or Separation
28 - Termination with Severance

Amit ThorveVinayak KulkarniCindy Wibbing

Hi Kanchan Jalgaonkar

Please check this, Thanks.

Hi Vinayak Kulkarni ,

I have added the config entries .

Thanks ,
Kanchan J

CC-Prajakta Belhe

Deploy config changes into production.

This is done. Kanchan Jalgaonkar, can you please check?

Vinayak Kulkarni

Hi Rochelle Thomas ,

We have made the changes , please verify at your end .

Thanks.

CC-Vinayak Kulkarni Rajendra Pawar

Hi Kanchan Jalgaonkar,
Thank you so much!! I tested and it looks good.
Closing the ticket.

Vinayak KulkarniAmanda Hagan

Email from Abhay,

EDI asked for data transformation of a field. It was done from the back-end. UI doesn't show that it is dt'ed. From the “support” point of view I wish to understand the details and whether this can be done by the user.
· Do we have a list of fields that are dt enabled?
· What makes a field eligible for dt, and what does it take to make it dt enabled (so that it shows up
· What steps are taken from back-end to dt? Can it at least be shown in UI as dt’ed?

Development comments:

Below are details about this field and at the end will have answers to your questions.

Here support work is done for a mapping field "Enrollment cobra qualifying event name", this field is used in cobra templates built using old approach i.e. template type Payroll data.

This field is used to get cobra event name on file like Termination, Divorce etc. Values may differ for different companies as per requirement. So values are kept in configuration file as below

If we don't have values in configuration file for a particular company then we have default set of values

We updated configuration file to get values for Rogers company as per client requirement. However we are using "data transform" terminology wrongly, There is no relation of our regular data transformation with this support task.

We do have alternative in which user can achieve this from screen by creating cobra template using new approach i.e. template type COBRA data, in this we have another field which pulls out reason

This field points to event builder cobra reason, these events are part of setting up new cobra approach.

Once we map this field, we get data transformation available in pop-up

Below are answers to your questions

#1 Do we have a list of fields that are dt enabled?

Yes, this Field Mapping Definitions.xlsx tells whether field is DTS applicable or not in last column, also if we get any field in data transformation page then its a DTS applicable field.

#2 What makes a field eligible for dt, and what does it take to make it dt enabled (so that it shows up

if values are fixed set of values, We call it as meta-data, if its a meta-data then its DTS applicable.
State, country & gender are examples of such fields.

Also we have implemented/extended DTS feature to some of fields like Enrolled Plan name & classes, these have fixed set of values but values are defined by user, we call it as transactional meta-data, few such type of fields are DTS applicable and we can make such fields as DTS applicable field by doing some code change if we want.

#3 What steps are taken from back-end to dt? As stated above, We have modified back-end config file.

Can it at least be shown in UI as dt’ed? No.

Let us know if you have any questions on this, Thanks.

Thanks a lot Vinayak Kulkarni!
It appears that "Enrollment cobra qualifying event name" is directly read from the enrollment. They also appear to be a fixed set of values as seen in the default values below - and these are not defined by users (like plan names and classes). Therefore not clear why they are not treated as metadata and DTS enabled.

Hi Abhay,

Our DTS information gets stored into specific database table and we can only show a field as DTS enabled if it has information stored into this table. below is snap of state DTS field

On other hand, config files are stored outside of table and we can see them disconnected from application ( logic and databases) .

We can make it DTS applicable by doing code changes, However we already have introduced new cobra approach which solves our purpose and is DTS applicable.