Hi Revansiddha Gaur

Please refer this ticket for new changes 2017.

FYI Nandkumar Prabhakar Karlekar,Sachin Hingole,Kumar Chhajed

New Jira for Wheton

Hi Smita Pawar,

Jan file is sent to you by mail for testing.

CC: Mahendra Mungase Sachin Hingole Nandkumar Prabhakar Karlekar.

New requirement implementation is done. Now its in QA testing.

Sachin Hingole Nandkumar Prabhakar Karlekar

Hi Van Nguyen,

We are sending Jan & Feb 17 files as per new requirement for tango.
Actually testing is in progress at our end also.
Please review it and let us know if any feed back for same.

FTP details are as follows.

URL:https://ftpsecure.ebsbenefits.com
Path:/users/workterraaca/BSG ACA/Ascension Wisconsin/03242017
Folders: 1. Jan.zip 2.Feb.zip

Thanks,
Smita

FYI Nandkumar Prabhakar Karlekar,Sachin Hingole,Revansiddha Gaur,Kumar Chhajed

Hi Van Nguyen,

Please let us know feed back for files if you have any.

Thanks,
Smita

FYI Nandkumar Prabhakar Karlekar,Sachin Hingole,Revansiddha Gaur,Kumar Chhajed

Hi Nandkumar Prabhakar Karlekar, Mahendra Mungase,

The BSG is expecting the test files tomorrow that includes the new coding of the plans based on rates.

Van Nguyen

We have already delivered Jan and Feb files 6 day's ago and we are waiting for the feedback. I think you have not refereed the smita's comment 6 day's ago.

We have delivered these file early to manage any type of risk because we need 2-4 days to refurnish these files.

[~chimane@ebsbenefits.com],Jennifer Leugers

Nandkumar Prabhakar Karlekar,

I have not heard back from BSG in regards to the files. I will follow up with her. I did post the files to the EBS SFTP site for her to review on 3/27/2017.

Feedback from BSG:

I reviewed the DEM 35366211120170324061806.csv file today and I have some feedback

Why are there multiple lines of data showing up for an individual with exactly the same information? See Jackie Anderson for an example, she has 5 individual lines of data, everything is exactly the same.

Employment Status file (Column T) shows as FT for all employees except for 1 – this field should be mapped to the Wheaton Employee Type UDF for proper information the valid records should be Full Time (FT), Part Time (PT) or Per Diem (VA) not everyone is FT.

The employee Type field in Workterra is typically not populated for this group as they have the UDF to identify the proper employment status.

Enrolled Plan ID (Column AP) and
Offered Plan ID (Column AQ) are blank. There should be data of WPPO and WHDHP populated in these fields.

Enrolled Plan ID should be the plan that the employee is actually enrolled in. The Offered Plan ID will default to WHDHP for everyone except for those that are in the Socially Just Plans, they would have the WPPO as their offered Plan ID, I believe.

How is the employment Status Effective Date populating? For example on Jackie Anderson, I see an Employment Status Effective Date of 2/15/2017, is that based on the date she moved to a LOA status?

Patricia Wolff (PT employee) has enrollment in the HDHP effective 1/1/2017, yet she is not showing up on the report. Are there others and why isn’t she populating on the report?

There are 124 records showing a benefit eligibility date prior to 1/1/2017, it seems like the earliest effective date should be 1/1/2017 since this is based on the 2017 Plan year.

Benefits Eligibility Terminate Date (Column Y) This is the last day of the employee’s medical benefits eligibility. For someone terminating employment the benefits run through the end of the month. How can there be a date in the middle of the month for an employee? Please see Jacob Allen – he is showing with a termination of 2/20/2017 when actually Single Tier ended and Family tier began 2/21/2017 – 2/28/2017. Benefits for Jacob did run through 2/28/2017, not sure why 2/20/2017 is populating in Column Y. There are 27 records (18 unique employees) that have a Benefits Eligibility Terminate date other than the end of the month. Some may be due to a Qualified Life Event, but I believe others would be a mid-month tier change as noted above.

File naming convention is incorrect and the DEP Files are missing.

Also, since these are monthly files is it appropriate for February data to be showing on the January file, or should it just represent January activity?

Kim

Hi Van Nguyen,

We have analysed the issues mentioned above.
Most of them are of customization, we will change customization. Few items are with Dev team.

We will update Delivery date by tomorrow EOD. [04/05/2017]

Thanks,
Smita

FYI Nandkumar Prabhakar Karlekar,Sachin Hingole,Kumar Chhajed,Revansiddha Gaur

Hi Van Nguyen,

We can provide corrected Tango files on 15 April 2017 or before that.

Thanks,
Smita

FYI Nandkumar Prabhakar Karlekar,Sachin Hingole,Kumar Chhajed,Revansiddha Gaur

Hi Smita,

BSG requested for the test files to be available my tomorrow if possible. They have a deadline of April 10th to send the reports to Tango, but BSG will not have enough time to audit the file if it is not available by tomorrow. Please advise. Thank you.

Hi Van Nguyen,
Please find inline Harbinger comments.

Point 1:
Why are there multiple lines of data showing up for an individual with exactly the same information?See Jackie Anderson for an example, she has 5 individual lines of data, everything is exactly the same.

Harbinger Comment: We have resolved this issue by customization.Hencefore multiple rows for coverage same date won't come on file.

Point 2:
Employment Status file (Column T) shows as FT for all employees except for 1 – this field should be mapped to the Wheaton Employee Type UDF for proper information the valid records should be Full Time (FT), Part Time (PT) or Per Diem (VA) not everyone is FT.The employee Type field in Workterra is typically not populated for this group as they have the UDF to identify the proper employment status.

Harbinger Comment: We have resolved this issue by customization.Hencefore data as per the UDF will occure on file.

Point 3:
Enrolled Plan ID (Column AP) and Offered Plan ID (Column AQ) are blank. There should be data of WPPO and WHDHP populated in these fields.
Enrolled Plan ID should be the plan that the employee is actually enrolled in. The Offered Plan ID will default to WHDHP for everyone except for those that are in the Socially Just Plans, they would have the WPPO as their offered Plan ID, I believe.

Harbinger Comment: We have resolved this issue by customization. Hencefore plan ID will get populated as per plan.

Point 4:
How is the employment Status Effective Date populating? For example on Jackie Anderson, I see an Employment Status Effective Date of 2/15/2017, is that based on the date she moved to a LOA status?

Harbinger Comment: Yes, We are populating the Latest employee status change date .
Van Nguyen :Please confirm same at your end with client.

Point 5:
Patricia Wolff (PT employee) has enrollment in the HDHP effective 1/1/2017, yet she is not showing up on the report. Are there others and why isn’t she populating on the report?

+Harbinger Comment:+In latest run of file, we found this employee.

Point 6:

File naming convention is incorrect and the DEP Files are missing.

+Harbinger comment: Files shall be named using the three letter file type code (DEM, BEN, RET, PAY, DEP, or LOA), followed by the reporting entity's EIN (Employer Tax ID), followed by a timestamp (YYYYMMDDHHMMSS). The timestamp should represent the effective date of the information in the file, often the time the file was generated. For example, a Demographic file for an EIN 999999998 containing data accurate as of July 31st, 2015 at 12:00 PM would have a filename of DEM99999999820150731120000.
e.g - DEM36326211120170407060432.csv
Below is the explanation

DEM 363262111 2017 04 07 06 04 32.csv
Type code EIN YYYY MM DD HH MM SS

Van Nguyen: Please confirm same with client.

Development Team is working on below points.

There are 124 records showing a benefit eligibility date prior to 1/1/2017, it seems like the earliest effective date should be 1/1/2017 since this is based on the 2017 Plan year.
Benefits Eligibility Terminate Date (Column Y) This is the last day of the employee’s medical benefits eligibility. For someone terminating employment the benefits run through the end of the month. How can there be a date in the middle of the month for an employee? Please see Jacob Allen – he is showing with a termination of 2/20/2017 when actually Single Tier ended and Family tier began 2/21/2017 – 2/28/2017. Benefits for Jacob did run through 2/28/2017, not sure why 2/20/2017 is populating in Column Y. There are 27 records (18 unique employees) that have a Benefits Eligibility Terminate date other than the end of the month. Some may be due to a Qualified Life Event, but I believe others would be a mid-month tier change as noted above.

Also, since these are monthly files is it appropriate for February data to be showing on the January file, or should it just represent January activity?

Revansiddha GaurRevan: Please update for remaining points.

Thanks,
Smita

Hi Van Nguyen and Debbie Kulling

We have exported DEM and DEP files for 3 Months-Jan,Feb,Mar 2017 and uploaded on FTP.

Please download files from below FTP location.

FTP URL - https://ftpsecure.ebsbenefits.com/

FOLDER PATH - /users/workterraaca/BSG ACA/Ascension Wisconsin/10April2017

File Names:
1.DEM FIle Name - 1.DEM JanFebMar_Employee_2017.zip
2.DEP File Name - 2.DEP JanFebMar_Dependents_2017.zip

Thanks,
Revan

Smita Pawar Sachin Hingole Nandkumar Prabhakar Karlekar

Hi Van Nguyen,

Can we get feedback on Jan,Feb and March month Tango files.

Debbie Kulling,Abhay Patil

Hi Nandkumar Prabhakar Karlekar,

I have not heard back yet, but I followed up with Tamkeen and Scott today.

Hi Nandkumar Prabhakar Karlekar,

Per Tamkeen at BSG, it is best to wait for Kim's feedback when she returns from vacation on Tuesday, April 18th.

Please find the mail communication reply for feedback. Ascencion Wisconsin (Wheaton) ­ Tango ­ WT­8884 Request.pdf.

Smita Pawar Mahendra Mungase Sachin Hingole Nandkumar Prabhakar Karlekar

Hi Nandkumar Prabhakar Karlekar,

Kim at BSG would like to know when the next test files will be available. Please let us know.

Hi Van Nguyen,Alex Nguyen

We have uploaded Eligible & Ineligible Combined files for the month Jan, Feb, Mar, Apr 2017.
Previously sent [3 May 2017] Dependent files are sending again.
Details of uploaded files are as follows.

URL: https://ftpsecure.ebsbenefits.com
Path: /users/workterraaca/BSG ACA/Ascension Wisconsin/05092017
Folder: Delivery 9 May 2017.zip

Thanks

FYI Amit Thorve,Nandkumar Prabhakar Karlekar,Revansiddha Gaur,Kumar Chhajed

Latest update on test files:

Hi Kim,

Thank you for the detailed explanation. We will proceed with reviewing and loading the four 2017 files and then analyze the results.

Scott Van Horn
Tango Health
svanhorn@tangohealth.com
855-468-2646 x 803 Direct Phone

From: Van Nguyen van.nguyen@ebsbenefits.com
Sent: Wednesday, May 10, 2017 10:22 AM
To: 'Kim Matus' <Kim.Matus@bsg.com>; Scott Van Horn <svanhorn@tangohealth.com>; Salman Khoja <SalmanK@tangohealth.com>
Cc: Carrie Craft <ccraft@tangohealth.com>; 'Hanley, Karen' <Karen.Hanley@ascension.org>; Tamkeen Siddiqui <Tamkeen.Siddiqui@bsg.com>; Sherri Hauser <Sherri.Hauser@bsg.com>; Amit Thorve <amit.thorve@ebsbenefits.com>
Subject: RE: Question regarding 2017 Ascension Files

Hi Scott,

The 8 files have just been posted.

Thank you,
Van Nguyen | EDI Analyst
Employee Benefit Specialists, Inc.
PO Box 11657, Pleasanton, CA 94588
Direct: 925-621-5250 | Cell: 209-275-9486
FAX: 925-460-3920 | van.nguyen@ebsbenefits.com

_______________________________________________________________________________________________________________________________________

Total Enrollment Services l Employer & Employee Member Portals l Flexible Spending Accounts l Commuter Benefits
Employer Flex Benefit Card l COBRA & Retiree Administration l Invoice Reconciliation l Voluntary Benefits

www.ebsbenefits.com www.workterra.com

DISCLAIMER
This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary, confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately.

From: Kim Matus Kim.Matus@bsg.com
Sent: Wednesday, May 10, 2017 8:11 AM
To: 'Scott Van Horn' <svanhorn@tangohealth.com>; Salman Khoja <SalmanK@tangohealth.com>
Cc: Carrie Craft <ccraft@tangohealth.com>; 'Hanley, Karen' <Karen.Hanley@ascension.org>; Tamkeen Siddiqui <Tamkeen.Siddiqui@bsg.com>; Sherri Hauser <Sherri.Hauser@bsg.com>; Van Nguyen <van.nguyen@ebsbenefits.com>
Subject: RE: Question regarding 2017 Ascension Files

Scott:

I think the only way to determine if these files will work as expected is to have Workterra send you the 4 DEM and DEP files for January – April 2017 and have you load them.

After they are loaded we can review some of the scenarios that I have concerns with,

James Manto - employee moved from a Benefit Ineligible to a Benefit Eligible position in March. He shows up on the Jan and Feb reports with a PT Employment Status, isn’t on the March report and is again on the April report but in this case his Benefit eligibility date, opt out date and minimum coverage effective date are all populating with 3/27/2017, the date of the change.

Nancy Bechtel – scenario discussed below

Pamela Abernathy – Qualified Life Event where 1 of 3 dependent children were dropped from the medical plan in February. I want to make sure dates are correct and the dependents are loading and then will report correctly. We also asked Workterra to make some changes to the date logic due to these QLEs.

All employees are now reporting not only those that are Benefit Eligible. This set of reports is the first time we have captured the entire population housed in the Workterra system.

I have asked Van to post the 4 DEM and 4 DEP files to the Tango FTP site today. Hopefully this plan of action will help you to identify if there will still be issues and if the manual updates may be the best way to handle these if still issues. Perhaps once the files are loaded we can discuss the above scenarios to make sure data will report as expected.

Kim

From: Scott Van Horn svanhorn@tangohealth.com
Sent: Wednesday, May 10, 2017 9:58 AM
To: Kim Matus <Kim.Matus@bsg.com>; Salman Khoja <SalmanK@tangohealth.com>
Cc: Carrie Craft <ccraft@tangohealth.com>
Subject: RE: Question regarding 2017 Ascension Files

Hi Kim,

I totally understand how challenging this is!

If the Employment Status Effective Date is 2/1/2016 my fear (I’d have to test it to find out) is that we’d have a duplicate employment status of FT and VA since 2/1/2016 since that field will trump the filename timestamp. If Field 44 were removed (which is what we did when we loaded the historical files for this very reason) then we’d consider them VA as of the file timestamp, which would be March.

That all being said, it may not actually matter. The ACA law says until someone is in a stability period, you consider the employment status as of their date of hire. This employee would be in a new hire measurement period from 2/1/2016 until 1/31/2017 and then in a stability period 3/1/2017-2/28/2018 based on hours during the measurement. Even if they moved to VA on 12/1/2016, we still would treat them as FT until we had a MP result. If the hours were below 30 hours, we’d treat them as PT from 3/1/2017 onwards. If above 30 hours we’d treat them FT from 3/1/2017 even if Ascension thinks they are VA.

All that said — I think we’re going to be ok. We just may need to ignore that Field 44 so that we don’t retro their employment status. Does that make sense?

Scott Van Horn
Tango Health
svanhorn@tangohealth.com
855-468-2646 x 803 Direct Phone

From: Kim Matus Kim.Matus@bsg.com
Sent: Wednesday, May 10, 2017 9:47 AM
To: Scott Van Horn <svanhorn@tangohealth.com>; Salman Khoja <SalmanK@tangohealth.com>
Cc: Carrie Craft <ccraft@tangohealth.com>
Subject: RE: Question regarding 2017 Ascension Files

What if the Employment Status Effective date in field 44 isn’t showing 2/12/2017 but rather 2/1/2016, her date of original employment? You wouldn’t then be able to leverage that field.

Also, I found another situation where an employee moved from a Benefit Ineligible to a Benefit Eligible position in March. He shows up on the Jan and Feb reports with a PT Employment Status, isn’t on the March report and is again on the April report but in this case his Benefit eligibility date, opt out date and minimum coverage effective date are all populating with 3/27/2017, the date of the change. My guess is this will also cause issues for Tango.

We really are getting closer, it is just these stragglers that are making me a bit nuts.
Kim

From: Scott Van Horn svanhorn@tangohealth.com
Sent: Wednesday, May 10, 2017 9:35 AM
To: Kim Matus <Kim.Matus@bsg.com>; Salman Khoja <SalmanK@tangohealth.com>
Cc: Carrie Craft <ccraft@tangohealth.com>
Subject: RE: Question regarding 2017 Ascension Files

Hi Kim,

Good questions. This should not be a big concern since we are leveraging the hours from Payroll (through the measurement period) to determine their actual ACA employment status. However, last year’s files leveraged a field “Employment Status Effective Date” that give us what we need.

In your example, is the 2/12/2017 date in Field 44 (Employment Status Effective Date)? If so, we’ll tie that date with the change to VA. That is our way to handle cases where we find out about a change in an earlier month but in a later file.

Scott Van Horn
Tango Health
svanhorn@tangohealth.com
855-468-2646 x 803 Direct Phone

From: Kim Matus Kim.Matus@bsg.com
Sent: Wednesday, May 10, 2017 9:08 AM
To: Scott Van Horn <svanhorn@tangohealth.com>; Alex Mize <AlexM@tangohealth.com>; Salman Khoja <SalmanK@tangohealth.com>
Subject: Question regarding 2017 Ascension Files

I am reviewing what I hope to be final files for the Ascension ACA reporting for 2017. I have a quick question regarding the data. Workterra is only able to capture current employment status, not the status that was actual during the month of reporting.

For example, Nancy Bechtel was FT in January 2017 carrying benefits and then moved to a VA position February 12, 2017. She carried benefits in February as well. When I am reviewing the January file, her data shows correctly, but she is listed as a VA employee rather than FT. Will this cause issues at Tango or will the data you are receiving from the payroll side correct this?

If the employment status data is a concern the only way to correct would be manually for around 200 employees that had changes in their Benefit Eligibility Status in 2017. I would guess I would need to make the appropriate changes on each of the 4 applicable months DEM files.

This is how her record looks on the January file showing VA as Employment Status and 2/28/2017 as the Eligibility Termination date, even though this is January data.

Please let me know if this will be a concern and if not, I think the files look good and I can get them posted to Tango as soon as you weigh in on the above question.

Thanks
Kim Matus, MILR, GBA
Account Manager
The Benefit Services Group, Inc. | www.bsg.com
N25 W23050 Paul Road, Pewaukee, WI 53072
Phone: 262-521-5700, ext. 1033 | Fax: 262-521-5710
Direct Dial: 262-446-5933
E-mail: Kim.Matus@bsg.com

Wellness Council of America (WELCOA) – Gold Well Workplace Award
American Heart Association – Bronze Workplace Health Achievement
The Business Journal three-time recipient – Healthiest Employer Small Business Award

The information contained in this communication may be confidential, is intended only for the use of the recipient(s) named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender.

I followed up with Tango on the results to the latest files.

Tango is still testing the latest files.

Feedback from Tango in regards to latest test files:

Hi Van Nguyen,

Could you please clear action points on received feedback.

Thanks,

FYI Nandkumar Prabhakar Karlekar, Sachin Hingole,Rakesh Roy,Revansiddha Gaur

I am closing this ticket as Kim at BSG confirmed that the data from the last files were good and no more testing is required on Workterra's side.

Kim: It sounds like from review the data from Workterra is good and loading as expected. We only have 1 more week of access to the Workterra site, as it will be archived on June 16th at 11:59pm CST. At this point there is no anticipation of any additional of different reports needed for ACA reporting purposes.