Revansiddha Gaur (Inactive) added a comment - 21/Sep/16 06:59 AM Sachin Hingole shyam sharma HI Nandkumar Prabhakar Karlekar , Still discussion is not cleared for this Jira. Keeping on hold. Regards, Revan

Yogesh Chaudhari (Inactive) added a comment - 07/Feb/17 05:32 AM - edited Assigning to Revan Nandkumar Prabhakar Karlekar

Revansiddha Gaur (Inactive) added a comment - 26/Feb/18 07:15 AM Hi Amit Thorve , As per current implementation, enrollment data gets populated correctly irrespective of any transition take place like class change, address change etc. But the thing is if any demographic fields are mapped in a template, will be populated only latest demographic data on a file which is less important for the ACA files. To clarify with more detail, please go through our example as below.. Ex: XYZ employee Class1-C1 Address- ABC Effective Date- 01/01/2017 to 02/28/2017 Eligible plans- p1,p2,p3 Enrolled in- Plan p2 with effective from 01/01/2017 Now changes happen as below.. Class1-C2 Address- DEF Effective Date- 03/01/2017 to NULL Eligible plans- p4,p5,p6 Enrolled in- Plan p4 with effective from 03/01/2017 Exporting -> Suppose today we export a file for Jan month (01/01/2017 to 01/31/2017), will be populated data on the file with his Jan month eligible plans like p1,p2,p3 and his Jan month enrollment data with enrolled as p2 but demographic details of latest only i.e. C2 as Class1, DEF as Address( these data of demographic only discrepancy but this is less important for ACA perspective.) We approached to get the approval for the ticket and discussed with Samir that such requirement is not arisen till now from any client till that period we should hold on this JIRA. Please let us know your view on this, still this is required, please provide approval. Thanks, Revan CC- Nandkumar Prabhakar Karlekar , Satya , Samir , Ramya Tantry , Smita Pawar , Sachin Hingole