Medium City of Claremont-Sunlife 834 Enrollment and Demographic change type.
This enhancement is related to EDI-22
After moving to change file testing, the only remaining issue we have is INS03 and INS04. They want a code based on the type of change. Please see below.
This is absolute requirement for Sun Life and we cannot pass testing without coding for this. How quickly can this achieved?
I have a call on Friday, 4/1 with the Broker and Carrier and need to have some indication of what how long this will take.
INS04:
INS04 maintenance code '25' should ONLY be used for a member SSN change.
You are sending member change INS03 ='001' with an INS04 value '25'.
For member demographic change, NON SSN, INS03 = '001' please use INS04 = '33'.
If INS04 = '25' is received for an existing client the transactions reject because we are trying to update an existing SSN with the same SSN.
General Guidelines:
Initial Enrollment - INS03 = '021'
USE: INS04 ='28' (initial enrollment)
Termination - INS03 = '024'
USE INS04 = '07' (benefit termination) or '08' (EE termination)
SSN Change - INS03 = '001'
USE: INS04 ='25'
Any Other Demographic Change: Address, Salary, Name etc. - INS03 = '001'
Use: INS04 = '33'
Rehire - INS03 = '021'
USE: INS04 = '41' (re-enrollment)
Unknown/Unidentified Change: INS03 ='001'
Use: INS04 = 'AI'
Thanks,
Chris
| Field | Original Value | New Value |
|---|---|---|
| Account Executive | Kiyo Takahashi [ ktak ] |
| Developer | Ganesh Sadawarte [ ganesh.sadawarte ] | |
| Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) |
| Status | New Request [ 10029 ] | Pending for Approval [ 10002 ] |
| Status | Pending for Approval [ 10002 ] | Approved for Development [ 10003 ] |
| Dev Due Date | 22/Apr/2016 |
| Dev Estimates | 80 |
| Stage Due Date | 27/Apr/16 [ 2016-04-27 ] |
| Status | Approved for Development [ 10003 ] | In Development [ 10007 ] |
| Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) | Parent values: Development(10200)Level 1 values: In Progress(10206) |
| Production Due Date | 03/May/2016 |
Rohan J KhandaveKiyo Takahashi[~chimane@ebsbenefits.com]
Hi Rohan,
Can you please provide the expected date for production deployment? I need to quote ETA of next test file to the broker.
In EDI-22, ETA for QA testing deployment is 4/22/2016. +2.5 working days for local testing = 4/26 - 4/27 Prod deployment? Please confirm.
Thanks,
Chris
Hi Chris,
ETA for QA Testing deployment as per our patch process is given below
LB Deployment - 04/22/2016
Stage Deployment - 04/27/2016
Production Deployment - 05/03/2016
Thanks & Regards,
Aniruddha Dev
| Description |
City of Claremont-Sunlife 834 Enrollment and Demographic change type. This enhancement is related to EDI-22 |
City of Claremont-Sunlife 834 Enrollment and Demographic change type. This enhancement is related to EDI-22 After moving to change file testing, the only remaining issue we have is INS03 and INS04. They want a code based on the type of change. Please see below. This is absolute requirement for Sun Life and we cannot pass testing without coding for this. How quickly can this achieved? I have a call on Friday, 4/1 with the Broker and Carrier and need to have some indication of what how long this will take. INS04: INS04 maintenance code '25' should ONLY be used for a member SSN change. You are sending member change INS03 ='001' with an INS04 value '25'. For member demographic change, NON SSN, INS03 = '001' please use INS04 = '33'. If INS04 = '25' is received for an existing client the transactions reject because we are trying to update an existing SSN with the same SSN. General Guidelines: Initial Enrollment - INS03 = '021' USE: INS04 ='28' (initial enrollment) Termination - INS03 = '024' USE INS04 = '07' (benefit termination) or '08' (EE termination) SSN Change - INS03 = '001' USE: INS04 ='25' Any Other Demographic Change: Address, Salary, Name etc. - INS03 = '001' Use: INS04 = '33' Rehire - INS03 = '021' USE: INS04 = '41' (re-enrollment) Unknown/Unidentified Change: INS03 ='001' Use: INS04 = 'AI' Thanks, Chris |
| Fix Version/s | 1.0 [ 10000 ] |
| Sprint | WT Sprint 1 [ 6 ] |
| Rank | Ranked higher |
| Item State | Parent values: Development(10200)Level 1 values: In Progress(10206) | Parent values: Development(10200)Level 1 values: Ready for Review(10208) |
| Item State | Parent values: Development(10200)Level 1 values: Ready for Review(10208) | Parent values: LB QA(10201) |
| Item State | Parent values: LB QA(10201) | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
| Assignee | Ganesh Sadawarte [ ganesh.sadawarte ] | Aniruddha Dev [ aniruddha.dev ] |
Affected Files:
1)App/BusinessLogic/ImportExportDTS/CommonExportRoutines.vb
2)App/BusinessLogic/ImportExportDTS/ExportConstants.vb
3)App/BusinessLogic/ImportExportDTS/ExportProcess.vb
4)App/BusinessLogic/ImportExportDTS/ExportProcessRowwise.vb
5)DatabaseObjects/MasterCompanyDB/
01_DDL/60_WT1667_WTB_Export_NewTable_ExportEnrollmentAndDemograhicChangeType.sql
6)Database Objects/MasterCompanyDB/01_DDL/61_WT1667_WTB_Export_NewData_Fields.sql
7)Database Objects/MasterCompanyDB/04_StoredProcedures/
OES_SP_Export_GetEnrollmentAndDemographicChangeType.sql
8)DatabaseObjects/MasterCompanyDB/01_DDL/
9)2_WT1667_WTB_Export_NewData_ExportEnrollmentAndDemograhicChangeType
10)Database Objects/OnlineEnrollment/01_DDL/10_WT1667_WTB_Export_NewData_Fields.sql
11)DatabaseObjects/OnlineEnrollment/01_DDL/
_WT1667_WTB_Export_NewTable_ExportEnrollmentAndDemograhicChangeType.sql
12) DatabaseObjects/OnlineEnrollment/01_DDL/
_WT1667_WTB_Export_NewData_ExportEnrollmentAndDemograhicChangeType.sql
Code Review: Rohan K.
| Attachment | 426201695307AM_1601_2.txt [ 16221 ] |
Blocked for Testing as getting server error while creating new ANSI template on LB on all companies. Please find attached error log 426201695307AM_1601_2.txt
Mail sent to Ashwin with error log
Hi Aniruddha Dev,
We have solve the LB error while creating ANSI template which get wrong BaseTemplateID in ImportExportDLL.cofig file.
Please check now.
Thanks,
Ganesh
Started testing on Column wise fixed length .Template till the ANSI issue gets resolved.
1) verified Demographic change (DOB) , enrollment Change (Re-Enrollment)
Above two are working fine
As ANSI Issue is resolved now. Will continue testing with ANSI 834 template.
*Testing is in progress *
Macro Name: Enrollment And Demographic Change Type
| Attachment | New field DTS.JPG [ 16491 ] |
Created ANSI 834 Template , Mapped Enrollment and Demographic change type field on Subscriber, Spouse and Child sub templates (PFA screenshot for DTS values) on ASML Temp company and verified below scenarios
1) New hire Enrollment
2) Only SSN Change
3) Enrollment Coverage amount change ( by Raising QE with 05/01/2016)
4) Employee Termination
5) Terminate Dependent Plan Elections (Spouse Life and Spouse AD&D)
6) other Demographic Changes (DOB)
7) Class Change (no effect on benefits)
8) SSN Change and Coverage Amount change
9) Terminate Employee Plan Elections
Result : Scenario #5 is not working. I've terminated dependent plan election (for Spouse Life and Spouse AD&D) . Made sure these plans are selected on the template and have their segments on subscriber and spouse sub template. Still the records is not getting exported on the file. WT-2151 is created for the same
| Status | Local Testing [ 10200 ] | Reopen in Local [ 10018 ] |
| Assignee | Aniruddha Dev [ aniruddha.dev ] | Ganesh Sadawarte [ ganesh.sadawarte ] |
Hi Aniruddha Dev,
CC- Rohan J Khandave
As this enhancement is not blocking any record. This is field level enhancement not record level. If any record is exporting on file in that case value field need to proper and if records not exporting file these will another scenarios ca you please continue with you testing as you created separate JIRA for this we will check and update
Thanks,
Ganesh
| Assignee | Ganesh Sadawarte [ ganesh.sadawarte ] | Aniruddha Dev [ aniruddha.dev ] |
| Item State | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) | Parent values: LB QA(10201)Level 1 values: In Testing(10210) |
| Status | Reopen in Local [ 10018 ] | In Development [ 10007 ] |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
Verified on Changes only and Full File Columnwise and City of claremont 834 5010 copy Template on ASML temp company on LB for above scenarios including Re-Enrollment scenario (where INS 04 should populate 41 ) for Enrollment and Demographic Change Type.
Working Fine
Note: Also Verified WT-2151. We can handle it through the customization.
| Item State | Parent values: LB QA(10201)Level 1 values: In Testing(10210) | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) |
| Status | Local Testing [ 10200 ] | Pending for Stage Approval [ 10300 ] |
Hello,
We were quoted production deployment for this enhancement today, 5/3. I see it is pending stage approval as of now. Broker just followed up asking if I will be running a file today and I have to say no.
Please advise when this will be deployed ASAP.
Thanks,
Chris
| Item State | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) |
| Status | Pending for Stage Approval [ 10300 ] | Approved for Stage [ 10030 ] |
| Status | Approved for Stage [ 10030 ] | Stage Testing [ 10201 ] |
Hi Chris,
The patch got delayed due to an internal issue found in LB testing . It has fixed now . We will deploy this on production tomorrow and will let you know once its deployed . Regret the inconvenience caused to you .
Thanks & Regards,
Aniruddha Dev
| Item State | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) |
| Item State | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) |
| Status | Stage Testing [ 10201 ] | Pending for Production Approval [ 10301 ] |
Verified on City of Claremont for HSPL company on stage on 'City of Claremont 834 5010' Template on Stage
Working as expected
| Status | Pending for Production Approval [ 10301 ] | Approved for production [ 10034 ] |
| Status | Approved for production [ 10034 ] | Production Testing [ 10202 ] |
| Item State | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) | Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) |
Verified this on City of Claremont for HSPL company on Production for 'City of Claremont SunLife 834 5010' template by mapping 'Enrollment and Demographic change type'macro for below fields on INS segment.
1) INS03 Maintenance Type Code
2) INS04 Maintenance Reason Code
and data transformed its values as per attached screenshots.
Working as expected
| Item State | Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) | Parent values: Production QA(10203)Level 1 values: In Testing(10218) |
| Attachment | INS 03.JPG [ 17010 ] |
Chris Ellenberger Kiyo Takahashi
Hello,
We have deployed this on production . Can you please verify this at your end and Close this JIRA ? Please let us know in case of any queries .
Thanks & Regards,
Aniruddha Dev
| Assignee | Aniruddha Dev [ aniruddha.dev ] | Kiyo Takahashi [ ktak ] |
| Resolution | Fixed [ 1 ] | |
| Status | Production Testing [ 10202 ] | Production Complete [ 10028 ] |
| Item State | Parent values: Production QA(10203)Level 1 values: In Testing(10218) | Parent values: Production Complete(10222) |
| Status | Production Complete [ 10028 ] | Closed [ 6 ] |
| Transition | Time In Source Status | Execution Times |
|---|
|
1d 23h 11m | 1 |
|
2s | 1 |
|
4d 3h 35m | 1 |
|
3d 8h 32m | 1 |
|
4d 19h 6m | 1 |
|
13d 20h 57m | 2 |
|
1m 5s | 1 |
|
1d 2h 15m | 1 |
|
1s | 1 |
|
20h 11m | 1 |
|
2h 24m | 1 |
|
2s | 1 |
|
3h 14m | 1 |
|
236d 6h 25m | 1 |
Hello Chris Ellenberger,
We have scheduled this enhancement on Monday(04/11/2016) as per our estimation it needs 10 working days for development
and 2.5 working days for local testing.
Thanks
CC-- Samir Vinayak Kulkarni Satya Hrishikesh Deshpande Aniruddha Dev