CC : Sheetal Bodhale

Hi Satya

We are working on this and will update you by monday.

Thanks,
Swapnil P.

Ok Swapnil, please share list of characters which can be allowed for Dependent SSN, we would get it confirmed with UHC first then we will start working on this change request.

Hi Jennifer Leugers

For Dependent SSN we cannot consider special characters ^ and ~ .
These special characters are used as data wipeout in Import and as a string concatenating character in EDS module.So using them could cause errors.

We can use one of below special characters:

1. ,*,%,!,<,>

We are considering below formats for SSN :
1)123456789 or ######### ( 9 digits or 9 special characters).
2)12345#### (5 digits and 4 special charaters ).
3)#####1234 ( 5 special characters and 4 digits).

Please let us know the format of SSN for Child ,Spouse and Beneficiary we are considering is fine or some other format is required .

CC:Satya Swapnil Pandhare Sheetal Bodhale

Hi Swapnil Pandhare & Chaitali Acharya,

I confirmed with UHC for special characters of Dependent SSN. They are fine with asterisk character *

On Dependents SSN (UI & Import) it should be allowed along with Beneficiary. On confirmation statement when there is * in database we can ignore it and display Null character symbol (---).

Let's schedule this enhancement on priority after WT-6447. UHC will continue using ^ symbol in address line 2 as it is not creating any issues with them as of now.

Rakesh Roy: We should start with test cases for including special characters.

Regards,
Satya Prakash

Nandkumar Prabhakar Karlekar: Can we check if there will be any changes required on ACA for this change?

Cc: shyam sharma Samir Vijay Siddha Sachin Hingole Jaideep Vinchurkar

Hi Satya

Based on Design Team Meeting Discussion we have certain queries mentioned in below document.
Queries for WT-6478.doc .
Please let us know further details on this.

CC:Swapnil Pandhare Sheetal Bodhale
Thanks,
Chaitali

Hi Satya

Based on Design Team Meeting Discussion we have certain queries mentioned in below document.

Queries for WT-6478 - Design Team Meeting.doc
Please let us know further details on this.

CC:Swapnil Pandhare Sheetal Bodhale
Thanks,
Chaitali Acharya

Hi Chaitali Acharya,

Can you please share the analysis document for the enhancement, this will help us in test cases writing, impact on Export / Import and testing scope.

Thanks,
Priya

Hi Priya Dhamande

Please thoroughly verify the enhancement.
1)Partner login
2)Company Admin Login
3)Employee Login(with without workflow)
with and without mandatory fields.
change the rights of the fields on spouse and child and check in workflow also without workflow.

As per discussion with Satya ,if Child ,Spouse SSN is mandatory and we enter *,it will be saved as null in database and bypass the SSN mandatory check on click of Continue button in workflow.

CC:Sheetal Bodhale Swapnil Pandhare
Thanks,
Chaitali Acharya

Environment: LB
Company: Caiso and MBF
Login: Partner, Company Admin and Employee

Testing in-progress.

Scenarios Covered Today:
1. Partner:

• Spouse [Spouse, ExSpouse, DP]
• Child [Natural, Step, Disabled Child]
• Confirmation statement Under header Dependents Information - Three dash appeared
• Confirmation statement PDF - Three dash appeared
• Export - Blank appears in place of *
  2. Company Admin:
• Spouse [Spouse, ExSpouse, DP]
• Child [Natural, Step, Disabled Child]
• Confirmation statement Under header Dependents Information - Three dash appeared
• Confirmation statement PDF - Three dash appeared
• Export - Blank appears in place of *
  3. Employee
• Spouse [Spouse, ExSpouse, DP]
• Child [Natural, Step, Disabled Child]
• Confirmation statement Under header Dependents Information - Three dash appeared
• Confirmation statement PDF - Three dash appeared

Pending Scenarios: need to check on Reports for all above scenarios. Willbe completing the reaming scenarios tomorrow and will move jira for Stage.

Environment: LB
Company: Caiso and MBF
Login: Partner, Company Admin and Employee

The enhancement is verified on LB and it is working as expected. Scenarios covered are updated in above comments. These are checked by changing the rights for Employee and CA login.

For Impact we have checked on: Confirmation Statement PDF, Confirmation statement
Under header Dependents Information, Export and Reports [Dependent Census].

As mentioned scenarios worked well so moving jira on Stage.

Environment: Stage
Company: Wheaton Franciscan Healthcare OE 2017 For HSPL
Login: Partner, Company Admin and Employee

Scenarios Covered:
1. Partner:

• Added Spouse [Spouse, ExSpouse, DP]
• Added Child [Natural, Step, Disabled Child]
• Verified on Confirmation statement Under header Dependents Information - Three dash appeared
• Verified on Confirmation statement PDF - Three dash appeared
• Export - Blank appears in place of *

2. Company Admin:

• Added Spouse [Spouse, ExSpouse, DP]
• Added Child [Natural, Step, Disabled Child]
• Verified on Confirmation statement Under header Dependents Information - Three dash appeared
• Verified on Confirmation statement PDF - Three dash appeared
• Export - Blank appears in place of *

3. Employee [verified by OE and New Hire Mode]

• Spouse [Spouse, ExSpouse, DP]
• Child [Natural, Step, Disabled Child]
• Confirmation statement Under header Dependents Information - Three dash appeared
• Confirmation statement PDF - Three dash appeared

We have checked Export, Report and Confirmation Statement for its Impact. As mentioned scenarios worked as expected moving jira on Production.

Environment: Production
Company: Utah Valley University For HSPL
Login: Partner, Company Admin and Employee

Scenarios Covered:
1. Partner:
Added Spouse [Spouse, ExSpouse, DP]
Added Child [Natural, Step, Disabled Child]
Verified on Confirmation statement Under header Dependents Information - Three dash appeared
Verified on Confirmation statement PDF - Three dash appeared
Export - Blank appears in place of *

2. Company Admin:
Added Spouse [Spouse, ExSpouse, DP]
Added Child [Natural, Step, Disabled Child]
Verified on Confirmation statement Under header Dependents Information - Three dash appeared
Verified on Confirmation statement PDF - Three dash appeared
Export - Blank appears in place of *

3. Employee [verified by OE and New Hire Mode]
Spouse [Spouse, ExSpouse, DP]
Child [Natural, Step, Disabled Child]
Confirmation statement Under header Dependents Information - Three dash appeared
Confirmation statement PDF - Three dash appeared

We have checked Export, Report and Confirmation Statement for its Impact.

Pending:
As WT-6897 patch, Import dependent SSN didn't went to production cannot verify the Import dependent through Ui. So, will able to complete jira once the mentioned jira goes to production and is verified.

verified the import Spouse and Child SSN through UI. Blank appears even if the SSN is inserted as '*' so closing jira on Production.

Jennifer Leugers: Can you pleas confirm from your end and close the jira.